Methods for receiving and transmitting downlink channels, user equipment, processing devices, base stations, storage media, and computer program products.

Abstract

The UE may: determine a first transmission time of a first HARQ-ACK for a first downlink channel associated with a first HARQ process; and receive a second downlink channel associated with the first HARQ process. Receiving the second downlink channel of the first HARQ process may include: receiving the second downlink channel after the first transmission time based on the first HARQ-ACK not being subject to HARQ delay; and receiving the second downlink channel after the second transmission time based on the first HARQ-ACK being subject to HARQ delay and the first transmission time being determined by HARQ delay from a second transmission time earlier than the first transmission time.

Description

Technical Field

[0001] This disclosure relates to a wireless communication system. Background Technology

[0002] Technologies such as machine-to-machine (M2M) communication, machine-type communication (MTC), and various devices requiring high data throughput (e.g., smartphones and tablet PCs) have emerged and become widespread. Consequently, the data throughput required to be processed in cellular networks is increasing rapidly. To meet this rapidly increasing data throughput, carrier aggregation or cognitive radio technologies have been developed for the efficient use of more frequency bands, as well as multiple-input multiple-output (MIMO) or multi-base station (BS) cooperation technologies to improve the data transmission capacity on limited frequency resources.

[0003] As more and more communication devices require greater communication capacity, there is a need for enhanced mobile broadband (eMBB) communication relative to traditional radio access technologies (RAT). Furthermore, massive machine-type communication (mMTC), which enables the provision of various services anytime, anywhere by connecting multiple devices and objects to each other, is a major issue to be considered in next-generation communications.

[0004] The design of communication systems for service / user equipment (UE) that are sensitive to reliability and latency is also under discussion. The introduction of next-generation RATs is being considered, taking into account eMBB communication, mMTC, and ultra-reliable low-latency communication (URLLC). Summary of the Invention

[0005] Technical issues

[0006] With the introduction of new radio communication technologies, the number of UEs to which a BS should provide services within a designated resource area is constantly increasing, as is the amount of data and control information that the BS sends / receives to / from the UEs it serves. Since the amount of resources available to the BS for communicating with UEs is limited, a new method is needed for the BS to efficiently receive / transmit uplink / downlink data and / or uplink / downlink control information using limited radio resources. In other words, due to the increasing density of nodes and / or UEs, a method is needed to efficiently utilize high-density nodes or high-density UEs for communication.

[0007] There is also a need for a method to effectively support various services with different requirements in wireless communication systems.

[0008] For applications where performance is sensitive to latency / delay, overcoming latency or delay is a significant challenge.

[0009] In addition, appropriate scheduling constraints for the Hybrid Automatic Repeat Request (HARQ) process need to be defined according to various scenarios.

[0010] The purposes that can be achieved by utilizing this disclosure are not limited to those specifically described above, and those skilled in the art will understand more clearly from the following detailed description other purposes not described herein.

[0011] Technical solution

[0012] In one aspect of this disclosure, a method is provided for a user equipment (UE) to receive a downlink channel in a wireless communication system. The method may include the steps of: determining a first transmission time of a first HARQ-ACK (HARQ-ACK) of a first downlink channel associated with a first Hybrid Automatic Repeat Request (HARQ) process; and receiving a second downlink channel associated with the first HARQ process. Receiving the second downlink channel of the first HARQ process may include: receiving the second downlink channel after the first transmission time based on the first HARQ-ACK not being subject to HARQ delay; and receiving the second downlink channel after the second transmission time based on the first HARQ-ACK being subject to HARQ delay and the first transmission time being determined by HARQ delay from a second transmission time earlier than the first transmission time.

[0013] In another aspect of this disclosure, a UE is provided for receiving a downlink channel in a wireless communication system. The UE may include: at least one transceiver; at least one processor; and at least one computer memory operatively connected to the at least one processor and configured to store instructions that, when executed, cause the at least one processor to perform an operation. The operation may include: determining a first transmission time of a first HARQ-ACK for a first downlink channel associated with a first HARQ process; and receiving a second downlink channel associated with the first HARQ process. Receiving the second downlink channel of the first HARQ process may include: receiving the second downlink channel after the first transmission time based on the first HARQ-ACK not being subject to HARQ delay; and receiving the second downlink channel after the second transmission time based on the first HARQ-ACK being subject to HARQ delay and the first transmission time being determined by HARQ delay from a second transmission time earlier than the first transmission time.

[0014] In another aspect of this disclosure, a processing apparatus in a wireless communication system is provided. The processing apparatus may include: at least one processor; and at least one computer memory operatively connected to the at least one processor and configured to store instructions that, when executed, cause the at least one processor to perform an operation. The operation may include: determining a first transmission time of a first HARQ-ACK for a first downlink channel associated with a first HARQ process; and receiving a second downlink channel associated with the first HARQ process. Receiving the second downlink channel of the first HARQ process may include: receiving the second downlink channel after the first transmission time based on the first HARQ-ACK not being subject to HARQ delay; and receiving the second downlink channel after the second transmission time based on the first HARQ-ACK being subject to HARQ delay and the first transmission time being determined by HARQ delay from a second transmission time earlier than the first transmission time.

[0015] In another aspect of this disclosure, a computer-readable storage medium is provided. This computer-readable storage medium can be configured to store at least one computer program including instructions that, when executed by at least one processor, cause the at least one processor to perform operations against a UE. The operations may include: determining a first transmission time of a first HARQ-ACK for a first downlink channel associated with a first HARQ process; and receiving a second downlink channel associated with the first HARQ process. Receiving the second downlink channel of the first HARQ process may include: receiving the second downlink channel after the first transmission time based on the first HARQ-ACK not being subject to HARQ delay; and receiving the second downlink channel after the second transmission time based on the first HARQ-ACK being subject to HARQ delay and the first transmission time being determined by HARQ delay from a second transmission time earlier than the first transmission time.

[0016] In another aspect of this disclosure, a computer program stored in a computer-readable storage medium is provided. The computer program may include at least one program code comprising instructions that, when executed, cause at least one processor to perform operations. The operations may include: determining a first transmission time of a first HARQ-ACK for a first downlink channel associated with a first HARQ process; and receiving a second downlink channel associated with the first HARQ process. Receiving the second downlink channel of the first HARQ process may include: receiving the second downlink channel after the first transmission time based on the first HARQ-ACK not being subject to HARQ delay; and receiving the second downlink channel after the second transmission time based on the first HARQ-ACK being subject to HARQ delay and the first transmission time being determined by HARQ delay from a second transmission time earlier than the first transmission time.

[0017] In another aspect of this disclosure, a method is provided for a base station (BS) to transmit a downlink channel to a user equipment (UE) in a wireless communication system. The method may include: determining a first reception time of a first HARQ-ACK for a first downlink channel associated with a first HARQ process; and transmitting a second downlink channel associated with the first HARQ process. Transmitting the second downlink channel for the first HARQ process may include: transmitting the second downlink channel after the first reception time based on the first HARQ-ACK not being subject to HARQ delay; and transmitting the second downlink channel after the second reception time based on the first HARQ-ACK being subject to HARQ delay and the first reception time being determined by HARQ delay from a second reception time earlier than the first reception time.

[0018] In another aspect of this disclosure, a BS configured to transmit a downlink channel to a UE in a wireless communication system is provided. The BS may include: at least one transceiver; at least one processor; and at least one computer memory operatively connected to the at least one processor and configured to store instructions that, when executed, cause the at least one processor to perform an operation. The operation may include: determining a first reception time for a first HARQ-ACK of a first downlink channel associated with a first HARQ process; and transmitting a second downlink channel associated with the first HARQ process. Transmitting the second downlink channel of the first HARQ process may include: transmitting the second downlink channel after the first reception time based on the first HARQ-ACK not being subject to HARQ delay; and transmitting the second downlink channel after the second reception time based on the first HARQ-ACK being subject to HARQ delay and the first reception time being determined by HARQ delay from a second reception time earlier than the first reception time.

[0019] In all aspects of this disclosure, based on the fact that the first HARQ-ACK undergoes HARQ delay and the first transmission time is determined by HARQ delay from the second transmission time, the second downlink channel may begin before the end of the first transmission time.

[0020] In various aspects of this disclosure, the first downlink channel may be a Physical Downlink Shared Channel (PDSCH) based on Semi-Persistent Scheduling (SPS).

[0021] In various aspects of this disclosure, the second downlink channel can be used for retransmission of transport blocks included in the SPS-based PDSCH.

[0022] In all respects of this disclosure, the second downlink channel may be based on a dynamically scheduled PDSCH.

[0023] In various aspects of this disclosure, the operation of the UE may include: determining a third transmission time for the second HARQ-ACK of the second downlink channel; abandoning the transmission of the first HARQ-ACK within a first transmission time; and transmitting the second HARQ-ACK at the third transmission time.

[0024] The solutions described above are merely some examples of this disclosure, and those skilled in the art can deduce and understand various examples of the technical features incorporated herein from the following detailed description.

[0025] Beneficial effects

[0026] According to some implementations of this disclosure, wireless communication signals can be transmitted / received efficiently. Therefore, the overall throughput of the wireless communication system can be increased.

[0027] According to some implementations of this disclosure, various services with different requirements can be efficiently supported in a wireless communication system.

[0028] According to some implementations of this disclosure, the delay / latency generated during radio communication between communication devices can be reduced.

[0029] According to some implementations of this disclosure, the increase in overall system latency caused by scheduling constraints related to the Hybrid Automatic Repeat Request (HARQ) process can be prevented.

[0030] According to some implementation methods in this specification, the base station can be allowed to schedule other transmissions as needed, thereby improving the scheduling flexibility of the BS and reducing the overall system latency.

[0031] The effects of this disclosure are not limited to those specifically described above. Those skilled in the art will understand more clearly from the following detailed description other effects not described herein. Attached Figure Description

[0032] The accompanying drawings are included to provide a further understanding of this disclosure. The drawings illustrate examples of implementations of this disclosure and, together with the detailed description, serve to illustrate the implementations of this disclosure:

[0033] Figure 1 An example of a communication system 1 to which the implementation of this disclosure is applied is shown;

[0034] Figure 2 This is a block diagram illustrating an example of a communication device capable of performing the methods according to this disclosure;

[0035] Figure 3 Another example of a wireless device capable of implementing the embodiments of this disclosure is shown;

[0036] Figure 4 An example of a frame structure used in a wireless communication system based on the 3rd Generation Partnership Project (3GPP) is shown;

[0037] Figure 5 The resource grid showing the time slots;

[0038] Figure 6 The time slot structure used in a 3GPP-based system is shown.

[0039] Figure 7 Examples of Physical Downlink Shared Channel (PDSCH) Time Domain Resource Assignment (TDRA) caused by Physical Downlink Control Channel (PDCCH) and Physical Uplink Shared Channel (PUSCH) TDRA caused by PDCCH are shown.

[0040] Figure 8 This illustrates the HARQ-ACK transmission / reception process.

[0041] Figure 9 Examples of scheduling constraints based on some scenarios are shown;

[0042] Figure 10 This shows an example of HARQ-ACK postponement;

[0043] Figure 11 The operation flow of a user equipment (UE) according to some implementations of this disclosure is illustrated;

[0044] Figure 12 This illustrates another example of scheduling constraints based on certain scenarios;

[0045] Figure 13 Examples of HARQ timing according to some implementations of this disclosure are shown;

[0046] Figure 14The operation flow of a BS is shown according to some implementations of this disclosure. Detailed Implementation

[0047] In the following, implementations according to the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description given below with reference to the accompanying drawings is intended to illustrate exemplary implementations of the present disclosure, and not to show only implementations that can be implemented according to the present disclosure. The following detailed description includes specific details in order to provide a thorough understanding of the present disclosure. However, it will be apparent to those skilled in the art that the present disclosure can be practiced without these specific details.

[0048] In some cases, known structures and devices may be omitted or shown in block diagram form, thereby focusing on the essential features of the structures and devices so as not to obscure the concepts of this disclosure. The same reference numerals will be used throughout this disclosure to refer to the same or similar parts.

[0049] The following technologies, devices, and systems can be applied to various wireless multiple access systems. For example, multiple access systems may include Code Division Multiple Access (CDMA) systems, Frequency Division Multiple Access (FDMA) systems, Time Division Multiple Access (TDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single-Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Multi-Carrier Frequency Division Multiple Access (MC-FDMA) systems. CDMA can be implemented using radio technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented using radio technologies such as Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), and Enhanced Data Rate GSM Evolution (EDGE) (i.e., GERAN). OFDMA can be specifically implemented using radio technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, and Evolved UTRA (E-UTRA). UTRA is part of the Universal Mobile Telecommunications System (UMTS), and the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is part of E-UMTS that uses E-UTRA. 3GPP LTE uses OFDMA on the downlink (DL) and SC-FDMA on the uplink (UL). LTE-Advanced (LTE-A) is an evolution of 3GPP LTE.

[0050] For ease of description, this disclosure will be given under the assumption that it applies to LTE and / or the new RAT (NR). However, the technical features of this disclosure are not limited thereto. For example, although the following detailed description is based on a mobile communication system corresponding to a 3GPP LTE / NR system, the mobile communication system is applicable to any other mobile communication system except for matters specific to the 3GPP LTE / NR system.

[0051] For any terms and techniques used in this disclosure that are not described in detail, reference may be made to 3GPP-based standard specifications (e.g., 3GPP TS 36.211, 3GPP TS 36.212, 3GPP TS 36.213, 3GPP TS 36.321, 3GPP TS 36.300, 3GPP TS 36.331, 3GPP TS 37.213, 3GPP TS 38.211, 3GPP TS 38.212, 3GPP TS 38.213, 3GPP TS 38.214, 3GPP TS 38.300, 3GPP TS 38.331, etc.).

[0052] In the examples of this disclosure described later, if the apparatus “assumes” something, this could mean that the channel transmitting entity transmits the channel in accordance with the corresponding “assumption.” This could also mean that the channel receiving entity receives or decodes the channel in a form consistent with that “assumption,” provided that the channel is transmitted in accordance with that “assumption.”

[0053] In this disclosure, a user equipment (UE) can be fixed or mobile. Each of various devices that transmit and / or receive user data and / or control information by communicating with a base station (BS) can be a UE. The term UE can be referred to as a terminal device, mobile station (MS), mobile terminal (MT), user terminal (UT), subscriber station (SS), radio device, personal digital assistant (PDA), wireless modem, handheld device, etc. In this disclosure, a BS refers to a fixed station that communicates with a UE and / or another BS and exchanges data and control information with the UE and another BS. The term BS can be referred to as an advanced base station (ABS), node B (NB), evolved node B (eNB), base transceiver system (BTS), access point (AP), processing server (PS), etc. Specifically, a BS for Universal Terrestrial Radio Access (UTRAN) is referred to as an NB, a BS for Evolved UTRAN (E-UTRAN) is referred to as an eNB, and a BS for New Radio Access Technology networks is referred to as a gNB. In the following, for ease of description, regardless of the type or version of the communication technology, NB, eNB, or gNB will be referred to as BS.

[0054] In this disclosure, a node refers to a fixed point capable of sending / receiving radio signals to / from a UE via communication with the UE. Various types of BSs can be used as nodes, regardless of their name. For example, BS, NB, eNB, picocell eNB (PeNB), home eNB (HeNB), repeater, transponder, etc., can be nodes. Alternatively, a node may not be a BS. For example, a Radio Remote Header (RRH) or Radio Remote Unit (RRU) can be a node. Typically, RRHs and RRUs have a lower power level than the BS. Since RRHs or RRUs (hereinafter, RRH / RRU) are typically connected to the BS via dedicated lines such as fiber optic cables, cooperative communication between the RRH / RRU and the BS can be performed smoothly compared to cooperative communication between the BS connected via a radio link. Each node is equipped with at least one antenna. An antenna can refer to a physical antenna port or a virtual antenna or antenna array. A node can also be referred to as a point.

[0055] In this disclosure, a cell refers to a specific geographical area where one or more nodes provide communication services. Therefore, in this disclosure, communication with a specific cell can mean communication with a BS or node providing communication services to that specific cell. The DL / UL signal of a specific cell refers to the DL / UL signal from / to the BS or node providing communication services to that specific cell. A cell providing UL / DL communication services to a UE is specifically referred to as a serving cell. Furthermore, the channel state / quality of a specific cell refers to the channel state / quality of the channel or communication link established between the BS or node providing communication services to the specific cell and the UE. In 3GPP-based communication systems, the UE can use the CRS transmitted on the Cell Specific Reference Signal (CRS) resource and / or the CSI-RS transmitted on the Channel State Information Reference Signal (CSI-RS) resource (assigned to the specific node by the antenna port of the specific node) to measure the DL channel state from the specific node.

[0056] 3GPP-based communication systems use the concept of cells to manage radio resources and distinguish between cells related to radio resources and cells in geographical areas.

