Method and apparatus for transmitting uplink control information via multi-panel in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system supporting a higher data transmission rate. Specifically, the present disclosure provides a method and apparatus for performing an uplink transmission procedure in consideration of simultaneous transmission via multiple panels. A method and apparatus are provided in which first downlink control information (DCI) that schedules a first physical uplink shared channel (PUSCH) and second DCI that schedules a second PUSCH are received. The first PUSCH and the second PUSCH are simultaneous transmission across multiple panels (STxMP). A third DCI indicating a physical uplink control channel (PUCCH) that overlaps with the first PUSCH and the second PUSCH is received. A PUSCH associated with a control resource set (CORESET) pool index for the third DCI is identified from among the first PUSCH and the second PUSCH. Uplink control information (UCI) is transmitted by multiplexing the UCI in the identified PUSCH.

Description

Technical Field

[0001] The present disclosure generally relates to the operation of a terminal and a base station in a wireless communication system (or a mobile communication system), and more specifically, to a method for performing simultaneous uplink transmission using multiple panels in a wireless communication system, a method for correspondingly transmitting uplink control information, and a device capable of performing the method. Background Art

[0002] The fifth generation (5G) mobile communication technology defines a wide frequency band, making high transmission rates and new services possible, and can be implemented not only in "below 6 GHz" frequency bands such as 3.5 gigahertz (GHz), but also in "above 6 GHz" frequency bands called mmWave including 28 GHz and 39 GHz. In addition, the implementation of the sixth generation (6G) mobile communication technology (also called a super 5G system) in the terahertz (THz) frequency band (e.g., 95 GHz to 3 THz frequency band) has been considered to achieve a transmission rate that is fifty times that of the 5G mobile communication technology and an ultra-low latency that is one-tenth of the latency of the 5G mobile communication technology.

[0003] When 5G mobile communication technology is being developed, in order to support services and meet performance requirements for enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC) and massive machine type communication (mMTC), standardization is underway on the following items: beamforming and massive multiple-input multiple-output (MIMO) for reducing radio wave path loss and increasing radio wave transmission distance in mmWave, parameter sets supporting dynamic operations for efficiently utilizing mmWave resources and time slot formats (for example, operating multiple subcarrier spacings), initial access technology for supporting multi-beam transmission and broadband, definition and operation of bandwidth parts (BWP), new channel coding methods such as low-density parity-check (LDPC) codes for large-scale data transmission and polarization codes for highly reliable transmission of control information, layer 2 (L2) preprocessing, and network slicing for providing dedicated networks dedicated to specific services.

[0004] In view of the services to be supported by 5G mobile communication technology, improvements and performance enhancements of initial 5G mobile communication technology are being conducted. Physical layer standardization has been conducted on technologies such as Vehicle-to-Everything (V2X) for assisting autonomous vehicles in making driving decisions based on information about the location and status of the vehicle sent by the vehicle and enhancing user convenience, Unlicensed New Radio (NR-U) for the purpose of making system operations comply with various regulatory-related requirements in unlicensed bands, New Radio (NR) User Equipment (UE) power saving, Non-Terrestrial Network (NTN) as UE-satellite direct communication for providing coverage in areas where communication with terrestrial networks is not available, and positioning.

[0005] In addition, standardization has been carried out on the air interface architecture / protocol aspects of technologies such as the Industrial Internet of Things (IIoT) for supporting new services through interworking and integration with other industries, Integrated Access and Backhaul (IAB) for providing nodes for network service area extension by supporting wireless backhaul links and access links in an integrated manner, mobility enhancement including conditional switching and dual active protocol stack (DAPS) switching, and two-step random access (2-step random access channel (RACH) for NR) for simplifying the random access process. Standardization has also been carried out on the system architecture / service aspects of the following items: 5G baseline architecture (e.g., service-based architecture or service-based interface) for combining network function virtualization (NFV) and software defined network (SDN) technologies, and mobile edge computing (MEC) for receiving services based on UE location.

[0006] As 5G mobile communication systems are commercialized, the number of connected devices, which has been increasing exponentially, will be connected to the communication network, and it is expected that enhanced functions and performance of the 5G mobile communication systems and integrated operations of the connected devices will be necessary. To this end, new research is expected on the following items: extended reality (XR) for efficiently supporting augmented reality (AR), virtual reality (VR), mixed reality (MR), etc., 5G performance improvement and complexity reduction using artificial intelligence (AI) and machine learning (ML), AI service support, metaverse service support, and drone communication.

[0007] In addition, such development of 5G mobile communication systems will serve as the basis for not only developing new waveforms for providing coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as full-dimensional MIMO (FD-MIMO), array antennas and massive antennas, metamaterial-based lenses and antennas for improving the coverage of terahertz band signals, and high-dimensional spatial multiplexing technology using orbital angular momentum (OAM) and reconfigurable smart surfaces (RIS), but also developing full-duplex technology for improving the frequency efficiency of 6G mobile communication technology and improving system networks, AI-based communication technology for achieving system optimization from the design stage by utilizing satellites and AI and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at a complexity level that exceeds the limits of UE operating capabilities by utilizing ultra-high performance communication and computing resources.

[0008] As communication systems develop, research into uplink transmission or reception using a plurality of panels is being conducted, and in particular, demand for improving uplink control information transmission using a plurality of panels is increasing. Summary of the invention

[0009] Solution to the problem

[0010] The embodiment provides an apparatus and method capable of efficiently providing a service in a mobile communication system. The embodiment provides a method for simultaneously transmitting a plurality of uplink channels by using a plurality of panels in a wireless communication system and an apparatus for performing the method.

[0011] According to an embodiment, a method performed by a terminal in a wireless communication system is provided. The method includes: receiving a first downlink control information (DCI); identifying a first physical uplink shared channel (PUSCH) based on the first DCI; receiving a second DCI; identifying a second PUSCH based on the second DCI; receiving a third DCI; identifying a physical uplink control channel (PUCCH) for hybrid automatic repeat request acknowledgment (HARQ-ACK) information based on the third DCI, wherein the PUCCH overlaps with the first PUSCH and the second PUSCH; and in the case where simultaneous transmission across multiple panels (STxMP) is enabled, identifying a PUSCH for multiplexing uplink control information (UCI) including the HARQ-ACK information among the first PUSCH and the second PUSCH, wherein the PUSCH and the PUCCH are associated with the same control resource set (CORESET).

[0012] According to an embodiment, a method performed by a base station in a wireless communication system is provided. The method includes: sending a first downlink control information (DCI) for a first physical uplink shared channel (PUSCH); sending a second DCI for a second PUSCH; sending a third DCI for a physical uplink control channel (PUCCH) for hybrid automatic repeat request acknowledgement (HARQ-ACK) information, wherein the PUCCH overlaps with the first PUSCH and the second PUSCH; and receiving the PUSCH to which the uplink control information (UCI) including the HARQ-ACK information is multiplexed among the first PUSCH and the second PUSCH when simultaneous transmission across multiple panels (STxMP) is enabled, wherein the PUSCH and the PUCCH are associated with the same control resource set (CORESET).

[0013] According to an embodiment, a terminal in a wireless communication system is provided. The terminal includes a transceiver and a controller coupled to the transceiver. The controller is configured to: receive a first downlink control information (DCI); identify a first physical uplink shared channel (PUSCH) based on the first DCI; receive a second DCI; identify a second PUSCH based on the second DCI; receive a third DCI; identify a physical uplink control channel (PUCCH) for hybrid automatic repeat request confirmation (HARQ-ACK) information based on the third DCI, wherein the PUCCH overlaps with the first PUSCH and the second PUSCH; and when simultaneous transmission across multiple panels (STxMP) is enabled, identify the PUSCH for multiplexing uplink control information (UCI) including the HARQ-ACK information among the first PUSCH and the second PUSCH, wherein the PUSCH and the PUCCH are associated with the same control resource set (CORESET).

[0014] According to an embodiment, a base station in a wireless communication system is provided. The base station includes a transceiver and a controller coupled to the transceiver. The controller is configured to: send a first downlink control information (DCI) for a first physical uplink shared channel (PUSCH); send a second DCI for a second PUSCH; send a third DCI for a physical uplink control channel (PUCCH) for hybrid automatic repeat request confirmation (HARQ-ACK) information, wherein the PUCCH overlaps with the first PUSCH and the second PUSCH; and receive the PUSCH to which the uplink control information (UCI) including the HARQ-ACK information is multiplexed among the first PUSCH and the second PUSCH when simultaneous transmission across multiple panels (STxMP) is enabled, wherein the PUSCH and the PUCCH are associated with the same control resource set (CORESET). BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The above and other aspects, features and advantages of the present disclosure will become more apparent from the following description taken in conjunction with the accompanying drawings, in which:

[0016] Figure 1 is a diagram illustrating a basic structure of a time-frequency domain in a wireless communication system according to an embodiment;

[0017] Figure 2 is a diagram illustrating a frame, a subframe, and a slot structure in a wireless communication system according to an embodiment;

[0018] Figure 3 is a diagram illustrating an example of a BWP configuration in a wireless communication system according to an embodiment;

[0019] Figure 4 A diagram illustrating an example of base station beam assignment according to a transmission configuration indicator (TCI) state configuration in a wireless communication system according to an embodiment is shown;

[0020] Figure 5 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 is shown;

[0021] Figure 6 is a diagram illustrating an example of time axis resource allocation of a PDSCH in a wireless communication system according to an embodiment;

[0022] Figure 7 illustrates the process of beam configuration and activation for PDSCH;

[0023] Figure 8is a diagram illustrating an example of a medium access control (MAC) control element (CE) for activation based on a spatial relationship of a PUCCH resource group in a wireless communication system according to an embodiment;

[0024] Fig. 9 is a diagram illustrating an example of PUSCH repetition transmission type B in a wireless communication system according to an embodiment;

[0025] Fig.10 is a diagram illustrating a radio protocol structure of a terminal and a base station in a wireless communication system according to an embodiment in a single cell, carrier aggregation, and dual connectivity scenario;

[0026] Fig.11 A diagram illustrating an example of antenna port configuration and resource allocation for cooperative communication in a wireless communication system according to an embodiment is shown;

[0027] Fig.12 A diagram illustrating an example of a DCI configuration for cooperative communication in a wireless communication system according to an embodiment is shown;

[0028] Fig.13 is a diagram illustrating an enhanced PDSCH TCI state activation / deactivation MAC-CE structure;

[0029] Fig.14 is a diagram illustrating a radio link monitoring (RLM) reference signal (RS) selection process according to an embodiment;

[0030] Fig.15 is a diagram illustrating a MAC-CE structure for activation and indication of a joint TCI state in a wireless communication system according to an embodiment;

[0031] Fig.16 is a diagram illustrating another MAC-CE structure for activation and indication of a joint TCI state in a wireless communication system according to an embodiment;

[0032] Fig.17 is a diagram illustrating another MAC-CE structure for activation and indication of a joint TCI state in a wireless communication system according to an embodiment;

[0033] Fig.18 is a diagram illustrating a MAC-CE structure for activation and indication of a separate TCI state in a wireless communication system according to an embodiment;

[0034] Fig.19 is a diagram illustrating another MAC-CE structure for activation and indication of a separate TCI state in a wireless communication system according to an embodiment;

[0035] Fig. 20is a diagram illustrating another MAC-CE structure for activation and indication of a separate TCI state in a wireless communication system according to an embodiment;

[0036] Fig.21 is a diagram illustrating another MAC-CE structure for activation and indication of a separate TCI state in a wireless communication system according to an embodiment;

[0037] Fig. 22 is a diagram illustrating a MAC-CE structure for joint and individual TCI state activation and indication in a wireless communication system according to an embodiment;

[0038] Fig.23 is a diagram illustrating another MAC-CE structure for joint and individual TCI state activation and indication in a wireless communication system according to an embodiment;

[0039] Fig.24 is a diagram for beam application time that may be considered when an integrated TCI scheme is used in a wireless communication system according to an embodiment;

[0040] Fig.25 is a diagram illustrating a MAC-CE structure for activation and indication of multiple joint TCI states in a wireless communication system according to an embodiment;

[0041] Fig.26 is a diagram illustrating a MAC-CE structure for activation and indication of multiple individual TCI states in a wireless communication system according to an embodiment;

[0042] Fig. 27 is a diagram illustrating another MAC-CE structure for activation and indication of multiple individual TCI states in a wireless communication system according to an embodiment;

[0043] Fig.28 A diagram illustrating a panel for resource allocation and transmission for uplink transmission in frequency division multiplexing (FDM), space division multiplexing (SDM) and single frequency network (SFN) schemes to support simultaneous transmission with multiple panels or STxMPs is shown;

[0044] Fig.29 An example of multiplexing UCI in FDM-based and SDM-based STxMP transmission scenarios is illustrated;

[0045] Fig.30 A diagram illustrating an example of PUSCHs simultaneously transmitted through multiple panels scheduled via multi-DCI (mDCI) or single DCI (sDCI) and an example of overlap of scheduled PUSCHs and PUCCHs in the time domain is shown;

[0046] Fig.31is a diagram illustrating a structure of a terminal in a wireless communication system according to an embodiment;

[0047] Fig.32 is a diagram illustrating a structure of a base station in a wireless communication system according to an embodiment. DETAILED DESCRIPTION

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

[0049] When describing each embodiment, description 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 idea of ​​the present disclosure from being obfuscated and to convey the main idea more clearly.

[0050] For the same reason, in the accompanying drawings, some elements may be exaggerated, omitted or schematically illustrated. In addition, the size of each element does not fully reflect the actual size. In the accompanying drawings, the same or corresponding elements are provided with the same reference numerals.

[0051] By referring to the embodiments described in detail below in conjunction with the accompanying drawings, the advantages and features of the present disclosure and the means for realizing them will be clear. However, the present disclosure is not limited to the embodiments set forth below, but can be implemented in various different forms. The following embodiments are only provided to fully disclose the present disclosure and inform the scope of the present disclosure to those skilled in the art, and the present disclosure is limited only by the scope of the appended claims. The terms to be described below are defined in the context of the functions in the present disclosure, and may be different depending on the user, the user's intention or custom. Therefore, the definition of the terms should be made based on the content throughout this specification.

[0052] In this article, it should be understood that each box of the flowchart diagram and the combination of boxes in the flowchart diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer or other programmable data processing device to produce a machine, so that the instructions run by the processor of the computer or other programmable data processing device create a means for implementing the functions specified in one or more flowchart boxes. These computer program instructions can also be stored in a computer-usable or computer-readable memory, which can instruct a computer or other programmable data processing device to act in a specific way, so that the instructions stored in the computer-usable or computer-readable memory produce a product including an instruction means for implementing the functions specified in one or more flowchart boxes. Computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are performed on the computer or other programmable device to produce a computer-implemented process, so that the instructions running on the computer or other programmable device provide steps for implementing the functions specified in one or more flowchart boxes.

[0053] In addition, each box of the flowchart diagram can represent a module, segment or part of a code, which includes one or more executable instructions for implementing the specified (one or more) logical functions. It should also be noted that in some alternative implementations, the functions indicated in the box may not occur in order. For example, depending on the functions involved, two boxes shown in succession can actually be run substantially concurrently, or each box can sometimes be run in reverse order.

[0054] As used herein, the term "unit" refers to a software element or hardware element that performs a predetermined function, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). However, the term "unit" does not always have a meaning limited to software or hardware. A unit can be constructed to be stored in an addressable storage medium or to run one or more processors. Therefore, a unit includes, for example, software elements, object-oriented software elements, class elements or task elements, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcodes, circuits, data, databases, data structures, tables, arrays, and parameters. The elements and functions provided by the unit can be combined into a smaller number of elements or units, or divided into a larger number of elements or units. In addition, elements and units can be implemented to reproduce one or more CPUs in a device or a secure multimedia card. In addition, a unit can include one or more processors.

[0055] Wireless communication systems are advancing to broadband wireless communication systems for providing high-speed, high-quality packet data services as well as typical voice-based services using communication standards such as: 3GPP's High Speed ​​Packet Access (HSPA), Long Term Evolution (LTE) (or Evolved Universal Terrestrial Radio Access (E-UTRA)), Advanced LTE (LTE-A), LTE-Pro, 3GPP2's High Rate Packet Data (HRPD), Ultra Mobile Broadband (UMB), IEEE 802.16e, etc.

[0056] As a typical example of a broadband wireless communication system, the LTE system adopts an orthogonal frequency division multiplexing (OFDM) scheme in a downlink (DL) and a single carrier frequency division multiple access (SC-FDMA) scheme in an uplink (UL). The uplink indicates a wireless link by which a UE (or a mobile station (MS)) sends data or a control signal to a base station (BS) (eNode B), and the downlink indicates a wireless link by which a base station sends data or a control signal to a UE. The above-mentioned multiple access scheme can separate the data or control information of each user by allocating and operating time-frequency resources for sending data or control information for each user so as to avoid overlapping with each other (i.e., in order to establish orthogonality).

[0057] Since the 5G communication system as a post-LTE communication system must freely reflect various requirements of users, service providers, etc., it is necessary to support services that meet various requirements. Services considered in the 5G communication system include eMBB communication, mMTC, URLLC, etc.

[0058] eMBB aims to provide a higher data rate than that supported by existing LTE, LTE-A or LTE-Pro. For example, in a 5G communication system, eMBB must provide a peak data rate of 20Gbps in the downlink and a peak data rate of 10Gbps in the uplink for a single base station. In addition, the 5G communication system must provide an increased user-perceived data rate and a maximum data rate to the UE. In order to meet such requirements, improvements are required in the transmission / reception technology including further enhanced multiple-input multiple-output (MIMO) transmission technology. In addition, the data rate required by the 5G communication system can be obtained using a frequency bandwidth of more than 20MHz in a frequency band of 3 to 6GHz or above 6GHz, rather than using a transmission bandwidth of up to 20MHz to send signals in the 2GHz band used in LTE.

[0059] In addition, mMTC is being considered to support application services such as the Internet of Things (IoT) in the 5G communication system. In order to efficiently provide the Internet of Things (IoT), mMTC has requirements for supporting the connection of a large number of UEs in a cell, enhancing the coverage of the UE, improving the battery time, reducing the cost of the UE, etc. Since IoT provides communication functions when it is provided to various sensors and various devices, it must support a large number of UEs (e.g., 1,000,000 UEs / km2) in a cell. In addition, because the UE is likely to be located in a shadow area (such as a basement of a building) that is not covered by the cell due to the nature of the service, the UE supporting mMTC may require a wider coverage than those of other services provided by the 5G communication system. Because it is difficult to frequently replace the battery of the UE, the UE supporting mMTC must be configured to be cheap and may require a very long battery life such as 10 to 15 years.

[0060] Finally, URLLC, as a cellular-based mission-critical wireless communication service, can be used for remote control of robots or machines, industrial automation, unmanned aerial vehicles, remote health care, emergency alerts, etc. Therefore, URLLC must provide communications with ultra-low latency and ultra-high reliability. For example, services supporting URLLC must meet an air interface latency of less than 0.5ms, and also require a packet error rate of 10-5 or less. Therefore, for services supporting URLLC, the 5G system must provide a shorter TTI than other services, and may also require a design for allocating a large amount of resources in the frequency band to ensure the reliability of the communication link.

[0061] Three 5G services, namely eMBB, URLLC and mMTC, can be multiplexed and transmitted in a single system. In this case, different transmission / reception technologies and transmission / reception parameters can be used between the services to meet the different requirements of the corresponding services. Of course, 5G is not limited to the above three services.

[0062] In the following description, a base station is an entity that allocates resources to a terminal, and may be at least one of a gNode B, an eNode B, a Node B, a BS, a wireless access unit, a base station controller, and a node on a network. The terminal may include a UE, an MS, a cellular phone, a smart phone, a computer, or a multimedia system capable of performing a communication function. In this article, "downlink (DL)" refers to a wireless link by which a base station sends a signal to a terminal, and "uplink (UL)" refers to a wireless link by which a terminal sends a signal to a base station. In addition, an LTE or LTE-A system may be described as an example, but the embodiments of the present disclosure may also be applicable to other communication systems with similar technical backgrounds or channel types. Examples of such communication systems may include fifth-generation mobile communication technologies (5G, new wireless, and NR) developed outside of LTE-A, and in the following description, "5G" may be a concept covering existing LTE, LTE-A, or other similar services. In addition, based on determinations made by those skilled in the art, the embodiments of the present disclosure may also be applied to other communication systems with some modifications without significantly departing from the scope of the present disclosure.

[0063] NR time and frequency resources

[0064] Hereinafter, the frame structure of the 5G system is described in more detail with reference to the accompanying drawings.

[0065] Figure 1 It is a diagram illustrating the basic structure of the time-frequency domain as a wireless resource area for sending data or control channels in the 5G system.

[0066] exist Figure 1 In FIG. 1 , the horizontal axis represents the time domain, and the vertical axis represents the frequency domain. The basic unit of resources in the time domain and the frequency domain is a resource element (RE) 101, and can be defined as 1 OFDM symbol 102 on the time axis and 1 subcarrier 103 on the frequency axis. In the frequency domain, (For example, 12) consecutive REs may constitute one resource block (RB) 104. One subframe 110 on the time axis may include a plurality of OFDM symbols 102. For example, the length of one subframe may be 1 ms.

[0067] Figure 2 is a diagram illustrating a frame, a subframe, and a slot structure in a wireless communication system according to an embodiment.

[0068] Figure 2An example of a frame 200, a subframe 201, and a time slot 202 structure is illustrated. One frame 200 may be defined as 10 ms. One subframe 201 may be defined as 1 ms, and thus one frame 200 may include a total of 10 subframes 201. One time slot 202 or 203 may be defined as 14 OFDM symbols (that is, the number of symbols per time slot). ). A subframe 201 may include one or more time slots 202 and 203, and the number of time slots 202 and 203 per subframe 201 may vary according to a configuration value μ 204 or 205 for the subcarrier spacing. Figure 2 The example illustrates a case 204 of μ=0 and a case 205 of μ=1, where μ is a subcarrier spacing configuration value. In the case 204 of μ=0, one subframe 201 may include one time slot 202, while in the case 205 of μ=1, one subframe 201 may include two time slots 203. That is, the number of time slots per subframe is can vary according to the configured value μ for the subcarrier spacing and, therefore, the number of slots per frame The values ​​of μ according to the corresponding subcarrier spacing configuration value μ can be defined in Table 1 below: and

[0069] [Table 1]

[0070]

[0071] Bandwidth Part (BWP)

[0072] The BWP configuration in the 5G communication system is described in more detail below with reference to the accompanying drawings.

[0073] Figure 3 is a diagram illustrating an example of a BWP configuration in a wireless communication system according to an embodiment.

[0074] Figure 3 An example is shown in which a terminal bandwidth (UE bandwidth) 300 is configured to have two BWPs, namely, BWP#1 301 and BWP#2 302. The base station may configure one or more BWPs for the terminal, and may configure information for each BWP, as shown in Table 2 below.

[0075] [Table 2]

[0076]

[0077] The present disclosure is not limited to the above examples, and in addition to the configuration information, various parameters related to the BWP may be configured for the terminal. The base station may transmit information to the terminal via higher layer signaling (e.g., radio resource control (RRC) signaling). At least one of the configured one or more BWPs may be activated. Whether the configured bandwidth is activated may be semi-statically transmitted via RRC signaling or may be dynamically sent from the base station to the terminal via DCI.

[0078] According to some embodiments, the base station may configure the initial BWP for the terminal for initial access before RRC connection via the master information block (MIB). More specifically, during the initial access, the terminal may receive configuration information for the search space and the control region (CORESET), in which the PDCCH for receiving the system information required for the initial access (which may correspond to the rest of the system information (RMSI) or the system information block 1 (SIB1)) may be sent via the MIB. Each of the search space and the control region configured via the MIB may be considered as an identifier (identification (ID)) 0. The base station may notify the terminal of configuration information such as frequency allocation information, time allocation information and parameter set (numerology) for the control region #0 via the MIB. In addition, the base station may notify the terminal of the configuration information of the listening period and listening opportunity for the control region #0, i.e., the configuration information for the search space #0, via the MIB. The terminal may regard the frequency domain configured as the control region #0 obtained from the MIB as the initial BWP for initial access. In this case, the identification (ID) of the initial BWP may be considered as 0.

[0079] The BWP configuration supported by 5G can be used for various purposes.

[0080] If the bandwidth supported by the terminal is less than the system bandwidth, this can be supported via BWP configuration. For example, the base station can configure the frequency position of the BWP for the terminal (configuration information 2), and the terminal can therefore send or receive data at a specific frequency position within the system bandwidth.

[0081] For the purpose of supporting different parameter sets, the base station can configure multiple BWPs for the terminal. For example, in order to support data transmission or reception using both a subcarrier spacing of 15kHz and a subcarrier spacing of 30kHz for a certain terminal, the base station can configure two BWPs with subcarrier spacings of 15kHz and 30kHz, respectively. Different BWPs can be FDMed, and when data is to be sent or received at a specific subcarrier spacing, the BWP configured with the subcarrier spacing can be activated.

[0082] For the purpose of reducing the power consumption of the terminal, the base station can configure a BWP with different bandwidth sizes for the terminal. For example, if the terminal supports a very large bandwidth, such as a bandwidth of 100 MHz, and always sends or receives data via the corresponding bandwidth, very large power consumption may occur. In particular, in the case of no business, performing unnecessary monitoring for a downlink control channel with a large bandwidth of 100 MHz may be very inefficient in terms of power consumption. For the purpose of reducing the power consumption of the terminal, the base station can configure a BWP with a relatively small bandwidth, such as a BWP of 20 MHz, for the terminal. In the case of no business, the terminal can perform monitoring in a BWP of 20 MHz, and when data is generated, the terminal can use a BWP of 100 MHz to send or receive data according to the instructions of the base station.

[0083] In the method of BWP configuration, the terminal may receive configuration information for the initial BWP via the MIB during initial access before the RRC connection. More specifically, the terminal may be configured with a control region (i.e., CORESET) for a downlink control channel from the MIB of the physical broadcast channel (PBCH), through which the DCI for scheduling the SIB may be sent. The bandwidth of the control region configured via the MIB may be considered as the initial BWP, and the terminal may receive the PDSCH through which the SIB is sent via the configured initial BWP. In addition to the reception of the SIB, the initial BWP may also be used for other system information (OSI), paging, and random access.

[0084] Changes to BWP

[0085] When one or more BWPs are configured for a terminal, the base station may instruct the terminal to change (or switch or shift) the BWP by using the BWP indicator field in the DCI. Figure 3 In the present invention, if the current active BWP of the terminal is BWP#1 301, the base station may indicate BWP#2 302 to the terminal by using the BWP indicator in the DCI, and the terminal may switch the BWP to BWP#2 302 indicated by the BWP indicator in the received DCI.

[0086] As described above, the DCI-based switching of the BWP may be indicated by the DCI for scheduling the PDSCH or PUSCH, and therefore when receiving a request to switch the BWP, the terminal may need to easily perform the transmission or reception of the PDSCH or PUSCH scheduled by the corresponding DCI in the switched BWP. For this purpose, in the standard, the requirement for the delay time (TBWP) required when switching the BWP is specified, and can be defined, for example, as shown in Table 3 below.

[0087] [Table 3]

[0088]

[0089] The requirement for the BWP switching delay time supports type 1 or type 2 according to the capability of the terminal. The terminal can report the supportable BWP delay time type to the base station.

[0090] According to the aforementioned requirements for the BWP switching delay time, when the terminal receives a DCI including a BWP switching indicator in time slot n, the terminal can complete the switch to the new BWP indicated by the BWP switching indicator at a time point no later than time slot n+TBWP, and can perform transmission or reception for the data channel scheduled by the corresponding DCI in the switched new BWP. When the base station is to schedule a data channel with a new BWP, the time domain resource allocation for the data channel can be determined by considering the BWP switching delay time (TBWP) of the terminal. That is, in the method for determining the time domain resource allocation for the data channel when the base station schedules the data channel with a new BWP, the scheduling of the data channel can be performed after the BWP switching delay time. Therefore, the terminal may not expect the DCI indicating the BWP switch to indicate a time slot offset (K0 or K2) value less than the TBWP.

[0091] If the terminal receives a DCI indicating a BWP switch (e.g., DCI format 1_1 or 0_1), the terminal may not perform any transmission or reception during a time interval from the third symbol of the time slot in which the PDCCH including the DCI is received to the start point of the time slot indicated by the time slot offset (K0 or K2) value indicated by the time domain resource allocation indicator field in the DCI. For example, when the terminal receives a DCI indicating a BWP switch in time slot n, and the time slot offset value indicated by the DCI is K, the terminal may not perform any transmission or reception from the third symbol of time slot n to the symbol before time slot n+K (i.e., the last symbol in time slot n+K-1).

[0092] PDCCH: Related to DCI

[0093] The following describes DCI in the 5G system in detail.

[0094] In the 5G system, scheduling information for uplink data (or physical uplink data channel (PUSCH)) or downlink data (or physical downlink data channel (PDSCH)) is transmitted from the base station to the terminal via DCI. The terminal can monitor the fallback DCI format and the non-fallback DCI format for PUSCH or PDSCH. The fallback DCI format may include a fixed field predefined between the base station and the terminal, while the non-fallback DCI format may include a configurable field.

[0095] DCI can be sent on a physical downlink control channel (PDCCH) via channel coding and modulation. A cyclic redundancy check (CRC) is attached to the DCI message payload and can be scrambled by a radio network temporary identifier (RNTI) corresponding to the identity of the terminal. Different RNTIs can be used according to the following purposes of the DCI message: for example, terminal-specific (UE-specific) data transmission, power control commands, random access responses, etc. In other words, the RNTI is not sent explicitly, but is included in the CRC calculation and sent. When a DCI message sent on the PDCCH is received, the terminal can use the assigned RNTI to check the CRC and can determine that the message is sent to the terminal if the CRC check result is correct.

[0096] For example, the DCI used to schedule PDSCH for system information (SI) may be scrambled by SI-RNTI. The DCI used to schedule PDSCH for random access response (RAR) message may be scrambled by RA-RNTI. The DCI used to schedule PDSCH for paging message may be scrambled by P-RNTI. The DCI used to notify the slot format indicator (SFI) may be scrambled by SFI-RNTI. The DCI used to notify the transmit power control (TPC) may be scrambled by TPC-RNTI. The DCI used to schedule UE-specific PDSCH or PUSCH may be scrambled by cell RNTI (C-RNTI).

[0097] DCI format 0_0 may be used as a fallback DCI for scheduling PUSCH, where the CRC is scrambled by the C-RNTI. DCI format 0_0 where the CRC is scrambled by the C-RNTI may include information such as the following Table 4.

[0098] [Table 4]

[0099]

[0100] DCI format 0_1 ​​may be used as a non-fallback DCI for scheduling a PUSCH, where the CRC is scrambled by the C-RNTI. The DCI format 0_1 ​​where the CRC is scrambled by the C-RNTI may include information such as the following Table 5.

[0101] [Table 5]

[0102]

[0103] DCI format 1_0 may be used as a fallback DCI for scheduling PDSCH, where the CRC is scrambled by the C-RNTI. DCI format 1_0 where the CRC is scrambled by the C-RNTI may include information such as the following Table 6.

[0104] [Table 6]

[0105]

[0106] DCI format 1_1 may be used as a non-fallback DCI for scheduling PDSCH, where the CRC is scrambled by the C-RNTI. DCI format 1_1 where the CRC is scrambled by the C-RNTI may include information such as the following Table 7.

[0107] [Table 7]

[0108]

