KR20230017143A - Communication method and apparatus using multiple panels - Google Patents

Abstract

A method of a terminal comprises the following steps of: receiving a DCI from a base station including a first field indicating HARQ-ACK retransmission and a second field indicating priority; checking first HARQ-ACK information having the same priority as the priority indicated by the second field; and transmitting a first HARQ-ACK codebook including the first HARQ-ACK information to the base station based on an indication of the first field.

Description

Communication method and apparatus using multiple panels {COMMUNICATION METHOD AND APPARATUS USING MULTIPLE PANELS}

The present invention relates to a communication technology using multiple panels, and more particularly, to a communication technology using multiple panels in a communication system including one or more transmission reception points (TRPs).

Along 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), which are defined in the 3rd generation partnership project (3GPP) standard. LTE may be one wireless communication technology among 4th generation (4G) wireless communication technologies, and NR may be one wireless communication technology among 5th generation (5G) wireless communication technologies.

For the processing of rapidly increasing wireless data after the commercialization of 4G communication systems (eg, communication systems supporting LTE), the frequency band (eg, frequency bands below 6 GHz) of the 4G communication system as well as the 4G communication system A 5G communication system (eg, a communication system supporting NR) using a frequency band higher than the frequency band (eg, a frequency band of 6 GHz or higher) is being considered. The 5G communication system may support eMBB (enhanced Mobile BroadBand), URLLC (Ultra-Reliable and Low Latency Communication), and mMTC (massive machine type communication). Discussion on the 6G communication system after the 5G communication system is in progress.

Meanwhile, a plurality of transmission reception points (TRPs) may be introduced into the communication system. In this case, the terminal may be connected to a plurality of TRPs and may perform communication with the plurality of TRPs. A plurality of TRPs may provide communication services to terminals based on various communication schemes. For coherent communication in a communication system including a plurality of TRPs, a synchronization method of a plurality of TRPs and/or a method of sharing channel state information (CSI) reporting may be required.

An object of the present invention to solve the above problems is to provide a communication method and apparatus using multiple panels in a communication system including one or more transmission reception points (TRPs).

A method of a terminal according to a first embodiment of the present invention for achieving the above object includes receiving DCI from a base station including a first field indicating HARQ-ACK retransmission and a second field indicating priority, Checking first HARQ-ACK information having the same priority as the priority indicated by the second field, and based on the indication of the first field, a first step including the first HARQ-ACK information 1 HARQ-ACK codebook is transmitted to the base station.

The method of the terminal may further include checking second HARQ-ACK information having the same priority as the priority indicated by the second field, including the second HARQ-ACK information The second HARQ-ACK codebook may be transmitted to the base station together with the first HARQ-ACK codebook.

The first HARQ-ACK codebook may be a retransmission HARQ-ACK codebook, the second HARQ-ACK codebook may be a first transmission codebook, and the second HARQ-ACK codebook within the HARQ-ACK bit stream may be the first HARQ-ACK codebook. It may be placed before the HARQ-ACK codebook.

The method of the terminal includes the steps of checking second HARQ-ACK information having the same priority as the priority indicated by the second field, and the same priority as the priority indicated by the second field. It may further include checking third HARQ-ACK information having, wherein a second HARQ-ACK codebook including the second HARQ-ACK information and a third HARQ-ACK codebook including the third HARQ-ACK information An ACK codebook may be transmitted to the base station together with the first HARQ-ACK codebook.

The first HARQ-ACK codebook may be a retransmission HARQ-ACK codebook, the second HARQ-ACK codebook may be an initial transmission codebook, the third HARQ-ACK codebook may be a delayed SPS HARQ-ACK codebook, , The second HARQ-ACK codebook may be placed first in the HARQ-ACK bit stream, the third HARQ-ACK codebook may be placed after the second HARQ-ACK codebook, and the third HARQ-ACK codebook After the codebook, the first HARQ-ACK codebook may be placed.

A cell in which the first HARQ-ACK codebook is transmitted may be determined based on the format of the DCI.

When the DCI is a fallback DCI, the first HARQ-ACK codebook may be transmitted in PCell.

The method of the terminal may further include receiving configuration information of a PUCCH serving cell from the base station, and when the DCI is a non-fallback DCI, the first HARQ-ACK codebook according to the configuration information It may be transmitted in a PUCCH serving cell.

The method of the terminal may further include receiving configuration information of a PUCCH serving cell from the base station, and "the DCI is a non-fallback DCI and the DCI indicates a cell in which PUCCH transmission is performed. field", the first HARQ-ACK codebook may be transmitted in the PCell or the PUCCH serving cell based on the value of the third field.

The DCI may be a non-scheduling DCI.

A method of a base station according to a second embodiment of the present invention for achieving the above object includes generating a DCI including a first field indicating whether HARQ-ACK retransmission is performed and a second field indicating priority , transmitting the DCI to the terminal, and when the first field indicates retransmission of the HARQ-ACK, first HARQ-ACK information having the same priority as the priority indicated by the second field Receiving a first HARQ-ACK codebook containing from the terminal.

A second HARQ-ACK codebook including second HARQ-ACK information having the same priority as the priority indicated by the second field may be received from the terminal together with the first HARQ-ACK codebook, The first HARQ-ACK codebook may be a retransmission HARQ-ACK codebook, the second HARQ-ACK codebook may be a first transmission codebook, and the second HARQ-ACK codebook within the HARQ-ACK bit stream may be the first HARQ-ACK codebook. It may be placed before the HARQ-ACK codebook.

A second HARQ-ACK codebook including second HARQ-ACK information having the same priority as the priority indicated by the second field and having the same priority as the priority indicated by the second field A third HARQ-ACK codebook including third HARQ-ACK information may be received from the terminal together with the first HARQ-ACK codebook, and the first HARQ-ACK codebook may be a retransmission HARQ-ACK codebook, The second HARQ-ACK codebook may be an initial transmission codebook, the third HARQ-ACK codebook may be a delayed SPS HARQ-ACK codebook, and within the HARQ-ACK bit stream, the second HARQ-ACK codebook is first may be arranged, the third HARQ-ACK codebook may be arranged after the second HARQ-ACK codebook, and the first HARQ-ACK codebook may be arranged after the third HARQ-ACK codebook.

A cell in which the first HARQ-ACK codebook is received may be determined based on the format of the DCI, and when the DCI is a fallback DCI, the first HARQ-ACK codebook may be received in a PCell, and the DCI may be -In case of fallback DCI, the first HARQ-ACK codebook may be received in the PCell or PUCCH serving cell.

The method of the base station may further include transmitting configuration information of a PUCCH serving cell to the terminal, and the PUCCH serving cell may be used for transmission and reception of the first HARQ-ACK codebook.

A terminal according to a third embodiment of the present invention for achieving the above object includes a processor, a memory electronically communicating with the processor, and instructions stored in the memory, and when the instructions are executed by the processor, The commands include the terminal receiving a DCI including a first field indicating HARQ-ACK retransmission and a second field indicating a priority from a base station, and having the same priority as the priority indicated by the second field. Check first HARQ-ACK information having a priority, and transmit a first HARQ-ACK codebook including the first HARQ-ACK information to the base station based on the indication of the first field.

The commands may be further executed so that the terminal checks second HARQ-ACK information having the same priority as the priority indicated by the second field, and the second HARQ-ACK information including the second HARQ-ACK information The HARQ-ACK codebook may be transmitted to the base station together with the first HARQ-ACK codebook, the first HARQ-ACK codebook may be a retransmission HARQ-ACK codebook, and the second HARQ-ACK codebook may be a first transmission code book, and the second HARQ-ACK codebook within the HARQ-ACK bit stream may be placed earlier than the first HARQ-ACK codebook.

The commands are for the terminal to check second HARQ-ACK information having the same priority as the priority indicated by the second field, and the same priority as the priority indicated by the second field. It may be further executed to check third HARQ-ACK information having, the second HARQ-ACK codebook including the second HARQ-ACK information and the third HARQ-ACK codebook including the third HARQ-ACK information It may be transmitted to the base station together with the first HARQ-ACK codebook, the first HARQ-ACK codebook may be a retransmission HARQ-ACK codebook, the second HARQ-ACK codebook may be a first transmission codebook, and the The third HARQ-ACK codebook may be a delayed SPS HARQ-ACK codebook, the second HARQ-ACK codebook may be placed first in the HARQ-ACK bit stream, and the second HARQ-ACK codebook is followed by the second HARQ-ACK codebook. 3 HARQ-ACK codebooks may be arranged, and the first HARQ-ACK codebook may be arranged after the third HARQ-ACK codebook.

A cell in which the first HARQ-ACK codebook is transmitted may be determined based on the format of the DCI, and when the DCI is a fallback DCI, the first HARQ-ACK codebook may be transmitted in a PCell, and the DCI is -In case of fallback DCI, the first HARQ-ACK codebook may be transmitted in the PCell or PUCCH serving cell.

The commands may be further executed so that the terminal receives configuration information of a PUCCH serving cell from the base station, and the PUCCH serving cell may be used for transmission and reception of the first HARQ-ACK codebook.

According to the present application, a base station may transmit downlink control information (DCI) including a field instructing hybrid automatic repeat request-acknowledgement (HARQ-ACK) retransmission to a terminal. The terminal may receive DCI from the base station and may retransmit the HARQ-ACK codebook to the base station based on the field included in the DCI. At this time, the terminal may multiplex a plurality of HARQ-ACK codebooks and transmit the multiplexed HARQ-ACK codebooks to the base station. HARQ-ACK codebooks may be arranged in a HARQ-ACK bit stream according to a preset order. Therefore, 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 conceptual diagram illustrating a first embodiment of a method of supporting eMBB traffic and/or URLLC traffic in a communication system including a plurality of TRPs.
4 is a conceptual diagram illustrating a first embodiment of a UL communication method using a Tx beam (or Tx panel).
5 is a conceptual diagram illustrating a first embodiment of a DL communication method using an Rx beam (or Rx panel).
6 is a flowchart illustrating a first embodiment of a method of performing overlapped UL transmissions in the time domain.
7 is a flowchart illustrating a second embodiment of a method of performing overlapped UL transmissions in the time domain.
8 is a flowchart illustrating a third embodiment of a method for performing overlapped UL transmissions in the time domain.
9 is a conceptual diagram illustrating a first embodiment of a CG resource selection method for CG PUSCH.
10 is a conceptual diagram illustrating a first embodiment of a method of mapping code bits.
11 is a conceptual diagram illustrating a first embodiment of a mapping method in CG resources.
12 is a flowchart illustrating a first embodiment of a PUCCH transmission method when UCI 1 and UCI 0 occur.
13 is a conceptual diagram illustrating a first embodiment of a method for simultaneous transmission of a PUCCH and a PUSCH involving a sidelink HARQ codebook.
14 is a conceptual diagram illustrating a second embodiment of a method for simultaneous transmission of a PUCCH and a PUSCH involving a sidelink HARQ codebook.
15 is a conceptual diagram illustrating a third embodiment of a method for simultaneous transmission of a PUCCH and a PUSCH involving a sidelink HARQ codebook.
16 is a conceptual diagram illustrating a first embodiment of a method of checking information on a plurality of TRPs at one location in a GC-DCI.
17 is a conceptual diagram illustrating a first embodiment of a method for checking information on a plurality of serving cells and a plurality of TRPs at one location in a GC-DCI.
18 is a conceptual diagram illustrating a first embodiment of a method for acquiring information at two or more locations within a GC-DCI.
19 is a conceptual diagram illustrating a first embodiment of GC-DCI including beam information.
20 is a conceptual diagram illustrating a first embodiment of (sub)slot configuration when a reference subcarrier spacing in a reference serving cell is different from a subcarrier spacing in a PUCCH serving cell.
21 is a conceptual diagram illustrating a second embodiment of (sub)slot configuration when a reference subcarrier spacing in a reference serving cell is different from a subcarrier spacing in a PUCCH serving cell.
22 is a conceptual diagram illustrating a first embodiment of a timing of changing a state of a serving cell.
23 is a conceptual diagram illustrating a first embodiment of a method for changing a DL BWP.
24 is a conceptual diagram illustrating a first embodiment of a method for changing UL BWP.
25 is a conceptual diagram illustrating a first embodiment of a method of interpreting offset 1 indicating retransmission of a PUCCH.
26 is a conceptual diagram illustrating a second embodiment of a method of interpreting offset 1 indicating retransmission of a PUCCH.
27 is a conceptual diagram illustrating a third embodiment of a method of interpreting offset 1 indicating retransmission of a PUCCH.
28 is a conceptual diagram illustrating a first embodiment of a method of transmitting a PUCCH based on the number of repetitions of an HARQ codebook.
29 is a conceptual diagram illustrating a first embodiment of a method of canceling repeated transmission of PUCCH.
30 is a conceptual diagram illustrating a first embodiment of a PRB belonging to PUCCH format 2.
31 is a conceptual diagram illustrating a first embodiment of a method of multiplexing HP UCI and LP UCI in PUCCH format 2 having two OFDM symbols.

Since the present invention can make various changes and 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 should be understood to include all modifications, equivalents, and substitutes included in the spirit and scope of the present invention.

Terms such as first and second may be used to describe various components, but the components should not be limited by the terms. These terms are only used for the purpose of distinguishing one component from another. For example, a first element may be termed a second element, and similarly, a second element may be termed a first element, without departing from the scope of the present invention. The term "and/or" includes any 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, “one or more of A and B” may mean “one or more of A or B” or “one or more of combinations of one or more of A and B”.

It is understood that when an element is referred to as being "connected" or "connected" to another element, it may be directly connected or connected to the other element, but other elements may exist in the middle. It should be. On the other hand, when an element is referred to as “directly connected” or “directly connected” to another element, it should be understood that no other element exists in the middle.

Terms used in this application are only used to describe specific embodiments, and are not intended to limit the present invention. Singular expressions include plural expressions unless the context clearly dictates otherwise. In this application, the terms "include" or "have" are intended to designate that there is a feature, number, step, operation, component, part, or combination thereof described in the specification, but one or more other features It should be understood that the presence or addition of numbers, steps, operations, components, parts, or combinations thereof is not precluded.

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 the present invention belongs. Terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with the meaning in the context of the related art, and unless explicitly defined in this application, they should not be interpreted in an ideal or excessively formal meaning. don't

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

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

In an embodiment, “setting an operation (eg, transmission operation)” means “setting information for the corresponding operation (eg, information element, parameter)” and/or “performing the corresponding operation”. It may mean that the "instructing information" is signaled. "Setting an information element (eg, parameter)" may mean that a corresponding information element is signaled. Signaling is system information (SI) signaling (eg, system information block (SIB) and / or transmission of MIB (master information block)), RRC signaling (eg, RRC message, RRC parameter, and / or upper layer transmission of parameters), MAC control element (CE) signaling (eg, transmission of MAC messages and/or MAC CE), or PHY signaling (eg, downlink control information (DCI), uplink control information (UCI), and/or transmission of sidelink control information (SCI).

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

Referring to FIG. 1, a communication system 100 includes 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 includes a core network (eg, a serving-gateway (S-GW), a packet data network (PDN)-gateway (P-GW), and a mobility management entity (MME)). can include more. When the communication system 100 is a 5G communication system (eg, a new radio (NR) system), the core network includes an access and mobility management function (AMF), a user plane function (UPF), a session management function (SMF), and the like. can include

The plurality of communication nodes 110 to 130 may support communication protocols (eg, LTE communication protocol, LTE-A communication protocol, NR communication protocol, etc.) defined in the 3rd generation partnership project (3GPP) standard. The 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) 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, NOMA (Non-orthogonal Multiple Access) 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 , a 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 component included in the communication node 200 may be connected by a bus 270 to communicate with each other.

However, each component included in the communication node 200 may be connected through an individual interface or an individual bus centered on the processor 210 instead of the common bus 270 . For example, the processor 210 may be connected to at least one of the memory 220, the transmission/reception device 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 refer to 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 include at least one of a volatile storage medium and a non-volatile storage medium. For example, the memory 220 may include 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, 120-2), 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), a gNB, an advanced base station (ABS), and a HR -BS (high reliability-base station), BTS (base transceiver station), radio base station, radio transceiver, access point, access node, radio access station (RAS) ), 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, and 130-6 includes user equipment (UE), terminal equipment (TE), advanced mobile station (AMS), HR-MS (high reliability-mobile station), terminal, access terminal, mobile terminal, station, subscriber station, mobile station, mobile 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, and , 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 a corresponding terminal 130-1, 130-2, 130-3, and 130 -4, 130-5, 130-6), and signals received from corresponding terminals 130-1, 130-2, 130-3, 130-4, 130-5, 130-6 are 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 multi-input multi-output (MIMO) (eg, single user (SU)- MIMO, MU (multi user)-MIMO, massive MIMO, etc.), CoMP (coordinated multipoint) transmission, carrier aggregation (CA) transmission, transmission in unlicensed band, direct communication between devices (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, and 130-6 is a base station 110-1, 110-2, 110-3, 120-1 , 120-2) 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 can transmit a signal to the fourth terminal 130-4 based on the SU-MIMO scheme, and the fourth terminal 130-4 uses the SU-MIMO scheme. 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 terminal 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 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 CoMP. Each of the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 includes a terminal 130-1, 130-2, 130-3, and 130-4 belonging to its own cell coverage. , 130-5, 130-6) and a CA method. 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 (for example, transmission or reception of a signal) performed in a first communication node among communication nodes is described, a second communication node corresponding thereto is described as a method performed in the first communication node and a method (eg, signal transmission or reception) For example, receiving or transmitting a signal) may be performed. That is, when the operation of the terminal is described, the corresponding base station may perform an operation corresponding to the operation of the terminal. Conversely, when the operation of the base station is described, a terminal corresponding thereto may perform an operation corresponding to the operation of the base station.

A scenario to which communication is applied may be an Enhanced Mobile BroadBand (eMBB) scenario, a Massive Machine-Type Communication (mMTC) scenario, an Ultra-Reliable and Low Latency Communication (URLLC) scenario, and/or Time Sensitive Communication (TSC). The mMTC scenario, the URLLC scenario, and/or the TSC scenario can be applied in IoT (Internet of Things) communication. One communication network (eg, one communication system) can support all of the scenarios described above or some of the scenarios described above. In a communication network supporting the mMTC scenario, IMT-2020 requirements can be satisfied using NB (narrowband)-IoT and LTE-MTC. A lot of discussion may be needed to satisfy the requirements in a communication system that supports the URLLC scenario.

In order to reduce the error rate of data, a low modulation and coding scheme (MCS) level (eg, low MCS index) may be applied. In order to prevent the size of a field indicated by downlink control information (DCI) from increasing, the most frequently used MCS(s) may be selected. Then, in order to apply a low MCS, repeated transmission operation can be supported. Since the modulation rate of quadrature phase shift keying (QPSK) is the lowest, an effect of further lowering the code rate may occur. In particular, since transmit power is limited in uplink (UL) transmission, repeated transmission operations may be performed in the time domain rather than the frequency domain.

Enhanced Mobile BroadBand (eMBB) traffic and Ultra-Reliable and Low Latency Communication (URLLC) traffic can use low MCS for different purposes. eMBB traffic can use low MCS for reach extension. On the other hand, URLLC traffic can use a low MCS to reduce latency and obtain a low error rate. Since the necessary requirements are different, eMBB traffic can be repeatedly transmitted even if a delay occurs, and URLLC traffic can be transmitted using a new MCS (eg, low MCS) rather than repeated transmission. A new MCS may be established by an RRC message and/or DCI.

To support repeated transmission for eMBB traffic in the time domain, physical uplink shared channel (PUSCH) repetition (eg, PUSCH repetition type A) may be introduced. In this case, the PUSCH allocated in units of slots may be repeatedly transmitted. To extend the reach, time resources may be allocated to a plurality of slots. When PUSCH repetition type A is used, time resources may be configured by RRC messages and/or DCI. The number of repetitions of PUSCH transmission may be indicated by an RRC message, and the time resource for transmitting the PUSCH in the first slot is DCI (eg, type 2 CG (configured grant) or dynamic grant) or RRC message (eg, type 1 CG).

In order to support URLLC traffic, it may be desirable for a UE to perform frequent reception operations in DL (downlink) resources and/or frequent transmission operations in UL (uplink) resources. In a time division duplex (TDD) system, a terminal may operate based on a half duplex scheme. Accordingly, the support time of DL traffic and/or UL traffic may increase according to a slot pattern. On the other hand, in a frequency division duplex (FDD) system, a UE may utilize DL resources and UL resources. Therefore, the problems described above in the TDD system may not occur in the FDD system. An FDD system may use two or more carriers. When two or more serving cells are configured in the UE in the TDD system, the UE can utilize DL and UL resources.

In a communication system including at least one carrier to which FDD is applied (hereinafter, referred to as "FDD carrier"), there may be no problem regarding delay time of a terminal. In a communication system including only carrier(s) to which TDD is applied (hereinafter, referred to as “TDD carrier(s)”), there may be a problem with respect to a delay time of a UE. In order to solve the above problem, slots in TDD carriers may be configured according to different patterns.

CA (carrier aggregation) may be configured in the terminal, and PCell and SCell (s) may be activated. Depending on whether a common search space (CSS) set is included, a cell may be classified as a PCell or a SCell. For example, a PCell may include a CSS set, and a SCell may not include a CSS set. To reduce delay time in a communication system supporting URLLC traffic, slots having different patterns may be set and/or instructed to the terminal.

Since delay time occurs when URLLC traffic is repeatedly transmitted, it may not be appropriate to repeatedly transmit URLLC traffic. However, when a sufficiently low MCS is used, the delay for decoding URLLC traffic can be reduced. That is, when a sufficiently low MCS is used, the number of resource elements (REs) to which URLLC traffic is mapped may increase, and the base station (eg, a decoder of the base station) has to wait until all REs are received. In this case, the delay for decoding URLLC traffic can be reduced.

On the other hand, when a PUSCH to which a slightly higher MCS is applied is repeatedly transmitted, the base station can perform a decoding operation with only some REs. Therefore, the point at which decoding is first successful in repeated PUSCH transmissions (eg, repeated PUSCH transmissions to which a slightly higher MCS is applied) is greater than the time when decoding is first successful in PUSCH transmissions without repetitions (eg, PUSCH transmissions to which a low MCS is applied). It can be fast. When PUSCH repetition type A is used, unnecessary delay may occur, and PUSCH repetition type B may be introduced to reduce delay time for repeated transmission. When PUSCH repetition type B is used, the PUSCH allocated in units of mini-slots may be repeatedly transmitted. When PUSCH repetition type B is used, time resources may be configured by RRC messages and/or DCI. The combination of the reference time resource of the PUSCH instance and the number of repeated transmissions may be indicated by a DCI (eg, type 2 CG and/or dynamic grant) or an RRC message (eg, type 1 CG).

In order to control transmission power of an SRS resource indicated by a sounding reference signal (SRS) resource indicator (SRI), a base station may estimate path attenuation for each SRS resource. The base station can control transmit power for SRS resource(s) using DCI. Transmit power of the SRS resource(s) may be controlled based on the estimated path attenuation. The DCI is a scheduling DCI (eg, DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 1_0, DCI format 1_1, or DCI format 1_2) or GC (group common)-DCI (eg, DCI format 2_2 Or it may be DCI format 2_3). The DCI may include a field indicating a transmit power control (TPC) command, and the TPC command may be used to control transmit power of the terminal. For example, transmit power of the terminal may be increased or decreased based on a TPC command included in the DCI. To determine the transmit power of the PUSCH, the UE may consider a value obtained based on path attenuation, a value according to a TPC command included in the DCI, and/or a PUSCH bandwidth indicated by the DCI.

The base station may configure two or more sets to the terminal using higher layer signaling. The terminal may receive configuration information of two or more sets from the base station. An element constituting each of the two or more sets may be transmit power parameter(s), and may be indicated to be suitable for different scenarios (eg, a URLLC scenario, an eMBB scenario). The UE may receive scheduling DCI or activating DCI for allocating PUSCH resources from the base station, and the scheduling DCI or activating DCI may indicate a set for interpreting transmit power parameter(s). When the set of transmit power parameter(s) is different, the size of increase or decrease of transmit power indicated by the same TPC command may be different.

When a type 1 CG or a type 2 CG is used, transmit power may be determined based on DCI format 2_3 for an SRI associated with a PUSCH instance. When type 2 CG is used, the activation DCI may indicate a set of transmit power parameter(s) applied to the PUSCH occasion. A PUSCH occasion may mean a PUSCH instance. The terminal may obtain a TPC command for the SRI by receiving a GC (group common)-DCI, may interpret the TPC command to be suitable for a set of transmit power parameter (s) indicated by the base station, and according to the interpretation result Based on this, transmit power applied to the PUSCH instance can be derived.

In dynamically scheduled PUSCH transmission, a UE may derive transmit power applied to a PUSCH instance based on a combination of GC-DCI and scheduling DCI. The terminal can check the TCP command of the SRI by receiving the GC-DCI, and can store the checked TCP command. In dynamically scheduled PUSCH transmission, a set of transmit power parameter(s) applied to the PUSCH occasion and/or a TPC command may be indicated by the scheduling DCI. The UE may derive transmit power applied to the PUSCH instance based on the transmit power of the SRI associated with the PUSCH instance.

Repeated HARQ-ACK transmission may be indicated (or configured) by higher layer signaling for each physical uplink control channel (PUCCH) format. The number of repeated transmissions for PUCCH format i may be independently set. i can be 1, 3, or 4. The UE may repeatedly transmit the PUCCH format in slots. In this case, the PUCCH format may be transmitted using the same time resource in each of the slots.

Uplink control information (UCI) types may be classified according to the type of information included in the UCI. UCI may include at least one of scheduling request (SR), reference signal received power (L1-RSRP), HARQ-ACK, or channel state information (CSI). In an embodiment, UCI and UCI type may be used in the same meaning. In the repeated transmission operation of UCI, only one UCI type can be transmitted. To support this behavior, the priority of UCI types can be defined in the technical specification. One UCI type may be selected, and a PUCCH including one UCI type may be repeatedly transmitted. In this case, the UE may assume that other UCI types are not transmitted before transmission of the corresponding UCI type is completed. To support this operation, the base station may instruct the terminal to transmit UCI (eg, SR or HARQ-ACK) after PUCCH transmission is completed. The waiting time for the corresponding UCI transmission may be large, and the corresponding waiting time may act as a constraint on scheduling to the base station.

"When it is indicated to transmit HARQ-ACKs in the same slot (or the same sub-slot)" or "PUCCH time resources indicated by a DCI and/or RRC message allocating a physical downlink shared channel (PDSCH) overlap with each other If ", the UE may generate an HARQ codebook to be transmitted on one PUCCH (eg, one PUCCH time resource). Within the HARQ codebook, HARQ-ACK bits may be arranged according to the order defined in the technical specification. Information bits may be generated by the above-described operation. The terminal may generate coded bits by performing an encoding operation.

In the encoding operation, Reed Muller codes or polar codes may be used. A code rate applied in an encoding operation may be indicated by higher layer signaling. For example, in the PUCCH format, one value may be a code rate and may be indicated to the terminal.

One codeword may be mapped to one PUCCH. In repeated PUCCH transmission operation, one UCI type may be generated as a codeword. When the PUCCH is transmitted once, information bits of one UCI type or two or more UCI types may be concatenated, and the terminal may generate one codeword by performing the same encoding operation on the information bits. When Reed Muller codes or polar codes are used, it may be difficult to implement a soft combining operation. Therefore, even when PUCCH is repeatedly transmitted, the same codeword can be transmitted, and the base station can perform a chase combining operation on the same codeword. An encoded bit or codeword may mean a bit string in which a plurality of code blocks are concatenated. A modulation operation may be performed on the codeword, and a result of the modulation operation may be mapped to an RE.

Meanwhile, the same UCI type may be regarded as different information. The same UCI type regarded as different information may be mapped. For example, UCI can be created to support traffic having different priorities. A UCI (eg, SR or HARQ-ACK) supporting eMBB traffic may be regarded as information differentiated from a UCI (eg, SR or HARQ-ACK) supporting URLLC traffic. In this case, even if the UCI type is the same, it can be distinguished by different information.

Encoded UCI may be mapped to PUCCH. In the PUCCH transmission operation, the same preprocessing method (eg, spatial information, spatial relation) may be maintained. Alternatively, in the PUCCH transmission operation, the use of different preprocessing schemes for each PUCCH may be allowed by RRC signaling of the base station.

In an embodiment, two or more terminals may receive data from one or more TRPs and transmit data to one or more TRPs. It may be assumed that one base station or one server performs a management operation and/or a scheduling operation for one or more TRPs among a plurality of TRPs. TRPs may be directly connected. Alternatively, TRPs may be connected through a base station. The above connection may be a connection according to an Xn interface or a radio interface (eg, a 3GPP NR interface).

A shadow area may occur between areas supported by TRPs. Therefore, TRPs can resolve the sound area through cooperative transmission. Cooperative transmission may be performed for a terminal located between TRPs. Even when a shadow area does not occur, the quality of a radio link can be improved by installing many TRPs (or base stations) to transmit and receive a lot of data.

According to cooperative transmission and cooperative reception of TRPs, communication schemes can be classified into dynamic point selection (DPS) and joint transmission (JT). For a specific physical resource block (PRB) set, DPS may be a method of receiving data through one TRP, and JT may be a method of receiving data through two or more TRPs. Dynamic point blanking (DPB) may be one type of JT. When DPB is used, the terminal may not receive data from some TRPs and may receive data from the remaining TRPs. JT can be classified into coherent JP and noncoherent JP. Coherent JP or non-coherent JP may be used depending on whether a coherent combining operation is performed on signals received from TRPs.

"When synchronization between TRPs is correct and CSI reporting is shared", a performance gain may be generated by a coherent combining operation performed in the UE. When the above-mentioned condition(s) is not satisfied, performing a non-coherent combining operation in the terminal may be advantageous in terms of performance.

When the terminal is mounted in a vehicle, there may be few restrictions on the size and/or weight of the corresponding terminal. Portability may be considered for a terminal directly used by a person.

Chapter 1 UL transmission method considering multiple panels

1.1 Multi-panel support

A terminal may communicate with one or more TRPs. The terminal may communicate with one TRP to transmit and receive eMBB traffic. A terminal may communicate with two or more TRPs to transmit and receive URLLC traffic. Each of the aforementioned TRPs may support one or more traffic types. For example, TRP may support "eMBB traffic", "URLLC traffic", or "both eMBB traffic and URLLC traffic". The terminal transmits the same type of traffic (eg, eMBB traffic or URLLC traffic) or different types of traffic (eg, eMBB traffic and URLLC traffic) according to the configuration indicated by scheduling DCI and/or RRC signaling. can support The same kind of traffic can be eMBB traffic or URLLC traffic. Traffic of the same type may have different quality of service (QoS). For example, traffic derived from an XR service can be classified into traffic with I-frames and traffic with P-frames, and traffic with I-frames and traffic with P-frames can have different QoS. there is. Traffic having different QoSs may be mapped to different data radio bearers (DRBs). The base station and/or terminal may support the above-described operation.

