Patent Description:
To meet the demand for wireless data traffic having increased since deployment of <NUM> th generation (<NUM>) communication systems, efforts have been made to develop an improved <NUM>th generation (<NUM>) or pre-<NUM> communication system. Therefore, the <NUM> or pre-<NUM> communication system is also called a 'Beyond <NUM> Network' or a 'Post long term evolution (LTE) System'. The <NUM> communication system established by the 3rd generation partnership project (3GPP) is called a new radio (NR) system.

To decrease propagation loss of the radio waves and increase the transmission distance, the beamforming, massive multiple-input multiple-output (MIMO), Full Dimensional MIMO (FD-MIMO), array antenna, an analog beam forming, large scale antenna techniques have been discussed and adopted in <NUM> communication systems.

In the <NUM> system, Hybrid FSK and QAM Modulation (FQAM) and sliding window superposition coding (SWSC) as an advanced coding modulation (ACM), and filter bank multi carrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA) as an advanced access technology have been developed.

As various services can be provided according to the development of the above-described wireless communication system, a method for effectively providing such services is required.

There are needs of enhancing current communication system to provide various services efficiently.

According to embodiments of the disclosure, various types of services of next generation wireless communication system can be efficiently provided.

For the same reason, in the accompanying drawings, some elements are exaggerated, omitted, or schematically illustrated. Further, the size of each element does not entirely reflect the actual size. The same reference numerals are assigned to the same or corresponding elements in each drawing.

The advantages and features of the disclosure and a method of achieving the same should become clear with embodiments described in detail below with reference to the accompanying drawings. However, the disclosure is not limited to the embodiments disclosed below, but may be implemented in various different forms. The embodiments make the disclosure complete and are provided to completely inform a person skilled in the art to which the disclosure belongs of the scope of the disclosure. The scope of the disclosure is defined only by the appended claims. The same or like reference numerals refer to the same or like elements throughout the specification.

Here, it will be understood that each block of the process flowchart drawings and combinations of the flowchart drawings can be performed by computer program instructions. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing equipment to produce a machine, such that the instructions, which are executed via the processor of the computer or other programmable data processing equipment, create means for implementing the functions specified in the flowchart block(s). These computer program instructions may also be stored in a computer usable or computer-readable memory that can direct a computer or other programmable data processing equipment to function in a particular manner, such that the instructions stored in the computer usable or computer-readable memory produce an article of manufacture including instruction means that implement the function specified in the flowchart block(s). The computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operations to be performed on the computer or other programmable data processing equipment to produce a computer-implemented process such that the instructions that are executed on the computer or other programmable data processing equipment provide operations for implementing the functions specified in the flowchart block(s).

In addition, each block of the flowchart drawings may represent a module, segment, or portion of code, which includes one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the given order. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the corresponding function.

The term "-unit" as used in embodiments of the disclosure means a software or hardware element, such as a field-programmable gate array (FPGA) or an application specific integrated circuit (ASIC), and the "-unit" performs functions. However, the "~unit" does not always have a meaning limited to software or hardware. The "-unit" may be configured either to be stored in an addressable storage medium or to execute one or more processors. Therefore, for example, the "-unit" includes elements such as software elements, object-oriented software elements, class elements or task elements, processes, functions, properties, procedures, sub-routines, segments of a program code, drivers, firmware, micro-codes, circuits, data, database, data structures, tables, arrays, and parameters. Functions provided by elements and components "-units" may be formed by combining the small number of elements and components "-units" or may be divided into additional elements and components "-units". In addition, elements and components "-units" may also be implemented to execute one or more CPUs within a device or a security multimedia card. Further, in the embodiment, the "-unit" may include one or more processors.

A wireless communication system has been developed from an initial wireless communication system providing a voice-oriented service to a broadband wireless communication system providing a high-speed and high-quality packet data service, such as those according to communication standards including high speed packet access (HSPA), long term evolution (LTE) (or evolved universal terrestrial radio access (E-UTRA)), and LTE-advanced (LTE-A) defined in the 3GPP, high rate packet data (HRPD) and ultra mobile broadband (UMB) defined in the 3GPP2, and <NUM>. 16e defined in the IEEE. In addition, a <NUM> or NR communication standard has been established for a 5th generation wireless communication system.

As a typical example of the broadband wireless communication system, a <NUM> or NR system has adopted an orthogonal frequency division multiplexing (OFDM) scheme in a downlink (DL) and an uplink. More specifically, a cyclic-prefix OFDM (CP-OFDM) scheme is adopted in the downlink, and a discrete Fourier transform spreading OFDM (DFT-S-OFDM) scheme is adopted along with the CP-OFDM scheme in the uplink. The uplink refers to a radio link through which a terminal (user equipment (UE) or a mobile station (MS)) transmits data or a control signal to a base station (BS) (gNode B, eNode B, or BS), and the downlink refers to a radio link through which the base station transmits data or a control signal to the terminal. In such a multiple access scheme, normally, assigning and operating are performed such that time-frequency resources for transmission of data or control information for each user do not overlap with each other, that is, orthogonality is established. Therefore, each user's data or control information can be identified.

The <NUM> or NR system adopts a HARQ scheme in which corresponding data is retransmitted in a physical layer when a decoding failure occurs in initial transmission. The HARQ scheme refers to a scheme in which when a receiver fails to correctly decode data, the receiver transmits information (negative acknowledgement (NACK)) informing a transmitter of the decoding failure, so as to enable the transmitter to retransmit the corresponding data in the physical layer. The receiver increases data reception performance by combining the data retransmitted by the transmitter with the data that has previously failed to be decoded. In addition, when the receiver correctly decodes data, the receiver transmits information (acknowledgment (ACK)) informing the transmitter of a decoding success, so as to enable the transmitter to transmit new data.

Meanwhile, the NR system, which is a new <NUM> communication system, is designed to allow various services to be freely multiplexed in time and frequency resources. Accordingly, waveform/numerology and a reference signal can be dynamically or freely allocated according to the needs of a corresponding service. In wireless communication, in order to provide an optimal service to a terminal, optimized data transmission through measurement of channel quality and interference amount is important, and thus accurate channel state measurement is necessary. However, unlike <NUM> communication in which channel and interference characteristics are not significantly changed according to frequency resources, since the channel and interference characteristics are significantly changed according to services in the case of a <NUM> or NR channel, it is necessary to support a subset of frequency resource group (FRG) level, which enables separate measurement. Meanwhile, in the <NUM> or NR system, the types of supportable services may be divided into categories such as eMBB, mMTC, and URLLC. The eMBB aims for high-speed transmission of high-capacity data, the mMTC aims for minimization of power of the terminal and access by multiple terminals, and the URLLC aims for high reliability and low latency. Depending on the type of service applied to the terminal, different requirements may be applied.

Since the URLLC service among the above-described services aims for high reliability and low latency, there may be a need to transmit control information and data information which can be transmitted through a physical channel at a low coding rate. In the case of control information, a repetitive transmission function of control information has already been introduced in an MTC or narrow band Internet-of-Things (NB-IoT) service of the LTE. The purpose of the introduction is to provide high coverage for terminals having a small bandwidth, and thus latency has not been sufficiently considered. In addition, the minimum unit for control information repetitive transmission is fixed in the unit of a sub-frame based on the LTE.

In order to support the URLLC service in the NR or <NUM> system, it is required to introduce a control information repetitive transmission mode which can improve reliability while requiring low latency. Accordingly, the disclosure basically considers a situation in which control information is repeatedly transmitted within a slot. Additionally, the disclosure also considers a situation in which control information which can be transmitted over a slot boundary is repeatedly transmitted. Through operations provided in the disclosure, a terminal can detect control information transmitted from a base station with high reliability in a faster time.

In the disclosure, each term is defined in consideration of each function, and may vary according to a user's or operator's intention or practice. Therefore, the definition should be made based on the contents throughout the specification. Hereinafter, a base station, as a subject which performs resource allocation of a terminal, may include at least one of a next generation node B (gNodeB (gNB)), an evolved node B (eNode B (eNB)), a Node B, a base station (BS), a radio access unit, a base station controller, or a node on the network. The terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smart phone, a computer, or a multimedia system capable of performing a communication function. In the disclosure, a downlink (DL) refers to a wireless transmission path of a signal transmitted by the base station to the terminal, and an uplink (UL) refers to a wireless transmission path of a signal transmitted by the terminal to the base station. In addition, hereinafter, the disclosure describes the NR system as an example, but is not limited thereto, and embodiments of the disclosure may be applied to various communication systems having similar technical backgrounds or channel types. In addition, an embodiment of the disclosure may be applied to other communication systems through some modifications within a range which does not significantly depart from the scope of the disclosure, as determined by a person having skilled technical knowledge.

