Method, apparatus, and system for assigning HARQ process numbers for downlink and uplink transmission in wireless communication systems.

Abstract

A method for a terminal to transmit a physical uplink shared channel (PUSCH) to a base station in a wireless communication system is disclosed. The terminal can receive Radio Resource Control (RRC) configuration information related to a slot configuration from the base station and can receive a physical downlink control channel (PDCCH) including downlink control information (DCI) for scheduling multiple physical uplink shared channels (PUSCHs) for the terminal from the base station.

Description

[Technical Field]

[0001] The present invention relates to a wireless communication system. Specifically, the present invention relates to a method, apparatus, and system for determining and transmitting resources for downlink shared channels and uplink shared channels. [Background technology]

[0002] Since the commercialization of 4G (4th generation) communication systems, efforts have been made to develop new 5G (5th generation) communication systems to meet the increasing demand for wireless data traffic. 5G communication systems are also called beyond 4G network systems, post-LTE systems, or NR (new radio) systems. To achieve high data transmission rates, 5G communication systems are expected to be implemented at base stations and terminals, including systems operating in ultra-high frequency (mmWave) bands above 6 GHz, and also including communication systems operating in frequency bands below 6 GHz to ensure coverage.

[0003] 3GPP® (3rd Generation Partnership Project) NR systems improve the spectral efficiency of networks, enabling telecommunications carriers to provide more data and voice services within a given bandwidth. Therefore, 3GPP NR systems are designed to meet the demands for high-speed data and media transmission, in addition to high-capacity voice support. The advantages of NR systems include high processing power, low latency, support for FDD (frequency division duplex) and TDD (time division duplex), an improved end-user environment, and low operating costs due to a simple architecture, all on the same platform.

[0004] For more efficient data processing, the NR system's dynamic TDD can use a method that varies the number of OFDM (orthogonal frequency division multiplexing) symbols available for uplink and downlink according to the direction of user data traffic in the cell. For example, when downlink traffic in a cell is greater than uplink traffic, the base station can allocate more downlink OFDM symbols to slots (or subframes). Information regarding the slot configuration needs to be transmitted to the terminal.

[0005] To mitigate path loss in the ultra-high frequency band and increase the transmission distance of radio waves, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, hybrid beamforming (combining analog and digital beamforming), and large-scale antenna technologies are being discussed for 5G communication systems. Furthermore, in order to improve the system network, 5G communication systems are undergoing technological development in areas such as advanced small cells, improved small cells, cloud radio access networks (cloud RAN), ultra-dense networks, device-to-device communication (D2D), vehicle-to-everything communication (V2X), wireless backhaul, non-terrestrial network communication (NTN), moving networks, cooperative communication, CoMP (coordinated multi-points), and interference cancellation.In addition, 5G systems have seen the development of advanced coding modulation (ACM) methods such as FQAM (hybrid FSK and QAM modulation) and SWSC (sliding window superposition coding), as well as advanced connectivity technologies such as FBMC (filter bank multi-carrier), NOMA (non-orthogonal multiple access), and SCMA (sparse code multiple access).

[0006] Meanwhile, the internet is evolving from a human-centered network where humans generate and consume information to an IoT (Internet of Things) network where distributed components such as objects exchange and process information. IoE (Internet of Everything) technology, which combines IoT technology with big data processing technologies using connections with cloud servers, is also emerging. To realize IoT, technological elements such as sensing technology, wired and wireless communication and network infrastructure, service interface technology, and security technology are required. Recently, technologies such as sensor networks for connecting things, machine-to-machine (M2M) communication, and MTC (machine-type communication) are being researched. In an IoT environment, intelligent IT (internet technology) services can be provided that collect and analyze data generated from connected things to create new value in people's lives. IoT, through the integration and combination of existing IT (information technology) technologies and various industries, can be applied to fields such as smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart home appliances, and advanced medical services.

[0007] Therefore, various attempts are being made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine-to-machine (M2M) communication, and machine-type communication (MTC) are being realized through 5G communication technologies such as beamforming, MIMO, and array antennas. The application of cloud radio access networks (cloud RAN) as a big data processing technology, as mentioned earlier, can also be considered an example of the fusion of 5G technology and IoT technology. In general, mobile communication systems were developed to provide voice services while ensuring user activity.

[0008] However, mobile communication systems have gradually expanded their scope beyond voice to include data services, and have now developed to the point where they can provide high-speed data services. Nevertheless, due to resource shortages and user demand for high-speed services, there is a need for more advanced mobile communication systems. [Overview of the project] [Problems that the invention aims to solve]

[0009] The object of the present invention is to provide a method and apparatus for determining resources for downlink sharing channels and uplink sharing channels and assigning HARQ process numbers in a wireless communication system, particularly a cellular wireless communication system. [Means for solving the problem]

[0010] A terminal in a wireless communication system that transmits a physical uplink shared channel (PUSCH) includes a communication module and a processor that controls the communication module, wherein the processor receives RRC (Radio Resource Control) configuration information relating to the configuration of a slot from a base station, and receives a physical downlink control channel (PDCCH) from the base station that includes downlink control information (DCI) scheduling multiple physical uplink shared channels (PUSCH) for the terminal, the DCI indicating the HARQ (Hybrid Automatic Repeat Request) process number of the first PUSCH among the multiple PUSCHs, and the HARQ process number of the PUSCH constituting the multiple PUSCHs is increased from the HARQ process number of the PUSCH for a previous PUSCH depending on whether the symbol of the slot in which the PUSCH is scheduled overlaps with a symbol indicated as downlink or flexible by the RRC configuration information.

[0011] Furthermore, in the present invention, if the symbol of the slot in which the PUSCH is scheduled is indicated as an uplink symbol by the RRC configuration information, the HARQ process number for the PUSCH is increased by "1" from the HARQ process number for the previous PUSCH.

[0012] Furthermore, in the present invention, if the symbol of the slot in which the PUSCH is scheduled overlaps with the downlink symbol indicated by the RRC configuration information, the PUSCH is not transmitted in the slot.

[0013] Furthermore, in the present invention, the HARQ process number for the PUSCH does not increase compared to the previous HARQ process number for the PUSCH.

[0014] Furthermore, in the present invention, if the symbol of the slot in which the next PUSCH following the PUSCH is scheduled is indicated as an uplink symbol by the RRC configuration information, the HARQ process number for the next PUSCH is increased by "1" compared to the HARQ process number for the previous PUSCH.

[0015] Furthermore, in the present invention, if the symbol of the slot in which the PUSCH is scheduled overlaps with a flexible symbol indicated by the RRC configuration information, the HARQ process number for the PUSCH is increased by "1" from the previous HARQ process number for the PUSCH, depending on whether or not a specific signal is configured by the flexible symbol.

[0016] Furthermore, in the present invention, the specific signal is an SSB (Synchronization Signal / PBCH block) indicated by the upper-layer parameter SSBpositioninburst of the RRC configuration information.

[0017] Furthermore, in the present invention, if the specific signal is not configured with the flexible symbol, the HARQ process number for the PUSCH is increased by "1" compared to the previous HARQ process number for the PUSCH.

[0018] Furthermore, in the present invention, the HARQ process number for the PUSCH is increased by "1" from the previous HARQ process number for the PUSCH, regardless of whether the symbol of the slot on which the PUSCH is scheduled is indicated as an uplink, downlink, or flexible by the slot format indicator (SFI).

[0019] Furthermore, in the present invention, the symbol of the slot to which the first PUSCH is transmitted does not overlap with the symbol designated as a downlink by the RRC configuration information.

[0020] Furthermore, the present invention relates to a terminal in a wireless communication system that receives a physical downlink shared channel (PUSCH), wherein the terminal includes a communication module and a processor, the processor receiving RRC (Radio Resource Control) configuration information relating to the configuration of a slot from a base station, and receiving a Physical Downlink Control Channel (PDCCH) from the base station that includes Downlink Control information (DCI) scheduling multiple Physical Downlink Shared Channels (PUSCH) for the terminal, the DCI indicating the HARQ (Hybrid Automatic Repeat Request) process number of the first PDSCH among the multiple PDSCHs, the HARQ process number of the PDSCH constituting the multiple PDSCH is increased from the HARQ process number of the PDSCH for a previous PDSCH depending on whether the symbol of the slot on which the PDSCH is scheduled overlaps with a symbol indicated as uplink or flexible by the RRC configuration information.

[0021] Furthermore, in the present invention, if the symbol of the slot in which the PDSCH is scheduled is instructed to be a downlink symbol by the RRC configuration information, the HARQ process number for the PDSCH is increased by "1" from the HARQ process number for the previous PDSCH.

[0022] Furthermore, in the present invention, if the symbol of the slot on which the PDSCH is scheduled overlaps with the uplink symbol indicated by the RRC configuration information, the PDSCH is not received in the slot.

[0023] Furthermore, in the present invention, the HARQ process number for the PDSCH does not increase compared to the previous HARQ process number for the PDSCH.

[0024] Furthermore, in the present invention, if the symbol of the slot in which the next PDSCH following the PDSCH is scheduled is indicated as a downlink symbol by the RRC configuration information, the HARQ process number for the next PDSCH is increased by "1" compared to the HARQ process number for the previous PDSCH.

[0025] Furthermore, in the present invention, if the symbol of the slot in which the PDSCH is scheduled overlaps with a flexible symbol indicated by the RRC configuration information, the HARQ process number for the PDSCH increases by "1" compared to the HARQ process number for the previous PDSCH.

[0026] Furthermore, in the present invention, the HARQ process number for the PDSCH is increased by "1" from the previous HARQ process number for the PDSCH, regardless of whether the symbol of the slot on which the PDSCH is scheduled is indicated as uplink, downlink, or flexible by the slot format indicator (SFI).

[0027] Furthermore, in the present invention, the symbol of the slot to which the first PDSCH is transmitted does not overlap with the symbol designated as the uplink by the RRC configuration information.

[0028] Furthermore, the present invention includes the steps of receiving RRC (Radio Resource Control) configuration information relating to the configuration of a slot from a base station, and receiving a Physical Downlink Control Channel (PDCCH) from the base station that includes Downlink Control information (DCI) for scheduling multiple PUSCHs to the terminal, wherein the DCI indicates the HARQ (Hybrid Automatic Repeat Request) process number of the first PUSCH among the multiple PUSCHs, and the HARQ process number of the PUSCH constituting the multiple PUSCH is increased from the HARQ process number of the PUSCH for a previous PUSCH depending on whether the symbol of the slot on which the PUSCH is scheduled overlaps with a symbol indicated as downlink or flexible by the RRC configuration information. [Effects of the Invention]

[0029] According to an embodiment of the present invention, the terminal can efficiently determine the resources for data and control information to be transmitted via the uplink sharing channel and efficiently transmit the data and uplink control information to the base station via the uplink sharing channel.

[0030] Furthermore, according to embodiments of the present invention, the terminal can efficiently determine the resources for data and control information to be received via the downlink sharing channel and efficiently receive the downlink sharing channel from the base station.

[0031] Furthermore, the present invention allows for the efficient setting of HARQ process numbers when multiple PUSCH or multiple PDSCH processes are scheduled.

[0032] Furthermore, the present invention has the effect of eliminating ambiguity between the terminal and the base station due to the presence or absence of SFI detection on the terminal, by increasing the HARQ process number regardless of PDSCH reception if the symbol of the slot on which the multiple PDSCH is scheduled overlaps with a symbol indicated as flexible by the RRC configuration information when multiple PDSCHs are scheduled.

[0033] Furthermore, the present invention has the effect of eliminating ambiguity between the terminal and the base station due to the presence or absence of SFI detection on the terminal, by considering only whether or not a specific signal (for example, SSB (Synchronization Signal / PBCH block) reception is set) is configured for that symbol when multiple PUSCH is scheduled, if the symbol of the slot in which multiple PUSCH is scheduled overlaps with a symbol that is indicated as flexible by the RRC configuration information, regardless of whether or not PUSCH is transmitted.

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

[0035] [Figure 1] This figure shows an example of a wireless frame structure used in wireless communication systems. [Figure 2] This figure shows an example of a downlink (DL) / uplink (UL) slot structure in a wireless communication system. [Figure 3] This diagram illustrates the physical channels used in 3GPP systems (e.g., NR) and a common signal transmission method utilizing those physical channels. [Figure 4] This figure shows the SS / PBCH block for initial cell access in a 3GPP NR system. [Figure 5]This diagram shows the procedure for transmitting control information and control channels in a 3GPP NR system. [Figure 6] This diagram shows the CORESET to which PDCCH is transmitted in a 3GPP NR system. [Figure 7] This diagram shows how to configure the PDCCH search space in a 3GPP NR system. [Figure 8] Figure 8 is a conceptual diagram illustrating career integration. [Figure 9] This diagram illustrates terminal carrier communication and multi-carrier communication. [Figure 10] This figure shows an example where the cross-carrier scheduling technique is applied. [Figure 11] This is a block diagram showing the configuration of a terminal and a base station according to one embodiment of the present invention. [Figure 12] This figure shows the scheduling of a Physical Downlink Shared Channel (PDSCH) according to one embodiment of the present invention. [Figure 13] This figure shows the scheduling of a Physical Uplink Control Channel (PUCCH) according to one embodiment of the present invention. [Figure 14] This figure shows the scheduling of a physical uplink sharing channel and a physical uplink control channel according to one embodiment of the present invention. [Figure 15] This figure shows scheduling of a downlink shared channel by multiple slot scheduling according to one embodiment of the present invention. [Figure 16] This figure shows an example of uplink control channel transmission in one slot using multiple slot scheduling according to one embodiment of the present invention. [Figure 17] This figure shows the transmission of an uplink control channel in two or more slots by multiple slot scheduling according to one embodiment of the present invention. [Figure 18]This figure shows a candidate for a downlink shared channel corresponding to HARQ-ACK when an uplink control channel is transmitted in the nth slot according to one embodiment of the present invention. [Figure 19] This is a diagram showing HARQ-ACKoka according to one embodiment of the present invention. [Figure 20] This figure shows a time domain bundling window according to one embodiment of the present invention. [Figure 21] This figure shows a representative PDSCH with a time-domain bundling window according to one embodiment of the present invention. [Figure 22] This figure shows the HARQ-ACK occasion according to a time-domain bundling window in one embodiment of the present invention. [Figure 23] This flowchart shows an example of the operation of a terminal according to an embodiment of the present invention. [Modes for carrying out the invention]

[0036] The terms used herein have been selected to be as widely used and general as possible, taking into account the function of the present invention; however, this may vary depending on the intent, conventions, or emergence of new technologies of the articulate. In some cases, the applicant has arbitrarily selected terms, in which case their meaning will be described in the relevant section of the invention description. Therefore, it should be made clear that the terms used herein are not merely names of terms, but should be interpreted based on their substantive meaning and the overall content of this specification.

[0037] Throughout the specification, when one configuration is said to be “connected” to another, this includes not only cases where they are “directly connected,” but also cases where they are “electrically connected” through other intermediate components. Furthermore, when a configuration is said to “include” a particular component, this means, unless otherwise stated, that it includes other components rather than excluding them. In addition, the limitations of “greater than” or “less than” a particular critical point may be appropriately replaced by “greater than” or “less than” depending on the embodiment.

[0038] The following technologies are used in a variety of wireless connectivity systems, including CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access). CDMA is implemented using radio technology such as UTRA (Universal Terrestrial Radio Access) and CDMA2000. TDMA is implemented using radio technology such as GSM (Global System for Mobile communications) / GPRS (General Packet Radio Service) / EDGE (Enhanced Data Rates for GSM Evolution). OFDMA is implemented using radio technology such as IEEE802.11 (Wi-Fi), IEEE802.16 (WiMAX), IEEE802-20, and E-UTRA (Evolved UTRA). UTRA is part of UMTS (Universal Mobile Telecommunication System). 3GPP LTE (Long term evolution) is part of E-UMTS (Evolved UMTS) which uses E-UTRA, and LTE-A (Advanced) is an advanced version of 3GPP LTE. 3GPP NR is a system designed separately from LTE / LTE-A, and is intended to support eMBB (enhanced Mobile Broadband), URLLC (Ultra-Reliable and Low Latency Communication), and mMTC (massive Machine Type Communication) services, which are requirements of IMT-2020. While this explanation will focus on 3GPP NR for clarity, the technical concept of this invention is not limited to this.

[0039] Unless otherwise specified herein, a base station may include a gNB (next generation node B) as defined in 3GPP NR. Also, unless otherwise specified, a terminal may include a UE (user equipment). To aid understanding the explanation below, each concept will be described in separate embodiments, although these embodiments may be used in combination with each other. In this disclosure, terminal configuration may mean configuration by the base station. Specifically, the base station may transmit channels or signals to the terminal to configure the operation of the terminal or the values ​​of parameters used in the wireless communication system.

[0040] Figure 1 shows an example of a wireless frame structure used in a wireless communication system.

[0041] Referring to Figure 1, a radio frame (or radio frame) used in a 3GPP NR system has a length of 10 ms (ΔfmaxNf / 100) * Tc). A radio frame consists of 10 subframes (SF) of equal size, where Δfmax = 480 * 10³ Hz, Nf = 4096, Tc = 1 / (Δfref * Nf,ref), Δfref = 15 * 10³ Hz, and Nf,ref = 2048. Each of the 10 subframes within a single frame is assigned a number from 0 to 9. Each subframe has a length of 1 ms and consists of one or more slots determined by the subcarrier spacing. More specifically, the subcarrier spacing usable in a 3GPP NR system is 15 * 2 μkHz, where μ is the subcarrier spacing configuration, with values ​​from 0 to 4. In other words, 15kHz, 30kHz, 60kHz, 120kHz, or 240kHz are used as subcarrier intervals. A 1ms subframe consists of 2μm slots, each with a length of 2-μms. The 2μm slots within a subframe are each assigned numbers from 0 to 2μ-1. Similarly, the slots within a radio frame are each assigned numbers from 0 to 10*2μ-1. Time resources are divided by at least one of the following: radio frame number (also called radio frame index), subframe number (also called subframe index), or slot number (or slot index).

[0042] Figure 2 shows an example of a downlink (DL) / uplink (UL) slot structure in a wireless communication system. In particular, Figure 2 shows the resource grid structure of a 3GPP NR system.

[0043] There is one resource grid per antenna port. Referring to Figure 2, a slot contains multiple OFDM symbols in the time domain and multiple resource blocks (RBs) in the frequency domain. An OFDM symbol also means a single symbol interval. Unless otherwise specified, OFDM symbols are simply referred to as symbols. Hereafter, in this specification, symbols include OFDM symbols, SC-FDMA symbols, DFTs-OFDM symbols, etc. Referring to Figure 2, the signal transmitted from each slot is represented by a resource grid consisting of Nsize, μgrid, x*NRBSC subcarriers and Nslotsymb OFDM symbols. Here, x=DL for a downlink resource grid and x=UL for an uplink resource grid. Nsize, μgrid, and x indicate the number of resource blocks (RBs) with a subcarrier spacing component μ (x is DL or UL), and Nslotsymb indicates the number of OFDM symbols in the slot. NRBSC is the number of subcarriers constituting one RB, where NRBSC=12. OFDM symbols are also known as CP-OFDM (cyclic prefix OFDM) symbols or DFT-S-OFDM (discrete Fourier transform spread OFDM) symbols, depending on the multiple access method.

[0044] The number of OFDM symbols in a single slot can vary depending on the length of the cyclic prefix (CP). For example, a normal CP may contain 14 OFDM symbols in a single slot, while an extended CP may contain 12 OFDM symbols. In specific embodiments, extended CPs are used only with a subcarrier interval of 60 kHz. Figure 2 illustrates a case where a single slot consists of 14 OFDM symbols for ease of explanation, but embodiments of the present invention can be applied in the same manner to slots with other numbers of OFDM symbols. Referring to Figure 2, each OFDM symbol contains N size, μgrid, and x*NRBSC subcarriers in the frequency domain. Subcarrier types are divided into data subcarriers for transmitting data, reference signal subcarriers for transmitting reference signals, and guard bands. The carrier frequency is also called the center frequency (fc).

[0045] A single RB is defined by NRBSC (e.g., 12) consecutive subcarriers in the frequency domain. Incidentally, a resource consisting of one OFDM symbol and one subcarrier is called a resource element (RE) or tone. Therefore, a single RB consists of Nslotsymb*NRBSC resource elements. Each resource element in the resource grid is uniquely defined by an index pair (k, l) in a single slot. k is an index given in the frequency domain from 0 to Nsize, μgrid, and x*NRBSC-1, and l is an index given in the time domain from 0 to Nslotsymb-1.

