Method of transmitting an uplink channel, user equipment, processing device, storage medium and computer program, and method of receiving an uplink channel and base station

Abstract

A UE: based on a first PUCCH and a second PUCCH having a priority lower than that of the first PUCCH overlapping each other in time, and the first PUCCH satisfying a first time condition, performing transmission of the first PUCCH and cancelling transmission of the second PUCCH; and based on a first PUSCH and a second PUSCH having a priority lower than that of the first PUSCH overlapping each other in time, and the first PUSCH satisfying a second time condition, performing transmission of the first PUSCH and cancelling transmission of the second PUSCH, wherein a time length T_B of the second time condition is longer than a time length T_A of the first time condition.

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

[0010] Technical solution

[0011] In one aspect of this disclosure, a method is provided for a user equipment (UE) to transmit an uplink channel in a wireless communication system. The method may include the following steps: based on the time overlap of a first physical uplink control channel (PUCCH) and a second PUCCH having a lower priority than the first PUCCH, and the first PUCCH satisfying a first time condition, transmitting the first PUCCH and canceling the transmission of the second PUCCH; and based on the time overlap of a first physical uplink shared channel (PUSCH) and a second PUSCH having a lower priority than the first PUSCH, and the first PUSCH satisfying a second time condition, transmitting the first PUSCH and canceling the transmission of the second PUSCH. The duration T_B of the second time condition may be longer than the duration T_A of the first time condition.

[0012] In another aspect of this disclosure, a UE configured to transmit an uplink channel in a wireless communication system is provided. 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: transmitting the first PUCCH and canceling the transmission of the second PUCCH based on a time overlap between a first PUCCH and a second PUCCH having a lower priority than the first PUCCH, and the first PUCCH satisfying a first time condition; and transmitting the first PUSCH and canceling the transmission of the second PUSCH based on a time overlap between a first PUSCH and a second PUSCH having a lower priority than the first PUSCH, and the first PUSCH satisfying a second time condition. The duration T_B of the second time condition may be longer than the duration T_A of the first time condition.

[0013] 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: transmitting the first PUCCH and canceling the transmission of the second PUCCH based on a time overlap between a first PUCCH and a second PUCCH having a lower priority than the first PUCCH, and the first PUCCH satisfying a first time condition; and transmitting the first PUSCH and canceling the transmission of the second PUSCH based on a time overlap between a first PUSCH and a second PUSCH having a lower priority than the first PUSCH, and the first PUSCH satisfying a second time condition. The duration T_B of the second time condition may be longer than the duration T_A of the first time condition.

[0014] 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: transmitting the first PUCCH and canceling the transmission of the second PUCCH based on a time overlap between a first PUCCH and a second PUCCH having a lower priority than the first PUCCH, and the first PUCCH satisfying a first time condition; and transmitting the first PUSCH and canceling the transmission of the second PUSCH based on a time overlap between a first PUSCH and a second PUSCH having a lower priority than the first PUSCH, and the first PUSCH satisfying a second time condition. The duration T_B of the second time condition may be longer than the duration T_A of the first time condition.

[0015] 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 an operation. The operation may include: transmitting the first PUCCH and canceling the transmission of the second PUCCH based on a time overlap between a first PUCCH and a second PUCCH having a lower priority than the first PUCCH, and the first PUCCH satisfying a first timing condition; and transmitting the first PUSCH and canceling the transmission of the second PUSCH based on a time overlap between a first PUSCH and a second PUSCH having a lower priority than the first PUSCH, and the first PUSCH satisfying a second timing condition. The duration T_B of the second timing condition may be longer than the duration T_A of the first timing condition.

[0016] In another aspect of this disclosure, a method is provided for a base station (BS) to receive an uplink channel from a user equipment (UE) in a wireless communication system. The method may include the following steps: based on the time overlap of a first PUCCH and a second PUCCH having a lower priority than the first PUCCH, and the first PUCCH satisfying a first time condition, receiving the first PUCCH and canceling the reception of the second PUCCH; and based on the time overlap of a first PUSCH and a second PUSCH having a lower priority than the first PUSCH, and the first PUSCH satisfying a second time condition, receiving the first PUSCH and canceling the reception of the second PUSCH. The duration T_B of the second time condition may be longer than the duration T_A of the first time condition.

[0017] In another aspect of this disclosure, a BS configured to receive an uplink channel from 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: receiving the first PUCCH and canceling the reception of the second PUCCH based on a time overlap between a first PUCCH and a second PUCCH having a lower priority than the first PUCCH, and the first PUCCH satisfying a first time condition; and receiving the first PUSCH and canceling the reception of the second PUSCH based on a time overlap between a first PUSCH and a second PUSCH having a lower priority than the first PUSCH, and the first PUSCH satisfying a second time condition. The duration T_B of the second time condition may be longer than the duration T_A of the first time condition.

[0018] In all respects of this disclosure, the time length T_B can be d longer than the time length T_A. add , and d add This could be the additional processing time reported by the UE to the BS.

[0019] In all aspects of this disclosure, regarding d add Information can be provided to the UE by the BS.

[0020] In all respects of this disclosure, the time length T_B can be d longer than the time length T_A. add .

[0021] In all aspects of this disclosure, based on the fact that the first PUCCH, which overlaps with the second PUCCH in time, satisfies a first time condition but does not satisfy a second time condition, the uplink control information (UCI) included in the second PUCCH is multiplexed onto the first PUCCH.

[0022] In various aspects of this disclosure, the first timing condition may include a time distance from the last symbol of the physical downlink control channel (PDCCH) that schedules the higher priority uplink channel to the start of the higher priority uplink channel that is greater than or equal to T_A = T_proc,2 + d1, where T_proc,2 is the PUSCH preparation time of the UE's processing capability, and d1 is determined by the capability reported by the UE.

[0023] In various aspects of this disclosure, the second timing condition may include a time distance from the last symbol of the PDCCH to the start of the higher priority uplink channel that is greater than or equal to T_B = T_proc,2+d1+d add , where d add >0.

[0024] In various aspects of this disclosure, based on the time overlap between the third PUCCH and the fourth PUSCH, which has a lower priority than the third PUCCH, and the third PUCCH satisfying a first time condition, the transmission of the third PUCCH can be performed, and the transmission of the fourth PUSCH can be cancelled.

[0025] In various aspects of this disclosure, based on the time overlap between the third PUSCH and the fourth PUCCH having a lower priority than the third PUSCH and the third PUSCH satisfying a first time condition, the transmission of the third PUSCH can be performed, and the transmission of the fourth PUCCH can be cancelled.

[0026] In various aspects of this disclosure, based on the fact that the third PUSCH, which overlaps with the fourth PUCCH in time, satisfies a first time condition but does not satisfy a second time condition, the UCI included in the fourth PUCCH can be multiplexed onto the third PUSCH.

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

[0028] Beneficial effects

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

[0030] According to the implementation of this disclosure, various services with different requirements can be effectively supported in a wireless communication system.

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

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

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

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

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

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

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

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

[0039] Figure 6 Examples of PDSCH time-domain resource assignment (TDRA) caused by PDCCH and PUSCH TDRA caused by PDCCH are shown.

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

[0041] Figure 8 This illustrates an example of multiplexing uplink control information (UCI) with PUSCH;

[0042] Figure 9 This illustrates an example of how a UE with overlapping PUCCHs in a single time slot handles conflicts between UL channels.

[0043] Figure 10 Showing based on Figure 9 UCI multiplexing is performed;

[0044] Figure 11 This illustrates how a UE with overlapping PUCCH and PUSCH in a single time slot handles conflicts between UL channels.

[0045] Figure 12 This illustrates UCI multiplexing considering timeline conditions;

[0046] Figure 13 This shows the transmission of multiple HARQ-ACK PUCCHs in a time slot;

[0047] Figure 14 This illustrates conflict scenarios between PUCCHs with different priorities;

[0048] Figure 15 and Figure 16 This illustrates conflict scenarios between PUSCH and PUCCH with different priorities;

[0049] Figure 17 The process of UL channel transmission at the UE according to some implementations of this disclosure is illustrated;

[0050] Figure 18 This illustrates the flow of UL channel reception at the BS according to some implementations of this disclosure; and

[0051] Figure 19 The diagram illustrates the signal transmission / reception flow between the UE and BS according to some implementations of this disclosure. Detailed Implementation

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0068] In this disclosure, PDCCH refers to the time-frequency resource set (e.g., resource element (RE) set) carrying downlink control information (DCI), and PDSCH refers to the time-frequency resource set (e.g., RE set) carrying DL data. PUCCH, PUSCH, and PRACH refer to the time-frequency resource sets (i.e., RE sets) 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. Additionally, "BS transmits / receives PBCH / PDCCH / PDSCH" means that the BS transmits broadcast information / DCI / DL data on or through PBCH / PDCCH / PDSCH.

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

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

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

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

[0073] Wireless devices 100a to 100f can connect to network 300 via BS 200. 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 BS 200 / 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.

[0074] Wireless communication / connections 150a and 150b can be established between wireless devices 100a to 100f and BS 200, as well as 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.

[0075] 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 100 and the second wireless 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 BS 200} and / or {Wireless Device 100x and Wireless Device 100x}.

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

[0077] 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 above / below. For example, the processors 202 may process information in the memories 204 to generate a third message / signal, and then transmit a radio signal including the third message / signal via the transceivers 206. The processors 202 may receive a radio signal including a fourth message / signal via the transceivers 206, and then store the information obtained by processing the fourth message / 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 above / 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.

[0078] 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 communication. For example, NB-IoT technology may be an example of low-power wide-area network (LPWAN) technology and may be implemented via (but not limited to) standards such as LTE Cat NB1 and / or LTE Cat NB2. 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 may be referred to by various names such as Enhanced Machine-Type Communication (eMTC). For example, LTE-M technology may be implemented via (but not limited to) at least one of various standards, such as: 1) LTE Cat 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-bandwidth limited), 5) LTE-MTC, 6) LTE Machine-Type Communication, and / or 7) LTE M. Additionally or alternatively, considering low-power communication, the wireless communication technologies implemented in the wireless devices XXX and YYY of this disclosure may include (but are not limited to) at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN). For example, ZigBee technology may be based on various standards such as IEEE 802.15.4 to create personal area networks (PANs) related to small / low-power digital communication, and may be referred to by various names.

[0079] 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, procedures, proposals, and / or methods disclosed in this document. One or more processors 102 and 202 may generate messages, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in this document. 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 document, 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 document.

[0080] 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 document 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 document 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 document may be implemented using firmware or software in the form of code, commands, and / or sets of commands.

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

[0082] 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 document 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 document 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 document via one or more antennas 108 and 208. In this document, 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 by 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.

[0083] 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 130, and an additional component 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 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.

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

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

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

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

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

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

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

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

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

[0093] 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...sf The 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， slot ).

[0094] [Table 1]

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

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

[0097] [Table 2]

[0098] u <![CDATA[N slot symb ]]> <![CDATA[N rame,u slot ]]> <![CDATA[N subframe，u slot ]]> 2 12 40 4

[0099] For the subcarrier spacing configuration u, the time slots can be indexed in ascending order within the subframe as follows: nus∈{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}.

[0100] 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 Ns ubframe，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 Ns of the subcarrier spacing configuration u is given to the UE via higher-layer parameters (e.g., RRC parameters). ize，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 = u C RB +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.

[0101] 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 The length LRB is provided by the RRC parameter locationAndBandwidth as the resource indicator value (RIV) and the CRB N. start BWP =O carrier +RB start And the number of adjacent RBs N 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.

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

[0103] A UE configured with carrier aggregation can be configured to use one or more cells. If the UE is configured with multiple serving cells, it 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 ​​configured as a PUCCH cell within the corresponding cell group. Each serving cell of the UE belongs to one of the UE's cell groups and does not belong to multiple cells.

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

[0105] [Table 3]

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

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