[0109]

[0110] QCL and TCI status

[0111] In a wireless communication system, one or more different antenna ports may be associated with each other through a quasi co-location (QCL) configuration as shown in Table 8 below, where different antenna ports can be replaced with one or more channels, signals, and combinations thereof, but in the description of the following disclosure, for convenience, different antenna ports are commonly referenced. The TCI state is used to notify the QCL relationship between a PDCCH (or PDCCH DMRS) and another RS ​​or channel, where a certain reference antenna port A (reference RS#A) and another target antenna port B (target RS#B) are QCL with each other, indicating that the terminal is allowed to apply some or all of the large-scale channel parameters estimated at antenna port A to the channel measurement results from antenna port B. For QCL, it may be necessary to associate different parameters according to the situation, such as 1) time tracking affected by average delay and delay spread, 2) frequency tracking affected by Doppler shift and Doppler spread, 3) radio resource management (RRM) affected by average gain, and 4) beam management (BM) affected by spatial parameters. Therefore, NR supports four types of QCL relationships as shown in Table 8 below.

[0112] [Table 8]

[0113] QCL Type Large-scale features A Doppler shift, Doppler spread, average delay, delay spread B Doppler shift, Doppler spread C Doppler shift, average delay D Space Rx parameters

[0114] Spatial RX parameters may refer to some or all of various parameters such as angle of arrival (AoA), power angular spectrum (PAS) of AoA, angle of departure (AoD), PAS of AoD, transmit / receive channel correlation, transmit / receive beamforming, and spatial channel correlation.

[0115] As shown in Table 9 below, the QCL relationship can be configured for the terminal via the RRC parameters TCI-State and QCL-Info. Referring to Table 9, the base station can configure one or more TCI states for the terminal so as to inform up to two QCL relationships (qcl-Type1 and qcl-Type2) for the RS (ie, the target RS) with reference to the ID of the TCI state. Each piece of QCL information (QCL-Info) included in each TCI state includes the serving cell index and BWP index of the reference RS indicated by the corresponding QCL information, the type and ID of the reference RS, and the QCL type, as shown in Table 13.

[0116] [Table 9]

[0117]

[0118] Figure 4 A diagram illustrating an example of base station beam allocation configured according to TCI status is shown.

[0119] Reference Figure 4 , the base station can transmit information about N different beams to the terminal via N different TCI states. Figure 4 As shown, N=3, the base station can associate the qcl-Type2 parameters included in the three TCI states 400, 405 and 410 with the CSI-RS or SSB corresponding to different beams and be configured as QCL type D so as to notify that the antenna ports involving different TCI states 400, 405 or 410 are associated with different spatial Rx parameters (i.e., different beams).

[0120] The following Tables 10 to 14 show valid TCI state configurations according to the target antenna port type.

[0121] Table 10 shows the valid TCI state configuration when the target antenna port is a CSI-RS (ie, TRS) for tracking. TRS refers to an NZP CSI-RS in which the repetition parameter is not configured and trs-Info is configured as true. Configuration No. 3 in Table 10 can be used for aperiodic TRS.

[0122] [Table 10]

[0123]

[0124] Table 11 shows the valid TCI state configuration when the target antenna port is a CSI-RS for CSI. The CSI-RS for CSI refers to an NZP CSI-RS in which a parameter indicating repetition (e.g., a repetition parameter) is not configured among the CSI-RS and trs-Info is not configured as true.

[0125] [Table 11]

[0126]

[0127] Table 12 shows the valid TCI state configuration when the target antenna port is a CSI-RS for beam management (BM) (the same as the CSI-RS for L1 RSRP reporting). The CSI-RS for BM refers to the NZP CSI-RS in which the repetition parameter is configured and has a value of On or Off and trs-Info is not configured as true.

[0128] [Table 12]

[0129]

[0130] Table 13 shows the valid TCI state configuration when the target antenna port is PDCCH DMRS.

[0131] [Table 13]

[0132]

[0133] Table 14 shows the valid TCI state configuration when the target antenna port is PDCCH DMRS.

[0134] [Table 14]

[0135]

[0136] In the typical QCL configuration method according to Tables 10 to 14, the target antenna port and the reference antenna port for each operation are configured and operated as in "SSB"->"TRS"->"CSI-RS for CSI, CSI-RS for BM, PDCCH DMRS, or PDSCH DMRS". Based on this, the reception operation of the terminal can be assisted by associating statistical characteristics measurable from the SSB and TRS with the corresponding antenna port.

[0137] PDSCH: related to frequency resource allocation

[0138] Figure 5is a diagram illustrating an example of frequency-axis resource allocation of a PDSCH in a wireless communication system according to an embodiment.

[0139] Figure 5 The diagram illustrates three frequency axis resource allocation methods of type 0 500, type 1 505, and dynamic switching 510 configurable via a higher layer in an NR wireless communication system.

[0140] Reference Figure 5 , if the terminal is configured 500 via higher layer signaling to use only resource type 0, the DCI for allocating PDSCH to the terminal includes a bitmap with N_RBG bits. The conditions for this are described in more detail below. In this case, N_RBG refers to the number of resource block groups (RBGs) determined according to the BWP size assigned by the BWP indicator and the higher layer parameter rbg-Size as shown in Table 15 below, and data is sent to the RBG indicated by the bitmap as 1.

[0141] [Table 15]

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

[0143] If the terminal is configured 505 via higher layer signaling to use only resource type 1, a certain DCI for allocating PDSCH to the terminal includes The base station may configure the starting VRB 520 and the length 525 of the frequency axis resources continuously allocated therefrom.

[0144] If the terminal is configured 510 to use both resource type 0 and resource type 1 via higher layer signaling, a certain DCI for assigning PDSCH to the terminal includes frequency axis resource allocation information, which includes a bit of a larger value 535 among payloads 520 and 525 for configuring resource type 1 and payload 515 for configuring resource type 0. The conditions for this are described in more detail below. In this case, a bit 530 can be added to the first part (MSB) of the frequency axis resource allocation information in the DCI, and if the bit 530 has a value of "0", the use of resource type 0 can be indicated, and if the bit has a value of "1", the use of resource type 1 can be indicated.

[0145] PDSCH / PUSCH: related to time resource allocation

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

[0147] The base station can configure a table of time domain resource allocation information about a downlink data channel (PDSCH) and an uplink data channel (PUSCH) for the terminal via higher layer signaling (e.g., RRC signaling). A table including up to 16 entries (maxNrofDL-Allocations=16) can be configured for PDSCH, and a table including up to 16 entries (maxNrofUL-Allocations=16) can be configured for PUSCH. The time domain resource allocation information may include PDCCH to PDSCH slot timing (expressed as K0, and corresponding to the time point in which the PDCCH is received and the time point in which the PDSCH scheduled by the received PDCCH is sent, in units of time slots), PDCCH to PUSCH slot timing (expressed as K2, and corresponding to the time point in which the PDCCH is received and the time point in which the PUSCH scheduled by the received PDCCH is sent, in units of time slots), information about the position and length of the starting symbol for scheduling PDSCH or PUSCH in a slot, mapping type of PDSCH or PUSCH, etc. For example, information shown in the following Table 16 or Table 17 may be sent from the base station to the terminal.

[0148] [Table 16]

[0149]

[0150] [Table 17]

[0151]

[0152] The base station may notify the terminal via L1 signaling (e.g., DCI) of one of the entries in the table related to the above-mentioned time domain resource allocation information (e.g., the entry may be indicated by the "time domain resource allocation" field in the DCI). The terminal may obtain the time domain resource allocation information for the PDSCH or PUSCH based on the DCI received from the base station.

[0153] Figure 6 is a diagram illustrating an example of time axis resource allocation of a PDSCH in a wireless communication system according to an embodiment.

[0154] refer to Figure 6 The base station can indicate the time axis position of the PDSCH resource based on the starting position 600 and length 605 of the OFDM symbol in a time slot dynamically indicated via DCI, the scheduling offset K0 value, and the subcarrier spacing (SCS) (μPDSCH, μPDCCH) of the data channel and control channel configured using a higher layer.

[0155] PDSCH: TCI state activated MAC-CE

[0156] Figure 7 The process of beam configuration and activation for PDSCH is illustrated. At 700, a list of TCI states for PDSCH can be indicated via a higher layer list (such as RRC). The list of TCI states can be indicated, for example, by tci-StatesToAddModList and / or tci-StatesToReleaseList in the PDSCH-Config IE for each BWP. Next, at 720, some of the list of TCI states can be activated via MAC-CE. Among the TCI states activated via MAC-CE, at 740, the TCI state for PDSCH can be indicated via DCI. The maximum number of activated TCI states can be determined based on the capabilities reported by the terminal. 750 illustrates an example of a MAC-CE structure for PDSCH TCI state activation / deactivation.

[0157] The meaning of each field in the MAC CE and the configurable value for each field are as shown in Table 18 below.

[0158] [Table 18]

[0159]

[0160] PUCCH: related to transmission

[0161] In the NR system, the terminal may send control information (UCI) to the base station via the PUCCH. The control information may include at least one of HARQ-ACK indicating success or failure of demodulation / decoding of a transport block (TB) received by the terminal via the PDSCH, a scheduling request (SR) for requesting resource allocation from the PUSCH base station by the terminal for uplink data transmission, and channel state information (CSI) for reporting the channel state of the terminal.

[0162] PUCCH resources can be mainly divided into long PUCCH and short PUCCH according to the length of the assigned symbol. In the NR system, the length of long PUCCH in a time slot is 4 symbols or more, while the length of short PUCCH in a time slot is 2 symbols or less.

[0163] In more detail about the long PUCCH, the long PUCCH can be used for the purpose of improving uplink cell coverage and can therefore be transmitted in a DFT-S-OFDM scheme as a single carrier transmission rather than an 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 via Pre-DFT OCC support in the previous stage of IFFT.

[0164] First, PUCCH format 1 is a DFT-S-OFDM-based long PUCCH format capable of supporting up to 2 bits of control information and uses a frequency resource of 1 RB. The control information may include each of HARQ-ACK and 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 configured in a repeated manner.

[0165] For example, if the number of transmitted symbols of PUCCH format 1 is 8 symbols, then starting from the first starting symbol of the 8 symbols, it may include DMRS symbol, UCI symbol, DMRS symbol, UCI symbol, DMRS symbol, UCI symbol, DMRS symbol and UCI symbol in sequence. DMRS symbol may use an orthogonal code (or an orthogonal sequence or a spread code, w i (m)) is expanded into a sequence corresponding to the length of 1RB on the frequency axis within one OFDM symbol and is transmitted after performing IFFT.

[0166] For the UCI symbol, the terminal generates d(0) by BPSK modulating 1-bit control information and QPSK modulating 2-bit control information, multiplies the generated d(0) by a sequence corresponding to the length of 1RB on the frequency axis to perform scrambling, and performs scrambling using an orthogonal code (or an orthogonal sequence or a spread code, w) on the time axis. i (m)) is expanded into a scrambled sequence, IFFT is performed, and then transmission is performed.

[0167] The terminal generates a sequence based on the configured ID and the group hopping or sequence hopping configuration received from the base station via higher layer signaling, and generates a sequence corresponding to the length of 1RB by cyclically shifting the generated sequence using the initial cyclic shift (CS) value configured via higher layer signaling.

[0168] w i (m) is when the length of the spreading code (NSF) is given as in This is specifically shown in Table 19 below. i indicates the index of the extension code itself, and m indicates the index of the element of the extension code. Here, the numbers in [] in [Table 19] indicate For example, if the length of the spreading code is 2 and the index of the configured spreading code satisfies i=0, the spreading code w i (m) becomes and In order to satisfy w i (m) = [1 1].

[0169] [Table 19]

[0170] Spreading code for PUCCH format 1

[0171] Next, PUCCH format 3 is a DFT-S-OFDM-based long PUCCH format capable of supporting more than 2 bits of control information, and the number of RBs used is configurable via a higher layer. The control information may include each of HARQ-ACK, SR, and CSI or a combination thereof. In PUCCH format 3, the DMRS symbol position is presented in Table 20 below according to whether additional DMRS symbols are configured and whether frequency hopping is configured within a slot.

[0172] [Table 20]

[0173]

[0174] For example, if the number of transmission symbols of PUCCH format 3 is 8 symbols, DMRS is transmitted via the first symbol and the fifth symbol starting from the first start symbol 0 among the 8 symbols. Table 20 applies to the DMRS symbol position of PUCCH format 4 in the same manner.

[0175] Next, PUCCH format 4 is a DFT-S-OFDM-based long PUCCH format capable of supporting more than 2 bits of control information, and uses a frequency resource of 1RB. The control information may include each of HARQ-ACK, SR, and CSI or a combination thereof. The difference between PUCCH format 4 and PUCCH format 3 is that for PUCCH format 4, PUCCH format 4 of multiple terminals can be multiplexed within one RB. Multiplexing of PUCCH format 4 of multiple terminals is possible by applying Pre-DFT orthogonal cover code (OCC) to the control information in the previous stage of IFFT. However, the number of control information symbols that can be transmitted by one terminal is reduced according to the number of multiplexed terminals. The number of multiplexed terminals, that is, the number of different available OCCs, can be 2 or 4, and the number of OCCs and the OCC index to be applied can be configured via a higher layer.

[0176] The short PUCCH can be sent in both the downlink-centric time slot and the uplink-centric time slot, and in general, the short PUCCH can be sent at the last symbol or the OFDM symbol at the end of the time slot (for example, the last OFDM symbol, the second OFDM symbol from the last one, or the last 2 OFDM symbols at the end). Of course, the transmission of the short PUCCH at a random position in the time slot is also possible. The short PUCCH can be sent using one OFDM symbol or two OFDM symbols. The short PUCCH can be used to shorten the delay time in the case of good uplink cell coverage compared to the long PUCCH, and can be sent in the CP-OFDM scheme.

[0177] Short PUCCH can support transmission formats such as PUCCH format 0 and PUCCH format 2 according to the number of control information bits that can be supported. First, PUCCH format 0 is a short PUCCH format that can support up to 2 bits of control information and uses a frequency resource of 1RB. The control information may include each of HARQ-ACK and SR or a combination thereof. PUCCH format 0 has a structure that does not send DMRS and only sends a sequence of 12 subcarriers mapped to the frequency axis within one OFDM symbol. The terminal can generate a sequence based on the configured ID and the group hopping or sequence hopping configuration received from the base station via a higher layer, cyclically shift the generated sequence by using the final cyclic shift (CS) value obtained by adding different CS values ​​to the indicated initial CS value according to ACK or NACK, and map the cyclic shift sequence to 12 subcarriers for transmission.

[0178] For example, for a 1-bit HARQ-ACK, as shown in Table 21 below, if it is ACK, the terminal can generate the final CS by adding 6 to the initial CS value, and if it is NACK, the terminal can generate the final CS by adding 0 to the initial CS. The CS value of 0 for NACK and the CS value of 6 for ACK are defined in the standard, and the terminal can generate PUCCH format 0 according to the value defined in the standard to send a 1-bit HARQ-ACK.

[0179] [Table 21]

[0180] For example, if HARQ-ACK is 2 bits, as shown in Table 22 below, the terminal adds 0 to the initial CS value for (NACK, NACK), adds 3 to the initial CS value for (NACK, ACK), adds 6 to the initial CS value for (ACK, ACK), and adds 9 to the initial CS value for (ACK, NACK). A CS value of 0 for (NACK, NACK), a CS value of 3 for (NACK, ACK), a CS value of 6 for (ACK, ACK), and a CS value of 9 for (ACK, NACK) are defined in the standard, and the terminal can generate PUCCH format 0 according to the value defined in the standard to send a 2-bit HARQ-ACK. If the final CS value exceeds 12 due to the CS value added to the initial CS value according to ACK or NACK, since the sequence length is 12, modulo 12 can be applied to the final CS value.

[0181] [Table 22]

[0182]

[0183] Next, PUCCH format 2 is a short PUCCH format that supports more than 2 bits of control information, and the number of RBs used can be configured via a higher layer. The control information may include each of HARQ-ACK, SR, and CSI or a combination thereof. When the index of the first subcarrier is #0, in PUCCH format 2, the position of the subcarrier in which the DMRS is sent can be fixed to the subcarriers indexed as #1, #4, #7, and #10 within one OFDM symbol. The control information can be mapped to the subcarriers remaining after excluding the subcarrier where the DMRS is located via modulation after channel coding.

[0184] In summary, the configurable values ​​and ranges of the values ​​for the aforementioned corresponding PUCCH formats may be organized as shown in the following Table 23. In Table 23, the case where no configuration value is required is indicated as NA.

[0185] [Table 23]

[0186]

[0187]

[0188] 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. The terminal may repeatedly transmit PUCCH including UCI as many times as the number of slots configured via nrofSlots as higher layer signaling. For repeated PUCCH transmission, the PUCCH transmission in each slot may be performed using the same number of consecutive symbols, and the number of consecutive symbols may be configured via nrofSymbols as higher layer signaling in PUCCH format 1, PUCCH format 3, or PUCCH format 4. For repeated PUCCH transmission, the PUCCH transmission in each slot may be performed using the same starting symbol, and the starting symbol may be configured via startingSymbolIndex as higher layer signaling in PUCCH format 1, PUCCH format 3, or PUCCH format 4. For repeated PUCCH transmission, a single PUCCH-spatialRelationInfo may be configured for a single PUCCH resource. For repeated PUCCH transmission, if the terminal is configured to perform frequency hopping in PUCCH transmission in different time slots, the terminal can perform frequency hopping in units of time slots. In addition, if the terminal is configured to perform frequency hopping in PUCCH transmission in different time slots, the terminal can start PUCCH transmission in even time slots from the first PRB index configured via the startingPRB as a higher layer, and the terminal can start PUCCH transmission in odd time slots from the second PRB index configured via the secondHopPRB as a higher layer signaling. In addition, if the terminal is configured to perform frequency hopping in PUCCH transmission in different time slots, the index of the time slot indicated to the terminal for the first PUCCH transmission is 0, and during the configured total number of repeated PUCCH transmissions, the value of the number of repeated PUCCH transmissions can be increased in each time slot regardless of the execution of PUCCH transmission. If the terminal is configured to perform frequency hopping in PUCCH transmission in different time slots, the terminal does not expect to configure frequency hopping within the time slot during PUCCH transmission. If the terminal is not configured to perform frequency hopping in PUCCH transmission in different time slots, but is configured with frequency hopping within a time slot, the first PRB index and the second PRB index are equally applied within the time slot. If the number of uplink symbols available for PUCCH transmission is less than nrofSymbols configured via higher layer signaling, the terminal may not transmit PUCCH. Even if the terminal fails to transmit PUCCH for some reason in a certain time slot during repeated PUCCH transmission, the terminal may increase the number of repeated PUCCH transmissions.

[0189] PUCCH: PUCCH resource configuration

[0190] Next, the PUCCH resource configuration of the base station or terminal is described. The base station may be able to configure the PUCCH resources for each BWP for a specific terminal via a higher layer. The PUCCH resource configuration may be as shown in Table 24 below.

[0191] [Table 24]

[0192]

[0193]

[0194]

[0195] According to Table 24, one or more PUCCH resource sets in the PUCCH resource configuration 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 PUCCH resource may belong to one of the aforementioned PUCCH formats.

[0196] Regarding the PUCCH resource set, the maximum payload value of the first PUCCH resource set may be fixed to 2 bits. Therefore, the value may not be configured separately via a higher layer or the like. If the remaining PUCCH resource sets are configured, the index of the PUCCH resource set may be configured in ascending order according to the maximum payload value, and the maximum payload value may not be configured for the last PUCCH resource set. The higher layer configuration for the PUCCH resource set may be as shown in Table 25 below.

[0197] [Table 25]

[0198]

[0199] The parameter resourceList in Table 25 may include IDs of PUCCH resources belonging to a PUCCH resource set.

[0200] During initial access or if no PUCCH resource set is configured, a PUCCH resource set as shown in Table 26 may be used, which includes multiple cell-specific PUCCH resources in the initial BWP. The PUCCH resources in this PUCCH resource set to be used for initial access may be indicated via SIB1.

[0201] [Table 26]

[0202]

[0203] The maximum payload of each PUCCH resource included in the PUCCH resource set may be 2 bits for PUCCH format 0 or 1, and may be determined based on the symbol length, the number of PRBs, and the maximum code rate for the remaining formats. The 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.

[0204] Next, PUCCH resource selection for UCI transmission is described. For SR transmission, PUCCH resources for SR corresponding to schedulingRequestID may be configured via a higher layer as shown in Table 27. PUCCH resources may be resources belonging to PUCCH format 0 or PUCCH format 1.

[0205] [Table 27]

[0206]

[0207] For the configured PUCCH resources, the transmission period and offset may be configured via the parameter periodicityAndOffset of Table 27. If there is uplink data to be sent by the terminal at a time point corresponding to the configured period and offset, the corresponding PUCCH resource may be sent, otherwise the corresponding PUCCH resource may not be sent.

[0208] For CSI transmission, the PUCCH resources for sending periodic or semi-persistent CSI reports via PUCCH may be configured in the parameter pucch-CSI-ResourceList as shown in Table 28 below. The parameter pucch-CSI-ResourceList may include a list of PUCCH resources specific to each BWP for the cell or CC in which the corresponding CSI report is to be sent. The PUCCH resources may be resources belonging to PUCCH format 2, PUCCH format 3, or PUCCH format 4. For PUCCH resources, the transmission period and offset may be configured via reportSlotConfig of Table 28.

[0209] [Table 28]

[0210]

[0211]

[0212] For HARQ-ACK transmission, a resource set of PUCCH resources for transmission can be first selected according to the payload of UCI including the corresponding HARQ-ACK. That is, a PUCCH resource set with a minimum payload not less than the UCI payload can be selected. Next, the PUCCH resources in the PUCCH resource set can be selected via the PUCCH resource indicator (PRI) in the DCI for scheduling the TB corresponding to the HARQ-ACK, and the PRI can be the PUCCH resource indicator specified in Table 6 or Table 7. The relationship between the PRI and the PUCCH resources selected from the PUCCH resource set can be as shown in Table 29 below.

[0213] [Table 29]

[0214]

[0215] If the number of selected PUCCH resources in the PUCCH resource set is greater than 8, the PUCCH resources may be selected based on the following equation (1).

[0216]

[0217] In equation (1), r PUCCH Indicates the index of the selected PUCCH resource in the PUCCH resource set, R PUCCH Indicates the number of PUCCH resources belonging to the PUCCH resource set, Δ PRI Indicates PRI value, N CCE，p Indicates the total number of CCEs of CORESETp to which the received DCI belongs, and n CCE，p Indicates the first CCE index used for the received DCI.

[0218] The time point of sending the corresponding PUCCH resource is from the time when the TB corresponding to the corresponding HARQ-ACK is sent. 1 After time slots, the value K 1 The candidates are configured via higher layers, and more specifically, may be configured in the parameter dl-DataToUL-ACK in the PUCCH-Config specified in Table 27. One of the candidates K may be selected by the PDSCH to HARQ feedback timing indicator in the DCI for scheduling the TB. 1 value, and this value can be the value specified in Table 5 or Table 6. K 1 The unit of the value may be a unit of a slot or a unit of a subslot. Here, a subslot is a unit having a length smaller than that of a slot, and one or more symbols may constitute one subslot.

[0219] Next, a case where two or more PUCCH resources are located in one slot is described. The terminal may transmit UCI via one or two PUCCH resources in one slot or subslot, and when UCI is transmitted via two PUCCH resources in one slot / subslot, i) the corresponding PUCCH resources do not overlap in symbol units, and ii) at least one PUCCH resource may be a short PUCCH. The terminal may not expect to transmit multiple PUCCH resources in one slot for HARQ-ACK transmission.

[0220] PUCCH: related to the transmit beam

[0221] Next, the uplink transmit beam configuration to be used for PUCCH transmission is described. If the terminal does not have a UE-specific configuration for PUCCH resource configuration (dedicated PUCCH resource configuration), a PUCCH resource set is provided via pucch-ResourceCommon as higher layer signaling, wherein the beam configuration for PUCCH transmission conforms to the beam configuration used in PUSCH transmission scheduled via random access response (RAR) UL grant. If the terminal has a UE-specific configuration for PUCCH resource configuration (dedicated PUCCH resource configuration), the beam configuration for PUCCH transmission may be provided via pucch-spatialRelationInfoId as higher layer signaling included in Table 24. If the terminal is configured with one pucch-spatialRelationInfoId, the beam configuration for PUCCH transmission of the terminal may be provided via one pucch-spatialRelationInfoId. If the terminal is configured with multiple pucch-spatialRelationInfoIDs, the terminal may be instructed to activate one of the multiple pucch-spatialRelationInfoIDs via a MAC control element (CE). The terminal may be configured with up to eight pucch-spatialRelationInfoIDs via higher layer signaling, and may be instructed to activate only one pucch-spatialRelationInfoID from among them. If the terminal is instructed to activate any pucch-spatialRelationInfoID via MAC CE, the terminal may activate via MAC CE from the PDSCH relative to the MAC CE used to transmit the activation information including the pucch-spatialRelationInfoID in the time slot used for HARQ-ACK transmission. The first time slot after the first time slot, pucch-spatialRelationInfoID should be activated. μ is the parameter set applied to PUCCH transmission, and Refers to the number of slots per subframe in a given parameter set. The higher layer configuration for pucch-spatialRelationInfo can be as shown in Table 30 below.

[0222] [Table 30]

[0223]

[0224] According to Table 30, there may be one referenceSignal configuration in a specific pucch-spatialRelationInfo configuration, and the referenceSignal may be an ssb-Index indicating a specific SS / PBCH, may be a csi-RS-Index indicating a specific CSI-RS, or may be an srs indicating a specific SRS. If the referenceSignal is configured with an ssb-Index, the terminal may configure the beam used when receiving the SS / PBCH corresponding to the ssb-Index among the SS / PBCH in the same serving cell as the beam used for PUCCH transmission, or if servingCellId is provided, the beam used when receiving the SS / PBCH corresponding to the ssb-Index among the SS / PBCH in the cell indicated by servingCellId may be configured as the beam used for PUCCH transmission. If referenceSignal is configured with csi-RS-Index, the terminal can configure the beam used when receiving the CSI-RS corresponding to the csi-RS-Index among the CSI-RS in the same serving cell as the beam for PUCCH transmission, or if servingCellId is provided, the beam used when receiving the CSI-RS corresponding to the csi-RS-Index among the CSI-RS in the cell indicated by servingCellId can be configured as the beam for PUCCH transmission. If ReferenceSignal is configured with SRS, the terminal may configure the transmit beam used when transmitting an SRS corresponding to a resource index provided via a higher layer signaling resource in the same serving cell and / or in an activated uplink BWP as a beam for PUCCH transmission, or if servingCellID and / or uplinkBWP are provided, the transmit beam used when transmitting an SRS corresponding to a resource index provided via a higher layer signaling resource in a cell indicated by servingCellID and / or uplinkBWP and / or in an uplink BWP may be configured as a beam for PUCCH transmission. One pucch-PathlossReferenceRS-Id configuration may exist in a specific pucch-spatialRelationInfo configuration. The PUCCH-PathlossReferenceRS of Table 31 may be mapped with the pucch-PathlossReferenceRS-Id of Table 30, and up to 4 configurations are possible via pathlossReferenceRS in the higher signaling of PUCCH-PowerControl of Table 31.PUCCH-PathlossReferenceRS may be configured with ssb-Index when connected to SS / PBCH via higher signaling of referenceSignal, and may be configured with csi-RS-Index when connected to CSI-RS.

[0225] [Table 31]

[0226]

[0227]

[0228] PUCCH: Group-based spatial relationship activation

[0229] In version 15, if multiple pucch-spatialRelationInfoIDs are configured, the terminal can receive a MAC CE for activating the spatial relationship of each PUCCH resource, thereby determining the spatial relationship of the corresponding PUCCH resource. However, such a method has the disadvantage of requiring a lot of signaling overhead to activate the spatial relationship of multiple PUCCH resources. Therefore, in version 16, a new MAC CE for adding PUCCH resource groups and activating spatial relationships in units of PUCCH resource groups has been introduced. For PUCCH resource groups, up to 4 PUCCH resource groups can be configured via resourceGroupToAddModList of Table 24, and for each PUCCH resource group, multiple PUCCH resource IDs in one PUCCH resource group can be configured as a list as shown in Table 32 below.

[0230] [Table 32]

[0231]

[0232] In Release 16, the base station may configure each PUCCH resource group for the terminal via resourceGroupToAddModList in Table 24 and the higher layer configuration in Table 32, and may configure a MAC CE for simultaneous activation of the spatial relationship of all PUCCH resources in one PUCCH resource group.

[0233] Figure 8 is a diagram illustrating an example of a MAC CE for activation based on a spatial relationship of a PUCCH resource group in a wireless communication system according to an embodiment.

[0234] Reference Figure 8, a supported cell ID 810 and a BWP ID 820 configured with a PUCCH resource to which a MAC CE is to be applied are indicated by Oct (octet) 1 800. PUCCH resource IDs 831 and 841 indicate the IDs of the PUCCH resources, and if the indicated PUCCH resources are included in a PUCCH resource group according to resourceGroupToAddModList, another PUCCH resource ID in the same PUCCH resource group is not indicated in the same MAC CE, and all PUCCH resources in the same PUCCH resource group are activated with the same spatial relationship information IDs 836 and 846. In this case, the spatial relationship information IDs 836 and 846 include a value corresponding to PUCCH-SpatialRelationInfoId-1 to be applied to the PUCCH resource group of Table 30.

[0235] Related to SRS

[0236] A method for uplink channel estimation using a sounding reference signal (SRS) transmission of a terminal is described as follows. The base station may configure at least one SRS configuration for each uplink BWP to transmit configuration information for SRS transmission to the terminal, and may also configure at least one SRS resource group for each SRS configuration. As an example, the base station and the terminal may send and receive the following higher signaling information to transmit information about the SRS resource set.

[0237] -srs-ResourceSetId: SRS resource set index

[0238] -srs-ResourceIdList: A collection of SRS resource indexes referenced by the SRS resource set

[0239] -resourceType: The timeline transmission configuration of the SRS resource referenced by the SRS resource set, where resourceType can be configured as one of "periodic", "semi-persistent", and "aperiodic". If resourceType is configured as "periodic" or "semi-persistent", the associated CSI-RS information can be provided according to the usage of the SRS resource set. If resourceType is configured as "aperiodic", the aperiodic SRS resource trigger list and time slot offset information can be provided, and the associated CSI-RS information can be provided according to the usage of the SRS resource set.

[0240] -usage: Configuration for the usage of the SRS resource referenced by the SRS resource set, where usage can be configured as one of "beamManagement", "codebook", "nonCodebook" and "antennaSwitching".

[0241] -alpha, p0, pathlossReferenceRS, srs-PowerControlAdjustmentStates: Provides parameter configuration for transmit power adjustment of SRS resources referenced by an SRS resource set.

[0242] The terminal may understand that the SRS resources included in the SRS resource index set referenced by the SRS resource set conform to the information included in the SRS resource set.

[0243] In addition, the base station and the terminal may send or receive higher layer signaling information to transmit separate configuration information for SRS resources. As an example, the separate configuration information for SRS resources may include time-frequency axis mapping information within the time slot of the SRS resources, which may include information about frequency hopping within the time slot of the SRS resources or between the time slots of the SRS resources. In addition, the separate configuration information for SRS resources may include a timeline transmission configuration for the SRS resources, and may be configured as one of "periodic", "semi-persistent" and "aperiodic". This may be limited to having a timeline transmission configuration, such as an SRS resource set including an SRS resource. If the timeline transmission configuration of the SRS resource is configured as "periodic" or "semi-persistent", an additional SRS resource transmission period and time slot offset (e.g., periodityAndOffset) may be included in the timeline transmission configuration.

