KR20220015937A - Method and apparatus for transmitting data based on sensing in communication system - Google Patents

Abstract

Disclosed are a transmission method of data based on sensing of a communication system and a device thereof. An operating method of a terminal comprises the following steps of: receiving one or more data units from a base station; generating an HARQ codebook for at least one data unit of the one or more data units at a reference time; and transmitting the HARQ codebook to the base station.

Description

Method and apparatus for transmitting data based on sensing in a communication system

The present invention relates to data technology in a communication system, and more particularly, to a technology for transmitting data based on sensing.

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

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

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

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

An object of the present invention for solving the above problems is to provide a method and an apparatus for transmitting data based on sensing in a communication system.

In order to achieve the above object, there is provided a method of operating a terminal according to a first embodiment of the present invention, comprising: receiving one or more data units from a base station; HARQ for at least one data unit among the one or more data units at a reference time generating a codebook, and transmitting the HARQ codebook to the base station, wherein the reference time is shared between the terminal and the base station.

The method of operating the terminal may further include receiving a DCI triggering transmission of the HARQ codebook from the base station.

The reference time may be implicitly indicated by information included in the DCI.

The reference time may be set based on a channel through which the HARQ codebook is transmitted.

The one or more data units may be received on a resource according to one or more aggregated carriers or one or more SPSs.

The HARQ codebook is "HARQ-ACK for the at least one data unit received on the one or more aggregated carriers that are active at the reference time" or "Inactive with one or more aggregated carriers that are active at the reference time" HARQ-ACKs for data units received on one or more aggregated carriers.

The HARQ codebook is "HARQ-ACK for the at least one data unit received from a resource according to the one or more SPSs that are active at the reference time" or "One or more SPSs that are active at the reference time and an inactive state" HARQ-ACKs for data units received on resources according to one or more SPSs.

When the HARQ codebook includes a HARQ-ACK for the at least one data unit received on the one or more aggregated carriers in the active state at the reference time, the HARQ buffer for the one or more aggregated carriers in the inactive state is It may be empty at a preset point in time.

The preset time may be after transmission of the HARQ codebook.

When the HARQ codebook includes a HARQ-ACK for the at least one data unit received from a resource according to the one or more SPSs in the active state at the reference time, the HARQ buffer for the one or more SPSs in the inactive state is previously It can be empty at a set point in time.

When the HARQ-ACK for DCI indicating release of the SPS configuration is transmitted to the base station, the reference time may be set after a time required for the HARQ-ACK processing in the base station.

The method of operating a base station according to a second embodiment of the present invention for achieving the above object includes transmitting one or more data units to a terminal, and generating an HARQ codebook for at least one data unit among the one or more data units. Receiving from a terminal, estimating that the HARQ codebook is generated at a reference time, and interpreting the HARQ codebook based on the reference time, wherein the reference time is shared by the terminal and the base station .

The method of operating the base station may further include transmitting a DCI triggering transmission of the HARQ codebook to the terminal, and the DCI may include information indicating the reference time.

The one or more data units may be transmitted on a resource according to one or more aggregated carriers or one or more SPSs.

The HARQ codebook includes "HARQ-ACK for the at least one data unit received on the one or more aggregated carriers that are active at the reference time", "Inactive with one or more aggregated carriers that are active at the reference time" HARQ-ACKs for data units received on one or more aggregated carriers that are in the state", "HARQ-ACKs for the at least one data unit received in a resource according to one or more SPSs that are active at the reference time- ACK”, or “HARQ-ACKs for data units received in resources according to one or more SPSs in an active state and one or more SPSs in an inactive state at the reference time”.

The method of operating the base station may further include transmitting a DCI indicating release of SPS configuration to the terminal and receiving an HARQ-ACK for the DCI from the terminal, wherein the reference time is the base station It may be set after the time required for the processing of the HARQ-ACK in .

A terminal according to a third embodiment of the present invention for achieving the above object includes a processor, a memory in electronic communication with the processor, and instructions stored in the memory, and when the instructions are executed by the processor, The instructions are that the terminal receives one or more data units from a base station, generates a HARQ codebook for at least one data unit of the one or more data units at a reference time, and transmits the HARQ codebook to the base station and the reference time is shared by the terminal and the base station.

The instructions may be operable to further cause reception of a DCI triggering transmission of the HARQ codebook from the base station, and the DCI may include information indicating the reference time.

When the HARQ codebook includes a HARQ-ACK for the at least one data unit received on the one or more aggregated carriers in the active state at the reference time, the HARQ buffer for the one or more aggregated carriers in the inactive state is It may be empty at a preset point in time.

When the HARQ-ACK for DCI indicating release of the SPS configuration is transmitted to the base station, the reference time may be after a time required for the HARQ-ACK processing in the base station.

According to embodiments, when carrier aggregation (CA) or semi-persistent scheduling (SPS) is configured, the terminal may generate a hybrid automatic repeat request (HARQ) codebook for one or more data units at a reference time, and HARQ The codebook may be transmitted to the base station. Since the reference time is interpreted the same in the terminal and the base station, the interpretation of the HARQ codebook in the base station may be the same as the interpretation of the HARQ codebook in the terminal. 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 is a conceptual diagram illustrating a first embodiment of a method for monitoring a search space aggregation group based on an omni-directional sensing procedure.
4 is a conceptual diagram illustrating a first embodiment of a method for monitoring a search space aggregation group based on a directional sensing procedure.
5 is a conceptual diagram illustrating a second embodiment of a method for monitoring a search space aggregation group based on a directional sensing procedure.
6 is a conceptual diagram illustrating a first embodiment of SPS PDSCH configuration.
7 is a conceptual diagram illustrating a first embodiment of CG PDSCH configuration.
8A is a conceptual diagram illustrating a first embodiment of an SPS PDSCH occasion.
8B is a conceptual diagram illustrating a second embodiment of an SPS PDSCH occasion.
9A is a conceptual diagram illustrating a first embodiment of a method for setting a time resource of an SPS PUCCH.
9B is a conceptual diagram illustrating a second embodiment of a method for setting a time resource of an SPS PUCCH.
10A is a conceptual diagram illustrating a first embodiment of a method for transmitting HARQ-ACK in the last SPS PUCCH associated with the SPS PDSCH.
10B is a conceptual diagram illustrating a second embodiment of a method for transmitting HARQ-ACK in the last SPS PUCCH associated with the SPS PDSCH.
11A is a conceptual diagram illustrating a first embodiment of a method for transmitting HARQ-ACK in PUSCH.
11B is a conceptual diagram illustrating a second embodiment of a method for transmitting HARQ-ACK in PUSCH.
12 is a conceptual diagram illustrating a first embodiment of a temporal relationship to be considered for generating an (improved) Type-3 HARQ codebook.
13 is a conceptual diagram illustrating a reception time of a MAC CE for changing a state of a serving cell and a time taken to reflect the MAC CE.
14 is a conceptual diagram illustrating a reception operation of an activated DCI and a time at which the activated DCI is reflected.
15 is a conceptual diagram illustrating a reception operation of a release DCI and a time at which an activation DCI is reflected.
16 is a conceptual diagram illustrating a first embodiment of a method of changing a time resource (eg, feedback timing) of a PUCCH for an SPS PDSCH.
17 is a conceptual diagram illustrating a first embodiment of a method for changing a feedback timing of HARQ-ACK for an SPS PDSCH.
18A is a conceptual diagram illustrating a first embodiment of a method for transmitting a PUSCH occasion when PUSCH instances are consecutively arranged.
18B is a conceptual diagram illustrating a first embodiment of a method for transmitting a PUSCH occasion when PUSCH instances are arranged according to a preset interval.
19A is a conceptual diagram illustrating a first embodiment of a method for transmitting CG-UCI in all PUSCH instances belonging to a PUSCH occasion based on sensing when PUSCH instances are consecutively disposed.
19B is a conceptual diagram illustrating a first embodiment of a method of transmitting CG-UCI in all PUSCH instances belonging to a PUSCH occasion based on sensing when PUSCH instances are arranged according to a preset interval.
20A is a conceptual diagram illustrating a first embodiment of a method for transmitting CG-UCI in the first PUSCH instance that succeeds in LBT when PUSCH instances are consecutively deployed.
20B is a conceptual diagram illustrating a first embodiment of a method for transmitting CG-UCI in the first PUSCH instance that succeeds in LBT when PUSCH instances are arranged according to a preset interval.
21A is a conceptual diagram illustrating a first embodiment of a method for transmitting CG-UCI in one PUSCH instance for each COT/FFP when PUSCH instances are consecutively arranged.
21B is a conceptual diagram illustrating a first embodiment of a method for transmitting a CG-UCI in one PUSCH instance for each COT/FFP when PUSCH instances are arranged according to a preset interval.
22 is a conceptual diagram illustrating a first embodiment of a method of deferring HARQ-ACK transmission when repeated transmission of PUCCH is indicated in a TDD system.
23 is a conceptual diagram illustrating a first embodiment of a method for deferring HARQ-ACK transmission when repeated transmission of PUCCH is not indicated in a TDD system.
24 is a conceptual diagram illustrating a first embodiment of a method of changing a serving cell in which PUCCH is transmitted in TDD CA when repeated transmission of PUCCH is indicated.
25 is a conceptual diagram illustrating a second embodiment of a method of changing a serving cell in which PUCCH is transmitted in TDD CA when repeated transmission of PUCCH is indicated.
26 is a conceptual diagram illustrating a third embodiment of a method of changing a serving cell in which PUCCH is transmitted in TDD CA when repeated transmission of PUCCH is indicated.

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

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

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

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

Unless defined otherwise, all terms used herein, including technical 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 a commonly used dictionary should be interpreted as having a meaning consistent with the meaning in the context of the related art, and should not be interpreted in an ideal or excessively formal meaning unless explicitly defined in the present application. does not

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

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

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

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

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

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

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

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

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

Referring back to FIG. 1 , the communication system 100 includes a plurality of base stations 110 - 1 , 110 - 2 , 110 - 3 , 120 - 1 and 120 - 2 , and a plurality of terminals 130 - 1, 130-2, 130-3, 130-4, 130-5, 130-6). Each of the first base station 110-1, the second base station 110-2, and the third base station 110-3 may form a macro cell. Each of the fourth base station 120-1 and the fifth base station 120-2 may form a small cell. The fourth base station 120-1, the third terminal 130-3, and the fourth terminal 130-4 may belong to the cell coverage of the first base station 110-1. The second terminal 130-2, the fourth terminal 130-4, and the fifth terminal 130-5 may belong to the cell coverage of the second base station 110-2. The fifth base station 120-2, the fourth terminal 130-4, the fifth terminal 130-5, and the sixth terminal 130-6 may belong to the cell coverage of the third base station 110-3. 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, and 120-2 is a NodeB (NB), an evolved NodeB (eNB), gNB, an advanced base station (ABS), HR - BS (high reliability-base station), BTS (base transceiver station), radio base station (radio base station), radio transceiver (radio transceiver), access point (access point), access node (node), RAS (radio access station) ), MMR-BS (mobile multihop relay-base station), RS (relay station), ARS (advanced relay station), HR-RS (high reliability-relay station), HNB (home NodeB), HeNB (home eNodeB), It may be referred to as a road side unit (RSU), a radio remote head (RRH), a transmission point (TP), a transmission and reception point (TRP), and the like.

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

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

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

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

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

Chapter 1

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

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

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

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

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

Chapter 2 UL Channel Transmission Method

Section 2.1 Periodic Transmission Method of UL Channel Based on Omni-Directional Sensing Procedure

The UE may transmit a T1 (Type1) CG (configured grant) PUSCH or a T2 (Type2) CG PUSCH. The T1 CG PUSCH may be a data unit transmitted according to the T1 CG configuration, and the T2 CG PUSCH may be a data unit transmitted according to the T2 CG configuration. Information element(s) necessary for transmission of the T1 CG PUSCH may be indicated (eg, configured) to the UE through higher layer signaling only. Some information element(s) for transmission of T2 CG PUSCH may be indicated to the terminal by UL-DCI, and the remaining information element(s) for transmission of T2 CG PUSCH may be indicated to the terminal by higher layer signaling. have. A transmission beam used for transmission of the T1 CG PUSCH may be configured as higher layer signaling, and a transmission beam used for transmission of the T2 CG PUSCH may be activated and/or configured by the value of a field included in UL-DCI. can When the UL-DCI does not include a field for activating the T2 CG PUSCH transmission beam, the T2 CG PUSCH transmission beam may be configured as higher layer signaling. For example, a transmission beam applied to a PUCCH may also be applied to a CG PUSCH (eg, a PUSCH according to a CG configuration). Alternatively, the transmission beam (or spatial filter) associated with the reception beam (or transmission configuration indicator (TCI) state) of the CORESET having the lowest ID among control resource sets (CORESETs) configured in the serving cell may be applied to the CG PUSCH. have.

"When the transmit beam is associated with the receive beam and bidirectionality of the beam is established" means "the spatial filter used for the transmit beam and the spatial filter used for the receive beam are the same", "From the spatial filter used for the transmit beam It may mean "that a spatial filter used for a receive beam can be derived" or "that a spatial filter used for a transmit beam can be derived from a spatial filter used for a receive beam". "When the transmit beam is associated with the receive beam and the bidirectionality of the beam is not established" means that "the spatial filter used for the transmit beam and the spatial filter used for the receive beam have a one-to-one correspondence through the beam management procedure" can mean

One TCI state may be described in relation to one or more RSs. For example, the TCI state of the DL signal/channel may be defined as a quasi-colocation (QCL) relationship(s) or qcl-type between the corresponding DL signal/channel and one or more RSs. Each RS may have a different qcl-type. qcl-type can be divided into qcl-type1 and qcl-type2. qcl-type1 may have a value of qcl-typeA, qcl-typeB, or qcl-typeC, and qcl-type2 may have a value of qcl-typeD. For example, when a specific RS1 and/or RS2 is indicated in the TCI state in the PDSCH or PDCCH reception procedure, the UE assumes qcl-type1 for RS1 and qcl-type2 for RS2 to receive the PDSCH or PDCCH. have. qcl-typeA may mean sharing fine time and frequency synchronization, qcl-typeB may mean sharing fine frequency synchronization, and qcl-typeC may mean sharing coarse time and frequency synchronization. , and qcl-typeD may mean sharing a reception beam.

When operating in frequency range 1 (FR1), the TCI state may be indicated by one RS1, and the terminal may derive a parameter in a channel estimation process for receiving the RS1. When operating in frequency range 2 (FR2), the TCI state can be indicated by two RS1 and RS2, and the procedure for deriving parameters in the channel estimation process for RS1 reception is the same as the derivation procedure in FR1 , and the UE may additionally perform a procedure for deriving a beam for receiving RS2.

In the reception procedure from several base stations (or transmission and reception point (TRP)), the number of RSs constituting the TCI state may increase according to the number of TRPs.

In one example, the same TCI state may mean that both qcl-type1 and qcl-type2 are the same. In another example, the same TCI state may mean that only qcl-type2 is the same.

The UE may transmit the PUCCH to transmit the HARQ-ACK of a semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH). The SPS PDSCH may be a data unit transmitted according to the SPS configuration. According to the configuration of the base station, the resource of the PUCCH transmitted by the terminal may be determined. In this case, one spatial filter applied by the terminal may be determined according to the setting of the base station or the technical standard. For example, a transmission beam associated with a reception beam of a CORESET having the lowest ID among CORESETs configured in the serving cell may be applied to the PUCCH.

In a communication system supporting an unlicensed band, the terminal transmits a physical random access channel (PRACH), PUCCH, PUSCH, sounding reference signal (SRS), phase tracking-reference signal (PT-RS), etc. within the COT secured by the base station. can One spatial filter and/or spatial relation information for all UL channels and UL reference signals (RSs) transmitted by the UE may be defined as one. In embodiments, "spatial filter and/or spatial relationship information that the terminal applies to transmit a certain UL channel and/or UL RS" is "preprocessing applied by the terminal to transmit a certain UL channel and/or UL RS" manner". The preprocessing method may be indicated by DCI and/or higher layer signaling (eg, system information and/or RRC signaling). One preprocessing method may be indicated to the terminal. The preprocessing method may be indicated to the UE by an SRS resource indicator (SRI) field included in DCI. Alternatively, the preprocessing method may be indicated to the UE by a codepoint or index of the TCI status field included in DCI.

When the omni-directional sensing procedure is used for transmission of the UL channel and/or UL RS, the UE may apply the indicated pre-processing method without limitation. In this case, since the terminal can apply a spatial filter with directionality, the terminal's transmission may interfere with an adjacent base station or an adjacent terminal. Therefore, when omni-directional sensing is applied to the COT secured by the base station, it may be preferable for the terminal to transmit the UL channel and/or UL RS by applying a spatial filter without direction.

Method 2.1-1: "When the base station secures a COT using the omni-directional sensing procedure and the terminal does not apply a spatial filter within the corresponding COT", the terminal may transmit a UL channel and/or UL RS.

When the directional sensing procedure is applied, the terminal may perform the directional sensing procedure according to the indicated preprocessing method. For example, when a directional sensing procedure is used to transmit a UL channel (eg, PUSCH and/or PUCCH), the UE may form a reception beam corresponding to a transmission beam corresponding to the UL channel preprocessing method. And, it is possible to apply the maritime reception beam to the directional sensing procedure.

Method 2.1-2: The base station may secure a COT using an omni-directional sensing procedure, and the terminal may transmit a UL channel and/or UL RS by applying a spatial filter within the corresponding COT.

The UE may use the indicated or selected spatial filter as it is. In this case, it may be preferable that the terminal's transmission does not interfere with other base stations and/or other terminals that are not detected by the omni-directional sensing procedure performed by the base station. To support this operation, the UE may use a spatial filter. It may also be desirable to minimize the amount of interference through proper power regulation.

Method 2.1-3: The base station may secure the COT using the omni-directional sensing procedure, and the UE may perform an additional sensing procedure to transmit the UL channel and/or UL RS by applying a spatial filter within the COT. have.

"When the base station performs the omni-directional sensing procedure and the terminal transmits a UL channel and/or UL RS with directionality", the transmission of the terminal may interfere with an adjacent base station or an adjacent terminal. In order to prevent interference or minimize interference, the terminal may perform an additional sensing procedure. An additional sensing procedure may be associated with a spatial filter for a UL channel and/or UL RS that the UE intends to transmit. For example, the additional sensing procedure may be a directional sensing procedure. When the additional sensing procedure is performed, the reception parameters for the additional sensing procedure are the reception parameters for the sensing procedure performed by the terminal to obtain the COT (eg, the length of the sensing slot, the number of sensing slots, the length of the idle slot) , the number of valid slots, the relative arrangement of sensing slots and/or valid slots, a spatial filter deriving the directionality of sensing, a coefficient determining the directionality and/or the spatial filter, etc.) may be different from .

When each of the base station and the terminal performs a sensing procedure, the time for the terminal to receive the DL channel and/or DL RS (eg, decoding time, demodulation time), time allotted to the sensing procedure of the terminal, UL channel and / Alternatively, the time required to prepare the UL RS transmission, advance the time, and/or the time required for switching from the sensing procedure of the terminal supporting half duplex communication to the transmission procedure may be considered.

Section 2.2 Periodic Transmission Method of UL Channel Based on Omni-Directional Sensing Procedure

The base station may secure the COT by performing the directional sensing procedure, and "a case in which the terminal transmits the UL channel and/or UL RS within the COT secured by the base station" may be considered. The terminal may derive a preprocessing method related to the directional sensing procedure used by the base station to secure the COT. The UE may transmit only the UL channel and/or UL RS corresponding to the derived preprocessing method. For example, the base station may transmit COT-DCI, and the terminal may receive COT-DCI. In this case, the UE may know spatial relationship information (eg, spatial filter) related to the CORESET (hereinafter, referred to as “COT-CORESET”) to which the COT-DCI is transmitted. Accordingly, the UE may apply the corresponding pre-processing method to transmit the UL channel and/or UL RS within the COT.

