CN113519194A - Apparatus and method for transmitting uplink control information in network cooperative communication

Info

Abstract

Description

Claims

CN113519194A

Publication number: CN113519194A
Application number: CN202080017701.XA
Authority: CN
Inventors: 朴珍贤; 卢勋东; 张永禄; 杨熙喆; 池衡柱
Original assignee: Samsung Electronics Co Ltd
Current assignee: Samsung Electronics Co Ltd
Priority date: 2019-08-16
Filing date: 2020-08-14
Publication date: 2021-10-19
Also published as: KR20210020740A

The present disclosure relates to communication techniques and systems for integrating 5G communication systems with IoT techniques to support higher data transmission rates behind 4G systems. The present disclosure may be applied to smart services based on 5G communication technologies and IoT related technologies (e.g., smart homes, smart buildings, smart cities, smart cars or networked cars, healthcare, digital education, retail, security and security related services, etc.).

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

Technical Field

The present disclosure relates to a wireless communication system, and more particularly, to a method and apparatus for transmitting uplink control information to a plurality of transmission points/panels/beams by a terminal for cooperative communication between the plurality of transmission points/panels/beams.

Background

In order to meet the increasing demand for wireless data services since the deployment of fourth generation (4G) communication systems, efforts have been made to develop improved fifth generation (5G) or pre-5G communication systems. Accordingly, a 5G or pre-5G communication system is also referred to as an "beyond 4G network" or a "Long-Term Evolution system after Long Term Evolution (LTE)". In order to reduce propagation loss of radio waves and increase transmission distance, beamforming technology, massive multiple-input multiple-output (MIMO) technology, full-dimensional multiple-input multiple-output (FD-MIMO) technology, array antenna technology, analog beamforming technology, and massive antenna technology are discussed in the 5G communication system, and furthermore, in the 5G communication system, a wireless backhaul technology, a mobile network technology, a cooperative communication technology, a cooperative multi-point (coordinated multi-points, CoMP) technology and receiving-side interference cancellation technology, development of system network improvement is ongoing. In the 5G system, hybrid Frequency Shift Keying (FSK) and Quadrature Amplitude Modulation (QAM) as Advanced Coding Modulation (ACM) and Sliding Window Superposition Coding (SWSC) have also been developed, as well as filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA), and Sparse Code Multiple Access (SCMA) as advanced access technologies.

The Internet, which is a human-centric network in which people generate and consume information, is now evolving towards the Internet of things (IoT), where distributed entities, such as things, exchange and process information without human intervention. Internet of everything (IoE) has emerged as a combination of IoT technology and big data processing technology through connection with a cloud server. Since IoT implementations require technical elements such as "sensing technology", "wired/wireless communication and network infrastructure", "service interface technology", and "security technology", sensor networks, machine-to-machine (M2M) communication networks, and Machine Type Communication (MTC) networks have recently been studied. Such IoT environments can provide intelligent internet technology services that create new value for human life by collecting and analyzing data generated between networked things. IoT may be applied in various fields including smart homes, smart buildings, smart cities, smart cars or networked cars, smart grids, healthcare, smart appliances, and advanced medical services through the fusion and combination of existing Information Technology (IT) with various industrial applications.

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

The above information is provided merely as background information to aid in understanding the present disclosure. No determination has been made as to whether any of the above-described matters can be applied to the present disclosure as prior art, nor has any assertion been made.

Disclosure of Invention

Technical problem

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

Problem solving scheme

In order to solve the above-mentioned problem, an embodiment according to the present disclosure includes a method performed by a terminal in a wireless communication system, the method including: receiving configuration information from a base station, the configuration information including information on at least one number of repetitions and information on at least one transmission timing of a hybrid automatic repeat request (HARQ) feedback transmission; receiving Downlink Control Information (DCI) including information indicating one of at least one transmission timing and information indicating one of at least one repetition number from a base station; receiving data from the base station in a plurality of first slots based on the number of repetitions indicated by the DCI; and transmitting HARQ feedback to the base station in a plurality of second slots determined based on the plurality of first slots, wherein the HARQ feedback is set to Negative Acknowledgement (NACK) in a slot other than a slot determined based on transmission timing indicated by the DCI among the plurality of second slots.

In order to solve the above 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 configuration information to a terminal, the configuration information including information on at least one number of repetitions and information on at least one transmission timing of a hybrid automatic repeat request (HARQ) feedback transmission; transmitting 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 repetition number; transmitting data to the terminal in a plurality of first slots based on the number of repetitions indicated by the DCI; and receiving HARQ feedback from the terminal in a plurality of second slots determined based on the plurality of first slots, wherein the HARQ feedback is set to Negative Acknowledgement (NACK) in a slot other than a slot determined based on transmission timing indicated by the DCI among the plurality of second slots.

In order to solve the above 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: receiving configuration information from a base station, the configuration information including information on at least one number of repetitions and information on at least one transmission timing of a hybrid automatic repeat request (HARQ) feedback transmission, receiving Downlink Control Information (DCI) from the base station, the DCI including information indicating one of the at least one transmission timing and information indicating one of the at least one number of repetitions, receiving data from the base station in a plurality of first slots based on the number of repetitions indicated by the DCI, and transmitting HARQ feedback to the base station in a plurality of second slots determined based on the plurality of first slots, wherein the HARQ feedback is set to Negative Acknowledgement (NACK) in a slot among the plurality of second slots except for a slot determined based on the transmission timing indicated by the DCI.

In order to solve the above problem, an embodiment according to the present disclosure includes a base station in a wireless communication system, the base station including: a transceiver; and a controller configured to: transmitting configuration information to a terminal, the configuration information including information on at least one number of repetitions and information on at least one transmission timing of a hybrid automatic repeat request (HARQ) feedback transmission, transmitting Downlink Control Information (DCI) to the terminal, the DCI including information indicating one of the at least one transmission timing and information indicating one of the at least one number of repetitions, transmitting data to the terminal in a plurality of first slots based on the number of repetitions indicated by the DCI, and receiving HARQ feedback from the terminal in a plurality of second slots determined based on the plurality of first slots, wherein the HARQ feedback is set to Negative Acknowledgement (NACK) in a slot among the plurality of second slots except for a slot determined based on the transmission timing indicated by the DCI.

Advantageous effects of the invention

According to the present disclosure, when network cooperation is used in a wireless communication system, it is possible to shorten the time required for a terminal to transmit uplink control information to each transmission point/panel/beam.

Before proceeding with the following detailed description, it may be advantageous to set forth definitions of certain words and phrases used throughout this patent document: the terms "include" and "comprise," as well as derivatives thereof, mean inclusion without limitation; the term "or" is inclusive, meaning and/or; the phrases "associated with" and "associated therewith," and derivatives thereof, may mean including, included within, interconnected with, containing, contained within, connected to or connected with, coupled to or coupled with, communicable with, cooperative with, interleaved with, juxtaposed with, proximate to, bound to or bound with, having,. property, and the like; 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 the same. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether locally or remotely.

Further, various functions described below may 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 portions thereof adapted for implementation in suitable computer readable program code. The phrase "computer readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer readable medium" includes any type of medium capable of being accessed by a computer, such as Read Only Memory (ROM), Random Access Memory (RAM), a hard disk drive, a Compact Disc (CD), a Digital Video Disc (DVD), or any other type of memory. A "non-transitory" computer-readable medium does not include a wired, wireless, optical, or other communication link that propagates transitory electrical or other signals. Non-transitory computer readable media include media that can permanently store data and media that can store data and later be rewritten, such as rewritable optical disks or erasable storage devices.

Definitions for certain words and phrases are provided throughout this patent document, those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases.

Drawings

For a more complete understanding of the present disclosure and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which like reference numbers represent like parts:

fig. 1 is a view showing a basic structure of a time-frequency domain of a mobile communication system according to an embodiment;

fig. 2 shows a view for explaining a frame, subframe and slot structure of a mobile communication system according to an embodiment;

fig. 3 illustrates an example of a configuration of a bandwidth part (BWP) in a wireless communication system according to an embodiment;

fig. 4 illustrates a view of an example of configuring a control region of a downlink control channel in a wireless communication system according to an embodiment;

fig. 5 shows a view for explaining a structure of a downlink control channel of a mobile communication system according to an embodiment;

fig. 6 is a diagram illustrating an example of frequency axis resource allocation of a Physical Downlink Shared Channel (PDSCH) in a wireless communication system according to an embodiment;

fig. 7 is a view showing an example of time axis resource allocation of a PDSCH in a wireless communication system according to an embodiment;

fig. 8 is 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;

fig. 9 illustrates a view of a case where a plurality of PUCCH resources for HARQ-ACK transmission for a PDSCH overlap when multi-slot repetition is not configured, according to an embodiment;

fig. 10 illustrates a view of a case where PUCCH resources overlap when multi-slot repetition is configured according to an embodiment;

fig. 11 shows a view of a base station and terminal radio protocol structure when performing single cell, carrier aggregation and dual connectivity according to an embodiment;

fig. 12 illustrates a diagram of an example of antenna port configurations and resource allocations for cooperative communication in a wireless communication system according to some embodiments;

fig. 13 is a diagram illustrating an example of a Downlink Control Information (DCI) configuration for cooperative communication in a wireless communication system according to an embodiment;

fig. 14A illustrates a diagram of HARQ-ACK reporting for non-coherent joint transmission (NC-JT) transmission, according to an embodiment.

Fig. 14B illustrates a diagram of HARQ-ACK reporting for non-coherent joint transmission (NC-JT) transmission, according to an embodiment.

Fig. 14C illustrates a diagram of HARQ-ACK reporting for non-coherent joint transmission (NC-JT) transmission, according to an embodiment.

Fig. 14D shows a diagram of HARQ-ACK reporting for non-coherent joint transmission (NC-JT) transmission, in accordance with an embodiment;

fig. 15A illustrates a view of a case where overlap occurs between PUCCH resources according to an embodiment;

fig. 15B illustrates a view of a method of transmitting a PUCCH when overlap occurs between PUCCH resources according to an embodiment;

fig. 16A illustrates a view of a type 1HARQ-ACK codebook method for each PDSCH repeated transmission across multiple slots, PDSCH repeated transmission within a single slot, and no-repeat transmission according to an embodiment.

Fig. 16B illustrates a view of a type 1HARQ-ACK codebook method for each PDSCH repeated transmission across multiple slots, PDSCH repeated transmission within a single slot, and no-repeat transmission according to an embodiment.

Fig. 16C shows a view of a type 1HARQ-ACK codebook method for each PDSCH repeated transmission across multiple slots, PDSCH repeated transmission within a single slot, and no repeated transmission, in accordance with an embodiment;

fig. 17 shows a structure of a terminal in a wireless communication system according to an embodiment; and

fig. 18 shows a structure of a base station in a wireless communication system according to an embodiment.

Detailed Description

Fig. 1 through 18, discussed below, and the various embodiments used to describe the principles of the present disclosure in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the disclosure. Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably arranged system or device.

Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.

In describing the 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. Such omission of unnecessary description is intended to prevent the main ideas of the present disclosure from being obscured, and to more clearly convey the main ideas.

For the same reason, in the drawings, some elements may be exaggerated, omitted, or schematically shown. Further, 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.

Advantages and features of the present disclosure and the manner of attaining them will become apparent by reference to the following detailed description of embodiments when taken in conjunction with the accompanying drawings. However, the present disclosure is not limited to the embodiments set forth below, but may be implemented in various different forms. The following examples are provided solely for the purpose of complete disclosure and to inform those skilled in the art of the scope of the disclosure, and the disclosure is to be limited only by the scope of the appended claims. Throughout the specification, the same or similar reference numerals denote the same or similar elements.

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 may 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 may 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 instruction means that implement the function specified in the flowchart block or blocks. The computer program instructions may 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.

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

As used herein, a "unit" refers to a software element or a hardware element that performs a predetermined function, such as a Field Programmable Gate Array (FPGA) or an Application Specific Integrated Circuit (ASIC). However, the "unit" does not always have a meaning limited to only software or hardware. A "unit" may be configured to be stored in an addressable storage medium or to execute one or more processors. Thus, a "unit" includes, for example, software elements, object-oriented software elements, class elements or task elements, procedures, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and parameters. The elements and functions provided by a "unit" may be combined into a smaller number of elements or "units" or divided into a larger number of elements or "units". Further, the elements and "units" may alternatively be implemented as one or more CPUs within a rendering device or secure multimedia card. Furthermore, a "unit" in an embodiment may include one or more processors.

Hereinafter, the operational 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 may 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 may be different according to a user, a user's intention, or a habit. Therefore, the definition of the terms should be based on the contents of the entire specification. Hereinafter, the base station is a main body that performs resource allocation of the terminal, and may be at least one of a eNode 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. A terminal may include a User Equipment (UE), a Mobile Station (MS), a cellular phone, a smart phone, a computer, or a multimedia system capable of performing communication functions. Of course, it is not limited to the above example. Hereinafter, the present disclosure describes a technique for a terminal to receive broadcast information from a base station in a wireless communication system. The present disclosure relates to communication techniques and systems for integrating fifth generation (5G) communication systems with internet of things (IoT) technology to support higher data transfer rates after fourth generation (4G) systems. The present disclosure may be applied to smart services based on 5G communication technologies and IoT related technologies (e.g., smart homes, smart buildings, smart cities, smart cars or networked cars, healthcare, digital education, retail, security and security related services, etc.).

In the following description, terms related to broadcast information, terms related to control information, terms associated with communication coverage, terms related to state changes (e.g., events), terms related to network entities, terms related to messages, terms related to device elements, and the like 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 an equivalent technical meaning may be used.

In the following description, for convenience of description, the present disclosure uses terms and names defined in the third generation partnership project long term evolution (3GPP LTE) standard. However, the present disclosure is not limited to these terms and names, and may be applied to systems conforming to other standards in the same manner.

Wireless communication systems have evolved to broadband wireless communication systems that provide high-speed and high-quality packet data services using communication standards such as 3GPP high-speed packet access (HSPA), Long Term Evolution (LTE), or evolved universal terrestrial radio access (E-UTRA), LTE-advanced (LTE-a), LTE-Pro, 3GPP2 high-rate packet data (HRPD), ultra-mobile broadband (UMB), and IEEE 802.16E, etc., instead of providing the original voice-based services.

As a representative example of a broadband wireless communication system, in an LTE system, a Downlink (DL) employs an Orthogonal Frequency Division Multiplexing (OFDM) scheme, and an Uplink (UL) employs 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 a base station transmits data or control signals to a 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 carried by each user are not overlapped, i.e., orthogonality is established.

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

According to some embodiments, the eMBBs are intended to provide higher data transmission rates than existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, from the perspective of one base station, the eMBB should be able to provide a maximum data rate of 20Gbps in the downlink and 10Gbps in the uplink. At the same time, an increased actual perceived data rate of the terminal should be provided. To meet this demand, improvements in transmission/reception techniques, including more advanced multiple-input multiple-output (MIMO) transmission techniques, are required. Further, the data transmission speed required for the 5G communication system can be satisfied by using a wider bandwidth than 20MHz in a frequency band of 3-6GHz or higher, instead of the 2GHz band currently used by LTE.

Meanwhile, mtc is being considered to support application services such as internet of things (IoT) in a 5G communication system. To efficiently provide the internet of things, mtc may be required to support large-scale terminals within an access cell, improve the coverage of the terminal, improve battery time, and reduce the cost of the terminal. The internet of things should be able to support a large number of terminals (e.g., 1,000,000 terminals per square kilometer) in one cell because the cell is connected to various sensors and various devices to provide communication functions. Furthermore, due to the nature of the service, mtc-enabled terminals are likely to be located in shadow areas that cannot be covered by a cell, such as the basement of a building, and therefore may require a wider coverage than other services provided by a 5G communication system. Since the mtc-enabled terminal should be configured with a low-cost terminal and it is difficult to frequently replace a battery of the terminal, a very long battery life may be required.

