Method and apparatus for transmitting control information and data information in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. A method performed by a user equipment (UE) may comprise the steps of: receiving, from a base station, first downlink control information (DCI) for scheduling a first physical downlink shared channel (PDSCH), wherein the first DCI indicates whether a second DCI is to be received; receiving, on the basis of the first DCI, the second DCI for scheduling one or more PDSCHs; and receiving the one or more PDSCHs on the basis of the second DCI.

Description

Method and apparatus for transmitting control information and data information in a wireless communication system

[0001] The present disclosure relates to a wireless communication system, and more specifically, to a method and apparatus for transmitting control information and data information in a wireless communication system.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in frequency bands below 6 GHz ('Sub 6 GHz'), such as 3.5 gigahertz (3.5 GHz), but also in ultra-high frequency bands called millimeter waves (mmWave), such as 28 GHz and 39 GHz ('Above 6 GHz'). In addition, for 6G mobile communication technology, which is referred to as a system beyond 5G, implementation in the terahertz band (e.g., the 3 terahertz (3 THz) band at 95 GHz) is being considered to achieve transmission speeds 50 times faster and ultra-low latency reduced to one-tenth compared to 5G mobile communication technology.

[0003] In the early stages of 5G mobile communication technology, aiming to satisfy service support and performance requirements for enhanced Mobile BroadBand (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), technologies such as beamforming and Massive MIMO to mitigate path loss and increase transmission distance in ultra-high frequency bands, support for various numerologies (such as the operation of multiple subcarrier spacings) and dynamic operation of slot formats for the efficient utilization of ultra-high frequency resources, initial access techniques to support multi-beam transmission and broadband, definition and operation of Band-Width Parts (BWP), Low Density Parity Check (LDPC) codes for high-volume data transmission, new channel coding methods such as Polar Codes for the reliable transmission of control information, and L2 pre-processing (L2 Standardization has been carried out for pre-processing, network slicing which provides a dedicated network specialized for specific services, and other methods.

[0004] Currently, discussions are underway to improve and enhance the performance of the initial 5G mobile communication technology, taking into account the services that the 5G mobile communication technology was intended to support. Additionally, standardization of the physical layer is in progress for technologies such as V2X (Vehicle-to-Everything), which helps autonomous vehicles make driving decisions and enhance user convenience based on their own location and status information transmitted by the vehicle; NR-U (New Radio Unlicensed), which aims for system operation in unlicensed bands to comply with various regulatory requirements; NR terminal low power consumption technology (UE Power Saving); Non-Terrestrial Network (NTN), which is direct terminal-satellite communication for securing coverage in areas where communication with the terrestrial network is impossible; and positioning.

[0005] In addition, standardization is underway in the field of wireless interface architecture / protocols for technologies such as the Industrial Internet of Things (IIoT) for supporting new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) which provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement including Conditional Handover and Dual Active Protocol Stack (DAPS) Handover, and 2-step Random Access (2-step RACH for NR) which simplifies random access procedures. Standardization is also underway in the field of system architecture / services for 5G baseline architectures (e.g., Service based Architecture, Service based Interface) for incorporating Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC), which provides services based on the location of the terminal.

[0006] When such 5G mobile communication systems are commercialized, connected devices, which are increasing explosively, will be connected to communication networks. Accordingly, it is expected that there will be a need to enhance the functionality and performance of 5G mobile communication systems and to integrate the operation of connected devices. To this end, new research is planned to be conducted on 5G performance improvement and complexity reduction, support for AI services, support for metaverse services, and drone communication using eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] Furthermore, the advancement of these 5G mobile communication systems encompasses multi-antenna transmission technologies such as new waveforms to guarantee coverage in the terahertz band of 6G mobile communication technology, Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas; metamaterial-based lenses and antennas to improve terahertz band signal coverage; high-dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum); and Reconfigurable Intelligent Surface (RIS) technology; as well as Full Duplex technology for enhancing frequency efficiency and system networks in 6G mobile communication technology; AI-based communication technologies that realize system optimization by utilizing satellites and AI from the design stage and internalizing end-to-end AI support functions; and the realization of services of complexity exceeding the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could serve as a foundation for the development of next-generation distributed computing technologies.

[0008] According to one embodiment of the present disclosure, an apparatus and method capable of effectively providing services in a mobile communication system are provided.

[0009] According to one embodiment of the present disclosure, a method performed by user equipment (UE) may include receiving downlink control information (DCI) from a base station for scheduling a physical downlink shared channel (PDSCH), the first DCI indicating whether a second DCI is to be received, receiving a second DCI for scheduling one or more PDSCHs based on the first DCI, and receiving the one or more PDSCHs based on the second DCI.

[0010] According to one embodiment of the present disclosure, an apparatus and a method capable of effectively providing services in a wireless communication system may be provided.

[0011] The effects obtainable from the present disclosure are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art to which the present disclosure belongs from the description below.

[0012] FIG. 1 is a diagram illustrating the basic structure of the time-frequency domain in a wireless communication system according to one embodiment of the present disclosure.

[0013] FIG. 2 is a drawing illustrating a frame, subframe, and slot structure in a wireless communication system according to one embodiment of the present disclosure.

[0014] FIG. 3 is a drawing illustrating an example of a bandwidth portion setting in a wireless communication system according to an embodiment of the present disclosure.

[0015] FIG. 4 is a diagram illustrating an example of setting a control area of ​​a downlink control channel in a wireless communication system according to one embodiment of the present disclosure.

[0016] FIG. 5 is a diagram illustrating the structure of a downlink control channel in a wireless communication system according to one embodiment of the present disclosure.

[0017] FIG. 6 is a diagram illustrating, through a Span, a case in which a terminal in a wireless communication system according to one embodiment of the present disclosure may have a plurality of PDCCH (physical downlink control channel) monitoring locations within a slot.

[0018] FIG. 7 is a diagram illustrating an example of base station beam allocation according to TCI state setting in a wireless communication system according to one embodiment of the present disclosure.

[0019] FIG. 8 is a diagram illustrating an example of a method for allocating a TCI state to a PDCCH in a wireless communication system according to one embodiment of the present disclosure.

[0020] FIG. 9 is a diagram illustrating a TCI (transmission configuration indicator) indication MAC (medium access control) CE (control element) signaling structure for a PDCCH DMRS (demodulation reference signal) in a wireless communication system according to one embodiment of the present disclosure.

[0021] FIG. 10 is a drawing illustrating an example of beam settings for a control resource set and a search space in a wireless communication system according to one embodiment of the present disclosure.

[0022] FIG. 11 is a diagram illustrating a method for transmitting and receiving data in a wireless communication system according to one embodiment of the present disclosure, in consideration of a downlink data channel and a rate matching resource, between a base station and a terminal.

[0023] FIG. 12 is a diagram illustrating a method for selecting a set of receivable control resources by considering priority when a terminal receives a downlink control channel in a wireless communication system according to one embodiment of the present disclosure.

[0024] FIG. 13 is a diagram illustrating an example of a non-periodic CSI (channel state information) reporting method according to one embodiment of the present disclosure.

[0025] FIG. 14 is a drawing illustrating an example of a PUSCH (physical uplink shared channel) repetitive transmission type B in a wireless communication system according to one embodiment of the present disclosure.

[0026] FIG. 15 is a diagram illustrating the wireless protocol structure of a base station and a terminal in a single cell, CA (carrier aggregation), and DC (dual connectivity) situation in a wireless communication system according to one embodiment of the present disclosure.

[0027] FIG. 16 is a drawing illustrating an example of antenna port configuration and resource allocation for cooperative communication in a wireless communication system according to one embodiment of the present disclosure.

[0028] FIG. 17 is a diagram illustrating an example of downlink control information (DCI) configuration for cooperative communication in a wireless communication system according to one embodiment of the present disclosure.

[0029] FIG. 18 illustrates a procedure in which a base station controls the transmission power of a terminal in a cellular system.

[0030] FIG. 19 is a diagram illustrating the process of a terminal according to one embodiment of the present disclosure generating a Type-1 (quasi-static) HARQ (hybrid automatic repeat request)-ACK (acknowledgement) codebook.

[0031] FIG. 20 is a diagram illustrating the process of a terminal according to one embodiment of the present disclosure generating a Type-2 (dynamic) HARQ-ACK codebook.

[0032] FIG. 21 is a diagram illustrating the orbital period of a communication satellite according to the altitude or height of the satellite according to one embodiment of the present disclosure.

[0033] FIG. 22 is a diagram showing a PDCCH repetitive transmission according to one embodiment of the present disclosure.

[0034] FIG. 23 is a diagram showing a Type 0 PDCCH CSS (common search space) resource in a situation where a total of 4 SS (synchronization signal) / PBCH (physical broadcast channel) blocks can be transmitted and received according to one embodiment of the present disclosure.

[0035] FIG. 24 is a diagram showing a PDCCH repetitive transmission according to one embodiment of the present disclosure.

[0036] FIG. 25 is a diagram showing a PDCCH repetitive transmission according to one embodiment of the present disclosure.

[0037] FIG. 26 is a diagram showing a PDCCH repetitive transmission according to one embodiment of the present disclosure.

[0038] FIG. 27 is a diagram showing a PDCCH repetitive transmission according to one embodiment of the present disclosure.

[0039] FIG. 28 is a diagram showing a PDCCH repetitive transmission according to one embodiment of the present disclosure.

[0040] FIG. 29 is a diagram showing a PDCCH repetitive transmission according to one embodiment of the present disclosure.

[0041] FIG. 30 is a terminal flowchart for performing PDCCH repetitive transmission and reception according to one embodiment of the present disclosure.

[0042] FIG. 31 is a drawing illustrating the structure of a terminal in a wireless communication system according to one embodiment of the present disclosure.

[0043] FIG. 32 is a drawing illustrating the structure of a base station in a wireless communication system according to one embodiment of the present disclosure.

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

[0045] In describing the embodiments, technical details that are well known in the art to which this disclosure belongs and are not directly related to this disclosure are omitted. This is intended to convey the essence of this disclosure more clearly without obscuring it by omitting unnecessary explanations.

[0046] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Additionally, the size of each component does not entirely reflect its actual size. Identical or corresponding components in each drawing may be assigned substantially the same reference number.

[0047] The advantages and features of the present disclosure, and the methods for achieving them, will become clear by referring to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below but may be implemented in various different forms. These embodiments are provided merely to ensure that the disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Throughout the specification, the same reference numerals refer to the same components. Furthermore, in describing the present disclosure, if it is determined that a detailed description of a related function or configuration might unnecessarily obscure the essence of the present disclosure, such detailed description is omitted. Additionally, the terms described below are defined considering their functions in the present disclosure, and these may vary depending on the intentions or conventions of the user or operator. Therefore, their definitions should be based on the content throughout the specification.

[0048] Hereinafter, the base station is an entity that performs resource allocation for terminals and may be at least one of a gNode B (next generation node B), an eNode B (E-URTRA node B), a Node B, a BS (Base Station), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions. In this disclosure, the Downlink (DL) refers to the wireless transmission path of a signal transmitted by the base station to the terminal, and the Uplink (UL) refers to the wireless transmission path of a signal transmitted by the terminal to the base station. Furthermore, while LTE or LTE-A systems may be described as examples below, embodiments of this disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, 5th generation mobile communication technology (5G, new radio, NR) developed after LTE-A may be included, and the 5G below may be a concept that includes existing LTE, LTE-A, and other similar services. Furthermore, the present disclosure may be applied to other communication systems with some modifications without significantly departing from the scope of the present disclosure, at the discretion of a person with skilled technical knowledge.

[0049] At this time, it can be understood that each block of the process flow diagrams and combinations of the flow diagrams can be executed by computer program instructions. Since these computer program instructions can be loaded into the processor of a general-purpose computer, a computer for special purposes, or other programmable data processing equipment, the instructions executed through the processor of the computer or other programmable data processing equipment create means to perform the functions described in the flow diagram block(s). Since these computer program instructions can also be stored in computer-available or computer-readable memory that can be directed toward the computer or other programmable data processing equipment to implement the function in a specific way, the instructions stored in computer-available or computer-readable memory can also produce a manufactured item containing means of instruction to perform the function described in the flow diagram block(s). Since computer program instructions can be loaded onto a computer or other programmable data processing equipment, instructions that execute a computer or other programmable data processing equipment by performing a series of operation steps on the computer or other programmable data processing equipment to create a process executed by the computer may also provide steps for executing the functions described in the flowchart block(s).

[0050] Additionally, each block may represent a module, segment, or part of code containing one or more executable instructions for executing a specific logical function(s). It should also be noted that in some alternative execution examples, the functions mentioned in the blocks may occur out of order. For example, two blocks described in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order according to their corresponding functions.

[0051] In this embodiment, the term "part" refers to a software or hardware component such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit), and the "part" performs certain roles. However, the meaning of "part" is not limited to software or hardware. The "part" may be configured to reside in an addressable storage medium or configured to run one or more processors. Thus, as an example, the "part" includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and "parts" may be combined into a smaller number of components and "parts" or further separated into additional components and "parts." In addition, the components and 'parts' may be implemented to utilize one or more CPUs within the device or secure multimedia card. Also, in the embodiments, 'parts' may include one or more processors.

[0052] Wireless communication systems are evolving from providing early voice-oriented services to broadband wireless communication systems that provide high-speed and high-quality packet data services, such as communication standards like 3GPP’s HSPA (High Speed ​​Packet Access), LTE (Long Term Evolution or E-UTRA (Evolved Universal Terrestrial Radio Access)), LTE-Advanced (LTE-A), LTE-Pro, 3GPP2’s HRPD (High Rate Packet Data), UMB (Ultra Mobile Broadband), and IEEE’s 802.16e.

[0053] As a representative example of the above-mentioned broadband wireless communication system, the LTE (long term evolution) system employs the Orthogonal Frequency Division Multiplexing (OFDM) method for the downlink (DL) and the Single Carrier Frequency Division Multiple Access (SC-FDMA) method for the uplink (UL). The uplink refers to a wireless link through which a terminal (User Equipment (UE) or Mobile Station (MS)) transmits data or control signals to a base station (eNode B, or base station (BS)), and the downlink refers to a wireless link through which a base station transmits data or control signals to a terminal. The above-mentioned multiple access method can distinguish the data or control information of each user by allocating and operating time-frequency resources to be sent for each user so that they do not overlap, that is, so that orthogonality is established.

[0054] As a future communication system following LTE, that is, a 5G communication system, it must be able to freely reflect the diverse requirements of users and service providers, and therefore, services that satisfy various requirements simultaneously must be supported. Services being considered for the 5G communication system include enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra Reliability Low Latency Communication (URLLC).

[0055] eMBB aims to provide data transmission speeds that are superior to those supported by existing LTE, LTE-A (advanced), or LTE-Pro. For example, in a 5G communication system, eMBB must be able to provide a peak data rate of 20 Gbps in the downlink and 10 Gbps in the uplink from the perspective of a single base station. Furthermore, while providing these peak data rates, the 5G communication system must also provide an increased user-perceived data rate. To satisfy these requirements, it necessitates improvements in various transmission and reception technologies, including enhanced Multi-Input Multi-Output (MIMO) transmission technology. Additionally, while LTE transmits signals using a maximum transmission bandwidth of 20 MHz in the 2 GHz band, the 5G communication system can meet the data transmission speeds required by using a frequency bandwidth wider than 20 MHz in frequency bands of 3–6 GHz or above 6 GHz.

[0056] Simultaneously, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To efficiently provide IoT, mMTC may require support for a large number of terminal connections within a cell, improved terminal coverage, enhanced battery life, and / or reduced terminal costs. Since IoT provides communication functions attached to various sensors and devices, it must be possible to support a large number of terminals within a cell (e.g., 1,000,000 terminals / km²). Furthermore, due to the nature of the service, terminals supporting mMTC are likely to be located in dead zones not covered by cells, such as building basements; therefore, they may require wider coverage compared to other services provided by 5G communication systems. Terminals supporting mMTC must consist of low-cost devices, and since it is difficult to frequently replace terminal batteries, a very long battery life of 10 to 15 years may be required.

[0057] Finally, in the case of URLLC, it may be a mission-critical cellular-based wireless communication service. For example, services used for remote control of robots or machinery, industrial automation, unmanned aerial vehicles, remote health care, and emergency alerts can be considered. Therefore, the communication provided by URLLC must offer very low latency and very high reliability. For example, services supporting URLLC must satisfy an air interface latency of less than 0.5 milliseconds, and simultaneously 10 -5The following packet error rate requirements apply. Therefore, for services supporting URLLC, 5G systems must provide a Transmit Time Interval (TTI) smaller than other services, and at the same time, design considerations may be required to allocate a wide resource in the frequency band to ensure the reliability of the communication link.

[0058] The three 5G services, namely eMBB, URLLC, and mMTC, can be multiplexed and transmitted within a single system. In this case, different transmission and reception techniques and parameters may be used between the services to satisfy the different requirements of each service. Of course, 5G is not limited to the three services mentioned above.

[0059] The present disclosure relates to the operation of a terminal and a base station in a satellite communication system. Specifically, the present disclosure relates to a method for transmitting and receiving data information in a satellite communication system and an apparatus capable of performing the same.

[0060] Efforts are being made to develop improved 5G or pre-5G communication systems to meet the increasing demand for wireless data traffic following the commercialization of 4G communication systems. For this reason, 5G or pre-5G communication systems are referred to as systems beyond the 4G network or systems following the LTE system. To achieve high data transmission rates, the implementation of 5G communication systems in the mmWave band (e.g., the 60 GHz band) is being considered. To mitigate path loss and increase the transmission distance of radio waves in the mmWave band, technologies such as beamforming, massive MIMO, full Dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large-scale antennas are being discussed for 5G communication systems. In addition, to improve the network of the system, the development of technologies such as advanced small cell, advanced small cell, cloud radio access network (cloud RAN), ultra-dense network, Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, CoMP (Coordinated Multi-Points), and interference cancellation is taking place in 5G communication systems.In addition, advanced coding modulation (ACM) methods such as FQAM (Hybrid FSK and QAM Modulation) and SWSC (Sliding Window Superposition Coding), as well as advanced access technologies such as FBMC (Filter Bank Multi Carrier), NOMA (non-orthogonal multiple access), and SCMA (sparse code multiple access), are being developed in 5G systems.

[0061] Meanwhile, the Internet is evolving from a human-centered network where humans generate and consume information into an IoT (Internet of Things) network where distributed components, such as objects, exchange and process information. IoE (Internet of Everything) technology, which combines IoT with big data processing technologies through connections with cloud servers, is also emerging. To implement IoT, technological elements such as sensing technology, wired and wireless communication and network infrastructure, service interface technology, and security technology are required; consequently, technologies such as sensor networks, Machine-to-Machine (M2M) communication, and Machine-Type Communication (MTC) are currently being researched to facilitate the connection of objects. In an IoT environment, intelligent IT services that create new value for human life by collecting and analyzing data generated from connected objects can be provided. Through the convergence and integration of existing IT technologies with various industries, IoT can be applied to fields such as smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart home appliances, and advanced medical services.

[0062] Accordingly, various attempts are being made to apply 5G communication systems (5th generation communication systems or New Radio (NR)) to IoT networks. For example, technologies such as sensor networks, Machine to Machine (M2M), and Machine Type Communication (MTC) are being implemented using 5G communication technologies such as beamforming, MIMO, and array antennas. The application of cloud radio access networks (cloud RAN) as the big data processing technology described earlier can also be considered an example of the convergence of 3G and IoT technologies.

[0063] As a result of the aforementioned developments and advancements in wireless communication systems, it has become possible to provide various services, and thus measures are required to facilitate the smooth provision of these services.

[0064] [NR Time-Frequency Resources]

[0065] The frame structure of the 5G system will be explained in more detail below with reference to the drawings.

[0066] Figure 1 is a diagram illustrating the basic structure of the time-frequency domain, which is a wireless resource domain where data or control channels are transmitted in a 5G system.

[0067] The horizontal axis of FIG. 1 may represent the time domain, and the vertical axis may represent the frequency domain. In the time and frequency domains, the basic unit of a resource is a resource element (RE, 101), which can be defined as one OFDM (Orthogonal Frequency Division Multiplexing) symbol (102) on the time axis and one subcarrier (103) on the frequency axis. In the frequency domain (For example, 12) consecutive REs can form a single resource block (Resource Block, RB, 104).

[0068] FIG. 2 is a drawing illustrating a frame, subframe, and slot structure in a wireless communication system according to one embodiment of the present disclosure.

[0069] Referring to FIG. 2, an example of a frame (200), subframe (201), and slot (202) structure is illustrated. One frame (200) can be defined as 10ms. One subframe (201) can be defined as 1ms, and thus one frame (200) can be composed of a total of 10 subframes (201). One slot (202, 203) can be defined as 14 OFDM symbols (i.e., the number of symbols per slot ( )=14). A subframe (201) may be composed of one or more slots (202, 203), and the number of slots (202, 203) per subframe (201) may vary depending on the setting value μ (204, 205) for the subcarrier spacing. In one example of FIG. 2, cases where μ=0 (204) and μ=1 (205) are shown as the setting value for the subcarrier spacing. When μ=0 (204), a subframe (201) may be composed of one slot (202), and when μ=1 (205), a subframe (201) may be composed of two slots (203). That is, the number of slots per subframe ( ) may vary, and accordingly, the number of slots per frame ( ) may vary. Depending on each subcarrier spacing setting μ and It can be defined by Table 1 below.

[0070]

[0071] [Bandwidth Section (BWP)]

[0072] Next, the Bandwidth Part (BWP) setting in the 5G communication system will be explained in detail with reference to the drawing.

[0073] FIG. 3 is a drawing illustrating an example of a bandwidth portion setting in a wireless communication system according to one embodiment of the present disclosure.

[0074] FIG. 3 shows an example in which the terminal bandwidth (UE bandwidth) (300) is configured into two bandwidth portions, namely bandwidth portion #1 (BWP#1) (301) and bandwidth portion #2 (BWP#2) (302). The base station may configure one or more bandwidth portions for the terminal and may configure the following information for each bandwidth portion.

[0075]

[0076] Of course, the above examples are not limited, and various parameters related to bandwidth portions may be configured for the terminal in addition to the configuration information described above. The above information may be transmitted by the base station to the terminal via higher-layer signaling, for example, Radio Resource Control (RRC) signaling. Among the one or more configured bandwidth portions, at least one bandwidth portion may be activated. Whether a configured bandwidth portion is activated may be transmitted semi-statically from the base station to the terminal via RRC signaling or dynamically via Downlink Control Information (DCI).

[0077] According to one embodiment, prior to the Radio Resource Control (RRC) connection, the terminal may receive an Initial Bandwidth Part (Initial BWP) for initial connection from the base station via a Master Information Block (MIB). More specifically, during the initial connection phase, the terminal may receive configuration information for a Control Resource Set (CORESET) and a Search Space via the MIB, through which a Physical Downlink Control Channel (PDCCH) can be transmitted to receive system information required for initial connection (Remaining System Information; which may correspond to RMSI or System Information Block 1; SIB1). The Control Resource Set and Search Space configured via the MIB may each be considered as Identity (ID) 0. The base station may notify the terminal via the MIB of configuration information, such as frequency allocation information, time allocation information, and numerology, for Control Resource Set #0. In addition, the base station may notify the terminal via the MIB of configuration information regarding the monitoring period and occasion for control area #0, i.e., configuration information for search area #0. The terminal may regard the frequency area configured as control area #0 obtained from the MIB as the initial bandwidth portion for initial access. At this time, the identifier (ID) of the initial bandwidth portion may be identified as 0.

[0078] The settings for the bandwidth portion supported by 5G can be used for various purposes.

[0079] According to one embodiment, if the bandwidth supported by the terminal is smaller than the system bandwidth, this can be supported through the bandwidth portion setting. For example, by setting the frequency position of the bandwidth portion (setting information 2) to the terminal, the terminal can transmit and / or receive data at a specific frequency position within the system bandwidth.

[0080] According to one embodiment, a base station may set multiple bandwidth portions for a terminal for the purpose of supporting different numerologies. For example, to support data transmission and reception using both a 15 kHz subcarrier interval and a 30 kHz subcarrier interval for a terminal, the two bandwidth portions may be set to subcarrier intervals of 15 kHz and 30 kHz, respectively. Different bandwidth portions may be frequency division multiplexed, and when data transmission and reception is to be performed with a specific subcarrier interval, the bandwidth portion set to that subcarrier interval may be activated.

[0081] According to one embodiment, for the purpose of reducing the power consumption of the terminal, a base station may set a bandwidth portion having a different bandwidth size for the terminal. For example, if the terminal supports a very large bandwidth, such as 100 MHz, and always transmits and receives data using that bandwidth, very large power consumption may occur. In particular, in a situation where there is no traffic, performing monitoring of an unnecessary downlink control channel using a large bandwidth of 100 MHz may be very inefficient in terms of power consumption. For the purpose of reducing the power consumption of the terminal, the base station may set a bandwidth portion of a relatively small bandwidth, such as 20 MHz, for the terminal. In a situation where there is no traffic, the terminal can perform monitoring operations in the 20 MHz bandwidth portion, and when data is generated, it can transmit and receive data using the 100 MHz bandwidth portion according to the instructions of the base station.

