Method for performing communication in wireless communication system and apparatus therefor

Abstract

Disclosed, according to various embodiments, are a method for performing communication in a wireless communication system and an apparatus therefor. Disclosed are a method and an apparatus therefor, the method comprising: performing a first measurement for a first measurement resource and a second measurement for a second measurement resource; preferentially allocating transmission power to one uplink signal from among a first uplink signal and a second uplink signal, on the basis of a total transmission power of a first transmission opportunity for the first uplink signal including the first measurement and the second uplink signal including the second measurement exceeding a maximum transmission power of a UE; and transmitting the first uplink signal and the second uplink signal.

Description

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

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

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

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

[0004] The technical challenge is to provide a method for performing operations that report 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 performing a first measurement for a first measurement resource and a second measurement for a second measurement resource; preferentially allocating transmission power to one of the first uplink signal and the second uplink signal based on a total transmission power of a first transmission opportunity for a first uplink signal including the first measurement and a second uplink signal including the second measurement exceeding a maximum transmission power of the UE; and transmitting the first uplink signal and the second uplink signal; wherein the one uplink signal can be determined based on a report type of a measurement.

[0007] Alternatively, (i) the first measurement is a measurement for reporting channel state information (CSI) and (ii) the second measurement is a measurement for reporting cross link interference (CLI), wherein the one uplink signal is the second uplink signal.

[0008] Alternatively, the one uplink signal is characterized as being the first uplink signal, based on (i) the first measurement being a measurement for CSI (channel state information) reporting and (ii) the second measurement being a measurement for CLI (Cross Link Interference) reporting.

[0009] Alternatively, the first uplink signal is characterized in that the one uplink signal is determined based on the type of the measurement, based on the first uplink signal having the same priority index as the priority index of the second uplink signal.

[0010] Alternatively, the method further comprises receiving configuration information for a first time interval related to SBFD (Sub-Band Full-Duplex); and, based on the second measurement including a plurality of CLI measurements, the UE determines a priority among the plurality of CLI measurements based on whether the CLI measurements are measured on a measurement resource within the first time interval.

[0011] Alternatively, among the plurality of CLI measurements, a CLI measurement measured in a measurement resource within the first time interval has a higher priority than a CLI measurement measured in a measurement resource within a second time interval that is not related to the SBFD.

[0012] Alternatively, based on the second measurement including a plurality of CLI measurements, the UE is characterized in that it determines a priority among the plurality of CLI measurements based on whether the CLI measurements are event-triggered.

[0013] Alternatively, the UE performs CA (Carrier Aggregation) communication based on a first carrier and a second carrier, wherein the first uplink signal is transmitted through the first carrier, and the second uplink signal is transmitted through the second carrier.

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

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

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

[0017] Various embodiments enable the terminal to accurately and efficiently report measurements to the base station.

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

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

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

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

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

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

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

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

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

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

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

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

[0030] FIG. 13 is a diagram illustrating a method for a UE to allocate transmission power among uplink signals transmitted on multiple carriers.

[0031] Figure 14 illustrates a communication system applied to the present invention.

[0032] Figure 15 illustrates a wireless device applicable to the present invention.

[0033] Fig. 16 shows another example of a wireless device applied to the present invention.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0064] Bandwidth part (BWP)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0094] CSI-related actions

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0112] QCL (quasi-co location)

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

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

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

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

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

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

[0119] L3 CLI Report

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

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

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

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

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

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

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

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

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

[0129] 4> else:

[0130] 5> ifreportQuantityCLIis set tosrs-rsrp:

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

[0132] 5> else:

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

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

[0135] 5> include thesrs-ResourceId;

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

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

[0138] 5> include therssi-ResourceId;

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

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

[0141] Periodic configuration / event trigger

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0158] Beam Management (BM)

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

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

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

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

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

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

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

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

[0167] Full duplex operation for NR

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0182] (1) Measurement resource aspect

[0183] 1) About d / f TDD

[0184] - Aggressor: Inter-cell UE

[0185] - HD slot only

[0186] 2) About SBFD

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

[0188] - HD slot & SBFD slot

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

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

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

[0192] (1) Measurement resources

[0193] > SRS-Resource

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

[0195] - For CLI SRS-RSRP measurements

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

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

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

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

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

[0201] -- SRS Port 1

[0202] > CLI-RSSI-Resource

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

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

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

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

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

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

[0209] (2) Measurement / report trigger

[0210] > SRS-RSRP, CLI-RSSI

[0211] > Event triggered or periodical

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

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

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

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

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

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

[0218] > Background

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

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

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

[0222] > Measure resource

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

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

[0225] > Report

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

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

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

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

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

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

[0232] -> For SBFD settings,

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

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

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

[0236] -> Coexistence

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

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

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

[0240] (1) Scenario 1

[0241] -> gNB-to-gNB CLI

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

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

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

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

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

[0247] -> UE-to-UE CLI

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

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

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

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

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

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

[0254] (2) Scenario 2

[0255] -> gNB-to-gNB CLI

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

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

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

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

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