Finally, URLLC, which is a cellular-based wireless communication service for specific purposes (critical tasks), is a service for robot or mechanical equipment remote control, industrial automation, drone, remote health control, emergency notification, etc., and should provide communication providing ultra-low latency and ultra-high reliability. For example, a URLLC capable service should meet an air interface delay of less than 0.5 milliseconds, while requiring a packet error rate of 10-5 or less. Therefore, for services supporting URLLC, the 5G system needs to provide a smaller Transmission Time Interval (TTI) than other services, and at the same time, the design requires wider resources to be allocated in the frequency band. However, the above mtc, URLLC, and EmB are only examples of different service types, and the service types to which the present disclosure is applied are not limited to the above examples.

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

Further, hereinafter, the embodiments will be described as examples of LTE, LTE-a, LTE Pro, or NR systems, but the embodiments may be applied to other communication systems having similar technical backgrounds or channel types. Furthermore, as will be appreciated by those skilled in the art, embodiments may be applied to other communication systems with some modification within the scope that does not significantly depart from the scope of the present disclosure.

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

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

Hereinafter, the frame structure of the 5G system will be described in more detail with reference to the accompanying drawings.

Fig. 1 is a view showing a basic structure of a time-frequency domain of a mobile communication system according to an embodiment.

Referring to fig. 1, the horizontal axis represents the time domain, and the vertical axis represents the frequency domain. The basic unit in the time and frequency domains 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 (e.g., 12) consecutive REs can constitute one Resource Block (RB) 1-04. In an embodiment, multiple OFDM symbols may constitute one subframe 1-10.

Fig. 2 shows a view for explaining a frame, subframe and slot structure of a next generation mobile communication system according to an embodiment.

Referring to fig. 2, one frame 2-00 may be composed of one or more subframes 2-01, and one subframe may be composed of one or more slots 2-02. As an example, one frame 2-00 may be defined as 10 ms. One subframe 2-01 may be defined as 1ms, and in this case, one frame 2-00 may be composed of a total of 10 subframes 2-01. One slot 2-02, 2-03 may be defined by 14 OFDM symbols (i.e., the number of symbols per slot)

). One subframe 2-01 may be composed of one or more slots 2-02, 2-03, and the number of slots 2-02, 2-03 of each subframe 2-01 may be different according to the configuration values μ 2-04, 2-05 of the subcarrier spacing. In the example of fig. 2, the case where the subcarrier spacing is configured is μ ═ 0(2-04) and μ ═ 1 (2-05). One subframe 2-01 may consist of one slot 2-02 when μ ═ 0(2-04), and one subframe 2-01 may consist of two slots 2-03 when μ ═ 1 (2-05). That is, the number of slots per subframe

May vary according to the configuration value mu of the subcarrier spacing, and thus the number of slots per frame

May vary. Configuring mu according to each subcarrier spacing

And

can be as follows [ Table 1]And (4) defining.

[ Table 1]

In NR, one Component Carrier (CC) or serving cell may configure up to 250 or more RBs. Therefore, when a terminal always receives the entire serving cell bandwidth (LTE), such as LTE, power consumption of the terminal may be very large, and to solve this problem, the base station may configure one or more bandwidth parts (BWPs) for the terminal in order to support the terminal to change a reception area in a cell. In the NR, the base station may configure an 'initial BWP', which is a bandwidth of CORESET #0 (or common search space, CSS), for the terminal through a Master Information Block (MIB). Then, the base station may configure an initial BWP (first BWP) of the terminal through Radio Resource Control (RRC) signaling, and may notify the terminal of at least one BWP configuration information, which may be indicated by Downlink Control Information (DCI) in the future. Thereafter, the base station may inform the BWP identity through DCI to indicate which band the terminal will use. If the terminal fails to receive DCI from the currently allocated BWP for a certain time or more, the terminal may return to the 'default BWP' and attempt to receive DCI.

Fig. 3 illustrates a view of an example of a configuration of a bandwidth part (BWP) in a wireless communication system according to an embodiment.

Referring to fig. 3, fig. 3 shows an example in which a terminal bandwidth (3-00) is configured to have two bandwidth parts, i.e., a bandwidth part #1(3-05) and a bandwidth part #2 (3-10). The base station may configure one or more bandwidth parts for the terminal and may configure information as shown in [ table 2] below for each bandwidth part.

[ Table 2]

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

According to an embodiment, a terminal before a Radio Resource Control (RRC) connection may receive an initial bandwidth part (initial BWP) from a base station through a Master Information Block (MIB) for initial access. More specifically, in order to receive system information (remaining system information; may correspond to RMSI or System Information Block (SIB)1) required for initial access through the MIB in an initial access step, the terminal may receive configuration information for a control region (control resource set, CORSET) and a search space through which the PDCCH can be transmitted. The control region and the search space configured by the MIB may be respectively regarded as an Identifier (ID) 0.

The base station may notify the terminal of configuration information such as frequency allocation information, time allocation information, and a parameter set of the control region #0 through the MIB. Further, the base station may notify the terminal of configuration information of the monitoring period and timing of the control region #0, i.e., configuration information of the search space #0, through the MIB. The terminal may regard the frequency domain configured to the control region #0 obtained from the MIB as an initial bandwidth part for initial access. At this time, an Identifier (ID) of the initial bandwidth part may be regarded as 0.

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

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

As another example, to support different sets of parameters, the base station may configure multiple bandwidth parts for the terminal. For example, in order to support transmission and reception of data to and from any terminal using a subcarrier spacing of 15kHz and a subcarrier spacing of 30kHz, the two bandwidth parts may be configured to use subcarrier spacings of 15kHz and 30kHz, respectively. The different bandwidth parts may be Frequency Division Multiplexing (FDM), and when data is transmitted/received at a specific subcarrier interval, the bandwidth parts configured at the corresponding subcarrier interval may be activated.

As another example, to reduce power consumption of the terminal, the base station may configure the terminal with bandwidth parts having different bandwidth sizes. For example, if a terminal supports a very large bandwidth, for example, a bandwidth of 100MHz, and always transmits/receives data with the corresponding bandwidth, the large bandwidth may cause very large power consumption. In particular, in the absence of traffic, it is very inefficient in terms of power consumption for the terminal to perform unnecessary monitoring of the downlink control channel for a large bandwidth of 100 MHz. Therefore, in order to reduce the power consumption of the terminal, the base station may configure the terminal with a relatively small bandwidth portion, for example, a 20MHz bandwidth portion. In the case of no traffic, the terminal may perform a monitoring operation in the 20MHz bandwidth part, and when data occurs, may transmit/receive data using the 100MHz bandwidth part according to an instruction of the base station.

In the method of configuring the above bandwidth part, the terminal before the RRC connection may receive configuration information of the initial bandwidth part through the master information block in the initial access step. More specifically, the terminal may receive a control region (control resource set (CORESET)) of a downlink control channel through which Downlink Control Information (DCI) of a scheduling System Information Block (SIB) may be transmitted, from a MIB of a Physical Broadcast Channel (PBCH). The bandwidth of the control region configured as the MIB may be regarded as an initial bandwidth part, and the terminal may receive PDSCH through the configured initial bandwidth part, through which the SIB is transmitted. The initial bandwidth portion may be used for Other System Information (OSI), paging, and random access, in addition to the purpose of receiving the SIB. Hereinafter, a Synchronization Signal (SS)/PBCH block of a next generation mobile communication system (5G or NR system) will be described.

The SS/PBCH block may represent a physical layer channel block consisting of a primary SS (PSS), a Secondary SS (SSs), and a PBCH. More specifically, the SS/PBCH block may be defined as follows.

-PSS: a signal that is a downlink time/frequency synchronization reference, and may provide some information of the cell ID.

-SSS: the SSS is a reference for downlink time/frequency synchronization and may provide remaining cell ID information not provided by the PSS. Additionally, SSS may be used as a reference signal for PBCH demodulation.

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

-SS/PBCH block: the SS/PBCH block may be composed of a combination of PSS, SSs, and PBCH. One or more SS/PBCH blocks may be transmitted within 5 milliseconds, and each SS/PBCH block transmitted may be distinguished by an index.

The terminal may detect the PSS and SSS at the initial access phase and decode the PBCH. The terminal may acquire the MIB from the PBCH and may 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 may perform monitoring on the control region # 0. The terminal may receive system information as downlink control information transmitted from the control region # 0. The terminal may obtain Random Access Channel (RACH) related configuration information required for initial access from the received system information. The terminal may transmit a Physical RACH (PRACH) to the base station in consideration of the selected SS/PBCH index, and the base station receiving the PRACH may acquire information on 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 a control region #0 corresponding to (or associated with) the SS/PBCH block selected by the terminal.

Hereinafter, downlink control information (hereinafter, referred to as 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 Physical Uplink Shared Channel (PUSCH)) or scheduling information of downlink data (or Physical Downlink Shared Channel (PDSCH)) may be transmitted from a base station to a terminal through DCI. The terminal may monitor a fallback DCI format and a non-fallback DCI format for the PUSCH or PDSCH. The fallback DCI format may consist of a predetermined fixed field between the base station and the terminal, and the non-fallback DCI format may include a configurable field.

Through the channel coding and modulation process, DCI may be transmitted through a Physical Downlink Control Channel (PDCCH). A Cyclic Redundancy Check (CRC) may be attached to the DCI message payload, and the CRC may be scrambled with a Radio Network Temporary Identifier (RNTI) corresponding to the terminal identity. Different RNTIs may be used to scramble a CRC appended to the payload of the DCI message according to the purpose of the DCI message, such as terminal-specific (UE-specific) data transmission, power control command, or random access response. That is, the RNTI is not explicitly transmitted, but may be included in the CRC calculation process and transmitted. When receiving a DCI message transmitted on a PDCCH, the terminal may identify the CRC using the allocated RNTI. If the CRC recognition result is correct, the terminal can know that a corresponding message has been transmitted to the terminal.

For example, DCI scheduling PDSCH for System Information (SI) may be scrambled with SI-RNTI. DCI scheduling PDSCH for Random Access Response (RAR) messages may be scrambled with RA-RNTI. The DCI that schedules the PDSCH for a paging message may be scrambled with the P-RNTI. A DCI notifying a Slot Format Indicator (SFI) may be scrambled with an SFI-RNTI. A DCI informing a Transmit Power Control (TPC) may be scrambled with a TPC-RNTI. The DCI used to schedule the terminal-specific PDSCH or PUSCH may be scrambled with a cell RNTI (C-RNTI).

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

[ Table 3]

DCI format 0_1 may be used as a non-fallback DCI scheduling PUSCH, and CRC may be scrambled with C-RNTI. In an embodiment, the DCI format 0_1 in which CRC is scrambled with C-RNTI may include information as shown in [ table 4] below.

[ Table 4]

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

[ Table 5]

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

[ Table 6]

Fig. 4 is a view illustrating an example of configuring a control region of a downlink control channel in a next generation mobile communication system according to an embodiment. That is, fig. 4 is a view illustrating an embodiment of transmitting a control region (control resource set (CORESET)) of a downlink control channel in a 5G wireless communication system according to the embodiment.

Referring to fig. 4, fig. 4 shows a case in which two control regions (control region # 14-01 and control region # 24-02) are configured within a bandwidth part (UE bandwidth part) 4-10 of a terminal and in one slot 4-20 on a frequency axis and in one slot 4-20 on a time axis. The control regions 4-01 and 4-02 may be configured as specific frequency resources 4-03 within the entire terminal bandwidth portion 4-10 on the frequency axis. The control regions 4-01 and 4-02 may be configured as one or more OFDM symbols on a time axis, which may be defined as a control resource set duration (4-04). Referring to fig. 4, a control region #1(4-01) may be configured with a control resource set duration of 2 symbols, and a control region #2(4-02) may be configured with a control resource set duration of 1 symbol.

The control region in the above-described next generation mobile communication system (5G or NR system) may be configured by a base station performing higher layer signaling (e.g., system information, Master Information Block (MIB), Radio Resource Control (RRC) signaling) on a terminal. Configuring the control region to the 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 may include information as shown in [ table 7] below.

[ Table 7]

In [ table 7], the TCI-statesdcch (hereinafter, referred to as "TCI state") configuration information may 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 demodulation reference signals (DMRSs) transmitted in a corresponding control region. Further, the tci-statesdcch configuration information may include information about what the QCL relationship is. For example, the configuration of the TCI state may include information as shown below [ Table 8 ].

[ Table 8]

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

-QCL typeA: doppler shift, doppler spread, mean delay, delay spread.

-QCL typeB: doppler shift, doppler spread.

-QCL typeC: doppler shift, average delay.

-QCL type d: the spatial Rx parameters.

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

Fig. 5 shows a view for explaining a structure of a downlink control channel of a next generation mobile communication system according to an embodiment. That is, fig. 5 is a view showing an example of a basic unit configuring time and frequency resources of a downlink control channel that can be used in 5G according to an embodiment.

Referring to fig. 5, a basic unit of time and frequency resources constituting a control channel may be defined as a Resource Element Group (REG) 5-03. REG 5-03 may be defined as 1 OFDM symbol 5-01 on the time axis, 1 Physical Resource Block (PRB) 5-02 on the frequency axis, i.e., 12 subcarriers. The base station may configure the downlink control channel allocation unit by connecting REG 5-03.

As shown in fig. 5, when a basic unit to which a downlink control channel is allocated is referred to as a Control Channel Element (CCE) 5-04 in 5G, 1 CCE5-04 may consist of a plurality of REGs 5-03. For example, REG 5-03 shown in FIG. 5 may consist of 12 REs, and if 1 CCE5-04 consists of 6 REGs 5-03, then 1 CCE5-04 may consist of 72 REs. When configuring the downlink control region, the corresponding region may be composed of a plurality of CCEs 5-04, and a specific downlink control channel may 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 divided into a plurality of numbers, and the numbers of the CCEs 5-04 may be allocated according to a logical mapping method.

The basic element of the downlink control channel shown in fig. 5, REG 5-03, may include DCI mapped REs to which DCI is mapped and a region to which reference signals DMRS 5-05, which are reference signals for decoding, are mapped. As shown in fig. 5, three DMRSs 5-05 may be transmitted in 1 REG 5-03. The number of CCEs required to transmit the PDCCH may be 1, 2, 4, 8, or 16 according to an Aggregation Level (AL), and the number of different CCEs may be used to implement link adaptation of a downlink control channel. For example, when AL ═ L, one downlink control channel may be transmitted over L CCEs.

The terminal should detect the signal without knowing information about the downlink control channel and can define a search space indicating a set of CCEs for blind decoding. 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 that constitute bundles of 1, 2, 4, 8, and 16 CCEs, a terminal may have multiple search spaces. A set of search spaces may be defined as a collection of search spaces at all configured aggregation levels.

The search space may 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 may check a common search space of a PDCCH in order to receive control information common to cells, such as dynamic scheduling of system information or paging messages.

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

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

[ Table 9]

Based on the configuration information, the base station may configure one or more search space sets for the terminal. According to an embodiment, a base station may configure search space set 1 and search space set 2, configure a 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.

Depending on the configuration information, a set of one or more search spaces may exist in a common search space or a terminal-specific search space. For example, the search space set #1 and the search space set #2 may be configured as a common search space, and the search space set #3 and the search space set #4 may be configured as a terminal-specific search space.

In the common search space, the following combination of DCI format and RNTI may be monitored. Of course, the following examples are not limited.

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

DCI format 2_0 with CRC scrambled with SFI-RNTI

DCI format 2_1 with CRC scrambled with INT-RNTI

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

DCI format 2_3 with CRC scrambled with TPC-SRS-RNTI

In the terminal-specific search space, the following combination of DCI format and RNTI may be monitored. Of course, the following examples are not limited.

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

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

The specified RNTIs may follow the following definitions and uses.

C-RNTI (cell RNTI): terminal-specific PDSCH scheduling purposes.

TC-RNTI (temporary cell RNTI): terminal-specific PDSCH scheduling purposes.

CS-RNTI (configured scheduling RNTI): semi-statically configured terminal-specific PDSCH scheduling purposes.

RA-RNTI (random access RNTI): PDSCH scheduling in a random access phase.

P-RNTI (paging RNTI): PDSCH scheduling for paging transmissions.

SI-RNTI (system information RNTI): PDSCH scheduling for transmitting system information.

INT-RNTI (interrupt RNTI): for informing whether or not the PDSCH is punctured (puncturing).

TPC-PUSCH-RNTI (transmission power control for PUSCH RNTI): indicating the purpose of the power control command for the PUSCH.

TPC-PUCCH-RNTI (transmission power control for PUCCH RNTI): indicating the purpose of the power control command for the PUCCH.

TPC-SRS-RNTI (transmission power control for SRS RNTI): indicating the purpose of the power control command for the SRS.

In an embodiment, the DCI format described above may be defined as the following [ table 10 ].

[ Table 10]

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

When configuring a plurality of search space sets for a terminal, in order to determine a set of search spaces that the terminal should monitor, the following condition may be considered.

[ Condition 1: limiting the maximum number of PDCCH candidates

The number of PDCCH candidates that can be monitored per slot may not exceed M^μ。M^μCan be defined as a configuration of 15.2^μThe maximum number of PDCCH candidate sets per slot in a cell of kHz subcarrier spacing may be defined as shown in table 11 below.

[ Condition 2: limitation of maximum number of CCEs ]

The number of CCEs constituting the entire search space per slot (here, the entire search space may mean the entire CCE set corresponding to the joint region of the plurality of search space sets) may not exceed C^μ。C^μCan be defined as a configuration of 15.2^μThe maximum number of CCEs per slot in a cell of kHz subcarrier spacing, and can be defined as follows [ Table 12]]As shown.

[ Table 12]

For convenience of explanation, a case where both of the condition 1 and the condition 2 are satisfied at a specific time point is defined as "condition a". Therefore, not satisfying the condition a may mean that at least one of the condition 1 and the condition 2 is not satisfied.

Depending on the configuration of the search space set of base stations, condition a may not be satisfied at a particular time. If condition a is not satisfied at a particular time, the terminal may select and monitor only a subset of the set of search spaces configured to satisfy condition a at that time, and the base station may transmit a PDCCH to the selected search space set.

According to an embodiment, the following method may be used as a method of selecting some search spaces from a set of search spaces of all sets.

[ method 1]

If the condition a for the PDCCH is not satisfied at a specific time (slot), the terminal (or the base station) may preferentially select a set of search spaces of which search space types are configured as a common search space, rather than a set of search spaces configured as a terminal-specific search space, from among sets of search spaces existing at corresponding time points.

When all search space sets configured as a common search space are selected (i.e., when the condition a is satisfied even after all search spaces are selected as a common search space), the terminal (or the base station) may select a set of search spaces configured as terminal-specific search spaces. At this time, when there are a plurality of search space sets configured as terminal-specific search spaces, a search space set having a low search space set index may have a higher priority. In consideration of the priority, the terminal or the base station may select a terminal-specific search space set within a range satisfying the condition a.

Next, a time and frequency resource allocation method for data transmission in NR is described.

In NR, in addition to frequency axis resource candidate allocation indicated by BWP, frequency domain resource allocation (FD-RA) in detail below may be provided.

Fig. 6 is a diagram illustrating an example of PDSCH frequency axis resource allocation in a wireless communication system according to an embodiment.

Specifically, fig. 6 shows three types of frequency axis resource allocation methods of type 0(6-00), type 1(6-05), and dynamic switching (6-10) that can be configured by an upper layer in NR.

Referring to fig. 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 a corresponding terminal has a bitmap consisting of NRBG bits. The conditions 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 ]. The data is transmitted to the RBG indicated by 1.