In embodiments, the SPS PDSCH may mean a PDSCH (eg, data unit) transmitted according to the SPS, and the SPS PUCCH or the SPS PUSCH may mean a channel through which the HARQ-ACK for the SPS PDSCH is transmitted. , SPS HARQ-ACK may mean HARQ-ACK for SPS PDSCH. The UE may periodically transmit a UL channel (eg, PUCCH including HARQ-ACK for CG PUSCH or SPS PDSCH). In order to secure a time resource for transmitting a UL channel, the UE may secure a COT by itself by performing a sensing procedure. Alternatively, the terminal may transmit the UL channel within the COT secured by the base station. In this case, the terminal may perform a minimum sensing procedure. For example, the terminal may perform Type-1 channel access in order to secure COT by itself. In order to transmit the UL channel in the COT secured by the base station, the terminal may perform Type-2 channel access (or Type-2A channel access, Type-2B channel access, Type-2C channel access).

Even if the time resources of the UL channel transmitted based on one predetermined beam in the high frequency band are all within the COT secured by the base station, when the base station performs the directional sensing procedure, the terminal procedure), it is possible to determine whether to transmit the UL channel.

When COT-DCI is received, the UE may derive spatial relation information corresponding to the TCI state or quasi co location (QCL) assumption of the COT-CORESET. The UE may know the spatial filter applied to transmit the UL channel and/or UL RS in the corresponding COT based on the spatial relationship information.

Method 2.2-1: When the spatial filter derived from the COT-CORESET by the UE matches the spatial filter of the UL channel, the UE may transmit the UL channel within the COT secured by the base station.

For example, beamforming for control information may have a wide beamwidth, and beamforming for data may have a narrow beamwidth. The UE may determine a reception beam for COT-DCI by using COT-CORESET and may determine a transmission beam for data. Accordingly, even if the reciprocity of UL-DL is applied, the beamwidth of the reception beam may be different from the beamwidth of the transmission beam.

One preprocessing method applied by the UE to the UL channel is fixed, but a plurality of UL channels may be configured and/or activated. In this case, since the same time and frequency resources and different multi-input multi-output (MIMO) configuration variables are set, this may mean "a plurality of UL channels are configured and/or activated". When the maximum number of UL channels configurable in the UE is large, the above-described setting may be possible, but the above-described setting may not be applied to all UEs. Since there are cases in which a plurality of UL channels are configured and/or activated in order to continuously secure COT, the operation of configuring and/or activating a UL channel having only different MIMO configuration variables may be burdensome or wasteful for signaling. In the case of "in case the terminal transmits the UL channel to two or more base stations" or "in the case that the terminal has a plurality of antenna panels", two or more pre-processing schemes may be indicated to the terminal.

When the terminal performs the directional sensing procedure, a COT for the direction in which the directional sensing procedure is performed may be obtained. Accordingly, in the COT, a UL channel (eg, a UL channel with an appropriate spatial filter) may be transmitted. If "the base station secures the COT by performing the directional sensing procedure, and the COT secured by the base station is shared with the terminal", the terminal may transmit the UL channel only for the direction in which the base station performs the sensing procedure. In this case, in order to derive the correlation between the COT-CORESET and the UL channel, a plurality of spatial filters may be indicated to the UE.

Method 2.2-2: For the TCI state or QCL assumption of the COT-CORESET, a set of pre-processing schemes applicable to the UL channel may be indicated to the UE.

When the UE transmits the UL channel within the COT secured by the base station, the transmittable UL channel may be limited to only the UL channel having spatial relationship information associated with the COT-CORESET. The UE can implicitly know the spatial relation information described above from COT-CORESET. Alternatively, the UE may explicitly know the spatial relationship information described above from the COT-DCI.

Method 2.2-3: COT-DCI may include information on a set of preprocessing schemes applied to a UL channel (eg, a set of spatial filters and/or spatial relationship information).

In order to transmit the UL channel within the COT secured by the base station, the UE may select one preprocessing scheme belonging to a set of preprocessing schemes indicated by the COT-DCI. The UE may transmit a UL channel having the selected pre-processing scheme. The pre-processing method selected by the terminal may mean a pre-processing method allowed within the COT secured by the base station.

For example, the preprocessing scheme may be indicated in the form of a TCI state. A synchronization signal/physical broadcast channel (SS/PBCH) block index, a channel state information-reference signal (CSI-RS) resource ID, and/or a sounding reference signal (SRS) resource ID may be indicated to the UE. The preprocessing method may be defined differently for each terminal. In addition, the preprocessing method may be indicated differently for each terminal. Therefore, the set of preprocessing schemes may be expressed differently for each terminal. Therefore, in an embodiment according to method 2.2-3, the TCI status list may be included in the COT-DCI.

A location to which the TCI state is mapped in the COT-DCI may be different for each terminal. The COT-DCI may include a plurality of TCI status lists, and one TCI status list may be commonly interpreted by some UE(s). In this case, the size of the COT-DCI may increase by the number of TCI status lists. In order to reduce the burden of the TCI status list, the TCI status (eg, TCI status list) may consist of only an SS/PBCH block index, a CSI-RS resource ID, and/or an SRS resource ID. The reason is that orthogonal resources may be indicated for each UE for SRS, but the SS/PBCH block and CSI-RS may be commonly indicated to a plurality of UEs.

Alternatively, the method of pre-processing allowed for the UE may be implicitly derived by the reception processor of the CORESET from which the COT-DCI is received. Although the UE still complies with method 2.2-1, methods 2.2-3 and methods not conforming to method 2.2-3 may be utilized.

Section 2.2.1 Example: CG PUSCH

When the CG PUSCH is configured and/or activated in the unlicensed band, the UE may transmit uplink control information (CG-UCI) in the CG PUSCH by multiplexing it with a transport block (TB). CG-UCI may include HARQ process number (HPN), redundancy version (RV), new data indicator (NDI), and/or COT related information. When the UE performs the omni-directional sensing procedure and/or the directional sensing procedure to transmit the CG PUSCH, the COT secured by the sensing procedure may be considered to be initiated by the UE, and the COT-related information is information indicating that the COT cannot be used" or "when the base station uses the corresponding COT, the length of the COT and the CAPC (channel access priority class) index" may be included.

"When the terminal transmits the CG PUSCH within the COT secured by it" or "When the terminal transmits the CG PUSCH within the COT secured by the base station", spatial relation information applied to the CG PUSCH is selected by the terminal can be In this case, the CG-UCI may be extended to additionally include a TCI state or an SRI so that the TB of the CG PUSCH can be easily decoded by the base station.

Method 2.2-4: CG-UCI may include information of a preprocessing scheme (eg, spatial relation information and/or spatial filter).

The base station may indicate to the terminal a set of preprocessing methods or a TCI status list, and the terminal may transmit CG-UCI by applying a preprocessing method belonging to the set of preprocessing methods indicated by the base station. Therefore, the base station can easily decode the CG-UCI received from the terminal. Thereafter, based on the information element(s) included in the CG-UCI, the base station may know the preprocessing method applied to the TB by the terminal.

As a method of expressing the preprocessing method, SRI (or TCI status index) may be used. When the CG PUSCH is configured for the terminal, the base station may indicate and/or set a set of preprocessing methods to the terminal, and the terminal may select one preprocessing method from among the preprocessing method(s) belonging to the set of preprocessing methods. Therefore, the UE may change the SRI applied to the CG PUSCH according to the result of the directional sensing procedure.

The CG PUSCH may be transmitted based on the directional sensing procedure in the COT secured by the UE. In this case, the UE may derive spatial relation information related to the directional sensing procedure, and may apply the derived spatial relation information to the CG PUSCH. The CG PUSCH may be transmitted based on the directional sensing procedure in the COT secured by the base station. In this case, the UE may derive spatial relation information associated with COT-CORESET, and may apply the derived spatial relation information to the CG PUSCH.

"The COT obtained by the terminal is used (eg, shared) in the base station" may be allowed to the terminal by higher layer signaling (eg, CG-COT-Sharing). The base station may additionally set a boundary value (eg, ul-toDL-COT-SharingED-Threshold) applied to the sensing procedure by higher layer signaling to the terminal. When the result (eg, detected energy) of the sensing performed by the terminal is equal to or greater than (or exceeds) the boundary value indicated by the base station, the terminal may not share the COT acquired by the terminal with the base station. When the result (eg, detected energy) of the sensing performed by the terminal is less than (or less than) the boundary value indicated by the base station, the terminal may share the COT acquired by the terminal with the base station.

In addition, the UE may generate a CG-UCI including an index indicating a time resource structure that the COT obtained through the sensing procedure may have. The time resource structure may be expressed in terms of CAPC, slot offset, and/or the number of slots based on the slot in which the CG-UCI is transmitted. The above-described set of time resource structures may be configured in the terminal by higher layer signaling. Accordingly, the UE may express one or more time resource structures based on a set set by higher layer signaling. The UE may generate a CG-UCI including an index corresponding to one time resource structure belonging to a set of time resource structures.

When the directional sensing procedure is performed, the boundary value of the sensing procedure applied by the terminal may be indicated differently.

Method 2.2-5: The base station may indicate to the terminal two or more boundary values through higher layer signaling. The terminal may select one boundary value from among the boundary values indicated by the base station, and may perform an omni-directional sensing procedure or a directional sensing procedure based on the selected boundary value, and use the COT obtained by the sensing procedure as the base station or other terminal You can decide if you can share it with others.

In an embodiment, the boundary value for the directional sensing procedure and the boundary value for the omni-directional sensing procedure may be separately indicated to the terminal. For example, different boundary values may be indicated to the terminal according to a direction in which a directional sensing procedure is performed and/or a spatial filter applied to the sensing procedure. The boundary value for the omni-directional sensing procedure is distinguished from the boundary value for the directional sensing procedure, but the same boundary value may be indicated depending on the spatial filter in which the directional sensing is performed.

When the directional sensing procedure is performed, the time resource structure that the COT acquired by the terminal may have may be indicated differently. Alternatively, the time resource structure may be equally applied regardless of the direction of the sensing procedure.

Method 2.2-6: The time resource structure of the COT acquired by the terminal may be equally applied regardless of the method of the sensing procedure performed by the terminal.

Section 2.3 Dynamic Transmission Method of UL Channel Based on Directional Sensing Procedure

The terminal may transmit PUSCH or PUCCH according to the instruction of the base station. “When the UE transmits HARQ-ACK for PDSCH scheduled by DL-DCI as PUCCH” or “When UE transmits PUSCH scheduled by UL-DCI”, the UE transmits UL-DCI and/or The preprocessing method indicated in DL-DCI can be applied.

The preprocessing method may be explicitly or implicitly indicated by a non-fallback DCI. For example, the non-fallback DCI may include a field indicating a preprocessing method. In the PUSCH transmission procedure, the SRI field (or TCI status field) may indicate a spatial filter. In the PUCCH transmission procedure, an index of a control channel element (CCE) to which a PRI field and/or DL-DCI is mapped may indicate one resource (eg, a PUCCH resource). Here, the spatial relationship information for the PUCCH resource may be indicated by higher layer signaling.

The fallback DCI may not explicitly indicate a preprocessing method. In this case, the terminal may apply the standard preprocessing method. A preprocessing method applied to transmission of a UL channel may be indicated to be associated with CORESET. When it is configured to receive two or more CORESETs (eg, when two or more CORESET IDs are indicated), the UE may determine from which CORESET a pre-processing scheme should be derived. For example, the terminal may use "the most recently received CORESET", "the CORESET with the lowest ID", or "the CORESET that scheduled the corresponding UL channel" to derive the preprocessing method.

It may be desirable that the transmission directionality of the terminal coincides with the directionality sensing procedure performed. In order to transmit the UL channel within the COT secured by the base station, the terminal may consider a change to the reference preprocessing method.

Section 2.3.1 Example: PUCCH

The UE may receive a DL-DCI from the base station, may receive a PDSCH scheduled by the DL-DCI, and may decode the PDSCH. The UE may transmit the HARQ-ACK (eg, ACK or NACK), which is the decoding result of the PDSCH, to the base station through the PUCCH. A case of beam failure recovery may be considered in the PUCCH transmission procedure.

The beam failure recovery procedure may be performed for beam failure recovery for the PCell or the SCell. The UE may change the reception beam to a new DL RS referred to as q1 while receiving a radio link monitoring (RLM) RS referred to as q0. In order to support this operation (eg, a reception beam change operation), the UE sets a PRACH preamble configured for beam failure recovery and a search space set of beam failure recovery for receiving a response from the base station to the PRACH preamble. is available. When the UE needs to transmit the PUCCH even before receiving the information indicating the new reception beam from the base station, the spatial filter applied to the PUCCH may be limited to be the same as the spatial filter of the most recently transmitted PRACH preamble.

In a scenario other than beam failure recovery, the UE may select the CORESET having the lowest ID among the CORESET(s) configured in the serving cell transmitting the PUCCH. The spatial relationship information associated with the selected CORESET may correspond to a spatial filter of PUCCH. To support this operation, the base station may instruct the UE related information (eg, enableDefaultBeamPL-ForPUCCH) through higher layer signaling, and may not indicate RS, which is a reference for path attenuation, through higher layer signaling.

A case in which the base station secures the COT by performing the directional sensing procedure may be considered. In addition, a case in which the time resource indicated to transmit the PUCCH belongs to the COT may be considered.

Method 2.3-1: When spatial relationship information of PUCCH is not associated with COT-CORESET, the UE may not transmit PUCCH. When the spatial relationship information of the PUCCH is associated with the COT-CORESET, the UE may transmit the PUCCH.

The reason why the base station does not receive the PUCCH from the terminal (eg, DTX, "when the PUCCH is not transmitted by the sensing procedure performed in the terminal", or "when the spatial relationship information of the PUCCH is different from the COT-CORESET") may not know If the PUCCH is not received from the terminal, the base station may transmit the PDSCH to the terminal again. Alternatively, the base station may instruct the terminal to retransmit the PUCCH.

The UE may not fix one PUCCH pre-processing scheme, and may select and/or change the pre-processing scheme under a specific condition. In this case, the signaling burden of the base station can be reduced. When a search space set capable of detecting COT-DCI is configured in the UE, the same spatial filter as that of the PRACH preamble may not be applied in the PUCCH transmission procedure. To support this operation, the PUCCH pre-processing scheme may be implicitly changed by COT-DCI, and the UE may transmit the PUCCH within the COT secured by the base station.

Method 2.3-2: The UE may transmit the PUCCH to the base station by applying the spatial relationship information associated with the most recently received CORESET in the time resource indicated to transmit the PUCCH.

If it is not set in the terminal to receive COT-DCI, the terminal receives the most recently received CORESET (or CORESET including DCI to which PUCCH is allocated) instead of the same spatial relationship information as the most recently transmitted PRACH preamble. Related spatial relationship information can be applied.

When receiving the COT-DCI is configured in the terminal, the base station may instruct the terminal to transmit the PUCCH. In addition, the base station may instruct the terminal to transmit in an unreserved COT. The base station may instruct the terminal to perform Type-1 channel access (eg, "LBT category 4" or "sensing to perform random backoff") before transmission of the PUCCH. However, when the COT-DCI is received from the base station, the terminal performs a sensing procedure before transmission of the PUCCH for Type-2 channel access (eg, "LBT category 2 (eg, Type-2A, Type-2B, Type- 2C, etc.)" or "sensing performed in a fixed duration"), and the spatial relationship information of PUCCH may be changed to be related to the most recently received CORESET. Based on this operation, the terminal may transmit the PUCCH within the COT secured by the base station.

When the directional sensing procedure is used, the base station can transmit only the CORESET to which the same or similar spatial filter is applied within the COT secured by the base station. In this case, the UE may derive that the most recently received CORESET and COT-CORESET have the same spatial relationship information.

Method 2.3-3: The UE may transmit the PUCCH to the base station by applying spatial relation information associated with COT-CORESET.

The UE may derive spatial relation information from the COT-CORESET instead of the most recently received CORESET, and may know a spatial filter applied to the PUCCH based on the spatial relation information.

The UE may receive DL-DCI from the search space set of beam failure recovery. In this case, it may be assumed that the UE can receive CORESET 0 in association with the DL RS changed to q1 from a preset time.

Section 2.3.2 Example: PUSCH

When the pre-processing method is indicated by the base station in the PUSCH transmission procedure, the terminal may apply the pre-processing method indicated by the base station. Alternatively, the base station may not indicate the preprocessing method to the terminal. For example, when the PUSCH is scheduled by the fallback DCI, a spatial filter applied to the PUCCH may be applied as a preprocessing method of the PUSCH. In this case, the base station can always configure the PUCCH in the UL BWP for allocating the PUSCH, and the PUCCH pre-processing method can be necessarily configured. On the other hand, when the PUSCH is scheduled by non-fallback DCI, the preprocessing method applied to the PUSCH may be indicated by the SRI field (or the TCI status field). These restrictions can be relaxed. For example, even when a pre-processing method is not set for any PUCCH in the UL BWP used by the base station, "the spatial filter applied by the terminal is defined" is indicated by higher layer signaling (eg, enableDefaultBeamPL-ForPUSCH0_0). can be For example, the terminal may receive information on the reference beam from the base station, and may apply the reference beam in PUSCH scheduled by the fallback DCI. This operation may be applied even when the PUCCH pre-processing method is configured for the UE. When a spatial filter is separately instructed to the UE, a reference RS for estimating path attenuation may be separately instructed to the UE in order to transmit the PUSCH using the reference spatial filter. Whether the reference RS is applied or not may be indicated by higher layer signaling (eg, enableDefaultBeamPL-ForPUSCH0_0).

Therefore, the spatial filter applied to the PUSCH scheduled by the fallback DCI may be determined according to "whether to use the reference beam configured by higher layer signaling" and/or "whether to configure the PUCCH in the UL BWP in which the PUSCH is to be transmitted".

For example, if "the terminal uses the reference beam and the PUCCH is not configured in the UL BWP", the terminal has the lowest ID among the CORESET(s) set in the DL BWP for the PUSCH scheduled as the fallback DCI CORESET and Associated spatial relationship information can be derived. That is, the UE may derive the spatial filter applied to PUSCH transmission from the spatial filter applied in the reception procedure of the CORESET having the lowest ID.

For example, if "the terminal uses the reference beam, the PUCCH is configured in the UL BWP, and a preprocessing method is not configured for all PUCCHs", the terminal has the lowest ID among the CORESET(s) set in the DL BWP It is possible to derive spatial relation information related to CORESET.

A case in which the base station secures COT by performing directional sensing may be considered. In addition, a case in which the time resource indicated to transmit the PUSCH belongs to the COT may be considered.

Method 2.3-4: When spatial relation information of PUSCH is not associated with COT-CORESET, the UE may not transmit PUSCH. When spatial relation information of PUSCH is associated with COT-CORESET, the UE may transmit PUSCH.

The base station may not know why the UE does not receive the PUSCH. The reason for PUSCH reception failure may be "DTX", "transmission failure due to a sensing procedure performed in the terminal", or "spatial relationship information of PUSCH is different from spatial relationship information of COT-CORESET". In this case, the base station may instruct the terminal to retransmit PUSCH.

The UE may select and/or change the preprocessing scheme under a specific condition without fixing the PUSCH preprocessing scheme. In this case, the signaling burden of the base station may be reduced. When a search space set capable of detecting COT-DCI is configured in the UE, the spatial filter associated with the CORESET having the lowest ID in the PUSCH transmission procedure may not be applied. To support this operation, the PUSCH pre-processing scheme may be implicitly changed by COT-DCI, and the PUSCH may be transmitted within the COT secured by the base station.

Method 2.3-5: The UE may transmit the PUCCH to the base station by applying spatial relation information associated with the most recently received CORESET in the time resource indicated to transmit the PUSCH.

If it is not configured in the terminal to receive the COT-DCI, the terminal may apply spatial relationship information related to the most recently received CORESET rather than the spatial filter associated with the CORESET having the lowest ID.

When receiving the COT-DCI is configured in the terminal, the base station may instruct the terminal to transmit the PUSCH. Here, the base station may instruct the terminal to transmit the PUSCH in an unreserved COT. The base station may instruct the terminal to perform Type-1 channel access (eg, LBT category 4, or sensing to perform random backoff) before transmitting the PUSCH. The UE detecting the COT-DCI performs a sensing procedure before transmitting the PUSCH for Type-2 channel access (eg, LBT category 2 (eg, Type-2A, Type-2B, Type-2C) or a fixed duration Sensing performed by ). The UE may change spatial relation information of PUSCH to be related to the most recently received CORESET. According to this operation, the terminal can transmit the PUSCH within the COT secured by the base station.

When the directional sensing procedure is used, the base station can transmit only CORESET to which the same or similar spatial filter is applied within the secured COT. In this case, the UE may derive the same spatial relationship information for the most recently received CORESET and COT-CORESET.