[0108] 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 including information about the resource allocation of the DL-SCH is called the PDSCH scheduling DCI, and the DCI including information about the resource allocation of 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).

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

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

[0111] PUCCH stands for Physical Layer UL Channel used for UCI transmission. PUCCH carries UCI. UCI includes the following information.

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

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

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

[0115] 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 CSI PUCCH resources, respectively.

[0116] 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 4 for further information on the PUCCH format.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0143] [Table 4]

[0144]

[0145] The 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 N UCI from one of the following PUCCH resource sets.

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

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

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

[0150] 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 format 0 to 1, and other PUCCH resource sets can include resources of PUCCH format 2 to 4 (see Table 4).

[0151] The configuration of each PUCCH resource includes the PUCCH resource index, the starting PRB index, and the configuration of one of PUCCH format 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.

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

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

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

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

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

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

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

[0159] PDCCH can be used to schedule DL transmissions on PDSCH and UL transmissions on PUSCH. The DCI on the PDCCH used for scheduling DL transmissions may include DL resource assignment, which includes at least the modulation and coding format (e.g., Modulation and Coding Scheme (MCS)) index IMCS associated with the DL-SCH, resource allocation, and HARQ information. The DCI on the PDCCH used for scheduling UL transmissions may include UL scheduling permission, which includes at least the modulation and coding format associated with the UL-SCH, resource allocation, and HARQ information. HARQ information regarding 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 DCI format 0_2. Some implementations of this disclosure can be applied to DL data reception based on DCI format 1_2.

[0160] Figure 6 Examples of PDSCH TDRA caused by PDCCH and PUSCH TDRA caused by PDCCH are shown.

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

[0162] 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. The PDSCH / PUSCH mapping type has two mapping types: Mapping Type A and Mapping Type B. In PDSCH / PUSCH mapping type A, the demodulation reference signal (DMRS) is mapped to the PDSCH / PUSCH resource based on 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 PDSCH / PUSCH mapping type A, the DMRS is located on the third symbol (symbol #2) or the fourth symbol (symbol #3) in the time slot, according to RRC signaling. In PDSCH / PUSCH mapping type B, the DMRS is mapped based on 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 PDSCH / PUSCH mapping type B, the DMRS is located on 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.

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

[0164] Resource allocation via RRC

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

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

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

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

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

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

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

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

[0173] When configuring configuration license type 1 for a 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 begin with a symbol based on timeDomainOffset and S (derived from SLIV) and repeat with periodicity. After configuring the UL license for configuration license type 1, the UE can consider the UL license to be associated with repeated symbols satisfying 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*

[0174] 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 (see Tables 1 and 2).

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

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

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

[0178] 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 开始时间 slot 开始时间 and symbol 开始时间 These represent the SFN, slot, and symbol of the first transmission opportunity of the PUSCH after the configuration permission is (re)initialized. 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).

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

[0180] 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 following parameters to the UE via RRC signaling used to configure semi-persistent transmission:

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

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

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

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

[0185] After configuring DL assignment for SPS, the UE can 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).

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

[0187] 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 DL SPS assignment PDCCH verification or configures the UL license type 2 PDCCH. If all fields of the DCI format are set according to Tables 5 and 6, then DCI format verification is implemented. Table 5 shows examples of special fields for enabling PDCCH verification for DL ​​SPS and UL license type 2 scheduling, and Table 6 shows examples of special fields for releasing PDCCH verification for DL ​​SPS and UL license type 2 scheduling.

[0188] [Table 5]

[0189]

[0190] [Table 6]

[0191] 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"

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

[0193] Figure 7 This illustrates the HARQ-ACK sending / receiving process.

[0194] Reference Figure 7 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.

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

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

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

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

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

[0200] 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 a semi-static HARQ-ACK codebook and a dynamic HARQ-ACK codebook.

[0201] 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. In the case of a dynamic HARQ-ACK codebook, the size of the HARQ-ACK payload to be reported by the UE can be dynamically changed via DCI, etc. In a dynamic HARQ-ACK codebook scheme, the DL scheduling DCI can include counter-DAI (i.e., c-DAI) and / or total-DAI (i.e., t-DAI).Here, DAI indicates the downlink assignment index and is used by the BS to inform the UE to include the PDSCH of its HARQ-ACK in a HARQ-ACK transmission sent or scheduled. Specifically, c-DAI is an index indicating the order among PDCCHs carrying DL-scheduled DCIs (hereinafter, DL-scheduled PDCCHs), and t-DAI is an index indicating the total number of DL-scheduled PDCCHs up to the current timeslot with a PDCCH having t-DAI.

[0202] In NR systems, a method is considered for implementing multiple logical networks within a single physical network. These logical networks need to support services with various requirements (e.g., eMBB, mMTC, URLLC, etc.). Therefore, the physical layer of NR is designed to support flexible transmission architectures, taking into account the diverse service requirements. As an example, the physical layer of NR can change the OFDM symbol length (OFDM symbol duration) and subcarrier spacing (SCS) (hereinafter, the OFDM parameter set) if needed. The transmission resources of the physical channels can also be varied within a predetermined range (in symbols). For example, in NR, PUCCH (resources) and PUSCH (resources) can be configured flexibly with transmission lengths / transmission start timings within a predetermined range.

