KR20220047166A - Method and apparatus for uplink transmissions with different reliability conditions - Google Patents

Abstract

Disclosed are a method and apparatus for uplink transmission with different trust conditions. An operating method of a terminal includes the steps of: selecting one or more control elements from among a plurality of control elements included in a first UCI in consideration of the size of an uplink resource; generating multiplexed UCIs by multiplexing a second UCI with the one or more control elements; and transmitting the multiplexed UCIs to the base station through the uplink resource.

Description

Method and apparatus for uplink transmissions with different trust conditions

The present invention relates to an uplink transmission technique in a communication system, and more particularly, to a technique for transmitting traffic having different trust conditions.

With the development of information and communication technology, various wireless communication technologies are being developed. Representative wireless communication technologies include long term evolution (LTE) and new radio (NR) defined in 3rd generation partnership project (3GPP) standards. LTE may be one of 4G (4th Generation) wireless communication technologies, and NR may be one of 5G (5th Generation) wireless communication technologies.

For the processing of wireless data rapidly increasing after commercialization of a 4G communication system (eg, a communication system supporting LTE), a frequency band of a 4G communication system (eg, a frequency band of 6 GHz or less) as well as a 4G communication system A 5G communication system (eg, a communication system supporting NR) using a frequency band (eg, a frequency band of 6 GHz or more) higher than the frequency band of ' is being considered. The 5G communication system may support enhanced Mobile BroadBand (eMBB), Ultra-Reliable and Low Latency Communication (URLLC), and Massive Machine Type Communication (mMTC).

On the other hand, in order to provide a communication service in the unlicensed band, a communication node (eg, a base station, a terminal) using a sensing procedure (eg, LBT (Listen before talk) procedure or CCA (clear channel assessment) procedure) using Radio resources should be used equitably. In this case, the sensing procedure may have different set variables according to the importance of data. A communication node (eg, a base station, a terminal) may transmit a signal and/or a channel through a sensing procedure. In a special case (eg, when a transmission operation is performed at a channel occupancy time (COT) secured by a base station and/or a terminal), a signal and/or a channel may be transmitted without a sensing procedure.

A beam-based sensing procedure in an unlicensed band can be divided into two types. For example, the sensing procedure may be divided into an omni-directional sensing procedure and a directional sensing procedure. When the omni-directional sensing procedure is applied, the base station may not perform a transmission operation when energy is detected in a direction that does not interfere with the terminal. This problem may be referred to as the “exposed node problem”. When the directional sensing procedure is applied, a hidden node problem may occur. In this case, even if energy is not detected in the sensing procedure of the base station, the transmission of the base station may interfere with other terminals (eg, hidden nodes).

Meanwhile, the terminal may transmit uplink control information (UCI) to the base station. UCIs may have different priorities. For example, UCIs may be classified into a high priority (HP) UCI having a high priority and a low priority (LP) UCI having a low priority. For transmission of HP UCI and LP UCI, a multiplexing method of UCIs may be required. In addition, a method of transmitting multiplexed UCIs may be required.

An object of the present invention to solve the above problems is to provide a method and apparatus for transmitting data having different trust conditions in a communication system.

In order to achieve the above object, a method of operating a terminal according to a first embodiment of the present invention includes the steps of selecting one or more control elements from among a plurality of control elements included in a first UCI in consideration of the size of an uplink resource , generating multiplexed UCIs by multiplexing the one or more control elements and a second UCI, and transmitting the multiplexed UCIs to a base station through the uplink resource.

"When the total size of the first UCI is the first size, and the first UCI having a second size smaller than the first size is multiplexable with the second UCI", the one or more of the plurality of control elements Control elements may be selected, and transmissions of the remaining control elements may be dropped.

When the plurality of control elements include CSI and HARQ-ACK, the one or more control elements are "the HARQ-ACK", "part of the CSI + the HARQ-ACK", "CSI part 1 of the CSI + the HARQ-ACK”, or “CSI part 2 of the CSI + the HARQ-ACK”.

The method of operating the terminal may further include receiving information indicating multiplexing of the first UCI and the second UCI from the base station, and when the information is received, the multiplexed UCIs are to be generated. can

The first UCI may be an LP UCI having a low priority, and the second UCI may be an HP UCI having a high priority.

The uplink resource may be a PUCCH resource or a PUSCH resource.

The uplink resource may be a PUCCH resource, and the PUCCH resource set to which the PUCCH resource belongs may be determined in consideration of the size of the one or more control elements and the size of the second UCI.

The method of operating the terminal may further include receiving a first DCI from the base station, and receiving a second DCI from the base station, wherein transmission of the first UCI is indicated by the first DCI and transmission of the second UCI may be indicated by the second DCI.

In order to achieve the above object, a method of operating a terminal according to a second embodiment of the present invention includes generating a first codeword for a first UCI based on a first code rate, and a second codeword based on a second code rate. 2 Generating a second codeword for UCI, generating multiplexed UCIs by multiplexing the first codeword and the second codeword, and transmitting the multiplexed UCIs to a base station using PUCCH resources includes

The first code rate and the second code rate may be related to the PUCCH resource.

The first code rate may be associated with a first PUCCH format for the first UCI, and the second code rate may be associated with a PUCCH resource for the second UCI.

The first code rate may be associated with a first PUCCH format for the first UCI, and the second code rate may be associated with a second PUCCH format for the second UCI.

The first PUCCH format for the first UCI may be derived by a first DCI received from the base station, and the second PUCCH format for the second UCI may be derived by a second DCI received from the base station. there is.

When the second code rate for the PUCCH resource for the second UCI is not specified, the second code rate may be related to a format of the PUCCH resource for the second UCI, and for the second UCI When the second code rate for the PUCCH resource is specified, the second code rate may be associated with the PUCCH resource for the second UCI.

The PUCCH resource may be configured for transmission of the second UCI, the first UCI may be an LP UCI having a low priority, and the second UCI may be an HP UCI having a high priority.

A terminal according to a third embodiment of the present invention for achieving the above object includes a processor, a memory in electronic communication with the processor, and instructions stored in the memory, and when the instructions are executed by the processor, The commands are multiplexed by the terminal selecting one or more control elements from among a plurality of control elements included in the first UCI in consideration of the size of the PUCCH resource, and multiplexing the one or more control elements with the second UCI. generate UCIs, and operate to cause transmission of the multiplexed UCIs to a base station via the PUCCH resource.

"When the total size of the first UCI is the first size, and the first UCI having a second size smaller than the first size is multiplexable with the second UCI", the one or more of the plurality of control elements Control elements may be selected, and transmissions of the remaining control elements may be dropped.

When the plurality of control elements include CSI and HARQ-ACK, the one or more control elements are "the HARQ-ACK", "part of the CSI + the HARQ-ACK", "CSI part 1 of the CSI + the HARQ-ACK”, or “CSI part 2 of the CSI + the HARQ-ACK”.

A first codeword for the one or more control elements may be generated based on a first code rate, a second codeword for the second UCI may be generated based on a second code rate, and the first code The rate or the second code rate may be related to the PUCCH resource.

A first codeword for the one or more control elements may be generated based on a first code rate, a second codeword for the second UCI may be generated based on a second code rate, and the first code A rate may be associated with a first PUCCH format for the first UCI, the second code rate may be associated with a second PUCCH format for the second UCI, and the first PUCCH format may be the second PUCCH It may be set to be the same as or different from the format.

According to the present application, the UE can multiplex LP (low priority) UCI (uplink control information) and HP (high priority) UCI, and use the multiplexed UCIs (eg, LP UCI + HP UCI) for uplink resources can be transmitted using In this case, the UE may transmit some control elements included in the LP UCI in consideration of the size of the uplink resource, and may drop transmission of the remaining control elements. The encoding procedure for each of LP UCI and HP UCI may be independently performed. For example, different code rates may be applied to each of LP UCI and HP UCI. According to the above-described operations, the multiplexing procedure of UCIs and the transmission procedure of the multiplexed UCIs can be efficiently performed, and the performance of the communication system can be improved.

1 is a conceptual diagram illustrating a first embodiment of a communication system.
2 is a block diagram showing a first embodiment of a communication node constituting a communication system.
3 is a flowchart illustrating a first embodiment of a method for determining a PUCCH resource.
4 is a flowchart illustrating a second embodiment of a method for determining a PUCCH resource.
5 is a flowchart illustrating a third embodiment of a method for determining a PUCCH resource.
6 is a conceptual diagram illustrating a first embodiment of a multiplexing method of LP UCI and HP UCI in a PUCCH resource.
7 is a conceptual diagram illustrating a first embodiment of a method for accumulating a TPC command applied to a PUCCH.
8A is a conceptual diagram illustrating a first embodiment of HARQ-ACK timing applied to a Type 1 HARQ codebook.
8B is a conceptual diagram illustrating a second embodiment of HARQ-ACK timing applied to a Type 1 HARQ codebook.
9 is a conceptual diagram illustrating a first embodiment of a method for configuring PUSCHs according to SLIVs indicated by a TDRA index.
10 is a conceptual diagram illustrating a first embodiment of a method for analyzing a PUSCH instance based on a TDRA index.
11 is a conceptual diagram illustrating a second embodiment of a method for analyzing a PUSCH instance based on a TDRA index.
12A is a conceptual diagram illustrating a first embodiment of control information for super transmission.
12B is a conceptual diagram illustrating a first embodiment of control information for retransmission.
13A is a conceptual diagram illustrating a second embodiment of control information for super transmission.
13B is a conceptual diagram illustrating a second embodiment of control information for retransmission.

Since the present invention can have various changes and can have various embodiments, specific embodiments are illustrated in the drawings and described in detail. However, this is not intended to limit the present invention to specific embodiments, and it should be understood to include all modifications, equivalents and substitutes included in the spirit and scope of the present invention.

Terms such as first, second, etc. may be used to describe various elements, but the elements should not be limited by the terms. The above terms are used only for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, a first component may be referred to as a second component, and similarly, a second component may also be referred to as a first component. and/or includes a combination of a plurality of related listed items or any of a plurality of related listed items.

In embodiments of the present application, “at least one of A and B” may mean “at least one of A or B” or “at least one of combinations of one or more of A and B”. Also, in the embodiments of the present application, “at least one of A and B” may mean “at least one of A or B” or “at least one of combinations of one or more of A and B”.

When a component is referred to as being “connected” or “connected” to another component, it may be directly connected or connected to the other component, but it is understood that other components may exist in between. it should be On the other hand, when it is said that a certain element is "directly connected" or "directly connected" to another element, it should be understood that the other element does not exist in the middle.

The terms used in the present application are only used to describe specific embodiments, and are not intended to limit the present invention. The singular expression includes the plural expression unless the context clearly dictates otherwise. In the present application, terms such as “comprise” or “have” are intended to designate that a feature, number, step, operation, component, part, or combination thereof described in the specification exists, but one or more other features It should be understood that this does not preclude the existence or addition of numbers, steps, operations, components, parts, or combinations thereof.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. Terms such as those defined in a commonly used dictionary should be interpreted as having a meaning consistent with the meaning in the context of the related art, and should not be interpreted in an ideal or excessively formal meaning unless explicitly defined in the present application. does not

Hereinafter, preferred embodiments of the present invention will be described in more detail with reference to the accompanying drawings. In describing the present invention, in order to facilitate the overall understanding, the same reference numerals are used for the same components in the drawings, and duplicate descriptions of the same components are omitted.

A communication system to which embodiments according to the present invention are applied will be described. The communication system to which the embodiments according to the present invention are applied is not limited to the content described below, and the embodiments according to the present invention can be applied to various communication systems. Here, a communication system may be used in the same sense as a communication network (network).

1 is a conceptual diagram illustrating a first embodiment of a communication system.

1, the communication system 100 is a plurality of communication nodes (110-1, 110-2, 110-3, 120-1, 120-2, 130-1, 130-2, 130-3, 130-4, 130-5, 130-6). In addition, the communication system 100 is a core network (core network) (eg, S-GW (serving-gateway), P-GW (packet data network (PDN)-gateway), MME (mobility management entity)) may include more. When the communication system 100 is a 5G communication system (eg, a new radio (NR) system), the core network is an access and mobility management function (AMF), a user plane function (UPF), a session management function (SMF), etc. may include

The plurality of communication nodes 110 to 130 may support a communication protocol (eg, an LTE communication protocol, an LTE-A communication protocol, an NR communication protocol, etc.) defined in a 3rd generation partnership project (3GPP) standard. A plurality of communication nodes 110 to 130 are CDMA (code division multiple access) technology, WCDMA (wideband CDMA) technology, TDMA (time division multiple access) technology, FDMA (frequency division multiple access) technology, OFDM (orthogonal frequency division) technology multiplexing) technology, Filtered OFDM technology, CP (cyclic prefix)-OFDM technology, DFT-s-OFDM (discrete Fourier transform-spread-OFDM) technology, OFDMA (orthogonal frequency division multiple access) technology, SC (single carrier)-FDMA Technology, Non-orthogonal Multiple Access (NOMA) technology, GFDM (generalized frequency division multiplexing) technology, FBMC (filter bank multi-carrier) technology, UFMC (universal filtered multi-carrier) technology, SDMA (Space Division Multiple Access) technology, etc. can support Each of the plurality of communication nodes may have the following structure.

2 is a block diagram showing a first embodiment of a communication node constituting a communication system.

Referring to FIG. 2 , the communication node 200 may include at least one processor 210 , a memory 220 , and a transceiver 230 connected to a network to perform communication. In addition, the communication node 200 may further include an input interface device 240 , an output interface device 250 , a storage device 260 , and the like. Each of the components included in the communication node 200 may be connected by a bus 270 to communicate with each other.

However, each of the components included in the communication node 200 may not be connected to the common bus 270 but to the processor 210 through an individual interface or an individual bus. For example, the processor 210 may be connected to at least one of the memory 220 , the transceiver 230 , the input interface device 240 , the output interface device 250 , and the storage device 260 through a dedicated interface. .

The processor 210 may execute a program command stored in at least one of the memory 220 and the storage device 260 . The processor 210 may mean a central processing unit (CPU), a graphics processing unit (GPU), or a dedicated processor on which methods according to embodiments of the present invention are performed. Each of the memory 220 and the storage device 260 may be configured as at least one of a volatile storage medium and a non-volatile storage medium. For example, the memory 220 may be configured as at least one of a read only memory (ROM) and a random access memory (RAM).

Referring back to FIG. 1 , the communication system 100 includes a plurality of base stations 110 - 1 , 110 - 2 , 110 - 3 , 120 - 1 and 120 - 2 , and a plurality of terminals 130 - 1, 130-2, 130-3, 130-4, 130-5, 130-6). Each of the first base station 110-1, the second base station 110-2, and the third base station 110-3 may form a macro cell. Each of the fourth base station 120-1 and the fifth base station 120-2 may form a small cell. The fourth base station 120-1, the third terminal 130-3, and the fourth terminal 130-4 may belong to the cell coverage of the first base station 110-1. The second terminal 130-2, the fourth terminal 130-4, and the fifth terminal 130-5 may belong to the cell coverage of the second base station 110-2. The fifth base station 120-2, the fourth terminal 130-4, the fifth terminal 130-5, and the sixth terminal 130-6 may belong to the cell coverage of the third base station 110-3. there is. The first terminal 130-1 may belong to the cell coverage of the fourth base station 120-1. The sixth terminal 130-6 may belong to the cell coverage of the fifth base station 120-2.

Here, each of the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 is a NodeB (NB), an evolved NodeB (eNB), gNB, an advanced base station (ABS), HR - BS (high reliability-base station), BTS (base transceiver station), radio base station (radio base station), radio transceiver (radio transceiver), access point (access point), access node (node), RAS (radio access station) ), MMR-BS (mobile multihop relay-base station), RS (relay station), ARS (advanced relay station), HR-RS (high reliability-relay station), HNB (home NodeB), HeNB (home eNodeB), It may be referred to as a road side unit (RSU), a radio remote head (RRH), a transmission point (TP), a transmission and reception point (TRP), and the like.

Each of the plurality of terminals 130-1, 130-2, 130-3, 130-4, 130-5, 130-6 includes a user equipment (UE), a terminal equipment (TE), an advanced mobile station (AMS), HR-MS (high reliability-mobile station), terminal, access terminal, mobile terminal, station, subscriber station, mobile station, portable It may be referred to as a portable subscriber station, a node, a device, an on board unit (OBU), and the like.

Meanwhile, each of the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 may operate in different frequency bands or may operate in the same frequency band. Each of the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 may be connected to each other through an ideal backhaul link or a non-ideal backhaul link. , information can be exchanged with each other through an ideal backhaul link or a non-ideal backhaul link. Each of the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 may be connected to the core network through an ideal backhaul link or a non-ideal backhaul link. Each of the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 transmits a signal received from the core network to the corresponding terminals 130-1, 130-2, 130-3, 130 -4, 130-5, 130-6), and a signal received from the corresponding terminal (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) is transmitted to the core network can be sent to

In addition, each of the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 transmits a multi-input multi-output (MIMO) (eg, single user (SU)- MIMO, multi user (MU)-MIMO, massive MIMO, etc.), coordinated multipoint (CoMP) transmission, carrier aggregation (CA) transmission, transmission in an unlicensed band, direct communication between terminals (device) to device communication, D2D) (or Proximity services (ProSe)), Internet of Things (IoT) communication, dual connectivity (DC), and the like may be supported. Here, each of the plurality of terminals 130-1, 130-2, 130-3, 130-4, 130-5, 130-6 is the base station 110-1, 110-2, 110-3, and 120-1. , 120-2) and corresponding operations, and operations supported by the base stations 110-1, 110-2, 110-3, 120-1, and 120-2 may be performed. For example, the second base station 110-2 may transmit a signal to the fourth terminal 130-4 based on the SU-MIMO method, and the fourth terminal 130-4 may transmit a signal based on the SU-MIMO method. A signal may be received from the second base station 110 - 2 . Alternatively, the second base station 110 - 2 may transmit a signal to the fourth terminal 130 - 4 and the fifth terminal 130 - 5 based on the MU-MIMO scheme, and the fourth terminal 130 - 4 . and each of the fifth terminals 130 - 5 may receive a signal from the second base station 110 - 2 by the MU-MIMO method.

Each of the first base station 110-1, the second base station 110-2, and the third base station 110-3 may transmit a signal to the fourth terminal 130-4 based on the CoMP scheme, and the fourth The terminal 130-4 may receive signals from the first base station 110-1, the second base station 110-2, and the third base station 110-3 by the CoMP method. Each of the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 is a terminal 130-1, 130-2, 130-3, 130-4 belonging to its own cell coverage. , 130-5, 130-6) and the CA method can transmit and receive signals. Each of the first base station 110-1, the second base station 110-2, and the third base station 110-3 controls D2D between the fourth terminal 130-4 and the fifth terminal 130-5. and each of the fourth terminal 130-4 and the fifth terminal 130-5 may perform D2D under the control of the second base station 110-2 and the third base station 110-3, respectively. .

Next, operating methods of a communication node in a communication system will be described. Even when a method (eg, transmission or reception of a signal) performed in a first communication node among communication nodes is described, a corresponding second communication node is a method (eg, a method corresponding to the method performed in the first communication node) For example, reception or transmission of a signal) may be performed. That is, when the operation of the terminal is described, the corresponding base station may perform the operation corresponding to the operation of the terminal. Conversely, when the operation of the base station is described, the corresponding terminal may perform the operation corresponding to the operation of the base station.

Chapter 1: Introduction

To support service scenarios of eMBB (enhanced Mobile BroadBand), URLLC (Ultra-Reliable and Low Latency Communication), and mMTC (massive machine type communication), technical requirements are being studied in 3GPP. The purpose of the eMBB service may be processing of large-capacity traffic, the purpose of the URLLC service may be to reduce end-to-end latency and error rate, and the purpose of the mMTC service may be processing of intermittent or periodic traffic in a geographic area with high UE density. can be One communication system can support one or more service scenarios simultaneously. For service scenario(s), one communication system may be operated by variously adjusting configuration parameters (eg, numerology) of the OFDM waveform. One neuronology may be used in the LTE communication system, and one or more neuronologies may be applied according to a situation in the NR communication system.

A time division duplex (TDD)-based communication system (hereinafter, referred to as a “TDD system”) may support both an eMBB service and a URLLC service. In this case, the low-latency performance of the URLLC service may be improved. Since uplink hybrid automatic repeat request-acknowledgement (UL HARQ-ACK) is required to support downlink (DL) traffic, the delay time experienced by DL traffic may be determined by a period in which the DL slot and the UL slot repeatedly appear. Even in the case of UL traffic, since the BS indicates the UL grant to the UE in the DL slot, the delay time experienced by the UL traffic may be determined by a cycle in which the DL slot and the UL slot are repeated. In the NR communication system, the type of slot may be dynamically converted to suit a situation. The UE may know the DL symbol, the UL symbol, or the FL (flexible) symbol in units of symbols. The FL symbol may be redirected to a DL symbol or a UL symbol. In the LTE communication system, the type of subframe may be converted to suit the situation. The type of subframe may be a DL subframe, a UL subframe, and a special subframe. There is no concept of a FL subframe (or FL symbol) in the LTE communication system.