Method 2.3-6: The UE may transmit the PUSCH to the base station by applying spatial relation information associated with COT-CORESET.

The UE may derive spatial relation information from COT-CORESET instead of the most recently received CORESET, and may know a spatial filter applied to PUSCH based on the derived spatial relation information.

Chapter 3 DL Channel Reception Method

Section 3.1 Receiving Method of Search Space Set Based on Omni-Directional Sensing Procedure

The base station may secure a channel by performing a sensing procedure, and may transmit a PDCCH and/or a PDSCH to the terminal. The terminal may not know when the base station is sensing success. Therefore, the UE can frequently monitor CORESET to increase the transmission amount. When DCI is detected in CORESET, the UE may consider that the base station has secured the channel. If necessary, the base station can inform the types of time and frequency resources of the channel (eg, COT) secured by the base station by broadcasting the COT-DCI to the terminals. The base station may set the search space set to the terminal. In this case, the base station may set the period of the search space set to be short so that the terminal can receive the CORESET. Here, the period of the search space set may be set in units of mini-slots or sub-slots. Search space aggregation does not need to occur frequently according to characteristics of traffic (eg, eMBB traffic) within a time resource (eg, COT) secured by the base station. In this case, the base station may set the period of the search space set to be long in time within the COT, and may inform the terminal of the set period information. Here, the period of the search space set may be set in units of slots.

In order to reduce power wasted in the monitoring procedure of the search space set of the terminal, a function of search space set switching may be introduced. A search space set (eg, Type3-PDCCH CSS set or USS set) may consist of elements of a search space set group, and the search space set group may be divided into two. For example, the search space set group may be divided into a search space set group 0 and a search space set group 1 . The search space set group 0 and the search space set group 1 may be configured in the terminal to have different periods. For example, the period of the search space set group 0 may be shorter than the period of the search space set group 1. In this case, the terminal may perform a monitoring operation for search space set group 0 according to a short period, and may perform a monitoring operation for search space set group 1 according to a long period.

A search space set may correspond to CORESET. The search space set may be set together with the CORESET ID. When the search space set is periodically set, CORESET may be periodically transmitted. The TCI state for CORESET may be indicated to the UE by higher layer signaling (eg, system information, RRC signaling, and/or MAC CE). Since the UE knows the TCI state for CORESET, DCI can be detected using the corresponding TCI state in the time resource for monitoring the search space set.

3 is a conceptual diagram illustrating a first embodiment of a method for monitoring a search space aggregation group based on an omni-directional sensing procedure.

Referring to FIG. 3 , a search space aggregation group may be changed, and a plurality of TCI states for CORESET may exist. The UE may perform a CORESET reception operation to monitor a search space set belonging to search space set group 0. In search space set group 0, the UE may frequently monitor the search space set. Thereafter, the search space set group 0 may be changed to the search space set group 1. In this case, in the search space set group 1, the UE may rarely monitor the search space set. Thereafter, the search space set 1 may be changed back to the search space set group 0. In this case, the terminal may frequently monitor the search space set. The TCI state for CORESET belonging to the search space set group may be set to another TCI state. For example, the TCI state of CORESET a may be indicated as TCI state a, and the TCI state of CORESET b may be indicated as TCI state b. The UE may receive CORESET a by applying TCI state a, and may receive CORESET b by applying TCI state b. Since the UE can receive all CORESETs, it can perform a monitoring operation on all search space sets.

The base station can secure the channel by using the omni-directional sensing procedure. In this case, the base station may transmit a beam in any direction within the COT. Accordingly, the base station may transmit an arbitrary CORESET to the terminal. However, when the base station secures a channel using a directional sensing procedure, CORESET that can be transmitted within the COT may be limited. The reason is that only CORESET corresponding to directional sensing can be transmitted. The direction of the transmit beam of CORESET may coincide with the direction of the receive beam applied in the directional sensing procedure to some extent.

Section 3.2 Receiving Method of Search Space Set Based on Directional Sensing Procedure

When the directional sensing procedure is used, it may be preferable for the base station to transmit only the CORESET that is the same as the TCI state of the CORESET associated with the search space set in which the COT-DCI is transmitted within the COT. Therefore, the UE can distinguish between a valid TCI state and an invalid TCI state within the COT. In embodiments, "that the search space set is associated with a specific TCI state" may mean "that the TCI state of the CORESET with which the corresponding search space set is associated is the specific TCI state".

Method 3.2-1: The UE may receive only CORESET having a valid TCI state.

It is preferable that the UE does not change the reception beam in order to receive CORESET having an invalid TCI state. For a CORESET associated with a specific search space set, the UE may determine whether the TCI state of the CORESET is valid or invalid, and may not monitor the search space set associated with the invalid CORESET within the COT.

4 is a conceptual diagram illustrating a first embodiment of a method for monitoring a search space aggregation group based on a directional sensing procedure.

Referring to FIG. 4 , the UE may perform a reception operation for a specific CORESET according to the TCI state of the CORESET. The base station may perform a transmission operation using CORESET corresponding to the TCI state a. In this case, the UE may perform a reception operation for the CORESET corresponding to the TCI state a. When a certain search space set is associated with a TCI state other than the TCI state a, the UE may not monitor the search space set associated with the other TCI state. The UE may apply switching of the search space set group to the search space set associated with the TCI state a, and the monitoring opportunity (eg, monitoring occasion) according to the change of the search space set group is It may be a monitoring opportunity shown in FIG. 4 . The UE may receive the COT-DCI, and may know the time and frequency resources (eg, structure) of the COT secured by the base station from a field belonging to the received COT-DCI. In addition, the duration information of the COT may be indicated by the COT-DCI. The COT duration information may be utilized to change the search space set group.

When the UE performs a monitoring operation for only COT-CORESET, the potential number of DCIs and/or the size of the search space set may be insufficient. A part of the CORESET may not be monitored, and accordingly, the base station may control the same time resource using a small CORESET within the secured COT. It is desirable for the base station to secure more CORESETs.

Method 3.2-2: CORESET(s) including search space set(s) within the COT secured by the base station may all be interpreted as having the same TCI state.

CORESET can be divided into valid CORESET and invalid CORESET. The TCI state of an invalid CORESET may be updated, and the updated TCI state may be interpreted to be the same as the TCI state of a valid CORESET. According to this operation, the UE must receive all CORESETs set within the COT. FIG. 5 is a conceptual diagram illustrating a second embodiment of a method for monitoring a search space aggregation group based on a directional sensing procedure.

Referring to FIG. 5 , the TCI state of CORESET may be changed, and the UE may monitor a search space set group associated with CORESET interpreted as a valid CORESET according to the change in TCI state. CORESET may have the same TCI state as a specific CORESET regardless of the TCI state. For example, the TCI state of the COT-CORESET is set to the TCI state a, but the TCI states of the CORESETs other than the corresponding COT-CORESET may be set to the UE differently from the TCI state a. According to the proposed method, the UE may perform a reception operation for all CORESETs within the COT assuming the TCI state a, and may monitor the search space set(s) associated with the corresponding CORESET(s).

Chapter 4 Reception of SPS PDSCH

Section 4.1 How to Configure SPS PDSCH to Support Random Arrival Traffic

URLLC traffic can arrive periodically. Alternatively, the URLLC traffic may arrive randomly. In this case, the random arrival time may be expressed as a random variable, and an expected value and a variance value may be derived based on the random variable. This operation may be applied to DL traffic transmission in the base station. To reduce the amount of PDCCH (eg, DCI), the SPS PDSCH may be configured and/or activated. In this case, the period of the SPS PDSCH may be defined as an expected value of the arrival time of URLLC traffic, and a plurality of SPS PDSCHs may be configured and/or activated. The time resource of the SPS PDSCH may be configured to be more distributed than the dispersion value of the arrival time of the URLLC traffic. This setup can be illustrated in FIG. 6 .

6 is a conceptual diagram illustrating a first embodiment of SPS PDSCH configuration.

Referring to FIG. 6 , two PDSCH instances may be allocated in one PDSCH occasion, and PUCCHs for transmitting HARQ-ACKs for the two PDSCH instances may be allocated. The above-described PDSCH occasion may be periodically configured.

When the above-described operation is applied to UL traffic transmission, a CG (configured grant) PUSCH may be configured and/or activated, and the period of the CG PUSCH may be defined as an expected value of the arrival time of URLLC traffic, and a plurality of CGs PUSCHs may be configured and/or activated. The time resource of the CG PUSCH may be configured to be more distributed than the dispersion value of the arrival time of the URLLC traffic. This setup can be illustrated in FIG. 7 .

7 is a conceptual diagram illustrating a first embodiment of CG PDSCH configuration.

Referring to FIG. 7 , two PUSCH instances may be allocated in one PUSCH occasion, and the above-described PUSCH occasion may be periodically configured.

If the URLLC traffic arrives randomly, the URLLC traffic may arrive later than the last PDSCH instance belonging to the PDSCH occasion or the last PUSCH instance belonging to the PUSCH occasion. In this case, the base station may allocate the PDSCH using dynamic scheduling. Alternatively, the UE may request dynamic scheduling by transmitting a scheduling request (SR), may receive dynamic scheduling information according to the SR from the base station, and may check the allocated PUSCH from the dynamic scheduling information.

Section 4.2 How to Configure Time Resources of SPS PDSCH

To support URLLC traffic, an SPS PDSCH occasion comprising one or more SPS PDSCH instances may be introduced. In order to support this operation, the SPS PDSCH occasion may be one set consisting of two or more SPS PDSCHs (eg, SPS PDSCH instances). Alternatively, the resource of one SPS PDSCH (eg, SPS PDSCH instance) may be extended.

8A is a conceptual diagram illustrating a first embodiment of an SPS PDSCH occasion, and FIG. 8B is a conceptual diagram illustrating a second embodiment of an SPS PDSCH occasion.

Referring to FIG. 8A , SPS PDSCH instances included in an SPS PDSCH occasion may be configured within one slot.

Referring to FIG. 8B , SPS PDSCH instances included in the SPS PDSCH occasion may be configured in two slots.

Method 4.2-1: Configuration of one or more SPS PDSCHs may consist of one SPS set.

The SPS set may include one or more SPS PDSCHs. Each of the one or more SPS PDSCHs may be activated or deactivated. Alternatively, one or more SPS PDSCHs may be simultaneously activated or deactivated. The base station may indicate one SPS set using a specific field of an activating DCI, and all SPS PDSCH(s) belonging to the indicated SPS set may be activated. The base station may indicate one SPS set by using a specific field of the release DCI, and all SPS PDSCH(s) belonging to the indicated SPS set may be deactivated. A specific field of DCI (eg, activated DCI, released DCI) may be a HARQ process number (HPN) field.

Configurations for one or more SPS PDSCHs belonging to the same SPS set may have independent values for some or all configuration variables.

When some configuration variables have different values, time resource information of each SPS PDSCH and/or information related to PUCCH for transmission of HARQ-ACK for each SPS PDSCH may be included in the above-described configuration. The time resource of the SPS PDSCH may mean the first symbol to which the SPS PDSCH is mapped and the number of symbols (eg, start and length indicator value (SLIV)) within the slot. Information related to the PUCCH includes a resource index (eg, PRI) and a time resource in which the PUCCH is transmitted (eg, a (sub) slot offset in which the PDSCH is received and the (sub) slot in which the PUCCH is transmitted (sub) slot offset) can mean In embodiments (sub)slot may mean "slot" or "subslot".

Bit(s) included in a confirmation (confirmation) MAC control element (CE) may indicate all SPS PDSCHs belonging to the SPS set.

HPN may be independently derived for each SPS PDSCH. The HPN may be derived from a time resource at which the SPS PDSCH is received and/or an HPN offset.

Method 4.2-2: Two or more time resources may be configured for SPS PDSCH, and one or more PUCCH resources may be configured for SPS PDSCH.

The time resource (eg, time domain resource assignment (TDRA)) of the SPS PDSCH may be indicated by the activation DCI. According to method 4.2-2, the TDRA may represent two or more SLIVs. SLIV may not mean only an index derived from a combination of S and L. S and L may be indicated separately. S may be the index of the start symbol, and L may be the number of symbols. A value of L may be commonly applied, and S may be set to one or more values. TDRA may indicate non-consecutive symbols. Here, non-consecutive symbols may be distinguished from each other and may be expressed as SLIV. When the TDRA expresses n non-consecutive symbols, the non-consecutive symbols can be expressed as "SLIV 1, SLIV 2, ..., SLIV n" without compromising generalization. n may be a natural number.

TB may be allocated from some resources indicated by the TDRA. Therefore, in a resource indicated by one of the SLIVs, a TB may be mapped. Alternatively, a TB may be mapped in a resource indicated by one of the SLIVs, and a TB may not be mapped in a resource indicated by the other SLIV. A TB may be mapped differently for each SLIV, and a TB may not be mapped in a resource indicated by some SLIVs.

HPN may be derived from TDRA. The HPN may be derived from the first SLIV belonging to the TDRA. Alternatively, the HPN may be allocated for each SLIV expressed in TDRA. When HPN is derived from SLIV, HPN may be derived based on the value of S identified by SLIV. For example, the HPN may be derived from the value of S and the offset set in the terminal by higher layer signaling. As another example, the HPN may be derived from the sum of an offset set in the terminal by higher layer signaling and S.

Method 4.2-3: When method 4.2-2 is applied, each SLIV (or S) may be derived from the first symbol of the slot.

Method 4.2-4: When method 4.2-2 is applied, each SLIV (or S) may be derived from the first symbol of the CORESET in which the activation DCI is received.

Method 4.2-5: Where Method 4.2-2 applies, each SLIV (or S) may be derived based on the previous SLIV (or S and/or L). For example, SLIV 1 may be derived from the first symbol of the slot, and SLIV 2 may be derived from the last symbol indicated by SLIV 1 or a symbol following the last symbol. Therefore, some SLIVs may be interpreted beyond the boundary of the slot.

Method 4.2-6: The time resource of the PDSCH can be interpreted in a unit smaller than the slot (eg, a subslot or a minislot), and a configuration variable corresponding to the number of repetitions (K) is utilized in the configuration procedure of the SPS PDSCH can be For example, the number of SLIVs in the SPS PDSCH may be equal to the number of repetitions (K). The first SLIV may be indicated by the activating DCI, and the SLIV in consecutive K-1 subslots or minislots after the first SLIV may be interpreted relatively. In order to support this operation, the length of the PDSCH that SLIV means may be smaller than the length of a subslot or a minislot.

In the embodiment shown in FIG. 8A, the time resource of the SPS PDSCH may be configured (or defined) in one slot. In the embodiment shown in FIG. 8B, the time resource of the SPS PDSCH may be configured (or defined) in two or more slots.

Based on Method 4.2-3, SLIV 1 and SLIV 2 can be interpreted independently. The first symbol of the slot may be expressed as 0. In this case, in the embodiment shown in FIG. 8A , S ₁ of SLIV 1 may be 2, and S ₂ of SLIV 2 may be 9. In the embodiment shown in FIG. 8B , S ₁ of SLIV 1 may be 2, S ₂ of SLIV 2 may be 12, and S ₃ of SLIV 3 may be 22.

Based on Method 4.2-4, SLIV 1 and SLIV 2 can be interpreted independently. The first symbol of CORESET including active DCI in the slot may be expressed as 0. Accordingly, the embodiment shown in FIG. 8A and/or the embodiment shown in FIG. 8B may be interpreted differently according to the symbol in which the active DCI is received. In the embodiment shown in FIG. 8B , S of some SLIVs may be 14 or more.

Based on method 4.2-5, the first symbol of the slot or the first symbol of CORESET including the active DCI may be regarded as 0, and based on this, SLIV 1 may be interpreted. The last symbol of the PDSCH indicated by SLIV 1 or the symbol next to the last symbol may be regarded as 0, and SLIV 2 may be interpreted based on this. In the embodiment shown in FIG. 8A , S ₁ of SLIV 1 may be 2, and S ₂ of SLIV 2 may be 3. In the embodiment illustrated in FIG. 8B , S ₁ of SLIV 1 may be 2, S ₂ of SLIV 2 may be 6, and S ₃ of SLIV 3 may be 6.

Based on method 4.2-6, a minislot or subslot is 7 symbols (eg, half of the slot, 7 symbols when a normal cyclic prefix (CP) is used, extended) 6 symbols) when CP is used. In the procedure of setting the SPS PDSCH to the terminal, the number of minislots, the number of subslots, and/or the number of slots may be indicated to the terminal. The above-mentioned number may be pdsch-AggregationFactor-r16. According to the above configuration, it can be expected that the PDSCH is periodically received in consecutive minislots, consecutive subslots, or consecutive slots. In this case, one SLIV may be indicated, and the same SLIV may be applied to consecutive minislots, consecutive subslots, or consecutive slots. In the embodiment shown in FIG. 8A , S of SLIV may be 2, the length of the minislot or the length of the subslot may be half of the slot, and the number of minislots or the number of subslots may be 2.

The HPN may be independently derived for each SLIV (or S) of the SPS PDSCH. The HPN may be derived from a time resource at which the SPS PDSCH is received and/or an HPN offset. The HPN may be interpreted in units of symbols, mini-slots, or sub-slots.

Chapter 5 Transmission Method of SPS PUCCH

Section 5.1 How to Set Time Resources of SPS PUCCH

The UE may receive the SPS PDSCH and may transmit a HARQ-ACK for the SPS PDSCH. A set of slots or subslots through which PUCCH is transmitted by higher layer signaling may be indicated to the UE, and one value belonging to the set may be indicated as an index. The active DCI may include the above-described index. The time resource of the SPS PUCCH may mean not only the first symbol or the number of symbols to which the PUCCH is mapped, but also the timing at which the HARQ-ACK is transmitted (eg, a slot or a subslot).

When the SPS set based on method 4.2-1 is configured, the time resource of the SPS PUCCH may be independently indicated for each SPS PDSCH.

When one or more time resources for the SPS PDSCH are indicated (eg, when a plurality of SLIVs are used), time resources of a plurality of SPS PUCCHs may be derived.

Method 5.1-1: The time resource of one SPS PUCCH in TDRA may be derived.

One SPS PUCCH may include HARQ-ACK(s) for PDSCH(s) received on resource(s) indicated by one or more SLIVs.

Method 5.1-2: In TDRA, an independent SPS PUCCH time resource may be derived for each SLIV to which the SPS PDSCH is mapped.

One SPS PUCCH may include HARQ-ACK for one SLIV. Therefore, a plurality of SPS PUCCHs may be derived for the SPS PDSCH, and a specific method may be further subdivided.

Method 5.1-3: When method 5.1-2 is applied, the time resource of each SPS PUCCH may be derived from the offset of one slot (or minislot or subslot).

One offset (eg, K) may be indicated to the UE by “higher layer signaling” or “combination of higher layer signaling and activation DCI”. The offset may be an interval from the reception time of the PDSCH to the transmission time of the PUCCH. The offset may be interpreted in units of slots, minislots, or subslots. Based on the SLIV and K (eg, offset) to which the TB is mapped, the time resource of the PUCCH corresponding to the received TB may be derived. When only one or less TBs can be mapped in one slot, one minislot, or one subslot, the SPS PUCCH can be expected to be transmitted in different slots, different minislots, or different subslots.

Method 5.1-4: When method 5.1-2 is applied, the time resource of each SPS PUCCH may be independently indicated.

One offset (eg, K) may be indicated to the UE by “higher layer signaling” or “combination of higher layer signaling and activation DCI”. The offset may be interpreted as one or more time resources. The interpreted time resources may respectively correspond to time resources of the SPS PUCCH. The number of time resources may be equal to the number of SLIVs interpreted by the TDRA.

9A is a conceptual diagram illustrating a first embodiment of a method for setting a time resource of an SPS PUCCH, and FIG. 9B is a conceptual diagram illustrating a second embodiment of a method of setting a time resource of an SPS PUCCH.

Referring to FIG. 9A , two SLIVs (eg, SLIV 1 and SLIV 2) may be indicated, and a PUCCH resource (eg, SPS PUCCH resource) may be configured after K1 for each SLIV. . PUCCH resources may be allocated for each SLIV.

Referring to FIG. 9B , one SLIV may be indicated, and the SLIV may be applied to consecutive slots, consecutive minislots, or consecutive subslots. In this case, PUCCH resources (eg, SPS PUCCH resources) may be allocated after K1 from PDSCH.

