PDSCH transmission / reception method and apparatus in wireless communication system

Abstract

A method and apparatus for transmitting and receiving a PDSCH in a wireless communication system are disclosed. A method for receiving a multicast PDSCH according to an embodiment of the present disclosure may include receiving, from a base station, first configuration information associated with a PDSCH for a BWP and second configuration information associated with the multicast PDSCH for a CFR configured in the BWP, receiving, from the base station, DCI for scheduling the multicast PDSCH, and receiving, from the base station, the multicast PDSCH in the CFR based on the DCI.

Description

[Technical Field]

[0001] The present disclosure relates to wireless communication systems, and more particularly to a method and apparatus for transmitting and receiving a multicast physical downlink shared channel (PDSCH) in a wireless communication system. [Background technology]

[0002] Mobile communication systems were developed to provide voice services while ensuring user activity. However, the scope of mobile communication systems has expanded beyond voice to include data services, and the explosive growth in traffic is causing resource shortages. Users are also demanding faster services, so there is a demand for more advanced mobile communication systems.

[0003] The requirements for next-generation mobile communication systems are to accommodate large and explosive data traffic, dramatically increase the transmission rate per user, accommodate a significantly increased number of connected devices, support very low end-to-end latency, and high energy efficiency.To achieve this, various technologies are being researched, including dual connectivity, massive multiple input multiple output (MIMO), in-band full duplex, non-orthogonal multiple access (NOMA), super wideband support, and device networking. Summary of the Invention [Problem to be solved by the invention]

[0004] A technical problem of the present disclosure is to provide a method and apparatus for transmitting a multicast physical downlink shared channel (PDSCH).

[0005] A technical problem of the present disclosure is to provide a method and apparatus for rate match (RM) and / or channel state information-reference signal (CSI-RS) resource-related configuration / adaptation for transmission and reception of multicast PDSCH within a common frequency resource (CFR).

[0006] The technical problems to be solved by the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by a person having ordinary skill in the art to which the present disclosure pertains from the following description. [Means for solving the problem]

[0007] A method for receiving a multicast PDSCH (physical downlink shared channel) in a wireless communication system according to one embodiment of the present disclosure, the method being performed by a terminal, may include receiving, from a base station, first configuration information associated with a PDSCH for a frequency band part (BWP) and second configuration information associated with the multicast PDSCH for a common frequency resource (CFR) configured within the BWP, receiving, from the base station, downlink control information (DCI) for scheduling the multicast PDSCH, and receiving, from the base station, the multicast PDSCH within the CFR based on the DCI. The first configuration information includes information regarding one or more first rate match pattern groups, each of which includes one or more rate match patterns for resources that are not available for receiving a PDSCH; the second configuration information includes information regarding one or more second rate match pattern groups, each of which includes one or more rate match patterns for resources that are not available for receiving a PDSCH; and even if the CFR is configured within the BWP, only the one or more second rate match pattern groups may be indicated by the DCI to be applied to receiving the multicast PDSCH among the one or more first rate match pattern groups and the one or more second rate match pattern groups.

[0008] A method for transmitting a multicast PDSCH (physical downlink shared channel) in a wireless communication system according to another embodiment of the present disclosure, the method being performed by a base station, may include transmitting, to a terminal, first configuration information associated with a PDSCH for a frequency band part (BWP) and second configuration information associated with the multicast PDSCH for a common frequency resource (CFR) configured within the BWP, transmitting, to the terminal, downlink control information (DCI) for scheduling the multicast PDSCH, and transmitting, to the terminal, the multicast PDSCH within the CFR based on the DCI. The first configuration information includes information regarding one or more first rate match pattern groups, each of which includes one or more rate match patterns for resources that are not available for receiving a PDSCH; the second configuration information includes information regarding one or more second rate match pattern groups, each of which includes one or more rate match patterns for resources that are not available for receiving a PDSCH; and even if the CFR is configured within the BWP, only the one or more second rate match pattern groups may be indicated by the DCI to be applied to receiving the multicast PDSCH among the one or more first rate match pattern groups and the one or more second rate match pattern groups. [Effects of the Invention]

[0009] According to an embodiment of the present disclosure, multicast PDSCH transmission efficiency can be improved by transmitting and receiving multicast PDSCH based on rate match pattern configuration and CSI-RS resource configuration.

[0010] The effects obtained from the present disclosure are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those having ordinary skill in the art to which the present disclosure pertains from the following description. [Brief explanation of the drawings]

[0011] The accompanying drawings, which are included as part of the detailed description to aid in understanding the present disclosure, provide examples of the present disclosure and, together with the detailed description, explain the technical features of the present disclosure.

[0012] [Figure 1] 1 illustrates the structure of a wireless communication system to which the present disclosure can be applied.

[0013] [Figure 2] 1 illustrates an example of a frame structure in a wireless communication system to which the present disclosure can be applied.

[0014] [Figure 3] 1 illustrates an example of a resource grid in a wireless communication system to which the present disclosure can be applied.

[0015] [Figure 4] 1 illustrates an example of a physical resource block in a wireless communication system to which the present disclosure can be applied.

[0016] [Figure 5] 1 illustrates an example of a slot structure in a wireless communication system to which the present disclosure can be applied.

[0017] [Figure 6] 1 illustrates examples of physical channels used in a wireless communication system to which the present disclosure can be applied, and a general signal transmission / reception method using the physical channels.

[0018] [Figure 7] 1 illustrates a multiple TRP transmission method in a wireless communication system to which the present disclosure can be applied.

[0019] [Figure 8] 1 illustrates an example of a HARQ-ACK process for downlink data in a wireless communication system to which the present disclosure can be applied.

[0020] [Figure 9] 10 illustrates a HARQ-ACK transmission and reception procedure for a multicast PDSCH according to one embodiment of the present disclosure.

[0021] [Figure 10] 1 illustrates group-common PDCCH / PDSCH transmission and HARQ-ACK transmission in a wireless communication system to which the present disclosure can be applied.

[0022] [Figure 11] 1 illustrates a semi-persistent ZP CSI-RS resource set activation / deactivation MAC CE according to one embodiment of the present disclosure.

[0023] [Figure 12] 1 illustrates a PUCCH spatial relation Activation / Deactivation MAC CE according to one embodiment of the present disclosure.

[0024] [Figure 13] 10 illustrates an operation of a terminal with respect to a multicast PDSCH transmission / reception method according to an embodiment of the present disclosure.

[0025] [Figure 14] 10 illustrates an operation of a base station for a multicast PDSCH transmission / reception method according to an embodiment of the present disclosure.

[0026] [Figure 15] 1 illustrates a block diagram of a wireless communication device according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0027] Preferred embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. The detailed description disclosed below together with the accompanying drawings is intended to describe exemplary embodiments of the present disclosure and is not intended to represent the only embodiments in which the present disclosure can be implemented. The detailed description below includes specific details to provide a complete understanding of the present disclosure. However, it will be understood by those skilled in the art that the present disclosure can be implemented without such specific details.

[0028] In some cases, in order to avoid obscuring the concepts of the present disclosure, known structures and devices may be omitted or shown in block diagram form, focusing on the core functions of each structure and device.

[0029] In this disclosure, when a component is "coupled," "coupled," or "connected" to another component, this may include a direct connection, as well as an indirect connection where there is another component between them. Also, in this disclosure, the terms "comprise" or "have" specify the presence of stated features, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, elements, components, and / or groups thereof.

[0030] In this disclosure, terms such as "first" and "second" are used only to distinguish one component from another, not to limit the components, and do not limit the order or importance of the components unless otherwise specified. Therefore, within the scope of this disclosure, a first component in one embodiment may be referred to as a second component in another embodiment, and similarly, a second component in one embodiment may be referred to as a first component in another embodiment.

[0031] The terms used in this disclosure are for the purpose of describing particular embodiments and are not intended to limit the scope of the claims. As used in the description of the embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms unless the context clearly dictates otherwise. The term "and / or" used in this disclosure means that one of the associated listed items may be used, or that any and all possible combinations of two or more of them may be used. Also, in this disclosure, " / " between words has the same meaning as "and / or" unless otherwise specified.

[0032] The present disclosure is described with respect to a wireless communication network or a wireless communication system, and operations performed in a wireless communication network may be performed in the process in which a device (e.g., a base station) that manages the wireless communication network controls the network and transmits or receives signals, or in the process in which a terminal coupled to the wireless network transmits or receives signals to or from the network or between terminals.

[0033] In this disclosure, transmitting or receiving a channel includes transmitting or receiving information or signals on that channel. For example, transmitting a control channel means transmitting control information or signals on the control channel. Similarly, transmitting a data channel means transmitting data information or signals on the data channel.

[0034] Hereinafter, downlink (DL) refers to communication from a base station to a terminal, and uplink (UL) refers to communication from a terminal to a base station. In the downlink, a transmitter may be part of the base station, and a receiver may be part of the terminal. In the uplink, a transmitter may be part of the terminal, and a receiver may be part of the base station. The base station may be expressed as a first communication device, and the terminal may be expressed as a second communication device. A base station (BS) may be replaced with terms such as a fixed station, Node B, evolved-Node B (eNB), Next Generation Node B (gNB), base transceiver system (BTS), access point (AP), network (5G network), artificial intelligence (AI) system / module, road side unit (RSU), robot, unmanned aerial vehicle (UAV), augmented reality (AR) device, virtual reality (VR) device, etc. Furthermore, a terminal may be fixed or mobile, and may be replaced with terms such as UE (User Equipment), MS (Mobile Station), UT (user terminal), MSS (Mobile Subscriber Station), SS (Subscriber Station), AMS (Advanced Mobile Station), WT (Wireless terminal), MTC (Machine-Type Communication) device, M2M (Machine-to-Machine) device, D2D (Device-to-Device) device, vehicle, RSU (road side unit), robot, AI (Artificial Intelligence) module, drone (UAV: Unmanned Aerial Vehicle), AR (Augmented Reality) device, VR (Virtual Reality) device, etc.

[0035] The following technologies may be used for various wireless access systems, such as CDMA, FDMA, TDMA, OFDMA, SC-FDMA, etc. CDMA may be implemented by radio technologies such as Universal Terrestrial Radio Access (UTRA) and CDMA2000. TDMA may be implemented by radio technologies such as Global System for Mobile communications (GSM), General Packet Radio Service (GPRS), and Enhanced Data Rates for GSM Evolution (EDGE). OFDMA may be implemented by radio technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, Evolved UTRA (E-UTRA), etc. UTRA is part of the Universal Mobile Telecommunications System (UMTS). 3GPP (3rd Generation Partnership Project)® LTE (Long Term Evolution) is a part of E-UMTS (Evolved UMTS) that uses E-UTRA, and LTE-A (Advanced) / LTE-A pro is an evolved version of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an evolved version of 3GPP LTE / LTE-A / LTE-A pro.

[0036] For clarity, the following description will be based on a 3GPP communication system (e.g., LTE-A, NR), but the technical concept of the present disclosure is not limited thereto. LTE refers to technology from 3GPP Technical Specification (TS) 36.xxx Release 8 onward. Specifically, LTE technology from 3GPP TS 36.xxx Release 10 onward is called LTE-A, and LTE technology from 3GPP TS 36.xxx Release 13 onward is called LTE-A pro. 3GPP NR refers to technology from TS 38.xxx Release 15 onward. LTE / NR may be referred to as a 3GPP system. "xxx" refers to the standard document detail number. LTE / NR may be referred to as a 3GPP system. For background technology, terms, abbreviations, etc. used in the description of the present disclosure, please refer to the matters described in standard documents published before the present disclosure. For example, the following documents may be referenced:

[0037] In 3GPP LTE, reference can be made to TS 36.211 (Physical channels and modulation), TS 36.212 (Multiplexing and channel coding), TS 36.213 (Physical layer procedures), TS 36.300 (General description), and TS 36.331 (Radio resource control).

[0038] For 3GPP NR, reference can be made to TS 38.211 (Physical Channels and Modulation), TS 38.212 (Multiplexing and Channel Coding), TS 38.213 (Physical Layer Procedures for Control), TS 38.214 (Physical Layer Procedures for Data), TS 38.300 (General Description of NR and NG-RAN (New Generation-Radio Access Network)), and TS 38.331 (Radio Resource Control Protocol Standard).

[0039] The terminology abbreviations that may be used in this disclosure are defined as follows:

[0040] - BM: Beam management

[0041] - CQI: Channel Quality Indicator

[0042] - CRI: Channel state information-reference signal resource indicator

[0043] - CSI: Channel State Information

[0044] - CSI-IM: Channel state information-interference measurement

[0045] - CSI-RS: Channel state information-reference signal

[0046] - DMRS: Demodulation Reference Signal

[0047] - FDM: Frequency Division Multiplexing

[0048] - FFT: Fast Fourier transform

[0049] - IFDMA: Interleaved frequency division multiple access

[0050] - IFFT: Inverse fast Fourier transform

[0051] - L1-RSRP: Layer 1 reference signal received power

[0052] - L1-RSRQ: Layer 1 reference signal received quality

[0053] - MAC: Medium Access Control

[0054] - NZP: Non-zero power

[0055] - OFDM: Orthogonal frequency division multiplexing

[0056] - PDCCH: Physical downlink control channel

[0057] - PDSCH: Physical downlink shared channel

[0058] - PMI: Precoding matrix indicator

[0059] - RE: resource element

[0060] - RI: Rank indicator

[0061] - RRC: Radio resource control

[0062] - RSSI: received signal strength indicator

[0063] - Rx: Reception

[0064] - QCL: quasi co-location

[0065] - SINR: Signal to interference and noise ratio

[0066] - SSB (or SS / PBCH block): Synchronization signal block (including primary synchronization signal (PSS), secondary synchronization signal (SSS), and physical broadcast channel (PBCH))

[0067] - TDM: time division multiplexing

[0068] - TRP: transmission and reception point

[0069] - TRS: Tracking reference signal

[0070] - Tx: transmission

[0071] - UE: User equipment

[0072] - ZP: Zero power

[0073] System in general

[0074] As more communication devices require greater communication capacity, there is a growing need for improved mobile broadband communication compared to existing radio access technologies (RATs). Massive Machine Type Communications (MTC), which connects multiple devices and objects to provide a variety of services anytime, anywhere, is also one of the key issues being considered for next-generation communications. In addition, communication system designs that take into account reliability- and latency-sensitive services / terminals are also being discussed. Thus, the introduction of next-generation RATs that take into account technologies such as enhanced mobile broadband communication (eMBB), massive MTC (MMTC), and ultra-reliable and low latency communication (URLLC) is being discussed. For convenience, these technologies will be referred to as NR in this disclosure. NR is an example of a 5G RAT.

[0075] New RAT systems, including NR, use an OFDM transmission scheme or a similar transmission scheme. A new RAT system may follow OFDM parameters different from those of LTE. Alternatively, a new RAT system may follow the existing LTE / LTE-A numerology but support a larger system bandwidth (e.g., 100 MHz). Alternatively, one cell may support multiple numerologies. That is, terminals operating with different numerologies may coexist within one cell.

[0076] A numerology corresponds to a subcarrier spacing in the frequency domain. Different numerologies can be defined by scaling the reference subcarrier spacing by an integer N.

[0077] FIG. 1 illustrates the structure of a wireless communication system to which the present disclosure can be applied.

[0078] Referring to FIG. 1, the NG-RAN is composed of gNBs that provide the NG-RA (NG-Radio Access) user plane (i.e., new access stratum (AS) sublayer / Packet Data Convergence Protocol (PDCP) / Radio Link Control (RLC) / MAC / PHY) and control plane (RRC) protocol termination for the UE. The gNBs are interconnected via an Xn interface. The gNBs are also connected to an NGC (New Generation Core) via an NG interface. More specifically, the gNBs are connected to an AMF (Access and Mobility Management Function) via an N2 interface and to a UPF (User Plane Function) via an N3 interface.

[0079] FIG. 2 illustrates a frame structure in a wireless communication system to which the present disclosure can be applied.

[0080] An NR system can support multiple numerologies. Here, a numerology may be defined by subcarrier spacing and cyclic prefix (CP) overhead. In this case, multiple subcarrier spacings may be derived by scaling the base (reference) subcarrier spacing by an integer N (or μ). Furthermore, even if it is assumed that very low subcarrier spacings are not used at very high carrier frequencies, the numerology used may be selected independently of the frequency band. Furthermore, an NR system may support various frame structures based on multiple numerologies.

[0081] The following describes OFDM numerologies and frame structures that can be considered in an NR system. A number of OFDM numerologies supported in an NR system may be defined as shown in Table 1 below.

[0082] [Table 1]

[0083] NR supports multiple numerologies (or subcarrier spacing (SCS)) to support various 5G services. For example, a 15 kHz SCS supports wide areas in traditional cellular bands, a 30 kHz / 60 kHz SCS supports dense urban areas, lower latency, and wider carrier bandwidths, and a 60 kHz or higher SCS supports bandwidths greater than 24.25 GHz to overcome phase noise.

[0084] The NR frequency band is defined as two types of frequency ranges (FR1 and FR2). FR1 and FR2 may be configured as shown in Table 2 below. FR2 may also refer to millimeter wave (mmW).

[0085] [Table 2]

