Method and apparatus for transmitting or receiving hybrid automatic repeat request-acknowledgement information in a wireless communication system - Patents.com

Abstract

A method and an apparatus for transmitting or receiving Hybrid Automatic Repeat Request (HARQ)-Acknowledgement (ACK) information in a wireless communication system are disclosed. According to an embodiment of the present disclosure, in the wireless communication system, whether to multiplex a HARQ-ACK codebook for a cast type and a HARQ-ACK codebook type may be instructed based on a downlink assignment index (DAI) included in downlink control information (DCI) including scheduling information of a physical uplink shared channel (PUSCH).

Description

[Technical field]

[0001] The present disclosure relates to wireless communication systems, and more particularly, to a method and apparatus for transmitting or receiving Hybrid Automatic Repeat Request (HARQ)-Acknowledgement (ACK) information in a wireless communication system. [Background technology]

[0002] Mobile communication systems have been 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 explosive traffic growth, 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] The technical problem of the present disclosure is to provide a method and apparatus for transmitting or receiving HARQ-ACK information in a wireless communication system, which supports HARQ-ACK codebook multiplexing based on cast type and HARQ-ACK codebook type.

[0005] A further technical object of the present disclosure is to provide a method and device for transmitting or receiving HARQ-ACK information, in which whether or not to multiplex a HARQ-ACK codebook for a cast type and a HARQ-ACK codebook type is instructed based on a downlink allocation index (DAI) included in downlink control information (DCI) including scheduling information of a physical uplink shared channel (PUSCH) in a wireless communication system.

[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] According to an embodiment of the present disclosure, a method performed by a terminal in a wireless communication system may include receiving, from a network, downlink control information (DCI) including one or more bits of downlink allocation index (DAI) information and scheduling a physical uplink shared channel (PUSCH) transmission, generating a hybrid automatic repeat request (HARQ)-acknowledgement (ACK) codebook based on the DAI information, and multiplexing and transmitting HARQ-ACK information on the PUSCH based on the HARQ-ACK codebook to the network. For example, based on a semi-static HARQ-ACK codebook being set for both unicast and multicast, the DAI information may include one bit associated with a HARQ-ACK codebook for both unicast and multicast, or the DAI information may include a first bit associated with unicast HARQ-ACK information and a second bit associated with multicast HARQ-ACK information.

[0008] According to a further aspect of the present disclosure, a method performed by a base station in a wireless communication system may include transmitting, to a terminal, downlink control information (DCI) including one or more bits of downlink allocation index (DAI) information and scheduling a physical uplink shared channel (PUSCH) transmission, and receiving, from the terminal, HARQ-ACK information multiplexed in the PUSCH based on a hybrid automatic repeat request (HARQ)-acknowledgement (ACK) codebook generated by the terminal based on the DAI information. For example, based on a semi-static HARQ-ACK codebook being set for both unicast and multicast, the DAI information may include one bit associated with a HARQ-ACK codebook for both unicast and multicast, or the DAI information may include a first bit associated with unicast HARQ-ACK information and a second bit associated with multicast HARQ-ACK information. Effect of the Invention

[0009] According to the present disclosure, a method and apparatus for transmitting or receiving HARQ-ACK information in a wireless communication system can be provided, which supports HARQ-ACK codebook multiplexing based on a cast type and a HARQ-ACK codebook type.

[0010] According to the present disclosure, it is possible to provide a method and device for transmitting or receiving HARQ-ACK information in which whether or not to multiplex a HARQ-ACK codebook for a cast type and a HARQ-ACK codebook type is instructed based on a downlink allocation index (DAI) included in downlink control information (DCI) including scheduling information for a physical uplink shared channel (PUSCH) in a wireless communication system.

[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] 1 illustrates the structure of a wireless communication system to which the present disclosure can be applied.

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

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

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

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

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

[0019] [Figure 7] 1 is a diagram illustrating an example of the transmission timing of unicast HARQ-ACK information and multicast HARQ-ACK information to which the present disclosure can be applied.

[0020] [Figure 8] FIG. 13 is a diagram for explaining a HARQ-ACK transmission method of a terminal according to one embodiment of the present disclosure.

[0021] [Figure 9] A diagram for explaining a HARQ-ACK receiving method of a base station according to one embodiment of the present disclosure.

[0022] [Figure 10] A diagram for explaining a signaling procedure between the network side and the terminal according to one embodiment of the present disclosure.

[0023] [Figure 11] 1 is a block diagram illustrating a wireless communication device according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

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

[0026] In the present 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 the present disclosure, the terms "including" or "having" specify the presence of stated features, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, elements, components, and / or groups thereof.

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

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

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

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

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

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

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

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

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

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

[0037] - BM: Beam management

[0038] - CQI: channel quality indicator

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

[0040] - CSI: channel state information

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

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

[0043] - DMRS: Demodulation Reference Signal

[0044] - FDM: Frequency division multiplexing

[0045] - FFT: Fast Fourier transform

[0046] - IFDMA: Interleaved frequency division multiple access

[0047] - IFFT: inverse fast Fourier transform

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

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

[0050] - MAC: medium access control

[0051] - NZP: non-zero power

[0052] - OFDM: Orthogonal frequency division multiplexing

[0053] - PDCCH: physical downlink control channel

[0054] - PDSCH: physical downlink shared channel

[0055] - PMI: Precoding matrix indicator

[0056] - RE: resource element

[0057] - RI: Rank indicator

[0058] - RRC: Radio resource control

[0059] - RSSI: received signal strength indicator

[0060] - Rx: Reception

[0061] - QCL: quasi co-location

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

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

[0064] - TDM: time division multiplexing

[0065] - TRP: transmission and reception point

[0066] - TRS: Tracking reference signal

[0067] - Tx: transmission

[0068] - UE: User Equipment

[0069] - ZP: Zero power

[0070] System in general

[0071] As more communication devices require larger communication capacity, the need for improved mobile broadband communication compared to existing radio access technologies (RATs) is emerging. Massive Machine Type Communications (MTC), which connects a large number of devices and objects to provide various services anytime and anywhere, is also one of the major issues to be 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.

[0072] 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. Alternatively, the new RAT system may follow the existing LTE / LTE-A numerology but support a larger system bandwidth (e.g., 100 MHz). Alternatively, one cell may support multiple numerologies. That is, terminals operating with different numerologies may coexist in one cell.

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

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

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

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

[0077] 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 utilized at very high carrier frequencies. In addition, various frame structures with multiple numerologies may be supported in the NR system.

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

[0079] [Table 1]

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

[0081] 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. FR2 may also refer to millimeter wave (mmW).

[0082] [Table 2]

[0083] 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 Nf = 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,μ The slots are numbered in increasing order {N -1}. symb slot It consists of N consecutive OFDM symbols. symb slot is determined by the CP. s μ The start of OFDM symbol n s μ N symb slotNot all terminals can transmit and receive at the same time, which means that not all OFDM symbols in a downlink slot or uplink slot can be used.

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

[0085] [Table 3]

[0086] [Table 4]

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

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

[0089] First, with respect 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 properties 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 quasi co-located (QC / QCL) relationship. Here, the large-scale properties include at least one of delay spread, Doppler spread, frequency shift, average received power, and received timing.

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

[0091] 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 between uplink and downlink as well as numerology. In this case, one resource grid may be set for each μ and antenna port p. Each element of the resource grid for μ and antenna port p is called a resource element, and is represented by an index pair. JPEG2025506104000006.jpg9142, where k=0,...,N RB μ N sc RB -1 is the index in the frequency domain, JPEG2025506104000007.jpg11128 represents the position of the symbol within a subframe. When referring to resource elements in a slot, the index pair (k,l) is used, where l=0,...,N symb μ μ and the resource element for antenna port p. JPEG2025506104000008.jpg8129 is a complex value JPEG2025506104000009.jpg10130. 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 JPEG2025506104000010.jpg12123. Also, a resource block (RB) is N scRB = 12 consecutive subcarriers.

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

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

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

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

[0096]

number

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

[0098]

number

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

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

[0101] 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, whereas in the extended CP, one slot includes six symbols.

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

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

[0104] 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 set at a specific time (by L1 signaling, MAC CE (Control Element), RRC signaling, etc.). Also, the base station may instruct switching to another configured DL / UL BWP (by L1 signaling, MAC CE, RRC signaling, etc.). Or, the base station may switch to a predetermined DL / UL BWP when a timer value expires on a timer basis. In this case, the activated DL / UL BWP is defined as an active DL / UL BWP. However, in 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. In such a situation, the DL / UL BWP assumed by the UE is defined as an initially active DL / UL BWP.

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

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

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

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

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

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

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

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

[0113] [Table 5]

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

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

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

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

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

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

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

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