[0082] Regarding the method of configuring the bandwidth part, terminals prior to RRC connection (Connected) can receive configuration information for the Initial Bandwidth Part through the Master Information Block (MIB) during the initial connection phase. For example, a terminal can receive a Control Resource Set (CORESET) for a downlink control channel through which Downlink Control Information (DCI) scheduling System Information Blocks (SIB) can be transmitted from the MIB of the Physical Broadcast Channel (PBCH). The bandwidth of the control resource set by the MIB can be considered as the Initial Bandwidth Part, and through the configured Initial Bandwidth Part, the terminal can receive the Physical Downlink Shared Channel (PDSCH) through which SIBs are transmitted. In addition to receiving SIBs, the Initial Bandwidth Part may also be utilized for Other System Information (OSI), paging, and Random Access.

[0083] [Bandwidth Section (BWP) Change]

[0084] When one or more bandwidth parts are set for a terminal, the base station may instruct the terminal to change (or switch, transition) the bandwidth part using the Bandwidth Part Indicator field within the DCI. For example, in FIG. 3, if the currently active bandwidth part of the terminal is Bandwidth Part #1 (301), the base station may instruct the terminal to Bandwidth Part #2 (302) using the Bandwidth Part Indicator within the DCI, and the terminal may perform a bandwidth part change to Bandwidth Part #2 (302) indicated by the received Bandwidth Part Indicator within the DCI.

[0085] As mentioned above, since DCI-based bandwidth portion changes can be directed by the DCI scheduling PDSCH or PUSCH, when a terminal receives a bandwidth portion change request, it must be able to receive or transmit the PDSCH or PUSCH scheduled by the corresponding DCI in the changed bandwidth portion without difficulty. To this end, the standard specifies the delay time (T) required when changing the bandwidth portion. BWP The requirements for ) have been defined, and can be defined as, for example, as follows.

[0086]

[0087] The requirements for bandwidth portion change delay time support Type 1 or Type 2 depending on the terminal's capability. The terminal can report the supported bandwidth portion delay time type to the base station.

[0088] According to one embodiment, in accordance with the requirements for the aforementioned bandwidth portion change delay time, when a terminal receives a DCI including a bandwidth portion change indicator in slot n, the terminal performs a change to the new bandwidth portion indicated by the bandwidth portion change indicator in slot n+T BWP Completion can be performed at a time no later than the new bandwidth portion, and transmission and / or reception for the data channel scheduled by the corresponding DCI can be performed in the changed new bandwidth portion. If the base station intends to schedule a data channel in the new bandwidth portion, the terminal's bandwidth portion change delay time (T BWP By considering ), time-domain resource allocation for a data channel can be determined. That is, when a base station schedules a data channel with a new bandwidth portion, in the method for determining time-domain resource allocation for a data channel, the data channel can be scheduled after the bandwidth portion change delay time. Accordingly, the terminal [is notified] that the DCI instructing the bandwidth portion change is the bandwidth portion change delay time (T BWPYou may not expect to indicate a slot offset (K0 or K2) value smaller than )

[0089] If a terminal receives a DCI (e.g., DCI format 1_1 or 0_1) instructing a change in the bandwidth portion, the terminal may not perform any transmission or reception during a time interval corresponding to the time interval from the third symbol of the slot in which the PDCCH containing the DCI was received to the beginning of the slot indicated by the slot offset value (K0 or K2) indicated by the time domain resource allocation indicator field within the DCI. For example, if a terminal receives a DCI instructing a change in the bandwidth portion in slot n, and the slot offset value indicated by the DCI is K, the terminal may not perform any transmission or reception from the third symbol of slot n to the symbol before slot n+K (i.e., the last symbol of slot n+K-1).

[0090] [SS / PBCH Block]

[0091] Next, we will explain the SS (Synchronization Signal) / PBCH block in 5G.

[0092] An SS / PBCH block may refer to a physical layer channel block composed of PSS (Primary SS), SSS (Secondary SS), and PBCH. Specifically, it is as follows.

[0093] - PSS: A signal that serves as the reference for downlink time / frequency synchronization and provides some information about the cell ID (identity).

[0094] - SSS: Serves as the reference for downlink time / frequency synchronization and provides the remaining cell ID information not provided by PSS. Additionally, it can serve as a reference signal for PBCH demodulation.

[0095] - PBCH: Provides essential system information required for transmitting and receiving data channels and control channels of the terminal. The essential system information may include search space-related control information representing wireless resource mapping information of the control channel, and / or scheduling control information for a separate data channel that transmits system information.

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

[0097] According to one embodiment, the terminal can detect PSS and SSS during the initial connection phase and can decode PBCH. It can obtain MIB from PBCH and receive a Control Resource Set (CORESET) #0 (which may correspond to a control resource set with a control resource index of 0) from it. The terminal can perform monitoring of Control Resource Set #0 by assuming that the selected SS / PBCH block and the Demodulation Reference Signal (DMRS) transmitted from Control Resource Set #0 are Quasi-Co-Locationed (QCL). The terminal can receive system information as downlink control information transmitted from Control Resource Set #0. The terminal can obtain configuration information related to Random Access Channel (RACH) required for initial connection from the received system information. The terminal can transmit a Physical RACH (PRACH) to the base station considering the selected SS / PBCH index, and the base station receiving the PRACH can obtain information regarding the SS / PBCH block index selected by the terminal. The base station can know that the terminal has selected a block among the respective SS / PBCH blocks and is monitoring the associated control area #0.

[0098] [PDCCH: DCI related]

[0099] Next, Downlink Control Information (DCI) in 5G systems will be explained in detail.

[0100] In a 5G system, scheduling information for uplink data (or Physical Uplink Shared Channel (PUSCH)) or downlink data (or Physical Downlink Shared Channel (PDSCH)) can be transmitted from a base station to a terminal via DCI. The terminal can monitor the fallback DCI format and the non-fallback DCI format for PUSCH or PDSCH. The fallback DCI format may consist of fixed fields selected between the base station and the terminal, and the non-fallback DCI format may include configurable fields.

[0101] According to one embodiment, the DCI can be transmitted through a Physical Downlink Control Channel (PDCCH) after undergoing channel coding and modulation processes. A Cyclic Redundancy Check (CRC) is attached to the DCI message payload, and the CRC can be scrambled into a Radio Network Temporary Identifier (RNTI) corresponding to the identity of the terminal. Different RNTIs may be used depending on the purpose of the DCI message, for example, terminal-specific (UE-specific) data transmission, power control commands, or random access responses. That is, the RNTI is not explicitly transmitted but is included in the CRC calculation process and transmitted. Upon receiving a DCI message transmitted over the PDCCH, the terminal checks the CRC using the assigned RNTI, and if the result of the CRC check is correct, the terminal knows that the message has been transmitted to the terminal.

[0102] For example, a DCI scheduling a PDSCH for System Information (SI) can be scrambled to SI-RNTI. A DCI scheduling a PDSCH for Random Access Response (RAR) messages can be scrambled to RA-RNTI. A DCI scheduling a PDSCH for Paging messages can be scrambled to P-RNTI. A DCI notifying a Slot Format Indicator (SFI) can be scrambled to SFI-RNTI. A DCI notifying Transmit Power Control (TPC) can be scrambled to TPC-RNTI. A DCI scheduling a terminal-specific PDSCH or PUSCH can be scrambled to C-RNTI (Cell RNTI).

[0103] DCI format 0_0 can be used as a countermeasure DCI for scheduling PUSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 0_0 with the CRC scrambled with C-RNTI may include, for example, the following information.

[0104]

[0105] DCI format 0_1 ​​can be used as a non-defense DCI for scheduling PUSCH, whereby the CRC can be scrambled with C-RNTI. DCI format 0_1 ​​with the CRC scrambled with C-RNTI may include, for example, the following information.

[0106]

[0107]

[0108] DCI format 1_0 can be used as a countermeasure DCI for scheduling PDSCH, whereby the CRC can be scrambled with C-RNTI. DCI format 1_0 with the CRC scrambled with C-RNTI may include, for example, the following information.

[0109]

[0110] DCI format 1_1 can be used as a non-defense DCI for scheduling PDSCH, whereby the CRC can be scrambled with C-RNTI. DCI format 1_1 with the CRC scrambled with C-RNTI may include, for example, the following information.

[0111]

[0112] [PDCCH: CORESET, REG, CCE, Search Space]

[0113] In the following, the downlink control channel in a 5G communication system will be explained in more detail with reference to the drawings.

