KR20210120873A - Uplink transmission method for ultra-reliability and low-latency communication, and apparatus therefor - Google Patents

Abstract

An uplink transmission method performed in a terminal includes the steps of: receiving, from a base station, at least one DCI for allocating first uplink transmission and second uplink transmission; performing, when a first LBT procedure for the first uplink transmission is successful by performing the first LBT procedure, the first uplink transmission; and performing, when a second LBT procedure for the second uplink transmission is successful by performing the second LBT procedure, the second uplink transmission. The first uplink transmission and the second uplink transmission may be continuously performed with a time interval longer than a predetermined time.

Description

Uplink transmission method for high-reliability low-latency communication and apparatus therefor

The present invention relates to an uplink transmission method and apparatus for high-reliability low-delay communication.

In order to reduce the data error rate, a lower code rate and modulation rate (MCS) may be applied. However, in order to prevent the size of the field indicating the MCS in DCI from becoming too large, frequently used MCSs are selectively used. If it is necessary to apply a lower MCS, repeated transmission is used. When QPSK, which is the lowest modulation rate, is used in repetitive transmission, the effect of lowering the code rate can be obtained. In particular, in the case of uplink, since transmission power is limited, repeated transmission in the time domain is utilized rather than repetitive transmission in the frequency domain.

The eMBB traffic and URLL traffic supported by the 5G system need to be lowered by MCS for different purposes. eMBB traffic requires a lower MCS to extend reach, whereas URLL traffic requires a lower MCS to reduce latency and achieve lower error rates. Because of these different requirements, eMBB traffic can be transmitted using repetitive transmission despite a relatively long delay time. On the other hand, in the case of URLLC traffic, DCI/RRC signaling may indicate by introducing new MCSs rather than repeated transmission.

It is an object of the present invention to solve the above problems, to provide various uplink transmission methods for high-reliability low-delay communication.

Another object of the present invention for solving the above problems is to provide an apparatus for performing various uplink transmissions for high-reliability and low-delay communication.

An embodiment of the present invention for achieving the above object is an uplink transmission method performed in a terminal, at least one piece of downlink control information (DCI, downlink control) for allocating a first uplink transmission and a second uplink transmission information) from the base station; performing a first listen before talk (LBT) procedure for the first uplink transmission and, if the first LBT procedure is successful, performing the first uplink transmission; and performing a second LBT procedure for the second uplink transmission and, if the second LBT procedure is successful, performing the second uplink transmission, wherein the first uplink transmission and the second uplink transmission Link transmission may be performed continuously with a time interval longer than a predetermined time.

The at least one DCI may be one DCI to which both the first uplink transmission and the second uplink transmission are allocated, or DCIs to which the first uplink transmission and the second uplink transmission are allocated respectively.

The at least one DCI may indicate the manner of the first LBT procedure.

The first uplink transmission may be PUSCH or PUCCH transmission, and the second uplink transmission may be SRS transmission.

When the second uplink transmission exists within a channel occupancy time (COT) secured by the base station, the second LBT procedure is performed in a Type 2 channel access scheme, and the second uplink transmission is performed by the base station If it exists outside the secured COT, the second LBT procedure may be performed in a Type 1 channel access method.

The second LBT procedure may be performed in a Type 1 channel access method.

The second LBT procedure may be performed only for the first symbol of a resource for transmitting the SRS.

Another embodiment of the present invention for achieving the above object is an uplink transmission method performed in a terminal, at least one piece of downlink control information (DCI, downlink control) for allocating a first uplink transmission and a second uplink transmission. information) from the base station; not performing the first uplink transmission when the first LBT procedure fails by performing a first listen before talk (LBT) procedure for the first uplink transmission; and performing a second LBT procedure for the second uplink transmission to perform the second uplink transmission if the second LBT procedure succeeds, and perform the second uplink transmission if the second LBT procedure fails and not doing so, wherein the first uplink transmission and the second uplink transmission may be continuously performed with a time interval shorter than a predetermined time.

The at least one DCI may be one DCI to which both the first uplink transmission and the second uplink transmission are allocated, or DCIs to which the first uplink transmission and the second uplink transmission are allocated respectively.

The at least one DCI may indicate the manner of the first LBT procedure.

The first uplink transmission may be PUSCH or PUCCH transmission, and the second uplink transmission may be SRS transmission.

The second LBT procedure may be performed in a Type 1, Type 2, Type 2A, Type 2B, or Type 2C channel access method.

The second LBT procedure may be performed only for the first symbol of a resource for transmitting the SRS.

If the second LBT procedure fails, the entire SRS may not be transmitted.

Another embodiment of the present invention for achieving the above object is an uplink transmission method performed in a terminal, an uplink transmission method performed in a terminal, at least for allocating a first uplink transmission and a second uplink transmission Receiving one piece of downlink control information (DCI, downlink control information) from the base station; According to the method of the first LBT procedure indicated by the at least one DCI, if the first LBT procedure is successful by performing a first LBT (listen before talk) procedure for the first uplink transmission, the first uplink performing the transfer; determining whether the second uplink transmission exists within a channel occupancy time (COT) secured by the base station; and Performing a second LBT procedure in a different channel access method depending on whether the second uplink transmission exists within the COT secured by the base station, and performing the second uplink transmission if the second LBT procedure is successful In addition, the first uplink transmission and the second uplink transmission may be continuously performed with a time interval longer than a predetermined time.

The method of the first LBT procedure may be a Type 1 channel access method or a Type 2/2A/2B/2C channel access method.

The at least one DCI includes information on whether a cyclic prefix (CP) extension is applied to the first uplink transmission, information on a length value of the CP extension, and/or a channel access priority class. Additional information may be included.

The at least one DCI may not indicate the method of the LBT procedure for the second uplink transmission.

CP extension may not be applied to the second uplink transmission.

When the second uplink transmission exists within the COT (channel occupancy time) secured by the base station, the second LBT procedure is performed in a Type 2/2A channel access scheme, and the second uplink transmission is secured by the base station. When present outside the COT, the second LBT procedure may be performed in a Type 1 channel access method.

Using the embodiments of the present invention, efficient uplink transmission can be performed. In particular, using the embodiments of the present invention enables high-reliability low-delay communication in the unlicensed band. Accordingly, 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 and 4 are conceptual diagrams for explaining the configuration of time resources of PUSCH repetition type B according to an embodiment of the present invention.
5 is a conceptual diagram for explaining examples of reflecting a processing time for each PUSCH instance(s) according to an embodiment of the present invention.
6 is a conceptual diagram for explaining an example of a method of considering a slot boundary when a processing time is reflected for each PUSCH instance(s) according to an embodiment of the present invention.
7 to 10 are conceptual diagrams for explaining other examples of a method of considering a slot boundary when a processing time is reflected for each PUSCH instance(s) according to an embodiment of the present invention.
11 is a conceptual diagram for explaining the relationship between the time secured by the LBT procedure and PUSCH repetition type B according to an embodiment of the present invention.
12 is a conceptual diagram for explaining a method of determining valid symbols by combining a nominal time window and COT indicators according to an embodiment of the present invention.
13 is a conceptual diagram illustrating a case in which a terminal attempts an LBT procedure within a nominal time window according to an embodiment of the present invention.
14 is a conceptual diagram illustrating a case in which PUCCH is repeatedly transmitted according to an embodiment of the present invention.
15 is a conceptual diagram for explaining an example of a method of considering a slot boundary when a time interval is provided for each PUCCH instance(s) according to an embodiment of the present invention.
16 is a conceptual diagram illustrating a case of a PUCCH occasion based on a subslot according to an embodiment of the present invention.
17 is a conceptual diagram illustrating a case in which a PUCCH occasion consists of four PUCCH instances according to an embodiment of the present invention.
18 and 19 are conceptual diagrams illustrating a case in which a PUCCH instance cannot be transmitted due to invalid symbol(s) according to an embodiment of the present invention.
20 and 21 are conceptual diagrams for explaining examples of a method of mapping encoded UCI (or UCI-encoded codeword or UCI codeword) to split PUCCH instances according to an embodiment of the present invention.
22 is a conceptual diagram for explaining a method of considering invalid symbol(s) in PUCCH occasion transmission according to an embodiment of the present invention.
23 is a conceptual diagram illustrating an example of a field of DCI to which TPC commands are concatenated according to an embodiment of the present invention.
24 is a conceptual diagram illustrating an example of configuring a TPC field with a TPC index indicating a combination of TPC commands according to an embodiment of the present invention.
25 to 29 are conceptual diagrams illustrating configuration examples of MAC CE for changing spatial relation information applied to PUCCH according to an embodiment of the present invention.
30 is a conceptual diagram for explaining a mapping relationship between PUSCH instances and RVs according to an embodiment of the present invention.
31 is a conceptual diagram for explaining a mapping relationship between PUSCH instances and RVs when RV cycling is performed before TCI state cycling according to an embodiment of the present invention.
32 is a conceptual diagram for explaining a concept in which UCIs are concatenated and encoded according to an embodiment of the present invention.
33 and 34 are conceptual diagrams for explaining a case in which different code rates are applied to each UCI type/UCI priority according to an embodiment of the present invention.
35 is a conceptual diagram for explaining a case in which different encodings are applied to different UCI types/UCI priorities or two parts of UCI according to an embodiment of the present invention.
36 to 39 are conceptual diagrams for explaining repeated transmission of an HARQ codebook according to embodiments of the present invention.
40 to 43 are conceptual diagrams for explaining operating methods when a PUCCH instance and a full/split PUSCH instance overlap each other according to an embodiment of the present invention.
44 to 45 are conceptual diagrams for explaining other operation methods when a PUCCH instance and a full/split PUSCH instance overlap each other according to an embodiment of the present invention.
46 and 47 are conceptual diagrams for explaining a UCI transmission method when repeated UCI transmission starts when repeated UCI transmission is not finished according to an embodiment of the present invention.
48 is a conceptual diagram for explaining methods in which PT-RSs are mapped according to an embodiment of the present invention.
49 is a conceptual diagram illustrating a time relationship between SRS and PUSCH/PUCCH according to an embodiment of the present invention.
50 is a conceptual diagram illustrating a time relationship between SRS and PUSCH/PUCCH in uplink concatenated transmission according to an embodiment of the present invention.
51 to 53 are conceptual diagrams for explaining a method of allocating SRS and PUSCH/PUCCH in uplink concatenated transmission according to an embodiment of the present invention.
54 is a conceptual diagram for explaining SRS symbols to which CP extension is applied according to an embodiment of the present invention.
55 is another conceptual diagram for explaining SRS symbols to which CP extension is applied according to an embodiment of the present invention.
56 is another conceptual diagram for explaining SRS symbols to which CP extension is applied according to an embodiment of the present invention.
57 to 59 are conceptual diagrams illustrating a case in which scheduling for a plurality of TRPs is performed according to an embodiment of the present invention.
60 is a conceptual diagram illustrating a configuration example of information bits of GC-DCI according to an embodiment of the present invention.
61 is a conceptual diagram illustrating a configuration example of ULCI according to an embodiment of the present invention.
62 is a conceptual diagram illustrating another configuration example of ULCI according to an embodiment of the present invention.
63 is a conceptual diagram for explaining the relationship between PUSCH transmission of a UE and ULCI according to an embodiment of the present invention.
64 is a conceptual diagram for explaining an operation according to ULCI when two or more PUSCHs are allocated to a UE according to an embodiment of the present invention.
65 is a conceptual diagram for explaining an operation according to ULCI when sidelink transmission and PUSCH are allocated to a UE according to an embodiment of the present invention.
66 is a conceptual diagram for explaining a PHR operation when two PUSCHs are allocated to a UE according to an embodiment of the present invention.

Since the present invention can have various changes and can have various embodiments, specific embodiments are illustrated in the drawings and described in detail in the detailed description. However, this is not intended to limit the present invention to specific embodiments, and it should be understood to include all modifications, equivalents and substitutes included in the spirit and scope of the present invention. In describing each figure, like reference numerals have been used for like elements.

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

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

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

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

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

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

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

1, the communication system 100 is a plurality of communication nodes (110-1, 110-2, 110-3, 120-1, 120-2, 130-1, 130-2, 130-3, 130-4, 130-5, 130-6). A plurality of communication nodes 4G communication (eg, long term evolution (LTE), LTE-A (advanced)), 5G communication (eg, NR (new radio)) defined in the 3rd generation partnership project (3GPP) standard ) can be supported. 4G communication may be performed in a frequency band of 6 GHz or less, and 5G communication may be performed in a frequency band of 6 GHz or more as well as a frequency band of 6 GHz or less.

For example, a plurality of communication nodes for 4G communication and 5G communication is a CDMA (code division multiple access) based communication protocol, WCDMA (wideband CDMA) based communication protocol, TDMA (time division multiple access) based communication protocol, FDMA (frequency division multiple access) based communication protocol, OFDM (orthogonal frequency division multiplexing) based communication protocol, Filtered OFDM based communication protocol, CP (cyclic prefix)-OFDM based communication protocol, DFT-s-OFDM (discrete) Fourier transform-spread-OFDM) based communication protocol, OFDMA (orthogonal frequency division multiple access) based communication protocol, SC (single carrier)-FDMA based communication protocol, NOMA (Non-orthogonal multiple access), GFDM (generalized frequency) Division multiplexing)-based communication protocol, FBMC (filter bank multi-carrier)-based communication protocol, UFMC (universal filtered multi-carrier)-based communication protocol, SDMA (Space Division Multiple Access)-based communication protocol, etc. can be supported. .

In addition, the communication system 100 may further include a core network. When the communication system 100 supports 4G communication, the core network may include a serving-gateway (S-GW), a packet data network (PDN)-gateway (P-GW), a mobility management entity (MME), and the like. have. When the communication system 100 supports 5G communication, the core network may include a user plane function (UPF), a session management function (SMF), an access and mobility management function (AMF), and the like.

On the other hand, 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) may each have the following structure.

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

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

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

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

Referring back to FIG. 1 , the communication system 100 includes a plurality of base stations 110 - 1 , 110 - 2 , 110 - 3 , 120 - 1 and 120 - 2 , and a plurality of terminals 130 - 1, 130-2, 130-3, 130-4, 130-5, 130-6). base station (110-1, 110-2, 110-3, 120-1, 120-2) and terminal (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) The comprising communication system 100 may be referred to as an “access network”. 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. have. 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, 120-2 is a NodeB (NodeB), an advanced NodeB (evolved NodeB), a base transceiver station (BTS), Radio base station (radio base station), radio transceiver (radio transceiver), access point (access point), access node (node), RSU (road side unit), RRH (radio remote head), TP (transmission point), TRP ( transmission and reception point), eNB, gNB, and the like.

Each of the plurality of terminals 130-1, 130-2, 130-3, 130-4, 130-5, 130-6 is a user equipment (UE), a terminal, an access terminal, and a mobile Terminal (mobile terminal), station (station), subscriber station (subscriber station), mobile station (mobile station), portable subscriber station (portable subscriber station), node (node), device (device), Internet of Things (IoT) It may be referred to as a device, a mounted device (such as a mounted module/device/terminal or on board device/terminal).

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

The terminal may communicate with the base station in a wide frequency band ranging from several hundred MHz to several tens of GHz. In general, in a communication system operating in a high frequency band, since the diffraction or reflection characteristics of radio waves are not good, the coverage of radio waves can be extended through beam forming or pre-processing. In order to transmit the control channel and the data channel including the synchronization signal, the base station may perform beamforming to transmit them to the terminal, and the terminal may also receive them through beamforming. Also, the terminal may perform beamforming to transmit the control channel and the data channel, and the base station may also receive it through beamforming.

A terminal accessing the system receives a synchronization signal and a broadcast channel (eg, synchronization signal/physical broadcast channel, SS/PBCH block), obtains downlink frequency synchronization and time synchronization, and can know cell identification information . The UE can know the resource of the control channel or the region of the control channel (Control resource set, CORESET) and the search space set (search space set) from the PBCH. Information necessary for initial access of the UE may be indicated to the UE in the corresponding CORESET (or CORESET 0) and the search space set. At this time, the search space set in which system information (system information or remaining minimum system information) is scheduled may be referred to as a Type0-PDCCH CSS set.

SS/PBCH and CORESET 0 may not be frequency domain multiplexed depending on the bandwidth of the system in which the UE performs initial access. Accordingly, SS/PBCH and CORESET 0 may be received by the UE in the form of FDM and time domain multiplexing.

In order to support time-domain repetitive transmission for eMBB traffic, PUSCH repetition (or PUSCH repetition type A) was introduced. In this case, the PUSCH (or PUSCH mapping type A) allocated in units of slots is repeatedly transmitted. That is, PUSCH repetition type A is a method in which time resources are allocated over several slots in order to extend the reach. DCI (in case of type 2 configured grant and dynamic grant) or RRC signaling (in case of type 1 configured grant) indicates only the time resource used for transmission in the first slot, and by indicating the number of repetitions with RRC signaling, PUSCH repetition type Time resources for A may be determined.

Repeated transmission of URLL traffic is not appropriate because it consumes delay time, but the advantage of lowering the decoding delay caused by applying a sufficiently low MCS can be utilized. Specifically, if a sufficiently low MCS is applied, the number of REs (resource elements) increases, and thus a delay time may occur because the base station (the decoder of the base station) must wait until all REs are received. However, if a PUSCH to which a rather high MCS is applied is repeatedly transmitted, the base station can operate a decoder with only some REs, and the first successful decoding time is higher than the decoding success time when a lower MCS is applied in a single transmission. It could be rather faster. Since unnecessary delay occurs when PUSCH repetition type A is applied, in order to reduce a delay time due to repeated transmission, a PUSCH (PUSCH mapping type B) allocated to a mini-slot as a unit is repeatedly transmitted. Repetition type B was introduced. DCI (in the case of type 2 configured grant and dynamic grant) or RRC signaling (in case of type 1 configured) by indicating a reference time resource and the number of repetitions of one PUSCH instance in combination, time resource for PUSCH repetition type B can be determined.

For convenience of description, in PUSCH repetition type B, two or more PUSCH instances may be expressed as constituting one PUSCH occasion.

A. How to set time resource in UL repetition

(1) Interpretation method of time window in licensed band

The slot pattern may be indicated (or configured) to the UE by RRC signaling or a combination of RRC signaling and DCI. A semi-static UL/DL pattern of slots may be commonly given to an unspecified number of UEs through RRC signaling. Alternatively, a semi-static UL/DL pattern of slots may be given to a specific UE by RRC signaling. Alternatively, DCI-20 (DCI format 2_0) may be indicated (or configured) to the UE by RRC signaling, and the UL/DL pattern of slots may be dynamically given to a specific UE using DCI-20.

In PUSCH repetition type B, the time resource of the PUSCH occasion is indicated using DCI (in the case of type 1 configured grant, using RRC signaling), both the reference time resource and the number of repetitions of the PUSCH instance are indicated (or set) can be The time resource of the PUSCH occasion may be indicated (or configured) beyond the boundary of the slot. Format of the slot (eg, DL / FL symbols), occupancy time (eg, COT end symbol or fixed frame period by SFI or MCOT of channel occupancy time), or dynamic activation of invalid (invalid) resources Accordingly, the UE may or may not transmit the PUSCH instance(s) crossing the slot boundary.

For convenience of description, invalid symbol(s) means symbol(s) to which PUSCH is not mapped by DCI or RRC signaling, and valid symbol(s) are invalid symbol(s) within a nominal time window. ) other than the symbol(s), that is, the valid symbol(s) refers to the symbol(s) to which the PUSCH is mapped, and the invalid symbol(s) is a synchronization signal/physical broadcast channel (SS/PBCH) Symbol(s) indicated by RRC signaling that a block (or SSB) is transmitted and symbol(s) indicated (or set) by RRC signaling that a Type0-PDCCH CSS set is transmitted. In addition, according to the number indicated (or set) by RRC signaling, the terminal may assume that the indicated number of symbol(s) after the semi-static DL symbol(s) are invalid symbol(s).

Hereinafter, the nominal time window is not directly indicated to the UE, but for convenience of description, it may be described that PUSCH or PUCCH is transmitted within the time window. As an example of the signaling method, the number of symbol(s) of one full PUSCH instance and the number of PUSCH instance(s) constituting a PUSCH occasion may be signaled to the UE. The length of the nominal time window interpreted by the terminal may be a product of these. Here, the nominal time window may be longer than the time at which the PUCCH occasion is actually transmitted or may be the same length as the time at which the PUCCH occasion is actually transmitted.

3 and 4 are conceptual diagrams for explaining the configuration of time resources of PUSCH repetition type B according to an embodiment of the present invention.

Referring to FIG. 3 , the PUSCH is repeatedly transmitted 4 times in all symbols belonging to a nominal time window. Referring to FIG. 4 , the PUSCH is repeatedly transmitted 3 times in a nominal time window, but the PUSCH is not transmitted in some symbol(s) (ie, invalid symbol(s)) belonging to the nominal time window. For example, the second PUSCH instance may be transmitted temporally separated due to invalid symbols. In the following description, a PUSCH instance that is temporally separated and transmitted is defined as a spit PUSCH instance. In the Split PUSCH instance, DM-RSs for each are transmitted and TBs are mapped. If the split PUSCH instance consists of only a small number of symbol(s) and the TB cannot be mapped even if the DM-RS is mapped, the corresponding split PUSCH instance may not be transmitted.

If the base station(s) are deployed as several transmission and reception points (TRPs) (ie, mTRP or mTRP scenario), the UE may transmit PUSCH instances included in the PUSCH occasion to different TRPs. For example, in the case of a 3GPP NR system, if it operates in FR1 (frequency range 1), the UE applies the same TPMI (Transmit Precoding Matrix Indicator)/TRI (Transmit Rank Indicator) or SRS resource indicator (SRI) to all PUSCH instances. Even if applied, reception in a plurality of TRPs is not difficult. However, if operating in FR2, it is preferable that a different TPMI/TRI or SRI is applied for each TRP.

Therefore, in order for the UE to apply different spatial pre-processing (precoding or spatial filter) to each TRP or to allocate different transmission power, an operation of changing the TPMI/TRI or SRI for each PUSCH instance is required. In the following description, the UL Transmission Configuration Indicator (TCI) state may mean pre-processing applied by the UE. In the case of codebook-based PUSCH transmission, the UL TCI state may be interpreted as TPMI or TPMI and SRI, and in the case of non-codebook-based PUSCH transmission, the UL TCI state is SRI or DL RS (eg For example, it may be interpreted as an SS/PBCH block, CSI-RS for tracking).

The operation of changing the TCI state includes an operation of the UE changing a spatial preprocessing (TPMI or SRI or spatial filter) and/or an operation of allocating transmission power and/or timing advance differently. Therefore, a predetermined processing time is required to apply different TCI states depending on the capability of the terminal. Hereinafter, the processing time is expressed as the number of symbols (d) corresponding to the processing time for convenience of description.

(2) Interpretation method of time window considering additional RRC signaling

Hereinafter, examples in which processing time is considered for each PUSCH instance or a group of two or more PUSCH instances are described.

5 is a conceptual diagram for explaining examples of reflecting a processing time for each PUSCH instance(s) according to an embodiment of the present invention.

Referring to FIG. 5 , an example of PUSCH repetition type B is shown in the mTRP scenario. In the case of the PUSCH occasion indicated by the Dynamic UL grant, a nominal time window is derived from DCI. In the case of the PUSCH occasion indicated by the Type 1 configured grant (T1 CG), the length of the nominal time window is derived from RRC signaling, and in the case of the PUSH occasion indicated by the type 2 configured (T2 CG), the nominal time window from the activating DCI is derived from the length of The UE may map PUSCH instance(s) to time resources excluding invalid symbol(s). Thus, in the method of indicating a nominal time window, a predetermined processing time can be taken into account.

). 또한 PUSCH instance들이 비슷한 값의 TA를 가지는 경우에도 PUSCH instance들 간에는 별도의 간격이 불필요할 수 있다. 이러한 경우, PUSCH instance에 할당되어야 하는 전송 전력을 결정하기 위해서, PUCCH occasion에 속한 어느 하나의 PUSCH instance가 전송 전력을 도출하는 기준이 될 수 있다. When the same transmission power is allocated to PUSCH instances, the time taken for the operation of changing the preprocessing for each PUSCH instance may not be large. For example, the length of the time taken for the operation of changing the preprocessing for each PUSCH instance may be less than the length of the CP section. When a plurality of antenna panels included in the terminal are all activated, the operation of the terminal changing the preprocessing may be interpreted as an operation of the terminal selecting the antenna panel(s) and performing transmission. In this case, a separate interval may be unnecessary between PUSCH instances (that is,

). In addition, even when PUSCH instances have TAs having similar values, a separate interval between PUSCH instances may be unnecessary. In this case, in order to determine the transmission power to be allocated to the PUSCH instance, any one PUSCH instance belonging to the PUCCH occasion may be a reference for deriving the transmission power.

The same UL TCI state may be indicated to the UE for one or more PUSCH instance(s). In this case, it may be assumed that PUSCH instance(s) indicated by the same UL TCI state will be received by the same TRP. When the UL TCI state is changed, processing time is required to apply pre-processing differently or to allocate power differently.

For convenience of description, in the following methods, a case in which a time interval is provided for each PUSCH instance is considered. However, even when a time interval is provided for each group of PUSCH instances, the following methods can be easily extended and applied.

(Method A.2-1) A nominal time window is derived from DCI/RRC.

The UE may transmit a PUSCH occasion using only valid symbol(s) belonging to the nominal time window. In the case of a dynamic UL grant, the UE may be instructed with a time window by scheduling DCI. In the case of T1 CG, a time window may be indicated (or set) to the UE through RRC signaling. In the case of T2 CG, a time window may be indicated (or set) to the UE through activation DCI.

)와 반복 횟수(

)에 의해 결정된다.(Method A.2-2) the nominal time window is at least the reference length of the PUSCH instance (

) and the number of iterations (

) is determined by

)와 반복 횟수(

)를 활용하여 명목 시간 윈도우를 결정한다. 일 예에서, 명목 시간 윈도우는

개의 심볼들로서 연이어 주어질 수 있다. 단말은 무효 심볼들을 제외하고 PUSCH를 맵핑한다. PUSCH instance마다 단말에게 처리 시간이 필요하기 때문에, 하나의 PUSCH instance를 전송하기 위해서,

개 이상의 심볼들이 필요하다. 예를 들어,

개의 PUSCH instance들을 연이어 전송한다면,

개의 심볼들이 필요하다. 따라서,

개의 심볼들이 단말에게 지시된 경우, 단말은

개의 심볼들 중에서 유효 심볼(들)과 무효 심볼(들)을 확인하고, 유효 심볼(들)만을 이용해서 PUSCH instance(들)을 맵핑할 수 있다. (방법 A.2-2)에 의하면, 단말은 명목 시간 윈도우에 속한 모든 심볼들이 유효 심볼들이어도,

개의 PUSCH instance를 모두 전송할 수 없다.According to the proposed method, the terminal is at least the reference length of the PUSCH instance (

) and the number of iterations (

) to determine the nominal time window. In one example, the nominal time window is

It can be given consecutively as symbols of . The UE maps the PUSCH except for invalid symbols. Since processing time is required for the UE for each PUSCH instance, in order to transmit one PUSCH instance,

More than two symbols are required. E.g,

If the PUSCH instances are transmitted consecutively,

You need two symbols. thus,

When symbols are indicated to the terminal, the terminal

Valid symbol(s) and invalid symbol(s) may be identified among the symbols, and PUSCH instance(s) may be mapped using only the valid symbol(s). According to (Method A.2-2), even if all symbols belonging to the nominal time window are valid symbols,

All PUSCH instances cannot be transmitted.

), 반복 횟수(

), 및 처리 시간(

)에 의해 결정될 수 있다.(Method A.2-3) The nominal time window is at least the reference length of the PUSCH instance (

), the number of iterations (

), and processing time (

) can be determined by

의 함수로써 도출되어,

개의 심볼들로 연이어 주어질 수 있다. 단말은 무효 심볼들을 제외하고 PUSCH를 맵핑한다. (방법 A.2-3)에 의하면, 단말은 명목 시간 윈도우에 속한 모든 심볼들이 유효 심볼들일 때,

개의 PUSCH instance를 모두 전송할 수 있다.According to the proposed method, when the UE is allocated a PUSCH occasion according to (Method A.2-2), the processing time may be additionally considered. Here, the processing time may be given by RRC signaling. The processing time may be indicated to the terminal as a value determined by the base station in consideration of the capability of the terminal. Alternatively, a value predetermined in the technical standard may be applied as the processing time. Alternatively, the predetermined value may be different according to the frequency domain (FR1 or FR2). In one example, the nominal time window is

It is derived as a function of

It can be given consecutively as symbols of . The UE maps the PUSCH except for invalid symbols. According to (Method A.2-3), when all symbols belonging to the nominal time window are valid symbols,

All PUSCH instances can be transmitted.

In the following, a system operating in a licensed band is considered. When the UE transmits the PUSCH occasion to the base station, if the PUSCH occasion crosses the boundary of the slot, the base station may indicate to the UE a pattern of symbols that cannot transmit a PUSCH instance among FL symbols through RRC signaling. The base station may instruct (or configure) whether to use the corresponding symbols or not to use them by using scheduling/activating DCI or RRC signaling instructing the terminal to transmit a PUSCH occasion. That is, these symbol(s) may be used for transmission of the PUSCH instance according to the instruction of the base station. Hereinafter, these symbol(s) are referred to as invalid symbols ((in)valid symbol(s)). Invalid symbol(s) are indicated by RRC signaling, and while the terminal is allocated a PUSCH occasion from the base station, the terminal receives additional information (eg, the capability of the terminal, the pattern of the slot in case of TDD, a message set by the RRC signaling of the base station) , SS/PBCH block pattern, and/or Type0-PDCCH CSS set/CORESET 0) may be used to determine an invalid symbol as a valid symbol or an invalid symbol.

If the base stations are configured with a plurality of TRPs (ie, mTRP scenario), the UE may consider a predetermined processing time in order to transmit a PUSCH instance(s) belonging to a PUSCH occasion.

개 이상의 심볼로 구성된 경우, 유무효 심볼(들)이 무효 심볼(들)로 결정되더라도, 단말은 처리시간을 별도로 할당하지 않을 수 있다. 유무효 심볼(들)이

개 미만 (즉,

개 이하의 심볼로 구성된 경우)의 심볼로 구성된 경우, 유무효 심볼(들)이 무효 심볼(들)로 결정되면, 단말은 처리시간을 별도로 할당하여야 한다. (Method A.2-4) Invalid symbol(s)

In the case of two or more symbols, even if the invalid symbol(s) are determined to be invalid symbol(s), the terminal may not allocate processing time separately. invalid symbol(s)

