Apparatus and method for transmitting uplink control information in network coordinated communication

Abstract

The disclosure relates to a communication technology and system for integrating a 5G communication system with an IoT technology to support a higher data transmission rate after a 4G system. The disclosure can be applied to intelligent services (e.g., smart home, smart building, smart city, smart car or connected car, health care, digital education, retail, security and safety-related services, etc.) based on 5G communication technology and IoT-related technology.

Description

TECHNICAL FIELD

[0001] The disclosure relates to a wireless communication system, and more particularly, to a method and apparatus for transmitting uplink control information by a terminal to multiple transmission points / panels / beams for cooperative communication between the multiple transmission points / panels / beams. BACKGROUND

[0002] To meet the increasing demand for wireless data traffic since the deployment of the fourth generation (4G) communication systems, efforts have been made to develop an improved fifth generation (5G) or pre-5G communication system. Therefore, the 5G or pre-5G communication system is also called a 'beyond 4G network' or a 'post long term evolution (LTE) system'. The 5G communication system is considered to be implemented in higher frequency (mmWave) bands, e.g., 60 kilohertz (kHz) bands, so as to accomplish higher data rates. 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 are discussed in 5G communication systems. In addition, in 5G communication systems, development for system network improvement is under way based on advanced small cells, cloud radio access networks (RANs), ultra-dense networks, a device-to-device (D2D) communication, a wireless backhaul, a moving network, a cooperative communication, coordinated multi-points (CoMP), a reception-end interference cancellation and the like. In the 5G 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), a non-orthogonal multiple access (NOMA), and a sparse code multiple access (SCMA) as an advanced access technology have been developed.

[0003] The Internet, which is a human centered network, is now evolving to the Internet of things (IoT) where distributed entities, such as things, exchange and process information without human intervention. The Internet of everything (IoE), which is a combination of the IoT technology and a big data processing technology through connection with a cloud server, has emerged. As the IoT technology requires a 5G communication system for its implementation, such as a "sensing technology", "a wired / wireless communication and network infrastructure", "a service interface technology", and "a security technology", research is being conducted on a sensor network, a machine-to-machine (M2M) communication network, and a machine type communication (MTC) network in order to provide a variety of services such as a smart home, a smart building, a smart city, a smart car, a health care, an advanced medical service, and an intelligent distribution grid and security / safety through the combination of the IoT technology with the big data processing technology and the cloud server.

[0004] Various attempts have been made to apply the 5G communication system to the IoT network. For example, technologies, such as a sensor network technology, an MTC technology, and an M2M communication technology, can be implemented by beamforming, MIMO, and array antennas. The application of a cloud radio access network (RAN) as the above-described big data processing technology can also be considered as an example of convergence of the 5G technology with the IoT technology.

[0005] The above information is presented as background information only to assist with an understanding of the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art with regard to the present disclosure. SUMMARY

[0006] TECHNICAL PROBLEM

[0007] The present disclosure provides a method for transmitting uplink control information by a terminal to multiple transmission points / panels / beams for network cooperation in a wireless communication system.

[0008] SOLUTION TO PROBLEM

[0009] To address the above-described problem, an embodiment according to the present disclosure includes a method performed by a terminal in a wireless communication system, the method including receiving, from a base station, configuration information including information on at least one repetition number and information on at least one transmission timing of a hybrid automatic repeat request (HARQ) feedback transmission, receiving, from the base station, downlink control information (DCI) including information indicating one of the at least one transmission timing and information indicating one of the at least one repetition number, receiving data from the base station in a plurality of first slots based on the repetition number indicated by the DCI, and transmitting, to the base station, the HARQ feedback in a plurality of second slots determined based on the plurality of first slots, wherein the HARQ feedback is set to a negative acknowledgement (NACK) in slots among the plurality of second slots other than a slot determined based on the transmission timing indicated by the DCI.

[0010] To address the above-described problem, an embodiment according to the present disclosure includes a method performed by a base station in a wireless communication system, the method including transmitting, to a terminal, configuration information including information on at least one repetition number and information on at least one transmission timing of a hybrid automatic repeat request (HARQ) feedback transmission, transmitting, to the terminal, downlink control information (DCI) including information indicating one of the at least one transmission timing and information indicating one of the at least one repetition number, transmitting data to the terminal in a plurality of first slots based on the repetition number indicated by the DCI, and receiving, from the terminal, the HARQ feedback in a plurality of second slots determined based on the plurality of first slots, wherein the HARQ feedback is set to a negative acknowledgement (NACK) in slots among the plurality of second slots other than a slot determined based on the transmission timing indicated by the DCI.

[0011] To address the above-described problem, an embodiment according to the present disclosure includes a terminal in a wireless communication system, the terminal including a transceiver, and a controller coupled with the transceiver and configured to receive, from a base station, configuration information including information on at least one repetition number and information on at least one transmission timing of a hybrid automatic repeat request (HARQ) feedback transmission, receive, from the base station, downlink control information (DCI) including information indicating one of the at least one transmission timing and information indicating one of the at least one repetition number, receive data from the base station in a plurality of first slots based on the repetition number indicated by the DCI, and transmit, to the base station, the HARQ feedback in a plurality of second slots determined based on the plurality of first slots, wherein the HARQ feedback is set to a negative acknowledgement (NACK) in slots among the plurality of second slots other than a slot determined based on the transmission timing indicated by the DCI.

[0012] To address the aforementioned problems, embodiments of this disclosure include a base station in a wireless communication system, the base station comprising: a transceiver; and a controller configured to: send configuration information to a terminal, the configuration information including information about at least one number of repetitions and information about at least one transmission timing for Hybrid Automatic Repeat Request (HARQ) feedback transmission; send downlink control information (DCI) to the terminal, the DCI including information indicating one of at least one transmission timing and information indicating one of at least one number of repetitions; send data to the terminal in a plurality of first time slots based on the number of repetitions indicated by the DCI; and receive HARQ feedback from the terminal in a plurality of second time slots determined based on the plurality of first time slots, wherein, in the plurality of second time slots, except for the time slots determined based on the transmission timing indicated by the DCI, the HARQ feedback is set to negative acknowledgment (NACK).

[0013] Advantages of the invention

[0014] According to this disclosure, when using network cooperation in a wireless communication system, the time required for a terminal to send uplink control information to each transmission point / panel / beam can be reduced.

[0015] Before proceeding with the detailed implementation below, it may be advantageous to define certain words and phrases used throughout this patent document: the terms “comprising” and “including” and their derivatives mean to include rather than to limit; the term “or” is inclusive, meaning and / or; the phrases “associated with” and “associated with” and their derivatives may mean to include, be included, interconnected, contain, be contained within, connected to or connected with, coupled to or coupled with, communicate with, cooperate with, interleave, juxtapose, proximate, bind to or bind with, have, have... attributes, etc.; and the term “controller” means any device, system or part thereof that controls at least one operation, such a device may be implemented in hardware, firmware or software or some combination of at least two of them. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether local or remote.

[0016] Further, various ones of the functions described below can be implemented or supported by one or more computer programs, each of which is formed from computer readable program code and embodied in a computer readable medium. The terms "application" and "program" refer to one or more computer programs, software components, sets of instructions, procedures, functions, objects, classes, instances, related data, or a portion thereof applicable for implementation. The phrase "computer readable medium" includes any medium that can be accessed by a computer including, but not limited to, read only memory (ROM); random access memory (RAM); a hard disk; compact disc (CD); digital video disc (DVD); or any other medium that can be used to carry or store desired computer code in a manner that causes a computer to access the code, cause a computer or computing-based device to perform functions. The phrase "computer readable program code" includes any type of computer code, including source code, object code, and executable code.

[0017] The definitions for certain words and phrases used throughout this patent document should be given their built-in meanings. These include, but are not limited to "couple" and "coupled," meaning to be directly or indirectly connected so that interoperation is achieved; "program module," meaning a computer program or set of computer programs, instructions, or codes that are executed by a computer to cause the computer to perform a particular function; and "computer readable medium," meaning any medium that can be accessed by a computer including, but not limited to, read only memory (ROM); random access memory (RAM); a hard disk; compact disc (CD); digital video disc (DVD); or any other medium that can be used to carry or store desired computer code in a manner that causes a computer to access the code, cause a computer or computing-based device to perform functions. BRIEF DESCRIPTION OF DRAWINGS

[0018] For a more complete understanding of the present disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings in which like reference numerals represent like parts:

[0019] Figure 1 A view illustrating a basic structure of a time-frequency domain of a mobile communication system according to an embodiment is shown;

[0020] Figure 2 A view illustrating a frame, subframe, and slot structure of a mobile communication system according to an embodiment is shown;

[0021] Figure 3 An example of a configuration of a bandwidth part (BWP) in a wireless communication system according to an embodiment is shown;

[0022] Figure 4 A view illustrating an example of configuring a control region of a downlink control channel in a wireless communication system according to an embodiment is shown;

[0023] Figure 5A view showing a structure of a downlink control channel of a mobile communication system according to an embodiment is illustrated;

[0024] Figure 6 A view showing a frequency-axis resource allocation example of a physical downlink shared channel (PDSCH) in a wireless communication system according to an embodiment is illustrated;

[0025] Figure 7 A view showing an example of time-axis resource allocation of a PDSCH in a wireless communication system according to an embodiment is illustrated;

[0026] Figure 8 A view showing an example of time-axis resource allocation according to subcarrier spacing of a data channel and a control channel in a wireless communication system according to an embodiment is illustrated;

[0027] Figure 9 A view showing a case where multiple PUCCH resources for HARQ-ACK transmission for a PDSCH overlap when multi-slot repetition is not configured according to an embodiment is illustrated;

[0028] Figure 10 A view showing a case where PUCCH resources overlap when multi-slot repetition is configured according to an embodiment is illustrated;

[0029] Figure 11 A view showing a base station and terminal radio protocol structure when single-cell, carrier aggregation, and dual connectivity are performed according to an embodiment is illustrated;

[0030] Figure 12 A view showing an example of antenna port configuration and resource allocation for cooperative communication in a wireless communication system according to some embodiments according to an embodiment is illustrated;

[0031] Figure 13 A view showing an example of downlink control information (DCI) configuration for cooperative communication in a wireless communication system according to an embodiment is illustrated;

[0032] FIG. 14A illustrates a view of HARQ-ACK reporting for non-coherent joint transmission (NC-JT) transmission according to an embodiment.

[0033] FIG. 14B illustrates a view of HARQ-ACK reporting for non-coherent joint transmission (NC-JT) transmission according to an embodiment.

[0034] FIG. 14C illustrates a view of HARQ-ACK reporting for non-coherent joint transmission (NC-JT) transmission according to an embodiment.

[0035] FIG. 14D illustrates a view of HARQ-ACK reporting for non-coherent joint transmission (NC-JT) transmission according to an embodiment.

[0036] FIG. 15A illustrates a view of a case where overlapping occurs between PUCCH resources according to an embodiment;

[0037] FIG. 15B illustrates a view of a method of transmitting a PUCCH when overlapping occurs between PUCCH resources according to an embodiment;

[0038] FIG. 16A illustrates a view of a Type 1 HARQ-ACK codebook method for each PDSCH repetition transmission across multiple slots, PDSCH repetition transmission within a single slot, and no repetition transmission according to an embodiment.

[0039] FIG. 16B illustrates a view of a Type 1 HARQ-ACK codebook method for each PDSCH repetition transmission across multiple slots, PDSCH repetition transmission within a single slot, and no repetition transmission according to an embodiment.

[0040] FIG. 16C illustrates a view of a Type 1 HARQ-ACK codebook method for each PDSCH repetition transmission across multiple slots, PDSCH repetition transmission within a single slot, and no repetition transmission according to an embodiment;

[0041] Figure 17 a structure of a terminal in a wireless communication system according to an embodiment is illustrated; and

[0042] Figure 18 a structure of a base station in a wireless communication system according to an embodiment is illustrated. DETAILED DESCRIPTION

[0043] The following discussion is presented to enable a Figures 1 to 18 The various embodiments described for the principles of the present disclosure in this patent document are by way of example only, and should not be construed in any way to limit the scope of the present disclosure. Those having ordinary skill in the art will understand that the principles of the present disclosure can be implemented in any suitably arranged system or device.

[0044] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In the following description, same drawing reference numerals are used for same elements across various drawings.

[0045] In describing embodiments of the present disclosure, descriptions related to technical contents well known in the art and not directly related to the present disclosure will be omitted. The omission of such unnecessary descriptions is intended to prevent obscuring the main idea of the present disclosure and to more clearly convey the main idea.

[0046] For the same reason, in the drawings, some elements can be exaggerated, omitted, or schematically illustrated. In addition, the size of each element does not completely reflect the actual size. In the drawings, the same or corresponding elements have the same reference numerals.

[0047] The advantages and features of the present disclosure and the manner of attaining them will become apparent in light of the following detailed description and accompanying drawings. However, the present disclosure is not limited to the embodiments set forth below, but can be implemented in various forms. The embodiments are provided merely to completely disclose the present disclosure and to inform the skilled in the art of the scope of the present disclosure, and the present disclosure is defined only by the scope of the claims. Throughout the specification, like or similar components are denoted by like or similar reference numerals.

[0048] Here, it will be understood that each block of the flowchart illustrations, and combinations of blocks in the flowchart illustrations, can be implemented 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 apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart block or blocks. These computer program instructions can also be stored in a computer usable or computer-readable memory that can direct a computer or other programmable data processing apparatus 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 instructions which implement the function specified in the flowchart block or blocks. The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.

[0049] Furthermore, each block of the flowchart illustrations can represent a module, a segment, or a 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 can occur out of the order. For example, two blocks shown in succession can in fact be executed substantially concurrently or the blocks can sometimes be executed in the reverse order, depending upon the functionality involved.

[0050] As used herein, a "unit" refers to a software or hardware element, such as a Field Programmable Gate Array (FPGA) or Application Specific Integrated Circuit (ASIC), which performs a predetermined function. However, the "unit" is not limited to software or hardware, and can be configured in at least one of software or hardware, and expressed in at least one of a firmware, a micro-code, and a hardware description language (HDL). The "unit" can be configured to store data in a memory and operate one or more processors. Therefore, the "unit" includes, for example, a software element, an object-oriented software element, a class element or a task element, a process, a function, a property, a procedure, a subroutine, a program code segment, a driver, a firmware, a micro-code, a circuit, a data, a database, a data structure, a table, an array, and a parameter. Elements and functions provided by the "unit" can be either combined with fewer elements and "units" or divided into more elements and "units". In addition, the elements and "units" can be implemented as one or more CPUs in a reconfigurable device or a secure multimedia card. Furthermore, the "unit" in the embodiments can include one or more processors.

[0051] Hereinafter, the operation principle of the present disclosure will be described in detail with reference to the accompanying drawings. In the following description of the present disclosure, a detailed description of known functions or configurations incorporated herein will be omitted when it can make the subject matter of the present disclosure rather unclear. The terms to be described below are terms defined in consideration of functions in the present disclosure, and can vary according to users, user's intentions, or habits. Therefore, the definition of the terms should be based on the contents of the entire specification. Hereinafter, a base station is a subject performing resource allocation of a terminal, and can be at least one of a gNode B (gNB), an eNode B (eNB), a Node B (Node B), a base station (BS), a radio access unit, a base station controller, or a node on a network. The terminal can include a user equipment (UE), a mobile station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. Of course, it is not limited to the above examples. Hereinafter, the present disclosure describes a technology for a terminal to receive broadcast information from a base station in a wireless communication system. The present disclosure relates to a communication technology and system for integrating a fifth-generation (5G) communication system with Internet of Things (IoT) technology to support higher data transmission rates after a fourth-generation (4G) system. The present disclosure can be applied to intelligent services (e.g., smart home, smart building, smart city, smart car or connected car, health care, digital education, retail, security and safety-related services, etc.) based on 5G communication technology and IoT-related technology.

[0052] In the following description, terms related to broadcast information, terms related to control information, terms associated with communication coverage, terms related to state change (e.g., event), terms related to network entity, terms related to message, terms related to device elements, etc. are illustratively used for convenience. Accordingly, the present disclosure is not limited by the terms used below, and other terms related to the subject matter having equivalent technical meanings can be used.

[0053] In the following description, for convenience of description, the present disclosure uses terms and names defined in the 3rd Generation Partnership Project Long Term Evolution (3GPP LTE) standard. However, the present disclosure is not limited to these terms and names, and can be applied in the same manner to systems conforming to other standards.

[0054] Wireless communication systems have evolved into broadband wireless communication systems using communication standards such as 3GPP's high-speed packet access (HSPA), long term evolution (LTE) or evolved universal terrestrial radio access (E-UTRA), LTE-advanced (LTE-A), LTE-Pro, 3GPP2's high-rate packet data (HRPD), ultra-mobile broadband (UMB), and IEEE 802.16e, etc., which provide high-speed and high-quality packet data services, rather than providing initial voice-based services.

[0055] As a representative example of a broadband wireless communication system, in the LTE system, the downlink (DL) adopts an orthogonal frequency division multiplexing (OFDM) scheme, and the uplink (UL) adopts a single carrier frequency division multiple access (SC-OFDM) scheme. The uplink refers to a radio link through which a terminal (user equipment (UE) or mobile station (MS)) transmits data or control signals to a base station (eNode B or base station (BS)), and the downlink refers to a radio link through which the base station transmits data or control signals to the terminal. In such a multiple access method, data or control information of each user is generally divided by allocation and operation so that time-frequency resources corresponding to the data or control information to be carried for each user do not overlap, i.e., orthogonality is established.

[0056] As a future communication system after LTE, i.e., a 5G communication system, should be able to freely reflect various requirements of users and service providers, and thus should support services satisfying various requirements. Services considered for the 5G communication system include enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliability low latency communication (URLLC), etc.

[0057] According to some embodiments, eMBB aims to provide a higher data transmission rate than existing LTE, LTE-A, or LTE-Pro. For example, in the 5G communication system, from the perspective of one base station, eMBB should be able to provide a maximum data rate of 20 Gbps in the downlink and a maximum data rate of 10 Gbps in the uplink. At the same time, an increased actual perceived data rate of a terminal should be provided. To meet this requirement, it is necessary to improve transmission / reception technology, including a more advanced multiple input multiple output (MIMO) transmission technology. In addition, it is possible to meet the data transmission speed required for the 5G communication system by using a bandwidth wider than 20 MHz in a 3-6 GHz or 6 GHz or higher frequency band, instead of the 2 GHz frequency band currently used by LTE.

[0058] Meanwhile, mMTC is being considered to support application services such as Internet of Things (IoT) in the 5G communication system. In order to efficiently provide the Internet of Things, mMTC can be required to support access to a large number of terminals within a cell, improve coverage of a terminal, improve battery time, and reduce the cost of a terminal. The Internet of Things should be able to support a large number of terminals (e.g., 1,000,000 terminals / square kilometer) in a cell since the cell is connected to various sensors and various devices to provide a communication function. In addition, since the nature of the service, a terminal supporting mMTC is likely to be located in a shadow area, such as a basement of a building, which cannot be covered by a cell, and thus can require a wider coverage than other services provided by the 5G communication system. Since a terminal supporting mMTC should be configured with a low-cost terminal, and it is difficult to frequently replace the battery of the terminal, a very long battery life can be required.

[0059] Finally, URLLC, which is a cellular-based wireless communication service for a specific purpose (mission critical), is a service for remote control of robots or mechanical devices, industrial automation, drones, remote health control, emergency notification, etc., and should provide communication providing ultra-low latency and ultra-high reliability. For example, a service supporting URLLC should satisfy an air interface latency of less than 0.5 msec while requiring a packet error rate of 10-5 or less. Therefore, for a service supporting URLLC, the 5G system needs to provide a smaller transmit time interval (TTI) than other services, and at the same time, needs to be designed to require a wider resource to be allocated in a frequency band. However, the above-described mMTC, URLLC, and EmB are only examples of different service types, and the service type to which the present disclosure is applied is not limited to the above-described examples.

[0060] Services considered in the above-described 5G communication system should be provided by being fused with each other on the basis of one framework. That is, for efficient resource management and control, it is preferable that each service is integrated and controlled and transmitted as one system rather than independently operated.

[0061] Further, hereinafter, embodiments will be described as examples of an LTE, LTE-A, LTE Pro, or NR system, but the embodiments can be applied to other communication systems having a similar technical background or channel type. Further, the embodiments can be applied to other communication systems through some modifications within a range that does not significantly deviate from the scope of the present disclosure, as judged by one of ordinary skill in the art.

[0062] The present disclosure relates to a method and apparatus for reporting channel state information to improve power saving efficiency of a terminal in a wireless communication system.

[0063] According to the present disclosure, when a terminal operates in a power saving mode in a wireless communication system, power saving efficiency can be further improved by optimizing a channel state information reporting method accordingly.

[0064] Hereinafter, a framework structure of a 5G system will be described in more detail with reference to the accompanying drawings.

[0065] Figure 1 A view showing a basic structure of a time-frequency domain of a mobile communication system according to an embodiment is illustrated.

[0066] Reference Figure 1, the horizontal axis represents the time domain, and the vertical axis represents the frequency domain. A basic unit in the time domain and the frequency domain is a resource element (RE) 1-01, and can be defined as 1 orthogonal frequency division multiplexing (OFDM) symbol 1-02 in the time axis and 1 subcarrier 1-03 in the frequency axis. In the frequency domain, N_sc^RB (for example, 12) consecutive REs can constitute one resource block (RB) 1-04. In an embodiment, a plurality of OFDM symbols can constitute one subframe 1-10.

[0067] Figure 2 A view for explaining a frame, a subframe, and a slot structure of a next-generation mobile communication system according to an embodiment is illustrated.