[0046] For a terminal to receive signals from a base station or transmit base station signals, the terminal's time / frequency synchronization must be synchronized with the base station's time / frequency synchronization. If the base station and the terminal are not synchronized, the terminal cannot determine the time and frequency parameters necessary to demodulate DL signals and transmit UL signals at the correct time.

[0047] Each symbol in a radio frame operating in TDD (time division duplex) or unpaired spectrum consists of at least one of the following: a downlink symbol (DL symbol), an uplink symbol (UL symbol), or a flexible symbol. In FDD (frequency division duplex) or paired spectrum, a radio frame operating on a downlink carrier consists of either a downlink symbol or a flexible symbol, while a radio frame operating on an uplink carrier consists of either an uplink symbol or a flexible symbol. Downlink symbols can be used for downlink transmission but not uplink transmission, and uplink symbols can be used for uplink transmission but not downlink transmission. The use of a flexible symbol in the downlink or uplink is determined by the signal.

[0048] Information regarding the type of each symbol, i.e., whether it is a downlink symbol, uplink symbol, or flexible symbol, consists of a cell-specific (or common) RRC signal. Additionally, information regarding the type of each symbol consists of a UE-specific (or dedicated) RRC signal. The base station uses the cell-specific RRC signal to indicate: i) the period of the cell-specific slot configuration; ii) the number of slots containing only downlink symbols from the beginning of the cell-specific slot configuration period; iii) the number of downlink symbols from the first symbol in the slot immediately following the downlink-only slot; iv) the number of slots containing only uplink symbols from the end of the cell-specific slot configuration period; and v) the number of uplink symbols from the last symbol in the slot immediately preceding the uplink-only slot. Here, a symbol that is neither an uplink nor a downlink symbol is a flexible symbol.

[0049] If the information regarding the symbol type consists of the UE-specific RRC signal, the base station signals whether the flexible symbol is a downlink symbol or an uplink symbol by means of the cell-specific RRC signal. At this time, the UE-specific RRC signal cannot change a downlink symbol or an uplink symbol which consists of the cell-specific RRC signal into another symbol type. The specific UE RRC signal signals, for each slot, the number of downlink symbols among the Nslotsymb symbols of the slot and the number of uplink symbols among the Nslotsymb symbols of the slot. At this time, the downlink symbols of the slot are continuously configured from the first symbol to the i-th symbol of the slot. Also, the uplink symbols of the slot are continuously configured from the j-th symbol to the last symbol of the slot (where i < j). In a slot, a symbol that is not configured as either an uplink symbol or a downlink symbol is a flexible symbol.

[0050] The type of symbol configured by the RRC signal as described above can be called a semi-static DL / UL configuration. In the semi-static DL / UL configuration configured by the RRC signal previously, the flexible symbol may be indicated as a downlink symbol, an uplink symbol, or a flexible symbol by the dynamic SFI (slot format information) transmitted on the physical downlink control channel (PDCCH). At this time, a downlink symbol or an uplink symbol configured by the RRC signal is not changed into another symbol type. Table 1 exemplifies the dynamic SFI that the base station can indicate to the UE.

[0051]

Table 1

[0052] In Table 1, D represents the downlink symbol, U represents the uplink symbol, and X represents the flexible symbol. As shown in Table 1, a maximum of two DL / UL switching operations may be permitted in one slot.

[0053] Figure 3 illustrates the physical channels used in 3GPP systems (e.g., NR) and a typical signal transmission method utilizing those physical channels.

[0054] When the terminal is powered on or enters a new cell, the terminal performs an initial cell discovery operation (S101). Specifically, the terminal synchronizes with the base station during the initial cell discovery. To do this, the terminal receives a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) from the base station to synchronize with the base station and obtain information such as the cell ID. Next, the terminal receives the physical broadcast channel from the base station and obtains broadcast information within the cell.

[0055] A terminal that has completed the initial cell search receives a physical downlink shared channel (PDSCH) via the physical downlink control channel (PDCCH) and the information carried on the PDCCH, thereby obtaining more detailed system information than the system information obtained through the initial cell search (S102). Here, the system information transmitted to the terminal is cell common system information that enables the terminal to operate correctly in the physical layer of the RRC (Radio Resource Control, RRC), and is called remaining system information or system information block (SIB) 1.

[0056] When a terminal first connects to a base station or when there are no radio resources for signal transmission (when the terminal is in RRC_IDLE mode), the terminal can perform a random access process to the base station (steps S103 to S106). First, the terminal transmits a preamble via a physical random access channel (PRACH) (S103), and can receive a Random Access Response (RAR) message for the preamble from the base station via the PDCCH and the corresponding PDSCH (S104). At this time, the preamble in steps S103 and S104 may be described as message 1 (Msg1), and the random access response may be described as a response message or message 2 (Msg2). If the terminal receives a valid random access response, the terminal transmits data including its identifier to the base station via the physical uplink shared channel (PUSCH) indicated by the uplink grant transmitted from the base station via the PDCCH or PDSCH (S105). At this time, the data including its own identifier and the PUSCH containing the data in step S105 may be described as message 3 (Msg3). The PUSCH containing the data may also be described as message 3 PUSCH (Msg3 PUSCH). Next, the terminal waits to receive a PDCCH as an instruction from the base station for collision resolution. When the terminal successfully receives a PDCCH using its own identifier and receives the corresponding PDSCH (S106), the random access process ends. At this time, the PDCCH and PDSCH in step S106 may be described as message 4 (Msg4). During the random access process, the terminal can obtain terminal identification system information from the RRC layer that is necessary for the terminal to operate correctly at the physical layer. Once the terminal obtains terminal identification system information from the RRC layer, the terminal enters RRC_CONNECTED mode.

[0057] The RRC layer is used for message generation and management for control between terminals and the Radio Access Network (RAN). Furthermore, base stations and terminals can use the RRC layer to broadcast cell system information necessary for all terminals within a cell, manage the transmission of paging messages, manage mobility and handover, report and control terminal measurements, and manage terminal capabilities and storage. Generally, the update of signals transmitted in the RRC layer (hereinafter referred to as RRC signals) is longer than the transmission time interval (TTI) in the physical layer, so RRC settings can be maintained without change over long periods.

[0058] After the above procedure, the terminal receives PDCCH / PDSCH S107 and transmits the physical uplink sharing channel (PUSCH) / physical uplink control channel (PUCCH) S108 as a general uplink / downlink signal transmission procedure. In particular, the terminal receives downlink control information (DCI) via PDCCH. DCI includes control information such as resource allocation information for the terminal. Also, the format of DCI may differ depending on its intended use. Uplink control information (UCI) that the terminal transmits to the base station via the uplink includes downlink / uplink ACK / NACK signals, CQI (channel quality indicator), PMI (precoding matrix index), RI (rank indicator), etc. Here, CQI, PMI, and RI are included in CSI (channel state information). In the case of a 3GPP NR system, the terminal transmits the above-mentioned HARQ-ACK and control information such as CSI via PUSCH and / or PUCCH.

[0059] Figure 4 shows the SS / PBCH block for initial cell access in a 3GPP NR system.

[0060] When a terminal is powered on or attempts to access a new cell, it acquires time and frequency synchronization with the cell and performs an initial cell discovery process. During the cell discovery process, the terminal detects the cell's physical cell identity (NcellID). To do this, the terminal receives synchronization signals from the base station, such as the primary synchronization signal (PSS) and secondary synchronization signal (SSS), to synchronize with the base station. At this time, the terminal obtains information such as the cell identifier (identity, ID).

[0061] Refer to Figure 4(a) for a more detailed explanation of the synchronization signal (SS). The synchronization signal is divided into PSS and SSS. PSS is used to obtain time-domain synchronization and / or frequency-domain synchronization, such as OFDM symbol synchronization and slot synchronization. SSS is used to obtain frame synchronization and cell group ID. Referring to Figure 4(a) and Table 2, an SS / PBCH block consists of 20 RBs (=240 subcarriers) consecutively on the frequency axis and 4 OFDM symbols consecutively on the time axis. In this case, within the SS / PBCH block, the PSS is transmitted via the first OFDM symbol and the SSS via the second subcarrier (56-18) for the third OFDM symbol. Here, the lowest subcarrier index of the SS / PBCH block is assigned starting from 0. In the first OFDM symbol on which the PSS is transmitted, the base station does not transmit signals via the remaining subcarriers, i.e., subcarriers 0-55 and 183-239. Furthermore, in the third OFDM symbol on which SSS is transmitted, the base station does not transmit signals via subcarriers 48-55 and 183-19. In the SS / PBCH block, the base station transmits PBCH (physical broadcast channel) via the remaining REs excluding the aforementioned signals.

[0062] [Table 2]

[0063] The SS generates a total of 1008 unique physical layer cell IDs through combinations of three PSSs and SSSs. More specifically, each physical layer cell ID is part of only one physical layer cell identifier group, and each group is grouped into 336 physical layer cell identifier groups, each containing three unique identifiers. Therefore, the physical layer cell ID NcellID = 3N(1)ID + N(2)ID is uniquely defined by an index N(1)ID ranging from 0 to 335 that represents a physical layer cell identifier group, and an index N(2)ID ranging from 0 to 2 that represents a physical layer identifier within the physical layer cell identifier group. The terminal detects the PSS and identifies one of the three unique physical layer identifiers. The terminal also detects the SSS and identifies one of the 336 physical layer cell IDs associated with the physical layer identifier. In this case, the PSS sequence dPSS(n) is as shown in Equation 1 below.

[0064]

number

[0065] Here,

number

[0066]

number

[0067] Also, the sequence d of SSS SSS (n) is as follows:

[0068]

number

[0069] Here,

number

[0070]

number

[0071] A 10ms long wireless frame is divided into two 5ms long half-frames. Refer to Figure 4(b) to describe the slot in which an SS / PBCH block is transmitted within each half-frame. The slot in which an SS / PBCH block is transmitted is one of cases A, B, C, D, or E. In case A, the subcarrier interval is 15kHz, and the start of the SS / PBCH block is at the {2, 8} + 14*n symbol. In this case, n=0, 1 for carrier frequencies below 3GHz. Also, n=0, 1, 2, 3 for carrier frequencies above 3GHz and below 6GHz. In case B, the subcarrier interval is 30kHz, and the start of the SS / PBCH block is at the {4, 8, 16, 20} + 28*n symbol. In this case, n=0 for carrier frequencies below 3GHz. Also, n=0, 1 for carrier frequencies above 3GHz and below 6GHz. In Case C, the subcarrier spacing is 30 kHz, and the SS / PBCH block starts at the {2nd, 8th} + 14*nth symbol. In this case, for carrier frequencies below 3 GHz, n=0, 1. Also, for carrier frequencies above 3 GHz and below 6 GHz, n=0, 1, 2, 3. In Case D, the subcarrier spacing is 120 kHz, and the SS / PBCH block starts at the {4th, 8th, 16th, 20th} + 28*nth symbol. In this case, for carrier frequencies above 6 GHz, n=0, 1, 2, 3, 5, 6, 7, 8, 10, 11, 12, 13, 15, 16, 17, 18. In Case E, the subcarrier spacing is 240 kHz, and the SS / PBCH block starts at the {8th, 12th, 16th, 20th, 32nd, 36th, 40th, 44th} + 56*nth symbol. In this case, at carrier frequencies of 6 GHz or higher, n = 0, 1, 2, 3, 5, 6, 7, 8.

[0072] Figures 5a and 5b illustrate the procedures for transmitting control information and control channels in a 3GPP NR system. Referring to Figure 5(a), the base station adds a CRC (cyclic redundancy check) masked (e.g., by XOR operation) with an RNTI (radio network temporary identifier) ​​to the control information (e.g., DCI) in S202. The base station scrambles the CRC with an RNTI value determined according to the purpose / target of each piece of control information. A common RNTI used by one or more terminals includes at least one of the following: SI-RNTI (system information RNTI), P-RNTI (paging RNTI), RA-RNTI (random access RNTI), and TPC-RNTI (transmit power control RNTI). Furthermore, the terminal-specific RNTI includes at least one of the following: C-RNTI (cell temporary RNTI), CS-RNTI, or MCS-C-RNTI. Next, after the base station performs channel encoding (e.g., polar coding) in S204, it performs rate-matching in S206 to match the amount of resources used for PDCCH transmission. Next, the base station multiplexes the DCIs (data elements) based on the CCE (control channel element)-based PDCCH structure in S208. The base station also applies additional processes S210 to the multiplexed DCIs (data elements), such as scrambling, modulation (e.g., QPSK), and interleaving, before mapping them to the resources to be transmitted. A CCE is the basic resource unit for PDCCH, and one CCE consists of multiple (e.g., 6) REGs (resource element groups). One REG consists of multiple (e.g., 12) REs. The number of CCEs used for one PDCCH is defined as the aggregation level. The 3GPP NR system uses 1, 2, 4, 8, or 16 integrated levels.Figure 5(b) is a diagram relating to the CCE integration level and PDCCH multiplexing, showing the types of CCE integration levels used for a single PDCCH and the CCEs transmitted in the control domain as a result.

[0073] Figure 6 shows the CORESET (control resource set) to which the PDCCH (physical downlink control channel) is transmitted in a 3GPP NR system.

[0074] A CORESET is a time-frequency resource on which PDCCH, a control signal for a terminal, is transmitted. Furthermore, the search space, described later, is mapped to a single CORESET. Therefore, instead of monitoring the entire frequency band to receive PDCCH, the terminal monitors the CORESET and the designated time-frequency domain to decode the PDCCH mapped to the CORESET. A base station configures one or more CORESETs for each cell in the terminal. A CORESET consists of up to three consecutive symbols on the time axis. A CORESET also consists of six consecutive PRB units on the frequency axis. In the embodiment shown in Figure 5, CORESET#1 consists of consecutive PRBs, while CORESET#2 and CORESET#3 consist of discontinuous PRBs. A CORESET can be located at any symbol within a slot. For example, in the embodiment shown in Figure 5, CORESET#1 starts at the first symbol in the slot, CORESET#2 starts at the fifth symbol in the slot, and CORESET#9 starts at the ninth symbol in the slot.

[0075] Figure 7 shows how to configure the PDCCH search space in a 3GPP NR system.

[0076] To transmit a PDCCH to a terminal, each CORESET has at least one search space. In embodiments of the present invention, the search space is a collection of all time-frequency resources (hereinafter referred to as PDCCH candidates) from which a terminal's PDCCH is transmitted. The search space includes a common search space that all 3GPP NR terminals should search in common, and a terminal-specific or UE-specific search space that a specific terminal should search. In the common search space, all terminals in a cell belonging to the same base station monitor PDCCHs that are set to be searched in common. The terminal-specific search spaces are set up individually for each terminal to monitor the PDCCH assigned to each terminal at different locations in the search space depending on the terminal. In the case of terminal-specific search spaces, the search spaces between terminals may partially overlap due to the limited control area to which PDCCHs are assigned. Monitoring a PDCCH includes blind decoding of PDCCH candidates in the search space. If blind decoding is successful, it is expressed as the PDCCH being (successfully) detected / received. If blind decoding fails, it is expressed as the PDCCH not being detected / received, or not being successfully detected / received.

[0077] For the sake of explanation, a PDCCH scrambled with a group common (GC) RNTI already known by one or more terminals, in order to transmit downlink control information to one or more terminals, is referred to as a group common (GC) PDCCH or common PDCCH. Furthermore, a PDCCH scrambled with a terminal-specific RNTI already known by a specific terminal, in order to transmit uplink scheduling information or downlink scheduling information to a specific terminal, is referred to as a terminal-specific PDCCH. The common PDCCH is included in the common search space, and the terminal-specific PDCCH is included in either the common search space or the terminal-specific PDCCH.

[0078] The base station informs each terminal or group of terminals via the PDCCH about resource allocation information for the transmission channels PCH (paging channel) and DL-SCH (downlink-shared channel) (i.e., DL Grant), or information about UL-SCH resource allocation and HARQ (hybrid automatic repeat request) (i.e., UL Grant). The base station transmits PCH transmission blocks and DL-SCH transmission blocks via the PDSCH. The base station transmits data excluding specific control information or specific service data via the PDSCH. The terminal also receives data excluding specific control information or specific service data via the PDSCH.

[0079] The base station transmits a PDCCH containing information about which terminals (one or more terminals) the PDSCH data will be sent to and how those terminals should receive and decode the PDSCH data. For example, suppose a DCI transmitted via a particular PDCCH is CRC masked with an RNTI named "A", and that DCI indicates that the PDSCH is assigned to a radio resource (e.g., frequency location) named "B", and indicates transmission format information (e.g., transmission block size, modulation scheme, coding information, etc.) named "C". Terminals monitor the PDCCH using their own RNTI information. In this case, if a terminal blind-decodes the PDCCH using the "A" RNTI, that terminal will receive the PDCCH and, through the information of the received PDCCH, receive the PDSCH indicated by "B" and "C".

[0080] Table 3 shows one example of PUCCH used in a wireless communication system.

[0081] [Table 3]

[0082] PUCCH is used to transmit the following uplink control information (UCI).

[0083] -SR (Scheduling Request): This is information used to request uplink UL-SCH resources.

[0084] -HARQ-ACK: A response to a PDCCH and / or an uplink transmission block (TB) on a PDSCH (indicating a DL SPS release). HARQ-ACK indicates the receipt of information transmitted via a PDCCH or PDSCH. HARQ-ACK responses include positive ACK (simply ACK), negative ACK (hereinafter NACK), DTX (Discontinuous Transmission), or NACK / DTX. Here, the term HARQ-ACK is used interchangeably with HARQ-ACK / NACK and ACK / NACK. Generally, ACK is represented by a bit value of 1 and NACK by a bit value of 0.

[0085] -CSI: This is feedback information for the downlink channel. It is generated by the terminal based on the CSI-RS (Reference Signal) transmitted by the base station. MIMO (multiple input multiple output) related feedback information includes RI and PMI. CSI is divided into CSI Part 1 and CSI Part 2 depending on the information it indicates.

[0086] The 3GPP NR system uses five PUCCH formats to support diverse service scenarios, diverse channel environments, and frame structures.

[0087] PUCCH format 0 is a format for transmitting 1-bit or 2-bit HARQ-ACK information or SR. PUCCH format 0 is transmitted via one or two OFDM symbols on the time axis and one RB on the frequency axis. If PUCCH format 0 is transmitted with two OFDM symbols, the same sequence is transmitted for each symbol with different RBs. Through this, the terminal obtains a frequency diversity gain. More specifically, the terminal determines the cyclic shift value mcs according to the Mbit bit UCI (Mbit=1 or 2), and maps a sequence obtained by cyclic shifting a base sequence of length 12 by the determined value mcs to 12 REs (Res) consisting of one OFDM symbol and one PRB, and transmits it. If the number of cyclic shifts available to the terminal is 12 and Mbit=1, then 1-bit UCI0 and 1 are represented by sequences corresponding to two cyclic shifts with a cyclic shift value difference of 6. Furthermore, if Mbit=2, the 2-bit UCI00, 01, 11, and 10 represent a sequence of four cyclic shifts where the difference in cyclic shift values ​​is 3.

[0088] PUCCH format 1 transmits 1-bit or 2-bit HARQ-ACK information or SR. PUCCH format 1 is transmitted via a continuous sequence of OFDM symbols on the time axis and one PRB on the frequency axis. Here, the number of OFDM symbols occupied by PUCCH format 1 is one of 4 to 14. For more details, see M bit UCI with =1 is modulated by BPSK. The terminal is M bitThe UCI, which is equal to 2, is modulated using QPSK (quadrature phase shift keying). The modulated complex valued symbol d(0) is multiplied by a sequence of length 12 to obtain a signal. In this case, the sequence may be the base sequence used for PUCCH format 0. The terminal transmits the obtained signal by spreading it with time-axis OCC (orthogonal cover code) to the even-numbered OFDM symbols to which PUCCH format 1 is assigned. The maximum number of different terminals that multiplex with the same RB in PUCCH format 1 is determined by the length of the OCC used. The DMRS (demodulation reference signal) is spread with OCC and mapped to the odd-numbered OFDM symbols in PUCCH format 1.