[0122] MBMS(Multimedia Broadcast Multicast Service)

[0123] MBMS may include a single frequency network (SFN) scheme in which multiple base stations or multiple cells are synchronized to transmit the same data to a terminal, and a single cell point to multipoint (SC-PTM) scheme in which data is broadcast within the cell coverage via a PDCCH / PDSCH channel.

[0124] The SFN scheme may be used to provide broadcast services to a wide area (e.g., an MBMS area) using resources that are semi-statically allocated in advance. The MBSFN (Multicast Broadcast Single Frequency Network) provides the logical channels MCCH (Multicast Control Channel) and MTCH (Multicast Traffic Channel), and both the MCCH and MTCH are mapped to the MCH (Multicast Channel), which is a transport channel, and the MCH is mapped to the PMCH (Physical Multicast Channel), which is a physical channel. That is, multiple base stations / cells can synchronize and provide the same data to a terminal via the PMCH. One base station / cell may belong to multiple MBSFN areas. Also, it may be necessary to configure an MBSFN subframe for the MBSFN service.

[0125] The SC-PTM scheme may be mainly used to provide broadcast services only within a cell coverage using dynamic resources. The SC-PTM provides one logical channel SC-MCCH (Single Cell Multicast Control Channel) and one or more logical channels SC-MTCH (Single Cell Multicast Traffic Channel). These logical channels (i.e., SC-MCCH and SC-MTCH) are mapped to a transmission channel DL-SCH, which is mapped to a physical channel PDSCH. The PDSCH transmitting data corresponding to the SC-MCCH or SC-MTCH is scheduled via a PDCCH that is CRC scrambled with a Group-Radio Network Temporary Identifier (G-RNTI). Here, a Temporary Mobile Group Identity (TMGI) corresponding to an MBMS service ID may be one-to-one mapped to a specific G-RNTI value. Therefore, when a base station provides multiple MBMS services, multiple G-RNTI values ​​may be assigned for SC-PTM transmission. One or more terminals can perform PDCCH monitoring using a specific G-RNTI to receive a specific MBMS service. Here, a discontinuous reception (DRX) on-duration period dedicated to the SC-PTM may be configured for a specific MBMS service / specific G-RNTI. In this case, the terminal can wake up only during a specific on-duration period and perform PDCCH monitoring for the G-RNTI.

[0126] SPS(semi-persistent scheduling)

[0127] The base station may provide a terminal-dedicated SPS configuration to a specific terminal and may allocate one or more downlink SPS transmission resources that are repeated according to a set period. The DCI of the terminal-dedicated (or terminal-specific) PDCCH may indicate SPS activation of a specific SPS configuration index. The terminal may perform downlink reception using the activated SPS transmission resource. Such an SPS transmission resource may be used for initial HARQ transmission. The base station may also allocate a retransmission resource of a specific SPS configuration index using the DCI of the terminal-dedicated PDCCH. For example, if the terminal reports a HARQ NACK for the SPS transmission resource, the base station may allocate a retransmission resource to the DCI so that the terminal can receive downlink retransmission.

[0128] The DCI of the UE-dedicated PDCCH may indicate the release or deactivation of a specific SPS configuration index, in which case the UE does not receive the SPS transmission resource for which the release / deactivation is indicated.

[0129] The CRC of the DCI / PDCCH for activation / retransmission / deactivation for SPS configuration / resources may be scrambled by a configured scheduling-radio network temporary identifier (CS-RNTI).

[0130] MBS(Multicast Broadcast Service)

[0131] In the NR-based wireless communication system, the introduction of a new MBS-based DL broadcast or DL ​​multicast transmission method that is distinct from the above-mentioned MBMS (e.g., MBSFN or SC-PTM) is being discussed. For example, the network side (e.g., base station / cell / TRP) can provide a point-to-multipoint (PTM) transmission method and a point-to-point (PTP) transmission method for transmitting DL broadcast or DL ​​multicast.

[0132] In the PTM transmission scheme for MBS, a base station can transmit a group common (or group specific) PDCCH (Group Common PDCCH) and a group common PDSCH (Group Common PDSCH) to multiple terminals. Multiple terminals can simultaneously receive the same group common PDCCH and group common PDSCH transmission and decode the same MBS data.

[0133] In the PTP transmission method for MBS, a base station can transmit a terminal-dedicated (or terminal-specific) PDCCH and a terminal-dedicated PDSCH to a specific terminal. A corresponding terminal can receive a terminal-dedicated PDCCH and a terminal-dedicated PDSCH. When there are multiple terminals receiving the same MBS service, the base station can transmit the same MBS data separately to each of the multiple terminals via different terminal-dedicated PDCCHs and terminal-dedicated PDSCHs.

[0134] In the PTM transmission scheme, a base station can transmit a plurality of group-common PDSCHs to a terminal, and can receive HARQ-ACKs from the terminals for the group-common PDSCHs by using PUCCH resources dedicated to the terminals.

[0135] When a terminal successfully decodes a TB (Transport Block) for a group-common PDSCH, the terminal can transmit an ACK value as HARQ-ACK information. When a terminal cannot successfully decode a TB for a unicast PDSCH or a group-common PDSCH, the terminal can transmit a NACK value as HARQ-ACK information. Such a HARQ-ACK transmission method can be referred to as an ACK / NACK-based HARQ-ACK method. The ACK / NACK-based HARQ-ACK information may generally be transmitted on a terminal-dedicated PUCCH resource.

[0136] A NACK-only based HARQ-ACK scheme may be applied / configured for a group-common PDSCH. For example, a terminal may not transmit a PUCCH if the ACK value is present (i.e., decoding of the received PDSCH is successful), and may transmit a PUCCH only if the NACK value is present (i.e., decoding of the received PDSCH is unsuccessful). NACK-only based HARQ-ACK information may generally be transmitted in a group-common PUCCH resource. In the case where multiple HARQ-ACKs are transmitted in the NACK-only based HARQ-ACK scheme, if only an ACK value is included, HARQ-ACK information may not be transmitted, and if at least one NACK value is included, HARQ-ACK information may be transmitted.

[0137] In the following examples, the ACK / NACK-based HARQ-ACK can be referred to as HARQ-ACK information based on the first HARQ-ACK reporting mode, and the NACK-only-based HARQ-ACK can be referred to as HARQ-ACK information based on the second HARQ-ACK reporting mode. In addition, the DCI format CRC-scrambled by the G-RNTI or G-CS-RNTI can be referred to as a group-common DCI format or a multicast DCI format. The group-common / multicast DCI format can also be referred to as a group-common / multicast PDCCH, and the PDSCH scheduled thereby can be referred to as a group-common / multicast PDSCH.

[0138] For example, a terminal can receive unicast traffic via a terminal-specific unicast PDSCH and receive multicast traffic such as MBS via a group-common multicast PDSCH. A terminal can transmit a unicast HARQ-ACK for a unicast PDSCH and a multicast HARQ-ACK for a multicast PDSCH. If a PUCCH transmission for a unicast HARQ-ACK and a PUCCH transmission for a multicast HARQ-ACK overlap or should be transmitted in the same slot, it is unclear how a terminal that cannot transmit two PUCCHs simultaneously transmits a unicast HARQ-ACK and a multicast HARQ-ACK. In particular, when a multicast HARQ-ACK is set to a NACK-only based HARQ-ACK, it is unclear how multiple HARQ-ACKs are transmitted in a situation where a NACK-only based HARQ-ACK and an ACK / NACK based HARQ-ACK transmission overlap or should be transmitted in the same slot.

[0139] In the present disclosure, the ACK / NACK-based HARQ-ACK transmission method is not limited to HARQ-ACK for unicast PDCCH / PDSCH, and as described above, the ACK / NACK-based HARQ-ACK transmission method may also be applied to HARQ-ACK for multicast PDCCH / PDSCH.

[0140] In this disclosure, various examples are described for transmitting or receiving HARQ-ACKs by applying one or more of multiplexing, dropping, partial selection, or separation when unicast HARQ-ACK information, multicast HARQ-ACK information (e.g., one or more of ACK / NACK-based HARQ-ACK information, or NACK-only-based HARQ-ACK information) collide in the same time unit.

[0141] For example, when NACK-only based HARQ-ACK and ACK / NACK based HARQ-ACK transmissions overlap or are to be transmitted in the same slot, multiple HARQ-ACKs may be multiplexed into one PUCCH or may be transmitted separately across multiple PUCCHs.

[0142] For example, the terminal may be configured to transmit a HARQ-ACK according to any one of the schemes described below, or to transmit a HARQ-ACK according to a combination of two or more of the schemes described below.