less than dogs (i.e.,

In case of consisting of symbols (in the case of not more than 2 symbols), if the invalid symbol(s) is determined to be invalid symbol(s), the terminal must allocate processing time separately.

개의 심볼 또는 그 이상의 간격을 가질 수 있다.Depending on the capability of the terminal, post-processing for downlink reception and pre-processing for uplink transmission may be operated separately. When the invalid symbol(s) is determined to be invalid symbol(s), since the PUSCH instance is not mapped to the invalid symbol(s), the terminal changes the preprocessing period for the period corresponding to the invalid symbol(s) time can be used. For example, based on the boundary of the slot, the immediately preceding PUSCH instance and the immediately following PUSCH instance are

It can have an interval of n symbols or more.

6 is a conceptual diagram for explaining an example of a method of considering a slot boundary when a processing time is reflected for each PUSCH instance(s) according to an embodiment of the present invention.

개의 심볼로 표현된 시간이 충분히 길지 못해서, split PUSCH instance를 맵핑할 수 없기 때문이다. 유무효 심볼(들)이 무효 심볼(들)로 결정된 경우, 단말은 그 이후에 위치한 심볼(들)을 유효한 심볼(들)로 해석할 수 있다.Referring to FIG. 6 , since processing time for a PUSCH instance transmitted before the boundary of the slot is not sufficiently secured, subsequent PUSCH instances are transmitted after the boundary of the slot.

This is because the time expressed by the symbols is not long enough, and thus the split PUSCH instance cannot be mapped. When the invalid symbol(s) is determined as the invalid symbol(s), the terminal may interpret the symbol(s) located thereafter as valid symbol(s).

7 to 10 are conceptual diagrams for explaining other examples of a method of considering a slot boundary when a processing time is reflected for each PUSCH instance(s) according to an embodiment of the present invention.

개의 심볼 이후에 PUSCH instance를 맵핑할 수 있다. Referring to FIG. 7 , a case in which the length of the invalid symbol(s) is shorter than the processing time is illustrated. When the invalid symbol(s) is determined as the invalid symbol(s), the terminal in order to secure processing time

A PUSCH instance may be mapped after symbols.

On the other hand, referring to FIG. 8 , a case in which the length of the invalid symbol(s) is longer than the processing time is illustrated. When the invalid symbol(s) is determined to be the invalid symbol(s), the terminal can separate the processing time because the period of the invalid symbol(s) can be used as the processing time by applying (Method A.2-4). no need to secure

Meanwhile, depending on the capability of the terminal, post-processing for downlink reception and pre-processing for uplink transmission may not be distinguished. In this case, if the invalid symbol(s) is determined as the invalid symbol(s), the terminal cannot arbitrarily utilize the period of the invalid symbol(s) for downlink reception from the base station. Therefore (Method A.2-4) cannot be applied.

(Method A.2-5): If the invalid symbol(s) is determined as the invalid symbol(s), the UE separately allocates processing time after the invalid symbol(s), and thereafter, the PUSCH instance can be transmitted have.

Referring to FIGS. 9 and 10 , the UE may separately allocate processing time regardless of the length of the invalid symbol(s).

(3) Analysis method of time window considering additional DCI

In the following, a system operating in an unlicensed band is considered. In order to perform high-reliability low-delay communication in the unlicensed band, the base station may instruct (or set) the PUSCH repetition type B to the terminal. In the unlicensed band, the base station or the terminal must perform channel sensing (or LBT (listen before talk) procedure) before performing transmission. When the terminal operates as load based equipment (LBE), the terminal may secure a channel occupancy time (COT) starting at an arbitrary time through the LBT procedure. When the UE operates as frame based equipment (FBE), the UE may secure a COT (or FFP) starting at a predetermined time through LBT. In order for the UE to operate as an FBE, the UE may be instructed (or configured) by higher layer signaling. For example, the base station may explicitly instruct the terminal to operate as an FBE in the corresponding band by using a specific parameter of SIB1 or RRC signaling. Alternatively, when the unlicensed band is determined, it may be determined that the terminal operates in LBE or FBE without separate signaling.

When operating in LBE, if the terminal fails in the LBT procedure, the LBT procedure is not performed again for a predetermined time. In order to give fairness to the time occupied by several terminals and/or base stations in the unlicensed band, the time during which the LBT procedure is prohibited may increase or decrease depending on the success or failure of the LBT procedure. When the terminal succeeds in the LBT procedure and transmits an uplink signal and/or a channel, the maximum occupied time (maximum COT, MCOT) may be determined. At this time, the value of the MCOT may be derived from the characteristics of the LBT procedure performed by the terminal or the length of the sensing time of the LBT procedure.

When operating in FBE, the terminal may periodically perform the LBT procedure. Even if the terminal fails the LBT procedure, the time to perform LBT again is not affected. The LBT procedure can be performed only for a sensing time of a preset time. If the LBT procedure is successful, the terminal may transmit an uplink signal and/or a channel within the MCOT. Alternatively, if the terminal succeeds in the LBT procedure by performing the LBT procedure before transmitting the uplink signal and/or channel, the terminal may transmit the uplink signal and/or the channel. At this time, the maximum time secured by the terminal as the time corresponding to the MCOT may be derived from the period in which the terminal performs the LBT procedure. The time that the terminal can perform the LBT procedure is determined in the technical standard, for example, the periodic LBT procedure is started only in even-numbered radio frames, the value selected by the terminal (eg, {1, 2, 4, 5 , 10, 20}), the LBT procedure can be started only when it becomes an integer multiple. That is, the terminal may start the LBT procedure at one or more predetermined time positions among them, and if the LBT procedure is successful, the terminal may occupy 95% or less of the time of the corresponding period. In this case, a time that the terminal cannot occupy or a time that the terminal does not occupy may be referred to as an idle time (or an idle period).

An example of PUSCH repetition type B in the unlicensed band scenario has relevance to the time secured by the serving base station or the terminal performing the LBT procedure. The UE may transmit the PUSCH only after the LBT procedure is successful. As an example, it may be assumed that the nominal time window belongs to all of the time resources (COT) already secured by the base station or the terminal.

11 is a conceptual diagram for explaining the relationship between the time secured by the LBT procedure and PUSCH repetition type B according to an embodiment of the present invention.

Referring to FIG. 11 , a PUSCH occasion consists of four PUSCH instances. According to the result of the LBT procedure, the UE may transmit 4 or less PUSCH instance(s). In FIG. 11, case (a) is a case in which the first LBT procedure is successful so that transmission is possible from the first PUSCH instance of a PUSCH occasion, and case (b) is a case in which the first LBT procedure fails and the second LBT procedure succeeds and the second PUSCH It is a case in which transmission is possible from the instance, case (c) is a case where the first and second LBT procedures fail and the third LBT procedure succeeds and transmission is possible from the third PUSCH instance, and case (d) is the first, second, and third LBT This is a case where all procedures fail and the fourth LBT procedure succeeds and transmission is possible from the last PUSCH instance. Here, the terminal may perform LBT procedures up to four times, and may operate in LBE or FBE according to the specification of the unlicensed band. The specific method of the LBT procedure may be different depending on whether the terminal operates in LBE or FBE, and there may be cases in which the LBT procedure is unnecessary.

On the other hand, the nominal time window can be interpreted to exceed one COT. For example, the nominal time window starts at the time secured by the base station or the terminal, and the nominal time window of the PUSCH occasion may be interpreted so as to exceed the MCOT (or idle time). Here, the LBT procedure performed by the base station and the LBT procedure performed by the terminal may have the same sensing time length (ie, sensing time or LBT category), but may have different sensing times.

(Method A.3-1) The UE may consider some symbol(s) among symbols belonging to both the nominal time window and the COT as valid symbol(s).

The UE may know the symbol(s) capable of transmitting the PUSCH instance in the COT. For example, the terminal may receive a COT indicator from the base station through DCI. At this time, the COT indicator may classify the characteristics of symbols of the time resource secured by the base station into DL, FL, and UL. The UE may transmit a PUSCH instance in non-DL symbols (ie, FL symbol(s) or UL symbol(s)). Therefore, the UE can know the nominal time window as scheduling DCI and/or activation DCI, and combine the nominal time window and a separate DCI (ie, COT indicator) to derive valid symbol(s) capable of transmitting the PUSCH occasion can do. Here, the COT indicator indicates the structure of the time resource secured by the base station and shared to the terminal, and the terminal receives the characteristic and/or effective symbol(s) of symbols belonging to the same time resource by one or more COT indicators. can

12 is a conceptual diagram for explaining a method of determining valid symbols by combining a nominal time window and COT indicators according to an embodiment of the present invention.

12, COT1 and COT2 mean COTs secured by the base station. The UE may derive the nominal time window and determine the effective symbol(s) from among the symbols belonging to the nominal time window and COT1 or COT2. To this end, the UE may determine the valid symbol(s) by decoding the COT indicators. The UE may determine the valid symbol(s) by considering both the COT indicator for COT1 and the COT indicator for COT2.

Meanwhile, the valid symbol(s) may be determined not from the COT secured by the base station, but also from the COT secured by the terminal. For example, in FIG. 12 , COT2 may be a COT secured by the terminal. In this case, the COT indicator for COT2 may not be separately signaled to the UE. Alternatively, even if the terminal receives the COT indicator from the base station and the COT indicator includes information about symbols belonging to COT2, if the terminal secures COT2, the information of the COT indicator for COT2 received from the base station may not be utilized. have.

On the other hand, the base station may not signal the COT indicator(s) to the terminal to the terminal. In this case, the terminal may consider the symbols that succeeded in the LBT procedure and subsequent symbols among the symbols belonging to the nominal time window as valid symbols within the MCOT.

On the other hand, when the terminal operates in FBE, the terminal may not be able to receive or transmit in the idle time. Accordingly, symbols belonging to the idle time may be regarded as invalid symbols.

(Method A.3-2) The UE may try several LBT procedures to transmit the PUSCH occasion in the symbol(s) belonging to the nominal time window.

The UE may perform the LBT procedure in a symbol belonging to the immediately preceding or nominal time window of the nominal time window, and may transmit a PUSCH occasion if the LBT procedure is successful. Since the PUSCH occasion consists of two or more PUSCH instances, the UE may perform the LBT procedure as many as the number of (split) PUSCH instances.

13 is a conceptual diagram illustrating a case in which a terminal attempts an LBT procedure within a nominal time window according to an embodiment of the present invention.

Referring to FIG. 13 , the UE derives a nominal time window, performs the LBT procedure, and, if successful, may map the PUSCH instance. Depending on whether the terminal operates in LBE or FBE, the terminal may or may not perform the LBT procedure. For example, when operating as LBE, the UE attempts a C2 LBT (category 2 LBT or type 2/2A/2B/2C channel access) procedure to secure COT1, and C4 LBT (category 4 LBT or type 1 channel access) ) procedure to obtain COT2. For example, in the case of operating as FBE, the terminal may secure COT1 without an LBT procedure or by performing a C2 LBT procedure, and may secure COT2 by retrying the LBT procedure.

The UE may determine some symbol(s) of the nominal time window and symbol(s) belonging to COT1 or COT2 as valid symbol(s). In this case, the full PUSCH instance may be divided into two or more split PUSCH instances by invalid symbol(s).

(4) How to determine time resources for UCI transmission

Hereinafter, a method of allocating a PUCCH occasion will be described. In order to transmit uplink control information (UCI), the UE may be instructed by RRC signaling the resource of the PUCCH. The resource of the PUCCH transmitted by the UE may be indicated by using information included in DL-DCI or by using information indicated by the MAC layer. Here, DL-DCI may mean scheduling DCI, but is not limited thereto, and activating DCI for SPS PDSCH may also be included. The CRC of the Scheduling DCI may be scrambled by at least C-RNTI, MCS-C-RNTI, or CS-RNTI, and the CRC of the activating DCI may be scrambled by the CS-RNTI.

Considering a scenario in which one or more TRPs are deployed, PUCCH may be repeatedly transmitted for each TRP. That is, UCI is repeatedly transmitted, and preprocessing considering each TRP may be applied to the PUCCH instance. Here, the preprocessing applied to the PUCCH instance may be indicated (or configured) to the UE by higher layer signaling. For example, as a message indicated by the MAC layer, preprocessing applied to the PUCCH instance may be indicated (or configured) to the terminal using one index.

The nominal time window is not directed to the terminal and may be derived based on information received by the terminal. For example, the first symbol of the PUCCH occasion may be indicated to the UE through DL-DCI or RRC signaling. In addition, the number of PUCCH instance(s) constituting the PUCCH occasion should be indicated (or set) to the UE.

(Method A.4-1) In the RRC parameter representing the resource of the PUCCH, the number of repetitions is additionally expressed.

When a PDSCH is allocated from DL-DCI or RRC signaling, the UE may also be instructed with a PUCCH resource for this. In this case, the resource of the PUCCH is expressed as an index, and the resource set of at least one PUCCH and the resource of at least one PUCCH belonging thereto may be indicated (or configured) to the UE through RRC signaling. The resource of the PUCCH may include at least a time resource (ie, the number of symbols of the PUCCH) and a format. Here, when transmitted as a PUCCH occasion, the number of repetitions may be further included.

When the amount of UCI is 2 bits or less, the UE may use a format based on a spread sequence, and otherwise may use a format in which the encoded UCI is mapped. In this case, the number of repetitions applied on the PUCCH occasion may be different from each other. For example, according to (Method A.4-1), since the number of repetitions is provided for each resource of the PUCCH, a different number of repetitions may be provided for each format.

In one example, the UE may interpret the PUCCH instance as the number of times transmitted in consecutive symbols. Alternatively, the UE may interpret the PUCCH instance as the number of transmissions with a predetermined interval (d symbols). Alternatively, in another example, the UE may interpret the PUCCH instance as the number of times it is transmitted with a (sub)slot interval.

(Method A.4-2) For each resource set of PUCCH, the number of repetitions of PUCCH may be included.

The resource set of PUCCH may be selected by the UE according to the amount of UCI. Depending on the amount of UCI, PUCCH may be generated by spreading, Reed Muller code, or polar code applied. The resource set of PUCCH is determined according to the amount of UCI, the first set is selected when the amount (N bits) of UCI is 1 or 2 bits, and the i-th set is selected when N _i-1 <N≤N _i bits do. Here, _{the value of N i} may be indicated (or set) to the UE by RRC signaling. The value of i has a value of 4 or less, and is fixed to _{N 2} =3 and N _{4 =1706.} If _{the value of N i} is not indicated (or set) to the terminal, it is regarded as 1706.

A coding scheme (ie, spreading, Reed Muller code, polar code) applied to PUCCH for each resource set of PUCCH may be different. When appropriate N _i is set, the same number of repetitions can be obtained according to (Method A.4-2) while having the same coding scheme in a resource set of one PUCCH. This may have a small RRC signaling burden compared to (Method A.4-1).

In one example, when UCI is spread and mapped to PUCCH, such repeated transmission may not be supported. That is, in the first set (ie, when the amount of UCI is less than 3 bits) in the resource set of PUCCH, it may be considered that transmission of PUCCH is not repeated.

In another example, such repeated transmission may be independently indicated regardless of the resource set of the PUCCH regardless of the amount of UCI. That is, according to the indication (or configuration) of the base station, it may be considered that repeated transmission is instructed (or configured) only in all sets or some sets among resource sets of PUCCH.

(Method A.4-3) The number of repetitions is indicated in the RRC parameter expressing repeated transmission of PUCCH.

The UE does not indicate repeated transmission in the index representing the resource of the PUCCH, and the number of repetitions may be indicated (or set) separately from the resource of the PUCCH. In one example, one RRC parameter indicating repeated transmission of PUCCH may be used. The same number of times may be applied regardless of whether the number of PUCCH transmissions (ie, the number of PUCCH instances) is slot-based or sub-slot-based.

On the other hand, in another example, several RRC parameters indicating repeated transmission of PUCCH may be indicated to the UE. For example, the RRC parameter 1 may indicate the number of repetitions spaced by the slot, and the RRC parameter 2 may indicate the number of repetitions spaced by the sub-slot. In this case, the UE may apply RRC parameter 2 when PUCCH transmission is expressed in a subslot, and may apply RRC parameter 1 when PUCCH transmission is expressed in a slot.

In addition, an RRC parameter indicating repeated transmission of PUCCH may be indicated differently for each format. In this case, the RRC parameter may be differently indicated to the UE for each format and for each slot/sub-slot. Pre-processing of the PUCCH occasion may be indicated (or set) by TCI state or SRI.

Hereinafter, a case of transmitting a PUCCH occasion in consecutive symbols will be described.

PUCCH instances belonging to the PUCCH occasion include UCI, and the UCI is preferably transmitted to the base station (or TRP) in a short time. This is because the terminal can support URLLC traffic. If the UCI is repeatedly transmitted, the error rate in the TRP may be further reduced, but the delay time may be increased in proportion to the time of the PUCCH occasion. In order to reduce this delay time, it is desirable to reduce the time interval between PUCCH instances.

(Method A.4-4) The time interval between PUCCH instances may have d (d≥0) symbol(s) according to the capability of the UE.

If a PUCCH occasion is transmitted to transmit one TRP, since the PUCCH instances may be identical to each other, they may be transmitted in consecutive symbols (ie, when d=0). If a PUCCH occasion is transmitted to transmit to two or more TRPs, since different preprocessing may be applied for each TRP, the UE may space a predetermined symbol between PUCCH instances. Depending on the capability of the terminal, the value of d may be 0 or may be greater than 0.

14 is a conceptual diagram illustrating a case in which PUCCH is repeatedly transmitted according to an embodiment of the present invention.

The size of the nominal time window may be explicitly or implicitly indicated to the terminal, or may be derived by the terminal based on received information. PUCCH instances having a predetermined interval within a nominal time window may be repeatedly transmitted a predetermined number of times.

A PUCCH instance may not always be transmitted in all symbols belonging to a nominal time window. For example, according to the pattern of the slot, some symbol(s) belonging to the (sub)slot are indicated as DL symbol(s), SSB is transmitted in some symbol(s), or some symbol(s) ) may indicate that the Type0-PDCCH CSS set is transmitted. In this case, some PUCCH instance(s) belonging to the PUCCH occasion may not be transmitted. In this case, the interpretation of the nominal time window described above in (1), (2), and (3) may be applied.

15 is a conceptual diagram for explaining an example of a method of considering a slot boundary when a time interval is provided for each PUCCH instance(s) according to an embodiment of the present invention.

15 shows cases in which some symbol(s) are considered invalid symbol(s) because they cross the boundary of a (sub)slot. Unlike transmission of PUSCH, a PUCCH instance may not be transmitted separately. Accordingly, in case (a) and case (b) of FIG. 15, the third PUSCH instance is not transmitted because some symbol(s) are composed of invalid symbol(s).

(Method A.4-5) If some symbol(s) belonging to a PUCCH instance are considered invalid symbol(s), the corresponding PUCCH instance is not transmitted.

Hereinafter, transmission of a PUCCH occasion in units of (sub) slots will be described. A subslot consists of a smaller number of consecutive symbols than a slot, and the length of the subslot may be indicated (or set) by RRC signaling.

16 is a conceptual diagram illustrating a case of a PUCCH occasion based on a subslot according to an embodiment of the present invention.

Referring to FIG. 16 , a subslot consisting of two symbols (case (a)) or half of a slot (case (b)) may be indicated (or configured) to the UE. The resource index of the PUCCH applied in the subslot may be indicated to the UE. This may be indicated (or configured) using RRC signaling and/or DL-DCI.

The time resource of the PUCCH may be indicated regardless of the boundary of the subslot, and thus may be indicated to exceed the boundary of the subslot. However, according to a certain UCI type or configuration, it may be indicated not to cross the boundary of the subslot. For example, the time resource of the PUCCH for transmitting the HARQ-ACK may be indicated not to exceed the boundary of the subslot (as illustrated in FIG. 16 ). Alternatively, the time resource of the PUCCH for transmitting the CSI may be indicated in units of slots, and may have time resources that exceed the boundary of the subslot.

The following methods may be equally applied not only to the sub-slot but also to the slot. For example, in FIG. 16 , by interpreting that the time resource is allocated to a subslot consisting of 14 symbols, a nominal time window can be interpreted, and the PUCCH resource (or PUCCH instance) is transmitted once per slot or subslot can be

When the UE is instructed to transmit the PUCCH occasion, the subslot to which the first PUCCH instance belonging to the PUCCH occasion belongs may be indicated. For example, when the UCI is SR, the period of the SR may be interpreted as the period of the subslot. For example, when UCI is HARQ-ACK, it may be given as an offset of a subslot as a timing for feeding back HARQ-ACK for PDSCH. As such, when the length of the subslot is indicated (or set) to the UE, repeated transmission may be performed in units of subslots regardless of UCI.

Alternatively, a nominal time window in which repeated transmission is performed may be interpreted differently depending on the UCI type. For example, even when the length of the subslot is indicated (or set) to the UE, when UCI is SR, it is repeatedly transmitted in units of slots, and when UCI is HARQ-ACK, it is repeatedly transmitted in units of subslots. can

When the UE is instructed (or configured) to transmit the PUCCH occasion, the UE may transmit the PUCCH instance in consecutive (sub)slot(s). At this time, in order to reduce the burden of signaling, it is preferable that PUCCH instances are transmitted in the same resources having a predetermined time interval (ie, (sub)slot).

(Method A.4-6) A PUCCH instance is expressed by the same resource index in each (sub) slot, and may be repeated at intervals of the (sub) slot.

17 is a conceptual diagram illustrating a case in which a PUCCH occasion consists of four PUCCH instances according to an embodiment of the present invention.

Referring to FIG. 17, all PUCCH instances can be transmitted because invalid symbol(s) are not included in the nominal time window (or time resource derived from the number of repetitions and the first subslot of the PUCCH instance) indicated to the terminal. . Here, four sub-slots are utilized, which may be included in one or more slot(s).

A PUCCH instance may not always be transmitted in consecutive (sub) slots. For example, in a system operating in TDD, some symbol(s) belonging to (sub)slots are indicated as DL symbol(s) or SSB is transmitted in some symbol(s) according to the slot pattern, It may be indicated that Type0-PDCCH CSS is transmitted in some symbol(s). In this case, some PUCCH instances belonging to the PUCCH occasion may not be transmitted. In this case, the interpretation of the nominal time window described above in (1), (2), and (3) can be applied.

(Method A.4-7) If some symbol(s) belonging to the PUCCH instance are considered invalid symbol(s), the corresponding PUCCH instance is not transmitted.

18 and 19 are conceptual diagrams illustrating a case in which a PUCCH instance cannot be transmitted due to invalid symbol(s) according to an embodiment of the present invention.

18 illustrates a case in which the corresponding PUCCH instance cannot be transmitted because of an invalid symbol belonging to the PUCCH instance. Since invalid symbol(s) are included in the second and third PUCCH instances, the remaining first and fourth PUCCH instances are transmitted, so that the UE can transmit only two PUCCH instances.

On the other hand, the time window may be long interpreted so that the PUCCH occasion has a valid resource by avoiding invalid symbol(s). That is, in order to transmit the PUCCH occasion, the indicated nominal time window may be extended and interpreted.

(Method A.4-8) When some symbols belonging to a PUCCH instance are considered invalid symbols, the corresponding PUCCH instance is not transmitted, but the corresponding PUCCH instance may be transmitted from valid symbols that can be transmitted later.

19 illustrates a case in which only two PUCCH instances are transmitted within the time window indicated to the UE because invalid symbol(s) are included in the second and third PUCCH instances. According to the proposed method (A.4-8), the terminal can interpret the nominal time window longer in consideration of invalid symbols. That is, referring to the case shown in FIG. 19 , since the transmission of the PUCCH instance is pushed back in time, the UE can always transmit the PUCCH instance a guaranteed number of times. To this end, the UE may identify valid symbols by receiving a separate DCI (eg, DCI format 2_0) indicating the format of the slot and transmit a PUCCH occasion in the valid symbols. If the UE is not configured (or instructed) to receive such DCI, valid symbols indicated (or configured) by RRC signaling (ie, semi-static DL symbol, semi-static FL symbol, SSB, T0-PDCCH) Symbols that are not invalid symbols expressed in CSS) can only be transmitted.

(5) How to transmit a split PUCCH instance in some valid symbol(s)

A PUCCH instance may be transmitted in some symbol(s) that are not determined to be invalid symbol(s), and for this, a rate matching procedure in units of symbols may be performed. To this end, it is preferable to distinguish the full PUCCH instance from the split PUCCH instance, and to determine the position of the DM-RS in the split PUCCH instance.

Invalid symbol(s) in the PUCCH occasion may be indicated by RRC signaling and DCI. Alternatively, the invalid symbol(s) of the PUCCH occasion may be indicated only by RRC signaling.

(Method A.5-1) If some symbol(s) belonging to the PUCCH instance are considered invalid symbol(s), UCI may be mapped and transmitted to the symbol(s) excluding invalid symbols in the corresponding PUCCH instance. have. The UE may map UCI only to valid symbol(s). Here, UCI may be channel coded or spread coded. Accordingly, the DM-RS and UCI may be mapped to the symbol(s) to which the PUCCH instance is mapped, except for the invalid symbol(s) from among the symbols belonging to the time window.

(Method A.5-2) Split PUCCH instance and full PUCCH instance may have different formats. When the full PUCCH instance is not transmitted and the split PUCCH instances are transmitted, the split PUCCH instances may consist of a different number of symbols, and the split PUCCH instance may have an arbitrary format. For example, even if the full PUCCH instance has format 1, format 3, or format 4, the split PUCCH instance may have format 0 or format 2. Here, the split PUCCH instance and the full PUCCH instance may be interpreted from the same PRI.

(Method A.5-3) Split PUCCH instance and full PUCCH instance may always have the same format. If not, split PUCCH instance may not be transmitted.

A full PUCCH instance may have a format having one or two symbols, or a format having four or more symbols. According to (Method A.5-3), for a format in which a full PUCCH instance has two symbols, a split PUCCH instance may have one symbol. For a format in which a full PUCCH instance has 4 or more symbols (eg, PUCCH formats 1, 3, 4), a split PUCCH instance may consist of less than 4 symbols. However, according to (Method A.5-3), if the split PUCCH instance consists of less than 4 symbols, since the split PUCCH instance and the full instance may have different formats, the UE does not transmit the split PUCCH instance. may not be In addition, in the case of a specific PUCCH format (eg, PUCCH format 1), it may have two or more arbitrary symbols. In this case, according to (Method A.5-3), if one split PUCCH instance is configured, the UE may not transmit the split PUCCH instance.

The PUCCH instance constituting the PUCCH occasion has a DM-RS. In this case, a DM-RS may be mapped as a PUCCH instance as a unit, and multiple PUCCH instances may become a unit, so that the DM-RS may not be shared. According to the implementation of the base station, DM-RS belonging to several PUCCH instances are temporally related and can be used when estimating a channel, but the terminal does not assume such a base station processing and allocates the DM-RS to the PUCCH instance can do. If the PUCCH instance is transmitted to a split PUCCH instance due to invalid symbols, a DM-RS may be allocated in one split PUCCH instance.

(Method A.5-4) Assuming only valid symbols of the split PUCCH instance, the location of the DM-RS corresponding to the length of the split PUCCH instance is derived.

For a given PUCCH instance, the position and number of DM-RSs with respect to the number of symbol(s) belonging to a full PUCCH instance or a split PUCCH instance may be determined from the technical specification. For example, the technical specification may include Table 1, and the UE may derive the positions of the DM-RS of the PUCCH instance from Table 1 (that is, without separate signaling).

PUCCH length DM-RS position within PUCCH instance No additional DM-RS Additional DM-RS No freq hopping Freq hopping No freq hopping Freq hopping 4 One 0, 2 One 0, 2 5 0, 3 0, 3 6 1, 4 1, 4 7 1, 4 1, 4 8 1, 5 1, 5 9 1, 6 1, 6 10 2, 7 1, 3, 6, 8 11 2, 7 1, 3, 6, 9 12 2, 8 1, 4, 7, 10 13 2, 9 1, 4, 7, 11 14 3, 10 1, 5, 8, 12

In addition, according to Table 1, the DM-RS position of the split PUCCH instance is determined according to the number of symbol(s), and frequency hopping and/or additional DM-RS are higher layer signaling to the UE. can be directed. In this way, the location of the DM-RS for a given split PUCCH instance may be known to the UE.

There may be no limit to the number of symbols of the Split PUCCH instance. Therefore, if the base station determines that the terminal has a high movement speed, or if high quality channel estimation is required, the base station may instruct the terminal to allocate an additional DM-RS through RRC signaling.

(Method A.5-5) The front-loaded DM-RS and additional DM-RS of the Split PUCCH instance may be indicated to the UE.

However, in order to allocate an additional DM-RS, one PUCCH instance must have several symbols. In this case, the UE is instructed to repeat the PUCCH instance having a small number of symbols, so that an additional DM-RS may not be allocated. That is, when transmitted on a PUCCH occasion, the maximum length of the PUCCH instance may be limited so that an additional DM-RS cannot be indicated.

(Method A.5-6) The DM-RS of the Split PUCCH instance consists of a front-loaded DM-RS, and the PUCCH instance may be instructed to have a predetermined length or less so that the additional DM-RS is not indicated to the UE. have. According to the technical standard (or Table 1), when the PUCCH instance has a length of 10, 11, 12, 13, or 14, an additional DM-RS may be indicated. As such, according to (Method A.5-6), a split PUCCH instance may have only 9 or fewer symbols. Here, the specific number may vary according to technical standards.

(Method A.5-7) Frequency hopping for a Split PUCCH instance may or may not be indicated. Whether frequency hopping for the split PUCCH instance is performed through higher layer signaling or DL-DCI may be indicated to the UE. When frequency hopping is not indicated, the UE may use the same frequency resource for all PUCCH occasions. Alternatively, when frequency hopping is indicated, the UE may use different frequency resources for PUCCH instances. Such an operation may be indicated to the UE by DL-DCI or by RRC signaling.

(Method A.5-8) Frequency hopping is not performed within a full PUCCH instance or a split PUCCH instance, and frequency hopping can be performed only between split PUCCH instances or between full PUCCH instances.

Meanwhile, the power applied to the PUCCH occasion may depend on the amount of UCI included in the PUCCH instance, the bandwidth, and the number of symbols. Therefore, the power allocated to the split PUCCH instance and the power allocated to the full PUCCH instance may have different values.

(Method A.5-9) The power applied to the PUCCH occasion is not derived for each split PUCCH instance, and the power calculated for the full PUCCH instance may be equally applied to the split PUCCH instances.

When one full PUCCH instance is divided into two or more split PUCCH instances, a method in which coded UCI mapping is started may be different. In the case of a full instance, the encoded UCI can always be mapped from the first symbol. In the case of the first split instance, the encoded UCI may be mapped from the first position. However, in the case of the second or subsequent split PUCCH instance, the encoded UCI may be mapped from the first position or mapped from an intermediate position other than the first position.

(Method A.5-10) In the case of the second or subsequent split PUCCH instances, the encoded UCI may always be mapped from the same position (eg, the first position or the first index).

The UE can always map to the split PUCCH instance from the front part of the encoded UCI. In this case, if the codeword is composed of systematic bits and parity bits, there is an advantage that the UE can transmit the systematic bits more frequently.

20 and 21 are conceptual diagrams for explaining examples of a method of mapping an encoded UCI to a split PUCCH instance according to an embodiment of the present invention.

Referring to FIG. 20 , since mapping always starts at a fixed position of a split PUCCH instance, if all PUCCH occasions are transmitted only to split PUCCH instances, some bits of the encoded UCI may not always be transmitted. However, since some bits that are not transmitted in this way are highly likely to be parity bits, the error rate obtained by the base station may not be significantly affected.

(Method A.5-11) In the case of the second or subsequent split PUCCH instance, the encoded UCI may be mapped from the position immediately following the position mapped to the split PUCCH instance immediately before it. That is, the terminal may transmit the untransmitted codeword portion without transmitting the already transmitted codeword portion. For example, if the mapping of UCI encoded at the m-th position of a certain split PUCCH instance is finished, mapping of the UCI encoded at the m+1-th position of the next split PUCCH instance can be started. In this case, since the terminal can sufficiently transmit parity bits, the base station can utilize the parity bits for decoding.

Referring to FIG. 21 , the location at which the mapping of the encoded UCI starts may vary for each split PUCCH instance. In this case, the codeword may be received by the base station using several split PUCCH instances. Compared with method (A.5-10), if (method A.5-11) is followed, it may be interpreted that the base station performs soft combining on UCI.

(Example)

22 is a conceptual diagram for explaining a method of considering invalid symbol(s) in PUCCH occasion transmission according to an embodiment of the present invention.

Referring to FIG. 22 , a PUCCH occasion consists of 4 PUCCH instances, some of which may be transmitted as split PUCCH instances according to invalid symbol(s). Here, the PUCCH instance is exemplified as having 4 or more symbols, but is not limited thereto. For example, when UCI has an amount of 2 bits or less, the PUCCH instance may be transmitted in PUCCH format 0 or format 1. In this case, the UE may transmit split PUCCH instances while maintaining the corresponding format. In FIG. 22, each symbol may represent a TCI state of a corresponding PUCCH instance.

According to case (a), the PUCCH instance is transmitted in consecutive symbols, and the method described in (5) may be applied to PUCCH instance 2 and PUCCH instance 3 because of the slot boundary and invalid symbols. Since PUCCH instance 1 and PUCCH instance 4 are transmitted in valid symbols, they are transmitted as full PUCCH instances, and the location of the DM-RS may also be determined according to the standard. PUCCH instance 2 consists of 5 symbols with one symbol excluded due to the boundary of the slot and invalid symbol(s). In PUCCH instance 2, DM-RS is mapped within 5 symbols. In the case of PUCCH instance 3, only one symbol is left by invalid symbols. Here, the split PUCCH instance may be transmitted with only one symbol. Alternatively, if the format of one symbol is changed, the transmission of the split PUCCH instance may be dropped.

According to case (b), the PUCCH instance is transmitted in consecutive subslots, and the method described in (5) may be applied to PUCCH instance 3 because of the boundary of the slot and the invalid symbol. Since PUCCH instance 1, PUCCH instance 2, and PUCCH instance 4 are transmitted in valid symbols, they are transmitted as a full PUCCH instance, and the location of the DM-RS may also be determined according to a standard. In PUCCH instance 3, only one symbol is left because of the boundary of the slot and the invalid symbol. Here, the split PUCCH instance may be transmitted with only one symbol. Alternatively, if the format of one symbol is changed, the transmission of the split PUCCH instance may be dropped.

According to case (c), a predetermined number of PUCCH instances are arranged in consecutive symbols, but a larger number of PUCCH instances may be transmitted with a predetermined interval from each other. The method expressed in (5) can be applied to PUCCH instance 2 and PUCCH instance 3 because of the slot boundary and invalid symbol. Since PUCCH instance 1 and PUCCH instance 4 are transmitted in valid symbols, they are transmitted as full PUCCH instances, and the location of the DM-RS may also be determined according to the standard. PUCCH instance 2 and PUCCH instance 4 are transmitted as split PUCCH instances because of slot boundaries and/or invalid symbols. PUCCH instance 2 is one split PUCCH instance and consists of 5 symbols. In the case of PUCCH instance 3, a split PUCCH instance composed of two symbols may be transmitted as it is. Alternatively, if the split PUCCH instance composed of two symbols has a format different from the full PUCCH instance, transmission may be dropped.