According to another method, PDSCH candidates included in the SPS PUCCH may be classified into all PDSCH candidates belonging to a predetermined time window from the transmission timing of the PUCCH. This operation will be described in more detail in Method 5.3-7.

Section 5.2 How to Determine HARQ-ACK Transmitted in SPS PUCCH

The UE may receive the TB and may transmit a HARQ-ACK for the received TB. In the eMBB traffic transmission procedure, the base station may generally perform scheduling such that "ACK probability = 90%, NACK probability = 10%". In the URLLC traffic transmission procedure, the base station may perform scheduling such that the ACK probability is generally 1E-3 or more. Accordingly, the UE may determine the ACK with a probability of 1E-3 and may transmit the ACK in the PUCCH. In order not to interfere with other UEs, when an ACK occurs, the UE may not transmit the corresponding ACK in the PUCCH. That is, the UE may transmit only the NACK through the PUCCH.

Method 5.2-1: Only when HARQ-ACK is NACK, the UE may transmit NACK in PUCCH.

In order to transmit HARQ-ACK of 3 bits or more, the UE may generate a HARQ codebook and may transmit the HARQ codebook in PUCCH. In this case, in order to apply method 5.2-1, it may be limited to a case of transmitting HARQ-ACK of less than 3 bits or 1 bit.

In the case of transmitting 1-bit HARQ-ACK, only a sequence for NACK may be configured in the UE. If the PUCCH is not received from the terminal, the base station may consider that the HARQ-ACK for the corresponding TB (or the corresponding SPS PDSCH) is ACK. When the PUCCH is received from the terminal, the base station may consider that the HARQ-ACK for the corresponding TB (or the corresponding SPS PDSCH) is NACK.

Based on method 5.2-1, "in case the SPS PDSCH is associated with a plurality of SPS PUCCHs and a continuous NACK occurs in the terminal", the terminal may not transmit the PUCCH. The reason is that the UE can transmit the PUCCH only when the ACK is first obtained. After that, for the PUCCH associated with the SPS PDSCH, the UE may transmit the PUCCH. Alternatively, the UE may not transmit the PUCCH.

10A is a conceptual diagram illustrating a first embodiment of a method of transmitting HARQ-ACK in the last SPS PUCCH associated with the SPS PDSCH, and FIG. 10B is a second embodiment of a method of transmitting a HARQ-ACK in the last SPS PUCCH associated with the SPS PDSCH. is a conceptual diagram showing

Referring to FIG. 10A , when the HARQ-ACK is an ACK, the UE may transmit the corresponding ACK in the SPS PUCCH.

Referring to FIG. 10B , when a NACK occurs, the UE may not transmit an SPS PUCCH, and when an ACK occurs, the UE may transmit an ACK in the last SPS PUCCH. Since only the ACK for the SPS PDSCH is transmitted, the base station cannot know whether "the reason that the ACK is not received" is "the reason why the NACK for the TB received by the terminal occurred" or "the reason why the TB was not received by the terminal". In order to resolve the ambiguity described above, the UE may transmit a PUCCH including HARQ-ACK. Here, the PUCCH may be the last resource (eg, the last SPS PUCCH) located in the time domain among the SPS PUCCHs related to the SPS PDSCH. The UE may not transmit SPS PUCCH when NACK occurs, and may transmit HARQ-ACK (eg, TB decoding result) in the last SPS PUCCH.

Method 5.2-2: Based on method 5.2-1, the UE may transmit HARQ-ACK in the last SPS PUCCH.

Method 5.2-3: The UE may generate a HARQ codebook including HARQ-ACK (eg, ACK or NACK).

For HARQ-ACK transmission of 3 bits or more, the UE may generate a HARQ codebook including HARQ-ACK bit(s) based on a location determined according to a technical standard. In the procedure for receiving URLLC traffic, the UE may acquire ACK in most cases, and may acquire NACK in some cases. In this case, the UE may generate a HARQ codebook including HARQ-ACK.

Transmission of PUSCH as well as PUCCH may be indicated to the UE. In this case, the UE may multiplex HARQ-ACK (or HARQ codebook including HARQ-ACK) in PUSCH.

In the case of the Type-1 HARQ codebook and/or the Type-3 HARQ codebook, the size of the HARQ codebook may be indicated semi-fixedly. In this case, the size of the HARQ codebook may not change depending on whether DCI is received. In order to maintain the size of the HARQ codebook regardless of "when HARQ-ACK is always transmitted", "when only NACK is transmitted", or "when only ACK is transmitted", Type-1 HARQ codebook and/or Type-3 The HARQ codebook may include HARQ-ACK for the SPS PDSCH as any value. In this case, the corresponding value may be HARQ-ACK, fixed ACK, or fixed NACK. In embodiments, the Type-1 HARQ codebook may mean a Type1 HARQ-ACK codebook, and the Type-3 HARQ codebook may mean a Type-3 HARQ-ACK codebook. The Type-3 HARQ codebook may include a HARQ-ACK for a data unit received on each of one or more aggregated carriers. The data unit may be a transport block (TB) or a code block group (CBG). The Type-3 HARQ codebook may be used for HARQ-ACK transmission for aggregated carrier(s) when communication according to carrier aggregation (CA) is performed.

Two or more SPS PDSCHs may be configured. Alternatively, two or more SLIVs for the SPS PDSCH may be configured. According to method 5.2-1, when only PUCCH is transmitted, the UE may not transmit PUCCH according to HARQ-ACK. On the other hand, if "PUCCH and PUSCH are transmitted, X is derived from the first HARQ-ACK, and Y is derived from the second HARQ-ACK," the UE multiplexes HARQ-ACK(s) in each PUSCH. can

Method 5.2-4: "When the SPS PDSCH corresponds to a plurality of PUCCH resources" or "When a PUCCH resource corresponds to each SLIV derived from the SPS PDSCH", HARQ-ACK is bundling of HARQ-ACKs associated with the same SPS PDSCH (bundling) can be expressed. This operation can be illustrated in FIG. 11 .

11A is a conceptual diagram illustrating a first embodiment of a method for transmitting HARQ-ACK in PUSCH, and FIG. 11B is a conceptual diagram illustrating a second embodiment of a method for transmitting HARQ-ACK in PUSCH.

Referring to FIG. 11A , HARQ-ACK may be independently multiplexed in PUSCH. When X is ACK, the UE may not transmit PUCCH. When X is NACK, the UE may transmit PUCCH. Alternatively, when X is ACK or NACK, the UE may transmit PUCCH. When the UE transmits the PUSCH, HARQ-ACK may be multiplexed in the PUSCH. The above-described method can also be applied to Y transmission.

Referring to FIG. 11B , the method according to FIG. 11A may be applied to X transmission. Y transmission may be performed based on method 5.2-4. For example, the result of OR operation on X and Y may be included in the HARQ codebook or PUSCH. That is, when X or Y is ACK, HARQ-ACK may be ACK. When both X and Y are NACK, HARQ-ACK may be NACK.

The above-described method may be applied even when the SPS PDSCH corresponds to two or more PUCCHs. For example, HARQ-ACK is X, X+Y, X+Y+Z, ... It can be expressed as Based on this operation, the UE may repeatedly inform the base station of a reception response (eg, ACK or NACK) for one TB received in the SPS PDSCH.

Section 5.3 How to Reduce the Size of HARQ-ACK for SPS PDSCH

In order to transmit randomly arriving traffic, "configuration and/or activation of many SPS PDSCHs" or "extension of time resources of SPS PDSCHs" may be supported. Therefore, the UE needs to transmit many HARQ-ACKs. When the Type-1 HARQ codebook is used, HARQ-ACK for the PDSCH for the configured SPS may be derived. As a method for solving the above-described problem, a method for reducing some HARQ-ACKs may be required. The method proposed below can be implemented alone. Alternatively, a combination of the methods proposed below and other methods may be implemented.

Method 5.3-1: HARQ codebook may include HARQ-ACK(s) of PDSCH(s) for all serving cells (eg, all carriers) configured with RRC signaling.

Method 5.3-2: HARQ codebook may include HARQ-ACK(s) of PDSCH(s) for active serving cell (eg, active carrier).

The UE may assume a specific BWP for a deactivation serving cell (eg, a deactivation carrier), and based on the above-mentioned assumption, a HARQ codebook including the HARQ-ACK (eg, NACK) of the PDSCH may be generated. have. When the base station transmits the MAC CE for deactivating some serving cells to the terminal, the terminal may transmit a HARQ-ACK for the MAC CE. Therefore, the terminal and the base station may have the same information about the inactive serving cell. Accordingly, the UE may generate a HARQ codebook including HARQ-ACK for the active serving cell. This operation can be applied not only to the SPS PDSCH but also to the PDSCH scheduled by DCI.

The UE may select some serving cell(s) and may generate a HARQ codebook including HARQ-ACK of the PDSCH for the selected serving cell(s). This operation can be further specified in the method below.

Method 5.3-3: The UE may transmit the HARQ codebook for the corresponding serving cell using a carrier indication field (CIF) included in the DCI.

Method 5.3-4: HARQ codebook may include HARQ-ACKs of all SPS PDSCHs configured with RRC signaling.

Method 5.3-5: HARQ codebook may include HARQ-ACK(s) of PDSCH(s) received for the activated SPS.

The UE may start receiving the SPS PDSCH based on the activating DCI. Alternatively, the UE may not perform the reception operation of the SPS PDSCH based on the release DCI. When the release DCI for the SPS configuration is received, the UE may transmit a HARQ-ACK for the corresponding DCI. When activation DCI for SPS configuration is received, the UE may transmit HARQ-ACK for SPS PDSCH. Therefore, the base station and the terminal may have the same information. Accordingly, the UE may generate a HARQ codebook including HARQ-ACK for the active SPS PDSCH.

The UE may receive a TDRA including a plurality of SLIVs indicating the SPS PDSCH. Alternatively, a plurality of SPS PDSCHs may be combined, and the combined SPS PDSCHs may be configured and/or activated. In this case, the size of the HARQ-ACK may be compressed (eg, bundled) and expressed. For example, an AND operation or an OR operation on HARQ-ACK may be performed. Based on method 5.2-4, the size of HARQ-ACK can be reduced by applying an OR operation. Even in this case, there is no loss of information.

Method 5.3-6: HARQ codebook may include bundled HARQ-ACK.

When the SPS HARQ codebook for all configured SPS configs or all activated SPSconfigs is generated, HARQ-ACK for unnecessary SPS config may also be transmitted to the base station. Bundling of HARQ-ACK may cause information loss. In order to solve the above-described problem, a method for reducing the size of the SPS HARQ codebook is needed. The SPS HARQ codebook may include a HARQ-ACK for a data unit (eg, TB or CBG) received according to each of one or more SPSs. In embodiments, methods applied to the Type-3 HARQ codebook may also be applied to the SPS HARQ codebook, and methods applied to the SPS HARQ codebook may also be applied to the Type-3 HARQ codebook.

Method 5.3-7: A predetermined time window may be applied from the time of transmission of the SPS PUCCH, and the SPS HARQ codebook may include a HARQ-ACK for the SPS config belonging to the time window.

The time window may be defined in a technical specification. Alternatively, the base station may indicate the time window to the terminal using "higher layer signaling" or "a combination of higher layer signaling and active DCI". It may be desirable to reduce the size of the SPS HARQ codebook by minimizing the size of the time window. Therefore, the time window may be indicated by the DCI triggering the SPS HARQ codebook to the UE. For example, a section from a reception time of DL-DCI (eg, a slot or a subslot) to a transmission time of the SPS HARQ codebook may be interpreted as a time window. For example, the last time point of the time window may be interpreted as a transmission time of the SPS HARQ codebook, and the start time point of the time window may not be separately signaled. The UE may interpret the length of the time window based on the HARQ-ACK timing (eg, K1, slot offset, subslot offset) of the SPS PDSCH. When two or more HARQ-ACK timings are configured in the terminal, the terminal may interpret the length of the time window based on one HARQ-ACK timing among the two or more HARQ-ACK timings. For example, the HARQ-ACK timing used to interpret the length of the time window may be the largest HARQ-ACK timing among two or more HARQ-ACK timings.

Alternatively, in order to reduce the size of the SPS HARQ codebook, only the minimum HARQ-ACK may be transmitted.

Method 5.3-8: The SPS HARQ codebook may include only the HARQ-ACK that the UE has not transmitted.

The UE may not be able to transmit the PUCCH due to the slot format, the SS/PBCH block, or the Type0-PDCCH CSS set.

In the SPS HARQ codebook generation procedure, the SPS HARQ-ACK may be arranged in consideration of the following methods. The methods below can be applied to all methods of generating the SPS HARQ codebook.

Method 5.3-9: HARQ-ACKs in the SPS HARQ codebook may be arranged in the order of SPS-ConfigIndex.

Method 5.3-10: HARQ-ACKs in the SPS HARQ codebook may be arranged in a reception order of SPS PDSCH candidates.

Method 5.3-11: Can be arranged in the order of HARQ process numbers in the SPS HARQ codebook.

If the time window is large in the SPS HARQ codebook generation procedure, two or more HARQ-ACK bits may occur in SPSs having the same SPS-ConfigIndex (Method 5.3-9), or two or more SPSs having the same HPN may occur. Yes (Method 5.3 11).

Section 5.4 Priority of HARQ-ACK for SPS PDSCH

The PUCCH through which the HARQ-ACK for the SPS PDSCH is transmitted may have priority. In order to transmit other uplink control information (UCI) or TB, the UE may perform multiplexing or selection (prioritization) on PUCCH(s) and/or PUSCH(s) according to the priority of the PUCCH. This operation may be performed according to method 5.4-1 or method 5.4-2.

Method 5.4-1: The priority of the PUCCH (eg, HARQ-ACK) may be determined by RRC signaling that configures the SPS PDSCH.

The priority of the SPS PDSCH may be indicated to the UE by semi-static signaling. The priority of the SPS PDSCH may not be dynamically changed.

Method 5.4-2: The HARQ-ACK for the SPS PDSCH may follow the priority indicated by the field included in the active DCI.

When the SPS PDSCH is activated by DCI format 1_1 or format 1_2, the above-mentioned priority may be explicitly indicated. When the SPS PDSCH is activated by DCI format 1_0, the priority may be determined from a search space set in which the activated DCI is detected. For example, if the active DCI is detected in the USS set (UE-specific search space set), the priority may be interpreted as high, and if the active DCI is detected in the CSS set (common search space set), the priority is interpreted as low can be

A field included in the active DCI may indicate multiplexing between UCI or TB and HARQ-ACK having different priorities. In this case, multiplexing may be considered for not only the same priority but also different priorities in the PUCCH.

The methods proposed in Section 5.3 can be applied. In this case, in the HARQ-ACK arrangement procedure in the HARQ codebook, the first HARQ-ACK for the SPS PDSCH and the second HARQ-ACK for the PDSCH scheduled with DCI may be independently multiplexed, and the multiplexed first HARQ -ACK and the multiplexed second HARQ-ACK may be concatenated with each other.

Section 5.5 Trigger Method for SPS PUCCH

The base station may dynamically instruct the terminal to transmit the SPS PUCCH. DCI indicating transmission of the SPS PUCCH may be referred to as a triggering DCI. The triggering DCI may be a DL-DCI (eg, DCI format 1_0, DCI format 1_1, DCI format 1_2, or DCI format 2_x). Scrambling for the triggering DCI may be performed differently. A triggering DCI (eg, a cyclic redundancy check (CRC) of the triggering DCI) may be scheduled by a cell-radio network temporary identifier (C-RNTI). Alternatively, the triggering DCI may be scrambled based on method 5.5-1.

Method 5.5-1: Triggering DCI may be scrambled by configured scheduling (CS)-RNTI.

When a specific field (eg, One-shot HARQ-ACK request) included in the triggering DCI has a preset value (eg, 1), the UE may interpret that the SPS PUCCH is triggered. According to this operation, the UE can distinguish a triggering DCI, an active DCI, and a release DCI. The format of the triggering DCI may be DCI format 1_1, DCI format 1_2, or DCI format 2_x. The UE may determine that the SPS PUCCH is triggered based on a specific field included in DCI format 1_1, DCI format 1_2, or DCI format 2_x.

When the triggering DCI is DCI format 1_1, the One-shot HARQ-ACK request field may be reused.

Method 5.5-2: DCI format 1_2 may include a specific field triggering SPS PUCCH.

The triggering DCI does not need to allocate a PDSCH. Therefore, the TDRA and/or FDRA included in the triggering DCI may indicate a predetermined value, and the UE may not interpret the value indicated by the TDRA and/or FDRA as a resource of the PDSCH. Alternatively, the UE may ignore the TDRA and/or FDRA included in the triggering DCI.

Method 5.5-3: The HARQ-ACK timing indicated by the triggering DCI may be interpreted as an offset (K1) of a slot or subslot in which the SPS HARQ codebook is transmitted.

K1 may have a sufficiently large value in consideration of the processing capability of the terminal. For example, K1 may indicate a time longer than "time from the last symbol of the CORESET for which the triggering DCI is received to the symbol after the preset symbol(s)". Here, the time according to the processing capability of the terminal may be the processing time applied to the SPS PDSCH release or the Type-3 HARQ-ACK codebook.

12 is a conceptual diagram illustrating a first embodiment of a temporal relationship to be considered for generating an (improved) Type-3 HARQ codebook.

Referring to FIG. 12 , the base station may transmit a triggering DCI to the terminal. The UE may receive the triggering DCI and may generate a (improved) Type-3 HARQ codebook. In embodiments, the (improved) Type-3 HARQ codebook may mean “Type-3 HARQ codebook” or “improved Type-3 HARQ codebook”. Time may be required for the UE to decode the triggering DCI, and time may be required for the UE to generate the Type-3 HARQ codebook. It may take time for the serving base station to deliver the decoding result of the Type-3 HARQ codebook to the HARQ entity of the MAC layer.

In this case, it may be desirable for the serving base station and the terminal to derive the Type-3 HARQ codebook from the same time resource. To support this operation, a reference time resource may be introduced, and a Type-3 HARQ codebook may be derived from a reference time resource (eg, a slot or a subslot). The reference time resource may be shared between the base station and the terminal. That is, the reference time resource known by the base station may be the same as the reference time resource known by the terminal. The reference time resource may be signaled from the base station to the terminal by system information, RRC signaling, MAC CE, and/or DCI. The reason why the reference time resource is needed will be described in detail in the methods described below. For example, when a method in which the size of the Type-3 HARQ codebook is determined by activation DCI, release DCI, and/or MAC CE is applied, the reference time resource may be utilized. Here, if the time point for deriving the Type-3 HARQ codebook is not defined, a plurality of slots or a plurality of subslots may be considered, whereby the terminal and the base station can derive the Type-3 HARQ codebook of different sizes. have. In embodiments, the reference time resource may be referred to as “reference time” or “reference time”.

The reference time may be implicitly determined by the triggering DCI. Alternatively, the reference time may be defined in a technical standard. The reference time may be defined after N symbols from the last symbol at which the PDCCH (eg, triggering DCI) was received. The reference time may be defined from before B symbols from the first symbol of the PUCCH or PUSCH (eg, a channel through which the Type-3 HARQ codebook is transmitted).

Method 5.5-4: A reference time (eg, slot or subslot) for deriving a Type-3 HARQ codebook may be introduced, and the UE may derive a Type-3 HARQ codebook from the reference time. The terminal may transmit the Type-3 HARQ codebook to the base station. The base station may receive the Type-3 HARQ codebook from the terminal, may estimate that the Type-3 HARQ codebook is generated at the reference time, and may interpret the Type-3 HARQ codebook based on the reference time.

When the triggering DCI includes a downlink assignment index (DAI), the value of the DAI may indicate the size of the SPS HARQ codebook (or Type-3 HARQ codebook). For example, when the SPS HARQ codebook includes HARQ-ACK(s) for all configured SPS-ConfigIndex (Method 5.3-4), the UE may ignore the information indicated by the DAI. When the SPS HARQ codebook includes HARQ-ACK(s) for the active SPS-ConfigIndex (Method 5.3 5), the DAI may indicate the size of the SPS HARQ codebook. Even when the size of the SPS HARQ codebook is dynamically changed, the UE can know the size of the SPS HARQ codebook from the DAI included in the triggering DCI.