[0261] -> UE-to-UE CLI

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

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

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

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

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

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

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

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

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

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

[0272] In addition, it is described below that L1 / L2 CLI measurement / reporting can be performed by reusing the existing CSI framework. In this context, the CSI framework-based L1 / L2 CLI may consider the following approaches. A method of adding a configuration for CLI to the CSI reporting configuration (e.g., Periodic / Semi-periodic / Aperiodic CLI-RSSI resources and / or SRS resources, report quantity (CLI-RSSI, SRS-RSRP)) may be considered. For example, the UE may additionally obtain a configuration for CLI measurement / reporting from the CSI reporting configuration from the gNB. At this time, the UE may report the measurement results measured in the resource for CLI measurement to the base station via UCI based on the configuration for CLI measurement / reporting (e.g., report configuration ID for CLI) obtained from the CSI reporting configuration. Alternatively, if it is assumed that the existing CLI measurement / reporting operates event-based, event-based L1 / L2 CLI reporting may be introduced. Existing CLI is reported to the gNB through L3 signaling when it exceeds the threshold for the configured measurement resource. However, the gNB must quickly identify the CLI environment of the UE to apply CLI handling / suppression techniques to reduce the CLI experienced by the UE. Therefore, it is possible to reuse the mechanism for performing CLI measurement reporting when the CLI measurement value exceeds the threshold for the preset measurement resource, but consider performing the CLI measurement reporting through L1 / L2 signaling. In this case, in order to eliminate ambiguity in UE operation, a method for handling collisions between the CLI report of the UE and other ULs of the UE is described in detail.

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

[0274] collision rule between CLI report based on CSI framework and other UL

[0275] When considering the introduction of L1 / L2 CLI reported to UCI based on the CSI reporting framework, the simplest approach that can be considered may be to define L1 / L2 CLI as a separate report without mixing it with the existing BM / CSI. This could be done similarly to how L1-triggered mobility reporting is configured as a separate reporting configuration from BM / CSI reporting. In this case, L1 / L2 CLI could operate as a separate report from CSI reporting. Alternatively, to ensure gNB scheduling flexibility, CLI measurement resources could be indicated in the CSI reporting configuration, and new measurement metrics (e.g., L1-RSSI) could be additionally introduced.

[0276] Alternatively, L1 / L2 CLI reporting can be triggered in two main ways, separate from the above-described methods. First, there can be gNB-instructed CLI reporting, where the gNB instructs the UE to report, and event-triggered L1 / L2 CLI reporting can be newly introduced by defining a new event for L1 / L2 CLI reporting. The former can determine which CLI report will take precedence in a conflict between CLI reports (e.g., priorities are set for aperiodic, semi-persistent, and periodic reports) based on a priority rule similar to the priority of CSI reporting according to time domain settings, and lower priority CLI reports can be dropped and not transmitted. However, since event-triggered L1 / L2 CLI reporting is a newly introduced L1 / L2 CLI reporting, the UE's behavior may still be ambiguous when a conflict occurs between event-based L1 / L2 CLI reporting and gNB-instructed CLI reporting (or other UL signaling channels).

[0277] Below, we describe in detail the priority rules for resolving collisions when a UL channel of a CLI report (or a CSI report including a CLI report) collides with another UL signal (e.g., overlaps in the time domain).

[0278] 1. Proposal 1

[0279] In Proposal 1, there may be priorities for individual L1 / L2 CLI reports. In this case, if a collision occurs between CLI reports, the UE may transmit a CLI report with a higher priority and drop a CLI report with a lower priority. Here, transmitting a CLI report with a higher priority and dropping a CLI report with a lower priority means that if a high-priority CLI report and a low-priority CLI report collide, the UE performs the CLI report with the higher priority but does not perform the CLI report with the lower priority. Alternatively, if the UE can multiplex between CLI reports, the UE may multiplex the conflicting CLI reports, but drop the CLI reports in the order of lower priority if the capacity (or size) of the allocated UL channel is smaller than the payload size to be reported, so that only CLI reports corresponding to the capacity of the UL channel are multiplexed. For example, if the payload size of CLI reports is larger than the size of allocated / granted UL resources, the UE may multiplex and report only some of the CLI reports (having payloads within the size of allocated / granted UL resources) based on priority, and drop the remaining reports.

[0280] (1) Proposal 1-1

[0281] Proposal 1-1 may be a way to set priorities for CLI reports based on event-specific priorities (e.g., priorities set among trigger events of CLI reports) when event-based L1 / L2 CLI reporting is performed.

[0282] For example, if multiple events that trigger L1 / L2 CLI reporting (e.g., an event for RSRP, an event for RSSI, an event for SBFD CLI, an event for non-SBFD CLI, etc.) are configured, the gNB may instruct / configure priorities among the multiple events when configuring the multiple events to the UE. In this case, the UE may resolve conflicts between different event-triggered L1 / L2 CLI reports based on the priorities among the multiple events. Alternatively, if multiple events that trigger L1 / L2 CLI reporting (e.g., an event for RSRP, an event for RSSI, an event for SBFD CLI, an event for non-SBFD CLI, etc.) are configured, the UE may resolve conflicts between different event-triggered L1 / L2 CLI reports by using a priority rule agreed upon in advance for each event.

