Method and apparatus for transmitting or receiving hybrid automatic repeat request-acknowledgement information in a wireless communication system - Patents.com
The method allows for efficient multiplexing and transmission of multiple HARQ-ACK information bits in wireless communication systems by converting or selecting PUCCH resources, addressing the challenges of NACK-only reporting mode inefficiencies.
Patent Information
- Application Number
- JP2024525444
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2021-11-04
- Filing Date
- 2022-11-04
- Publication Date
- 2024-11-13
- Estimated Expiration
- 2042-11-04
AI Technical Summary
Existing wireless communication systems face challenges in efficiently multiplexing and transmitting multiple pieces of HARQ-ACK information in a NACK-only based reporting mode, leading to issues such as dropping of some HARQ-ACK information or conversion to other reporting modes.
A method for a terminal to generate N HARQ-ACK information bits associated with a second HARQ-ACK reporting mode and transmit them using either a first method of converting into a first HARQ-ACK reporting mode or selecting a PUCCH resource based on the value of the HARQ-ACK information bits, and a base station to receive these bits using similar methods based on network settings.
Enables efficient multiplexing and transmission of multiple HARQ-ACK information in a NACK-only based reporting mode, reducing information loss and improving communication efficiency in wireless systems.
Smart Images

Figure 2024541999000001_ABST
Abstract
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 were developed to provide voice services while ensuring user activity. However, the scope of mobile communication systems has expanded beyond voice to data services, and currently, resource shortages are occurring due to the explosive increase in traffic, and users are demanding faster services, so there is a demand for more advanced mobile communication systems.
[0003] The requirements for the next generation mobile communication system are to accommodate large and explosive data traffic, dramatically increase the transmission rate per user, accommodate a significantly increased number of connected devices, and 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] An object of the present disclosure is to provide a method and apparatus for multiplexing and transmitting or receiving multiple HARQ-ACK information in a NACK-only based reporting mode in a wireless communication system.
[0005] A further technical object of the present disclosure is to provide a method and apparatus for transmitting or receiving multiplexed HARQ-ACK information for multiple HARQ-ACK information in a NACK-only based reporting mode in a wireless communication system based on one or more of candidate resources mapped to the HARQ-ACK information, dropping some of the HARQ-ACK information, or converting it to HARQ-ACK information of another reporting mode.
[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] A method for a terminal to transmit HARQ-ACK information in a wireless communication system according to one embodiment of the present disclosure includes: generating N (N>1) HARQ-ACK information bits associated with a second HARQ-ACK reporting mode; and applying, on one physical uplink control channel (PUCCH), either a first scheme according to the first HARQ-ACK reporting mode or a second scheme of selecting one PUCCH resource from a set of PUCCH resources based on values of the N HARQ-ACK information bits, and transmitting the HARQ-ACK information to a network, wherein either the first scheme or the second scheme may be applied based on a setting by the network.
[0008] A method for a base station receiving hybrid automatic repeat request (HARQ)-acknowledgement (ACK) information in a wireless communication system according to a further aspect of the present disclosure includes: transmitting at least one of one or more multicast DCI formats or one or more multicast physical downlink shared channels (PDSCHs) to a terminal; and receiving from the terminal, via one physical uplink control channel (PUCCH), HARQ-ACK information to which either a first scheme according to a first HARQ-ACK reporting mode or a second scheme for selecting one PUCCH resource from a set of PUCCH resources based on values of the N HARQ-ACK information bits is applied, for N (N>1) HARQ-ACK information bits associated with a second HARQ-ACK reporting mode generated based on at least one of the one or more DCI formats or the one or more PDSCHs, wherein either the first scheme or the second scheme may be applied based on a configuration by the base station. Effect of the Invention
[0009] According to the present disclosure, it is possible to provide a method and apparatus for multiplexing and transmitting or receiving multiple HARQ-ACK information in a NACK-only based reporting mode in a wireless communication system.
[0010] According to the present disclosure, a method and apparatus may be provided for transmitting or receiving multiplexed HARQ-ACK information for a NACK-only based reporting mode in a wireless communication system based on one or more of candidate resources mapped to the HARQ-ACK information, dropping some HARQ-ACK information, or converting it to HARQ-ACK information of another reporting mode.
[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. [Diagram 2] 1 illustrates a frame structure in a wireless communication system to which the present disclosure can be applied. [Diagram 3] 1 illustrates an example of a resource grid in a wireless communication system to which the present disclosure can be applied. [Figure 4] 1 illustrates an example of a physical resource block in a wireless communication system to which the present disclosure can be applied. [Diagram 5] 1 illustrates an example of a slot structure in a wireless communication system to which the present disclosure can be applied. [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. [Figure 7] 1 illustrates an example of a situation in which HARQ-ACK information is duplicated in a NACK-only based reporting mode to which the present disclosure can be applied. [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. [Figure 9] A diagram for explaining a HARQ-ACK receiving method of a base station according to one embodiment of the present disclosure. [Figure 10] A diagram for explaining a signaling procedure between the network side and the terminal according to one embodiment of the present disclosure. [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
[0014] Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description disclosed below together with the accompanying drawings is intended to describe exemplary embodiments of the present disclosure, and is not intended to show the only embodiment in which the present disclosure can be implemented. The detailed description below includes specific details to provide a complete understanding of the present disclosure. However, it is understood by those skilled in the art that the present disclosure can be implemented without such specific details.
[0015] In some cases, in order to avoid obscuring the concepts of the present disclosure, known structures and devices may be omitted or may be shown in the form of a block diagram focusing on the core functions of each structure and device.
[0016] In this disclosure, when an element is "coupled," "coupled," or "connected" to another element, this can include a direct connection as well as an indirect connection where there is still another element between them. Also, in this disclosure, the terms "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.
[0017] In this disclosure, terms such as "first" and "second" are used only to distinguish one component from another component, and are not used to limit the components, and do not limit the order or importance of the components unless otherwise specified. Therefore, within the scope of this disclosure, a first component in one embodiment may be referred to as a second component in another embodiment, and similarly, a second component in one embodiment may be referred to as a first component in another embodiment.
[0018] The terms used in this disclosure are for the purpose of describing particular embodiments and are not intended to limit the scope of the claims. As used in the description of the embodiments and the appended claims, the singular form is intended to include the plural form unless the context dictates otherwise. The term "and / or" used in this disclosure means that one of the associated listed items may be included, or any and all possible combinations of two or more of them. Also, in this disclosure, " / " between words has the same meaning as "and / or" unless otherwise specified.
[0019] The present disclosure is described with respect to a wireless communication network or wireless communication system, and operations performed in the wireless communication network may be performed in a process in which a device (e.g., a base station) that manages the wireless communication network controls the network and transmits or receives signals, or in a process in which a terminal coupled to the wireless network transmits or receives signals to or between the network.
[0020] In this disclosure, transmitting or receiving a channel includes transmitting or receiving information or signals on that channel. For example, transmitting a control channel means transmitting control information or signals on the control channel. Similarly, transmitting a data channel means transmitting data information or signals on the data channel.
[0021] In the following, downlink (DL) means communication from a base station to a terminal, and uplink (UL) means communication from a terminal to a base station. In the downlink, a transmitter may be a part of the base station, and a receiver may be a part of the terminal. In the uplink, a transmitter may be a part of the terminal, and a receiver may be a part of the base station. The base station may be expressed as a first communication device, and the terminal may be expressed as a second communication device. A base station (BS) may be replaced with terms such as a fixed station, Node B, eNB (evolved-NodeB), gNB (Next Generation NodeB), BTS (base transceiver system), access point (AP), network (5G network), AI (Artificial Intelligence) system / module, RSU (road side unit), robot, drone (UAV: Unmanned Aerial Vehicle), AR (Augmented Reality) device, VR (Virtual Reality) device, etc. In addition, a terminal may be fixed or mobile, and may be replaced with terms such as User Equipment (UE), Mobile Station (MS), user terminal (UT), Mobile Subscriber Station (MSS), Subscriber Station (SS), Advanced Mobile Station (AMS), Wireless terminal (WT), Machine-Type Communication (MTC) device, Machine-to-Machine (M2M) device, Device-to-Device (D2D) device, vehicle, road side unit (RSU), robot, Artificial Intelligence (AI) module, drone (UAV: Unmanned Aerial Vehicle), Augmented Reality (AR) device, Virtual Reality (VR) device, etc.
[0022] The following technologies may be used for various wireless access systems such as CDMA, FDMA, TDMA, OFDMA, SC-FDMA, etc. CDMA may be implemented by radio technologies such as Universal Terrestrial Radio Access (UTRA) and CDMA2000. TDMA may be implemented by radio technologies such as Global System for Mobile communications (GSM) / General Packet Radio Service (GPRS) / Enhanced Data Rates for GSM Evolution (EDGE). OFDMA may be implemented by radio technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, Evolved UTRA (E-UTRA), etc. UTRA is part of the Universal Mobile Telecommunications System (UMTS). 3GPP (registered trademark) (3rd Generation Partnership Project) LTE (Long Term Evolution) is a part of E-UMTS (Evolved UMTS) that uses E-UTRA, and LTE-A (Advanced) / LTE-A pro is an evolved version of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an evolved version of 3GPP LTE / LTE-A / LTE-A pro.
[0023] For clarity of explanation, the following description will be based on a 3GPP communication system (e.g., LTE-A, NR), but the technical idea of the present disclosure is not limited thereto. LTE refers to technology after 3GPP TS (Technical Specification) 36.xxx Release 8. In detail, LTE technology after 3GPP TS 36.xxx Release 10 is called LTE-A, and LTE technology after 3GPP TS 36.xxx Release 13 is called LTE-A pro. 3GPP NR refers to technology after TS 38.xxx Release 15. LTE / NR may be called a 3GPP system. "xxx" refers to a standard document detail number. LTE / NR may be called a 3GPP system. For background technology, terms, abbreviations, etc. used in the description of the present disclosure, reference may be made to matters described in standard documents published before the present disclosure. For example, the following documents may be referenced.
[0024] In 3GPP LTE, reference can be made to TS 36.211 (physical channels and modulation), TS 36.212 (multiplexing and channel coding), TS 36.213 (physical layer procedures), TS 36.300 (general description), and TS 36.331 (radio resource control).
[0025] For 3GPP NR, reference can be made to TS 38.211 (Physical channels and modulation), TS 38.212 (Multiplexing and channel coding), TS 38.213 (Physical layer procedures for control), TS 38.214 (Physical layer procedures for data), TS 38.300 (General description of NR and NG-RAN (New Generation-Radio Access Network)), and TS 38.331 (Radio resource control protocol standard).
[0026] The following terminology abbreviations may be used in this disclosure:
[0027] - BM: Beam management
[0028] - CQI: channel quality indicator
[0029] - CRI: channel state information-reference signal resource indicator
[0030] - CSI: channel state information
[0031] - CSI-IM: channel state information-interference measurement
[0032] - CSI-RS: Channel state information-reference signal
[0033] - DMRS: Demodulation Reference Signal
[0034] - FDM: Frequency division multiplexing
[0035] - FFT: Fast Fourier transform
[0036] - IFDMA: Interleaved frequency division multiple access
[0037] - IFFT: inverse fast Fourier transform
[0038] - L1-RSRP: Layer 1 reference signal received power
[0039] - L1-RSRQ: Layer 1 reference signal received quality
[0040] - MAC: medium access control
[0041] - NZP: non-zero power
[0042] - OFDM: Orthogonal frequency division multiplexing
[0043] - PDCCH: physical downlink control channel
[0044] - PDSCH: physical downlink shared channel
[0045] - PMI: Precoding matrix indicator
[0046] - RE: resource element
[0047] - RI: Rank indicator
[0048] - RRC: Radio resource control
[0049] - RSSI: received signal strength indicator
[0050] - Rx: Reception
[0051] - QCL: quasi co-location
[0052] - SINR: signal to interference and noise ratio
[0053] - SSB (or SS / PBCH block): Synchronization signal block (including primary synchronization signal (PSS), secondary synchronization signal (SSS) and physical broadcast channel (PBCH))
[0054] - TDM: time division multiplexing
[0055] - TRP: transmission and reception point
[0056] - TRS: Tracking reference signal
[0057] - Tx: transmission
[0058] - UE: User Equipment
[0059] - ZP: Zero power
[0060] System in general
[0061] As more communication devices require larger communication capacity, the need for improved mobile broadband communication compared to existing radio access 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.
[0062] New RAT systems including NR use an OFDM transmission scheme or a similar transmission scheme. The new RAT system may follow OFDM parameters different from those of LTE. 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.
[0063] A numerology corresponds to a subcarrier spacing in the frequency domain. Different numerologies can be defined by scaling the reference subcarrier spacing by an integer N.
[0064] FIG. 1 illustrates the structure of a wireless communication system to which the present disclosure can be applied.
[0065] Referring to FIG. 1, the NG-RAN is composed of gNBs that provide an NG-Radio Access (NG-RA) user plane (i.e., a new access stratum (AS) sublayer / Packet Data Convergence Protocol (PDCP) / Radio Link Control (RLC) / MAC / PHY) and control plane (RRC) protocol termination for the UE. The gNBs are interconnected via an Xn interface. The gNBs are also connected to a New Generation Core (NGC) via an NG interface. More specifically, the gNBs are connected to an Access and Mobility Management Function (AMF) via an N2 interface and to a User Plane Function (UPF) via an N3 interface.
[0066] FIG. 2 illustrates a frame structure in a wireless communication system to which the present disclosure can be applied.
[0067] The NR system can support multiple numerologies, where the numerology may be defined by subcarrier spacing and cyclic prefix (CP) overhead. In this case, the multiple subcarrier spacing may be derived by scaling the base (reference) subcarrier spacing by an integer N (or μ). In addition, the numerology used may be selected independently of the frequency band, even if it is assumed that very low subcarrier spacing is not utilized at very high carrier frequencies. In addition, various frame structures with multiple numerologies may be supported in the NR system.
[0068] The following describes OFDM numerologies and frame structures that can be considered in the NR system. A number of OFDM numerologies supported in the NR system may be defined as shown in Table 1 below.
[0069] [Table 1]
[0070] NR supports multiple numerologies (or subcarrier spacing (SCS)) to support various 5G services, 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.
[0071] 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).
[0072] [Table 2]
[0073] 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.
[0074] 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.
[0075] [Table 3]
[0076] [Table 4]
[0077] 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.
[0078] 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.
[0079] 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.
[0080] FIG. 3 illustrates a resource grid in a wireless communication system to which the present disclosure can be applied.
[0081] 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. It is uniquely identified by JPEG2024541999000006.jpg617, where k=0,...,N RB μ N sc RB -1 is the index in the frequency domain, JPEG2024541999000007.jpg677 represents the position of a symbol within a subframe. When referring to a resource element in a slot, the index pair (k,l) is used, where l=0,...,N symb μ μ and the resource element for antenna port p. JPEG2024541999000008.jpg618 is a complex value JPEG2024541999000009.jpg911. 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 JPEG2024541999000010.jpg1130. Also, a resource block (RB) is N sc RB= 12 consecutive subcarriers.
[0082] Point A serves as a common reference point for the resource block grid and is obtained as follows:
[0083] - offsetToPointA for the primary cell (PCell) downlink indicates the frequency offset between the lowest subcarrier of the lowest resource block overlapping with the SS / PBCH block used by the terminal for initial cell selection and point A. It is expressed in resource block units assuming 15 kHz subcarrier spacing for FR1 and 60 kHz subcarrier spacing for FR2.
[0084] - absoluteFrequencyPointA indicates the frequency-location of point A expressed as in ARFCN (absolute radio-frequency channel number).
[0085] 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.
[0086]
number
[0087] 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.
[0088]
number
[0089] N BWP,i start,μ is the common resource block where the BWP starts relative to common resource block 0.
[0090] 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.
[0091] 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.
[0092] 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.
[0093] 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).
[0094] 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 the initially active DL / UL BWP.
[0095] 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.
[0096] 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.
[0097] 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.
[0098] 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).
[0099] 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: Random Access Procedure) 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: Physical Random Access Channel) (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.
[0100] 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.
[0101] 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.
[0102] Table 5 shows an example of a DCI format in an NR system.
[0103] [Table 5]
[0104] 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.), transmission block (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.
[0105] 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.
[0106] 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.
[0107] 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.
[0108] 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.
[0109] DCI format 1_0 is used for PDSCH scheduling in one DL cell. Information included in DCI format 1_0 is CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI and transmitted.
[0110] 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.
[0111] 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.
[0112] MBMS(Multimedia Broadcast Multicast Service)
[0113] 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.
[0114] 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.
[0115] 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.
[0116] SPS(semi-persistent scheduling)
[0117] 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.
[0118] The DCI of the UE-dedicated PDCCH may indicate the release or deactivation of a specific SPS configuration index. In this case, the UE does not receive the SPS transmission resource for which the release / deactivation is indicated.
[0119] 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).
[0120] MBS(Multicast Broadcast Service)
[0121] 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.
[0122] 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.
[0123] 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.
[0124] 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.
[0125] 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.
[0126] 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.
[0127] 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.
[0128] 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.
[0129] 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.
[0130] 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.
[0131] 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.
[0132] 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.
[0133] 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.
[0134] For example, for overlapping unicast HARQ-ACK and multicast HARQ-ACK transmissions, the following options may be considered:
[0135] Option 1: The terminal may give priority to transmitting unicast HARQ-ACKs and drop multicast HARQ-ACKs.
[0136] 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.
[0137] 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.
[0138] 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.
[0139] 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.
[0140] In the present disclosure, defining certain information between a terminal and a base station means that the terminal and the base station know the information without any additional signaling between the terminal and the base station, configuring the information between the terminal and the base station means transmitting / receiving the information through higher layer (e.g., RRC) signaling between the terminal and the base station, and indicating the information between the terminal and the base station can mean transmitting / receiving the information through lower layer (e.g., L1 (e.g., DCI / UCI), L2 (e.g., MAC-CE)) signaling.
[0141] FIG. 7 illustrates an example of an overlapping situation of HARQ-ACK information in a NACK-only based reporting mode to which the present disclosure can be applied.
[0142] 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, four sets of related / corresponding DCI (PDCCH), PDSCH, and HARQ-ACK are shown. In the example of Fig. 7, four HARQ-ACKs for four 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 related to time, but does not indicate absolute or relative time position, and illustrates a situation where HARQ-ACKs corresponding to different DCI / PDSCHs overlap (or are transmitted in the same slot).
[0143] In the example of Figure 7, the multicast DCI may be CRC scrambled with the G-RNTI. The multicast DCI may indicate high priority (HP) or low priority (LP). The HARQ-ACK for the multicast DCI / PDSCH is a NACK-only based HARQ-ACK.
[0144] In the example of Figure 7, the terminal can receive multiple multicast PDCCH / PDSCH scheduled with different G-RNTIs in an FDM or TDM manner. Here, the transmission of multicast HARQ-ACK information for the multicast PDCCH / PDSCH may be set / determined to be performed in the same slot. All the multicast HARQ-ACKs may be set as NACK-only based HARQ-ACKs. In this case, the terminal can transmit one or multiple PUCCHs for multiple NACK-only based HARQ-ACKs.
[0145] FIG. 8 is a diagram for explaining a HARQ-ACK transmission method of a terminal according to one embodiment of the present disclosure.
[0146] In step S810, the terminal may generate N HARQ-ACK information bits associated with a second HARQ-ACK reporting mode.
[0147] N may be defined as an integer greater than 1. That is, a number of HARQ-ACK information bits associated with the second HARQ-ACK reporting mode (ie, the NACK-only based HARQ-ACK reporting mode) may be generated.
[0148] The N HARQ-ACK information bits may be generated for at least one of one or more multicast DCI formats and / or one or more multicast PDSCHs received from the network, where the multicast DCI formats may be CRC scrambled with a group-radio network temporary identifier (G-RNTI) or a configured scheduling (G-CS)-RNTI.
[0149] In step S820, the terminal can transmit HARQ-ACK information to the network by applying either the first scheme or the second scheme in one PUCCH.
[0150] Here, either the first scheme or the second scheme may be applied based on a setting by the network (or the base station).
[0151] For example, the second scheme may be applied for N=k according to a configuration of a base station, and the first scheme may be applied for N>k according to a configuration of the base station, where k may be 2, 3, or 4. According to this example, the second scheme may be applied for 2, 3, or 4 NACK-only based HARQ-ACK information bits, and the first scheme may be applied for more than 4 NACK-only based HARQ-ACK information bits.
[0152] The first scheme may refer to a scheme of transmitting HARQ-ACK information according to a first HARQ-ACK reporting mode (i.e., an ACK / NACK based HARQ-ACK reporting mode), i.e., the first scheme may include converting and multiplexing N HARQ-ACK information bits associated with the second HARQ-ACK reporting mode into HARQ-ACK information bits of the first HARQ-ACK reporting mode.
[0153] Here, for the HARQ-ACK information bits of the (converted) first HARQ-ACK reporting mode, a PUCCH resource may be determined based on a PUCCH resource indicator (PRI) field included in a multicast DCI format, which may be a last DCI format among one or more multicast DCI formats. That is, the HARQ-ACK information bits of the (converted) first HARQ-ACK reporting mode may be transmitted on a PUCCH resource indicated by one or more DCI formats associated with the second HARQ-ACK reporting mode.
[0154] The second scheme may refer to a scheme in which one PUCCH resource is selected from a set of PUCCH resources based on the value of N HARQ-ACK information bits to transmit HARQ-ACK information. For example, the set of PUCCH resources may be 2 N -1 PUCCH resource candidates, each of which may correspond to a different combination of values of N HARQ-ACK information bits. If the value of the HARQ-ACK information bit is 0, it means that the terminal cannot correctly decode a transport block (TB), and if the value is 1, it means that the terminal correctly decodes the TB.
[0155] FIG. 9 is a diagram for explaining a HARQ-ACK receiving method of a base station according to an embodiment of the present disclosure.
[0156] In step S910, the base station may transmit at least one of one or more multicast DCIs or one or more multicast PDSCHs to the terminal.
[0157] In step S920, the base station may receive HARQ-ACK information to which either the first scheme or the second scheme is applied from the terminal via one PUCCH for N HARQ-ACK information bits associated with a second HARQ-ACK reporting mode generated based on one or more multicast DCI / PDSCHs.
[0158] In the example of Figure 9, the examples described with reference to Figure 8 can be applied equally to the N HARQ-ACK information bits associated with the second HARQ-ACK reporting mode, and the first and second schemes, so duplicated explanations will be omitted.
[0159] Various examples of transmitting multiple HARQ-ACK information bits associated with a second HARQ-ACK reporting mode (i.e., a NACK-only based HARQ-ACK reporting mode) on one PUCCH, including the above-mentioned content, which are applicable to the examples of Figures 8 and 9, are described below.
[0160] Example 1
[0161] This embodiment relates to a method in which a terminal configures a resource for NACK-only based HARQ-ACK transmission / reception and transmits / receives HARQ-ACK information using the resource. Here, the resource for HARQ-ACK transmission / reception may correspond to one or more of a PUCCH resource, a PUCCH resource block (RB), or a PUCCH sequence (e.g., a cyclic shift (CS) index).
[0162] It may be assumed that a PUCCH transmission of a NACK-only based HARQ-ACK collides with one or more other PUCCH transmissions of NACK-only based HARQ-ACKs or should be transmitted in the same slot. A terminal capable of simultaneously transmitting two PUCCHs can simultaneously transmit at least two NACK-only based HARQ-ACKs on different PUCCHs. In the case of a terminal that is not capable of simultaneously transmitting multiple PUCCHs or when more than two NACK-only based HARQ-ACKs collide, the following example may be applied for a terminal to multiplex and transmit NACK-only based HARQ-ACKs.
[0163] To support N HARQ-ACK transmissions for N (for example, N is an integer greater than 1) group common PDSCH transmissions being multiplexed in the same UL slot, the base station N - 1 PUCCH resource can be configured, where 2 N One PUCCH resource may be configured separately as a PUCCH resource for the NACK-only based HARQ-ACK reporting mode (eg, distinct from the PUCCH resource for the ACK / NACK based HARQ-ACK reporting mode).
[0164] Here, the group-common PDSCH may correspond to a group-common SPS PDSCH or a group-common SPS PDSCH scheduled by a DCI. In addition, the HARQ-ACK information bit may be generated for a multicast PDSCH scheduled by a DCI indicating activation / deactivation of SPS transmission and / or a multicast DCI.
[0165] It is also assumed that at least one PDSCH among the N group-common PDSCHs is scheduled by a DCI, which may include a PUCCH resource indicator (PRI).
[0166] For example, when N=k (e.g., k=2), the PUCCH resource indicated by the PRI is used as a reference PUCCH resource, and the reference PUCCH resource is included in the reference PUCCH resource. N Up to -1 (e.g. up to 3) PUCCH resources can be defined / configured.
[0167] If N>k, the PUCCH resource indicated by the PRI and the specified PUCCH resource are combined to form 2 N A PUCCH resource up to PRI-1 can be defined / configured. Here, the predetermined PUCCH resource may be a PUCCH resource corresponding to a value of PRI+1, or may be a PUCCH resource defined / configured for an adjacent RB (or PRB) of an RB (or PRB) configured for a PUCCH resource indicated by PRI.
[0168] For example, 2 N The PUCCH resources may be differentiated based on different time-frequency resources, or may be differentiated based on different PUCCH sequences or different cyclic shift values (eg, 0, 3, 6) applied to the PUCCH sequences.
[0169] For example, a PUCCH-config (i.e., a set of higher layer parameters) for NACK-only HARQ-ACK may be configured. For clarity of explanation, in the following example, it is assumed that three HARQ-ACKs (i.e., NACK-only HARQ-ACK information bits) for three group-common PDSCHs are multiplexed and transmitted in the same UL slot (i.e., N=3). In this case, HARQ-ACK information may be transmitted via one PUCCH depending on the combination of values of the three HARQ-ACK information bits (i.e., HARQ-ACK status).
[0170] When N=3, the maximum number of PUCCH resources per PUCCH resource set is 8 (=2 N) Among these, the maximum number of PUCCH resources (or PUCCH sequences) for the combination of NACK-only HARQ-ACK is 7 (=2 N It may be assumed that the PUCCH resource index indicated by the PRI of the last received DCI (e.g., the last received DCI among group common (or multicast) DCIs) is 4.
[0171] For the case where N=3, when three HARQ-ACKs are multiplexed in the same UL slot, the combinations of NACK-only HARQ-ACK information bits (i.e., HARQ-ACK states) are 7 (=2) as shown in the table below, except for the case where all three HARQ-ACKs are ACK. N -1) cases can be assumed. In the table below, N means NACK or 0, and A means ACK or 1.
[0172] [Table 6]
[0173] Based on the above assumptions, a specific example of a method for selecting one transmission resource from a set of transmission resources (e.g., PUCCH resources, RBs, sequences, CS indexes, etc.) based on the values of N HARQ-ACK information bits is described below.
[0174] Example 1-1
[0175] Based on the PUCCH resource indicated by the PRI of the last received group common DCI, N -1 PRI can be selected. 2 PRIs can be selected according to the decoding results for N group common PDSCHs. N -One of 1 HARQ-ACK states can be selected. 2 N - It is possible to transmit the HARQ-ACK multiplexed on the PUCCH resource according to the PRI corresponding to the HARQ-ACK state selected from one PRI.
[0176] For example, if the PRI value indicated by the DCI is 4, seven adjacent PRIs including 4 can be selected. That is, seven PRIs, PRI=4, 5, 6, 7, 8, 9, 10, can be selected.
[0177] If the maximum value of PRI is 8, PRI=4, 5, 6, 7, 8, 1, or 2 can be selected taking into account wraparound.
[0178] Assume that the value of the HARQ-ACK information bit for the first PDSCH is 1 (or ACK), the value of the HARQ-ACK information bit for the first PDSCH is 0 (or NACK), and the value of the HARQ-ACK information bit for the first PDSCH is 0 (or NACK). In this case, a PUCCH resource corresponding to HARQ-ACK state index 2 and PRI=5, which is the second PRI starting from PRI4, may be selected in the example of Table 6. The HARQ-ACK information transmitted / received in the selected PUCCH resource may indicate the success or failure of decoding each PDSCH (or the corresponding TB) corresponding to HARQ-ACK state index 2.
[0179] When all N group-common PDSCHs are SPS PDSCHs, the PRI indicated by the DCI may not exist. In this case, the PRI of the PUCCH resource of the group-common PDSCH corresponding to the lowest SPS configuration index, the highest SPS configuration index, or a higher priority among the N PDSCHs may be determined as the reference resource. N The PUCCH resources corresponding to one PRI may be selected as a PUCCH resource set.
[0180] As shown above, two PUCCH resources are included in one PUCCH resource set. N-1 PUCCH resource (or PRI) and 2 N - A one-to-one mapping relationship may be defined / set between one HARQ-ACK state and one HARQ-ACK state. For example, for the case where N=2, 3, or 4, the mapping relationship between the combination of HARQ-ACK information bits (i.e., HARQ-ACK states) and the PUCCH resources may be predefined / set as shown in the table below. In the example of Table 7, the transmission resource set may correspond to the set of exemplary PUCCH resources (or PRI) described above, or may be defined / set / determined by a combination of one or more of exemplary PUCCH resources, PUCCH RBs, PUCH sequences, or CS indexes described below.
[0181] [Table 7]
[0182] Example 1-2 Based on the RB corresponding to the PUCCH resource indicated by the PRI of the last received group common DCI, N -1 RB can be selected. 2 N -One of 1 HARQ-ACK states can be selected. 2 N - It is possible to transmit the HARQ-ACK multiplexed in the PUCCH resource by the RB corresponding to the HARQ-ACK state selected from one RB.
[0183] For example, when the PRI value indicated by the DCI is 4, seven adjacent RBs can be selected including the RB corresponding to the PUCCH resource indicated by PRI = 4. That is, when the RB (or starting PRB) index set for the PUCCH resource indicated by PRI = 4 is RB #4, seven RBs, RB #5, RB #6, RB #7, RB #8, RB #9, and RB #10, can be selected.
[0184] If additional RBs need to be selected after the RB indexes have been selected in ascending order up to the maximum value in the UL BWP, the required number of additional RBs may be selected starting from the lowest RB in the UL BWP.
[0185] Assume that the value of the HARQ-ACK information bit for the first PDSCH is 1 (or ACK), the value of the HARQ-ACK information bit for the first PDSCH is 0 (or NACK), and the value of the HARQ-ACK information bit for the first PDSCH is 0 (or NACK). In this case, in the example of Table 6, a PUCCH resource corresponding to HARQ-ACK state index 2 and RB#5, which is the second RB from RB#4, which is the RB index corresponding to the PUCCH resource indicated by PRI=4, may be selected. HARQ-ACK information transmitted / received using the selected PUCCH resource may indicate the success or failure of decoding each PDSCH (or the corresponding TB) corresponding to HARQ-ACK state index 2.
[0186] If all N group-common PDSCHs are SPS PDSCHs, there may be no PRI indicated by DCI. In this case, the RB corresponding to the PUCCH resource of the group-common PDSCH corresponding to the lowest SPS configuration index, the highest SPS configuration index, or a higher priority among the N PDSCHs may be determined as the reference resource. N A PUCCH resource corresponding to one RB may be selected as a PUCCH resource set.
[0187] Examples 1-3
[0188] Based on the PUCCH sequence of the PUCCH resource indicated by the PRI of the last received group common DCI, N-1 PUCCH sequence can be selected. Here, adjacent PUCCH sequences can be based on PRI. 2 N -One of 1 HARQ-ACK states can be selected. 2 N - It is possible to transmit the HARQ-ACK multiplexed on the PUCCH resources according to the PUCCH sequence corresponding to the HARQ-ACK state selected from one PUCCH sequence.
[0189] For example, when the PRI value indicated by the DCI is 4, the PUCCH sequence of the PUCCH resource indicated by PRI=4 is determined as the reference resource, and seven PUCCH sequences corresponding to seven adjacent CS indexes including the cyclic shift (CS) index of the reference PUCCH sequence can be selected. That is, when the CS index of the PUCCH sequence of the PUCCH resource indicated by PRI=4 is CS#4, PUCCH sequences based on seven CS indexes, CS#5, CS#6, CS#7, CS#8, CS#9, and CS#10, can be selected. This corresponds to the case where a PUCCH resource set can be configured with PUCCH sequences applicable to one PUCCH resource.
[0190] If the number of CS index resource candidates applicable to one PUCCH resource is X (e.g., X=4), seven CS indexes cannot be selected for one PUCCH resource, and only up to four CS indexes can be selected. The remaining three CS indexes may be selected from CS index resource candidates applied to PUCCH sequences for other PUCCH resources (e.g., adjacent PUCCH resources based on PRI). For example, four PUCCH sequences corresponding to four CS resource indexes of a PUCCH resource corresponding to PRI=4 are selected, and three PUCCH sequences corresponding to three CS resource indexes of an adjacent PUCCH resource corresponding to PRI=5 are selected, so that the transmission resource set can include seven PUCCH sequences.
[0191] For example, X=4 PUCCH sequences for one PUCCH resource may be PUCCH sequences corresponding to CS indexes 0, 3, 6, and 9. For example, the four CS indexes may be selected in the order of 0, 6, 3, and 9.
[0192] Assume that the value of the HARQ-ACK information bit for the first PDSCH is 1 (or ACK), the value of the HARQ-ACK information bit for the first PDSCH is 0 (or NACK), and the value of the HARQ-ACK information bit for the first PDSCH is 0 (or NACK). This may correspond to HARQ-ACK state index 2 in the example of Table 6. Four PUCCH sequences (i.e., CS indexes 0, 6, 3, 9) for PUCCH resources corresponding to PRI=4 and three PUCCH sequences (i.e., CS indexes 0, 6, 3) for PUCCH resources corresponding to PRI=5 may be included in the transmission resource set. Resource index 2 in the transmission resource set corresponding to HARQ-ACK state index 2 may be selected as the PUCCH sequence to apply CS index 6 to the PUCCH resource corresponding to PRI=4. The HARQ-ACK information transmitted / received using a PUCCH resource based on the selected PUCCH sequence may indicate whether each PDSCH (or the corresponding TB) corresponding to HARQ-ACK status index 2 has been decoded successfully or not.
[0193] If all N group-common PDSCHs are SPS PDSCHs, there may be no PRI indicated by DCI. In this case, a PUCCH sequence corresponding to a PUCCH resource of a group-common PDSCH corresponding to the lowest SPS configuration index, the highest SPS configuration index, or a higher priority among the N PDSCHs may be determined as a reference resource. A total of two PUCCH sequences including the PUCCH sequence (i.e., CS resource index) corresponding to the reference resource and the subsequent PUCCH sequence (or CS resource index) based on the PRI may be determined as a reference resource. N PUCCH resources corresponding to one PUCCH sequence may be selected as a PUCCH resource set.
[0194] Examples 1-4
[0195] Based on the PUCCH sequence of the PUCCH resource indicated by the PRI of the last received group common DCI, N -1 PUCCH sequence can be selected. Here, adjacent PUCCH sequences can be based on RB. 2 N -One of 1 HARQ-ACK states can be selected. 2 N - It is possible to transmit the HARQ-ACK multiplexed on the PUCCH resources according to the PUCCH sequence corresponding to the HARQ-ACK state selected from one PUCCH sequence.
[0196] When a PUCCH resource set is configured with PUCCH sequences applicable to one PUCCH resource, a PUCCH resource set including adjacent PUCCH sequences (or CS resource indexes) may be configured in the same manner as in Examples 1-3.
[0197] If the number of candidates for CS index resources applicable to one PUCCH resource is X (e.g., X=4), seven CS indexes cannot be selected for one PUCCH resource, and only up to four CS indexes can be selected. The remaining three CS indexes may be selected from CS index resource candidates applied to PUCCH sequences for other PUCCH resources (e.g., PUCCH resources adjacent based on RB). For example, four PUCCH sequences corresponding to four CS resource indexes of a PUCCH resource corresponding to PRI=4 may be first selected. When RB#n is configured for a PUCCH resource corresponding to PRI=4, three PUCCH sequences corresponding to three CS resource indexes of a PUCCH resource corresponding to RB#n+1 may be further selected. As a result, the transmission resource set can include seven PUCCH sequences.
[0198] For example, X=4 PUCCH sequences for one PUCCH resource may be PUCCH sequences corresponding to CS indexes 0, 3, 6, and 9. For example, the four CS indexes may be selected in the order of 0, 6, 3, and 9.
[0199] Assume that the value of the HARQ-ACK information bit for the first PDSCH is 1 (or ACK), the value of the HARQ-ACK information bit for the first PDSCH is 0 (or NACK), and the value of the HARQ-ACK information bit for the first PDSCH is 0 (or NACK). This may correspond to HARQ-ACK state index 2 in the example of Table 6. Four PUCCH sequences (i.e., CS indexes 0, 6, 3, 9) for PUCCH resources corresponding to PRI=4 and RB#n, and three PUCCH sequences (i.e., CS indexes 0, 6, 3) for PUCCH resources corresponding to RB#n+1 may be included in the transmission resource set. Resource index 2 in the transmission resource set corresponding to HARQ-ACK state index 2 may be selected as a PUCCH sequence that applies CS index 6 to PUCCH resources corresponding to PRI=4. The HARQ-ACK information transmitted / received on the PUCCH resource based on the selected PUCCH sequence may indicate the success or failure of decoding of each PDSCH (or the corresponding TB) corresponding to HARQ-ACK status index 2.
[0200] If all N group-common PDSCHs are SPS PDSCHs, there may be no PRI indicated by DCI. In this case, a PUCCH sequence corresponding to a PUCCH resource of a group-common PDSCH corresponding to the lowest SPS configuration index, the highest SPS configuration index, or a higher priority among the N PDSCHs may be determined as a reference resource. A total of two PUCCH sequences including the PUCCH sequence (i.e., CS resource index) corresponding to the reference resource and the subsequent PUCCH sequence (or CS resource index) on an RB basis may be determined as a reference resource. N The PUCCH resources corresponding to one PUCCH sequence may be selected as a PUCCH resource set.
[0201] In the first embodiment and the detailed embodiment, since all N group-common PDSCHs are SPS PDSCHs, when there is no PRI indicated by DCI, the reference resource may be determined based on sps-PUCCH-AN, which is PUCCH resource configuration information for HARQ-ACK for SPS transmission, and sps-PUCCH-AN-List corresponding to the list. For example, the PUCCH resource listed first or last in sps-PUCCH-AN-List, or the PUCCH resource corresponding to the lowest or highest RB, may be determined as the reference resource. In this way, adjacent PUCCH resources including the PUCCH resource corresponding to the reference resource may be included in the PUCCH resource set.
[0202] Example 2
[0203] For N NACK-only based HARQ-ACKs transmitted in the same UL slot, the terminal can apply the above-mentioned method (i.e., Example 1 or a detailed example thereof) or the method described below (i.e., Example 2 or a detailed example thereof) depending on the configuration of the base station.
[0204] The setting of the base station may be related to a predetermined threshold. The predetermined threshold may be related to the above-mentioned N value (i.e., the number of NACK-only HARQ-ACK reporting mode based HARQ-ACK information bits to be multiplexed). For example, when the N value is equal to or less than k (i.e., the threshold), the first embodiment may be applied, and when the N value exceeds k, the second embodiment may be applied. For example, k may be 2, 3, or 4. For example, when the N value is equal to or less than 4, the method of the first embodiment of selecting one PUCCH resource from a set of PUCCH resources based on the values of N HARQ-ACK information bits (i.e., HARQ-ACK status) may be applied. When the N value exceeds 4, the method of the second embodiment of dropping some NACK-only based HARQ-ACK information bits or transforming them into ACK / NACK based HARQ-ACK information bits and transmitting multiplexed HARQ-ACK information may be applied, as described below.
[0205] Such threshold k may be set by the base station to the terminal or may be predefined as a fixed value between the base station and the terminal. That is, when the base station configuration is provided, the first embodiment may be applied to N values equal to or less than the fixed k, even if the k value is not separately set / instructed to the terminal.
[0206] In addition, when the base station sets the threshold value, the base station can also set the threshold for each G-RNTI, for each PUCCH-config, for each CFR (common frequency resource), for each UL BWP, or for each serving cell.
[0207] Example 2-1
[0208] Of the N NACK-only based HARQ-ACK information bits, HARQ-ACK information bits exceeding a threshold k (or equal to or greater than k) may be dropped, and HARQ-ACK information bits less than the threshold k (or equal to or less than k) may be multiplexed.
[0209] For example, HARQ-ACK information bits with low priority may be dropped in preference to HARQ-ACK information bits with high priority, i.e., only a threshold number of HARQ-ACK information bits with high priority may be multiplexed.
[0210] Additionally or alternatively, HARQ-ACK information bits for the most recently received PDSCH may be dropped in preference to HARQ-ACK information bits for previously received PDSCHs, i.e., only a threshold number of previously received HARQ-ACK information bits for group-common PDSCHs may be multiplexed.
[0211] Additionally or alternatively, HARQ-ACK information bits with a large remaining PDB (Packet Data Budget) may be dropped preferentially over HARQ-ACK information bits with a small remaining PDB, i.e., only HARQ-ACKs for TBs with a threshold number of small remaining PDBs may be multiplexed.
[0212] Additionally or alternatively, SPS PDSCHs not scheduled in DCI may be preferentially dropped, where among SPS PDSCHs, SPS PDSCHs for higher SPS-config indices may be preferentially dropped, and therefore SPS PDSCHs for lower SPS-config indices may be preferentially multiplexed.
[0213] Additionally or alternatively, a group-common PDSCH scheduled in a DCI may be preferentially dropped. Then, among the SPS PDSCHs, an SPS PDSCH for a higher SPS-config index may be preferentially dropped. Thus, an SPS PDSCH for a lower SPS-config index may be preferentially multiplexed.
[0214] Example 2-2
[0215] When the value of N exceeds (or is equal to or greater than) the threshold value k, all NACK-only based HARQ-ACK information bits may be transformed into ACK / NACK based HARQ-ACK information bits, and one PUCCH resource may be selected to transmit / receive the multiplexed HARQ-ACK. That is, when N<=k, a scheme of selecting one PUCCH resource from a set of PUCCH resources based on the values of N HARQ-ACK information bits (i.e., HARQ-ACK status) according to the first embodiment may be applied.
[0216] Here, the PUCCH resource selected for transmission of the (converted) HARQ-ACK information bit may correspond to the PUCCH resource / transmission indicated by the PRI of the last received DCI.
[0217] Or, the 2 described in Example 1 N - Applying the method of selecting one transmission resource (for example, based on one or more combinations of PRI-based PUCCH resources, PUCCH RBs, or PUCCH sequences) as is, N 2 transmission resources may be selected. N One transmission resource (e.g., PUCCH resource / RB / sequence) from among the transmission resources may be defined / configured as the PUCCH resource / transmission (i.e., selected for transmitting the (converted) HARQ-ACK information bit) for the case where N>k.
[0218] Alternatively, the PUCCH resource selected for transmission of the (converted) HARQ-ACK information bits may be selected by the PUCCH-config for unicast or the PUCCH-config for ACK / NACK based HARQ-ACK for multicast. In case the PUCCH-config for multicast is not configured, the PUCCH resource may be selected by the configuration of the PUCCH-config for unicast.
[0219] If all N group-common PDSCHs are SPS PDSCHs, there may be no PRI indicated by the DCI. In this case, the PUCCH resource of the group-common PDSCH corresponding to the lowest SPS configuration index, the highest SPS configuration index, or a higher priority among the N PDSCHs may be selected for transmitting the (converted) HARQ-ACK information bit.
[0220] The base station may set the aforementioned N or k value to a specific value, where the N or k value may be set to be adjusted according to (or in consideration of) the RSRP measurement value of the serving cell measured by the terminal.
[0221] 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.
[0222] FIG. 10 shows an example of signaling between the network side and a terminal (UE) in a situation in which the above-described examples of the present disclosure (e.g., a combination of one or more of Examples 1, 2, or detailed examples thereof) can be applied.
[0223] 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.
[0224] 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.
[0225] 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).
[0226] 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.).
[0227] 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.
[0228] The terminal may enter an RRC_CONNECTED mode and report a message indicating one or more interested MBS services to the network side (S105).
[0229] 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.
[0230] 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.
[0231] 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.
[0232] 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.
[0233] Upon receiving the message, the network side can send configuration information to the terminal through an RRC message (S110).
[0234] 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.
[0235] Here, 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 UE-specific Dedicated Control Channel (DCCH).
[0236] 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.
[0237] 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.
[0238] 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.
[0239] 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.
[0240] 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.
[0241] [Table 8]
[0242] Meanwhile, when a specific PUCCH resource is configured as a NACK-only based HARQ-ACK, the base station may provide the terminal with an RRC information element (IE) for the specific PUCCH resource formed in the following manner. Scheme 1A: The terminal may distinguish between NACK-only and ACK / NACK based on different PRIs and PUCCH resource IDs.
[0243] Method 1A-1: For each PUCCH resource, an indication of whether or not NACK-only based HARQ-ACK is configured may be included. For example, the PUCCH resource, which is an RRC IE for a specific PUCCH resource, may include one or more of an IE for a PUCCH resource ID or an indication IE for NACK only.
[0244] Method 1A-2: The RRC IE for a PUCCH resource set including a specific PUCCH resource may include a PUCCH resource IE for NACK-only (e.g., 4 to 7 PUCCH resources are configured as NACK-only based HARQ-ACK) and a PUCCH resource IE for ACK / NACK (e.g., 0 to 3 PUCCH resources are configured as ACK / NACK based HARQ-ACK). All of these IEs may be mapped to the same PUCCH resource set ID. In this case, different PUCCH resources may be configured for ACK / NACK and NACK-only in the same PUCCH resource set based on different PUCCH resource IDs.
[0245] Scheme 1B: NACK-only and ACK / NACK may be distinguished based on another indicator in the DCI.
[0246] Method 1B-1: In the RRC configuration, both ACK / NACK and NACK only may be configured for the same PUCCH resource ID. Another indicator may be defined and included in the DCI to indicate whether to apply the ACK / NACK configuration or the NACK only configuration. Therefore, in the RRC configuration, it is not necessary to configure whether to support NACK only for each PUCCH resource.
[0247] Even in the case of following the method 1B-1, it is possible to configure whether to support NACK-only on a PUCCH-config basis or on a PUCCH resource set basis. In this case, the terminal may assume that all PUCCH resources in the PUCCH-config or PUCCH resource set can also support NACK-only.
[0248] Scheme 1B-2: Individual PUCCH resource sets in the PUCCH-config may be configured as ACK / NACK-based HARQ-ACK or NACK-only based HARQ-ACK. For example, the PUCCH-config RRC IE may include a PUCCH resource set IE for NACK-only (e.g., PRIs 0-7 are all configured as NACK-only based HARQ-ACK) and a PUCCH resource set IE for ACK / NACK (e.g., PRIs 0-7 are all configured as ACK / NACK-based HARQ-ACK).
[0249] Configuration method 1B-3: Each PUCCH-config in the PUCCH-configurationList may be configured as ACK / NACK-based HARQ-ACK or NACK-only based HARQ-ACK. For example, the PUCCH-configurationList RRC IE may include a PUCCH-config IE for NACK-only (e.g., all PUCCH resources corresponding to PRI 0 to 7 for the PUCCH resource set of the PUCCH-config are configured as NACK-only based HARQ-ACK) and a PUCCH-config IE for ACK / NACK (e.g., all PUCCH resources corresponding to PRI 0 to 7 for the PUCCH resource set of the PUCCH-config are configured as ACK / NACK-based HARQ-ACK).
[0250] In the prior art, up to four PUCCH resource sets for ACK / NACK may be configured in consideration of the payload size. One PUCCH resource set for NACK may be sufficient. For example, it may be sufficient to configure only PUCCH resource set 0 for PUCCH format 0 (PF0) and PUCCH format 1 (PF1). Therefore, in the above-mentioned configuration method, the terminal may determine a PUCCH resource set for NACK-only based HARQ-ACK in the following manner. That is, the method of determining a PUCCH resource set for NACK-only based HARQ-ACK from a plurality of PUCCH resource sets configured by the base station is as follows.
[0251] Method 1-1: When NACK-only based HARQ-ACK and ACK / NACK based HARQ-ACK share the same PUCCH resource set, only the first PUCCH resource set in a list of up to four PUCCH resource sets in the PUCCH-config (i.e., the PUCCH resource set with PUCCH resource set ID=0) may be configured as the NACK-only based HARQ-ACK.
[0252] Alternatively, the initial PUCCH resource set may be configured such that only NACK-only based HARQ-ACK is possible in the multicast PUCCH-config without a separate NACK-only based HARQ-ACK indication, or such that both NACK-only based HARQ-ACK and ACK / NACK based HARQ-ACK are possible.
[0253] Scheme 1-2: The base station can configure whether the first or a specific PUCCH resource set in up to four PUCCH resource set lists in the PUCCH-config is used as NACK-only based HARQ-ACK.
[0254] Scheme 1-2A: Whether the first or a specific PUCCH resource set is used as NACK-only based HARQ-ACK may be indicated in the PUCCH-config or in the PUCCH resource sets of the PUCCH-config.
[0255] Method 1-2B: Whether the first PUCCH resource set is used as NACK-only based HARQ-ACK may be indicated by DCI. For example, when a DCI indicates NACK-only based HARQ-ACK, the terminal can determine that the first or a specific PUCCH resource set of the PUCCH-config is used as NACK-only based HARQ-ACK, and the PUCCH resource indicated by the PRI of the DCI is a PUCCH resource in the first or a specific PUCCH resource set.
[0256] Method 1-3: When the DCI indicates a NACK-only based HARQ-ACK, the terminal can always select a PUCCH resource indicated by the PRI of the DCI from the initial PUCCH resource set and transmit the NACK-only based HARQ-ACK.
[0257] Alternatively, when a specific PUCCH resource set is configured as a NACK-only based HARQ-ACK in the PUCCH-config, if the DCI indicates a NACK-only based HARQ-ACK, the terminal can always select a PUCCH resource indicated by the PRI of the DCI from the specific PUCCH resource set and transmit a NACK-only based HARQ-ACK.
[0258] 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.
[0259] 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.
[0260] 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.
[0261] 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.
[0262] The terminal can receive the TB from the network side (S120).
[0263] 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.
[0264] 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.
[0265] 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.
[0266] 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.
[0267] 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.
[0268] 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.
[0269] 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.
[0270] 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.
[0271] 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.
[0272] 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.
[0273] 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.
[0274] Here, the PRI (PUCCH Resource Indicator) may be indicated by a group-common DCI, as described later.
[0275] 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".
[0276] 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'.
[0277] 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.
[0278] 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.
[0279] 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.
[0280] 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.
[0281] K1 (PDSCH-to-HARQ_feedback timing indicator) may be indicated by a group-common DCI as described below.
[0282] 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.
[0283] 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.
[0284] 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.
[0285] 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.
[0286] 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.
[0287] 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.
[0288] As yet another example, the candidate 'dl-DataToUL-ACK' values may be configured by RRC and separately for different terminals of the same group at least in the 'PUCCH-config' for multicast.
[0289] 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.
[0290] 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.
[0291] 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.
[0292] If an SPS configuration is activated by the terminal based on an interested MBS service, the terminal may periodically receive SPS transmission opportunities on the configured downlink allocation for the SPS configuration according to the above mathematical formula. The terminal may consider the NDI to be toggled for each reception of an SPS PDSCH opportunity.
[0293] Upon reception of a particular SPS PDSCH transmission opportunity in a configured downlink allocation for an SPS configuration, the terminal may consider that SPS PDSCH transmission opportunity to be associated with the MTCH, MRB, TMGI, G-RNTI and / or short ID of the MBS service based on the mapping between the MBS service and the SPS configuration, the mapping between the MBS service and the HARQ Process Number (HPN) for the SPS configuration, and / or the mapping between the MBS service and the short ID (if available), as indicated by the activation DCI or retransmission DCI and / or as configured by an RRC message.
[0294] When a group-common SPS PDSCH and a unicast SPS PDSCH are scheduled in the same DL slot, if a terminal cannot receive all the SPS PDSCHs, the terminal can select some of the SPS PDSCHs as follows.
[0295] Option A: The terminal may select an SPS PDSCH based on an ascending order of SPS configuration index starting from the lowest SPS configuration index for both the group-common SPS PDSCH and the unicast SPS PDSCH. The terminal may not receive any unselected SPS PDSCH.
[0296] The base station can set separate SPS configuration indexes for the group-common SPS PDSCH and the unicast SPS PDSCH.
[0297] Option B: If the terminal can receive all unicast SPS PDSCHs, the terminal may select all unicast SPS PDSCHs, and then select a group-common SPS PDSCH based on ascending order of SPS configuration indexes starting from the lowest SPS configuration index for the group-common SPS PDSCH. The terminal may not receive all unselected SPS PDSCHs.
[0298] If the terminal cannot receive all unicast SPS PDSCHs, the terminal may select a unicast SPS PDSCH based on ascending order of SPS configuration indexes starting from the lowest SPS configuration index for the unicast SPS PDSCH. The terminal may not receive all unselected SPS PDSCHs, including all group-common SPS PDSCHs.
[0299] Option C: The terminal may select a unicast SPS PDSCH with a higher priority based on ascending order of SPS configuration indexes starting from the lowest SPS configuration index for the unicast SPS PDSCH. Then, the terminal may select a group-common SPS PDSCH with a higher priority based on ascending order of SPS configuration indexes starting from the lowest SPS configuration index for the group-common SPS PDSCH. Then, the terminal may select a unicast SPS PDSCH with a lower priority based on ascending order of SPS configuration indexes starting from the lowest SPS configuration index for the unicast SPS PDSCH. Then, the terminal may select a group-common SPS PDSCH with a lower priority based on ascending order of SPS configuration indexes starting from the lowest SPS configuration index for the group-common SPS PDSCH. The terminal may not receive all unselected SPS PDSCHs.
[0300] The terminal may determine PUCCH resources only for HARQ-ACK for the selected SPS PDSCH, and may generate HARQ-ACK information bits only for HARQ-ACK for the selected SPS PDSCH.
[0301] For the above options, if the terminal selects the group common SPS PDSCH, the terminal may prioritize the multicast SPS PDSCH over the broadcast SPS PDSCH, regardless of the SPS configuration index for the multicast / broadcast SPS PDSCH.
[0302] 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.
[0303] 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.
[0304] 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.
[0305] 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.
[0306] 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.
[0307] Using the same PUCCH resource, the terminal can also transmit HARQ-ACK for other PDSCH transmissions, such as unicast. In this case, the PUCCH resource for multiplexing of unicast (i.e., terminal-specific data transmission) and / or multicast (i.e., group-common data transmission) can be determined as follows:
[0308] For multiplexing of NACK-only HARQ-ACK for multiple group-common SPS PDSCHs, when the PUCCH-config for multicast is set to NACK-only, the terminal can select a PUCCH resource based on the sps-PUCCH-AN-List of the PUCCH-config for multicast.
[0309] If the PUCCH-config for multicast is not configured, the PUCCH-config for unicast is used and the NACK-only HARQ-ACK may be converted to an ACK / NACK-based HARQ-ACK.
[0310] For multiplexing of NACK-only HARQ-ACK and SR (scheduling request) for multiple group-common SPS PDSCHs, the terminal can select PUCCH resources based on the sps-PUCCH-AN-List of the PUCCH-config for unicast, regardless of whether the PUCCH-config for multicast is set to NACK-only.
[0311] Alternatively, when the PUCCH-config for multicast is configured for ACK / NACK-based HARQ-ACK, the terminal may select a PUCCH resource based on the sps-PUCCH-AN-List of the PUCCH-config for multicast.
[0312] For multiplexing of NACK-only HARQ-ACK for multiple group-common SPS PDSCHs and HARQ-ACK (and SR, if present) for unicast SPS PDSCHs, the terminal can select PUCCH resources based on the sps-PUCCH-AN-List of the PUCCH-config for unicast, regardless of whether the PUCCH-config for multicast is set to NACK-only.
[0313] Alternatively, when the PUCCH-config for multicast is configured for ACK / NACK-based HARQ-ACK, the terminal may select a PUCCH resource based on the sps-PUCCH-AN-List of the PUCCH-config for multicast.
[0314] For multiplexing of NACK-only HARQ-ACK for group-common SPS PDSCH and ACK / NACK-based HARQ-ACK for group-common SPS PDSCH, the terminal may select a PUCCH resource based on the sps-PUCCH-AN-List in the PUCCH-config for multicast.
[0315] If the PUCCH-config for multicast is not configured, the terminal can select a PUCCH resource based on the sps-PUCCH-AN-List of the PUCCH-config for unicast.
[0316] For multiplexing of NACK-only HARQ-ACK for group-common SPS PDSCH and ACK / NACK-based HARQ-ACK and SR for group-common SPS PDSCH, the terminal may select a PUCCH resource based on the sps-PUCCH-AN-List in the PUCCH-config for unicast.
[0317] When a serving cell is deactivated and a CFR is configured for the serving cell, the terminal does not need to receive a multicast PDSCH on the serving cell.
[0318] Upon deactivation of a serving cell with CFR configured, the terminal shall determine the MARQ for the type 1 HARQ-ACK codebook by one of the following options: A,c A set of opportunities can be determined.
[0319] Option A: Regardless of whether the CFR is associated with the DL BWP provided by the firstActiveDownlinkBWP-Id parameter, it is assumed that the terminal is not configured to monitor the PDCCH for the multicast DCI format for the serving cell c, and M A,c A set of opportunities can be determined.
[0320] Option B: Assume that the terminal is configured to monitor the PDCCH for the multicast DCI format for the serving cell c when the CFR is associated with the DL BWP provided by the firstActiveDownlinkBWP-Id parameter, and A,c A set of opportunities can be determined.
[0321] Option B-1: If no CFR is associated with the DL BWP provided by the firstActiveDownlinkBWP-Id parameter, it is assumed that the terminal is not configured to monitor the PDCCH for the multicast DCI format for the serving cell c, and MA,c A set of opportunities can be determined.
[0322] Option B-2: If no CFR is associated with the DL BWP provided by the firstActiveDownlinkBWP-Id parameter, but a CFR is associated with the DL BWP of the serving cell, it is assumed that the terminal is configured to monitor the PDCCH for the multicast DCI format for the serving cell c, and uses the DL BWP to monitor the M for the candidate PDSCH reception. A,c A set of opportunities can be determined.
[0323] If there is more than one DL BWP associated with the CFR for the serving cell, the DL BWP may be indicated by the base station or selected based on the lowest (or highest) BWP index.
[0324] It is assumed that if there is no DL BWP associated with the CFR for the serving cell, the terminal is not configured to monitor the PDCCH for the multicast DCI format for the serving cell c, and M A,c A set of opportunities can be determined.
[0325] 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.
[0326] 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).
[0327] 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.
[0328] 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.
[0329] 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.
[0330] 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.
[0331] 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.
[0332] Apparatus to which the present disclosure can be applied
[0333] FIG. 11 illustrates a block diagram of a wireless communication device according to an embodiment of the present disclosure.
[0334] 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).
[0335] 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.
[0336] 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.
[0337] 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.
[0338] 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.
[0339] 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.
[0340] 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.
[0341] 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.
[0342] 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.
[0343] 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.
[0344] 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]
[0345] The method proposed in this disclosure has been described mainly as being applied to 3GPP LTE / LTE-A and 5G systems, but it can be applied to various wireless communication systems other than 3GPP LTE / LTE-A and 5G systems.
Claims
1. 1. A method for transmitting Hybrid Automatic Repeat Request (HARQ)-Acknowledgement (ACK) information by a terminal in a wireless communication system, the method comprising: generating N (N>1) HARQ-ACK information bits associated with a second HARQ-ACK reporting mode; and applying either a first scheme according to a first HARQ-ACK reporting mode in one physical uplink control channel (PUCCH) or a second scheme of selecting one PUCCH resource from a set of PUCCH resources based on values of the N HARQ-ACK information bits, and transmitting HARQ-ACK information to a network; A method, wherein either the first scheme or the second scheme is applied based on a setting by the network.
2. For the second scheme, the set of PUCCH resources is N The method of claim 1, further comprising: - 1 PUCCH resource candidate.
3. The method of claim 2 , wherein each of the PUCCH resource candidates corresponds to a different combination of values of the N HARQ-ACK information bits.
4. The method of claim 1, wherein the first scheme includes converting and multiplexing the N HARQ-ACK information bits of the second HARQ-ACK reporting mode into HARQ-ACK information bits of a first HARQ-ACK reporting mode.
5. The method of claim 4, wherein a PUCCH resource is determined based on a PUCCH resource indicator field included in a multicast downlink control information (DCI) format based on the HARQ-ACK information bits of the first HARQ-ACK reporting mode being provided for the N HARQ-ACK information bits of the second HARQ-ACK reporting mode by the first scheme.
6. The method of claim 5 , wherein the multicast DCI format is a last DCI format of one or more multicast DCI formats.
7. The method of claim 5, wherein the multicast DCI format is cyclic redundancy check (CRC) scrambled with a group-radio network temporary identifier (G-RNTI) or a configured scheduling (G-CS)-RNTI.
8. The method of claim 1 , wherein the N HARQ-ACK information bits are generated for at least one of one or more multicast DCI formats or one or more multicast Physical Downlink Shared Channels (PDSCHs) received from the network.
9. The method of claim 1 , wherein the second scheme is applied for N=k and the first scheme is applied for N>k according to a configuration of the base station.
10. The method of claim 1 , wherein k is 2, 3, or 4.
11. The method of claim 1, wherein the first HARQ-ACK reporting mode includes generating an ACK value or a non-acknowledgement (NACK) value as HARQ-ACK information based on success or failure of decoding of a transmission block.
12. The method of claim 1 , wherein the second HARQ-ACK reporting mode includes: HARQ-ACK information including only an ACK value is not transmitted; and HARQ-ACK information including a NACK value is transmitted.
13. A terminal for transmitting hybrid automatic repeat request (HARQ)-acknowledgement (ACK) information 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: generating N (N>1) HARQ-ACK information bits associated with a second HARQ-ACK reporting mode; A physical uplink control channel (PUCCH) is configured to apply either a first scheme according to a first HARQ-ACK reporting mode or a second scheme of selecting one PUCCH resource from a set of PUCCH resources based on values of the N HARQ-ACK information bits, and transmit HARQ-ACK information to a network via the one or more transceivers; A terminal, wherein either the first method or the second method is applied based on a setting by the network.
14. 1. A method for receiving Hybrid Automatic Repeat Request (HARQ)-Acknowledgement (ACK) information by a base station in a wireless communication system, the method comprising: transmitting at least one of one or more multicast DCI formats or one or more multicast Physical Downlink Shared Channels (PDSCHs) to a terminal; receiving HARQ-ACK information, to which either a first scheme according to a first HARQ-ACK reporting mode or a second scheme of selecting one PUCCH resource from a set of PUCCH resources based on values of the N HARQ-ACK information bits is applied, for N (N>1) HARQ-ACK information bits associated with a second HARQ-ACK reporting mode generated based on at least one of the one or more DCI formats or the one or more PDSCHs, from the terminal via one physical uplink control channel (PUCCH); A method, wherein either the first scheme or the second scheme is applied based on a setting by the base station.
15. 1. A base station for receiving hybrid automatic repeat request (HARQ)-acknowledgement (ACK) information in a wireless communication system, comprising: one or more transceivers; one or more processors coupled to the one or more transceivers; The one or more processors: Transmitting at least one of one or more multicast DCI formats or one or more multicast physical downlink shared channels (PDSCHs) to a terminal via one or more transceivers; The terminal is configured to receive HARQ-ACK information, to which either a first scheme according to a first HARQ-ACK reporting mode or a second scheme of selecting one PUCCH resource from a set of PUCCH resources based on values of the N HARQ-ACK information bits is applied, for N (N>1) HARQ-ACK information bits associated with a second HARQ-ACK reporting mode generated based on at least one of the one or more DCI formats or the one or more PDSCHs, from the terminal via one or more transceivers on one physical uplink control channel (PUCCH); A base station, wherein either the first scheme or the second scheme is applied based on a setting by the base station.
16. 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 operatively coupled to said one or more processors and storing instructions for performing the method of any one of claims 1 to 12 when executed by said one or more processors.
17. One or more non-transitory computer-readable media storing one or more instructions, A computer readable medium, wherein the one or more instructions, when executed by one or more processors, control an apparatus in a wireless communication system to perform the method of any one of claims 1 to 12.
Citation Information
Cited By
Response feedback method and device, terminal, and readable storage medium
JP2025506174A
Response feedback method and device, terminal, and readable storage medium
JP7823210B2