[ Table 13]

If the terminal is configured to use only resource types 16-05 through upper layer signaling, some DCIs for allocating PDSCH to the corresponding terminal have a resource pattern of

And frequency axis resource allocation information consisting of bits. The conditions for this case will be explained again later. By this, the base station can configure the start VRB 6-20 and length 6-25 of the frequency axis resources allocated continuously therefrom.

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

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

The base station may 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 up to 16 entries of maxNrofDL-Allocations may be configured for the PDSCH, and a table consisting of up to 16 entries of maxNrofUL-Allocations may be configured for the PUSCH. In the embodiment, in the time domain resource allocation information, PDCCH-to-PDSCH (PDCCH-to-PDSCH) slot timing (corresponding to a time interval in units of slots between a time when a PDCCH is received and a time when 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 when a PDCCH is received and a time when a received PDCCH-scheduled PUSCH is transmitted, denoted by K2), information on a position and a length of a starting symbol for which a PDSCH or a PUSCH is scheduled in a slot, a mapping type of the PDSCH or the PUSCH, and the like may be included. For example, information such as [ table 14] or [ table 15] below may be notified from the base station to the terminal.

[ Table 14]

[ Table 15]

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

Fig. 7 is a view showing an example of time axis resource allocation of a PDSCH in a wireless communication system according to an embodiment.

Referring to fig. 7, a base station may indicate subcarrier spacing (SCS) of a data channel and a control channel using an upper configuration (μ;)_PDSCH，μ_PDCCH) Scheduling offset (K)₀) A value and a time axis position configuration of a PDSCH resource according to an OFDM symbol start position (7-00) and a length (7-05) in one slot dynamically indicated by DCI.

Fig. 8 is a view illustrating 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.

Referring to fig. 8, it can be seen that when the subcarrier intervals of the data channel and the control channel are the same (8-00, μ)_PDSCH＝μ_PDCCH) The slot numbers used for data and control are the same, so that K is offset according to the predetermined slots in the base station and the terminal₀A scheduling offset occurs for 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 are different (8-05, μ @)_PDSCH≠μ_PDCCH) The slot numbers used for data and control are different so that K is offset according to the predetermined slots in the base station and the terminal₀Based on the subcarrier spacing of the PDCCH, a scheduling offset occurs for the base station and the terminal.

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

The base station may transmit a terminal capability query message requesting a capability report to the terminal in a connected state. In this message, the base station may include a request for terminal capabilities for each RAT type. The request for each RAT type may include the requested band information. In addition, the terminal capability query message may request a plurality of RRC types from one RRC message container, or the terminal capability query message including a request for each RRC type may be transmitted to the terminal a plurality of times. That is, the terminal capability query may be repeated a plurality of times, and the terminal may report the number of times by configuring a corresponding terminal capability information message. In a next generation mobile communication system, a terminal capability request can be made for MR-DC including NR, LTE, and E-UTRA new radio dual connectivity (EN-DC). Further, the terminal capability inquiry message is generally initially transmitted after the terminal is connected to the base station, but may be requested under any condition when needed by the base station.

In step, the terminal receiving the terminal capability report request from the base station may configure the terminal capability according to the RAT type and the band information requested from the base station. A method for configuring a terminal capability by a terminal in an NR system is as follows.

1. If the terminal is provided with a list of LTE and/or NR bands in a terminal capability request from a base station, the terminal may configure band combining for EN-DC and NR independent networking (SA). That is, the candidate lists for EN-DC and NR SA may be configured based on the frequency band requested by FreqBandList to the base station. Further, the priority of the band has a priority in the order described in FreqBandList.

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

3. Thereafter, the terminal may remove the fallback BC from the BC candidate list configured in the above step. Here, the backoff BC corresponds to a case where a band corresponding to at least one SCell is removed from a superset (super set) BC, and may be omitted because the superset BC may already cover the backoff BC. This procedure is also applicable to Multi-RAT (Multi-RAT) dual connectivity (MR-DC), that is, also to LTE bands. The BC remaining after this stage is the final "candidate BC list".

4. The terminal may select the BC to be reported by selecting the BC corresponding to the requested RAT type in the final "candidate BC list". In this step, the terminal may configure supportedbandcombinationlists in a predetermined order. That is, the terminal may configure the BC and terminal capabilities to report in a predetermined rat-Type order (nr- > eutra-nr- > eutra). In addition, featurecombining of the provisioned bandcombinationlist may be configured, and a list of "candidate feature set combinations" may be constructed from the list of candidate BCs from which the list of fallback BCs (that include the same or lower level capabilities) is removed. "candidate feature set combination" includes feature set combinations of NR and EUTRA-NR BC, and can be obtained from feature set combinations of UE-NR-Capabilities and UE-MRDC-Capabilities containers.

5. Furthermore, if the requested rat type is eutra-NR, then featurescombinations may be included in two containers, UE-MRDC-Capabilities and UE-NR-Capabilities. However, the feature set of the New Radio (NR) may include only UE-NR-Capabilities.

After configuring the terminal capability, the terminal may 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.

In NR, a terminal may transmit Uplink Control Information (UCI) to a base station through a Physical Uplink Control Channel (PUCCH). The control information may include at least one of HARQ-ACK indicating whether demodulation/deciphering of a transport block received through the PDSCH by the terminal is successful, a scheduling request for requesting PUSCH resources 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.

PUCCH resources may be mainly divided into a long PUCCH and a short PUCCH according to the allocated symbol length. In NR, a long PUCCH has a length of 4 or more symbols in a slot, and a short PUCCH has a length of 2 or less symbols in a slot.

Describing the long PUCCH in more detail, the long PUCCH may be used for the purpose of improving uplink cell coverage, and thus may be transmitted in a DFT-S-OFDM method, which is short carrier transmission 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 through Pre-DFT OCC support of the IFFT front end.

First, PUCCH format 1 is a long PUCCH format based on DFT-S-OFDM that can support 2-bit control information at most and uses frequency resources of 1 RB. The control information may consist of HARQ-ACK, SR, or a combination thereof. In PUCCH format 1, an OFDM symbol including a demodulation reference signal (DMRS) as a demodulation reference signal (or reference signal) and an OFDM symbol including UCI are repeatedly configured.

For example, when the number of transmission symbols of the PUCCH format 1 is 8 symbols, a first start symbol of the 8 symbols is sequentially composed of a DMRS symbol, a UCI symbol, a DMRS symbol, and a UCI symbol. A DMRS symbol is spread in a sequence corresponding to a 1RB length on the frequency axis within 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 performing IFFT.

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 and multiplying the generated d (0) by a sequence corresponding to 1RB length on the frequency axis, spreading the scrambled sequence on the time axis using an orthogonal code (or an orthogonal sequence or a spreading code, w _ i (m)), and transmitting the sequence after performing IFFT.

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

W _ i (m) is as follows when the length of the spreading code (NSF) is given

Determined as given, and given as table 16 below. i denotes the index of the spreading code itself and m denotes the index of the element of the spreading code. Here, [ Table 16 ]]Zhonglong (Chinese character)]The number in (b) represents phi (m), and for example, when the length of the spreading code is 2 and the index i of the configured spreading code is 0, the spreading code w _ i (m) becomes

So that w _ i (m) is [ 11]。

[ Table 16 ]]Spreading code for PUCCH format 1

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 may be configured by an upper layer. The control information may consist of HARQ-ACK, SR, CSI, or a combination thereof. The DMRS symbol positions in PUCCH format 3 are as shown in [ table 17] below depending on whether frequency hopping and additional DMRS symbols in a slot are configured.

[ Table 17]

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

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 frequency resources of 1 RB. The control information may consist of HARQ-ACK, SR, CSI, or a combination thereof. PUCCH format 4 is different from PUCCH format 3 in that PUCCH format 4 can multiplex terminals of multiple PUCCH formats 4 within one RB. By applying Pre-DFT OCC to the control information in the IFFT front end, multiple PUCCH format 4 UEs can be multiplexed. However, the number of control information symbols that can be transmitted by one terminal is reduced according to the number of terminals to be multiplexed. The number of reusable terminals, i.e., the number of different OCCs that can be used, may be 2 or 4, and the number of OCCs to be applied and the OCC index may be configured by an upper layer.

Next, a short PUCCH will be described. The short PUCCH may be transmitted in a downlink center slot (downlink center slot) and an uplink center slot (uplink center slot), and is typically transmitted in the last or following OFDM symbol of the slot (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 may be transmitted at any position in the slot. Also, the short PUCCH may be transmitted using one OFDM symbol or two OFDM symbols. In case of good uplink cell coverage and transmission in CP-OFDM, a short PUCCH may be used to shorten the delay time compared to a long PUCCH.

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, PUCCH format 0 is a short PUCCH format capable of supporting at most 2-bit control information, and uses frequency resources of 1 RB. The control information may consist of HARQ-ACK, SR, or a combination thereof. The PUCCH format 0 does not transmit the DMRS and has a structure in which only sequences mapped to 12 subcarriers on the frequency axis within one OFDM symbol are transmitted. The terminal generates a sequence based on a packet hopping or a sequence hopping set and a set ID received from the base station as a higher layer signal, cyclic-shifts the generated sequence to a final Cyclic Shift (CS) value obtained by adding another CS value according to whether an indicated initial CS value is ACK or NACK, then maps the sequence and transmits the mapped sequence to 12 subcarriers.

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

[ Table 18]

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

When the final CS value exceeds 12 by the CS value added to the initial CS value according to the ACK or NACK, a modulo (modulo)12 is applied to the final CS value since the length of the sequence is 12.

[ Table 19]

Next, PUCCH format 2 is a short PUCCH format supporting more than 2-bit control information, and the number of RBs used may be configured by an upper layer. The control information may 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 transmitting the DMRS in one OFDM symbol is fixed to subcarriers with indexes #1, #4, #7, # 10. Through a modulation process after channel coding, control information is mapped to the remaining subcarriers except for the subcarrier where the DMRS is located.

In summary, the values and ranges that may be configured for each PUCCH format described above may be summarized as [ table 20 ]. If the values in the table below do not need to be configured, the values will be shown as n.a.

[ Table 20]

Meanwhile, to improve uplink coverage, multi-slot repetition may be supported for PUCCH formats 1, 3, and 4, and PUCCH repetition may be configured for each PUCCH format.

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

[ Table 21]

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

For a PUCCH resource set, a maximum payload value of a first PUCCH resource set may be fixed to 2 bits, and thus a corresponding value may not be separately configured by an upper layer or the like. When the remaining PUCCH resource sets are configured, the indexes of the corresponding PUCCH resource sets may be configured in an ascending order according to the maximum payload value, and the maximum payload value may not be configured in the last PUCCH resource set. The upper layer configuration of the PUCCH resource set may be as shown in [ table 22 ].

[ Table 22]

The resourceList parameter of the table may include an ID of a PUCCH resource belonging to the PUCCH resource set.

If the initial access or PUCCH resource set is not configured, a PUCCH resource set consisting of a plurality of cell-specific PUCCH resources in the initial BWP as shown in [ table 22] may be used. The PUCCH resources to be used for initial access in the PUCCH resource set may be indicated by SIB 1.

[ Table 23]

In case of

PUCCH format

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

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

[ Table 24]

For the configured PUCCH resource, the transmission period and offset are configured by 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, otherwise the corresponding PUCCH resource may not be transmitted.

In case of CSI transmission, PUCCH resources to send periodic or semi-persistent CSI reports over PUCCH may be configured in PUCCH-CSI-ResourceList parameter as shown in [ table 23 ]. The parameter contains a list of PUCCH resources for each BWP of the cell or CC that sent the corresponding CSI report. The PUCCH resource may be a resource belonging to PUCCH format 2 or PUCCH format 3 or PUCCH format 4.

[ Table 25]

For PUCCH resources, the transmission period and offset are configured by reportSlotConfig in [ table 23 ].

In case of HARQ-ACK transmission, a resource set of PUCCH resources to be transmitted is first selected according to a payload including UCI of a corresponding HARQ-ACK. That is, a PUCCH resource set having a minimum payload not less than the UCI payload is selected. Next, a PUCCH resource in the PUCCH resource set may be selected by scheduling a PUCCH Resource Indicator (PRI) of DCI of a TB corresponding to a corresponding HARQ-ACK, and the PRI may be a 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 may be as shown in [ table 26 ].

[ Table 26]

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

[ equation 1]

In the above equation, r_PUCCHIndex, R, representing PUCCH resource selected in PUCCH resource set_PUCCHDenotes the number of PUCCH resources, Delta, belonging to a PUCCH resource set_PRIDenotes the PRI value, N_CCE，pDenotes the total number of CCEs of the CORESET to which the received DCI belongs, and N_CCE，pThe first CCE index indicating reception of DCI.

The time at which the corresponding PUCCH resource is transmitted is K at the TB transmission corresponding to the corresponding HARQ-ACK₁After the time slot. K₁The candidates of the value are configured as upper layers, and more specifically, are configured in [ table 21]]dl-DataToUL-ACK parameter in PUCCH-Config specified in (1). K of one of these candidates₁The value may be selected by a PDSCH-to-HARQ feedback timing indicator in DCI for a scheduling TB, and the value may be in [ table 5]]Or [ Table 6]]The value specified in (1). At the same time, K₁The unit of the value may be a slot unit or a sub-slot unit. Here, the sub-slot is a unit having a length smaller than the slot length, and one or more symbols may constitute one sub-slot.