When the triggering DCI includes a counter DAI (cDAI), the number of SPS HARQ-ACKs may correspond to the remaining value divided by a predetermined number (eg, 2^cDAI). Additionally, when the triggering DCI includes tDAI (total DAI), the size of the SPS HARQ codebook may correspond to a remainder value divided by a predetermined number (eg, 2^tDAI).

In the triggering DCI, a priority indicator field may be activated, and the priority indicator field may indicate the priority of the PUCCH generated in the UE. When the Type-3 HARQ codebook is configured in the terminal, it may be configured in the terminal to generate the Type-3 HARQ codebook including the NDI. The UE may derive HARQ-ACK and NDI for each HPN. Alternatively, the UE may derive only HARQ-ACK for each HPN. The improved Type-3 HARQ codebook may not separately include NDI. If the UE is instructed to derive HARQ-ACK only for the active serving cell, it may not be configured that the Type-3 HARQ codebook additionally includes NDI. The HARQ codebook additionally including NDI may be introduced to solve a problem that occurs when listen before talk (LBT) fails in an unlicensed band. There may be no case in which the terminal fails the LBT in the licensed band. The case in which the terminal fails LBT in the unlicensed band supporting the semi-static access mode may be quite small.

Method 5.5-5: When the Type-3 HARQ codebook (or the improved Type-3 HARQ codebook) is generated for the active serving cell, the terminal always includes the Type-3 HARQ codebook (or the improved Type-3 HARQ codebook) that does not include NDI -3 HARQ codebook) can be generated. Alternatively, the base station may configure the terminal to generate a Type-3 HARQ codebook (or an improved Type-3 HARQ codebook) that does not include NDI.

When the serving cell operates in the unlicensed band, it may be advantageous for NDI to be included in the Type-3 HARQ codebook (or the improved Type-3 HARQ codebook). It may be unnecessary for NDI to be included in the Type-3 HARQ codebook (or the improved Type-3 HARQ codebook) in the serving cell operating in the licensed band. To support this operation, whether NDI is included in the Type-3 HARQ codebook (or the improved Type-3 HARQ codebook) for each serving cell may be independently configured.

Method 5.5-6: Based on method 5.5-5, whether or not to include NDI may be set in units of serving cells considered in the Type-3 HARQ codebook (or the improved Type-3 HARQ codebook).

Section 5.5.1 How to Trigger M SPS HARQ Codebooks

The base station may instruct (or configure) M SPS HARQ codebooks to the terminal by RRC signaling. M may be a natural number. One SPS HARQ codebook among the M SPS HARQ codebooks may be indicated to the UE by a specific field or combination of fields included in DCI. The HARQ codebook indicated by the base station may not be limited to the SPS HARQ codebook. For example, the SPS HARQ codebook may be regarded as a Type-3 HARQ codebook.

For example, according to Table 1 below, four HARQ codebooks may be triggered using two bits. The size of each HARQ codebook may not be dynamically determined. The size of each HARQ codebook may be determined by higher layer signaling (eg, RRC signaling and/or MAC signaling). In Table 1, the form of the HARQ codebook according to the value of the trigger field for the HARQ codebook may be defined.

Method 5.5-7: The length of the field indicating the one-shot HARQ-ACK request included in DCI may be increased.

If method 5.5-7 is utilized for triggering of the SPS HARQ codebook, the corresponding DCI may be scrambled by C-RNTI or MCS-C-RNTI.

In order not to increase the size of the DCI field, the HARQ codebook may be indicated by a combination of other fields included in the DCI. Some fields included in the DCI triggering the Type-3 HARQ codebook may have specific values. Alternatively, some fields included in the DCI triggering the Type-3 HARQ codebook may be reserved.

Method 5.5-8: When the one-shot HARQ-ACK request has a specific value in DCI, the reused HPN field may indicate a specific HARQ codebook.

The size of the HPN field included in DCI may have 4 bits or less than 4 bits. The bit(s) in the HPN field may be selected from most significant bit (MSB) or least significant bit (LSB), and method 5.5-7 may be applied.

In another embodiment, the UE may generate different HARQ codebooks according to the RNTI. In DCI scrambled with C-RNTI, a one-shot HARQ-ACK request may be indicated to the UE. Alternatively, a one-shot HARQ-ACK request may be indicated to the UE in DCI scrambled with CS-RNTI. When C-RNTI is used, Type-3 HARQ codebooks for all HPNs in all serving cells (eg, active carrier(s) and deactivation carrier(s)) configured for the terminal may be generated. When CS-RNTI is used, a preset HARQ codebook may be indicated to the UE. The above-described embodiment may be an embodiment according to Table 1. For example, the HARQ codebook may be an SPS HARQ codebook. The UE may generate an SPS HARQ codebook for the SPS PDSCH for the BWP in which the DCI is received.

How to interpret the time when the HARQ buffer is flushed in the procedure of Section 5.5.2 Activation and/or Deactivation of the Serving Cell

A plurality of serving cells may be configured in the terminal, and some serving cell(s) among the plurality of serving cells may be activated. The UE may identify the active serving cell(s) and/or the inactive serving cell(s) by using the bitmap included in the MAC CE. The UE may empty the HARQ buffer of the inactive serving cell(s), stop a timer (eg, sCellDeactivationTimer and/or bwp-InactivityTimer), and suspend SPS and/or CG (configured grant) can do.

When the PDSCH including the MAC CE is received, the reflection time of the terminal may be defined in the technical standard. When activation of the serving cell is indicated, operations related to CSI reporting and timers may be distinguished from operations other than the corresponding operation. For the last slot n in which the PDSCH is received, the UE may perform deactivation and/or activation of serving cells according to the instruction of the MAC CE. To support this operation, the technical standard may define a preset time for the terminal to change the state of the serving cell. The UE may change the state of the serving cell before the preset time elapses. The base station may check whether decoding of the PDSCH is successful based on the HARQ-ACK received from the terminal (eg, HARQ-ACK in slot n+m). Therefore, depending on the time when the terminal transmits the HARQ-ACK to the base station and the above-described preset time, the state of the serving cell may not be clearly defined.

13 is a conceptual diagram illustrating a reception time of a MAC CE for changing a state of a serving cell and a time taken to reflect the MAC CE.

에 의해 결정될 수 있다.

은 하나의 서브프레임에 속한 슬롯의 개수일 수 있다. μ는 HARQ-ACK이 전송되는 PUCCH에 적용된 μ일 수 있다. PUCCH의 전송 시점으로부터 3ms 이후의 첫 번째 슬롯은 k에 대응될 수 있다. 슬롯 n+k에서 MAC CE의 복호의 성공 후에 서빙 셀의 상태 변환을 위한 충분한 시간이 지난 것으로 판단될 수 있다. 슬롯 n+j와 슬롯 n+k 간의 선후 관계에 따라 단말의 동작 및/또는 서빙 셀의 상태는 기지국의 해석과 다를 수 있다.Referring to FIG. 13 , a preset time allowed for the terminal may occur in slot n+j. The slot n+k may be the first slot 3 ms after the slot n+m in which the HARQ-ACK for the PDSCH is transmitted. The value of k is

can be determined by

may be the number of slots belonging to one subframe. μ may be μ applied to PUCCH on which HARQ-ACK is transmitted. The first slot 3 ms after the PUCCH transmission time may correspond to k. After the successful decoding of MAC CE in slot n+k, it may be determined that sufficient time has elapsed for state transformation of the serving cell. According to the precedence relationship between the slot n+j and the slot n+k, the operation of the terminal and/or the state of the serving cell may be different from the interpretation of the base station.

In the first case, slot n+j may occur first, and slot n+k may occur after slot n+j. Although the UE must complete the state change of the serving cell in slot n+j, a logical error may occur because slot n+j is located before slot n+k. The base station should not cause such a case, and may instruct the terminal not to be too late for the value of k (eg, feedback of HARQ-ACK).

In the second case, slot n+k may occur first, and slot n+j may occur after slot n+k. The UE may not change the state of the serving cell until slot n+k-1. slot n+k, slot n+k+1, ... , the state of the serving cell in slot n+j-1 may or may not be changed. This operation may be determined by the implementation of the terminal. slot n+j, slot n+j+1, ... In , the state of the serving cell may not be changed. Therefore, slots in which the state of the serving cell is not conclusive may occur. Slots in which the state of the serving cell is not conclusive are slot n+k, slot n+k+1, ... , slot n+j-1.

The state change of the serving cell may be completed from a specific slot among the above-described slots. The UE may perform an operation according to the activation state for the activated serving cell and may perform an operation according to the deactivated state for the deactivated serving cell.

In an exceptional case, an operation related to CSI reporting and sCellDeactivationTimer may be performed in a reference slot. The UE may perform operations related to CSI reporting for an active serving cell in slot n+k. The UE may not perform CSI reporting for the inactive serving cell in slot n+k, and CSI reporting in the first slot (eg, slot after slot n+k) activated for a serving cell that will be activated soon. related operations may be performed. An operation for sCellDeactivationTimer may be considered to be performed in slot n+k.

When the serving cell is deactivated, the UE may perform an operation of emptying the HARQ buffer. However, in slots in which the status of the serving cell is not conclusive (eg, slot n+k, slot n+k+1, ..., slot n+j-1), the status of one serving cell is determined by the terminal and the base station. can be considered as different states.

According to the instruction of the base station, the terminal may generate the (improved) Type-3 HARQ codebook. For example, the UE may select some serving cell(s) and may generate a Type-3 HARQ codebook including HARQ-ACK(s) for the selected serving cell(s). When only the active serving cell is to be selected, the state of the serving cell known by the terminal must be the same as the state of the serving cell known by the base station.

Method 5.5-9: When the (improved) Type-3 HARQ codebook is generated only for an active serving cell (eg, an active carrier), the terminal checks the HARQ buffer for the inactive serving cell (eg, an inactive carrier) It can be empty based on a predetermined slot t.

An operation for CSI reporting and/or sCellDeactivationTimer may or may not be performed based on slot n+k depending on the state of the serving cell. Therefore, the operation on the HARQ buffer may also be performed in a predetermined slot t (eg, t=n+k). In addition, when generating the (improved) Type-3 HARQ codebook in slot t (eg, when slot t is the reference time), the state of the HARQ buffer may be determined. The base station may inform the terminal of the time (eg, slot t) to empty the HARQ buffer for the inactive serving cell (or the inactive SPS) using system information, RRC signaling, MAC CE, and/or DCI. Alternatively, the time (eg, slot t) to empty the HARQ buffer for the inactive serving cell (or the inactive SPS) may be predefined in a technical standard.

Method 5.5-10: In method 5.5-9, it may be assumed that the flush of the HARQ buffer occurs in slot n+k.

If the (improved) Type-3 HARQ codebook generation time (eg, reference time) is slot t or a section including slot t, if the serving cell is assumed to be deactivated, the information of HARQ-ACK becomes meaningless may be If only the active serving cell is considered, HARQ-ACK information for the corresponding serving cell may be omitted. In the former case in which the HARQ buffer is emptied, HARQ-ACK information may be filled with a fixed value (eg, NACK or ACK). In the latter case except the deactivation serving cell, HARQ-ACKs equal to the number of HPNs configured in the deactivation serving cell may not be included in the HARQ codebook. When "inactive serving cell is activated and method 5.5-9 is applied", HPN with HARQ-ACK set to a fixed value (eg, NACK or ACK) may exist. The reason is that since PDSCH is not received in any HPN, the UE may generate HARQ-ACK having an arbitrary value, but a fixed value is defined in the technical standard.

Section 5.6 How to Create SPS HARQ Codebook

HARQ-ACK for SPS PDSCH may be transmitted in SPS PUCCH or PUSCH. The SPS PUCCH may include a HARQ codebook for the SPS PDSCH. The SPS HARQ codebook may mean a HARQ codebook consisting of only HARQ-ACK for the SPS PDSCH.

A method of disposing HARQ-ACK in the SPS HARQ codebook will be described. When two or more SPS configs are configured, SPS-ConfigIndex may be assigned. All or part of two or more SPS configs may be activated. All or part of two or more SPS configs may be canceled.

The size of the SPS HARQ codebook may be set by RRC signaling. Alternatively, according to an indication of DCI, the SPS HARQ codebook may include only a small number of HARQ-ACK bits.

In the SPS HARQ codebook, HARQ-ACK may be arranged in the order of the SPS config configured in the terminal (eg, SPS-ConfigIndex).

In one method, SPS HARQ codebooks for all SPS configs indicated to the UE by RRC signaling may be generated.

Since the number of SPS configs configured in the terminal is determined by RRC signaling, when only a small number of SPS configs are activated, the size of the SPS HARQ codebook may be unnecessarily large. Therefore, a method for reducing the size of the SPS HARQ codebook may be required.

Alternatively, the SPS HARQ codebook for the activated SPS config among the SPS configs indicated to the UE by RRC signaling may be generated.

The UE may generate the SPS HARQ codebook in the order of SPS-ConfigIndex for the activated SPS config. Some SPS configs may be activated or deactivated, some SPS configs may be activated, and some SPS configs may be deactivated. In this case, the terminal and the base station should be able to interpret the state of the SPS config (eg, an active state or an inactive state) as the same state.

When activation DCI (eg, activation DCI for SPS configuration) is received, the UE may not transmit an ACK for activation DCI to the base station. The UE may receive the SPS PDSCH and may transmit a HARQ-ACK for the SPS PDSCH to the base station. In a procedure in which the base station instructs the terminal to transmit the SPS HARQ codebook, when some SPS configs are activated, a time point at which the state of the SPS config can be interpreted as the same state may be defined.

After a predetermined processing time required for decoding from the time of reception of the active DCI, the UE can expect to receive a certain SPS PDSCH. When the SPS HARQ codebook needs to be transmitted at the request of the base station, the UE may consider that the HARQ-ACK for the corresponding SPS config is included in the SPS HARQ codebook. Before the preset processing time elapses, it may be considered that the UE has not decoded the activated DCI, and it may be considered that the corresponding SPS config is not activated in the SPS HARQ codebook.

When the release DCI (eg, release DCI for SPS configuration) is received, the UE may transmit an ACK for the release DCI to the base station. When the base station cancels some SPS config, a time point at which the state of the corresponding SPS config can be interpreted as the same state may be defined. Since the base station can select a time for receiving the ACK for the release DCI, it can be assumed that the terminal can transmit the PUCCH including the ACK. For example, when the PUCCH cannot be transmitted in a certain slot according to the slot format, the base station may transmit a release DCI to the terminal to transmit the PUCCH in a valid slot.

In this case, in order to transmit the SPS HARQ codebook, the states (eg, activated and/or deactivated) of SPS configs (SPS-ConfigIndex) to be included in the SPS HARQ codebook may be made clear.

In the SPS HARQ codebook, HARQ-ACK may be arranged in the order of HPNs indicated to the UE. The HPN may be determined by the time and/or offset at which the SPS PDSCH is received. The HPN may be calculated as a function of a slot in which the SPS PDSCH is received, the maximum value of HPN, and/or an offset indicated by RRC signaling.

Different SPS PDSCHs belonging to one SPS config may have the same HPN. Alternatively, SPS PDSCHs belonging to two or more SPS configs may have the same HPN. In this case, since the UE maps only one HARQ-ACK to the HPN, one SPS PDSCH may be selected by the UE.

Method 5.6-1: The UE may use HARQ-ACK for a temporally late SPS PDSCH among SPS PDSCHs having the same HPN.

Method 5.6-2: The UE may use HARQ-ACK for the SPS PDSCH having the lowest SPS-ConfigIndex among SPS PDSCHs having the same HPN.

In the method to be described later, a method of generating an SPS HARQ codebook using only some SPSs will be specifically described.

When Section 5.6.1 SPS HARQ codebook includes only HARQ-ACK for activated SPS, time to reflect activation DCI and/or release DCI

In one BWP, a plurality of SPSs may be configured in the terminal, and some SPS(s) among the plurality of SPSs may be activated. Therefore, when the SPS HARQ codebook includes only the HARQ-ACK for the activated SPS, the time point at which the activated DCI and/or the released DCI is reflected between the UE and the base station should be promised.

14 is a conceptual diagram illustrating a reception operation of an activated DCI and a time at which the activated DCI is reflected.

Referring to FIG. 14 , the base station may instruct the terminal to receive the SPS PDSCH by using the active DCI. The UE may receive the activated DCI and may not perform a separate operation for the activated DCI. The UE may receive the SPS PDSCH, may generate a HARQ-ACK for the SPS PDSCH, and may transmit the HARQ-ACK to the base station.

The UE may receive an active DCI, may receive an SPS PDSCH, and may transmit a HARQ-ACK for the SPS PDSCH to the base station. The base station may recognize the HARQ-ACK as ACK or NACK for a preset time (eg, Δ). When ACK or NACK is received from the base station, the corresponding SPS may be considered activated. However, the base station may not know the state of the corresponding SPS before checking the ACK or NACK.

15 is a conceptual diagram illustrating a reception operation of a release DCI and a time at which an activation DCI is reflected.

Referring to FIG. 15 , the UE may receive the release DCI and may transmit the HARQ-ACK for the release DCI to the base station. The base station may recognize the HARQ-ACK as ACK or NACK for a preset time (eg, Δ). When ACK or NACK is received from the base station, the corresponding SPS may be considered to be deactivated. However, the base station may not know the state of the corresponding SPS before checking the ACK or NACK.

For the SPS HARQ codebook, the state of the SPS (eg, activation or deactivation) needs to be checked, so a reference time needs to be determined between the terminal and the base station. In the proposed method, the time at which activation and/or deactivation of the SPS PDSCH is recognized by the base station may be set as a boundary, and it may be assumed that the state of the corresponding SPS does not change before the boundary. In order to support this operation, a preset time (eg, Δ) from the time when the HARQ-ACK is received by the base station to the time when the result of the HARQ-ACK is reflected may be defined. The preset time may be indicated to the UE by system information, RRC signaling, MAC CE, and/or control information. Alternatively, the preset time may be defined in a technical standard. The reference time for generation of the (improved) Type-3 HARQ codebook or the SPS HARQ codebook may be after a predetermined time (eg, Δ).

Method 5.6-3: A preset time from the time of decoding the HARQ-ACK related to the SPS to the time at which the decoding result is reflected in the base station may be defined in the technical specification. Alternatively, the preset time may be indicated to the UE by system information, RRC signaling, MAC CE, and/or control information.

When the UE receives a triggering DCI triggering the (improved) Type-3 HARQ codebook or SPS HARQ codebook, the size of the (improved) Type-3 HARQ codebook or SPS HARQ codebook depends on the time at which the corresponding HARQ codebook is triggered. can be different. When the active DCI is received, the UE may transmit a HARQ-ACK for the first SPS PDSCH, and a slot or symbol after a preset time may become a boundary. When the release DCI is received, the UE may transmit a HARQ-ACK for the release DCI, and a slot or symbol after a preset time may become a boundary.

The preset time may vary depending on the processing capability of the terminal. For example, the base station may receive the processing capability information of the terminal, and in consideration of the processing capability of the terminal, processing capability 1 or processing capability 2 may be set in the terminal using RRC signaling. . Alternatively, when there is no configuration by RRC signaling, processing capability 1 may be considered to be used. When processing capability 2 is used, the base station may set processing capability 2 to the terminal by using RRC signaling.

The preset time may be defined in units of symbols. The preset time may be determined by a combination of subcarrier intervals used in DL BWP and/or UL BWP in which the UE operates.

The base station may transmit the triggering DCI to the terminal, and the terminal may receive the triggering DCI on the PDCCH. After a preset time (eg, N symbols) from the next symbol of the last symbol of the PDCCH, the UE may generate the SPS HARQ codebook by using the HARQ-ACK corresponding to the HPN. Therefore, the UE may derive the HARQ-ACK for the activated SPS or the deactivated SPS according to the time of generating the SPS HARQ codebook.

It may be indicated that the (improved) Type-3 HARQ codebook or the SPS HARQ codebook does not include NDI. Alternatively, whether the (improved) Type-3 HARQ codebook or the SPS HARQ codebook includes NDI may be interpreted differently for each serving cell.

Section 5.6.2 When the HARQ-ACK for the configured SPS is included in the SPS HARQ codebook, one or more SPSs may be configured in the UE by RRC signaling. The UE may receive a PDSCH according to the active SPS among one or more SPSs, and reports the HARQ-ACK for the received PDSCH to the base station. When the SPS HARQ codebook (or (improved) Type-3 HARQ codebook) is triggered to the UE, the UE may derive HARQ-ACK(s) for all configured SPS(s), and HARQ-ACK(s) It is possible to generate an SPS HARQ codebook including In this case, the SPS HARQ codebook may include HARQ-ACK for inactive SPS as well as HARQ-ACK for activated SPS.