[0143] For example, a scheme may be applied / configured in which, for all overlapping unicast HARQ-ACKs and multicast HARQ-ACKs, LP (low priority) HARQ-ACKs are dropped and HP (high priority) HARQ-ACKs are transmitted.

[0144] For example, for overlapping unicast HARQ-ACK and multicast HARQ-ACK transmissions, the following options may be considered:

[0145] Option 1: The terminal may give priority to transmitting unicast HARQ-ACKs and drop multicast HARQ-ACKs.

[0146] Option 2: The base station can determine which unicast and multicast HARQ-ACKs to transmit with priority and which to drop, and set / instruct the terminal.

[0147] Option 3: Compare the priority indicated by the last received DCI for a unicast HARQ-ACK with the priority indicated by the last received DCI for a multicast HARQ-ACK, send a unicast HARQ-ACK or multicast HARQ-ACK with the higher priority, and drop the remaining HARQ-ACKs.

[0148] Option 4: Among unicast HARQ-ACKs and multicast HARQ-ACKs, those with small HARQ-ACK payloads can be dropped, and those with large HARQ-ACK payloads can be transmitted.

[0149] In addition, when ACK (only) is indicated for the NACK-only based HARQ-ACK (i.e., when actual PUCCH transmission is not required), the terminal may determine that there is no possibility of collision with other HARQ-ACKs, SR / CSI reports, etc. Or, even when ACK (only) is indicated for the NACK-only based HARQ-ACK (i.e., when actual PUCCH transmission is not required), it may be assumed that the HARQ-ACK is virtually transmitted and may determine that there is a possibility of collision with other HARQ-ACKs, SR / CSI reports, etc. The base station may configure the terminal as to whether the NACK-only based HARQ-ACK is to be considered as being actually transmitted or to be virtually transmitted regardless of whether the NACK-only based HARQ-ACK is actually transmitted, when the terminal determines whether there is a collision with other UCI.

[0150] In the present disclosure, when certain information is defined between a terminal and a base station, it means that the terminal and the base station know the information without any separate signaling between the terminal and the base station; when information is configured between a terminal and a base station, it means that the information is transmitted / received by higher layer (e.g., RRC) signaling between the terminal and the base station; when information is indicated between a terminal and a base station, it can mean that the information is transmitted / received by lower layer (e.g., L1 (e.g., DCI / UCI), L2 (e.g., MAC-CE)) signaling.

[0151] Improved HARQ-ACK codebook

[0152] In the following, an example of the present disclosure for a HARQ-ACK codebook considering various cast types (eg, unicast, multicast, broadcast, etc.) is described.

[0153] The HARQ-ACK codebook may correspond to a set (or sequence) of bits indicating HARQ-ACK information (e.g., ACK / NACK information) for one or more PDSCHs received in a certain time window. The size of the HARQ-ACK codebook may be set according to a semi-static type (or type-1), a dynamic type (or type-2), or a one-shot type (or type-3). The HARQ-ACK codebook may be configured to be transmitted on the PUCCH or to be transmitted on the PUSCH.

[0154] Multicast SPS may be activated or deactivated based on DCI. For broadcast SPS, a DCI-based activation / deactivation method may be applied, but an activation / deactivation method using an RRC message may also be applied. In this case, since multiple terminals activate or deactivate the same broadcast SPS transmission, there is a problem that it is not clear to the terminal when it should be activated / deactivated.

[0155] Also, it may be assumed that a type-3 HARQ-ACK codebook is configured for a unicast PDSCH, and a type-1 or type-2 HARQ-ACK codebook is configured for a multicast PDSCH. In this case, it is unclear how to configure a type-3 codebook for a HARQ process number (HPN) value shared by a unicast PDSCH and a multicast PDSCH. In particular, when sharing an HARQ process, it is unclear whether or not NDI is toggled, and therefore, it is unclear how to configure the NDI of the type-3 codebook.

[0156] In the present disclosure, an example is described in which a type-3 codebook is configured for a HARQ process shared by a unicast PDSCH and a multicast PDSCH when a type-3 codebook is configured for a terminal-dedicated PDSCH and another type of codebook is configured for a multicast PDSCH.

[0157] FIG. 7 is a diagram illustrating an example of transmission timing of unicast HARQ-ACK information and multicast HARQ-ACK information to which the present disclosure can be applied.

[0158] In the example of Fig. 7, DCI (or PDCCH), PDSCH scheduled by it, and HARQ-ACK for it are displayed on the same line. That is, in Fig. 7, three sets of associated / corresponding DCI (PDCCH), PDSCH, and HARQ-ACK are shown. In the example of Fig. 7, three HARQ-ACKs for three DCI / PDSCH are shown, but the scope of the present disclosure may also be applied to multiple HARQ-ACKs for multiple DCI / PDSCH. The horizontal axis is associated with time, but is not intended to indicate absolute or relative time positions, and illustrates a situation in which HARQ-ACKs corresponding to different DCI / PDSCHs overlap (or are transmitted in the same slot).

[0159] In the example of FIG. 7, a terminal can receive multiple multicast PDCCHs / PDSCHs scheduled with different G-RNTIs in an FDM or TDM manner.

[0160] In the example of Figure 7, the DCI CRC-scrambled in the C-RNTI may correspond to a unicast DCI, and the DCI CRC-scrambled in the G-RNTI may correspond to a multicast DCI. In addition, the unicast DCI / multicast DCI may indicate high priority (HP) or low priority (LP).

[0161] In the example of Figure 7, the terminal can receive both unicast PDSCH and multicast PDSCH transmitted by FDM or TDM. For example, a unicast PDSCH opportunity may be transmitted by TDM with a multicast PDSCH opportunity for G-RNTI #1, and may be transmitted by FDM with a multicast PDSCH opportunity for G-RNTI #2.

[0162] The base station may configure the PDSCH-config for CFR separately from a set of PDSCH configuration parameters for BWP (e.g., PDSCH-config). In this case, the CFR may be associated with an active BWP of the terminal. Thus, some parameters may be configured in common for the CFR and BWP. Thus, the base station may configure some parameters only in one PDSCH-config without repeating them in the PDSCH-config for CFR and the PDSCH-config for BWP.

[0163] That is, when the setting value for parameter A is the same in the PDSCH-config for CFR and the PDSCH-config for BWP, the base station may include parameter A only in the PDSCH-config for BWP and not in the PDSCH-config for CFR.

[0164] In the example of Figure 7, in individual PDSCHs that may be transmitted in the same cell, if the HARQ-ACK for the unicast PDSCH is configured as a type-3 codebook and the multicast PDSCH is configured as a type-1 codebook or a type-2 codebook, the terminal can configure the type-3 codebook for the HPN value shared by the unicast PDSCH and the multicast PDSCH as follows.

[0165] Example 1

[0166] This embodiment relates to a method for configuring an NDI value of a Type-3 codebook based on whether PTM transmission and unicast transmission share a HARQ process.

[0167] Depending on whether a specific HARQ process mapped to a specific HPN value may be used in a shared manner for multicast transmission and unicast transmission, or whether a specific HARQ process mapped to a specific HPN value is used exclusively for multicast transmission or exclusively for unicast transmission, the terminal may configure a Type-3 codebook for unicast HARQ-ACK transmission for a specific HARQ process as follows:

[0168] If a specific HARQ process mapped to a specific HPN value can be shared by multicast transmission and unicast transmission, the base station can transmit a multicast PDSCH and a unicast PDSCH consecutively for the HARQ process for the same HPN value, or transmit a unicast PDSCH and a multicast PDSCH consecutively. In this case, the NDI value of the DCI for the multicast PDSCH and the NDI value of the DCI for the unicast PDSCH that are transmitted consecutively may be toggled.

[0169] If the NDI is toggled for the same HPN value regardless of the cast type, the terminal that last received a unicast or multicast transmission can construct a Type-3 codebook as follows and transmit it to the network:

[0170] Option 1: (regardless of whether the last reception is unicast or multicast) the terminal may include, for a specific HARQ process, the NDI value indicated by the last received unicast DCI and the HARQ-ACK result of the unicast PDSCH scheduled by the DCI in the type-3 codebook, i.e., the terminal may make the actual reception result of the unicast PDSCH be included in the type-3 codebook for the HARQ process.

[0171] Option 2: (regardless of whether the last reception is unicast or multicast) the terminal may include the NDI value indicated by the last received multicast DCI and the HARQ-ACK result of the multicast PDSCH scheduled by the DCI as NACK in the type-3 codebook for a specific HARQ process, i.e., the terminal may make the type-3 codebook indicate NACK for the HARQ process regardless of whether the actual decoding of the multicast PDSCH is successful or not.

[0172] Option 3: The terminal can configure the Type-3 codebook in one of the following ways: A, B, C, D, or E.