Among UL channels transmitted by the UE, a physical uplink shared channel (PUSCH) and a physical uplink control channel (PUCCH) may be considered. PUSCH can be dynamically scheduled. Alternatively, it may be indicated that the PUSCH is periodically transmitted. The periodic PUSCH transmission method may be divided into two methods according to a periodic PUSCH transmission indication method. In order to activate the semi-static PUSCH in the LTE communication system, downlink control information (UL-DCI) may be utilized. Considering URLLC traffic in the NR communication system, in order to reduce the dependence on the error rate of UL-DCI, periodic PUSCH transmission may be indicated only by higher layer signaling instead of UL-DCI.

On the other hand, in order to provide a communication service in the unlicensed band, a communication node (eg, a base station, a terminal) using a sensing procedure (eg, LBT (Listen before talk) procedure or CCA (clear channel assessment) procedure) using Radio resources should be used equitably. In this case, the sensing procedure may have different set variables according to the importance of data. A communication node (eg, a base station, a terminal) may transmit a signal and/or a channel through a sensing procedure. In a special case (eg, when a transmission operation is performed at a channel occupancy time (COT) secured by a base station and/or a terminal), a signal and/or a channel may be transmitted without a sensing procedure.

A beam-based sensing procedure in an unlicensed band can be divided into two types. For example, the sensing procedure may be divided into an omni-directional sensing procedure and a directional sensing procedure. When the omni-directional sensing procedure is applied, the base station may not perform a transmission operation when energy is detected in a direction that does not interfere with the terminal. This problem may be referred to as the “exposed node problem”. When the directional sensing procedure is applied, a hidden node problem may occur. In this case, even if energy is not detected in the sensing procedure of the base station, the transmission of the base station may interfere with other terminals (eg, hidden nodes).

Uplink control information (UCI) may include a scheduling request (SR), channel state information (CSI), hybrid automatic repeat request-acknowledgement (HARQ-ACK), and/or link recovery request (LRR). Each of SR, CSI, HARQ-ACK, and LRR included in UCI may be referred to as a control element. That is, UCI may include one or more control elements (eg, SR, CSI, HARQ-ACK, and/or LRR). UCI may be used to manage downlink. Information (eg, SR, CSI, HARQ-ACK, and/or LRR) included in UCI may vary according to a UCI type. UCI may be transmitted through a physical uplink control channel (PUCCH) and/or a physical uplink shared channel (PUSCH). When PUCCH and PUSCH overlap in one or more symbols, UCI may be transmitted through PUSCH instead of PUCCH. In this case, the PUCCH may not be transmitted. When the frequency band (eg, FR1) in which the PUCCH is transmitted is different from the frequency band (eg, FR2) in which the PUSCH is transmitted, the PUSCH and the PUCCH may be transmitted simultaneously. When the PUCCH and the PUSCH overlap in one or more symbols, the UE may compare the priority of the PUCCH and the priority of the PUSCH. Transmission having a lower priority among PUCCH transmission and PUSCH transmission may be dropped. The size of UCI may be expressed as the sum of the number of bits representing the UCI type. The size of the UCI may be used to determine the PUCCH resource.

One UCI type may correspond to one PUCCH resource on a one-to-one basis. When PUCCH resources corresponding to different UCI types overlap in the time domain, the UE may select an appropriate PUCCH resource set again based on the sum of sizes of the corresponding UCI types. In addition, the UE may apply the PUCCH resource index indicated in downlink control information (DCI). When UCI types not scheduled by DCI are multiplexed, transmission resources of the multiplexed UCI types may be indicated by a PUCCH resource index configured by RRC signaling. This operation may mean that multiplexed UCI types are periodically transmitted. The base station may indicate (eg, configure) "multiplexing of UCI types" and/or "PUCCH resource for transmission of UCI type(s)" to the terminal through RRC signaling.

The PUCCH resource may be determined as follows. The base station may transmit PUCCH-configCommon and/or PUCCH-config to the terminal through RRC signaling (eg, system information block (SIB)1 transmission or dedicated signaling). The PUCCH resource set(s) for the UE may be indicated by PUCCH-configCommon and/or PUCCH-config. The UE may select one PUCCH resource set from among the PUCCH resource sets indicated by the base station according to the UCI size. The PUCCH resource set may include a plurality of PUCCH resources. Each of the plurality of PUCCH resources may be indicated by a PUCCH resource index. The base station may inform the terminal of the PUCCH resource index through DCI or RRC signaling. The UE may check the PUCCH resource indicated by the PUCCH resource index received from the base station among the plurality of PUCCH resources.

A configured grant (CG)-UCI may be used for CG PUSCH transmission in an unlicensed band. The CG-UCI may include transport block (TB) information and/or channel occupancy time (COT) information. The TB information may include a HARQ process number, a redundancy version (RV), and/or a new data indicator (NDI). The COT information may include COT sharing information. CG-UCI may be transmitted in PUSCH.

The UE may transmit UCI and/or CG-UCI. The priority of UCI may be different from that of CG-UCI. UCI and/or CG-UCI may be used for TB transmission. Therefore, the TB priority may be considered as “UCI priority” or “CG-UCI priority”. In the allocation procedure of PUSCH resources, physical downlink shared channel (PDSCH) resources, or physical sidelink shared channel (PSSCH) resources by DCI and / or RRC signaling, TB priority may be set, and TB priority is "UCI priority " or "CG-UCI priority". Periodic CSI and/or semi-persistent CSI may have a low priority. SR priority and LRR priority may be set by RRC signaling. The priority of HARQ-ACK for PSSCH may be set to be the same as TB priority. "When the priority of HARQ-ACK exceeds the threshold of the priority indicated by RRC signaling" is distinguished from "when the priority of HARQ-ACK does not exceed the threshold of the priority indicated by RRC signaling" can be The priority of HARQ-ACK for PSSCH may not correspond to TB priority on a one-to-one basis as an exception. In this case, the TB priority may be derived from the priority of the HARQ-ACK for the PSSCH.

UCI and CG-UCI having different priorities may not be multiplexed. In this case, the UE may transmit one piece of control information having a high priority among UCI and CG-UCI (eg, high priority (HP) UCI or HP CG-UCI). Alternatively, the UE may transmit one piece of control information (eg, low priority (LP) UCI or LP CG-UCI) having a lower priority among UCI and CG-UCI. The UE may assume that HP UCI types are multiplexed, and may generate HP PUCCH (eg, virtual HP PUCCH) based on the assumption. The UE may assume that LP UCI types are multiplexed, and may generate an LP PUCCH (eg, a virtual LP PUCCH) based on the assumption. When the HP PUCCH overlaps the LP PUCCH in the time domain, the UE may transmit the HP PUCCH including the HP UCI type(s). Therefore, only UCI types having the same priority can be multiplexed. Alternatively, one UCI type among UCI types may be dropped as needed. The base station may anticipate the UCI type dropped from the terminal. Accordingly, the base station may instruct the terminal to transmit the dropped UCI type (eg, UCI or CG-UCI) by performing a scheduling operation for the dropped UCI type.

In the present application, "a method of multiplexing LP UCI and HP UCI", "a method of transmitting multiplexed UCIs (eg, LP UCI + HP UCI) in a PUCCH", and "a method of transmitting multiplexed UCIs in a PUSCH" This will be suggested. In the present application, UCI and UCI type may have the same meaning, UCI may mean "UCI" or "CG-UCI", and a UCI-related operation may be interpreted as a CG-UCI-related operation. That is, the UCI-related operation may be applied for CG-UCI transmission, and the CG-UCI-related operation may be applied for UCI transmission.

Chapter 2: Method of Determination of PUCCH Resources

For multiplexing of HP UCI and LP UCI, the UE considers "when one UCI type is indicated by DCI" and/or "when a PUCCH resource or PUSCH resource for all UCI types is indicated by RRC signaling" can Methods for determining a PUCCH resource to which both LP UCI and HP UCI are multiplexed will be proposed.

In embodiments, the PUCCH transmitted by the UE may be distinguished from the PUCCH resource, the DCI indicating transmission of LP UCI may be referred to as LP DCI, and the DCI indicating transmission of HP UCI may be referred to as HP DCI. can In addition, SR may mean "scheduling request" or "link recovery request", or "scheduling request and link recovery request".

2.1: Methods for determining the PUCCH resource set considering both the LP UCI size and the HP UCI size

The UCI type may correspond one-to-one with the PUCCH resource. Methods for determining PUCCH resources of UCI types having different priorities will be described. Here, the LP UCI size may be expressed by x bits, and the HP UCI size may be expressed by y bits. Each of x and y may be a natural number. Alternatively, the LP UCI size may be a value of a function based on x considering a code rate applied to LP UCI, etc., and the HP UCI size may be a value of a function based on y considering a code rate applied to HP UCI. The meaning of x + y may mean "an arithmetic sum of x and y". Alternatively, the meaning of x + y may mean “a value derived based on the value of the function based on x and the value of the function based on y”.

Method 2.1-1: The UE may multiplex UCI types having the same priority. The UE may derive one PUCCH resource for each priority and may derive a PUCCH resource capable of multiplexing all UCIs.

Method 2.1-2: The UE sets the PUCCH resource by utilizing both the LP UCI size (eg, a value derived from x) and the HP UCI size (eg, a value derived from y) confirmed in method 2.1-1 can be decided The UE may multiplex all or part of the LP UCI with all of the HP UCI, and may transmit the multiplexed UCIs in the PUCCH resource.

The base station may instruct the terminal to multiplex HP UCI and LP UCI. In this case, the UE may determine the PUCCH resource set in consideration of both the HP UCI size and the LP UCI size. The UE may select a PUCCH resource from within the PUCCH resource set based on a PUCCH resource indicator (PRI) or a PUCCH resource index indicated by DCI and/or RRC signaling. For example, x + y bits may be a criterion for determining a PUCCH resource set. When x + y is 1 bit or 2 bits, the PUCCH resource set may be distinguished from the PUCCH resource set when x + y is 3 bits.

Some UCI types of LP UCI or some of UCI types of LP UCI may be dropped. For example, when the UE intends to transmit LP UCI including CSI (or LP UCI including CSI and HARQ-ACK), all or part of CSI may be dropped. In this case, when CSI is divided into CSI part 1 and CSI part 2, CSI part 1 and/or CSI part 2 may be dropped. The UE may transmit the LP UCI including the non-dropped CSI part(s). Here, the LP UCI may be multiplexed with the HP UCI. For another example, when the UE intends to transmit an LP UCI including an SR and an HP UCI including an SR, the SR of the LP UCI may be dropped. Accordingly, the UE may transmit some bits among x bits in the PUCCH resource. However, when method 2.1-2 is followed, the UE may determine the PUCCH resource set using x + y.

Method 2.1-3: In method 2.1-1, the UE transmits control elements (eg, some control elements) in the PUCCH resource among all control elements (eg, CSI and HARQ-ACK) included in the LP UCI. ) can be selected. That is, when LP UCI and HP UCI are multiplexed in a PUCCH resource, the UE may select transmittable control elements in consideration of the size of the PUCCH resource. Some control elements may include "HARQ-ACK", "part of CSI + HARQ-ACK", "CSI part 1 + HACK-ACK", or "CSI part 2 + HARQ-ACK". Some control elements may be selected taking into account x'. The UE may determine the PUCCH resource set by utilizing both the size of the LP UCI including the selected control elements and the size of the HP UCI (eg, a value derived from y). In addition, the UE may select a PUCCH resource from within the PUCCH resource set. The UE may generate multiplexed UCIs (eg, LP UCI + HP UCI) by multiplexing LP UCI (eg, LP UCI including selected control elements) and HP UCI, and PUCCH the multiplexed UCIs It can be transmitted to the base station through the resource. In the above operations, the PUCCH resource set may be interpreted as a PUSCH resource set, and the PUCCH resource may be interpreted as a PUSCH resource.

The base station may instruct the terminal to multiplex HP UCI and LP UCI. The UE may consider both the HP UCI size and the LP UCI size. In particular, the UE may first calculate the transmission size of the LP UCI. The LP UCI size is x bits, but when LP UCI and HP UCI are multiplexed, the transmittable LP UCI size may be x' bits. x' may be less than x. For example, in transmission of LP UCI including CSI, some CSI, (partial) CSI part 1, or (partial) CSI part 2 may be dropped. Alternatively, all of the CSI may be dropped. For another example, in the transmission of LP UCI including CSI and HARQ-ACK, all CSI or part of CSI of LP UCI (eg, CSI part 1 or CSI part 2) may be dropped, and HARQ of LP UCI may be dropped. -Only ACK can be multiplexed with HP UCI. The UE may calculate the size of LP UCI (eg, LP UCI to which some control elements are dropped), and x' + y bits may be used as a criterion for determining a PUCCH resource set. The UE may select a PUCCH resource from within the PUCCH resource set based on the PRI or PUCCH resource index indicated by DCI and/or RRC signaling.

3 is a flowchart illustrating a first embodiment of a method for determining a PUCCH resource.

Referring to FIG. 3 , the UE may determine a PUCCH resource through which HP UCI is transmitted based on a technical standard. The size of HP UCI may be y bits. The UE may determine whether all or part of the PUCCH resources corresponding to the LP UCI overlap with the PUCCH resource including the HP UCI in the time domain. The UE may select the most advanced PUCCH resource (eg, the overlapping PUCCH resource) from among the PUCCH resources including HP UCI and the PUCCH resources overlapping in the time domain (S301). The size of the LP UCI may be x bits. When there is no overlapping PUCCH resource, the method of determining the PUCCH resource may be terminated. That is, if the PUCCH resource corresponding to the LP UCI does not overlap with the PUCCH resources in the time domain, the UE may transmit all or part of the HP UCI and the LP UCI using the last determined PUCCH resource. When overlapping PUCCH resources exist, the UE may select a new PUCCH resource set based on x + y bits (S302). The UE may determine a new PUCCH resource within the new PUCCH resource set (S303). The new PUCCH resource may be used for transmission of multiplexed UCIs (eg, LP UCI + HP UCI). If necessary, the UE may drop a part of the LP UCI (S304). In this case, an LP UCI having a size of x' bits may be transmitted. That is, the size of the multiplexed UCIs may be x' + y bits. The UE may determine again whether the PUCCH resource obtained by the above operation overlaps the PUCCH resource corresponding to the LP UCI in the time domain (S301).

4 is a flowchart illustrating a second embodiment of a method for determining a PUCCH resource.

Referring to FIG. 4 , the UE may determine the PUCCH resource through which the HP UCI is transmitted based on the technical standard. The size of the HP UCI may be y bits. The UE may determine whether all or part of the PUCCH resources corresponding to the LP UCI overlap with the PUCCH resource including the HP UCI in the time domain. The UE may select the most advanced PUCCH resource (eg, the overlapping PUCCH resource) from among the PUCCH resources including HP UCI and the PUCCH resources overlapping in the time domain (S401). When there is no overlapping PUCCH resource, the method of determining the PUCCH resource may be terminated. If overlapping PUCCH resources exist, the UE may perform S402. In S402, the UE may drop a part of the LP UCI if necessary. In addition, the UE may not consider the PUCCH resource corresponding to a part of the LP UCI. Therefore, the UE may not derive a new PUCCH resource. If the PUCCH resource derived in the previous step exists, the UE may maintain the corresponding PUCCH resource. When a part of the LP UCI is dropped, the size of the remaining LP UCI may be x'. In S402, an effective LP UCI may be derived, and x' may be the size of an effective LP UCI. When it is determined not to multiplex LP UCI and HP UCI (eg, when it is determined that LP UCI transmission is dropped), the UE may perform again from S401. When it is determined to multiplex LP UCI and HP UCI, the UE may perform S403.

The UE may configure a new PUCCH resource set based on x' + y bits (S403). The y bits may be the size of HP UCI. The UE may determine a new PUCCH resource within the new PUCCH resource set (S404). The new PUCCH resource may be used for transmission of multiplexed UCIs (eg, LP UCI + HP UCI). When S404 is completed, the terminal may perform again from S401.

The embodiment illustrated in FIG. 3 may be method 2.1-2, and the embodiment illustrated in FIG. 4 may be method 2.1-3. In the embodiment shown in FIG. 3 , in order to reduce the size of the LP UCI, the UE may reduce the size of the LP UCI after determining the PUCCH resource. In the embodiment shown in FIG. 4 , the UE may determine the PUCCH resource after deriving an effective LP UCI.

The PUCCH resource derived from the multiplexing procedure of LP UCI may overlap with other PUCCH resources. In this case, the terminal may perform the multiplexing procedure again. If the PUCCH resource derived from the multiplexing procedure of the LP UCI overlaps the PUCCH resource including the HP UCI, the UE may select the LP UCI again.

2.1.1: Methods for solving the problem that PUCCH resource for LP UCI overlaps with PUCCH resource including HP UCI again

PUCCH resources considered in the multiplexing procedure or selection procedure of HP UCI and LP UCI may overlap other PUCCH resources in the time domain. The UE may derive new PUCCH resources for transmitting all or part of UCI by solving the problem of overlapping PUCCH resources.

The PUCCH resource determined in the multiplexing procedure of LP UCI may overlap with other HP UCI-related PUCCH resources in the time domain. In this case, even when a PUCCH resource for multiplexing of LP UCI and/or HP UCI is determined, the UE may consider multiplexing with a new HP UCI. The reason is that the derived PUCCH resource occupies many symbols in the time domain, so that it may overlap with the PUCCH resource located in another (sub) slot in the time domain. Accordingly, the UE may perform the UCI multiplexing and selection procedure again, and all of the LP UCI, a part of the LP UCI, or some types of the LP UCI may be dropped as a result of the multiplexing and selection procedure.

In order to determine the UCI size in the step of determining the PUCCH resource, the UE may repeat the procedure for considering the PUCCH resource again. According to this operation, the amount of calculation can be increased. Therefore, when the UE determines the UCI size and/or PUCCH resource, it may be preferable not to recalculate the UCI size and/or PUCCH resource.

In order to solve the above-mentioned problem, it may be preferable that the PUCCH resource to which the LP UCI and/or the HP UCI are multiplexed is indicated by the HP DCI. This operation may be referred to as method 2.2-1 or method 2.2-2, which will be described later. According to method 2.2-2, the PUCCH resource to which the HP UCI is mapped may not cross the boundary of the (sub)slot in the time domain. Therefore, it may be interpreted that one PUCCH resource is defined for each (sub) slot. Since the PUCCH resource considered for multiplexing HP UCI and LP UCI does not cross the boundary of the (sub) slot, the corresponding PUCCH resource may not overlap with the new PUCCH resource including the new HP UCI in the time domain.

Alternatively, the operation of the terminal may be configured so that the above-described situation (eg, a situation in which PUCCH resources overlap) does not occur in the terminal. The terminal may not perform a separate operation, and the serving base station may indicate to the terminal "a PUCCH resource to which all HP UCIs are mapped" or "a PUCCH resource to which HP UCI is not mapped". That is, when the additional multiplexing operation of LP UCI is performed, it is assumed that the "PUCCH resource indicated to the terminal" or "PUCCH resource derived from the terminal" does not overlap the PUCCH resource to which the HP UCI is mapped more than once in the time domain. can be

On the other hand, when HP UCI and LP UCI are multiplexed, "a method of considering a separate PUCCH resource set" or "a method of not selecting a PUCCH resource set according to the UCI size" may be considered.

5 is a flowchart illustrating a third embodiment of a method for determining a PUCCH resource.

Referring to FIG. 5 , a UE may determine a PUCCH resource through which HP UCI is transmitted based on a technical standard. The size of HP UCI may be y bits. The UE may determine whether all or part of the PUCCH resources corresponding to the LP UCI overlap with the PUCCH resource including the HP UCI in the time domain. The UE may select the most advanced PUCCH resource (eg, the overlapping PUCCH resource) from among the PUCCH resources including HP UCI and the PUCCH resources overlapping in the time domain (S501). The size of the LP UCI may be x bits. When the first overlapping PUCCH resource does not exist, the method of determining the PUCCH resource may be terminated. When the first overlapping PUCCH resource exists, the UE may perform S502. In S502, the UE may drop a part of the LP UCI if necessary. In addition, the UE may not consider the PUCCH resource corresponding to a part of the LP UCI. Therefore, the UE may not derive a new PUCCH resource. If the PUCCH resource derived in the previous step exists, the UE may maintain the corresponding PUCCH resource. When a part of the LP UCI is dropped, the size of the remaining LP UCI may be x'. In S502, an effective LP UCI may be derived, and x' may be the size of an effective LP UCI. When it is determined not to multiplex LP UCI and HP UCI (eg, when it is determined that LP UCI transmission is dropped), the UE may perform again from S501. When it is determined to multiplex LP UCI and HP UCI, the UE may perform S503. In S503, the UE may determine a new PUCCH resource. The new PUCCH resource may be used for transmission of multiplexed UCIs (eg, LP UCI + HP UCI). When S503 is completed, the UE may perform again from S501.