[0086] In relation to the frame structure in an NR system, the size of the various fields in the time domain is T c =1 / (Δf max N f ) where Δf max =480 10 3 Hz and Nf = 4096. Downlink and uplink transmission is T f =1 / (Δf max N f / 100)·T c The radio frame is organized into radio frames each having a duration of T = 10 ms. sf =(Δf max N f / 1000)·T c In this case, there may be one set of frames for the uplink and one set of frames for the downlink. In addition, transmission from a terminal in uplink frame number i begins T TA =(N TA +N TA,offset )T c For a subcarrier spacing configuration μ, a slot is allocated within a subframe. s μ ∈{0,...,N slot subframe,μ -1}, and n s,f μ ∈{0,...,N slot frame,μ The slots are numbered in increasing order {N -1}. symb slot It consists of N consecutive OFDM symbols, symb slot is determined by the CP. s μ The start of OFDM symbol n s μ N symb slotNot all terminals can transmit and receive at the same time, which means that not all OFDM symbols in a downlink slot or uplink slot can be used.

[0087] Table 3 shows the number of OFDM symbols per slot (N symb slot ), the number of slots per radio frame (N slot frame,μ ), the number of slots per subframe (N slot subframe,μ ) and Table 4 shows the number of OFDM symbols per slot, the number of slots per radio frame, and the number of slots per subframe in the extended CP.

[0088] [Table 3]

[0089] [Table 4]

[0090] Figure 2 shows an example where μ = 2 (SCS is 60 kHz), and one subframe can include four slots as shown in Table 3. One subframe = {1, 2, 4} slots shown in Figure 2 is an example, and the number of slots that can be included in one subframe is defined as shown in Table 3 or Table 4. Also, a mini-slot can include 2, 4, or 7 symbols, or more or fewer symbols.

[0091] In relation to physical resources in an NR system, antenna ports, resource grids, resource elements, resource blocks, carrier parts, etc. may be considered. The physical resources that can be considered in an NR system will be specifically described below.

[0092] First, with respect to antenna ports, the antenna port is defined so that the channel on which symbols on the antenna port are carried can be inferred from the channel on which other symbols on the same antenna port are carried. If the large-scale properties of the channel on which symbols on one antenna port are carried can be inferred from the channel on which symbols on the other antenna port are carried, the two antenna ports are said to have a QC / QCL (quasi co-located or quasi co-location) relationship. Here, the large-scale properties include one or more of delay spread, Doppler spread, frequency shift, average received power, and received timing.

[0093] FIG. 3 illustrates a resource grid in a wireless communication system to which the present disclosure can be applied.

[0094] Referring to FIG. 3, the resource grid is divided into N RB μ N sc RB It consists of subcarriers, and one subframe is 14.2 μ In the NR system, a transmitted signal is composed of N OFDM symbols. RBμ N sc RB One or more resource grids consisting of subcarriers and two μ N symb (μ) OFDM symbols, where N RB μ ≦N RB max,μ The above N RB max,μ represents the maximum transmission bandwidth, which may vary not only depending on the numerology but also between the uplink and downlink. In this case, one resource grid may be configured for each μ and antenna port p. Each element of the resource grid for μ and antenna port p is called a resource element, and is represented by an index pair. JPEG0007737543000005.jpg9107, where k=0,...,N RB μ N sc RB -1 is the index in the frequency domain, JPEG0007737543000006.jpg10110,...,2 μ N symb (μ) -1 represents the position of the symbol within the subframe. When referring to resource elements in a slot, the index pair (k, l) is used, where l = 0,...,N symb μ μ and the resource element for antenna port p. JPEG0007737543000007.jpg9113 is a complex value JPEG0007737543000008.jpg1095. If there is no risk of confusion or if a specific antenna port or numerology is not specified, the indices p and μ may be dropped, so that the complex value is JPEG0007737543000009.jpg13100. Also, a resource block (RB) is N sc RB = 12 consecutive subcarriers.

[0095] Point A serves as a common reference point for the resource block grid and is obtained as follows:

[0096] - offsetToPointA for the primary cell (PCell) downlink indicates the frequency offset between point A and the lowest subcarrier of the lowest resource block that overlaps with the SS / PBCH block used by the terminal for initial cell selection. It is expressed in resource block units assuming 15 kHz subcarrier spacing for FR1 and 60 kHz subcarrier spacing for FR2.

[0097] - absoluteFrequencyPointA indicates the frequency-location of point A expressed as in ARFCN (absolute radio-frequency channel number).

[0098] Common resource blocks are numbered from 0 upwards in the frequency domain for a subcarrier spacing setting μ. The center of subcarrier 0 of common resource block 0 for a subcarrier spacing setting μ coincides with 'point A'. In the frequency domain, common resource block number n CRB μ The relationship between the resource elements (k, l) for the subcarrier spacing setting μ is given by the following equation 1.

[0099]

number

[0100] In Equation 1, k is defined relative to point A so that k=0 corresponds to the subcarrier centered at point A. The physical resource blocks are numbered from 0 to N within the bandwidth part (BWP). BWP,i size,μ Physical resource block n in BWP i is numbered from -1 to i. PRB and common resource block n CRB The relationship between is given by Equation 2 below.

[0101]

number

[0102] N BWP,i start,μ is the common resource block where the BWP starts relative to common resource block 0.

[0103] Fig. 4 illustrates a physical resource block in a wireless communication system to which the present disclosure can be applied, and Fig. 5 illustrates a slot structure in a wireless communication system to which the present disclosure can be applied.

[0104] 4 and 5, a slot includes multiple symbols in the time domain. For example, in the general CP, one slot includes seven symbols, while in the extended CP, one slot includes six symbols.

[0105] A carrier wave includes multiple subcarriers in the frequency domain. A resource block (RB) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A bandwidth part (BWP) is defined as multiple consecutive (physical) resource blocks in the frequency domain, and may correspond to one numerology (e.g., SCS, CP length, etc.). A carrier wave can include up to N (e.g., 5) BWPs. Data communication is performed using activated BWPs, and only one BWP may be activated for one terminal. Each element in the resource grid is called a resource element (RE), and one complex symbol may be mapped to it.

[0106] The NR system may support up to 400 MHz per component carrier (CC). If a terminal operating on such a wideband CC keeps the radio frequency (RF) chip for the entire CC on at all times, battery consumption may increase. Considering various application cases (e.g., eMBB, URLLC, MMTc, V2X, etc.) operating within a single wideband CC, different numerologies (e.g., subcarrier spacing, etc.) may be supported for each frequency band within the CC. Each terminal may have different capabilities for maximum bandwidth. In consideration of this, a base station may instruct a terminal to operate only with a portion of the bandwidth of a wideband CC, rather than the entire bandwidth. For convenience, this portion of the bandwidth is defined as a bandwidth part (BWP). A BWP may consist of contiguous RBs on the frequency axis and may correspond to one numerology (e.g., subcarrier spacing, CP length, slot / minislot duration).

[0107] Meanwhile, a base station can configure multiple BWPs within one CC configured for a terminal. For example, a BWP occupying a relatively small frequency region can be configured in a PDCCH monitoring slot, and the PDSCH indicated by the PDCCH can be scheduled on a larger BWP. Alternatively, when UEs are concentrated in a specific BWP, other BWPs can be configured for some terminals for load balancing. Alternatively, both BWPs can be configured within the same slot by excluding a portion of the spectrum from the entire bandwidth, taking into account frequency domain inter-cell interference cancellation between neighboring cells. That is, a base station can configure at least one DL / UL BWP for a terminal associated with a wideband CC. The base station can activate at least one DL / UL BWP configured at a specific time (through L1 signaling, MAC Control Element (CE), RRC signaling, etc.). In addition, the base station can instruct switching to another configured DL / UL BWP (by L1 signaling, MAC CE, RRC signaling, etc.). Alternatively, the base station may switch to a predetermined DL / UL BWP when a timer value expires on a timer basis. In this case, the activated DL / UL BWP is defined as an active DL / UL BWP. However, in situations where the UE is performing an initial access procedure or before an RRC connection is set up, the UE may not be able to receive the configuration for the DL / UL BWP. Therefore, the DL / UL BWP assumed by the UE in such a situation is defined as the initially active DL / UL BWP.

[0108] FIG. 6 illustrates examples of physical channels used in a wireless communication system to which the present disclosure can be applied, and a general signal transmission / reception method using the physical channels.

[0109] In a wireless communication system, a terminal receives information from a base station through a downlink and transmits information to the base station through an uplink. Information exchanged between the base station and the terminal includes data and various control information, and various physical channels exist depending on the type / purpose of the information exchanged.

[0110] When a terminal is powered on or newly enters a cell, it performs an initial cell search, such as synchronizing with a base station (S601). To do this, the terminal receives a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) from the base station to synchronize with the base station and acquire information such as a cell identifier (ID). The terminal then receives a physical broadcast channel (PBCH) from the base station to acquire broadcast information within the cell. Meanwhile, the terminal can receive a downlink reference signal (DL RS) during the initial cell search phase to check the downlink channel status.

[0111] After completing the initial cell search, the terminal receives a Physical Downlink Control Channel (PDCCH) and a Physical Downlink Shared Channel (PDSCH) based on the information carried on the PDCCH, thereby obtaining more specific system information (S602).

[0112] Meanwhile, when the terminal first connects to the base station or when there are no radio resources for signal transmission, the terminal can perform a random access procedure (RACH) with the base station (steps S603 to S606). To this end, the terminal transmits a specific sequence as a preamble on a physical random access channel (PRACH) (steps S603 and S605) and can receive a response message to the preamble on a PDCCH and a corresponding PDSCH (steps S604 and S606). In the case of a contention-based RACH, a contention resolution procedure can also be performed.

[0113] After performing the above-described procedures, the UE can then perform PDCCH / PDSCH reception (S607) and Physical Uplink Shared Channel (PUSCH) / Physical Uplink Control Channel (PUCCH) transmission (S608) as a general uplink / downlink signal transmission procedure. In particular, the UE receives downlink control information (DCI) through the PDCCH. Here, DCI includes control information such as resource allocation information for the UE, and its format varies depending on its purpose.

[0114] Meanwhile, control information that a terminal transmits to a base station on the uplink or that the terminal receives from a base station includes downlink / uplink ACK / NACK (Acknowledgement / Non-Acknowledgement) signals, CQI (Channel Quality Indicator), PMI (Precoding Matrix Indicator), RI (Rank Indicator), etc. In a 3GPP LTE system, a terminal can transmit the above-mentioned control information such as CQI / PMI / RI on a PUSCH and / or a PUCCH.

[0115] Table 5 shows an example of a DCI format in an NR system.

[0116] [Table 5]

[0117] Referring to Table 5, DCI formats 0_0, 0_1, and 0_2 may include resource information related to PUSCH scheduling (e.g., UL / SUL (Supplementary UL), frequency resource allocation, time resource allocation, frequency hopping, etc.), transport block (TB) related information (e.g., MCS (Modulation Coding and Scheme), NDI (New Data Indicator), RV (Redundancy Version), etc.), hybrid-automatic repeat and request (HARQ) related information (e.g., process number, DAI (Downlink Assignment Index), PDSCH-HARQ feedback timing, etc.), multiple antenna related information (e.g., DMRS sequence initialization information, antenna port, CSI request, etc.), and power control information (e.g., PUSCH power control, etc.), and the control information included in each DCI format may be predefined.

[0118] DCI format 0_0 is used for PUSCH scheduling in one cell. Information included in DCI format 0_0 is CRC (cyclic redundancy check) scrambled using a Cell Radio Network Temporary Identifier (C-RNTI), a Configured Scheduling RNTI (CS-RNTI), or a Modulation Coding Scheme Cell RNTI (MCS-C-RNTI) before being transmitted.

[0119] DCI format 0_1 ​​is used to indicate scheduling of one or more PUSCHs in one cell or downlink feedback information of configured grants (CGs) to a terminal. The information included in DCI format 0_1 ​​is CRC-scrambled using C-RNTI, CS-RNTI, SP-CSI-RNTI (Semi-Persistent CSI RNTI), or MCS-C-RNTI and then transmitted.

[0120] DCI format 0_2 is used for PUSCH scheduling in one cell. Information included in DCI format 0_2 is CRC scrambled using C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI and then transmitted.

[0121] Next, DCI formats 1_0, 1_1, and 1_2 may include resource information related to PDSCH scheduling (e.g., frequency resource allocation, time resource allocation, VRB (virtual resource block)-PRB (physical resource block) mapping, etc.), transmission block (TB) related information (e.g., MCS, NDI, RV, etc.), HARQ related information (e.g., process number, DAI, PDSCH-HARQ feedback timing, etc.), multiple antenna related information (e.g., antenna port, TCI (transmission configuration indicator), SRS (sounding reference signal) request, etc.), and PUCCH related information (e.g., PUCCH power control, PUCCH resource indicator, etc.), and the control information included in each DCI format may be pre-defined.

[0122] DCI format 1_0 is used for PDSCH scheduling in one DL cell. Information included in DCI format 1_0 is CRC scrambled using C-RNTI, CS-RNTI, or MCS-C-RNTI and then transmitted.

[0123] DCI format 1_1 is used for scheduling PDSCH in one cell. Information included in DCI format 1_1 is CRC scrambled using C-RNTI, CS-RNTI, or MCS-C-RNTI and then transmitted.

[0124] DCI format 1_2 is used for scheduling PDSCH in one cell. Information included in DCI format 1_2 is CRC scrambled using C-RNTI, CS-RNTI, or MCS-C-RNTI and then transmitted.

[0125] Quasi-Co Location (QCL)

[0126] Antenna ports are defined such that the channel on which symbols on an antenna port are carried can be inferred from the channel on which other symbols on the same antenna port are carried. Two antenna ports are said to be in a QC / QCL (quasi co-located or quasi co-located) relationship if the properties of the channel on which symbols on one antenna port are carried can be inferred from the channel on which symbols on the other antenna port are carried.

[0127] Here, the channel characteristics include one or more of delay spread, Doppler spread, frequency / Doppler shift, average received power, received timing / average delay, and spatial Rx parameter, where the spatial Rx parameter refers to a spatial (reception) channel characteristic parameter such as angle of arrival.

[0128] A terminal may be configured by a list of up to M TCI-State settings in the higher layer parameter PDSCH-Config to decode a PDSCH with a detected PDCCH having DCI intended for the terminal and a given serving cell, where M depends on the UE capability.

[0129] Each TCI-State contains parameters for setting quasi-co-location relationships between one or two DL reference signals and DM-RS ports of the PDSCH.

[0130] The quasi-co-location relationship is established by the higher layer parameters qcl-Type1 for the first DL RS and qcl-Type2 (if configured) for the second DL RS. For two DL RSs, the QCL types are not the same, regardless of whether the references are the same DL RS or different DL RSs.

[0131] The quasi co-location type corresponding to each DL RS is given by the higher layer parameter qcl-Type of QCL-Info and can take one of the following values:

[0132] - "QCL-TypeA":{Doppler shift,Doppler spread,average delay,delay spread}

[0133] - "QCL-TypeB":{Doppler shift,Doppler spread}

[0134] - "QCL-TypeC":{Doppler shift, average delay}

[0135] - "QCL-TypeD":{Spatial Rx parameter}

[0136] For example, if a target antenna port is a specific NZP CSI-RS, the NZP CSI-RS antenna port may be instructed / configured to be QCL-connected with a specific TRS from the perspective of QCL-Type A, and with a specific SSB from the perspective of QCL-Type D. A terminal receiving such instruction / configuration can receive the NZP CSI-RS using the Doppler and delay values ​​measured in the QCL-Type A TRS, and can apply the receive beam used for QCL-Type D SSB reception to receive the NZP CSI-RS.

[0137] The UE can receive an activation command via MAC CE signaling, which is used to map up to eight TCI states to codepoints in the DCI field "Transmission Configuration Indication."

[0138] Multi-TRP related operations

[0139] The Coordinated Multipoint (CoMP) technique is a method of effectively controlling interference by having multiple base stations mutually exchange (e.g., using the X2 interface) or utilize channel information (e.g., RI / CQI / PMI / LI (layer indicator)) fed back from terminals and then transmit coordinated data to the terminal. Depending on the method used, CoMP can be categorized into joint transmission (JT), coordinated scheduling (CS), coordinated beamforming (CB), dynamic point selection (DPS), dynamic point blocking (DPB), etc.

[0140] The M-TRP transmission method, in which M TRPs transmit data to one terminal, can be broadly divided into i) eMBB M-TRP transmission, which is a method for increasing the transmission rate, and ii) URLLC M-TRP transmission, which is a method for increasing the reception success rate and reducing latency.

[0141] In terms of DCI transmission, the M-TRP transmission method can be divided into i) M-DCI (multiple DCI)-based M-TRP transmission in which each TRP transmits different DCI, and ii) S-DCI (single DCI)-based M-TRP transmission in which one TRP transmits DCI. For example, in the case of S-DCI-based M-TRP transmission, all scheduling information for data transmitted by the M TRP needs to be transmitted to the UE in one DCI, and it can be used in an ideal backhaul (ideal BH) environment in which dynamic coordination between both TRPs is possible.

[0142] A UE can recognize PUSCHs (or PUCCHs) scheduled by DCIs received in different control resource sets (CORESETs) (or CORESETs belonging to different CORESET groups) as PUSCHs (or PUCCHs) transmitted in different TRPs or as PDSCHs (or PDCCHs) in different TRPs. In addition, the schemes for UL transmissions (e.g., PUSCHs / PUCCHs) transmitted in different TRPs, which will be described later, can also be applied to UL transmissions (e.g., PUSCHs / PUCCHs) transmitted in different panels belonging to the same TRP.

[0143] Hereinafter, a CORESET group identifier (group ID) described / mentioned in this disclosure may refer to an index / identification information (e.g., ID) for distinguishing a CORESET for each TRP / panel. A CORESET group may be a group / union of CORESETs distinguished by an index / identification information (e.g., ID) for distinguishing a CORESET for each TRP / panel / the CORESET group ID. As an example, a CORESET group ID may be specific index information defined in a CORESET configuration. In this case, a CORESET group may be set / indicated / defined by an index defined in a CORESET configuration for each CORESET. And / or a CORESET group ID may refer to an index / identification information / designator for distinguishing / identifying CORESETs set in / associated with each TRP / panel. Hereinafter, the CORESET group ID described / mentioned in the present disclosure may be expressed as a specific index / specific identification information / specific indicator for distinguishing / identifying between CORESETs set in / associated with each TRP / panel. The CORESET group ID, i.e., a specific index / specific identification information / specific indicator for distinguishing / identifying between CORESETs set in / associated with each TRP / panel, may be set / instructed to a terminal by higher layer signaling (e.g., RRC signaling), Layer 2 signaling (L2 signaling, e.g., MAC-CE), Layer 1 signaling (L1 signaling, e.g., DCI), etc. As an example, it may be set / instructed to perform PDCCH detection for each TRP / panel (i.e., for each TRP / panel belonging to the same CORESET group) in units of the CORESET group.And / or, it may be configured / instructed that uplink control information (e.g., CSI, HARQ-A / N (ACK / NACK), SR (scheduling request)) and / or uplink physical channel resources (e.g., PUCCH / PRACH / SRS resources) are separately managed / controlled for each TRP / panel (i.e., for each TRP / panel belonging to the same CORESET group) in the CORESET group unit. And / or, HARQ A / N (process / retransmission) for PDSCH / PUSCH, etc. scheduled for each TRP / panel (i.e., for each TRP / panel belonging to the same CORESET group) may be managed.

[0144] For example, a ControlResourceSet information element (IE), which is an upper layer parameter, is used to configure a time / frequency control resource set (CORESET). For example, the control resource set (CORESET) may be related to detection and reception of downlink control information. The ControlResourceSet IE may include a CORESET-related ID (e.g., controlResourceSetID), a CORESET pool index (e.g., CORESETPoolIndex) for the CORESET, a time / frequency resource configuration of the CORESET, TCI information related to the CORESET, etc. As an example, a CORESET pool index (e.g., CORESETPoolIndex) may be set to 0 or 1. In the above description, a CORESET group may correspond to a CORESET pool, and a CORESET group ID may correspond to a CORESET pool index (e.g., CORESETPoolIndex).

[0145] A method for improving reliability in multi-TRP will be described below.

[0146] The following two methods can be considered as transmission and reception methods for improving reliability using transmission with multiple TRPs.

[0147] FIG. 7 illustrates a multiple TRP transmission scheme in a wireless communication system to which the present disclosure is applicable.

[0148] 7A shows a case where layer groups transmitting the same codeword (CW) / transport block (TB) correspond to different TRPs. In this case, a layer group may refer to a predetermined layer set consisting of one or more layers. In this case, the number of layers increases the amount of transmission resources, which has the advantage of allowing robust channel coding with a low code rate to be used for the TB. In addition, since the channels are different from each other across the multiple TRPs, it is possible to expect improved reliability of the received signal based on diversity gain.

[0149] FIG. 7(b) shows an example in which different CWs are transmitted in layer groups corresponding to different TRPs. In this case, it can be assumed that the TBs corresponding to CW #1 and CW #2 in the figure are identical. That is, CW #1 and CW #2 mean that the same TB is converted into different CWs by channel coding, etc., according to different TRPs. Therefore, it can be considered an example of repeated transmission of the same TB. Compared to FIG. 7(a), FIG. 7(b) may have a disadvantage in that the code rate corresponding to the TB is higher. However, it has an advantage in that the code rate can be adjusted by specifying different redundancy version (RV) values ​​for encoded bits generated from the same TB according to the channel environment, or the modulation order of each CW can be adjusted.