[0173] Scheme A: In the Type-3 codebook, the HARQ-ACK bit for the specific HARQ process may indicate ACK or NACK according to the HARQ-ACK value for the last received unicast PDSCH or the HARQ-ACK value reported immediately before.

[0174] Scheme B: In the Type-3 codebook, the HARQ-ACK bit for the specific HARQ process indicates ACK or NACK according to the HARQ-ACK value for the last received PDSCH or the HARQ-ACK value reported immediately before, where the last received PDSCH can be a unicast PDSCH or a multicast PDSCH.

[0175] Scheme C: When a multicast PDSCH is finally received by the specific HARQ process, the HARQ-ACK bit for the specific HARQ process in the Type-3 codebook may be set to always NACK or always ACK, where whether always NACK or always ACK may be set by signaling between the base station and the terminal, or may be predefined without signaling between the base station and the terminal.

[0176] Scheme D: When a multicast PDSCH is received last through the specific HARQ process, in the type-3 codebook, the HARQ-ACK bit for the specific HARQ process may not be included in the type-3 codebook.

[0177] Scheme E: When the specific HARQ process is set to be shared by multicast and unicast, or is mapped to an HPN specified by the base station, the HARQ-ACK bit for the specific HARQ process in the Type-3 codebook may be set to always NACK or always ACK, where whether always NACK or always ACK may be set by signaling between the base station and the terminal, or may be predefined without signaling between the base station and the terminal.

[0178] If the NDI is toggled only for the same HPN value of the same cast type and not for the same HPN value of different cast types (regardless of whether the last reception is unicast or multicast), the terminal may include the NDI value indicated by the last received unicast DCI and the HARQ-ACK result of the unicast PDSCH scheduled by the DCI in the type-3 codebook for a specific HARQ process, i.e., the terminal may cause the actual reception result of the unicast PDSCH for the HARQ process to be included in the type-3 codebook.

[0179] If a specific HARQ process mapped to a specific HPN value is used only for multicast transmission or only for unicast transmission, the terminal may include HARQ-ACK information and NDI information for the unicast-only HARQ process in the type-3 codebook, and may not include information on the multicast-only HARQ process in the type-3 codebook. Alternatively, if the base station specifies a specific HARQ process as a type-3 codebook setting for unicast, the terminal may include HARQ-ACK information and NDI information for the specified HARQ process in the type-3 codebook, and may not include information on unspecified HARQ processes in the type-3 codebook.

[0180] Example 2

[0181] This embodiment relates to a scheme for newly defining a downlink assignment index (DAI) of a DCI for constructing a multicast HARQ-ACK codebook.

[0182] The terminal can configure a type-1 codebook and / or a type-2 codebook in the following manner according to the setting from the base station and the DAI value of the DCI.

[0183] A base station may use DCI to allocate UL PUSCH resources or schedule DL PDSCH transmission. In this case, DCI transmitted by a base station to allocate UL PUSCH resources may be abbreviated as UL DCI, and DCI transmitted by a base station to schedule DL PDSCH transmission may be abbreviated as DL DCI.

[0184] The terminal can receive a PUCCH resource indicator (PRI) by a group common DCI or a terminal specific (or UE-specific) DCI. The terminal can transmit HARQ-ACK information for a PDSCH scheduled by the group common DCI or the terminal specific DCI on a PUCCH resource indicated by the PRI. If the PUCCH transmission overlaps with a PUSCH transmission, the terminal can transmit a PUSCH instead of a PUCCH. That is, the UCI including the HARQ-ACK information can be transmitted to the network in a piggyback manner on the PUSCH.

[0185] 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 may indicate the total number of PDSCHs currently scheduled for a specific G-RNTI.

[0186] A TB transmitted via a PDSCH scheduled by a group-common DCI may be retransmitted in the PTP manner. In this case, the terminal may obtain PDSCH transmission information for the retransmission of the TB by using a terminal-specific DL DCI in which a CRC is scrambled by a C-RNTI. Here, the DL DCI may include a counter DAI and a total DAI for a G-RNTI corresponding to the TB. For example, if one and the same TB is scheduled twice by two group-common DCIs and scheduled a third time by a PTP retransmission, the [counter DAI, total DAI] pair may have values ​​of [0,0] and [1,1] in the first two group-common DCIs, respectively. In the terminal-specific DCI for the next PTP retransmission, the [counter DAI, total DAI] pair may have a value of [2,2] based on (or subsequent to) the DAI value of the group-common DCI. Or, the DAI of the DCI for the PTP retransmission may have a value different from (or not based on, or not subsequent to) the DAI value of the group-common DCI. For example, the [counterDAI, totalDAI] pair of a DCI for a PTP retransmission may have a value that is based on (or follows) the [counterDAI, totalDAI] value of a previously transmitted unicast DCI (of another TB).

[0187] Meanwhile, the base station may include a total DAI for G-RNTI transmission in the UL DCI in which the CRC is scrambled by the C-RNTI. For example, when a UL DCI is transmitted after transmitting two group common DCIs, the total DAI of the UL DCI may have a value of 1. Or, when a UL DCI is transmitted immediately after a PTP retransmission, the total DAI of the UL DCI may have a value of 2. That is, in consideration of a case in which the terminal cannot receive DL DCI transmitted immediately before the UL DCI, the base station may indicate a total DAI for UCI transmission of PUSCH in the UL DCI.

[0188] FIG. 8 is a diagram for explaining a HARQ-ACK transmission method of a terminal according to one embodiment of the present disclosure.

[0189] In step S810, the terminal may receive DCI from the network, the DCI including DAI information and scheduling PUSCH transmission.

[0190] The DAI information may include one or more bits.

[0191] For example, when a semi-static (or type-1) HARQ-ACK codebook is configured for both unicast and multicast, the DAI information may include one bit associated with the HARQ-ACK codebook for both unicast and multicast. Here, whether to generate a HARQ-ACK codebook may be determined based on the value of the one bit. For example, if the value is 1, a HARQ-ACK codebook is generated, and if the value is 0, a HARQ-ACK codebook is not generated.

[0192] Or, when a semi-static (or type-1) HARQ-ACK codebook is configured for both unicast and multicast, the DAI information may include a first 1 bit associated with unicast HARQ-ACK information and a second 1 bit associated with multicast HARQ-ACK information. For example, whether to generate unicast HARQ-ACK information may be determined based on the value of the first 1 bit. For example, if the value is 1, unicast HARQ-ACK information may be generated, and if the value is 0, unicast HARQ-ACK information may not be generated. Also, whether to generate multicast HARQ-ACK information may be determined based on the value of the second 1 bit. For example, if the value is 1, multicast HARQ-ACK information may be generated, and if the value is 0, multicast HARQ-ACK information may not be generated.

[0193] Additionally or alternatively, a semi-static HARQ-ACK codebook may be configured for unicast, and a dynamic HARQ-ACK codebook may be configured for multicast. In this case, the DAI information may include one bit associated with the unicast HARQ-ACK codebook and two bits associated with the multicast HARQ-ACK information. For example, whether to generate the unicast HARQ-ACK codebook may be determined based on the value of the one bit associated with the unicast HARQ-ACK codebook. For example, if the value is 1, a unicast HARQ-ACK codebook may be generated, and if the value is 0, a unicast HARQ-ACK codebook may not be generated. Also, the number associated with the multicast HARQ-ACK information may be determined based on the value of the two bits associated with the multicast HARQ-ACK information. For example, two bit positions of the two bits may be 00, 01, 01, 11 (or the values ​​indicated by the two bits are 1, 2, 3, 4), which may correspond to information regarding the number of HARQ-ACK information bits in the multicast HARQ-ACK codebook or related numbers.

[0194] Additionally or alternatively, a dynamic HARQ-ACK codebook may be configured for unicast, and a semi-static HARQ-ACK codebook may be configured for multicast. In this case, the DAI information may include two bits associated with unicast HARQ-ACK information and one bit associated with a multicast HARQ-ACK codebook. For example, a number associated with the unicast HARQ-ACK information may be determined based on the value of the two bits associated with the unicast HARQ-ACK information. For example, two bit positions of the two bits may be 00, 01, 01, 11 (or the values ​​indicated by the two bits are 1, 2, 3, 4), which may correspond to information on the number of HARQ-ACK information bits in the unicast HARQ-ACK codebook or related numbers. Also, whether to generate the multicast HARQ-ACK codebook may be determined based on the value of the one bit associated with the multicast HARQ-ACK codebook. For example, if the value is 1, a multicast HARQ-ACK codebook is generated, and if the value is 0, a multicast HARQ-ACK codebook does not need to be generated.

[0195] In step S820, the terminal may generate a HARQ-ACK codebook based on the DAI information.