[0089] PUCCH format 2 can transmit UCIs of more than 2 bits. PUCCH format 2 can be transmitted via one or two OFDM symbols on the time axis and one or more RBs on the frequency axis. When PUCCH format 2 is transmitted via two OFDM symbols, the same sequence can be transmitted via two OFDM symbols to different RBs, where the sequence is a plurality of modulated complex number symbols d(0), ..., d(M symbol -1) is possible. Here, M symbol is M bit It may also be / 2. This allows the terminal to obtain frequency diversity gain. More specifically, M bit Bit UCI(M bit >2) is bit-level scrambled, QPSK modulated, and mapped to the RB of one or two OFDM symbols, where the number of RBs can be one of 1 to 16.

[0090] PUCCH format 3 or PUCCH format 4 transmits UCI exceeding 2 bits. PUCCH format 3 or PUCCH format 4 is transmitted via OFDM symbols continuous on the time axis and one PRB on the frequency axis. The number of OFDM symbols occupied by PUCCH format 3 or PUCCH format 4 is one of 4 to 14. Specifically, the terminal modulates Mbit bits of UCI (M bit >2) with π / 2-BPSK (Binary Phase Shift Keying) or QPSK to generate complex symbols d(0) to d(M symb -1). Here, when using π / 2-BPSK, M symb =M bit and when using QPSK, Msymb = Mbit / 2. The terminal does not apply block-wise spreading to PUCCH format 3. However, the terminal may apply block-wise spreading to one RB (i.e., 12 subcarriers) using a length-12 PreDFT-OCC so that PUCCH format 4 has two or four multiplexing capacities. The terminal transmit precodes (or DFT-precodes) the spread signal, maps it to each RE, and transmits the spread signal.

[0091] At this time, the number of RBs occupied by PUCCH format 2, PUCCH format 3, or PUCCH format 4 is determined according to the length of the UCI transmitted by the terminal and the maximum code rate. If the terminal uses PUCCH format 2, the terminal transmits both HARQ-ACK information and CSI information via PUCCH. If the number of RBs that the terminal can transmit is greater than the maximum number of RBs that can be used by PUCCH format 2, PUCCH format 3, or PUCCH format 4, the terminal does not transmit some UCI information according to the priority of the UCI information and transmits only the remaining UCI information.

[0092] PUCCH format 1, PUCCH format 3, or PUCCH format 4 is configured via an RRC signal to instruct frequency hopping within a slot. When frequency hopping is configured, the index of the RB to be frequency-hopped is determined by the RRC signal. If PUCCH format 1, PUCCH format 3, or PUCCH format 4 is transmitted over N OFDM symbols in the time axis, the first hop will have floor(N / 2) OFDM symbols, the second hop will have ceil(N / 2) OFDM symbols.

[0093] PUCCH format 1, PUCCH format 3, or PUCCH format 4 are configured to be repeatedly transmitted to multiple slots. In this case, the number K of slots to which the PUCCH is repeatedly transmitted is determined by the RRC signal. The repeatedly transmitted PUCCH should start from the same OFDM symbol in the same position within each slot and have the same length. If any of the OFDM symbols in a slot to which the terminal is to transmit the PUCCH is indicated as a DL symbol by the RRC signal, the terminal does not transmit the PUCCH from that slot but postpones transmission to the next slot.

[0094] On the other hand, in the 3GPP NR system, terminals transmit and receive using a bandwidth smaller than or equal to the carrier (or cell) bandwidth. For this purpose, terminals are configured with a bandwidth part (BWP) consisting of a continuous portion of the carrier bandwidth. Terminals operating according to TDD or in the ampered spectrum have up to four DL / UL BWP pairs per carrier (or cell). The terminal also activates one DL / UL BWP pair. Terminals operating according to FDD or in the paired spectrum have up to four DL BWPs configured on the downlink carrier (or cell) and up to four UL BWPs configured on the uplink carrier (or cell). The terminal activates one DL BWP and one UL BWP for each carrier (or cell). The terminal does not have to receive or transmit from time-frequency resources other than the activated BWPs. The activated BWPs are called active BWPs.

[0095] The base station refers to the activated BWP among the configured BWPs of a terminal as the DCI. The BWP indicated by the DCI is activated, and the other configured BWPs are deactivated. In a carrier (or cell) operating in TDD mode, the base station includes a BPI (bandwidth part indicator) in the DCI that schedules a PDSCH or PUSCH to indicate which BWP to activate in order to change the terminal's DL / UL BWP pair. The terminal receives the DCI that schedules a PDSCH or PUSCH and identifies the DL / UL BWP pair to activate based on the BPI. In the case of a downlink carrier (or cell) operating in FDD mode, the base station includes a BPI informing the DCI that schedules a PDSCH which BWP to activate in order to change the terminal's DL BWP. In the case of an uplink carrier (or cell) operating in FDD mode, the base station includes a BPI informing the DCI that schedules a PUSCH which BWP to activate in order to change the terminal's UL BWP.

[0096] Figure 8 is a conceptual diagram illustrating career aggregation.

[0097] Carrier aggregation refers to a method used by wireless communication systems to utilize a wider frequency band by having terminals use multiple frequency blocks, or (logical) cells, consisting of uplink resources (or component carriers) and / or downlink resources (or component carriers), within a single larger logical frequency band. For convenience of explanation, the term "component carrier" will be used consistently below.

[0098] Referring to Figure 8, as an example of a 3GPP NR system, the overall system bandwidth includes up to 16 component carriers, each component carrier having a bandwidth of up to 400 MHz. Each component carrier includes one or more physically consecutive subcarriers. Although Figure 8 shows each component carrier having the same bandwidth, this is merely illustrative, and each component carrier may have different bandwidths. Also, although each component carrier is shown as being adjacent to each other on the frequency axis, the diagram is a logical representation, and each component carrier may be physically adjacent to or far from each other.

[0099] Each component carrier uses a different center frequency. Furthermore, physically adjacent component carriers share a single common center frequency. In the embodiment shown in Figure 8, assuming all component carriers are physically adjacent, center frequency A is used for all component carriers. If we assume that the component carriers are not physically adjacent, then center frequencies A and B are used for each component carrier.

[0100] When the overall system bandwidth is expanded through carrier aggregation, the frequency band used for communication with each terminal is defined on a component carrier basis. Terminal A uses the overall system bandwidth of 100 MHz and communicates using all five component carriers. Terminals B1 to B5 use only a 20 MHz bandwidth and communicate using one component carrier each. Terminals C1 and C2 use only a 40 MHz bandwidth and communicate using two component carriers each. The two component carriers may be logically / physically adjacent or not. In the embodiment shown in Figure 8, terminal C1 uses two non-adjacent component carriers, and terminal C2 uses two adjacent component carriers.

[0101] Figure 9 is a diagram illustrating terminal carrier communication and multiple carrier communication. Specifically, Figure 9(a) shows the subframe structure of a single carrier, and Figure 9(b) shows the subframe structure of a multiple carrier.

[0102] Referring to Figure 9(a), a typical wireless communication system, in FDD mode, transmits or receives data via one DL band and its corresponding UL band. In other specific embodiments, in TDD mode, the wireless communication system divides the wireless frame into uplink time units and downlink time units in the time domain, and transmits or receives data via the uplink / downlink time units. Referring to Figure 9(b), three 20MHz component carriers (CCs) are aggregated in both the UL and DL bands, supporting a 60MHz bandwidth. Each CC is either adjacent or non-adjacent to the others in the frequency domain. For convenience, Figure 9(b) shows a symmetrical case where the bandwidths of the UL CCs and DL CCs are the same, but the bandwidths of each CC may be determined independently. Asymmetric carrier aggregations with different numbers of UL CCs and DL CCs are also possible. A DL / UL CC assigned / configured to a specific terminal via RRC is referred to as the serving DL / UL CC of that terminal.

[0103] A base station communicates with a terminal by activating some or all of the terminal's serving CCs, or by deactivating some of the CCs. The base station may change which CCs are activated / deactivated, or change the number of CCs that are activated / deactivated. Once a base station assigns available CCs to a terminal, either cell-specific or terminal-specific, at least one of the initially assigned CCs does not need to be deactivated unless the CC assignments for the terminal are completely reconfigured or the terminal is handed over. The CC that is not deactivated by the terminal is called the primary CC (PCC) or PCell (primary cell), and the CCs that the base station can freely activate / deactivate are called secondary CCs (SCC) or SCell (secondary cell).

[0104] On the other hand, 3GPP NR uses the concept of a cell to manage radio resources. A cell is defined as a combination of downlink and uplink resources, i.e., a combination of DL CC and UL CC. A cell consists of DL resources alone, or a combination of DL and UL resources. If carrier aggregation is supported, the linkage between the carrier frequency of the DL resource (or DL ​​CC) and the carrier frequency of the UL resource (or UL CC) is indicated by system information. Carrier frequency refers to the center frequency of each cell or CC. A cell corresponding to a PCC is called a PCell, and a cell corresponding to an SCC is called a SCell. In the downlink, the carrier corresponding to a PCell is a DL PCC, and in the uplink, the carrier corresponding to a PCell is a UL PCC. Similarly, in the downlink, the carrier corresponding to a SCell is a DL SCC, and in the uplink, the carrier corresponding to a SCell is a UL SCC. Depending on the terminal capacity, a serving cell consists of one PCell and zero or more SCells. If the RRC_CONNECTED state exists but carrier aggregation is not configured, or if the UE does not support carrier aggregation, there will be only one serving cell consisting solely of PCells.

[0105] As described above, the term "cell" used in carrier aggregation is distinct from the term "cell" which refers to a specific geographical area where communication services are provided by a single base station or antenna group. However, in order to distinguish between a cell referring to a specific geographical area and a cell in carrier aggregation, in this invention, a cell in carrier aggregation is referred to as CC, and a cell referring to a geographical area is referred to as cell.

[0106] Figure 10 shows an example where the cross-carrier scheduling technique is applied. Once cross-carrier scheduling is set up, the control channel transmitted via the first CC uses the carrier indicator field (CIF) to schedule the data channel transmitted via the first or second CC. The CIF is contained within the DCI. In other words, a scheduling cell is set up, and DL grants / UL grants transmitted from the PDCCH area of ​​the scheduling cell schedule the PDSCH / PUSCH of the scheduled cell. That is, the PDCCH area of ​​the scheduling cell is a search area for multiple component carriers. A PCell is essentially a scheduling cell, and a particular SCell is designated as a scheduling cell by a higher hierarchy.

[0107] In the embodiment shown in Figure 10, we assume that three DL CCs are merged. Here, DL component carrier #0 is assumed to be a DL PCC (or PCell), and DL component carriers #1 and #2 are assumed to be DL SCCs (or SCells). We also assume that the DL PCC is configured as a PDCCH monitoring CC. If cross-carrier scheduling is not configured by terminal-specific (or terminal-group-specific, or cell-specific) higher-level signaling, the CIF will be disabled, and each DL CC will send only PDCCHs that schedule their own PDSCH without a CIF according to the NR PDCCH rule (non-cross-carrier scheduling, self-carrier scheduling). In contrast, if cross-carrier scheduling is configured through terminal-specific (or terminal-group-specific, or cell-specific) higher-level signaling, CIF is enabled, and a specific CC (e.g., DL PCC) uses CIF to transmit not only PDCCHs that schedule DL CC A's PDSCH, but also PDCCHs that schedule other CCs' PDSCHs (cross-carrier scheduling). In contrast, other DL CCs do not transmit PDCCHs. Therefore, depending on whether cross-carrier scheduling is configured for the terminal, the terminal either monitors PDCCHs without CIFs to receive self-carrier scheduled PDSCHs, or monitors PDCCHs with CIFs to receive cross-carrier scheduled PDSCHs.

[0108] On the other hand, Figures 9 and 10 illustrate the subframe structure of a 3GPP LTE-A system, and the same or similar configurations are applicable to a 3GPP NR system. However, in a 3GPP NR system, the subframes in Figures 9 and 10 are switched to slots.

[0109] Figure 11 is a block diagram showing the configuration of a terminal and a base station according to one embodiment of the present invention.

[0110] In one embodiment of the present invention, the terminal is embodied in various types of wireless communication devices or computing devices that ensure portability and mobility. The terminal is referred to as UE, STA (Station), MS (Mobile Subscriber), etc. In another embodiment of the present invention, the base station controls and manages the cells (e.g., macrocells, femtocells, picocells, etc.) in the service area and performs functions such as signal transmission, channel assignment, channel monitoring, self-diagnosis, and relaying. The base station is referred to as gNB (next Generation NodeB) or AP (Access Point), etc.

[0111] As shown in the figure, a terminal 100 according to one embodiment of the present invention includes a processor 110, a communication module 120, a memory 130, a user interface unit 140, and a display unit 150.

[0112] First, the processor 110 executes various instructions or programs to process data inside the terminal 100. The processor 110 also controls the overall operation of the terminal 100, including each unit, and controls the transmission and reception of data between units. Here, the processor 110 is configured to perform the operations described in the embodiment of the present invention. For example, the processor 110 may receive slot configuration information, determine the slot configuration based on that information, and perform communication according to the determined slot configuration.

[0113] Next, the communication module 120 is an integrated module that performs wireless communication using a wireless communication network and wireless LAN access using a wireless LAN. To this end, the communication module 120 incorporates multiple network interface cards (NICs), such as cellular communication interface cards 121 and 122 and an unlicensed band communication interface card 123, either internally or externally. In the drawing, the communication module 120 is shown as an integrated module, but each network interface card may be arranged independently depending on the circuit configuration or application, contrary to the drawing.

[0114] The cellular communication interface card 121 transmits and receives radio signals to and from at least one of the base station 200, an external device, and a server via a mobile communication network, and provides cellular communication services in a first frequency band based on instructions from the processor 110. According to one embodiment, the cellular communication interface card 121 includes at least one NIC module that utilizes a frequency band of less than 6 GHz. The at least one NIC module of the cellular communication interface card 121 independently performs cellular communication with at least one of the base station 200, an external device, and a server, depending on the cellular communication standard or protocol of the sub-6 GHz frequency band supported by the NIC module.

[0115] The cellular communication interface card 122 uses a mobile communication network to send and receive radio signals with at least one of the base station 200, an external device, or a server, and provides cellular communication services in the second frequency band based on instructions from the processor 110. According to one embodiment, the cellular communication interface card 122 includes at least one NIC module that utilizes a frequency band of 6 GHz or higher. At least one NIC module of the cellular communication interface card 122 independently performs cellular communication with at least one of the base station 200, an external device, or a server, according to the cellular communication standard or protocol of the 6 GHz or higher frequency band supported by the NIC module.

[0116] The unlicensed band communication interface card 123 transmits and receives radio signals to and from at least one of the base station 200, an external device, or a server via the third frequency band, which is an unlicensed band, and provides communication services in the unlicensed band based on instructions from the processor 110. The unlicensed band communication interface card 123 includes at least one NIC module that utilizes the unlicensed band. For example, the unlicensed band may be a 2.4 GHz or 52.6 GHz band. At least one NIC module of the unlicensed band communication interface card 123 independently or dependently performs cellular communication with at least one of the base station 200, an external device, or a server, depending on the unlicensed band communication standard or protocol of the frequency band supported by the NIC module.

[0117] Next, the memory 130 stores control programs used by the terminal 100 and various data associated with them. Such control programs include predetermined programs necessary for the terminal 100 to communicate wirelessly with at least one of the following: a base station 200, an external device, or a server.

[0118] Next, the user interface 140 includes various forms of input / output means provided in the terminal 100. In other words, the user interface unit 140 receives user input using various input means, and the processor 110 controls the terminal 100 based on the received user input. The user interface 140 also outputs based on instructions from the processor 110 using various output means.

[0119] Next, the display unit 150 outputs various images to the display screen. The display unit 150 outputs various display objects, such as content generated by the processor 110 or user interfaces based on control instructions from the processor 110.

[0120] Furthermore, the base station 200 according to the embodiment of the present invention includes a processor 210, a communication module 220, and a memory 230.

[0121] First, the processor 210 executes various instructions or programs to process data within the base station 200. The processor 210 also controls the overall operation of the base station 200, including each unit, and controls the transmission and reception of data between units. Here, the processor 210 is configured to perform the operations described in the embodiment of the present invention. For example, the processor 210 may signal slot configuration information and perform communication according to the signaled slot configuration.

[0122] Next, the communication module 220 is an integrated module that performs wireless communication using a wireless communication network and wireless LAN access using a wireless LAN. To this end, the communication module 220 incorporates multiple network interface cards, such as cellular communication interface cards 221 and 222, and an unlicensed band communication interface card 223, either internally or externally. In the drawings, the communication module 220 is shown as an integrated module, but each network interface card may be arranged independently depending on the circuit configuration or application, contrary to the drawings.

[0123] The cellular communication interface card 221 transmits and receives wireless signals to and from at least one of the terminal 100, external devices, and servers described above using a mobile communication network, and provides cellular communication services in the first frequency band based on instructions from the processor 210. According to one embodiment, the cellular communication interface card 221 includes at least one NIC module that utilizes a frequency band of less than 6 GHz. At least one NIC module of the cellular communication interface card 221 independently performs cellular communication with at least one of the terminal 100, external devices, and servers, depending on the cellular communication standard or protocol of the frequency band of less than 6 GHz supported by the NIC module.

[0124] The cellular communication interface card 222 transmits and receives wireless signals to and from at least one of the terminal 100, an external device, and a server using a mobile communication network, and provides cellular communication services in a second frequency band based on instructions from the processor 210. According to one embodiment, the cellular communication interface card 222 includes at least one NIC module that utilizes a frequency band of 6 GHz or higher. At least one NIC module of the cellular communication interface card 222 independently performs cellular communication with at least one of the terminal 100, an external device, and a server, according to the cellular communication standard or protocol of the 6 GHz or higher frequency band supported by the NIC module.

[0125] The unlicensed band communication interface card 223 uses the third frequency band, which is an unlicensed band, to send and receive wireless signals with at least one of the terminal 100, an external device, or a server, and provides communication services in the unlicensed band based on instructions from the processor 210. The unlicensed band communication interface card 223 includes at least one NIC module that utilizes the unlicensed band. For example, the unlicensed band may be the 2.4GHz or 52.6GHz band. At least one NIC module of the unlicensed band communication interface card 223 independently or dependently performs cellular communication with at least one of the terminal 100, an external device, or a server, depending on the unlicensed band communication standard or protocol of the frequency band supported by the NIC module.

[0126] The terminal 100 and base station 200 shown in Figure 11 are block diagrams according to one embodiment of the present invention, and the separately shown blocks represent logically distinguished elements of the device. Therefore, the above-mentioned elements of the device are mounted on one or more chips depending on the device design. Furthermore, some components of the terminal 100, such as the user interface unit 150 and the display unit 150, may be selectively provided in the terminal 100. In addition, the user interface 140 and the display unit 150 may be additionally provided in the base station 200 as needed.

[0127] The following describes how a terminal receives a physical downlink control channel and a physical downlink sharing channel, and how it transmits a physical uplink control channel and a physical uplink sharing channel, using Figures 12 and 13.

[0128] The terminal can receive the physical downlink control channel transmitted from the base station, and may be configured to receive the downlink control channel by setting information such as a control resource set (CORESET) or a search space.

[0129] The control resource set includes frequency domain information on which the physical downlink control channel should be received. More specifically, the information in the control resource set may include the index of the PRB or PRB set on which the terminal should receive the physical downlink control channel, and the number of consecutive symbols. Here, the number of consecutive symbols is one of 1, 2, or 3.

[0130] The search space includes time information for receiving the set of PRBs specified in the control resource set. More specifically, the search space information may include at least one of the following: periodicity or offset. Here, the periodicity or offset may be specified in units of slots, subslots, symbols, symbol sets, or slot sets. Furthermore, the search space information may include the CCE aggregation level received by the terminal, the number of PDCCHs to monitor for each CCE aggregation level, the search space type, or the DCI format or RNTI information to monitor.

[0131] The CCE integration level has at least one value from 1, 2, 4, 8, or 16. The terminal can monitor the PDCCH with the same number of control channel elements (CCE) as the value of the CCE integration level.

[0132] The search space type may be a common search space (CSS) or an UE-specific search space. The common search space means a search space in which all terminals in a cell or some terminals in a cell commonly monitor PDCCHs. Terminals can monitor and receive candidate PDCCHs (for example, PDCCHs that transmit DCIs having a CRC scrambled with at least one RNTI from among SI-RNTI, RA-RNTI, MsgB-RNTI, P-RNTI, TC-RNTI, INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, CI-RNTI, C-RNTI, MCS-C-RNTI, CS-RNTI, or PS-RNTI) broadcast in this search space to all terminals in a cell or some terminals in a cell. In the terminal identification search space, it is possible to monitor and receive candidate PDCCHs (for example, PDCCHs that transmit DCIs having a CRC scrambled with at least one RNRTI from C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, CS-RNTI, SL-RNTI, SL-CS-RNTI, or SL-L-CS-RNTI) that are sent to individual terminals. In addition, terminals can receive PDCCHs that transmit DCIs instructing the reception of a physical downlink sharing channel, the transmission of a physical uplink control channel, or the transmission of a physical uplink sharing channel in the common search space and the terminal identification search space.

