Method and device for performing communication in wireless communication system

Abstract

Disclosed are a method and a device for performing communication in a wireless communication system according to various embodiments. Disclosed is a device for receiving muting configuration information for configuration of at least one muting resource, receiving downlink control information (DCI), and transmitting an uplink signal on the basis of the muting configuration information and the DCI.

Description

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

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

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

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

[0004] The technical challenge is to provide a method for terminals to transmit and receive signals more accurately and efficiently.

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

[0006] A method by a UE (User Equipment) according to one aspect includes the steps of: receiving muting configuration information for setting at least one muting resource; receiving downlink control information (DCI); and transmitting an uplink signal based on the muting configuration information and the DCI; wherein the DCI can indicate a first muting resource to be applied to the uplink signal among the at least one muting resource through a TDRA (Time domain resource allocation) field.

[0007] Alternatively, the TDRA field includes information about a time resource associated with a first muting resource among a plurality of time resources allocated to the uplink signal, and the first muting resource is characterized in that it is a frequency resource having an even index or a frequency resource having an odd index among frequency resources allocated to the time resource associated with the first muting resource.

[0008] Alternatively, based on the first muting resource overlapping with a resource for a DMRS (Demodulation Reference Signal) of the uplink signal, the first muting resource is not applied to the uplink signal.

[0009] Alternatively, the UE is characterized in that it determines that the first muting resource overlapping with the resource for the DMRS (Demodulation Reference Signal) of the uplink signal is invalid.

[0010] Alternatively, based on the first muting resource overlapping with a resource for multiplexing of UCI (Uplink control information) of the uplink signal, the first muting resource is characterized in that it is not applied to the uplink signal.

[0011] Alternatively, the UE is characterized in that it multiplexes Uplink Control Information (UCI) to the uplink signal based on the number of resources allocated for the uplink signal minus the number of the first muting resources.

[0012] Alternatively, the method further comprises a step of scheduling repetitive transmission of a plurality of uplink signals related to DMRS (Demodulation Reference Signal) bundling.

[0013] Alternatively, the first uplink signal is characterized in that it is transmitted by including only DMRS based on the number of symbols remaining, excluding symbols of the first muting resource, in the first uplink signal to which the first muting resource is applied among the plurality of uplink signals being equal to or less than a preset number.

[0014] Alternatively, the method further includes receiving configuration information for a first time interval related to a sub-band full duplex (SBFD) or single frequency full duplex (SFFD) operation of a base station, wherein the first muting resource is valid only within the first time interval.

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

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

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

[0018] A method by a base station according to another aspect includes the steps of: transmitting muting configuration information for setting at least one muting resource among uplink resources; transmitting downlink control information (DCI); and receiving an uplink signal based on the muting configuration information and the DCI; wherein the DCI can indicate a first muting resource to be applied to the uplink signal among the at least one muting resource through a TDRA (Time domain resource allocation) field.

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

[0020] Various embodiments enable the terminal to transmit and receive signals accurately and efficiently.

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

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

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

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

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

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

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

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

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

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

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

[0032] Figures 11 to 13 are drawings for explaining a method of setting muting resources related to UL muting.

[0033] FIG. 14 is a diagram illustrating a method for a UE to apply muting resources in transmission of an uplink signal.

[0034] Figure 15 is a diagram illustrating a method for a base station to instruct a UE on muting resources.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0068] Bandwidth part (BWP)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0098] CSI-related actions

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0116] QCL (quasi-co location)

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

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

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

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

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

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

[0123] Beam Management (BM)

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

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

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

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

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

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

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

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

[0132] DMRS bundling

[0133] As defined in a given scenario (Rel-17), the gNB can instruct / configure the UE a time domain window (TDW) associated with received DMRS bundling. In this case, the UE can transmit DMRS bundled uplink signals based on the TDW. Specific operations related to this are detailed in Tables 5 to 8 below (see section 6.1.7 of TS 38.214).

[0134] DMRS bundling

[0135] As defined in a given scenario (Rel-17), the gNB can instruct / configure the UE a time domain window (TDW) associated with received DMRS bundling. In this case, the UE can transmit DMRS bundled uplink signals based on the TDW. Specific operations related to this are detailed in Tables 5 to 8 below (see section 6.1.7 of TS 38.214).

[0136] For PUSCH transmissions of PUSCH repetition Type A scheduled by DCI format 0_1 or 0_2, PUSCH repetition Type A with a configured grant, PUSCH repetition Type B and TB processing over multiple slots, whenPUSCH-DMRS-Bundlingis enabled, and for PUCCH transmissions of PUCCH repetition, whenPUCCH-DMRS-Bundlingis enabled, the UE determines one or multiple nominal TDWs, as follows:- For PUSCH transmissions of repetition Type A, PUSCH repetition Type B and TB processing over multiple slots, the duration of each nominal TDW except the last nominal TDW, in number of consecutive slots, is:- Given by PUSCH-TimeDomainWindowLength, if configured.- Computed as min ([maxDMRS-BundlingDuration], M), if PUSCH-TimeDomainWindowLength is not configured, where M is the time duration in consecutive slots of N*K PUSCH transmissions, and where:- For PUSCH transmissions of PUSCH repetition Type A, N=1 and K is the number of repetitions, as defined in Clause 6.1.2.1.- For PUSCH transmissions of PUSCH repetition Type B, N=1 and K is the number of nominal repetitions, as defined in Clause 6.1.2.1.- For PUSCH transmissions of TB processing over multiple slots, N is the number of slots used for TBS determination and K is the number of repetitions of the number of slots N used for TBS determination, as defined in Clause 6.1.2.1.- For PUCCH transmissions of PUCCH repetition, the duration of each nominal TDW except the last nominal TDW, in number of consecutive slots, is:- Given by PUCCH-TimeDomainWindowLength, if configured.- Computed as min ([maxDMRS-BundlingDuration], M), if PUCCH-TimeDomainWindowLength is not configured, where M is the time duration in consecutive slots from the first slot determined for PUCCH transmissions of PUCCH repetition to the last slot determined for PUCCH transmissions of PUCCH repetition according to clause 9.2.6 of [6, TS 38.213].- For PUSCH transmission of a PUSCH repetition Type A scheduled by DCI format 0_1 or 0_2 and PUSCH repetition Type A with a configured grant, whenAvailableSlotCountingis enabled, and for TB processing over multiple slots:- The start of the first nominal TDW is the first slot determined for the first PUSCH transmission.- The end of the last nominal TDW is the last slot determined for the last PUSCH transmission.- The start of any other nominal TDWs is the first slot determined for PUSCH transmission after the last slot determined for PUSCH transmission of a previous nominal TDW.- For PUSCH transmissions of a PUSCH repetition type A scheduled by DCI format 0_1 or 0_2 and PUSCH repetition Type A with a configured grant, when the UE is not configured withAvailableSlotCountingor whenAvailableSlotCountingis disabled, and for PUSCH repetition type B:- The start of the first nominal TDW is the first slot for the first PUSCH transmission.- The end of the last nominal TDW is the last slot for the last PUSCH transmission.- The start of any other nominal TDWs is the first slot after the last slot of a previous nominal TDW.- For PUCCH transmissions of a PUCCH repetition:- The start of the first nominal TDW is the first slot determined for the first PUCCH transmission.- The end of the last nominal TDW is the last slot determined for the last PUCCH transmission.- The start of any other nominal TDWs is the first slot determined for PUCCH transmission after the last slot determined for PUCCH transmission of a previous nominal TDW.

[0137] For PUSCH transmissions of a PUSCH repetition Type A scheduled by DCI format 0_1 or 0_2, PUSCH repetition Type A with a configured grant, PUSCH repetition Type B and TB processing over multiple slots, a nominal TDW consists of one or multiple actual TDWs. The UE determines the actual TDWs as follows:- The start of the first actual TDW is the first symbol of the first PUSCH transmission in a slot for PUSCH transmission of PUSCH repetition type A scheduled by DCI format 0_1 or 0_2, or PUSCH repetition Type A with a configured grant, or PUSCH repetition type B or TB processing over multiple slots within the nominal TDW.- The end of an actual TDW is- The last symbol of the last PUSCH transmission in a slot for PUSCH transmission of PUSCH repetition type A scheduled by DCI format 0_1 or 0_2, or PUSCH repetition Type A with a configured grant, or PUSCH repetition type B or TB processing over multiple slots within the nominal TDW, if the actual TDW reaches the end of the last PUSCH transmission within the nominal TDW.- The last symbol of a PUSCH transmission before the event, if an event occurs which causes power consistency and phase continuity not to be maintained across PUSCH transmissions of PUSCH repetition type A scheduled by DCI format 0_1 or 0_2, or PUSCH repetition Type A with a configured grant, or PUSCH repetition type B or TB processing over multiple slots within the nominal TDW, and the PUSCH transmission is in a slot for PUSCH transmission of PUSCH repetition type A scheduled by DCI format 0_1 or 0_2, or PUSCH repetition Type A wth a configured grant, or PUSCH repetition type B or TB processing over multiple slots.- WhenPUSCH-Window-Restartis enabled, the start of a new actual TDW is the first symbol of the PUSCH transmission after the event which causes power consistency and phase continuity not to be maintained across PUSCH transmissions of PUSCH repetition type A scheduled by DCI format 0_1 or 0_2, or PUSCH repetition Type A with a configured grant, or PUSCH repetition type B or TB processing over multiple slots within the nominal TDW, and the PUSCH transmission is in a slot for PUSCH transmission of PUSCH repetition type A scheduled by DCI format 0_1 or 0_2, or PUSCH repetition Type A with a configured grant, or PUSCH repetition type B or TB processing over multiple slots.

