Method and apparatus for uplink multi-panel simultaneous transmission in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. The present disclosure relates to a method performed by a terminal in a wireless communication system, the method comprising the steps of: transmitting terminal capability information including information related to multi-panel simultaneous transmission (STxMP) to a base station; receiving an upper layer signal from the base station; checking whether the upper layer signal comprises a parameter for supporting STxMP; if the upper layer signal includes a parameter for supporting the STxMP, checking support for the STxMP based on multiple downlink control information (DCI); receiving, from a base station, a first DCI for scheduling a first physical uplink shared channel (PUSCH) from a first control resource set (CORESET) with a CORESET pool index set to 0, and a second DCI for scheduling a second PUSCH from a second CORESET with a CORESET pool index set to 1; and performing at least a first PUSCH transmission and a second PUSCH transmission overlapping in a time domain based on the STxMP.

Description

Technical Field

[0001] The present disclosure relates to operations of a terminal and a base station in a wireless communication system. In particular, the present disclosure relates to a method for performing simultaneous uplink transmission by using a plurality of panels in a wireless communication system and a device capable of performing the method. Background Art

[0002] 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 GHz, but also in "above 6 GHz" frequency bands called millimeter waves including 28 GHz and 39 GHz. In addition, in order to achieve a transmission rate 50 times faster than 5G mobile communication technology and an ultra-low latency of one-tenth of 5G mobile communication technology, the implementation of 6G mobile communication technology (called a super 5G system) in the terahertz (THz) frequency band (e.g., 95 GHz to 3 THz frequency band) has been considered.

[0003] In the initial stage of 5G mobile communication technology, in order to support services and meet the performance requirements related to enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC) and massive Machine-Type Communications (mMTC), standardization is underway on the following items: beamforming and massive multiple-input multiple-output (MIMO) for alleviating radio wave path loss and increasing radio wave transmission distance in millimeter waves; basic parameter sets (e.g., operating multiple subcarrier spacings) for efficient utilization of millimeter wave resources and dynamic operation of time slot formats; initial access technology for supporting multi-beam transmission and broadband; definition and operation of BWP (BandWidth Part); new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and polarization codes for highly reliable transmission of control information; L2 preprocessing; and network slicing for providing dedicated networks customized for specific services.

[0004] Currently, in view of the services that 5G mobile communication technology will support, discussions are underway on improvements and performance enhancements of initial 5G mobile communication technology, and there is already physical layer standardization on technologies such as: Vehicle-to-everything (V2X), for assisting driving determination of autonomous vehicles based on information about the location and status of the vehicle sent by the vehicle, and for enhancing user convenience; New Radio Unlicensed (NR-U), for system operation that complies with various regulatory requirements in unlicensed bands; NR UE energy saving; Non-Terrestrial Network (NTN), which is UE-satellite direct communication for ensuring coverage in areas where communication with terrestrial networks is unavailable; and positioning.

[0005] In addition, in the field of wireless interface architecture / protocol, standardization is already underway on technologies such as: Industrial Internet of Things (IIoT), which is used to support new services through intercommunication and integration with other industries; IAB (Integrated Access and Backhaul), which is used to provide nodes for network service area expansion by supporting wireless backhaul links and access links in an integrated manner; Mobility enhancement, including conditional handover and DAPS (Dual Active Protocol Stack) handover; and two-step random access, which is used to simplify the random access procedure (2-step RACH (random access channel) for NR). In the field of system architecture / service, standardization is also underway on the following: 5G baseline architecture (e.g., service-based architecture or service-based interface), which is used to combine network function virtualization (NFV) and software-defined networking (SDN) technologies; and Mobile Edge Computing (MEC), which is used to receive services based on UE location.