[0068] Reference Figure 2 , one frame 2-00 can consist of one or more subframes 2-01, and one subframe can consist of one or more slots 2-02. As an example, one frame 2-00 can be defined as 10 ms. One subframe 2-01 can be defined as 1 ms, and in this case, one frame 2-00 can consist of a total of 10 subframes 2-01. One slot 2-02, 2-03 can be defined by 14 OFDM symbols (i.e., the number of symbols per slot ). One subframe 2-01 can consist of one or more slots 2-02, 2-03, the number of slots 2-02, 2-03 per subframe 2-01 can be different according to a configuration value μ 2-04, 2-05 of a subcarrier spacing. In Figure 2 , cases where subcarrier spacing is configured are μ=0 (2-04) and μ=1 (2-05). When μ=0 (2-04), one subframe 2-01 can consist of one slot 2-02, and when μ=1 (2-05), one subframe 2-01 can consist of two slots 2-03. That is, the number of slots per subframe may change according to a configuration value μ of a subcarrier spacing, and thus the number of slots per frame may change. According to each subcarrier spacing configuration μ, and may be defined as follows [Table 1].

[0069] [Table 1]

[0070]

[0071] In NR, one component carrier (CC) or serving cell can be configured with up to 250 or more RBs. Therefore, when a terminal always receives the entire serving cell bandwidth (LTE) such as LTE, the power consumption of the terminal can be extremely great, and in order to solve this problem, the base station can configure one or more bandwidth parts (bandwidth part, BWP) for the terminal in order to support the terminal to change the reception area in the cell. In NR, the base station can configure the 'initial BWP' for the terminal through the master information block (MIB), which is the bandwidth of the CORESET #0 (or common search space, CSS). Then, the base station can configure the initial BWP (first BWP) of the terminal through the radio resource control (RRC) signaling, and can inform the terminal of at least one BWP configuration information, which can be indicated by the downlink control information (DCI) in the future. Thereafter, the base station can indicate which frequency band the terminal will use by the BWP identification through the DCI. If the terminal cannot receive the DCI from the currently allocated BWP for a certain time or longer, the terminal can return to the 'default BWP' and attempt to receive the DCI.

[0072] Figure 3 A view showing an example of configuration of a bandwidth part (BWP) in a wireless communication system according to an embodiment is illustrated.

[0073] Reference Figure 3 , Figure 3 An example in which a terminal bandwidth (3-00) is configured to have two bandwidth parts, i.e., bandwidth part #1 (3-05) and bandwidth part #2 (3-10), is illustrated. The base station can configure one or more bandwidth parts for the terminal, and can configure each bandwidth part with information as shown in [Table 2] below.

[0074] [Table 2]

[0075]

[0076] Of course, the disclosure is not limited to the above-described example, and various parameters related to the bandwidth part can be configured for the terminal in addition to the above-described configuration information. The above-described information can be transmitted to the terminal by the base station through higher layer signaling (e.g., RRC signaling). At least one of the configured one or more bandwidth parts can be activated. Whether the configured bandwidth part is activated can be semi-statically transmitted from the base station to the terminal through RRC signaling, or can be dynamically transmitted through a MAC control element (CE) or DCI.

[0077] According to an embodiment, a terminal before a radio resource control (RRC) connection can receive an initial bandwidth part (initial BWP) for initial access from a base station through a master information block (MIB). More specifically, in order to receive system information (remaining system information; can correspond to RMSI or system information block (SIB) 1) required for initial access through the MIB in the initial access step, the terminal can receive configuration information for a control region (control resource set, CORSET) and a search space through which a PDCCH can be transmitted. The control region and the search space configured by the MIB can be regarded as identifiers (IDs) 0, respectively.

[0078] The base station can inform the terminal of configuration information such as frequency allocation information, time allocation information, and a numerology of the control region #0 through the MIB. In addition, the base station can inform the terminal of configuration information of a monitoring period and occasion of the control region #0 through the MIB, that is, configuration information of the search space #0. The terminal can regard the frequency domain of the control region #0 configured to be obtained from the MIB as an initial bandwidth part for initial access. At this time, the identifier (ID) of the initial bandwidth part can be regarded as 0.

[0079] The bandwidth part supported by the above-described next-generation mobile communication system (5G or NR system) can be used for various purposes.

[0080] For example, when the bandwidth supported by the terminal is less than the system bandwidth, the bandwidth supported by the terminal can be supported by configuring the bandwidth part. For example, in Table 2, the frequency location of the bandwidth part (configuration information 2) is configured for the terminal so that the terminal can transmit and receive data at a specific frequency location within the system bandwidth.

[0081] As another example, to support different numerologies, the base station can configure a plurality of bandwidth parts for the terminal. For example, to support transmitting and receiving data to and from any terminal using a subcarrier spacing of 15 kHz and a subcarrier spacing of 30 kHz, two bandwidth parts can be configured to use subcarrier spacings of 15 kHz and 30 kHz, respectively. Different bandwidth parts can be frequency division multiplexed (FDM), and when data is transmitted / received in a specific subcarrier spacing, a bandwidth part configured in a corresponding subcarrier spacing can be activated.

[0082] As another example, to reduce the power consumption of the terminal, the base station can configure a bandwidth part having a different bandwidth size for the terminal. For example, if the terminal supports a very large bandwidth, such as a bandwidth of 100 MHz, and always transmits / receives data in the corresponding bandwidth, the large bandwidth can cause very large power consumption. In particular, in the absence of traffic, the terminal performs unnecessary monitoring of the downlink control channel for a large bandwidth of 100 MHz, which is very inefficient in terms of power consumption. Therefore, to reduce the power consumption of the terminal, the base station can configure a bandwidth part of a relatively small bandwidth, such as a bandwidth part of 20 MHz, for the terminal. In the absence of traffic, the terminal can perform a monitoring operation in the 20 MHz bandwidth part, and when data occurs, can transmit / receive data using the 100 MHz bandwidth part according to the instruction of the base station.

[0083] In a method of configuring the above-described bandwidth part, the terminal before RRC connection can receive configuration information of an initial bandwidth part through a master information block in an initial access step. More specifically, the terminal can receive a control region (control resource set (CORESET)) of a downlink control channel through the MIB of the physical broadcast channel (PBCH), through which downlink control information (DCI) scheduling a system information block (SIB) can be transmitted. The bandwidth configured as the control region of the MIB can be considered as an initial bandwidth part, and the terminal can receive a PDSCH through the configured initial bandwidth part, through which the SIB is transmitted. In addition to the purpose of receiving the SIB, the initial bandwidth part can be used for other system information (OSI), paging, and random access. Hereinafter, a synchronization signal (SS) / PBCH block of a next-generation mobile communication system (5G or NR system) will be described.

[0084] An SS / PBCH block can denote a physical layer channel block consisting of a primary SS (PSS), a secondary SS (SSS), and a PBCH. More specifically, the SS / PBCH block can be defined as follows.

[0085] - PSS: a signal that is a downlink time / frequency synchronization reference and can provide some information of a cell ID.

[0086] - SSS: the SSS is a reference for downlink time / frequency synchronization and can provide remaining cell ID information that the PSS does not provide. Additionally, the SSS can be used as a reference signal for PBCH demodulation.

[0087] - PBCH: the PBCH makes it possible to provide basic system information required for a data channel and a control channel of a transmission / reception terminal. The basic system information can include search space related control information indicating radio resource mapping information of a control channel, scheduling control information for a separate data channel for transmitting system information, and the like.

[0088] - SS / PBCH block: the SS / PBCH block can consist of a combination of the PSS, the SSS, and the PBCH. One or more SS / PBCH blocks can be transmitted within 5 milliseconds, and each SS / PBCH block transmitted can be distinguished by an index.

[0089] The terminal can detect the PSS and the SSS in an initial access phase and decode the PBCH. The terminal can acquire the MIB from the PBCH and can receive control region #0 through the MIB. Assuming that the selected SS / PBCH block and a demodulation reference signal (DMRS) transmitted from the control region #0 are quasi co-located (QCL), the terminal can perform monitoring on the control region #0. The terminal can receive system information as downlink control information transmitted from the control region #0. The terminal can obtain random access channel (RACH) related configuration information required for initial access from the received system information. The terminal can transmit a physical RACH (PRACH) to the base station in consideration of the selected SS / PBCH index, and the base station that receives the PRACH can acquire information about the SS / PBCH block index selected by the terminal. It can be seen that the base station selects a certain block from each SS / PBCH block and monitors the control region #0 corresponding (or associated) to the SS / PBCH block selected by the terminal.

[0090] Hereinafter, downlink control information (hereinafter, DCI) in a next-generation mobile communication system (5G or NR system) will be described in detail. In the next-generation mobile communication system (5G or NR system), scheduling information of uplink data (or a physical uplink shared channel (PUSCH)) or scheduling information of downlink data (or a physical downlink shared channel (PDSCH)) can be transmitted from a base station to a terminal through DCI. The terminal can monitor a fallback DCI format and a non-fallback DCI format for the PUSCH or the PDSCH. The fallback DCI format can consist of a predetermined fixed field between the base station and the terminal, and the non-fallback DCI format can include a configurable field.

[0091] Through a channel coding and modulation process, the DCI can be transmitted through a physical downlink control channel (PDCCH). A cyclic redundancy check (CRC) can be attached to a DCI message payload, and the CRC can be scrambled with a radio network temporary identifier (RNTI) corresponding to a terminal identification. Different RNTIs can be used to scramble the CRC attached to the payload of the DCI message according to the purpose of the DCI message, for example, terminal-specific (UE-specific) data transmission, a power control command, or a random access response. That is, the RNTI is not explicitly transmitted, but can be included in the CRC calculation process and transmitted. When receiving the DCI message transmitted in the PDCCH, the terminal can use the allocated RNTI to identify the CRC. If the CRC identification result is correct, the terminal can know that the corresponding message has been transmitted to the terminal.

[0092] For example, DCI scheduling a PDSCH for system information (SI) can be scrambled with an SI-RNTI. DCI scheduling a PDSCH for a random access response (RAR) message can be scrambled with an RA-RNTI. DCI scheduling a PDSCH for a paging message can be scrambled with a P-RNTI. DCI notifying a slot format indicator (SFI) can be scrambled with an SFI-RNTI. DCI notifying transmit power control (TPC) can be scrambled with a TPC-RNTI. DCI for scheduling a terminal-specific PDSCH or PUSCH can be scrambled with a cell RNTI (C-RNTI).

[0093] The DCI format 0_0 can be used as fallback DCI scheduling PUSCH, and CRC can be scrambled with C-RNTI at this time. In one embodiment, the DCI format 0_0 in which CRC is scrambled with C-RNTI can include information as shown in the following [Table 3].

[0094] [Table 3]

[0095]

[0096] The DCI format 0_1 can be used as non-fallback DCI scheduling PUSCH, and CRC can be scrambled with C-RNTI. In an embodiment, the DCI format 0_1 in which CRC is scrambled with C-RNTI can include information as shown in the following [Table 4].

[0097] [Table 4]

[0098]

[0099]

[0100] The DCI format 1_0 can be used as fallback DCI for scheduling PDSCH, and CRC can be scrambled with C-RNTI. In an embodiment, the DCI format 1_0 in which CRC is scrambled with C-RNTI can include information as shown in the following [Table 5].

[0101] [Table 5]

[0102]

[0103] The DCI format 1_1 can be used as non-fallback DCI for scheduling PDSCH, in which CRC can be scrambled with C-RNTI. In an embodiment, the DCI format 1_1 in which CRC is scrambled with C-RNTI can include information as shown in the following [Table 6].

[0104] [Table 6]

[0105]

[0106]

[0107] Figure 4 A view showing an example of configuring a control region of a downlink control channel in a next-generation mobile communication system according to an embodiment is shown. That is, Figure 4 is a view showing an embodiment of transmitting a control region (control resource set (CORESET)) of a downlink control channel in a 5G wireless communication system according to an embodiment.