[0283] (2) Proposal 1-2

[0284] For Proposal 1-2, different priorities can be set between gNB instruction-based L1 / L2 CLI reporting and event-triggered L1 / L2 CLI reporting.

[0285] For example, since gNB indication-based L1 / L2 CLI reporting is a report of information to be reflected in the scheduler for the purpose of the gNB determining whether to apply a specific CLI handling scheme to the UE, it may be given a higher priority than event-triggered L1 / L2 CLI reporting. Alternatively, event-triggered L1 / L2 CLI reporting may be a report of a severe CLI environment of the UE that the gNB must quickly identify by detecting CLI exceeding a preset threshold, it may be given a higher priority than gNB indication-based L1 / L2 CLI reporting.

[0286] (3) Proposal 1-3

[0287] For Proposals 1-3, priorities may be set based on the time at which the UE performed measurements for CLI reporting. For example, since the gNB aims to receive information about L1 / L2 CLI that is not outdated, the highest priority for CLI reporting may be set / applied to the CLI report for which measurements were most recently performed from the reporting time of the CLI report (the CLI report containing the latest CLI measurement information). Alternatively, considering that the CLI report generated from measurements made at the oldest time from the reporting time of the CLI report is the most reliable CLI report, the highest priority may be set / applied to the CLI report measured at the oldest time from the reporting time.

[0288] (4) Proposal 1-4

[0289] For proposals 1-4, the priority for CLI reporting can be set based on the type of time interval in which the UE has measurement resources set for CLI reporting.

[0290] For example, if a CLI measurement resource is located in an SBFD slot (or if a CLI measurement resource for an SBFD slot exists), the result of measuring CLI in the resource has a higher priority than the CLI result measured in a measurement resource in a non-SBFD slot (or if a CLI measurement resource for a non-SBFD slot exists). Here, the SBFD slot refers to a time period in which the serving cell of the UE performs the SBFD operation, and thus, in the time period, UEs receiving DL signals within the cell and UEs transmitting UL may coexist. Therefore, intra-cell CLI is likely to occur, and even if DL and UL are actually performed in different time resources, CLI may occur due to out-of-band emission. In this respect, CLI measurement in an SBFD slot or CLI measurement / reporting in a CLI measurement resource for an SBFD slot may have a higher priority and be reported preferentially than CLI measurement in a non-SBFD slot or CLI measurement / reporting in a CLI measurement resource for a non-SBFD slot.

[0291] Alternatively, if the CLI measurement resource is located in a non-SBFD slot (or if a CLI measurement resource exists for a non-SBFD slot), the result of measuring CLI in the resource may have a higher priority than the CLI result measured in the measurement resource when the CLI measurement resource is located in the SBFD slot (or if a CLI measurement resource exists for the SBFD slot). Here, a non-SBFD slot is a time period in which the serving cell of the UE does not perform the SBFD operation, but inter-cell CLI is likely to occur when adjacent cells perform the SBFD operation or when the link direction is different (e.g., dynamic / flexible TDD). Therefore, since this is a period in which CLI that is difficult for the serving gNB to predict may occur, the UE needs to perform a quick report on the CLI environment change. Therefore, a CLI report measured in a non-SBFD slot may be reported with a higher priority than a CLI measurement in an SBFD slot or a CLI measurement / report in a CLI measurement resource for an SBFD slot.

[0292] 2. Proposal 2

[0293] For Proposal 2, the priority index can also be set to a specific value for the UL channel of CLI reporting based on the priority index introduced in Rel-16 URLLC (Ultra-Reliable Low Latency Communication).

[0294] The priority index introduced in Rel-16 URLLC is an index to give priority to URLLC TB (Transport Block) / UCI transmission over other UL TB / UCI. Such priority index is indicated by DCI in case of DG (dedicated grant) PUSCH, by RRC signal / DCI in case of CG (configured grant) PUSCH, and can be set (via RRC signal) for each PUCCH resource on which A / N is transmitted in case of A / N, and can be set (via RRC signal) for each SR resource in case of SR. Depending on the multiplexing capability of the UE, muxing between UL channels with different priority indexes can be supported, and if the UE does not have the multiplexing capability, only the UL channel with the (highest) priority index among the UL channels can be reported and the remaining UL channels can be dropped. This is defined in a given scenario (3GPP TS 38 specification) as shown in Table 7 below.