[0138] For PUCCH transmissions of PUCCH repetition, a nominal TDW consists of one or multiple actual TDWs. The UE determines the actual TDWs as follows:- The start of the first actual TDW is the first symbol of the first PUCCH transmission in a slot determined for PUCCH tranmission within the nominal TDW.- The end of an actual TDW is- The last symbol of the last PUCCH transmission in a slot determined for transmission of the PUCCH within the nominal TDW, if the actual TDW reaches the end of the last PUCCH transmission within the nominal TDW.- The last symbol of a PUCCH transmission before the event, if an event occurs which causes power consistency and phase continuity not be maintained across PUCCH transmissions of PUCCH repetition within the nominal TDW, and the PUCCH transmission is in a slot determined for transmission of the PUCCH.- WhenPUCCH-Window-Restartis enabled, the start of a new actual TDW is the first symbol of the PUCCH transmission after the event which causes power consistency and phase continuity not to be maintained across PUCCH transmissions of PUCCH repetition within the nominal TDW, and the PUCCH transmission is in a slot determined for transmission of the PUCCH.

[0139] Events which cause power consistency and phase continuity not to be maintained across PUSCH transmissions of PUSCH repetition type A scheduled by DCI format 0_1 or 0_2, or PUSCH repetition Type A with a configured grant, or PUSCH repetition type B or TB processing over multiple slots, or PUCCH transmissions of PUCCH repetition, within the nominal TDW, are:- A downlink slot or downlink reception or downlink monitoring based ontdd-UL-DL-ConfigurationCommonand tdd-UL-DL-ConfigurationDedicated for unpaired spectrum.- The gap between any two consecutive PUSCH transmissions, or the gap between any two consecutive PUCCH transmissions, exceeds 13 symbols for normal cyclic prefix or exceeds 11 symbols for extended cyclic prefix.- The gap between any two consecutive PUSCH transmissions, or the gap between any two consecutive PUCCH transmissions, does not exceed 13 symbols but other uplink transmissions are scheduled between the two consecutive PUSCH transmissions or the two consecutive PUCCH transmissions.- For PUSCH transmissions of PUSCH repetition type A, or PUSCH repetition type B or TB processing over multiple slots, a dropping or cancellation of a PUSCH transmission according to clause 9, clause 11.1 and clause 11.2A of [6, TS 38.213].- For PUCCH transmissions of PUCCH repetition, a dropping or cancellation of a PUCCH transmission according to clause 9, clause 9.2.6 and clause 11.1 of [6, TS 38.213].- For any two consecutive PUSCH transmissions of PUSCH repetition type A, or PUSCH repetition type B, and when two SRS resource sets are configured insrs-ResourceSetToAddModListorsrs-ResourceSetToAddModListDCI-0-2with higher layer parameterusageinSRS-ResourceSetset to 'codebook' or 'noncodebook', a different SRS resource set association is used for the two PUSCH transmissions of PUSCH repetition type A, or PUSCH repetition type B, according to Clause 6.1.2.1.- For any two consecutive PUCCH transmissions of PUCCH repetition, and when a PUCCH resource used for repetitions of a PUCCH transmission by a UE includes first and second spatial relations or first and second sets of power control parameters, as described in [10, TS 38.321] and in clause 7.2.1 of [6, TS 38.213], different spatial relations or different power control parameters are used for the two PUCCH transmissions of PUCCH repetition, according to Clause 9.2.6 of [6, TS 38.213].- Uplink timing adjustment in response to a timing advance command according to clause 4.2 of [6, TS 38.213].- Frequency hopping.- For reduced capability half-duplex UEs,- a dropping or cancellation of a PUSCH transmission according to clause 17.2 of [6, TS 38.213] or- an overlapping of the gap between two consecutive PUSCH transmissions and any symbol of downlink reception or downlink monitoringThe UE shall maintain power consistency and phase continuity within an actual TDW, across PUSCH transmissions of PUSCH repetition Type A scheduled by DCI format 0_1 or 0_2, or PUSCH repetition Type A with a configured grant, or PUSCH repetition type B or TB processing over multiple slots, or across PUCCH transmissions of PUCCH repetition, in case the actual TDW is created in response to frequency hopping, or in response to the use of a different SRS resource set association for the two PUSCH transmissions of PUSCH repetition type A, or PUSCH repetition type B, or in response to the use of different spatial relations or different power control parameters for the two PUCCH transmissions of PUCCH repetition, or in response to any event not triggered by DCI or MAC-CE.The UE maintains power consistency and phase continuity within an actual TDW, across PUSCH transmissions of PUSCH repetition Type A scheduled by DCI format 0_1 or 0_2, or PUSCH repetition Type A with a configured grant, or PUSCH repetition type B or TB processing over multiple slots, or across PUCCH transmissions of PUCCH repetition, in case the actual TDW is created in response to an event triggered by DCI other than frequency hopping or by MAC-CE, subject to UE capability.

[0140] As described in Tables 5 to 8, as an indication method related to the current DMRS bundling, the gNB can indicate to the UE a TDW to be set when PUSCH / PUCCH repetition is performed within a maximum duration included in the capability or capability information reported by the UE. The indicated / set TDW can be repeated if the number of repetitions is smaller than the number of repetitions, and the actual TDW can start with the start of the set TDW. Within the actual TDW, the UE can start transmitting an uplink signal (PUSCH / PUCCH) while maintaining power consistency and phase continuity. If an event occurs, such as when power consistency and phase continuity cannot be maintained, the actual TDW can be terminated, and a new actual TDW can be started after the event depending on the capability of the UE. In addition, the actual TDW is terminated with the termination of the set TDW.

[0141] Full duplex operation for NR

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

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

[0144] 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 a subband-wise full duplex (SB-FD) method (e.g., SBFD method) illustrated in Fig. 8 (a) and a spectrum-sharing full duplex (SS-FD) method (e.g., SSFD method) illustrated in Fig. 8 (b).

[0145] 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. For example, DL and UL can be assigned the same or overlapping frequency resources for the same time resource.

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

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

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

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

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

