Method and apparatus for performing uplink transmission in a wireless communication system

Abstract

This disclosure relates to methods and apparatus for performing uplink transmissions in a wireless communication system. A method and apparatus for transmitting a PUCCH in a wireless communication system are disclosed. According to an embodiment of this disclosure, the method includes the steps of: receiving first configuration information associated with time-domain bundling from a base station; receiving at least one PDSCH from the base station at at least one PDSCH reception time; and transmitting a PUCCH to the base station including HARQ-ACK information for the at least one PDSCH, wherein the transmission power of the PUCCH is based on a specific PDSCH among the at least one PDSCH, and the specific PDSCH is associated with the last SLIV among at least one SLIV included in a TDRA line indicated by a DCI.

Description

Technical Field

[0001] This disclosure relates to a wireless communication system, and more specifically, to a method and apparatus for performing uplink transmission / reception in a wireless communication system based on time domain bundling. Background Technology

[0002] A mobile communication system has been developed to provide voice services while ensuring user mobility. However, mobile communication systems have expanded to include data and voice services, and the current explosive growth in these services has led to resource shortages. Users are demanding faster services and therefore require more advanced mobile communication systems.

[0003] The overall requirements for next-generation mobile communication systems should be able to support the capacity for explosive data traffic, significantly increased per-user transmission rates, a significantly increased number of connected devices, very low end-to-end latency, and high energy efficiency. To this end, various technologies such as dual connectivity, massive MIMO, in-band full-duplex, non-orthogonal multiple access (NOMA), ultra-wideband support, and device networking have been investigated. Summary of the Invention

[0004] Technical issues

[0005] The technical objective of this disclosure is to provide a method and apparatus for performing uplink transmission / reception in a wireless communication system.

[0006] Another technical objective of this disclosure is to provide a method and apparatus for determining the transmit power of a PUCCH, including HARQ-ACK information, when time-domain binding is configured.

[0007] The technical objectives to be achieved by this disclosure are not limited to those described above, and other technical objectives not described herein will be clearly understood by those skilled in the art through the following description.

[0008] Technical solution

[0009] In embodiments of this disclosure, a method for transmitting a Physical Uplink Control Channel (PUCCH) by a User Equipment (UE) in a wireless communication system may include the following steps: receiving first configuration information associated with time-domain bundling from a base station; receiving at least one PDSCH from the base station at the timing of receiving at least one Physical Downlink Shared Channel (PDSCH); and transmitting a PUCCH to the base station including HARQ-ACK information for the at least one PDSCH, wherein the transmission power of the PUCCH is based on a specific PDSCH among the at least one PDSCH, and the specific PDSCH is associated with the last SLIV (start and length indicator value) among at least one SLIV (start and length indicator value) included in a Time Domain Resource Allocation (TDRA) line indicated by Downlink Control Information (DCI).

[0010] In embodiments of this disclosure, a method for receiving a Physical Uplink Control Channel (PUCCH) in a wireless communication system may include the following steps: sending first configuration information related to time-domain bundling to a User Equipment (UE); sending at least one PDSCH to the UE at the timing of receiving at least one Physical Downlink Shared Channel (PDSCH); and receiving from the UE a PUCCH including HARQ-ACK information for the at least one PDSCH, wherein the transmission power of the PUCCH is based on a specific PDSCH among the at least one PDSCH, and the specific PDSCH is associated with the last SLIV (start and length indicator value) among at least one SLIV included in a Time Domain Resource Allocation (TDRA) line indicated by Downlink Control Information (DCI).

[0011] Technical effect

[0012] According to embodiments of this disclosure, a method and apparatus for performing uplink transmission / reception can be provided in a wireless communication system.

[0013] According to embodiments of this disclosure, when time-domain binding is configured, a method and apparatus for determining the transmit power of a PUCCH including HARQ-ACK information can be provided.

[0014] According to embodiments of this disclosure, stable HARQ-ACK feedback can be performed by determining the transmission power of the PUCCH based on the number of bits of HARQ-ACK information.

[0015] The effects achievable by this disclosure are not limited to those described above, and those skilled in the art can clearly understand other effects not described herein through the following description. Attached Figure Description

[0016] The accompanying drawings, which are included as part of the detailed description for understanding this disclosure, provide embodiments of the disclosure and describe the technical features of the disclosure through detailed description.

[0017] Figure 1 The structure of a wireless communication system to which this disclosure can be applied is illustrated.

[0018] Figure 2 A frame structure in a wireless communication system to which this disclosure can be applied is illustrated.

[0019] Figure 3 An example is shown of a resource grid in a wireless communication system to which this disclosure can be applied.

[0020] Figure 4 Examples of physical resource blocks in wireless communication systems to which this disclosure can be applied are provided.

[0021] Figure 5 The time slot structure in a wireless communication system to which this disclosure can be applied is illustrated.

[0022] Figure 6 Examples are given of physical channels used in wireless communication systems to which this disclosure may be applied, as well as general signal transmission and reception methods using such physical channels.

[0023] Figure 7 The process of a user equipment (UE) and a base station sending and receiving HARQ-ACK in a wireless communication system to which this disclosure may be applied is illustrated.

[0024] Figure 8 An example is illustrated of DCI-based uplink and / or downlink transmission / reception procedures in a wireless communication system to which this disclosure may be applied.

[0025] Figure 9 This is a diagram used to describe the downlink reception and uplink transmission operations of a UE in a wireless communication system to which this disclosure can be applied.

[0026] Figure 10 This is a diagram used to describe the downlink transmission and uplink reception operations of a base station in a wireless communication system to which the present disclosure may be applied.

[0027] Figure 11 This is a diagram illustrating the signaling process between the network side and the UE according to an embodiment of this disclosure.

[0028] Figure 12 A block diagram illustrating a wireless communication device according to an embodiment of the present disclosure is shown. Detailed Implementation

[0029] In the following, embodiments according to this disclosure will be described in detail with reference to the accompanying drawings. The detailed description disclosed with reference to the drawings is intended to describe exemplary embodiments of this disclosure and not to represent the only embodiments in which this disclosure can be implemented. The following detailed description includes specific details to provide a complete understanding of this disclosure. However, those skilled in the art will recognize that this disclosure can be implemented without these specific details.

[0030] In some cases, known structures and devices may be omitted, or they may be shown in block diagram form based on the core functions of each structure and device in order to prevent ambiguity of the concepts in this disclosure.

[0031] In this disclosure, when an element is referred to as “connected,” “combined,” or “linked” to another element, it can include both indirect and direct connections between the two elements. Furthermore, in this disclosure, the terms “comprising” or “having” specify the presence of the mentioned features, steps, operations, components, and / or elements, but do not exclude the presence or addition of one or more other features, stages, operations, components, elements, and / or groups thereof.

[0032] In this disclosure, terms such as "first" and "second" are used only to distinguish one element from another and are not used to limit the elements. Unless otherwise stated, they do not limit the order or importance of the elements. Therefore, within the scope of this disclosure, a first element in one embodiment may be referred to as a second element in another embodiment, and similarly, a second element in one embodiment may be referred to as a first element in another embodiment.

[0033] The terminology used in this disclosure is for the purpose of describing particular embodiments and not for limiting the claims. As used in the description of embodiments and the appended claims, the singular form is intended to include the plural form unless the context clearly indicates otherwise. The term “and / or” as used in this disclosure may refer to one of the associated enumerations, or is intended to refer to and include any and all possible combinations of two or more of them. Furthermore, unless otherwise stated, the “ / ” between words in this invention has the same meaning as “and / or”.

[0034] This disclosure describes a wireless communication network or wireless communication system, and operations performed in the wireless communication network can be performed during the process of a device (e.g., a base station) controlling the network and transmitting or receiving signals, or during the process of a terminal associated with the corresponding wireless network transmitting or receiving signals between the network or between the terminal.

[0035] In this disclosure, the term "transmit or receive channel" includes the meaning of transmitting or receiving information or signals through a corresponding channel. For example, transmitting a control channel means transmitting control information or control signals through a control channel. Similarly, transmitting a data channel means transmitting data information or data signals through a data channel.

[0036] In the following text, downlink (DL) refers to communication from a base station to a terminal, while uplink (UL) refers to communication from a terminal to a base station. In the downlink, the transmitter can be part of the base station, and the receiver can be part of the terminal. In the uplink, the transmitter can be part of the terminal, and the receiver can be part of the base station. A base station can be referred to as a first communication device, and a terminal can be referred to as a second communication device. A base station (BS) can be replaced by terms such as fixed station, Node B, eNB (evolved Node B), gNB (next-generation Node B), BTS (Base Transceiver System), Access Point (AP), Network (5G network), AI (Artificial Intelligence) system / module, RSU (Roadside Unit), robot, UAV (Unmanned Aerial Vehicle), AR (Augmented Reality) device, VR (Virtual Reality) device, etc. In addition, terminals can be fixed or mobile, and can be replaced by terms such as UE (User Equipment), MS (Mobile Station), UT (User Terminal), MSS (Mobile Subscriber Station), SS (Subscriber Station), AMS (Advanced Mobile Station), WT (Wireless Terminal), MTC (Machine-Type Communication) equipment, M2M (Machine-to-Machine) equipment, D2D (Device-to-Device) equipment, vehicles, RSU (Roadside Unit), robots, AI (Artificial Intelligence) modules, drones (UAVs), AR (Augmented Reality) equipment, and VR (Virtual Reality) equipment.

[0037] The following descriptions can be applied to various radio access systems, such as CDMA, FDMA, TDMA, OFDMA, SC-FDMA, etc. CDMA can be implemented using technologies such as UTRA (Universal Terrestrial Radio Access) or CDMA2000. TDMA can be implemented using radio technologies such as GSM (Global System for Mobile Communications) / GPRS (General Packet Radio Service) / EDGE (GSM Evolution with Enhanced Data Rates). OFDMA can be implemented using radio technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and E-UTRA (Evolved UTRA). UTRA is part of UMTS (Universal Mobile Telecommunications System). 3GPP (3rd Generation Partnership Project) LTE (Long Term Evolution) is part of E-UMTS (Evolved UMTS) using E-UTRA, and LTE-A (Advanced) / LTE-Apro are advanced versions of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an advanced version of 3GPP LTE / LTE-A / LTE-Apro.

[0038] To make the description clearer, it is based on 3GPP communication systems (e.g., LTE-A, NR), but the technical ideas of this disclosure are not limited thereto. LTE refers to technology from 3GPP TS (Technical Specification) version 8 onwards. Specifically, LTE technology in or after 3GPP TS 36.xxx is called LTE-A, and LTE technology in or after 3GPP TS 36.xxx is called LTE-Apro. 3GPP NR refers to technology in or after TS 38.xxx. LTE / NR can be referred to as a 3GPP system. "xxx" refers to the detailed number of the standard document. LTE / NR is generally referred to as a 3GPP system. For background information, terminology, abbreviations, etc., used to describe this disclosure, reference can be made to the matters described in the standard documents previously published. For example, the following documents can be consulted.

[0039] For 3GPP LTE, you can refer to TS 36.211 (Physical Channels and Modulation), TS 36.212 (Multiplexing and Channel Coding), TS 36.213 (Physical Layer Procedures), TS 36.300 (General Description), and TS 36.331 (Radio Resource Control).

[0040] For 3GPP NR, you can refer to TS 38.211 (Physical Channels and Modulation), TS 38.212 (Multiplexing and Channel Coding), TS 38.213 (Physical Layer Procedures for Control), TS 38.214 (Physical Layer Procedures for Data), TS 38.300 (General Description of NR and NG-RAN (Next Generation Radio Access Network)), and TS 38.331 (Radio Resource Control Protocol Specification).

[0041] The abbreviations of terms that may be used in this disclosure are defined as follows.

[0042] -BM: Beam Management

[0043] -CQI: Channel Quality Indicator

[0044] -CRI: Channel State Information - Reference Signal Resource Indicator

[0045] -CSI: Channel State Information

[0046] -CSI-IM: Channel State Information - Interference Measurement

[0047] -CSI-RS: Channel State Information - Reference Signal

[0048] -DMRS: Demodulation Reference Signal

[0049] -FDM: Frequency Division Multiplexing

[0050] -FFT: Fast Fourier Transform

[0051] -IFDMA: Interleaved Frequency Division Multiple Access

[0052] -IFFT: Inverse Fast Fourier Transform

[0053] -L1-RSRP: Layer 1 Reference Signal Received Power

[0054] -L1-RSRQ: Layer 1 reference signal reception quality

[0055] -MAC: Media Access Control

[0056] -NZP: Non-zero power

[0057] -OFDM: Orthogonal Frequency Division Multiplexing

[0058] –PDCCH: Physical Downlink Control Channel

[0059] -PDSCH: Physical Downlink Shared Channel

[0060] -PMI: Precoding Matrix Indicator

[0061] -RE: Resource Elements

[0062] -RI: Rank indicator

[0063] -RRC: Radio Resource Control

[0064] -RSSI: Received Signal Strength Indicator

[0065] -Rx: Receive

[0066] -QCL: Quasi-co-location

[0067] -SINR: Signal-to-Noise Ratio

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

[0069] -TDM: Time Division Multiplexing

[0070] -TRP: Sending and Receiving Point

[0071] -TRS: Tracking Reference Signal

[0072] -Tx: Send

[0073] -UE: User Equipment

[0074] -ZP: Zero Power

[0075] Overall System

