Methods of performing communications, user equipment, base stations, processing devices, and media

Abstract

Methods of performing communications, user equipment, base stations, processing devices, and media are disclosed. In embodiments of the present disclosure, a method of performing communications by a user equipment (UE) can include receiving, from a base station, configuration information related to at least one time domain resource allocation (TDRA) row including multiple start and length indicator values (SLIVs) for a physical downlink shared channel (PDSCH), and receiving, from the base station, a first downlink control information (DCI), and the first DCI includes transmission configuration indicator (TCI) state indication information and does not include downlink (DL) assignment information, and a number of SLIVs in a particular TDRA row among the at least one TDRA row indicated by the first DCI is 1.

Description

Technical Field

[0001] This disclosure relates to wireless communication systems, and more specifically, to methods and apparatus for performing communication in wireless communication systems based on a DCI for scheduling multiple PDSCHs. 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 communication in a wireless communication system.

[0006] Another technical objective of this disclosure is to provide a method and apparatus for transmitting and receiving HARQ-ACKs corresponding to (multi)DCIs used for scheduling multiple PDSCHs.

[0007] Another technical objective of this disclosure is to provide a method and apparatus for indicating the TDRA (Time Domain Resource Allocation) row index associated with a single SLIV when updating the TCI state via M-DCI without PDSCH scheduling.

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

[0009] Technical solution

[0010] In embodiments of this disclosure, a method for a user equipment (UE) to perform communication in a wireless communication system may include the following steps: receiving configuration information from a base station relating to at least one time-domain resource allocation (TDRA) line including a plurality of start and length indicator values ​​(SLIVs) for a physical downlink shared channel (PDSCH); and receiving first downlink control information (DCI) from the base station, wherein the first DCI includes transmission configuration indicator (TCI) status indication information and does not include downlink (DL) assignment information, and the number of SLIVs in a particular TDRA line indicated by the first DCI in the at least one TDRA line is 1.

[0011] In embodiments of this disclosure, a method for a base station to perform communication in a wireless communication system may include the following steps: sending configuration information to a user equipment (UE) relating to at least one time-domain resource allocation (TDRA) line including a plurality of start and length indicator values ​​(SLIVs) for a physical downlink shared channel (PDSCH); and sending first downlink control information (DCI) to the UE, the first DCI including transmission configuration indicator (TCI) status indication information and excluding downlink (DL) assignment information, and the number of SLIVs in a particular TDRA line indicated by the first DCI among the at least one TDRA line is 1.

[0012] Technical effect

[0013] According to embodiments of this disclosure, methods and apparatus for performing communication in a wireless communication system can be provided.

[0014] According to embodiments of this disclosure, a method and apparatus for transmitting and receiving HARQ-ACKs corresponding to DCI (M-DCI) used for scheduling multiple PDSCHs can be provided.

[0015] According to embodiments of this disclosure, by supporting the scheduling of multiple PDSCH transmissions via M-DCI, the transmission efficiency of DCI for scheduling PDSCH and / or PUSCH can be improved.

[0016] According to embodiments of this disclosure, when updating the TCI status via M-DCI without PDSCH scheduling, a method and apparatus for indicating the TDRA row index associated with a single SLIV can be provided.

[0017] According to the embodiments of this disclosure, even if the TCI state update is indicated by M-DCI without PDSCH scheduling, the ambiguity of the configuration based on the UE's HARQ-ACK codebook can be resolved since the corresponding DCI only schedules one resource for one PDSCH.

[0018] 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

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

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

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

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

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

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

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

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

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

[0028] Figure 9 This is a diagram illustrating a method for sending and receiving HARQ-ACKs for a PDSCH scheduled by a DCI according to an embodiment of this disclosure.

[0029] Figure 10 This is a diagram illustrating a method by which a UE performs communication in a wireless communication system to which this disclosure can be applied.

[0030] Figure 11 This is a diagram illustrating a method by which a base station performs communication in a wireless communication system to which this disclosure may be applied.

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

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

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

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

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

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

[0037] 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”.

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

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

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

[0041] 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-A pro 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-A pro.

[0042] 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 referred to as LTE-A, and LTE technology in or after 3GPP TS 36.xxx is referred to as LTE-A pro. 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.

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

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

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

[0046] -BM: Beam Management

[0047] -CQI: Channel Quality Indicator

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

[0049] -CSI: Channel State Information

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

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

[0052] -DMRS: Demodulation Reference Signal

[0053] -FDM: Frequency Division Multiplexing

[0054] -FFT: Fast Fourier Transform

[0055] -IFDMA: Interleaved Frequency Division Multiple Access

[0056] -IFFT: Inverse Fast Fourier Transform

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

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

[0059] -MAC: Media Access Control

[0060] -NZP: Non-zero power

[0061] -OFDM: Orthogonal Frequency Division Multiplexing

[0062] –PDCCH: Physical Downlink Control Channel

[0063] -PDSCH: Physical Downlink Shared Channel

[0064] -PMI: Precoding Matrix Indicator

[0065] -RE: Resource Elements

[0066] -RI: Rank indicator

[0067] -RRC: Radio Resource Control

[0068] -RSSI: Received Signal Strength Indicator

[0069] -Rx: Receive

[0070] -QCL: Quasi-co-location

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

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

[0073] -TDM: Time Division Multiplexing

[0074] -TRP: Sending and Receiving Point

[0075] -TRS: Tracking Reference Signal

[0076] -Tx: Send

[0077] -UE: User Equipment

[0078] -ZP: Zero Power

[0079] Overall System

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

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

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

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

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

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

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

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

[0088] [Table 1]

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

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

[0091] [Table 2]

[0092]

[0093] 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 480·10 3 Hz, 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.

[0094] 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.symb slot 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.

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

[0096] [Table 3]

[0097] μ <![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

[0098] [Table 4]

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

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

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

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

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

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

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

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

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

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

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

[0110] [Equation 1]

[0111]

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

[0113] [Equation 2]

[0114]

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

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

[0117] refer to Figure 4 and Figure 5 A time slot comprises 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0135] [Table 5]

[0136] 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 and Coding Scheme), NDI (New Data Indicator), RV (Redundancy Version), etc.), information related to HARQ (Hybrid Automatic Repeat 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0180] To improve the transmission efficiency of the scheduling DCI for PDSCH / PUSCH, multiple PDSCH / PUSCH scheduling can be supported by a single DCI. For the convenience of this disclosure, the corresponding DCI is referred to as M-DCI, and the DCI used for scheduling a single PDSCH / PUSCH is referred to as S-DCI. However, a single PDSCH / PUSCH can be scheduled by M-DCI.