[0151] 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 (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 (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 it transmits and receives at the same time, while in all cases, it is assumed that the gNB transmits and receives at the same time.

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

[0153] First, SBFD can be considered as shown in Figs. 9 (a) and 10 (a). Specifically, referring to Fig. 9 (a), 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. Alternatively, referring to Fig. 10 (a), a subband region of a DL and a subband region of an UL may not overlap with 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 a slot configuration).

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

[0155] When considering the FDR operation of the gNB in ​​both SBFD and SFFD, Self-interference (SI) may be the most essential factor to consider. The transmit power of the base station is relatively higher than the transmit power of the UE. Therefore, from the receiving perspective of the gNB performing FDR, the power level of the SI is likely to be higher than the received power level of the signal transmitted by the UE. In this regard, the introduction of a high level of SI suppression may be essential. Meanwhile, interference may occur not only when the gNB transmits and receives DL and UL at the same time and frequency, but also when the frequency gap between the UL and DL is not sufficient even when the gNB uses different frequencies for DL ​​and UL at the same time. SI suppression methods need to be applied in both of the above-mentioned cases.

[0156] Hereinafter, a case in which a UE transmits in a Full Duplex Radio (FDR) scenario of a base station (e.g., a scenario in which a gNB transmits and receives in the same time slot) may be considered. The FDR operation of the gNB includes both cases in which the transmit and receive frequencies are the same or different, and may be a case in which transmission and reception are performed simultaneously in the same time / slot. When the gNB transmits and receives simultaneously (e.g., when performing FDR operation), an operation to remove SI (Self-Interference) may be required at the receiver end. Receiver technologies that enable this include Successive Interference Cancellation (SIC). Meanwhile, a method may be considered in which the UE transmits power during the FDR period compared to the time resources when the gNB does not perform FDR in order to address limitations of receiver technologies or to improve reception sensitivity of a base station performing FDR. In this context, inter-gNB Cross-Layer Interference (CLI) may occur due to a gNB performing SBFD operation or the presence of a gNB performing SBFD operation within the network. In this case, the gNB can perform inter-gNB channel measurement or interference measurement for the purpose of reducing the degradation of reception performance from the UE due to CLI, and perform CLI handling based on the measured channel or interference. At that time, the gNB needs to instruct the UE not to perform transmission on a specific resource for the purpose of inter-gNB CLI or channel measurement. Hereinafter, a method for instructing the UE not to perform uplink transmission on a specific resource (e.g., a muting resource or muting pattern) for the purpose of inter-gNB CLI or channel measurement is proposed.

[0157] Meanwhile, there are two ways to handle inter-gNB CLI measurements at the gNB or UE, whether in a RSRP-like or RSSI-like manner. The first is to avoid CLI detected at the gNB through scheduling. The second is to consider applying an advanced receiver that utilizes measured channel information. For this purpose, the signal r(k) received from the UE to the gNB can be as follows.

[0158] [Mathematical Formula 1]

[0159]

[0160] Here, H(k) and d(k) are the channel and signal received from the serving UE, respectively, and H j (k), d j (k) are the channels and signals received from each other UE, H m (k), d m (k) represents the channel and signal of the CLI received from the gNB, respectively. At this time, the received signal from the UE restored by the gNB. Is " =w(k)r(k)", and w(k), defined according to the following mathematical expression 2, is a receiver weight matrix.

[0161] [Equation 2]

[0162]

[0163] In order to obtain the MMSE-IRC receiver weighting matrix, estimation of the covariance matrix is ​​required, and this is based on the following mathematical expression 3.

[0164] [Equation 3]

[0165]

[0166] Note that the noise ( ) represents not only the thermal noise but also includes the self-interference, co-site inter-sector gNB-to-gNB co-channel CLI. Here, the covariance matrix added due to the SBFD operation is R m There are two ways to estimate and apply this.

[0167] First, there is a method to measure the covariance matrix through RSSI-like measurements. That is, the received signal of the gNB in ​​the section where the serving UE and other UEs do not transmit is It will be, by measuring this value directly This is a method for deriving. In other words, it estimates the interference between gNBs by treating it as colored noise. This is suitable when the channel from the aggressor gNB is not time-varying and the transmission is not continuous, and it can be measured and used without distinguishing the aggressor gNB. This technique has the advantage of not increasing the gNB implementation complexity. For the convenience of the technology, according to the following mathematical expression 4 MMSE-IRC receiver based on receiver weighting matrix, w MMSE-IRC (k) is called.

[0168] [Equation 4]

[0169]

[0170] Second, the same method is used for the gNB-to-gNB channel, as in the existing MMSE, which applies MMSE-IRC using estimated channels for interference from other UEs. That is, the covariance matrix is ​​estimated by performing channel estimation between gNBs. To do this, RSRP-like measurements are performed on the inter-gNB channel to reconstruct the covariance matrix based on the transmission power of the transmitting gNB. This has the advantage of being able to adaptively apply a more accurately estimated channel to the time-varying channel between the aggressor gNB and the victim gNB. However, this assumes that the channel measurement is performed in a timely manner, and to achieve this, a channel measurement procedure between gNBs is required. This is especially true when there are multiple aggressor gNBs, where each channel must be measured separately. For the convenience of the description, the following mathematical expression is used: MMSE-IRC receiver, w based on the receiver weight matrix eMMSE-IRC (k) is called.

[0171] [Equation 5]

[0172]

[0173] Against this backdrop, to perform estimation using advanced receivers, the gNB must either measure and reconstruct inter-gNB channel information based on RSRP, or directly measure the CLI from the gNB and average it over the time axis to construct a covariance matrix. To achieve this, it is necessary to instruct the serving UE and other UEs not to transmit on the corresponding resource. Below, a method for restricting UEs from transmitting on the corresponding resource is described in detail.

[0174] UL resource muting for CLI handling

[0175] There are two possible methods for a gNB to instruct a UE not to perform UL transmission on specific resources (e.g., instructing uplink resource muting) for purposes such as inter-gNB channel measurement. The first method may be a method in which, when the gNB instructs the transmission time / frequency resources of the UE's UL signal, some of the time / frequency resources may be designated as muting resources. For example, the UE may be instructed not to transmit on resources designated as muting resources for UL signals transmitted to the UE. The second method may be a method in which a specific resource may be designated as a muting resource regardless of the UL signal / channel, and the UE behavior may be defined when the designated muting resource and the UL signal partially overlap. For example, a specific time / frequency resource may be designated as a muting resource independently of the resource designation of the UL signal / channel, and the UE may transmit the UL signal as instructed by the gNB (or according to a prior rule). In this case, the second method may be a method for defining UE behavior when there is a resource that partially overlaps with the indicated muting resource in the time / frequency resources of the above-mentioned transmitted UL signal. The first method is described in detail in Scenario 1, and the second method is described in detail in Scenario 2.

[0176] In addition, for the convenience of explanation, in the following description, at least one resource among the resources of the UL signal for which muting is indicated is defined as a muting resource, and the muting resource may also be defined as a muting pattern in the time domain and / or frequency domain.

[0177] 1. Scenario 1

[0178] In Scenario 1, the UE may be instructed by the gNB to designate specific time / frequency resources (e.g., some time / frequency resources among scheduled UL resources) as muting resources during the resource configuration phase for UL signal transmission. At this time, the UE may be instructed to designate UL resources for UL signal transmission and may be instructed to apply muting resources to some of the UL resources. In this case, the UE may apply the instructed muting resources.

[0179] The muting resource indication described below may be for the purpose of estimating the channel and / or CLI between gNBs. For example, it may be desirable to indicate that the muting resource is applied only during a (time) interval in which the inter-gNB CLI is determined to be severe or during an interval in which the inter-gNB CLI is expected to exist. In this context, the following may be considered. The UE may determine that the indicated muting resource is valid only within the time interval in which the gNB performs the SBFD operation indicated to the UE via SIB, etc. This may be an appropriate method for performing the gNB's CLI handling for the time interval in which the SBFD operation is performed. Alternatively, the UE may (separately) receive a configuration for the time interval in which the indicated muting resource is valid, separately from the gNB's indication of the muting resource. This approach can be useful when the time intervals during which SBFD operations are performed are different between the serving gNB and other gNBs (or, the serving gNB does not perform SBFD operations but other gNBs do), as it is expected that there will be a CLI between gNBs.

[0180] For channel measurement between gNBs via the (UL) muting resource described below to function properly, not only the serving UE but also other gNBs must be aware of the muting resource. This is because, while a specific gNB transmits a reference signal through the muting resource, transmissions from other gNBs need to be restricted. The following methods can be considered for this purpose.

[0181] - A gNB can instruct other gNBs about a specific resource (e.g., a muting resource) through information such as a reference SCS, periodicity, slot / symbol offset, etc., via an Xn / F2 interface, etc. Such an instruction of a muting resource for UL muting can be signaled together with existing information signaled between gNBs (e.g., intended TDD UL DL configuration information). In this way, by ensuring that the gNB performs transmission of a specific reference signal (e.g., CSI-RS, SSB) or transmission of a DL signal in the muting resource for the indicated UL muting, the (other) gNB that has received information about the resource for muting can effectively perform inter-gNB channel and / or CLI measurement in the muting resource.

[0182] Against this backdrop, the following describes in detail how to instruct UEs on muting resources and how to apply the instructed muting resources. Furthermore, the UL signals / channels described below are described as PUSCH for convenience, but can naturally be applied to other UL signals / channels, such as PUCCH, SRS, and PRACH.

[0183] (1) Method of directing muting resources

[0184] 1) Method 1

[0185] The UE may be separately instructed by the gNB about the frequency domain muting resources and the time resources to which the muting resources are to be applied. In this case, the UE may identify / determine the actual muting resources by considering both the instructed frequency domain muting resources and the time resources to which the muting resources are to be applied. Alternatively, if the UE is instructed about only one of the frequency domain muting resources and the time resource information (e.g., information about the time interval to which the muting resources are to be applied), the UE may perform an operation based on a prior agreement or contract.

[0186] This method 1 has the advantage of being applicable even when the UL / DL timing between gNBs is not aligned, given that the purpose of indicating the muting resource is inter-gNB channel measurement. For example, when the Tx / Rx timing between gNBs is not aligned, it is necessary to indicate the muting resource based on the time resources of the DL signal transmitted by another gNB and / or the UL signal transmitted by the UE. To this end, the gNB needs to indicate the muting resource by considering the timing advance from the UE's perspective regarding the time at which the DL signal of another gNB should be received. However, this method may have the problem that it is difficult to align the timing boundaries of the DL signal and the UL signal of another gNB, and the gNB needs to know both the timing boundaries of the DL signal and the UL signal. This may result in a burden that significantly increases the complexity of the gNB. Therefore, as in method 1, it is necessary to (separately) indicate the time resource information (e.g., multiple consecutive slots) to which the muting pattern is applied. For example, it may be easier for a gNB to indicate the time resource information with a margin that takes into account the misalignment between the reception timing of DL from another gNB (e.g., the reception timing at which DL from another gNB is received by the gNB) and the reception timing of UL from the UE. In this respect, Method 1 has the advantage of being able to effectively perform inter-gNB channel measurements without requiring fine-grained adjustments on the time axis for muting resources.

[0187] For example, the UE may be instructed of multiple muting resources in the frequency domain for multiple REs or RBs by RRC signaling from the gNB. In this case, one muting resource (to be applied) among the multiple muting resources may be indicated through the Frequency domain resource assignment (FDRA) field of the scheduling DCI (or the new field of the scheduling DCI). In addition, the UE may be instructed of multiple time resources, each comprising at least one slot (and / or multiple symbol indices within a slot) to which the muting resource is to be applied, from the gNB through RRC signaling, and one time resource (e.g., a time resource to which the muting resource is to be applied) among the multiple time resources may be instructed through the time domain resource assignment (TDRA) field of the scheduling DCI. Alternatively, the one muting resource and / or one time resource may be indicated through the new field of the scheduling DCI. When the time resource is indicated by a slot index (e.g., indicated by a TDRA field of scheduling DCI), the UE may apply the muting resource (e.g., indicated by a TDRA field of scheduling DCI) when transmitting a PUSCH in a slot having the slot index (e.g., when a transmission occasion is located at the indicated slot index). Alternatively, when the time resource is indicated by a symbol index (e.g., indicated by a TDRA field of scheduling DCI), the UE may apply the muting resource only to a symbol that overlaps with a symbol having the symbol index among symbols indicated by the TDRA of the PUSCH.When time resources are indicated through a slot index and a symbol index within the slot, the UE can apply muting resources only for symbols in which a transmission opportunity of a PUSCH is located in a slot having the slot index, and in which the indicated symbol index and the TDRA of the PUSCH overlap.

[0188] Alternatively, the UE may additionally consider the following prior commitments or agreements when only one of the muting resources and the time resource to apply it is indicated by the gNB.

[0189] - The UE may expect that the gNB will not indicate either the muting resource or the time resource to which the muting resource is to be applied. For example, if the UE is indicated for either the muting resource or the time resource to which the muting resource is to be applied, the UE may determine that the indication is invalid (or the UE may consider that no such indication is given).

[0190] - Alternatively, the UE may transmit only DMRS in the PUSCH transmission when only time resources are instructed by the gNB without an instruction of a muting pattern. For example, the UE may mute the remaining PUSCH REs (e.g., REs scheduled for PUSCH) excluding only DMRS in the instructed time resources of the PUSCH when a separate muting pattern is not instructed.

[0191] - Alternatively, the UE may apply a default muting pattern by prior agreement or agreement when it is instructed only of time resources without an instruction of a muting pattern from the gNB. Here, the default muting pattern may be composed of REs with even indices or REs with odd indices among the REs indicated in the FDRA (e.g., the FDRA field of the DCI).

[0192] 2) Method 2

[0193] The UE may be instructed by the gNB to provide at least one muting resource configured in the time domain and frequency domain, and may be instructed to provide a PUSCH transmission opportunity or slot index to which the at least one muting resource is to be applied. Method 2 thus has the advantage of minimizing the waste of REs resulting from the configuration / application of muting resources when the timing for inter-gNB measurements is aligned or close enough that timing alignment is not required.

[0194] For example, when applying Method 2, muting resources may be indicated based on the UCI multiplexing rule. The UE may be indicated only the number of REs as muting resources from the gNB, and may determine / specify the time / frequency positions of the indicated number of REs based on the UCI multiplexing rule. For example, the UE may determine / consider that REs to which CSI-part2 is multiplexed have been indicated as muting resources, assuming that HARQ-ACK and CSI-part 1 of a predetermined number (or a separately indicated number) of REs have been multiplexed. Alternatively, the UE may be indicated by the gNB via signaling such as RRC / MAC-CE / DCI a beta offset for determining that HARQ-ACK and CSI-part 1 have been dynamically multiplexed for REs to which muting resources are indicated, or may determine (the beta offset) by a prior agreement or contract.