The UE may derive the HARQ-ACK for the activated SPS PDSCH, and when the release DCI (eg, the release DCI for the SPS configuration) is received, the HARQ-ACK for the release DCI may be derived, and the deactivation SPS It is possible to derive NACK or ACK for .

For the active SPS, the HPN related to the SPS PDSCH may be determined based on a time resource in which the corresponding SPS PDSCH is received, a formula defined in a technical standard, and/or an HPN offset set by RRC signaling. When the SPS HARQ codebook includes only the configured SPS, the UE may place the HARQ-ACK in the SPS HARQ codebook according to the order of HPNs received in the SPS PDSCH (eg, ascending or descending order).

HPNs derived from SPSs may not always be contiguous. Even when some missing HPNs exist, the UE may derive the SPS HARQ codebook by arranging HARQ-ACKs in the order of HPNs associated with the SPS PDSCH.

Alternatively, the UE may derive the SPS HARQ codebook by disposing the HARQ-ACKs in the order (eg, ascending or descending order) of identifiers (or indexes) included in the SPS config.

Generation of the SPS HARQ codebook not including NDI may be instructed to the UE. Alternatively, the above-mentioned indication may be interpreted differently for each serving cell.

Section 5.7 HARQ-ACK Timing Change Method

The transmission time resource of the SPS PUCCH including the HARQ-ACK for the SPS PDSCH may be indicated to the UE by active DCI and/or higher layer signaling. In a TDD system or a system supporting an unlicensed band, the PUCCH resource through which the HARQ-ACK is transmitted may not always be utilized. In the TDD system, since the SPS PUCCH may be transmitted in a UL symbol, the UE may not transmit the PUCCH in a symbol other than the UL symbol (eg, a DL symbol or a FL symbol). In the system supporting the unlicensed band, "if the terminal does not acquire the COT", "when the COT is not shared with the terminal", or "when the PUCCH resource includes a symbol belonging to the idle period", the terminal may not transmit PUCCH.

In the TDD system, the slot pattern may be indicated to the UE by RRC signaling and/or DCI. A slot pattern having a specific period may be indicated, and a pattern of DL, UL, and/or FL symbols may be indicated to the UE. Some of the FL symbols indicated by RRC signaling may be changed (or confirmed) to DL, UL, or FL symbols through a specific DCI (eg, DCI format 2_0).

The UE may perform a reception operation of a DL signal/channel or a transmission operation of a UL signal/channel in a semi-static FL symbol according to configuration or scheduling. Alternatively, the UE may not perform a periodic reception operation or a periodic transmission operation on a semi-static FL symbol. For example, a symbol receivable by the SPS PDSCH may be a semi-static DL symbol. For example, a symbol capable of transmitting PUCCH including SPS HARQ-ACK may be limited to a semi-static UL symbol. Since UL signals/channels allocated to DCI can be multiplexed, in a transmission procedure involving DCI, UL signals/channels can be transmitted even in semi-static FL symbols.

Communication in the unlicensed band may be performed in a frame based equipment (FBE) scheme. In this case, the UE cannot transmit the UL signal/channel in the idle period. The UE may derive the idle period by a specific DCI (eg, DCI format 2_0) or an implicit method. For a fixed frame period (FFP) initiated by the terminal, the corresponding terminal may not be able to perform a transmission operation in the idle period. For the FFP initiated by the base station, the corresponding base station may not be able to perform the transmission operation in the idle period.

If the SPS PUCCH is not expected to be valid, the base station may not transmit the SPS PDSCH. If the SPS PUCCH is not expected to be valid, the UE may not transmit the SPS PUCCH (eg, SPS HARQ-ACK). When the SPS PDSCH is not transmitted, the base station may transmit DCI to the terminal to schedule the PDSCH having a valid PUCCH. In order to perform the above-described operation in the unlicensed band, the base station may secure the COT. Alternatively, the COT may be shared with the base station. If the COT is not secured or shared, the base station may not be able to transmit the PDCCH. In the proposed method, when the time resource (eg, transmission time resource) of the SPS PUCCH for the SPS PDSCH is changed in a predetermined method, the base station may transmit the SPS PDSCH without additional transmission of the DCI.

Method 5.7-1: If it is determined that the time resource of the SPS PUCCH is not valid, the UE may consider the time resource of the SPS PUCCH (or the timing of HARQ-ACK) as a non-numerical value K (NNK).

When generation of the Type-2 HARQ codebook is instructed to the terminal, the PDSCH may be divided into two groups, and a field included in the scheduling DCI may indicate a PDSCH group index. The UE may generate a HARQ codebook (eg, Type-2 HARQ codebook) for each PDSCH group index. The UE may map only the HARQ codebook having the same PDSCH group indexes on the PUCCH according to the scheduling DCI. Alternatively, the UE may map HARQ codebooks having different PDSCH group indices on the PUCCH according to the scheduling DCI.

The UE may consider the HARQ-ACK to be transmitted on the SPS PUCCH as NNK. In this case, HARQ-ACK (eg, NNK) may be multiplexed in the HARQ codebook for the PDSCH group to which the SPS PDSCH belongs. This may mean that the time resource of the PUCCH in which the NNK is transmitted is not determined.

16 is a conceptual diagram illustrating a first embodiment of a method of changing a time resource (eg, feedback timing) of a PUCCH for an SPS PDSCH.

Referring to FIG. 16 , the timing (eg, feedback timing) of HARQ-ACK may be changed based on method 5.7-1. The HARQ-ACK for the SPS PDSCH may not be transmitted in the SPS PUCCH, and the base station may instruct the terminal to transmit the HARQ codebook having the same PDSCH group index as the SPS PDSCH.

Alternatively, the PDSCH group to which the SPS PDSCH belongs may not be predefined. If the SPS HARQ-ACK is not transmitted in the SPS PUCCH, the corresponding SPS HARQ-ACK may be transmitted in the first PUSCH or the first PUCCH that occurs later. In this case, for the PDSCH group(s), the SPS HARQ-ACK may belong to any one PDSCH group, and may be concatenated with another HARQ-ACK in the PDSCH group (append or prepend). That is, the SPS HARQ-ACK may be mapped to the corresponding PDSCH group. In this case, when two PDSCH groups are configured, the HARQ-ACK bit string for each PDSCH group may be concatenated, and the SPS HARQ-ACK may be included in any one HARQ-ACK bit string.

Alternatively, the SPS HARQ-ACK may not belong to the PDSCH group. Therefore, after the HARQ codebook is generated, the SPS HARQ-ACK may be concatenated and mapped with the corresponding HARQ codebook. In this case, after the HARQ-ACK bit stream for the PDSCH group is concatenated, the SPS HARQ-ACK may be concatenated.

In a communication system supporting a licensed band, the PDSCH group may not be defined. At this time, the SPS PUCCH with NNK may be interpreted as being transmitted in the (sub)slot having the first PUSCH or PUCCH valid for the UE. For example, the terminal may receive from the base station one value indicating the offset of the (sub)slot in which the SPS PUCCH is transmitted. When the SPS PUCCH cannot be transmitted at the time indicated by the base station, the UE may multiplex the SPS HARQ-ACK on the first PUSCH or PUCCH. If the corresponding PUSCH or PUCCH is not indicated, the UE may transmit the previous SPS HARQ-ACK in the PUCCH for the received SPS PDSCH again.

In the TDD system, the UE may apply only a semi-static slot pattern to determine the transmission possibility of the SPS PUCCH. That is, the UE may operate without dependence on DCI format 2_0. Therefore, the terminal belongs to "symbols indicated by semi-static DL", "symbols belonging to SS/PBCH block", "Type-0-PDCCH CSS set", and/or "CORESET associated with Type-0-PDCCH CSS set". SPS PUCCH may not be transmitted in "symbol".

Method 5.7-2: In the TDD system, the terminal is "a symbol indicated by quasi-static DL", "a symbol belonging to an SS/PBCH block""Type-0-PDCCH CSS set", and/or "Type-0-PDCCH" PUCCH including SPS HARQ-ACK bit(s), SR, and/or CSI may not be transmitted in "symbols belonging to CORESET related to CSS set".

A symbol in which the SPS PUCCH may be transmitted may include at least a semi-static UL. In addition, the symbols in which the SPS PUCCH can be transmitted may also include some semi-static FL symbols. The reason is that if the symbol in which the SPS HARQ-ACK is transmitted is limited to only the semi-static UL symbol, the transmission of the SPS PUCCH is limited. In order to secure a high transmission amount, a part of the quasi-static FL symbol may be utilized. In order to support this operation, it may be desirable for the base station to perform RRC signaling to the terminal.

Method 5.7-3: In method 5.7-2, the base station indicates "information indicating from which quasi-static DL symbol to which quasi-static FL symbol is invalid" or "indicates from which quasi-static FL symbol is valid" information can be informed to the terminal using RRC signaling.

According to the slot pattern indicated to the UE, quasi-static DL symbols may be deployed first, quasi-static FL symbols may be deployed after that, and then quasi-static UL symbols may be deployed. A method in which the SPS PUCCH indicates a transmittable symbol to the UE may be divided into a "method of informing the boundary of an invalid symbol" or a "method of informing the boundary of a valid symbol".

In the method of notifying the boundary of an invalid symbol, the base station may inform the terminal up to which quasi-static FL symbols are invalid according to method 5.7-3. For example, when the base station indicates n to the terminal, the terminal cannot transmit the SPS PUCCH in n consecutive symbols from a semi-static FL symbol arranged consecutively with a semi-static DL symbol. n may be a natural number.

In the method of notifying the boundary of a valid symbol, according to method 5.7-3, the base station may inform the terminal from which quasi-static FL symbols are valid. For example, when the base station indicates n to the terminal, the terminal may transmit the SPS PUCCH from the first semi-static FL symbol consecutively arranged with the last semi-static DL symbol to the nth FL symbol. n may be a natural number.

A valid symbol or an invalid symbol indicated to the UE may be equally applied to not only the SPS PUCCH but also the PUSCH. To support this operation, the following method may be considered.

Method 5.7-4: In method 5.7-3, in order to indicate to the UE the semi-static FL symbol in which the SPS PUCCH cannot be transmitted, the RRC parameter (eg, numberOfInvalidSymbolsForDL-UL-Switching) applied to the PUSCH may be applied as it is. have. Alternatively, a new RRC parameter to which the same value is applied may be introduced.

As another method proposed to represent the time resource for transmitting the SPS PUCCH, two or more (sub)slot offsets for transmitting the SPS PUCCH may be considered. Since the UE transmits the SPS PUCCH only once, one (sub) slot offset may be selected from among two or more (sub) slot offsets.

Method 5.7-5: Two or more (sub)slot offsets may be indicated to the UE, and the UE may select the smallest valid value among the two or more (sub)slot offsets to transmit the SPS PUCCH.

According to the SPS-Config configured for the terminal, the resource of the PUCCH can be indicated, and a set of (sub)slot offsets of the PUCCH (eg, dl-DataToUL-ACK, dl-DataToUL-ACK based RRC parameters ( s), K1 set) can be considered. One value may be indicated to the UE by the activation DCI, and the (sub)slot in which the SPS PUCCH is transmitted may be determined. Therefore, in consideration of a subset consisting only of values larger than the value indicated by the active DCI, the UE may select the smallest value to which the SPS PUCCH can be transmitted from the corresponding subset.

When the terminal cannot find the above-mentioned value (eg, "if the corresponding subset is empty" or "when all elements of the subset indicate only invalid SPS PUCCH"), the terminal drops the SPS PUCCH )can do. Alternatively, the UE may multiplex SPS HARQ-ACK on PUSCH or PUCCH appearing later than the largest value among elements of the subset.

For example, the K1 set may have 16 values. In the active DCI, an arbitrary value (eg, a fourth value) belonging to the K1 set may be used. The UE may not be able to transmit the SPS PUCCH based on the fourth value. In this case, the UE may select the smallest value capable of transmitting the SPS PUCCH from among values greater than the fourth value in the K1 set. The corresponding value may be obtained from the K1 set. Alternatively, if the SPS PUCCH cannot be transmitted in all values belonging to the K1 set, the UE may select the initial PUCCH or PUSCH to transmit the SPS PUCCH at a value larger than the corresponding value, and the SPS HARQ- ACK can be multiplexed.

Section 5.7.1 How to change the timing of the SPS PUCCH to the first UL channel transmitted by the UE

According to the period of the SPS PDSCH, the period of the TDD slot, and/or the period of the FFP, the timing of the SPS PUCCH may be changed. The timing of the SPS PUCCH may be changed or deferred to a specific timing. According to the above-described methods, when the base station transmits a separate DCI, the SPS HARQ-ACK may be transmitted.

In a (sub)slot in which PUCCH or PUSCH can be transmitted, the UE may multiplex SPS HARQ-ACK and/or other UCI types. UCIs corresponding to different priorities (eg, eMBB or URLLC) may be multiplexed according to an indication and/or configuration of a base station.

If there is a deferred SPS HARQ-ACK, one PUCCH resource may be determined in consideration of the deferred SPS HARQ-ACK, SPS HARQ-ACK, and/or other UCIs. When the UE transmits a PUSCH, UCI may be multiplexed in the corresponding PUSCH. In the multiplexing procedure, some UCIs may be dropped.

Transmission of PUCCH and/or PUSCH may not be allowed according to a slot pattern, an invalid symbol, or a valid symbol. In this case, the UE may drop UCI and/or UL-SCH (or TB) excluding SPS HARQ-ACK. The SPS HARQ-ACK may include both the already deferred SPS HARQ-ACK and the first deferred SPS HARQ-ACK in the corresponding (sub)slot.

The UE may multiplex the SPS PUCCH in the first UL transmission. One or more SPS PUCCHs may be changed at the same timing. In this case, the PUCCH resource to be applied by the UE may be applied differently depending on the amount of HARQ-ACK (eg, the number of SPS PUCCHs).

Method 5.7-6: When the UE fails to transmit the SPS PUCCH, the corresponding SPS HARQ-ACK may be multiplexed in the first PUCCH or PUSCH transmitted after the SPS PUCCH.

The base station may allocate and/or activate the initial PUCCH or PUSCH using DCI. Alternatively, the base station may allocate the initial PUCCH or PUSCH using RRC signaling. For example, the PUCCH may be a PUCCH transmitting HARQ-ACK for a PDSCH allocated in a separate DL-DCI. Alternatively, PUCCH or PUSCH may have the same SPS-configIndex or different SPS-configIndex as the SPS HARQ-ACK for the SPS PDSCH. For example, the PUSCH may be a PUSCH allocated in a separate UL-DCI, a type 1 CG PUSCH, or a type 2 CG PUSCH. Here, the initial PUCCH may refer to a PUCCH having a time resource of the next (sub) slot of the (sub) slot to which the SPS PUCCH is to be transmitted or a subsequent (sub) slot. The initial PUSCH may mean a PUSCH having a time resource of a next (sub) slot or a subsequent (sub) slot in which the SPS PUCCH is to be transmitted.

Since the base station knows all of the TDD slot pattern, the time resource of the SPS PDSCH, and the time resource of the SPS PUCCH, it can know the first UL channel of the terminal. The UE may multiplex SPS HARQ-ACK on the first UL channel. When the timing of the SPS PUCCH is changed, the corresponding SPS HARQ-ACK may be multiplexed on another PUCCH or another PUSCH. In this case, since the amount of HARQ-ACK is changed, a method for indicating the changed amount of HARQ-ACK to the UE may be required.

The PUCCH resource index included in the SPS-config may indicate a resource for one HARQ-ACK bit. When the previously changed SPS HARQ-ACK is further multiplexed in the feedback timing, the SPS PUCCH may include two or more bits. To support this operation, the base station may indicate a separate PUCCH resource index to the terminal.

A payload may be determined according to the number of SPS HARQ-ACKs to be transmitted in the same PUCCH or the same HARQ codebook, and a PUCCH resource list for the corresponding payload may be indicated to the UE through RRC signaling. The UE may determine the PUCCH resource set according to the number of SPSs (eg, SPS-configIndex), and may determine the PUCCH resource by applying the PUCCH resource index indicated by the base station. Here, SPS HARQ-ACKs belonging to the HARQ codebook may have different SPS-configIndexes.

In another embodiment, SPS HARQ-ACKs having the same SPS-configIndex may be multiplexed in one HARQ codebook. Here, the HARQ codebook may be a Type-1 HARQ codebook, a Type-2 HARQ codebook, a Type-3 HARQ codebook, or an SPS HARQ codebook.

The UE may generate the HARQ codebook for the PUCCH that has not been transmitted due to the pattern of the TDD slot, and may multiplex the HARQ codebook on the first UL channel after the PUCCH that has not been transmitted. This operation may be embodied in the following methods.

Method 5.7-7: In the procedure of generating the Type-1 HARQ codebook, the UE may consider the order of time of the PUCCH. The UE may apply the K1 value for the actually transmitted SPS PDSCH instead of the untransmitted SPS PDSCH.

Consequently, in method 5.7-7, the order of time of the PUCCH may be the order of the (sub)slots in which the SPS PDSCH is received. The reason is that the value of K1 of the SPS PDSCH may be the same. PDSCH candidate(s) included in the Type-1 HARQ codebook may be referred to as MA _,c . When the HARQ-ACK for the changed timing is included in the Type-1 HARQ codebook, the HARQ-ACK(s) that were not transmitted for _the SPS PDSCH(s) are also included in the Type-1 HARQ codebook. The size of the set may be further increased.

For example, periodic repetition of DSUUU, which is a slot pattern, may be indicated (or configured) to the UE by RRC signaling. In this case, the SPS PDSCH may be activated, the period of the SPS PDSCH may be 4 slots, and the HARQ-ACK feedback timing may be indicated to the UE in 2 slots. Among the slot patterns, D may be a DL slot and U may be a UL slot. In S among the slot patterns, PDSCH may not be received and PUCCH may not be transmitted. The K1 set utilized by the UE may be assumed to be {2, 4} slots. Here, the slot may be interpreted as a sub-slot.

17 is a conceptual diagram illustrating a first embodiment of a method for changing a feedback timing of HARQ-ACK for an SPS PDSCH.

Referring to FIG. 17 , the HARQ codebook may be considered in one specific slot n. In the TDD system, the UE may consider the PDSCH received in slots n-2 and n-4. Considering the SPS PDSCH, the UE may derive HARQ-ACKs for the PDSCH received in the slot {n-4, n-2}. The derived HARQ-ACKs may be arranged in the PUCCH of slot n according to the reception order of the PDSCH. That is, the derived HARQ-ACKs may be included in the HARQ codebook. The UE cannot transmit the HARQ-ACK for the PDSCH received in slot n-6. The reason is that the PUCCH for the corresponding HARQ-ACK should be transmitted in slot n-4, but slot n-4 is a DL slot.

According to method 5.7-6, since the SPS HARQ-ACK for the SPS PDSCH received in slot n-6 cannot be transmitted in the PUCCH of slot n-4, the terminal selects a slot in which PUCCH transmission is possible after slot n-4. can be found A slot in which PUCCH transmission is possible may be regarded as slot n. According to method 5.7-7, the time order between the PDSCH received in slot n-6 and PDSCHs received in slot {n-4, n-2} may be considered. The UE may generate the HARQ codebook by arranging HARQ-ACKs for PDSCHs received in the slot {n-6, n-4, n-2} in order, and the HARQ codebook is to be transmitted in the PUCCH of the slot n. can

When the SPS-configIndex is configured according to the pattern of the TDD slot, the procedure for determining whether the SPS PDSCH is received in a valid time resource may be modified. If the SPS PDSCH for the SPS-configIndex is not received in a valid time resource, the UE may not generate an SPS HARQ-ACK. Alternatively, in this case, the UE may fix the SPS HARQ-ACK to NACK. In addition, when the timing of the SPS PUCCH is changed, the UE may generate the SPS HARQ-ACK in consideration of the changed timing, and may generate the HARQ codebook by disposing the SPS HARQ-ACK in the order of reception of the SPS PDSCH, and the HARQ codebook may be transmitted on PUCCH or PUSCH. This operation can be expressed in method 5.7-8 below. Method 5.7-8 may be applied in a Type-1 SPS HARQ codebook or a Type-2 SPS HARQ codebook.