In the disclosure, the terms "physical channel" and "signal" can be used interchangeably with "data" or "control signal". For example, a physical downlink shared channel (PDSCH) is a physical channel through which data is transmitted, but the PDSCH may also be referred to as data in the disclosure.

In the disclosure, higher layer signaling may be a signal transmission method of transmitting a signal from a base station to a terminal by using a downlink data channel of a physical layer or from the terminal to the base station by using an uplink data channel of the physical layer, and may be referred to as radio resource control (RRC) signaling or a medium access control (MAC) control element (CE).

Meanwhile, as research on a next-generation communication system has recently been conducted, various methods for scheduling communication with a terminal are being discussed. Accordingly, an efficient scheduling and data transmission/reception method considering characteristics of a next-generation communication system is required. Accordingly, in order to provide a plurality of services to a user in the communication system, there is a need for a method capable of providing each service within the same time interval according to characteristics of a corresponding service, and an apparatus using the same.

Hereinafter, the disclosure describes a method and an apparatus for transmitting HARQ-ACK feedback for downlink data transmission. Specifically, a method for configuring HARQ-ACK feedback bits when a terminal intends to transmit multiple HARQ-ACKs within one slot through an uplink is described.

In the wireless communication system, particularly, the new radio (NR) system, a base station may configure one component carrier (CC) or a plurality of component carriers for downlink transmission to a terminal. In addition, downlink transmission and uplink transmission slots and symbols may be configured in each CC. Meanwhile, when a PDSCH, which is downlink data, is scheduled, downlink control information (DCI) may transmit at least one of slot timing information to which the PDSCH is mapped, information on a start symbol position to which the PDSCH is mapped in a corresponding slot, and information on the number of symbols to which the PDSCH is mapped, through a specific bit field. For example, when the DCI is transmitted in slot n and the PDSCH is scheduled, if K0, which is slot timing information in which the PDSCH is transmitted, indicates <NUM>, the start symbol position is <NUM>, and a symbol length is <NUM>, the corresponding PDSCH is mapped to <NUM> symbols from symbol <NUM> in slot n and transmitted. Meanwhile, a PDSCH, which is a downlink data signal, is transmitted, and HARQ-ACK feedback is transmitted from the terminal to the base station after slot K1. K1 information, which is timing information in which HARQ-ACK is transmitted, may be transmitted in the DCI, and a candidate set of possible K1 values may be transmitted by higher layer signaling, and determined as one of the values in DCI.

When a semi-static HARQ-ACK codebook is configured for the terminal, the terminal may determine a feedback bit (or an HARQ-ACK codebook size) required to be transmitted, based on a table including K0 which is slot information to which a PDSCH is mapped, start symbol information, and information on the number or length of symbols, and K1 candidate values which are HARQ-ACK feedback timing information for the PDSCH. The table including the slot information to which the PDSCH is mapped, the start symbol information, and the information on the number or length of symbols may have a default value, and there may also be a table that the base station can set for the terminal.

When a dynamic HARQ-ACK codebook is configured for the terminal, the terminal may determine a HARQ-ACK feedback bit (or an HARQ-ACK codebook size) required to be transmitted by the terminal according to downlink assignment indicator (DAI) information included in the DCI in a slot in which HARQ-ACK information is transmitted by a K1 value which is HARQ-ACK feedback timing information for the PDSCH and K0 which is slot information to which the PDSCH is mapped.

In the disclosure, one or more PUCCHs including HARQ-ACK may be transmitted in one slot in a situation in which the terminal performs transmission of one or more HARQ-ACKs in one slot. The PUCCHs and another PUCCH including channel information or scheduling request information may be overlappingly transmitted in a specific OFDM symbol. In this case, a method for resolving a problem of a conflict between a PUCCH and a PUCCH and operating a terminal in the above case is provided. In addition, the PUCCHs and a PUSCH for transmitting uplink data information may be overlappingly transmitted in a specific OFDM symbol. In this case, a method for resolving a problem of a conflict between a PUCCH and a PUSCH and operating a terminal in the above case is provided.

<FIG> illustrates a transmission structure of a time-frequency domain which is a radio resource region of a <NUM> or NR system according to an embodiment of the disclosure.

Referring to <FIG>, in a radio resource region, the horizontal axis indicates a time domain, and the vertical axis indicates a frequency domain. A minimum transmission unit in the time domain is an OFDM symbol, and Nsymb number of OFDM symbols <NUM> are gathered to form one slot <NUM>. The length of a sub-frame may be defined as <NUM>, and a radio frame <NUM> may be defined as <NUM>. A minimum transmission unit in the frequency domain is a sub-carrier, and the bandwidth of the entire system transmission band may be configured by a total of NBW number of sub-carriers <NUM>. However, such a specific value may be variably applied according to systems.

A basic unit of the time-frequency resource region is a resource element <NUM> (hereinafter, RE), and may be indicated by an OFDM symbol index and a sub-carrier index. A resource block <NUM> (hereinafter, RB) or a physical resource block (hereinafter, PRB) may be defined by Nsymb number of consecutive OFDM symbols <NUM> in the time domain and NRB number of consecutive sub-carriers <NUM> in the frequency domain. Therefore, one RB <NUM> may include Nsymb * NRB number of REs <NUM>.

In general, a minimum transmission unit of data is an RB unit. In the <NUM> or NR system, generally, Nsymb is <NUM> (Nsymb = <NUM>) and NRB is <NUM> (NRB = <NUM>), and NBW and NRB may be proportional to the bandwidth of the system transmission band. A data rate is increased in proportion to the number of RBs scheduled for a terminal. In the <NUM> or NR system, in the case of an FDD system operated by dividing a downlink and an uplink by frequencies, a downlink transmission bandwidth and an uplink transmission bandwidth may be different from each other. A channel bandwidth indicates an RF bandwidth corresponding to a system transmission bandwidth. The following Table <NUM> indicates a corresponding relationship between a system transmission bandwidth and a channel bandwidth which are defined in an LTE system that is a 4th generation wireless communication system before the <NUM> or NR system. For example, the LTE system having a channel bandwidth of <NUM> has a transmission bandwidth including <NUM> RBs.

In the <NUM> or NR system, a terminal may operate in a wider channel bandwidth than the channel bandwidth of the LTE presented in Table <NUM>. Table <NUM> indicates a corresponding relationship among a system transmission bandwidth, a channel bandwidth, and sub-carrier spacing (SCS) in the <NUM> or NR system.

In the <NUM> or NR system, scheduling information for downlink data or uplink data is transmitted from a base station to a terminal through downlink control information (DCI). The DCI may be defined according to various formats, and indicate whether the DCI is scheduling information (UL grant) for uplink data or scheduling information (DL grant) for downlink data according to each format, whether the DCI is compact DCI having a small control information size, whether to apply spatial multiplexing using multiple antennas, whether the DCI is DCI for power control, and the like. For example, DCI format <NUM>-<NUM>, which is scheduling control information (DL grant) for downlink data, may include at least one piece of the following control information.

In a case of the above-mentioned PUSCH transmission, time domain resource assignment may be transmitted by information on a slot in which a PUSCH is transmitted, start OFDM symbol position S in a corresponding slot, and the number of OFDM symbols L to which the PUSCH is mapped. The S may be a relative position from the start of a slot, the L may be the number of consecutive OFDM symbols, and the S and L may be determined from a start and length indicator value (SLIV) defined as follows. If (L-<NUM>) ≤ <NUM> then
SLIV <NUM>*(L-<NUM>)+S
else
SLIV <NUM>*(<NUM>-L+<NUM>)+(<NUM>-<NUM>-S)
where <NUM> < L ≤ <NUM>-S.

In the <NUM> or NR system, generally, a table including, in one row, information on an SLIV value, a PUSCH mapping type, and a slot in which a PUSCH is transmitted may be configured through RRC configuration. Subsequently, in the time domain resource assignment of DCI, an index value in the configured table is indicated, so that a base station may transmit, to a terminal, information on the SLIV value, the PUSCH mapping type, and the slot in which the PUSCH is transmitted.

In the <NUM> or NR system, the PUSCH mapping type is defined as type A and type B. In PUSCH mapping type A, the first OFDM symbol among demodulation reference signal (DMRS) OFDM symbols is located in the second or third OFDM symbol in a slot. In PUSCH mapping type B, the first OFDM symbol among the DMRS OFDM symbols is located in the first OFDM symbol in a time domain resource allocated by PUSCH transmission. The above-mentioned PUSCH time domain resource assignment method may be equally applicable to PDSCH time domain resource assignment.