3 is a conceptual diagram illustrating a first embodiment of a method of supporting eMBB traffic and/or URLLC traffic in a communication system including a plurality of TRPs.

Referring to FIG. 3, a terminal can communicate with three TRPs. The three TRPs may be connected to one or more base stations. A terminal may have one or more panels (eg, antenna panels, Tx panel, Rx panel). eMBB traffic may be transmitted and received in a low frequency band (eg FR1), and URLLC traffic may be transmitted and received in a high frequency band (eg FR2) as well as a low frequency band (eg FR1). Because a wide bandwidth is required to support URLLC traffic, URLLC traffic may not be supported in FR1 depending on the frequency distribution. Since FR2 has a wide bandwidth, URLLC traffic can be supported in FR2 when the channel condition of TRP is good. Since blockage frequently occurs in FR2, it may be desirable to use multiple TRPs. For example, three TRPs may support URLLC traffic.

A terminal may have a plurality of Tx panels and a plurality of Rx panels. The number of panels (eg, Tx panels and/or Rx panels) used in the terminal may be indicated or configured through explicit signaling or implicit signaling. For example, scheduling information (eg, DCI) may indicate an index of an Rx beam receiving a PDSCH to a UE. Scheduling information (eg, DCI) may indicate the index of the Tx beam transmitting the PUSCH to the UE. A terminal may use a plurality of panels to generate Rx beam(s) or Tx beam(s). In an embodiment, a panel may mean an Rx panel, a Tx panel, and/or an antenna panel.

The base station transmits scheduling information indicating performance of a transmission operation using a plurality of Tx beams simultaneously (eg, a transmission operation based on frequency division multiplexing (FDM) or a transmission operation based on spatial division multiplexing (SDM)) to the terminal. can The base station may transmit scheduling information indicating execution of a reception operation (eg, an FDM-based reception operation or an SDM-based reception operation) using a plurality of Rx beams simultaneously to the terminal. The number of beams simultaneously used in the transmission operation or the reception operation may correspond to the minimum number of panels simultaneously used by the terminal. This is because one beam is generally generated for each panel when the terminal forms a beam. When two or more beams are generated from one panel, the number of beams simultaneously used in a transmission operation or a reception operation may not correspond to the number of panels.

Method 1.1-1: The terminal may report capability information including information indicating the maximum number of Tx beams and/or the maximum number of Rx beams that can be simultaneously processed (eg, simultaneously used) to the base station. there is.

Each of the maximum number of Tx beams and the maximum number of Rx beams may be expressed as an independent parameter, and the corresponding parameter may be included in RRC signaling. A combination of the maximum number of Tx beams and the maximum number of Rx beams may be expressed as one parameter, and the corresponding parameter may be included in RRC signaling.

The reference signal may be transmitted and received through a beam (eg, a Tx beam and/or an Rx beam) and/or a panel (eg, a Tx panel and/or an Rx panel). In an embodiment, an operation related to the Tx beam may be interpreted as an operation related to the Tx panel, and an operation related to the Tx panel may be interpreted as an operation related to the Tx beam. In an embodiment, an operation related to the Rx beam may be interpreted as an operation related to the Rx panel, and an operation related to the Rx panel may be interpreted as an operation related to the Rx beam. Reference signals associated with a common beam may be interpreted as belonging to the same reference signal (RS) group. RS groups can be distinguished by different antenna ports.

4 is a conceptual diagram illustrating a first embodiment of a UL communication method using a Tx beam (or Tx panel).

Referring to FIG. 4 , a terminal may perform UL communication using two Tx beams. The PUCCH, PUSCH, and/or RS group may be transmitted through each Tx beam of the UE. The RS group may be indicated or configured in the terminal. Alternatively, the UE may implicitly derive the RS group.

5 is a conceptual diagram illustrating a first embodiment of a DL communication method using an Rx beam (or Rx panel).

Referring to FIG. 5 , a terminal may perform DL communication using two Rx beams. The PDCCH, PDSCH, and/or RS group may be received through each Rx beam of the UE. The RS group may be indicated or configured in the terminal. Alternatively, the UE may implicitly derive the RS group.

An RS group may be represented by an RS index (eg, an RS resource index, a synchronization signal block (SSB) index, a CSI-RS ID, and a CSI-RS resource ID) belonging to the corresponding RS group. RS configuration information may include an RS group ID (eg, an RS group index). In an embodiment, the RS index may mean including the RS resource index, and the CSI-RS ID may mean including the CSI-RS resource ID.

qcl-type1, qcl-type2, "qcl-type1 and qcl-type2", or other RS indexes that provide spatial relation information (e.g. RS resource index SSB index, CSI-RS ID, CSI-RS resource ID) is indicated or configured, the UE can check the SSB index referenced by the RS. SSB indices may belong to different groups (eg, different RS groups). An SSB index may be regarded as one group (eg, RS group). SSB indexes can be managed using a separate ID.

In the DL beam management procedure, the base station can manage the transmission configuration indication (TCI) state of the RS as a valid value using a MAC control element (CE). When an RS group for one RS is indicated or configured, the RS group may be updated by MAC signaling.

Method 1.1-2: When the RS group to which the RS belongs is configured, the RS group ID (eg, RS group index) may be changed using MAC CE.

To transmit one beam, a UE may use two or more Tx panels. In this case, an RS group to which an RS used to derive one beam belongs may correspond to two or more Tx panels.

Method 1.1-3: The UE may consider that the same beam is applied to RS(s) belonging to the same RS group.

Different beams may be applied to RSs belonging to different RS groups. In this case, when RSs belonging to different RS groups are simultaneously transmitted or received, the terminal may regard interference between the RSs as insignificant.

The UE may regard RSs that do not belong to the same RS group as different antenna ports.

1.2 Power control and reporting

In the UL communication procedure, the terminal may receive configuration information of transmit power from the base station. The UE may check transmit power based on a value of a transmission power control (TPC) field included in the scheduling DCI. Alternatively, the terminal may check transmit power based on a block at a specific position in the group common DCI. The terminal may report power headroom to the base station. The power headroom may be “maximum power minus power used (eg, actual transmitted power)” or “maximum power minus reference format power”. When UL communication is scheduled, power used may mean power actually used. If UL communication is not scheduled, the reference format power may be derived based on technical specifications.

The terminal may simultaneously use one or more Tx beams (or one or more Tx panels). In this case, the terminal may use one or more power amplifiers. When one power amplifier is used, since the terminal must use the common maximum power of Tx beams, the UL communication procedure may not be performed according to technical standards.

A Tx beam may have different power control parameters, and different commands may be accumulated. Power control parameters may be divided into parameters (eg, variables) required for open loop control and parameters required for closed loop control. Parameters required for open loop control may include at least path loss and fractional path loss compensation. The above parameters may be set independently for each Tx beam. That is, the above parameters may have independent values. When performing a power control operation using a sounding reference signal (SRS) is configured in the UE, the UE may derive a DL RS and/or SSB index for calculating path loss based on the SRI included in the scheduling DCI.

The same frequency resource can be scheduled for Tx beams. In this case, in order to utilize the common maximum power, two Tx beams may be simultaneously used, and one Tx beam among the two Tx beams may be interpreted as having a high priority.

When the terminal uses two Tx beams, the use of the two Tx beams may be indicated by one scheduling information or different scheduling information. One piece of scheduling information may instruct the UE to use one or more Tx beams. When two or more Tx beams are used, UL transmissions may overlap in the time domain.

A Tx beam can be interpreted as a Tx panel. The Tx panel may be configured or instructed to the UE by explicit signaling or implicit signaling. Since the RS group is configured in the UE by RRC signaling, the Tx panel can be implicitly indicated to the UE.

When two Tx beams are simultaneously used by one scheduling information (eg, DCI and/or RRC signaling), sufficient power can be allocated to one Tx beam, and the remaining power can be allocated to another Tx beam. can

As a method for instructing or setting two Tx beams to the UE using one scheduling information, "a method in which two RS indexes are derived from one index" or "a method in which an RS index is directly indicated" can be used. there is. In this case, based on the method defined in the technical standard, one RS index may be considered preferentially, and sufficient power may be allocated to the RS considered preferentially.

The UE can simultaneously transmit beams derived from RS 1 (or the RS group to which RS 1 belongs) and RS 2 (or the RS group to which RS 2 belongs). When RSs are derived in the order of “RS 1 → RS 2” based on scheduling information, sufficient power may be allocated to a beam corresponding to RS 1.

Method 1.2-1: When scheduling information indicates two or more RSs to determine the Tx beam (or Tx panel) of the UE, sufficient power may be allocated to the RSs corresponding to the order defined in the technical standard.

One scheduling information may indicate one Tx beam. The UE can receive two pieces of scheduling information, check two Tx beams based on the two pieces of scheduling information, and transmit two Tx beams simultaneously. In this case, one RS index may be directly or indirectly derived from one scheduling information. The terminal can allocate sufficient power to the beam by selecting one scheduling information from among two pieces of scheduling information.

When each scheduling information is received on different PDCCH monitoring occasions (MOs), the UE may compare the order of different PDCCH MOs. The UE can compare the order of PDCCH MOs in the frequency domain and then compare the order of PDCCH MOs in the time domain.

Method 1.2-2: One scheduling information may indicate the use of one Tx beam, and the terminal may receive a plurality of scheduling information. According to the plurality of scheduling pieces of information, simultaneous transmission of a plurality of Tx beams may be indicated. In this case, the UE can allocate sufficient power to the Tx beam according to scheduling information received in the early PDCCH MO among PDCCH MOs for which a plurality of scheduling information items have been received.

1.3 Simultaneous support of UL transmissions considering RS group

The UE can simultaneously perform UL transmissions. In this case, the amount of transmit power available in the terminal and/or the Tx beam may be considered. It can be assumed that the terminal has the ability to perform two UL transmissions. If the terminal does not have the capability of performing two UL transmissions, the base station may not schedule for two UL transmissions. The UE can multiplex uplink control information (UCI) and data in one UL transmission procedure.

Two or more UL transmissions may overlap in the time domain. In this case, the terminal can determine whether the transmit power is sufficient. Tx beams for two or more UL transmissions can be interpreted as the same.

6 is a flowchart illustrating a first embodiment of a method of performing overlapped UL transmissions in the time domain.

Referring to FIG. 6, the base station may schedule two or more UL transmissions overlapping in the time domain to the terminal (S601). The UE may determine whether transmission power for two or more UL transmissions is sufficient. If the transmit power of the UE is sufficient, the corresponding UE can simultaneously perform two or more UL transmissions (S602). If the transmit power of the terminal is not sufficient, the corresponding terminal may perform one UL transmission (S603). Information required in step S603 may be multiplexed (eg, piggybacked).

Since the Tx beam (or Tx panel) is considered, a procedure for determining whether Tx beams for UL transmissions overlapping in the time domain are the same may be necessary.

7 is a flowchart illustrating a second embodiment of a method of performing overlapped UL transmissions in the time domain.

Referring to FIG. 7, the base station may schedule two or more UL transmissions overlapping in the time domain to the terminal (S701). The UE may determine whether Tx beams (eg, RS groups) for two or more UL transmissions are the same. After that, the UE can determine whether the transmit power for two or more UL transmissions is sufficient. If "Tx beams for two or more UL transmissions are different from each other and transmit power is not sufficient", the terminal may perform some UL transmission(s) among the two or more UL transmissions (S702). "When Tx beams for two or more UL transmissions are different and transmit power is sufficient" or "when Tx beams for two or more UL transmissions are the same and transmit power is sufficient", the UE transmits two or more UL Transmissions can be performed simultaneously (S703). If "the Tx beams for two or more UL transmissions are the same and the transmit power is not sufficient", the UE may perform one UL transmission (S704). In step S704, necessary information may be multiplexed (eg, piggybacked).

"When two or more UL transmissions using two or more Tx beams are scheduled for a UE and the transmit power of the UE is not sufficient", the UE may select some UL transmission (s) based on priority, and the remaining UL transmission (s) can be dropped. If "two or more UL transmissions using the same Tx beam are scheduled for the UE and the transmit power of the UE is insufficient", the UE may perform one UL transmission based on the piggyback method.

8 is a flowchart illustrating a third embodiment of a method for performing overlapped UL transmissions in the time domain.

Referring to FIG. 8, the base station may schedule two or more UL transmissions overlapping in the time domain to the terminal (S801). The UE may determine whether transmission power for two or more UL transmissions is sufficient. If the transmit power of the terminal is sufficient, the corresponding terminal can simultaneously perform two or more UL transmissions (S802). If the transmit power of the UE is not sufficient, the UE may determine whether Tx beams (eg, RS groups) for two or more UL transmissions are the same. If Tx beams for two or more UL transmissions are different from each other, the UE may perform some UL transmission(s) among the two or more UL transmissions (S803). If the Tx beams for two or more UL transmissions are the same, the UE can perform one UL transmission (S804). In step S804, necessary information may be multiplexed (eg, piggybacked).

1.3.1 Multiplexing of PUCCHs

"If the UCI type has the same priority index (eg, the same priority) and PUCCHs associated with the corresponding UCI type overlap in some symbols", the UE can multiplex the PUCCHs. "If the UCI type is HARQ (hybrid automatic repeat request)-ACK, and PUCCH resources do not overlap in slot units (or subslot units)", the UE can multiplex HARQ-ACKs in one HARQ codebook, The corresponding HARQ codebook may be transmitted on PUCCH (eg, PUCCH resource). In an embodiment, HARQ-ACK may mean HARQ-ACK information or HARQ-ACK bits, and HARQ codebook may mean HARQ-ACK codebook.

Spatial relationship information derived from PUCCH resources may not be considered in the UCI multiplexing procedure. UCI types having different spatial relationship information can be multiplexed on PUCCH. If the UE is allowed to use a plurality of Tx panels or a plurality of Tx beams, the UE can simultaneously use one or more Tx beams for PUCCH transmission.

When Tx beams for PUCCH are the same or similar, UCI types can be multiplexed. If the Tx beam for PUCCH is different, UCI types may not be multiplexed. If UCI types are not multiplexed, the UE can simultaneously transmit two or more PUCCHs.

Method 1.3-1: The UE may check whether Tx beams of PUCCH associated with each UCI type are the same. If Tx beams of PUCCHs are different from each other, the UE may not multiplex UCI types on one PUCCH.

Method 1.3-2: In method 1.3-1, the UE can expect multiplexing of UCI types having the same Tx beam on one PUCCH.

The base station may instruct or set RSs determined to be the same Tx beam to the terminal using RRC signaling. The aforementioned RSs may include an SRS, a tracking RS (TRS), a CSI-RS, an SSB, and/or a physical random access channel (PRACH) preamble. In this case, the same Tx beam may be limited to the Tx beam applied to the last PRACH preamble used by the UE.

Method 1.3-3: The UE may receive RS group configuration information through RRC signaling, and share the same Tx beam (or qcl-Type 1, qcl-Type D) for RSs belonging to the RS group. can be considered

When RSs are divided into RS groups, the UE can apply the same Tx beam to transmit RS(s) belonging to the RS group. When method 1.3-1 is used, the UE can check the RS group to which the spatial relationship information belongs for the PUCCH associated with the UCI type.

If the same RS group is derived for different UCI types, the UE may consider using the same Tx beam. When different RS groups are derived for different UCI types, the UE may consider that different Tx beams are used. In this case, Method 1.3-1 can be applied.

When a UCI type different from link recovery request (LRR)/scheduling request (SR) is considered, the Tx beam may be different. The reason why LRR/SR is separately considered is that the UE transmits PUCCH in case of positive LRR/SR but does not transmit PUCCH in case of negative LRR/SR. The above-described operation may be expressed by on/off shift keying. In PUCCH for other UCI types, UCI may be expressed using a phase shift keying (PSK) symbol, and PUCCH may always be transmitted.

When periodic CSI, semi-persistent CSI, or configured grant (CG) PUSCH is configured, PUCCH for LRR/SR may overlap in the time domain. In this case, LRR/SR may be multiplexed with CSI or transport block (TB). When method 1.3-1 is applied, LRR/SR may not be multiplexed.

Method 1.3-4: When the Tx beam (or RS group) of PUCCH associated with LRR/SR is different from the Tx beam associated with another UCI type, the UE may not multiplex LRR/SR with other UCI types.

If LRR/SR is not multiplexed, LRR/SR may be considered to have a higher priority than other UCI types. In this case, the PUCCH corresponding to LRR/SR may be transmitted, but the PUCCH corresponding to other UCI types may not be transmitted.

1.3.2 Multiplexing of PUSCH and PUCCH

When PUCCH and PUSCH overlap in some symbol(s), UCI may be multiplexed with data in PUSCH. Alternatively, PUSCH and PUCCH may be transmitted simultaneously.

If the UCI is transmitted on the PUSCH, the performance degradation of the power amplifier can be avoided because peak to average power ratio (PAPR) and/or inter-modulation distortion (IMD) can be avoided. Even when the performance of the power amplifier is degraded, if reception performance (eg, block error rate (BLER)) of the PUSCH and the PUCCH is maintained, the UE can simultaneously transmit the PUSCH and the PUCCH. Whether or not the above operation is performed may be determined by the base station. The base station may determine whether simultaneous transmission of the PUSCH and the PUCCH can be performed by the corresponding terminal in consideration of the capability of the terminal. The base station may generate scheduling information based on the determination result and transmit the scheduling information to the terminal. Alternatively, the base station may transmit information indicating whether simultaneous transmission of the PUSCH and the PUCCH is performed to the terminal using RRC signaling.

In the UCI multiplexing procedure, spatial relationship information may not be considered for PUSCH scheduling. PUCCHs having different spatial relationship information may be multiplexed in PUSCH. If the UE is allowed to use a plurality of Tx panels or a plurality of Tx beams, the UE can simultaneously use one or more Tx beams for PUSCH transmission.

If the Tx beams for PUSCH and PUCCH are the same or similar, UCI (eg, UCI types) can be multiplexed on PUSCH. If Tx beams for PUSCH and PUCCH are different, UCI (eg, UCI types) may not be multiplexed in PUSCH. If UCI types are not multiplexed, the UE can simultaneously transmit two or more PUCCHs.

When the RS group considered for PUSCH transmission (hereinafter referred to as "PUSCH RS group") is the same as the RS group considered for PUCCH transmission (hereinafter referred to as "PUCCH RS group"), the UE Tx beams (or Tx panels) may be regarded as the same or similar.

Method 1.3-5: If the PUSCH RS group and the PUCCH RS group are the same, the UE can multiplex and transmit UCI and PUSCH associated with the same RS group. If the PUSCH RS group and the PUCCH RS group are different, the UE can simultaneously transmit PUSCH and PUCCH associated with different RS groups. UCI may be transmitted on PUCCH.

The UE may additionally perform a procedure for determining whether the RS groups are the same. Whether or not to perform a procedure for determining whether the RS groups are identical may be based on the capability of the UE. Therefore, the base station can transmit information indicating whether to perform a procedure for determining whether the RS groups are identical to the terminal.

Method 1.3-6: The base station may inform the terminal of information indicating the execution of a procedure for determining whether the PUSCH RS group and the PUCCH RS group are identical using RRC signaling. The UE may or may not perform a procedure for determining whether RS groups are identical based on information indicated by RRC signaling.

If a procedure for determining whether the PUSCH RS group and the PUCCH RS group are the same is performed in the UE, the UE may simultaneously transmit the PUSCH and the PUCCH. Accordingly, PDCCH MOs in which scheduling information is transmitted may have an arbitrary order.

When UCI is multiplexed on PUSCH, information sufficient to transmit PUSCH may be included in DCI allocating PUSCH. The DCI for allocating the PUCCH may be received by the UE at an earlier time than the DCI for allocating the PUSCH. Alternatively, the DCI for allocating the PUCCH may be received by the UE at the same time as the DCI for allocating the PUSCH. Specifically, the times of PDCCH MOs in which DCI is searched can be compared, and the above-described operation can be applied even when the priority (eg, priority index) of PUCCH and the priority of PUSCH are the same.

Method 1.3-7: Based on the PDCCH MO, "if a DCI allocating a PUCCH is received earlier than a DCI allocating a PUSCH" or "a DCI allocating a PUCCH is received at the same time as a DCI allocating a PUSCH"case", the UE may assume that UCI is transmitted on PUCCH. The UE may assume that PUSCH and PUCCH have different Tx beams (or different RS groups).

1.3.3 Multiplexing of PUSCHs

The UE may simultaneously transmit PUSCHs having different Tx beams (or different RS groups) according to capabilities. Two or more DCIs allocating the PUSCH may indicate the same priority (eg, priority index) to the UE. When PUSCHs having different Tx beams have different priorities, the UE can select a PUSCH having a higher priority from among the PUSCHs and transmit the selected PUSCH. Alternatively, the UE may multiplex data units having different priorities in one PUSCH according to RRC signaling.

Method 1.3-8: When PUSCHs having different priorities have different Tx beams, the UE can simultaneously transmit the PUSCHs.

It may be assumed that the UE does not receive scheduling information for two or more PUSCHs having the same priority and the same Tx beam. Circumstance(s) other than those described above may be permissible.

Method 1.3-9: When PUSCHs having different priorities have the same Tx beam, the UE performs "transmission operation of one PUSCH having a high priority" or "simultaneous transmission of all PUSCHs" according to RRC signaling and/or DCI action" can be performed.

For example, simultaneous transmission of PUSCHs may be allowed (eg, enabled) by RRC signaling, and the scheduling DCI may instruct the UE to perform simultaneous transmission or priority transmission. When a simultaneous transmission operation is indicated, the UE may simultaneously transmit PUSCHs. When a priority transmission operation is indicated, the UE may transmit one PUSCH having a high priority.

1.3.4 Multiplexing of configured grant (CG) PUSCHs

Two or more CG PUSCHs may be activated or configured in the UE, and two or more CG PUSCHs may overlap in the time domain. When the CG PUSCHs have the same priority, the UE can select a CG PUSCH having a lower CG index and transmit the selected CG PUSCH. When CG PUSCHs have different priorities, the UE can select a CG PUSCH having a higher priority and transmit the selected CG PUSCH.

If "CG PUSCHs having the same priority (eg, the same priority index) are transmitted in the same Tx beam and the CG PUSCHs overlap in the time domain", the UE can multiplex all data units in one CG PUSCH. and can transmit CG PUSCH multiplexed with data units.

Based on configuration information and/or activation DCI of CG PUSCH, frequency resources and/or time resources (eg, some time resources) of CG PUSCH may be determined. At least PRB allocation and start and length indicator value (SLIV) for CG PUSCH may be determined. The UE may derive the amount of resource elements (REs) allocated to it based on the PRB allocation and SLIV, and determine the size of the TB based on the derived information.

A base station may configure or instruct a terminal of two or more resources (eg, resources of two or more CG PUSCHs), and the terminal may multiplex all data units on two or more PUSCHs.

Method 1.3-10: In the transmission procedure of type 1 CG PUSCH, a resource list may be configured in the UE, and the UE is in the resource list for one CG PUSCH among CG PUSCHs having overlapping Tx beams and/or time resources. You can select resources from

The UE may select a CG PUSCH having the smallest index among CG PUSCHs. The selected CG PUSCH may have more than one resource. In this case, the UE can multiplex TBs to be transmitted on two or more CG PUSCHs on one CG PUSCH (eg, a selected CG PUSCH).

The resource list configured in the terminal may include CG resource 1 and CG resource 2. CG resource 1 and CG resource 2 may be defined in the same slot. The size of codeword 1 supported by CG resource 1 and the size of codeword 2 supported by CG resource 2 may be compared in consideration of the number of MCSs, REs, and/or layers.

9 is a conceptual diagram illustrating a first embodiment of a CG resource selection method for CG PUSCH.

Referring to FIG. 9 , CG resource 1 may be used when CG PUSCHs do not collide, and CG resource 1A may be used when CG PUSCHs collide. The size of CG resource 1A may be larger than that of CG resource 1. A resource list for CG PUSCH ID 1 may be configured, and the resource list may include CG resource 1 and CG resource 1A. For each of CG resource 1 and CG resource 1A, at least TBS (TB size), MCS, PRB allocation, start symbol, and number of symbols may be set. The size of TB transmittable in CG resource 1 may be TBS 1, and the size of TB transmittable in CG resource 1A may be TBS 1A.

CG PUSCH ID 2 may be configured in the UE. CG PUSCH ID 2 may be transmitted in the same time resource as CG PUSCH ID 1. Transmission of CG PUSCH ID 2 and CG PUSCH ID 1 may overlap in some symbols. In this case, the UE may transmit the data unit using the resource derived from CG resource 1A according to method 1.3-9.

Data units with TBS 1A can be multiplexed in CG resource 1B. Even when TB 2 corresponding to CG PUSCH ID 2 as well as TB 1 corresponding to CG PUSCH ID 1 are multiplexed, the size of “TB 1 + TB 2” may not be larger than TBS 1A.

Method 1.3-11: The same coding operation may be performed for TB 1 for CG PUSCH ID 1 and TB 2 for CG PUSCH ID 2, and one cyclic redundancy check (CRC) (eg, TB-level CRC ) can be given.

The same coding operation and the same modulation operation for multiplexed TBs can be performed. Alternatively, different encoding operations and the same modulation operation for multiplexed TBs may be performed. The reason is that TB 1 and TB 2 may have different BLERs, so it may be desirable to apply inefficiencies differently. In this case, the code rate set for CG PUSCH ID 1 can be applied to TB 1, and the code rate set for CG PUSCH ID 2 can be applied to TB 2. The terminal may generate one bit stream by interleaving the codebook(s) for TB 1 and the codebook(s) for TB 2.

Method 1.3-12: The UE may perform different encoding operations for each TB for the CG PUSCH ID and may assign a separate CRC (eg, TB-level CRC).

The result of rate matching may be different depending on the amount of resources corresponding to CG PUSCH ID 1A. For example, UCI may need to be piggybacked on CG PUSCH ID 1A. To multiplex UCI, TB 1, and TB 2, the UE may perform RE mapping operation based on priority.

For example, the number of REs may be derived according to the code rate of UCI. A rate matching operation for UCI may be performed first. TB 1 and TB 2 may be mapped to REs to which UCI is not mapped. The UE may derive the number of REs required for TB 1 for CG PUSCH ID 1 and perform a rate matching operation based on the number of REs. A rate matching operation for mapping TB 2 may be performed in REs to which UCI and TB 1 are not mapped.

Method 1.3-13: In Method 1.3-12, TBs and UCIs may have an order, and rate matching operations may be sequentially performed according to the order.

When the encoding operation is completed, a result of the encoding operation may be mapped to a modulation symbol. Coded bits belonging to different TBs may be mapped in the same modulation symbol. In the CG PUSCH transmission procedure, RE level puncturing may be performed. In this case, it may be desirable for only one TB to be affected by the puncturing operation.

Method 1.3-14: In method 1.3-12, coded bits for different TBs may be mapped to different REs. For this operation, many coded bits can be mapped. Alternatively, a separate known bit (eg, 0 or 1) may be prepended or appended to the code bit.

10 is a conceptual diagram illustrating a first embodiment of a method of mapping code bits.

Referring to FIG. 10, a terminal may append many code bits before performing a modulation operation. Alternatively, the terminal may append 0 or 1 to the codeword before performing the modulation operation. The terminal may generate an augmented codeword by concatenating codewords, and may perform a modulation operation on the augmented codeword.

Meanwhile, when CG PUSCH ID 1A is used to multiplex TB 1, TB 2, and/or UCI, the size of “TB 1 + TB 2” may be smaller than that of TBS 1A. In this case, it may be a waste of resources for the UE to transmit the PUSCH using all resources of CG PUSCH ID 1A.

To this end, the UE may derive the minimum number of PRBs capable of transmitting TB 1 + TB 2, and transmit the PUSCH in the derived PRB(s). The time resource of CG PUSCH ID 1A is reused, but the bandwidth can be reduced by using less PRBs. In this case, among PRBs allocated for CG PUSCH ID 1A, a PRB having a low index may be used. When DFT-s-OFDM is used for CG PUSCH transmission, the number of PRBs for CG PUSCH transmission may be a multiple of 2, 3, or 5.

Method 1.3-15: The UE may transmit the CG PUSCH using only the minimum number of PRBs capable of transmitting both TB 1 and TB 2.

To derive the number of PRBs, the UE can calculate the amount of resources required for each of TB 1 and TB 2 using TBS derived from the amount of scheduled resources and the code rate set by RRC signaling. Regarding code rate r _i of TB i and TBS s _i , considering the CRC length O _i of TB or code block group (CBG), s _i +O _i may be used as an information bit. i may be a natural number.

는 성립할 수 있다. 여기서, 서로 다른 변조율 Q_i가 TB i에 적용되면,

는 성립할 수 있다.When a code rate is applied, the length of a codeword can be approximately given as (s _i + O _i )/r _i . The number of REs required to transmit TBs can be represented by N symbols and M subcarriers. When the modulation factor is Q,

can be achieved. Here, when different modulation rates Q _i are applied to TB i,

can be achieved.