[0006] If such 5G mobile communication systems are commercialized, the already exponentially increasing number of connected devices will be connected to the communication network, and accordingly, it is expected that enhanced functions and performance of the 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research related to the following items is planned: extended reality (eXtended Reality, XR) (XR = AR (Augmented Reality) + VR (Virtual Reality) + MR (Mixed Reality)) for efficient support of augmented reality, virtual reality, etc.; improving 5G performance and reducing complexity by utilizing 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 not only as a basis for developing new waveforms for ensuring coverage of the terahertz band for 6G mobile communication technology, full Dimensional MIMO (FD-MIMO), multi-antenna transmission technology (such as array antennas and massive antennas), metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional spatial multiplexing technology using orbital angular momentum (OAM), and reconfigurable intelligent surfaces (RIS), but also as a basis for developing full-duplex technology for improving the frequency efficiency of 6G mobile communication technology and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (artificial intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services with a level of complexity that exceeds the limits of UE operating capabilities by utilizing ultra-high performance communication and computing resources. Summary of the invention

[0008] Technical issues

[0009] Various embodiments of the present disclosure will provide an apparatus and method that enables efficient provision of services in a mobile communication system. Various embodiments of the present disclosure will provide a method for simultaneously transmitting multiple uplink channels by using multiple panels in a wireless communication system and an apparatus for performing the method.

[0010] Solution

[0011] In order to solve the above problems, an embodiment of the present disclosure provides a method performed by a terminal in a wireless communication system, the method comprising: sending terminal capability information including information related to simultaneous transmission with multi-panel (STxMP) to a base station; receiving a high-layer signal from the base station; identifying whether the high-layer signal includes parameters for supporting STxMP; in the case where the high-layer signal includes parameters for supporting STxMP, identifying support for STxMP based on multiple downlink control information (DCI); receiving first downlink control information (DCI) and a second DCI from the base station, the first DCI being used to schedule a first physical uplink shared channel (PUSCH) from a first control resource set (CORESET) pool index configured as 0, and the second DCI being used to schedule a second PUSCH from a second CORESET pool index configured as 1; and performing a first PUSCH transmission and a second PUSCH transmission overlapping at least in the time domain based on STxMP.

[0012] In addition, an embodiment of the present disclosure provides a method performed by a base station in a wireless communication system, the method comprising: receiving terminal capability information including information related to multi-panel simultaneous transmission (STxMP) from a terminal; generating a high-layer signal including parameters for supporting STxMP based on the terminal capability information; sending the high-layer signal to the terminal; determining support for STxMP based on multiple downlink control information (DCI); sending first downlink control information (DCI) and a second DCI to the terminal, the first DCI being used to schedule a first physical uplink shared channel (PUSCH) from a first control resource set (CORESET) pool index configured as 0, and the second DCI being used to schedule a second PUSCH from a second CORESET pool index configured as 1; and performing a first PUSCH transmission and a second PUSCH reception that overlap at least in the time domain based on STxMP.

[0013] In addition, an embodiment of the present disclosure provides a terminal of a wireless communication system, which includes a transceiver and a controller, wherein the controller is configured to perform control to: send terminal capability information including information related to multi-panel simultaneous transmission (STxMP) to a base station; receive a high-layer signal from the base station; identify whether the high-layer signal includes parameters for supporting STxMP; in the case where the high-layer signal includes parameters for supporting STxMP, identify support for STxMP based on multiple downlink control information (DCI); receive first downlink control information (DCI) and a second DCI from the base station, the first DCI being used to schedule a first physical uplink shared channel (PUSCH) from a first control resource set (CORESET) pool index configured as 0, and the second DCI being used to schedule a second PUSCH from a second CORESET pool index configured as 1; and perform a first PUSCH transmission and a second PUSCH transmission that overlap at least in the time domain based on STxMP.

[0014] In addition, an embodiment of the present disclosure provides a base station in a wireless communication system, the base station including a transceiver and a controller, wherein the controller is configured to perform control to: receive terminal capability information including information related to multi-panel simultaneous transmission (STxMP) from a terminal; generate a high-layer signal including parameters for supporting STxMP based on the terminal capability information; send the high-layer signal to a UE; determine support for STxMP based on multiple downlink control information (DCI); send first downlink control information (DCI) and a second DCI to the terminal, the first DCI being used to schedule a first physical uplink shared channel (PUSCH) from a first control resource set (CORESET) pool index configured as 0, and the second DCI being used to schedule a second PUSCH from a second CORESET pool index configured as 1; and perform a first PUSCH transmission and a second PUSCH reception overlapping at least in the time domain based on STxMP.

[0015] Beneficial Effects

[0016] According to various embodiments of the present disclosure, an apparatus and method enabling efficient provision of services in a mobile communication system may be provided.

[0017] According to various embodiments of the present disclosure, 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 may be provided. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 The basic structure of the time-frequency domain in the wireless communication system according to an embodiment of the present disclosure is shown.

[0019] Figure 2 The structure of a frame, a subframe, and a time slot in a wireless communication system according to an embodiment of the present disclosure is shown.

[0020] Figure 3 An example of bandwidth portion configuration in a wireless communication system according to an embodiment of the present disclosure is shown.

[0021] Figure 4 An example of a control resource set configuration of a downlink control channel in a wireless communication system is shown.

[0022] Figure 5a The structure of a downlink control channel in a wireless communication system according to an embodiment of the present disclosure is shown.

[0023] Figure 5b The situation in which a UE may have multiple physical downlink control channel (PDCCH) monitoring opportunities within a time slot in a wireless communication system according to an embodiment of the present disclosure is shown in terms of span.

[0024] Figure 6 An example of a discontinuous reception (DRX) operation in a wireless communication system according to an embodiment of the present disclosure is shown.

[0025] Figure 7 An example of base station beam allocation configured according to a transmission configuration indicator (TCI) state in a wireless communication system according to an embodiment of the present disclosure is shown.

[0026] Figure 8 An example of a method for allocating TCI states to a PDCCH in a wireless communication system according to an embodiment of the present disclosure is shown.

[0027] Fig. 9 A TCI indication medium access control (MAC) control element (CE) signaling structure for a PDCCH demodulation reference signal (DMRS) in a wireless communication system according to an embodiment of the present disclosure is shown.

[0028] Fig.10 An example of beam configuration for a control resource set and a search space in a wireless communication system according to an embodiment of the present disclosure is shown.

[0029] Fig.11 A method for a base station and a UE in a wireless communication system according to an embodiment of the present disclosure to transmit / receive data in consideration of a downlink data channel and rate matching resources is shown.

[0030] Fig.12 A method for a UE in a wireless communication system according to an embodiment of the present disclosure to select a receivable control resource set in consideration of a priority when receiving a downlink control channel is shown.

[0031] Fig.13 An example of frequency domain resource allocation for PDSCH in a wireless communication system according to an embodiment of the present disclosure is shown.

[0032] Fig.14 An example of time domain resource allocation for PDSCH in a wireless communication system according to an embodiment of the present disclosure is shown.

[0033] Fig.15 The process for beam configuration and activation for PDSCH is shown.

[0034] Fig.16 is a diagram showing an example of a MAC CE for activating a spatial relationship based on a physical uplink control channel (PUCCH) resource group in a wireless communication system according to an embodiment of the present disclosure;

[0035] Fig.17 An example of physical uplink shared channel (PUSCH) repetition transmission type B in a wireless communication system according to an embodiment of the present disclosure is shown.

[0036] Fig.18 The radio protocol structures of a base station and a UE in a wireless communication system according to an embodiment of the present disclosure in single cell, carrier aggregation and dual connectivity scenarios are shown.

[0037] Fig.19 is a diagram showing an example of antenna port configuration and resource allocation for cooperative communication in a wireless communication system according to an embodiment of the present disclosure;

[0038] Fig. 20 is a diagram showing a configuration example of downlink control information (DCI) for cooperative communication in a wireless communication system according to an embodiment of the present disclosure;

[0039] Fig.21 is a diagram showing an enhanced PDSCH TCI state activation / deactivation MAC-CE structure;

[0040] Fig. 22 is a diagram illustrating a radio link monitoring (RLM) reference signal (RS) selection process according to an embodiment of the present disclosure;

[0041] Fig.23 is a diagram showing a MAC-CE structure for joint TCI state activation and indication in a wireless communication system according to an embodiment of the present disclosure;

[0042] Fig.24is a diagram showing another MAC-CE structure for joint TCI state activation and indication in a wireless communication system according to an embodiment of the present disclosure;

[0043] Fig.25 is a diagram showing another MAC-CE structure for joint TCI state activation and indication in a wireless communication system according to an embodiment of the present disclosure;

[0044] Fig.26 is a diagram showing a MAC-CE structure for separating TCI state activation and indication in a wireless communication system according to an embodiment of the present disclosure;

[0045] Fig. 27 is a diagram showing another MAC-CE structure for separating TCI state activation and indication in a wireless communication system according to an embodiment of the present disclosure;

[0046] Fig.28 is a diagram showing another MAC-CE structure for separating TCI state activation and indication in a wireless communication system according to an embodiment of the present disclosure;

[0047] Fig.29 is a diagram showing another MAC-CE structure for separating TCI state activation and indication in a wireless communication system according to an embodiment of the present disclosure;

[0048] Fig.30 is a diagram showing a MAC-CE structure for joint TCI state activation and indication and separate TCI state activation and indication in a wireless communication system according to an embodiment of the present disclosure;

[0049] Fig.31 is a diagram showing another MAC-CE structure for joint TCI state activation and indication and separate TCI state activation and indication in a wireless communication system according to an embodiment of the present disclosure;

[0050] Fig.32 is a diagram showing beam application time that can be considered when a unified TCI scheme is used in a wireless communication system according to an embodiment of the present disclosure;

[0051] Fig.33 is a diagram showing a MAC-CE structure for activating and indicating multiple joint TCI states in a wireless communication system according to an embodiment of the present disclosure;

[0052] Fig.34 is a diagram showing a MAC-CE structure for activating and indicating multiple separated TCI states in a wireless communication system according to an embodiment of the present disclosure;

[0053] Fig.35is a diagram showing another MAC-CE structure for activating and indicating multiple separated TCI states in a wireless communication system according to an embodiment of the present disclosure;

[0054] Fig.36 An example of scheduling PUSCHs transmitted simultaneously in uplink via respective panels by using multiple DCIs is shown;

[0055] Fig.37 An operation flow chart of a terminal supporting STxMP based on mDCI is shown;

[0056] Fig.38 A flowchart showing the operation of a base station for supporting STxMP based on mDCI;

[0057] Fig.39 The structure of a UE in a wireless communication system according to an embodiment of the present disclosure is shown.

[0058] Fig.40 The structure of a base station in a wireless communication system according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

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

[0060] When describing the embodiments, descriptions related to well-known technical contents in the relevant field and not directly related to the present disclosure will be omitted. Such omission of unnecessary descriptions is intended to prevent the main idea of ​​the present disclosure from being obscured and to convey the main idea more clearly.

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

[0062] 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 ways to achieve them will become apparent. 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 provided only to fully disclose the present disclosure and inform those skilled in the art of the scope of the present disclosure, and the present disclosure is limited only by the scope of the appended claims. Throughout the specification, the same or similar reference numerals indicate the same or similar elements. In addition, when describing the present disclosure, when it is determined that a detailed description of a known function or configuration incorporated herein may make the subject matter of the present disclosure unnecessarily unclear, the description will be omitted. The terms to be described below are terms defined in the context of the functions in the present disclosure, and may be different according to the user, the user's intention or custom. Therefore, the definition of the term should be based on the content in the entire specification.

[0063] Here, it will be understood that each frame of the flowchart diagram and the frame combination in the flowchart diagram can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device create a component for implementing the function specified in one or more flowchart frames. These computer program instructions can also be stored in a computer-usable or computer-readable memory, where the computer-usable or computer-readable memory can instruct the computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-usable or computer-readable memory produce an article of instruction components including the functions specified in one or more flowchart frames. The 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 a computer or other programmable device, thereby generating a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more flowchart frames.

[0064] In addition, each box in the flowchart diagram may represent a module, a code fragment or a code portion, wherein the module, the code fragment or the code portion includes one or more executable instructions for implementing (a plurality of) specified logical functions. It should also be noted that in some alternative implementations, the functions mentioned in the box may not occur in order. For example, two boxes shown in succession may actually be performed substantially simultaneously, or these boxes may sometimes be performed in reverse order, depending on the functions involved.

[0065] As used in the embodiments of the present disclosure, "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, "unit" does not always have a meaning limited to software or hardware. "Unit" can be constructed to be stored in an addressable storage medium or to execute one or more processors. Therefore, "unit" includes, for example, software elements, object-oriented software elements, class elements or task elements, processes, functions, attributes, programs, subroutines, program code segments, drivers, firmware, microcodes, circuits, data, databases, data structures, tables, arrays, and parameters. The elements and functions provided by "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 as reproducing one or more CPUs (central processing units, central processing units) in a device or a secure multimedia card. In addition, the "unit" in the embodiment can include one or more processors.

[0066] Wireless communication systems are evolving toward broadband wireless communication systems to provide high-speed, high-quality packet data services using communication standards such as 3GPP's high-speed packet access (HSPA), LTE (long-term evolution (LTE) or evolved universal terrestrial radio access (E-UTRA)), Advanced LTE (LTE-Advanced, LTE-A), LTE-Pro, 3GPP2's high-rate packet data (HRPD), ultra-mobile broadband (UMB), IEEE 802.16e, and typical voice-based services.

[0067] As a typical example of a broadband wireless communication system, the LTE system adopts an orthogonal frequency division multiplexing (OFDM) scheme in the downlink (DL) and a single carrier frequency division multiple access (SC-FDMA) scheme in the uplink (UL). The uplink refers to the radio link through which a user equipment (UE) or a mobile station (MS) sends data or a control signal to a base station (BS) or an eNode B, and the downlink refers to the radio link through 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 to each user so as to avoid overlapping with each other, that is, so as to establish orthogonality.

[0068] 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 enhanced mobile broadband (eMBB) communication, massive machine type communication (mMTC), ultra-reliable low latency communication (URLLC), etc.

[0069] eMBB is designed to provide higher data rates than those supported by existing LTE, LTE-A or LTE-Pro. For example, in a 5G communication system, for a single base station, eMBB must provide a peak data rate of 20Gbps in the downlink and a peak data rate of 10Gbps in the uplink. In addition, the 5G communication system must provide an increased user-perceived data rate as well as a maximum data rate to the UE. In order to meet this requirement, it is necessary to improve the transmission / reception technology, including further enhanced multiple-input multiple-output (MIMO) transmission technology. In addition, a frequency bandwidth of more than 20MHz can be used in a frequency band of 3 to 6GHz or 6GHz or higher to obtain the data rate required by the 5G communication system, instead of using a transmission bandwidth of up to 20MHz to send signals in the 2GHz band used in LTE.

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

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

[0072] These three services in 5G (i.e., 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 services to meet the different requirements of each service. Of course, 5G is not limited to the above three services.

[0073] 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 base station (BS), a wireless access unit, a base station controller, and a node on a network. The terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smart phone, a computer, or a multimedia system capable of performing a communication function. In the present disclosure, "downlink (DL)" refers to a radio link via which a base station sends a signal to a terminal, and "uplink (UL)" refers to a radio link via which a terminal sends a signal to a base station. In addition, in the following description, an LTE or LTE-A system may be described by way of example, but the embodiments of the present disclosure may also be applied to other communication systems with similar technical backgrounds or channel types. Examples of such communication systems may include the fifth generation mobile communication technology (5G, new radio, and NR) developed outside of LTE-A, and in the following description, "5G" may be a concept covering existing LTE, LTE-A, and other similar services. In addition, based on the determination of those skilled in the art, the present disclosure may also be applied to other communication systems with some modifications without significantly departing from the scope of the present disclosure.

[0074] [NR time-frequency resources]

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

[0076] Figure 1 The basic structure of the time-frequency domain as a radio resource domain for transmitting data or control channels in the 5G system is shown.

[0077] exist Figure 1 In the diagram, 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, which can be defined as an orthogonal frequency division multiplexing (OFDM) symbol 102 on the time axis and a subcarrier 103 on the frequency axis. In the frequency domain, (For example, 12) consecutive REs may constitute one resource block (RB) 104. In the time domain, one subframe 110 may include a plurality of OFDM symbols 102. For example, the length of one subframe may be 1 ms.

[0078] Figure 2 The structure of a frame, a subframe, and a time slot in a wireless communication system according to an embodiment of the present disclosure is shown.

[0079] Figure 2An example of the structure of a frame 200, a subframe 201, and a time slot 202 is shown in FIG. One frame 200 may be defined as 10 ms. One subframe 201 may be defined as 1 ms, so one frame 200 may include a total of 10 frames 201. One time slot 202 or 203 may be defined as 14 OFDM symbols (i.e., the number of symbols per time slot is 14 OFDM symbols). ). A subframe 201 may include one or more time slots 202 and 203, and the number of time slots 202 and 203 of each subframe 201 may vary depending on the configured value μ of the subcarrier spacing 204 or 205. Figure 2 The example in FIG. 2 shows a case where the subcarrier spacing configuration value μ=0 (204) and a case where μ=1 (205). In the case where μ=0 (204), one subframe 201 may include one time slot 202, and in the case where μ=1 (205), one subframe 201 may include two time slots 203. That is, the number of time slots in each subframe is The number of time slots per frame may vary depending on the subcarrier spacing configuration value μ. May be different accordingly. and It can be defined depending on each subcarrier spacing configuration μ in Table 1 below.

[0080] [Table 1]

[0081]

[0082] [Bandwidth Part (BWP)]

[0083] Next, a bandwidth part (BWP) configuration in a 5G communication system will be described in detail with reference to the accompanying drawings.

[0084] Figure 3 An example of bandwidth portion configuration in a wireless communication system according to an embodiment of the present disclosure is shown.

[0085] Figure 3 An example is shown in which the UE bandwidth 300 is configured to include two bandwidth parts, namely, bandwidth part #1 (BWP#1) 301 and bandwidth part #2 (BWP#2) 302. The base station may configure one or more bandwidth parts for the UE, and may configure the following multiple pieces of information for each bandwidth part, as given in Table 2 below.

[0086] [Table 2]

[0087]

[0088] Of course, the above examples are not restrictive, and in addition to the configuration information given above, various parameters related to the bandwidth part may be configured for the UE. The base station may transmit the configuration information to the UE via upper layer signaling (e.g., radio resource control (RRC) signaling). At least one bandwidth part among one or more configured bandwidth parts may be activated. Whether the configured bandwidth part is activated may be transmitted semi-statically via RRC signaling or dynamically via downlink control information (DCI) from the base station to the UE.

[0089] According to one embodiment, before a radio resource control (RRC) connection, a base station may configure an initial bandwidth part (BWP) for an initial access for a UE through a master information block (MIB). More specifically, the UE may receive configuration information about a control resource set (CORESET) and a search space of a PDCCH that may be used to send a PDCCH for receiving system information (which may correspond to remaining system information (RMSI) or system information block 1 (SIB1) necessary for initial access through the MIB in an initial access step). Both the control resource set and the search space configured through the MIB may be considered as an identification (ID) 0. The base station may notify the UE of configuration information about control region #0, such as frequency allocation information, time allocation information, and a basic parameter set, through the MIB. In addition, the base station may notify the UE of configuration information about a monitoring period and timing for control resource set #0, i.e., configuration information about search space #0, through the MIB. The UE may consider the frequency domain configured by the control resource set #0 obtained from the MIB to be the initial bandwidth part for initial access. The ID of the initial bandwidth part may be considered to be 0.

[0090] The bandwidth-portion-dependent configurations supported by 5G can be used for various purposes.

[0091] According to some embodiments, if the bandwidth supported by the UE is less than the system bandwidth, this can be supported by bandwidth part configuration. For example, the base station can configure the frequency position of the bandwidth part for the UE (configuration information 2) so that the UE can send / receive data at a specific frequency position within the system bandwidth.

[0092] In addition, according to some embodiments, in order to support different basic parameter sets, the base station can configure multiple bandwidth parts for the UE. For example, in order to support data transmission / reception of the UE using both a subcarrier spacing of 15kHz and a subcarrier spacing of 30kHz, two bandwidth parts can be configured as subcarrier spacings of 15kHz and 30kHz, respectively. Different bandwidth parts can be subjected to frequency division multiplexing (FDM), and if data is to be sent / received at a specific subcarrier spacing, the bandwidth part configured as the corresponding subcarrier spacing can be activated.

[0093] In addition, according to some embodiments, in order to reduce the power consumed by the UE, the base station can configure bandwidth parts with different bandwidth sizes for the UE. For example, if the UE supports a relatively large bandwidth (e.g., 100 MHz) and always sends / receives data with the corresponding bandwidth, a considerable amount of power consumption may occur. In particular, from the perspective of power consumption, it may be quite inefficient to unnecessarily monitor the downlink control channel using a large bandwidth of 100 MHz in the absence of traffic. In order to reduce the power consumed by the UE, the base station can configure a bandwidth part with a relatively small bandwidth (e.g., a bandwidth part of 20 MHz) for the UE. In the absence of traffic, the UE can perform monitoring operations in the 20 MHz bandwidth part, and if data has occurred, it can send / receive data using the 100 MHz bandwidth part as instructed by the base station.

[0094] In conjunction with the bandwidth part configuration method, before the RRC connection, the UE may receive configuration information about the initial bandwidth part through the MIB in the initial access step. More specifically, the UE may have a control resource set (CORESET) configured for a downlink control channel that can be used to send downlink control information (DCI) for scheduling system information blocks (SIBs) from the MIB of the physical broadcast channel (PBCH). The bandwidth of the control resource set configured through the MIB can be considered as the initial bandwidth part, and the UE can receive the physical downlink shared channel (PDSCH) through which the SIB is sent through the configured initial bandwidth part. The initial bandwidth part can be used not only for the purpose of receiving SIBs, but also for other system information (OSI), paging, random access, etc.

[0095] [Bandwidth Part (BWP) Change]

[0096] If the UE has one or more bandwidth parts configured for it, the base station may indicate to the UE to change (or switch or convert) the bandwidth part by using the bandwidth part indicator field in the DCI. As an example, if the UE's currently activated bandwidth part is Figure 3 If the bandwidth part #1 301 in the DCI is received, the base station can use the bandwidth part indicator in the DCI to indicate the bandwidth part #2 302, and the UE can change the bandwidth part to the bandwidth part #2 302 indicated by the bandwidth part indicator in the received DCI.

[0097] As described above, the DCI-based bandwidth part change can be indicated by the DCI for scheduling PDSCH or PUSCH, so when receiving the bandwidth part change request, the UE needs to be able to receive or send the PDSCH or PUSCH scheduled by the corresponding DCI in the changed bandwidth part without any problem. To this end, the delay time (T BWP ) are specified in the standard and can be defined as given in, for example, Table 3 below.

[0098] [Table 3]

[0099]

[0100] Depending on the capability of the UE, the requirement for the bandwidth fraction change delay time supports type 1 or type 2. The UE may report the supportable bandwidth fraction change delay time type to the base station.

[0101] If the UE has received the DCI including the bandwidth part change indicator in time slot n, then according to the above requirements on the bandwidth part change delay time, the UE may BWP The change to the new bandwidth part indicated by the bandwidth part change indicator is completed at a time point of 1000, and the data channel scheduled by the corresponding DCI can be sent / received in the newly changed bandwidth part. According to one embodiment, if the base station wants to schedule the data channel by using the new bandwidth part, the base station can change the bandwidth part delay time (T BWP ) determines the time domain resource allocation for the data channel. That is, when scheduling the data channel by using the new bandwidth part, in combination with the method for determining the time domain resource allocation for the data channel, the base station may schedule the corresponding data channel after the bandwidth part change delay time. Accordingly, the UE may not expect that the DCI indicating the bandwidth part change will indicate a delay time less than the bandwidth part change delay time (T BWP )’s time slot offset (K0 or K2) value.

[0102] If the UE has received a DCI indicating a bandwidth partial change (e.g., DCI format 1_1 or 0_1), the UE may not perform transmission or reception during a time interval from the third symbol of the slot for receiving the PDCCH including the corresponding DCI to the slot start point indicated by the slot offset (K0 or K2) value indicated by the time domain resource allocation indicator field in the corresponding DCI. For example, if the UE has received a DCI indicating a bandwidth partial change in slot n, and if the slot offset value indicated by the corresponding DCI is K, the UE may not perform transmission or reception from the third symbol of slot n to the symbol before slot n+K (e.g., the last symbol of slot n+K-1).

[0103] [SS / PBCH block]

[0104] Next, the synchronization signal (SS) / PBCH block in 5G will be described.

[0105] The SS / PBCH block may refer to a physical layer channel block including a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a PBCH. The details are as follows.

[0106] -PSS: A signal that becomes a reference for downlink time / frequency synchronization and provides partial information of a cell ID.

[0107] -SSS: Becomes a reference for downlink time / frequency synchronization and provides the remaining cell ID information not provided by the PSS. In addition, the SSS can be used as a reference signal for PBCH demodulation of the PBCH.

[0108] -PBCH: Provides necessary system information necessary for data channel and control channel transmission / reception of UE. The necessary system information may include search space related control information indicating radio resource mapping information of control channel, scheduling control information about a separate data channel for transmitting system information, etc.

[0109] -SS / PBCH block: An SS / PBCH block includes a combination of PSS, SSS, and PBCH. One or more SS / PBCH blocks may be transmitted within a period of 5 ms, and each transmitted SS / PBCH block may be distinguished by an index.

[0110] The UE can detect the PSS and SSS in the initial access phase and can decode the PBCH. The UE can obtain the MIB from the PBCH, and this can be used to configure the control resource set (CORESET) #0 (which can correspond to the control resource set with a control resource set index of 0). The UE can monitor the control resource set #0 by assuming that the demodulation reference signal (DMRS) sent in the selected SS / PBCH block and the control resource set #0 are quasi-co-located (QCL). The UE can receive system information with downlink control information sent in the control resource set #0. The UE can obtain configuration information related to the random access channel (RACH) necessary for initial access from the received system information. The UE can send a physical RACH (PRACH) to the base station in consideration of the selected SS / PBCH index, and the base station can obtain information about the SS / PBCH block index selected by the UE when receiving the PRACH. The base station can know which block the UE has selected from the various SS / PBCH blocks and the fact that the control resource set #0 associated therewith is monitored.

[0111] [PDCCH: About DCI]

[0112] Next, downlink control information (DCI) in the 5G system will be described in detail.

[0113] In the 5G system, scheduling information about uplink data (or physical uplink shared channel (PUSCH)) or downlink data (or physical downlink shared channel (PDSCH)) is included in the DCI and delivered from the base station to the UE through the DCI. For PUSCH or PDSCH, the UE can monitor the fallback DCI format and the non-fallback DCI format. The fallback DCI format may include a fixed field predefined between the base station and the UE, and the non-fallback DCI format may include a configurable field.

[0114] The DCI may undergo a channel coding and modulation process and then be sent through a physical downlink control channel (PDCCH) or on the PDCCH. A payload cyclic redundancy check (CRC) may be attached to the DCI message, and the CRC may be scrambled by a radio network temporary identifier (RNTI) corresponding to the identity of the UE. Different RNTIs may be used according to the purpose of the DCI message (e.g., UE-specific data transmission, power control commands, or random access responses). That is, the RNTI may not be sent explicitly, but may be sent while being included in the CRC calculation process. Upon receiving a DCI message sent via the PDCCH, the UE may identify the CRC by using the allocated RNTI, and if the CRC identification result is correct, the UE may know that the corresponding message has been sent to the UE.

[0115] For example, the DCI for scheduling PDSCH regarding system information (SI) may be scrambled by SI-RNTI. The DCI for scheduling PDSCH regarding random access response (RAR) messages may be scrambled by RA-RNTI. The DCI for scheduling PDSCH regarding paging messages may be scrambled by P-RNTI. The DCI for notifying the slot format indicator (SFI) may be scrambled by SFI-RNTI. The DCI for notifying transmit power control (TPC) may be scrambled by TPC-RNTI. The DCI for scheduling UE-specific PDSCH or PUSCH may be scrambled by cell RNTI (C-RNTI).

[0116] DCI format 0_0 may be used as a fallback DCI for scheduling a PUSCH, and in this case, the CRC may be scrambled by the C-RNTI. For example, DCI format 0_0 in which the CRC is scrambled by the C-RNTI may include the following pieces of information.

[0117] [Table 4]

[0118]

[0119] DCI format 0_1 ​​may be used as a non-fallback DCI for scheduling a PUSCH, and in this case, the CRC may be scrambled by the C-RNTI. For example, DCI format 0_1 ​​in which the CRC is scrambled by the C-RNTI may include the following pieces of information.

[0120] [Table 5]

[0121]

[0122]

[0123] DCI format 1_0 may be used as a fallback DCI for scheduling a PDSCH, and in this case, the CRC may be scrambled by the C-RNTI. For example, DCI format 1_0 in which the CRC is scrambled by the C-RNTI may include the following pieces of information.

[0124] [Table 6]

[0125]

[0126]

[0127] DCI format 1_1 may be used as a non-fallback DCI for scheduling a PDSCH, and in this case, the CRC may be scrambled by the C-RNTI. For example, DCI format 1_1 in which the CRC is scrambled by the C-RNTI may include the following pieces of information.

[0128] [Table 7]

[0129]

[0130]

[0131] [PDCCH: CORESET, REG, CCE and search space]

[0132] Hereinafter, a downlink control channel in a 5G communication system will be described in more detail with reference to the accompanying drawings.

[0133] Figure 4 An example of a control resource set (CORESET) for transmitting a downlink control channel in a 5G wireless communication system is shown.

[0134] Figure 4An example is shown in which a UE bandwidth portion 410 is configured along the frequency axis and two CORESETs (CORESET#1 401 and CORESET#2 402) are configured along the time axis within one time slot 420. CORESETs 401 and 402 may be configured in specific frequency resources 403 within the entire UE bandwidth portion 410 along the frequency axis. One or more OFDM symbols may be configured along the time axis, and this may be defined as a control resource set duration 404. Figure 4 In the example shown, CORESET#1 401 is configured to have a control resource set duration corresponding to two symbols, and CORESET#2 402 is configured to have a control resource set duration corresponding to one symbol.

[0135] The control resource set in the above 5G can be configured for the UE by the base station through upper layer signaling (e.g., system information, master information block (MIB), radio resource control (RRC) signaling). The description of configuring the control resource set for the UE means providing information such as the control resource set identifier, the frequency position of the control resource set, and the symbol duration of the control resource set. For example, the information may include multiple pieces of information given below.

[0136] [Table 8]

[0137]

[0138]

[0139] In Table 8, the tci-StatesPDCCH (referred to as transmission configuration indication (TCI) state) configuration information may include information of one or more SS / PBCH block indices or channel state information reference signal (CSI-RS) indices that are quasi co-located (QCL) with the DMRS transmitted in the corresponding CORESET.

[0140] Figure 5a An example of a basic unit of time-frequency resources constituting a downlink control channel available in a 5G system is shown.

[0141] according to Figure 5a , the basic unit of time-frequency resources constituting the control channel may be referred to as a resource element group (REG) 503, and the REG 503 may be defined by an OFDM symbol 501 along the time axis and a physical resource block (PRB) 502 (i.e., 12 subcarriers) along the frequency axis. The base station may configure the downlink control channel allocation unit by cascading the REG 503.

[0142] Assume that the basic unit of downlink control channel allocation in 5G is as follows Figure 5aAs shown in FIG. 5 , a control channel element (CCE) 504 may include multiple REGs 503. For example, to describe Figure 5a As shown in the REG 503, REG 503 may include 12 REs, and if a CCE 504 includes 6 REGs 503, then a CCE 504 may include 72 REs. Once configured, a downlink control resource set may include multiple CCEs 504, and a specific downlink control channel may be mapped to one or more CCEs 504 and then transmitted according to an aggregation level (AL) in the control resource set. The CCEs 504 in the control resource set are distinguished by numbers, and the numbers of the CCEs 504 may be allocated according to a logical mapping scheme.

[0143] Figure 5a The basic unit of the downlink control channel (ie, REG 503) shown in FIG. 5 may include both the RE to which the DCI is mapped and the area to which the reference signal (DMRS 505) for decoding the RE is mapped. Figure 5a As shown, three DRMS ​​505 can be sent within one REG 503. Depending on the aggregation level (AL), the number of CCEs necessary to send the PDCCH can be 1, 2, 4, 8, or 16, and different numbers of CCEs can be used to implement link adaptation of the downlink control channel. For example, in the case of AL=L, one downlink control channel can be sent by L CCEs. The UE needs to detect the signal while having no information about the downlink control channel, so a search space indicating a set of CCEs has been defined for blind decoding. The search space is a set of downlink control channel candidates including CCEs that the UE needs to attempt to decode at a given AL, and since 1, 2, 4, 8, or 16 CCEs can be bundled in various ALs, the UE can have multiple search spaces. A search space set can be defined as a set of search spaces at all configured aggregation levels.

[0144] Search spaces can be classified into common search spaces and UE-specific search spaces. A group of UEs or all UEs can search the common search space of the PDCCH in order to receive cell common control information, such as dynamic scheduling of system information or paging messages. For example, PDSCH scheduling allocation information for sending SIBs including cell operator information, etc. can be received by searching the common search space of the PDCCH. In the case of a common search space, a group of UEs or all UEs need to receive the PDCCH, so the PDCCH can be defined as a predetermined CCE set. Scheduling allocation information about UE-specific PDSCH or PUSCH can be received by searching the UE-specific search space of the PDCCH. The UE-specific search space can be specifically defined by the UE as a function of various system parameters and UE identification.

[0145] In 5G, the parameters of the search space for PDCCH can be configured for the UE by the base station through upper layer signaling (e.g., SIB, MIB or RRC signaling). For example, the base station can provide the UE with configurations such as the number of PDCCH candidates under each aggregation level L, the monitoring period of the search space, the monitoring timing of each symbol in the time slot for the search space, the search space type (common search space or UE-specific search space), the combination of RNTI and DCI format to be monitored in the corresponding search space, and the control resource set index for monitoring the search space. For example, the control resource set may include the following multiple pieces of information given in Table 8 below.

[0146] [Table 9]

[0147]

[0148]

[0149]

[0150] According to the configuration information, the base station may configure one or more search space sets for the UE. According to some embodiments, the base station may configure search space set 1 and search space set 2 for the UE, may configure DCI format A scrambled by X-RNTI to be monitored in the common search space in search space set 1, and may configure DCI format B scrambled by Y-RNTI to be monitored in the UE-specific search space in search space set 2.

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

[0152] The combinations of DCI formats and RNTIs given below may be monitored in the common search space. Obviously, the examples given below are not limiting.

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

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

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

[0156] -DCI format 2_2 with CRC scrambled by TPC-PUSCH-RNTI, TPC-PUCCH-RNTI

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

[0158] The combinations of DCI formats and RNTIs given below may be monitored in the UE-specific search space. Obviously, the examples given below are not limiting.

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

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

[0161] The enumerated RNTIs may follow the definitions and usages given below.

[0162] -Cell RNTI (C-RNTI): used to schedule UE-specific PDSCH

[0163] -Temporary cell RNTI (TC-RNTI): used to schedule UE-specific PDSCH

[0164] -Configuration Scheduling RNTI (CS-RNTI): used to schedule a semi-statically configured UE-specific PDSCH

[0165] - Random Access RNTI (RA-RNTI): used to schedule PDSCH in the random access procedure

[0166] - Paging RNTI (P-RNTI): used to schedule the PDSCH in which paging is sent

[0167] - System Information RNTI (SI-RNTI): used to schedule the PDSCH in which system information is sent

[0168] -Interrupt RNTI (INT-RNTI): used to indicate whether PDSCH is punctured

[0169] - Transmit Power Control for PUSCH RNTI (TPC-PUSCH-RNTI): used to indicate the power control command for PUSCH

[0170] - Transmit Power Control for PUCCH RNTI (TPC-PUCCH-RNTI): used to indicate the power control command for PUCCH

[0171] - Transmit Power Control for SRS RNTI (TPC-SRS-RNTI): used to indicate the power control command for SRS

[0172] The DCI formats enumerated above may follow the definitions given below.

[0173] [Table 10]

[0174]

[0175]

[0176] In 5G, the search space of aggregation level L with respect to CORESET p and search space set s can be expressed by the following Equation 1.

[0177] [Equation 1]

[0178]

[0179] -L: aggregation level

[0180] -n CI : Carrier index

[0181] -N CCE,p : Controls the total number of CCEs in resource set p

[0182] - Time slot index

[0183] - Number of PDCCH candidates at aggregation level L

[0184] - PDCCH candidate index at aggregation level L =

[0185] -i=0,…,L-1

[0186] - For mpod3 = 0, A p =39827, for pmod3 = 1, A p =39829, for mpod3 = 2, A p =39839, D=65537

[0187] -n RNTI :UE ID

[0188] In the case of a common search space, the value Can correspond to 0.

[0189] In case of UE-specific search space, the value It may correspond to a value changed by the UE identity (C-RNTI or ID configured by the base station for the UE) and the time index.

[0190] In 5G, multiple search space sets may be configured by different parameters (e.g., the parameters in Table 9), and a set of search space sets monitored by the UE at each time point may be different accordingly. For example, if search space set #1 is configured with a period of X time slots, if search space set #2 is configured with a period of Y time slots, and if X and Y are different, the UE may monitor both search space set #1 and search space set #2 in one specific time slot, and may monitor one of search space set #1 and search space set #2 in another specific time slot.

[0191] [PDCCH: span]

[0192] For the case where the UE has multiple PDCCH monitoring opportunities within a time slot, the UE can perform UE capability reporting at each subcarrier interval, and the concept "span" can be used for this. The span refers to the consecutive symbols configured within the time slot so that the UE can monitor the PDCCH, and each PDCCH monitoring opportunity is within a span. The span can be expressed by (X, Y), where X refers to the minimum number of symbols that separate the first symbols of two consecutive spans from each other, and Y refers to the number of consecutive symbols that can monitor the PDCCH within a span. Here, the UE can monitor the PDCCH within the range of Y symbols from the first symbol of the span within the span.

[0193] Figure 5b The span aspect shows that in a wireless communication system, a UE may have multiple PDCCH monitoring opportunities within a time slot.

[0194] The possible spans are (X,Y) = (7,3), (4,3), (2,2), and these three cases can be represented by Figure 5b, "5-1-00", "5-1-05", and "5-1-10" in the time slot. As an example, "5-1-00" may describe a situation where there are two spans described by (7,3) in the time slot. The interval between the first symbols of the two spans is described as X=7, the PDCCH monitoring opportunity may exist within a total of Y=3 symbols from the first symbol of each span, and search space 1 and search space 2 may exist within Y=3 symbols, respectively. As another example, "5-1-05" may describe a situation where there are a total of three spans described by (4,3) in the time slot and the second span and the third span are separated by X'=5 symbols which is greater than X=4.

[0195] [PDCCH: UE capability report]

[0196] The time slot positions where the above common search space and UE-specific search space are located are indicated by the parameter "monitoringSymbolsWithinSlot" in Table 11-1, and the symbol position within the time slot is indicated as a bitmap by the parameter "monitoringSymbolsWithinSlot" in Table 9. At the same time, the symbol position within the time slot at which the UE can monitor the search space can be reported to the base station through the following UE capabilities.

[0197] -UE capability 1 (hereinafter referred to as FG 3-1). UE capability 1 may have the following meanings: As shown in Table 11-1 below, if there is a monitoring occasion (MO) for type 1 and type 3 common search space or UE specific search space in a time slot, the UE is able to monitor the corresponding MO when the corresponding MO is located within the first three symbols in the time slot. This UE capability is a mandatory capability supported by all UEs that support NR, and whether this UE capability is supported is not explicitly reported to the base station.

[0198] [Table 11-1]

[0199]

[0200]

[0201]

[0202] -UE capability 2 (hereinafter referred to as FG 3-2). This UE capability has the following meaning: As shown in Table 11-2 below, if there is a monitoring opportunity (MO) for a common search space or a UE-specific search space in a time slot, the UE can monitor the corresponding MO regardless of the starting symbol position of the corresponding MO. This UE capability is optionally supported by the UE, and whether the UE capability is supported is explicitly reported to the base station.

[0203] [Table 11-2]

[0204]

[0205] -UE capability 3 (hereinafter referred to as FG 3-5, 3-5a or 3-5b). The UE capability has the following meaning: as shown in Table 11-3 below, if there are multiple monitoring opportunities (MO) regarding a common search space or a UE-specific search space within a time slot, the pattern of the MOs that the UE can monitor is indicated. The above pattern includes the spacing X between the starting symbols of different MOs and the maximum symbol length Y regarding an MO. The (X,Y) combinations supported by the UE can be one or more of {(2,2), (4,3), (7,3)}. The UE capability is optionally supported by the UE, and whether the UE capability is supported and the above (X,Y) combination are explicitly reported to the base station.

[0206] [Table 11-3]

[0207]

[0208]

[0209]

[0210]

[0211] The UE may report to the base station whether it supports the above UE capability 2 and / or UE capability 3 and related parameters. The base station may allocate time domain resources to the common search space and the UE specific search space based on the UE capability report. During resource allocation, the base station may ensure that the MO is not located in a position where the UE cannot monitor.

[0212] [PDCCH: BD / CCE restriction]

[0213] If there are multiple search space sets configured for the UE, the following conditions may be considered in conjunction with a method for determining a search space set to be monitored by the UE.

[0214] If the value of "monitoringCapabilityConfig-r16" (upper layer signaling) has been configured as "r15monitoringcapability" for the UE, the UE defines the maximum value of the number of PDCCH candidates that can be monitored and the number of CCEs constituting the entire search space (as used herein, the entire search space refers to the entire CCE set corresponding to the joint domain of multiple search space sets) for each time slot. If the value of "monitoringCapabilityConfig-r16" has been configured as "r16monitoringcapability", the UE defines the maximum value of the number of PDCCH candidates that can be monitored and the number of CCEs constituting the entire search space (as used herein, the entire search space refers to the entire CCE set corresponding to the joint domain of multiple search space sets) for each span.

[0215] [Condition 1: Maximum number of PDCCH candidates is limited]

[0216] According to the above upper layer signaling configuration value, if the reference is configured with 15·2 μ The maximum number of PDCCH candidates that a UE can monitor is defined by the time slot in the cell with a subcarrier spacing of kHz. μ , the following Table 12-1 can be followed, and if the reference span is used to define the maximum number of PDCCH candidates that the UE can monitor, M μ , you can follow Table 12-2 given below.

[0217] [Table 12-1]

[0218] μ <![CDATA[Maximum number of PDCCH candidates per serving cell per time slot (M μ )]]> 0 44 1 36 2 22 3 20

[0219] [Table 12-2]

[0220]

[0221] [Condition 2: Maximum number of CCEs is limited]

[0222] According to the above upper layer signaling configuration value, if the reference is configured with 15·2 μ The maximum number of CCEs C constituting the entire search space (as used herein, the entire search space refers to the entire set of CCEs corresponding to the joint domain of multiple search space sets) is defined by the time slots in the cell with a subcarrier spacing of kHz. μ , the following Table 12-3 can be followed, and if the reference span is used to define the maximum number of CCEs constituting the entire search space (as used herein, the entire search space refers to the entire set of CCEs corresponding to the joint domain of multiple search space sets) Cμ , you can follow Table 12-4 given below.

[0223] [Table 12-3]

[0224] μ <![CDATA[Maximum number of non-overlapping CCEs per slot per serving cell (C μ )]]> 0 56 1 56 2 48 3 32

[0225] [Table 12-4]

[0226]

[0227] For convenience of description, a situation where both the above conditions 1 and 2 are satisfied at a specific time point may be defined as “condition A.” Therefore, a description that condition A is not satisfied may mean that at least one of the above conditions 1 and 2 is not satisfied.

[0228] [PDCCH: Oversubscription]

[0229] According to the configuration of the search space set of the base station, it may happen that condition A is not satisfied at a specific time point. If condition A is not satisfied at a specific time point, the UE may select and monitor only some search space sets configured to satisfy condition A at the corresponding time point, and the base station may send a PDCCH to the selected search space set.

[0230] The method for selecting some search spaces from the set of search spaces of all configurations may follow the method given below.

[0231] If condition A regarding PDCCH is not met at a specific time point (time slot), the UE (or base station) may, among the search space sets existing at the corresponding time point, give priority to a search space set having a search space type configured as a common search space over a search space set configured as a UE-specific search space.

[0232] If all search space sets configured as common search spaces have been selected (that is, if condition A is satisfied even after all search spaces configured as common search spaces have been selected), the UE (or base station) may select a search space set configured as a UE-specific search space. If there are multiple search space sets configured as UE-specific search spaces, a search space set with a lower search space set index may have a higher priority. In consideration of priority, as long as condition A is satisfied, a UE-specific search space set may be selected.

[0233] [DRX]

[0234] Figure 6 Discontinuous reception (DRX) is shown.

[0235] DRX refers to the operation of a UE currently using a service to discontinuously receive data in an RRC connected state, where a radio link is configured between a base station and the UE. If DRX is applied, the UE may turn on a receiver at a specific time point in order to monitor a control channel, and if no data is received within a predetermined time period, the receiver may be turned off, thereby reducing the power consumed by the UE. The DRX operation may be controlled by a MAC layer device based on various parameters and timers.

[0236] See also Figure 6 , the active time 605 refers to the time when the UE wakes up and monitors the PDCCH in each DRX cycle. The active timer 605 can be defined as follows.

[0237] - drx-onDurationTimer or drx-InactivityTimer or drx-RetransmissionTimerDL or drx-RetransmissionTimerUL or ra-ContentionResolutionTimer is running; or

[0238] - a scheduling request is sent on the PUCCH and is pending; or

[0239] - After successfully receiving a random access response to a random access preamble that was not selected by the MAC entity among the contention-based random access preambles, a PDCCH indicating a new transmission of the C-RNTI addressed to the MAC entity has not been received

[0240] drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, ra-ContentionResolutionTimer, etc. are timers having values ​​configured by the base station and have a function of enabling the UE to monitor the PDCCH if a predetermined condition is satisfied.

[0241] drx-onDurationTimer 615 is a parameter for configuring the minimum time that the UE wakes up in the DRX cycle. drx-InactivityTimer 620 is a parameter for configuring the time that the UE additionally wakes up upon receiving (630) a PDCCH indicating a new uplink transmission or downlink transmission. drx-RetransmissionTimerDL is a parameter for configuring the maximum time that the UE wakes up in order to receive a downlink retransmission in a downlink HARQ process. drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL and drx-RetransmissionTimerUL can be configured as, for example, a time, a number of subframes, a number of time slots, etc. ra-ContentionResolutionTimer is a parameter for monitoring the PDCCH in the random access procedure.

[0242] The inactive time 610 refers to a time configured so that the PDCCH is not monitored during the DRX operation, or a time configured so that the PDCCH is not received, and the inactive time 610 can be obtained by subtracting the active timer 605 from the entire time for performing the DRX operation. If the UE does not monitor the PDCCH during the active time 605, the UE can enter a sleep or inactive state, thereby reducing power consumption.

[0243] The DRX cycle refers to the period during which the UE wakes up and monitors the PDCCH. That is, the DRX cycle refers to the time interval between when the UE monitors one PDCCH and when it monitors the next PDCCH, or the period during which the on-duration occurs. There are two types of DRX cycles: short DRX cycle and long DRX cycle. The short DRX cycle can be optionally applied.

[0244] The long DRX cycle 625 is a longer cycle among the two DRX cycles configured for the UE. While operating with long DRX, the UE restarts the drx-onDurationTimer 615 at a time point when the long DRX cycle 625 has passed from the starting point (e.g., the starting symbol) of the drx-onDurationTimer 615. If operating under the long DRX cycle 625, the UE may start the drx-onDurationTimer 615 in a time slot after the drx-SlotOffset in a subframe satisfying the following equation 2. Here, drx-SlotOffset refers to a delay before starting the drx-onDurationTimer 615. The drx-SlotOffset may be configured as, for example, a time, a number of time slots, etc.

[0245] [Equation 2]

[0246] [(SFN×10)+subframe number]modulo(drx-LongCycle)=drx-StartOffset

[0247] The drx-LongCycleStartOffset may be used to define the long DRX cycle 625, and the drx-StartOffset may be used to define the subframe for starting the long DRX cycle 625. The drx-LongCycleStartOffset may be configured as, for example, time, number of subframes, number of time slots, and the like.

[0248] [QCL, TCI status]

[0249] In a wireless communication system, one or more different antenna ports (which may be replaced by one or more channels, signals and combinations thereof, but for convenience in the following description of the present disclosure, will be referred to as different antenna ports as a whole) may be associated with each other through a quasi co-location (QCL) configuration as shown in Table 13 below. The TCI state is used to declare the QCL relationship between a PDCCH (or a PDCCH DRMS) and another RS ​​or channel, and the description of the QCL between a reference antenna port A (reference RS#A) and another target antenna port B (target RS#B) means allowing the UE to apply some or all of the large-scale channel parameters estimated in antenna port A to the channel measurement value from antenna port B. QCL needs to be associated with different parameters according to situations 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, or 4) beam management (BM) affected by spatial parameters. Accordingly, four types of QCL relationships as shown in Table 13 below are supported in NR.

[0250] [Table 13]

[0251] 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

[0252] The spatial Rx parameters as a whole may refer to some or all of the following 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.

[0253] The QCL relationship can be configured for the UE through the RRC parameters TCI-state and QCL-info as shown in Table 14 below. Referring to Table 14, the base station can configure one or more TCI states for the UE, thereby notifying information about up to two QCL relationships (qcl-Type1, qcl-Type2) of the RS (i.e., the target RS) that references the TCI state ID. Each piece of QCL information (QCL-Info) for each TCI state may include the serving cell index and BWP index of the reference RS indicated by the corresponding QCL information, the type and ID of the reference BS, and the QCL type as shown in Table 13 above.

[0254] [Table 14]

[0255]

[0256]

[0257] Figure 7 An example of base station beam allocation configured according to TCI status is shown.

[0258] See also Figure 7 , the base station can transmit information about N different beams to the UE through N different TCI states. Figure 7 When N=3, the base station can configure the qcl-Type2 parameters included in the three TCI states 700, 705 and 710 as QCL typeD, and associate them with CSI-RS or SSB corresponding to different beams, thereby notifying that the antenna ports referencing different TCI states 700, 705 and 710 are associated with different spatial Rx parameters (i.e., different beams).

[0259] Tables 15-1 to 15-5 below enumerate the valid TCI state configurations according to the target antenna port type.

[0260] Table 15-1 enumerates the valid TCI state configurations when the target antenna port is a CSI-RS (TRS) for tracking. TRS refers to an NZP CSI-RS among CRI-RSs for which no repetition parameter is configured and whose trs-Info is configured as "true". In Table 15-1, configuration 3 can be used for aperiodic TRS.

[0261] [Table 15-1] Valid TCI state configuration when the target antenna port is CSI-RS (TRS) for tracking

[0262]

[0263]

[0264] Table 15-2 enumerates the valid TCI state configurations when the target antenna port is a CSI-RS for CSI. The CSI-RS for CSI may refer to an NZP CSI-RS for which no parameter indicating repetition (e.g., a repetition parameter) is configured among the CRI-RS and whose trs-Info is not configured as "true".

[0265] [Table 15-2] Valid TCI state configuration when the target antenna port is CSI-RS for CSI

[0266]

[0267] Table 15-3 enumerates the valid TCI state configuration when the target antenna port is a CSI-RS for beam management (BM) (which has the same meaning as the CSI-RS for L1 RSRP reporting). The CSI-RS for BM refers to an NZP CSI-RS with a repetition parameter configured as a value of "on" or "off" among CRI-RSs and whose trs-Info is not configured as "true".

[0268] [Table 15-3] Valid TCI state configuration when the target antenna port is CSI-RS for BM (for L1 RSRP reporting)

[0269]

[0270] Table 15-4 enumerates the valid TCI state configurations when the target antenna port is PDCCH DMRS.

[0271] [Table 15-4] Valid TCI state configuration when the target antenna port is PDCCH DMRS

[0272]

[0273] Table 15-5 enumerates the valid TCI state configurations when the target antenna port is PDSCH DMRS.

[0274] [Table 15-5] Valid TCI state configuration when the target antenna port is PDSCH DMRS

[0275]

[0276] According to the representative QCL configuration method based on Tables 15-1 to 15-5 above, the target antenna port and the reference antenna port of each step are configured and operated such as "SSB" -> "TRS" -> "CSI-RS for CSI or CSI-RS for BM or PDCCH DMRS or PDSCH DMRS". Accordingly, the reception operation of the UE can be assisted by associating statistical characteristics that can be measured from the SSB and TRS with each antenna port.

[0277] [PDCCH: About TCI status]

[0278] The specific TCI state combinations applicable to the PDCCH DMRS antenna ports may be given in the following Table 16. The fourth row in Table 16 corresponds to the combination assumed by the UE before RRC configuration, and no configuration is possible after RRC.

[0279] [Table 16]

[0280]

[0281]

[0282] Figure 8 An example of a method for allocating TCI states to a PDCCH in a wireless communication system according to an embodiment of the present disclosure is shown.

[0283] In NR, for dynamic allocation of PDCCH beams, the following are supported: Figure 8 The layered signaling approach shown in Figure 1. Figure 8 , the base station may configure N TCI states 805, 810, ..., 820 for the UE through RRC signaling 800, and may configure some of the states as the TCI states of the CORESET (825). The base station may then indicate one of the TCI states 830, 835, and 840 of the CORESET to the UE through MAC control element (CE) signaling (845). The UE may then receive the PDCCH based on the beam information included in the TCI state indicated by the MAC CE signaling.

[0284] Fig. 9 The TCI indication MAC CE signaling structure for PDCCH DMRS is shown.

[0285] See also Fig. 9 , TCI indication MAC CE signaling for PDCCH DMRS can be configured by 2 bytes (16 bits) and includes a 5-bit serving cell ID 915, a 4-bit CORESET ID 920 and a 7-bit TCI state ID 925.

[0286] Fig.10 An example of beam configuration for a control resource set (CORESET) and a search space according to the above description is shown.

[0287] See also Fig.10, the base station may indicate one of the TCI state lists (1005) included in the CORESET 1000 configuration through MAC CE signaling. Until different TCI states are indicated for the corresponding CORESET through different MAC CE signaling, the UE may consider that the same QCL information (beam #1) 1005 is applied to one or more search spaces 1010, 1015, and 1020 connected to the CORESET. The above-mentioned PDCCH beam allocation method may have a problem in that it is difficult to indicate a beam change faster than the MACCE signaling delay, and the same beam is unilaterally applied to each CORESET regardless of the search space characteristics, making flexible PDCCH beam operation difficult. The following embodiments of the present disclosure provide more flexible PDCCH beam configuration and operation methods. Although a plurality of different examples will be provided for the convenience of describing the embodiments of the present disclosure, they are not mutually exclusive and may be appropriately combined and applied for each situation.

[0288] The base station can configure one or more TCI states for the UE for a specific control resource set, and can activate one of the configured TCI states through a MACCE activation command. For example, if {TCI state #0, TCI state #1, TCI state #2} is configured as the TCI state of control resource set #1, the base station can send an activation command to the UE through a MAC CE so that TCI state #0 is assumed to be the TCI state for control resource set #1. Based on the activation command for the TCI state received through the MAC CE, the UE can correctly receive the DMRS of the corresponding CORESET based on the QCL information in the activated TCI state.

[0289] For CORESET with configuration index 0 (CORESET#0), if the UE has not yet received a MAC CE activation command regarding the TCI state of CORESET#0, the UE can assume that the DMRS sent in CORESET#0 has been QCLed with the SS / PBCH blocks identified during the initial access procedure or in a non-contention-based random access procedure not triggered by a PDCCH command.

[0290] For a CORESET (CORESET#X) with a configuration index other than 0, if the UE has no TCI state configured for CORESET#X, or if the UE has one or more TCI states configured for it but has not yet received a MAC CE activation command to activate one of them, the UE may assume that the DMRS sent in CORESET#X is already QCL with the SS / PBCH blocks identified during the initial access procedure.

[0291] [About rate matching / puncturing]

[0292] Hereinafter, the rate matching operation and the puncturing operation will be described in detail.

[0293] If the time-frequency resource A used to send symbol sequence A overlaps with the time-frequency resource B, then considering resource C (the area where resource A and resource B overlap), the rate matching or puncturing operation can be considered as the operation of sending / receiving channel A. The specific operation can follow the following description.

[0294] Rate Matching Operation

[0295] - The base station may transmit channel A after mapping channel A only to the remaining resource region except resource C (region overlapping with resource B) among the entire resource A to be used to transmit the symbol sequence A to the UE. For example, if the symbol sequence A is configured as {symbol #1, symbol #2, symbol #3, symbol #4}, if resource A is {resource #1, resource #2, resource #3, resource #4}, and if resource B is {resource #3, resource #5}, the UE may receive the symbol sequence A based on the assumption that the symbol sequence A has been successively mapped to the remaining resources {resource #1, resource #2, resource #4} except {resource #3} (corresponding to resource C) among resource A. Therefore, the base station may transmit the symbol sequence after mapping the symbol sequence {symbol #1, symbol #2, symbol #3} to {resource #1, resource #2, resource #4}, respectively.

[0296] The UE may evaluate resource A and resource B according to scheduling information about symbol sequence A from the base station, thereby evaluating resource C (an area where resource A and resource B overlap). The UE may receive symbol sequence A based on the assumption that symbol sequence A has been mapped to and transmitted in the remaining area except resource C among the entire resource A. For example, if symbol sequence A is configured as {symbol #1, symbol #2, symbol #3, symbol #4}, if resource A is {resource #1, resource #2, resource #3, resource #4}, and if resource B is {resource #3, resource #5}, the UE may receive symbol sequence A based on the assumption that the symbol sequence has been successively mapped to the remaining resources {resource #1, resource #2, resource #4} except {resource #3} (corresponding to resource C) among resource A. Therefore, based on the assumption that the symbol sequence {symbol #1, symbol #2, symbol #3} has been transmitted after being respectively mapped to {resource #1, resource #2, resource #4}, the UE may perform a series of the following reception operations.

[0297] Punching operation

[0298] If there is resource C (an area overlapping with resource B) in the entire resource A to be used to send symbol sequence A to the UE, the base station can map the symbol sequence A to the entire resource A, but may not perform transmission in the resource area corresponding to resource C, and may only perform transmission on the remaining resource areas in resource A except resource C. For example, if symbol sequence A is configured as {symbol #1, symbol #2, symbol #3, symbol #4}, if resource A is {resource #1, resource #2, resource #3, resource #4}, and if resource B is {resource #3, resource #5}, the UE may assume that symbol sequence A {symbol #1, symbol #2, symbol #3, symbol #4} is mapped to resource A {resource #1, resource #2, resource #3, resource #4}, respectively, but {symbol #3} mapped to {resource #3} (corresponding to resource C) is not transmitted, and the UE may receive the symbol sequence based on the assumption that the symbol sequence {symbol #1, symbol #2, symbol #4} corresponding to the remaining resources {resource #1, resource #2, resource #4} except {resource #3} (corresponding to resource C) in resource A has been mapped and transmitted. Therefore, the base station may transmit the symbol sequence after mapping the symbol sequence {symbol #1, symbol #2, symbol #4} to {resource #1, resource #2, resource #4}, respectively.

[0299] The UE can evaluate resource A and resource B according to the scheduling information about symbol sequence A from the base station, thereby evaluating resource C (a region where resource A and resource B overlap). The UE can receive symbol sequence A based on the assumption that symbol sequence A has been mapped to the entire resource A but is transmitted only in the remaining region of resource region A except resource C. For example, if symbol sequence A is configured as {symbol #1, symbol #2, symbol #3, symbol #4}, if resource A is {resource #1, resource #2, resource #3, resource #4}, and if resource B is {resource #3, resource #5}, the UE may assume that symbol sequence A {symbol #1, symbol #2, symbol #3, symbol #4} is mapped to resource A {resource #1, resource #2, resource #3, resource #4} respectively, but {symbol #3} mapped to {resource #3} (corresponding to resource C) is not sent, and based on the assumption that the symbol sequence {symbol #1, symbol #2, symbol #4} corresponding to the remaining resources {resource #1, resource #2, resource #4} in resource A except {resource #3} (corresponding to resource C) has been mapped and sent, the UE may receive the symbol sequence. Therefore, based on the assumption that the symbol sequence {symbol #1, symbol #2, symbol #4} has been transmitted after being respectively mapped to {resource #1, resource #2, resource #4}, the UE can perform a series of the following reception operations.

[0300] Hereinafter, a method for configuring rate matching resources for the purpose of rate matching in a 5G communication system will be described. Rate matching refers to adjusting the size of a signal while taking into account the amount of resources that can be used to send the signal. For example, data channel rate matching may mean that a data channel is not mapped and sent for a specific time-frequency resource domain, and the size of the data is adjusted accordingly.

[0301] Fig.11 A method in which a base station and a UE transmit / receive data in consideration of a downlink data channel and rate matching resources is shown.

[0302] Fig.11 A downlink data channel (PDSCH) 1101 and a rate matching resource 1102 are shown. The base station can configure one or more rate matching resources 1102 for the UE through upper layer signaling (e.g., RRC signaling). The rate matching resource 1102 configuration information may include time domain resource allocation information 1103, frequency domain resource allocation information 1104, and period information 1105. The bitmap corresponding to the frequency domain resource allocation information 1104 will be referred to as the "first bitmap" hereinafter, the bitmap corresponding to the time domain resource allocation information 1103 will be referred to as the "second bitmap", and the bitmap corresponding to the period information 1105 will be referred to as the "third bitmap". If all or some of the time-frequency resources of the scheduled PDSCH 1101 overlap with the configured rate matching resources 602, the base station can rate match and transmit the PDSCH 1102 in the rate matching resource 1101 part, and the UE can perform reception and decoding after assuming that the PDSCH 1102 has been rate matched in the rate matching resource 1101 part.

[0303] The base station can dynamically inform the UE via DCI whether the PDSCH will be rate matched in the configured rate matching resource part through an additional configuration (e.g., corresponding to the "rate matching indicator" within the above-mentioned DCI format). Specifically, the base station can select some from the configured rate matching resources and group them into rate matching resource groups, and can indicate to the UE via DCI whether the PDSCH is rate matched for each rate matching resource group by using a bitmap type. For example, if 4 rate matching resources RMR#1, RMR#2, RMR#3 and RMR#4 are configured, the base station can configure the rate matching group RMG#1={RMR#1,RMR#2}, RMG#2={RMR#3,RMR#4}, and can indicate to the UE via a bitmap whether the rate matching occurs in RMG#1 and RMG#2 respectively by using two bits within the DCI field. For example, in the case where rate matching is to be performed, the base station can indicate this situation with "1", and in the case where rate matching is not to be performed, the base station can indicate this situation with "0".

[0304] 5G supports the granularity of "RB symbol level" and "RE level" as a method for configuring the above rate matching resources for the UE. More specifically, the following configuration method can be followed.

[0305] RB symbol level

[0306] The UE may have up to 4 RateMatchPattern configured per bandwidth part through upper layer signaling, and one RateMatchPattern may include the following contents.

[0307] - In conjunction with the reserved resources within the bandwidth part, resources in the time-frequency resource domain with corresponding reserved resources configured as a combination of an RB level bitmap and a symbol level bitmap in the frequency domain may be included. The reserved resources may span one or two time slots. A time domain pattern (periodicityAndPattern) may be additionally configured, wherein the time-frequency domain including each pair of RB level bitmap and symbol level bitmap is repeated.

[0308] - may include a resource region corresponding to a time domain pattern configured by a time-frequency domain resource region configured by a CORESET within a bandwidth part, and a search space configuration in which the corresponding resource region is repeated.

[0309] RE Level

[0310] The UE may have the following contents configured through upper layer signaling.

[0311] - About the configuration information (lte-CRS-ToMatchAround) of REs corresponding to the LTE CRS (cell-specific reference signal or common reference signal) pattern, which may include the port number (nrofCRS-Ports) and (multiple) LTE-CRS-vshift values ​​(v-shift) of the LTE CRS, the position information (carrierFreqDL) of the center subcarrier of the LTE carrier from the reference frequency point (e.g., reference point A), the bandwidth size (carrierBandwidthDL) information of the LTE carrier, and the subframe configuration information (mbsfn-SubframConfigList) corresponding to the multicast-broadcast single-frequency network (MBSFN), etc. The UE can determine the position of the CRS in the NR time slot corresponding to the LTE subframe based on the above multiple information.

[0312] - May include configuration information about resource sets corresponding to one or more zero-power (ZP) CSI-RS within a bandwidth part.

[0313] [About LTE CRS rate matching]

[0314] Next, the rate matching process for the above-mentioned LTE CRS will be described in detail. In NR, for coexistence between long term evolution (LTE) and new RAT (NR) (LTE-NR coexistence), the pattern of the cell-specific reference signal (CRS) of LTE can be configured for the NR UE. More specifically, the CRS pattern can be provided by RRC signaling including at least one parameter within the ServingCellConfig IE (information element) or the ServingCellConfigCommon IE. Examples of parameters may include lte-CRS-ToMatchAround, lte-CRS-PatternList1-r16, lte-CRS-PatternList2-r16, crs-RateMatch-PerCORESETPoolIndex-r16, etc.

[0315] Release 15NR provides a function that can configure a CRS pattern for each serving cell through the parameter lte-CRS-ToMatchAround. In Release 16NR, the above function has been extended to make it possible to configure multiple CRS patterns for each serving cell. More specifically, a UE with a single TRP (transmission and reception point) configuration can now configure a CRS pattern for each LTE carrier, and a UE with a multi-TRP configuration can now configure two CRS patterns for each LTE carrier. For example, a UE with a single TRP configuration can configure up to 3 CRS patterns for each serving cell through the parameter lte-CRS-PatternList1-r16. As another example, a UE with a multi-TRP configuration can configure CRS for each TRP. That is, the CRS pattern for TRP1 can be configured through the parameter lte-CRS-PatternList1-r16, and the CRS pattern for TRP2 can be configured through the parameter lte-CRS-PatternList2-r16. If two TRPs are configured as above, the parameter crs-RateMatch-PerCORESETPoolIndex-r16 is used to determine whether the CRS patterns of both TRP1 and TRP2 are applied to a specific physical downlink shared channel (PDSCH) or only the CRS pattern of one TRP is applied, where if the parameter crs-RateMatch-PerCORESETPoolIndex-r16 is configured to "Enabled", only the CRS pattern of one TRP is applied, and in other cases, the CRS patterns of both TRPs are applied.

[0316] Table 17 shows ServingCellConfig IE including the CRS pattern, and Table 18 shows RateMatchPatternLTE-CRS IE including at least one parameter regarding the CRS pattern.

[0317] [Table 17]

[0318]

[0319]

[0320]

[0321]

[0322]

[0323] [Table 18]

[0324]

[0325]

[0326]

[0327] [PDCCH: QCL priority sorting rules]

[0328] Hereinafter, an operation for determining the QCL priority with respect to the PDCCH will be described in detail.

[0329] If multiple control resource sets operating according to carrier aggregation within a single cell or frequency band and existing in a bandwidth portion activated within a single or multiple cells overlap in time and have the same or different QCL-TypeD characteristics in a specific PDCCH monitoring opportunity, the UE can select a specific control resource set according to the QCL priority determination operation and can monitor the control resource set having the same QCL-TypeD characteristics as the corresponding control resource set. That is, if multiple control resource sets overlap in time, only one QCL-TypeD characteristic can be received. The QCL priority can be determined by the following criteria.

[0330] - Criterion 1: Among cells including a common search space, the control resource set connected to the common search space with the lowest index in the cell corresponding to the lowest index

[0331] - Criterion 2: Among the cells including the UE-specific search space, the control resource set connected to the UE-specific search space with the lowest index in the cell corresponding to the lowest index

[0332] As described above, if one of the criteria is not met, the next criterion may be applied. For example, if the control resource sets overlap in time in a specific PDCCH monitoring opportunity, and if all control resource sets are not connected to a common search space but to a UE-specific search space (e.g., if criterion 1 is not met), the UE may omit the application of criterion 1 and apply criterion 2.

[0333] If the control resource set is selected according to the above criteria, the UE may additionally consider two aspects of the QCL information configured for the control resource set. First, if control resource set 1 has CSI-RS 1 as a reference signal with a QCL-TypeD relationship, if the CSI-RS1 has a QCL-TypeD relationship with reference signal SSB 1, and if another control resource set 2 has a QCL-TypeD relationship with reference signal SSB 1, the UE may consider that the two control resource sets 1 and 2 have different QCL-TypeD characteristics. Second, if control resource set 1 has CSI-RS1 configured for cell 1 as a reference signal with a QCL-TypeD relationship, if the CSI-RS1 has a QCL-TypeD relationship with reference signal SSB 1, if control resource set 2 has a QCL-TypeD relationship with reference signal CSI-RS2 configured for cell 2, and if the CSI-RS2 has a QCL-TypeD relationship with the same reference signal SSB 1, the UE may consider that the two control resource sets have the same QCL-TypeD characteristics.

[0334] Fig.12A method for selecting a receivable control resource set in consideration of priority when a UE in a wireless communication system according to an embodiment of the present disclosure receives a downlink control channel is shown. As an example, the UE may be configured to receive multiple control resource sets overlapping in time in a specific PDCCH monitoring opportunity 1210, and such multiple control resource sets may be connected to a common search space or a UE-specific search space for multiple cells. In the corresponding PDCCH monitoring opportunity, a control resource set 1 1215 connected to the common search space 1 may exist in a bandwidth part 11200 of cell 1, and a control resource set 1 1220 connected to the common search space 1 and a control resource set 2 1225 connected to the UE-specific search space 2 may exist in a bandwidth part 1 1205 of cell 2. The control resource sets 1215 and 1220 may have a QCL-TypeD relationship with the CSI-RS resource 1 configured in the bandwidth part 1 of cell 1, and the control resource set 1225 may have a QCL-TypeD relationship with the CSI-RS resource 1 configured in the bandwidth part 1 of cell 2. If criterion 1 is applied to the corresponding PDCCH monitoring opportunity 1210, all other control resource sets having the same QCL-TypeD reference signal as control resource set 1 1215 may be received. Therefore, the UE may receive control resource sets 1215 and 1220 in the corresponding PDCCH monitoring opportunity 1210. As another example, the UE may be configured to receive a plurality of control resource sets overlapping in time in a specific PDCCH monitoring opportunity 1240, and such a plurality of control resource sets may be connected to a common search space or a UE-specific search space for a plurality of cells. In the corresponding PDCCH monitoring opportunity, control resource set 1 1245 connected to UE-specific search space 1 and control resource set 2 1250 connected to UE-specific search space 2 may exist in bandwidth part 1 1230 of cell 1, and control resource set 1 1255 connected to UE-specific search space 1 and control resource set 2 1260 connected to UE-specific search space 3 may exist in bandwidth part 1 1235 of cell 2. Control resource sets 1245 and 1250 may have a QCL-TypeD relationship with CSI-RS resource 1 configured in bandwidth part 1 of cell 1, control resource set 1255 may have a QCL-TypeD relationship with CSI-RS resource 1 configured in bandwidth part 1 of cell 2, and control resource set 1260 may have a QCL-TypeD relationship with CSI-RS resource 2 configured in bandwidth part 1 of cell 2. If criterion 1 is applied to the corresponding PDCCH monitoring opportunity 1240, there is no common search space, so the next criterion, i.e., criterion 2, may be applied.If criterion 2 is applied to the corresponding PDCCH monitoring opportunity 1240 , all other control resource sets having the same QCL-Type D reference signal as control resource set 1 1245 may be received. Therefore, the UE may receive control resource sets 1245 and 1250 in the corresponding PDCCH monitoring opportunity 1240 .

[0335] [PDSCH: Regarding frequency resource allocation]

[0336] Fig.13 An example of frequency domain resource allocation for a physical downlink shared channel (PDSCH) in a wireless communication system according to an embodiment of the present disclosure is shown.

[0337] Fig.13 Three frequency domain resource allocation methods that can be configured by the upper layer in the NR wireless communication system are shown: Type 0 13-00, Type 1 13-01, and dynamic switching 13-10.

[0338] See also Fig.13 , in the case where the UE is configured to use only resource type 0 by upper layer signaling (13-00), the partial downlink control information (DCI) used to allocate PDSCH to the UE includes a bitmap containing the NRBG bit. The conditions for this case will be described again later. As used herein, NRBG refers to the number of resource block groups (RBGs) determined according to the BWP size allocated by the BWP indicator and the upper layer parameter rbg-Size, as shown in Table 19 below, and data is sent in the RBG indicated by the bitmap as "1".

[0339] [Table 19]

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

[0341] In the case where the UE is configured to use only resource type 1 through upper layer signaling (13-05), the partial DCI includes The conditions for this case will be described again later. The base station can thus configure the starting VRB 13-20 and the length 13-25 of the frequency domain resources from which the allocation is to be performed continuously.

[0342] In the case where the UE is configured to use both resource type 0 and resource type 1 through upper layer signaling (13-10), the partial DCI for allocating PDSCH to the corresponding UE includes frequency domain resource allocation information containing as many bits as the payload 13-15 for configuring resource type 0 and the larger value 13-35 among the payloads 13-20 and 13-25 for configuring resource type 1. The conditions for this situation will be described again later. One bit can be added to the front part (MSB) of the frequency domain resource allocation information within the DCI. If the value of this bit is "0", the use of resource type 0 can be indicated, and if the value of this bit is "1", the use of resource type 1 can be indicated.

[0343] [PDSCH / PUSCH: About time resource allocation]

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

[0345] The base station can configure a table for time domain resource allocation information about a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH) for the UE through upper layer signaling (e.g., RRC signaling). A table including a maximum of maxNrofDL-Allocations=16 entries can be configured for PDSCH, and a table including a maximum of maxNrofUL-Allocations=16 entries can be configured for PUSCH. In one embodiment, the time domain resource allocation information may include PDCCH to PDSCH time slot timing (e.g., corresponding to the time slot unit time interval between the time point when the PDCCH is received and the time point when the PDSCH scheduled by the received PDCCH is sent; marked as K0), PDCCH to PUSCH time slot timing (e.g., corresponding to the time slot unit time interval between the time point when the PDCCH is received and the time point when the PUSCH scheduled by the received PDCCH is sent; marked as K2 below), information about the position and length of the starting symbol of the PDSCH or PUSCH scheduled within the time slot, the mapping type of the PDSCH or PUSCH, etc. For example, information such as in Table 20 or Table 21 below may be sent from the base station to the UE.

[0346] [Table 20]

[0347]

[0348]

[0349] [Table 21]

[0350]

[0351] The base station may notify the UF of one of the entries in the table of the above-mentioned time domain resource allocation information through L1 signaling (e.g., DCI) (e.g., the "time domain resource allocation" field in the DCI may indicate the information). The UE may obtain the time domain resource allocation information about the PDSCH or PUSCH based on the DCI obtained from the base station.

[0352] Fig.14 An example of time domain resource allocation for PDSCH in a wireless communication system according to an embodiment of the present disclosure is shown.

[0353] See also Fig.14 The base station can configure the data channel and the control channel according to the subcarrier spacing (SCS) (μ PDSCH , μ PDCCH ), scheduling offset (K0) value, and the OFDM symbol starting position 14-00 and length 14-05 within the time slot dynamically indicated by DCI to indicate the time domain position of the PDSCH resource.

[0354] [PDSCH: TCI state activated MAC-CE]

[0355] Fig.15 The process for beam configuration and activation for PDSCH is shown. The TCI state list for PDSCH can be indicated by an upper layer list (such as RRC) (15-00). For example, the TCI state list can be indicated by tci-StatesToAddModList and / or tci-StatesToReleaseList within the BWP-specific PDSCH-Config IE. Next, a portion of the TCI state list can be activated by MAC-CE (15-20). Among the TCI states activated by MAC-CE, the TCI state of PDSCH can be indicated by DCI (15-40). The maximum number of activated TCI states can be determined by the capabilities reported by the UE. "15-50" shows an example of a MAC-CE structure for PDSCH TCI state activation / deactivation.

[0356] The meaning of each field in the MAC CE and the configurable values ​​for each field are as follows.

[0357] - Serving Cell ID (Serving Cell Identity): This field indicates the identity of the serving cell to which the MAC CE applies. The length of this field is 5 bits. If the indicated serving cell is configured as part of simultaneousTCI-UpdateList1 or simultaneousTCI-UpdateList2 as specified in TS 38.331 [5], then this MAC CE applies to all serving cells configured in the simultaneousTCI-UpdateList1 or simultaneousTCI-UpdateList2 respectively;

[0358] - BWP ID (Bandwidth Part Identification): This field indicates the DL BWP to which the MAC CE applies as the code point of the DCI Bandwidth Part Indicator field as specified in TS 38.212 [9]. The length of the BWP ID field is 2 bits. This field is ignored if the MAC CE applies to a serving cell set;

[0359] -Ti (TCI State Identifier): If there is a TCI state with TCI-StateId i as specified in TS 38.331 [5], this field indicates the activation / deactivation status of the TCI state with TCI-StateId i, otherwise the MAC entity shall ignore the Ti field. The Ti field is set to 1 to indicate that the TCI state with TCI-StateId i will be activated and mapped to the codepoint of the DCI transmission configuration indication field as specified in TS 38.214 [7]. The Ti field is set to 0 to indicate that the TCI state with TCI-StateId i will be deactivated and not mapped to the codepoint of the DCI transmission configuration indication field. The codepoint to which the TCI state is mapped is determined by its ordinal position among all TCI states with the Ti field set to 1, that is, the first TCI state with the Ti field set to 1 will be mapped to the codepoint value 0, the second TCI state with the Ti field set to 1 will be mapped to the codepoint value 1, and so on. The maximum number of activated TCI states is 8;

[0360] -CORESET Pool ID: This field indicates that the mapping between the activated TCI state and the codepoint indicated by the DCI transmission configuration set by field Ti is specific to the ControlResourceSetId configured with the CORESET Pool ID as specified in TS 38.331 [5]. This field is set to 1 to indicate that this MAC CE will be applied to DL transmissions scheduled by the CORESET with CORESET Pool ID equal to 1, otherwise, this MAC CE will be applied to DL transmissions scheduled by the CORESET with CORESET Pool ID equal to 0. If coresetPoolIndex is not configured for any CORESET, the MAC entity will ignore the CORESET Pool ID field in the MAC CE when receiving the MAC CE. If the serving cell in the MAC CE is configured in a cell list containing more than one serving cell, the CORESET Pool ID field will be ignored when receiving the MAC CE.

[0361] [PUCCH: related to transmission]

[0362] In the NR system, the UE can send control information (uplink control information, UCI) to the base station through the physical uplink control channel (PUCCH). The control information may include at least one of the following: HARQ-ACK indicating whether the UE has successfully demodulated / decoded the transport block (TB) received through the PDSCH, a scheduling request (SR) through which the UE requests the PUSCH base station to allocate resources for uplink data transmission, and channel state information (CSI) as information for reporting the channel state of the UE.

[0363] According to the length of the allocated symbol, PUCCH resources can generally be classified into long PUCCH and short PUCCH. In the NR system, the length of long PUCCH in a time slot is 4 or more symbols, and the length of short PUCCH in a time slot is 2 or less symbols.

[0364] In a more detailed description of the long PUCCH, the long PUCCH can be used for the purpose of increasing uplink cell coverage and can therefore be sent in a DFT-S-OFDM scheme associated with single carrier transmission rather than OFDM transmission. Depending on the number of control information bits that can be supported and the support or non-support of UE multiplexing through pre-DFT OCC (orthogonal cover code) support at the IFFT front end, the long PUCCH supports transmission formats such as PUCCH format 1, PUCCH format 3 and PUCCH format 4.

[0365] 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 corresponding to 1 RB. The control information may be configured by HARQ-ACK, SR, or a combination thereof. PUCCH format 1 repeatedly includes an OFDM symbol containing a demodulation reference signal (DMRS) as a demodulation reference signal (or reference signal) and an OFDM symbol containing UCI.

[0366] For example, if the number of transmission symbols of PUCCH format 1 is 8, the 8 symbols can be sequentially configured from the first starting symbol by DMRS symbol, UCI symbol, DMRS symbol, UCI symbol, DMRS symbol, UCI symbol, DMRS symbol and UCI symbol. For a sequence corresponding to the length of 1 RB on the frequency axis in one OFDM symbol, an orthogonal code (or orthogonal sequence or spread code w is used on the time axis. i (m)) to spread the DMRS symbol, and IFFT can be performed on it and then transmitted.

[0367] Regarding the UCI symbol, the UE may perform BPSK modulation of 1-bit control information or QPSK modulation of 2-bit control information to generate d(0), multiply the generated d(0) by a sequence corresponding to the length of 1 RB on the frequency axis to scramble it, and perform scrambling by using an orthogonal code (or an orthogonal sequence or a spreading code w on the time axis). i (m)) to spread the scrambling sequence, perform IFFT on the spread sequence, and transmit it.

[0368] The UE generates a sequence based on the group hopping configuration or sequence hopping configuration and the configuration ID configured by the base station through high-layer signaling, and performs a cyclic shift on the generated sequence by using an initial cyclic shift (CS) value configured via a high-layer signal to generate a sequence corresponding to a length of 1 RB.

[0369] When the length of the spreading code (N SF ) and is specifically given as shown in [Table 22] below, w i (m) is determined as i means the index of the extension code itself, and m represents the index of each element of the extension code. Here, the numbers in the square brackets [] in [Table 22] indicate that, when the length of the extension code is 2 and the configuration index i of the extension code is 0 (i=0), the extension code w i (m) becomes and Therefore it is equal to [1 1].

[0370] [Table 22]

[0371]

[0372] 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 by the higher layer. The control information can be configured by HARQ-ACK, SR, CSI, or a combination thereof. Depending on whether there is frequency hopping in the time slot and whether additional DMRS symbols are configured, the DMRS symbol position in PUCCH format 3 is presented in the following [Table 23].

[0373] [Table 23]

[0374]

[0375]

[0376] If the number of transmission symbols of PUCCH format 3 is 8, when the 0th symbol is used as the first starting symbol among 8 symbols, DMRS is transmitted on the first symbol and the fifth symbol. [Table 23] is applied even to the DMRS symbol position of PUCCH format 4 in the same manner.

[0377] 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 frequency resources corresponding to 1 RB. The control information can be configured by HARQ-ACK, SR, CSI, or a combination thereof. The difference between PUCCH format 4 and PUCCH format 3 is that, in the case of PUCCH format 4, the PUCCH format 4 of several UEs is multiplexed in one RB. The PUCCH format 4 of multiple UEs can be multiplexed by applying a pre-DFT orthogonal cover code (OCC) to the control information at the IFFT front end. However, the number of control information symbols that can be sent by one UE is reduced according to the number of multiplexed UEs. The number of multiplexed UEs (i.e., the number of different OCCs available) can be 2 or 4, and the number of OCCs to be applied and the OCC index can be configured by a high layer.

[0378] Next, the short PUCCH is described. The short PUCCH can be sent on both the downlink-centric time slot and the uplink-centric time slot, and generally speaking, can be sent on the last symbol of the time slot or the OFDM symbol located at the rear (for example, the last OFDM symbol, the second to last OFDM symbol, or the last two OFDM symbols). The short PUCCH can also be sent at a random position in a time slot. The short PUCCH can be sent using one OFDM symbol or two OFDM symbols. In the case of good uplink cell coverage, the short PUCCH can be used to shorten the delay time compared to the long PUCCH, and can be sent in the CP-OFDM scheme.

[0379] According to the number of control information bits that can be supported, the short PUCCH can support transmission formats such as PUCCH format 0 and PUCCH format 2. First, PUCCH format 0 is a short PUCCH format that can support up to 2 bits of control information and uses frequency resources corresponding to 1 RB. The control information can be configured by HARQ-ACK, SR, or a combination thereof. PUCCH format 0 does not send DMRS and has a structure that only sends a sequence of 12 subcarriers mapped to the frequency axis in one OFDM symbol. The UE can generate a sequence based on a group hopping configuration or a sequence hopping configuration and a configuration ID configured by a base station through a high-layer signal, perform a cyclic shift (CS) on the generated sequence by using a final CS value obtained after adding a CS value that varies according to ACK or NACK to the indicated initial CS value, map the sequence to 12 subcarriers, and send the mapped sequence.

[0380] For example, in the case where HARQ-ACK has 1 bit, as shown in the following [Table 24], if HARQ-ACK is ACK, the UE can generate the final CS by adding 6 to the initial CS value, and if HARQ-ACK is NACK, the UE can generate the final CS by adding 0 to the initial CS. The value 0 as the CS value for NACK and the value 6 as the CS value for ACK are defined in the specification, and the UE can generate PUCCH format 0 according to the values ​​defined in the specification to send 1-bit HARQ-ACK.

[0381] [Table 24]

[0382] 1-bit HARQ-ACK NACK ACK Final CS (initial CS+0) mod 12 = initial CS (initial CS+6) mod 12

[0383] For example, in the case where HARQ-ACK has 2 bits, as shown in the following [Table 25], if HARQ-ACK is (NACK, NACK), the UE can add 0 to the initial CS value, if HARQ-ACK is (NACK, ACK), add 3 to the initial CS value, if HARQ-ACK is (ACK, ACK), add 6 to the initial CS value, and if HARQ-ACK is (ACK, NACK), add 9 to the initial CS value. The value 0 as the CS value for (NACK, NACK), the value 3 as the CS value for (NACK, ACK), the value 6 as the CS value for (ACK, ACK), and the value 9 as the CS value for (ACK, NACK) are defined in the specification, and the UE can generate PUCCH format 0 according to the values ​​defined in the specification to send 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 length of the sequence is 12, the modulo 12 can be applied to the final CS value.

[0384] [Table 25]

[0385]

[0386]

[0387] 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 by a higher layer. The control information can be configured by HARQ-ACK, SR, CSI, or a combination thereof. If the index of the first subcarrier is #0, PUCCH format 2 can be fixed to subcarriers with indices #1, #4, #7, and #10 as the subcarrier positions on which DMRS is transmitted in one OFDM symbol. The control information can undergo channel coding and then a modulation process to be mapped to the remaining subcarriers except the subcarrier where the DMRS is located.

[0388] In summary, the configurable values ​​and their ranges for each PUCCH format can be organized as shown in the following [Table 26]. Values ​​that do not need to be configured are indicated by "Not Applicable" in the following [Table 26].

[0389] [Table 26]

[0390]

[0391]

[0392] For uplink coverage improvement, multi-slot repetition can be supported for PUCCH formats 1, 3 and 4, and PUCCH repetition can be configured for each PUCCH format. The UE can perform repetition of PUCCH including UCI, and the number of repetitions is as many as the number of slots configured by high-level signaling nrofSlots. For PUCCH repetition, the same number of consecutive symbols is used to perform PUCCH transmission on each slot, and the number of consecutive symbols can be configured by nrofSymbols in high-level signaling PUCCH-format1, PUCCH-format3 or PUCCH-format4. For PUCCH repetition, the same starting symbol is used to perform PUCCH transmission on each slot, and the starting symbol can be configured by startingSymbolIndex in high-level signaling PUCCH-format1, PUCCH-format3 or PUCCH-format4. For PUCCH repetition, a single PUCCH-spatialRelationInfo can be configured for a single PUCCH resource. For PUCCH repetition, if the UE is configured to perform frequency hopping between PUCCH transmissions on different time slots, the UE may perform frequency hopping in units of time slots. In addition, if the UE is configured to perform frequency hopping between PUCCH transmissions on different time slots, the UE may start PUCCH transmission on an even time slot at the first PRB index configured by high-level signaling startingPRB, and start PUCCH transmission on an odd time slot at the second PRB index configured by high-level signaling secondHopPRB. In addition, if the UE is configured to perform frequency hopping between PUCCH transmissions on different time slots, the index of the time slot on which the first PUCCH transmission is performed indicated to the UE is 0, and the PUCCH repetition count value may increase independently of whether PUCCH transmission is performed on each time slot until the configured entire PUCCH repetition count is reached. If the UE is configured to perform frequency hopping between PUCCH transmissions on different time slots, the UE does not expect to configure frequency hopping in the time slot when transmitting PUCCH. If the UE is not configured to perform frequency hopping between PUCCH transmissions on different time slots, and frequency hopping in a time slot is configured, the first PRB index and the second PRB index may also be applied to the time slot in the same manner. If the number of uplink symbols on which PUCCH transmission is possible is less than the number indicated by nrofSymbols configured by higher layer signaling, the UE may not send PUCCH. Even if the UE fails to transmit PUCCH on a time slot for some reason during PUCCH repetition, the UE may increase the PUCCH repetition count.

[0393] [PUCCH: PUCCH resource configuration]

[0394] Next, the PUCCH resource configuration of the base station or UE is described. The base station can configure PUCCH resources for each BWP of a specific UE through a higher layer. The PUCCH resource configuration can be as shown in [Table 27] below.

[0395] [Table 27]

[0396]

[0397]

[0398] According to [Table 27], one or more PUCCH resource sets may be configured in the PUCCH resource configuration for a specific BWP, and a maximum payload value for UCI transmission may be configured for some PUCCH resource sets. One or more PUCCH resources may belong to each PUCCH resource set, and each PUCCH resource may belong to one of the above-mentioned PUCCH formats.

[0399] Regarding PUCCH resource sets, the maximum payload value of the first PUCCH resource set may be fixed to 2 bits. Accordingly, this value may not be configured separately by higher layers. If the remaining PUCCH resource sets are configured, the indexes of the corresponding PUCCH resource sets 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 28] below.

[0400] [Table 28]

[0401]

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

[0403] At the time of initial access, or if the PUCCH resource set is not configured, a PUCCH resource set as shown in the following [Table 29] configured by multiple PUCCH resources specific to the cell in the initial BWP may be used. The PUCCH resources to be used for initial access in the PUCCH resource set may be indicated by SIB1.

[0404] [Table 29]

[0405]

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

[0407] Next, PUCCH resource selection for UCI transmission is described. In the case of SR transmission, PUCCH resources for SR corresponding to the schedulingRequestID shown in the following Table 30 may be configured by a higher layer. The PUCCH resource may be a resource belonging to PUCCH format 0 or PUCCH format 1.

[0408] [Table 30]

[0409]

[0410] The transmission period and offset of the configured PUCCH resources may be configured by the parameter periodicityAndOffset in Table 30. If there is uplink data to be sent by the UE at a time point corresponding to the configured period and offset, the PUCCH resources are sent, otherwise, the PUCCH resources may not be sent.

[0411] In the case of CSI transmission, the PUCCH resources on which periodic CSI reports or semi-persistent CSI reports are to be sent through PUCCH can be configured in the parameter pucch-CSI-ResourceList, as shown in Table 31 below. The parameter pucch-CSI-ResourceList may include a list of PUCCH resources for each BWP of the cell or CC on which the CSI report is to be sent. The PUCCH resources may be resources belonging to PUCCH format 2, PUCCH format 3, or PUCCH format 4. The transmission period and offset of the PUCCH resources may be configured by reportSlotConfig in Table 31.

[0412] [Table 31]

[0413]

[0414] In the case of HARQ-ACK transmission, a resource set of PUCCH resources to be sent may be first selected based on the payload of the UCI including the HARQ-ACK. That is, a PUCCH resource set with a minimum payload not less than the UCI payload may be selected. Next, the PUCCH resources in the PUCCH resource set may be selected by a PUCCH resource indicator (PRI) in the DCI for scheduling the TB corresponding to the HARQ-ACK, and the PRI may be a PUCCH resource indicator specified in Table 6 or Table 7. The relationship between the PRI and the PUCCH resources selected in the PUCCH resource set may be as shown in Table 32 below.

[0415] [Table 32]

[0416]

[0417] If the number of PUCCH resources in the selected PUCCH resource set is greater than 8, the PUCCH resources may be selected by Equation 3 below.

[0418] [Equation 3]

[0419]

[0420] In equation 3, r PUCCH Indicates the index of the selected PUCCH resource in the PUCCH resource set, R PUCCH represents the number of PUCCH resources belonging to the PUCCH resource set, ΔPRI represents the PRI value, N CCE,p Indicates the total number of CCEs in CORESET p to which the DCI is received, and n CCE,p Indicates the index of the first CCE receiving DCI.

[0421] The time point at which the PUCCH resource is transmitted is K after the transmission of the TB corresponding to the HARQ-ACK. 1 The time point after time slots K 1 The candidates for the value K are configured by higher layers, and more specifically, can be configured in the parameter dl-DataToUL-ACK in the PUCCH-Config specified in Table 27. One of these candidates K 1 The value may be selected by the PDSCH to HARQ feedback timing indicator in the DCI for scheduling the TB, and the value may be the value specified in Table 5 or Table 6. 1 The unit of the value may be a slot unit or a subslot unit. Here, a subslot is a length unit smaller than a slot, and one subslot may be configured by one or more symbols.

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

[0423] [PUCCH: related to transmit beam]

[0424] Next, the uplink transmit beam configuration to be used in PUCCH transmission is described. If the UE does not have a UE-specific configuration for PUCCH resource configuration (dedicated PUCCH resource configuration), the PUCCH resource set is provided through high-level signaling pucch-ResourceCommon, and the beam configuration used for PUCCH transmission follows the beam configuration used in PUCCH transmission scheduled by a random access response (RAR) UL grant. If the UE has a UE-specific configuration for PUCCH resource configuration (dedicated PUCCH resource configuration), the beam configuration for PUCCH transmission may be provided by high-level signaling pucch-spatialRelationInfoId included in [Table 27]. If one pucch-spatialRelationInfoId value is configured for the UE, the beam configuration for PUCCH transmission of the UE may be provided by this one pucch-spatialRelationInfoId value. If multiple pucch-spatialRelationInfoID values ​​are configured for the UE, the activation of one pucch-spatialRelationInfoID value among the multiple values ​​may be indicated to the UE through a MAC control element (CE). A maximum of 8 pucch-spatialRelationInfoID values ​​may be configured for the UE through higher layer signaling, and only one pucch-spatialRelationInfoID value among the 8 values ​​that is activated may be indicated to it. If activation of a random pucch-spatialRelationInfoID value is indicated to the UE through a MAC CE, then from the time slot after sending the HARQ-ACK for the PDSCH sending the MAC CE containing the activation information about the pucch-spatialRelationInfoID Starting from the first time slot after the first time slot, the UE can apply pucch-spatialRelationInfoID activation through MAC CE. μ is the basic parameter set applied to PUCCH transmission, and Indicates the number of time slots per subframe under a given basic parameter set. The high-level configuration for pucch-spatialRelationInfo may be as shown in [Table 33].

[0425] [Table 33]

[0426]

[0427] According to Table 33, one referenceSignal configuration may exist in a specific pucch-spatialRelationInfo configuration, and the referenceSignal may be an ssb-Index indicating a specific SS / PBCH, a csi-RS-Index indicating a specific CSI-RS, or an srs indicating a specific SRS. If the referenceSignal is configured as ssb-Index, the UE may configure the beam used when the SS / PBCH corresponding to the ssb-Index is received among the SS / PBCH in the same serving cell as the beam used for PUCCH transmission, or when servingCellId is provided, configure the beam used when the SS / PBCH corresponding to the ssb-Index is received among the SS / PBCH in the cell indicated by servingCellId as the beam used for PUCCH transmission. If referenceSignal is configured as csi-RS-Index, the UE may configure the beam used when a CSI-RS corresponding to the csi-RS-Index is received among CSI-RSs in the same serving cell as a beam for PUCCH transmission, or when servingCellId is provided, configure the beam used when a CSI-RS corresponding to the csi-RS-Index is received among CSI-RSs in the cell indicated by servingCellId as a beam for PUCCH transmission. If ReferenceSignal is configured as SRS, the UE may configure the transmit beam used when sending an SRS corresponding to a resource index provided by a higher-layer signaling resource in the same serving cell and / or in an activated uplink BWP as a beam for PUCCH transmission, or when servingCellID and / or uplinkBWP are provided, configure the transmit beam used when sending an SRS corresponding to a resource index provided by a higher-layer signaling resource in a cell and / or uplink BWP indicated by servingCellID and / or uplinkBWP as a beam for PUCCH transmission. One pucch-PathlossReferenceRS-Id configuration may exist in a specific pucch-spatialRelationInfo configuration. The PUCCH-PathlossReferenceRS in Table 34 may be mapped to the pucch-PathlossReferenceRS-Id in [Table 33], and up to 4 values ​​may be configured through the pathlossReferenceRS in the higher-layer signaling PUCCH-PowerControl in Table 34.If PUCCH-PathlossReferenceRS is connected to SS / PBCH through higher layer signaling referenceSignal, ssb-Index may be configured, and if it is connected to CSI-RS, csi-RS-Index may be configured.

[0428] [Table 34]

[0429]

[0430] [PUCCH: Group-based spatial relationship activation]

[0431] In Release 15, if multiple pucch-spatialRelationInfoID values ​​are configured for the UE, the UE can receive a MAC CE for activating the spatial relationship of each PUCCH resource to determine the spatial relationship of the PUCCH resources. However, the disadvantage of this method is that a large signaling overhead is required to activate the spatial relationship of multiple PUCCH resources. Therefore, in Release 16, PUCCH resource groups are added, and a new MAC CE for activating spatial relationships in units of PUCCH resource groups is introduced. Up to 4 PUCCH resource groups can be configured through resourceGroupToAddModList in Table 27, and each PUCCH resource group can configure multiple PUCCH resource IDs in a PUCCH resource group as a list, as shown in Table 35 below.

[0432] [Table 35]

[0433]

[0434] In Release 16, the base station can configure each PUCCH resource group for the UE through resourceGroupToAddModList in Table 27 and the high-level configuration in Table 35, and can configure the MAC CE to simultaneously activate the spatial relationship of all PUCCH resources in one PUCCH resource group.

[0435] Fig.16 is a diagram showing an example of a MAC CE for activating a spatial relationship based on a PUCCH resource group in a wireless communication system according to an embodiment of the present disclosure.

[0436] See also Fig.16In the example of , Oct (8-bit byte) 1 1600 indicates a supporting cell ID 1610 and a bandwidth part ID 1620 for which a PUCCH resource to which the corresponding MAC CE is to be applied is configured. A PUCCH resource ID 1631 or 1641 indicates an ID of a PUCCH resource, and if the indicated PUCCH resource is included in a PUCCH resource group according to resourceGroupToAddModList, other PUCCH resource IDs in the same PUCCH resource group are not indicated in the same MAC CE, and all PUCCH resources in the same PUCCH resource group are activated by the same spatial relationship information ID 1636 or 1646. The spatial relationship information ID 1636 or 1646 includes a value corresponding to an expression (PUCCH-SpatialRelationInfoId-1) to be applied to the PUCCH resource group in Table 33.

[0437] [About SRS]

[0438] Next, an uplink channel estimation method using a sounding reference signal (SRS) transmission of a UE will be described. The base station may configure at least one SRS configuration for each uplink BWP to deliver configuration information for SRS transmission to the UE, and may also configure at least one SRS resource set for each SRS configuration. As an example, the base station and the UE may exchange upper layer signaling information as follows to deliver information about the SRS resource set.

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

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

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

[0442] -usage: configuration about the usage location of the SRS resource referenced by the SRS resource set, and can be configured as one of "beamManagement", "codebook", "nonCodebook", and "antennaSwitching".

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

[0444] The UE may understand that the SRS resources included in the set of SRS resource indexes referenced by the SRS resource set comply with the information configured for the SRS resource set.

[0445] In addition, the base station and the UE may send / receive upper layer signaling information to convey separate configuration information about the SRS resources. As an example, the separate configuration information about the SRS resources may include time-frequency domain mapping information within the time slot of the SRS resources, and this may include information about frequency hopping within or between time slots of the SRS resources. The separate configuration information about the SRS resources may include the time domain transmission configuration of the SRS resources, and may be configured as one of "periodic", "semi-persistent" and "aperiodic". The time domain transmission configuration of the SRS resources may be limited to having the same time domain transmission configuration as the SRS resource set including the SRS resources. If the time domain transmission configuration of the SRS resources is configured as "periodic" or "semi-persistent", the time domain transmission configuration may also include the SRS resource transmission period and time slot offset (e.g., periodicityAndOffset).

[0446] The base station may activate or deactivate SRS transmission for the UE through upper layer signaling including RRC signaling or MAC CE signaling or L1 signaling (e.g., DCI). For example, the base station may activate or deactivate periodic SRS transmission for the UE through upper layer signaling. The base station may indicate the activation of an SRS resource set having a resourceType configured as "periodic" through upper layer signaling, and the UE may send SRS resources referenced by the activated SRS resource set. The time-frequency domain resource mapping within the time slot of the transmitted SRS resource follows the resource mapping information configured for the SRS resource, and the time slot mapping including the transmission period and the time slot offset follows the periodicityAndOffset configured for the SRS resource. In addition, the spatial domain transmit filter applied to the transmitted SRS resource may reference the spatial relationship information configured for the SRS resource, or may reference the associated CSI-RS information configured for the SRS resource set including the SRS resource. The UE may send SRS resources within an uplink BWP activated for periodic SRS resources activated by upper layer signaling.

[0447] For example, the base station may activate or deactivate semi-persistent SRS transmission for the UE through upper layer signaling. The base station may indicate the activation of the SRS resource set through MAC CE signaling, and the UE may send the SRS resources referenced by the activated SRS resource set. The SRS resource set activated by MAC CE signaling may be limited to the SRS resource set with resourceType configured as "semi-persistent". The time-frequency domain resource mapping within the time slot of the transmitted SRS resource follows the resource mapping information configured for the SRS resource, and the time slot mapping including the transmission period and time slot offset follows the periodicityAndOffset configured for the SRS resource. In addition, the spatial domain transmit filter applied to the transmitted SRS resource may reference the spatial relationship information configured for the SRS resource, or may reference the associated CSI-RS information configured for the SRS resource set including the SRS resource. If the SRS resource has spatial relationship information configured for it, the spatial domain transmit filter can be determined by referencing the configuration information about the spatial relationship information delivered via MAC CE signaling for activating semi-persistent SRS transmission, without following the spatial relationship information. The UE can transmit the SRS resource within the uplink BWP activated for the semi-persistent SRS resource activated by upper layer signaling.

[0448] For example, the base station may trigger the aperiodic SRS transmission of the UE through the DCI. The base station may indicate one of the aperiodic SRS triggers (aperiodicSRS-ResourceTrigger) through the SRS request field of the DCI. The UE may understand that, among the configuration information of the SRS resource set, the SRS resource set triggered by the aperiodic SRS resource indicated by the DCI in the aperiodic SRS resource trigger list has been triggered. The UE may send the SRS resource referenced by the triggered SRS resource set. The time-frequency domain resource mapping within the time slot of the transmitted SRS resource follows the resource mapping information configured for the SRS resource. In addition, the time slot mapping of the transmitted SRS resource may be determined by the time slot offset between the SRS resource and the PDCCH including the DCI, and this may refer to the (multiple) values ​​included in the time slot offset set configured for the SRS resource set. Specifically, as a time slot offset between an SRS resource and a PDCCH including a DCI, a value indicated in a time domain resource assignment field of a DCI among the (multiple) offset values ​​included in a time slot offset set configured for an SRS resource set may be applied. A spatial domain transmit filter applied to a transmitted SRS resource may reference spatial relationship information configured for an SRS resource, or may reference associated CSI-RS information configured for an SRS resource set including an SRS resource. A UE may transmit an SRS resource within an uplink BWP activated for an aperiodic SRS resource triggered by a DCI.

[0449] If the base station triggers the non-periodic SRS transmission of the UE through DCI, a minimum time interval between the transmitted SRS and the PDCCH including the DCI that triggers the non-periodic SRS transmission may be necessary so that the UE sends the SRS by applying the configuration information about the SRS resources. The time interval for the SRS transmission of the UE can be defined as the number of symbols between the last symbol of the PDCCH including the DCI that triggers the non-periodic SRS transmission and the first symbol of the first transmitted SRS resource mapped to the transmitted (multiple) SRS resources. The minimum time interval can be determined with reference to the PUSCH preparation process time required for the UE to prepare for PUSCH transmission. Depending on the location of use of the SRS resource set including the transmitted SRS resources, the minimum time interval can have different values. For example, the minimum time interval can be determined as N2 symbols defined in view of the UE processing capability of the UE capability following the PUSCH preparation process time of the reference UE. In addition, if the usage location 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 location 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 UE may transmit the non-periodic SRS, and if the time interval for non-periodic SRS transmission is less than the minimum time interval, the DCI triggering the non-periodic SRS may be ignored.

[0450] [Table 36]

[0451]

[0452]

[0453]

[0454] The configuration information spatialRelationInfo in Table 36 above may refer to one reference signal and be applied to a beam for SRS transmission corresponding to beam information of a corresponding reference signal. For example, the configuration of spatialRelationInfo may include information as shown in Table 37 below.

[0455] [Table 37]

[0456]

[0457] Referring to the above-mentioned 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 upper layer signaling referenceSignal corresponds to the configuration information indicating which reference signal's beam information is to be referenced for corresponding SRS transmission, ssb-Index refers to the index of the SS / PBCH block, csi-RS-Index refers to the index of the CSI-RS, and srs refers to the index of the SRS. If the configuration value of the upper layer signaling referenceSignal is "ssb-Index", the UE may apply the receive beam used to receive the SS / PBCH block corresponding to the ssb-Index as the transmit beam for the corresponding SRS transmission. If the configuration value of the upper layer signaling referenceSignal is "csi-RS-Index", the UE may apply the receive beam used to receive the CSI-RS corresponding to the csi-RS-Index as the transmit beam for the corresponding SRS transmission. If the configuration value of the higher-layer signaling referenceSignal is "srs", the UE can apply the reception beam used to transmit the SRS corresponding to the srs as the transmission beam for the corresponding SRS transmission.

[0458] [PUSCH: About transmission scheme]

[0459] Next, the PUSCH transmission scheduling scheme will be described. PUSCH transmission can be dynamically scheduled by UL grant in DCI, or operated by configuring grant type 1 or type 2. Dynamic scheduling indication on PUSCH transmission can be made by DCI format 0_0 or 0_1.

[0460] Configured Grant Type 1 PUSCH transmissions may be semi-statically configured by receiving a configuredGrantConfig including the rrc-ConfiguredUplinkGrant in Table 16 via upper layer signaling without receiving an UL grant within the DCI. Configured Grant Type 2 PUSCH transmissions may be semi-persistently scheduled by an UL grant within the DCI after receiving a configuredGrantConfig not including the rrc-ConfiguredUplinkGrant in Table 16 via upper layer signaling. If the PUSCH transmission operates via a configured grant, the parameters applied to the PUSCH transmission are applied via configuredGrantConfig (upper layer signaling) in Table 38, except for the scaling of dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, and UCI-OnPUSCH provided by pusch-Config (upper layer signaling) in Table 39. If transformPrecoder is provided in configuredGrantConfig (upper layer signaling) in Table 38, the UE applies tp-pi2BPSK in pusch-Config in Table 39 to PUSCH transmissions operated by the configured grant.

[0461] [Table 38]

[0462]

[0463]

[0464]

[0465]

[0466] Next, the PUSCH transmission method will be 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 (upper layer signaling) in Table 39 is "codebook" or "nonCodebook", PUSCH transmission can follow the codebook-based transmission method and the non-codebook-based transmission method.

[0467] Codebook-based PUSCH transmission can be dynamically scheduled through DCI format 0_0 or 0_1, and can be semi-statically configured by configuring the grant. Upon receiving an indication of scheduling of PUSCH transmission through DCI format 0_0, the UE performs beam configuration for PUSCH transmission by using the pucch-spatialRelationInfoID corresponding to the UE-specific PUCCH resource corresponding to the minimum ID within the uplink BWP activated within the serving cell, and the PUSCH transmission is based on a single antenna port. The UE does not expect scheduling of PUSCH transmission through DCI format 0_0 within a BWP where PUCCH resources including pucch-spatialRelationInfo are not configured. If the UE does not configure txConfig within pusch-Config in Table 39, the UE does not expect scheduling through DCI format 0_1.

[0468] [Table 39]

[0469]

[0470]

[0471] In the following, codebook-based PUSCH transmission will be described. Codebook-based PUSCH transmission can be dynamically scheduled through DCI format 0_0 or 0_1, and can be operated semi-statically by configuring the grant. If the codebook-based PUSCH is dynamically scheduled through DCI format 0_1, or semi-statically configured by configuring the grant, the UE determines the precoder for PUSCH transmission based on the SRS resource indicator (SRI), the transmission precoding matrix indicator (TPMI) and the transmission rank (number of PUSCH transmission layers).

[0472] SRI can be given by the SRS resource indicator (field in DCI) or configured by srs-ResourceIndicator (upper layer signaling). During codebook-based PUSCH transmission, the UE has at least one SRS resource configured for it and can have up to two SRS resources configured for it. If SRI is provided to the UE through DCI, the SRS resource indicated by the corresponding SRI refers to the SRS resource corresponding to the SRI among the SRS resources sent before the PDCCH including the corresponding SRI. In addition, TPMI and transmission rank can be given by "precoding information and number of layers" (field in DCI) or configured by precodingAndNumberOfLayers (upper layer signaling). TPMI is used to indicate the precoder to be applied to PUSCH transmission. If one SRS resource is configured for the UE, TPMI can be used to indicate the precoder to be applied in one configured SRS resource. If multiple SRS resources are configured for the UE, TPMI is used to indicate the precoder to be applied in the SRS resource indicated by SRI.

[0473] The precoder to be used for PUSCH transmission is selected from an uplink codebook with the same number of antenna ports as the value of nrofSRS-Ports in SRS-Config (upper layer signaling). In conjunction with codebook based PUSCH transmission, the UE determines the codebook subset based on codebookSubset and TPMI in pusch-Config (upper layer signaling). Based on the UE capabilities reported by the UE to the base station, codebookSubset in pusch-Config (upper layer signaling) can be configured as one of "fullyAndPartialAndNonCoherent", "partialAndNonCoherent" or "noncoherent". If the UE reports "partialAndNonCoherent" as the UE capability, the UE does not expect the value of codebookSubset (upper layer signaling) to be configured as "fullyAndPartialAndNonCoherent". In addition, if the UE reports "noncoherent" as a UE capability, the UE does not expect the value of codebookSubset (upper layer signaling) to be configured as "fullyAndPartialAndNonCoherent" or "partialAndNonCoherent". If nrofSRS-Ports in SRS-ResourceSet (upper layer signaling) indicates two SRS antenna ports, the UE does not expect the value of codebookSubset (upper layer signaling) to be configured as "partialAndNonCoherent".

[0474] The UE may have one SRS resource set configured for it, where the value of usage in SRS-ResourceSet (upper layer signaling) is "codebook", and one SRS resource may be indicated by the SRI in the corresponding SRS resource set. If multiple SRS resources are configured in an SRS resource set, where the value of usage in SRS-ResourceSet (upper layer signaling) is "codebook", the UE expects the value of nrofSRS-Ports in SRS-Resource (upper layer signaling) to be the same for all SRS resources.

[0475] The UE sends one or more SRS resources included in the SRS resource set to the base station, where the usage value is configured as "codebook" according to upper layer signaling, and the base station selects an SRS resource from the SRS resources sent by the UE and indicates that the UE can send PUSCH by using the transmit beam information of the corresponding SRS resource. In conjunction with codebook-based PUSCH transmission, SRI is used as information for selecting an index of an SRS resource and is included in the DCI. In addition, the base station adds information to the DCI indicating the rank and TPMI to be used by the UE for PUSCH transmission. Using the SRS resource indicated by SRI, the UE applies the precoder indicated by the rank and the TPMI indicated based on the transmit beam of the corresponding SRS resource when performing PUSCH transmission, thereby performing PUSCH transmission.

[0476] Next, non-codebook based PUSCH transmission will be described. Non-codebook based PUSCH transmission can be dynamically scheduled through DCI format 0_0 or 0_1, and can be operated semi-statically by configuring the grant. If at least one SRS resource is configured in the SRS resource set, where the usage value in SRS-ResourceSet (upper layer signaling) is "nonCodebook", non-codebook based PUSCH transmission can be scheduled for the UE through DCI format 0_1.

[0477] For an SRS resource set where the value of usage in the SRS-ResourceSet (upper layer signaling) is "nonCodebook", a connected NZP CSI-RS resource (non-zero power CSI-RS) may be configured for the UE. The UE may calculate the precoder for SRS transmission by measuring 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 UE is less than 42 symbols, the UE does not expect that the information about the precoder for SRS transmission will be updated.

[0478] If the configured value of resourceType within SRS-ResourceSet (upper layer signaling) is "aperiodic", the connected NZP CSI-RS is indicated by an SRS request as a field within DCI format 0_1 ​​or 1_1. If the connected NZP CSI-RS resource is an aperiodic NZP CSI-RS resource, the presence of the connected NZP CSI-RS is indicated for the case where the value of the SRS request (field within DCI format 0_1 ​​or 1_1) is not "00". The corresponding DCI should not indicate cross-carrier or cross-BWP scheduling. In addition, if the value of the SRS request indicates the presence of NZP CSI-RS, the NZP CSI-RS is located in the time slot used to send the PDCCH including the SRS request field. In this case, the TCI state configured for the scheduled subcarrier is not configured as QCL-TypeD.

[0479] If a periodic or semi-persistent SRS resource set is configured, the connected NZP CSI-RS can be indicated by the associatedCSI-RS in the SRS-ResourceSet (upper layer signaling). For non-codebook based transmission, the UE does not expect that the spatialRelationInfo as the upper layer signaling about the SRS resource and the associatedCSI-RS in the SRS-ResourceSet (upper layer signaling) will be configured together.

[0480] If multiple SRS resources are configured for the UE, the UE can determine the precoder and transmission rank to be applied to the PUSCH transmission based on the SRI indicated by the base station. The SRI can be indicated by the SRS resource indicator (field within the DCI) or configured by the srs-ResourceIndicator (upper layer signaling). Similar to the above-mentioned codebook-based PUSCH transmission, if the SRI is provided to the UE through the DCI, the SRS resource indicated by the corresponding SRI refers to the SRS resource corresponding to the SRI among the SRS resources sent before the PDCCH including the corresponding SRI. The UE can use one or more SRS resources for SRS transmission, and the maximum number of SRS resources that can be sent simultaneously in the same symbol within an SRS resource set and the maximum number of SRS resources are determined by the UE capabilities reported by the UE to the base station. The SRS resources sent simultaneously by the UE occupy the same RB. The UE configures an SRS port for each SRS resource. There may be only one configured SRS resource set, where the value of usage in SRS-ResourceSet (upper layer signaling) is "nonCodebook", and up to 4 SRS resources may be configured for non-codebook based PUSCH transmission.

[0481] The base station sends an NZP-CSI-RS connected to an SRS resource set to the UE, and based on the measurement result when receiving the corresponding NZP-CSI-RS, the UE calculates the precoder used when sending one or more SRS resources within the corresponding SRS resource set. The UE applies the precoder calculated when sending one or more SRS resources within the SRS resource set to the base station, where the configured usage is "nonCodebook", and the base station selects one or more SRS resources from the received one or more SRS resources. In conjunction with non-codebook based PUSCH transmission, the SRI can indicate an index that can express an SRS resource or a combination of multiple SRS resources. 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 UE sends the PUSCH by applying the precoder applied to the SRS resource transmission to each layer.

[0482] [PUSCH: Preparation process time]

[0483] Next, the PUSCH preparation process time will be described. If the base station schedules the UE to send PUSCH by using DCI format 0_0, 0_1, or 0_2, the UE may need the PUSCH preparation process time so that the PUSCH is sent by applying the transmission method (SRS resource transmission precoding method, number of transmission layers, spatial transmission filter) indicated via DCI. Taking this into consideration, the PUSCH preparation process time is defined in the NR system. The PUSCH preparation process time of the UE can follow Equation 4 given below.

[0484] [Equation 4]

[0485] T proc,2 =max((N 2 +d 2,1 +d 2 )(2048+144)κ2 -μ T c +T ext +T switch ,d 2,2 )

[0486] T described in Equation 4 above proc,2 Each parameter in can have the following meanings.

[0487] -N 2 : The number of symbols determined according to the UE processing capability 1 or 2 based on the UE capability and the basic parameter set μ. If the UE processing capability 1 is reported according to the UE capability report, then N 2may have the values ​​in Table 40, and if UE processing capability 2 is reported and if the availability of UE processing capability 2 is configured through upper layer signaling, then N 2 It can have the values ​​in Table 41.

[0488] [Table 40]

[0489] μ <![CDATA[PUSCH Preparation Time N 2 [Symbol]]]> 0 10 1 12 2 23 3 36

[0490] [Table 41]

[0491] μ <![CDATA[PUSCH preparation time N 2 [Symbol]]]> 0 5 1 5.5 2 For frequency range 1, 11

[0492] -d 2,1 : If all resource elements of the first OFDM symbol of PUSCH transmission include DM-RS, the symbol number is determined to be 0, otherwise, it is determined to be 1.

[0493] -κ: 64

[0494] -μ: Follow μ DL and μ UL Among them, T proc,2 Larger value. DL refers to a basic parameter set for downlink transmission of a PDCCH including a DCI scheduling a PUSCH, and μ UL Refers to the basic parameter set for uplink transmission of PUSCH.

[0495] -Tc: Δf max =480·10 3 Hz,N f =4096

[0496] -d 2,2 : If the DCI scheduling PUSCH indicates BWP switching, the BWP switching time is followed, otherwise it is 0.

[0497] -d 2 : If OFDM symbols overlap in time between a PUSCH with a high priority index and a PUCCH with a low priority index, the d of the PUSCH with the high priority index is used. 2 Otherwise, d 2 is 0.

[0498] -T ext : If the UE uses a shared spectrum channel access solution, the UE can calculate T ext And apply it to the PUSCH preparation process time. Otherwise, T ext is assumed to be 0.

[0499] -T switch: If the uplink switching interval has been triggered, then T switch is assumed to be the switching interval. Otherwise, T switch is assumed to be 0.

[0500] In view of the influence of the timing advance between uplink and downlink and the time domain resource mapping information of the PUSCH scheduled by DCI, if the first symbol of the PUSCH is earlier than the T from the last symbol of the PDCCH including the DCI scheduling the PUSCH, proc,2 If the first uplink symbol after the CP starts starts earlier, the base station and the UE determine that the PUSCH preparation process time is insufficient. Otherwise, the base station and the UE determine that the PUSCH preparation process time is sufficient. The UE can send PUSCH only when the PUSCH preparation process time is sufficient, and if the PUSCH preparation process time is insufficient, the DCI scheduling PUSCH can be ignored.

[0501] [PUSCH: About repeated transmission]

[0502] Hereinafter, the repeated transmission of the uplink data channel in the 5G system will be described in detail. The 5G system supports two types of methods for repeatedly transmitting the uplink data channel: PUSCH repetition transmission type A and PUSCH repetition transmission type B. One of PUSCH repetition transmission type A and PUSCH repetition transmission type B can be configured for the UE through upper layer signaling.

[0503] PUSCH repetition transmission type A

[0504] -As described above, the symbol length and the position of the starting symbol of the uplink data channel can be determined by the time domain resource allocation method in one time slot, and the base station can notify the UE of the number of repeated transmissions through upper layer signaling (e.g., RRC signaling) or L1 signaling (e.g., DCI).

[0505] -Based on the number of repetition transmissions received from the base station, the UE may repeatedly transmit an uplink data channel having the same length and starting symbol as the configured uplink data channel in consecutive time slots. If the base station configures the time slot as a downlink for the UE, or if at least one symbol of the uplink data channel configured for the UE is configured as a downlink, the UE omits the uplink data channel transmission, but counts the number of repetition transmissions of the uplink data channel.

[0506] PUSCH repetition transmission type B

[0507] -As described above, the symbol length and the position of the starting symbol of the uplink data channel can be determined by the time domain resource allocation method in one time slot, and the base station can notify the UE of the number of repetitions through upper layer signaling (e.g., RRC signaling) or L1 signaling (e.g., DCI).

[0508] Based on the starting symbol and length of the previously configured uplink data channel, the nominal repetition of the uplink data channel is determined as follows. The time slot where the nth nominal repetition starts is determined by is given by , and the symbol starting in this time slot is given by The time slot where the nth nominal repetition ends is given by . is given by , and the symbol ending in this time slot is given by In this regard, n=0, ..., number of repetitions-1, S refers to the starting symbol of the configured uplink data channel, and L refers to the symbol length of the configured uplink data channel. K s is the time slot where PUSCH transmission starts, and Refers to the number of symbols per time slot.

[0509] -UE determines invalid symbols of PUSCH repetition transmission type B. Symbols configured as downlink through tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated are determined as invalid symbols of PUSCH repetition transmission type B. In addition, invalid symbols can be configured in upper layer parameters (e.g., InvalidSymbolPattern). The upper layer parameters (e.g., InvalidSymbolPattern) can provide a symbol level bitmap across one or two time slots to configure invalid symbols. In the bitmap, 1 represents an invalid symbol. In addition, the period and pattern of the bitmap can be configured by the upper layer parameters (e.g., InvalidSymbolPattern). If an upper layer parameter (e.g., InvalidSymbolPattern) is configured, and if the parameter InvalidSymbolPatternIndicator-ForDCIFormat0_1 or InvalidSymbolPatternIndicator-ForDCIFormat0_2 indicates 1, the UE applies an invalid symbol pattern, and if the above parameter indicates 0, the UE does not apply the invalid symbol pattern. If an upper layer parameter (e.g., InvalidSymbolPattern) is configured, and if the parameter InvalidSymbolPatternIndicator-ForDCIFormat0_1 or InvalidSymbolPatternIndicator-ForDCIFormat0_2 is not configured, the UE applies an invalid symbol pattern.

[0510] After determining the invalid symbol, for each nominal repetition, the UE may consider the symbols other than the invalid symbol to be valid symbols. If one or more valid symbols are included in each nominal repetition, the nominal repetition may include one or more actual repetitions. Each actual repetition includes a set of consecutive valid symbols that can be used for PUSCH repetition transmission type B in a time slot.

[0511] Fig.17 An example of PUSCH repetition transmission type B in a wireless communication system according to an embodiment of the present disclosure is shown.

[0512] The UE may receive the following configuration: the start symbol S of the uplink data channel is 0, the length L of the uplink data channel is 14, and the number of repeated transmissions is 16. In this case, the nominal repetition may appear in 16 consecutive time slots (%n). Thereafter, the UE may determine that the symbol configured as the downlink symbol in each nominal repetition 1701 is an invalid symbol. The UE determines that the symbol configured as 1 in the invalid symbol pattern 1702 is an invalid symbol. If valid symbols other than the invalid symbol in each nominal repetition constitute one or more consecutive symbols in one time slot, they are configured as actual repetitions and transmitted (1703).

[0513] For PUSCH repetitive transmission, additional methods for UL grant-based PUSCH transmission across slot boundaries and configuration grant-based PUSCH transmission can be defined in NR Release 16 as follows:

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

[0515] -Method 2 (multi-segment transmission): Two or more PUSCH repetition transmissions are scheduled in consecutive time slots through one UL grant. Transmission 1 can be specified for each time slot, and the starting point or repetition length can be different between each transmission. In method 2, the time domain resource allocation information within the DCI indicates the starting point and repetition length of all repetition transmissions. In the case of performing repetition transmission in a single time slot through method 2, if there are multiple bundles of consecutive uplink symbols in the corresponding time slot, each repetition transmission can be performed for each uplink symbol bundle. If there is a single bundle of consecutive uplink symbols in the corresponding time slot, one PUSCH repetition transmission is performed according to the method of NR version 15.

[0516] - Method 3: Two or more PUSCH repetitive transmissions are scheduled in consecutive time slots by two or more UL grants. Transmission 1 is assigned to each time slot, and the nth UL grant can be received before the PUSCH transmission scheduled by the n-1th UL grant ends.

[0517] -Method 4: One or more PUSCH repetition transmissions within a single time slot, or two or more PUSCH repetition transmissions across the boundaries of consecutive time slots can be supported by one UL grant or one configuration grant. The number of repetitions indicated by the base station to the UE is only a nominal value, and the UE can actually perform more PUSCH repetition transmissions than the nominal number of repetitions. The time domain resource allocation information or configuration grant within the DCI refers to the resources of the first repetition transmission indicated by the base station. The time domain resource information of the remaining repetitions can be determined with reference to the resource information of the first repetition transmission and the uplink or downlink direction of the symbol. If the time domain resource information of the repetition transmission indicated by the base station crosses the time slot boundary or includes an uplink / downlink switching point, the corresponding repetition transmission can be divided into multiple repetition transmissions. For each uplink cycle, one repetition transmission can be included in one time slot.

[0518] [PUSCH: frequency hopping process]

[0519] Hereinafter, frequency hopping of a physical uplink shared channel (PUSCH) in a 5G system will be described in detail.

[0520] For each PUSCH repetition transmission type, 5G supports two PUSCH frequency hopping methods. First, in PUSCH repetition transmission type A, intra-slot frequency hopping and inter-slot frequency hopping are supported, and in PUSCH repetition transmission type B, inter-repetition frequency hopping and inter-slot frequency hopping are supported.

[0521] The intra-slot frequency hopping method supported in PUSCH repetition transmission type A is a method in which the UE transmits the resource in two hops in one slot after changing the resource allocated in the frequency domain according to the configured frequency offset. The starting RB of each hop in conjunction with the intra-slot frequency hopping can be expressed by the following equation 5:

[0522] [Equation 5]

[0523]

[0524] In Equation 5, i=0 and i=1 may represent the first hop and the second hop, respectively, and RB start It can represent the starting RB in the ULBWP and can be calculated according to the frequency resource allocation method. RB offset represents the frequency offset between two hops through upper layer parameters. The number of symbols in the first hop can be determined by is represented by, and the number of symbols in the second hop can be expressed by To express. It is the length of PUSCH transmission in one slot and is expressed by the number of OFDM symbols.

[0525] Next, the inter-slot hopping method supported in PUSCH repetition transmission types A and B is a method in which the UE transmits the resource in each slot after changing the resource allocated in the frequency domain according to the configured frequency offset. The starting RB during the slot combined with the inter-slot hopping can be expressed by the following equation 6.

[0526] [Equation 6]

[0527]

[0528] In equation 6, Indicates the current slot number during multi-slot PUSCH transmission, and RB start Indicates the starting RB within the UL BWP and is calculated according to the frequency resource allocation method. RB offset Indicates the frequency offset between two hops through upper layer parameters.

[0529] The inter-repetition frequency hopping method supported in PUSCH repetition transmission type B may be one in which resources allocated in the frequency domain for one or more actual repetitions in each nominal repetition are moved and then transmitted according to the configured frequency offset. The index RB in the frequency domain of the starting RB for one or more actual repetitions in the nth nominal repetition start (n) can follow the equation 7 given below:

[0530] [Equation 7]

[0531]

[0532] In Equation 7, n represents the index of the nominal repetition, and RB offset Indicates the RB offset between two hops through upper layer parameters.

[0533] [About UE Capability Report]

[0534] In LTE and NR, the UE may perform a process in which the UE reports capabilities supported by the UE to the corresponding base station while being connected to the serving base station. In the following description, the above process will be referred to as UE capability reporting.

[0535] The base station may transmit a UE capability query message to a UE in a connected state to request a capability report. The message may include a UE capability request for each radio access technology (RAT) type of the base station. The RAT type specific request may include supported frequency band combination information, etc. In addition, in the case of a UE capability query message, UE capabilities for multiple RAT types may be requested by an RRC message container sent by the base station, or the base station may transmit a UE capability query message including multiple UE capability requests for each RAT type. That is, the capability query may be repeated multiple times in one message, and the UE may configure a UE capability information message corresponding thereto and report the message multiple times. In the next generation mobile communication system, a UE capability request for multi-RAT dual connectivity (MR-DC) may be made, such as NR, LTE, and E-UTRA-NR dual connectivity (EN-DC). In general, the UE capability query message may initially be sent after the UE is connected to the base station, but if the base station requires, it may be requested under any conditions.

[0536] When receiving the UE capability report request from the base station in the above steps, the UE configures the UE capability according to the frequency band information and RAT type requested by the base station. The method for UE to configure UE capability in the NR system is summarized as follows.

[0537] 1. If the UE receives a list of LTE and / or NR bands from the base station in response to a UE capability request, the UE constructs a band combination (BC) for EN-DC and NR standalone (SA). That is, the UE configures a BC candidate list for EN-DC and NR SA based on the bands received from the base station via a request of FreqBandList. The bands have priorities in the order described in FreqBandList.

[0538] 2. If the base station sets the "eutra-nr-only" flag or the "eutra" flag and requests UE capability reporting, the UE removes everything related to NR SA BC from the configured BC candidate list. This operation can only happen if the LTE base station (eNB) requests the "eutra" capability.

[0539] 3. The UE then removes the fallback BC from the BC candidate list configured in the above steps. As used herein, a fallback BC refers to a BC that can be obtained by removing the frequency band corresponding to at least one SCell from a specific BC, and since the BC before removing the frequency band corresponding to at least one SCell can already cover the fallback BC, the fallback BC can be omitted. This step also applies to MR-DC, that is, also to LTE bands. The remaining BCs after the above steps constitute the final "candidate BC list".

[0540] 4. The UE selects a BC suitable for the requested RAT type from the final "candidate BC list" and configures the BC to be reported. In this step, the UE configures the supportedBandCombinationList in a determined order. That is, the UE configures the BC to be reported and the UE capabilities according to the preconfigured rat-Type order (nr->eutra-nr->eutra). In addition, the UE configures the featureSetCombination about the configured supportedBandCombinationList, and configures a list of "candidate feature set combinations" based on the candidate BC list from which the list about fallback BC (including capabilities of the same or lower steps) is removed. The "candidate feature set combination" may include all feature set combinations about NR and EUTRA-NR BCs, and may be obtained from the feature set combinations of the containers UE-NR-Capabilities and UE-MRDC-Capabilities.

[0541] 5. If the requested RAT type is eutra-nr and has an impact, featureSetCombinations are included on both containers UE-MRDC-Capabilities and UE-NR-Capabilities. However, feature sets for NR are only included in UE-NR-Capabilities.

[0542] After configuring the UE capabilities, the UE transfers a UE capability information message including the UE capabilities to the base station. The base station performs scheduling and transmission / reception management suitable for the UE based on the UE capabilities received from the UE.

[0543] [About CA / DC]

[0544] Fig.18 The radio protocol structures of a base station and a UE in single cell, carrier aggregation and dual connectivity scenarios according to an embodiment of the present disclosure are shown.

[0545] See also Fig.18The radio protocol of the mobile communication system includes NR Service Data Adaptation Protocol (SDAP) S25 or S70, NR Packet Data Convergence Protocol (PDCP) S30 or S65, NR Radio Link Control (RLC) S35 or S60, and NR Medium Access Control (MAC) S40 or S55 on both the UE side and the NR base station side.

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

[0547] -Transmission of user plane data

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

[0549] - Mark QoS flow ID in both DL and UL packets

[0550] -Reflective QoS flow to DRB mapping for UL SDAP PDU

[0551] For SDAP layer devices, the UE can be configured through RRC messages, for each PDCP layer device or each bearer or each logical channel, whether to use the header of the SDAP layer device or whether to use the function of the SDAP layer device, and if the SDAP header is configured, the non-access layer (NAS) QoS reflection configuration 1-bit indicator (NAS reflection QoS) and AS QoS reflection configuration 1-bit indicator (AS reflection QoS) of the SDAP header can be indicated, so that the UE can update or reconfigure the mapping information of the QoS flow and data bearer for 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., for smoothly supporting services.

[0552] The main functions of NR PDCP S30 or S65 may include the following functions.

[0553] -Header compression and decompression: ROHC only

[0554] -Transfer of user data

[0555] - Ordered delivery of upper layer PDUs

[0556] - Out-of-order delivery of upper layer PDUs

[0557] - Reordering of received PDCP PDUs

[0558] - Duplicate detection of lower layer SDU

[0559] -Retransmission of PDCP SDU

[0560] -Encryption and decryption

[0561] - Timer-based SDU discard in uplink

[0562] The above-mentioned reordering of the NR PDCP device refers to a function of reordering the PDCP PDUs received from the lower layer in an order based on the PDCP sequence number (SN), and may include a function of delivering data to the upper layer in the reordered order. Alternatively, the reordering of the NR PDCP device may include a function of delivering data immediately without considering the order, may include a function of recording the PDCP PDUs lost due to the reordering, may include a function of reporting the status of the lost PDCP PDUs to the transmitting side, and may include a function of requesting retransmission of the lost PDCP PDUs.

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

[0564] - Delivery of upper layer PDU

[0565] - Ordered delivery of upper layer PDUs

[0566] - Out-of-order delivery of upper layer PDUs

[0567] - Error correction via ARQ

[0568] - Concatenation, segmentation and reassembly of RLC SDU

[0569] - Re-segmentation of RLC data PDUs

[0570] - Reordering of RLC data PDUs

[0571] - Duplicate detection

[0572] -Protocol error detection

[0573] -RLC SDU discarded

[0574] -RLC reconstruction

[0575] The above-mentioned ordered delivery of the NR RLC device refers to a function of delivering the RLC SDU received from the lower layer to the upper layer in sequence. The ordered delivery of the NR RLC device may include a function of reassembling the RLC SDU and delivering the reassembled RLC SDU when one original RLC SDU is segmented into multiple RLC SDUs and the segmented RLC SDUs are received, may include a function of reordering the received RLC PDU with reference to the RLC sequence number (SN) or the PDCP sequence number (SN), may include a function of recording the RLC PDU lost due to the reordering, 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 ordered delivery of the NR RLC device may include a function of delivering only the RLC SDUs before the lost RLC SDU to the upper layer in succession in the presence of a lost RLC SDU, and may include a function of delivering all RLC SDUs received before the timer starts to the upper layer in succession in the presence of a lost RLC SDU, and may include a function of delivering all RLC SDUs received before the timer starts to the upper layer in succession in the presence of a lost RLC SDU but a predetermined timer has expired despite the presence of a lost RLC SDU. Alternatively, the in-order delivery of the NR RLC device may include a function of delivering all RLC SDUs received until now to the upper layer in succession in a case where a predetermined timer has expired despite the existence of lost RLC SDUs. In addition, the in-order delivery of the NR RLC device may include a function of processing the RLC PDUs in the order of reception (regardless of the sequence number order, in the order of arrival) and delivering them to the PDCP device regardless of the order (out-of-order delivery), and may include a function of receiving segments stored in a buffer or segments to be received later in the case of segmentation, reconfiguring them into a complete RLC PDU, processing them and delivering them to the PDCP device. The NR RLC layer may not include a cascading function, which may be performed in the NR MAC layer or replaced by a multiplexing function of the NR MAC layer.

[0576] The above-mentioned out-of-order delivery of the NR RLC device refers to the function of immediately delivering the RLC SDU received from the lower layer to the upper layer regardless of the order, which may include the function of reassembling and delivering them when multiple RLC SDUs are received (one of which the original RLC SDU has been segmented into multiple SDUs), and may include the function of storing the RLC SN or PDCP SN of the received RLC PDU and recording the RLC PDU lost due to reordering.

[0577] NR MAC S40 or S55 can be connected to multiple NR RLC layer devices configured in one UE, and the main functions of NR MAC may include some of the following functions.

[0578] - Mapping between logical channels and transport channels

[0579] -Multiplexing / demultiplexing of MAC SDU

[0580] -Dispatch information report

[0581] - Error correction through HARQ

[0582] - Priority handling between logical channels of a UE

[0583] - Priority handling between UEs with the help of dynamic scheduling

[0584] -MBMS service logo

[0585] -Transmission format selection

[0586] -filling

[0587] The NR PHY layer S45 or S50 may perform operations of channel coding and modulating the upper layer data to obtain OFDM symbols and deliver them through a radio channel, or demodulate the OFDM symbols received through the radio channel, channel-decode them, and deliver them to the upper layer.

[0588] The detailed structure of the radio protocol structure may change differently depending on the carrier (or cell) operation scheme. For example, in the case where the base station sends data to the UE based on a single carrier (or cell), the base station and the UE may use a protocol structure having a single structure for each layer, such as S00. On the other hand, in the case where the base station sends data to the UE based on carrier aggregation (CA) using multiple carriers in a single TRP, the base station and the UE may use a protocol structure having a single structure up to the RLC but multiplexing the PHY layer through the MAC layer, such as S10. As another example, in the case where the base station sends data to the UE based on dual connectivity (DC) using multiple carriers in multiple TRPs, the base station and the UE may use a protocol structure having a single structure up to the RLC but multiplexing the PHY layer through the MAC layer, such as S20.

[0589] [Related to NC-JT (non-coherent joint transmission)]

[0590] According to an embodiment of the present disclosure, non-coherent joint transmission (NC-JT) can be used to enable a UE to receive PDSCH from multiple TRPs.

[0591] Unlike conventional systems, 5G wireless communication systems can support not only services that require high data 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 receive points (TRPs) or beams, collaborative communication (coordinated transmission) between cells, TRPs and / or beams can increase the strength of the signal received by the UE, or efficiently perform interference control between cells, TRPs and / or beams to meet various service requirements.

[0592] Joint transmission (JT) is a representative transmission technology for the above-mentioned cooperative communication, and in this technology, a signal is sent to one UE through multiple different cells, TRPs and / or beams in order to improve the processing rate or strength of the signal received by the UE. The channels between the cells, TRPs and / or beams and the UE may differ greatly in their characteristics. In particular, in the case of supporting non-coherent joint transmission (NC-JT) with non-coherent precoding between cells, TRPs and / or beams, separate precoding, MCS, resource allocation and TCI indication may be required according to the channel characteristics of each link between the UE and the cell, TRP and / or beam.

[0593] The above-mentioned NC-JT can be applied to at least one of the downlink data channel (physical downlink shared channel PDSCH), the downlink control channel (physical downlink control channel PDCCH), the uplink data channel (physical uplink shared channel PUSCH) and the uplink control channel (physical uplink control channel PUCCH). During PDSCH transmission, transmission information (such as precoding, MCS, resource allocation and TCI) is indicated by DL DCI, and the transmission information needs to be indicated independently for each cell, TRP and / or beam used for NC-JT. This is the main reason for increasing the payload required for DL ​​DCI transmission, and may adversely affect the reception performance of the PDCCH that sends 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 reception performance of the control information.

[0594] Fig.19 is a diagram showing an example of antenna port configuration and resource allocation for transmitting a PDSCH by using cooperative communication in a wireless communication system according to an embodiment of the present disclosure.

[0595] See also Fig.19 , examples of PDSCH transmission are described for each joint transmission (JT) technique, and an embodiment of allocating wireless resources for each TRP is shown.

[0596] See also Fig.19, showing an example N000 of coherent joint transmission (C-JT) supporting inter-cell, TRP and / or beam interfering coding.

[0597] In the case of C-JT, TRP A N005 and TRP B N010 send a single data (PDSCH) to UE N015, and multiple TRPs can perform joint precoding. This can imply sending DMRS through the same DMRS port to allow TRP AN005 and TRP B N010 to send the same PDSCH. For example, both TRP AN 005 and TRP B N010 can send DMRS to the UE through DMRS port A and DMRS B. In this case, the UE can receive a piece of DCI information for receiving a PDSCH demodulated based on the DMRS sent through DMRS port A and DMRS B.

[0598] Fig.19 Example N020 is shown of non-coherent joint transmission (NC-JT) supporting non-coherent intercoding between cells, TRPs and / or beams for PDSCH transmission.

[0599] In the case of NC-JT, each cell, TRP and / or beam sends PDSCH to UE N035, and a separate precoding can be applied to each PDSCH. Each cell, TRP and / or beam can send different PDSCHs or different PDSCH layers to the UE to improve the processing rate compared to a single cell, TRP and / or beam transmission. In addition, each cell, TRP and / or beam can repeatedly send the same PDSCH to the UE to improve reliability compared to a single cell, TRP and / or beam transmission. For ease of explanation, in the following, cells, TRPs and / or beams are collectively referred to as TRPs.

[0600] Various wireless resource allocations may be considered, such as in case N040 where the time-frequency resources used in multiple TRPs for PDSCH transmission are the same, in case N045 where the time-frequency resources used in multiple TRPs do not overlap at all, and in case N050 where some time-frequency resources used in multiple TRPs overlap.

[0601] For NC-JT support, multiple DCIs with various types, structures, and relationships can be considered to simultaneously allocate multiple PDSCHs to one UE.

[0602] Fig. 20is a diagram showing a configuration example of downlink control information (DCI) for NC-JT in a wireless communication system according to an embodiment of the present disclosure, wherein each TRP sends a different PDSCH or a different PDSCH layer to the UE.

[0603] See also Fig. 20 , Case #1N100 is an example in which, in a case where different N-1 PDSCHs are sent from N-1 TRPs (TRP#1 to TRP#(N-1)) additionally added in addition to the serving TRP (TRP#0) used in a single PDSCH transmission, control information for the PDSCH sent from the additional N-1 TRPs is sent independently of the control information for the PDSCH sent from the serving TRP. That is, the UE can obtain control information for the PDSCH sent from different TRPs (TRP#0 to TRP#(N-1)) through multiple independent DCIs (DCI#0 to DCI#(N-1)). The formats of the multiple independent DCIs may be the same as or different from each other, and the payloads of the multiple DCIs may also be the same as or different from each other. In the above case #1, free control or allocation of each PDSCH can be fully ensured, but when multiple DCIs are sent from different TRPs, differences occur in coverage between the multiple DCIs, and thus reception performance may be degraded.

[0604] Case #2N105 shows an example in which, in a situation where different N-1 PDSCHs are transmitted from N-1 TRPs (TRP#1 to TRP#(N-1)) attached in addition to the serving TRP (TRP#0) used in single PDSCH transmission, multiple control information (DCI) for the PDSCHs of the attached N-1 TRPs are respectively transmitted, and each DCI depends on the control information for the PDSCH transmitted from the serving TRP.

[0605] For example, DCI#0, which is control information for a PDSCH transmitted from a serving TRP (TRP#0), includes all information elements of DCI format 1_0, DCI format 1_1, or DCI format 1_2, but shortened DCI (hereinafter referred to as sDCI) (sDCI#0 to sDCI#(N-2)), which is control information for each PDSCH transmitted from a collaborative TRP (TRP#1 to TRP#(N-1)), may include only some information elements of DCI format 1_0, DCI format 1_1, or DCI format 1. Therefore, the sDCI that transmits control information for a PDSCH transmitted from a collaborative TRP has a smaller payload than a normal DCI (nDCI) that transmits control information related to a PDSCH transmitted from a serving TRP, and is therefore able to include a reserved bit compared to the nDCI.

[0606] In the above case #2, the free control or allocation of each PDSCH can be limited according to the content of the information elements included in the sDCI, but the reception performance of sDCI is better than nDCI, so the probability of coverage differences between multiple DCIs can be reduced.

[0607] Case #3N110 shows an example in which, in a situation where different N-1 PDSCHs are sent from N-1 TRPs (TRP#1 to TRP#(N-1)) attached in addition to the serving TRP (TRP#0) used in a single PDSCH transmission, control information for the PDSCH of the attached N-1 TRPs is sent, and this DCI depends on the control information for the PDSCH sent from the serving TRP.

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

[0609] Case #3N110 is an example in which the free control or allocation of each PDSCH can be limited according to the content of the information elements included in the sDCI, but the reception performance of the sDCI is controllable and the complexity of the UE's DCI blind decoding can be reduced compared to case #1N100 or case #2N105.

[0610] Case #4N115 is an example in which, in a case where different N-1 PDSCHs are transmitted from N-1 TRPs (TRP#1 to TRP#(N-1)) additionally provided in addition to the serving TRP (TRP#0) used in a single PDSCH transmission, control information for the PDSCH transmitted from the additional N-1 TRPs is transmitted through the same DCI (long DCI) as the control information for the PDSCH transmitted from the serving TRP. That is, the UE can obtain control information for the PDSCH transmitted from different TRPs (TRP#0 to TRP#(N-1)) through a single DCI. In the case of case #4N115, the complexity of the UE's DCI blind decoding may not increase, but the PDSCH may not be as freely controlled or allocated as when the number of collaborative TRPs is limited due to the limitation of the long DCI payload.

[0611] In the following description and embodiments, sDCI may be referred to as individual spare DCIs, such as shortened DCI, auxiliary DCI or normal DCI (DCI format 1_0 or 1_1 mentioned above), including PDSCH control information sent from the collaborative TRP, and if there is no particularly explicit restriction, the corresponding description applies similarly to each spare DCI.

[0612] In the following description and embodiments, the above-mentioned case #1N100, case #2N105, and case #3N110 in which one or more DCIs (PDCCHs) are used for NC-JT support are classified as multi-PDCCH-based NC-JT, and the above-mentioned case #4N115 in which a single DCI (PDCCH) is used for NC-JT support can be classified as single-PDCCH-based NC-JT. In multi-PDCCH-based PDSCH transmission, the CORESET of the DCI that schedules the service TRP (TRP#0) can be distinguished from the CORESET of the DCI that schedules the collaborative TRP (TRP#1 to TRP#(N-1)). As a method for distinguishing the CORESETs, there may be a method of distinguishing using a high-layer indicator for each CORESET, or a method of distinguishing using a beam configuration for each CORESET. In addition, in single-PDCCH-based NC-JT, a single DCI schedules a single PDSCH with multiple layers, instead of scheduling multiple PDSCHs, and multiple layers can be sent from multiple TRPs. The connection relationship between a layer and the TRP that sends the layer can be indicated by a transmission configuration indicator (TCI) indication for the layer.

[0613] In the embodiments of the present disclosure, when actually applied, "collaborative TRP" may be replaced by various terms including "collaborative panel" or "collaborative beam".

[0614] In the embodiments of the present disclosure, "a case where NC-JT is applied" may be interpreted differently according to the following scenarios: "a case where the UE simultaneously receives one or more PDSCHs in one BWP", "a case where the UE simultaneously receives PDSCHs in one BWP based on two or more transmission configuration indicator (TCI) indications", and "a case where the PDSCH received by the UE is associated with one or more DMRS port groups". However, for ease of explanation, one expression is used.

[0615] In the present disclosure, the wireless protocol structure for NC-JT can be used differently according to the TRP-based scenario. For example, if there is no backhaul delay or the backhaul delay is small between the cooperative TRPs, Fig.18 The structure S10 in FIG. 1 similarly uses a method based on a MAC layer multiplexing structure (similar to the CA method). In contrast, if the return delay between the cooperative TRPs is large enough to be non-negligible (for example, it takes 2 ms or more to exchange information such as CSI, scheduling, or HARQ-ACK between the cooperative TRPs), it can be used with Fig.18 Structure S20 in similarly uses a method of TRP-specific independent structure from the RLC layer (similar to the DC method) to ensure delay-resistant characteristics.

[0616] A UE supporting C-JT / NC-JT can receive parameters or setting values ​​related to C-JT / NC-JT from a high-level configuration, and set the UE's RRC parameters based on the same parameters or setting values. The UE can use UE capability parameters (e.g., tci-StatePDSCH) for high-level configuration. The UE capability parameters (e.g., tci-StatePDSCH) can define TCI states for the purpose of PDSCH transmission, and the number of TCI states can be configured as 4, 8, 16, 32, 64, or 128 in FR 1, and as 64 and 128 in FR 2, and a maximum of 8 states of the configured number of TCI states indicated by 3 bits of the TCI field of the DCI can be configured through a MAC CE message. The maximum value of 128 means the value indicated by the maxNumberConfiguredTCIstatesPerCC in the tci-StatePDSCH parameter included in the UE's capability signaling. As described above, a series of configuration processes from high-level configuration to MAC CE configuration can be applied to beamforming indication or beamforming change command for at least one PDSCH from one TRP.

[0617] [Multiple TRPs based on multiple DCIs]

[0618] 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, the downlink control channel for NC-JT can be configured based on multiple PDCCHs.

[0619] In multi-PDCCH based NC-JT, when DCI for PDSCH scheduling of each TRP is transmitted, a CORESET or search space distinguished by each TRP may be provided. The CORESET or search space of each TRP may be configured as at least one of the following cases.

[0620] *Configuration of high-layer index for each CORESET: The CORESET configuration information configured by the high layer may include an index value, and the index value configured for each CORESET may be used to distinguish the TRP that sends the PDCCH in the corresponding CORESET. That is, in a set of CORESETs with the same high-layer index value, the same TRP may be considered to send the PDCCH or schedule the PDCCH of the PDSCH of the same TRP. The index of each CORESET may be referred to as CORESETPoolIndex, and the PDCCH may be considered to be sent from the same TRP in the CORESET configured with the same CORESETPoolIndex value. For a CORESET for which a CORESETPoolIndex value is not configured, a default CORESETPoolIndex value may be considered to be configured, and the default value may be 0.

[0621] -In the present disclosure, if the number of CORESETPoolIndex types of multiple CORESETs included in the high-level signaling PDCCH-Config exceeds 1, that is, if each CORESET has a different CORESETPoolIndex value, the UE may consider that the base station is capable of using a multi-TRP transmission method based on multi-DCI.

[0622] -On the contrary, in the present disclosure, if the number of CORESETPoolIndex types of multiple CORESETs included in the high-level signaling PDCCH-Config is 1, that is, if all CORESETs have the same CORESETPoolIndex value (such as 0 or 1), the UE can consider that the base station performs transmission by using a single TRP instead of a multi-TRP transmission method based on multi-DCI.

[0623] *Configuration of multiple values ​​of PDCCH-Config: Multiple values ​​of PDCCH-Config are configured in one BWP, and each value of PDCCH-Config may include a TRP-specific PDCCH configuration. That is, a CORESET list for each TRP and / or a search space list for each TRP may be configured in one value of PDCCH-Config, and one or more CORESETs and one or more search spaces included in one value of PDCCH-Config may be considered to correspond to a specific TRP.

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

[0625] *Search space beam / beam group configuration: Beams or beam groups are configured for each search space, and the TRP of each search space can be distinguished by them. For example, if the same beam / beam group or TCI state is configured for multiple search spaces, it can be assumed that the same TRP sends PDCCH in the search space, or the PDCCH scheduling the PDSCH of the same TRP is sent in the search space.

[0626] As described above, the CORESET or search space is distinguished by each TRP, so that the PDSCH and HARQ-ACK information of each TRP can be classified, so that the HARQ-ACK codebook can be generated independently and the PUCCH resources of each TRP can be used independently.

[0627] The configuration may be independent for each cell or each BWP. For example, two different CORESETPoolIndex values ​​may be configured in the PCell, whereas a CORESETPoolIndex value may not be configured in a specific SCell. In this case, it may be assumed that NC-JT is configured in the PCell, but not in the SCell where the CORESETPoolIndex value is not configured.

[0628] The PDSCH TCI state activation / deactivation MAC-CE applicable to the multi-TRP transmission method based on multi-DCI can follow the above Fig.15. If the CORESETPoolIndex of all CORESETs in the higher-layer signaling PDCCH-Config is not configured for the UE, the UE may ignore the CORESET pool ID field 15-55 in the MAC-CE 15-50. If the UE is capable of supporting a multi-TRP transmission method based on multiple DCIs, that is, if the respective CORESETs in the higher-layer signaling PDCCH-Config have different CORESETPoolIndex values, the UE may activate the TCI state in the DCI included in the PDCCH sent in the CORESET having the same CORESETPoolIndex value as the CORESET pool ID field 15-55 in the MAC-CE 15-50. For example, if the value of the CORESET pool ID field 15-55 in the MAC-CE 15-50 is 0, the TCI state of the DCI included in the PDCCH sent from the CORESET whose CORESETPoolIndex is 0 may follow the activation information of the MAC-CE.

[0629] When the UE is configured by the base station to be able to use the multi-TRP transmission method based on multi-DCI, that is, when the number of CORESETPoolIndex types of multiple CORESETs included in the high-level signaling PDCCH-Config exceeds 1, or when each CORESET has a different CORESETPoolIndex value, the UE can recognize that the PDSCH scheduled by the PDCCH in each CORESET with two different CORESETPoolIndex values ​​has the following constraints.

[0630] 1) If the PDSCHs indicated by the PDCCHs in each CORESET with two different CORESETPoolIndex values ​​completely or partially overlap with each other, the UE may apply the TCI states indicated by the PDCCH to different CDM (Code Division Multiplexing) groups, respectively. That is, two or more TCI states may not be applied to one CDM group.

[0631] 2) If the PDSCHs indicated by the PDCCHs in respective CORESETs with two different CORESETPoolIndex values ​​completely or partially overlap with each other, the UE may expect the PDSCHs to have the same number of actual frontload DMRS symbols, the same number of actual additional DMRS symbols, actual DMRS symbols in the same positions, and the same DMRS type.

[0632] 3) The UE may expect that the bandwidth portion indicated by the PDCCH in each CORESET with two different CORESETPoolIndex values ​​is the same, and the subcarrier spacing indicated thereby is also the same.

[0633] 4) The UE may expect that information on the PDSCH scheduled by the PDCCH in each of the CORESETs having two different CORESETPoolIndex values ​​is fully included in the PDCCH.

[0634] [Multiple TRPs based on a single DCI]

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

[0636] In a multi-TRP transmission method based on a single DCI, a PDSCH sent by multiple TRPs can be scheduled by one DCI. As a method of indicating the number of TRPs that send PDSCH, the number of TCI states can be used. That is, if the number of TCI states indicated in the DCI for scheduling PDSCH is 2, the transmission can be considered as NC-JT based on a single PDCCH, and if the number of TCI states is 1, the transmission can be considered as a single TRP transmission. The TCI state indicated in the DCI may correspond to one or two TCI states among the TCI states activated by MAC-CE. If the TCI state of the DCI corresponds to two TCI states activated by MAC-CE, the TCI code point indicated in the DCI and the TCI state activated by MAC-CE may have a corresponding relationship, and this may correspond to the case where the number of TCI states activated by MAC-CE and corresponding to the TCI code point is 2.

[0637] 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 UE may consider that the base station is capable of performing transmission according to a multi-TRP method based on a single DCI. At least one code point indicating two TCI states in the TCI state field may be activated by an enhanced PDSCH TCI state activation / deactivation MAC-CE.

[0638] Fig.21 : is a diagram showing an enhanced PDSCH TCI state activation / deactivation MAC-CE structure. The meaning of each field in the MAC CE and the configurable values ​​in each field are as follows.

[0639] - Serving Cell ID: This field indicates the identity of the serving cell to which the MAC CE applies. The length of this field is 5 bits. If the indicated serving cell is configured as part of simultaneousTCI-UpdateList1 or simultaneousTCI-UpdateList2 as specified in TS 38.331 [5], then this MAC CE applies to all serving cells configured in the simultaneousTCI-UpdateList1 or simultaneousTCI-UpdateList2 respectively;

[0640] - BWP ID: This field indicates the DL BWP to which the MAC CE applies as the codepoint of the DCI Bandwidth Part Indicator field as specified in TS 38.212 [9]. The length of the BWP ID field is 2 bits;

[0641] -C i : This field indicates whether there is a TCI status ID i,2 If this field is set to "1", there is a TCI status ID. i,2 If this field is set to "0", there is no TCI status ID i,2 8-bit byte;

[0642] -TCI Status ID i,j : This field indicates the TCI state identified by TCI-StateId as specified in TS 38.331 [5], where i is the index of the codepoint of the DCI Transmission Configuration Indication field as specified in TS 38.212 [9] and TCI State ID i,j = represents the jth TCI state indicated for the i-th code point in the DCI transmission configuration indication field. The TCI code point to which the TCI state is mapped is determined by its TCI state ID i,j The ordinal position among all TCI code points in the field set is determined, that is, with TCI status ID 0,1 and TCI Status ID 0,2 The first TCI code point will be mapped to code point value 0, with TCI state ID 1,1 and TCI Status ID 1,2 The second TCI code point will be mapped to code point value 1, and so on. Based on the indication of the Ci field, the TCI state ID i,2 The maximum number of activated TCI code points is 8, and the maximum number of TCI states mapped to a TCI code point is 2.

[0643] -R: Reserved bit, set to "0".

[0644] exist Fig.21 If C 0 If the value of field 21-05 is 1, then in addition to the TCI status ID 0,1 In addition to field 21-10, MAC-CE may also include TCI state ID 0,2 Field 21-15. This implies the TCI status ID 0,1 and TCI Status ID 0,2 The 0th code point of the TCI status field included in the DCI is activated, and if the base station indicates this code point to the UE, two TCI states can be indicated to the UE. 0 If the value of field 21-05 is 0, the MAC-CE cannot include the TCI state ID 0,2 Fields 21-15, and this implies the TCI status ID 0,1 A corresponding one TCI state is activated for the 0th code point of the TCI state field included in the DCI.

[0645] The configuration may be independent for each cell or each BWP. For example, the number of activated TCI states corresponding to one TCI code point may be a maximum of 2 in the PCell, but the number of activated TCI states corresponding to one TCI code point may be a maximum of 1 in a specific SCell. In this case, it can be considered that NC-JT is configured in the PCell, but not in the SCell.

[0646] [Multi-TRP PDSCH repetition technology (TDM / FDM / SDM) differentiation method based on single DCI]

[0647] Next, a method for distinguishing between multiple TRP PDSCH repetition techniques based on a single DCI is described. Different single DCI-based multiple TRP PDSCH repetition techniques (e.g., TDM, FDM, and SDM) can be indicated to the UE by the base station based on the DCI field and high-level signaling configuration. Table 42 below shows a method for distinguishing between single-TRP or multi-TRP-based techniques indicated to the UE based on specific DCI field values ​​and high-level signaling configurations.

[0648] [Table 42]

[0649]

[0650]

[0651] In Table 42 above, each column can be described as follows.

[0652] - TCI State Number (second column): This indicates the TCI state number indicated by the TCI State field in the DCI, for example, it can be 1 or 2.

[0653] - Number of CDM groups (third column): This indicates the number of different CDM groups for the DMRS ports indicated by the Antenna Ports field in the DCI. For example, it can be 1, 2 or 3.

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

[0655] ■ Condition 1: At least one of all TDRA entries that may be indicated by the time domain resource allocation field includes a configuration regarding repetitionNumber, and the TDRA entry indicated by the time domain resource allocation field in the DCI includes a configuration regarding a repetitionNumber greater than 1.

[0656] ■ Condition 2: At least one of all TDRA entries that may be indicated by the time domain resource allocation field includes a configuration regarding repetitionNumber, and the TDRA entry indicated by the time domain resource allocation field in the DCI does not include a configuration regarding repetitionNumber.

[0657] ■Condition 3: All TDRA entries indicated by the time domain resource allocation field do not include configuration regarding repetitionNumber.

[0658] - Related to repetitionScheme configuration (fifth column): This indicates whether the higher layer signaling repetitionScheme is configured. As the higher layer signaling repetitionScheme, one of "tdmSchemeA", "fdmSchemeA" and "fdmSchemeB" can be configured.

[0659] -Transmission technology indicated to the UE (sixth column): This indicates the single TRP or multi-TRP technology indicated by the combination (first column) represented in the above [Table 42].

[0660] ■ Single TRP: This indicates a single TRP based PDSCH transmission. If the pdsch-AggegationFactor in the higher layer signaling PDSCH-config is configured for the UE, as many single TRP based PDSCH repetitions as configured may be scheduled for the UE. Otherwise, a single single TRP based PDSCH transmission may be scheduled for the UE.

[0661] ■Single TRP TDM Scheme B: This indicates PDSCH repetition based on inter-slot time resource partitioning based on a single TRP. According to condition 1 related to the above repetitionNumber, the UE repeats PDSCH transmission in the time domain according to the number of time slots equal to the count of repetitionNumber greater than 1 configured in the TDRA entry indicated by the time domain resource allocation field. The UE applies the same starting symbol and the same symbol length of the PDSCH indicated by the TDRA entry to each time slot, the number of time slots is equal to the count of repetitionNumber, and the same TCI state is applied to each PDSCH repetition transmission. This technology is similar to the time slot aggregation scheme in that inter-slot PDSCH repetition transmission is performed in the time resources, but different from time slot aggregation in that whether to indicate repetition transmission can be dynamically determined based on the time domain resource allocation field in the DCI.

[0662] ■Multi-TRP SDM: This means a spatial resource division PDSCH transmission scheme based on multiple TRPs. This is a method of receiving distributed layers from TRPs, not a repetition scheme, but can increase the reliability of PDSCH transmission because the number of layers is increased to achieve lower code rate transmission. The UE can apply the two TCI states indicated by the TCI state field in the DCI to the two CDM groups indicated by the base station respectively in order to receive the PDSCH.

[0663] ■Multi-TRP FDM Scheme A: This means a PDSCH transmission scheme based on frequency resource division of multiple TRPs. This technology provides one PDSCH transmission opportunity, so it is not a repetition like multi-TRP SDM. However, the amount of frequency resources is increased to reduce the code rate, thus achieving high reliability transmission. Multi-TRP FDM Scheme A can apply two TCI states indicated by the TCI state field in the DCI to frequency resources that do not overlap with each other, respectively. In the case where the PRB bundling size is determined as wideband, if the number of RBs indicated by the frequency domain resource allocation field is N, the UE applies the first TCI state to the first ceil(N / 2) RBs and the second TCI state to the remaining floor(N / 2) RBs to perform reception. Here, ceil(.) and floor(.) are operators indicating rounding up and down to a decimal place. If the PRB bundling size is determined to be 2 or 4, the UE applies the first TCI state to the even PRG and the second TCI state to the odd PRG to perform reception.

[0664] ■Multi-TRP FDM Scheme B: This means dividing the PDSCH repetition scheme based on the frequency resources of multiple TRPs, and providing two PDSCH transmission opportunities to repeat PDSCH transmission at each opportunity. In the same way as the multi-TRP FDM scheme A, the multi-TRP FDM scheme B can also apply the two TCI states indicated by the TCI state field in the DCI to the frequency resources that do not overlap with each other. In the case where the PRB bundling size is determined to be wideband, if the number of RBs indicated by the frequency domain resource allocation field is N, the UE applies the first TCI state to the first ceil(N / 2) RBs and the second TCI state to the remaining floor(N / 2) RBs to perform reception. Here, ceil(.) and floor(.) are operators indicating rounding up and down to a decimal place. If the PRB bundling size is determined to be 2 or 4, the UE applies the first TCI state to the even PRG and the second TCI state to the odd PRG to perform reception.

[0665] ■Multi-TRP TDM Scheme A: This means an intra-slot PDSCH repetition transmission scheme based on time resource division of multiple TRPs. The UE can have two PDSCH transmission opportunities in one slot, and can determine the first reception opportunity based on the starting symbol and symbol length of the PDSCH indicated by the time domain resource allocation field in the DCI. The starting symbol of the second reception opportunity of the PDSCH can be a position obtained by applying the symbol offset of the high-level signaling StartingSymbolOffsetK to the last symbol of the first transmission opportunity, and the transmission opportunity can be determined to be as long as the indicated symbol length from this position. If the high-level signaling StartingSymbolOffsetK is not configured, the symbol offset can be considered to be 0.

[0666] ■Multi-TRP TDM Scheme B: This means an inter-slot PDSCH repetition scheme based on time resource division of multiple TRPs. The UE can have one PDSCH transmission opportunity in one slot and receive repetitions based on the same starting symbol and the same symbol length of the PDSCH during multiple slots corresponding to the repetitionNumber indicated by the time domain resource allocation field in the DCI. If the repetitionNumber is 2, the UE can receive PDSCH repetitions in the first slot and the second slot by applying the first TCI state and the second TCI state thereto, respectively. If the repetitionNumber is greater than 2, the UE can use different TCI state application schemes according to which the high-layer signaling tciMapping is configured. If tciMapping is configured as cyclicMapping, the UE applies the first TCI state and the second TCI state to the first PDSCH transmission opportunity and the second PDSCH transmission opportunity, respectively, and also applies the TCI state application method to the remaining PDSCH transmission opportunities in the same manner. If tciMapping is configured as sequentialMapping, the UE applies the first TCI state to the first PDSCH transmission timing and the second PDSCH transmission timing, applies the second TCI state to the third PDSCH transmission timing and the fourth PDSCH transmission timing respectively, and also applies the TCI state application method to the remaining PDSCH transmission timings in the same manner.

[0667] [Related to RLMRS]

[0668] Next, a method for selecting or determining a radio link monitoring reference signal (RLM RS) when RLM RS is configured or not configured is described. The base station can configure an RLM RS set for each downlink bandwidth part of the SpCell of the UE through RadioLinkMonitoringRS in the high-level signaling RadioLinkMonitoringConfig, and the detailed high-level signaling structure can follow the following [Table 43].

[0669] [Table 43]

[0670]

[0671] Table 44 below may represent the configuration of RLM RS for a specific purpose or according to the maximum number of SSBs per half frame (L max ) of the selectable RLM RS number. As shown in Table 44 below, according to L max Value, N LR-RLM RSs can be used for link recovery or radio link monitoring, and N LR-RLM N of RS RLM RSs can be used for radio link monitoring.

[0672] [Table 44]

[0673]

[0674] If the higher layer signaling RadioLinkMonitoringRS has not been configured for the UE, the TCI state for receiving the PDCCH is configured for the UE's control resource set, and the TCI state includes at least one CSI-RS, the UE can select the RLM RS according to the following RLM RS selection method.

[0675] -RLM RS selection method 1): If the activated TCI state to be used for PDCCH reception has one reference RS (i.e., one activated TCI state has only one of QCL-TypeA, QCL-TypeB and QCL-TypeC), the UE can select the reference RS of the activated TCI state to be used for PDCCH reception as the RLM RS.

[0676] -RLM RS selection method 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, QCL-TypeB, and QCL-TypeC, and additionally has QCL-TypeD), the UE may select the reference RS of QCL-TypeD as the RLM RS. The UE may not expect to configure 2 QCL-TypeD for this one activated TCI state.

[0677] - RLM RS selection method 3): The UE is not expected to select an aperiodic or semi-persistent RS as the RLM RS.

[0678] -RLM RS selection method 4): If L max =4, then the UE can select N RLM RS(L max is 4, so 2 RSs can be selected). The selection of the RLM RS is performed among the reference RSs of the TCI state configured for the control resource set for PDCCH reception based on RLM RS selection methods 1 to 3, is determined by giving high priority to the search space having a short period and connected to the control resource set, and is performed for the reference RS starting from the reference RS of the TCI state configured for the control resource set connected to the search space having the shortest period. If there are multiple control resource sets connected to multiple search spaces with the same period, RLM RS selection is performed for the reference RS starting from the reference RS of the TCI state configured for the highest control resource set index.