[0057] A "cell" of a geographic area can be understood as the coverage area within which a node can use a carrier to provide service, and a "cell" of radio resources is associated with the bandwidth (BW) of the frequency range configured by the carrier. Since DL coverage (the range within which a node can transmit a valid signal) and UL coverage (the range within which a node can receive a valid signal from a UE) depend on the carrier carrying the signal, a node's coverage area can also be associated with the coverage area of ​​the "cell" of the radio resources used by that node. Therefore, the term "cell" can be used to sometimes indicate the service coverage area of ​​a node, at other times to indicate a radio resource, or at other times to indicate the range within which a signal using a radio resource can reach with available effective strength.

[0058] In 3GPP communication standards, the concept of a cell is used to manage radio resources. A “cell” associated with radio resources is defined by a combination of DL resources and UL resources (i.e., a combination of DL component carriers (CCs) and UL CCs). A cell can be configured with only DL resources, or with a combination of DL and UL resources. If carrier aggregation is supported, the link between the carrier frequencies of the DL resources (or DL ​​CCs) and the UL resources (or UL CCs) can be indicated by system information. For example, a combination of DL and UL resources can be indicated by a System Information Block Type 2 (SIB2) link. In this case, the carrier frequencies can be equal to or different from the center frequencies of the individual cells or CCs. When carrier aggregation (CA) is configured, the UE has only one Radio Resource Control (RRC) connection with the network. During RRC connection establishment / re-establishment / handover, a serving cell provides Non-Access Plane (NAS) mobility information. During RRC connection re-establishment / handover, a serving cell provides security input. This cell is called the primary cell (Pcell). A Pcell refers to the cell operating on the primary frequency on which the UE performs the initial connection establishment procedure or initiates the connection re-establishment procedure. Depending on the UE's capabilities, a secondary cell (Scell) can be configured to form a set of serving cells together with a Pcell. An Scell ​​can be configured after RRC connection establishment and is used to provide additional radio resources beyond those of a specific cell (SpCell). The carrier corresponding to the Pcell on the DL is called the Downlink Primary CC (DL PCC), and the carrier corresponding to the Pcell on the UL is called the Uplink Primary CC (UL PCC). The carrier corresponding to the Scell ​​on the DL is called the Downlink Secondary CC (DLSCC), and the carrier corresponding to the Scell ​​on the UL is called the Uplink Secondary CC (UL SCC).

[0059] For dual connectivity (DC) operation, the term SpCell refers to the Pcell of the primary cell group (MCG) or the Pcell of the secondary cell group (SCG). The SpCell supports PUCCH transmission and contention-based random access and is always enabled. The MCG is a set of serving cells associated with the primary node (e.g., BS) and includes the SpCell (Pcell) and optionally one or more Scells. For a UE configured with DC, the SCG is a subset of serving cells associated with the secondary node and includes the PSCell and zero or more Scells. The PSCell is the primary Scell ​​of the SCG. For a UE in the RRC_CONNECTED state without a CA or DC configured, only one serving cell exists, consisting only of the Pcell. For a UE in the RRC_CONNECTED state with a CA or DC configured, the term serving cell refers to the set of cells including the SpCell and all Scells. In DC, two Media Access Control (MAC) entities are configured for the UE: one MAC entity for the MCG and one MAC entity for the SCG.

[0060] A UE configured with a CA but not a DC can be configured with a Pcell PUCCH group (including Pcells and 0 or more Scells) and an Scell ​​PUCCH group (including only Scells). For an Scell, an Scell ​​(hereinafter, PUCCH cell) can be configured to transmit PUCCHs associated with the corresponding cell. An Scell ​​indicated as a PUCCH Scell ​​belongs to the Scell ​​PUCCH group and performs PUCCH transmissions of the relevant UCI on the PUCCH Scell. An Scell ​​not indicated as a PUCCH Scell ​​or whose cell indicated for PUCCH transmission is a Pcell belongs to the Pcell PUCCH group and performs PUCCH transmissions of the relevant UCI on the Pcell.

[0061] In a wireless communication system, the UE receives information from the BS on the DL and transmits information to the BS on the UL. The information transmitted and / or received by the BS and UE includes data and various control information, and various physical channels exist depending on the type / purpose of the information transmitted and / or received by the UE and BS.

[0062] 3GPP-based communication standards define DL physical channels corresponding to resource elements carrying information originating from higher layers, and DL physical signals corresponding to resource elements used by the physical layer but not carrying information originating from higher layers. For example, the Physical Downlink Shared Channel (PDSCH), Physical Broadcast Channel (PBCH), Physical Multicast Channel (PMCH), Physical Control Format Indicator Channel (PCFICH), and Physical Downlink Control Channel (PDCCH) are defined as DL physical channels, and reference signals (RS) and synchronization signals (SS) are defined as DL physical signals. RS (also called pilot) represents a signal with a predefined special waveform known to both the BS and the UE. For example, demodulation reference signal (DMRS) and channel state information RS (CSI-RS) are defined as DL RS. 3GPP-based communication standards also define UL physical channels corresponding to resource elements carrying information originating from higher layers, and UL physical signals corresponding to resource elements used by the physical layer but not carrying information originating from higher layers. For example, the Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), and Physical Random Access Channel (PRACH) are defined as UL physical channels, and the DMRS for UL control / data signals and the SRS for UL channel measurements are defined, etc.

[0063] In this disclosure, PDCCH refers to a set of time-frequency resources (e.g., REs) that serve as a set of resource elements (REs) carrying downlink control information (DCI), and PDSCH refers to a set of time-frequency resources that serve as a set of REs carrying DL data. PUCCH, PUSCH, and PRACH refer to sets of time-frequency resources that serve as a set of time-frequency REs carrying uplink control information (UCI), UL data, and random access signals, respectively. In the following description, "UE transmits / receives PUCCH / PUSCH / PRACH" means that the UE transmits / receives UCI / UL data / random access signals on or through PUCCH / PUSCH / PRACH. Furthermore, "BS transmits / receives PBCH / PDCCH / PDSCH" means that the BS transmits broadcast information / DCI / DL data on or through PBCH / PDCCH / PDSCH.

[0064] In this specification, radio resources (e.g., time-frequency resources) scheduled or configured by the BS for the UE to transmit or receive PUCCH / PUSCH / PDSCH may be referred to as PUCCH / PUSCH / PDSCH resources.

[0065] Because communication devices receive SS / PBCH resource blocks (SSB), DMRS, CSI-RS, PBCH, PDCCH, PDSCH, PUSCH, and / or PUCCH in the form of radio signals on a cell, the communication device may not select and receive radio signals that only include specific physical channels or specific physical signals via a radio frequency (RF) receiver, or it may not select and receive radio signals without specific physical channels or specific physical signals via an RF receiver. In practice, the communication device receives radio signals on the cell via an RF receiver, converts the radio signals, which are RF band signals, into baseband signals, and then uses one or more processors to decode the physical signals and / or physical channels in the baseband signals. Therefore, in some implementations of this disclosure, not receiving physical signals and / or physical channels may mean that the communication device does not attempt to recover physical signals and / or physical channels from the radio signals, for example, it does not attempt to decode physical signals and / or physical channels, rather than that the communication device does not actually receive radio signals that include the corresponding physical signals and / or physical channels.

[0066] With an increasing number of communication devices requiring greater communication capacity, there is a need for eMBB communication relative to traditional radio access technologies (RATs). Furthermore, massive MTC (Medium-Terminal Communication) to provide various services anytime, anywhere by connecting multiple devices and objects to each other is a major issue to be considered in next-generation communications. In addition, communication system designs considering reliability and latency-sensitive services / UEs are also being discussed. The introduction of next-generation RATs is being discussed, taking into account eMBB communication, massive MTC, ultra-reliable low-latency communication (URLLC), etc. Currently, research on next-generation mobile communication systems after EPC is underway within 3GPP. In this disclosure, for convenience, the corresponding technology is referred to as New RAT (NR) or Fifth Generation (5G) RAT, and systems using or supporting NR are referred to as NR systems.

[0067] Figure 1 An example of a communication system 1 to which the implementation of this disclosure is applied is shown. (Refer to...) Figure 1The communication system 1 applied to this disclosure includes wireless devices, a BS, and a network. Here, a wireless device refers to a device that performs communication using RAT (e.g., 5G NR or LTE (e.g., E-UTRA)) and may be referred to as a communication / radio / 5G device. Wireless devices may include (but are not limited to) robots 100a, vehicles 100b-1 and 100b-2, extended reality (XR) devices 100c, handheld devices 100d, home appliances 100e, Internet of Things (IoT) devices 100f, and artificial intelligence (AI) devices / servers 400. For example, vehicles may include vehicles with wireless communication capabilities, autonomous vehicles, and vehicles capable of performing vehicle-to-vehicle communication. Here, vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices may include augmented reality (AR) / virtual reality (VR) / mixed reality (MR) devices and may be implemented in the form of head-mounted displays (HMDs), head-up displays (HUDs) installed in vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signage, vehicles, robots, etc. Handheld devices may include smartphones, smart tablets, wearable devices (e.g., smartwatches or smart glasses), and computers (e.g., laptops). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters. For example, the BS and network may also be implemented as wireless devices, and a particular wireless device may operate as a BS / network node relative to another wireless device.

[0068] Wireless devices 100a to 100f can connect to network 300 via BS200. AI technology can be applied to wireless devices 100a to 100f, and wireless devices 100a to 100f can connect to AI server 400 via network 300. Network 300 can be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. Although wireless devices 100a to 100f can communicate with each other via BS200 / network 300, wireless devices 100a to 100f can perform direct communication with each other (e.g., sidelink communication) without going through the BS / network. For example, vehicles 100b-1 and 100b-2 can perform direct communication (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). IoT devices (e.g., sensors) can perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

[0069] Wireless communication / connections 150a and 150b can be established between wireless devices 100a to 100f and BS200, and between wireless devices 100a to 100f. Here, wireless communication / connections such as UL / DL communication 150a and sidelink communication 150b (or device-to-device (D2D) communication) can be established via various RATs (e.g., 5G NR). The wireless devices and the BS / wireless devices can transmit / receive radio signals to / from each other via wireless communication / connections 150a and 150b. For this purpose, at least a portion of various configuration information configuration processes for transmitting / receiving radio signals, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, and resource mapping / demapping), and resource allocation processes can be performed based on various proposals of this disclosure.

[0070] Figure 2 This is a block diagram illustrating an example of a communication device capable of performing the methods according to this disclosure. (Refer to...) Figure 2 The first wireless device / first device 100 and the second wireless device / second device 200 can transmit and / or receive radio signals via various RATs (e.g., LTE and NR). Here, {first wireless device 100 and second wireless device 200} can correspond to Figure 1 {Wireless Device 100x and BS200} and / or {Wireless Device 100x and Wireless Device 100x}.

[0071] The first wireless device 100 may include one or more processors 102 and one or more memories 104, and 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 functions, processes, and / or methods described / presented below. For example, the processors 102 may process information in the memories 104 to generate first information / signals, and then transmit radio signals including the first information / signals via the transceivers 106. The processors 102 may receive radio signals including second information / signals via the transceivers 106, and then store the information obtained by processing the second information / signals in the memories 104. The memories 104 may be connected to the processors 102 and may store various information relating to the operation of the processors 102. For example, the memories 104 may execute some or all of the processes controlled by the processors 102 or store software code including commands for executing the processes and / or methods described / presented below. Here, processor 102 and memory 104 may be part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). Transceiver 106 may be connected to processor 102 and transmit and / or receive radio signals via one or more antennas 108. Each transceiver 106 may include a transmitter and / or a receiver. Transceiver 106 may be used interchangeably with radio frequency (RF) units. In this disclosure, a wireless device may refer to a communication modem / circuit / chip.

[0072] The second wireless device 200 may include one or more processors 202 and one or more memories 204, and 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 functions, processes, and / or methods described / presented below. For example, the processors 202 may process information in the memories 204 to generate a third information / signal, and then transmit a radio signal including the third information / signal via the transceivers 206. The processors 202 may receive a radio signal including a fourth information / signal via the transceivers 206, and then store the information obtained by processing the fourth information / signal in the memories 204. The memories 204 may be connected to the processors 202 and may store various information relating to the operation of the processors 202. For example, the memories 204 may execute some or all of the processes controlled by the processors 202 or store software code including commands for executing the processes and / or methods described / presented below. Here, processor 202 and memory 204 may be part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). Transceiver 206 may be connected to processor 202 and transmit and / or receive radio signals via one or more antennas 208. Each transceiver 206 may include a transmitter and / or a receiver. Transceiver 206 may be used interchangeably with an RF unit. In this disclosure, a wireless device may refer to a communication modem / circuit / chip.

[0073] The wireless communication technologies implemented in the wireless 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 low-power wide-area network (LPWAN) technology and implemented in standards such as LTE Cat NB1 and / or LTE Cat NB2. However, NB-IoT technology is not limited to the above names. Alternatively or additionally, the wireless communication technologies implemented in the wireless devices XXX and YYY of this disclosure may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and is referred to by various names including enhanced machine-type communication (eMTC). For example, LTE-M technology may be implemented in at least one of the following standards: 1) LTE Cat 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-bandwidth limited (non-BL), 5) LTE-MTC, 6) LTE machine-type communication, and / or 7) LTE M, etc., but LTE-M technology is not limited to the above names. Additionally or alternatively, considering low-power communication, the wireless communication technology implemented in the wireless devices XXX and YYY of this disclosure may include at least one of ZigBee, Bluetooth, and LPWAN, but the wireless communication technology is not limited to the above names. For example, ZigBee technology can be used to create personal area networks (PANs) related to low / low-power digital communication based on various standards such as IEEE 802.15.4, and ZigBee technology may be referred to by various names.

[0074] The hardware elements of wireless devices 100 and 200 will be described in more detail below. One or more protocol layers may be implemented by (but are not limited to) 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 the Physical (PHY) layer, Medium Access Control (MAC) layer, Radio Link Control (RLC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Resource Control (RRC) layer, and Service Data Adaptation Protocol (SDAP) layer). One or more processors 102 and 202 may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the functions, processes, proposals, and / or methods disclosed in this disclosure. One or more processors 102 and 202 may generate messages, control information, data, or information according to the functions, processes, proposals, and / or methods disclosed in this disclosure. One or more processors 102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the functions, processes, proposals, and / or methods disclosed in this disclosure, and provide the generated signals to one or more transceivers 106 and 206. One or more processors 102 and 202 may receive signals (e.g., baseband signals) and acquire PDUs, SDUs, messages, control information, data, or information from one or more transceivers 106 and 206 according to the functions, processes, proposals, and / or methods disclosed in this disclosure.

[0075] One or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. As an example, one or more application-specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field-programmable gate arrays (FPGAs) may be included in one or more processors 102 and 202. The functions, processes, proposals, and / or methods disclosed in this disclosure may be implemented using firmware or software, and the firmware or software may be configured to include modules, processes, or functions. Firmware or software configured to perform the functions, processes, proposals, and / or methods disclosed in this disclosure may be included in one or more processors 102 and 202 or stored in one or more memories 104 and 204 to be driven by one or more processors 102 and 202. The functions, processes, proposals, and / or methods disclosed in this disclosure may be implemented using firmware or software in the form of code, commands, and / or sets of commands.

[0076] One or more memories 104 and 204 may be connected to one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, code, commands, and / or instructions. One or more memories 104 and 204 may be configured with read-only memory (ROM), random access memory (RAM), electrically erasable programmable read-only memory (EPROM), flash memory, hard disk drive, registers, cache memory, computer-readable storage media, and / or combinations thereof. One or more memories 104 and 204 may be located internally and / or externally to one or more processors 102 and 202. One or more memories 104 and 204 may be connected to one or more processors 102 and 202 via various technologies such as wired or wireless connections.

[0077] One or more transceivers 106 and 206 may transmit user data, control information, and / or radio signals / channels mentioned in the methods and / or operation flowcharts of this disclosure to one or more other devices. One or more transceivers 106 and 206 may receive user data, control information, and / or radio signals / channels mentioned in the functions, processes, proposals, methods, and / or operation flowcharts disclosed in this disclosure from one or more other devices. For example, one or more transceivers 106 and 206 may be connected to one or more processors 102 and 202 and transmit and receive radio signals. For example, one or more processors 102 and 202 may perform control to enable one or more transceivers 106 and 206 to transmit user data, control information, or radio signals to one or more other devices. One or more processors 102 and 202 may perform control to enable one or more transceivers 106 and 206 to receive user data, control information, or radio signals from one or more other devices. One or more transceivers 106 and 206 may be connected to one or more antennas 108 and 208. One or more transceivers 106 and 206 may be configured to transmit and receive user data, control information, and / or radio signals / channels mentioned in the functions, processes, proposals, methods, and / or operation flowcharts disclosed in this disclosure via one or more antennas 108 and 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 and 206 may convert received radio signals / channels, etc., from RF band signals to baseband signals for processing by one or more processors 102 and 202. One or more transceivers 106 and 206 may convert user data, control information, radio signals / channels, etc., processed using one or more processors 102 and 202 from baseband signals to RF band signals. For this purpose, one or more transceivers 106 and 206 may include (analog) oscillators and / or filters.

