Method and apparatus of repetitive transmission and reception for downlink control information in wireless communication system

The method and apparatus optimize downlink control information transmission and reception in 5G systems by employing multiple TRP-based PDCCH iterations, addressing efficiency and reliability challenges, particularly in scenarios with multiple TRPs and diverse service demands.

KR103046459B1Active Publication Date: 2026-11-10SAMSUNG ELECTRONICS CO LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
KR1020200138299
Authority / Receiving Office
KR · KR
Patent Type
Patents
Current Assignee / Owner
Filing Date
2020-10-23
Publication Date
2026-11-10
Estimated Expiration
2040-10-23

AI Technical Summary

Technical Problem

Existing wireless communication systems face challenges in efficiently and repeatedly transmitting and receiving downlink control information, which is crucial for providing various services in 5G communication systems, especially in scenarios involving multiple transmission-reception-points (TRPs) and diverse service requirements such as eMBB, mMTC, and URLLC.

Method used

A method and apparatus that involves transmitting and receiving first information related to a multiple TRP-based PDCCH iteration, including the number of blind decodings for PDCCH candidates, control resources, and search spaces, allowing terminals to monitor PDCCH candidates effectively, and enabling base stations to transmit downlink control information based on these parameters.

Benefits of technology

Enhances the efficiency and reliability of downlink control information transmission and reception, supporting diverse 5G services by optimizing the number of blind decodings and resource allocation, thereby improving service provision in complex wireless communication environments.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 112020112675233-PAT00063_ABST
    Figure 112020112675233-PAT00063_ABST
Patent Text Reader

Abstract

The present disclosure relates to a communication technique and a system for integrating a 5G communication system with IoT technology to support higher data transmission rates than those of 4G systems. The present disclosure may be applied to intelligent services (e.g., smart homes, smart buildings, smart cities, smart cars or connected cars, healthcare, digital education, retail, security and safety-related services, etc.) based on 5G communication technology and IoT-related technology. The present disclosure discloses a method for improving coverage of a PDCCH in a wireless communication system. A method performed by a terminal in a wireless communication system according to an embodiment of the present disclosure comprises: transmitting first information related to a multiple TRP-based PDCCH iteration to a base station; the first information includes second information indicating the number of blind decodings for PDCCH candidates; receiving third information regarding a set of control resources and fourth information regarding a search space from the base station; and monitoring PDCCH candidates based on a span, which is the number of consecutive symbols in a slot set for monitoring PDCCH, the second information, the third information, and the fourth information, wherein the second information indicates the terminal's ability to count two PDCCH candidates as two PDCCH candidates or three PDCCH candidates.
Need to check novelty before this filing date? Find Prior Art

Description

Technology Field

[0001] The present disclosure relates to a method and apparatus for repeatedly transmitting and receiving downlink control information in a wireless communication system. Background Technology

[0002] Efforts are being made to develop improved 5G or pre-5G communication systems to meet the increasing demand for wireless data traffic since 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 transmission distance 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.

[0003] 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.

[0004] 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 techniques 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 3eG and IoT technologies.

[0005] 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. The problem to be solved

[0007] The disclosed embodiments aim to provide an apparatus and method capable of effectively providing services in a wireless communication system.

[0008] The disclosed embodiment aims to provide an apparatus and method for efficiently transmitting and receiving downlink control information in a wireless communication system.

[0009] The disclosed embodiment aims to provide an apparatus and method for efficiently and repeatedly transmitting and receiving downlink control information in a wireless communication system. means of solving the problem

[0010] A method performed by a terminal in a wireless communication system according to an embodiment of the present disclosure comprises: transmitting first information related to a multiple transmission-reception-point (TRP) based physical downlink control channel (PDCCH) iteration to a base station; the first information includes second information indicating the number of blind decodings for PDCCH candidates; receiving third information regarding a set of control resources and fourth information regarding a search space from the base station; and monitoring PDCCH candidates based on the second information, the third information and the fourth information, a span which is the number of consecutive symbols in a slot configured for the terminal to monitor the PDCCH, and the second information indicating the terminal's ability to count two PDCCH candidates as two PDCCH candidates or three PDCCH candidates.

[0011] In addition, in a wireless communication system according to an embodiment of the present disclosure, a terminal comprises a transceiver and, through the transceiver, transmits first information related to a multiple TRP-based PDCCH iteration to a base station, wherein the first information includes second information indicating the number of blind decodings for PDCCH candidates; receives from the base station through the transceiver third information regarding a set of control resources and fourth information regarding a search space; and comprises a processor configured to monitor PDCCH candidates based on the second information, the third information and the fourth information, a span which is the number of consecutive symbols in a slot configured for the terminal to monitor PDCCH, and the second information indicating the terminal's ability to count two PDCCH candidates as two PDCCH candidates or three PDCCH candidates.

[0012] Additionally, a method performed by a base station in a wireless communication system according to an embodiment of the present disclosure comprises: receiving first information related to a multiple TRP-based PDCCH iteration from a terminal; transmitting third information regarding a set of control resources and fourth information regarding a search space, wherein the first information includes second information indicating the number of blind decodings for PDCCH candidates; and transmitting downlink control information from PDCCH candidates based on the second information, the third information, and the fourth information, wherein the second information indicates the terminal's ability to count two PDCCH candidates as two PDCCH candidates or three PDCCH candidates.

[0013] In addition, in a wireless communication system according to an embodiment of the present disclosure, a base station comprises a transceiver and, through the transceiver, a first information related to a multiple TRP-based PDCCH iteration from a terminal, wherein the first information includes second information indicating the number of blind decodings for PDCCH candidates; through the transceiver, a third information regarding a set of control resources and a fourth information regarding a search space; and, through the transceiver, a processor configured to transmit downlink control information from PDCCH candidates based on the second information, the third information and the fourth information, wherein the second information indicates the terminal's ability to count two PDCCH candidates as two PDCCH candidates or three PDCCH candidates.

[0014] delete Brief explanation of the drawing

[0015] 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. 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. FIG. 3 is a diagram illustrating an example of a bandwidth portion setting in a wireless communication system according to one embodiment of the present disclosure. FIG. 4 is a diagram illustrating an example of setting a control resource set of a downlink control channel in a wireless communication system according to one embodiment of the present disclosure. FIG. 5a is a diagram illustrating the structure of a downlink control channel in a wireless communication system according to one embodiment of the present disclosure. FIG. 5b 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 monitoring positions within a slot. FIG. 6 is a diagram illustrating an example of DRX operation in a wireless communication system according to one embodiment of the present disclosure. 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. 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. FIG. 9 is a diagram illustrating a TCI indication MAC CE signaling structure for a PDCCH DMRS in a wireless communication system according to one embodiment of the present disclosure. FIG. 10 is a drawing illustrating an example of CORESET and search space beam settings in a wireless communication system according to one embodiment of the present disclosure. FIG. 11 is a diagram illustrating an example of frequency axis resource allocation of a PDSCH in a wireless communication system according to one embodiment of the present disclosure. FIG. 12 is a diagram illustrating an example of time-axis resource allocation of PDSCH in a wireless communication system according to one embodiment of the present disclosure. FIG. 13 is a diagram illustrating an example of time-axis resource allocation according to the subcarrier interval of a data channel and a control channel in a wireless communication system according to one embodiment of the present disclosure. FIG. 14 is a diagram illustrating the wireless protocol structure of a base station and a terminal in a single cell, carrier aggregation, dual connectivity situation in a wireless communication system according to one embodiment of the present disclosure. FIG. 15 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. FIG. 16 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. FIGS. 17 and 18 are drawings illustrating the operation of a terminal regarding the number of PDCCH candidates and the number of CCEs according to terminal capability reporting and whether base station transmission conditions are satisfied during repeated PDCCH transmission according to various embodiments of the present disclosure. FIG. 19 is a drawing illustrating the structure of a terminal in a wireless communication system according to one embodiment of the present disclosure. FIG. 20 is a drawing illustrating the structure of a base station in a wireless communication system according to one embodiment of the present disclosure. Specific details for implementing the invention

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

[0017] 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.

[0018] For the same reason, some components in the attached drawings have been exaggerated, omitted, or schematically depicted. Additionally, the dimensions of each component do not entirely reflect their actual dimensions. Identical or corresponding components in each drawing have been assigned the same reference numbers.

[0019] 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.

[0020] Hereinafter, the base station is an entity that performs resource allocation for terminals and may be at least one of a gNode B, gNB, eNode B, eNB, Node B, BS (Base Station), radio access unit, base station controller, or a node on a network. In addition, the base station may be a network entity comprising at least one of an IAB-donor (Integrated Access and Backhaul - donor) which is a gNB providing network access to terminal(s) through a network of backhaul and access links in an NR system, and an IAB-node which is a RAN (radio access network) node that supports NR access link(s) to terminal(s) and supports NR backhaul links to said IAB-donor or another IAB-node. A terminal can wirelessly connect through an IAB-node and transmit and receive data with an IAB-donor connected to at least one IAB-node through a backhaul link.

[0021] A terminal may include a UE (User Equipment), MS (Mobile Station), cellular phone, smartphone, 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 a base station to a terminal, and the Uplink (UL) refers to the wireless transmission path of a signal transmitted by a terminal to a base station. Furthermore, while LTE or LTE-A systems may be described below as examples, 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 technologies (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. Additionally, this disclosure may be applied to other communication systems with some modifications made at the discretion of a person with skilled technical knowledge, provided that such modifications do not significantly deviate from the scope of this disclosure.

[0022] At this point, it will 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 special-purpose computer, 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 instruction means 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 perform a series of operation steps on the computer or other programmable data processing equipment to create a process executed by the computer can also provide steps for executing the functions described in the flowchart block(s).

[0023] 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.

[0024] 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.

[0025] Wireless communication systems are evolving from providing early voice-oriented services to broadband wireless communication systems that provide high-speed, 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.

[0026] As a representative example of the above-mentioned broadband wireless communication system, the LTE 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.

[0027] 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).

[0028] eMBB aims to provide data transmission speeds that are superior to those supported by existing LTE, LTE-A, 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 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.

[0029] 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 requires support for a large number of terminal connections within a cell, improved terminal coverage, enhanced battery life, and reduced terminal costs. Since IoT devices are attached to various sensors and equipment to provide communication functions, the system must be able 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.