In order to derive the minimum number of PRBs, the minimum value of M may be derived, and the minimum value of M may be converted to the number of PRBs (M'=M/12). When DFT-s-OFDM is used in CG PUSCH transmission, M' may be the smallest natural number among values that are multiples of 2, 3, or 5. In order to express the operation result as a natural number, a rounding operation or a rounding operation may be performed in addition to the operation result.

In order to apply the above methods, the procedure for deriving the TBS in the terminal may be changed. In order to derive the TBS, the amount of resources (eg, the number of REs), the amount of overhead, and/or the code rate scheduled for the UE may be utilized.

In order to derive TBS 1 from CG resources of CG PUSCH ID 1, the number of REs allocated to CG PUSCH ID 1, the amount of overhead, and/or the code rate may be utilized. The size of TB in the CG resource of CG PUSCH ID 1A may be regarded as TBS 1. Therefore, the UE may consider that TBS 1 or "TBS 1 + TBS 2" is derived for CG PUSCH ID 1A, not TBS 1A. When TB 2 is multiplexed, the UE may consider that the TBS for CG PUSCH ID 1A is "TBS 1 + TBS 2".

Method 1.3-16: If there are two or more TBs that can be transmitted on the CG PUSCH, the size of the TBs (eg, TBS 1A) to be transmitted on each CG PUSCH overlapping the corresponding CG PUSCH in the time domain is different from the CG PUSCH It can be derived based on TBSs derived using the resources of .

Three or more CG PUSCHs may overlap each other, and a UE may transmit all TBs by multiplexing on one CG PUSCH among three or more CG PUSCHs. Even in this case, method 1.3-16 can be extended and applied. For example, in the transmission procedure of CG PUSCH ID 1, CG PUSCH ID 2, and CG PUSCH ID 3, TB 1, TB 2, and/or TB 3 may be multiplexed. When TB 1, TB 2, and/or TB 3 are multiplexed and transmitted in resources of CG PUSCH ID 1A, TBS may be given as "TBS 1 + TBS 2 + TBS 3". Thereafter, a common CRC or each CRC may be appended to the TBs, and the UE may perform a common encoding operation or each encoding operation on the TBs. A rate matching operation can be performed by applying the method 1.3-13 in the encoding operation.

A codeword may be derived from each TB, the codewords may be concatenated, and a modulation operation on the concatenated codewords may be performed. The concatenation order may be an order considered in the rate matching operation.

Meanwhile, priorities (eg, priority indexes) of CG PUSCHs may be set differently. Depending on the setting of the base station, the priority of the CG PUSCH may be indicated or set to the terminal by RRC signaling. The priority of CG PUSCH can be divided into two based on a value of 0 or 1. For example, the CG PUSCH may be divided into a low priority (LP) CG PUSCH and a high priority (HP) CG PUSCH.

To transmit CG PUSCH(s) in the same symbol, one CG PUSCH may be selected, and all or some TBs and/or UCIs may be multiplexed in one CG PUSCH. In this case, one CG PUSCH may be selected from CG PUSCHs having a high priority. When CG PUSCHs having the same priority overlap in the time domain, all or some TBs and/or UCIs may be multiplexed in the resource of the CG PUSCH having the lowest ID or the highest ID.

The UE may not always transmit TB in CG PUSCH. If the upper layer (eg, MAC layer) of the UE does not transfer TB to the physical layer, the CG PUSCH may not be transmitted. The UE may receive DCI and may transmit PUSCH when a UL grant is derived from the received DCI. In this case, if a resource temporally overlapping with CG PUSCH is dynamically indicated, CG PUSCH may not be transmitted.

When resources for CG PUSCH ID 1, CG PUSCH ID 2, and CG PUSCH ID 3 overlap each other, the UE can transmit only TBs corresponding to some CG PUSCHs. For example, CG PUSCH ID 2 may not be transmitted. In this case, since TB 1 and TB 3 are transmitted according to the selection of the terminal, the above-described transmission operation can be equally recognized by the terminal and the base station. The UE may transmit control information on the CG PUSCH, and the control information may include lists of CG PUSCH IDs mapped on the CG PUSCH.

In the unlicensed band, CG PUSCH including CG-UCI can be transmitted. When a resource region is determined to be in an idle state in a listen before talk (LBT) procedure performed by a terminal and a base station, a transmission operation may be performed in the corresponding resource region. Therefore, even when dynamically transmitting the UL grant and the PUSCH, the UE may not be able to perform actual transmission. The UE performs a retransmission operation (eg, transmission operation of some control information) as well as an initial transmission operation (eg, an initial transmission operation including transmission operation of some control information) for a specific HARQ process number (HPN) even in CG PUSCH. It is possible to notify the base station of performing a retransmission operation including). Since channel occupancy time (COT) secured by the terminal can be shared with the base station or other terminals, COT-related information can be included in control information. The aforementioned control information may be referred to as CG-UCI. In the licensed band, the UE may transmit CG PUSCH including CG-UCI. The above-described methods can be applied to both unlicensed and licensed bands.

When PUCCH and CG PUSCH overlap in the time domain, the same encoding operation for UCI and CG-UCI may be performed. Information bits of HARQ-ACK and information bits of CG-UCI may be concatenated, and one codeword may be derived by performing the same encoding operation on the concatenated information bits. Different encoding operations may be performed on CSI and CG-UCI, and CSI and CG-UCI may belong to different codewords.

If TB is not transferred from the MAC layer of the UE to the PHY layer, transmission of the CG PUSCH may be skipped. Since the base station cannot know whether transmission of the CG PUSCH is skipped, it can perform blind detection. If "CG PUSCH corresponding to one ID has a plurality of resources" or "CG PUSCH (s) corresponding to a plurality of IDs exist", the UE performs a CG transmission operation on temporally overlapping resources. PUSCH(s) can be selected.

For example, resources corresponding to CG PUSCH IDs 1, 2, and 3 may overlap in time, and TB(s) corresponding to CG PUSCH IDs 2 and 3 may be generated. The UE may multiplex and transmit TBs in the resource of CG PUSCH ID 1A. The base station may not know the combination of CG PUSCH IDs and/or resources on which TB(s) are transmitted. Since CG PUSCH ID 1A includes CG-UCI, CG-UCI may include information indicating multiplexing of TBs corresponding to CG PUSCH IDs 2 and 3.

Method 1.3-17: CG-UCI may indicate a TB pattern.

Method 1.3-18: In method 1.3-17, a specific field of CG-UCI may be interpreted as a bitmap, and the bitmap may indicate a pattern of CG PUSCH IDs associated with TBs, corresponding to each bit of the bitmap CG PUSCH may correspond to an order according to ascending or descending order of CG PUSCH IDs.

When CG PUSCH IDs 1, 2, and 3 temporally overlap in CG PUSCH ID 1A, the length of the bitmap may be given as 3. If TBs corresponding to CG PUSCH IDs 2 and 3 are transmitted, the bitmap may be given as 011. If other combinations occur, the bitmap can be interpreted regardless of the index of the resource on which the CG PUSCH is transmitted. Even if a transmission operation is performed in CG PUSCH ID 2A instead of CG PUSCH ID 1A, resources of CG PUSCH IDs 1, 2, and 3 may overlap in time. In this case, CG PUSCHs corresponding to each bit of the bitmap may be CG PUSCH ID 1, CG PUSCH ID 2, and CG PUSCH ID 3.

11 is a conceptual diagram illustrating a first embodiment of a mapping method in CG resources.

Referring to FIG. 11 , CG-UCI may be included in CG PUSCH ID 1 (eg, CG resource 1) and CG PUSCH ID 1A (eg, CG resource 1A). Since multiple TBs can be transmitted in CG PUSCH ID 1A, CG-UCI can be included in CG PUSCH ID 1A. For frequency multiplexing in the RE mapping procedure, CG-UCIs may be mapped to subcarriers according to preset intervals. When only one TB is transmitted on CG PUSCH ID 1, CG-UCI may not be mapped to CG PUSCH ID 1. In this case, CG-UCI may be mapped in CG PUSCH ID 1A. When the CG-UCI is mapped, the location of the RE to which the CG-UCI is mapped may be the same so that the base station can easily distinguish CG PUSCH ID 1 and CG PUSCH ID 1A.

When a plurality of TBs are transmitted in CG PUSCH ID 1A, a HARQ process number (HPN) of each of the plurality of TBs may be determined. When one TB is transmitted, the HPN for one TB may be derived from a time resource (eg, slot index) through which the CG PUSCH is transmitted. If the HPN offset (eg, harq-ProcID-Offset) is indicated to the UE by RRC signaling, the HPN may be derived using the time resource and the HPN offset through which the CG PUSCH is transmitted.

The HPN field included in CG-UCI can be reused. Since the retransmission operation of TB in the unlicensed band can be performed in CG PUSCH based on the determination of the terminal, the HPN field can be included in the CG-UCI. In licensed bands, the HPN field of CG-UCI can be used for other purposes. For example, in a licensed band, the HPN field may be used to express a pattern of TB. The most significant bits (MSBs) or least significant bits (LSBs) of the HPN field may be used to represent the pattern of TB.

The size of the HPN field included in CG-UCI may be limited to 4 bits. In this case, when there are 5 or more temporally overlapping resources in the CG PUSCH, up to 4 CG PUSCHs having a low ID or a high ID can be selected from among CG PUSCH IDs. Alternatively, among the fields included in the CG-UCI, other fields may be used together with the HPN field. For example, the NDI field and the HPN field may be concatenated, and the concatenated fields may be used as bits for expressing a transmission pattern of TB. In this case, up to 5 temporally overlapping resources may be allowed in the CG PUSCH.

HPN for CG PUSCH can be determined without CG-UCI. In this case, the following method may be applied.

Method 1.3-19: The derived HPN can be used as the HPN of the first TB multiplexed on the CG PUSCH transmitted by the UE, and the HPNs of other TBs can be consecutive values of HPNs according to the order of CG PUSCH IDs.

For two or more TBs transmitted on CG PUSCH ID 1A, the HPN of each TB may be determined based on the transmission order of each TB. For example, if CG PUSCH IDs 2 and 3 are transmitted, the HPN can be derived from the time and / or HPN offset at which CG PUSCH ID 1A is transmitted, and the derived HPN is the TB corresponding to CG PUSCH ID 2 can be used for And the HPN of the TB corresponding to CG PUSCH ID 3 may be the derived HPN + 1.

Repeated transmission may be configured in CG PUSCH. The base station may indicate the number of repeated transmissions to the terminal using RRC signaling. Alternatively, the number of repeated transmissions may be derived from an index indicating a time resource of the CG PUSCH. When the CG PUSCH is repeatedly transmitted, a redundancy version (RV) may be changed in transmission of each CG PUSCH. Repetition of PUSCH instances may constitute one PUSCH occasion. A unique RV may be derived for each PUSCH instance. When the repeated transmission operation is performed in units of slots according to the interval of PUSCH instances (eg, the interval of the first symbols of adjacent PUSCH instances), the repeated transmission operation may be referred to as type A. If "repeated transmission operation is continuously performed, and the last symbol of the previous PUSCH instance and the first symbol of the next PUSCH instance are adjacent", the corresponding repeated transmission operation may be referred to as type B.

When time resources corresponding to a plurality of CG PUSCH IDs overlap, repetitive transmission of some CG PUSCH(s) for some CG PUSCH ID(s) may be in progress, and some CG PUSCHs for some CG PUSCH ID(s) (s) may be transmitted first. When one CG PUSCH is repeatedly transmitted, collision between repeated transmission and another PUSCH may not be allowed. Alternatively, transmission of the CG PUSCH may be canceled due to transmission of the PUSCH scheduled by DCI. Alternatively, a CG PUSCH with a high priority may be transmitted instead of a CG PUSCH (eg, a CG PUSCH with a low priority). Alternatively, transmission of the CG PUSCH may be canceled due to transmission of a PUSCH scheduled for a DCI having a high priority.

Even if the repeatedly transmitted CG PUSCHs overlap in time, the UE can transmit multiple TBs on one CG PUSCH. When the code rate and/or size of each of the TBs is derived using the above-described methods, the RV of each of the TBs may be derived.

Method 1.3-20: The RV applied to each TB may be the RV for each CG PUSCH resource.

1.3.5 Concurrency support for SRS transmission

Regarding transmission of the SRS, if the PUSCH and/or the PUCCH partially or entirely overlap in time in the same serving cell, the UE may not transmit the SRS. In addition, when a plurality of SRS resources are configured and / or activated in the terminal, the base station may allocate a plurality of SRS resources so as not to overlap in time. If the UE can transmit two or more Tx beams (or two or more RS groups), the above methods or a modification of the above methods can be applied to SRS transmission. For example, in the SRS resource configuration procedure, the RS group may be additionally included in the SRS resource configuration.

In order to determine whether SRS resources can be configured simultaneously, whether Tx beams (or RS groups) are identical may be considered. When it is determined that different Tx beams (or different RS groups) are determined, the UE may transmit the SRS in SRS resources partially or entirely overlapping in time. In order to determine whether SRS and PUCCH (or PUSCH) can be simultaneously transmitted, whether Tx beams (or RS groups) are identical may be considered. When it is determined that different Tx beams (or different RS groups) are used, the UE can transmit SRS and PUCCH (or PUSCH) even when some or all of the SRS resources overlap in time.

When SRS transmission is triggered using DCI, the base station may instruct or configure a method of interpreting the trigger field for SRS transmission included in DCI to the terminal through RRC signaling. There may be one interpretation method of the trigger field for SRS transmission.

Method 1.3-21: The index indicated by the trigger field may mean that one or more SRS resources are transmitted or configured in the UE.

1.4 Simultaneous support of UL transmission considering priority index

1.4.1 Framework for transmission of PUCCH and PUSCH

Based on UL-DCI, DL-DCI, and/or RRC signaling, the UE may multiplex UCI 1, UCI 0, TB 1, and/or TB 0. Performing simultaneous transmission of PUCCHs without multiplexing may be indicated to the UE. "Information indicating whether UCI 1 and UCI 0 are multiplexed on one PUCCH" and/or "information indicating whether only UCI 1 is transmitted on PUCCH" may be indicated to the UE. The base station may use a combination of RRC signaling, UL-DCI, and/or DL-DCI to indicate the above information to the terminal.

In the embodiments below, a transmission method of one TB will be described. The following embodiments can be easily applied to a transmission method of two TBs (eg, TB 1 and TB 0). When UCI 1, UCI 0, and TB are considered, the base station may transmit DL-DCI including information indicating whether to multiplex UCI 1 and UCI 0 to the terminal. The base station may transmit UL-DCI including information indicating whether to multiplex UCI having a priority index different from that of the TB to the terminal. Alternatively, the base station may transmit UL-DCI including information indicating whether TB and UCI 1 are multiplexed to the terminal. In the former case, TB 1 and UCI 1 may be multiplexed, and the base station may indicate information indicating whether to multiplex UCI 0 to the terminal using UL-DCI and/or RRC signaling. TB 0 and UCI 0 may be multiplexed, and the base station may instruct the terminal with information indicating whether or not UCI 1 is multiplexed.

The UE may perform a procedure for determining an uplink channel (ULCH) resource (eg, PUCCH resource and/or PUSCH resource) before considering the Tx panel. The above procedure may be divided into two procedures (eg, procedure 1 and procedure 2). In procedure 1, the UE can derive one ULCH or two ULCHs for each priority index. The UE may check whether resources corresponding to UCI 1 and TB 1 (eg, PUCCH 1 and PUSCH 1) temporally overlap each other, and resources corresponding to each of UCI 0 and TB 0 (eg, PUCCH 1 and PUSCH 1) It can be confirmed whether PUCCH 0 and PUSCH 0) overlap each other in time. If PUCCH and PUSCH overlap in time, UCI can be multiplexed on PUSCH. Therefore, when the UE performs procedure 1, PUCCH 1, PUSCH 1, PUCCH 0, and PUSCH 0 that do not temporally overlap each other may be set or indicated. Only some of the above-described ULCHs may be determined according to scheduling transmitted to the UE.

In procedure 2, some ULCHs may be multiplexed and transmission of the remaining ULCHs may be dropped, considering the priority index and whether the ULCH(s) are multiplexed. When procedure 1 is performed, ULCHs having the same priority index may be considered. When procedure 2 is performed, ULCH multiplexing and/or drop may be indicated differently in each of DL-DCI and UL-DCI. For example, DL-DCI may instruct the UE to transmit UCI 1 and drop UCI 0, and UL-DCI may instruct the UE to multiplex UCI 1 and UCI 0. For another example, DL-DCI may instruct the UE to multiplex UCI 1 and UCI 0, and UL-DCI may instruct the UE to transmit UCI 1 and drop UCI 0.

Procedure 2 can be subdivided into procedure 2-1 and procedure 2-2. In procedure 2-1, PUCCH may be determined considering UCI 1 and UCI 0. In procedure 2-2, the PUSCH may be determined in consideration of the PUCCH (eg, the PUCCH determined in procedure 2-1), and the UE maps UCI (eg, all or part of UCI 1 and UCI 0) to the PUSCH. can do. Regardless of TB 1 and TB 0 in procedure 2-1, PUCCH may be determined based on UCI 1 and UCI 0. The DL-DCI finally received from the base station may indicate to the terminal that “UCI 1 and UCI 0 are multiplexed” or “UCI 1 or UCI 0 is transmitted”. If the UE does not transmit the PUSCH, the PUCCH may be determined based on procedure 2-1, and the UE may transmit the corresponding PUCCH.

UCI 1 and UCI 0 may correspond to PUCCH 1 and PUCCH 0 of the UE after performing procedure 1, respectively. The UE may already multiplex some UCIs on PUSCH 1 and PUSCH 0, and some multiplexed UCIs may not be considered in procedure 2-1. When multiplexing of UCI 1 and UCI 0 is performed in Procedure 2-1, PUCCH 1 corresponding to UCI 1 may be a reference. UCI 0 corresponding to PUCCH 0 overlapping PUCCH 1 may be multiplexed. When a subslot is configured for a resource set corresponding to PUCCH 1, a time resource of PUCCH 1 may belong to one subslot. That is, PUCCH 1 can be transmitted in one subslot. Since PUCCH 0 may follow a separate subslot configuration, PUCCH 0 may be transmitted in one or more subslots. In this case, PUCCH 0 may overlap two or more PUCCH 1s. PUCCH 0 may be considered to overlap in the earliest subslot or the latest subslot among the aforementioned subslots. The determined subslot may be used to determine overlap with PUCCH 1.

When multiplexing UCI 1 and UCI 0, a method of selecting different subslots according to the UCI type of UCI 1 may be considered. The reason is that whether to multiplex UCI 1 and UCI 0 may depend on the UCI type. For example, when UCI 0 overlaps several PUCCH 1s, PUCCH 1 and a subslot including HARQ-ACK (eg, HARQ-ACK 1) among UCI 1 may be considered. In this case, the UCI types of UCI 0 that can be multiplexed with HARQ-ACK 1 may be HARQ-ACK and SR/LRR. On the other hand, when the UCI type of UCI 1 is SR 1/LRR 1, HARQ-ACK 0 or SR0/LRR 0 of UCI 0 may not be multiplexed. When SR 1/LRR 1 is transmitted in PUCCH format 0/1, the payload of HARQ-ACK 0 may be large. Accordingly, PUCCH 1 having PUCCH formats 2/3/4 may be configured or instructed to the UE. Since the PUCCH multiplexed with UCI 1 and UCI 0 can be considered to have a high priority, and UCI 1 and UCI 0 are transmitted on PUCCH 1, it may be difficult to change the PUCCH format to PUCCH format 2/3/4. there is.

In order to apply the above-described methods, the terminal may separately perform a multiplexing procedure with UCI 0 according to the UCI type of UCI 1. However, in terms of implementation, it may be advantageous for the UE to perform a multiplexing procedure regardless of the UCI type. This is because it is simpler to multiplex or drop all of UCI 0 included in PUCCH 0 for PUCCH 0 overlapping PUCCH 1 under the condition that UCI 1 transmission is not dropped. Therefore, it may be desirable for one subslot to be selected regardless of the UCI type of UCI 1.

In order to determine a PUCCH multiplexed with UCI 1 and UCI 0, a method of considering PUCCH 0 overlapping with reference PUCCH 1 can be further subdivided. Considering all PUCCH 0 overlapping with the reference PUCCH 1, UCI 1 and all UCI 0 can be multiplexed. Alternatively, PUCCH 0 overlapping PUCCH 1 may be selected one by one, a multiplexing operation for UCI 1 and the selected UCI 0 may be performed, and the multiplexing operation may be repeated.

A difference may exist between "a case in which UCI 1 and all UCI 0s are multiplexed at once" and "a case in which UCI 1 and UCI 0 are sequentially multiplexed". For example, PUCCH 1 corresponding to UCI 1 may overlap PUCCH 0 corresponding to HARQ-ACK 0, and the aforementioned PUCCH 1 and PUCCH 0 corresponding to SR 0 may overlap. PUCCH 0 corresponding to HARQ-ACK 0 may be early in time, and PUCCH 0 corresponding to SR 0 may be late in time.

If it is considered that HARQ-ACK 0 and SR 0 are sequentially multiplexed on UCI 1, PUCCH 1 on which UCI 1 and HARQ-ACK 0 are multiplexed can be derived again. When the aforementioned PUCCH 1 and PUCCH 0 including SR 0 overlap again, PUCCH 1 multiplexing UCI 1 and SR 0 may be derived again. If PUCCH 0 including PUCCH 1 and SR 0 described above do not overlap each other, the UE may consider that all of UCI 1, HARQ-ACK 0, and SR 0 are transmitted, and may perform procedure 2-2. Depending on the multiplexing method, UCI 1 and SR 0 may not be multiplexed. In this case, transmission of SR 0 may be dropped, and UCI 1 and HARQ-ACK 0 may be multiplexed on PUCCH 1.

If it is considered that HARQ-ACK 0 and SR 0 are multiplexed on UCI 1 at once, UCI 1, HARQ-ACK 0, and SR 0 may be included in PUCCH 1. Alternatively, SR 0 transmission may be dropped, and PUCCH 1 including UCI 1 and HARQ-ACK 0 may be derived. After procedure 1 is performed, SR and CSI may be processed differently in UC I. For example, when HARQ-ACK 0 and SR 0 are multiplexed on PUCCH 0 after Procedure 1 is performed, "HARQ-ACK 0 and SR 0" and "UCI 1 multiplexed with HARQ-ACK 1 and SR 1" Multiplexing can be considered. In this case, HARQ-ACK 0 of UCI 0 may be selected for multiplexing with UCI 1, and transmission of SR 0 of UCI 0 may be dropped. The dropped SR 0 may be assumed to be a negative SR.

In the SR transmission procedure, the MAC layer of the UE may deliver a positive SR or negative SR to the PHY layer of the UE. Considering the processing time required in the multiplexing procedure of UCI 1 and UCI 0, all PUSCHs and all PUCCHs scheduled for the UE may be instructed to have sufficient processing time. Channels and/or signals indicated to the UE may include SPS PDSCH, CG PUSCH, periodic PUCCH, semi-persistent PUCCH, and/or SR.

Sufficient processing time may be derived from technical specifications according to the capability of the terminal. For example, the terminal may perform procedures 1 and 2 by applying a Rel-15 timeline. Therefore, the UE can already know the existence and/or time resource of all PUSCHs and all PUCCHs before performing procedures 1 and 2.

In the SR transmission procedure, since the MAC layer of the UE delivers SR 1 and SR 0 to the PHY layer of the UE sufficiently early, it can be assumed that there are no unnecessary positive SRs. For example, the case where positive SR 1 is delivered after positive SR 0 can be excluded.

If the positive SR is not delivered, if the SR is configured to be transmitted in PUCCH format 0/1, procedures 1 and 2 can be simplified because PUCCH is not transmitted in the PHY layer. When SR is multiplexed with CSI and/or HARQ-ACK, the SR can be transmitted in PUCCH formats 2/3/4 as well as PUCCH formats 0/1. If "two or more SRs overlap in time and are multiplexed with CSI and/or HARQ-ACK", bit(s) in PUCCH formats 2/3/4 may represent an index where a positive SR occurred. If all SRs are positive SRs, the aforementioned bit(s) may be set to 0. Dropping of SR transmission in consideration of multiplexing with UCI 1 may mean dropping of the aforementioned bit(s).

Unlike SR, periodic CSI/quasi-persistent CSI may occur periodically in the PHY layer of the UE and may be classified as UCI 0. According to procedure 1, CSI can be multiplexed on PUCCH 0, and according to procedure 2, CSI can be multiplexed on UCI 1 and PUCCH 1. Alternatively, according to procedure 2, CSI transmission may be dropped on PUCCH 1. In procedure 2, the UE may drop transmission of some UCI types. Therefore, it may be preferable that the UCI in PUCCH 0 obtained by performing procedure 1 be divided into UCI types rather than UCI indexes (eg, UCI 0, UCI). Since all UCI types are transmitted in UCI 1, UCI types may not be distinguished.

When the UE performs Procedure 2-1 and/or Procedure 2-2, the UCI type may not be distinguished for UCI 1, and the UCI type may be distinguished for UCI 0. Procedure 2-1 may be performed according to the format of PUCCH 1 for UCI 1. The case of PUCCH formats 0 and 1 and the cases of PUCCH formats 2, 3, and 4 may be distinguished during the execution of procedure 2-1. Since all or part of UCI 1 and UCI 0 are multiplexed in PUCCH 1, when the format of PUCCH 1 is PUCCH format 0 and/or 1, the sum of the size of UCI 1 and the size of UCI 0 may not exceed 2 bits. The size of UCI 1 may be 1 bit, the size of UCI 0 may be 1 bit, and UCI 1 and UCI 0 may be multiplexed on PUCCH 1. When the amount of UCI 0 is large, the sum of the size of UCI 1 and the size of UCI 0 may exceed a boundary value supported by the PUCCH 1 format. Alternatively, when the format of PUCCH 0 is PUCCH format 2, 3, and/or 4, all of UCI 0 may be dropped. In this case, the UCI type of UCI 0 may be HARQ-ACK, SR, and/or CSI. In this case, Procedures 2-1 and/or 2-2 may be performed without considering the UCI types of UCI 1 and UCI 0.

When the format of PUCCH 1 is PUCCH format 2, 3, and/or 4, positive SR or negative SR in UCI 1 may be expressed as a value of bit(s). In this case, whether to multiplex UCI 1 and UCI 0 may be determined according to values of some UCI types of UCI 1. Transmission of UCI 0 may be dropped. Alternatively, UCI 0 may be multiplexed with UCI 1. It may be undesirable for a procedure performed by a UE to be determined based on a value of a payload. Accordingly, all of UCI 0 may be dropped according to the format of PUCCH 1 in which UCI 1 and UCI 0 are multiplexed.

In procedure 2-2, PUCCH 0 to which only UCI 0 is mapped, PUCCH 1 to which only UCI 1 is mapped, PUCCH 1 to which both UCI 0 and UCI 1 are mapped, PUSCH 1 to which only TB 1 is mapped, PUSCH 0 to which only TB 0 is mapped, UCI PUSCH 0 to which both 0 and TB 0 are mapped, and/or PUSCH 1 to which both UCI 1 and TB 1 are mapped may be considered. Since multiplexing of SR and TB is not supported, a case in which UCI types are distinguished may occur. When a positive SR 1 occurs in the UE, the UE can drop PUSCH 0 because it cannot multiplex SR 1 on PUSCH 0. When a positive SR 0 occurs in the UE, the UE can drop SR 0 because it cannot multiplex SR 0 on PUSCH 1. In this case, even when two or more UCI types (eg, SR and HARQ-ACK) are included in UCI 1, since SR is included in UCI 1, PUSCH 0 transmission can be dropped and PUCCH 1 can be transmitted. can

"If the negative SR generated by the UE is included in UCI 1 (for example, if UCI 1 includes two or more UCI types)", the UE may drop PUSCH 0 overlapping with PUCCH 1 and transmit PUCCH 1. can When UCI 1 includes only SR, the negative SR may not be delivered to the PHY layer of the UE. Therefore, the negative SR in procedure 1 and/or procedure 2 may not be considered in the multiplexing procedure with UCI 1, UCI 0, and/or TB 0. In procedure 2-2, the PUSCH may be determined considering "UCI 1 and UCI 0" as well as "TB 1 and TB 0". Here, the last received UL-DCI informs the UE that "UCI 1 and UCI 0 are multiplexed with TB", "UCI 1 is multiplexed with TB", or "UCI 0 is multiplexed with TB". can instruct

Method 1.4-1: When the UE transmits only the PUCCH, the UE transmits “PUCCH resource” and “all or part of the UCI based on the most recently received DL-DCI (eg, HP DL-DCI) "can be determined.

Method 1.4-2: When the UE transmits the PUSCH, the UE transmits "PUSCH resources" and "all or part of the UCI based on the most recently received UL-DCI (eg, HP UL-DCI) "can be determined.

When procedure 2-1 is performed, some or all of the UCI may be dropped. In UCI 1, HARQ-ACK and SR may be considered, and in UCI 2, HARQ-ACK, SR, and/or CSI may be considered. In this case, at least CSI transmission may be dropped in procedure 2-1. This is because the number of encoding chains that can be simultaneously executed by the terminal is limited. For example, the number of encoding chains that can be executed simultaneously may be two or three.

Method 1.4-3: Procedure 2-2 may be performed for UCIs determined to be transmitted in procedure 2-1. In this case, the UCI dropped in Procedure 1 and/or Procedure 2-1 may not be considered in Procedure 2-2.

When the UE applies method 1.4-3 and CSI is dropped, the UE may not map CSI on the PUSCH. CSI may be CSI transmitted on PUCCH (eg, periodic CSI or quasi-persistent CSI). When Procedure 1, Procedure 2-1, and/or Procedure 2-2 are performed, the UE may not store the dropped UCI. In this case, the terminal can utilize a small-sized storage device. If some UCIs are dropped, system performance may not be improved. In order to prevent this problem, even when UCI is dropped, whether or not to multiplex UCI may be determined again in a subsequent procedure.

Method 1.4-4: Procedure 2-2 may be performed for all UCIs considered in Procedure 1. In this case, the UCI dropped in Procedure 1 and/or Procedure 2-1 may be considered again in Procedure 2-2.

When the UE applies method 1.4-4, if CSI is dropped, the UE may map CSI on PUSCH. CSI may be CSI transmitted on PUCCH (eg, periodic CSI or quasi-persistent CSI). Since UCI that can be multiplexed on PUSCH in procedure 2-2 is considered, UCI other than UCI included in PUCCH obtained in procedure 2-1 can also be considered.

For example, since aperiodic CSI or quasi-persistent CSI can be transmitted on PUSCH, multiplexing of UCI and TB in procedure 1 can be considered. Since only UCI included in PUCCH is considered in procedure 2-1, aperiodic CSI or quasi-persistent CSI may not be considered in procedure 2. Since multiplexing of UCI and TB included in PUSCH is considered in procedure 2-2, when method 1.4-4 is applied, aperiodic CSI or quasi-persistent CSI can be multiplexed with TB. When method 1.4-3 is applied, since aperiodic CSI or quasi-persistent CSI is excluded from procedure 2-1, aperiodic CSI or quasi-persistent CSI may not be multiplexed with TB.

On the other hand, considering the case where PUCCH and PUSCH can be simultaneously transmitted in different serving cells, when only procedure 1 is applied, PUSCH (eg, PUSCH with UCI) can be derived for each priority index. In this case, the UE may not perform procedure 2 and may transmit PUSCH (eg, PUSCH with UCI) in different serving cells.

Method 1.4-5: The UE may perform procedure 1, one PUSCH may be derived for each priority index, and the PUSCHs may be scheduled in different serving cells. In this case, the UE may simultaneously transmit the PUSCH without performing procedure 2.

Procedure 1 may be performed for PUCCH and PUSCH scheduled in different serving cells, and PUCCH and PUSCH may be simultaneously transmitted according to the result of procedure 2. Each of the serving cells may belong to different frequency bands.

When PUSCHs are scheduled for a UE in a plurality of serving cells, one PUSCH that can be multiplexed with a PUCCH may be selected from among the corresponding PUSCHs. When the UE selects one PUSCH, the UE may multiplex UCI on the selected PUSCH and may not multiplex UCI on another PUSCH. If the UE cannot select the PUSCH, the UE may simultaneously transmit the PUSCH and the PUCCH.