[0150] According to the schemes illustrated in Figures 7(a) and 7(b), the same TB is repeatedly transmitted in different layer groups, and each layer group is transmitted by a different TRP / panel, thereby increasing the probability of data reception by the terminal. This is called an SDM (Spatial Division Multiplexing)-based M-TRP URLLC transmission scheme. Layers belonging to different layer groups are transmitted by DMRS ports belonging to different DMRS CDM groups.

[0151] Furthermore, although the above-mentioned contents related to multiple TRPs have been described based on the SDM (spatial division multiplexing) method using different layers, it is of course possible to extend and apply this to the FDM (frequency division multiplexing) method based on different frequency domain resources (e.g., RB / PRB (set), etc.) and / or the TDM (time division multiplexing) method based on different time domain resources (e.g., slots, symbols, sub-symbols, etc.).

[0152] A multi-TRP scheduled by at least one DCI may be performed as follows:

[0153] i) Scheme 1 (SDM): n (n is a natural number) TCI states in a single slot with overlapping time and frequency resource allocation

[0154] - Method 1a: Each transmission occasion is a layer or a set of layers of the same TB, and each layer or layer set is associated with one TCI and one set of DMRS ports. A single codeword with one redundancy version (RV) is used for all layers or layer sets. From the UE's perspective, different coded bits are mapped to different layers or layer sets according to a specific mapping rule.

[0155] - Approach 1b: Each transmission occasion is a layer or a set of layers of the same TB, and each layer or layer set is associated with one TCI and one set of DMRS ports. A single codeword with one RV is used for each spatial layer or layer set. The RVs corresponding to each spatial layer or layer set may be the same or different.

[0156] - Approach 1c: Each transmission opportunity is one layer of the same TB with one DMRS port associated with multiple TCI state indices, or one layer of the same TB with multiple DMRS ports associated with multiple TCI indices one by one.

[0157] In the above-mentioned methods 1a and 1c, the same MCS is applied to all layers or layer sets.

[0158] ii) Scheme 2 (FDM): n (n is a natural number) TCI states in a single slot with non-overlapping frequency resource allocations. Each non-overlapping frequency resource allocation is associated with one TCI state. The same single / multiple DMRS ports are associated with all non-overlapping frequency resource allocations.

[0159] - Method 2a: A single codeword with one RV is used across the entire resource allocation. From the UE perspective, a common RB mapping (layer mapping of the codeword) is applied across all resource allocations.

[0160] - Scheme 2b: A single codeword with one RV is used for each non-overlapping frequency resource allocation, and the RVs corresponding to each non-overlapping frequency resource allocation may be the same or different.

[0161] In scheme 2a, the same MCS is applied to all non-overlapping frequency resource allocations.

[0162] iii) Scheme 3 (TDM): n (n is a natural number) TCI states within a single slot with non-overlapping time resource allocation. Each transmission opportunity in the TB has one TCI and one RV with mini-slot time granularity. All transmission opportunities within a slot use a common MCS with the same single or multiple DMRS ports. The RV / TCI states may be the same or different across transmission opportunities.

[0163] iv) Scheme 4 (TDM): n (n is a natural number) TCI states in K (n<=K, K is a natural number) distinct slots. Each transmission opportunity in the TB has one TCI and one RV. All transmission opportunities across the K slots use a common MCS with the same single or multiple DMRS ports. The RV / TCI states may be the same or different across transmission opportunities.

[0164] Hereinafter, in this disclosure, DL MTRP-URLLC means that M-TRPs transmit the same data (e.g., transport block (TB)) / DCI using different layer / time / frequency resources. For example, TRP 1 transmits the same data / DCI using resource 1, and TRP 2 transmits the same data / DCI using resource 2. A UE configured with the DL MTRP-URLLC transmission method receives the same data / DCI using different layer / time / frequency resources. Herein, the UE may be instructed by the base station which QCL RS / type (i.e., DL TCI state) to use on the layer / time / frequency resource that receives the same data / DCI. For example, when the same data / DCI is received on resource 1 and resource 2, the DL TCI state to be used on resource 1 and the DL TCI state to be used on resource 2 are instructed. Since the UE receives the same data / DCI on resource 1 and resource 2, high reliability can be achieved. Such DL MTRP URLLC may be applied to the PDSCH / PDCCH.

[0165] Conversely, UL MTRP-URLLC means that M-TRPs receive the same data / UCI from a UE using different layer / time / frequency resources. For example, TRP 1 receives the same data / UCI from the UE using resource 1, and TRP 2 receives the same data / UCI from the UE using resource 2. The received data / UCI is then shared through a connected backhaul link between the TRPs. A UE configured with the UL MTRP-URLLC transmission scheme transmits the same data / UCI using different layer / time / frequency resources. Here, the UE receives instructions from the base station regarding which Tx beam and Tx power (i.e., UL TCI state) to use on the layer / time / frequency resource for transmitting the same data / UCI. For example, if the same data / UCI is transmitted on resource 1 and resource 2, the UE is instructed on the UL TCI state to be used on resource 1 and resource 2. Such UL MTRP URLLC may be applied to the PUSCH / PUCCH.

[0166] In the method proposed in this document, using (or mapping) a specific TCI state (or TCI) when receiving data / DCI / UCI for a certain frequency / time / space resource can mean, in DL, estimating a channel from a DMRS using a QCL type and QCL RS indicated by the TCI state in the frequency / time / space resource and receiving / demodulating the data / DCI using the estimated channel. In UL, it can mean transmitting / modulating the DMRS and data / UCI using a Tx beam and / or Tx power indicated by the TCI state in the frequency / time / space resource.

[0167] The UL TCI status includes Tx beam and / or Tx power information of the UE, and instead of the TCI status, spatial relation info or the like may be configured in the UE by other parameters. The UL TCI status may be directly indicated in the UL grant DCI, or may represent spatial relation info of the SRS resource indicated in the SRS resource indicator (SRI) field of the UL grant DCI. Alternatively, it may represent open-loop (OL) Tx power control parameters (j: index for open-loop parameters Po and alpha (maximum 32 parameter value sets per cell), q_d: index of DL RS for path loss (PL) measurement (maximum 3 measurements per cell), l: closed-loop power control process index (maximum 2 processes per cell)) linked to the value indicated in the SRI field of the UL grant DCI.

[0168] On the other hand, MTRP-eMBB means that the M-TRP transmits different data using different layers / time / frequencies, and a UE configured with the MTRP-eMBB transmission method is instructed to have various TCI states in the DCI, and it is assumed that the data received using the QCL RS for each TCI state is different from each other.

[0169] In addition, the UE can determine whether it is MTRP URLLC transmission / reception or MTRP eMBB transmission / reception by separately using the RNTI for MTRP-URLLC and the RNTI for MTRP-eMBB. That is, if the CRC of the DCI is masked using the RNTI for URLLC, it is determined to be URLLC transmission, and if the CRC of the DCI is masked using the RNTI for eMBB, it is determined to be eMBB transmission. Alternatively, the base station may configure the UE for MTRP URLLC transmission / reception or MTRP eMBB transmission / reception using other new signaling.

[0170] For convenience of explanation, this disclosure applies the proposed method assuming cooperative transmission / reception between two TRPs, but it can be extended to a multi-TRP environment of three or more, and also to a multi-panel environment. Different TRPs may be recognized by the UE as different TCI (Transmission Configuration Indication) states. That is, when a UE receives / transmits data / DCI / UCI using TCI state 1, it means that the UE receives / transmits data / DCI / UCI from / to TRP 1.

[0171] The proposals of the present disclosure may be utilized in situations where MTRPs cooperatively transmit PDCCHs (repeatedly transmit the same PDCCH or transmit it separately), and some proposals may also be utilized in situations where MTRPs cooperatively transmit PDSCHs or cooperatively receive PUSCHs / PUCCHs.

[0172] Furthermore, in the following description of the present disclosure, the term "multiple base stations (i.e., MTRPs) repeatedly transmitting the same PDCCH" may refer to the transmission of the same DCI using multiple PDCCH candidates, and is the same as the term "multiple base stations repeatedly transmitting the same DCI." The term "same DCI" may refer to two DCIs having the same DCI format / size / payload. Alternatively, two DCIs may be considered to be the same if they have different payloads but the same scheduling results. For example, the time domain resource allocation (TDRA) field of the DCI determines the slot / symbol positions of data and the slot / symbol positions of acknowledgement (ACK) and non-acknowledgement (NACK) relative to the time point at which the DCI is received. Here, if a DCI received at time n and a DCI received at time n+1 report the same scheduling results to a UE, the TDRA fields of the two DCIs will be different, and as a result, the DCI payloads will be different. The number of repetitions R may be directly instructed by the base station to the UE or may be mutually agreed upon. Alternatively, even if two DCIs have different payloads and not identical scheduling results, they can be considered the same DCI if the scheduling result of one DCI is a subset of the scheduling result of another DCI. For example, when identical data is time-division multiplexed and transmitted N times, DCI 1 received before the first data indicates N data repetitions, and DCI 2 received after the first data but before the second data indicates N-1 data repetitions. The scheduling data of DCI 2 is a subset of the scheduling data of DCI 1, and both DCIs are scheduled for the same data, so this case can also be considered the same DCI.

[0173] Furthermore, in the following description of the present disclosure, when multiple base stations (i.e., MTRPs) transmit the same PDCCH in separate transmissions, it means that one DCI is transmitted using one PDCCH candidate, with TRP1 transmitting some of the resources defined for that PDCCH candidate and TRP2 transmitting the remaining resources. For example, when TRP1 and TRP2 separately transmit PDCCH candidates corresponding to aggregation level m1+m2, the PDCCH candidates are separated into PDCCH candidate 1 corresponding to aggregation level m1 and PDCCH candidate 2 corresponding to aggregation level m2, and TRP1 transmits PDCCH candidate 1 and TRP2 transmit PDCCH candidate 2 using different time / frequency resources. After receiving PDCCH candidate 1 and PDCCH candidate 2, the UE generates PDCCH candidates corresponding to aggregation level m1+m2 and attempts DCI decoding.

[0174] When the same DCI is transmitted divided into multiple PDCCH candidates, there are two possible implementation methods.

[0175] First, the DCI payload (control information bits + CRC) may be encoded using a single channel encoder (e.g., a polar encoder), and the resulting coded bits may be transmitted separately by two TRPs. In this case, the coded bits transmitted by each TRP may encode the entire DCI payload, or only a portion of the DCI payload. Second, the DCI payload (control information bits + CRC) may be divided into two parts (DCI 1 and DCI 2), each of which may be encoded using a channel encoder (e.g., a polar encoder). Then, the two TRPs may transmit the coded bits corresponding to DCI 1 and DCI 2, respectively.

[0176] In short, multiple base stations (ie, MTRPs) may transmit the same PDCCH separately / repeatedly over multiple monitoring occasions (MOs) as follows.

[0177] i) It may mean repeatedly transmitting coded DCI bits obtained by encoding the entire DCI content of the PDCCH in each MO for each base station (i.e., STRP); or

[0178] ii) It may mean dividing the coded DCI bits obtained by encoding the entire DCI content of the PDCCH into multiple parts and transmitting different parts for each base station (i.e., STRP) in each MO; or

[0179] iii) This may mean dividing the DCI content of the corresponding PDCCH into multiple parts, separately encoding different parts for each base station (i.e., STRP), and transmitting them in each MO.

[0180] That is, regardless of whether the PDCCH is repeatedly transmitted or divided, it may be understood that the PDCCH is transmitted multiple times at multiple transmission times (TOs: transmission opportunities). Here, TO refers to a specific time / frequency resource unit in which the PDCCH is transmitted. For example, if the PDCCH is transmitted multiple times in slots 1, 2, 3, and 4 (in a specific resource block (RB)), TO may refer to each slot. If the PDCCH is transmitted multiple times in RB sets 1, 2, 3, and 4 (in a specific slot), TO may refer to each RB set. Alternatively, if the PDCCH is transmitted multiple times at different times and frequencies, TO may refer to each time / frequency resource. In addition, the TCI state used for DMRS channel estimation may be set differently for each TO, and TOs set with different TCI states may be assumed to be transmitted by different TRPs / panels. The repeated or divided transmission of the PDCCH by multiple base stations means that the PDCCH is transmitted in multiple TOs, and the union of the TCI states set in the TOs is composed of two or more TCI states. For example, if the PDCCH is transmitted in TOs 1, 2, 3, and 4, TCI states 1, 2, 3, and 4 may be set in TOs 1, 2, 3, and 4, respectively, which means that TRP i coordinates the PDCCH transmission in TO i.

[0181] For multiple TOs instructed to a UE for repeated or separate transmission of PDCCH / PDSCH / PUSCH / PUCCH, each TO is transmitted in the UL direction toward a specific TRP or received in the DL direction from a specific TRP. Here, a UL TO transmitted to TRP 1 (or a TO for TRP 1) refers to a TO using the first of two spatial relations, two UL TCIs, two UL power control parameters, and / or two path loss reference signals (PLRSs) instructed to the UE, and a UL TO transmitted to TRP 2 (or a TO for TRP 2) refers to a TO using the second of two spatial relations, two UL TCIs, two UL power control parameters, and / or two PLRSs instructed to the UE. Similarly, during DL transmission, the DL TO sent by TRP 1 (or the TO of TRP 1) means the TO using the first value of the two DL TCI states (e.g., when two TCI states are set in CORESET) instructed to the UE, and the DL TO sent by TRP 2 (or the TO of TRP 2) means the TO using the second value of the two DL TCI states (e.g., when two TCI states are set in CORESET) instructed to the UE.

[0182] The proposal of the present disclosure can be expanded and applied to various channels such as PUSCH / PUCCH / PDSCH / PDCCH.

[0183] The proposal of the present disclosure can be extended to both cases where the channel is repeatedly transmitted on different time / frequency / spatial resources and where it is separately transmitted.

[0184] Data transmission and HARQ (Hybrid Automatic Repeat and reQuest)-ACK (Acknowledgement) process

[0185] FIG. 8 illustrates a HARQ-ACK process for downlink data in a wireless communication system to which the present disclosure can be applied.

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

[0187] Frequency domain resource assignment: Indicates the RB resources (e.g., one or more (non-)contiguous RBs) allocated to the PDSCH.

[0188] - Time domain resource assignment: K0, indicating the starting position (e.g., OFDM symbol index) and length (e.g., number of OFDM symbols) of the PDSCH within the slot

[0189] - PDSCH HARQ feedback timing indicator (PDSCH-to-HARQ_feedback timing indicator): indicates K1

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

[0191] - PUCCH resource indicator (PRI): indicates the PUCCH resource used for UCI transmission among multiple PUCCH resources in the PUCCH resource set.

[0192] Thereafter, the UE receives the PDSCH at slot #(n+K0) according to the scheduling information of slot #n, and then transmits UCI via the PUCCH at slot #(n+K1). Here, the UCI includes a HARQ-ACK response for the PDSCH. If the PDSCH is configured to transmit up to one TB, the HARQ-ACK response may be configured as 1 bit. If the PDSCH is configured to transmit up to two TBs, the HARQ-ACK response may be configured as 2 bits if spatial bundling is not configured, or as 1 bit if spatial bundling is configured. If the HARQ-ACK transmission time for multiple PDSCHs is specified as slot #(n+K1), the UCI transmitted in slot #(n+K1) includes a HARQ-ACK response for multiple PDSCHs.

[0193] Multimedia Broadcast / Multicast Service (MBMS)

[0194] 3GPP MBMS is divided into two types: i) a single frequency network (SFN) scheme in which multiple base station cells synchronize and transmit the same data over a physical multicast channel (PMCH), and ii) a single cell point to multipoint (SC-PTM) scheme in which data is broadcast within the cell coverage area over a PDCCH / PDSCH channel. The SFN scheme is used to provide broadcast services over a wide area (e.g., an MBMS area) using semi-statically allocated resources, while the SC-PTM scheme is mainly used to provide broadcast services only within the cell coverage area using dynamic resources.

[0195] The SC-PTM provides one logical channel, the Single Cell Multicast Control Channel (SC-MCCH), and one or more logical channels, the Single Cell Multicast Traffic Channel (SC-MTCH). These logical channels are mapped to the downlink shared channel (DL-SCH), which is a transport channel, and the PDSCH, which is a physical channel. The PDSCH transmitting the SC-MCCH or SC-MTCH data is scheduled via a PDCCH indicated by a group-RNTI (G-RNTI). In this case, a temporary multicast group ID (TMGI) corresponding to a service identity (ID) may be one-to-one mapped to a specific G-RNTI value. Therefore, when a base station provides multiple services, multiple G-RNTI values ​​may be assigned for SC-PTM transmission. One or more terminals can perform PDCCH monitoring using a specific G-RNTI to receive a specific service. Here, a DRX on-duration period dedicated to SC-PTM can be set for a specific service / specific G-RNTI. In this case, these terminals wake up only during the specific on-duration period and perform PDCCH monitoring for the G-RNTI.

[0196] Type 3 HARQ-ACK codebook support method for multicast transmission

[0197] - PUCCH: Physical Uplink Control Channel

[0198] - PUSCH: Physical Uplink Shared Channel

[0199] - MCCH: Multicast Control Channel

[0200] - MTCH: Multicast Traffic Channel

[0201] - RRM: Radio resource management

[0202] - RLM: Radio link monitoring

[0203] - SCS: Sub-carrier spacing

[0204] - RLM: Radio link monitoring

[0205] - DCI: Downlink Control Information

[0206] - CAP: Channel Access Procedure

[0207] - Ucell: Unlicensed cell

[0208] - PCell: Primary Cell

[0209] - PSCell: Primary SCG Cell

[0210] - TBS: Transport Block Size

[0211] - TDRA: Time Domain Resource Allocation

[0212] SLIV: Starting and Length Indicator Value (an indication value for the starting symbol index and number of symbols in a PDSCH and / or PUSCH slot. May be set as a component of an entry constituting a TDRA field in a PDCCH scheduling the PDSCH and / or PUSCH.)