[0196] For example, based on the DAI information, a HARQ-ACK codebook for a particular cast type (e.g., unicast or multicast) may or may not be generated, or a HARQ-ACK codebook may be generated but HARQ-ACK information for the particular cast type may or may not be generated.

[0197] In step S830, the terminal multiplexes HARQ-ACK information on the PUSCH based on the HARQ-ACK codebook and transmits the multiplexed HARQ-ACK information to the network.

[0198] FIG. 9 is a diagram for explaining a HARQ-ACK receiving method of a base station according to an embodiment of the present disclosure.

[0199] In step S910, the base station may transmit a DCI including the DAI information and scheduling a PUSCH transmission to the terminal.

[0200] In step S920, the base station may receive HARQ-ACK information from the terminal, the HARQ-ACK information being multiplexed on the PUSCH, based on a HARQ-ACK codebook generated by the terminal based on the DAI information.

[0201] In the example of Figure 9, the configuration of DAI information and whether or not an HARQ-ACK codebook is generated and / or whether or not HARQ-ACK information is generated associated therewith may be the same as the example described with reference to Figure 8, and duplicate explanations will be omitted.

[0202] Next, various examples of the structure of the DAI included in the UL DCI including the above content that can be applied to the examples of Figures 8 and 9 will be described.

[0203] Unicast HARQ-ACK and multicast HARQ-ACK of the same priority may be multiplexed on the same PUSCH. In this case, the DCI that schedules the PUSCH may include a DAI field in the following format: The DAI included in the UL DCI may be referred to as the UL DAI.

[0204] The following examples may be distinguished according to the case of a unicast HARQ-ACK codebook type and a multicast HARQ-ACK codebook type.

[0205] The first assumption is that the unicast HARQ-ACK codebook and the multicast HARQ-ACK codebook are both set as type-1 (ie, semi-static size).

[0206] In this case, one bit of information included in the UL DAI (or the UL DAI is configured as a one-bit size field) can indicate whether the unicast HARQ-ACK and the multicast HARQ-ACK are multiplexed on the same PUSCH. For example, if the value of the one-bit UL DAI is a first value (e.g., 1), it can indicate that the unicast HARQ-ACK codebook and the multicast HARQ-ACK codebook are multiplexed on the same PUSCH. If the value of the UL DAI is a second value (e.g., 0), it can indicate that the unicast HARQ-ACK codebook and the multicast HARQ-ACK codebook are not multiplexed on the same PUSCH.

[0207] As another example, each bit of the 2-bit information included in the UL DAI (or the UL DAI is configured as a 2-bit size field) can individually indicate whether the unicast HARQ-ACK codebook and / or the multicast HARQ-ACK codebook are multiplexed on the same PUSCH. For example, if the first bit position value of the 2-bit UL DAI is a first value (e.g., 1), it can indicate that the unicast HARQ-ACK codebook is multiplexed on the same PUSCH. If the first bit position value of the UL DAI is a second value (e.g., 0), it can indicate that the unicast HARQ-ACK codebook is not multiplexed on the same PUSCH. For example, if the second bit position value of the 2-bit UL DAI is a first value (e.g., 1), it can indicate that the multicast HARQ-ACK codebook is multiplexed on the same PUSCH. If the second bit position value of the UL DAI is a second value (e.g., 0), it can indicate that the multicast HARQ-ACK codebook is not multiplexed on the same PUSCH.

[0208] For example, if only one sub-codebook is generated for all configured G-RNTIs, then one bit (e.g., the second bit position) of the 2-bit UL DAI may indicate whether the multicast HARQ-ACK codebook that applies to all configured G-RNTIs is multiplexed onto the same PUSCH.

[0209] For example, if N distinct sub-codebooks are generated for N distinct G-RNTIs, one bit (e.g., the second bit position) of the 2-bit UL DAI may indicate whether a multicast HARQ-ACK sub-codebook that applies to only one of the configured G-RNTIs is multiplexed onto the same PUSCH, where one G-RNTI may be the one that has a higher priority, is indicated by the network, or corresponds to the last (or most recently) scheduled PDSCH.

[0210] As another example, each bit of the N+1-bit information included in the UL DAI (or the UL DAI is configured as a field of N+1-bit size) may separately indicate whether each of the unicast HARQ-ACK codebook and / or the multicast HARQ-ACK codebook is multiplexed on the same PUSCH.

[0211] For example, when N separate sub-codebooks are generated for N separate G-RNTIs, each of the N+1 bits may indicate whether a multicast HARQ-ACK codebook applied to each G-RNTI of the configured G-RNTIs is multiplexed onto the same PUSCH. That is, N of the N+1 bits of the UL DAI are associated with a multicast HARQ-ACK codebook, and each of the N bits may indicate whether a multicast HARQ-ACK sub-codebook for one G-RNTI of the G-RNTIs is multiplexed onto the same PUSCH.

[0212] For example, if the first bit position value of the 3-bit UL DAI is a first value (e.g., 1), it can indicate that the unicast HARQ-ACK codebook is multiplexed on the same PUSCH. If the first bit position value of the UL DAI is a second value (e.g., 0), it can indicate that the unicast HARQ-ACK codebook is not multiplexed on the same PUSCH. For example, if the second bit position value of the 3-bit UL DAI is a first value (e.g., 1), it can indicate that the first multicast HARQ-ACK sub-codebook is multiplexed on the same PUSCH. If the second bit position value of the UL DAI is a second value (e.g., 0), it can indicate that the first multicast HARQ-ACK sub-codebook is not multiplexed on the same PUSCH. For example, if the third bit position value of the 3-bit UL DAI is a first value (e.g., 1), it can indicate that the second multicast HARQ-ACK sub-codebook is multiplexed on the same PUSCH. If the third bit position value of the UL DAI is a second value (eg, 0), it may indicate that the second multicast HARQ-ACK sub-codebook is not multiplexed on the same PUSCH.

[0213] The second assumption is that the unicast HARQ-ACK codebook and the multicast HARQ-ACK codebook are both set as type-2 (ie, dynamic size).

[0214] In this case, the 2-bit information included in the UL DAI (or the UL DAI is configured as a 2-bit size field) may be applied to both the unicast HARQ-ACK codebook and the multicast HARQ-ACK codebook. In a dynamic type HARQ-ACK codebook, the DAI value may indicate the number associated with the HARQ-ACK information (e.g., the number of PDSCH transmissions for which the HARQ-ACK information is generated, PDCCHs indicating SPS PDSCH release, etc.).

[0215] As another example, the first 2-bit information included in the UL DAI may apply to multicast, and the second 2-bit information may apply to unicast.

[0216] For example, one UL DAI may be applied to all G-RNTIs, or an individual UL DAI may be applied to each configured G-RNTI.

[0217] The third assumption is that the unicast HARQ-ACK codebook is set as type-1 (ie, semi-static size) and the multicast HARQ-ACK codebook is set as type-2 (ie, dynamic size).

[0218] In this case, one bit of information included in the UL DAI may be applied to unicast, and two bits of information may be applied to multicast. For example, of the three bits of information included in the UL DAI in the DCI (e.g., the UL DAI is configured as a three-bit size field), one bit may be associated with unicast, and two bits may be associated with multicast.

[0219] For example, the 1-bit information of the UL DAI can indicate whether the unicast HARQ-ACK codebook is multiplexed on the same PUSCH. For example, if the value of the 1-bit information of the UL DAI is a first value (e.g., 1), it can indicate that the unicast HARQ-ACK codebook is multiplexed on the same PUSCH. If the value of the 1-bit information is a second value (e.g., 0), it can indicate that the unicast HARQ-ACK codebook is not multiplexed on the same PUSCH.

[0220] The 2-bit information of the UL DAI can indicate the number associated with the multicast HARQ-ACK information (e.g., the number of PDSCH transmissions for which the HARQ-ACK information is generated, PDCCHs indicating SPS PDSCH release, etc.). For example, the 2-bit information of the UL DAI can indicate the number of HARQ-ACK information bits for the Type-2 multicast HARQ-ACK codebook.

[0221] The fourth assumption is that the unicast HARQ-ACK codebook is set as type-2 (ie, dynamic size) and the multicast HARQ-ACK codebook is set as type-1 (ie, semi-static size).

[0222] In this case, one bit of information included in the UL DAI may be applied to multicast, and two bits of information may be applied to unicast. For example, of the three bits of information included in the UL DAI in the DCI (e.g., the UL DAI is configured as a three-bit size field), one bit may be associated with multicast, and two bits may be associated with unicast.

