Method and apparatus for performing uplink transmission and reception in a wireless communication system - Patents.com

Abstract

A method and an apparatus for performing uplink transmission and reception in a wireless communication system are disclosed. According to an embodiment of the present disclosure, a method for performing uplink transmission by a terminal includes: receiving configuration information related to a semi-static HARQ-ACK codebook for PDSCH from a base station; receiving at least one DCI including a DAI field from the base station; and transmitting HARQ-ACK information for the first PDSCH to the base station based on only a first PDSCH satisfying a specific condition among a plurality of PDSCHs being received from the base station, and the semi-static HARQ-ACK codebook including HARQ-ACK information for each of the plurality of PDSCHs may be transmitted to the base station based on the DAI field included in the at least one DCI associated with the plurality of PDSCHs indicating a specific value.

Description

[Technical field]

[0001] The present disclosure relates to wireless communication systems, and more particularly, to methods and apparatus for uplink transmission and reception in wireless communication systems. [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 data services, and currently, resource shortages are occurring due to the explosive increase in traffic, and users are demanding faster services, so there is a demand for more advanced mobile communication systems.

[0003] The requirements for the next generation mobile communication system 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 such as dual connectivity, massive multiple input multiple output (MIMO), in-band full duplex, non-orthogonal multiple access (NOMA), super wideband support, and device networking are being researched. 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 performing uplink transmission and reception in a wireless communication system.

[0005] Furthermore, a further technical object of the present disclosure is to provide a method and apparatus for performing a fall-back operation when simultaneously transmitting and receiving unicast and / or multicast PDSCHs.

[0006] The technical problems to be achieved 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] In one embodiment of the present disclosure, a method for a terminal performing uplink transmission in a wireless communication system includes the steps of receiving configuration information related to a semi-static hybrid automatic repeat request (HARQ)-acknowledge (ACK) codebook for a physical downlink shared channel (PDSCH) from a base station, receiving at least one downlink control information (DCI) including a downlink assignment index (DAI) field from the base station, and transmitting HARQ-ACK information for the first PDSCH to the base station based on only a first PDSCH satisfying a specific condition among a plurality of PDSCHs being received from the base station, and the semi-static HARQ-ACK codebook including HARQ-ACK information for each of the plurality of PDSCHs may be transmitted to the base station based on the DAI field included in the at least one DCI associated with the plurality of PDSCHs indicating a specific value.

[0008] In another embodiment of the present disclosure, a method for uplink reception by a base station in a wireless communication system includes: transmitting configuration information related to a semi-static hybrid automatic repeat request (HARQ)-acknowledge (ACK) codebook for a physical downlink shared channel (PDSCH) to a terminal; transmitting at least one downlink control information (DCI) including a downlink assignment index (DAI) field to the terminal; and receiving HARQ-ACK information for the first PDSCH from the terminal based on only a first PDSCH satisfying a specific condition among a plurality of PDSCHs being received from the base station, wherein the semi-static HARQ-ACK codebook including HARQ-ACK information for each of the plurality of PDSCHs may be received from the terminal based on the DAI field included in the at least one DCI associated with the plurality of PDSCHs indicating a specific value. Effect of the Invention

[0009] According to an embodiment of the present disclosure, a method and apparatus for performing uplink transmission and reception in a wireless communication system can be provided.

[0010] In addition, an embodiment of the present disclosure may provide a method and apparatus for performing a fall-back operation when simultaneously transmitting and receiving unicast and / or multicast PDSCHs.

[0011] 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 a person having ordinary skill in the art to which the present disclosure pertains from the following description. [Brief description of the drawings]

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

[0013] [Figure 1] FIG. 1 is a diagram illustrating the structure of a wireless communication system to which the present disclosure can be applied. [Diagram 2] FIG. 1 illustrates a frame structure in a wireless communication system to which the present disclosure can be applied. [Diagram 3] FIG. 1 illustrates a resource grid in a wireless communication system to which the present disclosure can be applied. [Figure 4] FIG. 1 is a diagram illustrating a physical resource block in a wireless communication system to which the present disclosure can be applied. [Diagram 5] FIG. 1 illustrates a slot structure in a wireless communication system to which the present disclosure can be applied. [Figure 6] 1 is a diagram illustrating 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. [Figure 7] FIG. 13 is a diagram for explaining the transmission timing of unicast / multicast HARQ-ACK to which the present disclosure can be applied. [Figure 8] A diagram for explaining an FDM unicast / multicast transmission / reception method for the same G-RNTI to which the present disclosure can be applied. [Figure 9] A diagram for explaining an FDM-based unicast / multicast transmission / reception method for two G-RNTIs to which the present disclosure can be applied. [Figure 10] 1 is a diagram for explaining an uplink transmission operation of a terminal in a wireless communication system to which the present disclosure can be applied. [Figure 11] 1 is a diagram for explaining an uplink receiving operation of a base station in a wireless communication system to which the present disclosure can be applied. [Figure 12]A diagram for explaining a signaling procedure between the network side and the terminal according to one embodiment of the present disclosure. [Figure 13] 1 is a block diagram illustrating a wireless communication device according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] Hereinafter, preferred embodiments of the present disclosure will be described in detail 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 show the only embodiment 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 is understood by those skilled in the art that the present disclosure can be implemented without such specific details.

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

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

[0017] In this disclosure, terms such as "first" and "second" are used only to distinguish one component from another component, and are not used 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.

[0018] 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 form is intended to include the plural form unless the context dictates otherwise. The term "and / or" used in this disclosure means that one of the associated listed items may be included, or any and all possible combinations of two or more of them. Also, in this disclosure, " / " between words has the same meaning as "and / or" unless otherwise specified.

[0019] The present disclosure is described with respect to a wireless communication network or wireless communication system, and operations performed in the wireless communication network may be performed in a 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 a process in which a terminal coupled to the wireless network transmits or receives signals to or between the network.

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

[0021] In the following, downlink (DL) means communication from a base station to a terminal, and uplink (UL) means communication from a terminal to a base station. In the downlink, a transmitter may be a part of the base station, and a receiver may be a part of the terminal. In the uplink, a transmitter may be a part of the terminal, and a receiver may be a 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, eNB (evolved-NodeB), gNB (Next Generation NodeB), BTS (base transceiver system), access point (AP), network (5G network), AI (Artificial Intelligence) system / module, RSU (road side unit), robot, drone (UAV: Unmanned Aerial Vehicle), AR (Augmented Reality) device, VR (Virtual Reality) device, etc. In addition, a terminal may be fixed or mobile, and may be replaced with terms such as User Equipment (UE), Mobile Station (MS), user terminal (UT), Mobile Subscriber Station (MSS), Subscriber Station (SS), Advanced Mobile Station (AMS), Wireless terminal (WT), Machine-Type Communication (MTC) device, Machine-to-Machine (M2M) device, Device-to-Device (D2D) device, vehicle, road side unit (RSU), robot, Artificial Intelligence (AI) module, drone (UAV: Unmanned Aerial Vehicle), Augmented Reality (AR) device, Virtual Reality (VR) device, etc.

[0022] 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) / 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 (registered trademark) (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.

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

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

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

[0026] The following terminology abbreviations may be used in this disclosure:

[0027] - BM: Beam management

[0028] - CQI: channel quality indicator

[0029] - CRI: channel state information- reference signal resource indicator

[0030] - CSI: channel state information

[0031] - CSI-IM: channel state information-interference measurement

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

[0033] - DMRS: Demodulation Reference Signal

[0034] - FDM: Frequency division multiplexing

[0035] - FFT: Fast Fourier transform

[0036] - IFDMA: Interleaved frequency division multiple access

[0037] - IFFT: inverse fast Fourier transform

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

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

[0040] - MAC: medium access control

[0041] - NZP: non-zero power

[0042] - OFDM: Orthogonal frequency division multiplexing

[0043] - PDCCH: physical downlink control channel

[0044] - PDSCH: physical downlink shared channel

[0045] - PMI: Precoding matrix indicator

[0046] - RE: resource element

[0047] - RI: Rank indicator

[0048] - RRC: Radio resource control

[0049] - RSSI: received signal strength indicator

[0050] - Rx: Reception

[0051] - QCL: quasi co-location

[0052] - SINR: signal to interference and noise ratio

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

[0054] - TDM: time division multiplexing

[0055] - TRP: transmission and reception point

[0056] - TRS: Tracking reference signal

[0057] - Tx: transmission

[0058] - UE: User Equipment

[0059] - ZP: Zero power

[0060] System in general

[0061] As more communication devices require larger communication capacity, the need for improved mobile broadband communication compared to existing radio access technology (RAT) is emerging. Massive MTC (Machine Type Communications), which connects multiple devices and objects to provide various services anytime and anywhere, is also one of the major issues considered in next-generation communication. In addition, communication system design considering reliability and latency-sensitive services / terminals is also being discussed. Thus, the introduction of next-generation RATs considering eMBB (enhanced mobile broadband communication), Mmtc (massive MTC), URLLC (Ultra-Reliable and Low Latency Communication), etc. is being discussed, and for convenience in this disclosure, the technology is referred to as NR. NR is an expression representing an example of 5G RAT.

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

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

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

[0065] Referring to FIG. 1, the NG-RAN is composed of gNBs that provide an NG-Radio Access (NG-RA) 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 UEs. The gNBs are interconnected via an Xn interface. The gNBs are also connected to a New Generation Core (NGC) via an NG interface. More specifically, the gNBs are connected to an Access and Mobility Management Function (AMF) via an N2 interface and to a User Plane Function (UPF) via an N3 interface.

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

[0067] The NR system can support multiple numerologies, where the numerology may be defined by subcarrier spacing and cyclic prefix (CP) overhead. In this case, the multiple subcarrier spacing may be derived by scaling the base (reference) subcarrier spacing by an integer N (or μ). In addition, the numerology used may be selected independently of the frequency band, even if it is assumed that very low subcarrier spacing is not used at very high carrier frequencies. In addition, various frame structures with multiple numerologies may be supported in the NR system.

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

[0069] [Table 1]

[0070] NR supports multiple numerologies (or subcarrier spacing (SCS)) to support various 5G services. For example, when the SCS is 15 kHz, it supports a wide area in a traditional cellular band, when the SCS is 30 kHz / 60 kHz, it supports dense urban areas, lower latency, and wider carrier bandwidth, and when the SCS is 60 kHz or higher, it supports a bandwidth larger than 24.25 GHz to overcome phase noise. The NR frequency band is defined as two types of frequency ranges (FR1, FR2). FR1 and FR2 may be configured as shown in Table 2 below. Also, FR2 can mean millimeter wave (mmW).

[0071] [Table 2]

[0072] In relation to the frame structure in the NR system, the sizes of the various fields in the time domain are T c =1 / (Δf max N f ) where Δf max =480 10 3 Hz and N f= 4096. Downlink and uplink transmissions are f =1 / (Δf max N f / 100)·T c The radio frame is organized into radio frames each having a duration of T 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. Also, the transmission from the terminal in the uplink frame number i starts 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,μ -1}. A slot is numbered in increasing order. 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.

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

[0074] [Table 3]

[0075] [Table 4]

[0076] FIG. 2 is an example when μ=2 (SCS is 60 kHz), and referring to Table 3, one subframe can include four slots. One subframe={1, 2, 4} slots shown in FIG. 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 less symbols. In relation to physical resources in an NR system, antenna ports, resource grids, resource elements, resource blocks, carrier parts, and the like may be considered.

[0077] The physical resources that can be considered in the NR system will be specifically described below. First, in relation to antenna ports, the antenna ports are defined such that the channel on which a symbol on an antenna port is carried can be inferred from the channel on which another symbol on the same antenna port is carried. If the large-scale property of the channel on which a symbol on one antenna port is carried can be inferred from the channel on which a symbol on the other antenna port is carried, the two antenna ports are said to be in a QC / QCL (quasi co-located or quasi co-location) relationship. Here, the large-scale property includes one or more of delay spread, Doppler spread, frequency shift, average received power, and received timing. FIG. 3 illustrates a resource grid in a wireless communication system to which the present disclosure can be applied.

[0078] Referring to FIG. 3, the resource grid is divided into N RB μ N sc RB Each subframe consists of 14·2 subcarriers. μ In the present embodiment, the OFDM symbol is used as an example, but is not limited to, an OFDM symbol. 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 with numerology but also between uplink and downlink. In this case, one resource grid may be set for μ 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: JPEG2025506177000006.jpg8143, where k=0,...,N RB μ N sc RB -1 is the index in the frequency domain, JPEG2025506177000007.jpg91522 μ 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.

[0079] where l=0,...,N symb μ μ and the resource element for antenna port p. JPEG2025506177000008.jpg9134 is a complex value JPEG2025506177000009.jpg10150. If there is no risk of confusion or if a specific antenna port or numerology is not specified, the indexes p and μ may be dropped, so that the complex value is JPEG2025506177000010.jpg12137. Also, a resource block (RB) is N sc RB = 12 consecutive subcarriers.

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

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

[0082] - absoluteFrequencyPointA denotes the frequency-location of point A expressed as in ARFCN (absolute radio-frequency channel number). Common resource blocks are numbered from 0 upwards in the frequency domain for subcarrier spacing setting μ. The center of subcarrier 0 of common resource block 0 for subcarrier spacing setting μ coincides with 'point A'. Common resource block number n in the frequency domain CRB μ The relationship between k, l and the resource element (k, l) for the subcarrier spacing setting μ is given by the following Equation 1.

[0083]

number

[0084] In Equation 1, k is defined relative to point A such that k=0 corresponds to the subcarrier centered at point A. A physical resource block is a number ranging from 0 to N within a bandwidth part (BWP). BWP,i size,μ The numbering is from -1 to i, where i is the number of the BWP. PRB and common resource block n CRB The relationship between is given by Equation 2 below.

[0085]