According to case (d), PUCCH instances are transmitted with a predetermined interval, and the method expressed in (5) may be applied to PUCCH instance 2, PUCCH instance 3, and PUCCH instance 4 because of the slot boundary and invalid symbol. . Since PUCCH instance 1 is transmitted in valid symbols, it is transmitted as a full PUCCH instance, and the location of the DM-RS may also be determined according to the standard. PUCCH instance 2 and PUCCH instance 4 are transmitted as split PUCCH instances because of slot boundaries and invalid symbols. PUCCH instance 2 is composed of 4 symbols as one split PUCCH instance. PUCCH instance 4 may be composed of a split PUCCH instance composed of two 4 symbols and a split PUCCH instance composed of two symbols. Here, the split PUCCH instance having two symbols may be transmitted as it is, or transmission may be dropped because it has a format different from that of the full PUCCH instance. In the case of PUCCH instance 3, it may be configured as one split PUCCH instance composed of three symbols due to invalid symbols. The split PUCCH instance may be transmitted as it is, or if it has a format different from that of the full PUCCH instance, transmission may be dropped.

B. How to determine transmit power in UL repetition

(1) Method of determining transmission power of SRS resource and PUSCH

In order to control the transmission power applied to the SRS resource corresponding to the SRI, the base station may estimate each path loss for each SRS resource. The base station may control transmission power for SRS resources by using DCI. DCI may be a scheduling DCI (eg, DCI format 0_0, 0_1, 0_2, or DCI format 1_0, 1_1, 1_2), and may be a group common DCI (GC-DCI) (eg, DCI format 2_3, or DCI format 2_2). have. By indicating to the terminal an index (TPC command) indicating transmission power as a field value of DCI, the terminal may increase or decrease the transmission power. In order to determine the power applied to the PUSCH, the UE may reflect the bandwidth of the PUSCH indicated by the DCI in addition to the value obtained by the path attenuation and the value reflecting the field value of the DCI.

The terminal may receive two or more sets of transmit power parameters from the base station using higher layer signaling. Elements constituting each set are transmit power parameter(s), and each set may have transmit power parameter(s) suitable for different scenarios (eg, URLLC or eMBB). The UE may be instructed with a transmission power parameter set to be applied in scheduling DCI or activating DCI for allocating PUSCH. When the transmit power parameter set is changed, for example, the magnitude of the increase/decrease in transmit power indicated by the same TPC command may be different in the terminal.

In the case of T1 CG and T2 CG, transmission power for the SRI associated with the PUSCH instance may be applied using a value indicated using DCI 22 (or DCI 23). In the case of T2 CG, the activating DCI may indicate a set of transmission power parameters to be applied to the PUSCH occasion. Thereafter, the UE receives the TPC command using GC-DCI and appropriately interprets the indicated transmission power parameter set, thereby deriving the transmission power applied to the PUSCH instance. The PUSCH may be transmitted using preprocessing (or beam) based on the SRI configured for the UE.

In the case of a dynamically scheduled PUSCH, the UE may derive the transmission power applied to the PUSCH instance by combining the GC-DCI and the scheduling DCI. It may be assumed that the UE stores the TPC command for PUSCH by using GC-DCI. In the case of a dynamically scheduled PUSCH, the scheduling DCI may indicate a set of transmission power parameters and a TPC command to be applied to the PUSCH occasion. The UE may transmit the PUSCH instance by using preprocessing (or beam) for the SRI associated with the PUSCH instance.

(2) TPC analysis method in PUSCH repetition

A PUSCH occasion may consist of two or more PUSCH instances, and when operating according to an mTRP scenario, each PUSCH instance may be transmitted using different TRPs. In this case, the radio channel formed by the terminal and each TRP may have different characteristics.

(Method B.2-1): Different transmission powers may be applied to PUSCH instances corresponding to (or mapped to) different TRPs (or TCI states or RSs).

Multiple SRIs may be configured and activated for the UE, and different transmission powers may be managed for each SRI. According to (Method B.2-1), since the PUSCH instance can be independently instructed by the SRI, the UE can apply different transmission powers for each SRI.

When a PUSCH occasion is indicated by one DCI (ie, a scheduling DCI or an activating DCI), it is preferable that the UE be able to derive transmission power for all PUSCH instance(s) belonging to the PUSCH occasion. In addition, the UE may receive information on the transmission power for the PUSCH occasion also through the group common DCI.

(Method B.2-2): A TPC command is independently indicated for each different TCI state (or SRI) associated with (or mapped or corresponding to) a PUSCH instance by a field related to the TPC of DCI, and the TPC commands are concatenated can be directed.

23 is a conceptual diagram illustrating an example of a field of DCI to which TPC commands are concatenated according to an embodiment of the present invention.

Referring to FIG. 23 , the length of the field indicating the TPC of DCI may increase in direct proportion to the maximum number of PUSCH instances belonging to the PUSCH occasion. DCI may include a TPC command for each PUSCH instance. From the bit string included in the DCI field, the UE must interpret the TPC commands according to the order of the TRP (ie, the order of the SRI). In the conventional technical standard, it is defined that the TPC command has a size of 2 bits. Accordingly, if this definition is applied as it is, the TPC field may be expressed as a bit string having a length twice the number of TRPs.

(Method B.2-3): When (Method B.2-2) is applied, the terminal has a TPC command for a specific TRP (ie, each RS included in the SRI or TCI state) in the TPC field of DCI. It can be interpreted as indicating to the terminal by higher layer signaling at a predetermined location.

For example, a specific position of the field indicating the TPC command may include a TPC command for a specific PUSCH instance. If there are two SRIs, the UE may indicate (or set) information on TRP1 in CORESET belonging to CORESETpoolIndex1, and may indicate (or set) SRI1 mapped (or related) thereto. In the same way, information on TRP2 may be indicated (or set) in CORESET belonging to CORESETpoolIndex2, and SRI2 mapped (or related) thereto may be indicated (or set) to the UE. Here, SRI1 and SRI2 may indicate SRS interpreted as a TCI state according to an indication (or setting) of a base station. However, it is not limited thereto, and SRI1 and SRI2 may indicate a DL RS (eg, SSB, TRS, CSI-RS) associated therewith (or mapped). The TCI state set (or indicated) to the UE consists of two RSs, and each RS may correspond (or map) to each TRP (or CORESETpoolIndex).

For example, if the TCI state indicated to the UE is expressed as (SRI1, SRI2), the spatial filter indicated by SRI1 is applied to the PUSCH instance transmitted to TRP1 (or CORESETpoolIndex1), and the space indicated by SRI2 The filter may be applied to the PUSCH instance transmitted to TRP2 (or CORESETpoolIndex2).

Values of TPC command 1 for PUSCH instance related to SRI1 and TPC command 2 for PUSCH instance related to SRI2 may be concatenated and included in DCI. Here, the DCI may be a scheduling DCI or a group common DCI including a TPC command.

The PUSCH instance to which the TPC command 1 of FIG. 23 is applied may be determined by RRC signaling, and the PUSCH instance to which the TPC command 2 of FIG. 23 is applied may be determined.

(Method B.2-4): When (Method B.2-2) is applied, the UE determines the order of TPC commands in the TPC field of DCI in the order of TRP (or order of SRI or RS included in the TCI state) order) can be derived.

For example, according to the allocation for the PUSCH occasion by DCI, the order of PUSCH instances may be different from the order of TRPs (or the order of CORESETpoolIndex or the order of SRI). In one example, DCI may be given so that the order of SRIs (or TCI state) applied to PUSCH instances corresponds to the order of TRPs. That is, the order of TPC commands applied in the TPC field may follow the order of TRPs as it is.

When there are two TRPs, a PUSCH occasion is allocated in DCI, and the order of SRIs (or TCI state) applied to each PUSCH instance may be indicated. That is, with respect to SRI1 mapped to TRP1 and SRI2 mapped to TRP2, according to DCI, the order of SRI1 and SRI2 or the order of SRI2 and SRI1 may be applied (or mapped) to the PUSCH instance.

Interpretation of the TPC field included in DCI is divided into TPC command 1 and TPC command 2 in FIG. 23, and is applied to SRI1 and SIR2 (or TRP order, or CORESETpoolIndex order), respectively. That is, in the case of (SRI1, SRI2), TPC command 1 may be applied to a PUSCH instance corresponding to SRI1, and TPC command 2 may be applied to a PUSCH instance corresponding to SRI2. In the case of (SRI2, SRI1), TPC command 1 may be applied to a PUSCH instance corresponding to SRI2, and TPC command 2 may be applied to a PUSCH instance corresponding to SRI1.

According to the method (B.2-2), the size of the TPC field should increase according to the number of TRPs (ie, the number of SRIs to be indicated). Since scheduling allocating to utilize only a portion of TRP in DCI may also occur, it is desirable to reduce the average size of DCI. Therefore, it is preferable that the given TPC field can be utilized differently according to the size of the SRI field (or the size of the field indicating the TCI state) used in the PUSCH occasion. In addition, it is preferable to be able to indicate TPC commands for two or more SRIs while maintaining the size of the TPC field.

(Method B.2-5): One TPC command may be indicated for a PUSCH occasion in the TPC field of DCI.

DCI includes one TPC command, and the UE may apply it to all PUSCH instances belonging to a PUSCH occasion. For example, when a large increase/slight increase/decrease/maintenance is indicated through the TPC command in scheduling/activating DCI, the UE may apply the same TPC command to all PUSCH instances. This method has a limited degree of freedom of transmission power control, but does not increase the size of the TPC field of DCI.

(Method B.2-6): The number of bits in which a part of the TPC field of DCI expresses the TPC command for the PUSCH instance may be reduced in inverse proportion to the number of TRPs.

)은

또는

비트의 크기를 가질 수 있다. 2개의 TRP들에게 PUSCH occasion을 전송하는 경우, 2개의 SRI들에 대한 TPC command들이 DCI이 포함되어야 한다. TPC 필드의 크기가 2비트로 고정된 경우, 각각의 SRI에 대한 TPC command는 1 비트의 크기를 가질 수 있다. 이러한 방법은, 1개의 TRP에게 PUSCH occasion을 전송할 때에 필요한 TPC 필드의 크기와 2개의 TRP에게 PUSCH occasion을 전송할 때에 필요한 TPC 필드의 크기가 동일하다는 장점을 가진다.When the TPC field of DCI is given with N bits, TPC command m (

)silver

or

It can have the size of bits. When transmitting a PUSCH occasion to two TRPs, DCI must be included in TPC commands for two SRIs. When the size of the TPC field is fixed to 2 bits, the TPC command for each SRI may have a size of 1 bit. This method has the advantage that the size of the TPC field required when transmitting the PUSCH occasion to one TRP and the size of the TPC field required when transmitting the PUSCH occasion to two TRPs are the same.

However, in the case of one TRP and two TRPs, there is a difference in how to interpret the TPC field. The TPC command of the PUSCH occasion for one TRP may indicate four cases, but the TPC commands of the PUSCH occasion for two TRPs may indicate only two cases, respectively.

In one example, the MSB of the TPC field of the DCI indicates TPC command 1 of the PUSCH occasion for the first TRP, and the LSB of the TPC field of the DCI indicates the relative offset for determining the TPC command2 of the PUSCH occasion for the second TRP. can TPC command 2 is determined by the sum of TPC command 1 and relative offset. For example, assuming that TPC command 1 is indicated to increase/maintain, and the relative offset is indicated to increase/decrease, when TPC command 1 is indicated as 'increase', TPC command 2 increases from 'increase' to a value ( That is, it can be interpreted as a significant increase (eg, +4 dB) or a decrease in 'increase' (ie, hold, eg, 0 dB). If TPC command 1 is indicated as 'maintain', TPC command 2 is an increased value in 'maintain' (ie, increases, eg, +1 dB) or decreases in 'maintain' (ie, decreases, eg, -1 dB). can be interpreted as

In this case, TPC command 1 may be composed of two types, but TPC command 2 may be composed of four types. Therefore, it is desirable to adjust the order of SRIs in the TCI state field so that, if transmission power for a certain SRI is to be maintained, TPC command 2 can be used for the corresponding SRI.

(Method B.2-7): The TPC field of DCI may indicate an index indicating a combination of TPC commands (TPC index).

The TPC index may indicate TPC commands applied to one or more PUSCH instances. The size of the TPC index may be derived from the maximum number of RSs constituting TCI states configured for the UE or the maximum number of PUSCH instances that a PUSCH occasion may include.

The base station may set combinations of TPCs to the terminal through higher layer signaling. When a maximum of M TRPs are given, the values of the TPC command i (i = 1,2, ..., M) for TRP i (or the i-th RS of RS pairs expressing the TCI state) are from one index. can be derived.

Here, DCI may be GC-DCI as well as scheduling/activation DCI. In the case of GC-DCI, the UE may receive from the base station through additional higher layer signaling, receive an indication (or set) of a determined location, and recognize the TPC index in the GC-DCI payload of the corresponding location.

24 is a conceptual diagram illustrating an example of configuring a TPC field with a TPC index indicating a combination of TPC commands according to an embodiment of the present invention.

24 , the TPC field of DCI may indicate a TPC index. From the TPC index, the UE may derive (TPC command 1, TPC command 2, ..., TPC command M). For convenience of description, one combination of TPC commands (TPC command 1, TPC command 2, ..., TPC command M) may be described as corresponding to one “TPC state”.

When two TRPs are given (or when the TCI state is expressed by two or more RSs and is indicated to the terminal), (TRP1, TRP2) (or an ordered pair of RSs indicated in the TCI state) The TPC index increases / decreases / There can be 3 ² (=9) cases that hold. At this time, according to (Method B.2-7), the TPC field can represent all 9 cases using 4 bits. This corresponds to a smaller number than the 16 cases represented by 4 bits.

Also, 4 bits are needed when the TPC field complies with (Method B.2-2). However, if a part of the TPC state is omitted, since the number of TPC states to be expressed by the TPC index can be reduced to 8 or less, by applying (Method B.2-7), the size of the TPC field of DCI is reduced to 3 bits. can be reduced below. For example, it may not indicate a TPC state that reduces both transmission power for TRP1 and TRP2, and other TPC states may be expressed by eight indices.

^{When three TRPs are given, there may be 3 3} (=27) cases in which the TPC index for (TRP1, TRP2, TRP3) is increased/decreased/maintained. In this case, according to (Method B.2-7), all 27 cases in which the TPC field is smaller than the 32 cases expressed using 5 bits can be expressed. On the other hand, when the TPC field follows (Method B.2-2), a TPC field with a size of 6 bits that is directly proportional to the number of TRPs is required. However, if some of the TPC states are omitted, the size of the TPC field of DCI is reduced to 4 bits or less by applying (Method B.2-7) when the number of TPC states that the TPC index must express is reduced to 16 or less. can

In one example, some of the TPC states for reducing/maintaining the transmission power for two or more TRPs may not be indicated by the TPC index. The reason is that in order to reduce the error rate of the PUSCH occasion, the TPC index that rapidly increases the transmission power may be needed more frequently. In this case, one TPC state to reduce the power of two TRPs and six TPC states to reduce the power of two TRPs, one TPC state to reduce the power of two TRPs, six TPC states to maintain the power of two TRPs, and the power of three TRPs One TPC state may be required. Accordingly, ^{13 TPC states except for 14 TPC states among 3 3} (=27) TPC states may be expressed using TPC indices. In order to express with 4 bits (ie, 16 TPC indices), three TPC states among the excluded TPC states may be additionally mapped to TPC indices, and additionally, the TPC state is not allowed and left as a reserved state. may be

(Method B.2-8): Depending on the number of TRPs used in the PUSCH occasion (or the number of RSs or the number of SRIs indicated in the TCI state), the TPC index may be interpreted differently.

The size of the TPC field of DCI may be determined by RRC signaling, and the value is determined from the maximum number of TRPs that the PUSCH occasion has (or the number of RSs, the number of SRIs, or the number of PUSCH instances indicated in the TCI state). can be derived. In DCI, since the UE dynamically controls the TCI state (or the number of TRPs) to be applied on the PUSCH occasion, a method for the UE to interpret the TPC field may vary. In order to interpret the TPC field, the UE may refer to the TCI state, and the method of interpreting the TPC field may vary according to the TCI state.

Therefore, when the number of TRPs of a smaller number (or the number of RSs, the number of SRIs, or the number of PUSCH instances indicated in the TCI state) is indicated, the TPC index indicated by the TPC field is interpreted as a different meaning for the terminal. can

For example, for a PUSCH occasion in which up to three TRPs are utilized, the TPC field of DCI may have a fixed size. When allocating a PUSCH occasion in DCI, 1, 2, or 3 TRPs may be utilized, and the number of utilized TRPs is the number of RSs, the number of SRIs, or the number of PUSCH instances indicating to the UE in the TCI state. can be derived from the number. At this time, the UE interprets the TPC field as a TPC index indicating the TPC state for the PUSCH occasion in which three TRPs are used (ie, (Method B.2-7)), but on the PUSCH occasion in which two TRPs are used For this, it can be interpreted that the TPC field includes TPC commands for each TRP rather than the TPC index (ie, (Method B.2-2). Similarly, for the PUSCH occasion in which one TRP is utilized, the terminal The TPC index can be interpreted as a TPC command as it is.

For example, the MSB or LSB of the TPC index indicated to the terminal may be interpreted as a TPC command. The base station may set 6 bits or less to the terminal as the size of the TPC field expressing the TPC index.

When the size of the TPC field is 6 bits (eg, (b6, b5, b4, b3, b2, b1)), when the UE derives the number of TRPs from the TCI state and receives three TRPs, the TPC field is each It can be interpreted as TPC commands for TRPs. (b6, b5) is applied to the first RS of the TCI state, (b4, b3) is applied to the second RS, and (b2, b1) is applied to the third RS, so that a PUSCH occasion can be transmitted.

When two TRPs are indicated, the MSB or LSB of the TPC field may be interpreted as TPC commands for each TRP. When MSB is applied, (b6, b5) is applied to the first RS of the TCI state, and (b4, b3) is applied to the second RS, so that a PUSCH occasion can be transmitted. When the LSB is applied, (b4, b3) is applied to the first RS of the TCI state, and (b2, b1) is applied to the second RS, so that a PUSCH occasion can be transmitted. Even when one TRP is instructed, the same method can be applied. Alternatively, when two or less TRPs are indicated, the TPC command for each TRP may be interpreted at a predetermined position in the TPC field. Depending on the configuration of the base station, for example, (b2, b1) is applied to the first RS of the TCI state, and (b6, b5) is applied to the second RS to transmit a PUSCH occasion. This location may be indicated (or configured) to the UE by RRC signaling.

When the size of the TPC field is 4 bits (eg, (b4, b3, b2, b1)), when the terminal is instructed to receive three TRPs by deriving the number of TRPs from the TCI state, the TPC field is a TPC index. can be interpreted. A TPC command may be applied to each RS in the TCI state by the TPC index configured (or indicated) for the UE, so that a PUSCH occasion may be transmitted. On the other hand, if two or less TRPs are indicated, since the size of the TPC field is sufficient, the TPC field may be interpreted as including TPC commands for each TRP. As described above, to which TRP (or RS) each 2 bits are mapped (or associated) in the TPC field follows the setting of the base station or is fixed in the technical standard, so a separate indication may not be required. For example, (b4, b3) may be applied in the first RS of the TCI state, and (b2, b1) may be applied in the second RS. For example, (b2, b1) may be applied in the first RS of the TCI state, and (b4, b3) may be applied in the second RS. For example, if only one RS is indicated in the TCI state, a PUSCH occasion may be transmitted by applying (b4, b3) or (b2, b1).

For example, for a PUSCH occasion in which up to two TRPs are utilized, the TPC field of DCI may be indicated (or configured) to have a fixed size. For example, with RRC signaling). The same field is applied to the PUSCH occasion in which one or two TRPs are utilized. In this case, the UE interprets the TPC state that can be expressed by the TPC index for the PUSCH occasion in which two TRPs are used (ie, method B.2-7), and for the PUSCH occasion in which one TRP is utilized, the TPC command is It can be interpreted as given in part of the TPC field (ie, MSB or LSB) (ie, method B.2-2).

(Method B.2-9): A state indicating transmit power for TRP(s) may be expressed as a relative offset in which a TPC command for at least one TRP is relative to another TRP.

It may not be necessary to indicate the TPC commander in the same unit for all radio links that the terminal has with the TRPs. For example, a TPC command is indicated in a fine unit for a standard TRP, but other TRPs indicate an offset for the standard TRP, so that the TPC command for the corresponding TRP is derived from the offset and the standard TPC command. can For example, TPC command 2 may be derived by adding the relative offsets for TPC command 1 and TPC command 1. As an example, the relative offset may be expressed only by increasing/decreasing/maintaining rather than numerical values. As an example, the reference TRP may be the TRP corresponding to the first SRI in the TCI state indicated by the TCI state field of the DCI.

While TPC command 1 for TRP 1 as a reference indicates one of the four cases of greatly increasing/slightly increasing/decreasing/maintaining, the offset for TRP 2 increases/decreases/maintains as a relative value for TRP 1. In the following three cases, one can be indicated. According to (Method B.2-9), TPC command 2 can be obtained by adding a relative offset from TPC command 1. TPC command 1 and TPC command 2 should be able to be interpreted by the terminal in the same range. That is, when TPC command 1 means the largest value (eg, +4 dB), the base station instructs the terminal to increase more than +4 dB as a relative offset, or TPC command 2 means the smallest value (eg, -1 dB), the base station may not instruct the terminal to decrease more than -1 dB as a relative offset. Since such an offset is not indicated, the number of TPC states to be expressed may be reduced.

For example, for a PUSCH occasion in which two TRPs are utilized, TPC command 1 for TRP1 is given, and TPC command 2 for TRP2 can be derived from TPC command 1 using an offset for TPC command 1. For example, if the TPC command for TRP1 indicates 4 cases and the offset for TRP2 indicates 3 cases, a total of 12 cases may be expressed. Here, except when the power to TRP2 is further increased when the power to TRP1 is greatly increased, and when the power to TRP1 is decreased, the power to TRP2 is further decreased (i.e. two cases), 10 A TPC index representing the TPC states of the branch may be indicated in the TPC field of DCI.

For example, for a PUSCH occasion in which three TRPs are utilized, TPC command 1 for TRP1 is given, and TPC command i (i=2, 3) for TRPi may be given as an offset for TPC command 1. For example, if the TPC command for TRP1 indicates 4 cases and the TPC command for TRPi (i=2,3) indicates 3 cases, 36 TPC states may be expressed. Here, when the transmit power for TRP1 is greatly increased, the case where the transmit power for the other TRP increases more than this, and the case where the transmit power for the other TRP is further reduced when the transmit power for TRP1 decreases (i.e., 10 branch), a TPC index representing 26 TPC states may be indicated in the TPC field of DCI.

(3) TPC analysis method in PUCCH repetition

In (1) and (2), a method of defining a TPC state for transmitting a PUSCH instance has been described, but the same method may be applied to repeatedly transmitting a PUCCH. That is, in group common DCI (eg, DCI format 2_2) or scheduling DCI/activating DCI indicating the TPC command of PUCCH, the methods described in (1) and (2) may be used as they are.

C. Setting method of pre-processing in UL repetition

(1) Operation of a terminal supporting multiple beams

A terminal may have one or more antenna panels. A method for the terminal to use the multi-panel may be divided into several types. In any terminal, only one panel is activated, and a predetermined time (eg, several ms) may be required for panel change/activation. One or more panels are simultaneously activated in a certain terminal, and the terminal may perform transmission/reception using one or more panels. Although one or more panels are simultaneously activated in a certain terminal, transmission and reception can be performed using only one panel at a time.

The base station sets TCI state(s) to the terminal by using higher layer signaling, and one TCI state among them may be used for transmission of a PUSCH or PUSCH occasion. The TCI state index means one TCI state, and the base station may indicate the TCI state index to the terminal by using DCI. Here, the TCI state may indicate an RS pair (or a pair of antenna ports corresponding to RS) or TPMIs. Alternatively, the RS pair may correspond to the TPMI.

(Method C.1-1): The TCI state is given by an RS pair consisting of a source RS and a target RS and two or more RS pairs, and may mean a quasi-co-location (QCL) type of the RS pair.

The TCI state is expressed as a TCI state index, and the TCI state represents one or more combinations. Here, the combination may include at least a reference RS and a corresponding QCL in a relationship between the target RS of the TCI state and the QCL. The number of combinations that can be indicated by the TCI state (that is, the number of pairs of reference RS and target RS) is indicated (or set) to the UE by higher layer signaling as a maximum value, or the TCI state is indicated to a higher layer (or set) By doing so, it can be implicitly instructed to the terminal.

An example in which the TCI state is expressed by up to two pairs to the UE may be shown in Table 2. The TCI state is indicated to the UE by higher layer signaling, and represents an example composed of M TCI states. The UE may be instructed with two or less RS pairs. According to the TCI state index 1, the PUSCH DM-RS and the SRS resource configured for beam management in the first RS pair have a QCL relationship, and there is no particular information in the second RS pair. Accordingly, when TCI state index 1 is indicated, the UE applies the preprocessing applied in the SRS resource for beam management to the PUSCH when transmitting the PUSCH. According to TCI state index 2, the PUSCH DM-RS and the CSI-RS resource have a QCL relationship in the first RS pair, and the PUSCH DM-RS and the SSB have a QCL relationship in the second RS pair. The UE may derive preprocessing to be applied when transmitting the PUSCH by combining it with other information of DCI. For example, when transmitting PUSCH using two panels, the UE may interpret preprocessing to be applied to each panel. For example, when the PUSCH is repeatedly transmitted, the UE may interpret the preprocessing to be applied in each transmission.

In Table 2, only the PUSCH DM-RS is exemplified, but the PUCCH DM-RS is also applicable, and it is also applicable to other QCL types other than spatial relation. In addition, in order to apply the QCL type to each of two or more RS pairs, the QCL type may be included in the TCI state for each RS pair.

When only QCL type 1 is instructed (or set) to the UE, or both QCL type 1 and QCL type 2 are instructed (or set) to the UE, QCL type 2 may mean QCL type D. In this case, in the (Source RS, Target RS) pair in Table 2, two source RSs are given and correspond to QCL type 1 and QCL type 2, respectively, and can be interpreted by the UE as a relationship with the target RS.

If both the TCI state and the TPMI are provided to the UE, the UE may determine each preprocessing for the PUSCH instance according to the mapping relationship between the RS and the TPMI indicated in the TCI state, and transmit it to the base station. If two or more RS pairs are indicated to the UE in the TCI state, two or more TPMIs may be indicated to the UE. In this case, the UE may determine preprocessing for the PUSCH instance by combining the RS pair and the TPMI.

In DCI received by the UE, the TCI field (or SRI field) implies transmission for only one TRP, but TPMIs may be indicated. In this case, for the same TCI state (or SRI), the UE may determine preprocessing for applying the TPMIs to the PUSCH instance in order or according to a predetermined rule.

TCI state index (Source RS, Target RS) pair 1 (Source RS, Target RS) pair 2 QCL type One (SRS resource for BM, PUSCH DM-RS) Not applicable Spatial relation 2 (CSI-RS resource, PUSCH DM-RS) (SSB, PUSCH DM-RS) Spatial relation ... ... ... ... ... ... ... ...

(2) Interpretation method of TCI state in PUSCH repetition

For application in the mTRP scenario, it is preferable in terms of obtaining a multiplexing gain to apply a different TCI state to each PUSCH instance while allocating a PUSCH occasion in one DCI. When operating in FR2 (frequency range 2), a beam suitable for one TRP may be formed in the pre-processing applied to the panel by the terminal. That is, when the terminal has several panels, it is preferable to indicate the TCI state differently for each panel. In addition, in PUSCH repetition type A and/or PUSCH repetition type B, a TCI state may be differently indicated according to a PUSCH instance. For convenience of explanation, the number of PUSCH instances included in the time domain resource allocation (TDRA) of DCI (ie, the number of SLIVs, or the number of L) or split PUSCH instances generated at the boundary of the slot and the boundary of invalid symbols The number may be referred to as K, and the number of PUSCH instances that the TCI state index of DCI means may be referred to as M.

A TCI state in which DCI is composed of two or more RS pairs may indicate to the UE. In this case, the UE may transmit the m-th PUSCH instance by using the m-th RS pair and/or the TPMI mapped (or associated) therewith (m=1,2, ...,M). For convenience of description, the QCL relationship derived from each RS pair constituting the TCI state and preprocessing (or TPMI) applied to the PUSCH instance is also referred to as a TCI state.

(Method C.2-1): Transmission power applied to the PUSCH instance may be determined by applying the methods described above.

(Method C.2-2): A time resource applied to a PUSCH instance may respectively correspond to m SLIVs indicated by a TDRA of DCI.

M), PUSCH instance들에 적용되는 전처리는 DCI의 TCI state 필드에서 지시한 TCI state들에 각각 순서대로 대응될 수 있다.(Method C.2-3): If K is not greater than M (K

M), preprocessing applied to PUSCH instances may correspond to TCI states indicated in the TCI state field of DCI in order, respectively.

If K=M, the SLIV of the TDRA and the TCI state of the TCI state may be interpreted as a one-to-one correspondence. If K<M, the SLIV of the TDRA corresponds to the TCI state of the TCI state, and some TCIs do not correspond to the SLIV, but the UE may determine the SLIV and TCI state of the PUSCH instance. The reason is that it can be assumed that the number of PUSCH instances constituting the PUSCH occasion is K.

However, when K>M, a method of determining the SLIV corresponding to the TCI state indicated by the TCI state is required. The allocation of these PUSCH occasions occurs frequently. This is because a small number (eg, two) of TRPs are usually deployed in the mTRP scenario, and the PUSCH is repeatedly transmitted 8 or 16 times in the URLLC scenario.

(Method C.2-4): When K is greater than M (K > M), the preprocessing applied to PUSCH instances is to cyclically expand the TCI states indicated in the TCI state field of DCI and convert them to K in order can be responded to.

That is, the M TCI states may be cyclically extended to generate K-M TCI states. For example, when TCI state 1, TCI state 2, ..., TCI state M is given in the TCI state field, TCI states corresponding to TCI state (M+1), ..., TCI state K are respectively TCI State 1, TCI state 2, ..., may be given as a TCI state (KM).

(Method C.2-5): When K is greater than M (K > M), the pre-processing applied to PUSCH instances is that the TCI states indicated in the TCI state field of DCI are repeatedly expanded and converted into K in order can be matched.

또는

회 반복될 수 있다. TCI state m이

회씩(또는

회씩) 반복되고(m=1,2,...,M-1), TCI state M이

회(또는

회) 반복될 수 있다.That is, M TCI states may be repeatedly extended to generate KM TCI states. For example, when TCI state 1, TCI state 2, ..., TCI state M is given in the TCI state field, one TCI state is

or

can be repeated several times. TCI state m

each time (or

times) is repeated (m=1,2,...,M-1), and the TCI state M is

times (or

times) can be repeated.

(Method C.2-6): When K is greater than M (K > M), or in a combination of all K and M, preprocessing applied to PUSCH instances is applied to the TCI states indicated in the TCI state field of DCI. A corresponding method may be indicated (or configured) by higher layer signaling, and one of (Method C.2-4) and (Method C.2-5) may be indicated.

When a predetermined time is required for the UE to change the TCI state, (Method C.2-4) consumes a lot of time because the TCI state is changed for each PUSCH instance, but in (Method C.2-5), several Since the TCI state can be changed for each PUSCH instance, less time is consumed. In (Method C.2-6), the base station may select this method by higher layer signaling and instruct the terminal.

When several preprocesses (eg, TCI state or SRI or TPMI) are indicated to the UE, TAs of PUSCH instances may all have different values. In this case, PUSCH instances may be arranged in the order of the longer TAs. The reason is that when a PUSCH instance with a shorter TA is deployed earlier, a problem occurs in which a part of the last symbol of a previous PUSCH instance overlaps in time with a part of the first symbol of a subsequent PUSCH instance in some PUSCH instances. Therefore, the order of the preprocessing(s) may be determined by the length of the TA(s) regardless of the order of the preprocessing(s) to be applied to the PUSCH occasion.

(Method C.2-7): The order of the pretreatment(s) may be determined by the length of the TA(s) regardless of the order of the pretreatment(s) to be applied to the PUSCH occasion.

(3) Interpretation method of TCI state in PUCCH repetition

In (1) and (2), a method of defining a TCI state for transmitting a PUSCH instance has been described, but the same method may be applied when repeatedly transmitting a PUCCH. That is, in the case of including the RS pair together with the QCL type in a spatial relation in the RRC information element that sets the PUCCH resource, when repeatedly transmitting the PUCCH, the TCI state(s) (or SRI) ) or pretreatment(s) may be applied. Here, when the number of antenna ports used by the PUCCH is one, preprocessing may be derived only with the TCI state without the TPMI.

When multiple TCI states, pre-processes, or SRIs are indicated to the UE, TAs of PUCCH instances may all have different values. In this case, the PUCCH instances may be arranged in the order of the TA being longer. The reason is that, when a PUCCH instance with a shorter TA is disposed ahead, a portion of the first symbol of the PUCCH instance followed by a portion of the last symbol of the preceding PUCCH instance in some PUCCH instances temporally overlaps because a problem occurs. Therefore, the order of the preprocessing(s) may be determined by the length of the TA(s) regardless of the order of the preprocessing(s) to be applied to the PUSCH occasion.