[0078] Figure 3 Another example of a wireless device capable of implementing the embodiments of this disclosure is shown. (Refer to...) Figure 3 Wireless devices 100 and 200 can correspond to Figure 2 The wireless devices 100 and 200 are configured with various elements, components, units / parts, and / or modules. For example, each of the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit (memory) 130, and additional components 140. The communication unit may include a communication circuit 112 and a transceiver 114. For example, the communication circuit 112 may include... Figure 2One or more processors 102 and 202 and / or one or more memories 104 and 204. For example, transceiver 114 may include Figure 2 The device comprises one or more transceivers 106 and 206 and / or one or more antennas 108 and 208. Control unit 120 is electrically connected to communication unit 110, memory unit 130, and add-on components 140, and controls the overall operation of the wireless device. For example, control unit 120 may control the electrical / mechanical operation of the wireless device based on programs / code / commands / information stored in memory unit 130. Control unit 120 may transmit information stored in memory unit 130 to an external source (e.g., other communication devices) via communication unit 110 through a wireless / wired interface, or store information received from an external source (e.g., other communication devices) via communication unit 110 in memory unit 130 via a wireless / wired interface.

[0079] The additional component 140 can be configured differently depending on the type of wireless device. For example, the additional component 140 may include at least one of a power supply unit / battery, an input / output (I / O) unit, a drive unit, and a computing unit. The wireless device may be configured according to (but is not limited to) a robot. Figure 1 100a), vehicles ( Figure 1 100b-1 and 100b-2), XR device ( Figure 1 100c), handheld device ( Figure 1 100d), home appliances ( Figure 1 100e), IoT devices ( Figure 1 100f), digital broadcast UE, holographic devices, public safety devices, MTC devices, medical devices, fintech devices (or financial devices), security devices, climate / environment devices, AI servers / devices ( Figure 1 400), BS ( Figure 1 This can be achieved through 200 network nodes, etc. Wireless devices can be used in mobile or fixed locations depending on usage / service.

[0080] exist Figure 3In wireless devices 100 and 200, all elements, components, units / parts, and / or modules may be interconnected via wired interfaces, or at least a portion thereof may be wirelessly connected via communication unit 110. For example, in each of wireless devices 100 and 200, control unit 120 and communication unit 110 may be wired connected, and control unit 120 and first units (e.g., 130 and 140) may be wirelessly connected via communication unit 110. The various elements, components, units / parts, and / or modules within wireless devices 100 and 200 may also include one or more elements. For example, control unit 120 may be configured as a collection of one or more processors. As an example, control unit 120 may be configured as a collection of communication control processors, application processors, electronic control units (ECUs), graphics processing units, and memory control processors. As another example, memory 130 may be configured as random access memory (RAM), dynamic RAM (DRAM), read-only memory (ROM), flash memory, volatile memory, non-volatile memory, and / or combinations thereof.

[0081] In this disclosure, at least one memory (e.g., 104 or 204) may store instructions or programs, and when executed, these instructions or programs may cause at least one processor operatively connected to the at least one memory to perform operations according to some embodiments or implementations of this disclosure.

[0082] In this disclosure, a computer-readable (non-transitory) storage medium may store at least one instruction or program, and the at least one instruction or program, when executed by at least one processor, may cause the at least one processor to perform operations according to some embodiments or implementations of this disclosure.

[0083] In this disclosure, a processing apparatus or device may include at least one processor and at least one computer memory operatively connected to said at least one processor. The at least one computer memory may store instructions or programs, and when executed, these instructions or programs may cause the at least one processor operatively connected to the at least one memory to perform operations according to some embodiments or implementations of this disclosure.

[0084] In this disclosure, a computer program may include program code stored on at least one computer-readable (non-volatile) storage medium, and when executed, is configured to perform operations according to some implementation of this disclosure or to cause at least one processor to perform operations according to some implementation of this disclosure. The computer program may be provided in the form of a computer program product. A computer program product may include at least one computer-readable (non-volatile) storage medium.

[0085] The communication apparatus of this disclosure includes: at least one processor; and at least one computer memory operatively connected to the at least one processor and configured to store instructions that, when executed, cause the at least one processor to perform operations according to examples of this disclosure described later.

[0086] Figure 4 An example of a frame structure used in a 3GPP-based wireless communication system is shown.

[0087] Figure 4 The frame structure described is merely exemplary, and the number of subframes, time slots, and symbols within a frame can vary. In an NR system, different sets of OFDM parameters (e.g., subcarrier spacing (SCS)) can be configured for multiple cells aggregated for a UE. Therefore, the (absolute time) duration of time resources comprising the same number of symbols (e.g., subframes, time slots, or transmission time intervals (TTI)) can be configured differently for the aggregated cells. Here, symbols may include OFDM symbols (or cyclic prefix-OFDM (CP-OFDM) symbols) and SC-FDMA symbols (or discrete Fourier transform-extended-OFDM (DFT-s-OFDM) symbols). In this disclosure, symbols, OFDM-based symbols, OFDM symbols, CP-OFDM symbols, and DFT-s-OFDM symbols are used interchangeably.

[0088] Reference Figure 4 In NR systems, UL and DL transmissions are organized into frames. Each frame has a T f =(△f max *N f / 100)*T c =10ms duration and is divided into two half-frames, each 5ms. The basic time unit of NR is T. c =1 / (△f) max *N f ), where △f max =480*10 3 Hz and N f = 4096. For reference, the basic time unit for LTE is T. s =1 / (△f) ref *N f,ref ), where △f ref =15*10 3 Hz and N f,ref =2048. T c and T f Having a constant κ = T c / T f =64. Each half-frame consists of 5 subframes, and the duration T of a single subframe is... sfThe duration is 1 ms. Subframes are further divided into time slots, and the number of time slots within a subframe depends on the subcarrier spacing. Each time slot comprises either 14 or 12 OFDM symbols based on the cyclic prefix. In normal CP, each time slot comprises 14 OFDM symbols, while in extended CP, each time slot comprises 12 OFDM symbols. The parameter set depends on the exponentially scalable subcarrier spacing Δf = 2. u *15kHz. The following shows the number of OFDM symbols per time slot (N). slot symb ), the number of time slots per frame (N) frame,u slot ) and the number of time slots per subframe (N) subframe,u slot ).

[0089] [Table 1]

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

[0091] The following table shows the subcarrier spacing Δf = 2 u *15kHz, the number of OFDM symbols per time slot, the number of time slots per frame, and the number of time slots per subframe.

[0092] [Table 2]

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

[0094] For the subcarrier spacing configuration u, the time slots can be indexed in ascending order within the subframe as follows: n u s ∈{0,...,n subframe ,u slot -1}, and indexed in ascending order within the frame as follows: n u s,f ∈{0,...,n frame,u slot -1}.

[0095] Figure 5 The resource grid for the time slots is shown. A time slot comprises multiple (e.g., 14 or 12) symbols in the time domain. For each parameter set (e.g., subcarrier spacing) and carrier, the common resource block (CRB) N is indicated by higher-layer signaling (e.g., RRC signaling). start,u grid N was defined first. size,u grid,x *N RB sc Subcarriers and N subframe,u symb A resource grid of OFDM symbols, where N size,u grid,xN represents the number of resource blocks (RBs) in the resource grid, with the index x representing DL for downlinks and UL for uplinks. RB sc N is the number of subcarriers per RB. In 3GPP-based wireless communication systems, N... RB sc Typically, it is 12. For a given antenna port p, subcarrier spacing configuration u, and transmission link (DL or UL), there exists a resource grid. The carrier bandwidth N of the subcarrier spacing configuration u is given to the UE via higher-layer parameters (e.g., RRC parameters). size,u grid Each element in the resource grid used for antenna port p and subcarrier spacing configuration u is called a resource element (RE), and a complex symbol can be mapped to each RE. Each RE in the resource grid is uniquely identified by an index k in the frequency domain and an index l representing the symbol position relative to a reference point in the time domain. In NR systems, RBs are defined by 12 consecutive subcarriers in the frequency domain. In NR systems, RBs are classified into CRBs and physical resource blocks (PRBs). For subcarrier spacing configuration u, CRBs are numbered from 0 upwards in the frequency domain. The center of subcarrier 0 of CRB 0 in subcarrier spacing configuration u is equal to "point A", which serves as the common reference point for the RB grid. The PRBs of subcarrier spacing configuration u are defined within the bandwidth portion (BWP) and numbered from 0 to N. size,u BWP,i -1 is the number, where i is the number of BWPs. PRB n in BWPi PRB With CRB n u CRB The relationship between n u PRB =n u CRB +N size,u BWP,i Given, where N size BWP,i The BWP is the CRB that starts relative to CRB 0. A BWP comprises multiple consecutive RBs in the frequency domain. For example, a BWP can be a BWP i on a given carrier with a given set of parameters u. i A subset of adjacent CRBs is defined. A carrier may include up to N (e.g., 5) BWPs. A UE may be configured to have one or more BWPs on a given component carrier. Data communication is performed via enabled BWPs, and a predetermined number of BWPs (e.g., one BWP) may be active on the component carrier only among the BWPs configured for the UE.

[0096] For each serving cell in the set of DL BWPs or UL BWPs, the network can configure at least an initial DL BWP and one (if the serving cell has an uplink) or two (if supplementary uplinks are used) initial UL BWPs. The network can configure additional UL and DL BWPs. For each DL BWP or UL BWP, the following parameters can be provided to the UE for the serving cell: i) SCS; ii) CP; iii) parameters generated by N. start BWP＝ Under the assumption of 275, the indicated offset RB set and length L RB The CRB N is provided by the RRC parameter locationAndBandwidth as the Resource Indicator Value (RIV). start BWP =O carrier +RB start The number N of adjacent RBs size BWP =L RB And the value O provided by the RRC parameter offsetToCarrier for SCS. carrier ; an index in the set of DL BWP or UL BWP; a set of BWP common parameters; and a set of BWP specific parameters.

[0097] Virtual Resource Blocks (VRBs) can be defined within a BWP and range from 0 to N. size,u BWP,i -1 index, where i represents the BWP number. VRBs can be mapped to PRBs based on non-interleaved mappings. In some implementations, for non-interleaved VRB-to-PRB mappings, VRB n can be mapped to PRB n.

[0098] A UE configured with carrier aggregation can be configured to use one or more cells. If the UE is configured with multiple serving cells, the UE can be configured with one or more cell groups. The UE can also be configured with multiple cell groups associated with different BSs. Alternatively, the UE can be configured with multiple cell groups associated with a single BS. Each cell group of the UE includes one or more serving cells and includes a single PUCCH cell configured with PUCCH resources. The PUCCH cell can be a Pcell or an Scell ​​of the corresponding cell group configured as a PUCCH cell. Each serving cell of the UE belongs to one of the UE's cell groups and does not belong to multiple cells.

[0099] Figure 6The time slot structure used in a 3GPP-based system is shown. In all 3GPP-based systems (e.g., in NR systems), individual time slots may have a self-contained structure comprising i) a DL control channel, ii) DL or UL data, and / or iii) a UL control channel. For example, the first N symbols in a time slot may be used to transmit the DL control channel (hereinafter, the DL control area), and the last M symbols in the time slot may be used to transmit the UL control channel (hereinafter, the UL control area), where N and M are integers other than negative numbers. The resource area (hereinafter, the data area) between the DL control area and the UL control area may be used to transmit either DL data or UL data. Symbols in a single time slot may be divided into consecutive groups of symbols that can be used as DL symbols, UL symbols, or flexible symbols. The information indicating how the individual symbols in a time slot are used will be referred to as the time slot format. For example, the time slot format may define which symbols in the time slot are used for UL and which symbols in the time slot are used for DL.

[0100] When the BS is intended to operate the serving cell in Time Division Duplex (TDD) mode, the BS can configure UL and DL allocation patterns for the serving cell via higher-layer (e.g., RRC) signaling. For example, the following parameters can be used to configure TDD DL-UL patterns:

[0101] -dl-UL-TransmissionPeriodicity provides the periodicity of DL-UL patterns;

[0102] -nrofDownlinkSlots provides the number of consecutive full DL slots at the beginning of each DL-UL pattern, where a full DL slot is a slot that only has a DL symbol;

[0103] -nrofDownlinkSymbols provides the number of consecutive DL symbols at the beginning of the slot immediately following the last full DL slot;

[0104] -nrofUplinkSlots, which provides the number of consecutive full UL slots at the end of each DL-UL pattern, where a full UL slot is a slot with only the UL symbol; and

[0105] -nrofUplinkSymbols provides the number of consecutive UL symbols at the end of the slot immediately preceding the first full UL slot.

[0106] The remaining symbols in the DL-UL pattern that are not configured as DL symbols or UL symbols are flexible symbols.

[0107] If a TDD DL-UL pattern configuration, i.e., a TDD UL-DL configuration (e.g., tdd-UL-DL-ConfigurationCommon or tdd-UL-DLConfigurationDedicated), is provided to the UE via higher-layer signaling, the UE sets the time slot format for each time slot across multiple time slots based on this configuration.

[0108] For symbols, although various combinations of DL symbols, UL symbols, and flexible symbols are possible, a predetermined number of combinations can be predefined into time slot formats, and these predefined time slot formats can be identified by time slot format indices. A selection of predefined time slot formats are shown below. In the table below, D represents a DL symbol, U represents a UL symbol, and F represents a flexible symbol.

[0109] [Table 3]

[0110]

[0111] To indicate which time slot format to use in a specific time slot within a predefined time slot format, the BS can configure a set of time slot format combinations applicable to the corresponding serving cell for each cell in the serving cell set via higher-layer (e.g., RRC) signaling, and enable the UE to monitor the group common PDCCH of the Time Slot Format Indicator (SFI) via higher-layer (e.g., RRC) signaling. In the following text, the DCI carried by the group common PDCCH of the SFI will be referred to as the SFIDCI. DCI format 2_0 is used as the SFIDCI. For example, for each serving cell in the serving cell set, the BS can provide the UE with the (starting) position of the time slot format combination ID (i.e., SFI index) of the corresponding serving cell in the SFIDCI, the set of time slot format combinations applicable to the serving cell, and the reference subcarrier spacing configuration of each time slot format in the time slot format combination indicated by the SFI index value in the SFIDCI. One or more time slot formats are configured for each time slot format combination in the set of time slot format combinations, and a time slot format combination ID (i.e., SFI index) is assigned to the time slot format combination. For example, when the BS aims to configure a combination of time slot formats with N time slot formats, it can indicate the N time slot format indices from a predefined time slot format index (e.g., see Table 3) for the time slot format combination. To configure the UE to monitor the group common PDCCH for SFI, the BS informs the UE of the SFI-RNTI corresponding to the Radio Network Temporary Identifier (RNTI) used for SFI and the total length of the DCI payload scrambled with the SFI-RNTI. When the PDCCH is detected based on the SFI-RNTI, the UE can determine the time slot format of the corresponding serving cell from the SFI index of the serving cell in the DCI payload of the PDCCH.

[0112] Symbols designated as flexible symbols by TDD DL-UL pattern configuration may be designated as UL symbols, DL symbols, or flexible symbols by SFIDCI. Symbols designated as DL / UL symbols by TDD DL-UL pattern configuration are not overridden by SFIDCI as UL / DL symbols or flexible symbols.

[0113] If a TDD DL-UL pattern is not configured, the UE determines whether each time slot is used for UL or DL ​​and determines the symbol allocation in each time slot based on the SFIDCI and / or DCI (e.g., DCI format 1_0, DCI format 1_1, DCI format 1_2, DCI format 0_0, DCI format 0_1, DCI format 0_2, and DCI format 2_3) used to schedule or trigger DL or UL signal transmission.

[0114] The NR band is defined as two types of frequency ranges, namely FR1 and FR2. FR2 is also known as millimeter wave (mmW). The following shows the frequency range that NR can operate in.

[0115] [Table 4]

[0116] Frequency range specification Corresponding frequency range Subcarrier spacing FR1 410MHz-7125MHz 15, 30, 60kHz FR2 24250MHz-52600MHz 60, 120, 240kHz

[0117] The physical channels available in 3GPP-based wireless communication systems will be described in detail below.

[0118] The PDCCH carries the DCI. For example, the PDCCH (i.e., the DCI) carries information about the transmission format and resource allocation of the downlink shared channel (DL-SCH), information about the resource allocation of the uplink shared channel (UL-SCH), paging information about the paging channel (PCH), system information about the DL-SCH, resource allocation information about control messages (e.g., Random Access Response (RAR) sent on the PDSCH) of layers higher than the physical layer in the UE / BS protocol stack (hereinafter, higher layers), transmission power control commands, and information about enabling / disabling configuration scheduling (CS), etc. The DCI that includes resource allocation information about the DL-SCH is called the PDSCH scheduling DCI, and the DCI that includes resource allocation information about the UL-SCH is called the PUSCH scheduling DCI. The DCI includes Cyclic Redundancy Check (CRC). The CRC is masked / scrambled with various identifiers (e.g., Radio Network Temporary Identifier (RNTI)) according to the owner and purpose of the PDCCH. For example, if the PDCCH is used for a specific UE, the CRS is masked with the UE identifier (e.g., Cell-RNTI (C-RNTI)). If the PDCCH is used for paging messages, the CRC is masked with the Paging RNTI (P-RNTI). If the PDCCH is used for system information (e.g., System Information Block (SIB)), the CRC is masked with the System Information RNTI (SI-RNTI). If the PDCCH is used for random access responses, the CRC is masked with the Random Access-RNTI (RA-RNTI).