[0223] For example, the 1-bit information of the UL DAI can indicate whether the multicast HARQ-ACK codebook is multiplexed on the same PUSCH. For example, if the value of the 1-bit information of the UL DAI is a first value (e.g., 1), it can indicate that the multicast HARQ-ACK codebook is multiplexed on the same PUSCH. If the value of the 1-bit information is a second value (e.g., 0), it can indicate that the multicast HARQ-ACK codebook is not multiplexed on the same PUSCH.

[0224] For example, if only one sub-codebook is generated for all configured G-RNTIs, one bit of the 3-bit UL DAI can indicate whether the multicast HARQ-ACK codebook applied to all configured G-RNTIs is multiplexed onto the same PUSCH.

[0225] For example, if N distinct sub-codebooks are generated for N distinct G-RNTIs, one bit of the 3-bit UL DAI may indicate whether a multicast HARQ-ACK sub-codebook that applies to only one of the configured G-RNTIs is multiplexed onto the same PUSCH, where one G-RNTI may be the one that has a higher priority, is indicated by the network, or corresponds to the last (or most recently) scheduled PDSCH.

[0226] The 2-bit information of the UL DAI can indicate the number associated with the unicast HARQ-ACK information (e.g., the number of PDSCH transmissions for which the HARQ-ACK information is generated, PDCCHs indicating SPS PDSCH release, etc.). For example, the 2-bit information of the UL DAI can indicate the number of HARQ-ACK information bits for the Type-2 unicast HARQ-ACK codebook.

[0227] Example 3

[0228] This embodiment relates to a method of configuring a UL DCI by separating a total DAI for unicast and a total DAI for multicast.

[0229] Here, the UL DCI may include a multicast total DAI for a multicast HARQ-ACK in addition to a unicast total DAI for a unicast HARQ-ACK, as follows:

[0230] Example 3-1

[0231] Multiple bits in the DAI field of the UL DCI can indicate the unicast total DAI and the multicast total DAI separately.

[0232] For example, N LSB bits and M MSB bits of the first DAI field or the second DAI field of DCI 0_1 can indicate the unicast total DAI and the multicast total DAI separately, or N MSB bits and M LSB bits of the first DAI field or the second DAI field of DCI 0_1 can indicate the unicast total DAI and the multicast total DAI separately, respectively.

[0233] Example 3-2

[0234] A reserved field or a specific field in the UL DCI can indicate the multicast total DAI.

[0235] For example, the ChannelAccess-CPext field of DCI 0_1 can indicate the multicast total DAI.

[0236] If the terminal receives PDSCHs for multiple G-RNTIs, the UL DCI can indicate the multicast total DAI value as follows.

[0237] Option 1: The sum of the total DAI values ​​for all G-RNTIs that the terminal reports it intends to receive or is interested in can be indicated.

[0238] For example, if a terminal reports to a base station that it will receive G-RNTI#1 and G-RNTI#2, and the current total DAI for G-RNTI#1 is 2 and the current total DAI for G-RNTI#2 is 3, the total DAI of the UL DCI may indicate 5, which is 2+3.

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

[0240] For example, if a terminal reports to a base station that it will receive G-RNTI#1 and G-RNTI#2, and the current total DAI for G-RNTI#1 is 2 and the current total DAI for G-RNTI#2 is 3, the UL DCI may include two separate total DAIs, indicating 2 and 3, respectively.

[0241] An individual total DAI value may be indicated in one field, and multiple total DAI values ​​may be concatenated in one field to form one bit string or bitmap. For example, if the individual total DAI values ​​for two G-RNTIs are each N bits, a bit string or bitmap may be formed such 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.

[0242] It may not be possible to indicate individual total DAI values ​​for all G-RNTIs due to limited field size, etc. In this case, the base station can indicate the total DAI for each G-RNTI as follows.

[0243] Option 2-1: The total DAI per G-RNTI can be indicated only for the maximum number of G-RNTIs.

[0244] For example, when the maximum number of G-RNTIs is set to 2 in the RRC message, if the terminal reports to the base station to receive G-RNTI#1, G-RNTI#2, and G-RNTI#3, the base station can configure the UL DCI to indicate only the total DAI for the two G-RNTIs among them that have the higher or lower G-RNTI values, respectively.

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

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

[0247] Option 2-2: The total DAI per G-RNTI can be indicated only for a selected set of G-RNTIs.

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

[0249] Alternatively, when the terminal reports to the base station that it will receive G-RNTI#1, G-RNTI#2, and G-RNTI#3, the terminal can recognize (or expect) that only the total DAI for the two G-RNTIs having the higher or lower G-RNTI values ​​is indicated in the UL DCI, without the base station informing it.

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

[0251] Option 3: It is possible to indicate only the total DAI value that has the highest value among the individual total DAI values ​​for each G-RNTI that the terminal reports that it intends to receive or is interested in.

[0252] For example, if a terminal reports to the base station to receive G-RNTI#1 and G-RNTI#2, and the current total DAI for G-RNTI#1 is 2 and the current total DAI for G-RNTI#2 is 3, the UL DCI may indicate 3, which has the highest total DAI value of both. Here, the UL DCI may further indicate an index for G-RNTI#2 (i.e., the G-RNTI associated with the highest total DAI value).

[0253] Option 4: All G-RNTIs that the terminal reports it intends to receive or is interested in are grouped into multiple G-RNTI groups, and the total DAI is indicated for each G-RNTI group. One G-RNTI group can contain one or more G-RNTIs.

[0254] For example, if the terminal reports to the base station to receive G-RNTI#1, G-RNTI#2, and G-RNTI#3, the base station may designate G-RNTI#1 and G-RNTI#2 as the first G-RNTI group and G-RNTI#3 as the second G-RNTI group in an RRC message. The base station may then configure the UL DCI to indicate the total DAI for each of the two G-RNTI groups.

[0255] Here, the total DAI value of the first G-RNTI group can indicate the sum of the total DAI values ​​for all G-RNTIs in the group, as in option 1.

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

[0257] Here, the total DAI value of the second G-RNTI group, which includes only one G-RNTI, is the same as the total DAI value of G-RNTI#3.

[0258] If there is a total DAI value of the G-RNTI that is missing due to such a total DAI indication method of the UL DCI, the terminal may also configure a type-2 based HARQ-ACK codebook only based on the total DAI of the DL DCI.

[0259] Example 4

[0260] This embodiment relates to a method for configuring a UL DCI that combines a unicast total DAI and a multicast total DAI.

[0261] For example, the UL DCI can combine the unicast total DAI for the unicast HARQ-ACK and the multicast total DAI for the multicast HARQ-ACK and indicate it as follows: Meanwhile, instead of the UL DCI, the DAI value of the following method can be transmitted by the group common MAC CE. Here, the PDSCH resource for transmitting the group common MAC CE may be allocated by the UL DCI.

[0262] Option 1: The sum of the total DAI value of all G-RNTIs that the terminal reports it intends to receive or is interested in and the total DAI value for unicast transmission can be indicated.

[0263] For example, if a terminal reports to a base station to receive G-RNTI#1 and G-RNTI#2, and the current total DAI for G-RNTI#1 is 2, the current total DAI for G-RNTI#2 is 3, and the current total DAI for unicast is 1, the total DAI of the UL DCI may indicate 6, which is 2+3+1.

[0264] Option 2: The terminal may indicate an individual total DAI value for each G-RNTI that it intends to receive or has reported an interest in, and a total DAI value for unicast separately. That is, the terminal may indicate a total DAI value for each G-RNTI and a total DAI value for unicast separately.

[0265] For example, if a terminal reports to a base station to receive G-RNTI#1 and G-RNTI#2, and the current total DAI for G-RNTI#1 is 2, the current total DAI for G-RNTI#2 is 3, and the current total DAI for unicast is 1, the UL DCI may include three total DAIs separately, indicating 2, 3, and 1, respectively.

[0266] An individual total DAI value may be indicated in one field, and multiple total DAI values ​​may be concatenated in one field to form one bit string or bitmap. For example, if the individual total DAI values ​​for two G-RNTIs are each N bits, a bit string or bitmap may be formed such 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. Furthermore, the unicast total DAI values ​​may be concatenated to form a final bit string or bitmap.

[0267] It may not be possible to indicate all total DAI values ​​due to limited field size, etc. In this case, the base station may indicate the unicast total DAI and the G-RNTI-specific total DAI as follows.

[0268] Option 2-1: The total DAI per G-RNTI can be indicated only for the maximum number of G-RNTIs.

[0269] For example, when the maximum number of G-RNTIs is set to 2 in the RRC message, if the terminal reports to the base station to receive G-RNTI#1, G-RNTI#2, and G-RNTI#3, the base station can configure the UL DCI to indicate only the total DAI for the two G-RNTIs having the higher or lower G-RNTI value among them, respectively. Furthermore, the UL DCI can be configured to indicate or not indicate the unicast total DAI together at the instruction of the base station.