Next, a case where 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 symbol units, and ii) at least one PUCCH resource may be a short PUCCH), the terminal may transmit UCI through one or two PUCCH resources in one slot or sub-slot. Meanwhile, the terminal may not desire to transmit multiple PUCCH resources for HARQ-ACK transmission in one slot.

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

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) of the other cases.

Case 1-1) is shown in fig. 9.

Fig. 9 illustrates a view of a case where a plurality of PUCCH resources for HARQ-ACK transmission for a PDSCH overlap when multi-slot repetition is not configured, according to an embodiment. Referring to fig. 9, for two or more different PDCCHs (9-10, 9-11) scheduling a PDSCH, when transmission slots of PUCCH resources corresponding to each PDCCH are the same, the corresponding PUCCH resources may be considered to overlap each other. That is, when K indicated by a plurality of PDSCHs is associated with₁The uplink slots corresponding to the values (9-50, 9-51) are the same, PUCCH resources corresponding to the respective PDSCHs may be considered to overlap each other.

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

Next, a case 1-2) where PUCCH resources for HARQ-ACK transmission and PUCCH resources for SR and/or CSI transmission overlap, or when a plurality of PUCCH resources for SR and/or CSI transmission overlap, will be described. In the above case, when a plurality of PUCCH resources transmitted in the same slot overlap one or more symbols on the time axis, the corresponding PUCCH resources are defined to overlap, and whether UCI is multiplexed in these resources may be summarized as [ table 27 ].

[ Table 27]

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

On the other hand, when each PUCCH resource transmitting SR and HARQ-ACK overlaps, i.e., in case 1-2-1, whether UCI multiplexing is performed is divided according to the format of the PUCCH resource.

SR on PUCCH format 0 + HARQ-ACK on PUCCH format 1: SR is discarded and only HARQ-ACK is sent

-other cases: SR and HARQ-ACK are multiplexed

Further, in the remaining case 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 these CSI are multiplexed may follow the upper layer configuration. Further, the configuration of whether to multiplex between HARQ-ACK and CSI and the configuration of whether to multiplex between a plurality of CSIs may be independently performed.

For example, whether multiplexing is performed between HARQ-ACK and CSI may be configured by simultaneousHARQ-ACK-CSI parameters of each

PUCCH format

2, 3, or 4, and the corresponding parameters may be configured to the same value of the PUCCH format. If multiplexing is configured not to be performed by the above-described parameters, only HARQ-ACK may be transmitted and overlapping CSI may be discarded. In addition, whether multiplexing is performed between multiple CSIs can be configured through a multi-CSI-PUCCH-ResourceList parameter in PUCCH-Config. That is, when the multi-CSI-PUCCH-ResourceList parameter is configured, multiplexing between CSIs may be performed, otherwise, only the PUCCH corresponding to CSI having a higher priority may be transmitted according to a priority between CSIs.

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

[ Table 28]

Each of the options in the table above is as follows.

-option 1: the 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 for SR is selected, and if the SR value is negative, the PUCCH resource for HARQ-ACK is selected. The HARQ-ACK information is transmitted to the selected PUCCH resource.

-option 2: the HARQ-ACK information and the SR information are multiplexed and transmitted to a PUCCH resource for HARQ-ACK.

-option 3: the SR information and the HARQ-ACK information are multiplexed and transmitted to PUCCH resources for CSI.

Option 4: and transmitting PUCCH resources for overlapping HARQ-ACK. The detailed operation is described in the above case 1-1).

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

Option 6: when a PUCCH resource for HARQ-ACK corresponding to a semi-persistent scheduling (SPS) PDCCH and a PUCCH resource for CSI transmission overlap and multiplexing between the HARQ-ACK and the CSI is configured as a higher layer, HARQ-ACK information and CSI information are multiplexed and transmitted to the PUCCH resource for HARQ-ACK.

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

Option 7: when a plurality of PUCCH resources for CSI transmission overlap and multiplexing between a plurality of CSIs is configured as an upper layer, a PUCCH resource list for CSI multiplexing configured as an upper layer, that is, all UCI payloads multiplexed in a multi-CSI-PUCCH-ResourceList may be transmitted, and the UCI payload is transmitted after selecting a resource having a lowest index. If there are no resources in the list that can transmit all multiplexed UCI payloads, the resource with the largest index is selected and a CSI report corresponding to the number of transmittable resources is transmitted.

In the above, for convenience of description, a case where two PUCCH resources overlap is focused, but even when three or more PUCCH resources overlap, the method may be similarly applied. 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 may be followed.

If transmission is configured without multiplexing between specific UCIs, UCI having a higher priority may be transmitted and UCI having a lower priority may be discarded according to an order of HARQ-ACK > SR > CSI. If transmission is configured without multiplexing when a plurality of CSI PUCCH resources overlap, a PUCCH corresponding to CSI having a higher priority may be transmitted and a PUCCH corresponding to another CSI may be discarded.

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 rest. Each as shown in fig. 10.

Fig. 10 illustrates a view of a case where PUCCH resources overlap when multi-slot repetition is configured according to an embodiment.

Referring to case 2-1), when multi-slot repetition is configured in PUCCH resources for HARQ-ACK, i.e., PUCCH #1 is repeatedly transmitted over a plurality of slots (10-30, 10-40) and PUCCH #2 is also repeatedly transmitted over a plurality of slots (10-31, 10-41), if K is greater than K₁The indicated starting slots of the two PUCCHs 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). Accordingly, HARQ-ACKs corresponding to PDSCH #1 and PDSCH #2 are multiplexed and transmitted to the corresponding PUCCH through the HARQ-ACK codebook.

For convenience of description, a case where a plurality of multi-slot repeated PUCCHs overlap is exemplified, but the same method may be applied when there is overlap between the multi-slot repeated PUCCH and a PUCCH transmitted in a single slot.

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

Between PUCCHs where more than one symbol overlaps in a corresponding slot (10-70), UCI having a higher priority may be transmitted by comparing priorities between UCI in the PUCCHs, and other UCI may be discarded from the corresponding slot. At this time, the priority between UCI may follow the order of HARQ-ACK > SR > CSI.

In addition, when a plurality of CSI PUCCH resources overlap, a PUCCH corresponding to high priority CSI may be transmitted, and a PUCCH corresponding to another CSI may be dropped from a corresponding slot. The PUCCH transmission or dropping according to the above priority is performed only in slots where symbol-by-symbol overlapping occurs, and is not performed in other slots. That is, a PUCCH in which multi-slot repetition is configured may be discarded in a slot in which overlapping in symbol units occurs, but may be transmitted in the configured remaining slots.

In the above case, for convenience of description, a case where a plurality of multi-slot repeated PUCCHs are overlapped is exemplified, but the same method may be applied when there is an overlap between the multi-slot repeated PUCCH and a PUCCH transmitted in a single slot.

Next, a method of generating a HARQ-ACK codebook for transmitting HARQ-ACK on the selected PUCCH resource will be described. And when the PDSCH is scheduled based on the DCI information of the downlink data PDCCH, transmitting the PDSCH, and transmitting the time slot information mapped by the corresponding HARQ-ACK feedback and the mapping information of an uplink control channel PUCCH carrying the HARQ-ACK feedback information. Specifically, the slot interval between downlink data PDSCH and corresponding HARQ-ACK feedback may be indicated by the PDSCH-to-HARQ feedback timing indicator and may indicate one of eight feedback timing offsets configured by higher layers (e.g., RRC signaling). Also, in order to transfer PUCCH resources including a type of uplink control channel PUCCH to which HARQ-ACK feedback information is to be mapped, a position of a start symbol, and the number of mapping symbols, one of 8 resources configured to an upper layer by a PUCCH resource indicator may 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 may be referred to as a mixture of HARQ-ACK codebooks.

The base station may configure a type 1HARQ-ACK codebook for the terminal to transmit HARQ-ACK feedback bits corresponding to a PDSCH that may be transmitted at a predetermined slot position regardless of whether an actual PDSCH is transmitted. Alternatively, the base station may configure a type 2HARQ-ACK codebook for the terminal to manage and transmit HARQ-ACK feedback bits corresponding to the actually transmitted PDSCH through a counter Downlink Assignment Index (DAI) or a total DAI.

When the terminal receives the type 1HARQ-ACK codebook, the terminal may determine feedback bits to transmit through a K1 candidate value, which is HARQ-ACK feedback timing information for the PDSCH and a table including slot, starting symbol, number of symbols, or length information to which the PDSCH is mapped. The table including the starting symbol, the number of symbols, or the length information of the PDSCH may be configured as higher layer signaling or may be determined as a default table. Further, the K1 candidate may 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 by a value of K1, and if the PDSCH is repeatedly transmitted in a plurality of slots (slot aggregation), the upper layer parameter indicates a value of K1 and the number of repeated transmissions, for example, a PDSCH-aggregation factor value configured in a PDSCH-configuration IE in active BWP. If the PDSCH is repeatedly transmitted in a plurality of slots, a value of K1 is indicated based on the last slot in the PDSCH repeated transmission, and the slot to which the PDSCH is mapped is regarded as a PDSCH-aggregate factor slots from the last slot to be repeatedly transmitted, i.e., a slot from which the repeated transmission starts.

Assume that the set of PDSCH reception candidate cases in serving cell c is M_A，c，M_A，cCan be in the following [ pseudo code 1]]The determination in the step.

[ Start pseudo code 1]

-step 1: initialize j to 0, M_A，cIs initialized to the empty set and the HARQ-ACK transmission timing index k is initialized to 0.

-step 2: r is configured for each set of rows in a table including slot, starting symbol, symbol number or length information to which PDSCH is mapped. If the symbol to which the PDSCH indicated by each row of R is mapped is configured as an uplink symbol according to higher layer configuration, the corresponding row is deleted from R.

-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，cIn (1).

-step 3-2: if the terminal receives more than one PDSCH in one slot, the maximum number of PDSCHs that can be allocated to different symbols in R is counted, the number of j is increased by 1, and they are added to M_A，cIn (1).

-step 4: restart from the second step and increase k by 1.

[ pseudo code 1 end ]

For MAs and c defined as [ pseudocode 1], HARQ-ACK feedback bits may be determined in the following [ pseudocode 2] step.

[ Start pseudo code 2]

-step 1: the HARQ-ACK reception opportunity index m is initialized to 0 and the HARQ-ACK feedback bit index j is initialized to 0.

-step 2-1: if the terminal is instructed not to receive HARQ-ACK bundling of codewords through higher layer signaling, not to receive CBG transmission of PDSCHs, and to receive up to 2 codewords through 1 PDSCH, HARQ-ACK feedback bits for each codeword are constructed by increasing j by 1.

-step 2-2: if the terminal is instructed to receive HARQ-ACK bundling of codewords through higher layer signaling AND is instructed to receive up to 2 codewords through 1 PDSCH, HARQ-ACK feedback bits are composed for each codeword of one HARQ-ACK feedback bit through a binary AND operation.

-step 2-3: if the terminal is instructed to transmit CBGs of PDSCH through higher layer signaling and is not instructed to receive at most 2 codewords through 1 PDSCH, HARQ-ACK feedback bits for each codeword of the number of CBGs are constructed by increasing j by 1.

-step 2-4: if the terminal is instructed to transmit CBG of PDSCH through higher layer signaling and is instructed to receive at most 2 codewords through 1 PDSCH, a CBG number of HARQ-ACK feedback bits are constructed by increasing j by 1 and added to each codeword.

-step 2-5: if the terminal is not instructed to transmit CBG of PDSCH through higher layer signaling and is not instructed to receive up to 2 codewords through 1 PDSCH, HARQ-ACK feedback bits for each codeword are constructed.

-step 3: restart from step 2-1 and increase m by 1.

[ pseudo code 2 end ]

When the terminal receives the type 2HARQ-ACK codebook, the terminal determines feedback bits to be transmitted by managing counter Downlink Assignment Indices (DAIs) or total DAIs corresponding to HARQ-ACK feedback bits of the PDSCH and K1 candidate values, the K1 candidate value being HARQ-ACK feedback timing information for the PDSCH. The K1 candidate value as HARQ-ACK feedback timing information for the PDSCH is composed of a combination of a default value and a value specified by higher layer signaling. For example, the default value may be configured as {1, 2, 3, 4, 5, 6, 7, 8 }.

The counter DAI of DCI format 1_0 or DCI format 1_1 if PDSCH is allocated in the serving cell c is referred to as PDCCH monitoring timing m

And the total DAI of DCI format 1_1 to which PDSCH is allocated in the uplink control channel PDCCH monitoring timing m is

Then may be in the following [ pseudo code 3]]Configuring a type 2HARQ-ACK codebook in the step.

[ Start pseudo code 3]

-step 1: initializing a serving cell index c to 0, a PDCCH monitoring timing m to 0, j to 0, and a DAI comparison index V_temp、V_tempIs initialized to 0 and sets the HARQ-ACK feedback bit set VS to the null set.

-step 2: c is excluded from the serving cell set if the PDCCH monitoring timing m is before a downlink BWP change of the serving cell c or before an uplink BWP change of the PCell and the downlink BWP change is not triggered due to the DCI format 1_1 of the PDCCH monitoring timing m.

-step 3-1: if there is a PDSCH allocated by a PDCCH corresponding to the PDCCH monitoring timing m in the serving cell c, and if

Less than or equal to V_tempJ is increased by 1 and V_tempIs configured to

Furthermore, if

Is an empty set, then V_temp2Is configured as

And if

If not, then V_temp2Is configured as

-step 3-2: if there is a PDSCH allocated by a PDCCH corresponding to the PDCCH monitoring timing m in the serving cell c and the terminal is instructed to receive HARQ-ACK bundling of codewords through higher layer signaling and is instructed to receive up to two codewords through one PDSCH from at least one downlink BWP of at least one serving cell, the HARQ-ACK feedback bit for each codeword is constructed by increasing j by 1.

-step 3-3: if there is a PDSCH allocated by a PDCCH corresponding to the PDCCH monitoring timing m in the serving cell c AND the terminal is instructed to receive HARQ-ACK bundling of codewords through higher layer signaling AND is instructed to receive at most two codewords through one PDSCH from at least one downlink BWP of at least one serving cell, a HARQ-ACK feedback bit is composed for each codeword of one HARQ-ACK feedback bit through a binary AND operation.

-step 3-4: if there is a PDSCH allocated by a PDCCH corresponding to the PDCCH monitoring timing m in the serving cell c and the terminal is not instructed to receive at most two codewords through one PDSCH, an HARQ-ACK feedback bit is constructed for one codeword.

-step 4: restart from step 2 and increase c by 1.

-step 5: restart from step 2 and increase m by 1.