The DCI may be transmitted on a physical downlink control channel (PDCCH) (or control information, hereinafter, interchangeably used), through channel coding and modulation processes.

In general, the DCI is independently scrambled with a specific radio network temporary identifier (RNTI) (or terminal identifier) for each terminal, and cyclic redundancy check (CRC) is added, and after channel coding, each DCI is configured by an independent PDCCH and transmitted. The PDCCH is mapped in a control resource set (CORESET) configured for a terminal, and transmitted.

The downlink data may be transmitted on a PDSCH which is a physical channel for downlink data transmission. The PDSCH may be transmitted after a control channel transmission interval, and scheduling information such as a modulation scheme and a specific mapping position in the frequency domain is determined based on the DCI transmitted through the PDCCH.

Among control information configuring the DCI, through the MCS, the base station notifies the terminal of the modulation scheme applied to a PDSCH to be transmitted and the size of data to be transmitted (transport block size: TBS). In an embodiment, the MCS may be configured by <NUM> bits or more or fewer bits than <NUM> bits. The TBS corresponds to the size before channel coding for error correction is applied to data (transport block: TB) to be transmitted by the base station.

In the disclosure, a transport block (hereinafter, TB) may include a MAC header, a MAC control element (CE), one or more MAC service data units (SDUs), and padding bits. Alternatively, the TB may indicate a MAC protocol data unit (PDU) or a unit of data transmitted from a MAC layer to a physical layer.

The modulation scheme supported by the <NUM> or NR system includes quadrature phase shift keying (QPSK), <NUM> quadrature amplitude modulation (QAM), <NUM> QAM, and <NUM> QAM, and each modulation order (Qm) corresponds to <NUM>, <NUM>, <NUM>, or <NUM>. That is, <NUM> bits per symbol for QPSK modulation, <NUM> bits per OFDM symbol for <NUM> QAM modulation, and <NUM> bits per symbol for <NUM> QAM modulation may be transmitted, and <NUM> bits per symbol for <NUM> QAM modulation may be transmitted.

In a case where time resource allocation field index m included in the DCI is indicated when the base station schedules a PDSCH or PUSCH by the DCI to the terminal in the <NUM> or NR system, a table indicating time domain resource assignment information shows a combination of DRMS Type A position information corresponding to m+<NUM>, PDSCH mapping type information, slot index K<NUM>, data resource start symbol S, and data resource allocation length L. As an example, Table <NUM> is a table including time domain resource assignment information.

In Table <NUM>, dmrs-typeA-Position is a field indicating a position of a symbol in which a DMRS is transmitted in one slot indicated by a system information block (SIB) which is one of terminal common control information. A possible value for the corresponding field is <NUM> or <NUM>. When the number of symbols configuring one slot is a total of <NUM> and the first symbol index is <NUM>, <NUM> means the third symbol and <NUM> means the fourth symbol. In Table <NUM>, the PDSCH mapping type is information indicating a position of a DMRS in a scheduled data resource region. When the PDSCH mapping type is type A, the DMRS is always transmitted or received at a symbol position determined by dmrs-typeA-Position, regardless of an allocated data time domain resource. When the PDSCH mapping type is type B, the DMRS is always transmitted or received in a position of the first symbol of the allocated data time domain resource. In other words, the PDSCH mapping type B does not use dmrs-typeA-Position information. In Table <NUM>, K<NUM> denotes offsets of a slot index to which a PDCCH through which DCI is transmitted belongs and a slot index to which a PDSCH or PUSCH scheduled in the DCI belongs. As an example, when the slot index of the PDCCH is n, the slot index of the PDSCH or PUSCH scheduled by the DCI of the PDCCH is n+K<NUM>. In Table <NUM>, S denotes a start symbol index of a data time domain resource in one slot. The range of possible S values is usually <NUM> to <NUM> based on a normal cyclic prefix. In Table <NUM>, L denotes an interval length of the data time domain resource in one slot. The range of possible L values is <NUM> to <NUM>. However, the possible values of S and L are determined by the following Equation <NUM> and Table <NUM> or Table <NUM>. Table <NUM> may include values used by the terminal as a default before receiving time resource allocation information through terminal-specific or terminal-common higher layer signaling. As an example, DCI format 0_0 or 1_0 may always use Table <NUM> as a default time resource region value.

Table <NUM> includes a PDSCH time domain resource assignment value, and a K1 value is used instead of K2 for PUSCH time domain resource assignment. Table <NUM> below is an example of a PUSCH time domain resource assignment table.

The following Table <NUM> is a table showing a possible combination of S and L according to whether a cyclic prefix is normal or extended and whether a PDSCH mapping type is type A or type B.

The following Table <NUM> is a table showing a possible combination of S and L according to whether a cyclic prefix is normal or extended and whether a PUSCH mapping type is type A or type B.

In Table <NUM>, each index can be configured through a higher layer signaling parameter PDSCH-TimeDomainResourceAllocationList or PUSCH-TimeDomainResourceAllocationList.

PDSCH-TimeDomainResourceAllocationList is configured by one or multiple higher layer signaling parameter PDSCH-TimeDomainResourceAllocations, and PDSCH-TimeDomainResourceAllocation has k<NUM>, mappingtype, and startSymbol-AndLength. The range of possible values for k<NUM> is <NUM> to <NUM>. The mappingtype may correspond to type A or type B. The range of possible values for startSymbol-AndLength is <NUM> to <NUM>. As described above, when the mappingtype is type A, a symbol position of a DMRS follows a value indicated by dmrs-typeA-Position.

PUSCH-TimeDomainResourceAllocationList is configured by one or multiple higher layer signaling parameter PUSCH-TimeDomainResourceAllocations, and PUSCH-TimeDomainResourceAllocation has k<NUM>, mappingtype, and startSymbol-AndLength. The range of possible values for k<NUM> is <NUM> to <NUM>. The mappingtype may correspond to type A or type B. The range of possible values for startSymbol-AndLength is <NUM> to <NUM>. As described above, when the mappingtype is type A, a symbol position of a DMRS follows a value indicated by dmrs-typeA-Position.

The above-described PDSCH-TimeDomainResourceAllocation or PUSCH-TimeDomainResource Allocation is a time domain resource assignment method of a PDSCH or a PUSCH in one slot. Higher layer signaling aggregationFactorDL denotes the number of slots in which a PDSCH-TimeDomainResourceAllocation value applied in one slot is repeatedly transmitted. Higher layer signaling aggregationFactorUL denotes the number of slots in which a PUSCH-TimeDomainResourceAllocation value applied in one slot is repeatedly transmitted. The range of possible values for aggregationFactorDL and aggregationFactorUL is {<NUM>,<NUM>,<NUM>,<NUM>}. For example, when aggregationFactorDL is <NUM>, it means that one of possible PDSCH-TimeDomainResourceAllocations is repeatedly transmitted over a total of <NUM> slots. However, when at least a part of symbols applied to PDSCH-TimeDomainResourceAllocation in a specific slot is an uplink symbol, PDSCH transmission and reception of the corresponding slot is omitted. Similarly, when at least a part of symbols applied to PUSCH-TimeDomainResourceAllocation in a specific slot is a downlink symbol, PUSCH transmission and reception of the corresponding slot is omitted.

Next, a PUCCH will be described. First, in regard to a long PUCCH, since a control channel of a long transmission interval is used for the purpose of extending cell coverage, the long PUCCH may be transmitted in a DFT-S-OFDM scheme which is single carrier transmission, rather than OFDM transmission. Therefore, in this case, the PUCCH is required to be transmitted using only consecutive sub-carriers, and frequency hopping may be configured in order to obtain a frequency diversity effect. That is, when frequency hopping is applied (frequency hopping is enabled through a higher layer signal), an uplink control channel of a long transmission interval may be configured at a position where frequency resources are spaced apart from each other. When frequency hopping is not applied (frequency hopping is disabled through a higher layer signal), a control channel may be transmitted during a transmission symbol interval of the long PUCCH at a frequency position based on transmission start PRB information and PRB number information, which are configured in a higher layer signal. A separated distance in terms of frequency is required to be smaller than a bandwidth supported by the terminal. In the front part of a slot, a PUCCH is transmitted using PRB-<NUM>, which is a transmission start PRB configured by a higher layer signal. In the rear part of the slot, in a case that frequency hopping is configured, a PUCCH is transmitted using PRB-<NUM> spaced a frequency resource for the frequency hopping apart from PRB-<NUM>. In this discussion, a PRB is a physical resource block, which means a minimum transmission unit on the frequency side, and may be defined by <NUM> sub-carriers. Therefore, a frequency-side distance of PRB-<NUM> and PRB-<NUM> is required to be smaller than the maximum supported bandwidth of the terminal, and the maximum supported bandwidth of the terminal may be equal to or smaller than the bandwidth supported by the system.