[0119] When a PDCCH on one serving cell schedules a PDSCH or PUSCH on another serving cell, it is called cross-carrier scheduling. Cross-carrier scheduling with a Carrier Indicator Field (CIF) allows the PDCCH on one serving cell to schedule resources on another serving cell. When a PDSCH on one serving cell schedules a PDSCH or PUSCH on another serving cell, it is called self-carrier scheduling. When cross-carrier scheduling is used in a cell, the BS can provide the UE with information about the scheduling cell. For example, the BS can inform the UE whether the serving cell is scheduled by a PDCCH on another (scheduling) cell or by the serving cell itself. If the serving cell is scheduled by another (scheduling) cell, the BS can inform the UE which cell signals the DL assignment and UL authorization of the serving cell. In this disclosure, the cell carrying the PDCCH is called the scheduling cell, and the cell whose PUSCH or PDSCH transmission is scheduled by the DCI included in the PDCCH (i.e., the cell carrying the PUSCH or PDSCH scheduled by the PDCCH) is called the scheduled cell.

[0120] The PDSCH is the physical layer UL channel for UL data transmission. The PDSCH carries DL data (e.g., DL-SCH transport blocks) and is modulated using techniques such as Quadrature Phase Shift Keying (QPSK), 16-Quadrature Amplitude Modulation (QAM), 64QAM, 256QAM, etc. Codewords are generated by encoding the transport block (TB). A PDSCH can carry up to two codewords. Scrambling and modulation mapping can be performed for each codeword, and modulation symbols generated from each codeword can be mapped to one or more layers. Each layer, along with the DMRS, is mapped to radio resources and generated as OFDM symbol signals. The OFDM symbol signals are then transmitted through the corresponding antenna ports.

[0121] PUCCH refers to the physical layer UL channel used for uplink control information (UCI) transmission. PUCCH carries UCI. The types of UCI transmitted on PUCCH include Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) information, Scheduling Request (SR) information, and Channel State Information (CSI). UCI bits include HARQ-ACK information bits (if any), SR information bits (if any), Link Recovery Request (LRR) information bits (if any), and CSI bits (if any). In this disclosure, the HARQ-ACK information bits correspond to the HARQ-ACK codebook. Specifically, the bit sequence of the HARQ-ACK information bits arranged according to a predetermined rule is called the HARQ-ACK codebook.

[0122] - Scheduling Request (SR): Information used to request UL-SCH resources.

[0123] - Hybrid Automatic Repeat Request (HARQ) - Acknowledgment (ACK): A response to a DL data packet (e.g., a codeword) on the PDSCH. HARQ-ACK indicates whether the communication device has successfully received the DL data packet. A 1-bit HARQ-ACK can be sent in response to a single codeword. A 2-bit HARQ-ACK can be sent in response to two codewords. HARQ-ACK responses include affirmative ACK (simply ACK), negative ACK (NACK), discontinuous transmission (DTX), or NACK / DTX. Here, the term HARQ-ACK can be used interchangeably with HARQ ACK / NACK, ACK / NACK, or A / N.

[0124] - Channel State Information (CSI): Feedback information about the DL channel. CSI may include Channel Quality Information (CQI), Rank Indicator (RI), Precoding Matrix Indicator (PMI), CSI-RS Resource Indicator (CRI), SS / PBCH Resource Block Indicator (SSBRI), and Layer Indicator (L1). Based on the UCI types included in the CSI, CSI can be classified into CSI Part 1 and CSI Part 2. For example, the CRI, RI, and / or CQI of the first codeword may be included in CSI Part 1, while the LI, PMI, and / or CQI of the second codeword may be included in CSI Part 2.

[0125] Link Recovery Request (LRR)

[0126] In this disclosure, for convenience, the PUCCH resources for which the BS configures / instructs the UE to transmit HARQ-ACK, SR, and CSI are referred to as HARQ-ACK PUCCH resources, SR PUCCH resources, and CSIPUCCH resources, respectively.

[0127] The PUCCH format can be defined as follows, depending on the UCI payload size and / or transmission length (e.g., the number of symbols included in the PUCCH resource). See Table 5 for further information on the PUCCH format.

[0128] (0) PUCCH format 0 (PF0 or F0)

[0129] - Supported UCI payload size: up to K bits (e.g., K=2)

[0130] - The number of OFDM symbols that make up a single PUCCH: 1 to X symbols (e.g., X = 2)

[0131] - Transmission Structure: PUCCH format 0 includes only UCI signals and no DMRS. The UE transmits the UCI status by selecting and transmitting one of several sequences. For example, the UE transmits a specific UCI to the BS by transmitting one of several sequences via PUCCH (PUCCH format 0). The UE only transmits PUCCH (PUCCH format 0) in the PUCCH resources configured for the corresponding SR when transmitting an affirmative SR.

[0132] The configuration for PUCCH format 0 includes the following parameters for the corresponding PUCCH resource: the index of the initial cyclic shift, the number of symbols used for PUCCH transmission, and / or the first symbol used for PUCCH transmission.

[0133] (1) PUCCH format 1 (PF1 or F1)

[0134] - Supported UCI payload size: up to K bits (e.g., K=2)

[0135] - The number of OFDM symbols that make up a single PUCCH: Y to Z symbols (e.g., Y=4 and Z=14)

[0136] - Transmission Structure: DMRS and UCI are configured / mapped to different OFDM symbols according to TDM. In other words, DMRS is transmitted in symbols where no modulation symbols are transmitted, and UCI is represented as a product between a specific sequence (e.g., orthogonal overlay code (OCC)) and a modulation (e.g., QPSK) symbol. Code division multiplexing (CDM) is supported among multiple PUCCH resources (compliant with PUCCH format 1) (within the same RB) by applying cyclic shift (CS) / OCC to both UCI and DMRS. PUCCH format 1 carries up to 2 bits of UCI and extends the modulation symbols in the time domain via OCC (configured differently depending on whether frequency hopping is performed).

[0137] The configuration for PUCCH format 1 includes the following parameters for the corresponding PUCCH resource: the index of the initial cyclic shift, the number of symbols used for PUCCH transmission, and the index of the first symbol and / or OCC used for PUCCH transmission.

[0138] (2) PUCCH format 2 (PF2 or F2)

[0139] - Supported UCI payload size: exceeding K bits (e.g., K=2)

[0140] - The number of OFDM symbols that make up a single PUCCH: 1 to X symbols (e.g., X = 2)

[0141] - Transmission Structure: Frequency Division Multiplexing (FDM) is used within the same symbol to configure / map DMRS and UCI. The UE transmits UCI by applying IFFT to the encoded UCI bits without DFT. PUCCH Format 2 carries UCI bits larger than K bits, and the modulated symbols undergo FDM with DMRS for transmission. For example, the DMRS is located in symbol indices #1, #4, #7, and #10 within a given RB, with a density of 1 / 3. A pseudo-noise (PN) sequence is used for the DMRS sequence. Frequency hopping can be enabled for 2-symbol PUCCH Format 2.

[0142] The configuration of PUCCH Format 2 includes the following parameters for the corresponding PUCCH resource: the number of PRBs, the number of symbols used for PUCCH transmission, and / or the first symbol used for PUCCH transmission.

[0143] (3) PUCCH format 3 (PF3 or F3)

[0144] - Supported UCI payload size: exceeding K bits (e.g., K=2)

[0145] - The number of OFDM symbols that make up a single PUCCH: Y to Z symbols (e.g., Y=4 and Z=14)

[0146] - Transmission Structure: DMRS and UCI are configured / mapped to different OFDM symbols according to TDM. The UE transmits UCI by applying DFT to the encoded UCI bits. PUCCH Format 3 does not support UE multiplexing for the same time-frequency resource (e.g., the same PRB).

[0147] The configuration of PUCCH format 3 includes the following parameters for the corresponding PUCCH resource: the number of PRBs, the number of symbols used for PUCCH transmission, and / or the first symbol used for PUCCH transmission.

[0148] (4) PUCCH format 4 (PF4 or F4)

[0149] - Supported UCI payload size: exceeding K bits (e.g., K=2)

[0150] - The number of OFDM symbols that make up a single PUCCH: Y to Z symbols (e.g., Y=4 and Z=14)

[0151] - Transmission Structure: DMRS and UCI are configured / mapped to different OFDM symbols using TDM. By applying OCC to the front end of the DFT and applying CS (or interleaved FDM (IFDM) mapping) to the DMRS, PUCCH Format 4 can multiplex up to 4 UEs in the same PRB. In other words, the modulation symbols of UCI undergo TDM with the DMRS for transmission.

[0152] The configuration of PUCCH format 4 includes the following parameters for the corresponding PUCCH resource: the number of symbols used for PUCCH transmission, the length of the OCC, the index of the OCC, and the first symbol used for PUCCH transmission.

[0153] The following table shows the PUCCH format. Based on the PUCCH transmission length, the PUCCH format can be divided into short PUCCH format (formats 0 and 2) and long PUCCH format (formats 1, 3 and 4).

[0154] [Table 5]

[0155]

[0156] PUCCH resources can be determined according to the UCI type (e.g., A / N, SR, or CSI). The PUCCH resources for UCI transmission can be determined based on the UCI (payload) size. For example, the BS can configure multiple PUCCH resource sets for the UE, and the UE can select a specific PUCCH resource set corresponding to a specific range according to the range of the UCI (payload) size (e.g., the number of UCI bits). For example, the UE can select one of the following PUCCH resource sets according to the number of UCI bits NUCI.

[0157] - PUCCH resource set #0, if the number of UCI bits = <2

[0158] - PUCCH resource set #1, if 2 < the number of UCI bits = <N1 ...

[0160] - PUCCH resource set #(K - 1), if N K-2 < the number of UCI bits = <N K-1

[0161] Here, K represents the number of PUCCH resource sets (K > 1), and N i represents the maximum number of UCI bits supported by PUCCH resource set #i. For example, PUCCH resource set #1 can include resources of PUCCH formats 0 to 1, and other PUCCH resource sets can include resources of PUCCH formats 2 to 4 (see Table 5).

[0162] The configuration of each PUCCH resource includes the PUCCH resource index, the starting PRB index, and the configuration of one of PUCCH formats 0 to PUCCH format 4. The BS configures the code rate for multiplexing HARQ-ACK, SR, and CSI reports in PUCCH transmission using PUCCH format 2, PUCCH format 3, or PUCCH format 4 for the UE through the high-layer parameter maxCodeRate. The high-layer parameter maxCodeRate is used to determine how to feedback UCI on the PUCCH resources of PUCCH format 2, 3, or 4.

[0163] If the UCI type is SR and CSI, the PUCCH resources to be used for UCI transmission in the PUCCH resource set can be configured for the UE through high-layer signaling (e.g., RRC signaling). If the UCI type is HARQ-ACK for semi-persistent scheduling (SPS) PDSCH, the PUCCH resources to be used for UCI transmission in the PUCCH resource set can be configured for the UE through high-layer signaling (e.g., RRC signaling). On the other hand, if the UCI type is HARQ-ACK for DCI-scheduled PDSCH, the PUCCH resources to be used for UCI transmission in the PUCCH resource set can be scheduled by DCI.

[0164] In the case of DCI-based PUCCH resource scheduling, the BS can send a DCI to the UE on the PDCCH and indicate the PUCCH resources to be used for UCI transmission in a specific PUCCH resource set via an ACK / NACK Resource Indicator (ARI) in the DCI. The ARI can be used to indicate PUCCH resources used for ACK / NACK transmission and is also called a PUCCH Resource Indicator (PRI). Here, the DCI can be used for PDSCH scheduling, and the UCI may include HARQ-ACK for the PDSCH. The BS can configure a PUCCH resource set for the UE via (UE-specific) higher-layer (e.g., RRC) signaling that includes a larger number of PUCCH resources than the ARI can represent. The ARI can indicate a subset of PUCCH resources in the PUCCH resource set, and which PUCCH resource in the indicated subset to use can be determined based on implicit rules according to transmission resource information about the PDCCH (e.g., the starting CCE index of the PDCCH).

[0165] For UL-SCH data transmission, the UE should include UL resources available to the UE; for DL-SCH data reception, the UE should include DL resources available to the UE. The BS assigns UL and DL resources to the UE through resource allocation. Resource allocation may include time-domain resource allocation (TDRA) and frequency-domain resource allocation (FDRA). In this disclosure, UL resource allocation is also referred to as UL licensing, and DL resource allocation is referred to as DL assignment. UL licensing is received dynamically by the UE on the PDCCH or in the RAR, or semi-persistently configured for the UE by the BS via RRC signaling. DL assignment is received dynamically by the UE on the PDCCH, or semi-persistently configured for the UE by the BS via RRC signaling.

[0166] On the UL, the BS can dynamically allocate UL resources to the UE via the PDCCH addressed to the Cell Radio Network Temporary Identifier (C-RNTI). The UE monitors the PDCCH to discover possible UL licenses for UL transmission. The BS can allocate UL resources to the UE using configuration licenses. Two types of configuration licenses are available: Type 1 and Type 2. In Type 1, the BS directly provides the configured UL licenses (including periodicity) via RRC signaling. In Type 2, the BS can configure the periodicity of RRC-configured UL licenses via RRC signaling and signal, enable, or disable the configured UL licenses via the PDCCH addressed to the Configuration Scheduling RNTI (CS-RNTI). For example, in Type 2, the PDCCH addressed to the CS-RNTI indicates deactivation, and the corresponding UL license can be implicitly reused based on the periodicity configured via RRC signaling.

[0167] On the DL (Deep Layer), the BS (Base Station) can dynamically allocate DL resources to the UE via a PDCCH addressed to the C-RNTI. The UE monitors the PDCCH to detect potential DL grants. The BS can allocate DL resources to the UE using SPS (Special Power Supply). The BS can configure the periodicity of the configured DL assignments via RRC (Regulatory Relationship Control) signaling and signal, enable, or disable the configured DL assignments via a PDCCH addressed to the CS-RNTI. For example, a PDCCH addressed to the CS-RNTI indicating deactivation can implicitly reuse the corresponding DL assignment based on the periodicity configured via RRC signaling.

[0168] Resource allocation via PDCCH and resource allocation via RRC will be described in more detail below.

[0169] Resource allocation via PDCCH: Dynamic licensing / assignment

[0170] The PDCCH can be used to schedule DL transmissions on the PDSCH and UL transmissions on the PUSCH. The DCI on the PDCCH used for scheduling DL transmissions may include DL resource assignments, which at least include an index I of the modulation and coding format (e.g., modulation and coding scheme (MCS)) associated with the DL-SCH. MCS The DCI on the PDCCH used for scheduling UL transmissions may include UL scheduling authorization, which includes at least the modulation and coding format associated with the UL-SCH, resource allocation, and HARQ information. HARQ information regarding the DL-SCH or UL-SCH may include a New Message Indicator (NDI), Transport Block Size (TBS), Redundancy Version (RV), and HARQ Process ID (i.e., HARQ Process Number). The size and purpose of the DCI carried by a PDCCH vary depending on the DCI format. For example, DCI format 0_0, DCI format 0_1, or DCI format 0_2 can be used to schedule PUSCH, while DCI format 1_0, DCI format 1_1, or DCI format 1_2 can be used to schedule PDSCH. Specifically, DCI format 0_2 and DCI format 1_2 can be used to schedule transmissions with higher transmission reliability and lower latency requirements than those guaranteed by DCI format 0_0, DCI format 0_1, DCI format 1_0, or DCI format 1_1. Some implementations of this disclosure can be applied to UL data transmission based on DCL format 0_2. Some implementations of this disclosure can be applied to DL data reception based on DCI format 1_2.

[0171] Figure 7 Examples of PDSCH TDRA caused by PDCCH and PUSCH TDRA caused by PDCCH are shown.

[0172] The DCI carried by the PDCCH for scheduling PDSCH or PUSCH includes a TDRA field. The TDRA field provides a row index m+1 value m for the PDSCH or PUSCH allocation table. A predefined default PDSCH time-domain allocation is applied as the PDSCH allocation table, or the PDSCH TDRA table configured by the BS via the RRC signal pdsch-TimeDomainAllocationList is applied as the PDSCH allocation table. Similarly, a predefined default PUSCH time-domain allocation is applied as the PUSCH allocation table, or the PUSCH TDRA table configured by the BS via the RRC signal pusch-TimeDomainAllocationList is applied as the PUSCH allocation table. The PDSCH TDRA table to be applied and / or the PUSCH TDRA table to be applied can be determined according to fixed / predefined rules (e.g., refer to 3GPPTS 38.214).