[0108] Referring to Figure 4 ,Figure 4 It is shown that two control regions (control region #1 4-01 and control region #2 4-02) are configured within a bandwidth part (UE bandwidth part) 4-10 of a terminal and in one slot 4-20 on the frequency axis, in one slot 4-20 on the time axis. The control regions 4-01 and 4-02 can be configured as specific frequency resources 4-03 within the entire terminal bandwidth part 4-10 on the frequency axis. The control regions 4-01 and 4-02 can be configured as one or more OFDM symbols on the time axis, which can be defined as a control resource set duration (4-04). Referring to Figure 4 , control region #1 (4-01) can be configured as a control resource set duration of 2 symbols, and control region #2 (4-02) can be configured as a control resource set duration of 1 symbol.

[0109] The above control region in the next generation mobile communication system (5G or NR system) can be configured by the base station to the terminal by higher layer signaling (e.g., system information, master information block (MIB), radio resource control (RRC) signaling). Configuring a control region to a terminal means providing information such as a control region identifier, a frequency location of the control region, and a symbol length of the control region. For example, the configuration of the control region can include information as shown in the following [Table 7].

[0110] [Table 7]

[0111]

[0112] In [Table 7], the tci-StatesPDCCH (hereinafter referred to as "TCI state") configuration information can include information of one or more synchronization signal (SS) / physical broadcast channel (PBCH) indexes or channel state information reference signal (CSI-RS) indexes in a quasi co-located (QCL) relationship with a demodulation reference signal (DMRS) transmitted in the corresponding control region. In addition, the tci-StatesPDCCH configuration information can include information about what the QCL relationship is. For example, the configuration of the TCI state can include information as shown in the following [Table 8].

[0113] [Table 8]

[0114]

[0115] Referring to the TCI state configuration, the cell index and / or BWP index and QCL type of the reference RS can be configured in the QCL relationship with the index of the reference RS, i.e., the SS / PBCH block index or the CSI-RS index. The QCL type indicates the channel properties assumed to be shared between the reference RS and the control region DMRS, and examples of possible QCL types are as follows.

[0116] - QCL typeA: Doppler shift, Doppler spread, average delay, delay spread.

[0117] - QCL typeB: Doppler shift, Doppler spread.

[0118] - QCL typeC: Doppler shift, average delay.

[0119] - QCL typeD: Spatial Rx parameter.

[0120] The TCI state can be similarly configured for the control region DMRS as well as other target RSs such as the PDSCH DMRS and the CSI-RS, but detailed descriptions thereof will be omitted in order not to obscure the subject matter of the description.

[0121] Figure 5 A view for explaining a structure of a downlink control channel of a next-generation mobile communication system according to an embodiment is illustrated. That is, Figure 5 is a view illustrating an example of a basic unit of time and frequency resources of a downlink control channel that can be configured to be used in 5G according to an embodiment.

[0122] Referring to Figure 5 , a basic unit of time and frequency resources constituting a control channel can be defined as a resource element group (REG) 5-03. The REG 5-03 can be defined as 1 OFDM symbol 5-01 on a time axis, 1 physical resource block (PRB) 5-02, i.e., 12 subcarriers, on a frequency axis. The base station can configure a downlink control channel allocation unit by connecting the REGs 5-03.

[0123] As illustrated in Figure 5 , when a basic unit to which a downlink control channel is allocated in 5G is referred to as a control channel element (CCE) 5-04, 1 CCE 5-04 can be composed of a plurality of REGs 5-03. For example, Figure 5The REG 5-03 shown in the middle can consist of 12 REs, and if 1 CCE 5-04 consists of 6 REGs 5-03, 1 CCE 5-04 can consist of 72 REs. When a downlink control region is configured, the corresponding region can consist of a plurality of CCEs 5-04, and a specific downlink control channel can be transmitted by being mapped to one or more CCEs 5-04 according to an aggregation level (AL) in the control region. The CCEs 5-04 in the control region are numbered, and the numbering of the CCEs 5-04 can be allocated according to a logical mapping method.

[0124] Figure 5 The basic unit of the downlink control channel shown in the middle, that is, the REG 5-03, can include a DCI-mapped RE to which DCI is mapped and a reference signal DMRS 5-05 to which a reference signal for decoding is mapped. As shown in the middle, Figure 5 As shown in the middle, three DMRSs 5-05 can be transmitted in 1 REG 5-03. According to an aggregation level (AL), the number of CCEs required to transmit a PDCCH can be 1, 2, 4, 8, or 16, and different numbers of CCEs can be used to implement link adaptation of a downlink control channel. For example, when AL=L, one downlink control channel can be transmitted through L CCEs.

[0125] The terminal should detect a signal without knowing information about a downlink control channel, and a search space indicating a set of CCEs for blind decoding can be defined. The search space is a set of downlink control channel candidates consisting of a set of CCEs that the terminal should attempt to decode at a given aggregation level. Since there are various aggregation levels consisting of bundles of 1, 2, 4, 8, and 16 CCEs, the terminal can have a plurality of search spaces. A search space set can be defined as a set of search spaces for all configured aggregation levels.

[0126] The search space can be classified into a common search space and a terminal-specific search space. According to an embodiment, a certain group of terminals or all terminals can check the common search space of the PDCCH in order to receive control information common to the cell, such as dynamic scheduling of system information or a paging message.

[0127] For example, the terminal can receive PDSCH scheduling allocation information for transmitting SIB including operator information of a cell by checking a common search space of PDCCH. In the case of a common search space, since a certain group of terminals or all terminals should receive PDCCH, the common search space can be defined as a set of predetermined CCEs. Meanwhile, the terminal can receive scheduling allocation information for a terminal-specific PDSCH or PUSCH by checking a terminal-specific search space of PDCCH. The terminal-specific search space can be defined as a function of terminal identification and various system parameters, specifically for the terminal.

[0128] In 5G, parameters for a search space of PDCCH can be configured from a base station to a terminal through higher layer signaling (e.g., SIB, MIB, RRC signaling). For example, the base station can configure the terminal with the number of PDCCH candidate groups per aggregation level L, a monitoring period of a search space, a monitoring occasion in a slot of a search space in units of symbols, a search space type (common search space or terminal-specific search space), a combination of DCI formats and RNTIs to be monitored in a search space, a control region index for monitoring a search space, etc. For example, the above-described configuration can include information such as [Table 9] below.

[0129] [Table 9]

[0130]

[0131]

[0132] Based on the configuration information, the base station can configure one or more search space sets for the terminal. According to an embodiment, the base station can configure search space set 1 and search space set 2, configure the terminal to monitor DCI format A scrambled with X-RNTI in search space set 1 in a common search space, and configure the terminal to monitor DCI format B scrambled with Y-RNTI in search space set 2 in a terminal-specific search space.

[0133] According to the configuration information, one or more sets of search spaces can exist in a common search space or a terminal-specific search space. For example, search space set #1 and search space set #2 can be configured as a common search space, and search space set #3 and search space set #4 can be configured as a terminal-specific search space.

[0134] In the common search space, the following combinations of DCI formats and RNTIs can be monitored. Of course, it is not limited to the following examples.

[0135] - DCI format 0_0 / 1_0 with CRC scrambled with C-RNTI, CS-RNTI, SP-CSI-RNTI, RA-RNTI, TC-RNTI, P-RNTI, SI-RNTI

[0136] - DCI format 2_0 with CRC scrambled with SFI-RNTI

[0137] - DCI format 2_1 with CRC scrambled with INT-RNTI

[0138] - DCI format 2_2 with CRC scrambled with TPC-PUSCH-RNTI, TPC-PUSCH-RNTI

[0139] - DCI format 2_3 with CRC scrambled with TPC-SRS-RNTI

[0140] In the terminal-specific search space, the following combinations of DCI format and RNTI can be monitored. Of course, the following examples are not limited.

[0141] - DCI format 0_0 / 1_0 with CRC scrambled with C-RNTI, CS-RNTI, TC-RNTI

[0142] - DCI format 1_0 / 1_1 with CRC scrambled with C-RNTI, CS-RNTI, TC-RNTI

[0143] The specified RNTIs can follow the following definitions and uses.

[0144] C-RNTI (Cell RNTI): Terminal-specific PDSCH scheduling purpose.

[0145] TC-RNTI (Temporary Cell RNTI): Terminal-specific PDSCH scheduling purpose.

[0146] CS-RNTI (Configured Scheduling RNTI): Semi-statically configured terminal-specific PDSCH scheduling purpose.

[0147] RA-RNTI (Random Access RNTI): PDSCH scheduling for the random access stage.

[0148] P-RNTI (Paging RNTI): PDSCH scheduling for paging transmission.

[0149] SI-RNTI (System Information RNTI): PDSCH scheduling for transmitting system information.

[0150] INT-RNTI (Interruption RNTI): Used to inform whether the PDSCH is punctured.

[0151] TPC-PUSCH-RNTI (Transmit Power Control for PUSCH RNTI): indicates the purpose of a power control command for PUSCH.

[0152] TPC-PUCCH-RNTI (Transmit Power Control for PUCCH RNTI): indicates the purpose of a power control command for PUCCH.

[0153] TPC-SRS-RNTI (Transmit Power Control for SRS RNTI): indicates the purpose of a power control command for SRS.

[0154] In an embodiment, the DCI formats described above can be defined as the following [Table 10].

[0155] [Table 10]

[0156]

[0157]

[0158] According to an embodiment, in 5G, a plurality of search space sets can be configured with different parameters (e.g., parameters in [Table 8]). Therefore, the set of search space sets monitored by the terminal at each time point can be different. For example, if search space set #1 is configured for an X slot period, search space set #2 is configured for a Y slot period, and X and Y are different, the terminal can monitor search space set #1 and search space set #2 in a certain slot, and monitor one of search space set #1 and search space set #2 in a certain slot.

[0159] When a plurality of search space sets are configured for a terminal, in order to determine the set of search spaces that the terminal should monitor, the following conditions can be considered.

[0160] [Condition 1: Limitation of the maximum number of PDCCH candidates]

[0161] The number of PDCCH candidates that can be monitored per slot can not exceed M μ . M μ Can be defined as the maximum number of PDCCH candidate groups per slot in a cell configured with 15·2 μ kHz subcarrier spacing, which can be defined as shown in the following Table 11.

[0162]

[0163] [Condition 2: Limitation of the maximum number of CCEs]

[0164] The number of CCEs per slot constituting the entire search space (here, the entire search space can mean the entire set of CCEs corresponding to the joint area of a plurality of search space sets) can not exceed C μ . C μ may be defined as the maximum number of CCEs per slot in a cell configured with 15·2 μ kHz subcarrier spacing, and can be defined as shown in the following [Table 12].

[0165] [Table 12]

[0166]

[0167]

[0168] For ease of explanation, a case where both Condition 1 and Condition 2 are satisfied at a specific time point is defined as "Condition A". Thus, not satisfying Condition A can mean not satisfying at least one of Condition 1 and Condition 2.

[0169] Depending on the configuration of the search space set of the base station, Condition A can not be satisfied at a specific time. If Condition A is not satisfied at a specific time, the terminal can select and monitor only a subset of the set of search spaces configured to satisfy Condition A at that time, and the base station can transmit PDCCH to the selected search space set.

[0170] According to an embodiment, the following method can be used as a method of selecting some search spaces from among the set of search spaces of all sets.

[0171] [Method 1]

[0172] If Condition A for PDCCH is not satisfied at a specific time (slot), the terminal (or base station) can preferentially select a set of search spaces whose search space type is configured as a common search space from among the search space sets existing at the corresponding time point, rather than a set of search spaces configured as a terminal-specific search space.

[0173] When all search space sets configured as common search spaces are selected (i.e., when Condition A is satisfied even after selecting all search spaces as common search spaces), the terminal (or base station) can select a set of search spaces configured as a terminal-specific search space. At this time, when there are a plurality of search space sets configured as a terminal-specific search space, a search space set having a low search space set index can have a higher priority. The terminal or base station can select a terminal-specific search space set within the range where Condition A is satisfied, considering the priority.

[0174] Below, a time and frequency resource allocation method for data transmission in NR is described.

[0175] In NR, in addition to the frequency axis resource candidate allocation indicated by the BWP, the following detailed frequency domain resource allocation (FD-RA) can be provided.

[0176] Figure 6 A view showing an example of PDSCH frequency axis resource allocation in a wireless communication system according to an embodiment is shown.

[0177] Specifically, Figure 6 Three types of frequency axis resource allocation methods, Type 0 (6-00), Type 1 (6-05), and dynamic switching (6-10), which can be configured by an upper layer in NR, are shown.

[0178] Referring to Figure 6 If a terminal is configured to use only resource type 0 (6-00) through upper layer signaling, some downlink control information (DCI) for allocating a PDSCH to the corresponding terminal has a bitmap consisting of NRBG bits. The condition for this case will be explained again later. At this time, NRBG refers to the number of resource block groups (RBGs) determined according to the BWP size allocated by the BWP indicator and the upper layer parameter NRBG-Size as shown in [Table 13]. Data is transmitted to the RBG indicated by 1.

[0179] [Table 13]

[0180] Bandwidth part size Configuration 1 Configuration 2 1-36 2 4 37-72 4 8 73-144 8 16 145-275 16 16

[0181] If a terminal is configured to use only resource type 1 6-05 through upper layer signaling, some DCI for allocating a PDSCH to the corresponding terminal has frequency axis resource allocation information consisting of bits. The condition for this case will be explained again later. Through this, the base station can configure the start VRB 6-20 and the length 6-25 of the frequency axis resource allocated continuously therefrom.

[0182] If a terminal is configured to use both resource type 0 and resource type 1 (6-10) through upper layer signaling, some DCI for allocating a PDSCH to the corresponding terminal has frequency axis resource allocation information consisting of the larger value 6-35 of the payload 6-15 for configuring resource type 0 and the payload 6-20, 6-25 for configuring resource type 1. The condition for this case will be explained again later. At this time, one bit can be added to the first part (MSB) of the frequency axis resource allocation information in the DCI, and when the corresponding bit is 0, the one bit can indicate that resource type 0 is used, and when the corresponding bit is 1, the one bit can indicate that resource type 1 is used.

[0183] Hereinafter, a time domain resource allocation method of a data channel in a next-generation mobile communication system (5G or NR system) is described.

[0184] The base station can configure a table of time domain resource allocation information of a downlink data channel (Physical Downlink Shared Channel (PDSCH)) and an uplink data channel (Physical Uplink Shared Channel (PUSCH)) of the terminal as higher layer signaling (e.g., RRC signaling). A table consisting of at most maxNrofDL-Allocations = 16 entries can be configured for the PDSCH, and a table consisting of at most maxNrofUL-Allocations = 16 entries can be configured for the PUSCH. In an embodiment, in the time domain resource allocation information, PDCCH-to-PDSCH slot timing (corresponding to a time interval in units of slots between a time at which a PDCCH is received and a time at which a PDSCH scheduled by the received PDCCH is transmitted, denoted by K0), PDCCH-to-PUSCH slot timing (corresponding to a time interval in units of slots between a time at which a PDCCH is received and a time at which a PUSCH scheduled by the received PDCCH is transmitted, denoted by K2), information on a position and length of a starting symbol for which the PDSCH or the PUSCH is scheduled in a slot, a mapping type of the PDSCH or the PUSCH, etc. can be included. For example, information such as the following [Table 14] or [Table 15] can be informed from the base station to the terminal.

[0185] [Table 14]

[0186]

[0187] [Table 15]

[0188]

[0189] The base station can inform the terminal of one of the entries in the above-described table of time domain resource allocation information through L1 signaling (e.g., DCI) (e.g., indicated by a 'Time domain resource allocation' field in the DCI). The terminal can acquire time domain resource allocation information for the PDSCH or the PUSCH based on the DCI received from the base station.

[0190] Figure 7 A view showing an example of time axis resource allocation of a PDSCH in a wireless communication system according to an embodiment is shown.

[0191] Referring to Figure 7 , the base station can indicate to use a subcarrier spacing (SCS) (μ PDSCH , μ PDCCH), a scheduling offset (K0) value, and a time axis position configuration of PDSCH resources according to the OFDM symbol start position (7-00) and length (7-05) in one slot dynamically indicated by the DCI.

[0192] Figure 8 A view showing an example of time axis resource allocation according to subcarrier spacing of a data channel and a control channel in a wireless communication system according to an embodiment is shown.

[0193] Referring to Figure 8 It can be seen that when the subcarrier spacing of the data channel and the control channel is the same (8-00, μ PDSCH = μ PDCCH ), the slot numbers for data and control are the same, so that a scheduling offset occurs for the base station and the terminal according to the predetermined slot offset K0 in the base station and the terminal. On the other hand, it can be seen that when the subcarrier spacing of the data channel and the control channel is different (8-05, μ PDSCH ≠ μ PDCCH ), the slot numbers for data and control are different, so that a scheduling offset occurs for the base station and the terminal based on the subcarrier spacing of the PDCCH according to the predetermined slot offset K0 in the base station and the terminal.

[0194] In LTE and NR, the terminal has a procedure of reporting a capability supported by the terminal to the corresponding base station while being connected to the serving base station. In the following description, this is referred to as terminal (UE) capability (reporting).

[0195] The base station can transmit a terminal capability inquiry message requesting a capability report to a terminal in a connected state. In this message, the base station can include a request for terminal capability for each RAT type. The request for each RAT type can include requested band information. In addition, the terminal capability inquiry message can request multiple RRC types from one RRC message container, or the terminal capability inquiry message including a request for each RRC type can be transmitted to the terminal multiple times. That is, the terminal capability inquiry can be repeated multiple times, and the terminal can report the number of times by configuring a corresponding terminal capability information message. In the next-generation mobile communication system, terminal capability requests can be made for MR-DC including NR, LTE, and E-UTRA New Radio Dual Connectivity (EN-DC). In addition, the terminal capability inquiry message is usually initially transmitted after the terminal is connected to the base station, but can be requested under any conditions when the base station needs.

[0196] In the step, the terminal receiving a terminal capability report request from the base station can configure the terminal capability according to the RAT type and band information requested from the base station. One method in which the terminal configures the terminal capability in the NR system is as follows.

[0197] 1. If the terminal is provided with a list of LTE and / or NR bands in a terminal capability request from the base station, the terminal can configure band combinations for EN-DC and NR stand-alone (SA) networking. That is, a candidate list for EN-DC and NR SA can be configured based on the bands requested by the base station with FreqBandList. In addition, the priority of the band has priority in the order described in FreqBandList.

[0198] 2. If the base station requests a terminal capability report by configuring the "eutra-nr-only" flag or the "eutra" flag, the terminal can completely remove the NR SA BC from the configured BC candidate list. This operation can be performed only when the LTE base station (eNB) requests "eutra" capability.

[0199] 3. Thereafter, the terminal can remove fallback BCs from the BC candidate list configured in the above steps. Here, the fallback BC corresponds to a case where a band corresponding to at least one SCell is removed from a super set BC, and can be omitted because the super set BC can already cover the fallback BC. This step is also applicable to Multi-RAT Dual Connectivity (MR-DC), that is, it can also be applied to LTE bands. The BC left after this stage is the final "candidate BC list".

[0200] 4. The terminal can select a BC to be reported by selecting a BC corresponding to a requested RAT type in the final "candidate BC list". In this step, the terminal can configure supportedBandCombinationList in a predetermined order. That is, the terminal can configure the BC and terminal capability to be reported in a predetermined rat-Type order (nr->eutra-nr->eutra). In addition, the featureSetCombination of the configured supportedBandCombinationList can be configured, and a "candidate feature set combination" list can be constructed from the candidate BC list in which the fallback BC (which includes the same or lower level capability) is removed from the list. The "candidate feature set combination" includes the feature set combination of NR and EUTRA-NR BC, and can be obtained from the feature set combination of the UE-NR-Capabilities and UE-MRDC-Capabilities containers.

[0201] 5. Also, if the requested rat type is eutra-nr, the featureSetCombinations can be included in two containers, UE-MRDC-Capabilities and UE-NR-Capabilities. However, the feature set of new radio (NR) can include only the UE-NR-Capabilities.

[0202] After the terminal capability is configured, the terminal can transmit a terminal capability information message including the terminal capability to the base station. Then, the base station can perform appropriate scheduling and transmission / reception management for the corresponding terminal based on the terminal capability received from the terminal.

[0203] In NR, a terminal can transmit uplink control information (UCI) to a base station through a physical uplink control channel (PUCCH). The control information can include at least one of HARQ-ACK indicating whether demodulation / decryption of a transport block received by the terminal through a PDSCH is successful, a scheduling request for requesting PUSCH resource allocation to the base station by the terminal for uplink data transmission, and channel state information (CSI) as information for reporting a channel state of the terminal.

[0204] According to the allocated symbol length, the PUCCH resource can be mainly divided into long PUCCH and short PUCCH. In NR, the long PUCCH has a length of 4 or more symbols in a slot, and the short PUCCH has a length of 2 or less symbols in a slot.

[0205] Describing the long PUCCH in more detail, the long PUCCH can be used for the purpose of improving uplink cell coverage, and thus can be transmitted in a DFT-S-OFDM method transmitted as a short carrier instead of OFDM transmission. The long PUCCH supports transmission formats such as PUCCH format 1, PUCCH format 3, and PUCCH format 4 depending on the number of control information bits that can be supported, and whether terminal multiplexing is supported by Pre-DFT OCC support through the IFFT front end.

[0206] First, PUCCH format 1 is a long PUCCH format based on DFT-S-OFDM in which at most 2 bits of control information can be supported and a frequency resource of 1 RB is used. The control information can consist of HARQ-ACK, SR, or a combination thereof. In PUCCH format 1, a repetition configuration includes an OFDM symbol including a demodulation reference signal (DMRS) as a demodulation reference signal (or reference signal) and an OFDM symbol including UCI.

[0207] For example, when the number of transmission symbols of PUCCH format 1 is 8 symbols, the first starting symbol of the 8 symbols is composed of 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 in this order. The DMRS symbol is spread in a sequence of 1RB length on the frequency axis within a corresponding one OFDM symbol by using an orthogonal code (or an orthogonal sequence or a spreading code, w_i(m)) on the time axis, and the symbol is transmitted after IFFT is performed.

[0208] The UCI symbol has a structure of generating d(0) by modulating 1-bit control information by BPSK and 2-bit control information by QPSK, scrambling the generated d(0), and multiplying a sequence corresponding to 1RB length on the frequency axis, spreading the scrambled sequence by using an orthogonal code (or an orthogonal sequence or a spreading code, w_i(m)) on the time axis, and transmitting the sequence after IFFT is performed.

[0209] The terminal generates a sequence based on a packet frequency hopping or a sequence frequency hopping configuration received from the base station as a higher layer signal and a configured ID, and generates a sequence corresponding to 1RB length by cyclically shifting the generated sequence with an initial cyclic shift (CS) value set as a higher layer signal.

[0210] When the length of a spreading code (NSF) is given, w_i(m) is determined as given in and is given as follows in Table 16. i indicates the index of the spreading code itself, and m indicates the index of the element of the spreading code. Here, the number in [] in [Table 16] indicates φ(m), for example, when the length of the spreading code is 2 and the index i of the configured spreading code = 0, the spreading code w_i(m) becomes so that w_i(m) = [1 1].

[0211] [Table 16] Spreading code of PUCCH format 1

[0212]

[0213] Next, PUCCH format 3 is a long PUCCH format based on DFT-S-OFDM capable of supporting more than 2 bits of control information, and the number of RBs used can be configured by an upper layer. The control information can consist of HARQ-ACK, SR, CSI, or a combination thereof. Depending on whether frequency hopping in a slot and additional DMRS symbols are configured, the DMRS symbol positions in PUCCH format 3 are as shown in [Table 17].

[0214] [Table 17]

[0215]

[0216] For example, if the number of transmission symbols of PUCCH format 3 is 8 symbols, the first starting symbol of 8 symbols starts with 0, and DMRS is transmitted to the 1st and 5th symbols. The above table also applies to the DMRS symbol position in PUCCH format 4.

[0217] Next, PUCCH format 4 is a long PUCCH format based on DFT-S-OFDM capable of supporting more than 2 bits of control information, and uses a frequency resource of 1 RB. The control information can consist of HARQ-ACK, SR, CSI, or a combination thereof. The difference between PUCCH format 4 and PUCCH format 3 is that PUCCH format 4 can multiplex a plurality of PUCCH format 4 terminals within one RB. By applying Pre-DFT OCC to the control information in the front end of IFFT, a plurality of PUCCH format 4 UEs can be multiplexed. However, the number of control information symbols that can be transmitted by one terminal decreases according to the number of terminals to be multiplexed. The number of multiplexable terminals, i.e., the number of different OCCs that can be used, can be 2 or 4, and the number of OCCs to be applied and the OCC index can be configured by the upper layer.

[0218] Next, a short PUCCH will be described. The short PUCCH can be transmitted in a downlink-centric slot (downlink-centric slot) and an uplink-centric slot (uplink-centric slot), and is generally transmitted in the last symbol of the slot or the following OFDM symbol (e.g., the last OFDM symbol or the second OFDM symbol at the end, or the last two OFDM symbols). Of course, the short PUCCH can also be transmitted at any position in the slot. In addition, the short PUCCH can be transmitted using one OFDM symbol or two OFDM symbols. In the case of uplink cell coverage and transmission in CP-OFDM, the short PUCCH can be used to shorten the delay time compared to the long PUCCH.

[0219] The short PUCCH supports transmission formats such as PUCCH format 0, PUCCH format 2 according to the number of control information bits that can be supported. First, the PUCCH format 0 is a short PUCCH format capable of supporting up to 2 bits of control information, and uses a frequency resource of 1 RB. The control information can consist of HARQ-ACK, SR, or a combination thereof. The PUCCH format 0 does not transmit a DMRS, and has a structure that transmits only a sequence mapped to 12 subcarriers on the frequency axis within one OFDM symbol. The terminal generates a sequence based on a set of frequency hopping or sequence hopping sets and set IDs received from the base station as a higher layer signal, cyclically shifts the generated sequence to a final CS value obtained by adding another CS value according to whether the indicated initial CS value is ACK or NACK, and then maps the sequence and transmits the mapped sequence to 12 subcarriers.

[0220] For example, if the HARQ-ACK is 1 bit, as shown in [Table 18] below, 6 is added to the initial CS value to generate the final CS, and in the case of NACK, 0 is added to the initial CS to generate the final CS. The CS value 0 for NACK and the CS value 6 for ACK are defined in the standard, and the terminal always generates the PUCCH format 0 according to the value and transmits 1 bit of HARQ-ACK.

[0221] [Table 18]

[0222]

[0223] For example, in the case of 2 bits of HARQ-ACK, as shown in [Table 19], if the 2 bits of HARQ-ACK are (NACK, NACK), 0 is added to the initial CS value, if the 2 bits of HARQ-ACK are (NACK, ACK), 3 is added to the initial CS value, if the 2 bits of HARQ-ACK are (ACK, ACK), 6 is added to the initial CS value, and if the 2 bits of HARQ-ACK are (ACK, NACK), 9 is added to the initial CS value. The CS value 0 for (NACK, NACK), the CS value 3 for (NACK, ACK), the CS value 6 for (ACK, ACK), and the CS value 9 for (ACK, NACK) are defined in the specification, and the terminal always generates the PUCCH format 0 according to the above values and transmits 2 bits of HARQ-ACK.

[0224] When the final CS value exceeds 12 by the CS value added to the initial CS value according to ACK or NACK, modulo 12 is applied to the final CS value because the length of the sequence is 12.

[0225] [Table 19]

[0226]

[0227] Next, PUCCH format 2 is a short PUCCH format supporting more than 2 bits of control information, and the number of RBs used can be configured by the upper layer. The control information can consist of HARQ-ACK, SR, CSI, or a combination thereof. In PUCCH format 2, when the index of the first subcarrier is #0, the position of the subcarrier in which the DMRS is transmitted is fixed to subcarriers with indices #1, #4, #7, and #10 in one OFDM symbol. Through the modulation process after channel coding, the control information is mapped to the remaining subcarriers except for the subcarriers in which the DMRS is located.

[0228] In summary, the values and ranges that can be configured for each of the above PUCCH formats can be summarized in [Table 20]. If there is no need to configure the values in the following table, the value will be shown as N.A.

[0229] [Table 20]

[0230]

[0231] Meanwhile, in order to improve uplink coverage, multi-slot repetition can be supported for PUCCH formats 1, 3, and 4, and PUCCH repetition can be configured for each PUCCH format.

[0232] Next, PUCCH resource configuration of a base station or a terminal will be described. The base station can configure PUCCH resources for each BWP through the upper layer of a specific terminal. The configuration can be as shown in [Table 21].

[0233] [Table 21]

[0234]

[0235] According to the above table, one or more of the PUCCH resource sets for a specific BWP can be configured, and the maximum payload value for UCI transmission can be configured in some of the PUCCH resource sets. Each PUCCH resource set can include one or more PUCCH resources, and each of the PUCCH resources can belong to one of the PUCCH formats described above.

[0236] For the PUCCH resource sets, the maximum payload value of the first PUCCH resource set can be fixed to 2 bits, so the corresponding value can not be separately configured by the upper layer or the like. When the remaining PUCCH resource sets are configured, the index of the corresponding PUCCH resource set can be configured in ascending order according to the maximum payload value, and the maximum payload value can not be configured in the last PUCCH resource set. The upper layer configuration of the PUCCH resource set can be as shown in [Table 22].

[0237] [Table 22]

[0238]

[0239] The resourceList parameter of the table can include IDs of PUCCH resources belonging to a PUCCH resource set.

[0240] If an initial access or PUCCH resource set is not configured, a PUCCH resource set consisting of a plurality of cell-specific PUCCH resources in an initial BWP can be used as shown in [Table 22]. A PUCCH resource to be used for initial access in the PUCCH resource set can be indicated by SIB1.

[0241] [Table 23]

[0242]

[0243] In the case of PUCCH format 0 or 1, the maximum payload of each PUCCH resource included in the PUCCH resource set can be 2 bits, and can be determined by a symbol length, a number of PRBs, and a maximum code rate of a remaining format. The aforementioned symbol length and the number of PRBs can be configured for each PUCCH resource, and the maximum code rate can be configured for each PUCCH format.

[0244] Next, PUCCH resource selection for UCI transmission will be described. In the case of SR transmission, a PUCCH resource of an SR corresponding to schedulingRequestID can be configured by an upper layer as shown in [Table 24]. The PUCCH resource can be a resource belonging to PUCCH format 0 or PUCCH format 1.

[0245] [Table 24]

[0246]

[0247] For a configured PUCCH resource, a transmission period and an offset are configured through the periodicityAndOffset parameter of [Table 24]. If the terminal has uplink data to transmit at a time corresponding to the set period and offset, the corresponding PUCCH resource is transmitted, and otherwise the corresponding PUCCH resource can not be transmitted.

[0248] In the case of CSI transmission, the PUCCH resource to transmit periodic or semi-persistent CSI report through PUCCH can be configured in the PUCCH-CSI-ResourceList parameter as shown in [Table 23]. This parameter contains a list of PUCCH resources for each BWP of a cell or CC that transmits a corresponding CSI report. The PUCCH resource can be a resource belonging to PUCCH format 2 or PUCCH format 3 or PUCCH format 4.

[0249] [Table 25]

[0250]

[0251] For the PUCCH resource, the transmission period and offset are configured by reportSlotConfig in [Table 23].

[0252] In the case of HARQ-ACK transmission, the resource set of the PUCCH resource to be transmitted is first selected according to the payload of the UCI including the corresponding HARQ-ACK. That is, the PUCCH resource set having the smallest payload not less than the UCI payload is selected. Next, the PUCCH resource in the PUCCH resource set can be selected by the PUCCH resource indicator (PRI) of the DCI scheduling the TB corresponding to the corresponding HARQ-ACK, and the PRI can be the PUCCH resource indicator specified in [Table 5] or [Table 6]. The relationship between the PRI and the PUCCH resource selected from the PUCCH resource set can be as shown in [Table 26].

[0253] [Table 26]

[0254]

[0255] If the number of PUCCH resources in the selected PUCCH resource set is greater than 8, the PUCCH resource can be selected by the following equation.

[0256] [Equation 1]

[0257]

[0258] In the above equation, r PUCCH denotes the index of the selected PUCCH resource in the PUCCH resource set, R PUCCH denotes the number of PUCCH resources belonging to the PUCCH resource set, Δ PRI denotes the PRI value, N CCE，p denotes the total number of CCEs of the CORESET to which the DCI belongs, and N CCE，pindicates a first CCE index in which the DCI is received.

[0259] The time at which the corresponding PUCCH resource is transmitted is after a K1 slot from the TB transmission corresponding to the corresponding HARQ-ACK. Candidates for the K1 value are configured as an upper layer, and more specifically, in the dl-DataToUL-ACK parameter in PUCCH-Config specified in [Table 21]. The K1 value of one of these candidates can be selected by the PDSCH-to-HARQ feedback timing indicator in the DCI that schedules the TB, and the value can be a value specified in [Table 5] or [Table 6]. Meanwhile, the unit of the K1 value can be a slot unit or a sub-slot unit. Here, a sub-slot is a unit having a length smaller than that of a slot, and one or more symbols can constitute one sub-slot.

[0260] Next, a case in which two or more PUCCH resources are located in one slot will be described. When UCI is transmitted through two PUCCH resources in one slot / sub-slot i) each PUCCH resource does not overlap in units of symbols, and ii) at least one PUCCH resource can be a short PUCCH, the terminal can transmit UCI through one or two PUCCH resources in one slot or sub-slot. Meanwhile, the terminal can not expect to transmit multiple PUCCH resources for HARQ-ACK transmission in one slot.