[0030] Finally, URLLC is a mission-critical cellular-based wireless communication service. For example, consider services used for remote control of robots or machinery, industrial automation, unmanned aerial vehicles, remote health care, and emergency alerts. Therefore, the communication provided by URLLC must offer very low latency and very high reliability. For instance, 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.

[0031] 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.

[0032] For convenience of explanation, some terms and names defined in 3GPP standards (specifications for 5G, NR, LTE, or similar systems) may be used. However, the present disclosure is not limited by these terms and names and may be equally applied to systems conforming to other standards. Furthermore, terms used in the following description to identify a connection node, to refer to network entities, to refer to messages, to refer to interfaces between network entities, and to refer to various identification information are examples provided for the convenience of explanation. Therefore, the present disclosure is not limited to the terms used, and other terms referring to objects having equivalent technical meanings may be used.

[0033] [NR Time-Frequency Resources]

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

[0035] 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.

[0036] The horizontal axis of FIG. 1 represents the time domain, and the vertical axis represents 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). In Fig. 1 is the number of OFDM symbols per subframe (110) for setting the subcarrier spacing (μ), and for a more specific description of the resource structure in a 5G system, refer to the TS 38.211 section 4 specification.

[0037] Figure 2 is a diagram illustrating a slot structure considered in a 5G system.

[0038] FIG. 2 illustrates an example of a frame (200), subframe (201), and slot (202) structure. 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 subcarrier spacing setting value are illustrated. 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.

[0039] [Table 1]

[0040]

[0041] [Bandwidth Section (BWP)]

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

[0043] Figure 3 is a diagram illustrating an example of a configuration for a bandwidth portion in a 5G communication system.

[0044] 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.

[0045] [Table 2]

[0046]

[0047] In [Table 2] above, "locationAndBandwidth" indicates the location and bandwidth in the frequency domain of the bandwidth part, "subcarrierSpacing" indicates the subcarrier spacing to be used in the bandwidth part, and "cyclicPrefix" indicates whether an extended CP (cyclic prefix) is used for the bandwidth part.

[0048] 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 above configuration information. The above information may be transmitted by the base station to the terminal via higher-layer signaling, for example, Radio Resource Control (RRC) signaling. At least one of the configured bandwidth portions 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).

[0049] According to some embodiments, 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 PDCCH for receiving system information required for initial connection (Remaining System Information; which may correspond to RMSI or System Information Block 1; SIB1) can be transmitted. The Control Resource Set and Search Space configured via the MIB may each be considered as Identity (ID) 0. The Control Resource Set and Search Space configured via the MIB may be referred to as a Common Control Resource Set and a Common Search Space, respectively. 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 Resource Set #0, that is, configuration information regarding Search Space #0. The terminal may regard the frequency range configured as Control Resource Set #0 obtained from the MIB as the initial bandwidth portion for initial access. In this case, the identifier (ID) of the initial bandwidth portion may be considered as 0. The above control resource set may be referred to as a control region, a control resource region, etc.

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

[0051] According to some embodiments, 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 to the terminal, the terminal can transmit and receive data at a specific frequency position within the system bandwidth.

[0052] Additionally, according to some embodiments, 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, 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.

[0053] In addition, according to some embodiments, a base station may set a bandwidth portion having different bandwidth sizes for the purpose of reducing the power consumption of 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 can be very inefficient in terms of power consumption. To reduce 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.

[0054] In the method for configuring the above bandwidth portion, 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. More specifically, the 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 configured through the MIB can be considered as the Initial Bandwidth Part, and through the configured Initial Bandwidth Part, the terminal can receive SIBs from the Physical Downlink Shared Channel (PDSCH). In addition to receiving SIBs, the Initial Bandwidth Part may also be utilized for Other System Information (OSI), paging, and Random Access.

[0055] [SS / PBCH Block]

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

[0057] 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.

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

[0059] - 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.

[0060] - 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, scheduling control information for a separate data channel that transmits system information, etc.

[0061] - 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.

[0062] 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 Set index of 0) from it. For example, 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-Locations (QCL assumption). The terminal can receive system information using downlink control information transmitted from Control Resource Set #0. The terminal can obtain configuration information related to the 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 resource set #0.

[0063] [DRX]

[0064] Figure 6 is a diagram illustrating DRX (Discontinuous Reception).

[0065] DRX (Discontinuous Reception) is an operation in which a terminal using a service receives data discontinuously while in an RRC Connected state, where a wireless link is established between the base station and the terminal. This DRX operation is also referred to as DRX operation in an RRC Connected state (i.e., C-DRX). When DRX is applied, the terminal can turn on the receiver at specific points to monitor the control channel, and turn off the receiver if no data is received for a certain period to reduce the terminal's power consumption. DRX operation can be controlled by a MAC layer device based on various parameters and timers.

[0066] Referring to FIG. 6, Active time (605) is the time during which the terminal wakes up at each DRX cycle to monitor the PDCCH. Active time (605) can be defined as follows.

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

[0068] - a Scheduling Request is sent on PUCCH and is pending; or

[0069] - a PDCCH indicating a new transmission addressed to the C-RNTI of the MAC entity has not been received after successful reception of a Random Access Response for the Random Access Preamble not selected by the MAC entity among the contention-based Random Access Preamble

[0070] The above drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, ra-ContentionResolutionTimer, etc. are timers whose values ​​are set by the base station, and have the function of setting the terminal to monitor the PDCCH when certain conditions are satisfied.

[0071] drx-onDurationTimer (615) is a parameter for setting the minimum time the terminal stays awake in the DRX cycle. drx-InactivityTimer (620) is a parameter for setting the additional time the terminal stays awake when receiving a PDCCH (630) instructing a new uplink transmission or downlink transmission. drx-RetransmissionTimerDL is a parameter for setting the maximum time the terminal stays awake to receive a downlink retransmission in the downlink HARQ procedure. drx-RetransmissionTimerUL is a parameter for setting the maximum time the terminal stays awake to receive an uplink retransmission grant in the uplink HARQ procedure. drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, and drx-RetransmissionTimerUL can be set, for example, to time, number of subframes, number of slots, etc. ra-ContentionResolutionTimer is a parameter for monitoring the PDCCH in the random access procedure.

[0072] The inActive time (610) is the time during which the PDCCH is not monitored or / or the PDCCH is not received during the DRX operation. The remaining time after subtracting the Active time (605) from the total time of performing the DRX operation may be the inActive time (610). If the terminal does not monitor the PDCCH during the Active time (605), it may enter a sleep or inActive state to reduce power consumption.

[0073] The DRX cycle refers to the period during which a terminal wakes up and monitors the PDCCH. In other words, it refers to the time interval or on-duration occurrence cycle between when the terminal monitors a PDCCH and when it monitors the next PDCCH. There are two types of DRX cycles: short DRX cycle and long DRX cycle. The short DRX cycle can be applied optionally.

[0074] Long DRX cycle (625) is the longer of the two DRX cycles set in the terminal. While operating as Long DRX, the terminal restarts drx-onDurationTimer (615) at a point where Long DRX cycle (625) has elapsed from the starting point (e.g., start symbol) of drx-onDurationTimer (615). When operating as Long DRX cycle (625), the terminal can start drx-onDurationTimer (615) in a slot after drx-SlotOffset in a subframe satisfying [Equation 1] below. Here, drx-SlotOffset refers to the delay before starting drx-onDurationTimer (615). drx-SlotOffset can be set to time, the number of slots, etc., as shown in [Equation 1] below.

[0075] [Mathematical Formula 1]

[0076]

[0077] Here, drx-LongCycleStartOffset can be used to define the subframe to start the Long DRX cycle (625) and drx-StartOffset can be used to define the subframe to start the Long DRX cycle (625). drx-LongCycleStartOffset can be set, for example, to time, number of subframes, number of slots, etc.

[0078] [PDCCH: DCI related]

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

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

[0081] DCI can be transmitted through the 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 terminal's identity. Different RNTIs may be used depending on the purpose of the DCI message, such as UE-specific data transmission, power control commands, or random access responses. In other words, the RNTI is not transmitted explicitly but is included in the CRC calculation process. Upon receiving a DCI message transmitted over the PDCCH, the terminal checks the CRC using the assigned RNTI; if the CRC check result is correct, the terminal knows that the message has been transmitted to it.

[0082] 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).

[0083] 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.

[0084] [Table 3]

[0085]

[0086] 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.

[0087] [Table 4]

[0088]

[0089]

[0090] 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.

[0091] [Table 5]

[0092]

[0093] 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.

[0094] [Table 6]

[0095]

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

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

[0098] Figure 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.