[0173] In the PDSCH time-domain resource configuration, each index row defines the DL assignment with the PDSCH slot offset K0, the start and length indicator value SLIV (or the start position of the PDSCH in the direct slot (e.g., the start symbol index S) and the allocation length (e.g., the number of symbols L)), and the PDSCH mapping type. In the PUSCH time-domain resource configuration, each index row defines the UL license with the PUSCH slot offset K2, the start position of the PUSCH in the slot (e.g., the start symbol index S) and the allocation length (e.g., the number of symbols L), and the PUSCH mapping type. K0 for PDSCH and K2 for PUSCH indicate the difference between a slot with a PDCCH and a slot with a corresponding PDSCH or PUSCH. SLIV represents a joint indicator of the start symbol S relative to the start of the slot with the PDSCH or PUSCH and the number L of consecutive symbols counted from symbol S. There are two PDSCH / PUSCH mapping types: mapping type A and mapping type B. In the case of PDSCH / PUSCH mapping type A, DMRS is mapped to the PDSCH / PUSCH resource relative to the start of the time slot. Depending on other DMRS parameters, one or two symbols of the PDSCH / PUSCH resource can be used as DMRS symbols. For example, in the case of PDSCH / PUSCH mapping type A, according to RRC signaling, the DMRS is located in the third symbol (symbol #2) or the fourth symbol (symbol #3) of the time slot. In the case of PDSCH / PUSCH mapping type B, DMRS is mapped relative to the first OFDM symbol of the PDSCH / PUSCH resource. Depending on other DMRS parameters, one or two symbols starting from the first symbol of the PDSCH / PUSCH resource can be used as DMRS symbols. For example, in the case of PDSCH / PUSCH mapping type B, the DMRS is located at the first symbol allocated to the PDSCH / PUSCH. In this disclosure, the PDSCH / PUSCH mapping type may be referred to as a mapping type or a DMRS mapping type. For example, in this disclosure, PUSCH mapping type A may be referred to as mapping type A or DMRS mapping type A, and PUSCH mapping type B may be referred to as mapping type B or DMRS mapping type B.

[0174] The scheduling DCI includes an FDRA field that provides assignment information about the RBs used for PDSCH or PUSCH. For example, the FDRA field provides information about the cell used for PDSCH or PUSCH transmission to the UE, information about the BWP used for PDSCH or PUSCH transmission, and / or information about the RBs used for PDSCH or PUSCH transmission.

[0175] Resource allocation via RRC

[0176] As described above, there are two types of transmissions without dynamic licensing: Configuration License Type 1 and Configuration License Type 2. In Configuration License Type 1, the UL license is provided by the RRC and stored as a configuration UL license. In Configuration License Type 2, the UL license is provided by the PDCCH and stored or cleared as a configuration UL license based on L1 signaling indicating whether the configuration UL license is enabled or disabled. Types 1 and 2 can be configured by the RRC per serving cell and per BWP. Multiple configurations can be active simultaneously on different serving cells.

[0177] When configuring license type 1, the following parameters can be provided to the UE via RRC signaling:

[0178] -cs-RNTI corresponds to CS-RNTI used for retransmission;

[0179] -periodicity corresponds to the periodicity of configuration license type 1;

[0180] -timeDomainOffset indicates the resource offset in the time domain relative to the system frame number (SFN) = 0;

[0181] The -timeDomainAllocation value m provides a row index m+1 pointing to the allocation table, indicating the combination of the start symbol S, length L, and PUSCH mapping type;

[0182] `-frequencyDomainAllocation` provides frequency domain resource allocation; and

[0183] -mcsAndTBS provides an I-value indicating the modulation order, target code rate, and transport block size. MCS .

[0184] When configuring configuration license type 1 for the serving cell via RRC, the UE stores the UL license provided by RRC as the configuration UL license for the indicated serving cell, and initializes or reinitializes the configuration UL license to start with a symbol based on timeDomainOffset and S (derived from SLIV) and repeats with periodicity. After configuring a UL license for license type 1, the UE can assume that the UL license is associated with repeated symbols that satisfy the following formula: [(SFN*numberOfSlotsPerFrame(numberOfSymbolsPerSlot)+(number of slots in the frame*numberOfSymbolsPerSlot)+number of symbols in the slot]=(timeDomainOffset*numberOfSymbolsPerSlot+S+N*periodicity)modulo(1024*numberOfSlotsPerFrame*numberOfSymbolsPerSlot), for all N>=0, where numberOfSlotsPerFrame and numberOfSymbolsPerSlot indicate the number of consecutive slots per frame and the number of consecutive OFDM symbols per slot, respectively (refer to Tables 1 and 2).

[0185] For configuration license type 2, the BS can provide the following parameters to the UE via RRC signaling:

[0186] -cs-RNTI corresponds to CS-RNTI, used to enable, disable, and retransmit; and

[0187] -periodicity provides the periodicity configuration for license type 2.

[0188] The actual UL license is provided to the UE via PDCCH (addressed to CS-RNTI). After configuring the UL license for license type 2, the UE can assume that the UL license is associated with the symbols that satisfy the following formula: [(SFN*numberOfSlotsPerFrame*numberOfSymbolsPerSlot)+(number of slots in the frame*numberOfSymbolsPerSlot)+number of symbols in the slot]=[(SFN 开始时间 *numberOfSlotsPerFrame*numberOfSymbolsPerSlot+slot 开始时间 *numberOfSymbolsPerSlot+symbol 开始时间)+N*periodicity]modulo(1024*numberOfSlotsPerFrame*numberOfSymbolsPerSlot), for all N>=0, where SFN 开始时间 The slot start time and symbol start time represent the SFN, slot, and symbol of the first transmission opportunity of PUSCH after the configuration permission is (re)initialized, respectively. numberOfSlotsPerFrame and numberOfSymbolsPerSlot indicate the number of consecutive slots per frame and the number of consecutive OFDM symbols per slot, respectively (refer to Tables 1 and 2).

[0189] In some scenarios, the BS may further provide the UE with the parameters harq-ProcID-Offset and / or harq-ProcID-Offset2 for deriving the HARQ process ID configured with UL permission. harq-ProcID-Offset is the offset of the configured UL-permitted HARQ process for shared spectrum channel access operations, and harq-ProcID-Offset2 is the offset of the configured UL-permitted HARQ process. In this disclosure, cg-RetransmissionTimer is the duration following a configured UL-permitted transmission (retransmission), where the UE should not autonomously perform retransmissions based on the HARQ process of the transmission (retransmission). The BS may provide cg-RetransmissionTimer to the UE when configuring retransmissions with UL permission. For a configuration license where neither harq-ProcID-Offset nor cg-RetransmissionTimer is configured, the HARQ process ID associated with the first symbol of the UL transmission can be derived from the following formula: HARQ process ID = [floor(CURRENT_symbol / periodicity)]modulonrofHARQ-Processes. For a configured UL license with harq-ProcID-Offset2, the HARQ process ID associated with the first symbol of the UL transmission can be derived from the following formula: HARQ process ID = [floor(CURRENT_symbol / periodicity)]modulo nrofHARQ-Processes+harq-ProcID-Offset2, where CURRENT_symbol = (SFN*numberOfSlotsPerFrame*numberOfSymbolsPerSlot + slot number in the frame*numberOfSymbolsPerSlot + symbol number in the slot), and numberOfSlotsPerFrame and numberOfSymbolsPerSlot represent the number of consecutive slots per frame and the number of consecutive OFDM symbols per slot, respectively. For a configured UL license with cg-RetransmissionTimer, the UE can select a HARQ process ID from those available for configuration license configuration.

[0190] On the DL, semi-persistent scheduling (SPS) can be provided to the UE from the BS per serving cell and per BWP via RRC signaling. For DL ​​SPS, DL assignments are provided to the UE via PDCCH and are stored or cleared based on L1 signaling indicating whether SPS is enabled or disabled. When configuring SPS, the BS can provide the UE with the following parameters via RRC signaling used to configure semi-persistent transmission (e.g., SPS configuration):

[0191] -cs-RNTI corresponds to CS-RNTI, which is used to enable, disable, and retransmit.

[0192] -nrofHARQ-Processes specifies the number of HARQ processes used for SPS;

[0193] -periodicity provides periodicity for configuration DL assignments for SPS;

[0194] -n1PUCCH-AN provides HARQ resources for PUCCH used in SPS (the network configures the HARQ resources as format 0 or format 1, and the actual PUCCH resources are configured by PUCCH-Config and referenced by their IDs in n1PUCCH-AN).

[0195] Multiple DL SPS configurations can be configured within the BWP of the serving cell. After configuring DL assignment for the SPS, the UE can sequentially assume that the Nth DL assignment occurs in a slot that satisfies the following formula: (numberOfSlotsPerFrame*SFN + number of slots in the frame) = [(numberOfSlotsPerFrame*SFN] 开始时间 +slot 开始时间 )+N*periodicity*numberOfSlotsPerFrame / 10]modulo(1024*numberOfSlotsPerFrame), where SFN 开始时间 and slot 开始时间 These represent the SFN and time slot of the first transmission of PDSCH after the configuration DL assignment is (re)initialized, respectively. numberOfSlotsPerFrame and numberOfSymbolsPerSlot indicate the number of consecutive time slots per frame and the number of consecutive OFDM symbols per time slot, respectively (refer to Tables 1 and 2).

[0196] In some scenarios, the BS can further provide the UE with the parameter harq-ProcID-Offset for deriving the HARQ process ID for the configured DL assignment. harq-ProcID-Offset is the offset of the SPS's HARQ process. For configured DL assignments without harq-ProcID-Offset, the HARQ process ID associated with the slot where the DL transmission begins can be determined from the following formula: HARQ process ID = [floor(CURRENT_slot*10 / (numberOfSlotsPerFrame*periodicity))]modulonrofHARQ-Processes, where CURRENT_slot = [(SFN*numberOfSlotsPerFrame) + slot number in the frame], and numberOfSlotsPerFrame represents the number of consecutive slots per frame. For a configured DL assignment with harq-ProcID-Offset, the HARQ process ID associated with the slot where the DL transfer begins can be determined by the following formula: HARQ process ID = [floor(CURRENT_slot / periodicity)]modulo nrofHARQ-Processes+harq-ProcID-Offset, where CURRENT_slot = [(SFN*numberOfSlotsPerFrame)+slot number in the frame], and numberOfSlotsPerFrame represents the number of consecutive slots per frame.

[0197] If the CRC corresponding to the DCI format is scrambled using the CS-RNTI provided by the RRC parameter cs-RNTI and the New Data Indicator field for enabling the transport block is set to 0, then the UE enables or releases the verification of the DL SPS assigned PDCCH or configures the UL licensed type 2 PDCCH for scheduling. Verification of the DCI format is achieved if all fields of the DCI format are set according to Tables 6 and 7. Table 6 shows examples of special fields for enabling PDCCH verification for DL ​​SPS and UL licensed type 2 scheduling, and Table 7 shows examples of special fields for releasing PDCCH verification for DL ​​SPS and UL licensed type 2 scheduling.

[0198] [Table 6]

[0199]

[0200] [Table 7]

[0201] DCI format 0_0 DCI format 1_0 HARQ process number Set all to "0" Set all to "0" Redundant version Set to "00" Set to "00" Modulation and coding schemes Set all to "1" Set all to "1" Resource block assignment Set all to "1" Set all to "1"

[0202] The actual DL assignment and UL license for DL ​​SPS or UL license type 2, and the corresponding MCS, are provided by the resource assignment field (e.g., the TDRA field providing the TDRA value m, the FDRA field providing the frequency resource block assignment, and / or the MCS field) in the DCI format carried by the corresponding DL SPS or UL license type 2 scheduling enabled PDCCH. If verification is implemented, the UE will treat the information in the DCI format as a valid enable or release of DL SPS or configured UL license type 2.

[0203] In this disclosure, a PDSCH based on DL SPS may be referred to as an SPS PDSCH, and a PUSCH based on UL Configuration License (CG) may be referred to as a CG PUSCH. A PDSCH dynamically scheduled by DCI carried on a PDCCH may be referred to as a Dynamically Licensed (DG) PDSCH, and a PUSCH dynamically scheduled by DCI carried on a PDCCH may be referred to as a DG PUSCH.

[0204] Figure 8 This illustrates the HARQ-ACK sending / receiving process.

[0205] Reference Figure 8 The UE can detect the PDCCH in time slot n. Next, the UE can receive the PDSCH in time slot n+K0 based on the scheduling information received via the PDCCH in time slot n, and then send a UCI via the PUCCH in time slot n+K1. In this case, the UCI includes a HARQ-ACK response to the PDSCH.

[0206] The DCI (e.g., DCI format 1_0 or DCI format 1_1) carried by the PDCCH used to schedule the PDSCH may include the following information.

[0207] -FDRA: FDRA indicates the set of RBs assigned to PDSCH.

[0208] -TDRA: TDRA indicates the DL assignment with respect to the PDSCH slot offset K0, the starting position (e.g., symbol index S) and length (e.g., number of symbols L) of the PDSCH in the slot, and the PDSCH mapping type. PDSCH mapping type A or PDSCH mapping type B can be indicated by TDRA. For PDSCH mapping type A, the DMRS is located in the third symbol (symbol #2) or fourth symbol (symbol #3) in the slot. For PDSCH mapping type B, the DMRS is allocated in the first symbol assigned to the PDSCH.

[0209] -PDSCH-to-HARQ_feedback timer indicator: This indicator points to K1.

[0210] If the PDSCH is configured to send a maximum of one TB, the HARQ-ACK response can consist of one bit. If the PDSCH is configured to send a maximum of two TBs, the HARQ-ACK response can consist of two bits when spatial binding is not configured, and one bit when spatial binding is configured. When the timing of HARQ-ACK transmission for multiple PDSCHs is specified as time slot n+K1, the UCI transmitted in time slot n+K1 includes HARQ-ACK responses for multiple PDSCHs.

[0211] In this disclosure, the HARQ-ACK payload consisting of one or more HARQ-ACK bits of the PDSCH can be referred to as the HARQ-ACK codebook. Depending on the HARQ-ACK payload determination scheme, the HARQ-ACK codebook can be classified as i) a semi-static HARQ-ACK codebook, ii) a dynamic HARQ-ACK codebook, and iii) a HARQ process-based HARQ-ACK codebook.

[0212] In the case of a semi-static HARQ-ACK codebook, parameters related to the size of the HARQ-ACK payload to be reported by the UE are semi-statically determined by (UE-specific) higher-layer (e.g., RRC) signals. The size of the HARQ-ACK payload in the semi-static HARQ-ACK codebook (e.g., the (maximum) HARQ-ACK payload (size) transmitted via a PUCCH in one slot) can be determined based on the number of HARQ-ACK bits corresponding to a combination (hereinafter, the bundled window) of all DL carriers (i.e., DL serving cells) configured for the UE and all DL scheduling slots (or PDSCH transmission slots or PDCCH monitoring slots) that can indicate the timing of HARQ-ACK transmission. That is, in a semi-static HARQ-ACK codebook scheme, the size of the HARQ-ACK codebook is fixed (to the maximum value), regardless of the actual amount of DL data scheduled. For example, the DL-granted DCI (PDCCH) includes PDSCH and HARQ-ACK timing information, and the PDSCH and HARQ-ACK 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 and HARQ-ACK timing information in the DL-licensed DCI (PDCCH) used to schedule the PDSCH indicates k, the HARQ-ACK information for the PDSCH can be sent in time slot #(m+k). As an example, k∈{1,2,3,4,5,6,7,8}. When HARQ-ACK information is sent in time slot #n, the HARQ-ACK information may include the maximum possible HARQ-ACK based on the bundling window. That is, the HARQ-ACK information for time slot #n may include the HARQ-ACK corresponding to time slot #(nk). For example, when k∈{1,2,3,4,5,6,7,8}, the HARQ-ACK information for time slot #n may include the HARQ-ACK corresponding to time slots #(n-8) to #(n-1), regardless of the actual DL data received (i.e., the maximum number of HARQ-ACKs). Here, HARQ-ACK information can be replaced by a HARQ-ACK codebook or a HARQ-ACK payload. Time slots can be understood / replaced as candidate timings for DL ​​data reception. As described in the example, the bundling window can be determined based on the HARQ-ACK time slots, using PDSCH and HARQ-ACK timings, and the PDSCH and HARQ-ACK 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. A semi-static HARQ-ACK codebook is referred to as a Type 1 HARQ-ACK codebook. For a Type 1 HARQ-ACK codebook, the number of bits to be sent in the HARQ-ACK report is fixed and can be large. If many cells are configured but only a few are scheduled, a Type 1 HARQ-ACK codebook can be inefficient.

[0213] In the case of a dynamic HARQ-ACK codebook, the size of the HARQ-ACK payload that the UE needs to report can be dynamically changed through DCI, etc. The dynamic HARQ-ACK codebook is referred to as a Type 2 HARQ-ACK codebook. A Type 2 HARQ-ACK codebook can be considered an optimized HARQ-ACK feedback because the UE only sends feedback for the scheduled serving cell. However, under poor channel conditions, the UE may incorrectly determine the number of scheduled serving cells. To address this issue, a downlink assignment index (DAI) can be included as part of the DCI. For example, in a dynamic HARQ-ACK codebook scheme, the DL scheduling DCI may include counter-DAI (i.e., c-DAI) and / or total-DAI (i.e., t-DAI). Here, the DAI indicates the downlink assignment index and is used by the BS to inform the UE that a HARQ-ACK transmission sent or scheduled should include its HARQ-ACK PDSCH. Specifically, c-DAI is an index indicating the order among PDCCHs (hereinafter, DL-scheduled PDCCHs) carrying DL-scheduled DCIs, and t-DAI is an index indicating the total number of DL-scheduled PDCCHs up to the point where there is a current slot with a PDCCH having t-DAI.