The long PUCCH supports transmission formats such as PUCCH format <NUM>, PUCCH format <NUM>, and PUCCH format <NUM> according to the number of control information bits which can be supported, and whether terminal multiplexing is supported through Pre-DFT OCC support at the front end of IFFT. First, PUCCH format <NUM> is a long PUCCH format based on DFT-S-OFDM which can support control information of up to <NUM> bits. The control information may be configured by a combination of HARQ-ACK and a scheduling request (SR) or each of them. In PUCCH format <NUM>, an OFDM symbol including a DMRS, which is a demodulation reference signal (or reference signal), and an OFDM symbol including control information (uplink control information: UCI), are repeatedly configured.

For example, when the number of transmission symbols of PUCCH format <NUM> is <NUM> symbols, the transmission symbols include a DMRS symbol, a UCI symbol, a DMRS symbol, a UCI symbol, a DMRS symbol, a UCI symbol, a DMRS symbol, and a UCI symbol sequentially from the first start symbol of <NUM> symbols. According to the structure of the DMRS symbol, the DMRS symbol is spread using an orthogonal code (or orthogonal sequence or spreading code, w_i (m)) along the time axis and a sequence corresponding to the length of <NUM> RB along the frequency axis within one OFDM symbol, is IFFTed, and is then transmitted.

According to the structure of the UCI symbol, d (<NUM>) is generated by BPSK-modulating <NUM>-bit control information and QPSK-modulating <NUM>-bit control information, the generated d (<NUM>) is scrambled by multiplying the same by a sequence corresponding to the length of <NUM> RB along the frequency axis, and the scrambled sequence is spread using an orthogonal code (or orthogonal sequence or spreading code, w_i (m)) along the time axis, is IFFTed, and is then transmitted. The terminal generates a sequence, based on group hopping or sequence hopping configuration received through a higher layer signal from the base station and the configured ID, and generates a sequence corresponding to the length of <NUM> RB by cyclic shifting the generated sequence with an initial cyclic shift (CS) value configured through the higher layer signal.

w_i(m) is given as shown in following Table <NUM> according to a length (NSF) of the spreading code, wherein i denotes an index of the spreading code itself, and m denotes an index of elements of the spreading code. Here, the numbers in [ ] in Table <NUM> denote ϕ(m), for example, when the length of the spreading code is <NUM> and index i of the configured spreading code is <NUM> (i = <NUM>), spreading code w_i(m) is wi(<NUM>) = ej<NUM>π*<NUM>/NSF = <NUM>, wi(<NUM>) = ej<NUM>π*<NUM>/NSF = <NUM>, so that w_i (m) is [<NUM><NUM>] (w_i(m) = [<NUM><NUM>]).

Next, PUCCH format <NUM> is a long PUCCH format based on DFT-S-OFDM which can support control information of more than <NUM> bits. The control information may be configured by a combination of HARQ-ACK, channel state information (CSI), and an SR or each of them. A DMRS symbol position of PUCCH format <NUM> is shown in Table <NUM> according to whether frequency hopping is performed and an additional DMRS symbol is configured.

For example, when the number of transmission symbols of PUCCH format <NUM> is <NUM> symbols, the first start symbol of <NUM> symbols starts with <NUM>, and the DMRS is transmitted to the first symbol and the fifth symbol. The above table is also applied to a DMRS symbol position of PUCCH format <NUM> in the same manner.

Next, PUCCH format <NUM> is a long PUCCH format based on DFT-S-OFDM which can support control information of more than <NUM> bits. The control information may be configured by a combination of HARQ-ACK, CSI, and an SR or each of them. PUCCH format <NUM> differs from PUCCH format <NUM> in that in PUCCH format <NUM> of a plurality of terminals can be multiplexed within one RB. It is possible to multiplex PUCCH format <NUM> of a plurality of terminals by applying Pre-DFT OCC to the control information at the front end of the IFFT. However, the number of control information symbols that can be transmitted from one terminal decreases according to the number of terminals to be multiplexed.

Next, a short PUCCH will be described. The short PUCCH may be transmitted in both the downlink centric slot and the uplink centric slot and is generally transmitted in the last symbol of the slot or in an OFDM symbol (e.g., the last OFDM symbol, the second-to-last OFDM symbol, or the last two OFDM symbols) at the rear part. The short PUCCH can also be transmitted at an arbitrary position in the slot. The short PUCCH may be transmitted using one OFDM symbol or two OFDM symbols. Radio resources for the short PUCCH are allocated in units of PRB on the frequency side. As the allocated PRBs, one PRB or a plurality of contiguous PRBs may be allocated, or a plurality of PRBs away from the frequency band may also be allocated. The allocated PRB is required to be included in a band smaller than or equal to a frequency band supported by the terminal. In addition, in one PRB, uplink control information and a demodulation reference signal are required to be multiplexed in the frequency band. The multiplexing mapping is defined in the standard, the terminal transmits the short PUCCH according to the mapping scheme, and the base station demodulates the short PUCCH according to the mapping scheme. Alternatively, the terminal multiplexes and transmits the demodulation reference signal and the uplink control information according to a method indicated through reception of a higher layer signal. Alternatively, a method for transmitting a demodulation reference signal may be determined according to the number of bits of uplink control information. When the number of bits of the uplink control information is large, it is necessary to use many resources for transmission of the uplink control information to lower a transmission code rate.

The short PUCCH supports the transmission formats such as PUCCH format <NUM> and PUCCH format <NUM> according to the number of control information bits that can be supported. First, PUCCH format <NUM> is a short PUCCH format based on CP-OFDM which can support control information of up to <NUM> bits. The control information may be configured by a combination of HARQ-ACK and an SR or each of them. PUCCH format <NUM> has a structure which does not transmit a DMRS but transmits only a sequence mapped to <NUM> sub-carriers on the frequency axis within one OFDM symbol. The terminal generates a sequence, based on group hopping or sequence hopping configuration received through a higher layer signal from the base station and the configured ID, and cyclically shifts the generated sequence based on a final CS value obtained by adding another CS value to the indicated initial CS value according to ACK or NACK to be mapped to <NUM> sub-carriers so as to transmit the generated sequence. For example, if the HARQ-ACK is <NUM> bit, as shown in the following Table <NUM>, in a case of the ACK, the final CS is generated by adding <NUM> to the initial CS value, and in a case of the NACK, the final CS is generated by adding <NUM> to the initial CS. <NUM> which is the CS value for the NACK and <NUM> which is the CS value for the ACK are defined in the standard, and the terminal generates PUCCH format <NUM> according to the values all the time and transmits <NUM>-bit HARQ-ACK. (see Table <NUM>).

For example, when HARQ-ACK is <NUM> bits, as shown in Table <NUM> below, in a case of (NACK, NACK), the final CS is generated by adding <NUM> to the initial CS value, in a case of (NACK, ACK), the final CS is generated by adding <NUM> to the initial CS value, in a case of (ACK, ACK), the final CS is generated by adding <NUM> to the initial CS value, and in a case of (ACK, NACK), the final CS is generated by adding <NUM> to the initial CS value. <NUM> which is the CS value for (NACK, NACK), <NUM> which is the CS value for (NACK, ACK), <NUM> which is the CS value for (ACK, ACK), and <NUM> which is the CS value for (ACK, NACK) are defined in the standard, and the terminal generates PUCCH format <NUM> according to the above values all the time and transmits <NUM>-bit HARQ-ACK. (see Table <NUM>).

If the final CS value exceeds <NUM>, due to the CS value added according to the ACK or NACK to the initial CS value, it is obvious that the length of the sequence is <NUM>, and therefore modulo <NUM> is applied.

Next, PUCCH format <NUM> is a short PUCCH format based on CP-OFDM which can support control information of more than <NUM> bits. The control information may be configured by a combination of HARQ-ACK, CSI, and an SR or each of them. According to PUCCH format <NUM>, as indicated by reference numeral <NUM>, a position of a sub-carrier to which the DMRS is transmitted in one OFDM symbol is fixed to sub-carriers having indexes of #<NUM>, #<NUM>, #<NUM>, and #<NUM> when the index of the first sub-carrier is #<NUM>. The control information is mapped to the remaining sub-carriers excluding the sub-carriers in which the DMRS is located by being subjected to the channel encoding and then subjected to the modulation process.