[0076] With more communication devices requiring higher capacity, there has been a demand for improved mobile broadband communications compared to existing radio access technologies (RATs). Furthermore, massive MTC (machine-type communication) that provides various services anytime, anywhere by connecting multiple devices and things is also one of the main issues to be considered in next-generation communications. In addition, communication system designs considering services / terminals sensitive to reliability and latency are discussed. Therefore, the introduction of next-generation RATs considering eMBB (enhanced mobile broadband communication), mMTC (massive MTC), URLLC (ultra-reliable low-latency communication), etc., is discussed, and for convenience, the corresponding technologies are referred to as NR in this disclosure. NR is an example expression representing 5G RAT.

[0077] New RAT systems, including those for NR, use OFDM or similar transmission methods. These new RAT systems may follow OFDM parameters different from those used in LTE. Alternatively, the new RAT system may follow existing LTE / LTE-A parameters as is, but may support a wider system bandwidth (e.g., 100MHz). Alternatively, a single cell may support multiple parameter sets. In other words, terminals operating according to different parameter sets can coexist in a single cell.

[0078] The parameter set corresponds to a subcarrier spacing in the frequency domain. Different parameter sets can be defined as the reference subcarrier spacing is scaled by an integer N.

[0079] Figure 1 The structure of a wireless communication system to which this disclosure can be applied is illustrated.

[0080] refer to Figure 1 The NG-RAN is configured with gNBs that provide control plane (RRC) protocol support for the NG-RA (NG Radio Access) user plane (i.e., the new AS (Access Layer) sublayer / PDCP (Packet Data Convergence Protocol) / RLC (Radio Link Control) / MAC / PHY) and UE. The gNBs interconnect via the Xn interface. Furthermore, the gNBs are connected to the NGC (Next Generation Core) via the NG interface. More specifically, the gNBs are connected to the AMF (Access and Mobility Management Power) via the N2 interface and to the UPF (User Plane Functions) via the N3 interface.

[0081] Figure 2 A frame structure in a wireless communication system to which this disclosure can be applied is illustrated.

[0082] NR systems can support multiple parameter sets. These parameter sets can be defined by subcarrier spacing and cyclic prefix (CP) overhead. Multiple subcarrier spacings can be derived by scaling the basic (reference) subcarrier spacing by an integer N (or μ). Furthermore, while it is assumed that very low subcarrier spacings are not used at very high carrier frequencies, the parameter set used can be selected independently of the frequency band. Moreover, various frame structures based on multiple parameter sets can be supported in NR systems.

[0083] The OFDM parameter sets and frame structures that can be considered in an NR system are described below. Several OFDM parameter sets supported in an NR system can be defined as shown in Table 1 below.

[0084] [Table 1]

[0085] μ <![CDATA[Δf=2 μ ·15[kHz]]]> CP 0 15 normal 1 30 normal 2 60 Normal, expanded 3 120 normal 4 240 normal

[0086] NR supports multiple parameter sets (or subcarrier spacing (SCS)) to support various 5G services. For example, a 15kHz SCS supports wide-area coverage of traditional cellular bands; a 30kHz / 60kHz SCS supports dense urban areas, lower latency, and wider carrier bandwidth; and a 60kHz or higher SCS supports bandwidths exceeding 24.25GHz to overcome phase noise. NR bands are defined as frequency ranges of two types (FR1, FR2). FR1 and FR2 can be configured as shown in Table 2 below. Additionally, FR2 can refer to millimeter wave (mmW).

[0087] [Table 2]

[0088]

[0089] Regarding the frame structure in the NR system, the size of various fields in the time domain is expressed as T. c =1 / (Δf) max ·N f A multiple of the time unit. Here, Δf max It is 480·10 3Hz, and N f The value is 4096. Downlink and uplink transmissions are configured (organized) to have a duration T. f =1 / Δf max N f / 100)·T c A radio frame of 10ms. Here, the radio frame is configured with 10 subframes, each with a T... sf =(Δf max N f / 1000)·T c = 1ms duration. In this case, there may be one frame set for the uplink and one frame set for the downlink.

[0090] Furthermore, the transmission in the i-th uplink frame from the terminal should begin T earlier than the corresponding downlink frame in the corresponding terminal. TA =(N TA +N TA,offset )T c Begin. For the subcarrier spacing configuration μ, the time slots are arranged in n-order within the subframe. s μ ∈{0,...,N slot subframe,μ The numbers are numbered in ascending order from -1, and in the radio frames, they are numbered in n... s,f μ ∈{0,...,N slot frame,μ The time slot is configured with N in ascending order of -1. symbslot N consecutive OFDM symbols, and N symb slot Determined based on CP. Slot n in the subframe s μ The start of the OFDM symbol n in the same subframe s μ N symb slot The beginnings are arranged chronologically.

[0091] All terminals may not be able to transmit and receive simultaneously, meaning that all OFDM symbols in either the downlink or uplink time slots may not be available. Table 3 shows the number of OFDM symbols (N) in each time slot during normal CP. symb slot ), Number of time slots per radio frame (N) slot frame,μ ) and the number of time slots per subframe (N) slot subframe,μ Table 4 shows the number of OFDM symbols per slot, the number of slots per radio frame, and the number of slots per subframe in the extended CP.

[0092] [Table 3]

[0093] μ <![CDATA[N symb slot ]]> <![CDATA[N slot frame,μ ]]> <![CDATA[N slot subframe,μ ]]> 0 14 10 1 1 14 20 2 2 14 40 4 3 14 80 8 4 14 160 16

[0094] [Table 4]

[0095] μ <![CDATA[N symb slot ]]> <![CDATA[N slot frame,μ ]]> <![CDATA[N slot subframe,μ ]]> 2 12 40 4

[0096] Figure 2 This is an example of μ=2 (SCS is 60kHz), see Table 3. One subframe can include 4 time slots. Figure 2 The subframe shown as {1,2,4} is an example; the number of time slots that can be included in a subframe is defined in Table 3 or Table 4. Additionally, micro-time slots can include 2, 4, or 7 symbols, or more or fewer symbols. Regarding physical resources in an NR system, antenna ports, resource grids, resource elements, resource blocks, carrier portions, etc., can be considered.

[0097] The physical resources that can be considered in an NR system will be described in detail below. First, regarding antenna ports, antenna ports are defined such that the channel carrying a symbol in an antenna port can be inferred from the channels carrying other symbols in the same antenna port. When the large-scale properties of the channel carrying a symbol in one antenna port can be inferred from the channels carrying symbols in another antenna port, it can be said that two antenna ports are in a QC / QCL (quasi-co-located or quasi-co-located) relationship.

[0098] In this context, large-scale properties include at least one of delay spread, Doppler spread, frequency shift, average received power, and received timing.

[0099] Figure 3 The illustration shows a resource grid in a wireless communication system to which this disclosure can be applied.

[0100] refer to Figure 3 The diagram illustrates the resource grid configuration with N in the frequency domain. RB μ N sc RB There are 14.2 subcarriers, and one subframe is configured with 14.2 μ OFDM symbols, but not limited to these.

[0101] In the NR system, the transmitted signal consists of 2 μ N symb (μ) Each OFDM symbol and configuration has N RB μ N sc RB It is described by one or more resource grids of N subcarriers. Here, N RB μ ≤N RB max,μ N RB max,μ This represents the maximum transmission bandwidth, which may differ between uplink and downlink, and between parameter sets. In this case, each μ and antenna port p can be configured with a resource grid. Each element of the resource grid used for μ and antenna port p is called a resource element and is uniquely identified by an index pair (k, l').

[0102] Here, k = 0, ..., N RB μ N sc RB -1 is the index in the frequency domain, and l' = 0, ..., 2 μ N symb (μ) -1 indicates the symbol position within the subframe. When referencing resource elements in a time slot, the index pair (k, l) is used. Here, l = 0,...,N symb μ -1. The resource element (k,l') used for μ and antenna port p corresponds to the complex value a. k,l' (p,μ) .

[0103] When there is no risk of confusion or when a specific antenna port or parameter set is not specified, the indices p and μ may be discarded, and the complex value may be ak,l'(p) or ak,l'. Furthermore, a resource block (RB) is defined as N in the frequency domain. sc RB = 12 consecutive subcarriers. Point A serves as a common reference point for the resource block grid and is obtained as follows. The offsetToPointA of the main cell (PCell) downlink represents the frequency offset between point A and the lowest subcarrier of the lowest resource block overlapping with the SS / PBCH block, which is used by the terminal for initial cell selection. Assuming a subcarrier spacing of 15kHz is used for FR1 and a subcarrier spacing of 60kHz is used for FR2, it is expressed in units of resource blocks. absoluteFrequencyPointA represents the frequency position of point A, expressed in ARFCN (Absolute Radio Frequency Channel Number).

[0104] For subcarrier spacing configuration μ, common resource blocks are numbered from 0 upwards in the frequency domain. The center of subcarrier 0 of common resource block 0 used for subcarrier spacing configuration μ is the same as "point A".

[0105] The common resource block number n of the subcarrier spacing configuration μ in the frequency domain CRB μ The relationship between the resource element (k,l) and the resource element (k,l) is given by Equation 1 below.

[0106] [Equation 1]

[0107]

[0108] In Equation 1, k is defined relative to point A such that k = 0 corresponds to a subcarrier centered at point A. Physical resource blocks range from 0 to N in the bandwidth portion (BWP). BWP,i size,μ -1 is the number, and i is the number of the BWP. The physical resource block n in BWP i. PRB and public resource block n CRB The relationship between them is given by the following equation 2.

[0109] [Equation 2]

[0110]

[0111] N BWP,i start,μ It is a public resource block relative to public resource block 0 in BWP.

[0112] Figure 4 Examples of physical resource blocks in wireless communication systems that can utilize this disclosure are provided. Furthermore, Figure 5The time slot structure in a wireless communication system to which this disclosure can be applied is illustrated.

[0113] refer to Figure 4 and Figure 5 A time slot includes multiple symbols in the time domain. For example, for a normal CP, one time slot includes 7 symbols, but for an extended CP, one time slot includes 6 symbols.

[0114] A carrier comprises multiple subcarriers in the frequency domain. An RB (Resource Block) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A BWP (Bandwidth Component) is defined as multiple consecutive (physical) resource blocks in the frequency domain and may correspond to a set of parameters (e.g., SCS, CP length, etc.).

[0115] A carrier can include up to N (e.g., 5) BWPs. Data communication can be performed through an active BWP, and only one BWP can be active for a single terminal. In the resource grid, each element is called a resource element (RE) and can be mapped to a complex number of symbols.

[0116] In NR systems, each component carrier (CC) can support up to 400MHz. If a terminal operating in such a wideband CC always operates with the radio frequency (FR) chip turned on for the entire CC, terminal battery consumption may increase. Alternatively, when considering multiple applications operating in a single wideband CC (e.g., eMBB, URLLC, Mmtc, V2X, etc.), different sets of parameters (e.g., subcarrier spacing, etc.) can be supported in each band of the corresponding CC.

[0117] Alternatively, each terminal may have different capabilities for the maximum bandwidth. With this in mind, the base station can instruct the terminal to operate only in a portion of the bandwidth, rather than in the full bandwidth of the wideband CC, and for convenience, the corresponding portion of the bandwidth is defined as the Bandwidth Part (BWP). The BWP can be configured with consecutive RBs on the frequency axis and can correspond to a set of parameters (e.g., subcarrier spacing, CP length, slot / microslot duration).

[0118] Furthermore, even within a single CC configured for a terminal, a base station can configure multiple BWPs. For example, a BWP occupying a relatively small frequency domain can be configured in a PDCCH monitoring slot, and a PDSCH indicated by the PDCCH can be scheduled within a larger BWP.

[0119] Alternatively, when a UE is congested in a particular BWP, other BWPs can be configured for some terminals to perform load balancing.

[0120] Alternatively, considering factors such as frequency domain inter-cell interference cancellation between neighboring cells, some full-bandwidth intermediate spectrum can be excluded, and two edge BWPs can be configured in the same time slot.

[0121] In other words, the base station can configure at least one DL / UL BWP to a terminal associated with a broadband CC. The base station can activate at least one of the configured DL / UL BWPs at a specific time (via L1 signaling, MAC CE (control element), or RRC signaling, etc.). Furthermore, the base station can instruct a switch to a different configured DL / UL BWP (via L1 signaling, MAC CE, or RRC signaling, etc.).

[0122] Alternatively, based on a timer, a switch can be made to a specific DL / UL BWP when the timer value expires. Here, the active DL / UL BWP is defined as the active DL / UL BWP. However, the terminal may not receive configuration on the DL / UL BWP before performing the initial access procedure or establishing an RRC connection; therefore, in these cases, the DL / UL BWP assumed by the terminal is defined as the initially active DL / UL BWP.

[0123] Figure 6 Examples are given of physical channels used in wireless communication systems to which this disclosure may be applied, as well as general signal transmission and reception methods using such physical channels.

[0124] In wireless communication systems, terminals receive information from base stations via downlink and transmit information to base stations via uplink. The information sent and received by base stations and terminals includes data and various control information, and various physical channels exist depending on the type / purpose of the information they send and receive.

[0125] When a terminal is powered on or enters a new cell, it performs an initial cell search (S601), including synchronization with the base station. For the initial cell search, the terminal synchronizes with the base station by receiving the primary synchronization signal (PSS) and secondary synchronization signal (SSS) from the base station, and obtains information such as the cell identifier (ID). Then, the terminal obtains broadcast information within the cell by receiving the physical broadcast channel (PBCH) from the base station. Simultaneously, the terminal checks the downlink channel state by receiving the downlink reference signal (DL RS) during the initial cell search phase.

[0126] The terminal that has completed the initial cell search can obtain more detailed system information by receiving the Physical Downlink Control Channel (PDCCH) and Physical Downlink Shared Channel (PDSCH) based on the information carried in the PDCCH (S602).