(Method C.3-1): The order of the pretreatment(s) may be determined by the length of the TA(s) regardless of the order of the pretreatment(s) to be applied to the PUCCH occasion.

(4) How to change the TCI state in PUCCH repetition

The UE is set with respect to preprocesses (ie, spatial relation information) applied to PUCCH by higher layer signaling, and when some of them are activated, the activated preprocessing may be applied. The UE may be instructed with an RS or SS/PBCH block applied to preprocessing as part of PUCCH resource configuration.

25 to 29 are conceptual diagrams illustrating configuration examples of MAC CE for changing spatial relation information applied to PUCCH according to an embodiment of the present invention.

In FIG. 25, an example of MAC CE for instructing the UE to have one TCI state, preprocessing, or SRI is shown in the base station. The corresponding MAC CE includes information on the serving cell in which the PUCCH resource is defined (ie, serving cell ID) and information on BWP (ie, BWP ID), and may include preprocessing information. The terminal may receive the PDSCH including the MAC CE illustrated in FIG. 25 and transmit the HARQ-ACK thereto to the base station. The changed PUCCH pre-processing may be applied after a predetermined time. In FIG. 25 , 'R' means a bit in which information is not loaded (or a bit having a fixed value), and spatial relation info ID means an index or identifier required to determine preprocessing.

When the PUCCH transmitted by the UE is received by two or more TRPs, two or more TCI states may be indicated in the MAC CE that changes the preprocessing of the PUCCH. For convenience of explanation, two pre-processes are considered, but it can be easily extended to a larger number of pre-processes. Methods for this are described below.

(Method C.4-1): The first pre-processing among the two pre-processes of the PUCCH resource given by the MAC CE may be changed, or both the first pre-processing and the second pre-processing may be changed.

The base station may change the first preprocessing of the PUCCH resource, and may also change the second preprocessing if necessary. The MAC CE used at this time (eg, MAC CE of FIG. 26 ) may have a form in which the last octet is additionally added to the MAC CE of FIG. 25 . The MAC CE of FIG. 26 may have a form that does not use _{C 0 , which will be described later.} Here, the positions of R (reserved) and the positions of spatial relation information may be changed.

_{On the other hand, the value of C 0} may indicate the preprocessing(s) to be changed. For example, if C ₀ has any one value, the proposed MAC CE indicates to change only the first preprocessing, but if C ₀ has a different value, the MAC CE may indicate to change both preprocesses. . The size of the MAC CE (ie, the MAC CE of FIG. 25 ) for changing only one preprocessing may be changed by _{C 0 .} For example, since the MAC CE illustrated in FIG. 27 includes the MAC CE of FIG. 25, the size of the MAC CE is conditionally extended to change the second preprocessing. Accordingly, MAC CE may have two sizes according to the value of _{C 0 .}

If the base station applies (method C.4-1) to change only one of the two preprocesses, inefficiency occurs when only the second preprocessor is changed. In this case, this is because the MAC CE of FIG. 27 includes both information on the first preprocessing and information on the second preprocessing. To solve this, MAC CE for changing only the second preprocessing of the PUCCH resource may be required.

(Method C.4-2): Using any one bit (Ci) of the MAC CE, only one of the two preprocesses of a given PUCCH resource may be changed.

The MAC CE illustrated in FIG. 28 includes a new bit Ci. If Ci has any one value, the first preprocessing of the PUCCH resource may be changed, and if Ci has a different value, the second preprocessing of the PUCCH resource may be changed. If only one pre-processing is required for the PUCCH resource, the UE may consider that the corresponding bit has a fixed value (eg, R). On the other hand, in order to change all the preprocessing of the PUCCH resource, the base station may allocate a new octet in the MAC CE and indicate each preprocessing in each octet.

In order to change only one preprocessor or to change all preprocesses in the base station, the MAC CE must be able to express three cases.

Referring to FIG. 29 , since a case of changing only one preprocessing should be expressed, information representing three cases should be included in octet x+2 or octet x+3 of the MAC CE. In order to secure backward compatibility, it is preferable that the additionally used bit is the previously unused bit (R).

(Method C.4-3): In one bit (k) of the MAC CE, which preprocessing of the PUCCH resource indicates which preprocessing is indicated, and in the other bit (C ₀ ), the number of changed preprocessing(s) is expressed. can

In the proposed MAC CE, two bits can be additionally used. In some octets, in addition to the value to change the preprocessing, which preprocessor is to be changed can be expressed as k. If two preprocessors are changed, C ₀ can be expressed that the subsequent octet changes the remaining preprocessing. Therefore, according to (Method C.4-3), the size of the MAC CE may be variable, so that the size of the MAC CE may be simplified even if only the second preprocessing of the PUCCH resource is changed.

When C ₀ has one value, MAC CE indicates that one preprocessing indicated by k is changed, and when C ₀ has another value, MAC CE indicates that all preprocesses are changed. When only one preprocessing is changed, k having a specific value may indicate that the first preprocessing is changed, and k having a different value may indicate that the second preprocessing is changed. If we want to change both preprocessors, the value of k may be meaningless. Since MAC CE includes information on both preprocesses, the first preprocessing may be included in octet x+2, and the second preprocessing may be included in octet x+3. An example of this is presented in Table 3. According to Table 3, MAC CE can be expressed with two bits in three cases except for a case in which preprocessing is not changed.

k C ₀ meaning 0 0 First change the preprocessing One 0 Changed the second preprocessing 0 One Changed all preprocessing

D. How to determine RV in UL-repetition

(1) How to determine RV for a single TRP

When a resource of a PUSCH occasion is indicated in scheduling DCI, activating DCI, or RRC signaling, a redundancy version (RV) of a PUSCH instance transmitted first may be indicated. RVs may be mapped to subsequent PUSCH instances or split PUSCH instances according to an order determined with a predetermined rule determined in a technical standard.

In this case, one order among several orders may be indicated. For example, the technical specification may be defined including at least sequences of cyclically extending (0,2,3,1), (0,0,0,0), or (0,3,0,3). can The base station may instruct the terminal to use one of the sequences of these RVs as higher layer signaling. Alternatively, when one order is fixedly used, separate signaling for the terminal may not be required. For example, in the technical standard, it may be specified that the order of cyclically extending (0,2,3,1) is fixedly used.

One RV may be assigned to each of several (split) PUSCH instances constituting the PUSCH occasion. The UE may map the coded bits by applying a new RV to each (split) PUSCH instance.

(2) How to determine RVs in an mTRP scenario

In the mTRP scenario, a case in which SRI is provided in PUSCH instance(s) may be further considered. When one TCI state is indicated to the UE, the UE may derive preprocessing method(s) to be applied to the PUSCH instance(s) from the indicated TCI state.

Since the base station can actually combine PUSCH instances received from multiple TRPs, it is preferable that the terminal does not distinguish between transmission for a single TRP and transmission for mTRP without a separate specification. However, it is preferable to determine the application method (eg, priority to be applied) of TCI state cycling and RV cycling for (split) PUSCH instances.

(Method D.2-1): The UE may apply RV to the (split) PUSCH instance regardless of the TCI state of the PUSCH instance.

Therefore, when a resource of a PUSCH occasion is indicated in scheduling DCI, activating DCI, or RRC signaling, the RV of the first transmitted PUSCH instance may be indicated. Thereafter, the PUSCH instance may be mapped to the PUSCH instance sequentially (split) from a sequence determined with a predetermined rule determined in the technical standard.

When a resource of a PUSCH occasion is indicated in scheduling DCI, activating DCI, or RRC signaling, a redundancy version (RV) of a PUSCH instance transmitted first may be indicated. RVs may be mapped to subsequent PUSCH instances or split PUSCH instances according to an order determined with a predetermined rule determined in a technical standard.

In a system operating in FR2, when the base station synthesizes PUSCH instances received from several TRPs, it may be easy to implement that the terminal's pre-processing is aligned with a specific TRP. In this case, it is desirable to allocate a new RV for the TRP (or for the SRI). Therefore, the UE may have to distinguish between transmission for a single TRP and transmission for mTRP. This is because, when the TRP is changed, it is preferable in terms of combining the base station that the RV has a new value and systematic bits are received.

(Method D.2-2): The UE may apply the order of RVs to (split) PUSCH instance(s) belonging to the same TCI state, respectively.

Scheduling DCI, activating DCI, or RRC signaling for allocating a PUSCH occasion may indicate two or more TCI states to the UE. In this case, the preprocessing may be changed for each PUSCH instance, and after the same preprocessing is applied to two or more consecutive PUSCH instance(s), the same preprocessing may be applied to consecutive PUSCH instance(s) after the time interval.

30 is a conceptual diagram for explaining a mapping relationship between PUSCH instances and RVs according to an embodiment of the present invention.

According to (Method D.2-2), the same RV order is used for PUSCH instances corresponding to the same TCI state. Referring to FIG. 30 , RVs may follow the order of (a, b). Here, (a, b) can be given as (0, 2) or (0, 0) or (0, 3).

The base station may instruct (or configure) the terminal to be mapped to a different RV for each first (split) PUSCH instance of the TCI state. This may be expressed as an RV offset. When this is applied, the UE may derive another RV order by applying an RV offset to one standard RV order. For example, for an RV sequence defined as 0,2,0,2,..., if RV offset (+2) is applied, another RV sequence interpreted as 2,0,2,0,... can be derived. As another example, with respect to an RV order defined as 0,2,3,1,0,2,3,1,..., by applying an RV offset, another RV order may be derived. The RV offset may be indicated (or set) to the UE through RRC signaling. Alternatively, the RV offset may be indicated to the UE through scheduling/activating DCI.

For example, while DCI allocates a PUSCH occasion, some bits of the RV field may be interpreted as an RV offset. For example, when a 3-bit RV field is given in DCI, 2 bits among 3 bits represent the first value of a standard RV order, and the remaining 1 bit expresses an RV offset to express another RV order. .

For example, as in the case of FIG. 30 , the RV order (a, b) may be equally applied to all TCI states, but according to another example, a different RV order may be applied to each TCI state. That is, RVs are mapped in the order of (a, b) to the first (split) PUSCH instance to which one TCI state (or SRI) is applied, but to the first (split) PUSCH instance to which another TCI state (or SRI) is applied RVs may be mapped in the order of (b, a).

The UE may derive the TCI state and time resource applied to the PUSCH instance from DCI or RRC signaling for allocating the PUSCH occasion. The UE may apply (Method D.2-1) or (Method D.2-2) to the (split) PUSCH instance.

31 is a conceptual diagram for explaining a mapping relationship between PUSCH instances and RVs when RV cycling is performed before TCI state cycling according to an embodiment of the present invention.

In FIG. 31, when RV cycling is performed before TCI state cycling, as the invalid symbol(s) is determined to be invalid symbol(s), the full PUSCH instance is changed to a split PUSCH instance, RV and TCI state are mapped An example is shown.

Referring to FIG. 31 , a PUSCH occasion is composed of four PUSCH instances, case (a) is a case in which PUSCH instances are sequentially mapped, and case (b) is a case in which PUSCH instances are mapped at a predetermined interval. If split PUSCH instances are generated by invalid symbol(s), RVs may be changed for split PUSCH instances as well. Each TCI state consists of two PUSCH instances, and the order of RVs is applied for each same TCI state. Accordingly, RV a and RV b are successively applied to TCI state x, and then RV a and RV b are successively applied to TCI state y.

E, transmission method of UCI

(1) Repeated transmission of UCI

(

)에 대한 반복 횟수가 독립적으로 주어질 수 있다. 단말이 PUCCH를 반복적으로 전송할 경우, 슬롯 마다 동일한 시간 자원을 이용하여 PUCCH를 반복적으로 전송할 수 있다. The repeated transmission of HARQ-ACK may be indicated (or configured) to the UE by higher layer signaling for each PUCCH format. PUCCH format to the terminal

(

) can be given independently. When the UE repeatedly transmits the PUCCH, the PUCCH may be repeatedly transmitted using the same time resource for each slot.

The UCI type is divided into at least SR, L1-RSRP, HARQ-ACK, and CSI. When UCI is repeatedly transmitted, only one UCI type may be transmitted. For this, the priority of UCI types may be defined in the technical standard. The priority of the UCI type may be HARQ-ACK, SR, and CSI in the highest order. CSI may be further subdivided according to the priority of the CSI report.

Also, if one UCI is selected and is repeatedly transmitted while being included in the PUCCH, it may be assumed that the UE does not transmit another UCI until transmission of the selected UCI is finished. To this end, in order to instruct the UE to transmit the SR or HARQ-ACK, the base station must instruct the UE to transmit the corresponding UCI after the transmission of the PUCCH is finished. Since there may be a lot of time consumed to wait for this, in some cases, this may act as a constraint on scheduling for the base station.

For example of HARQ-ACK among UCI types, when HARQ-ACKs are indicated to be transmitted in the same (sub)slot, or time resources of PUCCHs indicated by DCI/RRC signaling for allocating PDSCH overlap each other, one PUCCH A HARQ codebook may be generated to be transmitted in . In order to generate the HARQ codebook, the terminal generates information bits by arranging the HARQ-ACK bits in a bit stream according to a predetermined order prescribed by the technical standard, and through an encoding process, the encoded bits are formed. can do.

Here, as the encoding, a Reed Muller code or a polar code may be used. A code rate applied in the encoding process may be indicated to the UE by higher layer signaling. For example, in a given PUCCH format, one value may be indicated to the UE as a code rate.

According to the technical standard, one codeword is mapped to one PUCCH. If PUCCH is repeatedly transmitted, only one UCI type is generated as a codeword. If the PUCCH is transmitted only once, one or more UCI type(s) may be concatenated as information bits, and one codeword may be generated through the same encoding process. However, since soft combining of the Reed Muller code or the polar code is difficult to implement, the same codeword may be transmitted even if the PUCCH is repeatedly transmitted, and the base station may perform chase combining. Here, the coded bits or codewords may mean a bit stream expressed by concatenating several code blocks. The codeword may be mapped to REs through a modulation process.

On the other hand, a plurality of UCIs of the same UCI type may be mapped as different information. For example, UCIs may be generated to support traffic having different priorities. SR or HARQ-ACK supporting eMBB traffic and SR or HARQ-ACK supporting URLLC traffic may be regarded as separate information. In this case, UCIs of the same UCI type may be distinguished from each other.

32 is a conceptual diagram for explaining a concept in which UCIs are concatenated and encoded according to an embodiment of the present invention.

Referring to FIG. 32 , N (one or more) UCI types or UCIs having different priorities of the same UCI type may be concatenated and encoded.

The encoded UCI is mapped to the PUCCH. When the PUCCH is transmitted, the same preprocessing (or spatial information or spatial relation) may be maintained. Alternatively, when the PUCCH is transmitted, a different preprocessing may be applied to each transmitted PUCCH according to RRC signaling of the base station.

(2) When two or more codewords are multiplexed on one uplink channel

In order to solve the constraint on scheduling in the base station, it is preferable that different UCI types may be multiplexed or different encodings of the same UCI type may be multiplexed on the repeatedly transmitted PUCCH.

(Method E.2-1): Two or more codewords having different code rates or coding schemes may be multiplexed in one uplink channel.

When the UE transmits PUCCH or PUSCH, two or more codewords may be mapped to PUCCH or PUSCH. For example, while transmitting the PUSCH, the UCI and the TB may be multiplexed and transmitted. Here, the UCI may be composed of one or more UCI type(s) or UCIs having the same UCI type but different priorities (referred to as UCI type/UCI priorities for convenience). As described above, the UCIs distinguished from each other may have different code rates, and a codeword may be generated using a Reed Muller code or a polar code. Here, in the case of TB, a codeword may be generated using the LDPC code. The generated codewords may be modulated and mapped to PUSCH. For example, UCIs configured with one or more UCI type/UCI priority(s) may be transmitted while transmitting the PUCCH. Information having different UCI type/UCI priority(s) may be concatenated, undergo the same encoding process, and be modulated to generate one codeword.

In (Method E.2-1), (Method E.2-2) or (Method E.2-3) described below may be applied alone or in combination.

(Method E.2-2): In (Method E.2-1), a codeword may be defined for each UCI type/UCI priority.

The UE may derive a different codeword for each UCI type/UCI priority in the uplink channel to be transmitted. Possible code rate(s) for UCI type/UCI priority may be indicated by higher layer signaling or DCI. According to (Method E.2-2), different coding rates may be indicated according to the quality required for each UCI type/UCI priority.

33 and 34 are conceptual diagrams for explaining a case in which different code rates are applied to each UCI type/UCI priority according to an embodiment of the present invention.

That is, FIG. 33 shows one example according to (Method E.2-2). Since different UCI type/UCI priorities are used differently, code rates applied to different UCI type/UCI priorities may be different from each other. For example, a code rate applied to HARQ-ACK is related to PDSCH transmission, but a code rate applied to SR is related to PUSCH transmission.

Even if the error rates required by the UCI type/UCI priorities are different, if the same code rate is applied, the base station should apply the coding rate for the UCI type/UCI priority requiring the lowest error rate (ie, the highest quality). can In this case, the uplink channel should use more REs, and the uplink channel should be mapped to a wider bandwidth or more symbols.

(Method E.2-3): In (Method E.2-1), a codeword may be defined from different pieces of information having the same UCI type/UCI priority.

Different coded bits are derived for the same UCI type/UCI priority, and a codeword can be generated by concatenating them. Information having the same UCI type/UCI priority may also require different qualities.

When the UCI type/UCI priority is HARQ-ACK, the UE may transmit HARQ codebook 1 and HARQ codebook 2 to the base station. Here, the HARQ codebook is a bit stream composed of HARQ-ACK bits, and the HARQ-ACK bits are arranged in a predetermined order to generate a bit stream.

34 shows an example according to (Method E.2-3). Even if they have the same UCI type/UCI priority, encoding procedures having different coding rates may be performed.

As an example, HARQ codebook 1 may be derived from HARQ-ACKs for eMBB PDSCHs, and HARQ codebook 2 may be derived from HARQ-ACKs for URLLC PDSCHs. In this case, HARQ codebook 1 and HARQ codebook 2 may require different error rates.

For example, HARQ codebook 1 may have been transmitted to the base station, and HARQ codebook 2 may not have been transmitted to the base station yet. In this case, the base station may receive a PUCCH (or PUSCH) including both HARQ codebook 1 and HARQ codebook 2, and synthesize the HARQ codebook 1 that is already received and the HARQ codebook 1 to be received soon (e.g., chase synthesis or synthesis) ), so that an error can be corrected even at a code rate higher than that of HARQ codebook 2. Here, both HARQ codebook 1 and HARQ codebook 2 may be derived from eMBB PDSCH or URLLC PDSCH.

For example, HARQ codebook 1 may be transmitted to base station 1 or TRP 1, and HARQ codebook 2 may be transmitted to base station 2 or TRP 2. Although received through the same uplink channel (ie, PUSCH or PUCCH), since HARQ codebook 1 and HARQ codebook 2 may have different code rates, a sufficiently low error rate can be obtained even when base stations or TRPs are different. .

Encoded bits may be concatenated into one codeword. The codeword may undergo a modulation process. At this time, according to a modulation scheme, adjacent coded bits may be mapped to one modulation symbol. For example, when modulated with QPSK, two adjacent coded bits may be mapped to one modulation symbol. In this case, a situation in which coded bits that have undergone different encoding processes are mapped to the same modulation symbol may be considered. The base station can demodulate and decode one modulation symbol. In this case, demodulation and decoding may be implemented separately or integratedly.

In one implementation, when demodulation and decoding are implemented as separate steps, the base station may perform a hard decision in demodulating the PUCCH and perform decoding using the hard decision result. In another implementation, when demodulation and decoding are integrated and implemented, demodulation and decoding of PUCCH may be implemented in the same step. In this case, the base station may perform soft decision in demodulation of the PUCCH and perform decoding using the soft decision result.

(Method E.2-4): UCIs to which different encodings are applied can only be mapped to different modulation symbols.

The terminal concatenates the coded bits with known bit(s) (eg, 0 or 1) to adjust the length of the coded bits to a multiple of the number of coded bits required for one modulation symbol. The number of coded bits required for one modulation symbol may vary according to a modulation order. For example, since a QPSK symbol requires two coded bits, a known bit may be additionally concatenated to the coded bits. For example, since one π/2-BPSK or BPSK symbol requires one coded bit, there is no need to concatenate these bits to the coded bits.

35 is a conceptual diagram for explaining a case in which different encodings are applied to different UCI types/UCI priorities or two parts of UCI according to an embodiment of the present invention.

Referring to FIG. 35 , different UCI type/UCI priorities or code rates applied to two parts of UCI may be different from each other, and known bit(s) are concatenated to each of the coded bits to form a modulation symbol. can be aligned to the boundary of

Meanwhile, only the same modulation order may be applied to different UCI types/UCI priorities. In this case, coded bits of different UCI types/UCI priorities may be multiplexed in one modulation symbol.

(Method E.2-5): UCIs to which different encodings are applied may be mapped to the same modulation symbol.

For example, for one QPSK symbol, the coded bit of UCI 1 and the coded bit of UCI 2 may be concatenated. When a hard decision is performed in the demodulation process, the base station may apply (Method E.2-5). (Method E.2-5) can increase the complexity when soft decision is performed in the demodulation process, since the coded bits of UCI 1 and the coded bits of UCI 2 may affect each other have. Also, even using (Method E.2-5), known bits can be concatenated in order to map the coded bits concatenated with each other to a modulation symbol.

(3) How to indicate the HARQ codebook to be transmitted in PUCCH

PDSCHs indicated to the UE may be divided into two or more PDSCH groups. The PDSCH group may be indicated by scheduling DCI, and includes PDSCHs targeted by the same HARQ codebook. HARQ-ACKs belonging to the same HARQ codebook are transmitted through the same PUCCH. The base station may indicate to the terminal the PDSCH group to which the PDSCH belongs and PUCCH resources for the corresponding PDSCH by using scheduling DCI. The number of repeated PUCCH transmissions for each PUCCH format may be indicated to the UE through scheduling DCI or RRC signaling. In this case, in a time resource where repeated transmission 1 of PUCCH and repeated transmission 2 of PUCCH overlap each other, one or more HARQ codebook(s) may be concatenated and encoded. Here, when PUCCH is repeatedly transmitted, the time interval of PUCCH instances may be given by 0 or more symbol(s), slot(s), or subslot(s). The interval between PUCCH instances may be the interval of the first symbols of the PUCCH instances or the interval between the last symbol of the preceding PUCCH and the first symbol of the following PUCCH.

Here, the PDSCHs may have the same priority or different priorities, which may be indicated by RRC signaling or DCI. For example, a HARQ codebook for PDSCH for supporting eMBB traffic or URLLC traffic may be transmitted in PUCCH. For example, one PUCCH may include a HARQ codebook for PDSCH for eMBB traffic, and another PUCCH may include a HARQ codebook for PDSCH for URLLC traffic.

(Method E.3-1): The field of Scheduling DCI may indicate that the HARQ codebook for the PDSCH group to which the scheduled PDSCH belongs and other HARQ codebook(s) are multiplexed.

When the HARQ codebook(s) are multiplexed, (Method E.2-3) may be additionally applied. Accordingly, the HARQ codebook may be obtained with encoded bits through different encoding processes. Encoded bits may be concatenated to form one codeword.

The UE may repeatedly transmit HARQ codebook 1 for PDSCH group 1 and may repeatedly transmit HARQ codebook 2 for PDSCH group 2. Here, the UE may have partially transmitted HARQ codebook 1.

36 to 39 are conceptual diagrams for explaining repeated transmission of an HARQ codebook according to embodiments of the present invention.

)이 도시되며, 이들은 심볼(들), 슬롯(들), 또는 서브 슬롯(들)의 단위로 표현될 수 있다. HARQ 코드북 1과 HARQ 코드북 2가 다중화되는 경우, 부호화된 비트들의 개수에 따라서 PUCCH 자원이 다르게 결정될 수 있다. 이 때, PUCCH가 갖는 반복 횟수의 크기는 같도록 지시될 수 있다. 36 to 39, predetermined intervals between time resources of repeatedly transmitted PUCCHs (ie,

) are shown, which may be expressed in units of symbol(s), slot(s), or sub-slot(s). When HARQ codebook 1 and HARQ codebook 2 are multiplexed, PUCCH resources may be differently determined according to the number of coded bits. In this case, the size of the number of repetitions of the PUCCH may be indicated to be the same.

When the UE is instructed to repeatedly transmit PUCCH 4 times, after the UE repeatedly transmits HARQ codebook 1 twice, transmission of HARQ codebook 2 may be additionally instructed from PUCCH transmitted 3 times. Referring to FIG. 36, when repeated transmission is performed in units of HARQ codebooks, the terminal transmits only HARQ codebook 1 twice, then HARQ codebook 1 and HARQ codebook 2 are multiplexed and transmitted twice, and then only HARQ codebook 2 is transmitted twice can be transmitted Referring to FIG. 37, when the UE is instructed to transmit both HARQ codebook 2 as well as HARQ codebook 1 in the DCI received by the UE, the UE transmits both HARQ codebook 1 and HARQ codebook 2 in the same PUCCH. After the UE transmits only HARQ codebook 1 twice, HARQ codebook 1 and HARQ codebook 2 are multiplexed and transmitted 4 times. It is transmitted as an extended HARQ codebook by multiplexing HARQ codebook 1 and HARQ codebook 2, and the number of repetitions may be applied equally (ie, 4 times) with DCI (or RRC signaling). Therefore, HARQ codebook 1 has already been transmitted twice and may be transmitted four additional times.

(4) Example of repeated transmission of PUCCH

When the UCI is repeatedly transmitted, the number of repetitions may be indicated for each format of the PUCCH. In this case, the UE may repeatedly transmit a PUCCH to which only a codeword composed of only one UCI type is mapped. When the UE intends to transmit two or more UCI types or UCIs having UCI priorities, the UE may generate a codeword by selecting only one UCI type/priority according to a prioritization rule. Since this method has a disadvantage in that a transmission amount is reduced in a specific UCI type (eg, HARQ-ACK), a method capable of multiplexing UCIs of two or more UCI types or UCI priorities is required.

The number of repeated transmissions may be indicated to the UE for each UCI type or UCI priority (ie, for each codeword). For example, the base station instructs the UE to repeatedly transmit the HARQ-ACK for the eMBB PDSCH twice, to repeatedly transmit the HARQ-ACK for the URLLC PDSCH four times, and to transmit the CSI once. can The base station may indicate this information to the terminal through higher layer signaling. The UE may be instructed by the base station for resources for transmitting the PUCCH, and may apply the number of repeated transmissions for each codeword. Therefore, when the UE is instructed to the PUCCH resource through DL-DCI, the HARQ-ACKs or HARQ codebook is composed of one codeword and thus the same number of repetitions is applied, so the UE can repeatedly transmit the PUCCH as many times as possible. .

Also, if UCI (eg, HARQ codebook 2, CSI, etc.) is newly generated, it may be composed of a new codeword, and may be transmitted separately from the previous codeword (eg, HARQ codebook 1). For example, each codeword may be transmitted first from different (sub) slots, and each codeword may be transmitted last from different (sub) slots. Alternatively, the base station implements the (sub) slots in which the PUCCH is transmitted, so that the UE repeatedly transmits the PUCCH in which the HARQ codebook is encoded, and then repeatedly transmits the PUCCH in which the new HARQ codebook is encoded. Since this may mean a scheduling constraint, it is preferable that the base station be able to instruct transmission of a new PUCCH even before the transmission of the PUCCH ends. Here, when PUCCH is repeatedly transmitted, an interval between time resources of PUCCH instances may be given by 0 or more symbol(s) or slot(s). The interval between PUCCH instances may be the interval between the first symbols of the PUCCH instances or the interval between the last symbol of the preceding PUCCH instance and the first symbol of the following PUCCH instance.

(Method E.4-1): Repeated transmission of PUCCH (PUCCH instance) may not be transmitted when the time resource overlaps with repeated transmission of another PUCCH (PUCCH instance).

For convenience of description, it is assumed that repeated transmission 1 of PUCCH and repeated transmission 2 of PUCCH have overlapping time resources, and repeated transmission 2 of PUCCH starts later in time. According to (Method E.4-1), repeated transmission 2 of PUCCH is transmitted, and some repetitive transmission 1 of PUCCH may not be transmitted. (Method E.4-1) can be subdivided into (Method E.4-2) and (Method E.4-3).

Hereinafter, a case for HARQ-ACK will be described as an example of the UCI type, but the present invention is not limited thereto, and methods to be described later may be applied to L1-RSRP, SR, CSI, or a combination thereof. Here, UCIs having the same UCI type may have the same or different priorities, which may be indicated by RRC signaling or DCI. For example, a HARQ codebook for PDSCH for supporting eMBB traffic or URLLC traffic may be transmitted in PUCCH. For example, one PUCCH may include a HARQ codebook for PDSCH for eMBB traffic, and another PUCCH may include a HARQ codebook for PDSCH for URLLC traffic.

(Method E.4-2): When (Method E.4-1) is applied, repeated transmission of the interrupted PUCCH may not be attempted again later.

Since the PUCCH includes the HARQ codebook, in order to satisfy the required error rate, the base station must allocate sufficient resources. Therefore, according to (Method E.4-2), if two or more repeated transmissions of PUCCH are allocated, it may be replaced with repeated transmission of the PUCCH from which transmission started last. If the order in which the DCI is received and the order of the first PUSCH instance of the corresponding PUCCH repeated transmission are the same (in-order scheduling), it can be interpreted as replacing the last transmission with the repeated transmission of the allocated PUCCH. have.

Otherwise (in the case of out-of-order scheduling), the repeated transmission of the PUCCH to which the last transmission is allocated may differ from the repeated transmission of the PUCCH where the last transmission is started. At this time, according to (Method E.4-2), if two or more repeated transmissions of PUCCH are allocated, the last transmission may be replaced with repeated transmission of the allocated PUCCH.

)이 도시되며, 이들은 심볼(들), 슬롯(들), 또는 서브 슬롯(들)의 단위로 표현될 수 있다. HARQ 코드북 1과 HARQ 코드북 2가 다중화되는 경우, 부호화된 비트들의 개수에 따라서 PUCCH 자원이 다르게 결정될 수 있다. 이 때, PUCCH가 갖는 반복 횟수의 크기는 같도록 지시될 수 있다.In FIG. 38, predetermined intervals between time resources of repeatedly transmitted PUCCHs (ie,

) are shown, which may be expressed in units of symbol(s), slot(s), or sub-slot(s). When HARQ codebook 1 and HARQ codebook 2 are multiplexed, PUCCH resources may be differently determined according to the number of coded bits. In this case, the size of the number of repetitions of the PUCCH may be indicated to be the same.

The PUCCH format in which HARQ codebook 1 is transmitted may be repeatedly transmitted 4 times, and the PUCCH format in which both HARQ codebook 1 and HARQ codebook 2 are transmitted may be transmitted repeatedly 2 times. A case in which repeated transmission of a new PUCCH is indicated before the repeated transmission of the PUCCH in which the HARQ codebook 1 is transmitted ends, and the time resources of the PUCCHs are allocated to overlap each other in some slots are considered.

According to (Method E.4-2), HARQ codebook 1 can be transmitted only three times. Here, HARQ codebook 1 may be transmitted once through PUCCH alone, and may be transmitted twice through PUCCH including both HARQ codebook 1 and HARQ codebook 2. Alternatively, PUCCH including only HARQ codebook 2 may be transmitted. Here, HARQ codebook 2 may include HARQ codebook 1 and an additional HARQ-ACK bit stream. Alternatively, HARQ codebook 1 and HARQ codebook 2 may be configured with HARQ-ACK bit streams for different HARQ processes. Since the base station allocates resources so that HARQ codebook 2 achieves a sufficiently low error rate, HARQ codebook 1 can also obtain a sufficient error rate. Accordingly, the UE may not additionally transmit the PUCCH including the HARQ codebook 1.

Here, the base station should be able to perform hard combining while receiving the HARQ codebook 1 several times. It is preferable that the code rate and/or codeword of HARQ codebook 1 always maintain the same value when transmitted in PUCCHs.

(Method E.4-3): When (Method E.4-1) is applied, interruption of repeated PUCCH transmission is limited when time resources overlap, and repeated transmission of interrupted PUCCH may be attempted again later. have.

If the transmission of the repeated transmission 2 of the PUCCH is completed, the number of repetitions of the repeated transmission 1 of the PUCCH may still remain. At this time, according to (Method E.4-2), repeated transmission 1 of PUCCH can be canceled later, but according to (Method E.4-3), repeated transmission 1 of PUCCH can be transmitted even thereafter.

In the case illustrated in FIG. 39 , in the same environment as illustrated in FIG. 38 , a PUCCH including only HARQ codebook 1 may be additionally transmitted. Since the base station receives the codeword for HARQ codebook 1 four times, the error rate for HARQ codebook 1 can be kept sufficiently low. In addition, the base station can sufficiently maintain the error rate for the HARQ codebook 2 by allocating the resources of the PUCCH including the HARQ codebook 2 sufficiently low. Here, HARQ codebook 2 may include HARQ codebook 1 and an additional HARQ-ACK bit stream. Alternatively, HARQ codebook 1 and HARQ codebook 2 may be configured with HARQ-ACK bit streams for different HARQ processes.