number

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

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

[0088] 4 and 5, a slot includes a number of 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.

[0089] A carrier 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 may include up to N (e.g., 5) BWPs. Data communication is performed in the 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.

[0090] The NR system may support up to 400 MHz per component carrier (CC). If a terminal operating in such a wideband CC always operates with the radio frequency (RF) chip for the entire CC turned on, the terminal battery consumption may increase. Alternatively, considering various use cases (e.g., eMBB, URLLC, Mmtc, V2X, etc.) operating in one wideband CC, different numerologies (e.g., subcarrier spacing, etc.) may be supported for each frequency band in the CC. Alternatively, the capability for maximum bandwidth may differ for each terminal. In consideration of this, the base station may instruct the terminal to operate only in a part of the bandwidth rather than the entire bandwidth of the wideband CC, and the part of the bandwidth is defined as a bandwidth part (BWP) for convenience. The BWP may be composed of continuous RBs on the frequency axis and may correspond to one numerology (e.g., subcarrier spacing, CP length, slot / minislot interval).

[0091] Meanwhile, the base station can set multiple BWPs even within one CC set in the terminal. For example, a BWP occupying a relatively small frequency region can be set in the 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 set in some terminals for load balancing. Alternatively, in consideration of frequency domain inter-cell interference cancellation between adjacent cells, some spectrums of the entire bandwidth can be excluded and both BWPs can be set in the same slot. That is, the base station can set at least one DL / UL BWP in the terminal associated with the wideband CC. The base station can activate at least one DL / UL BWP among the DL / UL BWPs set at a specific time (by L1 signaling, MAC CE (Control Element), RRC signaling, etc.). The base station may also instruct (eg, by L1 signaling, MAC CE, or RRC signaling) switching to another configured DL / UL BWP.

[0092] Alternatively, when the timer value expires on a timer basis, the UE may switch to a predetermined DL / UL BWP. In this case, the activated DL / UL BWP is defined as an active DL / UL BWP. However, in a situation where the UE is performing an initial access process or before an RRC connection is set up, the UE may not be able to receive the configuration for the DL / UL BWP, and therefore the DL / UL BWP assumed by the UE in such a situation is defined as the initially active DL / UL BWP.

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

[0094] 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 transmitted and received 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 they transmit and receive.

[0095] When the terminal is powered on or newly enters a cell, the terminal performs an initial cell search such as synchronizing with the base station (S601). To this end, 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 obtain information such as a cell identifier (ID). After that, the terminal receives a physical broadcast channel (PBCH) from the base station to obtain broadcast information within the cell. Meanwhile, the terminal can receive a downlink reference signal (DL RS) during the initial cell search stage to check the downlink channel state.

[0096] 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, and can obtain more specific system information (S602).

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

[0098] After performing the above-mentioned procedures, the terminal 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 terminal receives Downlink Control Information (DCI) through the PDCCH. Here, the DCI includes control information such as resource allocation information for the terminal, and has different formats depending on its purpose.

[0099] Meanwhile, control information that a terminal transmits to a base station in an 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 in a PUSCH and / or a PUCCH.

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

[0101] [Table 5]

[0102] 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.), HARQ (Hybrid- Automatic Repeat and request) 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 of the DCI formats may be predefined.

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

[0104] DCI format 0_1 ​​is used to indicate to a terminal the scheduling of one or more PUSCHs in one cell or downlink feedback information of a configured grant (CG). Information included in DCI format 0_1 ​​is CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI (Semi-Persistent CSI RNTI), or MCS-C-RNTI and transmitted.

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

[0106] 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.), PUCCH related information (e.g., PUCCH power control, PUCCH resource indicator, etc.), and the control information included in each of the DCI formats may be pre-defined.

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

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

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

[0110] MBMS (multimedia broadcast / multicast service) method

[0111] MBMS may include a single frequency network (SFN) scheme in which multiple base station cells synchronize to transmit the same data via a physical multicast channel (PMCH), and a single cell point to multipoint (SC-PTM) scheme in which data is broadcast within the cell coverage via a PDCCH / PDSCH.

[0112] Here, the SFN method may be primarily used to provide broadcasting services to a wide area (e.g., an MBMS area) using resources that are semi-statically allocated in advance, and the SC-PTM method may be primarily used to provide broadcasting services only within a specific cell coverage area using dynamic resources.

[0113] The SC-PTM can provide one logical channel, SC-MCCH (Single Cell Multicast Control Channel) and one or more logical channels, SC-MTCH (Single Cell Multicast Traffic Channel). Such logical channels may be mapped to DL-SCH, which is a transmission channel, or / and PDSCH, which is a physical channel. The PDSCH that transmits the SC-MCCH or SC-MTCH data may be scheduled on the PDCCH indicated by the G-RNTI.

[0114] In this case, a temporary mobile group identify (TMGI) corresponding to a service ID may be one-to-one mapped to a specific G(group)-RNTI value. Therefore, when a base station provides multiple services, multiple G-RNTI values ​​may be assigned for SC-PTM transmission. One or multiple terminals may perform PDCCH monitoring using a specific G-RNTI to receive a specific service.

[0115] Furthermore, a DRX on-duration period can be set for SC-PTM only for a specific service / specific G-RNTI, in which case the terminal can wake up only during a specific on-duration period and perform PDCCH monitoring for the G-RNTI.

[0116] MBS (multicast broadcast service) based transmission and reception operation

[0117] In a basic wireless communication system, a base station may assign downlink (DL) SPS transmission resources to a specific terminal, which are repeated according to a set period, by configuring terminal-dedicated semi-persistent scheduling (SPS) configuration information for the specific terminal. In this case, a DCI transmitted on a terminal-dedicated PDCCH may indicate activation of a specific SPS configuration index, so that the terminal may repeatedly receive the SPS transmission resources according to a set period.

[0118] Such SPS transmission resources may be used for initial HARQ transmission, and the base station may allocate retransmission resources for a specific SPS configuration index using DCI transmitted on a terminal-dedicated PDCCH. For example, if the terminal reports a HARQ negative acknowledgement (NACK) for the SPS transmission resources, the base station may allocate retransmission resources in the DCI so that the terminal can receive DL retransmission.

[0119] The DCI transmitted on the UE-dedicated PDCCH may indicate deactivation (SPS release or SPS deactivation) of a specific SPS configuration index, in which case the UE may not receive the indicated SPS transmission resource. In this case, the CRC of the DCI for the activation / retransmission / deactivation may be scrambled with a Configured Scheduling RNTI (CS-RNTI).

[0120] In a wireless communication system (e.g., NR), a DL broadcast or DL ​​multicast transmission scheme may be applied to support an MBS similar to the above-mentioned MBMS. A base station may provide a point-to-multipoint (PTM) transmission scheme and a point-to-point (PTP) transmission scheme for DL ​​broadcast or DL ​​multicast transmission.

[0121] 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 can simultaneously receive the same group common PDCCH and group common PDSCH transmissions and decode the same MBS data.

[0122] In the PTP transmission method for MBS, the base station transmits a terminal-dedicated PDCCH and a terminal-dedicated PDSCH to a specific terminal, and only the specific terminal can receive the terminal-dedicated PDCCH and the terminal-dedicated PDSCH. In this case, when there are multiple terminals receiving the same MBS service, the base station can transmit the same MBS data to each terminal separately using different terminal-dedicated PDCCHs and terminal-dedicated PDSCHs.

[0123] In the PTM transmission method, a base station can transmit a plurality of group-common PDSCHs to a terminal, and the base station can receive the HARQ-ACK of the terminal for the group-common PDSCH using a PUCCH resource dedicated to the terminal.

[0124] In this case, if the TB (Transport Block) for the group-common PDSCH is successfully decoded, the terminal can transmit ACK as HARQ-ACK information. If the TB for the unicast PDSCH cannot be successfully decoded, the terminal can transmit NACK as HARQ-ACK information. Such a HARQ-ACK transmission method can be called ACK / NACK-based HARQ-ACK. The terminal can transmit ACK / NACK-based HARQ-ACK using the terminal-dedicated PUCCH resource.

[0125] As another example, assume that a NACK-only based HARQ-ACK scheme is configured for a group-common PDSCH. A terminal does not need to transmit a PUCCH when it needs to transmit an ACK. Then, the terminal can transmit a PUCCH only when it needs to transmit a NACK. Here, the terminal can transmit HARQ-ACK information including a NACK on a PUCCH using a group-common PUCCH resource.

[0126] In a basic wireless communication system, a terminal can receive unicast traffic on a terminal-specific unicast PDSCH and receive multicast traffic such as MBS on a group-common multicast PDSCH. In this case, the terminal can transmit a unicast HARQ-ACK for the unicast PDSCH and a multicast HARQ-ACK for the multicast PDSCH.

[0127] In this case, when a type 2 base codebook for multicast HARQ-ACK is configured and HARQ-ACK is activated or deactivated based on DCI, it is unclear how to configure the type 2 codebook according to a downlink assignment index (DAI) included in a group common DCI. Also, when a total DAI is indicated in UL DCI, it is unclear how to transmit / configure a multicast HARQ-ACK.

[0128] In addition, type 1 HARQ-AC has a drawback in that PUCCH overhead is large. Therefore, the following fall-back operation may be applied when PDSCH scheduling resources are scarce.

[0129] The terminal determines M for receiving the determined candidate PDSCH. A,cIt is assumed that, within an occasion, HARQ-ACK information is reported on the PUCCH only for SPS PDSCH release indicated by DCI format 1_0 with a counter DAI field value of 1 on the PCell, PDSCH reception scheduled by DCI format 1_0 with a counter DAI field value of 1 on the PCell, or SPS PDSCH reception.

[0130] In this case, the terminal may determine a HARQ-ACK codebook for only SPS PDSCH release, a HARQ-ACK codebook for only PDSCH reception, or a HARQ-ACK codebook for only SPS PDSCH reception according to the opportunity in each serving cell. Here, the counter DAI value of DCI format 1_0 may be according to Table 6.

[0131] [Table 6]

[0132] Otherwise, the fallback operation is not applied, and a general HARQ-ACK codebook determination method may be applied. As described above, in order for the terminal to perform fallback-based HARQ-ACK transmission, the base station may intentionally indicate a counter DAI field value of 1 for a HARQ-ACK transmission with a type 1 codebook configured.

[0133] In this case, in a basic wireless communication system, a fallback operation is supported when a terminal transmits a HARQ-ACK for a unicast PDSCH, but a fallback operation is not supported when a terminal transmits a HARQ-ACK for a multicast PDSCH.

[0134] Transmitting and receiving operations based on the CFR (common frequency resource) set for the terminal

[0135] One DL CFR (for an MBS) may include group-common PDCCH and group-common PDSCH transmission resources for MBS transmission and reception. One UL CFR may include HARQ-ACK PUCCH resources for group-common PDSCH reception. One CFR may be one MBS-specific BWP or one UE-specific BWP. Additionally or alternatively, one or more CFRs may be configured within one UE-specific BWP. One CFR has a connection relationship with one UE-specific BWP.

[0136] FIG. 7 is a diagram for explaining the timing of transmitting unicast HARQ-ACKs and multicast HARQ-ACKs for unicast PDCCH / PDSCHs and multicast PDCCHs / PDSCHs transmitted by FDM or TDM.

[0137] As shown in Fig. 7, the terminals can receive group-common PDCCH / PDSCH scheduled with different G-RNTIs (i.e., terminal group identifiers receiving MBS) by FDM or TDM. The base station can set a CFR, which is a frequency domain similar to the BWP, and the terminals can receive the group-common PDCCH / PDSCH by the CFR.

[0138] A UE in connected mode can activate one DL BWP to receive a unicast PDCCH / PDSCH, and can receive a group common PDCCH / PDSCH in a CFR associated with the activated DL BWP.

[0139] Since the CFR and its associated DL BWP overlap each other and the CFR of the serving cell is included in the active DL BWP of the serving cell, the terminal can receive all unicast PDSCHs and multicast PDSCHs transmitted in FDM or TDM.

[0140] If a terminal supports carrier aggregation (CA), the terminal can receive both unicast and multicast PDSCHs from multiple serving cells.

[0141] In this case, a unicast PDSCH opportunity may be transmitted in TDM with respect to a multicast PDSCH opportunity for G-RNTI #1, and may be transmitted in FDM with respect to a multicast PDSCH opportunity for G-RNTI #2.

[0142] A unicast PDSCH and a specific multicast PDSCH may be transmitted in the same or different serving cells, and multiple multicast PDSCHs may be transmitted in the same or different serving cells or in the same or different CFRs.

[0143] The base station can set (per G-RNTI, CFR, DL BWP, serving cell, or cell group) whether the unicast PDSCH and multicast PDSCH are transmitted on an FDM basis or on a TDM basis.

[0144] The base station may set "PUCCH-config" for each BWP or CFR, and may set k1 (for example, the number of slots from a slot where a PDSCH is scheduled to a PUCCH that transmits an ACK for the PDSCH) set by one "PUCCH-config". The base station may also set "PDSCH-config" for each BWP or CFR, and may set SLIV (start and length indicator value) by one "PDSCH-config". The SLIV is an indication field for the start symbol index and the number of symbols in a slot of the PDSCH and / or PUSCH, and may be carried on the PDCCH that schedules the PDSCH and / or PUSCH.

[0145] As shown in FIG. 8, in a basic wireless communication system, a terminal can perform type 1 codebook configuration for FDMed unicast and multicast having at least the following priorities for receiving one G(group)-RNTI for multicast:

[0146] - For a Type 1 HARQ-ACK codebook configuration for FDMed unicast and multicast with the same priority from the same TRP, the HARQ-ACK bits for all PDSCH opportunities for all slots for all serving cells for unicast may precede the HARQ-ACK bits for all PDSCH opportunities for all slots for all serving cells for multicast.