For example, UCI may be multiplexed in a PUSCH transmitted in a serving cell having the lowest index among serving cells in which the PUSCH is scheduled. For another example, the multiplexing procedure for UCI may be performed only in a serving cell in which simultaneous transmission of PUCCH and PUSCH is not permitted (eg, a serving cell belonging to the same frequency band). When procedure 2-2 is performed, PUCCH and PUSCH may be simultaneously transmitted in some serving cells, but PUCCH and PUSCH may not be simultaneously transmitted in other serving cells. A multiplexing operation of UCI in another serving cell may be considered.

In this case, whether to multiplex PUCCH and PUSCH in the same frequency band can be determined. Based on the determination result, the UE can multiplex the UCI on the PUSCH. Alternatively, the PUSCH transmission may be dropped. The dropped PUSCH may be simultaneously transmitted with a PUSCH scheduled in another frequency band.

Method 1.4-6: When simultaneous transmission of PUSCH and PUCCH is indicated, UCI on PUSCH of serving cell (s) on which PUSCH and PUCCH cannot be simultaneously transmitted among a plurality of PUSCHs on which UCI can be multiplexed in procedure 2-2 Multiplexing of can be determined.

Repeated transmission for UCI 1 or UCI 0 may be indicated. The number of repeated transmissions for the format of the PUCCH through which UCI is transmitted may be indicated. Alternatively, the number of repeated transmissions for PUCCH resources may be indicated. A multiplexing procedure for a UCI in which the number of repeated transmissions is indicated and a multiplexing procedure for a UCI in which the number of repeated transmissions is not indicated may be distinguished.

When UCI and/or TB for one priority index are scheduled for the UE, the UE may assume that PUCCH corresponding to one UCI type is repeatedly transmitted. Different UCI types can be interpreted as having different priorities. Repeated transmission for a UCI type with a high priority may be performed, and repeated transmission for a UCI type with a low priority may be dropped. HARQ-ACK may have the highest priority, positive SR may have a lower priority than HARQ-ACK, and CSI may have a lower priority than positive SR.

In procedure 2-1 in which UCI 1 and UCI 0 are multiplexed, repeated transmission of UCI 1 or UCI 0 may be performed. In this case, both the priority and the priority of the UCI type may be considered. When UCI 1 is repeatedly transmitted, the subslot considered in procedure 2-1 may be the second subslot in which UCI 1 is transmitted or a subslot subsequent to the second subslot. In this case, PUCCH 1 including UCI 1 may not additionally include other UCI (eg, UCI 1 or UCI 0). Therefore, when PUCCH 0 and PUCCH 1 overlap, only PUCCH 1 can be transmitted.

If UCI 1 is not repeatedly transmitted, the second transmission among repeated transmissions of UCI 0 may overlap the subslot considered in procedure 2-1. In this case, PUCCH 0 including UCI 0 may not additionally include other UCI (eg, UCI 1 or UCI 0). Therefore, when PUCCH 0 and PUCCH 1 overlap, the UE can transmit only PUCCH 1.

The multiplexing procedure in the first transmission of repeated transmissions of UCI may have a difference from the proposed method. In procedure 2-1, UCI 1 and UCI 0 may be multiplexed, and if the number of repeated transmissions associated with PUCCH 1 obtained by procedure 2-1 is greater than 1, it may be the first transmission. This is because an additional multiplexing procedure cannot be performed for UCI that has already been repeatedly transmitted. When an additional multiplexing procedure is performed, the base station cannot perform a soft combining operation because the code rate applied to UCI is changed.

In procedure 2-1, a procedure for determining multiplexing/selection with only untransmitted UCIs may be performed, and one PUCCH 1 may be determined. If procedure 2-1 is performed with only untransmitted UCIs, the UE may perform a multiplexing procedure for UCI 1 and UCI 0, multiplex two or more UCI types for UCI 1, and multiplex two or more UCI types for UCI 0. UCI types can be multiplexed. PUCCH 1 may be transmitted according to the number of repetitions associated with the resource of PUCCH 1 or the number of repetitions associated with the format of PUCCH 1.

Thereafter, a procedure for determining overlap with UCI (eg, PUCCH) being repeatedly transmitted may be performed. The high priority of the repeatedly transmitted UCI may mean "high priority (eg, priority index) of the UCI" or "high priority of the UCI type having the same priority index". . If "the UCI priorities are the same and the UCI types have the same priorities", it may be determined that the PUCCH transmitted in an earlier slot or an earlier symbol in the same slot has a higher priority. Thereafter, the UE may perform a multiplexing procedure with the PUSCH by performing procedure 2-2 using the determined PUCCH 1.

Meanwhile, if the number of encoding chains used in one ULCH or the number of codewords mapped in a ULCH exceeds a predetermined number (eg, n), the UE may drop some UCI transmissions. there is. For example, the value of n may be 3 or 2.

Method 1.4-7: The UE may drop part of a codeword when the number of encoding chains used in one ULCH exceeds the boundary value.

"When one priority index is considered and the UE transmits UCI and TB in one ULCH", HARQ-ACK, CSI part1, and / or SR form one coding chain (or one codeword) CSI part2 can configure another encoding chain (or another codeword), and TB can configure another encoding chain (or another codeword). Considering two priority indices, a larger number of coded chains may be required because the number of codewords increases for each priority index. When HARQ-ACK 1 and HARQ-ACK 0 are multiplexed on PUCCH, CSI may be dropped. CSI may be CSI part1 and/or CSI part2.

When either one of HARQ-ACK 1 and HARQ-ACK 0 is multiplexed on PUCCH, CSI (eg, periodic CSI or semi-persistent CSI) may not be dropped. In addition, when the UE transmits the PUSCH, not only HARQ-ACK 1, "HARQ-ACK 0 and periodic CSI" or quasi-persistent CSI, but also "aperiodic CSI and quasi-persistent CSI" may be additionally considered in the multiplexing procedure. there is. In this case, the UE may drop periodic CSI or quasi-persistent CSI, and multiplex "aperiodic CSI and quasi-persistent CSI" with HARQ-ACK 1 or HARQ-ACK 0 in the PUSCH.

When HARQ-ACK 1, HARQ-ACK 0, aperiodic CSI, and/or quasi-persistent CSI are multiplexed, UCIs having the same priority index can be generated as one codeword. The priority index of aperiodic CSI may be indicated by UL-DCI, and the priority index of semi-persistent CSI may be indicated by UL-DCI or RRC signaling. When CSI is divided into CSI part1 and CSI part2, HARQ-ACK and CSI part1 may be generated with one codeword, and CSI part2 may be generated with another codeword. Alternatively, HARQ-ACK and CSI may be generated with different codewords.

UL-DCI may indicate to the UE that TB is not transmitted. In this case, both HARQ-ACK 1 and HARQ-ACK 0 may be multiplexed together with aperiodic CSI or quasi-persistent CSI. The reason is that the UE can allocate the coding chain allocated to the TB to the CSI in the case of following the method 1.4-7. "CSI and HARQ-ACK" or "CSI, HARQ-ACK and TB" can be multiplexed on PUSCH. In this case, the code rate applied in the case of periodic CSI and quasi-persistent CSI and the code rate applied in the case of aperiodic CSI and quasi-persistent CSI may be indicated to the terminal in different ways.

After performing procedure 2-1, a procedure for simultaneous transmission of PUSCH and PUCCH will be described. In order to support simultaneous transmission of PUSCH and PUCCH, simultaneous transmission of PUSCH and PUCCH may be configured in a UE by RRC signaling. PUSCH and PUCCH may correspond to different priority indices, PUSCH and PUCCH may be transmitted in different serving cells, and the UE may perform frequency aggregation (inter-band CA (carrier aggregation)) can be assumed to be supported. After the end of procedure 1, the UE prioritizes the priority of PUCCH 1 (eg, high priority (HP)), the priority of PUSCH 0 (eg, low priority (LP)), and the priority of TB (eg, For example, HP or LP) can be compared. The UE can generate one ULCH by selecting or dropping some of PUCCH 1, PUSCH 0, and TB.

When procedure 2-1 is finished, the UE can multiplex UCI 1 and UCI 0 on HP PUCCH 1 and transmit HP PUCCH 1. Subsequently, the UE may perform procedure 2-2, which is a multiplexing procedure for the PUSCH corresponding to the TB. Simultaneous transmission of PUSCH and PUCCH may be configured in the UE by RRC signaling. In this case, the UE may perform a multiplexing procedure or a simultaneous transmission procedure for PUSCH and PUCCH 1 according to the priority of the PUSCH corresponding to the TB (eg, LP PUSCH 0 or HP PUSCH 1).

When PUSCH is PUSCH 0, simultaneous transmission on PUSCH 0 and PUCCH 1 may be allowed. When PUSCH is PUSCH 1, simultaneous transmission on PUSCH 1 and PUCCH 1 may not be allowed. In this case, a multiplexing procedure for PUSCH 1 and PUCCH 1 may be performed. If the above conditions for simultaneous transmission are not satisfied, PUCCH can be multiplexed on PUSCH, and PUSCH can be transmitted.

Method 1.4-8: A simultaneous transmission procedure for PUCCH 1 and PUSCH 0 in which HP UCI and LP UCI are multiplexed may be performed, and a multiplexing procedure for PUCCH 1 and PUSCH 1 in which HP UCI and LP UCI are multiplexed may be performed there is.

A method of dropping a part of a codeword when the number of coded chains exceeds the boundary value will be described. Aperiodic CSI reporting can be divided into CSI part1 and CSI part2. If the number of coding chains is insufficient, CSI part2 may be dropped. The UE may allocate an encoding chain to each UCI type according to a predetermined order for UCI to be multiplexed, and may drop a UCI type to which an encoding chain is not allocated. HARQ-ACK 1, HARQ-ACK 0, aperiodic CSI part1, and/or aperiodic CSI part2 may be considered. The DCI may indicate to the UE that the aperiodic CSI report has HP. If three encoding chains are available, any one of the three encoding chains may be dropped.

Method 1.4-9: The UE may compare priorities of HP UCI and LP UCI, and may use the number of coding chains as a criterion for selecting/dropping HP UCI and LP UCI.

In one example, the UE may drop aperiodic CSI part2 and multiplex HARQ-ACK 1, HARQ-ACK 0, and aperiodic CSI part1 on PUCCH. In the case of dropping the aperiodic CSI part2, since the base station cannot know the entirety of the CSI report, it may not be meaningful for the terminal to transmit the CSI report. In the proposed method, HARQ-ACK and CSI part1 having the same priority can be coded jointly. An operation of jointly encoding HARQ-ACK and CSI part1 having different priorities may not be supported.

Method 1.4-10: HARQ-ACK 0 may be dropped, and HARQ-ACK 1, aperiodic CSI part1, and aperiodic CSI part2 may be multiplexed on PUCCH. Subsequently, a multiplexing procedure of PUCCH and PUSCH may be performed.

When method 1.4-10 is applied in the PUCCH transmission procedure, HARQ-ACK 1 can be coded according to the HARQ-ACK coding operation specified in Rel-15, and aperiodic CSI part1 is CSI part1 specified in Rel-15. It can be encoded according to the encoding operation of CSI part2, and the aperiodic CSI part2 can be encoded according to the encoding operation of CSI part2 specified in Rel-15. Here, the encoding operation may mean a rate matching procedure, a puncturing procedure, and/or an RE mapping procedure.

The transmission of HARQ-ACK 0 canceled by the terminal may be retransmitted later according to the instructions of the base station. The corresponding HARQ-ACK 0 may be reported to the base station through a TB retransmission procedure, a HARQ codebook retransmission procedure, or a specific HARQ codebook transmission procedure. TB can be scheduled. Alternatively, TB may not be scheduled. Methods 1.4-9 and 1.4-10 can be applied before performing procedure 2-2. A UE that has performed both procedures 2-1 and 2-2 may perform a PUSCH transmission operation, a PUCCH transmission operation, or a simultaneous PUSCH and PUCCH transmission operation. Receiving ULCI (eg, DCI format 2_4) may be configured in the terminal.

An uplink cancellation indicator (ULCI) may not cancel PUCCH and all ULCHs related to initial access. ULCI can cancel PUSCH 0 or PUSCH 1. Even when PUSCH 0 includes UCI, corresponding PUSCH 0 may be canceled by ULCI. In UCI, only LP UCI can be multiplexed. In the proposed method, UCI 1 and/or UCI 0 can be multiplexed even on PUSCH 0. When the resource region indicated by the ULCI overlaps with the resource region of PUSCH 0, the UE may cancel part or all of PUSCH 0. PUSCH 0 including UCI 1 may also be canceled by ULCI. In the proposed method, when PUSCH 0 includes UCI 1, PUSCH 0 including UCI 1 can be regarded as PUSCH 1. The UE may not cancel PUSCH 0 even when ULCI is received.

Method 1.4-11: When ULCI is received from the base station, the UE may not cancel PUSCH 0 including UCI 1.

1.4.2 Another embodiment of multiplexing of PUCCHs

A priority index for PUCCH or PUSCH transmitted by the UE may be indicated. The scheduling DCI may indicate a priority index to the UE. Alternatively, RRC signaling may set a priority index to the UE. For example, when URLLC traffic is supported, the priority index may be indicated or set to 1. When eMBB traffic is supported, the priority index may be indicated or set to 0. The aforementioned simultaneous transmission may be interpreted as having the same priority index in consideration of the RS group (or Tx panel). When priority indexes are explicitly different, simultaneous transmission conditions may be different.

RRC signaling and / or DCI may indicate or configure simultaneous transmission of PUCCH and PUSCH to the UE. If the UE can simultaneously transmit PUCCH and PUSCH, PUCCH and PUSCH can be transmitted in different serving cells. If the UE has only one active serving cell, PUCCH and PUSCH may be multiplexed. UCI can be multiplexed on PUSCH. If the UE can simultaneously transmit two ULCHs (eg, PUCCH and PUSCH), the UE can simultaneously transmit PUCCHs. Whether or not to perform the above-described operation may be determined based on the capabilities of the UE. The base station may set simultaneous transmission operation to the terminal using separate RRC signaling.

Method 1.4-12: The UE may perform simultaneous transmission of PUCCHs.

Each of the PUCCHs may be transmitted in different serving cells. Alternatively, PUCCHs may be transmitted in the same serving cell. The serving cell may be a PCell (eg, SpCell, PSCell, PUCCH-SCell) or a PUCCH serving cell. When PUCCHs are transmitted in different serving cells, the corresponding PUCCHs may be transmitted in the same Tx panel or different Tx panels.

Method 1.4-13: In Method 1.4-12, simultaneous transmission of PUCCHs corresponding to different priority indices may be performed.

The HP DCI and/or the LP DCI may instruct the terminal with information indicating whether to perform a multiplexing operation with UCIs having different priority indices. For example, "when PDSCH is allocated by HP DCI (or LP DCI) and HARQ-ACK 1 (or HARQ-ACK 0) is transmitted", multiplexing operation with UCI 0 (or UCI 1) can be indicated.

It may be preferable that a PUCCH resource in which UCI 1 and UCI 0 are multiplexed has a high priority. Accordingly, multiplexing-related information may be preferably derived from information (eg, DCI) allocating UCI 1. Since the DCI format that the LP DCI can have and the DCI format that the HP DCI can have are not distinguished, the LP DCI can also instruct the UE to multiplex operation of UCI 1 and UCI 0. In this case, the UE may interpret that UCI 1 and UCI 0 are multiplexed in the PUCCH indicated in the last received HP DCI.

DCI (or RRC signaling) allocating UCI 1 may indicate to the UE that a multiplexing operation with UCI 0 is not performed. Each of the PUCCHs may include only UCI 1. Alternatively, each of the PUCCHs may include only UCI 0. A serving cell through which PUCCH is transmitted may be explicitly indicated by RRC signaling or DCI. For example, if it is assumed that two serving cells are activated, the UE may select a PUCCH serving cell indicated in DCI. Each of the PUCCHs may be determined after a multiplexing procedure for PUCCH resources having the same priority index is performed. PUCCH 1 may correspond to priority index 1 and may be transmitted in a serving cell associated with priority index 1. PUCCH 0 may correspond to priority index 0 and may be transmitted in a serving cell associated with priority index 0. The PUCCH 1 resource may be determined by the second PUCCH-config (or the second PUCCH resource set), and the PUCCH 0 resource may be determined by the first PUCCH-config (or the first PUCCH resource set).

12 is a flowchart illustrating a first embodiment of a PUCCH transmission method when UCI 1 and UCI 0 occur.

Referring to FIG. 12 , when a simultaneous transmission operation for PUCCHs is supported, the UE may generate HP UCI(s) and LP UCI(s) (S1201). If multiplexing of HP UCI(s) and LP UCI(s) is possible, the UE may multiplex HP UCI(s) and LP UCI(s) on HP PUCCH and transmit the HP PUCCH (S1202). If multiplexing of HP UCI(s) and LP UCI(s) is impossible, the UE may determine whether the serving cell of the HP PUCCH and the serving cell of the LP PUCCH are the same. When the serving cell of the HP PUCCH and the serving cell of the LP PUCCH are the same, the UE may transmit the HP PUCCH having the HP UCI (S1203). When the serving cell of the HP PUCCH and the serving cell of the LP PUCCH are different, the UE can determine whether the transmit power is sufficient. If the transmit power is sufficient, the UE may transmit HP PUCCH having HP UCI (S1203). If the transmission power is not sufficient, the terminal may transmit an LP PUCCH having an LP UCI and an HP PUCCH having an HP UCI (S1204).

Meanwhile, the UE may transmit at least PUCCH 1. PUCCH 1 may include only UCI 1. Alternatively, PUCCH 1 may include both UCI 1 and UCI 0. If the UE is instructed that UCI 1 and UCI 0 are not multiplexed, the UE can transmit UCI 1 on PUCCH 1 and determine whether UCI 0 can be transmitted on PUCCH 0. If the UE has sufficient transmit power, PUCCH 1 can be transmitted in a serving cell having index 1 (eg, priority index 1), and PUCCH 0 has index 0 (eg, priority index 0). It can be transmitted in the serving cell.

Thereafter, the UE may perform a simultaneous transmission procedure considering the Tx panel (or RS group) to transmit PUCCH 1 and/or PUCCH 0. Here, independent preprocessing operations may be applied to each of PUCCH 0 and PUCCH 1. Each of PUCCH 0 and PUCCH 1 may have an independent beam. When a UE simultaneously transmits two PUCCHs, the same antenna port 2000 may be applied to PUCCH 0 and PUCCH 1. A preprocessing operation or beam applied by the terminal may be set by RRC signaling (eg, PUCCH-SpatialRelationInfo). The UE may apply a value set by RRC signaling to each serving cell. PUCCHs simultaneously transmitted by the UE may be transmitted in the same Tx panel or different Tx panels.

Method 1.4-14: When two or more priority indices are considered, simultaneous transmission of PUCCHs in consideration of the priority index may be considered first, and then simultaneous transmission of PUCCHs in consideration of the Tx panel may be considered.

1.4.3 Another embodiment of multiplexing of PUSCH and PUCCH

In order to support traffic for two or more priority indices to the UE, a multiplexing procedure may be supported not only on the PUCCH but also on the PUSCH. A UCI corresponding to priority index 1 may be represented as UCI 1, and a UCI corresponding to priority index 0 may be represented as UCI 0. UL-SCH (or TB) may also have a priority index expressed as TB 1 and TB 0. The base station may transmit information indicating whether UCI 1 and UCI 0 are multiplexed to the terminal using RRC signaling and/or DCI. In addition, the base station may transmit information indicating whether the PUCCH and the PUSCH are multiplexed to the terminal using RRC signaling and / or DCI. The terminal may receive the above-described information from the base station.

Method 1.4-15: A PUCCH through which UCI 1 and UCI 0 are transmitted may be determined, and a PUSCH through which TB 1 and TB 0 are transmitted may be determined.

The UE may perform procedures for PUCCH and PUSCH, respectively. Here, PUCCH 1 (or PUCCH 1 and PUCCH 0) may be determined, and PUSCH 1 (or PUSCH 1 and PUSCH 0) may be determined. The MAC layer of the UE can deliver only one TB to the PHY layer of the UE. Even if the MAC layer of the UE transfers two TBs to the PHY layer of the UE, only TB 1 can be transmitted according to the procedure in the PHY layer. The method considering one TB can be easily extended and applied. In Table 1 below, the operation of the UE (eg, multiplexing operation of ULCHs) can be classified into four cases.

In case 1, UCI 1 and UCI 0 may not be multiplexed, and simultaneous transmission of PUCCH and PUSCH may be allowed. In this case, PUCCH 1, PUCCH 0, and PUSCH may be considered. PUCCH 1 and PUCCH 0 may be transmitted in different serving cells (eg, serving cell index 1, serving cell index 0). A serving cell through which PUSCH is transmitted may be the same as or different from serving cell(s) through which PUCCH 1 and PUCCH 0 are transmitted. The UE can transmit PUCCH 1, PUCCH 0, and PUSCH in three serving cells. One channel can be transmitted in one serving cell. If the two serving cells match, the UE can multiplex and transmit UCI and TB in the same serving cell. For example, the UE may transmit PUCCH 1 and PUSCH in different serving cells, and TB and UCI 0 may be multiplexed in PUSCH. For another example, the UE may transmit PUCCH 0 and PUSCH in different serving cells, and TB and UCI 1 may be multiplexed in PUSCH. After that, the terminal may perform a procedure considering the Tx panel.

In Case 2, UCI 1 and UCI 0 may be multiplexed, and simultaneous transmission of PUCCH and PUSCH may be permitted. In this case, PUCCH 1 and PUSCH may be considered. In one example, the UE may determine one PUCCH 1 in which UCI 1 and UCI 0 are multiplexed. PUCCH 1 and PUSCH may be transmitted in the same serving cell or different serving cells. The UE can transmit PUCCH 1 and PUSCH in two serving cells. If the serving cells match, the UE can multiplex and transmit UCI 1, UCI 0, and TB in the same serving cell. After that, the terminal may perform a procedure considering the Tx panel. In another example, the UE may consider PUSCH 1 to which UCI 1 is multiplexed and PUCCH 0 to which UCI 0 is mapped. When PUSCH 1 and PUCCH 0 are scheduled in different serving cells, the UE can simultaneously transmit PUSCH 1 and PUCCH 0. The UE may consider PUSCH 0 to which UCI 0 is multiplexed and PUCCH 1 to which UCI 1 is mapped. In different serving cells, the UE can simultaneously transmit PUSCH 0 and PUCCH 1.

In case 3, UCI 1 and UCI 0 may not be multiplexed, and simultaneous transmission of PUCCH and PUSCH may not be allowed. In this case, PUCCH 1, PUCCH 0, and PUSCH may be considered. The operation of the terminal may be subdivided. Since PUSCH and PUCCH are not simultaneously transmitted, UCI and TB can be multiplexed on PUSCH, and the corresponding PUSCH can be transmitted. UCI 1 and UCI 0 may not be multiplexed. For example, a UE may multiplex a UCI having the same priority as a TB and a corresponding TB on a PUSCH, and transmit the corresponding PUSCH. In this case, other UCIs (eg, UCIs having a different priority than TB) may not be transmitted. As another example, the UE may define a TB and a specific priority (eg, HP), multiplex UCI 1 having a specific priority and the corresponding TB on a PUSCH, and transmit the corresponding PUSCH. In this case, UCI 0 may not be transmitted. After that, the terminal may perform a procedure considering the Tx panel.

In Case 4, UCI 1 and UCI 0 may be multiplexed, and simultaneous transmission of PUCCH and PUSCH may not be allowed. In this case, PUCCH 1, PUCCH 0, and PUSCH may be considered. The UE can determine one PUCCH by multiplexing UCI 1 and UCI 0. One PUCCH may be PUCCH 1. Since PUCCH 1 and PUSCH cannot be transmitted simultaneously, both UCI 1 and UCI 0 can be multiplexed on PUSCH. Alternatively, some UCIs may be multiplexed on PUSCH. The latter method can be further refined. For example, TB and UCI 1 may be multiplexed on PUSCH, the corresponding PUSCH may be transmitted, and UCI 0 may not be transmitted. As another example, a UCI having the same priority as a TB and a corresponding TB may be multiplexed on a PUSCH, the corresponding PUSCH may be transmitted, and other UCIs may not be transmitted.

In the above cases, when the UE performs simultaneous transmission, it may be desirable to secure transmission power necessary for PUCCH or PUSCH. Thereafter, the remaining transmit power may be allocated as transmit power required for PUCCH 0. The base station may set case 1 and case 3 to the terminal using RRC signaling. A case in which the above-described operation can be supported may be limited to “a case in which serving cells in which PUCCH and PUSCH are transmitted are different from each other”. When serving cells belong to different frequency bands (eg, inter-band CA), the above-described RRC signaling operation may be supported. The aforementioned RRC signaling may be received by the UE.

When inter-band CA is configured, the serving cell of PUCCH and the serving cell of PUSCH may belong to different timing advance groups (TAGs). In this case, the multiplexing time of the ULCH may be set considering the first symbol of the PUSCH, the first symbol of the PUCCH, and different TAs.

1.5 Simultaneous support of UL transmission considering sidelink

A case in which two or more scenarios are supported in one terminal may be considered. When both device-to-device communication and communication between a terminal and a base station are supported, the terminal may perform direct communication in a resource scheduled by the base station. The terminal may communicate with the base station to perform URLLC communication. This may mean a scenario in which the terminal supports both sidelink and IIoT.

The UE may perform simultaneous transmission of PUCCH and PUSCH, but the above-described operation may be permitted in limited scenarios. In another scenario, PUCCH may not be transmitted, and UCI may be multiplexed and transmitted on PUSCH. In a limited scenario, PUCCH and PUSCH may correspond to different priority indices, and the serving cell to which the PUCCH is to be transmitted and the serving cell to which the PUSCH is to be transmitted are in different frequency bands (eg, inter-band) can belong to

When the terminal is configured to perform sidelink mode 1 resource allocation, the base station may allocate time resources and frequency resources to the terminal. A UE may transmit a physical sidelink control channel (PSCCH) and a physical sidelink shared channel (PSSCH) to other UEs using allocated resources. The UE may receive a decoding result of the PSSCH. Alternatively, the UE may assume a decoding result of the PSSCH as a specific value. The terminal may generate HARQ-ACK, which is a decoding result of the PSSCH, and may feed back the HARQ-ACK to the base station. At this time, the terminal may generate a sidelink HARQ codebook using one or more HARQ-ACK bits, and may transmit the sidelink HARQ codebook to the base station using a PUSCH or a PUCCH.

In the transmission procedure of the sidelink HARQ codebook, the sidelink HARQ codebook can be multiplexed in different UCI types and PUSCH. Considering all PUCCHs overlapping in time, the UE can transmit UCIs on one PUCCH. For transmission of the sidelink HARQ codebook, the UE may not multiplex the sidelink HARQ codebook with Uu UCI. Uu UCI may include SR for PUSCH transmission, HARQ-ACK for PDSCH, periodic CSI, semi-persistent CSI, aperiodic CSI, and/or LRR. The base station may perform scheduling such that the sidelink HARQ codebook is not transmitted in a time resource where Uu UCI is to be transmitted. That is, the base station may schedule Uu UCI and sidelink HARQ codebook so that they are not transmitted on the same PUCCH and/or PUSCH.

When the sidelink HARQ codebook and HP PUSCH (eg, PUSCH having priority index 1) overlap in the time domain, the UE may drop transmission of the sidelink HARQ codebook. That is, the sidelink HARQ codebook may not be multiplexed with HP PUSCH. The UE can transmit only the HP PUSCH. If the sidelink HARQ codebook and the LP PUSCH (eg, PUSCH having priority index 0) overlap in the time domain, the UE can multiplex the sidelink HARQ codebook on the LP PUSCH and transmit the LP PUSCH. In this case, Uu UCI may not be included in LP PUSCH.

The terminal may support all of inter-band CA, sidelink communication, and URLLC communication. In this case, since the UE can simultaneously transmit PUSCH and PUCCH, multiplexing and/or dropping with UCI or sidelink HARQ codebooks may not be considered. In order to support simultaneous transmission of PUSCH and PUCCH, the UE can determine whether a serving cell through which the PUSCH is transmitted and a serving cell through which the sidelink HARQ codebook is transmitted belong to the same frequency band.

If the serving cell to which the PUSCH is to be transmitted and the serving cell to which the sidelink HARQ codebook is to be transmitted belong to different frequency bands, the UE intends to transmit Uu UCI within the frequency band to which the serving cell to which the sidelink HARQ codebook is to be transmitted belongs. It is possible to check whether there is a serving cell to be used. This may have the purpose of avoiding multiplexing of Uu UCI and sidelink HARQ codebook. The base station may perform scheduling so that the serving cell to which the Uu UCI is to be transmitted and the serving cell to which the sidelink HARQ codebook is to be transmitted do not belong to the same frequency band. Even if the serving cell to which the PUSCH is to be transmitted and the serving cell to which the sidelink HARQ codebook is to be transmitted belong to the same frequency band, the base station indicates that the priority of the sidelink HARQ codebook is higher than the priority of Uu UCI, so that the UE can use the sidelink HARQ codebook. A codebook can be selected. Here, in the former method, the procedure for confirming the identity of the serving cell may be performed in the UE, and in the latter method, the procedure for confirming the identity of the serving cell may not be performed in the UE.

Method 1.5-1: When the UE performs simultaneous transmission, it can be considered that TB and Uu UCI are multiplexed on a PUCCH or a PUSCH multiplexed with a TB on which a sidelink HARQ codebook is transmitted, on a PUSCH or PUSCH in which simultaneous transmission is allowed. can

"If the UE transmits PUCCH in one frequency band and the sidelink HARQ codebook is included in the PUCCH", the PUSCH transmitted in another frequency band may include at least one combination of priority, TB, or Uu UCI there is.

13 is a conceptual diagram illustrating a first embodiment of a method for simultaneous transmission of a PUCCH and a PUSCH involving a sidelink HARQ codebook.

Referring to FIG. 13 , a UE may transmit an HP PUCCH in frequency band 1 and an LP PUSCH in frequency band 2. Sidelink HARQ codebook may be included in HP PUCCH, and TB and/or Uu UCI may be included in LP PUSCH.

14 is a conceptual diagram illustrating a second embodiment of a method for simultaneous transmission of a PUCCH and a PUSCH involving a sidelink HARQ codebook.

Referring to FIG. 14, a UE may transmit an LP PUCCH in frequency band 1 and an HP PUSCH in frequency band 2. Sidelink HARQ codebook may be included in LP PUCCH, and TB and/or Uu UCI may be included in HP PUSCH.