[0127] Simultaneously, when a terminal first accesses a base station or when there are no radio resources available for signal transmission, it can perform a random access (RACH) procedure (S603 to S606). For the random access procedure, the terminal can send a specific sequence as a preamble via the Physical Random Access Channel (PRACH) (S603 and S605), and can receive response messages to the preamble via the PDCCH and the corresponding PDSCH (S604 and S606). Contention-based RACH can further execute a contention resolution procedure.

[0128] The terminal that subsequently performs the above process can execute PDCCH / PDSCH reception (S607) and PUSCH (Physical Uplink Shared Channel) / PUCCH (Physical Uplink Control Channel) transmission (S608) as a general uplink / downlink signal transmission process. Specifically, the terminal receives downlink control information (DCI) via PDCCH. Here, DCI includes control information such as resource allocation information for the terminal, and its format varies depending on its intended use.

[0129] Meanwhile, control information sent by the terminal to the base station via the uplink or received by the terminal from the base station includes downlink / uplink ACK / NACK (acknowledgment / non-acknowledgment) signals, CQI (Channel Command Indicator), PMI (Precoding Matrix Indicator), RI (Rank Indicator), etc. For 3GPP LTE systems, the terminal can send the aforementioned control information such as CQI / PMI / RI via PUSCH and / or PUCCH.

[0130] Table 5 shows examples of DCI format in NR systems.

[0131] [Table 5]

[0132]

[0133] Referring to Table 5, DCI formats 0_0, 0_1, and 0_2 may include resource information (e.g., UL / SUL (Supplemental UL), frequency resource allocation, time resource allocation, frequency hopping, etc.), information related to transport blocks (TB) (e.g., MCS (Modulation Coding and Scheme), NDI (New Data Indicator), RV (Redundancy Version), etc.), information related to HARQ (Hybrid Automatic Repeat and Request) (e.g., process number, DAI (Downlink Assignment Index), PDSCH-HARQ feedback timing, etc.), information related to multiple antennas (e.g., DMRS sequence initialization information, antenna ports, CSI requests, etc.), power control information related to PUSCH scheduling (e.g., PUSCH power control, etc.), and control information included in each DCI format can be predefined.

[0134] DCI format 0_0 is used to schedule PUSCH in a cell. The information included in DCI format 0_0 is scrambled with CRC (Cyclic Redundancy Check) by C-RNTI (Cell Radio Network Temporary Identifier), CS-RNTI (Configured Scheduling RNTI), or MCS-C-RNTI (Modulation Coding Scheme Cell RNTI) and transmitted.

[0135] DCI format 0_1 ​​is used to indicate the scheduling of one or more PUSCHs or to provide downlink feedback information to the Terminal Configuration Grant (CG) in a cell. The information included in DCI format 0_1 ​​is scrambled and transmitted by C-RNTI, CS-RNTI, SP-CSI-RNTI (semi-persistent CSI RNTI), or MCS-C-RNTI.

[0136] DCI format 0_2 is used to schedule PUSCH within a cell. The information included in DCI format 0_2 is scrambled and transmitted using C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI.

[0137] Next, DCI formats 1_0, 1_1, and 1_2 may include resource information (e.g., frequency resource allocation, time resource allocation, VRB (Virtual Resource Block) - PRB (Physical Resource Block) mapping, etc.), information related to transport blocks (TB) (e.g., MCS, NDI, RV, etc.), information related to HARQ (e.g., process number, DAI, PDSCH-HARQ feedback timing, etc.), information related to multiple antennas (e.g., antenna port, TCI (Transmission Configuration Indicator), SRS (Sound Reference Signal) request, etc.), information related to PUCCH scheduling regarding PDSCH (e.g., PUCCH power control, PUCCH resource indicator, etc.), and control information included in each DCI format can be predefined.

[0138] DCI format 1_0 is used to schedule PDSCH in a DL cell. The information included in DCI format 1_0 is a CRC scrambled and transmitted by C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0139] DCI format 1_1 is used to schedule PDSCH in a cell. The information included in DCI format 1_1 is a CRC scrambled and transmitted by C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0140] DCI format 1_2 is used to schedule PDSCH in a cell. The information contained in DCI format 1_2 is a CRC scrambled and transmitted by C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0141] Figure 7 An example is provided of a hybrid automatic repeat and request (HARQ) sending method that can be applied to this disclosure.

[0142] When multiple terminals in a wireless communication system have data to transmit via uplink (UL) / downlink (DL), the base station can select the terminal to which to transmit data for each TTI (transmission time interval) (e.g., subframe, time slot). In multi-carrier and similar wireless communication systems, the base station can select a terminal to transmit data via UL / DL for each TTI, or it can select the frequency band for the corresponding terminal to transmit data.

[0143] For example, a terminal can transmit an RS (or pilot signal) via UL, and the base station can use the RS (or pilot signal) transmitted from the terminal to determine the terminal's channel state. Additionally, the base station can select a terminal to transmit data in the UL within a unit frequency band for each TTI and send the selection result to the terminal. That is, the base station can send an uplink allocation message (i.e., a UL grant message) to a terminal scheduled for UL using a specific frequency band in a specific TTI.

[0144] The terminal can send data to the base station based on the UL authorization message. Here, the UL authorization message may include, for example, the terminal (or UE) identity, RB allocation information, MCS (modulation and coding scheme), redundancy version (RV) version, new data indication (NDI), etc.

[0145] HARQ can include DL HARQ and UL HARQ. DL HARQ can represent DL data on PDSCH sent along with a HARQ-ACK returned on PUCCH or PUSCH. UL HARQ can represent UL data on PUSCH sent along with a HARQ-ACK returned on PDCCH.

[0146] Multiple parallel HARQ processes can exist in a base station / terminal used for DL / UL transmission. Multiple parallel HARQ processes allow DL / UL transmissions to be executed continuously while waiting for HARQ feedback on the success or failure of previous DL / UL transmissions.

[0147] Each HARQ procedure can be associated with a HARQ buffer at the MAC (Media Access Control) layer. Each HARQ procedure can manage state variables related to the number of MAC PDUs (Physical Data Units) transmitted in the buffer, HARQ feedback of the MAC PDUs in the buffer, and the current redundancy version.

[0148] For example, when using 8-channel HARQ, the HARQ procedure ID can be provided as 0-7. In synchronous HARQ schemes, the HARQ procedure IDs can be sequentially linked to time units (TUs). On the other hand, in asynchronous HARQ schemes, the HARQ procedure ID can be specified by the network (e.g., the base station) during data scheduling. Here, the TU can be replaced by the data transmission timing (e.g., subframe, time slot).

[0149] In HARQ transmission schemes, asynchronous HARQ schemes may mean that there is no fixed time pattern for each HARQ process. That is, since the HARQ retransmission time is not predefined, the base station can send a retransmission request message to the terminal.

[0150] In HARQ transmission schemes, synchronous HARQ schemes can have a fixed time pattern for each HARQ process. That is, the HARQ retransmission time can be predefined. Therefore, the UL authorization message sent from the base station to the terminal can be sent only initially, and subsequent retransmissions can be performed via ACK / NACK signals.

[0151] In HARQ transmission schemes, in a non-adaptive HARQ scheme, the frequency resources or MCS used for retransmission are the same as in the previous transmission. However, in an adaptive HARQ scheme, the frequency resources or MCS used for retransmission may be different from the previous transmission. For example, in an asynchronous adaptive HARQ scheme, since the frequency resources or MCS used for retransmission are different for each transmission time, the retransmission request message may include the UE ID, RB allocation information, HARQ procedure ID / number, RV, and NDI information.

[0152] refer to Figure 7 The base station (BS) can send a UL grant message to the UE via the PDCCH. The UE can then send uplink data to the base station via the PUSCH using the RB and MCS specified in the UL grant message, after a predetermined time from the time the UL grant message is received.

[0153] here, Figure 7 Each of the base station and UE shown can correspond to the reference. Figure 12 One of the first device 100 or the second device 200 described.

[0154] The base station can decode the UL data received from the UE. When uplink data decoding fails, the base station can send a NACK to the UE. The UE can retransmit the UL data after a predetermined time from the time the NACK is received. The initial transmission and retransmission of UL data can be performed by the same HARQ procedure (e.g., HARQ procedure 4).

[0155] In a synchronous HARQ scheme, the scheduled time can have a fixed value. Alternatively, in a synchronous HARQ scheme, the scheduled time can be indicated by the PDCCH to PUSCH timing indication information in the UL authorization message.

[0156] Figure 8 An example is shown of the process for transmitting uplink control information that can be applied to this disclosure.

[0157] refer to Figure 8 (a) The UE can detect the PDCCH in slot #n. Here, the PDCCH includes DL scheduling information (e.g., DCI format 1_0, 1_1), and the PDCCH can indicate "DL allocation to PDSCH offset (K0)" and "PDSCH-HARQ-ACK report offset (K1)".

[0158] Here, each of K0 and K1 can be indicated by the "Time Domain Resource Allocation (TDRA) field" and the "PDSCH to HARQ Feedback Timing Indicator field" of DCI formats 1_0 and 1_1.

[0159] Specifically, the "TDRA field" can indicate the start position (e.g., OFDM symbol index) and length (e.g., number of OFDM symbols) of the PDSCH in the time slot. The "PDSCH to HARQ Feedback Timing Indicator field" can indicate the position where HARQ-ACK reporting begins after the PDSCH is received.

[0160] Furthermore, DCI formats 1_0 and 1_1 include a "PUCCH Resource Indicator (PRI) field", which indicates the PUCCH resource to be used for UCI transmission that is included among multiple PUCCH resources in the PUCCH resource set.

[0161] After receiving the PDSCH from the base station in time slot #(n+K0) based on the scheduling information of time slot #n, the UE can send UCI to the base station via PUCCH in time slot #(n+K1).

[0162] Here, the UCI can include HARQ-ACK feedback for the PDSCH. When the PDSCH is configured to transmit a maximum of 1TB, the HARQ-ACK feedback can be configured to 1 bit. When the PDSCH is configured to transmit a maximum of two TB, the HARQ-ACK bit can be configured to 2 bits without spatial binding and 1 bit with spatial binding configured. When the HARQ-ACK transmission time for multiple PDSCHs is specified as time slot #(n+K1), the UCI transmitted in time slot #(n+K1) can include HARQ-ACK responses for multiple PDSCHs.

[0163] refer to Figure 8 (b) The UE can detect the PDCCH in time slot #n. Here, the PDCCH may include uplink scheduling information (e.g., DCI format 0_0, 0_1).

[0164] The DCI formats 0_0 and 0_1 may include a Frequency Domain Resource Allocation (FDRA) field indicating the set of RBs allocated to the PUSCH, a slot offset (K2), and a Time Domain Resource Allocation (TDRA) field indicating the start position (e.g., OFDM symbol index) and length (e.g., number of OFDM symbols) of the PUSCH within the slot. Here, the start position and length of the PUSCH can be indicated together by start and length indication values ​​(SLIV) or they can be indicated separately.

[0165] The UE can send PUSCH to the base station in time slot #(n+K2) according to the scheduling information of time slot #n. Here, PUSCH may include UL-SCH TB. When the PUCCH transmission time and PUSCH transmission time overlap, UCI can be sent through PUSCH (i.e., piggybacked on PUSCH).

[0166] Dynamic / Semi-static HARQ-ACK Codebook Configuration Method

[0167] In wireless communication systems, dynamic HARQ-ACK codebook configurations (e.g., Type 2 HARQ-ACK codebooks) and semi-static HARQ-ACK codebook configurations (e.g., Type 1 HARQ-ACK codebooks) may be supported. In describing this disclosure, the HARQ-ACK (or A / N) codebook may be replaced by a HARQ-ACK payload.

[0168] When the dynamic HARQ-ACK codebook configuration method is configured, the size of the A / N payload can vary depending on the actual amount of DL data scheduled. Therefore, the PDCCH associated with DL scheduling can include a counter DAI (Downlink Allocation Index) and a total DAI.

[0169] The counter DAI indicates the {CC,slot} scheduling order value calculated using the CC (component carrier) (or cell) first method, and can be used to specify the position of the A / N bits in the A / N codebook. The total DAI represents the cumulative time slot unit scheduling value up to the current time slot, and can be used to determine the size of the A / N codebook.

[0170] When a semi-static A / N codebook configuration method is configured, the size of the A / N codebook can be fixed (up to the maximum value) and is independent of the actual amount of scheduled DL data.

[0171] Specifically, the (maximum) A / N payload (size) transmitted via a PUCCH in a time slot can be determined as the number of A / N bits corresponding to the combination of all CCs configured for the UE and all DL scheduling time slots (or PDSCH transmission time slots or PDCCH monitoring time slots) that can indicate the timing of A / N transmission to it (hereinafter referred to as the bundled window).

[0172] For example, the DL-licensed DCI includes PDSCH-to-A / N timing information, and the PDSCH-to-A / N timing information can have one of several values ​​(e.g., k). For example, when a PDSCH is received in time slot #m and the PDSCH-to-A / N timing information in the DL-licensed DCI (PDCCH) that schedules the PDSCH indicates k, the A / N information for the PDSCH can be sent in time slot #(m+k).

[0173] As an example, k∈{1,2,3,4,5,6,7,8} can be given. When A / N information is transmitted in time slot #n, the A / N information can include the maximum possible A / N based on the bundling window. That is, the A / N information for time slot #n can include the A / N corresponding to time slot #(nk).