[0147] If the terminal reports a capability to support FDM-scheduled unicast and multicast in the same slot, the terminal may be semi-statically instructed to generate a Type 1 HARQ-ACK codebook in the FDM manner. Otherwise, the terminal may not expect that unicast and multicast will be scheduled in the FDM manner.

[0148] The terminal may perform the following steps to configure a type 1 codebook for FDM-based unicast transmission and multicast transmission for the same G-RNTI, as shown in FIG.

[0149] 1st stage - Generate sub-codebook #1 for unicast in every slot

[0150] 2nd stage - Generate another sub-codebook #2 for multicast in every slot

[0151] 3rd stage - append sub-codebook #2 to lower codebook #1

[0152] As a result, the order of the joint codebook may be (A, B, C, D, E, F, G, G).

[0153] The terminal may be configured to receive FDM-multiplexed unicast and multicast transmissions for multiple G-RNTIs for multicast, as shown in FIG.

[0154] As an example (alternative 1) of the present disclosure, in a type 1 codebook configuration for FDM-based unicast and multicast, when multiple G-RNTIs are configured for a terminal and "fdmed-Reception-Multicast" is configured, a HARQ-ACK sub-codebook for multicast may be configured as a sub-codebook for all G-RNTIs. A sub-codebook for each G-RNTI may be generated for each k1 and TDRA configuration for the G-RNTI.

[0155] The terminal may perform the following steps to configure a type-1 codebook for FDM-based unicast transmission and multicast transmission for two G-RNTIs, as shown in FIG.

[0156] 1st stage - Generate sub-codebook #1 for unicast in every slot

[0157] Phase 2 - Generate another sub-codebook #2 for multicast for all G-RNTIs in all slots

[0158] 3rd stage - append subcodebook#2 to subcodebook#1

[0159] As a result, the order of the joint codebook may be (A, B, C, D, E, F, G, H).

[0160] As another example (alternative 2) of the present disclosure, in a Type 1 codebook configuration for FDMed unicast and multicast, when multiple G-RNTIs are configured for a terminal and "fdmed-Reception-Multicast" is configured, the HARQ-ACK sub-codebook for multicast can be configured by appending sub-codebooks for each G-RNTI in ascending order of the G-RNTI values.

[0161] A sub-codebook for each G-RNTI may be generated for each k1 and TDRA setting for the G-RNTI. The maximum number of G-RNTIs configured in the terminal for FDM-based unicast and multicast type 1 codebooks may be based on UE capability E.

[0162] In FIG. 9, the terminal may perform the following steps to configure a type 1 codebook for FDM-based unicast transmission and multicast transmission for two G-RNTIs.

[0163] 1st stage - generate sub-codebook #1 for unicast in all slots,

[0164] 2nd stage - Generate another sub-codebook for multicast for each G-RNTI in every slot;

[0165] Generate sub-codebook #2-1 for G-RNTI value 1

[0166] Generate sub-codebook #2-2 for G-RNTI value 2

[0167] - Add sub-codebook #2-2 to sub-codebook #2-1 based on ascending order of G-RNTI values

[0168] 3rd step - Add subcodebook #2 to subcodebook #1

[0169] As a result, the order of the joint codebook may be (A, B, C, D, E, F, G, H).

[0170] In yet another example (Alternative 3) of the present disclosure, the terminal may determine a HARQ-ACK sub-codebook for multicast based on Alternative 2. However, if the UCI cannot accept the HARQ-ACK sub-codebook for multicast based on Alternative 2, the terminal may determine a HARQ-ACK sub-codebook for multicast based on Alternative 1.

[0171] Option 3A: If the UCI cannot accept the HARQ-ACK sub-codebook for multicast generated based on Alternative 2, the terminal may determine the HARQ-ACK sub-codebook for multicast based on Alternative 1. Otherwise, the terminal may determine the HARQ-ACK sub-codebook for multicast based on Alternative 2.

[0172] Option 3B: If the number of G-RNTIs that the terminal wishes to receive is equal to or greater than a threshold specified by the base station, the terminal may determine a HARQ-ACK sub-codebook for multicast based on Alternative 1. Otherwise, the terminal may determine a HARQ-ACK sub-codebook for multicast based on Alternative 2.

[0173] Option 3C: If the HARQ-ACK sub-codebook for multicast corresponds to a low priority of the G-RNTI(s), the terminal may determine the HARQ-ACK sub-codebook for multicast based on Alternative 1.

[0174] If the HARQ-ACK sub-codebook for multicast corresponds to a high priority of the G-RNTI(s), the terminal may determine the HARQ-ACK sub-codebook for multicast based on alternative 2.

[0175] Alternatively, if the HARQ-ACK sub-codebook for multicast corresponds to a high priority of the G-RNTI(s), the terminal may determine the HARQ-ACK sub-codebook for multicast based on Alternative 1.

[0176] If the HARQ-ACK sub-codebook for multicast corresponds to a low priority of the G-RNTI(s), the terminal may determine the HARQ-ACK sub-codebook for multicast based on alternative 2.

[0177] Option 3D: In the case of M-TRP, if the multicast HARQ-ACK sub-codebook corresponds to the first TRP, the terminal can determine the multicast HARQ-ACK sub-codebook based on alternative 1.

[0178] If the HARQ-ACK sub-codebook for multicast corresponds to the second TRP, the terminal may determine the HARQ-ACK sub-codebook for multicast based on alternative 2.

[0179] Option 3E: In the case of CA or double concatenation, if the HARQ-ACK sub-codebook for multicast corresponds to the first serving cell or the first serving cell group, the terminal can determine the HARQ-ACK sub-codebook for multicast based on alternative 1.

[0180] If the HARQ-ACK sub-codebook for multicast corresponds to the second serving cell or the second serving cell group, the terminal may determine the HARQ-ACK sub-codebook for multicast based on alternative 2.

[0181] The first serving cell group may be a secondary cell group and the second serving cell group may be a primary cell group, or vice versa. The first serving cell may be a SCell and the second serving cell may be a PCell (or a PSCell), or vice versa. The first serving cell may be a scheduling cell and the second serving cell may be a scheduled cell, or vice versa.

[0182] In addition to the unicast SPS configuration, the CFR configuration may include a group-common SPS configuration, where the group-common SPS may include a multicast SPS for connected terminals or a broadcast SPS for idle / inactive / connected terminals.

[0183] It is assumed that information for setting multiple group common SPSs (i.e., group common SPS) is received, or information for setting a group common SPS setting and a UE dedicated SPS (i.e., group common SPS setting and UE dedicated SPS) is received. In this case, a UE that receives DCI of CS-RNTI for PTP retransmission of SPS can distinguish different SPS settings according to the HARQ Process ID included in the DCI.

[0184] As an example, when a DCI in which a CRC is scrambled is received in a CS-RNTI, and the HPN value of the received DCI corresponds to a specific SPS setting index or a group common SPS setting, the terminal can determine / judge to retransmit a TB of an SPS PDSCH in which a PDSCH scheduled by the DCI corresponds to a specific SPS setting index or a group common SPS setting.

[0185] When distinguishing SPS configuration index or group-common SPS configuration based on HPN (i.e., HARQ Process ID), the base station can set different 'nrofHARQ-Processes' (i.e., the number of configured HARQ processes) and 'harq-ProcID-Offset' (i.e., an offset used to derive the HARQ process ID) for different SPS configurations, or for terminal-dedicated SPS and group-common SPS configurations.

[0186] That is, 'nrofHARQ-Processes' and 'harq-ProcID-Offset' are set for each SPS configuration index, and the terminal can determine the HARQ Process ID for a specific SPS transmission according to Equation 3 below.

[0187]

number

[0188] Additionally or alternatively, when multiple group common SPS configurations are configured, or when both group common SPS configuration and UE dedicated SPS configuration are configured, the group common CS-RNTI and the unicast CS-RNTI may be configured separately. In this case, the group common SPS and the unicast SPS may share the same HARQ process ID. That is, the group common SPS and the unicast SPS may overlap the same HARQ process ID.

[0189] Additionally or alternatively, the same CS-RNTI may be configured for the group common SPS configuration and the terminal dedicated SPS configuration, and a new indicator may be included in the DCI of the CS-RNTI to distinguish whether the corresponding transmission is a PTP retransmission or a unicast transmission. In this case, the new indicator of the DCI may be configured with 1 bit, but is not limited thereto. And, the new indicator of the DCI may indicate a group common SPS configuration index.

[0190] Additionally or alternatively, the same CS-RNTI may be configured for group-common SPS configuration and UE-specific SPS configuration, and group-common SPS transmission and UE-specific SPS transmission may be distinguished by the HARQ process ID included in the DCI of the CS-RNTI. In this case, the group-common SPS and the unicast SPS may use different HARQ processes (numbers).

[0191] According to the above-mentioned method, the terminal can receive the SPS as follows.

[0192] After a specific group common SPS is activated in a DCI whose CRC is scrambled with a specific G-CS-RNTI, the UE may store and decode the TB received via the group common SPS PDSCH in a HARQ process corresponding to a specific HPN value. The specific HPN value is the same as the HARQ Process ID corresponding to the group common SPS PDSCH resource.

[0193] Thereafter, the terminal can receive DCI whose CRC is scrambled with a terminal-specific CS-RNTI or C-RNTI, or can receive DCI whose CRC is scrambled with a specific G-CS-RNTI, from the base station.

[0194] If the received DCI indicates a retransmission resource and a specific HPN value, the UE can recognize that the retransmission resource is a retransmission resource for a HARQ process corresponding to the indicated HPN value, and can store the TB received on the retransmission resource in the HARQ process corresponding to the indicated HPN value and re-decode the TB.

[0195] In this case, the DCI for the UE-specific CS-RNTI or C-RNTI may be used to allocate PTP retransmission resources for the group common SPS, and the DCI for the specific G-CS-RNTI may be used to allocate PTM retransmission resources for the group common SPS. In this manner, the specific G-CS-RNTI and the UE-specific CS-RNTI may have an optional relationship as described below. The optional relationship as described below may be configured by the base station for the UE or may be predefined.

[0196] Option 1: A specific G-CS-RNTI may be mapped to a specific terminal specific CS-RNTI by configuration of the base station.

[0197] Option 2: The terminal-specific CS-RNTI of the terminal may be mapped to all G-CS-RNTIs for group common SPS.

[0198] Option 3: If there is an SPS configuration index indicated by a specific UE-specific CS-RNTI DCI, the G-CS-RNTI concatenated with the SPS configuration index may be mapped to a specific UE-specific CS-RNTI.

[0199] As described above, when a DCI whose CRC is scrambled in a C-RNTI indicates a specific HPN for which a group common SPS of the G-CS-RNTI is in use, the terminal may determine that the DCI schedules a unicast PDSCH and allow a TB received from the unicast PDSCH to replace a TB stored in the HARQ process for the specific HPN.

[0200] Additionally or alternatively, the terminal may determine that the DCI schedules a retransmission of a group-common SPS PDSCH, accumulate a TB received from the retransmitted PDSCH into a TB stored in the HARQ process for the particular HPN, and decode the TB.

[0201] An example of a UE-specific PDCCH activation command method for activating a group common SPS is as follows.

[0202] The unicast SPS and the group-common SPS use the same CS-RNTI, and the DCI for SPS activation can indicate the group-common SPS with 1-bit information. In this case, the HPN of the activation DCI may not be related to the SPS HARQ Process ID actually used.

[0203] In this case, the same SPS configuration index may be configured and used for both the group common SPS and the unicast SPS, i.e., the terminal can simultaneously activate the group common SPS and the unicast SPS having the same SPS configuration index.

[0204] Additionally or alternatively, the activation DCI may indicate that a group common SPS and a unicast SPS having the same SPS setting index are activated simultaneously, or the above one bit may indicate that only one of the group common SPS or the unicast SPS is activated.

[0205] Additionally or alternatively, the unicast SPS and the group-common SPS may use the same CS-RNTI, and the DCI for SPS activation may not include the above 1-bit information. In this case, the HPN value of the activation DCI may indicate the unicast SPS and the group-common SPS to be distinguished. For example, the unicast SPS and the group-common SPS may be mapped to different HPNs.

[0206] In this case, the same SPS configuration index is not mapped to the group common SPS and the unicast SPS at the same time, but may be mapped to only one of the group common SPS or the unicast SPS. A terminal can simultaneously activate a group common SPS and a unicast SPS having the same SPS configuration index.

[0207] Additionally or alternatively, the unicast SPS and the group-common SPS may use different CS-RNTIs, and the DCI for SPS activation may not include the above 1-bit information. In this case, the CS-RNTI value of the activation DCI may be indicated to distinguish the unicast SPS and the group-common SPS.

[0208] In the following, a fallback scheme for supporting the case where a terminal transmits both a unicast HARQ-ACK and a multicast HARQ-ACK will be described.

[0209] FIG. 10 is a diagram for explaining an uplink transmission operation of a terminal in a wireless communication system to which the present disclosure can be applied.

[0210] The terminal may receive configuration information related to a semi-static hybrid automatic repeat request (HARQ)-acknowledge (ACK) codebook for a physical downlink shared channel (PDSCH) from the base station (S1010).

[0211] As an example, the configuration information may include information for setting whether the PDSCH HARQ-ACK codebook is a semi-static codebook (i.e., a type 1 codebook) or a dynamic codebook (a type 2 codebook). As another example, the configuration information may include information for configuring a (semi-static or dynamic) HARQ-ACK codebook (e.g., k1 set, HARQ-ACK transmission mode, time / frequency resource configuration information, etc.).

[0212] The terminal may receive at least one downlink control information (DCI) including a downlink assignment index (DAI) field from the base station (S1020).