[0679] Fig. 22is a diagram showing an RLM RS selection process according to an embodiment of the present disclosure. The figure shows control resource sets #1 22-05 to control resource sets #3 22-07 connected to search spaces #1 22-01 to search spaces #4 22-04 with different periods in the activated downlink bandwidth portion, and reference RSs of TCI states configured for each control resource set. Based on the above-mentioned RLM RS selection method 4, RLM RS selection uses the TCI state configured for the control resource set connected to the search space with a shortened period. However, search space #1 22-01 and search space #3 22-03 have the same period, so the reference RS of the TCI state configured for the control resource set #2 with a higher index among the control resource set #1 22-05 and the control resource set #2 22-06 connected to each search space can be used as the highest priority in RLM RS selection. In addition, the TCI state configured for the control resource set #2 has only QCL-TypeA, and the reference RS is a periodic RS, so PCSI-RS#2 22-10 can be first selected as the RLM RS through the above-mentioned RLM RS selection methods 1 and 3. The reference RS of QCL-TypeD among the reference RSs of the TCI state configured for the control resource set #1 with the next priority can be a selection candidate according to the above-mentioned RLM RS selection method 2. However, the RS is a semi-persistent RS (22-09), and thus is not selected as the RLM RS according to the above-mentioned RLM RS selection method 3. Therefore, the reference RS of the TCI state configured for the control resource set #3 can be considered as the next priority, the reference RS of QCL-TypeD can be a selection candidate according to the above-mentioned RLM RS selection method 2, and the reference RS is a periodic RS, so PCSI-RS#4 22-12 can be second selected as the RLM RS through the above-mentioned RLM RS selection method 3. Therefore, the finally selected RLM RSs may be PCSI-RS#2 and PCSI-RS#4 (22-13).