[0099] FIG. 4 illustrates an example in which two control resource sets (Control Resource Set #1 (401), Control Resource Set #2 (402)) are set within a terminal bandwidth part (UE bandwidth part) (410) on the frequency axis and one slot (420) on the time axis. The control resource sets can be set to specific frequency resources within the entire terminal bandwidth part (410) on the frequency axis. In FIG. 4, the specific frequency resource (403) illustrates an example of a frequency resource set to Control Resource Set #1 (401). The control resource sets can be set to one or more OFDM symbols on the time axis and can be defined as the Control Resource Set Duration (404). Referring to the example illustrated in FIG. 4, Control Resource Set #1 (401) is set to a Control Resource Set Duration of 2 symbols, and Control Resource Set #2 (402) is set to a Control Resource Set Duration of 1 symbol.

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

[0101] [Table 7]

[0102]

[0103] In the above [Table 7], 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 (SSB) indices or CSI-RS (Channel State Information Reference Signal) indices that are in a QCL (Quasi Co Located) relationship with DMRS transmitted from the corresponding control resource set.

[0104] FIG. 5a 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.

[0105] According to FIG. 5a, the basic unit of time and frequency resources constituting a control channel (PDCCH) 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, i.e., 12 subcarriers. A base station can concatenate REGs (503) to form a downlink control channel allocation unit.

[0106] As illustrated in FIG. 5a, 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 multiple REGs (503). For example, if the REG (503) illustrated in FIG. 5a is described, the REG (503) can be composed of 12 REs, and if 1 CCE (504) is composed of, for example, 6 REGs (503), then 1 CCE (504) can be composed of 72 REs. When a downlink control resource set is established, the corresponding area can be composed of multiple CCEs (504), and a specific downlink control channel can be mapped to one or multiple CCEs (504) and transmitted according to the Aggregation Level (AL) within the control resource set. The CCEs (504) in the control resource set are distinguished by numbers, and the numbers of the CCEs (504) can be assigned according to a logical mapping method.

[0107] The basic unit of the downlink control channel, namely the REG (503) illustrated in FIG. 5a, 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. 5a, 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, or 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 at 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 at all configured aggregation levels.

[0108] 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.

[0109] In 5G, parameters for the search space for a PDCCH can be configured from the base station to the terminal using 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 the control resource set index to be monitored in the search space. Configuration information for the search space for a PDCCH may include, for example, the information in [Table 8] below.

[0110] [Table 8]

[0111]

[0112]

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

[0114] According to the above 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.

[0115] 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.

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

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

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

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

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

[0121] 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.

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

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

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

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

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

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

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

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

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

[0132] INT-RNTI (Interruption RNTI): Used to indicate whether PDSCH is pucturing.

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

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

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

[0136] The aforementioned specified DCI formats may follow the definitions in [Table 9] below.

[0137] [Table 9]

[0138]

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

[0140] [Mathematical Formula 2]

[0141]

[0142] Y_(p,n μ s,f 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 time index.

[0143] In 5G, as multiple sets of search spaces can be set with different parameters (e.g., the parameters of [Table 8] above), 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 set to an X-slot period and search space set #2 is set to 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 may monitor either search space set #1 or search space set #2 in a specific slot.

[0144] [PDCCH: span]

[0145] A terminal can perform terminal capability reporting for each subcarrier interval when it has multiple PDCCH monitoring locations within a slot, and in this case, the concept of a Span can 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 represents 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 range of Y symbols from the first symbol of the Span.

[0146] FIG. 5b is a diagram illustrating, through a Span, a case where a terminal in a wireless communication system can have multiple PDCCH monitoring positions within a slot.

[0147] Referring to FIG. 5b, the Span can be, for example, (X,Y) = (7,4), (4,3), or (2,2), and each of the three cases is illustrated in FIG. 5b as reference numbers 510, 520, and 530. For example, 510 represents the case where there are two Spans within the slot that can be expressed as (7,4). The distance between the first symbols of the two Spans is expressed as X=7, and PDCCH monitoring locations can exist within a total of Y=3 symbols from the first symbol of each Span, indicating that search spaces 1 and 2 exist within Y=3 symbols, respectively. As another example, 520 represents the case where there are a total of three Spans within 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, which is greater than X=4. In 530, a case was represented in which there are a total of 7 spans that can be expressed as (2,2) within the slot, and a PDCCH monitoring location can exist within a total of Y=2 symbols from the first symbol of each span, and a search space 3 exists within Y=2 symbols.

[0148] [PDCCH: Terminal Capability Report]

[0149] The slot locations where the aforementioned common search space and terminal-specific search space are located are indicated by the monitoringSlotPeriodicityAndOffset parameter in [Table 8], which represents the configuration information for the search space for the PDCCH, and the symbol locations within the slot are indicated by a bitmap through the monitoringSymbolsWithinSlot parameter in [Table 8]. 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).

[0150] - Terminal Capability 1 (hereinafter referred to as "FG (Feature group) 3-1"): Terminal Capability 1 refers to the capability to monitor a monitoring occasion (MO) when that MO is located within the first 3 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 10] below. The above Terminal Capability 1 is a mandatory capability that all terminals supporting NR must support, and whether Terminal Capability 1 is supported may not be explicitly reported to the base station.

[0151] [Table 10]

[0152]

[0153] - Terminal Capability 2 (hereinafter referred to as "FG 3-2"): Terminal Capability 2 refers to the capability to monitor 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 11] below, when there is one monitoring occasion within the slot. The terminal capability 2 is optionally supported by the terminal, and whether terminal capability 2 is supported can be explicitly reported to the base station.

[0154] [Table 11]

[0155]

[0156] - Terminal Capability 3 (hereinafter referred to as FG 3-5, 3-5a, and 3-5b): Terminal Capability 3 indicates a pattern of monitoring occasions (MOs) that the terminal can monitor when multiple monitoring occasions exist within a slot for a common search space or a terminal-specific search space, as shown in [Table 12a] and [Table 12b] below. This pattern of MOs may consist of an interval X between starting 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, for example, {(2,2), (4,3), (7,3)}. This terminal capability is optional for the terminal to support, and whether this capability is supported and the aforementioned combinations of (X,Y) are explicitly reported to the base station.

[0157] [Table 12a]

[0158]

[0159] [Table 12b]

[0160]

[0161] The terminal may report to the base station whether it supports the aforementioned 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 MO is not placed in a location where the terminal cannot monitor.

[0162] [PDCCH: BD / CCE limit]

[0163] When multiple sets of search spaces are configured for a terminal, the following conditions may be considered in determining the set of search spaces that the terminal must monitor.

[0164] If the terminal receives the value of monitoringCapabilityConfig-r16, which is an upper layer signaling, as r15monitoringcapability, the terminal defines the maximum value for the number of PDCCH candidates that can be monitored and the number of CCEs constituting the entire search space (where the entire search space refers to the entire set of CCEs corresponding to the union area of ​​multiple search space sets) per slot, and if the value of monitoringCapabilityConfig-r16 is received as r16monitoringcapability, the terminal defines the maximum value for the number of PDCCH candidates that can be monitored and the number of CCEs constituting the entire search space (where the entire search space refers to the entire set of CCEs corresponding to the union area of ​​multiple search space sets) per span. The above monitoringCapabilityConfig-r16 may refer to the configuration information in [Table 13a] and [Table 13b] below.

[0165] [Table 13a]

[0166]

[0167] [Table 13b]

[0168]

[0169] [Condition 1: Limit on the maximum number of PDCCH candidates]

[0170] As described above, M is the maximum number of PDCCH candidate groups that the terminal can monitor, depending on the setting value of the upper layer signaling. μ The subcarrier interval is 15·2 μ In a cell set to kHz, if defined based on slots, follow [Table 14a] below, and if defined based on spans, follow [Table 14b] below.

[0171] [Table 14a]

[0172]

[0173] [Table 14b]

[0174]

[0175] [Condition 2: Limit on Maximum CCEs]

[0176] As described above, depending on the setting value of the upper-level signaling, C, which is the maximum number of CCEs constituting the entire search space (where the entire search space refers to the entire set of CCEs corresponding to the union area of ​​multiple search space sets), μ The subcarrier interval is 15·2 μ In a cell set to kHz, if defined based on slots, follow [Table 15a] below, and if defined based on spans, follow [Table 15b] below.

[0177] [Table 15a]

[0178]

[0179] [Table 15b]

[0180]

[0181] For the convenience of explanation, a situation in which both of the above conditions 1 and 2 are satisfied at a specific point in time is defined as "condition A". Therefore, not satisfying condition A may mean not satisfying at least one of the above conditions 1 and 2.

[0182] [PDCCH: Overbooking]

[0183] Depending on the configuration of the base station's search space sets, there may be cases where the above condition A is not satisfied at a specific point in time. If the above condition A is not satisfied at a specific point in time, the terminal may select and monitor only some of the search space sets configured to satisfy the above condition A at that point in time, and the base station may transmit a PDCCH to the selected search space set.

[0184] You can follow the method below to select some of the search spaces from the entire set of configured search spaces.

[0185] If the above condition A for the PDCCH is not satisfied at a specific time point (slot), the terminal (or base station) may preferentially select a search space set in which the search space type is set as a common search space among the search space sets existing at that time point, over a search space set in which the search space type is set as a terminal-specific search space.

[0186] When all sets of search spaces configured as common search spaces have been selected (i.e., when Condition A is satisfied even after selecting all search spaces configured as common search spaces), the terminal (or base station) may select sets of search spaces configured as terminal-specific search spaces. In this case, if there are multiple sets of search spaces configured as terminal-specific search spaces, the search space set with a lower search space set index may have a higher priority. Considering the priority, sets of terminal-specific search spaces may be selected within the range where Condition A is satisfied.

[0187] [QCL, TCI state]

[0188] 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 16] below. The TCI state is intended to announce / indicate the QCL relationship between a PDCCH (or PDCCH DMRS) and other RS ​​or channels. 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 16] below.

[0189] [Table 16]

[0190]

[0191] The above 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 spatial channel correlation.

[0192] The above QCL relationship can be configured for the terminal through the RRC parameters TCI-State and QCL-Info as shown in [Table 17] below. Referring to [Table 17] below, the base station can configure one or more TCI states for the terminal and provide up to two QCL relationships (qcl-Type1, qcl-Type2) for the RS that references the ID of the said TCI state, i.e., the target RS. At this time, each QCL information (QCL-Info) included in each said TCI state includes the serving cell index and BWP index of the reference RS pointed to by the corresponding QCL information, the type and ID of the reference RS, and the QCL type as shown in [Table 16] above.

[0193] [Table 17]

[0194]

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

[0196] 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 / indicate 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 CSI-RS or SSB corresponding to different beams and set to QCL type D.

[0197] Tables 18a through 18e below show valid TCI state settings according to the target antenna port type.

[0198] Table 18a below shows valid TCI state settings when the target antenna port is CSI-RS for tracking (TRS). The above TRS refers to a Non-Zero-Power (NZP) CSI-RS in which the repetition parameter is not set and trs-Info is set to true in the configuration information exemplified in Tables 19a and 19b below. In the case of setting 3 in Table 18a, it can be used for aperiodic TRS.

[0199] [Table 18a]

[0200]

[0201] Table 18b below shows valid TCI state settings when the target antenna port is CSI-RS for CSI. The above CSI-RS for CSI refers to an NZP CSI-RS in which the parameter indicating repetition (e.g., the repetition parameter) is not set and the above trs-Info is also not set to true.

[0202] [Table 18b]

[0203]

[0204] Table 18c below shows valid TCI state settings when the target antenna port is CSI-RS for BM (beam management) (BM, which is the same meaning as CSI-RS for L1 RSRP (Reference Signal Received Power) reporting). The above CSI-RS for BM refers to an NZP CSI-RS in which the repetition parameter among CSI-RS is set to have a value of On or Off, and the above trs-Info is not set to true.

[0205] [Table 18c]