F. Multiplexing Method of Repeated UCI and Repeated PUSCH

(1) When the same UCI is repeated

Hereinafter, a case in which the PUCCH is indicated to be repeatedly transmitted and the PUSCH is indicated to be repeatedly transmitted is considered.

UCIs of the same UCI type may have the same or different priorities, and the priorities may be indicated by RRC signaling or DCI. For example, a HARQ codebook for PDSCH for supporting eMBB traffic or URLLC traffic may be transmitted through PUCCH. For example, one PUCCH may include a HARQ codebook for PDSCH for eMBB traffic, and another PUCCH may include a HARQ codebook for PDSCH for URLLC traffic. In addition, when the PUSCH includes a TB, the priority of the TB may be the same as or different from the priority of the UCI.

(Method F.1-1): While the PUSCH and the PUCCH are repeatedly transmitted, if some overlap in time, the PUCCH may be transmitted and the PUSCH may not be transmitted.

Here, the PUCCH instance may be repeated based on a slot or may be repeated based on a subslot. When a full PUSCH instance or a split PUSCH instance belonging to a PUSCH or PUSCH occasion overlaps with a PUCCH instance in some symbols, only PUCCH may be transmitted.

40 to 43 are conceptual diagrams for explaining operating methods when a PUCCH instance and a full/split PUSCH instance overlap each other according to an embodiment of the present invention.

Referring to FIG. 40 , there is an interval of d between PUCCH instances, and d may be slot(s) or subslot(s). d may mean a time interval between the first symbols of PUCCH instances. Alternatively, d may be an interval between the last symbol of the preceding PUCCH instance and the first symbol of the following PUCCH instance.

(1.1) When PUCCH(s) and PUSCH(s) are temporally overlapped in one-to-one correspondence

When UCI and PUSCH are repeatedly transmitted, UCI and PUSCH may overlap repeatedly. In this case, a PUSCH instance may multiplex UCI, and may multiplex UCI in all these PUSCH instances, or may multiplex UCI only in a specific PUSCH instance.

(Method F.1-2): In all PUSCHs temporally overlapping with PUCCH, UCI may be multiplexed to PUSCH.

When the UE is instructed to repeatedly transmit the HARQ codebook, the HARQ codebook may be repeatedly multiplexed to PUSCH instances. 41 shows such a case. For example, the UE may be instructed to transmit the HARQ codebook 1 m times (m≥3) and the PUSCH may be instructed to transmit k times (k≥2). Here, PUCCHs including HARQ codebook 1 (ie, HARQ1) may overlap PUSCHs in time. Therefore, according to (Method F.1-2), the UE may transmit the PUSCH multiplexed with HARQ codebook 1 twice. At this time, a PUCCH instance that does not overlap in time with the PUSCH instance may be additionally transmitted (case (a)). Alternatively, a PUCCH instance that does not temporally overlap a PUSCH instance may not be transmitted anymore (case (b)).

When the UE continues to transmit the PUCCH instance, the base station must be able to associate HARQ codebook 1. However, the coding rate applied to the HARQ codebook 1 multiplexed to the PUSCH instance and the coding rate applied to the HARQ codebook 1 transmitted through the PUCCH instance may be different from each other. In this case, it may be difficult for the base station to perform association for them. Nevertheless, since the error rate for HARQ codebook 1 can be improved by implementation in the base station, a PUCCH instance that does not temporally overlap with the PUSCH instance may be additionally transmitted as in case (a). If the base station does not support such an implementation, a PUCCH instance that does not temporally overlap a PUSCH instance may not be transmitted as in case (b). In case (b), the base station must perform scheduling so that HARQ codebook 1 has a sufficient error rate.

(Method F.1-3): UCI may be multiplexed in a specific PUSCH temporally overlapping with the PUCCH.

When the UE is instructed to repeatedly transmit the HARQ codebook, the HARQ codebook may be multiplexed to only one PUSCH instance. For example, among PUSCHs temporally overlapping with PUCCHs, UCI may be multiplexed only on the temporally most advanced PUSCH. 42 shows such a case. The UE may be instructed to transmit the HARQ codebook 1 m times (m≥3), and the PUSCH may be instructed to transmit k times (k≥2). Here, the PUCCH including the HARQ codebook 1 may overlap the PUSCH in time. Therefore, according to (Method F.1-3), the UE may transmit a PUSCH multiplexed with HARQ codebook 1 once. At this time, a PUCCH instance that does not overlap in time with the PUSCH instance may be additionally transmitted (case (a)). Alternatively, a PUCCH instance that does not temporally overlap a PUSCH instance may not be transmitted anymore (case (b)).

As described above, according to the implementation and scheduling of the base station for improving the error rate for HARQ codebook 1, the terminal may operate in case (a) or case (b).

(1.2) When PUCCH(s) and PUSCH(s) are temporally overlapped by corresponding one-to-many (or many-to-one)

The above-described methods can be applied when one PUSCH instance and one PUCCH instance overlap. On the other hand, one PUSCH instance may overlap two or more PUCCH instances, or one PUCCH instance may overlap two or more PUSCH instances. In such cases, the above-described methods may be difficult to apply. In addition, PUCCH instances may be repeatedly transmitted including the same UCI or may be repeatedly transmitted including different UCIs.

Therefore, the PUCCH including the HARQ codebook may be indicated to be repeatedly transmitted, and all PUCCH instances may include the same HARQ codebook. While the PUCCH is repeatedly transmitted in the HARQ codebook, the PUSCH may be transmitted over several (sub) slots. As the PUSCH is transmitted over several (sub) slots, it may overlap two or more PUCCH instances in time. 43 shows such a case.

As shown in case (a), the PUSCH allocated by the base station temporally overlaps with two or more PUCCH instances. In this case, the UE may multiplex HARQ codebook 1 to PUSCH. Since two or more PUCCH instances are repeatedly transmitted including HARQ codebook 1, the UE may multiplex a specific PUCCH instance (eg, the PUSCH instance that overlaps the PUSCH first) among the PUCCH instances to the PUSCH. In this case, sufficient processing time for the UE to multiplex HARQ codebook 1 to the corresponding PUSCH instance must be secured.

In this case, the remaining PUCCH instances that do not overlap in time with the PUSCH may be transmitted (case (a)). Alternatively, the remaining PUCCH instances that do not overlap in time with the PUSCH may not be transmitted (case (b)). As described above, according to the implementation and scheduling of the base station for improving the error rate for HARQ codebook 1, the terminal may operate in case (a) or case (b).

(2) When different UCIs are transmitted

(2.1) When PUCCH(s) and PUSCH(s) are temporally overlapped in one-to-one correspondence

The base station may instruct the terminal to sequentially transmit UCIs. In this case, the PUSCH may temporally overlap with one or more PUCCH instances. In this case, a PUCCH instance (ie, UCI) may be multiplexed to the PUSCH. When multiplexing UCI to PUSCH, the UE needs to know the amount of UCI.

In the case of HARQ-ACK, the UE may estimate the size of the HARQ codebook from the DAI field of DL-DCI. A case in which one PUSCH overlaps two or more PUCCH instances in time and the HARQ codebook is not repeatedly transmitted may be considered. Since there are several HARQ codebooks, the UE needs to know the size of each HARQ codebook.

(Method F.2-1): The number of HARQ codebooks (or PUCCH instances) multiplexed on the PUSCH occasion is limited to a maximum of n.

(Method F.2-2): In (Method F.2-1), the number of HARQ codebooks multiplexed to one PUSCH instance is limited to one or less.

The UE may estimate the size of the HARQ codebook from a specific field of DCI. In order to limit the size of DCI, the base station may indicate the value of n to the terminal through RRC signaling. Alternatively, the value of n may be determined as one value in the technical standard. In one example, n may be set to 1. When n is 1, the conventional DCI can be reused. If n has a value of 2 or more, n DAIs may be included in DCI. In addition, the base station must schedule so that n or less PUCCH instances can overlap the PUSCH(s) in time.

In (Method F.2-1) and (Method F.2-2), the priority (ie, eMBB or URLLC) corresponding to the HARQ codebooks may be counted as n regardless, or counted to n for each priority. can be messy If each priority is counted to n, since two priorities are given even when n is 1, the DAI must be able to derive two indices.

44 to 45 are conceptual diagrams for explaining other operation methods when a PUCCH instance and a full/split PUSCH instance overlap each other according to an embodiment of the present invention.

를 전송하도록 지시받을 수 있고, HARQ 코드북

에 연관된 PUCCH instance와 시간적으로 겹치는 PUSCH를 할당받을 수 있다(경우 (a)). 기지국은 PUSCH를 할당하는 UL-DCI를 HARQ 코드북

에 연관될 수 있는 DL-DCI보다 시간적으로 같거나 더 늦게 전송해야 한다. 하지만, HARQ 코드북 3을 포함한 PUCCH instance는 PUSCH와 시간적으로 겹치지 않기 때문에, 이러한 제약을 가지지 않는다.As shown in Figure 44, the terminal is a HARQ codebook

may be instructed to transmit a HARQ codebook

A PUSCH temporally overlapping with the PUCCH instance associated with may be allocated (case (a)). The base station uses the UL-DCI to allocate the PUSCH to the HARQ codebook

It should be transmitted at the same time or later than the DL-DCI that can be associated with the DL-DCI. However, since the PUCCH instance including the HARQ codebook 3 does not overlap in time with the PUSCH, it does not have such a restriction.

On the other hand, in the case of a PUSCH occasion that is not allocated by UL-DCI, this limitation is unnecessary. Therefore, the number (n) of the HARQ codebook(s) that can be multiplexed on the PUSCH occasion may be extended as needed (n≥1). However, it is preferable that the number of HARQ codebook(s) multiplexed to one PUSCH instance is still limited to one or less.

According to (Method F.2-1) when n=1, PUSCH multiplexed with HARQ codebook 1 may be transmitted, and HARQ codebook 2 may not be transmitted. Alternatively, the base station schedules so that such allocation does not occur, and the terminal may assume that such allocation does not occur.

는 각각 PUSCH에 다중화되어 전송될 수 있다. 이는 경우 (b)로 표현된다.According to (Method F.2-1) in the case of n=2, HARQ codebook

may be multiplexed and transmitted to each PUSCH. This is expressed as case (b).

(2.2) When PUCCH(s) and PUSCH(s) are temporally overlapped by corresponding one-to-many (or many-to-one)

The base station may instruct the terminal to sequentially transmit UCIs. Here, UCIs may be generated by different DCIs or resource allocations. In this case, the PUSCH may temporally overlap with one or more PUCCH instances. In this case, a PUCCH instance (ie, UCI) may be multiplexed to the PUSCH. When multiplexing UCI to PUSCH, the UE needs to know the amount of UCI.

In the case of HARQ-ACK, the UE may estimate the size of the HARQ codebook from the DAI field of DL-DCI. A case in which one PUSCH overlaps two or more PUCCH instances in time and the HARQ codebook is not repeatedly transmitted may be considered. Since there are several HARQ codebooks, the UE needs to know the size of each HARQ codebook.

(Method F.2-3): The number of HARQ codebooks (or PUCCH instances) multiplexed to PUSCH is limited to a maximum of n.

The UE may estimate the size of the HARQ codebook from a specific field of DCI. In order to limit the size of DCI, the base station may indicate the value of n to the terminal through RRC signaling. Alternatively, the value of n may be determined as one value in the technical standard. In one example, n may be set to 1. When n is 1, the conventional DCI can be reused. If n has a value of 2 or more, n DAIs may be included in DCI. In addition, the base station must schedule so that n or less PUCCH instances can overlap the PUSCH(s) in time.

In (Method F.2-3) and (Method F.2-4) to (Method F.2-5), the priority (ie, eMBB or URLLC) corresponding to HARQ codebooks may be counted to n regardless of Or, it may be counted as n per priority. If each priority is counted to n, since two priorities are given even when n is 1, the DAI must be able to derive two indices.

를 전송하도록 지시받을 수 있고, HARQ 코드북

에 연관된 PUCCH instance와 시간적으로 겹치는 PUSCH를 할당받을 수 있다. 기지국은 PUSCH를 할당하는 UL-DCI를 HARQ 코드북

에 연관될 수 있는 DL-DCI보다 시간적으로 같거나 더 늦게 전송해야 한다. 하지만, HARQ 코드북 3을 포함한 PUCCH instance는 PUSCH와 시간적으로 겹치지 않기 때문에, 이러한 제약을 가지지 않는다.As shown in Figure 45, the terminal is a HARQ codebook

may be instructed to transmit a HARQ codebook

A PUSCH that temporally overlaps with a PUCCH instance associated with . The base station uses the UL-DCI to allocate the PUSCH to the HARQ codebook

It should be transmitted at the same time or later than the DL-DCI that can be associated with the DL-DCI. However, since the PUCCH instance including the HARQ codebook 3 does not overlap in time with the PUSCH, it does not have such a restriction.

을 다중화하여 전송할 수 있다. n=1인 경우에 (방법 F.2-3)을 따르면, PUSCH에는 HARQ 코드북 1만이 다중화되고, HARQ 코드북 2는 전송되지 않을 수 있다. 또는, 기지국은 이러한 할당이 발생하지 않도록 스케줄링하며, 단말은 이러한 할당이 발생하지 않는다고 가정할 수 있다.According to (Method F.2-3) in the case of n=2, PUSCH is HARQ codebook

can be multiplexed and transmitted. According to (Method F.2-3) when n=1, only HARQ codebook 1 may be multiplexed to PUSCH, and HARQ codebook 2 may not be transmitted. Alternatively, the base station schedules so that such allocation does not occur, and the terminal may assume that such allocation does not occur.

(Method F.2-4): The value of n applied to (Method F.2-3) is a PUSCH occasion dynamically allocated through DCI, a PUCCH occasion allocated in a T1 CG method, and a T2 CG method. It may be the same for the PUCCH occasion.

Since the implementation of the UE can be simplified, the value of n is a method in which a PUSCH occasion is allocated (that is, a dynamic allocation method by DCI, a method configured by RRC signaling and activated by DCI, or a method in which only RRC signaling is allocated/activated. ) may be irrelevant. However, in this case, the value of n should have the lowest value for these three schemes. Accordingly, the value of n may be independently assigned for each scheme in which the PUSCH occasion is allocated.

(Method F.2-5): The value of n applied to (Method F.2-3) is a PUSCH occasion that is dynamically allocated through DCI, a PUCCH occasion that is allocated in a T1 CG method, and a T2 CG method that is allocated It may be different for each PUCCH occasion.

For example, for a dynamically allocated PUSCH occasion, n=1, and for a PUSCH occasion allocated by the T1/T2 CG scheme, n may have a value greater than 1. Here, the value of n for the PUSCH occasion allocated in the T1/T2 CG scheme means the number of PUCCH instances overlapping the PUSCH.

(3) When a new UCI is repeated when the iteration is not finished

A case in which multiplexing between UCI and PUSCH is considered will be described.

46 and 47 are conceptual diagrams for explaining a UCI transmission method when repeated UCI transmission starts when repeated UCI transmission is not finished according to an embodiment of the present invention.

)이 존재하며, 이는 슬롯(들) 또는 서브 슬롯(들)일 수 있다. PUCCH instance들 간의 간격은 PUCCH instance들의 첫 심볼들 간의 시간 간격을 의미할 수 있다. 또는, PUCCH instance들 간의 간격은 앞서는 PUCCH instance의 마지막 심볼과 뒤서는 PUCCH instance의 첫 심볼 간의 간격일 수 있다46 and 47, a predetermined interval (ie, a predetermined interval between repeated PUCCH instances)

), which may be slot(s) or sub-slot(s). The interval between PUCCH instances may mean a time interval between first symbols of PUCCH instances. Alternatively, the interval between PUCCH instances may be the interval between the last symbol of the preceding PUCCH instance and the first symbol of the following PUCCH instance.

When HARQ codebook 1 and HARQ codebook 2 are multiplexed, PUCCH resources may be differently determined according to the number of coded bits. In this case, the number of repeated transmissions of PUCCHs may be equally indicated.

In one example, when the time resource of the PUCCH corresponding to the allocated UCI and the time resource of the PUSCH overlap, the UE may map the UCI to the PUCCH and may not transmit the PUSCH. Here, the PUSCH not transmitted may mean all full/split PUSCH instances in which the PUCCH and the time resource overlap.

Referring to FIG. 46 , the UE repeatedly transmits the PUSCH 4 times and repeatedly transmits the PUCCH 2 times. In this case, the PUSCH is transmitted only once, and since the remaining PUSCH instances overlap with the PUCCH instances, PUCCH instances may be transmitted instead of PUSCH instances. One of HARQ codebook 1 or HARQ codebook 2 is transmitted in a PUCCH instance, or HARQ codebook 1 and HARQ codebook 2 are concatenated and transmitted in a PUCCH instance, or HARQ codebook 1 or HARQ codebook 2 is generated as a new HARQ codebook and generated as a PUCCH instance can be transmitted from

In another example, when the time resource of the PUCCH corresponding to the allocated UCI and the time resource of the PUSCH overlap, the UE may map the UCI to the PUSCH.

Referring to FIG. 47 , the UE repeatedly transmits the PUSCH 4 times and repeatedly transmits the PUCCH 2 times. HARQ codebook 1 and HARQ codebook 2 are respectively generated. Here, an example of a method of generating the HARQ codebook 2 is to generate the HARQ codebook 2 independently of the HARQ codebook 1 . In this case, overlapping HARQ process identifiers may not exist in HARQ codebook 1 and HARQ codebook 2 . Alternatively, another example of a method of generating the HARQ codebook 2 is to generate the HARQ codebook 2 by adding the HARQ-ACK bit stream to the HARQ codebook 1.

The repeated transmission of the PUCCH may follow the above-described methods ((Method E.4-1), (Method E.4-2), (Method E.4-3)). When the repeated transmission method of the PUCCH is determined, a multiplexing method with the PUSCH may be considered.

Referring to FIG. 47, only the PUSCH is transmitted in the first transmission of the PUSCH (the first PUSCH instance). In the second transmission of PUSCH (second PUSCH instance), HARQ codebook 1 is transmitted. In the third transmission of PUSCH (third PUSCH instance), HARQ codebook 1 and HARQ codebook 2 or HARQ codebook 2 including HARQ codebook 1 may be transmitted. In the fourth transmission of the PUSCH (the fourth PUSCH instance), HARQ codebook 2 or HARQ codebook 2 including HARQ codebook 1 may be transmitted.

When only HARQ codebook 1 is allocated, the UE may transmit HARQ codebook 1 in all PUSCH instances temporally overlapping with the PUCCH instances.

When HARQ codebook 1 and HARQ codebook 2 consist only of different HARQ process identifiers, in UL-DCI, both the offset of the code rate that the HARQ codebook 1 should have (beta offset) and the offset of the code rate that the HARQ codebook 2 should have may include This can be applied to all UCIs as well as HARQ-ACK.

(Method F.3-1): UL-DCI may indicate offsets of code rates applied to two or more UCI types, the same UCI type, or UCIs having different priorities.

Since different UCIs may be mapped to PUSCH, a beta offset may be indicated to the UE for each of these UCIs (ie, UCI type or UCI codebook, etc.). The code rate applied to each UCI may be indicated to the UE by higher layer signaling. Alternatively, a code rate applied to each UCI may be indicated as a beta offset through UL-DCI. Since the base station can repeatedly receive UCI, it is preferable that the code rate indicated by higher layer signaling to the terminal and the beta offset indicated by UL-DCI can be indicated only by the same value.

However, when the number of UCI types or HARQ codebooks is large, or when the priority of traffic (ie, eMBB or URLLC) is distinguished, it may be ineffective to indicate all beta offsets for UCI types or HARQ codebooks in UL-DCI. can Therefore, for the same UCI type, it is preferable that several beta offsets are indicated using one index.

(Method F.3-2): In (Method F.3-1), one index may indicate several offsets.

Indexes for beta offsets may be included in UL-DCI. The beta offsets corresponding to one index may be different depending on the UCI type and the coding method (Reed Muller code or polar code). This correspondence may be indicated by higher layer signaling. According to (Method F.3-2), both the beta offset for the HARQ codebook 1 and the beta offset for the HARQ codebook 2 can be derived from one index.

(4) How UCI is multiplexed in Split PUSCH instance

According to the prior art standard, when UCI is multiplexed to PUSCH, the number of REs used by UCI is determined using various variables, and REs used by TB are determined as the remainder of REs used by UCI. For example, when HARQ-ACK(s) is mapped to PUSCH to which UL-SCH is mapped, the number of REs to which HARQ-ACH(s) are mapped may be determined using Equation 1 below.

는 HARQ-ACK(들)의 개수,

는 CRC의 길이,

는

번째 심볼이 갖는 부반송파들의 개수,

은

번째 코드북의 크기,

는 PUSCH가 가지는 심볼들의 개수,

는 TB가 가지는 코드 블록들의 개수,

는 DM-RS를 포함하지 않는 첫 심볼의 인덱스(또는 DM-RS 심볼 이후의 첫 인덱스)를 의미한다. 여기서,

(또는 beta offset)는 HARQ-ACK(들)의 유효 부호율과 PUSCH의 부호율의 비율을 대략적으로 나타내며, RRC 시그널링으로 여러 값들이 단말에게 지시되고, 여러 값들 중 하나의 값이 UL-DCI를 통해 단말에게 지시된다.

(또는 alpha scaling 또는 scaling)은 HARQ-ACK(들)이 PUSCH의 RE들을 너무 많이 차지하지 않도록, 상한값의 비율로써 작용한다. RRC 시그널링으로 단말에게 하나의

값이 지시될 수 있다. here,

is the number of HARQ-ACK(s),

is the length of the CRC,

Is

the number of subcarriers in the th symbol,

silver

the size of the second codebook,

is the number of symbols the PUSCH has,

is the number of code blocks in TB,

denotes the index of the first symbol that does not include the DM-RS (or the first index after the DM-RS symbol). here,

(or beta offset) roughly indicates the ratio of the effective code rate of HARQ-ACK(s) and the code rate of PUSCH, several values are indicated to the UE by RRC signaling, and one of the values indicates UL-DCI is directed to the terminal through

(or alpha scaling or scaling) acts as a ratio of the upper limit so that HARQ-ACK(s) do not occupy too many REs of PUSCH. One signal to the UE by RRC signaling

A value may be indicated.

In addition to HARQ-ACK, similar equations (Equation 2, Equation 3, Equation 4, Equation 5, and Equation 6) are applied to other UCI types (ie, SR, L1-RSRP, CSI) can Specifically, when HARQ-ACK(s) is mapped to a PUSCH to which a UL-SCH is not mapped, the number of REs to which the HARQ-ACK(s) are mapped may be determined using Equation 2 below. When CSI part 1 is mapped to a PUSCH to which UL-SCH is mapped, the number of REs to which CSI part 1 is mapped may be determined using Equation 3 below. When CSI part 1 is mapped to a PUSCH to which UL-SCH is not mapped, the number of REs to which CSI part 1 is mapped may be determined using Equation 4 below. When CSI part 2 is mapped to PUSCH to which UL-SCH is mapped, the number of REs to which CSI part 2 is mapped may be determined using Equation 5 below. When CSI part 2 is mapped to a PUSCH to which UL-SCH is not mapped, the number of REs to which CSI part 2 is mapped may be determined using Equation 6 below. Accordingly, all methods described below can be easily extended and applied.

When UCI is multiplexed to PUSCH, not only beta offset but also alpha scaling is applied, so that the number of REs that can be occupied by the encoded UCI is determined. Alpha scaling is used to determine the upper limit that the number of REs can have. For example, when a beta offset is indicated so that only too few REs are allocated to a TB belonging to a PUSCH, or when there are few REs of a PUSCH that cannot follow the indicated beta offset, an upper limit of alpha scaling may be used.

When the PUSCH is transmitted as a split PUSCH instance, Equation 1 cannot be applied as it is. The reason is that the number of REs used when calculating the upper limit in Equation 1 is derived assuming a full PUSCH instance, not a split PUSCH instance. Since the upper limit may have an invalid value in the Split PUSCH instance, a new method must be applied.

(Method F.4-1) When calculating the upper limit of Equation 1, the parameter derived based on the split PUSCH instance to which UCI is to be multiplexed is used in Equation 1.

PUCCH associated with UCI may temporally overlap with a split PUSCH instance rather than a full PUSCH instance. In this case, the UE may calculate the upper limit applied to Equation 1 by using the values for the corresponding split PUSCH instance. Therefore, even if interpreted as a beta offset for the split PUSCH instance, the number of REs that can be occupied by the encoded UCI is calculated to be the upper limit or less. However, since the UE uses one alpha scaling, if the base station determines alpha scaling assuming that UCI is multiplexed to the full PUSCH instance, alpha scaling is set to an inappropriate value when the UE multiplexes UCI in the split PUSCH instance. can be directed.

(Method F.4-2) When calculating the upper limit of Equation 1, Equation 1 is used by deriving a parameter from the full PUSCH instance. When calculating the upper limit of Equation 1, the parameters derived based on the full PUSCH instance are used in Equation 1.

(Method F.4-3): When the upper limit is calculated using (Method F.4-2), if the upper limit is derived as an invalid value for the split PUSCH instance for which UCI is to be multiplexed, the corresponding split PUSCH instance is dropped, and PUCCH is transmitted.

The UE calculates the upper limit applied to Equation 1 by using the values for the full PUSCH instance. Thereafter, by using the number of REs of the split PUSCH instance, it may be determined whether the calculated upper limit value is valid (ie, whether the upper limit value is not greater than the number of REs of the split PUSCH instance). When it is determined that the upper limit value is invalid, the UE does not transmit the corresponding split PUSCH instance, but may transmit the PUCCH instead.

The above-described (Method F.4-1), (Method F.4-2), and (Method F.4-3) can be applied at least when the base station instructs the UE to perform one alpha scaling. The value of alpha scaling can be determined so that the amount of resources (the number of REs) for PUSCH allocated by the base station is sufficient so that UCI and TB can obtain a sufficient error rate. However, when UCI is multiplexed in the split PUSCH instance, it may be considered that alpha scaling is used with a different value. Since the number of REs of a split PUSCH instance may vary greatly, an error rate of TB and/or UCI may vary greatly when a split PUSCH instance is decoded.

(Method F.4-4): The base station may calculate a value of one alpha scaling based on the full PUSCH instance, and may indicate the value of another alpha scaling for the split PUSCH instance to the UE.

The alpha scaling value applied by the UE to the full PUSCH instance and the alpha scaling value applied by the UE to the split PUSCH instance may be different from each other. The base station may indicate (or set) two or more alpha scaling values to the terminal through RRC signaling.

In order to determine the alpha scaling value for the split PUSCH instance, it is necessary to assume the split PUSCH instance. For a standard split PUSCH instance (ie, a reference split PUSCH instance), an alpha scaling value that sufficiently lowers the error rates of TB and UCI may be derived. A reference split PUSCH instance is defined in the technical standard, and the base station may calculate an alpha scaling value based on the reference split PUSCH instance.

Depending on the allocation of the Split PUSCH instance, even for one or more alpha scaling value(s) indicated to the UE, the error rate of TB and/or UCI is not low enough, or an invalid upper limit value is derived from Equation 1 can In this case, it is preferable not to transmit UCI.

(Method F.4-5): If an invalid upper limit value is derived from Equation 1 from all alpha scaling values indicated to the UE, or the error rate of TB and/or UCI is not sufficiently low, the split PUSCH instance is not transmitted. Instead, PUCCH may be transmitted instead.

(5) Multiplexing method of UCI having different priorities

The UE may transmit UCIs having different types/priorities in one uplink channel. For example, a case in which PUCCHs related to UCI overlap each other in time or a case in which a PUSCH and PUCCH overlap in time may occur. At this time, since PAPR/IMD occurs when the UE transmits several PUCCH(s) or PUSCH(s) at the same time, the UE may not be able to allocate sufficient transmission power.

Hereinafter, when time resources of PUCCH corresponding to UCI and/or PUSCH corresponding to TB partially overlap, when UCI and/or TB are multiplexed, a method of deriving the resources of virtually multiplexed PUCCH and/or PUSCH is described. do.

(Method F.5-1): It may be determined whether to multiplex UCIs and/or TBs with high priority first, and then multiplex UCIs and/or TBs with low priority.

Since the UE can assume that UCI and/or TB having a high priority are transmitted, a multiplexing procedure for UCI and/or TB having a high priority is performed first, and then UCI and/or TB having a low priority are performed. Alternatively, it may determine whether to further multiplex the TB. If multiplexing for low priority is performed, sufficient uplink resources (eg, bandwidth, transmission power) should be allocated to the terminal. When sufficient uplink resources are allocated to the UE, the high priority UCI and/or TB can multiplex the low priority UCI and/or TB while obtaining a sufficiently low error rate. Therefore, when allocating UCI and/or TB having high priority, it should be known to the UE whether multiplexing is allowed for UCI and/or TB of low priority.

(Method F.5-2): RRC signaling or DCI for allocating UCI and/or TB with high priority instructs the UE to multiplex UCI and/or TB with low priority or not (or configure) )can do.

When UCI and/or TB having high priority are allocated, in the case of the T1 CG scheme, PUSCH resources may be allocated by RRC signaling. In the case of the T2 CG scheme, PUSCH resources are allocated through RRC signaling and DCI, and may be additionally allocated through DCI. Resources of PUCCH for transmitting HARQ-ACK may also be allocated as RRC signaling and DCI for allocating SPS PDSCH. In addition, the resource of the PUCCH for the dynamically allocated PDSCH may be allocated as DCI. Accordingly, UCI and/or TB having high priority may be indicated to the UE through several RRC signaling or DCIs.

(Method F.5-3): In (Method F.5-2), in order to multiplex UCI or TB with high priority and UCI with low priority, DCI allocating UCI with high priority Multiplexing may be indicated in (s), and a resource to be used for multiplexing may be indicated in the last received DCI among DCI(s).

When DCI is involved in allocating UCI and/or TB with high priority, UCI and/or TB with high priority may be multiplexed to the uplink resource indicated by the DCI received last to the UE. . According to an indication of the corresponding DCI, UCI and/or TB having a low priority may also be multiplexed to the corresponding uplink resource.

When the DCI receives an instruction to multiplex UCI and/or TB having low priority, the UE may multiplex all or part of UCI and/or TB having low priority to the corresponding uplink resource.

(Method F.5-4): After performing (Method F.5-1), if PUCCHs related to UCIs of low priority overlap in time with a virtual PUCCH, whether the UCIs are multiplexed can be determined sequentially. have.

(Method F.5-5): In (Method F.5-2), when UCIs with low priority are multiplexed, only some UCI types, or UCIs with relatively high priority in the same UCI type) It can be multiplexed with UCI or TB with high priority.

The priority of the UCI type may be HARQ-ACK, SR, and CSI in the highest order. CSI may be further subdivided according to the priority of the CSI report.

For example, when it is necessary to determine whether or not the eMBB SR is to be multiplexed after the URLLC SR and the URLLC HARQ-ACK are multiplexed, the eMBB SR does not need to be transmitted, and thus the eMBB SR may be dropped.

For example, when the eMBB SR is multiplexed after the URLLC HARQ-ACK is multiplexed, the multiplexing procedure may be determined in consideration of both the UCI type of SR and the priority of eMBB/URLLC.

For example, when the URLLC SR and the eMBB SR are multiplexed, the URLLC SR and the eMBB SR may be included as one codeword or may be included as each codeword.

For example, if it is necessary to determine whether or not to multiplex the eMBB HARQ-ACK and the eMBB CSI after the URLLC HARQ-ACK is multiplexed, all of the eMBB CSI may not be transmitted. In this case, the multiplexed UCI may be considered according to the UCI type. Alternatively, some CSI report(s) with low priority in eMBB CSI may not be transmitted. In this case, the multiplexed UCI may be determined in consideration of both the UCI type and the relative priority.

In (Method F.5-4), if PUCCHs associated with UCIs of low priority overlap with a virtual PUCCH in time, whether the corresponding UCIs are multiplexed is determined in the order in which the first symbol of the PUCCH associated with the UCIs arrives first. have.

On the other hand, (Method F.5-5) can be easily extended even when TB is multiplexed. When it is determined whether or not to multiplex the eMBB TB after the URLLC HARQ-ACK and the URLLC TB are multiplexed, all the eMBB TBs may not be transmitted.

(Method F.5-6): In (Method F.5-2), when a UCI having a high priority and a UCI having a low priority are multiplexed, the multiplexed PUCCH resource is a PUCCH resource having a high priority. can only be considered as a set of

When UCIs with the same priority are multiplexed, the UE determines a resource set of PUCCHs according to the amount of UCIs (ie, the number of bits), and receives additional indications of the resource index of PUCCH by DCI or RRC signaling. It is possible to determine the resource of one PUCCH belonging to the set. If UCIs of different priorities are multiplexed, the UE may not determine the resource set of PUCCHs according to the arithmetic amount of UCIs because resource allocation for high-priority UCIs and low-priority UCIs may not be considered equally. may not be