In the method of determining the PUCCH resource shown in FIG. 5 , the procedure of calculating the HP UCI size and the LP UCI size to determine the PUCCH resource set may be omitted. The method of determining the PUCCH resource shown in FIG. 5 may be subdivided into method 2.1-4 and method 2.1-5.

Method 2.1-4: When HP UCI and LP UCI are configured to be multiplexed, the base station may set a separate PUCCH resource set to the terminal, and the terminal may consider the PUCCH resource index or PRI within the PUCCH resource set set by the base station. .

The serving base station may instruct (eg, configure) the multiplexing of HP UCI and LP UCI to the terminal using RRC signaling. In this case, the serving base station may indicate (eg, configure) a new PUCCH resource set to the terminal using RRC signaling. An encoding method (eg, Reed Muller, Polar, Simplex, etc.) may vary depending on the UCI size, and a block error rate (BLER) required according to the UCI size may be different. Therefore, the PUCCH resource set may be divided by the UCI size. The above-described operations may be applied when only UCI having the same priority is considered.

When the base station instructs the UE to multiplex LP UCI and HP UCI, UCIs having different requested BLERs may be multiplexed in one PUCCH resource. In this case, it may be desirable to introduce a new PUCCH resource set.

Method 2.1-5: The UE may apply the PRI or PUCCH resource index in one PUCCH resource set regardless of the UCI size.

The PUCCH resource set introduced by the base station may be intended not to be multiplexed more than twice with the PUCCH resource related to HP UCI. For example, the time resource of the PUCCH resource may be configured to always be included in one (sub) slot. Therefore, PUCCH resources used for transmission in the UE may be multiplexed with PUCCH resources related to one or less HP UCIs.

The codeword of LP UCI may be different from the codeword of HP UCI. Alternatively, although LP UCI and HP UCI have the same codeword, the information word of LP UCI may be different from the information word of HP UCI. According to method 2.1-5, "when the codeword of LP UCI is different from the codeword of HP UCI and the terminal applies PRI indicated by DCI or RRC signaling", the terminal may use a specific PUCCH resource set. Therefore, a procedure for selecting a separate PUCCH resource set may be unnecessary.

When LP UCI and HP UCI are composed of one codeword, in order to follow Method 2.1-5, the UE may derive a predetermined value based on the HP UCI size and/or the LP UCI size, and use the predetermined value to determine the PUCCH resource set.

According to method 2.1-5, the length of the information word (eg, "information word of HP UCI", "information word of LP UCI", or "information word concatenating HP UCI and LP UCI") is a preset length. If longer or shorter, the PUCCH formats may be different. In this case, the terminal can manage the information word by adding preset bit(s) to the information word so that the length of the corresponding information word is not always shorter than a predetermined length. For example, the terminal may increase the length of the information word to 11 bits by adding 0 or 1 to the information word. As another example, the terminal may increase the length of the information word to 12 bits or more by adding 0 or 1 to the information word. Therefore, the PUCCH resource(s) belonging to the PUCCH resource set indicated to the UE may not include a specific PUCCH format. For example, the serving base station may indicate to the terminal a PUCCH resource set consisting of PUCCH format 2, PUCCH format 3, and/or PUCCH format 4.

2.1.2: Examples using legacy aggregation

"When the size of LP UCI is nLP bits and the size of HP UCI is nHP bits", to determine the PUCCH resource set to which the PUCCH resource in which LP UCI and HP UCI are multiplexed belongs, the terminal is derived from nLP and / or nHP value can be used. Each of nLP and nHP may be a natural number.

Method 2.1-6: In the selection procedure of the PUCCH resource set, LP UCI and HP UCI may be regarded as the same weight. Accordingly, a case in which nLP + nHP exceeds a predetermined threshold may be considered.

nLP may be 1 bit, and nHP may be 1 bit. In this case, nLP + nHP may be regarded as 2 bits. Therefore, all PUCCH resources belonging to the PUCCH resource set may be used for PUCCH format 0 and/or PUCCH format 1. The UE may assume that the importance of the LP UCI is the same as that of the HP UCI. In this case, the LP UCI may also be considered to have a high priority. Alternatively, the UE may transmit only HP UCI and may drop LP UCI.

nLP may be 2 bits or less, nHP may be 2 bits or less, and nLP+nHP may be 3 bits or more. In this case, the UE may select a PUCCH resource having PUCCH format 2, PUCCH format 3, or PUCCH format 4 from the PUCCH resource set. When the codeword of LP UCI is different from the codeword of HP UCI, the code rate may be applied as a value indicated in RRC signaling.

When nLP and nHP have values other than the above-mentioned values, the terminal applies the code rate indicated by the base station (eg, the code rate indicated by RRC signaling) to the codeword of LP UCI, the code of HP UCI , or "one codeword for LP UCI and HP UCI" can be generated.

Method 2.1-7: In the selection procedure of the PUCCH resource set, LP UCI and HP UCI may be regarded as different weights. Accordingly, nLP and nHP may be corrected in consideration of the code rate, and a case in which "nLP corrected in consideration of the encoding rate + nHP corrected in consideration of the encoding rate" exceeds a predetermined threshold may be considered.

nLP may be 1 bit, and nHP may be 1 bit. In this case, the UE may multiplex UCIs having a size of 2 bits (eg, LP UCI + HP UCI) based on PUCCH format 0 or format 1. Alternatively, the UE may express HP UCI (or LP UCI) as a cyclic shift, and may express LP UCI (or HP UCI) as a physical resource block (PRB) selection (selection). Alternatively, the UE may transmit only HP UCI and may drop LP UCI transmission.

nLP may be 1 bit, and nHP may be 2 bits. Alternatively, nLP may be 2 bits and nHP may be 1 bit. In this case, the UE may express nHP bits as a cyclic shift based on PUCCH format 0 or PUCCH format 1, and may express nLP bits as PRB selection. Alternatively, the UE may transmit only HP UCI and may drop LP UCI transmission. Alternatively, if "the codeword of HP UCI is different from that of LP UCI" or "when the codeword of HP UCI is the same as the codeword of LP UCI", the terminal performs multiplexed UCIs (eg, HP UCI + LP UCI) PUCCH format 2, PUCCH format 3, or PUCCH format 4 may be transmitted in a PUCCH resource. In this case, a repetition code or a simplex code may be applied. If necessary, a simplex code with zero added or a Reed Muller code may be applied.

When nLP and nHP have values other than the above-mentioned values, the terminal applies the code rate indicated by the base station to the codeword of LP UCI, the codeword of HP UCI, or "one code for LP UCI and HP UCI" can be created. When each codeword is generated, the terminal can check whether a value obtained by dividing each codeword by a code rate indicated by the base station and adding it exceeds a preset boundary value. Here, the code rate of LP UCI may be expressed as rLP, and the code rate of HP UCI may be expressed as rHP.

For example, the UE may determine the PUCCH resource set using a value determined based on nLP/rLP and nHP/rHP (eg, nLP/rLP + nHP/rHP). In this case, nLP/rLP + nHP/rHP may not be an integer. The UE may generate each codeword and transmit each code using PUCCH format 2, PUCCH format 3, or PUCCH format 4.

As another example, nHP+nLPХg may be defined, and g may be determined as a ratio of rLP to rHP. The value of g may not be an integer. The UE may generate each codeword, and may transmit each codeword using PUCCH format 2, PUCCH format 3, or PUCCH format 4.

Here, nLP may be interpreted as the size of LP UCI or “LP UCI + cyclic redundancy check (CRC) field”, and nHP may be interpreted as the size of HP UCI or “HP UCI + CRC field”. .

The UE may determine the PUCCH resource set using the value obtained by applying method 2.1-7. That is, the UE may select one PUCCH resource set from among the PUCCH resource sets.

One PUCCH resource set may include a plurality of PUCCH resources. Accordingly, the UE may receive the PUCCH resource index from the base station, and may select one PUCCH resource capable of transmitting UCI (eg, LP UCI and/or HP UCI) based on the PUCCH resource index.

Here, the base station may transmit PUCCH configuration information (eg, PUCCH format or PUCCH resource) including a code rate applied to each UCI to the terminal. The terminal may check the code rate applied to each UCI based on the configuration information of the PUCCH received from the base station. The code rate of LP UCI and the code rate of HP UCI may be set by the base station. The LP UCI code rate may be set independently of the HP UCI code rate.

2.2: When DCI is received, PUCCH resource determination method

The UE may receive a plurality of DCIs. DCI indicating transmission of LP UCI may be received relatively early. DCI may indicate the reception of the PDSCH and transmission of the PUCCH, and may include a (sub) slot offset in which the PUCCH is transmitted.

The base station may transmit an RRC signaling message and/or DCI (eg, a field included in DCI) indicating multiplexing of HP UCI and LP UCI to the terminal. The UE may confirm that multiplexing of HP UCI and LP UCI is indicated based on the DCI and/or the RRC signaling message received from the base station. For example, one value in the RRC signaling message or one value in the field of DCI may indicate multiplexing of HP UCI and LP UCI. A different value in the RRC signaling message or a different value in the field of DCI may indicate that HP UCI and LP UCI are not multiplexed.

As another example, one value of a field indicating a beta offset included in DCI may indicate that HP UCI and LP UCI are not multiplexed. For example, when the beta offset for LP UCI has 0, LP UCI may not be multiplexed. In this case, the terminal may transmit only HP UCI. That is, LP UCI transmission may be dropped.

Method 2.2-1: HP DCI may indicate multiplexing of LP UCI and HP UCI.

DCI including a field indicating multiplexing of HP UCI and LP UCI may be non-fallback DCI (eg, DCI format other than DCI format 1_0) and/or HP DCI. For example, when the priority field included in the DCI received from the terminal indicates a low priority (eg, 0), the terminal may ignore the value of the field indicating the multiplexing of HP UCI and LP UCI. On the other hand, if the priority field included in the DCI received from the terminal indicates a high priority (eg, 1), the terminal generates the PUCCH according to the value of the field indicating the multiplexing of HP UCI and LP UCI. can

For example, in DCI scheduling PUSCH, total-downlink assignment index (T-DAI) of HP UCI and T-DAI of LP UCI may be independently indicated. To support this operation, the size of the T-DAI field may be doubled. When the base station instructs the terminal to generate the T1 HARQ codebook, the terminal may multiplex the UCI having the corresponding priority in the PUSCH according to the value of T-DAI. Alternatively, the UE may drop UCI transmission having a corresponding priority according to the value of T-DAI. When the base station instructs the terminal to generate the T2 HARQ codebook, a field other than the T-DAI field in DCI may indicate multiplexing or dropping of UCI transmission having a corresponding priority. Here, UCI may be multiplexed in PUSCH.

Method 2.2-2: The UE may apply the PRI indicated by the HP DCI.

A PUCCH resource in which LP UCI and HP UCI are multiplexed may be indicated by HP DCI. The target BLER of HP UCI may be different from the target BLER of LP UCI. When the HP UCI is included and transmitted in the PUCCH resource derived from the PRI indicated by the LP DCI, the base station may obtain a high BLER. The terminal may obtain one codeword by encoding the information word of LP UCI and the information word of HP UCI. Alternatively, the codeword of the LP UCI may be different from the codeword of the HP DCI. The PUCCH resource (eg, resource element (RE)) indicated in the LP DCI may not be sufficient. For example, insufficient REs may be allocated for the codeword of HP UCI. However, the PRI included in the HP DCI may indicate the PUCCH resource so that a sufficient number of REs are allocated for at least the codeword of the HP UCI.

For example, both Method 2.2-1 and Method 2.2-2 may be applied to the HP DCI received by the UE. Information necessary for PUCCH transmission may be indicated by HP DCI. For example, HP DCI may include "information indicating whether LP UCI is multiplexed", "PRI for HP UCI", and/or "LP UCI and PRI for HP UCI when LP UCI is multiplexed". can

Method 2.2-3: The UE may apply the PRI of the last received DCI.

The DCI that the UE determines was last received may be an HP DCI or an LP DCI. The UE may receive a plurality of DCIs and may multiplex LP UCI and/or HP UCI on the same PUCCH. In this case, the UE may select the last DCI received in the time domain from among a plurality of DCIs. When carrier aggregation (CA) is configured, the UE may receive two or more DCIs from control resource sets (CORESETs) starting from the same symbol. When two or more DCIs are last received in the time domain, the UE may select one DCI from among two or more DCIs based on CORESET ID, search space set ID, or DAI of DCI. . For example, the DCI selected by the UE may be “DCI received from CORESET with lowest ID”, “DCI received from search space set with lowest ID”, or “DCI with highest DAI”. The base station may derive an appropriate PRI to indicate multiplexing of LP UCI and/or HP UCI. Therefore, the UE may apply the PRI of the DCI received last in the time domain.

Method 2.2-4: The UE may apply the PRI of the LP DCI.

The UE may apply the PRI of the LP DCI. HP UCI may be coded, and the coded HP UCI may be multiplexed in PUCCH to which PRI of LP DCI is applied. In this case, the LP UCI codeword may be multiplexed with the HP UCI codeword by puncturing or rate matching.

6 is a conceptual diagram illustrating a first embodiment of a multiplexing method of LP UCI and HP UCI in a PUCCH resource.

Referring to FIG. 6 , a codeword of HP UCI (eg, encoded HP UCI) may be modulated and mapped to some resources of PUCCH resources indicated by LP DCI, HP DCI, or RRC signaling. The codeword of the LP UCI may be modulated and mapped to the remaining resources of the PUCCH resource. A PUCCH resource may be configured for each hop, and a demodulation-reference signal (DM-RS) resource is omitted from the PUCCH resource shown in FIG. 6 . The coded LP UCI may be a punctured LP UCI or a rate-matched LP UCI.

Although HP UCI and LP UCI are mapped to different symbols in the embodiment shown in FIG. 6 , the present application may not necessarily be limited to the above-described embodiment. Depending on the relative amounts of HP UCI and LP UCI, both the encoded HP UCI and the encoded LP UCI may be mapped in the same symbol(s). In this case, the encoded HP UCI and the encoded LP UCI may be mapped in all PRBs belonging to the PUCCH resource in order to obtain a frequency multiplexing gain.

In the embodiment shown in FIG. 6 , PUCCH format 2, PUCCH format 3, and/or PUCCH format 4 may be applied. When PUCCH format 4 is used, since PUCCH format 4 is spread and mapped in the frequency domain, the HP UCI code can also be spread and mapped in the frequency domain.

Method 2.2-5: When method 2.2-4 is applied, according to the PUCCH format indicated by the PRI of the LP DCI, the UE may apply the PRI of the LP DCI or the PRI of the HP DCI.

The PRI of the LP DCI may indicate a PUCCH resource and a PUCCH format. When PUCCH format 0 or PUCCH format 1 is indicated by the PRI of the LP DCI, the UE may multiplex only 1 bit or 2 bits of the UCI. In this case, the UE may determine the PUCCH resource set based on the LP UCI size. Therefore, when the sum of the LP UCI size and the HP UCI size is 3 bits or more, the PRI of the LP DCI cannot be applied. In this case, the terminal may not be able to perform method 2.2-4. On the other hand, if "PUCCH format 2, PUCCH format 3, or PUCCH format 4 is used and the UCI size is 3 bits or more", the UE may multiplex UCI. Therefore, the UE can apply the PRI of the LP DCI and can additionally multiplex the HP UCI. In the LP DCI transmission procedure, the base station may know the LP UCI size. In this case, since HP UCI may additionally occur in the terminal, the base station may determine the PUCCH resource by predicting the size of the HP UCI.

In order to improve the above-described operation, when the PRI of LP DCI indicates PUCCH format 0 or PUCCH format 1, since the UE cannot multiplex HP UCI, the UE applies PRI of HP DCI to LP UCI and HP UCI. can be multiplexed.

Method 2.2-6: When method 2.2-4 is applied, according to the PUCCH format indicated by the PRI of the LP DCI, the UE may transmit the LP UCI and the HP UCI by applying the PRI of the LP DCI. Alternatively, the UE may drop the LP UCI transmission, and may transmit only the HP UCI by applying the PRI of the HP DCI.

The PRI of the LP DCI may indicate a PUCCH resource and a PUCCH format. When LP DCI indicates PUCCH format 0 or PUCCH format 1, it may be difficult to multiplex LP UCI and HP UCI having PUCCH format 0 or PUCCH format 1. That is, for multiplexing of HP UCI and LP UCI, the PUCCH format is preferably indicated by PUCCH format 2, PUCCH format 3, or PUCCH format 4. Therefore, when LP DCI indicates PUCCH format 0 or PUCCH format 1, the UE may drop LP UCI to transmit HP UCI. That is, the UE may transmit only the HP UCI for the HP DCI regardless of the LP DCI. This operation may be interpreted as "an operation in which the terminal compares the priority of the PUCCH including only the LP UCI with the priority of the PUCCH including only the HP UCI, and transmits only the PUCCH including only the HP UCI according to the comparison result".

The UE may transmit "only HP UCI" or "both LP UCI and HP UCI" according to RRC signaling, HP DCI, or an instruction of LP DCI.

2.2.1: Example in which fallback DCI is received

A specific DCI format may not include a field indicating multiplexing of LP UCI and HP UCI. In this case, LP UCI and HP UCI may not be multiplexed, and the UE may transmit only HP UCI in PUCCH.

A specific DCI format may not include a field to distinguish between LP UCI and HP UCI. In this case, the priority of a specific DCI format may be defined in a technical standard. Alternatively, the priority of a specific DCI format may vary according to a search space set in which the specific DCI format is transmitted.

If "PUCCH resource is indicated by LP DCI and LP DCI is DCI format 1_0 (eg, fallback DCI)", the UE may not multiplex LP UCI and HP UCI. In this case, the UE may transmit only HP UCI in PUCCH.

"When PUCCH resource is indicated by HP DCI and HP DCI is DCI format 1_0 (eg, fallback DCI)", LP UCI and HP UCI may not be multiplexed. In this case, the UE may transmit only HP UCI in PUCCH.

When the last DCI affecting transmission of PUCCH is a fallback DCI (eg, DCI format 1_0), LP UCI and HP UCI may not be multiplexed. In this case, the UE may transmit only HP UCI in PUCCH.

2.3: Determination method of PUCCH resource when DCI is not received

DCI may not be received by the UE, and the UE may transmit HARQ-ACK for PDSCH indicated by RRC signaling or PUCCH indicated by RRC signaling. The priority of the SR and/or the priority of the LRR may be determined by RRC signaling. The priority of CSI may be regarded as the priority of LP UCI. The priority of semi-persistent scheduling (SPS) PDSCH may be determined by RRC signaling or DCI (hereinafter referred to as “activation DCI”) activating the SPS PDSCH. Therefore, the UE may anticipate a time resource in which HP UCI or LP UCIs indicated by RRC signaling are multiplexed and/or types of multiplexed UCIs.

Method 2.3-1: When transmission of UCI is determined by RRC signaling or activation DCI, whether HP UCI and LP UCI are multiplexed may be indicated by corresponding RRC signaling or activation DCI.

HP UCI and LP UCI having different periods may be transmitted in PUCCH. In this case, HP UCI transmission and LP UCI transmission may occur in the same symbol(s). In this case, the UE may transmit "only HP UCI" or "multiplexed HP UCI and LP UCI" according to RRC signaling.

The SPS PDSCH may be configured by RRC signaling and may be activated by active DCI. The UE may receive the SPS PDSCH in a periodic time resource. For example, one field of active DCI may indicate whether HP UCI and LP UCI are multiplexed. As another example, information included in the RRC signaling message for configuring the SPS PDSCH may indicate whether HP UCI and LP UCI are multiplexed.

Method 2.3-2: When HP UCI and LP UCI are multiplexed in method 2.3-1, the UE may generate one codeword by concatenating HP UCI and LP UCI. Alternatively, the terminal may multiplex the codeword of HP UCI and the codeword of LP UCI. Here, the codeword of HP UCI may be different from the codeword of LP UCI.

If the HP UCI or LP UCI is too short, the UE may add preset bit(s) to the HP UCI or LP UCI having a short length, and then may perform an encoding procedure for the corresponding UCI. In this case, the length of the increased UCI may be 3 bits or 12 bits.