[0213] BWP: Bandwidth Part (may be composed of contiguous resource blocks (RBs) on the frequency axis. It may correspond to one numerology (e.g., SCS, CP length, slot / mini-slot duration, etc.). In addition, multiple BWPs may be configured on one carrier (the number of BWPs per carrier may also be limited), but the number of activated BWPs per carrier may be limited to a portion (e.g., 1).

[0214] CORESET: Control resource set (means a time-frequency resource region in which PDCCH can be transmitted, and the number of CORESETs per BWP may be limited).

[0215] - REG: Resource element group

[0216] - SFI: Slot Format Indicator (an indicator indicating the symbol level DL / UL direction within a specific slot, transmitted on a group common PDCCH)

[0217] - COT: Channel occupancy time

[0218] - SPS: Semi-persistent scheduling

[0219] - QCL: Quasi-Co-Location (QCL relationship between two reference signals (RSs)) means that QCL parameters such as Doppler shift, Doppler spread, average delay, delay spread, and spatial Rx parameter obtained from one RS can also be applied to the other RS ​​(or antenna port of the RS). In the NR system, four QCL types are defined as follows: "type A": {Doppler shift, Doppler spread, average delay, delay spread}, "type B": {Doppler shift, Doppler spread}, "type C": {Doppler shift, average delay}, and "type D": {Spatial Rx parameter}. For a given DL RS antenna port, the first DL RS is set as a reference for QCL type X (X = A, B, C, or D), and the second DL RS is set as a reference for QCL type X (X = A, B, C, or D). RS may be set as a reference to QCL type Y (Y=A, B, C, or D, where X≠Y).

[0220] -TCI: Transmission Configuration Indication (One TCI state includes the QCL relationship between one or more DL RSs, such as the DM-RS port of the PDSCH, the DM-RS port of the PDCCH, or the CSI-RS port of the CSI-RS resource. For the 'Transmission Configuration Indication' field in the DCI that schedules the PDSCH, the TCI state index corresponding to each code point constituting the field is activated by a MAC control element (CE), and the TCI state setting for each TCI state index is configured by RRC signaling. In the Rel-16 NR system, the TCI state is configured between DL RSs, but in future releases, configuration between DL RSs and UL RSs or between UL RSs and UL RSs may be allowed. Examples of UL RSs include SRS, PUSCH DM-RS, and PUCCH DM-RS.)

[0221] - SRI: SRS resource indicator (Indicates one of the SRS resource index values ​​set in the 'SRS resource indicator' field in the DCI that schedules the PUSCH. When transmitting the PUSCH, the UE may transmit the PUSCH using the same spatial domain transmission filter as used for transmitting and receiving a reference signal associated with the SRS resource. Here, the reference RS is set by RRC signaling according to the SRS spatial relationship information (SRS-SpatialRelationInfo) parameter for each SRS resource, and the SS / PBCH block, CSI-RS, or SRS may be set as the reference RS.)

[0222] - TRP: Transmission and Reception Point

[0223] - PLMN ID: Public Land Mobile Network identifier

[0224] - RACH: Random Access Channel

[0225] - RAR: Random Access Response

[0226] - Msg3: C-RNTI MAC CE or CCCH (common control channel) service data unit (SDU) transmitted via the uplink shared channel (UL-SCH) and provided by a higher layer. This message is associated with the UE Contention Resolution Identity as part of the random access procedure.

[0227] Special Cell: In dual connectivity operation, the term special cell refers to a PCell of a master cell group (MCG) or a PSCell of a secondary cell group (SCG), depending on whether the MAC entity is associated with the MCG or SCG, respectively. Alternatively, the term special cell refers to a PCell. A special cell supports PUCCH transmission and contention-based random access and is always activated.

[0228] - Serving Cell: Includes PCell, PSCell, and SCell (secondary cell).

[0229] - CG: Configured Grant

[0230] - Type 1 CG or Type 2 CG: Type 1 configured grant or Type 2 configured grant

[0231] - Fall-back DCI: Indicates a DCI format available for fallback operation, for example, DCI format 0_0, 1_0.

[0232] - Non-fallback DCI: This refers to a DCI format other than the fallback DCI, such as DCI format 0_1 ​​and 1_1.

[0233] - SS: Search space

[0234] - FDRA: Frequency domain resource allocation

[0235] - TDRA: Time Domain Resource Allocation

[0236] - LP, HP: Low(er) priority, High(er) priority

[0237] A / N for cell A: A / N (acknowledgement / negative acknowledgment) information for data (e.g., PDSCH) received in cell A

[0238] - UL CI: Uplink cancelation indication

[0239] - CFR: Common frequency resource for MBS (multicast and broadcast service). One DL CFR provides a group common PDCCH and group common PDSCH transmission resource for MBS transmission and reception. One UL CFR provides a HARQ-ACK PUCCH resource for group common PDSCH reception. One CFR is one MBS specific BWP or one UE specific BWP. Alternatively, one or more CFRs may be configured within one UE specific BWP. One CFR has a connection relationship with one UE specific BWP.

[0240] - TMGI: Temporary Mobile Group Identity, an MBS service identifier that indicates a specific service.

[0241] - G-RNTI: Group Radio Network Temporary Identifier, which represents the identifier of a group of terminals receiving the MBS.

[0242] The above-mentioned contents (3GPP system, frame structure, NR system, etc.) may be applied in combination with the method proposed in this disclosure described below, or may help clarify the technical features of the method proposed in this disclosure. In this disclosure, " / " means "and," "or," or "and / or," depending on the context.

[0243] In the prior art, a base station can configure a terminal-dedicated SPS configuration for a specific terminal and allocate downlink SPS transmission resources that are repeated at a set period. Here, a DCI of a terminal-dedicated PDCCH can indicate SPS activation for a specific SPS configuration index, allowing the terminal to repeatedly receive the SPS transmission resources at a set period. Such SPS transmission resources are used for initial hybrid automatic repeat request (HARQ) transmission, and the base station can allocate retransmission resources for a specific SPS configuration index using the DCI of the terminal-dedicated PDCCH. For example, if the terminal reports a HARQ NACK for the SPS transmission resource, the base station can allocate retransmission resources using the DCI to enable the terminal to receive downlink retransmission. In addition, the DCI of the terminal-dedicated PDCCH can indicate deactivation (SPS release or SPS deactivation) for a specific SPS configuration index, and the terminal receiving this does not receive the indicated SPS transmission resource. Here, a cyclic redundancy check (CRC) of the DCI for activation / retransmission / deactivation of the SPS is scrambled with a configured scheduling-RNTI (CS-RNTI).

[0244] Rel-17 NR aims to introduce a DL broadcast or DL ​​multicast transmission method to support Multicast Broadcast Service (MBMS) services similar to LTE MBMS. A base station provides a point-to-multipoint (PTM) transmission method and / or a point-to-point (PTP) transmission method for DL ​​broadcast or DL ​​multicast transmission.

[0245] In the PTM transmission method for MBS, a base station transmits a group common PDCCH and a group common PDSCH to multiple terminals, and the multiple terminals simultaneously receive the same group common PDCCH and group common PDSCH transmissions and decode the same MBS data.

[0246] Meanwhile, in the PTP transmission method for MBS, a base station transmits a terminal-dedicated PDCCH and a terminal-dedicated PDSCH to a specific terminal, and only the terminal receives the terminal-dedicated PDCCH and the terminal-dedicated PDSCH. Here, when there are multiple terminals receiving the same MBS service, the base station transmits the same MBS data to each terminal individually via different terminal-dedicated PDCCHs and terminal-dedicated PDSCHs. That is, the same MBS data is provided to multiple terminals, but different channels (i.e., PDCCHs and PDCCHs) are used for each terminal.

[0247] As described above, in the PTM transmission scheme, a base station transmits multiple group-common PDSCHs to multiple terminals, and the base station can receive HARQ-ACKs from the multiple terminals for the group-common PDSCHs using terminal-dedicated PUCCH resources.

[0248] Here, if a TB (Transport Block) for a multicast PDSCH (or a group common PDSCH) is successfully decoded, the UE transmits ACK as HARQ-ACK information. On the other hand, if a TB (Transport Block) cannot be successfully decoded, the UE transmits NACK as HARQ-ACK information. Such a HARQ-ACK transmission method is called an ACK / NACK-based HARQ-ACK method (mode). Generally, a UE can transmit ACK / NACK-based HARQ-ACK using a UE-dedicated PUCCH resource.

[0249] On the other hand, when a NACK only based HARQ-ACK method (mode) is configured for a multicast PDSCH (or a group-common PDSCH), the terminal does not transmit a PUCCH in the case of an ACK, but transmits a PUCCH only in the case of a NACK. Here, the PUCCH may transmit only a NACK as HARQ-ACK information using a group-common PUCCH resource.

[0250] Hereinafter, in this disclosure, a DCI format (or PDCCH) that schedules reception of a PDSCH carrying an MBS service (i.e., an MBS TB) may be referred to as an MBS DCI format (or PDCCH) or a multicast DCI format (or PDCCH). For example, a DCI format (or PDCCH) that includes a CRC scrambled by a G-RNTI (group-RNTI) or G-CS-RNTI (group-configured scheduling-RNTI) that schedules reception of a PDSCH may be referred to as an MBS DCI format (or PDCCH) or a multicast DCI format (or PDCCH). Herein, unless otherwise specified in this disclosure, the MBS DCI format (or PDCCH) or multicast DCI format (or PDCCH) may include both a group-common DCI format (or PDCCH) based on the PTM scheme for MBS and a UE-specific DCI format (or PDCCH) based on the PTP scheme for MBS.

[0251] Furthermore, unless otherwise specified in the present disclosure (e.g., the distinction between PDSCHs using dynamic scheduling and PDSCHs using SPS), PDSCHs scheduled using an MBS DCI format (or PDCCH) or a multicast DCI format (or PDCCH) (also, PDSCHs scheduled using a UE-specific DCI format (or PDCCH) using the PTP method) and group-common SPS PDSCHs may be collectively referred to as MBS PDSCHs or multicast PDSCHs. In other words, unless otherwise specified in the present disclosure, MBS PDSCHs or multicast PDSCHs may include both a group-common PDSCH using the PTM method for MBS and a UE-specific PDSCH using the PTP method for MBS.

[0252] Furthermore, HARQ-ACK information associated with a multicast (or MBS) DCI format (or PDCCH) or a multicast PDSCH may be referred to as MBS HARQ-ACK information or multicast HARQ-ACK information. Unless otherwise specified in the present disclosure, such MBS HARQ-ACK information or multicast HARQ-ACK information may be transmitted via a UE-specific PUCCH / PUSCH in accordance with the PTP / PTM scheme, or may be transmitted via a group-common PUCCH / PUSCH in accordance with the PTM scheme.

[0253] Furthermore, unless otherwise specified in this disclosure (for example, the distinction between PDSCH by dynamic scheduling and PDSCH by SPS), the PDSCH scheduled by the unicast DCI format (or PDCCH) and the UE-specific SPS PDSCH may be collectively referred to as the unicast / UE-specific PDSCH.

[0254] In addition, in the present disclosure, if a TB (Transport Block) for an MBS PDSCH or a multicast PDSCH is successfully decoded, the UE can transmit an ACK as HARQ-ACK information. On the other hand, if a TB for an MBS PDSCH or a multicast PDSCH is not successfully decoded, the UE can transmit a NACK as HARQ-ACK information. This HARQ-ACK transmission method is called an ACK / NACK-based HARQ-ACK method (mode).

[0255] Meanwhile, if the TB for the MBS PDSCH or the multicast PDSCH is successfully decoded, the UE does not need to transmit HARQ-ACK information (i.e., ACK) via the PUCCH (or PUSCH). On the other hand, if the TB for the MBS PDSCH or the multicast PDSCH is not successfully decoded, the UE may transmit a NACK as the HARQ-ACK information. Such a HARQ-ACK transmission scheme is called a NACK-based HARQ-ACK scheme (mode). In other words, when the NACK-only based HARQ-ACK scheme (mode) is configured, the UE does not transmit a PUCCH (or PUSCH) if there is an ACK, but can transmit a PUCCH (or PUSCH) only if there is a NACK.

[0256] In addition, in this disclosure, the terms subslot, minislot, and symbol slot all refer to time units smaller than one slot, and unless otherwise clearly distinguished and described in this disclosure, they may all be interpreted as having the same meaning. Furthermore, all of these terms may be considered / interpreted as one or more symbols within a slot.

[0257] FIG. 9 illustrates a HARQ-ACK transmission and reception procedure for a multicast PDSCH according to one embodiment of the present disclosure.

[0258] FIG. 9(a) illustrates a signaling procedure between UE1 and a base station (gNB) (beam / TRP 1), and FIG. 9(b) illustrates a signaling procedure between UE2 and a base station (gNB) (beam / TRP 2). Also, FIG. 9(a) illustrates a case where there is no PDSCH retransmission, and FIG. 9(b) illustrates a case where there is PDSCH retransmission. For convenience of explanation, FIG. 9 illustrates two procedures together, but the present invention is not limited thereto. That is, UE1 and UE2 are not limited to connecting to the same base station (via different beams / TRPs), and the two procedures are not limited to proceeding together. In other words, FIG. 9(a) and FIG. 9(b) are separate procedures, but are shown together for convenience of explanation, and common steps are described in common.

[0259] 1. Although not shown in FIG. 9, (before the procedure of FIG. 9) the UE enters RRC_CONNECTED mode and can send a message / information to the base station indicating one or more interested MBS services.

[0260] A. The message / information may be transmitted by any one of uplink control information (UCI), a MAC control element (CE), and an RRC message.

[0261] B. The MBS service of interest in the message / information may refer to one of the TMGI or G-RNTI included in the DL message received from the base station.

[0262] For example, the DL message may be a service availability message including TMGI#1, TMGI#3, TMGI#5, and TMGI#10. If the UE is interested in TMGI#5, the UE can indicate the order of TMGI#5 in the message / information. That is, the UE can report "3" to the base station.

[0263] As another example, the DL message may be a service availability message including G-RNTI#1, G-RNTI#3, G-RNTI#5, and G-RNTI#10. If the UE is interested in G-RNTI#10, the UE may indicate the order of G-RNTI#10 in the message / information. That is, the UE may report "4" to the base station.

[0264] 2. Upon receiving the message / information, the base station can transmit at least one of the following to the UE via an RRC message (S901a, S901b): i) a common frequency resource (CFR) configuration; ii) one or more group common PDSCH configurations including TCI states for one or more G-RNTI values; and iii) a search space (SS) configuration including TCI states for one or more G-RNTI values.

[0265] Although FIG. 9 illustrates one RRC message as an example, the present invention is not limited to this, and the configurations i) to iii) may be provided to the UE in different (or only partially identical) RRC messages.

[0266] A UE that receives an RRC message from a base station can configure one or more group-common PDSCHs (eg, group-common SPS PDSCHs) via the RRC message.

[0267] A. The RRC message may be a group-common message transmitted on a PTM MCCH (Multicast Control Channel) or a UE-specific message transmitted on a UE-specific DCCH (Dedicated Control Channel).

[0268] B. The UE may be configured with at least a G-RNTI value for each MBS CFR or each serving cell, or may additionally be configured with a group common-configured scheduling-RNTI (GC-CS-RNTI), which may be used for activating, retransmitting, or deactivating one or more group common SPS configurations.

[0269] - If the UE does not configure a GC-CS-RNTI for a CFR or serving cell, and a CS-RNTI is configured for the CFR or serving cell, the UE may use the CS-RNTI to activate, retransmit, or deactivate one or more group-common SPS configurations.

[0270] The base station may associate a list of TMGIs or a list of G-RNTIs with one GC-CS-RNTI. In this case, the base station may provide the terminal with a list of TMGIs or a list of G-RNTIs associated with the GC-CS-RNTI value.

[0271] C. Each PDSCH configuration (eg, RRC parameter PDSCH-config) may include at least information elements (IEs) for multicast and / or broadcast as shown in Table 6 below.

[0272] Table 6 illustrates the PDSCH-Config IE used to configure the PDSCH parameters.

[0273] [Table 6]

[0274] Table 7 illustrates the description of the fields of PDSCH-config in FIG. 6 above.

[0275] [Table 7-1] [Table 7-2]

[0276] 3. Once the search space (SS) for the configured CFR is configured, the UE monitors the PDCCH on the configured SS within the configured CFR to receive DCI whose CRC is scrambled with the G-RNTI or G-CS-RNTI (S902a, S902b).

[0277] 4. If a data unit is available on the Multicast Traffic Channel (MTCH) of the multicast radio bearer (MRB) for the MBS service, the base station constructs and transmits a transport block (TB) including a data unit for an SPS PDSCH opportunity associated with i) the MTCH of the MRB for the MBS service, ii) the TMGI of the MBS service, iii) the short ID of the MBS service, or iv) the G-RNTI mapped to the MBS service, according to service-to-resource mapping.

[0278] In the group-wide dynamic scheduling of TB, the base station transmits DCI to the UE on the PDCCH (S903a, S903b).

[0279] Here, the CRC of the DCI may be scrambled by the G-RNTI, G-CS-RNTI, or CS-RNTI, and the PDCCH may be a group-common PDCCH or a UE-specific PDCCH.

[0280] FIG. 9 illustrates a case where a group common DCI with a scrambled CRC attached (included) in G-RNTI#1 is transmitted and repetition=3.

[0281] The DCI may include the following information (fields):

[0282] - Identifier for DCI formats: This field can indicate an MBS-specific DCI format or one of the existing DCI formats for the MBS.

[0283] - Carrier indicator: This information (field) indicates the (serving or MBS-specific) cell of the CFR in which the group-common PDCCH / PDSCH is transmitted or the serving cell of the active BWP of the UE associated with the CFR.

[0284] - Bandwidth part indicator: This information (field) indicates the BWP ID assigned to the CFR in which the group common PDCCH / PDSCH is transmitted or the BWP ID of the active BWP of the UE associated with the CFR.

[0285] In addition, the DCI may include a frequency domain resource assignment, a time domain resource assignment, a VRB-to-PRB mapping, a PRB bundling size indicator, a rate matching indicator, a ZP CSI-RS trigger, a modulation and coding scheme, a new data indicator (NDI), a redundancy version, a HARQ process number, a downlink assignment index, a transmit power control (TPC) command for scheduled PUCCH, a PUCCH resource indicator (PRI), a PDSCH-to-HARQ_feedback timing indicator, an antenna port ...UCCH resource indicator (PRI), a PDSCH-to-HARQ_feedback timing indicator, an antenna port, a PUCCH resource indicator (PRI), a PUCCH resource indicator (PRI), a PDSCH-to-HARQ_feedback timing indicator, an antenna port, a PUCCH resource indicator (PRI), a PUCCH resource indicator (PRI), a PDSCH-to-HARQ_feedback The information may include information about the port(s), transmission configuration indication (TCI), SRS request, DMRS sequence initialization, and priority indicator.

[0286] In group-common dynamic scheduling, the base station can provide the UE with one or more of the following service-to-resource mappings for the MBS service identified by the TMGI, G-RNTI, or GC-CS-RNTI via i) a group-common or UE-specific RRC message, or ii) a group-common or UE-specific MAC CE. Data for the MBS service may be carried through an MBS Radio Bearer (MRB) of an MTCH associated with the MBS service, which is a multicast traffic logical channel. The RRC message may be a group-common message transmitted through a PTM Multicast Control Channel (MCCH) or a UE-dedicated message transmitted through a UE-specific Dedicated Control Channel (DCCH). The DCI scheduling the PDSCH carrying MBS service data may also indicate one or more of a short ID, MTCH ID, MRB ID, G-RNTI value, and TMGI value for the MBS service.

[0287] 5. When the UE receives a DCI whose CRC is scrambled by the G-RNTI that it is interested in receiving, based on i) the mapping between the MBS service and the HARQ process number (HPN) indicated in the DCI, and / or ii) (if available) the mapping between the MBS service and the short ID indicated in the DCI, the UE can determine the MBS service associated with one or more of the short ID, MTCH ID, MRB ID, G-RNTI value, and TMGI value for each PDSCH occasion.