[0261] Next, a PUCCH transmission procedure when two or more PUCCH resources overlap will be described. When two or more PUCCH resources overlap, one of the overlapping PUCCH resources can be selected according to the above conditions, or a new PUCCH resource can be selected, that is, the PUCCH resources to be transmitted should not overlap in units of symbols. In addition, all UCI payloads transmitted through the overlapping PUCCH resources can be multiplexed or partially discarded. First, case 1 in which multi-slot repetition is not configured in the PUCCH resource, and case 2 in which multi-slot repetition is configured will be described.

[0262] For case 1, when PUCCH resources overlap, case 1 is divided into case 1-1) when two or more PUCCH resources for HARQ-ACK transmission overlap, and case 1-2) for other cases.

[0263] Case 1-1) is shown in Figure 9 .

[0264] Figure 9 A view of a case in which multiple PUCCH resources for HARQ-ACK transmission for a PDSCH overlap when multi-slot repetition is not configured is shown according to an embodiment. Referring to Figure 9For two or more different PDCCHs (9-10, 9-11) scheduling PDSCH, when the transmission time slots of the PUCCH resources corresponding to each PDCCH are the same, the corresponding PUCCH resources can be considered to overlap each other. That is, when the uplink time slots corresponding to the K1 values (9-50, 9-51) indicated by the multiple PDSCHs are the same, the PUCCH resources corresponding to the respective PDSCHs can be considered to overlap each other.

[0265] At this time, among the PUCCH resources indicated by the PRI 9-40, 9-41 of the PDCCH, only the PUCCH resource 9-31 selected based on the PRI 9-41 corresponding to the last transmitted PDCCH 9-11 is selected and transmitted. Therefore, the HARQ-ACK information for the PDSCH 9-21 through the selected PUCCH resource 9-31, and all of the HARQ-ACK information of the other PUCCHs 9-30 overlapping the PUCCH resource 9-31 are transmitted after being encoded by the pre-defined HARQ-ACK codebook.

[0266] Next, a case 1-2) in which a PUCCH resource for HARQ-ACK transmission and a PUCCH resource for SR and / or CSI transmission overlap, or multiple PUCCH resources for SR and / or CSI transmission overlap will be described. In the above case, when multiple PUCCH resources transmitted in the same time slot overlap one or more symbols on the time axis, the corresponding PUCCH resources are defined as overlapping, and whether to multiplex UCI in these resources can be summarized as [Table 27].

[0267] [Table 27]

[0268]

[0269] According to the above table, when overlapping between PUCCH resources transmitting HARQ-ACK or between PUCCHs transmitting SR and CSI, these UCIs are always multiplexed.

[0270] On the other hand, when each PUCCH resource transmitting SR and HARQ-ACK overlaps, that is, in case 1-2-1, whether to perform UCI multiplexing is divided according to the format of the PUCCH resource.

[0271] - SR on PUCCH format 0 + HARQ-ACK on PUCCH format 1: SR is discarded, and only HARQ-ACK is transmitted

[0272] - Other cases: SR and HARQ-ACK are multiplexed

[0273] Further, in the remaining cases corresponding to Case 1-2-2, i.e., when HARQ-ACK and CSI overlap between transmitted PUCCH resources, or when CSI overlaps between multiple transmitted PUCCH resources, whether the CSIs are multiplexed can follow upper layer configuration. Further, the configuration of whether to multiplex between HARQ-ACK and CSI and the configuration of whether to multiplex between multiple CSIs can be performed independently.

[0274] For example, whether to multiplex between HARQ-ACK and CSI can be configured by the simultaneousHARQ-ACK-CSI parameter of each PUCCH format 2, 3, or 4, and the corresponding parameter can be configured as the same value of the PUCCH format. If multiplexing is configured not to be performed through the above-mentioned parameter, only HARQ-ACK can be transmitted, and the overlapping CSI can be discarded. Further, whether to multiplex between multiple CSIs can be configured by the multi-CSI-PUCCH-ResourceList parameter in PUCCH-Config. That is, when the multi-CSI-PUCCH-ResourceList parameter is configured, multiplexing between CSIs can be performed, otherwise, only the PUCCH corresponding to the CSI having a higher priority can be transmitted according to the priority between CSIs.

[0275] When UCI multiplexing is performed as described above, the method of selecting a PUCCH resource for transmitting the corresponding UCI resource and the multiplexing method can vary according to the information of the UCI being overlapped and the format of the PUCCH resource, which can be summarized as [Table 28].

[0276] [Table 28]

[0277]

[0278] Each of the options in the above table is as follows.

[0279] - Option 1: PUCCH resource selection is different depending on the SR value of the SR PUCCH resource overlapping with the HARQ-ACK PUCCH resource. That is, if the SR value is positive, the PUCCH resource of the SR is selected, and if the SR value is negative, the PUCCH resource of the HARQ-ACK is selected. The HARQ-ACK information is transmitted to the selected PUCCH resource.

[0280] - Option 2: The HARQ-ACK information and the SR information are multiplexed and transmitted to the PUCCH resource for HARQ-ACK.

[0281] - Option 3: SR information and HARQ-ACK information are multiplexed and transmitted to the PUCCH resource for CSI.

[0282] - Option 4: PUCCH resource for overlapping HARQ-ACK is transmitted. - Detailed operation is described in the above case 1-1).

[0283] - Option 5: When the PUCCH resource for HARQ-ACK corresponding to the PDSCH scheduled by the PDCCH and the resource for CSI transmission overlap and the multiplexing between HARQ-ACK and CSI is configured to the upper layer, the PUCCH resource for HARQ-ACK information and CSI information are multiplexed and transmitted.

[0284] - Option 6: When the PUCCH resource for HARQ-ACK corresponding to the semi-persistent scheduling (SPS) PDCCH and the PUCCH resource for CSI transmission overlap and the multiplexing between HARQ-ACK and CSI is configured to the upper layer, HARQ-ACK information and CSI information are multiplexed and transmitted to the PUCCH resource for HARQ-ACK.

[0285] If the PUCCH resource list for multiplexing to the upper layer, i.e., multi-CSI-PUCCH-ResourceList, is configured, all multiplexed UCI payloads among the resources in the list can be transmitted, and the UCI payload is transmitted after selecting one resource having the lowest index. If there is no resource in the list that can transmit all multiplexed UCI payloads, a resource having the largest index is selected, and HARQ-ACK and CSI reports corresponding to the number of transmittable resources are transmitted.

[0286] - Option 7: When multiple PUCCH resources for CSI transmission overlap and the multiplexing between multiple CSIs is configured to the upper layer, all UCI payloads multiplexed in the PUCCH resource list configured for CSI multiplexing to the upper layer, i.e., multi-CSI-PUCCH-ResourceList, can be transmitted, and the UCI payload is transmitted after selecting a resource having the lowest index. If there is no resource in the list that can transmit all multiplexed UCI payloads, a resource having the largest index is selected, and CSI reports corresponding to the number of transmittable resources are transmitted.

[0287] In the above, for convenience of description, a case where two PUCCH resources overlap is focused on, but the method can be similarly applied even when three or more PUCCH resources overlap. For example, when a PUCCH resource multiplexed with SR+HARQ-ACK overlaps with a CSI PUCCH resource, a multiplexing method between HARQ-ACK and CSI can be followed.

[0288] If transmission is configured without multiplexing between specific UCIs, according to the order of HARQ-ACK>SR>CSI, a UCI with a higher priority can be transmitted, and a UCI with a lower priority can be discarded. If transmission is configured without multiplexing when multiple CSI PUCCH resources overlap, a PUCCH corresponding to a CSI with a higher priority can be transmitted, and a PUCCH corresponding to another CSI can be discarded.

[0289] Next, Case 2, i.e., when multi-slot repetition is configured, is divided into Case 2-1) when two or more PUCCH resources for HARQ-ACK transmission are located in the same starting slot, and Case 2-2) the remaining cases. Each case is as shown in Figure 10

[0290] Figure 10 A view showing a case of PUCCH resource overlap when multi-slot repetition is configured according to an embodiment is shown.

[0291] Referring to Case 2-1), when multi-slot repetition is configured in a PUCCH resource for HARQ-ACK, i.e., PUCCH #1 is repeatedly transmitted over multiple slots (10-30, 10-40), and PUCCH #2 is also repeatedly transmitted over multiple slots (10-31, 10-41), if the starting slots of two PUCCHs indicated by K1 are the same, a single PUCCH resource (PUCCH transmitted at the last time point in one slot), i.e., PUCCH #2, can be selected in the same manner as in Case 1-1). Thus, HARQ-ACKs corresponding to PDSCH #1 and PDSCH #2 are multiplexed and transmitted to the corresponding PUCCH through a HARQ-ACK codebook.

[0292] For convenience of description, a case of multiple multi-slot repetition PUCCH overlap is exemplified, but the same method can be applied when there is overlap between a multi-slot repetition PUCCH and a PUCCH transmitted in a single slot.

[0293] ​Case 2-2) corresponds to a case in which overlapping occurs in units of symbols between a PUCCH for HARQ-ACK transmission and a PUCCH for SR or CSI transmission, or a PUCCH for multiple SR or CSI transmissions. That is, case 2-2) corresponds to a case in which PUCCH #1 is repeatedly transmitted over multiple slots (10-50, 10-51) and PUCCH #2 is also repeatedly transmitted over multiple slots (10-60, 10-61), and a case in which PUCCH #1 and PUCCH #2 overlap more than one symbol in one slot (10-70).

[0294] Between PUCCHs in which overlapping of more than one symbol occurs in a corresponding slot (10-70), UCI having a higher priority among UCI in the PUCCHs can be transmitted by comparing the priorities, and other UCI can be discarded from the corresponding slot. At this time, the priorities among the UCI can follow the order of HARQ-ACK > SR > CSI.

[0295] In addition, when multiple CSI PUCCH resources overlap, a PUCCH corresponding to high-priority CSI can be transmitted, and a PUCCH corresponding to another CSI can be discarded from the corresponding slot. The PUCCH transmission or discarding according to the priorities described above is performed only in a slot in which overlapping occurs in units of symbols, and is not performed in other slots. That is, a PUCCH in which multi-slot repetition is configured can be discarded in a slot in which overlapping occurs in units of symbols, but can be transmitted in the remaining slots configured.

[0296] In the above-described cases, for convenience of description, a case in which multiple multi-slot repetition PUCCHs overlap is exemplified, but the same method can be applied when overlapping exists between a multi-slot repetition PUCCH and a PUCCH transmitted in a single slot.

[0297] Next, a method of generating a HARQ-ACK codebook for transmitting HARQ-ACK on a selected PUCCH resource will be described. When a PDSCH is scheduled based on DCI information of a downlink data PDCCH, the PDSCH is transmitted, and mapping information of a time slot in which corresponding HARQ-ACK feedback is mapped and an uplink control channel PUCCH carrying HARQ-ACK feedback information is transmitted. Specifically, a time slot interval between a downlink data PDSCH and corresponding HARQ-ACK feedback can be indicated by a PDSCH-to-HARQ feedback timing indicator, and one of eight feedback timing offsets configured through a higher layer (e.g., RRC signaling) can be indicated. In addition, in order to convey a PUCCH resource including a type of an uplink control channel PUCCH to which HARQ-ACK feedback information is mapped, a position of a starting symbol, and a number of mapping symbols, one of eight resources configured as an upper layer through a PUCCH resource indicator can be indicated. The terminal collects and transmits HARQ-ACK feedback bits to transmit HARQ-ACK information to the base station. Hereinafter, the collected HARQ-ACK feedback bits can be referred to as a mixture of a HARQ-ACK codebook.

[0298] The base station can configure a type 1 HARQ-ACK codebook for the terminal to transmit HARQ-ACK feedback bits corresponding to PDSCHs that can be transmitted at a predetermined time slot position regardless of whether actual PDSCHs are transmitted. Alternatively, the base station can configure a type 2 HARQ-ACK codebook for the terminal to manage and transmit HARQ-ACK feedback bits corresponding to actually transmitted PDSCHs through a counter downlink assignment index (DAI) or a total DAI.

[0299] When the terminal receives a type 1 HARQ-ACK codebook, the terminal can determine the feedback bits to be transmitted through K1 candidate values, which is HARQ-ACK feedback timing information for PDSCH and a table including slot, starting symbol, symbol number, or length information to which PDSCH is mapped. The table including the starting symbol, symbol number, or length information of the PDSCH can be configured as higher layer signaling, or can be determined as a default table. In addition, the K1 candidate value can be determined as a default value, such as {1, 2, 3, 4, 5, 6, 7, 8} or higher layer signaling. When the PDSCH is transmitted in a single slot, the slot to which the PDSCH is mapped can be known through the K1 value, and if the PDSCH is repeatedly transmitted in multiple slots (slot aggregation), the upper layer parameter indicates the K1 value and the number of repeated transmissions, for example, the pdsch-AggregationFactor value configured in the PDSCH-Config IE in the active BWP. If the PDSCH is repeatedly transmitted in multiple slots, the K1 value is indicated based on the last slot in the PDSCH repeated transmission, and the slot to which the PDSCH is mapped is considered as pdsch-AggregationFactor slots from the last slot to be repeatedly transmitted, i.e., the slot where the repetition starts.

[0300] Suppose that the set of PDSCH reception candidate cases in a serving cell c is M A，c , M A，c can be determined in the following [Pseudo code 1] steps.

[0301] [Start Pseudo code 1]

[0302] - Step 1: Initialize j to 0, M A，c to an empty set, and HARQ-ACK transmission timing index k to 0.

[0303] - Step 2: Configure R for the set of each row in the table including slot, starting symbol, symbol number, or length information to which PDSCH is mapped. If each row of R is configured as an uplink symbol to which PDSCH is mapped according to higher layer configuration, the corresponding row is deleted from R.

[0304] - Step 3-1: If the terminal receives one PDSCH for unicast in one slot, and R is not an empty set, k is added to the set M A，c .

[0305] - Step 3-2: If the terminal receives more than one PDSCH in one slot, the maximum number of PDSCHs that can be assigned to different symbols in R is counted, the number of j is increased by 1, and they are added to M A，c .

[0306] - Step 4: Start from the second step again, and increase k by 1.

[0307] [End of pseudo code 1]

[0308] For MA and c defined as [pseudo code 1], HARQ-ACK feedback bits can be determined in the following [pseudo code 2] steps.

[0309] [Start of pseudo code 2]

[0310] - Step 1: Initialize HARQ-ACK reception occasion index m to 0, and HARQ-ACK feedback bit index j to 0.

[0311] - Step 2-1: If the terminal is indicated not to receive HARQ-ACK bundling of codewords through higher layer signaling, does not receive CBG transmission of PDSCH, and receives at most 2 codewords through 1 PDSCH, construct HARQ-ACK feedback bits for each codeword by increasing j by 1.

[0312] - Step 2-2: If the terminal is indicated to receive HARQ-ACK bundling of codewords through higher layer signaling, and is indicated to receive at most 2 codewords through 1 PDSCH, compose HARQ-ACK feedback bits for each codeword as one HARQ-ACK feedback bit through a binary AND operation.

[0313] - Step 2-3: If the terminal is indicated to transmit CBG of PDSCH through higher layer signaling, and is not indicated to receive at most 2 codewords through 1 PDSCH, construct HARQ-ACK feedback bits for each codeword of the number of CBGs by increasing j by 1.

[0314] - Step 2-4: If the terminal is indicated to transmit CBG of PDSCH through higher layer signaling, and is indicated to receive at most 2 codewords through 1 PDSCH, construct HARQ-ACK feedback bits for the number of CBGs by increasing j by 1, and add it to each codeword.

[0315] - Step 2-5: If the terminal is not indicated to transmit CBG of PDSCH through higher layer signaling, and is not indicated to receive at most 2 codewords through 1 PDSCH, construct HARQ-ACK feedback bits for each codeword.

[0316] - Step 3: Start from Step 2-1 again, and increase m by 1.

[0317] [End of pseudo code 2]

[0318] When the terminal receives a Type 2 HARQ-ACK codebook, the terminal determines the feedback bits to be transmitted by managing a counter downlink assignment index (DAI) or a total DAI corresponding to the HARQ-ACK feedback bits of the PDSCH and a K1 candidate value which is HARQ-ACK feedback timing information for the PDSCH. The K1 candidate value which is the HARQ-ACK feedback timing information for the PDSCH is composed of a combination of a default value and a value specified through higher layer signaling. For example, the default value can be configured as {1, 2, 3, 4, 5, 6, 7, 8}.

[0319] If the counter DAI of the DCI format 1_0 or the DCI format 1_1 of the PDSCH allocated in the serving cell c is referred to as and the total DAI of the DCI format 1_1 of the PDSCH allocated in the uplink control channel PDCCH monitoring timing m is then the Type 2 HARQ-ACK codebook can be configured in the following [pseudo code 3] steps.

[0320] [Start pseudo code 3]

[0321] - Step 1: Initialize the serving cell index c to 0, the PDCCH monitoring timing m to 0, j to 0, the DAI comparison index V temp , V temp is initialized to 0, and the HARQ-ACK feedback bit set VS is set to an empty set.

[0322] - Step 2: If the PDCCH monitoring timing m is before the downlink BWP change of the serving cell c or before the uplink BWP change of the PCell, and the downlink BWP change is not triggered by the DCI format 1_1 of the PDCCH monitoring timing m, c is excluded from the serving cell set.

[0323] - Step 3-1: If there is a PDSCH allocated by the PDCCH corresponding to the PDCCH monitoring timing m in the serving cell c, and if is less than or equal to V temp , j is increased by 1, and V temp is configured as In addition, if is an empty set, V temp2 is configured as and if is not an empty set, V temp2 is configured as

[0324] - Step 3-2: If there exists a PDSCH in the serving cell c which is allocated by the PDCCH corresponding to the PDCCH monitoring timing m, and the terminal is indicated not to receive HARQ-ACK bundling of codewords by higher layer signaling, and is indicated to receive at most two codewords from at least one downlink BWP of at least one serving cell by one PDSCH, the HARQ-ACK feedback bit for each codeword is constructed by increasing j by 1.

[0325] - Step 3-3: If there exists a PDSCH in the serving cell c which is allocated by the PDCCH corresponding to the PDCCH monitoring timing m, and the terminal is indicated to receive HARQ-ACK bundling of codewords by higher layer signaling, and is indicated to receive at most two codewords from at least one downlink BWP of at least one serving cell by one PDSCH, the HARQ-ACK feedback bit is composed of each codeword for one HARQ-ACK feedback bit by binary AND operation.

[0326] - Step 3-4: If there exists a PDSCH in the serving cell c which is allocated by the PDCCH corresponding to the PDCCH monitoring timing m, and the terminal is not indicated to receive at most two codewords by one PDSCH, the HARQ-ACK feedback bit is constructed for one codeword.

[0327] - Step 4: Start again from Step 2, and increase c by 1.

[0328] - Step 5: Start again from Step 2, and increase m by 1.

[0329] - Step 6: When V temp2 is less than V temp , increase j by 1.

[0330] - Step 7-1: If the terminal is indicated not to bundle HARQ-ACK for codewords by higher layer signaling, and is indicated to receive at most 2 codewords from at least one downlink BWP of at least one serving cell by one PDSCH, the total number of HARQ-ACK feedback bits is configured as 2·(4·j+V temp2 ).

[0331] - Step 7-2: If the terminal is indicated to bundle HARQ-ACK for codewords by higher layer signaling, or is not indicated to receive at most 2 codewords by 1 PDSCH, the total number of HARQ-ACK feedback bits is configured as 4·j+V temp2 .

[0332] - Step 8: For the HARQ-ACK feedback bits not configured in Steps 3-1, 3-2, 3-3, and 3-4, the HARQ-ACK feedback bits are determined using NACK.

[0333] [End of pseudo code 3]

[0334] Figure 11 A view of a base station and a terminal radio protocol structure when single cell, carrier aggregation, and dual connectivity are performed is shown according to an embodiment.

[0335] Referring to Figure 11 , the radio protocol of the next-generation mobile communication system includes NR service data adaptation protocol (SDAP) 1125 and 1170, NR packet data convergence protocol (PDCP) 1130 and 1165, and NR radio link control (RLC) 1140 and 1155, and NR medium access control (MAC) in the terminal and the NR base station 1135 and 1160, respectively.