When HP UCI and LP UCI are multiplexed, since the size of UCI (eg, multiplexed UCIs) transmitted in PUCCH increases, a separate PUCCH resource may be defined. For example, in order to transmit the HARQ-ACK of the SPS PDSCH, the UE may determine the PUCCH resource by performing the step of determining the size of the UCI. If "the size of LP UCI is N bits and the size of HP UCI is M bits", the UE may independently derive a PUCCH resource for transmitting N bits and a PUCCH resource for transmitting M bits. The PUCCH resource set to which the PUCCH resource for transmitting N bits belongs may be different from the PUCCH resource set to which the PUCCH resource for transmitting M bits belongs. Each of N and M may be a natural number.

Therefore, in order to multiplex HP UCI and HP UCI, different PUCCH resources may be derived. A code rate applied to HP UCI may be different from a code rate applied to LP UCI. Therefore, it may not be desirable to derive a PUCCH resource for transmitting N + M bits.

Method 2.3-3: When HP UCI and LP UCI are multiplexed in method 2.3-1, the UE may select PUCCH resource(s) in a separate PUCCH resource set. Here, the PUCCH format for the PUCCH resource(s) may be limited to a specific format (eg, PUCCH format 2, PUCCH format 3, PUCCH format 4).

2.3.1: HARQ-ACK, CSI, and/or SR multiplexing method of SPS PDSCH

The SR may correspond to a PUCCH resource on a one-to-one basis, and the PUCCH including the SR may be in PUCCH format 0 or PUCCH format 1. The upper layer of the terminal may deliver only one SR to the physical layer of the terminal. Accordingly, the UE may transmit one SR in the PUCCH resource. After the SR having priority A (eg, LP SR) is delivered to the physical layer, the SR (eg, HP SR) having a higher priority than priority A (eg, priority B) is can occur In this case, the upper layer of the terminal may transmit the HP SR back to the physical layer of the terminal. When the PUCCH resource for LP SR transmission overlaps with the PUCCH resource for HP SR transmission in the time domain (eg, the same symbol(s)), the UE may transmit only the HP SR. That is, the transmission of the LP SR may be dropped.

Next, CSI transmission may be considered. The base station may indicate (or configure) the PUCCH resource for CSI transmission to the terminal by using RRC signaling. The UE may check the PUCCH resource indicated by the base station, and may map the coded CSI to the PUCCH resource. When the PUCCH resource indicated by the base station (eg, resource for CSI transmission) overlaps with another UCI or resource for data transmission, the UE multiplexes "CSI and other UCI" or "CSI and data". can Here, the other UCI may include HARQ-ACK and/or SR for the SPS PDSCH. If the other UCI is HARQ-ACK for the PDSCH indicated by the DCI, the UE may determine the PUCCH resource based on the PRI of the corresponding DCI. Alternatively, when data is a PUSCH indicated by a DCI, the UE may determine a PUSCH resource based on the PRI of the corresponding DCI.

In the CSI transmission procedure, a plurality of CSI reports may be multiplexed. To support this operation, the base station may transmit the PUCCH resource list to the terminal using RRC signaling, and the terminal may obtain the PUCCH resource list from the base station. For example, the PUCCH resource list may include two PUCCH resources. The UE may select one PUCCH resource belonging to the PUCCH resource list according to the size of the CSI report.

The priority of CSI may be considered as low priority. For example, UCI including CSI may be LP UCI. The SPS PDSCH may have a high priority or a low priority according to the indication of the base station. The priority of the HARQ-ACK for the SPS PDSCH (hereinafter, referred to as “SPS HARQ-ACK”) may follow the priority of the SPS PDSCH. In embodiments, the CSI/SPS HARQ-ACK may include “CSI”, “SPS HARQ-ACK with low priority”, or “SPS HARQ-ACK with CSI and low priority”.

CSI/SPS HARQ-ACK and LP SR may occur, and PUCCH resources corresponding to CSI/SPS HARQ-ACK and LP SR may share the same symbol(s). In this case, the UE may generate one information word by concatenating the CSI/SPS HARQ-ACK and the LP SR, and may derive one codeword by performing the same encoding procedure for one information word. One codeword may be mapped to a PUCCH resource. CSI/SPS HARQ-ACK and HP SR may occur, and PUCCH resources corresponding to CSI/SPS HARQ-ACK and HP SR may share the same symbol(s). In this case, the UE may transmit only the HP SR and may not transmit the CSI/SPS HARQ-ACK. CSI/SPS HARQ-ACK, LP SR, and HP SR may occur, and PUCCH resources corresponding to CSI/SPS HARQ-ACK, LP SR, and HP SR may share the same symbol(s). In this case, the UE may transmit only the HP SR and may not transmit the CSI/SPS HARQ-ACK and the LP SR.

The base station may instruct (eg, configure) the multiplexing of HP UCI and LP UCI to the terminal. Here, the PUCCH resource associated with CSI/SPS HARQ-ACK and LP SR may have the same symbol(s), and the PUCCH resource associated with CSI/SPS HARQ-ACK and HP SR may have the same symbol(s), PUCCH resources associated with CSI/SPS HARQ-ACK, LP SR, and HP SR may have the same symbol(s).

Since each of LP UCI and HP UCI is independently encoded, the same UCI type may include different codewords (eg, a codeword of LP UCI and a codeword of HP UCI). Therefore, CSI/SPS HARQ-ACK and SR may be included in different codewords.

Method 2.3-4: CSI/SPS HARQ-ACK and SR/LRR (eg, HP SR/LRR and/or LP SR/LRR) may belong to different codewords.

A code rate applied to CSI/SPS HARQ-ACK may be a code rate applied to LP UCI, and a code rate applied to HP SR and LP SR may be a code rate applied to HP UCI. When the information word is generated by concatenating the HP SR and the LP SR, only one state in which the SR does not occur in the terminal can be expressed.

Meanwhile, according to Method 2.3-2, different encoding procedures may be performed for CSI/SPS HARQ-ACK (or "CSI/SPS HARQ-ACK and LP SR") and HP SR, and different encoding procedures Independent codewords may be derived by , and the independent codewords may be mapped to one PUCCH resource. Therefore, "CSI/SPS HARQ-ACK" or "CSI/SPS HARQ-ACK and LP SR" may be derived from one codeword, and the HP SR may be derived from another codeword. The derived codewords may be mapped to a PUCCH resource. In order to map the HP SR codeword, a puncturing operation or a rate matching operation may be performed on the codeword of “CSI/SPS HARQ-ACK codeword” or “CSI/SPS HARQ-ACK and LP SR” codeword. .

PUCCH resources for kHP HP SRs may overlap in the same symbol(s), and PUCCH resources for kLP LP SRs may overlap in the same symbol(s). Each of kHP and kLP may be a natural number. What SR has occurred in the terminal may be expressed. In this case, a case in which SR does not occur in the terminal may also be expressed.

Method 2.3-5: When LP SR and HP SR are concatenated and included in one codeword, the information word concatenated with LP SR and HP SR may be expressed as a ceiling(log2(1 + kLP + kHP)) bit.

Here, 1 may mean a case in which SR does not occur in the terminal. In order to express the SR regardless of priority, the case of l + kLP + kHP may be expressed.

Method 2.3-6: When LP SR and HP SR belong to different codewords, the information word of HP SR can be expressed as ceiling(log2(1+kHP)) bit, and the information word of LP SR is ceiling(log2(1) +kLP)) bit.

A case in which no SR has occurred to the UE may be expressed in both the HP SR and the LP SR. Accordingly, the base station can determine whether the SR has occurred by decoding one of the codeword of the HP SR and the codeword of the LP SR.

On the other hand, a case in which SR does not occur in the UE may be regarded as LP UCI or HP UCI. In this case, the terminal may reduce the length of the information word. When it is considered as LP UCI that SR does not occur in the terminal, the ceiling (log2(kHP)) bit may be required to express the HP SR. If it is considered as HP UCI that no SR occurs in the terminal, the ceiling (log2(kLP)) bit may be required to express the LP SR. When an SR is expressed for one priority, it may not be necessary to express an SR for another priority. This behavior will be defined in Method 2.3-7.

Method 2.3-7: When LP SR and HP SR belong to different codewords, the information word of HP SR can be expressed as ceiling(log2(kHP)) bit, and the information word of LP SR is celing(log2(1+kLP) )) can be expressed in bits. Alternatively, when LP SR and HP SR belong to different codewords, the information word of LP SR can be expressed as ceiling(log2(kLP)), and the information word of HP SR) is expressed as ceiling(log2(1+kHP). can be expressed

The payload may include both the LP SR and the HP SR, and the LP SR and the HP SR may have independent values. In this case, the UE may display the positive SR in both the LP SR and the HP SR.

2.4: How to Multiplex Resources of LP UCI and HP UCI

UCI (eg, HP UCI) or TB (eg, HP data) having different priorities may be transmitted, and transmission of overlapping LP UCI or LP data in the time domain may be dropped.

To support this operation, UCI types having the same priority may be considered. When the corresponding UCI types overlap in the time domain, the UE may multiplex the corresponding UCI types. One PUCCH resource may be derived by the above-described operations. Thereafter, when PUCCH resources having different priorities overlap in the time domain, transmission may be performed only on the PUCCH resource corresponding to the high priority, and transmission may be dropped from the PUCCH corresponding to the low priority.

In embodiments, “overlapping of PUCCH resources in the time domain” may mean “collision of UCIs”. SR may mean SR and/or LRR.

When the HP SR and the LP SR collide (eg, when two or more positive SRs having different priorities occur), the UE may transmit only the HP SR.

A case in which HP SR collides with LP UCI may be considered. Here, the LP UCI may include SR, HARQ-ACK, and/or CSI. Therefore, the PUCCH resource corresponding to the LP UCI may be used for transmission of PUCCH format 2, PUCCH format 3, or PUCCH format 4, and the SR may be included in the payload. The type of SR (eg, positive SR or negative SR) may be distinguished by 0 or 1.

The LP SR may not be multiplexed with the HP SR. According to Method 2.4-1, Method 2.4-2, and Method 2.4-3, which will be described later, HP UCI may not be multiplexed with LP UCI. When the HP SR is multiplexed, in order not to multiplex the LP SR, the size of the LP UCI may be reduced, and the PUCCH resource determination procedure for the LP UCI having the reduced size may be performed again.

Method 2.4-1: When the LP UCI including the LP SR and the HP SR collide, the UE may transmit the HP SR and may drop the transmission of the LP UCI.

Method 2.4-2: When the LP UCI including the LP SR and the HP SR collide, the UE may transmit the HP SR and may multiplex the remaining control information except for the LP SR in the LP UCI.

When method 2.4-2 is applied, the PUCCH resource associated with the LP UCI may be a resource in consideration of the LP SR. From the viewpoint of the payload, the LP SR may be excluded from the payload, and the LP SR from the viewpoint of the PUCCH resource may be used in the multiplexing procedure.

When the PUCCH resource associated with the LP SR is excluded, the PUCCH resource for the UCI type except for the LP SR may be considered in the procedure for determining the PUCCH resource associated with the LP UCI. The UE may perform the PUCCH resource determination procedure again.

Method 2.4-3: When the LP UCI including the LP SR and the HP SR collide, the collision between the LP SR and the HP SR may be resolved first. When a positive HP SR occurs, the PUCCH resource associated with the LP SR may not be considered in the multiplexing procedure of the LP UCI.

This operation may mean "the MAC layer of the terminal transmits only one positive SR among the HP SR and the LP SR to the PHY layer of the terminal". When the HP SR is a positive SR, the PUCCH resource associated with the LP SR may be considered as not configured in the UE. Thereafter, the UE may determine one PUCCH resource by multiplexing the LP UCI. Therefore, the UE may perform a procedure of multiplexing LP UCI and HP UCI or selecting UCI (prioritization).

The methods described above can be easily extended. For example, the above-described methods may be applied to HP UCI including HP SR.

Chapter 3: PUCCH generation method

In the PUCCH generation procedure, the UE may spread UCI and map the spread UCI to a resource grid. Alternatively, the UE may generate a codeword by performing an encoding operation on UCI, may generate a modulated codeword by performing a modulation operation on the codeword, and may map the modulated codeword to a resource grid. there is. Here, the modulation method may be quadrature phase shift keying (QPSK). However, the modulation method may not be limited to QPSK. For example, the modulation scheme may be set to QPSK or π/2-BPSK (binary phase shift keying) by RRC signaling.

3.1: Determination method of code rate

LP UCI and HP UCI may be generated using different codewords. For example, the codeword of LP UCI and the codeword of HP UCI may be independently generated. The PUCCH format may be indicated by RRC signaling, and the UE may determine a code rate of each of LP UCI and HP UCI in consideration of the PUCCH format. The code rate of UCI may be determined in DCI or RRC signaling to which UCI is allocated. Alternatively, the UCI code rate may be determined independently of DCI or RRC signaling. When the UE transmits two or more UCI types or UCIs having two or more priorities, a PUCCH resource set and/or PUCCH resource may be interpreted differently according to a multiplexing procedure. When the PUCCH format is changed, a code rate applied to UCI may be changed. The code rate applied to UCI may be indicated by the following method(s).

Method 3.1-1: The UE may apply a code rate associated with a PUCCH format for a PUCCH resource in which UCI is transmitted.

The multiplexing procedure of HP UCI and LP UCI may be completed, and PUCCH resources may be determined. In this case, the UE may encode the LP UCI and the HP UCI by applying a code rate associated with the PUCCH format. HP DCI for generation/transmission of HP UCI may be received in the terminal later than LP DCI for generation/transmission of LP UCI. In this case, in order to utilize the PUCCH resource, the UE may not perform the encoding of the LP UCI in advance. The reason is that the UE cannot know the PUCCH format for the PUCCH resource through which the LP UCI is transmitted. However, since a code rate suitable for the PUCCH format can also be applied to the LP UCI, the BLER obtained from the base station may be sufficiently low.

In a method for solving the above-described problem, when LP UCI and HP UCI are multiplexed, the base station PRI or PUCCH so that the "PUCCH format associated with LP UCI" and "PUCCH format for multiplexing of LP UCI and HP UCI" are always the same The resource index may be transmitted to the terminal. Alternatively, when the PUCCH formats are indicated differently, the method(s) below may be used.

Method 3.1-2: The UE may apply a code rate associated with a PUCCH format indicated by DCI or RRC signaling indicating (eg, scheduling) transmission of UCI.

A code rate applied to LP UCI may follow a code rate for a PUCCH format indicated by LP DCI or RRC signaling. Therefore, the UE may apply the code rate applied to the LP UCI regardless of the PUCCH format (eg, the PUCCH format associated with HP UCI) for the PUCCH resource through which the corresponding LP UCI is transmitted. Since the above-described method is applied even when the PUCCH resource through which the LP UCI is transmitted has a different PUCCH format from the aforementioned PUCCH format, the encoding procedure of the LP UCI may be performed in advance. When the PUCCH resource in which the HP UCI and the LP UCI are multiplexed is determined, the UE may modulate the encoded LP UCI and map the modulation result to the RE of the PUCCH resource.

For example, the PUCCH on which the LP UCI is actually transmitted may be “PUCCH1 on which the LP UCI is to be transmitted” or “PUCCH2 on which the LP UCI and the HP UCI are multiplexed”. If method 3.1-1 is applied, the code rate applied to LP UCI may be related to the PUCCH format for PUCCH2. If method 3.1-2 is applied, the code rate applied to LP UCI may be related to the PUCCH format for PUCCH1.

There may be two code rates for UCI. In this case, based on Method 3.1-2, two code rates associated with the PUCCH format may be indicated. One of the two code rates may be an offset with respect to the code rate. For example, the UE may apply one of the two code rates to HP UCI, and may apply another code rate (or a code rate derived from an offset) to LP UCI. The offset may be set by system information, RRC message, MAC CE, and/or DCI.

Method 3.1-3: Two code rates may be associated with a PUCCH format.

The code rate applied to UCI may not be the code rate associated with the PUCCH format. The code rate may be a variable for configuring resources of PUCCH, and may be included in configuration information of PUCCH. In this case, UCI may have a different code rate for each PUCCH resource.

Method 3.1-4: A code rate (or an offset of a code rate) applied to UCI in a PUCCH resource may be associated with one or more values.

When the code rate offset is indicated (or set), the UE may determine the code rate by applying the offset to the code rate associated with the PUCCH format.

When UCI multiplexed in PUCCH consists of only LP UCI or only HP UCI, one code rate may be required. In this case, the UE may select one of a code rate associated with the PUCCH format and a code rate associated with the PUCCH resource.

Method 3.1-5: In Method 3.1-4, when the code rate for the PUCCH resource is not specified, the UE may apply the code rate associated with the PUCCH format, and when the code rate for the PUCCH resource is specified, the UE is PUCCH A code rate associated with a format may not be applied.

When UCI multiplexed in PUCCH includes LP UCI and HP UCI, two code rates may be required in the UE. Therefore, when the code rate associated with the PUCCH resource is one, the UE may apply the code rate associated with the PUCCH format together. For example, a code rate applied in LP UCI may be a code rate associated with a PUCCH resource, and a code rate applied in HP UCI may be a code rate associated with a PUCCH format. Alternatively, the code rate applied in the LP UCI may be an associated code rate in the PUCCH resource, and the code rate applied in the HP UCI may be an associated code rate in the PUCCH format.

When two code rates are associated with the PUCCH resource, the UE may use only the code rates associated with the PUCCH resource. In this case, two code rates or two offsets for a code rate may be defined. Alternatively, one code rate and one offset for the code rate may be defined.

3.2: Mapping method of encoded UCI

Since the modulation rate is fixed, if the UCI code rate is determined, the number of REs to which the UCI codewords are mapped may be determined. In embodiments, the number of REs required to map a codeword of an LP UCI may be referred to as nLP, and the number of REs required to map a codeword of an HP UCI may be referred to as nHP. The number of independent REs that a PUCCH resource has may be referred to as n. For example, when spreading code is applied, the number of REs before applying the spreading code rate may be n. Each of nLP, nHP, and n may be a natural number. "The codeword of UCI is mapped to the RE" or "UCI is mapped to the RE" may mean "a modulation symbol that is a modulation result of the codeword of UCI is mapped to the RE".

The UE may map the LP UCI and the HP UCI in the PUCCH, and in order to obtain a sufficiently low BLER in the base station, REs of “nLP + nHP” or more may be included in the PUCCH (eg, PUCCH resource). The number of REs that the PUCCH resource has (eg, the size of the PUCCH resource) may be determined by the PRI or PUCCH resource index. The number of REs that the PUCCH resource has may be different from "nLP + nHP". In this case, the UE may additionally map the codeword of the LP UCI or the codeword of the HP UCI to the PUCCH resource.

"When rate matching is performed for LP UCI and HP UCI" may be distinguished from "when puncturing is performed for at least one UCI from among LP UCI and HP UCI". When rate matching is performed, the coded UCI may always be received by the base station. When puncturing is performed, a part of the encoded UCI may not be received by the base station.

Method 3.2-1: For the n REs of the PUCCH resource, the UE may assume that HP UCI does not exist, and may map the codeword of the LP UCI according to the assumption, and a preset location (eg, For example, a codeword of HP UCI may be mapped from nHP REs within a preset area).

In this case, the codeword of LP UCI may be mapped or may be mapped to nHP REs, but instead of the codeword of LP UCI, the codeword of HP UCI may be mapped to nHP REs. Since the base station already knows the preset location, it can extract and decode only the valid part from the codeword of the LP UCI. The base station may inform the terminal of information on the preset location using RRC signaling, and the terminal may know that the HP UCI codeword is mapped in consecutive nHP REs within the preset location indicated by the base station.

Method 3.2-2: The UE may map LP UCI codewords to nLP REs among RE(s) of the PUCCH resource, and may map HP UCI codewords to the remaining n - nLP REs. n may be the total number of REs of the PUCCH resource.

When the PUCCH resource is indicated by the HP DCI, REs necessary for mapping the codeword of the LP UCI may be secured, and the codeword of the HP UCI may be mapped from the remaining REs. The base station may indicate to the terminal an appropriate PUCCH resource so that sufficient REs (eg, a minimum of nHP REs) are allocated to HP UCI. Therefore, the BLER experienced by HP UCI can be minimized.

"When the terminal receives the LP DCI first and then receives the HP DCI", a range of n in consideration of nLP may be defined, and the HP DCI may indicate a PUCCH resource satisfying the range of n.

Method 3.2-3: The UE may map HP UCI codewords to nHP REs among RE(s) of the PUCCH resource, and may map LP UCI codewords to the remaining n - nHP REs. n may be the total number of REs of the PUCCH resource.

The number of REs (eg, n) of the PUCCH resource may not be sufficient. For example, n may be less than “nHP+nLP”. In this case, the UE may allocate many REs to the codeword of UCI having high priority. In this case, according to method 3.2-3, sufficient REs may be allocated to the codeword of HP UCI. Since insufficient REs are allocated to the codeword of the LP UCI, the base station may request a retransmission procedure of the PUCCH from the terminal later. Alternatively, the base station may reschedule the PDSCH transmission.

Method 3.2-4: The UE may determine whether the size of the PUCCH resource (eg, n REs) is sufficient. For example, when n < (nHP + nLP), the UE may determine that the size of the PUCCH resource is insufficient. If n ≥ (nHP + nLP), the UE may determine that the size of the PUCCH resource is sufficient. When the size of the PUCCH resource is sufficient, the UE may apply method 3.2-2, and when the size of the PUCCH resource is insufficient, the UE may apply method 3.2-3.

If the size of the PUCCH resource is insufficient, the UE may map the HP UCI codeword to the PUCCH resource, but may not be able to map the LP UCI codeword to the PUCCH resource. In this case, transmission of some LP UCIs may be dropped. For example, all or part of a specific UCI type may be dropped from LP UCI. This operation can be distinguished from method 3.2-4, and can be defined as method 3.2-5 below.

Method 3.2-5: The UE may determine whether the size of the PUCCH resource (eg, n REs) is sufficient. For example, when n < (nHP + nLP), the UE may determine that the size of the PUCCH resource is insufficient. If n ≥ (nHP + nLP), the UE may determine that the size of the PUCCH resource is sufficient. When the size of the PUCCH resource is sufficient, the UE may apply method 3.2-2, and when the size of the PUCCH resource is insufficient, the UE may drop all or part of a specific UCI type of the LP UCI.

Here, the droppable UCI type may be CSI. When there are a plurality of CSI reports, the UE may select some CSI report(s) and may transmit the selected CSI report(s). When the CSI report is divided into CSI part 1 and CSI part 2, the UE may select and transmit CSI part 1, and CSI part 1 may be utilized in calculations limiting the number of CSI reports. That is, the transmission of CSI part 2 may be dropped.

The size of the PUCCH resource indicated by the base station to the terminal (eg, n REs) may be adjusted to be greater than nHP + nLP. In this case, since the number of PUCCH resources that can be configured for the UE is limited, n unnecessarily larger than nHP + nLP may be configured. In this case, the UE may reduce the size of the PUCCH resource by deriving n' less than n.

Method 3.2-6: When the size of the PUCCH resource is large, the UE can use the minimum number of PRBs greater than nHP + nLP by reducing the number of PRBs.

When the CSI report is transmitted in PUCCH, in order to find the minimum number of PRBs (eg, PRBs constituting the PUCCH resource), calculation considering "LP UCI" or "LP UCI + CRC field" and the code rate can be performed. The CRC field may mean a CRC value. This operation may be directly applied to UCI having the same priority. However, when HP UCI and LP UCI are multiplexed, it may be necessary to modify the above-described operation.

Since HP UCI and LP UCI may belong to different codewords, different CRC fields may be added to each of HP UCI and LP UCI. Different code rates may be applied to each of "HP UCI + CRC field" and "LP UCI + CRC field", and each of "HP UCI + CRC field" and "LP UCI + CRC field" may be expressed as the number of REs. there is.

Method 3.2-7: Based on the sum of a first value that is a result of dividing the size of “HP UCI + HP CRC field” by a code rate and a second value that is a result of dividing the size of “LP UCI + LP CRC field” by a code rate Thus, the number of REs can be derived. The number of derived REs may be converted into the number of PRBs.

For example, "when the size of HP UCI is oHP, the size of the HP CRC field (eg, CRC field for HP UCI) is oHPCRC, and the code rate is rHP", the number of REs (eg, nHP) may be the result of (oHP + oHPCRC)/rHP. Each of oHP and oHPCRC may be a natural number. "When the size of LP UCI is oLP, the size of the LP CRC field (eg, CRC field for LP UCI) is oLPCRC, and the code rate is rLP", the number of REs (eg, nLP) is ( oLP + oLPCRC)/rLP. Each of oLP and oLPCRC may be a natural number.

In all REs of the PUCCH resource, the number of REs other than REs to which the DM-RS is mapped may be n. n may be converted to an integer number of PRBs (or PRBs that are multiples of 2, 3, or 5).

On the other hand, the number of PRBs of the PUCCH resource may be insufficient. In this case, the UE may reduce the size of the UCI.

When HP UCI and LP UCI are multiplexed, HP UCI may always be transmitted, and all LP UCIs may be dropped. Alternatively, some or all of the LP UCI may be transmitted. Therefore, the UE can distinguish "a case where only HP UCI is transmitted", "a case where HP UCI and some LP UCI are transmitted", and "a case where HP UCI and all LP UCI are transmitted".

Method 3.2-6: The UE may additionally perform a procedure for determining the size of a part of the dropped LP UCI.

The above-described additional procedure may correspond to the procedure of changing the x bit to the x' bit in the embodiments shown in FIGS. 3, 4, and/or 5 .

3.3: How to indicate the number of repetitions of PUCCH

PUCCH (eg, UCI or multiplexed UCIs) may be repeatedly transmitted. The base station may set (or indicate) the number of repetitions of the PUCCH to the terminal by using RRC signaling, and the terminal may check the number of repetitions of the PUCCH set by the base station. Therefore, the time resource in which the PUCCH is transmitted is "a (sub)slot in which UCI (eg, HARQ-ACK, SR, and/or CSI) is transmitted" or "Considering the slot pattern, all symbols of PUCCH can be transmitted. first valid (sub)slot". The UE may perform the first transmission of the PUCCH in the aforementioned (sub)slot.

The number of repetitions of PUCCH may be flexibly indicated. The UE may transmit multiplexed UCIs (eg, LP UCI + HP UCI) in the PUCCH resource. According to the mobility of the terminal, the terminal can move quickly from the boundary area of the cell to the center area of the cell. Accordingly, the quality (eg, reception quality) of UCI may be greatly changed.

Method 3.3-1: PUCCH resource configuration information may include information on the number of repetitions of PUCCH.

The UE may receive the scheduling DCI, and may check the number of repetitions of the PUCCH based on the PRI included in the scheduling DCI. HARQ-ACK for SPS PDSCH, semi-persistent CSI, periodic CSI, and/or PRI for SR may be configured (or indicated) to the UE by RRC signaling.

The number of repetitions of the PUCCH may be determined for each PUCCH format, and the base station may set (or indicate) the number of repetitions of the PUCCH associated with the PUCCH format to the terminal using RRC signaling. According to method 3.3-1, "the number of repetitions of the PUCCH associated with the PUCCH format" and/or the "number of repetitions of the PUCCH associated with the PUCCH resource" may be configured in the terminal. The number of repetitions of the PUCCH associated with the PUCCH format may not be set, and the number of repetitions of the PUCCH associated with the PUCCH resource may be configured in the terminal. The UE may use one of "the number of repetitions of PUCCH associated with the PUCCH format" and "the number of repetitions of the PUCCH associated with the PUCCH resource".

Method 3.3-2: When the number of repetitions of the PUCCH associated with the PUCCH resource in method 3.3-1 is set in the terminal, the terminal may use the number of repetitions of the PUCCH associated with the PUCCH resource regardless of the number of repetitions of the PUCCH associated with the PUCCH format.

When the number of repetitions of the PUCCH is associated with the PUCCH resource through which the UCI is transmitted, the number of repetitions of the corresponding PUCCH may be applied to the UCI type indicated by the ID of the corresponding PUCCH resource. For example, the PRI included in the scheduling DCI may indicate the number of repetitions of the PUCCH. PUCCH resources for transmitting other UCI types (eg, HARQ-ACK for SPS PDSCH, semi-persistent CSI, periodic CSI, and/or SR) are indicated by the PUCCH resource ID. can

Method 3.3-3: Method 3.3-1 may be applied regardless of the UCI type.

Chapter 4: Method of Determination of Transmission Power of PUCCH

4.1: PUCCH transmission power control method

Transmission power applied to the PUCCH may be calculated based on Equation (eg, Equation 1 below). Here, P(i,u,d,l) may be applied to a transmission occasion i of PUCCH, u may be an index of a UL-RS used by the UE to calculate transmission power, d may be an index of a DL-RS used by the UE to calculate transmit power, and l may be an index of a set managing a transmit power control (TPC) command.

P _o (u) may be a variable based on transmit power for PUCCH, and a value for the u -th power control loop may be indicated by RRC signaling. μ may be a variable for the subcarrier interval used by the PUSCH instance, and PL(d) may be the amount of path attenuation of the DL (downlink) calculated as d when the reference RS is defined as d . . PL(d) may be measured (or estimated) in the terminal. g(i,l) may be an accumulated value of TPC commands for the l -th power control loop.

의 값은 RRC 시그널링으로 지시될 수 있고, PUCCH의 포맷에 따라 다르게 지시될 수 있다.here,

The value of may be indicated by RRC signaling, and may be indicated differently according to the format of the PUCCH.

의 값은 RRC 시그널링으로 지시되는 값에 따라 0(예를 들어, 고정된 값) 또는 다른 값으로 계산될 수 있다. PUCCH의 포맷에 따라 서로 다른 수학식들이 적용될 수 있다. 그 이유는 "PUCC에 확산 부호의 적용" 또는 "서로 다른 부호 방식"으로 인하여 비슷한 BLER을 겪도록 전송 전력의 오프셋을 조절하기 위함일 수 있다.here,

The value of may be calculated as 0 (eg, a fixed value) or another value according to a value indicated by RRC signaling. Different equations may be applied according to the format of the PUCCH. The reason may be to adjust the offset of the transmit power so that it experiences a similar BLER due to "application of a spreading code to PUCC" or "different coding schemes".

가 정의될 수 있다.If the PUCCH format is 0 or 1,

can be defined.

When the PUCCH format is 2, 3, or 4, an embodiment in which the size of UCI is 11 bits or less and an embodiment in which the size of UCI is 12 bits or more can be divided.

가 정의될 수 있다. UCI의 크기가 12 비트 이상인 경우,

가 정의될 수 있다.If the size of UCI is 11 bits or less,

can be defined. If the size of UCI is more than 12 bits,

can be defined.

로 표현될 수 있다. O _HARQ-ACK (i)와 n _HARQ-ACK (i)는 HARQ-ACK의 크기를 의미할 수 있고, O _SR (i)은 SR을 표현하는 비트의 크기를 의미할 수 있고, O _CSI (i)은 CSI의 크기를 의미할 수 있다. O _CRC (i)은 CRC 필드의 크기를 의미할 수 있다. N(i)은 PUCCH 자원이 갖는 RE의 개수를 의미할 수 있다. DM-RS가 맵핑된 RE는 N(i)에서 제외될 수 있다.Here, each of K ₁ and K ₂ may be a constant defined in a technical standard. BPRE (bit per resource element) may be a variable related to the code rate,

can be expressed as O _HARQ-ACK (i) and n _HARQ-ACK (i) may mean the size of HARQ-ACK, O _SR (i) may mean the size of bits representing the SR, O _CSI (i) ) may mean the size of CSI. O _CRC (i) may mean the size of the CRC field. N(i) may mean the number of REs included in the PUCCH resource. The RE to which the DM-RS is mapped may be excluded from N(i) .