[0213] Each of the at least one DCI may be scrambled by a different or the same RNTI. For example, a portion of the at least one DCI may be CRC-scrambled by a G-CS-RNTI or a G-RNTI, and the remainder of the at least one DCI may be scrambled by a CS-RNTI, etc. However, this is merely one embodiment, and each of the at least one DCI may be scrambled by various types of RNTIs.

[0214] Also, each of the at least one DCI may include a DAI field (e.g., a first DAI field and / or a second DAI field). The DAI field may be set to indicate a specific value (e.g., 1), but may also be set to indicate a value other than the specific value.

[0215] When a first PDSCH that satisfies a specific condition is received from the base station among the multiple PDSCHs, the terminal can transmit HARQ-ACK information for the first PDSCH to the base station (S1030).

[0216] Specifically, when a first PDSCH that satisfies a specific condition is received (or detected) in multiple candidate PDSCH receiving opportunities, and other PDSCHs that satisfy a specific condition (e.g., a fallback condition) are not received (or detected), the terminal can independently transmit HARQ-ACK information (e.g., 1-bit HARQ-ACK information) for the first PDSCH to the base station.

[0217] As an example, the PDSCH that satisfies the specific condition may include a semi-persistent scheduling (SPS) group-common SPS PDSCH scrambled by a group (G)-RNTI (radio network temporary identifier) ​​or a configured scheduling (G-CS)-RNTI, or a group-common PDSCH scheduled by the at least one DCI CRC-scrambled to a G-RNTI or a G-CS-RNTI.

[0218] As another example of the present disclosure, based on the DAI field included in at least one DCI associated with multiple PDSCHs indicating a specific value (e.g., 1), the terminal may transmit a semi-static HARQ-ACK codebook including HARQ-ACK information for each of the multiple PDSCHs to the base station.

[0219] As an example, if a DAI field included in at least one DCI associated with a plurality of PDSCHs indicates a specific value (e.g., 1), the terminal may configure 1-bit HARQ-ACK information for each of the plurality of PDSCHs, and may configure a HARQ-ACK codebook with the 1-bit HARQ-ACK information for each of the plurality of PDSCHs and transmit the HARQ-ACK codebook to the base station.

[0220] As yet another example of the present disclosure, based on receiving a first PDSCH and a second PDSCH not satisfying a specific condition from the base station among the multiple PDSCHs, the terminal may transmit a semi-static codebook for the multiple PDSCHs to the base station. That is, when a PDSCH satisfying a fallback condition and a PDSCH not satisfying a fallback condition are received, the terminal may configure a full semi-static codebook for the multiple PDSCHs based on the k1 set and the TDRA configuration, and transmit the configured full semi-static codebook to the base station.

[0221] As yet another example of the present disclosure, the at least one DCI may include a first DCI and a second DCI. Based on the DAI field included in the first DCI indicating a specific value (e.g., 1) and the second DCI field indicating no specific value, the terminal may transmit a semi-static codebook for multiple PDSCHs to the base station.

[0222] For example, when the DAI field of the DCI associated with one G-RNTI indicates 1 and the DAI field of the DCI associated with another G-RNTI does not indicate 1, the terminal can configure a full semi-static codebook based on the k1 set and TDRA settings for multiple PDSCHs and transmit the configured full semi-static codebook to the base station.

[0223] Additionally or alternatively, the multiple PDSCHs may include a first PDSCH and a second PDSCH, where the first PDSCH is a multicast PDSCH scheduled by a multicast DCI among the at least one DCI, and the second PDSCH is a unicast PDSCH scheduled by a unicast DCI among the at least one DCI.

[0224] If the second PDSCH (i.e., unicast PDSCH) satisfies a certain condition, the terminal may configure HARQ-ACK information (e.g., 1-bit HARQ-ACK information) for the second PDSCH and transmit it to the base station. In this case, the terminal may concatenate the HARQ-ACK information for the first PDSCH and the HARQ-ACK information for the second PDSCH and transmit it to the base station.

[0225] However, this is only one embodiment, and the first PDSCH is a unicast PDSCH, and the DAI field of the DCI that schedules the first PDSCH among at least one DCI may indicate a specific value. In this case, the terminal may transmit HARQ-ACK information for the first PDSCH (e.g., 1-bit HARQ-ACK information) to the base station.

[0226] Additionally or alternatively, based on receiving a (single) multicast DCI CRC-scrambled by the G-RNTI or G-CS-RNTI from the base station among at least one DCI, the terminal can transmit HARQ-ACK information for the (single) multicast DCI to the base station.

[0227] Here, the single multicast DCI may include a DAI value for activating or releasing a group-common SPS PDSCH among a plurality of PDSCHs.

[0228] FIG. 11 is a diagram for explaining an uplink receiving operation of a base station in a wireless communication system to which the present disclosure can be applied.

[0229] The base station may transmit configuration information related to a semi-static (or Type-1) HARQ-ACK codebook for the PDSCH to the terminal (S1110).

[0230] That is, the base station can transmit to the terminal configuration information related to the HARQ-ACK codebook for the PDSCH transmitted by the terminal (e.g., the type of the HARQ-ACK codebook, resources and modes for transmitting HARQ-ACK information, etc.).

[0231] The base station may transmit at least one DCI including a DAI field to the terminal (S1120).

[0232] When a first PDSCH that satisfies a specific condition is transmitted to the terminal among the multiple PDSCHs, the base station can receive HARQ-ACK information for the first PDSCH from the terminal (S1130).

[0233] That is, based on the terminal detecting / receiving only the first PDSCH that satisfies a specific condition among multiple candidate PDSCH receiving opportunities, the base station can receive HARQ-ACK information for the first PDSCH (e.g., 1-bit HARQ-ACK information) from the terminal.

[0234] The operations and parameters associated with S1010, S1020, and S1030 may correspond to the operations and parameters associated with S1110, S1120, and S1130.

[0235] In the following, a fallback scheme for supporting the case where a terminal transmits both a unicast HARQ-ACK and a multicast HARQ-ACK will be described in detail.

[0236] Example 1: Fallback scheme of Type-1 codebook for multicast HARQ-ACK

[0237] When a type 1 codebook is configured, the terminal may perform the following fallback operation for each configured G-RNTI / G-CS-RNTI or for all configured G-RNTIs / G-CS-RNTIs.

[0238] For the type 1 HARQ-ACK codebook configuration for the G-RNTI or G-CS-RNTI that the terminal intends to receive among the candidate PDSCH reception opportunities:

[0239] If the terminal detects only a group-common SPS PDSCH scrambled by a given G-RNTI or G-CS-RNTI, only a group-common PDSCH scheduled by a multicast DCI format 4-1 having a CRC scrambled by a given G-RNTI or G-CS-RNTI and a counter DAI value of 1, only a single multicast DCI format 4-1 having a CRC scrambled by a given G-RNTI or G-CS-RNTI and a DAI value of 1 for activating a group-common SPS PDSCH, or only a single multicast DCI format 4-1 having a CRC scrambled by a G-RNTI or G-CS-RNTI and a DAI value of 1 for deactivating a group-common SPS PDSCH;

[0240] The terminal may determine that a corresponding HARQ-ACK sub-codebook for a given G-RNTI or G-CS-RNTI includes only a single HARQ-ACK information bit for a group-common SPS PDSCH, a group-common PDSCH, a single DCI format 4-1 for a group-common SPS PDSCH activation, or a single DCI format 4-1 for a group-common SPS PDSCH deactivation (i.e., a fallback operation for a type 1 codebook configuration);

[0241] If not;

[0242] The terminal may determine the HARQ-ACK sub-codebook for a given G-RNTI or G-CS-RNTI by the k1 set and a TDRA configuration (ie, a general type-1 codebook configuration).

[0243] That is, in the above-described operation, the fallback condition of the terminal for a candidate PDSCH reception opportunity relates to whether the terminal detects only a group-common SPS PDSCH scrambled by a given G-RNTI or G-CS-RNTI, only a group-common PDSCH scheduled by multicast DCI format 4-1 having a CRC scrambled by a given G-RNTI or G-CS-RNTI and a counter DAI value of 1, only a single multicast DCI format 4-1 having a CRC scrambled by a given G-RNTI or G-CS-RNTI and a DAI value of 1 for activating the group-common SPS PDSCH, or only a single multicast DCI format 4-1 having a CRC scrambled by a G-RNTI or G-CS-RNTI and a DAI value of 1 for deactivating the group-common SPS PDSCH.

[0244] As an embodiment of the present disclosure, an additional fallback condition may be applied to the above-mentioned fallback operation, i.e., a terminal receiving a PDSCH for one or more G-RNTIs may perform a fallback operation according to the additional fallback condition described below.

[0245] Option 1: The terminal can configure the HARQ-ACK sub-codebook with a single HARQ-ACK information bit for each G-RNTI or G-CS-RNTI only if all of the respective fallback conditions for all configured G-RNTIs or G-CS-RNTIs are met, and can transmit the configured HARQ-ACK sub-codebook (to the base station).

[0246] In this case, the terminal may configure one HARQ-ACK sub-codebook for all G-RNTIs or G-CS-RNTIs, or the terminal may configure each HARQ-ACK sub-codebook for each G-RNTI or G-CS-RNTI.

[0247] Additionally or alternatively, if there is a G-RNTI or G-CS-RNTI that does not satisfy the fallback condition, the terminal can configure a type-1 codebook with k1 set and TDRA settings for all G-RNTIs or G-CS-RNTIs and transmit (to the base station) the configured HARQ-ACK sub-codebook.

[0248] Option 2: For each G-RNTI or G-CS-RNTI that satisfies the fallback condition, the terminal can configure a HARQ-ACK sub-codebook with a single HARQ-ACK information bit and transmit the configured HARQ-ACK sub-codebook (to the base station).

[0249] Here, the terminal can configure a full type-1 codebook according to the K1 set and TDRA setting for a G-RNTI or G-CS-RNTI that does not satisfy the fallback condition, and transmit the configured HARQ-ACK sub-codebook (to the base station).

[0250] Option 2-1: If the fallback conditions are met for all G-RNTIs or there is no reception that does not meet the fallback conditions for other G-RNTIs, the terminal can perform fallback operation independently only for that G-RNTI.

[0251] That is, the terminal can configure the HARQ-ACK sub-codebook with a single HARQ-ACK information bit for the G-RNTI or G-CS-RNTI, and transmit the configured HARQ-ACK sub-codebook (to the base station).

[0252] Additionally or alternatively, the terminal may configure a full type-1 codebook with the K1 set and TDRA settings for the remaining G-RNTIs or G-CS-RNTIs.

[0253] Additionally or alternatively, if there is reception where the fallback condition is met for a particular G-RNTI but the fallback condition is not met for other G-RNTIs, the terminal may configure an entire type-1 codebook with k1 set and TDRA settings for all G-RNTIs.

[0254] Option 2-2: When the DAI field of the DCI indicates 1 for only one G-RNTI and no DAI or DCI is received for the other G-RNTIs, the terminal can configure the HARQ-ACK sub-codebook with a single HARQ-ACK information bit for each of all G-RNTIs and G-CS-RNTIs and transmit the configured HARQ-ACK sub-codebook (to the base station). That is, the terminal can perform a fallback operation.

[0255] Otherwise, the terminal does not need to perform a fallback operation. That is, the terminal can configure an entire type 1 codebook by the k1 set and TDRA configuration for all G-RNTIs. Therefore, if the DAI fields for all G-RNTIs indicate 1 in the DCI, the terminal does not need to perform a fallback operation.

[0256] Option 2-3: The terminal can perform fallback operation for all G-RNTIs only if the DAI fields of the respective DCIs for all G-RNTIs indicate 1. That is, the terminal can configure the corresponding HARQ-ACK sub-codebook with a single HARQ-ACK information bit for each of all G-RNTIs and G-CS-RNTIs, and transmit the configured HARQ-ACK sub-codebook (to the base station).

[0257] Otherwise (i.e., if the DAI fields of each DCI for all G-RNTIs do not indicate all 1), the terminal does not need to perform a fallback operation, i.e., the terminal may configure the entire type-1 codebook by the K1 set and TDRA setting for all G-RNTIs.

[0258] Option 2-4: When one multicast sub-codebook is configured for all G-RNTIs configured in the Type 1 codebook, if a fallback condition is met for one or more G-RNTIs or G-CS-RNTIs (e.g., if the DAI field of the DCI indicates 1), the terminal can perform fallback operations for all G-RNTIs and G-CS-RNTIs configured as multicast, regardless of whether it receives DAI or DCI for other G-RNTIs.

[0259] That is, for all G-RNTIs and G-CS-RNTIs set as multicast, the terminal can construct a HARQ-ACK sub-codebook with each corresponding single HARQ-ACK information bit (e.g., a single HARQ-ACK information bit corresponding to each of all G-RNTIs and G-CS-RNTIs) and transmit the constructed HARQ-ACK sub-codebook (to the base station).

[0260] As an example of the present disclosure, it is assumed that G-RNTI-specific sub-codebooks are configured for multiple G-RNTIs in a type-1 codebook.

[0261] If one G-RNTI or G-CS-RNTI satisfies a fallback condition (e.g., if the DAI field of the DCI indicates 1), the terminal may perform a fallback operation for the G-RNTI or G-CS-RNTI. That is, the terminal may configure the HARQ-ACK sub-codebook with a single HARQ-ACK information bit for each of the G-RNTI or G-CS-RNTI.

[0262] When each of multiple G-RNTIs or G-CS-RNTIs satisfies a fallback condition (for example, when the DAI field of each DCI indicates 1), the terminal can perform a fallback operation for each G-RNTI or G-CS-RNTI. That is, the terminal can configure a corresponding HARQ-ACK sub-codebook by a single HARQ-ACK information bit for each of the G-RNTIs or G-CS-RNTIs.