[0195] Alternatively, since the muting pattern is intended for channel measurement between gNBs, the muting pattern may be indicated based on a specific reference signal transmitted by the gNB. For example, the gNB may indicate a resource ID such as ZP-CSI-RS, SSB, CSI-IM, etc., and the UE may specify a muting resource based on a symbol location within a slot and a frequency location within a BWP of a reference signal corresponding to the resource ID. Alternatively, for the purpose of applying a muting pattern to the UL transmission of the UE, the gNB may indicate the muting pattern / muting resource based on a specific reference signal transmitted by the UE. For example, the gNB may indicate a resource ID such as SRS, CLI-RSSI, etc., and indicate a muting resource based on a symbol location within a slot and a frequency location within a BWP of a reference signal corresponding to the resource ID.

[0196] When the gNB instructs the UE to use muting resources using the above method 2, the information indicating the muting resources can be transmitted / instructed to the UE as cell-specific configuration information. This is because the application of muting resources to UL resources is intended for inter-gNB channel measurement, and therefore it is appropriate to apply them commonly to all UEs within the cell.

[0197] (2) Method of applying muting resources

[0198] The UE performs predetermined actions in applying the muting resources indicated by the gNB. For example, the UE may perform rate matching or puncturing on all time / frequency resources that match the indicated muting resources, judging that the resources have not been allocated. Here, rate matching means that the UE does not perform data mapping on REs indicated as muting resources because it judges that the resources have not been allocated, and puncturing means that the UE performs data mapping (or, after generating a PUSCH) on REs indicated as muting resources, and does not perform transmission on REs indicated as muting resources.

[0199] Alternatively, the UE may consider the following methods when the indicated muting resource partially overlaps with the time / frequency resource of the DMRS of the PUSCH. For example, in the case of a muting resource that partially overlaps with the time / frequency resource of the DMRS of the PUSCH, the UE may determine that there is no indication of the muting resource and may not apply the muting resource. This is to prioritize channel estimation between the gNB and the UE over channel estimation between the gNBs. Alternatively, in the case of a muting resource that partially overlaps with the time / frequency resource of the DMRS of the PUSCH, the UE may determine that the time / frequency resource where the DMRS is located among the muting resources is not valid as a muting resource. For example, the UE may transmit the DMRS on the time / frequency resource that partially overlaps with the muting resource, but apply the muting resource only to the time / frequency resource that does not overlap with the DMRS. Alternatively, for muting resources that partially overlap with the time / frequency resources of the DMRS of the PUSCH, the UE may determine that the time / frequency resources of the DMRS are also indicated as muting resources. This may be an appropriate method for saving power of the UE and reducing interference due to unnecessary signal transmission, as other gNBs may transmit signals for CLI and / or channel measurement for resources to which muting resources are applied, which is expected to degrade the reception performance of the DMRS at the gNB level.

[0200] 2. Scenario 2

[0201] The UE is instructed by the gNB to use a specific time resource or time / frequency resource as a muting resource through RRC / MAC-CE / DCI, etc., and can apply the muting resource when the muting resource overlaps with the UL signal / channel transmitted by the UE.

[0202] The muting resource indication described below may be for the purpose of channel and / or CLI estimation between gNBs. For example, it may be desirable to indicate that the indicated muting resource is applied only during a period (e.g., a time period) in which CLI is determined to be severe between gNBs, or during a period (e.g., a time period) in which CLI is expected to exist between gNBs. In this context, the following methods may be considered. The UE may determine that the indicated muting resource is valid only within the time period in which the gNB performs the SBFD operation, which the gNB has indicated to the UE via a system information block (SIB), etc. This is because it is appropriate for the gNB to perform CLI handling during the time period in which the SBFD operation is performed. Alternatively, the UE may be configured (separately) with a time period in which the muting resource is valid, separately from the muting resource indication by the gNB. This may be useful in cases where the serving gNB and other gNBs perform SBFD operations during different time intervals (e.g., when the serving gNB does not perform SBFD operations but other gNBs perform SBFD operations, such that resources are available for inter-gNB CLI to exist).

[0203] In order for channel measurements between gNBs to be properly performed in relation to the UL muting operation described below, not only the serving UE but also other gNBs must be aware of muting resource information related to the UL muting operation. This is to allow a specific gNB to transmit a reference signal in the muting resource corresponding to the muting resource information, while restricting transmission operations of gNBs other than the specific gNB. For this purpose, the following methods may be considered.

[0204] - A gNB can instruct (other gNBs) about a specific (muting) resource based on information such as reference SCS, periodicity, slot / symbol offset, etc. through an Xn / F2 interface, etc. Such an instruction of a muting resource for UL muting can be signaled together with existing information signaled between gNBs (e.g., intended TDD UL DL configuration information). The muting resource for UL muting indicated in this way ensures that the gNB performs transmission of a specific reference signal (e.g., CSI-RS, SSB) (or, DL signal transmission), and other gNBs that have received information about such a muting pattern can perform channel and / or CLI measurements between gNBs in the muting resource.

[0205] Below, the method for indicating the aforementioned muting resources and the method for applying the indicated muting resources are described separately. Furthermore, the UL signals / channels described below are described as PUSCH for convenience, but can naturally be applied to other UL signals / channels such as PUCCH, SRS, and PRACH.

[0206] (1) Method of indicating muting resources

[0207] The UE may be instructed of time and / or frequency resources (e.g., muting resources) for muting separately from the time / frequency resource indication of a specific UL signal / channel from the gNB. For example, if only time resources are instructed as muting resources from the gNB, the UE may be configured with muting resources for multiple bundles from the gNB in ​​units of {periodicity, multiple slot indices, or slot indices and symbol indices} via RRC / MAC-CE / DCI, etc. Alternatively, if muting resources are instructed as time / frequency resources, the UE may be configured with muting resources for multiple bundles from the gNB in ​​units of {periodicity, multiple slot indices or symbol indices, multiple PRBs, or PRBs and RE indices}.

[0208] SCS may also be indicated together to indicate slots / symbols and RBs / REs for the above-described muting resources. This may facilitate more flexible indication of actual time / frequency resources even when indicated with the same slots / symbols and RBs / REs. For example, if muting resources and reference SCSs are indicated together from the gNB, the UE may determine / specify the indicated time resources or time / frequency resources based on the indicated SCS. Alternatively, if SCS is not set in the indication of muting resources from the gNB, the UE may determine / consider that the SCS of the active UL BWP is indicated as the SCS.

[0209] Alternatively, if the UE receives an indication of a muting resource from the gNB via MAC-CE and / or DCI signaling, the following methods may be considered. The UE may receive a list of muting resources from the gNB via RRC signaling, and may activate / deactivate a specific muting resource with an indication such as an ID of the muting resource via MAC-CE. And / or, the UE may receive a list of muting resources from the gNB via RRC signaling, and may be instructed to apply the muting resource at a specific time resource with an indication such as an ID of the muting resource via DCI.

[0210] Alternatively, since the muting resource is intended for channel measurement between gNBs, the muting resource may be indicated based on a specific reference signal transmitted by the gNB. For example, if a resource ID such as ZP-CSI-RS, SSB, CSI-IM, etc. is indicated (in relation to the muting resource), the muting resource may be indicated based on a symbol position within a slot and / or a frequency position within a BWP of the indicated reference signal. Alternatively, since the muting resource is intended for application when the UE transmits, the muting resource may be indicated based on a specific reference signal transmitted by the UE. For example, if a resource ID such as SRS, CLI-RSSI, etc. is indicated (in relation to the muting resource), the muting resource may be indicated based on a symbol position within a slot and a frequency position within a BWP of the indicated reference signal.

[0211] When a gNB instructs a UE to provide muting resources using the methods described above, the information indicating the muting resources may be transmitted to the UE as cell-specific configuration information. This is because UL resource muting needs to be applied commonly to all UEs within a cell when the purpose is to measure channels between gNBs.

[0212] (2) Method of applying muting resources

[0213] The UE may apply the muting resources indicated / configured by the gNB in ​​the above-described manner when there is some overlap between the muting resources and the uplink signals / channels scheduled by the gNB. The method for applying such muting resources may vary depending on the uplink signals / channels scheduled by the gNB (e.g., the uplink signal / channel type).

[0214] 1) In the case of PUSCH

[0215] For example, in the case of PUSCH (e.g., if the time / frequency resources of the PUSCH scheduled by the gNB overlap at least partly with the indicated muting resources), the UE may transmit the PUSCH after performing rate matching or puncturing on the resources of the PUSCH that overlap with the resources indicated as the muting resources. For example, since the indicated muting resources are resources that the gNB intentionally wants to empty (e.g., for inter-gNB channel and / or CLI measurement), the UE may not transmit on the indicated muting resources according to this intention.

[0216] Alternatively, if the time / frequency resources of the PUSCH scheduled from the gNB overlap even partially with the indicated muting resources, the UE may transmit the PUSCH by performing rate matching or puncturing on the PUSCH resources that overlap with the muting resources. However, the DMRS may be transmitted even if it overlaps with the muting resources. This is because the channel estimation between the UE and the gNB should be prioritized over the channel and / or CLI estimation between the gNBs.

[0217] Alternatively, if UCI is multiplexed and transmitted on some of the PUSCH resources that overlap with muting resources, the UE may transmit PUSCH without performing rate matching or puncturing. This is because, since muting resources are resources that the gNB intentionally wants to vacate (e.g., for inter-gNB channel and / or CLI measurements), it is appropriate for the UE to refrain from transmitting on those resources accordingly, but further guarantees of transmission of UCI, which is important information, are needed.

[0218] 2) In case of PUCCH