[0270] Alternatively, when the maximum number of G-RNTIs is set to 2 in the RRC message, if the terminal reports to the base station to receive G-RNTI#1, G-RNTI#2, and G-RNTI#3, the base station can configure the UL DCI to indicate only the total DAI values ​​for the two G-RNTIs with the highest priority among them. Furthermore, the UL DCI can be configured to indicate or not indicate both the unicast total DAI at the instruction of the base station. Alternatively, the UL DCI can be configured to indicate only the total DAI for the unicast or G-RNTI with the highest priority, depending on the priority for the unicast and G-RNTI.

[0271] Alternatively, when the maximum number of G-RNTIs is set to 2 in the RRC message, if the terminal reports to the base station to receive G-RNTI#1, G-RNTI#2, and G-RNTI#3, the base station can configure the UL DCI to indicate only the total DAI values ​​for the two G-RNTIs that are pre-specified in the RRC message among them. Furthermore, the UL DCI can be configured to indicate or not indicate the unicast total DAI together at the instruction of the base station.

[0272] Option 2-2: The G-RNTI-specific total DAI can be indicated only for some selected G-RNTIs. Furthermore, the UL DCI can be configured to indicate or not indicate the unicast total DAI together at the instruction of the base station.

[0273] For example, when the terminal reports to the base station to receive G-RNTI#1, G-RNTI#2, and G-RNTI#3, the base station can configure the UL DCI to indicate only the total DAI for each of the two G-RNTIs notified to the terminal in the RRC message. Therefore, the total DAI for the unselected G-RNTIs does not need to be included in the UL DCI. Furthermore, the UL DCI can be configured to indicate or not indicate the unicast total DAI at the instruction of the base station.

[0274] Alternatively, when the terminal reports to the base station to receive G-RNTI#1, G-RNTI#2, and G-RNTI#3, the terminal can recognize (or expect) that only the total DAI for the two G-RNTIs having the higher or lower G-RNTI value is indicated in the UL DCI, without the base station informing it. Furthermore, the UL DCI can be configured to indicate or not indicate the unicast total DAI together at the instruction of the base station.

[0275] Alternatively, when the terminal reports to the base station to receive G-RNTI#1, G-RNTI#2, and G-RNTI#3, the terminal can recognize (or expect) that only the total DAI for the G-RNTI with higher priority (e.g., HP) is indicated in the UL DCI, even if the base station does not inform the terminal. Furthermore, the UL DCI can be configured to indicate or not indicate both the unicast total DAI at the instruction of the base station. Or, the terminal can recognize (or expect) that only the total DAI for the unicast or G-RNTI with higher priority (e.g., HP) is indicated in the UL DCI depending on the priority for the unicast and G-RNTI.

[0276] Option 3: It is possible to indicate only the total DAI value that has the highest value among the individual total DAI values ​​and the unicast DAI values ​​for each G-RNTI that the terminal reports it intends to receive or is interested in.

[0277] For example, if a terminal reports to the base station to receive G-RNTI#1 and G-RNTI#2, and the current total DAI for G-RNTI#1 is 2, the current total DAI for G-RNTI#2 is 3, and the unicast total DAI is currently 1, the UL DCI may indicate 3, which has the highest total DAI value. Here, the UL DCI may further indicate an index for G-RNTI#2 (i.e., the G-RNTI with the highest total DAI value).

[0278] Or, if a terminal reports to the base station to receive G-RNTI#1 and G-RNTI#2, and the current total DAI for G-RNTI#1 is 2, the current total DAI for G-RNTI#2 is 3, and the unicast total DAI is currently 4, then the UL DCI may indicate 4, which has the highest total DAI value. Here, the UL DCI (i.e., the one with the highest total DAI value) may further indicate an index for a unicast related element.

[0279] Option 4: All G-RNTIs that the terminal reports it intends to receive or is interested in are grouped into multiple G-RNTI groups, and a total DAI is indicated for each G-RNTI group. Furthermore, the UL DCI can be configured to indicate or not indicate the unicast total DAI at the instruction of the base station. Alternatively, the unicast total DAI can be set to be included in a specific G-RNTI group. Here, one G-RNTI group can include one or more elements (here, an element is a G-RNTI or a unicast-related element).

[0280] For example, if the terminal reports to the base station that it will receive G-RNTI#1, G-RNTI#2, and G-RNTI#3, the base station can designate G-RNTI#1 and G-RNTI#2 as the first group in the RRC message and designate G-RNTI#3 and unicast as the second group. The base station can configure the UL DCI to indicate the total DAI for both groups, respectively.

[0281] Here, the total DAI value for each group can be indicated as the sum of all the total DAI values ​​within the group, as in option 1.

[0282] Alternatively, the total DAI value for each group can indicate the highest total DAI value within the group, as in option 3.

[0283] Example 5

[0284] This embodiment relates to a type-2 codebook configuration method with HARQ-ACK deactivation.

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

[0286] If HARQ-ACK transmission for a specific G-RNTI is deactivated by RRC configuration, the terminal can determine that the total DAI for the specific G-RNTI is not included in the UL DCI. On the other hand, if HARQ-ACK transmission for a specific G-RNTI is deactivated by DCI, the terminal can determine that the total DAI for the specific G-RNTI is included in the UL DCI, taking into consideration the case where the terminal cannot receive the DCI. Alternatively, even if HARQ-ACK transmission for a specific G-RNTI is deactivated by DCI, the terminal can also determine that the total DAI for the specific G-RNTI is not included in the UL DCI.

[0287] In the above operation, the UL DCI may be replaced with either 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.

[0288] For a group-common DCI indicating HARQ-ACK activation / deactivation (or enable / disable), in generating a type-2 HARQ-ACK codebook, the terminal can expect that HARQ-ACK feedback for all PDSCHs transmitted in the same PUCCH slot is all enabled or all disabled. If the HARQ-ACK feedback for all PDSCHs for such a PUCCH slot is not all disabled in the same way, the terminal can determine that all DAIs for all corresponding PDSCHs are all enabled and configure a type-2 codebook.

[0289] Therefore, regardless of whether HARQ-ACK is enabled or disabled, the HARQ-ACK information bits of the Type 2 codebook can be configured by analyzing / assuming that all DAIs for all PDSCHs are enabled.

[0290] Alternatively, the HARQ-ACK information bits of the Type 2 codebook can be configured only for those HARQ-ACKs that are actually enabled.

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

[0292] FIG. 10 shows an example of signaling between the network side and a terminal (UE) in a situation where the above-described examples of the present disclosure (e.g., one or more combinations of Examples 1, 2, 3, 4, 5, or detailed examples thereof) can be applied.

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

[0294] 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 TRP1 and TRP2 constituting the network side. In addition, the following description is described based on multiple TRPs, but this may be equally extended and applied to transmission through multiple panels / cells, and may be equally extended and applied to transmission through multiple RRHs / RRUs, etc.

[0295] In addition, the following description will be based on "TRP", but as described above, "TRP" may be applied in place 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).

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

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

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

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

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

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

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

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

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

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

[0306] 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 have a connection relationship with one UE-specific BWP.

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

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

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

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

[0311] [Table 6]

[0312] For example, the operation of the UE (100 or 200 in FIG. 11) receiving the configuration information from the network side (200 or 100 in FIG. 11) in step S110 described above may be implemented by the apparatus in FIG. 11 described below. For example, referring to FIG. 11, 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.

[0313] The terminal may receive control information from the network side (S115). For example, the terminal may receive downlink control information (DCI) for scheduling / activating / releasing uplink / downlink from the network side.

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

[0315] For example, the operation of the UE (100 or 200 in FIG. 11) receiving the control information from the network side (200 or 100 in FIG. 11) in step S115 described above may be implemented by the apparatus in FIG. 11 described below. For example, referring to FIG. 11, one or more processors 102 may 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 may receive the control information from the network side.

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

[0317] 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 associated with the short ID of the MBS service, including a data unit for the SPS PDSCH case, or associated with a G-RNTI mapped to the MBS service by service-to-resource mapping, and transmit it to the terminal.

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

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

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

[0321] 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 the short ID, MTCH ID, MRB ID, G-RNTI value, and TMGI value for each PDSCH opportunity based on the mapping between the MBS service indicated in the DCI and the HPN and / or the mapping between the MBS service indicated in the DCI and the short ID.

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

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

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

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

[0326] 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 the terminal-specific "PUCCH-config" for multicast or unicast (unless "PUCCH-config" for multicast is set). Different PUCCH resources may be assigned to different terminals with the same PUCCH resource indicator and the same PDSCH-to-HARQ_feedback timing indicator of the group-common DCI.

[0327] In 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.

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