[0206]

[0207] [Table 18d] below shows valid TCI state settings when the target antenna port is a PDCCH DMRS.

[0208] [Table 18d]

[0209]

[0210] [Table 18e] below shows valid TCI state settings when the target antenna port is PDSCH DMRS.

[0211] [Table 18e]

[0212]

[0213] The representative QCL setting method according to [Table 18a] to [Table 18e] above 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.

[0214] For configuration information of trs-Info related to the above NZP CSI-RS, refer to [Table 19a] and [Table 19b] below.

[0215] [Table 19a]

[0216]

[0217] [Table 19b]

[0218]

[0219] [PDCCH: TCI state related]

[0220] Specifically, the TCI state combinations applicable to the PDCCH DMRS antenna port are as shown in [Table 20] below. In [Table 20], the fourth row represents the combinations assumed by the terminal prior to RRC setup, and it is not possible to set them after RRC setup.

[0221] [Table 20]

[0222]

[0223] NR supports a hierarchical signaling method as shown in Fig. 8 for dynamic allocation of PDCCH beams.

[0224] 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.

[0225] Referring to FIG. 8, the base station can set a number of TCI states (805, 810, ..., 820) to the terminal through RRC signaling (800), and some of these can be set as TCI states for CORESET (825). Subsequently, the base station can instruct the terminal to use one of the TCI states for CORESET (830, 835, ..., 840) through MAC CE (MAC Control Element) signaling (845). Subsequently, the terminal receives a PDCCH based on beam information contained in the TCI state indicated by the MAC CE signaling.

[0226] FIG. 9 is a diagram illustrating a TCI indication MAC CE signaling structure for a PDCCH DMRS in a wireless communication system according to one embodiment of the present disclosure.

[0227] Referring to FIG. 9, the TCI indication MAC CE signaling for the PDCCH DMRS is composed of, for example, 2 bytes (16 bits) (Oct1 900, Oct2 905) and includes a 5-bit serving cell ID (915), a 4-bit CORESET ID (920), and a 7-bit TCI state ID (925).

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