The terminal receives configuration of PUCCH resource sets through a higher layer signal. The terminal selects the configured PUCCH resource sets according to the number of control information bits. In a specific slot, the terminal selects PUCCH resource set <NUM> when the number of control information bits required to be transmitted is <NUM> to <NUM>, selects PUCCH resource set <NUM> when the number of control information bits required to be transmitted is <NUM> to N<NUM>-<NUM>, selects PUCCH resource set <NUM> when the number of control information bits required to be transmitted is N2 to N<NUM>-<NUM>, and selects PUCCH resource set <NUM> when the number of control information bits required to be transmitted is N<NUM> to N<NUM>-<NUM>. All of the N<NUM>, N<NUM>, and N<NUM> may be a higher layer signal and received from the base station by the terminal in advance.

Each PUCCH resource set includes X number of PUCCH resources, and the X number of PUCCH resources include a resource for the short PUCCH (PUCCH format <NUM> or PUCCH format <NUM>) or a resource for the long PUCCH (PUCCH format <NUM>, PUCCH format <NUM>, or PUCCH format <NUM>). That is, each of the configured PUCCH resources includes all information required to transmit a specific PUCCH format (PUCCH format <NUM>, PUCCH format <NUM>, PUCCH format <NUM>, PUCCH format <NUM>, or PUCCH format <NUM>), and each PUCCH resource may be configured to transmit different PUCCH formats. X is a constant, and X may be differently configured by the higher layer signal for each PUCCH resource set. That is, PUCCH resource set <NUM> may be X = <NUM>, and the remaining PUCCH resource set <NUM>, <NUM>, and <NUM> may be X = <NUM>. Which of the X resources the terminal selects and whether to transmit the PUCCH format corresponding to the selected resource may be indicated through bits of a downlink control channel and may be induced through a transmission resource or a slot index of the downlink control channel, a unique ID of the terminal, and the like. Alternatively, the indication method through the downlink control channel and the induction method through the transmission resource or slot index of the downlink control channel, the unique identifier of the terminal, and the like may be combined to be indicated to the terminal.

The terminal receives or induces the indication scheme to select one PUCCH resource from the X number of PUCCH resources and transmit the control information through the corresponding PUCCH format. The PUCCH resource indication method can be applied only when the terminal can determine the PUCCH resource through the corresponding downlink control channel reception before HARQ-ACK transmission, like HARQ-ACK transmission. When the terminal does not receive the corresponding downlink control channel reception before the CSI or SR, like CSI or SR transmission, the terminal receives, in advance, the PUCCH format to be used at the time of the CSI or SR transmission and the required PUCCH resource through the higher layer signal from the base station, and in the slot for the CSI or SR transmission according to a period and offset configured by the higher layer signal from the base station, the terminal uses the configured PUCCH format in the configured PUCCH resource to transmit the CSI or SR.

Each PUCCH resource corresponding to the PUCCH format includes at least one of the following information.

The required information and the value range are summarized by Table <NUM> according to the respective PUCCH formats. If a value is not required to be configured in the following Table <NUM> or is <NUM> and therefore the value range is not required, the value is marked by N.

Hereinafter, with the short PUCCH, it is referred to as PUCCH format <NUM> or PUCCH format <NUM> unless specifically specified, and with the long PUCCH, it is referred to as PUCCH format <NUM>, PUCCH format <NUM>, or PUCCH format <NUM> unless specifically specified. In addition, in the disclosure, the transmission by PUCCH format X refers to the transmission by a specific PUCCH format corresponding to a PUCCH resource by using the PUCCH resource obtained by the method of the disclosure such as the indication, the induction, and the like from the base station unless specifically specified.

<FIG> is a view for explaining a method for allocating data for an eMBB, URLLC, and mMTC in a time-frequency resource region in a <NUM> or NR system according to an embodiment of the disclosure.

Referring to <FIG>, the data for the eMBB, URLLC, and mMTC may be allocated in the entire system frequency band (e.g., system bandwidth) <NUM>. When URLLC data <NUM>, <NUM>, and <NUM> are generated and are thus required to be transmitted while an eMBB <NUM> and an mMTC <NUM> are allocated and transmitted in a specific frequency band, the eMBB <NUM> and the mMTC <NUM> may transmit the URLLC data <NUM>, <NUM>, and <NUM> without emptying or transmitting a portion which has been already allocated. Among the above-described services, since the URLLC is required to reduce latency, the URLLC data may be allocated and transmitted to a part of a resource to which the eMBB or mMTC is allocated. When the URLLC is additionally allocated and transmitted in the resource to which the eMBB is allocated, eMBB data may not be transmitted in the overlapped time-frequency resource, and thus transmission performance of the eMBB data may be lowered. That is, eMBB data transmission failure due to URLLC allocation may occur.

<FIG> illustrates a method for configuring a semi-static HARQ-ACK codebook in an NR system according to an embodiment of the disclosure.

Referring to <FIG>, in a situation in which a HARQ-ACK PUCCH that a terminal can transmit in one slot is limited to one, if the terminal receives semi-static HARQ-ACK codebook higher layer configuration, the terminal reports HARQ-ACK information for PDSCH reception or SPS PDSCH release in a HARQ-ACK codebook in a slot indicated by a value of a PDSCH-to-HARQ_feedback timing indicator in DCI format 1_0 or DCI format 1_1. The terminal reports a HARQ-ACK information bit value in the HARQ-ACK codebook as NACK in a slot which is not indicated by a PDSCH-to-HARQ_feedback timing indicator field in DCI format 1_0 or DCI format 1_1. If the terminal reports only HARQ-ACK information for one SPS PDSCH release or one PDSCH reception in MA,C cases for candidate PDSCH reception, and the report is scheduled by DCI format 1_0 including information indicating that a counter DACI field is <NUM> in a Pcell, the terminal determines one HARQ-ACK codebook for the corresponding SPS PDSCH release or the corresponding PDSCH reception.

Otherwise, the terminal follows a HARQ-ACK codebook determination method according to the method described below.

Assuming that a set of PDSCH reception candidate occasions in serving cell c is MA,c , MA,c can be obtained in the following [pseudo-code <NUM>] operations. <IMG>
<IMG>.

When the above-described pseudo-code <NUM> is described with reference to <FIG>, in order to perform HARQ-ACK PUCCH transmission in slot #k <NUM>, all of slot candidates capable of PDSCH-to-HARQ-ACK timing which can indicate slot #k <NUM> are considered. Referring to <FIG>, it is assumed that only the PDSCHs scheduled in slot #n <NUM>, slot #n+<NUM><NUM>, and slot #n+<NUM><NUM> can be used for HARQ-ACK transmission in slot #k <NUM> by a possible combination of the PDSCH-to-HARQ-ACK timing. In addition, the maximum number of PDSCHs which can be scheduled for each slot is derived in consideration of time domain resource configuration information of PDSCHs which can be scheduled in the slots <NUM>, <NUM>, and <NUM>, respectively, and information indicating whether symbols in the slots are downlink or uplink symbols. For example, when the maximum scheduling is possible for <NUM> PDSCHs in the slot <NUM>, <NUM> PDSCHs in the slot <NUM>, and <NUM> PDSCHs in the slot <NUM>, the maximum number of PDSCHs included in a HARQ-ACK codebook transmitted from the slot <NUM> is <NUM> in total. This is referred to as cardinality of the HARQ-ACK codebook.

<FIG> illustrates a method for configuring a dynamic HARQ-ACK codebook in an NR system according to an embodiment of the disclosure.

Referring to <FIG>, a terminal transmits HARQ-ACK information transmitted in one PUCCH in the corresponding slot n, based on a PDSCH-to-HARQ_feedback timing value for PUCCH transmission of HARQ-ACK information in slot n for PDSCH reception or SPS PDSCH release and K0, which is transmission slot position information of a PDSCH scheduled by DCI format 1_0 or 1_1. Specifically, in order to transmit the above-described HARQ-ACK information, the terminal determines a HARQ-ACK codebook of the PUCCH transmitted from the slot determined by the PDSCH-to-HARQ_feedback timing and K0, based on DAI included in DCI indicating PDSCH or SPS PDSCH release.

The DAI is configured by counter DAI and total DAI. The counter DAI is information in which HARQ-ACK information corresponding to a PDSCH scheduled by DCI format 1_0 or DCI format 1_1 indicates a position in the HARQ-ACK codebook. Specifically, a value of the counter DAI in DCI format 1_0 or 1_1 indicates a cumulative value of SPS PDSCH release or PDSCH reception scheduled by DCI format 1_0 or DCI format 1_1 in specific cell c. The accumulated value is configured based on a serving cell and a PDCCH monitoring occasion where the scheduled DCI exists.