[0214] In the case of a HARQ-ACK codebook based on HARQ processes, the HARQ-ACK payload is determined based on all HARQ processes of all configured (or enabled) serving cells in the PUCCH group. For example, the size of the HARQ-ACK payload that the UE will report using a HARQ-ACK codebook based on HARQ processes can be determined based on the number of all configured or enabled serving cells in the PUCCH group configured for the UE and the number of HARQ processes of the serving cells. A HARQ-ACK codebook based on HARQ processes is also known as a Type 3 HARQ-ACK codebook. A Type 3 HARQ-ACK codebook can be used for one-time feedback.

[0215] In some scenarios, PUCCH feedback based on sub-slots consisting of fewer than 14 OFDM symbols (e.g., 2 or 7 OFDM symbols) and PUCCH feedback based on slots consisting of 14 OFDM symbols can be considered.

[0216] Individual codebooks can be formed / generated for HARQ-ACK feedback on multiple DL data channels (e.g., multiple PDSCHs) with different service types, quality of service (QoS), latency requirements, reliability requirements, and / or priorities. For example, HARQ-ACK codebooks for PDSCHs associated with high priority and HARQ-ACK codebooks for PDSCHs associated with low priority can be configured / formed separately. For HARQ-ACK feedback on PDSCHs with different priorities, PUCCH transmissions with different priorities can consider different parameters and resource configurations (see Information Element (IE) pucch-ConfigurationList in 3GPP TS 38.331). For example, if a pdsch-HARQ-ACK-CodebookList is provided to the UE via RRC signaling, the pdsch-HARQ-ACK-CodebookList can instruct the UE to generate one or more HARQ-ACK codebooks. When the UE is instructed to generate a HARQ-ACK codebook, the HARQ-ACK codebook is associated with the PUCCH of priority index 0. When providing the UE with a pdsch-HARQ-ACK-CodebookList, the UE only multiplexes HARQ-ACK information associated with the same priority index with the same HARQ-ACK codebook. When the UE is instructed to generate two HARQ-ACK codebooks, the first HARQ-ACK codebook is associated with the PUCCH of priority index 0, and the second HARQ-ACK codebook is associated with the PUCCH of priority index 1.

[0217] The unit of the time difference between the DL data channel and the PUCCH used for HARQ-ACK feedback transmission (e.g., the PDSCH-to-HARQ_feedback timing indicator) can be determined by a predetermined sub-slot length (e.g., the number of symbols included in the sub-slot). For example, the unit of the time difference between the DL data channel and the PUCCH used for HARQ-ACK feedback transmission can be configured by the parameter "subslotLengthForPUCCH" in the configuration information PUCCH-Config used to configure UE-specific PUCCH parameters. Depending on these scenarios, the length unit of the PDSCH-to-HARQ feedback timing indicator can be configured for each HARQ-ACK codebook.

[0218] In some scenarios, out-of-order PDSCH reception and HARQ-ACK transmission of a HARQ process are not permitted. This is one method used by the UE and BS to assume the same PUCCH transmission time so that the BS is allowed to successfully receive PUCCHs transmitted from the UE. In these scenarios, for example, it is necessary to schedule PDSCHs so that HARQ-ACK transmission for the first received PDSCH ends before HARQ-ACK transmission for the later received PDSCH. In these scenarios, it is stipulated that for any HARQ process ID in a given scheduled cell, the UE does not expect to receive PDSCHs that overlap with another PDSCH in time. Additionally, in these scenarios, it is stipulated that the UE does not expect to receive another PDSCH for a given HARQ process until the expected transmission of the HARQ-ACK for the HARQ process has ended.

[0219] Figure 9 Examples of scheduling constraints based on some scenarios are shown.

[0220] Reference Figure 9 For example, in some scenarios, when receiving PDSCH#1 of HARQ process #i, the UE may not expect to receive another PDSCH of HARQ process #i before the HARQ-ACK for PDSCH#1 is completed (e.g., Figure 9 (PDSCH#2 in the example). That is, the UE can expect to receive another PDSCH for HARQ process #i only after the HARQ-ACK for PDSCH#1 has ended.

[0221] In some scenarios, UL or DL ​​scheduling can be performed dynamically or semi-persistently. The BS can configure or indicate the transmission direction (e.g., DL, UL, or flexible) of individual symbols to the UE semi-persistently or dynamically based on DCI format 2_0, using the tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated messages. Configured / indicated UL or DL ​​scheduling can be canceled by specifying the transmission direction.

[0222] Figure 10 This shows an example of HARQ-ACK being delayed.

[0223] In some scenarios (e.g., 3GPP NR Rel-16), when a UE receives a PDSCH scheduled by the BS, the UE can send a PUCCH carrying a HARQ-ACK for the PDSCH (hereinafter, HARQ-ACK PUCCH) at the time specified in the scheduling information about the PDSCH. However, this series of operations always results in the UE sending the PUCCH after a predetermined time has elapsed since receiving the semi-persistent SPS PDSCH. As a result, the PUCCH transmission can be easily canceled through the BS's dynamic TDD operation using a TDD pattern that is inconsistent with the periodicity of the SPS PDSCH, and the PDSCH transmission associated with the canceled PUCCH transmission can also be canceled or retransmission can be requested. Therefore, to address these issues, consider the operation of the UE delaying the PUCCH timing determined for the PDSCH in a predetermined or arbitrary manner (i.e., delay operation). For example, when a PUCCH configured to send a HARQ-ACK (hereinafter, SPS HARQ-ACK) for SPSPDSCH is cancelled by the configured or indicated transmission direction, a HARQ-ACK delay can be considered, which postpones the HARQ-ACK transmission until after the originally scheduled time. For example, refer to Figure 10 When the SPS PDSCH in time slot #n-1 uses HARQ process #i, and the HARQ-ACK transmission for the SPS PDSCH is scheduled in time slot #n, the UE can determine, based on predetermined conditions, to postpone the PUCCH used for the HARQ-ACK transmission of the SPS PDSCH in time slot #n to time slot #m. Due to this HARQ-ACK postponement, even if the PUCCH transmission is canceled, the UE and BS can still send / receive the HARQ-ACK information for the SPS PDSCH later.

[0224] However, based on Figure 9 As described in the scenario, due to scheduling constraints, SPS PDSCH retransmission also needs to be performed after HARQ-ACK is sent. Therefore, if HARQ-ACK is delayed for SPS PDSCH, HARQ-ACK can be sent later than expected, resulting in potentially significant delays in SPS PDSCH retransmission.

[0225] Considering these issues, the implementation of a new PDSCH reception and corresponding HARQ-ACK transmission for the associated HARQ process will be described when the UE delays a portion of the PUCCH transmission for SPS, thus increasing the interval between the PDSCH reception timing and the HARQ-ACK transmission timing.

[0226] Specifically, an implementation method will be described whereby the UE and BS select an alternative UL channel (e.g., PUCCH) to transmit the SPS HARQ-ACK information when the PUCCH transmission of the SPS HARQ-ACK information at the UE is cancelled. Additionally, an implementation method for multiplexing the SPS HARQ-ACK information with existing UCI will be described. According to some implementations of this disclosure, the BS can provide the UE with more freedom in providing TDD UL-DL configuration and SPS PDSCH resources. Even if the PUCCH for a given SPS PDSCH is unavailable due to TDD operation, the UE can still provide the relevant SPSHARQ-ACK response to the BS based on available UL resources and channels, according to some implementations of this disclosure.

[0227] UE side:

[0228] Figure 11 The operation flow of a UE according to some implementations of this disclosure is shown.

[0229] In some implementations of this disclosure, when the UE sends a HARQ-ACK to an SPS PDSCH associated with a HARQ process with a time delay indicated or configured by the BS, the BS can schedule different PDSCHs for the UE to enable the UE to receive another PDSCH of the same HARQ process. In this case, in some implementations, the UE can abandon the delayed HARQ-ACK transmission. Alternatively, in some implementations, the UE can multiplex the delayed HARQ-ACK transmission with other UCI or UL data.

[0230] The UE may receive TDD configuration (e.g., tdd-UL-DL-ConfigurationCommon or tdd-UL-DLConfigurationDedicated) and SPS radio resource configuration (e.g., SPS configuration) from the BS. The UE may receive the SPS PDSCH of HARQ process #i on the DL radio resource based on the TDD configuration and SPS configuration (S1101). After receiving the SPS PDSCH of HARQ process #i, if the PUCCH resource X associated with the SPS PDSCH indicates a DL radio resource, the UE may determine to perform a HARQ-ACK transmission for the SPS PDSCH on another available PUCCH resource or an available UL resource Y (S1103). The UE may anticipate receiving new PDSCH scheduling information for the HARQ process #i of the SPS PDSCH after PUCCH resource X. The UE may anticipate receiving another PDSCH for the HARQ process #i of the SPS PDSCH after PUCCH resource X (S1105).

[0231] When the UE receives new PDSCH scheduling information and sends related HARQ-ACK information on PUCCH resource Z, the UE can determine whether to send HARQ-ACK information on UL resource Y and PUCCH resource Z according to some implementation methods of this disclosure.

[0232] Among some implementations of this disclosure, the following UE operations may be considered.

[0233] <Implementation Method A1> Fast transmission (retransmission) after delaying PUCCH transmission

[0234] The UE can receive TDD configuration and configuration related to SPS radio resources from the BS, and perform SPS PDSCH reception on DL radio resources. After receiving the SPS PDSCH, if the relevant PUCCH resource X includes DL radio resources, the UE can perform HARQ-ACK transmission for the corresponding SPS PDSCH on another available PUCCH resource or available UL resource Y. The UE can expect to receive new scheduling information for the HARQ process of the SPS PDSCH from or after PUCCH resource X.

[0235] In some implementations, for example, the UE may expect to receive new scheduling information for the HARQ process of the SPS PDSCH at the following time points:

[0236] i) If PUCCH resource X is indicated in time slot #n or sub-time slot #n, then from time slot #n+1 or sub-time slot #n+1;

[0237] ii) The start symbol from resource X in PUCCH;

[0238] iii) From the last symbol of PUCCH resource X; and

[0239] iv) End from PUCCH resource X.

[0240] In some implementations, new scheduling information for the HARQ process of the SPS PDSCH can be limited to retransmissions of transport blocks (TBs) sent on the SPS PDSCH. For example, implementation A1 can be applied restrictively when the scheduling DCI indicating a new PDSCH is scrambled with CS-RNTI and the NDI value is indicated as 1. For example, in some implementations, when the scheduling DCI indicating a new PDSCH associated with a delayed HARQ-ACK transmission is scrambled with CS-RNTI and the NDI value is indicated as 1, the UE can expect to receive the scheduling DCI if the transmission time before the delay of the HARQ-ACK transmission ends even before the end of the transmission time after the delay of the HARQ-ACK transmission.

[0241] In some implementations, the new scheduling information may include information for changing the TB or associated HARQ information of the corresponding HARQ process, such as information for changing at least one of the following: received coded bits, last received RV, received TB, indicated MCS value, TB length, NDI value, HARQ-ACK transmission timing, or PUCCH resource indicator value.

[0242] Figure 12 This illustrates another example of scheduling constraints based on certain scenarios. Specifically, Figure 12 This illustrates the relationship between the PDSCH reception time and the HARQ-ACK transmission time of the same HARQ process when HARQ-ACK delay is performed in some scenarios where out-of-order HARQ transmission is not allowed.

[0243] In some scenarios, the UE is not allowed to receive the PDSCH and send the HARQ-ACK for a HARQ process out of order. For example, the UE may not expect to receive another PDSCH for a given HARQ process until the expected HARQ-ACK for the HARQ process has been sent (see [link]). Figure 9 In a given scheduled cell, the UE does not expect to receive a first PDSCH and a second PDSCH that starts later than the first PDSCH simultaneously. The corresponding HARQ-ACK for the second PDSCH is assigned to be transmitted on a resource that ends before the start of a different resource used to assign the HARQ-ACK to the first PDSCH, wherein the two resources are in different time slots for the reception of the associated HARQ-ACK, each time slot consisting of 14 symbols or the number of symbols indicated by subslotLengthForPUCCH (if provided), and the HARQ-ACKs for the two PDSCHs are associated with HARQ-ACK codebooks of the same priority. In a given scheduled cell, the UE does not expect to receive a first PDSCH and a second PDSCH that starts later than the first PDSCH simultaneously. The corresponding HARQ-ACK for the second PDSCH is assigned to be transmitted on a resource that ends before the start of a different resource used to assign the HARQ-ACK to the first PDSCH, if the HARQ-ACKs for the two PDSCHs are associated with HARQ-ACK codebooks of different priorities.

[0244] Reference Figure 12When the HARQ-ACK transmission of PDSCH #1 based on HARQ process #i is delayed from time slot #n to time slot #m, which is after time slot #n, the UE does not expect to receive another PDSCH of the same HARQ process #i before the expected HARQ-ACK transmission in time slot #m ends. That is, the UE only expects to receive another PDSCH of the same HARQ process #i after the expected HARQ-ACK transmission in time slot #m ends.

[0245] However, in some implementations of this disclosure, the following can be considered for faster retransmission or new transmission. For the transmission of a HARQ-ACK response that is abandoned due to a conflict with a DL symbol and / or a low-priority HARQ-ACK response that is canceled due to a conflict with high-priority UL control information (and the associated HARQ process ID), the UE may exceptionally 1) be allowed to perform PDSCH transmission (retransmission) / reception and associated HARQ-ACK transmission with the same HARQ process ID even before performing the corresponding HARQ-ACK transmission via a delayed-loaded PUCCH or Type 3 codebook through the abandoned and / or canceled HARQ-ACK transmission; and 2) be relaxed to determine the predefined out-of-order HARQ restrictions for the HARQ process ID based on the HARQ-ACK transmission time indicated / configured before abandonment / cancellation (rather than the actual HARQ-ACK transmission time (e.g., the delayed HARQ-ACK transmission time)).

[0246] In other words, in some implementations of this disclosure, for sending HARQ-ACK responses that are abandoned due to conflicts with DL symbols and / or low-priority HARQ-ACK responses that are canceled due to conflicts with high-priority UL control information (and the associated HARQ process ID), the following exceptions may be considered: 1) even before sending the corresponding A / N feedback via a PUCCH or Type 3 codebook loaded with a delayed A / N feedback via abandoned and / or canceled A / N feedback, the operation of PDSCH transmission (retransmission) / reception and associated A / N feedback transmission with the same HARQ process ID is allowed; and 2) the determination of whether HARQs with the same HARQ process ID are out of order is relaxed, such that the determination is based on the A / N transmission time indicated / configured before abandonment / cancellation (rather than the actual A / N transmission time (e.g., the delayed HARQ-ACK transmission time)).

[0247] Figure 13 Examples of HARQ timing according to some implementations of this disclosure are shown. Specifically, Figure 13 This illustrates the relationship between the PDSCH reception time and the HARQ-ACK transmission time of the same HARQ process when HARQ-ACK is delayed.

[0248] Reference Figure 13 When the HARQ-ACK transmission of PDSCH #1 based on HARQ process #i is delayed from time slot #n to time slot #m after time slot #n via HARQ-ACK postponement, according to some implementations of this disclosure, the UE can expect to receive another PDSCH of the same HARQ process #i even before the expected HARQ-ACK transmission in time slot #m ends and after the expected HARQ-ACK transmission in time slot #n ends.

[0249] However, the UE does not expect to receive another PDSCH using the same HARQ process #i before the expected HARQ-ACK transmission in time slot #n ends. That is, the UE can expect to receive another PDSCH using the same HARQ process #i no earlier than after the expected HARQ-ACK transmission in time slot #n ends. Here, the other PDSCH can be a PDSCH corresponding to the retransmission of PDSCH #1 or a new PDSCH different from PDSCH #1. In some implementations, when it is said that the UE expects to receive another PDSCH using the same HARQ process #i only after the expected HARQ-ACK transmission in time slot #n ends, it may mean that the UE will not receive another PDSCH using the same HARQ process #i before the expected HARQ-ACK transmission in time slot #m ends. Alternatively, when it is said that the UE expects to receive another PDSCH using the same HARQ process #i only after the expected HARQ-ACK transmission in time slot #n has ended, it may mean that even if the UE receives another PDSCH using the same HARQ process #i before the expected HARQ-ACK transmission in time slot #n has ended, the UE will not decode that other PDSCH, will not send a HARQ-ACK for it, or will determine that an error exists. Alternatively, when it is said that the UE expects to receive another PDSCH using the same HARQ process #i only after the expected HARQ-ACK transmission in time slot #n has ended, it may mean that even if the UE receives scheduling information indicating that it should send another PDSCH using the same HARQ process #i before the HARQ-ACK transmission has ended, the UE will determine that the scheduling information is invalid.