[0295] -> if this is for cases the UE supports multiplexing information of different priorities in a PUCCH / PUSCH transmission- a PUCCH transmission with HARQ-ACK information, without repetitions, with smaller priority index overlaps with a PUCCH transmission only with HARQ-ACK information, without repetitions, with larger priority index, or- a PUCCH transmission without repetitions that includes HARQ-ACK information of smaller priority index overlaps with a PUCCH transmission without repetitions using a PUCCH resource with PUCCH format 2 / 3 / 4 with HARQ-ACK information and SR of larger priority index, or- a PUCCH transmission with HARQ-ACK information, without repetitions, with smaller or larger priority index overlaps, respectively, with a PUSCH transmission with larger or smaller priority indexthe UE- multiplexes HARQ-ACK information of different priority indexes and SR information of larger priority index, if any, in a same PUCCH transmission of larger priority index, or multiplexes HARQ-ACKinformation the UE would provide in a PUCCH transmission of smaller or larger priority index in a PUSCH transmission of larger or smaller priority index, respectively, and applies the procedures in clause 9.2.5.3 or 9.3, respectively, and- drops CSI and / or SR carried in the PUCCH transmission of smaller priority index, if any- drops negative SR carried in the PUCCH transmission of larger priority index, if any, if the UE would multiplex the HARQ-ACK information of larger priority index in a PUSCH transmission of smaller priority index- drops HARQ-ACK information of smaller priority index if the UE would multiplex the HARQ-ACK information of smaller priority index in a PUSCH transmission where the UE multiplexes Part 1 CSI reports and Part 2 CSI reports of larger priority index- drops Part 2 CSI reports of smaller priority index if the UE would multiplex the HARQ-ACK information of smaller and larger priority indexes in a PUSCH transmission where the UE multiplexes Part 1 CSI reportsand Part 2 CSI reports of smaller priority index- drops HARQ-ACK information of smaller priority index if the UE would multiplex the HARQ-ACK information of smaller priority index in a PUCCH transmission of larger priority index using a PUCCH resource provided by n1PUCCH-AN- drops Part 2 CSI reports of smaller priority index if the UE would multiplex the HARQ-ACK information of larger priority index in a PUSCH transmission where the UE multiplexes CG-UCI, or UTO-UCI, Part 1 CSI reports and Part 2 CSI reports of smaller priority index-> else- if the UE would transmit the following channels that would overlap in time where, if a channel transmission is with repetitions, the following are applicable per repetition- a first PUCCH transmission of larger priority index and a second PUCCH transmission of smaller priority index- a first PUCCH transmission of larger priority index and a second PUSCH transmission of smaller priority index when the UE cannot simultaneously transmit the firstPUCCH and second PUSCH- a first PUCCH transmission of smaller priority index and a second PUSCH transmission of larger priority index when the UE cannot simultaneously transmit the first PUCCH and second PUSCHthe UE- transmits the PUCCH or the PUSCH of the larger priority index subject to the limitations for UE transmissions described in clauses 11.1, 11.1.1, 11.2A, and 15 and- does not transmit a PUCCH or a PUSCH of smaller priority index(중략)If a UE would transmit the following channels, including repetitions if any, that would overlap in time- a first PUCCH of larger priority index with SR and a second PUCCH or PUSCH of smaller priority index, or- a configured grant PUSCH of larger priority index and a PUCCH of smaller priority index, or- a first PUCCH of larger priority index with HARQ-ACK information only in response to PDSCH(s) reception without corresponding PDCCH(s) and a second PUCCH of smaller priority index with HARQ-ACK information only in response to PDSCH(s) receptionwithout corresponding PDCCH(s), or a second PUCCH of smaller priority index with SR and / or CSI, or a configured grant PUSCH with smaller priority index, or a PUSCH of smaller priority index with SP-CSI report(s) without a corresponding PDCCH, or- a PUSCH of larger priority index with SP-CSI report(s) without a corresponding PDCCH and a PUCCH of smaller priority index with SR, or CSI, or HARQ-ACK information only in response to PDSCH(s) reception without corresponding PDCCH(s), or- a configured grant PUSCH of larger priority index and a configured grant PUSCH of smaller priority index or a PUSCH of smaller priority index with SP-CSI report(s) without a corresponding PDCCH on a same serving cell- a PUSCH of larger priority index with SP-CSI report(s) without a corresponding PDCCH and a configured grant PUSCH of smaller priority index or a PUSCH of smaller priority index with SP-CSI report(s) without a corresponding PDCCH on a same serving cell- a PUSCH of smaller priority index scheduledby a DCI format and a configured grant PUSCH of larger priority index on a same serving cell if the UE is providedprioLowDG-HighCG- a PUSCH of larger priority index scheduled by a DCI format and a configured grant PUSCH of smaller priority index on a same serving cell if the UE is providedprioHighDG-LowCGthe UE is expected to cancel a repetition of the PUCCH / PUSCH transmissions of smaller priority index before the first symbol overlapping with the PUCCH / PUSCH transmission of larger priority index if the repetition of the PUCCH / PUSCH transmissions of smaller priority index overlaps in time with the PUCCH / PUSCH transmissions of larger priority index.

[0296] The UE can set the priority index for the UL channel of the CLI report to a specific value based on the priority index defined as in Table 7. Here, based on the priority index can mean that muxing between UL channels of different priority indices is supported according to the multiplexing capability of the UE with respect to the indication of the existing priority index, or else it follows the UE behavior of reporting only the UL channel of the (highest) priority index and dropping the rest.