[0244] The base station may activate, deactivate or trigger SRS transmission to the terminal via L1 signaling (e.g., DCI) or higher layer signaling including MAC CE signaling or RRC signaling. For example, the base station may activate or deactivate periodic SRS transmission of the terminal via higher layer signaling. The base station may indicate via higher layer signaling that an SRS resource set in which resourceType is configured as periodic is to be activated, and the terminal may transmit SRS resources referenced by the activated SRS resource set. The time-frequency axis resource mapping within the time slot of the transmitted SRS resource conforms to the resource mapping information configured in the SRS resource, and the time slot mapping including the transmission period and time slot offset conforms to the periodicityAndOffset configured in the SRS resource. In addition, the spatial domain transmit filter applied to the transmitted SRS resource may refer to the spatial relationship information configured in the SRS resource, or may refer to the associated CSI-RS information configured in the SRS resource set including the SRS resource. The terminal may transmit SRS resources in an uplink BWP activated for periodic SRS resources activated via higher layer signaling.

[0245] For example, the base station may activate or deactivate the semi-persistent SRS transmission of the terminal via higher layer signaling. The base station may indicate the activation of the SRS resource set via MAC CE signaling, and the terminal may transmit the SRS resource referenced by the activated SRS resource set. The SRS resource set activated via MAC CE signaling may be limited to the SRS resource set in which the resourceType is configured as semi-persistent. The time-frequency axis resource mapping within the time slot of the transmitted SRS resource conforms to the resource mapping information configured in the SRS resource, and the time slot mapping including the transmission period and the time slot offset conforms to the periodicityAndOffset configured in the SRS resource. In addition, the spatial domain transmission filter applied to the transmitted SRS resource may refer to the spatial relationship information configured in the SRS resource, or may refer to the associated CSI-RS information configured in the SRS resource set including the SRS resource. If the spatial relationship information is configured in the SRS resource, it is not in accordance with the spatial relationship information, but the spatial domain transmission filter may be determined by referring to the configuration information about the spatial relationship information transmitted via the MAC CE signaling for activating the semi-persistent SRS transmission. The terminal may transmit SRS resources in the uplink BWP activated for the semi-persistent SRS resources activated via higher layer signaling.

[0246] For example, the base station may trigger aperiodic SRS transmission to the terminal via DCI. The base station may indicate one of the aperiodic SRS resource triggers (apiodicSRS-ResourceTrigger) via the SRS request field of the DCI. The terminal may understand that the SRS resource set has been triggered, and the SRS resource set includes the aperiodic SRS resource trigger indicated by DCI in the aperiodic SRS resource trigger list in the configuration information of the SRS resource set. The terminal may send the SRS resource referenced by the triggered SRS resource set. The time-frequency axis resource mapping within the time slot of the transmitted SRS resource conforms to the resource mapping information configured in the SRS resource. In addition, the time slot mapping of the transmitted SRS resource may be determined via the time slot offset between the PDCCH including the DCI and the SRS resource, which may refer to the value included in the time slot offset set configured in the SRS resource set. Specifically, the time slot offset between the PDCCH including the DCI and the SRS resource may be applied, that is, the value indicated by the time domain resource assignment field of the DCI among the offset values ​​included in the time slot offset set configured in the SRS resource set. In addition, the spatial domain transmit filter applied to the transmitted SRS resource may refer to the spatial relationship information configured in the SRS resource, or may refer to the associated CSI-RS information configured in the SRS resource set including the SRS resource. The terminal may transmit the SRS resource in the uplink BWP activated for the aperiodic SRS resource triggered via DCI.

[0247] When the base station triggers aperiodic SRS transmission to the terminal via DCI, in order for the terminal to send SRS by applying the configuration information of the SRS resource, a minimum time interval between the PDCCH including the DCI that triggers the aperiodic SRS transmission and the SRS transmitted may be necessary. The time interval for SRS transmission of the terminal can be defined as the number of symbols between the last symbol of the PDCCH including the DCI that triggers the aperiodic SRS transmission and the first symbol to which the first transmitted SRS resource among the transmitted SRS resources is mapped. The minimum time interval can be determined by referring to the PUSCH preparation process time required for the terminal to prepare for PUSCH transmission. In addition, the minimum time interval can have different values ​​depending on the usage of the SRS resource set including the transmitted SRS resource. For example, the minimum time interval can be defined as N2 symbols determined by referring to the PUSCH preparation process time of the terminal taking into account the terminal processing capability. In addition, if the usage of the SRS resource set including the transmitted SRS resource is configured as "codebook" or "antennaSwitching", the minimum time interval may be determined as N2 symbols, and if the usage of the SRS resource set is configured as "nonCodebook" or "beamManagement", the minimum time interval may be determined as N2+14 symbols. If the time interval for non-periodic SRS transmission is greater than or equal to the minimum time interval, the terminal may transmit the non-periodic SRS, and if the time interval for non-periodic SRS transmission is less than the minimum time interval, the terminal may ignore the DCI triggering the non-periodic SRS.

[0248] [Table 33]

[0249]

[0250]

[0251] The spatialRelationInfo configuration information in Table 33 refers to one reference signal and applies the beam information of the reference signal to the beam used for corresponding SRS transmission. For example, the configuration of spatialRelationInfo may include the information shown in Table 34 below.

[0252] [Table 34]

[0253]

[0254] Referring to the spatialRelationInfo configuration, the SS / PBCH block index, CSI-RS index, or SRS index may be configured as the index of the reference signal to be referenced in order to use the beam information of a specific reference signal. The higher signaling referenceSignal is configuration information indicating which reference signal beam information is to be referenced for the corresponding SRS, ssb-Index refers to the SS / PBCH block index, csi-RS-Index refers to the CSI-RS index, and ssr refers to the SRS index. If the value of the higher signaling referenceSignal is configured as "ssb-Index", the terminal may apply the receive beam used when receiving the SS / PBCH block corresponding to the ssb-Index as the transmit beam for SRS transmission. If the value of the higher signaling referenceSignal is configured as "csi-RS-Index", the terminal may apply the receive beam used when receiving the CSI-RS corresponding to the csi-RS-Index as the transmit beam for SRS transmission. If the value of the higher signaling referenceSignal is configured as "srs", the terminal can apply the transmission beam used when transmitting the SRS corresponding to the srs as the transmission beam for SRS transmission.

[0255] PUSCH: related to the transmission scheme

[0256] Next, a scheduling scheme for PUSCH transmission is described. PUSCH transmission can be dynamically scheduled by a UL grant in DCI or can be operated by a configured grant type 1 or type 2. Dynamic scheduling indication for PUSCH transmission is possible in case of DCI format 0_0 or 0_1.

[0257] For configured grant type 1 PUSCH transmission, UL grant in DCI may not be received, and configuration may be performed semi-statically by receiving configuredGrantConfig including rrc-ConfiguredUplinkGrant of Table 35 via higher signaling. After receiving configuredGrantConfig not including rrc-ConfiguredUplinkGrant of Table 35 via higher signaling, configured grant type 2 PUSCH transmission may be semi-persistently scheduled via UL grant in DCI. When PUSCH transmission is operated via configured grant, in addition to dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, and scaling of UCI-OnPUSCH provided via pusch-Config as higher signaling in Table 36, parameters applied to PUSCH transmission are applied via configuredGrantConfig as higher signaling in Table 38. If the terminal is provided with transformPrecoder in configuredGrantConfig as higher signaling in Table 35, the terminal applies tp-pi2BPSK in pusch-Config of Table 36 to PUSCH transmission operated by the configured grant.

[0258] [Table 35]

[0259]

[0260]

[0261]

[0262] Next, the PUSCH transmission method is described. The DMRS antenna port used for PUSCH transmission is the same as the antenna port used for SRS transmission. Depending on whether the value of txConfig in pusch-Config as higher signaling of Table 36 is "codebook" or "nonCodebook", PUSCH transmission can conform to each of the codebook-based transmission method and the non-codebook-based transmission method.

[0263] As described above, PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1, or can be semi-statically configured by a configured grant. If the terminal is instructed to schedule PUSCH transmission via DCI format 0_0, the terminal performs beam configuration for PUSCH transmission by using the pucch-spatialRelationInfoID corresponding to the UE-specific PUCCH resource, which corresponds to the smallest ID within the uplink BWP enabled in the serving cell, in which case PUSCH transmission is based on a single antenna port. Within a BWP in which a PUCCH resource including pucch-spatialRelationInfo is not configured, the terminal does not expect PUSCH transmission to be scheduled via DCI format 0_0. If the terminal is not configured with txConfig in pusch-Config of Table 36, the terminal does not expect scheduling via DCI format 0_1.

[0264] [Table 36]

[0265]

[0266]

[0267] Next, codebook-based PUSCH transmission is described. Codebook-based PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1, and can work semi-statically through the configured grant. If the codebook-based PUSCH is dynamically scheduled via DCI format 0_1 ​​or semi-statically configured through the configured grant, the terminal determines the precoder for PUSCH transmission based on the SRS resource indicator (SRI), the transmission precoding matrix indicator (TPMI) and the transmission rank (the number of PUSCH transmission layers).

[0268] In this case, SRI may be given via the SRS resource indicator field in the DCI, or may be configured via srs-ResourceIndicator as higher signaling. The terminal is configured with at least one SRS resource under codebook-based PUSCH transmission, and may be configured with up to two SRS resources. When the terminal is provided with SRI via DCI, the SRS resource indicated by SRI refers to the SRS resource corresponding to SRI among the SRS resources transmitted before the PDCCH including SRI. TPMI and transmission rank may be given via fields, precoding information, and the number of layers in the DCI, or may be configured via precodingAndNumberOfLayers as higher signaling. TPMI is used to indicate the precoder applied to PUSCH transmission. If the terminal is configured with one SRS resource, TPMI is used to indicate the precoder to be applied in one configured SRS resource. If the terminal is configured with multiple SRS resources, TPMI is used to indicate the precoder to be applied in the SRS resource indicated via SRI.

[0269] The precoder to be used for PUSCH transmission is selected from an uplink codebook whose number of antenna ports is the same as the value of nrofSRS-Ports in SRS-Config as higher signaling. In codebook-based PUSCH transmission, the terminal determines the codebook subset based on codebookSubset and TPMI in pusch-Config as higher signaling. The codebookSubset in pusch-Config as higher signaling can be configured as one of "fullAndPartialAndNonCoherent", "partialAndNonCoherent" or "nonCoherent" based on the UE capabilities reported by the terminal to the base station. If the terminal has reported "partialAndNonCoherent" as the UE capability, the terminal does not expect the value of codebookSubset as higher signaling to be configured as "fullAndPartialAndNonCoherent". If the terminal has reported "nonCoherent" as a UE capability, the terminal expects that the value of codebookSubset as higher signaling is neither configured as "fullyAndPartialAndNonCoherent" nor as "partialAndNonCoherent". If nrofSRS-Ports in SRS-ResourceSet as higher signaling indicates two SRS antenna ports, the terminal does not expect the value of codebookSubset as higher signaling to be configured as "partialAndNonCoherent".

[0270] The terminal may be configured with an SRS resource set in which the value of usage in SRS-ResourceSet as higher signaling is configured as "codebook", and one SRS resource in the corresponding SRS resource set may be indicated via SRI. If multiple SRS resources are configured in the SRS resource set in which the value of usage in SRS-ResourceSet as higher signaling is configured as "codebook", the terminal expects that the value of nrofSRS-Ports in SRS-Resource as higher signaling is configured to be the same for all SRS resources.

[0271] The terminal sends one or more SRS resources included in the SRS resource set in which the usage value is configured as "codebook" to the base station according to higher signaling, and the base station selects one of the SRS resources sent by the terminal and instructs the terminal to use the transmit beam information of the corresponding SRS resource to perform PUSCH transmission. In this case, in the codebook-based PUSCH transmission, SRI is used as information for selecting an index of an SRS resource and is included in the DCI. Additionally, the base station adds information indicating the rank and TPMI to be used by the terminal for PUSCH transmission to the DCI. The terminal performs PUSCH transmission using the SRS resource indicated by SRI by applying the precoder indicated by TPMI and the rank already indicated based on the transmit beam of the SRS resource.

[0272] Next, non-codebook based PUSCH transmission is described. Non-codebook based PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1, and can work semi-statically through the configured permission. If at least one SRS resource is configured in the SRS resource set in which the value of usage in the SRS-ResourceSet as higher signaling is configured as "nonCodebook", the terminal can schedule non-codebook based PUSCH transmission via DCI format 0_1.

[0273] For an SRS resource set in which the value of usage in the SRS-ResourceSet as higher signaling is configured as "nonCodebook", the terminal may be configured with a connected non-zero power (NZP) CSI-RS resource. The terminal may perform calculations on the precoder used for SRS transmission via measurements of the NZP CSI-RS resources connected to the SRS resource set. If the difference between the last received symbol of the aperiodic NZP CSI-RS resource connected to the SRS resource set and the first symbol of the aperiodic SRS transmission in the terminal is less than 42 symbols, the terminal does not expect information about the precoder used for SRS transmission to be updated.

[0274] If the value of resourceType in SRS-ResourceSet as higher signaling is configured as "aperiodic", the connected NZP CSI-RS is indicated via the SRS request as a field in DCI format 0_1 ​​or 1_1. In this case, if the connected NZP CSI-RS resource is a non-periodic NZP CSI-RS resource, it indicates that the connected NZP CSI-RS exists when the value of the field SRS request in DCI format 0_1 ​​or 1_1 is not "00". In this case, the corresponding DCI should neither indicate cross-carrier scheduling nor cross-BWP scheduling. If the value of the SRS request indicates the presence of NZP CSI-RS, the NZP CSI-RS is located in a time slot in which a PDCCH including an SRS request field has been sent. The TCI state configured in the scheduled subcarrier is not configured as QCL-TypeD.

[0275] If a periodic or semi-persistent SRS resource set is configured, the connected NZP CSI-RS may be indicated via the associatedCSI-RS in the SRS-ResourceSet as higher signaling. For non-codebook based transmission, the terminal does not expect the spatialRelationInfo as higher signaling for the SRS resource to be configured together with the associatedCSI-RS in the SRS-ResourceSet as higher signaling.

[0276] If multiple SRS resources are configured, the terminal can determine the precoder and transmission rank to be applied to PUSCH transmission based on the SRI indicated by the base station. SRI can be indicated via the field SRS resource indicator in the DCI, or can be configured via srs-ResourceIndicator as a higher signaling. Like the aforementioned codebook-based PUSCH transmission, when the terminal receives SRI via DCI, the SRS resource indicated by SRI refers to the SRS resource corresponding to SRI among the SRS resources sent before the PDCCH including SRI. The terminal can use one or more SRS resources for SRS transmission, and the maximum number of SRS resources that can be transmitted simultaneously in the same symbol in an SRS resource set is determined by the UE capability reported by the terminal to the base station. In this case, the SRS resources transmitted simultaneously by the terminal occupy the same RB. The terminal configures an SRS port for each SRS resource. Only one SRS resource set in which the value of usage in SRS-ResourceSet as a higher signaling is configured as "nonCodebook" can be configured, and up to 4 SRS resources for non-codebook-based PUSCH transmission can be configured.

[0277] The base station sends an NZP CSI-RS connected to an SRS resource set to the terminal, and the terminal calculates the precoder to be used during the transmission of one or more SRS resources in the SRS resource set based on the result measured when receiving the NZP CSI-RS. The terminal applies the calculated precoder when sending one or more SRS resources in the SRS resource set in which usage is configured as "nonCodebook" to the base station, and the base station selects one or more SRS resources from the received one or more SRS resources. In non-codebook based PUSCH transmission, SRI refers to an index that can represent an SRS resource or a combination of multiple SRS resources, and the SRI is included in the DCI. The number of SRS resources indicated by the SRI sent by the base station can be the number of transmission layers of the PUSCH, and the terminal sends the PUSCH by applying the precoder applied to the SRS resource transmission to each layer.

[0278] PUSCH: Preparation process time

[0279] Next, the PUSCH preparation process time is described. If the base station uses DCI format 0_0, 0_1, or 0_2 to schedule the terminal to send PUSCH, the terminal may need the PUSCH preparation process time to send PUSCH by applying the transmission method indicated by DCI (transmission precoding method of SRS resources, number of transmission layers, and spatial domain transmission filter). In NR, the PUSCH preparation process time is defined with this in mind. The PUSCH preparation process time of the terminal can follow the following equation (2).

[0280] Tproc,2=max((N2+d2,1+d2)(2048+144)κ2-μTc+Text+Tswitch,d2,2)

[0281] …(2)

[0282] In Tproc,2 described above by equation (2), each variable can have the following meanings.

[0283] -N2: The number of symbols determined according to UE processing capability 1 or 2 and parameter set μ according to the capability of the terminal. If UE processing capability 1 is reported according to the capability report of the terminal, N2 has the value of Table 37, and if UE processing capability 2 is reported and UE processing capability 2 is configured to be available via higher layer signaling, N2 may have the value of Table 38.

[0284] [Table 37]

[0285]

[0286] [Table 38]

[0287]

[0288] -d2,1: when all resource elements of the first OFDM symbol transmitted by the PUSCH are configured to include only DM-RS, the number of symbols is determined to be 0; otherwise, the number of symbols is determined to be 1.

[0289] -κ: 64

[0290] -μ:μ follows μ DL or μ UL One of them, in this case Tproc,2 has a larger value. DL indicates a downlink parameter set in which a PDCCH including a DCI for scheduling a PUSCH is transmitted, and μ UL Indicates the uplink parameter set in which the PUSCH is transmitted.

[0291] -Tc: Tc has 1 / (Δf max ·N f ), Δf max =480·10 3 Hz and N f =4096.

[0292] -d2,2: d2,2 follows the BWP switching time when the DCI for scheduling PUSCH indicates BWP switching, otherwise it has 0.

[0293] -d2: When the OFDM symbols of the PUCCH with a low priority index, the PUSCH with a high priority index, and the PUCCH overlap in time, the value of d2 of the PUSCH with a high priority index is used. Otherwise, d2 is 0.

[0294] -Text: When the terminal uses the shared spectrum channel access scheme, the terminal can calculate the Text and apply it to the PUSCH preparation process time. Otherwise, Text is assumed to be 0.

[0295] -Tswitch: If an uplink switching interval is triggered, Tswitch is assumed to be the switching interval time. Otherwise, Tswitch is assumed to be 0.

[0296] In consideration of the time axis resource mapping information of the PUSCH scheduled via the DCI and the timing advance effect between the uplink and the downlink, when the first symbol of the PUSCH starts before the first uplink symbol starting after the last symbol Tproc,2 of the PDCCH including the DCI for scheduling the PUSCH, the base station and the terminal determine that the PUSCH preparation procedure time is insufficient. Otherwise, the base station and the terminal determine that the PUSCH preparation procedure time is sufficient. If the PUSCH preparation procedure time is sufficient, the terminal sends the PUSCH, and if the PUSCH preparation procedure time is insufficient, the terminal can ignore the DCI for scheduling the PUSCH.

[0297] PUSCH: related to transmission

[0298] In the following, repeated transmission of an uplink data channel in a 5G system is described as follows. In a 5G system, repeated PUSCH transmission type A and repeated PUSCH transmission type B are supported as two types of methods for repeated transmission of an uplink data channel. The terminal can be configured with one of repeated PUSCH transmission types A or B via higher layer signaling.

[0299] 1. Repeated PUSCH transmission type A

[0300] As described above, the symbol length and the position of the starting symbol of the uplink data channel are determined by the time domain resource allocation method within a time slot, and the base station can notify the terminal of the number of repeated transmissions via higher layer signaling (e.g., RRC signaling) or L1 signaling (e.g., DCI).

[0301] The terminal can repeatedly transmit the uplink data channel having the same length and starting symbol as those of the configured uplink data channel in consecutive time slots based on the number of repeated transmissions received from the base station. In this case, when at least one symbol in the symbols of the uplink data channel configured for the terminal or in the time slot configured for the terminal for the uplink is configured as a downlink, the terminal omits the uplink data channel transmission, but counts the number of repeated transmissions of the uplink data channel.

[0302] 2. Repeated PUSCH transmission type B

[0303] As described above, the starting symbol and length of the uplink data channel are determined by the time domain resource allocation method within a time slot, and the base station can notify the terminal of the number of repetitions via higher layer signaling (e.g., RRC signaling) or L1 signaling (e.g., DCI).

[0304] First, the nominal repetition of the uplink data channel is determined based on the configured starting symbol and length of the uplink data channel as follows. The time slot where the nth nominal repetition starts is given by is given by , and the symbol starting in the time slot is given by The time slot at which the nth nominal repetition ends is given by is given by , and the symbol that ends in the time slot is given by Here, n=0, ..., number of repetitions-1, S is the starting symbol of the configured uplink data channel, and L indicates the symbol length of the configured uplink data channel. K s indicates the timeslot in which PUSCH transmission starts, and Indicates the number of symbols per slot.

[0305] The terminal determines an invalid symbol for repeated PUSCH transmission type B. Symbols configured for the downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated are determined to be invalid symbols for repeated PUSCH transmission type B. In addition, invalid symbols can be configured by higher layer parameters (e.g., InvalidSymbolPattern). The higher layer parameters (e.g., InvalidSymbolPattern) provide a symbol-level bitmap throughout one time slot or two time slots so that invalid symbols can be configured. A 1 in the bitmap indicates an invalid symbol. In addition, the period and pattern of the bitmap can be configured via a higher layer parameter (e.g., periodicityAndPattern). If a higher layer parameter (e.g., InvalidSymbolPattern) is configured and the parameter InvalidSymbolPatternIndicator-ForDCIFormat0_1 or InvalidSymbolPatternIndicator-ForDCIFormat0_2 indicates 1, the terminal applies an invalid symbol pattern, and if the parameter indicates 0, the terminal does not apply the invalid symbol pattern. If a higher layer parameter (e.g., InvalidSymbolPattern) is configured and the parameter InvalidSymbolPatternIndicator-ForDCIFormat0_1 or InvalidSymbolPatternIndicator-ForDCIFormat0_2 is not configured, the terminal applies an invalid symbol pattern.

[0306] After the invalid symbols are determined, for each nominal repetition, the terminal may consider symbols other than the invalid symbols as valid symbols. If one or more valid symbols are included in each nominal repetition, the nominal repetition may include one or more actual repetitions. Here, each actual repetition includes a "continuous set" of valid symbols of PUSCH transmission type B that can be used for repetition in a time slot.

[0307] Fig. 9 is a diagram illustrating an example of repeated PUSCH transmission type B in a wireless communication system according to an embodiment.

[0308] For the terminal, the start symbol S of the uplink data channel may be configured as 0, the length L of the uplink data channel may be configured as 14, and the number of repeated transmissions may be configured as 16. In this case, the nominal repetition 901 is indicated in 16 consecutive time slots. Then, the terminal may determine the symbol configured as the downlink symbol in each nominal repetition 901 as an invalid symbol. In addition, the terminal determines the symbol configured as 1 in the invalid symbol pattern 902 as an invalid symbol. In each nominal repetition, if a valid symbol that is not an invalid symbol includes one or more consecutive symbols in one time slot, an actual repetition 903 is configured and transmission is performed.

[0309] In addition, with regard to repeated PUSCH transmission, in NR Release 16, the following additional methods may be defined for UL grant-based PUSCH transmission and configured grant-based PUSCH transmission over slot boundaries.

[0310] - Method 1 (Mini-slot level repetition): Two or more repeated PUSCH transmissions are scheduled within one slot or on the boundary of consecutive slots via one UL grant. In addition, with respect to method 1, the time domain resource allocation information in the DCI indicates the resources of the first repeated transmission. In addition, the time domain resource information of the remaining repeated transmissions can be determined based on the time domain resource information of the first repeated transmission and the uplink or downlink direction determined for each symbol of each slot. Each repeated transmission occupies consecutive symbols.

[0311] -Method 2 (multi-segment sending):Two or more repeated PUSCH transmissions are scheduled in consecutive time slots via one UL grant. In this case, one transmission is specified for each time slot, and the starting point or repetition length may be different for each transmission. In addition, with respect to method 2, the time domain resource allocation information in the DCI indicates the starting point and repetition length of all repeated transmissions. In addition, when repeated transmissions are performed within a single time slot via method 2, if there are multiple consecutive uplink symbol bundles in the time slot, each repeated transmission is performed for each uplink symbol bundle. If there are consecutive uplink symbol bundles uniquely in the time slot, one repeated PUSCH transmission is performed according to the method of NR version 15.

[0312] -Method 3: Two or more repeated PUSCH transmissions are scheduled in consecutive time slots via two or more UL grants. In this case, one transmission is assigned to each time slot, and the nth UL grant can be received before the PUSCH transmission scheduled via the (n-1)th UL grant ends.

[0313] -Method 4: Via an UL grant or a configured grant, one or more repeated PUSCH transmissions within a single time slot or two or more repeated PUSCH transmissions on the boundary of consecutive time slots can be supported. The number of repetitions indicated by the base station to the terminal is only a nominal value, and the number of repeated PUSCH transmissions actually performed by the terminal may be greater than the nominal number of repetitions. The time domain resource allocation information in the DCI or in the configured grant refers to the resources of the first repeated transmission indicated by the base station. The time domain resource information of the remaining repeated transmissions can be determined by at least partially referring to the resource information of the first repeated transmission and the uplink or downlink direction of the symbol. If the time domain resource information of the repeated transmission indicated by the base station crosses the time slot boundary or includes an uplink / downlink switching point, the repeated transmission can be divided into multiple repeated transmissions. In this case, one repeated transmission can be included in each uplink cycle in a time slot.

[0314] PUSCH: Frequency Hopping Process

[0315] Hereinafter, frequency hopping of an uplink data channel (PUSCH) in a 5G system is described in detail.

[0316] In 5G, as a frequency hopping method for the uplink data channel, each repeated PUSCH transmission type supports two methods. First, repeated PUSCH transmission type A supports intra-slot frequency hopping and inter-slot frequency hopping, while repeated PUSCH transmission type B supports inter-repetition frequency hopping and inter-slot frequency hopping.

[0317] The intra-slot frequency hopping method supported by repeated PUSCH transmission type A is a method by which a terminal changes the allocated resources in the frequency domain by a configured frequency offset in two hops within one slot and performs transmission. In the intra-slot frequency hopping, the starting RB of each hop can be expressed by the following equation (3).

[0318]

[0319] In equation (3), i=0 and i=1 indicate the first hop and the second hop, respectively, and RB start Indicates the starting RB in the UL BWP and is calculated based on the frequency resource allocation method. RB offset The frequency offset between two hops is indicated via a higher layer parameter. The number of symbols in the first hop can be determined by Indicated, and the number of symbols in the second hop can be determined by instruct. It is the length of a PUSCH transmission within one slot and is represented by the number of OFDM symbols.

[0320] Hereinafter, the inter-slot frequency hopping method supported by repeated PUSCH transmission types A and B is a method in which the terminal changes the allocated resources in the frequency domain by the configured frequency offset for each time slot and performs transmission. During a time slot, the starting RB can be expressed by the following equation (4).

[0321]

[0322] In equation (4), Indicates the current slot number in a multi-slot PUSCH transmission, and RB start Indicates the starting RB in the UL BWP and is calculated based on the frequency resource allocation method. RB offset The frequency offset between two hops is indicated via a higher layer parameter.

[0323] Next, the inter-repetition frequency hopping method supported by repeated PUSCH transmission type B includes performing transmission by moving the resources allocated in the frequency domain as much as the configured frequency offset for one or more actual repetitions within each nominal repetition. RBstart(n), which is the index of the starting RB for one or more actual repetitions within the nth nominal repetition in the frequency domain, can conform to the following equation (5).

[0324]

[0325] In equation (5), n indicates the index of the nominal repetition, and RB offset The RB offset between two hops is indicated via a higher layer parameter.

[0326] Rate matching for UCI multiplexed on PUSCH

[0327] Hereinafter, rate matching for UCI in a 5G system is described in detail. First, before describing rate matching for UCI, a case in which UCI is multiplexed to PUSCH is described. The terminal sends multiple overlapping PUCCHs or overlapping PUCCHs and PUSCHs in one time slot, and the terminal is configured to multiplex different UCI types on one PUCCH, and if at least one of the multiple overlapping PUCCHs or PUSCHs is a signal sent by the terminal when a DCI format is received, the terminal can multiplex all corresponding UCI types that satisfy the timeline condition as described in detail in the following clause 9.2.5 of 3GPP standard TS 38.213. As an example of a timeline condition for UCI multiplexing, if one of PUCCH transmission or PUSCH transmission is scheduled via DCI, the terminal can perform UCI multiplexing only when the first symbol of the earliest PUCCH or PUSCH among the overlapping PUCCH and PUSCH in the time slot satisfies the following conditions:

[0328] S0 is not from the last symbol of the corresponding PDSCH The symbol sent before the symbol including the CP starting after. Here, is the i-th PDSCH associated with the HARQ-ACK sent on the PUCCH in the overlapping PUCCH and PUSCH group. The maximum value of . is the processing time for the ith PDSCH and is defined as Here, d 1,1 is a value determined for the i-th PDSCH with reference to clause 5.3 of 3GPP standard TS 38.214, and N 1 is the PDSCH processing time value according to the PDSCH processing capability. In addition, μ is the minimum subcarrier configuration value between the PDCCH for scheduling the i-th PDSCH, the i-th PDSCH, the PUCCH including the HARQ-ACK for the i-th PDSCH, and all PUSCHs in the overlapping PUCCH and PUSCH group. T C is 1 / (Δf max ·N f ), Δf max =480·10 3 Hz、N f =4096, and k is 64.

[0329] This is part of the timeline condition for UCI multiplexing, and when the timeline condition is met by referring to clause 9.2.5 of 3GPP standard TS 38.213, the terminal can perform UCI multiplexing on PUSCH. When PUCCH and PUSCH overlap and the timeline condition for UCI multiplexing described in detail in clause 9.2.5 of 3GPP standard TS 38.213 including the above example is met, the terminal can multiplex HARQ-ACK and / or CSI information included in PUCCH on PUSCH, and may not send PUCCH according to UCI information included in PUSCH.

[0330] Then, if PUCCH and PUSCH overlap, the timeline condition for UCI multiplexing is met, and the terminal determines that the UCI included in the PUCCH is to be multiplexed on the PUSCH, the terminal performs UCI rate matching for UCI multiplexing. UCI multiplexing is performed in the order of HARQ-ACK, configured grant uplink control information (CG-UCI), CSI part 1, and CSI part 2. The terminal performs rate matching while considering the UCI multiplexing order. Therefore, the terminal calculates each layer of coded modulation symbols for HARQ-ACK and CG-UCI, and while considering this, the terminal calculates each layer of coded modulation symbols for CSI part 1. Thereafter, the terminal calculates each layer of coded modulation symbols for CSI part 2 while considering each layer of coded modulation symbols for HARQ-ACK, CG-UCI, and CSI part 1.

[0331] When rate matching is performed according to each UCI type, the method for calculating the number of coded modulation symbols per layer varies depending on the repetition transmission type of the PUSCH on which the UCI is multiplexed and whether uplink data (uplink shared channel, hereinafter UL-SCH) is included. For example, when rate matching for HARQ-ACK is performed, the equation for obtaining the coded modulation symbol per layer according to the PUSCH on which the UCI is multiplexed is shown in the following equation (6).