-step 6: when V is_temp2Less than V_tempWhen, j is increased by 1.

-step 7-1: configuring a total number of HARQ-ACK feedback bits to 2 · (4 · j + V) if the terminal is instructed not to bundle HARQ-ACK codewords through higher layer signaling and is instructed to receive at most 2 codewords through one PDSCH from at least one downlink BWP of at least one serving cell_temp2)。

-step 7-2: configuring a total number of HARQ-ACK feedback bits to 4 · j + V if the terminal is indicated as codeword bundling HARQ-ACK through higher layer signaling or is not indicated to receive up to 2 codewords through 1 PDSCH_temp2。

-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.

[ pseudo code 3 end ]

Fig. 11 shows a view of base station and terminal radio protocol structures when performing single cell, carrier aggregation, and dual connectivity according to an embodiment.

Referring to fig. 11, radio protocols of the next generation mobile communication system include NR Service Data Adaptation Protocols (SDAP) 1125 and 1170, NR Packet Data Convergence Protocols (PDCP) 1130 and 1165, and NR Radio Link Controls (RLC) 1140 and 1155 in the terminal and

NR base stations

1135 and 1160, and NR Medium Access Controls (MAC), respectively.

The primary functions of

NR SDAPs

1125 and 1170 may include some of the following functions.

-transmission of user plane data

Mapping between QoS flows and DRBs for both DL and UL

Marking QoS flow IDs in both DL and UL data packets

Mapping of reflected QoS flows of UL SDAP PDUs to DRBs

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

The primary functions of the NR PDCP10-30 and 10-65 may include some of the following functions.

Header compression and decompression: ROHC only

-transmission of user data

-sequential delivery of upper layer PDUs

Out-of-order delivery of upper layer PDUs

-PDCP PDU reordering for reception

Duplicate detection of lower layer SDU

-retransmission of PDCP SDU

-encryption and decryption

Timer-based SDU discard in uplink

In the above, the order reordering function of the NR PDCP device refers to a function of reordering PDCP PDUs received from a lower layer in order based on a PDCP Sequence Number (SN), may include a function of delivering data to an upper layer in the reordered order, may include a function of directly transmitting regardless of order, may include a function of reordering and recording lost PDCP PDUs, may include a function of transmitting a status report of the lost PDCP PDUs to a transmitting side, or may include a function of requesting retransmission of the lost PDCP PDUs.

The main functions of

NR RLC

1135 and 1160 may include some of the following functions.

-transmission of upper layer PDU

-sequential delivery of upper layer PDUs

Out-of-order delivery of upper layer PDUs

Error correction by ARQ

Concatenation, segmentation and reassembly of RLC SDUs

Re-segmentation of PDCP data PDUs

Reordering of PDCP data PDUs

-duplicate detection

-protocol error detection

RLC SDU discard

RLC re-establishment

In the above, the sequential delivery of the NR RLC device refers to a function of sequentially transmitting RLC SDUs received from a lower layer to an upper layer, and may include a function of reassembling and delivering when one RLC SDU is initially divided into a plurality of RLC SDUs and received, may include a function of rearranging and delivering received RLC PDUs based on RLC Sequence Numbers (SNs) or PDCP Sequence Numbers (SNs), may include a function of reordering and recording missing RLC PDUs, may include a function of reporting a status of missing RLC PDUs to a transmitting side, may include a function of requesting retransmission of missing RLC PDUs, may include a function of sequentially forwarding only RLC PDUs before missing RLC SDUs when there are missing RLC SDUs, may include a function of sequentially delivering all RLC SDUs received before a timer starts to a higher layer even if there are missing RLC SDUs if a predetermined timer expires, or may include a function of sequentially delivering all RLC SDUs received to a higher layer if a predetermined timer expires even if there are missing RLC SDUs. Further, RLC PDUs may be processed in the order in which they were received (in which order they arrived regardless of sequence number or sequence number) and delivered to the PDCP device in any order (out-of-order delivery), and in the case of fragments, fragments stored in a buffer or to be received later may be received and reconstructed into complete RLC PDUs, processed, and then transmitted to the PDCP device. The NR RLC layer may not include a connection function, and this function may be performed in the NR MAC layer or replaced by a multiplexing function of the NR MAC layer.

In the above, out-of-order delivery of the NR RLC device refers to a function of directly transmitting RLC PDUs received from a lower layer to an upper layer regardless of order, and may include a function of re-assembling and delivering when one RLC SDU is initially divided into a plurality of RLC PDUs and received, or may include a function of storing RLC SNs or PDCP SNs of the received RLC PDUs and ordering the order to record the missing RLC PDUs.

The

NR MACs

1140 and 1155 may be connected to several NR RLC layer devices configured in one terminal, and the main functions of the NR MACs may include some of the following functions.

Mapping between logical channels and transport channels

-multiplexing/demultiplexing of MAC SDUs

-scheduling information reporting

Error correction by HARQ

-priority handling between logical channels of one UE

-priority handling between UEs by dynamic scheduling

-MBMS service identification

-transport format selection

-filling

The NR PHY layers 1145 and 1150 may 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 the radio channel to deliver them to the upper layer.

The detailed structure of the radio protocol structure may vary according to the carrier (or cell) operation method. For example, when a base station transmits data to a terminal 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 a plurality of carriers in a single TRP, the base station and the terminal have a single structure up to the RLC, such as 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 a dual connectivity (DDC) using a plurality of carriers among a plurality of TRPs, the base station and the terminal have a single structure up to RLC as in 1120, but use a protocol structure for multiplexing a PHY layer through a MAC layer.

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 a plurality of TRPs, and transmits only one PUCCH resource for HARQ-ACK within one slot as a HARQ-ACK transmission method.

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

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 may 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 may be different according to a user, a user's intention, or a habit. Therefore, the definition of the terms should be based on the contents of the entire specification.

Hereinafter, the base station is a main body that performs resource allocation of the terminal, and may be at least one of a eNode 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. A terminal may include a User Equipment (UE), a Mobile Station (MS), a cellular phone, a smart phone, a computer, or a multimedia system capable of performing communication functions. Further, the NR or LTE/LTE-a system will be described below as an example, but embodiments of the present disclosure may be applied to other communication systems having similar technical backgrounds or channel types. Furthermore, embodiments of the present disclosure may be applied to other communication systems with some modifications within the scope not too departing from the scope of the present disclosure as determined by those having skill in the art.

The present disclosure is applicable to both FDD and TDD systems.

Hereinafter, in the present disclosure, the higher layer signaling is a signal transmission method transmitted from the base station to the terminal using a downlink data channel of a physical layer or a signal transmission method transmitted from the terminal to the base station using an uplink data channel of a physical layer, and may be referred to as RRC signaling, PDCP signaling, or Medium Access Control (MAC) control element (MAC CE).

Hereinafter, in the present disclosure, in determining whether to apply cooperative communication, the terminal may use various methods in which PDCCH(s) to which PDSCH to which cooperative communication is applied have a specific format, PDCCH(s) to which PDSCH to which cooperative communication is applied include a specific indicator indicating whether cooperative communication is applied, PDCCH to which 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 convenience of description, receiving, by the terminal, the PDSCH to which the cooperative communication is applied based on a condition similar to that described above will be referred to as an NC-JT case.

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

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

< first embodiment: DCI reception for NC-JT >

Unlike before, the 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 cell, TRP and/or beam is one of the basic technologies capable of satisfying various service demands by increasing the strength of a signal received by a terminal or effectively performing interference control between cells, TRPs and/or beams.

Joint Transmission (JT) is a representative transmission technique for cooperative communication as described above, and one terminal is supported through different cells, TRPs, and/or beams by the joint transmission technique to increase the signal strength received by the terminal. Meanwhile, since each cell, TRP or/and beam and a channel of a terminal may have significantly different characteristics, different precoding, Modulation and Coding Schemes (MCS) and resource allocation need to be applied to a link between each cell, TRP or/and beam and the terminal. Especially, in 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, separate DL transmission information configuration per cell, TRP, and/or beam is a major factor in increasing the payload required for DL DCI transmission, which may adversely affect the reception performance of a Physical Downlink Control Channel (PDCCH) transmitting DCI. Therefore, it is necessary to carefully design a trade-off between the amount of DCI information and PDCCH reception performance to support JT.

Fig. 12 illustrates an example of antenna port configuration and resource allocation for cooperative communication in a wireless communication system according to some embodiments.

Referring to fig. 12, an example of joint resource allocation according to TRP according to Joint Transmission (JT) technology and situation is shown. In fig. 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 from TRP a (1205) and TRP B (1210) to terminal 1215, and joint precoding may be performed among a plurality of TRPs. This may 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 may receive one DCI information for receiving one PDSCH demodulated based on DMRSs transmitted through DMRS ports a and B.

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

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

Various radio resource allocations may be considered, such as when the frequency and time resources used by multiple TRPs to transmit PDSCH 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 a plurality of TRPs repeatedly transmit the same PDSCH in each case of the above radio resource allocation to improve reliability, if a receiving terminal does not know whether the corresponding PDSCH is repeatedly transmitted, the corresponding terminal may have a limitation in improving reliability because the terminal cannot perform combining on the corresponding PDSCH in the physical layer. Accordingly, the present disclosure provides a repeat transmission instruction and configuration method for improving NC-JT transmission reliability.

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

Fig. 13 is a diagram illustrating an example of Downlink Control Information (DCI) configuration for cooperative communication in a wireless communication system according to an embodiment.

Referring to fig. 13, four examples of DCI design for NC-JT support are shown.

Referring to fig. 13, a case #1(1300) is an example in which control information of a PDSCH transmitted in (N-1) additional TRPs is transmitted in the same form (the same DCI format) as that of the PDSCH transmitted in the serving TRP in the case where different (N-1) PDSCHs are transmitted from (N-1) additional TRPs (TRP #1 to TRP # (N-1)) except for the serving TRP (TRP #0) used when a single PDCCH is transmitted. That is, the terminal may obtain control information of 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)).

In the above case #1, the degree of freedom of control (allocation) per PDSCH can be fully guaranteed, but when each DCI is transmitted in different TRPs, a coverage difference of each DCI may occur and reception performance may deteriorate.

Case #2(1305) is an example in which, in addition to the serving PDSCH (TRP #0) used when transmitting a single PDSCH, in the case where a different PDSCH is transmitted among (N-1) additional TRPs (TRP #1 to TRP # (N-1)), control information of the PDSCH transmitted from the (N-1) additional TRPs is transmitted in a form different from that of the PDSCH transmitted from the serving TRP (a different DCI format or a different DCI payload). For example, in the case where DCI #0 transmits control information for a PDSCH transmitted in a serving TRP (TRP #0), all 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 for a PDSCH transmitted from a cooperating TRP (TRP #1 to TRP # (N-1)), some of the information elements of DCI format 1_0 to DCI format 1_1 may be included. Therefore, in the case where the sDCI transmits control information of the PDSCH transmitted in the cooperative TRP, the payload may be small compared to the normal dci (nDCI) transmitting PDSCH-related control information transmitted from the serving TRP, or the payload may include as many reserved bits as the number of bits smaller than nDCI.