[0133] The DCI format monitored by a terminal that is scheduled to transmit a physical uplink shared channel and receive a physical downlink shared channel from a base station may be DCI format 0_0, 0_1, 0_2, 1_0, 1_1, or 1_2. The RNTI information in DCI format 0_0, 0_1, 0_2, 1_0, 1_1, or 1_2 may include at least one RNTI from among CS-RNTI, MCS-C-RNTI, or C-RNTI. Here, CS-RNTI is used by the base station to activate / release or retransmit an SPS (semi-persistent) PDSCH or CG (configured grant) PUSCH, and can also be used by the terminal for reception. Here, MCS-C-RNTI is used by the base station to schedule a PDSCH or PUSCH using a highly reliable MCS (modulation and coding scheme), and can also be used by the terminal for reception. C-RNTI is used by base stations to schedule PDSCH or PUSCH, and terminals can use it to receive.

[0134] Furthermore, the DCI format that the terminal monitors in PDCCH may include at least the following:

[0135] DCI Format 2_0 includes Dynamic SFI (slot format indicator) information that indicates the orientation of slot symbols as uplink, downlink, or flexible symbols. The RNTI used for DCI Format 2_0 is SFI-RNTI.

[0136] DCI format 2_1 includes a PRB and a DL preemption indication (or interrupted transmission indication) that indicates there are no downlink transmissions sent from the base station to the terminal. The RNTI used for DCI format 2_1 is INT-RNTI.

[0137] DCI format 2_4 indicates a UL cancellation indication in which the terminal signals the cancellation of an uplink transmission using a PRB and symbols. The RNTI used for DCI format 2_4 is CI-RNTI.

[0138] The terminal can determine PDCCH candidates that should receive a PDCCH using the configured control resource set and search space information. The terminal can monitor the PDCCH candidates, check the CRC using the RNTI value, and then determine whether a correct PDCCH has been received. The RNTI value may include at least C-RNTI, MCS-C-RNTI, CS-RNTI, as well as SFI-RNTI, INT-RNTI, and CI-RNTI values.

[0139] If a terminal receives a correct PDCCH, the terminal can analyze the DCI (downlink control information) transmitted by the PDCCH based on the control resource set and search space information, and perform the operation instructed by the DCI. The DCI may include one of DCI formats 0_0, 0_1, or 0_2 for scheduling a physical uplink sharing channel (PUSCH). The DCI may include one of DCI formats 1_0, 1_1, or 1_2 for scheduling a physical downlink sharing channel (PDSCH). The DCI may include one of DCI formats 1_0, 1_1, or 1_2 for scheduling a physical uplink control channel (PUCCH). For reference, the PUCCH may include a PUCCH that transmits a HARQ-ACK. The DCI may also include DCI formats 2_0, 2_1, or 2_4.

[0140] When a terminal receives DCI format 1_0, 1_1, or 1_2 for scheduling a physical downlink shared channel (PDSCH), the terminal must receive the downlink shared channel scheduled by the DCI format. To do this, the terminal must analyze (determine) from the DCI format the slot in which the physical downlink shared channel is scheduled, and the starting index and length of the symbols within that slot. The TDRA (time domain resource assignment) field of DCI format 1_0, 1_1, or 1_2 can indicate the K0 value, which is the timing information of the scheduled slot, and the SLIV (starting length indicator value), which is the index and length of the starting symbol within that slot. Here, the K0 value may be a non-negative integer. Here, SLIV may be a joint-encoded value of the index (S) and length (L) of the starting symbol within the slot. Alternatively, SLIV may be a value where the index (S) and length (L) of the starting symbol within the slot are transmitted separately. Here, in a normal CP, S may have one value from 0, 1, ..., 13, and L may have one value from among the natural numbers that satisfy the condition S+L is less than or equal to 14. In an extended CP, S may have one value from 0, 1, ..., 11, and L may have one value from among the natural numbers that satisfy the condition S+L is less than or equal to 12.

[0141] The terminal can determine which slot should receive the physical downlink shared channel (PDSCH) based on the K0 value. More specifically, the terminal can determine which slot should receive the physical downlink shared channel based on the K0 value, the index of the slot where the DCI is received, the subcarrier spacing (SCS) of the downlink BWP that received the DCI, or the subcarrier spacing of the downlink BWP that receives the scheduled downlink shared channel.

[0142] For example, let's assume that the subcarrier interval of the downlink BWP that receives the DCI and the downlink BWP that receives the scheduled physical downlink shared channel (PDSCH) are the same. Let's assume that the DCI is received in downlink slot n. In this case, the downlink shared channel (PDSCH) must be received in downlink slot n+K0.

[0143] For example, let's assume that the subcarrier interval of the downlink BWP that receives the DCI is 15kHz*2^mu_PDCCH, and the subcarrier interval of the downlink BWP that receives the scheduled physical downlink shared channel (PDSCH) is 15kHz*2^mu_PDSCH. Let's assume that the DCI is received in downlink slot n. Here, the index of downlink slot n is the index based on the subcarrier interval of the downlink BWP that received the DCI. In this case, the physical downlink shared channel must be received in slot floor(n*2^mu_PDSCH / 2^mu_PDCCH)+K0. Here, the index of the downlink slot floor(n*2^mu_PDSCH / 2^mu_PDCCH)+K0 is the index based on the subcarrier interval of the downlink BWP that receives the physical downlink shared channel. In the above explanation, mu_PDCCH or mu_PDSCH may have values ​​of 0, 1, 2, or 3.

[0144] Figure 12 shows the scheduling of a Physical Downlink Shared Channel (PDSCH) according to one embodiment of the present invention.

[0145] Referring to Figure 12, the terminal may schedule the PDSCH according to the specific format of the DCI of the PDCCH.

[0146] Specifically, as shown in Figure 12, the terminal can receive a PDCCH that schedules a physical downlink shared channel (PDSCH) in downlink slot n. Let's assume that the K0 of the DCI transmitted via the PDCCH indicates 3. Let's also assume that the subcarrier interval of the DL BWP where the PDCCH is received is the same as the subcarrier interval of the DL BWP where the PDSCH is scheduled. In this case, the terminal can determine that the PDSCH is scheduled in downlink slot n+K0, i.e., slot n+3.

[0147] The terminal can determine which symbols should receive the physical downlink shared channel (PDSCH) in the slot where the PDSCH should be received, using the index (S) and length (L) of the starting symbol within the slot, based on the K0 value. The symbols that should receive the physical downlink shared channel (PDSCH) are symbols S through S+L-1 within the slot, determined based on the K0 value. For reference, symbols S through S+L-1 are L consecutive symbols.

[0148] The terminal may have further downlink slot aggregation configured from the base station. The downlink slot aggregation value may be 2, 4, or 8. Once downlink slot aggregation is configured, the terminal must receive a physical downlink shared channel (PDSCH) in consecutive slots corresponding to the slot aggregation value, based on the slots determined from the K0 value.

[0149] When a terminal receives DCI format 1_0, 1_1, or 1_2 for scheduling a physical uplink control channel, the terminal must transmit the scheduled uplink control channel. The physical uplink control channel may include HARQ-ACK information. The PDSCH-to-HARQ_feedback timing indicator field in DCI format 1_0, 1_1, or 1_2 can indicate a K1 value, which is a value for information about the slot to which the scheduled uplink control channel should be transmitted. Here, the value of K1 may be a non-negative integer. The K1 value in DCI format 1_0 can indicate one of {0, 1, 2, 3, 4, 5, 6, 7}. The K1 values ​​that can be indicated in DCI format 1_1 or 1_2 may be configured or set from the upper layer.

[0150] The HARQ-ACK information may be HARQ-ACK information regarding the success or failure of reception of two types of channels. The first type may be HARQ-ACK information regarding the success or failure of reception of a physical downlink shared channel (PDSCH) when a physical downlink shared channel (PDSCH) is scheduled in DCI format 1_0, 1_1, or 1_2. The second type may be HARQ-ACK information regarding the success or failure of reception of DCI format 1_0, 1_1, or 1_2 when DCI format 1_0, 1_1, or 1_2 is a DCI that instructs the release of a semi-static physical downlink shared channel (SPS PDSCH).

[0151] The terminal can determine the slot to transmit an uplink control channel containing the first type of HARQ-ACK information as follows: The terminal can determine the uplink slot that overlaps with the last symbol of the physical downlink shared channel (PDSCH) corresponding to the HARQ-ACK information. When the index of the uplink slot is m, the uplink slot to which the terminal transmits the physical uplink control channel containing the HARQ-ACK information may be m+K1. Here, the index of the uplink slot is a value based on the subcarrier interval of the uplink BWP to which the uplink control channel is transmitted.

[0152] For reference, when downlink slot aggregation is configured on a terminal, the last symbol indicates the last symbol of the PDSCH scheduled within the last slot among the slots from which the physical downlink shared channel (PDSCH) is received.

[0153] Figure 13 shows the scheduling of a Physical Uplink Control Channel (PUCCH) according to one embodiment of the present invention.

[0154] Referring to Figure 13, the terminal can receive scheduling information for transmitting PDSCH and PUCCH via the DCI of PDCCH, and can receive PDSCH and transmit PUCCH based on the received DCI.

[0155] Specifically, as shown in Figure 13, the terminal can receive a PDCCH that schedules a downlink shared channel (PDSCH) in downlink slot n. At this time, the DCI transmitted from the PDCCH may include scheduling information for receiving the PDSCH and transmitting the PUCCH. For example, if the value of K0 included in the DCI is "3" and the value of K1 is "2", and the subcarrier interval of the DL BWP where the PDCCH is received, the subcarrier interval of the DL BWP where the PDSCH is scheduled, and the subcarrier interval of the UL BWP where the PUCCH is transmitted are the same, the terminal can determine that the PDSCH is scheduled in downlink slot n+K0, i.e., slot n+3. The terminal also determines the uplink slot that overlaps with the last symbol of the PDSCH scheduled in downlink slot n+3. Here, the last symbol of the PDSCH in downlink slot n+3 overlaps with the uplink slot n+3. Therefore, the terminal sends a PUCCH to the uplink slot n+3+K1, i.e., slot n+5.

[0156] The terminal can determine the slot to transmit a physical uplink control channel containing a second type of HARQ-ACK information as follows: The terminal can determine the uplink slot that overlaps with the last symbol of the physical downlink control channel (PDCCH) corresponding to the HARQ-ACK information. When the index of the uplink slot is m, the slot to which the terminal transmits the uplink control channel containing the HARQ-ACK information may be m+K1. Here, the index of the slot is a value based on the subcarrier interval of the uplink BWP to which the physical uplink control channel (PUCCH) is transmitted.

[0157] Figure 14 shows the scheduling of a physical uplink sharing channel and a physical uplink control channel according to one embodiment of the present invention.

[0158] Referring to Figure 14, the terminal can receive scheduling information for sending PUSCH and PUCCH via the DCI of PDCCH, and can send PUSCH and PUCCH based on the received DCI.

[0159] As shown in Figure 14, the terminal can receive a PDCCH transmitting an SPS PDSCH release DCI in downlink slot n. At this time, if K1 of the DCI transmitted from the PDCCH indicates "3", and the subcarrier interval of the DL BWP where the PDCCH is received is the same as the subcarrier interval of the UL BWP where the PUCCH is transmitted, the terminal determines the uplink slot that overlaps with the last symbol of the PDCCH in downlink slot n. In this case, the terminal can determine that a PUCCH transmitting an SPS PDSCH release DCI HARQ-ACK is scheduled in uplink slot n+K1, i.e., n+3.

[0160] When a terminal receives DCI format 0_0, 0_1, or 0_2 to schedule a physical uplink shared channel, the terminal must transmit the scheduled uplink shared channel. To do this, the terminal must analyze (determine) from the DCI the slot in which the physical uplink shared channel is scheduled, as well as the starting index and length of the symbols within that slot. In DCI formats 0_0, 0_1, or 0_2, the TDRA (time domain resource assignment) field can indicate a K2 value, which is a value for information about the scheduled slot, and an SLIV (starting length indicator value), which is a value for information about the index and length of the starting symbols within the slot. Here, the K2 value may be a non-negative integer. Here, SLIV may be a joint-encoded value of the index (S) and length (L) of the starting symbols within the slot. Alternatively, SLIV may be a value where the index (S) and length (L) of the starting symbols within the slot are transmitted separately. Here, in a normal CP, S may have one value from 0, 1, ..., 13, and L may have one value from among the natural numbers that satisfy the condition S+L is less than or equal to 14. In an extended CP, S may have one value from 0, 1, ..., 11, and L may have one value from among the natural numbers that satisfy the condition S+L is less than or equal to 12.

[0161] The terminal can determine which slot should transmit the physical uplink shared channel (PUSCH) based on the K2 value. More specifically, the terminal can determine which slot should transmit the physical uplink shared channel (PUSCH) based on the K2 value, the index of the slot where the DCI is received, the subcarrier interval of the downlink BWP that received the DCI, or the subcarrier interval of the uplink BWP that transmits the uplink shared channel.

[0162] For example, let's assume that the subcarrier intervals of the downlink BWP that receives the DCI and the uplink BWP that transmits the scheduled physical uplink shared channel (PUSCH) are the same. Let's assume that the DCI is received in downlink slot n. In this case, the uplink shared channel (PUSCH) must be transmitted in uplink slot n+K2.

[0163] For example, let's assume that the subcarrier interval of the downlink BWP that receives the DCI is 15kHz*2^mu_PDCCH, and the subcarrier interval of the uplink BWP that receives the scheduled physical uplink shared channel (PUSCH) is 15kHz*2^mu_PUSCH. Let's assume that the DCI is received in downlink slot n. Here, the index of downlink slot n is the index based on the subcarrier interval of the downlink BWP that received the DCI. In this case, the physical uplink shared channel (PUSCH) must be transmitted in slot floor(n*2^mu_PUSCH / 2^mu_PDCCH)+K2. Here, the index of the uplink slot floor(n*2^mu_PUSCH / 2^mu_PDCCH)+K2 is the index based on the subcarrier interval of the uplink BWP that transmits the uplink shared channel. In the above explanation, mu_PDCCH or mu_PUSCH may have values ​​of 0, 1, 2, or 3.

[0164] As shown in Figure 14, the terminal can receive a PDCCH in downlink slot n that schedules a physical uplink shared channel (PUSCH). At this time, the DCI transmitted from the PDCCH indicates that the value of K2 is "3", and the subcarrier interval of the DL BWP where the PDCCH is received is the same as the subcarrier interval of the UL BWP where the PUCCH is transmitted. In this case, the terminal can determine that a PUSCH is scheduled in uplink slot n + K2 = n + 3.

[0165] Based on the K2 value, the terminal can determine which symbols should transmit the physical uplink shared channel (PUSCH) in the slot where the PUSCH should be transmitted, using the index (S) and length (L) of the starting symbol within the slot. The symbols to which the physical uplink shared channel (PUSCH) should be transmitted are symbols S to S+L-1 within the slot, determined based on the K2 value. For reference, symbols S to S+L-1 are L consecutive symbols.

[0166] The terminal may have an uplink slot aggregation set up from the base station. The uplink slot aggregation value may be 2, 4, or 8. Once the uplink slot aggregation is set up, the terminal must transmit a physical uplink shared channel (PUSCH) using consecutive slots corresponding to the slot aggregation value, determined based on the K2 value.

[0167] In Figures 12 to 14, the terminal uses K0, K1, and K2 values ​​to determine the slot on which the scheduled physical downlink sharing channel (PDSCH) is received, the slot on which the physical uplink control channel (PUCCH) and physical uplink sharing channel (PUSCH) are transmitted. For the convenience of this invention, the slot obtained by assuming that the K0, K1, and K2 values ​​are 0 is called the reference point or reference slot.

[0168] In Figure 12, the reference slot to which the K0 value is applied is the downlink slot n, which is the slot where the PDCCH was received.

[0169] In Figure 13, the reference slot to which the K1 value is applied is the uplink slot n+3, which is the uplink slot that overlaps with the last symbol of the PDSCH.

[0170] In Figure 14, the reference slot to which the K1 value is applied is the uplink slot n, which is the uplink slot that overlaps with the last symbol of the PDCCH. The reference slot to which the K2 value is applied is also the uplink slot n.

[0171] For convenience in this invention, the following description assumes that the subcarrier interval of the downlink BWP that receives PDSCH and PDCCH at the terminal is the same as the subcarrier interval of the uplink BWP that transmits PUSCH and PUCCH. In this case, separate uplink slots and downlink slots are not distinguished and are simply referred to as slots.

[0172] In the previous explanation, the terminal received one DCI from the base station and, based on the DCI, received a PDSCH or sent a PUSCH in one slot. However, if the base station provides scheduling information for one slot using one DCI, then to schedule multiple slots, it must send the same number of DCIs as there are slots. This can lead to a waste of downlink resources.

[0173] To solve this, a method may be used in which the terminal receives one DCI from the base station and receives PDSCHs in multiple slots based on the DCI. Here, the PDSCHs received in each slot may contain different downlink data. More specifically, the PDSCHs received in each slot may contain different transport blocks (TBs). Also, the PDSCHs received in each slot may have different HARQ process numbers. Furthermore, the PDSCHs received in each slot may occupy different symbols within each slot.

[0174] Alternatively, a method may be used in which the terminal receives one DCI from the base station and transmits PUSCHs in multiple slots based on the DCI. Here, each PUSCH transmitted in each slot may contain different uplink data. More specifically, each PUSCH transmitted in each slot may contain different transport blocks (TBs). Also, each PUSCH transmitted in each slot may have different HARQ process numbers. Furthermore, each PUSCH transmitted in each slot may occupy different symbols within each slot.

[0175] As described above, receiving PDSCH signals or transmitting PUSCH signals in multiple slots based on a single DCI is conveniently referred to as multi-slot scheduling.

[0176] For reference, this type of multi-slot scheduling differs from existing slot aggregation (a method of repeatedly receiving PDSCH signals or repeatedly transmitting PUSCH signals using multiple slots) in the following ways.

[0177] Existing slot aggregation (a method of repeatedly receiving PDSCH or repeatedly transmitting PUSCH in multiple slots) is a method of repeatedly receiving or transmitting PDSCH or PUSCH with the same TB in multiple slots in order to expand coverage and improve reliability. However, multi-slot scheduling is a method of receiving or transmitting PDSCH or PUSCH with different TBs in multiple slots in order to reduce the overhead of the downlink control channel.

[0178] In existing downlink slot aggregation (a method of repeatedly receiving PDSCHs in multiple slots), PDSCHs containing the same TB are received in multiple slots, so the success or failure of receiving the same TB is determined from the PDSCHs received in the multiple slots. Therefore, the terminal must send a HARQ-ACK to the base station indicating the success or failure of receiving the single TB. However, in multi-slot scheduling, the terminal must determine whether reception was successful for each TB, since the PDSCHs received in the multiple slots contain different TBs. Furthermore, it must send a HARQ-ACK to the base station indicating whether reception was successful for each TB.

[0179] The scheduling for multiple slots will be explained below using Figures 15 to 17.

[0180] Figure 15 shows the scheduling of a downlink shared channel by multiple slot scheduling according to one embodiment of the present invention.

[0181] Referring to Figure 15, a terminal may schedule PDSCH reception in multiple slots by a single DCI of the PDCCH. In other words, multiple PDSCHs may be scheduled on the terminal by a single DCI.

[0182] Specifically, one DCI can schedule the reception of a PDSCH in multiple slots. As shown in Figure 15, a PDCCH containing one DCI may be received in slot n. The TDRA (time domain resource assignment) field contained in one DCI can indicate the K0 value, which is the timing information of the scheduled slot, and the SLIV (starting length indicator value) value, which is the index and length of the starting symbol within each slot. More specifically, the K0 value may determine the first slot from which the PDSCH is transmitted. The reception of the PDSCH may be scheduled in M ​​consecutive slots starting from the first slot determined by the K0 value. For example, as shown in Figure 15, if K0 is "3" and M is "3", the reception of the PDSCH may be scheduled in slots n+3, n+4, and n+5. The terminal may be instructed on the index (S) of the starting symbol and the number of consecutive symbols (L) for the reception of the PDSCH in each slot. These may be the same or different for each slot. If they differ for each slot, the index (S) of the starting symbol for receiving the PDSCH and the number of consecutive symbols (L) may be specified for each slot.