[0297] For example, the UE may determine / assume that the CLI report is given the highest priority (priority index = 1 or 0) even if no priority index is set for the CLI report. This may be because the UE-to-UE CLI measurement value can be determined by the gNB (which the gNB cannot directly predict) based on the reception of the UE's measurement report, and the importance of L1 / L2 CLI, which was introduced for the purpose of allowing the gNB to quickly identify the CLI environment of the UE. Alternatively, the UE may determine that the CLI report is given a medium priority (priority index = 0.5) even if no priority index is set. Although the CLI report is less important than URLLC, it may be information that is set to a higher priority than other UL channels that do not have a priority index set so that the gNB can quickly identify the CLI environment of the UE. Therefore, it may be appropriate to set a medium priority for the CLI report. Alternatively, the UE may determine that the CLI report is set to the lowest priority (priority index = -1) even if no priority index is set. This is because the CLI report is not information related to data transmission, and the existing CSI report via the Interference Measurement Resource (IMR) contains some interference information due to the CLI.

[0298] 3. Proposal 3

[0299] In Proposal 3, when L1 / L2 CLI reporting is introduced, the power allocation priority rules defined in Rel-16 CA (Carrier Aggregation) can be applied between CLI reporting and existing CSI reporting.

[0300] As shown in Table 8 below, the NR Rel-16 standard can allocate power in a priority manner starting from the UL channel of a carrier with a higher priority among multiple carriers by applying power allocation priorities to a CA environment. For example, when uplink signals are transmitted through multiple carriers in a specific transmission opportunity, if the sum of the transmission powers of the multiple uplink signals exceeds the maximum transmission power for the UE, the UE can allocate transmission power in a priority manner to a specific uplink signal among the multiple uplink signals according to the priorities defined in Table 8. For example, the UE can allocate transmission power for the multiple uplink signals within the maximum transmission power for the UE by allocating transmission power for the multiple uplink signals according to the priorities defined in Table 8. Meanwhile, the priorities for CSI reporting may be the same as those separately indicated in Table 8.

[0301] For single cell operation with two uplink carriers or for operation with carrier aggregation or for operation with a candidate cell configured byLTM-Config, if a total UE transmit power for PUSCH or PUCCH or PRACH or SRS transmissions on serving cells or on a candidate cell, if any, in a frequency range in a respective transmission occasion i would exceed , where is the linear value of P CMAX(i) in transmission occasion i as defined in [8-1, TS 38.101-1] for FR1 and [8-2, TS 38.101-2] for FR2, the UE allocates power to PUSCH / PUCCH / PRACH / SRS transmissions according to the following priority order (in descending order) so that the total UE transmit power for transmissions on serving cells or on a candidate cell, if any, in the frequency range is smaller than or equal to for that frequency range in every symbol of transmission occasion i. If the UE transmits SRS on multiple SRS resources according theXYZ[6, TS 38.214], the UE allocates power so that all REs of the SRS transmission have same power.For the purpose of power allocation in this clause, if a UE is provideduci-MuxWithDiffPrioand the UE multiplexes HARQ-ACK information in a PUSCH, a priority index of the PUSCH is the larger of (a) the priority index of the PUSCH according to clause 9 and (b) the larger priority index of the HARQ-ACK information. When determining a total transmit power for serving cells or a candidate cell, if any, as described in Clause 21 in a frequency range in a symbol of transmission occasion i, the UE does not include power for transmissions starting after the symbol of transmission occasion i. The total UE transmit power in a symbol of a slot is defined as the sum of the linear values of UE transmit powers for PUSCH, PUCCH, PRACH,and SRS in the symbol of the slot.-> PRACH transmission on a candidate cell, if any, as described in Clause 21-> PRACH transmission on the PCell-> PUCCH or PUSCH transmissions with larger priority index-> For PUCCH or PUSCH transmissions with same priority index-- PUCCH transmission with HARQ-ACK information, and / or SR, and / or LRR, or PUSCH transmission with HARQ-ACK information of the priority index-- PUCCH transmission with CSI or PUSCH transmission with CSI-- PUSCH transmission without HARQ-ACK information of the priority index or CSI and, for Type-2 random access procedure, PUSCH transmission on the PCell-> If the UE is configured with prioSCellPRACH-OverSP-PeriodicSRS-r17-- Aperiodic SRS transmission or PRACH transmission on a serving cell other than the PCell-- Semi-persistent and / or periodic SRS transmission-> otherwise,- SRS transmission, with aperiodic SRS having higher priority than semi-persistent and / or periodic SRS,or PRACH transmission on a serving cell other than the PCell,

[0302] In the following, when UE initiated beam reporting (or L1 / L2 CLI reporting) is introduced, a higher priority (or lower priority) can be set for UE initiated beam reporting (or L1 / L2 CLI reporting) than for existing CSI reporting.