[0203] PDCCH is transmitted via a control resource set (CORESET). One or more CORESETs can be configured for the UE. A CORESET consists of a set of PRBs with a duration of 1 to 3 OFDM symbols. The PRBs constituting the CORESET and the CORESET duration can be provided to the UE via higher-layer (e.g., RRC) signaling. The set of PDCCH candidates in the configured CORESET is monitored according to the corresponding search space set. In this disclosure, monitoring means decoding each PDCCH candidate according to the monitored DCI format (referred to as blind decoding). The Master Information Block (MIB) on the PBCH provides the UE with parameters (e.g., CORESET#0 configuration) for monitoring the PDCCH used to schedule the PDSCH of bearer System Information Block 1 (SIB1). The PBCH may also indicate that there is no associated SIB1. In this case, not only can the frequency range in which the UE can assume that there is no SSB associated with SSB1 be provided, but other frequencies for searching for SSBs associated with SIB1 can also be provided. As a CORESET used at least for scheduling SIB1, CORESET#0 can be configured by the MIB or dedicated RRC signaling.

[0204] The set of PDCCH candidates monitored by the UE is defined based on the PDCCH search space set. The search space set can be a common search space (CSS) set or a UE-specific search space (USS) set. Each CORESET configuration is associated with one or more search space sets, and each search space set is associated with a CORESET configuration. The search space set is determined based on the following parameters provided to the UE by the BS.

[0205] -controlResourceSetId: An identifier used to identify the CORESET p associated with the search space set s.

[0206] -monitoringSlotPeriodicityAndOffset: time slot k s PDCCH monitoring periodicity and o s The PDCCH monitoring offset for each time slot is configured to be used for PDCCH monitoring.

[0207] -duration:T s <k s The duration of each time slot indicates the number of time slots for which a search space set s exists.

[0208] -monitoringSymbolsWithinSlot: PDCCH monitoring pattern within a slot, indicating the first symbol of the CORESET within the slot used for PDCCH monitoring.

[0209] -nrofCandidates: The number of PDCCH candidates per CCE aggregation level.

[0210] -searchSpaceType: Indicates whether the search space set s is a CCE set or a USS set.

[0211] The parameter `monitoringSymbolsWithinSlot` indicates the first symbol in the time slot configured for PDCCH monitoring (see, for example, `monitoringSlotPeriodicityAndOffset` and `duration`). For instance, when `monitoringSymbolsWithinSlot` is a 14-bit parameter, the most significant (leftmost) bit represents the first OFDM symbol in the time slot, and the second most significant (leftmost) bit represents the second OFDM symbol. Thus, the bits in `monitoringSymbolsWithinSlot` can represent the 14 OFDM symbols in the time slot. For example, a bit set to 1 in `monitoringSymbolsWithinSlot` identifies the first symbol in the CORESET of the time slot.

[0212] The UE monitors PDCCH candidates only during PDCCH monitoring periods. The UE determines the monitoring period on the active DL BWP from the PDCCH monitoring pattern, PDCCH monitoring offset, and PDCCH monitoring periodicity within the time slot. In some implementations, for the search space set s, if (n f *N frame,u slot +n u s,f -o s )mod k s =0, then UE is determined to exist at number n f The frame numbered n u s,f The PDCCH monitoring timing within time slot n. The UE monitors the PDCCH within time slot n. u s,f Beginning with T s The PDCCH candidates are searched in a continuous time-slot monitoring space set s, and for the next k s -T s PDCCH candidates for the search space set s are not monitored.

[0213] The following table shows the search space set, the relevant RNTIs, and their usage.

[0214] [Table 7]

[0215]

[0216] The following shows the DCI format carried by PDCCH.

[0217] [Table 8]

[0218]

[0219] DCI format 0_0 can be used to schedule TB-based (or TB-level) PUSCH, and DCI format 0_1 ​​can be used to schedule TB-based (or TB-level) PUSCH or code block group (CBG)-based (or CBG-level) PUSCH. DCI format 1_0 can be used to schedule TB-based (or TB-level) PDSCH, and DCI format 1_1 can be used to schedule TB-based (or TB-level) PDSCH or CBG-based (or CBG-level) PDSCH. For CSS, DCI formats 0_0 and 1_0 have fixed sizes after the BWP size is initially given via RRC. For USS, the sizes of DCI formats 0_0 and 1_0 are fixed in fields other than the Frequency Domain Resource Assignment (FDRA) field, while the size of the FDRA field can be varied through relevant BS parameter configurations. In DCI formats 0_1 and 1_1, the size of the DCI field can be changed through various BS RRC reconfigurations. DCI format 2_0 can be used to provide dynamic timeslot format information (e.g., SFI DCI) to the UE, DCI format 2_1 can be used to provide DL preemption information to the UE, and DCI format 2_4 can be used to indicate to the UE that UL resources need to be canceled for UL transmission.

[0220] In a wireless communication system including a BS and a UE, when a UE transmits a UCI on a PUCCH, the PUCCH resource may overlap with another PUCCH resource or PUSCH resource on the time axis. For example, (1) PUCCH (resource) and PUCCH (resource) (for different UCI transmissions) or (2) PUCCH (resource) and PUSCH (resource) may overlap on the time axis (in the same time slot) for the same UE. The UE may not support simultaneous PUCCH-PUCCH transmission or simultaneous PUCCH-PUSCH transmission (depending on the limitations on the UE's capabilities or the configuration information received from the BS). In addition, the UE may not be allowed to transmit multiple UL channels simultaneously within a predetermined time range.

[0221] This disclosure describes a method for handling multiple UL channels when a UE should transmit a UL channel within a predetermined time range. This disclosure also describes a method for handling UCI and / or data that should have been transmitted / received on the UL channels. The following terminology is used in the description of examples in this disclosure.

[0222] -UCI: UCI refers to the control information transmitted by the UE on the UL. UCI includes various types of control information (i.e., UCI types). For example, UCI may include HARQ-ACK (abbreviated as A / N or AN), SR and / or CSI.

[0223] - UCI Multiplexing: UCI multiplexing can refer to the operation of transmitting different UCIs (UCI types) on a common physical UL channel (e.g., PUCCH or PUSCH). UCI multiplexing can include the multiplexing of different UCIs (UCI types). For convenience, the multiplexed UCI is referred to as MUX UCI. Furthermore, UCI multiplexing can include operations performed regarding MUX UCIs. For example, UCI multiplexing can include the process of determining UL channel resources for transmitting MUX UCIs.

[0224] - UCI / Data Multiplexing: UCI / data multiplexing can refer to the operation of transmitting UCI and data on a common physical UL channel (e.g., PUSCH). UCI / data multiplexing may include the operation of multiplexing UCI with data. For convenience, the multiplexed UCI / data is referred to as MUX UCI / data. Furthermore, UCI / data multiplexing may include operations performed regarding MUX UCI / data. For example, UCI / data multiplexing may include the process of determining UL channel resources for transmitting MUX UCI / data.

[0225] - Time Slot: A time slot refers to a basic unit of time or time interval used for data scheduling. A time slot consists of multiple symbols. Here, the symbols can be OFDM-based symbols (e.g., CP-OFDM symbols or DFT-s-OFDM symbols).

[0226] - Overlapping UL Channel Resources: Overlapping UL channel resources refer to UL channel (e.g., PUCCH or PUSCH) resources that overlap with each other (at least partially) on the time axis within a predetermined time period (e.g., time slot). Overlapping UL channel resources may refer to UL channel resources prior to the performance of UCI multiplexing. In this disclosure, UL channels that overlap (at least partially) on the time axis are referred to as UL channels that conflict in time or in the time domain.

[0227] Figure 8 An example of multiplexing UCI with PUSCH is shown. When PUCCH and PUSCH resources overlap in a time slot and simultaneous PUCCH-PUSCH transmission is not configured, UCI can be transmitted on the PUSCH as shown. Transmission of UCI on the PUSCH is called UCI piggybacking or PUSCH piggybacking. Specifically, Figure 8 This shows the case where HARQ-ACK and CSI are carried on the PUSCH resource.

[0228] When multiple UL channels overlap within a predetermined time interval, it is necessary to specify the method for the UE to handle the UL channels so that the BS can correctly receive the UL channels. The method for handling conflicts between UL channels will be described below.

[0229] Figure 9An example is shown of how a UE with overlapping PUCCHs in a single time slot handles conflicts between UL channels.

[0230] To transmit UCIs, the UE can determine PUCCH resources for each UCI. Each PUCCH resource can be defined by a start symbol and a transmission interval. When PUCCH resources used for PUCCH transmission overlap in a single time slot, the UE can perform UCI multiplexing based on the PUCCH resource with the earliest start symbol. For example, the UE can determine (temporally) overlapping PUCCH resources (hereinafter, PUCCH resource B) based on the PUCCH resource with the earliest start symbol in the time slot (hereinafter, PUCCH resource A) (S901). The UE can apply UCI multiplexing rules to PUCCH resource A and PUCCH resource B. For example, based on UCI A of PUCCH resource A and UCI B of PUCCH resource B, a MUX UCI including all or part of UCI A and UCI B can be obtained according to the UCI multiplexing rules. To multiplex the UCIs associated with PUCCH resource A and PUCCH resource B, the UE can determine a single PUCCH resource (hereinafter, MUX PUCCH resource) (S903). For example, the UE determines a PUCCH resource set (hereinafter, PUCCH resource set X) that corresponds to the payload size of the MUX UCI within the PUCCH resource set configured for or available to the UE, and identifies one of the PUCCH resources belonging to PUCCH resource set X as the MUX PUCCH resource. For example, using the PUCCH resource indicator field in the last DCI of a DCI that has a PDSCH to HARQ feedback timing indicator field indicating that the same time slot is used for PUCCH transmission, the UE can identify one of the PUCCH resources belonging to PUCCH resource set X as the MUX PUCCH resource. The UE can determine the total number of PRBs for the MUX PUCCH resource based on the payload size of the MUX UCI and the maximum bit rate of the PUCCH format of the MUX PUCCH resource. If the MUX PUCCH resource overlaps with other PUCCH resources (other than PUCCH resource A and PUCCH resource B), the UE can perform the above operation again based on the MUX PUCCH resource (or the PUCCH resource with the earliest start symbol among the other PUCCH resources including the MUX PUCCH resource).

[0231] Figure 10 Showing based on Figure 9 The implementation of UCI multiplexing. (See reference...) Figure 10 When multiple PUCCH resources overlap in a time slot, UCI multiplexing can be performed based on the earliest PUCCH resource A (e.g., the PUCCH resource A with the earliest start symbol). Figure 10Cases 1 and 2 illustrate an overlap between a first PUCCH resource and another PUCCH resource. In this case, execution can proceed as if the first PUCCH resource were considered the earliest PUCCH resource A. Figure 9 The processing is as follows. In contrast, Case 3 shows that the first PUCCH resource does not overlap with another PUCCH resource and the second PUCCH resource overlaps with another PUCCH resource. In Case 3, UCI multiplexing is not performed on the first PUCCH resource. Instead, it can be performed when the second PUCCH resource is considered as the earliest PUCCH resource A. Figure 9 The processing. Case 2 shows that the MUX PUCCH resource determined to be a UCI for transmission multiplexing overlaps with another PUCCH resource again. In this case, additional processing can be performed under the condition that the earliest PUCCH resource among the other PUCCH resources including the MUX PUCCH resource (e.g., the PUCCH resource with the earliest start symbol) is regarded as the earliest PUCCH resource A. Figure 9 The processing.

[0232] Figure 11 This illustrates how a UE with overlapping PUCCH and PUSCH in a single time slot handles conflicts between UL channels.

[0233] In order to transmit UCI, the UE may determine the PUCCH resource (S1101). Determining the PUCCH resource for UCI may include determining the MUX PUCCH resource. In other words, the determination of the PUCCH resource for UCI by the UE may include determining the MUX PUCCH resource based on multiple overlapping PUCCHs in the time slot.

[0234] The UE can perform UCI piggybacking on PUSCH resources based on the determined (MUX) PUCCH resources (S1103). For example, when a PUSCH resource exists (on which multiplexing of UCI transmission is allowed), the UE can apply UCI multiplexing rules to the PUCCH resources that overlap with the PUSCH resources (in time). The UE can then transmit UCI on the PUSCH.

[0235] If there is no PUSCH overlapping with the determined PUCCH resource in the time slot, S1103 is omitted, and UCI can be sent on the PUCCH.

[0236] When a determined PUCCH resource overlaps with multiple PUSCHs on the timeline, the UE can multiplex the UCI with one of the PUSCHs. For example, when the UE intends to send a PUSCH to a corresponding serving cell, the UE can multiplex the UCI onto the PUSCH of a specific serving cell (e.g., the serving cell with the smallest serving cell index). When there is more than one PUSCH in a specific serving cell's time slot, the UE can multiplex the UCI onto the earliest PUSCH sent in the time slot.

[0237] Figure 12 This illustrates UCI multiplexing considering timeline conditions. When a UE performs UCI and / or data multiplexing for overlapping PUCCHs and / or PUSCHs on the timeline, the UE may lack processing time for UCI and / or data multiplexing due to the flexible UL timing configuration of the PUCCH or PUSCH. To prevent insufficient processing time for the UE, the two timeline conditions described below (hereinafter, multiplexing timeline conditions) are considered during UCI / data multiplexing for overlapping PUCCHs and / or PUSCHs (on the timeline).

[0238] (1) The last symbol of the PDSCH corresponding to the HARQ-ACK information is received before time T1, starting from the start symbol of the earliest channel among the overlapping PUCCH and / or PUSCH (on the time axis). T1 can be determined based on i) the minimum PDSCH processing time N1 defined according to the UE's processing capability and / or ii) d1,1, which is a predefined integer equal to or greater than 0, based on the position of the scheduling symbol, the PDSCH mapping type, BWP handover, etc.

[0239] For example, T1 can be determined as follows: T1 = (N1 + d 1,1 )*(2048+144)*κ*2 -u *T c N1 is based on u in Tables 9 and 10 for UE processing capabilities #1 and #2 respectively, and μ is the one in (μPDCCH, μPDSCH, μUL) that results in a maximum T1, where μPDCCH corresponds to the subcarrier spacing of the PDCCH used for scheduling PDSCH, μPDSCH corresponds to the subcarrier spacing of the scheduled PDSCH, μUL corresponds to the subcarrier spacing of the UL channel to which HARQ-ACK is to be transmitted, and κ = T. c / T f =64. In Table 9, in N 1,0 In the case where the added DMRS PDSCH DMRS position is l1 = 12, then N 1,0 =14, otherwise, N 1,0=13 (Refer to Section 7.4.1.1.2 of 3GPP TS 38.211). If the last symbol of the PDSCH used for PDSCH mapping type A exists in the i-th time slot, then for i < 7, d 1,1 =7-i, otherwise, d 1,1 =0. If for UE processing capability #1, PDSCH has mapping type B, then when the number of allocated PDSCH symbols is 7, d 1,1 It can be 0 when the number of allocated PDSCH symbols is 4. 1,1 The value can be 3, when the number of allocated PDSCH symbols is 2. 1,1 It can be 3+d, where d is the number of overlapping symbols between the scheduled PDCCH and the scheduled PDSCH. If, for UE processing capability #2, the PDSCH mapping type is B, then when the number of allocated PDSCH symbols is 7, d... 1,1 It can be 0, and d is used when the number of allocated PDSCH symbols is 4. 1,1 This corresponds to the number of overlapping symbols of the scheduled PDCCH and the scheduled PDSCH. Furthermore, if the number of allocated PDSCH symbols is 2, then when the scheduled PDSCH is within a 3-symbol CORESET and the CORESET and PDSCH have the same starting symbol, d... 1,1 It can be 3, and for other cases, d 1,1 This can be the number of overlapping symbols between the scheduled PDCCH and the scheduled PDSCH. In this disclosure, T1 can also be referred to as T_proc,1.

[0240] (2) The last symbol of the PDCCH used to indicate PUCCH or PUSCH transmission (e.g., trigger) is received before time T2, starting from the start symbol of the earliest channel among the overlapping PUCCH and / or PUSCH (on the time axis). T2 may be based on i) the minimum PUSCH preparation time N2 defined according to the UE PUSCH timing capability, and / or ii) a predefined integer d equal to or greater than 0, based on the scheduled symbol position, BWP handover, etc. 2,x To determine. d 2,x d can be categorized as being related to the position of the scheduled symbol. 2,1 and related to BWP handover d 2,2 .

[0241] For example, T2 can be determined as follows: T2 = max{(N2 + d 2,1 )*(2048+144)*κ*2 -u *T c +T ext +T switch ,d 2,2}. N2 is based on u in Tables 11 and 12 for UE timing capabilities #1 and #2 respectively, and μ is the one in (μDL, μUL) that causes the maximum T1, where μ DL The subcarrier spacing μ corresponds to the PDCCH carrying the DCI used for scheduling PUSCH. UL The subcarrier spacing corresponding to PUSCH, and κ = T c / T f =64. If the first symbol assigned by PUSCH consists only of DMRS, then d 2,1 It can be 0, otherwise, d 2,1 It can be 1. If the scheduling DCI triggers a BWP handover, then d 2,2 Equals the switching time, otherwise, d 2,2 The value is 0. The switching time can be defined differently depending on the frequency range (FR). For example, for FR1, the switching time can be defined as 0.5 ms, and for FR2, it can be defined as 0.25 ms. In this disclosure, T2 can also be referred to as T_proc,2.

[0242] The following tables show the processing time based on the UE's processing capabilities. Specifically, Table 9 shows the PDSCH processing time for UE's PDSCH processing capability #1, Table 10 shows the PDSCH processing time for UE's PDSCH processing capability #2, Table 11 shows the PUSCH preparation time for UE's PUSCH timing capability #1, and Table 12 shows the PUSCH processing time for UE's PUSCH timing capability #2.

[0243] [Table 9]

[0244]

[0245] [Table 10]

[0246] u / SCS PDSCH decoding time N1 [symbol] 0 / 15kHz 3 1 / 30kHz 4.5 2 / 60kHz For frequency ranges 1, 9

[0247] [Table 11]

[0248] u / SCS PUSCH preparation time N2 [symbol] 0 / 15kHz 10 1 / 30kHz 12 2 / 60kHz 23 3 / 120kHz 36

[0249] [Table 12]

[0250] u / SCS PUSCH preparation time N2 [symbol] 0 / 15kHz 5 1 / 30kHz 5.5 2 / 60kHz For frequency range 1, 11