[0183] Table 4 below is an example showing a TDRA table used for multi-slot scheduling. The TDRA table may consist of 12 entries, each entry may be assigned an index from 0 to 11. Each entry can schedule a PDSCH in up to 4 slots. To illustrate this, each entry may be given up to 4 SLIV (starting and length value) values ​​and a K0 value. Here, the K0 value indicates the difference between the slot where the PDCCH was received and the slot where the PDSCH is received. SLIV indicates the starting index (S) of the symbol in which the PDSCH is received in the slot and the number of consecutive symbols (L). In Table 4, a PDSCH scheduled in one slot may be represented as (K0, S, L).

[0184] [Table 4]

[0185] If multiple slot scheduling allows PDSCH to be scheduled in consecutive slots, the K0 value indicating the scheduled slot may be omitted. This is shown in Table 5 below. More specifically, each entry in the TDRA table may contain only one K0 value. Each entry may also contain two or more SLIV values ​​(i.e., (S,L)). In that case, PDSCH reception may be scheduled for the symbol corresponding to the first SLIV value (first (S,L)) in the slot determined by the K0 value, and PDSCH reception may be scheduled for the symbol corresponding to the second SLIV value (second (S,L)) in the next slot.

[0186] [Table 5]

[0187] If multiple slot scheduling allows scheduling a PDSCH in a discontinuous slot, the SLIV may include a K0 value indicating the scheduled slot and an offset value from that K0 value slot. Here, the offset value indicates the difference between the slot indicated by the K0 value and the slot to which reception is instructed. This is shown in Table 6. More specifically, each entry in the TDRA table may include only one K0 value. Each SLIV may further have an offset value (O in Table 6). For reference, the SLIV of the K0 value slot may omit the aforementioned offset value.

[0188] [Table 6]

[0189] For the sake of explanation, this invention will describe the case where PDSCH is scheduled in multiple consecutive slots. Therefore, unless otherwise specified, the value of K0 will be omitted. However, this invention also includes the case where PDSCH is scheduled in multiple non-contiguous slots.

[0190] Figure 16 shows the transmission of an uplink control channel in one slot by multiple slot scheduling according to one embodiment of the present invention.

[0191] Referring to Figure 16, the terminal may have multiple slots scheduled to receive PDSCHs via a single DCI of PDCCH, and the HARQ-ACKs of the scheduled multiple PDSCHs may be transmitted via PUCCH in one slot.

[0192] Specifically, a HARQ-ACK for a PDSCH scheduled to be received by multiple slots by a single DCI may be transmitted as a PUCCH in one slot. Here, the uplink slot that coincides with the end of the last PDSCH among the PDSCHs received by multiple slots can be determined to be the uplink slot with a K1 value of 0. In Figure 16, uplink slot n+5 is the uplink slot with a K1 value of 0 and can be called a reference slot. A terminal may be instructed by the single DCI to have one K1 value. In this case, the uplink slot corresponding to the one K1 can transmit a HARQ-ACK for a PDSCH scheduled to be received by multiple slots by the single DCI.

[0193] In other words, a terminal may schedule the reception of multiple PDSCHs in multiple slots and the transmission of HARQ-ACKs in one slot using a single DCI. The terminal can determine the first slot for transmitting multiple PDSCHs using the K0 value of the DCI, the slot on which the last PDSCH of the multiple PDSCH was transmitted as the reference slot, and the single slot for transmitting HARQ-ACKs for the multiple PDSCHs using the K1 value.

[0194] Figure 17 shows a diagram illustrating the transmission of an uplink control channel using two or more slots through multiple slot scheduling according to one embodiment of the present invention.

[0195] Referring to Figure 17, the terminal may have a single DCI of a PDCCH that schedules reception of PDSCHs in multiple slots, and the scheduled multiple PDSCH HARQ-ACKs may be transmitted via PUCCH in two or more slots.

[0196] Specifically, a HARQ-ACK of a multiplexed PDSCH scheduled to be received in multiple slots by a single DCI may be transmitted as a PUCCH in two or more slots. In this case, first, the PDSCHs scheduled to be received in multiple slots by a single DCI may be grouped into two or more groups. For example, multiplexed PDSCHs may be grouped into two or more groups in chronological order, and PDSCHs that are consecutive in chronological order (i.e., sequentially according to time) may be grouped into one group. As shown in Figure 17, a single DCI may be scheduled to receive PDSCHs in three slots, and the first two PDSCHs of the three slots may be grouped together into one group (group0), and the last one into another group (group1). The specific method for grouping the above is as follows.

[0197] As a first method, a terminal can group PDSCHs based on the number of PDSCHs scheduled in a single DCI. In this case, the number of PDSCHs to be grouped may be limited to a certain number. Therefore, PDSCHs may be grouped in fixed numbers, and one or more groups may be generated. For example, if the fixed number is 2 and the number of PDSCHs is 4, the 4 PDSCHs can be grouped together in sets of 2. Here, the fixed number may be set by the base station.

[0198] As a second method, a terminal can create groups based on a predetermined number of groups in a single DCI. That is, a predetermined number of groups may be set for the terminal by the base station. For example, if the predetermined number of groups is 2, and the number of PDSCHs scheduled by one DCI is 6, then the 6 PDSCHs can be divided into 2 groups. In this case, the PDSCHs may be sequentially combined into one group over time, and the number of PDSCHs included in each group may be as similar as possible, with a difference of up to 1.

[0199] As a third method, the terminal may be configured to specify how each entry in the TDRA is grouped. More specifically, each entry in the TDRA contains information for PDSCH reception in multiple slots. This may include information on which slots' PDSCHs are grouped together. That is, in addition to the SLIV indicating the reception of PDSCH in each slot, an index of the group containing the SLIV may be included. Referring to Table 7, each entry in the TDRA table may include an index (G) of the group containing the SLIV. Here, an SLIV belonging to G=0 corresponds to group 0, and an SLIV belonging to G=1 corresponds to group 1.

[0200] [Table 7]

[0201] A terminal can transmit the HARQ-ACK of a PDSCH included in a group using the PUCCH of the uplink slot. The method for determining the uplink slot is to identify the uplink slot that coincides with the end of the last PDSCH included in the group as the reference slot, which has a K1 value of 0. That is, in Figure 16, the reference slot for group 0 is slot n+4, and the reference slot for group 1 is slot n+5.

[0202] A terminal may be instructed to receive one K1 value from one DCI. In this case, for each group, the HARQ-ACK of the PDSCH scheduled to be received by multiple slots by the DCI can be transmitted in the uplink slot corresponding to the one K1. For example, in Figure 17, K1=2. The HARQ-ACKs of the two PDSCHs included in group 0 are transmitted in the PUCCH of slot n+4+2 (=reference slot index of group 0 + K1), and the HARQ-ACK of the one PDSCH included in group 1 is transmitted in the PUCCH of slot n+7 (=reference slot index of group 1 + K1).

[0203] The terminal may be instructed by the aforementioned DCI to specify a K1 value for each group. In this case, for each group, the terminal can send a HARQ-ACK of a PDSCH that the aforementioned DCI has scheduled to receive in multiple slots, using the uplink slot corresponding to the K1 of each group. For example, the K1 value may be 1 for group 0 and 2 for group 1. In this case, the HARQ-ACKs of the two PDSCHs included in group 0 are sent via PUCCH in slot n+4+K1 (=reference slot index of group 0 + K1 of group 0), and the HARQ-ACK of the one PDSCH included in group 1 is sent via PUCCH in slot n+7 (=reference slot index of group 1 + K1 of group 1).

[0204] This invention deals with a method for transmitting a HARQ-ACK of a PDSCH when the PDSCH is scheduled using multiple slot scheduling.

[0205] Figure 18 shows a candidate for a downlink shared channel corresponding to HARQ-ACK when an uplink control channel is transmitted in the nth slot according to one embodiment of the present invention.

[0206] In an NR wireless communication system, a terminal can signal whether it has successfully received a downlink signal or channel by transmitting a codebook containing hybrid automatic repeat request (HARQ)-ACK information. A HARQ-ACK codebook contains one or more bits indicating whether it has successfully received a downlink channel or signal. Here, the downlink channel may include at least one of the following: a physical downlink shared channel (PDSCH), a semi-persistence scheduling (SPS) PDCSH, and a PDCCH that releases an SPS PDSCH. HARQ-ACK codebooks can be distinguished into semi-static and dynamic HARQ-ACK codebooks. A base station can configure a terminal with one of two HARQ-ACK codebooks. The terminal can then use the HARQ-ACK codebook configured for it.

[0207] Type-1 HARQ-ACK Codebook

[0208] Let's assume that the terminal is set to K1 values ​​of 1 and 2. When the TDRA table is set as shown in Table 4 above, the PDSCH candidates corresponding to the HARQ-ACK to be sent in the PUCCH when a PUCCH is sent in slot n are shown in Figure 18.

[0209] When a Type-1 HARQ-ACK codebook (semi-static HARQ-ACK codebook) is used, the base station can use the RRC signal to set the number of bits in the HARQ-ACK codebook and whether each bit in the HARQ-ACK codebook indicates whether the reception of a channel or signal was successful. Therefore, the base station does not need to signal the terminal with the information necessary to transmit the HARQ-ACK codebook each time it is required.

[0210] More specifically, the method for generating a Type-1 HARQ-ACK codebook is as follows: Here, a Type-1 HARQ-ACK codebook is sent in slot n.

[0211] 1) Let K1_set be the set of possible K1 values. Take the largest K1 value from K1_set. Let's call this K1_max. Remove this K1 value from K_set.

[0212] 2) Let R be the set of PDSCH candidates that can be received in slot n-K1_max. Here, each PDSCH candidate in set R has a start symbol and length that are received in the slot according to the TDRA table. If the symbol of a PDSCH candidate in set R overlaps with the symbol configured with the uplink in a semi-static UL / DL configuration, the PDSCH candidate is excluded from set R.

[0213] 3) The terminal performs steps A and B on the PDSCH candidates included in R.

[0214] A) Assign a new HARQ-ACK occasion to the PDSCH candidate in set R whose last symbol is the earliest. Then, if there is a PDSCH candidate in set R whose last symbol overlaps with the earliest PDSCH candidate by at least one symbol, assign the same HARQ-ACK occasion to that PDSCH candidate. The PDSCH candidates to which the HARQ-ACK occasion has been assigned (the PDSCH candidate whose last symbol is the earliest, and the PDSCH candidates that overlap with that PDSCH candidate by at least one symbol) are removed from set R.

[0215] B) Repeat step 3-A until the set R becomes an empty set.

[0216] 4) Repeat steps 1), 2), and 3) above until K1_set becomes an empty set.

[0217] The terminal can generate a type-1 HARQ-ACK codebook based on the HARQ-ACK occasion. If the terminal receives a DCI to schedule a PDSCH, or receives an SPS (semi-persistent scheduling) PDSCH, the HARQ-ACK information for the PDSCH can be transmitted in the HARQ-ACK occasion of that PDSCH. If no PDSCHs corresponding to a given HARQ-ACK occasion are received, the HARQ-ACK occasion may be set to NACK.

[0218] For reference, the HARQ-ACK occasion may contain one bit of ACK / NACK, or multiple bits of ACK / NACK. For example, if a PDSCH contains one TB, the HARQ-ACK occasion may contain one bit of ACK / NACK, and if a PDSCH contains two TBs, the HARQ-ACK occasion may contain two bits of ACK / NACK. Furthermore, if CBG (code block group) based PDSCH reception is configured on the terminal, the HARQ-ACK occasion may contain ACK / NACK corresponding to the maximum number of CBGs that a single PDSCH may contain.

[0219] In the following, for the sake of explanation, we will assume that there is 1 bit per HARQ-ACK occasion.

[0220] The problem that this invention aims to solve concerns a method for generating a Type-1 HARQ-ACK codebook (semistatic HARQ-ACK codebook) when a PDSCH is scheduled using multiple slot scheduling.

[0221] First embodiment: PDSCH candidate base in a slot

[0222] The first embodiment of the present invention is a method of converting a PDSCH scheduled by multi-slot scheduling into PDSCH candidates for each slot, and generating a type-1 HARQ-ACK codebook using the PDSCH candidates in each slot. More specifically, the method for generating a type-1 HARQ-ACK codebook according to the first embodiment is as follows.

[0223] 1) First stage: Let the set of K1 values that can be indicated be K1_set. Based on the K1_set and the TDRA table, the terminal can determine the index of the slot in which the PDSCH candidate to be included in the Type-1 HARQ-ACK codebook is received. Let such a set of indexes be K_slot.

[0224] More specifically, the method for determining the index set K_slot is as follows. One K1 value can be selected from K1_set. Let the selected K1 value be K1_a. Based on the K1_a value and the TDRA table, the terminal can determine in which slot the PDSCH should be received. For example, when the TDRA table includes PDSCH allocation information for up to N consecutive slots, it can be determined that the PDSCH allocation information is for slots n-K1_a-(N-1), slot n-K1_a-(N-2),..., slot n-K1_a. Therefore, the K_slot set may include {K1_a+(N-1), K1_a+(N-2),..., K1_a}. (For reference, the TDRA table may include PDSCH allocation information for non-consecutive slots. In this case, N is the number from the first scheduled slot to the last scheduled slot among the slots scheduled in the TDRA table, and slots that are not scheduled in the TDRA table among slots from slot n-K1_a-(N-1) to slot n-K1_a may be excluded.

[0225] In this way, for all K1 values ​​in K1_set, the index of the slot in which a PDSCH candidate can be received can be obtained, and these indices can be collected and included in the K_slot set.

[0226] 2) Second stage: Extract the maximum K1 value from K_slot. Let's call this K1_max. This K1 value is then removed from K_slot.

[0227] 3) Third stage: Let R be the set of PDSCH candidates that can be received in slot n-K1_max. If the symbol of a PDSCH candidate included in set R overlaps with the symbol configured with the uplink in the semi-static UL / DL setting, the PDSCH candidate is excluded from set R.

[0228] The PDSCH candidates included in the set R can be determined as follows: One K1 value can be selected from K1_set. Let's call the selected K1 value K1_a. Based on the K1_a value and the TDRA table, the terminal can determine the PDSCH candidates for slot n-K1_max. For example, if one entry in the TDRA table contains PDSCH assignment information for M consecutive slots, it can be determined that this is PDSCH assignment information for slot n-K1_a-(M-1), slot n-K1_a-(M-2), ..., slot n-K1_a. If one of the slots n-K1_a-(M-1), slot n-K1_a-(M-2), ..., slot n-K1_a is slot n-K1_max, then the PDSCH candidates included in that slot can be included in the set R. The above process may be performed for all entries in the TDRA table, and for all K1 values ​​in K1_set.

[0229] 4) Stage 4: The terminal performs steps A and B on the PDSCH candidates included in R.

[0230] A) Assign a new HARQ-ACK occasion to the PDSCH candidate in set R whose last symbol is the earliest. Then, if there is a PDSCH candidate in set R whose last symbol overlaps with the PDSCH candidate with the earliest symbol by at least one symbol, assign the same HARQ-ACK occasion to that PDSCH candidate. The PDSCH candidates to which the HARQ-ACK occasion has been assigned (the PDSCH candidate whose last symbol is the earliest, and the PDSCH candidates that overlap with that PDSCH candidate by at least one symbol) are removed from set R.

[0231] B) Repeat step 4-A until the set R becomes an empty set.

[0232] 5) Stage 5: Repeat stages 2, 3, and 4 until K1_slot becomes an empty set.

[0233] Figure 19 shows a HARQ-ACK occasion according to one embodiment of the present invention.

[0234] Referring to Figure 19, PDSCHs scheduled with multi-slot scheduling may be converted into PDSCH candidates for each slot, and a type-1 HARQ-ACK codebook may be generated using the PDSCH candidates in each slot.

[0235] Specifically, as shown in Figure 19, a type-1 HARQ-ACK codebook may be generated through the following five steps.

[0236] 1) First stage: The terminal has been set to K1 values ​​of 1 and 2, so K1_set={1,2}. The terminal can determine K1_slot through the following process.

[0237] A single value may be selected from K1_set. For example, if the value K1_a selected from K1_set is "2", the TDRA table contains PDSCH assignment information for a maximum of N=4 consecutive slots. Therefore, the terminal can determine that the PDSCH assignment information is for slots n-K1_a-(N-1)=n-2-(4-1)=n-5, n-K1_a-(N-2)=n-2-(4-2)=n-4, n-K1_a-(N-3)=n-2-(4-3)=n-3, and n-K1_a=n-2. Thus, K1_slot contains {5,4,3,2}.

[0238] Subsequently, one more value is selected from K1_set. If the selected value K1_a is "1", the terminal can determine that the entry in the TDRA table contains PDSCH assignment information for a maximum of N=4 consecutive slots, and therefore the terminal can determine that it contains PDSCH assignment information for slots n-K1_a-(N-1)=n-1-(4-1)=n-4, n-K1_a-(N-2)=n-1-(4-2)=n-3, n-K1_a-(N-3)=n-1-(4-3)=n-2, and n-K1_a=n-1. Thus, K1_slot contains {4,3,2,1}.

[0239] Therefore, K1_slot contains {5,4,3,2,1}.

[0240] 2) Second stage: Select the maximum value K1_max=5 from the K1_slot. The K1 value is then removed from K_slot.

[0241] 3) Third stage: Let R be the set of PDSCH candidates that can be received in slot n-K1_max=n-5. If the symbol of a PDSCH candidate included in set R overlaps with the symbol configured with the uplink in the semi-static UL / DL setting, the PDSCH candidate is excluded from set R. Here, we assume that all symbols are downlink symbols.

[0242] The PDSCH candidates included in the set R in slot n-5 can be determined as follows:

[0243] Select one value from K1_set. Let's say this is K1_a=2. Entries 3, 4, and 5 in the TDRA table contain PDSCH assignment information for four consecutive slots: slot n-K1_a-(M-1)=n-5, slot n-K1_a-(M-2)=n-4, ..., slot n-K1_a=n-2. The remaining entries 0, 1, 2, 6, 7, 8, 9, 10, and 11 contain PDSCH assignment information for two consecutive slots: slot n-3 and slot n-2. Therefore, entries 3, 4, and 5 in the TDRA table contain PDSCH candidates for slot n-K1_max=n-5, and the PDSCH candidates included in the said slot may be included in the set R. That is, the set R of PDSCH candidates that can be received in slot n-K1_max=n-5 includes the following: The set R may include {(S=0,L=14), (S=0,L=7), and (S=7,L=7)}. For reference, here, (S=0,L=14) is a candidate for PDSCH in slot n-5 in entry 3 of the TDRA table, (S=0,L=7) is a candidate for PDSCH in slot n-5 in entry 4 of the TDRA table, and (S=7,L=7) is a candidate for PDSCH in slot n-5 in entry 5 of the TDRA table.

[0244] Select the remaining value from K1_set. Let's call this K1_a=1. Entries 3, 4, and 5 in the TDRA table contain PDSCH assignment information for four consecutive slots: slot n-K1_a-(M-1)=n-4, slot n-K1_a-(M-2)=n-3, ..., slot n-K1_a=n-1. The remaining entries 0, 1, 2, 6, 7, 8, 9, 10, and 11 contain PDSCH assignment information for two consecutive slots: slot n-2 and slot n-1. Therefore, the slot corresponding to K1_a=1 does not overlap with slot n-K1_max=n-5, and there are no PDSCH candidates to include in set R.

[0245] Therefore, R = {(S = 0, L = 14), (S = 0, L = 7), (S = 7, L = 7)}.

[0246] 4) Fourth stage: The terminal performs the following step A and step B for the PDSCH candidates included in R.

[0247] A) Assign HARQ-ACK occasion 0 to the PDSCH candidate in the set R with the earliest last symbol (S = 0, L = 7). And assign the same HARQ-ACK occasion to the PDSCH candidate (S = 0, L = 14) in the set R that overlaps with the PDSCH candidate (S = 0, L = 7) with the earliest last symbol by even one symbol. Exclude the PDSCH candidates (S = 0, L = 7) and (S = 0, L = 14) to which the HARQ-ACK occasion is assigned from the set R. Therefore, the set R = {(S = 7, L = 7)}.

[0248] B) Repeat the 4-A step until the set R becomes an empty set.