[0263] When one or more other G-RNTIs or G-CS-RNTIs do not satisfy a fallback condition (for example, the DAI field of the DCI does not indicate 1), the terminal does not need to perform a fallback operation for each of the G-RNTIs or G-CS-RNTIs. That is, the terminal can configure a corresponding entire type-1 HARQ-ACK sub-codebook for each of the G-RNTIs or G-CS-RNTIs.

[0264] In this case, a codebook may be constructed by concatenating HARQ-ACK sub-codebooks for one or more G-RNTIs for which fallback operation is or is not performed in ascending or descending order of G-RNTI values, and the terminal may transmit the constructed codebook (to the base station).

[0265] As an example of the present disclosure, when one multicast sub-codebook is configured for all G-RNTIs set in a Type 1 codebook, if a fallback instruction is received for a G-RNTI DCI (i.e., a DCI CRC-scrambled by the G-RNTI), the terminal can perform a fallback operation for the entire multicast.

[0266] However, when a sub-codebook is configured for each of a plurality of G-RNTIs, if a fallback instruction is received by a DCI for each G-RNTI, the terminal can perform a fallback operation only for that G-RNTI.

[0267] Option 3: When both unicast and multicast are configured as type 1 codebooks and the fallback conditions are met for all configured G-RNTIs that the terminal is interested in, if the fallback conditions are met for unicast, the terminal can perform a fallback operation. Thus, the terminal can concatenate a single HARQ-ACK information bit for unicast and a single HARQ-ACK information bit for each G-RNTI and send it to the base station.

[0268] Otherwise, the terminal does not need to perform a fallback operation. That is, the terminal can configure a type 1 sub-codebook with the K1 set and TDRA setting for unicast and configure a type 1 sub-codebook with the K1 set and TDRA setting for all G-RNTIs. Then, the terminal can concatenate the type 1 sub-codebooks for each of the unicast and all G-RNTIs and transmit it (to the base station).

[0269] In the description of this disclosure, "unicast" may include unicast transmissions and / or HARQ-ACK information (or / and codebooks) for unicast transmissions, and "multicast" may include multicast transmissions and / or HARQ-ACK information (or / and codebooks) for multicast transmissions.

[0270] Option 4: When both unicast and multicast are configured with a type 1 codebook, if the counter DAI field of the unicast DCI indicates a specific value, the terminal can perform a fallback operation. Therefore, the terminal can concatenate a single HARQ-ACK information bit for unicast and a single HARQ-ACK information bit for each G-RNTI and transmit it (to the base station).

[0271] Otherwise, the terminal does not need to perform fallback operation. That is, the terminal can configure a type 1 sub-codebook with k1 set and TDRA setting for unicast, and configure a type 1 sub-codebook with K1 set and TDRA setting for all G-RNTIs. The terminal can concatenate the sub-codebooks for each of the unicast and all G-RNTIs, and transmit it (to the base station).

[0272] Option 5: When unicast and multicast are both configured with a type 1 codebook, the terminal may perform fallback operation when the counter DAI field of the unicast DCI indicates 1 and there is no transmission for multicast.

[0273] Therefore, the terminal can concatenate the single HARQ-ACK information bit for the unicast and the single HARQ-ACK information bit for each G-RNTI and transmit it (to the base station).

[0274] Additionally or alternatively, if unicast and multicast are both configured with a type 1 codebook, the terminal may perform fallback operation if the counter DAI field of the multicast DCI indicates 1 and there is no unicast transmission.

[0275] Therefore, the terminal can concatenate the single HARQ-ACK information bit for the unicast and the single HARQ-ACK information bit for each G-RNTI and transmit it (to the base station).

[0276] Option 6: Assume that unicast and multicast are configured with separate types of codebooks.

[0277] If a type 1 codebook is configured for unicast and the counter DAI field of the unicast DCI indicates 1, the terminal can perform fallback operation only for unicast, regardless of whether multicast is transmitted. Therefore, the terminal can set a single HARQ-ACK information bit for unicast and configure a sub-codebook for unicast.

[0278] If a type 1 codebook is configured for multicast only and the counter DAI field of the multicast DCI indicates 1, the terminal can perform fallback operation only for multicast, regardless of whether unicast is transmitted or not. Therefore, the terminal can configure a single HARQ-ACK information bit for the configured G-RNTI and configure a sub-codebook for multicast.

[0279] In this case, the terminal may configure a sub-codebook for multicast in one or more of the above options. For example, the terminal may configure a corresponding HARQ-ACK sub-codebook with a single HARQ-ACK information bit for each of all G-RNTIs and G-CS-RNTIs or one or more G-RNTIs or G-CS-RNTIs, and transmit the configured HARQ-ACK sub-codebook.

[0280] Example 2: Downlink Assignment Index (DAI) Scheme of DCI for Constructing Multicast HARQ-ACK Codebook

[0281] The terminal can configure a type-2 codebook in the manner described below through base station configuration.

[0282] The base station can use DCI to allocate UL PUSCH resources or schedule DL PDSCH transmission to the terminal. In this case, the DCI transmitted by the base station to allocate UL PUSCH resources is abbreviated as UL DCI, and the DCI transmitted by the base station to schedule DL PDSCH transmission is abbreviated as DL DCI.

[0283] The terminal receives a PUCCH resource indicator (PRI) in the group-common DCI or terminal-specific DCI, and can transmit HARQ-ACK information for a PDSCH scheduled by the group-common DCI or terminal-specific DCI on a PUCCH resource indicated by the PRI.

[0284] If the PUCCH transmission overlaps with a PUSCH transmission, the terminal may transmit a PUSCH instead of a PUCCH and transmit the UCI including the HARQ-ACK information piggybacked on the PUSCH.

[0285] When a type-2 codebook is configured for HARQ-ACK of a multicast PDSCH, a group common DCI for scheduling a group common PDSCH for a specific G-RNTI may include a counter DAI and a total DAI. The counter DAI indicates the order of a PDSCH currently scheduled for a specific G-RNTI, and the total DAI indicates the total number of PDSCHs scheduled to date for a specific G-RNTI.

[0286] A TB transmitted by a PDSCH scheduled by a group common DCI may be retransmitted by PTP retransmission. In this case, the terminal may obtain PDSCH transmission information for the TB from a terminal-specific DL DCI whose CRC is scrambled by the C-RNTI. In this case, the DL DCI may include a counter DAI and an overall DAI for the G-RNTI corresponding to the TB.

[0287] For example, assume that the same TB is scheduled twice by two group-common DCIs and scheduled a third time by PTP retransmission. In this case, the first two group-common DCIs are transmitted with the [counter DAI, overall DAI] values ​​set to [0,0] and [1,1], respectively, and the terminal-specific DCI for the PTP retransmission may be transmitted with the [2,2] following the value of the group-common DCI.

[0288] Additionally or alternatively, the DAI value of the DCI for PTP retransmission may be set separately from the value of the group common DCI. For example, the [counter DAI, total DAI] value of the DCI for PTP retransmission may be set following the [counter DAI, total DAI] value of the previously transmitted unicast DCI.

[0289] The UL DCI, the CRC of which is scrambled by the C-RNTI, may include an overall DAI for the G-RNTI transmission. For example, when the UL DCI is transmitted immediately after two group common DCIs, the overall DAI of the UL DCI may be set to 1. When the UL DCI is transmitted immediately after a PTP retransmission, the overall DAI of the UL DCI may be set to 2.

[0290] That is, in consideration of the case where the UE cannot receive DL DCI transmitted immediately before the UL DCI, the base station can indicate the entire DAI for UCI transmission of the PUSCH in the UL DCI.

[0291] Unicast and multicast HARQ-ACKs with the same priority may be multiplexed onto the same PUSCH. In this case, the DCI scheduling PUSCH may include the UL DAI field as follows:

[0292] When the unicast and multicast HARQ-ACK codebooks are both Type 1, the following options 1-1, 1-2, and 1-3 may be applied.

[0293] Option 1-1: A 1-bit UL DAI with value "1" may indicate multiplexing of unicast and multicast HARQ-ACK codebooks onto the same PUSCH.

[0294] Option 1-2: The 2-bit UL DAI can separately indicate whether unicast and / or multicast HARQ-ACK codebooks are multiplexed into the same PUSCH.

[0295] When only one sub-codebook is configured for all configured G-RNTIs, one bit of the 2-bit UL DAI indicating whether or not a multicast HARQ-ACK codebook is multiplexed into the same PUSCH may be applied to all configured G-RNTIs.

[0296] When N different sub-codebooks are configured for N different configured G-RNTIs, one bit of the 2-bit UL DAI indicating whether a multicast HARQ-ACK codebook is multiplexed into the same PUSCH may be applied to only one G-RNTI among the configured G-RNTIs. Here, the G-RNTI may have a higher priority, or may be indicated by the network, or the G-RNTI may correspond to the most recently scheduled PDSCH.

[0297] Option 1-3: An N+1-bit UL DAI can individually indicate whether a unicast and / or multicast HARQ-ACK codebook is multiplexed into the same PUSCH. When N different sub-codebooks are configured for N different configured G-RNTIs, an N-bit UL DAI indicating whether a multicast HARQ-ACK codebook is multiplexed into the same PUSCH may be applied to the N different configured G-RNTIs, respectively.

[0298] That is, one bit of the UL DAI can be applied to one single G-RNTI to indicate whether or not the multicast HARQ-ACK sub-codebook applicable to the G-RNTI is multiplexed into the same PUSCH.

[0299] As an example of the present disclosure, when both the unicast and multicast HARQ-ACK codebooks are set to type 2, option 2-1 and option 2-2 may be applied.

[0300] Option 2-1: 2-bit UL DAI is applicable to any of the HARQ-ACK codebooks.

[0301] Option 2-2: In addition to the 2-bit UL DAI for unicast, a 2-bit UL DAI may be included in the DCI for multicast.

[0302] Whether a single UL DAI field applies to all G-RNTIs or a separate UL DAI field applies to each configured G-RNTI may be configured by the base station or may be predefined.

[0303] As an example of the present disclosure, it is assumed that the unicast and multicast HARQ-ACK codebooks are set as a type 1 codebook and a type 2 codebook, respectively.

[0304] In this case, a 1-bit UL DAI for unicast may be included in the DCI, and the 1-bit UL DAI may indicate whether a unicast HARQ-ACK codebook is multiplexed into the same PUSCH.

[0305] And, a 2-bit UL DAI for multicast may be further included in the DCI, and the 2-bit UL DAI may indicate the number of HARQ-ACK bits for the multicast type 2 codebook.

[0306] As yet another example of the present disclosure, assume that the unicast and multicast HARQ-ACK codebooks are set as a type 2 codebook and a type 1 codebook, respectively.

[0307] In this case, a 1-bit UL DAI for multicast may be included in the DCI, and the 1-bit UL DAI may indicate whether a multicast HARQ-ACK codebook is multiplexed into the same PUSCH.

[0308] When only one sub-codebook is configured for all configured G-RNTIs, one bit of the 2-bit UL DAI indicating whether or not a multicast HARQ-ACK codebook is multiplexed into the same PUSCH may be applied to all configured G-RNTIs.

[0309] When N different sub-codebooks are configured for N different configured G-RNTIs, one bit of the 2-bit UL DAI indicating whether a multicast HARQ-ACK codebook is multiplexed into the same PUSCH may be applied to only one G-RNTI among the configured G-RNTIs, where the G-RNTI may have a higher priority. The G-RNTI may be indicated by the network and may correspond to the most recently scheduled PDSCH.

[0310] And, a 2-bit UL DAI for unicast may be further included in the DCI, and the 2-bit UL DAI may indicate the number of HARQ-ACK bits for the unicast type 2 codebook.

[0311] Example 2-1: Configuration and transmission / reception method of UL DCI with separate overall DAI for unicast and overall DAI for multicast

[0312] The UL DCI may include an overall DAI for multicast for multicast HARQ-ACK, apart from an overall DAI for unicast for unicast HARQ-ACK, as follows:

[0313] Method 1-1: Multiple bits in the DAI field of the UL DCI can indicate the overall DAI for unicast and the overall DAI for multicast separately.

[0314] As an example, the N LSB bits and the M MSB bits of the first or second DAI field of DCI0_1 can separately indicate the overall DAI for unicast and the overall DAI for multicast, respectively.

[0315] Additionally or alternatively, each of the N MSB bits and M LSB bits of the first or second DAI field of DCI0_1 can separately indicate the overall DAI for unicast and the overall DAI for multicast, respectively.

[0316] Method 1-2: A reserved field or a specific field in the UL DCI can indicate the overall DAI for multicast.

[0317] As an example, the "ChannelAccess-CPext" field of DCI 0_1 can indicate the overall DAI for multicast.

[0318] When a terminal is receiving PDSCHs for multiple G-RNTIs, the UL DCI can indicate the overall DAI value for multicast as an option described later.

[0319] Option 1: The UL DCI may indicate the sum of the overall DAI values ​​for all G-RNTIs that the terminal intends to receive or has reported an interest in.

[0320] For example, assume that the terminal reports to the base station that it intends to receive G-RNTI #1 and G-RNTI #2. If the current overall DAI for G-RNTI #1 is 2 and the current overall DAI for G-RNTI #2 is 3, the overall DAI of the UL DCI can indicate 5, which is 2+3.

[0321] Option 2: The UL DCI may indicate an individual overall DAI value for each G-RNTI that the terminal intends to receive or has reported an interest in. That is, the UL DCI may indicate an overall DAI value for each G-RNTI.

[0322] As an example, assume that the terminal reports to the base station that it intends to receive G-RNTI #1 and G-RNTI #2. If the current total DAI for G-RNTI #1 is 2 and the current total DAI for G-RNTI #2 is 3, the UL DCI includes two separate total DAIs, and the total DCIs can indicate 2 and 3, respectively.

[0323] An individual total DAI value may be indicated in one field, and multiple total DAI values ​​may be concatenated within one field to form one bit string or bitmap.