[0303] When L1 / L2-based CLI reporting is introduced, a higher priority may be set for L1 / L2-based CLI reporting compared to existing CSI reporting. For example, the priorities defined in the existing scenario (`3GPP TS 38 specification) may be changed as follows:

[0304] -> For PUCCH or PUSCH transmissions with same priority index

[0305] - PUCCH transmission with HARQ-ACK information, and / or SR, and / or LRR, or PUSCH transmission with HARQ-ACK information of the priority index

[0306] - PUCCH or PUSCH transmission with CLI reporting

[0307] - PUCCH transmission with CSI or PUSCH transmission with CSI

[0308] - PUSCH transmission without HARQ-ACK information of the priority index or CSI and, for Type-2 random access procedure, PUSCH transmission on the PCell

[0309] The CLI environment is something that the UE experiences and cannot be directly detected by the gNB. For example, since the subject of measuring the CLI environment is the UE, the gNB can only detect the CLI environment of the UE through reports from the UE. Therefore, in order for the gNB to (prioritizely) determine the CLI environment of the UE, the CLI report must be reported to the gNB with priority over the CSI report. Furthermore, in order for the gNB to recognize changes in the CLI environment and apply the CLI suppression technique in a timely manner, the CLI report must be reported to the gNB promptly. Therefore, the UE may report the CLI report with priority over the CSI report. Alternatively, "PUCCH or PUSCH transmission with CLI reporting" may be determined to have the same priority as or higher priority than "PUCCH transmission with HARQ-ACK information, and / or SR, and / or LRR, or PUSCH transmission with HARQ-ACK information of the priority index."

[0310] Alternatively, a lower priority may be set for L1 / L2-based CLI reporting compared to existing CSI reporting. In this case, for example, the priorities defined in the existing scenario (`3GPP TS 38 specification) may be changed as follows:

[0311] -> For PUCCH or PUSCH transmissions with same priority index

[0312] - PUCCH transmission with HARQ-ACK information, and / or SR, and / or LRR, or PUSCH transmission with HARQ-ACK information of the priority index

[0313] - PUCCH transmission with CSI or PUSCH transmission with CSI

[0314] -PUCCH or PUSCH transmission with CLI reporting

[0315] - PUSCH transmission without HARQ-ACK information of the priority index or CSI and, for Type-2 random access procedure, PUSCH transmission on the PCell

[0316] Because CSI reporting includes interference measurements as well as channel measurements for data transmission, CSI reporting can include more comprehensive channel environment information than CLI reporting and can directly impact data transmission performance. Therefore, CSI reporting may be reported with priority over CLI reporting. Alternatively, "PUCCH or PUSCH transmission with CLI reporting" may be set to the same priority as or lower than "PUSCH transmission without HARQ-ACK information of the priority index or CSI and, for Type-2 random access procedures, PUSCH transmission on the PCell."

[0317] FIG. 13 is a diagram illustrating a method for a UE to allocate transmission power among uplink signals transmitted on multiple carriers.

[0318] As described above, L1 / L2 CLI reporting may be introduced instead of L3 CLI reporting in relation to CLI reporting. In this case, L1 / L2 CLI reporting may be performed based on the existing L1 / L2 CSI reporting framework, and uplink signals for CLI reporting and uplink signals for CSI reporting may be transmitted simultaneously in a CA communication environment. At this time, as described in Proposal 3, transmission power may be preferentially allocated to a specific uplink signal among the uplink signal for CLI reporting and the uplink signal for CSI reporting according to an additionally defined priority rule between the uplink signal for CLI reporting and the uplink signal for CSI reporting. Hereinafter, a method for allocating transmission power according to a priority rule between the UL signal for CLI reporting and the UL signal for other reports will be described in detail. Meanwhile, the methods proposed in Proposals 1, 2, and 3 described above may be naturally applied even if not explicitly described in the contents described below.

[0319] Additionally, it is assumed below that the UE can simultaneously transmit uplink signals based on multiple carriers (e.g., perform CA communication). For example, the UE may be a UE that performs CA (Carrier Aggregation) communication based on a first carrier and a second carrier.

[0320] Referring to FIG. 13, the UE can perform a first measurement on a first measurement resource and a second measurement on a second measurement resource (S131). As described above, the UE can configure / allocate measurement resources for CLI measurement and measurement resources for CSI measurement through CSI resource configuration information. For example, the UE can receive the CSI resource configuration information for configuring the measurement resource(s) for the CLI measurement and the measurement resource(s) for the CSI measurement from the base station. Alternatively, when the UE performs CA communication using a first carrier and a second carrier, the UE can configure / allocate first measurement resources on the first carrier and configure / allocate second measurement resources on the second carrier. Hereinafter, for convenience of explanation, the first measurement resource is defined as a measurement resource configured / allocated for the first carrier, and the second measurement resource is defined as a measurement resource configured / allocated for the second carrier.