If "the terminal transmits the PUSCH in one frequency band and the sidelink HARQ codebook is included in the PUSCH", the PUCCH transmitted in the other frequency band may include Uu UCI.

15 is a conceptual diagram illustrating a third embodiment of a method for simultaneous transmission of a PUCCH and a PUSCH involving a sidelink HARQ codebook.

Referring to FIG. 15, a UE may transmit an LP PUSCH in frequency band 1 and an HP PUCCH in frequency band 2. Sidelink HARQ codebook and/or TB may be included in LP PUSCH, and Uu UCI may be included in HP PUCCH.

The priority of the sidelink HARQ codebook can be distinguished from the sidelink priority and priority index. Assuming that the priority of the sidelink HARQ codebook is determined, the priority index may be regarded as 0 or 1 through comparison between the boundary value indicated by RRC signaling to the UE and the priority of the sidelink HARQ codebook. The priority of the sidelink HARQ codebook may follow the highest priority among priorities of each of the sidelink HARQ-ACK bits constituting the sidelink HARQ codebook. If the priority index is 0, PUCCH may be regarded as LP PUCCH. If the priority index is 1, PUCCH may be regarded as HP PUCCH.

Chapter 2 How to receive group common DCI

Considering a communication system operating in FR2, a control channel and a data channel may be transmitted and received based on beams. A terminal and a base station (or TRP) may have one or more antenna panels, and in technical specifications, the antenna panels may be expressed as a QCL relationship or a TCI state index.

The search space set received by the terminal may be classified into various types. For example, the search space set includes a type0-PDCCH CSS set, a type0A-PDCCH CSS set, a type1-PDCCH CSS set, a type2-PDCCH CSS set, and a type3-PDCCH CSS set (e.g., a type3 CSS set). set), and USS set. In the type 3 CSS set, a group common DCI can be searched for.

The terminal may perform transmission and reception operations of multiple TRPs, control channels, and data channels. The TCI state index for multiple TRPs may be appropriately indicated, and the UE may not be able to distinguish between single TRPs and multiple TRPs. Alternatively, the terminal may implicitly distinguish between a single TRP and multiple TRPs. A CORESET pool may be configured by RRC signaling to the UE. Two or more QCL information may be derived from the TCI state index applied when receiving the PDCCH and/or PDSCH. Two or more QCL information may be derived from an SRI or TCI state index applied when PUSCH and/or PUCCH are transmitted. Here, one piece of QCL information may correspond to demodulation of one radio channel.

The group common DCI may include information transmitted to a plurality of terminals. For example, in the NR system, DCI format 2_0 may represent slot format indicator (SFI) or channel occupancy time (COT). DCI format 2_1 may represent downlink preemption indication (DLPI). DCI format 2_2 may represent transmit power control (TPC) PUSCH/PUCCH. DCI format 2_3 may represent TPC SRS. DCI format 2_4 may represent uplink cancellation indication (ULCI). The above-mentioned indication and / or information may also be set in other DCI formats. Information on a plurality of terminals or a plurality of serving cells may be composed of one information word (eg, information bit), and one information word may be included in the GC-DCI. The information word may be generated as one code word through a common encoding operation. Information useful for a specific terminal may correspond to a part of an information word, and a location of useful information within the information word may be indicated to the terminal by RRC signaling.

In FR2, GC-DCI can be transmitted based on a beam. It may be desirable that the beam(s) formed in each of the Tx panel(s) and Rx panel(s) may be properly aligned, and good quality (e.g., SINR) obtained at the Rx panel(s) . In the DL transmission procedure, the beam(s) of the Tx panel(s) of the TRP and the beam(s) of the Rx panel(s) of the UE may be paired. In the UL transmission procedure, the beam(s) of the Tx panel(s) of the UE and the beam(s) of the Rx panel(s) of the TRP may be paired. TRP may mean a beam. Depending on the purpose of GC-DCI, TRP can mean either a Tx panel or an Rx panel.

2.1 How to support GC-PDCCH in multiple TRPs

A specific terminal can dynamically receive scheduling information from a plurality of TRPs, and another terminal can receive scheduling information from one TRP. A specific terminal can transmit and receive URLLC traffic, another terminal can transmit and receive eMBB traffic, and another terminal can transmit and receive both eMBB traffic and URLLC traffic.

According to specific scheduling, interference may occur between a terminal that transmits and receives URLLC traffic and a terminal that transmits and receives eMBB traffic. According to another scheduling method, interference between a terminal that transmits and receives URLLC traffic and a terminal that transmits and receives eMBB traffic may be insignificant. That is, the interference can be ignored.

GC-DCI can be received from one or more CORESET pools. GC-DCI may have information received by two or more terminals, and the terminal may transmit and receive information with two or more TRPs. A terminal receiving GC-DCI may need information on only one TRP, and another terminal may need information on both TRPs. This may be applied to the same serving cell. When two or more serving cells are configured, the GC-DCI may include information for each serving cell.

Method 2.1-1: For the serving cell, information can be obtained from only one location of the GC-DCI.

GC-DCI may include information on only one TRP. Alternatively, the GC-DCI may include information about TRPs. Information on TRPs may be concatenated with each other and may be expressed as information having a length twice or more based on one starting position. The starting position may be set by RRC signaling, and information on the length may be explicitly set from RRC signaling. Alternatively, information on the length may be implicitly derived by RRC signaling.

Method 2.1-2: The number of TRPs (or the number of beams or the number of panels) observed by the UE may be indicated to the UE by RRC signaling. Alternatively, the number of TRPs (or the number of beams or the number of panels) observed by the UE may be derived implicitly.

16 is a conceptual diagram illustrating a first embodiment of a method of checking information on a plurality of TRPs at one location in a GC-DCI.

Referring to FIG. 16, all information necessary for a terminal can be concatenated and mapped at one location. Method 2.1-2 can be extended, and even when two or more serving cells are configured for the UE, information can be checked from the same location.

Method 2.1-2: In Method 2.1-1, information may be mapped into GC-DCI in the order of TRP (or beam, RS group, panel), and then information is mapped into GC-DCI in order of serving cell index It can be.

Method 2.1-3: The method shown in FIG. 17 below may be applied.

17 is a conceptual diagram illustrating a first embodiment of a method for checking information on a plurality of serving cells and a plurality of TRPs at one location in a GC-DCI.

Referring to FIG. 17, information on TRPs belonging to the same serving cell may be located contiguous with each other. Based on the combination of method 2.1-2 and method 2.1-3, the terminal can check the location of information about the necessary serving cell index and the necessary TRP within the GC-DCI. Alternatively, the order of the serving cell index and TRP (or beam, RS group, panel) may be reversed. That is, information can be mapped into GC-DCI in the order of serving cell index, and then information can be mapped into GC-DCI in the order of TRP. According to the above method, the length of a block in GC-DCI can be determined according to method 2.1-2. According to another method (eg, method 2.1-4), the length of the same block may be ascertained at each of different positions.

Method 2.1-4: Depending on the number of TRPs (or beams, RS groups, and panels), two or more positions of one serving cell may be known to the UE.

GC-DCI may include information about two or more TRPs. The UE may receive the location of the GC-DCI through RRC signaling. RRC signaling may indicate two or more locations for GC-DCI to the UE. According to method 2.1-4, the starting position where information on each TRP is located may be indicated to the terminal. This operation can be shown in FIG. 18 below.

18 is a conceptual diagram illustrating a first embodiment of a method for acquiring information at two or more locations within a GC-DCI.

Referring to FIG. 18, a base station may indicate a start position of information for each of TRP i and TRP j within GC-DCI to the terminal using RRC signaling. In one example, the terminal may receive an RRC variable indicating a start position of information on each TRP from the base station. The above methods may be applied in DCI format 2_2 and/or format 2_3.

2.2 How to receive DLPI

When puncturing of the eMBB PDSCH occurs due to transmission of the URLLC PDSCH, the base station may transmit a downlink preemption indicator (DLPI) to the terminal. DLPI may be transmitted to the UE through GC-DCI. For example, the terminal may receive DCI format 2_1 including DLPI.

The DLPI may be a bitmap indicating a puncturing pattern for reference numerology in a given serving cell. The terminal may interpret the bitmap (eg, DLPI) according to the method determined in the technical standard. One bit in the bitmap may mean a time resource and a frequency resource. The UE may compare resources indicated by scheduling information of PDSCH with resources indicated by DLPI. When a resource indicated by scheduling information and a resource indicated by DLPI overlap, the UE may not perform a PDSCH decoding operation.

DLPI may be given differently for each beam or TRP. URLLC PDSCH can be transmitted for each TRP or beam, and eMBB PDSCH can be transmitted for different TRPs or different beams. For the same time and frequency resources, puncturing of one beam may occur and puncturing of another beam may not occur. If it is determined that interference does not occur between beams, the base station may express the puncturing pattern differently.

Puncture may be performed in the Tx panel (or Tx beam) of the base station (or TRP). A UE receiving the eMBB PDSCH in the Tx beam of the base station may receive the DLPI. On the other hand, puncturing may not occur in a UE receiving an eMBB PDSCH in a different Tx beam. A method for allowing the UE to interpret the DLPI limited to the scheduled Tx beam may be required. A terminal may have a plurality of Rx panels (or a plurality of Rx beams).

A beam management procedure may be performed before PDSCH scheduling. The base station (or TRP) may determine the Tx beam, and information necessary for the terminal to determine the Rx beam may be included in scheduling information. Since DLPI can be generated based on the Tx beam of the base station, the Rx beam of the UE can be derived based on the TCI state index included in scheduling information (eg, DCI or RRC signaling). In addition, the TCI state index may be configured by RRC signaling to the UE. Therefore, even when it is assumed that the Tx beam of the base station can be derived from the TCI state index, different TCI state indexes may be required for each UE in order to express the same Tx beam.

When the Tx beam of the base station is interpreted as a Tx panel, the DLPI may additionally include information suggesting the Tx panel as well as a bitmap. For example, it may be considered that the Tx panel index is included in the DLPI. In one method, a block constituting the DLPI may include the index of the Tx panel as well as the bitmap. In technical specifications, the Tx panel(s) utilized by the base station may be defined. In this case, the terminal receiving the DLPI can recognize the Tx panel and can check whether the DLPI is applied. If the Tx panel scheduled for the UE and the Tx panel included in the DLPI match, the UE can compare the resource indicated by the DLPI bitmap with the PDSCH region.

It is assumed that the Tx panel generates one Tx beam, but different Tx beams may be used for specific symbol(s). In this case, it may be desirable to present one or more Tx panels. This may mean that information of a plurality of Tx panels is included, and overhead may increase. Since the DLPI is transmitted through the GC-DCI, information for each UE may not be included in the DLPI (eg, GC-DCI). DLPI (eg, GC-DCI) may include useful information in a plurality of terminals. Also, information on the Tx panel may not be defined in the technical specifications.

In another method, as a method of expressing a Tx panel or a Tx beam, an index applicable to a plurality of terminals may be introduced. For example, SS/PBCH block index (eg, SSB index) may be considered. The SSB index may mean the Tx beam of the base station and/or the Rx beam of the terminal. The SSB index may be indicated to the UE through RRC signaling. The SSB index, which is information common to terminals rather than the Tx panel index used by the base station, may be included in the DLPI together with the bitmap.

Method 2.2-1: DLPI may include SSB index.

According to the TCI state index received by the terminal, the Tx beam estimated to be used by the base station can be derived. From the TCI state index, qcl-type1 and qcl-type2 can be derived, and an RS or SSB index provided with qcl-type A can be derived from qcl-type1. When RS is derived from qcl-type 1, an SSB index providing fine time sync and fine frequency sync for RS can be derived. When the above-described operation is repeated, the UE can check the SSB index x providing qcl-type 1 associated with the PDSCH DM-RS.

The UE may check whether the SSB index included in the DLPI and the index x are identical. If the SSB index included in the DLPI is equal to index x, the UE may consider that puncturing has occurred in the same Tx beam as SSB index x. If the SSB index included in the DLPI is different from the index x, the UE may consider that puncturing does not occur in the same Tx beam as the SSB index x.

Method 2.2-2: In method 2.2-1, a block of DLPI may include a bitmap and an SSB index.

If different Tx beams are used in specific symbol(s), the DLPI may include a plurality of SSB indices. If the DLPI includes SSB index(s), a block of the DLPI may include a plurality of SSB indexes. Alternatively, a separate block may include SSB indices, and puncturing may be determined based on a combination with a block set to be referred to by the terminal.

According to another method, Tx beam change information may be transmitted instead of accurate Tx beam information where puncturing occurs. Comparing this operation with Method 2.2-1, overhead generated as the DLPI includes a plurality of SSB indexes can be reduced.

Method 2.2-3: DLPI may include information about change of Tx beam.

Changing the Tx beam may mean changing the Tx panel (or Tx beam) of the base station (or TRP). Changing the Tx beam may mean not using the Tx beam (or Tx panel) planned to be used by the UE in the scheduling step. The change information of the Tx beam may indicate beam change or beam maintenance. The size of the Tx beam change information may be 1 bit. Since a plurality of Tx beams may be punctured, a plurality of bits may be required for change information of the Tx beam.

Method 2.2-4: In method 2.2-3, a DLPI (eg, a block of DLPI) may include a bitmap and Tx beam change information. Alternatively, the bitmap may include change information of the Tx beam.

The minimum unit to which puncturing is applied in the Tx beam may be the number of symbols representing the time unit of the DLPI. The minimum unit to which puncturing is applied in the Tx beam may be the same as the number of bits representing time in the DLPI. This is because the Tx beam is formed in a wideband and does not need to additionally express a frequency. Methods 2.2-4 may be illustrated in FIG. 19 .

19 is a conceptual diagram illustrating a first embodiment of GC-DCI including beam information.

Referring to FIG. 19, a UE may receive DLPI, and may use both a bitmap indicating Tx beam change (eg, a beam change bitmap) and a bitmap indicating puncturing in a block related to DLPI. . "If puncturing occurs and the Tx beam is maintained, the UE can recognize that puncturing has occurred. "If puncturing occurs and the Tx beam is determined to be changed", the UE transmits the Tx beam of the base station (or TRP) It may be determined that no puncturing has occurred in the beam (or Tx panel or resource).

2.3 How to receive ULCI

When interference of the eMBB PUSCH is expected due to transmission of the URLLC PUSCH, the base station may transmit an uplink cancellation indicator (ULCI) to the terminal. ULCI may be transmitted to the UE through GC-DCI. For example, the terminal may receive DCI format 2_4 including ULCI.

According to technical specifications, ULCI may be a bitmap indicating a cancellation pattern for reference numerology in a given serving cell. The terminal may interpret the bitmap according to the method specified in the technical standard. One bit may mean a time resource and a frequency resource, and the UE may compare a resource indicated by a bitmap with a resource indicated by scheduling information received from a base station. When the resources indicated by the bitmap and the resources indicated by the scheduling information overlap, the UE may not transmit the PUSCH.

ULCI may be set differently for each beam, TRP, or Rx panel. The base station can receive URLLC PUSCH for each TRP or Rx beam, and can receive eMBB PUSCH for different TRPs or different Rx beams. For the same time and frequency resources, interference may occur in one beam, but interference may not occur in another beam. When it is determined that interference does not occur between beams, the base station may prefer to express a cancellation pattern differently.

Since interference occurs in the Rx panel (or Rx beam) of the base station (or TRP), the ULCI can be received by the terminal transmitting the eMBB PUSCH through the Rx panel (or Rx beam) of the base station. On the other hand, there may be little or no interference from other Rx beams of the base station through which the eMBB PUSCH is received. A method for interpreting ULCI limited to terminals transmitting signals and/or channels through an Rx beam that the base station plans to use may be required. A UE may have a plurality of Tx panels (or Tx beams).

A beam management procedure may be performed before a PUSCH scheduling procedure. The base station may determine the Rx beam and transmit scheduling information including information for determining the Tx beam of the terminal (eg, the Tx beam of the terminal corresponding to the Rx beam of the base station) to the terminal. The terminal may receive scheduling information from the base station and check information included in the scheduling information. Since ULCI can be generated based on the Rx beam of the base station, the Tx beam of the UE can be derived based on the SRI (or TCI state index) included in scheduling information (eg, DCI or RRC signaling). Since the SRI is configured by RRC signaling to the UE, it can be assumed that the Rx beam of the base station can be derived from the SRI. Even in this case, different SRIs may be required for each UE in order to express the same Rx beam.

When the Rx beam of the base station is interpreted as an Rx panel, the ULCI may include information suggesting the Rx panel as well as a bitmap. For example, an Rx panel index may be considered as information suggesting an Rx panel. In technical specifications, the Rx panel(s) used by the base station may be defined. The above definition may not be desirable, since different Rx beams may be used for specific symbol(s). As another method of expressing an Rx panel or an Rx beam, an index applied to a plurality of terminals may be considered. For example, an SSB index may be considered to represent an Rx panel or an Rx beam. The SSB index may mean the Rx beam of the base station and may mean the Tx beam of the terminal. The SSB index may be indicated to the UE through RRC signaling. An SSB index, which is information common to terminals rather than an index of an Rx panel used by a base station, may be used, and the ULCI may include the SSB index along with a bitmap.

Method 2.3-1: ULCI may include SSB index.

The terminal may derive a Tx beam estimated to be used by the base station based on the SRI (or TCI state index) received from the base station. A Tx beam (or spatial relation) applied to a corresponding SRS resource may be derived from SRI. The Tx beam of the SRS resource may be derived based on the Rx beam used for reception of the DL RS. Alternatively, the Tx beam of the SRS resource may be derived based on the Tx beam of the SRS resource having a different SRI. A DL RS may be a CSI-RS or SSB, and an Rx beam of a CSI-RS may refer to an Rx beam for another CSI-RS or SSB. By repeating the above-described operation, the UE can check the SSB index x providing the Tx beam associated with the PUSCH DM-RS. At this time, when the terminal transmits the PUSCH corresponding to the SRI, the base station may use the Rx beam derived based on the Tx beam to which the SSB index x is transmitted.

The UE can check whether the SSB index included in the ULCI is the same as the SSB index x. If the SSB index included in the ULCI is equal to SSB index x, the UE may consider that interference is expected to occur in the Rx beam corresponding to SSB index x. If the SSB index included in the ULCI is different from the SSB index x, the UE may consider that no interference occurs in the Rx beam corresponding to the SSB index x.

Method 2.3-2: In method 2.3-1, a block for ULCI may include a bitmap and an SSB index.

If different Rx beams are used in specific symbol(s), the ULCI may include a plurality of SSB indices. In this case, a block of ULCI may include a plurality of SSB indices. Alternatively, a separate block in the DCI may include SSB indexes, and whether or not interference occurs may be confirmed based on a combination with a block configured to be referred to by the terminal. According to another method, Rx beam change information may be transmitted instead of information accurately indicating an Rx beam in which interference occurs. Comparing this method with Method 2.3-1, overhead caused by the DCI (eg, ULCI) including a plurality of SSB indices can be reduced.

Method 2.3-3: ULCI may include Rx beam change information.

Changing the Rx beam may mean changing the Rx panel (or Rx beam) of the base station (or TRP). Changing the Rx beam may mean not using the Rx beam (or Rx panel) planned to be used by the UE in the scheduling step. The Rx beam change information may indicate beam change or beam maintenance. The size of the Rx beam change information may be 1 bit. Since conditions for interference may change when a plurality of Rx beams are used, a plurality of bits may be required for Rx beam change information.

Method 2.3-4: In method 2.3-3, a ULCI (eg, block of ULCI) may include a bitmap and Rx beam change information. Alternatively, the ULCI bitmap may include Rx beam change information.

The minimum unit for estimating the presence or absence of interference in the Rx beam may be the number of symbols representing a time unit of ULCI. The minimum unit for estimating the presence or absence of interference in the Rx beam may be the same as the number of bits representing the time of ULCI. The reason for this is that the Rx beam is formed with a wide band, so there is no need to additionally express the frequency. Methods 2.3-4 may be illustrated in FIG. 19 .

The UE may receive ULCI and may use both a bitmap indicating Rx beam change (eg, a beam change bitmap) and a bitmap indicating interference in a block related to ULCI. If it is interpreted that the Rx beam is maintained even when transmission of the PUSCH is allowed in the resource indicated by the ULCI, the UE may determine that interference occurs in the Rx beam (or Rx panel or resource) of the base station. Accordingly, the UE may not transmit the PUSCH. If it is interpreted that the Rx beam is changed when transmission of the PUSCH is allowed in the resource indicated by the ULCI, the UE may determine that no interference occurs in the Rx beam (or Rx panel or resource) of the base station. If two or more Rx beams (or Rx panels, resources) can be processed according to the capabilities of the base station, the UE can transmit the PUSCH (ie, the first operation of the UE). If the base station can process one Rx beam (or Rx panel, resource), since the base station cannot receive the PUSCH of the terminal, the terminal may not transmit the PUSCH (ie, the second operation of the terminal) . In one example, the operation of the terminal in the technical standard may be defined as one of the above-described first operation and second operation. In another example, the base station may set one operation of the above-described first operation and second operation to the terminal using higher layer signaling. The terminal may perform one operation (eg, a first operation or a second operation) set by higher layer signaling.

2.3.1 How Priority is Interpreted

LP PUSCH can be canceled using ULCI, and PUCCH can be transmitted as it is. LP PUSCH may include LP UCI and/or LP UL-SCH. For transmission of HP UCI and/or HP UL-SCH, a UE may multiplex UCI and/or UL-SCH having the same priority. When multiplexing is performed on UCI and/or UL-SCH having different priorities, the UE may not cancel PUCCH transmission even when ULCI is received. When LP UL-SCH and "LP UCI and/or HP UCI" are multiplexed, HP UCI may also not be transmitted if PUSCH transmission is canceled.

Method 2.3-5: The UE may derive an effective priority of the PUSCH based on the UCI or UL-SCH having the highest priority.

In one example, when HP UCI is multiplexed on a PUSCH scheduled by a DCI allocating an LP UL-SCH, it can be interpreted that the priority of the corresponding PUSCH is high. Therefore, the UE can transmit the PUSCH regardless of ULCI. UCI may include at least HARQ-ACK for DL-SCH or SL-SCH.

2.4 TPC commands

In the DCI format for controlling the power of the PUCCH, the power (eg, TPC command) for the PCell and the PUCCH serving cell may be indicated in a separate location. When the PUCCH is transmitted to the UE in two serving cells, each of the locations (eg, the location of the TPC command) for the PCell and the additional serving cell may be indicated to the UE by RRC signaling.

Method 2.4-1: In the DCI format for controlling PUCCH power, the positions of all serving cells capable of PUCCH transmission (eg, positions of TPC commands) may be configured in the UE by RRC signaling, and for each serving cell The TPC command may be independently instructed to the terminal.

Chapter 3 PUCCH transmission method

The UE may transmit PUCCH using the Tx panel(s). The method and embodiment below will be described based on one Tx panel, but can also be applied to two or more Tx panels.

3.1 PUCCH transmit power control method

Transmit power applied to PUCCH may be calculated based on an equation defined in technical specifications. For example, transmit power of PUCCH may be calculated based on Equation 1 below. Here, P ( i,u,d,l ) may be applied to transmission occasion i of PUCCH, and u may indicate an index of a DL-RS used by the UE to calculate power power, d may indicate an index of a UL-RS used by the UE to calculate power, and l may indicate an index of a set managing TPC commands.

P _o ( u ) may be a reference variable for transmission power of the PUCCH, and a value for the u -th power control loop may be indicated to the UE by RRC signaling. μ may be a variable for the subcarrier spacing used by the PUSCH instance, and PL ( d ) may be the amount of path attenuation of the DL calculated based on the reference RS d when the reference RS is defined as d . The UE may estimate PL ( d ) based on the measurement result of the reference RS. g ( i, l ) may be an accumulated value of TPC commands for the lth power control loop.

가 정의될 수 있다.The value of _ΔF may be indicated to the UE by RRC signaling. The value of _ΔF may be indicated differently according to the PUCCH format. A value of Δ _{( i )} may be fixed to 0 according to a value indicated by RRC signaling. Alternatively, the value of Δ _{( i )} may be calculated as a different value according to a value indicated by RRC signaling. Different equations may be applied depending on the PUCCH format. The reason is to adjust the offset of transmission power so that a similar BLER can be experienced because a spreading code is applied to PUCCH or PUCCH has a different code scheme. If the PUCCH format is PUCCH format 0 or 1,

can be defined.

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

가 정의될 수 있다. 여기서, K ₁와 K ₂는 기술규격에서 정해진 상수(constant)일 수 있다. BPRE(bits per resource element)는 부호율과 관련된 변수일 수 있고,

에 의해 정의될 수 있다.

과

는 HARQ-ACK의 양을 의미할 수 있고, O _SR (i)은 SR을 표현하는 비트의 양을 의미할 수 있고, O _CSI (i)은 CSI의 양을 의미할 수 있다. O _CRC (i)는 CRC의 양을 의미할 수 있다. N(i)은 PUCCH 자원이 갖는 RE의 개수를 의미할 수 있다. N(i)에 해당하는 RE들에서 DM-RS가 맵핑 되는 RE는 제외될 수 있다.When the PUCCH format is PUCCH format 2, 3, or 4, the UCI may be classified into a UCI having a size of 11 bits or less and a UCI having a size of 12 bits or more. If the size of UCI is 11 bits or less,

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

can be defined. Here, K ₁ and K ₂ may be constants determined in technical specifications. Bits per resource element (BPRE) may be a variable related to a code rate,

can be defined by

class

may mean the amount of HARQ-ACK, O _SR ( i ) may mean the amount of bits representing SR, and O _CSI ( i ) may mean the amount of CSI. O _CRC ( i ) may mean the amount of CRC. N ( i ) may mean the number of REs that PUCCH resources have. Among the REs corresponding to N ( i ), the RE to which the DM-RS is mapped may be excluded.

g ( i,l ) may mean an accumulated value of TPC command(s) received through DCI(s) during a preset time period. The preset time can be defined in technical specifications. The time to start accumulating TPC commands for PUCCH transmission location i may be after the time to end accumulation of TPC commands for PUCCH transmission location i - i ₀ . The time for ending TPC command accumulation for PUCCH transmission location i may mean the last symbol of CORESET to which the last DCI belongs, among DCIs scheduling UCI transmission in PUCCH transmission location i . Here, i ₀ may mean a minimum natural number for which a time interval during which accumulation of TPC commands is performed may be greater than 0. The cumulative operation of the TPC instruction can only be applied for the same l .

UCIs having the same priority may be multiplexed on a PUCCH, and the corresponding PUCCH may be transmitted. Therefore, Equation 1 can be applied. When UCIs having different priorities are multiplexed, the power of PUCCH may not be properly expressed only with Equation 1.

Method 3.1-1: Considering the amount of UCIs having different priorities, transmit power of a PUCCH on which HP UCI and LP UCI are multiplexed may be corrected.

In the case of "when LP UCI and HP UCI are multiplexed and an existing PUCCH resource set is used", an equation for deriving transmit power may vary depending on the amount of UCI. In the case of "when LP UCI and HP UCI are multiplexed and one PUCCH resource set is defined", it may be assumed that the amount of UCI is always larger than a predetermined amount. For example, the terminal may assume that the amount of LP UCI is 12 bits or more in the calculation procedure of Δ( i ).

Method 3.1-2: According to the PUCCH format in which LP UCI and HP UCI are multiplexed, Δ'( i ) may be additionally added to the transmit power of the PUCCH.

또는

가 정의될 수 있다. PUCCH가 HP DCI에 의해 지시되는 경우, Δ'(i)는 LP UCI의 양으로부터 도출될 수 있다. HP DCI에서 지시한 PUCCH 포맷에 대해서,

또는

가 정의될 수 있다. BPRE는

을 의미할 수 있다. 여기서, K₁과 K₂의 값은 LP UCI와 HP UCI에서 서로 다를 수 있다. 여기서 N(i)는 HP UCI와 LP UCI에서 동일한 값을 가질 수 있다. Δ(i)와 Δ'(i)의 계산 절차에서, LP UCI가 맵핑 되는 RE의 개수(N(i))와 HP UCI가 맵핑 되는 RE의 개수(N'(i))는 서로 다를 수 있으므로, 서로 다른 N(i)와 N'(i)는 적용될 수 있다.When PUCCH is indicated by LP DCI, Δ'( i ) may be derived from the amount of HP UCI. For the PUCCH format indicated by LP DCI,

or

can be defined. When PUCCH is indicated by HP DCI, Δ' ( i ) may be derived from the amount of LP UCI. For the PUCCH format indicated by HP DCI,

or

can be defined. BPRE is

can mean Here, the values of K ₁ and K ₂ may be different between the LP UCI and the HP UCI. Here, N ( i ) may have the same value in HP UCI and LP UCI. In the calculation procedure of Δ( i ) and Δ′( i ), the number of REs to which LP UCI is mapped ( N ( i )) and the number of REs to which HP UCI are mapped ( N’ ( i )) may be different, so , different N ( i ) and N' ( i ) can be applied.

Method 3.1-3: When Δ( i ) and/or Δ'( i ) are calculated in Method 3.1-2, N ( i ) and N' ( i ) are based on the number of REs to which rate-matched UCIs are mapped can be determined by

According to another method, the LP UCI and the HP UCI may not be distinguished from each other and may be summed as the amount of UCI. A separate Δ′( i ) may not be introduced and Δ( i ) may be defined differently. When HP UCI and LP UCI are multiplexed, multiplexed information may be limited to HARQ-ACK. In this case, Δ( i ) can be calculated based on one offset.

Method 3.1-4: According to the format of PUCCH in which LP UCI and HP UCI are multiplexed, priority based on the amount of HARQ-ACK and/or RE is considered to calculate Δ( i ) for transmit power. can

가 정의될 수 있다. LP UCI와 HP UCI의 산술적인 합이 12비트 이상인 경우에,

의 계산 절차에서,

가 정의될 수 있다.In one example, when the arithmetic sum of the LP UCI and the HP UCI is 11 bits or less,

can be defined. If the arithmetic sum of LP UCI and HP UCI is 12 bits or more,

In the calculation procedure of

can be defined.

또는

가 정의될 수 있다. 여기서, LP UCI의 양은

로 정의될 수 있고, HP UCI의 양은

로 정의될 수 있다. BPRE는

으로 정의될 수 있고, LP UCI와 HP UCI의 양은 더해질 수 있다. In another example,

or

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

, and the amount of HP UCI is

can be defined as BPRE is

, and the amounts of LP UCI and HP UCI may be added.

3.2 How to change PUCCH carrier

In a terminal supporting URLLC traffic, a delay time for transmitting and receiving control information may be advantageous as it is smaller. A difference between the reception time of DCI and the transmission time of UCI (eg, HARQ-ACK for PDSCH allocated by DCI) for DCI may occur, and resources capable of transmitting other UCI types (CSI, SR) Frequent occurrences may be desirable. It may be desirable to frequently generate resources capable of transmitting PDSCH and/or PUSCH.