[0251] The UE can report the supported PDSCH processing capabilities to the BS for a carrier corresponding to a frequency band entry within a frequency band combination. For example, the UE can report whether it supports only PDSCH processing capability #1 or PDSCH processing capability #2 for each SCS supported in the corresponding frequency band. Similarly, the UE can report the supported PUSCH processing capabilities to a carrier corresponding to a frequency band entry within a frequency band combination. For example, the UE can report whether it supports only PUSCH processing capability #1 or PUSCH processing capability #2 for each SCS supported in the corresponding frequency band.

[0252] If a UE configured to multiplex different UCI types within a single PUCCH intends to transmit multiple overlapping PUCCHs or overlapping PUCCHs and PUSCHs in a time slot, the UE can multiplex UCI types when certain conditions are met. These conditions may include multiplexing timeline conditions. For example, Figures 9 to 11 The PUCCH and PUSCH used in UCI multiplexing can be UL channels that meet the multiplexing timeline conditions. (See reference...) Figure 12 The UE may need to transmit multiple UL channels in the same time slot (e.g., UL channels #1 to #4). Here, UL CH#1 can be a PUSCH scheduled by PDCCH#1. UL CH#2 can be a PUCCH used to transmit HARQ-ACKs to PDSCH. PDSCH is scheduled by PDCCH#2, and the resources of UL CH#2 can also be indicated by PDCCH#2.

[0253] In this scenario, if the overlapping UL channels on the timeline (e.g., UL channels #1 to #3) meet the multiplexing timeline conditions, the UE can perform UCI multiplexing for the overlapping UL channels #1 to #3. For example, the UE can check whether the first symbol of UL CH #3, starting from the last symbol of PDSCH, meets condition T1. The UE can also check whether the first symbol of UL CH #3, starting from the last symbol of PDCCH #1, meets condition T2. ​​If the multiplexing timeline conditions are met, the UE can perform UCI multiplexing for UL channels #1 to #3. In contrast, if the earliest UL channel among the overlapping UL channels (e.g., the UL channel with the earliest start symbol) does not meet the multiplexing timeline conditions, the UE may not be allowed to multiplex all corresponding UCI types.

[0254] Figure 13 This shows the transmission of multiple HARQ-ACK PUCCHs in a time slot.

[0255] In some scenarios, it is stipulated that the UE does not expect to send more than one PUCCH with HARQ-ACK information in a time slot. Therefore, depending on these scenarios, the UE can send at most one PUCCH with HARQ-ACK information in a time slot. To prevent the UE from failing to send HARQ-ACK information due to the limitation on the number of HARQ-ACK PUCCHs that the UE can send, the BS needs to perform DL scheduling so that HARQ-ACK information can be reused on a single PUCCH resource. However, when considering services with strict latency and reliability requirements (such as URLLC services), the scheme of focusing multiple HARQ-ACK feedbacks on only one PUCCH in a time slot may not be desirable in terms of PUCCH performance. In addition, to support latency-critical services, the BS may need to schedule multiple consecutive PDSCHs of short duration in a time slot. Although the UE can send PUCCHs in random symbols in a time slot through the BS's configuration / instruction, if the UE is only allowed to send at most one HARQ-ACK PUCC in a time slot, the BS may not be able to perform fast back-to-back scheduling of PDSCHs and the UE may not be able to perform fast HARQ-ACK feedback. Therefore, to utilize resources flexibly and efficiently and support services, it is best to allow the transmission of multiple (non-overlapping) HARQ-ACK PUCCHs (or PUSCHs) in a single time slot, such as... Figure 13 As shown.

[0256] The following describes a method for handling multiple UL transmissions (e.g., multiple UL channels) when UL transmissions overlap in time within a time slot. For example, this disclosure provides an implementation of avoiding conflicts between UL transmissions with different priorities when higher-priority UL transmissions and lower-priority UL transmissions overlap in time (i.e., when triggered, assigned, or configured to overlap in time with higher-priority UL transmissions and lower-priority UL transmissions).

[0257] Figure 14 This illustrates conflict scenarios between PUCCHs with different priorities. Figure 15 and Figure 16 This illustrates conflict scenarios between PUSCH and PUCCH with different priorities. (See reference...) Figure 14When a higher-priority H-PUCCH, scheduled (i.e., triggered) in the DCI format during PDCCH reception, overlaps with a lower-priority L-PUCCH in time, the UE can cancel the transmission of the L-PUCCH before the first symbol overlapping with the H-PUCCH. In this case, depending on the UE implementation, the transmission of the entire L-PUCCH can be canceled, or the transmission of the portion of the L-PUCCH overlapping with the H-PUCCH can be canceled. Therefore, at least the transmission of the portion of the L-PUCCH overlapping with the H-PUCCH can be canceled.

[0258] Reference Figure 15 When a higher-priority H-PUCCH, scheduled (i.e., triggered) in the DCI format during PDCCH reception, overlaps with a lower-priority L-PUSCH in time, the UE can cancel the transmission of the L-PUSCH before the first symbol overlapping with the H-PUCCH. Depending on the UE implementation, the transmission of the entire L-PUSCH can be canceled, or the transmission of the portion of the L-PUSCH overlapping with the H-PUCCH can be canceled. Therefore, at least the transmission of the portion of the L-PUSCH overlapping with the H-PUCCH can be canceled.

[0259] Reference Figure 16 When a higher-priority H-PUSCH scheduled via DCI format overlaps with a lower-priority L-PUCCH in PDCCH reception, the UE can cancel the transmission of the L-PUCCH before the first symbol overlapping with the H-PUSCH. Depending on the UE implementation, the transmission of the entire L-PUCCH can be canceled, or the transmission of the portion of the L-PUCCH overlapping with the H-PUSCH can be canceled. Therefore, at least the transmission of the portion of the L-PUCCH overlapping with the H-PUSCH can be canceled.

[0260] exist Figures 14 to 16 In this context, the UE can anticipate that the transmission of H-PUCCH or H-PUSCH will not begin before the last symbol T_proc,2+d1 of the PDCCH reception, where T_proc,2 is based on u and N2 in d 2,1 Under the assumption of [specific assumptions], the PUSCH preparation time corresponding to the UE's processing capability is d1, which is determined by the reported UE capability. For example, the value of the parameter push-PreparationLowPriority reported by the UE to the BS can be used as d1.

[0261] Specifically, referring to 3GPP TS 38.213V16.2.0, when the UE sends a first PUCCH or first PUSCH with higher priority in the first PDCCH via DCI format, and this overlaps with a second PUCCH or second PUSCH with lower priority in the second PDCCH via DCI format,

[0262] >T_proc,2 can be configured based on the value of u corresponding to the minimum SCS among the first PDCCH, second PDCCH, first PUCCH or first PUSCH and second PUCCH or second PUSCH.

[0263] >>If the overlapping group includes the first PUCCH,

[0264] >>>If the parameter processingType2Enabled in the RRC configuration PDSCH-ServingCellConfig used to configure public UE-specific PDSCH parameters on the BWP of a UE in a serving cell is set to enabled for the serving cell in which the UE receives the first PDCCH and for all serving cells in which the UE receives the PDSCH corresponding to the second PUCCH, and if processingType2Enabled in PDSCH-ServingCellConfig is set to enabled for the serving cell with the second PUSCH, then N2 can be 5 for u=0, 5.5 for u=1, and 11 for u=2.

[0265] >>>Otherwise, for u=0, N2 can be 10, for u=1 it can be 12, for u=2 it can be 23, and for u=3 it can be 36.

[0266] If the overlapping group includes the first PUSCH

[0267] >>If PDSCH-ServingCellConfig's processingType2Enabled is enabled for serving cells with a first PUSCH and a second PUSCH, and if PDSCH-ServingCellConfig's processingType2Enabled is enabled for all serving cells where the UE receives the PDSCH corresponding to the second PDCCH, then for u=0, N2 can be 5, for u=1 it is 5.5, and for u=2 it is 11.

[0268] >>>Otherwise, for u=0, N2 can be 10, for u=1 it can be 12, for u=2 it can be 23, and for u=3 it can be 36.

[0269] The parameter processingType2Enabled can be used to configure advanced processing time capabilities of PDSCH.

[0270] When conflicts occur between PUCCHs with different priorities or between PUCCHs and PUSCHs with different priorities, traditional 3GPP-based communication systems can guarantee UE processing time and ensure that lower-priority UL transmissions are canceled before higher-priority UL transmissions by using an extended scheduling timeline. Figures 14 to 16 This is illustrated in the example. In other words, in a traditional 3GPP-based communication system, the UE needs to cancel the transmission of the L-PUCCH or L-PUSCH no later than the first symbol overlapping with the H-PUCCH, where the L-PUCCH or L-PUSCH overlaps in time with the H-PUCCH that begins at least T_proc,1+d1 after the last symbol of the PDCCH. Additionally, the UE needs to cancel the transmission of the L-PUCCH no later than the first symbol overlapping with the H-PUSCH, where the L-PUCCH overlaps in time with the corresponding H-PUSCH that begins at least T_proc,1+d1 after the last symbol of the PDCCH. Figures 14 to 16 This illustrates the case where a lower-priority UL channel transmission is triggered / scheduled to begin before a higher-priority UL channel transmission. However, for an L-PUSCH / L-PUCCH that overlaps with a higher-priority UL channel satisfying the time condition T_proc,1+d1 and is scheduled / triggered to start later than the higher-priority UL channel, the UE can cancel the L-PUSCH / L-PUCCH transmission before the first overlap symbol. When a lower-priority UL channel is scheduled / triggered to start later than the higher-priority UL channel, the UE can cancel the entire L-PUSCH / L-PUCCH transmission because the L-PUSCH / L-PUCCH overlaps with the higher-priority UL channel from the start symbol of the L-PUSCH / L-PUCCH.

[0271] For conflicts between PUSCHs with different priorities, traditional 3GPP-based communication systems only consider conflicts between configuration-granted PUSCHs, with semi-static configuration that makes it difficult for the BS to avoid conflicts through scheduling. That is, traditional 3GPP-based communication systems do not consider conflicts between different types of PUSCHs with different priorities (e.g., overlapping in time between configuration-granted PUSCHs and dynamic-granted PUSCHs with different priorities, or overlapping in time between dynamic-granted PUSCHs with different priorities). Since PUSCH transmission is based on transport blocks (TBs) provided by the Media Access (MAC) layer, not only physical layer operations but also MAC layer operations need to be considered to cancel the transmission of some PUSCHs among the overlapping PUSCHs. It has been stipulated that the UE should not expect overlapping in time between PUSCHs with different priorities; therefore, it is expected that the BS will schedule PUSCHs with different priorities to avoid overlapping in time with each other. However, if the BS configures multiple configuration-granted (CG) PUSCHs, the BS may find it difficult to schedule PDCCH-based PUSCHs (i.e., dynamically granted PUSCHs) to avoid overlap with CG PUSCHs, as CG PUSCHs are expected to consume significant resources. In some cases, the BS may want to dynamically schedule another PUSCH (hereinafter referred to as the second PUSCH) while the BS is scheduling a dynamically granted (DG) PUSCH (hereinafter referred to as the first PUSCH) to the UE. However, according to traditional 3GPP-based radio systems, the BS is constrained to schedule the second PUSCH so that its timing does not overlap with the first PUSCH. Recently, to allow the BS to schedule PUSCHs more freely, it has been considered to allow the BS to schedule PUSCHs such that CG-based PUSCHs and DG-based PUSCHs with different priorities overlap in timing, or that DG-based PUSCHs with different priorities overlap in timing.

[0272] The following describes a method for handling conflicts between UL channels when there are conflicts between PUSCHs with different priorities (i.e., when PUSCHs with different priorities are scheduled to overlap with each other in time).

[0273] If a conflict occurs between PUSCHs with different priorities, the UE needs to cancel the ongoing or preparing PUSCH transmission and prepare for the transmission of the new PUSCH. The new PUSCH transmission can be used to send services such as URLLC services with higher priority, and the UE may need to send the new PUSCH within a minimal processing time. However, if a portion of the PUSCH pipeline was used for a previous PUSCH transmission, the UE may need additional time to cancel the previous PUSCH and reuse the PUSCH pipeline to match the new PUSCH, potentially resulting in a longer processing time than the existing processing time used for PUSCH transmissions.

[0274] Additionally, to protect lower-priority UCIs that are relatively more important, consideration is being given to transmitting lower-priority UCIs on higher-priority PUSCHs. The corresponding UCI could correspond to a UCI multiplexed with the PUSCH to be cancelled. In this case, the UE may need additional time to include UCIs with different priorities in the PUSCH.

[0275] The following implementation describes how, when a higher-priority PUSCH transmission cancels other lower-priority UL transmissions, the scheduling time of the higher-priority PUSCH transmission guarantees sufficient time to cancel the other lower-priority UL transmissions and minimize time delays in URLLC transmissions. Specifically, the implementation uses different cancellation timelines based on the type of lower-priority (LP) UL transmission to be canceled by the higher-priority (HP) PUSCH and handles LP PUCCH / PUSCH cancellations based on the cancellation timelines.

[0276] UE side:

[0277] First, the implementation of this disclosure will be described again from the perspective of the user experience (UE).

[0278] Figure 17 The procedure for transmitting the UL channel at the UE according to some implementations of this disclosure is illustrated.

[0279] The UE can be configured with higher-layer parameters required for transmitting PUCCH and / or PUSCH for various priorities. If PUCCH and / or PUSCH with different priorities overlap in time, the UE can apply the cancellation timeline described in some implementations of this disclosure. In some implementations of this disclosure, when UL channels conflict with each other (i.e., when UL channels overlap at least in time), the UE can multiplex the LP UCI included in the LP PUCCH / PUSCH onto the HP PUSCH / PUCCH based on the cancellation timeline (i.e., the cancellation time condition) that is satisfied.

[0280] In some implementations of this disclosure, the UE can operate as follows.

[0281] The UE can establish an RRC connection with the BS and send a UE capability report to the BS (S1701). The UE can receive UL licenses with different priorities (S1703). According to some implementations of this disclosure, the UE can perform multiplexing and / or prioritization among multiple UL licenses based on the sent UE capability report. The UE can cancel the transmission of non-priority PUCCH and / or PUSCH and transmit a priority PUSCH (S1705). In this case, the UCI in the non-priority PUCCH and / or PUSCH can be transmitted on the priority PUSCH according to the satisfied timeline.

[0282] The following implementation methods can be considered in the operation of the UE disclosed herein.

[0283] <Implementation Method A1> Additional UL Cancellation / Preparation Time Offset for PUSCH Prioritization

[0284] In prioritization, the cases of PUCCH and PUSCH conflicts and PUSCH conflicts with another PUSCH can be treated differently. When two UL channels with different priorities overlap, when the UE selects and transmits one of the two UL channels, and when both UL channels are PUSCHs, the UE can assume a longer PUSCH preparation time or a longer scheduling time (compared to when PUCCHs with different priorities overlap in time or when PUCCHs and PUSCHs with different priorities overlap in time) in order to determine the effectiveness of scheduling (e.g., to determine whether the HP PUSCH is effectively scheduled).

[0285] In traditional 3GPP-based wireless communication systems, the process of a UE transmitting a PUCCH (specifically, a HARQ-ACK PUCCH) may include the UE receiving and processing a PDSCH and transmitting the processing result on the PUCCH at the physical (PHY) layer. On the other hand, the PUSCH transmission process may include the following: after receiving a UL clearance via the PDCCH, the MAC layer generates a TB suitable for PUSCH resources from the higher-layer information (MAC SDU) and sends the TB to the PHY layer. Different processing may be required when individual channels are cancelled. When a PUCCH is cancelled, PDSCH decoding and HARQ combination do not necessarily need to be cancelled; therefore, the process of the PHY layer converting HARQ-ACK information into a bit sequence and transmitting the bit sequence may need to be cancelled. On the other hand, for PUSCH, the PUSCH that has already generated a MAC PDU from the MAC SDU is cancelled. Therefore, if only the transmission of the PHY channel is cancelled without cancelling the PUSCH, it may be difficult to transmit the generated MAC PDU unless there is special assistance from the BS, and there may be significant delays due to waiting until RLC reordering. To avoid these adverse effects, a MAC layer procedure for canceling the MAC PDU generation process may be necessary, which may require additional inter-layer operations. In implementation A1, an additional processing time offset d3 is used to reflect the characteristics of this canceled UL channel.

[0286] In this scenario, d3 can be included and transmitted in capability signaling used to inform the BS of the capabilities supported by the UE. The value of d3 can be transmitted via RRC parameters and can be selected from a predetermined range. For example, one of the values ​​{0, 1, 2} can be selected.

[0287] Alternatively, to determine the value of d3, the type of conflicting radio resource (e.g., PUSCH or PUCCH) (specifically, the type of radio resource to be cancelled) can be considered as described above. For example, when PUCCH is cancelled, d3 = 0, or d3 may not be applied. When PUSCH is cancelled, d3 can be selected from values ​​0, 1, and 2 as the value reported by the UE via capability signaling. Alternatively, the value of d3 applied when PUCCH is cancelled can be different from the value of d3 applied when PUSCH is cancelled, as reported by a separate RRC parameter as a separate capability.

[0288] Alternatively, the value of d3 can be considered to change dynamically based on the conflicting resources. For example, d3 may have different values ​​depending on whether the number of channels involved in the conflict between UL channels is greater than or equal to N or less than or equal to N. As another example, d3 may have different values ​​depending on whether the duration of the channel to be cancelled is greater than or equal to L symbols or less than or equal to L symbols. As yet another example, d3 may have different values ​​depending on whether another UL channel is scheduled to overlap with the cancelled channel in time. For example, d3 may have a larger value when there is another PUCCH resource that overlaps in time with the cancelled PUSCH resource, and when PUCCH transmission can be performed by performing UCI multiplexing on the corresponding PUSCH resource in the case of PUSCH resource cancellation. In this case, the number of channels N, the channel length L, and the value of d3 to be used in each case can be predefined or determined by the L1 signaling and / or higher-layer signaling of the BS.

[0289] For example, when a UE supports prioritization between two PUSCHs with different priorities, the UE can report an additional processing time d3 to the BS via capability signaling (i.e., capability report). When the UE performs prioritization between two PUSCHs with different priorities, the UE can only expect the following: the distance from the end of the PDCCH scheduling the PUSCH with the higher (i.e., larger) priority to the start of the corresponding PUSCH is greater than or equal to T_proc,2+d1+d3 or T'_proc,2+d1. In other words, it can be adjusted so that the UE expects the HP PUSCH that overlaps with the LP PUSCH in time not to start before the time T_proc,2+d1+d3 elapsed from the last symbol of the PDCCH scheduling the HP PUSCH transmission.

[0290] Alternatively, for time delay reduction, when the UE performs prioritization between two PUSCHs with different priorities, the UE can only expect the following: the distance from the end of the PDCCH scheduling the higher (i.e., higher) priority PUSCH to the start of the first symbol among the overlapping symbols of the higher-priority PUSCH and the lower (i.e., lower) priority PUSCH is greater than or equal to T_proc,2+d1+d3 or T'_proc,2+d1. In other words, the adjustable UE expects the first symbol of the overlap between the LP PUSCH and HPPUSCH not to start before the time T_proc,2+d1+d3 elapsed from the last symbol of the PDCCH scheduling the HP PUSCH transmission. This guarantees the distance from the PDCCH scheduling of the HP PUSCH to the actual point of cancellation, thereby reducing the delay in higher-priority scheduling.

[0291] The following can be considered in implementation method A1.

[0292] -T_proc,2=max{(N2+d 2,1 +d2)(2048+144)*κ*2 -u *T c +T ext +T switch ,d 2,2}}

[0293] -T'_proc,2=max{(N2+d 2,1 +d2+d3)(2048+144)*κ*2 -u *T c +T ext +T switch ,d 2,2}}

[0294] -T_proc,2 and T'_proc,2 are the PUSCH preparation times for the corresponding UE processing capabilities.

[0295] -Assume d 2,1 =0, other parameters besides N2 and d3 are defined in Section 6.4 of 3GPP TS 38.214V16.2.0 (e.g., T ext T swtich d 2,2 wait).

[0296] -d1 can be determined from the reported UE capabilities.

[0297] -N2 can be determined as described in 3GPP TS 38.214V16.2.0 (see N2 in 3GPP TS 38.214V16.2.0).

[0298] <Implementation Method A2> Additional UL Cancellation / Preparation Timeline for PUSCH Multiplexing

[0299] When a UE selects and transmits one of two UL channels that overlap (in time) and have different priorities, the UE can determine the effectiveness of H-PUSCH scheduling based on the two PUSCH preparation times or scheduling times by taking into account the additional preparation time or scheduling time.

[0300] Additional preparation or scheduling time can be defined as an offset represented by the number of symbols, which can be predetermined or determined by L1 signaling or higher-layer signaling between the UE and the BS. The UE can use the offset to determine the validity of scheduling based on each of the regular timeline X and the additional timeline Y.

[0301] For example, when the UE supports prioritization between two PUSCH / PUCCH with different priorities (i.e., between PUSCH and PUCCH with different priorities, between PUSCH with different priorities, or between PUCCH with different priorities), the UE can report additional processing time d via capability signaling. 优先级 When the UE performs prioritization between PUSCH / PUCCHs with different priorities, if the distance between the start of the PUSCH / PUCCH with the higher priority and the end of the PDCCH of the corresponding PUSCH / PUCCH or related PDSCH is greater than or equal to T_proc,2+d1, then the UE can determine that timeline X is satisfied. If this distance is greater than or equal to T_proc,2+d1+d... 优先级 If T'_proc,2d1, then the UE can determine that the additional timeline Y is satisfied.

[0302] The following can be considered in implementation method A2.

[0303] -T_proc,2=max{(N2+d 2,1 +d2)(2048+144)*κ*2 -u *T c +T ext +T switch ,d 2,2}}