[0336] The main functions of the NR SDAPs 1125 and 1170 can include some of the following functions.

[0337] - Transmission of user plane data

[0338] - Mapping between QoS flows and DRBs for both DL and UL

[0339] - Marking of QoS flow ID in both DL and UL data packets

[0340] - Mapping of reflective QoS flows to DRB for UL SDAP PDU

[0341] For the SDAP layer device, the terminal can be configured by an RRC message whether to use the header of the SDAP layer device for each PDCP layer device, each bearer, or each logical channel, or whether to use the function of the SDAP layer device, and when the SDAP header is configured, the NAS QoS reflection configuration 1-bit indicator (NAS reflective QoS) and the AS QoS reflection configuration 1-bit indicator (AS reflective QoS) of the SDAP header indicate that the terminal can update or reconfigure the mapping information of the QoS flow and the data bearer of the uplink and the downlink. The SDAP header can include QoS flow ID information indicating QoS. The QoS information can be used as data processing priority and scheduling information to support a smooth service.

[0342] The main functions of the NR PDCP 10-30 and 10-65 can include some of the following functions.

[0343] - Header compression and decompression: ROHC only

[0344] - Transfer of user data

[0345] - In-sequence delivery of upper layer PDUs

[0346] - Out-of-sequence delivery of upper layer PDUs

[0347] - PDCP PDU reordering for reception

[0348] - Duplicate detection of lower layer SDUs

[0349] - Re-transmission of PDCP SDUs

[0350] - Ciphering and deciphering

[0351] - Timer-based SDU discard in uplink

[0352] In the above, the in-sequence reordering function of the NR PDCP device refers to a function of reordering PDCP PDUs received from a lower layer in sequence based on a PDCP sequence number (SN), can include a function of delivering data to an upper layer in a reordered sequence, can include a function of directly sending without considering the sequence, can include a function of reordering and recording lost PDCP PDUs, can include a function of transmitting a status report of the lost PDCP PDUs to a transmission side, or can include a function of requesting retransmission of the lost PDCP PDUs.

[0353] The main functions of the NR RLC 1135 and 1160 can include some of the following functions.

[0354] - Transfer of upper layer PDUs

[0355] - In-sequence delivery of upper layer PDUs

[0356] - Out-of-sequence delivery of upper layer PDUs

[0357] - Error correction through ARQ

[0358] - Concatenation, segmentation, and reassembly of RLC SDUs

[0359] - Re-segmentation of PDCP data PDUs

[0360] - Reordering of PDCP data PDUs

[0361] - Duplicate detection

[0362] - Protocol error detection

[0363] - RLC SDU discard

[0364] - RLC re-establishment

[0365] In the above, the in-sequence delivery of the NR RLC device refers to a function of sequentially transmitting the RLC SDU received from the lower layer to the upper layer, and can include a function of reassembling and delivering when one RLC SDU is initially divided into a plurality of RLC SDUs and received, can include a function of rearranging the received RLC PDU based on the RLC sequence number (SN) or the PDCP sequence number (SN), can include a function of reordering and recording the lost RLC PDU, can include a function of reporting the status of the lost RLC PDU to the transmission side, can include a function of requesting retransmission of the lost RLC PDU, can include a function of sequentially forwarding only the RLC PDU before the lost RLC SDU when there is a lost RLC SDU, can include a function of sequentially delivering all RLC SDUs received before the start of a predetermined timer to the upper layer even if there is a lost RLC SDU if the predetermined timer expires, or can include a function of sequentially delivering all received RLC SDUs to the upper layer even if there is a lost RLC SDU if the predetermined timer expires. In addition, the RLC PDU can be processed in the order in which they are received (regardless of the serial number or the sequence number, in the order of arrival), and delivered to the PDCP device in any order (out-of-sequence delivery), and in the case of a segment, the segment that is stored in the buffer or will be received later can be received and reconstructed into a complete RLC PDU, processed, and then transmitted to the PDCP device. The NR RLC layer can not include a connection function, and the function can be performed in the NR MAC layer or replaced by the multiplexing function of the NR MAC layer.

[0366] In the above, the out-of-sequence delivery of the NR RLC device refers to a function of directly transmitting the RLC PDU received from the lower layer to the upper layer regardless of the order, and can include a function of reassembling and delivering when one RLC SDU is initially divided into a plurality of RLC PDUs and received, or can include a function of storing the RLC SN or the PDCP SN of the received RLC PDU and ordering the order to record the lost RLC PDU.

[0367] The NR MAC 1140 and 1155 can be connected to several NR RLC layer devices configured in one terminal, and the main function of the NR MAC can include some of the following functions.

[0368] - Mapping between logical channels and transport channels

[0369] - Multiplexing / demultiplexing of MAC SDUs

[0370] - Scheduling information reporting

[0371] - Error correction through HARQ

[0372] - Priority handling between logical channels of one UE

[0373] - Priority handling between UEs through dynamic scheduling

[0374] - MBMS service identification

[0375] - Transport format selection

[0376] - Padding

[0377] The NR PHY layers 1145 and 1150 can perform channel coding and modulation on upper layer data, make OFDM symbols and transmit them to a radio channel, or demodulate and channel-decode OFDM symbols received through a radio channel to deliver them to upper layers.

[0378] The detailed structure of the radio protocol structure can change according to a carrier (or cell) operation method. For example, when a base station transmits data to a terminal based on a single carrier (or cell), the base station and the terminal use a protocol structure having a single structure per layer, such as 1100. On the other hand, when the base station transmits data to the terminal based on carrier aggregation (CA) using multiple carriers in a single TRP, the base station and the terminal have a single structure up to the RLC, as in 1110, but use a protocol structure for multiplexing the PHY layer through the MAC layer. As another example, when the base station transmits data to the terminal based on dual connectivity (DDC) using multiple carriers in multiple TRPs, the base station and the terminal have a single structure up to the RLC, as in 1120, but use a protocol structure for multiplexing the PHY layer through the MAC layer.

[0379] Referring to the above PUCCH-related description, the current Rel-15 NR focuses on PDSCH transmission from a single cell / transmission point / panel / beam (hereinafter, referred to as a transmission-reception point (TRP)), or coherent PDSCH transmission for multiple TRPs, and transmission of only one PUCCH resource for HARQ-ACK in one slot as a HARQ-ACK transmission method.

[0380] On the other hand, the NR Release 16 supports non-coherent transmission per TRP, i.e., non-coherent joint transmission (NC-JT). At this time, each TRP participating in the NC-JT can simultaneously transmit a separate PDSCH to the terminal. Considering a case where the overhead due to information exchange between the TRPs is very large, such as a case where the backhaul delay time per TRP is long, the HARQ-ACK information for the PDSCH can be transmitted through one PUCCH resource, and the HARQ-ACK information can be transmitted through a separate PUCCH resource per TRP. In particular, when the HARQ-ACK information (or UCI information) is transmitted through a separate PUCCH resource for HARQ-ACK transmission per TRP, the HARQ-ACK information can be transmitted through time division multiplexing in a slot. There is no definition of a processing method for overlapping between PUCCH resources in Rel-15. In the present disclosure, by providing a processing method for the above-described case, the loss and transmission delay time of the uplink control information in the NC-JT transmission can be minimized. Meanwhile, when a plurality of PUCCH resources for HARQ-ACK transmission are included in one slot, the present disclosure can be applied regardless of whether the NC-JT transmission is performed.

[0381] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In the following description of the present disclosure, a detailed description of known functions or configurations incorporated herein will be omitted when it can make the subject matter of the present disclosure rather unclear. The terms to be described below are terms defined in consideration of functions in the present disclosure, and can vary according to users, user's intention, or customs. Therefore, the definition of the terms should be based on the contents throughout the specification.

[0382] Hereinafter, the base station is a subject that performs resource allocation of the terminal, and can be at least one of a gNode B (gNB), an eNode B (eNB), a Node B, a base station (BS), a radio access unit, a base station controller, or a node on a network. The terminal can include a user equipment (UE), a mobile station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In addition, the NR or LTE / LTE-A system will be described below as an example, but embodiments of the present disclosure can be applied to other communication systems having a similar technical background or channel type. In addition, embodiments of the present disclosure can be applied to other communication systems through some modifications within a range that does not too deviate from the scope of the present disclosure determined by those having skilled knowledge.

[0383] The content of the present disclosure is applicable to FDD and TDD systems.

[0384] Hereinafter, in the present disclosure, high layer signaling is a signal transmission method transmitted from a base station to a terminal using a downlink data channel of a physical layer, or a signal transmission method transmitted from a terminal to a base station using an uplink data channel of a physical layer, and can be referred to as RRC signaling, PDCP signaling, or a medium access control (MAC) control element (MAC CE).

[0385] Hereinafter, in the present disclosure, the terminal can use various methods in determining whether to apply cooperative communication, in which a PDCCH(s) allocating a PDSCH to which cooperative communication is applied has a specific format, a PDCCH(s) allocating a PDSCH to which cooperative communication is applied includes a specific indicator indicating whether cooperative communication is applied, a PDCCH allocating a PDSCH to which cooperative communication is applied is scrambled by a specific RNTI, or it is assumed that cooperative communication is applied in a specific part indicated by an upper layer. Hereinafter, for the convenience of description, receiving a PDSCH to which cooperative communication is applied based on a condition similar to the above by the terminal will be referred to as an NC-JT case.

[0386] Hereinafter, in the present disclosure, determining the priority between A and B can be differently applied, for example, selecting one having a higher priority to perform an operation corresponding thereto according to a predetermined priority rule, or omitting or discarding a lower priority operation.

[0387] Hereinafter, in the present disclosure, the above-described examples will be described through a plurality of embodiments, but the embodiments are not independent of each other, and one or more embodiments can be simultaneously or in combination applied.

[0388] <First embodiment: DCI reception of NC-JT>

[0389] Unlike the past, a 5G wireless communication system can support not only a service requiring a high transmission speed, but also a service having a very short transmission delay and a service requiring a high connection density. In a wireless communication network including a plurality of cells, transmission and reception points (TRPs), or beams, cooperative transmission between each of the cells, TRPs, and / or beams is one of basic techniques capable of satisfying various service requirements by increasing the signal strength received by a terminal or effectively performing interference control between the cells, TRPs, and / or beams.

[0390] Joint transmission (JT) is a representative transmission technique for cooperative communication as described above, and one terminal is supported by different cells, TRPs, and / or beams through the joint transmission technique to increase the signal strength received by the terminal. Meanwhile, since the channels of each cell, TRP, or / and beam and the terminal can have significantly different characteristics, different precoding, modulation and coding schemes (MCS), and resource allocation need to be applied to the link between each cell, TRP, or / and beam and the terminal. In particular, in the case of non-coherent joint transmission (NC-JT) supporting non-coherent precoding between each cell, TRP, or / and beam, it is important to configure separate DL (downlink) transmission information for each cell, TRP, or / and beam. Meanwhile, the separate DL transmission information configuration of each cell, TRP, and / or beam is a major factor in increasing the payload required for DL DCI transmission, which can adversely affect the reception performance of the physical downlink control channel (PDCCH) that transmits the DCI. Therefore, it is necessary to carefully design a trade-off between the amount of DCI information and the PDCCH reception performance to support JT.

[0391] Figure 12 A view showing an example of antenna port configuration and resource allocation for cooperative communication according to some embodiments in a wireless communication system according to embodiments is illustrated.

[0392] Reference Figure 12 , an example of joint resource allocation according to TRP according to joint transmission (JT) techniques and cases is illustrated. In Figure 12 , 1200 is an example of coherent joint transmission (C-JT) supporting coherent precoding between each cell, TRP, or / and beam. In C-JT, a single data (PDSCH) is transmitted to the terminal 1215 from TRP A (1205) and TRP B (1210), and joint precoding can be performed in multiple TRPs. This can mean that TRP A (1205) and TRP B (1210) transmit DMRS through the same DMRS port (e.g., DMRS ports A and B in both TRPs) to receive the same PDSCH. In this case, the terminal can receive one DCI information for receiving one PDSCH demodulated based on the DMRS transmitted through the DMRS ports A and B.

[0393] In Figure 12 , 1220 is an example of non-coherent joint transmission (NC-JT) supporting non-coherent precoding between each cell, TRP, or / and beam.

[0394] In the case of NC-JT, PDSCHs can be transmitted to the terminal 1235 for each cell, TRP, or / and beam, and precoding can be applied individually to each PDSCH. Each cell, TRP, or / and beam transmits a different PDSCH to improve throughput compared to single cell, TRP, or / and beam transmission, or each cell, TRP, or / and beam can repeatedly transmit the same PDSCH to improve reliability compared to single cell, TRP, or / and beam transmission.

[0395] Various radio resource allocations can be considered, such as when the frequency and time resources used for transmitting PDSCHs by multiple TRPs are all the same (1240), when the frequency and time resources used by multiple TRPs do not overlap at all (1245), or when some of the frequency and time resources used by multiple TRPs overlap (1250). When multiple TRPs repeatedly transmit the same PDSCH to improve reliability in each of the above radio resource allocations, if the receiving terminal does not know whether the corresponding PDSCH is repeatedly transmitted, the corresponding terminal can have limitations in improving reliability because the terminal cannot perform combining on the corresponding PDSCH in the physical layer. Accordingly, the disclosure provides a repetition transmission instruction and configuration method for improving NC-JT transmission reliability.

[0396] For NC-JT support, various forms, structures, and relationships of DCI can be considered to simultaneously allocate multiple PDSCHs to one terminal.

[0397] Figure 13 A view showing an example of downlink control information (DCI) configuration for cooperative communication in a wireless communication system according to an embodiment is illustrated.

[0398] Referring to Figure 13 , four examples of DCI design for NC-JT support are illustrated.

[0399] Referring to Figure 13 Case #1 (1300) is an example in which, in the case of transmitting different (N-1) PDSCHs from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) in addition to a serving TRP (TRP#0) used when a single PDCCH is transmitted, control information for PDSCHs transmitted in (N-1) additional TRPs is transmitted in the same form (same DCI format) as control information for a PDSCH transmitted in the serving TRP. That is, a terminal can obtain control information for PDSCHs transmitted from different TRPs (DCI#0 to DCI#(N-1)) through DCIs having the same DCI format and the same payload (TRP#0 to TRP#(N-1)).

[0400] In the above-described Case #1, the freedom of control (allocation) of each PDSCH can be completely guaranteed, but when each DCI is transmitted in different TRPs, a coverage difference of each DCI can occur, and reception performance can deteriorate.

[0401] Case #2 (1305) is an example in which, in addition to the serving PDSCH (TRP #0) used when a single PDSCH is transmitted, control information of PDSCHs transmitted from (N-1) additional TRPs (TRP #1 to TRP #(N-1)) is transmitted in a different form (different DCI format or different DCI payload) from the control information of the PDSCH transmitted from the serving TRP. For example, in the case where DCI #0 transmits control information for the PDSCH transmitted in the serving TRP (TRP #0), all of the information elements of DCI format 1_0 to DCI format 1_1 are included, but in the case where "shortened" DCI (sDCI #0 to sDCI #(N-2)) transmits control information of the PDSCH transmitted from the cooperating TRP (TRP #1 to TRP #(N-1)), some of the information elements of DCI format 1_0 to DCI format 1_1 can be included. Therefore, in the case where sDCI transmits control information of the PDSCH transmitted in the cooperating TRP, the payload can be small compared to the normal DCI (nDCI) that transmits control information of the PDSCH transmitted from the serving TRP, or the payload can include as many reserved bits as the number of bits that is smaller than nDCI.

[0402] In the above-described Case #2, the freedom of control (allocation) of each PDSCH can be limited depending on the content of the information elements included in the sDCI, but since the reception performance of the sDCI is superior to the reception performance of the nDCI, the probability of occurrence of a coverage difference of each DCI can be reduced.

[0403] Case #3 (1310) is an example in which, in the case where (N-1) PDSCHs are transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) instead of a serving TRP (TRP#0) used when a single PDSCH is transmitted, control information for the PDSCHs transmitted from the (N-1) additional TRPs is transmitted in a format (different DCI format or different DCI payload) different from that of the control information for the PDSCH transmitted from the serving TRP. For example, in the case where DCI#0 transmits control information for the PDSCH transmitted in the serving TRP (TRP#0), all information elements of DCI format 1_0 to DCI format 1_1 are included, and in the case of control information for the PDSCHs transmitted from the cooperating TRPs (TRP#1 to TRP#(N-1)), only some of the information elements of DCI format 1_0 to DCI format 1_1 can be collected and transmitted in one "secondary" DCI (sDCI). For example, the sDCI can have at least one of the HARQ-related information such as frequency domain resource allocation, time domain resource allocation, and MCS of the cooperating TRPs. In addition, for information not included in the sDCI, such as a bandwidth part (BWP) indicator or a carrier indicator, the information can follow the DCI (DCI#0, normal DCI, nDCI) of the serving TRP.

[0404] In case #3, the degree of freedom of each PDSCH control (allocation) can be limited according to the content of the information elements included in the sDCI, but compared to case #1 or case #2, the reception performance of the sDCI can be adjusted, and the complexity of DCI blind decoding can be reduced.

[0405] Case #4 (1315) is an example in which, in the case where (N-1) PDSCHs are transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) instead of a serving TRP (TRP#0) used when a single PDSCH is transmitted, control information for the PDSCHs transmitted from the (N-1) additional TRPs is transmitted in a DCI (long DCI, lDCI) as control information for the PDSCH transmitted from the serving TRP. That is, the terminal can acquire control information for the PDSCHs transmitted from different TRPs (TRP#0 to TRP#(N-1)) through a single DCI. In case #4, the complexity of DCI blind decoding of the terminal can not increase, but the PDSCH control (allocation) degree of freedom can be low, for example, due to a limited number of cooperating TRPs due to long DCI payload limitations.

[0406] In the following description and embodiments, sDCI can refer to various secondary DCI such as shortened DCI, secondary DCI, or normal DCI including PDSCH control information transmitted from a cooperating TRP (PDI formats 1_0 to 1_1 described above). If not specifically limited, the description is similarly applicable to various secondary DCI.

[0407] In the following description and embodiments, the above-described Case #1, Case #2, and Case #3 in which one or more DCI (PDCCH) is used for NC-JT support are divided into multiple PDCCH-based NC-JT, and in the above-described Case #4, a single DCI (PDCCH) for NC-JT support can be classified as a single PDCCH-based NC-JT.

[0408] In embodiments of the disclosure, when actually applied, "cooperating TRP" can be replaced with various terms such as "cooperating panel" or "cooperating beam."

[0409] In embodiments of the disclosure, the term "when NC-JT is applied" can be interpreted in various ways depending on the case, such as "when the terminal receives one or more PDSCHs from one BWP at the same time," "when the terminal receives two or more PDSCHs from one BWP at the same time based on a transmission configuration indicator (TCI) indication," "when the terminal receives a PDSCH associated with one or more DMRS port groups (port groups)," and the like, but for ease of explanation, it is used as a kind of expression.

[0410] In the present disclosure, depending on the TRP deployment scenario, the radio protocol structure of NC-JT can be used in various ways. For example, if there is no or little backhaul delay between cooperating TRPs, a structure using MAC layer multiplexing similar to Figure 11 1110 (CA-like method) can be used. On the other hand, when the backhaul delay between cooperating TRPs is large enough to ignore the backhaul delay (for example, when information exchange such as CSI, scheduling, and HARQ-ACK between cooperating TRPs takes 2 milliseconds (ms) or more), a structure from the RLC layer of each TRP similar to Figure 11 1120 (DC-like method) can be used to ensure the robustness of the delay.

[0411] <Embodiment 1-1: Method of configuring a downlink control channel for NC-JT transmission based on multiple PDCCHs>

[0412] In NC-JT based on multiple PDCCHs, when DCI that schedules PDSCH of each TRP is transmitted, there can be CORESETs or search spaces classified for each TRP. The CORESET or search space of each TRP can be configured as at least one of the following.

[0413] · By higher layer indexing of CORESET: The TRP that transmits the PDCCH in the corresponding CORESET can be distinguished by the higher layer index value of each set CORESET. That is, in a set of CORESETs having the same higher layer index value, it can be considered that the same TRP transmits the PDCCH or the PDCCH that schedules the PDSCH of the same TRP is transmitted.

[0414] · Multiple PDCCH-Config configuration: Multiple PDCCH-Configs are configured in one BWP, and each PDCCH-Config can be considered to be configured for each TRP PDCCH. Here, a list of TRP-specific CORESETs and / or a list of search spaces of TRPs can be configured.

[0415] · CORESET beam / beam group configuration: By the beam or beam group set for each CORESET, the TRP corresponding to the corresponding CORESET can be identified. For example, when the same TCI state is configured in multiple CORESETs, the corresponding CORESET can be considered to be transmitted by the same TRP, or the PDCCH that schedules the PDSCH of the same TRP in the corresponding CORESET can be transmitted.

[0416] · Search space beam / beam group configuration: A beam or beam group is configured for each search space, and by this, the TRP of each search space can be classified. For example, when the same beam / beam group or TCI state is configured in multiple search spaces, in the search space, it can be considered that the same TRP transmits the PDCCH, or it can be considered that the PDCCH that schedules the PDSCH of the same TRP is transmitted in the search space.

[0417] By dividing the CORESET or search space for each TRP as described above, the PDSCH and HARQ-ACK information can be classified for each TRP, and thus, an independent HARQ-ACK codebook can be generated for each TRP, and an independent PUCCH resource can be used.

[0418] <Second embodiment: HARQ-ACK information transmission method for NC-JT transmission>

[0419] The following embodiment provides a detailed method of transmitting HARQ-ACK information for NC-JT transmission.

[0420] FIG. 14A illustrates a view of HARQ-ACK reporting for non-coherent joint transmission (NC-JT) transmission according to an embodiment, FIG. 14B is a view illustrating HARQ-ACK reporting for non-coherent joint transmission (NC-JT) transmission according to an embodiment, FIG. 14C is a view illustrating HARQ-ACK reporting for non-coherent joint transmission (NC-JT) transmission according to an embodiment, and FIG. 14D is a view illustrating HARQ-ACK reporting for non-coherent joint transmission (NC-JT) transmission according to an embodiment.