[0680] Hereinafter, for the convenience of description, a cell, a transmission point, a panel, a beam, and / or a transmission direction that can be distinguished by an upper layer / L1 parameter (such as a TCI state or spatial relationship information, a cell ID, a TRP ID, or a panel ID) as a whole may be described as a TRP, a beam, or a TCI state. Therefore, when actually applied, the TRP, the beam, or the TCI state may be appropriately replaced by one of the above terms.

[0681] Hereinafter, in the present disclosure, the UE may use various methods to determine whether collaborative communication is applied, for example, the (multiple) PDCCHs allocated to the PDSCH applied for collaborative communication have a specific format, or the (multiple) PDCCHs allocated to the PDSCH applied for collaborative communication include a specific indicator indicating whether collaborative communication is applied, or the (multiple) PDCCHs allocated to the PDSCH applied for collaborative communication are scrambled by a specific RNTI, or collaborative communication is assumed to be applied in a specific range indicated by an upper layer. Hereinafter, for the sake of convenience of description, it will be assumed that the NC-JT situation refers to a situation in which the UE receives the PDSCH applied for collaborative communication based on conditions similar to the above conditions.

[0682] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. Hereinafter, a base station is an entity that allocates resources to a terminal, and may be at least one of a gNode B, a gNB, an eNode B, a node B, a base station (BS), a radio access unit, a base station controller, or a node on a network. The terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smart phone, a computer, or a multimedia system capable of performing a communication function. In the following description of the embodiments of the present disclosure, a 5G system will be described by way of example, but the embodiments of the present disclosure may also be applied to other communication systems with similar technical backgrounds or channel types. Examples of such communication systems may include LTE or LTE-A mobile communication systems and mobile communication technologies that have developed beyond 5G. Therefore, based on the determination of those skilled in the art, the embodiments of the present disclosure may be applied to other communication systems with some modifications in the case of significantly departing from the scope of the present disclosure. The contents of the present disclosure may be applied to FDD systems and TDD systems. As used herein, upper layer signaling (or high-layer signaling) is a method for transmitting a signal from a base station to a UE by using a downlink data channel of a physical layer or from a UE to a base station by using an uplink data channel of a physical layer, and may also be referred to as "RRC signaling", "PDCP signaling" or "MAC Control Element (MACCE)".