Full-duplex operation may be performed in an FDD system (eg, a system operating in FDD), and half-duplex operation may be performed in a TDD system (eg, a system operating in TDD). Time (eg, alignment delay) waiting for the DL slot and/or the UL slot in the terminal may be additionally required. For transmission of UCI, PUCCH and/or PUSCH may be transmitted to the UE. PUCCH and/or PUSCH may be transmitted in one serving cell. One serving cell may be referred to as a special serving cell (SpCell) among a plurality of serving cells to which frequency aggregation is applied. One serving cell may mean a PCell of a master cell group (MCG) and/or a PSCell of a secondary cell group (SCG). One serving cell may mean PUCCH-SCell of MCG or SCG.

In a TDD system, time waiting for a UL slot of a specific serving cell may be wasted. In order to solve this problem, it may be desirable to allow PUCCH transmission in several serving cells rather than a specific serving cell. PUCCH transmission may be performed in one Tx panel according to spatial relation info (or Tx filter) configured for the UE. If two or more spatial relationships are indicated to the UE, PUCCH transmission may be performed on two or more Tx panels.

3.2.1 Transmission method of RRC configured pattern

A base station may utilize multiple carriers. The base station may set all or some carriers to the terminal through RRC signaling. That is, the base station may set or instruct the terminal to perform frequency aggregation using RRC signaling. All or some of the configured serving cells may be activated or deactivated by MAC signaling from the base station. An activated serving cell may utilize one DL BWP and/or UL BWP by technical specifications or PHY signaling from a base station.

PUCCH resources may be configured for each UL BWP. PUCCH-config for UL BWP may be configured, and a plurality of PUCCH resources may be configured by PUCCH-config. Several serving cells may be configured for the UE, and a case in which all or some of the configured serving cells are activated may be considered.

Method 3.2-1: PUCCH-config may be configured in all or some of configured serving cells. Two or more PUCCH serving cells may exist in a PUCCH cell group.

The base station may inform the terminal of the serving cell through which the PUCCH is transmitted using the scheduling DCI. Alternatively, the base station may inform the terminal of which serving cell to transmit the PUCCH in a specific slot using RRC signaling. Combinations of the methods described above may be used.

The base station may set the PUCCH serving cell pattern to the terminal using RRC signaling. Since two or more serving cells are utilized by frequency aggregation, two or more BWPs may be utilized. One PUCCH serving cell pattern configured by RRC signaling may be applied to a plurality of BWP combinations. The subcarrier spacing of the BWP of PCell and the subcarrier spacing of BWP of SCell may be different.

Method 3.2-2: Information indicating the PUCCH serving cell pattern includes a reference subcarrier interval, a reference serving cell index (eg, a reference index of a serving cell), a length of the PUCCH serving cell pattern, and a period in which the PUCCH serving cell pattern is applied. , or index (s) of serving cell (s) belonging to the PUCCH cell group.

The base station may separately set the reference subcarrier interval to the terminal. Alternatively, the terminal may derive a subcarrier spacing (eg, referenceSubcarrierSpacing) for interpreting the TDD slot pattern from RRC signaling, and may determine the derived subcarrier spacing as a reference subcarrier spacing. The UE may utilize the reference subcarrier interval as a criterion for interpreting the PUCCH serving cell pattern. Here, a specific combination of the period of the PUCCH serving cell pattern and the reference subcarrier interval may be indicated to the UE.

The PUCCH serving cell pattern may be applied in slots including at least UL symbols. Depending on the slot pattern and/or dynamic SFI, FL symbols may also be utilized for PUCCH transmission. When frequency aggregation is configured, not one serving cell but a plurality of serving cells may be configured as a PUCCH serving cell. Therefore, it may be desirable for the PUCCH serving cell pattern to include information on all slots.

Method 3.2-3: In Method 3.2-2, the information indicating the PUCCH serving cell pattern may include one of a reference subcarrier interval and an index of a reference serving cell.

A plurality of UL BWPs may operate in the reference serving cell. In this case, the subcarrier interval of the UL BWP may be selected based on one UL BWP among a plurality of UL BWPs. The UE may utilize the selected subcarrier range to interpret the PUCCH serving cell pattern. According to an example, a PUCCH serving cell pattern may be defined using either a reference subcarrier interval or an index of a reference serving cell. According to another example, one of a reference subcarrier interval or an index of a reference serving cell may be selected by RRC signaling, and the selected information may be used to interpret a PUCCH serving cell pattern. In another example, when the index of the reference serving cell is fixed to PCell, separate information may not be indicated to the UE. In this case, the reference subcarrier interval may be indicated to the UE using RRC signaling. Alternatively, the reference subcarrier spacing may be applied as a subcarrier spacing of an active UL BWP.

3.2.2 Method not following PUCCH serving cell pattern

The UE may not always be able to use the PUCCH serving cell pattern. After the PUCCH serving cell pattern is configured or instructed to the UE, some serving cells belonging to the PUCCH cell group may be deactivated. In this case, the UE may not be able to use the deactivated serving cell to transmit the PUCCH. In a specific BWP (eg, dormant BWP) for an activated serving cell belonging to a PUCCH cell group, the UE cannot transmit the PUCCH. In this case, the UE must transmit the PUCCH using a specific serving cell and an activated UL BWP (or reference BWP) according to the PUCCH serving cell pattern, but since the corresponding serving cell or UL BWP cannot be used, another reference serving cell and/or other criteria UL BWP may be required.

Method 3.2-4: If the PUCCH cannot be transmitted according to the PUCCH serving cell pattern configured for the UE, the UE may transmit the PUCCH in the reference serving cell and reference BWP.

For example, the reference serving cell may be PCell, PSCell, or SpCell. Alternatively, a separate serving cell index may be configured for the UE. For example, the reference BWP may be a BWP currently activated in the reference serving cell. In another example, the reference BWP may be a firstActiveUplinkBWP (BWP) initially activated in the reference serving cell. In this case, the BWP id may be additionally indicated in order to notify the UE of the firstActiveUplinkBWP.

Method 3.2-5: In method 3.2-4, the index and/or BWP id of the reference serving cell may be additionally indicated to the UE.

Meanwhile, the UE may receive the PDSCH based on fallback DCI. In this case, the UE may not follow the PUCCH serving cell pattern and may transmit PUCCH using SpCell (or PUCCH-SCell). The fallback DCI format may be used for RRC connection re-establishment, handover, and/or load balancing. When the RRC configuration variable is changed, the PUCCH serving cell pattern may be changed. In this case, when the fallback DCI is received, the UE may not transmit the PUCCH in the PUCCH serving cell indicated in the PUCCH serving cell pattern and may transmit the PUCCH in the SpCell. In this case, the following methods can be applied.

Method 3.2-6: According to the format of the DCI for allocating the PDSCH, the UE may or may not follow the PUCCH serving cell pattern.

For example, for a PDSCH scheduled with a fallback DCI (eg, DCI format 1_0), the UE may not follow the PUCCH serving cell pattern in order to determine a serving cell transmitting the PUCCH. On the other hand, for a PDSCH scheduled with a non-fallback DCI (eg, DCI format 1_1 or DCI format 1_2), the UE may follow the PUCCH serving cell pattern. The PUCCH serving cell pattern may be set or indicated to the UE through RRC signaling.

An embodiment may be further specified in case a fallback DCI is utilized. In one example, regardless of the search space set in which the fallback DCI is detected, the UE may transmit PUCCH in PCell, PSCell, PUCCH-SCell, or SpCell. In another example, the PUCCH serving cell through which the UE transmits the PUCCH may be changed according to the search space set in which the fallback DCI is detected. For example, for a PDSCH allocated as a fallback DCI, when the search space in which the fallback DCI is received is a CSS set, the UE may not follow the PUCCH serving cell pattern. If the search space in which the fallback DCI is received is the USS set, the UE may follow the PUCCH serving cell pattern.

Method 3.2-7: According to the search space set in which the fallback DCI is discovered, the UE may or may not follow the PUCCH serving cell pattern.

3.2.3 Method of Indicating Slot Offset of PUCCH Serving Cell

A method of determining a time resource for transmitting HARQ-ACK in DL-DCI may be considered. The offset (eg, K1 offset) for the (sub)slot in which the PUCCH is transmitted may be indicated to the UE, and the resource of the PUCCH within the (sub)slot is CCE occupied by PRI and / or DL-DCI can be given as an index of When the PUCCH serving cell pattern is set, the UE may use the reference UL BWP or reference subcarrier interval of the reference serving cell to apply the K1 offset. The derived (sub)slot may not be aligned with the (sub)slot boundary or symbol boundary of the PUCCH serving cell.

20 is a conceptual diagram illustrating a first embodiment of (sub)slot configuration when a reference subcarrier spacing in a reference serving cell is different from a subcarrier spacing in a PUCCH serving cell.

Referring to FIG. 20, "when the reference subcarrier spacing of the reference serving cell is 30 kHz, the subcarrier spacing of the PUCCH serving cell is 15 kHz, and a subslot having 7 symbols is set in the reference serving cell", the reference serving cell and In a PUCCH serving cell, (sub)slot boundaries and/or symbol boundaries may not be aligned. Two subslots in the reference serving cell may correspond to one subslot in the PUCCH serving cell.

21 is a conceptual diagram illustrating a second embodiment of (sub)slot configuration when a reference subcarrier spacing in a reference serving cell is different from a subcarrier spacing in a PUCCH serving cell.

Referring to FIG. 21, "when the reference subcarrier spacing of the reference serving cell is 15 kHz, the subcarrier spacing of the PUCCH serving cell is 30 kHz, and a subslot having 7 symbols is set in the reference serving cell", the reference serving cell and the PUCCH In a serving cell, a (sub)slot boundary and/or a symbol boundary may not be aligned. One subslot in the reference serving cell may correspond to two subslots in the PUCCH serving cell.

If transmission in two reference subslots of the reference serving cell is to be performed in one subslot of the PUCCH serving cell, the scheduler of the base station can predict the above transmission. Therefore, load balancing of PUCCH can be maintained. One reference subslot in the reference serving cell may correspond to two subslots in the PUCCH serving cell. As a first method, one subslot corresponding to one reference subslot among two subslots in a PUCCH serving cell may be defined in technical specifications. As a second method, the base station may dynamically indicate one subslot corresponding to one reference subslot among two subslots in the PUCCH serving cell to the terminal. The ratio of the numerology and/or the ratio of the length of the subslot may be set in various ways.

Method 3.2-8: One subslot corresponding to one reference subslot among two subslots in a PUCCH serving cell may be defined in technical specifications.

One reference subslot (or one reference slot) may correspond to 2 or 4 subslots in a PUCCH serving cell. The UE may select one subslot among 2 or 4 subslots in the PUCCH serving cell according to a method derived from technical specifications. For example, the terminal may select one subslot that is (most) early or (most) late in time from among the subslots. After selecting a subslot, the UE may determine a PUCCH resource (eg, one PUCCH resource) indicated by the PRI and/or CCE index included in the DCI. If one reference subslot (or one reference slot) corresponds to 2 or 4 subslots in the PUCCH serving cell, the UE bases 2 or 4 subslots in the PUCCH serving cell on the basis of information included in the DCI. A subslot among subslots may be selected.

Method 3.2-9: An index indicating a specific subslot among subslots of a PUCCH serving cell may be derived from DCI.

Method 3.2-10: In method 3.2-9, the DCI may include K1 and a (sub)slot offset.

Method 3.2-11 : In method 3.2-9, DCI may indicate a combination of K1 and (sub)slot offset. A combination of K1 and a (sub)slot offset may be indicated by one index. Alternatively, a separate field included in DCI may indicate a (sub)slot offset. In this case, the existing field of DCI may be extended. Or, a new field may be introduced into the DCI.

For example, since the ratio of the subcarrier spacing may be 2 or 4 times, the index of the subslot may be expressed with 1 bit or 2 bits. The above-described operation may be applied when the number of symbols (eg, 2 or 7) belonging to the subslot(s) configured in the terminal is all the same.

Method 3.2-12: When subslot(s) are configured in a PUCCH serving cell (or PUCCH cell group), the number of symbols belonging to the subslot(s) may be the same.

In case of “different lengths of subslot(s) in some PUCCH serving cells” or “case in which subslots are not configured in some PUCCH serving cells”, the ratio of subcarrier intervals and the ratio of subslots may be indicated more complicatedly. . If method 3.2-12 is not followed, the number of indexes required in DCI may significantly increase by applying method 3.2-9. In order not to increase the size of the DCI, the (sub)slot offset may be determined based on implicit information derived from the DCI. For example, a (sub)slot offset may be determined based on CCEs occupied by a PDCCH through which DCI is transmitted.

Method 3.2-13: In method 3.2-9, the smallest index or the largest index among indexes of CCEs to which DCI is mapped may be used to determine a (sub)slot offset.

For example, the maximum value or reference value of the ratio of the subcarrier spacing and/or the ratio of the number of symbols belonging to the subslot may be known to the terminal. The terminal may use the remainder of dividing the CCE index by the above-described maximum value or reference value as a (sub)slot offset.

3.2.4 How to apply delay time

BWPs of some serving cells belonging to the PUCCH cell group may be changed. Alternatively, some serving cells (eg, BWPs of some serving cells) may be activated or deactivated. Even when some serving cells (eg, BWPs of some serving cells) are inactivated, the UE can perform downlink communication and/or uplink communication in a predetermined BWP.

BWPs of some serving cells belonging to PUCCH serving cells may be changed. Some serving cells (eg, BWPs of some serving cells) may be activated or deactivated. When the PUCCH serving cell pattern is configured for the UE by RRC signaling, the UE cannot always transmit the PUCCH.

When the PUCCH serving cell pattern is configured, the corresponding PUCCH serving cell may be configured not to be deactivated. Alternatively, the BWP may be configured not to change to a specific BWP (eg, dormant BWP).

Method 3.2-14: When the PUCCH serving cell pattern is set to RRC signaling, it can be assumed that the UE can transmit the PUCCH in the PUCCH serving cell for the corresponding (sub)slot.

When the state or BWP of a PUCCH serving cell is limited in a specific (sub)slot, the scheduling of the base station may be restricted. A PUCCH serving cell pattern may be configured, and a complementary pattern may be known to the UE. If the UE cannot operate according to the PUCCH serving cell pattern, it may be desirable for the UE to use another serving cell.

Method 3.2-15: "When the PUCCH serving cell pattern is set to RRC signaling and it is determined that the UE cannot transmit the PUCCH in the PUCCH serving cell for the corresponding (sub) slot", the UE performs the PUCCH in the PCell, SpCell, or PSCell can transmit.

The UE can always select an activated serving cell. The selected serving cell may be PCell. The UE may transmit the PUCCH by utilizing an activated BWP among BWPs of the PCell. When the state of some PUCCH serving cells is changed, the UE may assume that the PUCCH serving cell(s) are activated or deactivated based on a predetermined (sub)slot. If the aforementioned reference (sub)slot is not clear, the UE may determine whether to follow the PUCCH serving cell pattern or use another serving cell.

When the state of the PUCCH serving cell changes, MAC CE may be received in slot n, and slot n + k may be defined in the technical specification. k is a value indicating a slot immediately after 3 ms from slot n + m in which the UE transmitted HARQ-ACK for MAC CE (for example, 3 + 1 when a subcarrier interval of 15 kHz is applied, and a subcarrier interval of 30 kHz is applied). In some cases, it may mean 6+1). According to technical specifications, when the state of the serving cell is changed, the terminal may perform various operations according to the state change. For example, for a serving cell that is deactivated, the UE transmits SRS, CSI, UL-SCH transmission, random access channel (RACH) transmission, PDCCH monitoring, PDSCH monitoring, and/or PUCCH transmission operation may not be performed. For example, for an activated serving cell, the UE performs an SRS transmission operation, a CSI transmission operation, a UL-SCH transmission operation, a RACH transmission operation, a PDCCH monitoring operation, a PDSCH monitoring operation, and/or a PUCCH transmission operation in the corresponding serving cell. can be done

The above-described operations may be performed no later than the minimum time defined in the technical standard. The above-described operations may be performed in a time not earlier than slot n+k. Roughly speaking, when the state of the PUCCH serving cell is changed, the terminal can perform operations according to the state change at a time that is neither too early nor too late. Reference time for operations according to state change may be determined according to technical standards.

When a PUCCH is transmitted in a PUCCH serving cell, an operation in a specific slot may be defined. A specific slot may be determined as slot n+k. According to technical specifications, a UE may not transmit a PUCCH in an inactive serving cell. When the PUCCH serving cell is inactivated, the UE may not transmit the PUCCH. When the deactivation timer of the PUCCH serving cell expires, the corresponding PUCCH serving cell may be deactivated. Even in this case, the terminal can perform the above-described operation in slot n+k. PUCCH transmission may start in an activated serving cell. In this case, the terminal may perform the above-described operation in slot n+k.

Method 3.2-16: When the state of the serving cell is changed, it can be assumed that the state of the serving cell is changed based on a predetermined slot determined by technical specifications.

22 is a conceptual diagram illustrating a first embodiment of a timing of changing a state of a serving cell.

Referring to FIG. 22, before and after a specific slot may not be clearly distinguished in the technical standard. According to method 3.2-16, a changed state (eg, updated state) of a serving cell may be applied from a predetermined slot (eg, slot n+k).

Meanwhile, even when the BWP is changed, a time when the UE cannot transmit the PUCCH may occur. For a serving cell whose BWP is changed, the terminal may not perform a transmission operation and/or a reception operation at a predetermined time. According to the technical specification, symbols from which DCI indicating a BWP change can be received may be limited to the first three symbols of a slot. The three symbols may be determined based on the serving cell in which the UE receives the PDCCH.

23 is a conceptual diagram illustrating a first embodiment of a method for changing a DL BWP.

Referring to FIG. 23, a time (eg, a fourth symbol) after a DCI reception time in a serving cell in which a PDSCH is received may be interpreted as t1. The start time of the slot in which the PDSCH is received may be interpreted as t2. The terminal may not perform a transmission operation and/or a reception operation for the corresponding serving cell in the period from t1 to t2.

24 is a conceptual diagram illustrating a first embodiment of a method for changing UL BWP.

Referring to FIG. 24, in the interval from the fourth symbol (eg, t1) in the serving cell in which the PUSCH is transmitted to the start time (eg, t2) of the slot in which the PUSCH is transmitted, the terminal is in the corresponding serving cell A transmission operation and/or a reception operation may not be performed.

When the BWP of the PUCCH serving cell is changed, the UE cannot transmit the PUCCH in the corresponding PUCCH serving cell for a predetermined time. In this situation, when the PUCCH serving cell pattern is indicated to the UE, it may be desirable for the base station not to change the corresponding BWP. However, the above-described operation may not always be performed. The reason is that the BWP change operation affects a plurality of terminals.

Alternatively, the UE may select another serving cell to transmit the PUCCH. A method applied when the state of the serving cell is changed may be reused. In one example, method 3.2-4 and/or method 3.2-5 may be applied. The UE may transmit the PUCCH in a separately configured reference serving cell and/or reference BWP. In another example, method 3.2-14 and/or method 3.2-15 may be applied. The UE may transmit PUCCH in SpCell.

3.2.5 How to perform repeated transmission

A UE may transmit PUCCH in two or more serving cells. If the PUCCH is repeatedly transmitted, the PUCCH serving cell pattern may be set or indicated to the UE by RRC signaling. The PUCCH serving cell pattern may be set or indicated by RRC signaling and/or DCI. PUCCH may be transmitted in one serving cell (eg, PCell or PUCCH serving cell) of one (sub)slot, and PUCCH may be transmitted in another serving cell of another (sub)slot.

Since different UL BWPs are activated in different serving cells, different numerologies may be applied. In the repetitive PUCCH transmission procedure, a case in which the subcarrier interval is changed may occur. In this case, as one method, repeated transmission of PUCCH may not be performed. Alternatively, repeated transmission of PUCCH is permitted, but repeated transmission of PUCCH may be performed in a restricted situation.

Method 3.2-17: Repeated transmission of PUCCH may be allowed when the numerologies of UL BWPs in two serving cells are the same.

3.2.6 Method of Indicating PUCCH Serving Cell Based on Field of DCI

A field for notifying a PUCCH serving cell (hereinafter referred to as "PUCCH serving cell field") may be included in the scheduling DCI. The size of the PUCCH serving cell field may be determined according to the number of cells that can be indicated as the PUCCH serving cell. For example, the size of the PUCCH Serving Cell field may be 1 bit or 2 bits. The UE may know the value corresponding to the index of the PUCCH serving cell. For example, an index of a PUCCH serving cell indicated by RRC signaling may correspond to a value of a PUCCH serving cell field in DCI.

Method 3.2-18: DCI format 1_0 may indicate that PUCCH is transmitted in PCell, SpCell, PSCell, or PUCCH-SCell.

DCI format 1_0, DCI format 1_1, and/or DCI format 1_2 may include the aforementioned field (eg, PUCCH serving cell field). Alternatively, DCI format 1_0, DCI format 1_1, and/or DCI format 1_2 may not include the aforementioned field. For example, DCI format 1_0 used as a fallback DCI may not include a PUCCH serving cell field. At this time, the UE may consider the PUCCH serving cell as PCell, SpCell, PSCell, or PUCCH-SCell. On the other hand, DCI format 1_1 or DCI format 1_2 may include a PUCCH serving cell field indicating a PUCCH serving cell.

Method 3.2-19: According to the search space set in which DCI format 1_0 is detected, the UE may perform different interpretations of the PUCCH serving cell.

In one example, the UE may interpret the PUCCH serving cell differently according to a search space set (eg, CSS or USS) in which DCI format 1_0 is searched. When DCI format 1_0 is detected in the CSS, the UE may regard the PUCCH serving cell as the PCell. When DCI format 1_0 is detected in the USS, the UE may regard the PUCCH serving cell as a serving cell configured for RRC signaling.

Some of the serving cell(s) that are considered PUCCH serving cells may be inactive. In this case, the UE may not transmit PUCCH in the inactive serving cell. When a PUCCH serving cell is indicated by a field of DCI (eg, a PUCCH serving cell field), since the base station knows the state of the serving cell (s), it may not be indicated that the inactive serving cell is used. . When determining a PUCCH serving cell according to a DCI field (eg, PUCCH serving cell field), the UE may assume that the corresponding serving cell (eg, PUCCH serving cell) is activated.

When DCI format 1_0 is used, according to method 3.2-18, the UE can transmit PUCCH on PCell, SpCell, PSCell, or PUCCH-SCell. Therefore, the corresponding serving cell may be activated.

Scheduling DCI (eg, DCI format 1_0, DCI format 1_1, DCI format 1_2) may indicate a PUCCH serving cell to the UE. When the non-fallback DCI field (eg, PUCCH serving cell field) has a first value, it may indicate that PUCCH is transmitted using SpCell. When the non-fallback DCI field (eg, PUCCH serving cell field) has the second value, this may indicate that PUCCH is transmitted using another serving cell. The fallback DCI may not include a field indicating a PUCCH serving cell (eg, a PUCCH serving cell field). In this case, the UE may transmit PUCCH in SpCell.

3.3 Retransmission of HARQ-ACK

UCI transmitted on PUCCH may have a low priority derived from eMBB or a high priority derived from URLLC. The base station may set or instruct the UE the priority of the PUCCH or PUSCH through which the UCI is transmitted using RRC signaling and/or scheduling DCI. The priority of PUCCH or PUSCH may be indicated by a priority index.

According to technical specifications, when a UE cannot simultaneously transmit two or more UL channels, it can select a UL channel having a high priority index and transmit the selected UL channel. When a PUCCH including LP UCI (eg, LP PUCCH) and a PUCCH including HP UCI (eg, HP PUCCH) overlap in some symbols of the time domain, the UE may transmit only HP PUCCH. That is, LP PUCCH may not be transmitted.

If the LP PUCCH that is not transmitted includes HARQ-ACK, the base station may perform scheduling for the HARQ process for the corresponding HARQ-ACK again. When the number of HARQ-ACK bits is large due to the application of frequency aggregation, many resources may be consumed for scheduling of corresponding HARQ processes. Therefore, a method for retransmitting an untransmitted PUCCH may be required.

In the UCI transmission procedure, at least one of HARQ-ACK (eg, HARQ codebook), CSI, or SR may be multiplexed on PUCCH or PUSCH, and the corresponding PUCCH or PUSCH may be transmitted. When retransmission of PUCCH is indicated, all or part of UCI (eg, UCI type) may be retransmitted.

Method 3.3-1: In the PUCCH retransmission procedure, all UCIs (eg, UCI types) may be retransmission targets regardless of the UCI type.

In the PUCCH retransmission procedure, a UCI encoding operation may not be newly performed. However, transmission opportunities for periodic CSI, quasi-persistent CSI, and/or positive SR may exist in the next period. Therefore, only the retransmission operation for HARQ-ACK can be allowed, and in this case, resources for the remaining retransmission operations can be saved.

Method 3.3-2: In the PUCCH retransmission procedure, only a retransmission operation for HARQ-ACK may be allowed.

In the retransmission procedure, priority according to traffic characteristics may be considered. Urgent data can be transmitted in the transmission procedure of URLLC traffic. A delay time according to PUCCH retransmission may be shorter than a time (eg, round trip time (RTT)) for receiving an HARQ-ACK for a rescheduled PDSCH. In this case, retransmission of PUCCH for URLLC traffic may be performed.

Method 3.3-3: The HARQ codebook for a PDSCH (eg, URLLC traffic) having a high priority index may be retransmitted.

Although eMBB traffic is not traffic that needs to be transmitted urgently, the resource efficiency obtained by not rescheduling the PDSCH (eg, eMBB traffic) can be significant. Accordingly, a retransmission operation for PDSCH (eg, eMBB traffic) may be supported.

Method 3.3-4: The HARQ codebook for PDSCH (eg, URLLC traffic and/or eMBB traffic) may be retransmitted regardless of the priority index.

3.3.1 Method of Instructing UE to Retransmit PUCCH

The PUCCH retransmission procedure may be performed based on one method of triggering the (enhanced) Type3 HARQ codebook (eg, Type3 'HARQ codebook). In this case, performing PUCCH retransmission in one of the trigger states may be configured for the UE. According to another method, a PUCCH including a separate indication other than the type 3 HARQ codebook may be retransmitted.

Method 3.3-5: The DCI may instruct the UE to retransmit the PUCCH.

Retransmission of PUCCH using DCI may be supported. In this case, the terminal can interpret the priority of the retransmitted HARQ codebook based on the priority index indicated by the DCI. The priority of the retransmitted HARQ codebook may be changed according to the priority index indicated by DCI. For example, a specific HARQ-ACK bit may have a low priority in an initial transmission procedure and may be regarded as having a high priority in a retransmission procedure. Conversely, a specific HARQ-ACK bit may have a high priority in the initial transmission procedure and may be regarded as having a low priority in the retransmission procedure.

A specific field of the DCI may indicate retransmission of the HARQ-ACK codebook (eg, HARQ-ACK information, HARQ-ACK bit). The UE can know the slot offset and/or resource index for PUCCH transmission using the information included in the DCI. That is, the UE may perform a PUCCH retransmission procedure, and PUCCH resources (eg, PUCCH format, number of PRBs, number of symbols, etc.) may be changed. If LP UCI is canceled, at least HARQ-ACK may be retransmitted.

Method 3.3-6: In method 3.3-5, one field in DCI may be utilized to indicate retransmission of PUCCH.

For example, a new feedback indicator (NFI) in DCI may be used to indicate retransmission of PUCCH. According to the technical specifications, NFI can be utilized in unlicensed bands. When the NFI field has a first value, the UE can generate an HARQ codebook for one PDSCH group and transmit the HARQ codebook on the PUCCH. When the NFI field has a second value, the UE can generate HARQ codebooks for two PDSCH groups and transmit the HARQ codebooks on PUCCH. The above-described operation may be applied to a licensed band.

For example, a field triggering a type 3 HARQ codebook to indicate retransmission of PUCCH may be reused. In another example, a field of DCI may be extended, and the extended field may include two or more bits. The UE may select one of the type 3' HARQ codebooks according to the value of the corresponding field in the DCI. Existing fields included in the DCI (eg, a HARQ process number (HPN) field and/or a modulation and coding scheme (MCS) field) may be reinterpreted. In this case, the DCI may be limited to a non-scheduling DCI that does not schedule TB. Alternatively, DCI may support a scheduling operation of TB and a trigger operation of type 3' HARQ codebook. In this case, a new field for triggering one of type 3' HARQ codebooks may be introduced into DCI. Therefore, it may be preferable that the above-described DCI is limited to a non-scheduling DCI that does not schedule TB.

To determine whether the DCI is a scheduling DCI or a non-scheduling DCI, the UE can check whether a field of the DCI represents a frequency resource valid or invalid. If the DCI indicates an invalid frequency resource (eg, frequency domain resource allocation (FDRA)) to the UE, the UE may regard the corresponding DCI as a non-scheduling DCI. For example, FDRA included in the non-scheduling DCI may be represented as 0.

In the DCI format, the length of a specific field may be different. For example, in DCI format 1_1 and DCI format 1_0, the HPN field may be set to 4 bits, and in DCI format 1_2, the HPN field may be set to less than 4 bits. For example, in DCI format 1_2, the HPN field may be set to 0, 1, 2, or 3 bits.

Method 3.3-7: When the index (or code point) derived by applying the same rule to fields having different lengths in the DCI format has the same value, the terminal can generate the same type 3' HARQ codebook there is.

In the HPN field of DCI format 1_2, a known bit may be added to the MSB or LSB, and in this case, the size of the HPN field may be interpreted as 4 bits. For example, 0 may be appended to the MSB in the value indicated by the HPN field, and in this case, the value of the HPN field may be interpreted as a binary number read from the LSB. If the HPN field of DCI format 1_1 and the HPN field of DCI format 1_2 have the same value, the terminal can interpret that the same type 3' HARQ codebook is always triggered. For example, the MCS field included in the DCI format may always be set to 5 bits regardless of the DCI format.

Method 3.3-8: DCI format configuration information may indicate a method of generating a type 3' HARQ codebook.

HARQ codebooks derived from the same field included in each of DCI format 1_1 and DCI format 1_2 may be set independently of each other. In one example, the terminal may assume that the method of interpreting the HPN field is different for each DCI format. A serving cell through which PUCCH is transmitted (eg, a PUCCH serving cell) may be changed. The index of the PUCCH serving cell may be indicated from the DCI field. When two serving cells are involved, a serving cell through which PUCCH is transmitted may be derived from a field having a size of 1 bit in DCI.

As another method of performing Method 3.3-5 or Method 3.3-6, a new field unrelated to the Type 3 HARQ codebook or the Type 3' HARQ codebook may be introduced into the DCI. When a field (eg, a new field) included in the DCI has a first value, it may instruct the terminal to transmit HARQ codebook 1 that has failed to transmit or HARQ codebook 1 that is scheduled to be transmitted. When a field (eg, a new field) included in the DCI has a second value, this may indicate that HARQ codebook 1 is not transmitted to the terminal. Here, transmission failure refers to "failure to access a channel in an unlicensed band" and/or "transmission being dropped due to a comparison result of a priority field (priority index) allocated to scheduling of data in a licensed band or unlicensed band" can mean

The DCI received by the UE may not be the scheduling DCI. In one example, DCI may include a field indicating whether to multiplex HARQ codebook 2 having a different priority index. In another example, RRC signaling may indicate whether to multiplex HARQ codebook 2 having a different priority index, and in this case, DCI may indicate whether to transmit HARQ codebook 1. When multiplexing of HARQ codebook 2 is indicated (eg, when UCIs having different priorities are multiplexed), HARQ codebook 1 and HARQ codebook 2 may be concatenated according to a priority index. When it is indicated that HARQ codebook 2 is not multiplexed (eg, "when RRC signaling indicating multiplexing of UCIs having different priorities is not received" or "RRC signaling indicates that UCIs having different priorities are In case of indicating non-multiplexing"), the terminal may select an HARQ codebook having a high priority index and transmit the selected HARQ codebook.

Method 3.3-9: One field included in the DCI format indicating PUCCH retransmission may instruct the UE to multiplex HARQ-ACKs having different priorities.

DCI indicating PUCCH retransmission may include time resource information for PUCCH transmission. The first PUCCH through which HARQ codebook 1 is transmitted may be indicated to the terminal, and the time point 2 (eg, the first symbol of the PUCCH resource) at which HARQ codebook 1 is transmitted is the first PUCCH resource through which HARQ codebook 1 is transmitted (eg, the first symbol of the PUCCH resource). , the first symbol of the first PUCCH resource) may not be earlier than time 1. Therefore, time point 1 may occur before time point 2. Alternatively, time 1 and time 2 may occur simultaneously.