[0332]

[0333] Equation (6) is an equation for obtaining a per-layer coded modulation symbol for HARQ-ACK multiplexed on PUSCH except for PUSCH transmission type B including repetition of UL-SCH, and equation (7) is an equation for obtaining a per-layer coded modulation symbol for HARQ-ACK multiplexed on PUSCH transmission type B including repetition of UL-SCH. Equation (8) is an equation for obtaining a per-layer coded modulation symbol for HARQ-ACK multiplexed on PUSCH not including UL-SCH.

[0334] In equation (6), O ACK is the number of HARQ-ACK bits. ACK is the number of CRC bits used for HARQ-ACK. is the beta offset for HARQ-ACK and is related to Same. C UL-SCH is the number of UL-SCH code blocks used for PUSCH transmission, and K r is the code block size of the rth code block. Indicates the number of resource elements available for UCI transmission in symbol 1, and this number is determined by the presence or absence of DMRS and PTRS in symbol 1. If symbol 1 includes DMRS, then For symbol l not including DMRS, is the number of subcarriers of the bandwidth scheduled in case of PUSCH transmission, and is the number of subcarriers including PTRS in symbol 1. Indicates the total number of PUSCH symbols. α is a higher layer parameter scaling, which refers to the ratio of resources on which UCI can be multiplexed among all resources used for PUSCH transmission. 0 Indicates the index of the first symbol that does not include a DMRS after the first DMRS.

[0335] In equation (7), Indicates the number of resource elements available for UCI transmission for nominal repetition and is 0 for symbols including DMRS and 0 for symbols not including DMRS and is the number of subcarriers including PTRS in symbol 1 for PUSCH assuming nominal repetition. Indicates the total number of nominally repeated symbols used for PUSCH. Indicates the number of resource elements available for UCI transmission for actual repetition, which is 0 for symbols including DMRS and satisfies and is the number of subcarriers including PTRS in symbol 1 used for the actual repetition of PUSCH. Indicates the total number of actual repeated symbols used for PUSCH.

[0336] In equation (8), R is the PUSCH code rate, and Q m is the modulation order of PUSCH.

[0337] The number of coded modulation symbols per layer for which rate matching of CSI part 1 has been performed can be calculated similarly to HARQ-ACK, but the maximum number of allocable resources among all resources can be reduced to a value obtained by excluding the number of coded modulation symbols for HARQ-ACK / CG-UCI. Depending on the repeated PUSCH transmission type and whether UL-SCH is included, the equations for the coded modulation symbols per layer for CSI part 1 are shown in equations (9), (10), (11), and (12).

[0338]

[0339]

[0340] Equation (9) is used to obtain the per-layer coded modulation symbol for CSI part 1 multiplexed on PUSCH except for repeated PUSCH transmission type B including UL-SCH, and equation (10) is used to obtain the per-layer coded modulation symbol for CSI part 1 multiplexed on repeated PUSCH transmission type B including UL-SCH. Equation (11) is used to obtain the per-layer coded modulation symbol for multiplexing CSI part 1 when CSI part 1 and CSI part 2 are multiplexed on PUSCH not including UL-SCH. Equation (12) is an equation for obtaining the per-layer coded modulation symbol for multiplexing CSI part 1 when CSI part 2 is not multiplexed on PUSCH not including UL-SCH. In equation (9), O CSI-1 and L CSI-1 They refer to the number of bits used for CSI part 1 and the number of CRC bits used for CSI part 1, respectively. is the beta offset for CSI part 1 and is related to Same. Q′ ACK / CG-UCI is the number of coded modulation symbols per layer calculated for HARQ-ACK and / or CG-UCI. The other parameters are the same as the aforementioned parameters required for calculating the number of coded modulation symbols per layer for HARQ-ACK.

[0341] The number of coded modulation symbols per layer for which rate matching of CSI part 2 has been performed can also be calculated similarly to CSI part 1, but the maximum number of allocable resources among all resources can be reduced to a value obtained by excluding the number of coded modulation symbols for CSI part 2 and the number of coded modulation symbols for HARQ-ACK / CG-UCI. Depending on the repeated PUSCH transmission type and whether UL-SCH is included, the equations for the coded modulation symbols per layer for CSI part 1 are shown in equations (13), (14), and (15).

[0342]

[0343] Equation (13) is used to obtain the per-layer coded modulation symbol for CSI part 2 multiplexed on PUSCH except for PUSCH transmission type B including repetition of UL-SCH, and equation (14) is used to obtain the per-layer coded modulation symbol for CSI part 2 multiplexed on PUSCH transmission type B including repetition of UL-SCH. Equation (15) is an equation for obtaining the per-layer coded modulation symbol for CSI part 2 multiplexed on PUSCH not including UL-SCH. In equation (13), O CSI-2 and L CSI-2 They refer to the number of bits used for CSI part 2 and the number of CRC bits used for CSI part 2, respectively. is the beta offset for CSI part 2 and is related to The other parameters are the same as the aforementioned parameters 1 required for calculating the number of coded modulation symbols per layer for HARQ-ACK and CSI part 1.

[0344] The number of coded modulation symbols per layer for which rate matching of the CG-UCI has been performed can also be calculated similarly to HARQ-ACK. The equation for obtaining the coded modulation symbols per layer for the CG-UCI multiplexed on the PUSCH including the UL-SCH is shown in equation (16).

[0345]

[0346] In equation (16), O CG-UCI and L CG-UCI They respectively refer to the number of CG-UCI bits and the number of CRC bits used for CG-UCI. is the beta offset for CG-UCI and is related to The other parameters are the same as those required for calculating the number of coded modulation symbols per layer for HARQ-ACK.

[0347] When HARQ-ACK and CG-UCI are multiplexed on PUSCH including UL-SCH, the number of coded modulation symbols per layer for which rate matching has been performed for HARQ-ACK and CG-UCI can be calculated as in the following equation (17).

[0348]

[0349] In equation (17), is the beta offset for HARQ-ACK and is equal to The other parameters are the same as the aforementioned parameters required to calculate the number of coded modulation symbols per layer for HARQ-ACK.

[0350] After calculating the number of coded modulation symbols per layer according to each UCI type as described above, the number of coded modulation symbols per layer can be calculated based on E UCI =N L *Q′*Q m To calculate the number of digits E used for the entire UCI UCI , where N L is the number of PUSCH transmission layers, Q m is the modulation order, and Q′ is the value that can be obtained according to ACK , Q′ CSI-1 , Q′ CSI-2 , or Q′ CG-UCI The number of coded modulation symbols per layer of the UCI type.

[0351] Related to UE capability reporting

[0352] In LTE and NR, when the terminal is connected to the serving base station, the terminal can perform a process of reporting the capabilities supported by the base station to the base station. In the following description, this is referred to as UE capability reporting.

[0353] The base station may send a UE capability inquiry message for requesting a capability report to the connected terminal. The message may include a UE capability request for each radio access technology (RAT) type of the base station. The request for each RAT type may include supported band combination information, etc. In the case of a UE capability inquiry message, UE capabilities may be requested for multiple RAT types via a container of a single RRC message sent by the base station, or the base station may include multiple UE capability inquiry messages with UE capability requests for each RAT type to transmit them to the terminal. That is, the UE capability inquiry is repeated multiple times within one message, and the terminal may configure the corresponding UE capability information message and report it multiple times. In the next generation mobile communication system, a UE capability request for multi-RAT dual connection (MR-DC) including NR, LTE and E-UTRA NR dual connection (EN-DC) may be made. The UE capability inquiry message is usually initially sent after the terminal connects to the base station, but may be requested by the base station under any conditions when necessary.

[0354] As described above, the terminal that receives the request for UE capability report from the base station configures the UE capability according to the RAT type and frequency band information requested from the base station. Hereinafter, a method for configuring UE capability by the terminal in the NR system is described.

[0355] 1. If the terminal receives a list of LTE and / or NR bands from the base station via UE capabilities, the terminal configures a band combination (BC) for EN-DC and NR standalone (SA). That is, the terminal configures a candidate list of BCs for EN-DC and NR SA based on the bands requested from the base station via FreqBandList. These bands have priority in the order described in FreqBandList.

[0356] 2. If the base station requests UE capability reporting by setting the "eutra-nr-only" flag or the "eutra" flag, the terminal completely removes the NR SA BC from the candidate list of configured Bcs. This only happens when the LTE base station (eNB) requests "eutra" capability.

[0357] 3. Thereafter, the terminal removes the fallback BC from the candidate list of BCs configured in the above operation. Here, the fallback BC refers to the BC that can be obtained by removing the frequency band corresponding to at least one SCell from any BC, and since the BC before removing the frequency band corresponding to at least one SCell can already cover the fallback BC, this can be omitted. This operation also applies to MR-DC, i.e., the LTE band. The remaining BCs after this operation constitute the final "candidate BC list".

[0358] 4. The terminal selects the BC to be reported by selecting the BC that meets the requested RAT type from the final "candidate BC list". In this operation, the terminal configures the supportedBandCombinationList in a predetermined order. That is, the terminal configures the BC to be reported and the UE capabilities according to the preconfigured rat-Type order (nr->eutra-nr->eutra). The terminal configures featureSetCombination for the configured supportedBandCombinationList and configures the "candidate feature set combination" list from the candidate BC list from which the fallback BC (including equal or lower level capabilities) has been removed. The "candidate feature set combination" may include feature set combinations for NR and UTRA-NR BCs, and may be obtained from the feature set combinations of UE-NR-capabilities and UE-MRDC-capabilities containers.

[0359] 5. If the requested rat-Type is eutra-nr and affects, featureSetCombinations is included in both containers of UE-MRDC-Capabilities and UE-NR-Capabilities. However, feature sets for NR are only included in UE-NR-Capabilities.

[0360] After configuring the UE capabilities, the terminal transmits a UE capability information message including the UE capabilities to the base station. The base station performs appropriate scheduling and transmission or reception management for the corresponding terminal at a later time based on the UE capabilities received from the terminal.

[0361] CA / DC related

[0362] Fig.10 is a diagram illustrating a radio protocol structure of a base station and a terminal in single cell, carrier aggregation, and dual connectivity scenarios according to an embodiment.

[0363] Reference Fig.10 The wireless protocol of the next-generation mobile communication system includes the NR Service Data Adaptation Protocol (SDAP) S25 and S70, NR Packet Data Convergence Protocol (PDCP) S30 and S65, NR Radio Link Control (RLC) S35 and S60, and NR Medium Access Control (MAC) S40 and S55 layers located in the terminal and NR base station respectively.

[0364] The main functions of NR SDAP S25 and S70 may include some of the following functions.

[0365] -User data transmission function (transmission of user plane data)

[0366] - Functionality to map QoS flows and data bearers for uplink and downlink (mapping between QoS flows and DRBs for both DL and UL)

[0367] - Function to mark QoS flow ID in uplink and downlink (mark QoS flow ID in both DL packet and UL packet)

[0368] - Functionality to map Reflective QoS flows to data bearers for uplink SDAP PDUs (Reflective QoS flows to DRB mapping for UL SDAPPDUs)

[0369] Regarding the SDAP layer device, the terminal can be configured via an RRC message with a header of whether to use the SDAP layer device for each PDCP layer device, for each bearer or for each logical channel, or a function of using the SDAP layer device, and if the SDAP header is configured, the NAS QoS reflection configuration 1-bit indicator (NAS reflective QoS) and the AS QoS reflection configuration 1-bit indicator (AS reflective QoS) in the SDAP header can be indicated to enable the terminal to update or reconfigure the mapping information for data bearers and QoS flows in the uplink and downlink. The SDAP header may include QoS flow ID information indicating QoS. QoS information can be used as data processing priority, scheduling information, etc. to support smooth services.

[0370] Main functions of NR PDCP S30 and S65 may include some of the following functions.

[0371] -Header compression and decompression function (ROHC only)

[0372] -User data transmission function (transmission of user data)

[0373] - Sequential delivery function (in-sequence delivery of upper layer PDUs)

[0374] - Out-of-sequence delivery function (out-of-sequence delivery of upper layer PDUs)

[0375] - Reordering function (reordering received PDCP PDUs)

[0376] -Duplicate detection function (duplicate detection of lower layer SDU)

[0377] -Retransmission function (retransmission of PDCP SDU)

[0378] -Encryption and decryption functions (encryption and decryption)

[0379] - Timer-based SDU discard functionality (Timer-based SDU discard in uplink)

[0380] In the above, the reordering function of the NR PDCP device refers to a function of reordering the PDCP PDUs received from the lower layer in order based on the PDCP sequence number (SN), and may include a function of transmitting data to a higher layer according to the reordered sequence. Alternatively, the reordering function of the NR PDCP device may include a function of directly transmitting without considering the sequence, may include a function of reordering the sequence to record the lost PDCP PDU, may include a function of reporting the status of the lost PDCP PDU to the transmitting side, and may include a function of requesting retransmission of the lost PDCP PDU.

[0381] The main functions of NR RLC S35 and S60 may include some of the following functions.

[0382] -Data transmission function (transmission of upper layer PDU);

[0383] - Sequential delivery function (in-sequence delivery of upper layer PDUs)

[0384] - Out-of-sequence delivery function (out-of-sequence delivery of upper layer PDUs)

[0385] -ARQ function (error correction through ARQ)

[0386] - Concatenation, segmentation and reassembly function (concatenation, segmentation and reassembly of RLC SDU)

[0387] - Re-segmentation function (resegmentation of RLC data PDU)

[0388] - Reordering function (reordering of RLC data PDU)

[0389] - Duplicate detection function

[0390] -Error detection function (protocol error detection)

[0391] -RLC SDU discard function

[0392] -RLC reconstruction function

[0393] In the above, the in-sequence delivery function of the NR RLC device may refer to a function of sequentially transmitting the RLC SDUs received from the lower layer to a higher layer. The in-sequence delivery function of the NR RLC device may include a function of reassembling and transmitting the received RLC SDU when an original RLC SDU is segmented into multiple RLC SDUs and then received, may include a function of reordering the received RLC PDU according to the RLC sequence number (SN) or the PDCP sequence number (SN), may include a function of reordering the sequence and recording the lost RLC PDU, may include a function of reporting the status of the lost RLC PDU to the transmitting side, and may include a function of requesting retransmission of the lost RLC PDU. The in-sequence delivery function of the NR RLC device may include a function of sequentially transmitting only the RLC SDUs before the lost RLC SDU to a higher layer when there is a lost RLC SDU, or may include a function of sequentially transmitting all RLC SDUs received before the timer starts to a higher layer if a predetermined timer expires even if there is a lost RLC SDU. Alternatively, the in-sequence delivery function of the NR RLC device may include a function of sequentially transmitting all currently received RLC SDUs to a higher layer even if there is a lost RLC SDU if a predetermined timer expires. In the above, the RLC PDUs can be processed in the order in which they are received (in the order of arrival regardless of the order of sequence number or sequence number) and can be delivered to the PDCP device regardless of the order (out-of-sequence delivery). In the case of segmentation, the segments stored in the buffer or to be received at a later time can be received, reconfigured into one complete RLC PDU, processed and then delivered to the PDCP device. The NR RLC layer may not include a cascading function, and the function may be performed in the NR MAC layer, or may be replaced by a multiplexing function of the NR MAC layer.

[0394] In the above, the out-of-sequence delivery function of the NR RLC device refers to a function of directly delivering the RLC SDU received from the lower layer to the higher layer regardless of the order, and may include a function of reassembling the divided RLC SDU when an original RLC SDU is divided into multiple RLC SDUs and then received and then delivering it, and may include a function of storing the RLC SN or PDCP SN of the received RLC PDU and arranging it so as to record the lost RLC PDU.

[0395] NR MAC S40 and S55 can be connected to multiple NR RLC layer devices included in one terminal, and the main functions of NR MAC can include some of the following functions.

[0396] - Mapping function (mapping between logical channels and transport channels);

[0397] -Multiplexing and demultiplexing functions (multiplexing / demultiplexing of MAC SDU)

[0398] -Scheduling information reporting function

[0399] -HARQ function (error correction through HARQ)

[0400] - Priority handling between logical channels (priority handling between logical channels of a UE)

[0401] - Priority handling between terminals (priority handling between UEs with dynamic scheduling)

[0402] -MBMS service identification function

[0403] -Transmission format selection function

[0404] - Fill function

[0405] The NR PHY layers S45 and S50 may perform channel coding and modulation on higher layer data, form the channel-coded and modulated higher layer data into OFDM symbols, and send the OFDM symbols via a wireless channel, or may perform demodulation and channel decoding on OFDM symbols received through a wireless channel and transmit them to a higher layer.

[0406] The detailed structure of the wireless protocol structure can be changed differently according to the carrier (or cell) operation method. For example, when the base station sends data to the terminal based on a single carrier (or cell), the base station and the terminal use a protocol structure with a single structure for each layer, as shown in S00. On the other hand, when the base station sends data to the terminal based on carrier aggregation (CA) using multiple carriers in a single TRP, the base station and the terminal use a protocol structure in which a single structure is used before the RLC layer but the PHY layer is multiplexed via the MAC layer, as shown in S10. As another example, when the base station sends data to the terminal based on dual connectivity (DC) using multiple carriers in multiple TRPs, the base station and the terminal use a protocol structure in which a single structure is used before the RLC layer but the PHY layer is multiplexed via the MAC layer, as shown in S20.

[0407] Related to NC-JT

[0408] According to an embodiment, non-coherent joint transmission (NC-JT) can be used for a terminal to receive PDSCH from multiple TRPs.

[0409] Unlike conventional systems, 5G wireless communication systems are able to support not only services that require high transmission rates, but also services with very short transmission delays and services that require high connection density. In a wireless communication network including multiple cells, transmit and receive points (TRPs) or beams, collaborative communication (coordinated transmission) between corresponding cells, TRPs or / and beams can meet various service requirements by enhancing the strength of the signal received by the terminal or efficiently performing interference control between corresponding cells, TRPs or / and beams.

[0410] Joint transmission (JT) is a representative transmission scheme of the aforementioned cooperative communication, and is a scheme for improving the strength or throughput of a signal received by a terminal by sending a signal to one terminal via multiple different cells, TRPs and / or beams. In this case, the channel between the terminal and the corresponding cell, TRP and / or beam may have significantly different characteristics, and in particular, non-coherent joint transmission (NC-JT) supporting non-coherent precoding between the corresponding cells, TRPs and / or beams may require separate precoding, MCS, resource allocation, TCI indication, etc. according to the channel characteristics of each link between the terminal and the corresponding cell, TRP and / or beam.

[0411] The aforementioned NC-JT transmission can be applied to at least one of the downlink data channel (PDSCH), the downlink control channel (PDCCH), the uplink data channel (PUSCH) and the uplink control channel (PUCCH). During PDSCH transmission, transmission information such as precoding, MCS, resource allocation and TCI is indicated via DL DCI, and for NC-JT transmission, the transmission information should be indicated independently for each cell, TRP and / or beam. This becomes the main factor in increasing the payload required for DL ​​DCI transmission, which may adversely affect the reception performance of the PDCCH that transmits the DCI. Therefore, in order to support JT of PDSCH, it is necessary to carefully design the trade-off between the amount of DCI information and the control information reception performance.

[0412] Fig.11 is a diagram illustrating an example of antenna port configuration and resource allocation for PDSCH transmission using cooperative communication in a wireless communication system according to an embodiment.

[0413] Reference Fig.11 , an example for PDSCH transmission is described for each joint transmission (JT) scheme, and an example of wireless resource allocation for each TRP is illustrated.

[0414] Reference Fig.11 , illustrating an example 1100 for coherent joint transmission (C-JT) supporting interfering coding between corresponding cells, TRPs, or / and beams.

[0415] For C-JT, TRP A 1105 and TRP B 1110 transmit a single data (PDSCH) to the terminal 1115, and joint precoding may be performed in multiple TRPs. This may indicate that DMRS is transmitted through exactly the same DMRS port so that TRP A 1105 and TRP B 1110 transmit the same PDSCH. For example, TRP A 1105 and TRP B 1110 may transmit DRMS ​​to the terminal through DMRS port A and DMRS port B, respectively. In this case, the terminal may receive a piece of DCI information for receiving a PDSCH demodulated based on the DMRS transmitted through DMRS port A and DMRS port B.

[0416] Reference Fig.11 , illustrating an example 1120 of supporting non-coherent joint transmission (NC-JT) with non-coherent intercoding between corresponding cells, TRPs and / or beams for PDSCH transmission.

[0417] For NC-JT, PDSCH is sent to terminal 1135 for each cell, TRP and / or beam, and a separate precoding may be applied to each PDSCH. Each cell, TRP and / or beam sends different PDSCHs or different PDSCH layers to the terminal, thereby improving throughput compared to a single cell, TRP and / or beam transmission. Each cell, TRP and / or beam repeatedly sends the same PDSCH to the terminal, thereby improving reliability compared to a single cell, TRP and / or beam transmission. In the following, for ease of description, cells, TRPs and / or beams are collectively referred to as TRPs.

[0418] In this case, various wireless resource allocations can be considered, such as the case 1140 where all the frequency and time resources used in multiple TRPs for PDSCH transmission are the same, the case 1145 where the frequency and time resources used in multiple TRPs do not overlap at all, and the case 1150 where some of the frequency and time resources used in multiple TRPs overlap.

[0419] For NC-JT support, various types, structures, and relationships of DCI may be considered to assign multiple PDSCHs to a single terminal simultaneously.

[0420] Fig.12 2. It is a diagram illustrating an example of the configuration of DCI for sending NC-JT of different PDSCHs or different PDSCH layers to a terminal in a wireless communication system for corresponding TRP according to an embodiment.

[0421] Reference Fig.12, case #1 1200 is an example of sending control information for the PDSCH sent in the additional (N-1) TRPs independently of the control information for the PDSCH sent in the serving TRP in a situation where different (N-1) PDSCHs are sent from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) in addition to the serving TRP (TRP#0) used during a single PDSCH transmission. That is, the terminal can obtain control information for the PDSCH sent from different TRPs (TRP#0 to TRP#(N-1)) via each independent DCI (DCI#0 to DCI#(N-1)). The formats of the independent DCIs may be the same or different from each other, and the payloads of the DCIs may also be the same or different from each other. In the aforementioned case #1, each PDSCH control or allocation freedom can be fully guaranteed, but if each DCI is sent in a different TRP, a coverage difference of each DCI occurs and the reception performance may be degraded as a result.

[0422] Case #2 1205 shows an example depending on control information for PDSCH, where, in a situation where (N-1) different PDSCHs are transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) in addition to the serving TRP (TRP#0) used during a single PDSCH transmission, control information (DCI) for each PDSCH of the additional (N-1) TRPs is transmitted, and each DCI is transmitted from the serving TRP.

[0423] For example, DCI#0, which is control information for the PDSCH sent from the serving TRP (TRP#0), includes all information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2, but shortened DCI (hereinafter sDCI) (sDCI#0 to sDCI#(N-2)), which is control information for the PDSCH sent from the collaborative TRP (TRP#1 to TRP#(N-1)), may include only some of the information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2. Therefore, for the sDCI for sending control information for the PDSCH sent for the collaborative TRP, the payload is small compared to the normal DCI (nDCI) for sending control information related to the PDSCH sent from the serving TRP, and thus reserved bits may be included when compared to the nDCI.

[0424] In the aforementioned case #2, each PDSCH control or allocation freedom can be limited according to the content of the information elements included in the sDCI, but since the reception performance of sDCI is better than that of nDCI, the probability of coverage differences in each DCI can be reduced.

[0425] Case #3 1210 shows an example depending on control information for PDSCH, where in a case where (N-1) different PDSCHs are transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) in addition to the serving TRP (TRP#0) used during a single PDSCH transmission, each control information for the PDSCH of the (N-1) additional TRPs is transmitted, and DCI is transmitted from the serving TRP.

[0426] For example, DCI#0, which is control information for the PDSCH sent from the serving TRP (TRP#0), includes all information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2, and for control information for the PDSCH sent from the collaborative TRP (TRP#1 to TRP#(N-1)), only some of the information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2 may be collected into one "secondary" DCI (sDCI) for transmission. For example, the sDCI may include at least one piece of HARQ-related information such as frequency domain resource assignment, time domain resource assignment, and MCS of the collaborative TRP. In addition, information not included in the sDCI, such as a BWP indicator or a carrier indicator, may be based on the DCI of the serving TRP (DCI#0, normal DCI, or nDCI).

[0427] In case #3 1210, each PDSCH control or allocation freedom can be limited according to the content of the information element included in the sDCI, but the sDCI reception performance can be adjustable and the complexity of the DCI blind decoding of the terminal can be reduced compared to case #1 1200 or case #2 1205.

[0428] Case #4 1215 is an example of sending control information for PDSCHs sent from (N-1) additional TRPs in the same DCI (long DCI) as the DCI used for control information for PDSCHs sent from the serving TRP in a situation where (N-1) different PDSCHs are sent from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) in addition to the serving TRP (TRP#0) used during a single PDSCH transmission. That is, the terminal can obtain control information for PDSCHs sent from different TRPs (TRP#0 to TRP#(N-1)) via a single DCI. For case #4 1215, the complexity of DCI blind decoding of the terminal may not increase, but the PDSCH control or allocation freedom can be low, so that the number of collaborative TRPs is limited according to the long DCI payload limitation.

[0429] In the following description and embodiments, sDCI may refer to various auxiliary DCIs, such as shortened DCI, auxiliary DCI and normal DCI (the aforementioned DCI formats 1_0 to 1_1) including PDSCH control information sent in a coordinated TRP, and if no specific restrictions are specified, the description applies similarly to various auxiliary DCIs.

[0430] In the following description and embodiments, the aforementioned case #1 1200, case #2 1205, and case #3 1210 in which one or more DCI (PDCCH) are used for NC-JT support are classified as multi-PDCCH-based NC-JT, and the aforementioned case #4 1215 in which a single DCI (PDCCH) is used for NC-JT support may be classified as single PDCCH-based NC-JT. In multi-PDCCH-based PDSCH transmission, a CORESET in which a DCI for a service TRP (TRP#0) is scheduled and a CORESET in which a DCI for a collaborative TRP (TRP#1 to TRP#(N-1)) is scheduled may be distinguished. As a method for distinguishing the CORESETs, there may be a method for distinguishing via a higher layer indicator for each CORESET, a method for distinguishing via a beam configuration for each CORESET, and the like. In addition, in NC-JT based on a single PDCCH, a single DCI is used to schedule a single PDSCH with multiple layers instead of scheduling multiple PDSCHs, and the aforementioned multiple layers can be sent from multiple TRPs. In this case, the connection relationship between the layer and the TRP used to send the layer can be indicated via a transmission configuration indicator (TCI) indication for the layer.

[0431] In various embodiments of the present disclosure, "collaborative TRP" may be replaced with various terms such as "collaborative panel" or "collaborative beam" when actually applied.

[0432] In various embodiments of the present disclosure, "when NC-JT is applied" can be interpreted in various ways according to situations such as: "when the terminal simultaneously receives one or more PDSCHs in one BWP", "when the terminal simultaneously receives PDSCH based on two or more transmission configuration indicator (TCI) indications in one BWP", "when the PDSCH received by the terminal is associated with one or more DMRS port groups", etc., but it is used as an expression for convenient description.

[0433] In the present disclosure, the wireless protocol structure for NC-JT can be used in various ways according to the TRP deployment scenario. For example, if there is no backhaul delay or a small backhaul delay between the cooperating TRPs, a wireless protocol structure similar to Fig.10On the other hand, if the backhaul delay between the cooperative TRPs is so large that the backhaul delay cannot be ignored (for example, when the information exchange between the cooperative TRPs (such as CSI, scheduling, and HARQ-ACK) takes 2ms or more), then a method similar to Fig.10 The S20 method is possible by using an independent structure for each TRP from the RLC layer to ensure a delay-robust characteristic (similar to the DC method).

[0434] A terminal supporting C-JT / NC-JT can receive C-JT / NC-JT related parameters, setting values, etc. from a higher layer configuration, and can set the RRC parameters of the terminal based on the parameters, setting values, etc. For higher layer configuration, the terminal can use UE capability parameters, such as tsi-StatePDSCH. Here, the UE capability parameter (e.g., tci-StatePDSCH) can define the TCI state for the purpose of PDSCH transmission, and the number of TCI states can be configured as 4, 8, 16, 32, 64 and 128 in FR1, and configured as 64 and 128 in FR2, and among the configured number, up to 8 states that can be indicated by 3 bits of the TCI field in the DCI can be configured via a MAC CE message. The maximum value of 128 refers to the value indicated by maxNumberConfiguredTCIstatesPerCC in the parameter tci-StatePDSCH included in the terminal's capability signaling. In this way, a series of configuration processes from higher layer configuration to MAC CE configuration can be applied to a beamforming change command or beamforming indication for at least one PDSCH in one TRP.

[0435] Multi-TRP based on multi-DCI

[0436] As an embodiment of the present disclosure, a multi-TRP transmission method based on multiple DCI is described. In the multi-TRP transmission method based on multiple DCI, a downlink control channel for NC-JT transmission can be configured based on multiple PDCCHs.

[0437] In multi-PDCCH based NC-JT, when transmitting DCI for PDSCH scheduling for each TRP, a CORE SET or search space distinguished for each TRP may be provided. The CORE SET or search space for each TRP can be configured as at least one of the following cases.

[0438] *Higher layer index configuration for each CORESET: The CORESET configuration information configured via a higher layer may include an index value, and the TRP used for PDCCH transmission in the corresponding CORESET may be distinguished by the configured index value for each CORESET. That is, in a CORESET set with the same higher layer index value, it may be considered that the same TRP transmits a PDCCH, or transmits a PDCCH for scheduling a PDSCH of the same TRP. The aforementioned index for each CORESET may be named CORESETPoolIndex, and for a CORESET that has been configured with the same CORESETPoolIndex value, it may be considered that the PDCCH is transmitted from the same TRP. For a CORESET that has not yet configured a CORESETPoolIndex value, it may be considered that a default value of CORESETPoolIndex has been configured, where the default value is 0.

[0439] **In the present disclosure, if there are multiple CORESETs, each of which has more than one CORESETPoolIndex, that is, if each CORESET has a different CORESETPoolIndex, and multiple CORESETs are included in the PDCCH-Config as a higher layer signaling, the terminal can assume that the base station can use a multi-TRP sending method based on multi-DCI.

[0440] **Different from this, in the present disclosure, if there is a CORESETPoolIndex that each of multiple CORESETs has, and multiple CORESETs are included in the PDCCH-Config which is a higher layer signaling, that is, if all CORESETs have a CORESETPoolIndex of 0 or 1, the terminal can consider that the base station uses a single TRP to perform transmission without using a multi-TRP transmission method based on multi-DCI.

[0441] *Multiple PDCCH-Config configurations: Multiple PDCCH-Configs in one BWP can be configured, and each PDCCH-Config can include a PDCCH configuration for each TRP. That is, a list of CORESETs for each TRP and / or a list of search spaces for each TRP can be configured in one PDCCH-Config, and one or more CORESETs and one or more search spaces included in one PDCCH-Config can be considered to correspond to a specific TRP.

[0442] *CORESET beam / beam group configuration: The TRP corresponding to the corresponding CORESET can be distinguished via the beam or beam group configured for each CORESET. For example, if the same TCI state is configured in multiple CORESETs, it can be considered that the CORESET is transmitted via the same TRP, or the PDCCH for scheduling the PDSCH of the same TRP is transmitted from the corresponding CORESET.