[0683] In addition, when describing the present disclosure, when it is determined that the description may make the subject matter of the present disclosure unnecessarily unclear, a detailed description of known functions or configurations incorporated herein will be omitted. The terms to be described below are defined in consideration of the functions in the present disclosure, and may differ depending on the user, the user's intention or custom. Therefore, the definition of the terms should be based on the content of the entire specification.

[0684] In the following description of the present disclosure, upper layer signaling may refer to signaling corresponding to at least one of the following signalings, or a combination of one or more thereof.

[0685] -Master Information Block (MIB)

[0686] - System Information Block (SIB) or SIB X (X = 1, 2, ...)

[0687] -Radio Resource Control (RRC)

[0688] -Media Access Control (MAC) Control Element (CE)

[0689] In addition, L1 signaling may refer to signaling corresponding to at least one signaling method among signaling methods using the following physical layer channels or signaling, or a combination of one or more thereof.

[0690] - Physical Downlink Control Channel (PDCCH)

[0691] - Downlink Control Information (DCI)

[0692] -UE-specific DCI

[0693] -Group Common DCI

[0694] - Public DCI

[0695] - Scheduling DCI (e.g., DCI for the purpose of scheduling downlink or uplink data)

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

[0697] -Physical Uplink Control Channel (PUCCH)