[0324] As an example, assume that the total DAI values ​​for two different G-RNTIs are each N bits. A bit string or bitmap may be configured such that the total DAI value for a lower G-RNTI value corresponds to N LSB bits or N MBS bits, and the total DAI value for a higher G-RNTI value corresponds to N MSB bits or N LBS bits.

[0325] It may not be necessary to indicate separate overall DAI values ​​for all G-RNTIs due to limited field size, etc. In this case, the base station may indicate the overall DAI for each G-RNTI as an option described below.

[0326] Option 2-1: The base station can indicate the entire DAI for each G-RNTI up to the maximum number of G-RNTIs.

[0327] As an example, if the maximum number of G-RNTIs is set to 2 in the RRC message and the terminal reports to the base station that it intends to receive G-RNTI #1, G-RNTI #2, and G-RNTI #3, the base station can configure the UL DCI to indicate only the overall DAI for the two G-RNTIs among G-RNTI #1, G-RNTI #2, and G-RNTI #3 that have the higher or lower G-RNTI value, respectively.

[0328] Alternatively, if the maximum number of G-RNTIs is set to 2 in the RRC message and the terminal reports to the base station that it intends to receive G-RNTI #1, G-RNTI #2, and G-RNTI #3, the base station can configure the UL DCI to indicate only the overall DAI for the two G-RNTIs with the highest priority among G-RNTI #1, G-RNTI #2, and G-RNTI #3.

[0329] Alternatively, when the maximum number of G-RNTIs is set to 2 in the RRC message, if the terminal reports to the base station that it intends to receive G-RNTI #1, G-RNTI #2, and G-RNTI #3, the base station can configure the UL DCI to indicate only the overall DAI for two G-RNTIs, among G-RNTI #1, G-RNTI #2, and G-RNTI #3, that were pre-specified in the RRC message.

[0330] Option 2-2: UL DCI can indicate the entire DAI per G-RNTI only for a selected portion of G-RNTIs.

[0331] For example, if the terminal reports to the base station that it intends to receive G-RNTI #1, G-RNTI #2, and G-RNTI #3, the base station can configure the UL DCI to indicate only the overall DAI for each of the two G-RNTIs notified to the terminal in the RRC message. Therefore, the overall DAI for the unselected G-RNTIs does not need to be included in the UL DCI.

[0332] Alternatively, if the terminal reports to the base station that it intends to receive G-RNTI #1, G-RNTI #2, and G-RNTI #3, the terminal can recognize that only the overall DAI for the two G-RNTIs with the higher or lower G-RNTI values ​​is indicated in the UL DCI (even without the base station informing it).

[0333] Alternatively, when the terminal reports to the base station that it intends to receive G-RNTI #1, G-RNTI #2, and G-RNTI #3, the terminal can recognize (without the base station informing it) that only the overall DAI for the G-RNTI with the highest priority (e.g., HP) is indicated in the UL DCI.

[0334] Option 3: The UL DCI may indicate only the overall DAI value that has the highest value among the individual overall DAI values ​​for each of the G-RNTIs that the terminal intends to receive or has reported an interest in.

[0335] As an example, assume that the UE reports to the base station that it intends to receive G-RNTI #1 and G-RNTI #2. If the current overall DAI for G-RNTI #1 is 2 and the current overall DAI for G-RNTI #2 is 3, the UL DCI may indicate 3, which is the highest overall DAI value of the two. In this case, the UL DCI may further indicate an index for G-RNTI #2.

[0336] Option 4: All G-RNTIs that the terminal reports it intends to receive or is interested in may be grouped into multiple G-RNTI groups, and an overall DAI may be indicated for each G-RNTI group.

[0337] For example, if the terminal reports to the base station that it intends to receive G-RNTI #1, G-RNTI #2, and G-RNTI #3, the base station can group G-RNTI #1 and G-RNTI #2 into the first G-RNTI group and specify G-RNTI #3 as the second G-RNTI group in an RRC message. The base station can then configure UL DCI to indicate the overall DAI for the two G-RNTI groups, respectively.

[0338] In this case, the overall DAI value of the first G-RNTI group can indicate the sum of the overall DAI values ​​for all G-RNTIs in the group, as in option 1.

[0339] Alternatively, the overall DAI value of the first G-RNTI group may indicate the highest overall DAI value for all G-RNTIs in the group, as in option 3.

[0340] In this case, the overall DAI value of the second G-RNTI group including only one G-RNTI may be the same as the overall DAI value of G-RNTI #3.

[0341] When there is a missing overall DAI value of the G-RNTI due to the overall DAI indication method of the UL DCI, the terminal can configure an actual type 2-based HARQ-ACK codebook based on the overall DAI of the DL DCI.

[0342] Example 2-2: UL DCI method combining global DAI for unicast and global DAI for multicast

[0343] In this case, the UL DCI may be indicated as an option described below by combining the unicast overall DAI for the unicast HARQ-ACK and the multicast overall DAI for the multicast HARQ-ACK.

[0344] Meanwhile, instead of the UL DCI, the following optional DAI value may be transmitted to the terminal in the group common MAC CE. In this case, the PDSCH resource for transmitting the group common MAC CE may be allocated by the UL DCI.

[0345] Option 1: The UL DCI may indicate the sum of the overall DAI value of all G-RNTIs that the terminal intends to receive or has reported an interest in and the overall DAI value for unicast transmissions.

[0346] As an example, assume that the terminal reports to the base station that it intends to receive G-RNTI #1 and G-RNTI #2. If the current overall DAI for G-RNTI #1 is 2, the current overall DAI for G-RNTI #2 is 3, and the current overall DAI for unicast is 1, the overall DAI of the UL DCI may indicate 6, which is 2+3+1.

[0347] Option 2: The UL DCI can indicate an individual overall DAI value for each G-RNTI that the terminal intends to receive or reports an interest in, and an overall DAI value for unicast separately. That is, the UL DCI can indicate an overall DAI value for each G-RNTI and an overall DAI value for unicast, respectively.

[0348] For example, assume that the terminal reports to the base station that it intends to receive G-RNTI #1 and G-RNTI #2. If the current overall DAI for G-RNTI #1 is 2, the current overall DAI for G-RNTI #2 is 3, and the current overall DAI for unicast is 1, the UL DCI includes three overall DAIs individually, and the three overall DAIs can indicate 1, 2, and 3, respectively.

[0349] An individual total DAI value may be indicated in one field, and multiple total DAI values ​​may be concatenated within one field to form one bit string or bitmap.

[0350] For example, assume that the total DAI values ​​for two different G-RNTIs are each N bits. A bit string or bitmap may be configured so that the total DAI value for the lower G-RNTI value corresponds to N LSB bits or N MBS bits, and the total DAI value for the higher G-RNTI value corresponds to N MSB bits or N LBS bits. Then, the total DAI value for unicast may be concatenated and a bit string or bitmap may be configured so that it corresponds to the final bits.

[0351] It may not be necessary to indicate all the overall DAI values ​​due to a limited field size, etc. In this case, the base station may indicate the overall DAI for unicast and the overall DAI for each G-RNTI as an option described below.

[0352] Option 2-1: The base station can instruct the terminal on the overall DAI for each G-RNTI up to the maximum number of G-RNTIs.

[0353] As an example, assume that the terminal reports to the base station that it intends to receive G-RNTI #1, G-RNTI #2, and G-RNTI #3 when the maximum G-RNTI number is set to 2 in the RRC message. The base station can configure the UL DCI to indicate only the overall DAI for two G-RNTIs having higher or lower G-RNTI values ​​among G-RNTI #1, G-RNTI #2, and G-RNTI #3. Furthermore, the UL DCI can be configured by the base station to indicate or not indicate the overall DAI for unicast at all.

[0354] Alternatively, if the maximum number of G-RNTIs is set to 2 in the RRC message and the terminal reports to the base station that it intends to receive G-RNTI#1, G-RNTI#2, and G-RNTI#3, the base station can configure the UL DCI to indicate only the overall DAI for the two G-RNTIs with the highest priority.

[0355] Additionally or alternatively, the UL DCI may be configured by the base station to indicate both or not all of the global DAI for unicast, or may be configured to indicate only the global DAI for the unicast or G-RNTI with higher priority according to the priority for the unicast and G-RNTI, respectively.

[0356] Additionally or alternatively, assume that the terminal reports to the base station that it intends to receive G-RNTI #1, G-RNTI #2, and G-RNTI #3 when the maximum number of G-RNTIs is set to 2 in the RRC message. The base station can configure the UL DCI to indicate only the overall DAI for two of those G-RNTIs that are pre-specified in the RRC message. Furthermore, the UL DCI may be configured by the base station to indicate or not indicate the overall DAI for unicast as well.

[0357] Option 2-2: The base station may indicate the entire DAI for each G-RNTI only for some selected G-RNTIs. In addition, the UL DCI may be configured to indicate or not indicate the entire DAI for unicast by the base station.

[0358] As an example, if the terminal reports to the base station that it intends to receive G-RNTI #1, G-RNTI #2, and G-RNTI #3, the base station can configure the UL DCI to indicate only the overall DAI for each of the two G-RNTIs notified to the terminal in the RRC message. Thus, the overall DAI for unselected G-RNTIs may not be included in the UL DCI. Furthermore, the UL DCI may be configured by the base station to indicate or not indicate the overall DAI for unicast.

[0359] Additionally or alternatively, if the terminal reports to the base station that it intends to receive G-RNTI#1, G-RNTI#2, and G-RNTI#3, the terminal can recognize that only the overall DAI for the two G-RNTIs having the higher or lower G-RNTI value is indicated in the UL DCI (even without being notified by the base station). Furthermore, the UL DCI may be configured by the base station to indicate or not indicate the overall DAI for unicast together.

[0360] Additionally or alternatively, when a terminal reports to the base station that it intends to receive G-RNTI #1, G-RNTI #2, and G-RNTI #3, the terminal can recognize (without being notified by the base station) that only the overall DAI for the G-RNTI with the highest priority (e.g., HP) is indicated in the UL DCI.

[0361] Additionally or alternatively, the UL DCI may be configured by the base station to indicate both or not the overall DAI for unicast, or depending on the priority for unicast and G-RNTI, the terminal may recognize that only the overall DAI for the unicast or G-RNTI with the higher priority (e.g., HP) is indicated in the UL DCI.

[0362] Option 3: The base station can indicate only the overall DAI value that has the highest value among the individual overall DAI values ​​and the unicast DAI value for each G-RNTI that the terminal intends to receive or has reported an interest in.

[0363] As an example, assume that the UE reports to the base station that it intends to receive G-RNTI #1 and G-RNTI #2. If the current overall DAI for G-RNTI #1 is 2, the current overall DAI for G-RNTI #2 is 3, and the current overall DAI for unicast is 1, the UL DCI may indicate 1, which has the highest overall DAI value. In this case, the UL DCI may further indicate an index for G-RNTI #2.

[0364] Additionally or alternatively, assume that the terminal reports to the base station that it intends to receive G-RNTI #1 and G-RNTI #2. If the current overall DAI for G-RNTI #1 is 2, the current overall DAI for G-RNTI #2 is 3, and the current overall DAI for unicast is 4, the UL DCI may indicate 4, which has the highest overall DAI value. In this case, the UL DCI may further indicate an index for unicast.

[0365] Option 4: All G-RNTIs that the terminal reports it intends to receive or is interested in may be grouped into multiple G-RNTI groups, and the base station may indicate to the terminal the overall DAI for each G-RNTI group.

[0366] Additionally or alternatively, the UL DCI may be configured by the base station to indicate or not indicate the overall DAI for unicast at all, or the overall DAI for unicast may be set to be included in a specific G-RNTI group.

[0367] As an example, if the terminal reports to the base station that it intends to receive G-RNTI #1, G-RNTI #2, and G-RNTI #3, the base station can group G-RNTI #1 and G-RNTI #2 together in a first group and specify G-RNTI #3 and unicast as a second group in an RRC message. The base station can then configure the UL DCI to indicate the overall DAI for each of the two groups.

[0368] In this case, the total DAI value of each group can indicate the sum of all the total DAI values ​​in the group as in option 1, or the total DAI value of each group can indicate the highest total DAI value in the group as in option 3.

[0369] Example 3: Type 2 codebook configuration method with HARQ-ACK deactivation

[0370] HARQ-ACK transmission for PDSCH reception of a specific G-RNTI may be activated or deactivated by a group common DCI indication or RRC configuration.

[0371] When HARQ-ACK transmission for a specific G-RNTI is deactivated by RRC configuration, the terminal can determine that the entire DAI for the specific G-RNTI is not included in the UL DCI.

[0372] Considering the case where a terminal is unable to receive a DCI when HARQ-ACK transmission for a specific G-RNTI is deactivated by the DCI, the terminal can determine that the UL DCI includes an overall DAI for the specific G-RNTI.

[0373] Additionally or alternatively, if HARQ-ACK transmission for a specific G-RNTI is deactivated by the DCI, the terminal may also determine that the UL DCI does not include the entire DAI for the specific G-RNTI.

[0374] In the above operation, the UL DCI may be replaced with one of a DL DCI that is CRC scrambled with the G-RNTI, or a DL DCI that schedules PTP transmission of a TB for the G-RNTI.

[0375] For group-common DCI indicating HARQ-ACK activation / deactivation, for type 2 codebook generation, the terminal can expect that HARQ-ACK feedback for all PDSCHs transmitted in the same PUCCH slot will be all activated or all deactivated.

[0376] If the HARQ-ACK feedbacks of all PDSCHs for the same PUCCH slot are not all identically disabled, the terminal may determine that all DAIs for all PDSCHs are mode activated and configure a type-2 codebook.

[0377] Therefore, regardless of whether HARQ-ACK is activated or deactivated, the terminal can analyze all DAIs for all PDSCHs as being activated and configure the HARQ-ACK information bit of the type 2 codebook.