[0219] Alternatively, in case of PUCCH (e.g., if the indicated muting resource and the time / frequency resource of the PUCCH scheduled from the gNB overlap even partially), the UE does not transmit PUCCH in the transmission opportunity of PUCCH that overlaps with the resource indicated as the muting resource. If the repetition transmission for the PUCCH is indicated / configured, the UE may not count the PUCCH repetition for the PUCCH resource that overlaps with the resource indicated as the muting resource, since the UE did not transmit PUCCH in the PUCCH resource.

[0220] 3) In case of PRACH

[0221] For PRACH (e.g., if the indicated muting resources and the time / frequency resources of the PRACH scheduled from the gNB overlap even partially), the UE may transmit the PRACH by performing rate-matching or puncturing on the resources that overlap with the resources indicated as muting resources.

[0222] Alternatively, if the time / frequency resources of the indicated muting resources and the CBRA (contention-based random access) PRACH overlap even partially, the UE may determine that no muting resources have been set and perform PRACH transmission. This is because CBRA PRACH transmission is a high-priority transmission for purposes such as initial access or RLF (Radio link failure), and therefore it is appropriate to protect PRACH transmission as much as possible.

[0223] Alternatively, the UE may conditionally drop transmissions on repeated PUSCH transmissions with muting resources applied, such as through the methods described in Scenario 1 and / or Scenario 2, or transmit only DMRS on said transmission opportunities (e.g., PUSCH transmission opportunities that (partially) overlap with muting resources).

[0224] For example, if the actual repetition of a PUSCH with muting resources applied is less than or equal to X symbols in the time domain, the UE may not perform transmission for the PUSCH. Since the configurable SLIV of PUSCH repetition type A is 4 symbols or more, a value of 2 or 3 may be set / considered as the value of X.

[0225] Alternatively, if the actual repetition of the PUSCH with muting resources applied is 2 or 3 symbols or less in the time domain, the UE may transmit only DMRS without data on the PUSCH. Such a PUSCH (e.g., a PUSCH containing only DMRS without data) may help in channel estimation between the UE and gNB at the gNB, while at the same time minimizing contamination of inter-gNB channel measurements or CLI measurements.

[0226] Alternatively, if the actual repetition of the PUSCH with the muting resource applied is 2 or 3 symbols or less in the time domain and the indicated muting resource does not overlap with any part of the DMRS of the PUSCH, the UE may transmit only the DMRS without data for the PUSCH. This is because, compared to the previous method, it does not contaminate the inter-gNB channel measurement or CLI measurement at all, and at the same time, if the conditions are met, it can also help in estimating the channel between the UE and the gNB at the gNB via the DMRS.