[0249] Since the set R is not an empty set, repeat the 4-A step again. By the 4-A step, HARQ-ACK occasion 1 is assigned to the PDSCH candidate (S = 7, L = 7), and the set R becomes an empty set. Thus, the fourth stage ends.

[0250] 5) Fifth stage: Repeat the second / third / fourth stages until K1_slot becomes an empty set.

[0251] K1_slot = {4, 3, 2, 1} and it is not an empty set. Since it is not an empty set, repeat the second / third / fourth stages again.

[0252] By the above stages, the PDSCH candidates and HARQ-ACK occasions are determined as follows.

[0253] HARQ-ACK occasion 0: PDSCH candidates for slot n-5 (S=0, L=7), (S=0, L=14)

[0254] HARQ-ACK occasion 1: PDSCH candidate for slot n-5 (S=7, L=7)

[0255] HARQ-ACK occasion 2: PDSCH candidates for slot n-4 (S=0, L=7), (S=0, L=14)

[0256] HARQ-ACK occasion 3: PDSCH candidate for slot n-4 (S=7, L=7)

[0257] HARQ-ACK occasion 4: PDSCH candidates for slot n-3 (S=0, L=7), (S=0, L=14)

[0258] HARQ-ACK occasion 5: PDSCH candidate for slot n-3 (S=7, L=7)

[0259] HARQ-ACK occasion 6: PDSCH candidates for slot n-2 (S=0, L=7), (S=0, L=14)

[0260] HARQ-ACK occasion 7: PDSCH candidate for slot n-2 (S=7, L=7)

[0261] HARQ-ACK occasion 8: PDSCH candidates for slot n-1 (S=0, L=7), (S=0, L=14)

[0262] HARQ-ACK occasion 9: PDSCH candidate for slot n-1 (S=7, L=7)

[0263] Therefore, a Type-1 HARQ-ACK codebook may consist of 10 HARQ-ACK occasions.

[0264] For example, let's assume that the DCI received by the terminal indicates entry 4 in the TDRA table and K1=2. In this case, the terminal receives the first PDSCH (S=0,L=7) in slot n-5, the second PDSCH (S=0,L=7) in slot n-4, the third PDSCH (S=0,L=7) in slot n-3, and the fourth PDSCH (S=0,L=7) in slot n-2. The terminal includes the HARQ-ACK(o1) of the first PDSCH in HARQ-ACK occasion 0, the HARQ-ACK(o2) of the second PDSCH in HARQ-ACK occasion 2, the HARQ-ACK(o3) of the third PDSCH in HARQ-ACK occasion 4, and the HARQ-ACK(o4) of the fourth PDSCH in HARQ-ACK occasion 6. Therefore, the Type-1 HARQ-ACK codebook is [o1N o2N o3N o4N NN], where N stands for NACK.

[0265] Furthermore, let's assume that the DCI received by the terminal indicates entry 5 in the TDRA table and K1=1. In this case, the terminal receives the 5th PDSCH (S=7,L=7) in slot n-4, the 6th PDSCH (S=7,L=7) in slot n-3, the 7th PDSCH (S=7,L=7) in slot n-2, and the 8th PDSCH (S=7,L=7) in slot n-1. The terminal includes the HARQ-ACK(o5) of the 5th PDSCH in HARQ-ACK occasion 3, the HARQ-ACK(o6) of the 6th PDSCH in HARQ-ACK occasion 5, the HARQ-ACK(o7) of the 7th PDSCH in HARQ-ACK occasion 7, and the HARQ-ACK(o8) of the 8th PDSCH in HARQ-ACK occasion 9. Therefore, the Type-1 HARQ-ACK codebook is [o1N o2o5o3o6o4o7N o8], where N stands for NACK.

[0266] In the first embodiment of the present invention, a HARQ-ACK occasion is created using a PDSCH candidate in each slot. However, since one DCI can schedule PDSCHs in multiple slots, creating a HARQ-ACK occasion using a PDSCH candidate in each slot may be inefficient. For example, referring to Figure 19, a terminal may schedule up to eight PDSCHs in any case. This is the case as follows:

[0267] (TDRA table entry 4 and K1=2, TDRA table entry 5 and K1=2)

[0268] (TDRA table entry 4 and K1=2, TDRA table entry 5 and K1=1)

[0269] (TDRA table entry 4 and K1=1, TDRA table entry 5 and K1=2)

[0270] (TDRA table entry 4 and K1=1, TDRA table entry 5 and K1=1)

[0271] Therefore, the type-1 HARQ-ACK codebook transmitted by the terminal should contain eight HARQ-ACK occasions. However, as mentioned earlier, in this case, it contains ten HARQ-ACK occasions. Two of the HARQ-ACK occasions are not always used to transmit HARQ-ACK information.

[0272] Second embodiment: PDSCH candidate base in all slots

[0273] A second embodiment of the present invention is a method for generating a type-1 HARQ-ACK codebook using PDSCH candidates in all slots. More specifically, the type-1 HARQ-ACK codebook generation method according to the second embodiment is as follows:

[0274] 1) First stage: The terminal may include a set of PDSCH candidate pairs that can be scheduled in set R. Here, a PDSCH candidate pair is a collection of PDSCH candidates that can be scheduled by one entry in the TDRA table. Therefore, a PDSCH candidate pair represents a PDSCH candidate that can be scheduled to be received in multiple slots. If the symbols of the PDSCH candidates included in a PDSCH candidate pair included in set R overlap with the symbols configured with the uplink in a semi-static UL / DL setting, the PDSCH candidate is excluded from the PDSCH candidate pair. If all PDSCH candidates are excluded for a given PDSCH candidate pair, the PDSCH candidate pair is excluded from set R.

[0275] 2) Second stage: The terminal performs steps A and B for the PDSCH candidate pairs included in set R.

[0276] A) Select one PDSCH candidate pair from the PDSCH candidate pairs in set R. Assign a new HARQ-ACK occasion to that PDSCH candidate pair. Then, if there is another PDSCH candidate pair in set R that overlaps with that PDSCH candidate pair by even one symbol, assign the same HARQ-ACK occasion to that PDSCH candidate pair. Remove the PDSCH candidate pair to which the HARQ-ACK occasion has been assigned from set R.

[0277] B) Repeat step 2-A until the set R becomes an empty set.

[0278] Unlike the first embodiment, in the second embodiment, a terminal corresponds to a PDSCH candidate pair for each HARQ-ACK occasion. Each PDSCH candidate pair may contain a different number of PDSCH candidates. Therefore, the number of PDSCH candidates that a single HARQ-ACK occasion should represent may differ. To this end, the number of PDSCH candidates that a HARQ-ACK occasion should represent is determined based on the maximum number of PDSCH candidates among the PDSCH candidate pairs corresponding to a single HARQ-ACK occasion.

[0279] In stage 2-A, the terminal must select one PDSCH candidate pair from the set R. To do this, at least the following methods or a combination of the following methods may be considered.

[0280] As a first method, a pair of PDSCH candidate candidates can be selected that includes the PDSCH candidate with the earliest start time. This allows for the priority assignment of the HARQ-ACK occasion to the PDSCH candidate with the earliest time point.

[0281] As a second method, the PDSCH candidate pair with the earliest completion time can be selected. This allows the HARQ-ACK occasion to be preferentially assigned to the PDSCH candidate that completes earliest in terms of time.

[0282] A third method allows for the selection of PDSCH candidate pairs with the fewest symbols. This minimizes the likelihood of overlap with other PDSCH candidate pairs.

[0283] A fourth method allows us to select the PDSCH candidate pair with the largest number of symbols. This eliminates a large number of PDSCH candidates from the set R because it overlaps with the PDSCH candidate pair with the largest number of symbols.

[0284] A fifth method involves selecting the PDSCH candidate pair with the largest number of slots. As mentioned earlier, the HARQ-ACK occasion is determined by the number of PDSCH candidates in the PDSCH candidate pair, so we can search for PDSCH candidate pairs with fewer slots that overlap with the PDSCH candidate pair with more slots.

[0285] A sixth method is to select the PDSCH candidate pair with the lowest index in the TDRA table. This may be set when the base station configures the TDRA table.

[0286] Figure 20 shows a time domain bundling window according to one embodiment of the present invention.

[0287] Time domain bundling

[0288] The terminal may be configured for time-domain bundling when generating a Type-1 HARQ-ACK codebook. Time-domain bundling is a method of bundling the HARQ-ACKs of each PDSCH into a single HARQ-ACK bit (generating the HARQ-ACKs as a single HARQ-ACK bit using a binary 'AND' operation; that is, if all the HARQ-ACKs are ACKs, one HARQ-ACK bit is an ACK; otherwise, one HARQ-ACK bit is a NACK) and transmitting it. Here, the PDSCHs may be PDSCHs in the same slot or PDSCHs in different slots. Here, the PDSCHs are PDSCHs scheduled in one DCI and are adjacent PDSCHs when the PDSCHs are aligned in time. For example, if a single DCI has PDSCHs scheduled as PDSCH#0 in slot n, PDSCH#1 in slot n+1, PDSCH#2 in slot n+2, and PDSCH#3 in slot n+3, the terminal can bundle the HARQ-ACKs of {PDSCH#0 in slot n, PDSCH#1 in slot n+1} into one HARQ-ACK bit, and bundle the HARQ-ACKs of {PDSCH#2 in slot n+2, PDSCH#3 in slot n+3} into one HARQ-ACK bit. Therefore, although four HARQ-ACK bits are generated by the four PDSCHs, only two HARQ-ACK bits may be transmitted due to time-domain bundling.

[0289] For time-domain bundling, the terminal may be configured with at least one of the following pieces of information from the base station:

[0290] As first information, the base station can set the number of PDSCH HARQ-ACKs (or the number of PDSCHs) to bundle for time-domain bundling. bundle Let's assume that the above N bundle The value can be one of 2, 4, or 8. bundle When this setting is enabled, the device will be N bundleThe HARQ-ACKs of each PDSCH are bundled into a single HARQ-ACK bit and sent. Let's assume that M PDSCHs are scheduled on one DCI at a terminal. If M is N bundle If it is a multiple of (M mod N) bundle =0), the terminal is N bundle Each PDSCH is combined to generate one bundled HARQ-ACK, and the total M / N bundle It is possible to generate bundled HARQ-ACKs. However, if M is N bundle If it is not a multiple of (M mod N) bundle >0), the terminal can group PDSCH as follows. For reference, here PDSCH#0, PDSCH#1, ..., PDSCH#(M-1) are arranged in chronological order.

[0291] As the first method, N in chronological order bundle The individual PDSCHs are combined to generate a single bundled HARQ-ACK. Assuming there are N remaining PDSCHs... bundle If the number is less than the specified number, the remaining PDSCHs are grouped together to generate a single bundled HARQ-ACK. More specifically, {PDSCH#0,PDSCH#1,…,PDSCH#(N bundle Combine the -1)} to generate a single bundled HARQ-ACK. {PDSCH#(N bundle ),PDSCH#(N bundle +1), ..., PDSCH#(2*N bundle Combine the -1)} to generate a single bundled HARQ-ACK. Continue bundling in this manner, {PDSCH#(floor(M / N bundle )*N bundle ),PDSCH#(floor(M / N bundle )*N bundle The +1), ..., PDSCH#(M-1)} are combined to generate a single bundled HARQ-ACK. As a result, the total ceil(M / N bundle The bundled HARQ-ACK bits are generated.

[0292] As a second method, PDSCH can be grouped in chronological order and K = ceil(M / N bundle ) groups can be formed. The PDSCHs included in the group may be ceil(M / K) or floor(M / K). The ceil(M / K) PDSCHs can be grouped together in chronological order to form M mod K groups, and the next ceil(M / K) PDSCHs can be grouped together to form K-(M mod K) groups. The HARQ-ACKs within the group can be bundled to generate one bundled HARQ-ACK, resulting in a total of ceil(M / N bundle ) bundled HARQ-ACK bits are generated.

[0293] As a second piece of information, the base station may be configured with the number of bundled HARQ-ACKs (or the number of PDSCH groups) after time-domain bundling. group Let's assume that the above N group The value can be one of 2, 4, or 8. group When configured, the terminal groups M PDSCHs together to form N group You can create a PDSCH group of this size. For reference, M is N group If it is smaller than, combine one PDSCH to form M PDSCH groups, and then the next N group -M groups do not include PDSCH. HARQ-ACKs for groups that do not include PDSCH may be set to NACK. HARQ-ACKs for groups that do not include PDSCH do not need to be sent to the base station.

[0294] As the first method, K=ceil(M / N) in chronological order group) PDSCHs are grouped together to generate one bundled HARQ-ACK. If the number of remaining PDSCHs is less than K, the remaining PDSCHs are grouped together to generate one bundled HARQ-ACK. More specifically, {PDSCH#0,PDSCH#1,…,PDSCH#(K-1)} are grouped together to generate one bundled HARQ-ACK. {PDSCH#(K),PDSCH#(K+1),…,PDSCH#(2*K-1)} are grouped together to generate one bundled HARQ-ACK. This grouping continues until {PDSCH#(floor(M / K)*K),PDSCH#(floor(M / K)*K+1),…,PDSCH#(M-1)} are grouped together to generate one bundled HARQ-ACK. As a result, a total of N group The bundled HARQ-ACK bits are generated.

[0295] As a second method, group PDSCH in chronological order N group A group can be formed. The PDSCH included in the group is ceil(M / N group ) or floor(M / N group There may be ) items. In chronological order, ceil(M / N group ) PDSCHs combined into M mod N group Create individual groups, and then, in chronological order, floor(M / N group ) PDSCHs are grouped together N group -(M mod N group ) groups can be created. The HARQ-ACKs within the group can be bundled to generate a single bundled HARQ-ACK, resulting in a total of N group The bundled HARQ-ACK bits are generated.

[0296] As a third piece of information, the base station can set time intervals for time-domain bundling. These time intervals may be set in slot units. These time intervals can be called bundling windows. N slot Let's assume the terminal is N slot PDSCHs contained in individual slots can be grouped together into one group. If there is at least one PDSCH in the group, the terminal can bundle the HARQ-ACKs of the PDSCH into one HARQ-ACK. HARQ-ACKs of groups that do not contain PDSCHs may be set to NACK. HARQ-ACKs of groups that do not contain PDSCHs do not need to be transmitted to the base station. The terminal can then... slot The number of slots can be determined as follows:

[0297] As the first method, the terminal starts from frame slot 0 and continues through N consecutive frames. slot The PDSCHs contained in each slot can be grouped together to form a group. That is, slot i*N slot Slot i*N slot +1, ..., slot(i+1)*N slot The PDSCH elements included in -1 can be grouped together, where i is an integer.

[0298] As a second method, the terminal takes a continuous N from slot k of the frame. slot The PDSCHs contained in each individual slot can be grouped together. That is, slot i*N slot +k, slot i*N slot +k+1, ..., slot(i+1)*N slotPDSCHs included in -1+k can be grouped together. For reference, PDSCHs included in slot 0, slot 1, ..., slot k-1 can be grouped together into one group. Here, i is an integer. Here, k may be a value set by the base station on the terminal, a value determined based on the index of the slot in which the first PDSCH is scheduled, a value determined based on the index of the slot in which the PDCCH scheduling the PDSCH is transmitted, or a value determined based on the index of the slot in which the PUCCH containing the HARQ-ACK of the PDSCH is transmitted.

[0299] For example, let X be a value determined based on the index of the slot in which the first PDSCH is scheduled. Then k = X is acceptable. Since the first PDSCH is scheduled in slot 3, N can be found from slot 3. slot =The PDSCHs contained in the four slots, slots 3, 4, 5, and 6, are grouped together into one group, and the next N slot The four slots, slots 7, 8, 9, and 10, can be grouped together into a single group.

[0300] For example, if X is a value determined based on the index of the slot from which the PDCCH that schedules the PDSCH is transmitted, then k may be X. Since the PDCCH is scheduled for slot 1, from slot 1 to N slot =The PDSCHs contained in the four slots, slot 1, slot 2, slot 3, and slot 4, are grouped together into one group, and the next N slot The four slots, slots 5, 6, 7, and 8, can be grouped together into a single group.

[0301] For example, if X is the index of the slot to which the PUCCH containing the HARQ-ACK of the PDSCH is transmitted, then k = X mod N slotThis is acceptable. Since PUCCH is scheduled for slot 10, k=10 mod 4=2, and therefore, from slot 2 to N slot =The PDSCHs contained in the four slots, slot 2, slot 3, slot 4, and slot 5, are grouped together into one group, and the next N slot The four slots, slots 6, 7, 8, and 9, can be grouped together into a single group.

[0302] For example, as shown in Figure 20, N slot When is set to "3" and k=n-5, a bundling window may be set by grouping three slots together starting from slot n-5. That is, slots n-5, n-4, and n-3 are included in one bundling window (bundling window#A), and slots n-2, n-1, and n are included in another bundling window (bundling window#B). Therefore, one bundled HARQ-ACK bit may be generated for all PDSCHs included in bundling window#A, and one bundled HARQ-ACK bit may be generated for all PDSCHs included in bundling window#B.

[0303] The problem that this invention aims to solve concerns a method for a terminal to generate a type-1 HARQ-ACK codebook when the aforementioned time-domain bundling is configured on the terminal.

[0304] For illustrative purposes, the present invention assumes that the terminal generates a group of PDSCHs based on the first information, the second information, or the third information. For convenience, let's denote the PDSCHs included in the group as {PDSCH#n, PDSCH#(n+1), ..., PDSCH#(n+k-1)}. The number of PDSCHs included in the group is k.

[0305] In a preferred first embodiment of the present invention, a terminal can select one of the PDSCHs included in the group as a representative. A Type-1 HARQ-ACK codebook can be generated based on the SLIV corresponding to the PDSCH.

[0306] The method for selecting one of the PDSCHs included in the group as a representative may include at least one of the following:

[0307] As a first method, we can select the PDSCH that is earliest in time from among the PDSCHs included in the group. For example, if the PDSCHs included in the group are {PDSCH#n, PDSCH#(n+1), ... PDSCH#(n+k-1)}, we can select PDSCH#n.

[0308] As a second method, we can select the PDSCH with the latest time interval from among the PDSCHs included in the group. For example, if the PDSCHs included in the group are {PDSCH#n, PDSCH#(n+1), ... PDSCH#(n+k-1)}, then we can select PDSCH#(n+k-1).

[0309] A third method allows selecting the PDSCH that occupies the most symbols among the PDSCHs included in the group. If multiple PDSCHs occupy the same number of symbols, then the earliest or latest PDSCH in terms of time can be selected.

[0310] A fourth method allows selecting the PDSCH with the fewest symbols among those included in the group. If multiple PDSCHs occupy the same number of symbols, then the earliest or latest PDSCH in terms of time can be selected.

[0311] As a fifth method, in the first, second, third, and fourth methods described above, PDSCHs in which at least one symbol overlaps with a UL symbol due to the semi-static UL / DL setting may be excluded.

[0312] Figure 21 shows a representative PDSCH with a time-domain bundling window according to one embodiment of the present invention.

[0313] As shown in Figure 21, the terminal receives the aforementioned second information N slot When the value of k is set to "3" and the value of k is "n-5", a bundling window may be set by grouping three slots together, starting from slot n-5. For example, slots n-5, n-4, and n-3 are included in one bundling window (bundling window#A), while slots n-2, n-1, and n are included in another bundling window (bundling window#B). The terminal can select the PDSCH candidate with the latest time interval from among the PDSCH candidates in the bundling window as the representative PDSCH (representative SLIV). For example, if the K1 value is 2 and the TDRA index=3, four PDSCH candidates may be scheduled in slots n-5, n-4, n-3, and n-2. Of these, the first three PDSCH candidates (the PDSCH candidates scheduled in slots n-5, n-4, and n-3) belong to bundling window#A. Therefore, among the PDSCH candidates, the PDSCH candidate in slot n-3, which is the latest in terms of time, can be selected as the representative PDSCH (representative SLIV). Then, one PDSCH candidate (the PDSCH candidate scheduled for slot n-2) belongs to bundling window #B. Therefore, among the PDSCH candidates, the PDSCH candidate in slot n-2, which is the latest in terms of time, can be selected as the representative PDSCH (representative SLIV). The representative PDSCH (representative SLIV) selected in this way is shown in Figure 20.

[0314] In the following explanation, the selected PDSCH (and its corresponding SLIV) will be referred to as the representative PDSCH (or representative SLIV). One representative PDSCH (or representative SLIV) is determined for each group. The terminal can generate a type-1 HARQ-ACK CB based on the representative SLIV as follows:

[0315] 1) First stage: Let K1_set be the set of possible K1 values. Based on the K1_set and the TDRA table, the terminal can determine the index of the slot in which the representative PDSCH candidate (representative SLIV candidate) is received. Let K_slot be the set of such indices.

[0316] 2) Second stage: Extract the maximum K1 value from K_slot. Let's call this K1_max. This K1 value is then removed from K_slot.

[0317] 3) Third stage: Let R be the set of representative PDSCH candidates (representative SLIV candidates) that can be received in slot n-K1_max. If the symbol of a representative PDSCH candidate (representative SLIV candidate) included in set R overlaps with the symbol configured with the uplink in the semi-static UL / DL setting, the representative PDSCH candidate (representative SLIV candidate) is excluded from set R.

[0318] The representative PDSCH candidate (representative SLIV candidate) included in the set R can be determined as follows: One K1 value can be selected from K1_set. Let the selected K1 value be K1_a. Based on the K1_a value and the TDRA table, the terminal can determine the representative PDSCH candidate (representative SLIV candidate) for slot n-K1_max.

[0319] 4) Stage 4: The terminal performs steps A and B on the representative PDSCH candidate (representative SLIV candidate) included in R.

[0320] A) The representative PDSCH candidate (representative SLIV candidate) in set R whose last symbol is earliest is assigned a new HARQ-ACK occasion. Then, in set R, if there is a representative PDSCH candidate (representative SLIV candidate) whose last symbol overlaps with the said representative PDSCH candidate (representative SLIV candidate) by at least one symbol, that representative PDSCH candidate (representative SLIV candidate) is assigned the same HARQ-ACK occasion. The representative PDSCH candidate (representative SLIV candidate) to which the HARQ-ACK occasion has been assigned (the representative PDSCH candidate (representative SLIV candidate) whose last symbol is earliest, and the representative PDSCH candidate (representative SLIV candidate) that overlaps with that representative PDSCH candidate (representative SLIV candidate) by at least one symbol) is removed from set R.