[0174] For example, if k∈{1,2,3,4,5,6,7,8}, then the A / N information for time slot #n includes the A / N corresponding to time slots #(n-8) to #(n-1) (i.e., the maximum number of A / Ns), and is independent of the actual DL data reception. Here, the A / N information can be replaced by the A / N codebook and the A / N payload.

[0175] Additionally, time slots can be understood / replaced as candidate timings for DL ​​data reception. As an example, the bundling window can be determined based on the PDSCH to A / N timing according to the A / N time slot, and the PDSCH to A / N timing set can have predefined values ​​(e.g., {1,2,3,4,5,6,7,8}) or can be configured by higher-layer (RRC) signaling.

[0176] HARQ-ACK codebook configuration method based on time-bundled interval configuration

[0177] To improve the transmission efficiency of the scheduling DCI for PDSCH, multiple PDSCHs can be scheduled using a single DCI. For the convenience of this disclosure, the corresponding DCI will be referred to as M-DCI, and the DCI used for scheduling a single PDSCH will be referred to as S-DCI. However, a single PDSCH can be scheduled by M-DCI.

[0178] For example, when a Time Domain Resource Allocation (TDRA) entry for M-DCI is configured, suppose there is only one SLIV linked to row index #A, and multiple SLIVs linked to another row index #B. When row index #A is indicated by M-DCI, M-DCI can schedule only a single PDSCH. On the other hand, when row index #B is indicated by M-DCI, M-DCI can schedule multiple PDSCHs.

[0179] Furthermore, for the sake of clarity in describing this disclosure, the case where the PDSCH is scheduled by S-DCI and the case where only one PDSCH is scheduled by M-DCI (or, when the SPS PDSCH is released, the secondary cell (SCell) sleeps or the TCI status is updated by DCI) are referred to as the single PDSCH case. The case where multiple PDSCHs are scheduled by M-DCI is referred to as the multi-PDSCH case.

[0180] Additionally, when time binding is configured in addition to M-DCI, the number of binding groups can be defined as G. For example, when multiple PDSCHs are scheduled via M-DCI in a cell where G is configured as 1, this can be called a single PDSCH case. And when multiple PDSCHs are scheduled via M-DCI in a cell where G is configured as a value greater than 1, this can be called a multi-PDSCH case.

[0181] On the other hand, considering the 480 / 960kHz SCS applicable to the FR 2-2 band (or FR 3 band) (e.g., 52.6GHz or higher), the absolute time of PDSCH transmission can be very short when multiple PDSCHs are scheduled in multiple time domains (e.g., time slot domains) via M(multi)-DCI. Since the channel information associated with multiple PDSCHs may not change significantly in the corresponding time domains, the decoding results of multiple PDSCHs for the UE may be identical.

[0182] When configuring time-bundling periods taking the above factors into account, HARQ-ACK information / results of PDSCH within the corresponding time-bundling period can be bundled (e.g., performing a logical AND operation on the HARQ-ACK information), thus reducing the HARQ-ACK payload. The time-bundling method will be described in detail below.

[0183] As method 1, time bundling can be performed based on the number of PDSCHs scheduled. For example, when scheduling M or fewer PDSCHs, the corresponding PDSCHs can be bundled into one group. When scheduling more than M PDSCHs, the PDSCHs can be divided into two groups and bundled.

[0184] In this scenario, the M value can be half the maximum number of PDSCHs that can be scheduled by the M-DCI configured in the corresponding cell (or all cells configured for the UE). When half the maximum number of PDSCHs is not an integer, the M value can be an integer obtained by applying a floor function, a ceiling function, or rounding to half the maximum number of PDSCHs. However, this is only one implementation method, and the M value can be configured via higher-layer signaling.

[0185] Specifically, when the actual number of PDSCHs scheduled is N (in this case, N>M), the first M PDSCHs can be bundled into group 1, and the remaining NM PDSCHs can be bundled into group 2. As another example, the first ceil (N / 2) PDSCHs can be bundled into group 1, while the remaining floor (N / 2) PDSCHs can be bundled into group 2.

[0186] As a second method, time bundling can be performed based on the number of time slots occupied by the PDSCH. For example, when scheduling L or fewer PDSCHs, the corresponding PDSCHs can be bundled into one group. When scheduling more than L PDSCHs, the PDSCHs can be divided into two groups and bundled.

[0187] In this scenario, the L value can be half the maximum number of PDSCH slots that the M-DCI configured in the corresponding cell (or all cells configured for the UE) can schedule. When half the maximum number of PDSCHs is not an integer, the M value can be an integer obtained by applying a floor function, a ceiling function, or rounding to half the maximum number of PDSCHs. However, this is only one implementation method, and the L value can be set via higher-layer signaling.

[0188] Specifically, when the time slot duration from the first time slot of the first PDSCH to the last time slot of the actually scheduled PDSCH consists of K (K>L) time slots, the PDSCHs in the first L time slot durations can be bundled into group 1, and the PDSCHs in the remaining KL time slot durations can be bundled into group 2. As another method, the PDSCHs in the first ceil (K / 2) time slot durations can be bundled into group 1, and the PDSCHs in the remaining floor (K / 2) time slot durations can be bundled into group 2.

[0189] As method 3, regardless of the number of PDSCHs and the number of time slots, PDSCHs can be bundled into two groups by time. For example, when the actual number of scheduled PDSCHs is N, the first ceil (N / 2) PDSCHs can be bundled into group 1, and the remaining floor (N / 2) PDSCHs can be bundled into group 2.

[0190] Alternatively or alternatively, G groups can be created. And, based on the scheduled (or valid) order, PDSCH can be mapped to each group (e.g., in ascending order of group index).

[0191] As an example, when 5 PDSCHs are scheduled (or active) and G is configured to 4, PDSCH#0 / #4 can correspond to (or map) group #0, PDSCH#1 can correspond to group #1, PDSCH#2 can correspond to group #2, and PDSCH#3 can correspond to group #3. In this case, an active PDSCH may mean a PDSCH that does not overlap with symbols (or time slots including the corresponding symbols) configured as uplink (or flexible) by parameters associated with TDD UL / DL configuration (e.g., 'tdd-UL-DL-ConfigurationCommon' or / and 'tdd-UL-DL-ConfigurationDedicated').

[0192] An example of two groups in methods 1 through 3 is described. However, this is only one implementation method, and the operations / information according to methods 1 through 3 can be applied even when the number of groups exceeds one or two.

[0193] Configuration method for type 1 HARQ-ACK codebook when time binding is configured

[0194] Among multiple PDSCHs scheduled by M-DCI, the K1 value can be applied based on the time slot (in the time domain) of the last PDSCH sent.

[0195] Here, the K1 value refers to the time slot interval between the PDSCH transmission time slot used for corresponding PDSCH reception and the HARQ-ACK transmission time slot, and can be indicated by DCI.

[0196] That is, the HARQ-ACK timing (slot) can be determined by applying K1 based on the slot in which the last PDSCH is sent among multiple PDSCHs scheduled by M-DCI. In addition, HARQ-ACK feedback for all multiple PDSCHs scheduled from M-DCI can be sent centrally at the corresponding HARQ-ACK timing (the same timing).

[0197] Therefore, HARQ-ACK feedback for all multiple PDSCHs scheduled by the M-DCI (or / and S-DCI indicating the HARQ-ACK timing corresponding to the time slot for sending the last PDSCH) can be reused. Furthermore, all multiplexed HARQ-ACKs can be sent within the same single HARQ-ACK timing.

[0198] As an example, suppose a set of multiple (e.g., K_N) K1 value candidates are configured. In the case of a Type 1 HARQ-ACK codebook in a basic wireless communication system, the timing of receiving candidate PDSCHs corresponding to each DL slot (including determining the position / order of the HARQ-ACK bits corresponding to each SLIV) can be configured by calculating the combination of all PDSCH timings (SLIVs) that can be transmitted in the preceding DL slot (e.g., K1 DL slots) for transmitting the HARQ-ACK corresponding to each (configured for each serving cell) K1 value. (i.e., SLIV pruning)

[0199] Here, SLIV is an indicator value for the starting symbol index and the number of symbols in the time slot of PDSCH and / or PUSCH. It can be configured to constitute a component of the entry in the PDCCH used to schedule the TDRA field of the corresponding PDSCH and / or PUSCH.

[0200] HARQ-ACK information bits can be configured for each timing included in the candidate PDSCH reception timing set. Since the HARQ-ACK information is concatenated as shown in Table 6 below, the entire HARQ-ACK codebook can be configured.

[0201] [Table 6]

[0202]

[0203]

[0204] The following section describes how to configure a type 1 HARQ-ACK codebook when time binding is configured.

[0205] First, SLIV pruning can be performed based on the last SLIV (in each row of the TDRA table). For each DL slot corresponding to K1, if any of the TDRA row indices corresponding to K1 after SLIV pruning requires G groups, up to (G-1) time slots can be added to the SLIV pruning result.

[0206] For example, a TDRA entry for an M-DCI in a specific cell may include row index #0 and row index #1. In this case, with row index #0, five SLIV values ​​can be linked, and the last SLIV can be configured as {S=0, L=5}. And with row index #1, three SLIV values ​​are linked, and the last SLIV can be configured as {S=2, L=5}. Here, S can represent the start symbol, and L can represent the symbol length.

[0207] Additionally, the TDRA entry for the S-DCI in the corresponding cell can include row index #0, and the SLIV corresponding to row index #0 can consist of {S=9, L=5}.

[0208] When SLIV pruning is performed using only the last SLIV of a specific DL time slot corresponding to a specific K1 of the corresponding cell, two opportunities for receiving candidate PDSCHs can be allocated to the corresponding DL time slot.

[0209] When two groups are configured as in Method 1 above and M is configured as 4, since at least row index #0 requires these two groups, the number of opportunities for receiving candidate PDSCH in the final corresponding DL slot can be three.

[0210] For example, when M-DCI schedules row index #0 or row index #1, the HARQ-ACK information associated with row index #0 or row index #1 can correspond to the first two of multiple timings.

[0211] Here, in the case of row index #1, since there is no PDSCH corresponding to the second group, the second timing can be filled with NACK. And when row index #0 is scheduled by S-DCI, the HARQ-ACK information (corresponding to S-DCI) can correspond to the third timing.

[0212] As another example, the TDRA entry for M-DCI in a specific cell may include row index #0 and row index #1. In this case, with row index #0, five SLIV values ​​can be linked, and the last SLIV can be configured as {S=9, L=5}. And with row index #1, three SLIV values ​​are linked, and the last SLIV can be configured as {S=10, L=4}.

[0213] Additionally, the TDRA entry for the S-DCI in the corresponding cell may include row index #0, and the SLIV corresponding to row index #0 may consist of {S=0, L=5}.

[0214] When SLIV pruning is performed using only the last SLIV of a specific DL slot corresponding to a specific K1 for the corresponding cell, two opportunities for candidate PDSCH reception can be allocated to the corresponding DL slot.

[0215] When two groups are configured as described in Method 1 above and M is configured as 4, since both groups require at least row index #0, the number of candidate PDSCH reception opportunities in the corresponding DL time slot can be 3.

[0216] When M-DCI schedules row index #0 or row index #1, the HARQ-ACK information associated with row index #0 or row index #1 can correspond to the first and third timings among multiple timings.

[0217] In this scenario, for row index #1, since there is no PDSCH corresponding to the second group, the third timing can be filled with NACK. Furthermore, when S-DCI schedules row index #0, the HARQ-ACK information associated with row index #0 can correspond to the second timing.

[0218] That is, when SLIV pruning is performed using only the last SLIV, the timing can first be assigned to row index #0 corresponding to the S-DCI. And, since the next timing is assigned to row index #0 / 1 corresponding to the M-DCI, a total of two timings can be configured / assigned. Furthermore, since the timing based on time binding is configured before the corresponding two timings, a total of three timings can be assigned to the corresponding DL slots.

[0219] M-DCI-based type 2HARQ-ACK codebook configuration method

[0220] In the case of S-DCI in a basic wireless communication system, the counter DAI (C-DAI) and the total DAI (T-DAI) value can be counted in units of 1 for each DCI or each PDSCH. In the case of M-DCI, since there may be multiple PDSCHs corresponding to a DCI, the method for counting the DAI value may differ. For example, the DAI value can be counted per DCI, per PDSCH, or in units of W PDSCHs.

[0221] The following describes the method for configuring the HARQ-ACK codebook for each DCI count DAI value, as well as the method for configuring a single codebook / separate sub-codebook (sub-CB) for single PDSCH and multiple PDSCH cases.

[0222] In describing this disclosure, configuring separate sub-CBs may mean that the C / T-DAI value for each sub-CB is determined independently and signaled (i.e., the DCI / PDSCH order / total number scheduled for each sub-CB is determined independently / signed).

[0223] For example, configuring separate sub-CBs for single PDSCH and multi-PDSCH cases may mean that the C / T-DAI value is determined and signaled independently for each of the single PDSCH and multi-PDSCH cases (i.e., the DCI / PDSCH order / total number scheduled for each case is determined / signed independently).

[0224] That is, the DCI corresponding to the single PDSCH case can be signaled by determining the DAI value only for the single PDSCH case, and the DCI corresponding to the multi-PDSCH case can be signaled by determining the DAI value only for the multi-PDSCH case.

[0225] In addition, HARQ-ACK payloads corresponding to different sub-CBs can be concatenated to form the final HARQ-ACK codebook.

[0226] Furthermore, configuring a single CB may mean that a common C / T-DAI value is determined and signaled (i.e., the DCI / PDSCH order / total number for a single CB scheduling is determined and signaled).