[0443] *Search space beam / beam group configuration: A beam or beam group can be configured for each search space, and the TRP used for each search space can be distinguished based on the configured beam or beam group. For example, when the same beam / beam group or TCI state is configured in multiple search spaces, it can be considered that the same TRP sends PDCCH in the corresponding search space, or the PDCCH for scheduling the PDSCH of the same TRP is sent in the corresponding search space.

[0444] By distinguishing the CORESET or search space used for each TRP as described above, the PDSCH and HARQ-ACK information of each TRP can be classified, and based on this, the HARQ-ACK codebook can be independently generated for each TRP and the PUCCH resources can be used independently.

[0445] The aforementioned configuration may be independent for each cell or each BWP. For example, although two different CORESETPoolIndex values ​​are configured for the PCell, the CORESETPoolIndex value may not be configured for a specific SCell. In this case, it can be considered that NC-JT transmission is configured for the PCell, but NC-JT transmission is not configured for the SCell in which the CORESETPoolIndex value is not configured.

[0446] The PDSCH TCI state activation / deactivation MAC-CE applicable to the multi-TRP transmission method based on multi-DCI can follow Figure 7. If the terminal is not configured with the CORESETPoolIndex for each of all CORESETs in the higher layer signaling of the PDCCH-Config, the terminal may ignore the CORESET pool ID field 755 in the corresponding MAC-CE 750. If the terminal is capable of supporting a multi-TRP transmission method based on multiple DCIs, that is, if the terminal has a CORESETPoolIndex in which the corresponding CORESET in the higher layer signaling of the PDCCH-Config is different, the terminal may activate the TCI state in the DCI included in the PDCCH transmitted from the CORESET having the same CORESETPoolIndex value as the CORESET pool ID field 755 value in the corresponding MAC-CE 750. For example, if the value of the CORESET pool ID field 755 in the MAC-CE 750 is 0, the TCI state in the DCI included in the PDCCH transmitted from the CORESET having the CORESETPoolIndex value of 0 may conform to the activation information of the MAC-CE.

[0447] If the terminal is configured to use a multi-DCI-based multi-TRP transmission method from a base station, that is, if there is more than one CORESETPoolIndex for each of a plurality of CORESETs included in the higher layer signaling of PDCCH-Config, or if each CORESET has a different CORESETPoolIndex, the terminal can recognize that there are the following restrictions for the PDSCH scheduled from the PDCCH in the corresponding CORESET with two different CORESETPoolIndex values.

[0448] 1) If the PDSCH indicated by the PDCCH in the corresponding CORESETs with two different CORESETPoolIndex values ​​completely or partially overlap, the terminal may apply the TCI state indicated by the corresponding PDCCH to different CDM groups. That is, two or more TCI states may not be applied to one CDM group.

[0449] 2) If the PDSCH indicated by the PDCCH in the corresponding CORESETs with two different CORESETPoolIndex values ​​overlap completely or partially, the terminal can expect that the actual number of frontloaded DMRS symbols, the actual number of additional DMRS symbols, the actual position of the DMRS symbols and the DMRS type of the corresponding PDSCH may not be different from each other.

[0450] 3) The terminal can expect that the BWP indicated by the PDCCH in the corresponding CORESETs with two different CORESETPoolIndex values ​​is the same, and their subcarrier spacing may also be the same.

[0451] 4) The terminal may expect that the corresponding PDCCH completely includes information about the PDSCH scheduled from the PDCCH in the corresponding CORESET with two different CORESETPoolIndex values.

[0452] Multiple TRPs based on a single DCI

[0453] In the multi-TRP transmission method based on a single DCI, the downlink control channel for NC-JT transmission can be configured based on a single PDCCH.

[0454] In a multi-TRP transmission method based on a single DCI, a PDSCH transmitted by multiple TRPs can be scheduled via one DCI. In this case, the number of TCI states can be used to indicate the method of the number of TRPs that transmit the corresponding PDSCH. That is, if the number of TCI states indicated in the DCI for scheduling the PDSCH is two, NC-JT transmission based on a single PDCCH can be considered, and if the number of TCI states is one, a single TRP transmission can be considered. The TCI state indicated by the DCI may correspond to one or two TCI states among the TCI states activated via MAC-CE. If the TCI state of the DCI corresponds to two TCI states activated via MAC-CE, a correspondence is established between the TCI code point indicated in the DCI and the TCI state activated via MAC-CE, and there may be two TCI states activated via MAC-CE, which correspond to the TCI code point.

[0455] As another example, if at least one code point among all code points of the TCI state field in the DCI indicates two TCI states, the terminal may assume that the base station may perform transmission according to a multi-TRP method based on a single DCI. In this case, at least one code point indicating two TCI states in the TCI state field may be activated via an enhanced PDSCH TCI state activation / deactivation MAC-CE.

[0456] Fig.13 The diagram illustrates the enhanced PDSCH TCI state activation / deactivation MAC-CE structure. The meaning of each field in the corresponding MAC CE and the configurable value for each field are shown in Table 39 below.

[0457] [Table 39]

[0458]

[0459] Reference Fig.13 , if the value of the C0 field 1305 is 1, the corresponding MAC-CE may include a field TCI state ID0,2 1315 in addition to the field TCI state ID0,1 1310. This may indicate that TCI state ID0,1 and TCI state ID0,2 are activated for the zeroth code point of the TCI state field included in the DCI, and if the base station indicates the corresponding code point to the terminal, the terminal may receive an indication of two TCI states. If the value of the C0 field 1305 is 0, the corresponding MAC-CE may not include the field TCI state ID0,2 1315, and this indicates that one TCI state corresponding to TCI state ID0,1 is activated for the zeroth code point of the TCI state field included in the DCI.

[0460] The above configuration may be independent for each cell or each BWP. For example, a PCell may have up to two activated TCI states corresponding to one TCI code point, whereas a specific SCell may have up to one activated TCI state corresponding to one TCI code point. In this case, it may be considered that NC-JT transmission is configured for the PCell, whereas NC-JT transmission is not configured for the aforementioned SCell.

[0461] Method for distinguishing multiple TRP repeated PDSCH transmission schemes (TDM / FDM / SDM) based on single DCI

[0462] A method for distinguishing a multi-TRP repetition PDSCH transmission scheme based on a single DCI is described below. The terminal can be indicated with different multi-TRP repetition PDSCH transmission schemes based on a single DCI (e.g., TDM, FDM, and SDM) according to a higher layer signaling configuration and a value indicated from a base station via a DCI field. Table 40 shows a method for distinguishing a single TRP-based scheme and a multi-TRP-based scheme indicated to a terminal according to a value of a specific DCI field and a higher layer signaling configuration.

[0463] [Table 40]

[0464]

[0465] In Table 40, each column can be described as follows.

[0466] -TCI state number (column 2): This refers to the TCI state number indicated by the TCI state field in the DCI, and the TCI state number can be one or two.

[0467] - Number of CDM groups (3rd column): This refers to the number of different CDM groups for the DMRS ports indicated by the Antenna Ports field in the DCI. The number of CDM groups can be 1, 2 or 3.

[0468] - repetitionNumber configuration and indication condition (column 4): There may be three conditions depending on whether repetitionNumber is configured for all TDRA entries that may be indicated by the time domain resource allocation field in the DCI and whether the actually indicated TDRA entry has the configuration of repetitionNumber.

[0469] *Condition 1: A case where at least one TDRA entry among all TDRA entries indicated by the time domain resource allocation field includes a configuration for repetitionNumber and a TDRA entry indicated by the time domain resource allocation field in the DCI includes a configuration for a repetitionNumber greater than 1.

[0470] *Condition 2: A case where at least one TDRA entry among all TDRA entries indicated by the time domain resource allocation field includes a configuration for repetitionNumber and a TDRA entry indicated by the time domain resource allocation field in the DCI does not include a configuration for repetitionNumber.

[0471] *Condition 3: All TDRA entries indicated by the time domain resource allocation field do not include the configuration for repetitionNumber

[0472] - Related to the configuration of repetitionScheme (5th column): repetitionScheme indicates whether repetitionScheme as higher layer signaling is configured. One of "tdmSchemeA", "fdmSchemeA" and "fdmSchemeB" can be configured for repetitionScheme as higher layer signaling.

[0473] -Transmission scheme indicated to the terminal (column 6): This refers to the single TRP or multi-TRP scheme indicated according to each combination (column 1) shown in Table 42 above.

[0474] *Single TRP: Single TRP refers to PDSCH transmission based on a single TRP. If the terminal is configured with pdsch-AggegationFactor in the higher layer signaling PDSCH-config, the terminal can be scheduled with repeated PDSCH transmission based on a single TRP as many times as configured. Otherwise, the terminal can be scheduled with a single PDSCH transmission based on a single TRP.

[0475] *Single TRP TDM Scheme B: This refers to repeated PDSCH transmission based on time resource division between time slots based on a single TRP. According to the described condition 1 related to repetitionNumber, the terminal repeatedly transmits PDSCH on time resources as many times as the number of time slots is greater than 1 and as many times as the repetitionNumber configured in the TDRA entry indicated by the time domain resource allocation field. In this case, the same starting symbol and symbol length of the PDSCH indicated by the TDRA entry are applied to each time slot as many times as the repetitionNumber, and the same TCI state is applied to each repeated PDSCH transmission. This scheme is similar to the time slot aggregation scheme in view of performing repeated PDSCH transmission between time slots on time slot resources, but is different from time slot aggregation in that whether the indication of repeated transmission can be dynamically determined based on the time domain resource allocation field in the DCI.

[0476] *Multi-TRP SDM: This refers to a PDSCH transmission scheme based on spatial resource division based on multiple TRPs. Multi-TRP SDM is a method for receiving from each TRP by dividing the layers, and although it is not a repeated transmission scheme, Multi-TRP SDM implements transmission at a low coding rate by increasing the number of layers in order to improve the reliability of PDSCH transmission. The terminal can receive PDSCH by respectively applying the two TCI states indicated by the TCI status field in the DCI to the two CDM groups indicated by the base station.

[0477] *Multi-TRP FDM Scheme A: This refers to a PDSCH transmission scheme based on frequency resource division based on multiple TRPs, and although unlike the multi-TRP SDM, in view of having one PDSCH transmission opportunity for repeated transmission, the multi-TRP FDM scheme A is a scheme for achieving transmission with high reliability at a low coding rate by increasing the amount of frequency resources. In the multi-TRP FDM scheme A, two TCI states indicated by the TCI state field in the DCI can be applied to frequency resources that do not overlap with each other, respectively. If the PRB bundling size is determined to be wideband, when the number of RBs indicated by the frequency domain resource allocation field is N, the terminal receives the first ceil (N / 2) RBs by applying the first TCI state and receives the remaining floor (N / 2) RBs by applying the second TCI state. Here, ceil (.) and floor (.) are operators for rounding the first decimal place. If the PRB bundling size is determined to be 2 or 4, even PRGs are received by applying the first TCI state, and odd PRGs are received by applying the second TCI state.

[0478] *Multi-TRP FDM Scheme B: This refers to a frequency resource partitioning-based repeated PDSCH transmission scheme based on multiple TRPs, wherein when there are two PDSCH transmission opportunities, the multi-TRP FDM scheme B can implement repeated PDSCH transmission at each opportunity. In the multi-TRP FDM scheme B, as in the multi-TRP FDM scheme A, the two TCI states indicated by the TCI state field in the DCI can be respectively applied to frequency resources that do not overlap with each other. If the PRB bundling size is determined to be wideband, when the number of RBs indicated by the frequency domain resource allocation field is N, the terminal receives the first ceil (N / 2) RBs by applying the first TCI state and receives the remaining floor (N / 2) RBs by applying the second TCI state. Here, ceil (.) and floor (.) are operators for rounding the first decimal place. If the PRB bundling size is determined to be 2 or 4, an even number of PRGs is received by applying the first TCI state, and an odd number of PRGs is received by applying the second TCI state.

[0479] *Multi-TRP TDM Scheme A: This refers to a repeated PDSCH transmission scheme in a time slot based on time resource division of multiple TRPs. The terminal has two PDSCH transmission opportunities in one time slot, and can determine the first reception opportunity based on the starting symbol and symbol length of the PDSCH indicated via the time domain resource allocation field in the DCI. The starting symbol of the second reception opportunity of the PDSCH can be a position where a symbol offset as much as StartingSymbolOffsetK as a higher layer signaling is applied from the last symbol of the first transmission opportunity, and the transmission opportunity can be determined according to the symbol length indicated thereby. If StartingSymbolOffsetK as a higher layer signaling is not configured, the symbol offset can be considered to be 0.

[0480] *Multi-TRP TDM Scheme B: This refers to a repeated PDSCH transmission scheme between time slots based on time resource division of multiple TRPs. The terminal has one PDSCH transmission opportunity in one time slot, and can receive repeated transmissions based on the same starting symbol and symbol length of PDSCH during the time slots of the repetitionNumber number of times indicated by the time domain resource allocation field in the DCI. If repetitionNumber is 2, for repeated PDSCH transmissions in the first time slot and the second time slot, the terminal can receive PDSCH by applying the first TCI state and the second TCI state, respectively. If repetitionNumber is greater than 2, the terminal can use different TCI state application schemes according to the configuration of tciMapping as higher layer signaling. If tciMapping is configured as cyclicMapping, the first TCI state and the second TCI state are applied to the first PDSCH transmission opportunity and the second PDSCH transmission opportunity, respectively, and this TCI state application method is similarly applicable to the remaining PDSCH transmission opportunities. If tciMapping is configured as sequentialMapping, the first TCI state is applied to the first PDSCH transmission timing and the second PDSCH transmission timing, and the second TCI state is applied to the third PDSCH transmission timing and the fourth PDSCH transmission timing, where this TCI state application method is applied to the remaining PDSCH transmission timings in the same manner.

[0481] Related to RLM RS

[0482] A method for selecting or determining a radio link monitoring (RLM) reference signal (RS) is provided, wherein the RLM RS may be configured or may not be configured. For each downlink BWP of the SPCell, the terminal may be configured with a set of RLM RSs from the base station via the RadioLinkMonitoringRS in the RadioLinkMonitoringConfig as higher layer signaling for each downlink BWP of the SPCell, and the specific higher layer signaling structure may follow the following Table 41.

[0483] [Table 41]

[0484]

[0485] Table 42 can be used to calculate the maximum number of SSBs per half frame (L max ) indicates the configurable or selectable number of RLM RSs for each specific use. As shown in Table 42, according to L maxvalue, the NLR-RLM RS can be used for link recovery or wireless link monitoring, and the NRLM RS in the NLR-RLM RS can be used for wireless link monitoring.

[0486] [Table 42]

[0487] As the maximum number of SS / PBCH blocks per half-frame, L max The function of N LR-RLM and N RLM

[0488]

[0489] If the terminal is not configured with RadioLinkMonitoringRS as higher layer signaling, and the terminal is configured with a TCI state for receiving a PDCCH in a control resource set, and if at least one CSI-RS is included in the TCI state, an RLM RS may be selected according to the following RLM RS selection method.

[0490] -1) If the activated TCI state to be used for PDCCH reception has one reference RS (ie, one activated TCI state has only one of QCL-Type A, B or C), the terminal may select the reference RS of the activated TCI state to be used for PDCCH reception as the RLM RS.

[0491] -2) If the activated TCI state to be used for PDCCH reception has two reference RSs (i.e., one activated TCI state has one of QCL-TypeA, B or C, and further has QCL-TypeD), the terminal may select the reference RS of QCL-TypeD as the RLM-RS. The terminal does not expect to configure two QCL-TypeD in one activated TCI state.

[0492] -3) The terminal does not expect an aperiodic or semi-persistent RS to be selected as an RLM RS.

[0493] -4) If L max =4, the terminal can choose NRLM RS (due to L maxis 4, so two can be selected). The RLM RS is selected from the reference RS of the TCI state configured in the control resource set for PDCCH reception based on RLM RS selection methods 1 to 3, wherein the search space to which the control resource set with a short period is linked is determined to have a high priority, and the RLM RS is selected from the reference RS of the TCI state configured in the control resource set linked to the search space with the shortest period. If there are multiple control resource sets linked to multiple search spaces with the same period, the RLM RS is selected from the reference RS of the TCI state configured in the high control resource set index.

[0494] Fig.14 is a diagram illustrating an RLM RS selection process according to an embodiment. Fig.14 The reference RSs of control resource sets #1 1405 to control resource sets #3 to 1407 linked to search spaces #1 1401 to search spaces #4 1404 having different periods within an activated downlink BWP and TCI states configured in each CORESET are illustrated. Based on RLM RS selection method 4, RLM RS selection uses the TCI state configured in the control resource set linked to the search space having the shortest period, but since search space #1 1401 and search space #3 1403 have the same period, the reference RS of the TCI state configured in control resource set #2 having a higher index between control resource set #1 1405 and control resource set #2 1406 linked to the corresponding search space can be used as the reference RS having the highest priority in RLM RS selection. In addition, since the TCI state configured in the control resource set #2 has only QCL-TypeA and its reference RS is a periodic RS, PCSI-RS#2 1410 may be first selected as the RLM RS according to RLM RS selection methods 1 and 3. The reference RS of QCL-TypeD may be a selection candidate RS from among the reference RSs of the TCI state configured in the control resource set #1 having a subsequent priority according to RLMRS selection method 2, but the corresponding RS is a semi-persistent RS 1409 and is therefore not selected as the RLM RS according to RLM RS selection method 3. Therefore, the reference RS of the TCI state configured in the control resource set #3 may be considered to have a subsequent priority, and the reference RS of QCL-TypeD may be a selection candidate according to the RLM RS selection method 2, and since the corresponding reference RS is a periodic RS, PCSI-RS#4 1412 may be selected as the second RLM RS according to the RLM RS selection method 3. Therefore, the finally selected RLM RS 1413 may be PCSI-RS#2 and PCSI-RS#4.

[0495] In the following description of the present disclosure, for the convenience of description, cells, transmission points, panels, beams, transmission directions, and / or the like that can be distinguished via higher layer / L1 parameters (such as TCI states or spatial relationship information) or indicators (such as cell IDs, TRP IDs, and panel IDs) may be described in a unified manner as transmission / reception points (TRPs), beams, or TCI states. Therefore, in actual applications, TRPs, beams, or TCI states may be appropriately replaced with one of the above terms.

[0496] Hereinafter, in the present disclosure, when determining whether cooperative communication is applied, the terminal may use various methods, wherein the (one or more) PDCCHs assigned to the PDSCH to which cooperative communication is applied have a specific format, the PDCCHs assigned to the PDSCH to which cooperative communication is applied include a specific indicator indicating whether cooperative communication is applied, the (one or more) PDCCHs assigned to the PDSCH to which cooperative communication is applied are scrambled by a specific RNTI, it is assumed that cooperative communication is applied in a specific segment indicated by a higher layer, etc. Hereinafter, for convenience of description, a case in which the terminal receives a PDSCH to which cooperative communication has been applied based on conditions similar to the above conditions is referred to as an NC-JT case.

[0497] In the following, the base station is a subject that performs resource allocation to the terminal, and may be at least one of a gNode B, a gNB, an eNodeB, a Node B, a BS, a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE, an MS, a cellular phone, a smart phone, a computer, or a multimedia system that can perform a communication function. In the following, the 5G system is used as an example to describe the embodiment, but the embodiment of the present disclosure may also be applied to other communication systems with similar technical backgrounds or channel types. For example, LTE or LTE-A mobile communications and mobile communication technologies developed after 5G may be included therein. Therefore, according to the determination made by those skilled in the art, without departing from the scope of the present disclosure, the embodiment of the present disclosure may be applied to other communication systems via some modifications. The content of the present disclosure is applicable in frequency division duplex (FDD) and time division duplex (TDD) systems. Hereinafter, higher signaling (or higher layer signaling) is a method of transmitting a signal from a base station to a terminal by using a physical layer downlink data channel or from a terminal to a base station by using a physical layer uplink data channel, and may be referred to as RRC signaling, PDCP signaling, or a medium access control (MAC) control element (MAC CE).

[0498] Hereinafter, in the following description, higher layer signaling may be signaling corresponding to at least one of the following signaling types or a combination thereof.

[0499] -MIB

[0500] -SIB or SIB X (X = 1, 2, ...)

[0501] -RRC

[0502] -MAC CE

[0503] In addition, the L1 signaling may be signaling corresponding to at least one signaling method using the following physical layer channels or signaling types or a combination of one or more thereof.

[0504] -PDCCH

[0505] -DCI

[0506] -Terminal-specific (UE-specific) DCI

[0507] -Group Common DCI

[0508] - Public DCI

[0509] - Scheduling DCI (e.g., DCI for scheduling downlink data or uplink data)

[0510] - Non-scheduled DCI (e.g., DCI not used for the purpose of scheduling downlink data or uplink data)

[0511] -PUCCH

[0512] -UCI

[0513] Hereinafter, the determination of the priority between A and B may be referred to in various ways such as selecting one with a higher priority to execute an operation corresponding thereto or omitting or discarding an operation with a lower priority according to a predetermined priority rule.

[0514] Hereinafter, the term "time slot" is used as a general term that may refer to a specific time unit corresponding to a transmission time interval (TTI), and specifically, the time slot may refer to a time slot used in a 5G NR system and may also refer to a time slot or subframe used in a 4G LTE system.

[0515] Hereinafter, a description of examples is provided via a plurality of embodiments, but these are not independent of each other, and it is possible to apply one or more embodiments simultaneously or in combination.

[0516] First embodiment: Single TCI state activation and indication method based on integrated TCI solution

[0517] According to an embodiment, a method for indicating and activating a single TCI state based on an integrated TCI scheme is described. The integrated TCI scheme may refer to a scheme in which a terminal integrates and manages a transmit / receive beam management scheme distinguished by a spatial relationship information scheme used in uplink transmission and a TCI state scheme used in downlink reception in existing versions 15 and 16. Therefore, if the terminal is indicated with a TCI state from a base station, beam management may be performed using the TCI state even for uplink transmission based on the integrated TCI scheme. If the terminal is configured with a TCI-State that is a higher layer signaling having a tci-stateId-r17 that is a higher layer signaling from a base station, the terminal may perform operations based on the integrated TCI scheme by using the corresponding TCI-State. TCI-State may exist in two types: a joint TCI state and a separate TCI state.

[0518] The first type is a joint TCI state, and the terminal may be indicated by the base station via one TCI-State to have a TCI-State to be applied to both uplink transmission and downlink reception. If the terminal is indicated to have a TCI-State based on a joint TCI state, the terminal may be indicated to have parameters to be used for downlink channel estimation by using an RS corresponding to qcl-Type1 under a TCI-State based on a joint TCI state and parameters to be used as a downlink receive beam or receive filter by using an RS corresponding to qcl-Type2. If the terminal is indicated to have a TCI-State based on a joint TCI state, the terminal is indicated to have parameters to be used as an uplink transmit beam or transmit filter by using an RS corresponding to qcl-Type2 under the corresponding TCI-State based on a joint DL / UL TCI state. In this case, if the terminal is indicated to have a TCI-State based on a joint TCI state, the terminal may apply the same beam to both uplink transmission and downlink reception.

[0519] The second type is a separate TCI state, and the terminal can be separately indicated by the base station with a UL TCI-State to be applied to uplink transmission and a DL TCI-State to be applied to downlink reception. If the terminal is indicated with a UL TCI state, the terminal can be indicated with parameters to be used as an uplink transmit beam or transmit filter by using a reference RS or source RS configured in the UL TCI state. If the terminal is indicated with a DL TCI state, the terminal can be indicated with parameters to be used for downlink channel estimation by using an RS corresponding to qcl-Type1 and parameters to be used as a downlink receive beam or receive filter by using an RS corresponding to qcl-Type2, which are configured in the DL TCI state.

[0520] If the terminal is indicated with both a DL TCI state and a UL TCI state, the terminal may be indicated with parameters to be used as an uplink transmit beam or a transmit filter by using a reference RS or a source RS configured in the UL TCI state, and may be indicated with parameters to be used as downlink channel estimation by using an RS corresponding to qcl-Type1 and parameters to be used as a downlink receive beam or a receive filter by using an RS corresponding to qcl-Type2, which are configured in the DL TCI state. In this case, if the DL TCI state indicated to the terminal and the reference RS or the source RS configured in the UL TCI state are different, the terminal may apply an uplink transmit beam based on the indicated UL TCI state and apply a downlink receive beam based on the DL TCI state.

[0521] The terminal can be configured with up to 128 joint TCI states for each specific BWP in a specific cell by the base station via higher layer signaling, and up to 64 or 128 DL TCI states can be configured for each specific BWP in a specific cell based on the UE capability report via higher layer signaling, and the DL TCI state and the joint TCI state in the separate TCI state can use the same higher layer signaling structure. For example, if 128 joint TCI states are configured and 64 DL TCI states are configured in the separate TCI state, the 64 DL TCI states can be included in the 128 joint TCI states.

[0522] Up to 32 or 64 UL TCI states among the individual TCI states can be configured for each specific BWP in a specific cell based on the UE capability report via higher layer signaling, and like the relationship between the joint TCI state and the DL TCI state among the individual TCI state, the UL TCI state among the joint TCI state and the individual TCI state can also use the same higher layer signaling structure, wherein the UL TCI state among the individual TCI state can use a higher layer signaling structure different from the DL TCI state among the joint TCI state and the individual TCI state. As described above, the use of different higher layer signaling structures or the use of the same higher layer signaling structure can be defined in the standard, and based on information including whether there is a supportable usage scheme for the terminal among the two types, the use of the scheme can be distinguished via another higher layer signaling configured by the base station.

[0523] The terminal can receive the transmit / receive beam-related indication in the integrated TCI scheme by using one of the joint TCI state and the separate TCI state configured by the base station. The terminal can be configured by the base station via higher layer signaling whether to use one of the joint TCI state and the separate TCI state.

[0524] The terminal can receive transmit / receive beam-related indications via higher layer signaling by using a scheme selected from a joint TCI state and a separate TCI state, where the method of transmit / receive beam indication from the base station can include a MAC-CE-based indication method and two methods of MAC-CE-based activation and DCI-based indication method.

[0525] If the terminal is configured via higher layer signaling to receive a transmit / receive beam related indication by using a joint TCI state scheme, the terminal may receive a MAC-CE indicating a joint TCI state from the base station and perform a transmit / receive beam application operation, and the base station may schedule the terminal to receive a PDSCH including the MAC-CE via the PDCCH. If a joint TCI state is included in the MAC-CE, the terminal may send a PUCCH including HARQ-ACK information indicating whether reception of the PDSCH including the MAC-CE is successful to the base station, and may determine an uplink transmit beam or transmit filter and a downlink receive beam or receive filter by using the indicated joint TCI state starting from 3 ms after the PUCCH is sent. If two or more joint TCI states are included in the MAC-CE, the terminal may send a PUCCH including HARQ-ACK information indicating whether the reception of the PDSCH including the MAC-CE is successful to the base station, and identify that the multiple joint TCI states indicated by the MAC-CE correspond to each code point of the TCI state field of the DCI format 1_1 or 1_2 from 3ms after the PUCCH is sent and activate the joint TCI state indicated by the MAC-CE. Thereafter, the terminal may receive the DCI format 1_1 or 1_2 and apply one joint TCI state indicated by the corresponding TCI state field in the DCI to the uplink transmission and downlink reception beams. In this case, the DCI format 1_1 or 1_2 may include downlink data channel scheduling information (with DL assignment) or may not include the information (without DL assignment).

[0526] If the terminal is configured via higher layer signaling to receive a transmit / receive beam related indication by using a separate TCI state scheme, the terminal may receive a MAC-CE indicating a separate TCI state from the base station and perform a transmit / receive beam application operation, and the base station may schedule the terminal to receive a PDSCH including the MAC-CE via the PDCCH. If a separate TCI state set is included in the MAC-CE, the terminal may send a PUCCH including HARQ-ACK information indicating whether the reception of the PDSCH is successful to the base station, and may determine an uplink transmit beam or transmit filter and a downlink receive beam or receive filter by using a separate TCI state included in the indicated separate TCI state set from 3 ms after the PUCCH is sent. In this case, a separate TCI state set may refer to a single separate TCI state or multiple separate TCI states that a code point of the TCI state field in DCI format 1_1 or 1_2 may have, and a separate TCI state set may include a DL TCI state, include a UL TCI state, or include a DL TCI state and a UL TCI state. If two or more separate TCI state sets are included in the MAC-CE, the terminal may send a PUCCH including HARQ-ACK information indicating whether the reception of the PDSCH is successful to the base station, and identify that the multiple separate TCI state sets indicated by the MAC-CE correspond to each code point of the TCI state field of the DCI format 1_1 or 1_2 from 3ms after sending the PUCCH and activate the indicated separate TCI state set. In this case, each code point of the TCI state field of the DCI format 1_1 or 1_2 may indicate a DLTCI state, indicate a UL TCI state, or indicate a DL TCI state and a UL TCI state. The terminal may receive the DCI format 1_1 or 1_2 and apply the separate TCI state set indicated by the corresponding TCI state field in the DCI to the uplink transmission and downlink reception beams. In this case, the DCI format 1_1 or 1_2 may include downlink data channel scheduling information (ie, with DL assignment) or may not include the information (ie, without DL assignment).

[0527] For each of the joint TCI state scheme and the individual TCI state scheme, there may be a MAC-CE for activating or indicating the above-mentioned single joint TCI state and individual TCI state, and the TCI state may be activated or indicated based on one of the joint TCI state scheme or the individual TCI state scheme by using one MAC-CE. Various MAC-CE structures for activating and indicating the joint TCI state or the individual TCI state may be considered.

[0528] Fig.15is a diagram illustrating a MAC-CE structure for activation and indication of a joint TCI state in a wireless communication system according to an embodiment.

[0529] Reference Fig.15 , the S field 1500 may indicate the number of pieces of joint TCI state information included in the MAC-CE. If the value of the S field 1500 is 1, the MAC-CE may indicate one joint TCI state and may have a length of only up to the second octet. If the value of the S field 1500 is 0, the MAC-CE may include two or more pieces of joint TCI state information, each joint TCI state may be activated at each code point of the TCI state field of the DCI format 1_1 or 1_2, and up to 8 joint TCI states may be activated. The values ​​of 0 and 1 of the configuration S field 1500 are not limited to the configuration method, wherein a value of 0 may indicate that one joint TCI state is to be included, and a value of 1 may indicate that two or more pieces of joint TCI state information are to be included. This interpretation of the S field may also be applied to other embodiments of the present disclosure. The TCI states indicated via the TCI state ID0 field 1515 to the TCI state ID N-1 field 1525 may correspond to the zeroth code point to the (N-1)th code point of the TCI state field of the DCI format 1_1 or 1_2, respectively. The serving cell ID field 1505 may indicate a serving cell identifier (ID), and the BWP ID field 1510 may indicate a BWPID. The R field may be a 1-bit reserved field that does not include indication information.

[0530] Fig.16 is a diagram illustrating another MAC-CE structure for activation and indication of a joint TCI state in a wireless communication system according to an embodiment.