(Method F.5-7): The UE may consider the code rate in order to derive the amount of UCI.

비트이고 이에 적용되는 부호율이

으로 주어지고, 낮은 우선순위에 대한 UCI의 양이

비트이고 이에 적용되는 부호율이

으로 주어질 수 있다. 이 때, UCI의 유효한 양은 부호율로 나누어 주어질 수 있다. 그러므로, UCI의 도출된 유효한 양은

으로 주어질 수 있으며, 이는 정수가 아닐 수도 있다.

의 값은, (방법 F.5-6)을 적용할 때 PUCCH 자원들의 집합을 선택하기 위해 활용될 수 있다.As an example, the amount of UCI with high priority is

bit and the code rate applied to it is

given as , and the amount of UCI for lower priority is

bit and the code rate applied to it is

can be given as In this case, the effective amount of UCI may be divided by the code rate. Therefore, the derived effective amount of UCI is

, which may not be an integer.

The value of may be utilized to select a set of PUCCH resources when (Method F.5-6) is applied.

(6) Multiplexing method of PUSCH and UCI transmitted in unlicensed band

In a system operating in the unlicensed band, some or all of the carriers may belong to the unlicensed band. When a carrier of a licensed band (an uplink carrier or a supplementary uplink (SUL) carrier) is configured, it is preferable to configure PUCCH to be transmitted in a carrier of a licensed band in order to transmit UCI. However, when PUSCH and PUCCH are to be transmitted in the same time resource, in order to reduce PAPR and/or IMD, the UE may multiplex UCI and data to one PUSCH. Therefore, when the PUSCH is to be transmitted in the unlicensed band, the UCI may be multiplexed and transmitted in the PUSCH of the unlicensed band instead of being transmitted in the licensed band. Thereafter, the UE may determine whether PUSCH can be transmitted using the LBT procedure. Although the base station can predict the transmission of the PUSCH using the UL-DCI, it is difficult to predict the transmission of the PUSCH allocated in the T1/T2 CG scheme due to the UL skipping procedure. Therefore, the base station cannot always avoid the time resources of UCI and PUSCH (including at least PUSCH allocated in the T1/T2 CG scheme) only by scheduling.

(Method F.6-1): The UE may transmit the PUCCH and the PUSCH on each carrier simultaneously (simultaneous).

When the PUSCH is scheduled in the unlicensed band and the PUCCH is transmitted in the licensed band, the base station may allow the UE to simultaneously transmit the PUCCH and the PUSCH. In this case, when the transmission power of the UE is sufficient, both the power indicated for transmitting the PUCCH and the power indicated for transmitting the PUSCH may be satisfied. However, when the transmission power of the UE is insufficient, the UE may transmit the PUSCH with the remaining power after using the indicated transmission power to transmit the PUCCH as it is.

In order for the UE to simultaneously transmit the PUCCH and the PUSCH, the capability of the UE must be separately managed and configured. To solve this, the UE may transmit only PUCCH or PUSCH.

(Method F.6-2): When the PUCCH is transmitted, the UE may not transmit the PUSCH.

The base station may schedule the terminal not to transmit the PUSCH in the unlicensed band. However, since the PUSCH allocated in the T1/T2 CG method is not dynamically scheduled by the base station, the UE may transmit the corresponding PUSCH in the unlicensed band. In this case, UCI may be multiplexed to the corresponding PUSCH. According to (Method F.6-2), the UE may transmit only the PUCCH without transmitting the PUSCH. (Method F.6-2) can be applied to at least CG PUSCH. In order for the UE to transmit the PUSCH, the TB is transmitted from the upper layer to the physical layer. According to (Method F.6-2), if the MAC layer (or HARQ entity) determines that the time resource for transmitting the UCI and the time resource for transmitting the PUSCH overlap, the upper layer does not deliver the TB to the physical layer. may not be

In one example, the MAC layer may not deliver the TB to the physical layer even if the UE receives the UL-DCI. In the case of CG PUSCH, the MAC layer may not deliver the TB to the physical layer. In another example, when the UE receives the UL-DCI, the MAC layer may deliver the TB to the physical layer, and in the case of the CG PUSCH, the MAC layer may not deliver the TB to the physical layer.

G. Transmission method of PT-RS

(1) PT-RS transmission method

A phase-tracking reference signal (PT-RS) is a pilot transmitted for compensating for a phase error in a system operating in FR2. REs occupied by the PT-RS are limited to the areas of PDSCH and PUSCH, and are distinguished from TRS transmitted regardless of data allocation. A time resource and a frequency resource to which the PT-RS is mapped are defined in the technical standard, and the base station may indicate the PT-RS resource to the terminal by RRC signaling.

)은 MCS에 의해서 결정되며, 표 4는 PUSCH의 지시된 MCS에 따른 PT-RS의 시간 간격들의 일 예를 표시한다. MCS 인덱스가 소정 값보다 낮은 경우에는 PT-RS가 맵핑되지 않는다. 상위계층 시그널링으로 단말에게 지시된 MCS 인덱스 범위들에 따라서,

은 1, 2, 4 값들 중에서 하나로 결정된다. MCS 인덱스가 높을수록

의 값은 작게 대응된다. 그 이유는 변조율과 복조율이 높아질 수록 위상이 더 많은 오류를 가지기 때문이다.The time resource of the PT-RS has a constant time interval from the last symbol to which the DM-RS is mapped. The MCS applied to the PUSCH is indicated by scheduling/activating DCI or RRC signaling for allocating the PUSCH. According to the technical standard, the time interval (

) is determined by the MCS, and Table 4 shows an example of time intervals of the PT-RS according to the MCS indicated by the PUSCH. If the MCS index is lower than a predetermined value, the PT-RS is not mapped. According to the MCS index ranges indicated to the UE by higher layer signaling,

is determined as one of 1, 2, or 4 values. The higher the MCS index, the more

The values of are small. The reason is that the higher the modulation and demodulation rates, the more errors the phase has.

)가 정해져 있으며, 표 5는 PUSCH에 할당된 대역폭에 따른 PT-RS의 주파수 밀도들의 일 예를 표시한다. 할당된 대역폭이 소정의 값보다 작으면, PT-RS가 맵핑되지 않는다. 상위계층 시그널링으로 단말에게 지시된 대역폭 범위들에 따라서,

은 2, 4 값들 중에서 하나로 결정된다. 대역폭이 넓을수록

의 값은 크게 대응되어 주파수 밀도가 감소한다.Meanwhile, the frequency resource of the PT-RS may be PRBs having regular intervals among PRBs belonging to the PUSCH. According to the technical specification, these frequency intervals (or density

) is determined, and Table 5 shows an example of the frequency densities of the PT-RS according to the bandwidth allocated to the PUSCH. If the allocated bandwidth is less than a predetermined value, the PT-RS is not mapped. According to the bandwidth ranges indicated to the terminal by higher layer signaling,

is determined as one of 2 or 4 values. the wider the bandwidth

The values of α are largely corresponding to a decrease in frequency density.

(2) How to support T2 FDRA

A system operating in the unlicensed band requires waveform characteristics different from those of the licensed band in time and frequency domains in order to satisfy various frequency regulations. That is, the base station or the terminal can use the resource only when it succeeds by performing the LBT procedure for a certain resource. The maximum time to use the resource is limited by the technical specification, and the minimum frequency bandwidth is also limited by the technical specification. In addition, according to the technical standard, the maximum value of the average value of the power density in the band occupied by the base station or the terminal is determined. In order to satisfy these conditions, the PUCCH and PUSCH transmitted by the UE have an interlace structure. The interlace structure refers to a structure of frequency resources in which PRBs are arranged at equal intervals. According to the technical standard, type 2 resource allocation (T2 FDRA) for allocating frequency resources of PUSCH as index(s) of interlace(s) may be indicated to the UE.

을 따르는 맵핑)을 따르기 때문에, T2 FDRA에 적용되는 PT-RS의 주파수 밀도를 결정하기 어렵다.When PUSCH supports T2 FDRA in FR2, PT-RS may also be configured for the UE. A PT-RS may be mapped according to a resource allocation scheme for PUSCH. In this case, according to the conventional PT-RS, the criteria applied in T0 (type 0) FDRA or T1 (type 1) FDRA (eg,

mapping), it is difficult to determine the frequency density of the PT-RS applied to the T2 FDRA.

(2.1) Interpretation of temporal density

In the PUSCH allocated to the T0 FDRA or the T1 FDRA, the PT-RS may not be mapped to a low MCS area. However, since non-discontinuous PRBs may be allocated according to a method of allocating an interlace with the T2 FDRA, a method of integrally compensating for a phase error by bundling several PRBs in the frequency domain may not be applied.

(Method G.2-1): PT-RS may be mapped even in low MCS.

For the PUSCH allocated to the T2 FDRA, a PT-RS may be required even at a low MCS depending on the capability of the UE. According to the technical standard, the time density value of the PT-RS may be determined.

In the further proposed method, the PT-RS may be unnecessary in the low MCS depending on the capability of the UE. Therefore, it is preferable that the time density value of the PT-RS in the low MCS region can be set. For example, Table 6 shows an example of the time densities of the PT-RS according to the MCS index allocated to the PUSCH. The MCS area is indicated to the UE by RRC signaling, and the time density of the PT-RS for the low MCS area is given as _{r 0 .} Here, _{the value of r 0} is indicated by RRC signaling and may mean that PT-RS does not exist or may mean one value. r1, r2, and r3 may have values determined by the technical standard.

(2.2) Analysis of frequency density

(Method G.2-2): The value of the frequency density of the PT-RS may be determined using at least the number of PRBs of the PUSCH.

An interlace indicated by T2 FDRA consists of several PRBs. The number of PRBs constituting the interlace is determined according to the uplink BWP. At this time, the value of the frequency density of the PT-RS may be determined using the number of PRBs. When the PUSCH is composed of M PRBs, the section to which M belongs is determined by a rule (eg, Table 5) determined in the technical standard, and accordingly, the frequency density of the PT-RS may be given as one value. PUSCH is allocated as T2 FDRA, and may be indicated by one or more interlace(s). The value of M may be determined based on the subcarrier spacing of the PUSCH, the number of interlace(s), and the bandwidth of the uplink BWP.

48 is a conceptual diagram for explaining methods in which PT-RSs are mapped according to an embodiment of the present invention.

)이 결정되면, PT-RS는 PUSCH가 할당된 PRB들 중

개의 PRB들마다 맵핑된다.

이 지시되면, PUSCH에 속한 모든 PRB들에 PT-RS가 맵핑될 수 있다. 도 48은

가 지시된 경우의 (방법 G.2-2)에 따른 PT-RS 매핑의 예들을 도시하고 있다. 경우 (a)에서 PT-RS들이 동일한 간격을 가지고 맵핑될 수 있다. 그 이유는 인터레이스들의 개수와

가 같은 값을 가지기 때문이다. 경우 (b)에서 PT-RS가 다른 간격들을 가지고 맵핑될 수 있다. 그 이유는 인터레이스들의 개수와

가 다른 값을 가지기 때문이다.The value of the frequency density of the PT-RS (eg,

) is determined, the PT-RS is among the PRBs to which the PUSCH is allocated.

Each of the PRBs is mapped.

If this is indicated, the PT-RS may be mapped to all PRBs belonging to the PUSCH. 48 is

It shows examples of PT-RS mapping according to (Method G.2-2) in the case where is indicated. In case (a), PT-RSs may be mapped with the same interval. The reason is the number of interlaces and

because they have the same value. In case (b), the PT-RS may be mapped with different intervals. The reason is the number of interlaces and

because it has a different value.

(Method G.2-3): The value of the frequency density of the PT-RS may be determined using at least the number of interlace(s) of the PUSCH.

The value of the frequency density of the PT-RS may be given as a function of the number of interlaces, not the number of PRBs of the PUSCH. According to (Method G.2-3), since the T2 FDRA allocates interlace(s), one interlace has a feature of being mapped to the entire LBT subband, and the bandwidth to which the PUSCH is allocated is at least one LBT subband of If PUSCH is allocated in two or more LBT subbands, one interlace means PRBs mapped with the same interval in all allocated LBT subbands. The number of PRBs of the PUSCH is limited to a predetermined number, which is determined by the number of allocated interlaces and the number of allocated LBT subbands.

)이 결정되면, PT-RS는 PUSCH가 할당된 인터레이스를 단위로

개의 인터레이스마다 맵핑된다. 즉, 인터레이스(들)에서

개가 선택되고, 선택된 인터레이스(들)에 속한 PRB들에서만 PT-RS가 맵핑된다. PUSCH를 할당하는 DCI/RRC 시그널링에 따라서, 어떠한 인터레이스(들)에 PT-RS가 맵핑될 수 있는지가 결정될 수 있다. 여기서 PT-RS를 생성하는 시퀀스는 PRB 인덱스에 대한 순서로 맵핑될 수 있다.The value of the frequency density of the PT-RS (eg,

) is determined, the PT-RS is based on the interlace to which the PUSCH is allocated.

Each interlace is mapped. That is, in the interlace(s)

is selected, and only PRBs belonging to the selected interlace(s) are mapped to the PT-RS. According to DCI/RRC signaling for allocating PUSCH, it may be determined to which interlace(s) the PT-RS can be mapped. Here, the sequence for generating the PT-RS may be mapped in the order of the PRB index.

Table 7 shows an example in which (Method G.2-3) is applied. The base station indicates to the terminal the boundary of the number of interlace(s) by RRC signaling, so that the number of interlace(s) constituting the PUSCH always belongs to a predetermined interval. The predetermined period may mean an interval of interlaces to which PT-RSs are mapped. According to Table 7, the PT-RS considers the interlace interval k ₀ , k ₁ , or k ₂ , and may be mapped in such interlace(s), and _{the value of k 0} , k ₁ , or k ₂ is the technical specification. can be determined by

In the proposed method, a PT-RS may not be mapped to a PUSCH composed of less than a predetermined number of interlaces. That is, k ₀ may mean that the PT-RS is not mapped.

In the proposed method, even if one interlace is allocated, the PT-RS may be mapped. That is, _{the value of k 0} may be a natural number of 1 or more.

(Method G.2-4): The value of the frequency density of the PT-RS may be determined regardless of the number of interlace(s) of the PUSCH.

The PT-RS may also be mapped to a PUSCH to which one interlace is allocated. In this case, whether the PT-RS is mapped may be determined according to the MCS indicated for the PUSCH. Even when two or more interlaces are allocated to the PUSCH, the PT-RS may be mapped to PRB(s) belonging to one interlace. According to DCI/RRC signaling for allocating PUSCH, it may be determined to which interlace the PT-RS may be mapped.

(3) Example of PUSCH repetition type B

In order to transmit traffic for the purpose of low delay and high reliability, the base station may instruct the UE to repeatedly transmit PUSCH. When PUSCH repetition type B is indicated to the UE, the UE may transmit a PUSCH occasion. Additionally, invalid symbol(s) are indicated to the UE, and the UE may have to map PUSCH instance(s) using only the valid symbol(s). In this process, a split PUSCH instance may occur, and in this case, the MCS indicated to the UE may be interpreted differently.

(Method G.3-1): PT-RS may be mapped based on the PUSCH occasion.

In PUSCH repetition type B, the same data is repeatedly transmitted. Therefore, a PUSCH occasion may be interpreted as one PUSCH. PT-RS may not be mapped in low MCS. In one full PUSCH instance constituting the PUSCH occasion, although the PT-RS must be mapped because the code rate is high (eg, L is small), the effective code rate derived from the PUCCH occasion is low (eg, K is large) PT-RS may not be mapped. That is, when the number (L) of the symbols of the PUSCH instance is small but the repetition number (K) is large, the PT-RS may be mapped while the MCS applied to the PUSCH instance crosses the boundary value, but the total amount of resources of the PUSCH occasion In some cases, the PT-RS may not be mapped because the effective MCS is smaller than the boundary value.

In order to support this more efficiently, the PT-RS may be mapped to all REs allocated to the PUSCH occasion. The time density of the PT-RS may be applied from the DM-RS of the first PUSCH instance of the PUSCH occasion. The symbol(s) to which the PT-RS is mapped may belong to valid symbol(s) in the time window of the PUSCH occasion. When the DM-RS is located in a symbol to which the PT-RS is to be mapped, the PT-RS may not be mapped to the symbol in which the DM-RS is located.

MCS for determining the time density of the PT-RS may be derived from the number of REs actually utilized in the PUSCH occasion. That is, since the modulation rate is not changed, but the code rate is changed according to the number of effective symbol(s), an actually applied modulation/demodulation rate can be derived. When the modulation/demodulation rate actually applied is derived, the time density for mapping the PT-RS is determined according to which section of the MCS index belongs to the modulation/demodulation rate.

(Method G.3-2): PT-RS may be mapped based on PUSCH instance.

If MCS is included in DCI/RRC signaling for allocating PUSCH occasion, PT-RS may be mapped using it as it is. That is, the MCS applied to the full PUSCH instance becomes the standard. If the PT-RS is transmitted, the PT-RS may be mapped to the PUSCH instance.

In the case where some split PUSCH instances are generated by indicating invalid symbol(s) to the UE, separate optimization may not be performed. That is, whether the PT-RS is mapped to the split PUSCH instance is determined according to the full PUSCH instance.

H. How to transmit SRS

(1) How to transmit SRS in unlicensed band

A resource (hereinafter, referred to as an 'SRS resource') for transmitting a sounding reference signal (SRS) may consist of one or more SRS symbol(s). SRS may be transmitted when the LBT procedure is successful. The base station may indicate the SRS resource to the terminal through higher layer signaling. The SRS resource may be periodically/semi-statically configured or may be dynamically indicated.

According to a conventional technical standard, a case in which SRS and PUCCH/PUSCH are transmitted in the same subframe (or slot) and a case in which SRS and PUCCH/PUSCH are transmitted in different subframes (or slots) may be distinguished. The SRS resource may be indicated by the base station using DCI for allocating PDSCH/PUSCH to a specific terminal, or by using DCI for triggering transmission of SRS to one or more terminals.

A case in which both SRS and PUCCH/PUSCH are included in the same subframe (or slot) is considered. When an SRS resource is allocated to the last symbol(s) of a subframe (or slot) according to a conventional technical standard, PUCCH/PUSCH and SRS are time division multiplexed, and PUCCH/PUSCH is transmitted first and then SRS is transmitted. Therefore, if the terminal successfully performs the LBT procedure before the first symbol of the PUCCH / PUSCH, the terminal may transmit the PUCCH / PUSCH and then transmit the SRS. However, if the terminal fails to perform the LBT procedure, the terminal cannot transmit PUCCH / PUSCH. In this case, in the case of periodic SRS, whether the SRS is transmitted depends on the result of performing the C4 LBT procedure (or the Type 1 LBT procedure). When the terminal succeeds by retrying the LBT procedure before the first symbol of the SRS resource, the terminal may transmit the SRS. If the LBT procedure fails again, the terminal does not transmit the SRS. Alternatively, the UE may perform the LBT procedure on all SRS symbol(s) belonging to the SRS resource, and the UE may transmit the SRS in the remaining symbol(s) from the first symbol that succeeds in the LBT procedure. If the LBT procedure fails in all SRS symbol(s) belonging to the SRS resource, the UE does not transmit the SRS.

(2) Channel access method for SRS resource

(2.1) Method of allowing and restricting the temporal order of uplink concatenated transmission

If the SRS resource can start from any symbol, the prior art standard cannot be easily extended because this is a resource allocation that has not been considered in the prior art standard. This is because if the SRS resource can be started from any symbol, the SRS resource can be started before the PUCCH/PUSCH. That is, the UE may be instructed to start uplink transmission with SRS. In this case, a channel access method for SRS resources is required.

The base station may indicate to the terminal the method of CP extension (CPE) and LBT procedure by using DCI. Here, C4 LBT or C2 LBT may be indicated in the manner of the LBT procedure. When the UE transmits the PUCCH for the PDSCH or transmits the PUSCH, the UE transmits the CP extension and LBT procedure indicated by DCI (ie, C2 LBT, C4 LBT, or channel access priority class (CAPC, Channel access priority) class)) may be applied to the first symbol of PUCCH or PUSCH or before.

The base station may trigger the corresponding terminal to transmit the SRS. The time resource in which the SRS is transmitted may be indicated (or set) to the UE by higher layer signaling. As a triggering method, scheduling DCI or group common DCI (eg, DCI format 2_3) may be used. One index may be indicated to the UE in the field of DCI triggering SRS transmission. The UE may know from the received index which SRS resource to use to transmit the SRS. Thereafter, the UE may transmit the SRS in time resources (ie, symbol(s) and slots) of the corresponding SRS resource.

The first symbol of the SRS resource may not be indicated by DCI. In this case, the time resource of PUSCH/PUCCH may not be adjacent to the time resource of SRS. In particular, the interval between the SRS resource and the PUSCH/PUCCH indicated by the base station to the terminal may be greater than a predetermined time (eg, several us). Here, the predetermined time may be stipulated in a technical standard (eg, 3GPP TS37.213, etc.). If the SRS resource and the PUSCH/PUCCH have a larger interval than the predetermined time, the LBT procedure may need to be performed for transmission of the PUSCH/PUCCH (when the SRS is transmitted first).

49 is a conceptual diagram illustrating a time relationship between SRS and PUSCH/PUCCH according to an embodiment of the present invention.

In the case of FIG. 49 (a), the UE may perform the LBT procedure to transmit SRS first, and then perform the LBT procedure again to transmit PUSCH/PUCCH. In the case (b) of FIG. 49, the order is reversed.

Here, the channel access method for SRS may follow the method indicated by DCI (eg, ul-dci-triggered-UL-ChannelAccess-CPext-CAPC of DCI). Therefore, to the UE, the channel access method for SRS (ie, Type 1 channel access or Type 2/2A/2B/2C channel access), whether the CP extension is extended and the index of the length value of the CP extension, and/or channel access priority A ranking (CAPC) may be indicated. Here, various values may be indicated (or set) to the UE by RRC signaling, and one value may be given to the UE as an index in DCI. However, the channel access method for SRS indicated in DCI may not be applied to transmission of PUSCH/PUCCH.

For example, in case (a), a channel access scheme, CP extension, and/or CAPC for PUSCH/PUCCH transmitted later among non-concatenated SRS resources and PUSCH/PUCCH may not be indicated. The channel access method for PUSCH/PUCCH varies depending on the UE's determination of whether PUSCH/PUCCH is transmitted within the COT secured by the base station or transmitted outside the channel occupancy time (COT). The CP of the first symbol of PUSCH/PUCCH may not be extended. CAPC may follow a value included in DCI.

Alternatively, a channel access scheme for PUSCH/PUCCH may follow a scheme indicated by DCI (eg, ul-dci-triggered-UL-ChannelAccess-CPext-CAPC of DCI). Accordingly, a channel access scheme (ie, Type 1 channel access or Type 2/2A/2B/2C channel access), CP extension, and/or channel access priority (CAPC) for PUSCH/PUCCH may be indicated to the UE. . However, the channel access method for PUSCH/PUCCH indicated in DCI may not be applied to SRS transmission.

For example, in case (b), a channel access scheme, CP extension, and/or CAPC for SRS transmitted later may not be indicated among non-contiguous PUSCH/PUCCH and SRS. This is because the channel access method for the SRS varies according to the UE's determination as to whether the SRS is transmitted within the COT secured by the base station or transmitted outside the COT. The CP extension of SRS may not be applied.

(Method H.2-1): A channel access method for PUSCH/PUCCH and an SRS resource indicated to have a longer interval than a predetermined time. Outside the COT of the base station, a Type 1 channel access method (C4 LBT) is applied. and a Type 2 channel access scheme (C2 LBT) can be applied within the COT of the base station.

In order to transmit the SRS, the UE may observe the COT indicator from the base station. The COT indicator may be included in DCI (eg, DCI format 2_0) of a specific format broadcast to an unspecified number of terminals. The base station may instruct (or configure) the terminal to observe the COT indicator using higher layer signaling. The terminal can know the structure of the COT secured by the base station by using the COT indicator, and can check whether the time resource of the SRS belongs to the COT of the base station. According to (Method H.2-1), the LBT procedure for transmitting the SRS may vary depending on whether the time resource of the SRS belongs to the COT of the base station. If the time resource of the SRS belongs to the COT of the base station, the terminal may perform sensing for a shorter time (than the time required for Type 1 channel access) by performing Type 2/2A/2B/2C channel access. On the other hand, if the time resource of the SRS does not belong to the COT of the base station, the terminal may determine whether to transmit the SRS by performing Type 1 channel access.

On the other hand, the terminal may not be instructed to observe the COT indicator from the base station. In this case, since the terminal cannot know the COT of the base station, it is preferable to always perform the C4 LBT procedure when the terminal transmits the SRS alone. Since the method of the LBT procedure for PUSCH/PUCCH is indicated to the UE by scheduling DCI, the UE may perform Type 1 channel access (C4 LBT) or Type 2/2A/2B/2C channel access (C2 LBT). .

(Method H.2-2): Type 1 channel access scheme (C4 LBT) may be applied as a channel access scheme for PUSCH/PUCCH and an SRS resource indicated to have a longer interval than a predetermined time.

Here, when the SRS resource consists of two or more symbols, the UE may perform the LBT procedure for each symbol or may perform the LBT procedure only on the first symbol of the SRS resource.

(Method H.2-3): When Type 1 channel access is performed on an SRS resource in (Method H.2-1) or (Method H.2-2), Type 1 channel access for each symbol belonging to the SRS resource can be performed.

(Method H.2-4): When Type 1 channel access is performed for an SRS resource in (Method H.2-1) or (Method H.2-2), Type 1 only in the first SRS symbol belonging to the SRS resource Channel access may be performed.

According to the configuration of the base station and DCI, the interval between the SRS resource indicated to the terminal and the PUSCH/PUCCH may be smaller than a predetermined time. To this end, the base station must schedule the SRS resource and the PUSCH/PUCCH to be transmitted in the same slot, and the SRS resource and the PUSCH/PUCCH must be contiguous. For convenience of description, continuous transmission of the SRS and the PUSCH/PUCCH with an interval smaller than a predetermined time may be referred to as 'uplink concatenated transmission'.

Uplink concatenated transmission means uplink transmissions in which a gap not greater than 16 us is allowed. If the uplink transmissions having an interval greater than 16 us are regarded as different transmissions, they are not expressed as concatenated transmissions. For different uplink transmissions having an interval of 16 us or less, the UE may transmit an uplink after the interval without performing a channel access procedure. And, in the method for the terminal to receive an uplink concatenated transmission instruction from the base station, the PUSCH is included from one or more UL grant(s) or the PUCCH indicated from one or more DL grant(s) (ie, DCI or semi-persistent scheduling) is It may be an SRS included or indicated from one or more UL grant(s) or DL grant(s).

(Law H.2-5): Instructs the UE to transmit SRS later in uplink concatenated transmission.

50 is a conceptual diagram illustrating a time relationship between SRS and PUSCH/PUCCH in uplink concatenated transmission according to an embodiment of the present invention.

The UE may assume that the SRS is indicated to be transmitted later than the PUSCH/PUCCH in uplink concatenated transmission. According to (Method H.2-5), case (a) of FIG. 50 is not allowed and only case (b) of FIG. 50 may be allowed, and the base station may instruct the UE only for such scheduling. The reason is that the base station estimates the uplink channel using the SRS resource, and the later the SRS is received, the slower the time of acquiring the channel estimation result. In addition, the method of the LBT procedure for the SRS resource may be indicated in scheduling DCI, but the method of the LBT procedure for the SRS resource may be indicated in the group common DCI. In this case, Type 1 channel access may be performed for the SRS resource. On the other hand, according to (Method H.2-5) indicating that PUSCH/PUCCH is transmitted first in uplink concatenated transmission, when PUSCH/PUCCH is transmitted, Type 2 channel access or LBT procedure is omitted when the UE transmits SRS can do.

(2.2) LBT procedure method that can be applied when SRS precedes in uplink concatenated transmission

According to (Method H.2-5), there may be restrictions on time resources in which the SRS can be transmitted. Since SRS can be used not only for channel estimation but also for beam management, it is preferable to allow a case in which SRS is transmitted first in uplink concatenated transmission. Methods to be described later can be applied when both case (a) and case (b) of FIG. 50 can be supported in uplink concatenated transmission.

DCI for triggering SRS and DCI for allocating PUSCH/PUCCH of uplink concatenated transmission may be the same or different. Since the slot in which the SRS is triggered may be indicated (or configured) to the UE by higher layer signaling, the slot in which the SRS is triggered may be different from the slot to which the PUSCH/PUCCH is allocated.

51 to 53 are conceptual diagrams for explaining a method of allocating SRS and PUSCH/PUCCH in uplink concatenated transmission according to an embodiment of the present invention.

Referring to FIG. 51 , depending on the configuration of the base station, the slot in which the SRS is triggered and the slot in which the PUSCH/PUCCH is transmitted may be the same. In this case, one DCI may allocate both SRS and PUSCH/PUCCH belonging to uplink concatenated transmission.

In addition, the UE may receive two DCIs including a DCI for triggering SRS and a DCI for allocating PUSCH/PUCCH. A case in which time resources allocated by two DCIs are contiguous with each other (ie, consecutively located with an interval smaller than a predetermined time) may be interpreted as uplink concatenated transmission. 52 shows a case in which an order in which two DCIs are transmitted is the same as an order in which SRS and PUSCH/PUCCH are transmitted, and FIG. 53 shows a case in which an order in which two DCIs are transmitted is different from an order in which SRS and PUSCH/PUCCH are transmitted is showing

At this time, the method of the LBT procedure applied to the uplink concatenated transmission (ie, the channel access method, CP extension, and/or CAPC) may be indicated by the DCI received by the terminal. In order to apply this, the methods described below may be considered.

(Method H.2-6): The method of the LBT procedure applied to uplink concatenated transmission may be indicated by scheduling DCI for allocating PUSCH/PUCCH of uplink concatenated transmission.

In the case of (a) of Figure 51, the case of Figure 52 (a), and the case of Figure 53 (a), the LBT procedure performed by the terminal to transmit the SRS is a method indicated by DCI for allocating PUSCH / PUCCH can follow In the case of Figure 51 (b), Figure 52 (b), and Figure 53 (b), the LBT procedure performed by the UE to transmit PUSCH / PUCCH is indicated by DCI for allocating PUSCH / PUCCH. method can be followed.

DCI triggering SRS may allocate PUSCH/PUCCH without triggering only SRS. At this time, the LBT scheme indicated by DCI triggering SRS may be suitable for PUSCH/PUCCH rather than SRS resource. Accordingly, the UE may be instructed by another DCI on the method of the LBT procedure for transmitting the SRS.

(Method H.2-7): When (Method H.2-6) is applied, if the time between DCI for allocating PUCCH/PUSCH and the first symbol of uplink concatenated transmission is indicated to be shorter than a predetermined processing time, uplink When link concatenation transmission starts with SRS, in the LBT procedure for SRS transmission, the UE may use Type 1 channel access or apply the LBT method indicated by DCI triggering SRS.

When the base station instructs the terminal to transmit PUCCH/PUSCH, a predetermined processing time determined by higher layer signaling and/or processing capability of the terminal may be given to the terminal. The UE may transmit the PUSCH/PUCCH after the predetermined processing time has elapsed. When SRS is located first in uplink concatenated transmission, time for applying (Method H.2-6) (that is, processing DCI for allocating PUSCH/PUCCH to check the LBT method to be applied to uplink concatenated transmission) time) may be insufficient, so it may be difficult for the terminal to determine the LBT method to be applied to the SRS resource. In this case, the UE may apply (Method H.2-7) to transmit the SRS. It may be assumed that the UE performs Type 1 channel access on the assumption that only SRS is transmitted or that the LBT procedure for SRS resources is indicated through another method (ie, DCI triggering SRS).

The base station may assume that the method of the LBT procedure for the SRS resource and PUCCH / PUSCH configured for the terminal is not changed by another DCI. In this case, each DCI for uplink concatenated transmission may be used only to determine the method of the LBT procedure for the corresponding UL channel/signal. More specifically, when some uplink transmission is not performed according to the result of the LBT procedure in the uplink concatenated transmission, the method of the LBT procedure applied to the subsequent uplink transmission is to be indicated by the DCI corresponding to the uplink transmission. can

(Method H.2-8): Among uplink signals/channels that belong to uplink concatenated transmission and that have not yet failed in the LBT procedure, the LBT method applied to the uplink signal/channel that the terminal wants to transmit first. The indication of the base station may follow DCI for allocating the corresponding uplink signal/channel.

For example, in uplink concatenated transmission, SRS resources and PUSCH/PUCCH may be sequentially arranged, and a time interval between them may be allocated to be less than or equal to a predetermined value. When the above (Method H.2-8) is applied, the LBT method for transmitting the SRS resource is determined according to the DCI that triggered the SRS resource. If the LBT procedure performed by the terminal is successful, the terminal may transmit an SRS and then transmit a PUSCH/PUCCH without performing a separate LBT. If the LBT procedure performed by the terminal fails, the terminal does not transmit the SRS, and derives the LBT method from the DCI allocated PUSCH/PUCCH. The terminal may perform the LBT procedure, and may or may not transmit PUSCH/PUCCH according to the result.