[0181] 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 / PUSCH. On the other hand, when row index #B is indicated by M-DCI, M-DCI can schedule multiple PDSCH / PUSCHs.

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

[0183] This disclosure describes a scheduling method for multiple PDSCH / PUSCH in the case of multiple PDSCH / PUSCH, and a method for configuring the HARQ-ACK codebook corresponding to M-DCI.

[0184] When time binding is configured in addition to M-DCI, the number of binding groups can be defined as G. For example, when multiple PDSCH / PUSCHs are scheduled via M-DCI in a cell where G is configured as 1, this can be called a single PDSCH / PUSCH case. Furthermore, 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 / PUSCH case.

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

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

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

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

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

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

[0191] 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 configured via higher-layer signaling.

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

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

[0194] 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 the group index).

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

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

[0197] Configuration method for Type 1 HARQ-ACK codebook when time binding is configured

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

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

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

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

[0202] 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)

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

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

[0205] [Table 6]

[0206]

[0207]

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

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

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

[0211] 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}.

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

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

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

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

[0216] 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}.

[0217] 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}.

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

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

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

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

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

[0223] SPS PDSCH activation and SPS PDSCH release method via M-DCI

[0224] In NR systems, activation of semi-persistent scheduling (SPS) PDSCH can be performed as shown in Table 7 below.

[0225] [Table 7]

[0226]

[0227]

[0228] In this respect, the resource location in the slot of the SPS configuration activated by the SLIV value indicated in the TDRA field on the corresponding SPS PDSCH activation DCI can be determined. However, when SPS PDSCH activation is performed via M-DCI, the determination of the resource location in the slot of the SPS PDSCH can become ambiguous because multiple SLIVs can be linked to a specific row index indicated by the TDRA field on the M-DCI.

[0229] To solve this problem, the following methods can be considered.

[0230] In one approach, when at least one row index among the TDRA row indexes configured in the M-DCI is linked to only a single SLIV, it can be configured / specified to allow SPS activation via the corresponding M-DCI. In this case, when SPS is actually activated via the corresponding M-DCI, the UE can expect the corresponding M-DCI to indicate the TDRA row index linked to only a single SLIV.

[0231] When this method is applied, even if the SPS PDSCH activation DCI is indicated by the M-DCI, the constraint that only one resource is scheduled for one PDSCH can be eliminated for the UE by applying the corresponding DCI, and the implementation complexity of the UE can be reduced.

[0232] Alternatively, even if all TDRA row indexes configured in the M-DCI are linked to multiple SLIVs, or if some TDRA row indexes configured in the M-DCI are linked to multiple SLIVs, when SPS is activated through the corresponding M-DCI, it is permissible to indicate which TDRA row indexes are linked to multiple SLIVs.

[0233] In this scenario, the UE can consider only a specific SLIV (e.g., the first SLIV, the last SLIV, etc.) among the multiple SLIVs linked to the indicated TDRA row index to be valid. In this approach, the UE can determine the location of the SPS PDSCH timing resource based on the specific SLIV information and can determine the location of the HARQ-ACK bit when configuring the HARQ-ACK timing and HARQ-ACK codebook.