[0304] -T'_proc,2=max{(N2+d 2,1 +d2+d 优先级 (2048+144)*κ*2 -u *T c +T ext +T switch ,d 2,2}}

[0305] -T_proc,2 and T'_proc,2 are the PUSCH preparation times for the corresponding UE processing capabilities.

[0306] -Assume d 2,1 =0, N2 and d are defined in Section 6.4 of 3GPP TS 38.214V16.2.0. 优先级 Other parameters (e.g., T) ext T swtich d 2,2 wait).

[0307] -d1 can be determined from the reported UE capabilities.

[0308] -N2 can be determined as described in 3GPP TS 38.214V16.2.0 (see N2 in 3GPP TS 38.214V16.2.0).

[0309] In some embodiments of this disclosure, the UE may consider timeline X and timeline Y to perform the following operations.

[0310] <Implementation Method A2-1>

[0311] If two overlapping UL transmissions with different priorities satisfy timeline X but not timeline Y, the UE may cancel the transmission of the lower (i.e., lower) priority PUSCH or PUCCH starting from the first symbol of the lower priority PUSCH or PUCCH that overlaps with the higher (i.e., higher) priority PUSCH or PUCCH, and the BS may expect the UE to operate as described above.

[0312] <Implementation Method A2-2>

[0313] If two overlapping UL transmissions with different priorities satisfy both timelines X and Y, and if the UL channel with the lower (lower) priority is a PUCCH or PUSCH that includes a UCI, then the UE can multiplex and transmit the UCI included in the PUSCH or PUCCH that has the higher (higher) priority, and the BS can expect the UE to operate as described above.

[0314] In implementation A2-2, timeline Y can be the time condition for enabling inter-priority multiplexing. That is, when UL transmissions with higher (higher) priority are scheduled for sufficient time, implementation A2-2 can enable inter-priority UL multiplexing on a limited basis, thereby preventing problems that may occur when LP PUSCH / PUCCH is canceled.