g(i,l) may mean a value accumulating TPC commands included in DCI for a preset time. The preset time may be defined in a technical standard.

7 is a conceptual diagram illustrating a first embodiment of a method for accumulating a TPC command applied to a PUCCH.

Referring to Figure 7, the time to start the accumulation of the TPC command for the PUCCH transmission occasion i (ie, PUCCH ( i )) is the PUCCH transmission occasion ii ₀ (ie, PUCCH ( ii ₀ )) of the TPC command for It may be after the time to end the accumulation. The time to end the accumulation of TPC commands for PUCCH transmission occasion i may mean the last symbol of CORESET to which the last DCI belongs among DCIs allocating UCI to PUCCH transmission occasion i . Here, i ₀ may mean a minimum natural number in which a time interval during which TPC command accumulation is performed is greater than 0. The accumulation of TPC instructions can only be applied to the same l .

When the UE transmits the PUCCH by multiplexing UCIs having the same priority, Equation 1 may be applied. When UCIs having different priorities are multiplexed, an appropriate power of PUCCH may not be expressed by Equation (1).

Method 4.1-1: When the PUCCH resource in which the HP UCI and the LP UCI are multiplexed is indicated by the LP DCI, the transmission power of the PUCCH may be determined only by the size of the LP UCI. Alternatively, when the PUCCH resource is indicated by the HP DCI, the transmission power of the PUCCH may be determined only by the size of the HP UCI.

Method 4.1-1 may mean "determining transmission power of PUCCH when DCI indicating a PUCCH resource is received". If "the terminal receives the HP DCI after receiving the LP DCI, and the LP UCI and the HP UCI are multiplexed", the transmission power of the PUCCH indicated by the LP DCI may not be sufficient. This is because the size of the additional HP UCI is not taken into account. To solve this problem, TPC instructions can be further accumulated.

Method 4.1-2: In order to determine the transmit power of the PUCCH in the method 4.1-1, the DCI to which the accumulation of the TPC command is applied may include at least all DCIs that cause UCI transmission in the PUCCH.

Here, the DCI may include an LP DCI and/or an HP DCI for scheduling UCI transmission. Also, the DCI may be a TPC DCI (eg, DCI format 2_2). In this case, even when l managing TPC commands has a different value, according to method 4.1-2, TCP commands can be accumulated.

Method 4.1-3: When TPC commands for different set indices ( l ) are accumulated in method 4.1-2, the accumulated value of the corresponding TPC commands is calculated for subsequent PUCCH transmission occasions (eg, PUCCH transmission occasions ( i ) +1), PUCCH transmission occasion ( i +2), etc.) may not be reflected.

DCI indicating PUCCH transmission occasion i may assume a specific l . In the multiplexing procedure of HP UCI and LP UCI, the transmit power of PUCCH may be appropriately corrected. In the PUCCH transmission occasion i +1, multiplexing of HP UCI and LP UCI may not be performed. In this case, the terminal may reflect the accumulated value of TPC commands only for the same l . Therefore, the terminal may re-calibrate the accumulated values of TPC commands for different l , and may regard the corrected value as a value before accumulation.

Since only the size of HP UCI or LP UCI is considered in the proposed method (eg, method 4.1-1), in order to correct the accumulated value, it is preferable that TPC commands for different l are also accumulated. Alternatively, both the size of the HP UCI and the size of the LP UCI may be considered. In this case, the transmit power of the PUCCH may be sufficient even by accumulating TPC commands for the same l .

Method 4.1-4: In consideration of the size of UCI having different priorities, the transmit power of PUCCH in which HP UCI and LP UCI are multiplexed may be corrected.

In the case of "when LP UCI and HP UCI are multiplexed and the existing PUCCH resource set is used", the equation for deriving the transmission power of the PUCCH may be different according to the size of the UCI.

를 계산하는 경우에 LP UCI의 크기가 12비트 이상인 것으로 가정할 수 있다."When LP UCI and HP UCI are multiplexed and PUCCH resources are defined within one PUCCH resource set", the size of UCI may always be assumed to be larger than a threshold value. For example, the terminal

When calculating , it can be assumed that the size of the LP UCI is 12 bits or more.

를 추가할 수 있다. LP DCI에 의해 지시되는 PUCCH를 위해,

는 HP UCI의 크기로부터 도출될 수 있다. LP DCI에 의해 지시되는 PUCCH 포맷에 대해,

또는

가 정의될 수 있다.According to the PUCCH format in which the LP UCI and the HP UCI are multiplexed, the UE is dependent on the transmission power of the PUCCH.

can be added. For PUCCH indicated by LP DCI,

can be derived from the size of HP UCI. For the PUCCH format indicated by the LP DCI,

or

can be defined.

는 LP UCI의 크기로부터 도출될 수 있다. HP DCI에 의해 지시되는 PUCCH 포맷에 대해,

또는

가 정의될 수 있다. BPRE는

을 의미할 수 있다. 여기서, LP UCI를 위한 K ₁ 및 K ₂ 의 값은 HP UCI를 위한 K ₁ 및 K ₂ 의 값과 다를 수 있다.For PUCCH indicated by HP DCI,

may be derived from the size of the LP UCI. For the PUCCH format indicated by HP DCI,

or

can be defined. BPRE

can mean Here, values of K ₁ and K ₂ for LP UCI may be different from values of K ₁ and K ₂ for HP UCI.

가 도입되지 않을 수 있고,

가 다르게 정의될 수 있다. 예를 들어,

또는

가 정의될 수 있다. 여기서, LP UCI의 크기는

일 수 있고, HP UCI의 크기는

일 수 있다. BPRE는

일 수 있다. BPRE의 계산을 위해 LP UCI의 크기와 HP UCI의 크기의 합이 사용될 수 있다.According to another method, the LP UCI and the HP UCI may not be distinguished from each other, and the size of the UCI may be the sum of the size of the LP UCI and the size of the HP UCI. Separate

may not be introduced,

may be defined differently. for example,

or

can be defined. Here, the size of LP UCI is

can be, and the size of HP UCI is

can be BPRE

can be For the calculation of the BPRE, the sum of the size of the LP UCI and the size of the HP UCI may be used.

In addition, the size of the UCI having a size of 11 bits or less may be calculated using a separate equation, and the transmission power of the PUCCH may be calculated based on the calculation result.

Chapter 5: How to allocate two or more TBs using one DCI.

The base station may allocate two or more TBs to the terminal. In order to save power of the terminal, the base station may instruct (or set) the search space having a long period to the terminal. In this case, the traffic of the terminal may occur more frequently than the period of the search space. In this case, transmission of two or more TBs may be indicated to the UE by one DCI, one configured grant (CG), or one semi-persistent scheduling (SPS).

5.1: PDSCH allocation method

The base station may set a time domain resource assignment (TDRA) table to the terminal by using RRC signaling, and may transmit a DCI including information of one index (eg, one TDRA index) in the TDRA table to the terminal. . One index in the TDRA table may indicate a time resource of the PDSCH. Each of the indexes belonging to the TDRA table may indicate a PDSCH mapping type, K ₀ , and/or a start and length indicator (SLIV). The PDSCH mapping type may be classified into a mapping type A and a mapping type B. The PDSCH mapping type may be used to determine a location of a DSCH DM-RS and a method in which coded data is mapped. K ₀ may mean a slot offset between the slot in which the scheduling DCI is received and the first slot in which the PDSCH is received. The SLIV may be an index derived by the number of the first symbol belonging to the PDSCH and the number of symbols belonging to the PDSCH.

Each of the indexes belonging to the TDRA table (eg, TDRA indexes) may additionally indicate the number of repetitions of the PDSCH. Alternatively, the TDRA index may not indicate the number of repetitions of the PDSCH, and the base station may indicate (or set) the number of repetitions of the PDSCH to the UE using separate RRC signaling. In this case, the terminal indicates that "a reception resource (eg, time resource) of a PDSCH is repeated in units of slots, subslots, or minislots, and the number of repetitions of the PDSCH is indicated by a TDRA index or RRC signaling (or set ) can be considered as

In the repetitive reception procedure of the PDSCH, the UE may assume that TBs having different redundancy versions (RVs) are received. For example, the RV indicated by the scheduling DCI may correspond to the RV applied to the initial PDSCH received by the UE, and the RV(s) applied to the PDSCH(s) received by the UE later is the initial RV and preset RV. It may be determined according to an order (eg, RV pattern). The TDRA table may be set as shown in Table 1 below. The number of repetitions of the PDSCH may be additionally indicated by the TDRA index. Alternatively, the number of repetitions of the PDSCH may not be indicated by the TDRA index.

In Table 1, the TDRA table may include four TDRA indexes. The UE may determine the time resource of the PDSCH by using information indicated by one TDRA index. In the proposed method, in order to allocate a plurality of TBs to the UE, the field of the scheduling DCI may be extended.

Method 5.1-1: The TDRA index may be extended, and the TDRA index may indicate two or more SLIVs.

Method 5.1-2: In method 5.1-1, each of the SLIVs indicated by the TDRA index may be interpreted as a time resource to which one TB is mapped, and one SLIV may correspond to each slot or mini-slot. For example, when the TDRA index indicates K SLIVs, the PDSCH may be received in K slots. That is, the terminal may receive K TBs. K may be a natural number.

Since the TBs are managed differently, [NDI, RV, HPN] for each of the TBs may be independently included in the scheduling DCI. To support this operation, a field of DCI may be extended, and K NDIs and K RVs may be included in DCI.

DCI (eg, field of DCI) may be extended to include K [NDI, RV]. When a HARQ process number (HPN) for one TB is indicated, the HPN for each of the remaining TBs (eg, K-1 TBs) may be determined as a value increased by 1 from the indicated HPN. For example, if DCI indicates HPN #x, HPN for the i-th TB (i = 0, 1, 2, ..., K-1) may be interpreted as (x+i)%N. Here, N may mean the number of HARQ process identifiers (HPIDs) that the UE can use in the serving cell.