[0531] exist Fig.16 , the serving cell ID field 1605 may indicate a serving cell identifier (ID), and the BWP ID field 1610 may indicate a BWP ID. The R field 1600 may be a 1-bit reserved field that does not include indication information. Each field in the second octet to the Nth octet is a bitmap indicating each joint TCI state configured via higher layer signaling. As an example, T7 1615 may be a field indicating whether the eighth joint TCI state configured via higher layer signaling is indicated. If the TN value is 1, this may be interpreted as the corresponding joint TCI state being indicated or activated, and if the TN value is 0, this may be interpreted as the corresponding joint TCI state not being indicated or activated. Configuration values ​​0 and 1 are not limited to the above configuration method. If there is a joint TCI state configured via higher layer signaling, the configuration values ​​0 and 1 are not limited to the above configuration method. If there is a joint TCI state configured via higher layer signaling, the configuration values ​​0 and 1 are not limited to the above configuration method. If there is a joint TCI state configured via higher layer signaling, the configuration values ​​0 and 1 are not limited to the above configuration method. If there is a joint TCI state configured via higher layer signaling, the configuration values ​​0 and 1 are not limited to the above configuration method. Fig.16If there is a joint TCI state sent via the MAC-CE structure of the DCI format 1_1 or 1_2, the terminal can apply the joint TCI state indicated via the MAC-CE to the uplink transmission and downlink reception beams. If there are two or more joint TCI states sent via the MAC-CE structure, the terminal can identify that each joint TCI state indicated via the MAC-CE corresponds to each code point of the TCI state field of the DCI format 1_1 or 1_2, and can activate each joint TCI state, and starting from the joint TCI state with the lowest index among the indicated joint TCI states, the joint TCI states corresponding to the code points with low indexes of the TCI state field of the DCI format 1_1 or 1_2 can be activated in sequence.

[0532] Fig.17 is a diagram illustrating another MAC-CE structure for activation and indication of a joint TCI state in a wireless communication system according to an embodiment.

[0533] exist Fig.17 , the serving cell ID field 1705 may indicate a serving cell identifier (ID), and the BWP ID field 1710 may indicate a BWP ID.

[0534] The S field 1700 may indicate the number of pieces of joint TCI state information included in the MAC-CE. If, for example, the value of the S field 1700 is 1, the MAC-CE may indicate one joint TCI state and may include only up to the second octet, and the joint TCI state may be indicated to the terminal via the TCI state ID0 field 1720. If the value of the S field 1700 is 0, the MAC-CE may include two or more pieces of joint TCI state information, each code point of the TCI state field of the DCI format 1_1 or 1_2 may activate each joint TCI state, up to 8 joint TCI states may be activated, the second octet may not exist, and in Fig.17 The first octet and the third octet to the (N+1)th octet may exist on the MAC-CE structure of . The corresponding field present in the third octet to the (N+1)th octet is a bitmap indicating the corresponding joint TCI state configured via higher layer signaling. As an example, T15 1725 may be a field indicating whether the 16th joint TCI state configured via higher layer signaling is indicated. The R field 1715 may be a 1-bit reserved field that does not include indication information.

[0535] If there is a Fig.17 If a joint TCI state is sent via the MAC-CE structure, the terminal can apply the joint TCI state indicated via MAC-CE to the uplink transmission and downlink reception beams. Fig.17If two or more joint TCI states are sent by the MAC-CE structure of the DCI format 1_1 or 1_2, the terminal can identify that each joint TCI state indicated via the MAC-CE corresponds to each code point of the TCI status field of the DCI format 1_1 or 1_2, and can activate each joint TCI state, and starting from the joint TCI state with the lowest index among the indicated joint TCI states, the joint TCI states corresponding to the code points with low indexes in the TCI status field of the DCI format 1_1 or 1_2 can be activated in sequence.

[0536] Fig.18 is a diagram illustrating a MAC-CE structure for activation and indication of a separate TCI state in a wireless communication system according to an embodiment.

[0537] exist Fig.18 , the serving cell ID field 1805 may indicate a serving cell ID, and the BWP ID field 1810 may indicate a BWP ID.

[0538] The S field 1800 may indicate the number of pieces of joint TCI state set information included in the MAC-CE. If, for example, the value of the S field 1800 is 1, the MAC-CE may indicate a single TCI state set and may include only up to the third octet. If the value of the S field 1800 is 0, the MAC-CE may include two or more separate TCI state set information, each code point of the TCI state field of the DCI format 1_1 or 1_2 may activate each separate TCI state set, and up to 8 separate TCI state sets may be activated. The C0 field 1815 may be a field indicating which separate TCI states are included in the indicated separate TCI state set. For example, a C0 field value of "00" may indicate a reservation, a C0 field value of "01" may indicate a DL TCI state, a C0 field value of "10" may indicate a UL TCI state, and a C0 field value of "11" may indicate a DL TCI state and a UL TCI state. However, this is merely an example of an explanation of the C0 field 1815, and the explanation of the C0 field 1815 is not limited thereto. The TCI state IDD,0 field 1820 and the TCI state IDU,0 field 1825 may respectively refer to a DL TCI state and a UL TCI state that may be included in the zeroth separate TCI state set so as to be indicated. If the value of the C0 field is "01", the TCI state IDD,0 field 1820 may indicate the DL TCI state, and the TCI state IDU,0 field 1825 may be ignored. If the value of the C0 field is "10", the TCI state IDD,0 field 1820 may be ignored, and the TCI state IDU,0 field 1825 may indicate the UL TCI state. If the value of the C0 field is "11", the TCI state IDD,0 field 1820 may indicate the DL TCI state, and the TCI state IDU,0 field 1825 may indicate the UL TCI state.

[0539] Fig.18 An example of MAC-CE when the UL TCI state among the individual TCI states uses a higher layer signaling structure as described above (such as the DL TCI state and the joint TCI state among the individual TCI states) may be illustrated. Therefore, the length of the TCI state IDD,0 field 1820 and the TCI state IDU,0 field 1825 may be 7 bits to express up to 128 TCI states. Therefore, in order to use 7 bits for the TCI state IDD,0 field 1820, 6 bits 1820 may be assigned to the second octet and 1 bit 1821 may be assigned to the third octet. In addition, Fig.18A case where the UL TCI state among the individual TCI states as described above uses a higher layer signaling structure different from the DL TCI state and the joint TCI state among the individual TCI states may be indicated. Therefore, since the UL TCI state requires 6 bits to enable expression of up to 64 UL TCI states, the first bit of the TCI state IDU,0 field 1825 may be fixed to 0 or 1, and the bits expressing the actual UL TCI state may correspond only to a total of 6 bits from the second bit to the seventh bit.

[0540] Fig.19 is a diagram illustrating another MAC-CE structure for activation and indication of a separate TCI state in a wireless communication system according to an embodiment.

[0541] exist Fig.19 , the serving cell ID field 1905 may indicate the serving cell ID, and the BWP ID field 1910 may indicate the BWP ID. The S field 1900 may indicate the number of pieces of separate TCI state set information included in the MAC-CE. If, for example, the value of the S field 1900 is 1, the MAC-CE may indicate one separate TCI state set and may include only up to the third octet. If, for example, the value of the S field 1900 is 0, the MAC-CE may include two or more pieces of separate TCI state set information, and each code point corresponding to each separate TCI state set of the TCI state field of DCI format 1_1 or 1_2 may activate each separate TCI state set, and up to 8 separate TCI state sets may be activated. The CD,0 field 1915 may be a field indicating whether the indicated individual TCI state set includes a DL TCI state, wherein if the value of the CD,0 field 1915 is 1, the DL TCI state may be included and the DL TCI state may be indicated via the TCI state ID D,0 field 1925, and if the value of the CD,0 field 1915 is 0, the DL TCI state is not included and the TCI state ID D,0 field 1925 may be ignored. Similarly, the CU,0 field 1920 may be a field indicating whether the indicated individual TCI state set includes a UL TCI state, wherein if the value of the CU,0 field 1920 is 1, the UL TCI state may be included and the UL TCI state may be indicated via the TCI state ID D,0 field 1930, and if the value of the CU,0 field 1920 is 0, the UL TCI state is not included and the TCI state ID D,0 field 1930 may be ignored.

[0542] Fig.19An example of MAC-CE when the UL TCI state among the individual TCI states uses the same higher layer signaling structure as the higher layer signaling structure of the DL TCI state and the joint TCI state among the individual TCI states as described above may be illustrated. Therefore, the length of the TCI state ID D,0 field 1925 and the TCI state ID U,0 field 1930 may be 7 bits to express up to 128 TCI states. In addition, Fig.19 An example of MAC-CE when the UL TCI state among the individual TCI states uses a higher layer signaling structure different from the higher layer signaling structure of the DL TCI state and the joint TCI state among the individual TCI states as described above may be illustrated. Therefore, since the UL TCI state requires 6 bits to enable expression of up to 64 UL TCI states, the first bit of the TCI state IDU,0 field 1925 may be fixed to 0 or 1, and the bit expressing the actual UL TCI state may correspond only to a total of 6 bits from the second bit to the seventh bit.

[0543] Fig. 20 is a diagram illustrating another MAC-CE structure for activation and indication of a separate TCI state in a wireless communication system according to an embodiment.

[0544] exist Fig. 20 , the serving cell ID field 2005 may indicate the serving cell ID, and the BWP ID field 2010 may indicate the BWP ID. The S field 2000 may indicate the number of pieces of separate TCI state set information included in the MAC-CE. If, for example, the value of the S field 2000 is 1, the MAC-CE may indicate one separate TCI state set and may include only up to the third octet. Fig. 20 The MAC-CE structure may indicate a separate TCI state set by using two octets, and if the separate TCI state set includes a DL TCI state, the first octet of the two octets may indicate the DL TCI state, and the second octet may indicate the UL TCI state. Alternatively, the order may be changed.

[0545] If the value of the S field 2000 is 0, the MAC-CE may include two or more separate TCI state set information, each code point of the TCI state field of the DCI format 1_1 or 1_2 may activate each separate TCI state set, and up to 8 separate TCI state sets may be activated. The C0,0 field 2015 may have a meaning for distinguishing whether the TCI state indicated by the TCI state ID0,0 field 2025 is a DL TCI state or a UL TCI state. A C0,0 field 2015 value of 1 may indicate a DL TCI state, and the DL TCI state may be indicated via the TCI state ID0,0 field 2025, and the third octet may be present. In this case, if the value of the C1,0 field 2020 is 1, the UL TCI state may be indicated via the TCI state ID1,0 field 2030, and if the value of the C1,0 field 2020 is 0, the TCI state ID1,0 field 2030 may be ignored. If the value of the C0,0 field 2015 is 0, the UL TCI state may be indicated via the TCI state ID0,0 field 2025, and the third octet may not exist. This interpretation of the C0,0 field 2015 field and the C1,0 field 2020 is merely an example and does not exclude the opposite interpretation of the C0,0 field 2015 field values ​​of 0 and 1 or the opposite interpretation of the DL TCI state and UL TCI state values.

[0546] Fig. 20 An example of MAC-CE when the UL TCI state among the individual TCI states uses the same higher layer signaling structure as the higher layer signaling structure of the DL TCI state and the joint TCI state among the individual TCI states as described above may be illustrated, and therefore, the length of the TCI state ID0,0 field 2025 and the TCI state ID1,0 field 2030 may be 7 bits to express up to 120 TCI states. In addition, Fig. 20 An example of MAC-CE when the UL TCI state among the individual TCI states uses a higher layer signaling structure different from the higher layer signaling structure of the DL TCI state and the joint TCI state among the individual TCI states as described above may be illustrated. Therefore, the TCI state ID0,0 field 2025 may be 7 bits that enable expression of both 6 bits for expressing up to 64 possible UL TCI states and 7 bits for expressing up to 120 possible DL TCI states. If the value of the C1,0 field 2015 is 1, and thus the TCI state ID0,0 field 2025 indicates the UL TCI state, the first bit of the TCI state ID0,0 field 2025 may be fixed to 0 or 1, and the bit expressing the actual UL TCI state may correspond only to a total of 6 bits from the second bit to the seventh bit.

[0547] Fig.21 is a diagram illustrating another MAC-CE structure for activation and indication of a separate TCI state in a wireless communication system according to an embodiment.

[0548] exist Fig.21 , the serving cell ID field 2105 may indicate the serving cell ID, and the BWP ID field 2110 may indicate the BWP ID. The S field 2100 may indicate the number of pieces of separate TCI state set information included in the MAC-CE. If, for example, the value of the S field 2100 is 1, the MAC-CE may indicate one separate TCI state set and may include only up to the third octet.

[0549] If the value of the S field 2100 is 0, the MAC-CE may include two or more separate TCI state set information, each code point of the TCI state field of the DCI format 1_1 or 1_2 may activate each separate TCI state set, and up to 8 separate TCI state sets may be activated. The C0 field 2115 may be a field indicating which separate TCI states are included in the indicated separate TCI state set, a C0 field 2115 value of "00" may indicate a reserved, a C0 field 2115 value of "01" may indicate one DLTCI state, a C0 field 2115 value of "10" may indicate one UL TCI state, and a C0 field 2115 value of "11" may indicate one DL TCI state and one UL TCI state. However, this is merely an example of the interpretation of the C0 field 2115, and the interpretation of the C0 field 2125 is not limited thereto. The TCI state IDD,0 field 2120 and the TCI state IDD,0 field 2125 may respectively refer to a UL TCI state and a DL TCI state that may be included in the zeroth separate TCI state set so as to be indicated. If the value of the C0 field 2115 is "01", the TCI state IDD,0 field 2125 may indicate the DL TCI state, and the TCI state IDD,0 field 2120 may be ignored. If the value of the C0 field 2115 is "10", the third octet may be ignored, and the TCI state IDD,0 field 2120 may indicate the UL TCI state. If the value of the C0 field 2115 is "11", the TCI state IDD,0 field 2125 may indicate the DL TCI state, and the TCI state IDD,0 field 2120 may indicate the UL TCI state. The R field 2121 may be a 1-bit reserved field that does not include indication information.

[0550] Fig.21An example of a MAC-CE used when the UL TCI state among the individual TCI states uses a higher layer signaling structure different from the higher layer signaling structure of the DL TCI state and the joint TCI state among the individual TCI states as described above can be illustrated. Therefore, for the length of the TCI state ID D,0 field 2125, up to 128 TCI states can be expressed using 7 bits, and for the length of the TCI state ID U,0 field 2120, up to 64 TCI states can be expressed using 6 bits.

[0551] Fig. 22 is a diagram illustrating a MAC-CE structure for joint and individual TCI state activation and indication in a wireless communication system according to an embodiment.

[0552] exist Fig. 22 , the serving cell ID field 2205 may indicate the serving cell ID, and the BWP ID field 2210 may indicate the BWP ID. The J field 2200 may indicate whether the TCI state indicated via the MAC CE is a joint TCI state or a separate TCI state set. For example, if the value of the J field 2200 is 1, the MAC-CE may indicate the joint TCI state, and if the value of the J field 2200 is 0, the MAC-CE may indicate a separate TCI state set. The above explanation of the J field 2200 is merely an example, and does not exclude the opposite interpretation.

[0553] If the MAC-CE indicates a joint TCI state, all odd octets (the third octet, the fifth octet, ...) except the first octet may be ignored. The C0,0 field 2215 may indicate whether the MAC-CE indicates one joint TCI state or includes two or more pieces of TCI state information, and may indicate whether each code point of the TCI state field of the DCI format 1_1 or 1_2 activates each TCI state. If the value of the C0,0 field 2215 is 1, the MAC-CE may indicate one joint TCI state, and the third octet and more octets may not exist. If the value of the C0,0 field 2215 is 0, the two or more joint TCI states indicated by the MAC-CE correspond to each code point of the TCI state field of the DCI format 1_1 or 1_2 and may be activated. TCI state ID0,0 may refer to the first indicated joint TCI state.

[0554] If the MAC-CE indicates a separate TCI state set, for example, the C0,0 field 2215 may have a meaning of distinguishing whether the TCI state indicated by the TCI state ID0,0 field 2225 is a DL TCI state or a UL TCI state, a value of 1 may indicate a DL TCI state, the DL TCI state may be indicated via the TCI state ID0,0 field 2225, and the third octet may be present. In this case, if the value of the C1,0 field 2220 is 1, the UL TCI state may be indicated via the TCI state ID1,0 field 2230, and if the value of the C1,0 field 2220 is 0, the TCI state ID1,0 field 2230 may be ignored. If the value of the C0,0 field 2215 is 0, the UL TCI state may be indicated via the TCI state ID0,0 field 2225, and the third octet may not be present. Fig. 22 An example of MAC-CE used when the UL TCI state among the individual TCI states uses the same higher layer signaling structure as the higher layer signaling structure of the DL TCI state and the joint TCI state among the individual TCI states as described above may be illustrated. Therefore, the length of the TCI state ID0,0 field 2225 and the TCI state ID1,0 field 2230 may be 7 bits to express up to 128 TCI states. In addition, Fig. 22 An example of a MAC-CE used when the UL TCI state among the individual TCI states uses a higher layer signaling structure different from the higher layer signaling structure of the DL TCI state and the joint TCI state among the individual TCI states as described above may be illustrated. Therefore, the TCI state ID0,0 field 2225 uses 7 bits that enable expression of both 6 bits for expressing up to 64 possible UL TCI states and 7 bits for expressing up to 128 possible DL TCI states. If the value of the C0,0 field 2215 is 1, and thus the TCI state ID0,0 field 2225 indicates the UL TCI state, the first bit of the TCI state ID0,0 field 2225 may be fixed to 0 or 1, and the bit expressing the actual UL TCI state may correspond only to a total of 6 bits from the second bit to the seventh bit.

[0555] Fig.23 is a diagram illustrating another MAC-CE structure for joint and individual TCI state activation and indication in a wireless communication system according to an embodiment.

[0556] exist Fig.23, the serving cell ID field 2305 and the BWP ID field 2310 may indicate the serving cell ID and the BWP ID, respectively. The J field 2300 may indicate whether the TCI state indicated via the MAC CE is a joint TCI state or a separate TCI state set. For example, if the value of the J field 2300 is 1, the MAC-CE may indicate the joint TCI state, and if the value of the J field 2300 is 0, the MAC-CE may indicate a separate TCI state set. The above explanation of the J field 2300 is merely an example, and does not exclude the opposite explanation.

[0557] If the MAC-CE indicates a joint TCI state, all even octets (the second octet, the fourth octet, ...) except the first octet may be ignored. The S0 field 2321 may indicate whether the MAC-CE indicates a joint TCI state or whether two or more TCI states correspond to each code point of the TCI state field of the DCI format 1_1 or 1_2 and are activated. If the value of the S0 field 2321 is 1, the MAC-CE may indicate a joint TCI state, and the third octet and more octets may not exist. If the value of the S0 field 2321 is 0, the MAC-CE may include two or more pieces of joint TCI state information, and each code point of the TCI state field of the DCI format 1_1 or 1_2 may activate each joint TCI state. TCI state IDD,0 may refer to the first indicated joint TCI state.

[0558] If the MAC-CE indicates a separate TCI state set, the C0 field 2315 may be a field indicating which separate TCI states are included in the indicated separate TCI state set. A C0 field 2315 value of "00" may indicate a reserved, a C0 field 2315 value of "01" may indicate a DL TCI state, a C0 field 2315 value of "10" may indicate a UL TCI state, and a C0 field 2315 value of "11" may indicate a DL TCI state and a UL TCI state. These values ​​are merely examples and the present disclosure is not limited by these examples. The TCI state ID DU,0 field 2320 and the TCI state ID DD,0 field 2325 may refer to a UL TCI state and a DL TCI state, respectively, that may be included in the zeroth separate TCI state set so as to be indicated. If the value of the C0 field 2315 is "01", the TCI state ID D,0 field 2325 may indicate the DL TCI state and the TCI state ID U,0 field 2320 may be ignored, if the value of the C0 field 2315 is "10", the TCI state ID U,0 field 2320 may indicate the UL TCI state, and if the value of the C0 field 2315 is "11", the TCI state ID D,0 field 2325 may indicate the DL TCI state and the TCI state ID U,0 field 2320 may indicate the UL TCI state. If the value of the S0 field 2321 is 1, the MAC-CE may indicate one separate TCI state set, and the fourth octet and more octets may not exist. If the value of the S0 field 2321 is 0, the MAC-CE may include two or more separate TCI state set information, each code point of the TCI state field of the DCI format 1_1 or 1_2 may activate each separate TCI state set, and up to 8 separate TCI state sets may be activated. For example, if the value of the S0 field 2321 is 0, if the values ​​of the C1, ..., CN-1 fields are "10", this indicates that only the UL TCI state is indicated, so that the fifth octet, the seventh octet, ..., the Mth octet can be ignored. Alternatively, the Sn field can indicate whether there is an octet for a subsequent separate TCI state set. For example, if the value of the Sn field is 1, there may be no subsequent octet, and if the value of the Sn field is 0, there may be a subsequent octet including Cn+1 and TCI state ID U,n+1. These Sn field values ​​are merely examples and the present disclosure is not limited to these examples.

[0559] Fig.23An example of MAC-CE when the UL TCI state among the individual TCI states uses a higher layer signaling structure different from the higher layer signaling structure of the DL TCI state and the joint TCI state among the individual TCI states as described above may be illustrated. Therefore, the length of the TCI state ID D,0 field 2325 may be 7 bits for expressing up to 128 TCI states, and the length of the TCI state ID U,0 field 2320 may be 6 bits for expressing up to 64 TCI states.

[0560] If the terminal receives a transmit / receive beam related indication via higher layer signaling by using a joint TCI state scheme or a separate TCI state scheme, the terminal may receive a PDSCH including a MAC-CE indicating a joint TCI state or a separate TCI state from the base station to perform application of the transmit / receive beam. If two or more joint TCI states or separate TCI state sets are included in the MAC-CE as described above, the terminal may identify that the multiple joint TCI states or separate TCI state sets indicated via the MAC-CE correspond to each code point of the TCI state field of the DCI format 1_1 or 1_2 and may activate the indicated joint TCI state or separate TCI state set from 3ms after sending the PUCCH including HARQ-ACK information indicating the reception success or failure of the corresponding PDSCH. Thereafter, the terminal may receive the DCI format 1_1 or 1_2 and apply the joint TCI state or separate TCI state set indicated by the corresponding TCI state field in the DCI to the uplink transmission and downlink reception beams. In this case, DCI format 1_1 or 1_2 may include downlink data channel scheduling information (with DL assignment) or may not include the information (without DL assignment).

[0561] Fig.24 is a diagram of beam application time that may be considered when an integrated TCI scheme is used in a wireless communication system according to an embodiment.

[0562] As described above, the terminal can receive DCI format 1_1 or 1_2 including downlink data channel scheduling information (with DL assignment) or not including downlink data channel scheduling information (without DL assignment) from the base station, and apply a joint TCI state or a separate TCI state set indicated by the corresponding TCI state field in the DCI to the uplink transmission and downlink reception beams.

[0563] DCI format 1_1 or 1_2 with DL assignment 2400: If the terminal receives DCI format 1_1 or 1_2 including downlink data channel scheduling information from the base station and indicates a joint TCI state or a separate TCI state set based on the integrated TCI scheme, the terminal may receive 2405 a PDSCH scheduled based on the received DCI, and transmit 2410 a PUCCH including HARQ-ACK indicating the success or failure of receiving DCI and PDSCH to the base station. In this case, HARQ-ACK may include the success or failure of receiving both DCI and PDSCH, the terminal may send NACK when at least one of DCI and PDSCH cannot be received, and the terminal may send ACK when both have been successfully received.

[0564] DCI format 1_1 or 1_2 without DL assignment 2450: If the terminal receives 2455 from the base station a DCI format 1_1 or 1_2 that does not include downlink data channel scheduling information and indicates one joint TCI state or a separate TCI state set based on an integrated TCI scheme, the terminal may assume the following for the DCI.

[0565] *Includes CRC scrambled with CS-RNTI.

[0566] *The value of all bits assigned to all fields used as redundancy version (RV) fields is 1.

[0567] *The value of all bits assigned to all fields used as modulation and coding scheme (MCS) fields is 1.

[0568] *The value of all bits assigned to all fields used as New Data Indication (NDI) fields is 0.

[0569] *The values ​​of all bits assigned to the Frequency Domain Resource Allocation (FDRA) field are 0 for FDRA type 0, the values ​​of all bits assigned to the FDRA field are 1 for FDRA type 1, and if the FDRA scheme is dynamicSwitch, the values ​​of all bits assigned to the FDRA field are 0.

[0570] The terminal may transmit 2460 to the base station a PUCCH including HARQ-ACK indicating reception success or failure of DCI format 1_1 or 1_2 that has assumed the above matter.

[0571] For DCI format 1_1 or 1_2 with downlink assignment 2400 and without downlink assignment 2450, if the new TCI state indicated via DCI 2401 or 2455 is the same as the TCI state previously indicated and applied to the uplink transmission and downlink reception beams, the terminal can maintain the previously applied TCI state. If the new TCI state is different from the previously indicated TCI state, the terminal can determine that the time point of applying the joint TCI state or the individual TCI state set indicated by the TCI state field included in the DCI can be applied from the starting point 2420 or 2470 of the first time slot after the beam application time (BAT) 2415 or 2465 following PUCCH transmission (interval of 2430 or 2480), and the previously indicated TCI-state can be used until the interval 2425 or 2475 before the starting point 2420 or 2470 of the time slot.

[0572] For DCI format 1_1 or 1_2 with DL assignment 2400 and without DL assignment 2450, the BAT is a specific number of OFDM symbols and can be configured via higher layer signaling based on UE capability report information. The BAT and the parameter set for the first time slot after the BAT can be determined based on the minimum parameter set among all cells to which the joint TCI state or separate TCI state set indicated via DCI is applied.

[0573] The terminal can apply one joint TCI state indicated via MAC-CE or DCI to the reception of a control resource set linked to all UE-specific search spaces, the reception of a PDSCH scheduled via a PDCCH sent from the corresponding control resource set, the transmission of a PUSCH, and the transmission of all PUCCH resources.

[0574] If a single TCI state set indicated via MAC-CE or DCI includes a DL TCI state, the terminal can apply the single TCI state set to the reception of control resource sets linked to all UE-specific search spaces and the reception of PDSCH scheduled via PDCCH sent from the corresponding control resource set, and based on the previously indicated UL TCI state, the single TCI state set can be applied to all PUSCH and PUCCH resources.

[0575] If a separate TCI state set indicated via MAC-CE or DCI includes a UL TCI state, the terminal can apply the separate TCI state set to all PUSCH and PUCCH resources, and based on the previously indicated DL TCI state, can apply the separate TCI state set to the reception of control resource sets linked to all UE-specific search spaces and the reception of PDSCH scheduled via PDCCH sent from the corresponding control resource set.

[0576] If a separate TCI state set indicated via MAC-CE or DCI includes a DL TCI state and a UL TCI state, the terminal can apply the DL TCI state to the reception of the control resource set linked to the UE-specific search space and the reception of the PDSCH scheduled via the PDCCH sent from the corresponding control resource set, and can apply the UL TCI state to all PUSCH and PUCCH resources.

[0577] exist Figures 15 to 23 In the aforementioned examples of the MAC CE, it is possible that one or more elements are coupled to each other.

[0578] Second embodiment: Multi-TCI status indication and activation method based on integrated TCI solution

[0579] According to an embodiment, a method for indicating and activating multiple TCI states based on an integrated TCI scheme is described. The multiple TCI state indication and activation method may refer to a case where the number of indicated joint TCI states is extended to two or more and a case where each of the DL TCI states and the UL TCI states included in a single TCI state set is extended to two or more. If a single TCI state set can include up to two DL TCI states and two UL TCI states, a total of 8 combinations of DL TCI states and UL TCI states that a single TCI state set can have may be possible ({DL,UL}={0,1},{0,2},{1,0},{1,1},{1,2},{2,0},{2,1},{2,2}, where the number indicates the number of TCI states).

[0580] If the terminal is indicated by the base station as having multiple TCI states based on MAC-CE, the terminal may receive two or more joint TCI states or a single TCI state set from the base station via MAC-CE. The base station may schedule the reception of the PDSCH including the MAC-CE for the terminal via the PDCCH, and from 3 ms after sending the PUCCH including HARQ-ACK information indicating the success or failure of the reception of the PDSCH including the MAC-CE, the terminal may determine the uplink transmit beam or transmit filter and the downlink receive beam or receive filter based on the indicated two or more joint TCI states or a single TCI state set.

[0581] If the terminal is indicated by the base station as having multiple TCI states based on DCI format 1_1 or 1_2, each code point of a TCI state field in DCI format 1_1 or 1_2 may indicate two or more joint TCI states or two or more separate TCI state sets. In this case, the terminal may receive a MAC-CE from the base station and activate two or more joint TCI states or two or more separate TCI state sets corresponding to each code point of a TCI state field in DCI format 1_1 or 1_2. The base station may schedule the reception of a PDSCH including a MAC-CE for the terminal via the PDCCH, and the terminal may activate the TCI state information included in the MAC-CE starting from 3ms after sending a PUCCH including HARQ-ACK information indicating the success or failure of reception of the PDSCH including the MAC-CE.

[0582] If the terminal is indicated to have multiple TCI states based on DCI format 1_1 or 1_2 from the base station, there may be two or more TCI state fields in DCI format 1_1 or 1_2, and one of two or more joint TCI states or two or more separate TCI state sets may be indicated based on each TCI state field. In this case, the terminal may receive a MAC-CE from the base station and activate a joint TCI state or a separate TCI state set corresponding to each code point of the two TCI state fields in DCI format 1_1 or 1_2. The base station may schedule the reception of the PDSCH including the MAC-CE for the terminal via the PDCCH. The terminal may activate the TCI state information included in the MAC-CE from 3ms after sending the PUCCH including the HARQ-ACK information indicating the success or failure of the reception of the PDSCH including the MAC-CE. The terminal may be configured for the presence or absence of one or more additional TCI state fields via higher layer signaling, and the bit length of the additional TCI state field may be the same as the bit length of the existing TCI state field, or the length may be adjusted based on higher layer signaling.

[0583] The terminal can receive the transmit / receive beam-related indication in the integrated TCI scheme by using one of the joint TCI state and the separate TCI state configured by the base station. The terminal can be configured by the base station via higher signaling to use one of the joint TCI state or the separate TCI state. For the separate TCI state indication, the terminal can be configured via higher layer signaling so that the bit length of the TCI state field in DCI format 1_1 or 1_2 is up to 4.

[0584] For each of the joint TCI state scheme and the individual TCI state scheme, there may be a MAC-CE for activating or indicating the above-mentioned multiple joint TCI states and individual TCI states, and the TCI state may be activated or indicated based on the joint TCI state scheme or one of the individual TCI state schemes by using one MAC-CE, and the MAC-CE for the MAC-CE-based indication scheme and the MAC-CE-based activation scheme may share one MAC-CE structure and may use an individual MAC-CE structure. Various MAC-CE structures for activation and indication of multiple joint or individual TCI states may be considered. A case where two TCI states are activated or indicated is considered, but the present disclosure may be applied to the case of three or more TCI states in a similar manner.

[0585] Fig.25 is a diagram illustrating a MAC-CE structure for activation and indication of multiple joint TCI states in a wireless communication system according to an embodiment.

[0586] exist Fig.25 , the serving cell ID field 2505 may indicate the serving cell ID, and the BWP ID field 2510 may indicate the BWP ID. The R field may be a 1-bit reserved field that does not include indication information. The S field 2500 may indicate the number of pieces of joint TCI state set information included in the MAC-CE. If, for example, the value of the S field 2500 is 1, the MAC-CE may indicate one or two joint TCI states and may have a length of only up to the third octet. In this case, if the value of the C0 field 2515 is 0, the third octet may not exist, and one joint TCI state may be indicated via the TCI state ID0,0 field 2520, and if the value of the C0 field 2515 is 1, the third octet may exist, and two joint TCI states may be indicated via the TCI state ID0,0 field 2520 and the TCI state ID1,0 field 2525, respectively.