This can be equally applied even when PUSCH/PUCCH and SRS resources are sequentially arranged in uplink concatenated transmission. The UE performs an LBT procedure before performing PUSCH/PUCCH transmission. If the LBT procedure is successful, the UE transmits both the PUSCH/PUCCH and the SRS belonging to the uplink concatenated transmission, but if the LBT procedure fails, only the PUSCH/PUCCH is not transmitted. The UE performs the LBT procedure for the remaining SRS resources in the uplink concatenated transmission to transmit or not transmit the SRS. Here, the LBT method for the PUSCH / PUCCH or SRS resource is determined according to the DCI allocated to each.

When the above (Method H.2-8) is applied, an uplink signal/channel that has failed the LBT procedure among uplink signals/channels constituting uplink concatenated transmission cannot be transmitted. Subsequent uplink signals/channels may still be regarded as uplink concatenated transmissions, and according to (Method H.2-8), the terminal uses the LBT procedure indicated by DCI to which the uplink signals/channels to be transmitted are allocated. Channel access can be performed by applying the method. In this case, CP extension may not be applied to subsequent uplink signals/channels other than the first uplink signals/channels of uplink concatenated transmission.

When the above (Method H.2-8) is applied, it may be difficult for the base station to instruct the UE to access the Type 2/2A/2B/2C channel. The reason is that in order to perform Type 2/2A/2B/2C channel access, it is necessary to be able to predict the COT of the base station, but in general, this prediction is not accurate. Therefore, it is preferable that the method of the LBT procedure can be changed later.

To solve this, for two or more DCIs for allocating uplink concatenated transmission, the base station may transmit a new DCI that changes the method of the LBT procedure indicated in the previously transmitted DCI. The new DCI does not change the trigger of SRS or resource allocation of PUSCH / PUCCH, but may change the method of the LBT procedure.

(Method H.2-9): The method of the LBT procedure applied to uplink concatenated transmission may follow the last received DCI.

For uplink concatenated transmission, SRS may be allocated first and PUSCH/PUCCH may be allocated, or PUSCH/PUCCH may be allocated first and SRS may be allocated. However, the reception order of DCIs to which each is allocated may be different. If (Method H.2-9) is applied, the DCI given in the reverse order of the received order may be selected as the method of the LBT procedure applied to uplink concatenated transmission. When uplink concatenated transmission is performed using DCI for allocating SRS and DCI for allocating PUSCH/PUCCH (Method H.2-9) is applied, the method of the LBT procedure for SRS transmission is PUSCH/PUCCH It may be indicated by an allocating DCI. Similarly, the scheme of the LBT procedure for transmission of PUSCH / PUCCH may be indicated by DCI triggering SRS.

(Method H.2-10): When (Method H.2-9) is applied, when the time between DCI for allocating PUCCH/PUSCH and the first symbol of uplink concatenated transmission is indicated to be shorter than a predetermined processing time , when the uplink concatenated transmission starts with SRS, the UE may use Type 1 channel access in the LBT procedure or apply the method of the LBT procedure indicated by DCI triggering SRS.

Since the UE can decode DCI and transmit PUCCH/PUSCH using a predetermined processing time, (Method H.2-10), as in (Method H.2-7), considers the processing time of the UE. should be able to define That is, when the SRS resource is first located in the uplink concatenated transmission, the time for applying (Method H.2-9) (that is, the DCI for allocating PUSCH/PUCCH is processed to determine the LBT method to be applied to the uplink concatenated transmission) time for confirmation) may be insufficient, so it may be difficult for the terminal to determine the LBT method to be applied to the SRS resource. In this case, in order for the UE to transmit the SRS, (Method H.2-10) may be applied. It may be assumed that the UE performs Type 1 channel access on the assumption that only SRS is transmitted or that the LBT procedure for SRS resources is indicated through another method (ie, DCI triggering SRS).

(3) How to instruct application of CP extension to SRS resources in DCI

The method of the LBT procedure applied to the SRS resource may be indicated to the terminal through DCI. If Type 2 channel access is indicated for the SRS resource, the Type 2 channel access may be applied from the first symbol of the SRS resource. However, when the SRS resource consists of two or more symbols and the terminal fails the LBT procedure in the first symbol of the SRS resource, the LBT procedure method indicated by DCI may not be applied as it is. In this case, another method of Type 2 channel access may be applied. When the LBT procedure according to type 2B channel access or type 2C channel access indicated by DCI fails, the terminal may perform Type 2A channel access for the second or subsequent SRS symbol(s).

In the uplink concatenated transmission, the case in which the SRS is transmitted earlier (in the case of FIG. 51 (a), in the case of FIG. 52 (a), in the case of FIG. 53 (a)) is considered. However, uplink concatenated transmission is not necessarily assumed, and even when only SRS is transmitted, the following methods (methods for a case in which SRS is located first) may be applied.

(Method H.2-11): If the LBT procedure fails in the first symbol of the SRS resource, the UE does not transmit both the entire SRS and the PUSCH/PUCCH.

By interpreting the uplink concatenated transmission as one uplink transmission, the UE may or may not transmit the entire uplink concatenated transmission. According to (Method H.2-11), depending on the result of the LBT procedure, the UE may not allow a kind of puncturing for uplink concatenated transmission.

However, when the SRS resource consists of two or more symbols, some SRS symbol(s) may be transmitted according to the result of the LBT procedure. In this case, (Method H.2-12) can be applied.

(Method H.2-12): If the LBT procedure performed on the first symbol of the SRS resource fails, the terminal performs the LBT procedure (Type 1, Type 2, or Type 2A channel access) in the remaining symbol(s) of the SRS resource. By performing the LBT procedure, it is possible to transmit the SRS in the SRS symbol and the subsequent SRS symbol(s), and transmit the PUSCH/PUCCH.

On the other hand, a case in which PUSCH/PUCCH is previously transmitted in uplink concatenated transmission (in the case of FIG. 51 (b), in the case of FIG. 52 (b), in the case of FIG. 53 (b)) is considered.

(Method H.2-13): If the LBT procedure performed in the first symbol of PUSCH / PUCCH fails, the UE does not transmit PUSCH / PUCCH, and LBT procedure (Type 1 or Type 2/2A in the first symbol of SRS resources) /2B/2C channel access). If the LBT procedure fails, the terminal does not transmit the entire SRS.

(Method H.2-14): If the LBT procedure performed in the first symbol of PUSCH / PUCCH fails, the UE does not transmit PUSCH / PUCCH, and LBT procedure (Type 1 or Type 2 / 2A) in the first symbol of SRS resources /2B/2C channel access). If the LBT procedure fails, the terminal may perform the LBT procedure (Type 1 channel access or Type 2A channel access) again to transmit the SRS in the SRS symbol and subsequent SRS symbol(s) in which the LBT procedure is successful.

When application of the CP extension to the SRS resource is indicated, the UE may extend the CP of the first SRS symbol to be transmitted in the SRS resource. DCI may indicate the length of the extended CP as one of several values.

54 is a conceptual diagram for explaining SRS symbols to which CP extension is applied according to an embodiment of the present invention.

In FIG. 54, an example of an SRS resource composed of two symbols is shown. When the SRS is transmitted from the second SRS symbol or a subsequent SRS symbol of the SRS resource, the CP is not extended and the SRS may be transmitted at the position of the symbol(s) included in the SRS resource.

Case (a) represents a case in which CP extension is not performed. Case (a) may correspond to a case in which the terminal does not perform the LBT procedure to transmit the SRS, or it can be assumed that the preceding symbol is not occupied by another base station, terminal, or other node. The reason is that the channel is sensed in the preceding symbol period in order to match the time point of completing the LBT procedure to the boundary of the symbol.

In case (b), the UE may apply CP extension. The UE may transmit the CP derived from the first SRS symbol in C1 symbol(s) located in front of the SRS resource. The value of C1 is defined by the technical standard, and the value of C1 may be defined as 1 when the subcarrier spacing of the SRS resource is 15 kHz, and may be defined as 2 when the subcarrier spacing of the SRS resource is 30 kHz. Case (b) of FIG. 54 shows a case where C1 is given as 1.

In case (c), the UE may apply CP extension. The UE may transmit the CP derived from the first SRS symbol in C2 symbol(s) located in front of the SRS resource. The value of C2 may be indicated to the UE by higher layer signaling. Case (c) of FIG. 54 shows a case where C2 is given as 2.

In case (d), the UE may apply CP extension. The UE may transmit the CP derived from the first SRS symbol in C3 symbol(s) located in front of the SRS resource. The value of C3 may be indicated to the UE by higher layer signaling. Case (d) of FIG. 54 shows a case where C3 is given as 3.

55 is another conceptual diagram for explaining SRS symbols to which CP extension is applied according to an embodiment of the present invention.

In FIG. 55, for convenience of description, an example of an SRS resource composed of two symbols is shown. When (Method H.2-12) is applied, the time point at which channel access is performed is shown. (a), (b), (c), and (d) in FIG. 55 correspond to (a), (b), (c), and (d) in FIG. 54 , respectively. If channel access is not successful in the first symbol of the SRS resource, the first symbol of the SRS resource is not transmitted. Thereafter, the terminal performs channel access at a time point for transmitting the next symbol of the SRS resource. If channel access is successful, the UE may transmit SRS in the remaining symbols of the SRS resource. The UE may repeat this to transmit SRS in all or part of symbol(s) of SRS resources.

For convenience of explanation, the timing advance of (b), (c), and (d) of FIG. 54 and (b), (c), and (d) of FIG. 55 is in the CP extension The time length of the first symbol may be determined. 54 and 55 represent time from the viewpoint of the base station, the terminal may perform LBT on the symbol of the SRS resource at the boundary of the symbol. If the LBT is successful, the terminal transmits an SRS, and the transmitted SRS is received by the base station after the timing advance time elapses. Therefore, since the terminal performs channel access immediately before transmitting a symbol belonging to the SRS resource, from the viewpoint of the terminal, it can be interpreted as performing LBT at or immediately before the boundary of the symbol.

For SRS transmitted periodically or semi-statically by higher layer signaling other than DCI, CP extension may not be applied. This case corresponds to case (a) of FIG. 54 and case (a) of FIG. 55, and channel access may be performed for each SRS symbol. Accordingly, the UE may transmit the entire SRS or a part of the SRS.

(3) How the UE transmits SRS resources at the boundary of the COT of the base station

When the SRS is transmitted regardless of the time (eg, gNB COT) secured by the base station, type 1 channel access may be indicated to the terminal. However, the terminal receiving the COT indicator from the base station may change the channel access method for uplink transmission belonging to the COT of the base station from the indicated type 1 channel access to the type 2, type 2A, type 2B, or type 2C channel access. However, if some symbol(s) of uplink transmission do not belong to the COT of the base station, the terminal may perform only type 1 channel access.

When uplink transmissions are concatenated and all uplink transmissions belong to the COT of the base station, the channel access scheme may be changed. That is, if the type 2, type 2A, type 2B, or type 2C channel access for a certain uplink transmission fails, the remaining uplink transmission may be performed through the type 2A channel access. That is, the sensing period of the LBT procedure may be longer. For example, the sensing period of the LBT procedure may be changed from 0 us or 16 us to 25 us.

(Method H.3-1): Uplink transmission includes at least SRS, and when it can be determined that the SRS resources are all within the COT of at least the base station, it is allowed to change the channel access method for the SRS resources.

The SRS to be transmitted by the terminal is composed of two or more symbols, some symbol(s) may belong to the COT of the base station, and the remaining symbol(s) may not belong to the COT of the base station. In this case, the UE may apply the following methods to transmit the SRS.

(Method H.3-2): If there are SRS symbol(s) that do not belong to the COT of the base station, the UE does not transmit the entire SRS.

The UE interprets the SRS resource as one unit and can perform channel access only when all symbols of the SRS resource are included in the COT of the base station. Here, the method (H.2-11) or the method (H.2-12) may be combined and performed.

Even if some of the SRS symbol(s) of the SRS resource do not belong to the COT of the base station, it may be desirable to transmit the remaining SRS symbol(s). To this end, (Method H.3-3) or (Method H.3-4) may be applied, and additionally (Method H.2-11) or (Method H.2-12) may be applied. Although transmission of the SRS symbol(s) may not be allowed outside the COT of the base station, the UE may transmit the SRS symbol(s) by performing channel access again.

(Method H.3-3): Only the SRS symbol(s) belonging to the COT of the base station is transmitted through channel access, and the remaining SRS symbol(s) are not transmitted.

The terminal receives the COT from the base station and considers that transmission of only SRS symbol(s) belonging to the shared COT is possible. Accordingly, the UE may transmit the SRS symbol(s) belonging to the shared COT by performing type 2, 2A, 2B, or 2C channel access. In addition, the UE may not perform channel access to the SRS symbol(s) that do not belong to the COT.

56 is another conceptual diagram for explaining SRS symbols to which CP extension is applied according to an embodiment of the present invention.

In FIG. 56, for convenience of description, an example of an SRS resource composed of two symbols is shown. If the COT of the base station lasts only until the first symbol of the SRS resource or the symbol to which the CP extension of the first symbol is applied, the second symbol of the SRS resource does not belong to the COT of the base station. Therefore, according to (Method H.3-3), all symbols of the SRS resource cannot be transmitted.

On the other hand, a part of the SRS resource may be allowed to be transmitted.

(Method H.3-4): Channel access to SRS symbols belonging to the COT of the base station and channel access to SRS symbols not belonging to the COT are distinguished, and depending on the channel access, some of the SRS symbols may be transmitted. have.

Channel access to symbols belonging to the SRS resource belonging to the COT of the base station may be changed. That is, the terminal performs channel access of the changed method by changing the channel access method for symbols belonging to the SRS resource belonging to the COT from the type 1 channel access to the type 2, 2A, 2B, or 2C channel access, and the SRS belonging to the COT. Symbols belonging to a resource may be transmitted. Thereafter, when the COT of the base station is finished, in order to transmit the subsequent SRS symbol(s), the terminal must perform new channel access. That is, the remaining SRS symbols should belong to the COT of the terminal. Accordingly, at least one SRS symbol that starts immediately after the COT of the base station ends cannot be transmitted. This is because, after the COT of the base station is terminated, it is necessary for the terminal to newly perform channel access.

In case (a), the COT of the base station continues until immediately before the first symbol of the SRS resource. Accordingly, the terminal performs channel access, but the channel access method is not changed because the SRS resource is outside the COT of the base station. Since the LBT procedure for the CPE symbol (or region) obtained from the first symbol is performed within the COT of the base station, it takes time for the terminal to perform type 1 channel access in order to transmit the remaining SRS resources. If the base station or another terminal is already transmitting, the type 1 channel access performed by the terminal may fail, and depending on the result of the type 1 channel access, the terminal (outside the COT of the base station) may transmit the second symbol of the SRS resource. have.

In cases (b), (c), and (d), the COT of the base station continues until the CPE symbol in which the first symbol of the SRS resource is extended. Therefore, the LBT procedure for the first symbol of the SRS resource may fail because the type 1 channel access method is performed within the COT of the base station. According to the result of type 1 channel access to the second symbol, the UE may transmit the corresponding symbol (outside the COT of the base station).

If CPE is applied to the first symbol of the SRS resource, the same SRS sequence may be transmitted in two or more symbols. This is also illustrated in FIGS. 54 , 55 , and 56 . In this case, it may be interpreted that the corresponding SRS sequence is repeatedly transmitted in two or more symbols. Therefore, when the same SRS sequence is transmitted, it can be further divided into symbol(s) belonging to the COT of the base station and symbol(s) not belonging to the COT.

(Method H.3-5): In (Method H.3-3) or (Method H.3-4), only a part of the CPE region generated from the first symbol of the SRS resource may be transmitted using the COT of the base station. have.

In case (b), the section to which CPE is applied is smaller than one symbol. However, in cases (c) and (d), the period to which the CPE is applied is longer than one symbol. Accordingly, when a symbol belonging to the COT of the base station includes the CPE, it may include one or more complete SRS symbols, which have the same sequence as the first symbol of the SRS resource. That is, if the symbol in front of the SRS resource includes the CPE, the SRS may also be transmitted in the corresponding symbol. In this case, according to (Method H.3-5), all or part of the CPE portion of the SRS symbol belonging to the COT of the base station may be transmitted. In this case, the terminal can transmit all or part of the CPE portion of the SRS symbol belonging to the COT of the base station only when it succeeds by performing type 2, 2A, 2B, or 2C channel access. SRS symbol(s) that do not belong to the COT of the base station are not transmitted. That is, the first symbol of the SRS resource and a part of the CPE portion are not transmitted. However, the second symbol of the SRS resource may be transmitted according to the result of type 1 channel access.

(4) How to dynamically indicate SRS resources

The base station may instruct the terminal to transmit the SRS using DCI. Time resources and frequency resources required to transmit the SRS may be indicated by DCI. The following methods may be applied in a licensed band or an unlicensed band.

(Method H.4-1): The time and frequency resources indicated by the UL-DCI may represent the resources through which the SRS is transmitted.

The UE may check the indicated SRS resource by combining a field indicating time and frequency resources in UL-DCI, an SRS trigger field, and a field indicating the presence or absence of UL-SCH.

When the UL-DCI indicates that a TB is included in the PUSCH and the SRS trigger field indicates one index, the UE transmits the SRS in the SRS resource corresponding to the indicated index. Here, time and frequency resources are not determined by DCI. On the other hand, if the UL-DCI indicates that the PUSCH does not include a TB and the SRS trigger field indicates one index, the UE transmits the SRS in the SRS resource corresponding to the indicated index, but time and frequency resources are provided by DCI. can be decided.

The frequency resource indicated by UL-DCI is composed of consecutive PRBs, and may be composed of multiples of 2 or multiples of 4, not common multiples of 2, 3, and 5. In addition, SLIV indicated by UL-DCI may indicate symbols through which SRS is transmitted. SLIV is divided into S and L, and S means the first symbol in which the SRS is transmitted.

According to another method, a TB is not allocated to a UE by UL-DCI, and only SRS transmission may be triggered by UL-DCI. Here, it may be implicitly indicated from the UL-DCI that the TB is not allocated.

(Method H.4-2): In UL-DCI, it is possible to express at least a time resource in which the SRS is transmitted.

(Method H.4-3): In (Method H.4-2), the index of the frequency resource expressed by UL-DCI may be assigned an index implying that the size of the TB is 0.

If an index representing a frequency resource has a specific value and indicates one index in the SRS trigger field, the UE does not transmit a TB and transmits an SRS resource corresponding to the indicated index. Here, the time resource may be determined by DCI.

I. Scheduling PDCCH support method

(1) Out-of-order scheduling and Overlapped data channel reception method

A UE may support traffic having two or more severities. When PDSCH/PUSCH is allocated, the importance of traffic is indicated to the UE as a priority index using RRC signaling or DCI field. The base station transmits two PDCCHs to the terminal, and the PDCCHs may allocate a PDSCH (and a PUCCH including HARQ-ACK) or a PUSCH having different priority indices. Here, the time interval between the PDCCH and the PDSCH may be given by K0 slot(s), and the time interval between the PDCCH and the PUSCH may be given by K2 slot(s).

Several TRPs connected by a backhaul may be considered. If a delay occurs in the backhaul, even if the TRPs belong to one base station, it may be difficult to dynamically perform scheduling cooperation. In some cases, the scheduling allocated by one TRP and the scheduling allocated by the other TRP may be indicated independently. This can be explained by referring to FIG. 57, FIG. 58, or a combination of FIGS. 57 and 58, which will be described later.

57 to 59 are conceptual diagrams illustrating a case in which scheduling for a plurality of TRPs is performed according to an embodiment of the present invention.

If the priority index for the PUSCH allocated to the UE is given through DCI or RRC signaling, this may be interpreted as a priority of traffic. If the priority index is not given, it may be interpreted that the priority of the corresponding traffic is low. The UE may receive the PDCCH and perform preparation work (procedure of decoding DCI and encoding TB) for transmitting the PUSCH using a predetermined time.

Prior to transmitting two PUSCHs, the UE may check whether time resources of the PUSCHs overlap each other. If the PUSCHs overlap each other in time, the UE may select and transmit only one PUSCH. Here, it is assumed that the PDCCH is received early enough, so that the processing time is sufficiently secured for the UE.

(Method I.1-1): The UE may select and transmit a PUSCH having the highest priority among PUSCHs, and may not transmit an unselected PUSCH.

When the PUSCHs have the same priority, a time point at which a DCI corresponding to each PUSCH is received or a symbol of each PUSCH may be used as a criterion for selecting a PUSCH. The time at which the DCI is received is further divided, and may be the time of the DCI received earlier or the time of the DCI received later.

(Method I.1-2): For PUSCH(s) allocated through different scheduling DCIs, the UE may select and transmit a PUSCH corresponding to the scheduling DCI received from CORESET having an earlier first symbol.

When several CORESET pools are configured, (Method I.1-2) can be performed based on only the first symbols of CORESETs regardless of CORESET pools. If scheduling DCIs are detected in CORESETs that belong to different CORESET pools and start from the same first symbol, PUSCH indicated by scheduling DCI included in CORESETs belonging to CORESET pool indicated in higher layer signaling or technical standard You can choose. According to (Method I.1-2), the UE may not be disturbed by the subsequently received scheduling DCI while performing preparation work for transmitting the PUSCH in the order in which the scheduling DCI is received. Therefore, there is an advantage of easy implementation.

(Method I.1-3): For PUSCH(s) allocated through different scheduling DCIs, the UE may select and transmit a PUSCH corresponding to the scheduling DCI received from CORESET having a later last symbol.

Meanwhile, when there are several scheduling DCIs, the UE may select a PUSCH based on the first symbols in which PUSCHs are transmitted. That the UE can receive scheduling DCIs from multiple TRPs means that the UE has the ability to receive or transmit multiple TBs. In this case, there is no need to select a PUSCH only in the order in which DCIs are received. Therefore, it is preferable that methods other than (Method I.1-2) and (Method I.1-3) are applied.

(Method I.1-4): The UE may select a PUSCH having priority over the first symbol.

The UE may decode DCI from several CORESETs (and/or CORESET pools) and compare time resources of PUSCH. When the PUSCHs have the same priority, the UE may select a PUSCH indicated to be transmitted earlier. In this case, the UE may first prepare to transmit the PUSCH according to the received scheduling DCI, and then cancel the transmission of the PUSCH prepared by the received scheduling DCI.

The proposed methods are described with reference to FIGS. 57 , 58 , and 59 .

Referring to FIG. 57, although scheduling DCIs are respectively received from two CORESET pools, the first symbols of PUSCHs allocated by the scheduling DCIs have an order different from the order of the scheduling DCIs. According to (Method I.1-4), scheduling in which the reception order of scheduling DCIs and the transmission order of PUSCHs are reversed may be allowed. Referring to FIG. 58, scheduling DCIs are respectively received in two CORESET pools, and time resources of PUSCHs partially overlap. In this case, the UE selects and transmits a PUSCH allocated to be transmitted first, and does not transmit another PUSCH. In FIG. 58, since the reception order of DCIs and the transmission order of PUSCHs are the same, (Method I.1-2) may be applied. However, if the reception order of DCIs and the transmission order of PUSCHs are different, (Method I.1-4) may be applied when the time resources of the PUSCHs partially overlap (FIG. 59).

J. How to support GC-PDCCH in multiple TRP

(1) How a plurality of TRPs support GC-PDCCH

The group-common (GC) PDCCH includes information transmitted to a plurality of terminals. For example, in the case of an NR system, DCI 20 indicates SFI or COT, DCI 21 indicates DLPI, DCI 22 indicates TPC PUSCH/PUCCH, DCI 23 indicates TPC SRS, DCI 24 indicates ULCI may be indicated. In the GC-DCI included in the GC PDCCH, information on multiple terminals or multiple serving cells is composed of one information bits and undergoes a common encoding procedure. Accordingly, information useful to a specific terminal corresponds to a part of information bits, and the information at which position among the information bits is useful is indicated to the terminal by RRC signaling.

In a scenario where multiple TRPs are used, there may be delays in communication over the backhaul. When the UE receives the GC-DCI from the CORESET belonging to any one TRP, it may urgently instruct the UE to transmit/receive for another TRP for which the GC-DCI is not received, or an appropriate delay time may be allowed. . For example, when URLLC traffic needs to be transmitted, there may be information urgently needing cooperation for ULCI or DLPI. For example, in the case of TPC PUSCH/PUCCH/SRS, a TPC command determined by TRPs cooperating relatively slowly may be included in GC-DCI.

(Method J.1-1): GC-DCI can be set in only one CORESET pool.

One CORESET pool may be fixedly indicated in the technical standard, or one CORESET pool may be indicated by RRC signaling. In one CORESET pool, Type 3 PDCCH CSS may be set to the UE by RRC signaling. In this case, the UE may not receive GC-DCIs having conflicting information from TRPs. However, it is preferable that some GC-DCI can be transmitted per TRP.

(Method J.1-2): GC-DCI can be set for each CORESET pool.

For each CORESET pool, Type 3 PDCCH CSS may be set to the UE by RRC signaling.

The GC-DCI transmitted in the GC-PDCCH may include information on only one TRP. Alternatively, it may be allowed that the GC-DCI transmitted on the GC-PDCCH includes information on two or more TRPs.

(Method J.1-3): The UE may read information from only one location for one serving cell in GC-DCI.

GC-DCI may include information on only one TRP, or even if it does not include information on TRP, the UE may be informed of which TRP information it is. The UE may obtain information on only one TRP (or CORESET pool) at one location for the payload of GC-DCI.

Although one or more CORESET pool(s) are set for the UE, it may be interpreted that only information on TRP corresponding thereto is mapped to CORESETs belonging to each CORESET pool. Alternatively, if the CORESET pool is not configured, the UE may not distinguish between TRPs. Alternatively, the UE may use one CORESET pool in a fixed manner. Therefore, the UE must search for CORESET(s) belonging to other CORESET pool(s) in order to receive GC-DCI.

Considering the PDSCH/PUSCH/PUCCH/SRS to which GC-DCI is applied, the TRP (or CORESET and/or CORESET pool including GC-DCI) transmitting the GC-DCI and PDSCH/PUSCH/PUCCH/SRS terminal The TRP transmitted and received can always be the same. Alternatively, the UE may apply GC-DCI to PDSCH/PUSCH/PUCCH/SRS for any TRP regardless of CORESET and/or CORESET pool including GC-DCI.

(Method J.1-4): The UE may read information from two or more locations for one serving cell in GC-DCI.

GC-DCI may include information on two or more TRPs. The UE may receive information on two or more locations in GC-DCI through RRC signaling. According to (Method J.1-4), the terminal may be instructed on the starting point at which information for each TRP is located.

60 is a conceptual diagram illustrating a configuration example of information bits of GC-DCI according to an embodiment of the present invention.

Referring to FIG. 60 , the UE may be instructed by RRC signaling at a starting point at which information on each of TRP i and TRP j is located. In one example, the UE may be additionally instructed such a starting point as a separate RRC parameter.

(2) Interpretation method of ULCI (and/or DLPI)

The CORESET pool may be indicated by RRC signaling so that the UE supports several TRPs (eg, two TRPs). The methods described below may be equally applied to DLPI as well as ULCI, but for convenience of description, the methods described below are described as being applied to ULCI.

According to (Method J.1-3), the UE may receive a separate GC-PDCCH for each TRP (or CORESET pool). One starting point is applied to the GC-PDCCH, so that the ULCI can be delivered to the UE. The UE may receive the GC-PDCCH from each of the two CORESET pools to know each ULCI.

According to (Method J.1-4), the bitmap included in the ULCI may be expressed differently for each TRP, but may be included in one GC-PDCCH (ie, one CORESET pool). The UE may acquire ULCI for each TRP from two or more locations of a given GC-DCI by using a bitmap.

).In one example, the bitmap included in the ULCI may be applied to PDSCH/PUSCH/SRS scheduled by CORESET belonging to each CORESET pool. Therefore, the UE may not apply GC-DCI i received from CORESET pool i to PDSCH/PUSCH/SRS allocated by scheduling DCI j received from CORESET pool j (

).

In one example, the bitmap included in the ULCI may be applied to PDSCH/PUSCH/SRS regardless of which CORESET pool is received. Therefore, when the unit UL resource is expressed as 1 in the bitmaps of ULCI, the UE transmits PDSCH/PUSCH/SRS in the corresponding unit UL resource regardless of the CORESET pool including the ULCI and the CORESET pool including the scheduling DCI. may not transmit.

The UE may receive opposite ULCIs for the same unit UL resource. In this case, if the corresponding unit UL resource is expressed as 1 in any one ULCI, the UE may not transmit PDSCH/PUSCH/SRS in the corresponding unit UL resource.

(3) TPC analysis method

). 이들이 동일한 슬롯에서 수신되는 경우, 단말은 TPC command들을 단순히 누적하지 않아야 한다.The CORESET pool may be indicated by RRC signaling so that the UE can support multiple TRPs. When TPC PUSCH / PUCCH / SRS is indicated to the UE, when it is difficult for TRPs to dynamically cooperate, different TPC commands for the same PUSCH (or PUCCH or SRS) through GC-PDCCHs belonging to different CORESET pools may be instructed to the terminal. For example, for one PUSCH/PUCCH/SRS, GC-DCI i received by the UE from CORESET pool i increases transmission power, and GC-DCI j received by the UE from CORESET pool j decreases transmission power. can do (

). If they are received in the same slot, the UE should not simply accumulate TPC commands.

According to (Method J.1-1), the UE can receive the TPC command from only one CORESET pool. When (Method J.1-4) is additionally applied, each predetermined position of the received GC-DCI may mean each TRP. The terminal independently accumulates the TPC commands received at a predetermined location, and can be applied when the terminal transmits it to each TRP.

According to (Method J.1-2), the UE may receive a TPC command for each CORESET pool. The UE considers that the CORESET pool and TRP correspond to 1-1, so it can be applied when accumulating TPC commands for each CORESET pool independently and transmitting them to each TRP.

K. How ULCI Can Apply

(1) How to support ULCI in licensed bands

DCI 24 (DCI format 2_4) may include ULCI information for several serving cells and SUL carriers. The ULCI required for the UE is received at a specific location of GC-DCI, and the specific location is indicated to the UE by RRC signaling.

61 is a conceptual diagram illustrating a configuration example of ULCI according to an embodiment of the present invention.

Referring to FIG. 61 , the reference uplink resource is divided into 4 time groups and 4 frequency groups, but is not limited thereto. One time group may be composed of several consecutive symbols, and one frequency group may be composed of several consecutive PRBs. One unit UL resource consists of one time group and one frequency group. In FIG. 61 , information for canceling PUSCH transmission in two unit UL resources may be expressed as a bit stream.

The reference UL resource consists of time and frequency resources, and is indicated to the UE by RRC signaling. The reference UL resource is divided into several unit UL resources, and one unit UL resource corresponds to one bit on the bitmap. That is, one unit UL resource corresponds to 0 or 1 on the bitmap. For a unit UL resource belonging to a resource for transmitting a PUSCH/SRS, when a corresponding bit is 1, the UE may cancel transmission of the corresponding PUSCH/SRS. In the case of a PUSCH, transmission of the entire PUSCH (or a corresponding PUSCH instance in the case of repeated transmission) may be canceled. In the case of SRS, only SRS transmission in SRS symbol(s) overlapping with a unit UL resource may be canceled.

In a scenario supporting URLLC traffic and eMBB traffic, a reference UL resource and a unit UL resource may be utilized to suppress transmission of eMBB traffic in order to reduce interference to URLLC traffic.

The ULCI (or GC-DCI associated therewith) may be periodically transmitted to the UE. However, the UE may not necessarily periodically observe the ULCI. It is preferable that the UE observes ULCI only when transmitting PUSCH (eg, CG PUSCH or DG PUSCH by UL grant). At this time, if the UE detects that the bit for the unit UL resource corresponding to the CG PUSCH is set to 1 in any one GC-DCI before transmitting the CG PUSCH, the PUSCH may not be transmitted in the unit UL resource. .

(2) How to support ULCI in unlicensed bands

In the unlicensed band, the frequency resource of the PUSCH may be expressed differently. In order to properly distribute transmit power while complying with frequency regulation, the PUSCH may occupy PRBs in the form of interlaces (Type 2, or T2 FDRA). Accordingly, if the PUSCH includes URLLC traffic, bits corresponding to all frequency groups in ULCI may be set to 1. According to this, a PUSCH to transmit eMBB traffic cannot be transmitted. In order to express resources of PUSCH allocated to T2 FDRA, it is necessary to improve a method of expressing reference UL resources in ULCI.

(Method K.2-1): The frequency band of the reference UL resource may be expressed as interlace(s).

The number of interlaces may vary according to the subcarrier spacing. For example, in the case of a 15 kHz subcarrier interval, a bitmap having a length of 6 bits may be used. In the case of a 30 kHz subcarrier spacing, a bitmap with a length of 5 bits may be used.