[0229] Referring to FIG. 10, the base station can instruct the terminal to use one of the TCI state lists included in the CORESET (1000) settings via MAC CE signaling (1005). Subsequently, until another TCI state is instructed to the corresponding CORESET via another MAC CE signaling, the terminal considers that the same QCL information (beam #1, 1005) is applied to all search spaces #1, #2, #3 (1010, 1015, 1020) connected to the CORESET. The PDCCH beam allocation method described above makes it difficult to instruct a beam change faster than the MAC CE signaling delay, and also makes flexible PDCCH beam operation difficult because the same beam is applied collectively to all CORESETs regardless of search space characteristics.

[0230] The embodiments of the present disclosure below provide a more flexible method for setting and operating a PDCCH beam. For convenience of explanation, several distinct examples are provided in describing the embodiments of the present disclosure below; however, the exemplified embodiments are not mutually exclusive, and two or more embodiments may be appropriately combined and applied depending on the situation.

[0231] The base station may set one or more TCI states for a specific control resource set 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 resource set #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 resource set #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 resource set based on the QCL information within the activated TCI state.

[0232] For a control resource set (control resource set #0) with an index set to 0, if the terminal has not received a MAC CE activation command for the TCI state of control resource set #0, the terminal can assume that it has been QCLed with an SS / PBCH block (SSB) identified during 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 resource set #0.

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

[0234] [PDSCH: Regarding Frequency Resource Allocation]

[0235] FIG. 11 is a diagram illustrating an example of frequency axis resource allocation of a physical downlink shared channel (PDSCH) in a wireless communication system according to one embodiment of the present disclosure.

[0236] FIG. 11 illustrates three frequency axis resource allocation methods that can be configured through an upper layer in an NR wireless communication system: resource allocation (RA) type 0 (1110), RA type 1 (1120), and dynamic switch of resource allocation (RA type 0, RA type 1) (1130).

[0237] Referring to FIG. 11, if a terminal is configured to use only RA type 0 (1110) through upper layer signaling, some downlink control information (DCI) that assigns PDSCH to the terminal includes a bitmap (1111) composed of NRBG bits. The conditions for this will be described later. In this case, the NRBG refers to the number of RBGs (resource block groups) determined as shown in [Table 21] below according to the BWP size assigned by the BWP indicator and the upper layer parameter rbg-Size, and data is transmitted to the RBG indicated as 1 by the bitmap.

[0238] [Table 21]

[0239]

[0240] If the terminal is configured to use only RA type 1 (1120) through upper layer signaling, some DCIs that assign PDSCH to the terminal are It includes frequency axis resource allocation information consisting of bits. DL,BWP RBis the number of RBs of the downlink bandwidth portion (BWP). The conditions for this will be described later. Through this, the base station can set the starting VRB (1121) and the length (1123) of the frequency axis resources continuously allocated therefrom.

[0241] If the terminal is configured to use both RA type 0 and RA type 1 through upper layer signaling (1130), some DCIs that allocate PDSCH to the terminal include frequency axis resource allocation information composed of bits of the larger value (1133) of the payload (1111) for setting RA type 0 (1110) and the payload (1121, 1123) for setting RA type 1 (1120). The conditions for this will be described later. At this time, one bit (1131) may be added to the first part (MSB) of the frequency axis resource allocation information within the DCI to indicate the use of RA type 0 or RA type 1. For example, if the bit (1131) has a value of '0', it indicates that RA type 0 is used, and if it has a value of '1', it indicates that RA type 1 is used.

[0242] [Regarding PDSCH Time Resource Allocation]

[0243] The following describes a time domain resource allocation (TDRA) method for data channels in next-generation mobile communication systems (5G or NR systems).

[0244] The base station may set a table for time-domain resource allocation information for the Physical Downlink Shared Channel (PDSCH) and the Physical Uplink Shared Channel (PUSCH) for the terminal using upper-layer signaling (e.g., RRC signaling). For PDSCH, a table consisting of a maximum of maxNrofDL-Allocations = 16 entries may be set, and for PUSCH, a table consisting of a maximum of maxNrofUL-Allocations = 16 entries may be set. In one embodiment, the time domain resource allocation information may include PDCCH-to-PDSCH slot timing (corresponding to a slot-unit time interval between the time when the PDCCH is received and the time when the PDSCH scheduled by the received PDCCH is transmitted, denoted as K0), PDCCH-to-PUSCH slot timing (corresponding to a slot-unit time interval between the time when the PDCCH is received and the time when the PUSCH scheduled by the received PDCCH is transmitted, denoted as K2), information regarding the position and length of the start symbol in which the PDSCH or PUSCH is scheduled within the slot, and the mapping type of the PDSCH or PUSCH. For example, information such as [Table 22] or [Table 23] below may be transmitted from the base station to the terminal.

[0245] [Table 22]

[0246]

[0247] [Table 23]

[0248]

[0249] The base station may notify the terminal of one of the entries in the table for time domain resource allocation information in [Table 22] and [Table 23] above via L1 signaling (e.g., DCI) (e.g., indicated by the 'time domain resource allocation' field within the DCI). The terminal may obtain time domain resource allocation information for PDSCH or PUSCH based on the DCI received from the base station.

[0250] FIG. 12 is a diagram illustrating an example of time-axis resource allocation of PDSCH in a wireless communication system according to one embodiment of the present disclosure.

[0251] Referring to FIG. 12, the base station uses upper layer signaling to set the subcarrier spacing (SCS) of the data channel and control channel ( m PDSCH , m PDCCH The time axis position of the PDSCH resource can be indicated according to the scheduling offset (K0) value, and the OFDM symbol start position (S) (1203) and length (L) (1205) within one slot (1201) that are dynamically indicated through DCI.

[0252] FIG. 13 is a diagram illustrating an example of time-axis resource allocation according to the subcarrier interval of a data channel and a control channel in a wireless communication system according to one embodiment of the present disclosure.

[0253] Referring to FIG. 13, the subcarrier spacing (SCS) of the data channel and the control channel ( m PDSCH , m PDCCH In the case where ) is the same (1310, m PDSCH = m PDCCH ), since the slot numbers for data and control are the same, the base station and the terminal can generate a scheduling offset by aligning with a predetermined slot offset K0. On the other hand, when the subcarrier spacing of the data channel and the control channel is different (1320, m PDSCH ≠ m PDCCH Since the slot numbers for data and control are different, the base station and the terminal can generate a scheduling offset based on the subcarrier interval of the PDCCH and a predetermined slot offset K0. For example, if a terminal receives a DCI instructing a change in the bandwidth part in slot n, and the slot offset value indicated by the DCI is K0, then data can be received from the PDSCH scheduled in slot n+K0.

[0254] [Regarding Terminal Capability Reporting]

[0255] In LTE and NR systems, 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 is referred to as a UE capability report.

[0256] 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 such as supported frequency band combinations. Furthermore, in the case of the UE capability enquiry message, multiple UE capabilities for each RAT type may be requested through the container of a single RRC message transmitted by the base station, or the base station may transmit the UE capability enquiry message, which includes the request for each RAT type, to the terminal multiple times. That is, the UE capability inquiry may be repeated multiple times within a single message, and the terminal may construct and report the corresponding UE capability information message multiple times. In next-generation mobile communication systems, UE capability requests can be made for NR, LTE, EN-DC (E-UTRA - NR dual connectivity), and MR-DC (Multi-RAT dual connectivity). Additionally, while the UE capability enquiry message is generally transmitted initially after the terminal connects with the base station, the base station may request it under any conditions whenever necessary.

[0257] As described above, a terminal that has received a request from a base station to report UE capability configures its terminal capability according to the RAT type and band information requested from the base station. Examples of methods for a terminal to configure UE capability in an NR system are as follows.

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

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

[0260] 3. Subsequently, the terminal removes fallback BCs from the candidate list of the configured BCs. 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 can 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 applies to LTE bands. The BCs remaining after this step constitute the final "candidate BC list."

[0261] 4. The terminal selects the BCs to be reported by selecting BCs that match the requested RAT type from the final "Candidate BC List" above. In this step, the terminal constructs the supportedBandCombinationList in a predetermined order. That is, the terminal constructs the BCs and UE capabilities to be reported according to the pre-set order of rat-Type (nr -> eutra-nr -> eutra). Additionally, it constructs a featureSetCombination for the constructed supportedBandCombinationList and constructs 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.

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

[0263] After the terminal capability is configured, the terminal transmits 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 subsequently performs appropriate scheduling and transmission / reception management for the terminal.

[0264] [CA / DC Related]

[0265] FIG. 14 is a diagram illustrating the wireless protocol structure of a base station and a terminal in a single cell (1410), carrier aggregation (1420), and dual connectivity (1430) situation according to one embodiment of the present disclosure.

[0266] Referring to FIG. 14, the wireless protocol of the next-generation mobile communication system includes 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) layers at the terminal and the NR base station, respectively. In the following description, each layer device can be understood as a functional block responsible for the corresponding layer.

[0267] The main functions of the above NR SDAP (S25, S70) may include some of the following functions.

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

[0269] - Mapping function between a QoS flow and a DRB for both DL and UL for uplink and downlink

[0270] - Marking QoS flow ID for uplink and downlink (marking QoS flow ID in both DL and UL packets)

[0271] - Function to map reflective QoS flow to data bearers for uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).

[0272] Regarding the SDAP layer device, the terminal may receive a setting via an RRC message indicating 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 configured, the terminal may instruct the NAS QoS reflective setting 1-bit indicator (NAS reflective QoS) and the AS QoS reflective setting 1-bit indicator (AS reflective QoS) 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.

[0273] The main functions of the above NR PDCP (10-30, 10-65) may include some of the following functions.

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

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

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

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

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

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

[0280] - Retransmission of PDCP SDUs

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

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

[0283] The reordering function of the above NR PDCP 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 above NR PDCP 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.

[0284] The main functions of the above NR RLC (S35, S60) may include some of the following functions.

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

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

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

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

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

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

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

[0292] - Duplicate detection

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

[0294] - RLC SDU discard function

[0295] RLC re-establishment function

[0296] The in-sequence delivery function of the above NR RLC refers to the function of delivering RLC SDUs received from a lower layer to an upper layer in order. The in-sequence delivery function of the above NR RLC 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 lost RLC PDUs by rearranging the order, a function of reporting the status of lost RLC PDUs to the transmitting side, and a function of requesting retransmission of lost RLC PDUs. The in-sequence delivery function of the above NR RLC 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 they are received (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.

[0297] The out-of-sequence delivery function of the above NR RLC refers to a function that delivers RLC SDUs received from a lower layer directly to an upper layer regardless of order. It may include a function to reassemble and deliver the RLC SDUs when the original RLC SDU is divided into multiple RLC SDUs and received, and may include a function to store the RLC SN or PDCP SN of the received RLC PDUs and record the lost RLC PDUs by sorting their order.

[0298] The above 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 some of the following functions.

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

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

[0301] - Scheduling information reporting function

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

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

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

[0305] - MBMS service identification function

[0306] - Transport format selection function

[0307] - Padding

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

[0309] The above wireless protocol structure may vary in its detailed structure 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, as shown in reference number 1410 in Fig. 14. 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 but multiplexes the PHY layer through the MAC layer, as shown in reference number 1420. 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 use a protocol structure that has a single structure up to the RLC but multiplexes the PHY layer through the MAC layer, as shown in reference number 1430.

[0310] Referring to the descriptions regarding PDCCH and beam settings described above, PDCCH repeated transmission is not currently supported in Rel-15 and Rel-16 NR, making it difficult to achieve the required reliability in scenarios requiring high reliability, such as URLLC. The present disclosure provides a method for PDCCH repeated transmission through multiple transmission points (TRPs) to improve the PDCCH reception reliability of a terminal. Specific methods are described in detail in the following examples.

[0311] The contents of this disclosure are applicable to at least one of FDD and TDD systems. Hereinafter, upper signaling (or upper layer signaling) in this disclosure 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).

[0312] 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 will be referred to as the NC-JT (non-coherent joint transmission) case.

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

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

[0315] [Regarding NC-JT]

[0316] 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 transmission and reception points (TRPs).

[0317] 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 densities. In a wireless communication network comprising multiple cells, TRPs, 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.

[0318] Joint Transmission (JT) is a representative transmission technology for the aforementioned cooperative communication 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, and / or beam and the terminal may differ significantly. In particular, in the case of Non-Coherent Joint Transmission (NC-JT) that supports non-coherent precoding between each cell, TRP, and / or beam, individual precoding, MCS, resource allocation, TCI instructions, etc., may be required depending on the link-specific channel characteristics between each cell, TRP, and / or beam and the terminal.

[0319] The aforementioned NC-JT transmission may be applied to at least one of the downlink data channel (PDSCH), downlink control channel (PDCCH), uplink data channel (PUSCH), and uplink control channel (PUCCH). During PDSCH transmission, transmission information such as precoding, Modulation Coding Scheme (MCS), resource allocation, and Transmission Configuration Indication (TCI) is indicated by DL DCI, and for NC-JT transmission, said transmission information must be indicated independently by cell, TRP, or / and beam. This is a major factor in increasing the payload required for DL ​​DCI transmission, which can have a negative impact on 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.

[0320] FIG. 15 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.

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

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

[0323] In the case of the above C-JT, TRP A (1511) and TRP B (1513) transmit a single data (PDSCH) to the terminal (1515), and joint precoding can be performed in multiple TRPs. This may mean that DMRS is transmitted through the same DMRS ports for TRP A (1511) and TRP B (1513) to transmit the same PDSCH. For example, TRP A (1511) and TRP B (1513) each can transmit DRMS ​​to the terminal through DMRS port A and DMRS port 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 port B.

[0324] Also, FIG. 15 shows an example (1520) of non-coherent joint transmission (NC-JT) that supports non-coherent precoding between each cell, TRP or / and beam for PDSCH transmission.

[0325] In the case of the above NC-JT, a PDSCH is transmitted to the terminal (1525) for each cell, TRP or / and beam, and individual precoding may be applied to each PDSCH. This may mean that DMRS is transmitted through different DMRS ports for TRP A (1521) and TRP B (1523) to transmit different PDSCHs. For example, TRP A (1521) may transmit DRMS ​​to the terminal through DMRS port A, and TRP B (1523) may transmit DRMS ​​to the terminal through DMRS port B. The terminal may receive DCI information for receiving each PDSCH that is demodulated based on the DMRS transmitted through DMRS port A and DMRS port B, respectively. Each cell, TRP or / and beam transmits a different PDSCH or a different PDSCH layer to the terminal, thereby improving the throughput compared to single cell, TRP or / and beam transmission. In addition, each cell, TRP, or / and beam can repeatedly transmit the same PDSCH to the terminal to improve reliability compared to single cell, TRP, or / and beam transmission. For convenience of explanation, the cell, TRP, or / and beam will be collectively referred to as TRP below.

[0326] In addition, various wireless resource allocations may be considered in the embodiment of FIG. 15, such as when the frequency and time resources used by multiple TRPs for PDSCH transmission are all the same (1530), when the frequency and time resources used by multiple TRPs do not overlap at all (1540), or when some of the frequency and time resources used by multiple TRPs overlap (1550).

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

[0328] FIG. 16 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.

[0329] Referring to FIG. 16, case #1 (1610) is 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. That is, the terminal can 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 (1610), the degrees of freedom for each PDSCH control or allocation can be fully guaranteed, but when each DCI is transmitted from different TRPs, coverage differences per DCI may occur, which may degrade reception performance.

[0330] Case #2 (1620) shows an example 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 (sDCI#0 to sDCI#(N-2)) is dependent on the control information (DCI#0) for the PDSCH transmitted from the serving TRP.

[0331] 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 is possible to include reserved bits compared to nDCI.

[0332] In the aforementioned case #2 (1620), the degree of freedom for each PDSCH control or allocation may be limited depending on the content of the information element included in the sDCI, but since the receiving performance of the sDCI is superior to that of the nDCI, the probability of a difference in coverage between DCIs may be reduced.

[0333] In FIG. 16, case #3 (1630) illustrates an example 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 (sDCI) for the PDSCHs of the (N-1) additional TRPs is transmitted, and this DCI is dependent on the control information (DCI) for the PDSCH transmitted from the serving TRP.

[0334] For example, DCI#0, which is control information for a PDSCH transmitted from a serving TRP (TRP#0), includes all information elements of DCI format 1_0, DCI format 1_1, 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, the sDCI may include at least one piece of HARQ-related information such as frequency domain resource assignment, time domain resource assignment, and MCS of 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.

[0335] In FIG. 16, case #3 (1630) may have limited freedom for each PDSCH control or allocation depending on the content of the information element included in the sDCI, but the reception performance of the sDCI can be adjusted, and the complexity of the terminal's DCI blind decoding can be reduced compared to case #1 (1610) or case #2 (1620).

[0336] In FIG. 16, case #4 (1640) is 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 in the same DCI (Long DCI) as the control information for the PDSCH transmitted from the serving TRP. That is, the terminal can obtain control information for the PDSCHs transmitted from different TRPs (TRP#0 to TRP#(N-1)) through a single DCI. In the case of case #4 (1640), 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.

[0337] 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.

[0338] In the following description and embodiments, the aforementioned cases #1 (1610), #2 (1620), and #3 (1630), in which one or more DCIs (PDCCHs) are used to support NC-JT, may be classified as multiple PDCCH-based NC-JT, and the aforementioned case #4 (1640), 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 PDCCHs, 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, 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. In this case, the connection relationship between a layer and the TRP transmitting that layer can be indicated through a TCI (Transmission Configuration Indicator) indication for the layer.

[0339] 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.

[0340] 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,” 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.

[0341] 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 reference number 1420 in FIG. 14 (CA-like method) is possible. On the other hand, when the backhaul delay between cooperative TRPs is large enough to be non-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, similar to reference number 1430 in FIG. 14, to ensure robustness against delay (DC-like method) is possible.

[0342] A terminal supporting the above-mentioned C-JT / NC-JT can receive C-JT / NC-JT related parameters or setting values ​​from the upper layer configuration and set the terminal's RRC parameters based on this. For the upper layer configuration, the terminal may utilize, for example, tci-StatePDSCH as a UE capability parameter. The above-mentioned tci-StatePDSCH can define TCI states for the purpose of PDSCH transmission, and the number of TCI states can be set to 4, 8, 16, 32, 64, or 128 in FR1, and to 64 or 128 in FR2. Among the set number, a maximum of 8 states can be set, which can be indicated by the 3 bits of the TCI field of the DCI via a MAC CE message. The above-mentioned maximum value of 128 refers 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.

[0343] [Multi-DCI-based Multi-TRP]

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

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

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

[0347] * 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.

[0348] * 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 can be considered to be transmitted through the same TRP, or a PDCCH scheduling a PDSCH of the same TRP within that CORESET can be considered to be transmitted.

[0349] * 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 PDSCH is being transmitted in that search space.

[0350] 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, which enables the generation of independent HARQ-ACK codebooks and the use of independent PUCCH resources for each TRP.

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

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

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

[0354] In Single PDCCH-based NC-JT, a single DCI can schedule PDSCHs 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 in 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 in 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 in 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.

[0355] The above-described settings 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, it can be assumed that NC-JT transmission is configured in the PCell, whereas NC-JT transmission is not configured in the aforementioned SCell.

[0356] Referring to the descriptions regarding PDCCH and beam configuration 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. The present disclosure provides a method for PDCCH repeated transmission through multiple transmission points (TRPs) to improve the PDCCH reception reliability of a terminal. The specific method is described in detail in the following examples.

[0357] For convenience in the following description of the present disclosure, cells, transmission points, panels, beams, and / or transmission directions that can be distinguished through upper-level / L1 parameters such as TCI state or spatial relation information, or indicators such as cell ID, TRP ID, and panel ID, are uniformly referred to as TRP (transmission reception point). Therefore, in actual application, TRP can be appropriately replaced with one of the above terms.

[0358] 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 will be referred to as the NC-JT case.

[0359] In describing the present disclosure below, the term "upper layer signaling" may refer to a signaling corresponding to at least one or a combination of at least one of the following signalings.

[0360] - MIB (Master Information Block)

[0361] - SIB (System Information Block) or SIB

[0362] - RRC (Radio Resource Control)

[0363] - MAC (Medium Access Control) CE (Control Element)

[0364] In addition, L1 signaling may be a signaling corresponding to at least one or a combination of at least one of the following physical layer channels or signaling methods using signaling.

[0365] - PDCCH (Physical Downlink Control Channel)

[0366] - DCI (Downlink Control Information)

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

[0368] - Group common DCI

[0369] - Common DCI

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

[0371] - Non-scheduling DCI (e.g., DCI not intended for scheduling downlink or uplink data)

[0372] - PUCCH (Physical Uplink Control Channel)

[0373] - UCI (Uplink Control Information)

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

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

[0376] <1st Embodiment: Multiple TRP-based PDCCH Iterative Transmission Method>

[0377] In one embodiment of the present disclosure, the maximum number of PDCCH candidates and the number of CCEs are limited according to a PDCCH iterative transmission method considering multiple TRPs. There may be various methods for PDCCH iterative transmission considering multiple TRPs depending on how each TCI state to be applied when transmitting a PDCCH at each TRP is applied to the various parameters mentioned above used for PDCCH transmission. For example, various parameters used for PDCCH transmission to apply different TCI states may include CCEs, PDCCH candidates, control resource sets, and search spaces. When PDCCH iterative transmission considering multiple TRPs is performed, soft combining and selection methods may be considered for the terminal's reception method.

[0378] There may be the following four methods for repeated PDCCH transmission through multiple TRPs, and the base station may set at least one of the four methods to the terminal through upper layer signaling, instruct through L1 signaling, or set and instruct through a combination of upper layer signaling and L1 signaling.

[0379] [Method 1] Multiple PDCCH repeated transmission methods with the same payload

[0380] Method 1 is a method of repeatedly transmitting multiple control information having the same DCI format and payload. Each of the aforementioned control information may indicate information for scheduling the repeatedly transmitted PDSCH, for example, {PDSCH#1, PDSCH#2, ..., PDSCH#Y} that is repeatedly transmitted over multiple slots. The fact that the payload of each repeatedly transmitted control information is the same can be expressed as meaning that the PDSCH scheduling information of each control information, for example, the number of PDSCH repeated transmissions, time-axis PDSCH resource allocation information (i.e., slot offset (K_0) and number of PDSCH symbols between the control information and PDSCH#1), frequency-axis PDSCH resource allocation information, DMRS port allocation information, PDSCH-to-HARQ-ACK timing, PUCCH resource indicator, etc., are all identical. The terminal can improve the reception reliability of the control information by soft combining the repeatedly transmitted control information having the same payload.

[0381] For the aforementioned soft combine, the terminal needs to know in advance the resource location and the number of repeated transmissions of the control information to be repeatedly transmitted. To this end, the base station may pre-instruct the resource configuration of the time domain, frequency domain, and spatial domain of the aforementioned repeated transmission control information. When control information is repeatedly transmitted in the time domain, the control information may be repeatedly transmitted across different CORESETs, repeatedly transmitted across different search space sets within a single CORESET, or repeatedly transmitted across different PDCCH monitoring occasions within a single CORESET and a single search space set. The unit of the resource being repeatedly transmitted in the time domain (CORESET unit, search space set unit, PDCCH monitoring occasion unit) and the location of the repeated transmission resource (PDCCH candidate index, etc.) may be indicated through the base station's upper layer settings. In this case, the number of repeated transmissions of the PDCCH and / or the list and transmission pattern of TRPs participating in the repeated transmission may be explicitly indicated, and upper layer instructions or MAC-CE / L1 signaling may be used as methods for explicit indication. In this case, the list of TRPs can be indicated in the form of a TCI state or the aforementioned QCL assumption.

[0382] When control information is repeatedly transmitted along the frequency axis, the control information may be repeatedly transmitted across different CORESETs, across different PDCCH candidates within a single CORESET, or repeatedly transmitted per CCE. The unit of the resource being repeatedly transmitted along the frequency axis and the location of the repeated transmission resource may be specified through the base station's upper layer settings, etc. Additionally, the number of repeated transmissions and / or the list of TRPs participating in the repeated transmission and the transmission pattern may be explicitly specified; methods such as upper layer indication or MAC-CE / L1 signaling may be used for explicit indication. In this case, the list of TRPs may be specified in the form of a TCI state or the aforementioned QCL assumption.

[0383] When control information is repeatedly transmitted along the spatial axis, the control information may be repeatedly transmitted across different CORESETs, or repeated transmission may occur by setting two or more TCI states in a single CORESET.

[0384] [Method 2] Method for repeatedly transmitting multiple control information that may differ in DCI format and / or payload

[0385] Method 2 is a method of repeatedly transmitting multiple control information that may differ in DCI format and / or payload. These control information schedules repeated PDSCH transmissions, and the number of repeated PDSCH transmissions indicated by each control information may differ. For example, PDCCH#1 indicates information for scheduling {PDSCH#1, PDSCH#2, ..., PDSCH#Y}, while PDCCH#2 indicates information for scheduling {PDSCH#2, ..., PDSCH#Y}, and ..., PDCCH#X may indicate information for scheduling {PDSCH Y}. This method of repeatedly transmitting control information has the advantage of reducing the total delay time required for repeated transmission of control information and PDSCH compared to Method 1. On the other hand, since the payloads of each repeatedly transmitted control information may differ, soft combine of the repeatedly transmitted control information is not possible, so the reliability may be lower compared to Method 1.

[0386] In the above-described method 2, the terminal may not need to know in advance the resource location and number of repeated transmissions of the control information to be repeatedly transmitted, and the terminal may independently decode and process each of the repeatedly transmitted control information. If the terminal decodes multiple repeated transmission control information that schedules the same PDSCH, it may process only the first repeated transmission control information and ignore the second and subsequent repeated transmission control information. Alternatively, the resource location and number of repeated transmissions of the control information to be repeatedly transmitted may be indicated in advance, and the method of indication may be the same as the method described in the above-described method 1.

[0387] [Method 3] Method for repeatedly transmitting multiple control information, each of which may have different DCI formats and / or payloads.

[0388] Method 3 is a method of repeatedly transmitting multiple control information, each of which may have different DCI formats and / or payloads. In this case, each control information transmitted repeatedly has the same DCI format and payload. Since multiple control information in Method 2 above cannot be soft-combined, the reliability may be lower compared to Method 1 above, and the total delay time required for the repeated transmission of control information and PDSCH in Method 1 above may be longer. Method 3 above is a method that utilizes the advantages of Method 1 and Method 2 above, and can transmit control information with higher reliability compared to Method 2 while reducing the total delay time required for the repeated transmission of control information and PDSCH above compared to Method 1.

[0389] In the above method 3, the soft combine of method 1 and the individual decoding of method 2 may be used to decode and soft combine the repeatedly transmitted control information. For example, among the repeated transmissions of multiple control information, each having a different DCI format and / or payload, the first transmitted control information may be decoded as in method 2, and the repeated transmissions of the decoded control information may be soft combined as in method 1.

[0390] Meanwhile, the base station may select and configure one of the above-described methods 1, 2, or 3 for the repeated transmission of control information. The method of repeated transmission of control information may be explicitly instructed by the base station to the terminal through upper-layer signaling. Alternatively, the method of repeated transmission of control information may be instructed in combination with other configuration information. For example, an upper-layer configuration instructing the PDSCH repeated transmission method may be combined with the instruction for repeated transmission of control information. If PDSCH is instructed to be repeatedly transmitted in the FDM method, it may be interpreted that the control information is repeatedly transmitted only via the above-described method 1, because the repeated transmission of PDSCH in the FDM method does not have the delay time reduction effect of the above-described method 2. For similar reasons, if PDSCH is instructed to be repeatedly transmitted in the intra-slot TDM method, it may be interpreted that the control information is repeatedly transmitted via the above-described method 1. On the other hand, if PDSCH is instructed to be repeatedly transmitted in the inter-slot TDM method, the above-described method 1, method 2, or 3 for the repeated transmission of control information may be selected through upper-layer signaling or L1 signaling.

[0391] Meanwhile, through settings such as upper layers, the base station may explicitly instruct the terminal on the control information repetitive transmission unit. Alternatively, the control information repetitive transmission unit may be instructed in combination with other setting information. For example, an upper layer setting that instructs the PDSCH repetitive transmission method may be combined with the control information repetitive transmission unit. If PDSCH is instructed to be repetitively transmitted in the FDM method, it can be interpreted that the control information is repetitively transmitted via FDM or SDM, because if the control information is repetitively transmitted in a manner such as inter-slot TDM, there is no latency reduction effect resulting from the FDM method of PDSCH repetitive transmission. For similar reasons, if PDSCH is instructed to be repetitively transmitted in the intra-slot TDM method, it can be interpreted that the control information is repetitively transmitted via intra-slot TDM, FDM, or SDM. On the other hand, if PDSCH is instructed to be repetitively transmitted in the inter-slot TDM method, upper layer signaling, etc., may be selected so that the control information can be repetitively transmitted via inter-slot TDM, intra-slot TDM, FDM, or SDM.

[0392] [Method 4] PDCCH transmission method applying multiple TCI states

[0393] Method 4 can transmit by applying different TCI states, signifying transmission from multiple TRPs, to different CCEs within a PDCCH candidate group to improve PDCCH reception performance without PDCCH repetitive transmission. Although this method is not PDCCH repetitive transmission, since it transmits different CCEs within the PDCCH candidate group by applying different TCI states from each TRP, it can serve as a method to acquire spatial diversity within the PDCCH candidate group. Different CCEs to which different TCI states are applied can be separated by time or frequency dimensions, and the terminal needs to know in advance the resource locations to which different TCI states are applied. The terminal can receive different CCEs with different TCI states applied within different PDCCHs and decode them independently or all at once.

[0394] <Second Embodiment: Limiting the Maximum Number of PDCCH Candidates and CCEs According to the PDCCH Repeated Transmission Method>

[0395] The terminal may individually report as a terminal capability whether it supports a method among the above-described methods 1 to 4 for the PDCCH iterative transmission of the base station. The terminal may report as a terminal capability whether it supports soft combining for the terminal reception method for the PDCCH iterative transmission. Additionally, the terminal may report as a terminal capability regarding the limit on the maximum number of PDCCH candidates and the maximum number of CCEs for the PDCCH iterative transmission. The terminal capability may be a limit per individual slot, a limit per multiple slots, a limit per individual span, or a limit per multiple spans. Furthermore, the terminal may report as a terminal capability the counting method for the PDCCH candidates and the number of CCEs for a method among the above-described four PDCCH iterative transmission methods that is supported.

[0396] Depending on the above terminal capability report and base station transmission conditions, the counting method for the PDCCH candidate group and the number of CCEs may vary.

[0397] FIG. 17 is a diagram illustrating the operation of a terminal regarding the number of PDCCH candidate groups and the number of CCEs according to the terminal capability report and whether the base station transmission conditions are satisfied during repeated PDCCH transmission according to one embodiment of the present disclosure.

[0398] Referring to FIG. 17, the terminal reports its terminal capability related to PDCCH repetitive transmission to the base station (1701). At this time, the possible terminal capability report may include information on at least one of the PDCCH repetitive transmission methods supported by the terminal (e.g., one of [Method 1] to [Method 4] above), whether soft combining is supported for PDCCH repetitive transmission, a method for counting PDCCH candidates and CCEs, the maximum number of PDCCH candidates and CCEs per individual slot / multiple slot and individual span / multiple slot, and the overbooking method described above. In another embodiment, if the information regarding the terminal capability is pre-set for the terminal, the operation of step 1701 may be omitted. Additionally, if the information regarding the terminal capability is applied identically as default information for a defined group of terminals, step 1701 may be omitted.

[0399] Subsequently, the terminal receives first configuration information for the PDCCH from the base station (1703) and may additionally receive second configuration information for the PDCCH repeated transmission (1704). At this time, the second configuration information may include at least one of the following: a repeated transmission method, the number of repeated transmissions, a repeated transmission interval, a repeated transmission period, a PDCCH monitoring occasion where repeated transmission is assumed, and whether a connection between repeated transmissions can be verified. Additionally, the terminal may receive at least a portion of the first and second configuration information via L1 signaling or implicitly determine at least a portion based on other configuration information. Furthermore, the first and second configuration information may be provided as a single configuration information.

[0400] A terminal that receives the above-mentioned configuration information checks the number of repeated transmissions (N, an integer such that N≥1) if the number of repeated transmissions is greater than 1, and if the number of repeated transmissions is greater than 1, the terminal checks whether the transmission conditions of the base station are satisfied (1707). The transmission conditions may be a combination of at least one of [Condition 1] to [Condition 4] described later. If the transmission conditions are not satisfied, the terminal operates using the existing method for counting the number of PDCCH candidates and CCEs (the second method for counting the number of PDCCH candidates and CCEs) (1711). If the transmission conditions are not satisfied, the terminal operates by applying a new standard (the first method for counting the number of PDCCH candidates and CCEs) to the counting of the number of PDCCH candidates and CCEs (1709). When counting the number of PDCCH candidates and CCEs by applying the operation of applying the new standard, one of the following [Operation 1] to [Operation 3] may be applied when the number of repeated PDCCH transmissions is N. Meanwhile, if the number of repeated transmissions in step 1705 is not greater than 1 (i.e., the number of repeated transmissions is 1), proceed to step 1711, and the terminal operates using the existing PDCCH candidate count and CCE count method (second PDCCH candidate count and CCE count method). The number of repeated transmissions being 1 means that repeated transmissions are not performed.

[0401] [Operation 1] Count N repeated transmissions as 1.

[0402] Even if the terminal receives N repeated PDCCH transmissions according to the terminal's capabilities, it can count the number of PDCCH candidates and CCEs by considering all N repeated transmissions as one. For example, when there are 2 repeated transmissions, the 2 repeated PDCCHs can be counted by considering them as one.

[0403] [Operation 2] Existing counting method

[0404] For PDCCH candidates that are transmitted N times repeatedly, the terminal can count the number of PDCCH candidates or CCEs N times compared to the existing counting method, assuming that individual decoding is performed without, for example, soft combining. For example, when there are 2 repeated transmissions, it can be counted as 2, just as when counting the number of PDCCH candidates or CCEs for the transmission of 2 different PDCCHs.

[0405] [Action 3] 2 N Count to -1

[0406] Assuming that the terminal counts once whenever it performs soft combining for at least one combination of PDCCH candidates transmitted N times repeatedly, 2 during N repeated transmissions N It can be counted as -1. For example, if a terminal receives two repeated PDCCH transmissions from a base station, the first and second transmissions are counted individually, and assuming soft combining of the first and second transmissions, one additional count is added, resulting in a total of 2 2 -1 can be counted as 3 times.

[0407] At this time, the items that can be considered as conditions for counting the number of PDCCH candidates and CCEs by applying the operation of applying new criteria as described above can be a combination of at least one of the following [Condition 1] to [Condition 4].

[0408] [Condition 1] Whether soft combining is supported

[0409] The terminal may perform different counting of the number of PDCCH candidates or the number of CCEs depending on whether soft combining is supported, which is transmitted to the base station through a capability report. For example, if the terminal can support soft combining based on PDCCH iterative transmission, the terminal may count the number of PDCCH candidates and the number of CCEs by selecting one of the above-described operations 1 to 3. Additionally, if the terminal receives a PDCCH iterative transmission setting or instruction from the base station that enables soft combining (e.g., the same DMRS location based on the same scrambling sequence, the same PDCCH candidate location based on the same hash function result, etc.), the terminal may count the number of PDCCH candidates and the number of CCEs by selecting one of the above-described operations 1 to 3.

[0410] [Condition 2] Existence within the same / different control resource set

[0411] The terminal may perform different operations for counting the number of PDCCH candidates and the number of CCEs depending on whether the PDCCH repeatedly transmitted from the base station exists in the same control resource set or in a different control resource set.

[0412] [Condition 3] PDCCH Repeated Transmission Method

[0413] The terminal may perform different operations for counting the number of PDCCH candidates and CCEs according to the four PDCCH repetitive transmission methods (methods 1 to 4) described above. When the PDCCH repetitive transmission methods of method 1 and method 3, which enable soft combining, are set and instructed to the terminal by the base station, and when counting the number of PDCCH candidates and CCEs for the repetitive transmission method of method 4 described above, that is, the PDCCH transmission method considering non-repetitive based multiple TRPs, the terminal may apply the new criteria described above (first PDCCH candidate count and CCE count method) to the operation for counting the number of PDCCH candidates and CCEs.

[0414] [Condition 4] Number of applied TCI states, or whether identical / different TCI states are applied

[0415] The terminal may perform different counting operations for the PDCCH candidate group and the number of CCEs depending on the number of TCI states applied to the PDCCH transmitted from the base station, or whether the same or different TCI states are applied.

[0416] <Third Embodiment: Overbooking Method According to PDCCH Repeated Transmission Method>

[0417] Depending on the above terminal capability report and base station transmission conditions, the counting method for the PDCCH candidate group and the number of CCEs may vary.

[0418] FIG. 18 is a diagram illustrating the operation of a terminal regarding the number of PDCCH candidate groups and the number of CCEs according to the terminal capability report and whether the base station transmission conditions are satisfied during repeated PDCCH transmission according to one embodiment of the present disclosure.

[0419] Referring to FIG. 18, the terminal reports its terminal capability related to PDCCH repetitive transmission to the base station (1801. At this time, the possible terminal capability report may include information on at least one of the PDCCH repetitive transmission methods supported by the terminal (e.g., one of [Method 1] to [Method 4] above), whether soft combining is supported for PDCCH repetitive transmission, a method for counting PDCCH candidates and CCEs, the maximum number of PDCCH candidates and CCEs per individual slot / multiple slot and individual span / multiple slot, and the overbooking method described above. In another embodiment, if the information regarding the terminal capability is pre-set for the terminal, the operation of step 1701 may be omitted. Additionally, if the information regarding the terminal capability is applied identically as default information for a defined group of terminals, step 1801 may be omitted.

[0420] Subsequently, the terminal receives first configuration information for the PDCCH from the base station (1803) and may additionally receive second configuration information for the PDCCH repeated transmission (1805). At this time, the second configuration information may include at least one of the following: a repeated transmission method, the number of repeated transmissions, a repeated transmission interval, a repeated transmission period, a PDCCH monitoring occasion where repeated transmission is assumed, and whether a connection between repeated transmissions can be verified. Additionally, the terminal may receive at least a portion of the first and second configuration information via L1 signaling or implicitly determine at least a portion based on other configuration information. Furthermore, the first and second configuration information may be provided as a single configuration information.

[0421] A terminal that receives the above-mentioned configuration information checks the number of repeated transmissions (N, an integer such that N≥1) if the number of repeated transmissions is greater than 1, and if the number of repeated transmissions is greater than 1, the terminal checks whether the transmission conditions of the base station are satisfied (1809). The transmission conditions may be a combination of at least one of [Condition 1] to [Condition 4] above. If the transmission conditions are not satisfied, the terminal operates using the existing overbooking method (second overbooking method) (1813), and if the transmission conditions are not satisfied, the terminal operates by applying a new standard (first overbooking method) to the overbooking method (1811). When performing the overbooking method by applying the new standard, when the number of repeated PDCCH transmissions is N, one of the following [Operation 4] and [Operation 5] may be applied. Meanwhile, if the number of repeated transmissions in step 1807 is not greater than 1 (i.e., the number of repeated transmissions is 1), proceed to step 1813, and the terminal operates using the existing overbooking method (second overbooking method). The number of repeated transmissions being 1 means that repeated transmissions are not performed.

[0422] [Operation 4] Reuse existing overbooking method

[0423] If the terminal exceeds the limits on the maximum number of PDCCH candidates and CCEs at that time, it may monitor only a subset of the configured search space sets to satisfy the limits on the maximum number of PDCCH candidates and CCEs, and the base station may transmit the PDCCH to the selected search space set. The terminal may perform overbooking in the conventional manner even if repeated PDCCH transmissions occur within a specific search space set or across multiple search space sets. That is, among the search space sets existing at that time, the terminal may prioritize selecting a search space set configured as a common search space over a search space set configured as a terminal-specific search space. If all search space sets configured as common search spaces have been selected (i.e., if the limits on the maximum number of PDCCH candidates and CCEs are satisfied even after selecting all search spaces configured as common search spaces), the terminal (or the base station) may select the search space sets configured as terminal-specific search spaces. In this case, if there are multiple search space sets configured as terminal-specific search spaces, the search space set with a lower search space set index may have a higher priority. Considering the priority, terminal-specific search space sets can be selected within a range that satisfies the limits on the maximum number of PDCCH candidates and CCEs.

[0424] [Action 5] Select some PDCCHs within the search space set

[0425] When a terminal determines whether to select a specific search space set considering that it is a recurrence transmission if the search space set is not selected by the existing method, the terminal may select only some of the recurrence transmissions and not select the remaining recurrence transmissions within the range satisfying the limits on the maximum number of PDCCH candidates and the number of CCEs. In this case, the criteria for selecting some of the PDCCH recurrence transmissions may be to prioritize recurrence transmissions with different TCI states applied, or to prioritize recurrence transmissions transmitted from different control resource sets.

[0426] At this time, the items that can be considered as conditions for performing an overbooking method by applying a new standard may be a combination of at least one of [Condition 1] to [Condition 4] of the second embodiment.

[0427] According to the embodiments of the present disclosure described above, as downlink control information is repeated, the maximum number of blind decodings and the maximum number of CCEs that a terminal must consider can be determined. For example, the terminal may receive different candidates of a downlink control channel using a soft combining method, and in this case, the terminal may group candidates capable of soft combining and count them as one blind decoding count. As another example, the terminal may receive different candidates of a downlink control channel using an optional decoding method, and in this case, if the terminal is explicitly instructed to receive connection information for candidates capable of optional decoding, it may count the candidates as one blind decoding count, and if the terminal is implicitly instructed to receive connection information for candidates capable of optional decoding or is unaware of it, it may count individual blind decoding counts for the candidates. In addition to receiving methods such as soft combining or selective decoding, the embodiments of the present disclosure may provide various methods for limiting and counting the maximum number of blind decodings and the maximum number of CCEs depending on the resource usage method of repetitive transmission and reception, the beam setting used for repetitive transmission and reception, the setting of the search space and control resource area, the aggregation level, etc.

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

[0429] Referring to FIG. 19, the terminal may include a transceiver comprising a receiver (1901) and a transmitter (1903), a memory (not shown), and a processor (1905). The processor (1905) may be at least one processor and may be referred to as a controller or a control unit. The processor (1905) may control the entire device of the terminal so that the terminal operates according to each of the embodiments of the present disclosure described above, as well as a combination of at least one embodiment. However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more or fewer components than the components described above. Furthermore, the transceiver, memory, and processor may be implemented in the form of at least one chip.

[0430] The above-described transceiver can transmit and receive signals with a base station. Here, the signal may include control information and data. To this end, the above-described 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 above-described transceiver, and the components of the above-described transceiver are not limited to an RF transmitter and an RF receiver.

[0431] In addition, the transceiver can receive a signal through a wireless channel and output it to the processor (1905), and transmit the signal output from the processor (1905) through the wireless channel.

[0432] The memory can store programs and data necessary for the operation of the terminal. In addition, the memory can 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, RAM, hard disk, CD-ROM, and DVD. In addition, there may be multiple memories.

[0433] Additionally, the processor (1905) can control a series of processes to enable the terminal to operate according to the above-described embodiment. For example, the processor (1905) can control the components of the terminal to receive a DCI composed of two layers and receive a plurality of PDSCHs simultaneously. The processor (1905) may be multiple, and the processor (1905) can perform control operations on the component(s) of the terminal by executing a program stored in memory.

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

[0435] Referring to FIG. 20, a base station may include a transceiver comprising a receiver (2001) and a transmitter (2003), a memory (not shown), and a processor (2005). The base station may include a communication interface (not shown) for wired or wireless communication with another base station via a backhaul link. The processor (2005) may be at least one processor and may be referred to as a controller or a control unit. The processor (2005) may control the entire device of the base station so that the base station operates according to each of the embodiments of the above disclosure as well as a combination of at least one embodiment. However, the components of the base station are not limited to the examples described above. For example, the base station may include more or fewer components than the components described above. Furthermore, the transceiver, memory, and processor may be implemented in the form of at least one chip.

[0436] The above-described transceiver can transmit and receive signals with a terminal. Here, the signal may include control information and data. To this end, the above-described 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 above-described transceiver, and the components of the above-described transceiver are not limited to an RF transmitter and an RF receiver.

[0437] In addition, the transceiver can receive a signal through a wireless channel and output it to the processor (2005), and transmit the signal output from the processor (2005) through the wireless channel.

[0438] The memory can store programs and data necessary for the operation of the base station. In addition, 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, hard disk, CD-ROM, and DVD. In addition, there may be multiple memories.

[0439] The processor (2005) can control a series of processes to enable the base station to operate according to the embodiments of the present disclosure described above. For example, the processor (2005) 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. The processor (2005) may be a plurality of times, and the processor (2005) can perform control operations on the component(s) of the base station by executing a program stored in memory.

[0440] 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.

[0441] 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.

[0442] 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.

[0443] 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.

[0444] 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.

[0445] 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.

[0446] 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.

[0447] Alternatively, 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 disclosure is not impaired.

[0448] 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.

[0449] 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 their equivalents should be interpreted as being included within the scope of the present disclosure.

Claims

Claim 1 A method performed by a terminal in a wireless communication system, comprising: transmitting first information related to a multiple transmission-reception-point (TRP) based physical downlink control channel (PDCCH) iteration to a base station; said first information including second information indicating the number of blind decodings for PDCCH candidates; receiving third information regarding a set of control resources and fourth information regarding a search space from said base station; and a method of monitoring PDCCH candidates based on said second information, said third information and said fourth information, wherein said second information indicates the terminal's ability to count two PDCCH candidates as three PDCCH candidates. Claim 2 delete Claim 3 In claim 1, the second information is a method for indicating the number of times the blind decoding is performed for the two PDCCH candidates. Claim 4 delete Claim 5 delete Claim 6 A terminal in a wireless communication system comprises: a transceiver; and, through the transceiver, a first information related to a multiple TRP (transmission-reception-point) based PDCCH (physical downlink control channel) iteration to a base station, wherein the first information includes second information indicating the number of blind decodings for PDCCH candidates; receiving from the base station through the transceiver a third information regarding a set of control resources and a fourth information regarding a search space; and a processor configured to monitor PDCCH candidates based on the second information, the third information and the fourth information, a span which is the number of consecutive symbols in a slot configured for the terminal to monitor PDCCH, wherein the second information indicates the terminal's ability to count two PDCCH candidates as three PDCCH candidates. Claim 7 delete Claim 8 In claim 6, the second information is a terminal indicating the number of times the blind decoding is performed for the two PDCCH candidates. Claim 9 delete Claim 10 delete Claim 11 A method performed by a base station in a wireless communication system, comprising: receiving first information related to a multiple transmission-reception-point (TRP) based physical downlink control channel (PDCCH) iteration from a terminal; the first information including second information indicating the number of blind decodings for PDCCH candidates; transmitting third information regarding a set of control resources and fourth information regarding a search space; and transmitting downlink control information from PDCCH candidates based on the span, which is the number of consecutive symbols in a slot set for the terminal to monitor the PDCCH, the second information, the third information, and the fourth information, wherein the second information indicates the terminal's ability to count two PDCCH candidates as three PDCCH candidates. Claim 12 delete Claim 13 In claim 11, the second information is a method for indicating the number of times the blind decoding is performed on the two PDCCH candidates. Claim 14 delete Claim 15 delete Claim 16 A base station in a wireless communication system comprises: a transceiver; and, through the transceiver, receiving first information related to a multiple TRP (transmission-reception-point) based PDCCH (physical downlink control channel) iteration from a terminal, wherein the first information includes second information indicating the number of blind decodings for PDCCH candidates; transmitting through the transceiver third information regarding a set of control resources and fourth information regarding a search space, and, through the transceiver, a processor configured to transmit downlink control information from PDCCH candidates based on the second information, the third information and the fourth information, wherein the second information indicates the terminal's ability to count two PDCCH candidates as three PDCCH candidates. Claim 17 delete Claim 18 In claim 16, the second information is a base station indicating the number of times the blind decoding is performed for the two PDCCH candidates. Claim 19 delete Claim 20 delete

Citation Information

Patent Citations

  • Method for transmitting or receiving downlink control information in wireless communication system and device therefor

    US20190306847A1