[0587] If, for example, the value of the S field 2500 is 0, the MAC-CE may activate one or two joint TCI states corresponding to each code point of the TCI state field of the DCI format 1_1 or 1_2, or may activate one joint TCI state corresponding to each code point of the two TCI state fields of the DCI format 1_1 or 1_2, and may activate joint TCI states for up to 8 code points. If one or two joint TCI states are activated for one code point of one TCI state field, the TCI state ID0, Y field and the TCI state ID1, Y field may respectively refer to the first joint TCI state and the second joint TCI state among the two joint TCI states activated at the Yth code point of the TCI state field. If one joint TCI state is activated for one code point of two TCI state fields, the TCI state ID0, Y field and the TCI state ID1, Y field may respectively refer to the joint TCI state activated at the Yth code point of the first TCI state field and the second TCI state field.

[0588] Fig.26 is a diagram illustrating a MAC-CE structure for activation and indication of multiple individual TCI states in a wireless communication system according to an embodiment.

[0589] exist Fig.26 , the serving cell ID field 2605 may indicate the serving cell ID, and the BWP ID field 2610 may indicate the BWP ID. The R field may be a 1-bit reserved field that does not include indication information. The S field 2600 may indicate the number of pieces of separate TCI state set information included in the MAC-CE. If the value of the S field 2600 is 1, the MAC-CE may indicate a separate TCI state set and may include only up to the fifth octet. If the value of the S field 2600 is 0, the MAC-CE may include information about multiple separate TCI state sets, and the MAC-CE may activate a separate TCI state set corresponding to each code point of the TCI state field of DCI format 1_1 or 1_2 or may activate a separate TCI state set corresponding to each code point of the two TCI state fields of DCI format 1_1 or 1_2, and may activate separate TCI states for up to 8 or 16 code points via higher layer signaling as described above.

[0590] exist Fig.26 In the MAC-CE structure of , starting from the second octet, every 4 octets may correspond to a single TCI state set. For example, the C0 field 2615 may have a total of 8 values ​​from "000" to "111", and as described above, these values ​​may respectively correspond to 8 cases that a single TCI state set may have.

[0591] The C0 field with a value of "000" indicates that a single TCI state set includes a UL TCI state, the TCI state ID D,0,0 fields 2620 and 2621 may be ignored, and the TCI state ID U,0,0 field 2625 may include a piece of UL TCI state information. In addition, the fourth octet and the fifth octet may be ignored.

[0592] The C0 field having a value of "001" indicates that a single TCI state set includes two UL TCI states, the TCI state ID D,0,0 fields 2620 and 2621 may be ignored, and the TCI state ID U,0,0 field 2625 may include the first UL TCI state information among the two UL TCI states. In addition, the fourth octet may be ignored, and the TCI state ID U,1,0 field 2635 may include the second UL TCI state information among the two UL TCI states.

[0593] The C0 field having a value of '010' indicates that a single TCI state set includes a DL TCI state, the TCI state ID D,0,0 fields 2620 and 2621 may include one piece of DL TCI state information, and the TCI state ID U,0,0 field 2625 and the fourth octet and the fifth octet may be ignored.

[0594] The C0 field with a value of "011" indicates that a single TCI state set includes a DL TCI state and a UL TCI state, TCI state ID D,0,0 fields 2620 and 2621 may have one DL TCI state information, and TCI state ID U,0,0 field 2625 may include one UL TCI state information. The fourth octet and the fifth octet may be ignored.

[0595] The C0 field having a value of "100" indicates that a single TCI state set includes one DL TCI state and two UL TCI states, TCI state ID D,0,0 fields 2620 and 2621 may include one DL TCI state information, and TCI state ID U,0,0 field 2625 may include the first UL TCI state information among the two UL TCI states. In addition, the fourth octet may be ignored, and the TCI state ID U,1,0 field 2635 may include the second UL TCI state information among the two UL TCI states.

[0596] The C0 field with a value of "101" indicates that a single TCI state set includes two DL TCI states, the TCI state IDD,0,0 fields 2620 and 2621 may include the first DL TCI state information among the two DL TCI states, and the TCI state IDD,0,0 field 2625 and the fifth octet may be ignored. The TCI state IDD,1,0 field 2630 may include the second DL TCI state information among the two DL TCI states.

[0597] The C0 field with a value of "110" indicates that a single TCI state set includes two DL TCI states and one UL TCI state, the TCI state IDD,0,0 fields 2620 and 2621 may include the first DL TCI state information among the two DL TCI states, the TCI state IDD,0,0 field 2625 may include a UL TCI state information, the TCI state IDD,1,0 field 2630 may include the second DL TCI state information among the two DL TCI states, and the fifth octet may be ignored.

[0598] The C0 field with a value of "111" indicates that a single TCI state set includes two DL TCI states and two UL TCI states, the TCI state IDD,0,0 fields 2620 and 2621 may include the first DL TCI state information among the two DL TCI states, the TCI state IDU,0,0 field 2625 may include the first UL TCI state information among the two UL TCI states, the TCI state IDD,1,0 field 2630 may include the second DL TCI state information among the two DL TCI states, and the TCI state IDU,1,0 field 2635 may include the second UL TCI state information among the two UL TCI states.

[0599] Fig.26 An example of MAC-CE used when the UL TCI state among the individual TCI states uses a higher layer signaling structure different from the higher layer signaling structure of the DL TCI state and the joint TCI state among the individual TCI states as described above can be illustrated. Therefore, since the UL TCI state requires 6 bits to express up to 64 UL TCI states, the TCI state IDU,0,0 to TCI state IDU,1,N fields expressing the UL TCI state can be expressed with 6 bits, while the TCI state IDD,0,0 to TCI state IDD,1,N fields expressing the DL TCI state can be expressed with 7 bits.

[0600] Fig. 27is a diagram illustrating another MAC-CE structure for activation and indication of multiple individual TCI states in a wireless communication system according to an embodiment.

[0601] exist Fig. 27 , the serving cell ID field 2705 may indicate a serving cell identifier (ID), and the BWP ID field 2710 may indicate a BWP ID. The R field may be a 1-bit reserved field that does not include indication information. The S field 2700 may indicate the number of pieces of separate TCI state set information included in the MAC-CE. If, for example, the value of the S field 2700 is 1, the MAC-CE may indicate one separate TCI state set and may have a length of only up to the fifth octet.

[0602] For example, if the value of the S field 2700 is 0, the MAC-CE may include information about multiple separate TCI state sets, and the MAC-CE may activate a separate TCI state set corresponding to each code point of the TCI state field of DCI format 1_1 or 1_2, or may activate a separate TCI state set corresponding to each code point of the two TCI state fields of DCI format 1_1 or 1_2, and may activate separate TCI state sets corresponding to up to 8 or 16 code points via higher layer signaling as described above.

[0603] exist Fig. 27 In the MAC-CE structure of , starting from the second octet, every 4 octets may correspond to a single TCI state set. The CU,0 field 2715 and the CD,0 field 2721 may respectively refer to the number of UL TCI states and DL TCI states included in a single TCI state set, and may have the following meanings for each code point.

[0604] The CU,0 field having a value of '00' indicates that the UL TCI state is not included, and thus, the TCI state IDU,0,0 2720 and the TCI state IDU,1,0 2725 may be ignored.

[0605] The CU,0 field having a value of '01' indicates that one UL TCI state is included, and thus, TCI state IDU,0,0 2720 may include one piece of UL TCI state information and TCI state IDU,1,0 2725 may be ignored.

[0606] The CU,0 field having a value of '10' indicates that two UL TCI states are included, and thus, TCI state IDU,0,0 2720 may include first UL TCI state information among the two UL TCI states, and TCI state IDU,1,0 2725 may include second UL TCI state information among the two UL TCI states.

[0607] The CU,0 field having a value of '00' indicates that the DL TCI state is not included, and thus, the fourth octet and the fifth octet may be ignored.

[0608] The CU,0 field having a value of '01' indicates that one DL TCI state is included, and thus, TCI state IDU,0,0 2730 may include one DL TCI state information and the fifth octet may be ignored.

[0609] The CU,0 field having a value of '10' indicates that two DL TCI states are included, and thus, the TCI state IDU,0,0 2730 may include first DL TCI state information among the two DL TCI states, and the TCI state IDU,1,0 field 2735 may include second DL TCI state information among the two DL TCI states.

[0610] Fig. 27 The MAC-CE used when the UL TCI state among the individual TCI states uses a higher layer signaling structure that is different from the higher layer signaling structure of the DL TCI state and the joint TCI state among the individual TCI states as described above can be illustrated, and therefore, since the UL TCI state requires 6 bits to express up to 64 UL TCI states, the TCI state IDU,0,0 to TCI state IDU,1,N fields expressing the UL TCI state can be expressed with 6 bits, whereas the TCI state IDD,0,0 to TCI state IDU,1,N fields expressing the DL TCI state can be expressed with 7 bits.

[0611] exist Figure 25 to Figure 27 In the aforementioned example of the MAC CE, one or more elements may be coupled to each other.

[0612] Third embodiment: sending packets with the same priority when using multiple panels to support simultaneous uplink transmission Method for including uplink control information in an uplink channel

[0613] According to an embodiment, a method for multiplexing UCI on simultaneously transmitted uplink channels when multiple uplink channels are simultaneously transmitted using multiple panels is provided. It can be assumed that the UCI to be multiplexed is information included (or multiplexed) in a PUSCH or PUCCH having the same priority.

[0614] Prior to NR Release 17, methods for sending multiple uplink channels (for example, PUSCH, PUCCH, or SRS may be included in the uplink channel) in the same time resource for one serving cell were not supported. In order to support such operations, multiple panels capable of sending different uplink channels may be required. Here, the panel can be interpreted in various ways. For example, a panel can be defined as one or more transmit and receive units or transceiver units (TXRUs) capable of receiving or sending signals by using one downlink receive beam or one uplink transmit beam, and a set of antenna elements associated with these TXRUs. Alternatively, multiple antenna elements may be configured as one panel, regardless of the number of supportable receive beams or transmit beams. Alternatively, a certain number of TXRUs may be configured as one panel according to the capabilities of the terminal or base station, and one or more antenna elements may be connected to one TXRU. In addition, various panel implementations may be considered. As in the example of the first panel configuration, the panel is assumed to be a TXRU capable of receiving or sending signals by using one downlink receive beam or one uplink transmit beam, and a set of antenna elements associated with it.

[0615] In the NR version 18 stage, in order to support simultaneous transmission in time resources, a transmission scheme using multiple panels is discussed, and specific schemes, operations, etc. may be introduced into the standard. In NR version 17, improvements have been made for integrated beam management for downlink and uplink. As a separate scheme improvement, NR version 17 has introduced PUCCH and PUSCH transmission methods taking into account multiple TRPs (hereinafter referred to as multi-TRP (mTRP)). In this case, PUCCH or PUSCH can be repeatedly sent to the mTRP by using a multiplexing scheme (e.g., TDM) divided in the time domain. Since the PUCCH or PUSCH sent to each TRP is sent in different time domains, the terminal supports time division repeated transmission instead of simultaneous transmission. However, in NR version 18, simultaneous uplink transmission using multiple panels (simultaneous transmission with multiple panels (UL STxMP), hereinafter referred to as STxMP) can be supported, where STxMP is achieved by using two or more panels to send different uplink beams (or the same uplink beam) to different TRPs (or the same TRP) on corresponding uplink channels in the same time domain while considering FDM, SDM, single frequency network (SFN) (e.g., single frequency broadcast network), etc. instead of TDM scheme.

[0616] Fig.28is a diagram illustrating resource allocation and transmission panels for uplink transmission in FDM, SDM, and SFN schemes for supporting STxMP.PUSCH is described herein as an example, but the contents disclosed hereinafter may be similarly applied to PUCCH, SRS, or other uplink channels.

[0617] FDM scheme A2800 is used to configure all resources of a scheduled PUSCH into one TB, and to encode information bits based on this. Thereafter, according to the FDM scheme, the resources can be divided into two halves in the frequency domain so as to be transmitted simultaneously by using each panel. For example, the terminal can transmit 2801 the first part of all PUSCH resources (including a part of the low-index RB) via the first panel, and can transmit 2802 the second part of all PUSCH resources (a part other than the first part) via the second panel. The corresponding parts can be mapped to the panels so as to be transmitted in an order different from the order in the example (for example, the first part of all PUSCH resources can be transmitted via the second panel, and the second part of all PUSCH resources can be transmitted via the first panel). In this case, if a TB is divided into two halves and transmitted via the corresponding panels, and the transmission is performed to different TRPs by using the corresponding panels, a part of a TB is received in one TRP. Thereafter, depending on the implementation of the base station, the base station can collect the parts into one and perform joint decoding or separate decoding to receive the signal sent by the terminal. 2805 DMRS may be sent over all PUSCH resources in FDM scheme A 2800. Alternatively, DMRS may be sent over corresponding PUSCH portions sent to different TRPs, where different DMRS ports may be configured or different DMRS sequences may be used for DMRS sent to different TRPs.

[0618] FDM scheme B 2810 is a scheme that first divides a scheduled PUSCH resource into two halves in the frequency domain according to the FDM scheme, configures each of the divided PUSCH resources as a TB to be sent using each panel, and then encodes the information bit. Thereafter, the terminal sends the same TB via each panel. In this case, the TB sent via each panel may have the same redundant version (RV) sequence or may have different RV sequences. Since the result is obtained by rate matching according to each RV sequence in a buffer of coded bits encoded via one TB, the FDM scheme 2810 may be referred to as repeated transmission. For example, the terminal may send 2811 a first repeatedly transmitted part via a first panel and send 2812 a second repeatedly transmitted part via a second panel. In this case, if the repeatedly transmitted TB is transmitted via the corresponding panel and is transmitted to different TRPs by using the corresponding corresponding panel, the repeatedly transmitted TB is received in one TRP. Thereafter, the base station may collect the parts into one and perform joint decoding or separate decoding according to the implementation of the base station, thereby receiving the signal sent by the terminal. In FDM scheme B, 2815 DMRS may be transmitted over all PUSCH resources. Alternatively, DMRS may be transmitted over corresponding PUSCH portions transmitted to different TRPs, where different DMRS ports may be configured or different DMRS sequences may be used for DMRS transmitted to different TRPs.

[0619] The SDM scheme 2820 is a scheme in which all resources of a scheduled PUSCH are configured as a TB and information bits are encoded based on this, taking into account the number of all layers. Thereafter, according to the SDM scheme, the terminal can divide the resources into two halves in the spatial domain so as to simultaneously send the resources at the same time point by using the corresponding panel. That is, the terminal sends different layers by dividing each layer into the corresponding panel. For example, the terminal can send the first part 2821 (including a part of the layer with a low index) via the first panel, and can send the second part 2822 (a part other than the first part) via the second panel. This is just an example, and the corresponding part can be mapped to the panel so as to be sent in an order different from the order in the example (for example, the first part can be sent via the second panel, and the second part can be sent via the first panel). For the DMRS 2825 of the PUSCH sent via the corresponding panel, different DMRS ports can be configured, and different DMRS ports can be included in different CDM groups. Alternatively, the DMRS can be included in the same CDM group with different DMRS ports. In this case, if one TB is divided into two halves and transmitted via corresponding panels, and transmission is performed to different TRPs by using the corresponding panels, a portion of one TB is received in one TRP. Thereafter, the base station can collect the portions into one and perform joint decoding or separate decoding according to the implementation method of the base station, thereby receiving the signal sent by the terminal.

[0620] The SFM scheme 2830 is a scheme for performing transmission by configuring the same DMRS and the exact same TB in the same frequency resource and the same time resource. The PUSCH sent via the corresponding panel may include the same data and the same DMRS. That is, the terminal may send the first part 2831 via the first panel and send the second part via the second panel 2832. This is just an example, and the corresponding parts may be mapped to the panels so as to be sent in an order different from the order in the example (for example, the first part may be sent via the second panel, and the second part may be sent via the first panel). In this case, if the same TB is sent via the corresponding panel and sent to different TRPs by using the corresponding panel, the same TB is received in one TRP. Thereafter, the base station may collect the parts into one and perform joint decoding or separate decoding according to the implementation of the base station, thereby receiving the signal sent by the terminal. In the SFN scheme 2830, the DMRS sent to the corresponding panel may be configured with the same DMRS port 2835.

[0621] In addition to the above Fig.28In addition to the transmission method described in the embodiment, repeated transmission of the same TB based on the SDM scheme can also be supported. That is, any scheme that can simultaneously transmit in the time domain by using different panels can follow the UCI multiplexing method according to this embodiment.

[0622] In the case of considering various transmission schemes for supporting STxMP as described above, transmission channel configuration methods in two directions can be considered. In the first transmission channel configuration method, the terminal can repeatedly send the same information by using the corresponding panel. In the second transmission channel configuration method, the terminal can send different information by using different panels via spatial multiplexing (SM). According to the second transmission channel configuration method, the terminal can configure the same transmission block (TB) and perform resource mapping to different frequency domains or different layers in order to send the same transmission block, and the terminal can configure different TBs according to the corresponding panel and map these TBs to different frequency domains or different layers in order to send the same transmission block. Prior to NR version 17, the uplink support has supported the transmission using only one TB (or can be expressed as a codeword (CW)), so that in order to support TBs greater than one TB, a higher layer configuration for this and a new DCI field configuration within the DCI may be required.

[0623] The terminal may perform UCI multiplexing by considering whether UCI included in PUCCH or PUSCH has the same priority index (indicator) or different priority indexes. UCI having the same priority index may be assumed, and a method of multiplexing UCI accordingly by the terminal may be as follows.

[0624] Example 1) If the terminal:

[0625] - UCI needs to be multiplexed on a PUCCH transmission that overlaps with a PUSCH transmission, and

[0626] - As described above with respect to rate matching of UCI multiplexed to PUSCH, if PUSCH and PUCCH meet the conditions for multiplexing UCI (the timeline conditions specified in clause 9.2.5 of 3GPP standard TS 38.213),

[0627] terminal:

[0628] - If the terminal multiplexes aperiodic or semi-persistent CSI reporting on PUSCH, only HARQ-ACK information from UCI is multiplexed on PUSCH transmission and PUCCH is not transmitted.

[0629] - If the terminal does not multiplex aperiodic or semi-persistent CSI reporting on PUSCH, HARQ-ACK and CSI reporting (if any) for UCI are multiplexed on PUSCH transmission and PUCCH is not sent.

[0630] Example 2) If the terminal multiplexes non-periodic CSI on PUSCH and multiplexes UCI including HARQ-ACK information on PUCCH overlapping with PUSCH, and the timeline condition specified in clause 9.2.5 of standard TS 38.213 is satisfied, the terminal multiplexes HARQ-ACK information on PUSCH and does not send PUCCH.

[0631] In addition to the aforementioned operation of multiplexing UCI by the terminal, the terminal may also multiplex UCI according to a specific operation described in clause 9 of 3GPP standard TS 38.213 and transmit only some uplink channels.

[0632] In NR Release 17, if the terminal multiplexes UCI on PUSCH when the timeline condition and UCI multiplexing condition as described above are met, the terminal may multiplex UCI on PUSCH in the following order:

[0633] -The terminal can identify the resources of the PUSCH on which the UCI is multiplexed. In this case, for the PUSCH transmitted based on the DCI format received by the terminal, the PUSCH resource amount (or TB size) can be identified based on the scheduling information included in the DCI (e.g., time domain resource allocation region, frequency domain resource allocation region, MCS region, SRI region, TPMI region, antenna port region for indicating a DMRS port, etc.). If the PUSCH corresponds to a PUSCH transmission according to a configuration based on a configuration grant, the PUSCH resource amount (or TB size) can be identified by referring to a higher layer configuration, a DCI format for activating transmission, or a DCI format including scheduling information other than a higher layer configuration, etc.

[0634] -The terminal calculates the number of coded modulation symbols per layer according to the UCI type, as described above for rate matching of UCI multiplexed on the PUSCH. In this case, the terminal calculates the number of coded modulation symbols per layer based on information such as the amount of resources (or TB size) of the scheduled PUSCH, the number of bits of UCI information such as HARQ-ACK information and CSI information, the beta offset value for the UCI type, and the code rate for the coding block.

[0635] - The terminal performs channel coding taking into account the number of coded bits used to encode the UCI.

[0636] -The terminal multiplexes the coded bits for UCI on the PUSCH. In this case, according to each piece of information of UCI, the terminal maps and multiplexes the coded bits for UCI on the PUSCH resources according to the following order.

[0637] * The terminal first multiplexes the HARQ-ACK information. In this case, if frequency hopping is not performed on the PUSCH, the HARQ-ACK information is multiplexed on the PUSCH while starting from the first OFDM symbol index l with respect to all layers of the scheduled PUSCH. (1) The OFDM symbol of the PUSCH is mapped sequentially over all layers for the corresponding subcarriers and symbols, and then sequentially maps the HARQ-ACK information over all layers for the subsequent subcarrier indexes. When the HARQ-ACK information has been mapped over the subcarriers in all layers and corresponding symbols, the same multiplexing process is performed for the subsequent OFDM symbol indexes. If there is CG-UCI after the terminal first multiplexes all HARQ-ACK information on PUSCH, the CG-UCI can be multiplexed on PUSCH in the same manner as the method of multiplexing HARQ-ACK information. If there is CSI information after multiplexing both the HARQ-ACK information and the CG-UCI information, the CSI information is multiplexed on PUSCH in a similar manner. Here, the CSI information includes both CSI part 1 and CSI part 2, and the terminal first multiplexes CSI part 1 on the PUSCH and then multiplexes CSI part 2 on the PUSCH. The terminal multiplexes CSI information on the PUSCH in a similar manner. (1) Different, as the OFDM symbol index used as a reference for first mapping the CSI information is defined as the index of the first OFDM symbol that does not include DMRS. The terminal identifies whether it can The CSI information is multiplexed with the symbols indexed by the OFDM symbols, and the CSI information is mapped while increasing the index in the order of layer-frequency-symbol similar to the mapping of the above-mentioned HARQ-ACK information.

[0638] * Even when frequency hopping is performed on the PUSCH, UCI is multiplexed on the PUSCH similarly to the case where frequency hopping is not performed on the PUSCH as described above, but with respect to each frequency hopping, HARQ-ACK, CG-UCI, or CSI information is divided into two parts for each frequency hop, and each part is multiplexed on the PUSCH transmitted on each frequency hop. In this case, an index used as a reference for OFDM symbols on which HARQ-ACK information and CSI information are mapped is defined for each frequency hop. (1) may be defined as the index of the first OFDM symbol after the first set of OFDM symbols including DMRS on the first frequency hop, and l(2) It can be defined as the index of the first OFDM symbol after the first set of OFDM symbols including DMRS on the second frequency hop. may be defined as the index of the first OFDM symbol that does not include a DMRS in the first frequency hop, and It can be defined as the index of the first OFDM symbol that does not include DMRS in the second frequency hop. The terminal multiplexes the PUSCH by referring to l with respect to each frequency hop. (1) , l (2) , or Each UCI information divided for each hop.

[0639] As described above, before NR version 17, the terminal multiplexed UCI in consideration of all resources scheduled for PUSCH. This may indicate that UCI is multiplexed for all TBs for PUSCH transmission. If UCI is multiplexed in this manner, the multiplexed UCI may be sent to different TRPs via different panels because simultaneous transmission using multiple panels is not considered. For example, if a TB is divided in the frequency domain and sent via the corresponding panel as in FDM scheme A2800, the multiplexed UCI may be sent to different TRPs via different frequency domains. In order to decode UCI, the base station may need to perform joint decoding by combining the received UCI that has been divided into the corresponding TRP into one, so as to successfully receive UCI information. For example, as in SDM scheme 2820, if a TB is divided in the spatial domain and the divided layers are sent via the corresponding panel, the multiplexed UCI may be sent to different TRPs via different layers. Similarly, in order to decode UCI, the base station may need to perform joint decoding by combining the received UCI that has been divided into the corresponding TRP into one, so as to successfully receive UCI information.

[0640] However, blocking may occur in a specific direction between the base station and the terminal, and the channel state in the corresponding direction may be bad. As a result, if the signal sent via a specific panel is not successfully received by the corresponding TRP or base station due to blocking, the base station may ultimately fail to receive the entire UCI. Since the UCI information that may include HARQ-ACK or CSI reports has a relatively higher importance than data, more reliable transmission may be required. Therefore, even if blocking occurs with a small probability, a transmission method that can ensure high reliability may be required to send UCI information in order to prevent the problem of decoding failure due to blocking. As a UCI multiplexing method that can ensure high reliability, the following method can be considered.

[0641] [Method 1] By introducing a new type of beta offset value, UCI can be sent so that highly reliable coding is possible at a lower code rate. Prior to NR Release 17, configuration of different beta offset values ​​was possible according to each UCI type (e.g., HARQ-ACK, CSI part 1, or CSI part 2). By extending this, when PUSCH including UCI is sent via multiple panels, UCI can be encoded according to the extended beta offset configuration value.

[0642] In this case, the base station and the terminal can work as in the following example. First, the terminal can report the UE capability for multi-panel transmission to the base station. In this case, the terminal can report the supportable multi-panel-based STxMP transmission method and the necessary detailed information thereof. The terminal can additionally report the ability to use the new beta offset when considering STxMP. For example, the terminal can report the ability to use the new beta offset to the base station by configuring the UE capability of "betaoffsetforSTxMP" as "enable". Alternatively, the terminal can perform the UE report to the base station by configuring the corresponding function to be enabled via the UE capability area with different names for similar or identical functions. Alternatively, the ability to use the new beta offset can be implicitly included as part of the UE function report indicating that STxMP may be sent. The base station can determine whether STxMP is supported based on the UE capability received from the terminal, and if STxMP is supported for the terminal, the base station can configure the relevant higher-layer parameters for the terminal. As an example of a new higher-layer parameter, a configuration such as a new "BetaOffsets2" or "BetaOffsetsforSTxMP" can be considered. Table 43 describes 'BetaOffsets2' as an example of a new higher layer parameter.

[0643] [Table 43]

[0644]

[0645] Similar to the higher layer parameter "BetaOffsets" before NR Release 17, different index values, such as "betaOffsetACK-Index1", "betaOffsetACK-Index2" or "betaOffsetACK-Index3", may be configured depending on the number of bits per HARQ-ACK, CSI part 1 or CSI part 2. Here, the candidate values ​​may be expressed by 0 to xx, and the value of xx may be 31 as in NR Release 17. Alternatively, the value of xx may be any value of an exponent of 2-1, and 16-1=15 may be configured as xx, for example. Due to the introduction of a new beta offset, a new table for determining a beta value via an index configured in a higher layer parameter may be defined. Prior to NR Release 17, the terminal determined the beta value for multiplexing HARQ-ACK by mapping the index value configured in "BetaOffsets" to Table 9.3-1 (Table 44 below) in 3GPP standard TS 38.213. As an example, if the index value of betaOffsetACK-Index2 configured for the case where the number of HARQ-ACK information bits is greater than 2 and less than or equal to 11 is 6, the beta value is determined to be 6.250 as a value corresponding to index 6 in Table 44 below, and the terminal can use the beta value for rate matching of the corresponding HARQ-ACK as described above. The contents described in Table 44 below are merely examples, and the beta offset value can be determined based on other references and values.

[0646] [Table 44]

[0647]

[0648] If the terminal sends a PUSCH including HARQ-ACK via STxMP, the terminal can determine the beta value for HARQ-ACK sent for STxMP by referring to the new higher layer parameter "betaOffsets2" (or any higher layer parameter with the same function) and the following Table 45, instead of determining the beta value for HARQ-ACK by referring to the higher layer parameter "betaOffsets" and Table 44, and the determined beta value can be used for UCI multiplexing. Similar to the above example, if the index value of the configured betaOffsetACK-Index2 in "betaOffsets2" is 6 for the case where the number of bits of the HARQ-ACK information is greater than 2 and less than or equal to 11, the terminal determines "value 7 for STxMP" as the beta value by referring to the following Table 45. The terminal can then calculate the number of coded modulation symbols per layer and perform multiplexing in the same manner. Even for CSI part 1 and CSI part 2, the terminal can determine the beta value by referring to Table 45 and the new higher layer parameters for each UCI. The contents described in Table 45 are merely examples, and the beta offset value may be determined based on other references and values.

[0649] [Table 45]

[0650]

[0651] The above method is merely an example, and the new higher layer parameters and beta values ​​can be determined by referring to Table 44 in NR Release 17. Alternatively, as in NR Release 17, the higher layer parameter "betaOffsets" can be configured, and the beta value can be determined by referring to Table 45. Alternatively, based on any combination of using the above configuration and Table 45, the terminal can determine the beta value for the corresponding UCI. The higher layer parameters and Table 45 newly defined according to Method 1 can be applied so that the terminal determines the beta value only when a PUSCH on which UCI is multiplexed is sent via STxMP using multiple panels, and if the PUSCH is not sent via PUSCHSTxMP, the beta value can be determined in the same manner as the terminal operation before NR Release 17. Alternatively, the terminal can determine the beta value based on Table 45 and the higher layer parameters newly defined for all cases, instead of following the terminal operation before NR Release 17.

[0652] [Method 2] The terminal can identify the resources of the PUSCH on which the UCI is multiplexed, and repeatedly send the UCI in both panels according to the conditions. Before multiplexing UCI on the PUSCH, the terminal identifies the amount of PUSCH resources (or TB) sent simultaneously via the corresponding panel. In this case, the amount of PUSCH resources (or TB) sent simultaneously via the corresponding panel can be determined based on the MCS (for example, which can refer to the modulation order and the target code rate), the number of layers, the number of allocated PRBs, the number of allocated OFDM symbols, the DMRS overhead, etc.). If the amount of PUSCH resources (or TB) sent via the corresponding panel is the same, the terminal can repeatedly multiplex the same UCI on each PUSCH. In this case, the terminal can perform multiplexing so that the repeatedly multiplexed UCI coded bits can be mapped to the same position of the PUSCH.

[0653] In this way, by mapping the same UCI coded bit to the same position of PUSCH, the terminal can multiplex UCI so that the UCI received by each TRP (or base station) can be combined and decoded. This is because UCI is channel coded differently from the data mapped to PUSCH. Although the data is encoded / decoded based on a low-density parity check (LDPC) code, the UCI information can be encoded / decoded using a repetition code, a Reed-Muller code, a polarity code, etc. according to the number of UCI bits. In particular, for the coded bits of UCI encoded based on polarity codes, it is necessary to ensure the same coded bit length and the same multiplexing position in order to achieve performance gain and decoding using a combination. If the UCI bits are repeatedly sent in this way, although the uplink signal including UCI sent via one panel is not received by the base station due to blocking, the uplink signal including UCI sent via another panel can be successfully received by the base station. Thereafter, the base station can understand the UCI information by decoding the uplink signal successfully received from one panel. That is, even if the base station fails to receive the data included in the PUSCH, since each UCI is repeatedly transmitted, even if only the PUSCH transmitted from one panel is successfully received, the UCI can be successfully decoded and the UCI information can be recognized. When UCI is multiplexed on the PUSCH according to method 2, the base station and the terminal can perform the following operations. The terminal can report the UE capability for multi-panel transmission to the base station. In this case, the terminal can report the supportable multi-panel-based STxMP transmission method and its necessary detailed information.