The total DAI is a value indicating the size of the HARQ-ACK codebook. Specifically, a value of total DAI refers to the total number of SPS PDSCH releases or previously scheduled PDSCHs including a time point when the DCI is scheduled. In addition, the total DAI is a parameter used when HARQ-ACK information in serving cell c also includes HARQ-ACK information for a PDSCH scheduled in another cell including the serving cell c in a carrier aggregation (CA) situation. In other words, there is no total DAI parameter in a system operating with one cell.

An example of an operation for the DAI is shown in <FIG> shows a change in the values of counter DAI (C-DAI) and total DAI (T-DAI) indicated by DCI discovered for at each PDCCH monitoring occasion configured for each carrier, when the terminal transmits a HARQ-ACK codebook selected based on the DAI in a n-th slot of carrier <NUM><NUM> to a PUCCH <NUM> in a situation in which two carriers are configured. First, in the DCI discovered at m = <NUM><NUM>, each of the C-DAI and T-DAI indicates a value <NUM> of <NUM>. In the DCI discovered at m = <NUM><NUM>, each of the C-DAI and T-DAI indicates a value <NUM> of <NUM>. In the DCI discovered in carrier <NUM> (c = <NUM>) <NUM> of m = <NUM><NUM>, the C-DAI indicates a value <NUM> of <NUM>. In the DCI discovered in carrier <NUM> (c = <NUM>) <NUM> of m = <NUM><NUM>, the C-DAI indicates a value <NUM> of <NUM>. In this case, when carriers <NUM> and <NUM> are scheduled in the same monitoring occasion, all of the T-DAIs are indicated as <NUM>.

Referring to <FIG> and <FIG>, the HARQ-ACK codebook determination is operated in a situation in which only one PUCCH including HARQ-ACK information is transmitted in one slot. This is referred to as mode <NUM>. As an example of a method in which one PUCCH transmission resource is determined in one slot, when PDSCHs scheduled in different DCIs are multiplexed with one HARQ-ACK codebook and transmitted in the same slot, a PUCCH resource selected for HARQ-ACK transmission is determined as a PUCCH resource indicated by a PUCCH resource field indicated by DCI in which a PDSCH is lastly scheduled. That is, a PUCCH resource indicated by a PUCCH resource field indicated by DCI scheduled before the DCI is ignored.

The following description defines methods and apparatuses for determining a HARQ-ACK codebook in a situation in which two or more PUCCHs including HARQ-ACK information can be transmitted in one slot. This is referred to as mode <NUM>. A terminal may be able to operate only in mode <NUM> (transmit only one HARQ-ACK PUCCH in one slot) or in mode <NUM> (transmit one or more HARQ-ACK PUCCHs in one slot). Alternatively, a terminal supporting both mode <NUM> and mode <NUM> may configure such that a base station operates only in one mode by higher layer signaling, or implicitly determine mode <NUM> and mode <NUM> by DCI format, RNTI, a DCI specific field value, scrambling, and the like. For example, a PDSCH scheduled by DCI format A and HARQ-ACK information associated therewith are based on mode <NUM>, and a PDSCH scheduled by DCI format B and HARQ-ACK information associated therewith are based on mode <NUM>.

Next, provided is an operation method of a terminal in a case where a terminal performs one or more HARQ-ACK transmissions in one slot, one or more PUCCHs including HARQ-ACK are transmitted in one slot, and the PUCCHs overlap, in a specific OFDM symbol, with another PUCCH including channel information or scheduling request information, that is, a PUCCH and a PUCCH collide with each other. In addition, provided is an operation method of a terminal in a case where the PUCCHs and a PUSCH for transmitting uplink data information are overlappingly transmitted in a specific OFDM symbol, that is, a PUCCH and a PUSCH collide with each other.

<FIG> shows embodiment <NUM> in a case where one or more PUCCHs including HARQ-ACK are transmitted in one slot, and the PUCCHs overlap, in a specific OFDM symbol, with another PUCCH including channel information or scheduling request information, that is, a PUCCH and a PUCCH collide with each other according to an embodiment of the disclosure.

Referring to <FIG>, first, a terminal receives simultaneousHARQ-ACK-CSI from a base station through a higher layer signal. When a collision between a PUCCH including CQI/SR and a PUCCH including HARQ-ACK occurs in a specific OFDM symbol, as in embodiment <NUM> of the disclosure, the terminal which receives the higher layer signal attempts a method to be described in the disclosure to multiplex uplink control information such as the CQI/SR and the HARQ-ACK. If the terminal fails to receive simultaneousHARQ-ACK-CSI from the base station through a higher layer signal, the terminal may drop the CQI. If the terminal transmits a positive SR, the terminal may multiplex the SR with the HARQ-ACK. If the terminal transmits a negative SR, the terminal may transmit only the HARQ-ACK.

Referring to <FIG>, the terminal receives configuration from the base station in advance through the higher layer signal, with respect to a transmission occasion for a CQI/SR <NUM>, a transmission resource, a parameter related to transmission, and information to be transmitted. Therefore, the terminal is required to transmit the CQI/SR <NUM> in slot #n, and is aware of a time resource and a frequency resource required to perform transmission. In addition, the terminal determines a PUCCH resource set according to the information bit size of HARQ-ACK <NUM><NUM>, and is aware of a time resource and a frequency resource required to transmit HARQ-ACK <NUM><NUM> from a PUCCH resource determined by a PDCCH resource or a specific field through a PDCCH.

Next, the terminal receives a PDSCH corresponding to HARQ-ACK <NUM><NUM> before slot #n <NUM>, and determines whether a processing time required to decode the PDSCH and prepare for transmission of HARQ-ACK <NUM><NUM>, that is, a value, obtained by adding the processing time after the last symbol of the PDSCH, is located before the first symbol of a transmission time resource of the CQI/SR <NUM>. Otherwise, the terminal may not be required to determine the processing time for HARQ-ACK <NUM><NUM>. The reason is that the base station is required to schedule the PDSCH corresponding to HARQ-ACK <NUM><NUM> in consideration of the processing time for HARQ-ACK <NUM><NUM> and the first symbol of the time resource of the CQI/SR <NUM>. Otherwise, the terminal may determine the case as an error. In this case, the base station cannot predict a procedure to be applied by the terminal for the case, and a terminal procedure may be terminal implementation.

The processing time is given as a constant value after the last symbol of the PDSCH, wherein the constant value T is (N1 +d_11+<NUM>)*(<NUM>+<NUM>)*k*<NUM>^(-u)*T_c. N1 is a value related to processing capability of the terminal, and is a constant determined based on sub-carrier spacing (u) of the PDCCH or PDSCH. d_11 is a constant determined based on the number of PDSCH symbols. K = <NUM>, and T_c is the basic time unit of NR and is <NUM>/(<NUM>*<NUM>^<NUM>*<NUM>).

If it is determined that the value, obtained by adding the processing time after the last symbol of the PDSCH, is located before the first symbol of the transmission time resource of the CQI/SR <NUM>, or without the above determination, the terminal selects a PUCCH resource set as the size of the sum of information bits of the CQI/SR <NUM> and HARQ-ACK <NUM><NUM>. Subsequently, the terminal determines a new time resource and frequency resource A of a PUCCH required to transmit the CQI/SR <NUM> and HARQ-ACK <NUM><NUM> from the PUCCH resource determined by the PDCCH resource or the specific field through the PDCCH. Next, the terminal determines a PUCCH resource set according to the information bit size of HARQ-ACK <NUM><NUM>, and is aware of a time resource and a frequency resource required to transmit HARQ-ACK <NUM><NUM> from the PUCCH resource determined by the PDCCH resource or the specific field through the PDCCH.

A case in which the resource A does not overlap with HARQ-ACK <NUM><NUM> in a specific OFDM symbol will be described. In order to multiplex HARQ-ACK <NUM><NUM> with the CQI/SR <NUM> and HARQ-ACK <NUM><NUM>, the terminal does not determine whether, in the frequency resource A, a processing time for HARQ-ACK <NUM><NUM>, that is, a processing time required to decode the PDSCH and prepare for transmission of HARQ-ACK <NUM><NUM> is located before a time resource of the frequency resource A. That is, the terminal transmits the CQI/SR <NUM> and HARQ-ACK <NUM><NUM> through the PUCCH of the resource A, determines a PUCCH resource set of HARQ-ACK <NUM><NUM> according to the information bit size of HARQ-ACK <NUM><NUM>, and transmits HARQ-ACK <NUM><NUM> through a separate PUCCH through a time resource and a frequency resource required to transmit HARQ-ACK <NUM><NUM> from a PUCCH resource determined by a PDCCH resource or a specific field through a PDCCH.