[0421] First, FIG. 14A (Option #1: HARQ-ACK for single PDCCH NC-JT) 14-00 illustrates a case where HARQ-ACK information for one or more PDSCHs 14-05 scheduled by a TRP is transmitted through one PUCCH resource 14-10 in the case of NC-JT based on a single PDCCH. The PUCCH resource can be indicated by the PRI value and the K1 value in the DCI described above.

[0422] FIGS. 14B (Option #2) to 14D (Option #4) 14-20, 14-40, 14-60 illustrate the case of NC-JT based on multiple PDCCHs. At this time, each option can be classified according to the number of PUCCH resources through which HARQ-ACK information corresponding to the PDSCH of each TRP is transmitted and the location of the PUCCH resources on the time axis.

[0423] FIG. 14B (Option #2: Joint HARQ-ACK) 14-20 illustrates a case where HARQ-ACK information corresponding to PDSCHs 14-25 and 14-26 of each TRP is transmitted through one PUCCH resource. All HARQ-ACK information of each TRP can be generated based on a single HARQ-ACK codebook, or the HARQ-ACK information of each TRP can be generated based on separate HARQ-ACK codebooks.

[0424] When separate HARQ-ACK codebooks for each TRP are used, the TRP can be classified based on at least one of a set of CORESETs having the same upper index, a set of CORESETs belonging to the same TCI state, beam, or beam group, or a set of search spaces belonging to the same TCI state, beam, or beam group, as defined in Example 1-1.

[0425] FIG. 14C (Option #3: Time Division Multiplexed (TDMed) separate HARQ-ACK per TRP) 14-40 illustrates a case where HARQ-ACK information corresponding to PDSCHs 14-45 and 14-46 of each TRP is transmitted through PUCCH resources 14-50 and 14-51 of different slots 14-52 and 14-53. The slot through which the PUCCH resource of each TRP is transmitted can be determined by the K1 value described above. If the K1 values indicated by the multiple PDCCHs indicate the same slot, all the corresponding PDCCHs can be considered to be scheduled in the same TRP, and all the HARQ-ACK information corresponding thereto can be transmitted.

[0426] FIG. 14D (Option #4: Intra-slot TDMed separate HARQ-ACK) 14-60 illustrates a case where HARQ-ACK information corresponding to PDSCHs 14-65 and 14-66 of each TRP is transmitted in different symbols in the same slot 14-75 through different PUCCH resources 14-70 and 14-71. The slot through which the PUCCH resource of each TRP is transmitted can be determined by the K1 value described above, and if the K1 values indicated by the multiple PDCCHs indicate the same slot, at least one of the following methods determines the PUCCH resource selection and transmission symbol

[0427] • Configuring PUCCH resource groups for each TRP

[0428] The PUCCH resource group for HARQ-ACK transmission of each TRP can be configured. When the TRP of each CORESET / search space is classified as Example 1-1, the PUCCH resource for HARQ-ACK transmission of the TRP can be selected in the PUCCH resource group of the corresponding TRP. It can be expected that TDM is performed between the PUCCH resources selected from different PUCCH resource groups, that is, it can be expected that the selected PUCCH resources do not overlap in units of symbols. As described above, a separate HARQ-ACK codebook for each TRP can be generated and transmitted to the PUCCH resource selected for each TRP.

[0429] • Indicating different PRI for each TRP

[0430] When the TRP of each CORESET / search space is classified as Example 1-1, the PUCCH resource of each TRP can be selected according to the PRI. That is, the PUCCH resource selection procedure in the above-described Rel-15 can be independently performed for each TRP. At this time, the PRI used to determine the PUCCH resource for each TRP can be different. For example, the terminal can not expect the PRI used for PUCCH resource determination for each TRP to be indicated with the same value. In addition, it can be desirable to TDM between the PUCCH resources corresponding to the PRI of each TRP. That is, it can be desirable for the selected PUCCH resources not to overlap in units of symbols. As described above, a separate HARQ-ACK codebook for each TRP can be generated and transmitted to the PUCCH resource selected for each TRP.

[0431] • Defining K1 value in units of sub-slot

[0432] The PUCCH resource selection procedure in Rel-15 is as follows, but one value can be defined in units of sub-slot. For example, the HARQ-ACK codebook for PDSCH / PDSCH indicated to be reported in the same sub-slot can be generated and transmitted through the PDSCH resource indicated as the PRI. The HARQ-ACK codebook generation and PUCCH resource selection procedure can be independent of whether the TRP is classified for each CORESET / search space.

[0433] When the terminal supports NC-JT reception, one of the upper layer configuration options can be configured, or one of the options can be implicitly selected depending on the situation. For example, Option 2 and one of Option 3 / 4 can be configured as the upper layer for a terminal supporting NC-JT based on multiple PDCCHs. As another example, depending on whether NC-JT based on a single PDCCH or NC-JT based on multiple PDCCHs is supported / configured, Option 1 can be selected for NC-JT based on a single PDCCH, and one of Options 2 / 3 / 4 can be selected for NC-JT based on multiple PDCCHs. As another example, in NC-JT based on multiple PDCCHs, the used option can be determined according to the selection of PUCCH resources. When PUCCH resources of the same slot are selected from different TRPs, if the corresponding PUCCH resources are different and do not overlap in units of symbols, HARQ-ACK can be transmitted according to Option 4, and if the PUCCH resources overlap in units of symbols or are the same, HARQ-ACK can be transmitted according to Option 2. When PUCCH resources of different slots are selected from different TRPs, HARQ-ACK can be transmitted according to Option 3. The configuration of the options can depend on the terminal capability. For example, the base station can receive the terminal capability according to the above-described procedure, and can configure the options based on this. For example, Option 4 configuration can be allowed for a terminal supporting intra-slot TDMed separate HARQ-ACK, and a terminal not having this capability can not expect configuration according to Option 4.

[0434] <Third Embodiment: PUCCH-PUCCH Overlap Handling Method for NC-JT Based on Multiple PDCCHs>

[0435] In NC-JT based on multiple PDCCHs, when intra-slot TDMed separate HARQ-ACK is used, multiple HARQ-ACKs in one slot can be transmitted through PUCCH resources. This is different from Rel-15, which is limited so that only one HARQ-ACK is transmitted in one slot. Therefore, in this embodiment, a specific handling method for the case where overlap occurs between PUCCH resources for HARQ-ACK and PUCCH resources for other uplink control information is given.

[0436] In this embodiment, a method for the case where overlap occurs between PUCCH resources for which multiple repetitions are not configured will be described first. At this time, the following two cases shown in FIG. 15 will be described.

[0437] FIG. 15A illustrates a view of the case where overlap occurs between PUCCH resources according to an embodiment.

[0438] Referring to FIG. 15A, case 1 (15-10) illustrates a case where an overlap occurs between PUCCH resources #1 and #2 (15-11 and 15-12) for HARQ-ACK transmission and other PUCCH resource #3 (15-13).

[0439] Case 2 (15-20) illustrates a case where an overlap occurs between PUCCH resource #1 (15-21) for HARQ-ACK transmission and other PUCCH resource #3 (15-23).

[0440] According to the TRP-specific PUCCH resource configuration and HARQ-ACK transmission method described in example 2, some of the above cases can not occur.

[0441] For example, in the case of applying joint HARQ-ACK to time-slot inter-TDMed separate HARQ-ACK, only case 2 can occur.

[0442] On the other hand, in the case of applying time-slot intra-TDMed separate HARQ-ACK, both case 1 and case 2 can occur.

[0443] As another example, according to whether the PUCCH resource group of each TRP is configured as described in example 2, some of the above cases can not occur. If all PUCCH resources are classified according to the TRP-specific PUCCH resource group, only case 2 can occur. On the other hand, in the case where the PUCCH resource group of each TRP is not configured or only the PUCCH resources for HARQ-ACK transmission are classified according to the PUCCH resource group of each TRP, both case 1 and case 2 can occur.

[0444] A method of processing PUCCH according to the overlap of PUCCH resources according to FIG. 15A will be described in FIG. 15B.

[0445] FIG. 15B illustrates a view of a method of transmitting PUCCH when an overlap occurs between PUCCH resources according to an embodiment.

[0446] Referring to FIG. 15B, in operation 1530, the terminal can receive configuration information related to PUCCH resources. The configuration information can be received through higher layer signaling.

[0447] At this time, the configuration information can include one or more PUCCH resource sets as described above, and one or more PUCCH resources can be included in one PUCCH resource set. For details, refer to the above.

[0448] Further, in operation 1540, the terminal can receive DCI including resource allocation information. The resource allocation information can include at least one of information about resources for receiving downlink data and information about resources for transmitting uplink control information.

[0449] At this time, the information about resources for transmitting uplink control information can include an indicator indicating a PUCCH resource received through configuration information. Further, it can include information K1 about a slot position for transmitting the PUCCH resource. For details, refer to the above.

[0450] Further, when the terminal supports NC-JT reception, the terminal can receive DCI per TRP. At this time, as a method of receiving DCI, various methods proposed in Figure 13 may be used. For details, refer to the above.

[0451] Further, in step 1550, the terminal can identify a PUCCH resource for transmitting uplink control information. The terminal can identify the PUCCH resource based on at least one of configuration information or DCI.

[0452] When NC-JT is configured in the terminal, the terminal can transmit UCI for a plurality of TRPs, and can identify a plurality of PUCCH resources. At this time, when the plurality of PUCCH resources identified are located in one slot, as described above, a PUCCH resource group can be configured for each TRP, a different PRI can be indicated for each TRP, or a K1 value included in DCI can be defined in units of sub-slots to be allocated to other symbols within one slot. For details, refer to the above.

[0453] On the other hand, the terminal can transmit capability information about whether to transmit multiplexing control information for HARQ-ACK transmission through TDM PUCCH resources in one slot to the base station, and the base station can configure a plurality of PUCCH resources for HARQ-ACK transmission in one slot only when the terminal has the capability as described above. Details related to the capability transmission / reception method and the transmission / reception point in time are the same as described above, and will be omitted below.

[0454] When two or more PUCCH resources (PUCCH#1, PUCCH#2) are located in one slot, simultaneously, a PUCCH resource (PUCCH#3) for different UCI transmission can be allocated to the same slot. At this time, the other uplink information can include SR, QoS information, etc., or can include HARQ-ACK information of other TRPs. Meanwhile, for convenience of description, PUCCH#1 and PUCCH#2 which are TDMed on the time axis among the PUCCH resources illustrated in FIG. 15A can be referred to as a first PUCCH, and PUCCH#3 can be referred to as a second PUCCH. Alternatively, PUCCH#1, PUCCH#2, and PUCCH#3 can be referred to as a first PUCCH, a second PUCCH, and a third PUCCH, respectively.

[0455] Accordingly, in operation 1560, the terminal can identify whether an overlap has occurred between the PUCCH resources. At this time, the terminal can identify whether an overlap has occurred between the PUCCH resource (e.g., TDM PUCCH resource in a slot) identified in operation 1550 and another PUCCH resource. At this time, the other PUCCH resource can mean a resource for transmitting different UCI (e.g., UCI other than HARQ-ACK). As described above, the PUCCH resource (PUCCH#1, PUCCH#2) identified in operation 1550 can be referred to as a first PUCCH, and the other PUCCH resource (PUCCH#3) can be referred to as a second PUCCH.

[0456] At this time, the overlap between the PUCCH resources can mean an overlap in units of symbols. Accordingly, operation 1560 can refer to an operation of identifying whether there is a PUCCH resource overlapping the TDM PUCCH resource as illustrated in FIG. 15A in a slot.

[0457] As a result of the identification, if no overlap occurs, the terminal can transmit UCI through each PUCCH resource. For example, if the PUCCH resources corresponding to each of TRP 1 and TRP 2 are included in one slot, and intra-slot TDMed individual HARQ-ACK is configured, the terminal can multiplex and transmit the HARQ-ACK information of each TRP to the PUCCH resource of each TRP. At this time, the PUCCH resource of each TRP can be determined according to the PUCCH resource selection procedure in the intra-slot TDMed individual HARQ-ACK described above. Further, other uplink information can also be transmitted through the allocated PUCCH resource.

[0458] On the other hand, when an overlap occurs, case 1 and case 2 described in FIG. 15A can occur.

[0459] Accordingly, when it is determined in operation 1570 that the case corresponds to Case 1, the terminal can perform operations accordingly.

[0460] On the other hand, if it is determined in operation 1580 that the case corresponds to Case 2, the terminal can perform operations accordingly.

[0461] Details of operations according to Case 1 and Case 2 will be described below.

[0462] Returning to the description of FIG. 15A, in Case 1, whether the Rel-15 based PUCCH overlapping handling method is applicable can be determined according to the format of each PUCCH resource and transmission of SR or CSI through PUCCH resource #3. If SR is transmitted through PUCCH resource #3, the following problems can occur when the Rel-15 based PUCCH multiplexing method is applied.

[0463] It is assumed that one of the PUCCH resources for HARQ-ACK transmission is PUCCH format 1, and PUCCH resource #3 for SR transmission is PUCCH format 1. Hereinafter, for convenience of description, the PUCCH resource for HARQ-ACK transmission corresponding to PUCCH format 1 is referred to as PUCCH resource #1.

[0464] In this case, if SR is positive at this time, HARQ-ACK of PUCCH resource #1 should be transmitted through PUCCH resource #3. However, since PUCCH resource #3 is not TDMed with PUCCH resource #2, it is necessary to change the Rel-15 based handling method.

[0465] Accordingly, at least one of the following methods can be considered to solve the above problem.

[0466] • Method 1-1: When intra-slot TDMed separate HARQ-ACK is applied, when PUCCH resource (PUCCH format 1) for HARQ-ACK transmission and PUCCH resource (PUCCH format 1) for SR transmission overlap, the multiplexing rule is changed to drop SR.

[0467] • Method 1-2: When intra-slot TDMed separate HARQ-ACK is applied, PUCCH format 1 is not configured for HARQ-ACK transmission.

[0468] • Method 1-3: When intra-slot TDMed separate HARQ-ACK is applied, PUCCH format 1 is not configured for SR transmission.

[0469] • Method 1-4: When slot-wise TDMed separate HARQ-ACK is applied, the terminal does not expect overlap between PUCCH resource (PUCCH format 1) for HARQ-ACK transmission and PUCCH format 1 for SR transmission.

[0470] On the other hand, when the PUCCH multiplexing method based on Rel-15 is applied, the following problem can occur. It is assumed that the PUCCH resource for HARQ-ACK transmission is not PUCCH format 1. In this case, the same SR information is multiplexed and transmitted in both PUCCH resources for HARQ-ACK transmission. This can be a situation that is not desirable in the network. For example, multiple TRPs that receive HARQ-ACK can perform all response procedures for SR requests, and thus unnecessary control information transmission and reception and uplink resource allocation can occur. Therefore, a method of selecting one of PUCCH resources #1 and #2 and allowing SR to be multiplexed only for that resource is needed.

[0471] Therefore, at least one of the following methods can be considered to solve the above problem. Specifically, SR is multiplexed and transmitted to both PUCCH resources for HARQ-ACK transmission, or SR can be multiplexed and transmitted to any one of the two PUCCH resources, and the following methods can be considered as a method of selecting one PUCCH resource.

[0472] • Method 2-1: Selection according to index or order. For example, the PUCCH resource that is first transmitted on the time axis can be selected, or the PUCCH resource corresponding to low PRI or the PUCCH resource corresponding to low PUCCH resource group can be selected.

[0473] • Method 2-2: Selection according to maximum payload. For example, a PUCCH resource with a large maximum payload that can be transmitted can be selected in priority.

[0474] • Method 2-3: Selection according to PUCCH format. Long PUCCH with good coverage can be selected in priority to short PUCCH. In addition, PUCCH format 2 / 3 / 4 capable of transmitting a payload of more than 2 bits can be selected in priority to PUCCH 0 / 1.

[0475] • Method 2-4: Selection according to TRP. When it is necessary to transmit SR information to a specific TRP, a PUCCH resource corresponding to the same TRP can be selected. For example, a PUCCH resource for HARQ-ACK with the same spatial relation information as PUCCH resource #3 can be selected. Alternatively, a PUCCH resource in a PUCCH resource group belonging to the TRP corresponding to the SR can be selected. Alternatively, if a TRP index is configured in a CORESET where DCI scheduling PDSCH and HARQ-ACK PUCCH transmission, a TRP index corresponding to each SR ID can be configured or it can be assumed that the TRP index to which all SRs are transmitted is a specific value, e.g., TRP index 0. Alternatively, a TRP index can be configured in a PUCCH resource for transmitting an SR, or a specific value, e.g., TRP index 0, can be assumed. At this time, a PUCCH resource corresponding to HARQ-ACK with the same value as the TRP index associated with the above SR ID or the PUCCH for SR transmission can be selected. Alternatively, the TRP index can be expressed as a parameter set for PUCCH power control. As an example, the TRP index can be expressed by one or a combination of the following values in the following PUCCH-PowerControl IE configured as RRC.

[0476]

[0477] In more detail, the TRP index can correspond to a p0-PUCCH-Id value configured for PUCCH power control. For example, if the value of p0-PUCCH-Id is between 1 and 4, it can correspond to TRP index 0, and when the value of p0-PUCCH-Id is between 5 and 8, it can correspond to TRP index 1. The mapping between the range of p0-PUCCH-Id and the TRP index can change. Alternatively, the TRP index can correspond to a pathlossReferenceRS configured for PUCCH power control. Alternatively, the TRP index can correspond to a power control adjustment state index configured for PUCCH power control. The power control adjustment state index is an indicator indicating the power control state of the PUCCH resource, and can also be expressed by a representation such as a closed loop power control index and a TRP / panel specific closed loop power control index. When the value of the RRC parameter twoPUCCH-PC-AdjustmentStates is configured as twoStates, the power control adjustment state index can have one of two values (e.g., i0 or i1), where i0 can correspond to TRP index 0 and i1 can correspond to TRP index 1. The above i0 or i1 can be indicated in the form of a closedLoopIndex parameter value in the spatial relation information activated for each PUCCH / PUCCH group as shown below.

[0478]

[0479] According to the above description, a resource having a closedLoopIndex parameter included in the spatial relation information associated with the PUCCH resource configured as i0 can be regarded as a PUCCH resource corresponding to TRP index 0, and a resource having a closedLoopIndex parameter configured as i1 can be regarded as a PUCCH resource corresponding to TRP index 1.

[0480] On the other hand, the power control adjustment state index can be extended to be able to configure two per TRP. Thus, when the number of supported TRPs is at most 2, the total configurable power control adjustment state index can be extended to at most 4. For example, a value such as FourStates can be configured as a value of a twoPUCCH-PC-AdjustmentStates parameter, or a new parameter such as a fourPUCCH-PC-AdjustmentStates parameter can be configured. At this time, when a closedLoopIndex parameter included in the spatial relation information is configured as i0 and i1, it can be considered as TRP index 0, and when the closedLoopIndex parameter is configured as i2, i3, or a new parameter such as a closedLoopIndexNew parameter is additionally configured in the spatial relation information, it can be considered as TRP index 1. In addition, as described above, a connection between the PUCCH resource and the TRP index can be established.

[0481] If a PUCCH resource of a TRP to which an SR is to be transmitted is not selected (for example, due to lack of information such as spatial relation information), the terminal can not multiplex the SR and the HARQ-ACK. In this case, according to the order of HARQ-ACK > SR > CSI, the PUCCH resource or the UCI having a lower priority can be dropped.

[0482] Alternatively, in order to simplify the terminal operation, the base station can appropriately schedule the PUCCH resource or indicate the multiplexing configuration so that the above-described case does not occur.

[0483] Next, in case 1, if CSI is transmitted through the PUCCH resource #3, it can be determined whether multiplexing between HARQ-ACK and CSI is configured by a higher layer. If multiplexing is configured, the following problem can occur when applying the PUCCH multiplexing method based on Rel-15.

[0484] The same CSI information can be multiplexed to both PUCCH resources for HARQ-ACK transmission and transmitted, which can cause a waste of uplink transmission resources and transmission power due to repeated CSI payload transmission. Thus, a method of selecting one of the PUCCH resources #1 and #2 and allowing multiplexing of CSI only for that resource is required.

[0485] In order to solve the above-described problem, at least one of the following methods can be considered.

[0486] • Method 3-1: Selection according to index or order. For example, a PUCCH resource that is first transmitted on a time axis can be selected, or a PUCCH resource corresponding to a low PRI or a PUCCH resource corresponding to a low PUCCH resource group can be selected.

[0487] • Method 3-2: Selection according to maximum payload. A PUCCH resource having a large maximum payload that can be transmitted can be selected preferentially.

[0488] • Method 3-3: Selection according to PUCCH format. A long PUCCH having good coverage can be selected preferentially over a short PUCCH. Also, when reporting sub-band CSI, a PUCCH format 3 / 4 capable of sub-band CSI transmission can be selected preferentially over a PUCCH format 2 capable of only wideband CSI transmission.

[0489] • Method 3-4: Selection according to TRP. When only the channel state of a specific TRP is included in the CSI information, it can be desirable to multiplex the CSI information only on the PUCCH resource to be transmitted to the corresponding TRP. For this, for example, the PUCCH resource for HARQ-ACK with the same spatial relation information as PUCCH resource #3 can be selected. Alternatively, the PUCCH resource in the PUCCH resource group belonging to the TRP corresponding to the CSI information can be selected. Alternatively, if the TRP index is configured in the CORESET in which the DCI that has scheduled the PDSCH and the HARQ-ACK PUCCH transmission is transmitted, the TRP index can be configured in the CSI report / resource configuration or in the TRP index in the PUCCH resource for CSI report transmission. At this time, the PUCCH resource corresponding to the HARQ-ACK with the same value as the TRP index associated with the above-mentioned CSI PUCCH can be selected. If the PUCCH resource of the TRP to which the CSI is to be transmitted is not selected, the terminal can not multiplex the CSI with other CSI. In this case, according to the order of HARQ-ACK > SR > CSI, the PUCCH resource or UCI with lower priority can be dropped. When multiple CSIs overlap, the priority between CSIs can be applied. Alternatively, when the TRP index is configured in the CSI report / resource configuration or in the PUCCH resource for transmitting the CSI report, multiple CSIs with different TRP indexes can overlap. At this time, if the CSI is configured to be multiplexed, for example, when multi-CSI-PUCCH-ResourceList is configured, the TRP index of the PUCCH resource for transmitting the multiplexed CSI can not be clear. The above-mentioned case can be prevented by appropriately scheduling the PUCCH resource for CSI report transmission in the network. Alternatively, if the CSI report / resource with different TRP indexes is configured or activated / triggered, it can not be desirable to configure multi-CSI-PUCCH-ResourceList. Alternatively, the TRP index can be configured for each PUCCH resource corresponding to multi-CSI-PUCCH-ResourceList, or a specific TRP index value, for example, TRP index 0, can be assumed. Alternatively, in this case, even if multi-CSI-PUCCH-ResourceList is configured, multiplexing between overlapping CSI reports is not performed, and dropping according to the priority can be performed. The priority at this time can follow the CSI report priority based on Rel-15.

[0490] Alternatively, the TRP index can be represented as a parameter set for PUCCH power control. As an example, the TRP index can be represented by one of the following values or their combination in the following PUCCH-PowerControl IE configured as RRC.

[0491]

[0492] In more detail, the TRP index can correspond to a p0-PUCCH-Id value configured for PUCCH power control. For example, if the value of p0-PUCCH-Id is between 1 and 4, it can correspond to TRP index 0, and when the value of p0-PUCCH-Id is between 5 and 8, it can correspond to TRP index 1. The mapping between the range of p0-PUCCH-Id and the TRP index can change. Alternatively, the TRP index can correspond to a pathlossReferenceRS configured for PUCCH power control. Alternatively, the TRP index can correspond to a power control adjustment state index configured for PUCCH power control. The power control adjustment state index is an indicator indicating the power control state of the PUCCH resource, and can also be represented by an expression such as a closed loop power control index and a TRP / panel specific closed loop power control index. When the twoPUCCH-PC-AdjustmentStates value of the RRC parameter is configured as twoStates, the power control adjustment state index can have one of two values (e.g., i0 or i1), where i0 can correspond to TRP index 0, and i1 can correspond to TRP index 1. The above i0 or i1 can be indicated in the form of a closedLoopIndex parameter value in the spatial relation information activated for each PUCCH / PUCCH group as shown below.

[0493]

[0494] According to the above description, among the PUCCH resources, the resource having the closedLoopIndex parameter related to the spatial relation information configured as i0 can be considered as a PUCCH resource corresponding to TRP index 0, and the resource having the closedLoopIndex parameter configured as i1 can be considered as a PUCCH resource corresponding to TRP index 1.

[0495] On the other hand, the power control adjustment state index can be extended to be able to configure two per TRP. Thus, when the number of supported TRPs is at most 2, the total configurable power control adjustment state index can be extended to 4. For example, as a value of the twoPUCCH-PC-AdjustmentStates parameter, for example, FourStates can be configured, or a new parameter such as the fourPUCCH-PC-AdjustmentStates parameter can be configured. At this time, when the closedLoopIndex parameter related to the spatial relation information is configured as i0 and i1, it can be considered as TRP index 0, and when the closedLoopIndex parameter is configured as i2, i3, or a new parameter such as the closedLoopIndexNew parameter is additionally configured in the spatial relation information, it can be considered as TRP index 1. In addition, as described above, the association between the PUCCH resource and the TRP index can be established.

[0496] However, if CSI is transmitted through PUCCH resource #3 and multiplexing between HARQ-ACK and CSI is configured, a method of multiplexing and transmitting the same CSI information to two PUCCH resources can be used.

[0497] Alternatively, in order to simplify the terminal operation, the base station can appropriately schedule the PUCCH resource or indicate the multiplexing configuration so that the above-described case does not occur. For example, when simultaneousHARQ-ACK-CSI described above is configured, in case 1, a case in which the terminal can not expect to transmit CSI through PUCCH resource #3.

[0498] In case 2, the beams between the overlapping PUCCH resources can be different. This can be interpreted as the TRP to which UCI is transmitted through the overlapping PUCCH resources can be different. If multiplexing is configured between the corresponding PUCCH resources, a problem can occur in that some of the multiplexed UCI can be transmitted to an undesired TRP. To solve this problem, at least one of the following methods can be considered.

[0499] • Method 4-1: This method follows the beam applied to the PUCCH corresponding to the high-priority UCI among the multiplexed UCI. At least the high-priority UCI can be transmitted to the desired TRP. The UCI priority can be HARQ-ACK > SR > CSI. When multiple CSIs overlap, the priority between the CSIs can be applied.

[0500] • Method 4-2: When beams between overlapping PUCCHs are different, multiplexing can not be performed, which can take priority over upper layer configuration. Thus, only one of the overlapping PUCCHs can be selected and transmitted, and the rest can be discarded, and PUCCH selection can follow the priority between UCI contained in the overlapping PUCCHs. The UCI priority can be HARQ-ACK > SR > CSI. When multiple CSIs overlap, the priority between CSIs can be applied. The above PUCCH beams can be indicated by PUCCH spatial relation information. Alternatively, the above PUCCH beams can be replaced with a TRP that transmits the PUCCH, where the TRP can be represented by PUCCH spatial relation information, PUCCH resource group, TRP index, etc. For example, when a TRP index is configured in a CORESET that transmits DCI scheduling PDSCH and HARQ-ACK PUCCH transmission, the TRP index can be configured in CSI reporting / resource configuration, or in a TRP index in a PUCCH resource for CSI reporting transmission. At this time, a PUCCH resource corresponding to a CSI having the same value as the TRP index associated with the above HARQ-ACK PUCCH can be selected.

[0501] Alternatively, the TRP index configured in the CSI report or the PUCCH resource for SR or HARQ-ACK transmission can be represented as a parameter configured for PUCCH power control. As an example, the TRP index can be represented by one or a combination of the following values in the following PUCCH-PowerControl IE configured as RRC.

[0502]

[0503] In more detail, the TRP index can correspond to a p0-PUCCH-Id value configured for PUCCH power control. For example, if the value of p0-PUCCH-Id is between 1 and 4, it can correspond to TRP index 0, and when the value of p0-PUCCH-Id is between 5 and 8, it can correspond to TRP index 1. The mapping between p0-PUCCH-Id range and TRP index can change. Alternatively, the TRP index can correspond to a pathlossReferenceRS configured for PUCCH power control. Alternatively, the TRP index can correspond to a power control adjustment state index configured for PUCCH power control. The power control adjustment state index is an indicator indicating the power control state of a PUCCH resource, and can also be referred to in expressions such as closed loop power control index or TRP / panel specific closed loop power control index. When the value of the RRC parameter twoPUCCH-PC-AdjustmentStates is configured as twoStates, the power control adjustment state index can have one of two values (e.g., i0 or i1), where i0 is TRP index 0, i1 can correspond to TRP index 1. The above i0 or i1 can be indicated in the form of a closedLoopIndex parameter value in the spatial relation information activated by a PUCCH / PUCCH group as shown below.

[0504]

[0505] According to the above description, among the PUCCH resources, the resource having the closedLoopIndex parameter related to the spatial relation information configured as i0 can be considered as the PUCCH resource corresponding to the TRP index 0, and the resource having the closedLoopIndex parameter configured as i1 can be considered as the PUCCH resource corresponding to the TRP index 1. On the other hand, the power control adjustment state index can be extended to be able to configure two per TRP. Therefore, when the number of supported TRPs is at most 2, the total configurable power control adjustment state index can be extended to 4. For example, as a value of the twoPUCCH-PC-AdjustmentStates parameter, for example, FourStates can be configured, or a new parameter such as a fourPUCCH-PC-AdjustmentStates parameter can be configured. At this time, when the closedLoopIndex parameter related to the spatial relation information is configured as i0 and i1, it can be considered as the TRP index 0, and when the closedLoopIndex parameter is configured as i2, i3, or a new parameter, for example, a closedLoopIndexNew parameter is additionally configured, in the spatial relation information, it can be considered as the TRP index 1. In addition, as described above, the mapping between the PUCCH resource and the TRP index can be established.

[0506] If the TRP index is configured in the CSI report / resource configuration, or the TRP index is configured in the PUCCH resource for transmitting the CSI report, multiple CSIs having different TRP indexes can be overlapped. At this time, if the CSI is configured to be multiplexed, for example, when the multi-CSI-PUCCH-ResourceList described above is configured, the TRP index of the PUCCH resource for transmitting the multiplexed CSI can not be clear. The above situation can be prevented by appropriately scheduling the PUCCH resource for CSI report transmission in the network. Alternatively, if the CSI report / resource having different TRP indexes is configured or activated / triggered, it can not be desirable to configure the multi-CSI-PUCCH-ResourceList. Alternatively, the TRP index can be configured for each PUCCH resource corresponding to the multi-CSI-PUCCH-ResourceList, or a specific TRP index value, for example, the TRP index 0, can be assumed. Alternatively, in this case, even if the multi-CSI-PUCCH-ResourceList is configured, multiplexing between overlapping CSI reports is not performed, and dropping according to the PRI can be performed. The PRI at this time can follow the CSI report priority based on Rel-15.

[0507] • Method 4-3: In order to simplify terminal operation, the base station can appropriately schedule the PUCCH resource so that the PUCCH beam / TRP overlap does not occur in different cases.

[0508] At this time, the TRP or TRP index can be classified by the method described in Method 4-2. For example, the TRP index can be configured for each PUCCH resource. At the same time, the TRP index can not be configured in the PUCCH resource for HARQ-ACK transmission, or even if the TRP index is configured, the TRP index can not be used. Instead, the TRP index configured in the CORESET in which the DCI scheduling the PUCCH transmission is actually transmitted can be used. In addition, the terminal can not expect the TRP index configured for each PUCCH resource to be different from the TRP index value configured in the CORESET in which the DCI scheduling the PUCCH transmission is transmitted.

[0509] For example, the TRP index configured for each PUCCH resource can be expressed with a parameter configured for PUCCH power control. As an example, the TRP index can be expressed by one of the following values or a combination thereof in the following PUCCH-PowerControl IE configured as RRC.

[0510]

[0511] In more detail, the TRP index can correspond to the p0-PUCCH-Id value configured for PUCCH power control. For example, if the value of p0-PUCCH-Id is between 1 and 4, it can correspond to TRP index 0, and when the value of p0-PUCCH-Id is between 5 and 8, it can correspond to TRP index 1. The mapping between the range of p0-PUCCH-Id and the TRP index can change. Alternatively, the TRP index can correspond to the pathlossReferenceRS configured for PUCCH power control. Alternatively, the TRP index can correspond to the power control adjustment state index configured for PUCCH power control. The power control adjustment state index is an indicator indicating the power control state of the PUCCH resource, and can also be expressed by an expression such as a closed loop power control index and a TRP / panel specific closed loop power control index. When the twoPUCCH-PC-AdjustmentStates value of the RRC parameter is configured as twoStates, the power control adjustment state index can have one of two values (e.g., i0 or i1), where i0 can correspond to TRP index 0, and i1 can correspond to TRP index 1. The above i0 or i1 can be indicated in the form of a closedLoopIndex parameter value in the spatial relation information activated for each PUCCH / PUCCH group as shown below.

[0512]

[0513] According to the above description, among the PUCCH resources, the resource having the closedLoopIndex parameter related to the spatial relation information configured as i0 can be considered as the PUCCH resource corresponding to the TRP index 0, and the resource having the closedLoopIndex parameter configured as i1 can be considered as the PUCCH resource corresponding to the TRP index 1. Meanwhile, the power control adjustment state index can be extended to be able to configure two per TRP. Therefore, when the number of supported TRPs is at most 2, the total configurable power control adjustment state index can be extended to 4. For example, as a value of the twoPUCCH-PC-AdjustmentStates parameter, for example, FourStates can be configured, or a new parameter such as a fourPUCCH-PC-AdjustmentStates parameter can be configured. At this time, when the closedLoopIndex parameter related to the spatial relation information is configured as i0 and i1, it can be considered as the TRP index 0, and when the closedLoopIndex parameter is configured as i2, i3, or a new parameter, for example, a closedLoopIndexNew parameter is additionally configured in the spatial relation information, it can be considered as the TRP index 1. In addition, as described above, the association between the PUCCH resource and the TRP index can be established.

[0514] Alternatively, when the beams / TRPs between the overlapping PUCCHs are different, the base station can indicate a multiplexing configuration so that multiplexing is not performed. For example, when simultaneousHARQ-ACK-CSI described above is configured, the terminal can not expect a case where the PUCCH resource in which the HARQ-ACK is transmitted and the PUCCH resource in which the CSI is transmitted overlap in case 2. At this time, the inter-PUCCH beam / TRP can indicate the above-described TRP index.

[0515] In the case of the intra-slot TDMed separate HARQ-ACK, a constraint for simplifying the overlapping processing method between PUCCHs can be configured. For example, the PUCCH format of the PUCCH resource for HARQ-ACK transmission can be limited, and the format can be short PUCCH, i.e., format 0 and format 2 or some of them. It is also possible to be limited to long PUCCH or some of them only. Alternatively, in the case of the intra-slot TDMed separate HARQ-ACK, multiplexing between HARQ-ACK and CSI is not expected, or multiplexing between HARQ-ACK and CSI can be ignored, and overlapping CSI is always dropped.

[0516] Meanwhile, even when multi-slot repetition is configured, the above-described method can be similarly applied. Thus, refer to the above for details.

[0517] Alternatively, when multi-slot repetition is configured, similar to Rel-15, multiplexing between overlapping PUCCHs is not allowed, and depending on the priority of HARQ-ACK>SR>CSI, a PUCCH resource or UCI with a low priority can be dropped from overlapping slots. Thus, when multiple CSIs are multiplexed, the priority between CSIs can be applied.

[0518] Meanwhile, even when PUCCH and PUSCH overlap, multiplexing or dropping can occur. In this case, the PUCCH and PUSCH can be scheduled in the same serving cell or component carrier (CC), or can be scheduled in the same cell group or other serving cells / CCs belonging to the same PUCCH group. At this time, cases similar to Case 1 in which multiple PUCCHs for HARQ-ACK transmission and a single PUCCH overlap within the same cell group or the same PUCCH group, Case 2 in which a single PUCCH for HARQ-ACK / SR / CSI transmission and a single PUSCH overlap, or a case in which multiple PUSCHs scheduled in multiple serving cells / CCs and a single / multiple PUSCHs overlap can occur. At this time, a TRP index is configured for each CORESET in which DCI for scheduling PUSCH is transmitted in each serving cell / CC, and a TRP index can be configured for a PUCCH overlapping with these PUSCHs. When multiplexing between overlapping PUCCHs and PUSCHs, the PUCCH can be multiplexed on a PUSCH corresponding to the lowest serving cell / CC index among PUSCHs corresponding to the same value as the TRP index of the PUCCH. If there is no PUSCH corresponding to the same value as the TRP index of the corresponding PUCCH, the corresponding PUCCH or PUSCH can be dropped according to a predetermined priority. For example, when the PUCCH includes HARQ-ACK, the PUSCH is dropped, and when the PUCCH includes CSI and the PUSCH also includes CSI, the PUCCH can be dropped. If a TRP index is not configured in the PUSCH, dropping or multiplexing can be performed according to the rule configured in Rel-15.

[0519] At this time, the TRP or TRP index of the PUCCH can be obtained according to the above-described method. For example, the TRP index can be expressed as a parameter configured for PUCCH power control. As an example, the TRP index can be expressed as one of the following values or a combination thereof in the following PUCCH-PowerControl IE configured as RRC.

[0520]

[0521] In more detail, the TRP index can correspond to a p0-PUCCH-Id value configured for PUCCH power control. For example, if the value of p0-PUCCH-Id is between 1 and 4, it can correspond to TRP index 0, and when the value of p0-PUCCH-Id is between 5 and 8, it can correspond to TRP index 1. The mapping between the p0-PUCCH-Id range and the TRP index can change. Alternatively, the TRP index can correspond to a pathlossReferenceRS configured for PUCCH power control. Alternatively, the TRP index can correspond to a power control adjustment state index configured for PUCCH power control. The power control adjustment state index is an indicator indicating the power control state of the PUCCH resource, and can also be referred to as an expression such as closed loop power control index or TRP / panel specific closed loop power control index. When the value of the RRC parameter twoPUCCH-PC-AdjustmentStates is configured as twoStates, the power control adjustment state index can have one of two values (e.g., i0 or i1), where i0 can correspond to TRP index 0, and i1 can correspond to TRP index 1. The above i0 or i1 can be indicated in the form of a closedLoopIndex parameter value in the spatial relation information activated by the PUCCH / PUCCH group as shown below.

[0522]

[0523] According to the above description, among the PUCCH resources, the resource having the closedLoopIndex parameter related to the spatial relation information configured as i0 can be considered as a PUCCH resource corresponding to TRP index 0, and the resource having the closedLoopIndex parameter configured as i1 can be considered as a PUCCH resource corresponding to TRP index 1.

[0524] On the other hand, the power control adjustment state index can be extended to be able to configure two per TRP. Thus, when the number of supported TRPs is at most 2, the total configurable power control adjustment state index can be extended to at most 4. For example, as a value of the twoPUCCH-PC-AdjustmentStates parameter, for example, FourStates can be configured, or a new parameter such as the fourPUCCH-PC-AdjustmentStates parameter can be configured. At this time, when the closedLoopIndex parameter connected to the spatial relation information is configured as i0 and i1, it can be considered as TRP index 0, and when the closedLoopIndex parameter is configured as i2, i3, or a new parameter in the spatial relation information, for example, the closedLoopIndexNew parameter is additionally configured, it can be considered as TRP index 1. In addition, as described above, the association between the PUCCH resource and the TRP index can be established.

[0525] <Example 4; Method of selecting PUCCH resource for multi-PDCCH based NC-JT>

[0526] In this embodiment, when two or more PUCCH resources overlap, a method of selecting a PUCCH resource for multiplexing is proposed.

[0527] Case i. When two or more PUCCH resources overlap, when a PUCCH for grant-based HARQ-ACK transmission is included, as described above, among the PUCCH resources indicated by the PRI 9-40, 9-41 of the HARQ-ACK of the PDCCH, only the PUCCH resource (9-31) selected based on the PRI (9-41) corresponding to the PDCCH (9-11) transmitted at the last time point can be selected and transmitted. As described above, the PUCCH resource selected at this time can be selected based on the payload of the UCI to be transmitted. That is, a PUCCH resource set having a minimum payload not less than the UCI payload can be selected. Next, a PUCCH resource set indicated as a PRI in the corresponding PUCCH resource set can be selected.

[0528] If the overlapping PUCCH resources contain UCI to be transmitted to different TRPs, the dropping rule as described in Example 3 can be applied.

[0529] If the overlapping PUCCH resources contain UCI to be transmitted to the same TRP, a method of ensuring that the selected PUCCH resource can also be transmitted to the same TRP according to the payload of the multiplexed UCI is required. For this, at least one of the following methods can be considered.

[0530] Method 1. Among the PUCCH resource set, only the PUCCH resource corresponding to the target TRP of the UCI to be multiplexed is selected.

[0531] Method 2. Among the PUCCH resource set, the PUCCH resource not corresponding to the target TRP of the UCI to be multiplexed is excluded. That is, one of the PUCCH resource corresponding to the target TRP and the PUCCH resource not configured with the target TRP is selected.

[0532] Method 3. The PUCCH resource set and the PUCCH resource are selected according to the above-mentioned Rel-15-based method. At this time, it is assumed that the target TRP of the selected PUCCH resource corresponds to the target TRP of the multiplexed UCI.

[0533] At this time, the index of the target TRP of the UCI can be an upper layer index configured in the CORESET transmitting the DCI corresponding to the respective HARQ-ACK, for example, the CORESET group index or the TRP index in the case of HARQ-ACK. Meanwhile, in the case of CSI, the index of the target TRP can be the CORESET group index or the TRP index corresponding to the respective CSI report / resource configuration. Alternatively, the HARQ-ACK or the CSI can be an explicit / implicit TRP classification factor corresponding to the PUCCH resource to be transmitted, and the respective TRP classification factor can be one of the CORESET group index / TRP index / service cell index. Alternatively, the PUCCH resource group including the corresponding PUCCH resource or the group / group index corresponding to the PUCCH resource group can be used as the TRP classification factor.

[0534] Meanwhile, the target TRP corresponding to the PUCCH resource can be an explicit / implicit TRP classification factor corresponding to the corresponding PUCCH resource, and the TRP classification factor can be one of the CORESET group index / TRP index / service cell index. Alternatively, the PUCCH resource group to which the respective PUCCH resource belongs or the group / set index corresponding to the PUCCH resource set can be used as the TRP classification factor. Alternatively, the third embodiment can be represented by one or a combination of the above-mentioned PUCCH power control parameters, and the parameter can be the above-mentioned p0-PUCCH-Id value, pathlossReferenceRS, power control adjustment state index. If the power control adjustment state index is used, as described above, the TRP classification factor can be the respective TRP index from the power control adjustment state index.

[0535] When the PUCCH resource selected according to one of the above methods overlaps with other PUCCH resources, if the target TRPs of these PUCCH resources are the same, the above UCI multiplexing and PUCCH resource selection procedures can be (re)applied. If the target TRPs of these PUCCH resources are different, the dropping rule described in Embodiment 3 above can be applied.

[0536] Case ii. When two or more PUCCH resources overlap, each of the corresponding PUCCH resources is a resource for CSI transmission, or when HARQ-ACK based on configured grant and one or more CSI overlap, as described above, if multiplexing between multiple CSIs is configured as higher layer, the PUCCH resource list for CSI multiplexing is configured as higher layer, for example, all multiplexed UCI payloads in multi-CSI-PUCCH-ResourceList can be transmitted, and UCI payloads can be transmitted after selecting one resource with the lowest index. If there is no resource that can transmit all multiplexed UCI payloads in the list, select the resource with the largest index, and transmit the number of CSI reports that can be transmitted to this resource.

[0537] If the overlapping PUCCH resources contain UCI to be transmitted to different TRPs, the dropping rule as described in Example 3 can be applied.

[0538] If the overlapping PUCCH resources contain UCI to be transmitted to the same TRP, a method is needed to ensure that the selected PUCCH resource can also be transmitted to the same TRP according to the payload of the multiplexed UCI. For this purpose, at least one of the following methods can be considered.

[0539] Method 1. In multi-CSI-PUCCH-ResourceList, only PUCCH resources corresponding to the target TRP of the UCI to be multiplexed are selected.

[0540] Method 2. In multi-CSI-PUCCH-ResourceList, PUCCH resources that do not correspond to the target TRP of the UCI to be multiplexed are excluded. That is, one of the PUCCH resources corresponding to the target TRP and the PUCCH resources without the target TRP is selected.

[0541] Method 3. According to the above method based on Rel-15, PUCCH resources are selected in multi-CSI-PUCCH-ResourceList. At this time, it is assumed that the target TRP of the selected PUCCH resource corresponds to the target TRP of the multiplexed UCI.

[0542] At this time, the target TRP of UCI and the target TRP of PUCCH resource can be identified according to the above method (e.g., case i).

[0543] When the PUCCH resource selected according to one of the above methods overlaps with other PUCCH resources, if the target TRPs of the overlapping PUCCH resources are the same, the above UCI multiplexing and PUCCH resource selection procedure can be re-applied. If the target TRPs of these PUCCH resources are different, the dropping rule described in Embodiment 3 above can be applied.

[0544] Case iii. In the case of overlap between PUCCH resources and PUSCH, in Rel-15, a procedure is described in which only the UCI of PUCCH is multiplexed to PUSCH or the PUSCH is dropped after transmitting the PUSCH without PUCCH-PUSCH multiplexing. At this time, the overlapping PUCCH and PUSCH can belong to the same serving cell, or can belong to the same cell group or to another serving cell belonging to the same PUCCH group.

[0545] If the target TRPs of the overlapping PUCCH resources and PUSCH are different, a dropping rule similar to that described in (e.g., Embodiment 3) can be applied.

[0546] If the target TRPs of the overlapping PUSCH resources and PUSCH are the same, a method is required to ensure that the multiplexed PUSCH can also be designated as the same target TRP. To this end, at least one of the following methods can be considered.

[0547] Method 1. Among the PUSCH and the overlapping PUSCH, one PUSCH corresponding to the target TRP of the UCI to be multiplexed is selected according to a predetermined rule. The rule can be the same as the rule described in Embodiment 3.

[0548] Method 2. Among the PUSCH and the overlapping PUSCH, the PUCCH resource not corresponding to the target TRP of the UCI to be multiplexed is excluded. That is, one of the PUSCH corresponding to the target TRP and the PUSCH not configured with the target TRP is selected. The rule can be the same as the rule described in Embodiment 3.

[0549] Method 3. According to the Rel-15-based method, the PUSCH to be multiplexed is selected regardless of the target TRP value or target TRP configured for the PUSCH. At this time, it can be assumed that the target TRP of the selected PUSCH corresponds to the target TRP of the multiplexed UCI. At this time, the target TRP of the UCI and the target TRP of the PUCCH resource can be identified according to the above-described method (e.g., case i). The target TRP of the PUSCH can be identified by the TRP index configured in the CORESET in which the DCI scheduling the PUSCH is transmitted, or can be identified by the beam used to transmit the corresponding PUSCH, for example, the TPMI indicated by the spatial relation information of the DCI scheduling the corresponding PUSCH or the SRS connected to the SRI or designated as the SRI.

[0550] When the selected PUSCH overlaps with other PUSCH resources according to one of the above-described methods, if the target TRPs of these PUSCHs and PUCCH resources are the same, the above-described multiplexing procedure can be re-applied. If the target TRPs of these PUSCHs and PUCCH resources are different, the dropping rule described in Embodiment 3 above can be applied.

[0551] Meanwhile, in the method proposed in the disclosure, some components can be omitted and only some components can be included without deviating from the essence of the disclosure.

[0552] In addition, the method proposed in the disclosure can be executed by combining some or all of the contents included in each embodiment without deviating from the essence of the disclosure.

[0553] <Embodiment; Method of generating HARQ-ACK codebook for NC-JT repetition transmission>

[0554] NC-JT can be used to improve the reliability of PDSCH repetition transmission. The repetition transmission of NC-JT PDSCH can be performed by different time resources. For example, the PDSCH can be repeatedly transmitted for each slot on multiple slots, or the PDSCH can be repeatedly transmitted within one slot. A single PDCCH can be used to schedule the repetition transmission. The DCI of the PDCCH can indicate a list of all TRPs participating in the repetition transmission. The list of TRPs to be repeatedly transmitted can be represented in the form of a TCI state list, and the length of the TCI state list can be dynamically changed.

[0555] When the PDSCH is repeatedly transmitted over multiple slots, the time and frequency resources of the first PDSCH transmitted are indicated by the DCI, and the time and frequency resources allocated to the PDSCH repeatedly transmitted for each slot can be the same. If the number of repeated transmissions is greater than the number of TCI states, a specific pattern can be followed when the TCI states are applied to each repeated slot. For example, if the number of repeated transmissions is 4 and TCI state indexes 1 and 2 are indicated, the TCI states can be applied to each of the transmission slots according to a pattern of 1, 2, 1, 2 or a pattern of 1, 1, 2, 2. In addition, the number of repeated transmissions can be dynamically indicated through the DCI / MAC-CE. For example, the number of repeated transmissions can be indicated through the time domain resource allocation field indicated by the DCI. For example, in addition to the values indicated by the time domain resource allocation field of the DCI in the current NR (e.g., the values of K0, S, L, etc. described above in the description of the embodiment), the number of repeated transmissions can also be indicated together. Figure 8

[0556] When the PDSCH is repeatedly transmitted in one slot, the time and frequency resources of the first PDSCH transmitted in the slot can be indicated by the DCI, and the symbol length and frequency resources allocated for each PDSCH repeatedly transmitted can be the same. The PDSCH repeatedly transmitted can be configured in units of symbols. For example, as a reference to the last symbol of the first repeated transmission PDSCH, the next repeated transmission PDSCH can be transmitted after the symbols separated by the configured offset.

[0557] For convenience of description, the repeated transmission method has been described as an example of NC-JT, but the repeated transmission method is similarly applicable to single-TRP-based transmission. For example, the method in which the number of repeated transmissions is dynamically indicated through the time domain resource allocation field indicated by the DCI is similarly applicable to single-TRP-based transmission.

[0558] When the repeated transmission is configured according to the above-described embodiment, for each repeated transmission method, the HARQ-ACK codebook generation method can be different. That is, according to the repeated transmission in a slot or the repeated transmission over multiple slots, a different HARQ-ACK codebook generation method can be applied. In this embodiment, for convenience of description, the description is focused on the type 1 HARQ-ACK codebook.

[0559] ​FIG. 16A illustrates a view of a Type 1 HARQ-ACK codebook method for each PDSCH repetition transmission across multiple slots, PDSCH repetition transmission within a single slot, and no repetition transmission according to an embodiment, FIG. 16B is a view illustrating a Type 1 HARQ-ACK codebook method for each PDSCH repetition transmission across multiple slots, PDSCH repetition transmission within a single slot, and no repetition transmission according to an embodiment, and FIG. 16C illustrates a view of a Type 1 HARQ-ACK codebook method for each PDSCH repetition transmission across multiple slots, PDSCH repetition transmission within a single slot, and no repetition transmission according to an embodiment.

[0560] First, when there is no repetition transmission (16-00), a set M of reception candidate cases can be configured according to pseudo code 1 A，c , and HARQ-ACK feedback bits can be determined according to whether or not a PDSCH corresponding to each reception candidate in the set M A，c is received according to pseudo code 2. Whether or not PDSCH #1 16-10 and PDSCH #2 16-20 are received are composed of a HARQ-ACK codebook 16-40, respectively, and can be transmitted as a PUCCH resource 16-30 or a PUSCH resource.

[0561] Next, when repetition transmission in a slot is configured (16-50), a set M of reception candidate cases can be configured according to pseudo code 1 A，c , and HARQ-ACK feedback bits can be determined according to whether or not each reception candidate in the set M A，c is received according to pseudo code 2, and HARQ-ACK feedback bits are determined according to whether or not a PDSCH corresponding to each reception candidate in the set M A，c is received according to pseudo code 2. On the other hand, in pseudo code 2, HARQ-ACK feedback bits are determined according to whether or not a repeated PDSCH is received for a PDSCH transmitted for the first repetition, and the HARQ-ACK feedback bits are ignored or the corresponding PDSCH of the second and subsequent PDSCH, or in the case of a corresponding reception candidate, that is, the HARQ-ACK feedback bits can be determined as NACK at a position of the corresponding PDSCH among M A，C . In addition, when whether or not intra-slot repetition transmission is performed is configured, repetition transmission on multiple slots can not be configured at the same time, and thus, in this case, the number of transmission slots can be regarded as one slot.

[0562] Next, when the repetition transmission is configured over multiple slots (16-90), the HARQ-ACK feedback bit of the repetition transmission PDSCH 16-92 can be transmitted to the PUCCH 16-95, which is transmitted to the slot corresponding to the K1 value from the last slot in which the PDSCH is repeatedly transmitted. When the HARQ-ACK is transmitted with respect to the PUCCH (16-94) of the remaining slots according to Pseudo Code 1 and Pseudo Code 2, the HARQ-ACK feedback bit can be determined as NACK at the reception candidate corresponding to the repeatedly transmitted PDSCH, i.e., corresponding to M A，c When the position of the corresponding PDSCH among the slots is not the last slot, the HARQ-ACK feedback bit can be determined as ACK.

[0563] Figure 17 A terminal structure in a wireless communication system according to an embodiment is shown.

[0564] Reference Figure 17 The terminal can include a transceiver 17-00, a memory 17-05, and a processor 17-10. The transceiver 17-00 and the processor 17-10 of the terminal can operate according to the communication method of the terminal described above. However, the components of the terminal are not limited to the above-described examples. For example, the terminal can include more or less components than the aforementioned components. In addition, the transceiver 17-00, the memory 17-05, and the processor 17-10 can be implemented in the form of a single chip.

[0565] The transceiver 17-00 can transmit and receive signals to and from the base station. Here, the signals can include control information and data. To this end, the transceiver 17-00 can include an RF transmitter that up-converts and amplifies the frequency of the transmitted signal, and an RF receiver that amplifies the received signal and down-converts the frequency. However, this is only an embodiment of the transceiver 17-00, and the components of the transceiver 17-00 are not limited to the RF transmitter and the RF receiver.

[0566] The transceiver 17-00 can receive a signal through a wireless channel, output the signal to the processor 17-10, and transmit a signal output from the processor 17-10 through a wireless channel.

[0567] The memory 17-05 can store programs and data required for the operation of the terminal. In addition, the memory 17-05 can store control information or data included in the signal transmitted and received by the terminal. The memory 17-05 can include a storage medium such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD, or a combination of storage media. In addition, a plurality of memories 17-05 can be provided.

[0568] Further, the processor 17-10 can control a series of processes so that the terminal operates according to the above-described embodiments. For example, the processor 17-10 can control components of the terminal to simultaneously receive a plurality of PDSCHs by receiving a DCI consisting of two layers. There can be a plurality of processors 17-10, and the processor 17-10 can perform the component control operation of the terminal by executing a program stored in the memory 17-05.

[0569] Figure 18 A structure of a base station in a wireless communication system according to an embodiment is illustrated.

[0570] Reference Figure 18 The base station can include a transceiver 18-00, a memory 18-05, and a processor 18-10. The transceiver 18-00 and the processor 18-10 of the base station can operate according to the communication method of the base station. However, the components of the base station are not limited to the above-described examples. For example, the base station can include more or less components than the above-described components. Further, the transceiver 18-00, the memory 18-05, and the processor 18-10 can be implemented in the form of a single chip.

[0571] The transceiver 18-00 can transmit and receive signals to and from the terminal. Here, the signals can include control information and data. To this end, the transceiver 18-00 can be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise-amplifies a received signal and down-converts the frequency. However, this is only an embodiment of the transceiver 18-00, and the components of the transceiver 18-00 are not limited to the RF transmitter and the RF receiver.

[0572] The transceiver 18-00 can receive a signal through a wireless channel, output the signal to the processor 18-10, and transmit a signal output from the processor 18-10 through a wireless channel.

[0573] The memory 18-05 can store programs and data required for the operation of the base station. Further, the memory 18-05 can store control information or data included in a signal transmitted and received by the base station. The memory 18-05 can include a storage medium such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD, or a combination of storage media. Further, a plurality of memories 18-05 can be provided.

[0574] The processor 18-10 can control a series of processes so that the base station can operate according to the above-described embodiments. For example, the processor 18-10 can configure two-layer DCI including allocation information of a plurality of PDSCHs, and control each component of the base station to transmit them. There can be a plurality of processors 18-10, and the processor 18-10 can perform the component control operation of the base station by executing a program stored in the memory 18-05.

[0575] The method disclosed in the claims and / or the method according to the various embodiments described in the specification of the disclosure can be implemented by hardware, software, or a combination of hardware and software.

[0576] When the methods are implemented by software, a computer-readable storage medium for storing one or more programs (software modules) can be provided. The one or more programs stored in the computer-readable storage medium can be configured to be executed by one or more processors within the electronic device. At least one program can include instructions that cause the electronic device to perform the methods according to various embodiments of the disclosure defined by the appended claims and / or disclosed herein.

[0577] The programs (software modules or software) can be stored in non-volatile memory (including random access memory and flash memory, read-only memory (ROM), electrically erasable programmable memory (EEPROM), magnetic disk storage devices, compact disc-ROM (CD-ROM), digital versatile discs (DVD), or other types of optical storage devices, or magnetic tapes). Alternatively, some or all of them can form a memory that stores programs in any combination. In addition, a plurality of such memories can be included in the electronic device.

[0578] In addition, the programs can be stored in an attachable storage device, which can access the electronic device through a communication network such as the Internet, an intranet, a local area network (LAN), a wide LAN (WLAN), and a storage area network (SAN), or a combination thereof. Such a storage device can access the electronic device through an external port. In addition, a separate storage device on a communication network can access a portable electronic device.

[0579] In the above detailed embodiments of the disclosure, elements included in the disclosure are expressed in singular or plural according to the detailed embodiments presented. However, for ease of description, the singular form or the plural form is appropriately selected to the presented case, and the disclosure is not limited by the elements expressed in singular or plural. Therefore, the elements expressed in plural can also include a single element, or the elements expressed in singular can also include a plurality of elements.

[0580] The embodiments of the disclosure described and illustrated in the specification and drawings are for easy explanation of the technical content of the disclosure and to help understanding of the disclosure, and are not intended to limit the scope of the disclosure. That is, it is obvious to those skilled in the art that other modifications and changes can be made to the disclosure based on the technical spirit of the disclosure. In addition, the above-described various embodiments can be used in combination as needed. For example, Embodiments 1 and 2 of the disclosure can be partially combined to operate a base station and a terminal. In addition, although the above-described embodiments have been described through an FDD LTE system, other variations based on the technical idea of the embodiments can be implemented in other systems such as a TDD LTE, 5G, and NR system.

[0581] In the drawings describing the methods of the disclosure, the order described does not always correspond to the order of performing each method step, and the order relationship between the steps can change or the steps can be performed in parallel.

[0582] Alternatively, in the drawings describing the methods of the disclosure, some elements can be omitted and only some of them can be included without departing from the essential spirit and scope of the disclosure.

[0583] Although the disclosure has been described with various embodiments, various changes and modifications can be suggested to one skilled in the art. It is intended that the disclosure encompass such changes and modifications as fall within the scope of the appended claims.

Claims

1. A method performed by a terminal in a wireless communication system for transmitting hybrid Automatic Repeat Request (HARQ) information for multiple transmit and receive points (TRP), the method comprising: The system receives from the base station a list of physical downlink shared channel (PDSCH) time-domain resources and information about the timing of multiple HARQ feedbacks via Radio Resource Control (RRC) signaling. Each of the PDSCH time-domain resources includes a mapping type and information about the start symbol and length. Downlink control information (DCI) is received from the base station. The DCI includes a time domain resource allocation field indicating one of the PDSCH time domain resources, information indicating one of the plurality of HARQ feedback timings, and a transmission configuration indication (TCI) field, wherein the time domain resource allocation field indicates the number of repetitions and the number of repetitions indicates the number of time slots. When the TCI field indicates two TCI states, PDSCH is received from the base station in the time slot based on the number of repetitions indicated by the DCI; as well as The HARQ information of the PDSCH is sent to the base station in the first time slot corresponding to the HARQ feedback timing indicated by the DCI, starting from the last time slot in the time slot. In this case, the HARQ information received by PDSCH in the second time slot other than the first time slot is set to negative acknowledgment (NACK).

2. The method according to claim 1, wherein, Sending the HARQ information for the PDSCH also includes sending an ACK if at least one of the PDSCHs is successfully received.

3. The method according to claim 1, wherein, The number of HARQ feedback timings is configured to a maximum of 8.

4. A method performed by a base station in a wireless communication system for receiving hybrid Automatic Repeat Request (HARQ) information of multiple transmit and receive points (TRPs), the method comprising: The terminal is sent a list of physical downlink shared channel (PDSCH) time-domain resources and information about the timing of multiple HARQ feedbacks via Radio Resource Control (RRC) signaling. Each of the PDSCH time-domain resources includes a mapping type and information about the start symbol and length. Send downlink control information (DCI) to the terminal. The DCI includes a time domain resource allocation field indicating one of the PDSCH time domain resources, information indicating one of the plurality of HARQ feedback timings, and a transmission configuration indication (TCI) field, wherein the time domain resource allocation field indicates the number of repetitions, and the number of repetitions indicates the number of time slots. When the TCI field indicates two TCI states, based on the number of repetitions indicated by the DCI, a PDSCH is sent to the terminal in the time slot using the two TCI states; and The HARQ information of the PDSCH is received from the terminal in the first time slot corresponding to the HARQ feedback timing indicated by the DCI, starting from the last time slot in the time slot. In this case, the HARQ information in the second time slot other than the first time slot is set to negative acknowledgment (NACK).

5. The method according to claim 4, wherein, If the terminal successfully receives at least one of the PDSCHs, it receives an ACK.

6. The method according to claim 4, wherein, The number of HARQ feedback timings is configured to a maximum of 8.

7. A terminal in a wireless communication system, configured to transmit Hybrid Automatic Repeat Request (HARQ) information of multiple transmit and receive points (TRP), the terminal comprising: transceiver; and The controller, coupled to the transceiver, is configured to: The system receives from the base station a list of physical downlink shared channel (PDSCH) time-domain resources and information about the timing of multiple HARQ feedbacks via Radio Resource Control (RRC) signaling. Each of the PDSCH time-domain resources includes a mapping type and information about the start symbol and length. Downlink control information (DCI) is received from the base station. The DCI includes a time domain resource allocation field indicating one of the PDSCH time domain resources, information indicating one of the plurality of HARQ feedback timings, and a transmission configuration indication (TCI) field, wherein the time domain resource allocation field indicates the number of repetitions and the number of repetitions indicates the number of time slots. When the TCI field indicates two TCI states, PDSCH is received from the base station in the time slot based on the number of repetitions indicated by the DCI; as well as The HARQ information of the PDSCH is sent to the base station in the first time slot corresponding to the HARQ feedback timing indicated by the DCI, starting from the last time slot in the time slot. In this case, the HARQ information received by PDSCH in the second time slot other than the first time slot is set to negative acknowledgment (NACK).

8. The terminal according to claim 7, wherein, The controller is also configured to send an acknowledgment (ACK) upon successful receipt of at least one of the PDSCHs.

9. The terminal according to claim 7, wherein, The number of HARQ feedback timings is configured to a maximum of 8.

10. A base station in a wireless communication system, configured to receive hybrid Automatic Repeat Request (HARQ) information from multiple transmit and receive points (TRPs), the base station comprising: transceiver; and The controller is configured as follows: The terminal is sent a list of physical downlink shared channel (PDSCH) time-domain resources and information about the timing of multiple HARQ feedbacks via Radio Resource Control (RRC) signaling. Each of the PDSCH time-domain resources includes a mapping type and information about the start symbol and length. Send downlink control information (DCI) to the terminal. The DCI includes a time domain resource allocation field indicating one of the PDSCH time domain resources, information indicating one of the plurality of HARQ feedback timings, and a transmission configuration indication (TCI) field, wherein the time domain resource allocation field indicates the number of repetitions, and the number of repetitions indicates the number of time slots. When the TCI field indicates two TCI states, based on the number of repetitions indicated by the DCI, a PDSCH is sent to the terminal in the time slot using the two TCI states; and The HARQ information of the PDSCH is received from the terminal in the first time slot corresponding to the HARQ feedback timing indicated by the DCI, starting from the last time slot in the time slot. In this case, the HARQ information in the second time slot other than the first time slot is set to negative acknowledgment (NACK).

11. The base station according to claim 10, wherein, If the terminal successfully receives at least one of the PDSCHs, it receives an ACK.

12. The base station according to claim 10, wherein, The number of HARQ feedback timings is configured to a maximum of 8.

Images