[0654] In addition, whether UCI can be repeatedly multiplexed in two panel transmissions according to the amount of PUSCH resources (or TB) sent via each panel as in method 2 can be notified to the base station as a UE report. Thus, the UE report for reporting whether method 2 is supported can be explicitly reported via a new UE reporting parameter. Alternatively, when the terminal reports to the base station the UE capability indicating support for STxMP transmission, the base station and the terminal can define rules in advance, that is, the capability for method 2 should also be supported. In this case, whether the terminal supports the capability for method 2 is reported via a UE capability report supporting STxMP transmission, and therefore, it can be defined whether the capability for method 2 is supported to be implicitly reported. If the terminal explicitly or implicitly reports to the base station that the terminal can support method 2, the base station can first determine whether STxMP is supported based on the report, and then determine whether method 2 is supported separately. Alternatively, if STxMP is supported, it can be determined that method 2 is supported without additional conditions.

[0655] If the base station supports STxMP and method 2 for the terminal, the base station can configure higher layer parameters for supporting STxMP and higher layer parameters for supporting method 2 for the terminal. The higher layer parameters for supporting STxMP can report the supported STxMP transmission methods and the detailed information required for this in the same manner, as described in method 1. The higher layer parameters for supporting method 2 can be an indicator for indicating whether the terminal uses two panels to repeatedly multiplex UCI on two PUSCHs according to method 2. For example, a new higher layer parameter "UCIrepetition_forSTxMP" (or a higher layer parameter with a different name for a similar / same function) can be configured as "enable" (or any value for indicating support, such as "1"). Although the new higher layer parameter "UCIrepetition_forSTxMP" has been introduced, if the higher layer parameter is not configured (does not exist) for the terminal, the terminal can recognize that the base station does not support method 2 and can multiplex UCI on PUSCH in the same manner as in NR version 17. Alternatively, if the base station and the terminal define in advance rules for implicitly supporting method 2 when supporting STxMP, the terminal can recognize support for method 2 by recognizing that higher layer parameters for supporting STxMP have been configured for the terminal even without introducing a separate new higher layer parameter "UCIrepetition_forSTxMP".

[0656] Thereafter, for the UCI and uplink data to be sent to the base station, the terminal may send a scheduling request (SR) for PUSCH transmission to the base station, and based on the SR, the base station may send a DCI format for scheduling PUSCH to the terminal. The terminal may identify the scheduled PUSCH by receiving the DCI format, and may assume that the scheduled PUSCH is the PUSCH transmitted via STxMP. Alternatively, PUSCH resources may be scheduled based on higher layer parameters based on the configured permission, and the scheduled PUSCH may be identified based on the configured higher layer parameters (for the permitted PUSCH configured in type 2, the scheduled PUSCH may be identified only when the DCI format is received together with the higher layer parameters). In this case, another uplink channel overlapping with the scheduled PUSCH transmitted via STxMP (hereinafter, simply expressed as the scheduled PUSCH) may also be identified. If there is another uplink channel overlapping with the scheduled PUSCH in the time domain, the uplink channel to be transmitted and the UCI to be multiplexed may be determined via the same process as in NR version 17. In this case, it is assumed that the scheduled PUSCH is sent by the terminal and the UCI is multiplexed on the PUSCH, and the operation of the terminal and the base station according to method 2 is described in more detail below. The terminal identifies whether the amount of resources of the PUSCH (or TB) sent via the corresponding panel is the same. If the amount of PUSCH resources (or TB) sent via the corresponding panel is the same, the terminal calculates the number of coded modulation symbols per layer for UCI and performs rate matching for the corresponding panel in consideration of the amount of PUSCH resources (or TB). In order to make the amount of PUSCH resources (or TB) sent via the corresponding panel the same, a prerequisite may be required according to the FDM scheme or the SDM scheme. For example, in FDM-based STxMP, for the same amount of resources, all PUSCH resources need to be scheduled with even RBs. This is because when the RB is divided into two halves, only even RBs can be allocated as PUSCH resources in which an integer number of RBs are sent via the corresponding panel. Similarly, in SDM-based STxMP, in order to allocate the same amount of resources, all PUSCH resources need to be scheduled with even layers (or ranks).

[0657] As described above, if the prerequisite is met according to the STxMP transmission scheme and the amount of resources of the PUSCH (or TB) transmitted via the corresponding panel is the same, the parameter value considered for calculating the number of coded modulation symbols per layer may vary according to the STxMP transmission method of the scheduled PUSCH. For example, if the scheduled PUSCH is transmitted in the FDM-based STxMP scheme, the terminal may consider the number of subcarriers in the frequency domain for the PUSCH transmitted via one panel according to the FDM scheme in order to calculate the number of coded modulation symbols per layer. Instead of considering the number of subcarriers scheduled for PUSCH in the frequency domain For a specific example, as described in equation (6) above, in the equation for calculating each layer of coded modulation symbols for HARQ-ACK multiplexed on PUSCH for cases other than repeated PUSCH transmission type B including UL-SCH, if modifications are made while considering the subcarriers of the PUSCH transmitted via one panel when transmission is performed in an FDM-based STxMP scheme, equation (18) can be obtained.

[0658]

[0659] Equation (18) is used to calculate each layer of coded modulation symbols for HARQ-ACK in the case of two divided PUSCH resources, in which all scheduled PUSCH resources are divided into two halves in the frequency domain according to the FDM scheme to be sent via the corresponding panel. Similarly, even for CG-UCI, CSI part 1 or CSI part 2, it can be considered when calculating each layer of coded modulation symbols taking into account that the resources are divided into two halves in the frequency domain according to the FDM scheme. Rather than

[0660] If the scheduled PUSCH is sent in the SDM-based STxMP scheme, the terminal may consider Then, when determining the number of UCI bits E UCI (N L *Q′*Q m ), the terminal can use N by considering the number of layers divided into two halves according to the SDM scheme. L / 2 instead of N L To calculate the UCI quantile.

[0661] Thereafter, the terminal can encode the UCI information according to the calculated number of UCI bits, generate modulation symbols, and repeatedly multiplex the modulation symbols on two PUSCHs sent via the corresponding panel. Since the resource amount (or TB) of the two PUSCHs sent via the corresponding panel is the same and the modulation symbols for the same UCI are multiplexed, the terminal multiplexes the UCI modulation symbols at the same position in the two PUSCHs. Here, the same position may refer to a position determined to be the same or to correspond to each other in a resource region during multiplexing on each PUSCH when considering the frequency in FDM and considering the layer in SDM, as shown in an example of multiplexing UCI in a STxMP transmission scenario based on FDM and SDM. Fig.29 Same as in.

[0662] Specifically, according to the scheme of FDM scheme A2900, the terminal can multiplex 2903 UCI and send the first part 2901 of all PUSCH resources (for example, a part of RBs including low indexes) via the first panel at the same time. In addition, the terminal can multiplex 2904 UCI and send the second part 2902 of all PUSCH resources (for example, a part of RBs including high indexes) via the second panel at the same time. Since the UCI sent via different parts of the entire PUSCH is the same UCI modulation symbol, the same UCI can be sent repeatedly. Unlike the above-mentioned embodiment, it is undoubtedly possible that the first part of all PUSCH resources is sent via the second panel, and the second part of all PUSCH resources is sent via the first panel. In this case, if one TB is divided into two halves and sent via the corresponding panel, and the transmission is performed to different TRPs by using the corresponding panel, a part of one TB is received in one TRP. Thereafter, the base station can collect the TB and UCI into one and perform joint decoding or separate decoding according to the implementation method of the base station, thereby receiving the signal sent by the terminal.

[0663] According to the SDM scheme 2920, the terminal can divide the resources into two halves in the spatial domain so as to simultaneously send the resources at the same time point via the corresponding panel. Specifically, the terminal can reuse 2923 UCI and send the first resource part 2921 (for example, a part of the layer including the low index) via the first panel at the same time. In addition, the terminal can reuse 2924 UCI and send the second resource part 2922 (for example, a part of the layer including the high index or a part other than the first part) via the second panel at the same time. Since the UCI sent via different layers of all resources is the same UCI modulation symbol, the same UCI can be sent repeatedly. Unlike the above-mentioned embodiment, it is undoubtedly possible that the first resource part is sent via the second panel and the second resource part is sent via the first panel. For the DMRS of the PUSCH sent via the corresponding panel, different DMRS ports can be configured, and different DMRS ports can be included in different CDM groups. Alternatively, the DMRS can be included in the same CDM group with different DMRS ports. In this case, if a TB is divided into two halves and sent via the corresponding panel, and the transmission is performed to different TRPs by using the corresponding panel, a part of a TB is received in one TRP. Thereafter, the base station may collect the TB and the UCI into one and perform joint decoding or separate decoding according to an implementation manner of the base station, thereby receiving a signal sent by the terminal.

[0664] [Method 3] Method 3 is a method for the operation of the terminal and the base station when the resource amount of the PUSCH (or TB) sent by the terminal via the corresponding panel in Method 2 is different. When the terminal identifies that the resource amount of the PUSCH (or TB) sent via the corresponding panel is the same, the method of multiplexing UCI on the PUSCH with the same resource amount can be defined as Method 2. On the other hand, the terminal has identified whether the resource amount of the PUSCH (or TB) sent via the corresponding panel is the same, but if the resource amount of the corresponding PUSCH is not the same, the method of multiplexing UCI on the PUSCH with the same resource amount can be defined as in Method 3. In Method 3, the higher layer parameter configuration and UE capability report between the base station and the terminal can be defined in the same manner as in Method 2. Similarly, if a higher layer parameter (e.g., "UCIrepetition_forSTxMP") is configured in Method 2 and Method 3 or STxMP is explicitly supported, the base station and the terminal can understand that Method 2 and Method 3 are implicitly supported. Thereafter, based on the PUSCH scheduling based on the configured permission or the DCI format including the PUSCH scheduling information for STxMP transmission, the amount of PUSCH resources (or TB) to be sent by the terminal can be identified. In this case, if there is another uplink channel that overlaps with the scheduled PUSCH (hereinafter, simply expressed as scheduled PUSCH) transmitted via STxMP, the uplink channel is processed in the same manner as in method 2. Then, if UCI is multiplexed on the scheduled PUSCH, the terminal identifies whether the amount of resources of the PUSCH (or TB) transmitted via the corresponding panel is the same. If the amount of resources of the PUSCH (or TB) transmitted via the corresponding panel is not the same, UCI can be multiplexed on the PUSCH according to one of the following multiple methods or a combination thereof.

[0665] [Method 3-1] UCI is multiplexed only on the PUSCH sent via one panel. If the resource amounts of two PUSCHs sent simultaneously via two panels are different, the terminal can select one PUSCH sent via one panel, multiplex UCI on the corresponding PUSCH, and send UCI to the base station. In this case, in order to select a PUSCH, the terminal can consider one or more combinations of the following items.

[0666] - Perform UCI multiplexing by selecting a PUSCH including PRB resources of lower or higher indexes (for FDM scheme);

[0667] - Perform UCI multiplexing by selecting a PUSCH including a lower or higher indexed layer (for SDM scheme);

[0668] - Compare resource amounts of PUSCHs transmitted via corresponding panels, and perform UCI multiplexing by selecting a PUSCH with a larger resource amount or a PUSCH with a smaller resource amount; and

[0669] -If the MCSs of PUSCHs transmitted via a plurality of panels are different, UCI multiplexing is performed by selecting a PUSCH with a higher or lower coding rate.

[0670] [Method 3-2] UCI is multiplexed in the same manner as in NR Release 17. If the amount of resources of two PUSCHs simultaneously transmitted in two panels is different, the terminal multiplexes UCI on the PUSCH in the same manner as in the method of multiplexing UCI before NR Release 17. That is, UCI is multiplexed over subcarriers in the entire frequency domain and layers in the spatial domain by considering the number of all scheduled PUSCH resources without considering the resource division due to the transmission of each panel. In this way, if each panel is used to transmit a PUSCH on which UCI is multiplexed, the base station may need to decode the UCI information by jointly decoding each transmitted PUSCH.

[0671] [Method 3-4] In order to repeatedly multiplex UCI on the PUSCH sent via the corresponding panel, the following prerequisites need to be met. That is, if the terminal sends PUSCH in the STxMP scheme and needs to multiplex UCI on PUSCH, the terminal does not expect that the following conditions are not met. The following is an example of the conditions that need to be met when sending PUSCH in the STxMP scheme and multiplexing UCI on PUSCH.

[0672] - If PUSCH is transmitted in the FDM-based STxMP scheme and UCI is multiplexed on PUSCH, two or more even-numbered PRBs are scheduled as PUSCH resources.

[0673] - If PUSCH is transmitted and UCI is multiplexed on PUSCH in the SDM-based STxMP scheme, two or more even layers (or ranks) are scheduled for PUSCH.

[0674] - If PUSCH is transmitted in the STxMP scheme and UCI is multiplexed on the PUSCH, scheduling is performed so that the MCSs used for corresponding PUSCH transmissions are the same.

[0675] - If PUSCH is transmitted in the STxMP scheme and UCI is multiplexed on PUSCH, the same number of OFDM symbols are scheduled for PUSCH in the time domain.

[0676] In addition to the above examples, any additional conditions that enable resource amounts of PUSCHs transmitted via corresponding panels to be equally scheduled may also be included, and the terminal may not expect the conditions to be not satisfied.

[0677] Fourth embodiment: for handling overlapping uplinks when using multiple panels to support simultaneous uplink transmissions Channel Overlap Rules

[0678] The fourth embodiment provides a detailed description of a method of determining an uplink channel for transmission when an uplink channel simultaneously transmitted via a plurality of panels and another scheduled uplink channel overlap in the time domain and a method of determining an uplink channel on which UCI is multiplexed.

[0679] Prior to NR version 17, if PUCCH and PUSCH overlap in the time domain, the terminal determines the uplink channel to be sent according to the timeline condition and the UCI multiplexed on the uplink channel, and performs uplink channel transmission according to the overlapping rule to determine whether to multiplex the UCI multiplexed on the uplink channel not transmitted on the uplink channel to be transmitted. Prior to NR version 17, since a method of simultaneously transmitting multiple uplink channels in the time domain by using multiple panels is not supported, the overlapping rule prior to NR version 17 cannot provide a method for performing UCI multiplexing and a method for determining the transmission channel by considering STxMP transmission.

[0680] Prior to NR Release 17, if PUCCH is repeatedly transmitted and PUCCH overlaps with PUSCH in the time domain, the terminal does not transmit PUSCH in the overlapping time slot (for repeated PUSCH transmission type A) or does not perform overlapping actual repeated PUSCH transmission (for repeated PUSCH transmission type B). Similarly, since the overlapping rule between repeated PUCCH transmission and PUSCH prior to NR Release 17 does not consider STxMP transmission, operation in consideration of STxMP transmission cannot be provided.

[0681] According to Embodiment 4-1, a detailed description is provided for an enhanced overlapping rule for handling a situation where PUSCHs transmitted using multiple panels in an STxMP scheme and repeated PUCCH transmissions overlap in the time domain. According to Embodiment 4-2, a detailed description is provided for a method for determining a PUSCH on which UCI is multiplexed from among multiple PUSCHs when PUCCHs and PUSCHs transmitted in an STxMP scheme overlap in the time domain and UCI in the PUCCH is multiplexed on the PUSCH.

[0682] Embodiment 4-1: Enhanced overlap rule for solving the situation where PUSCH and repeated PUCCH transmissions transmitted in the STxMP scheme overlap in the time domain

[0683] In Embodiment 4-1, terminal operations for handling a case in which PUSCH transmitted using multiple panels and repeated PUCCH transmission overlap in the time domain in the STxMP scheme are described in more detail below.

[0684] As described above, before NR version 17, if the repeatedly transmitted PUCCH and PUSCH overlap in the time domain, the terminal transmits the PUCCH without transmitting the overlapping PUSCH regardless of the priority of the UCI included in each channel. However, if the PUSCH can be transmitted simultaneously via multiple panels, and reliability can be obtained through sufficient diversity gain by transmitting to different TRPs, a new overlapping rule can be defined so that the terminal multiplexes the UCI in the PUCCH on the PUSCH and transmits the PUSCH, instead of discarding the PUSCH and transmitting only the PUCCH. That is, for the repeatedly transmitted PUCCH and the PUSCH overlapping in the time domain, the PUSCH is transmitted simultaneously by using multiple panels in the STxMP scheme, and the terminal may transmit the PUSCH simultaneously without transmitting the PUCCH according to one of the following detailed methods or a combination of multiple detailed methods.

[0685] [Method 4-1-1] For a PUCCH that is repeatedly transmitted and a PUSCH that overlaps in the time domain, the PUSCH is simultaneously transmitted in the STxMP scheme by using multiple panels, and the terminal identifies whether UCI can be multiplexed on all PUSCHs according to the amount of PUSCH resources (or TB) transmitted via all panels as in Method 2 of the above-mentioned Embodiment 3. Then, if UCI can be multiplexed on the PUSCH transmitted via all panels according to Method 2 of this Embodiment 3, the terminal repeatedly multiplexes UCI on the PUSCH transmitted via all panels without transmitting PUCCH in the same manner as in Method 2. That is, if the amount of resources of the PUSCH transmitted via all panels is the same, the terminal repeatedly multiplexes UCI in the PUCCH on all PUSCHs without transmitting PUCCH. In this case, the UCI multiplexed on the PUSCH can be determined in the same manner as in NR Version 17. That is, if CSI information is not multiplexed on PUSCH, the terminal may repeatedly multiplex the HARQ-ACK information and CSI information included in the PUCCH on the PUSCH sent via all panels. On the other hand, if CSI information is multiplexed on PUSCH, the terminal may repeatedly multiplex only the HARQ-ACK information included in the PUCCH on the PUSCH sent via all panels. Alternatively, regardless of the operation in NR version 17, the terminal may repeatedly multiplex all UCI information except the SR information included in the PUCCH on the PUSCH sent via all panels. The terminal may repeatedly apply the operation of multiplexing UCI on PUSCH to all time slots in which PUCCH and PUSCH overlap. Alternatively, the terminal may multiplex UCI only for the first overlapping time slot, and then may neither perform UCI multiplexing nor repeat PUCCH transmission.

[0686] If the amount of resources of the PUSCH transmitted via the corresponding panels is not the same, the terminal may not transmit the PUSCH transmitted simultaneously in the STxMP scheme by using multiple panels, where the PUSCH and the repeatedly transmitted PUCCH overlap in the time domain. Alternatively, like multiplexing UCI on PUSCH instead of dropping PUSCH in NR Release 17, the terminal may multiplex and transmit UCI over all scheduled subcarriers and all layers while considering all scheduled PUSCH resources without repeatedly multiplexing UCI.

[0687] [Method 4-1-2] For a repeatedly transmitted PUCCH and a PUSCH overlapping in the time domain, the PUSCH is simultaneously transmitted by using multiple panels in the STxMP scheme, and the terminal may select one PUSCH (or multiple PUSCHs) on which UCI is multiplexed from among multiple PUSCHs, multiplex UCI on the selected PUSCH, and may not transmit the PUCCH. Alternatively, the terminal may multiplex UCI only for the first overlapping time slot, and then may neither perform UCI multiplexing nor perform repeated PUCCH transmission.

[0688] Method 4-1-2 may be applied to all time slots in which PUCCH and PUSCH overlap during repeated transmission. In this case, a method of selecting a PUSCH on which UCI is multiplexed may be one of the methods described in more detail below in Embodiment 4-2 or a combination of a plurality of methods.

[0689] Embodiment 4-2: PUSCH selection and multiplexing method for multiplexing UCI on PUSCH when PUSCH and PUCCH transmitted in STxMP scheme overlap in time domain

[0690] According to Embodiment 4-2, a detailed description is provided for a method of selecting and multiplexing a PUSCH on which UCI is multiplexed from among multiple simultaneously transmitted PUSCHs when PUCCH and PUSCH simultaneously transmitted using multiple panels overlap in the time domain and UCI multiplexed on the PUCCH is multiplexed on the PUSCH.

[0691] As described above, since simultaneous uplink transmission using multiple panels is not supported before NR Release 17, only one uplink channel is allowed to be transmitted for one serving cell at one time opportunity. Therefore, when PUCCH and PUSCH overlap and UCI included in PUCCH is multiplexed on PUSCH, the terminal multiplexes UCI on the overlapping PUSCH without a separate PUSCH selection process. However, if it is possible to simultaneously transmit multiple PUSCHs at the same time opportunity by using multiple panels, the terminal may need to select the PUSCH on which UCI will be multiplexed from among multiple simultaneously transmitted PUSCHs. Fig.30 A diagram illustrating an example of a PUSCH simultaneously transmitted through multiple panels scheduled via multi-DCI (mDCI) or single DCI (sDCI) and an example of scheduled PUSCH and PUCCH overlapping in the time domain is shown.

[0692] If simultaneous PUSCH transmission is scheduled 3000 based on mDCI 3000, the base station can use multiple panels to schedule simultaneous PUSCH transmission 3003 and 3004 for the terminal via multiple DCIs 3001 and 3002 associated with different CORESETPoolIndex values. In addition, DCI 3005 received at a time that satisfies the timeline condition that needs to be satisfied in order to apply the aforementioned overlapping rule can be used to schedule PDSCH 3009 and PUCCH 3006 for HARQ-ACK transmission therefor. In this case, since the scheduled PUSCHs 3003 and 3004 and PUCCH 3006 overlap in the time domain, the terminal can determine one of the PUSCHs 3003 and 3004 on which the UCI included in PUCCH 3006 will be multiplexed by applying the overlapping rule. In this case, since the STxMP-based simultaneous transmission method is not supported before NR Release 17, in this case, there is no rule for the PUSCHs 3003 and 3004 on which the UCI within the PUCCH 3006 will be multiplexed by the terminal. Similarly, even when simultaneous PUSCH transmission is scheduled based on sDCI 3010, there is no PUSCH for the terminal to determine the UCI in the PUCCH 3016 overlapping in the time domain to be multiplexed from among the PUSCHs 3013 and 3014 simultaneously transmitted via a plurality of panels.

[0693] Thus, a method for determining a PUSCH on which UCI included in a PUCCH is to be multiplexed is required.Therefore, a PUSCH on which UCI is to be multiplexed may be determined via one of the following methods or a combination of a plurality of methods.

[0694] -[Selection Method 1] The terminal may repeatedly multiplex UCI on all simultaneously transmitted PUSCHs. In this case, the method of multiplexing UCI to all PUSCHs may be configured in the same manner as Method 2 of Embodiment 3. That is, the terminal may identify whether the amount of resources (or TB) of the simultaneously transmitted PUSCHs is the same, and if the amount of resources is the same, UCI may be repeatedly multiplexed on all PUSCHs as in Method 2. On the other hand, the terminal may identify whether the amount of resources (or TB) of the simultaneously transmitted PUSCHs is the same, and if the amount of resources is not the same, an operation may be performed in Method 3-1 or Method 3-2 of Method 3.

[0695] -[Selection Method 2] UCI may be multiplexed on a PUSCH transmitted on the same uplink transmit beam as that of a scheduled PUCCH. The uplink transmit beams of the PUCCH and PUSCH may be determined based on the indicated TCI state and activated according to the integrated TCI scheme. For multiple PUSCHs transmitted simultaneously via multiple panels, as many TCI states as the number of simultaneously transmitted PUSCHs may be indicated. The terminal may multiplex UCI on a PUSCH transmission of the same TCI state as that used for the scheduled PUCCH among the indicated multiple TCI states. Selection Method 2 may be used for both the case where simultaneous transmission using multiple panels is scheduled based on mDCI and the case where simultaneous transmission using multiple panels is scheduled based on sDCI.

[0696] If overlapping PUCCH is scheduled to be sent to mTRP, PUSCH on which UCI is multiplexed may be determined, or PUCCH may be sent without sending PUSCH according to the following method. Here, PUCCH being scheduled to be sent to mTRP may include a case where PUCCH is also scheduled to be sent simultaneously using multiple panels or is scheduled to perform TDM-based mTRPPUCCH transmission, etc.

[0697] *1) The terminal may repeatedly multiplex UCI on all simultaneously transmitted PUSCHs. In this case, the method of multiplexing UCI to all PUSCHs may be configured in the same manner as method 2 of embodiment 3.

[0698] *2) UCI ​​multiplexing is performed by selecting a PUSCH including PRB resources of lower or higher indexes (for FDM scheme);

[0699] *3) UCI ​​multiplexing is performed by selecting a PUSCH including a lower or higher indexed layer (for SDM scheme);

[0700] *4) If PUCCH is scheduled to be sent to mTRP, PUCCH is sent without sending overlapping PUSCH.

[0701] -[Selection Method 3] The terminal may multiplex the UCI in the PUCCH on a PUSCH scheduled via a DCI associated with the same CORESETPoolIndex as the DCI used to schedule the PUCCH. Selection Method 3 is a method available when simultaneous STxMP-based PUSCH transmission based on mDCI is scheduled. As a specific example, assume that a base station schedules a PUCCH including UCI via a DCI associated with a CORESET whose CORESETPoolIndex is 0 or is not configured, schedules a first simultaneous PUSCH transmission via a DCI associated with a CORESET whose CORESETPoolIndex is 0 or is not configured, and schedules a second simultaneous PUSCH transmission via a DCI associated with a CORESET whose CORESETPoolIndex is 1. In this case, if the PUCCH, the first simultaneous PUSCH transmission, and the second simultaneous PUSCH transmission overlap in the time domain, the terminal may multiplex the UCI on the first simultaneous PUSCH transmission scheduled from a CORESET whose CORESETPoolIndex is the same as the CORESETPoolIndex of the DCI used to schedule the PUCCH. If DCI for scheduling PUCCH is received from a CORESET whose CORESETPoolIndex value is 1, the terminal may multiplex UCI on the second simultaneous PUSCH transmission instead of the first simultaneous PUSCH transmission.

[0702] -[Selection method 4] The terminal can determine the PUSCH on which the UCI included in th...

Claims

1. A method performed by a terminal in a wireless communication system, the method comprising: Receiving first downlink control information DCI; identifying a first physical uplink shared channel PUSCH based on the first DCI; receiving a second DCI; identifying a second PUSCH based on the second DCI; receiving a third DCI; identifying a physical uplink control channel PUCCH for hybrid automatic repeat request acknowledgement HARQ-ACK information based on the third DCI, wherein the PUCCH overlaps with the first PUSCH and the second PUSCH; and In a case where simultaneous transmission of STxMP across multiple panels is enabled, identifying a PUSCH among the first PUSCH and the second PUSCH for multiplexing uplink control information UCI including the HARQ-ACK information, The PUSCH and the PUCCH are associated with the same control resource set CORESET.

2. The method of claim 1, wherein the first DCI is associated with a first CORESET pool index and the second DCI is associated with a second CORESET pool index different from the first CORESET pool index. 3 . The method according to claim 1 , wherein the HARQ-ACK information is for a physical downlink shared channel (PDSCH) scheduled by the third DCI.

4. The method of claim 1 , wherein a beta offset for STxMP is applied to the PUSCH multiplexed with the UCI, and the beta offset for STxMP is different from the beta offset for UCI, and in, In the case where the PUCCH is based on a single frequency network SFN solution: The PUCCH is considered as a PUCCH repetition and the first PUSCH and the second PUSCH are dropped; or The PUCCH is not considered as the PUCCH repetition and the UCI is multiplexed in the PUSCH.

5. A method performed by a base station in a wireless communication system, the method comprising: Sending first downlink control information DCI for a first physical uplink shared channel PUSCH; Sending a second DCI for a second PUSCH; transmitting a third DCI of a physical uplink control channel PUCCH for hybrid automatic repeat request acknowledgement HARQ-ACK information, wherein the PUCCH overlaps with the first PUSCH and the second PUSCH; and In a case where simultaneous transmission of STxMP across multiple panels is enabled, receiving a PUSCH in which uplink control information UCI including the HARQ-ACK information is multiplexed among the first PUSCH and the second PUSCH, The PUSCH and the PUCCH are associated with the same control resource set CORESET.

6. The method of claim 5, wherein the first DCI is associated with a first CORESET pool index and the second DCI is associated with a second CORESET pool index different from the first CORESET pool index, and The HARQ-ACK information is for a physical downlink shared channel PDSCH scheduled by the third DCI.

7. The method of claim 5, wherein a beta offset for STxMP is applied to the PUSCH multiplexed with the UCI, and the beta offset for STxMP is different from the beta offset for UCI, and in, In the case where the PUCCH is based on a single frequency network SFN solution: The PUCCH is considered as a PUCCH repetition and the first PUSCH and the second PUSCH are dropped; or The PUCCH is not considered as the PUCCH repetition and the UCI is multiplexed in the PUSCH.

8. A terminal in a wireless communication system, the terminal comprising: Transceiver; as well as a controller coupled to the transceiver and configured to: Receiving first downlink control information DCI; identifying a first physical uplink shared channel PUSCH based on the first DCI; receiving a second DCI; identifying a second PUSCH based on the second DCI; receiving a third DCI; identifying a physical uplink control channel PUCCH for hybrid automatic repeat request acknowledgement HARQ-ACK information based on the third DCI, wherein the PUCCH overlaps with the first PUSCH and the second PUSCH; and In a case where simultaneous transmission of STxMP across multiple panels is enabled, identifying a PUSCH among the first PUSCH and the second PUSCH for multiplexing uplink control information UCI including the HARQ-ACK information, The PUSCH and the PUCCH are associated with the same control resource set CORESET.

9. The terminal of claim 8, wherein the first DCI is associated with a first CORESET pool index, and the second DCI is associated with a second CORESET pool index different from the first CORESET pool index. 10 . The terminal according to claim 8 , wherein the HARQ-ACK information is for a physical downlink shared channel (PDSCH) scheduled by the third DCI.

11. The terminal according to claim 8, wherein a beta offset for STxMP is applied to the PUSCH multiplexed with the UCI, and the beta offset for STxMP is different from the beta offset for UCI, and in, In the case where the PUCCH is based on a single frequency network SFN solution: The PUCCH is considered as a PUCCH repetition and the first PUSCH and the second PUSCH are dropped; or The PUCCH is not considered as the PUCCH repetition and the UCI is multiplexed in the PUSCH.

12. A base station in a wireless communication system, the base station comprising: Transceiver; as well as a controller coupled to the transceiver and configured to: Sending first downlink control information DCI for a first physical uplink shared channel PUSCH; Sending a second DCI for a second PUSCH; transmitting a third DCI of a physical uplink control channel PUCCH for hybrid automatic repeat request acknowledgement HARQ-ACK information, wherein the PUCCH overlaps with the first PUSCH and the second PUSCH; and In a case where simultaneous transmission of STxMP across multiple panels is enabled, receiving a PUSCH in which uplink control information UCI including the HARQ-ACK information is multiplexed among the first PUSCH and the second PUSCH, The PUSCH and the PUCCH are associated with the same control resource set CORESET.

13. The base station of claim 12, wherein the first DCI is associated with a first CORESET pool index, and the second DCI is associated with a second CORESET pool index different from the first CORESET pool index. 14 . The base station according to claim 12 , wherein the HARQ-ACK information is for a physical downlink shared channel (PDSCH) scheduled by the third DCI.

15. The base station of claim 12, wherein a beta offset for STxMP is applied to the PUSCH multiplexed with the UCI, and the beta offset for STxMP is different from the beta offset for UCI, and in, In the case where the PUCCH is based on a single frequency network SFN solution: The PUCCH is considered as a PUCCH repetition and the first PUSCH and the second PUSCH are dropped; or The PUCCH is not considered as the PUCCH repetition and the UCI is multiplexed in the PUSCH.

Images