[0227] For example, configuring a single CB for single PDSCH and multiple PDSCH cases may mean counting and signaling the C / T-DAI value by grouping single PDSCH and multiple PDSCH cases (i.e., the DCI / PDSCH order / total is determined / signaled to the scheduler without distinguishing between each case).

[0228] Methods for configuring a single CB for single / multiple PDSCH scenarios

[0229] The following section describes a method for configuring a single codebook when counting the DAI for each DCI. Specifically, it describes methods for configuring a single codebook for both single PDSCH and multi-PDSCH scenarios.

[0230] In this case, M-DCI can maintain the existing DL DAI size (i.e., 2 bits per C / T-DAI), S-DCI can maintain the existing DL DAI size, and UL licensing can maintain the existing UL DAI size (i.e., 2 bits per T-DAI).

[0231] Furthermore, the HARQ-ACK payload can be determined by the maximum number (Y) of PDSCHs that M-DCI can schedule.

[0232] For example, for a cell configured with 2 TB (transport blocks) and without spatial bonding, 2 bits can be calculated / allocated for each PDSCH (2 bits per PDSCH). Furthermore, for a cell configured with 2 TB but with spatial bonding, or a cell configured with 1 TB, 1 bit can be calculated / allocated for each PDSCH.

[0233] That is, when calculating / allocating X bits for each PDSCH (where X is the number of TBs and can be 1 or 2, depending on the space bundling configuration), the number of HARQ-ACK bits corresponding to one DAI can be calculated as X*Y for both single PDSCH and multi-PDSCH cases.

[0234] For example, when configuring M-DCI for multiple cells (in a cell group), the number of HARQ-ACK bits for each DAI can be determined by the maximum X*Y value in any cell.

[0235] Method for configuring a single CB (codebook) when time binding is configured.

[0236] The following describes the method for configuring a single CB for both single PDSCH and multiple PDSCH scenarios when counting the DAI for each DCI and configuring time binding. Specifically, it describes the method for configuring a type 2 HARQ-ACK codebook when time binding is configured.

[0237] In this case, M-DCI can maintain the existing DL DAI size (i.e., 2 bits per C / T-DAI), S-DCI can maintain the existing DL DAI size, and UL licensing can maintain the existing UL DAI size (i.e., 2 bits per T-DAI).

[0238] The HARQ-ACK payload can be determined by the (maximum) number of groups (G) configured for time bundling. For both single PDSCH and multi-PDSCH cases, the number of HARQ-ACK bits corresponding to one DAI can be G (or X*G) (where X is the number of TBs set to 1 or 2 depending on the spatial bundling configuration).

[0239] For example, if M-DCI is configured for multiple cells (within a cell group), the number of HARQ-ACK bits for each DAI can be determined by the maximum G (or X*G) value in any cell. For example, NACK can be mapped when the PDSCH corresponding to a specific time-bundled group does not exist.

[0240] Methods for configuring separate CBs for single / multiple PDSCH scenarios

[0241] The following describes how to configure a subcodebook corresponding to the single PDSCH case and another sub-CB corresponding to the multiple PDSCH case when counting the DAI of each DCI.

[0242] In this case, M-DCI can maintain the existing DL DAI size (i.e., 2 bits per C / T-DAI), S-DCI can maintain the existing DL DAI size, and for the existing UL DAI size, UL licensing may require an additional 2 bits of T-DAI (for the additional sub-CB).

[0243] Furthermore, in the case of a sub-CB corresponding to a single PDSCH scenario, the number of HARQ-ACK bits per DAI can be X (where X is the number of TBs and is configured to be 1 or 2 depending on the spatial bundling configuration). Also, in the case of a sub-CB corresponding to a multi-PDSCH scenario, the number of HARQ-ACK bits per DAI can be the maximum X*Y value among any cell (in a cell group).

[0244] Methods for configuring separate CBs for single / multiple PDSCH scenarios when establishing a CBG

[0245] The following describes how to configure individual CBs for single / multiple PDSCH cases when counting the DAI for each DCI and configuring CBG (code block group).

[0246] Here, a CBG (Block Group) is a group of one or more CBs. Specifically, a PDSCH (Programmable Scripting Chain) can carry one or more TBs (Blocks of Code). TBs can be compiled into codewords (CWs) and then transmitted through scrambling and modulation processes. A CW consists of one or more code blocks (CBs). More than one CB can be bundled into a CBG.

[0247] Option 1

[0248] When scheduling a TB-based PDSCH in a single PDSCH scenario, a corresponding first sub-CB can be configured. When scheduling a TB-based PDSCH in a multi-PDSCH scenario, a corresponding second sub-CB can be configured. When scheduling a CBG-based PDSCH in a single PDSCH scenario, a corresponding third sub-CB can be configured.

[0249] When a CBG is configured in a cell with M-DCI, the DAI in the M-DCI under the single PDSCH scenario can indicate the C / T-DAI value of the PDSCH based on the CBG. If no CBG is configured in a cell with M-DCI, the DAI in the M-DCI under the single PDSCH scenario can indicate the C / T-DAI value of the PDSCH based on the TB.

[0250] S-DCI or M-DCI can maintain the existing DL DAI size. In addition, for the existing UL DAI size (for two additional sub-CBs), UL licensing may require an additional 4 bits of T-DAI (i.e., 2 bits of T-DAI for each sub-CB).

[0251] Furthermore, in the case of scheduling TB-based PDSCHs in a single PDSCH scenario, the payload of the first sub-CB can be the same as that of the sub-CB corresponding to the single PDSCH scenario described above. The payload of the second sub-CB configured for the multi-PDSCH scenario can be the same as that of the sub-CB corresponding to the multi-PDSCH scenario described above. In the case of a single PDSCH, the payload of the third sub-CB configured for CBG-based PDSCH scheduling can be the same as the payload of the existing CBG-based sub-CB configuration.

[0252] Option 2

[0253] When scheduling TB-based PDSCH in a single PDSCH scenario, a first sub-CB can be configured. Additionally, CBG-based PDSCH scheduling in both multi-PDSCH and single-PDSCH scenarios can be integrated to form a second sub-CB.

[0254] When a CBG is configured in a cell with M-DCI, the DAI in the M-DCI can indicate the C / T-DAI value of the second sub-CB in a single PDSCH scenario. When no CBG is configured in a cell with M-DCI, the DAI in the M-DCI can indicate the C / T-DAI value of the first sub-CB in a single PDSCH scenario. Furthermore, the S-DCI, M-DCI, or UL authorization may be the same as in Option 1.

[0255] Furthermore, when the maximum number of CBGs configured is C, the HARQ-ACK payload can be configured using the maximum value of C (max_C) corresponding to any cell (within a cell group) and the maximum value of X*Y (max_XY) corresponding to any cell (within a cell group). That is, for both single PDSCH and multi-PDSCH scenarios, the number of HARQ-ACK bits corresponding to the second sub-CBG can be determined as max{max_C, max_XY}.

[0256] Additionally, for the first sub-CB, the number of HARQ-ACK bits per DAI can be X (where X is the number of TBs and is configured to be 1 or 2 depending on the space bundling configuration).

[0257] PUCCH power control method in HARQ-ACK feedback

[0258] In the following text, the method for controlling the power of the PUCCH will be described when sending HARQ-ACK feedback configured according to M-DCI and / or CBG via the PUCCH.

[0259] In wireless communication systems, millimeter-wave bands (e.g., 7.125 GHz or 24.25 GHz or higher, up to 52.6 GHz) can be defined as frequency range (FR)2 (or FR2-1). The subcarrier spacing (SCS) of the SS / PBCH block in the corresponding frequency band can be 120 kHz or 240 kHz, and the SCS of other signals / channels (e.g., PDCCH, PDSCH, PUSCH, etc.) can be 60 kHz or 120 kHz.

[0260] Larger SCSs can be used in the frequency band of high-frequency wireless communication systems (FR 2-2) (e.g., 52.6 GHz or higher, up to 71 GHz). While maintaining the scalability of OFDM symbol duration and CP length as defined in current wireless communication systems, the OFDM symbol duration and CP length of each SCS can be defined as shown in Table 7 below.

[0261] [Table 7]

[0262] SCS[kHz] 120 240 480 960 Symbol duration 8.33us 4.17us 2.08us 1.04us CP length 586ns 293ns 146ns 73ns

[0263] Considering the UE's monitoring capabilities in the FR2-2 band, PDCCH monitoring can be performed in a single time slot, with multiple time slots as a unit. Therefore, considering the reduced PDCCH monitoring opportunity area, multiple PDSCHs can be scheduled through a single DCI. However, PDSCHs indicated / scheduled by the corresponding DCI can be indicated / scheduled to be transmitted not only in the FR2-2 band but also in other FR bands.

[0264] That is, the M-DCI described in this disclosure is not limited to wireless communication systems operating in FR2-2, but can be extended and applied to wireless communication systems operating in other frequency bands.

[0265] When configuring a Type 2 codebook in a basic wireless communication system, if the total number of HARQ-ACK bits is 11 or less, the calculation of the HARQ-ACK information bits is shown in Tables 8 to 10 below. The transmission power of PUCCH can be determined based on the calculated HARQ-ACK information bits.

[0266] [Table 8]

[0267]

[0268]

[0269] [Table 9]

[0270]

[0271]

[0272] [Table 10]

[0273]

[0274]

[0275] In equations (1) and (2) included in Tables 8 and 10, 'n HARQ-ACK The value can be determined based on the number of PDSCHs (or TBs) actually received (the first element of each equation) and the number of PDSCHs (or TBs) lost (the second element of each equation) (which differs from the actual CB size).

[0276] In this disclosure, modifications to the calculation of n will be described when M-DCI and / or CBG are configured. HARQ-ACK The method of equality of values.

[0277] Figure 9 This is a flowchart illustrating a method for a terminal (or user equipment (UE)) to perform downlink reception and uplink transmission according to an embodiment of the present disclosure.

[0278] The UE can receive first configuration information S910 related to time domain binding from the base station.

[0279] For example, when the time-bundling period is configured by the first configuration information, the HARQ-ACK information in the time-bundling period (or duration) is bundled (e.g., bundled by AND operation, etc.) and reported to the base station, thereby reducing the HARQ-ACK payload.

[0280] As an example, the first configuration information may include 'enableTimeDomainHARQ' or 'timeDomainHARQ-BundlingType1', but is not limited to these.

[0281] The UE can receive at least one PDSCH S920 from the base station at at least one Physical Downlink Shared Channel (PDSCH) reception time.

[0282] Specifically, the UE may receive a PDSCH scheduled by the DCI at one or more PDSCH reception times, the DCI indicating a TDRA line including one or more SLIV entries. One or more PDSCHs may include one or more transport blocks.

[0283] The UE can send a PUCCH (S930) to the base station, which includes HARQ-ACK information for at least one PDSCH.

[0284] As an example, the UE can generate a HARQ-ACK codebook by cascading HARQ-ACK information for at least one PDSCH, and send a PUCCH including the generated HARQ-ACK codebook to the base station.

[0285] As another example, HARQ-ACK information within the time-binding period configured in the first configuration information is bound (e.g., bound via AND operation, etc.), and the UE can send a PUCCH including the bound HARQ-ACK information to the base station.

[0286] Here, the transmission power of PUCCH can be based on a specific PDSCH within at least one PDSCH. That is, the transmission power of PUCCH can be based on specific PDSCH-related information (e.g., the number of specific PDSCHs or the number of TBs included in a specific PDSCH).