[0321] B) Repeat step 4-A until the set R becomes an empty set.

[0322] 5) Stage 5: Repeat stages 2, 3, and 4 until K1_slot becomes an empty set.

[0323] 6) Stage 6: The terminal can assign the B HARQ-ACK bit to a candidate representative PDSCH (representative SLIV candidate) that has been assigned the same HARQ-ACK occasion. Here, B is the maximum number of PDSCHs in the group that includes the candidate representative PDSCH (representative SLIV candidate) that has been assigned the same HARQ-ACK occasion.

[0324] Figure 22 shows a HARQ-ACK occasion according to a time-domain bundling window in one embodiment of the present invention.

[0325] Referring to Figure 22, in the above-described embodiment, the representative PDSCH candidate (representative SLIV candidate) can be determined by Figure 21.

[0326] 1) First stage: The terminal has been set to K1 values ​​of 1 and 2, so K1_set={1,2}. When the K1 value is 2, the representative PDSCH candidate (representative SLIV candidate) is located in slot n-3 and slot n-2. Therefore, the K1 values ​​of the said slots are 3 and 2. These two values ​​may be included in K1_slot. When the K1 value is 1, the representative PDSCH candidate (representative SLIV candidate) is located in slot n-3 and slot n-1. Therefore, the K1 values ​​of the said slots are 3 and 1. These two values ​​may be included in K1_slot. Therefore, K1_slot is {1,2,3}.

[0327] 2) Second stage: Select the maximum value K1_max=3 from the K1_slot. The K1 value is then removed from K_slot.

[0328] 3) Third stage: Let R be the set of representative PDSCH candidates (representative SLIV candidates) that can be received in slot n-K1_max=n-3. If the symbol of a representative PDSCH candidate (representative SLIV candidate) included in set R overlaps with the symbol configured with the uplink in the semi-static UL / DL setting, then the representative PDSCH candidate (representative SLIV candidate) is excluded from set R. Here, we assume that all symbols are downlink symbols.

[0329] In slot n-3, the representative PDSCH candidates (representative SLIV candidates) included in the set R are R={(S=0,L=14), (S=0,L=7), (S=7,L=7)}.

[0330] 4) Stage 4: The terminal performs steps A and B on the representative PDSCH candidate (representative SLIV candidate) included in R.

[0331] A) Among the representative PDSCH candidates in set R, the last symbol of the earliest representative PDSCH candidate (representative SLIV candidate), (S=0,L=7), is assigned the HARQ-ACK occasion 0. Then, in set R, the representative PDSCH candidate (representative SLIV candidate), (S=0,L=14), which overlaps with the aforementioned last symbol of the earliest representative PDSCH candidate (representative SLIV candidate), (S=0,L=7), by at least one symbol, is assigned the same HARQ-ACK occasion. The representative PDSCH candidates (representative SLIV candidates) (S=0,L=7) and (S=0,L=14), to which the HARQ-ACK occasion was assigned, are removed from set R. Therefore, set R = {(S=7,L=7)}.

[0332] B) Repeat step 4-A until the set R becomes an empty set.

[0333] Since the set R is not empty, we repeat step 4-A. Step 4-A assigns the representative PDSCH candidate (representative SLIV candidate) (S=7, L=7) HARQ-ACK occasion 1, and the set R becomes empty. This completes step 4.

[0334] 5) Stage 5: Repeat stages 2, 3, and 4 until K1_slot becomes an empty set.

[0335] Since K1_slot = {2,1}, it is not an empty set. Because it is not an empty set, we repeat steps 2 / 3 / 4 again.

[0336] Based on the above steps, the PDSCH candidate and HARQ-ACK occasion are determined as follows.

[0337] HARQ-ACK occasion 0: Representative PDSCH candidates for slot n-3 (S=0, L=7), (S=0, L=14)

[0338] HARQ-ACK occasion 1: Representative PDSCH candidate for slot n-3 (S=7, L=7)

[0339] HARQ-ACK occasion 2: Representative PDSCH candidates for slot n-2 (S=0, L=7), (S=0, L=14)

[0340] HARQ-ACK occasion 3: Representative PDSCH candidate for slot n-2 (S=7, L=7)

[0341] HARQ-ACK occasion 4: Representative PDSCH candidates for slot n-1 (S=0, L=7), (S=0, L=14)

[0342] HARQ-ACK occasion 5: Representative PDSCH candidate for slot n-1 (S=7, L=7)

[0343] Therefore, a Type-1 HARQ-ACK codebook may consist of six HARQ-ACK occasions.

[0344] 6) Stage 6: The terminal determines the number of HARQ-ACK bits per HARQ-ACK occasion as follows:

[0345] The representative PDSCH candidates included in HARQ-ACK occasion 0 are (S=0,L=7) and (S=0,L=14). Within the bundling window, the TDRA indices to which these representative PDSCH candidates belong are 0, 1, 3, 4, 6, 7, 8, and 9 when K1=2, and 3 and 4 when K1=1. Of these, when K1=2 and the TDRA index is 3, there are the most PDSCH candidates (3) within the bundling window, so HARQ-ACK occasion 0 contains 3 HARQ-ACK bits. Using the same method, HARQ-ACK occasion 1 may contain 3 HARQ-ACK bits, HARQ-ACK occasion 2 may contain 1 HARQ-ACK bit, HARQ-ACK occasion 3 may contain 1 HARQ-ACK bit, HARQ-ACK occasion 4 may contain 2 HARQ-ACK bits, and HARQ-ACK occasion 5 may contain 2 HARQ-ACK bits.

[0346] Therefore, a type-1 HARQ-ACK codebook may contain a total of 12 HARQ-ACK bits.

[0347] Type-2 HARQ-ACK Codebook

[0348] The terminal may be configured with a type-2 HARQ-ACK codebook.

[0349] A Type-2 HARQ-ACK codebook may consist of two sub-codebooks.

[0350] The first subcodebook contains the HARQ-ACK bits for PDSCHs with TB (transport block) based transmission. Here, if a PDSCH with TB-based transmission is configured to contain one TB, one HARQ-ACK bit is generated per PDSCH; if it is configured to contain two TBs in at least one cell, two HARQ-ACK bits are generated per PDSCH. Therefore, P HARQ-ACK bits are generated per DCI that schedules TB-based transmission, where P is the maximum number of TBs contained in the PDSCH. For reference, if the number of TBs scheduled by a DCI is less than P, the HARQ-ACK bits corresponding to the missing number are set to NACK.