[0250] <Implementation Method A1-1> HARQ-ACK response for fast transmission (retransmission)

[0251] Regarding implementation A1, the following can also be considered. If, as in implementation A1, the scheduling of a new dynamic PDSCH for the HARQ process associated with HARQ-ACK transmission X and its HARQ-ACK transmission Y is indicated before the delayed HARQ-ACK transmission X of the SPS PDSCH, then the UE can perform HARQ-ACK transmission X and / or HARQ-ACK transmission Y according to the following alternative scheme. For example, when the HARQ-ACK transmission of PDSCH #1 based on HARQ process #i is delayed from time slot #n to time slot #m after time slot #n by delaying the HARQ-ACK transmission of PDSCH #1 based on HARQ process #i, if the UE receives scheduling information for the new dynamically scheduled PDSCH (hereinafter, dynamic PDSCH) and the HARQ-ACK transmission Y of the dynamic PDSCH before the expected HARQ-ACK transmission X in time slot #m, then the UE can perform HARQ-ACK transmission X and HARQ-ACK transmission Y according to the following alternative scheme.

[0252] *Alternative Solution 1: If HARQ-ACK transmission X and HARQ-ACK transmission Y are HARQ-ACK responses of the same TB, then the UE executes both HARQ-ACK transmission X and HARQ-ACK transmission Y. In this case, the latest decoding result of the corresponding HARQ process can be reported as the feedback value based on the transmission time of HARQ-ACK transmission X and HARQ-ACK transmission Y, respectively. Alternative Solution 1 can be used to improve HARQ-ACK reliability.

[0253] *Alternative Option 1-1: If HARQ-ACK transmission X and HARQ-ACK transmission Y are HARQ-ACK responses of the same TB, then the UE executes both HARQ-ACK transmission X and HARQ-ACK transmission Y. In this case, the value of the decoding result based on SPS PDSCH can be used as the feedback value for HARQ-ACK transmission X, and the value of the decoding result based on dynamic PDSCH can be used as the feedback value for HARQ-ACK transmission Y.

[0254] *Alternative Solution 2: If HARQ-ACK transmission X and HARQ-ACK transmission Y are HARQ-ACK responses of the same TB, the UE may only perform HARQ-ACK transmission Y without performing HARQ-ACK transmission X. Alternative Solution 2 can be applied restrictively when HARQ-ACK transmission X is the only HARQ-ACK feedback on the UL resource for which HARQ-ACK transmission X was performed. For example, alternative solution 2 can be applied restrictively when HARQ-ACK transmission X is not multiplexed with other HARQ-ACK transmissions on the PUCCH, i.e., when there are no other HARQ-ACK messages other than HARQ-ACK transmission X on the corresponding PUCCH. Alternative Solution 2 minimizes UE complexity and UE UL transmission by allowing the UE to transmit only the latest decoding result.

[0255] *Alternative Option 3: If HARQ-ACK transmission X and HARQ-ACK transmission Y are HARQ-ACK responses for different TBs, then the UE executes both HARQ-ACK transmission X and HARQ-ACK transmission Y. In this case, the latest decoding result of the corresponding HARQ process can be reported as a feedback value based on the corresponding transmission time of HARQ-ACK transmission X and HARQ-ACK transmission Y. The reported feedback values ​​may be different or the same depending on the transmission time of HARQ-ACK transmission X and HARQ-ACK transmission Y. For example, if PDSCH Y is received after PDSCH X and the decoding of the TB related to HARQ-ACK transmission Y is completed before HARQ-ACK transmission X, then HARQ-ACK for PDSCH X may not be transmitted, and the decoding result of PDSCH X can be reported as a feedback value in both HARQ-ACK transmission X and HARQ-ACK transmission Y. Alternative Option 3 can be used to improve HARQ-ACK reliability.

[0256] In some implementations, if the transmission of the HARQ-ACK response for the SPS PDSCH is abandoned, the corresponding SPS PDSCH for which the HARQ-ACK (sub) codebook only includes the HARQ-ACK response for the SPS PDSCH can be disregarded during the construction process. For example, in the case of an SPS PDSCH for which the HARQ-ACK response transmission is abandoned, even if the corresponding SPS PDSCH resource is valid (because there is no UL symbol or no UL transmission), HARQ-ACK information about the SPS PDSCH can be excluded during the formation / generation of the HARQ-ACK (sub) codebook based on the PDSCH timing. Therefore, the HARQ-ACK (sub) codebook may not have bit positions associated with the SPS PDSCH resource.

[0257] BS side:

[0258] The implementation methods of this disclosure will be described again from the perspective of the BS.

[0259] Figure 14 The operation flow of a BS is shown according to some implementations of this disclosure.

[0260] In some implementations of this disclosure, when the UE sends a HARQ-ACK to an SPS PDSCH associated with a HARQ process with a time delay indicated or configured by the BS, the BS can send another PDSCH of the same HARQ process to the UE through different PDSCH scheduling for the UE. In this case, in some implementations, the BS may assume that the UE abandons the delayed HARQ-ACK transmission. Alternatively, in some implementations, the BS may assume that the UE multiplexes the delayed HARQ-ACK transmission with other UCI or UL data.

[0261] The BS may send the TDD configuration (e.g., tdd-UL-DL-ConfigurationCommon or tdd-UL-DLConfigurationDedicated) and SPS radio resource configuration (e.g., SPS configuration) to the UE. The BS may send the SPS PDSCH of HARQ process #i to the UE on the DL radio resource based on the TDD configuration and SPS configuration (S1401). If the PUCCH resource X associated with the SPS PDSCH of HARQ process #i includes a DL radio resource, the BS may attempt to receive the HARQ-ACK of the SPS PDSCH by assuming that the UE will send a HARQ-ACK in another PUCCH resource or an available UL resource Y (S1403). The BS may send new PDSCH scheduling information for the HARQ process #i of the SPS PDSCH after PUCCH resource X. The BS may send another PDSCH for the HARQ process #i of the SPSPDSCH after PUCCH resource X (S1405).

[0262] When the UE receives new PDSCH scheduling information and sends related HARQ-ACK information on PUCCH resource Z, according to some implementations of this disclosure, the BS may assume that the UE will determine to send HARQ-ACK information on UL resource Y and PUCCH resource Z.

[0263] Among some implementations of this disclosure, the following BS operations may be considered.

[0264] <Implementation Method B1> Fast transmission (retransmission) after delaying PUCCH transmission

[0265] The BS can send TDD configuration and configuration related to SPS radio resources to the UE, and send SPS PDSCH in DL radio resources. When the PUCCH resource X associated with the SPS PDSCH includes DL radio resources, the BS can attempt to receive the HARQ-ACK of the SPS PDSCH by assuming that the UE will send the HARQ-ACK of the corresponding SPS PDSCH on another available PUCCH resource or available UL resource Y. The BS can send new scheduling information for the HARQ process of the SPS PDSCH from or after PUCCH resource X.

[0266] In some implementations, for example, the BS may send new scheduling information for the SPS PDSCH HARQ process at the following times:

[0267] i) If PUCCH resource X is indicated in time slot #n or sub-time slot #n, then from time slot #n+1 or sub-time slot #n+1;

[0268] ii) The start symbol from resource X in PUCCH;

[0269] iii) From the last symbol of PUCCH resource X; and

[0270] iv) End from PUCCH resource X.

[0271] In some implementations, new scheduling information for the HARQ process of the SPS PDSCH can be limited to retransmissions of TBs sent on the SPS PDSCH. For example, implementation B1 can be applied restrictively when the scheduling DCI indicating a new PDSCH is scrambled with CS-RNTI and the NDI value is indicated as 1. For example, in some implementations, when the scheduling DCI indicating a new PDSCH for a HARQ process associated with a delayed HARQ-ACK transmission is scrambled with CS-RNTI and the NDI value is indicated as 1, the BS can send the scheduling DCI if the transmission time before the delay of the HARQ-ACK transmission ends even before the transmission time after the delay of the HARQ-ACK transmission ends.

[0272] In some implementations, the new scheduling information may include information for changing the TB or associated HARQ information of the corresponding HARQ process, such as information for changing at least one of the following: received coded bits, last received RV, received TB, indicated MCS value, TB length, NDI value, HARQ-ACK transmission timing, or PUCCH resource indicator value.

[0273] In some scenarios, the BS is not allowed to perform PDSCH transmission and HARQ-ACK reception for a HARQ process. For example, the BS is not allowed to transmit another PDSCH for a given HARQ process until the expected reception of the HARQ-ACK for the HARQ process has ended (see [link]). Figure 9 In a given scheduled cell, a BS is not allowed to simultaneously transmit a first PDSCH and a second PDSCH that starts later than the first PDSCH. The corresponding HARQ-ACK for the second PDSCH is assigned to be received on a resource that ends before the start of a different resource used to assign the HARQ-ACK to the first PDSCH, wherein these two resources are in different time slots used for the associated HARQ-ACK reception, each time slot consisting of 14 symbols or the number of symbols indicated by subslotLengthForPUCCH (if provided), and the HARQ-ACKs for both PDSCHs are associated with HARQ-ACK codebooks of the same priority. In a given scheduled cell, a BS is not allowed to simultaneously transmit a first PDSCH and a second PDSCH that starts later than the first PDSCH. If the HARQ-ACKs for these two PDSCHs are associated with HARQ-ACK codebooks of different priorities, then the corresponding HARQ-ACK for the second PDSCH is assigned to be received on a resource that ends before the start of a different resource used to assign the HARQ-ACK to the first PDSCH.

[0274] Reference Figure 12 When the HARQ-ACK reception of PDSCH #1 based on HARQ process #i is delayed from time slot #n to time slot #m, which is after time slot #n, the BS is not allowed to send another PDSCH of the same HARQ process #i before the expected HARQ-ACK reception in time slot #m ends. That is, the BS is only allowed to send another PDSCH of the same HARQ process #i after the expected HARQ-ACK reception in time slot #m ends.

[0275] However, in some implementations of this disclosure, the following can be considered for faster retransmission or new transmission. For the reception of HARQ-ACK responses that are abandoned due to conflicts with DL symbols and / or low-priority HARQ-ACK responses (and associated HARQ process IDs) that are canceled due to conflicts with high-priority UL control information, the BS may exceptionally 1) be allowed to perform PDSCH transmission (retransmission) and associated HARQ-ACK reception with the same HARQ process ID even before performing the corresponding HARQ-ACK reception via a delayed-loaded PUCCH or Type 3 codebook after the abandoned and / or canceled HARQ-ACK reception; and 2) be relaxed the predefined out-of-order HARQ restrictions on determining a HARQ process ID based on the HARQ-ACK reception time indicated / configured before abandonment / cancellation (rather than the actual HARQ-ACK reception time (e.g., the delayed HARQ-ACK reception time)).

[0276] In other words, in some implementations of this disclosure, the reception of HARQ-ACK responses (and associated HARQ process IDs) that are abandoned due to conflicts with DL symbols and / or canceled due to conflicts with high-priority UL control information may be exceptionally considered as follows: 1) the operation of PDSCH transmission (retransmission) and related A / N feedback reception with the same HARQ process ID is allowed even before the corresponding A / N feedback is received by the PUCCH or Type 3 codebook that has been delayed via abandoned and / or canceled A / N feedback; and 2) the determination of whether HARQs with the same HARQ process ID are out of order is relaxed so that the determination is based on the A / N reception time indicated / configured before abandonment / cancellation (rather than the actual A / N reception time (e.g., the delayed HARQ-ACK reception time)).

[0277] For example, refer to Figure 13 When the HARQ-ACK transmission of PDSCH #1 based on HARQ process #i is delayed from time slot #n to time slot #m after time slot #n via HARQ-ACK postponement, according to some implementations of this disclosure, it is permissible for the BS to transmit another PDSCH of the same HARQ process #i to the UE even after the expected HARQ-ACK reception in time slot #n has ended, even before the expected HARQ-ACK reception in time slot #m has ended.

[0278] However, the BS is not allowed to send another PDSCH using the same HARQ process #i before the expected HARQ-ACK reception in slot #n ends. That is, the BS is allowed to send another PDSCH using the same HARQ process #i to the UE no later than after the expected HARQ-ACK reception in slot #n ends. Here, the other PDSCH can be a PDSCH corresponding to the retransmission of PDSCH #1 or a new PDSCH different from PDSCH #1. In some implementations, when it is said that the BS is allowed to send another PDSCH using the same HARQ process #i to the UE only after the expected HARQ-ACK reception in slot #n ends, it may mean that the BS does not send another PDSCH using the same HARQ process #i to the UE before the expected HARQ-ACK reception in slot #m ends. Alternatively, when it is said that the BS is allowed to send another PDSCH using the same HARQ process #i to the UE only after the expected HARQ-ACK reception in slot #n has ended, it may mean that even if the BS sends another PDSCH using the same HARQ process #i to the UE before the expected HARQ-ACK reception in slot #n has ended, the BS assumes that the UE will not decode the other PDSCH, will not send a HARQ-ACK, or can determine that an error exists. Alternatively, when it is said that the BS is allowed to send another PDSCH using the same HARQ process #i to the UE only after the expected HARQ-ACK reception in slot #n has ended, it may mean that even if the BS sends scheduling information to the UE instructing that another PDSCH using the same HARQ process #i be sent before the HARQ-ACK transmission has ended, the BS determines that the scheduling information is invalid.

[0279] <Implementation Method B1-1> HARQ-ACK response for fast transmission (retransmission)

[0280] Regarding implementation B1, the following can also be considered. If the BS indicates to the UE the scheduling of a new dynamic PDSCH for the HARQ process associated with HARQ-ACK transmission X and its HARQ-ACK transmission Y before the delayed HARQ-ACK transmission X of the SPS PDSCH, the UE can perform HARQ-ACK transmission X and / or HARQ-ACK transmission Y according to the following alternative scheme. For example, when the HARQ-ACK reception of PDSCH #1 based on HARQ process #i is delayed from time slot #n to time slot #m after time slot #n by HARQ-ACK postponement, if the BS sends scheduling information about the dynamic PDSCH of HARQ process #i and the HARQ-ACK transmission Y of the dynamic PDSCH to the UE before the expected HARQ-ACK reception X in time slot #m, the BS can attempt to receive UCI by assuming that the UE will perform HARQ-ACK transmission X and HARQ-ACK transmission Y according to the following alternative scheme.

[0281] *Alternative Solution 1: If HARQ-ACK transmission X and HARQ-ACK transmission Y are HARQ-ACK responses of the same TB, then the UE executes both HARQ-ACK transmission X and HARQ-ACK transmission Y. In this case, the latest decoding result of the corresponding HARQ process can be reported as the feedback value based on the transmission time of HARQ-ACK transmission X and HARQ-ACK transmission Y, respectively. Alternative Solution 1 can be used to improve HARQ-ACK reliability.

[0282] *Alternative Option 1-1: If HARQ-ACK transmission X and HARQ-ACK transmission Y are HARQ-ACK responses of the same TB, then the UE executes both HARQ-ACK transmission X and HARQ-ACK transmission Y. In this case, the value of the decoding result based on SPS PDSCH can be used as the feedback value for HARQ-ACK transmission X, and the value of the decoding result based on dynamic PDSCH can be used as the feedback value for HARQ-ACK transmission Y.

[0283] *Alternative Solution 2: If HARQ-ACK transmission X and HARQ-ACK transmission Y are HARQ-ACK responses of the same TB, the UE may only perform HARQ-ACK transmission Y without performing HARQ-ACK transmission X. Alternative Solution 2 can be applied restrictively when HARQ-ACK transmission X is the only HARQ-ACK feedback on the UL resource for which HARQ-ACK transmission X was performed. For example, alternative solution 2 can be applied restrictively when HARQ-ACK transmission X is not multiplexed with other HARQ-ACK transmissions on the PUCCH, i.e., when there are no other HARQ-ACK messages other than HARQ-ACK transmission X on the corresponding PUCCH. Alternative Solution 2 minimizes UE complexity and UE UL transmission by allowing the UE to transmit only the latest decoding result.

[0284] *Alternative Option 3: If HARQ-ACK transmission X and HARQ-ACK transmission Y are HARQ-ACK responses for different TBs, then the UE executes both HARQ-ACK transmission X and HARQ-ACK transmission Y. In this case, the latest decoding result of the corresponding HARQ process can be reported as a feedback value based on the corresponding transmission time of HARQ-ACK transmission X and HARQ-ACK transmission Y. The reported feedback values ​​may be different or the same depending on the transmission time of HARQ-ACK transmission X and HARQ-ACK transmission Y. For example, if PDSCH Y is received after PDSCH X and the decoding of the TB related to HARQ-ACK transmission Y is completed before HARQ-ACK transmission X, then HARQ-ACK for PDSCH X may not be transmitted, and the decoding result of PDSCH X can be reported as a feedback value in both HARQ-ACK transmission X and HARQ-ACK transmission Y. Alternative Option 3 can be used to improve HARQ-ACK reliability.