(Method K.2-2): In (Method K.2-1), an RB set (or LBT subband) may also be further expressed.

The active BWP may consist of one or more RB set(s) (or LBT subband(s)), and the frequency resource of the PUSCH from the base station may be indicated by a combination of the RB set and the interlace. Similarly, since the reference UL resource may include one or more RB set(s), the frequency band of the reference UL resource may also represent the RB set.

The index of the RB set is indicated to the UE by RRC signaling. The UE may check which RB set is a frequency resource from among the already indicated RB set(s) by using ULCI. The index of the RB set may be indicated separately from DCI 20. Alternatively, the RB set indicated in DCI 20 may be reused and utilized in ULCI.

62 is a conceptual diagram illustrating another configuration example of ULCI according to an embodiment of the present invention.

62 shows an example in which (Method K.2-1) and/or (Method K.2-2) is applied. In FIG. 62 , the reference UL resource is divided into four time groups in the time domain and one RB set and five frequency groups in the frequency domain, but is not limited thereto. One time group may consist of several consecutive symbols, and one frequency group may consist of one or more interlace(s). One unit UL resource consists of one time group and one frequency group. In FIG. 62, one frequency group is represented by one interlace. In FIG. 62 , information for canceling transmission of PUSCH in two unit UL resources may be expressed as a bit string.

(Method K.2-3): One method of interpreting the reference UL resource by RRC signaling may be indicated to the UE.

When the indication value of the RRC signaling is set to a specific value, the frequency of the reference UL resource may be interpreted as consecutive PRBs (RBG scheme). When the indication value of the RRC signaling is set to a specific value, the frequency of the reference UL resource may be interpreted as interlace(s) (interlace scheme).

(Method K.2-4): In (Method K.2-3), even when the UE receives only T2 FDRA as RRC signaling, the UE can observe the reference UL resource according to both interpretation methods.

The UE may receive ULCIs at two locations belonging to the same GC-DCI. According to (Method K.2-4), interpretation methods for ULCIs may be different. It is possible to observe a bitmap given in an RBG scheme in ULCI and a bitmap given in an interlace scheme in ULCI. If it is indicated not to transmit the PUSCH in any one ULCI (ie, if the unit UL resource indicated by 1 overlaps with the allocated frequency resource of the PUSCH), the UE may not transmit the PUSCH.

(3) How to determine uplink transmission power

63 is a conceptual diagram for explaining the relationship between PUSCH transmission of a UE and ULCI according to an embodiment of the present invention.

Referring to FIG. 63 , when a UE is allocated a PUSCH through UL-DCI or higher layer signaling, a PUSCH preparation time Δ _preparation must be secured. The UE may cancel PUSCH transmission in the time and frequency resources indicated by the ULCI, and in this case, PUSCH cancellation time Δ _cancel must be secured. If Δ _preparation is not secured, the UE may transmit the PUSCH as it is. In general, Δ _preparation ≥ _{Δ cancel} can be assumed.

In the case of uplink carrier aggregation or when one serving cell has two or more uplink carriers, the UE may be instructed to transmit two or more PUSCHs at the same time. Here, the UE may be allocated PUSCHs through UL-DCI or higher layer signaling. When the search space set for receiving the ULCI is configured for the UE, the region of the time/frequency resource indicated by the ULCI may partially overlap with one or more PUSCH(s). In this case, the UE may be instructed by higher layer signaling to not transmit the PUSCH or to cancel the PUSCH during transmission when it overlaps with the resource indicated by the ULCI.

64 is a conceptual diagram for explaining an operation according to ULCI when two or more PUSCHs are allocated to a UE according to an embodiment of the present invention.

Referring to FIG. 64 , two or more UL-DCIs may allocate PUSCHs to the UE so that at least some overlap in time on different uplink carriers. For example, a case in which two PUSCHs overlap is illustrated in FIG. 62 . However, the following descriptions may be equally extended and applied even when three or more PUSCHs overlap.

를 할당하고, PUSCH 2에 대해 전력

를 할당할 수 있다(

). PUSCH 1 및 PUSCH 2가 각각 서로 다른 시간들에서 전송될 때에는 단말이 PUSCH 1과 PUSCH 2에 각각 전력

및 전력

를 할당하는 것으로 가정될 수 있다. 단말에게 PUSCH들을 동시에 전송하면서 동적으로 전력을 공유하도록 지시된 경우에는, PUSCH들 각각에게 보다 작은 전력이 할당될 수 있다(즉,

). PUSCH 1에 더욱 높은 우선순위를 두는 경우에는 전력

이 PUSCH 1에 할당될 수 있고, PUSCH 2에는 나머지 전력이 할당될 수 있다(

). 반대의 경우, PUSCH 2 및 PUSCH 1에 각각

가 할당될 수 있다.The UE powers for PUSCH 1

Allocate and power for PUSCH 2

can be assigned (

). When PUSCH 1 and PUSCH 2 are transmitted at different times, the UE supplies power to PUSCH 1 and PUSCH 2, respectively.

and power

It can be assumed to allocate . When the UE is instructed to dynamically share power while simultaneously transmitting PUSCHs, a smaller power may be allocated to each of the PUSCHs (that is,

). If PUSCH 1 is given a higher priority, the power

This may be allocated to PUSCH 1, and the remaining power may be allocated to PUSCH 2 (

). In the opposite case, PUSCH 2 and PUSCH 1 respectively

can be assigned.

In the case of FIG. 64, if ULCI is reflected, PUSCH 2 may be transmitted, but PUSCH 1 may be canceled or only some symbol(s) of PUSCH 1 may be transmitted. When the UE cancels PUSCH 1, since the power that can be allocated to PUSCH 2 increases, the UE may consider the power for PUSCH 2 again.

). PUSCH 2가 CG PUSCH인 경우, 단말은 TPC-GC-DCI를 수신해서 PUSCH 2의 전력을 계산할 수 있다.The UE may change the power of PUSCH 2 to a different value, but a separate processing time may be required for this. In this case, the UE may maintain the power of PUSCH 2 as it is (that is,

). When PUSCH 2 is a CG PUSCH, the UE may receive TPC-GC-DCI and calculate the power of PUSCH 2.

(Method K.3-1): The UE does not use ULCI to determine the power of PUSCH 2.

가 할당될 수 있다. If a separate processing time is not required for the UE or if the ULCI is received early enough, the UE may readjust the power of PUSCH 2. Since only the power of the PUSCH is adjusted while maintaining the UCI or TB mapped to the PUSCH, a special processing time may not be required for the UE. In this case, the step of determining at least the power of PUSCH 2 is performed after applying ULCI to PUSCH 1, and the power to PUSCH 2

can be assigned.

(Method K.3-2): The power of PUSCH 2 may be recalculated based on PUSCH(s) actually transmitted after applying ULCI.

In addition, a separate processing time for allocating power may be defined in the specification.

로 정의되는 처리 시간)이 확보되지 않는 경우에는, (방법 K.3-2)를 따르더라도, 단말은 PUSCH 2의 전력을 재조절하지 않을 수 있다.(Method K.3-3): processing time sufficient for the terminal (eg,

If the processing time defined by ) is not secured, the UE may not readjust the power of PUSCH 2 even if (Method K.3-2) is followed.

과

은

의 함수로 주어질 수 있다.

은

에 대응되는 시간 및

에 대응되는 시간 중에서 큰 값으로 결정될 수 있다. 여기서,

는 BWP의 부반송파 간격에 따라서 기술 규격에서 결정될 수 있다.

는 단말의 처리 능력에 따라서 더욱 작은 값 또는 더욱 큰 값을 가질 수 있다.

은 PUSCH DM-RS의 형상으로 결정되며,

는 BWP의 변환(switching)에 필요한 시간으로 결정될 수 있다.

은

에 대응되는 시간 및

에 대응되는 시간 중에서 큰 값으로 결정될 수 있다. 여기서.

을 결정하기 위한

의 값은

을 결정하기 위한

의 값과는 다르게 결정될 수 있다. 즉, 이 경우,

는 ULCI가 수신된 BWP의 부반송파 간격, PUSCH가 전송/취소되는 BWP의 부반송파 간격, 및 RRC 시그널링으로 주어지는 값(들)의 함수로 결정될 수 있다.In more detail about sufficient processing time,

class

silver

can be given as a function of

silver

corresponding time and

It may be determined as a larger value among the times corresponding to . here,

may be determined in the technical standard according to the subcarrier spacing of the BWP.

may have a smaller value or a larger value according to the processing capability of the terminal.

is determined by the shape of the PUSCH DM-RS,

may be determined as the time required for BWP switching.

silver

corresponding time and

It may be determined as a larger value among the times corresponding to . here.

to determine

the value of

to determine

may be determined differently from the value of That is, in this case,

may be determined as a function of the subcarrier interval of the BWP in which the ULCI is received, the subcarrier interval of the BWP in which the PUSCH is transmitted/canceled, and the value(s) given by RRC signaling.

만큼 이른 시점에 단말에게 수신되어야 한다.When sufficient time is secured for the UE, the UE may receive and decode the ULCI, recognize that PUSCH 1 is canceled through this, and reflect the change in power according to the cancellation of PUSCH 1 to PUSCH 2. At this time, in order for the UE to transmit the CG PUSCH or the DG PUSCH, the time for generating the PUSCH must be considered, so that the ULCI is at least greater than the first symbol of the PUSCH.

It should be received by the terminal as early as possible.

(3.1) Embodiment 1: Dual connectivity

A method for considering ULCI when determining transmission power for uplink transmission transmitted to E-UTRA in a dual connectivity scenario is presented. When the UE intends to perform uplink transmissions in two or more serving cells, the UE may prepare for uplink transmissions by applying power control already instructed to the UE. Thereafter, any one uplink transmission may be canceled by ULCI. In this case, the power of the uplink transmission actually performed by the UE may be changed by cancellation of any one of the uplink transmissions or may be determined regardless of the reception of the ULCI (that is, the power determined without receiving the ULCI is maintained as it is) .

When the UE has the ability to dynamically share power and the UE performs uplink transmissions in a master cell group (MCG) and a secondary cell group (SCG), the UE transmits power for any one uplink transmission. It is possible to secure enough power for the other uplink transmission.

In the case of EN-DC, since the UE is instructed by higher layer signaling to use E-UTRA cells as MCG and NR cells as SCG, the UE transmits uplink to SCG in order to sufficiently secure the power of uplink transmission to MCG. may lower the power of , or may not perform uplink transmission to the SCG. In the case of NE-DC, since the UE is instructed by higher layer signaling to use NR cells as MCG and E-UTRA cells as SCG, the UE lowers the power of uplink transmission to MCG or performs uplink transmission to MCG. By not doing so, it is possible to sufficiently secure the power of uplink transmission to the SCG.

In the case of NR-DC, the base station uses higher layer signaling (eg, nrdc-PCmode-FR1 or nrdc-PCmode-FR2) to share static power with the UE (eg, semi-static-mode1 or semi-static-mode2) Alternatively, dynamic power sharing may be indicated. The UE may sufficiently secure the power of uplink transmission to the MCG, and may lower the power of the uplink transmission through the SCG or not perform the uplink transmission through the SCG.

로 정의되는 처리 시간)이 주어지지 않는 경우, (방법 K.3-2)이 적용되더라도, 단말은 SCG로의 상향링크 전송의 전력을 변경하지 않을 수 있다.When static power sharing is indicated, power control may be performed regardless of reception of ULCI in the UE. On the other hand, in the case where dynamic power sharing is indicated, power may be irrespective of ULCI according to (Method K.3-1). Accordingly, although the UE can further increase the transmission power of uplink transmission to the SCG, a low power may be allocated to the uplink transmission to the SCG. On the other hand, according to (Method K.3-2), the UE may further increase the transmission power of uplink transmission to the SCG by applying ULCI. In this case, the UE must perform a procedure for allocating power or determining power after receiving the ULCI. Sufficient processing time for the terminal (eg,

When the processing time defined by ) is not given, even if (Method K.3-2) is applied, the UE may not change the power of uplink transmission to the SCG.

(4) How to determine the power of SL transmission when performing SL transmission and UL transmission at the same time

The UE may simultaneously support sidelink (SL) and uplink. A resource pool may be (pre) configured for the UE. When the terminal is controlled by the base station, the base station may reset the resource pool to the terminal. There are two types of resource allocation methods supported by the resource pool. In the first mode (resource allocation mode 1), the terminal receives the SL-DCI from the base station, transmits the PSCCH and the PSSCH to the counterpart terminal based on the SL-DCI, and receives the PSFCH from the counterpart terminal, and the PUCCH ( or PUSCH). In the second mode (resource allocation mode 2), without the involvement of the base station, the terminal may measure interference in an adjacent area and perform sidelink transmission when the interference is less than the reference value.

When the terminal supports both sidelink and uplink, since the terminal is controlled by the base station, the base station sets the search space set(s) to the terminal so that the terminal receives SL-DCI and UL-DCI. Also, a case in which the base station is servicing eMBB traffic and URLLC traffic may be considered. If the UE supports both eMBB traffic and URLLC traffic, the priority threshold of sidelink transmission (ie, SL-SS, PSBCH, PSCCH, PSSCH, PSFCH) may be indicated to the UE by higher layer signaling. The priority of uplink transmission may be indicated by higher layer signaling or UL-DCI. The value of the priority included in the SL-DCI and/or PSCCH and/or SCI (sidelink control information) is compared with the threshold, and according to the comparison result, the traffic allocated by the SL-DCI and/or PSCCH is more important ( i.e. URLLC) or less important traffic (i.e. eMBB). The importance of such traffic is first applied to selection between sidelink transmission and sidelink reception, and then also applied to determining transmission priority with uplink transmission.

If multiple uplink transmissions or uplink receptions have occurred to the UE, the UE may select sidelink transmission(s) or sidelink reception(s) according to their priorities.

When the terminal does not have the ability to perform sidelink transmission or sidelink reception and uplink transmission at the same time, if the time resources of sidelink transmission or sidelink reception and uplink transmission overlap each other in some symbols, the terminal first By applying a rank, one of sidelink transmission or sidelink reception and uplink transmission can be selected. Since the base station transmits UL-DCI or SL-DCI to the terminal, the base station can know in advance the selection of the terminal. When the terminal can perform sidelink transmission and uplink transmission at the same time, the terminal may allocate sufficient transmission power to transmission having a higher priority, and may allocate the remaining transmission power to transmission having a lower priority.

A case in which a search space set for receiving ULCI is configured for the UE is considered.

65 is a conceptual diagram for explaining an operation according to ULCI when sidelink transmission and PUSCH are allocated to a UE according to an embodiment of the present invention.

When the ULCI is received, the UE may cancel the transmission of the PUSCH. When ULCI is not received, uplink transmission and sidelink transmission may occur simultaneously to the UE, and the UE may perform both uplink transmission and sidelink transmission by dynamically sharing power. On the other hand, if uplink transmission is canceled by ULCI, the UE may consider only sidelink transmission.

A case in which the terminal selects one of sidelink transmission and uplink transmission is considered. The UE may allocate sufficient power to a sidelink channel or an uplink channel having a higher priority by performing power control. If the sidelink transmission is selected, the power of the sidelink transmission can be determined regardless of the ULCI.

Meanwhile, even if the priority of uplink transmission is higher, the UE may perform sidelink transmission according to the application time of ULCI. For example, after ULCI is first applied and uplink transmission is canceled, the UE may consider sidelink transmission. In this case, the UE may allocate sufficient power in sidelink transmission. For example, before ULCI is received and/or applied, the UE compares the priorities of uplink and sidelink, and according to the comparison result, sidelink transmission is canceled and uplink transmission is performed (or prepared). After that, the UE may cancel the previously selected uplink transmission by applying ULCI. In this case, the terminal may not transmit anything as a result.

(Method K.4-1): ULCI is applied first, and selection between sidelink transmission and uplink transmission may be performed thereafter.

The UE may first determine whether uplink transmission is valid or invalid by using ULCI, and may perform sidelink transmission thereafter, so that the throughput is increased.

In order to perform sidelink transmission and uplink transmission, the UE must wait for a time from receiving and processing the ULCI. This means that the UE may not be able to prepare in advance for sidelink transmission or uplink transmission because it depends on the result of ULCI. In addition, when the terminal is not configured to receive ULCI, since sidelink transmission or uplink transmission can be prepared in advance, the implementation of the terminal may vary depending on whether ULCI is configured. Therefore, as a simpler method, ULCI may be applied after selection between sidelink transmission and uplink transmission.

(Method K.4-2): ULCI may be applied after selection between sidelink transmission and uplink transmission is performed.

A case in which the terminal simultaneously performs sidelink transmission and uplink transmission is considered. UEs may dynamically share power. Sidelink transmission and uplink transmission may be performed on different carriers. Hereinafter, one sidelink transmission and one uplink transmission are considered, but the following description will be extended and applied even when one or more sidelink transmission(s) and one or more uplink transmission(s) are simultaneously performed. can

을 할당하고, 사이드링크 전송에 대해 전력

을 할당할 수 있다(

). 상향링크 전송과 사이드링크 전송이 각각 서로 다른 시간들에서 전송될 때에는 단말이 상향링크 전송과 사이드링크 전송에 각각 전력

과 전력

를 할당되는 것으로 가정될 수 있다. 단말에게 상향링크 전송과 사이드링크 전송을 동시에 수행하면서 동적으로 전력을 공유하도록 지시된 경우에는, 상향링크 전송과 사이드링크 전송 각각에게 보다 작은 전력이 할당될 수 있다(즉,

). 상향링크 전송에 더욱 높은 우선순위를 두는 경우에는 전력

이 상향링크 전송에 할당될 수 있고, 사이드링크 전송에는 나머지 전력을 할당할 수 있다(

). 반대의 경우, 사이드링크 전송과 상향링크 전송에 각각

가 할당될 수 있다.The terminal has power for uplink transmission

, and power for sidelink transmission

can be assigned (

). When the uplink transmission and the sidelink transmission are transmitted at different times, the UE uses power for the uplink transmission and the sidelink transmission, respectively.

over power

may be assumed to be allocated. When the UE is instructed to dynamically share power while simultaneously performing uplink transmission and sidelink transmission, a smaller power may be allocated to each of uplink transmission and sidelink transmission (that is,

). If higher priority is given to uplink transmission, power

It may be allocated to this uplink transmission, and the remaining power may be allocated to the sidelink transmission (

). In the opposite case, for sidelink transmission and uplink transmission, respectively

can be assigned.

When the uplink transmission is set to be canceled according to the reception of the ULCI, the UE may consider the order of the time of preparing the simultaneous transmission of the sidelink transmission and the uplink transmission and the time of applying the ULCI. If ULCI is applied first, the UE may perform only sidelink transmission. However, if ULCI is applied later, the UE may prepare all or part of uplink transmission and sidelink transmission, and then may apply ULCI.

)도 결정할 수 있다. 전송 전력들은 ULCI가 적용된 이후에도 변경되지 않는다.(Method K.4-3): The terminal prepares for simultaneous transmission of uplink transmission and sidelink transmission, and transmit powers (

) can also be determined. Transmit powers do not change even after ULCI is applied.

)이 할당될 수 있다. 단말은 사이드링크 전송을 수행하기 위해서 ULCI에 의존하지 않기 때문에, SL-DCI, PSCCH, 또는 CG PSSCH의 스케줄링을 위한 상위계층 시그널링만으로 사이드링크 전송을 결정할 수 있다. 기지국은 단말이 ULCI를 수신하지 않도록 설정할 수 있으며, 단말이 (방법 K.4-3)을 따르면

결정하는 절차가 단말이 ULCI를 수신하지 않도록 설정된 경우의 절차와 동일할 수 있다.The UE uses UCI and SCI for uplink transmission and sidelink transmission. Alternatively, encoding of the TB may be performed, and transmission powers of uplink transmission and sidelink transmission may also be determined. The UE may then cancel uplink transmission by applying ULCI. In this case, if the terminal follows (Method K.4-3), power is required for sidelink transmission.

) can be assigned. Since the UE does not rely on ULCI to perform sidelink transmission, sidelink transmission may be determined only by higher layer signaling for scheduling of SL-DCI, PSCCH, or CG PSSCH. The base station may set the terminal not to receive ULCI, and if the terminal follows (Method K.4-3)

The determining procedure may be the same as the procedure when the UE is configured not to receive ULCI.

)은 (다시) 결정될 수 있다.(Method K.4-4): The UE prepares for simultaneous transmission of uplink transmission and sidelink transmission, and transmits powers (

) can be (again) determined.

로 결정할 수 있다.The UE uses UCI and SCI for uplink transmission and sidelink transmission. Alternatively, encoding of the TB may be performed, but transmission powers of uplink transmission and sidelink transmission may not be determined. Alternatively, even if the transmit powers are determined, the transmit powers may be changed after the transmit powers are set to temporary values and the ULCI is applied. When ULCI is applied and the UE cancels uplink transmission, the UE may perform only sidelink transmission. Therefore, the terminal can reduce the power of the sidelink transmission.

can be decided with

(5) Field of SL-DCI

The SL-DCI (eg, DCI format 3_0, format 3_1) may include information necessary for the UE to perform sidelink transmission and include the HARQ-ACK therefor in the PUCCH. The SC-DCI may include a PUCCH Resource Indicator (PRI). The base station may receive PUCCHs from several different terminals. Depending on the format of the PUCCHs, the PUCCHs may be received in the form of CDMA or OFDMA. Accordingly, the base station can adjust the PUCCH transmission power of the terminal using the scheduling DCI field (TPC PUCCH field). In this case, the TPC PUCCH field may have a size of 2 bits, and instructs the UE to increase (+1 dB, or +3 dB), maintain (0 dB), or decrease (-1 dB) the power level of the PUCCH. index can be included.

(Method K.4-5): A field for controlling transmission power of PUCCH may be additionally included in SL-DCI.

For the NR system, DCI format 3_0 for controlling the NR sidelink may include both a PRI field and a TPC PUCCH field. On the other hand, DCI format 3_1 for controlling the LTE sidelink does not include both the PRI field and the TPC PUCCH field for HARQ-ACK transmission and reception because it does not support unicast traffic.

(6) How to report power headroom

The power margin indicates the amount of power that the UE can further allocate in the uplink, and the UE may report the power margin to the base station. This may include both a periodic report, a report by an indication, or a trigger by expiration of a timer. The power margin may be derived from one or more carriers configured for the terminal, and may be included in the same PUSCH and received by the base station.

There are three types of reporting power margins. Type 1 refers to the difference between the estimated (or instructed) value of the power when the UL-SCH is transmitted for each activated serving cell and the maximum power that the UE can utilize. Type 2 means a difference between an estimated (or instructed) value of transmission power of the UL-SCH and PUCCH transmitted to the activated serving cell and the maximum power that the UE can utilize. For example, for a MAC entity other than NR (ie, E-UTRA MAC entity in case of EN-DC, NE-DC, NGEN-DC), it may be utilized in SpCell. Type 3 means the difference between the estimated (or instructed) value of the power when the SRS is transmitted for each activated serving cell and the maximum power that the UE can utilize.

When performing type 1 report, the power margin derived by the UE may be a carrier and/or BWP on which a PUSCH is not transmitted, or a carrier and/or a BWP on which a PUSCH is transmitted. If the power margin is derived for the carrier and/or the BWP on which the PUSCH is transmitted, it can be expressed that it is derived for the actual PUSCH. Here, the PUSCH from which the power margin is derived and the PUSCH including the power margin may be different from each other. If a power margin is derived for a carrier and/or BWP on which a PUSCH is not transmitted, it is assumed that a PUSCH conforming to the format determined in the technical standard is transmitted, and it can be expressed that the reference PUSCH is derived.

The ULCI may be received by the UE before or after a _{predetermined time (Δ preparation} ) from the start of PUSCH 2. When the ULCI is received before a predetermined time before the start of PUSCH 2, the UE may not only adjust the transmission power for PUSCH 2 but also process the TB. Accordingly, a power headroom report (PHR) may be additionally considered.

When the PUSCH is transmitted, the PHR may be a value obtained by quantizing the power margin for the actually transmitted PUSCH. Alternatively, when the PUSCH is not transmitted, the PHR may be a value obtained by quantizing the power margin for the reference PUSCH. When PUSCH 1 is canceled by ULCI, a case in which PUSCH 2 includes PHR and PHR is a quantized value of the actual power margin for PUSCH 1 may be considered.

66 is a conceptual diagram for explaining a PHR operation when two PUSCHs are allocated to a UE according to an embodiment of the present invention.

Referring to FIG. 66, although the PHR for PUSCH 1 is transmitted in PUSCH 2, PUSCH 1 may be canceled by ULCI. Although FIG. 66 illustrates a case in which PUSCHs are allocated by UL-DCIs, the following descriptions may be applied to both CG PUSCH and DG PUSCH.

UCI and TB of PUSCH 2 may be coded regardless of ULCI. The base station cannot confirm whether the terminal has successfully received the ULCI. In addition, even if the ULCI search space set is configured for the UE and the UE receives the ULCI, the UE may not reflect the received ULCI in the encoding process of UCI and TB of PUSCH 2 . This means that the PHR is generated by the assumption that PUSCH 1 is transmitted.

(Method K.5-1): The UE generates a PHR based on the assumption that no PUSCH is dropped regardless of the reception of the ULCI.

Meanwhile, if the transmission of PUSCH 1 is canceled by ULCI, the PHR may no longer be based on whether PUSCH 1 is actually transmitted. If the ULCI is received by the UE at a sufficiently early point in time, the UE may know that the transmission of PUSCH 1 is canceled by applying the ULCI, which may affect the process of generating the UCI and TB of PUSCH 2. Therefore, the PHR may be generated based on the reference PUSCH by reflecting the transmission of PUSCH 1 being canceled, and the PHR may be included in the TB belonging to PUSCH 2.

(Method K.5-2): The UE generates a PHR based on the actual PUSCH or the reference PUSCH according to the reception of the ULCI.

로 정의되는 시간) 없이 단말에게 수신될 수 있다. 이러한 경우, (방법 K.5-2)가 적용되면, PUSCH 2에 포함되는 TB에 ULCI가 적용되지 않은 PHR이 포함될 수 있다. Sufficient time for ULCI to be applied (e.g.,

It can be received by the terminal without a time defined as . In this case, if (Method K.5-2) is applied, the TB included in PUSCH 2 may include a PHR to which ULCI is not applied.

과

은

의 함수로 주어질 수 있다.

은,

에 대응되는 시간 및

에 대응되는 시간 중에서 큰 값으로 결정될 수 있다. 여기서,

는 BWP의 부반송파 간격에 따라서 기술 규격에서 결정될 수 있다.

는 단말의 처리능력에 따라서 더욱 작은 값 또는 더욱 큰 값을 가질 수 있다.

은 PUSCH DM-RS의 형상으로 결정되며,

는 BWP의 변환(switching) 때 필요한 시간으로 결정될 수 있다.

은

에 대응되는 시간 및

에 대응되는 시간 중에서 큰 값으로 결정될 수 있다. 여기서.

을 결정하기 위한

의 값은

을 결정하기 위한

의 값과는 다르게 결정될 수 있다. 즉, 이 경우,

는 ULCI가 수신된 BWP의 부반송파 간격, PUSCH가 전송/취소되는 BWP의 부반송파 간격, 및 RRC 시그널링으로 주어지는 값(들)의 함수로 결정될 수 있다.In more detail about sufficient processing time,

class

silver

can be given as a function of

silver,

corresponding time and

It may be determined as a larger value among the times corresponding to . here,

may be determined in the technical standard according to the subcarrier spacing of the BWP.

may have a smaller value or a larger value depending on the processing capability of the terminal.

is determined by the shape of the PUSCH DM-RS,

may be determined as the time required for BWP switching.

silver

corresponding time and

It may be determined as a larger value among the times corresponding to . here.

to determine

the value of

to determine

may be determined differently from the value of That is, in this case,

may be determined as a function of the subcarrier interval of the BWP in which the ULCI is received, the subcarrier interval of the BWP in which the PUSCH is transmitted/canceled, and the value(s) given by RRC signaling.

만큼 이른 시점에 단말에게 수신되어야 한다.When sufficient time is secured for the UE, the UE may receive and decode the ULCI, recognize that PUSCH 1 is canceled through this, and reflect the change in power according to the cancellation of PUSCH 1 to PUSCH 2. At this time, in order for the UE to transmit the CG PUSCH or the DG PUSCH, the time for generating the PUSCH must be considered, so that the ULCI is at least greater than the first symbol of the PUSCH.

It should be received by the terminal as early as possible.

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

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

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

Claims (20)

As an uplink transmission method performed in a terminal,
Receiving at least one piece of downlink control information (DCI) for allocating a first uplink transmission and a second uplink transmission from a base station;
performing a first listen before talk (LBT) procedure for the first uplink transmission and, if the first LBT procedure is successful, performing the first uplink transmission; and
If the second LBT procedure is successful by performing a second LBT procedure for the second uplink transmission, performing the second uplink transmission;
The first uplink transmission and the second uplink transmission are successively performed with a time interval longer than a predetermined time,
Uplink transmission method. The method according to claim 1,
The at least one DCI is one DCI for allocating the first uplink transmission and the second uplink transmission, or DCIs for allocating the first uplink transmission and the second uplink transmission, respectively.
Uplink transmission method. The method according to claim 1,
The at least one DCI indicates the manner of the first LBT procedure,
Uplink transmission method. The method according to claim 1,
The first uplink transmission is transmission of PUSCH or PUCCH, and the second uplink transmission is transmission of SRS,
Uplink transmission method. 5. The method according to claim 4,
When the second uplink transmission exists within a channel occupancy time (COT) secured by the base station, the second LBT procedure is performed in a Type 2 channel access scheme, and the second uplink transmission is performed by the base station When present outside the secured COT, the second LBT procedure is performed in a Type 1 channel access method,
Uplink transmission method. 5. The method according to claim 4,
The second LBT procedure is performed in a Type 1 channel access scheme,
Uplink transmission method. 5. The method according to claim 4,
The second LBT procedure is performed only for the first symbol of the resource for transmitting the SRS,
Uplink transmission method. As an uplink transmission method performed in a terminal,
Receiving at least one piece of downlink control information (DCI) for allocating a first uplink transmission and a second uplink transmission from a base station;
not performing the first uplink transmission when the first LBT procedure fails by performing a first listen before talk (LBT) procedure for the first uplink transmission; and
If the second LBT procedure is successful by performing the second LBT procedure for the second uplink transmission, the second uplink transmission is performed, and if the second LBT procedure fails, the second uplink transmission is not performed. including steps that do not
The first uplink transmission and the second uplink transmission are successively performed with a time interval shorter than a predetermined time,
Uplink transmission method. 9. The method of claim 8,
The at least one DCI is one DCI for allocating the first uplink transmission and the second uplink transmission, or DCIs for allocating the first uplink transmission and the second uplink transmission, respectively.
Uplink transmission method. 9. The method of claim 8,
The at least one DCI indicates the manner of the first LBT procedure,
Uplink transmission method. 9. The method of claim 8,
The first uplink transmission is transmission of PUSCH or PUCCH, and the second uplink transmission is transmission of SRS,
Uplink transmission method. 12. The method of claim 11,
The second LBT procedure is performed in a Type 1, Type 2, Type 2A, Type 2B, or Type 2C channel access scheme,
Uplink transmission method. 13. The method of claim 12,
The second LBT procedure is performed only for the first symbol of the resource for transmitting the SRS,
Uplink transmission method. 14. The method of claim 13,
If the second LBT procedure fails, the entire SRS is not transmitted,
Uplink transmission method. As an uplink transmission method performed in a terminal,
Receiving at least one piece of downlink control information (DCI) for allocating a first uplink transmission and a second uplink transmission from a base station;
According to the method of the first LBT procedure indicated by the at least one DCI, if the first LBT procedure is successful by performing a first LBT (listen before talk) procedure for the first uplink transmission, the first uplink performing the transmission;
determining whether the second uplink transmission exists within a channel occupancy time (COT) secured by the base station; and
Performing a second LBT procedure in a different channel access method depending on whether the second uplink transmission exists within the COT secured by the base station and performing the second uplink transmission if the second LBT procedure is successful including,
The first uplink transmission and the second uplink transmission are successively performed with a time interval longer than a predetermined time,
Uplink transmission method. 16. The method of claim 15,
The method of the first LBT procedure is a Type 1 channel access method or a Type 2/2A/2B/2C channel access method,
Uplink transmission method. 16. The method of claim 15,
The at least one DCI includes information on whether a cyclic prefix (CP) extension is applied to the first uplink transmission, information on a length value of the CP extension, and/or a channel access priority class. containing additional information about
Uplink transmission method. 16. The method of claim 15,
The at least one DCI does not indicate the method of the LBT procedure for the second uplink transmission,
Uplink transmission method. 16. The method of claim 15,
CP extension is not applied to the second uplink transmission,
Uplink transmission method. 16. The method of claim 15,
When the second uplink transmission exists within the COT (channel occupancy time) secured by the base station, the second LBT procedure is performed in a Type 2/2A channel access scheme, and the second uplink transmission is secured by the base station. When present outside the COT, the second LBT procedure is performed in a Type 1 channel access method,
Uplink transmission method.

Images