[0288] The base station transmits a PDSCH carrying the MBS service data to the UE (S904a, S904b) (Figure 9 illustrates the case where MBS service data mapped to G-RNTI#1 is transmitted), and if the UE is interested in the determined MBS service, it can receive the PDSCH transmission scheduled by the DCI (S905a, S905b).

[0289] On the other hand, unlike the example of FIG. 9, if the UE is not interested in the determined MBS service, the UE does not need to receive the PDSCH transmission scheduled by the DCI.

[0290] Then, depending on the decoding status of the PDSCH transmission, the UE sends HARQ feedback to the base station.

[0291] 6. A UE that receives a group-common DCI indicating PUCCH resources for MBS HARQ-ACK can transmit HARQ-ACK to the base station via PUCCH after receiving the PDSCH scheduled by the DCI (S906a) as follows:

[0292] In A.PTM method 1, the group-common DCI can indicate at least a single PUCCH resource indicator (PRI) and a single PDSCH-to-HARQ_feedback timing indicator (K1) for ACK / NACK-based HARQ-ACK.

[0293] B. In UE-specific PUCCH resource allocation for ACK / NACK-based HARQ-ACK for group-common DCI, different UEs in a group may be configured with at least other values ​​of PUCCH resources and candidate DL data-UL ACK (e.g., dl-DataToUL-ACK) in the UE-dedicated PUCCH configuration (e.g., PUCCH-config) for multicast or for unicast (if PUCCH-config for multicast is not configured).

[0294] Different PUCCH resources may be allocated to different UEs according to the same PUCCH resource indicator (PRI) and the same PDSCH-to-HARQ_feedback timing indicator (K1) of the group-common DCI.

[0295] C. In PTP retransmission, the PUCCH resource indicator (PRI) and PDSCH-to-HARQ_feedback timing indicator (K1) in the UE-specific DCI may be analyzed based on the PUCCH configuration for unicast (e.g., PUCCH-config), regardless of whether the PUCCH configuration for multicast (e.g., PUCCH-config) is configured or not.

[0296] D. PRI (PUCCH Resource Indicator) may be indicated by group common DCI as follows.

[0297] 1) Option 1A-1: A list of UE-specific PRIs may be included in the DCI.

[0298] Each PRI in the list can point to an entry corresponding to a candidate PUCCH resource ID (e.g., pucch-ResourceId) value in a PUCCH configuration (e.g., PUCCH-config) for the same or different PUCCH resource allocation for other UEs in the group that receive the same DCI. Other PRIs in the DCI can point to other entries in the PUCCH configuration (e.g., PUCCH-config).

[0299] - The candidate PUCCH resource ID (e.g., pucch-ResourceId) value is configured by higher layers (e.g., RRC), and other PUCCH resource ID (e.g., pucch-ResourceId) values ​​may be configured for other UEs of the same group at least in a multicast PUCCH configuration (e.g., PUCCH-config).

[0300] 2) Option 1A-2: A group-common PRI may be included in the DCI.

[0301] - A single group common PRI can indicate a corresponding entry for a candidate PUCCH resource ID (e.g., pucch-ResourceId) value in a UE-specific PUCCH configuration (e.g., PUCCH-config) for the same or different PUCCH resource allocation for all UEs in the group.

[0302] - The candidate PUCCH resource ID (e.g., pucch-ResourceId) value is configured by a higher layer (e.g., RRC), and different PUCCH resource ID (e.g., pucch-ResourceId) values ​​may be configured for different UEs of the same group, at least in the PUCCH configuration (e.g., PUCCH-config) for multicast.

[0303] - If a PUCCH configuration for multicast (e.g., PUCCH-config) is configured for HARQ-ACK for a group-common PDSCH scheduled by a group-common DCI, the UE may assume that the PRI of the group-common DCI indicates a corresponding entry for a candidate PUCCH resource ID (pucch-ResourceId) value in the PUCCH configuration for multicast (e.g., PUCCH-config). That is, the PRI value of the group-common DCI may be analyzed based on the PUCCH configuration for multicast (e.g., PUCCH-config).

[0304] On the other hand, if the PUCCH configuration for multicast (e.g., PUCCH-config) is not configured for HARQ-ACK for the group-common PDSCH scheduled by the group-common DCI, the UE may assume that the PRI of the group-common DCI indicates a corresponding entry for the candidate PUCCH resource ID (pucch-ResourceId) value in the PUCCH configuration for unicast (e.g., PUCCH-config). That is, the PRI value of the group-common DCI may be analyzed based on the PUCCH configuration for unicast (e.g., PUCCH-config).

[0305] E.K1 (PDSCH-to-HARQ_feedback timing indicator) may be indicated by group-common DCI as follows:

[0306] 1) Option 1B-1: A list of UE-specific K1 values ​​may be included in the DCI.

[0307] Each K1 in the list can point to the same UL slot or different UL (sub)slots for different UEs in the group.

[0308] As an example, different K1 values ​​may be assigned to different UEs, e.g., K1-UE1, K2-UE2, K3-UE3, ...

[0309] As another example, the K1 value may be shared among multiple UEs (eg, K1-UE1 / UE2, K2-UE3 / UE4).

[0310] As another example, one K1 value may be a reference, and other K1 values ​​may be assigned based on the reference. For example, a list of {K1_ref, K1_offset (offset from reference)} may be indicated in the DCI.

[0311] For example, UE1 may use K1_ref, UE2 may use K1_ref+K1_offest1, and UE3 may use K1_ref+K1_offest2.

[0312] 2) Option 1B-2: A group-common K1 value may be included in the DCI.

[0313] A single K1 value may be the same for all UEs in a group receiving the DCI, or may indicate a corresponding entry for a candidate DL Data-UL ACK value (e.g., dl-DataToUL-ACK) in a UE-specific PUCCH configuration (e.g., PUCCH-config) for different PUCCH resource allocations. This may apply when the DCI format of the DCI is configured in the UE-specific PUCCH configuration (e.g., PUCCH-config) for the K1 value.

[0314] - Candidate DL Data-UL ACK values ​​(e.g., dl-DataToUL-ACK) are configured by higher layers (e.g., RRC) and may be different for different UEs of the same group at least in the PUCCH configuration for multicast (e.g., PUCCH-config).

[0315] - If the PUCCH configuration for multicast (e.g., PUCCH-config) is configured for HARQ-ACK for the group-common PDSCH scheduled by the group-common DCI, the UE may assume that the K1 value of the group-common DCI indicates a corresponding entry for a candidate DL Data-UL ACK value (e.g., dl-DataToUL-ACK) in the PUCCH configuration for multicast (e.g., PUCCH-config). That is, the K1 value of the group-common DCI may be analyzed based on the PUCCH configuration for multicast (e.g., PUCCH-config).

[0316] On the other hand, if the PUCCH configuration for multicast (e.g., PUCCH-config) is not configured for HARQ-ACK for the group-common PDSCH scheduled by the group-common DCI, the UE may assume that the K1 value of the group-common DCI indicates a corresponding entry for a candidate DL Data-UL ACK value (e.g., dl-DataToUL-ACK) in the PUCCH configuration for unicast (e.g., PUCCH-config). That is, the K1 value of the group-common DCI may be analyzed based on the PUCCH configuration for unicast (e.g., PUCCH-config).

[0317] Furthermore, when receiving a group-common DCI whose CRC is scrambled by the G-RNTI and / or a UE-specific DCI whose CRC is scrambled by the C-RNTI, if a Type-1 HARQ-ACK codebook for the PUCCH-config for multicast and / or the PUCCH-config for unicast is configured, the UE can configure TDRA (Time Domain Resource Allocation) and generate a Type-1 HARQ-ACK codebook for the HARQ-ACK for the group-common PDSCH scheduled by the group-common DCI and / or the UE-specific PDSCH scheduled by the UE-specific DCI.

[0318] 7. If the UE fails to decode the TB on the PDSCH transmission opportunity, the UE may transmit a HARQ NACK to the base station on a PUCCH resource within the configured UL CFR (S906b).

[0319] By using the PUCCH resources, the UE can also transmit HARQ-ACKs for other PDSCH transmissions, such as unicast SPS PDSCHs, dynamic unicast PDSCHs, PTP retransmissions, and / or dynamic group common PDSCHs. In this case, the UE can construct a codebook based on one or more options in step 7 to multiplex HARQ-ACKs on the PUCCH in (sub)slots for SPS PDSCHs for multicast, SPS PDSCHs for unicast, dynamically scheduled multicast PDSCHs, and / or dynamically scheduled unicast PDSCHs.

[0320] If a reference signal received power (RSRP) threshold is configured, the UE can use NACK-only based HARQ-ACK based on the measured RSRP of the serving cell. For example, if the measured RSRP is higher than (or equal to or greater than) the threshold, the NACK-only based HARQ-ACK may be transmitted on a group-common PUCCH resource indicated by the PRI of the DCI. On the other hand, if the measured RSRP is lower than (or equal to or less than) the threshold, the NACK-only based HARQ-ACK is changed to a HARQ-ACK-based HARQ-ACK and may be transmitted on a UE-specific PUCCH resource indicated by the PRI of the DCI.

[0321] On the other hand, if a PDSCH aggregation factor (pdsch-AggregationFactor) is set for the G-RNTI or the base station indicates a repetition number (repeat_number) in the DCI, the TB scheduled by the group-common DCI may be repeated for the Nth HARQ transmission of the TB within each symbol allocation in each of the PDSCH aggregation factor (pdsch-AggregationFactor) consecutive slots or in each of the repetition number (repeat_number) consecutive slots.

[0322] 8. The base station that receives the HARQ NACK in the TCI state can retransmit the PDCCH and PDSCH in the TCI state within the DL CFR configured for the TB retransmission. The UE can monitor the group-common and / or UE-specific PDCCH in the TCI state on the search space configured in the DL CFR to receive the TB retransmission (S907b).

[0323] The base station may retransmit the TB to only one of the UEs in the group via the UE-specific PDCCH, and the other UEs may not receive the TB retransmission (e.g., because the other UEs successfully received the TB).

[0324] 9. If the UE receives a PDCCH for retransmission of the TB (S908b), the UE can receive a PDSCH scheduled by the DCI of the PDCCH (S909b, S910b).

[0325] If the UE successfully decodes a TB on the PDSCH, the UE can consider the decoded TB to be associated with the MTCH, MRB, TMGI, G-RNTI and / or short ID of the MBS service based on the mapping between the MBS service indicated by the DCI and the HPN (HARQ process number) and / or the mapping between the MBS service indicated by the DCI and the short ID (if available).

[0326] 10. If TB decoding is successful in the PDSCH transmission opportunity, the UE can transmit a HARQ ACK to the base station on the PUCCH resource in the UL CFR configured in step 7. On the other hand, if TB decoding on the PDSCH transmission opportunity fails, the UE can transmit a HARQ NACK to the base station on the PUCCH resource in the configured UL CFR (S911b).

[0327] By using the PUCCH resources, the UE can also transmit HARQ-ACKs for other PDSCH transmissions, such as unicast SPS PDSCHs, dynamic unicast PDSCHs, PTP retransmissions, and / or dynamic group common PDSCHs. In this case, the UE can construct a codebook based on one or more options in step 7 to multiplex HARQ-ACKs on the PUCCH in (sub)slots for SPS PDSCHs for multicast, SPS PDSCHs for unicast, dynamically scheduled multicast PDSCHs, and / or dynamically scheduled unicast PDSCHs.

[0328] Meanwhile, the example of Figure 9 is for convenience of explanation and does not limit the scope of the present disclosure. Some steps illustrated in Figure 9 may be omitted depending on the situation and / or setting. Also, the base station and terminal in Figure 9 are merely examples and may be embodied by the devices illustrated in Figure 15 below. For example, the processor (102 / 202) of Figure 15 may control the transceiver (106 / 206) to transmit and receive channels / signals / data / information, etc., and may also control the memory (104 / 204) to store the transmitted or received channels / signals / data / information, etc.

[0329] A base station may collectively refer to an object that transmits and receives data to and from a terminal. For example, the base station may be a concept including one or more Transmission Points (TPs) and one or more Transmission and Reception Points (TRPs). Furthermore, the TP and / or TRP may include a base station panel, a transmission and reception unit, etc. Furthermore, the term "TRP" may be substituted with expressions such as a panel, an antenna array, a cell (e.g., a macro cell, a small cell, a pico cell, etc.), a transmission point (TP), a base station (gNB, etc.), etc. As described above, a TRP may be distinguished by information (e.g., an index, an ID) related to a CORESET group (or a CORESET pool). For example, if one terminal is configured to transmit and receive data to and from multiple TRPs (or cells), this may mean that multiple CORESET groups (or CORESET pools) are configured for one terminal. Such a configuration for a CORESET group (or a CORESET pool) may be performed by higher layer signaling (for example, RRC signaling, etc.).

[0330] 9, for convenience of explanation, signaling between one base station and a terminal is considered, but it goes without saying that the signaling scheme may be extended to signaling between multiple TRPs and multiple UEs. Alternatively, the base station may include multiple TRPs, or may be a cell including multiple TRPs.

[0331] In the prior art, rate match (RM)-related parameters and CSI-RS resources are configured by a PDSCH configuration (e.g., PDSCH-config) of a BWP. In other words, one or more BWPs may be configured for a UE, and RM-related information applied to PDSCH reception may be configured for the UE by configuration information (e.g., PDSCH-config) related to the PDSCH transmitted within each BWP.

[0332] More specifically, one or more (e.g., up to four) RM patterns may be configured for a terminal at the cell level (i.e., for each cell). For example, a plurality of (e.g., up to four) RM patterns may be configured (e.g., by rateMatchPatternToAddModList) in configuration information common to serving cells (e.g., ServingCellConfig). Furthermore, one or more (e.g., up to four) RM patterns may be configured for a terminal at the BWP level (i.e., for each BWP). For example, one or more (e.g., up to four) RM patterns may be configured (e.g., by rateMatchPatternToAddModList) in PDSCH-related configuration information in the BWP configuration (e.g., PDSCH-Config).

[0333] Here, each RM pattern may define a set of resource blocks belonging to a particular symbol that are not available for PDSCH transmission (ie, reserved resources).

[0334] Furthermore, the sets of RM patterns configured at the cell level and the BWP level are used to generate one or two RM pattern groups (i.e., RM pattern group 1 and RM pattern group 2). Here, a specific RM pattern group is activated by a rate matching indicator field in the DCI that later schedules the PDSCH. The rate matching indicator has a maximum length of two bits, and each bit corresponds to a specific RM pattern group. Therefore, the rate matching indicator field in the DCI may indicate one or two RM pattern groups to be used / applied for PDSCH reception.

[0335] Each RM pattern group may include one or more RM patterns (e.g., up to eight RM patterns (i.e., up to four cell-level RM patterns and up to four BWP-level RM patterns)). In other words, one or two RM pattern groups that can be dynamically activated by DCI may be configured in PDSCH-related configuration information in the BWP configuration (e.g., PDSCH-Config), and each RM pattern group may include one or more cell-level RM patterns and / or one or more BWP-level RM patterns.

[0336] Here, among one or more RM patterns at the cell level and one or more RM patterns at the BWP level configured for the terminal, an RM pattern that does not belong to an RM pattern group may be configured for the terminal semi-statically.

[0337] In this way, resources (e.g., REs) corresponding to the union of resources (i.e., reserved resources) configured by one or more RM patterns semi-statically and / or dynamically configured for the terminal are not used for the PDSCH. Therefore, the terminal can assume that the PDSCH is not transmitted on resources (e.g., REs) corresponding to the union of resources configured by the RM patterns, and can attempt to decode the TB carried on the PDSCH.

[0338] Meanwhile, in multicast PDSCH / PDCCH (e.g., group-common PDSCH / PDCCH) transmission, a separate CFR (Common Frequency Resource) (i.e., MBS frequency resource) may be configured within the BWP. That is, a UE may be configured with a CFR (i.e., MBS frequency resource) for each DL BWP, and PDSCH-related configuration information (e.g., PDSCH-config) for the CFR may be provided separately to the UE. As a result, there is a problem that it is unclear how the UE configures and applies RM-related parameters and CSI-RS resources for the CFR.

[0339] Therefore, the present disclosure proposes a rate matching / matching (RM) setting and CSI-RS setting method for transmitting and receiving a multicast PDSCH / PDCCH (for example, a group-common PDCCH / PDSCH) in consideration of the CFR setting.

[0340] FIG. 10 illustrates group-common PDCCH / PDSCH transmission and HARQ-ACK transmission in a wireless communication system to which the present disclosure can be applied.

[0341] As shown in Fig. 10, a terminal can receive multicast PDSCH / PDCCH (e.g., group-common PDCCH / PDSCH) scheduled with different G-RNTIs (or G-CS-RNTIs) by FDM or TDM. Also, the terminal can transmit multicast HARQ-ACK transmission / feedback for the multicast PDSCH / PDCCH (e.g., group-common PDCCH / PDSCH) to the base station.

[0342] 10, a terminal may receive DCI having a CRC scrambled by a G-RNTI (i.e., a multicast DCI) and a group-common PDSCH scheduled by the DCI (1001). The terminal may then decode the multicast PDSCH and transmit a multicast HARQ-ACK to a base station based on a decoding result (1002). The terminal may also receive DCI having a CRC scrambled by a G-RNTI (i.e., a multicast DCI) and a group-common PDSCH scheduled by the DCI (1003). The terminal may then decode the multicast PDSCH and transmit a multicast HARQ-ACK to a base station based on a decoding result (1004).

[0343] As shown in Fig. 10, a terminal can receive both the group-common PDSCH (1001) and the group-common PDSCH (1003) transmitted by FDM or TDM. Furthermore, the HARQ-ACK (1002) for the group-common PDSCH (1001) and the HARQ-ACK (1004) for the group-common PDSCH (1003) may be transmitted on the same PUCCH (or PUSCH), or may be transmitted individually on different PUCCHs (or PUSCHs).

[0344] Example 1: Priority of receiving multicast PDSCH / PDCCH (for example, group-common PDCCH / PDSCH)

[0345] When a multicast PDSCH / PDCCH (e.g., a group-common (SPS) PDCCH / PDSCH) is activated, the terminal can assume that no multicast PDSCH / PDCCH (e.g., a group-common (SPS) PDCCH / PDSCH) overlaps with system information (SI) transmission or paging transmission.

[0346] Alternatively, in reception, the terminal may assume that a multicast PDSCH / PDCCH (e.g., a group-common (SPS) PDCCH / PDSCH) that overlaps with an SI transmission or a paging transmission can occur. Therefore, in this case, if the terminal does not support parallel reception of the multicast PDSCH / PDCCH (e.g., a group-common (SPS) PDCCH / PDSCH) and the SI / paging PDSCH, the terminal may prioritize either i) the multicast PDSCH / PDCCH (e.g., a group-common (SPS) PDCCH / PDSCH) or ii) the SI transmission and / or the paging transmission over the other (e.g., receive only the prioritized one and not receive (decode) the others). Here, which one to prioritize may be determined by the terminal, may be predefined, or may be set by the base station. For example, the terminal may prioritize a multicast PDSCH / PDCCH (e.g., a group-common (SPS) PDCCH / PDSCH) over an SI transmission or a paging transmission, or the terminal may prioritize an SI transmission or a paging transmission over a multicast PDSCH / PDCCH (e.g., a group-common (SPS) PDCCH / PDSCH). The terminal may also deprioritize any multicast PDSCH / PDCCH (e.g., a group-common (SPS) PDCCH / PDSCH) reception in parallel with an SI transmission or a paging transmission at the terminal's own paging occasion (PO).

[0347] If a multicast PDSCH (e.g., a group-common (SPS) PDSCH) is scheduled by a DCI indicating high(er) priority (HP), the multicast PDSCH (e.g., a group-common (SPS) PDSCH) may be prioritized for reception over SI or paging. Also, a multicast PDSCH (e.g., a group-common (SPS) PDSCH) with HP may have higher priority for reception than a multicast PDSCH (e.g., a group-common (SPS) PDSCH) with low(er) priority (LP).

[0348] When receiving a PDSCH scheduled by an SC-RNTI or G-RNTI or when receiving a PDSCH by a group-common SPS, if the RE corresponding to the resource configured or dynamically indicated in Sections 5.1.4.1 and 5.1.4.2 of TS 38.214 is not available for the PDSCH, the terminal can assume SS / PBCH block transmission according to ssb-PositionsInBurst. Also, if the PDSCH resource allocation overlaps with a PRB including an SS / PBCH block transmission resource, the terminal can assume that the PRB including the SS / PBCH block transmission resource within the OFDM symbol in which the SS / PBCH block is transmitted is not available for the PDSCH.