[0315] <Implementation Method A3>

[0316] If the UE receives a PDCCH that meets certain conditions after cancelling a PUSCH / PUCCH, the UE may transmit the payload of the canceled PUSCH or PUCCH on the resource indicated by the corresponding PDCCH or on a resource having the same location within the same time slot (or sub-time slot) as the previously canceled PUSCH or PUCCH within the time slot indicated by the corresponding PDCCH (or a sub-time slot consisting of fewer than 14 symbols (e.g., 2 or 7 symbols)). If the PUCCH is canceled and if the PUSCH scheduling meets certain conditions, the UE may transmit a UCI on the PUSCH that is assumed to be transmitted on the canceled PUCCH. If the PUSCH is canceled and if the PUSCH scheduling meets certain conditions, the UE may retransmit only the canceled portion of the PUSCH. For example, see reference... Figure 15 If an L-PUSCH transmission starts but is cancelled before an H-PUSCH transmission starts, then only the portion of the L-PUSCH that was cancelled due to the start of the H-PUSCH can be retransmitted, except for the portion that was transmitted before the L-PUSCH was cancelled.

[0317] When prioritizing UL transmissions between a traditional UE or a UE using implementation A2-1, the UE can cancel all or part of the LPPUSCH / PUCCH. According to implementation A3, the UE can directly send the UCI included in the canceled transmission to the BS via another transmission. Specifically, when a PUSCH / PUCCH including HARQ-ACK feedback is canceled, the BS can receive the HARQ-ACK feedback again, that is, receive the reception result of the PDSCH associated with the canceled HARQ-ACK feedback, without scheduling the retransmission of the associated PDSCH.

[0318] In implementation A3, the following can be considered as specific conditions.

[0319] - The corresponding PDCCH is the first PDCCH received after a symbol whose transmission with a lower priority has been cancelled.

[0320] - The specific field value of the scheduling DCI matches the predetermined field value. For example, the type 1 resource allocation field in the scheduling DCI carried on the corresponding PDCCH is 0 and the value of MCS is 31 (see 3GPP TS 38.212).

[0321] - A pre-configured RNTI is used to identify PDCCHs that meet specific conditions, and the CRC of the corresponding PDCCH is scrambled using the corresponding RNTI. In this case, the corresponding PDCCH can be a group of common PDCCHs. If the UE cancels the transmission of PUCCH / PUSCH, the UE can transmit the canceled PUCCH / PUSCH in the same manner as the previously canceled transmission, in a time slot determined by applying a predetermined or indicated time slot or sub-time slot offset to the time when the PDCCH scheduled for receiving the canceled PUCCH / PUSCH is received. For example, the retransmission of the canceled PUCCH / PUSCH can be performed based on the same parameters as the previously canceled transmission, except for the time slot location used for transmission (e.g., start symbol, number of symbols, DM-RS location, antenna port, etc.).

[0322] BS side:

[0323] The above implementation method of this disclosure will be described again from the perspective of BS.

[0324] Figure 18 The flow of UL channel reception at the BS is shown according to some implementations of this disclosure.

[0325] The BS can be configured with higher-layer parameters required for transmitting PUCCH and / or PUSCH for various priorities. If PUCCH and / or PUSCH with different priorities overlap in time for the UE, the BS can anticipate that the UE can apply the cancellation timelines described above in some implementations of this disclosure. In some implementations of this disclosure, when the UE has conflicts between UL channels (i.e., when the UL channels overlap at least in time), the BS can anticipate that the UE can multiplex the LP UCI included in the LP PUCCH / PUSCH to HPPUSCH / PUCCH based on the cancellation timeline (i.e., the cancellation time condition) that is satisfied.

[0326] In some implementations of this disclosure, the BS can operate as follows.

[0327] The BS can establish an RRC connection with the UE and receive a UE capability report from the UE (S1801). The BS can consider the UE's capabilities and send UL licenses for multiple PUSCHs with different priorities to the UE (S1803). The BS can assume that the UE performs multiplexing and / or prioritization among the multiple UL licenses according to some embodiments of this disclosure, and then receive the PUSCH prioritized by the UE based on the result of the multiplexing and / or prioritization (S1805). The BS can assume that, based on the UE's capabilities, it transmits the UCI in the non-priority PUCCH and / or PUSCH on the prioritized PUSCH, and then performs PUSCH decoding. The UCI in the non-priority PUCCH and / or PUSCH can be transmitted on the prioritized PUSCH.

[0328] The following implementation methods can be considered in the operation of the BS disclosed herein.

[0329] <Implementation Method B1> Additional UL Cancellation / Preparation Time Offset for PUSCH Prioritization

[0330] In prioritization, the cases of PUCCH and PUSCH conflicts and PUSCH conflicts with another PUSCH can be treated differently. When two UL channels with different priorities overlap, when the UE selects and transmits one of the two UL channels, and when both UL channels are PUSCHs, the BS can assume that the UE uses a longer PUSCH preparation time or a longer scheduling time (compared to when PUCCHs with different priorities overlap in time or when PUCCHs and PUSCHs with different priorities overlap in time) in order to determine the effectiveness of scheduling (e.g., to determine whether the HP PUSCH is effectively scheduled).

[0331] In traditional 3GPP-based wireless communication systems, the process of a UE transmitting a PUCCH (specifically, a HARQ-ACK PUCCH) may include the UE receiving and processing a PDSCH and transmitting the processing result on the PUCCH at the PHY layer. On the other hand, the PUSCH transmission process may include the following: after receiving a UL clearance via the PDCCH, the MAC layer generates a TB suitable for PUSCH resources from the higher-layer information (MAC SDU) and sends the TB to the PHY layer. Different processing may be required when individual channels are cancelled. When a PUCCH is cancelled, PDSCH decoding and HARQ combination do not necessarily need to be cancelled; therefore, the process of the PHY layer converting HARQ-ACK information into a bit sequence and transmitting the bit sequence may need to be cancelled. On the other hand, for PUSCH, the PUSCH that has already generated a MAC PDU from the MAC SDU is cancelled. Therefore, if only the transmission of the PHY channel is cancelled without cancelling the PUSCH, it may be difficult to transmit the generated MAC PDU unless there is special assistance from the BS, and there may be significant delays due to waiting until RLC reordering. To avoid these adverse effects, a MAC layer procedure for canceling the MAC PDU generation process may be necessary, which may require additional inter-layer operations. In implementation B1, an additional processing time offset d3 is used to reflect the characteristics of this canceled UL channel.

[0332] In this scenario, d3 can be included in and transmitted in capability signaling used to inform the BS of the capabilities supported by the UE. The value of d3 can be transmitted via RRC parameters and can be selected from a predetermined range. For example, one of the values ​​{0, 1, 2} can be selected.

[0333] Alternatively, to determine the value of d3, the type of conflicting radio resource (e.g., PUSCH or PUCCH) (specifically, the type of radio resource to be cancelled) can be considered as described above. For example, when PUCCH is cancelled, d3 = 0, or d3 may not be applied. When PUSCH is cancelled, d3 can be selected from values ​​0, 1, and 2 as the value reported by the UE via capability signaling. Alternatively, the value of d3 applied when PUCCH is cancelled can be different from the value of d3 applied when PUSCH is cancelled, as reported by a separate RRC parameter as a separate capability.

[0334] Alternatively, the value of d3 can be considered to change dynamically based on the conflicting resources. For example, d3 may have different values ​​depending on whether the number of channels involved in the conflict between UL channels is greater than or equal to N or less than or equal to N. As another example, d3 may have different values ​​depending on whether the duration of the channel to be cancelled is greater than or equal to L symbols or less than or equal to L symbols. As yet another example, d3 may have different values ​​depending on whether another UL channel is scheduled to overlap with the cancelled channel in time. For example, d3 may have a larger value when there is another PUCCH resource that overlaps in time with the cancelled PUSCH resource, and when PUCCH transmission can be performed by performing UCI multiplexing on the corresponding PUSCH resource in the case of PUSCH resource cancellation. In this case, the number of channels N, the channel length L, and the value of d3 to be used in each case can be predefined or determined by the L1 signaling and / or higher-layer signaling of the BS.

[0335] For example, when a UE supports prioritization between two PUSCHs with different priorities, the UE can report an additional processing time d3 to the BS via capability signaling (i.e., capability report). When the UE performs prioritization between two PUSCHs with different priorities, the BS can perform scheduling by assuming that the UE only expects the following: the distance from the end of the PDCCH scheduling the PUSCH with the higher (i.e., larger) priority to the start of the corresponding PUSCH is greater than or equal to T_proc,2+d1+d3 or T'_proc,2+d1. For example, the BS can schedule an HP PUSCH that overlaps with the LP PUSCH in time, such that the HP PUSCH begins at least after a time T_proc,2+d1+d3 elapsed from the last symbol of the PDCCH scheduling the HPPUSCH transmission.

[0336] Alternatively, for time delay reduction, when the UE performs prioritization between two PUSCHs with different priorities, the BS can perform scheduling by assuming the UE only expects the following: the distance from the end of the PDCCH scheduling the higher (i.e., higher) priority PUSCH to the start of the first symbol among the overlapping symbols of the higher-priority PUSCH and the lower (i.e., lower) priority PUSCH is greater than or equal to T_proc,2+d1+d3 or T'_proc,2+d1. For example, the BS can perform scheduling such that the first symbol overlapping the LP PUSCH and HP PUSCH begins at least after a time T_proc,2+d1+d3 elapsed from the last symbol of the PDCCH scheduling the HP PUSCH transmission. This guarantees the distance from the PDCCH scheduling of the HP PUSCH to the actual point in time when cancellation is required, thereby reducing delays in higher-priority scheduling.

[0337] The following can be considered in implementation method B1.

[0338] -T_proc,2=max{(N2+d 2,1 +d2)(2048+144)*κ2 -u *T c +T ext +T switch ,d 2,2}}

[0339] -T'_proc,2=max{(N2+d 2,1 +d2+d3)(2048+144)*κ2 -u *T c +T ext +T switch ,d 2,2}}

[0340] -T_proc,2 and T'_proc,2 are the PUSCH preparation times for the corresponding UE processing capabilities.

[0341] -Assume d 2,1 =0, other parameters besides N2 and d3 are defined in Section 6.4 of 3GPP TS 38.214V16.2.0 (e.g., T ext T swtich d 2,2 wait).

[0342] -d1 can be determined by the reported UE capabilities.

[0343] -N2 can be determined as described in 3GPP TS 38.214V16.2.0 (see N2 in 3GPP TS 38.214V16.2.0).

[0344] <Implementation Method B2> Additional UL Cancellation / Preparation Timeline for PUSCH Multiplexing

[0345] When a UE selects and transmits one of two UL channels that overlap (in time) and have different priorities, the BS may assume that the UE will determine the effectiveness of the H-PUSCH scheduling based on the two PUSCH preparation times or scheduling times by taking into account the additional preparation time or scheduling time.

[0346] Additional preparation time or scheduling time can be defined as an offset represented by the number of symbols, which can be predetermined or determined by L1 signaling or higher-layer signaling between the UE and the BS. The BS can assume that the UE will use the offset to determine the validity of the scheduling based on each of the regular timeline X and the additional timeline Y.

[0347] For example, when the UE supports prioritization between two PUSCH / PUCCH with different priorities (i.e., between PUSCH and PUCCH with different priorities, between PUSCH with different priorities, or between PUCCH with different priorities), the UE can report additional processing time d via capability signaling. 优先级 The BS can perform scheduling and / or receiving of UL channels based on the following assumption: when the UE performs prioritization between PUSCH / PUCCHs with different priorities, if the distance between the start of the PUSCH / PUCCH with the higher (i.e., higher) priority and the end of the PDCCH of the corresponding PUSCH / PUCCH or related PDSCH is greater than or equal to T_proc,2+d1, then the UE will determine that timeline X is satisfied. Additionally, the BS can perform scheduling and / or receiving of UL channels based on the following assumption: if the distance is greater than or equal to T_proc,2+d1+d... 优先级 If T'_proc,2+d1, then the UE can determine that it satisfies the additional timeline Y.