[0287] The transmit power of the PUCCH can use information related to a specific PDSCH. and the number of CBGs received from the base station at at least one PDSCH reception time. To obtain it. That is, the UE can obtain it by using... and sum(n HARQ-ACK To obtain the transmit power of PUCCH.

[0288] In this case, the number of bits of the UCI payload included in the PUCCH can be 11 or less. The UCI payload may include at least one of HARQ-ACK information, scheduling request (SR) information, and channel state information (CSI) information.

[0289] A specific PDSCH can be associated with the last SLIV among at least one SLIV (entry) included in the TDRA line indicated by the DCI. That is, the UE can consider only the specific PDSCH associated with the last SLIV among at least one PDSCH as a PDSCH related to PUCCH transmission power. A PDSCH related to PUCCH transmission power can refer to the PDSCH used for transmitting power from... Calculate / Obtain PDSCH.

[0290] Additionally, when the PDSCH received at at least one PDSCH timing does not correspond to the last SLIV, the UE may not regard that PDSCH (i.e., the remaining PDSCHs in at least one PDSCH other than the specific PDSCH) as a PDSCH related to the PUCCH transmission power.

[0291] As an example, the transmission power of PUCCH can be based on the number of transport blocks (TBs) included in a particular PDSCH, based on the second configuration information related to spatial bundling not received from the base station and the third configuration information related to code block group (CBG) transmission.

[0292] As another example, the transmit power of the PUCCH can be based on the number of specific PDSCHs, based on the second configuration information related to bundling received from the base station.

[0293] As another example, based on third configuration information related to code block group (CBG) transmission received from the base station and DCI that does not support CGB-based PDSCH reception, the transmit power of PUCCH can be based on the number of TBs included in a particular PDSCH.

[0294] Figure 10 This is a diagram used to describe the downlink transmission and uplink reception operations of a base station in a wireless communication system to which the present disclosure may be applied.

[0295] The base station can send first configuration information S1010 related to time domain binding to the UE.

[0296] The base station may send at least one PDSCH S1020 to the UE at at least one PDSCH reception time.

[0297] The base station can receive PUCCH S1030 from the UE, which includes HARQ-ACK information for at least one PDSCH.

[0298] In this case, the transmission power of the PUCCH can be based on a specific PDSCH among at least one PDSCH. The specific PDSCH can be associated with the last SLIV among at least one SLIV included in the TDRA line indicated by the DCI.

[0299] The operations and related parameters associated with S1010, S1020 and S1030 correspond to S910, S920 and S930, and repeated descriptions will be omitted.

[0300] The following section will describe in detail a method for controlling the transmission power of the PUCCH, which includes HARQ-ACK information.

[0301] Implementation Method 1

[0302] Implementation 1 involves calculating n when configuring one sub-CB corresponding to a single PDSCH case and another sub-CB corresponding to a multi-PDSCH case. HARQ-ACK The method for determining the value.

[0303] Because separate sub-CBs can be configured for each case, n HARQ-ACK The final value can be derived from n corresponding to the single PDSCH case. HARQ-ACK,S-PDSCH The value of n corresponding to the multiple PDSCH case HARQ-ACK,M-PDSCH The sum of the values ​​is obtained.

[0304] Specifically, n HARQ-ACK,S-PDSCH The value can be configured according to Equation 3 below, similar to Equation (1) in Table 8.

[0305] [Equation 3]

[0306]

[0307] here, It can represent the total (or counter) DAI value indicated in the last DCI format corresponding to a single PDSCH case.

[0308] U DAI,c It can indicate the total number of DCI formats corresponding to a single PDSCH case (detected by the UE during all M PDCCH times).

[0309] It can represent the total number of PDSCHs or TBs scheduled by DCI corresponding to a single PDSCH case.

[0310] For example, based on the lack of provided spatial bundling configuration information related to PUCCH (e.g., 'harq-ACK-SpatialBundlingPUCCH'), This can indicate the number of TBs for DCI scheduling corresponding to a single PDSCH case. As another example, based on the provided space bundling configuration information related to PUCCH, It can indicate the total number of PDSCHs scheduled for DCI corresponding to a single PDSCH case.

[0311] The remaining parameters can be the same as those disclosed in Tables 8 to 10.

[0312] As an example, when time binding is configured for serving cell c, including multiple PDSCH scenarios or M-DCI, This is the total number of PDSCHs or TBs scheduled by DCI for a single PDSCH case, plus the number of M-DCIs (received at PDCCH monitoring time m), where the M-DCI is scheduled for cells configured with G=1 (e.g., serving cell c) (i.e., the 'maxNrofCodeWordsScheduledByDCI' value of cells configured with G=1) (except when multiple PDSCHs are scheduled via M-DCI). 'maxNrofCodeWordsScheduledByDCI' can indicate the maximum number of codewords that a single DCI can schedule.

[0313] As another example, suppose that for a serving cell c configured with M-DCI, time binding is configured to 1. This occurs when 'maxNrofCodeWordsScheduledByDCI' is 2 and spatial binding configuration information related to PUCCH is provided, or when G is configured to 1 for a cell with 'maxNrofCodeWordsScheduledByDCI' value of 1. It can be the following value: the number of M-DCIs (received at PDCCH monitoring time m) plus the total number of PDSCHs or TBs scheduled by DCIs corresponding to a single PDSCH case (except when multiple PDSCHs are scheduled via M-DCI).

[0314] As another example, in a cell where the value of 'maxNrofCodeWordsScheduledByDCI' is 2 and G is configured as 1, without providing spatial bundling configuration information related to PUCCH, It can be the following value: twice the number of M-DCIs (received at PDCCH monitoring time m) plus the total number of PDSCHs or TBs scheduled by DCIs corresponding to a single PDSCH case (except when multiple PDSCHs are scheduled via M-DCIs).

[0315] As another example, when configuring time binding for a serving cell c with DCI configured (e.g., the G value is configured to 1), the 'maxNrofCodeWordsScheduledByDCI' value is 2 and provides spatial binding information related to PUCCH, or when the 'maxNrofCodeWordsScheduledByDCI' value is 1, It can represent the number of DCIs (received at PDCCH monitoring time m).

[0316] Additionally, when the 'maxNrofCodeWordsScheduledByDCI' value is 2 and no space binding information related to PUCCH is provided, This can represent twice the number of DCIs (received at PDCCH monitoring time m).

[0317] Here, the number of M-DCI or DCI can be replaced with the number of (bundled) HARQ-ACK bits.

[0318] n HARQ-ACK,M-PDSCH The value can be configured as Equation 4, similar to Equation (2) in Table 10.

[0319] [Equation 4]

[0320]

[0321] here, It can represent the total (or counter) DAI value indicated in the last DCI format corresponding to the multi-PDSCH case.

[0322] It can indicate the number of serving cells configured with M-DCI (or, the number of binding groups configured with M-DCI and G>1, or the number of serving cells configured with M-DCI but without time binding).

[0323] It can indicate the total number of DCI formats corresponding to multiple PDSCH scenarios (detected by the UE during all M PDCCH events).

[0324] It can indicate the total number of PDSCHs or TBs received (or scheduled) by DCI (received at PDCCH monitoring time m) corresponding to multiple PDSCH cases.

[0325] For example, based on the lack of provided spatial bundling configuration information related to PUCCH (e.g., 'harq-ACK-SpatialBundlingPUCCH'), This can indicate the number of TBs in the DCI scheduling corresponding to a multi-PDSCH scenario. As another example, based on the provided space bundling configuration information related to PUCCH, It can indicate the total number of PDSCHs in the DCI scheduling corresponding to the multi-PDSCH case.

[0326] This can be determined as the maximum X*Y value within any cell (in a cell group). Here, Y can represent the maximum number of PDSCHs that can be scheduled for each serving cell using the M-DCI configured for that cell. Furthermore, X can be 1 when PUCCH spatial binding is configured for the serving cell (or when 'maxNrofCodeWordsScheduledByDCI' is 1). And X can be 2 when 'maxNrofCodeWordsScheduledByDCI' is 2 and PUCCH spatial binding is not configured for the serving cell.

[0327] The remaining parameters can be the same as those disclosed in Tables 8 to 10.

[0328] As an example, for a multi-PDSCH scenario, assume the time binding is configured as G>1. The following will describe the calculation of n for a serving cell c configured with the corresponding time binding. HARQ-ACK,M-PDSCH When calculating the value and The method for determining the value.

[0329] X can be determined as the maximum X*G value within any cell (in a cell group). Here, G can represent the (maximum) number of groups configured via time-binding (configured individually for each serving cell or collectively for serving cells). Furthermore, if PUCCH spatial binding is configured for the serving cell, X can be 1, and if PUCCH spatial binding is not configured for the serving cell, X can be 2.

[0330] At this point, for cells that have configured M-DCI but not time binding, the value of G can be replaced with the maximum number of PDSCHs (Y) that the corresponding M-DCI can schedule.

[0331] That is, for cells among multiple cells configured with M-DCI (within a PUCCH cell group) that are not configured with time binding, or cells configured with time binding and configured with a G greater than 1 (the number of PDSCH groups performing time binding), The value can be determined by the maximum of the Q values ​​calculated for each cell.

[0332] In this scenario, for cells configured with M-DCI but without time-binding, the Q value can be calculated as the product of the maximum number of PDSCHs that the corresponding M-DCI can schedule and X. For example, for a cell configured with 2TB but without space-binding, X can be 2; for a cell configured with 2TB but with space-binding or with 1TB, X can be 1.

[0333] Furthermore, in the case of a cell configured with M-DCI and time binding configured for a G value greater than 1, the Q value can be calculated as the product of G and X. In this case, X can be 1 or 2 depending on the number of TBs and the spatial binding configuration as described above.

[0334] This can represent the number of (time-bundled) groups received from the DCI corresponding to the multi-PDSCH case. Alternatively, if an M-DCI (scheduling multiple PDSCHs) is received at PDCCH monitoring time m in serving cell c, then... It can represent the number of time-binding groups configured for the corresponding serving cell c.

[0335] Assume that the maximum number of PDSCHs that can be scheduled by M-DCI for serving cell c is 8, and the maximum number of configured (time-binding) groups is 2. When the number of time-binding groups generated using the PDSCHs actually scheduled by the corresponding M-DCI is one (when M-DCI (scheduling multiple PDSCHs) is detected at PDCCH reception time m on the corresponding serving cell c), the value of N for that cell (e.g., ) can be 1 (or 2, regardless of the number of PDSCHs scheduled).

[0336] For example, when scheduling multiple PDSCHs via M-DCI, 2TB scheduling can be performed without configuring PUCCH space binding (when M-DCI (scheduling multiple PDSCHs) is detected in the corresponding serving cell c at PDCCH reception time m), and the value of N (e.g., ) can be 2 (or 4, regardless of the number of PDSCHs scheduled).

[0337] As another example, suppose that K binding groups are configured for serving cell c, and M UEs detect M-DCI received at PDCCH monitoring time m (multiple PDSCHs are scheduled on serving cell c).

[0338] At this time, when the value of 'maxNrofCodeWordsScheduledByDCI' is 2 and PUCCH space binding is configured, or when the value of 'maxNrofCodeWordsScheduledByDCI' is 1, The value can be K*M.

[0339] Alternatively, when the 'maxNrofCodeWordsScheduledByDCI' value is 2 and PUCCH space binding is not configured, The value can be 2*K*M.

[0340] When G=1 is configured for all cells with M-DCI (within the same PUCCH cell group), n can be ignored when calculating the PUCCH power. HARQ-ACK,M-PDSCH The value of .

[0341] Implementation Method 2

[0342] As in Option 1, when scheduling a TB-based PDSCH in a single PDSCH scenario, a first sub-CB for the corresponding PDSCH can be configured. When scheduling a TB-based PDSCH in a multi-PDSCH scenario, a second sub-CB for the corresponding PDSCH can be configured. When scheduling a CBG-based PDSCH in a single PDSCH scenario, a third sub-CB can be configured. In this case, Implementation 2 involves calculating n. HARQ-ACK The method for determining the value.

[0343] The final n HARQ-ACK The value can be derived as the sum of n values ​​corresponding to a single sub-CB. For example, in the case of a single PDSCH, the final n HARQ-ACK The value can be derived as the n value corresponding to the TB-based PDSCH case. HARQ-ACK,S-PDSCH&TB The value of n corresponding to the multiple PDSCH case. HARQ-ACK,M-PDSCH And the value n for CBG-based PDSCH in the case of a single PDSCH. HARQ-ACK,CBG The sum of .

[0344] Specifically, n HARQ-ACK,S-PDSCH&TB The value can be related to nn in implementation 1. HARQ-ACK,S-PDSCH Same. Specifically, in calculating n HARQ-ACK,S-PDSCH&TB When n is a value, the DCI corresponding to the single PDSCH case can represent the TB-based PDSCH for scheduling DCI. Additionally, n HARQ-ACK,M-PDSCH The value can be related to n in implementation method 1. HARQ-ACK,M-PDSCH The values ​​of n are the same. And n HARQ-ACK,CBG The value can be compared with n in equation (2) of Table 10. HARQ-ACK,CBG same.

[0345] Implementation Method 3

[0346] As in Option 2, when scheduling TB-based PDSCH in the single PDSCH case, a first sub-CB can be configured. Alternatively, a second sub-CB can be configured that integrates CBG-based PDSCH scheduling for both multi-PDSCH and single-PDSCH scenarios. In this case, Implementation 3 involves calculating n. HARQ-ACK The method for determining the value.

[0347] The final n HARQ-ACK The value can be from n HARQ-ACK,S-PDSCH&TB and nHARQ-ACK,M-PDSCH / CBG The summation leads to the conclusion that n HARQ-ACK,S-PDSCH&TB This is the value of n corresponding to the TB-based PDSCH in the case of a single PDSCH, and n HARQ-ACK,M-PDSCH / CBG This is the value of n corresponding to the CBG-based PDSCH in the case of multiple PDSCHs.

[0348] Specifically, n HARQ-ACK,S-PDSCH&TB The value can be related to n in implementation method 1. HARQ-ACK,S-PDSCH Same. Specifically, in calculating n HARQ-ACK,S-PDSCH&TB When the value is , the DCI corresponding to the single PDSCH case can represent the TB-based PDSCH for scheduling DCI.

[0349] Additionally, n HARQ-ACK,M-PDSCH / CBG The value of can be determined by Equation 5, which is similar to Equation (2) in Table 10.

[0350] [Equation 5]

[0351]

[0352] at this time, It can represent the total (or counter) DAI value indicated in the last DCI format corresponding to multiple PDSCH cases or CBG-based PDSCH.

[0353] It can indicate the number of serving cells configured with M-DCI or CBG.

[0354] It can indicate the total number of DCI formats corresponding to multiple PDSCH cases (detected by the UE) or CBG-based PDSCH.

[0355] It can represent the total number of PDSCHs received from DCI or the number of TBs corresponding to multiple PDSCH cases.

[0356] For example, based on the lack of provided spatial bundling configuration information related to PUCCH (e.g., 'harq-ACK-SpatialBundlingPUCCH'), This can indicate the number of TBs in the DCI scheduling corresponding to a multi-PDSCH scenario. As another example, based on the provided space bundling configuration information related to PUCCH, It can represent the total number of PDSCHs in DCI scheduling corresponding to the case of multiple PDSCHs.

[0357] in addition, It can be determined that the calculation is based on Implementation Method 1. The calculations in equation (2) of Table 10 The maximum value among them. Other parameters can be the same as in Table 10.

[0358] Implementation Method 4

[0359] Implementation method 4 relates to a method for calculating n when configuring a single CB for both single PDSCH and multi-PDSCH scenarios, provided that time bundling is configured. HARQ-ACK The method for determining the value.

[0360] For example, when a CBG is configured, a separate sub-CB can be configured for CBG-based PDSCH scheduling. The final n HARQ-ACK The value can be from n HARQ-ACK,S / M-PDSCH&TB and n HARQ-ACK,CBG The summation leads to the conclusion that n HARQ-ACK,S / M-PDSCH&TB This refers to the value of n for TB-based PDSCH in the case of single / multiple PDSCHs. HARQ-ACK,CBG This corresponds to the value of n for CBG-based PDSCH in the case of a single PDSCH.

[0361] Specifically, n HARQ-ACK,CBG The value can be compared with n in equation (2) of Table 10. HARQ-ACK,CBG Same. If CBG is not configured in the same PUCCH group, then n can be disregarded. HARQ-ACK,CBG .

[0362] n HARQ-ACK,S / M-PDSCH&TB The value can be determined based on the number of identified lost PDSCHs (or TBs), the number of received PDSCHs corresponding to the single PDSCH case, and the number of bundled HARQ-ACK bits corresponding to the multi-PDSCH case (or based on the number of HARQ-ACK bits generated by time bundling of multiple PDSCHs using DCI scheduling corresponding to the multi-PDSCH case).

[0363] As an example, n HARQ-ACK,S / M-PDSCH&TB It can be determined by Equation 6, which is similar to Equation (1) in Table 8.

[0364] [Equation 6]

[0365]

[0366] in this case, It can indicate the total (or counter) DAI value indicated in the last DCI format in the case of a single PDSCH corresponding to a TB-based PDSCH schedule or in the case of multiple PDSCH.

[0367] U DAI,c It can represent the total number of DCI formats corresponding to TB-based PDSCH scheduling or multi-PDSCH scenarios in the case of a single PDSCH (detected by the UE).

[0368] also, and The values ​​can be determined according to the method described later, and other parameters can be the same as those in Tables 8 to 10.

[0369] This can be determined as the maximum X*G value within any cell (in a cell group). Here, G can represent the (maximum) number of groups configured for time-binding (configured individually or collectively for each serving cell). Furthermore, X can be 1 when the corresponding serving cell has PUCCH spatial binding configured, and 2 when the corresponding serving cell does not have PUCCH spatial binding configured. And, when G = 1, It can be compared with equation (1) in Table 8. same.

[0370] This can indicate the number of TBs or PDSCHs received from the DCI corresponding to a single PDSCH case. As disclosed in Tables 8 to 10, It can be based on The number of TBs or PDSCHs in the 2-TB transmission and PUCCH space bundle configuration.

[0371] It can indicate the number of (time-bundled) groups of DCI reception corresponding to multiple PDSCH scenarios.

[0372] As an example, assume the maximum number of PDSCHs that can be scheduled for the serving cell cM-DCI is 8, and the maximum number of configured groups is 2. When the number of time-bundled groups generated using the PDSCHs actually scheduled through the corresponding M-DCI is one, the value of N for that cell (e.g., ) can be 1 (or 2, regardless of the number of PDSCHs scheduled).

[0373] As another example, suppose multiple PDSCHs are scheduled by M-DCI. When the corresponding DCI can perform 2TB scheduling and PUCCH space bundling is not configured, N (e.g., The value of ) can be 2 (or 4, regardless of the number of PDSCHs scheduled).

[0374] For example, if the maximum number of groups is 1, then the corresponding N value (e.g., This can represent the number of bundled TBs received.

[0375] As another example, if the maximum number of groups is 1, then the corresponding N value (e.g., The value of N can be determined by the number of DCIs (=Q) received by the UE corresponding to the multi-PDSCH scenario. For example, if 2-TB indication / scheduling is possible in the corresponding DCI and PUCCH space binding is not configured, then the corresponding N value (e.g., It can be 2*Q. And, for example, when 2-TB indication / scheduling is not possible in DCI, or when PUCCH space bundling is configured, the corresponding N value (e.g., ) can be Q.

[0376] The above method can be applied when G=1 is configured for all cells with M-DCI (within the same PUCCH cell group).

[0377] Implementation Method 5

[0378] Implementation 5 relates to a method for calculating n in the type 1 HARQ-ACK codebook when configuring time-binding or CBG for M-DCI. HARQ-ACK The method for determining the value.

[0379] In the case of a Type 1 HARQ-ACK codebook, when the total HARQ-ACK codebook size is 11 bits or less, n HARQ-ACK The value can be determined as shown in Table 11 below.

[0380] [Table 11]

[0381]

[0382] If time binding or CBG is configured for M-DCI, then n HARQ-ACK It can be determined based on the number of PDSCHs received corresponding to the single PDSCH case, the number of bundled HARQ-ACK bits corresponding to the multi-PDSCH case (or the number of HARQ-ACK bits generated based on the time bundling of multiple PDSCHs scheduled by DCI corresponding to the multi-PDSCH case), and the number of CBGs received.

[0383] n HARQ-ACK The value of can be determined as shown in Equation 7 below.

[0384] [Equation 7]

[0385]

[0386] at this time, Can be compared with those in Table 11 same. and The value can be related to implementation method 4. and The values ​​are the same.

[0387] Alternatively, considering that G=1 can only be configured for type 1 HARQ-ACK codebooks, the equations in Table 11 are maintained, but Values ​​can be calculated in new ways.

[0388] As an example, suppose time-domain bundling is configured for serving cell c (i.e., the higher-level parameter 'enableTimeDomainHARQ-Bundling' is configured). In this case, The value can indicate the number of TBs corresponding to the last SLIV (indicated by the TDRA line index in the associated DCI format) received (or scheduled) by the UE in the PDSCH reception timing m (when 'harq-ACK-SpatialBundlingPUCCH' is not configured) or the number of PDSCHs (when 'harq-ACK-SpatialBundlingPUCCH' is configured).

[0389] That is, even if the UE receives the PDSCH at PDSCH reception time m, if the corresponding PDSCH does not correspond to the last SLIV (of the TDRA row index indicated in the associated DCI format), then The value may not increase because the corresponding PDSCH value is likely to be lost.

[0390] Here, the last SLIV can refer to the last SLIV configured based on the SLIV in the indicated TDRA table index.

[0391] As another example, the last SLIV can refer to the last SLIV among those SLIVs configured in the indicated TDRA table index, excluding the invalid SLIV. Here, an invalid SLIV can refer to an SLIV that overlaps with a UL symbol configured by a specific higher-level signaling (e.g., 'tdd-UL-DL-ConfigurationCommon' or 'tdd-UL-DL-ConfigurationDedicated'), even if it is a symbol.

[0392] Figure 11 This is a diagram illustrating the signaling process between the network side and the UE according to an embodiment of this disclosure.

[0393] Figure 11 This describes an example of signaling between the UE and the network side in an M-TRP scenario where implementations of this disclosure (e.g., implementation 1 / implementation 2 / implementation 3 / implementation 4 / implementation 5, or a combination of one or more of their detailed examples) can be applied.

[0394] Here, the UE / network side is exemplary and can be referenced. Figure 12 The various devices described are used as alternatives. Figure 11 This is for illustrative purposes only and does not limit the scope of this disclosure. Furthermore, depending on the circumstances and / or configuration, details may be omitted. Figure 11 Some of the steps are shown in the diagram. Additionally, the aforementioned uplink transmission and reception operations, MTRP-related operations, etc., may be involved in or used for... Figure 11 Operations on the network side / UE.

[0395] In the following description, the network side can be a base station comprising multiple TRPs, or a cell comprising multiple TRPs. Alternatively, the network side can include multiple RRHs (Remote Radio Headers) / RRUs (Remote Radio Units). For example, ideal / non-ideal backhaul can be configured between TRP 1 and TRP 2 constituting the network side. Furthermore, while the following description is based on multiple TRPs, it can be similarly extended and applied to transmissions through multiple panels / cells, and also to transmissions through multiple RRHs / RRUs, etc.

[0396] Furthermore, the following description is based on "TRP," but as mentioned above, "TRP" can be applied by replacing it with expressions such as panel, antenna array, cell (e.g., macro cell / small cell / pecimen cell, etc.), TP (transmitter point), base station (gNB, etc.). As mentioned above, TRPs can be classified based on information about CORESET groups (or CORESET pools) (e.g., CORESET index, ID).

[0397] For example, when a UE is configured to transmit and receive with multiple TRPs (or cells), it may mean that multiple CORESET groups (or CORESET pools) are configured for a UE. The configuration of such CORESET groups (or CORESET pools) can be performed via higher-layer signaling (e.g., RRC signaling, etc.).

[0398] Additionally, a base station can generally refer to the entity that performs data transmission and reception with a terminal. For example, a base station can be a concept that includes at least one TP (transmitter point) and at least one TRP (transmitter and receiver point). Furthermore, the TP and / or TRP can include the base station's panel, transmission and reception units, etc.

[0399] The UE can receive configuration information S105 from the network side via / using TRP 1 and / or TRP 2.

[0400] For example, configuration information may include information related to network-side configuration (i.e., TRP configuration), resource allocation related to M-TRP-based transmission and reception, and so on. Configuration information can be sent via higher-layer signaling (e.g., RRC, MAC CE, etc.). Configuration information may include information related to configuration-based grant (CG) uplink transmission. Furthermore, when the configuration information is predefined or configured, the corresponding steps can be omitted.

[0401] As another example, the configuration information may include at least one of the following: information related to time domain binding (e.g., 'enableTimeDomainHARQ'), information related to spatial binding (e.g., 'harq-ACK-SpatialBundlingPUCCH'), and information related to CBG transmission (e.g., 'PDSCH-CodeBlockGroupTransmission').

[0402] For example, UE ( Figure 12 In step S105 above, 100 or 200) are obtained from the network side ( Figure 12 The operation of receiving configuration information (200 or 100) can be performed by Figure 12 The device implementation in [the document] (will be described later). For example, refer to [reference]. Figure 12 At least one processor 102 can control at least one transceiver 106 and / or at least one memory 104 to receive configuration information, and at least one transceiver 106 can receive configuration information from the network side.

[0403] The UE can receive control information S110 from the network side. For example, the UE can receive a DCI for scheduling uplink / downlink from the network side. In this case, the DCI can indicate a TDRA line including one or more SLIV entries. Furthermore, the DCI can schedule the PDSCH sent to the UE at the time of PDSCH reception.

[0404] In addition, when the control information is predefined or configured, the corresponding steps can be omitted.

[0405] For example, UE ( Figure 12 In step S110 above, 100 or 200) are obtained from the network side ( Figure 12 The operation of receiving control information (200 or 100) can be described later. Figure 12 The device implementation in [the context]. For example, refer to [reference]. Figure 12 One or more processors 102 can control one or more transceivers 106 and / or one or more memories 104 to receive control information, and one or more transceivers 106 can receive control information from the network side.

[0406] The UE can send uplink signals to the network or receive downlink signals (S115).

[0407] The UE can receive at least one PDSCH from the base station during PDSCH reception. Furthermore, the UE can send a PUCCH to the base station that includes a HARQ-ACK for at least one PDSCH.

[0408] In this case, the transmission power of the PUCCH can be based on a specific PDSCH among at least one PDSCH. The specific PDSCH can be associated with the last SLIV among at least one SLIV included in the TDRA line indicated by the DCI.

[0409] The UE can perform uplink transmission or downlink reception based on the implementation methods of this disclosure (e.g., implementation method 1, implementation method 2, implementation method 3, implementation method 4, implementation method 5, or one or more combinations thereof in detailed implementation methods).

[0410] For example, the UE in step S115 above ( Figure 12 100 or 200 in the middle) to the network side ( Figure 12 (200 or 100) sends uplink or from the network side ( Figure 12 The operation of receiving downlink signals (200 or 100) can be described below. Figure 12 This is achieved through equipment.

[0411] For example, refer to Figure 12 One or more processors 102 can control one or more transceivers 106 and / or one or more memories 104 to transmit uplinks or receive downlinks, and one or more transceivers 106 to transmit uplinks or receive downlinks to the network side.

[0412] The general apparatus disclosed herein can be used

[0413] Figure 12 This is a block diagram illustrating a wireless communication system according to an embodiment of the present disclosure.

[0414] Reference Figure 12 The first device 100 and the second device 200 can transmit and receive wireless signals through various radio access technologies (e.g., LTE, NR).

[0415] The first device 100 may include one or more processors 102 and one or more memories 104, and may additionally include one or more transceivers 106 and / or one or more antennas 108. The processors 102 may control the memories 104 and / or the transceivers 106, and may be configured to implement the descriptions, functions, processes, suggestions, methods and / or operation flowcharts included in this disclosure.

[0416] For example, after generating first information / signal by processing information in memory 104, processor 102 can transmit a wireless signal including the first information / signal via transceiver 106. Alternatively, processor 102 can receive a wireless signal including second information / signal via transceiver 106, and then store the information obtained through signal processing of the second information / signal in memory 104.

[0417] Memory 104 may be connected to processor 102 and may store various information related to the operation of processor 102. For example, memory 104 may store software code including commands for performing all or part of the processing controlled by processor 102 or for performing commands included in the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts herein. Here, processor 102 and memory 104 may be part of a communication modem / circuit / chip designed to implement wireless communication technologies (e.g., LTE, NR). Transceiver 106 may be connected to processor 102 and may transmit and / or receive wireless signals via one or more antennas 108. Transceiver 106 may include a transmitter and / or a receiver. Transceiver 106 may be used with an RF (radio frequency) unit. In this disclosure, wireless device may refer to a communication modem / circuit / chip.

[0418] The second device 200 may include one or more processors 202 and one or more memories 204, and may additionally include one or more transceivers 206 and / or one or more antennas 208. The processors 202 may control the memories 204 and / or the transceivers 206, and may be configured to implement the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in this disclosure. For example, the processors 202 may generate third information / signals by processing information in the memories 204, and then transmit a wireless signal including the third information / signals via the transceivers 206. Additionally, the processors 202 may receive wireless signals including fourth information / signals via the transceivers 206, and then store information obtained through signal processing of the fourth information / signals in the memories 204. The memories 204 may be connected to the processors 202 and may store various information related to the operation of the processors 202. For example, the memories 204 may store software code including commands for performing all or part of the processing controlled by the processors 202 or for executing the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in this disclosure. Here, processor 202 and memory 204 may be part of a communication modem / circuit / chip designed to implement wireless communication technologies (e.g., LTE, NR). Transceiver 206 may be connected to processor 202 and may transmit and / or receive wireless signals via one or more antennas 208. Transceiver 206 may include a transmitter and / or a receiver. Transceiver 206 may be used with an RF unit. In this disclosure, wireless device may refer to a communication modem / circuit / chip.

[0419] The hardware components of devices 100 and 200 will be described in more detail below. Not limited thereto, one or more protocol layers may be implemented by one or more processors 102 and 202. For example, one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors 102 and 202 may generate one or more PDUs (Protocol Data Units) and / or one or more SDUs (Service Data Units) according to the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in this disclosure. One or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in this disclosure. One or more processors 102, 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information, in accordance with the functions, processes, suggestions, and / or methods disclosed in this disclosure, to provide them to one or more transceivers 106, 206. One or more processors 102, 202 may receive signals (e.g., baseband signals) from one or more transceivers 106, 206, and obtain PDUs, SDUs, messages, control information, data, or information, in accordance with the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in this disclosure.

[0420] One or more processors 102, 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102, 202 may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more ASICs (Application-Specific Integrated Circuits), one or more DSPs (Digital Signal Processors), one or more DSPDs (Digital Signal Processing Devices), one or more PLDs (Programmable Logic Devices), or one or more FPGAs (Field-Programmable Gate Arrays) may be included in one or more processors 102, 202. The descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in this disclosure may be implemented using firmware or software, and the firmware or software may be implemented to include modules, processes, functions, etc. Firmware or software configured to execute the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in this disclosure may be included in one or more processors 102, 202, or may be stored in one or more memories 104, 204 and driven by one or more processors 102, 202. The descriptions, functions, processes, suggestions, methods and / or operation flowcharts included in this disclosure can be implemented using firmware or software in the form of codes, commands and / or command sets.

[0421] One or more memories 104, 204 may be connected to one or more processors 102, 202 and may store data, signals, messages, information, programs, code, instructions, and / or commands in various forms. One or more memories 104, 204 may be configured with ROM, RAM, EPROM, flash memory, hard disk drive, registers, cache memory, computer-readable storage media, and / or combinations thereof. One or more memories 104, 204 may be located internally and / or externally to one or more processors 102, 202. Furthermore, one or more memories 104, 204 may be connected to one or more processors 102, 202 via various technologies such as wired or wireless connections.

[0422] One or more transceivers 106, 206 can transmit user data, control information, wireless signals / channels, etc., mentioned in the methods and / or operation flowcharts of this disclosure to one or more other devices. One or more transceivers 106, 206 can receive user data, control information, wireless signals / channels, etc., mentioned in the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in this disclosure from one or more other devices. For example, one or more transceivers 106, 206 can be connected to one or more processors 102, 202 and can transmit and receive wireless signals. For example, one or more processors 102, 202 can control one or more transceivers 106, 206 to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors 102, 202 can control one or more transceivers 106, 206 to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers 106, 206 may be connected to one or more antennas 108, 208, and one or more transceivers 106, 206 may be configured to transmit and receive user data, control information, wireless signals / channels, etc., mentioned in the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in this disclosure, via one or more antennas 108, 208. In this disclosure, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers 106, 206 may convert received wireless signals / channels, etc., from RF band signals into baseband signals for processing using one or more processors 102, 202. One or more transceivers 106, 206 may convert user data, control information, wireless signals / channels, etc., processed using one or more processors 102, 202, from baseband signals into RF band signals. Therefore, one or more transceivers 106, 206 may include (analog) oscillators and / or filters.

[0423] The above embodiments combine the elements and features of this disclosure in a predetermined form. Unless otherwise expressly stated, each element or feature should be considered optional. Each element or feature may be implemented without being combined with other elements or features. Furthermore, embodiments of this disclosure may include combinations of some elements and / or features. The order of operations described in embodiments of this disclosure may be changed. Some elements or features of one embodiment may be included in other embodiments, or may be replaced by corresponding elements or features of other embodiments. Obviously, embodiments may include claims that are not explicitly referenced in the claims, or may be included as new claims after the application has been amended.

[0424] It will be apparent to those skilled in the art that this disclosure may be implemented in other specific forms without departing from its essential characteristics. Therefore, the foregoing detailed description should not be construed as restrictive in every respect, but rather as illustrative. The scope of this disclosure should be determined by a reasonable interpretation of the appended claims, and all variations within the equivalent scope of this disclosure are included within its scope.

[0425] The scope of this disclosure includes software or machine-executable commands (e.g., operating systems, applications, firmware, programs, etc.) that operate in a device or computer according to methods of various embodiments, and non-transitory computer-readable media that cause software or commands to be stored and executable in a device or computer. Commands that can be used to program a processing system to perform the features described in this disclosure can be stored in a storage medium or a computer-readable storage medium, and the features described in this disclosure can be implemented by using a computer program product including such a storage medium. The storage medium may include, but is not limited to, high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state storage devices, and may include non-volatile memory, such as one or more disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory may optionally include one or more storage devices located remotely from the processor. The memory, or alternatively, the non-volatile memory devices in the memory include non-transitory computer-readable storage media. The features described in this disclosure can be stored in any machine-readable medium to control the hardware of a processing system and can be integrated into software and / or firmware that allows the processing system to interact with other mechanisms using results from embodiments of this disclosure. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments / containers.

[0426] The wireless communication technologies implemented in the devices 100 and 200 of this disclosure may include narrowband Internet of Things (IoT) for low-power communication, as well as LTE, NR, and 6G. For example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology, implemented in standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the aforementioned names. Additionally or alternatively, the wireless communication technologies implemented in the devices 100 and 200 of this disclosure may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be referred to by various names such as eMTC (Enhanced Machine-Type Communication). For example, LTE-M technology may be implemented in at least any of various standards, including 1) LTE Cat 0; 2) LTE Cat M1; 3) LTE Cat M2; 4) LTE non-BL (non-bandwidth limited); 5) LTE-MTC; 6) LTE Machine-Type Communication; and / or 7) LTE M, etc., and is not limited to the aforementioned names. Additionally or alternatively, the wireless communication technologies implemented in the devices 100 and 200 of this disclosure may include at least any one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) considering low-power communication, and are not limited to the aforementioned names. For example, ZigBee technology can generate PANs (Personal Area Networks) associated with small / low-power digital communication based on various standards (e.g., IEEE 802.15.4, etc.) and may be referred to by various names.