In the above case #2, the degree of freedom of control (allocation) per PDSCH may be limited according to the content of the information element included in the sDCI, but since the reception performance of the sDCI is superior to that of the nDCI, the occurrence probability of the coverage difference of each DCI may be reduced.

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 from the serving TRP (TRP #0) used when a single PDSCH is transmitted, control information of PDSCHs transmitted from the (N-1) additional TRPs is transmitted in a format different from that of the control information of the PDSCHs transmitted from the serving TRPs (a different DCI format or a different DCI payload). For example, in case that DCI #0 transmits control information of a PDSCH transmitted in a serving TRP (TRP #0), all information elements of DCI format 1_0 to DCI format 1_1 are included, and in case of control information of a PDSCH transmitted from a cooperating TRP (TRP #1 to TRP # (N-1)), only some of the information elements of DCI format 1_0 to DCI format 1_1 may be collected and transmitted in one "secondary" DCI (sdic). For example, the sDCI may have at least one of HARQ-related information, such as frequency domain resource allocation, time domain resource allocation, and MCS of the cooperative TRP. Further, for information not included in the sDCI, such as a bandwidth part (BWP) indicator or a carrier indicator, the information may follow the DCI serving the TRP (DCI #0, normal DCI, nDCI).

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

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 from the serving TRP (TRP #0) used when a single PDSCH is transmitted, control information of PDSCHs transmitted from (N-1) additional TRPs is transmitted as control information of PDSCHs transmitted from the serving TRPs in DCI (long DCI, lddci). That is, the terminal can acquire control information of a PDSCH 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 may not increase, but the PDSCH control (allocation) freedom may be low, e.g., having a limited number of cooperative TRPs due to long DCI payload restriction.

In the following description and embodiments, the sDCI may refer to various auxiliary DCIs, such as shortened DCI, auxiliary DCI, or normal DCI including PDSCH control information transmitted from a cooperative TRP (the above-described PDI formats 1_0 to 1_ 1). The description similarly applies to various supplementary DCIs, if not particularly limited.

In the following description and embodiments, the above-described case #1, case #2, and case #3, in which one or more DCIs (PDCCHs) are used for NC-JT support, are divided into a plurality of PDCCH-based NC-JTs, and in the case of the above-described case #4, a single DCI (for NC-JT support) (PDCCH) may be classified as a single PDCCH-based NC-JT.

In the embodiment of the present disclosure, the "cooperative TRP" may be replaced with various terms such as "cooperative panel" or "cooperative beam" when actually applied.

In the embodiment of the present disclosure, the term "when NC-JT is applied" may be interpreted in various ways according to circumstances, such as "when a terminal simultaneously receives one or more PDSCHs from one BWP", "when a terminal indicates simultaneous reception of two or more PDSCHs from one BWP based on a Transmission Configuration Indicator (TCI)", "when a terminal receives PDSCHs associated with one or more DMRS port groups (port groups)", and the like, but it is used as one expression for convenience of explanation.

In the present disclosure, the radio protocol architecture of NC-JT may be used in various ways depending on the TRP deployment scenario. For example, if there is no or little backhaul delay between cooperating TRPs, a structure based on MAC layer multiplexing similar to 1110 of fig. 11 (CA-like approach) may be used. On the other hand, when the backhaul delay between the cooperative TRPs is so large that the backhaul delay cannot be ignored (for example, when information exchange such as CSI, scheduling, and HARQ-ACK between the cooperative TRPs requires 2 milliseconds (ms) or more), an independent structure of each TRP from the RLC layer (DC-like method) similar to 1120 of fig. 11 may be used to ensure a robust characteristic of delay.

< example 1-1: method for configuring Downlink control channel for NC-JT Transmission based on multiple PDCCH >

In NC-JT based on multiple PDCCHs, when DCI scheduled for a PDSCH of each TRP is transmitted, there may be CORESET or search space classified for each TRP. The CORESET or search space of each TRP may be configured to be at least one of the following.

Configuration of upper-level indices by CORESET: the TRP transmitting the PDCCH in the corresponding CORESET may be distinguished by an upper layer index value of each set CORESET. That is, in a set of CORESET having the same upper layer index value, it can be considered that the same TRP transmission PDCCH or PDCCH scheduling PDSCH of the same TRP is transmitted.

Multiple PDCCH-Config configuration: a plurality of PDCCH-configs are configured in one BWP, and each PDCCH-Config may be considered to be configured for each TRP PDCCH. Here, a list of TRP-specific CORESET and/or a list of search spaces for TRP may be configured.

CORESET beam/group configuration: by the beam or beam group set for each CORESET, the TRP corresponding to the respective CORESET can be identified. For example, when the same TCI state is configured in a plurality of CORESET, the corresponding CORESET may be considered to be transmitted through the same TRP, or a PDCCH scheduling a PDSCH of the same TRP in the corresponding CORESET may be transmitted.

Search space beam/beam group configuration: a beam or a group of beams 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 a plurality of search spaces, in the search spaces, it may be considered that the same TRP transmits a PDCCH, or it may be considered that a PDCCH scheduling a PDSCH of the same TRP transmits in the search spaces.

By dividing CORESET or search space for each TRP as described above, 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.

< second embodiment: HARQ-ACK information transmission method for NC-JT transmission >

The following embodiments provide a detailed method of transmitting HARQ-ACK information for NC-JT transmission.

Fig. 14A shows a view of a HARQ-ACK report for a non-coherent joint transmission (NC-JT) transmission according to an embodiment, fig. 14B is a view showing a HARQ-ACK report for a non-coherent joint transmission (NC-JT) transmission according to an embodiment, fig. 14C is a view showing a HARQ-ACK report for a non-coherent joint transmission (NC-JT) transmission according to an embodiment, and fig. 14D is a view showing a HARQ-ACK report for a non-coherent joint transmission (NC-JT) transmission according to an embodiment.

First, fig. 14A (option # 1: HARQ-ACK for single PDCCH NC-JT) 14-00 shows a case where HARQ-ACK information of one or more PDSCHs 14-05 scheduled by TRP is transmitted through one PUCCH resource 14-10 in case of NC-JT based on single PDCCH. Can be determined by PRI value and K in the DCI₁A value indicates PUCCH resources.

Fig. 14B (option #2) to 14D (option #4)14-20, 14-40, 14-60 show the case of NC-JT based on multiple PDCCHs. At this time, each option may be classified according to the number of PUCCH resources transmitting HARQ-ACK information corresponding to the PDSCH of each TRP and the position of the PUCCH resources on the time axis.

Fig. 14B (option # 2: joint HARQ-ACK)14-20 shows a case where HARQ-ACK information corresponding to PDSCHs 14-25 and 14-26 of each TRP is transmitted through one PUCCH resource. All of the HARQ-ACK information for each TRP may be generated based on a single HARQ-ACK codebook, or the HARQ-ACK information for each TRP may be generated based on a separate HARQ-ACK codebook.

When a separate HARQ-ACK codebook for each TRP is used, the TRP may be classified based on at least one of a set of CORESET having the same upper layer index, a set of CORESET 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.

Fig. 14C (option # 3: time division multiplexed (TDMed) individual HARQ-ACK)14-40 shows a case in which 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 may be defined by the K described above₁And (4) determining the value. If K is indicated by multiple PDCCH₁The values indicate the same slot, all corresponding PDCCHs can be considered to be scheduled in the same TRP, and all HARQ-ACK information corresponding thereto can be transmitted.

Fig. 14D (option # 4: TDMed individual HARQ-ACK within slot) 14-60 shows 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 PUCH resources 14-70 and 14-71. The slot through which the PUCCH resource of each TRP is transmitted may be defined by the K described above₁The value is determined and if K is indicated by multiple PDCCHs₁The values indicate the same slot, at least one of the following methods determines PUCCH resource selection and transmission symbol

Configure PUCCH resource groups for each TRP

A PUCCH resource group for HARQ-ACK transmission of each TRP may be configured. When the TRP of each CORESET/search space is classified as example 1-1, a PUCCH resource for HARQ-ACK transmission of the TRP may be selected among PUCCH resource groups of the corresponding TRP. It may be desirable to perform TDM between PUCCH resources selected from different PUCCH resource groups, that is, it may be desirable that the selected PUCCH resources do not overlap in symbol units. As described above, a separate HARQ-ACK codebook for each TRP may be generated and transmitted to the PUCCH resource selected for each TRP.

Indicating a different PRI for each TRP

When the TRP of each CORESET/search space is classified as example 1-1, PUCCH resources of each TRP may be selected according to the PRI. That is, the PUCCH resource selection procedure in Rel-15 described above may be independently performed for each TRP. At this time, the PRI used to determine the PUCCH resource for each TRP may be different. For example, the terminal may not desire to indicate the PRI for PUCCH resource determination for each TRP with the same value. Furthermore, TDM between PUCCH resources corresponding to the PRI of each TRP may be desired. That is, it may be desirable that the selected PUCCH resources do not overlap in symbol units. As described above, a separate HARQ-ACK codebook for each TRP may be generated and transmitted to the PUCCH resource selected for each TRP.

Defining K in units of sub-slots₁Value of

The PUCCH resource selection procedure in Rel-15 is as follows, but one value may be defined in a sub-slot unit. For example, a HARQ-ACK codebook for PDSCH/PDSCH that is indicated to report HARQ-ACK in the same sub-slot may be generated and transmitted through PDSCH resources indicated as PRI. The HARQ-ACK codebook generation and PUCCH resource selection process may be independent of whether TRP is classified for each CORESET/search space.

When the terminal supports NC-JT reception, one of the options may be configured by the upper layer, or implicitly selected depending on the case. For example, one of option 2 and option 3/4 may configure a terminal supporting NC-JT based on multiple PDCCHs as an upper layer. As another example, depending on whether single PDCCH based NC-JT or multiple PDCCH based NC-JT is supported/configured, option 1 may be selected for single PDCCH based NC-JT and one of options 2/3/4 may be selected for multiple PDCCH based NC-JT. As another example, in multi-PDCCH based NC-JT, the options used may be determined according to the selection of PUCCH resources. When PUCCH resources of the same slot are selected from different TRPs, HARQ-ACK may be transmitted according to option 4 if the corresponding PUCCH resources are different and do not overlap in symbol units, and HARQ-ACK may be transmitted according to option 2 if the PUCCH resources overlap or are the same in symbol units. When PUCCH resources of different slots are selected from different TRPs, HARQ-ACK may be transmitted according to option 3. The configuration of the options may depend on the terminal capabilities. For example, the base station may receive the terminal capabilities according to the procedure described above, and may configure the options based thereon. For example, option 4 configuration may be allowed for terminals supporting TDMed-only HARQ-ACK within a time slot, and terminals not having this capability may not desire the configuration according to option 4.

< third embodiment: PUCCH-PUCCH overlap processing method for NC-JT based on multiple PDCCHs >

In multi-PDCCH based NC-JT, when intra-slot TDMed single HARQ-ACK is used, multiple HARQ-ACKs within one slot may be transmitted through PUCCH resources. This is different from Rel-15, where Rel-15 is restricted, so only one HARQ-ACK is sent in one slot. Therefore, in this embodiment, a specific processing method of a case where overlap occurs between the PUCCH resources for HARQ-ACK and the PUCCH resources for other uplink control information is given.

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

Fig. 15A illustrates a view of a case where overlap occurs between PUCCH resources according to an embodiment.

Referring to fig. 15A, case 1(15-10) shows 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).

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

Some of the above cases may not occur according to the TRP-specific PUCCH resource configuration and HARQ-ACK transmission method described in example 2.

For example, in case of applying joint HARQ-ACK to inter-slot TDMed individual HARQ-ACK, only case 2 may occur.

On the other hand, in case of TDMed-only HARQ-ACK within the application slot, both case 1 and case 2 may occur.

As another example, some of the above cases may not occur according to whether the PUCCH resource group for each TRP described in example 2 is configured or not. Case 2 may only occur if all PUCCH resources are classified according to the TRP-specific PUCCH resource group. On the other hand, both

cases

1 and 2 may occur in the case where PUCCH resource groups per TRP are not configured or only PUCCH resources for HARQ-ACK transmission are classified according to the PUCCH resource groups per TRP.

A method of processing a PUCCH according to overlapping of PUCCH resources according to fig. 15A will be described in fig. 15B.

Fig. 15B illustrates a view of a method of transmitting a PUCCH when overlap occurs between PUCCH resources according to an embodiment.

Referring to fig. 15B, the terminal may receive configuration information related to PUCCH resources in operation 1530. The configuration information may be received through higher layer signaling.

At this time, the configuration information may include one or more PUCCH resource sets as described above, and the one or more PUCCH resources may be included in one PUCCH resource set. Please refer to the above for details.

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

At this time, the information on the resource for transmitting the uplink control information may include an indicator indicating the PUCCH resource received through the configuration information. Further, it may include information K1 on a slot position for transmitting the PUCCH resource. Please refer to the above for details.

In addition, when the terminal supports NC-JT reception, the terminal may receive DCI for each TRP. At this time, as a method of receiving DCI, various methods proposed in fig. 13 may be used. Please refer to the above for details.

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

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

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

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

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

At this time, the overlap between PUCCH resources may mean overlap in symbol units. Accordingly, operation 1560 may refer to an operation of identifying whether there is a PUCCH resource overlapping with a TDM PUCCH resource as shown in fig. 15A in a slot.

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

On the other hand, when overlap occurs, case 1 and case 2 described in fig. 15A may occur.

Accordingly, when it is determined in operation 1570 that the case corresponds to case 1, the terminal may perform an operation accordingly.

On the other hand, if it is determined in operation 1580 that the case corresponds to case 2, the terminal may perform an operation accordingly.

Details of the operation according to case 1 and case 2 will be described below.

Returning to the description of fig. 15A, in case 1, whether the Rel-15 based PUCCH overlap processing method is applicable may be determined according to the format of each PUCCH resource and transmission of SR or CSI through PUCCH resource # 3. If the SR is transmitted through the PUCCH resource #3, the following problems may occur when applying the Rel-15 based PUCCH multiplexing method.

It is assumed that one of 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, a PUCCH resource for HARQ-ACK transmission corresponding to PUCCH format 1 is referred to as PUCCH resource # 1.

In this case, if the 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 TDM with PUCCH resource #2, it is necessary to change the processing method based on Rel-15.

Therefore, at least one of the following methods can be considered to solve the above-described problems.

Method 1-1: when TDMed-only HARQ-ACK within a slot is applied, when an overlap occurs between a PUCCH resource (PUCCH format 1) for HARQ-ACK transmission and a PUCCH resource (PUCCH format 1) for SR transmission, a multiplexing rule is changed to discard an SR.

Methods 1-2: when TDMed-only HARQ-ACK within an application slot, PUCCH format 1 is not configured for HARQ-ACK transmission.

Methods 1 to 3: when TDMed-only HARQ-ACK within an application slot, PUCCH format 1 is not configured for SR transmission.

Methods 1 to 4: when TDMed-only HARQ-ACK within an application slot, the terminal does not expect an overlap between PUCCH resources for HARQ-ACK transmission (PUCCH format 1) and PUCCH format 1 for SR transmission.

On the other hand, when the Rel-15 based PUCCH multiplexing method is applied, the following problems may 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 PUCCH resources for both HARQ-ACK transmissions. This may be an undesirable situation in the network. For example, a plurality of TRPs receiving the HARQ-ACK may make all response processes of the SR request, and thus unnecessary control information transmission and reception and uplink resource allocation may occur. Therefore, a method of selecting one of PUCCH resources #1 and #2 and allowing multiplexing of an SR only for the resource is required.

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

Method 2-1: the selection is made according to an index or order. For example, a PUCCH resource transmitted first on the time axis may be selected, or a PUCCH resource corresponding to a low PRI or a PUCCH resource corresponding to a low PUCCH resource group may be selected.

Method 2-2: the selection is based on the maximum payload. For example, PUCCH resources having a large maximum payload that can be transmitted may be preferentially selected.

Methods 2 to 3: and selecting according to the PUCCH format. A long PUCCH with good coverage may be selected in preference to a short PUCCH. Further, PUCCH format 2/3/4 capable of transmitting more than 2 bits of payload may be selected in preference to PUCCH 0/1.

Methods 2-4: selection is based on TRP. When SR information needs to be transmitted to a specific TRP, a PUCCH resource corresponding to the same TRP may be selected. For example, a PUCCH resource for HARQ-ACK having the same spatial relationship information as PUCCH resource #3 may be selected. Alternatively, a PUCCH resource among PUCCH resource groups belonging to the TRP corresponding to the SR may be selected. Alternatively, if a TRP index is configured in CORESET transmitting DCI scheduling PDSCH and HARQ-ACK PUCCH transmission, a TRP index corresponding thereto may be configured for each SR ID, or it may be assumed that the TRP index to which all SRs are transmitted is a specific value, for example, TRP index 0. Alternatively, a TRP index may be configured in a PUCCH resource for transmitting an SR, or a specific value, for example, a TRP index 0 may be assumed. At this time, a PUCCH resource corresponding to a HARQ-ACK having the same value as the above-described SR ID or TRP index associated with the PUCCH for SR transmission may be selected. Alternatively, the TRP index may be represented as a parameter set for PUCCH power control. As an example, the TRP index may be represented by one of the following values in the following PUCCH-PowerControl IE configured as RRC or a combination thereof.

In more detail, the TRP index may 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 may correspond to TRP index 0, and when the value of p0-PUCCH-Id is between 5 and 8, it may correspond to TRP index 1. The mapping between the range of p0-PUCCH-Id and TRP index may vary. Alternatively, the TRP index may correspond to pathlossfrerencers configured for PUCCH power control. Alternatively, the TRP index may correspond to a power control adjustment state index configured for PUCCH power control. The power control adjustment state index is an indicator indicating a power control state of the PUCCH resource and may also be represented by expressions such as a closed loop power control index and a TRP/panel-specific closed loop power control index. When the twpucch-PC-adjustment states value of the RRC parameter is configured as twoStates, the power control adjustment state index may have one of two values (e.g., i0 or i1), where i0 may correspond to TRP index 0 and i1 may correspond to TRP index 1. The above i0 or i1 may be indicated in the form of a closed loopindex parameter value in spatial relationship information activated for each PUCCH/PUCCH group as shown below.

According to the above description, a resource having a closed loopindex parameter configured as i0 included in spatial relationship information associated with a PUCCH resource may be regarded as a PUCCH resource corresponding to TRP index 0, and a resource having a closed loopindex parameter configured as i1 may be regarded as a PUCCH resource corresponding to 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 at most 4. For example, a value, e.g., FourStates, may be configured as a twoPUCCH-PC-AdjustmentStates parameter, or a new parameter, e.g., fourPUCCH-PC-AdjustmentStates parameter, may be configured. At this time, when the closed loopindex parameter included in the spatial relationship information is configured as i0 and i1, it may be considered as TRP index 0, and when the closed loopindex parameter is configured as i2, i3, or a new parameter in the spatial relationship information, for example, the closed loopindex new parameter is additionally configured, it may be considered as TRP index 1. In addition, as described above, the association between the PUCCH resource and the TRP index may be established.

The terminal may not multiplex the SR and the HARQ-ACK if a PUCCH resource of the TRP to which the SR is to be transmitted is not selected (e.g., due to lack of information such as spatial relationship information). In this case, PUCCH resources or UCI having lower priority may be discarded according to the order of HARQ-ACK > SR > CSI.

Alternatively, to simplify the terminal operation, the base station may appropriately schedule PUCCH resources or indicate multiplexing configuration so that the above-described situation does not occur.

Next, in case 1, if CSI is transmitted through PUCCH resource #3, it may be determined whether to multiplex between HARQ-ACK and CSI by configuring a higher layer. If multiplexing is configured, the following problems may occur when applying the Rel-15 based PUCCH multiplexing method.

The same CSI information may be multiplexed to PUCCH resources for both HARQ-ACK transmissions and transmitted, which may result in a waste of uplink transmission resources and transmission power due to repeated CSI payload transmissions. Therefore, a method of selecting one of PUCCH resources #1 and #2 and allowing multiplexing of CSI only for the resource is required.

In order to solve the above problem, at least one of the following methods may be considered.

Method 3-1: according to index or order selection. For example, a PUCCH resource transmitted first on the time axis may be selected, or a PUCCH resource corresponding to a low PRI or a PUCCH resource corresponding to a low PUCCH resource group may be selected.

Method 3-2: the selection is based on the maximum payload. PUCCH resources having a large maximum payload that can be transmitted may be preferentially selected.

Methods 3-3: and selecting according to the PUCCH format. A long PUCCH with good coverage may be selected in preference to a short PUCCH. Further, when reporting sub-band CSI, PUCCH format 3/4 capable of sub-band CSI transmission may be selected in preference to PUCCH format 2 capable of wideband CSI transmission only.

Methods 3-4: selection is based on TRP. When only the channel state of a specific TRP is included in the CSI information, it may be desirable to multiplex the CSI information only on PUCCH resources to be transmitted to the corresponding TRP. For this, for example, a PUCCH resource for HARQ-ACK having the same spatial relationship information as PUCCH resource #3 may be selected. Alternatively, a PUCCH resource among PUCCH resource groups belonging to a TRP corresponding to CSI information may be selected. Alternatively, if a TRP index is configured in CORESET where DCI having scheduled PDSCH and HARQ-ACK PUCCH transmission is transmitted, the TRP index may be configured in a CSI report/resource configuration or in a TRP index in PUCCH resources for CSI report transmission. At this time, a PUCCH resource corresponding to the HARQ-ACK having the same value as the TRP index associated with the CSI PUCCH described above may be selected. The terminal may not multiplex CSI with other CSI if a PUCCH resource of TRP to which CSI is to be transmitted is not selected. In this case, PUCCH resources or UCI having lower priority may be discarded according to the order of HARQ-ACK > SR > CSI. When multiple CSIs overlap, priority between the CSIs may be applied. Alternatively, when a TRP index is configured in a CSI report/resource configuration or a TRP index is configured in a PUCCH resource for transmitting a CSI report, multiple CSIs having different TRP indexes may overlap. At this time, if CSI is configured to be multiplexed, for example, when the multi-CSI-PUCCH-ResourceList described above is configured, a TRP index of a PUCCH resource for transmitting the multiplexed CSI may not be clear. This can be prevented by appropriately scheduling PUCCH resources for CSI report transmission in the network. Alternatively, it may not be desirable to configure multi-CSI-PUCCH-resource list if CSI reports/resources with different TRP indices are configured or activated/triggered. Alternatively, a TRP index may be configured for each PUCCH resource corresponding to multi-CSI-PUCCH-ResourceList, or a specific TRP index value, for example, TRP index 0, may be assumed. Alternatively, in this case, even if multi-CSI-PUCCH-ResourceList is configured, multiplexing between overlapping CSI reports is not performed, and discarding according to priority may be performed. The priority at this time may follow the CSI reporting priority based on Rel-15.

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

According to the above description, among PUCCH resources, a resource having a closed loopindex parameter configured as i0 related to spatial relationship information may be regarded as a PUCCH resource corresponding to TRP index 0, and a resource having a closed loopindex parameter configured as i1 may be regarded as a PUCCH resource corresponding to 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-adjustments states parameter, for example, FourStates may be configured or a new parameter such as a foupucch-PC-adjustments states parameter may be configured. At this time, when the closed loopindex parameter related to the spatial relationship information is configured as i0 and i1, it may be considered as TRP index 0, and when the closed loopindex parameter is configured as i2, i3, or a new parameter in the spatial relationship information, for example, the closed loopindex new parameter is additionally configured, it may be considered as TRP index 1. In addition, as described above, the association between the PUCCH resource and the TRP index may be established.

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

Alternatively, to simplify the terminal operation, the base station may appropriately schedule PUCCH resources or indicate multiplexing configuration so that the above-described situation does not occur. For example, when the above simultaneousHARQ-ACK-CSI is configured, in case 1, the terminal may not desire a case of transmitting CSI through PUCCH resource # 3.

In case 2, the beam may be different between the overlapping PUCCH resources. This may be interpreted that the TRP to which UCI is transmitted may be different through overlapping PUCCH resources. A problem occurs if multiplexing is configured between corresponding PUCCH resources, that some of the multiplexed UCI may be transmitted to an undesired TRP. To solve this problem, at least one of the following methods can be considered.

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

Method 4-2: when the beams are different between the overlapping PUCCHs, multiplexing may not be performed, which may take priority over upper layer configuration. Accordingly, only one of the overlapping PUCCHs can be selected and transmitted, and the rest can be discarded, and PUCCH selection can follow a priority between UCIs contained in the overlapping PUCCHs. The UCI priority may be HARQ-ACK > SR > CSI. When multiple CSIs overlap, priority between the CSIs may be applied. The above PUCCH beams may be indicated by PUCCH spatial relationship information. Alternatively, the above-described PUCCH beam may be replaced with a TRP transmitting a PUCCH, wherein the TRP may be represented by PUCCH spatial relationship information, PUCCH resource groups, a TRP index, or the like. For example, when a TRP index is configured in CORESET that transmits DCI scheduled for PDSCH and HARQ-ACK PUCCH transmission, the TRP index may be configured in a CSI report/resource configuration or in a TRP index in PUCCH resources for CSI report transmission. At this time, a PUCCH resource corresponding to CSI having the same value as the TRP index associated with the above HARQ-ACK PUCCH may be selected.

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

In more detail, the TRP index may 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 may correspond to TRP index 0, and when the value of p0-PUCCH-Id is between 5 and 8, it may correspond to TRP index 1. The mapping between the p0-PUCCH-Id range and TRP index may vary. Alternatively, the TRP index may correspond to pathlossfrerencers configured for PUCCH power control. Alternatively, the TRP index may correspond to a power control adjustment state index configured for PUCCH power control. The power control adjustment state index is an indicator indicating a power control state of the PUCCH resource, and may also be referred to in an expression such as a closed loop power control index or a TRP/panel-specific closed loop power control index. When the twoPUCCH-PC-adjustment states value of the RRC parameter is configured as twoStates, the power control adjustment state index may have one of two values (e.g., i0 or i1), where i0 is TRP index 0 and i1 may correspond to TRP index 1. The above i0 or i1 may be indicated in the form of a closed loopindex parameter value in spatial relationship information activated by PUCCH/PUCCH groups as shown below.

According to the above description, among PUCCH resources, a resource having a closed loopindex parameter configured as i0 related to spatial relationship information may be regarded as a PUCCH resource corresponding to TRP index 0, and a resource having a closed loopindex parameter configured as i1 may be regarded as a PUCCH resource corresponding to 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-adjustments states parameter, for example, FourStates may be configured or a new parameter such as a foupucch-PC-adjustments states parameter may be configured. At this time, when the closed loopindex parameter related to the spatial relationship information is configured as i0 and i1, it may be considered as TRP index 0, and when the closed loopindex parameter is configured as i2, i3, or a new parameter in the spatial relationship information, for example, the closed loopindex new parameter is additionally configured, it may be considered as TRP index 1. In addition, as described above, a gap between the PUCCH resource and the TRP index may be established.

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

Methods 4-3: in order to simplify the terminal operation, the base station may appropriately schedule PUCCH resources so that PUCCH beam/TRP overlap does not occur in different situations.

At this time, the TRP or TRP index can be classified by the method described in method 4-2. For example, a TRP index may be configured for each PUCCH resource. Meanwhile, the TRP index may not be configured in the PUCCH resource for HARQ-ACK transmission or may not be used even if the TRP index is configured. Instead, a TRP index configured in CORESET in which DCI scheduling PUCCH transmission is transmitted may be actually used. Furthermore, the terminal may not expect that the TRP index configured for each PUCCH resource is different from the TRP index value configured in CORESET in which DCI scheduling PUCCH transmission is transmitted.

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

In more detail, the TRP index may 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 may correspond to TRP index 0, and when the value of p0-PUCCH-Id is between 5 and 8, it may correspond to TRP index 1. The mapping between the range of p0-PUCCH-Id and TRP index may vary. Alternatively, the TRP index may correspond to pathlossfrerencers configured for PUCCH power control. Alternatively, the TRP index may correspond to a power control adjustment state index configured for PUCCH power control. The power control adjustment state index is an indicator indicating a power control state of the PUCCH resource, and may also be represented by expressions such as a closed loop power control index and a TRP/panel-specific closed loop power control index. When the twpucch-PC-adjustment states value of the RRC parameter is configured as twoStates, the power control adjustment state index may have one of two values (e.g., i0 or i1), where i0 may correspond to TRP index 0 and i1 may correspond to TRP index 1. The above i0 or i1 may be indicated in the form of a closed loopindex parameter value in spatial relationship information activated for each PUCCH/PUCCH group as shown below.

According to the above description, among PUCCH resources, a resource having a closed loopindex parameter configured as i0 related to spatial relationship information may be regarded as a PUCCH resource corresponding to TRP index 0, and a resource having a closed loopindex parameter configured as i1 may be regarded as a PUCCH resource corresponding to 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-adjustments states parameter, for example, FourStates may be configured or a new parameter such as a foupucch-PC-adjustments states parameter may be configured. At this time, when the closed loopindex parameter related to the spatial relationship information is configured as i0 and i1, it may be considered as TRP index 0, and when the closed loopindex parameter is configured as i2, i3, or a new parameter in the spatial relationship information, for example, the closed loopindex new parameter is additionally configured, it may be considered as TRP index 1. In addition, as described above, the association between the PUCCH resource and the TRP index may be established.

Alternatively, when the beam/TRP is different between the overlapping PUCCHs, the base station may indicate the multiplexing configuration so that multiplexing is not performed. For example, when the above simultaneousHARQ-ACK-CSI is configured, the terminal may not expect the case where the PUCCH resource transmitting the HARQ-ACK and the PUCCH resource transmitting the CSI overlap in case 2. At this time, the inter-PUCCH beam/TRP may indicate the above-described TRP index.

In case of TDMed single HARQ-ACK within a slot, a constraint for simplifying an overlap processing method between PUCCHs may be configured. For example, the PUCCH format of the PUCCH resources for HARQ-ACK transmission may be limited, and the format may be a short PUCCH, i.e., format 0 and format 2 or some of them. It is also possible to limit the PUCCH to only long PUCCH or some of them. Alternatively, in case of TDMed individual HARQ-ACK within a slot, multiplexing between HARQ-ACK and CSI is not desired or can be omitted and overlapping CSI is always discarded.

Meanwhile, even when multi-slot repetition is configured, the above method can be similarly applied. Therefore, please refer to the above for details.

Alternatively, when multi-slot repetition is configured, multiplexing between overlapping PUCCHs is not allowed, similar to Rel-15, and PUCCH resources or UCI with low priority may be dropped from overlapping slots depending on the priority of HARQ-ACK > SR > CSI. Therefore, when multiplexing a plurality of CSIs, priority between the CSIs may be applied.

Meanwhile, multiplexing or dropping may occur even when PUCCH and PUSCH overlap. In this case, the PUCCH and PUSCH may be scheduled in the same serving cell or Component Carrier (CC), or may be scheduled in the same cell group or other serving cells/CCs belonging to the same PUCCH group. At this time, there may occur a case where a plurality of PUCCHs and a single PUCCH for HARQ-ACK transmission similar to case 1 overlap within the same cell group or the same PUCCH group, a single PUCCH and a single PUSCH for HARQ-ACK/SR/CSI transmission similar to case 2 overlap, or a plurality of PUSCHs scheduled in a plurality of serving cells/CCs and a single/plurality of PUSCHs overlap. At this time, a TRP index is configured for each CORESET, wherein DCI for scheduling PUSCH is transmitted in each serving cell/CC, and TRP indexes may be configured for PUCCH overlapping these PUSCHs. When multiplexing between the overlapped PUCCH and PUSCH, the PUCCH may 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 may be discarded according to a preset priority. For example, when PUCCH includes HARQ-ACK, PUSCH is dropped, and when PUCCH includes CSI and PUSCH also includes CSI, PUCCH may be dropped. If the TRP index is not configured in the PUSCH, dropping or multiplexing may be performed according to the rule configured in Rel-15.

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

In more detail, the TRP index may 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 may correspond to TRP index 0, and when the value of p0-PUCCH-Id is between 5 and 8, it may correspond to TRP index 1. The mapping between the p0-PUCCH-Id range and TRP index may vary. Alternatively, the TRP index may correspond to pathlossfrerencers configured for PUCCH power control. Alternatively, the TRP index may correspond to a power control adjustment state index configured for PUCCH power control. The power control adjustment state index is an indicator indicating a power control state of the PUCCH resource and may also be referred to as an expression such as a closed loop power control index or a TRP/panel-specific closed loop power control index. When the twpucch-PC-adjustment states value of the RRC parameter is configured as twoStates, the power control adjustment state index may have one of two values (e.g., i0 or i1), where i0 may correspond to TRP index 0 and i1 may correspond to TRP index 1. The above i0 or i1 may be indicated in the form of a closed loopindex parameter value in spatial relationship information activated by PUCCH/PUCCH groups as shown below.

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 at most 4. For example, as a value of the twoPUCCH-PC-adjustments states parameter, for example, FourStates may be configured or a new parameter such as a foupucch-PC-adjustments states parameter may be configured. At this time, when the closed loopindex parameter connected to the spatial relationship information is configured as i0 and i1, it may be considered as TRP index 0, and when the closed loopindex parameter is configured as i2, i3, or a new parameter in the spatial relationship information, for example, the closed loopindex new parameter is additionally configured, it may be considered as TRP index 1. In addition, as described above, the association between the PUCCH resource and the TRP index may be established.

< example 4; method for selecting PUCCH resources for multi-PDCCH based NC-JT >

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

Case i. When two or more PUCCH resources overlap, when a PUCCH for grant-based HARQ-ACK transmission is included, as described above, among PUCCH resources indicated by PRIs 9-40, 9-41 of HARQ-ACK of PDCCH, only PUCCH resources (9-31) selected based on PRI (9-41) corresponding to PDCCH (9-11) transmitted at the last time point may be selected and transmitted. As described above, the PUCCH resource selected at this time may 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 may be selected. Next, a PUCCH resource set indicated as PRI in the corresponding PUCCH resource set may be selected.

If the overlapping PUCCH resources contain UCI transmitted to different TRPs, the dropping rule as described in example 3 may be applied.

If 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 purpose, at least one of the following methods may be considered.

Method 1. In the PUCCH resource set, only PUCCH resources corresponding to a target TRP of UCI to be multiplexed are selected.

Method 2. In the PUCCH resource set, PUCCH resources not corresponding to a target TRP of UCI to be multiplexed are excluded. That is, one of a PUCCH resource corresponding to the target TRP and a PUCCH resource for which the target TRP is not configured is selected.

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

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

Meanwhile, the target TRP corresponding to the PUCCH resource may be a TRP classification factor explicitly/implicitly corresponding to the corresponding PUCCH resource, and the TRP classification factor may be one of CORESET index/TRP index/serving cell index. Alternatively, a PUCCH resource group to which a corresponding PUCCH resource belongs or a group/set index corresponding to a PUCCH resource set may be used as the TRP classification factor. Alternatively, the third embodiment may be represented by one or a combination of the above PUCCH power control parameters, and the parameters may be the above p0-PUCCH-Id value, pathlossReferenceRS, power control adjustment state index. If a power control adjustment state index is used, the TRP classification factor may be the corresponding TRP index from the power control adjustment state index, as described above.

When a PUCCH resource selected according to one of the above methods overlaps with other PUCCH resources, if target TRPs of the PUCCH resources are the same, the above UCI multiplexing and PUCCH resource selection procedure may be (re) applied. If the target TRPs of these PUCCH resources are different, the discard rule described in embodiment 3 above may be applied.

Case ii. When two or more PUCCH resources overlap, each of the respective PUCCH resources is a resource for CSI transmission, or when HARQ-ACK based on configuration grant and one or more CSI overlap, as described above, if multiplexing between multiple CSIs is configured as a higher layer, a PUCCH resource list for CSI multiplexing is configured as a higher layer, e.g., all multiplexed UCI payloads in multi-CSI-PUCCH-ResourceList may be transmitted, and the UCI payload may be transmitted after selecting one resource with the lowest index. If there is no resource on which all multiplexed UCI payloads in the list can be transmitted, the resource having the largest index is selected and the number of CSI reports that can be transmitted to the resource is transmitted.

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

Method 2. In the multi-CSI-PUCCH-ResourceList, PUCCH resources not corresponding to a target TRP of UCI to be multiplexed are excluded. That is, one of a PUCCH resource corresponding to the target TRP and a PUCCH resource for which the target TRP is not configured is selected.

Method 3. According to the method based on Rel-15, PUCCH resources are selected in the 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.

At this time, the target TRP of the UCI and the target TRP of the PUCCH resource may be identified according to the above-described method (e.g., case i).

When a PUCCH resource selected according to one of the above methods overlaps with other PUCCH resources, if a target TRP of the overlapped PUCCH resource is the same, the above UCI multiplexing and PUCCH resource selection procedure may be reapplied. If the target TRPs of these PUCCH resources are different, the discard rule described in embodiment 3 above may be applied.

And (iii) a case. In case of overlap between PUCCH resources and PUSCH, in Rel-15, a procedure of transmitting PUSCH only after multiplexing UCI of PUCCH to PUSCH or dropping PUSCH without PUCCH-PUSCH multiplexing is described. At this time, the PUCCH and PUSCH where the overlap occurs may belong to the same serving cell, or may belong to the same cell group or another serving cell belonging to the same PUCCH group.

A dropping rule similar to that described in (e.g., embodiment 3) may be applied if the target TRP of the overlapped PUCCH resource and PUSCH are different.

If the overlapped PUSCH resources and the target TRP of the PUSCH are the same, a method of ensuring that the multiplexed PUSCH can also be designated as the same target TRP is required. For this purpose, at least one of the following methods may be considered.

Method 1. Among the PUSCHs and the overlapped PUSCHs, one PUSCH corresponding to a target TRP of UCI to be multiplexed is selected according to a predetermined rule. The rule may be the same as the rule described in embodiment 3.

Method 2. In the PUSCH and the overlapped PUSCH, PUCCH resources not corresponding to a target TRP of UCI to be multiplexed are excluded. That is, one of the PUSCH corresponding to the target TRP and the PUSCH on which the target TRP is not configured is selected. The rule may be the same as the rule described in embodiment 3.

Method 3. According to the method based on Rel-15, whether a target TRP value or a target TRP of a PUSCH is configured, a PUSCH to be multiplexed is selected. At this time, it may 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 may be identified according to the above-described method (e.g., case i). The target TRP of the PUSCH may be identified by a TRP index configured in CORESET in which DCI scheduling the PUSCH is transmitted, or may be identified by a beam used to transmit the corresponding PUSCH, for example, TPMI indicated by spatial relationship information of DCI scheduling the corresponding PUSCH or SRS connected to or designated as the SRI.

When the selected PUSCH overlaps with other PUSCH resources according to one of the above methods, the above multiplexing procedure may be reapplied if the target TRPs of these PUSCH and PUCCH resources are the same. The dropping rule described in the above embodiment 3 may be applied if the target TRPs of these PUSCH and PUCCH resources are different.

Meanwhile, in the method proposed by the present disclosure, some components may be omitted and only some components may be included without departing from the spirit of the present disclosure.

Further, the methods proposed in the present disclosure may be performed in combination with some or all of the contents included in each embodiment without departing from the essence of the present disclosure.

< examples; method for generating HARQ-ACK codebook for repeated transmission NC-JT >

NC-JT may be used to improve the reliability of PDSCH repeated transmissions. The repeated transmission of the NC-JT PDSCH may be performed through different time resources. For example, the PDSCH may be repeatedly transmitted for each slot over multiple slots, or may be repeatedly transmitted within one slot. A single PDCCH may be used to schedule repeated transmissions. The DCI of the PDCCH may indicate a list of all TRPs participating in repeated transmission. The list of TRPs to be repeatedly transmitted may be represented in the form of a TCI status list, and the length of the TCI status list may be dynamically changed.

When the PDSCH is repeatedly transmitted over a plurality of slots, time and frequency resources of the first PDSCH transmitted are indicated by DCI, and the time and frequency resources in the slots allocated to the PDSCH repeatedly transmitted for each slot may be the same. If the number of repeated transmissions is greater than the number of TCI states, a particular pattern may be followed as TCI states are applied to each repeated slot. For example, if the number of repetitive transmissions is 4 and

TCI status indexes

1 and 2 are indicated, the TCI status may be applied to each of the transmission slots according to a pattern of 1, 2, 1, 2 or a pattern of 1, 2. Further, the number of repeated transmissions may be dynamically indicated by the DCI/MAC-CE. For example, the number of repeated transmissions may be indicated by a time domain resource allocation field indicated by the DCI. For example, except for the value indicated in the current NR by the time domain resource allocation field of the DCI (e.g., K described in fig. 8 above)₀Values of S, L, etc.), the number of repeated transmissions may also be indicated together.

When the PDSCH is repeatedly transmitted in one slot, time and frequency resources of the first PDSCH transmitted in the slot may be indicated by DCI, and a symbol length and frequency resources allocated for each PDSCH repeatedly transmitted may be the same. The repeatedly transmitted PDSCH offset may be configured in symbol units. For example, as a reference to the last symbol of the first repeat-transmitted PDSCH, the next repeat-transmitted PDSCH may be sent after the symbol separated by the configured offset.

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

When the repetitive transmission is configured according to the above-described embodiment, the HARQ-ACK codebook generation method may be different for each repetitive transmission method. That is, different HARQ-ACK codebook generation methods may be applied according to a repeated transmission in a slot or a repeated transmission over a plurality of slots. In this embodiment, for convenience of description, the description focuses on the type 1HARQ-ACK codebook.

Fig. 16A illustrates a view of a type 1HARQ-ACK codebook method for each PDSCH repeated transmission across multiple slots, PDSCH repeated transmission within a single slot, and no-repeat transmission according to an embodiment, fig. 16B is a view illustrating a type 1HARQ-ACK codebook method for each PDSCH repeated transmission across multiple slots, PDSCH repeated transmission within a single slot, and no-repeat transmission according to an embodiment, and fig. 16C illustrates a view of a type 1HARQ-ACK codebook method for each PDSCH repeated transmission across multiple slots, PDSCH repeated transmission within a single slot, and no-repeat transmission according to an embodiment.

First, when there is no duplicate transmission (16-00), the set M of reception candidate cases may be configured according to the pseudo code 1_A，cAnd may depend on whether or not a corresponding set M is received, based on pseudo-code 2_A，cReceives the candidate PDSCH to determine HARQ-ACK feedback bits. Whether to receive PDSCH # 116-10 and PDSCH # 216-20 is composed of HARQ-ACK codebooks 16-40, respectively, and may be transmitted as PUCCH resources 16-30 or PUSCH resources.

Next, when repeated transmission in a slot is configured (16-50), a set M of reception candidate cases may be configured according to pseudo code 1_A，cAnd may depend on whether set M is received or not, based on pseudo-code 2_A，cDetermines HARQ-ACK feedback bits according to whether received and set M according to pseudo code 2_A，cReceives a PDSCH corresponding to the candidate to determine HARQ-ACK feedback bits. On the other hand, in the pseudo code 2, the HARQ-ACK feedback bit is determined according to whether a repeated PDSCH is received for a first repeatedly transmitted PDSCH, and the HARQ-ACK feedback bit is ignored or corresponding PDSCHs of a second and subsequent PDSCHs, or in case of a corresponding reception candidate, that is, the HARQ-ACK feedback bit may be in correspondence with M_A，CThe location of the corresponding PDSCH among them is determined as NACK. Further, when configuring whether to perform intra-slot repeat transmission, repeat transmission on a plurality of slots may not be configured at the same time, and therefore, in this case, the number of transmission slots may be regarded as one slot.

Next, when the repeated transmission is configured over a plurality of slots (16-90), HARQ-ACK feedback bits of the repeatedly transmitted PDSCH 16-92 may be transmitted to the PUCCH 16-95, wherein the PUCCH 16-95 is transmitted to a slot corresponding to the K1 value from the last slot in which the PDSCH is repeatedly transmitted. When HARQ-ACK is transmitted with respect to PUCCHs (16-94) of remaining slots according to pseudo code 1 and pseudo code 2, at reception candidates corresponding to repeatedly transmitted PDSCH, i.e., corresponding to M_A，cThe HARQ-ACK feedback bit may be determined as NACK, for the position of the corresponding PDSCH therein.

Fig. 17 shows a terminal structure in a wireless communication system according to an embodiment.

Referring to fig. 17, the terminal may include a transceiver 17-00, a memory 17-05, and a processor 17-10. According to the communication method of the terminal described above, the transceiver 17-00 and the processor 17-10 of the terminal can operate. However, the components of the terminal are not limited to the above examples. For example, a terminal may include more or fewer components than the preceding components. Further, the transceiver 17-00, the memory 17-05 and the processor 17-10 may be implemented in the form of a single chip.

The transceivers 17-00 may transmit signals to and receive signals from base stations. Here, the signal may include control information and data. To this end, the transceiver 17-00 may include an RF transmitter that up-converts and amplifies the frequency of the transmitted signal, and an RF receiver that low-noise amplifies the received signal and down-converts the frequency. However, this is merely an example of a transceiver 17-00 and the components of the transceiver 17-00 are not limited to RF transmitters and RF receivers.

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

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

Further, the processors 17-10 may control a series of processes such that the terminal operates according to the above-described embodiments. For example, the processor 17-10 may control components of the terminal to simultaneously receive multiple PDSCHs by receiving DCI consisting of two layers. There may be a plurality of processors 17-10, and the processors 17-10 may perform component control operations of the terminal by executing programs stored in the memories 17-05.

Referring to fig. 18, a base station may 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 may operate according to the communication method of the base station. However, the components of the base station are not limited to the above examples. For example, a base station may include more or fewer components than those described above. Further, the transceiver 18-00, the memory 18-05, and the processor 18-10 may be implemented in a single chip.

The transceivers 18-00 can transmit signals to and receive signals from the terminals. Here, the signal may include control information and data. To this end, the transceivers 18-00 may be configured with an RF transmitter that upconverts and amplifies the frequency of the transmitted signal, and an RF receiver that low-noise amplifies the received signal and downconverts the frequency. However, this is merely an example of a transceiver 18-00 and the components of the transceiver 18-00 are not limited to RF transmitters and RF receivers.

The transceiver 18-00 may receive signals through a wireless channel, output signals to the processor 18-10, and transmit signals output from the processor 18-10 through the wireless channel.

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

The processor 18-10 may control a series of processes so that the base station may operate in accordance with the embodiments described above. For example, the processor 18-10 may configure two-layer DCI including allocation information of multiple PDSCHs and control each component of the base station to transmit them. There may be multiple processors 18-10 and the processors 18-10 may perform component control operations of the base station by executing programs stored in the memory 18-05.

The methods disclosed in the claims and/or the methods according to the various embodiments described in the specification of the present disclosure may be implemented by hardware, software, or a combination of hardware and software.

When the methods are implemented by software, a computer-readable storage medium for storing one or more programs (software modules) may be provided. One or more programs stored in the computer-readable storage medium may be configured to be executed by one or more processors within the electronic device. The at least one program may include instructions for causing the electronic device to perform methods in accordance with various embodiments of the present disclosure as defined by the appended claims and/or disclosed herein.

The program (software module or software) may be stored in a non-volatile memory (including random access memory and flash memory, Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), magnetic disk storage devices, optical disks (CD-ROM), Digital Versatile Disks (DVD), or other types of optical storage devices or tapes). Alternatively, any combination of some or all of them may form a memory storing a program. Further, a plurality of such memories may be included in the electronic device.

Further, the program may be stored in an attachable Storage device that can access the electronic device through a communication Network such as the internet, an intranet, a Local Area Network (LAN), a Wide Area Network (WLAN), and a Storage Area Network (SAN), or a combination thereof. Such a storage device may access the electronic device through an external port. In addition, a separate storage device on the communication network may access the portable electronic device.

In the above detailed embodiments of the present disclosure, elements included in the present disclosure are expressed in singular or plural according to the presented detailed embodiments. However, the singular or plural forms are appropriately selected to the presented case for convenience of description, and the present disclosure is not limited by the elements expressed in the singular or plural forms. Thus, elements in the plural may also comprise a single element, or elements in the singular may also comprise a plurality of elements.

The embodiments of the present disclosure described and illustrated in the specification and drawings are for easily explaining technical contents of the present disclosure and assisting understanding of the present disclosure, and are not intended to limit the scope of the present disclosure. That is, other modifications and changes may be apparent to those skilled in the art based on the technical spirit of the present disclosure. Further, the above-described respective embodiments may be used in combination as necessary. For example,

embodiments

1 and 2 of the present disclosure may be partially combined to operate a base station and a terminal. Further, although the above embodiments have been described by the FDD LTE system, other variations based on the technical idea of the embodiments may be implemented in other systems (such as TDD LTE, 5G, and NR systems).

In the drawings describing the methods of the present disclosure, the order described does not always correspond to the order in which the steps of each method are performed, and the order relationship between the steps may be changed or the steps may be performed in parallel.

Alternatively, in the drawings describing the method of the present disclosure, some elements may be omitted and only some of them may be included without departing from the true spirit and scope of the present disclosure.

While the present disclosure has been described with various embodiments, various changes and modifications may be suggested to one skilled in the art. The present disclosure is intended to embrace such alterations and modifications as fall within the scope of the appended claims.

Size of bandwidth part

Configuration

Configuration 2

1. A method performed by a terminal in a wireless communication system, the method comprising:

receiving configuration information from a base station, the configuration information comprising information on at least one number of repetitions and information on at least one transmission timing of a hybrid automatic repeat request, HARQ, feedback transmission;

receiving downlink control information, DCI, from the base station, the 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 number of repetitions indicated by the DCI; and

transmitting HARQ feedback to the base station 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 a slot among the plurality of second slots except for a slot determined based on the transmission timing indicated by the DCI.

2. The method of claim 1, wherein transmitting the HARQ feedback further comprises transmitting an ACK in a slot among the second slots if data is successfully received.

3. The method of claim 1, wherein the number of the at least one transmission timing is configured to be at most 8, and

wherein the configuration information is received through radio resource control, RRC, signaling.

4. The method of claim 1, wherein the configuration information comprises information regarding a starting symbol and a number of symbols of the first slot.

5. A method performed by a base station in a wireless communication system, the method comprising:

transmitting configuration information to a terminal, the configuration information including information on at least one number of repetitions and information on at least one transmission timing of a hybrid automatic repeat request, HARQ, feedback transmission;

transmitting downlink control information, DCI, to the terminal, the 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 number of repetitions indicated by the DCI; and

receiving HARQ feedback from the terminal in a plurality of second slots determined based on the plurality of first slots,

6. The method of claim 5, wherein an ACK is received in a slot among the second slots in case of successful transmission of data.

7. The method according to claim 5, wherein the number of the at least one transmission timing is configured to be at most 8, and

wherein the configuration information is transmitted by radio resource control, RRC, signaling.

8. The method of claim 5, wherein the configuration information comprises information regarding a starting symbol and a number of symbols of the first slot.

9. A terminal in a wireless communication system, the terminal comprising:

a transceiver; and

a controller coupled with the transceiver and configured to:

transmitting HARQ feedback to the base station in a plurality of second time slots determined based on the plurality of first time slots,

10. The terminal of claim 9, wherein the controller transmits an ACK in a slot among the second slots in case of successful reception of data.

11. The terminal according to claim 9, wherein the number of the at least one transmission timing is configured to be at most 8, and

12. The terminal of claim 9, wherein the configuration information includes information on a starting symbol and a number of symbols of the first slot.

13. A base station in a wireless communication system, the base station comprising:

a transceiver; and

a controller configured to:

14. The base station of claim 13, wherein an ACK is received in a slot among the second slots on a successful transmission of data.

15. The base station according to claim 13, wherein the number of the at least one transmission timing is configured to be at most 8,

wherein the configuration information is received through radio resource control, RRC, signaling, and

wherein the configuration information includes information on a start symbol and a number of symbols of the first slot.