[0285] In some implementations, if the transmission of the HARQ-ACK response for the SPS PDSCH is abandoned, the corresponding SPS PDSCH for which the HARQ-ACK (sub) codebook only includes the HARQ-ACK response for the SPS PDSCH can be disregarded during the construction process. For example, in the case of an SPS PDSCH for which the HARQ-ACK response transmission is abandoned, even if the corresponding SPS PDSCH resource is valid (because there is no UL symbol or no UL transmission), HARQ-ACK information about the SPS PDSCH can be excluded during the formation / generation of the HARQ-ACK (sub) codebook based on the PDSCH timing. Therefore, the HARQ-ACK (sub) codebook may not have bit positions associated with the SPS PDSCH resource.

[0286] In some implementations of this disclosure, the BS may provide the UE with an RRC configuration for slot format determination based on SPS PDSCH and TDD operations. The BS may provide the UE with one or more SPS PDSCH configurations, and the UE may receive the SPS PDSCH based on the SPS PDSCH configuration and perform associated PUCCH transmissions. When a UE's PUCCH transmission is cancelled, the UE may delay the corresponding PUCCH transmission, and the BS may indicate a new schedule for the associated HARQ process after the PUCCH resources used to cancel the PUCCH transmission. In some implementations of this disclosure, the UE may receive one or more schedules for a HARQ process before a HARQ-ACK response. The UE may perform a HARQ-ACK PUCCH transmission including a HARQ-ACK response and / or a HARQ-ACK associated with the one or more schedules.

[0287] According to some implementations of this disclosure, when a UE's PUCCH transmission is cancelled, the BS can schedule and transmit new PDSCH resources that improve the reception reliability of the associated PDSCH. According to some implementations of this disclosure, when PUCCH transmission is delayed, the UE can quickly receive PDSCH retransmissions, thereby reducing DL latency.

[0288] To receive the DL channel, the UE may perform operations according to some implementations of this disclosure. The UE may include: at least one transceiver; at least one processor; and at least one computer memory operatively connected to the at least one processor and configured to store instructions that, when executed, cause the at least one processor to perform operations according to some implementations of this disclosure. Processing means for the UE may include: at least one processor; and at least one computer memory operatively connected to the at least one processor and configured to store instructions that, when executed, cause the at least one processor to perform operations according to some implementations of this disclosure. A computer-readable (non-transitory) storage medium may store at least one computer program including instructions that, when executed by the at least one processor, cause the at least one processor to perform operations according to some implementations of this disclosure. A computer program or computer program product may include instructions stored on at least one computer-readable (non-volatile) storage medium and, when executed, cause (at least one processor) to perform operations according to some implementations of this disclosure.

[0289] For the UE, processing apparatus, computer-readable (non-volatile) storage medium, and / or computer program product, the operation may include: determining a first transmission time of a first HARQ-ACK for a first DL channel associated with a first HARQ process; and receiving a second DL channel associated with the first HARQ process. Receiving the second DL channel of the first HARQ process may include: receiving the second DL channel after the first transmission time based on the first HARQ-ACK not being subject to HARQ delay; and receiving the second DL channel after the second transmission time based on the first HARQ-ACK being subject to HARQ delay and the first transmission time being determined by HARQ delay from a second transmission time earlier than the first transmission time.

[0290] In some implementations, the second DL channel can be received before the end of the first transmission time, based on the first HARQ-ACK undergoing HARQ delay and the first transmission time being determined by HARQ delay from the second transmission time.

[0291] In some implementations, the first DL channel can be an SPS-based PDSCH.

[0292] In some implementations, the second DL channel can be used for retransmission of TBs included in the SPS-based PDSCH.

[0293] In some implementations, the second DL channel can be based on a dynamically scheduled PDSCH.

[0294] In some implementations, the operation may include: determining a third transmission time for the second HARQ-ACK of the second DL channel; abandoning the transmission of the first HARQ-ACK within a first transmission time; and transmitting the second HARQ-ACK at the third transmission time.

[0295] To transmit the DL channel, the BS may perform operations according to some implementations of this disclosure. The BS may include: at least one transceiver; at least one processor; and at least one computer memory operatively connected to the at least one processor and configured to store instructions that, when executed, cause the at least one processor to perform operations according to some implementations of this disclosure. Processing means for the BS may include: at least one processor; and at least one computer memory operatively connected to the at least one processor and configured to store instructions that, when executed, cause the at least one processor to perform operations according to some implementations of this disclosure. A computer-readable (non-transitory) storage medium may store at least one computer program including instructions that, when executed by the at least one processor, cause the at least one processor to perform operations according to some implementations of this disclosure. A computer program or computer program product may include instructions stored on at least one computer-readable (non-volatile) storage medium and, when executed, cause (at least one processor) to perform operations according to some implementations of this disclosure.

[0296] For a BS, processing apparatus, computer-readable (non-volatile) storage medium, and / or computer program product, the operation may include: determining a first reception time of a first HARQ-ACK for a first DL channel associated with a first HARQ process; and transmitting a second DL channel associated with the first HARQ process. Transmitting the second DL channel for the first HARQ process may include: transmitting the second DL channel after the first reception time based on the first HARQ-ACK not being subject to HARQ delay; and transmitting the second DL channel after the second reception time based on the first HARQ-ACK being subject to HARQ delay and the first reception time being determined by HARQ delay from a second reception time earlier than the first reception time.

[0297] In some implementations, based on the first HARQ-ACK undergoing HARQ delay and the first reception time being determined by HARQ delay from the second reception time, the second DL channel can be sent before the end of the first reception time.

[0298] In some implementations, the first DL channel can be an SPS-based PDSCH.

[0299] In some implementations, the second DL channel can be used for retransmission of TBs included in the SPS-based PDSCH.

[0300] In some implementations, the second downlink channel can be based on a dynamically scheduled PDSCH.

[0301] In some implementations, the operation may include: determining a third reception time for the second HARQ-ACK of the second downlink channel; skipping (omitting) the reception of the first HARQ-ACK within a first transmission time; and receiving the second HARQ-ACK at the third reception time.

[0302] Examples of this disclosure as described above have been presented to enable those skilled in the art to implement and practice this disclosure. Although the disclosure is described with reference to examples, various modifications and variations can be made to the examples of this disclosure by those skilled in the art. Therefore, this disclosure is not intended to be limited to the examples set forth herein, but is to be accorded the widest scope consistent with the principles and features disclosed herein.

[0303] Industrial applicability

[0304] Implementations of this disclosure can be used in BS, UE, or other devices in wireless communication systems.

Claims

1. A method for a user equipment (UE) to receive a downlink channel in a wireless communication system, the method comprising the following steps: During the first reception time, the first physical downlink shared channel (PDSCH) associated with the first HARQ process among multiple Hybrid Automatic Repeat Request (HARQ) processes is received. In the first transmission time, send the first HARQ-ACK of the first PDSCH associated with the first HARQ process; as well as During the second reception time, a second PDSCH with the same HARQ process identifier ID as the first HARQ process of the first PDSCH is received. The second PDSCH, which has the same HARQ process ID as the first HARQ process of the first PDSCH, is a PDSCH scheduled via downlink control information (DCI). The step of receiving the second PDSCH with the same HARQ process ID as the first HARQ process of the first PDSCH includes the following steps: Based on the fact that the first HARQ-ACK is not subject to HARQ delay, the second PDSCH with the same HARQ process ID as the first HARQ process of the first PDSCH is received in the second reception time after the first transmission time; and Based on the first HARQ-ACK undergoing the HARQ delay and the first transmission time being determined by delaying the HARQ from a second transmission time earlier than the first transmission time, the second PDSCH is received in the second reception time after the second transmission time, with the same HARQ process ID as the first HARQ process of the first PDSCH.

2. The method according to claim 1, wherein, Based on the first HARQ-ACK undergoing the HARQ delay and the first transmission time being determined by the HARQ delay from the second transmission time, the second PDSCH with the same HARQ process ID as the first PDSCH is received in the second reception time before the end of the first transmission time and after the second transmission time.

3. The method according to claim 2, wherein, The first PDSCH is a PDSCH based on semi-persistent scheduling (SPS).

4. The method according to claim 3, wherein, The PDSCH is used for retransmission of transport blocks included in the SPS-based PDSCH.

5. The method according to claim 2, further comprising the following steps: The third transmission time of the second HARQ-ACK of the PDSCH with the same HARQ process ID as the first HARQ process of the first PDSCH; and The second HARQ-ACK is sent at the third transmission time.

6. A user equipment (UE) for receiving a downlink channel in a wireless communication system, the UE comprising: At least one transceiver; At least one processor; as well as At least one computer memory, operatively connected to the at least one processor and configured to store instructions, which, when executed, cause the at least one processor to perform operations including: During the first reception time, the first physical downlink shared channel (PDSCH) associated with the first HARQ process among multiple Hybrid Automatic Repeat Request (HARQ) processes is received. In the first transmission time, send the first HARQ-ACK of the first PDSCH associated with the first HARQ process; and During the second reception time, a second PDSCH with the same HARQ process identifier ID as the first HARQ process of the first PDSCH is received. The second PDSCH, which has the same HARQ process ID as the first HARQ process of the first PDSCH, is a PDSCH scheduled via downlink control information (DCI). The operation of receiving the second PDSCH with the same HARQ process ID as the first HARQ process of the first PDSCH includes: Based on the fact that the first HARQ-ACK is not subject to HARQ delay, the second PDSCH with the same HARQ process ID as the first HARQ process of the first PDSCH is received in the second reception time after the first transmission time; and Based on the first HARQ-ACK undergoing the HARQ delay and the first transmission time being determined by delaying the HARQ from a second transmission time earlier than the first transmission time, the second PDSCH is received in the second reception time after the second transmission time, with the same HARQ process ID as the first HARQ process of the first PDSCH.

7. A processing apparatus in a wireless communication system, the processing apparatus comprising: At least one processor; as well as At least one computer memory, operatively connected to the at least one processor and configured to store instructions, which, when executed, cause the at least one processor to perform operations including: During the first reception time, the first physical downlink shared channel (PDSCH) associated with the first HARQ process among multiple Hybrid Automatic Repeat Request (HARQ) processes is received. In the first transmission time, send the first HARQ-ACK of the first PDSCH associated with the first HARQ process; and During the second reception time, a second PDSCH with the same HARQ process identifier ID as the first HARQ process of the first PDSCH is received. The second PDSCH, which has the same HARQ process ID as the first HARQ process of the first PDSCH, is a PDSCH scheduled via downlink control information (DCI). The operation of receiving the second PDSCH with the same HARQ process ID as the first HARQ process of the first PDSCH includes: Based on the fact that the first HARQ-ACK is not subject to HARQ delay, the second PDSCH with the same HARQ process ID as the first HARQ process of the first PDSCH is received in the second reception time after the first transmission time; and Based on the first HARQ-ACK undergoing the HARQ delay and the first transmission time being determined by delaying the HARQ from a second transmission time earlier than the first transmission time, the second PDSCH is received in the second reception time after the second transmission time, with the same HARQ process ID as the first HARQ process of the first PDSCH.

8. A computer-readable storage medium storing at least one program code, which, when executed, causes at least one processor to perform operations, said operations including: During the first reception time, the first physical downlink shared channel (PDSCH) associated with the first HARQ process among multiple Hybrid Automatic Repeat Request (HARQ) processes is received. In the first transmission time, send the first HARQ-ACK of the first PDSCH associated with the first HARQ process; as well as During the second reception time, a second PDSCH with the same HARQ process identifier ID as the first HARQ process of the first PDSCH is received. The second PDSCH, which has the same HARQ process ID as the first HARQ process of the first PDSCH, is a PDSCH scheduled via downlink control information (DCI). The operation of receiving the second PDSCH with the same HARQ process ID as the first HARQ process of the first PDSCH includes: Based on the fact that the first HARQ-ACK is not subject to HARQ delay, the second PDSCH with the same HARQ process ID as the first HARQ process of the first PDSCH is received in the second reception time after the first transmission time; and Based on the first HARQ-ACK undergoing the HARQ delay and the first transmission time being determined by delaying the HARQ from a second transmission time earlier than the first transmission time, the second PDSCH is received in the second reception time after the second transmission time, with the same HARQ process ID as the first HARQ process of the first PDSCH.

9. A computer program product comprising a computer program that, when executed, causes at least one processor to perform operations, the operations including: Determine the first HARQ-ACK transmission time for the first downlink channel associated with the first Hybrid Automatic Repeat Request (HARQ) process; as well as During the first reception time, the first physical downlink shared channel (PDSCH) associated with the first HARQ process among multiple Hybrid Automatic Repeat Request (HARQ) processes is received. In the first transmission time, send the first HARQ-ACK of the first PDSCH associated with the first HARQ process; as well as During the second reception time, a second PDSCH with the same HARQ process identifier ID as the first HARQ process of the first PDSCH is received. The second PDSCH, which has the same HARQ process ID as the first HARQ process of the first PDSCH, is a PDSCH scheduled via downlink control information (DCI). The operation of receiving the second PDSCH with the same HARQ process ID as the first HARQ process of the first PDSCH includes: Based on the fact that the first HARQ-ACK is not subject to HARQ delay, the second PDSCH with the same HARQ process ID as the first HARQ process of the first PDSCH is received in the second reception time after the first transmission time; and Based on the first HARQ-ACK undergoing the HARQ delay and the first transmission time being determined by delaying the HARQ from a second transmission time earlier than the first transmission time, the second PDSCH is received in the second reception time after the second transmission time, with the same HARQ process ID as the first HARQ process of the first PDSCH.

10. A method for transmitting a downlink channel from a base station (BS) to a user equipment (UE) in a wireless communication system, the method comprising the following steps: During the first transmission time, the first physical downlink shared channel (PDSCH) associated with the first HARQ process among the multiple Hybrid Automatic Repeat Request (HARQ) processes is transmitted. In the first reception time, send the first HARQ-ACK of the first PDSCH associated with the first HARQ process; and In the second transmission time, a second PDSCH with the same HARQ process identifier ID as the first HARQ process in the first PDSCH is transmitted. The second PDSCH, which has the same HARQ process ID as the first HARQ process of the first PDSCH, is a PDSCH scheduled via downlink control information (DCI). The step of sending the second PDSCH with the same HARQ process ID as the first HARQ process in the first PDSCH includes the following steps: Based on the fact that the first HARQ-ACK is not subject to HARQ delay, a second PDSCH with the same HARQ process ID as the first HARQ process of the first PDSCH is transmitted in the second transmission time after the first reception time; and Based on the first HARQ-ACK undergoing the HARQ delay and the first reception time being determined by the HARQ delay from a second reception time earlier than the first reception time, a second PDSCH with the same HARQ process ID as the first HARQ process of the first PDSCH is transmitted in a second transmission time after the second reception time.

11. The method according to claim 10, wherein, Based on the first HARQ-ACK undergoing the HARQ delay and the first reception time being determined by the HARQ delay from the second reception time, a second PDSCH with the same HARQ process ID as the first HARQ process of the first PDSCH is transmitted in a second transmission time before the end of the first reception time and after the second reception time.

12. The method according to claim 11, wherein, The first PDSCH is a PDSCH based on semi-persistent scheduling (SPS).

13. The method according to claim 12, wherein, The second PDSCH with the same HARQ process ID as the first HARQ process of the first PDSCH is used for retransmission of transport blocks included in the SPS-based PDSCH.

14. The method of claim 11, further comprising the step of: The third reception time of the second HARQ-ACK of the PDSCH is determined to be the same as the HARQ process ID of the first HARQ process of the first PDSCH; and The second HARQ-ACK is received at the third receiving time.

15. A base station (BS) in a wireless communication system for transmitting a downlink channel to a user equipment (UE), the BS comprising: At least one transceiver; At least one processor; as well as At least one computer memory, operatively connected to the at least one processor and configured to store instructions, which, when executed, cause the at least one processor to perform operations including: During the first transmission time, the first physical downlink shared channel (PDSCH) associated with the first HARQ process among the multiple Hybrid Automatic Repeat Request (HARQ) processes is transmitted. In the first reception time, send the first HARQ-ACK of the first PDSCH associated with the first HARQ process; and In the second transmission time, a second PDSCH with the same HARQ process identifier ID as the first HARQ process in the first PDSCH is transmitted. The second PDSCH, which has the same HARQ process ID as the first HARQ process of the first PDSCH, is a PDSCH scheduled via downlink control information (DCI). The operation of sending the second PDSCH with the same HARQ process ID as the first HARQ process that sends the first PDSCH includes: Based on the fact that the first HARQ-ACK is not subject to HARQ delay, a second PDSCH with the same HARQ process ID as the first HARQ process of the first PDSCH is transmitted in the second transmission time after the first reception time; and Based on the first HARQ-ACK undergoing the HARQ delay and the first reception time being determined by the HARQ delay from a second reception time earlier than the first reception time, a second PDSCH with the same HARQ process ID as the first HARQ process of the first PDSCH is transmitted in a second transmission time after the second reception time.

Images