[0227] Alternatively, when the application of muting resources to some resources of the PUSCH is indicated, such as through the methods proposed in Scenario 1 and Scenario 2, DMRS bundling may also be indicated for the transmission of the PUSCH. In this case, the UE may operate / understand the PUSCH with the muting resources applied in a different way from the conventional way in terms of maintaining phase continuity and power consistency. For example, the UE may treat the PUSCH with the muting resources applied as a semi-static event. For example, the UE may treat / determine that the PUSCH with the muting resources indicated is included in the nominal time domain window but not included in the actual time domain window. If the muting resources are applied in the middle of the PUSCH repetitions transmitted according to the instruction, the UE may always start the actual time domain window (e.g., regardless of the UE's capability) after the PUSCH with the muting resources applied.

[0228] Alternatively, the UE may not include the PUSCH indicated by the muting resource in the counting of the nominal time domain window. For example, if the PUSCH indicated by the muting resource is included in the nominal time domain window, the actual time domain window may be unnecessarily shortened. To avoid unnecessarily shortening the actual time domain window, when the UE places the PUSCH indicated by the muting resource in the nominal time domain window, the UE may place only the remaining PUSCHs except the PUSCH to which the muting resource is applied in the nominal time domain window (or, when placing the nominal time domain window, place the nominal time domain window only for the remaining PUSCHs except the PUSCH to which the muting resource is applied). The purpose of DMRS bundling is to obtain joint combination gain at the gNB level, and the serving gNB has a high probability of experiencing strong CLI from other gNBs for the PUSCH indicated by the muting resource. This method has the advantage of effectively ensuring CLI measurements without losing the DMRS bundling benefits.

[0229] Alternatively, the UE may not treat a PUSCH with muting resources as an event. From the UE's perspective, the transmit power for the PUSCH transmission opportunity with muting resources applied has not changed, and the time / frequency resource configuration of the PUSCH may not have changed except for some resources. Therefore, phase continuity can be maintained. Since the receiving gNB is the entity that processes the DMRS-bundled PUSCHs to achieve combining gain, joint combining may still be possible depending on the gNB implementation. Therefore, even if a PUSCH with muting resources is present, the UE may not treat it as an event but may include it in the actual time domain window and perform transmission while maintaining phase continuity / power consistency. This may be similar to the existing operation, considering that even if UCI multiplexing is performed on the PUSCH, it is still not an event.

[0230] When some of the PUSCH REs are muted by the above-described methods and transmitted with DFT-S-OFDM (discrete Fourier transform spread orthogonal frequency division multiplexing), the PAPR (Peak To Average Power Ratio) may increase if the existing DFT size is used as is. In this way, an increase in PAPR due to RE muting may not be desirable. As an example of a method to prevent PAPR from increasing in a symbol where RE muting is used, a method of adjusting the DFT size to the number of REs remaining excluding the number of REs being RE-muted may be considered. For example, when a DFT size of 12 RE * N RB length is used, a DFT of 6 RE * N RB length may be used in the OFDM symbol position where RE muting is performed. For example, if RE muting is indicated for a PUSCH RE transmitted with DFT-S-OFDM, the UE can configure the PUSCH by applying DFTs of different sizes to symbols for which RE muting is indicated and symbols for which RE muting is not indicated.

[0231] UCI multiplexing can be performed on a PUSCH to which muting resources have been indicated. The existing UCI multiplexing rules are described in 3GPP TS 38.212. Meanwhile, for a given scenario (e.g., a work item related to PUSCH muting), it is assumed that the provisions defined in Section 6.2.7 of 3GPP TS 38.212 will not be changed. Under this assumption, the following approaches may be considered for performing UCI multiplexing on a PUSCH to which muting has been applied.

[0232] - Approach 1: If the UE determines that UCI multiplexing is performed on a PUSCH for which muting is indicated, UL muting can be applied after determining the UCI RE. At this time, if a UCI corresponding to a muting resource exists, muting may not be applied to the muting resource. For example, whether or not to apply a muting resource can be determined after UCI multiplexing. In this case, since UCI transmission is not missed due to UL resource muting, the existing UCI multiplexing rules can be maintained.

[0233] - Approach 2: If it is determined that UCI multiplexing is performed for a PUSCH for which muting is indicated, the UE may apply UL muting after determining a UCI RE. If UL muting is indicated for a resource determined as a UCI RE, the UE applies muting for the UCI RE, but the UCI corresponding to the UCI RE may be transmitted in the remaining UCI RE resources for which muting is not indicated. In this case, if the UCI RE is muted, the number of REs to which UCI is allocated will decrease. Considering this, the gNB may instruct the UE to scale the beta offset to prepare for the decrease in the UCI RE. The beta offset scaling may be indicated during the scheduling of the PUSCH, or may be performed through separate signaling such as RRC / MAC-CE / DCI. The UE may be instructed to apply a beta offset for a PUSCH with UCI multiplexing performed without muting and a beta offset for a PUSCH with UCI multiplexing performed with muting applied, based on the indication of the scaling parameter, or may be separately instructed to apply a beta offset for a PUSCH with UCI multiplexing performed without muting and a beta offset for a PUSCH with UCI multiplexing performed with muting applied.

[0234] - Approach 3: If the UE is instructed to mute the PUSCH on which UCI multiplexing is performed, the UE may perform UCI RE mapping after applying UL muting. In this case, since the resource for which muting is instructed is no longer a PUSCH data RE, UCI RE mapping is not performed. For such an operation, the definition of "number of resource elements that can be used for transmission of UCI in OFDM symbol of PUSCH" in the above-mentioned scenario (Section 6.3.2.4.1 of 3GPP TS 38.214) needs to be modified. For example, the existing "number of coded modulation symbols per layer for HARQ-ACK transmission, number of coded modulation symbols per layer for CSI-part 1 transmission, number of coded modulation symbols per layer for CSI-part 2 transmission" are all described in a given scenario (e.g., section 6.3.2.4.1 of 3GPP TS 38.214). For example, the "number of coded modulation symbols per layer for HARQ-ACK transmission" is defined as in Table 9 below.

[0235] 6.3.2.4.1 UCI encoded by Polar codeIf the higher layer parameternrof_UTO_UCIis configured, the procedures in this clause and the clauses it refers to apply by replacing CG-UCI with UTO-UCI in all the notations and texts, when applicable.6.3.2.4.1.1 HARQ-ACKFor HARQ-ACK transmission on PUSCH not using repetition type B with UL-SCH and ifnumberOfSlotsTBoMSis not present in the resource allocation table, or ifnumberOfSlotsTBoMSis present in the resource allocation table and the value ofnumberOfSlotsTBoMSin the row indicated by the Time domain resource assignment field in DCI is equal to 1, the number of coded modulation symbols per layer for HARQ-ACK transmission, denoted as is determined as follows: where- O ACK is the number of HARQ-ACK bits;- if ; otherwise L ACK is the number of CRC bits for HARQ-ACK determined according to Clause 6.3.1.2.1;- ;- C UL-SCHis the number of code blocks for UL-SCH of the PUSCH transmission;- if the DCI format scheduling the PUSCH transmission includes a CBGTI field indicating that the UE shall not transmit the r-th code block, Kr=0; otherwise, Kr is the r-th code block size for UL-SCH of the PUSCH transmission;- is the scheduled bandwidth of the PUSCH transmission, expressed as a number of subcarriers;- is the number of subcarriers in OFDM symbol l that carries PTRS, in the PUSCH transmission;- is the number of resource elements that can be used for transmission of UCI in OFDM symbol l, for , in the PUSCH transmission and is the total number of OFDM symbols of the PUSCH, including all OFDM symbols used for DMRS;- for any OFDM symbol that carries DMRS of the PUSCH, ;- for any OFDM symbol that does not carry DMRS of the PUSCH, ;- αis configured by higher layer parameterscaling;- l0is the symbol index of the first OFDM symbol that does not carry DMRS of the PUSCH, after the first DMRS symbol(s), in the PUSCH transmission.

[0236] For example, as defined in Table 9 The number of REs available for OFDM symbol l of each PUSCH is used to derive can be used. At this time, if the symbol is a symbol to which muting is applied (or, a muted symbol), it may be necessary to determine the number of available REs differently. For example, used in the calculation of When UL resource muting is applied to the corresponding OFDM symbol, the number of subcarriers of the PUSCH to which muting is applied or the number of REs can be derived from the scheduled bandwidth expressed as the number of subcarriers of the PUSCH. For example, it can be newly defined as in Table 10.

[0237]

[0238] Here, ZP SRS is a resource for indicating UL resource muting, may be the number of REs or subcarriers on which UL resource muting is applied to the PUSCH symbol and PUSCH data is not transmitted. For example, a proposed method as shown in Table 11 below may be considered.

[0239] (According to WID) Resources for which UL resource muting is determined (i.e., PUSCH transmission resources that overlap with ZP SRS and for which UL resource muting is determined to be applied) are rate-matching, not puncturing. If UCI multiplexing is performed on PUSCH with UL resource muting applied, UCI transmission is also transmitted within the PUSCH resource according to the current specification, so there is no issue of overlap between UCI transmission resources and muting resources. Observation x. Since the UL resource muting is rate-matching, the UCI multiplexed RE of PUSCH cannot be indicated by UL resource muting. It should be written that UL resource muting is for the purpose of protecting UCI with a rate-matching motivation, not puncturing. Muting should not be applied to PUSCH (PUSCH for aperiodic CSI reporting) where only UCI is transmitted with the same motivation. However, when UCI multiplexing is performed on PUSCH with muting applied, the number of coded modulation symbols per layer for {HARQ-ACK, CSI part1, CSI part 2} is calculated based on the number of REs available per symbol. Currently, the calculation is 0 for DMRS symbols, and only through the difference in the sub-carriers on which PT-RS is transmitted in the scheduled BW in other cases. However, in the case of muted symbols, the number of REs has decreased, and this may need to be reflected. Proposal x.To determine the number of coded modulation symbols per layer for UCI, ie, Q'_ACK, Q'_CSI-1, Q'_CSI-2, the number of muted REs should be accounted for the number of REs that can be used for transmission of UCI in the OFDM symbol when UCI is multiplexed on UL resource muted PUSCH.

[0240] Below, the proposed methods described above are described in detail in relation to a given scenario.

[0241] Uplink resource muting for PUSCH

[0242] Figures 11 to 13 are drawings for explaining a method of setting muting resources related to UL muting.

[0243] At the study item stage, it was agreed to introduce uplink resource muting for PUSCH. Before discussing the design details, it is necessary to clearly understand the motivation for its introduction and the following characteristics. The motivation for introducing UL resource muting is to reserve some REs for PUSCH transmission, so that such resources can be used for gNB-gNB co-channel CLI measurement and estimation. Instead of directly measuring the CLI between gNBs on the muted REs, a covariance matrix can be measured. For example, referring to Figure 11, the muted resources can be generically indicated between potential attacker gNBs to enable covariance estimation. Here, uplink resource muting for PUSCH is applicable to both DFT-S-OFDM and CP-OFDM, and the actual application of DFT-S-OFDM or CP-OFDM may vary depending on the UE capabilities.

[0244] Uplink resource muting for PUSCH may have very specific restrictions. It is explicitly stated that no new DCI field / MAC CE is introduced for indicating / determining UL resource muting, which may mean that it consists solely of RRC signaling. Furthermore, it may be expected that the data and control multiplexing defined in a given scenario (Section 6.2.7 of TS 38.212) will not be affected. For example, the UCI multiplexing for PUSCH may not change regardless of muting. Furthermore, the TBS determination for PUSCH may not change. Finally, the UE may assume / consider that the muting resources for UL resources do not overlap with UL DMRS or PT-RS in the same symbol. For example, muting resources for reference resources do not apply. Muting resources are comb-2 in each allocated PRB and can be indicated / configured for up to two symbols in the time domain. Based on this, details on how to configure UL resource muting and related UE operations are described in detail below.

[0245] When muting resources are configured via RRC signaling, there are two main ways to indicate UL resource muting. The first method is to specify specific time / frequency resources to be excluded from the resource configuration of a specific PUSCH. The second method is to separately designate a muting resource, but if it overlaps with the PUSCH, the muting resource may be applied and the resources of the muting resource may be muted. The first method is applicable only to periodic PUSCH because it does not introduce or improve the MAC-CE / DCI. This is because the motivation for introducing uplink resource muting is to estimate the covariance matrix of the inter-gNB channel, and the first method may not be consistent with the motivation for introducing it. Therefore, the second method may be more appropriate to meet the motivation for introduction. This operation may be an uplink version of ZP CSI-RS, given that the downlink ZP CSI-RS is a method for indicating raid matching (or muting) of the PDSCH. For ease of discussion and intuitive understanding, these reference signals can be defined as ZP SRS, i.e., zero power SRS.

[0246] Parameters for ZP SRS configuration can be considered. Since the purpose is long-term channel measurement between gNBs, the configuration parameters need not change according to the UE's request or BWP. Therefore, a reference SCS needs to be specified. Since the muting resources / muting patterns are already defined, it may be sufficient to indicate whether the RE is even / odd, the frequency bandwidth, the period in the time domain and the time offset (slot offset, symbol offset) from the period to the resource to be actually configured, and the number of symbols (symbol length) where the resource is located.

[0247] For example, UL resource muting for PUSCH can be indicated via a Zero-power SRS (ZP SRS). The ZP SRS can be configured with the following parameters.

[0248] - Reference SCS

[0249] - RB number, even / odd RE

[0250] - Period, slot offset, symbol offset, symbol length (1 or 2)

[0251] Here, the muting pattern / muting resource may have a length of 1 or 2 symbols at the comb-2 frequency, but it may not be clear whether the two muting patterns / muting resources can intersect. For example, referring to Fig. 12 (a), in the case of a muting pattern with a length of 2 symbols, even REs may be muted in the first symbol and odd REs may be muted in the second symbol (e.g., an intersection of the two muting patterns) (Option 1). Alternatively, either even REs or odd REs may be applied to both symbols (Option 2). Additional discussion may be required regarding the reference signal to be used for estimating the inter-gNB covariance matrix and / or constraints on UE operation for a specific muting pattern. In summary, the following options may be considered for a UL resource muting pattern with a length of 2 symbols:

[0252] - Option 1. Muted REs are crossed at the symbol level.

[0253] - Option 2. Muted REs are the same across symbols.

[0254] Since ZP SRS will be used to measure the covariance matrix between gNBs operating in SBFD mode, we can aim to ensure that ZP SRS is muted from the UE perspective. Since dynamic / non-aligned SBFD operation is not introduced in a given scenario, the SBFD configuration between gNBs can be the same. Therefore, ZP SRS needs to be applied only during the time periods when gNBs operate in SBFD mode. The simplest and most direct solution is for the UE to assume that ZP SRS is configured only during SBFD operation. Alternatively, ZP SRS can be considered to be applicable only to SBFD operation, but can be configured for SBFD / non-SBFD operation. For example, a validity test for the configured ZP SRS can be introduced. In summary, the UE can expect that ZP SRS is configured only during SBFD operation.

[0255] Uplink resource muting may be designed based on the fact that the purpose of uplink resource muting is to estimate the covariance matrix between gNBs and that gNBs perform long-term measurements on the muted resources. Therefore, while it is not a problem if the UE can mute all requested resources, if it can mute only some of the resources for muting, it may be a problem whether to mute only some of them or not at all (e.g., to apply partial muting or not apply muting to all designated muting resources). Transmitting such partial muting may, in effect, be equivalent to supporting flexible muting resources.

[0256] When PUSCH is introduced, significant discussion may ensue regarding the muting resources. As a result of this discussion, muting resources are defined as being limited to comb-2 in the frequency domain and 2 symbols in the time domain. In the frequency domain, this limitation may be aimed at minimizing the impact on PUSCH PAPR. For example, PARP issues may be exacerbated when transmitted via DFT-S-OFDM. Against this backdrop, it may be appropriate for UEs to mute using designated muting resources or not mute at all. In summary, muting can be applied to PUSCH REs indicated in the ZP SRS only if all designated resources can be muted.

[0257] Based on basic rules, the application and scope of muting can be determined in various situations. First, the conflict between ZP SRS and UCI must be considered. Resources indicated by ZP SRS and resources indicated by UCI should not overlap, which was a common understanding among the group during the Study Item stage. However, the discussion primarily focused on UCI multiplexed on PUSCH, and the same rule should also apply to PUSCHs that only contain UCI (e.g., PUSCHs used for aperiodic CSI reporting). If UCI within a PUSCH overlaps with a ZP SRS, the ZP SRS should not be applied. The same rule applies to reference signals: if the REs containing the reference signal and the REs of the ZP SRS collide, the ZP SRS should not be applied. In summary, the UE mutes REs that overlap with ZP SRS in a PUSCH symbol only if the following conditions are met:

[0258] - If the RE indicated by muting does not include UCI

[0259] - When the RE indicated by muting does not contain a reference signal (DMRS, PTRS)

[0260] The performance benefits of BFD primarily stem from contiguous UL slots. Even with the same DL and UL ratio, more contiguous UL slots can improve coverage and reduce latency. To achieve this, several UL coverage enhancement and URLLC features exist, such as PUSCH repetition (Type B), TB processing over multi-slot (TBoMS), and DMRS bundling. The availability of these features depends on the scheduling flexibility of the gNB. If UL resource muting is not applied globally to PUSCH transmissions, the benefits of SBFD may be diminished. To prevent this, it is reasonable to ensure flexibility in UL resource muting settings. In summary, UL resource muting applies to PUSCH, including PUSCH repetition (Types A and B), DMRS bundling, and TBoMS.

[0261] As previously discussed, if the resources indicated by the ZP SRS partially overlap with the UCI and reference signals of the PUSCH, muting should not be applied to the entire ZP SRS-indicated resources, including both overlapping and non-overlapping resources, for UE-side simplicity. However, if the ZP SRS does not cover the entire bandwidth (BW) or symbols of the PUSCH transmission opportunity, it is also necessary to discuss how the UE should interpret this.

[0262] For example, referring to Fig. 12 (b) (when the ZP SRS does not cover the entire RB of the PUSCH), the number of RBs indicated by the ZP SRS may not cover the entire bandwidth of the PUSCH transmission opportunity or the allocated PRB. In this case, two options can be considered. First, the option of not applying PUSCH muting is the most intuitive and unambiguous, but may degrade the inter-gNB covariance matrix estimation performance. Second, the option of applying UL resource muting by expanding the resources indicated by the ZP SRS may be a better approach for covariance matrix estimation, but may result in PUSCH performance degradation. This has the same impact as when the entire time-frequency domain is reserved, and DMRS / PTRS deployment may want to avoid this. In summary, if only some REs of the PUSCH overlap with the ZP SRS in the frequency domain, UL resource muting is not applied.

[0263] Next, referring to Fig. 12 (c) (when the ZP SRS does not cover the entire symbol of the PUSCH), the ZP SRS has a two-symbol length and can overlap only one symbol with a specific PUSCH transmission opportunity (i). In this case, if the resource indicated by the ZP SRS does not overlap with the UCI or reference signal of the PUSCH, the PUSCH must be muted. Therefore, even if the symbol indicated by the ZP SRS does not completely cover the PUSCH transmission opportunity, UL resource muting is applied if it does not collide with the UCI and reference signal. In summary, if the bandwidth of the ZP SRS includes the PUSCH, but the entire symbol indicated by the ZP SRS does not cover the PUSCH transmission opportunity, UL resource muting can be applied.

[0264] Next, PUSCH and other mechanisms with UL resource muting may be as follows.

[0265] To benefit from SBFD operation, UL resource muting must be applicable to various types of PUSCH (e.g., PUSCH repetitions, DMRS bundling, TBoMS, etc.). While supporting this is technically necessary, careful consideration is required when applying it. For PUSCH repetition Type A, there is no ambiguity regarding muting only some of the repeated PUSCHs. This is similar to the case where UCI multiplexing is applied only to some PUSCH repetitions, if necessary. On the other hand, PUSCH repetition Type B requires additional consideration. In PUSCH repetition Type B, a single symbol is omitted from the actual repetition, which corresponds to the case where the PUSCH symbol length is 1. That is, if the PUSCH symbol length is 2 or greater, all PUSCH repetitions are transmitted. If a specific repetition is muted by the ZP SRS in PUSCH repetition Type B, as illustrated in Figure 13, the number of REs containing data may be significantly reduced.

[0266] Referring to FIG. 13, if the actual repetition of the PUSCH has a symbol length of 2 (e.g., A2 in FIG. 13), the subsequent symbol may be designated by the ZP SRS but may not collide with the UCI and DMRS. In this case, the remaining data REs may only be REs excluding the ZP SRS and DMRS. However, if the DMRS is Code Division Multiplexed (CDM), the symbol in which the DMRS is transmitted cannot be used as a data RE, resulting in a situation where no data REs exist. In this case, there is a high possibility that A2 reception will not be successful due to the extremely high coding rate. The simplest way to prevent this is to consider the symbol designated by the ZP SRS as an invalid symbol. However, this method is inefficient because if the invalid symbol is located in the middle, one repetition will be divided into two independent repetitions, increasing the coding rate. To prevent this, UL resource muting should be applied only when the symbol length of the actual repetition is 3 or more. To summarize, the UE can apply UL resource muting only when the symbol length of the actual repetition in PUSCH repetition Type B is 3 or more.

[0267] The REs of symbols with UL resource muting are assumed to have power boosting applied. However, since the transmit power of the PUSCH does not change between symbols, if a muted PUSCH and an unmuted PUSCH exist within the same repetition, the transmit power between the two PUSCHs may differ. This problem becomes more pronounced when combined with DMRS bundling. In general, the power of the DMRS is proportional to the PUSCH power, and the relationship between the PUSCH EPRE (Equivalent Power Radiated per Element) and the DM-RS EPRE is defined according to a given scenario (TS 38.214 Section 6.2.2). However, if some symbols within the PUSCH are muted, it may not be possible to maintain power consistency throughout the entire PUSCH repetition. For example, if a portion of the PUSCH is muted, power consistency cannot be maintained throughout the entire PUSCH repetition.

[0268] When UL resource muting is used on PUSCH with DMRS bundling, consideration must be given to how to handle it. The simplest approach is to treat UL resource muting as a semi-static event. Since both DMRS bundling and UL resource muting are configured via RRC signaling, treating them as semi-static events is feasible and simple to implement. However, it is important to consider that the actual time domain window is placed after the semi-static event. This means that the semi-static event splits the originally single time domain window into two independent windows, which can reduce the performance benefits expected from DMRS bundling. To prevent this, time domain window placement can be configured to account for UL resource muting. That is, rather than treating the muted PUSCH as a single event, the muted PUSCH is placed so that it is not included in the time domain window. Both options require further discussion, but the former, with its simpler implementation, may be a sufficient solution. In summary, when DMRS bundling is configured, PUSCH with UL resource muting applied can be considered a semi-static event.

[0269] FIG. 14 is a diagram illustrating a method for a UE to apply muting resources in transmission of an uplink signal.

[0270] Referring to FIG. 14, a UE may receive muting configuration information that configures at least one muting resource related to transmission of an uplink signal from a base station (S141). For example, the muting configuration information may include information on a plurality of muting resources or a plurality of muting patterns to be applied to transmission of an uplink signal. Alternatively, the muting configuration information may configure a plurality of muting resources or a plurality of muting patterns based on a transmission time interval and / or a transmission resource of uplink signals. As described above, the muting resource may be a resource on which transmission of an uplink signal of a UE is restricted for interference measurement or CLI measurement between base stations. Meanwhile, the muting resource may include one or more REs / resources.

[0271] Next, the UE may receive downlink control information (DCI) for scheduling an uplink signal from the base station (S143). Here, the DCI may further include information indicating a first muting resource to be activated among at least one muting resource included in the muting configuration information. For example, the DCI may allocate a plurality of resources for transmission of the uplink signal, and may also include information indicating a first muting resource to be applied to the uplink signal among the at least one muting resource.

[0272] Alternatively, the DCI may indicate / activate the first muting resource among the at least one muting resource through a TDRA (Time domain resource allocation) field. For example, the TDRA field may include information on at least one time resource associated with the first muting resource among a plurality of time resources allocated for the uplink signal. For example, the TDRA field may include index information on at least one symbol associated with the first muting resource among a plurality of time resources allocated for the uplink signal. In this case, the UE may determine / specify a frequency resource (or RE) having an even index or a frequency resource (or RE) having an odd index as the first muting resource among frequency resources (or REs) included in the at least one time resource associated with the first muting resource.

[0273] Next, the UE can transmit an uplink signal based on the DCI and the muting configuration information (S145). For example, the UE can transmit the uplink signal by muting a resource designated as a first muting resource among a plurality of resources for uplink transmission allocated through the DCI. Specifically, the UE can transmit the uplink signal on the remaining resources excluding the first muting resource among the plurality of resources. For example, the UE may determine that the resource designated as the first muting resource among the plurality of resources is not allocated for transmission of the uplink signal, and may not perform data mapping for the resource designated as the first muting resource (e.g., rate matching). Alternatively, the UE may perform the data mapping including the resource designated as the first muting resource, but transmit the uplink signal only on the remaining resources excluding the resource designated as the first muting resource (e.g., puncturing).

[0274] Alternatively, the UE may not apply the first muting resource to a resource for mapping DMRS among the multiple resources allocated for the uplink signal. For example, if the first muting resource overlaps with a resource for mapping the DMRS, the UE may not apply the first muting resource to the uplink signal or may consider the first muting resource as not being indicated. For example, if all or some of the resources indicated as the first muting resource overlap with the resources for mapping the DMRS, the UE may not mute all of the resources indicated as the first muting resource for the uplink signal.

[0275] Alternatively, the UE may determine that only the resources indicated as the first muting resource and the resources overlapping with the resources for mapping the DMRS are invalid. In this case, the UE may transmit the uplink signal by muting only the remaining resources, excluding the resources for mapping the DMRS, among the resources indicated as the first muting resource.

[0276] Alternatively, if a resource for multiplexing UCI (Uplink control information) overlaps with the first muting resource among the plurality of resources allocated for the uplink signal, the UE may not apply the first muting resource in transmitting the uplink signal. For example, if all or part of the resources indicated as the first muting resource overlap with the resource for multiplexing UCI (Uplink control information), the UE may transmit the uplink signal without muting the resources indicated as the first muting resource. Alternatively, as described with reference to Table 10, the UE may multiplex UCI (Uplink Control Information) based on the number of resources remaining after subtracting the number of the first muting resources from the number of resources allocated for the uplink signal.

[0277] Meanwhile, based on configuration information that sets repeated transmission of a plurality of uplink signals related to DMRS bundling, the UE may repeatedly transmit the uplink signal. At this time, a first muting resource may be indicated for one uplink signal (or at least one uplink signal) among the plurality of uplink signals. In this case, the UE may transmit the first uplink signal including only DMRS when the number of symbols remaining, excluding at least one symbol indicated as the first muting resource among symbols for transmission of the one uplink signal, is equal to or smaller than a preset number. Here, the preset number may be 2 or 3 as described above. In addition, as described above, the UE may place / start an actual time domain window and / or a nominal time domain window related to the DMRS bundling depending on whether the first muting resource is indicated / applied.

[0278] Alternatively, the UE may receive configuration information for a first time interval associated with the sub-band full duplex (SBFD) or single frequency full duplex (SFFD) operation of the base station. In this case, the first muting resource may be valid only within the first time interval. For example, the UE may apply the first muting resource only to the uplink signal scheduled within the first time interval via the DCI.

[0279] Figure 15 is a diagram illustrating a method for a base station to instruct a UE on muting resources.

[0280] Referring to FIG. 15, a base station may transmit muting configuration information to a UE, which configures at least one muting resource associated with transmission of an uplink signal (S151). For example, the muting configuration information may include information on a plurality of muting resources or a plurality of muting patterns to be applied to transmission of an uplink signal. Alternatively, the muting configuration information may configure a plurality of muting resources or a plurality of muting patterns based on a transmission time interval and / or a transmission resource of uplink signals. As described above, the muting resource may be a resource on which transmission of an uplink signal of a UE is restricted for interference measurement or CLI measurement between base stations. Meanwhile, the muting resource may include one or more REs / resources.

[0281] Next, the base station may transmit DCI (downlink control information) for scheduling an uplink signal to the UE (S153). Here, the DCI may further include information indicating a first muting resource to be activated among at least one muting resource included in the muting configuration information. For example, the DCI may allocate a plurality of resources for transmission of the uplink signal, and may also include information indicating a first muting resource to be applied to the uplink signal among the at least one muting resource.

[0282] Alternatively, the DCI may indicate / activate the first muting resource among the at least one muting resource through a TDRA (Time domain resource allocation) field. For example, the TDRA field may include information on at least one time resource associated with the first muting resource among a plurality of time resources allocated for the uplink signal. For example, the TDRA field may include index information on at least one symbol associated with the first muting resource among a plurality of time resources allocated for the uplink signal. In this case, the base station may expect that the uplink signal will be received by muting a frequency resource (or RE) having an even index or a frequency resource (or RE) having an odd index among frequency resources (or REs) included in the at least one time resource associated with the first muting resource.

[0283] Next, the base station can receive an uplink signal based on the DCI and the muting configuration information (S155). For example, the base station can receive the uplink signal only from the remaining resources, excluding the first muting resource, among the plurality of resources. For example, the base station can receive the uplink signal that is rate-matched or punctured from the first muting resource among the plurality of resources.

[0284] Alternatively, the base station may expect that the first muting resource will not be applied to a resource for mapping the DMRS among the multiple resources allocated for the uplink signal. For example, if the first muting resource and the resource for mapping the DMRS overlap, the base station may receive the uplink signal that is not muted for the first muting resource. Alternatively, the base station may receive the uplink signal with muting applied from the remaining resources, excluding the resource for mapping the DMRS, among the resources indicated as the first muting resource.

[0285] Alternatively, if a resource for multiplexing UCI (Uplink control information) overlaps with the first muting resource among the multiple resources allocated for the uplink signal, the base station may receive an uplink signal to which muting is not applied for the first muting resource. Alternatively, as described with reference to Table 10, the base station may expect that UCI (Uplink Control Information) will be multiplexed for the uplink signal based on the number of resources remaining after subtracting the number of the first muting resources from the number of resources allocated for the uplink signal.

[0286] Alternatively, the base station may transmit configuration information for a first time interval related to the base station's sub-band full duplex (SBFD) or single frequency full duplex (SFFD) operation to the UE. In this case, the first muting resource may be valid only within the first time interval. For example, the base station may expect the first muting resource to be applied only to the uplink signal scheduled within the first time interval via the DCI.

[0287] In this way, the proposed invention can effectively configure / indicate muting resources for inter-gNB channel measurement purposes within UL resources. Alternatively, the proposed invention can efficiently transmit uplink signals within scheduled UL resources even when some of the UL resources are muted. Alternatively, the proposed invention can minimize degradation of UL throughput even when measurements for CLI mitigation are performed by configuring muting resources within UL resources.

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

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

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

[0291] Figure 16 illustrates a communication system applied to the present invention.

[0292] Referring to FIG. 16, 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.

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

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

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

[0296] Figure 17 illustrates a wireless device applicable to the present invention.

[0297] Referring to FIG. 17, 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. 16.

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

[0299] 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 FIGS. 11 to 15.

[0300] Specifically, the processor (102) of the first wireless device or UE (100) may receive muting configuration information for setting at least one muting resource, receive downlink control information (DCI), and transmit an uplink signal based on the muting configuration information and the DCI. Here, the DCI may indicate a first muting resource to be applied to the uplink signal among the at least one muting resource through a TDRA (Time domain resource allocation) field.

[0301] Alternatively, a processing device including a processor (102) and a memory (104) may be configured. In this case, the processing device may include at least one processor; and at least one memory connected to the at least one processor and storing instructions, wherein the instructions, when executed by the at least one processor, cause the UE (100) to: receive muting configuration information for setting at least one muting resource, receive downlink control information (DCI), and transmit an uplink signal based on the muting configuration information and the DCI. Here, the DCI may indicate a first muting resource to be applied to the uplink signal among the at least one muting resource through a TDRA (Time domain resource allocation) field.

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

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

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

[0305] Specifically, the processor (202) of the second wireless device or base station (200) controls the transceiver (206) or the RF transceiver to transmit muting configuration information for setting at least one muting resource, transmit downlink control information (DCI), and receive an uplink signal based on the muting configuration information and the DCI. Here, the DCI may indicate a first muting resource to be applied to the uplink signal among the at least one muting resource through a TDRA (Time domain resource allocation) field.

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

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

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

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

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

[0311] Figure 18 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.

[0312] Referring to FIG. 18, the wireless device (100, 200) corresponds to the wireless device (100, 200) of FIG. 17 and may be composed of various elements, components, units / units, and / or modules. For example, the wireless device (100, 200) may include a communication unit (110), a control unit (120), a memory unit (130), and additional elements (140). The communication unit may include a communication circuit (112) and a transceiver(s) (114). For example, the communication circuit (112) may include one or more processors (102, 202) and / or one or more memories (104, 204) of FIG. 18. For example, the transceiver(s) (114) may include one or more transceivers (106, 206) and / or one or more antennas (108, 208) of FIG. 17. 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).

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

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

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

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

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

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

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

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

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