Method 5.7-8: For a given SPS-configIndex, two or more HARQ-ACKs may be placed in the SPS HARQ codebook. The SPS HARQ codebook may include a HARQ-ACK (eg, deferred HARQ-ACK) for an SPS PDSCH associated with an invalid SPS PUCCH resource.

When the timing of the SPS PUCCH is changed from (sub) slot m to (sub) slot n, one or more HARQ-ACKs may be deployed according to SPS-ConfigIndex in the SPS HARQ codebook transmitted in (sub) slot n, and one or more The arrangement order of the HARQ-ACKs may be the reception order of the SPS PDSCH(s). The SPS HARQ-ACK to be transmitted in the (sub)slot m and the SPS HARQ-ACK to be transmitted in the (sub)slot n may be concatenated, and then a loop considering the SPS-ConfigIndex may be performed outside.

As another proposed method, the SPS HARQ-ACK in the SPS HARQ codebook may be arranged in a different manner.

Method 5.7-9: In the procedure of generating the Type-1 SPS HARQ codebook, the UE can separately generate the SPS HARQ codebook that was intended to be transmitted for the corresponding SPS-configIndex, and the deferred SPS HARQ codebook and the SPS to be transmitted this time One HARQ codebook can be generated by concatenating the HARQ codebooks.

Method 5.7-10: In the procedure of generating the Type-2 SPS HARQ codebook, the UE can separately generate the SPS HARQ codebook that was intended to be transmitted for the corresponding SPS-configIndex, and the deferred SPS HARQ codebook and the SPS to be transmitted this time By concatenating HARQ codebooks, one HARQ codebook can be generated.

The timing of the SPS PUCCH may be changed from (sub)slot m to (sub)slot n. In this case, the UE may generate an SPS HARQ codebook (eg, an SPS HARQ codebook with a changed feedback timing) associated with (sub)slot m, and an SPS HARQ codebook associated with (sub)slot n (eg, feedback An SPS HARQ codebook whose timing is not changed) may be generated, and the HARQ codebook may be generated by concatenating the above-described SPS HARQ codebooks.

It may wait a long time until the UE transmits the first UL channel. In this case, the UE may not transmit the SPS HARQ-ACK according to traffic delay conditions. In order to solve this problem, the base station may schedule the UL channel to the terminal by using an additional DCI.

Method 5.7-11: A time window may be indicated to the UE, and the UE may transmit an SPS HARQ-ACK in the following UL channel within the time window. In this case, transmission of the SPS HARQ-ACK may be delayed. The UE may not multiplex the SPS HARQ-ACK outside the time window. Alternatively, the UE may consider the SPS HARQ-ACK as NACK outside the time window, and may multiplex the NACK.

The base station may indicate the time window to the terminal using higher layer signaling. The UE may know the time during which the SPS HARQ-ACK is valid within the time window. Therefore, it is not necessary to transmit the HARQ-ACK outside the time window, and a procedure for including the SPS HARQ-ACK for the corresponding SPS-configIndex in a subsequent UL channel may not be performed. This operation can be applied to all types of SPS HARQ codebooks.

Section 5.8 Multiplexing of SPS HARQ Codebook and UCI

The SPS HARQ codebook may correspond to PUCCH. If only the SPS HARQ codebook is to be transmitted, the UE may transmit only the SPS PUCCH. The time resource of SPS PUCCH may overlap with the time resource of PUCCH or PUSCH for other UCI or TB. In this case, the SPS HARQ codebook may be multiplexed with UCI or TB and transmitted.

UCI may be configured as a Type-1 HARQ codebook. In this case, the UE may generate a bit stream including HARQ-ACK for all potential PDSCH candidates for which PUCCH can be transmitted in the overlapping symbol.

UCI may include a Type-2 HARQ codebook. In this case, the UE may generate a bit stream including HARQ-ACK for all PDSCH candidates dynamically indicated in the PUCCH (eg, PRI) of the same resource.

When the priority of UCI is the same as that of SPS HARQ-ACK, UCI and SPS HARQ-ACK may be concatenated, and an encoding operation may be performed on the concatenation result. When the priority of UCI is different from that of SPS HARQ-ACK, the UE may transmit only UCI or SPS HARQ-ACK having a high priority. Alternatively, the UE may perform different encoding operations for SPS HARQ-ACK and UCI, and may concatenate results of different encoding operations.

UCI may include a Type-3 HARQ codebook. In this case, the Type-3 HARQ codebook may include HARQ-ACKs for all HARQ processes configured for the UE. Therefore, the Type-3 HARQ codebook may also include HARQ-ACK for the HARQ process included in the SPS HARQ codebook.

When the priority of UCI is the same as that of SPS HARQ-ACK, SPS HARQ-ACK may not be transmitted, and only the encoding operation for UCI may be performed. When the priority of UCI is different from that of SPS HARQ-ACK, the UE may transmit UCI or SPS HARQ-ACK having a high priority. Alternatively, the UE may perform different encoding operations for SPS HARQ-ACK and UCI, and may concatenate results of different encoding operations.

Method 5.8-1: When overlapping symbol(s) exists between the PUCCH corresponding to the Type-3 HARQ codebook and the PUCCH corresponding to the SPS HARQ codebook, the UE may transmit only the PUCCH having a high priority. When the priority of the Type-3 HARQ codebook is the same as that of the SPS HARQ codebook, the UE may transmit only the Type-3 HARQ codebook.

Section 5.8.1 Generation Time of Type-3 HARQ Codebook

The UE may receive a triggering DCI indicating transmission of the (improved) Type-3 HARQ codebook. The UE may transmit the (improved) Type-3 HARQ codebook to the base station using the PUCCH resource indicated in the triggering DCI. In this case, the time of the HARQ-ACK reflected in the (improved) Type-3 HARQ codebook can be clearly defined.

The UE receives HARQ-ACKs related to all HARQ processes configured in a reference time resource (eg, slot or subslot), HARQ-ACK(s) for active serving cell, HARQ-ACK(s) for active SPS , or a combination of the above-described HARQ-ACK(s) may be used to generate the Type-3 HARQ codebook.

When the generation time of the Type-3 HARQ codebook is not defined, the time resource from the reception time of the triggering DCI to the transmission time of the PUCCH (or PUSCH) may be given to a plurality of (sub) slots. "When some serving cells are activated or deactivated" or "some SPS is activated or deactivated", the interpretation of the generation time of the Type-3 HARQ codebook (or SPS HARQ codebook) in the base station is Type-3 in the terminal It may be different from the interpretation of the generation time of the HARQ codebook (or the SPS HARQ codebook). In order for the base station and the terminal to always derive a Type-3 HARQ codebook (or SPS HARQ codebook) of the same size, one criterion may be introduced.

Method 5.8-2: The reference time resource for generation of the (improved) Type-3 HARQ codebook may be the last (sub)slot to which the PDCCH in which the triggering DCI is received belongs.

HARQ-ACK for a certain HPN may already be reported to the base station as a Type-3 HARQ codebook. In this case, the same HARQ-ACK for the same HPN may be repeatedly reported to the base station. In order to prevent such a problem, it is necessary to distinguish whether a new PDSCH is received or not. This operation may be determined using NDI. If the NDI is changed, the UE may consider that a new PDSCH has been received. At this time, the terminal may report the HARQ-ACK to the base station. If the NDI is not changed, the UE does not need to report the HARQ-ACK to the base station.

Method 5.8-3: A new PDSCH may not be received after HARQ-ACK has already been reported in the (improved) Type-3 HARQ codebook generation procedure. In this case, the UE may not report the HARQ-ACK for the corresponding HPN.

The UE may report HARQ-ACK having a fixed value (eg, NACK) in order to maintain the size of the Type-3 HARQ codebook.

When the HARQ-ACK already reported to the base station is to be included in the Type-3 HARQ codebook, in order to prevent the HARQ-ACK from being reported to the base station in duplicate, a fixed value (e.g., NACK) ) may be reported to the base station.

Chapter 6 Transmission Method of CG PUSCH Based on Sensing

Section 6.1. Transmission method of PUSCH repetition type (repetition type) B in licensed band

The slot pattern may be indicated to the UE by “RRC signaling” or “combination of RRC signaling and DCI”. A semi-stationary UL/DL pattern of slots may be set in common to an unspecified number of terminals by RRC signaling. A semi-static UL/DL pattern of slots may be configured for a specific UE by RRC signaling. DCI format 2_0 may be configured to a UE by RRC signaling, and a UL/DL pattern of slots may be dynamically configured to a specific UE by DCI format 2_0.

When PUSCH repetition type B is used, the time resource of the PUSCH occasion may be indicated by DCI, and both the reference time resource and the number of repetitions of the PUSCH instance(s) may be indicated. When type 1 configured grant (CG) is used, the time resource of the PUSCH occasion may be indicated by RRC signaling. A time resource of a PUSCH occasion may cross a slot boundary. The terminal is slotted according to the slot format (eg, DL / FL symbols), occupancy time (eg, COT termination symbol by SFI or MCOT of channel occupancy time), or dynamic activation of invalid (invalid) resources. It may or may not transmit PUSCH instance(s) that exceed the boundary of . The invalid symbol may mean a symbol to which PUSCH is not mapped by DCI or RRC signaling, and the valid symbol may mean a symbol (eg, a symbol to which PUSCH is mapped) that is not an invalid symbol within a time window. In addition, the invalid symbol may include a symbol indicating that the SS/PBCH block is transmitted by RRC signaling and a symbol in which the Type0-PDCCH CSS set is set. In addition, the UE may assume that the number of symbols indicated by RRC signaling after the semi-stationary DL symbols are invalid symbols.

18A is a conceptual diagram illustrating a first embodiment of a method of transmitting a PUSCH occasion when PUSCH instances are consecutively arranged, and FIG. 18B is a method of transmitting a PUSCH occasion when PUSCH instances are arranged according to a preset interval. It is a conceptual diagram illustrating a first embodiment of

18A and 18B , the time resource may be a time resource for PUSCH repetition type B. The UE may repeatedly transmit the PUSCH 4 times in some symbols belonging to the time window. Invalid symbols that cannot transmit PUSCH may be excluded from symbols belonging to the time window. The second and third PUSCH instances may be transmitted separately in the time domain due to invalid symbols. The second and third PUSCH instances may be referred to as split PUSCH instances. A DM-RS for each split PUSCH instance may be transmitted, and a TB may be mapped to each split PUSCH instance. "If the split PUSCH instance consists of only a small number of symbols (eg, one symbol), and DM-RS mapping to the split PUSCH is possible and TB mapping is not possible", the split PUSCH instance may not be transmitted have.

When the base station (s) is deployed in several R × P (eg, mTRP (multi-TRP) or mR × P (multi-R × P) scenario), the UE selects a PUSCH instance in a PUSCH occasion It can be transmitted with different RxPs. Even when the UE applies the same transmit precoding matrix indicator (TPMI)/transmit rank indicator (TRI) or SRS resource indicator (SRI) to all PUSCH instances in a communication system operating in FR1, the reception operation in mR×P is difficult may not be In a communication system operating in FR2, it may be desirable for the UE to apply a different TPMI/TRI or SRI for each R×P. Therefore, in order for the UE to apply a spatial preprocessor (eg, precoding or spatial filter) differently for each R×P or to allocate transmission power differently, each PUSCH instance TPMI/TRI or The operation of changing the SRI may be necessary. The UL TCI state may mean a preprocessor applied by the UE.

The operation of changing the TCI state may include "operation of the terminal changing a spatial preprocessor", "operation of allocating transmission power differently" and/or "operation of allocating time advance differently". Therefore, processing time for applying different TCI states may be required according to the capability of the terminal. The processing time d may be set in units of symbols. For example, the processing time d may be set by RRC signaling. Alternatively, the processing time d may be a fixed value in the technical standard. In the embodiment shown in FIG. 18A , the processing time d may be zero, and in the embodiment shown in FIG. 18B , the processing time d may be zero or more. For example, the value of d may be determined as one value according to the frequency band.

Split PUSCH instances may have different RVs. Each split PUSCH instance may have one value belonging to one sequence among sequences indicated by higher layer signaling. Alternatively, each split PUSCH instance may have one value from among sequences fixed in the technical standard.

Symbols belonging to the time window may be divided into a valid symbol to which a PUSCH instance can be mapped and an invalid symbol to which a PUSCH instance is not mapped. The base station may indicate to the terminal the time pattern (eg, period and slot offset) of the invalid symbol by higher layer signaling. The base station may indicate whether to apply the time pattern of the invalid symbol by using DCI for scheduling or activating the PUSCH occasion. The UE may consider the symbol(s) in which the SS/PBCH block is transmitted or the symbol(s) in which the Type0-PDCCH CSS set is set among the symbol(s) that do not correspond to the time pattern of the invalid symbol as an invalid symbol, and the PUSCH Instances may not be mapped to invalid symbols.

Section 6.2 Transmission method of CG-UCI in unlicensed band

The base station may allocate or activate periodic transmission of PUSCH to the terminal. When PUSCH transmission is performed in an unlicensed band, the UE may select some scheduling information. The UE may express the above-described scheduling information using CG-UCI, and the CG-UCI may be multiplexed with PUSCH and transmitted. The CG-UCI may include the HARQ process number, RV, and/or NDI of the TB mapped to the PUSCH. In addition, the CG-UCI may include information for sharing the COT secured by the terminal (hereinafter, referred to as “COT sharing information”). The COT shared information may be configured in two ways, and the number of bits used to express the COT shared information in CG-UCI may vary according to the configuration method.

According to the first configuration method, the energy detection threshold may be indicated to the terminal, the terminal may secure a COT based on the energy detection threshold, and COT sharing information of the terminal may be indicated to the base station. The COT shared information may be interpreted as a list, and one or more values may constitute a corresponding list. A single value in the list may indicate that COT sharing is not allowed. Another value included in the list may be a slot offset, and the slot offset may indicate slots that the base station can use. The slot offset may indicate D consecutive slots, and the time when O slots have elapsed from slot n in which the CG-UCI is transmitted (ie, slots n+O, n+O+1, …, n+O+D). -1) can be expressed as Since the access priority of LBT (eg, channel access priority class (CAPC)) is also indicated to the terminal, when the terminal selects one value in CG-UCI, the base station CAPC of COT shared by CG-UCI DL transmission according to Since the COT sharing information may be expressed in the CG-UCI in the form of a plurality of indices, the change of the UL-DL may occur several times in the COT secured by the UE. COT sharing information may be expressed in bits corresponding to the size of the list in CG-UCI.

According to the second configuration method, the energy detection threshold may not be indicated to the terminal, and COT sharing information for sharing the COT secured by the terminal may be indicated to the base station. COT sharing information may be expressed by 1 bit. When COT sharing information is expressed as 1 in CG-UCI, the COT secured by the terminal may be shared with the base station. When COT sharing information is expressed as 0 in CG-UCI, the COT secured by the terminal may not be shared with the base station. A symbol offset (or slot offset) may be configured, and the base station may perform DL transmission after the symbol offset (or slot offset) from slot n in which the CG-UCI is transmitted.

CG-UCI may be mapped in PUSCH, and TB may be rate matched in PUSCH. When the PUSCH and the PUCCH overlap in the time domain, UCI belonging to the PUCCH may be multiplexed to the PUSCH and transmitted. In this case, the PUCCH may not be transmitted. When the UCI includes the HARQ-ACK, the corresponding UCI may be concatenated with the CG-UCI, and an encoding operation on the concatenation result may be performed. The coded CG-UCI and/or UCI may be mapped in the RE close to the DM-RS.

If the (sub) slot in which the PUCCH is transmitted and the (split) PUSCH instance(s) overlap, the UE may multiplex UCI in the first transmitted (split) PUSCH instance among the (split) PUSCH instance(s) overlapping the PUCCH. have. Alternatively, the UE may multiplex UCI in the first (split) PUSCH instance belonging to the PUSCH occasion. (split) PUSCH instance may mean "PUSCH instance (eg, complete PUSCH instance)" or "split PUSCH instance".

Section 6.2.1 Mapping method of CG-UCI considering frequency hopping

The UL signal/channel transmitted by the UE in the unlicensed band may have an appropriate power density, and the UL signal/channel may be transmitted in an appropriate bandwidth. A DL signal/channel transmitted by the base station in the unlicensed band may have an appropriate power density, and the DL signal/channel may be transmitted in an appropriate bandwidth.

Section 6.3 Transmission method according to CG PUSCH repetition type B in unlicensed band

A terminal operating in an unlicensed band may transmit a CG PUSCH. The CG-UCI may include information on scheduling information for PUSCH and information on a time resource (eg, COT) secured by the UE. The CG-UCI may include information on HPN, RV, NDI, and/or time resources secured by the UE. Information on the time resource secured by the terminal may be expressed as an index. For example, information on time resources secured by the terminal may be expressed by one or more bits. It may be configured that the time resource secured by the terminal can be shared with the base station or other terminals. In this case, a list of methods for sharing the energy detection threshold and/or the time secured by the terminal may be indicated to the terminal.

"If the PUCCH and the PUSCH are located in the same symbol and the UE is given sufficient processing time", UCI may be multiplexed in the PUSCH. When the CG PUSCH is transmitted in the unlicensed band, the CG-UCI may be multiplexed in the UCI and the CG PUSCH, and an encoding operation on the multiplexing result may be performed. In this case, UCI may include at least HARQ-ACK.

When the UE is instructed to perform PUSCH repetition type B, the UE may consider the following method(s) in order to transmit CG-UCI in PUSCH.

19A is a conceptual diagram illustrating a first embodiment of a method for transmitting CG-UCI in all PUSCH instances belonging to a PUSCH occasion based on sensing when PUSCH instances are consecutively arranged, and FIG. 19B is a diagram illustrating PUSCH instances It is a conceptual diagram illustrating a first embodiment of a method of transmitting a CG-UCI in all PUSCH instances belonging to a PUSCH occasion based on sensing when they are arranged according to a preset interval.

19A and 19B , the UE may transmit CG-UCI based on the method(s) below.

Method 6.3-1: All (split) PUSCH instances belonging to a PUSCH occasion may include a CG-UCI.

CG-UCI may always be included in a PUSCH instance. A PUSCH occasion may include four PUSCH instances, and a CG-UCI may always be included in a PUSCH instance. The CG-UCI may include HPN, NDI, RV and/or COT sharing information.

With respect to the COT sharing information, the UE may transmit different COT sharing information for each PUSCH instance, but it may be preferable not to overturn the previously transmitted COT sharing information. Therefore, it may be desirable to add new COT shared information while maintaining previously transmitted COT shared information.

When transmission according to PUSCH repetition type B is performed, the UE may transmit one TB in a PUSCH occasion. Accordingly, a portion (eg, HPN, NDI) of scheduling information included in CG-UCI may maintain the same value. RV may have different values in a split PUSCH instance.

According to the proposed method, the UE may interpret the RV as the RV for the split PUSCH instance. Therefore, CG-UCI may always have a different value for each PUSCH instance. When PUSCH repetition type B is used, the method of applying RV may be known. Therefore, the terminal and the base station can predict the change value of the RV even when the CG-UCI is changed.

According to another proposed method, the UE may interpret the RV as the RV for the first PUSCH instance in the PUSCH occasion. If the value of energy, which is a result of LBT performed in the terminal, is measured to be high, the terminal may not be able to transmit the first PUSCH instance. Even in this case, the UE may apply the corresponding RV in the first PUSCH instance. In the (split) PUSCH instance that the UE actually transmits, the actual RV may be derived from the RV indicated by the CG-UCI, and the derived actual RV may be applied. According to this method, since all of the CG-UCIs express the same scheduling information, if the COT sharing information is also maintained the same, the CG-UCI may always be maintained the same in the PUSCH occasion. The base station can lower the error rate by decoding the CG-UCI based on the above-described setting.

In the mTRP scenario, a plurality of spatial relation information for a PUSCH occasion, a plurality of TPMIs, or a TCI state index may be indicated to the UE. In this case, if method 6.3-1 is applied, each spatial relationship information may correspond to CG-UCI, and a PUSCH instance including CG-UCI may be transmitted.

Method 6.3-2: Some PUSCH instances belonging to the PUSCH occasion may include CG-UCI, and the PUSCH instance including CG-UCI is the first PUSCH instance that succeeds in LBT or the first PUSCH instance transmitted within FFP can be