[0349] Example 2: RM (rate match / matching) setting method for multicast PDSCH / PDCCH (e.g., group-common PDCCH / PDSCH) transmission

[0350] When a common frequency resource (CFR) for transmitting and receiving a multicast PDSCH / PDCCH (e.g., a group-common PDCCH / PDSCH) is configured, the base station can provide separate (individual) RM configuration information for the CFR as follows: Here, the terminal can apply conventional RM configuration information (e.g., cell-level RM configuration information, BWP-level RM configuration information) and RM configuration information for the CFR as follows.

[0351] 1. Method 2A: RM configuration information for CFR may be provided based on a rate match pattern group of a PDSCH-related configuration (e.g., PDSCH-config) for unicast or in a PDSCH-related configuration (e.g., PDSCH-config) for a separate CFR.

[0352] A) Configuration method 2A-1: A base station can configure a "CFR level rate match pattern" in rate match pattern group 1 or 2 of the existing unicast PDSCH-related configuration (e.g., PDSCH-config). In other words, in the past, multiple RM patterns (up to four each) at the cell level and BWP level could be configured for a terminal. According to one embodiment of the present disclosure, configuration information for the CFR level RM pattern may be further configured as shown in Table 8 below.

[0353] Table 8 illustrates configuration information for a CFR RM pattern on a rate match pattern group basis in a unicast PDSCH-related configuration (eg, PDSCH-config) according to one embodiment of the present disclosure.

[0354] [Table 8]

[0355] Table 8 illustrates information for configuring an RM pattern group, and one or two RM pattern groups may be configured for a terminal using such information. As shown in Table 8, each RM pattern group may include one or more RM patterns at the cell level and / or one or more RM patterns at the BWP level and / or one or more RM patterns at the CFR level. B) Configuration Method 2A-2: Existing cell-level or BWP-level configuration may be maintained. Furthermore, the terminal may apply RM pattern group 1 (RateMatchPatternGroup1) and / or RM pattern group 2 (RateMatchPatternGroup2) according to an instruction of a multicast DCI (e.g., a group-common DCI) (i.e., according to the rate matching indicator field value).

[0356] i) Option 1: The CFR level RM pattern may be configured according to the unicast PDSCH-related configuration (eg, PDSCH-config) of the active BWP of the UE associated with the CFR.

[0357] For example, the PDSCH-related configuration (e.g., PDSCH-config) for the active BWP of the terminal may include the following information: In addition, the terminal can apply one or more RM pattern groups among a plurality of RM pattern groups to a multicast PDSCH (e.g., a group-common PDSCH). Although the following illustrates an example in which two RM pattern groups are configured, the present disclosure is not limited thereto.

[0358] - RM pattern group 1 (RateMatchPatternGroup1)

[0359] - RM pattern group 2 (RateMatchPatternGroup2)

[0360] According to option 1, multiple RM pattern groups may be configured by the PDSCH-related configuration (e.g., PDSCH-config) for the terminal's BWP, and the terminal can apply some (i.e., one or more) RM pattern groups to PDSCH reception by multicast DCI.

[0361] Here, the RM pattern group configured by the PDSCH-related configuration (e.g., PDSCH-config) for the BWP of the terminal may be divided into an RM pattern group for a unicast PDSCH and an RM pattern group for a multicast PDSCH. In this case, only the RM pattern group for the multicast PDSCH may be indicated by the multicast DCI.

[0362] Alternatively, the RM pattern group configured by the PDSCH-related configuration (e.g., PDSCH-config) for the BWP of the UE may not be divided into an RM pattern group for a unicast PDSCH and an RM pattern group for a multicast PDSCH. In this case, the RM pattern indicated by the multicast DCI may be applied for receiving the multicast PDSCH, and the RM pattern indicated by the unicast DCI may be applied for receiving the unicast PDSCH.

[0363] ii) Option 2: A PDSCH-related configuration for CFR (PDSCH-config) may be defined / configured. Then, a CFR-level RM pattern may be configured for a terminal by the PDSCH-related configuration for CFR (PDSCH-config). For example, one or two RM pattern groups may be configured by the PDSCH-related configuration for CFR (PDSCH-config), and each RM pattern group may include one or more RM patterns. Furthermore, among the RM pattern groups configured by the PDSCH-related configuration for CFR (PDSCH-config), one or more RM patterns included in one or more RM pattern groups indicated by the multicast DCI may be applied to multicast PDSCH reception (i.e., resources configured by the one or more RM patterns are not available for multicast PDSCH).

[0364] For example, the terminal can apply the RM pattern group (RateMatchPatternGroup) configuration included in the PDSCH-related configuration (PDSCH-config) for CFR to a multicast PDSCH (for example, a group-common PDSCH).

[0365] Here, the RM pattern group may be configured by a PDSCH-related configuration (for example, PDSCH-config) for BWP of the terminal, and may also be configured by a PDSCH-related configuration (PDSCH-config) for CFR.

[0366] For example, when two RM pattern groups are configured, each RM pattern group may be included in a different PDSCH-related configuration (e.g., PDSCH-config) as follows: However, the present disclosure is not limited to configuring only two RM pattern groups by different PDSCH-related configurations (e.g., PDSCH-config). That is, multiple (e.g., two) RM pattern groups may be configured by the PDSCH-related configuration (e.g., PDSCH-config) for BWP of the terminal, and multiple (e.g., two) RM pattern groups may also be configured by the PDSCH-related configuration (PDSCH-config) for CFR.

[0367] - PDSCH-related configuration for the active BWP of the terminal (e.g., PDSCH-config): RM pattern group 1 (RateMatchPatternGroup1)

[0368] - PDSCH-related configuration for CFR (PDSCH-config): RM pattern group 2 (RateMatchPatternGroup2)

[0369] Based on the above-described setting method (i.e., setting method 2A-1 or 2A-2), the terminal can apply RM pattern group 1 (RateMatchPatternGroup1) and / or RM pattern group 2 (RateMatchPatternGroup2) as follows. Here, when two RM pattern groups are set, one of the RM pattern groups may be set for CFR, and the other RM pattern group may be set for non-CFR. Here, as described above, the number of RM pattern groups set in the terminal is not limited to two, and multiple RM pattern groups for CFR and multiple RM pattern groups not for CFR may be set in the terminal.

[0370] i) Option 1: A multicast DCI (e.g., a group-wide DCI) can always indicate an RM pattern group for CFR. Therefore, if a multicast DCI (e.g., a G-RNTI-based DCI) indicates an RM pattern group that is not for CFR, the terminal can either ignore the indication of the DCI (e.g., ignore only the rate matching indicator field indicating the RM pattern group) or ignore the entire DCI.

[0371] Similarly, a terminal-specific DCI (e.g., a C-RNTI-based DCI) can always indicate an RM pattern group that is not for CFR. Therefore, when a terminal-specific DCI (e.g., a C-RNTI-based DCI) indicates an RM pattern group for CFR, the terminal can ignore only that indication of the DCI (e.g., ignore only the rate matching indicator field indicating the RM pattern group) or ignore the entire DCI.

[0372] ii) Option 2: The DCI does not need to directly indicate the RM pattern group. The terminal can use the RM pattern group depending on the RNTI used to scramble the CRC of the DCI. Furthermore, if the RNTI used to scramble the CRC of the DCI is a G-RNTI, the terminal can use / apply the RM pattern group for CFR, and if the RNTI used to scramble the CRC of the DCI is a C-RNTI, the terminal can use / apply the RM pattern group not for CFR. In this case, the RM pattern group for CFR and the RM pattern group not for CFR may each be configured as a single RM pattern group.

[0373] 2. Method 2B: RM configuration information for CFR may be provided based on separate rate match pattern groups.

[0374] Here, a CFR-based (for) RM pattern group (ie, rateMatchPatternGroupCFR) may be further defined or set by the base station.

[0375] A) Configuration method 2B-1: A CFR-level RM pattern may be configured in the PDSCH-related configuration for unicast (PDSCH-config) of the active BWP of a CFR-associated UE. That is, an RM pattern group for CFR may be configured in the PDSCH-related configuration for unicast (PDSCH-config) of the active BWP of the UE. The following example illustrates a case where one CFR-level RM pattern group is configured, but the present disclosure is not limited thereto, and two CFR-level RM pattern groups may be configured.

[0376] - UE active BWP PDSCH-config configuration:

[0377] RM pattern group 1 (RateMatchPatternGroup1),

[0378] RM pattern group 2 (RateMatchPatternGroup2),

[0379] RM pattern group for CFR (RateMatchPatternGroupCFR)

[0380] B) Configuration method 2B-2: A CFR-level RM pattern may be configured in the PDSCH-related configuration (PDSCH-config) of the CFR. That is, an RM pattern group for the CFR may be configured in the PDSCH-related configuration (PDSCH-config) of the CFR. In the following example, a case where one CFR-level RM pattern group is configured is illustrated, but the present disclosure is not limited thereto, and two CFR-level RM pattern groups may be configured.

[0381] - UE active BWP PDSCH-config configuration:

[0382] RM pattern group 1 (RateMatchPatternGroup1),

[0383] RM pattern group 2 (RateMatchPatternGroup2)

[0384] - CFR PDSCH-config configuration

[0385] RM pattern group for CFR (RateMatchPatternGroupCFR)

[0386] The base station can use DCI to indicate to the terminal the RM pattern group for CFR (RateMatchPatternGroupCFR) as follows:

[0387] The existing DCI can indicate two RM pattern groups with a maximum of two bits. Therefore, the newly added pattern group may be provided as follows:

[0388] - Option 1: The base station can always configure only two of the three pattern groups (when there is one RM pattern group for CFR (RateMatchPatternGroupCFR)) using an RRC message. Therefore, the base station can configure the DCI to indicate RM pattern group 1 (RateMatchPatternGroup1) or the RM pattern group for CFR (RateMatchPatternGroupCFR), or to indicate RM pattern group 2 (RateMatchPatternGroup2) or the RM pattern group for CFR (RateMatchPatternGroupCFR).

[0389] - Option 2: The base station can configure up to three RM pattern groups (when there is one RM pattern group for CFR (RateMatchPatternGroupCFR)) in an RRC message.

[0390] Option 2-1: A one-bit flag may be added to the DCI, and the one-bit flag may indicate the RM pattern group for CFR (RateMatchPatternGroupCFR) to the terminal.

[0391] Option 2-2: The DCI still consists of only a maximum of a 2-bit flag (i.e., a rate matching indicator field), but may be parsed differently from the existing one as follows:

[0392] For example, in the case of a multicast DCI (e.g., a group-common DCI or a DCI in which the CRC is scrambled with the G-RNTI), the terminal can analyze that the flag of the conventional DCI (i.e., the rate matching indicator field) always indicates only the RM pattern group for CFR.

[0393] If the corresponding bit in the "Rate matching indicator" field of a DCI format (e.g., DCI format 1_1) that schedules a PDSCH is equal to 1, the configured RM pattern group 1 (rateMatchPatternGroup1), RM pattern group 2 (rateMatchPatternGroup2), or CFR-level RM pattern group (rateMatchPatternGroupCFR) may include a list of indexes of RM patterns that form a union of resource sets that are not dynamically available for the PDSCH. REs that fall within the union of resource sets configured by RM patterns that are not included in any one of the three RM groups are not available for the PDSCH scheduled by a DCI format (e.g., DCI format 1_0 or DCI format 1_1) or a PDSCH with SRS. When receiving a PDSCH scheduled by a DCI format (e.g., DCI format 1_0) or when receiving a PDSCH with group-common SPS activated by a DCI format (e.g., DCI format 1_0), the REs corresponding to the resources configured in RM pattern group 1 (rateMatchPatternGroup1) or RM pattern group 2 (rateMatchPatternGroup2) or CFR level RM pattern group (rateMatchPatternGroupCFR) may not be available for the scheduled PDSCH.

[0394] 3. Method 2C: Limited Buffer Rate Matching (LBRM) Configuration Method

[0395] When CFR is set, the LBRM for PTM transmission may be determined by CFR. If PTP retransmission of a TB transmitted in PTM occurs, the UE can determine the LBRM for PTP retransmission as follows, depending on the base station configuration.

[0396] A) Method 2C-1: The terminal can determine the LBRM for PTP retransmission by the same CFR as the PTM. For example, this method may be applied only when the CFR is set.

[0397] B) Method 2C-2: The UE can determine the LBRM for PTP retransmission based on the UE active BWP. For example, this method may be applied only when the CFR is set and the UE receives a PTM transmission in the active BWP.

[0398] Third Embodiment: Method for setting parameters (e.g., xOverhead) for overhead configuration (e.g., overhead from CSI-RS, CORESET, etc.) when transmitting a multicast PDCCH / PDSCH (e.g., group-common PDCCH / PDSCH)

[0399] When a Common Frequency Resource (CFR) for transmitting and receiving a multicast PDCCH / PDSCH (for example, a group-common PDCCH / PDSCH) is configured, the base station can set the xOverhead configuration parameters as follows.

[0400] Here, when a parameter (e.g., xOverhead) for configuring separate overhead for each CFR is configured for a terminal receiving a multicast PDSCH (e.g., a group-common PDSCH), the terminal may determine a transport block size (TBS) of the multicast PDSCH (e.g., a group-common PDSCH) according to a method 3B described below. On the other hand, when a parameter (e.g., xOverhead) for configuring separate overhead for each CFR is not configured for a terminal, the terminal may determine a TBS of the multicast PDSCH (e.g., a group-common PDSCH) according to a method 3A described below.

[0401] A) Method 3A: A parameter (eg, xOverhead) for overhead configuration may be configured for each PDSCH configuration (eg, PDSCH-ServingCellConfig) for the existing serving cell.

[0402] A terminal receiving a multicast PDSCH (e.g., a group-common PDSCH) can determine the TBS for the multicast PDSCH (e.g., a group-common PDSCH) by applying a parameter (e.g., xOverhead) for overhead configuration corresponding to the cell to which the CFR-related DL BWP belongs (e.g., according to section 5.1.3.2 of TS 38.214).

[0403] Here, the base station can configure all terminals receiving a multicast PDSCH (eg, a group-common PDSCH) in the same CFR to have the same parameters for overhead configuration (eg, xOverhead).

[0404] B) Scheme 3B: The base station can set parameters (e.g., xOverhead) for overhead configuration separately for each CFR.

[0405] A terminal receiving a multicast PDSCH (e.g., a group-common PDSCH) can apply a parameter (e.g., xOverhead) for overhead setting corresponding to the CFR of the multicast PDSCH (e.g., a group-common PDSCH) (e.g., according to section 5.1.3.2 of TS 38.214) and determine the TBS for that multicast PDSCH (e.g., a group-common PDSCH).

[0406] If a separate xOverhead is not configured for each CFR, the UE may determine the TBS of the multicast PDSCH (eg, group-common PDSCH) according to Method 3A.

[0407] Example 4: CSI-RS configuration method when transmitting multicast PDCCH / PDSCH (for example, group-common PDCCH / PDSCH)

[0408] In NR, Zero Power (ZP) CSI-RS is used for rate matching, where the base station may or may not provide a separate ZP CSI-RS configuration for CFR.

[0409] A) Method 3A: The base station may not provide a separate ZP CSI-RS configuration for the CFR. For example, the PDSCH-related configuration (e.g., PDSCH-config) for the CFR may not include the ZP CSI-RS resource configuration.

[0410] In this scheme, the UE applies the ZP CSI-RS resource configuration of the UE's active BWP associated with the CFR to the CFR and can receive multicast transmissions (e.g., group common transmissions) from the CFR.

[0411] B) Method 3B: The base station may provide a separate ZP CSI-RS configuration for the CFR. For example, the ZP CSI-RS resource configuration may be included in the PDSCH-related configuration (e.g., PDSCH-config) of the CFR.

[0412] Here, the base station can activate or deactivate the ZP CSI-RS by transmitting a separate message for CFR (e.g., a semi-persistent (SP) ZP CSI-RS Resource Set Activation / Deactivation MAC control element (CE)) to the terminal.

[0413] FIG. 11 illustrates a semi-persistent ZP CSI-RS resource set activation / deactivation MAC CE according to one embodiment of the present disclosure.

[0414] 11, the A / D (activation / deactivation) field indicates the activation or deactivation of the indicated SP ZP CSI-RS resource set. This field is set to 1 to indicate activation; otherwise, this field indicates deactivation.

[0415] The Serving Cell ID field indicates the identifier of the serving cell to which the MAC CE applies. The length of this field is 5 bits.

[0416] The BWP ID field indicates the DL BWP to which the MAC CE applies as the code point value of the bandwidth part indicator field of the DCI. The length of this field is 2 bits.

[0417] The SP ZP CSI-RS resource set ID field contains an index in the sp-ZP-CSI-RS-ResourceSetsToAddModList indicating the semi-persistent ZP CSI-RS resource set to be activated or deactivated. The length of this field is 4 bits.

[0418] R is a reserved bit and is set to 0.

[0419] Here, the MAC CE for CFR and the MAC CE for conventional BWP may be distinguished by a logical channel identity (LCID) field value in a MAC header constituting a MAC protocol data unit (PDU).

[0420] Also, the BWP ID field of the MAC CE for the CFR can be replaced with the CFR ID or can indicate the ID of the BWP associated with the CFR.

[0421] The terminal can determine the ZP CSI-RS resource as follows:

[0422] i) Method 3B-1: The base station can provide the UE with ZP CSI-RS resource configuration for active BWP and ZP CSI-RS resource configuration for CFR separately. An example of the configuration method is as follows:

[0423] - ZP CSI-RS resource configuration of PDSCH related configuration (e.g. PDSCH-config) for UE active BWP:

[0424] sp-ZP-CSI-RS-ResourceSetsToAddModList SEQUENCE(SIZE(1..maxNrofZP-CSI-RS-ResourceSets))OF ZP-CSI-RS-ResourceSet

[0425] - ZP CSI-RS resource configuration for PDSCH related configuration for CFR (e.g., PDSCH-config):

[0426] MBS-sp-ZP-CSI-RS-ResourceSetsToAddModList SEQUENCE(SIZE(1..maxNrofZP-CSI-RS-ResourceSets))OF ZP-CSI-RS-ResourceSet

[0427] In this case, the terminal may determine the ZP CSI-RS resource by combining (for example, union) the ZP CSI-RS resource configuration of the UE active BWP and the ZP CSI-RS resource configuration of the CFR.

[0428] ii) Method 3B-2: The base station can configure the ZP CSI-RS resource configuration of the UE active BWP to include ZP CSI-RS resources for multicast transmission (e.g., group-common).

[0429] As described below, in the ZP CSI-RS resource configuration of the UE active BWP, one or more ZP-CSI-RS-ResourceSets may be configured to include ZP CSI-RS resources for multicast transmission (e.g., group-common).

[0430] - ZP CSI-RS resource configuration of PDSCH-config for UE active BWP

[0431] sp-ZP-CSI-RS-ResourceSetsToAddModList SEQUENCE(SIZE(1..maxNrofZP-CSI-RS-ResourceSets))OF ZP-CSI-RS-ResourceSet

[0432] In this case, the terminal can determine the ZP CSI-RS resource by conventional ZP CSI-RS resource configuration.