Claims

1. A method performed by a user equipment (UE), the method comprising the following steps: Receive first configuration information related to time-domain binding from the base station; During at least one Physical Downlink Shared Channel (PDSCH) reception timing, at least one PDSCH comprising at least one transport block (TB) is received from the base station; and Based on enabling the time-domain binding through the first configuration information, a PUCCH including hybrid automatic repeat request-acknowledgment (HARQ-ACK) information related to the at least one PDSCH is sent to the base station. The transmit power for the PUCCH is based on the number of PDSCHs associated with the last SLIV of at least one start and length indicator value SLIV in at least one serving cell, or the number of transport blocks associated with the last SLIV in at least one transport block in at least one serving cell. The at least one SLIV is included in the Time Domain Resource Allocation (TDRA) line associated with Downlink Control Information (DCI).

2. The method according to claim 1, wherein, Based on the fact that no second configuration information related to spatial bundling and a third configuration information related to code block group (CBG) transmission were received from the base station, the transmit power for the PUCCH is based on the number of transport blocks associated with the last SLIV for the at least one serving cell.

3. The method according to claim 1, wherein, Based on the second configuration information related to spatial bundling received from the base station, the transmit power for the PUCCH is based on the number of PDSCHs associated with the last SLIV for the at least one serving cell.