[0698] - Uplink Control Information (UCI)

[0699] Hereinafter, determining the priority between A and B may be variously described as, for example, selecting an entity with a higher priority and performing an operation corresponding thereto according to a predetermined priority rule, or omitting or discarding an operation on an entity with a lower priority.

[0700] As used herein, the term "time slot" may generally refer to a specific time unit corresponding to a transmission time interval (TTI), and may specifically refer to a time slot used in a 5G NR system, or may refer to a time slot or subframe used in a 4G LTE system.

[0701] Hereinafter, the above-mentioned examples may be described through several embodiments, but they are not independent of each other, and one or more embodiments may be applied simultaneously or in combination.

[0702] <First embodiment: Single TCI state activation and indication method based on unified TCI solution>

[0703] As an embodiment of the present disclosure, a single TCI state indication and activation method based on a unified TCI scheme is described. The unified TCI scheme may mean a scheme for overall management through the TCI state, rather than a transmit / receive beam management scheme that has been classified as a TCI state scheme used in the downlink reception of the UE and a spatial relationship information scheme used in the uplink transmission in conventional versions 15 and 16. Therefore, in the case where the base station indicates the TCI state to the UE, based on the unified TCI scheme, the UE can even perform beam management for uplink transmission by using the TCI state. If the base station configures the UE with a high-layer signaling TCI-State with high-layer signaling tci-stateId-r17, the UE can perform operations based on the unified TCI scheme by using TCI-State. TCI-State may exist in two forms, including a joint TCI state and a separate TCI state.