[0329] 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 or different PUCCH resources to different terminals of a group that receive the same DCI. Other PRIs in the DCI may point to other entries in "PUCCH-config".

[0330] Here, the candidate 'pucch-resourceId' values ​​may be configured by RRC, and distinct 'pucch-resourceId' values ​​may be configured for different terminals of the same group at least in the multicast 'PUCCH-config'.

[0331] As yet another example, a group-common PRI may be included in the DCI (option 1A-2). The single group-common PRI may be the same for all terminals of the group or may point to a specific entry for a candidate "pucch-resourceId" value in the terminal-specific "PUCCH-config" for other PUCCH resource allocations.

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

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

[0334] If the "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 a corresponding entry for the candidate "pucch-Resource Id" value of the "PUCCH-config" for unicast.

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

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

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

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

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

[0340] As an example, terminal 1 may use K1_ref, terminal 2 may use K1_ref+K1_offest1, and terminal 3 may use K1_ref+K1_offest2.

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

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

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

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

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

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

[0347] By using the PUCCH resources, the terminal may transmit HARQ-ACK for other PDSCH transmissions, such as a unicast SPS PDSCH, a dynamic unicast PDSCH, a PTP retransmission, and / or a dynamic group common PDSCH.

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

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

[0350] 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 between each "pdsch-AggregationFactor" consecutive slots or between each "repeat_number" consecutive slots, if set.

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

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

[0353] The terminal can monitor the group-common and / or UE-specific PDCCH using the TCI state for the search space set 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. However, the other terminals do not need to receive the retransmission of the TB because they have successfully received the TB.

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

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

[0356] In this case, 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.

[0357] For example, the operation of the UE (100 or 200 in FIG. 11) receiving a TB retransmission from a network side (200 or 100 in FIG. 11) in step S130 described above may be implemented by the apparatus in FIG. 11 described below. For example, referring to FIG. 11, 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.

[0358] Apparatus to which the present disclosure can be applied

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

[0360] Referring to FIG. 11, a first wireless device 100 and a second wireless device 200 can transmit and receive wireless signals using various wireless access technologies (eg, LTE, NR).

[0361] The first wireless device 100 includes one or more processors 102 and one or more memories 104, and may further include one or more transceivers 106 and / or one or more antennas 108. The processor 102 may be configured to control the memory 104 and / or the transceiver 106 to implement the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in the present disclosure. For example, the processor 102 may process 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 information obtained from signal processing of the second information / signal in the memory 104. The memory 104 may be coupled to the processor 102 and may store various information related to the operation of the processor 102. For example, the memory 104 may store software code including instructions for performing some or all of the processes controlled by the processor 102 or 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 implement a wireless communication technology (e.g., LTE, NR). The transceiver 106 may be coupled to the processor 102 and may transmit and / or receive wireless signals via one or more antennas 108. The transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may be referred to as a Radio Frequency (RF) unit. In the present invention, a wireless device may mean a communication modem / circuit / chip.

[0362] The second wireless 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 invention, a wireless device may mean a communication modem / circuit / chip.

[0363] The hardware elements of the wireless devices 100, 200 are described in more detail below. Without being limited thereto, one or more protocol layers may be embodied by one or more processors 102, 202. 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.

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

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

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

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

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

[0369] 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 to, 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.

[0370] Here, the wireless communication technology implemented in the wireless devices 100 and 200 of the present disclosure may include LTE, NR, and 6G as well as Narrowband Internet of Things (NB-IoT) for low power communication. At this time, for example, the NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) 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 wireless 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 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 wireless 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]

[0371] 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. 1. A method performed by a terminal in a wireless communication system, the method comprising: receiving downlink control information (DCI) from a network, the DCI including one or more bits of downlink allocation index (DAI) information and scheduling a physical uplink shared channel (PUSCH) transmission; generating a Hybrid Automatic Repeat Request (HARQ)-Acknowledgement (ACK) codebook based on the DAI information; multiplexing HARQ-ACK information on the PUSCH based on the HARQ-ACK codebook and transmitting the multiplexed HARQ-ACK information to the network; A method, wherein, based on a semi-static HARQ-ACK codebook being set for both unicast and multicast, the DAI information includes one bit associated with a HARQ-ACK codebook for both unicast and multicast, or the DAI information includes a first bit associated with unicast HARQ-ACK information and a second bit associated with multicast HARQ-ACK information.

2. The method of claim 1 , wherein it is determined whether to generate the HARQ-ACK codebook based on a value of one bit associated with a HARQ-ACK codebook for both the unicast and multicast.

3. determining whether to generate the unicast HARQ-ACK information based on a value of the first 1 bit; The method of claim 1 , further comprising: determining whether to generate the multicast HARQ-ACK information based on a value of the second 1 bit.

4. 2. The method of claim 1, wherein, based on a semi-static HARQ-ACK codebook being set for unicast and a dynamic HARQ-ACK codebook being set for multicast, the DAI information includes 1 bit associated with a unicast HARQ-ACK codebook and 2 bits associated with multicast HARQ-ACK information.

5. determining whether to generate the unicast HARQ-ACK codebook based on a value of one bit associated with the unicast HARQ-ACK codebook; The method of claim 4 , wherein a number associated with the multicast HARQ-ACK information is determined based on a value of two bits associated with the multicast HARQ-ACK information.

6. 2. The method of claim 1, wherein, based on a dynamic HARQ-ACK codebook being configured for unicast and a semi-static HARQ-ACK codebook being configured for multicast, the DAI information includes two bits associated with a unicast HARQ-ACK codebook and one bit associated with multicast HARQ-ACK information.

7. determining a number associated with the unicast HARQ-ACK information based on a 2-bit value associated with the unicast HARQ-ACK codebook; The method of claim 6 , further comprising: determining whether to generate the multicast HARQ-ACK codebook based on a value of one bit associated with the multicast HARQ-ACK information.

8. A terminal in a wireless communication system, the terminal comprising: one or more transceivers; one or more processors coupled to the one or more transceivers; The one or more processors: receiving downlink control information (DCI) from a network via the one or more transceivers, the DCI including one or more bits of downlink allocation index (DAI) information and scheduling a physical uplink shared channel (PUSCH) transmission; generating a hybrid automatic repeat request (HARQ)-acknowledgement (ACK) codebook based on the DAI information; multiplexing HARQ-ACK information on the PUSCH based on the HARQ-ACK codebook and transmitting the multiplexed HARQ-ACK information to the network via the one or more transceivers; A terminal, wherein, based on a semi-static HARQ-ACK codebook being set for both unicast and multicast, the DAI information includes one bit associated with a HARQ-ACK codebook for both unicast and multicast, or the DAI information includes a first bit associated with unicast HARQ-ACK information and a second bit associated with multicast HARQ-ACK information.

9. 1. A method performed by a base station in a wireless communication system, the method comprising: transmitting, to a terminal, downlink control information (DCI) including one or more bits of downlink allocation index (DAI) information and scheduling a physical uplink shared channel (PUSCH) transmission; receiving, from the terminal, hybrid automatic repeat request (HARQ)-acknowledgement (ACK) information multiplexed on the PUSCH based on a HARQ-ACK codebook generated by the terminal based on the DAI information; A method, wherein, based on a semi-static HARQ-ACK codebook being set for both unicast and multicast, the DAI information includes one bit associated with a HARQ-ACK codebook for both unicast and multicast, or the DAI information includes a first bit associated with unicast HARQ-ACK information and a second bit associated with multicast HARQ-ACK information.

10. A base station in a wireless communication system, the base station comprising: one or more transceivers; one or more processors coupled to the one or more transceivers; The one or more processors: transmitting downlink control information (DCI) to a terminal via the one or more transceivers, the DCI including one or more bits of downlink allocation index (DAI) information and scheduling a physical uplink shared channel (PUSCH) transmission; receiving, from the terminal via the one or more transceivers, hybrid automatic repeat request (HARQ)-acknowledgement (ACK) information multiplexed on the PUSCH based on a HARQ-ACK codebook generated by the terminal based on the DAI information; A base station, wherein, based on a semi-static HARQ-ACK codebook being set for both unicast and multicast, the DAI information includes one bit associated with a HARQ-ACK codebook for both unicast and multicast, or the DAI information includes a first bit associated with unicast HARQ-ACK information and a second bit associated with multicast HARQ-ACK information.

11. 1. A processing device configured to control a terminal in a wireless communication system, the processing device comprising: one or more processors; and one or more computer memories operably coupled to said one or more processors and storing instructions for performing the method according to any one of claims 1 to 7 when executed by said one or more processors.

12. One or more non-transitory computer-readable media storing one or more instructions, A computer readable medium, the one or more instructions being executed by one or more processors to control an apparatus in a wireless communication system to perform the method according to claims 1-7.

Images