Claims

1. In the method using UE (User Equipment), A step of receiving muting configuration information that sets at least one muting resource; A step of receiving DCI (downlink control information); and A step of transmitting an uplink signal based on the muting setting information and the DCI; A method wherein the DCI indicates a first muting resource to be applied to the uplink signal among the at least one muting resource through a TDRA (Time domain resource allocation) field.

2. In paragraph 1, The above TDRA field includes information about a time resource associated with a first muting resource among a plurality of time resources allocated for the uplink signal, A method, characterized in that the first muting resource is a frequency resource having an even index or a frequency resource having an odd index among frequency resources allocated to a time resource related to the first muting resource.

3. In paragraph 1 A method, characterized in that the first muting resource is not applied to the uplink signal based on the fact that the first muting resource overlaps with a resource for a DMRS (Demodulation Reference Signal) of the uplink signal.

4. In paragraph 1, A method characterized in that the UE determines that the first muting resource overlapping with a resource for a DMRS (Demodulation Reference Signal) of the uplink signal is invalid.

5. In paragraph 1, A method, characterized in that the first muting resource is not applied to the uplink signal based on the fact that the first muting resource overlaps with a resource for multiplexing UCI (Uplink control information) of the uplink signal.

6. In paragraph 1, A method characterized in that the UE multiplexes UCI (Uplink Control Information) to the uplink signal based on the number of resources allocated for the uplink signal minus the number of the first muting resources.