[0704] The first type is a joint TCI state, and all TCI states applied to uplink transmission and downlink reception can be indicated to the UE by the base station through one TCI-State value. If the TCI-State based on the joint TCI state is indicated to the UE, the parameters to be used in downlink channel estimation can be indicated to the UE by using the RS corresponding to the qcl-Type1 in the TCI-State based on the joint TCI state, and the parameters to be used as a downlink receive beam or receive filter can be indicated to it by using the RS corresponding to qcl-Type2. If the TCI-State based on the joint TCI state is indicated to the UE, the parameters to be used as an uplink transmit beam or transmit filter can be indicated to the UE by using the RS corresponding to the qcl-Type2 in the corresponding TCI-State based on the joint DL / UL TCI state. If the TCI-State based on the joint TCI state is indicated to the UE, the UE can apply the same beam to uplink transmission and downlink reception.

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

[0706] If the DL TCI state and the UL TCI state are indicated to the UE together, the parameters to be used as an uplink transmit beam or a transmit filter may be indicated to the UE by using a reference RS or a source RS configured in the UL TCI state, the parameters to be used in downlink channel estimation may be indicated to the UE by using an RS corresponding to qcl-Type1 configured in the DL TCI state, and the parameters to be used as a downlink receive beam or a receive filter may be indicated to it using an RS corresponding to qcl-Type2. If the respective reference RSs or source RSs configured in the DL TCI state and the UL TCI state indicated to the UE are different from each other, the UE 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.

[0707] Based on the UE capability report, the base station can configure up to 128 joint TCI states for a specific bandwidth part (BWP) in a specific cell of the UE through high-level signaling, and can configure up to 64 or 128 DL TCI states as separate TCI states for a specific bandwidth part in a specific cell through high-level signaling, and the DL TCI states and the joint TCI states in the separate TCI states can use the same high-level signaling structure. For example, if 128 joint TCI states are configured and 64 DL TCI states of the separate TCI states are configured, the 64 DL TCI states can be included in the 128 joint TCI states.

[0708] Based on the UE capability report, up to 32 or 64 UL TCI states as separate TCI states can be configured for a specific bandwidth part in a specific cell through high-layer signaling, and the UL TCI state and the joint TCI state among the separate TCI states can also use the same high-layer signaling structure similar to the relationship between the DL TCI state and the joint TCI state among the separate TCI states, or the UL TCI state among the separate TCI states can also use a different high-layer signaling structure from the joint TCI state and the DL TCI state among the separate TCI states. As described above, based on the UE capability report including information about the usage schemes that the UE can support in two types of usage schemes, the use of different or the same high-layer signaling structures can be defined in the specification, or can be distinguished by another high-layer signaling configured by the base station.

[0709] By using one of the joint TCI state and the separate TCI state configured by the base station, the UE can receive the transmit / receive beam-related indication in the unified TCI scheme. The base station can configure whether to use one of the joint TCI state and the separate TCI state for the UE through high-layer signaling.

[0710] By using a scheme selected from the joint TCI state and the separate TCI state, the UE can receive transmit / receive beam related indications through high-layer signaling, and the transmit / receive beam indication method of the base station can be classified into two types of methods, including a MAC-CE-based indication method and a MAC-CE-based activation and DCI-based indication method.

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

[0712] In the case where the UE is configured to receive a transmit / receive beam related indication via high-layer signaling by using a split TCI state scheme, the UE may receive a MAC-CE indicating a split TCI state from the base station to perform a transmit / receive beam application operation, and the base station may schedule the PDSCH including the MAC-CE for the UE through the PDCCH. If the MAC-CE includes a split TCI state set, the UE may send a PUCCH including HARQ-ACK information indicating whether the reception of the corresponding PDSCH is successful to the base station, and determine an uplink transmit beam or transmit filter and a downlink receive beam or receive filter by using the split TCI state included in the split TCI state set indicated 3 ms after the transmission of the PUCCH. The split TCI state set may indicate a single or multiple split TCI states that a code point of the TCI state field in DCI format 1_1 or 1_2 may have, and a split 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 MAC-CE includes two or more separate TCI state sets, the UE may transmit a PUCCH including HARQ-ACK information indicating whether the reception of the corresponding PDSCH is successful to the base station, identify that the multiple separate TCI state sets indicated by MAC-CE correspond to the respective code points of the TCI state field of DCI format 1_1 or 1_2 after 3ms after the transmission of the PUCCH, and activate the indicated separate TCI state set. Each code point of the TCI state field of DCI format 1_1 or 1_2 may indicate one DL TCI state, one UL TCI state, or one DL TCI state and one UL TCI state. The UE may receive DCI format 1_1 or 1_2 to apply the separate TCI state set indicated by the TCI state field in the DCI to the uplink transmit beam and the downlink receive beam. DCI format 1_1 or 1_2 may include downlink data channel scheduling information (with DL assignment) or not include downlink data channel scheduling information (without DL assignment).

[0713] For each of the joint TCI state scheme and the separate TCI state scheme, there may be a MAC-CE for activating or indicating the above-mentioned single joint TCI state and separate TCI state, or based on one of the joint TCI state scheme and the separate TCI state scheme, one MAC-CE may be used to activate or indicate the TCI state. Through the accompanying drawings to be described below, various MAC-CE structures for activating and indicating the joint TCI state or the separate TCI state may be considered.

[0714] Fig.23is a diagram showing a MAC-CE structure for joint TCI state activation and indication in a wireless communication system according to an embodiment of the present disclosure.

[0715] See also Fig.23 , the S field 23-00 may indicate the number of pieces of joint TCI state information included in the MAC-CE. If the value of the S field 23-00 is 1, the MAC-CE may indicate one joint TCI state and may have a length of only up to the second 8-bit byte. If the value of the S field 23-00 is 0, the MAC-CE may include information about two or more joint TCI states, and activate each joint TCI state 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. Configuring 0 or 1 as the value of the S field 23-00 is not limited to the above configuration method. When the value is 0, this may indicate that one joint TCI state is included, and when the value is 1, this may indicate that information about two or more joint TCI states is included. The above explanation of the S field may also be applied to other embodiments of the present disclosure. By TCI state ID 0 Field 23-15 to TCI Status ID N-1 The TCI status indicated by fields 23-25 ​​may correspond to the 0th to N-1th code points of the TCI status field of DCI format 1_1 or 1_2, respectively. The serving cell ID field 23-05 may indicate an identifier of the serving cell (serving cell ID), and the BWP ID field 23-10 may indicate a bandwidth part ID. The R field may be a 1-bit reserved field that does not include indication information.

[0716] Fig.24 is a diagram showing another MAC-CE structure for joint TCI state activation and indication in a wireless communication system according to an embodiment of the present disclosure.

[0717] exist Fig.24 In the 8-bit byte, the serving cell ID field 24-05 may indicate an identifier of the serving cell (serving cell ID), and the BWP ID field 24-10 may indicate a bandwidth part ID. The R field 24-00 may be a 1-bit reserved field that does not include indication information. Each field present in the second to n-th 8-bit bytes is a bitmap indicating a joint TCI state configured by high-layer signaling. For example, T 7 24-15 may be a field indicating whether to indicate the eighth joint TCI state configured by higher layer signaling. N The value is 1, then the corresponding joint TCI state is interpreted as indicated or activated, and if T N If the value is 0, the corresponding joint TCI state is interpreted as not indicated or activated. The configuration of values ​​0 and 1 is not limited to the above configuration method. Fig.24 If the number of joint TCI states transmitted by the MAC-CE structure is 1, the UE can apply the joint TCI state indicated by the MAC-CE to the uplink transmission beam and the downlink reception beam. If the number of joint TCI states transmitted by the MAC-CE structure is 2 or more, the UE can identify that the respective joint TCI states indicated by the MAC-CE correspond to the respective code points of the TCI status field of the DCI format 1_1 or 1_2 and activate each joint TCI state, and by sequentially corresponding to the code points of the TCI status field of the DCI format 1_1 or 1_2 starting from the code point with the lowest index, the indicated joint TCI state can be activated starting from the joint TCI state with the lowest index.

[0718] Fig.25 is a diagram showing another MAC-CE structure for joint TCI state activation and indication in a wireless communication system according to an embodiment of the present disclosure.

[0719] exist Fig.25 In the UEFI field, the serving cell ID field 25-05 may indicate an identifier of a serving cell (serving cell ID), and the BWP ID field 25-10 may indicate a bandwidth part ID.

[0720] The S field 25-00 may indicate the number of pieces of joint TCI state information included in the MAC-CE. For example, if the value of the S field 25-00 is 1, the MAC-CE may indicate one joint TCI state and may have a length of only up to the second 8-bit byte, and the joint TCI state may be indicated by the TCI state ID. 0 For example, if the value of S field 25-00 is 0, the MAC-CE may include information about two or more joint TCI states, each code point of the TCI state field of DCI format 1_1 or 1_2 may activate each joint TCI state, up to 8 joint TCI states may be activated, the second 8-bit byte does not exist, and in Fig.25 The first octet and the third octet to the N+1th octet may exist on the MAC-CE structure of the MAC-CE. The fields present in the third to the N+1th octets are bitmaps indicating the joint TCI status configured by higher layer signaling. For example, T 15 25-25 may be a field indicating whether to indicate the 16th joint TCI state configured by higher layer signaling. R field 25-15 may be a 1-bit reserved field not including indication information.

[0721] If passed Fig.25If the number of joint TCI states transmitted by the MAC-CE structure of is 1, the UE may apply the joint TCI state indicated by the MAC-CE to both the uplink transmit beam and the downlink receive beam. Fig.25 If the number of joint TCI states conveyed by the MAC-CE structure is 2 or greater, the UE can identify that the individual joint TCI states indicated by the MAC-CE correspond to the individual code points of the TCI status field of the DCI format 1_1 or 1_2 and activate each joint TCI state, and by sequentially corresponding to the code points of the TCI status field of the DCI format 1_1 or 1_2 starting from the code point with the lowest index, the indicated joint TCI state can be activated starting from the joint TCI state with the lowest index.

[0722] Fig.26 is a diagram showing a MAC-CE structure for separating TCI state activation and indication in a wireless communication system according to an embodiment of the present disclosure.

[0723] exist Fig.26 In the UEFI field, the serving cell ID field 26-05 may indicate an identifier of a serving cell (serving cell ID), and the BWP ID field 26-10 may indicate a bandwidth part ID.

[0724] The S field 26-00 may indicate the number of pieces of separate TCI state set information included in the MAC-CE. For example, if the value of the S field 26-00 is 1, the MAC-CE may indicate one separate TCI state set and may include only 8-bit bytes up to the third 8-bit byte. For example, if the value of the S field 26-00 is 0, the MAC-CE may include information about two or more separate TCI state sets, and 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. 0 Field 26-15 may be a field indicating the separated TCI states included in the indicated separated TCI state set. 0 The value of the field is "00", which may mean reserved. 0 The value of the field is "01", which may mean a DL TCI state. 0 The value of the field is "10", which may mean a UL TCI state, and if C 0 If the value of the field is "11", this may mean indicating one DL TCI state and one UL TCI state, but this interpretation is only for C 0 Example of interpretation of field 26-15, and C 0 The interpretation of field 26-15 is not limited thereto. TCI Status IDD,0 Field 26-20 and TCI Status ID U,0 Fields 26-25 may mean the DL TCI state and UL TCI state that may be included and indicated in the 0th Split TCI State Set. 0 The value of the field is "01", then the TCI status ID D,0 Field 26-20 may indicate the DL TCI state and the TCI state ID may be ignored. U,0 Fields 26-25. If C 0 If the value of this field is "10", the TCI status ID can be ignored. D,0 Fields 26-20 and TCI Status ID U,0 Fields 26-25 may indicate the ULTCI status. 0 The value of the field is "11", then the TCI status ID D,0 Field 26-20 may indicate the DL TCI state, and the TCI state ID U,0 Fields 26-25 may indicate the UL TCI status.

[0725] Fig.26 An example of MAC-CE when the UL TCI state among the separated TCI states uses the same high-level signaling structure as the DL TCI state and the joint TCI state among the separated TCI states as described above can be shown. D,0 Field 26-20 and TCI Status ID U,0 Fields 26-25 may be 7 bits long to represent up to 128 TCI states. Therefore, in order to use 7 bits as the TCI state ID D,0 Fields 26-20 may allocate 6 bits 26-20 to the second 8-bit byte and 1 bit 26-21 to the third 8-bit byte. Fig.26 It can be shown that the UL TCI state among the separated TCI states uses a different high-level signaling structure from the DL TCI state and the joint TCI state among the separated TCI states as described above. Accordingly, the UL TCI state requires 6 bits to represent a maximum of 64 states, so the TCI state ID U,0 The first bit of the fields 26-25 may be fixed to 0 or 1, and the bits for indicating the actual UL TCI state may correspond to a total of 6 bits from the second bit to the seventh bit.

[0726] Fig. 27 is a diagram showing another MAC-CE structure for separating TCI state activation and indication in a wireless communication system according to an embodiment of the present disclosure.

[0727] exist Fig. 27In the DCI format 1_1 or 1_2, the serving cell ID field 27-05 may indicate an identifier of the serving cell (serving cell ID), and the BWP ID field 27-10 may indicate a bandwidth part ID. The S field 27-00 may indicate the number of pieces of separate TCI state set information included in the MAC-CE. For example, if the value of the S field 27-00 is 1, the MAC-CE may indicate one separate TCI state set and may include only 8-bit bytes up to the third 8-bit byte. For example, if the value of the S field 27-00 is 0, the MAC-CE may include information about two or more separate TCI state sets, and each code point of the TCI state field of the DCI format 1_1 or 1_2 may correspond to each separate TCI state set to activate it, and up to 8 separate TCI state sets may be activated. D,0 Field 27-15 may be a field indicating whether the indicated separate TCI state set includes a DL TCI state. D,0 If the value of field 27-15 is 1, the separate TCI state set includes the DL TCI state, and the DL TCI state can be identified by the TCI state ID D,0 Fields 27-25 indicate that if C D,0 If the value of field 27-15 is 0, the separate TCI state set does not include the DL TCI state, and the TCI state ID can be ignored. D,0 Fields 27-25. Similarly, C U,0 Field 27-20 may be a field indicating whether the indicated separate TCI state set includes a UL TCI state. U,0 If the value of field 27-20 is 1, the separate TCI state set includes the UL TCI state, and the UL TCI state can be identified by the TCI state ID. U,0 Fields 27-30 indicate that if C U,0 If the value of field 27-20 is 0, the detached TCI state set does not include the UL TCI state, and the TCI state ID can be ignored. U,0 Fields 27-30.

[0728] Fig. 27 An example of MAC-CE when the UL TCI state among the separated TCI states uses the same high-level signaling structure as the DL TCI state and the joint TCI state among the separated TCI states as described above can be shown. D,0 Fields 27-25 and TCI Status ID U,0 Fields 27-30 may be 7 bits in length to represent up to 128 TCI states. Fig. 27An example of MAC CE when the UL TCI state among the separated TCI states uses a different high-level signaling structure from the DL TCI state and the joint TCI state among the separated TCI states as described above can be shown. Accordingly, the UL TCI state requires 6 bits to represent a maximum of 64 states, so the TCI state ID U,0 The first bit of the fields 27 - 25 may be fixed to 0 or 1, and the bits for indicating the actual UL TCI state may correspond to a total of 6 bits from the second bit to the seventh bit.

[0729] Fig.28 is a diagram showing another MAC-CE structure for separating TCI state activation and indication in a wireless communication system according to an embodiment of the present disclosure.

[0730] exist Fig.28 In the MAC-CE, the serving cell ID field 28-05 may indicate an identifier of the serving cell (serving cell ID), and the BWP ID field 28-10 may indicate a bandwidth part ID. The S field 28-00 may indicate the number of pieces of separated TCI state set information included in the MAC-CE. For example, if the value of the S field 28-00 is 1, the MAC-CE may indicate one separated TCI state set and may include only 8-bit bytes up to the third 8-bit byte. Fig.28 The MAC-CE structure of the MAC-CE may use two 8-bit bytes to indicate a separate TCI state set, and if the separate TCI state set includes a DL TCI state, the first 8-bit byte of the two 8-bit bytes indicates the DL TCI state, and the second 8-bit byte may indicate the UL TCI state. Alternatively, the order may also be changeable.

[0731] For example, if the value of the S field 28-00 is 0, the MAC-CE may include information about two or more separate TCI state sets, 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. 0,0 Field 28-15 can have a TCI status ID 0,0 The TCI state indicated by field 28-25 means whether it is a DL TCI state or a UL TCI state. 0,0 If the value of field 28-15 is 1, the TCI state means the DL TCI state. The DL TCI state can be determined by the TCI state ID. 0,0 Fields 28-25 are used to indicate that a third octet may be present. In this case, if C 1,0 If the value of field 28-20 is 1, the UL TCI status can be determined by TCI status ID 1,0Fields 28-30 indicate that if C 1,0 If the value of field 28-20 is 0, the TCI status ID can be ignored. 1,0 Fields 28-30. If C 0,0 If the value of field 28-15 is 0, the UL TCI status can be determined by TCI status ID 0,0 Fields 28-25 are used to indicate that the third octet may not be present. 0,0 Fields 28-15 and C 1,0 This interpretation of fields 28-20 corresponds only to an example, C 0,0 The values ​​0 and 1 of the field 28-15 may be interpreted in opposite ways, or the values ​​of the DL TCI state and the UL TCI state may be interpreted in opposite ways.

[0732] Fig.28 An example of MAC-CE when the UL TCI state among the separated TCI states uses the same high-level signaling structure as the DL TCI state and the joint TCI state among the separated TCI states as described above can be shown. 0,0 Fields 28-25 and TCI Status ID 1,0 Fields 28-30 may be 7 bits in length to represent up to 128 TCI states. Fig.28 An example of MAC CE when the UL TCI state among the separated TCI states uses a higher layer signaling structure different from that of the DL TCI state and the joint TCI state among the separated TCI states as described above can be shown. 0,0 Field 28-25 may have 7 bits, which can represent both 6 bits for representing up to 64 UL TCI states and 7 bits for representing up to 128 DL TCI states. 1,0 The value of field 28-15 is 1, and therefore the TCI status ID 0,0 Field 28-25 indicates the UL TCI state, the TCI state ID 0,0 The first bit of the fields 28-25 may be fixed to 0 or 1, and the bit for indicating the actual UL TCI state may correspond to only a total of 6 bits from the second bit to the seventh bit.

[0733] Fig.29 is a diagram showing another MAC-CE structure for separating TCI state activation and indication in a wireless communication system according to an embodiment of the present disclosure.

[0734] exist Fig.29In the MAC-CE, the serving cell ID field 29-05 may indicate an identifier of the serving cell (serving cell ID), and the BWP ID field 29-10 may indicate the serving cell ID and the bandwidth part ID. The S field 29-00 may indicate the number of pieces of separated TCI state set information included in the MAC-CE. For example, if the value of the S field 29-00 is 1, the MAC-CE may indicate one separated TCI state set and may include only 8-bit bytes up to the third 8-bit byte.

[0735] For example, if the value of the S field 29-00 is 0, the MAC-CE may include information about two or more separate TCI state sets, 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. 0 Field 29-15 may be a field indicating the separated TCI status included in the indicated separated TCI status set. 0 The value of field 29-15 is "00", which means reserved. 0 The value of field 29-15 is "01", which means a DL TCI state. 0 The value of field 29-15 is "10", which means a UL TCI state, and if C 0 If the value of field 29-15 is "11", this means indicating a DL TCI state and a UL TCI state, but this interpretation is only for C 0 Example of interpretation of field 29-15 and C 0 The interpretation of field 29-15 is not limited thereto. TCI Status ID U,0 Fields 29-20 and TCI Status ID U,0 Fields 29-25 may mean the UL TCI state and DL TCI state that may be included and indicated in the 0th Split TCI State Set. 0 If the value of field 29-15 is "01", the TCI status ID D,0 Fields 29-25 may indicate the DL TCI state and the TCI state ID may be ignored. U,0 Field 29-20. If C 0 If the value of field 29-15 is "10", the third octet can be ignored and the TCI status ID U,0 Field 29-20 may indicate the ULTCI status. 0 If the value of field 29-15 is "11", the TCI status ID D,0 Field 29-25 may indicate the DL TCI state and TCI state ID U,0Field 29-20 may indicate a UL TCI state. R field 29-21 may be a 1-bit reserved field that does not include indication information.

[0736] Fig.29 An example of a MAC CE used when the UL TCI state among the separated TCI states uses a higher layer signaling structure different from that of the DL TCI state and the joint TCI state among the separated TCI states as described above can be shown. D,0 Fields 29-25 may be 7 bits long to represent up to 128 TCI states, and the TCI state ID U,0 Field 29-20 may be 6 bits in length to represent up to 64 TCI states.

[0737] Fig.30 2 is a diagram showing a MAC-CE structure for joint TCI state activation and indication and separate TCI state activation and indication in a wireless communication system according to an embodiment of the present disclosure.

[0738] exist Fig.30 , the serving cell ID field 30-05 may indicate an identifier of the serving cell (serving cell ID), and the BWP ID field 30-10 may indicate a bandwidth part ID. The J field 30-00 may indicate whether the TCI state indicated by the MAC-CE is a joint TCI state or a separate TCI state set. For example, if the value of the J field 30-00 is 1, the MAC-CE may indicate a joint TCI state, and if the value of the J field 30-00 is 0, the MAC-CE may indicate a separate TCI state set. This interpretation of the J field 30-00 corresponds only to an example, and it may be interpreted in the opposite manner.

[0739] - If the MAC-CE indicates the joint TCI state, all odd octets except the first octet may be ignored (the third octet, the fifth octet, ...). 0,0 Field 30-15 includes whether MAC-CE indicates a joint TCI state, or information about two or more TCI states, and each code point of the TCI state field of DCI format 1_1 or 1_2 activates each TCI state. 0,0 If the value of field 30-15 is 1, the MAC-CE may indicate a joint TCI state and there may be no octets starting from the third octet. 0,0 If the value of field 30-15 is 0, two or more joint TCI states indicated by MAC-CE may correspond to the respective code points of the TCI state field of DCI format 1_1 or 1_2 and be activated.0,0 May mean the first joint TCI state indicated.

[0740] - For example, in the case where MAC-CE indicates a separate TCI state set, C 0,0 Field 30-15 may have a TCI status ID 0,0 The TCI state indicated by field 30-25 means whether the DL TCI state or the UL TCI state, and if the value of this field is 1, the TCI state means the DL TCI state, and the DL TCI state can be determined by the TCI state ID. D,0 Fields 30-25 are used to indicate that a third 8-bit byte may be present. In this case, if C 1,0 If the value of field 30-20 is 1, the UL TCI status can be determined by TCI status ID 1,0 Field 30-30 indicates that if C 1,0 If the value of field 30-20 is 0, the TCI status ID can be ignored. 1,0 Field 30-30. If C 0,0 If the value of field 30-15 is 0, the UL TCI status can be determined by TCI status ID 0,0 Fields 30-25 are used to indicate that the third octet may not be present. Fig.30 An example of MAC-CE used when the UL TCI state among the separated TCI states uses the same high-level signaling structure as the DL TCI state and the joint TCI state among the separated TCI states as described above can be shown. 0,0 Fields 30-25 and TCI Status ID 1,0 Field 30-30 may be 7 bits in length to represent up to 128 TCI states. Fig.30 An example of a MAC CE used when the UL TCI state among the separated TCI states uses a higher layer signaling structure different from that of the DL TCI state and the joint TCI state among the separated TCI states as described above can be shown. 0,0 Field 30-25 may have 7 bits, which can represent both 6 bits for representing up to 64 UL TCI states and 7 bits for representing up to 128 DL TCI states. 0,0 The value of field 30-15 is 1, and therefore the TCI status ID 0,0 Field 30-25 indicates the UL TCI state, then TCI state ID 0,0 The first bit of the field 30-25 may be fixed to 0 or 1, and the bit for indicating the actual UL TCI state may correspond to only a total of 6 bits from the second bit to the seventh bit.

[0741] Fig.31 2 is a diagram showing another MAC-CE structure for joint TCI state activation and indication and separate TCI state activation and indication in a wireless communication system according to an embodiment of the present disclosure.

[0742] exist Fig.31 In the MAC-CE, the serving cell ID field 31-05 and the BWP ID field 31-10 may indicate the serving cell ID and the bandwidth part ID, respectively. The J field 31-00 may indicate whether the TCI state indicated by the MAC-CE is a joint TCI state or a separate TCI state set. For example, if the value of the J field 31-00 is 1, the MAC-CE may indicate the joint TCI state, and if the value of the J field 31-00 is 0, the MAC-CE may indicate a separate TCI state set. This interpretation of the J field 30-00 corresponds only to an example, and it may be interpreted in the opposite manner.

[0743] - If the MAC-CE indicates the joint TCI state, all even-numbered octets except the first octet may be ignored (the second octet, the fourth octet, ...). 0 Field 31-21 indicates whether the MAC-CE indicates one joint TCI state, or whether two or more TCI states correspond to the respective code points of the TCI state field of DCI format 1_1 or 1_2 and are activated. 0 If the value of field 31-21 is 1, the MAC-CE may indicate a joint TCI state and there may be no octets starting from the third octet. 0 If the value of 31-21 is 0, the MAC-CE may include information about two or more joint TCI states, and each code point of the TCI state field of DCI format 1_1 or 1_2 may activate each joint TCI state. D,0 May mean the first joint TCI state indicated.

[0744] - If MAC-CE indicates a separate TCI state set, then C 0 Field 31-15 may be a field indicating the separation TCI state included in the indicated separation TCI state set. 0 The value of field 31-15 is "00", which means reserved. 0 The value of field 31-15 is "01", which means a DL TCI state. 0 The value of field 31-15 is "10", which means a UL TCI state, and if C 0If the value of field 31-15 is "11", this means indicating one DL TCI state and one UL TCI state. These values ​​correspond only to an example, and the present disclosure is not limited to the example. TCI State ID U,0 Fields 31-20 and TCI Status ID U,0 Field 31-25 may mean the UL TCI state and DL TCI state that may be included and indicated in the 0th Split TCI State Set. 0 If the value of field 31-15 is "01", the TCI status ID D,0 Field 31-25 may indicate the DL TCI state, and the TCI state ID may be ignored. U,0 Field 31-20, if C 0 If the value of field 31-15 is "10", the TCI status ID U,0 Field 31-20 may indicate the UL TCI status, and if C 0 If the value of field 31-15 is "11", the TCI status ID D,0 Field 31-25 indicates the DL TCI state and TCI state ID U,0 Field 31-20 may indicate the UL TCI status. 0 If the value of Field 31-21 is 1, the MAC-CE may indicate a separate TCI state set and there may be no octets starting from the fourth octet. 0 If the value of 31-21 is 0, the MAC-CE may include information about two or more separate TCI state sets, and each code point 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. 0 If the value of field 31-21 is 0, if C 1 ,……,C N-1 If the value of the S field is "10", this means that only the UL TCI status is indicated, so the fifth, seventh, ..., Mth octets can be ignored. n The field may indicate whether there is an 8-bit byte for the next separate TCI state set. For example, if S n The value of this field is 1, then the next 8-bit byte may not exist, and if S n If the value of the field is 0, then there can be C n+1 and TCI Status ID U,n+1 The next 8-bit byte. n These values ​​of the fields merely correspond to an example, and the present disclosure is not limited to the example.

[0745] Fig.31 An example of MAC CE when the UL TCI state among the separated TCI states uses a higher layer signaling structure different from that of the DL TCI state and the joint TCI state among the separated TCI states as described above can be shown. D,0 Fields 31-25 may be 7 bits long to represent up to 128 TCI states, and the TCI state ID U,0 Field 31-20 may be 6 bits in length to represent up to 64 TCI states.

[0746] In the case where the UE receives a transmit / receive beam related indication via high-layer signaling using a joint TCI state scheme or a separate TCI state scheme, the UE may receive a PDSCH including a MAC-CE indicating a joint TCI state or a separate TCI state from a base station to perform application of the transmit / receive beam. If the MAC-CE includes two or more joint TCI states or separate TCI state sets, the UE may recognize that, as described above, the multiple joint TCI states or separate TCI state sets indicated by the MAC-CE correspond to the respective code points of the TCI state field of the DCI format 1_1 or 1_2 3ms after the transmission of the PUCCH including HARQ-ACK information indicating whether the reception of the corresponding PDSCH is successful, and may activate the indicated joint TCI state or separate TCI state set. Thereafter, the UE may receive DCI format 1_1 or 1_2 to apply one joint TCI state or separate TCI state set indicated by the TCI state field in the DCI to the uplink transmit beam and the downlink receive beam. DCI format 1_1 or 1_2 may include downlink data channel scheduling information (with DL assignment) or may not include downlink data channel scheduling information (without DL assignment).

[0747] Fig.32 is a diagram showing beam application time that can be considered when a unified TCI scheme is used in a wireless communication system according to an embodiment of the present disclosure.

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

[0749] -DCI format 1_1 or 1_2 with DL assignment (32-00): If the UE receives DCI format 1_1 or 1_2 (32-01) including downlink data channel scheduling information from the base station, so that a joint TCI state or a separate TCI state set based on the unified TCI scheme is indicated, the UE can receive the PDSCH scheduled based on the received DCI (32-05), and send a PUCCH (32-10) including HARQ-ACK indicating whether the reception of DCI and PDSCH is successful to the base station. For both DCI and PDSCH, HARQ-ACK may include whether the reception is successful. If the UE fails to receive at least one of the DCI and PDSCH, the UE may send NACK, and if the UE successfully receives both of them, the UE may send ACK.

[0750] -DCI format 1_1 or 1_2 (32-50) without DL assignment: If the UE receives DCI format 1_1 or 1_2 (32-55) from the base station that does not include downlink data channel scheduling information, so that a joint TCI state or a separate TCI state set based on a unified TCI scheme is indicated, the UE can assume the following items for the DCI.