Next, a case in which the resource A overlaps with HARQ-ACK <NUM><NUM> in a specific OFDM symbol will be described. When the resource A and a resource of HARQ-ACK <NUM><NUM> overlap with each other in a specific OFDM symbol, the terminal does not perform the procedure of multiplexing the CQI/SR <NUM> and HARQ-ACK <NUM><NUM>, and may drop the CQI/SR <NUM>. Alternatively, the terminal may perform transmission by dropping only the CQI and multiplexing the SR with HARQ-ACK <NUM>. Therefore, when the SR is a positive SR, the terminal determines a PUCCH resource set for transmitting HARQ-ACK <NUM><NUM> or HARQ-ACK <NUM><NUM> and the SR, according to the information bit size of HARQ-ACK <NUM><NUM> or the sum of HARQ-ACK <NUM><NUM> and the SR. Subsequently, the terminal transmits HARQ-ACK <NUM><NUM> or HARQ-ACK <NUM> and the SR by using a PUCCH in a time resource and a frequency resource required to transmit HARQ-ACK <NUM><NUM> or HARQ-ACK <NUM> and the SR from a PUCCH resource determined by a PDCCH resource or a specific field through a PDCCH. In addition, the terminal determines a PUCCH resource set of HARQ-ACK <NUM><NUM> according to the information bit size of HARQ-ACK <NUM><NUM>, and transmits HARQ-ACK <NUM><NUM> through a separate PUCCH through a time resource and a frequency resource required to transmit HARQ-ACK <NUM><NUM> from the PUCCH resource determined by the PDCCH resource or the specific field through the PDCCH.

As in embodiment <NUM> described above, a plurality of HARQ-ACKs are transmitted in one slot via a separate PUCCH through the terminal procedure, so that if there is an urgent downlink data transmission such as URLLC, it is possible to satisfy a latency condition of the URLLC by directly providing HARQ-ACK feedback.

If HARQ-ACK <NUM><NUM> exists, the terminal may repeat the procedures performed in HARQ-ACK <NUM><NUM>, and thus apply the procedures to HARQ-ACK <NUM><NUM>. The procedures may be equally applied to the case where there are N, which is <NUM> or more, number of HARQ-ACKs to be transmitted in slot n <NUM>.

Referring to <FIG>, first, a terminal receives simultaneousHARQ-ACK-CSI from a base station through a higher layer signal. When a collision between a PUCCH including HARQ-ACK and a PUCCH including CQI/SR occurs in a specific OFDM symbol, as in embodiment <NUM> of the disclosure, the terminal which receives the higher layer signal attempts a method to be described in the disclosure to multiplex uplink control information such as the HARQ-ACK and the CQI/SR. If the terminal fails to receive simultaneousHARQ-ACK-CSI from the base station through a higher layer signal, the terminal may drop the CQI. If the terminal transmits a positive SR, the terminal may multiplex the SR with the HARQ-ACK. If the terminal transmits a negative SR, the terminal may transmit only the HARQ-ACK.

The processing time is given as a constant value after the last symbol of the PDSCH, and the constant value T is (N1 +d_11+<NUM>)*(<NUM>+<NUM>)*k*<NUM>^(-u)*T_c. N1 is a value related to processing capability of the terminal, and is a constant determined based on sub-carrier spacing (u) of the PDCCH or PDSCH. d_11 is a constant determined based on the number of PDSCH symbols. K = <NUM>, and T_c is the basic time unit of NR and is <NUM>/(<NUM>*<NUM>^<NUM>*<NUM>).

Next, a case in which the resource A overlaps with HARQ-ACK <NUM><NUM> in a specific OFDM symbol will be described. When the resource A and HARQ-ACK <NUM><NUM> overlap with each other in a specific OFDM symbol, the terminal does not perform the above procedure of multiplexing the CQI/SR <NUM> and HARQ-ACK <NUM><NUM>, and may drop the CQI/SR <NUM>. Alternatively, the terminal may perform transmission by dropping only the CQI and multiplexing the SR with HARQ-ACK <NUM>. Therefore, when the SR is a positive SR, the terminal determines a PUCCH resource set for transmitting HARQ-ACK <NUM><NUM> or HARQ-ACK <NUM><NUM> and the SR, according to the information bit size of HARQ-ACK <NUM><NUM> or the sum of HARQ-ACK <NUM><NUM> and the SR. Subsequently, the terminal transmits HARQ-ACK <NUM><NUM> or HARQ-ACK <NUM> and the SR by using a PUCCH in a time resource and a frequency resource required to transmit HARQ-ACK <NUM><NUM> or HARQ-ACK <NUM> and the SR from a PUCCH resource determined by a PDCCH resource or a specific field through a PDCCH. In addition, the terminal determines a PUCCH resource set of HARQ-ACK <NUM><NUM> according to the information bit size of HARQ-ACK <NUM><NUM>, and transmits HARQ-ACK <NUM><NUM> through a separate PUCCH through a time resource and a frequency resource required to transmit HARQ-ACK <NUM><NUM> from the PUCCH resource determined by the PDCCH resource or the specific field through the PDCCH.

<FIG> shows embodiment <NUM> in a case where one or more PUCCHs including HARQ-ACK are transmitted in one slot, and the PUCCHs overlap, in a specific OFDM symbol, with a PUSCH for transmitting uplink data information, that is, a PUCCH and a PUSCH collide with each other according to an embodiment of the disclosure.

Referring to <FIG>, first, when a terminal has simultaneous PUSCH/PUCCH transmission capability and transmits the capability to a base station, the terminal may receive simultaneousPUSCH-PUCCH from the base station through a higher layer signal.

When a collision between a PUCCH including HARQ-ACK and a PUSCH required to transmit a shared channel (UL-SCH) occurs in a specific OFDM symbol, as in embodiment <NUM> of the disclosure, the terminal having received the higher layer signal can transmit the PUCCH and the PUSCH at the same time. If the terminal does not have a simultaneous PUSCH/PUCCH transmission capability or has a simultaneous PUSCH/ PUCCH transmission capability but has not received simultaneousPUSCH-PUCCH from the base station through a higher layer signal even after transmitting the capability to the base station, the terminal may transmit a PUCCH and drop a PUSCH. Alternatively, the terminal may transmit a channel prioritized according to the service type of the terminal, and may drop the remaining channels. The above service type or priority may be received by the terminal from a CORESET or search space having a priority or a PDCCH having a priority or a specific field of a PDCCH transmitted by the base station.

Referring to <FIG>, the terminal receives a transmission resource for a PUSCH <NUM> and a parameter related to transmission from the base station through a higher layer signal and a PDCCH. In addition, the terminal determines a PUCCH resource set according to the information bit size of HARQ-ACK <NUM><NUM>, and is aware of a time resource and a frequency resource required to transmit HARQ-ACK <NUM><NUM> from a PUCCH resource determined by a PDCCH resource or a specific field through a PDCCH.

Next, the terminal receives a PDSCH corresponding to HARQ-ACK <NUM><NUM> before slot #n <NUM>, and determines whether a processing time required to decode the PDSCH and prepare for transmission of HARQ-ACK <NUM><NUM>, that is, a value, obtained by adding the processing time after the last symbol of the PDSCH, is located before the first symbol of a transmission time resource of the PUSCH <NUM>.

If it is determined that the value, obtained by adding the processing time after the last symbol of the PDSCH, is located before the first symbol of the transmission time resource of the PUSCH <NUM>, the terminal multiplexes HARQ-ACK <NUM><NUM> with the PUSCH <NUM>. Next, the terminal determines a PUCCH resource set for transmitting HARQ-ACK <NUM><NUM> according to the information bit size of HARQ-ACK <NUM><NUM>. The terminal is aware of a time resource and a frequency resource required to transmit HARQ-ACK <NUM><NUM> from a PUCCH resource determined by a PDCCH resource or a specific field through a PDCCH.