[0348] The following can be considered in implementation method B2.

[0349] -T_proc,2=max{(N2+d 2,1 +d2)(2048+144)*κ*2 -u *T c +T ext +T switch ,d 2,2}}

[0350] -T'_proc,2=max{(N2+d 2,1 +d2+d 优先级 (2048+144)*κ*2 -u *T c +T ext +T switch ,d 2,2}}

[0351] -T_proc,2 and T'_proc,2 are the PUSCH preparation times for the corresponding UE processing capabilities.

[0352] -Assume d 2,1 =0, N2 and d are defined in Section 6.4 of 3GPP TS 38.214V16.2.0. 优先级 Other parameters (e.g., T) ext T swtich d 2,2 wait).

[0353] -d1 can be determined from the reported UE capabilities.

[0354] -N2 can be determined as described in 3GPP TS 38.214V16.2.0 (see N2 in 3GPP TS 38.214V16.2.0).

[0355] In some embodiments of this disclosure, the BS may consider timeline X and timeline Y to perform the following resource allocation operations for the UE.

[0356] <Implementation Method B2-1>

[0357] If two overlapping UL transmissions with different priorities satisfy timeline X but not timeline Y, the UE may cancel the transmission of the PUSCH or PUCCH with the lower priority starting from the first symbol among the symbols of the PUSCH or PUCCH with the lower priority that overlaps with the PUSCH or PUCCH with the higher priority, and the BS may expect the UE to operate as described above.

[0358] <Implementation Method B2-2>

[0359] If two overlapping UL transmissions with different priorities satisfy both timelines X and Y, and if the UL channel with the lower (lower) priority is a PUCCH or PUSCH that includes a UCI, then the UE can multiplex and transmit the UCI included in the PUSCH or PUCCH that has the higher (higher) priority, and the BS can expect the UE to operate as described above.

[0360] In implementation B2-2, timeline Y can be the time condition for enabling inter-priority multiplexing. That is, when UL transmissions with higher (higher) priority are scheduled for sufficient time, implementation B2-2 can enable inter-priority UL multiplexing on a limited basis, thereby preventing problems that may occur when LP PUSCH / PUCCH is canceled.

[0361] <Implementation Method B3>

[0362] If the UE receives a PDCCH that meets certain conditions after canceling a PUSCH / PUCCH, the BS may assume that the UE will transmit the payload of the canceled PUSCH or PUCCH on the resource indicated by the corresponding PDCCH or on a resource having the same location in the same time slot (or sub-time slot) as the previously canceled PUSCH or PUCCH in the time slot indicated by the corresponding PDCCH. If the PUCCH is canceled and if the PUSCH scheduling meets certain conditions, the BS may receive the PUSCH by assuming that the UE will transmit a UCI on the PUSCH that is assumed to be transmitted on the canceled PUCCH. If the PUSCH is canceled and if the PUSCH scheduling meets certain conditions, the BS may perform UL reception by assuming that the UE will only retransmit the canceled portion of the PUSCH. For example, refer to Figure 15 If an L-PUSCH transmission begins but is cancelled before an H-PUSCH transmission begins, the BS may assume that only a portion of the L-PUSCH that was cancelled due to the start of the H-PUSCH is retransmitted, except for the portion that was transmitted before the L-PUSCH was cancelled.

[0363] When prioritizing UL transmissions between a traditional UE or a UE using implementation B2-1, the BS can perform UL reception based on the assumption that the UE will cancel all or part of the LP PUSCH / PUCCH. According to implementation B3, the BS can directly receive the UCI included in the canceled UE transmission through another transmission of the UE. Specifically, according to implementation B3, when a PUSCH / PUCCH including HARQ-ACK feedback is canceled, the BS can receive the HARQ-ACK feedback again, that is, receive the reception result of the PDSCH associated with the canceled HARQ-ACK feedback, without scheduling the retransmission of the associated PDSCH.

[0364] In implementation B3, the following can be considered as specific conditions.

[0365] - The corresponding PDCCH is the first PDCCH received after a symbol whose transmission with a lower priority has been cancelled.

[0366] - The specific field value of the scheduling DCI matches the predetermined field value. For example, the type 1 resource allocation field in the scheduling DCI carried on the corresponding PDCCH is 0 and the value of MCS is 31 (see 3GPP TS 38.212).

[0367] - A pre-configured RNTI is used to identify PDCCHs that meet specific conditions, and the CRC of the corresponding PDCCH is scrambled using the corresponding RNTI. In this case, the corresponding PDCCH can be a group of common PDCCHs. If the UE cancels the transmission of PUCCH / PUSCH, the BS can perform UL reception by assuming that the UE transmits the canceled PUCCH / PUSCH in the same manner as the previously canceled transmission, in a time slot determined by applying a predetermined or indicated time slot or sub-time slot offset to the PDCCH scheduled for receiving the canceled PUCCH / PUSCH. For example, the BS can perform UL reception by assuming that the canceled PUCCH / PUSCH is retransmitted based on the same parameters as the previously canceled transmission, except for the time slot location used for transmission (e.g., start symbol, number of symbols, DM-RS location, antenna port, etc.).

[0368] Figure 19 The diagram illustrates the signal transmission / reception flow between the UE and BS according to some implementations of this disclosure.

[0369] The BS and UE can establish an RRC connection, and the UE can report UE capability information to the BS (S1901). The BS can send UL authorizations for allocating multiple PUSCH resources with different priorities and overlapping timeframes to the UE (S1903). According to some implementations of this disclosure, the UE can perform prioritization and / or multiplexing based on UL authorizations and timeline conditions, and the BS can assume prioritization and / or multiplexing to be performed by the UE. The UE can perform UL transmissions on prioritized PUSCH resources, and the BS can receive UL transmissions on prioritized PUSCH resources (S1905).

[0370] According to some implementations of this disclosure, when an HP PUSCH transmission cancels other LP UL transmissions, the BS and UE can ensure that the scheduling time of the HP PUSCH transmission is sufficient to cancel other LP UP transmissions and minimize the time delay in the URLLC transmission. According to some implementations of this disclosure, the UE can use multiple timelines (i.e., multiple time conditions), thereby reducing the implementation complexity of the UE and enabling UL multiplexing between priorities. Additionally, the BS can be allowed to perform reception on the HP channel without needing to request LP UCI again.

[0371] The UE can perform operations associated with transmission of the UL channel 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 storing instructions that, when executed, cause the at least one processor to perform operations according to some implementations of this disclosure. A processing device for the UE may include: at least one processor; and at least one computer memory operatively connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations according to some implementations of this disclosure. A computer-readable 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-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.

[0372] For the UE, processing device, computer-readable (non-volatile) storage medium, and / or computer program product, these operations may include: transmitting the first PUCCH and canceling the transmission of the second PUCCH based on the fact that a first PUCCH and a second PUCCH having a lower priority than the first PUCCH overlap in time and the first PUCCH satisfies a first time condition; and transmitting the first PUSCH and canceling the transmission of the second PUSCH based on the fact that a first PUSCH and a second PUSCH having a lower priority than the first PUSCH overlap in time and the first PUSCH satisfies a second time condition. The duration T_B of the second time condition may be longer than the duration T_A of the first time condition.

[0373] In some implementations of this disclosure, these operations may further include: based on the fact that the third PUCCH and the fourth PUSCH, which have a lower priority than the third PUCCH, overlap in time and the third PUCCH satisfies a first time condition, performing the transmission of the third PUCCH and canceling the transmission of the fourth PUSCH.

[0374] In some implementations of this disclosure, these operations may further include: based on the fact that the third PUSCH and the fourth PUCCH, which have a lower priority than the third PUSCH, overlap in time and the third PUSCH satisfies a first time condition, performing the transmission of the third PUSCH and canceling the transmission of the fourth PUCCH.

[0375] In some implementations of this disclosure, these operations may further include: multiplexing the UCI included in the second PUCCH onto the first PUCCH based on the first PUCCH satisfying a first time condition and not satisfying a second time condition, since the first PUCCH overlaps with the second PUCCH in time.

[0376] In some implementations of this disclosure, these operations may further include: multiplexing the UCI included in the fourth PUCCH onto the third PUSCH based on the fact that the third PUSCH, which overlaps with the fourth PUCCH in time, satisfies a first time condition but does not satisfy a second time condition.

[0377] In some implementations of this disclosure, the first timing condition may include the following: the time distance from the last symbol of the PDCCH that schedules the higher priority UL channel to the start of the higher priority uplink channel is greater than or equal to T_A = T_proc,2 + d1, where T_proc,2 is the PUSCH preparation time for the UE's processing capability, and d1 is determined by the capability reported by the UE.

[0378] In some implementations of this disclosure, the second timing condition may include the following: the time distance from the last symbol of the PDCCH to the start of the higher priority uplink channel is greater than or equal to T_B = T_proc,2+d1+d add , where T_proc,2 is the PUSCH preparation time for the UE's processing capabilities, and d1 is determined by the capabilities reported by the UE.

[0379] The BS can perform operations related to HARQ-ACK reception 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.

[0380] For a BS, processing device, computer-readable (non-volatile) storage medium, and / or computer program product, these operations may include: receiving the first PUCCH and canceling the reception of the second PUCCH based on the fact that a first PUCCH and a second PUCCH having a lower priority than the first PUCCH overlap in time and the first PUCCH satisfies a first timing condition; and receiving the first PUSCH and canceling the reception of the second PUSCH based on the fact that a first PUSCH and a second PUSCH having a lower priority than the first PUSCH overlap in time and the first PUSCH satisfies a second timing condition. The duration T_B of the second timing condition may be longer than the duration T_A of the first timing condition.

[0381] In some implementations of this disclosure, these operations may further include: based on the time overlap between the third PUCCH and the fourth PUSCH, which has a lower priority than the third PUCCH, and the third PUCCH satisfying a first time condition, performing reception of the third PUCCH and canceling reception of the fourth PUSCH.

[0382] In some implementations of this disclosure, these operations may further include: based on the time overlap of the third PUSCH and the fourth PUCCH having a lower priority than the third PUSCH and the third PUSCH satisfying a first time condition, performing the reception of the third PUSCH and canceling the reception of the fourth PUCCH.

[0383] In some implementations of this disclosure, these operations may further include: receiving a UCI assumed to be received on the second PUCCH on the first PUCCH based on the first PUCCH satisfying a first time condition and not satisfying a second time condition, which overlaps with the second PUCCH in time.

[0384] In some implementations of this disclosure, these operations may further include: receiving a UCI assumed to be received on the fourth PUCCH on the third PUSCH based on the fact that the third PUSCH, which overlaps with the fourth PUCCH in time, satisfies a first time condition but does not satisfy a second time condition.

[0385] In some implementations disclosed herein, the time length T_B can be d longer than the time length T_A. add In this case, d add This may correspond to d3 described in implementation A1 of this disclosure or d described in implementation A2 of this disclosure. 优先级 .

[0386] In some implementations of this disclosure, the first timing condition may include the following: the time distance from the last symbol of the PDCCH that schedules the higher priority UL channel to the start of the higher priority uplink channel is greater than or equal to T_A = T_proc,2 + d1, where T_proc,2 is the PUSCH preparation time for the UE's processing capability, and d1 is determined by the capability reported by the UE.

[0387] In some implementations of this disclosure, the second timing condition may include the following: the time distance from the last symbol of the PDCCH to the start of the higher priority uplink channel is greater than or equal to T_B = T_proc,2+d1+d add , where T_proc,2 is the PUSCH preparation time for the UE's processing capabilities, and d1 is determined by the capabilities reported by the UE.

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

[0389] Industrial applicability

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

Claims