[0351] The second subcodebook includes the HARQ-ACK bit of the PDSCH transmitted via CBG (code block group). The terminal sends N per TB to cell c for the PDSCH transmitted via CBG. CBG,c It may be configured to include CBGs. For all cells where CBG-based transmission is configured, (# of TB in cell c)*N CBG,c The maximum value is N CBG,max Let's assume that the terminal schedules N CBG-based transmissions per DCI. CBG,max Generates a HARQ-ACK bit. For reference, the number of CBGs scheduled by DCI is N. CBG,max If the number is less than the required number, the HARQ-ACK bits corresponding to the missing number will be set to NACK.

[0352] The problem that this invention aims to solve is a method for determining which of the first subcodebook or the second subcodebook to use for transmission when multiple PDSCHs are scheduled in a single DCI.

[0353] As a first method of the present invention, when multiple PDSCHs are scheduled on a single DCI (multi-PDSCH scheduling), the terminal always transmits the HARQ-ACK of the PDSCH in a second subcodebook. Here, the second subcodebook may be modified as follows.

[0354] The second subcodebook includes PDSCHs transmitted via CBG (code block group) and the HARQ-ACK bits of multiple PDSCHs when scheduling multiple PDSCHs in DCI. The terminal sends N PDSCHs per TB to cell c via CBG-based transmission. CBG,c It may be configured to include CBGs. For all cells where CBG-based transmission is configured, (# of TB in cell c)*N CBG,c The maximum value is N CBG,max Let's assume that when multiple PDSCHs are scheduled in DCI, the maximum value of the number of PDSCHs scheduled by a single TDRA index is N. multi-PDSCH,max Let's go with that.

[0355] The terminal instructs the CBG-based transmission to send a maximum of (N) DCI per DCI. CBG,max ,N multi-PDSCH,max ) Generates a HARQ-ACK bit. The terminal sends max(N) to the DCI that instructs the multi-PDSCH scheduling. CBG,max ,N multi-PDSCH,max )Generates HARQ-ACK bits. Assuming the number of CBGs scheduled by DCI is max(N CBG,max ,N multi-PDSCH,max If the number of PDSCHs scheduled by the DCI instructing multi-PDSCH scheduling is less than max(N), then the HARQ-ACK bits corresponding to the missing number will be set to NACK. CBG,max ,N multi-PDSCH,max If the number is less than the number of missing HARQ-ACK bits, the corresponding HARQ-ACK bits will be set to NACK.

[0356] As a second method of the present invention, when a plurality of PDSCHs are scheduled by one DCI, the terminal selects and transmits the HARQ-ACK of the PDSCH by the number of the plurality of PDSCHs using a first sub-codebook or a second sub-codebook. Here, the first sub-codebook and the second sub-codebook may be modified as follows.

[0357] The first sub-codebook includes the HARQ-ACK bits of the PDSCH by TB (transport block)-based transmission, and when the number of the PDSCHs is X or less when a plurality of PDSCHs are scheduled by one DCI, the HARQ-ACK bits of the PDSCH are included. Here, assume that the PDSCH by TB-based transmission is set to include P transport blocks. Here, P is the maximum number of transport blocks included in the PDSCH. Therefore, max{P, X} HARQ-ACK bits are generated per DCI that schedules TB-based transmission. For reference, if the number of transport blocks scheduled by the DCI is less than max{P, X}, the HARQ-ACK bits corresponding to the insufficient number are set to NACK. Max{P, X} HARQ-ACK bits are generated per DCI that schedules TB-based transmission. For reference, the DCI that indicates multi-PDSCH scheduling includes PDSCHs of X or less. If the number of PDSCHs scheduled by the DCI that indicates multi-PDSCH scheduling is less than max{P, X}, the HARQ-ACK bits corresponding to the insufficient number are set to NACK.

[0358] The second sub-codebook includes the PDSCH by CBG (code block group)-based transmission and the HARQ-ACK bits of the plurality of PDSCHs when the number of the PDSCHs exceeds X when a plurality of PDSCHs are scheduled by DCI. The terminal may be set such that the PDSCH by CBG-based transmission includes N CBG,c code block groups per transport block in cell c. For all cells in which CBG-based transmission is set, the maximum value of (number of transport blocks in cell c) * N CBG,c is N CBG,maxLet's assume that when multiple PDSCHs are scheduled by DCI, the maximum value among the number of multiple PDSCHs scheduled by one TDRA index is N multi-PDSCH,max Let's assume that for reference, N multi-PDSCH,max is a value greater than X.

[0359] The terminal generates max(N CBG,max , N multi-PDSCH,max ) HARQ-ACK bits for each DCI that indicates the CBG-based transmission. The terminal generates max(N CBG,max , N multi-PDSCH,max ) HARQ-ACK bits for the DCI that indicates the multi-PDSCH scheduling. If the number of CBGs scheduled by the DCI is less than max(N CBG,max , N multi-PDSCH,max ), the HARQ-ACK bits corresponding to the insufficient number are set to NACK. If the number of PDSCHs scheduled by the DCI that indicates the multi-PDSCH scheduling is less than max(N CBG,max , N multi-PDSCH,max ), the HARQ-ACK bits corresponding to the insufficient number are set to NACK.

[0360] In the above embodiment, preferably, X = P may be determined. That is, if the multi-PDSCH scheduling DCI schedules less than or equal to P PDSCHs, the HARQ-ACK of the PDSCH is included in the first sub-codebook, and if the multi-PDSCH scheduling DCI schedules more than X PDSCHs, the HARQ-ACK of the PDSCH is included in the second sub-codebook.

[0361] The above two methods may be modified as follows when the type-2 HARQ-ACK codebook and time-domain bundling are set simultaneously.

[0362] As a modified second method of the present invention, when multiple PDSCHs are scheduled in a single DCI, the terminal selects and transmits either a first subcodebook or a second subcodebook based on the number of bundled HARQ-ACK bits by the DCI. Here, the first and second subcodebooks may be modified as follows:

[0363] The first subcodebook includes the HARQ-ACK bits for PDSCHs using TB (transport block) based transmission, and, when multiple PDSCHs are scheduled by a single DCI, the bundled HARQ-ACK bits generated by the DCI are X bits or less. Let's assume that a PDSCH using TB-based transmission is configured to contain P TBs, where P is the maximum number of TBs included in the PDSCH. Therefore, max{P,X} HARQ-ACK bits are generated for each DCI that schedules TB-based transmission. For reference, if the number of TBs scheduled by the DCI is less than max{P,X}, the HARQ-ACK bits corresponding to the missing number will be set to NACK. max{P,X} bundled HARQ-ACK bits are generated for each DCI that schedules TB-based transmission. For reference, a DCI that instructs multi-PDSCH scheduling corresponds to bundled HARQ-ACK bits of X bits or less. If the number of bundled HARQ-ACK bits corresponding to the DCI that instructs multi-PDSCH scheduling is less than max{P,X}, then the bundled HARQ-ACK bits corresponding to the missing number will be set to NACK.

[0364] The second subcodebook includes PDSCHs transmitted via CBG (code block group) and, when multiple PDSCHs are scheduled via DCI, the bundled HARQ-ACK bits from DCI exceed X bits. The terminal sends to cell c that PDSCHs transmitted via CBG are N per TB. CBG,cIt may be configured to include CBGs. For all cells where CBG-based transmission is configured, (# of TB in cell c)*N CBG,c The maximum value is N CBG,max Let's assume that when multiple PDSCHs are scheduled in DCI, the maximum value of the number of bundled HARQ-ACK bits corresponding to one TDRA index is N. bundled,max Let's go with that. For reference, N bundled,max It is a value greater than X.

[0365] The terminal instructs the CBG-based transmission to send a maximum of (N) DCI per DCI. CBG,max ,N bundled,max ) Generates a HARQ-ACK bit. The terminal sends max(N) to the DCI that instructs the multi-PDSCH scheduling. CBG,max ,N bundled,max )Generates HARQ-ACK bits. Assuming the number of CBGs scheduled by DCI is max(N CBG,max ,N bundled,max If the number of bundled HARQ-ACK bits corresponding to the DCI that instructs multi-PDSCH scheduling is less than max(N), then NACK will be set for the missing HARQ-ACK bits. CBG,max ,N bundled,max If the number is less than the number of bundled HARQ-ACK bits that are missing, the bundled HARQ-ACK bits corresponding to the missing number will be set to NACK.

[0366] For example, suppose a terminal always generates one bundled HARQ-ACK bit for a DCI that instructs multi-PDSCH scheduling. In this case, the terminal always includes the bundled HARQ-ACK bit in the first subcodebook.

[0367] How to assign HARQ process numbers when multiple PDSCH or multiple PUSCH are scheduled.

[0368] As mentioned above, in NR, multiple PDSCHs or multiple PUSCHs may be scheduled in multiple slots. In this case, multiple PDSCHs or multiple PUSCHs may be scheduled in one DCI, and HARQ-ACKs for the scheduled multiple PDSCHs may be transmitted via PUCCH in one or more slots.

[0369] In this case, assigning HARQ process numbers (or HARQ process IDs) to scheduled multiple PDSCHs or multiple PUSCHs can be problematic. In particular, setting HARQ process numbers corresponding to each PDSCH or PUSCH constituting a multiple PDSCH or multiple PUSCH can be problematic when the symbols of the multiple slots in which the multiple PDSCHs or multiple PUSCHs are scheduled overlap with symbols set for other purposes by higher-level signaling (e.g., RRC configuration information such as TDD-UL-DL-ConfigurationCommon or TDD-UL-DL-ConfigurationDedicated).

[0370] The problem that this invention aims to solve is a method for assigning HARQ Process Numbers (HPNs) to PDSCH or PUSCH scheduled on multiple slots when a PDSCH or PUSCH is scheduled on multiple slots by a single DCI.

[0371] When a single DCI schedules PDSCH or PUSCH with multiple slot scheduling, collisions may occur, particularly with PDSCH or PUSCH scheduled on flexible symbols, due to other DL or UL slots and symbols. Furthermore, ambiguity regarding the HPN between other terminals and base stations may occur when a terminal configured to monitor DCI 2_0, i.e., SFI, receives or fails to receive the SFI. This invention provides a method to resolve these issues.

[0372] Specifically, when multiple PDSCHs or multiple PUSCHs are scheduled in multiple slots by a single DCI, the DCI can specify the HARQ process number for the first PDSCH of the multiple PDSCHs or the first PUSCH of the multiple PUSCHs. The HARQ process number may then be incremented by one according to the scheduling order of the PDSCHs or PUSCHs.

[0373] In other words, the HARQ process number for each subsequent PDSCH or PUSCH after the first PDSCH increases by "1". At this time, the symbol of the slot from which the first PDSCH or first PUSCH is transmitted does not overlap with the UL symbol indicated by the RRC configuration information.

[0374] However, if the symbols included in each slot of a slot where multiple PDSCHs or multiple PUSCHs are scheduled overlap with UL symbols or DL ​​symbols indicated by the RRC configuration information, the PDSCH or PUSCH will not be transmitted in that slot, and the HARQ process number for the PDSCH or PUSCH for that slot will not increase. Subsequently, the HARQ process number will increase if the PDSCH scheduled for the next slot is valid (valid PDSCH) or if the PUSCH scheduled for the next slot is valid (valid PUSCH).

[0375] Specifically, when multiple PDSCHs are scheduled by a single DCI, if the symbol of the slot to which the first PDSCH is sent does not overlap with the symbol set as a UL symbol by the RRC configuration information, the first PDSCH will be assigned the HARQ processor number indicated by the DCI. After the first PDSCH, the next PDSCH can be received effectively if the symbol of the slot to which the next PDSCH is sent does not overlap with the UL symbol indicated by the RRC configuration information, or overlaps with the DL symbol indicated by the RRC configuration information, and the HARQ processor number increases by "1". However, if the symbol of the slot to which the next PDSCH is scheduled overlaps with the UL symbol indicated by the RRC configuration information, the next PDSCH will not be received, and the HARQ process number will not increase.

[0376] If the symbol of a slot where multiple PDSCHs are scheduled overlaps with a flexible symbol indicated by the RRC configuration information, the HARQ process number may increase regardless of whether the PDSCH is received. In other words, even if the flexible symbol is indicated as UL or flexible by the SFI in DCI format 2_0 and the PDSCH is not received, the HARQ process number may increase. That is, the format of the symbol indicated by the SFI does not need to be related to whether the HARQ process number increases. This is to resolve the issue of whether the HARQ process number increases when ambiguity arises between the terminal and the base station because the SFI is not detected.

[0377] If, for example, the UL symbol indicated by the RRC configuration information and the slot symbol overlap, resulting in no PDSCH reception and no increase in the HARQ processor number, then if PDSCH scheduled for slots after the slot where the PDSCH was not received is valid, the HARQ processor number will increase by "1".

[0378] When multiple pushes are scheduled by a single DCI, if the symbol of the slot to which the first push is sent does not overlap with the symbol set as a DL symbol by the RRC configuration information, the first push will be sent with the HARQ processor number indicated by the DCI. After the first push, the next push can be sent effectively if the symbol of the slot to which the next push is sent does not overlap with the DL symbol indicated by the RRC configuration information, or overlaps with the UL symbol indicated by the RRC configuration information, and the HARQ processor number will increment by "1". However, if the symbol of the slot to which the next push is scheduled overlaps with the DL symbol indicated by the RRC configuration information, the next push will not be sent, and the HARQ process number will not increment.

[0379] If the symbol of a slot where multiple pushes are scheduled overlaps with a flexible symbol indicated by the RRC configuration information, the HARQ process number may increase depending on whether or not reception of a specific signal (e.g., SSB (Synchronization Signal / PBCH block)) is set for that symbol. In this case, even if reception of a specific signal is not set for that symbol, and it is indicated as DL or flexible by the SFI in DCI format 2_0, the HARQ process number may increase even if no push is transmitted. In other words, the format of the symbol indicated by the SFI does not need to be related to whether or not the HARQ process number increases. Here, whether or not reception of a specific signal is set can be determined based on the SSB indexes provided by SSBPositioninburst as part of the RRC configuration information. Whether or not SSB is received may be indicated (or set) by SSBPositioninburst, which is a higher-layer parameter of the RRC configuration information. That is, when a terminal receives RRC configuration information, it can determine whether or not SSB is set by SSBPositioninburst, which is a parameter included in the RRC configuration information. If a multiple PUSCH transmission is scheduled, and the symbol of the slot in which the PUSCH is scheduled overlaps with a flexible symbol indicated by the RRC configuration information, and reception of a specific signal is set for that symbol, the PUSCH transmission will not occur, and the HARQ process number will not increase.

[0380] However, if multiple PUSCH transmissions are scheduled, and the symbol of the slot in which a PUSCH is scheduled among the multiple PUSCHs overlaps with a flexible symbol indicated by the RRC configuration information, and reception of a specific signal is not set for that symbol, the HARQ process number will increase regardless of whether a PUSCH is transmitted or not. In other words, if reception of a specific signal is not set for that symbol, and that symbol is indicated as DL or flexible by the SFI in DCI format 2_0, the HARQ process number may increase even if a PUSCH is not transmitted. This is to resolve the issue of whether or not the HARQ process number increases when the SFI is not detected and ambiguity occurs between the terminal and the base station.

[0381] If, for example, the DL symbol specified by the RRC configuration information and the slot symbol overlap, and therefore a PUSCH transmission is not performed and the HARQ processor number does not increase, then if a PUSCH scheduled for a subsequent slot is valid, the HARQ processor number will increase by "1".

[0382] In this case, flexible symbols set by the RRC configuration information may be symbols that are not designated as DL symbols or UL symbols by the RRC configuration information. That is, if a symbol is not designated as a DL symbol or UL symbol by the RRC configuration information, it may be implicitly recognized as a flexible symbol.

[0383] In other words, when multiple PDSCHs (or multiple PUSCHs) are scheduled, the terminal expects the base station to instruct the first scheduled PDSCH (or first scheduled PUSCH) to be allocated a valid PDSCH (or PUSCH) resource, applies the HPN instructed by DCI to that valid PDSCH (or PUSCH), and increments the HPN by 1 for subsequent PDSCHs among the multiple PDSCHs.

[0384] In the above, a valid PDSCH (or PUSCH) resource will be considered by the PDSCH to include all DL / flexible symbols that are not UL slots / symbols configured by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, provided that if a PDSCH scheduled with a flexible symbol conflicts with a UL, the HPN will not be skipped (i.e., the HPN will be incremented by 1), and the HPN will be incremented by 1 for subsequent PDSCHs.

[0385] In the above, a valid PDSCH (or PUSCH) resource is considered by PUSCH to be any UL / flexible symbol that is not a DL slot / symbol configured by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, provided that if a PUSCH scheduled with a flexible symbol conflicts with a DL, the HPN is not skipped (i.e., the HPN is incremented by 1), and the HPN is incremented by 1 for subsequent PUSCHs.

[0386] In yet another embodiment of the present invention, when multiple PDSCHs (or multiple PUSCHs) are scheduled, the terminal may consider pre-configured resources, such as SPS-PDSCH or CG-PUSCH, as valid PDSCH (or PUSCH) resources for allocating an HPN for the first scheduled PDSCH (or PUSCH). However, for pre-configured HPNs, such as SPS-PDSCH or CG-PUSCH, the terminal may skip those HPNs and sequentially increase the HPN allocation for the multiple PDSCHs (or PUSCHs) by one.

[0387] In contrast, when multiple PDSCHs (or multiple PUSCHs) are scheduled, the terminal may consider pre-configured resources, such as SPS-PDSCHs or CG-PUSCHs, as valid PDSCH (or PUSCH) resources for allocating an HPN for the first scheduled PDSCH (or PUSCH). In this case, if a resource dynamically scheduled by the base station overlaps with a pre-configured resource such as an SPS-PDSCH or CG-PUSCH, the terminal may expect that the HPN of the pre-configured SPS-PDSCH or CG-PUSCH will not be considered by the base station. The terminal may then not skip the HPN of the pre-configured SPS-PDSCH or CG-PUSCH, but instead sequentially increment the HPN for the multiple PDSCHs (or multiple PUSCHs) by one.

[0388] In yet another embodiment of the present invention, when multiple PDSCHs (or multiple PUSCHs) are scheduled, the terminal expects that the base station will instruct the first scheduled PDSCH (or first scheduled PUSCH) to be allocated a valid PDSCH (or PUSCH) resource, and applies the HPN instructed by DCI to that valid PDSCH (or PUSCH), and increments the HPN by 1 for subsequent PDSCHs among the multiple PDSCHs.

[0389] In the above, a valid PDSCH (or PUSCH) resource is considered to be any DL / flexible symbol that is not a UL slot / symbol configured by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, provided that if a PDSCH scheduled with a flexible symbol conflicts with an SSB transmitted by the base station, the HPN is skipped for each subsequent PDSCH (i.e., the HPN is not increased by one), and the HPN is increased by one for subsequent PDSCHs. The terminal does not need to expect scheduling of multiple PDSCHs with flexible symbols configured to receive SSB transmissions, and for SSB reception at the terminal in response to SSB transmissions from the base station, it is assumed that one or more SSBs may be transmitted, each having candidate SSB indexes corresponding to the SSB indexes provided by SSB-PositionsInBurst configured by the base station, and the terminal does not need to expect scheduling of multiple PDSCHs with flexible symbols configured to receive such SSB transmissions.

[0390] In the above, a valid PDSCH (or PUSCH) resource is considered to be any UL / flexible symbol that is not a DL slot / symbol configured by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, provided that if a PUSCH scheduled with a flexible symbol conflicts with an SSB, the increment of HPN is skipped (i.e., HPN is not incremented by 1), and HPN is incremented by 1 for subsequent PUSCHs. The terminal does not need to expect scheduling of multiple PUSCHs with flexible symbols configured to receive SSBs, and for SSB reception at the terminal in response to SSB transmissions from the base station, it is assumed that one or more SSBs may be transmitted, each having candidate SSB indexes corresponding to the SSB indexes provided by SSB-PositionsInBurst configured by the base station, and the terminal does not need to expect scheduling of multiple PUSCHs with flexible symbols configured to receive such SSB transmissions. When a multiplexed push is scheduled from the base station to a flexible symbol that the terminal can assume is receiving SSB, and the scheduled push is either the first scheduled push among the multiplexed pushes, or a push scheduled after the first scheduled push among the multiplexed pushes, if the push scheduled to the terminal collides with SSB, the HPN is skipped for that push (i.e., the HPN is not increased by 1), and the HPN is increased by 1 for subsequent pushes.

[0391] In the above, a valid PDSCH (or PUSCH) resource is considered to be a DL / flexible symbol that is not a UL slot / symbol configured by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated. However, if a PDSCH scheduled with a flexible symbol experiences a collision due to group common signaling transmitted by the base station, such as a UL cancellation indication, slot format indication, or rate-matching pattern indication, the HPN will not be increased by one each time (i.e., the HPN will be increased by one each time), and the HPN will be increased by one each time for subsequent PDSCHs. This is because in dynamic indications, ambiguity can arise between the terminal and the base station regarding whether the terminal receives it or not, and this is resolved by operating based on the scheduling instructed by the base station to resolve such ambiguity. However, for resource settings configured so that the terminal and base station have the same understanding through RRC signaling, there is no room for ambiguity between the terminal and base station, so this means that the operation based on the RRC settings can be performed as is.

[0392] In the above, a valid PDSCH (or PUSCH) resource is considered to be any UL / flexible symbol that is not a DL slot / symbol configured by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, provided that if a PUSCH scheduled with a flexible symbol is affected by group common signaling transmitted by the base station, such as a UL cancellation instruction, slot format instruction (SFI), or rate matching pattern instruction, the increment of the HPN should not be skipped (i.e., the HPN should be incremented by 1), and the HPN should be incremented by 1 for subsequent PUSCHs. This is because in dynamic instructions, ambiguity can arise between the terminal and the base station regarding whether the terminal receives it or not, and this is resolved by operating based on the scheduling instructed by the base station to resolve such ambiguity. However, for resource settings configured so that the terminal and base station have the same understanding through RRC signaling, there is no room for ambiguity between the terminal and base station, so this means that the operation based on the RRC settings can be performed as is.

[0393] Figure 23 is a flowchart showing an example of the operation of a terminal according to an embodiment of the present invention.

[0394] Referring to Figure 23, a terminal can set a HARQ process number for multiple pushes when multiple pushes are scheduled to be sent by a single DCI.

[0395] Specifically, the terminal receives RRC (Radio Resource Control) configuration information regarding the slot configuration from the base station (S23010). At this time, the RRC configuration information may include at least one of TDD-UL-DL-ConfigurationDedicated or TDD-UL-DLConfigurationCommon.

[0396] Subsequently, the terminal receives a Physical Downlink Control Channel (PDCCH) from the base station, which includes Downlink Control information (DCI) that schedules a multiple Physical Uplink Shared Channel (PUSCH) for the terminal (S23020).

[0397] DCI specifies the HARQ (Hybrid Automatic Repeat Request) process number of the first PUSCH among the multiple PUSCHs, and the HARQ process number of the PUSCHs constituting the multiple PUSCHs may be higher than the HARQ process number of the PUSCH for the previous PUSCH, depending on whether the symbol of the slot in which the PUSCH is scheduled overlaps with a symbol indicated as a downlink or flexible by the RRC configuration information.

[0398] Specifically, as mentioned above, when multiple PUSCHs are scheduled by a single DCI, if the symbol of the slot to which the first PUSCH is sent does not overlap with the symbol set as a DL symbol by the RRC configuration information, the first PUSCH will be sent with the HARQ processor number indicated by the DCI. After the first PDSCH, if the symbol of the slot to which the next PUSCH is scheduled does not overlap with the DL symbol indicated by the RRC configuration information, or overlaps with the UL symbol indicated by the RRC configuration information, the PUSCH can be sent successfully, and the HARQ processor number will increase by "1". However, if the symbol of the slot to which the next PUSCH is scheduled overlaps with the DL symbol indicated by the RRC configuration information, the next PUSCH will not be sent, and the HARQ process number will not increase.

[0399] If a symbol in a slot where multiple pushes are scheduled overlaps with a flexible symbol indicated by the RRC configuration information, the HARQ process number may increase depending on whether or not reception of a specific signal (e.g., SSB (Synchronization Signal / PBCH block)) is configured for that symbol. In this case, even if reception of a specific signal is not configured for that symbol, and it is indicated as DL or flexible by the SFI in DCI format 2_0, and no push is transmitted, the HARQ process number may still increase. In other words, the format of the symbol indicated by the SFI does not need to be related to whether or not the HARQ process number increases. Here, whether or not reception of a specific signal is configured can be determined based on the SSB indexes provided by SSBPositioninburst as part of the RRC configuration information. Whether or not SSB is received may be indicated (or configured) by SSBPositioninburst, which is a higher-layer parameter of the RRC configuration information. In other words, when a terminal receives RRC configuration information, it can determine whether SSB is configured or not based on the parameter SSBPositioninburst included in the RRC configuration information.

[0400] In other words, if a multiple PUSCH transmission is scheduled, and the symbol of the slot in which the PUSCH is scheduled among the multiple PUSCHs overlaps with a flexible symbol indicated by the RRC configuration information, and reception of a specific signal is set for that symbol, then the PUSCH transmission will not occur, and the HARQ process number will not increase.

[0401] However, if multiple PUSCH transmissions are scheduled, and the symbol of the slot in which a PUSCH is scheduled among the multiple PUSCHs overlaps with a flexible symbol indicated by the RRC configuration information, the HARQ process number will increase regardless of whether a PUSCH is transmitted, unless the reception of a specific signal is set for that symbol. In other words, if the reception of a specific signal is not set for that symbol, the symbol may be indicated as DL or flexible by the DCI format 2_0 SFI, and even if a PUSCH is not transmitted, the HARQ process number may increase. This is to resolve the issue of whether or not the HARQ process number increases when the SFI is not detected and ambiguity arises between the terminal and the base station.

[0402] If, for example, the DL symbol specified by the RRC configuration information and the slot symbol overlap, and therefore a PUSCH transmission is not performed and the HARQ processor number does not increase, then if a PUSCH scheduled for a subsequent slot is valid, the HARQ processor number will increase by "1".

[0403] In this case, flexible symbols set by the RRC configuration information may be symbols that are not designated as DL symbols or UL symbols by the RRC configuration information. That is, if a symbol is not designated as a DL symbol or UL symbol by the RRC configuration information, it may be implicitly recognized as a flexible symbol.

[0404] The above description of the present invention is illustrative, and a person with ordinary skill in the art to which the present invention belongs will understand that it can be easily modified into other specific forms without altering the technical idea or essential features of the present invention. Accordingly, the embodiments described above should be understood to be illustrative and not limiting in any respect. For example, each component described as a single type may be implemented in a distributed manner, and similarly, components described as distributed may be implemented in a combined manner.

[0405] The scope of the present invention is indicated more by the claims described below than by the detailed description above, and it should be interpreted that any modified or altered forms derived from the meaning and scope of the claims and the concept of equivalents thereto are included within the scope of the present invention.

Claims

1. A terminal configured to operate in a wireless communication system, Communication module and A processor, and the processor is The base station receives RRC (Radio Resource Control) configuration information regarding the slot configuration. The base station receives a Physical Downlink Control Channel (PDCCH) containing Downlink Control Information (DCI), The DCI schedules multiple Physical Uplink Shared Channels (PUSCHs) and specifies a specific HARQ (Hybrid Automatic Repeat Request) process number for a specific PUSCH among the multiple PUSCHs. The HARQ process number of a PUSCH among the multiple PUSCHs, excluding the specified PUSCH, increases relative to the HARQ process number of the previous PUSCH if the symbol on which the PUSCH is scheduled does not overlap with i) a downlink symbol indicated by the RRC configuration information, or ii) a symbol that constitutes an SS / PBCH (synchronization signal / physical broadcast channel) block. The specific PUSCH having the specific HARQ process number indicated by the DCI is a terminal that is i) the downlink symbol indicated by the RRC configuration information, or ii) the earliest PUSCH that does not overlap with the symbol that constitutes the SS / PBCH block.

2. The terminal according to claim 1, wherein when the symbol scheduled for the PUSCH is instructed to be an uplink symbol by the RRC configuration information, the HARQ process number of the PUSCH increases by "1" from the HARQ process number of the previous PUSCH.

3. The terminal according to claim 1, wherein the PUSCH is not transmitted if the symbol on which the PUSCH is scheduled overlaps with i) the downlink symbol indicated by the RRC configuration information, or ii) the symbol on which the SS / PBCH block is composed.

4. The terminal according to claim 3, wherein the HARQ process number of the PUSCH is not greater than the HARQ process number of the previous PUSCH.

5. The terminal according to claim 3, wherein if the symbol of the next PUSCH among the multiple PUSCHs is instructed to be an uplink symbol by the RRC configuration information, the HARQ process number of the next PUSCH is increased by "1" from the HARQ process number of the previous PUSCH.

6. The terminal according to claim 1, wherein the position of the symbol in the SS / PBCH block is indicated by SSBpositioninburst, which is an RRC information element.

7. The terminal according to claim 1, wherein if the SS / PBCH block does not consist of a scheduled flexible symbol, the HARQ process number of the PUSCH is increased by "1" from the HARQ process number of the previous PUSCH.

8. The terminal according to claim 7, wherein the HARQ process number of the PUSCH is increased by "1" from the HARQ process number of the previous PUSCH, regardless of whether the flexible symbol scheduled for the PUSCH is indicated as an uplink, downlink, or flexible by a slot format indicator (SFI).

9. A terminal configured to operate in a wireless communication system, Communication module and A processor, and the processor is The base station receives RRC (Radio Resource Control) configuration information regarding the slot configuration. The base station receives a Physical Downlink Control Channel (PDCCH) containing Downlink Control Information (DCI), The DCI schedules multiple physical downlink shared channels (PDSCHs) and specifies a specific HARQ (Hybrid Automatic Repeat Request) process number for a specific PDSCH among the multiple PDSCHs. The HARQ process number of a PDSCH among the multiple PDSCHs, excluding the specified PDSCH, increases relative to the HARQ process number of the previous PDSCH when the symbol on which the PDSCH is scheduled does not overlap with the uplink symbol indicated by the RRC configuration information. The terminal having the specific HARQ process number indicated by the DCI is the earliest PDSCH that does not overlap with the uplink symbol indicated by the RRC configuration information.

10. The terminal according to claim 9, wherein when the symbol scheduled for the PDSCH is instructed to be a downlink symbol by the RRC configuration information, the HARQ process number of the PDSCH increases by "1" from the HARQ process number of the previous PDSCH.

11. The terminal according to claim 9, wherein the PDSCH is not received if the symbol for which the PDSCH is scheduled overlaps with the uplink symbol indicated by the RRC configuration information.

12. The terminal according to claim 9, wherein the HARQ process number of the PDSCH is not greater than the HARQ process number of the previous PDSCH.

13. The terminal according to claim 9, wherein if the symbol of the next PDSCH among the multiple PDSCHs is designated as a downlink symbol by the RRC configuration information, the HARQ process number of the next PDSCH is increased by "1" from the HARQ process number of the previous PDSCH.

14. The terminal according to claim 13, wherein the HARQ process number of the PDSCH is increased by "1" from the HARQ process number of the previous PDSCH, regardless of whether the PDSCH is instructed by a slot format indicator (SFI) that the scheduled symbol is an uplink, downlink, or flexible.

15. A method by which a terminal configured to operate in a wireless communication system transmits a physical uplink shared channel (PUSCH), The process involves receiving RRC (Radio Resource Control) configuration information regarding the slot configuration from the base station, The process includes the step of receiving a Physical Downlink Control Channel (PDCCH) containing Downlink Control Information (DCI) from the base station, The DCI schedules multiple Physical Uplink Shared Channels (PUSCHs) and specifies a specific HARQ (Hybrid Automatic Repeat Request) process number for a specific PUSCH among the multiple PUSCHs. The HARQ process number of a PUSCH among the multiple PUSCHs, excluding the specified PUSCH, increases relative to the HARQ process number of the previous PUSCH if the symbol on which the PUSCH is scheduled does not overlap with i) a downlink symbol indicated by the RRC configuration information, or ii) a symbol that constitutes an SS / PBCH (synchronization signal / physical broadcast channel) block. The method wherein the specific PUSCH having the specific HARQ process number indicated by the DCI is the earliest PUSCH that does not overlap with i) the downlink symbol indicated by the RRC configuration information, or ii) the symbol that constitutes the SS / PBCH block.

Images