[0433] C) Method 3C: Method for supporting AP ZP CSI-RS using multicast (e.g., group-common) DCI

[0434] The CSI-RS configuration may be included in the PDSCH-related configuration (e.g., PDSCH-config) for CFR for each UE.

[0435] In this case, when a UE-specific DCI triggers a ZP CSI-RS, the DCI can indicate whether to trigger a conventional ZP CSI-RS or an MBS-specific (i.e., for multicast) ZP CSI-RS.

[0436] Option 1: The UE can determine whether to trigger a conventional ZP CSI-RS or an MBS-specific (i.e., for multicast) ZP CSI-RS based on the RNTI of the DCI. If an MBS-specific (i.e., for multicast) ZP CSI-RS is triggered, the UE can perform rate matching (RM) of the multicast PDSCH (e.g., group-common PDSCH) based on the CSI-RS configuration.

[0437] Option 2: The UE can determine whether to trigger a conventional ZP CSI-RS or an MBS-specific (i.e., for multicast) ZP CSI-RS based on a specific bit of DCI. If an MBS-specific (i.e., for multicast) ZP CSI-RS is triggered, RM of a multicast PDSCH (e.g., a group-common PDSCH) can be performed based on the CSI-RS configuration.

[0438] In the unlikely event that the DCI triggers an MBS-specific (i.e., for multicast) ZP CSI-RS, the following may occur.

[0439] For example, when an MBS-specific (i.e., for multicast) ZP CSI-RS is configured in the PDSCH-related configuration (e.g., PDSCH-config) of the CFR, the base station can trigger the MBS-specific (i.e., for multicast) ZP CSI-RS with the DCI of the G-RNTI, allowing the terminal to perform RM of the multicast PDSCH (e.g., group-common PDSCH).

[0440] As yet another example, if an MBS-specific (i.e., for multicast) ZP CSI-RS is not configured in the PDSCH-related configuration (e.g., PDSCH-config) of the CFR, the base station may trigger a conventional ZP CSI-RS with the G-RNTI DCI, allowing the terminal to perform RM of a multicast PDSCH (e.g., a group-common PDSCH).

[0441] D) Method 3D: The base station may transmit a MAC CE (e.g., a group common MAC CE) for multicasting for activation / deactivation of the SP ZP CSI-RS. The MAC CE for the SP ZP CSI-RS is shown in FIG.

[0442] i) Method 3D-1: A MAC CE for multicast (e.g., a group-common MAC CE) may be scheduled with a DCI of a special G-RNTI, so that a terminal can receive the MAC CE only using the special G-RNTI.

[0443] Here, the special G-RNTI may be set to a separate G-RNTI for transmitting a MAC CE for multicast (for example, a group common MAC CE).

[0444] Alternatively, the special G-RNTI may be set to one of the G-RNTIs received by the terminal. In this case, the terminal can apply the RM parameters applied to a specific G-RNTI to other G-RNTIs in the same CFR. In this case, the base station does not need to separately set the special G-RNTI.

[0445] ii) Method 3D-2: The base station can transmit a separate MAC CE for multicast (e.g., a group-common MAC CE) for all G-RNTIs, so that the terminal can receive the MAC CE with the G-RNTI that the terminal intends to receive.

[0446] Example 5: Method for configuring PDSCH-related configuration (e.g., PDSCH-config) for CFR

[0447] The base station can configure a PDSCH-related configuration for CFR (e.g., PDSCH-config) separately from a PDSCH-related configuration for BWP (e.g., PDSCH-config). Here, CFR is associated with the UE's active BWP. Therefore, some parameters in the PDSCH-related configuration (e.g., PDSCH-config) may be configured commonly for CFR and BWP. Therefore, the base station may not repeat some parameters in the PDSCH-related configuration for CFR (e.g., PDSCH-config) and the PDSCH-related configuration for BWP (e.g., PDSCH-config), but may configure the parameters only in one of the PDSCH-related configurations (e.g., PDSCH-config).

[0448] For example, if the setting value for parameter A is the same in the PDSCH-related configuration for CFR (e.g., PDSCH-config) and the PDSCH-related configuration for BWP (e.g., PDSCH-config), the base station can include parameter A only in the PDSCH-related configuration for BWP (e.g., PDSCH-config).If parameter A does not exist in the PDSCH-related configuration for CFR (e.g., PDSCH-config), the terminal can set parameter A as follows.

[0449] A) Method 5A: The UE may configure the PDSCH-related configuration (e.g., PDSCH-config) of the UE active BWP associated with the CFR to be identical to the PDSCH-related configuration (e.g., PDSCH-config) of the CFR. In other words, the parameters in the active BWP associated with the CFR may be applied identically.

[0450] B) Method 5B: If there is a reference instruction for a specific parameter A in the PDSCH-related configuration (e.g., PDSCH-config) for the CFR, the parameter A configuration included in the PDSCH-related configuration (e.g., PDSCH-config) of the UE active BWP associated with the CFR can be set as if it were also in the PDSCH-related configuration (e.g., PDSCH-config) of the CFR. In other words, only when there is a reference instruction for the parameter, the parameters in the active BWP associated with the CFR can be applied identically.

[0451] If there is no reference instruction, the terminal can determine that the specific parameter A configuration is not included in the PDSCH-related configuration (for example, PDSCH-config) of the CFR.

[0452] Example 6: PUCCH spatial relation Activation / Deactivation

[0453] FIG. 12 illustrates a PUCCH spatial relation Activation / Deactivation MAC CE according to one embodiment of the present disclosure.

[0454] 12, the Serving Cell ID field indicates the identifier of the serving cell to which the MAC CE applies, and is 5 bits long.

[0455] The BWP ID field is a codepoint of the DCI bandwidth part indicator field and indicates the UL BWP to which the MAC CE applies. The length of this field is 2 bits.

[0456] The PUCCH Resource ID field contains the identifier of the PUCCH resource ID identified by PUCCHResourceId. The length of this field is 7 bits.

[0457] S i The field is the PUCCH-SpatialRelationInfoId set for the uplink bandwidth portion indicated by the BWP ID field in the PUCCH-Config in which the PUCCH resource ID is set. If there is PUCCH Spatial Relation Info, i indicates the activation state of the PUCCH spatial relationship information with the same PUCCHSpatialRelationInfoId as i+1, otherwise the MAC entity ignores this field. i The field is set to 1 to indicate that the PUCCH spatial relationship information with the same PUCCH-SpatialRelationInfoId as i+1 is activated. i The field is set to 0 to indicate that the PUCCH spatial relationship information with the same PUCCH-SpatialRelationInfoId as i+1 is deactivated. Only one PUCCH spatial relationship information may be activated for a PUCCH resource at a time.

[0458] R is a reserved bit and is set to 0.

[0459] In Figure 12, in PUCCH spatial relation Activation / Deactivation MAC CE, S i The field is mapped to one of the specific PUCCH-SpatialRelationInfoIds in the PUCCH-Config for unicast. i If the field is set to 1, it indicates activation of PUCCH Spatial Relation Info for the mapped PUCCH-SpatialRelationInfoId. In this case, the UE determines that the PUCCH resource in the PUCCH resource ID field of the MAC CE is mapped to a reference signal included in the PUCCH spatial relation information (Spatial Relation Info).

[0460] When receiving the MAC CE of FIG. 12 for activating or deactivating the PUCCH spatial relation, the terminal can activate or deactivate the PUCCH spatial relation of the PUCCH resource for multicast HARQ-ACK as follows:

[0461] Method 6A: If the PUCCH resource for transmitting the multicast HARQ-ACK is determined by the PUCCH-config for unicast, the terminal can also activate or deactivate the PUCCH spatial relation of the PUCCH resource for transmitting the multicast HARQ-ACK by the MAC CE of FIG. 12.

[0462] Here, if the PUCCH resource ID indicated by the PUCCH resource ID field is configured to be able to transmit both unicast HARQ-ACK and multicast HARQ-ACK, the terminal can apply the same PUCCH spatial relation indicated by the MAC CE to both unicast HARQ-ACK transmission and multicast HARQ-ACK transmission.

[0463] On the other hand, the base station may configure the PUCCH resource ID for multicast HARQ-ACK not to be shared with the PUCCH resource ID for unicast HARQ-ACK. In this case, the terminal may determine whether the PUCCH spatial relation indicated by the MAC CE is applied only to unicast HARQ-ACK transmission or only to multicast HARQ-ACK transmission, depending on the PUCCH resource ID indicated by the PUCCH resource ID field.

[0464] B) Method 6B: If the PUCCH resource for transmitting the multicast HARQ-ACK is determined by the multicast PUCCH-config, the terminal does not need to activate or deactivate the PUCCH spatial relation of the PUCCH resource for transmitting the multicast HARQ-ACK by the MAC CE of Figure 12.

[0465] Here, if the PUCCH resource indicated by the PUCCH resource ID field is used for both unicast HARQ-ACK transmission and multicast HARQ-ACK transmission, the terminal can apply the same PUCCH spatial relation indicated by the MAC CE only to the unicast HARQ-ACK transmission.

[0466] Alternatively, even if the PUCCH resource for transmitting the multicast HARQ-ACK is determined by the PUCCH-config for multicast by the base station configuration, the terminal can also activate or deactivate the PUCCH spatial relation of the PUCCH resource for transmitting the multicast HARQ-ACK by the MAC CE of Figure 12.

[0467] Meanwhile, the base station may provide a separate MAC CE for activating or deactivating a PUCCH spatial relation for multicast. In this case, the separate PUCCH spatial relation Activation / Deactivation MAC CE for multicast may also be configured in the same or similar manner as in Figure 12. However, the MAC CE for multicast and the MAC CE for unicast may be distinguished by different LCID values ​​in the MAC PDU.

[0468] Alternatively, it is possible to configure separate PUCCH spatial relations for the unicast PUCCH and the multicast PUCCH for the same PUCCH resource ID in one MAC CE. For example, in the MAC CE structure of FIG. 12, separate PUCCH spatial relations for the multicast PUCCH resource ID field and the multicast PUCCH resource ID field can be configured. i A new field for the field (eg, a two octet field) may be added.

[0469] C) Method 6C: If the PUCCH resource for transmitting the multicast HARQ-ACK is determined by the PUCCH-config for unicast or multicast, the PUCCH spatial relation of the PUCCH resource for transmitting the multicast HARQ-ACK in the terminal may not be activated or deactivated by the MAC CE of Figure 12, but may be activated or deactivated by the MAC CE for multicast described in the above-mentioned Method 6A or 6B or a MAC CE of a new structure.

[0470] Here, the base station can configure the PUCCH resource ID for multicast HARQ-ACK and the PUCCH resource ID for unicast HARQ-ACK to be shared.

[0471] FIG. 13 is a diagram illustrating an operation of a terminal with respect to a multicast PDSCH transmission / reception method according to an embodiment of the present disclosure.

[0472] FIG. 13 illustrates an example of the operation of a terminal based on the previously proposed method (e.g., a combination of any one or more of Examples 1 to 7 and their detailed embodiments). The illustration of FIG. 13 is for convenience of explanation and does not limit the scope of the present disclosure. Some steps illustrated in FIG. 13 may be omitted depending on the situation and / or settings. Also, the terminal in FIG. 13 is merely an example and may be embodied by the device illustrated in FIG. 15 below. For example, the processor (102 / 202) of FIG. 15 may control the transceiver (106 / 206) to transmit and receive channels / signals / data / information (e.g., RRC signaling, MAC CE, DCI for UL / DL scheduling, SRS, PDCCH, PDSCH, PUSCH, PUCCH, etc.) and may also control the memory (104 / 204) to store the transmitted or received channels / signals / data / information.

[0473] The UE receives, from the base station, first configuration information associated with a PDSCH for a BWP and second configuration information associated with a multicast PDSCH for a CFR set in the BWP (S1301).

[0474] Here, CFR refers to common frequency resources for MBS. One DL CFR provides group common PDCCH and group common PDSCH transmission resources for MBS transmission and reception, and one UL CFR can provide HARQ-ACK PUCCH resources for group common PDSCH reception. One CFR may be one MBS-specific BWP or one UE-specific BWP. Alternatively, one or more CFRs may be configured within one UE-specific BWP. One CFR is associated with one UE-specific BWP.

[0475] According to the above second embodiment, the first configuration information may include information on one or more first rate match pattern groups, each of which may include one or more rate match patterns for resources that are not available for receiving a PDSCH. Also, the second configuration information may include information on one or more second rate match pattern groups, each of which may include one or more rate match patterns for resources that are not available for receiving a PDSCH.

[0476] As described above, one or more (e.g., up to four) RM patterns may be configured for a terminal at the cell level (i.e., for each cell). For example, a plurality of (e.g., up to four) RM patterns may be configured (e.g., by rateMatchPatternToAddModList) in configuration information common to serving cells (e.g., ServingCellConfig). Also, one or more (e.g., up to four) RM patterns may be configured for a terminal at the BWP level (i.e., for each BWP). For example, one or more (e.g., up to four) RM patterns may be configured (e.g., by rateMatchPatternToAddModList) in PDSCH-related configuration information in the BWP configuration (e.g., PDSCH-Config).

[0477] Here, each RM pattern may define a set of resource blocks belonging to a particular symbol that are not available for PDSCH transmission (ie, reserved resources).

[0478] The set of RM patterns configured at the cell level and the BWP level may be used to generate the one or more first rate match pattern groups and the one or more second rate match pattern groups, and each rate match pattern group may include one or more cell-level rate match patterns and / or one or more BWP-level rate match patterns.

[0479] Furthermore, according to the fifth embodiment, the settings for the parameters that overlap between the first setting information and the second setting information may be omitted in the second setting information. In this case, the parameters set in the first setting information that are not included in the second setting information may be applied to receive the multicast PDSCH in the CFR. Alternatively, based on a specific reference instruction in the first setting information, the parameters set in the first setting information that are not included in the second setting information may be applied to receive the multicast PDSCH in the CFR.

[0480] Furthermore, although not shown, according to the first embodiment, the terminal can receive from the base station configuration information regarding the priority between i) the multicast PDSCH and ii) the SI or paging transmission (when overlapping is allowed). In this case, when the multicast PDSCH overlaps with the SI or paging transmission, the terminal can receive either i) the multicast PDSCH or ii) the SI or paging transmission based on the preset priority. The terminal can also assume that the multicast PDSCH does not overlap with the SI or paging transmission.

[0481] Although not shown, the terminal may receive configuration information related to parameters for overhead configuration (e.g., xOverhead) for multicast PDSCH from the base station according to the third embodiment. In this case, the terminal may determine the TBS based on the configured parameters for overhead configuration (e.g., xOverhead).

[0482] Although not shown, the terminal can receive ZP CSI-RS related configuration information for CFR from the base station according to the above-mentioned Example 4. In addition, the terminal can receive a message for activating / deactivating ZP CSI-RS resources for CFR according to the above-mentioned Example 4. In this case, the terminal can determine that the RE corresponding to the ZP CSI-RS resource configured when receiving the multicast PDSCH in the CFR will not be used for the multicast PDSCH.

[0483] Furthermore, although not shown, the terminal may receive PUCCH-related configuration information for transmitting a multicast HARQ-ACK for a multicast PDSCH from the base station according to the sixth embodiment. In this case, when transmitting a PUCCH for transmitting a multicast HARQ-ACK for a multicast PDSCH, the terminal may transmit based on the configured spatial relationship (i.e., reference RS).

[0484] The terminal receives DCI for scheduling the multicast PDSCH from the base station (S1302).

[0485] Here, the DCI may be transmitted via a PDCCH, and the PDCCH may be transmitted within a CFR.

[0486] Here, a specific RM pattern group may be activated using a rate matching indicator field in the DCI. In particular, even if the CFR at which the multicast PDSCH is transmitted is set in the BWP, only the one or more second rate match pattern groups among the one or more first rate match pattern groups and the one or more second rate match pattern groups may be indicated by the DCI. Alternatively, the one or more second rate match pattern groups may be implicitly indicated by the DCI based on a radio network temporary identifier (RNTI) that scrambles a cyclic redundancy check (CRC) of the DCI.

[0487] On the other hand, if the one or more first rate match pattern groups are indicated by the DCI, the UE can ignore information (e.g., fields) indicating the one or more first rate match pattern groups in the DCI, i.e., can use only the remaining information, excluding the information (e.g., fields), for multicast PDSCH reception.

[0488] Alternatively, if the one or more first rate match pattern groups are indicated by the DCI, the terminal may ignore the DCI entirely, i.e., by ignoring the DCI in this case, the terminal may not receive the multicast PDSCH scheduled by the DCI.

[0489] Furthermore, the DCI may include a cyclic redundancy check (CRC) scrambled by a group-radio network temporary identifier (G-RNTI) or a group-configured scheduling-radio network temporary identifier (G-CS-RNTI).

[0490] The terminal receives the multicast PDSCH within the CFR based on the DCI from the base station (S1303).

[0491] Here, a resource (e.g., RE) corresponding to a union of resources (i.e., reserved resources) configured by one or more rate matching patterns in the second rate match pattern group indicated by the DCI may not be used for the PDSCH. Therefore, the terminal may consider that the PDSCH is not transmitted on the resource (e.g., RE) corresponding to the union of resources configured by the rate match patterns, and may attempt to decode the TB carried on the PDSCH.

[0492] Also, although not shown, the terminal can transmit HARQ-ACK information to the base station based on the decoding result of the TB carried in the multicast PDSCH through the operation illustrated in FIG.

[0493] FIG. 14 is a diagram illustrating an operation of a base station for a multicast PDSCH transmission / reception method according to an embodiment of the present disclosure.

[0494] FIG. 14 illustrates an example of the operation of a base station based on the previously proposed method (e.g., a combination of any one or more of Examples 1 to 7 and their detailed embodiments). The example of FIG. 14 is for convenience of explanation and does not limit the scope of the present disclosure. Some steps illustrated in FIG. 14 may be omitted depending on the situation and / or configuration. Also, the base station in FIG. 14 is merely an example and may be embodied by the device illustrated in FIG. 15 below. For example, the processor (102 / 202) of FIG. 15 may control the transceiver (106 / 206) to transmit and receive channels / signals / data / information (e.g., RRC signaling, MAC CE, DCI for UL / DL scheduling, SRS, PDCCH, PDSCH, PUSCH, PUCCH, etc.) and store the transmitted or received channels / signals / data / information in the memory (104 / 204).

[0495] The base station transmits, to the terminal, first configuration information associated with a PDSCH for a BWP and second configuration information associated with a multicast PDSCH for a CFR configured within the BWP (S1401).

[0496] Here, CFR refers to common frequency resources for MBS. One DL CFR provides group common PDCCH and group common PDSCH transmission resources for MBS transmission and reception, and one UL CFR can provide HARQ-ACK PUCCH resources for group common PDSCH reception. One CFR may be one MBS-specific BWP or one UE-specific BWP. Alternatively, one or more CFRs may be configured within one UE-specific BWP. One CFR is associated with one UE-specific BWP.

[0497] According to the above second embodiment, the first configuration information may include information on one or more first rate match pattern groups, each of which may include one or more rate match patterns for resources that are not available for receiving a PDSCH. Also, the second configuration information may include information on one or more second rate match pattern groups, each of which may include one or more rate match patterns for resources that are not available for receiving a PDSCH.