[0378] Additionally or alternatively, the HARQ-ACK information bits of the Type 2 codebook may be configured only for those HARQ-ACKs that are actually activated.

[0379] FIG. 12 is a diagram for explaining a signaling procedure of a network side and a terminal according to an embodiment of the present disclosure.

[0380] FIG. 12 shows an example of signaling between the network side and the terminal (UE) in a situation where the above-mentioned examples of the present disclosure (e.g., Example 1, Example 2, Example 3, or a combination of one or more of their detailed examples) can be applied.

[0381] Here, the UE / network side is exemplary and may be replaced with various devices as described with reference to Fig. 13. Fig. 12 is for convenience of explanation and does not limit the scope of the present disclosure. Also, some steps shown in Fig. 12 may be omitted depending on the situation and / or settings. Also, in the operation of the network side / UE in Fig. 12, the above-mentioned uplink transmission / reception operation may be referred to or used.

[0382] In the following description, the network side may be one base station including multiple TRPs, or one cell including multiple TRPs. Or, the network side may include multiple RRHs (remote radio heads) / RRUs (remote radio units). As an example, an ideal / non-ideal backhaul may be set between TRP 1 and TRP 2 constituting the network side. In addition, although the following description is based on multiple TRPs, this may be equally extended and applied to transmissions by multiple panels / cells, and may also be extended and applied to transmissions by multiple RRHs / RRUs, etc.

[0383] In addition, the following description will be based on "TRP", but as described above, "TRP" may be applied instead of expressions such as panel, antenna array, cell (e.g., macro cell / small cell / pico cell, etc.), TP (transmission point), base station (gNB, etc.), etc. As described above, TRP may be classified according to information (e.g., CORESET index, ID) related to a CORESET group (or CORESET pool).

[0384] As an example, when one terminal is configured to transmit and receive from multiple TRPs (or cells), this may mean that multiple CORESET groups (or CORESET pools) are configured for one terminal. Such configuration of the CORESET group (or CORESET pool) may be performed by higher layer signaling (e.g., RRC signaling, etc.).

[0385] Also, the base station may be a collective term for 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 TPs (Transmission Points), one or more TRPs (Transmission and Reception Points), etc. Also, the TPs and / or TRPs may include a panel of the base station, a transmission and reception unit, etc.

[0386] The terminal may enter an RRC_CONNECTED mode and report a message indicating one or more interested MBS services to the network side (S105).

[0387] Here, the terminal may transmit the message to the network side using at least one of UCI, MAC CE (Control Element), and RRC message, and the MBS service of interest in the message may mean one of TMGI or G-RNTI listed in the DL message received from the network side.

[0388] For example, the DL message may be a service availability message listing TMGI #1, TMGI #3, TMGI #5, and TMGI #10. If the terminal is interested in TMGI #5, the terminal may indicate the order of TMGI #5 in the message. That is, the terminal may report "3" to the network side.

[0389] As yet another example, the DL message may be a service availability message listing G-RNTI #1, G-RNTI #3, G-RNTI #5, and G-RNTI #10. If the terminal is interested in G-RNTI #10, the terminal may indicate the order of G-RNTI #10 in the message. That is, the terminal may report "4" to the network side.

[0390] For example, the operation of the UE (100 or 200 in FIG. 13) transmitting the message to the network side (200 or 100 in FIG. 13) in step S105 described above may be embodied by the device in FIG. 13 described below. For example, referring to FIG. 13, one or more processors 102 can control one or more transceivers 106 and / or one or more memories 104, etc. to transmit the message, and one or more transceivers 106 can transmit the message to the network side.

[0391] Upon receiving the message, the network side can send configuration information to the terminal through an RRC message (S110).

[0392] For example, the configuration information may include CFR (common frequency resource) configuration information, one or more group common PDSCH configuration information including a TCI state for one or more G-RNTI values, and search space configuration information including a TCI state for one or more G-RNTI values.

[0393] Here, the RRC message may be a group common message transmitted on a PTM Multicast Control Channel (MCCH) or a UE-specific message transmitted on a UE-specific Dedicated Control Channel (DCCH).

[0394] And, the CFR may include DL CFR and UL CFR. For example, one DL CFR may provide group-common PDCCH and group-common PDSCH transmission resources for MBS transmission and reception. One UL CFR may provide HARQ-ACK PUCCH resources for group-common PDSCH reception. One CFR may be one MBS-specific BWP or one UE-specific BWP. Additionally or alternatively, one or more CFRs may be configured within one UE-specific BWP. One CFR may be connected to one UE-specific BWP.

[0395] The terminal may be configured with at least a G-RNTI value for each MBS CFR or each serving cell. The GC-CS-RNTI may be configured / used for activation, retransmission, or deactivation of one or more group-common SPS configurations.

[0396] For a terminal, if a GC-CS-RNTI is not configured for a CFR or serving cell and a CS-RNTI is configured for a CFR or serving cell, the terminal may use the CS-RNTI to activate, retransmit, or deactivate one or more group common SPS configurations.

[0397] The network side can associate a TMGI list or a G-RNTI list with one GC-CS-RNTI value, and can provide an MGI list or a G-RNTI list associated with the GC-CS-RNTI value.

[0398] Then, the configuration information of each PDSCH (for example, "PDSCH-config") may be configured as shown in Table 7 as a minimum information element for multicast and / or broadcast.

[0399] [Table 7]

[0400] For example, the operation of the UE (100 or 200 in FIG. 13) receiving the configuration information from the network side (200 or 100 in FIG. 13) in step S110 described above may be embodied by the apparatus of FIG. 13 described below. For example, referring to FIG. 13, one or more processors 102 may control one or more transceivers 106 and / or one or more memories 104, etc. to receive the configuration information, and one or more transceivers 106 may receive the configuration information from the network side. The terminal may receive control information from the network side (S115). For example, the terminal may receive downlink control information (DCI) for scheduling / activating / deactivating uplink / downlink from the network side.

[0401] Specifically, when a search space is configured for a configured CFR, the terminal monitors the PDCCH in the configured SS (search space) in the configured CFR, and can receive DCI CRC-scrambled in the G-RNTI or G(group)-CS(configured scheduling)-RNTI.

[0402] For example, the operation of the UE (100 or 200 in FIG. 13) receiving the control information from the network side (200 or 100 in FIG. 13) in step S115 described above may be embodied by the apparatus in FIG. 13 described below. For example, referring to FIG. 13, one or more processors 102 can control one or more transceivers 106 and / or one or more memories 104, etc. to receive the control information, and one or more transceivers 106 can receive the control information from the network side.

[0403] The terminal can receive the TB from the network side (S120).

[0404] Specifically, when a data unit is available on the MTCH of an MRB (MBS radio bearer) for an MBS service, the network side can configure a TB associated with the MTCH of the MRB for the MBS service, or associated with the TMGI of the MBS service, or including a data unit for the case of an SPS PDSCH associated with a short ID of the MBS service, or associated with a G-RNTI mapped to the MBS service by service-to-resource mapping, and transmit it to the terminal.

[0405] For group-common dynamic scheduling of TB, the network side can transmit DCI to the UE on the PDCCH. The DCI may be CRC-scrambled by the G-RNTI, G-CS-RNTI, or CS-RNTI. The PDCCH may be embodied as a group-common PDCCH or a UE-specific PDCCH.

[0406] For example, the DCI may include at least one of an identifier for a DCI format, a carrier indicator, a bandwidth part indicator, 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, an MCS, an NDI, an RV, an HARQ process number, a downlink allocation index, a TPC command for a scheduled PUCCH, a PUCCH resource indicator, a PDSCH-to-HARQ_feedback timing indicator, an antenna port, a transmission configuration indication, an SRS request, a DMRS sequence initialization, and a priority indicator.

[0407] In group-common dynamic scheduling, the network side may provide the terminal with one or more service-resource mappings for the MBS service identified by the TMGI or G-RNTI or GC-CS-RNTI by a group-common or terminal-specific RRC message or by a group-common or terminal-specific MAC CE. The data of the MBS service may be carried on a multicast traffic logical channel, i.e., an MBS Radio Bearer (MRB) of an MTCH associated with the MBS service. The RRC message may be a group-common message transmitted on a PTM Multicast Control Channel (MCCH) or a terminal-specific message transmitted on a terminal-specific Dedicated Control Channel (DCCH). The DCI scheduling PDSCH carrying the MBS service data may also indicate one or more of a short ID, an MTCH ID, an MRB ID, a G-RNTI value, and a TMGI value for the MBS service.

[0408] When the terminal receives a DCI CRC-scrambled by the G-RNTI that it intends to receive, the terminal can determine an MBS service associated with one or more of a short ID, an MTCH ID, an MRB ID, a G-RNTI value, and a TMGI value for each PDSCH opportunity based on a mapping between the MBS service indicated in the DCI and an HPN and / or a mapping between the MBS service indicated in the DCI and a short ID.

[0409] Thereafter, if the terminal is interested in the determined MBS service, the terminal may receive the PDSCH transmission scheduled by the DCI. If the terminal is not interested in the determined MBS service, the terminal may not receive the PDSCH transmission scheduled by the DCI.

[0410] For example, the operation of the UE (100 or 200 in FIG. 13) receiving the TB from the network side (200 or 100 in FIG. 13) in step S120 described above may be embodied by the apparatus in FIG. 13 described below. For example, referring to FIG. 13, one or more processors 102 can control one or more transceivers 106 and / or one or more memories 104, etc. to receive the TB, and one or more transceivers 106 can receive the TB from the network side.

[0411] When receiving the group common DCI indicating the PUCCH resource for the MBS HARQ-ACK, the terminal can transmit the HARQ-ACK on the PUCCH after receiving the PDSCH scheduled by the DCI (S125). That is, the terminal can transmit the HARQ feedback to the network side according to the decoding state of the PDSCH transmission.

[0412] In PTM scheme 1, the group-common DCI can indicate at least a single PUCCH resource indicator and a single PDSCH-to-HARQ_feedback timing indicator for ACK / NACK-based HARQ-ACK.

[0413] Specifically, in terminal-specific PUCCH resource allocation for ACK / NACK-based HARQ-ACK for group-common DCI, other terminals in the group may be set to at least other values ​​of "PUCCH-Resource" and "dl-DataToUL-ACK" in terminal-specific "PUCCH-config" for multicast or unicast (unless "PUCCH-config" for multicast is set). Different PUCCH resources may be allocated to different terminals with the same PUCCH resource indicator and the same PDSCH-to-HARQ_feedback timing indicator of group-common DCI.

[0414] In the case of PTP retransmission, the PUCCH resource indicator and the PDSCH-to-HARQ_feedback timing indicator in the terminal-specific DCI may be analyzed based on the "PUCCH-config" for unicast, regardless of whether the "PUCCH-config" for multicast is configured or not.

[0415] Here, the PRI (PUCCH Resource Indicator) may be indicated by a group-common DCI, as described later.

[0416] As an example, a terminal-specific PRI list may be included in the DCI (option 1A-1). Each PRI in the list may point to an entry corresponding to a candidate "pucch-ResourceId" value in "PUCCH-config" for allocation of the same PUCCH resource or different PUCCH resources to different terminals in a group that receive the same DCI. Other PRIs in the DCI may point to other entries in "PUCCH-config".

[0417] Here, the candidate "pucch-ResourceId" values ​​may be configured by RRC and other "pucch-ResourceId" values ​​may be configured for other terminals of the same group at least in the multicast "PUCCH-config".

[0418] As yet another example, a group-common PRI may be included in the DCI (option 1A-2). A single group-common PRI may indicate a specific entry for a candidate "pucch-ResourceId" value in the terminal-specific "PUCCH-config" for the same or different PUCCH resource allocation for all terminals of the group.

[0419] And the candidate "pucch-ResourceId" values ​​may be configured by RRC. At least in the "PUCCH-config" for multicast, different "pucch-ResourceId" values ​​may be configured for different terminals of the same group.

[0420] When a HARQ-ACK is configured to group common PDSCHs scheduled by a group common DCI in a "PUCCH-config" for multicast, the terminal can assume that the PRI of the group common DCI indicates an entry corresponding to a candidate "pucch-ResourceId" value of the "PUCCH-config" for multicast.

[0421] If a "PUCCH-config" for multicast is not configured for a HARQ-ACK for a group common PDSCH scheduled by a group common DCI, the terminal may assume that the PRI of the group common DCI indicates an entry corresponding to the candidate "pucch-ResourceId" value of the "PUCCH-config" for unicast.

[0422] K1 (PDSCH-to-HARQ_feedback timing indicator) may be indicated by a group-common DCI as described below.

[0423] As an example, a list of terminal specific K1 values ​​may be included in the DCI (option 1B-1), where each K1 in the list may indicate the same UL slot or different UL (sub)slots for different terminals of the group.

[0424] For example, different K1 values ​​may be assigned to different terminals, i.e., terminal 1 may be assigned a K1 value, terminal 2 may be assigned a K2 value, and terminal 3 may be assigned a K3 value.

[0425] As yet another example, a K1 value may be shared by multiple terminals. For example, terminal 1 and terminal 2 may share a K1 value, and terminal 3 and terminal 4 may share a K2 value.

[0426] As yet another example, one K1 value may be a reference and other K1 values ​​may be assigned based on the reference. The list of {K1_ref, K1_offset} may be indicated in the DCI.

[0427] For example, terminal 1 may use K1_ref, terminal 2 may use K1_ref+K1_offest1, and terminal 3 may use K1_ref+K1_offest2.

[0428] As yet another example, a group-wide K1 value may be included in the DCI (option 1B-2). For example, the single K1 value may be the same for all terminals in the group receiving the DCI, or may point to the corresponding entry for a candidate "dl-DataToUL-ACK" value in the terminal-specific "PUCCH-config" for other PUCCH resource allocations. This may apply if a DCI format is configured in the terminal-specific "PUCCH-config" for the K1 value.