PUCCH resource 1 for retransmission may be indicated to the UE, and the UE may perform a multiplexing procedure for a PUCCH for PUCCH resource 1 and a different PUCCH and/or PUSCH. For example, PUCCH resource 1 may temporally overlap with PUCCH resource 2 corresponding to HARQ codebook 2. In this case, the UE can multiplex HARQ-ACK bits belonging to HARQ codebook 1 and HARQ codebook 2 on one PUCCH resource 3. The UE can check whether there is another UL transmission temporally overlapping with the UL transmission in PUCCH resource 3. The UE may perform UL transmission in separate UL transmission or PUCCH resource 3. The terminal may perform the same encoding operation or different encoding operations according to the priority index. Multiplexed HARQ codebooks (eg, HARQ-ACK bits, HARQ-ACK information) may have the same priority index.

If it is assumed that the PUCCH on which HARQ codebook 1 is to be transmitted has priority index 0, the DCI indicating transmission of HARQ codebook 2 may include information indicating priority index 0 or priority index 1. When Method 3.3-5 and/or Method 3.3-6 are applied, the UE can generate one codeword by performing the same encoding operation on two HARQ codebooks having the same priority index 0. If the priority indices of the two HARQ codebooks are different from each other, the terminal can generate two codewords by performing different encoding operations on the two HARQ codebooks. HARQ codebook 1 and HARQ codebook 2 may have different priority indices.

If DCI instructs retransmission of HARQ codebook 1, the terminal can retransmit up to m HARQ codebooks. Here, m may be 1. m=2 may not be supported. When the type 2 HARQ codebook is configured in the UE, the DCI may include a downlink assignment index (DAI) field. C (Counter) -DAI and T (total) -DAI may be indicated. C-DAI and T-DAI can be used to derive the size of the type 2 HARQ codebook. As in Method 3.3-5, in order for DCI 2 to indicate retransmission of PUCCH (eg, retransmission of HARQ codebook 1), both the size of HARQ codebook 1 and the size of HARQ codebook 2 can be known to the terminal.

When DTX occurs in the terminal, the corresponding terminal may not be able to detect DCI 1. In this case, the UE may not know that HARQ codebook 1 needs to be transmitted on PUCCH. At this time, the base station may instruct the terminal to transmit HARQ codebook 2. In order to transmit HARQ codebook 1 and HARQ codebook 2 on the same PUCCH, information necessary to derive the size of HARQ codebook 1 may be provided to the terminal through DCI 2. DCI may be DL-DCI or UL-DCI.

Method 3.3-10: DL-DCI may include two or more (C-DAI, T-DAI).

Method 3.3-11: A DL-DCI may include two or more T-DAIs and one or more C-DAIs.

Method 3.3-12: UL-DCI may include two or more T-DAIs.

If the DCI contains two (C-DAI, T-DAI)s (or two T-DAIs), two (C-DAI, T-DAI)s (or two T-DAIs) Each may correspond to information about HARQ codebook 1 and HARQ codebook 2. If the DCI includes one C-DAI, one C-DAI may correspond to HARQ codebook 2. The concatenation order of DAIs can be specified in technical specifications. The concatenation order of DAIs may correspond to "order of HARQ codebook 2 → HARQ codebook 1" or "order of HARQ codebook 1 → HARQ codebook 2". Initial transmission of HP UCI and LP UCI may be performed on PUCCH, and LP UCI (eg, HARQ-ACK) may be retransmitted on PUCCH. In this case, the number of HARQ codebooks may be three. In this case, the DCI may include three (C-DAI, T-DAI) and/or three T-DAIs.

Meanwhile, in the HARQ codebook retransmission procedure, it may be preferable that the base station does not schedule a new DL-SCH using the HARQ process for the corresponding HARQ codebook. The above-described operation in the transmission procedure of the SPS PDSCH may not be guaranteed. The HPN for the SPS PDSCH may be defined based on a predetermined function. The HARQ-ACK bit for the HPN associated with the activated SPS may be included in the HARQ codebook of the UE. Here, the HARQ codebook may be retransmitted. The retransmission procedure of the HARQ codebook may be affected by "whether information words and codewords are updated" and/or "reference timing of update".

In the transmission procedure of the HARQ codebook, HARQ-ACK bits may be referred to as an information word, and the terminal may generate a codeword by performing an encoding operation on the information word. The terminal may generate a symbol by performing a modulation operation on the codeword. When retransmission of the HARQ codebook is instructed to the UE, the UE may not generate a new HARQ codebook and may perform part of the PUCCH (or PUSCH) transmission procedure again.

Method 3.3-13: When retransmission of the HARQ codebook (or PUCCH) is instructed to the UE, the UE may update the HARQ-ACK bits (eg, information word) constituting the HARQ codebook.

The terminal may update the information word and generate a code word. The terminal may generate the HARQ codebook in the same way using the HARQ-ACK bit for the same HARQ process ID (or HPN) at a predetermined time. In this case, a new HARQ-ACK bit for the same HPN may be generated. For example, considering SPS, HARQ-ACK can be replaced with new information.

According to method 3.3-13, the predetermined time may be a boundary, and if retransmission of the HARQ codebook is instructed to the terminal before the predetermined time, the terminal may not renew the HARQ-ACK of the corresponding HPN, and the HARQ codebook may not be updated at the predetermined time or after the predetermined time. When retransmission of the codebook is instructed to the terminal, the terminal may renew the HARQ-ACK of the corresponding HPN. The predetermined time may be determined based on a mathematical formula specified in technical standards. The base station may set or instruct the terminal using RRC signaling in consideration of the terminal capability of the parameter (s) necessary for calculating the corresponding equation. Alternatively, parameter(s) required to calculate the corresponding equation may be derived from the BWP.

Method 3.3-14: In method 3.3-13, a predetermined time (eg, time boundary) for updating the information word may be introduced.

If the terminal fails to transmit the HARQ-ACK to the base station, it may not be desirable to replace the untransmitted HARQ-ACK with a new HARQ-ACK. Therefore, it may be desirable to keep the information word as it is.

Method 3.3-15: When retransmission of the HARQ codebook (or PUCCH) is instructed to the terminal, the terminal may maintain the HARQ-ACK bits (eg, information word) constituting the HARQ codebook at the same value, and the codeword can be updated.

The terminal may maintain the information word as it is and may update the code word. The code rate applied to the encoding operation may be a code rate applied in a new PUCCH resource indicated for retransmission to the UE.

The terminal may not know when to receive the retransmission instruction of the HARQ codebook (or PUCCH). Therefore, when the terminal stores the information word as it is, a separate memory may be required in the terminal. The terminal may store the information word for a predetermined period of time. The maximum value of the predetermined time may be determined according to the terminal capability. Alternatively, the base station may set or instruct the terminal a maximum value of a predetermined time using RRC signaling. After a predetermined time elapses, the terminal may not maintain the information word, and the base station may not request retransmission of the HARQ codebook (or PUCCH) from the terminal.

Method 3.3-16: After a predetermined time elapses, the UE may not perform retransmission of the HARQ codebook (or PUCCH).

When retransmission of the HARQ codebook is performed, the maximum number of HARQ codebooks (eg, retransmission HARQ codebooks) may be derived. This is because the memory of the terminal is additionally occupied when the terminal stores the information word and/or the codeword. The maximum number of HARQ codebooks capable of retransmission may be limited in consideration of UE capabilities.

Method 3.3-17: The base station may set or instruct the terminal the maximum number of HARQ codebooks (or PUCCHs) that can be retransmitted through RRC signaling.

Alternatively, the maximum number of HARQ codebooks (or PUCCHs) capable of retransmission may be defined in technical specifications. For example, the maximum number of HARQ codebooks (or PUCCHs) that can be retransmitted may be 1.

Method 3.3-18: The maximum number of HARQ codebooks (or PUCCHs) that can be retransmitted by the UE may be defined in technical specifications.

The amount and number of HARQ codebooks may be determined, and the maximum number of HARQ-ACK bits that can be retransmitted may be limited according to UE capabilities. The maximum number of HARQ-ACK bits that can be retransmitted may be indicated or configured in the terminal. In addition, the maximum holding time of the maximum number of HARQ-ACK bits that can be retransmitted may be instructed or configured in the terminal.

When the DCI instructing retransmission of the HARQ codebook is the scheduling DCI, the UE may perform PUCCH retransmission based on the field included in the DCI. In this case, the retransmitted PUCCH may be different from the HARQ-ACK for the PDSCH scheduled by DCI. A UE can derive two or more PUCCHs from one DCI. DL-DCI may schedule TB(s), HARQ-ACK bit(s) for TB(s) may be derived, and PUCCH 0 may be transmitted. In addition, one field of DL-DCI may indicate that a separate PUCCH 1 is transmitted. Alternatively, one field of DL-DCI may indicate that HARQ codebooks retransmitted on the same PUCCH 0 are multiplexed.

A time resource for transmitting PUCCH 0 may be indicated to the UE as an offset 0 of a (sub)slot in DL-DCI, and a time resource for retransmission may be indicated to the UE as an offset 1 of a (sub)slot.

When the DCI instructing retransmission is a non-scheduling DCI, only PUCCH 1 may be indicated to the UE. In this case, offset 0 may mean the time of PUCCH 0 in which the retransmission HARQ codebook is transmitted, and offset 1 may be used to specify the retransmission HARQ codebook. In an embodiment, the retransmission HARQ codebook may mean a retransmitted HARQ codebook, and the first transmission HARQ codebook may mean a first transmitted HARQ codebook.

Offset 0 is the (sub)slot and PUCCH 0 in which a DCI indicating retransmission (eg, when non-scheduling DCI indicates retransmission) or a PDSCH (eg, when scheduling DCI indicates retransmission) is received This may indicate a difference between (sub)slots being transmitted. Offset 1 can be interpreted based on the method(s) below.

Method 3.3-19: Offset 1 may be derived from a difference between a (sub)slot in which PUCCH 0 is transmitted and a (sub)slot in which PUCCH 1 is initially intended to be transmitted.

Method 3.3-20: Offset 1 may be derived from a difference between a (sub)slot in which PDCCH is received and a (sub)slot in which PUCCH 1 is transmitted.

In one example, offset 1 may not accurately indicate the (sub)slot in which the UE intended to transmit PUCCH 1. The UE may derive a time window from offset 1, and PUCCH 1 may be the last or first PUCCH generated in the time window. This can be applied in both method 3.3-17 and method 3.3-18.

If the UE fails to transmit PUCCH 1, the base station may trigger the UE to transmit PUCCH 1 (or HARQ codebook 1) in additional DL-DCI. Since there may be several PUCCHs that the UE failed to transmit, the base station may instruct the UE which PUCCH (or HARQ codebook) is to be retransmitted among the plurality of PUCCHs. In this case, the base station may specify PUCCH 1 in the form of offset 1 to the terminal. It can be assumed that the UE transmits one PUCCH 1 (or HARQ codebook 1) in the corresponding (sub)slot.

Method 3.3-21: The UE can generate one HARQ-ACK bit stream by concatenating retransmission HARQ codebook 1 and supertransmission HARQ codebook 0, and can perform an encoding operation on one HARQ-ACK bit stream.

The UE may deploy HARQ codebook 0 (eg, supertransmission HARQ codebook) first, and may deploy HARQ codebook 1 (eg, retransmission HARQ codebook) after HARQ codebook 0. According to the above-described operation, one HARQ-ACK bit string can be generated. After that, if necessary, the UE may consider multiplexing with a HARQ-ACK bit sequence having a different priority index.

25 is a conceptual diagram illustrating a first embodiment of a method of interpreting offset 1 indicating retransmission of a PUCCH.

Referring to FIG. 25 , offset 1 may be offset 1 according to method 3.3-19. Offset 1 may be a difference between a (sub)slot in which PUCCH 1 is initially transmitted and a (sub)slot in which PUCCH 0 is transmitted.

26 is a conceptual diagram illustrating a second embodiment of a method of interpreting offset 1 indicating retransmission of a PUCCH.

Referring to FIG. 26 , offset 1 may be offset 1 according to method 3.3-20. Offset 1 may be a difference between a (sub)slot in which PDCCH is received and a (sub)slot in which PUCCH 1 is transmitted.

27 is a conceptual diagram illustrating a third embodiment of a method of interpreting offset 1 indicating retransmission of a PUCCH.

Referring to FIG. 27 , offset 1 may be offset 1 according to method 3.3-20. Offset 1 may be a difference between a (sub)slot in which PDCCH is received and a (sub)slot in which PUCCH 1 is transmitted.

In the above-described embodiments, the UE may transmit PUCCH 0 based on offset 0. Retransmission HARQ codebook 1 can be concatenated with HARQ codebook 0 according to method 3.3-21. According to method 3.3-17 or method 3.3-18, the terminal can store all untransmitted HARQ codebooks. To support this operation, additional memory or storage space may be required in the terminal. Alternatively, the terminal may regenerate HARQ codebook 1 triggered to retransmit. The procedure of arranging HPNs in a predetermined order in the configured serving cell may be performed again. Since this operation does not require the terminal to decode an additional TB, the time required for the above operation may not be large.

The maximum delay time for transmission of TB for URLLC traffic can be defined. In this case, the maximum storage time in the terminal may be defined. The UE may assume that PUCCH 1 (or HARQ codebook 1) is not retransmitted after the maximum storage time. The maximum number of HARQ codebooks that can be stored by the terminal may be limited.

Method 3.3-22: The base station may set or instruct the terminal the maximum time for retransmitting PUCCH 1 (or HARQ codebook 1) through RRC signaling.

Method 3.3-23: The base station may set or instruct the terminal the maximum number of retransmittable PUCCH 1 (or HARQ codebook 1) through RRC signaling.

Method 3.3-24: The maximum time during which PUCCH 1 (or HARQ codebook 1) is retransmitted may be determined according to UE capabilities. Therefore, the UE may transmit a UE capability report including a configuration variable indicating the maximum time for retransmission of PUCCH 1 (or HARQ codebook 1) to the base station. The UE capability report may be transmitted to the base station by RRC signaling.

The base station may receive a UE capability report from the UE, and may check a configuration variable indicating a maximum time during which PUCCH 1 (or HARQ codebook 1) included in the UE capability report is retransmitted. The base station may perform scheduling according to a combination of the above-described method(s) in consideration of the confirmed configuration variable. "When the size (eg, number of HARQ-ACK bits) of PUCCH 1 (or HARQ codebook 1) that the UE wants to retransmit exceeds the maximum size" or "PUCCH 1 (or HARQ codebook 1) is retransmitted If the maximum time has passed", it can be assumed that the terminal does not receive the above-mentioned indication from the base station.

When PUCCH 1 (or HARQ codebook 1) is retransmitted, the UE may not store information on HARQ codebook 1 included in PUCCH 1. The above operation may be explicitly instructed by the base station, and the terminal may not store HARQ codebook 1 based on the explicit indication of the base station. When a new HARQ codebook is generated, HARQ-ACK bits (or HARQ codebooks) may be replaced with new HARQ codebooks in the order stored the longest.

While retransmission of PUCCH (or HARQ codebook) is instructed to the UE, BWP may be changed. The DL BWP of the serving cell in which the PDSCH is received may be changed. Alternatively, if the UL BWP of the serving cell through which PUCCH (or HARQ codebook) is transmitted is changed, HARQ-ACK may not be reported to the base station. For example, in the case of a Type 1 HARQ codebook, an HARQ-ACK for a PDSCH candidate received before the BWP is changed may not be included in the Type 1 HARQ codebook. For example, in the case of a type 2 HARQ codebook, all HARQ-ACKs for a serving cell whose BWP is changed may not be included in the type 2 HARQ codebook.

In the retransmission procedure of PUCCH (or HARQ codebook), the above-described method may be modified and applied. When the BWP is changed, in order not to report the HARQ-ACK generated before the BWP change, the terminal may not store the corresponding HARQ codebook. After BWP is instructed to change, the UE may not perform PUCCH retransmission. This operation may be performed based on a combination of method(s) below.

Method 3.3-25: "After the DL BWP of the serving cell on which the PDSCH is received is changed" or "After the UL BWP of the serving cell on which the PUCCH is transmitted is changed", PUCCH (or HARQ codebook) retransmission is instructed or set to the UE It may not be.

Method 3.3-26: After BWP change is indicated, the UE may perform retransmission of PUCCH (or HARQ codebook). However, the UE may not expect retransmission of the aforementioned PUCCH (or HARQ codebook).

In another example, HARQ-ACK bit(s) received before the slot where the change in BWP was triggered, HARQ-ACK bit(s) received in the slot where the change in BWP was triggered, and after the slot where the change in BWP was triggered. HARQ-ACK bit(s) received in may be distinguished. After the BWP is changed, the UE may regenerate the HARQ codebook with only the corresponding HARQ-ACK bits. In this case, the terminal may additionally perform subsequent procedures of the above-described procedure.

Method 3.3-27: When retransmission of the PUCCH (or HARQ codebook) is instructed to the UE, the UE "after the DL BWP of the serving cell on which the PDSCH is received is changed" or "after the UL BWP of the serving cell on which the PUCCH is transmitted is changed A new HARQ codebook can be generated only with HARQ-ACKs generated in ", and the HARQ codebook can be retransmitted. In this case, the size of the HARQ codebook retransmitted by the terminal may be reduced.

3.3.2 When UCI repeats are set and/or indicated

The UE may repeatedly transmit UCI. When UCI is transmitted in PUCCH, the base station may instruct or configure the number of repetitions of UCI (eg, PUCCH) to the terminal using RRC signaling. The number of repetitions of UCI may be determined for each PUCCH format. Alternatively, the number of repetitions of UCI may be determined as part of PUCCH resources. In the former case, the repetition number of PUCCH (eg, UCI) may be determined by RRC signaling. In the latter case, the repetition number of the PUCCH may be derived by DCI and/or RRC signaling allocating the PUCCH.

If the UE is instructed to transmit the UCI twice or more repeatedly, retransmission of the PUCCH may be considered. A PUCCH including only one UCI type (eg, SR, CSI, or HARQ-ACK) may be repeatedly transmitted. For repeated transmission of two or more UCI types, one UCI type may be repeatedly transmitted according to the order defined in the technical standard (eg, HARQ-ACK > SR > CSI). The number of PUCCH repetitions may be determined by the format of the PUCCH. In RRC signaling, one value for each PUCCH format may be set as the number of repetitions.

Alternatively, the repetition number of PUCCH may be known by PUCCH resource configuration. One value for each PUCCH resource may be set as the number of PUCCH repetitions. If one value is set as the number of repetitions of PUCCH for each PUCCH format, it may mean that the number of repetitions is set in each PUCCH resource and PUCCH format. In this case, the terminal may utilize one of the different values according to a predetermined rule. For example, when one value is set for each PUCCH resource, the UE may interpret the value associated with the PUCCH resource as the number of repetitions even if the associated value is indicated in the PUCCH format.

When retransmission of a type 3 HARQ codebook or HARQ-ACK is triggered in the same slot, another PUCCH may not be transmitted and only one PUCCH may be transmitted. Even if the repeated transmission procedure of PUCCH 1 including HARQ codebook 1 is not ended, the base station may instruct the terminal to retransmit HARQ codebook 1. In this case, the first transmission HARQ codebook 2 may be transmitted on the retransmitted PUCCH 2 (or PUSCH), HARQ codebook 2 and HARQ codebook 1 may be concatenated, and the concatenated HARQ codebooks may be repeatedly transmitted. For example, the number of repetitions of PUCCH 1 may be set to N1, and the number of repetitions of PUCCH 2 may be set to N2. HARQ codebook 1 can be repeated as many as N1 + N2 at most. Because of the drop in slot pattern, slot format, and/or priority index, HARQ codebook 1 can be transmitted less than N1 + N2.

If the number of repeatedly transmitted HARQ codebook 1 is sufficient, it may be preferable that the terminal does not transmit HARQ codebook 1 any more. To support this operation, the number of repetitions can be counted as the number of transmissions of the HARQ codebook.

Method 3.3-28: The number of HARQ codebook transmissions (eg, the number of repetitions) is the sum of the number of HARQ codebooks transmitted on PUCCH 1, the sum of the number of HARQ codebooks transmitted on PUCCH 2, or “the number of HARQ codebooks transmitted on PUCCH 1 It may be "the sum of the number of HARQ codebooks + the sum of the number of HARQ codebooks transmitted on PUCCH 2".

Method 3.3-29: When the number of transmissions of the HARQ codebook is greater than or equal to the preset maximum number, the UE may not transmit PUCCH 1.

If the number of transmissions of HARQ codebook 1 (eg, N1) is set for the UE, the UE can transmit HARQ codebook 1 in PUCCH 1 and PUCCH 2, and the number of transmissions of PUCCH 1 is N1 (eg, the maximum number of times) may be smaller than

28 is a conceptual diagram illustrating a first embodiment of a method of transmitting a PUCCH based on the number of repetitions of an HARQ codebook.

Referring to FIG. 28 , N1 may be set to 4 and N2 may be set to 2. In the initial transmission procedure of PUCCH 1 (or HARQ codebook 1), the UE may consider a case in which PUCCH 1 cannot be transmitted due to a low priority index. The UE may receive DCI indicating retransmission and may perform an initial transmission procedure for HARQ codebook 1 in PUCCH 2. If HARQ codebook 1 is transmitted 4 times on PUCCH 1 and PUCCH 2, the terminal may not need to transmit HARQ codebook 1 any more. Accordingly, the UE may not perform the 4th transmission of PUCCH 1. In the case of PUCCH 2, HARQ codebook 1 and HARQ codebook 2 may be concatenated. If necessary, HARQ codebook 1 and HARQ codebook 2 may be composed of one codeword. PUCCH 2 may be transmitted as many times as the number of repetitions of HARQ codebook 2. Even when HARQ codebook 1 is transmitted as many times as the number of repetitions, transmission of PUCCH 2 (eg, HARQ codebook 2) may not be dropped.

PUCCH 1 may not include only HARQ codebook 1, and HARQ codebook 1 may be multiplexed on another HARQ codebook 0 and PUCCH 1. Even in this case, method 3.3-28 or method 3.3-29 can be applied, and the minimum transmission that satisfies the number of repetitions of HARQ codebook 1 can be performed. Here, since the PUCCH is retransmitted, when HARQ codebook 0 and/or HARQ codebook 2 are involved, the actual number of transmissions of HARQ codebook 1 may be greater than the required number of repetitions. Alternatively, when retransmission of HARQ codebook 1 is instructed to the UE, PUCCH 1 may not be transmitted.

Method 3.3-30: The UE may receive DCI indicating retransmission of HARQ codebook 1, may drop PUCCH 1 after a predetermined processing time, and may transmit HARQ codebook 1 on PUCCH 2.

A polar code or a Reed Muller code may be applied to HARQ codebook 1. In this case, it may be desirable to perform a soft combining operation (eg, a chase combining operation). Therefore, the UE may newly calculate the number of PUCCH repetitions and transmit PUCCH 2.

29 is a conceptual diagram illustrating a first embodiment of a method of canceling repeated transmission of PUCCH.

Referring to FIG. 29, during transmission of PUCCH 1, retransmission of HARQ codebook 1 on PUCCH 2 may be instructed to the UE. The UE may receive DCI and may expect not to transmit PUCCH 1 after the DCI processing time has elapsed.

3.3.3 Multiplexing method of retransmitted PUCCHs (or HARQ codebooks)

If a plurality of PUCCHs overlap in the same symbol, all or some of the UCIs for the plurality of PUCCHs may be multiplexed, and the multiplexed UCIs may be transmitted on the PUCCH. When retransmission of the HARQ codebook is indicated, a retransmission procedure of all or part of the HARQ codebook may be required. The DCI field may indicate retransmission of the HARQ codebook on PUCCH in a specific slot. "When the slot in which the PUCCH is transmitted is the same and DCIs indicating retransmission are limited to the maximum number" or "the slot in which the PUCCH is transmitted is the same and two or more DCIs indicating retransmission are received" may occur .

Method 3.3-31: In the PUCCH transmission procedure, the maximum number of retransmission HARQ codebooks may be limited to K.

In one example, K may be 1. In another example, the base station may instruct or set the value of K, which is set in consideration of the capabilities of the terminal, to the terminal using RRC signaling.

Method 3.3-32: In method 3.3-31, the UE may assume that DCIs are not received so that K>1.

Method 3.3-33: In method 3.3-31, if DCIs are received so that K>1, the UE can select one DCI from among the corresponding DCIs, and assume that only one HARQ codebook is retransmitted based on the selected DCI. can

The selected DCI may be the first DCI or the last DCI received by the terminal, and retransmission of the HARQ codebook may be performed based on the selected DCI.

Method 3.3-34: In Method 3.3-31, DCIs indicating retransmission may all indicate retransmission of the same HARQ codebook.

The (sub)slot offset for the retransmission HARQ codebook may be indicated by l, and the (sub)slot associated with the retransmission HARQ codebook may be calculated from slot n where the DCI is received. The retransmission HARQ codebook may be determined as the HARQ codebook intended to be transmitted in (sub)slot m=n-l. The UE may retransmit the HARQ codebook in (sub)slot n+k. The (sub)slot offset k may be derived from the HARQ-ACK feedback timing field indicated in DCI. According to method 3.3-34, in order to indicate the same HARQ codebook, all (sub)slot m indicated by the DCI received from the terminal may be assumed to be the same.

Method 3.3-35: When retransmission of two or more HARQ codebooks is allowed, the terminal can generate one HARQ codebook by concatenating two or more HARQ codebooks.

Considering the case where DCI i is instructed to retransmit HARQ codebook i, DCI may be received by the terminal in the order of i. Here i may be a natural number. In one example, HARQ codebooks can be concatenated in the receiving order of DCIs triggering retransmission. HARQ codebook 1 may be placed first, and HARQ codebook 2 may be placed after HARQ codebook 1.

When the UE transmits PUCCH (or PUSCH) in (sub)slot n+k, the initial transmission HARQ codebook 0 and the retransmission HARQ codebook may be sequentially concatenated. Here, the retransmission HARQ codebook may be concatenated in the order of HARQ codebook 1 and HARQ codebook 2.

When two priority indices are indicated to the UE, the UE can generate a HARQ codebook for each same priority index, and then generate HARQ-ACK bit streams for different priority indices.

3.3.4 Examples

HARQ codebook A including initial HARQ-ACK bits, SPS HARQ-ACK bits, and retransmission HARQ-ACK bits can be considered. The first HARQ-ACK bits may mean HARQ-ACK bits included in the supertransmission HARQ-ACK codebook. Here, the arrangement method of SPS HARQ-ACK bits will be described in detail in Sections 3.4 and 3.4.1. In the embodiment, it may be assumed that the UE transmits PUCCH (or PUSCH) including HARQ codebook A in (sub)slot n + k.

Considering that the terminal receives the retransmission indication of HARQ codebook A again, all or part of HARQ codebook A may be retransmitted on PUCCH (or PUSCH) in (sub)slot y. (Sub)slot y may be located after (sub)slot n+k in the time domain. All of HARQ codebook A can be retransmitted, and the HARQ-ACK bit stream for HARQ codebook A can be concatenated with other HARQ-ACK bit streams. Here, the HARQ-ACK bit stream may be an initial transmission HARQ codebook or a retransmission HARQ codebook transmitted in (sub)slot y.

Method 3.3-36: The first HARQ codebook constituting the HARQ codebook A, the SPS HARQ codebook, and the retransmission HARQ codebook may be (re)transmitted.

In another method, part of HARQ codebook A may be retransmitted. In one example, in the process of generating the super transmission SPS HARQ codebook transmitted in (sub)slot y, SPS HARQ-ACK bits belonging to HARQ codebook A may be included in the SPS HARQ codebook. Therefore, in order to prevent redundant transmission, the SPS HARQ codebook constituting HARQ codebook A may not be retransmitted.

Method 3.3-37: The SPS HARQ codebook constituting HARQ codebook A may not be retransmitted.

In another example, there may be no supertransmission SPS HARQ codebook in (sub)slot y. In this case, it is preferable to retransmit the SPS HARQ-ACK bits included in HARQ codebook A. Accordingly, whether or not to retransmit the SPS HARQ-ACK bits included in the HARQ codebook A may be determined according to whether or not the supertransmission SPS HARQ codebook exists in (sub)slot y.

Method 3.3-38: When a supertransmission SPS HARQ codebook exists in (sub)slot y, SPS HARQ-ACK bits included in HARQ codebook A may not be retransmitted. If there is no SPS HARQ codebook for initial transmission in (sub)slot y, SPS HARQ-ACK bits included in HARQ codebook A may be retransmitted.