[0498] As described above, one or more (e.g., up to four) RM patterns may be configured for a terminal at the cell level (i.e., for each cell). For example, a plurality of (e.g., up to four) RM patterns may be configured (e.g., by rateMatchPatternToAddModList) in configuration information common to serving cells (e.g., ServingCellConfig). Also, one or more (e.g., up to four) RM patterns may be configured for a terminal at the BWP level (i.e., for each BWP). For example, one or more (e.g., up to four) RM patterns may be configured (e.g., by rateMatchPatternToAddModList) in PDSCH-related configuration information in the BWP configuration (e.g., PDSCH-Config).

[0499] Here, each RM pattern may define a set of resource blocks belonging to a particular symbol that are not available for PDSCH transmission (ie, reserved resources).

[0500] The set of RM patterns configured at the cell level and the BWP level may be used to generate the one or more first rate match pattern groups and the one or more second rate match pattern groups, and each rate match pattern group may include one or more cell-level rate match patterns and / or one or more BWP-level rate match patterns.

[0501] Furthermore, according to the fifth embodiment, the settings for the parameters that overlap between the first configuration information and the second configuration information may be omitted in the second configuration information. In this case, the parameters set in the first configuration information that are not included in the second configuration information may be applied to receive the multicast PDSCH in the CFR. Alternatively, based on a specific reference instruction in the first configuration information, the parameters set in the first configuration information that are not included in the second configuration information may be applied to receive the multicast PDSCH in the CFR.

[0502] Furthermore, although not shown, according to the first embodiment, the base station can transmit to the terminal configuration information regarding the priority between i) the multicast PDSCH and ii) the SI or paging transmission (when overlapping is allowed). In this case, when the multicast PDSCH overlaps with the SI or paging transmission, the terminal can receive either i) the multicast PDSCH or ii) the SI or paging transmission based on the preset priority. Furthermore, the terminal can assume that the multicast PDSCH does not overlap with the SI or paging transmission.

[0503] Although not shown, the base station may transmit configuration information related to parameters for overhead configuration (e.g., xOverhead) for multicast PDSCH to the terminal according to the third embodiment. In this case, the terminal may determine the TBS based on the configured parameters for overhead configuration (e.g., xOverhead).

[0504] Furthermore, although not shown in the figures, the base station can transmit ZP CSI-RS related configuration information for CFR to the terminal according to the above-mentioned Example 4. In addition, the base station can transmit a message for activating / deactivating ZP CSI-RS resources for CFR according to the above-mentioned Example 4. In this case, the terminal can determine that the RE corresponding to the ZP CSI-RS resource configured in CFR when receiving the multicast PDSCH will not be used for the multicast PDSCH.

[0505] Furthermore, although not shown, the base station can transmit PUCCH-related configuration information for transmitting a multicast HARQ-ACK for a multicast PDSCH to the terminal according to the sixth embodiment. In this case, when transmitting a PUCCH for transmitting a multicast HARQ-ACK for a multicast PDSCH, the base station can receive the PUCCH based on the configured spatial relationship (i.e., reference RS).

[0506] The base station transmits DCI for scheduling the multicast PDSCH to the terminal (S1402).

[0507] Here, the DCI may be transmitted via a PDCCH, and the PDCCH may be transmitted within a CFR.

[0508] Here, a specific RM pattern group may be activated using a rate matching indicator field in the DCI. In particular, even if the CFR at which the multicast PDSCH is transmitted is set in the BWP, only the one or more second rate match pattern groups among the one or more first rate match pattern groups and the one or more second rate match pattern groups may be indicated by the DCI. Alternatively, the one or more second rate match pattern groups may be implicitly indicated by the DCI based on a radio network temporary identifier (RNTI) that scrambles a cyclic redundancy check (CRC) of the DCI.

[0509] On the other hand, if the one or more first rate match pattern groups are indicated by the DCI, the UE can ignore information (e.g., fields) indicating the one or more first rate match pattern groups in the DCI, i.e., can use only the remaining information, excluding the information (e.g., fields), for multicast PDSCH reception.

[0510] Alternatively, if the one or more first rate match pattern groups are indicated by the DCI, the terminal may ignore the DCI entirely, i.e., by ignoring the DCI in this case, the terminal may not receive the multicast PDSCH scheduled by the DCI.

[0511] Furthermore, the DCI may include a cyclic redundancy check (CRC) scrambled by a group-radio network temporary identifier (G-RNTI) or a group-configured scheduling-radio network temporary identifier (G-CS-RNTI).

[0512] The base station transmits a multicast PDSCH within the CFR to the terminal based on the DCI (S1403).

[0513] Here, a resource (e.g., RE) corresponding to a union of resources (i.e., reserved resources) configured by one or more rate matching patterns in the second rate match pattern group indicated by the DCI may not be used for the PDSCH. Therefore, the terminal may consider that the PDSCH is not transmitted on the resource (e.g., RE) corresponding to the union of resources configured by the rate match patterns, and may attempt to decode the TB carried on the PDSCH.

[0514] Also, although not shown, by the operation illustrated in FIG. 9 above, the base station can receive HARQ-ACK information from the terminal based on the decoding result of the TB carried by the terminal in the multicast PDSCH.

[0515] General devices to which the present disclosure can be applied

[0516] FIG. 15 illustrates a block diagram of a wireless communication device according to an embodiment of the present disclosure.

[0517] Referring to FIG. 15, a first wireless device 100 and a second wireless device 200 can transmit and receive wireless signals using various wireless access technologies (e.g., LTE, NR).

[0518] The 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 may be configured to control the memory 104 and / or the transceiver 106 to implement the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in this disclosure. 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 from the transceiver 106. The processor 102 may also receive a wireless signal including second information / signal from 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 coupled to the processor 102 and may store various information related to the operation of the processor 102. For example, the memory 104 may store software code including instructions for performing some or all of the processes controlled by the processor 102 or for implementing the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in this disclosure. Here, the processor 102 and the memory 104 may be part of a communications modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver 106 may be coupled 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 also be referred to as an RF (Radio Frequency) unit. In the present invention, a wireless device may refer to a communications modem / circuit / chip.

[0519] 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 may be configured to control the memory 204 and / or the transceiver 206 to implement the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in this disclosure. For example, the processor 202 may process information in the memory 204 to generate third information / signal, and then transmit a wireless signal including the third information / signal from the transceiver 206. The processor 202 may also receive a wireless signal including fourth information / signal from the transceiver 206, and then store information obtained from signal processing of the fourth information / signal in the memory 204. The memory 204 may be coupled to the processor 202 and may store various information related to the operation of the processor 202. For example, the memory 204 may store software code including instructions for performing some or all of the processes controlled by the processor 202 or for implementing the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in this disclosure. Here, the processor 202 and the memory 204 may be part of a communications modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver 206 may be coupled 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 also be referred to as an RF unit. In the present invention, a wireless device may refer to a communications modem / circuit / chip.

[0520] The hardware elements of the wireless devices 100, 200 are described in more detail below. Without limitation, 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, and SDAP). The 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, suggestions, methods, and / or operational flow diagrams disclosed in this disclosure. The one or more processors 102, 202 may generate messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in this disclosure. The 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, suggestions, and / or methods disclosed in this disclosure and provide them to the one or more transceivers 106, 206. The one or more processors 102, 202 can receive signals (e.g., baseband signals) from the one or more transceivers 106, 206 and obtain the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in this disclosure.

[0521] The one or more processors 102, 202 may be referred to as a controller, microcontroller, microprocessor, or microcomputer. The one or more processors 102, 202 may be implemented using hardware, firmware, software, or a combination thereof. As an example, the one or more processors 102, 202 may include 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). The descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in this disclosure may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. Firmware or software configured to execute the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in this disclosure may be included in 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 operational flow diagrams disclosed in this disclosure may be embodied by firmware or software in the form of code, instructions, and / or collections of instructions.

[0522] One or more memories 104, 204 may be coupled to one or more processors 102, 202 and may store various types of data, signals, messages, information, programs, code, instructions, and / or instructions. The one or more memories 104, 204 may be comprised of 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 internal and / or external 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 techniques, such as wired or wireless connections.

[0523] One or more transceivers 106, 206 may transmit user data, control information, wireless signals / channels, etc., as referred to in the methods and / or operational flowcharts of the present disclosure, to one or more other devices. One or more transceivers 106, 206 may receive user data, control information, wireless signals / channels, etc., as referred to in the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts of the present disclosure, from one or more other devices. For example, one or more transceivers 106, 206 may be coupled to one or more processors 102, 202 and may transmit and receive wireless signals. For example, one or more processors 102, 202 may control one or more transceivers 106, 206 to transmit user data, control information, or wireless signals to one or more other devices. Also, 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. Furthermore, one or more transceivers 106, 206 may be coupled to one or more antennas 108, 208, and the one or more transceivers 106, 206 may be configured to transmit and receive user data, control information, wireless signals / channels, etc., referred to in the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in this disclosure, via the one or more antennas 108, 208. In this disclosure, the one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). The one or more transceivers 106, 206 may convert the received user data, control information, wireless signals / channels, etc., from RF band signals to baseband signals for processing using one or more processors 102, 202. The one or more transceivers 106, 206 may convert the user data, control information, wireless signals / channels, etc., processed using one or more processors 102, 202, from baseband signals to RF band signals. To that end, one or more of the transceivers 106, 206 may include (analog) oscillators and / or filters.

[0524] The embodiments described above are combinations of the components and features of the present disclosure in a predetermined form. Each component or feature should be considered optional unless otherwise explicitly stated. Each component or feature may be implemented without being combined with other components or features. It is also possible to combine some components and / or features to form embodiments of the present disclosure. The order of operations described in the embodiments of the present disclosure 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 clear that claims that do not have an explicit reference relationship in the claims may be combined to form embodiments, or may be included as new claims by amendment after filing.

[0525] It is obvious to those skilled in the art that the present disclosure can be embodied in other specific forms without departing from the essential features of the present disclosure. Therefore, the above detailed description should not be interpreted as limiting in any respect, but should be considered as illustrative. The scope of the present disclosure should be determined by reasonable interpretation of the appended claims, and any modifications within the equivalent scope of the present disclosure are included in the scope of the present disclosure.

[0526] The scope of the present disclosure includes software or machine-executable instructions (e.g., operating systems, applications, firmware, programs, etc.) that cause a device or computer to perform operations according to the methods of various embodiments, as well as non-transitory computer-readable media on which such software or instructions are stored and executable on a device or computer. Instructions usable for programming a processing system to perform features described in this disclosure may be stored on or in a storage medium or computer-readable storage medium, and computer program products including such storage media may be used to embody features described in this disclosure. The storage medium may include high-speed random access memory such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices, but is not limited to such, and may include non-volatile memory such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory optionally includes one or more storage devices located remotely from the processor. The memory, or alternatively, a non-volatile memory device within the memory, comprises a non-transitory computer-readable storage medium. The features described in this disclosure may be embodied in software and / or firmware stored on any one of a number of machine-readable media and capable of controlling the hardware of a processing system and allowing the processing system to interact with other mechanisms that utilize the results of embodiments of the present disclosure. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments / containers.

[0527] Here, the wireless communication technology implemented in the wireless devices 100 and 200 of the present disclosure may include LTE, NR, and 6G, as well as Narrowband Internet of Things (NB-IoT) for low-power communication. Here, for example, the NB-IoT technology may be an example of a Low Power Wide Area Network (LPWAN) technology and may be implemented according to standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-mentioned names. Additionally or alternatively, the wireless communication technology implemented in the wireless devices (XXX, YYY) of the present disclosure may perform communication based on the LTE-M technology. Here, for example, the LTE-M technology may be an example of an LPWAN technology and may be referred to by various names such as enhanced Machine Type Communication (eMTC). For example, LTE-M technology may 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 names. Additionally or alternatively, wireless communication technologies implemented in the wireless device (XXX, YYY) of the present disclosure may include at least one of ZigBee, Bluetooth, and a Low Power Wide Area Network (LPWAN), which consider low-power communication, and are not limited to the above names. As an example, ZigBee technology can create personal area networks (PANs) related to small / low-power digital communication based on various standards, such as IEEE 802.15.4, and may be referred to by various names. [Industrial Applicability]

[0528] The method proposed in this disclosure has been described mainly as being applied to 3GPP LTE / LTE-A and 5G systems, but it can also be applied to various other wireless communication systems in addition to 3GPP LTE / LTE-A and 5G systems.

Claims

1. A step in which a terminal receives, from a base station, first setting information related to a PDSCH for a BWP (bandwidth part) and second setting information related to a multicast PDSCH (physical downlink shared channel) for a CFR (common frequency resource) set in the BWP; receiving, from the base station, downlink control information (DCI) for scheduling the multicast PDSCH; receiving, by the terminal, the multicast PDSCH within the CFR based on the DCI from the base station; the first configuration information includes information related to at least one first rate match pattern group, each of the at least one first rate match pattern group including at least one rate match pattern for resources that are not available for reception of a PDSCH; the second configuration information includes information on at least one second rate match pattern group, each of the at least one second rate match pattern group including at least one rate match pattern for resources that are not available for reception of a PDSCH; a method in which, even though the CFR is set in the BWP, only the at least one second rate match pattern group is indicated by the DCI to be applied to reception of the multicast PDSCH among the at least one first rate match pattern group and the at least one second rate match pattern group.

2. 2. The method of claim 1, wherein, based on the indication of the at least one first rate match pattern group by the DCI, information indicating the at least one first rate match pattern group in the DCI is ignored by the terminal.

3. The method of claim 1 , wherein the entire DCI is ignored by the terminal based on the at least one first rate match pattern group being indicated by the DCI.

4. 2. The method of claim 1, wherein the at least one second rate match pattern group is implicitly indicated by the DCI based on a radio network temporary identifier (RNTI) that scrambles a cyclic redundancy check (CRC) of the DCI.

5. 2. The method of claim 1, wherein the DCI includes a cyclic redundancy check (CRC) scrambled by a group-radio network temporary identifier (G-RNTI) or a group-configured scheduling-radio network temporary identifier (G-CS-RNTI).

6. The method of claim 1 , wherein the terminal assumes that the multicast PDSCH does not overlap with system information (SI) or paging transmissions.

7. 2. The method of claim 1, wherein when the multicast PDSCH overlaps with system information (SI) or paging transmission, either i) the multicast PDSCH or ii) the SI or paging transmission is received based on a preset priority.

8. 2. The method of claim 1, wherein parameters configured in the first configuration information that are not included in the second configuration information are applied to receive the multicast PDSCH within the CFR.

9. 2. The method of claim 1, wherein, based on a reference instruction in the first configuration information, parameters set in the first configuration information that are not included in the second configuration information are applied to receive the multicast PDSCH within the CFR.

10. At least one transceiver for transmitting and receiving radio signals; at least one processor controlling the at least one transceiver; The at least one processor Receive, from a base station, first configuration information related to a PDSCH for a bandwidth part (BWP) and second configuration information related to a multicast physical downlink shared channel (PDSCH) for a common frequency resource (CFR) set in the BWP; receiving, from the base station, downlink control information (DCI) for scheduling the multicast PDSCH; configured to receive the multicast PDSCH within the CFR based on the DCI from the base station; the first configuration information includes information related to at least one first rate match pattern group, each of the at least one first rate match pattern group including at least one rate match pattern for resources that are not available for reception of a PDSCH; the second configuration information includes information on at least one second rate match pattern group, each of the at least one second rate match pattern group including at least one rate match pattern for resources that are not available for reception of a PDSCH; a terminal, wherein, even though the CFR is set in the BWP, only the at least one second rate match pattern group is indicated by the DCI to be applied to reception of the multicast PDSCH among the at least one first rate match pattern group and the at least one second rate match pattern group.

11. At least one non-transitory computer-readable medium storing at least one instruction, The at least one processor-executable instruction causes the apparatus to: Receive, from a base station, first configuration information related to a PDSCH for a bandwidth part (BWP) and second configuration information related to a multicast physical downlink shared channel (PDSCH) for a common frequency resource (CFR) set in the BWP; receiving, from the base station, downlink control information (DCI) for scheduling the multicast PDSCH; Controlling reception of the multicast PDSCH within the CFR based on the DCI from the base station; the first configuration information includes information related to at least one first rate match pattern group, each of the at least one first rate match pattern group including at least one rate match pattern for resources that are not available for reception of a PDSCH; the second configuration information includes information on at least one second rate match pattern group, each of the at least one second rate match pattern group including at least one rate match pattern for resources that are not available for reception of a PDSCH; a second rate match pattern group that is selected from the at least one first rate match pattern group and the at least one second rate match pattern group; a second rate match pattern group that is selected from the at least one first rate match pattern group and the at least one second rate match pattern group; 12. A processing device configured to control a terminal, comprising: at least one processor; at least one computer memory operably coupled to the at least one processor and storing instructions that perform operations based on being executed by the at least one processor; The operation is receiving, from a base station, first configuration information related to a PDSCH for a bandwidth part (BWP) and second configuration information related to a multicast physical downlink shared channel (PDSCH) for a common frequency resource (CFR) configured in the BWP; receiving downlink control information (DCI) for scheduling the multicast PDSCH from the base station; receiving the multicast PDSCH within the CFR from the base station based on the DCI; the first configuration information includes information related to at least one first rate match pattern group, each of the at least one first rate match pattern group including at least one rate match pattern for resources that are not available for reception of a PDSCH; the second configuration information includes information on at least one second rate match pattern group, each of the at least one second rate match pattern group including at least one rate match pattern for resources that are not available for reception of a PDSCH; A processing device, wherein, even though the CFR is set in the BWP, of the at least one first rate match pattern group and the at least one second rate match pattern group, only the at least one second rate match pattern group is indicated by the DCI to apply to reception of the multicast PDSCH.

13. A step in which a base station transmits to a terminal first setting information related to a PDSCH for a frequency BWP (bandwidth part) and second setting information related to a multicast PDSCH (physical downlink shared channel) for a CFR (common frequency resource) set in the BWP; The base station transmits downlink control information (DCI) for scheduling the multicast PDSCH to the terminal; The base station transmits the multicast PDSCH to the terminal within the CFR based on the DCI; the first configuration information includes information related to at least one first rate match pattern group, each of the at least one first rate match pattern group including at least one rate match pattern for resources that are not available for reception of a PDSCH; the second configuration information includes information on at least one second rate match pattern group, each of the at least one second rate match pattern group including at least one rate match pattern for resources that are not available for reception of a PDSCH; a method in which, even though the CFR is set in the BWP, only the at least one second rate match pattern group is indicated by the DCI to be applied to reception of the multicast PDSCH among the at least one first rate match pattern group and the at least one second rate match pattern group.

14. At least one transceiver for transmitting and receiving radio signals; at least one processor controlling the at least one transceiver; The at least one processor Transmitting, to a terminal, first configuration information related to a PDSCH for a frequency bandwidth part (BWP) and second configuration information related to a multicast physical downlink shared channel (PDSCH) for a common frequency resource (CFR) set in the BWP; Transmitting downlink control information (DCI) for scheduling the multicast PDSCH to the terminal; The terminal is configured to transmit the multicast PDSCH within the CFR based on the DCI; the first configuration information includes information related to at least one first rate match pattern group, each of the at least one first rate match pattern group including at least one rate match pattern for resources that are not available for reception of a PDSCH; the second configuration information includes information on at least one second rate match pattern group, each of the at least one second rate match pattern group including at least one rate match pattern for resources that are not available for reception of a PDSCH; A base station, wherein, even though the CFR is set in the BWP, only the at least one second rate match pattern group is indicated by the DCI to be applied to reception of the multicast PDSCH among the at least one first rate match pattern group and the at least one second rate match pattern group.

Images