When PUSCH repetition type B is used, PUSCH instances may have the same HPN and NDI. RV and/or COT sharing information may have different values for each PUSCH instance. For example, the RV may be determined according to a preset order in the (split) PUSCH instance. The first value of the sequence of the RV may be indicated to the UE by DCI or higher layer signaling. Here, one value may be indicated to the terminal. Therefore, it may be sufficient for the base station to receive the RV value only once.

The COT sharing information may imply a time during which the base station can perform DL transmission within the time secured by the terminal. When "the terminal does not update the COT shared information" or "the terminal does not add new COT shared information", it may be sufficient for the base station to receive the COT shared information only once.

Accordingly, the UE may transmit only one CG-UCI for all PUSCH instances belonging to the PUSCH occasion. In this case, considering the processing time of the base station, the PUSCH instance to which the CG-UCI is multiplexed may be the first (split) PUSCH instance transmitted by the UE. When it is determined that the amount of energy received as a result of the LBT performed by the terminal is small, CG-UCI may be multiplexed in the (split) PUSCH instance, and CG-UCI may not be multiplexed in the remaining PUSCH instances. When the UE performs a transmission operation in FFP, CG-UCI may be multiplexed in the first split PUSCH instance transmitted by the UE, and CG-UCI may not be multiplexed in the remaining PUSCH instances. This operation can be illustrated in FIGS. 20A and 20B .

20A is a conceptual diagram illustrating a first embodiment of a method for transmitting CG-UCI in the first PUSCH instance that succeeds in LBT when PUSCH instances are consecutively deployed, and FIG. 20B is a PUSCH instance is deployed according to a preset interval It is a conceptual diagram illustrating a first embodiment of a method for transmitting a CG-UCI in the first PUSCH instance that succeeds in LBT in the case of LBT.

20A and 20B , the UE may transmit CG-UCI based on the method(s) below.

Method 6.3-3: CG-UCI may be included in a discontinuous (split) PUSCH instance in the time domain.

Some symbols among symbols belonging to the PUSCH occasion may be determined to be invalid symbols or symbols other than valid symbols, and in this case, a (split) PUSCH instance may be transmitted. The UE may check whether the measured energy is less than or equal to a threshold by performing LBT before transmission of a (split) PUSCH instance. When the measured energy exceeds the threshold, the UE may not transmit the PUSCH instance. This operation may be illustrated in FIGS. 21A and 21B .

21A is a conceptual diagram illustrating a first embodiment of a method for transmitting CG-UCI in one PUSCH instance for each COT/FFP when PUSCH instances are consecutively arranged, and FIG. 21B is a PUSCH instance according to a preset interval. It is a conceptual diagram illustrating a first embodiment of a method for transmitting a CG-UCI in one PUSCH instance for each COT/FFP when deployed.

Referring to FIG. 21A , a PUSCH occasion may include two consecutive PUSCH instances, and a CG-UCI may be included in the first PUSCH instance of the consecutive PUSCH instances.

Referring to FIG. 21B , since PUSCH instances are arranged according to a preset interval, a PUSCH occasion may be interpreted as including two consecutive PUSCH instances. In this case, CG-UCI may be included in the first PUSCH instance of consecutive PUSCH instances. Alternatively, when d>0, the PUSCH occasion may be interpreted as including 4 PUSCH instances. In this case, CG-UCI may be included in all PUSCH instances.

When "the terminal fails to perform a transmission operation in consecutive symbols" or "when the terminal performs the first transmission operation", the terminal may secure COT by performing LBT. The terminal may share the secured COT with other terminals and/or base stations. The terminal may utilize the corresponding COT again after the shared time. In this case, the corresponding COT may be referred to as a “paused COT”. The terminal may perform LBT to re-utilize the stopped COT. Therefore, according to method 6.3-3, CG-UCI may be included in the PUSCH instance in which LBT is performed, not all PUSCH instances. Here, the PUSCH instance may be a complete PUSCH instance or a split PUSCH instance.

A UE operating according to the FBE scheme may transmit a PUSCH occasion for a time longer than one FFP. When the PUSCH occasion crosses the boundary of the FFP, according to method 6.3-3, the UE may transmit the CG-UCI again. That is, CG-UCI may be included in a specific PUCH instance.

Method 6.3-4: When method 6.3-3 is applied, one PUSCH instance including CG-UCI may be defined for each COT/FFP secured or stopped by the UE.

Chapter 7 PUCCH Carrier Switching

Section 7.1 PUCCH Transmission in One TDD Cell

When communication is performed in a single cell, the UE may transmit the HARQ-ACK to the base station using the valid PUCCH resource when the PUCCH resource is valid. In TDD, the symbol for the slot format (or slot pattern), SS/PBCH block, Type-0 PDCCH CSS set, and/or CORESET may be regarded as a symbol in which PUCCH is not transmitted.

When the above-described methods are applied in Sections 5.7 and 5, the UE may wait for a valid resource through which the PUCCH can be transmitted in order to transmit the PUCCH in the PCell. This operation may be established for at least HARQ-ACK transmission for the SPS PDSCH. The time resource in which the SPS HARQ-ACK is transmitted may be the first UL resource available in the UE. Here, the time resource for transmitting the PUCCH may be set and/or indicated in units of subslots or slots.

When repeated transmission of the PUCCH is configured, the configuration information of the PUCCH resource may include information indicating the number of repetitions of each PUCCH format. The number of repetitions of the PUCCH format may be one or more. For example, the number of repetitions of the PUCCH format may be 2, 4, or 8. When repeated transmission of PUCCH is configured in the terminal, the terminal may derive a time resource in which PUCCH can be transmitted in consideration of the slot pattern of TDD. In this case, the UE may wait until it can utilize an effective time resource while maintaining the number of transmissions of the PUCCH.

22 is a conceptual diagram illustrating a first embodiment of a method of deferring HARQ-ACK transmission when repeated transmission of PUCCH is indicated in a TDD system.

Referring to FIG. 22, HARQ-ACK may be repeatedly transmitted twice based on a slot. If the transmission time resource of the PUCCH in the current slot is not valid, the PUCCH may be transmitted through the same time resource in the next slot. This operation can be equally applied even when the subslot is configured in the terminal.

In the TDD system, since the slot pattern is indicated to the UE by RRC signaling, the UE may derive a time resource in which HARQ-ACK can be transmitted in advance. In particular, for transmission of SPS HARQ-ACK, the UE may predict in advance in which time resources PUCCH transmission is possible. Therefore, the UE does not need to calculate the time resource of PUCCH every time at least in the TDD system.

When repeated transmission of PUCCH is not configured (eg, when PUCCH is transmitted only once), PUCCH may be dropped according to a slot pattern. In order to improve the method in which the PUCCH is dropped in the TDD system, the repeated transmission procedure of the PUCCH may be extended. This operation can be illustrated in FIG. 23 .

23 is a conceptual diagram illustrating a first embodiment of a method for deferring HARQ-ACK transmission when repeated transmission of PUCCH is not indicated in a TDD system.

Referring to FIG. 23, when repeated transmission of PUCCH is not indicated, HARQ-ACK transmission may be delayed.

Method 7.1-1: The number of repeated transmissions of the PUCCH may be added once, and the HARQ-ACK may be transmitted in the first time resource among valid time resources in which the PUCCH may be transmitted. The number of repeated transmissions of the PUCCH may be set to one value from among 1, 2, 4, 8, or 8 or more values.

When the PUCCH is delayed, two or more SPS PDSCHs or HARQ-ACKs for two or more PDSCHs may be transmitted on the same PUCCH resource. In this case, when repeated transmission of PUCCH is not instructed to the UE, the UE may perform a UCI multiplexing operation according to a technical standard. For example, the terminal may generate a HARQ-ACK codebook, and may transmit the HARQ-ACK codebook to the base station through PUCCH.

When repeated transmission of PUCCH is indicated to the UE, the UE may transmit HARQ-ACK for the first transmission, and the HARQ-ACK for transmission after the first transmission is not transmitted in the same time resource (eg, PUCCH). can be assumed to be In the HARQ codebook generation procedure, some HARQ-ACKs may be deferred HARQ-ACKs, and other HARQ-ACKs may not be deferred HARQ-ACKs. According to the proposed method, the UE can generate the HARQ codebook regardless of deferred HARQ-ACK and non-deferred HARQ-ACK.

Method 7.1-2: When repeated transmission of PUCCH is indicated to the UE, the UE allows initial transmission in the same PUCCH instance without distinction between deferred HARQ-ACK and non-deferred HARQ-ACK HARQ codebook for HARQ-ACK can create

According to method 7.1 2, two or more SPS HARQ-ACK bits may be transmitted in one PUCCH according to the period of the SPS PDSCH. In this case, the HARQ codebook may be generated based on one or a combination of two or more of the methods proposed in Sections 5.6 and 5.8 described above.

Section 7.2 Intra-band (intra-band) TDD CA (carrier aggregation) PUCCH transmission

When two or more serving cells are activated for a UE by CA, two or more UL symbols may be configured in a slot according to a pattern of each serving cell. Since a serving cell (eg, PCell or PUCCH SCell) capable of transmitting PUCCH is configured by RRC signaling, the UE cannot transmit PUCCH using another serving cell (eg, SCell). In embodiments, the PUCCH may be assumed to be transmitted in the PCell, and the UE may assume that one or more SCells are activated.

When the UE waits for a valid time resource of the PCell for transmission of HARQ-ACK, the delay time of HARQ-ACK transmission may increase. To solve this problem, the effective time resource of the SCell may be used for transmission of HARQ-ACK.

Method 7.2-1: "Application of time deferral to SPS HARQ-ACK transmission" or "change of serving cell in which SPS HARQ-ACK is transmitted" may be indicated to the UE by RRC signaling.

The base station may instruct the terminal to perform one of "application of time delay to SPS HARQ-ACK transmission" and "change of serving cell in which SPS HARQ-ACK is transmitted". The reason is that it is desirable for the base station to receive the PUCCH in one resource. The UE may perform the multiplexing operation of UCI based on the technical standard, and then may check the frequency resource through which the PUCCH is transmitted. Thereafter, the UE may determine the time resource for transmitting the PUCCH using the group common DCI (eg, DCI format 2_0, DCI format 2_1, DCI format 2_4, etc.).

Method 7.2-2: After performing the multiplexing operation of UCI, the UE may perform "application of time deferral to SPS HARQ-ACK transmission" and "change of serving cell in which SPS HARQ-ACK is transmitted", after which Group common DCI can be applied.

When the serving cell in which the PUCCH is transmitted may be changed, resources of the PUCCH may be configured for each active BWP in the serving cell. A separate DCI for managing the transmission power of the PUCCH may be required.

Method 7.2-3: The DCI format for controlling the power of the PUCCH may indicate the power of the PUCCH in another serving cell by reusing a bit that applies a supplementary UL (SUL).

When the SUL carrier is not configured in the terminal, according to method 7.2-3, a method in which a transmit power control (TPC) command for SUL is indicated may be applied. Therefore, one bit can be added to the TPC instruction. That is, the TCP command can be expressed with 3 bits. Here, the added bit may mean an index of a serving cell, the added bit set to the first value may mean the PCell, and the added bit set to the second value may mean the SCell.

The change of the serving cell in which the PUCCH is transmitted may be indicated by RRC signaling and/or DCI. The frequency resource through which the PUCCH is transmitted may be indicated by RRC signaling. Specifically, the serving cell to which the PUCCH is transmitted may be indicated to the terminal in a preset pattern. The preset pattern may be periodically extended and applied. The preset pattern may be repeated with a period of 20 ms or a period of a factor of 20.

The terminal may receive the bitmap from the base station, and may determine in which serving cell the PUCCH is transmittable in the slot based on the value of the bit included in the bitmap. Here, a maximum of one serving cell may be indicated to the UE. For example, the terminal may receive the list of serving cells from the base station, and may apply the list of serving cells in order for each slot.

Method 7.2-4: The base station may indicate the pattern of the serving cell in which the PUCCH is transmitted to the terminal through RRC signaling.

According to another method, the serving cell in which the PUCCH is transmitted may be changed according to a dynamic indication of the base station. The UE may derive a serving cell in which the PUCCH is transmitted based on a combination of a separate field included in the scheduling DCI or a combination of field(s) indicating a resource of the PUCCH.

When the UE transmits a plurality of HARQ-ACK bits, the UE may derive a serving cell of the PUCCH based on a value indicated by the last received DL-DCI. When the PUCCH overlaps the PUSCH in the time domain of the derived serving cell, UCI may be multiplexed in the PUSCH in the corresponding serving cell.

Method 7.2-5: By extending (or reusing) a separate field or an existing field included in DL-DCI, a serving cell of PUCCH may be derived.

A new field may be introduced in DCI, and one serving cell may be selected from among two or more serving cells. Alternatively, the field indicating the PRI may be extended, and one bit in the field may indicate one of the serving cells. Alternatively, the PUCCH resource set may be extended, and the PUCCH resource belonging to the PUCCH resource set may include information implicitly indicating a change in the serving cell.

"The repeated transmission of the PUCCH is indicated to the terminal" may mean "the PUCCH is transmitted at least twice". When the above-described method 7.1-1 is applied, the PUCCH may be transmitted more than once. In this case, PUCCH carrier switching may be additionally activated in the terminal. In this case, the UE may transmit a PUCCH occasion and may derive frequency resources for one or more PUCCH instances.

Method 7.2-6: When UCI repetition is configured, the UE may transmit PUCCH on the same carrier.

A PUCCH instance may always be transmitted in the same serving cell. This operation can be illustrated in FIG. 24 .

24 is a conceptual diagram illustrating a first embodiment of a method of changing a serving cell in which PUCCH is transmitted in TDD CA when repeated transmission of PUCCH is indicated.

Referring to FIG. 24 , the UE may use two slots to transmit the PUCCH occasion, and the transmission of the PUCCH occasion may be performed in the SCell. At this time, since the slot pattern in the PCell is different from the slot pattern in the SCell, a valid UL resource may be allocated to the UE.

The UE may have to wait another time for transmission of the PUCCH instance according to the combination of the slot pattern(s) in the PCell and the slot pattern(s) in the SCell. This operation can be illustrated in FIG. 25 .

25 is a conceptual diagram illustrating a second embodiment of a method of changing a serving cell in which PUCCH is transmitted in TDD CA when repeated transmission of PUCCH is indicated.

Referring to FIG. 25 , the serving cell may be continuously maintained. For two transmissions of the PUCCH instance, the PUCCH may be transmitted in the SCell because the PUCCH cannot be transmitted in the PCell. The UE may postpone one slot according to the slot format of the SCell, and may transmit a PUCCH occasion using three slots.

Even when the method using only the PCell is applied, the PUCCH instance may be delayed. Accordingly, the UE may transmit the PUCCH occasion using three slots. If method 7.2-6 is applied, there may be a case where the delay time of PUCCH transmission cannot be reduced. The reason is that the PUCCH occasion is limited to always be transmitted in the same serving cell.

In another method, it may be allowed for the PUCCH instance to be transmitted in different serving cells. That is, the UE may transmit the PUCCH instance in all serving cells available for transmission of the PUCCH instance.

Method 7.2-7: When UCI repetition is configured, the UE may transmit each PUCCH instance in different serving cells. This operation can be illustrated in FIG. 26 .

26 is a conceptual diagram illustrating a third embodiment of a method of changing a serving cell in which PUCCH is transmitted in TDD CA when repeated transmission of PUCCH is indicated.

Referring to FIG. 26 , the serving cell may be further changed. For two transmissions of the PUCCH instance, available serving cells may be indicated to the UE by RRC signaling and/or DCI. Accordingly, the case in which the PUCCH instance is postponed may be reduced. The UE may transmit the PUCCH instance once in the PCell and may transmit the PUCCH instance once in the SCell. In this case, the UE may transmit the PUCCH occasion using only two slots.

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

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

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

Claims (20)

A method of operating a terminal in a communication system, comprising:
receiving one or more data units from a base station;
generating a hybrid automatic repeat request (HARQ) codebook for at least one data unit of the one or more data units at a reference time; and
Transmitting the HARQ codebook to the base station,
The reference time is shared by the terminal and the base station. The method according to claim 1,
The method of operation of the terminal,
The method of operating a terminal further comprising: receiving, from the base station, downlink control information (DCI) triggering transmission of the HARQ codebook. 3. The method according to claim 2,
The reference time is implicitly indicated by information included in the DCI. The method according to claim 1,
The reference time is set based on a channel through which the HARQ codebook is transmitted. The method according to claim 1,
The one or more data units are received through a resource according to one or more aggregated carriers or one or more semi-persistent scheduling (SPS). The method according to claim 1,
The HARQ codebook is "HARQ-ACK (acknowledgement) for the at least one data unit received on the one or more aggregated carriers that are active at the reference time" or "One or more aggregated carriers that are active at the reference time" and "HARQ-ACKs for data units received on one or more aggregated carriers in an inactive state". The method according to claim 1,
The HARQ codebook includes "HARQ-ACK for the at least one data unit received from a resource according to the one or more SPSs that are active at the reference time" or "One or more SPSs that are active at the reference time and an inactive state" HARQ-ACKs for data units received in resources according to one or more SPSs". The method according to claim 1,
When the HARQ codebook includes a HARQ-ACK for the at least one data unit received on the one or more aggregated carriers in the active state at the reference time, the HARQ buffer for the one or more aggregated carriers in the inactive state is A method of operating a terminal, which is emptied at a preset time point. 9. The method of claim 8,
The preset time point is after the transmission of the HARQ codebook, the method of operation of the terminal. The method according to claim 1,
When the HARQ codebook includes a HARQ-ACK for the at least one data unit received from a resource according to the one or more SPSs in the active state at the reference time, the HARQ buffer for the one or more SPSs in the inactive state is previously A method of operating a terminal, which is emptied at a set time point. The method according to claim 1,
When the HARQ-ACK for DCI indicating release of the SPS configuration is transmitted to the base station, the reference time is set after a time required for the HARQ-ACK processing in the base station. A method of operating a base station in a communication system, comprising:
transmitting one or more data units to the terminal;
receiving a hybrid automatic repeat request (HARQ) codebook for at least one data unit among the one or more data units from the terminal;
estimating that the HARQ codebook is generated at a reference time; and
Comprising the step of interpreting the HARQ codebook based on the reference time,
The reference time is shared by the terminal and the base station. 13. The method of claim 12,
The method of operation of the base station,
The method further comprising transmitting downlink control information (DCI) triggering transmission of the HARQ codebook to the terminal, wherein the DCI includes information indicating the reference time. 13. The method of claim 12,
The one or more data units are transmitted through one or more aggregated carriers or a resource according to one or more semi-persistent scheduling (SPS). 13. The method of claim 12,
The HARQ codebook includes "HARQ-ACK (acknowledgement) for the at least one data unit received on the one or more aggregated carriers that are active at the reference time", "One or more aggregated carriers that are active at the reference time" HARQ-ACKs for data units received on one or more aggregated carriers that are in an inactive state with HARQ-ACK for", or "HARQ-ACKs for data units received in resources according to one or more SPSs in an active state and one or more SPSs in an inactive state at the reference time". how it works. 13. The method of claim 12,
The method of operation of the base station,
transmitting DCI instructing release of SPS configuration to the terminal; and
Further comprising the step of receiving the HARQ-ACK for the DCI from the terminal,
The reference time is set after the time required for the processing of the HARQ-ACK in the base station. As a terminal in a communication system,
processor;
a memory in electronic communication with the processor; and
including instructions stored in the memory;
When the instructions are executed by the processor, the instructions cause the terminal to
receive one or more data units from a base station;
generate a hybrid automatic repeat request (HARQ) codebook for at least one of the one or more data units at a reference time; and
operative to cause transmission of the HARQ codebook to the base station;
The reference time is shared by the terminal and the base station. 18. The method of claim 17,
The commands are
and further cause reception of downlink control information (DCI) triggering transmission of the HARQ codebook from the base station, wherein the DCI includes information indicating the reference time. 18. The method of claim 17,
When the HARQ codebook includes a HARQ-ACK for the at least one data unit received on the one or more aggregated carriers in the active state at the reference time, the HARQ buffer for the one or more aggregated carriers in the inactive state is A terminal that is emptied at a preset time point. 18. The method of claim 17,
When the HARQ-ACK for DCI indicating release of the SPS configuration is transmitted to the base station, the reference time is after the time required for the HARQ-ACK processing in the base station, the terminal.

Images