5.1.1: PUCCH transmission method

The scheduling DCI may indicate one HARQ-ACK timing and one PUCCH resource. The UE may consider that HARQ-ACK bits for K TBs are multiplexed in one HARQ codebook.

For transmission of the Type 1 HARQ codebook, the UE may consider that one HARQ-ACK bit is generated for a TB corresponding to the SLIV according to the TDRA index one-to-one. K HARQ-ACK bits may be derived for K TDRA indices. One HARQ-ACK bit may correspond to a PDSCH candidate on a one-to-one basis.

When one TDRA index indicates K SLIVs, it may be desirable to minimize modification of the generation procedure of the Type 1 HARQ codebook.

In the type 1 HARQ codebook generation procedure, a PDSCH belonging to the TDRA table as a loop for the TDRA index may be considered only once, and then the corresponding PDSCH may be omitted from the TDRA table. Also, it may be assumed that the TDRA index corresponds to one TB.

Method 5.1-3: In order to express a TDRA index corresponding to K TBs, a TDRA index corresponding to one TB may indicate SLIV or “K ₀ and SLIV”, and information indicated by the TDRA index may not be considered in the size of the Type 1 HARQ codebook.

Method 5.1-4: In method 5.1-3, TDRA index(s) corresponding to K TBs may be expressed as a union of TDRA indices corresponding to one TB.

According to the above-described embodiment, the TDRA table may be set as shown in Table 2 below.

In Table 2, TDRA indexes #0 to #3 may be an existing TDRA list, and the TDRA table may further include additional TDRA indexes #4 and #5. The extended TDRA list may include TDRA indexes #0 to #5. Each of TDRA indexes #4 and #5 may indicate K ₀ and one or more (PDSCH mapping type, SLIV). A TDRA index belonging to the extended TDRA list may indicate K ₀ and one or more SLIVs.

The TDRA index may be classified into two types. One TDRA index corresponding to TDRA index type 1 may correspond to one TB. TDRA index type 1 may be a type of a TDRA index belonging to an existing TDRA list. One TDRA index corresponding to TDRA index type 2 may correspond to K TBs. TDRA index type 2 may be a type of a TDRA index (eg, an additional TDRA index) belonging to the extended TDRA list. One TDRA list (eg, one TDRA subtable) may be configured only with a TDRA index corresponding to one TB, and additionally considered TDRA indexes may indicate only time resources related to the TDRA subtable. . In Table 2, a TDRA subtable consisting of four TDRA indexes (eg, TDRA indexes #0 to #3) and two additional TDRA indexes (eg, TDRA indexes #4 and #5) including A TDRA table (or TDRA subtable) may be configured. The size of the Type 1 HARQ codebook may be determined in consideration of only the TDRA subtable.

Each of TDRA indices #4 and #5 may indicate “one or more SLIVs” or “K ₀ and one or more SLIVs”. TDRA indexes #4 and #5 may not be considered to determine the size of the Type 1 HARQ codebook. According to method 5.1-4, TDRA index #4 may be assumed to have SLIV(s) indicated by TDRA indexes #i and #j, and TDRA index #5 is indicated by TDRA indexes #k and #l can be assumed to have SLIV(s) of In this case, each of TDRA indexes #4 and #5 may indicate two TBs. Here, each of i, j, k, and l may be an integer of 0 or more.

In the step of recording the HARQ-ACK bit in the type 1 HARQ codebook, K HARQ-ACK bits corresponding to K PDSCHs according to the additional TDRA index may be recorded. Here, the PDSCH candidate according to the additional TDRA index may correspond to the TDRA index(s) belonging to the TDRA subtable.

"If TDRA index #4 is indicated to the terminal in the TDRA table defined in Table 2 and TDRA index #4 indicates two SLIVs", the terminal transmits two HARQ-ACK bits for the two received PDSCHs. may be generated, and two HARQ-ACK bits may be recorded at positions corresponding to TDRA indices #i and #j in the Type 1 HARQ codebook. "If TDRA index #5 is indicated to the terminal in the TDRA table defined in Table 2 and TDRA index #5 indicates two SLIVs", the terminal transmits two HARQ-ACK bits for the two received PDSCHs. may be generated, and two HARQ-ACK bits may be recorded at positions corresponding to TDRA indexes #k and #l in the Type 1 HARQ codebook.

Method 5.1-5: In method 5.1-3, the positions at which HARQ-ACK bits for the additional TDRA index are recorded in the Type 1 HARQ codebook are PDSCH candidates corresponding to TDRA indices belonging to the TDRA subtable referenced by the additional TDRA index. may be locations of

According to method 5.1-5, when resources of a plurality of TBs are indicated by one TDRA index, HARQ-ACK bits corresponding to the plurality of TBs may not be consecutively arranged in the Type 1 HARQ codebook. That is, HARQ-ACK bits corresponding to the plurality of TBs may be disposed at positions corresponding to slots in which the plurality of TBs are received in the Type 1 HARQ codebook.

The size of the Type 1 HARQ codebook may be determined by the number of PDSCH candidates. Therefore, in order to determine the size of the Type 1 HARQ codebook, HARQ-ACK timing may be considered together with the number of PDSCH candidates. If there is no restriction, in a slot or subslot in which the PUCCH is transmitted, the number of valid PDSCH candidates may be greatly increased. Therefore, the following method 5.1-6 can be considered.

Method 5.1-6: When the HARQ-ACK timing (eg, K ₁ offset) applicable to the terminal in method 5.1-3 indicates transmission of K TBs (eg, indicating transmission of 1 TB) case) may be a part of the K ₁ offset applied to

The above-described methods may be methods for instructing transmission of two or more TBs while maintaining the size of the Type 1 HARQ codebook. To support this operation, the TDRA index may be limitedly extended. Alternatively, application of the K ₁ offset may be limited.

For example, a relationship between K ₁ offsets applied when allocating resources of one TB and K ₁ offsets applied when allocating resources of K TBs may be interpreted as an inclusion relationship. For the (sub)slot n in which the PUCCH is transmitted, the (sub)slot to which the PDSCH candidate belongs may be the (sub)slot nK ₁ (i). Here, "i = 0, 1, 2, ..." may be defined. {K ₁ (0), K ₁ (1), K ₁ (2), K ₁ (3), … } may mean K ₁ offsets.

8A is a conceptual diagram illustrating a first embodiment of HARQ-ACK timing applied to a Type 1 HARQ codebook.

Referring to FIG. 8A , K ₁ may be set (or indicated) to {4,8,12,16}. When the transmission resource of one TB is allocated, the number of (sub)slots in which the PDSCH is received may be 4. When an additional TDRA index for allocating transmission resources of two TBs is considered, a (sub)slot in which each PDSCH is received may be determined from {4,8,12,16}. Therefore, in the reception procedure of 2 TBs, 2 TBs may be received with an interval of 4 (sub)slots. According to the proposed method, the number of TDRA indexes for allocating transmission resources of 4 TBs may be 1, and in this case, K ₁ may be set (or indicated) to 4.

When TBs are received in two consecutive (sub)slots, the value of K ₁ may be extended. Since the calculation unit of K ₁ is the last (sub) slot in which the PDSCH is received, when {4,8,12,16} is reused, the (sub)slot in which the PDSCH can be received is {4,5,7,8 ,11,12,15,16}. Accordingly, the size of the Type 1 HARQ codebook can be greatly increased, and the TDRA index is preferably expressed as a combination of TDRA indexes for allocating one TB of transmission resource. That is, in the embodiment shown in FIG. 8A , in order to allocate the transmission resource of two TBs, K ₁ may be considered as {4, 8, 12}, and the terminal is 2 at an interval of 4 (sub) slots. TBs can be received.

8B is a conceptual diagram illustrating a second embodiment of HARQ-ACK timing applied to a Type 1 HARQ codebook.

Referring to FIG. 8B , K ₁ may be set (or indicated) to {4,5,6,7,8}, and one TB may be allocated. In this case, "when it is desired to maintain the size of the type 1 HARQ codebook while allocating transmission resources of two TBs", the number of TDRA indexes for allocating transmission resources of two TBs may be 4. K ₁ may be set within {4,5,6,7}.

When the type 2 HARQ codebook is supported, since the number of TBs indicated to the terminal is dynamically changed, the terminal may assume the size of the type 2 HARQ codebook in consideration of DTX. Since the size of the Type 2 HARQ codebook is dynamically changed in the generation procedure of the Type 2 HARQ codebook, the scheduling DCI may include C-DAI and/or T-DAI. Since the DAI corresponds to the number of DCIs, when one TB of transmission resource is allocated, the number of DCIs may be interpreted as the size of the type 2 HARQ codebook. When "MIMO is configured and the maximum number of codewords is 2", DCI may allocate 2 TBs. In this case, the size of the Type 2 HARQ codebook may be 2 bits, and twice the number of DCIs may be interpreted as the size of the Type 2 HARQ codebook.

Method 5.1-7: The base station may configure (or indicate) DCI for allocating transmission resources of a plurality of TBs to the terminal. In this case, the type 2 HARQ codebook cannot be configured, and the fact that only the type 1 HARQ codebook is supported can be configured by RRC signaling.

Since the number of TBs indicated to the terminal is dynamically changed when the type 2 HARQ codebook is supported, the terminal may assume the size of the type 2 HARQ codebook in consideration of DTX.

Method 5.1-8: The TDRA index may be extended, and thus K HARQ-ACK bits may be generated. In this case, the number of DCIs is counted by the DAI, but K HARQ-ACK bits may be derived for one DCI.

The UE may actually record HARQ-ACK(s) for the scheduled TB(s) in the HARQ codebook in the order of SLIV, and may record the NACK in another location in the HARQ codebook. For example, if "K = 8 and 2 TBs are received", the first 2 bits in the HARQ codebook may be set to the reception results of 2 TBs (eg, HARQ-ACKs) and , the remaining 6 bits may be set to NACK.

When the bit(s) indicating NACK is always set, the size of the type 2 HARQ codebook may be increased by K times, and many bits in the type 2 HARQ codebook may be set to NACK. In order to solve this problem, since the TDRA index indicates the transmission resources of K or less TBs, it is preferable that the terminal actually know the number of TBs indicated by the base station. The above problem can be solved by extending the size of the DAI field included in DCI.

5.2: PUSCH allocation method

The base station may configure (or indicate) a TDRA table to the terminal by using RRC signaling, and may transmit a DCI including information of one TDRA index in the TDRA table to the terminal. The time resource of the PUSCH may be indicated by a TDRA index belonging to the TDRA table. The TDRA index may indicate a PUSCH mapping type, K ₂ , and/or SLIV. The PUSCH mapping type may be classified into a mapping type A and a mapping type B. The PUSCH mapping type may be used to determine a location of a PUSCH DM-RS and a method in which coded data is mapped. K ₂ may mean a slot offset between the slot in which the scheduling DCI is received and the first slot in which the PUSCH is transmitted. The SLIV may be an index derived by the number of the first symbol belonging to the PUSCH and the number of symbols belonging to the PUSCH.

One piece of information belonging to the TDRA table (eg, TDRA index) may additionally indicate the number of repetitions of the PUSCH (eg, the number of receptions of the PUSCH). Alternatively, the TDRA index may not indicate the number of repetitions of the PUSCH. In this case, the base station may inform the terminal of the number of repetitions of the PUSCH by using RRC signaling, and the terminal may check the number of repetitions of the PUSCH indicated by the base station. The UE may consider it as "a time resource in which a PUSCH is transmitted is repeated in units of slots, and the number of repetitions of a PUSCH is indicated by a TDRA index or RRC signaling".

In the repeated transmission procedure of PUSCH (eg, TB), the UE may transmit TBs having different RVs. For example, the RV indicated by the scheduling DCI may be the RV applied to the PUSCH transmitted by the UE first, and the RV applied to the PUSCH(s) after the initial PUSCH is the RV indicated by the scheduling DCI and a preset order can be determined according to The preset order may be defined in a technical standard.

Scheduling DCI may schedule transmissions of two or more TBs. In a communication system operating in an unlicensed band, the UE may derive information on a plurality of time resources (eg, a plurality of PUSCHs) based on the TDRA index indicated by DCI format 0_1. For example, the UE may independently derive the PUSCH mapping type and SLIV of each of the plurality of PUSCHs. However, in order to operate in the unlicensed band, PUSCHs according to SLIVs indicated to the UE may be continuous in the time domain. All SLIVs may be defined based on the same symbol. For example, the reference symbol for interpretation of SLIV may be the first symbol of the slot or the next symbol of CORESET including the scheduling DCI.

Since a valid value in SLIV means that the PUSCH is limited to one slot, when transmission resources of two or more TBs are allocated in an unlicensed band, the PUSCH can be continuously transmitted in up to 14 symbols.

9 is a conceptual diagram illustrating a first embodiment of a method for configuring PUSCHs according to SLIVs indicated by a TDRA index.

Referring to FIG. 9 , one TDRA index may indicate “PUSCH mapping type and/or SLIV” of each of four TBs. That is, one TDRA index may indicate four SLIVs (eg, first SLIV, second SLIV, third SLIV, and fourth SLIV). The UE may derive the first symbol to which each TB (eg, each PUSCH) is mapped by interpreting the four SLIVs based on the same reference symbol. "S _i+1 = S _i +L _i , i=1,2,3" may be defined, and K ₂ may be commonly indicated by a TDRA index.

The time resource for transmission of the first TB may be indicated by the first SLIV (eg, S ₁ , L ₁ ), and the time resource for transmission of the second TB is the second SLIV (eg, S ₂ , L ₂ ), and the time resource for transmission of the third TB may be indicated by the third SLIV (eg, S ₃ , L ₃ ), and for transmission of the fourth TB The time resource may be indicated by the fourth SLIV (eg, S ₄ , L ₄ ).

In order to freely allocate a transmission resource of a TB, transmissions of two or more TBs may be scheduled not only by a scheduling DCI but also by a CG (configured grant). In a communication system operating in a licensed band, PUSCH resources do not need to be consecutively deployed in the time domain. Therefore, the transmission resource of the TB can be scheduled freely. A plurality of SLIVs indicated by one TDRA index may indicate discontinuous time resources in the time domain.

Method 5.2-1: Time resources derived from SLIVs indicated by the TDRA index may not necessarily be contiguous.

A method in which the TDRA index indicates a plurality of SLIVs may be subdivided. As a first method, a TDRA index indicating a plurality of SLIVs may be a combination of TDRA indexes indicating one SLIV. As a second method, the interpretation method of the SLIV indicated by the TDRA index may be different.

Method 5.2-2: In method 5.2-1, the UE may derive K SLIVs from the TDRA index.

In order to freely allocate the resources of the K TBs, "PUSCH mapping type and/or SLIV" for each of the K TBs may be independently indicated (or set). K may be a natural number. Each of the K TDRA indices may indicate a time resource of 1 TB, and a combination of the K TDRA indices may be interpreted as one TDRA index for allocating time resources of the K TBs. To support this operation, the base station may transmit K TDRA indices to the terminal. A slot offset for PUSCH transmission may be set to a common value.

For example, the TDRA list may consist of only TDRA indices for allocating time resources of 1 TB, and a combination of the corresponding TDRA indices may be interpreted as a TDRA index for allocating time resources of K TBs.

According to the above-described embodiment, the TDRA table may be set as shown in Table 3 below.

In Table 3, TDRA indexes #0 to #3 may be an existing TDRA list, and the TDRA table may further include additional TDRA indexes #4 and #5. The extended TDRA list may include TDRA indices #0 to #5. Each of TDRA indexes #4 and #5 may indicate K ₂ and one or more (PUSCH mapping type, SLIV). Alternatively, the TDRA index belonging to the extended TDRA list may indicate K ₂ and one or more SLIVs.

The TDRA index may be classified into two types. One TDRA index corresponding to TDRA index type 1 may correspond to one TB. TDRA index type 1 may be a type of a TDRA index belonging to an existing TDRA list. One TDRA index corresponding to TDRA index type 2 may correspond to K TBs.