7. In paragraph 1, A method, characterized in that it further comprises a step of scheduling repetitive transmission of a plurality of uplink signals related to DMRS (Demodulation Reference Signal) bundling.

8. In paragraph 7, A method characterized in that the first uplink signal is transmitted including only DMRS based on the number of symbols remaining, excluding symbols of the first muting resource, in the first uplink signal to which the first muting resource is applied among the plurality of uplink signals being equal to or less than a preset number.

9. In paragraph 1, A step of receiving configuration information for a first time interval related to a sub-band full duplex (SBFD) or single frequency full duplex (SFFD) operation of a base station; further comprising; A method, characterized in that the first muting resource is valid only within the first time interval.

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

11. In UE (User Equipment), RF (Radio Frequency) transmitter and receiver; and A processor connected to the RF transceiver, The processor controls the RF transceiver to receive muting configuration information for setting at least one muting resource, receives downlink control information (DCI), and transmits an uplink signal based on the muting configuration information and the DCI. The above DCI indicates a first muting resource to be applied to the uplink signal among the at least one muting resource through a TDRA (Time domain resource allocation) field, UE.

12. In paragraph 11, The above TDRA field includes information about a time resource associated with a first muting resource among a plurality of time resources allocated for the uplink signal, A UE characterized in that the first muting resource is determined as frequency resources having an even index or frequency resources having an odd index among frequency resources allocated to time resources related to the first muting resource.

13. In a processing device that controls UE (User Equipment), at least one processor; and At least one memory connected to said at least one processor and storing instructions, said instructions being executed by said at least one processor, wherein said UE: Receive muting configuration information that sets at least one muting resource, receive DCI (downlink control information), and transmit an uplink signal based on the muting configuration information and the DCI, A processing device in which the DCI indicates a first muting resource to be applied to the uplink signal among the at least one muting resource through a TDRA (Time domain resource allocation) field.

14. In the method by the base station, A step of transmitting muting configuration information that sets at least one muting resource; A step of transmitting DCI (downlink control information); and A step of receiving an uplink signal based on the muting setting information and the DCI; A method wherein the DCI indicates a first muting resource to be applied to the uplink signal among the at least one muting resource through a TDRA (Time domain resource allocation) field.

15. At the base station, RF (Radio Frequency) transmitter and receiver; and A processor connected to the RF transceiver, The processor controls the RF transceiver to transmit muting configuration information that sets at least one muting resource, transmits DCI (downlink control information), and receives an uplink signal based on the muting configuration information and the DCI. A base station, wherein the DCI indicates a first muting resource to be applied to the uplink signal among the at least one muting resource through a TDRA (Time domain resource allocation) field.

Images