[0321] Next, the UE may preferentially allocate transmission power to one of the first uplink signal and the second uplink signal (S133). Specifically, the UE may simultaneously transmit a first uplink signal including the first measurement (or a first measurement report including measurement information measured on the first measurement resource) and a second uplink signal including the second measurement (or a second measurement report including measurement information measured on the second measurement resource) in a first transmission opportunity. For example, the UE may simultaneously transmit a first uplink signal on the first carrier and a second uplink signal on the second carrier in the first transmission opportunity. At this time, a first transmission power may be determined for the first uplink signal, a second transmission power may be determined for the second uplink signal, and a sum of the first transmission power and the second transmission power (or a total transmission power for the first transmission opportunity) may exceed a maximum transmission power set for the UE. In this case, the UE may allocate transmission power to one of the first uplink signal and the second uplink signal with priority based on the priority rules defined in Proposal 3 and Table 8, and allocate the remaining transmission power to the other uplink signal so that the total transmission power for the first transmission opportunity is within the maximum transmission power.

[0322] For example, if the priority indices (e.g., indices for determining priorities related to transmission power allocation in CA) between the first uplink signal and the second uplink signal are the same as defined in Table 8, the UE may additionally consider the report type of the measurement included in each of the first uplink signal and the second uplink signal to determine the uplink signal to which the transmission power is to be allocated with priority. Here, the report type of the measurement may include a CLI report type and a CSI report type. Meanwhile, if the priority indices between the first uplink signal and the second uplink signal are different, the uplink signal to which the transmission power is to be allocated with priority among the first uplink signal and the second uplink signal may be determined based on the priority indices without considering the report type of the measurement. Hereinafter, a description will be given on the assumption that the priority indices between the first uplink signal and the second uplink signal are the same.

[0323] For example, as described in Proposal 3, the CLI report may be given a higher priority than the CSI report. In this case, if the first measurement is a measurement for CSI reporting and the second measurement is a measurement for CLI reporting, the UE may preferentially allocate transmission power to the second uplink signal and allocate the remaining transmission power to the first uplink signal. Alternatively, the CLI report may be given a lower priority than the CSI report. In this case, if the first measurement is a measurement for CSI reporting and the second measurement is a measurement for CLI reporting, the UE may preferentially allocate transmission power to the first uplink signal and allocate the remaining transmission power to the second uplink signal.

[0324] Alternatively, the second measurement resource may include a first CLI measurement resource and a second CLI measurement resource. In this case, the UE may perform measurements on each of the first CLI measurement resource and the second CLI measurement resource to obtain the first CLI measurement and the second CLI measurement, and a report on the first CLI measurement and a report on the second CLI measurement may collide in the same time resource. In this case, the UE may transmit one of the first CLI measurement and the second CLI measurement via the second uplink signal based on a predetermined priority, and drop the remaining CLI measurements. For example, as described in Proposal 1, the UE may determine a priority among multiple CLI measurements based on whether a CLI measurement resource is allocated within an SBFD slot / SBFD time interval. For example, if a first CLI measurement resource is allocated within an SBFD slot and a second CLI measurement resource is allocated within a non-SBFD slot, the UE may determine that the first CLI measurement for the first CLI measurement resource has a higher priority than the second CLI measurement, and may transmit the first CLI measurement with priority over the second uplink signal. Alternatively, the UE may determine a priority among multiple CLI measurements based on whether the CLI measurement is measured based on an instruction of a gNB or based on an event trigger. For example, if the first CLI measurement is an event trigger-based measurement and the second CLI measurement is a measurement based on an instruction of a base station, the UE may transmit the first CLI measurement with priority over the second CLI measurement over the first uplink signal.

[0325] Next, the UE can transmit the first uplink signal and the second uplink signal to which the transmission power is allocated in the first transmission opportunity (S135). As described above, the first uplink signal can be transmitted through the first carrier, and the second uplink signal can be transmitted through the second carrier.

[0326] In this way, the proposed invention can effectively apply a transmission power allocation method according to priority rules in CA communication between an uplink signal including an L1 CLI report and an uplink signal including a CSI report. Alternatively, the proposed invention can effectively perform L1 CLI reporting using a CSI framework by clearly defining the priority between L1 CLI reports and CSI reports, and can effectively resolve ambiguity in UE operations for L1 CLI reports and L1 CSI reports. Alternatively, the proposed invention can clearly determine which L1 CLI report to transmit through an uplink signal among L1 CLI reports in the event of a conflict between L1 CLI reports.

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

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

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

[0330] Figure 14 illustrates a communication system applied to the present invention.

[0331] Referring to FIG. 14, 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.

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

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

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

[0335] Figure 15 illustrates a wireless device applicable to the present invention.

[0336] Referring to FIG. 15, 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. 14.

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

[0338] According to one example, the first wireless device or UE (100) 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 Proposals 1 to 3.

[0339] Specifically, the processor (102) controls the RF transceiver (106) to perform a first measurement for a first measurement resource and a second measurement for a second measurement resource, and, based on a total transmit power of a first transmission opportunity for a first uplink signal including the first measurement and a second uplink signal including the second measurement exceeding a maximum transmit power of the UE, preferentially allocates transmit power to one of the first uplink signal and the second uplink signal, and transmits the first uplink signal and the second uplink signal, wherein the one uplink signal can be determined based on a report type of the measurement.