4. The method according to claim 1, wherein, Based on the third configuration information related to CBG transmission received from the base station and the fact that the DCI does not support CBG-based PDSCH reception, the transmit power for the PUCCH is based on the number of TBs associated with the last SLIV for the at least one serving cell.

5. The method according to claim 1, wherein, The transmit power for the PUCCH is obtained by using the number of transport blocks associated with the last SLIV or the sum of the number of transport blocks associated with the last SLIV for the at least one serving cell and the number of CBGs received from the base station for the at least one serving cell during the at least one PDSCH reception timing.

6. The method according to claim 1, wherein, The remaining PDSCHs among the at least one PDSCHs that are not associated with the last SLIV are not considered as PDSCHs related to the transmit power for the PUCCH.

7. The method according to claim 1, wherein, The number of bits of the UCI payload included in the PUCCH is 11 or fewer, and The UCI payload includes at least one of the HARQ-ACK information, scheduling request (SR) information, or channel state information (CSI) information.

8. A user equipment (UE), the UE comprising: At least one transceiver; as well as At least one processor, said at least one processor being connected to said at least one transceiver, Wherein, the at least one processor is configured to: The transceiver receives first configuration information related to time-domain binding from the base station. During at least one Physical Downlink Shared Channel (PDSCH) reception time, the transceiver receives at least one PDSCH comprising at least one transport block (TB) from the base station; and Based on enabling the time-domain binding through the first configuration information, the transceiver sends a PUCCH to the base station, including hybrid automatic repeat request-acknowledgment (HARQ-ACK) information related to the at least one PDSCH. The transmit power for the PUCCH is based on the number of PDSCHs associated with the last SLIV of at least one start and length indicator value SLIV in at least one serving cell, or the number of transport blocks associated with the last SLIV in at least one transport block in at least one serving cell. The at least one SLIV is included in the Time Domain Resource Allocation (TDRA) line associated with Downlink Control Information (DCI).

9. A method performed by a base station, the method comprising the following steps: Send the first configuration information related to time domain binding to the user equipment (UE); At least one PDSCH, including at least one transport block TB, is sent to the UE during at least one physical downlink shared channel (PDSCH) reception timing; and Based on enabling the time-domain binding through the first configuration information, the UE receives a PUCCH including hybrid automatic repeat request-acknowledgment (HARQ-ACK) information related to the at least one PDSCH. The transmit power for the PUCCH is based on the number of PDSCHs associated with the last SLIV of at least one start and length indicator value SLIV in at least one serving cell, or the number of transport blocks associated with the last SLIV in at least one transport block in at least one serving cell. The at least one SLIV is included in the Time Domain Resource Allocation (TDRA) line associated with Downlink Control Information (DCI).

10. A base station, the base station comprising: At least one transceiver; as well as At least one processor, said at least one processor being connected to said at least one transceiver, Wherein, the at least one processor is configured to: The transceiver sends first configuration information related to time domain binding to the user equipment (UE). The transceiver transmits at least one PDSCH, including at least one transport block TB, to the UE during at least one physical downlink shared channel (PDSCH) reception opportunity; and Based on enabling the time-domain binding through the first configuration information, the transceiver receives a PUCCH from the UE, including hybrid automatic repeat request-acknowledgment (HARQ-ACK) information related to the at least one PDSCH. The transmit power for the PUCCH is based on the number of PDSCHs associated with the last SLIV of at least one start and length indicator value SLIV in at least one serving cell, or the number of transport blocks associated with the last SLIV in at least one transport block in at least one serving cell. The at least one SLIV is included in the Time Domain Resource Allocation (TDRA) line associated with Downlink Control Information (DCI).

11. A processing apparatus configured to control a user equipment (UE), the processing apparatus comprising: At least one processor; as well as At least one computer memory, operatively coupled to the at least one processor and storing instructions for performing operations when executed by the at least one processor. The operation includes: Receive first configuration information related to time-domain binding from the base station; During at least one Physical Downlink Shared Channel (PDSCH) reception timing, at least one PDSCH comprising at least one transport block (TB) is received from the base station; and Based on enabling the time-domain binding through the first configuration information, a PUCCH including hybrid automatic repeat request-acknowledgment (HARQ-ACK) information related to the at least one PDSCH is sent to the base station. The transmit power for the PUCCH is based on the number of PDSCHs associated with the last SLIV of at least one start and length indicator value SLIV in at least one serving cell, or the number of transport blocks associated with the last SLIV in at least one transport block in at least one serving cell. The at least one SLIV is included in the Time Domain Resource Allocation (TDRA) line associated with Downlink Control Information (DCI).

12. At least one non-transitory computer-readable medium storing at least one instruction, wherein, The at least one instruction control device, executed by at least one processor, performs the following: Receive first configuration information related to time-domain binding from the base station; At at least one Physical Downlink Shared Channel (PDSCH) reception time, at least one PDSCH comprising at least one transport block (TB) is received from the base station; and Based on enabling the time-domain binding through the first configuration information, a PUCCH including hybrid automatic repeat request-acknowledgment (HARQ-ACK) information related to the at least one PDSCH is sent to the base station. The transmit power for the PUCCH is based on the number of PDSCHs associated with the last SLIV of at least one start and length indicator value SLIV in at least one serving cell, or the number of transport blocks associated with the last SLIV in at least one transport block in at least one serving cell. The at least one SLIV is included in the Time Domain Resource Allocation (TDRA) line associated with Downlink Control Information (DCI).

Images