[0234] For example, if {slot n+1,SLIV#1} and {slot n+2,SLIV#2} are configured by the TDRA row index indicated in the M-DCI activated by the SPS sent in slot n, then the SPS PDSCH can be activated based on the last SLIV {slot n+2,SLIV#2}. In this case, SLIV#2 in slot n+2 can be the first time resource allocated for the SPS PDSCH. Therefore, when configuring the HARQ-ACK codebook (especially when configuring the type 1 HARQ-ACK codebook), the UE can send the ACK / NACK information for the SPSPDSCH to the HARQ-ACK bit position corresponding to the corresponding SLIV.

[0235] The above issues may also occur in Uplink Configuration License (CG) PUSCH type 2.

[0236] That is, the resource location in the slot of an activated CG configuration can be determined by the SLIV value indicated by the TDRA field on the corresponding CG PUSCH activation DCI. However, when CG PUSCH activation is performed via M-DCI, the determination of the resource location in the slot of the CG PUSCH may become ambiguous because multiple SLIVs can be linked to a specific row index indicated by the TDRA field on the M-DCI.

[0237] To solve this problem, the following methods can be considered.

[0238] In one approach, when at least one row index among the TDRA row indexes configured in the M-DCI is linked to only a single SLIV, it can be configured / specified to allow CG activation via the corresponding M-DCI. In this case, when the CG is actually activated via the corresponding M-DCI, the UE can expect the corresponding M-DCI to indicate the TDRA row index linked to only a single SLIV.

[0239] When this method is applied, even if the CG PUSCH activation DCI is indicated by M-DCI, the ambiguity of the UE's CG PUSCH resources can be eliminated by applying the corresponding DCI to schedule only one resource for a PUSCH, and the implementation complexity of the UE can be reduced.

[0240] Alternatively, even if all TDRA line indices configured in the M-DCI are linked to multiple SLIVs, or if some TDRA line indices configured in the M-DCI are linked to multiple SLIVs, when the CG is activated via the corresponding M-DCI, it is permissible to specify the TDRA line indexes that link to multiple SLIVs. In this case, the UE can consider only specific SLIVs (e.g., the first and last SLIVs) among the multiple SLIVs linked to the indicated TDRA line indexes to be valid. The UE can determine the time resource location of the CG PUSCH based on the specific SLIV information.

[0241] In particular, in the case of SPS PDSCH, a method can be considered in which only the last SLIV among multiple SLIVs linked to the TDRA row index indicated by the SPS-activated M-DCI is considered valid. Furthermore, in the case of CGPUSCH, a method can be considered in which only the first SLIV among multiple SLIVs linked to the TDRA row index indicated by the CG-activated M-DCI is considered valid.

[0242] Referring to Table 7 above, when DL SPS is activated via DCI format 1_1, there is a condition that all RV (redundant version) values ​​corresponding to the enabled transport block (TB) should be configured to 0. However, even when the TDRA row index where multiple SLIVs are linked can be indicated via the corresponding DCI format 1_1, a rule may still be required.

[0243] For example, the condition in Table 7 above can be replaced with the condition that all RV values ​​corresponding to the enabled TB of PDSCH scheduled through a specific SLIV (e.g., the first SLIV, the last SLIV) among multiple SLIVs must be configured to 0. Here, a specific SLIV can be configured based on the valid SLIV among multiple SLIVs.

[0244] Alternatively, as another example, the conditions in Table 7 above can be replaced with the condition that all RV values ​​corresponding to the enabled TB of the PDSCH scheduled through all SLIV values ​​among the multiple SLIVs must be configured to 0. Here, all SLIVs can be configured based on the valid SLIVs among the multiple SLIVs.

[0245] Furthermore, in the NR system, the deactivation or release of SPS PDSCH can be performed as shown in Table 7 above.

[0246] In this respect, the HARQ-ACK bit position can be determined by the SLIV value indicated by the TDRA field on the corresponding SPS PDSCH deactivation DCI when configuring HARQ-ACK timing and / or HARQ-ACK codebook.

[0247] However, when performing SPS PDSCH release via M-DCI, the HARQ-ACK timing and / or HARQ-ACK codebook configuration can become obscured because multiple SLIVs can be linked to a specific row index indicated by the TDRA field on M-DCI.

[0248] To solve this problem, the following methods can be considered.

[0249] As a method, when at least one row index in the TDRA row indexes configured in the M-DCI is linked to only a single SLIV, SPS deactivation via the corresponding M-DCI can be configured / specified. In this case, when SPS is actually deactivated via the corresponding M-DCI, the UE can expect the corresponding M-DCI to indicate the TDRA row index linked to only a single SLIV.

[0250] When this method is applied, even if the SPS PDSCH is instructed to disable DCI via M-DCI, the constraint that only one resource is scheduled for a PDSCH by applying the corresponding DCI can eliminate the ambiguity of the UE regarding the SPS PDSCH resource and reduce the implementation complexity of the UE.

[0251] Alternatively, even if all TDRA line indices configured in the M-DCI are linked to multiple SLIVs, or if some TDRA line indices configured in the M-DCI are linked to multiple SLIVs, the TDRA line index indicating which SLIVs are linked can still be allowed when SPS is disabled via the corresponding M-DCI. In this case, the UE can consider only specific SLIVs (e.g., the first and last SLIVs) among the multiple SLIVs linked to the indicated TDRA line index to be valid. In this approach, the UE can determine the HARQ-ACK bit position based on specific SLIV information when configuring HARQ-ACK timing and / or the HARQ-ACK codebook.

[0252] For example, if {slot n+1,SLIV#1} and {slot n+2,SLIV#2} are configured by the TDRA line index indicated in the SPS deactivation M-DCI sent in slot n, then the SPS PDSCH can be deactivated based on the last SLIV {slot n+2,SLIV#2}. In this case, based on slot n+2, the HARQ-ACK timing corresponding to the SPS PDSCH can be determined, and when configuring the HARQ-ACK codebook (especially when configuring a type 1 HARQ-ACK codebook), the UE can send ACK / NACK information for the SPS PDSCH at the HARQ-ACK bit position corresponding to the corresponding SLIV.

[0253] Based on the type 2 HARQ-ACK codebook (HCB) configuration method for enabling / disabling HARQ operations.

[0254] Specifically, this disclosure describes a method for configuring type 2HCB when the enable / disable of HARQ operations (including HARQ-ACK feedback operations) for all or some HARQ process numbers (HPNs) can be configured by higher-layer signaling (or when they can be dynamically indicated by DCI). In this embodiment, type 2HCB may include enhanced type 2HCB.

[0255] In one implementation, the following describes a method for configuring type 2HCB when the number of HPNs with HARQ operation enabled is 1 (or 0) and the number of HPNs with HPNs disabled is K-1 (or K) for a particular cell (configuration).

[0256] For example, when counting DAI via DCI, since even in the case of multiple PDSCH, the effective HARQ-ACK bit corresponding to each DCI can be at most 1 bit (however, at most 2 bits when 2-TB is enabled), a single codebook (CB) can be configured for the single PDSCH case and the multiple PDSCH case corresponding to the corresponding cell.

[0257] Here, configuring a single CB can mean a structure in which, considering both single-PDSCH and multi-PDSCH scenarios together, C-DAI / T-DAI values ​​are counted and signaled. That is, when configuring a single CB, the order and / or total number of DCI / PDSCHs scheduled indiscriminately for each scenario can be determined / signaled.

[0258] Specifically, when the number of HPNs that enable HARQ operation for each cell in all cells configured with multiple PDSCH DCI in the same PUCCH cell group is 1 or less, (if CBG is not configured), a single CB can be configured by counting the DAI value together for both single PDSCH and multiple PDSCH cases within the corresponding PUCCH cell group.

[0259] At this point, it is possible to perform DAI counting without independent configuration and without configuring separate sub-CBs for both single PDSCH and multi-PDSCH cases. Additionally, in this case, with UL-licensed DCI, for both single and multi-PDSCH cases, it is possible to not configure / indicate separate DAI fields / information, and only configure / indicate a common DAI field / information.

[0260] Alternatively, the following describes a method for configuring type 2HCB in such cases: for a specific cell configured with multiple PDSCH DCI, the number of HPNs with HARQ operation enabled is N (N>1) and the number of HPNs with HPNs disabled is KN.

[0261] Alternatively, a method for configuring type 2HCB in such a case is described: for at least one of the multiple cells in a PUCCH cell group that has multiple PDSCH DCI configured, the number of HPNs with HARQ operation enabled is N and the number of HPNs with HPNs disabled is KN.

[0262] For example, when counting DAI for each DCI, a sub-CB (referred to as the first sub-CB) can be configured corresponding to the single PDSCH case, and another sub-CB (referred to as the second sub-CB) can be configured corresponding to the multiple PDSCH case. Here, configuring separate sub-CBs can mean a structure where, for each sub-CB, the C-DAI / T-DAI values ​​are independently determined and signaled. That is, the order and / or total number of DCIs / PDSCHs scheduled for each sub-CB can be independently determined and signaled.

[0263] Based on the above example, when the number of enabled HPNs among those scheduled via M-DCI (or S-DCI) is one or fewer, the UE can map the HARQ-ACK bit corresponding to the DCI to the first sub-CB. Conversely, when the number of enabled HPNs among those scheduled via M-DCI (or S-DCI) is two or more, the UE can map the HARQ-ACK bit corresponding to the DCI to the second sub-CB.

[0264] In this case, for the second sub-CB, the number of HARQ-ACK bits corresponding to a DAI value can be calculated based on the max_XY or min(max_HPN_total,max_XY_total) value.

[0265] Here, the `max_HPN_total` value can refer to the maximum number of enabled HPNs configured in various cells across multiple cells, where multi-PDSCH DCI is configured in the same PUCCH cell group. For example, when cell #1 and cell #2 belong to the same PUCCH cell group and multi-PDSCH scheduling DCI is configured for both cells, if the number of HPNs enabling HARQ operation for cell #1 is 3 and the number of HPNs enabling HARQ operation for cell #2 is 4, then `max_HPN_total` can be 4.

[0266] As another example, when 2TB is configured for cell #1 without space bundling, and 2TB is not configured for cell #2, max_HPN_total can be 6. Here, max_HPN_total being 6 means that, considering that each PDSCH for cell #1 is 2 bits, the maximum value of 6 bits for cell #1 and 4 bits for cell #2 is configured as max_HPN_total.

[0267] Additionally, when M-DCI is configured for multiple cells, the max_XY_total value can be defined as the maximum X*Y value among any cells in a cell group. Here, Y is the maximum number of PDSCHs that M-DCI can schedule, and X can be calculated as 1 for cells configured with 2TB but with space bundling, or for cells configured with 1TB.

[0268] Alternatively, based on the max_HPN and max_XY values ​​of each cell, Z = min(max_HPN, max_XY) can be determined for each cell, and the number of HARQ-ACK bits corresponding to a DAI value can be calculated based on the maximum value among the Z values ​​of each cell.

[0269] As described above, when calculating the number of HARQ-ACK bits corresponding to a DAI value based on the values ​​of max_XY or min(max_HPN_total, max_XY_total), a method can be applied to map the HARQ-ACK bits corresponding to the enabled HPN in the HARQ-ACK payload corresponding to a DAI value to the lowest (or highest) bit index. Furthermore, for HARQ-ACK bits corresponding to the enabled HPN, a method can be applied to map bits with lower (or higher) HARQ IDs to lower (or higher) bit indices, or to map bits with earlier corresponding PDSCH reception times to lower (or higher) bit indices.

[0270] Furthermore, in the method described in this embodiment, an HPN value is indicated by M-DCI, and the indicated HPN value increments by 1 starting from the first PDSCH and can be mapped to each PDSCH. In this case, modulo operations can be applied with respect to the PDSCH mapping if necessary. Here, the corresponding PDSCH can be restricted to valid PDSCHs, which may refer to PDSCHs that do not overlap with UL symbols configured by higher-layer signaling (e.g., tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated).

[0271] Methods for scheduling multiple PXSCHs in a multi-PXSCH scenario and configuration of the HARQ-ACK codebook corresponding to M-DCI. method

[0272] The following describes the scheduling method for multiple PXSCHs in the case of multiple PXSCHs (e.g., PDSCH / PUSCH) and the method for configuring the HARQ-ACK codebook corresponding to M-DCI.

[0273] In wireless communication systems, the mmWave band (e.g., 7.125 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 band can be 120 or 240 kHz, and the SCS of other signals / channels (e.g., PDCCH, PDSCH, PUSCH, etc.) can be 60 or 120 kHz.

[0274] Larger SCSs can be used in the frequency bands 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 for each SCS can be defined as shown in Table 8 below.

[0275] [Table 8]

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

[0277] 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 timing 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.

[0278] In other words, 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 another frequency band.

[0279] Figure 10 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.

[0280] The UE can receive configuration information S1010 from the base station related to at least one TDRA line, which includes multiple SLIVs for PDSCH.

[0281] Specifically, the UE can receive configuration information related to at least one TDRA line on the downlink BWP of the serving cell via higher-layer signaling.

[0282] For example, configuration information associated with at least one TDRA line can be sent from the base station to the UE via RRC signaling (e.g., 'pdsch-TimeDomainAllocationListForMultiPDSCH').

[0283] The UE can receive the first downlink control information (DCI) S1020 from the base station.

[0284] In this case, the first DCI may include indication information of the Transport Configuration Indicator (TCI) status, but may not include downlink (DL) assignment information.

[0285] Here, the DL assignment information may include information for scheduling the PDSCH. Additionally, the TCI status indication information may include information for updating at least one DL reference signal (RS) with a quasi-co-location (QCL) relationship.

[0286] Furthermore, the number of SLIVs in a specific TDRA line indicated by the first DCI in at least one TDRA line can be 1. That is, the UE can expect the number of SLIVs in a specific TDRA line indicated by the first DCI to be no more than 1.

[0287] The UE can send a HARQ-ACK codebook to the base station, which includes a first Hybrid Automatic Repeat Request (HARQ)-Acknowledgement (ACK) message for the TCI status indication.

[0288] Here, when the PDSCH reception is scheduled by the first DCI using at least one decoded CBG (block group) or at least one transport block, the position of the HARQ-ACK information in the HARQ-ACK codebook can be the same as the position of the HARQ-ACK information for the PDSCH reception.

[0289] As another example of this disclosure, the UE may receive from the base station a second DCI that includes information indicating that the secondary cell (SCell) is in hibernation and does not include information for scheduling the PDSCH.

[0290] In this scenario, the UE can send HARQ-ACK information to the base station for the second DCI. Furthermore, the HARQ-ACK information value can include ACK.

[0291] Figure 11 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.

[0292] The base station can send configuration information S1110 to the UE related to at least one TDRA line, which includes multiple SLIVs for PDSCH.

[0293] The base station can send a first DCI S1120 to the UE. In this case, the first DCI may include indication information of the TCI status, but may not include DL assignment information. In addition, the number of SLIVs in a specific TDRA line indicated by the first DCI in at least one TDRA line may be 1.

[0294] The operations and parameters associated with S1110 and S1120 can correspond to the operations and parameters associated with S1010 and S1020, so redundant descriptions will be omitted.

[0295] The following sections will describe in more detail the scheduling methods for multiple PXSCHs in the case of multiple PXSCHs and the methods for configuring the HARQ-ACK codebook corresponding to M-DCI.

[0296] Implementation Method 1

[0297] Implementation 1 describes a method for configuring a type 1 HARQ-ACK codebook when time-domain binding is configured.

[0298] When time-domain bundling is configured for a cell that has M-DCI configured (for PDSCH) (i.e., when 'enableTimeDomainHARQ-Bundling' is configured as a higher-layer parameter), the UE can configure a type 1 HARQ-ACK codebook according to Tables 9 and 10.

[0299] [Table 9]

[0300]

[0301]

[0302] [Table 10]

[0303]

[0304]

[0305]

[0306] Specifically, Table 9 illustrates the method for determining the candidate PDSCH reception timing based on a specific SLIV for each TDRA table index. When multiple SLIVs correspond to a specific TDRA table index, the last SLIV can be identified as the specific SLIV.

[0307] Furthermore, Table 10 illustrates the method for mapping HARQ-ACK information to the determined candidate PDSCH reception timings. When a scheduled PDSCH corresponds to a specific PDSCH reception timing and the corresponding PDSCH corresponds to the last SLIV, bundled HARQ-ACK information can be mapped. Conversely, when the corresponding PDSCH does not correspond to the last SLIV, NACK can be mapped.

[0308] As another example, for a cell that has time-domain bundling configured and M-DCI configured (for PDSCH) as shown in Table 9, three consecutive time slots can be scheduled using an index on the TDRA table for the corresponding M-DCI scheduling. Furthermore, the SLIVs for each time slot can be configured identically.

[0309] Alternatively, assume that the K1 value configured for the corresponding cell is 2 or 3. According to Table 9, the type 1 HARQ-ACK codebook configuration for the PUCCH to be transmitted in slot #N can be determined by the K1 value. For example, if the K1 value is 3, then SLIV0 (i.e., the last SLIV) in slot #N-3 can be determined as the first PDSCH reception timing; if the K1 value is 2, then SLIV0 (i.e., the last SLIV) in slot #N-2 can be determined as the second PDSCH reception timing.

[0310] Since three consecutive PDSCHs are scheduled on slots #N-4 / N-3 / N-2 (via M-DCI), and the UE is instructed to set the K1 value to 2, HARQ-ACK feedback for the three PDSCHs can be sent on slot #N PUCCH.

[0311] The method for mapping HARQ-ACK information for each PDSCH reception timing will be described below, as shown in Table 10. Since the PDSCH scheduled through the corresponding DCI slot #N-4 does not correspond to the PDSCH reception timing determined by the method according to Table 9, the UE may not generate the corresponding HARQ-ACK information.

[0312] Furthermore, since the PDSCH of slot #N-3 scheduled through the corresponding DCI corresponds to the first PDSCH reception timing determined according to the method in Table 9, the corresponding HARQ-ACK bit can be generated. However, since the corresponding PDSCH does not correspond to the last SLIV, the UE maps NACK information. That is, since slots #N-5 / N-4 / N-3, which use slot #N-3 as the last SLIV, cannot be scheduled simultaneously, the UE can map NACK information.

[0313] Furthermore, since the PDSCH in slot #N-2, scheduled through the corresponding DCI, corresponds to the second PDSCH reception timing determined according to the method in Table 9, HARQ-ACK bits can be generated. Since the corresponding PDSCH corresponds to the last SLIV, the UE can bundle (i.e., by performing a logical AND operation) and map the HARQ-ACK information of the three PDSCHs received in slots #N-4 / N-3 / N-2.

[0314] The above operation assumes that the number of PDSCHs scheduled for a specific PDSCH reception time is not multiple. For example, such as Figure 9 As shown in (a), it can be assumed that the two PDSCHs cannot overlap with SLIV0 in slot #N-3 via different DCIs.

[0315] However, it is assumed that some time slots / symbols that can be scheduled by M-DCI overlap with semi-static UL symbols (i.e., UL symbols set by 'tdd-UL-DL-ConfigurationCommon' or 'tdd-UL-DL-ConfigurationDedicated')).

[0316] In this situation, even if some PDSCHs are scheduled, the UE may not receive PDSCHs that overlap with the corresponding semi-static UL symbols. The number of PDSCHs that can be scheduled for a specific PDSCH reception timing can be greater than one. A method for addressing this problem will be described below.

[0317] As an example, for a cell that is configured with time-domain binding and has configured M-DCI (for PDSCH), three consecutive time slots can be scheduled by an index on the TDRA table that can be scheduled by the corresponding M-DCI, and the SLIVs of each time slot can be configured identically.

[0318] Alternatively, assume that the K1 value configured for the corresponding cell is 2 or 3. According to Table 9, the Type 1 HARQ-ACK codebook configuration for the PUCCH to be transmitted in slot #N can be determined based on the K1 value. For example, if the K1 value is 3, then SLIV0 (i.e., the last SLIV) in slot #N-3 can be determined as the first PDSCH reception opportunity; and when the K1 value is 2, then SLIV0 (i.e., the last SLIV) in slot #N-2 can be determined as the second PDSCH reception opportunity.

[0319] Alternatively or in another location, such as Figure 9 As shown in (b), it is assumed that time slots #N-4 / N-3 are configured as semi-static UL time slots. Even if the PDSCH is scheduled via M-DCI in the corresponding time slot, the UE may consider the corresponding PDSCH invalid and may not receive the corresponding PDSCH.

[0320] For example, PDSCH on time slots #N-4 / N-3 / N-2 can be scheduled via M-DCI#1, and the K1 value can be indicated as 2. Alternatively, PDSCH on time slots #N-5 / N-4 / N-3 can be scheduled via M-DCI#2, and the K1 value can be indicated as 3.

[0321] In this scenario, a UE that has already received both M-DCI#1 and M-DCI#2 can receive PDSCH in time slots #N-5 and #N-2 (but not in time slots #N-4 / N-3). Furthermore, the UE can send HARQ-ACK information corresponding to each PDSCH via PUCCH in time slot #N. In the first PDSCH reception timing determined by Table 9, there may be two PDSCHs in time slot #N-3 scheduled by M-DCI#1 and two PDSCHs in time slot #N-3 scheduled by M-DCI#2.

[0322] As described above, assume there are multiple PDSCHs corresponding to a single PDSCH reception timing. If, among the multiple PDSCHs corresponding to a specific PDSCH reception timing, there exists a PDSCH corresponding to the last SLIV, the UE can map bundled HARQ-ACK information including the corresponding last SLIV (for the corresponding PDSCH reception timing). When none of the multiple PDSCHs corresponding to a specific PDSCH reception timing correspond to the last SLIV, the UE can map NACK information (for the corresponding PDSCH reception timing).

[0323] like Figure 9 As shown in (b), at the first PDSCH reception timing, there may be a PDSCH on slot #N-3 scheduled by M-DCI#1 and a PDSCH on slot #N-3 scheduled by M-DCI#2. At this time, since the PDSCH scheduled by M-DCI#2 corresponds to the last SLIV, the HARQ-ACK information of slot #N-5 PDSCH in slots #N-5 / N-4 / N-3 PDSCH scheduled by M-DCI#2 can be mapped to the corresponding PDSCH reception timing.

[0324] Alternatively or in another location, such as Figure 9 As shown in (b), when scheduling invalid PDSCHs in the same time slot is allowed, it is possible to schedule multiple M-DCIs with one PDSCH reception timing as the last SLIV.

[0325] As an example, such as Figure 9 As shown in (c), it is assumed that time slot #N-3 / N-2 is configured as a semi-static UL time slot. Line index 0 is indicated by M-DCI#1 so that PDSCH on time slot #N-4 / N-3 / N-2 can be scheduled, and line index 1 is indicated by M-DCI#2 so that PDSCH on time slot #N-5 / N-3 / N-2 can be scheduled.

[0326] At this time, the UE does not attempt to receive invalid PDSCH, and can receive time slot #N-4PDSCH scheduled through M-DCI#1 and time slot #N-5PDSCH scheduled through M-DCI#2.

[0327] However, when configuring the type 1 HARQ-ACK codebook, since the last SLIV of both PDSCHs is slot #N-2, and only one PDSCH reception timing is determined for the two last SLIVs, ambiguity may occur related to HARQ-ACK information for slots #N-4PDSCH and #N-5PDSCH.

[0328] In this case, the UE may not expect to schedule multiple (M-)DCIs with one PDSCH reception timing as the last SLIV.

[0329] like Figure 9 As shown in (c), when receiving M-DCI#1 in which a PDSCH is scheduled on slot #N-4 / N-3 / N-2, the UE may not expect to receive an additional DCI indicating the last SLIV corresponding to the PDSCH reception timing associated with the SLIV on the corresponding slot #N-2 (e.g., receiving M-DCI#2 scheduled PDSCH on slot #N-5 / N-3 / N-2). Alternatively, even if the UE receives the additional DCI, the UE may ignore or discard it.

[0330] As another example, such as Figure 9 As shown in (c), when receiving M-DCI#2, in which PDSCH is scheduled on slot #N-5 / N-3 / N-2, the UE may not expect to receive an additional DCI indicating the last SLIV of the PDSCH reception timing associated with the SLIV on the corresponding slot #N-2 (e.g., receiving M-DCI#1 scheduled PDSCH on slot #N-4 / N-3 / N-2). Alternatively, even if the UE receives the additional DCI, the UE may ignore or discard it.

[0331] Implementation Method 2

[0332] The above-described SPS PDSCH activation / release method via M-DCI can be extended even when the corresponding M-DCI does not schedule PDSCH (e.g., SCell sleep indicator or TCI status update indicator).

[0333] Specifically, when at least one row index in the TDRA row index configured for the M-DCI is linked to only a single SLIV, a SCell sleep indication or TCI status update indication via the corresponding M-DCI is permitted. Additionally, when a SCell sleep indication or TCI status update indication is given via the corresponding M-DCI, the UE can expect the indication to be a TDRA row index linked to only a single SLIV.

[0334] Alternatively, even if all or some TDRA line indices configured for the M-DCI are linked to multiple SLIVs, the TDRA line index indicating that multiple SLIVs are linked can still be allowed when the corresponding M-DCI indicates SCell sleep or TCI state update. In this case, the UE can consider only a specific SLIV (e.g., the first or last SLIV) among the multiple SLIVs linked to the indicated TDRA line index as valid.

[0335] When configuring the HARQ-ACK timing and HARQ-ACK codebook corresponding to the DCI indicating SCell sleep or TCI state update, the UE can determine the HARQ-ACK bit position based on specific SLIV information.

[0336] As an example, suppose that {slot n+1,SLIV#1} and {slot n+2,SLIV#2} are configured for the TDRA row index indicated by the M-DCI (including information indicating SCell hibernation or TCI status update) sent in slot n.

[0337] At this point, the HARQ-ACK timing corresponding to the corresponding DCI can be determined based on the last SLIV{slot n+2, SLIV#2}. Furthermore, when configuring the HARQ-ACK codebook (e.g., when configuring a type 1 HARQ-ACK codebook), the UE can send the ACK / NACK information for the DCI to the HARQ-ACK bit position corresponding to the SLIV.

[0338] Implementation Method 3

[0339] Suppose that among all K HPNs configured for a specific cell with M-PDSCH DCI, the number of HPNs with HARQ operation enabled is N (>1), and the number of HPNs with disabled operation is KN. In this case, Implementation 3 describes an enhanced Type 2 HARQ-ACK codebook configuration method.

[0340] Alternatively, it is assumed that all K HPNs are configured to be used in at least one of the multiple cells in the same PUCCH cell group that have configured M-PDSCHDCI. In this case, when the number of HPNs with HARQ operation enabled is N (>1) and the number of HPNs with disabled operation is KN, the third embodiment describes a method for an enhanced configuration type 2 HARQ-ACK codebook.

[0341] When performing DAI counting for each DCI, a first subcodebook can be configured for the single PDSCH case, and a second sub-CB can be configured for the multiple PDSCH case. Configuring a separate sub-CB means that the C / T-DAI value can be determined and signaled independently for each sub-CB. In other words, the order / total number of DCIs / PDSCHs scheduled for each sub-CB can be determined / signed independently.

[0342] At this point, if the number of enabled HPNs among those scheduled via M-DCI (or S-DCI) is one or fewer, the UE can map the HARQ-ACK bit corresponding to the corresponding DCI to the first sub-CB. Alternatively, when the number of enabled HPNs among those scheduled via M-DCI is two or more, the UE can map the HARQ-ACK bit corresponding to the corresponding DCI to the second sub-CB.

[0343] In this scenario, Z = min{max_HPN, max_XY} for each cell can be obtained based on the max_HPN and max_XY values ​​for each cell (for the second sub-CB). Furthermore, the number of HARQ-ACK bits corresponding to a DAI value can be calculated based on the maximum Z value among all cells.

[0344] Here, the max_XY value can be defined as the X*Y value of a specific serving cell configured with M-DCI, and Y can refer to the maximum number of PDSCHs that M-DCI can schedule. For example, for a cell configured with 2TB but without space bundling, X can be calculated as 2. As another example, for a cell configured with 2TB but with space bundling, or a cell configured with 1TB, X can be calculated as 1.

[0345] In this case, max_HPN can be determined by the number of enabled HPNs configured for a specific serving cell with M-DCI and Y (i.e., the maximum number of PDSCHs that M-DCI can schedule). max_HPN can refer to the maximum number of HPNs that can be allocated to Y PDSCHs.

[0346] For example, in the corresponding serving cell, 5 out of a total of 8 HPNs are configured as enabled HPNs {0, 2, 3, 4, 6}, and Y can be 4. When scheduling 4 consecutive PDSCHs, the maximum number of enabled HPNs that can be allocated to the corresponding 4 PDSCH windows is 3, so the max_HPN number can be 3.

[0347] Alternatively, the maximum value of max_XY_total among multiple cells configured with M-DCI in the same PUCCH cell group can be calculated. The maximum value of max_HPN_total among each cell in the multiple cells configured with M-DCI in the same PUCCH cell group can also be calculated. Furthermore, the number of HARQ-ACK bits corresponding to a DAI value of the second sub-CB can be determined based on the value of min{max_HPN_total, max_XY_total}.

[0348] As described above, assume that the number of HARQ-ACK bits corresponding to a DAI value is calculated based on (max_XY) or min{max_HPN_total,max_XY_total}. In this case, the UE can map the HARQ-ACK bits corresponding to the enabled HPN to the lowest (or highest) bit index in the HARQ-ACK payload corresponding to a DAI value.

[0349] Alternatively, for the HARQ-ACK bit corresponding to the enabled HPN, the lower bits of the HARQ ID can be mapped to a lower (or higher) bit index, or the bits corresponding to an earlier PDSCH reception time can be mapped to a lower (or higher) bit index.

[0350] The HPN is indicated by M-DCI, and the indicated HPN value is incremented by 1 from the first (valid) PDSCH (modulo operation is performed if necessary), thereby mapping each (valid) PDSCH.

[0351] Here, a valid PDSCH can refer to a PDSCH that does not overlap with a UL symbol configured by higher-level signaling (e.g., 'tdd-UL-DL-ConfigurationCommon' or 'tdd-UL-DL-ConfigurationDedicated'). As another example, an invalid PDSCH can refer to a PDSCH that overlaps with a UL symbol configured by higher-level signaling (e.g., 'tdd-UL-DL-ConfigurationCommon' or 'tdd-UL-DL-ConfigurationDedicated').

[0352] Alternatively, when time-domain bundling is configured, the HARQ-ACK bit corresponding to the PDSCH assigned to a disabled HPN can be considered the same as the HARQ-ACK bit corresponding to an invalid PDSCH. For example, bundling can be performed without excluding PDSCHs assigned to disabled HPNs. As another example, when configuring a bundling group, PDSCHs assigned to disabled HPNs can be excluded.

[0353] The above method is not limited to the configuration of type 2 HARQ-ACK codebooks, and can be equally applied to other types of codebooks (e.g., type 1 or type 3 HARQ-ACK codebooks).

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

[0355] Figure 12 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, or a combination of one or more of the detailed examples thereof) can be applied.

[0356] Here, the UE / network side is exemplary and can be referenced. Figure 13 The various devices described are used as alternatives. Figure 12 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 12 Some of the steps are shown. Additionally, in Figure 12 In the network-side / UE operations, the aforementioned uplink sending / receiving operations can be involved or used.

[0357] 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 Remote Radio Headers (RRHs) / Remote Radio Units (RRUs).

[0358] Additionally, a base station can generally refer to the entity that performs data transmission and reception with the UE. 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.

[0359] The UE can receive configuration information S105 from the network side.

[0360] For example, configuration information may include information related to network-side configuration (i.e., TRP configuration), resource allocation related to downlink / uplink transmission and reception, and so on.

[0361] Configuration information can be sent via higher-level signaling (e.g., RRC, MACCE, etc.). This configuration information may include details related to configuration-based authorization (CG) uplink transmissions. Furthermore, when the configuration information is predefined or configured, the corresponding steps can be omitted.

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

[0363] As another example, the configuration information may include information associated with at least one TDRA line, which includes multiple SLIVs for PDSCH (e.g., 'pdsch-TimeDomainAllocationListForMultiPDSCH').

[0364] As another example, configuration information may include information related to M-DCI, HARQ-ACK codebook (e.g., the type of HARQ-ACK codebook), and TCI status.

[0365] For example, UE ( Figure 13 In step S105 above, 100 or 200) are obtained from the network side ( Figure 13 The operation of receiving configuration information (200 or 100) can be performed by Figure 13 The device implementation in [the document] (will be described later). For example, refer to [reference]. Figure 13 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.

[0366] The UE can receive control information S110 from the network side.

[0367] Specifically, the UE can receive M-DCI / S-DCI from the network side. As an example, M-DCI / S-DCI may include information for scheduling DL / UL. As another example, M-DCI / S-DCI may include indication information of TCI status instead of DL assignment information. As yet another example, M-DCI / S-DCI may include information indicating SCell sleep and may not include information for scheduling PDSCH.

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

[0369] For example, UE ( Figure 13 In step S110 above, 100 or 200) are obtained from the network side ( Figure 13 The operation of receiving control information (200 or 100) can be described later. Figure 13 The device implementation in [the context]. For example, refer to [reference]. Figure 13 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.

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

[0371] As an example, the UE can send a HARQ-ACK codebook, including HARQ-ACK information for TCI status indication, to the network side via PUCCH. As another example, the UE can send HARQ-ACK information for DCI to the network side via PUCCH, which includes information indicating SCell sleep but does not include information for scheduling PDSCH.

[0372] As another example, the UE can receive one or more PDSCHs scheduled by the DCI from the network side. Furthermore, the UE can send HARQ-ACK information for one or more PDSCHs to the network side via PUCCH.

[0373] 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, or one or more combinations thereof in the detailed implementation methods).

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

[0375] For example, refer to Figure 13 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.

[0376] The general apparatus disclosed herein can be used

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

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

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

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

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

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

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

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

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

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

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

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

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

[0390] 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 configuration information from the base station relating to at least one Time Domain Resource Allocation (TDRA) line, including at least one start and length indicator value (SLIV) for at least one Physical Downlink Shared Channel (PDSCH); as well as Receive first downlink control information (DCI) from the base station. The first DCI includes Transmission Configuration Indicator (TCI) status indication information but does not include downlink DL assignment information. Specifically, based on a second DCI received from the base station, which includes information related to the secondary cell SCell sleep but does not include information for scheduling PDSCH, a first Hybrid Automatic Repeat Request-Acknowledgement (HARQ-ACK) message is sent to the base station for the second DCI, and the value of the first HARQ-ACK message is ACK. Wherein, the number of SLIVs in a specific TDRA line indicated by the first DCI in at least one TDRA line is 1, and Wherein, the position of the second HARQ-ACK information for the first DCI in the HARQ-ACK codebook is the same as the position of the third HARQ-ACK information related to the third DCI in the HARQ-ACK codebook, and the third DCI schedules the reception of PDSCH with at least one decoded code block group CBG or at least one transport block.

2. The method according to claim 1, wherein, The DL assignment information includes information for scheduling the at least one PDSCH.

3. The method according to claim 1, wherein, The TCI status indication information includes information for updating at least one DL reference signal RS with a quasi-co-located QCL relationship.

4. 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: Through the at least one transceiver, configuration information related to at least one Time Domain Resource Allocation (TDRA) line, including at least one start and length indicator value (SLIV) for the Physical Downlink Shared Channel (PDSCH), is received from the base station; and The first downlink control information (DCI) is received from the base station through the at least one transceiver. The first DCI includes Transmission Configuration Indicator (TCI) status indication information but does not include downlink DL assignment information. Specifically, based on a second DCI received from the base station, which includes information related to the secondary cell SCell sleep but does not include information for scheduling PDSCH, a first Hybrid Automatic Repeat Request-Acknowledgement (HARQ-ACK) message is sent to the base station for the second DCI, and the value of the first HARQ-ACK message is ACK. Wherein, the number of SLIVs in a specific TDRA line indicated by the first DCI in at least one TDRA line is 1, and Wherein, the position of the second HARQ-ACK information for the first DCI in the HARQ-ACK codebook is the same as the position of the third HARQ-ACK information related to the third DCI in the HARQ-ACK codebook, and the third DCI schedules the reception of PDSCH with at least one decoded code block group CBG or at least one transport block.

5. A method performed by a base station, the method comprising the following steps: Send configuration information to the user equipment (UE) related to at least one time-domain resource allocation (TDRA) line, including at least one start and length indicator value (SLIV) for the physical downlink shared channel (PDSCH); as well as Send the first downlink control information (DCI) to the UE. The first DCI includes Transmission Configuration Indicator (TCI) status indication information but does not include downlink DL assignment information. Specifically, based on a second DCI received from the base station, which includes information related to secondary cell SCell sleep but does not include information for scheduling PDSCH, a first Hybrid Automatic Repeat Request-Acknowledgement (HARQ-ACK) message for the second DCI is sent to the base station, and the value of the first HARQ-ACK message is ACK. Wherein, the number of SLIVs in a specific TDRA line indicated by the first DCI in at least one TDRA line is 1, and Wherein, the position of the second HARQ-ACK information for the first DCI in the HARQ-ACK codebook is the same as the position of the third HARQ-ACK information related to the third DCI in the HARQ-ACK codebook, and the third DCI schedules the reception of PDSCH with at least one decoded code block group CBG or at least one transport block.

6. 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: Through the at least one transceiver, configuration information related to at least one Time Domain Resource Allocation (TDRA) line, including at least one start and length indicator value (SLIV) for the Physical Downlink Shared Channel (PDSCH), is transmitted to the User Equipment (UE); and The first downlink control information (DCI) is sent to the UE through the at least one transceiver. The first DCI includes Transmission Configuration Indicator (TCI) status indication information but does not include downlink DL assignment information. Specifically, based on a second DCI received from the base station, which includes information related to secondary cell SCell sleep but does not include information for scheduling PDSCH, a first Hybrid Automatic Repeat Request-Acknowledgement (HARQ-ACK) message for the second DCI is sent to the base station, and the value of the first HARQ-ACK message is ACK. Wherein, the number of SLIVs in a specific TDRA line indicated by the first DCI in at least one TDRA line is 1, and Wherein, the position of the second HARQ-ACK information for the first DCI in the HARQ-ACK codebook is the same as the position of the third HARQ-ACK information related to the third DCI in the HARQ-ACK codebook, and the third DCI schedules the reception of PDSCH with at least one decoded code block group CBG or at least one transport block.

7. 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, which, when operational, is coupled to the at least one processor and stores instructions for performing operations when executed by the at least one processor. The operation includes: Receive configuration information from the base station relating to at least one Time Domain Resource Allocation (TDRA) line, including at least one start and length indicator value (SLIV) for the Physical Downlink Shared Channel (PDSCH); and Receive first downlink control information (DCI) from the base station. The first DCI includes Transmission Configuration Indicator (TCI) status indication information but does not include downlink DL assignment information. Specifically, based on a second DCI received from the base station, which includes information related to the secondary cell SCell sleep but does not include information for scheduling PDSCH, a first Hybrid Automatic Repeat Request-Acknowledgement (HARQ-ACK) message is sent to the base station for the second DCI, and the value of the first HARQ-ACK message is ACK. Wherein, the number of SLIVs in a specific TDRA line indicated by the first DCI in at least one TDRA line is 1, and Wherein, the position of the second HARQ-ACK information for the first DCI in the HARQ-ACK codebook is the same as the position of the third HARQ-ACK information related to the third DCI in the HARQ-ACK codebook, and the third DCI schedules the reception of PDSCH with at least one decoded code block group CBG or at least one transport block.

8. At least one non-transitory computer-readable medium storing at least one instruction, wherein, The at least one instruction executed by at least one processor controls the device to execute: Receive configuration information from the base station related to at least one Time Domain Resource Allocation (TDRA) line, including at least one start and length indicator value (SLIV) for the Physical Downlink Shared Channel (PDSCH); as well as Receive first downlink control information (DCI) from the base station. The first DCI includes Transmission Configuration Indicator (TCI) status indication information but does not include downlink DL assignment information. Specifically, based on a second DCI received from the base station, which includes information related to the secondary cell SCell sleep but does not include information for scheduling PDSCH, a first Hybrid Automatic Repeat Request-Acknowledgement (HARQ-ACK) message is sent to the base station for the second DCI, and the value of the first HARQ-ACK message is ACK. Wherein, the number of SLIVs in a specific TDRA line indicated by the first DCI in at least one TDRA line is 1, and Wherein, the position of the second HARQ-ACK information for the first DCI in the HARQ-ACK codebook is the same as the position of the third HARQ-ACK information related to the third DCI in the HARQ-ACK codebook, and the third DCI schedules the reception of PDSCH with at least one decoded code block group CBG or at least one transport block.

Images