[0429] As yet another example, the candidate 'dl-DataToUL-ACK' values ​​may be configured by RRC and set to be different for different terminals of the same group, at least in the 'PUCCH-config' for multicast.

[0430] As yet another example, when the "PUCCH-config" for multicast is configured for HARQ-ACK for grouping common PDSCHs scheduled by a group common DCI, the terminal may assume that the K1 value of the group common DCI indicates the corresponding entry for the candidate "dl-DataToUL-ACK" value in the "PUCCH-config" for multicast.

[0431] As yet another example, if the "PUCCH-config" for multicast is not configured for HARQ-ACK for grouping common PDSCHs scheduled by a group common DCI, the terminal may assume that the K1 value of the group common DCI indicates an entry in the "PUCCH-config" for unicast that corresponds to a candidate "dl-DataToUL-ACK" value.

[0432] In addition, when receiving a group-common DCI CRC-scrambled by a G-RNTI and / or a terminal-specific DCI CRC-scrambled by a C-RNTI, if a type-1 HARQ-ACK codebook is configured for the "PUCCH-config" for multicast and / or the "PUCCH-config" for unicast, the terminal can generate a type-1 HARQ-ACK codebook for the HARQ-ACK in order to configure a Time Domain Resource Allocation (TDRA) and group the common PDSCH scheduled by the group-common DCI and / or the terminal-specific PDSCH scheduled by the terminal-specific DCI.

[0433] If TB decoding is not successful in a PDSCH transmission opportunity, the terminal may transmit a HARQ NACK to the base station on a PUCCH resource in a configured UL CFR.

[0434] By using the PUCCH resource, the terminal may send HARQ-ACK for different PDSCH transmissions, such as a unicast SPS PDSCH, a dynamic unicast PDSCH, a PTP retransmission, and / or a dynamic group common PDSCH.

[0435] Here, in order to multiplex HARQ-ACK on PUCCH in (sub)slots for SPS PDSCH for multicast, SPS PDSCH for unicast, dynamically scheduled multicast PDSCH and / or dynamically scheduled unicast PDSCH, the terminal may configure a codebook based on one or more of the above-mentioned options.

[0436] When the RSRP threshold is configured, the terminal can use NACK-only based HARQ-ACK based NACK based on the measured serving cell's RSRP. When the measured RSRP is higher than the threshold, the NACK-only based HARQ-ACK may be transmitted on the group-common PUCCH resource indicated by the PRI of the DCI. When the measured RSRP is lower than the threshold, the NACK-only based HARQ-ACK may be changed to ACK / NACK based HARQ-ACK on the terminal-specific PUCCH resource indicated by the PRI of the DCI.

[0437] On the other hand, when "pdsch-AggregationFactor" is set for the G-RNTI or "repeat_number" is indicated by DCI from the network side, the TB scheduled by the group common DCI may be repeated for the Nth HARQ transmission of the TB within each symbol allocation, if set, during each "pdsch-AggregationFactor" consecutive slots or during each "repeat_number" consecutive slots.

[0438] For example, the operation of the UE (100 or 200 in FIG. 13) transmitting the HARQ-ACK from the network side (200 or 100 in FIG. 13) in step S125 described above may be implemented by the apparatus of FIG. 13 described below. For example, referring to FIG. 13, one or more processors 102 can control one or more transceivers 106 and / or one or more memories 104, etc. to transmit the HARQ-ACK, and one or more transceivers 106 can transmit the HARQ-ACK from the network side.

[0439] The network side that has received the HARQ NACK in the TCI state can retransmit the PDCCH and PDSCH using the TCI state at the DL CFR set for retransmission of the TB (S130).

[0440] The terminal can monitor the group-common and / or UE-specific PDCCH using the TCI state for the search space configured in the DL CFR to receive the retransmission of the TB. The network side can retransmit the TB to one of the terminals in the group via the terminal-specific PDCCH, but the other terminals do not need to receive the retransmission of the TB because they have successfully received the TB.

[0441] When the terminal receives a PDCCH for retransmission of the TB, the terminal may receive a PDSCH scheduled by the DCI of the PDCCH. If the terminal successfully decodes the TB from the PDSCH, the terminal may consider that the decoded TB is associated with an MTCH, an MRB, a TMGI, a G-RNTI, and / or a short ID of the MBS service based on the mapping between the MBS service and the HARQ process number (HPN) indicated by the DCI and / or the mapping between the MBS service and the short ID indicated by the DCI.

[0442] If TB decoding is successful during a PDSCH transmission opportunity, the terminal can transmit a HARQ ACK to the network side on a PUCCH resource in the configured UL CFR according to the above-mentioned procedure. Using the PUCCH resource, the terminal can transmit a HARQ-ACK for different PDSCH transmissions, such as a unicast SPS PDSCH, a dynamic unicast PDSCH, a PTP retransmission, and / or a dynamic group common PDSCH.

[0443] In this case, in order to multiplex HARQ-ACK on PUCCH in (sub)slots for SPS PDSCH for multicast, SPS PDSCH for unicast, dynamically scheduled multicast PDSCH and / or dynamically scheduled unicast PDSCH, the terminal may configure a codebook based on one or more of the above-mentioned options / embodiments.

[0444] For example, the operation of the UE (100 or 200 in FIG. 13) receiving a TB retransmission from a network side (200 or 100 in FIG. 13) in step S130 described above may be embodied by the apparatus of FIG. 13 described below. For example, referring to FIG. 13, one or more processors 102 may control one or more transceivers 106 and / or one or more memories 104, etc. to receive the TB retransmission, and one or more transceivers 106 may receive the TB retransmission from the network side.

[0445] Apparatus to which the present disclosure is applicable

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

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

[0448] The first 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 flow diagrams disclosed in the present disclosure.

[0449] For example, the processor 102 may process the information in the memory 104 to generate a 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 a second information / signal from the transceiver 106 and then store in the memory 104 information resulting from signal processing of the second information / signal.

[0450] 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 a part or all of the processes controlled by the processor 102 or for executing the descriptions, functions, procedures, suggestions, methods and / or operational flow diagrams disclosed in the present disclosure. Here, the processor 102 and the memory 104 may be part of a communication modem / circuit / chip designed to embody 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 be referred to as a Radio Frequency (RF) unit. In the present disclosure, the device may mean a communication modem / circuit / chip.

[0451] The second device 200 may include 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 flow diagrams disclosed in the present disclosure. For example, the processor 202 may process information in the memory 204 to generate a 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 a 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 executing the descriptions, functions, procedures, suggestions, methods and / or operational flow diagrams disclosed in the present disclosure. Here, the processor 202 and the memory 204 may be part of a communication modem / circuit / chip designed to embody 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 be referred to as an RF unit. In the present disclosure, the device may refer to a communication modem / circuit / chip.

[0452] The hardware elements of the devices 100, 200 are described in more detail below. One or more protocol layers may be embodied by one or more processors 102, 202, without being limited thereto. For example, one or more processors 102, 202 may embody one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors 102, 202 may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in the present disclosure. 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 the present disclosure. The one or more processors 102, 202 can generate and provide signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information to one or more transceivers 106, 206 according to the functions, procedures, suggestions, and / or methods disclosed in this disclosure. 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 flow diagrams disclosed in this disclosure.

[0453] The one or more processors 102, 202 may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. The one or more processors 102, 202 may be embodied in hardware, firmware, software, or a combination thereof. As an example, one or more application specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field programmable gate arrays (FPGAs) may be included in the one or more processors 102, 202. The descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in the present disclosure may be embodied using firmware or software, and the firmware or software may be embodied to include modules, procedures, functions, etc. Firmware or software configured to execute the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present 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 flowcharts disclosed in the present disclosure may be embodied in firmware or software in the form of code, instructions and / or collections of instructions.

[0454] One or more memories 104, 204 may be coupled to one or more processors 102, 202 and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories 104, 204 may be 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. Also, the one or more memories 104, 204 may be coupled to the one or more processors 102, 202 by various techniques, such as wired or wireless coupling.

[0455] The 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 flow diagrams of the present disclosure, to one or more other devices. The 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 flow diagrams of the present disclosure, from one or more other devices. For example, the 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, the one or more processors 102, 202 may control the one or more transceivers 106, 206 to transmit user data, control information, or wireless signals to one or more other devices. Also, the one or more processors 102, 202 may control the one or more transceivers 106, 206 to receive user data, control information, or wireless signals from one or more other devices. In addition, 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, radio signals / channels, etc., as described, functions, procedures, suggestions, methods, and / or operation flow diagrams disclosed in the present disclosure, via the one or more antennas 108, 208. In the present 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 radio signals / channels, etc., from RF band signals to baseband signals for processing the received user data, control information, radio signals / channels, etc., using one or more processors 102, 202. The one or more transceivers 106, 206 may convert the user data, control information, radio 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.

[0456] The above-described embodiments are combinations of the components and features of the present disclosure in a predetermined form. Each component or feature should be considered as optional unless otherwise expressly stated. Each component or feature may be implemented in a form not combined with other components or features. It is also possible to combine some components and / or features to configure the embodiments of the present disclosure. The order of operations described in the embodiments of the present disclosure may be changed. Some configurations or features of one embodiment may be included in another embodiment, or may be replaced with corresponding configurations 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 configure an embodiment, or may be included as a new claim by amendment after filing.

[0457] 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 a reasonable interpretation of the attached claims, and any modifications within the equivalent scope of the present disclosure are included in the scope of the present disclosure.

[0458] 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 the various embodiments, and non-transitory computer-readable media on which such software or instructions or the like can be stored and executed on a device or computer. Instructions available for programming a processing system to perform features described in the present disclosure may be stored on / 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 the present 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 thereto, 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. The memory optionally includes one or more storage devices that are located remotely from the processor. The memory or alternatively the non-volatile memory devices in the memory include non-transitory computer-readable storage media. 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.

[0459] Here, the wireless communication technology implemented in the 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. At this time, 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 names. Additionally or alternatively, the wireless communication technology implemented in the devices 100 and 200 of the present disclosure may perform communication based on the LTE-M technology. At this time, as an example, the LTE-M technology may be an example of an LPWAN technology, and may be called various names such as eMTC (enhanced Machine Type Communication). For example, the LTE-M technology may be embodied 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, the wireless communication technology embodied in the devices 100 and 200 of the present disclosure may include at least one of ZigBee (registered trademark), Bluetooth (registered trademark), and Low Power Wide Area Network (LPWAN), which consider low power communication, and is not limited to the above names. As an example, the ZigBee technology may generate personal area networks (PANs) related to small / low power digital communication based on various standards such as IEEE 802.15.4, and may be called various names. [Industrial Applicability]

[0460] 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 wireless communication systems other than 3GPP LTE / LTE-A and 5G systems.

Claims

1. A method of receiving, from a base station, a radio resource control (RRC) message associated with a semi-static hybrid automatic repeat request (HARQ)-acknowledgement (ACK) codebook for a physical downlink shared channel (PDSCH); receiving, from the base station, a first downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH), the first DCI including a downlink assignment index (DAI) field; generating the semi-static HARQ-ACK codebook including first HARQ-ACK information based on the RRC message, based on the DAI field included in the first DCI being set to 1; the UE transmitting the PUSCH including the semi-static HARQ-ACK codebook to the base station; The RRC message is for both multicast HARQ-ACK information and unicast HARQ-ACK information.

2. The first HARQ-ACK information is associated with a first PDSCH, The method of claim 1 , wherein the first PDSCH comprises a multicast PDSCH scheduled by a multicast DCI or a unicast PDSCH scheduled by a unicast DCI.

3. The method of claim 2, wherein the first HARQ-ACK information and second HARQ-ACK information for the second PDSCH are multiplexed within the PUSCH based on a second PDSCH transmitted to the UE.

4. The method of claim 3 , wherein the first HARQ-ACK information and the second HARQ-ACK information are concatenated in the HARQ-ACK codebook.

5. The method of claim 2, wherein the first HARQ-ACK information is generated by the UE based on the DAI field not indicating 1 and the first PDSCH satisfying a specific condition.

6. The method of claim 5 , wherein the first PDSCH is a semi-persistent scheduling (SPS) PDSCH or a PDSCH scheduled by a DCI.

7. the first HARQ-ACK information is unicast HARQ-ACK information; The method of claim 3 , wherein the second HARQ-ACK information is multicast HARQ-ACK information.

8. at least one transceiver; at least one processor coupled to the at least one transceiver; The at least one processor receiving, from a base station via the at least one transceiver, a radio resource control (RRC) message associated with a semi-static hybrid automatic repeat request (HARQ)-acknowledgement (ACK) codebook for a physical downlink shared channel (PDSCH); receiving, from the base station via the at least one transceiver, first downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH), the first DCI including a downlink assignment index (DAI) field; generating the semi-static HARQ-ACK codebook including first HARQ-ACK information based on the RRC message based on the DAI field included in the first DCI being set to 1; transmitting the PUSCH including the semi-static HARQ-ACK codebook to the base station via the at least one transceiver; The RRC messages are for both multicast and unicast HARQ-ACK information, UE (user equipment).

9. at least one transceiver; at least one processor coupled to the at least one transceiver; The at least one processor transmitting a radio resource control (RRC) message associated with a semi-static hybrid automatic repeat request (HARQ)-acknowledgement (ACK) codebook for a physical downlink shared channel (PDSCH) to a user equipment (UE) via the at least one transceiver; transmit, via the at least one transceiver, to the UE, a first downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH), the first DCI including a downlink assignment index (DAI) field; The semi-static HARQ-ACK codebook including first HARQ-ACK information is received from the UE via the PUSCH based on the RRC message based on the DAI field included in the first DCI being set to 1; The RRC message is for both multicast HARQ-ACK information and unicast HARQ-ACK information.

Images