A case where the PUSCH <NUM> does not overlap with HARQ-ACK <NUM><NUM> in a specific OFDM symbol, or a case where the terminal receives simultaneousPUSCH-PUCCH even when the PUSCH <NUM> overlaps with HARQ-ACK <NUM><NUM> in a specific OFDM symbol will be described. In this case, in order to multiplex HARQ-ACK <NUM><NUM> with the PUSCH <NUM>, the terminal does not determine whether a processing time for a resource of the PUSCH <NUM> and HARQ-ACK <NUM><NUM>, that is, a processing time required to decode the PDSCH and prepare for transmission of HARQ-ACK <NUM><NUM> is located before a time resource of the PUSCH <NUM>. That is, the terminal transmits the PUSCH multiplexed with HARQ-ACK <NUM><NUM> in a resource of the PUSCH <NUM>. In addition, the terminal determines a PUCCH resource set of HARQ-ACK <NUM><NUM> according to the information bit size of HARQ-ACK <NUM><NUM>, and transmits HARQ-ACK <NUM><NUM> through a separate PUCCH through a time resource and a frequency resource required to transmit HARQ-ACK <NUM><NUM> from a PUCCH resource determined by a PDCCH resource or a specific field through a PDCCH.

Next, a case in which the PUSCH <NUM> overlaps with HARQ-ACK <NUM><NUM> in a specific OFDM symbol will be described. That is, if the terminal fails to receive simultaneousPUSCH-PUCCH, or does not have simultaneous PUSCH/PUCCH capability, the terminal does not perform the above procedure of multiplexing the PUSCH <NUM> and HARQ-ACK <NUM><NUM>, and may drop the PUSCH <NUM>. Therefore, the terminal determines a PUCCH resource set according to the information bit size of HARQ-ACK <NUM><NUM>, and transmits HARQ-ACK <NUM><NUM> by using a PUCCH in a time resource and a frequency resource required to transmit HARQ-ACK <NUM><NUM> from a PUCCH resource determined by a PDCCH resource or a specific field through a PDCCH. In addition, the terminal determines a PUCCH resource set according to the information bit size of HARQ-ACK <NUM><NUM>, and transmits HARQ-ACK <NUM><NUM> through a separate PUCCH through a time resource and a frequency resource required to transmit HARQ-ACK <NUM><NUM> from the PUCCH resource determined by the PDCCH resource or the specific field through the PDCCH. In the above, an example of dropping the PUSCH and transmitting HARQ-ACK <NUM><NUM> and HARQ-ACK <NUM><NUM> has been described, but the terminal may transmit the PUSCH <NUM> when a prioritized channel is the PUSCH <NUM> according to the service type of the terminal, and may drop PUCCHs which are the remaining channels.

As in embodiment <NUM> described above, a plurality of HARQ-ACKs are transmitted in one slot via a separate PUCCH through a terminal procedure, so that if there is an urgent downlink data transmission such as URLLC, it is possible to satisfy a latency condition of the URLLC by directly providing HARQ-ACK feedback.

When a collision between a PUSCH required to transmit a UL-SCH and a PUCCH including HARQ-ACK occurs in a specific OFDM symbol, as in embodiment <NUM> of the disclosure, the terminal having received the higher layer signal can transmit the PUCCH and the PUSCH at the same time. If the terminal does not have a simultaneous PUSCH/PUCCH transmission capability or has a simultaneous PUSCH/PUCCH transmission capability but has not received simultaneousPUSCH-PUCCH from the base station through a higher layer signal even after transmitting the capability to the base station, the terminal may transmit a PUCCH and drop a PUSCH. Alternatively, the terminal may transmit a channel prioritized according to the service type of the terminal, and may drop the remaining channels. The above service type or priority may be received by the terminal from a CORESET or search space having a priority or a PDCCH having a priority or a specific field of a PDCCH transmitted by the base station.

Next, the terminal receives a PDCCH for scheduling the PUSCH <NUM> before slot #n <NUM>, and determines whether a processing time required to decode the PDDCH and prepare for transmission of the PUSCH <NUM>, that is, a value, obtained by adding the processing time after the last symbol of the PDDCH, is located before the first symbol of a transmission time resource of HARQ-ACK <NUM><NUM>.

The processing time is given as a constant value after the last symbol of the PDCCH, and the constant value T is max{(N2 +d_21+<NUM>)*(<NUM>+<NUM>)*k*<NUM>^(-u)*T_c, d_22}. N2 is a value related to processing capability of the terminal, and is a constant determined based on sub-carrier spacing (u) of the PDCCH or PUSCH. d_21 is a constant determined based on whether the first symbol of the PUSCH is configured by a DMRS only. K = <NUM>, and T_c is the basic time unit of NR and is <NUM>/(<NUM>*<NUM>^<NUM>*<NUM>). d_22 is a constant related to the switching of a BWP.

If it is determined that the value, obtained by adding the processing time after the last symbol of the PDCCH for scheduling the PUSCH, is located before the first symbol of the transmission time resource of HARQ-ACK <NUM><NUM>, the terminal multiplexes HARQ-ACK <NUM><NUM> with the PUSCH <NUM>. Next, the terminal determines a PUCCH resource set for transmitting HARQ-ACK <NUM><NUM> according to the information bit size of HARQ-ACK <NUM><NUM>. The terminal is aware of a time resource and a frequency resource required to transmit HARQ-ACK <NUM><NUM> from a PUCCH resource determined by a PDCCH resource or a specific field through a PDCCH.

A case where the PUSCH <NUM> does not overlap with HARQ-ACK <NUM><NUM> in a specific OFDM symbol, or a case where the terminal receives simultaneousPUSCH-PUCCH even when the PUSCH <NUM> overlaps with HARQ-ACK <NUM><NUM> in a specific OFDM symbol will be described. In this case, the terminal transmits the PUSCH multiplexed with HARQ-ACK <NUM><NUM> in a resource of the PUSCH <NUM>. In addition, the terminal determines a PUCCH resource set of HARQ-ACK <NUM><NUM> according to the information bit size of HARQ-ACK <NUM><NUM>, and transmits HARQ-ACK <NUM><NUM> through a separate PUCCH through a time resource and a frequency resource required to transmit HARQ-ACK <NUM><NUM> from a PUCCH resource determined by a PDCCH resource or a specific field through a PDCCH.

<FIG> is a block diagram showing a structure of a terminal according to an embodiment of the disclosure.

Referring to <FIG>, a terminal of the disclosure may include a terminal receiver <NUM>, a terminal transmitter <NUM>, and a terminal processor <NUM>. The terminal receiver <NUM> and the terminal transmitter <NUM> may be collectively referred to as a transceiver in an embodiment. The transceiver may transmit or receive a signal to or from a base station. To this end, the transceiver may include an RF transmitter configured to up-convert and amplify a frequency of a transmitted signal, and an RF receiver configured to amplify a received signal with low noise, and down-convert a frequency of the signal. In addition, the transceiver may receive a signal through a wireless channel, output the signal to the terminal processor or controller <NUM>, and transmit the signal output from the terminal processor <NUM> through the wireless channel. The terminal processor <NUM> may control a series of processes such that the terminal can operate according to the above-described embodiments.

<FIG> is a block diagram showing a structure of a base station according to an embodiment of the disclosure.

Referring to <FIG>, in an embodiment, a base station may include at least one of a base station receiver <NUM>, a base station transmitter <NUM>, and a base station processor <NUM>. The base station receiver <NUM> and the base station transmitter <NUM> may be collectively referred to as a transceiver in an embodiment. The transceiver may transmit or receive a signal to or from a terminal. To this end, the transceiver may include an RF transmitter configured to up-convert and amplify a frequency of a transmitted signal, and an RF receiver configured to amplify a received signal with low noise, and down-convert a frequency of the signal. In addition, the transceiver may receive a signal through a wireless channel, output the signal to the base station processor or controller <NUM>, and transmit the signal output from the base station processor <NUM> through the wireless channel. The base station processor <NUM> may control a series of processes such that the base station can operate according to the above-described embodiments.

Claim 1:
A method performed by a terminal in a wireless communication system, the method comprising:
receiving, from a base station, information configuring simultaneous transmission of hybrid automatic repeat request acknowledgement, HARQ-ACK, and channel state information, CSI;
identifying whether a timing obtained by adding a processing time of the terminal after a last symbol of a physical downlink shared channel, PDSCH, reception is before a first symbol of a first physical uplink control channel, PUCCH, resource for a channel quality information, CQI, and a scheduling request, SR, based on the information;
in case that the timing is before the first symbol of the first PUCCH resource, identifying an uplink resource for transmitting a first HARQ-ACK corresponding to the PDSCH reception, the CQI, and the SR;
identifying whether the uplink resource overlaps with a second PUCCH resource for a second HARQ-ACK; and
transmitting, to the base station, the first HARQ-ACK, the CQI, and the SR on the uplink resource, and the second HARQ-ACK on the second PUCCH resource, in case that the uplink resource does not overlap with the second PUCCH resource.