[0114] FIG. 4 is a diagram illustrating an example of a control resource set (CORESET) in which a downlink control channel is transmitted in a 5G wireless communication system. FIG. 4 illustrates an example in which two control resources (control resource #1 (401), control resource #2 (402)) are set within a terminal bandwidth part (UE bandwidth part) (410) in the frequency axis and one slot (420) in the time axis.

[0115] Referring to FIG. 4, control areas (401, 402) can be set to a specific frequency resource (403) within the entire terminal bandwidth portion (410) along the frequency axis. Along the time axis, they can be set to one or more OFDM symbols and can be defined as the control resource set duration (404). Referring to the example illustrated in FIG. 4, control area #1 (401) is set to a control resource set duration of 2 symbols, and control area #2 (402) is set to a control resource set duration of 1 symbol.

[0116] The control domain in the aforementioned 5G can be configured by a base station to a terminal via upper-layer signaling (e.g., System Information, Master Information Block (MIB), Radio Resource Control (RRC) signaling). Configuring a control domain to a terminal means providing information such as a control domain identifier, the frequency location of the control domain, and / or the symbol length of the control domain. For example, information for configuring a control domain may include at least some of the following information.

[0117]

[0118] In [Table 8], the tci-StatesPDCCH (simply named TCI (Transmission Configuration Indication) state) configuration information may include information on one or more SS (Synchronization Signal) / PBCH (Physical Broadcast Channel) block indices or CSI-RS (Channel State Information Reference Signal) indices that are in a QCL (Quasi Co Located) relationship with the DMRS transmitted in the corresponding control area.

[0119] FIG. 5 is a diagram showing an example of a basic unit of time and frequency resources that constitute a downlink control channel that can be used in 5G. According to FIG. 5, the basic unit of time and frequency resources that constitute a control channel can be called a REG (Resource Element Group, 503), and the REG (503) can be defined as 1 OFDM symbol (501) on the time axis and 1 PRB (Physical Resource Block, 502) on the frequency axis, that is, 12 subcarriers. A base station can construct a downlink control channel allocation unit by concatenating REGs (503).

[0120] As illustrated in FIG. 5, if the basic unit to which a downlink control channel is allocated in 5G is called a CCE (Control Channel Element, 504), then 1 CCE (504) can be composed of a plurality of REGs (503). For example, if the plurality of REGs (503) illustrated in FIG. 5 are described, the REG (503) can be composed of 12 REs, and if 1 CCE (504) is composed of 6 REGs (503), then 1 CCE (504) can be composed of 72 REs. When a downlink control area is established, the area can be composed of a plurality of CCEs (504), and a specific downlink control channel can be mapped to and transmitted by one or a plurality of CCEs (504) according to the Aggregation Level (AL) within the control area. The CCEs (504) in the control area are distinguished by numbers, and the numbers of the CCEs (504) can be assigned according to a logical mapping method.

[0121] The basic unit of the downlink control channel, namely the REG (503) illustrated in FIG. 5, may include both the REs to which the DCI is mapped and the DMRS (505), which is a reference signal for decoding, to which the area is mapped. As shown in FIG. 5, three DMRS (505) may be transmitted within one REG (503). The number of CCEs required to transmit the PDCCH may be 1, 2, 4, 8, and 16 depending on the Aggregation Level (AL), and different numbers of CCEs may be used to implement link adaptation of the downlink control channel. For example, when AL=L, one downlink control channel may be transmitted through L CCEs. The terminal must detect the signal without knowing information about the downlink control channel, and a search space representing a set of CCEs is defined for blind decoding. A search space is a set of downlink control channel candidates consisting of CCEs that a terminal must attempt to decode on a given aggregation level, and since there are various aggregation levels that form a group of 1, 2, 4, 8, or 16 CCEs, a terminal may have multiple search spaces. A search space set can be defined as a set of search spaces on all configured aggregation levels.

[0122] Search spaces can be classified into common search spaces and UE-specific search spaces. A certain group of terminals or all terminals may examine the common search space of the PDCCH to receive cell-common control information, such as dynamic scheduling or paging messages regarding system information. For example, PDSCH scheduling allocation information for the transmission of SIBs containing cell operator information can be received by examining the common search space of the PDCCH. In the case of the common search space, since a certain group of terminals or all terminals must receive the PDCCH, it can be defined as a pre-arranged set of CCEs. Scheduling allocation information for a UE-specific PDSCH or PUSCH can be received by examining the UE-specific search space of the PDCCH. The UE-specific search space can be defined specifically as a function of the terminal's identity and various system parameters.

[0123] In 5G, parameters for the search space for a PDCCH can be configured from the base station to the terminal via upper-layer signaling (e.g., SIB, MIB, RRC signaling). For example, the base station may configure the terminal the number of PDCCH candidates at each aggregation level L, the monitoring period for the search space, the occasion for monitoring in slot-symbol units for the search space, the search space type (common search space or terminal-specific search space), the combination of DCI format and RNTI to be monitored in the search space, and / or the control plane index to be monitored in the search space. For example, information for the search space may include at least some of the following information.

[0124]

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

[0126] Based on configuration information, one or more sets of search spaces may exist in a common search space or a terminal-specific search space. For example, Search Space Set #1 and Search Space Set #2 may be configured as a common search space, and Search Space Set #3 and Search Space Set #4 may be configured as a terminal-specific search space.

[0127] In the common search space, the following combinations of DCI formats and RNTI can be monitored. Of course, they are not limited to the examples below.

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

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

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

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

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

[0133] In terminal-specific search spaces, the following combinations of DCI formats and RNTI can be monitored. Of course, they are not limited to the examples below.

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

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

[0136] The specified RNTIs may follow the definitions and uses below.

[0137] C-RNTI (Cell RNTI): Used for terminal-specific PDSCH scheduling

[0138] TC-RNTI (Temporary Cell RNTI): Used for terminal-specific PDSCH scheduling

[0139] CS-RNTI (Configured Scheduling RNTI): Used for semi-statically configured terminal-specific PDSCH scheduling.

[0140] RA-RNTI (Random Access RNTI): Used for PDSCH scheduling during the random access phase

[0141] P-RNTI (Paging RNTI): Used for PDSCH scheduling where paging is transmitted.

[0142] SI-RNTI (System Information RNTI): Used for PDSCH scheduling where system information is transmitted.

[0143] INT-RNTI (Interruption RNTI): Used to indicate whether pumcturing has occurred on PDSCH.

[0144] TPC-PUSCH-RNTI (Transmit Power Control for PUSCH RNTI): Used to instruct power control commands to the PUSCH

[0145] TPC-PUCCH-RNTI (Transmit Power Control for PUCCH RNTI): Used to instruct power control commands to the PUCCH

[0146] TPC-SRS-RNTI (Transmit Power Control for SRS RNTI): Used to instruct power regulation commands to the SRS

[0147] The aforementioned specified DCI formats may follow the definitions below.

[0148]

[0149] In 5G, the search space of aggregation level L in the control domain p and search space set s can be expressed as Equation 1 below.

[0150]

[0151] The value may be 0 for the common search space.

[0152] In the case of a terminal-specific search space, the value may correspond to a value that changes according to the terminal's identity (C-RNTI or ID set by the base station for the terminal) and the time index.

[0153] In 5G, as multiple sets of search spaces can be configured with different parameters (e.g., the parameters in Table 10), the set of search space sets monitored by the terminal at each point in time may vary. For example, if search space set #1 is configured for an X-slot period and search space set #2 is configured for a Y-slot period and X and Y are different, the terminal may monitor both search space set #1 and search space set #2 in a specific slot, and monitor either search space set #1 or search space set #2 in a specific slot.

[0154] [PDCCH: span]

[0155] A terminal can perform terminal capability reporting for cases where it has multiple PDCCH monitoring locations within a slot at each subcarrier interval, and the concept of a Span may be used. A Span refers to a sequence of consecutive symbols within a slot through which the terminal can monitor a PDCCH, and each PDCCH monitoring location is within one Span. A Span can be expressed as (X,Y), where x represents the minimum number of symbols that must be separated between the first symbols of two consecutive Spans, and Y can be referenced as the number of consecutive symbols through which a PDCCH can be monitored within one Span. In this case, the terminal can monitor a PDCCH within a Span in a segment of Y symbols from the first symbol of the Span.

[0156] FIG. 6 is a diagram illustrating, through a Span, a case in which a terminal in a wireless communication system can have multiple PDCCH monitoring locations within a slot. The Span can be (X,Y) = (7,4), (4,3), or (2,2), and each of the three cases is represented as (6-00), (6-05), and (6-10) in FIG. 6. For example, (6-00) represents the case where there are two Spans within the slot that can be represented as (7,4). The spacing between the first symbols of the two Spans is represented as X=7, and PDCCH monitoring locations can exist within a total of Y=3 symbols from the first symbol of each Span, and it indicates that search spaces 1 and 2 exist respectively within Y=3 symbols. As another example, (6-05) shows a case where there are a total of 3 spans in the slot that can be expressed as (4,3), and the distance between the second and third spans is shown to be X'=5 symbols greater than X=4.

[0157] [PDCCH: Terminal Capability Report]

[0158] The slot locations where the aforementioned common search space and terminal-specific search space are located are indicated by the monitoringSymbolsWithinSlot parameter in Table 13-1, and the symbol locations within the slot are indicated by a bitmap through the monitoringSymbolsWithinSlot parameter in Table 9. Meanwhile, the symbol locations within the slot where the terminal can monitor the search space can be reported to the base station through the following terminal capabilities (UE capabilities).

[0159] - Terminal Capability 1 (hereinafter referred to as FG 3-1). This terminal capability may refer to the capability to monitor a monitoring occasion (MO) when that MO is located within the first three symbols of the slot, provided that there is one monitoring occasion for a Type 1 and Type 3 common search space or a terminal-specific search space within the slot, as shown in Table 9a below. This terminal capability is a mandatory capability that all terminals supporting NR must support, and whether this capability is supported is not explicitly reported to the base station.

[0160]

[0161] - Terminal capability 2 (hereinafter referred to as FG 3-2). This terminal capability may be referenced as a capability that allows monitoring regardless of the starting symbol position of a monitoring occasion (MO) for a common search space or a terminal-specific search space, as shown in Table 13-2 below, when there is one monitoring occasion within the slot. This terminal capability may be optionally supported by the terminal, and support for this capability may be explicitly reported to the base station.

[0162]

[0163] - Terminal Capability 3 (hereinafter referred to as FG 3-5, 3-5a, and 3-5b). This terminal capability may indicate a pattern of monitoring occasions (MOs) that the terminal can monitor when there are multiple monitoring occasions (MOs) for a common search space or a terminal-specific search space within a slot, as shown in Table 13-3 below. The aforementioned pattern may consist of an interval X between start symbols of different MOs and a maximum symbol length Y for one MO. The combinations of (X,Y) supported by the terminal may be one or more of {(2,2), (4,3), (7,3)}. This terminal capability may be optionally supported by the terminal, and whether this capability is supported and the aforementioned combinations of (X,Y) may be explicitly reported to the base station.

[0164]

[0165]

[0166] According to one embodiment, the terminal may report to the base station whether it supports the above-described terminal capability 2 and / or terminal capability 3 and related parameters. Based on the reported terminal capability, the base station may perform time-axis resource allocation for a common search space and a terminal-specific search space. When allocating resources, the base station may ensure that the monitoring occasion (MO) is not placed in a location where the terminal cannot monitor.

[0167] [QCL, TCI state]

[0168] In a wireless communication system, one or more different antenna ports (or may be replaced by one or more channels, signals, and combinations thereof, but for convenience in the following description of the disclosure, they will be referred to collectively as different antenna ports) may be associated with each other by a QCL (Quasi co-location) setting as shown in [Table 14] below. The TCI state is intended to disclose the QCL relationship between a PDCCH (or PDCCH DMRS) and another RS ​​or channel, and when a reference antenna port A (reference RS #A) and another target antenna port B (target RS #B) are said to be QCLed with each other, it means that the terminal is allowed to apply some or all of the large-scale channel parameters estimated from the antenna port A to the channel measurement from the antenna port B. QCL may require associating different parameters depending on the situation, such as 1) time tracking affected by average delay and delay spread, 2) frequency tracking affected by Doppler shift and Doppler spread, 3) RRM (radio resource management) affected by average gain, and 4) BM (beam management) affected by spatial parameters. Accordingly, NR supports four types of QCL relationships as shown in Table 14 below.

[0169]

[0170] According to one embodiment, the spatial RX parameter may collectively refer to some or all of various parameters, such as Angle of arrival (AoA), Power Angular Spectrum (PAS) of AoA, Angle of departure (AoD), PAS of AoD, transmit / receive channel correlation, transmit / receive beamforming, and / or spatial channel correlation.

[0171] According to one embodiment, QCL relationships can be set for a terminal through the radio resource control (RRC) parameters TCI-State and QCL-Info as shown in [Table 15] below. Referring to [Table 15], the base station can set one or more TCI states for the terminal and provide up to two QCL relationships (e.g., qcl-Type1, qcl-Type2) for the RS that references the ID of the TCI state, i.e., the target RS. At this time, each QCL information (e.g., QCL-Info) included in each TCI state may include the serving cell index and BWP index of the reference RS pointed to by the QCL information, the type and ID of the reference RS, and / or a QCL type such as [Table 14].

[0172]

[0173] Figure 7 is a diagram illustrating an example of base station beam allocation according to TCI state settings.

[0174] Referring to FIG. 7, the base station can transmit information about N different beams to the terminal through N different TCI states. For example, as in FIG. 7, when N=3, the base station can notify that antenna ports referencing the different TCI states 700, 705, or 710 are associated with different spatial Rx parameters, i.e., different beams, by setting the qcl-Type2 parameters included in the three TCI states (700, 705, 710) to be associated with the CSI-RS or SSB (synchronization signal block) corresponding to the different beams and set to QCL type D.

[0175] Tables 16 through 20 below show valid TCI state settings according to the target antenna port type.

[0176] [Table 16] shows the valid TCI state settings when the target antenna port is CSI-RS for tracking (TRS). TRS can be referenced as an NZP CSI-RS in which the repetition parameter is not set and trs-Info is set to true. In [Table 16], setting 3 can be used for aperiodic TRS.

[0177] [Table 16] Valid TCI state settings when the target antenna port is CSI-RS for tracking (TRS)

[0178]

[0179] [Table 17] shows the valid TCI state settings when the target antenna port is CSI-RS for CSI. CSI-RS for CSI can be referred to as an NZP CSI-RS in which the parameter indicating repetition (e.g., the repetition parameter) is not set and trs-Info is also not set to true.

[0180] [Table 17] Valid TCI state settings when the target antenna port is CSI-RS for CSI

[0181]

[0182] [Table 18] shows the valid TCI state settings when the target antenna port is CSI-RS for beam management (BM, which is the same as CSI-RS for L1 RSRP reporting). CSI-RS for BM refers to an NZP CSI-RS in which the repetition parameter is set to On or Off and trs-Info is not set to true.

[0183] [Table 18] Valid TCI state settings when the target antenna port is CSI-RS for BM (for L1 RSRP reporting)

[0184]

[0185] Table 19 shows the valid TCI state settings when the target antenna port is a PDCCH DMRS.

[0186] [Table 19] Valid TCI state settings when the target antenna port is PDCCH DMRS

[0187]

[0188] [Table 20] shows the valid TCI state settings when the target antenna port is PDSCH DMRS.

[0189] [Table 20] Valid TCI state settings when the target antenna port is PDSCH DMRS

[0190]

[0191] A representative QCL setting method according to [Table 16] to [Table 20] is to operate by setting the target antenna port and reference antenna port for each stage as "SSB" -> "TRS" -> "CSI-RS for CSI, or CSI-RS for BM, or PDCCH DMRS, or PDSCH DMRS". Through this, it is possible to link the statistical characteristics measurable from the SSB and TRS to each antenna port to assist the reception operation of the terminal.

[0192] [PDCCH: TCI state related]

[0193] Specifically, the TCI state combinations applicable to the PDCCH DMRS antenna port are as shown in [Table 21] below. In [Table 21], the fourth row represents the combinations assumed by the terminal before RRC setup, and setup after RRC may not be possible.

[0194]

[0195] NR (new radio) can support a hierarchical signaling method as illustrated in FIG. 8 for dynamic allocation of PDCCH beams. Referring to FIG. 8, the base station can set N TCI states (805, 810, ..., 820) to the terminal through RRC signaling (800), and some of the set N TCI states can be set as TCI states for CORESET (control resource set) (825). Subsequently, the base station can instruct the terminal to one of the TCI states for CORESET (830, 835, 840) through MAC CE signaling (845). Subsequently, the terminal can receive PDCCH based on beam information contained in the TCI state indicated by the MAC CE signaling.

[0196] Figure 9 is a diagram illustrating the TCI indication MAC CE signaling structure for the above PDCCH DMRS.

[0197] Referring to FIG. 9, the TCI indication MAC CE signaling for the PDCCH DMRS consists of 2 bytes (16 bits) and may include a 5-bit serving cell ID (915), a 4-bit CORESET ID (920), and a 7-bit TCI state ID (925).

[0198] FIG. 10 is a diagram illustrating an example of beam configuration for a control resource set (CORESET) and a search space according to the above description. Referring to FIG. 10, a base station may indicate one of the TCI state lists included in the CORESET (1000) configuration through MAC CE signaling (1005). Subsequently, until another TCI state is indicated to the corresponding CORESET through another MAC CE signaling, the terminal considers that the same QCL information (beam #1, 1005) is applied to all one or more search spaces (1010, 1015, 1020) connected to the CORESET. The PDCCH beam allocation method described above has the disadvantage that it is difficult to indicate a beam change faster than the MAC CE signaling delay, and also that the same beam is applied collectively to all CORESETs regardless of search space characteristics, which makes flexible PDCCH beam operation difficult. In the embodiments of the present disclosure below, a more flexible PDCCH beam configuration and operation method is provided. In describing the embodiments of the present disclosure below, several distinct examples are provided for convenience of explanation, but they are not mutually exclusive and may be appropriately combined and applied depending on the situation.

[0199] The base station may set one or more TCI states for a specific control area for the terminal, and may activate one of the set TCI states through a MAC CE activation command. For example, if {TCI state#0, TCI state#1, TCI state#2} are set as TCI states for control area #1, the base station may transmit a command to the terminal via MAC CE to activate TCI state#0 as the TCI state for control area #1. Based on the activation command for the TCI state received via MAC CE, the terminal can correctly receive the DMRS of the corresponding control area based on the QCL information within the activated TCI state.

[0200] For a control area (control area #0) with an index set to 0, if the terminal has not received a MAC CE activation command for the TCI state of control area #0, it can be assumed that the terminal has QCL with an SS / PBCH block identified in a non-contention-based random access process that is not triggered by an initial access process or a PDCCH command for DMRS transmitted from control area #0.

[0201] For a control area (control area #X) where the index is set to a value other than 0, if the terminal has not received a TCI state for control area #X, or has received one or more TCI states but has not received a MAC CE activation command to activate one of them, it can be assumed that the terminal has QCL with the SS / PBCH block identified during the initial connection process with the DMRS transmitted from control area #X.

[0202] [PDCCH: QCL prioritization rule related]

[0203] The QCL priority determination operation for PDCCH is described below.

[0204] According to one embodiment, the terminal operates as a carrier aggregation within a single cell or band, and when multiple control resource sets existing within an active bandwidth portion of a single or multiple cells overlap in time while having the same or different QCL-TypeD characteristics during a specific PDCCH monitoring interval, the terminal selects a specific control resource set according to a QCL priority determination operation and can monitor control resource sets having the same QCL-TypeD characteristics as the selected control resource set. That is, when multiple control resource sets overlap in time, only one QCL-TypeD characteristic can be received. At this time, the criteria for determining QCL priority may be as follows.

[0205] - Criterion 1. Within the cell corresponding to the lowest index among the cells containing the common search interval, the control resource set connected to the common search interval of the lowest index.

[0206] - Criterion 2. Within the cell corresponding to the lowest index among cells containing the terminal-specific search range, the control resource set connected to the terminal-specific search range of the lowest index.

[0207] As described above, if the corresponding criterion is not satisfied, the following criterion may be applied. For example, if control resource sets overlap in time during a specific PDCCH monitoring interval, and if not all control resource sets are connected to a terminal-specific search interval rather than a common search interval, that is, if criterion 1 is not satisfied, the terminal may omit the application of criterion 1 and apply criterion 2.

[0208] When a terminal selects a control resource set based on the criteria described above, it may additionally consider two matters regarding the QCL information set in the control resource set as follows. First, if control resource set 1 has CSI-RS 1 as a reference signal having a QCL-TypeD relationship, and the reference signal having a QCL-TypeD relationship with this CSI-RS 1 is SSB 1, and another control resource set 2 has SSB 1 as a reference signal having a QCL-TypeD relationship, the terminal may consider that these two control resource sets 1 and 2 have different QCL-TypeD characteristics. Secondly, if control resource set 1 has CSI-RS 1 set in cell 1 as a reference signal having a QCL-TypeD relationship, and the reference signal having a QCL-TypeD relationship with this CSI-RS 1 is SSB 1, and control resource set 2 has CSI-RS 2 set in cell 2 as a reference signal having a QCL-TypeD relationship, and the reference signal having a QCL-TypeD relationship with this CSI-RS 2 is the same SSB 1, then the terminal can consider that the two control resource sets have the same QCL-TypeD characteristics.

[0209] FIG. 12 is a diagram illustrating a method for selecting a receivable set of control resources by considering priority when a terminal receives a downlink control channel in a wireless communication system according to an embodiment of the present disclosure. For example, the terminal may be configured to receive a plurality of control resource sets that overlap in time during a specific PDCCH monitoring section (1210), and these plurality of control resource sets may be connected to a common search space or a terminal-specific search space for a plurality of cells. Within the PDCCH monitoring section, within the first bandwidth section (1200) of cell 1, there may be a first control resource set (1215) connected to the first common search section, and within the first bandwidth section (1205) of cell 2, there may be a first control resource set (1220) connected to the first common search section and a second control resource set (1225) connected to the second terminal-specific search section. Control resource sets (1215) and (1220) have a relationship with the first CSI-RS resource and QCL-TypeD set within the first bandwidth portion of cell 1, and control resource set (1225) can have a relationship with the first CSI-RS resource and QCL-TypeD set within the first bandwidth portion of cell 2. Therefore, if reference 1 is applied to the PDCCH monitoring section (1210), all other control resource sets having a reference signal of QCL-TypeD, such as the first control resource set (1215), can be received. Therefore, the terminal can receive control resource sets (1215) and (1220) in the corresponding PDCCH monitoring section (1210). As another example, the terminal may be configured to receive multiple sets of control resources that overlap in time during a specific PDCCH monitoring interval (1240), and these multiple sets of control resources may be connected to a common search space or a terminal-specific search space for multiple cells.Within the PDCCH monitoring section, within the first bandwidth section (1230) of cell 1, there may be a first control resource set (1245) connected to a specific search section of terminal 1 and a second control resource set (1250) connected to a specific search section of terminal 2, and within the first bandwidth section (1235) of cell 2, there may be a first control resource set (1255) connected to a specific search section of terminal 1 and a second control resource set (1260) connected to a specific search section of terminal 3. Control resource sets (1245) and (1250) have a relationship with the first CSI-RS resource set within the first bandwidth portion of cell 1 and QCL-TypeD, control resource set (1255) has a relationship with the first CSI-RS resource set within the first bandwidth portion of cell 2 and QCL-TypeD, and control resource set (1260) can have a relationship with the second CSI-RS resource set within the first bandwidth portion of cell 2 and QCL-TypeD. However, if criterion 1 is applied to the corresponding PDCCH monitoring section (1240), there is no common search section, so the next criterion, criterion 2, can be applied. If criterion 2 is applied to the corresponding PDCCH monitoring section (1240), all other control resource sets having a reference signal of QCL-TypeD, such as control resource set (1245), can be received. Therefore, the terminal can receive control resource sets (1245) and (1250) in the corresponding PDCCH monitoring section (1240).

[0210] [Regarding Rate Matching / Puncturing]

[0211] Rate matching and puncturing operations are described below.

[0212] When a time and frequency resource A intended to transmit an arbitrary symbol sequence A overlaps with an arbitrary time and frequency resource B, rate matching or puncturing operations may be considered as transmission and reception operations of channel A, taking into account the area resource C where resource A and resource B overlap. Specific operations may follow the details below.

[0213] Rate Matching Operation

[0214] - According to one embodiment, a base station may transmit a symbol sequence A to a terminal by mapping channel A only to the remaining resource area, excluding resource C which corresponds to the area overlapping with resource B among all resources A. For example, if symbol sequence A consists of {Symbol #1, Symbol #2, Symbol #3, Symbol #4}, resource A is {Resource #1, Resource #2, Resource #3, Resource #4}, and resource B is {Resource #3, Resource #5}, the base station may sequentially map and send symbol sequence A to the remaining resources {Resource #1, Resource #2, Resource #4}, excluding {Resource #3} which corresponds to resource C among resources A. Consequently, the base station may transmit the symbol sequence {Symbol #1, Symbol #2, Symbol #3} by mapping it to {Resource #1, Resource #2, Resource #4}, respectively.

[0215] According to one embodiment, a terminal can determine resource A and resource B from scheduling information for a symbol sequence A from a base station, and thereby determine resource C, which is an area where resource A and resource B overlap. The terminal can receive symbol sequence A by assuming that symbol sequence A is mapped and transmitted to the remaining area of ​​resource A excluding resource C. For example, if symbol sequence A consists of {symbol #1, symbol #2, symbol #3, symbol 4}, resource A is {resource #1, resource #2, resource #3, resource #4}, and resource B is {resource #3, resource #5}, the terminal can receive symbol sequence A by assuming that it is sequentially mapped to the remaining resources {resource #1, resource #2, resource #4}, excluding {resource #3} which corresponds to resource C among resource A. Consequently, the terminal can perform a subsequent series of receiving operations assuming that the symbol sequence {Symbol #1, Symbol #2, Symbol #3} has been transmitted and mapped to {Resource #1, Resource #2, Resource #4}, respectively.

[0216] Puncturing action

[0217] If there is a resource C corresponding to an area overlapping with resource B among all resources A to which the base station intends to transmit symbol sequence A to a terminal, the base station maps symbol sequence A to the entire resource A, but does not perform transmission in the resource area corresponding to resource C, and can perform transmission only in the remaining resource area of ​​resource A excluding resource C. For example, if symbol sequence A consists of {Symbol #1, Symbol #2, Symbol #3, Symbol #4}, resource A is {Resource #1, Resource #2, Resource #3, Resource #4}, and resource B is {Resource #3, Resource #5}, the base station can map symbol sequence A {Symbol #1, Symbol #2, Symbol #3, Symbol #4} to resource A {Resource #1, Resource #2, Resource #3, Resource #4} respectively, and can transmit only the symbol sequence {Symbol #1, Symbol #2, Symbol #4} corresponding to the remaining resources {Resource #1, Resource #2, Resource #4}, excluding {Resource #3} corresponding to resource C, and may not transmit {Symbol #3} mapped to {Resource #3} corresponding to resource C. Consequently, the base station can map and transmit the symbol sequence {Symbol #1, Symbol #2, Symbol #4} to {Resource #1, Resource #2, Resource #4} respectively.

[0218] The terminal can determine resources A and B from scheduling information for symbol sequence A from the base station, and thereby determine resource C, which is the area where resources A and B overlap. The terminal can receive symbol sequence A by assuming that symbol sequence A is mapped to the entire resource A, but is transmitted only in the remaining area of ​​resource A excluding resource C. For example, if symbol sequence A consists of {Symbol #1, Symbol #2, Symbol #3, Symbol #4}, resource A is {Resource #1, Resource #2, Resource #3, Resource #4}, and resource B is {Resource #3, Resource #5}, the terminal can 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 can receive by assuming that symbol sequence {Symbol #1, Symbol #2, Symbol #4} corresponding to the remaining resources {Resource #1, Resource #2, Resource #4}—excluding {Resource #3} corresponding to resource C—is mapped and transmitted. Consequently, the terminal can perform a subsequent series of receiving operations by assuming that the symbol sequence {Symbol #1, Symbol #2, Symbol #4} has been transmitted and mapped to {Resource #1, Resource #2, Resource #4}, respectively.

[0219] In the following, a method for setting rate matching resources for the purpose of rate matching in a 5G communication system is described. For example, rate matching can be understood as adjusting the size of a signal by considering the amount of resources available to transmit the signal. For example, rate matching of a data channel can be understood as adjusting the size of the data by mapping the data channel to a specific time and frequency resource range so that it is not transmitted.

[0220] FIG. 11 is a diagram illustrating a method for a base station and a terminal to transmit and / or receive data by considering downlink data channels and rate matching resources.

[0221] FIG. 11 illustrates a downlink data channel (PDSCH, 1101) and a rate matching resource (1102). A base station may set one or more rate matching resources (1102) to a terminal through upper layer signaling (e.g., RRC signaling). The setting information for the rate matching resource (1102) may include time-axis resource allocation information (1103), frequency-axis resource allocation information (1104), and period information (1105). In the following, the bitmap corresponding to the frequency-axis resource allocation information (1104) is named the “first bitmap,” the bitmap corresponding to the time-axis resource allocation information (1103) is named the “second bitmap,” and the bitmap corresponding to the period information (1105) is named the “third bitmap.” If all or part of the time and frequency resources of a scheduled data channel (1101) overlap with a set rate matching resource (602), the base station can transmit the data channel (1101) by rate matching it in the rate matching resource (1102) portion, and the terminal can perform reception and decoding after assuming that the data channel (1101) is rate matched in the rate matching resource (1102) portion.

[0222] According to one embodiment, the base station may dynamically notify the terminal via DCI whether to rate match a data channel in the set rate matching resource portion through additional settings (corresponding to the “rate matching indicator” in the aforementioned DCI format). For example, the base station may select some of the set rate matching resources and group them into rate matching resource groups, and may indicate to the terminal via DCI using a bitmap method whether to rate match a data channel for each rate matching resource group. For example, if four rate matching resources, RMR#1, RMR#2, RMR#3, and RMR#4, are set, the base station may set RMG#1={RMR#1, RMR#2} and RMG#2={RMR#3, RMR#4} as rate matching groups, and may indicate to the terminal via a bitmap whether to rate match in RMG#1 and RMG#2, respectively, using 2 bits in the DCI field. For example, the base station may instruct the terminal to "1" if rate matching is required, and "0" if rate matching is not required.

[0223] In 5G, granularity at the “RB (resource block) symbol level” and “RE (resource element) level” is supported as a method of setting the aforementioned rate matching resources in a terminal. More specifically, the following setting method may be followed.

[0224] RB symbol level

[0225] The terminal can receive up to four RateMatchPatterns as upper layer signaling for each bandwidth portion, and one RateMatchPattern may include the following contents.

[0226] - As a Reserved Resource within the bandwidth portion, a resource may be included in which the time and frequency resource domains of the said Reserved Resource are set as a combination of an RB level bitmap and a symbol level bitmap along the frequency axis. The Reserved Resource may span across one or two slots. Additionally, a time domain pattern (periodicityAndPattern) in which the time and frequency domains composed of each RB level and symbol level bitmap pair are repeated may be additionally set.

[0227] - It may include time and frequency domain resource areas set as control resource sets within the bandwidth portion, and resource areas corresponding to time domain patterns set as search space settings where the resource areas are repeated.

[0228] RE level

[0229] The terminal can receive the following information through upper-layer signaling (e.g., RRC message).

[0230] - Configuration information for an RE corresponding to an LTE CRS (Cell-specific Reference Signal or Common Reference Signal) pattern (lte-CRS-ToMatchAround) may include the number of ports (nrofCRS-Ports) and LTE-CRS-vshift(s) values ​​(v-shift) of the LTE (long term evolution) CRS, information on the location of the LTE carrier's center subcarrier (carrierFreqDL) from a reference frequency point (e.g., reference point A), information on the LTE carrier's bandwidth (carrierBandwidthDL), and subframe configuration information (mbsfn-SubframConfigList) corresponding to a Multiast-broadcast single-frequency network (MBSFN). Based on the aforementioned information, the terminal can determine the location of the CRS within the NR slot corresponding to the LTE subframe.

[0231] - It may include configuration information for resource sets corresponding to one or more ZP (Zero Power) CSI-RS within the bandwidth portion.

[0232] [Regarding LTE CRS rate match]

[0233] Next, the rate match process for the LTE CRS described above is explained. For the coexistence of LTE (Long Term Evolution) and NR (New RAT) (LTE-NR Coexistence), NR is provided with a function to set the pattern of the LTE CRS (Cell Specific Reference Signal) to the NR terminal. For example, the above CRS pattern may be provided by RRC signaling including at least one parameter within the ServingCellConfig IE (Information Element) or ServingCellConfigCommon IE. Examples of the above parameters may include lte-CRS-ToMatchAround, lte-CRS-PatternList1-r16, lte-CRS-PatternList2-r16, crs-RateMatch-PerCORESETPoolIndex-r16, etc.

[0234] In Rel-15 NR, a function is provided to set one CRS pattern per serving cell through the above lte-CRS-ToMatchAround parameter. In Rel-16 NR, this function has been extended to enable the setting of multiple CRS patterns per serving cell. For example, for a Single-TRP (transmission and reception point) configured terminal, one CRS pattern can be set per LTE carrier, and for a Multi-TRP configured terminal, two CRS patterns can be set per LTE carrier. For example, for a Single-TRP configured terminal, up to three CRS patterns per serving cell can be set through the above lte-CRS-PatternList1-r16 parameter. As another example, for a multi-TRP configured terminal, a CRS can be set per TRP. In other words, the CRS pattern for TRP1 is set via the lte-CRS-PatternList1-r16 parameter, and the CRS pattern for TRP2 can be set via the lte-CRS-PatternList2-r16 parameter. Meanwhile, when two TRPs are configured as described above, whether the CRS patterns of both TRP1 and TRP2 are applied to a specific PDSCH (Physical Downlink Shared Channel), or whether the CRS pattern of only one TRP is applied, is determined by the crs-RateMatch-PerCORESETPoolIndex-r16 parameter; if the crs-RateMatch-PerCORESETPoolIndex-r16 parameter is set to enabled, only the CRS pattern of one TRP is applied, whereas otherwise, the CRS patterns of both TRPs are applied.

[0235] [Table 22] shows a ServingCellConfig IE including the above CRS pattern, and [Table 23] shows a RateMatchPatternLTE-CRS IE including at least one parameter for the CRS pattern.

[0236]

[0237]

[0238]

[0239] [PDSCH: Processing Time]

[0240] Next, the PDSCH processing procedure time is described. When a base station schedules a terminal to transmit a PDSCH using DCI format 1_0, 1_1, or 1_2, the terminal may require PDSCH processing time to receive the PDSCH by applying the transmission method indicated by the DCI (modulation and coding scheme (MCS), information related to the demodulation reference signal, time and frequency resource allocation information, etc.). In NR, the PDSCH processing time is defined taking this into account. The terminal's PDSCH processing time may be based on [Equation 2] below.

[0241] [Mathematical Formula 2]

[0242] T proc,1 = ( N1+ d 1,1 + d2)( 2048 + 144 ) κ2 -μ T c + T ext

[0243] The aforementioned T in mathematical formula 2 proc,1 In this, each variable can have the following meanings.

[0244] - N1: The number of symbols determined by the terminal processing capability (UE processing capability) 1 or 2 based on the terminal's capability and the numerology μ. If the terminal processing capability is reported as 1 according to the terminal capability report, it has the value in [Table 24]; if the terminal processing capability is reported as 2 and the availability of terminal processing capability 2 is established through upper-layer signaling, it may have the value in [Table 24-2]. The numerology μ is the above T proc,1 to maximize μ PDCCH , μ PDSCH, μ UL It can correspond to the minimum value among them, and μ PDCCH , μ PDSCH, μ UL Each can be referenced as the numerology of the PDCCH that scheduled the PDSCH, the numerology of the scheduled PDSCH, and the numerology of the uplink channel to which the HARQ-ACK will be transmitted.

[0245] [Table 24] shows the PDSCH processing time when the PDSCH processing capability is 1.

[0246] [Table 24-2] shows the PDSCH processing time when the PDSCH processing capability is 2.

[0247]

[0248]

[0249] - κ: 64

[0250] - T ext : If the terminal uses a shared spectrum channel access method, the terminal is T ext can be calculated and applied to the PDSCH processing time. Otherwise, T ext is assumed to be 0.

[0251] - If l1, representing the PDSCH DMRS position value, is 12, then N1,0 in [Table x2-2] above can have a value of 14, otherwise it can have a value of 13.

[0252] - For PDSCH mapping type A, if the last symbol of the PDSCH is the i-th symbol in the slot where the PDSCH is transmitted, and i < 7, then d 1,1 is 7-i, and otherwise d 1,1 It is 0.

[0253] - d2: If a PUCCH with a higher priority index overlaps with a PUCCH or PUSCH with a lower priority index in time, the d2 of the PUCCH with the higher priority index can be set to the value reported from the terminal. Otherwise, d2 is 0.

[0254] - If PDSCH mapping type B is used for terminal processing capability 1, d 1,1 The value can be determined according to L, which is the number of symbols of the scheduled PDSCH, and d, which is the number of overlapping symbols between the PDSCH scheduling the PDSCH and the scheduled PDSCH, as follows.

[0255] - If L ≥ 7, then d 1,1 = 0.

[0256] - If L ≥ 4 and L ≤ 6, then d 1,1 = 7 - L.

[0257] - If L = 3, then d 1,1 = min (d, 1)

[0258] - If L = 2, then d 1,1 = 3 + d.

[0259] - If PDSCH mapping type B is used for terminal processing capability 2, d 1,1The value can be determined according to L, which is the number of symbols of the scheduled PDSCH, and d, which is the number of overlapping symbols between the PDSCH scheduling the PDSCH and the scheduled PDSCH, as follows.

[0260] - If L ≥ 7, then d 1,1 = 0.

[0261] - If L ≥ 4 and L ≤ 6, then d 1,1 = 7 - L.

[0262] - When L = 2,

[0263] - If the scheduled PDSCH exists within a CORESET consisting of 3 symbols, and the CORESET and the scheduled PDSCH have the same starting symbol, d 1,1 = 3.

[0264] - Otherwise, d 1,1 = d.

[0265] - For a terminal that supports capability 2 within a given serving cell, the PDSCH processing time according to the terminal processing capability 2 can be applied when processingType2Enabled, which is an upper layer signaling (e.g., RRC message) for the cell, is set to enable.

[0266] If the location of the first uplink transmission symbol of the PUCCH containing HARQ-ACK information (where K1, defined as the transmission time of the HARQ-ACK, the PUCCH resources used for HARQ-ACK transmission, and timing advance effects may be considered) is T from the last symbol of the PDSCH proc,1If it does not start before the first uplink transmission symbol occurring after a specified amount of time, the terminal may transmit a valid HARQ-ACK message. That is, the terminal may transmit a PUCCH containing a HARQ-ACK only if there is sufficient PDSCH processing time. Otherwise, the terminal cannot provide the base station with valid HARQ-ACK information corresponding to the scheduled PDSCH. proc,1 It can be used for both standard and extended CPs. If it is a PDSCH consisting of two PDSCH transmission positions within a single slot, d 1,1 It can be calculated based on the first PDSCH transmission position within the slot.

[0267] [PDSCH: Readiness time during cross-carrier scheduling]

[0268] μ, the numerology to which the next scheduled PDCCH is transmitted PDCCH and μ, the numerology through which the PDSCH scheduled via the corresponding PDCCH is transmitted PDSCH In the case of different cross-carrier scheduling, N is the terminal's PDSCH reception readiness time defined for the time interval between the PDCCH and PDSCH. pdsch It is hypothesized.

[0269] If μ PDCCH < μ PDSCH In this case, the scheduled PDSCH is N from the last symbol of the PDCCH that scheduled the PDSCH. pdsch It cannot be transmitted before the first symbol of the slot following the symbol. The transmission symbol of the corresponding PDSCH may include DM-RS.

[0270] If μ PDCCH > μ PDSCH In this case, the scheduled PDSCH is N from the last symbol of the PDCCH that scheduled the PDSCH. pdschIt can be transmitted starting from the symbol. The transmission symbol of the PDSCH may include DM-RS.

[0271] [Table 25] shows N according to the scheduled PDCCH subcarrier interval. pdsch It represents.

[0272]

[0273] [Regarding SRS]

[0274] Next, a method for estimating the uplink channel using the transmission of the terminal's Sounding Reference Signal (SRS) is described. To transmit configuration information for SRS transmission to the terminal, the base station may set at least one SRS configuration for each uplink bandwidth part (BWP), and may also set at least one SRS resource set for each SRS configuration. For example, the base station and the terminal may exchange upper-level signaling information as follows to transmit information regarding the SRS resource set.

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

[0276] - srs-ResourceIdList: A set of SRS resource indices referenced by the SRS resource set

[0277] - resourceType: This is the time-axis transmission setting for the SRS resource referenced in the SRS resource set, and can be set to one of 'periodic', 'semi-persistent', or 'aperiodic'. If set to 'periodic' or 'semi-persistent', associated CSI-RS information may be provided depending on the usage of the SRS resource set. If set to 'aperiodic', a non-periodic SRS resource trigger list and slot offset information may be provided, and associated CSI-RS information may be provided depending on the usage of the SRS resource set.

[0278] - usage: A setting regarding the usage of the SRS resource referenced in the SRS resource set, which can be set to one of 'beamManagement', 'codebook', 'nonCodebook', or 'antennaSwitching'.

[0279] - alpha, p0, pathlossReferenceRS, srs-PowerControlAdjustmentStates: Provides parameter settings for controlling the transmit power of the SRS resource referenced in the SRS resource set.

[0280] The terminal can base the SRS resources included in the set of SRS resource indices referenced in the SRS resource set on the information set in the SRS resource set.

[0281] According to one embodiment, a base station and a terminal may transmit and / or receive upper-layer signaling information (e.g., RRC messages and / or MAC CE) to transmit individual configuration information for an SRS resource. For example, the individual configuration information for an SRS resource may include time-frequency axis mapping information within the slot of the SRS resource, which may include information regarding frequency hopping within or between slots of the SRS resource. Additionally, the individual configuration information for an SRS resource may include a time-axis transmission setting of the SRS resource, which may be set to 'periodic', 'semi-persistent', or 'aperiodic'. This may be limited to having the same time-axis transmission setting as the SRS resource set containing the SRS resource. If the time-axis transmission setting of the SRS resource is set to 'periodic' or 'semi-persistent', the SRS resource transmission period and slot offset (e.g., periodicityAndOffset) may additionally be included in the time-axis transmission setting.

[0282] According to one embodiment, a base station may activate or deactivate or trigger SRS transmission to a terminal through upper layer signaling, including RRC signaling or MAC CE signaling, or L1 (layer 1) signaling (e.g., DCI). For example, the base station may activate or deactivate periodic SRS transmission to the terminal through upper layer signaling. The base station may instruct the terminal to activate an SRS resource set with resourceType set to periodic through upper layer signaling, and the terminal may transmit an SRS resource referenced in the activated SRS resource set. The time-frequency axis resource mapping within the slot of the transmitted SRS resource may be based on resource mapping information set in the SRS resource, and the slot mapping, including the transmission period and slot offset, may be based on periodicityAndOffset set in the SRS resource. Additionally, the spatial domain transmission filter applied to the transmitted SRS resource may refer to spatial relation information configured in the SRS resource, or may refer to associated CSI-RS information configured in the SRS resource set containing the SRS resource. The terminal may transmit the SRS resource within an uplink BWP that is activated for a periodic SRS resource activated through upper layer signaling.

[0283] For example, a base station can enable or disable semi-persistent SRS transmission to a terminal via upper-layer signaling. The base station can instruct the terminal to activate an SRS resource set via MAC CE signaling, and the terminal can transmit an SRS resource referenced in the activated SRS resource set. The SRS resource set activated via MAC CE signaling may be limited to an SRS resource set where the resourceType is set to semi-persistent. The time-frequency axis resource mapping within the slot of the transmitted SRS resource may be based on resource mapping information set in the SRS resource, and the slot mapping, including the transmission period and slot offset, may be based on periodicityAndOffset set in the SRS resource. Additionally, the spatial domain transmission filter applied to the transmitted SRS resource may refer to spatial relation info set in the SRS resource, or may refer to associated CSI-RS information set in the SRS resource set containing the SRS resource. If spatial relation info is configured in the SRS resource, the spatial domain transmission filter can be determined based on the configuration information regarding the spatial relation info transmitted via MAC CE signaling that enables semi-persistent SRS transmission without adhering to it. The terminal can transmit the SRS resource within the uplink BWP enabled for the semi-persistent SRS resource activated via upper layer signaling.

[0284] For example, a base station can trigger an aperiodic SRS transmission to a terminal via the DCI. The base station can indicate one of the aperiodic SRS resource triggers via the SRS request field of the DCI. The terminal may understand that an SRS resource set containing the aperiodic SRS resource trigger indicated via the DCI has been triggered from the list of aperiodic SRS resource triggers among the configuration information of the SRS resource set. The terminal can transmit the SRS resource referenced in the triggered SRS resource set. The time-frequency axis resource mapping within the slot of the transmitted SRS resource may be based on the resource mapping information set in the SRS resource. Additionally, the slot mapping of the transmitted SRS resource may be determined through the slot offset between the PDCCH containing the DCI and the SRS resource, which may be based on the value(s) included in the set of slot offsets set in the SRS resource set. Specifically, the slot offset between the PDCCH containing the DCI and the SRS resource may be the value specified in the time domain resource assignment field of the DCI from among the offset value(s) included in the slot offset set configured in the SRS resource set. Additionally, the spatial domain transmission filter applied to the transmitted SRS resource may refer to the spatial relation info configured in the SRS resource or the associated CSI-RS information configured in the SRS resource set containing the SRS resource. The terminal may transmit the SRS resource within an uplink BWP that is enabled for a non-periodic SRS resource triggered via the DCI.

[0285] According to one embodiment, when a base station triggers aperiodic SRS transmission to a terminal via a DCI, a minimum time interval may be required between the PDCCH containing the DCI that triggers the aperiodic SRS transmission and the transmitted SRS so that the terminal applies configuration information for the SRS resource to transmit the SRS. For example, the time interval for the terminal's SRS transmission may be defined as the number of symbols between the last symbol of the PDCCH containing the DCI that triggers the aperiodic SRS transmission and the first symbol to which the first transmitted SRS resource among the transmitted SRS resource(s) is mapped. For example, the minimum time interval may be determined based on the PUSCH preparation procedure time required for the terminal to prepare for PUSCH transmission. Additionally, the minimum time interval may have different values ​​depending on the usage of the SRS resource set including the transmitted SRS resource. For example, the minimum time interval may be determined by N2 symbols defined by considering the terminal's processing capability according to the terminal's capability, referencing the terminal's PUSCH preparation procedure time. Additionally, considering the usage of the SRS resource set including the transmitted SRS resource, if the usage of the SRS resource set is set to 'codebook' or 'antennaSwitching', the minimum time interval is determined to be N2 symbols, and if the usage of the SRS resource set is set to 'nonCodebook' or 'beamManagement', the minimum time interval can be determined to be N2+14 symbols.The terminal transmits an aperiodic SRS when the time interval for the aperiodic SRS transmission is greater than or equal to the minimum time interval, and can ignore the DCI that triggers the aperiodic SRS when the time interval for the aperiodic SRS transmission is less than the minimum time interval.

[0286]

[0287]

[0288] The spatialRelationInfo setting information in [Table 26] is intended to apply to the beam information of a reference signal (e.g., the beam used for the SRS transmission) by referencing a single reference signal. For example, the spatialRelationInfo setting may include information such as that shown in [Table 27] below.

[0289]

[0290] When referring to the spatialRelationInfo setting, an SS / PBCH block index, a CSI-RS index, or an SRS index can be set as the index of the reference signal to be referenced in order to use the beam information of a specific reference signal. The upper signaling referenceSignal is configuration information indicating which reference signal's beam information to reference for the corresponding SRS transmission, and ssb-Index can mean the SS / PBCH block index, csi-RS-Index the CSI-RS index, and srs the SRS index, respectively. If the value of the upper signaling referenceSignal is set to 'ssb-Index', the terminal can apply the receiving beam used when receiving the SS / PBCH block corresponding to ssb-Index as the transmitting beam for the corresponding SRS transmission. If the value of the upper signaling referenceSignal is set to 'csi-RS-Index', the terminal can apply the receiving beam used when receiving the CSI-RS corresponding to csi-RS-Index as the transmitting beam for the corresponding SRS transmission. If the value of the upper signaling referenceSignal is set to 'srs', the terminal can apply the transmission beam used during the transmission of the SRS corresponding to srs as the transmission beam for the transmission of the SRS.

[0291] [PUSCH: Regarding transmission method]

[0292] Next, the scheduling method for PUSCH transmissions is described. PUSCH transmissions can be dynamically scheduled by an uplink (UL) grant within the DCI, or operated by a configured grant Type 1 or Type 2. Dynamic scheduling instructions for PUSCH transmissions can be provided by DCI format 0_0 or 0_1.

[0293] Configured grant Type 1 PUSCH transmissions can be semi-statically configured by receiving configuredGrantConfig, which includes rrc-ConfiguredUplinkGrant of [Table 28], through the upper signaling, without receiving UL grants within the DCI. Configured grant Type 2 PUSCH transmissions can be semi-continuously scheduled by UL grants within the DCI after receiving configuredGrantConfig, which does not include rrc-ConfiguredUplinkGrant of [Table 28], through the upper signaling. When PUSCH transmissions are operated by configured grants, parameters applied to the PUSCH transmissions can be applied through configuredGrantConfig, the upper signaling of [Table 28], with the exception of dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, and scaling of UCI-OnPUSCH, which are provided by pusch-Config, the upper signaling of [Table 29]. If the terminal is provided with transformPrecoder in configuredGrantConfig, which is the upper signaling of [Table 28], the terminal can apply tp-pi2BPSK in pusch-Config of [Table 29] to PUSCH transmissions operated by the configured grant.

[0294]

[0295]

[0296] Next, the PUSCH transmission method is described. The DMRS antenna port for PUSCH transmission can be substantially the same as the antenna port for SRS transmission. PUSCH transmission can be based on a codebook-based transmission method and a non-codebook-based transmission method, respectively, depending on whether the value of txConfig in pusch-Config of the upper signaling [Table x2-4] is 'codebook' or 'nonCodebook'.

[0297] As described above, PUSCH transmissions can be dynamically scheduled via DCI format 0_0 or 0_1 and semi-statically configured by a configured grant. If a terminal is instructed to schedule a PUSCH transmission via DCI format 0_0, the terminal performs beam configuration for the PUSCH transmission using the pucch-spatialRelationInfoID corresponding to the terminal-specific PUCCH resource corresponding to the minimum ID within the active uplink BWP in the serving cell, wherein the PUSCH transmission is based on a single antenna port. The terminal does not expect scheduling for the PUSCH transmission via DCI format 0_0 within a BWP where the PUCCH resource containing the pucch-spatialRelationInfo is not configured. If the terminal is not configured with txConfig within pusch-Config of [Table 29], the terminal may not expect to be scheduled via DCI format 0_1.

[0298]

[0299]

[0300] Next, codebook-based PUSCH transmission is described. Codebook-based PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1 and can operate semi-statically via a configured grant. When codebook-based PUSCH is dynamically scheduled via DCI format 0_1 ​​or semi-statically configured via a configured grant, the terminal can determine a precoder for PUSCH transmission based on the SRS Resource Indicator (SRI), Transmission Precoding Matrix Indicator (TPMI), and the transmission rank (number of PUSCH transmission layers).

[0301] In this case, the SRI can be provided via the SRS resource indicator field within the DCI or configured to the terminal via the higher-level signaling srs-ResourceIndicator. During codebook-based PUSCH transmission, the terminal is configured with at least one SRS resource and can be configured with up to two. When the terminal receives an SRI via the DCI, the SRS resource indicated by that SRI may be referenced as the SRS resource corresponding to the SRI among the SRS resources transmitted prior to the PDCCH containing that SRI. Additionally, the TPMI and transmission rank can be provided via the precoding information and number of layers field within the DCI or configured to the terminal via the higher-level signaling precodingAndNumberOfLayers. The TPMI can be used to indicate the precoder applied to the PUSCH transmission. If the terminal is configured with one SRS resource, the TPMI is used to indicate the precoder to be applied from that configured SRS resource. If the terminal is configured with multiple SRS resources, TPMI can be used to specify the precoder to be applied to the SRS resource indicated by SRI.

[0302] The precoder to be used for PUSCH transmission can be selected from an uplink codebook having the same number of antenna ports as the nrofSRS-Ports value in the upper signaling SRS-Config. In codebook-based PUSCH transmission, the terminal determines the codebook subset based on TPMI and the codebookSubset in the upper signaling pusch-Config. The codebookSubset in the upper signaling pusch-Config can be set to one of 'fullyAndPartialAndNonCoherent', 'partialAndNonCoherent', or 'nonCoherent' based on the UE (user equipment) capability reported by the terminal to the base station. If the terminal reports 'partialAndNonCoherent' as the UE capability, the terminal does not expect the value of the upper signaling codebookSubset to be set to 'fullyAndPartialAndNonCoherent'. Additionally, if the terminal reports 'nonCoherent' as a UE capability, the terminal does not expect the value of the parent signaling codebookSubset to be set to 'fullyAndPartialAndNonCoherent' or 'partialAndNonCoherent'. If nrofSRS-Ports in the parent signaling SRS-ResourceSet points to two SRS antenna ports, the terminal does not expect the value of the parent signaling codebookSubset to be set to 'partialAndNonCoherent'.

[0303] According to one embodiment, a terminal may receive one SRS resource set in which the value of usage within the upper signaling SRS-ResourceSet is set to 'codebook', and one SRS resource within the said SRS resource set may be indicated via SRI. If multiple SRS resources are set within the SRS resource set in which the value of usage within the upper signaling SRS-ResourceSet is set to 'codebook', the terminal may expect that the value of nrofSRS-Ports within the upper signaling SRS-Resource will be set to the same value for all SRS resources.

[0304] According to one embodiment, a terminal may transmit one or more SRS resources included in an SRS resource set in which the value of usage is set to 'codebook' according to upper signaling to a base station, and the base station selects one of the SRS resources transmitted by the terminal and instructs the terminal to perform PUSCH transmission using the transmit beam information of the corresponding SRS resource. In this case, in codebook-based PUSCH transmission, SRI is used as information to select the index of one SRS resource and may be included in the DCI. Additionally, the base station includes information in the DCI that instructs the TPMI and rank to be used by the terminal for PUSCH transmission. The terminal performs PUSCH transmission by using the SRS resource instructed by the SRI, applying the instructed rank based on the transmit beam of the corresponding SRS resource and the precoder instructed by the TPMI.

[0305] Next, non-codebook-based PUSCH transmission is described. Non-codebook-based PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1 and can operate semi-statically via configured grant. If at least one SRS resource is configured in an SRS resource set in which the value of usage within SRS-ResourceSet, which is a higher-level signaling (e.g., RRC message), is set to 'nonCodebook', the terminal can receive a non-codebook-based PUSCH transmission scheduled via DCI format 0_1.

[0306] For an SRS resource set in which the value of usage within the upper signaling SRS-ResourceSet is set to 'nonCodebook', the terminal can receive one connected NZP CSI-RS resource (non-zero power CSI-RS). The terminal can perform calculations for a precoder for SRS transmission by measuring the NZP CSI-RS resource 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 at the terminal is less than 42 symbols, the terminal may not expect the information for the precoder for SRS transmission to be updated.

[0307] If the value of resourceType in the upper signaling SRS-ResourceSet is set to 'aperiodic', the connected NZP CSI-RS can be indicated by the SRS request field in DCI format 0_1 ​​or 1_1. In this case, if the connected NZP CSI-RS resource is a non-periodic NZP CSI-RS resource, the existence of the connected NZP CSI-RS is indicated if the value of the SRS request field in DCI format 0_1 ​​or 1_1 is not '00'. In this case, the corresponding DCI must not indicate cross-carrier or cross-BWP scheduling. Additionally, if the value of the SRS request indicates the existence of the NZP CSI-RS, the NZP CSI-RS is located in the slot where the PDCCH containing the SRS request field was transmitted. In this case, the TCI states set on the scheduled subcarrier are not set to QCL-TypeD.

[0308] If a periodic or semi-persistent SRS resource set is established, the associated NZP CSI-RS can be indicated via the associated CSI-RS within the parent signaling SRS-ResourceSet. For non-codebook-based transmissions, the terminal does not expect the parent signaling spatialRelationInfo for the SRS resource and the associated CSI-RS within the parent signaling SRS-ResourceSet to be established together.

[0309] When a terminal is configured with multiple SRS resources, it can determine the precoder and transmission rank to be applied to PUSCH transmission based on the SRI indicated by the base station. In this case, the SRI may be indicated via the field SRS resource indicator within the DCI or configured via the higher-level signaling srs-ResourceIndicator. Similar to the codebook-based PUSCH transmission described above, when the terminal receives the SRI via the DCI, the SRS resource indicated by the provided SRI may be referenced as the SRS resource corresponding to the SRI among the SRS resources transmitted prior to the PDCCH containing the SRI. The terminal may use one or multiple SRS resources for SRS transmission, and the maximum number of SRS resources that can be transmitted simultaneously within the same symbol in a single SRS resource set, as well as the maximum number of SRS resources, are determined by the UE capability reported by the terminal to the base station. In this case, SRS resources transmitted simultaneously by the terminal may occupy the same RB. The terminal may configure one SRS port for each SRS resource. Only one SRS resource set can be configured with the value of usage in the upper signaling SRS-ResourceSet set set to 'nonCodebook', and up to four SRS resources can be configured for non-codebook based PUSCH transmission.

[0310] According to one embodiment, a base station transmits one NZP-CSI-RS connected to an SRS resource set to a terminal, and the terminal can calculate a precoder to be used when transmitting one or more SRS resources within the SRS resource set based on the results measured upon receiving the NZP-CSI-RS. When the terminal transmits one or more SRS resources within an SRS resource set with usage set to 'nonCodebook' to the base station, the terminal applies the calculated precoder, and the base station can select one or more SRS resources from among the received one or more SRS resources. At this time, in non-codebook-based PUSCH transmission, the SRI represents an index capable of expressing a combination of one or more SRS resources, and the SRI may be included within the DCI. In this case, the number of SRS resources indicated by the SRI transmitted by the base station can be the number of transmission layers of PUSCH, and the terminal can transmit PUSCH by applying the precoder applied to the transmission of SRS resources to each layer.

[0311] [PUSCH: Preparation Process Time]

[0312] Next, the PUSCH preparation procedure time is described. When a base station schedules a terminal to transmit a PUSCH using DCI format 0_0, 0_1, or 0_2, the terminal may require PUSCH preparation procedure time to transmit the PUSCH by applying the transmission method specified through the DCI (e.g., transmission precoding method of the SRS resource, number of transmission layers, spatial domain transmission filter). In NR, the PUSCH preparation procedure time has been defined with this in mind. The terminal's PUSCH preparation procedure time may follow [Equation 3] below.

[0313] [Mathematical Formula 3]

[0314] T proc,2 = max(( N2+ d 2,1 + d2)( 2048 + 144 ) κ2 -μ Tc + T ex t + T switch , d 2,2 )

[0315] The aforementioned T in mathematical formula 3 proc,2 In this, each variable can have the following meanings.

[0316] - N2: A number of symbols determined by the terminal processing capability (UE processing capability) 1 or 2 and the numerology μ according to the terminal's capability. If the terminal processing capability is reported as 1 according to the terminal's capability report, it has the value of [Table 30], and if the terminal processing capability is reported as 2 and the ability to use terminal processing capability 2 is set through upper layer signaling, it may have the value of [Table 31].

[0317] [Table 30]

[0318]

[0319] [Table 31]

[0320]

[0321] - d 2,1 : The number of symbols determined as 0 if the resource elements of the first OFDM symbol of the PUSCH transmission are all configured to consist only of DM-RS, and 1 otherwise.

[0322] - κ: 64

[0323] - μ: μ DL or μ UL Middle, T proc,2 It follows the value that becomes larger. μ DL can be referenced as the numerology of the downlink through which a PDCCH containing a DCI scheduling PUSCH is transmitted, and μ UL can be referenced as the numerology of the uplink through which PUSCH is transmitted.

[0324] - T c : , , has.

[0325] - d 2,2 : If the DCI scheduling PUSCH directs BWP switching, follow the BWP switching time; otherwise, have 0.

[0326] - d2: If the OFDM symbols of PUCCH, PUSCH with a higher priority index, and PUCCH with a lower priority index overlap in time, the d2 value of PUSCH with the higher priority index is used. Otherwise, d2 is 0.

[0327] - T ext : If the terminal uses a shared spectrum channel access method, the terminal is T ext It can be calculated and applied to the PUSCH preparation process time. Otherwise, T ext is assumed to be 0.

[0328] - T switch: T when the uplink switching interval is triggered switch is assumed to be the switching interval time. Otherwise, it is assumed to be 0.

[0329] When the base station and terminal consider the time-axis resource mapping information of the PUSCH scheduled via DCI and the influence of uplink-downlink timing advance, from the last symbol of the PDCCH including the DCI that scheduled the PUSCH, T proc,2 Subsequently, if the first symbol of the PUSCH starts before the first uplink symbol initiated by the CP, it can be determined that the PUSCH preparation time is insufficient. Otherwise, the base station and the terminal can determine that the PUSCH preparation time is sufficient. The terminal transmits the PUSCH only if the preparation time is sufficient, and can ignore the DCI scheduling the PUSCH if the preparation time is insufficient.

[0330] [PUSCH: Repetitive transmission related]

[0331] The following describes the repetitive transmission of uplink data channels in a 5G system. 5G systems support two types of repetitive transmission methods for uplink data channels: PUSCH repetitive transmission type A and PUSCH repetitive transmission type B. A terminal can receive either PUSCH repetitive transmission type A or B as a setting for upper layer signaling.

[0332] PUSCH Repeated Transmission Type A

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

[0334] - The terminal may repeatedly transmit an uplink data channel in consecutive slots in which the length and start symbol of the uplink data channel configured based on the number of repeated transmissions received from the base station are substantially the same. In this case, if at least one of the slots configured as downlink by the base station to the terminal, or at least one of the symbols of the uplink data channel configured to the terminal, is configured as downlink, the terminal may omit the transmission of the uplink data channel, but the number of repeated transmissions of the uplink data channel may be counted.

[0335] PUSCH Repeated Transmission Type B

[0336] - As described above, in order to allocate time domain resources within a single slot, the start symbol and length of the uplink data channel are determined, and the base station may notify the terminal of the number of repetitions through upper signaling (e.g., RRC signaling) or L1 signaling (e.g., DCI).

[0337] - Based on the start symbol and length of the uplink data channel configured first, the nominal repetition of the uplink data channel is determined as follows. The slot where the nth nominal repetition starts is The symbol given by and starting in that slot is It can be given by. The slot where the nth nominal repetition ends is The symbol given by and ending in that slot is It is given by, where n=0,..., numberofrepetitions-1 and S represents the start symbol of the configured uplink data channel, L represents the symbol length of the configured uplink data channel. K s indicates the slot where the PUSCH transmission starts. Indicates the number of symbols per slot.

[0338] - The terminal can determine invalid symbols for PUSCH repeat transmission type B. Symbols configured for the downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated can be determined as invalid symbols for PUSCH repeat transmission type B. Additionally, invalid symbols can be set in upper layer parameters (e.g., InvalidSymbolPattern). Invalid symbols can be set in upper layer parameters (e.g., InvalidSymbolPattern) by providing a symbol-level bitmap spanning one or two slots. In the bitmap, 1 represents an invalid symbol. Additionally, the periodicity and pattern of the bitmap can be set through upper layer parameters (e.g., periodicityAndPattern). If an upper layer parameter (e.g., InvalidSymbolPattern) is set and the InvalidSymbolPatternIndicator-ForDCIFormat0_1 or InvalidSymbolPatternIndicator-ForDCIFormat0_2 parameter indicates 1, the terminal applies the invalid symbol pattern, and if the parameter indicates 0, the terminal does not apply the invalid symbol pattern. If an upper layer parameter (e.g., InvalidSymbolPattern) is set and the InvalidSymbolPatternIndicator-ForDCIFormat0_1 or InvalidSymbolPatternIndicator-ForDCIFormat0_2 parameter is not set, the terminal applies the invalid symbol pattern.

[0339] After an invalid symbol is determined, for each nominal repetition, the terminal may identify symbols other than the invalid symbol as valid symbols. If one or more valid symbols are included in each nominal repetition, the nominal repetition may include one or more actual repetitions. Here, each actual repetition contains a consecutive set of valid symbols that can be used for PUSCH repeat transmission type B within a single slot.

[0340] FIG. 14 is a drawing illustrating an example of PUSCH repeat transmission type B in a wireless communication system according to one embodiment of the present disclosure.

[0341] Referring to FIG. 14, a terminal according to one embodiment may have the start symbol S of the uplink data channel set to 0 and the length L of the uplink data channel set to 14, and the number of repeated transmissions set to 16. In this case, the nominal repetition may be represented in 16 consecutive slots (1401). Then, the terminal may determine that the symbol set as the downlink symbol in each nominal repetition (1401) is an invalid symbol. Additionally, the terminal may determine that the symbols set to 1 in the invalid symbol pattern (1402) are invalid symbols. In each nominal repetition, if valid symbols that are not invalid symbols are composed of one or more consecutive symbols in one slot, they may be set as an actual repetition and transmitted (1403).

[0342] In addition, for PUSCH repeated transmissions, NR Release 16 may define the following additional methods for UL grant-based PUSCH transmissions that cross slot boundaries and configured grant-based PUSCH transmissions.

[0343] - Method 1 (mini-slot level repetition): Through a single UL grant, two or more PUSCH repeat transmissions are scheduled within a single slot or across the boundaries of consecutive slots. Additionally, for Method 1, the time-domain resource allocation information within the DCI indicates the resources for the first repeat transmission. Furthermore, the time-domain resource information for the remaining repeat transmissions can be determined based on the time-domain resource information of the first repeat transmission and the uplink or downlink direction determined for each symbol in each slot. Each repeat transmission occupies consecutive symbols.

[0344] - Method 2 (multi-segment transmission): Two or more PUSCH (physical uplink shared channel) repeat transmissions may be scheduled in consecutive slots through a single UL grant. In this case, one transmission is designated per slot, and each transmission may have a different start point or repeat length. Additionally, in Method 2, time-domain resource allocation information within the DCI may indicate the start point and repeat length of all repeat transmissions. Furthermore, when repeat transmissions are performed within a single slot via Method 2, if there are multiple consecutive uplink symbol bundles within that slot, each repeat transmission may be performed for each uplink symbol bundle. If there is only a unique consecutive uplink symbol bundle within that slot, one PUSCH repeat transmission may be performed according to the method of NR Release 15.

[0345] - Method 3: Two or more repeated PUSCH transmissions may be scheduled in consecutive slots through two or more UL grants. In this case, one transmission is assigned per slot, and the n-th UL grant may be received before the PUSCH transmission scheduled by the n-1-th UL grant is finished.

[0346] - Method 4: Through one UL grant or one configured grant, one or more PUSCH repeat transmissions within a single slot, or two or more PUSCH repeat transmissions across the boundaries of consecutive slots, may be supported. The number of repeats instructed by the base station to the terminal is merely a nominal value, and the number of PUSCH repeat transmissions actually performed by the terminal may be greater than the nominal number of repeats. Time-domain resource allocation information within the DCI or within the configured grant may be referenced as the resource for the first repeat transmission instructed by the base station. The time-domain resource information for the remaining repeat transmissions may be determined by referencing at least the resource information of the first repeat transmission and the uplink or downlink direction of the symbols. If the time-domain resource information for the repeat transmission instructed by the base station spans a slot boundary or includes an uplink / downlink switching point, the repeat transmission may be divided into multiple repeat transmissions. In this case, one repeat transmission may be included within a single slot for each uplink period.

[0347] The repetitive transmission described above may be applicable to both DG (Dynamic Grant) PUSCH and CG (Configured Grant) PUSCH. DG PUSCH is a method in which all PUSCH scheduling information is provided by the DCI, and CG PUSCH can be referenced as a method in which PUSCH scheduling information is provided only by the upper signal or by some DCI. Additionally, DG PUSCH is a method in which the terminal transmits PUSCH only within the scheduling area provided by the DCI, and CG PUSCH can be referenced as a method in which the terminal periodically transmits PUSCH without receiving a separate DCI in accordance with the period set by the upper signal.

[0348] [PUSCH: Frequency Hopping Process]

[0349] Frequency hopping of the uplink data channel (Physical Uplink Shared Channel; PUSCH) in a 5G system is explained below.

[0350] In 5G, two methods can be supported for each PUSCH repeat transmission type as the frequency hopping method for the uplink data channel. First, in PUSCH repeat transmission type A, intra-slot frequency hopping and inter-slot frequency hopping are supported, and in PUSCH repeat transmission type B, inter-repetition frequency hopping and inter-slot frequency hopping can be supported.

[0351] The intra-slot frequency hopping method supported by PUSCH repeat transmission type A may be a method in which a terminal transmits by changing the allocated resources in the frequency domain by a set frequency offset at two hops within a single slot. In intra-slot frequency hopping, the starting RB of each hop can be represented by Equation 4.

[0352] [Mathematical Formula 4]

[0353]

[0354] In mathematical equation 4, i=0 and i=1 represent the first hop and the second hop, respectively, and represents the starting RB within the UL BWP and can be calculated from the frequency resource allocation method. It represents the frequency offset between two hops through the upper-layer parameters. The number of symbols in the first hop is It can be represented as, and the number of symbols for the second hop is It can be represented as. is the length of PUSCH transmission within one slot, represented by the number of OFDM (Orthogonal frequency division multiplexing) symbols.

[0355] Next, the inter-slot frequency hopping method supported by PUSCH repetitive transmission types A and B is a method in which the terminal transmits by changing the allocated resource in the frequency domain by a set frequency offset for each slot. In inter-slot frequency hopping The starting RB during the slot can be represented through mathematical formula 5.

[0356] [Mathematical Formula 5]

[0357]

[0358] In mathematical formula 5, is the current slot number in a multi-slot PUSCH transfer, represents the starting RB within the UL BWP and can be calculated from the frequency resource allocation method. It can represent the frequency offset between two hops through upper layer parameters.

[0359] Next, the inter-repetition frequency hopping method supported by PUSCH repeat transmission type B may involve transmitting resources allocated in the frequency domain for one or more actual repetitions within each nominal repetition, shifted by a set frequency offset. In the frequency domain for one or more actual repetitions within the nth nominal repetition, RB, which is the index of the starting RB, start (n) can follow the following mathematical formula 6.

[0360] [Mathematical Formula 6]

[0361]

[0362] In mathematical equation 6, n is the index of the nominal repetition, can represent the RB offset between two hops through the upper layer parameter.

[0363] [PUSCH: multiplexing rule when AP / SP CSI reporting]

[0364] The following describes a method for measuring and reporting channel state in a 5G communication system. Channel state information (CSI) may include channel quality information (CQI), precoding matrix index (PMI), CSI-RS resource indicator (CRI), SS / PBCH block resource indicator (SSSBRI), layer indicator (LI), rank indicator (RI), and / or L1-RSRP (Reference Signal Received Power). A base station may control time and frequency resources for the aforementioned CSI measurement and reporting by a terminal.

[0365] For the aforementioned CSI measurement and reporting, the terminal may receive setting information for N (≥1) CSI reports (CSI-ReportConfig), setting information for M (≥1) RS transmission resources (CSI-ResourceConfig), and / or one or two trigger state lists (CSI-AperiodicTriggerStateList, CSI-SemiPersistentOnPUSCH-TriggerStateList) via upper layer signaling (e.g., RRC message, MAC CE). More specifically, the setting information for the aforementioned CSI measurement and reporting may be as described below in [Table 32] to [Table 38].

[0366] [Table 32] describes CSI-ReportConfig.

[0367]

[0368]

[0369]

[0370]

[0371]

[0372] [Table 33] shows CSI-ResourceConfig.

[0373]

[0374]

[0375] [Table 34] shows NZP-CSI-RS-ResourceSet.

[0376]

[0377]

[0378] [Table 35] shows CSI-SSB-ResourceSet.

[0379]

[0380] [Table 36] shows CSI-IM-ResourceSet.

[0381]

[0382]

[0383] [Table 37] shows the CSI-AperiodicTriggerStateList.

[0384]

[0385]

[0386]

[0387] [Table 38] shows CSI-SemiPersistentOnPUSCH-TriggerStateList.

[0388]

[0389] Regarding the aforementioned CSI report setting (CSI-ReportConfig), each report setting CSI-ReportConfig may be associated with a single downlink (DL) bandwidth portion identified by the upper-layer parameter bandwidth portion identifier (bwp-id) given by the CSI-ResourceConfig, which is associated with the corresponding report setting. As for the time domain reporting operation for each report setting CSI-ReportConfig, 'Aperiodic', 'Semi-Persistent', or 'Periodic' methods may be supported, and the method may be set from the base station to the terminal by the reportConfigType parameter set from the upper layer. Semi-persistent CSI reporting methods may support 'PUCCH-based semi-persistent (semi-PersistentOnPUCCH)' and 'PUSCH-based semi-persistent (semi-PersistentOnPUSCH)'. In the case of a periodic or semi-permanent CSI reporting method, the terminal may receive a PUCCH or PUSCH resource to transmit the CSI from the base station via upper layer signaling. The period and slot offset of the PUCCH or PUSCH resource to transmit the CSI may be given as the numerology of the uplink (UL) bandwidth portion configured for transmitting the CSI report. In the case of a non-periodic CSI reporting method, the terminal may receive a PUSCH resource to transmit the CSI scheduled from the base station via L1 signaling (the aforementioned DCI format 0_1).

[0390] According to one embodiment, for the aforementioned CSI resource setting (CSI-ResourceConfig), each CSI resource setting CSI-ReportConfig may include S (≥1) CSI resource sets (given by the upper-level parameter csi-RS-ResourceSetList). The CSI resource set list may consist of non-zero power (NZP) CSI-RS resource sets and SS / PBCH block sets, or may consist of CSI-interference measurement (CSI-IM) resource sets. Each CSI resource setting may be located in a downlink (DL) bandwidth portion identified by the upper-level parameter bwp-id, and the CSI resource setting may be linked to a CSI report setting in the same downlink bandwidth portion. The time domain operation of the CSI-RS resources within the CSI resource setting may be set to one of 'non-periodic', 'periodic', or 'semi-permanent' by the upper-level parameter resourceType. For periodic or semi-permanent CSI resource settings, the number of CSI-RS resource sets may be limited to S=1, and the set period and slot offset may be given by the numerology of the downlink bandwidth portion identified by bwp-id. The terminal may receive one or more CSI resource settings for channel or interference measurement from the base station via upper layer signaling, and may include, for example, the following CSI resources.

[0391] - CSI-IM resources for interference measurement

[0392] - NZP CSI-RS resources for interference measurement

[0393] - NZP CSI-RS resources for channel measurement

[0394] For CSI-RS resource sets associated with a resource setting where the upper-level parameter resourceType is set to 'Aperiodic', 'Periodic', or 'Semi-permanent', the Trigger State for a CSI reporting setting where reportType is set to 'Aperiodic' and the resource setting for channel or interference measurements for one or more component cells (CC) can be set as the upper-level parameter CSI-AperiodicTriggerStateList.

[0395] Non-periodic CSI reporting of the terminal can be performed using PUSCH, periodic CSI reporting can be performed using PUCCH, and semi-permanent CSI reporting can be performed using PUSCH when triggered or activated by DCI, and using PUCCH after being activated by the MAC control element (MAC CE). As described above, CSI resource settings can also be configured non-periodic, periodic, or semi-permanent. Combinations between CSI reporting settings and CSI resource settings can be supported based on [Table 39] below.

[0396]

[0397] Aperiodic CSI reporting can be triggered by the “CSI request” field of the aforementioned DCI format 0_1, which corresponds to the scheduling DCI for PUSCH. The terminal can monitor PDCCH, obtain DCI format 0_1, and obtain scheduling information and CSI request indicators for PUSCH. The CSI request indicator can be set to NTS (=0, 1, 2, 3, 4, 5, or 6) bits and can be determined by the upper layer signaling (reportTriggerSize). One trigger state among one or more aperiodic CSI reporting trigger states that can be set by the upper layer signaling (CSI-AperiodicTriggerStateList) can be triggered by the CSI request indicator.

[0398] - If all bits of the CSI request field are 0, this may be referenced as not requesting a CSI report.

[0399] - If the number of CSI trigger states (M) in the configured CSI-AperiodicTriggerStateLite is greater than 2NTs-1, then M CSI trigger states can be mapped to 2NTs-1 according to a predefined mapping relationship, and one of the trigger states of 2NTs-1 can be indicated as a CSI request field.

[0400] - If the number of CSI trigger states (M) in the configured CSI-AperiodicTriggerStateLite is less than or equal to 2NTs-1, one of the M CSI trigger states may be indicated as a CSI request field.

[0401] The following [Table 40] shows an example of the relationship between a CSI request indicator and a CSI trigger state that can be indicated by that indicator.

[0402]

[0403] According to one embodiment, the terminal can perform a measurement on a CSI resource within a CSI trigger state triggered by a CSI request field and generate a CSI therefrom (e.g., including at least one of the aforementioned CQI, PMI, CRI, SSBRI, LI, RI, or L1-RSRP). The terminal can transmit the acquired CSI using a PUSCH scheduled by the corresponding DCI format 0_1. When a 1-bit corresponding to the uplink data indicator (UL-SCH indicator) in DCI format 0_1 ​​indicates “1”, the terminal can multiplex the uplink data (UL-SCH) and the acquired CSI and transmit them to the PUSCH resource scheduled by DCI format 0_1. When the 1 bit corresponding to the uplink data indicator (UL-SCH indicator) in DCI format 0_1 ​​indicates “0”, the terminal can transmit by mapping only the CSI without the uplink data (UL-SCH) to the PUSCH resource scheduled by DCI format 0_1.

[0404] Figure 13 is a diagram illustrating an example of a non-periodic CSI reporting method.

[0405] In one example (1300) of FIG. 13, the terminal can monitor the PDCCH (1301) to obtain DCI format 0_1, from which it can obtain scheduling information and CSI request information for the PUSCH (1305). The terminal can obtain resource information for the CSI-RS (1302) to be measured from the received CSI request indicator. The terminal can determine at what point in time to perform a measurement on the CSI-RS (1302) resource being transmitted based on the time when the DCI format 0_1 ​​is received and the parameter for the offset within the CSI resource set setting (e.g., NZP CSI-RS resource set setting (NZP-CSI-RS-ResourceSet) (the aperiodicTriggeringOffset described above). For example, the terminal may receive the offset value X of the parameter aperiodicTriggeringOffset within the NZP-CSI-RS resource set setting as an upper layer signaling from the base station, and the set offset value X may represent the offset between the slot in which the DCI triggering the aperiodic CSI report is received and the slot in which the CSI-RS resource is transmitted. For example, the aperiodicTriggeringOffset parameter value and the offset value X may have a mapping relationship as described in [Table 41] below.

[0406]

[0407] In one example (1300) of FIG. 13, an example is described in which the aforementioned offset value is set to X=0. In this case, the terminal can receive CSI-RS (1302) in a slot (corresponding to slot 0 (1306) in FIG. 13) that receives DCI format 0_1 ​​that triggers a non-periodic CSI report, and can report the CSI information measured by the received CSI-RS to the base station via PUSCH (1305). The terminal can obtain scheduling information for PUSCH (1305) for CSI reporting (information corresponding to each field of the aforementioned DCI format 0_1) from DCI format 0_1. For example, the terminal can obtain information about the slot to transmit PUSCH (1305) from the aforementioned time domain resource allocation information for PUSCH (1305) in DCI format 0_1. In one example (1300) of FIG. 13, the terminal obtains a K2 value corresponding to the slot offset value for PDCCH-to-PUSCH as 3, and accordingly, at the time when PUSCH (1305) receives PDCCH (1301), it can be transmitted from slot 3 (1309), which is 3 slots away from slot 0 (1306).

[0408] Referring to an example (1310) of FIG. 13, the terminal can monitor the PDCCH (1311) to obtain DCI format 0_1, from which it can obtain scheduling information and CSI request information for PUSCH (1315). The terminal can obtain resource information for the CSI-RS (1312) to be measured from the received CSI request indicator. In the example (1310) of FIG. 13, an example is described in which the offset value for the aforementioned CSI-RS is set to X=1. In this case, the terminal can receive the CSI-RS (1312) in the slot (corresponding to slot 0 (1316) in FIG. 13) that received the DCI format 0_1 ​​triggering a non-periodic CSI report, and can report the CSI information measured by the received CSI-RS to the base station via PUSCH (1315).

[0409] According to one embodiment, a non-periodic CSI report may include at least one or both of CSI part 1 or CSI part 2, and when the non-periodic CSI report is transmitted via PUSCH, it may be multiplexed with a transport block. For multiplexing, a CRC may be inserted into the input bits of the non-periodic CSI, followed by encoding and rate matching, and then mapped to a specific pattern in a resource element within PUSCH and transmitted. The insertion of the CRC may be omitted depending on the coding method or the length of the input bits. The number of modulation symbols calculated for rate matching during multiplexing of CSI part 1 or CSI part 2 included in the non-periodic CSI report can be calculated as shown in [Table 42] below.

[0410]

[0411]

[0412]

[0413] For example, in the case of PUSCH repetition modes A and B, the terminal may multiplex and transmit aperiodic CSI reports only during the first repetition of the PUSCH repetition. This may be because the aperiodic CSI report information being multiplexed is encoded in a polar code format, and for it to be multiplexed across multiple PUSCH repetitions, each PUSCH repetition must have the same frequency and time resource allocation. In particular, in the case of PUSCH repetition type B, since each actual repetition can have a different OFDM symbol length, the aperiodic CSI report may be multiplexed and transmitted only during the first PUSCH repetition.

[0414] Additionally, for PUSCH repeat transmission method B, if the terminal receives a DCI that schedules a non-periodic CSI report or enables a semi-permanent CSI report without scheduling for the transport block, the value of the nominal repetition may be assumed to be 1 even if the number of PUSCH repeat transmissions set by the upper layer signaling (e.g., RRC message) is greater than 1. Additionally, if the terminal schedules or enables a non-periodic or semi-permanent CSI report without scheduling for the transport block based on PUSCH repeat transmission method B, the terminal can expect the first nominal repetition to be the same as the first actual repetition. For a PUSCH transmitted including a semi-permanent CSI based on PUSCH repeat transmission method B without scheduling for the DCI after semi-permanent CSI reporting is enabled by the DCI, if the first nominal repetition is different from the first actual repetition, the transmission for the first nominal repetition may be ignored.

[0415] [Regarding Terminal Capability Reporting]

[0416] In LTE and NR, a terminal can perform a procedure to report the capabilities supported by the terminal to the base station while connected to the serving base station. In the description below, this procedure is referred to as a UE capability report.

[0417] A base station may transmit a UE capability enquiry message requesting capability reporting to a connected terminal. The message may include a request for terminal capability specific to the base station's RAT (radio access technology) type. The request for each RAT type may include information on supported frequency band combinations. Additionally, in the case of the UE capability enquiry message, UE capabilities for multiple RAT types may be requested through a single RRC message container transmitted by the base station. Alternatively, the base station may transmit the UE capability enquiry message, which includes the request for terminal capability for each RAT type, to the terminal multiple times. For example, the UE capability enquiry may be repeated multiple times within a single message, and the terminal may construct a corresponding UE capability information message and report it to the base station multiple times. In next-generation mobile communication systems, a UE capability request can be made for NR, LTE, EN-DC (E-UTRA (Universal Terrestrial Radio Access) - NR dual connectivity), and MR-DC (Multi-RAT dual connectivity). In addition, while terminal capability inquiry messages are generally transmitted initially after the terminal connects to the base station, the base station can request them under any conditions when necessary.

[0418] At this stage, a terminal that has received a request from a base station to report UE capability can configure terminal capability according to the RAT type and band information requested from the base station. The method by which a terminal configures UE capability in an NR system is described below.

[0419] 1. If the terminal receives a list of LTE and / or NR bands from the base station via a UE capability request, the terminal can configure a band combination (BC) for EN-DC and NR stand alone (SA). That is, based on the bands requested from the base station via FreqBandList, the terminal can configure a candidate list of BCs for EN-DC and NR SA. Additionally, the bands may have priority in the order listed in FreqBandList.

[0420] 2. If the base station requests a UE capability report by setting the “eutra-nr-only” flag or the “eutra” flag, the terminal may completely remove NR SA BCs from the above-mentioned list of configured BC candidates. This operation may occur only when the LTE base station (eNB) requests the “eutra” capability.

[0421] 3. Subsequently, the terminal may remove fallback BCs from the candidate list of BCs configured in the above step. Here, a fallback BC refers to a BC that can be obtained by removing a band corresponding to at least one SCell from any BC; this step may be omitted because the BC before removing the band corresponding to at least one SCell already covers the fallback BC. This step applies to MR-DC as well, meaning it can also be applied to LTE bands. The BCs remaining after this step may be the final "candidate BC list."

[0422] 4. The terminal can select BCs to report by selecting BCs that match the requested RAT type from the final "Candidate BC List" above. In this step, the terminal can configure the supportedBandCombinationList in a predetermined order. That is, the terminal can configure the BCs and UE capabilities to report according to the pre-configured rat-Type order (nr -> eutra-nr -> eutra). Additionally, the terminal can configure the featureSetCombination for the configured supportedBandCombinationList and construct a list of "Candidate Feature Set Combinations" from the Candidate BC List from which the list of fallback BCs (containing capabilities of the same or lower level) has been removed. The above "Candidate Feature Set Combinations" include feature set combinations for both NR and EUTRA-NR BCs and can be obtained from the feature set combinations of the UE-NR-Capabilities and UE-MRDC-Capabilities containers.

[0423] 5. Additionally, if the requested rat Type is eutra-nr and has an influence, featureSetCombinations can be included in both the UE-MRDC-Capabilities and UE-NR-Capabilities containers. However, the NR feature set can only be included in UE-NR-Capabilities.

[0424] After terminal capability is configured, the terminal can transmit a terminal capability information message containing the terminal capability to the base station. Based on the terminal capability received from the terminal, the base station can subsequently perform appropriate scheduling and transmission / reception management for the terminal.

[0425] [CA / DC Related]

[0426] FIG. 15 is a diagram illustrating the wireless protocol structure of a base station and a terminal in a single cell, carrier aggregation, dual connectivity situation according to one embodiment of the present disclosure.

[0427] Referring to FIG. 15, the wireless protocol of the next-generation mobile communication system consists of NR SDAP (Service Data Adaptation Protocol S25, S70), NR PDCP (Packet Data Convergence Protocol S30, S65), NR RLC (Radio Link Control S35, S60), and NR MAC (Medium Access Control S40, S55) at the terminal and the NR base station, respectively.

[0428] The main functions of NR SDAP (S25, S70) may include at least some of the following functions.

[0429] - User data transfer function (transfer of user plane data)

[0430] - Mapping function between a QoS flow and a DRB (data radio bearer) for both DL and UL for uplink and downlink

[0431] - Marking QoS flow ID for uplink and downlink (marking QoS (quality of service) flow ID in both DL and UL packets)

[0432] - Function to map reflective QoS flow to the data bearer for uplink SDAP PDUs (protocol data units).

[0433] For SDAP layer devices, the terminal may receive a setting via an RRC message regarding whether to use the header of the SDAP layer device or the functions of the SDAP layer device for each PDCP layer device, bearer, or logical channel. If the SDAP header is set, the terminal may instruct the NAS (non-access stratum) reflective QoS setting 1-bit indicator and the AS (access stratum) reflective QoS setting 1-bit indicator of the SDAP header to update or reset the mapping information for the QoS flow of the uplink and downlink and the data bearer. The SDAP header may include QoS flow ID information indicating QoS. The QoS information may be used for data processing priority, scheduling information, etc., to support smooth service.

[0434] The main functions of NR PDCP (S30, S65) may include at least some of the following functions.

[0435] - Header compression and decompression features (ROHC only)

[0436] - User data transfer function (Transfer of user data)

[0437] - Sequential delivery function (In-sequence delivery of upper layer PDUs)

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

[0439] - Reordering function (PDCP PDU reordering for reception)

[0440] - Duplicate detection function (Duplicate detection of lower layer SDUs)

[0441] - Retransmission of PDCP SDU (service data unit)s

[0442] - Encryption and decryption functions (Ciphering and deciphering)

[0443] - Timer-based SDU discard in uplink.

[0444] The reordering function of the NR PDCP device refers to a function that reorders PDCP PDUs received from a lower layer in order based on the PDCP SN (sequence number), and may include a function that transmits data to an upper layer in the reordered order. Alternatively, the reordering function of the NR PDCP device may include a function that transmits immediately without considering the order, a function that records lost PDCP PDUs by reordering, a function that reports the status of lost PDCP PDUs to the transmitting side, and a function that requests retransmission of lost PDCP PDUs.

[0445] The main functions of NR RLC (S35, S60) may include at least some of the following functions.

[0446] - Data transfer function (Transfer of upper layer PDUs)

[0447] - Sequential delivery function (In-sequence delivery of upper layer PDUs)

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

[0449] - ARQ function (Error Correction through ARQ)

[0450] - Concatenation, segmentation, and reassembly functions of RLC SDUs

[0451] - Re-segmentation function (Re-segmentation of RLC data PDUs)

[0452] - Reordering function (Reordering of RLC data PDUs)

[0453] - Duplicate detection

[0454] - Error detection function (Protocol error detection)

[0455] - RLC SDU discard function

[0456] - RLC (radio link control) re-establishment function

[0457] According to one embodiment, the in-sequence delivery function of the NR RLC device refers to a function of delivering RLC SDUs received from a lower layer to an upper layer in order. The in-sequence delivery function of the NR RLC device may include a function of reassembling and delivering the RLC SDUs when the original RLC SDU is received divided into multiple RLC SDUs, a function of rearranging the received RLC PDUs based on an RLC SN (sequence number) or PDCP SN (sequence number), a function of recording the lost RLC PDUs by rearranging the order, a function of reporting the status of the lost RLC PDUs to the transmitting side, and a function of requesting retransmission of the lost RLC PDUs. The in-sequence delivery function of the NR RLC device may include a function to deliver only the RLC SDUs prior to the lost RLC SDU in order to the upper layer if there is a lost RLC SDU, or a function to deliver all RLC SDUs received before the timer started in order to the upper layer if a predetermined timer has expired even if there is a lost RLC SDU. Alternatively, the in-sequence delivery function of the NR RLC device may include a function to deliver all RLC SDUs received up to the present in order to the upper layer if a predetermined timer has expired even if there is a lost RLC SDU.In addition, the RLC PDUs described above may be processed in the order in which they are received (e.g., regardless of the order of sequence numbers, in the order of arrival) and delivered to the PDCP device out of order (out-of-sequence delivery). In the case of segments, segments stored in a buffer or to be received later may be received, reconstructed into a single complete RLC PDU, processed, and delivered to the PDCP device. The NR RLC layer may not include a concatenation function, and this function may be performed by the NR MAC layer or replaced by the multiplexing function of the NR MAC layer.

[0458] According to one embodiment, the out-of-sequence delivery function of the NR RLC device may be referred to as a function of delivering RLC SDUs received from a lower layer directly to an upper layer regardless of order, and may include a function of reassembling and delivering them when an original RLC SDU is received divided into multiple RLC SDUs, and may include a function of storing the RLC SN or PDCP SN of the received RLC PDUs and sorting the order to record the lost RLC PDUs.

[0459] The NR MAC (S40, S55) can be connected to multiple NR RLC layer devices configured in a terminal, and the main functions of the NR MAC may include at least some of the following functions.

[0460] - Mapping function (Mapping between logical channels and transport channels)

[0461] - Multiplexing and demultiplexing functions (Multiplexing / demultiplexing of MAC SDUs)

[0462] - Scheduling information reporting function

[0463] - HARQ function (Error correction through HARQ)

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

[0465] - Priority handling between UEs by means of dynamic scheduling

[0466] - MBMS service identification function

[0467] - Transport format selection function

[0468] - Padding

[0469] The NR PHY layer (S45, S50) can perform the operation of channel coding and modulating upper layer data, creating OFDM symbols and transmitting them to the wireless channel, or demodulating OFDM symbols received through the wireless channel and channel decoding them to transmit them to the upper layer.

[0470] According to one embodiment, the detailed structure of the wireless protocol structure may vary depending on the carrier (or cell) operation method. For example, when a base station transmits data to a terminal based on a single carrier (or cell), the base station and the terminal use a protocol structure having a single structure for each layer, such as S00. On the other hand, when a base station transmits data to a terminal based on Carrier Aggregation (CA) using multiple carriers in a single TRP, the base station and the terminal use a protocol structure that has a single structure up to the RLC, such as S10, but multiplexes the PHY layer through the MAC layer. As another example, when a base station transmits data to a terminal based on Dual Connectivity (DC) using multiple carriers in multiple TRPs, the base station and the terminal may use a protocol structure that has a single structure up to the RLC, such as S20, but multiplexes the PHY layer through the MAC layer.

[0471] Referring to the descriptions regarding PDCCH and beam settings mentioned above, PDCCH repeated transmission is not supported in current Rel-15 and Rel-16 NR, making it difficult to achieve the required reliability in scenarios requiring high reliability, such as URLLC (ultra-reliable low latency communications). The present invention improves the PDCCH reception reliability of a terminal by providing a PDCCH repeated transmission method through multiple transmission reception points (TRPs). The specific method is described in detail in the following examples.

[0472] Embodiments of the present disclosure are described in detail below together with the accompanying drawings. The contents of the present disclosure are applicable to FDD and TDD systems. In the present disclosure, upper signaling (or upper layer signaling) is a signal transmission method transmitted from a base station to a terminal using a physical layer downlink data channel, or from a terminal to a base station using a physical layer uplink data channel, and may be referred to as RRC signaling, PDCP signaling, or a MAC (medium access control) control element (MAC CE).

[0473] In the present disclosure, when determining whether cooperative communication is applied, the terminal may use various methods, such as the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied having a specific format, or the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied including a specific indicator indicating whether cooperative communication is applied, or the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied being scrambled with a specific RNTI, or assuming the application of cooperative communication in a specific section indicated to an upper layer. For convenience of explanation thereafter, the case in which the terminal receives a PDSCH to which cooperative communication is applied based on conditions similar to those above may be referred to as the NC-JT case.

[0474] In the following disclosure, “determining priority between A and B” may be referred to in various ways, such as selecting the one with higher priority according to a predetermined priority rule and performing the corresponding action, or omitting or dropping the action for the one with lower priority.

[0475] In the following disclosure, the examples described above are explained through a number of embodiments, but these are not independent, and one or more embodiments may be applied simultaneously or in combination.

[0476] [Regarding NC-JT]

[0477] According to one embodiment of the present disclosure, non-coherent joint transmission (NC-JT) may be used for a terminal to receive PDSCH from a plurality of TRPs.

[0478] Unlike existing systems, 5G wireless communication systems can support not only services requiring high transmission speeds but also services requiring very short transmission delays and high connection density. In a wireless communication network comprising multiple cells, TRPs (transmission and reception points), or beams, coordinated transmission between each cell, TRP, or / and beam can satisfy various service requirements by increasing the signal strength received by the terminal or efficiently performing interference control between each cell, TRP, or / and beam.

[0479] Joint Transmission (JT) is a representative transmission technology for the aforementioned cooperative communication and can be referred to as a technology that increases the signal strength or throughput received by a terminal by transmitting signals to a single terminal through multiple different cells, TRPs, and / or beams. In this case, the characteristics of the channels between each cell, TRP, or / or beam and the terminal may differ significantly. In particular, in the case of Non-Coherent Joint Transmission (NC-JT), which supports non-coherent precoding between each cell, TRP, or / or beam, individual precoding, MCS, resource allocation, TCI instructions, etc., may be required depending on the link-specific channel characteristics between each cell, TRP, or / or beam and the terminal.

[0480] The aforementioned NC-JT transmission may be applied to at least one channel among the physical downlink shared channel (PDSCH), physical downlink control channel (PDCCH), or the physical uplink shared channel (PUSCH) and physical uplink control channel (PUCCH). When transmitting via PDSCH, transmission information such as precoding, MCS, resource allocation, and / or TCI may be indicated as DL DCI, and for NC-JT transmission, said transmission information must be indicated independently per cell, TRP, or / and beam. This is a major factor in increasing the payload required for DL ​​DCI transmission, which can adversely affect the reception performance of the PDCCH transmitting the DCI. Therefore, to support JT in PDSCH, it is necessary to carefully design the tradeoff between the amount of DCI information and the reception performance of control information.

[0481] FIG. 16 is a diagram illustrating an example of antenna port configuration and resource allocation for transmitting PDSCH using cooperative communication in a wireless communication system according to one embodiment of the present disclosure.

[0482] Referring to Fig. 16, examples for PDSCH transmission are described according to the Joint Transmission (JT) technique, and examples for allocating radio resources by TRP are illustrated.

[0483] Referring to FIG. 16, an example (N000) of a Coherent Joint Transmission (C-JT) that supports coherent precoding between each cell, TRP or / and beam is shown.

[0484] In the case of C-JT, TRP A (N005) and TRP B (N010) transmit a single data (PDSCH) to a terminal (N015), and joint precoding can be performed in multiple TRPs. This can be referenced as TRP A (N005) and TRP B (N010) transmitting DMRS through the same DMRS ports to transmit the same PDSCH. For example, TRP A (N005) and TRP B (N010) can each transmit DRMS ​​to the terminal through DMRS port A and DMRS B. In this case, the terminal can receive one DCI information for receiving a single PDSCH that is demodulated based on the DMRS transmitted through DMRS port A and DMRS B.

[0485] FIG. 16 shows an example (N020) of Non-Coherent Joint Transmission (NC-JT) that supports non-coherent precoding between each cell, TRP or / and beam for PDSCH transmission.

[0486] In the case of NC-JT, a PDSCH is transmitted to the terminal (N035) for each cell, TRP, and / or beam, and individual precoding may be applied to each PDSCH. Each cell, TRP, and / or beam can transmit a different PDSCH or a different PDSCH layer to the terminal to improve throughput compared to single cell, TRP, and / or beam transmission. Additionally, each cell, TRP, and / or beam can repeatedly transmit the same PDSCH to the terminal to improve reliability compared to single cell, TRP, and / or beam transmission. For convenience of explanation, the cell, TRP, and / or beam may be referred to as TRP below.

[0487] At this time, various wireless resource allocations may be considered, such as when the frequency and time resources used by multiple TRPs for PDSCH transmission are all the same (N040), when the frequency and time resources used by multiple TRPs do not overlap at all (N045), and when some of the frequency and time resources used by multiple TRPs overlap (N050).

[0488] To support NC-JT, DCIs of various forms, structures, and relationships can be considered to simultaneously allocate multiple PDSCHs to a single terminal.

[0489] FIG. 17 is a diagram illustrating an example of the configuration of downlink control information (DCI) for NC-JT in which each TRP transmits different PDSCH or different PDSCH layers to a terminal in a wireless communication system according to one embodiment of the present disclosure.

[0490] Referring to FIG. 17, according to one embodiment, case #1 (N100) may be an example in which, in addition to the serving TRP (TRP#0) used for a single PDSCH transmission, (N-1) different PDSCHs are transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)), and control information for the PDSCHs transmitted from the (N-1) additional TRPs is transmitted independently of the control information for the PDSCH transmitted from the serving TRP. For example, a terminal may obtain control information for the PDSCHs transmitted from different TRPs (TRP#0 to TRP#(N-1)) through independent DCIs (DCI#0 to DCI#(N-1)). The formats between the independent DCIs may be the same or different from each other, and the payloads between the DCIs may also be the same or different from each other. In the aforementioned case #1, the degrees of freedom for each PDSCH control or allocation can be fully guaranteed, but if each DCI is transmitted from different TRPs, coverage differences per DCI may occur, which may degrade reception performance.

[0491] According to one embodiment, case #2 (N105) describes a situation in which (N-1) different PDSCHs are transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) in addition to the serving TRP (TRP#0) used for a single PDSCH transmission, and control information (DCI) for the PDSCHs of the (N-1) additional TRPs is transmitted to each of them, and each of these DCIs may be dependent on the control information for the PDSCH transmitted from the serving TRP.

[0492] For example, DCI#0, which is control information for PDSCH transmitted from a serving TRP (TRP#0), includes all information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2, but shortened DCI (hereinafter sDCI) (sDCI#0 to sDCI#(N-2)), which is control information for PDSCH transmitted from cooperative TRPs (TRP#1 to TRP#(N-1)), may include only some of the information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2. Therefore, in the case of sDCI transmitting control information for PDSCH transmitted from cooperative TRPs, since the payload is smaller compared to normal DCI (nDCI) transmitting PDSCH-related control information transmitted from a serving TRP, it may be possible to include reserved bits compared to nDCI.

[0493] In the aforementioned case #2, the degree of freedom for each PDSCH control or allocation may be limited depending on the content of the information elements included in sDCI, but since the receiving performance of sDCI becomes superior to that of nDCI, the probability of coverage difference between DCIs occurring may be reduced.

[0494] According to one embodiment, case #3 (N110) describes a situation in which (N-1) different PDSCHs are transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) other than the serving TRP (TRP#0) used for a single PDSCH transmission, and one control information for the PDSCHs of the (N-1) additional TRPs is transmitted, and an example is described in which this DCI is dependent on the control information for the PDSCH transmitted from the serving TRP.

[0495] For example, DCI#0, which is control information for a PDSCH transmitted from a serving TRP (TRP#0), may include all information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2, and for control information for PDSCHs transmitted from cooperative TRPs (TRP#1 to TRP#(N-1)), it is possible to collect and transmit only some of the information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2 into a single 'secondary' DCI (sDCI). For example, sDCI may include at least one piece of HARQ-related information, such as frequency domain resource assignment, time domain resource assignment, and / or MCS of cooperative TRPs. In addition, for information not included in sDCI, such as BWP (bandwidth part) indicators or carrier indicators, the DCI of the serving TRP (DCI#0, normal DCI, nDCI) may be followed.

[0496] According to one embodiment, case #3 (N110) may limit the freedom of each PDSCH control or allocation according to the content of the information element included in sDCI, but the reception performance of sDCI can be adjusted, and the complexity of DCI blind decoding of the terminal can be reduced compared to case #1 (N100) or case #2 (N105).

[0497] According to one embodiment, case #4 (N115) is an example in which, in a situation where (N-1) different PDSCHs are transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) in addition to the serving TRP (TRP#0) used for a single PDSCH transmission, control information for the PDSCHs transmitted from the (N-1) additional TRPs is transmitted in the same DCI (Long DCI) as the control information for the PDSCH transmitted from the serving TRP. For example, a terminal can obtain control information for PDSCHs transmitted from different TRPs (TRP#0 to TRP#(N-1)) through a single DCI. In the case of case #4 (N115), the complexity of the terminal's DCI blind decoding may not increase, but the degree of freedom for PDSCH control or allocation may be low, such as when the number of cooperating TRPs is limited by the long DCI payload limit.

[0498] In the following description and embodiments, sDCI may refer to various auxiliary DCIs, such as shortened DCI, secondary DCI, or normal DCI (DCI formats 1_0 to 1_1 described above) containing PDSCH control information transmitted from a cooperative TRP, and unless a specific limitation is specified, the description may be similarly applied to the various auxiliary DCIs.

[0499] In the following description and embodiments, the aforementioned cases #1 (N100), #2 (N105), and #3 (N110), in which one or more DCIs (e.g., PDCCH) are used to support NC-JT, may be classified as multiple PDCCH-based NC-JT, and the aforementioned case #4 (N115), in which a single DCI (PDCCH) is used to support NC-JT, may be classified as single PDCCH-based NC-JT. In PDCCH transmission based on multiple PDCCH, a CORESET in which the DCI of the serving TRP (TRP#0) is scheduled and a CORESET in which the DCIs of the cooperating TRPs (TRP#1 to TRP#(N-1)) are scheduled may be distinguished. Methods for distinguishing the CORESETs may include distinguishing them through upper layer indicators for each CORESET, and / or distinguishing them through beam settings for each CORESET. In addition, in a single PDCCH-based NC-JT, instead of a single DCI scheduling multiple PDSCHs, a single PDSCH having multiple layers is scheduled, and the aforementioned multiple layers can be transmitted from multiple TRPs. At this time, the connection relationship between a layer and the TRP transmitting that layer can be indicated through a TCI (Transmission Configuration Indicator) for the layer.

[0500] In the embodiments of the present disclosure, "cooperative TRP" may be replaced with various terms such as "cooperative panel" or "cooperative beam" in actual application.

[0501] In the embodiments of the present disclosure, the phrase “where NC-JT is applied” can be interpreted in various ways depending on the situation, such as “where a terminal receives one or more PDSCHs simultaneously in one BWP,” “where a terminal receives PDSCHs based on two or more TCI (Transmission Configuration Indicator) indications simultaneously in one BWP,” and / or “where the PDSCHs received by the terminal are associated with one or more DMRS port groups,” but for the convenience of explanation, it has been used as a single expression.

[0502] In the present disclosure, the wireless protocol structure for NC-JT can be used in various ways depending on the TRP deployment scenario. For example, when there is no or small backhaul delay between cooperative TRPs, a method using a structure based on MAC layer multiplexing similar to S10 in FIG. 15 (e.g., CA-like method) is possible. On the other hand, when the backhaul delay between cooperative TRPs is large enough to be negligible (e.g., when more than 2 ms is required for the exchange of information such as CSI, scheduling, and HARQ-ACK between cooperative TRPs), a method using a structure independent of each TRP from the RLC layer to secure delay-robust characteristics (DC-like method) similar to S20 in FIG. 15 may be possible.

[0503] According to one embodiment, a terminal supporting C-JT / NC-JT receives C-JT / NC-JT related parameters or setting values, etc. from an upper layer setting, and can set the RRC parameters of the terminal based thereon. For the upper layer setting, the terminal can utilize UE capability parameters (e.g., tci-StatePDSCH). For example, UE capability parameters (e.g., tci-StatePDSCH) can define TCI states for the purpose of PDSCH transmission. For example, the number of TCI states can be set to 4, 8, 16, 32, 64, and 128 in FR1, and to 64 and 128 in FR2, and among the set number, up to 8 states can be set that can be indicated by 3 bits of the TCI field of DCI through a MAC CE message. The maximum value 128 may refer to the value indicated by maxNumberConfiguredTCIstatesPerCC within the tci-StatePDSCH parameter included in the terminal's capability signaling. In this way, a series of configuration processes from upper layer configuration to MAC CE configuration can be applied to beamforming instructions or beamforming change commands for at least one PDSCH in one TRP.

[0504] [Multi-DCI-based Multi-TRP]

[0505] According to one embodiment of the present disclosure, a downlink control channel for NC-JT transmission can be established based on Multi-PDCCH.

[0506] In NC-JT based on multiple PDCCH, when transmitting DCI for the PDSCH schedule of each TRP, a CORESET or search space may be provided for each TRP. The CORESET or search space for each TRP may be configured as in at least one of the following cases.

[0507] * Setting the upper layer index per CORESET: The CORESET setting information configured as the upper layer may include an index value, and the TRP transmitting the PDCCH from the corresponding CORESET can be distinguished by the configured CORESET-specific index value. For example, in a set of CORESETs with the same upper layer index value, it may be assumed that the same TRP transmits the PDCCH, or that a PDCCH scheduling a PDCCH from the same TRP is transmitted. The aforementioned CORESET-specific index may be named as CORESETPoolIndex, and for CORESETs with the same CORESETPoolIndex value configured, it may be assumed that the PDCCH is transmitted from the same TRP. For a CORESET where the CORESETPoolIndex value is not configured, it may be assumed that the default value of CORESETPoolIndex is configured, and the aforementioned default value may be 0.

[0508] * Multiple PDCCH-Config Settings: Multiple PDCCH-Configs are configured within a single BWP, and each PDCCH-Config may include PDCCH settings per TRP. That is, a single PDCCH-Config may contain a list of CORESETs and / or a list of search spaces per TRP, and one or more CORESETs and one or more search spaces included in a single PDCCH-Config may be considered to correspond to a specific TRP.

[0509] * CORESET Beam / Beam Group Configuration: TRPs corresponding to a given CORESET can be distinguished through beams or beam groups configured per CORESET. For example, if the same TCI state is configured for multiple CORESETs, those CORESETs may be considered to be transmitted through the same TRP, or a PDCCH scheduling a PDSCH of the same TRP within that CORESET may be considered to be transmitted.

[0510] * Search Space Beam / Beam Group Configuration: Beams or beam groups are configured for each search space, allowing TRPs to be distinguished by search space. For example, if the same beam / beam group or TCI state is set in multiple search spaces, it can be assumed that the same TRP is transmitting a PDCCH in that search space, or that a PDCCH scheduling the same TRP's PDCCH is being transmitted in that search space.

[0511] As described above, by separating the CORESET or search space by TRP, it is possible to classify PDSCH and HARQ-ACK information for each TRP, thereby enabling the generation of independent HARQ-ACK codebooks and the use of independent PUCCH resources for each TRP.

[0512] The above-described settings may be independent per cell or per BWP. For example, two different CORESETPoolIndex values ​​may be set in a PCell (primary cell), while a specific SCell may not have a CORESETPoolIndex value set. In this case, NC-JT transmission may be configured in the PCell, whereas NC-JT transmission may not be configured in the SCell (secondary cell) where the CORESETPoolIndex value is not set.

[0513] [Single-DCI-based Multi-TRP]

[0514] According to one embodiment of the present disclosure, a downlink beam for NC-JT transmission can be established based on a Single-PDCCH.

[0515] In a single PDCCH-based NC-JT, a single DCI can schedule a PDSCH transmitted by multiple TRPs. In this case, the number of TCI states can be used as a method to indicate the number of TRPs transmitting the PDSCH. That is, if the number of TCI states indicated to the DCI scheduling the PDSCH is 2, it can be considered a single PDCCH-based NC-JT transmission, and if the number of TCI states is 1, it can be considered a single-TRP transmission. The TCI states indicated to the above-mentioned DCI may correspond to one or two TCI states among the TCI states activated by MAC-CE. When the TCI states of the DCI correspond to two TCI states activated by MAC-CE, a correspondence relationship is established between the TCI codepoint indicated by the DCI and the TCI states activated by MAC-CE, and this may be the case when there are two TCI states activated by MAC-CE corresponding to the said TCI codepoint.

[0516] The above-described configuration may be independent per cell or per BWP. For example, a PCell may have up to two activated TCI states corresponding to a single TCI codepoint, whereas a specific SCell may have up to one activated TCI state corresponding to a single TCI codepoint. In this case, NC-JT transmission may be configured in the PCell, whereas NC-JT transmission may not be configured in the aforementioned SCell.

[0517] [PHR]

[0518] Figure 18 illustrates a procedure for a base station to control the transmit power of a terminal in a cellular system. In step 18-10 of Figure 18, a terminal within the base station's coverage area can perform downlink synchronization with the base station and obtain system information. For example, downlink synchronization can be achieved through the synchronization signals PSS / SSS (Primary Synchronization Signal / Secondary Synchronization Signal) received from the base station. Terminals that have performed downlink synchronization can receive MIB (Master Information Block) and SIB (System Information Block) from the base station and obtain system information. In step 18-15, the terminal can perform uplink synchronization with the base station through a random access procedure and establish a Raido Resource Control (RRC) connection. In the random access procedure, the terminal can transmit a random access preamble and message 3 (msg3) to the base station via the uplink. At this time, uplink transmit power control can be performed during the transmission of the random access preamble and message 3. For example, the terminal may control uplink transmit power by receiving parameters for uplink transmit power control from the base station through acquired system information, e.g., SIB, or by using agreed parameters. According to one embodiment, the terminal may measure the Reference Signal Received Power (RSRP) from the path attenuation estimation signal transmitted by the base station and estimate the downlink path attenuation value as shown in [Equation 7]. Then, based on the estimated path attenuation value, the terminal may set the uplink transmit power value for transmitting a random access preamble and message 3.

[0519] [Mathematical Formula 7]

[0520] Downlink path attenuation = Base station signal transmission power - RSRP measured by the terminal

[0521] In [Equation 7], the transmission power of the base station signal can be referenced as the transmission power of the downlink path attenuation estimate signal transmitted by the base station. The downlink path attenuation estimate signal transmitted by the base station may be a Cell-specific Reference Signal (CRS) or a Synchronization Signal Block (SSB).

[0522] According to one embodiment, when the path attenuation estimation signal is a Cell-specific Reference Signal (CRS), the transmission power of the base station signal refers to the transmission power of the CRS and can be transmitted to the terminal through the referenceSignalPower parameter of the system information. For example, when the path attenuation estimation signal is a Synchronization Signal Block (SSB), the transmission power of the base station signal refers to the transmission power of the DeModulation Reference Signal (DMRS) transmitted to the Secondary Synchronization Signal (SSS) and PBCH, and can be transmitted to the terminal through the ss-PBCH-BlockPower parameter of the system information.

[0523] According to one embodiment, in steps 18-20, the terminal may receive RRC parameters for uplink transmit power control from a base station via UE-specific RRC or common RRC. The received transmit power control parameters may differ depending on the type of uplink channel and the type of signal transmitted to the uplink. That is, the transmit power control parameters applied to the transmission of the uplink control channel (PUCCH: physical uplink control channel), the uplink data channel (PUSCH: physical uplink shared channel), and the sounding reference signal (SRS: sounding reference signal) may differ from each other.

[0524] In addition, as previously explained, transmit power control parameters received by the terminal via the system information block (SIB) from the base station prior to the RRC connection establishment, or transmit power control parameters used by the terminal as pre-agreed values ​​prior to the RRC connection establishment, may be included in the RRC parameters transmitted from the base station after the RRC connection establishment. The terminal may use the RRC parameter values ​​received from the base station after the RRC connection establishment for uplink transmit power control.

[0525] According to one embodiment, in steps 18-25, the terminal may receive a path attenuation estimation signal from the base station. For example, after establishing the terminal's RRC connection, the base station may configure the CSI-RS (Channel State Information-Reference Signal) as the terminal's path attenuation estimation signal. In this case, the base station may transmit information regarding the transmit power of the CSI-RS to the terminal through the powerControlOffsetSS parameter of the UE dedicated RRC information. At this time, powerControlOffsetSS may be referenced as the difference (offset) in transmit power between the SSB and the CSI-RS.

[0526] According to one embodiment, in steps 18-30, the terminal can estimate a downlink path attenuation value and set an uplink transmit power value. For example, the terminal can measure the downlink RSRP using CSI-RS and estimate the downlink path attenuation value through [Equation 1] using information on the transmit power of CSI-RS received from the base station. Then, based on the estimated path attenuation value, the terminal can set an uplink transmit power value for PUCCH, PUSCH, and SRS transmission.

[0527] According to one embodiment, in steps 18-35, the terminal may report power headroom (PHR) to the base station. Power headroom may be referenced as the difference between the terminal's current transmission power and the terminal's maximum output power.

[0528] According to one embodiment, in steps 18-40, the base station can optimize system operation based on the reported power headroom. For example, if the power headroom value reported to the base station by a specific terminal is positive, the base station can increase system yield by allocating more resources (RB: Resource Block) to the terminal.

[0529] According to one embodiment, in steps 18-45, the terminal may receive a transmission power control command (TPC) from the base station. For example, if the power headroom value reported by a specific terminal to the base station is negative, the base station may allocate fewer resources to the terminal or reduce the transmission power of the terminal through the transmission power control command (TPC). This may increase system yield or reduce unnecessary power consumption by the terminal.

[0530] According to one embodiment, in steps 18-50, the terminal can update the transmit power based on a TPC command. At this time, the TPC command may be transmitted to the terminal via a UE-specific DCI or a group common DCI. Thus, the base station can dynamically control the transmit power of the terminal through the TPC command.

[0531] According to one embodiment, in steps 18-55, the terminal can perform uplink transmission based on the updated transmission power.

[0532] [PUSCH power control]

[0533] The PUSCH transmission power can be determined through the following [Equation 8].

[0534] [Mathematical Formula 8]

[0535]

[0536] In [Equation 8] is the maximum transmission power set for the terminal for carrier f of serving cell c at time i of PUSCH transmission. is a reference setting transmission power setting value based on the active uplink bandwidth part (BWP) b of the carrier f of the serving cell c, and can have different values ​​depending on various transmission types j. It can have various values ​​depending on whether the PUSCH transmission is message 3 PUSCH for random access, or whether the PUSCH is a configured grant PUSCH, or a scheduled PUSCH. PUSCH can be referenced as the frequency size assigned. represents the degree of compensation ratio for the path loss of the UL BWP b of the carrier f of the serving cell c, and can be set by the upper signal and may have different values ​​depending on j. is an estimated value of the downlink path loss of the UL BWP b of the carrier f of the serving cell c, and the value measured through the reference signal in the activated downlink bandwidth interval can be used. The reference signal may be an SS / PBCH block or a CSI-RS. The downlink path loss can be calculated as described above in [Equation 7].

[0537] In one embodiment of the present disclosure, is a downlink warning attenuation value, which may be a path attenuation calculated by the terminal as in [Equation 7]. Depending on whether the upper signal is set, the terminal may calculate the path attenuation based on a reference signal resource associated with the SS / PBCH block or CSI-RS. The reference signal resource may select one of several sets of reference signal resources by the upper signal or L1 signal, and the terminal may calculate the path attenuation based on that reference signal resource. is a value determined by the MCS (Modulation and Coding Scheme) value of the PUSCH at time i of the PUSCH transmission of the carrier f of the serving cell c and the UL BWP b. The power value can be dynamically adjusted by the TPC command as a power adjustment adaptive value.

[0538] The TPC command is divided into accumulated and absolute modes, and one of the two modes can be determined by the upper signal. In the accumulated mode, the currently determined power regulation adaptation value is accumulated with the value indicated by the TPC command, and can be increased or decreased according to the TPC command, and f b,f,c (i,l)=f b,f,c It can have the relationship (i-i0,l)+∑δPUSCH,b,f,c. δPUSCH,b,f,c can be values ​​specified in the TPC command. The absolute mode is determined by the TPC command regardless of the currently determined power regulation adaptation value, and f b,f,c (i,l) has the relationship δPUSCH, b, f, c. [Table 43] below shows the values ​​that can be indicated by the TPC command.

[0539]

[0540] [PUCCH power control]

[0541] The following [Equation 9] is the equation for determining PUCCH transmission power.

[0542] [Mathematical Formula 9]

[0543]

[0544] In [Equation 9], P 0PUCCH,b,f,c (q u ) is a reference setting transmission power setting value, and various transmission types q u It has different values ​​depending on, and the values ​​can be changed by higher-level signals such as RRC or MAC CE. If the value is changed by MAC CE, the terminal sends a HARQ-ACK to the PDSCH that received the MAC CE; if the slot that sent the HARQ-ACK is k, then k + k offsetIt can be determined that the corresponding value is applied starting from the slot. k offset It has different values ​​depending on the subcarrier interval, and for example, it can have 3ms. can be the size of the frequency resource area to which PUCCH is allocated. PL b,f,c (q d ) is the estimated path attenuation value of the terminal, and as described in [Equation 7], the terminal can calculate it based on a specific reference signal among various CSI-RS or SS / PBCH depending on whether the upper signal is set and the type thereof. For repeated transmission PUCCHs, the same q d is applied. For repeated transmission PUCCHs, the same q is applied. u It can be applied.

[0545] [HARQ-ACK: Type 1 (semi-static) codebook related]

[0546] In a situation where the number of HARQ-ACK PUCCHs a terminal can transmit within a slot is limited to one, when the terminal receives a semi-static HARQ-ACK codebook upper setting, the terminal may report HARQ-ACK information regarding PDSCH reception or SPS PDSCH release in the HARQ-ACK codebook in the slot indicated by the value of the PDSCH-to-HARQ_feedback timing indicator in DCI format 1_0 or DCI format 1_1. The terminal may report the HARQ-ACK information bit value as NACK (negative-ACK) in the HARQ-ACK codebook in the slot not indicated by the PDSCH-to-HARQ_feedback timing indicator field in DCI format 1_0 or DCI format 1_1. If the terminal reports only one SPS PDSCH release or one HARQ-ACK information for one PDSCH reception in the MA,C cases for candidate PDSCH reception, and the report is scheduled by DCI format 1_0 containing information in which the counter DACI field in the Pcell indicates 1, the terminal can determine one HARQ-ACK codebook for the corresponding SPS PDSCH release or the corresponding PDSCH reception.

[0547] Other than that, the HARQ-ACK codebook determination method according to the method described below may be followed.

[0548] If MA,c is the set of PDSCH reception candidate cases in serving cell c, MA,c can be obtained through the following [pseudo-code 1] steps.

[0549] [pseudo-code 1 start]

[0550] - Step 1: Initialize j to 0 and MA and c to empty sets. Initialize k, the HARQ-ACK transmission timing index, to 0.

[0551] - Step 2: Set R as the set of each row in the table containing slot information, start symbol information, and symbol count or length information where PDSCH is mapped. If the PDSCH-possible mapping symbol pointed to by each value in R is set to a UL symbol according to the DL and UL settings established above, delete the corresponding row from R.

[0552] - Step 3-1: If a terminal can receive one unicast PDSCH per slot and R is not an empty set, add 1 to set MA,c.

[0553] - Step 3-2: If the terminal can receive more than one unicast PDSCH in a slot, count the number of PDSCHs that can be assigned to different symbols in the calculated R and add that number to MA,c.

[0554] - Step 4: Increase k by 1 and start again from Step 2.

[0555] [End of pseudo-code 1]

[0556] With the above-described pseudo-code 1 as an example in FIG. 19, all slot candidates capable of PDSCH-to-HARQ-ACK timing that can indicate slot#k (1908) can be considered in order to perform HARQ-ACK PUCCH transmission in slot#k (1908). In FIG. 19, it is assumed that HARQ-ACK transmission in slot#k (1908) is possible by PDSCH-to-HARQ-ACK timing combinations that are possible only for PDSCHs scheduled in slot#n (1902), slot#n+1 (1904), and slot#n+2 (1906). Then, the maximum number of PDSCHs that can be scheduled per slot can be derived based on time domain resource configuration information of PDSCHs that can be scheduled in slots 1902, 1904, and 1906, respectively, and information indicating whether the symbol within the slot is a downlink or an uplink. For example, assuming that a maximum of 2 PDSCHs are possible in slot 1902, 3 PDSCHs in slot 1904, and 2 PDSCHs in slot 1906, the maximum number of PDSCHs included in the HARQ-ACK codebook transmitted in slot 1908 can be 7. This is called the cardinality of the HARQ-ACK codebook.

[0557] Within a specific slot, the above step 3-2 is described through the following [Table 44] (Default PDSCH time domain resource allocation A for normal CP).

[0558]

[0559]

[0560] [Table 44] is the time resource allocation table in which the terminal operates by default before receiving time resource allocation via a separate RRC signal. For reference, in addition to separately indicating the row index value via RRC, the PDSCH time resource allocation value can be determined by the terminal common RRC signal, dmrs-TypeA-Position. In [Table 44], the ending and order columns are values ​​added separately for convenience of explanation and may not actually exist. The meaning of the ending column is the termination symbol of the scheduled PDSCH, and the order column is the code position value located within a specific codebook in the quasi-static HARQ-ACK codebook. This table can be applied to time resource allocation in DCI format 1_0 of the PDCCH common seek area.

[0561] To determine the HARQ-ACK codebook by calculating the maximum number of non-overlapping PDSCHs within a specific slot, the terminal may perform the following steps.

[0562] Step 1: Among all rows in the PDSCH time resource allocation table, you can identify the PDSCH allocation value that terminates first within a slot. In Table 44, you can see that row index 14 terminates first. This is marked as 1 in the order column. Other row indices that overlap with row index 14 by at least one symbol are marked as 1x in the order column.

[0563] * Step 2: Then, among the remaining row indices not displayed in the Order column, you can look for the PDSCH assignment value that terminates first. In Table 44, this corresponds to the row with row index 7 and dmrs-TypeA-Position value 3. Other row indices that overlap with that row index by at least one symbol are indicated as 2x in the order column.

[0564] * Step 3: Repeat Step 2, incrementing the order value. For example, in Table 44, you can find the earliest ending PDSCH assignment value among the row indices not displayed in the order column. In Table 44, this corresponds to the row with row index 6 and dmrs-TypeA-Position value 3. Other row indices that overlap with that row index by at least one symbol are marked as 3x in the order column.

[0565] * Step 4: Terminate when an order is displayed for all row indices. The size of that order is the maximum number of PDSCHs that can be scheduled within that slot without time overlap. Scheduling without time overlap means that different PDSCHs are scheduled via TDM.

[0566] In the 'order' column of [Table 44], the maximum value of 'order' represents the HARQ-ACK codebook size of the corresponding slot, and the 'order' value may represent the HARQ-ACK codebook point where the HARQ-ACK feedback bit for the scheduled PDSCH is located. For example, row index 16 in Table 44 may indicate that it exists at the 2nd code position in a semi-static HARQ-ACK codebook of size 3. The terminal transmitting the HARQ-ACK feedback [describes] the set of PDSCH reception candidate occasions M in serving cell c. A,c If so, M into [pseudo-code 1] or [pseudo-code 2] steps A,c can be obtained. M A,c It can be used to determine the number of HARQ-ACK bits that the terminal must transmit. For example, M A,cA HARQ-ACK codebook can be constructed using the cardinality of the set.

[0567] As another example, the factors to consider for determining a quasi-static HARQ-ACK codebook (or type 1 HARQ-ACK codebook) may be as follows.

[0568] a) on a set of slot timing values ​​K1associated with the active UL BWP

[0569] a) If the UE is configured to monitor PDCCH for DCI format 1_0 and is not configured to monitor PDCCH for DCI format 1_1 on serving cell c, K1is provided by the slot timing values ​​{1, 2, 3, 4, 5, 6, 7, 8} for DCI format 1_0

[0570] b) If the UE is configured to monitor PDCCH for DCI format 1_1 for serving cell c, K1is provided bydl-DataToUL-ACKfor DCI format 1_1

[0571] b) on a set of row indexesRof a table that is provided either by a first set of row indexes of a table that is provided byPDSCH-TimeDomainResourceAllocationListinPDSCH-ConfigCommonor by Default PDSCH time domain resource allocation A [6, TS 38.214], or by the union of the first set of row indexes and a second set of row indexes, if provided byPDSCH-TimeDomainResourceAllocationListinPDSCH-Config, associated with the active DL BWP and defining respective sets of slot offsets K0, start and length indicatorsSLIV, and PDSCH mapping types for PDSCH reception as described in [6, TS 38.214]

[0572] c) on the ratio between the downlink SCS configuration μ DL and the uplink SCS configuration μ UL provided bysubcarrierSpacinginBWP-DownlinkandBWP-Uplinkfor the active DL BWP and the active UL BWP, respectively

[0573] d) if provided, onTDD-UL-DL-ConfigurationCommonandTDD-UL-DL-ConfigDedicatedas described in Subclause 11.1.

[0574] As another example, the pseudo-code for determining the HARQ-ACK codebook can be as shown in [Table 45].

[0575]

[0576]

[0577]

[0578] The location in the HARQ-ACK codebook containing HARQ-ACK information for the DCI instructing the DL SPS release in pseudo-code 2 can be based on the location where the DL SPS PDSCH is received. For example, if the starting symbol of the DL SPS (semi-persistent scheduling) PDSCH being transmitted starts from the 4th OFDM symbol in the slot and has a length of 5 symbols, the HARQ-ACK information containing the DL SPS release instructing the release of the SPS can be assumed to be mapped to a PDSCH that starts from the 4th OFDM symbol in the slot where the DL SPS release was transmitted and has a length of 5 symbols, and the corresponding HARQ-ACK information can be determined through the PDSCH-to-HARQ-ACK timing indicator and PUSCH resource indicator included in the control information instructing the DL SPS release. For example, if the starting symbol of the DL SPS PDSCH being transmitted starts from the 4th OFDM symbol in the slot and has a length of 5 symbols, the HARQ-ACK information containing the DL SPS release that instructs the release of the SPS can be assumed to be mapped to the PDSCH that starts from the 4th OFDM symbol in the slot and has a length of 5 symbols, as indicated by the TDRA (Time domain resource allocation) of the DCI, which is the DL SPS release, and the corresponding HARQ-ACK information can be determined through the PDSCH-to-HARQ-ACK timing indicator and PUSCH resource indicator included in the control information that instructs the DL SPS release.

[0579] [HARQ-ACK: Type 2 (dynamic) codebook related]

[0580] The terminal can transmit HARQ-ACK information transmitted within one PUCCH in slot n based on the PDSCH-to-HARQ_feedback timing value for PUCCH transmission of HARQ-ACK information in slot n for PDSCH reception or SPS PDSCH release, and K0, which is transmission slot location information of the PDSCH scheduled in DCI format 1_0 or 1_1. For example, for the transmission of HARQ-ACK information described above, the terminal can determine the HARQ-ACK codebook of the PUCCH transmitted in the slot determined by the PDSCH-to-HARQ_feedback timing and K0 based on the DAI (downlink assignment index) included in the DCI indicating PDSCH or SPS PDSCH release.

[0581] A DAI may consist of a Counter DAI and a Total DAI. The Counter DAI may be information indicating the location within the HARQ-ACK codebook of HARQ-ACK information corresponding to a PDSCH scheduled in DCI format 1_0 or DCI format 1_1. For example, the value of the counter DAI in DCI format 1_0 or 1_1 indicates the cumulative value of a PDSCH reception or SPS PDSCH release scheduled by DCI format 1_0 or DCI format 1_1 in a specific cell c. The aforementioned cumulative value may be set based on the PDCCH monitoring occasion and serving cell where the scheduled DCI exists.

[0582] According to one embodiment, Total DAI may be a value indicating the size of the HARQ-ACK codebook. For example, the value of Total DAI may represent the total number of previously scheduled PDSCH or SPS PDSCH releases, including the time when the DCI was scheduled. Additionally, Total DAI may be a parameter used in a Carrier Aggregation (CA) situation where the HARQ-ACK information in serving cell c includes HARQ-ACK information for PDSCHs scheduled in other cells, including serving cell c. In other words, the Total DAI parameter does not exist in a system operating as a single cell.

[0583] According to one embodiment, an example of operation for DAI is shown in FIG. 20. In FIG. 20, when a terminal receives two carriers and transmits a HARQ-ACK codebook selected based on DAI in the n-th slot of carrier 0 (2002) to PUCCH (2020), the changes in the values ​​of Counter DAI (C-DAI) and Total DAI (T-DAI) indicated by the DCI found for each PDCCH monitoring occasion set for each carrier are described. First, the DCI found at m=0 (2006) may indicate a value of 1 for both C-DAI and T-DAI (2012). The DCI found at m=1 (2008) indicates a value of 2 for both C-DAI and T-DAI (2014). The DCI found in carrier 0 (c=0, 2002) of m=2 (2010) indicates a C-DAI value of 3 (2016). The DCI found in carrier 1 (c=1, 2004) of m=2 (2010) indicates a C-DAI value of 4 (2018). In this case, if carriers 0 and 1 are scheduled at the same monitoring occasion, the T-DAI can be indicated as 4 for both.

[0584] In FIGS. 19 and 20, the HARQ-ACK codebook determination may operate in a situation where only one PUCCH containing HARQ-ACK information is transmitted within a single slot. This is referred to as Mode 1. As an example of a method in which a single PUCCH transmission resource is determined within a single slot, when PDSCHs scheduled in different DCIs are multiplexed into a single HARQ-ACK codebook and transmitted within the same slot, the PUCCH resource selected for HARQ-ACK transmission is determined as the PUCCH resource indicated by the PUCCH resource field indicated by the DCI that last scheduled the PDSCH. That is, the PUCCH resource indicated by the PUCCH resource field indicated by the DCI scheduled prior to the above DCI may be ignored.

[0585] The description below defines methods and devices for determining the HARQ-ACK codebook in situations where two or more PUCCHs containing HARQ-ACK information can be transmitted within a single slot. This is referred to as Mode 2. A terminal may be able to operate only in Mode 1 (transmitting only one HARQ-ACK PUCCH within a slot) or only in Mode 2 (transmitting one or more HARQ-ACK PUCCHs within a slot). Alternatively, for a terminal that supports both Mode 1 and Mode 2, the base station may be configured to operate in only one mode by upper-level signaling, or Mode 1 and Mode 2 may be implicitly determined by DCI format, RNTI, DCI specific field values, scrambling, etc. For example, PDSCHs scheduled in DCI format A and associated HARQ-ACK information may be based on Mode 1, and PDSCHs scheduled in DCI format B and associated HARQ-ACK information may be based on Mode 2. Whether the HARQ-ACK codebook described above is semi-static or dynamic can be determined by the RRC signal.

[0586] [Multiple Cell Scheduling Method]

[0587] When a terminal supports control and data transmission and / or reception through multiple cells (or carriers), the base station may allocate PDSCH or PUSCH resources to each cell through various scheduling methods. Here, the multiple cells have different frequency bands in terms of frequency, and they may be located in adjacent bands or in non-adjacent bands. To receive PDSCH or PUSCH resources for each cell, the terminal may need to receive a DCI scheduled via a PDCCH. Typically, since a single DCI schedules one PDSCH or PUSCH, two DCIs may be required to schedule two PDSCHs or two PUSCHs for each of the two cells.

[0588] FIG. 21 is a diagram illustrating multiple cell scheduling according to an embodiment of the present disclosure. For convenience of explanation, the following description is based on PDSCH. However, the description is not limited thereto and can be extended and sufficiently applied to PUSCH. Referring to 2100 in FIG. 21, two PDSCHs (2106, 2108) can be scheduled through each DCI (2102, 2104) within two PDCCHs within each carrier (CC, Component Carrier). That is, PDSCH (2106) can be scheduled through one DCI (2102) of PDCCH in CC1, and PDSCH (2108) can be scheduled through one DCI (2104) of PDCCH in CC2. Each DCI format may be the same or different. Additionally, PDSCHs scheduled through each DCI may each have the same or different information regarding frequency resources, time resources, MCS, RV (redundancy value), HARQ process, NDI (new data indicator), precoding information, number of layers, antenna ports, VRB-PRB mapping, rate matching information, and / or CBG (Code Block Group) indication. Alternatively, as shown in 2110 of FIG. 21, two DCIs may be transmitted on the same carrier, but one of them may schedule a PDSCH of a different carrier. That is, a PDSCH (2116) may be scheduled through one DCI (2112) of the first PDCCH in CC1, and a PDSCH (2118) of CC2 may be scheduled through one DCI (2114) of the second PDCCH in CC1. Here, the first PDCCH and the second PDCCH may be different resources or the same resource, and in this case, two different DCIs may be transmitted and / or received through a single PDCCH resource. Although FIG. 21 illustrates a situation where two carriers are configured, if the terminal supports N carriers, N DCIs may schedule each of the PDSCHs.However, with this method, the number of DCIs required increases proportionally as the number of PDSCHs capable of scheduling for a plurality of carriers increases. Therefore, in situations where PDCCH resources are insufficient, using multiple DCIs for a single terminal can cause problems in efficiently managing PDCCH resources from a system perspective.

[0589] Therefore, it may be possible for a single DCI to schedule two or more PDSCHs. FIG. 22 is a diagram showing multiple cell scheduling according to one embodiment of the present disclosure.

[0590] Referring to FIG. 22, the PDSCH (2204) of CC1 and the PDSCH (2206) of CC2 can be scheduled through the DCI (2200) within the PDCCH of CC1. Since two PDSCHs can be scheduled using a single DCI, the resources of the PDCCH can be used more efficiently compared to the method described in FIG. 21. However, there is a possibility that the DCI size may increase. For example, if the size of the frequency resource field used to schedule one existing PDSCH is n bits, 2n bits may be arithmetically required for two PDSCHs to each support different frequency resources. However, there is a problem in that the DCI bit size required for each PDSCH scheduling cannot be increased by the number of PDSCHs that can be scheduled simultaneously. This is because the DCI applies channel coding using polar coding, and if the DCI size increases, the performance of polar coding degrades. Therefore, a DCI format for scheduling multiple PDSCHs for multiple cells can be configured using the following three field types.

[0591] * First field type: A single field representing information common to all co-scheduling cells. That is, a value corresponding to a single field may be a field that applies commonly to the scheduled cells. For example, fields such as Identifier for DCI formats, Downlink assignment index, TPC for scheduled PUCCH, PUCCH resource indicator, PDSCH-to-HARQ timing indicator, One-shot HARQ-ACK request, BWP indicator, VRB-PRB mapping, PRB bundling size, Antenna port(s), DMRS sequence initialization, Frequency hopping flag, Open-loop power control parameter set indication, Precoding / # of layer, and SRS resource indicator may fall under this category.

[0592] * Second field type: A method in which a single field is jointly displayed to each co-scheduled cell through separate information. A single field provides a value common to multiple cells, but the actual configuration or setting applied to each value can be determined based on the preceding upper signal of the cell. For example, fields such as Rate matching indicator, ZP CSI-RS trigger, TCI, SRS request, and SRS offset indicator may correspond to the second field type.

[0593] * Third field type: A method of configuring a separate field for each cell to be scheduled. This method may involve configuring multiple fields corresponding to the number of cells, whereby the value indicated by each field is applied to the cell associated with that field. For example, fields such as New data indicator per TB, Redundancy version per TB, HARQ process number, MCS, FDRA, Antenna port(s), TPC common for scheduled PUSCH, Precoding / # of layers, and PTRS-DMRS association may fall under this category.

[0594] Among the aforementioned field types, the third field type requires the largest DCI field size but can provide the highest scheduling flexibility. On the other hand, the first and second field types require the smallest DCI field size, but their scheduling flexibility may be lower compared to the third field type. The second field type may require the same DCI field size as the first field type, but additional related upper signal configuration information may be required to indicate different values ​​for each cell. To increase scheduling flexibility, it is inevitable that overhead will increase in terms of L1 (layer 1) signals or upper signals.

[0595] When scheduling multiple cells, some DCI fields were shared among each scheduled cell due to DCI size constraints. However, to provide more complete scheduling flexibility, it may be necessary for DCI fields to be applied to all scheduled cells. Below, a method using a 2-stage DCI concept is described to support the scheduling of multiple cells. For example, the first DCI can basically schedule a PDSCH for a specific cell, and through another DCI within that scheduled PDSCH, the PDSCHs of other cells can be scheduled. This method may be a scheduling method that utilizes all existing DCI fields, rather than dividing the DCI fields for the existing multiple cell scheduling method into the three types described above.

[0596] For example, FIG. 23 illustrates a method for scheduling multiple cells according to one embodiment of the present disclosure. A first DCI (2300) of CC1 can schedule a first PDSCH (2304) within the same CC1. Another second DCI (2302) within the first PDSCH (2304) can schedule a second PDSCH (2306) within another CC2. Accordingly, a terminal can receive the first PDSCH (2304) and the second PDSCH (2306) through the first DCI (2300) and the second DCI (2302).

[0597] Although FIG. 23 describes the second DCI as scheduling a single PDSCH belonging to a different cell, it is not limited to this and may be possible to schedule each PDSCH belonging to two or more different cells. Through this method, the DCI size transmitted from the PDCCH can be maintained at the same as before while supporting the scheduling of multiple cells.

[0598] The second DCI (2302) transmitted to the first PDSCH (2304) is transmitted via the PDSCH rather than the PDCCH, and since the resource location where the DCI is mapped is determined in advance, there is no need to separately constrain the size of the second DCI. For example, if the PDSCH scheduled by the second DCI belongs to two different cells, it may be possible to configure each of the two DCIs in a combined form. For example, if the total number of PDSCHs that can be scheduled through the second DCI is three and they belong to different cells, and when scheduling through the DCI of the existing PDCCH, the number of bits required for the DCI format is n1, n2, and n3 bits respectively, the second DCI may have a size of n1 + n2 + n3 bits, which is the sum of these bit numbers. In the following embodiments, a method for configuring the second DCI format and a method for indicating the second DCI format (or configuration) from the first DCI are described in relation to this. Since the second DCI (2302) is information for scheduling other PDSCHs, it may be desirable to place it before the first PDSCH (2304). Therefore, it may be possible to map it from the first symbol of the first PDSCH (2304) or immediately after the DMRS symbol.

[0599] [1st Example]

[0600] Hereinafter, methods for configuring the first DCI and the second DCI are described in the embodiments. Basically, the first DCI may include information for scheduling the PDSCH. Additionally, the first DCI may indicate whether the second DCI is transmitted within the scheduled PDSCH. At least one of the following two methods, or a combination thereof, may be possible.

[0601] Method 1-1: This involves indicating the presence or absence of the second DCI within the first DCI using a single bit. For example, it may be possible to indicate the absence of the second DCI with a value of 0 and the presence of the second DCI with a value of 1. Furthermore, the second DCI contains information for scheduling other cells, and if there are multiple cells, a method is required to indicate which of them are scheduled. For instance, if there are a total of N cells, and the base station schedules the PDSCH of a specific cell via the first DCI and informs the terminal that the second DCI exists, the base station needs to provide scheduling information for the other N-1 cells within the second DCI. Therefore, the DCI size corresponding to the i-th cell is n. i Assuming that, the first DCI size is n1, and the second DCI size is n2 + n3 + n4 + ... + n NIt may be possible. Additionally, the mapping of the second DCI may be mapped according to the ascending or descending order of the cell index. In summary, the size of the second DCI may be the combined size (or form) of the DCIs that schedule each of the N-1 cells. FIG. 28 is a diagram showing the configuration of the first DCI and the second DCI according to an embodiment of the present disclosure. The existence of the second DCI (2802) may be determined through one bit of the first DCI (2800). If the second DCI exists, the second DCI may include scheduling information for the cells set for the terminal, excluding the cell to which the second DCI transmitted and / or received. For example, if the first DCI contains scheduling information for the first cell, the first information (2810) in the second DCI (2802) may be referenced as scheduling information for the second cell, the second information (2812) in the second DCI (2802) may be referenced as scheduling information for the third cell, the third information (2814) in the second DCI (2802) may be referenced as scheduling information for the fourth cell, and the N-1 information (2816) in the second DCI (2802) may be referenced as scheduling information for the Nth cell. Accordingly, if the bit size indicating whether the second DCI is transmitted in the first DCI is 1 bit, the size of the second DCI can be set to include scheduling information for all remaining cells excluding the cell to which the first DCI was transmitted / received. (That is, the size of the second DCI can be based on the size of the scheduling information for cells other than the cell to which the first DCI was received.) As another example, the base station can provide a higher-level setting (e.g., higher layer message, RRC message, MAC CE) that limits the cells scheduled through the second DCI to some of the remaining cells rather than all remaining cells.For example, the base station may provide upper signal setting information to the terminal to allow only some of the remaining 2 cells to be scheduled through the second DCI, even though the total number of remaining cells is 5. If such upper signal setting information is not available, the terminal can identify that scheduling information for all remaining cells is included. For reference, in FIG. 28, if there is no scheduling information for the scheduling (2814) for the third cell, the bit values ​​for scheduling the cell may all be determined to be 0 or 1. Through this, the terminal can determine that there is no PDSCH scheduled (2814) for the third cell. This is merely an example, and it is also possible for some specific fields among the scheduling (2814) information for the third cell to have specific values. For example, even if the FDRA (frequency domain resource allocation) field is all 0 or 1, the terminal may determine that there is no scheduled (2814) PDSCH for the third cell. Since the size of the second DCI is based on a set of pre-configured cells, it may not be necessary to schedule PDSCH for all cells at a specific moment. Therefore, by setting all or some bits of the bit fields associated with the cell to a specific value, the base station may be able to inform the terminal that no actual PDSCH has been scheduled. For example, the size of the second DCI may be determined in advance by a higher signal (e.g., RRC message, MAC CE). As another example, the size of the second DCI may be indicated by the first DCI.

[0602] * Method 1-2: Indicates the existence of the second DCI through a specific field consisting of n bits within the first DCI. That is, the base station may inform the terminal of the existence of the second DCI and the combination of scheduleable cells constituting the second DCI. For example, if n is 2 bits, a bit value of 00 may indicate that the second DCI does not exist in the scheduled PDSCH. A bit value of 01 may indicate that the second DCI exists in the scheduled PDSCH and that the second DCI contains scheduling information for the first cell combination. A bit value of 10 may indicate that the second DCI exists in the scheduled PDSCH (or, the second DCI is scheduled to be transmitted) and that the second DCI contains scheduling information for the second cell combination. If the bit value is 11, it may be indicated that the second DCI exists in the scheduled PDSCH and that the second DCI includes scheduling information for the third cell combination. The first cell combination, the second cell combination, and / or the third cell combination may be determined in advance by upper signal setting information (e.g., RRC message, MAC CE), and the number of cells included in each cell combination may be substantially the same or different. Additionally, a specific code point may not be used if there is no upper signal setting information. FIG. 29 is a diagram showing the configuration of the first DCI and the second DCI according to an embodiment of the present disclosure. It may be possible to indicate whether the second DCI (2902) is transmitted and, if the second DCI is transmitted, which cell group combinations (e.g., first cell group, second cell group) are included in the scheduling information through the n bits of the first DCI (2900).In the case where the total number of cells within the cell group determined by this is 4 (e.g., a second cell corresponding to the first information (2910), a third cell corresponding to the second information (2912), a fourth cell corresponding to the third information (2914), and an Nth cell corresponding to the N-1 information (2916), each cell may include scheduling information for each cell in ascending or descending order or in the order set by the upper signal. Accordingly, the size of the second DCI has the characteristic of being determined in advance by the upper signal and the first DCI.

[0603] * Method 1-3: Similar to Method 1-2, but in Method 1-3, information regarding a specific cell group is indicated via n bits within the first DCI, and additionally, if there are multiple DCI formats that can be scheduled for each cell within the cell group, a specific DCI format may be indicated. For example, if the first DCI (e.g., n bits) indicates a first cell group and there are two cells in the first cell group, and the first cell can be scheduled with two DCI formats, the terminal may be instructed which DCI format is applied to the second DCI configuration. The DCI format may correspond to uplink scheduling information, downlink scheduling information, or other non-scheduling information (e.g., channel estimation or channel reporting, etc.). Alternatively, if a second DCI exists other than the bit indicating the presence or absence of the second DCI, a separate field may exist indicating the DCI format constituting the second DCI.

[0604] Scheduling information can be referenced as information included in the DCI field. For example, scheduling information may include at least some combinations or all of Identifier for DCI formats, Downlink assignment index, TPC for scheduled PUCCH, PUCCH resource indicator, PDSCH-to-HARQ timing indicator, One-shot HARQ-ACK request, BWP indicator, VRB (virtual resource block)-PRB (physical resource block) mapping, PRB bundling size, Antenna port(s), DMRS sequence initialization, Frequency hopping flag, Open-loop power control parameter set indication, Precoding / # of layer, SRS resource indicator, Rate matching indicator, ZP CSI-RS trigger, TCI, SRS request, SRS offset indicator, New data indicator per TB (transport block), Redundancy version per TB, HARQ process number, MCS, FDRA, Antenna port(s), TPC common for scheduled PUSCH, Precoding / # of layers, or PTRS (phase tracking reference signal)-DMRS associations.

[0605] For example, although it was explained that the second DCI is transmitted through the first PDSCH, the information included in the second DCI may also be transmitted / received through the MAC CE included in the first PDSCH. In this case, the terminal can identify the second DCI information through the MAC CE information after demodulating / decoding the Transport Block within the first PDSCH. Alternatively, the information included in the second DCI may be transmitted through the header information of the MAC CE, which may be indicated by a specific code point of the MAC CE header.

[0606] [2nd Example]

[0607] Hereinafter, in the embodiments, a method for setting a resource area in which the second DCI is transmitted and received is described. The second DCI is transmitted / received through the first PDSCH (2304) as described in FIG. 23, and at this time, the size of the resource in which the second DCI is transmitted / received can be determined through at least one of the following methods or a combination of some of them.

[0608] * Method 2-1: When the second DCI is transmitted through the first DCI, the resource area to which the second DCI is transmitted may be indicated through another DCI field. For example, the resource to which the second DCI is transmitted may be determined by indicating time or frequency resource information through a field of the first DCI. For example, the resource size allocated for the second DCI may be determined by indicating a code rate value through a field of the first DCI. For example, the second DCI size may be determined through at least one of the methods described in the first embodiment, and the resource information size may be determined through the determined DCI size and code rate. The determined resource may be mapped from the first symbol of the first PDSCH (2304) or from the first symbol immediately following the DMRS symbol. For example, the code rate may be determined in advance as a candidate value by a higher signal (e.g., MAC CE, and / or RRC message), and one of these values ​​may be indicated through the first DCI.

[0609] * Method 2-2: A code rate value may be set in advance as an upper signal, and the existence of a second DCI may be indicated through the first DCI. In this case, the resource size allocated for the second DCI may be determined based on the code rate value and the number of bits (or size) of the second DCI.

[0610] Based on the resource size determined through the above methods, the encoded / decoded information of the second DCI information can be mapped within the first PDSCH based on time-first mapping or frequency-first mapping. Time-first mapping can be referenced by allocating all information (or encoded / decoded information) to the frequency band assigned to the first PDSCH for each symbol, and then performing the same operation on the next symbol if the information is not fully mapped. In this case, if the number of information items to be allocated to the last symbol is smaller than the frequency band assigned to the first PDSCH, the information (or information elements) can be mapped evenly in terms of frequency band. Additionally, when mapping across different frequency resources in a specific symbol, the information can be mapped in order from the highest frequency value to the lowest value, or vice versa. Frequency axis priority mapping can be referenced as allocating information to the time resources allocated to the first PDSCH for each specific frequency value (or tone), and then, if the information is not fully mapped, performing the same operation at the next frequency value. In this case, if the number of information to be allocated to the last frequency value is smaller than the frequency band allocated to the first PDSCH, the information can be mapped evenly in terms of time resources. Additionally, when information is mapped across different time resources at a specific frequency value, the information may be mapped from the fastest symbol value to the lowest value, or vice versa.

[0611] [Third Example]

[0612] Hereinafter, in one embodiment, transmission / reception methods of PDSCHs scheduled with a first DCI and a second DCI are described. The first DCI is transmitted to a terminal by a base station on a PDCCH, and the second DCI may be transmitted from a base station to a terminal on a PDSCH scheduled based on the first DCI. Accordingly, generally, the time at which the terminal receives the second DCI may be substantially the same as or later than the first DCI.

[0613] FIG. 24 is a diagram illustrating the transmission / reception of PDSCHs scheduled by a first DCI and a second DCI according to an embodiment of the present disclosure. The first DCI (2400) schedules the first PDSCH (2404), and the second DCI (2402) included in the first PDSCH can schedule the second PDSCH (2406) of another cell. Since the time at which the terminal receives the second DCI is likely to be the same as or later than the time at which it receives the first DCI, the time at which the terminal identifies the scheduling information of the second PDSCH (2406) may be substantially the same as or later than the time at which the terminal identifies the scheduling information of the first PDSCH (2404). Therefore, as shown in FIG. 23, it may be impossible for the first PDSCH (2304) and the second PDSCH (2306) to be scheduled at the same time depending on the terminal's capabilities. Accordingly, the second PDSCH (2406) can be scheduled after the second DCI (2402) has been transmitted / received. With this in mind, at least one of the following methods or a combination thereof may be considered.

[0614] * Method 3-1: The difference between the end time of the first symbol of the first PDSCH (2404) and the start time of the first symbol of the second PDSCH (2406) may be at least a specific time (2410) (or, interval, offset). That is, the start symbol of the second PDSCH may be located after a specific time (2410) from the start symbol of the first PDSCH. The value of the specific time (2410) may be different depending on various variables. For example, the value of the specific time (2410) may vary depending on terminal capability. For example, the value of the specific time (2410) may vary depending on the subcarrier interval. For example, the value of the specific time (2410) may vary depending on the frequency resource size to which the first PDSCH or the second PDSCH is scheduled. For example, the value may vary depending on the respective DMRS symbol position. For example, the value may vary depending on the time resource or frequency resource size of the first DCI.

[0615] * Method 3-2: Similar to Method 3-1, but based on the starting symbol (or last symbol) of the first DCI (2402) rather than the first symbol of the first PDSCH (2404) as the criterion for determining a specific time (2410).

[0616] * Method 3-3: The second PDSCH may always be scheduled starting from the slot following the slot in which the second DCI is transmitted and received. FIG. 25 is a diagram illustrating the transmission / reception of PDSCHs scheduled by the first DCI and the second DCI according to an embodiment of the present disclosure. The first PDSCH (2504) scheduled by the first DCI (2500) is located in slot n, and the second PDSCH (2506) scheduled by the second DCI (2502) located in the first PDSCH (2504) may be located in the next slot n+1. Or, if slot n+1 is an uplink slot, the second PDSCH (2506) may be scheduled in the immediately following downlink slot. Alternatively, the data scheduled by the second DCI (2502) located in the first PDSCH (2504) may be the first PUSCH (2506). This is because slot n may be a downlink and slot n+1 may be an uplink. In this case, the second DCI may be able to include uplink scheduling information for CC (component carrier) 2.

[0617] Although the methods described above have been illustrated in FIGS. 24 and 25, the second PDSCH or the first PUSCH in FIGS. 24 and 25 may not be limited to corresponding to a specific single cell, and may also be applied to second PDSCHs or first PUSCHs existing in two or more cells. For example, the description of the second PDSCH or the first PUSCH may be applied not only to a single cell but also to multiple cells.

[0618] [Fourth Example]

[0619] Hereinafter, in one embodiment, different transmission / reception methods of PDSCHs scheduled by the first DCI and the second DCI are described. The first to third embodiments described above describe a method of scheduling through the first DCI and the second DCI in multiple cells. The fourth embodiment describes a method of scheduling different PDSCHs or PUSCHs across multiple slots in a single cell. FIG. 26 is a diagram illustrating a case in which PDSCHs or PUSCHs are transmitted / received across multiple slots according to one embodiment of the present disclosure. The first DCI (2600) of FIG. 26 schedules the first PDSCH (2604), and subsequent PDSCHs (2606, 2608, 2610) or PUSCHs (2606, 2608, 2610) in the slots can be scheduled through the second DCI (2602) included in the first PDSCH. Here, all resources (2606, 2608, 2610) may be scheduled with PDSCHs, all resources may be scheduled with PUSCHs, or a combination of PDSCHs and PUSCHs may be scheduled.

[0620] The scheduling information of the second DCI may include information for scheduling each slot. That is, the configuration of the second DCI for scheduling multiple cells in the first embodiment may be changed and applied to the configuration of the second DCI for scheduling multiple slots in the fourth embodiment. (Therefore, the description of the configuration of the second DCI described in the first embodiment may be applied to the fourth embodiment unless there is a contradiction.) FIG. 26 shows a situation where a total of three PDSCHs (2606, 2608, 2610) are scheduled through the second DCI (2602), and the scheduling information for each PDSCH may be included in the second DCI. In this case, the size and resource mapping of the second DCI may be similarly applicable to the methods described in the first and second embodiments. (Therefore, the size and resource mapping method of the second DCI described in the first and second embodiments may also be applied to the fourth embodiment unless there is a contradiction.) Additionally, the DCI formats constituting the second DCI may consist of some combination of information such as uplink scheduling or downlink scheduling or channel estimation or channel reporting. The terminal may identify (or determine) the scheduling information of each of the PDSCHs (or PUSCHs) (2606, 2608, 2610) through the second DCI (2602). Although FIG. 26 describes data resources being scheduled across consecutive slots, this is merely an example and some slots may not be scheduled. For example, if the second DCI (2602) is transmitted and received in slot n, the terminal may be scheduled to transmit and receive data in slots n+2, n+4, and n+6, respectively.

[0621] [5th ​​Example]

[0622] Hereinafter, in one embodiment, different transmission / reception methods of PDSCHs scheduled with a first DCI and a second DCI are described. PDSCHs scheduled with two DCIs may be scheduled through multiple different cells or through different slots of the same cell. Additionally, PDSCHs scheduled with the second DCI may be scheduled through multiple different cells and different slots. (i.e., a combination of multiple cells and multiple slots may be considered.) FIG. 27 is a diagram showing a situation in which PDSCHs or PUSCHs are transmitted / received across multiple cells and multiple slots according to one embodiment of the present disclosure. A first PDSCH (2704) is scheduled through the first DCI (2700) of FIG. 27, and a second DCI (2702) may be included in the first PDSCH (2704) to be transmitted and / or received. For example, the second DCI (2702) can schedule PDSCHs or PUSCHs in multiple cells and multiple slots. In FIG. 27, resources (2704, 2706, 2708, 2710, 2712, 2714, 2716, 2718) may each be a PDSCH or a PUSCH. For example, resources (2704, 2706, 2708, 2710, 2712, 2714, 2716, 2718) may be allocated for PDSCH and / or PUSCH. Since a total of 7 PDSCHs or PUSCHs or combinations thereof may be scheduled by the second DCI (2702) in FIG. 27, the second DCI (2702) may include at least 7 individual scheduling information. In Fig. 27, it is described that each data resource is scheduled across four consecutive slots (n, n+1, n+2, n+3) spanning two cells, but this is merely an example and some data resources may not be scheduled. For example, only some slots (n, n+2, n+3) may be scheduled.

[0623] According to one embodiment, in addition to indicating whether the first DCI described in the first embodiment transmits the second DCI, it may also indicate one of the scheduling methods described in FIG. 23, FIG. 26, and FIG. 27. That is, in addition to indicating whether the second DCI transmits the first DCI, it may be possible to indicate whether the second DCI provides scheduling information for multiple cells as described in FIG. 23, scheduling information for multiple slots as described in FIG. 26, or scheduling information for multiple cells and slots as described in FIG. 27. This may be configured in advance for the terminal via a higher-level signal (e.g., RRC message, MAC CE). For example, the first DCI may indicate to the terminal whether the second DCI transmits, whether the second DCI will indicate scheduling information for multiple cells, and / or whether the second DCI will indicate scheduling information for multiple slots.

[0624] FIG. 30 is a diagram illustrating a method for scheduling data resources through a first DCI and a second DCI according to an embodiment of the present disclosure.

[0625] Referring to FIG. 30, a terminal according to one embodiment may receive upper signal setting information (e.g., RRC message and / or MAC CE (medium access control control element)) from a base station in advance. For example, the upper signal setting information may include at least one of the upper signal setting information described in the first to fifth embodiments or a combination thereof.

[0626] According to one embodiment, the terminal may subsequently determine whether the first scheduled PDSCH contains second DCI information through first DCI search (or monitoring). For example, if the terminal receives a notification from a base station that the second DCI is included, the terminal may receive the second DCI information included in the first PDSCH and identify (or determine) information for scheduling the second PDSCHs (or PUSCHs) based on the methods described in the first to fifth embodiments. Based on the identified scheduling information, the terminal may receive (or transmit) the second PDSCHs (or PUSCHs) under scheduling conditions composed of a plurality of cells or a plurality of slots or a combination thereof.

[0627] FIG. 31 is a drawing illustrating the structure of a terminal in a wireless communication system according to one embodiment of the present disclosure.

[0628] Referring to FIG. 31, the terminal may include a transceiver (referring to a terminal receiver (3100) and a terminal transmitter (3110)), a memory (not shown), and a terminal processing unit (3105, or a terminal control unit or processor). Depending on the communication method of the terminal described above, the transceiver (3100, 3110), memory, and terminal processing unit (3105) of the terminal may operate. However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more components or fewer components than the components described above. Furthermore, the transceiver, memory, and processor may be implemented in the form of a single chip. The terminal of FIG. 31 of the present disclosure may correspond to the terminals of FIG. 1 through FIG. 30.

[0629] According to one embodiment, the transceiver may transmit and / or receive a signal with a base station. Here, the signal may include control information and data. To this end, the transceiver may be composed of an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. However, this is merely one embodiment of the transceiver, and the components of the transceiver are not limited to an RF transmitter and an RF receiver.

[0630] According to one embodiment, the transceiver receives a signal through a wireless channel and outputs it to a processor, and can transmit the signal output from the processor through the wireless channel.

[0631] According to one embodiment, the memory may store programs and data necessary for the operation of the terminal. Additionally, the memory may store control information or data included in signals transmitted or received by the terminal. The memory may be composed of a storage medium or a combination of storage media, such as ROM (read-only memory), RAM (random access memory), a hard disk, a CD-ROM, and a DVD. Additionally, there may be multiple memories.

[0632] According to one embodiment, at least one processor (or controller) can control a series of processes to enable the terminal to operate according to the above-described embodiment. For example, the processor can control the components of the terminal to receive a DCI composed of two layers and receive a plurality of PDSCHs simultaneously. There may be multiple processors, and the processors can perform the control operation of the terminal components by executing a program stored in memory.

[0633] FIG. 32 is a drawing illustrating the structure of a base station in a wireless communication system according to one embodiment of the present disclosure.

[0634] Referring to FIG. 32, a base station may include a transceiver unit, which refers to a base station receiver (3200) and a base station transmitter (3210), a memory (not shown), and a base station processing unit (3205, or a base station control unit or processor). According to the communication method of the base station described above, the transceiver unit (3200, 3210), the memory, and the base station processing unit (3205) of the base station may operate. However, the components of the base station are not limited to the examples described above. For example, the base station may include more components or fewer components than the components described above. Furthermore, the transceiver unit, the memory, and the processor may be implemented in the form of a single chip. The base station of FIG. 32 of the present disclosure may correspond to the base station of FIG. 1 to FIG. 31.

[0635] According to one embodiment, the transceiver may transmit and / or receive signals with a terminal. For example, the signal may include control information and data. To this end, the transceiver may be composed of an RF (radio frequency) transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. However, this is merely one embodiment of the transceiver, and the components of the transceiver are not limited to an RF transmitter and an RF receiver.

[0636] According to one embodiment, the transceiver receives a signal through a wireless channel and outputs it to a processor, and can transmit the signal output from the processor through the wireless channel.

[0637] According to one embodiment, the memory can store programs and data necessary for the operation of the base station. Additionally, the memory can store control information or data included in signals transmitted and received by the base station. The memory may be composed of a storage medium or a combination of storage media, such as ROM, RAM, a hard disk, CD-ROM, and DVD. Additionally, there may be multiple memories.

[0638] According to one embodiment, at least one processor (or controller) can control a series of processes to enable a base station to operate in accordance with the embodiments of the present disclosure described above. For example, the processor can control each component of the base station to configure two layers of DCIs containing allocation information for a plurality of PDSCHs and to transmit them. There may be multiple processors, and the processors can perform control operations on the components of the base station by executing a program stored in memory.

[0639] Methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

[0640] When implemented in software, a computer-readable storage medium may be provided for storing one or more programs (software modules). One or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. One or more programs include instructions that cause the electronic device to execute methods according to the embodiments described in the claims or specification of this disclosure.

[0641] Such programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, ROM (Read Only Memory), Electrically Erasable Programmable Read Only Memory (EEPROM), magnetic disc storage devices, Compact Disc-ROM (CD-ROM), Digital Versatile Discs (DVDs), or other forms of optical storage devices, magnetic cassettes. Alternatively, they may be stored in memory composed of some or all of these. Additionally, each constituent memory may include multiple units.

[0642] Additionally, the program may be stored on an attachable storage device accessible via a communication network such as the Internet, Intranet, Local Area Network (LAN), Wide LAN (WLAN), or Storage Area Network (SAN), or a combination thereof. Such a storage device may be connected to the device performing the embodiment of the present disclosure through an external port. Additionally, a separate storage device on the communication network may be connected to the device performing the embodiment of the present disclosure.

[0643] In the specific embodiments of the present disclosure described above, the components included in the invention are expressed in a singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the situation presented for convenience of explanation, and the present disclosure is not limited to singular or plural components; even if a component is expressed in the plural form, it may be composed of a singular form, or even if a component is expressed in the singular form, it may be composed of a plural form.

[0644] Meanwhile, the embodiments of the present disclosure disclosed in this specification and drawings are merely specific examples provided to facilitate the explanation of the technical content of the present disclosure and to aid in understanding the present disclosure, and are not intended to limit the scope of the present disclosure. That is, it is obvious to those skilled in the art that other variations based on the technical concept of the present disclosure are possible. Furthermore, each of the above embodiments may be combined and operated as needed. For example, parts of one embodiment of the present disclosure and parts of another embodiment may be combined to operate a base station and a terminal. For example, parts of the first embodiment and the second embodiment of the present disclosure may be combined to operate a base station and a terminal. In addition, although the above embodiments are presented based on an FDD LTE system, other variations based on the technical concept of the above embodiments may be implemented in other systems such as a TDD LTE system, 5G, or NR system.

[0645] Meanwhile, the order of description in the drawings illustrating the method of the present disclosure does not necessarily correspond to the order of execution, and the order of execution may be changed or executed in parallel.

[0646] Alternatively, the drawings describing the method of the present disclosure may omit some components and include only some components to the extent that the essence of the present invention is not impaired.

[0647] In addition, the method of the present disclosure may be implemented by combining some or all of the contents included in each embodiment to the extent that it does not impair the essence of the invention.

[0648] Various embodiments of the present disclosure have been described above. The foregoing description of the present disclosure is for illustrative purposes only, and the embodiments of the present disclosure are not limited to the disclosed embodiments. Those skilled in the art will understand that modifications can be easily made to other specific forms without altering the technical spirit or essential features of the present disclosure. The scope of the present disclosure is defined by the claims set forth below rather than by the foregoing detailed description, and all modifications or variations derived from the meaning and scope of the claims and equivalent concepts thereof should be interpreted as being included within the scope of the present disclosure.

Claims

1. In a method performed by UE (user equipment), A step of receiving a first DCI (downlink control information) for scheduling a first PDSCH (physical downlink shared channel) from a base station, wherein the first DCI indicates whether a second DCI will be received; A step of receiving a second DCI for scheduling one or more PDSCHs based on the first DCI; and A method comprising the step of receiving one or more PDSCHs based on the second DCI.

2. In Claim 1, A method in which the first DCI indicates information about cells associated with the one or more PDSCHs scheduled by the second DCI.

3. In Claim 1, The above second DCI is received within the above first PDSCH, and A method in which the first DCI includes a field indicating resource information in which the second DCI is received.

4. In Claim 1, A method in which a second PDSCH among the above one or more PDSCHs is received from the base station after a specified time based on the first PDSCH or the first DCI.

5. In a method performed by a base station, A step of transmitting a first DCI (downlink control information) to a UE (user equipment) for scheduling a first PDSCH (physical downlink shared channel), wherein the first DCI indicates whether a second DCI will be transmitted; A step of transmitting a second DCI for scheduling one or more PDSCHs based on the first DCI; and A method comprising the step of transmitting one or more PDSCHs based on the second DCI.

6. In Claim 5, A method in which the first DCI indicates information about cells associated with the one or more PDSCHs scheduled by the second DCI.

7. In Claim 5, The above second DCI is transmitted within the above first PDSCH, and A method in which the first DCI includes a field indicating resource information in which the second DCI is received.

8. In Claim 5, A method in which a second PDSCH among the above one or more PDSCHs is transmitted to the UE after a specified time based on the first PDSCH or the first DCI.

9. Regarding UE (user equipment), At least one transceiver; At least one processor communicatively coupled to the above at least one transceiver; and It includes at least one memory that is communicationally coupled to the above at least one processor and stores instructions, and The above instructions are executed individually or in any combination by the above at least one processor, so that the UE: Receives a first DCI (downlink control information) for scheduling a first PDSCH (physical downlink shared channel) from a base station, and the first DCI indicates whether to receive a second DCI. Receiving a second DCI for scheduling one or more PDSCHs based on the first DCI above, and A UE that receives one or more PDSCHs based on the above second DCI.

10. In Claim 9, The above first DCI indicates information about cells associated with the one or more PDSCHs scheduled by the above second DCI, UE.

11. In Claim 9, The above second DCI is received within the above first PDSCH, and The above-mentioned first DCI includes a field indicating resource information in which the above-mentioned second DCI is received, in a UE.

12. In Claim 9, Among the above one or more PDSCHs, the second PDSCH is received from the base station after a specified time based on the first PDSCH or the first DCI, in a UE.

13. Regarding base stations, At least one transceiver; At least one processor communicatively coupled to the above at least one transceiver; and It includes at least one memory that is communicationally coupled to the above at least one processor and stores instructions, and The above instructions are executed individually or in any combination by the above at least one processor, so that the base station: Transmits a first DCI (downlink control information) to the UE (user equipment) for scheduling a first PDSCH (physical downlink shared channel), and the first DCI indicates whether a second DCI will be transmitted. Transmitting a second DCI for scheduling one or more PDSCHs based on the first DCI above, and A base station that transmits one or more PDSCHs based on the above second DCI.

14. In Claim 13, A base station in which the first DCI indicates information about cells associated with the one or more PDSCHs scheduled by the second DCI.

15. In Claim 13, The above second DCI is transmitted within the above first PDSCH, and The above-mentioned first DCI includes a field indicating resource information in which the above-mentioned second DCI is received, a base station.

Images