When the SPS HARQ-ACK bits included in HARQ codebook A are retransmitted, the HARQ codebook may be composed of the SPS HARQ-ACK bits included in HARQ codebook A. According to another method, the SPS HARQ-ACK bits may not be included in HARQ codebook A, and may be regarded as a super transmission SPS HARQ codebook in (sub)slot y. In this case, the retransmission SPS HARQ codebook may be placed first, and part of the HARQ codebook A composed of the remaining HARQ-ACK bits may be placed after the retransmission SPS HARQ codebook. In order to prevent redundant transmission of the retransmission HARQ codebook among the HARQ-ACK bits constituting the HARQ codebook A, the retransmission HARQ codebook may not be retransmitted. In this case, HARQ codebook A may be composed of the first HARQ codebook and / or SPS HARQ-ACK bits.

Method 3.3-39: Retransmission HARQ codebook constituting HARQ codebook A may not be retransmitted.

When two or more priority indexes are considered, an HARQ-ACK bit stream for the same priority index may be configured. After the above-described operation, a concatenation operation of HARQ-ACK bit streams for different priority indices may be performed.

3.4 PUCCH transmission delay (deferred transmission)

For transmission of HARQ-ACK for SPS PDSCH, time resources for transmission of SPS PUCCH may be indicated to the UE by activating DCI and/or higher layer signaling. In a TDD system or a system operating in an unlicensed band, PUCCH resources for HARQ-ACK transmission may not always be utilized. In the TDD system, since the SPS PUCCH can be transmitted in UL symbols, the UE may not transmit PUCCH in symbols other than UL symbols (eg, DL symbols, FL symbols, etc.). In the unlicensed band, the UE may not transmit the PUCCH when "the UE does not acquire the COT", "when the COT is not shared with the UE", or "when a symbol belonging to an idle period exists" there is.

In an embodiment, HARQ-ACK for SPS PDSCH and/or HARQ-ACK for release DCI releasing SPS may be referred to as SPS HARQ-ACK. In a TDD system, a slot pattern may be indicated or set to a UE using RRC signaling and/or DCI. The slot pattern may have a specific period, and the specific period of the slot pattern may be indicated to the terminal. Patterns of DL, UL, and FL symbols may be indicated to the UE. Some of the FL symbols indicated by RRC signaling may be changed or determined to DL, UL, or FL symbols through a specific DCI (eg, DCI format 2_0).

The terminal may perform a reception operation of a DL signal/channel or a transmission operation of a UL signal/channel in a semi-static FL symbol according to configuration or scheduling. The terminal may not perform a periodic reception operation or a periodic transmission operation in a semi-static FL symbol. For example, a symbol capable of receiving an SPS PDSCH may be a semi-static DL symbol. For example, a symbol through which a PUCCH including SPS HARQ-ACK is transmitted may be limited to a semi-static UL symbol. Since UL signals/channels allocated by DCI can be multiplexed, UL signals/channels can be transmitted in semi-static FL symbols in DCI-involved transmission.

When frame based equipment (FBE) is supported in an unlicensed band, the UE cannot transmit a UL signal/channel in an idle period. Here, the idle period may be derived based on a specific DCI (eg, DCI format 2_0). Alternatively, the terminal may implicitly derive an idle period. If a fixed frame period (FFP) is initiated by the UE, the UE cannot transmit in the idle period. If FFP is initiated by the base station, the base station cannot transmit in the idle period.

If the SPS PUCCH is expected to be invalid, the base station may not transmit the SPS PDSCH. If the SPS PUCCH is expected to be invalid, the UE may not transmit the SPS PUCCH (eg, SPS HARQ-ACK). When the SPS PDSCH is not transmitted, the base station may transmit DCI to schedule the PDSCH. DCI may indicate a valid PUCCH. In order to perform the above-described operation in an unlicensed band, the base station may secure a COT. Alternatively, the base station may receive sharing of the COT (eg, COT secured by the terminal or another base station). Otherwise, the base station cannot transmit the PDCCH outside the COT.

The HPN of the SPS PDSCH may be determined according to an equation defined in technical specifications. The HPN may be determined according to the time resource at which the SPS PDSCH is received. Depending on the setting of the base station, the HPN offset may be indicated to the terminal through RRC signaling. In an SPS PDSCH transmission/reception procedure, SPS PDSCHs belonging to different SPS configs may have the same HPN. Alternatively, different SPS PDSCHs belonging to the same SPS configuration (config) may have the same HPN. The base station may properly set the HPN offset to the terminal so that the HPNs do not collide. However, when transmission of HARQ-ACK is deferred in a TDD system or an unlicensed band, different SPS PDSCHs may use the same HPN. In this case, for different SPS PDSCHs using the same HPN, the HARQ-ACK may be replaced with the HARQ-ACK for the SPS PDSCH received later in the time domain.

HPNs of PDSCHs scheduled by DCI may be the same. In this case, the corresponding HPN may be utilized in the PDSCH scheduled by DCI according to technical specifications. Therefore, HPN collision of only SPS PDSCHs can be considered. Considering one HPN, the corresponding HPN may be utilized in two or more SPS PDSCHs. For example, HPN can be used in both SPS PDSCH candidate 1 belonging to HARQ codebook 1 and SPS PDSCH candidate 0 belonging to HARQ codebook 0. If SPS PDSCH Candidate 0 is received later in the time domain, the corresponding HARQ-ACK in HPN may be derived from SPS PDSCH Candidate 0. Therefore, the size of HARQ codebooks can be maintained, and only an update operation for HARQ-ACK can be performed.

According to another method, the terminal may not report HARQ-ACK for SPS PDSCH candidate 1 to the base station. This operation may be applied to a plurality of HARQ codebooks (eg, HARQ codebook i). i may be a natural number. The deferred HARQ codebook may not include HARQ-ACK for a specific HPN (eg, HPN for HARQ-ACK in which HPN is shared between PDSCHs and replaced with a new value). Since HARQ-ACK for the aforementioned HPN is not included in HARQ codebook i, the size of HARQ codebook i may be reduced.

Meanwhile, the arrangement order of HARQ codebooks generated in units of deferred HARQ codebooks may not be considered. A method in which the deferred HARQ codebooks are generated at one time may be considered. In the generation procedure of the delayed HARQ codebook, the terminal may arrange the delayed HARQ-ACK bits in one HARQ codebook. How the terminal generates the SPS HARQ codebook will be described. In the SPS HARQ codebook, HARQ-ACKs (eg, HARQ-ACK bits) may be arranged in the order of reception of SPS PDSCHs, then in the order of SPS configuration indices, and then in the order of serving cell indices. can be placed.

The base station may instruct or configure (sub)slot offsets applied to PDSCH-to-HARQ-feedback to the terminal using RRC signaling. For a (sub)slot in which the UE intends to transmit the PUCCH, candidates for receiving the SPS PDSCH may be derived. The above-described (sub)slots may be limited to Nc in serving cell c. In the generation procedure of the SPS HARQ codebook, Nc may increase by a deferred window. If transmission is deferred once, the value of Nc may be doubled. That is, the value of Nc may be "a value of Nc that has been postponed + a value of Nc that has not been postponed". If transmission is delayed twice, the value of Nc can be increased by a factor of 3.

3.4.1 How to operate with retransmission of PUCCH

When the SPS HARQ codebook is delayed and transmitted in the target (sub) slot, the UE may also perform a PUCCH retransmission operation. The base station may transmit DCI to the corresponding terminal so that the terminal transmits the PUCCH (or PUSCH) in the target (sub) slot. In this case, the terminal may consider the initial HARQ codebook 0, the delayed HARQ codebook, and / or the retransmission HARQ codebook. The terminal may assume at least one combination of initial HARQ codebook 0, delayed HARQ codebook, or retransmission HARQ codebook. Alternatively, the UE may assume that the initial HARQ codebook 0, the delayed HARQ codebook, and/or the retransmission HARQ codebook are multiplexed in a predetermined order.

Method 3.4-1: The terminal may assume that operations (eg, multiplexing operation and / or transmission operation) for the delayed HARQ codebook and the retransmission HARQ codebook are not performed simultaneously.

Method 3.4-2: The delayed SPS HARQ codebook and the retransmission HARQ codebook may be arranged in the time order (or the reverse order of time) that the terminal initially wanted to transmit, and the "delayed SPS HARQ codebook and retransmission HARQ codebook" is HARQ codebook 0 can be connected with

When an information word is generated based on the bit stream of HARQ-ACK, the concatenation is "HARQ codebook 0 is deployed first, and then the delayed SPS HARQ codebook and/or retransmission HARQ codebook are deployed" or "delayed SPS It may mean that the HARQ codebook and / or the retransmission HARQ codebook are deployed first, and then the HARQ codebook 0 is deployed. HARQ codebook 0 (eg, initial HARQ codebook 0) may be deployed first, then the SPS HARQ codebook may be deployed, and then the retransmission HARQ codebook(s) may be deployed. That is, within the HARQ-ACK bit stream, it may be arranged in the order of “first HARQ-ACK bit(s) → SPS HARQ-ACK bit(s) → retransmitted HARQ-ACK bit(s)”. Alternatively, in the HARQ-ACK bit stream, it may be arranged in the order of “first HARQ-ACK bit(s) → retransmitted HARQ-ACK bit(s) → SPS HARQ-ACK bit(s)”. The number of retransmission HARQ codebooks may be limited to one. Two or more HARQ codebooks may be arranged in a predetermined order.

When two or more priority indices are considered, the UE may generate an HARQ-ACK bit stream for the same priority index. After that, the terminal may perform a concatenation operation of HARQ-ACK bit streams for different priority indices.

3.4.2 Simultaneous support of sidelink HARQ and Uu UCI

The UE may not transmit PUCCH and/or PUSCH multiplexed with sidelink HARQ-ACK (sidelink HARQ-ACK codebook) and Uu UCI. The reason is that it is difficult to determine the size of a type 2 HARQ codebook or a type 1 HARQ codebook when sidelink HARQ-ACK and HARQ-ACK for PDSCH are multiplexed.

For example, the size of the type 1 HARQ codebook may be determined regardless of the number of scheduling DCIs, but the amount of sidelink HARQ-ACK may depend on the scheduling DCI. A field for counting the number of scheduling DCIs may be introduced to determine the size of the type 2 HARQ codebook, but the field for counting the number of sidelink HARQ-ACKs and the field for counting the number of HARQ-ACKs for the PDSCH are separately may be needed In this case, the size of the scheduling DCI may increase. Since the field of DCI is set by RRC signaling, additional fields can be continuously included in DCI even when sidelink or PDSCH is not frequently allocated. This may reduce the performance of DCI.

For a terminal supporting the delayed SPS HARQ-ACK, the base station may schedule sidelink HARQ-ACK and SPS HARQ-ACK so that they are not multiplexed. Since the slot in which the SPS HARQ-ACK is transmitted can be predicted by the base station, the base station can schedule the sidelink HARQ-ACK not to be transmitted in the corresponding slot. A slot in which the delayed SPS HARQ-ACK is transmitted may depend on a slot pattern in a TDD system. Since the slot in which the delayed SPS HARQ-ACK is transmitted does not depend on DCI, the base station can predict the slot in which the delayed SPS HARQ-ACK is transmitted in advance.

The fact that UCIs having different priorities are not multiplexed can be configured in the UE through RRC signaling. Considering this case, since the UE multiplexes one of the sidelink HARQ-ACK and Uu UCI using the priority index, multiplexing of the delayed SPS HARQ-ACK and the sidelink HARQ-ACK may not occur. . The base station can accurately predict the priority index of the sidelink HARQ-ACK. The base station may transmit scheduling DCI (DCI format 3_0) that does not include a priority index. The UE may determine the priority of the sidelink using channel busy ratio (CBR) and/or channel occupancy ratio (CR). The priority of the SL-SCH, inter-UE coordination (IUC) message, and/or SL-CSI may be appropriately derived. If the priority of the sidelink HARQ-ACK and the priority of the Uu UCI are the same, the sidelink HARQ-ACK and the Uu UCI can be multiplexed. According to the method described above, it is preferable not to occur when the priority of sidelink HARQ-ACK and the priority of Uu UCI are the same.

Method 3.4-3: The base station may instruct the corresponding terminal that the terminal does not multiplex UCIs having different priorities using RRC signaling. In this case, the UE may determine (eg, assume) that Uu UCI and sidelink HARQ-ACK have different priorities.

When the Uu UCI type with priority index 1 and the Uu UCI type with priority index 0 are derived, the Uu UCI type with the same priority index as the sidelink HARQ-ACK may exist. Accordingly, the base station may not perform the above-described scheduling. The base station may instruct or configure the terminal to multiplex UCIs having different priorities by using RRC signaling. Considering this case, it is preferable not to generate sidelink HARQ-ACK and Uu UCI having different priorities.

The terminal may be implemented based on the assumption that the scheduling of the base station is error-free. The UE may determine that sidelink HARQ-ACK and Uu UCI multiplexing does not occur. When multiplexing of sidelink HARQ-ACK and Uu UCI occurs, the UE may consider that an error has occurred. For example, the UE may drop PUCCH transmission or PUSCH transmission. That is, the UE may drop transmission of sidelink HARQ-ACK and/or Uu UCI.

Method 3.4-4: The base station may instruct the corresponding terminal that the terminal multiplexes UCIs having different priorities using RRC signaling. In this case, if it is determined that Uu UCI and sidelink HARQ-ACK have different priorities, multiplexing of sidelink HARQ-ACK and Uu UCI may not be allowed.

3.5 How to generate HARQ codebook considering priority

3.5.1 Type 1 HARQ Codebook

The base station may instruct or configure the generation of the type 1 HARQ codebook to the terminal using RRC signaling. At this time, considering the priority index, UCI 1 and UCI 0 may be multiplexed in the type 1 HARQ codebook. Alternatively, the UE may select only UCI 1 and generate a type 1 HARQ codebook including UCI 1. In the PUSCH transmission procedure, the T-DAI field of UL-DCI may indicate multiplexing of HARQ codebook(s) to the UE.

Method 3.5-1: When transmission of the type 1 HARQ codebook is configured for the UE, the size of the T-DAI included in the UL-DCI may be extended to 2 bits. One of the 2 bits of T-DAI may indicate whether or not to multiplex the HARQ codebook.

Method 3.5-2: One bit of T-DAI may indicate multiplexing of HARQ codebooks having the same priority index as UL-DCI, and the remaining bits of T-DAI have a priority index different from that of UL-DCI Multiplexing of HARQ codebooks may be indicated.

Method 3.5-3: One bit of T-DAI may indicate HARQ codebook multiplexing for URLLC, and the remaining bits of T-DAI may indicate HARQ codebook multiplexing for eMBB.

Here, the order of bits constituting the T-DAI field may be defined in technical specifications. For example, in UL-DCI, two or more T-DAI fields may be arranged contiguous with each other. As another example, in UL-DCI, T-DAI fields may be arranged without concatenation, and information related to the same priority in UL-DCI may be arranged in a group.

UL-DCI may include a separate field indicating multiplexing of UCI 1 and UCI 0. For example, a first value of a specific field included in UL-DCI may indicate multiplexing of UCI 1 and UCI 0, and a second value of the specific field may indicate multiplexing of UCI 1 or UCI 0. As another example, a first value of a code point indicated by a field included in UL-DCI may indicate multiplexing of UCI 1 and UCI 0, and a second value of the corresponding code point indicates multiplexing of UCI 1 or UCI 0. can instruct

The UE may derive resources in which UCI 1, UCI 0, and/or TB are multiplexed by referring to both DL-DCI and UL-DCI, and may transmit a PUSCH including UCI 1, UCI 0, and/or TB there is. At this time, the UE may assume that the DL-DCI indication and the UL-DCI indication are not different from each other. The above-described operation can be applied regardless of the type of codebook set to the terminal.

Method 3.5-4: A multiplexing instruction in DL-DCI (eg, a multiplexing instruction for UCI 1 and UCI 0) and a multiplexing instruction in UL-DCI (eg, a multiplexing instruction for UCI 1 and UCI 0) may be the same there is.

Considering the time point at which the UE receives the UL-DCI, even when the DL-DCI indicates multiplexing of all UCIs, the UE can select some UCIs from among all UCIs and transmit the selected some UCIs. If the DL-DCI indicates selection of some UCIs, the UE may not expect that the UL-DCI indicates multiplexing of all UCIs.

Method 3.5-5: If the DL-DCI indicates selection of some UCI (eg, UCI 1), the UE selects more UCIs (eg, UCI 1) than the UCI indicated by the DL-DCI. and UCI 0) may not be expected to indicate multiplexing.

3.5.2 Type 2 HARQ Codebook

The base station may instruct or configure the generation of the type 2 HARQ codebook to the terminal using RRC signaling. In this case, DL-DCI and/or UL-DCI may include C-DAI and T-DAI. At this time, the arrangement method of C-DAI and T-DAI in DCI may be considered. In an embodiment, UCI 1 may be described as corresponding to C-DAI1 and T-DAI1, and UCI 0 may be described as corresponding to C-DAI0 and T-DAI0.

Method 3.5-6: The size of each of the C-DAI field and the T-DAI field may be doubled. For example, the C-DAI field may consist of [C-DAI0, C-DAI1] or [C-DAI1, C-DAI0], and the T-DAI field may consist of [T-DAI0, T-DAI1] or [ T-DAI1, T-DAI0].

Method 3.5-7: When the priorities of the C-DAI field and the T-DAI field are the same, concatenation operations may be performed on the C-DAI field and the T-DAI field. For example, [C-DAI0, T-DAI0] or [T-DAI0, C-DAI0] can be set in DCI, and [C-DAI1, T-DAI1] or [T-DAI1, C-DAI1] in DCI. DAI1] can be set. A separate field may exist between the C-DAI field and the T-DAI field.

3.5.3 Transmission method of PUCCH format 2 considering priority

One codeword may be modulated, and a modulation result (eg, modulation symbol) may be mapped to PUCCH format 2. The UCI type may be SR, LRR, HARQ-ACK, and/or CSI. A UCI type may be regarded as an information word. The UE may generate one codeword by performing the same encoding operation for the UCI type(s). Priority indexes of UCI types may be the same.

A case in which eMBB UCI and URLLC UCI (eg, LP UCI and HP UCI) are multiplexed and mapped in one PUCCH resource may be considered. A codeword other than an information word may be generated separately, and the codeword may be mapped to a PUCCH resource. PUCCH format 2 may be distinguished from other PUCCH formats (eg, PUCCH formats 3 and/or 4).

When PUCCH format 3 or 4 is used, PUCCH DM-RS can use all subcarriers of OFDM symbols. OFDM symbols to which UCI codewords are mapped can be distinguished based on distances from DM-RS symbols. A DM-RS symbol may mean a symbol to which a PUCCH DM-RS is mapped. A codeword of a UCI having a high importance may be mapped to a symbol close to a DM-RS symbol, and a codeword of a UCI having a low importance may be mapped to a symbol distant from a DM-RS symbol.

30 is a conceptual diagram illustrating a first embodiment of a PRB belonging to PUCCH format 2.

Referring to FIG. 30, the DM-RS of PUCCH format 2 may use some subcarriers in an OFDM symbol. DM-RS may be mapped to subcarriers 1, 4, 7, and 10 in PRB belonging to PUCCH. All PRBs belonging to PUCCH format 2 may have the same subcarrier index. Encoded UCI may be adjacent to DM-RS. That is, the UCI codeword can maintain the same distance as the DM-RS. It is not necessary to differently map UCI codewords based on the distance to the DM-RS.

When the UCI codeword is mapped to some subcarriers in one OFDM symbol, it may be desirable to map the UCI codeword in a wide band in order to obtain a frequency multiplexing gain. Accordingly, the intervals of subcarriers to which the UCI codeword is mapped may be the same. The codeword of UCI is preferably mapped to all PRBs corresponding to PUCCH resources. To support the above-described operation, a PUCCH having a sufficiently large bandwidth may be indicated. Alternatively, frequency gain may be achieved by frequency hopping. In this case, the PUCCH resource may have 2 symbols.

If the PUCCH resource consists of two OFDM symbols, the coded HP UCI may be mapped first, and then the coded LP UCI may be mapped. When the amount of HP UCI is small, the HP UCI may be mapped limited to one OFDM symbol. In this case, a frequency multiplexing gain may not be obtained. To solve this problem, a method for mapping HP UCI to both OFDM symbols may be needed.

Method 3.5-8: The coded HP UCI may be divided into a first coded HP UCI and a second coded HP UCI, and each of the first coded HP UCI and the second coded HP UCI is mapped to one OFDM symbol. It can be. Each of the first encoded HP UCI and the second encoded HP UCI may be mapped to subcarriers at equal intervals in one OFDM symbol.

31 is a conceptual diagram illustrating a first embodiment of a method of multiplexing HP UCI and LP UCI in PUCCH format 2 having two OFDM symbols.

Referring to FIG. 31, the encoded HP UCI may consist of K _HP bits, the number of PRBs of the PUCCH may be N, and the modulation rate may be Q. When Quadrature Phase Shift Keying (QPSK) is used, Q may be 2. When π/2 Binary Phase Shift Keying (BPSK) is used, Q can be regarded as 1.

는 첫 번째 OFDM 심볼에서 HP UCI의 부호어가 점유하는 RE(resource element)들의 개수를 나타낼 수 있다.

는 두 번째 OFDM 심볼에서 HP UCI의 부호어가 점유하는 RE들의 개수를 나타낼 수 있다. LP UCI의 부호어가 점유하는 RE들의 개수는 HP UCI의 부호어가 맵핑되지 않는 나머지 RE의 개수일 수 있다.

may indicate the number of resource elements (REs) occupied by the codeword of HP UCI in the first OFDM symbol.

may represent the number of REs occupied by the HP UCI codeword in the second OFDM symbol. The number of REs occupied by the codeword of the LP UCI may be the number of remaining REs to which the codeword of the HP UCI is not mapped.

또는

으로 표현될 수 있다. (12-4)는 PRB의 12개의 부반송파들 중에서 DM-RS가 맵핑되는 4개의 부반송파들을 제외한 나머지 부반송파들의 개수를 의미할 수 있다. 또한, 하나의 OFDM 심볼에서 UCI의 부호어가 맵핑되는 부반송파 간격은

또는

로 표현될 수 있다. 상술한 방법에 의해 획득된 부반송파 위치 및 OFDM 심볼 위치에서 부호화된 HP UCI는 맵핑될 수 있다. 이때, RE 매핑 동작은 주파수 도메인에서 먼저 수행될 수 있고, 그 후에 시간 도메인에서 수행될 수 있다.The subcarrier interval to which the UCI codeword is mapped in one OFDM symbol is

or

can be expressed as (12-4) may mean the number of remaining subcarriers excluding 4 subcarriers to which the DM-RS is mapped among the 12 subcarriers of the PRB. In addition, the subcarrier interval to which the UCI codeword is mapped in one OFDM symbol is

or

can be expressed as The HP UCI encoded at the location of the subcarrier obtained by the above method and the location of the OFDM symbol may be mapped. In this case, the RE mapping operation may be performed first in the frequency domain and then in the time domain.

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 on a computer readable medium. Computer readable media may include program instructions, data files, data structures, etc. alone or in combination. Program instructions recorded on a computer readable medium may be specially designed and configured for the present invention or may be known and usable to those skilled in computer software.

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

Although described with reference to the above embodiments, those skilled in the art will understand that the present invention can be variously modified and changed without departing from the spirit and scope of the present invention described in the claims below. You will be able to.

Claims (20)

As a terminal method,
Receiving downlink control information (DCI) including a first field indicating hybrid automatic repeat request-acknowledgement (HARQ-ACK) retransmission and a second field indicating priority from a base station;
checking first HARQ-ACK information having the same priority as the priority indicated by the second field; and
Based on the indication of the first field, transmitting a first HARQ-ACK codebook including the first HARQ-ACK information to the base station. The method of claim 1,
The method of the terminal,
Further comprising checking second HARQ-ACK information having the same priority as the priority indicated by the second field,
The second HARQ-ACK codebook including the second HARQ-ACK information is transmitted to the base station together with the first HARQ-ACK codebook. The method of claim 2,
The first HARQ-ACK codebook is a retransmission HARQ-ACK codebook, the second HARQ-ACK codebook is an initial transmission codebook, and the second HARQ-ACK codebook within an HARQ-ACK bit stream is the first HARQ-ACK codebook. A method of a terminal, which is arranged earlier. The method of claim 1,
The method of the terminal,
checking second HARQ-ACK information having the same priority as the priority indicated by the second field; and
Further comprising checking third HARQ-ACK information having the same priority as the priority indicated by the second field,
The second HARQ-ACK codebook including the second HARQ-ACK information and the third HARQ-ACK codebook including the third HARQ-ACK information are transmitted to the base station together with the first HARQ-ACK codebook. way of. The method of claim 4,
The first HARQ-ACK codebook is a retransmission HARQ-ACK codebook, the second HARQ-ACK codebook is a first transmission codebook, and the third HARQ-ACK codebook is a deferred semi-persistent scheduling (SPS) HARQ- ACK codebook, the second HARQ-ACK codebook is placed first in the HARQ-ACK bit stream, the third HARQ-ACK codebook is placed after the second HARQ-ACK codebook, and the third HARQ-ACK codebook Afterwards, the first HARQ-ACK codebook is deployed. The method of claim 1,
The cell in which the first HARQ-ACK codebook is transmitted is determined based on the format of the DCI. The method of claim 1,
When the DCI is a fallback DCI, the first HARQ-ACK codebook is transmitted in the PCell. The method of claim 1,
The method of the terminal,
Further comprising receiving configuration information of a physical uplink control channel (PUCCH) serving cell from the base station,
When the DCI is a non-fallback DCI, the first HARQ-ACK codebook is transmitted in the PUCCH serving cell according to the configuration information. The method of claim 1,
The method of the terminal,
Further comprising receiving configuration information of a PUCCH serving cell from the base station,
"When the DCI is a non-fallback DCI and the DCI includes a third field indicating a cell in which PUCCH transmission is performed", the first HARQ-ACK codebook is based on the value of the third field and transmitted in the PCell or the PUCCH serving cell. The method of claim 1,
The DCI is a non-scheduling DCI, the method of the terminal. As a base station method,
Generating downlink control information (DCI) including a first field indicating whether hybrid automatic repeat request-acknowledgement (HARQ-ACK) retransmission is performed and a second field indicating priority;
Transmitting the DCI to a terminal; and
When the first field indicates HARQ-ACK retransmission, a first HARQ-ACK codebook including first HARQ-ACK information having the same priority as the priority indicated by the second field A method of a base station comprising the step of receiving a from the terminal. The method of claim 11,
A second HARQ-ACK codebook including second HARQ-ACK information having the same priority as the priority indicated by the second field is received from the terminal together with the first HARQ-ACK codebook, and the 1 HARQ-ACK codebook is a retransmission HARQ-ACK codebook, the second HARQ-ACK codebook is an initial transmission codebook, and the second HARQ-ACK codebook is earlier than the first HARQ-ACK codebook in an HARQ-ACK bit stream Deployed, the method of the base station. The method of claim 11,
A second HARQ-ACK codebook including second HARQ-ACK information having the same priority as the priority indicated by the second field and having the same priority as the priority indicated by the second field A third HARQ-ACK codebook including third HARQ-ACK information is received from the terminal together with the first HARQ-ACK codebook, the first HARQ-ACK codebook is a retransmission HARQ-ACK codebook, and the second HARQ-ACK codebook -ACK codebook is a super transmission codebook, the third HARQ-ACK codebook is a deferred semi-persistent scheduling (SPS) HARQ-ACK codebook, and the second HARQ-ACK codebook in the HARQ-ACK bit stream is Arranged first, the third HARQ-ACK codebook is disposed after the second HARQ-ACK codebook, and the first HARQ-ACK codebook is disposed after the third HARQ-ACK codebook. The method of claim 11,
A cell in which the first HARQ-ACK codebook is received is determined based on the format of the DCI, and when the DCI is a fallback DCI, the first HARQ-ACK codebook is received in a PCell, and the DCI is discussed. In case of (non)-fallback DCI, the first HARQ-ACK codebook is received in the PCell or physical uplink control channel (PUCCH) serving cell. The method of claim 11,
The method of the base station,
Further comprising transmitting configuration information of a physical uplink control channel (PUCCH) serving cell to the terminal, wherein the PUCCH serving cell is used for transmission and reception of the first HARQ-ACK codebook. As a terminal,
processor;
a memory that communicates electronically with the processor; and
Includes instructions stored in the memory;
When the instructions are executed by the processor, the instructions cause the terminal to,
Receiving downlink control information (DCI) including a first field indicating hybrid automatic repeat request-acknowledgement (HARQ-ACK) retransmission and a second field indicating priority from a base station;
Check first HARQ-ACK information having the same priority as the priority indicated by the second field; and
A terminal configured to transmit a first HARQ-ACK codebook including the first HARQ-ACK information to the base station based on the indication of the first field. The method of claim 16
The commands are the terminal,
It is further executed to check second HARQ-ACK information having the same priority as the priority indicated by the second field,
The second HARQ-ACK codebook including the second HARQ-ACK information is transmitted to the base station together with the first HARQ-ACK codebook, the first HARQ-ACK codebook is a retransmission HARQ-ACK codebook, and the second The HARQ-ACK codebook is a first transmission codebook, and the second HARQ-ACK codebook is disposed before the first HARQ-ACK codebook in the HARQ-ACK bit stream. The method of claim 16
The command is the terminal,
Checking second HARQ-ACK information having the same priority as the priority indicated by the second field; and
It is further executed to check third HARQ-ACK information having the same priority as the priority indicated by the second field,
A second HARQ-ACK codebook including the second HARQ-ACK information and a third HARQ-ACK codebook including the third HARQ-ACK information are transmitted to the base station together with the first HARQ-ACK codebook, The first HARQ-ACK codebook is a retransmission HARQ-ACK codebook, the second HARQ-ACK codebook is an initial transmission codebook, and the third HARQ-ACK codebook is a deferred semi-persistent scheduling (SPS) HARQ-ACK codebook, the second HARQ-ACK codebook is placed first in the HARQ-ACK bit stream, the third HARQ-ACK codebook is placed after the second HARQ-ACK codebook, and after the third HARQ-ACK codebook The first HARQ-ACK codebook is disposed in. The method of claim 16
A cell in which the first HARQ-ACK codebook is transmitted is determined based on the format of the DCI, and when the DCI is a fallback DCI, the first HARQ-ACK codebook is transmitted in a PCell, and the DCI is discussed. In case of (non)-fallback DCI, the first HARQ-ACK codebook is transmitted in the PCell or physical uplink control channel (PUCCH) serving cell. The method of claim 16
The commands are the terminal,
Further executed to receive configuration information of a physical uplink control channel (PUCCH) serving cell from the base station, wherein the PUCCH serving cell is used for transmission and reception of the first HARQ-ACK codebook.

Images