One TDRA list (eg, one TDRA subtable) may be configured only with a TDRA index corresponding to one TB, and additionally considered TDRA indexes may indicate only time resources related to the TDRA subtable. . In Table 3, a TDRA subtable consisting of four TDRA indexes (eg, TDRA indexes #0 to #3) and two additional TDRA indexes (eg, TDRA indexes #4 and #5) including A TDRA table (eg, a TDRA subtable) may be configured. TDRA indexes #4 and #5 may be used to allocate time resources of 2 TBs.

Method 5.2-3: In method 5.2-1, the UE may interpret SLIVs indicated by the TDRA index in order. The UE may interpret the SLIV for the i+1-th TB based on the interpretation of the SLIV for the i-th TB.

The value of K ₂ may be shared, and the interpretation of each of the SLIVs may be different. S derived from SLIV may mean a symbol offset, and L derived from SLIV may mean the length of a PUSCH instance. For example, the UE may derive S _i and L _i from the i-th SLIV. In this case, the UE may interpret the result of the calculation based on (S _i , L _i ) as the position (T _i+1 ) of the first symbol to which the TB corresponding to the i+1th SLIV is mapped. T _i +L _i may belong to one slot.

10 is a conceptual diagram illustrating a first embodiment of a method for analyzing a PUSCH instance based on a TDRA index.

Referring to FIG. 10 , one TDRA index may indicate four SLIVs. The UE may derive 4 PUSCH instances from 4 SLIVs indicated by the TDRA index. One PUSCH instance may mean one TB transmission. For example, the UE may calculate _Ti based on Equation 2 below, and may derive 4 PUSCH instances based on _Ti .

11 is a conceptual diagram illustrating a second embodiment of a method for analyzing a PUSCH instance based on a TDRA index.

Referring to FIG. 11 , one TDRA index may indicate four SLIVs. The UE may derive 4 PUSCH instances from 4 SLIVs indicated by the TDRA index. For example, the UE may calculate _Ti based on Equation 3 below, and may derive 4 PUSCH instances based on _Ti .

TBs may be managed differently. Accordingly, NDI, RV, and/or HPN for each of the TBs may be configured independently, and the scheduling DCI may include NDI, RV, and/or HPN for each of the TBs. DCI (eg, field of DCI) may be extended to include K NDIs and K RVs. When the HPN for one TB is indicated by the DCI, the HPN of each of the remaining TBs (eg, K-1 TBs) may be a value increased by one from the HPN indicated by the corresponding DCI. For example, when the DCI indicates HPN #x, the HPN of the i-th TB may be (x+i)%N. "i = 0, 1, 2, ..., K-1" may be defined, and N may indicate the number of HPIDs usable in the serving cell.

5.3: Interpretation method of DCI (eg, field of DCI) in retransmission procedure

One DCI may schedule transmission of a plurality of TBs. In this case, the number of TBs scheduled by DCI may be dynamically changed. The base station may transmit information on the maximum number of schedulable TBs to the terminal by using RRC signaling, and the terminal may check the maximum number of schedulable TBs indicated (or set) by the base station. Alternatively, the UE may check the maximum number of TBs schedulable to the UE based on the TDRA index(s) indicated by the DCI. That is, the maximum number of schedulable TBs may be implicitly indicated by DCI.

When the TDRA index may indicate transmission resources of K or less TBs, the scheduling DCI may include scheduling information of L TBs. L may be less than or equal to K. The HPN of the first TB among the L TBs may be x indicated by the scheduling DCI, and the HPNs of the remaining TBs (eg, L-1 TBs) are x+1, ... , x+L-1.

In the transmission procedure of the PDSCH, one or more TBs among TBs received by the UE may be retransmission TB(s). When the number of TBs scheduled by DCI is L, consecutive L HPNs may not indicate supertransmission and/or retransmission. The above-described operation may be equally applied to the PUSCH transmission procedure.

In the embodiments below, the K TBs are all supertransmission TBs, and the L TBs may be retransmitted after transmission of the supertransmission TBs. The HPNs of K TBs are x, x+1, ... , x+K-1. Retransmission for all L TBs may not be scheduled by DCI.

Method 5.3-1: When transmissions of two or more TBs are scheduled by one DCI, both of the two or more TBs may be considered as supertransmission TBs.

Supertransmission and retransmission can be divided into DCI. For example, DCI for supertransmission may be distinguished from DCI for retransmission. Therefore, according to Method 5.3-1, the UE does not need to check the NDI. In this case, DCI may not include information indicating NDI.

Method 5.3-2: In method 5.3-1, DCI may not include an NDI field.

According to method 5.3-2, the UE may determine that the retransmission operation is not scheduled based on the DCI (eg, a specific DCI format) even when the NDI is not indicated by the DCI. If "all K TBs are retransmitted" or "L TBs are retransmitted", the transmissions may have consecutive HPNs. In this case, information indicating that all TBs scheduled by the DCI are supertransmission TBs or retransmission TBs may be included in the DCI.

Method 5.3-3: In method 5.3-1, the size of the NDI field included in DCI may be 1 bit.

It can be difficult to retransmit all TBs with consecutive HPNs. Accordingly, the base station may use L DCIs to retransmit the L TBs, and each of the L DCIs may schedule retransmission of one TB.

For example, DCI scheduling PDSCH for transmission of 4 TBs or less may be considered. DCI may indicate a common HPN for TBs, and a TDRA index for deriving time resources of each of the TBs may be included in the corresponding DCI. In order to jointly indicate NDI, according to method 5.3-3, one NDI included in DCI may be applied to all TBs.

On the other hand, when the joint NDI is applied to all TBs, the degree of freedom of scheduling may be reduced. Even if the payload size of DCI increases, as many NDI fields as the maximum number of TBs indicated by the TDRA table may be used. The reason is that the DCI size is indicated by RRC signaling in consideration of the limitation of the processing capability of the UE. The UE may derive the number of TBs based on the TDRA index, and may assume that the derived TBs correspond to the NDI in order.

Even in this case, in order to indicate non-consecutive HPNs, the DCI may include an additional field.

Method 5.3-4: DCI may include information indicating the reception pattern of the TB.

Method 5.3-5: In method 5.3-4, the information indicating the reception pattern of the TB may be set as a bitmap, and the length of the bitmap may be the maximum number of schedulable TBs.

According to method 5.3-4, the DCI may further include a bitmap indicating a TB reception pattern (hereinafter, referred to as a “TB transmission indicator (TBTI)”). The TBTI may indicate a TB that the terminal receives or a TB that the terminal transmits. The length of the TBTI may be the maximum number of TBs that can be scheduled by the TDRA table. A bit set to a first value (eg, 1) within the TBTI may indicate that the TB is transmitted, and a bit set to a second value (eg, 0) may indicate that the TB is not transmitted. there is.

When the DCI additionally includes the TBTI, the UE may generate various combinations of HPNs using the TBTI included in the DCI. This operation may be performed even if the HPNs are not contiguous. When HPN is a natural number between 0 and 15, a bitmap may be utilized to indicate non-consecutive combinations of HPNs. In this case, the size of the bitmap may be 16 bits. Alternatively, a bitmap having a size of less than 16 bits may be used to indicate a combination of HPNs. The combination of HPNs may be indicated by the first HPN and/or the number of consecutive HPNs. The first HPN may be indicated by 4 bits, and the number of consecutive HPNs may be indirectly indicated by the TDRA table. The number of SLIVs (eg, the number of TBs) indicated by the TDRA table may be regarded as the number of consecutive HPNs. When the TDRA table indicates the transmission resource of K TBs, the size of the TBTI included in DCI may be (4+K) bits. (4+K) bits may be less than 16 bits.

12A is a conceptual diagram illustrating a first embodiment of control information for super transmission.

Referring to FIG. 12A , the base station may transmit a DCI scheduling supertransmission of 4 TBs to the terminal. DCI may include HPN, NDI, TDRA index, and/or TBTI. The UE may receive the DCI from the base station, and may derive 4 SLIVs (eg, S and/or L) from the TDRA index included in the DCI. In this case, it may be assumed that the terminal receives 4 TBs. Since DCI indicates HPN #3, the four TBs received from the terminal may be processed in HPN #3, HPN #4, HPN #5, and HPN #6. DCI may include NDI, and NDI of each of the four TBs may be set to 0. According to method 5.3-4, DCI may include TBTI. The size of the TBTI may be 4 bits, and the value of the TBTI may be 1111. The TBTI set to 1111 may indicate reception of all four TBs.

The UE may perform a reception operation of 4 TBs based on DCI and may generate HARQ-ACK bits for the 4 TBs. The size of the HARQ-ACK bits may be 4 bits. The UE may transmit a HARQ codebook including HARQ-ACK bits to the base station. Here, the HARA-ACK bit for the first TB, the second TB, and the fourth TB may indicate NACK, and the HARQ-ACK bit for the third TB may indicate ACK.

The base station may receive the HARQ codebook from the terminal, and may perform a retransmission operation (eg, a retransmission operation for three TBs) based on the HARQ codebook. The retransmission operation may be performed as follows.

12B is a conceptual diagram illustrating a first embodiment of control information for retransmission.

Referring to FIG. 12B , the base station may transmit DCI for scheduling retransmission of three TBs to the terminal. DCI may include HPN, NDI, TDRA index, and/or TBTI. The UE may receive the DCI from the base station, and may derive three SLIVs (eg, S and/or L) from the TDRA index included in the DCI. In this case, it may be assumed that the terminal receives three TBs. Since DCI indicates HPN #3, three TBs received from the terminal may be processed in three HPNs among HPNs #3 to #6. According to Method 5.3-4 or Method 5.3-5, when the TBTI included in the DCI is set to 1101, the UE may determine that the HPNs of the three TBs are HPN #3, HPN #4, and HPN #6. The UE may interpret the NDI value (ie, 0000) included in the DCI based on the TBTI value (ie, 1101). The UE may determine a toggle for each TB based on the interpretation of the NDI value. Here, the third value of NDI may be interpreted as DC (don't care) by TBTI. Alternatively, the third value of NDI may be ignored.

Meanwhile, a method of not increasing the size of DCI may be considered. This method can be applied to the transmission procedure of the PDSCH. Since the terminal transmits the HARQ-ACK to the base station, the base station may not retransmit the TB before receiving the HARQ-ACK for the same HPN.

Method 5.3-6: When the UE transmits the ACK for the HPN, it may be assumed that the UE does not receive scheduling information for retransmission of the TB associated with the corresponding HPN.

Even when the terminal transmits the ACK, the base station may indicate retransmission by transmitting a DCI including the NDI set to the same value (eg, a value that is not toggled). The UE may receive the same TB and may generate a HARQ-ACK for the received TB. Even when the CRC operation for the TB is completed, the UE may perform a soft combining procedure again. The ACK may be regenerated with high probability, and the terminal may transmit the ACK to the base station. When the TB retransmission procedure is not performed, power consumption is reduced in the terminal, so the base station may consider method 5.3-6.

In this case, even when the DCI does not include the TBTI, the UE may use the HARQ-ACK previously derived for the same HPN as the TBTI. For example, if the decoding result of the TB is ACK, it may be assumed that the UE does not receive the corresponding TB again. When the decoding result of the TB is NACK, the UE may assume that the TB is received again.

13A is a conceptual diagram illustrating a second embodiment of control information for super transmission.

Referring to FIG. 13A , the base station may transmit a DCI scheduling supertransmission of 4 TBs to the terminal. DCI may include HPN, NDI, and/or TDRA index. The UE may receive the DCI from the base station, and may derive 4 SLIVs (eg, S and/or L) from the TDRA index included in the DCI. In this case, it may be assumed that the terminal receives 4 TBs. Since DCI indicates HPN #3, the four TBs received from the terminal may be processed in HPN #3, HPN #4, HPN #5, and HPN #6. DCI may include NDI, and NDI of each of the four TBs may be set to 0.

The UE may perform a reception operation of 4 TBs based on DCI, may generate HARQ-ACK bits for the 4 TBs, and may transmit UCI including the HARQ-ACK bits to the base station. Here, the HARA-ACK bit for the first TB (eg HPN #3), the second TB (eg HPN #4), and the fourth TB (eg HPN #6) indicates a NACK may indicate, and the HARQ-ACK bit for the third TB (eg, HPN #5) may indicate ACK.

The base station may receive the HARQ codebook from the terminal, and may perform a retransmission operation (eg, a retransmission operation for three TBs) based on the HARQ codebook. The retransmission operation may be performed as follows.

13B is a conceptual diagram illustrating a second embodiment of control information for retransmission.

Referring to FIG. 13B , the base station may transmit DCI for scheduling retransmission of three TBs to the terminal. DCI may include HPN, NDI, and/or TDRA index. The UE may receive the DCI from the base station, and may derive three SLIVs (eg, S and/or L) from the TDRA index included in the DCI. In this case, it may be assumed that the terminal receives three TBs. Since DCI indicates HPN #3, three TBs received from the terminal may be processed in three HPNs among HPNs #3 to #6. According to method 5.3-6, the UE may determine that retransmission for HPN #5 is not indicated. Accordingly, the UE may determine that the value of NDI (ie, 0000) is not toggled to mean retransmission for HPNs #3, #4, and #6. Here, the third value of NDI may be interpreted as DC (don't care). Alternatively, the third value of NDI may be ignored.

5.4: Interpretation method of DCI (eg, field of DCI) for BWP (bandwidth part) switching

DCI may indicate BWP switching (eg, BWP change). For example, DCI may include "switching information from BWP1 to BWP2" and "allocation information of PDSCH or allocation information of PUSCH". The configuration of the PDCCH may vary depending on the BWP. Therefore, the size of the DCI field may vary according to the configuration of the base station. When the size of the DCI field increases, the UE may interpret that the size of the DCI field is increased compared to the configured DCI field. When the size of the DCI field is decreased, the UE may interpret that the size of the DCI field is decreased than that of the configured DCI field.

When it is interpreted that the size of the DCI field is increased, 0 may be added to the most significant bit (MSB) of the corresponding DCI field. When it is interpreted that the size of the DCI field is reduced, only the least significant bit (LSB) of the corresponding DCI field can be interpreted. For example, if "the DCI field includes [b3, b2, b1, b0] and it is interpreted that the size of the DCI field is increased", the UE sets the DCI field to [0, 0, b3, b2, b1]. , b0]. If "the DCI field includes [b3, b2, b1, b0] and it is interpreted that the size of the corresponding DCI field is reduced", the UE may interpret the DCI field as [b1, b0].

The above-described DCI field interpretation method may be applied to scheduling DCI. In this case, since the degree of freedom for resource allocation is reduced, efficiency may be reduced. However, the interpretation of the DCI field in the base station and the terminal may be clear, and the above-described inefficiency may occur in DCI indicating BWP switching. Accordingly, the burden on the communication system may not be large. However, since the terminal may perform unnecessary operations, power consumption in the terminal may increase.

In one way, K1 or less TBs may be scheduled in BWP1, and K2 or less TBs may be scheduled in BWP2. In this case, the sizes of the RV field and the NDI field may be changed. Each of K1 and K2 may be a natural number.

Method 5.4-1: When the maximum number of schedulable TBs increases by the BWP change (eg, BWP1 → BWP2) (eg, K1 < K2), the terminal by DCI indicating the BWP change It can be assumed that K1 TBs are scheduled.

In this case, the base station may not be able to schedule K2-K1 TBs to the terminal. That is, inefficiencies may occur. However, since DCI indicating a BWP change does not occur frequently, the inefficiency may not be large.

0 may be added to the RV field. However, the RV field to which 0 is not added may be interpreted in BWP2. That is, the UE may interpret the value of the RV field of BWP1 as the RV of the TB scheduled in BWP2.

Method 5.4-2: In method 5.4-1, the UE may interpret only the LSB of the NDI field to which 0 is not added. K2-K1 zeros may be unused, and K1 bits may be utilized.

This method may mean that at least the NDI field is interpreted differently from other DCI fields (eg, a DCI field to which 0 is added) when the BWP is changed.

According to another method, the interpretation method of the DCI field may be improved so that the DCI can schedule K2 TBs.

When 0 is added to the RV field, the UE may interpret RV as 0. Even in the retransmission procedure of the TB, the UE may consider the RV to be 0.

When 0 is added to the NDI field, the UE may not be able to determine whether the TB associated with the corresponding NDI field is a supertransmission TB or a retransmission TB. Therefore, the NDI field may be interpreted as in Method 5.4-3 below.

Method 5.4-3: NDI fields may be interpreted in reverse order. The UE may interpret from the LSB of the NDI field.

For example, if "the DCI field received from the terminal is [b3, b2, b1, b0] and the size of the DCI field increases", the terminal sets [0, 0, b3, b2, b1, b0] to [ b0, b1, b2, b3, 0, 0]. In this case, information having a meaning in the NDI field may be mapped to a corresponding TB.

According to method 5.4-3, only the NDI field included in the DCI indicating the BWP change may be interpreted differently. When the interpretation of the NDI field starts from the MSB appended with 0, the UE may not be able to determine whether to maintain the circular buffer or the HARQ combining buffer for the HPN appended with 0. In this case, the UE may determine whether the TB is a supertransmission TB or a retransmission TB based on information other than the NDI.

Method 5.4-4 and/or method 5.4-5 below may be used in a PDSCH reception procedure.

The UE may receive downlink feedback information (DFI) from the base station to transmit the PUSCH. The DFI may include HARQ-ACK for all HPNs configured in the UE. Therefore, methods 5.4-4 and/or methods 5.4-5 below may be used as they are.

Method 5.4-4: The size of the NDI field may increase due to a change in BWP. In this case, the UE may determine that the HPN related to the NDI field having an increased size is related to the HARQ-ACK (or the HARQ-ACK received from the base station) transmitted to the base station last, and based on the determination result to interpret the initial transmission or the retransmission.

Method 5.4-5: In method 5.4-4, the UE may transmit HARQ-ACK related to HPN. Alternatively, the UE may not receive the HARQ-ACK related to the HPN. In this case, when NDI included in DCI is set to 0, the UE may consider that NDI is toggled. Alternatively, the UE may determine that the corresponding DCI schedules the super transmission.

If the UE is not instructed (or configured) to receive the DFI by the RRC signaling of the base station, the UE may not receive the DFI from the base station. Alternatively, the UE may receive the DFI after a preset time (eg, cg-minDFIDelay or a time required for a decoding operation) from the transmission time of the PUSCH. In this case, the UE may determine that the HARQ-ACK for the HPN is invalid, and may ignore the HARQ-ACK.

When the UE does not receive DFI, it may be assumed that supertransmission or retransmission is performed based on a technical standard.

Method 5.4-6: The UE may change the BWP according to an indication of DCI, and may transmit a PUSCH in the changed BWP. In this case, when the size of the NDI field increases, the UE may assume that the HPN corresponding to the NDI appended with 0 is related to the initial transmission or the retransmission.

For example, the UE may check whether there is a value stored in the UE as NDI is indicated in DCI for the corresponding HPN.

The terminal may determine whether there is an NDI stored in the corresponding terminal. When there is an NDI stored in the terminal, the terminal may consider that the HPN corresponding to the NDI set to 0 is related to retransmission. If the NDI stored in the terminal does not exist, since the TB transmission for the corresponding HPN is not scheduled, the terminal may regard the corresponding HPN as related to the initial transmission.

For example, the UE may assume that the NDI is 0 in the BWP (eg, firstActiveDownlinkBWP) in which the serving cell is activated. In this case, the DCI may include an NDI for a specific HPN, and the corresponding NDI may be set to 0. The UE may consider at least PUSCH transmission as only super transmission. On the other hand, the UE may regard the PDSCH transmission as super transmission or retransmission. For example, the UE may consider the PDSCH transmission as super transmission or retransmission based on the criteria defined in the technical standard.

The UE may consider the first TB received in the transmission procedure of the PDSCH according to the HPN as the retransmission TB. Even when the decoding result of the corresponding TB is NACK, it may be considered that there is no problem in the communication system. When no signal (eg, TB) is received in the PUSCH transmission procedure according to HPN, if retransmission is requested, the operation of the UE may not be defined.

Chapter 6: Transmission Method of PUSCH

6.1: How to restrict the combination of UCI types multiplexed in PUCCH differently from the combination of UCI types multiplexed in PUSCH

UCI may be generated for each UCI type. In addition, UCI may be generated for each UCI priority. Accordingly, the terminal may perform various encoding procedures, and thus power consumption may increase in the terminal. In order to receive both HP UCI and LP UCI in PUSCH without error, the base station may allocate considerable radio resources to the terminal.

When LP UCI and HP UCI are multiplexed in PUCCH, HP UCI may be limited to including HARQ-ACK, and LP UCI may be limited to including HARQ-ACK. Alternatively, HP UCI may be limited to including HARQ-ACK, and LP UCI may be limited to including CSI. When the CSI report is not transmitted periodically (eg, semi-persistent CSI report, aperiodic CSI report), other combinations of control information may be considered. The aperiodic CSI report may be transmitted by triggering.

The semi-persistent CSI report may be transmitted in PUCCH or PUSCH.

Method 6.1-1: "When the size of UCI transmitted in PUCCH is 3 bits or more and HP UCI includes HARQ-ACK", LP UCI is to be limited to a UCI type including at least one of HARQ-ACK or CSI. can

The UE may consider UCI including (HP HARQ-ACK, LP HARQ-ACK), (HP HARQ-ACK, semi-persistent CSI), or (HP HARQ-ACK, periodic CSI). When method 6.1-1 is applied, the UE may multiplex CSI and LP HARQ-ACK. In this case, the UE may assume that the HP HARQ-ACK is not additionally multiplexed.

HP DCI indicating transmission of HP UCI may include scheduling information of PUSCH. In this case, the terminal may consider more combinations than the combinations according to method 6.1-1. For example, the UE may further consider a combination of aperiodic CSI. The UE may consider HP UCI including HP HARQ-ACK, HP aperiodic CSI, and/or HP LRR, and may consider multiplexing of the corresponding HP UCI and LP UCI.

Method 6.1-2: "When the size of UCI transmitted in PUSCH is 3 bits or more and HP UCI includes HARQ-ACK", LP UCI may be multiplexed with HP UCI without limitation in UCI type.

According to method 6.1-2, the UE may generate a combination of HP UCI and LP UCI without restrictions. Accordingly, the terminal can generate various codewords. The UE may consider HP UCI including HARQ-ACK, aperiodic CSI, and/or LRR, (HARQ-ACK, aperiodic CSI), (semi-persistent CSI), or (periodic CSI, LRR) including LP UCI can be considered. The UE may consider HP UCI and LP UCI including only one type of CSI. For example, the UE may consider only one type of CSI from among aperiodic CSI, semi-persistent CSI, and periodic CSI. In this case, the CSI may be expressed as one CSI in consideration of all priorities. Regardless of priority, one CSI (eg, one type of CSI) may be included in the PUSCH. One CSI may follow a CSI reporting setting indicated by a technical standard and/or RRC signaling.

UCI may be generated for each UCI type. In addition, UCI may be generated for each UCI priority. Accordingly, the terminal may perform various encoding procedures, and thus power consumption may increase in the terminal. In order to receive both HP UCI and LP UCI in PUSCH without error, the base station may allocate considerable radio resources to the terminal. In order to reduce the number of times of performing an encoding procedure performed in the terminal and to reduce radio resources used in the terminal, the UCI type of the LP UCI may be limited.

Method 6.1-3: When UCI transmitted in PUSCH includes HP UCI including HARQ-ACK, LP UCI may be limited to a UCI type including at least one of HARQ-ACK or periodic CSI.

The difference between method 6.1-2 and method 6.1-3 may be "the terminal generates HP UCI without restriction of UCI type, but selects some UCI types to generate LP UCI". That is, since the base station can sufficiently control it, it can properly schedule the terminal. However, some UCI types for LP UCI may be restricted in technical standards, and both HARQ-ACK and CSI may not be multiplexed.

For example, the UE may consider HP UCI including (HARQ-ACK, semi-persistent CSI) or (HARQ-ACK, periodic CSI), and may consider LP UCI including HARQ-ACK, HP UCI and LP UCI may be multiplexed, and multiplexed UCIs (eg, HP UCI + LP UCI) may be transmitted in PUCCH.

For another example, the UE may consider HP UCI including (HARQ-ACK, aperiodic CSI) or (HARQ-ACK, semi-persistent CSI), and may consider LP UCI including HARQ-ACK, HP UCI and LP UCI may be multiplexed, and multiplexed UCIs (eg, HP UCI + LP UCI) may be transmitted in PUSCH. HP DCI triggering aperiodic CSI may include resource allocation information of PUSCH. HP DCI for semi-persistent CSI may include resource allocation information of the activated PUSCH.

For another example, the UE may consider HP UCI including HARQ-ACK and semi-persistent CSI, may consider LP UCI including HARQ-ACK, may multiplex HP UCI and LP UCI, and UCIs (eg, HP UCI + LP UCI) may be transmitted in PUSCH. HP DCI indicating transmission of semi-persistent CSI and/or HARQ-ACK may include resource allocation information of PUSCH. When HARQ-ACK of SP PDSCH is involved, transmission of semi-persistent CSI may not be scheduled by DCI. In "in case the activated PUSCH resource is used in the UE" or "LP DCI indicates transmission of HARQ-ACK", PUSCH resources may be scheduled, and both HP UCI and LP UCI may be multiplexed.

6.2: How to Direct Using Beta Offset

A separate field included in DCI may indicate multiplexing of LP UCI and HP UCI. Alternatively, "multiplexing of LP UCI and HP UCI", "multiplexing of HP UCIs", or "multiplexing of LP UCIs" may be indicated by implicitly utilizing a field included in DCI. The method of method 2.2-1 described above can be extended. In this case, a separate field may be introduced into DCI. Alternatively, other fields included in DCI may be used implicitly.

In an embodiment, DCI may always be HP DCI. Alternatively, DCI may not necessarily be limited to HP UCI. When DCI is limited to HP DCI (eg, when method 2.2-2 is applied), information indicating multiplexing of LP UCI may be derived from a beta offset indicator field. The beta offset indicator field may be referred to as a beta offset field or a beta offset indicator.

When UCIs having the same priority are considered, the beta offset field may be expressed as an index of values of (HARQ-ACK offset, CSI part 1 offset, CSI part 2 offset). When UCIs having different priorities are considered, various combinations may be considered.

According to the technical standard, the beta offset field may be expressed as an index indicating four cases. The UE may derive three values from one index of the beta offset field, and each of the three values may correspond to the beta offset of HARQ-ACK, the beta offset of the CSI part 1, and the beta offset of the CSI part 2. The beta offset of HARQ-ACK may be expressed as different beta offsets according to three encoding methods. The base station may set (or indicate) the above-described index(s) and/or beta offset(s) to the terminal using RRC signaling.

The combination in which HP UCI and LP UCI are multiplexed may be limited to only HARQ-ACK. In this case, if the HP DCI includes the beta offset indicator, the UE may interpret one value according to the beta offset indicator as HP HARQ-ACK, and interpret another value according to the beta offset indicator as LP HARQ-ACK. there is. If the LP DCI includes the beta offset indicator, the UE may interpret one value according to the beta offset indicator as HP HARQ-ACK, and may interpret another value according to the beta offset indicator as LP HARQ-ACK. Here, the UE may not interpret a value according to the beta offset indicator as CSI. When DCI indicates transmission (or presence) of HP UCI, the interpretation of the beta offset indicator in the terminal may be different.

Therefore, the base station can dynamically inform the UE of "the multiplexing method when the priority of PUSCH and the priority of UCI are the same" and "the multiplexing method when the priority of PUSCH and the priority of UCI are different". In the proposed method, depending on the presence or absence of UCI (or HARQ-ACK) having different priorities, the method of interpreting the beta offset indicator in the UE may be different.

Method 6.2-1: The base station may configure (or indicate) a set of two beta offsets to the terminal using RRC signaling, and the terminal may identify a set of two beta offsets set by the base station. The first set of beta offsets may be used for transmission of UCIs having the same priority, and the second set of beta offsets may be used for transmission of UCIs having different priorities.

Method 6.2-2: "If the UL DCI includes a beta offset indicator in method 6.2-1, and HARQ-ACKs having different priorities exist", the UE sets the beta offset indicator to HP HARQ-ACK and LP HARQ- It can be interpreted as a beta offset for ACK. If HARQ-ACK having different priorities is absent, the UE may interpret the beta offset indicator as a beta offset for HARQ-ACK and CSI.

Here, even though both the HP HARQ-ACK and the LP HARQ-ACK exist, the base station may instruct the terminal that the transmission of the LP HARQ-ACK is dropped. If the beta offset indicator includes 0, the UE may not transmit the LP HARQ-ACK.

The beta offset indicator including 0 may be limited to be applied only to LP UCI. If the LP UCI does not include the HARQ-ACK, the UE may interpret that the CSI transmission of the LP UCI is also dropped.

Method 6.2-3: In method 6.2-1 and/or method 6.2-2, the beta offset indicator for only LP HARQ-ACK may be indicated as 0. When the beta offset of LP HARQ-ACK is indicated as 0, CSI, SR, and/or LRR classified as LP UCI may be dropped regardless of the value of the beta offset.

Meanwhile, the terminal may receive a plurality of DCIs. Here, in DCIs received in the same slot, "information indicating whether HP UCI and LP UCI are multiplexed" and/or "information indicating whether LP UCI is dropped" may be equally indicated. The above-described information may be explicitly indicated by a separate field included in DCI. Alternatively, the above-described information may be implicitly derived by an existing field included in DCI. Alternatively, the UE may use both the above-described explicit indication method and the above-described implicit derivation method.

Method 6.2-4: In DCIs (eg, DCI format) received in the same slot, "information indicating whether HP UCI and LP UCI are multiplexed" and/or "information indicating whether LP UCI is dropped" may be indicated in the same way.

However, "information indicating whether HP UCI and LP UCI are multiplexed" and/or "information indicating whether LP UCI is dropped" may be indicated differently in DCIs received in different slots. The reason is that it is difficult to keep the error rate of HP UCI sufficiently low as the size of LP UCI is changed.

6.3: Mapping method of encoded data

The UE may multiplex part of HP UCI and LP UCI, and may transmit multiplexed UCIs (eg, part of HP UCI + LP UCI) through PUCCH. The UE may determine the PUCCH resource set according to the size of the multiplexed UCIs. In this case, the PUCCH resource index may be indicated by the scheduling DCI. The scheduling DCI may be an HP DCI that instructs the UE to transmit the HP UCI. When the size of UCI is 3 bits or more, the UE may perform an independent encoding procedure for HP UCI and LP UCI.

When "PUSCH and PUSCH are located in the same symbol(s)" or "PUSCH is transmitted in a subslot in which PUCCH is transmitted", the UE transmits UCI (eg, HP UCI and/or LP UCI ) can be multiplexed in PUSCH. In this case, the TB (or data) included in the PUSCH may be rate matched or punctured according to the size of the UCI.

According to the technical standard, the TB may be coded, and the UCI (eg, HP UCI or LP UCI) may be multiplexed with the coded TB. If the size of the UCI is 1 bit or 2 bits, the UE may map the TB (eg, the coded TB) to the RE(s) of the PUSCH, and then spread the UCI to the corresponding UCI of the PUSCH May map to some RE(s). That is, the TB may be punctured. If the size of the UCI is 3 bits or more, the RE(s) to which the TB is mapped may be distinguished from the RE(s) to which the UCI is mapped. In this case, the UE may perform rate matching on a TB (eg, an encoded TB) and may perform rate matching on UCI. Rate matching when UCI is encoded according to a Reed Muller code may be different from rate matching when UCI is encoded according to a polar code.

LP UCI and HP UCI may be multiplexed, LP UCI may be nLP bits, and HP UCI may be nHP. In this case, rate matching of the TB may be performed as follows. For example, the UE may consider both nLP and nHP equally UCI, and thus may perform rate matching for TB.

Method 6.3-1: When nLP + nHP is 3 bits or more, rate matching for TB may be performed on all REs of the PUSCH except for REs occupied by LP UCI and HP UCI.

PUSCH transmission may be scheduled by HP DCI and/or LP DCI, and HP UCI may not be distinguished from LP UCI, and accordingly, rate matching of TB may be performed. However, if "HP UCI is 1 bit (eg, nHP = 1)" or "LP UCI is 2 bits (eg, nLP = 2)", according to method 6.3-1, the UE encodes procedure may be performed, and rate matching may be performed on the TB based on the result of the encoding procedure. According to the technical standard, when the UCI is 1 bit or 2 bits, the TB may be punctured. That is, the UCI may be remapped to the RE(s) to which the TB is mapped.

Another proposed method is "when HP UCI is 1 bit (eg, nHP = 1)" or "when LP UCI is 2 bits (eg, nLP = 2)", the terminal Cheering can be performed. When the HP UCI or the LP UCI is 3 bits or more, the UE may perform rate matching for the TB. If "HP UCI is 1 bit (eg nHP = 1)" or "LP UCI is 2 bits (eg nLP = 2)", the TB may be assumed to be punctured.

Method 6.3-2: When nLP + nHP is 3 bits (eg, when LP UCI is 1 bit and HP UCI is 2 bits), the UE may puncture the TB. When nLP + nHP exceeds 3 bits, the UE may perform rate matching with respect to the TB in the remaining REs except for the REs used by the corresponding UCI among all REs of the PUSCH.

6.4: CG (configured grant)-UCI transmission method

When the CG PUSCH is configured and/or activated, the UE may multiplex CG-UCI and TB, and may transmit the multiplexed CG-UCI and TB in the CG PUSCH. The CG-UCI may include HPN, RV, NDI, and/or COT related information.

When the terminal performs omni-directional or directional sensing to transmit the CG PUSCH, the COT-related information is "information indicating that the COT is regarded as the COT initiated by the terminal and the base station cannot use the corresponding COT" or " When the base station uses the corresponding COT, the length of the COT and the index of the channel access priority class (CAPC)” may be included. When the CG PUSCH is transmitted in the unlicensed band, the base station may instruct (or configure) the terminal to transmit the CG-UCI including COT-related information using RRC signaling.

The UE may multiplex LP UCI, HP UCI, and/or TB in CG PUSCH. The base station may transmit information on the priority of the CG PUSCH to the terminal using RRC signaling, and the terminal may check the priority of the CG PUSCH indicated by the base station. According to the technical standard, the UE may multiplex PUCCH and PUSCH having the same priority. The priority of PUCCH may follow the priority of UCI, and the priority of CG PUSCH may be indicated by RRC signaling. The UE may encode both CG-UCI and HARQ-ACK, and may equally calculate CG-UCI and HARQ-ACK to derive the size of UCI. When the priority of PUCCH is different from that of CG PUSCH, the UE may transmit a PUCCH or CG PUSCH having a high priority, and transmission of a CG PUSCH or PUCCH having a low priority may be dropped.

In order to compensate for the above-described problem, the UE may transmit both LP UCI and HP UCI in CG PUSCH. Whether to allow this operation may be indicated (or set) to the terminal by RRC signaling of the base station. When "transmission operation of LP UCI and HP UCI in CG PUSCH" is not permitted or indicated to the UE, the UE may multiplex CG PUSCH and UCI having the same priority according to a technical standard.

Method 6.4-1: The base station may indicate (or configure) whether to allow the multiplexing operation of UCI and CG PUSCH having different priorities to the terminal using RRC signaling.

The UE can distinguish between CG PUSCH and HARQ-ACK having the same priority, and generates a codeword by performing the same encoding procedure for “HARQ-ACK having the same priority as CG PUSCH” and CG-UCI. can do. The UE may generate a codeword by performing an encoding procedure for HARQ-ACK having a priority different from that of CG PUSCH, and may generate a codeword by performing an encoding procedure for CG-UCI. That is, each encoding procedure of HARQ-ACK and CG-UCI may be independently performed, and different codewords may be generated.

When the size of the HARQ-ACK having a different priority than the CG PUSCH is large, it may be desirable to drop the transmission of the corresponding HARQ-ACK in the CG PUSCH. In this case, the terminal may inform the base station whether transmission of the HARQ-ACK is dropped.

DCI including resource allocation information of HP HARQ-ACK and LP HARQ-ACK may indicate to the UE whether to perform a multiplexing operation for UCI. For example, the HP DCI may include "information indicating the performance of a multiplexing operation for UCI" or "information indicating the drop of UCI transmission". The UE may generate a PUCCH and check whether the time resource of the PUCCH overlaps the time resource of the CG PUSCH. When the PUCCH overlaps the CG PUSCH in the time domain, the UE may multiplex UCI to be transmitted through the PUCCH in the CG PUSCH.

However, the size of the CG PUSCH resource may not always be sufficient. When the size of the HARQ-ACK is large, since the number of REs that can be allocated to the TB is reduced, the effective code rate of the TB may be increased. When an error occurs in the PUSCH decoding procedure, the base station may transmit DCI for retransmission to the terminal, and the terminal may receive DCI for retransmission from the base station. Alternatively, in a communication system operating in an unlicensed band, the terminal may know the ACK or NACK for the PDSCH by receiving the CG-DFI from the base station. In this case, the UE may retransmit the same TB.

In order to support the above-described operation, CG-UCI (eg, a field of GC-UCI) may include NDI and RV. That is, the terminal may inform the base station whether to perform the TB retransmission operation by transmitting the CG-UCI. In this case, the terminal may additionally transmit information indicating whether to perform the multiplexing operation for the LP UCI and the HP UCI to the base station.

Method 6.4-2: A new field may be introduced into CG-UCI, and a new field having a first value may indicate that UCIs having different priorities are multiplexed. The new field having the second value may indicate "UCIs having the same priority are multiplexed, and UCI transmissions having different priorities are dropped".

6.5: CG-DFI (downlink feedback information) receiving method

The base station may transmit the DFI to the terminal. When the CG PUSCH is configured and/or activated in the UE, DCI format 0_1 may include a specific field. A specific field included in DCI format 0_1 may be referred to as a DFI flag, and the size of the DFI flag may be 1 bit.

"When DCI format 0_1 (eg, CRC of DCI format 0_1) is scrambled by a configured scheduling-radio network temporary identifier (CS-RNTI), and the DFI flag included in DCI format 0_1 has a first value", The UE may consider that the type 2 CG PUSCH is activated by DCI format 0_1 (eg, DFI flag). If "DCI format 0_1 is scrambled by CS-RNTI and the DFI flag included in DCI format 0_1 has a second value", the UE may consider the DFI flag included in DCI format 0_1 as CG-DFI. When DCI format 0_1 received from the UE is scrambled by C-RNTI, MCS-C-RNTI, or SP-CSI-RNTI, the UE may consider that the DFI flag is reserved.

The CG-DFI according to DCI format 0_1 may include a HARQ-ACK bitmap and a TPC command for PUSCH, and the remaining bits constituting DCI format 0_1 may be set to 0. The length of the DCI format 0_1 may be determined by a technical standard, a configuration of a base station, a relationship between a search space set, and/or a processing capability of a terminal.

Method 6.5-1: DCI format 0_2 may include CG-DFI, and when the DFI flag is the first value, DCI may be interpreted as CG-DFI.

"When DCI format 0_2 is scrambled by CS-RNTI and the DFI flag included in DCI format 0_2 has a first value", the UE determines that the type 2 CG PUSCH is determined by DCI format 0_2 (eg, DFI flag). can be considered active. If "DCI format 0_2 is scrambled by CS-RNTI and the DFI flag included in DCI format 0_2 has a second value", the UE may regard the DFI flag included in DCI format 0_2 as CG-DFI. When DCI format 0_2 received from the UE is scrambled by C-RNTI, MCS-C-RNTI, or SP-CSI-RNTI, the UE may consider that the DFI flag is reserved.

The CG-DFI according to DCI format 0_2 may include a HARQ-ACK bitmap and a TPC command for PUSCH, and the remaining bits constituting DCI format 0_2 may be set to 0. The length of DCI format 0_2 may be determined according to a technical standard, a configuration of a base station, a relationship between a search space set, and/or a processing capability of a terminal.

The size of the HARQ-ACK bitmap may be 16. The reason is that the HPN capable of transmitting the CG PUSCH is derived from the index of the start slot in which the CG PUSCH is transmitted and/or the offset set by RRC signaling. This is because, if the size of the HARQ-ACK bitmap is not the same in DCI format 0_1 and DCI format 0_2, DCI format 0_2 cannot include some HARQ-ACK bits.

The methods according to the present invention may be implemented in the form of program instructions that can be executed by various computer means and recorded in a computer-readable medium. The computer-readable medium may include program instructions, data files, data structures, etc. alone or in combination. The program instructions recorded on the computer-readable medium may be specially designed and configured for the present invention, or may be known and available to those skilled in the art of computer software.

Examples of computer-readable media include hardware devices specially configured to store and carry out program instructions, such as ROM, RAM, flash memory, and the like. Examples of program instructions include not only machine language codes such as those generated by a compiler, but also high-level language codes that can be executed by a computer using an interpreter or the like. The hardware device described above may be configured to operate as at least one software module to perform the operations of the present invention, and vice versa.

Although it has been described with reference to the above embodiments, it will be understood by those skilled in the art that various modifications and changes can be made to the present invention without departing from the spirit and scope of the present invention as set forth in the claims below. will be able

Claims (20)

A method of operating a terminal in a communication system, comprising:
selecting one or more control elements from among a plurality of control elements included in first uplink control information (UCI) in consideration of the size of an uplink resource;
generating multiplexed UCIs by multiplexing a second UCI with the one or more control elements; and
and transmitting the multiplexed UCIs to a base station through the uplink resource. The method according to claim 1,
"When the total size of the first UCI is the first size, and the first UCI having a second size smaller than the first size is multiplexable with the second UCI", the one or more of the plurality of control elements Control elements are selected, transmission of the remaining control elements is dropped (drop), the operating method of the terminal. The method according to claim 1,
When the plurality of control elements include channel state information (CSI) and hybrid automatic repeat request-acknowledgement (HARQ-ACK), the one or more control elements are "the HARQ-ACK", "a part of the CSI + the HARQ -ACK", "the CSI part 1 of the CSI + the HARQ-ACK", or "the CSI part 2 of the CSI + the HARQ-ACK", the method of operation of the terminal. The method according to claim 1,
The method of operation of the terminal,
The method further comprises receiving information indicating multiplexing of the first UCI and the second UCI from the base station,
When the information is received, the multiplexed UCIs are generated, the operating method of the terminal. The method according to claim 1,
The method of claim 1, wherein the first UCI is a low priority (LP) UCI having a low priority, and the second UCI is a high priority (HP) UCI having a high priority. The method according to claim 1,
The uplink resource is a physical uplink control channel (PUCCH) resource or a physical uplink shared channel (PUSCH) resource. The method according to claim 1,
The uplink resource is a PUCCH resource, and the PUCCH resource set to which the PUCCH resource belongs is determined in consideration of the size of the one or more control elements and the size of the second UCI. The method according to claim 1,
The method of operation of the terminal,
receiving first downlink control information (DCI) from the base station; and
Further comprising the step of receiving a second DCI from the base station,
The transmission of the first UCI is indicated by the first DCI, and the transmission of the second UCI is indicated by the second DCI. A method of operating a terminal in a communication system, comprising:
generating a first codeword for first uplink control information (UCI) based on a first code rate;
generating a second codeword for a second UCI based on a second code rate;
generating multiplexed UCIs by multiplexing the first codeword and the second codeword; and
and transmitting the multiplexed UCIs to a base station using a physical uplink control channel (PUCCH) resource. 10. The method of claim 9,
The method of operating a terminal, wherein the first code rate and the second code rate are related to the PUCCH resource. 10. The method of claim 9,
The method of claim 1, wherein the first code rate is associated with a first PUCCH format for the first UCI, and the second code rate is associated with a PUCCH resource for the second UCI. 10. The method of claim 9,
The first code rate is associated with a first PUCCH format for the first UCI, the second code rate is associated with a second PUCCH format for the second UCI, and the terminal operates. 10. The method of claim 9,
A first PUCCH format for the first UCI is derived by first downlink control information (DCI) received from the base station, and a second PUCCH format for the second UCI is obtained by a second DCI received from the base station Derived, the method of operation of the terminal. 10. The method of claim 9,
When the second code rate for the PUCCH resource for the second UCI is not specified, the second code rate is related to a format of the PUCCH resource for the second UCI, and the PUCCH resource for the second UCI When the second code rate is specified for , the second code rate is associated with a PUCCH resource for the second UCI. 10. The method of claim 9,
The PUCCH resource is configured for transmission of the second UCI, the first UCI is a low priority (LP) UCI having a low priority, and the second UCI is a high priority (HP) UCI having a high priority. , the method of operation of the terminal. As a terminal,
processor;
a memory in electronic communication with the processor; and
including instructions stored in the memory;
When the instructions are executed by the processor, the instructions cause the terminal to
selecting one or more control elements from among a plurality of control elements included in first uplink control information (UCI) in consideration of the size of a physical uplink control channel (PUCCH) resource;
generate multiplexed UCIs by multiplexing a second UCI with the one or more control elements; And
and cause to transmit the multiplexed UCIs to the base station through the PUCCH resource. 17. The method of claim 16,
"When the total size of the first UCI is the first size, and the first UCI having a second size smaller than the first size is multiplexable with the second UCI", the at least one of the plurality of control elements The control elements are selected and the transmission of the remaining control elements is dropped. 17. The method of claim 16,
When the plurality of control elements include channel state information (CSI) and hybrid automatic repeat request-acknowledgement (HARQ-ACK), the one or more control elements are "the HARQ-ACK", "a part of the CSI + the HARQ -ACK", "CSI part 1 of the CSI + the HARQ-ACK", or "CSI part 2 of the CSI + the HARQ-ACK", the terminal. 17. The method of claim 16,
A first codeword for the one or more control elements is generated based on a first code rate, and a second codeword for the second UCI is generated based on a second code rate, The first code rate or the second code rate is associated with the PUCCH resource. 17. The method of claim 16,
A first codeword for the one or more control elements is generated based on a first code rate, a second codeword for the second UCI is generated based on a second code rate, and the first code rate is Associated with a first PUCCH format for 1 UCI, the second code rate is associated with a second PUCCH format for the second UCI, and the first PUCCH format is set to be the same as or different from the second PUCCH format, terminal.

Images