[0751] ■ The DCI includes a CRC scrambled with the CS-RNTI.

[0752] ■ The value of all bits assigned to all fields used as redundant version fields is 1.

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

[0754] ■The values ​​of all bits assigned to all fields used as New Data Indication (NDI) fields are 0.

[0755] ■In the case of frequency domain resource allocation (FDRA) type 0, the values ​​of all bits assigned to the FDRA field are 0, in the case of FDRA type 1, the values ​​of all bits assigned to the FDRA field are 1, and in the case where the FDRA scheme is dynamicSwitch, the values ​​of all bits assigned to the FDRA field are 0.

[0756] The UE may transmit a PUCCH (32-60) including a HARQ-ACK indicating whether DCI format 1_1 or 1_2 on which the above items are assumed is successfully received to the base station.

[0757] -For both DCI formats 1_1 or 1_2 with DL assignment (32-00) and without DL assignment (32-50), if the new TCI state indicated by DCI 32-01 or 32-55 is the same as the TCI state that has been previously indicated and is therefore already applied to uplink transmission and downlink reception, the UE may maintain the previously applied TCI state. If the new TCI state is different from the previously indicated TCI state, the UE can determine that after the start time point 32-20 or 32-70 of the first time slot after a time interval as long as the beam application time (BAT) 32-15 or 32-65 after PUCCH transmission (in the time interval 32-30 or 32-80), the joint TCI state or separate TCI state set indicated by the TCI state field included in the DCI is applied, and the previously indicated TCI state can be used in the time interval 32-35 or 32-75 before the start time point 32-20 or 32-70 of the time slot.

[0758] - For both DCI formats 1_1 or 1_2 with DL assignment (32-00) and without DL assignment (32-50), the BAT is a specific number of OFDM symbols and can be configured by higher layer signaling based on UE capability reporting information. The basic parameter set for the BAT and the first slot after the BAT can be determined based on the minimum basic parameter set among all cells to which the joint TCI state or separate TCI set indicated by the DCI is applied.

[0759] The UE may apply one joint TCI state indicated by MAC-CE or DCI to the reception of a control resource set connected to all UE-specific search spaces, the reception of a PDSCH and the transmission of a PUSCH scheduled by a PDCCH sent from the control resource set, and the transmission of all PUCCH resources.

[0760] If a separate TCI state set indicated by MAC-CE or DCI includes a DL TCI state, the UE may apply this separate TCI state set to the reception of a control resource set connected to all UE-specific search spaces and to the reception of a PDSCH scheduled by a PDCCH sent from the control resource set, and apply the previously indicated UL TCI state to all PUSCH resources and PUCCH resources.

[0761] If a separate TCI state set indicated by MAC-CE or DCI includes a UL TCI state, the UE may apply this separate TCI state set to all PUSCH resources and PUCCH resources, and apply the previously indicated DL TCI state to the reception of a control resource set connected to all UE-specific search spaces and to the reception of a PDSCH scheduled by a PDCCH sent from the control resource set.

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

[0763] Reference above Figures 23 to 31 In the described examples of MAC CE, at least one element thereof may be combined.

[0764] <Second embodiment: Multi-TCI status indication and activation method based on unified TCI solution>

[0765] As an embodiment of the present disclosure, a multi-TCI state indication and activation method based on a unified TCI scheme is described. The multi-TCI state indication and activation method may indicate a case where the number of indicated joint TCI states is extended to 2 or more and a case where the number of each of the DL TCI states and UL TCI states included in a separate TCI state set is extended to 2 or more. If the number of each of the DL TCI states and UL TCI states that can be included in a separate TCI state set is up to 2, the available combinations of DL TCI states and UL TCI states that a separate TCI state set can have may be a total of 8 ({DL,UL}={0,1},{0,2},{1,0},{1,1},{1,2},{2,0},{2,1},{2,2}, where each number indicates the number of TCI states).

[0766] If the base station indicates multiple TCI states to the UE based on MAC-CE, the UE may receive two or more joint TCI states or one separate TCI state set from the base station through MAC-CE. The base station may schedule the reception of the PDSCH including the MAC-CE for the UE through the PDCCH, and based on the two or more joint TCI states or one separate TCI state set indicated 3ms after the transmission of the PUCCH including HARQ-ACK information indicating whether the reception of the PDSCH including the MAC-CE is successful, the UE may determine an uplink transmit beam or transmit filter and a downlink receive beam or receive filter.

[0767] If the base station indicates multiple TCI states to the UE 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 UE 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 UE through the PDCCH, and the UE may activate multiple pieces of TCI state information included in the MAC-CE 3ms after the transmission of the PUCCH including HARQ-ACK information indicating whether the reception of the PDSCH including the MAC-CE is successful.

[0768] If the base station indicates multiple TCI states to the UE based on DCI format 1_1 or 1_2, there may be two or more TCI state fields in DCI format 1_1 or 1_2, and two or more joint TCI states or one of two or more separate TCI state sets may be indicated based on each TCI state field. In this case, the UE may receive a MAC-CE from the base station and activate a joint TCI state or separate TCI state set corresponding to each code point of two or more 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 to the UE through the PDCCH. The UE may activate multiple pieces of TCI state information included in the MAC-CE 3ms after the transmission of the PUCCH including HARQ-ACK information indicating whether the reception of the PDSCH including the MAC-CE is successful. Whether there are one or more additional TCI state fields can be configured for the UE through high-level signaling, and the bit length of the additional TCI state field may be the same as the existing TCI state field, or may be adjusted based on high-level signaling.

[0769] By using one of the joint TCI state and the separate TCI state configured by the base station, the UE can receive the transmit / receive beam-related indication in the unified TCI scheme. The base station can configure the UE to use one of the joint TCI state and the separate TCI state through high-layer signaling. The separate TCI state indication can be configured for the UE through high-layer signaling so that the bit length of the TCI state field in DCI format 1_1 or 1_2 is a maximum of 4.

[0770] For each of the joint TCI state scheme and the separate TCI state scheme, there may be a MAC-CE for activating or indicating the above-mentioned multiple joint TCI states and separate TCI states. Based on one of the joint TCI state scheme and the separate TCI state scheme, one MAC-CE may be used to activate or indicate the TCI state, or the MAC-CE used in the MAC-CE-based indication scheme and the MAC-CE-based activation scheme may share a MAC-CE structure or use a separate MAC-CE structure. Various MAC-CE structures for activating and indicating multiple joint TCI states or separate TCI states may be considered through the accompanying drawings to be described below. In the following drawings, for ease of explanation, two TCI states that are activated or indicated are considered, but the drawings may be similarly applied to three or more TCI states.

[0771] Fig.33 is a diagram showing a MAC-CE structure for activating and indicating multiple joint TCI states in a wireless communication system according to an embodiment of the present disclosure.

[0772] exist Fig.33 33-05 may indicate an identifier of a serving cell (serving cell ID), and a BWP ID field 33-10 may indicate a bandwidth part ID. The R field may be a 1-bit reserved field that does not include indication information. The S field 33-00 may indicate the number of pieces of joint TCI state set information included in the MAC-CE. For example, if the value of the S field 33-00 is 1, the MAC-CE may indicate one or two joint TCI states and may have a length of only up to the third 8-bit byte. In this case, if the C 0 If the value of field 33-15 is 0, the third octet is not present and a combined TCI state can be identified by the TCI state ID 0,0 Field 33-20 indicates that if C 0 If the value of field 33-15 is 1, the third 8-bit byte is present and the two combined TCI states can be identified by the TCI state ID 0,0 Field 33-20 and TCI Status ID 1,0 Field 33-25 indicates.

[0773] For example, if the value of the S field 33-00 is 0, the MAC-CE may activate one or two joint TCI states corresponding to each code point of the TCI status field of the DCI format 1_1 or 1_2, or activate one joint TCI state corresponding to each code point of the two TCI status fields of the DCI format 1_1 or 1_2, and may activate joint TCI states for up to 8 code points. In the case of activating one or two joint TCI states for one code point of one TCI status field, the TCI status ID 0,Y Field and TCI Status ID 1,Y The TCI Status ID field may indicate the first joint TCI state and the second joint TCI state of the two joint TCI states activated at the Yth code point of the TCI Status field, respectively. In the case where a joint TCI state is activated for one code point of the two TCI Status fields, the TCI Status ID 0,Y Field and TCI Status ID 1,Y The field can indicate the respective joint TCI states activated at the Yth code point of the first TCI status field and the second TCI status field.

[0774] Fig.34 is a diagram showing a MAC-CE structure for activating and indicating multiple separate TCI states in a wireless communication system according to an embodiment of the present disclosure.

[0775] exist Fig.34 In the MAC-CE, the serving cell ID field 34-05 may indicate an identifier of the serving cell (serving cell ID), and the BWP ID field 34-10 may indicate a bandwidth part ID. The R field may be a 1-bit reserved field that does not include indication information. The S field 34-00 may indicate the number of pieces of separate TCI state set information included in the MAC-CE. If the value of the S field 34-00 is 1, the MAC-CE may indicate one separate TCI state set and may include only 8-bit bytes up to the fifth 8-bit byte. If the value of the S field 34-00 is 0, the MAC-CE may include information about multiple separate TCI state sets, and the MAC-CE may activate one separate TCI state set corresponding to each code point of the TCI state field of DCI format 1_1 or 1_2, or activate one separate TCI state set corresponding to each code point of the two TCI state fields of DCI format 1_1 or 1_2, and as described above, a maximum of 8 or 16 separate TCI states of code points may be activated by high-layer signaling.

[0776] exist Fig.34 In the MAC-CE structure of , each four octets may correspond to a separate TCI state set starting from the second octet. 0Field 34-15 can have a total of 8 values ​​from "000" to "111", and these values ​​can respectively correspond to the 8 cases that a separate TCI state set can have, as described above.

[0777] - If C 0 The value of this field is "000", which means a separate TCI state set including a UL TCI state. The TCI state ID can be ignored. D,0,0 Fields 34-20 and 34-21, and a TCI status ID U,0,0 Field 34-25 may include information about a UL TCI state. In addition, the fourth octet and the fifth octet may be ignored.

[0778] - If C 0 The value of this field is "001", which means a split TCI state set includes two UL TCI states, and the TCI state ID can be ignored. D,0,0 Fields 34-20 and 34-21, and TCI Status ID U,0,0 Field 34-25 may include information about the first UL TCI state of the two UL TCI states. In addition, the fourth octet may be ignored and the TCI state ID U,1,0 Fields 34-35 may include information about the second UL TCI state among the two UL TCI states.

[0779] - If C 0 The value of this field is "010", which means that a separate TCI state set includes a DL TCI state, TCI state ID D,0,0 Fields 34-20 and 34-21 may include information about a DL TCI state, and the TCI state ID may be ignored. U,0,0 Fields 34-25 and the fourth octet and the fifth octet.

[0780] - If C 0 The value of the field is "011", which means that a separate TCI state set includes a DL TCI state and a UL TCI state. The TCI state ID D,0,0 Fields 34-20 and 34-21 may include information about a DL TCI state, and the TCI state ID U,0,0 Field 34-25 may include information about a UL TCI state. The fourth octet and the fifth octet may be ignored.

[0781] - If C 0The value of the field is "100", which means that a separate TCI state set includes one DL TCI state and two UL TCI states. D,0,0 Fields 34-20 and 34-21 may include information about a DL TCI state, and the TCI state ID U,0,0 Field 34-25 may include information about the first UL TCI state of the two UL TCI states. In addition, the fourth octet may be ignored and the TCI state ID U,1,0 Fields 34-35 may include information about the second UL TCI state among the two UL TCI states.

[0782] - If C 0 The value of the field is "101", which means that a split TCI state set includes two DL TCI states, TCI state ID D,0,0 Fields 34-20 and 34-21 may include information about the first DL TCI state among the two DL TCI states, and the TCI state ID may be ignored. U,0,0 Fields 34-25 and the fifth octet. In addition, the TCI Status ID D,1,0 Field 34-30 may include information about the second DL TCI state among the two DL TCI states.

[0783] - If C 0 The value of the field is "110", which means that a separate TCI state set includes two DL TCI states and one UL TCI state. D,0,0 Fields 34-20 and 34-21 may include information about the first DL TCI state of the two DL TCI states, TCI state ID U,0,0 Field 34-25 may include information about a UL TCI state, TCI state ID D,1,0 Field 34-30 may include information about the state of the second DL TCI of the two DL TCIs, and the fifth octet may be ignored.

[0784] - If C 0 The value of the field is "111", which means that a separate TCI state set includes two DL TCI states and two UL TCI states. D,0,0 Fields 34-20 and 34-21 may include information about the first DL TCI state of the two DL TCI states, TCI state ID U,0,0Field 34-25 may include information about the first UL TCI state of the two UL TCI states, TCI state ID D,1,0 Field 34-30 may include information about the second DL TCI state among the two DL TCI states, and the TCI state ID U,1,0 Fields 34-35 may include information about the second UL TCI state among the two UL TCI states.

[0785] Fig.34 An example of a MAC CE used when the UL TCI state among the separated TCI states uses a different high-level signaling structure from the DL TCI state and the joint TCI state among the separated TCI states as described above can be shown. Accordingly, the UL TCI state requires 6 bits to represent a maximum of 64 states, so the TCI state ID representing the UL TCI state U,0,0 To TCI Status ID U,1,N The field can be expressed using 6 bits, and the TCI state ID indicating the DL TCI state D,0,0 To TCI Status ID D,1,N The field can be expressed using 7 bits.

[0786] Fig.35 is a diagram showing another MAC-CE structure for activating and indicating multiple separate TCI states in a wireless communication system according to an embodiment of the present disclosure.

[0787] exist Fig.35 35-05 may indicate an identifier of a serving cell (serving cell ID), and a BWP ID field 35-10 may indicate a bandwidth part ID. The R field may be a 1-bit reserved field that does not include indication information. The S field 35-00 may indicate the number of pieces of separate TCI state set information included in the MAC-CE. For example, if the value of the S field 35-00 is 1, the MAC-CE may indicate one separate TCI state set and may have a length of only up to the fifth 8-bit byte.

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

[0789] exist Fig.35In the MAC-CE structure of C, every four 8-bit bytes can correspond to a separate TCI state set starting from the second 8-bit byte. U,0 Fields 35-15 and C D,0 Fields 35-21 respectively mean the number of UL TCI states and the number of DL TCI states included in one separate TCI state set, and the meaning of each code point may be as follows.

[0790] - If C U,0 The value of the field is "00", which means that the UL TCI state is not included, so the TCI state ID can be ignored. U,0,0 35-20 and TCI Status ID U,1,0 35-25.

[0791] - If C U,0 The value of the field is "01", which means that a UL TCI state is included, so the TCI state ID U,0,0 35-20 may include information about a UL TCI state and may ignore the TCI state ID U,1,0 35-25.

[0792] - If C U,0 If the value of the field is "10", it means that two UL TCI states are included, so the TCI state ID U,0,0 35-20 may include information about the first UL TCI state among the two UL TCI states, and the TCI state ID U,1,0 35-25 may include information about the second UL TCI state among the two UL TCI states.

[0793] - If C D,0 The value of the field is "00", which means that the DL TCI status is not included, so the fourth octet and the fifth octet can be ignored.

[0794] - If C D,0 The value of the field is "01", which means that a DL TCI state is included, so the TCI state ID D,0,0 35-30 may include information about a DL TCI state, and the fifth octet may be ignored.

[0795] - If C D,0 If the value of the field is "10", it means that two DL TCI states are included, so the TCI state ID D,0,0 35-30 may include information about the first DL TCI state among the two DL TCI states, and the TCI state ID D,1,035-35 may include information about the second DL TCI state among the two DL TCI states.

[0796] Fig.35 An example of a MAC CE used when the UL TCI state among the separated TCI states uses a different high-level signaling structure from the DL TCI state and the joint TCI state among the separated TCI states as described above can be shown. Accordingly, the UL TCI state requires 6 bits to represent a maximum of 64 states, so the TCI state ID representing the UL TCI state U,0,0 To TCI Status ID U,1,N The field can be expressed using 6 bits, and the TCI state ID indicating the DL TCI state D,0,0 To TCI Status ID D,1,N The field can be expressed using 7 bits.

[0797] Reference above Figure 33 to Figure 35 In the described examples of MAC CE, at least one element thereof may be combined.

[0798] <Third embodiment: UE capability reporting method for supporting simultaneous uplink transmission based on multiple DCIs using multiple panels and operations following the method>

[0799] As an embodiment of the present disclosure, a method of simultaneously transmitting an uplink signal scheduled by multi-DCI (mDCI) by using a plurality of panels is described.

[0800] Until NR version 17, one panel can be selected from multiple panels to send uplink signals, or all panels can be used to send uplink signals depending on the UE implementation. However, this transmission is a simultaneous transmission that is not supported in the specification, so it is not expected to allocate uplink transmission power according to each panel or send different data for each panel to increase the transmission volume. At the same time, based on multiple DCIs, each PUSCH is schedulable through different DCIs associated with different values ​​of CORESETPoolIndex, but the scheduled PUSCHs are constrained to overlap each other in the time domain. This implies that the function of performing simultaneous transmission in time by considering multiple panels is not supportable.

[0801] It is expected that future NR versions will discuss and introduce methods for supporting simultaneous uplink channel transmission by using multiple panels. In order to simultaneously transmit uplink signals by using multiple panels, uplink channels for simultaneous transmission can be scheduled based on a single DCI, or uplink channels for simultaneous transmission can be scheduled based on multiple DCIs. In the present disclosure, the case of scheduling uplink channels by multiple DCIs and simultaneously transmitting scheduled uplink channels that overlap in the time domain is considered. If two panels are considered, two uplink channels (e.g., PUSCH) can be scheduled by corresponding DCIs, the channels can partially or completely overlap with each other in the time domain, and some or all resources can overlap or not overlap with each other in the frequency domain (frequency division multiplexing FDM).

[0802] As described above, in order to support simultaneous uplink transmission using multiple panels, a multi-panel implementation scheme for UEs for simultaneous transmission and UE capabilities associated therewith are required. The UE may report to the base station the supportable UE capabilities among the various UE capabilities associated with simultaneous uplink transmission, and based on the UE capabilities, the base station may determine whether to use multiple panels to support simultaneous uplink transmission of the UE. If the base station determines that simultaneous uplink transmission is supported for a UE supporting simultaneous uplink transmission using multiple panels, the base station may configure the UE with high-level parameters associated therewith. Thereafter, the base station may schedule an uplink channel for simultaneous uplink transmission according to one of the scheduling methods based on a single DCI or multiple DCIs. Alternatively, by using two scheduling methods based on a single DCI and multiple DCIs, the base station may also support simultaneous uplink transmission by a dynamic switching method such as dynamic switching. In the present disclosure, simultaneous uplink transmission using multiple panels by scheduling based on multiple DCIs is considered. However, this does not mean that the UE cannot support simultaneous uplink transmission by scheduling based on a single DCI using multiple panels.

[0803] Fig.36 An example of scheduling PUSCHs that are simultaneously transmitted in uplink through respective panels by using multiple DCIs is shown.

[0804] The DCI 36-10 that has been received through the CORESET configured with CORESETPoolIndex of 0 may schedule transmission of PUSCHs 36-16 and 36-17 through panel1 for the UE. Fig.36A case is shown where PUSCHs 36-16 and 36-17 transmitted through panel1 and scheduled through DCI 36-10 have two layers but a PUSCH having a layer number of 1 instead of 2 may be scheduled. DCI 36-20, which has been received through a CORESET configured with a CORESETPoolIndex of 1, may schedule transmission of PUSCHs 36-26 and 36-27 through panel2 for the UE. Fig.36 The case where PUSCHs 36-26 and 36-17 transmitted through panel 2 and scheduled by DCI 36-20 have two layers but a PUSCH with a layer number of 1 instead of 2 can be scheduled is shown. In addition, depending on the implementation or capability of the UE, the respective PUSCHs scheduled by the respective DCIs 36-10 and 36-20 may need to have the same number of layers. Alternatively, depending on the implementation or capability of the UE, the respective PUSCHs scheduled by the respective DCIs 36-10 and 36-20 may have different numbers of layers. For the convenience of detailed explanation, Fig.36 The panel1 and panel2 shown correspond only to examples. DCI that has been received through a CORESET configured with CORESETPoolIndex of 0 may schedule uplink transmission through panel2 (a panel having an ID value greater than that of other panels in view of the panel management of the UE), and DCI that has been received through a CORESET configured with CORESETPoolIndex of 1 may schedule uplink transmission through panel1 (a panel having an ID value less than that of other panels in view of the panel management of the UE). The panel IDs may not be reported separately to the base station, and the UE may randomly assign and manage IDs in view of the implementation.

[0805] As reference Fig.36 As described above, each DCI received from a CORESET configured with a different CORESETPoolIndex value can schedule each PUSCH transmitted by each panel. Fig.36The UE shown can support UE capabilities for performing simultaneous transmission using multiple panels. In Embodiment 3-2, it is described whether the UE supports the UE capabilities described in Embodiment 3-1 and the specific operations of the base station and the UE according to the reported candidate values. The UE capability of using multiple panels for simultaneous uplink transmission based on multiple DCIs described in detail in the present disclosure can be used as the UE capability of using multiple panels for simultaneous uplink transmission based on a single DCI (if necessary) and operations based on multiple DCIs. Parameters for the corresponding feature group (FG) or the corresponding UE capability report can be defined as parameters for a common feature group or a common UE capability report for supporting simultaneous transmission using multiple panels.

[0806] <Example 3-1: UE Features for Supporting Simultaneous Uplink Transmission Based on Multiple DCIs Using Multiple Panels>

[0807] As an embodiment of the present disclosure, UE features required for a UE to support simultaneous uplink transmission based on multiple DCIs using multiple panels are described in detail.

[0808] In order to support multi-DCI based simultaneous uplink transmission using multiple panels (hereinafter, for the convenience of explanation in the present disclosure, it may be replaced by multi-panel simultaneous transmission (STxMP) based on mDCI), the following additional UE features and UE capability reports related thereto may be required. At least one of the following UE features may be defined, and a UE capability report for at least one UE feature may be required:

[0809] -UE Feature 1) Maximum number of configurable CORESETs per supported cell per bandwidth part (BWP) (if CORESET0 is configured, the maximum configurable number of CORESETs including CORESET0): This UE feature and the corresponding UE report can be used equivalently to the UE feature and corresponding UE report for multi-TRP based on multi-DCI supported for the downlink.

[0810] -UE Feature 2) Maximum number of CORESETs per CORESETPoolIndex: This UE feature and the corresponding UE report may be the same as the UE feature and the corresponding UE report for multi-TRP based on multi-DCI supported for the downlink.

[0811] -UE Feature 3) Support for transmission of PUSCH that is completely overlapped in the time domain: This UE feature may support transmission of PUSCH that is completely overlapped in the time domain but not in the frequency domain. In addition, this UE feature may also support transmission of PUSCH that is completely overlapped in the frequency domain as well as in the time domain. If the UE feature includes whether to support transmission of PUSCH that is completely overlapped in both the time domain and the frequency domain, "UE Feature 6" and UE capabilities described later may be omitted.

[0812] -UE feature 4) Maximum number of PUSCHs sent per CORESETPoolIndex per timeslot: This UE feature means the maximum number of PUSCHs scheduled by a DCI associated with one value of CORESETPoolIndex that the UE can process in one timeslot. The candidate value reportable by the UE capability may be one of {1,2,3,4,7}. Alternatively, any natural number between 1 and 7 may be a candidate. Alternatively, any natural number between 1 and 14 may be a candidate. For example, if the UE reports 2 to the base station for the UE report corresponding to UE feature 4), this may imply that the UE is able to send two PUSCHs scheduled by a DCI with a CORESETPoolIndex of 0 (or without a CORESETPoolIndex configured for it) or with a CORESETPoolIndex of 1 in one timeslot.

[0813] -UE Feature 5) Maximum number of PUSCHs sent for all values ​​of CORESETPoolIndex per slot: This UE feature means the maximum number of PUSCHs scheduled by DCI associated with all values ​​of CORES...

Claims

1. A method performed by a terminal in a wireless communication system, the method include: Sending terminal capability information including information related to simultaneous transmission of multiple panels (STxMP) to a base station; receiving a high-layer signal from a base station; Identify whether the higher layer signal includes parameters for supporting STxMP; In case that the higher layer signal includes parameters for supporting STxMP, identifying support for STxMP based on multiple downlink control information (DCI); receiving, from a base station, first downlink control information (DCI) for scheduling a first physical uplink shared channel (PUSCH) from a first control resource set (CORESET) pool index configured as 0 and a second DCI for scheduling a second PUSCH from a second CORESET pool index configured as 1; and The first PUSCH transmission and the second PUSCH transmission overlapping at least in the time domain are performed based on STxMP.

2. The method according to claim 1, in, The information related to STxMP includes information indicating whether more than one sounding reference signal (SRS) resource set with usage of codebook or nonCodebook is supported.

3. The method according to claim 1, in, The information related to STxMP includes at least one of information about supporting transmission of PUSCHs overlapping in the time domain, information about the maximum number of PUSCHs transmitted per time slot and CORESET pool index, and information about the maximum number of PUSCHs transmitted per time slot for all CORESET pool indexes.

4. The method according to claim 1, in, The information related to STxMP includes at least one of information on whether a corresponding SRS resource set supports different numbers of SRS resources in a case where STxMP is supported, and information on the number of SRS resources included at most in each SRS resource set.

5. A method performed by a base station in a wireless communication system, the method include: receiving terminal capability information including information related to simultaneous transmission of multiple panels (STxMP) from the terminal; generating a higher layer signal including parameters for supporting STxMP based on the terminal capability information; Send high-level signals to the terminal; Determining support for STxMP based on multiple downlink control information (DCI); Sending a first downlink control information (DCI) and a second DCI to the terminal, the first DCI being used to schedule a first physical uplink shared channel (PUSCH) from a first control resource set (CORESET) pool index configured as 0, and the second DCI being used to schedule a second PUSCH from a second CORESET pool index configured as 1; and A first PUSCH transmission and a second PUSCH reception that overlap at least in the time domain are performed based on the STxMP.

6. The method according to claim 5, in, The information related to STxMP includes information indicating whether more than one sounding reference signal (SRS) resource set with usage of codebook or nonCodebook is supported.

7. The method according to claim 5, in, The information related to STxMP includes at least one of information about supporting transmission of PUSCHs overlapping in the time domain, information about the maximum number of PUSCHs transmitted per time slot and CORESET pool index, and information about the maximum number of PUSCHs transmitted per time slot for all CORESET pool indexes.

8. The method according to claim 5, in, The information related to STxMP includes at least one of information on whether a corresponding SRS resource set supports different numbers of SRS resources in a case where STxMP is supported, and information on the number of SRS resources included at most in each SRS resource set.

9. A terminal of a wireless communication system, the terminal include: Transceiver; as well as Controller, The controller is configured to perform control to: Sending terminal capability information including information related to simultaneous transmission of multiple panels (STxMP) to a base station; receiving a high-layer signal from a base station; Identify whether the higher layer signal includes parameters for supporting STxMP; In case that the higher layer signal includes parameters for supporting STxMP, identifying support for STxMP based on multiple downlink control information (DCI); receiving, from a base station, first downlink control information (DCI) for scheduling a first physical uplink shared channel (PUSCH) from a first control resource set (CORESET) pool index configured as 0 and a second DCI for scheduling a second PUSCH from a second CORESET pool index configured as 1; and The first PUSCH transmission and the second PUSCH transmission overlapping at least in the time domain are performed based on STxMP.

10. The terminal according to claim 9, in, The information related to STxMP includes information indicating whether more than one sounding reference signal (SRS) resource set with usage of codebook or nonCodebook is supported.

11. The terminal according to claim 9, in, The information related to STxMP includes at least one of information about supporting transmission of PUSCHs overlapping in the time domain, information about the maximum number of PUSCHs transmitted per time slot and CORESET pool index, and information about the maximum number of PUSCHs transmitted per time slot for all CORESET pool indexes.

12. The terminal according to claim 9, in, The information related to STxMP includes at least one of information on whether a corresponding SRS resource set supports different numbers of SRS resources in a case where STxMP is supported, and information on the number of SRS resources included at most in each SRS resource set.

13. A base station in a wireless communication system, the base station include: Transceiver; as well as Controller, The controller is configured to perform control to: receiving terminal capability information including information related to simultaneous transmission of multiple panels (STxMP) from the terminal; generating a higher layer signal including parameters for supporting STxMP based on the terminal capability information; Sending high-layer signals to UE; Determining support for STxMP based on multiple downlink control information (DCI); Sending a first downlink control information (DCI) and a second DCI to the terminal, the first DCI being used to schedule a first physical uplink shared channel (PUSCH) from a first control resource set (CORESET) pool index configured as 0, and the second DCI being used to schedule a second PUSCH from a second CORESET pool index configured as 1; and A first PUSCH transmission and a second PUSCH reception that overlap at least in the time domain are performed based on the STxMP.

14. The base station according to claim 13, in, The information related to STxMP includes information indicating whether more than one sounding reference signal (SRS) resource set with usage of codebook or nonCodebook is supported.

15. The base station according to claim 13, in, Information related to STxMP includes: at least one of information about supporting transmission of PUSCHs overlapping in the time domain, information about a maximum number of PUSCHs transmitted per time slot and a CORESET pool index, and information about a maximum number of PUSCHs transmitted per time slot for all CORESET pool indexes; and At least one of information on whether a corresponding SRS resource set supports different numbers of SRS resources in a case of supporting STxMP, and information on the number of SRS resources included at a maximum in each SRS resource set.

Images