[0340] Alternatively, a processing device may be configured including a processor (102) and a memory (104). In this case, the processing device may include at least one processor; and at least one memory coupled 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: perform a first measurement for a first measurement resource and a second measurement for a second measurement resource, and, based on a total transmit power of a first transmission opportunity for a first uplink signal including the first measurement and a second uplink signal including the second measurement exceeding a maximum transmit power of the UE, preferentially allocate transmit power to one of the first uplink signal and the second uplink signal, and transmit the first uplink signal and the second uplink signal. Here, the one uplink signal may be determined based on a report type of the measurement.

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

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

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

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

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

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

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

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

[0349] Referring to FIG. 16, the wireless device (100, 200) corresponds to the wireless device (100, 200) of FIG. 15 and may be composed of various elements, components, 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. 16. For example, the transceiver(s) (114) may include one or more transceivers (106, 206) and / or one or more antennas (108, 208) of FIG. 15. 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).

[0350] 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. 14, 100a), a vehicle (Fig. 14, 100b-1, 100b-2), an XR device (Fig. 14, 100c), a portable device (Fig. 14, 100d), a home appliance (Fig. 14, 100e), an IoT device (Fig. 14, 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. 14, 400), a base station (Fig. 14, 200), a network node, etc. Wireless devices may be mobile or stationary depending on the use / service.

[0351] In FIG. 16, 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 one or more processor sets. 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.

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

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

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

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

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

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

[0358] 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 performing a first measurement on a first measurement resource and a second measurement on a second measurement resource; A step of preferentially allocating transmission power to one of the first uplink signal and the second uplink signal based on the total transmission power of the first transmission opportunity for the first uplink signal including the first measurement and the second uplink signal including the second measurement exceeding the maximum transmission power of the UE; and A step of transmitting the first uplink signal and the second uplink signal; A method wherein the above one uplink signal is determined based on the reporting type of the measurement.

2. In paragraph 1, A method characterized in that the one uplink signal is the second uplink signal, based on (i) the first measurement being a measurement for CSI (channel state information) reporting and (ii) the second measurement being a measurement for CLI (Cross Link Interference) reporting.

3. In paragraph 1 A method characterized in that the one uplink signal is the first uplink signal, based on (i) the first measurement being a measurement for CSI (channel state information) reporting and (ii) the second measurement being a measurement for CLI (Cross Link Interference) reporting.

4. In paragraph 1, A method characterized in that the one uplink signal is determined based on the type of the measurement, based on the first uplink signal having the same priority index as the priority index of the second uplink signal.

5. In paragraph 1, A step of receiving setting information for a first time interval related to SBFD (Sub-Band Full-Duplex); further comprising; A method characterized in that, based on the second measurement including a plurality of CLI measurements, the UE determines a priority among the plurality of CLI measurements based on whether the CLI measurements are measured on a measurement resource within the first time interval.

6. In paragraph 5, A method, characterized in that among the plurality of CLI measurements, a CLI measurement measured in a measurement resource within the first time interval has a higher priority than a CLI measurement measured in a measurement resource within a second time interval that is not related to the SBFD.

7. In paragraph 1, A method characterized in that, based on the second measurement including a plurality of CLI measurements, the UE determines a priority among the plurality of CLI measurements based on whether the CLI measurements are event-triggered.

8. In paragraph 1, The above UE performs CA (Carrier Aggregation) communication based on the first carrier and the second carrier, A method, characterized in that the first uplink signal is transmitted through the first carrier, and the second uplink signal is transmitted through the second carrier.

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 perform a first measurement for a first measurement resource and a second measurement for a second measurement resource, and, based on a total transmission power of a first transmission opportunity for a first uplink signal including the first measurement and a second uplink signal including the second measurement exceeding a maximum transmission power of the UE, preferentially allocates transmission power to one of the first uplink signal and the second uplink signal, and transmits the first uplink signal and the second uplink signal. The above one uplink signal is determined based on the reporting type of the measurement, UE.

11. In paragraph 10, A UE characterized in that the one uplink signal is the second uplink signal, based on (i) the first measurement being a measurement for CSI reporting and (ii) the second measurement being a measurement for CLI (Cross Link Interference) reporting.

12. In paragraph 10, A UE characterized in that the one uplink signal is the first uplink signal, based on (i) the first measurement being a measurement for CSI reporting and (ii) the second measurement being a measurement for CLI (Cross Link Interference) reporting.

13. In paragraph 10, A UE characterized in that the one uplink signal is determined based on the type of the measurement, based on the first uplink signal having the same priority index as the priority index of the second uplink signal.

14. In paragraph 10, A UE characterized in that the one uplink signal is determined based on the type of the measurement, based on the first uplink signal having the same priority index as the priority index of the second uplink signal.

15. 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: Performing a first measurement for a first measurement resource and a second measurement for a second measurement resource, and allocating transmission power preferentially to one of the first uplink signal and the second uplink signal based on the total transmission power of a first transmission opportunity for a first uplink signal including the first measurement and a second uplink signal including the second measurement exceeding a maximum transmission power of the UE, and transmitting the first uplink signal and the second uplink signal, A processing device wherein the above one uplink signal is determined based on the reporting type of the measurement.

Images