1. A method of transmitting uplink, UL, channels by a user equipment, UE, in a wireless communication system, the method comprising: reporting UE capability information including i) information on a first additional number of symbols, d_1, needed for cancelling a lower priority UL transmission that exceeds a physical uplink shared channel, PUSCH, preparation time, N_2, and ii) information on a second additional number of symbols, d_3, needed on top of N_2+d_1; detecting a downlink control information, DCI, format scheduling transmission of a first uplink channel of a greater priority; and for transmission of the first uplink channel of the greater priority that does not start T symbols after a last symbol of a physical downlink control channel, PDCCH, carrying the DCI format and based on a determination that the transmission of the first uplink channel of the greater priority overlaps in time with transmission of a second uplink channel of a lesser priority, cancelling the transmission of the second uplink channel of the lesser priority before an earliest symbol overlapping with the transmission of the first uplink channel of the greater priority, wherein T is a preparation time related to cancellation of the second uplink channel of the lesser priority, wherein T is determined based on d, wherein based on at least one of the first uplink channel of the greater priority and the second uplink channel of the lesser priority being a physical uplink control channel, PUCCH, d is equal to d_1, wherein d_1 is determined by the reported UE capability information, and wherein based on the first uplink channel of the greater priority and the second uplink channel of the lesser priority being a first PUSCH of the greater priority and a second PUSCH of the lesser priority, respectively, d is equal to d_1+d_3, wherein d_1 and d_3 are determined by the reported UE capability information.

2. The method of claim 1, wherein, The second PUSCH is a configured grant based PUSCH without a corresponding PDCCH. 3.The method of claim 1, further comprising: performing the transmission of the first uplink channel of the greater priority.

4. The method of any one of claims 1 to 3, wherein, T is determined based on N_2+d, wherein N_2 is a PUSCH preparation time predefined for a processing capability of the UE.

5. The method of claim 4, wherein, N_2 is based on a subcarrier spacing configuration u, wherein u is one of u_DL and u_UL that results in a maximum T, wherein u_DL corresponds to a downlink subcarrier spacing in which the PDCCH carrying the DCI format is transmitted and u_UL corresponds to an uplink subcarrier spacing in which the first uplink channel is to be transmitted. 6.A user equipment, UE, configured to transmit uplink, UL, channels in a wireless communication system, the UE comprising: at least one transceiver; at least one processor; and at least one computer memory operably connectable to the at least one processor and configured to store instructions that, when executed, are operable to cause the at least one processor to perform operations comprising: reporting UE capability information, the UE capability information including i) information about a first additional number of symbols d_1 needed for cancelling a lower priority UL transmission that exceeds a physical uplink shared channel, PUSCH, preparation time N_2, and ii) information about a second additional number of symbols d_3 needed on top of N_2+d_1; detecting a downlink control information, DCI, format scheduling a transmission of a first uplink channel of a larger priority; and for a transmission of the first uplink channel of a larger priority that does not start T symbols after a last symbol of a physical downlink control channel, PDCCH, carrying the DCI format, and based on a determination that the transmission of the first uplink channel of a larger priority overlaps in time with a transmission of a second uplink channel of a smaller priority, cancelling the transmission of the second uplink channel of a smaller priority before an earliest symbol that overlaps with the transmission of the first uplink channel of a larger priority, wherein T is a preparation time related to the cancellation of the second uplink channel of a smaller priority, wherein T is determined based on d, wherein based on at least one of the first uplink channel of a larger priority and the second uplink channel of a smaller priority being a physical uplink control channel, PUCCH, d is equal to d_1, wherein d_1 is determined by the reported UE capability information, and wherein based on the first uplink channel of a larger priority and the second uplink channel of a smaller priority being a first PUSCH of a larger priority and a second PUSCH of a smaller priority, respectively, d is equal to d_1+d_3, wherein d_1 and d_3 are determined by the reported UE capability information.

7. The UE of claim 6, wherein, the second PUSCH is a configured grant based PUSCH without a corresponding PDCCH.

8. The UE of claim 6, wherein, the operations further include: performing reception of the first uplink channel of a larger priority.

9. The UE of any one of claims 6-8, wherein, T is determined based on N_2+d, wherein N_2 is a PUSCH preparation time predefined for a processing capability of the UE.

10. The UE of claim 9, wherein, N_2 is based on a subcarrier spacing configuration u, wherein u is one of u_DL and u_UL that results in a maximum T, wherein u_DL corresponds to a downlink subcarrier spacing at which a PDCCH carrying the DCI format is transmitted, and u_UL corresponds to an uplink subcarrier spacing at which the first uplink channel is to be transmitted.

11. A processing apparatus in a wireless communication system, the processing apparatus comprising: at least one processor; and at least one computer memory operably connectable to the at least one processor and configured to store instructions that, when executed, are operable to cause the at least one processor to perform operations comprising: reporting user equipment, UE, capability information, the UE capability information comprising i) information on a first additional number of symbols, d_1, needed for cancelling a lower priority uplink, UL, transmission that exceeds a physical uplink shared channel, PUSCH, preparation time, N_2, and ii) information on a second additional number of symbols, d_3, needed on top of N_2+d_1; detecting a downlink control information, DCI, format scheduling a transmission of a first uplink channel of a higher priority; and for a transmission of the first uplink channel of the higher priority that does not start T symbols after a last symbol of a physical downlink control channel, PDCCH, carrying the DCI format, and based on a determination that the transmission of the first uplink channel of the higher priority overlaps in time with a transmission of a second uplink channel of a lower priority, cancelling the transmission of the second uplink channel of the lower priority before an earliest symbol that overlaps with the transmission of the first uplink channel of the higher priority, wherein T is a preparation time related to the cancellation of the second uplink channel of the lower priority, wherein T is determined based on d, wherein based on at least one of the first uplink channel of the higher priority and the second uplink channel of the lower priority being a physical uplink control channel, PUCCH, d is equal to d_1, wherein d_1 is determined by the reported UE capability information, and wherein based on the first uplink channel of the higher priority and the second uplink channel of the lower priority being a first PUSCH of the higher priority and a second PUSCH of the lower priority, respectively, d is equal to d_1+d_3, wherein d_1 and d_3 are determined by the reported UE capability information.

12. A computer-readable storage medium configured to store at least one computer program comprising instructions that, when executed by at least one processor, cause the at least one processor to perform operations for a user equipment, UE, the operations comprising: reporting UE capability information, the UE capability information comprising i) information on a first additional number of symbols, d_1, needed for cancelling a lower priority uplink, UL, transmission that exceeds a physical uplink shared channel, PUSCH, preparation time, N_2, and ii) information on a second additional number of symbols, d_3, needed on top of N_2+d_1; detecting a downlink control information, DCI, format scheduling a transmission of a first uplink channel of a higher priority; and for a transmission of the first uplink channel of the higher priority that does not start T symbols after a last symbol of a physical downlink control channel, PDCCH, carrying the DCI format, and based on a determination that the transmission of the first uplink channel of the higher priority overlaps in time with a transmission of a second uplink channel of a lower priority, cancelling the transmission of the second uplink channel of the lower priority before an earliest symbol that overlaps with the transmission of the first uplink channel of the higher priority, wherein T is a preparation time related to the cancellation of the second uplink channel of the lower priority, wherein T is determined based on d, wherein based on at least one of the first uplink channel of the higher priority and the second uplink channel of the lower priority being a physical uplink control channel, PUCCH, d is equal to d_1, wherein d_1 is determined by the reported UE capability information, and wherein based on the first uplink channel of the higher priority and the second uplink channel of the lower priority being a first PUSCH of the higher priority and a second PUSCH of the lower priority, respectively, d is equal to d_1+d_3, wherein d_1 and d_3 are determined by the reported UE capability information. wherein T is a preparation time related to cancellation of the second uplink channel of lower priority, wherein T is determined based on d, wherein at least one of the first uplink channel based on higher priority and the second uplink channel based on lower priority is a physical uplink control channel, PUCCH, d is equal to d_1, wherein d_1 is determined by the reported UE capability information, and wherein the first uplink channel based on higher priority and the second uplink channel based on lower priority are a first PUSCH based on higher priority and a second PUSCH based on lower priority, respectively, d is equal to d_1+d_3, wherein d_1 and d_3 are determined by the reported UE capability information. 13.A method of receiving an uplink (UL) channel from a user equipment (UE) by a base station (BS) in a wireless communication system, the method comprising: receiving UE capability information from the UE, the UE capability information including i) information on a first additional number of symbols d_1 needed for cancellation of a lower priority UL transmission beyond a physical uplink shared channel (PUSCH) preparation time N_2, and ii) information on a second additional number of symbols d_3 needed on top of N_2+d_1; transmitting a downlink control information (DCI) format scheduling a first uplink channel based on higher priority to the UE; and for reception of the first uplink channel based on higher priority which does not start T before a last symbol of a physical downlink control channel (PDCCH) carrying the DCI format, and based on a determination that the reception of the first uplink channel based on higher priority overlaps in time with reception of a second uplink channel based on lower priority, canceling the reception of the second uplink channel based on lower priority before an earliest symbol of the second uplink channel based on lower priority which overlaps with the reception of the first uplink channel based on higher priority, wherein T is a preparation time related to cancellation of the second uplink channel of lower priority, wherein T is determined based on d, wherein at least one of the first uplink channel based on higher priority and the second uplink channel based on lower priority is a physical uplink control channel, PUCCH, d is equal to d_1, wherein d_1 is determined by the received UE capability information, and wherein the first uplink channel based on higher priority and the second uplink channel based on lower priority are a first PUSCH based on higher priority and a second PUSCH based on lower priority, respectively, d is equal to d_1+d_3, wherein d_1 and d_3 are determined by the received UE capability information. 14.A base station (BS) configured to receive an uplink (UL) channel from a user equipment (UE) in a wireless communication system, the BS comprising: 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 comprising: receiving, from the UE, UE capability information including i) information about a first additional number of symbols d_1 needed for cancelling a lower priority UL transmission that exceeds a physical uplink shared channel, PUSCH, preparation time N_2, and ii) information about a second additional number of symbols d_3 needed on top of N_2+d_1; sending, to the UE, a downlink control information, DCI, format scheduling a first uplink channel of a larger priority; and for reception of the first uplink channel of a larger priority that does not start T symbols after a last symbol of a physical downlink control channel, PDCCH, carrying the DCI format, and based on a determination that the reception of the first uplink channel of a larger priority overlaps in time with reception of a second uplink channel of a smaller priority, cancelling the reception of the second uplink channel of a smaller priority before an earliest symbol that overlaps with the reception of the first uplink channel of a larger priority, wherein T is a preparation time related to cancellation of the second uplink channel of a smaller priority, wherein T is determined based on d, wherein based on at least one of the first uplink channel of a larger priority and the second uplink channel of a smaller priority being a physical uplink control channel, PUCCH, d is equal to d_1, wherein d_1 is determined by the received UE capability information, and wherein based on the first uplink channel of a larger priority and the second uplink channel of a smaller priority being a first PUSCH of a larger priority and a second PUSCH of a smaller priority, respectively, d is equal to d_1+d_3, wherein d_1 and d_3 are determined by the received UE capability information.

15. The BS of claim 14, wherein, The second PUSCH is a configured grant based PUSCH without a corresponding PDCCH.

16. The BS of claim 14, wherein, The operations further comprise: performing the reception of the first uplink channel of a larger priority.

17. The BS of any one of claims 14-16, wherein, T is determined based on N_2+d, wherein N_2 is a PUSCH preparation time predefined for a processing capability of the UE.

18. The BS of claim 17, wherein, N_2 is based on a subcarrier spacing configuration u, wherein u is one of u_DL and u_UL that results in a largest T, wherein u_DL corresponds to a downlink subcarrier spacing in which the PDCCH carrying the DCI format is transmitted, and u_UL corresponds to an uplink subcarrier spacing in which the first uplink channel is to be transmitted.

Images