Method and device for receiving pdcch using sub-interleaver in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. A method performed by a terminal in a wireless communication system, according to one embodiment of the present disclosure, comprises the steps of: receiving, from a base station, control resource set (CORESET) configuration information; identifying a first sub-CORESET and a second sub-CORESET on the basis of the CORESET configuration information, wherein the bandwidth of the first sub-CORESET is narrower than the bandwidth of the second sub-CORESET; determining at least one physical downlink control channel (PDCCH) candidate for the first sub-CORESET and the second sub-CORESET; and performing blind decoding on the determined at least one PDCCH candidate.

Description

Method and device for receiving PDCCH using a sub-interleaver in a wireless communication system

[0001] The present disclosure relates to the operation of a terminal and a base station in a wireless communication system or a mobile communication system. Specifically, the present disclosure relates to a method and device for receiving a physical downlink control channel (PDCCH) using a sub-interleaver in a wireless communication system.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz band (for example, the 3 terahertz (3THz) band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.

[0003] In the early stages of 5G mobile communication technology, the goal is to support services and satisfy performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.

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

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

[0006] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.

[0008] The present disclosure seeks to provide a device and method capable of effectively providing a service in a wireless communication system or a mobile communication system.

[0009] According to one aspect of an embodiment of the present disclosure, a method of operating a terminal may include: receiving CORESET (control resource set) configuration information from a base station; identifying a first sub-CORESET and a second sub-CORESET based on the CORESET configuration information, wherein a bandwidth of the first sub-CORESET is narrower than a bandwidth of the second sub-CORESET; determining at least one physical downlink control channel (PDCCH) candidate for the first sub-CORESET and the second sub-CORESET; and performing blind decoding on the determined at least one PDCCH candidate.

[0010] According to one aspect of an embodiment of the present disclosure, a method of operating a base station may include: identifying a first sub CORESET (control resource set) and a second sub CORESET, wherein a bandwidth of the first sub CORESET is narrower than a bandwidth of the second sub CORESET; generating CORESET configuration information based on a result of the identification; transmitting the CORESET configuration information to a terminal; and transmitting at least one physical downlink control channel (PDCCH) to the terminal based on the first sub CORESET and the second sub CORESET.

[0011] According to an aspect of an embodiment of the present disclosure, a terminal comprises: at least one transceiver; at least one processor communicatively connected to the at least one transceiver; and a step of communicatively connected to the at least one processor and executable individually or in any combination of the at least one processor, wherein the terminal receives CORESET (control resource set) configuration information from a base station, and identifies a first sub-CORESET and a second sub-CORESET based on the CORESET configuration information, wherein a bandwidth of the first sub-CORESET is narrower than a bandwidth of the second sub-CORESET, and determines at least one physical downlink control channel (PDCCH) candidate for the first sub-CORESET and the second sub-CORESET, and performs blind decoding on the determined at least one PDCCH candidate.

[0012] According to an aspect of an embodiment of the present disclosure, a base station comprises: at least one transceiver; at least one processor communicatively connected to the at least one transceiver; and a processor communicatively connected to the at least one processor and executable individually or in any combination of the at least one processor, wherein the base station identifies a first sub CORESET (control resource set) and a second sub CORESET, wherein a bandwidth of the first sub CORESET is narrower than a bandwidth of the second sub CORESET, generates CORESET configuration information based on the identification result, transmits the CORESET configuration information to a terminal, and transmits at least one PDCCH (physical downlink control channel) to the terminal based on the first sub CORESET and the second sub CORESET.

[0013] The technical problems to be achieved in various embodiments of the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art to which the present invention pertains from the description below.

[0014] According to one embodiment of the present disclosure, a device and method for effectively providing a service in a wireless communication system or a mobile communication system can be provided.

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

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

[0017] FIG. 3 is a diagram illustrating an example of bandwidth portion settings in a wireless communication system according to an embodiment of the present disclosure.

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

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

[0020] FIG. 6 is a diagram for explaining a method for a base station and a terminal to transmit and receive data by taking into account downlink data channels and rate matching resources according to an embodiment of the present disclosure.

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

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

[0023] FIG. 9 is a diagram illustrating an example of time axis resource allocation according to subcarrier spacing of a data channel and a control channel in a wireless communication system according to an embodiment of the present disclosure.

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

[0025] FIG. 11 is a diagram illustrating an SS / PBCH block, CORESET, and PDSCH according to an embodiment of the present disclosure.

[0026] FIG. 12 is a diagram illustrating a wideband CORESET set according to an embodiment of the present disclosure.

[0027] FIG. 13 is a diagram illustrating a wideband CORESET set according to an embodiment of the present disclosure.

[0028] FIG. 14 is a diagram illustrating a wideband CORESET set according to an embodiment of the present disclosure.

[0029] FIG. 15 is a diagram illustrating a sub-CORESET set according to an embodiment of the present disclosure.

[0030] FIG. 16 is a diagram illustrating an interleaver setting corresponding to a sub-CORESET according to an embodiment of the present disclosure.

[0031] Figure 17 is a flowchart illustrating the operation of a terminal according to the present disclosure.

[0032] FIG. 18 is a diagram illustrating PDCCH candidate monitoring corresponding to a sub-CORESET according to an embodiment of the present disclosure.

[0033] FIG. 19 is a diagram illustrating the structure of a terminal in a wireless communication system according to an embodiment of the present disclosure.

[0034] FIG. 20 is a diagram illustrating the structure of a base station in a wireless communication system according to an embodiment of the present disclosure.

[0035] To meet the increasing demand for wireless data traffic since the commercialization of 4G communication systems, efforts are being made to develop improved 5G communication systems, or pre-5G communication systems. For this reason, 5G communication systems, or pre-5G communication systems, are also called beyond 4G networks or post-LTE systems. To achieve high data rates, 5G communication systems are being considered for implementation in ultra-high frequency (mmWave) bands (e.g., 60 GHz bands). To mitigate radio path loss and increase the transmission range of radio waves in ultra-high frequency bands, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large-scale antenna technologies are being discussed in 5G communication systems. In addition, to improve the network of the system, technologies such as evolved small cells, advanced small cells, cloud radio access networks (cloud RAN), ultra-dense networks, device-to-device communication (D2D), wireless backhaul, moving networks, cooperative communication, CoMP (Coordinated Multi-Points), and interference cancellation are being developed 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.

[0036] Meanwhile, the Internet is evolving from a human-centric network where humans create and consume information to an Internet of Things (IoT) network where information is exchanged and processed between distributed components, such as objects. The Internet of Everything (IoE) is also emerging, combining IoT technologies with big data processing technologies, such as those connected to cloud servers. To implement the IoT, technological elements such as sensing technologies, wireless and wired communication and network infrastructure, service interface technologies, and security technologies are required. Recently, research is being conducted on technologies such as sensor networks, Machine-to-Machine (M2M), and Machine-Type Communication (MTC) for connecting objects. In the IoT environment, intelligent IT (Internet Technology) services can be provided that collect and analyze data generated from connected objects to create new value for human life. IoT can be applied to areas such as smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart appliances, and advanced medical services through the convergence and integration of existing IT (information technology) technologies with various industries.

[0037] Accordingly, various attempts are being made to apply 5G communication systems (also known as 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), a big data processing technology described above, can also be considered an example of the convergence of 3eG and IoT technologies.

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

[0039] In describing the embodiments, descriptions of technical details that are well known in the technical field to which the present disclosure pertains and are not directly related to the present disclosure will be omitted. This is to convey the gist of the present disclosure more clearly without obscuring it by omitting unnecessary explanations.

[0040] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference numbers.

[0041] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided only to ensure that the disclosure of the present 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. Like reference numerals designate like elements throughout the specification. In addition, when describing the present disclosure, if a specific description of a related function or configuration is determined to unnecessarily obscure the gist of the present disclosure, a detailed description thereof will be omitted. In addition, the terms described below are terms defined in consideration of the functions of the present disclosure, and may vary depending on the intention or custom of the user or operator. Therefore, their definitions should be made based on the contents throughout the specification.

[0042] Hereinafter, the base station is an entity that performs resource allocation of a terminal, and may be at least one of a gNode B, an eNode B, a Node B, a BS (Base Station), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In the present disclosure, downlink (DL) refers to a wireless transmission path of a signal transmitted from a base station to a terminal, and uplink (UL) refers to a wireless transmission path of a signal transmitted from a terminal to a base station. In addition, although LTE (Long-Term Evolution), LTE-A (LTE-Advanced) or a 5G system may be described as an example below, embodiments of the present disclosure may also be applied to other communication systems having a similar technical background or channel type. For example, this may include the fifth-generation mobile communication technology (5G, new radio, NR) developed after LTE-A. The term "5G" below may also encompass existing LTE, LTE-A, and other similar services. Furthermore, the present disclosure may be applied to other communication systems with some modifications, as determined by a person with skilled technical knowledge, without significantly departing from the scope of the present disclosure.

[0043] At this time, it will be understood that each block of the processing flowchart drawings and combinations of the flowchart drawings can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flowchart block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce a manufactured item that includes an instruction means for performing the functions described in the flowchart block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, and the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also provide steps for performing the functions described in the flowchart block(s).

[0044] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.

[0045] Here, the term '~ unit' used in the present embodiment means software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and the '~ unit' performs certain roles. However, the '~ unit' is not limited to software or hardware. The '~ unit' may be configured to be on an addressable storage medium and may be configured to play one or more processors. Therefore, as an example, the '~ unit' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, 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 '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. In addition, the components and '~parts' may be implemented to play one or more central processing units (CPUs) within the device or secure multimedia card. In addition, in the embodiment, the '~part' may include one or more processors.

[0046] Wireless communication systems are evolving from providing voice-oriented services in the early days to broadband wireless communication systems that provide high-speed, high-quality packet data services, such as communication standards such as 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.

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

[0048] As a future communications system beyond LTE, 5G communication systems must be able to freely reflect the diverse needs of users and service providers. Therefore, they must support services that simultaneously satisfy these diverse requirements. Services being considered for 5G communication systems include enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra Reliability Low Latency Communication (URLLC).

[0049] eMBB aims to provide data transmission rates that are significantly higher than those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, eMBB must be able to support a peak data rate of 20 Gbps in the downlink and a peak data rate of 10 Gbps in the uplink from the perspective of a single base station. Furthermore, 5G communication systems must simultaneously provide the peak data rate and an increased user-perceived data rate for terminals. To meet these requirements, improvements in various transmission and reception technologies, including improved multi-input, multi-output (MIMO) transmission technology, are required. Furthermore, while LTE transmits signals using a maximum transmission bandwidth of 20 MHz in the 2 GHz band, 5G communication systems can meet the data transmission rates required by 5G communication systems by using a wider frequency bandwidth than 20 MHz in the 3-6 GHz or higher 6 GHz band.

[0050] At the same time, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To efficiently provide the IoT, mMTC requires supporting large-scale terminal connections within a cell, improved terminal coverage, enhanced battery life, and reduced terminal costs. The IoT requires the ability to support a large number of terminals (e.g., 1,000,000 terminals / km^2) within a cell, as it provides communication capabilities through the attachment of various sensors and devices. Furthermore, due to the nature of the service, terminals supporting mMTC are likely to be located in shadow areas not covered by cells, such as basements, and thus may require wider coverage than other services provided by 5G communication systems. Terminals supporting mMTC must be inexpensive, and since frequent battery replacement is unlikely, they may require extremely long battery lifespans, such as 10 to 15 years.

[0051] Finally, URLLC refers to cellular-based wireless communication services used for specific mission-critical purposes. Examples include remote control of robots or machinery, industrial automation, unmanned aerial vehicles (UAVs), remote health care, and emergency alerts. Therefore, URLLC communications must offer extremely low latency and high reliability. For example, URLLC-enabled services must meet air interface latency requirements of less than 0.5 milliseconds and a packet error rate (PER) of less than 10^-5. Therefore, for services supporting URLLC, 5G systems must provide shorter transmission time intervals (TTIs) than other services, and design considerations may require the allocation of extensive resources in the frequency band to ensure communication link reliability.

[0052] The three 5G services—eMBB, URLLC, and mMTC—can be multiplexed and transmitted within a single system. To meet the differing requirements of each service, different transmission and reception techniques and parameters can be used. Of course, 5G is not limited to the three services described above.

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

[0054] 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. Specifically, FIG. 1 is a diagram illustrating the basic structure of the time-frequency domain, which is a wireless resource domain in which data or control channels are transmitted in a 5G system.

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

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

[0057] Figure 2 illustrates an example of a structure of a frame (Frame, 200), a subframe (Subframe, 201), and a slot (Slot, 202). One frame (200) can be defined as 10ms. One subframe (201) can be defined as 1ms, and therefore 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). 1 subframe (201) may be composed of one or more slots (202, 203), and the number of slots (202, 203) per 1 subframe (201) may vary depending on the setting value μ (204, 205) for the subcarrier spacing. In an example of FIG. 2, the cases where μ = 0 (204) and μ = 1 (205) as the subcarrier spacing setting value are illustrated. When μ = 0 (204), 1 subframe (201) may be composed of 1 slot (202), and when μ = 1 (205), 1 subframe (201) may be composed of 2 slots (203). That is, the number of slots per 1 subframe ( ) may vary, and accordingly the number of slots per frame ( ) may vary. Depending on the subcarrier spacing setting μ and can be defined as [Table 1] below.

[0058]

[0059] Next, the bandwidth part (BWP) setting in the 5G communication system will be explained in detail with reference to the drawing.

[0060] FIG. 3 is a diagram illustrating an example of bandwidth portion settings in a wireless communication system according to an embodiment of the present disclosure.

[0061] FIG. 3 shows an example in which the UE bandwidth (300) is set to two bandwidth portions, namely, bandwidth portion #1 (BWP#1) (301) and bandwidth portion #2 (BWP#2) (302). The base station can set one or more bandwidth portions to the UE, and can set information such as [Table 2] below for each bandwidth portion.

[0062] BWP ::= SEQUENCE {bwp-Id BWP-Id,(bandwidth part identifier)locationAndBandwidth INTEGER (1..65536),(bandwidth part location)subcarrierSpacing ENUMERATED {n0, n1, n2, n3, n4, n5},(subcarrier spacing)cyclicPrefix ENUMERATED { extended}(cyclic prefix)}

[0063] The configuration information according to an embodiment of the present disclosure is not limited to the above example, and in addition to the configuration information, various parameters related to the bandwidth portion may be configured for the terminal. The above information may be transmitted from the base station to the terminal via upper layer signaling, for example, RRC (Radio Resource Control) signaling. At least one of the configured one or more bandwidth portions may be activated. Whether or not the configured bandwidth portion is activated may be semi-statically transmitted from the base station to the terminal via RRC signaling or dynamically transmitted via DCI (Downlink Control Information).

[0064] According to one embodiment of the present disclosure, a terminal before RRC (Radio Resource Control) connection can receive configuration information for an initial bandwidth portion (Initial BWP) for initial access from a base station through a Master Information Block (MIB). More specifically, the terminal can receive configuration information for a control region (Control Resource Set, CORESET) and a search space, through the MIB, in the initial access phase, to which a PDCCH for receiving system information required for initial access (which may correspond to Remaining System Information (RMSI) or System Information Block 1 (SIB1)) can be transmitted. The control region and search space configured by the MIB may each be regarded as identifier (Identity, ID) 0. The base station can notify the terminal of configuration information such as frequency allocation information, time allocation information, and numerology for control region #0 through the MIB. Additionally, the base station can notify the terminal of the monitoring cycle and occasion settings for control area #0, i.e., search space #0, via the MIB. The terminal can consider the frequency range designated as control area #0, obtained from the MIB, as the initial bandwidth portion for initial access. At this time, the identifier (ID) of the initial bandwidth portion can be considered as 0.

[0065] The bandwidth settings supported by 5G systems can be used for various purposes.

[0066] According to one embodiment of the present disclosure, when the bandwidth supported by a terminal is smaller than the system bandwidth, this can be supported through bandwidth portion configuration. For example, the base station can configure the bandwidth portion frequency location (configuration information 2) for the terminal, thereby allowing the terminal to transmit and receive data at a specific frequency location within the system bandwidth.

[0067] According to one embodiment of the present disclosure, a base station may configure multiple bandwidth portions for a terminal to support different numerologies. For example, to support data transmission and reception using both a 15 kHz subcarrier spacing and a 30 kHz subcarrier spacing for a given terminal, the base station may configure two bandwidth portions with subcarrier spacings of 15 kHz and 30 kHz, respectively. The different bandwidth portions may be frequency-division multiplexed, and when data is to be transmitted and received using a specific subcarrier spacing, the bandwidth portion configured for the corresponding subcarrier spacing may be activated.

[0068] According to one embodiment of the present disclosure, for the purpose of reducing power consumption of a terminal, a base station can set bandwidth portions with different bandwidth sizes for the terminal. For example, if a terminal supports a very large bandwidth, such as 100 MHz, and constantly transmits and receives data within that bandwidth, significant power consumption may occur. In particular, monitoring unnecessary downlink control channels with a large bandwidth of 100 MHz in a traffic-free environment can be very inefficient in terms of power consumption. To reduce power consumption of the terminal, the base station can set a bandwidth portion with a relatively small bandwidth, such as 20 MHz, for the terminal. In a traffic-free environment, the terminal can perform monitoring operations in the 20 MHz bandwidth portion, and when data is generated, it can transmit and receive data in the 100 MHz bandwidth portion according to instructions from the base station.

[0069] In the method for setting the bandwidth part described above, terminals before RRC connection (Connected) can receive configuration information for the initial bandwidth part through the MIB (Master Information Block) during the initial access stage. More specifically, the terminal can receive a control region (Control Resource Set, CORESET) for a downlink control channel on which DCI (Downlink Control Information) for scheduling a SIB (System Information Block) can be transmitted from the MIB of the PBCH (Physical Broadcast Channel). The bandwidth of the control region set by the MIB can be regarded as the initial bandwidth part, and the terminal can receive the PDSCH (Physical Downlink Shared Channel) on which the SIB is transmitted through the set initial bandwidth part. In addition to receiving the SIB, the initial bandwidth part can also be utilized for other system information (Other System Information, OSI), paging, and random access.

[0070] When one or more bandwidth parts are set for a terminal, the base station can instruct the terminal to change (or switch, transition) the bandwidth part using the bandwidth part indicator field in the DCI. For example, in FIG. 3, when the currently activated bandwidth part of the terminal is bandwidth part #1 (301), the base station can instruct the terminal to bandwidth part #2 (302) using the bandwidth part indicator in the DCI, and the terminal can perform a bandwidth part change to bandwidth part #2 (302) indicated by the bandwidth part indicator in the received DCI.

[0071] As mentioned above, since DCI-based bandwidth part changes can be indicated by DCI scheduling PDSCH or PUSCH, when a UE receives a bandwidth part change request, it must be able to seamlessly receive or transmit the PDSCH or PUSCH scheduled by the corresponding DCI in the changed bandwidth part. To this end, the standard stipulates requirements for the delay time (TBWP) required when changing the bandwidth part, which can be defined, for example, as shown in [Table 3].

[0072]

[0073] The bandwidth-partial change delay time requirement can support either Type 1 or Type 2 depending on the terminal's capability. The terminal can report the supported bandwidth-partial delay time type to the base station.

[0074] According to the requirement for bandwidth part change delay time mentioned above, when the terminal receives DCI including bandwidth part change indicator in slot n, the terminal changes to the new bandwidth part indicated by the bandwidth part change indicator in slot n+T. BWP It can be completed at a later time, and transmission and reception for the data channel scheduled by the DCI can be performed in the new bandwidth portion that has been changed. If the base station wants to schedule a data channel in the new bandwidth portion, the terminal's bandwidth portion change delay time (T BWP ), time domain resource allocation for the data channel can be determined. That is, when the base station schedules a data channel with a new bandwidth portion, the data channel can be scheduled after the bandwidth portion change delay time in the method of determining time domain resource allocation for the data channel. Accordingly, the terminal can determine whether the DCI instructing a bandwidth portion change is after the bandwidth portion change delay time (T BWP) may not be expected to indicate a slot offset (K0 or K2) value smaller than that.

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

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

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

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

[0079] - SSS: It serves as a 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.

[0080] - PBCH: Provides essential system information required for the terminal's data channel and control channel transmission and reception. Essential system information may include search space-related control information indicating radio resource mapping information for the control channel, and scheduling control information for a separate data channel that transmits system information.

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

[0082] The terminal can detect PSS and SSS in the initial access stage, and decode PBCH. The terminal can obtain MIB from PBCH, and can set control region (Control Resource Set; CORESET) #0 (which may correspond to a control region with a control region index of 0) therefrom. The terminal can monitor control region #0, assuming that the selected SS / PBCH block and the DMRS (Demodulation Reference Signal) transmitted in control region #0 are QCL (Quasi Co Location). The terminal can receive system information through downlink control information transmitted in control region #0. The terminal can obtain RACH (Random Access Channel) related configuration information required for initial access from the received system information. The terminal can transmit PRACH (Physical RACH) to the base station considering the selected SS / PBCH index, and the base station receiving the PRACH can obtain information on the SS / PBCH block index selected by the terminal. The base station can know that the terminal has selected a block among each SS / PBCH block and monitors the control region #0 associated with it.

[0083] Next, we will specifically explain downlink control information (DCI) in the 5G system.

[0084] 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 a base station to a terminal via DCI. The terminal can monitor a DCI format for fallback and a DCI format for non-fallback for the PUSCH or PDSCH. The fallback DCI format can be composed of fixed fields predefined between the base station and the terminal, and the non-fallback DCI format can include configurable fields.

[0085] DCI can be transmitted over the Physical Downlink Control Channel (PDCCH) after going through the channel coding and modulation process. A Cyclic Redundancy Check (CRC) is attached to the DCI message payload, and the CRC can be scrambled with a Radio Network Temporary Identifier (RNTI) corresponding to the identity of the UE. Different RNTIs can be used depending on the purpose of the DCI message, such as UE-specific data transmission, power control command, or random access response. That is, the RNTI is not transmitted explicitly, but is included in the CRC calculation process. When the UE receives a DCI message transmitted on the PDCCH, it verifies the CRC using the assigned RNTI. If the CRC verification result is correct, the UE can determine that the message has been transmitted to the UE.

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

[0087] DCI format 0_0 can be used as a fallback 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 can include, for example, the information in [Table 4].

[0088]

[0089] DCI format 0_1 ​​can be used as a fallback DCI for scheduling PUSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 0_1 ​​with the CRC scrambled with C-RNTI can include, for example, the information in [Table 5].

[0090]

[0091]

[0092] DCI format 1_0 can be used as a fallback DCI for scheduling PDSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 1_0 with the CRC scrambled with C-RNTI can include, for example, the information in [Table 6].

[0093]

[0094] DCI format 1_1 can be used as a fallback DCI for scheduling PDSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 1_1 with the CRC scrambled with C-RNTI can include, for example, the information in [Table 7].

[0095]

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

[0097] FIG. 4 is a diagram illustrating an example of setting a control region of a downlink control channel in a wireless communication system according to an embodiment of the present disclosure. FIG. 4 illustrates an example of a control region (Control Resource Set, CORESET) in which a downlink control channel is transmitted in a 5G wireless communication system. FIG. 4 illustrates an example in which two control regions (Control Region #1 (401), Control Region #2 (402)) are set within a UE bandwidth part (410) in the frequency axis and one slot (420) in the time axis. The control regions (401, 402) may be set to specific frequency resources (403) within the entire UE bandwidth part (410) in the frequency axis. The control regions (401, 402) may be set to one or more OFDM symbols in the time axis, and this may be defined as a control region length (Control Resource Set Duration, 404). Referring to the illustrated example of FIG. 4, control area #1 (401) may be set to a control area length of 2 symbols, and control area #2 (402) may be set to a control area length of 1 symbol.

[0098] In the aforementioned 5G system, the control region can be established by the base station to the terminal through higher-layer signaling (e.g., system information, Master Information Block (MIB), Radio Resource Control (RRC) signaling). The base station establishing a control region for the terminal means that the base station provides the terminal with information such as the control region identifier (Identity), the frequency location of the control region, and the symbol length of the control region. For example, this information may include the information in [Table 8].

[0099] ControlResourceSet ::= SEQUENCE {-- Corresponds to L1 parameter 'CORESET-ID' controlResourceSetId ControlResourceSetId,(Control domain identifier (Identity)) frequencyDomainResources BIT STRING (SIZE (45)),(Frequency axis resource allocation information) duration INTEGER (1..maxCoReSetDuration),(Time axis resource allocation information) cce-REG-MappingType CHOICE {(CCE-to-REG mapping method) interleaved SEQUENCE {reg-BundleSize ENUMERATED {n2, n3, n6},(REG bundle size) precoderGranularity ENUMERATED {sameAsREG-bundle, allContiguousRBs}, interleaverSize ENUMERATED {n2, n3, n6}(interleaver size) shiftIndex INTEGER(0..maxNrofPhysicalResourceBlocks-1) OPTIONAL(Interleaved Shift)},nonInterleaved NULL},tci-StatesPDCCH SEQUENCE(SIZE (1..maxNrofTCI-StatesPDCCH)) OF TCI-StateId OPTIONAL,(QCL setting information)tci-PresentInDCI ENUMERATED {enabled} OPTIONAL, -- Need S}

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

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

[0102] Fig. 5 shows an example of a basic unit of time and frequency resources that constitute a downlink control channel that can be used in a 5G system. According to Fig. 5, the basic unit of time and frequency resources that constitute a control channel can be referred to as a REG (Resource Element Group, 503), and a 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 constitute a downlink control channel allocation unit.

[0103] As illustrated in FIG. 5, if the basic unit to which a downlink control channel is allocated in a 5G system is called a CCE (Control Channel Element, 504), 1 CCE (504) may be composed of multiple REGs (503). Taking the REG (503) illustrated in FIG. 5 as an example, the REG (503) may be composed of 12 REs, and if 1 CCE (504) is composed of 6 REGs (503), 1 CCE (504) may be composed of 72 REs. When a downlink control region is established, the region may be composed of multiple CCEs (504), and a specific downlink control channel may be mapped to one or multiple CCEs (504) and transmitted according to the aggregation level (AL) within the control region. CCEs (504) within the control area are distinguished by numbers, and the numbers of the CCEs (504) can be assigned according to a logical mapping method.

[0104] The basic unit of the downlink control channel illustrated in FIG. 5, that is, the REG (503), may include both the REs to which the DCI is mapped and the areas to which the DMRS (505), which is a reference signal for decoding the REs, is mapped. As shown in FIG. 5, three DMRSs (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 a 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 (CCEs) that a terminal must attempt to decode at a given aggregation level. Since there are multiple aggregation levels, each of which can be a set of 1, 2, 4, 8, or 16 CCEs, a terminal can have multiple search spaces. A search space set can be defined as the set of search spaces at all configured aggregation levels.

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

[0106] In a 5G system, parameters for a search space for PDCCH can be configured from a base station to a terminal via higher-layer signaling (e.g., SIB, MIB, RRC signaling). For example, the base station can configure the number of PDCCH candidates at each aggregation level L, the monitoring period for the search space, the monitoring occasion for each symbol within the slot 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 corresponding search space, the control region index to be monitored for the search space, etc. to the terminal. For example, the parameters for a search space for PDCCH can include the information in [Table 9].

[0107] SearchSpace ::= SEQUENCE {-- Identity of the search space. SearchSpaceId = 0 identifies the SearchSpace configured via PBCH (MIB) or ServingCellConfigCommon.searchSpaceId SearchSpaceId,(search space identifier)controlResourceSetId ControlResourceSetId,(control space identifier)monitoringSlotPeriodicityAndOffset CHOICE {(monitoring slot level period)sl1 NULL,sl2 INTEGER (0..1),sl4 INTEGER (0..3),sl5 INTEGER (0..4),sl8 INTEGER (0..7),sl10 INTEGER (0..9),sl16 INTEGER (0..15),sl20 INTEGER (0..19)} OPTIONAL,duration(monitoring length) INTEGER (2..2559)monitoringSymbolsWithinSlot BIT STRING (SIZE (14)) OPTIONAL,(슬롘 내 나이스 심보)nrofCandidates SEQUENCE {(집성 별보 PDCCH 이리군 수)aggregationLevel1 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8}, aggregationLevel2 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8},aggregationLevel4 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8},aggregationLevel8 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8},aggregationLevel16 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8}},searchSpaceType CHOICE {(தமம்ப்புக்குக்க்கு திய்)-- Configures this search space as common search space (CSS) and DCI formats to monitor.common SEQUENCE {(공통이이국이)}ue-Specific SEQUENCE {(단말-특정이스국)-- Indicates whether the UE monitors in this USS for DCI formats 0-0 and 1-0 or for formats 0-1 and 1-1.formats ENUMERATED {formats0-0-And-1-0, formats0-1-And-1-1},...}.

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

[0109] According to the configuration information, one or more search space sets 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 terminal-specific search spaces.

[0110] According to one embodiment of the present disclosure, the following combinations of DCI formats and RNTIs can be monitored in a common search space, but are not limited thereto.

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

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

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

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

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

[0116] According to one embodiment of the present disclosure, the following combinations of DCI formats and RNTIs can be monitored in a terminal-specific search space, but are not limited thereto.

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

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

[0119] According to one embodiment of the present disclosure, the specified RNTIs may follow the definitions and uses below, but are not limited thereto.

[0120] - C-RNTI (Cell RNTI): For terminal-specific PDSCH scheduling purposes

[0121] - TC-RNTI (Temporary Cell RNTI): For terminal-specific PDSCH scheduling purposes.

[0122] - CS-RNTI (Configured Scheduling RNTI): Used for terminal-specific PDSCH scheduling that is set semi-statically.

[0123] - RA-RNTI (Random Access RNTI): Used for PDSCH scheduling in the random access phase.

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

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

[0126] - INT-RNTI (Interruption RNTI): Used to indicate whether puncturing is occurring on the PDSCH.

[0127] - TPC-PUSCH-RNTI (Transmit Power Control for PUSCH RNTI): Used to indicate power control commands for PUSCH.

[0128] - TPC-PUCCH-RNTI (Transmit Power Control for PUCCH RNTI): Used to indicate power control commands for PUCCH.

[0129] - TPC-SRS-RNTI (Transmit Power Control for SRS RNTI): Used to indicate power control commands for SRS.

[0130] According to one embodiment of the present disclosure, the aforementioned specified DCI formats may follow definitions such as those in the example of [Table 10], but are not limited thereto.

[0131] DCI formatUsage0_0Scheduling of PUSCH in one cell0_1Scheduling of PUSCH in one cell1_0Scheduling of PDSCH in one cell1_1Scheduling of PDSCH in one cell2_0Notifying a group of UEs of the slot format2_1Notifying a group of UEs of the PRB(s) and OFDM symbol(s) where UE may assume no transmission is intended for the UE2_2Transmission of TPC commands for PUCCH and PUSCH2_3Transmission of a group of TPC commands for SRS transmissions by one or more UEs

[0132] In a 5G system, the search space of aggregation level L in a control region p and a search space set s can be expressed as in [Mathematical Formula 1] below.

[0133]

[0134] - Integration level

[0135] - : Carrier Index

[0136] - : Total number of CCEs existing within the control region p

[0137] - : slot index

[0138] - : Number of PDCCH candidates for aggregation level L

[0139] - = 0, ... , -1: PDCCH candidate index of aggregation level L

[0140] - = 0, ... , -1

[0141] - , , , , ,

[0142] - : Terminal identifier

[0143] The value can be 0 for a common search space.

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

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

[0146] According to one embodiment of the present disclosure, when multiple search space sets are set for a terminal, the following conditions may be considered in a method for determining a search space set that the terminal should monitor.

[0147] If the value of monitoringCapabilityConfig-r16, which is an upper layer signaling, is set to r15monitoringcapability, the terminal can define the maximum values ​​for the number of PDCCH candidates that can be monitored and the number of CCEs that constitute the entire search space (wherein the entire search space means the entire set of CCEs corresponding to the union area of ​​multiple search space sets) per slot. If the value of monitoringCapabilityConfig-r16 is set to r16monitoringcapability, the terminal can define the maximum values ​​for the number of PDCCH candidates that can be monitored and the number of CCEs that constitute the entire search space (wherein the entire search space means the entire set of CCEs corresponding to the union area of ​​multiple search space sets) per Span.

[0148] As described above, depending on the setting value of the upper layer signaling, the maximum number of PDCCH candidates that the terminal can monitor is M. μ is a subcarrier spacing of 15·2μ When defined based on slots in cells set to kHz, the following [Table 11] can be followed, and when defined based on spans, the following [Table 12] can be followed.

[0149]

[0150]

[0151] As above, according to the setting value of the upper layer signaling, the maximum number of CCEs that constitute the entire search space (here, the entire search space means the entire set of CCEs corresponding to the union area of ​​multiple search space sets) is C μ is a subcarrier spacing of 15·2 μ When defined based on slots in cells set to kHz, [Table 13] below can be followed, and when defined based on span, [Table 14] below can be followed.

[0152]

[0153]

[0154] For convenience of explanation, let us define a situation where both conditions 1 and 2 are satisfied at a certain point in time as “condition A.” Therefore, not satisfying condition A may mean not satisfying at least one of conditions 1 and 2.

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

[0156] The following method can be followed to select a partial search space from the entire set of search spaces.

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

[0158] If all search space sets set as common search spaces are selected (i.e., if condition A is satisfied even after selecting all search spaces set as common search spaces), the terminal (or base station) can select search space sets set as terminal-specific search spaces. At this time, if there are multiple search space sets set as terminal-specific search spaces, a search space set with a lower search space set index may have a higher priority. The terminal (or base station) can select terminal-specific search space sets within the range where condition A is satisfied, taking the priority into consideration.

[0159] Below, the rate matching operation and puncturing operation are described in detail.

[0160] When a time and frequency resource A, through which an arbitrary symbol sequence A is to be transmitted, overlaps with an arbitrary time and frequency resource B, a rate matching or puncturing operation may be considered for transmission and reception operations of channel A considering resource C, an area in which resources A and B overlap. The specific operations may follow the contents below.

[0161] The base station can map and transmit channel A only for the remaining resource areas excluding resource C corresponding to the overlapping area with resource B among the entire resources A that are trying to transmit symbol sequence A to the terminal. For example, if symbol sequence A is composed of {symbol #1, symbol #2, symbol #3, symbol #4}, resource A is {resource #1, resource #2, resource #3, resource #4}, and resource B is {resource #3, resource #5}, the base station can sequentially map and transmit symbol sequence A to {resource #1, resource #2, resource #4}, which are the remaining resources among resource A excluding {resource #3} corresponding to resource C. As a result, the base station can map and transmit symbol sequences {symbol #1, symbol #2, symbol #3} to {resource #1, resource #2, resource #4}, respectively.

[0162] The terminal can determine resources A and B from scheduling information for symbol sequence A from the base station, and can thereby determine resource C, which is an area where resources A and B overlap. The terminal can receive symbol sequence A, assuming that symbol sequence A was mapped and transmitted in the remaining area of ​​the entire resource A except for resource C. For example, if symbol sequence A is composed of {symbol #1, symbol #2, symbol #3, symbol #4}, and resource A is {resource #1, resource #2, resource #3, resource #4}, and resource B is {resource #3, resource #5}, the terminal can receive symbol sequence A, assuming that it was sequentially mapped to {resource #1, resource #2, resource #4}, which are the remaining resources of resource A except {resource #3}, which corresponds to resource C. As a result, the terminal can perform a series of subsequent reception operations, assuming that symbol sequences {symbol #1, symbol #2, symbol #3} were mapped and transmitted to {resource #1, resource #2, resource #4}, respectively.

[0163] When a base station wants to transmit symbol sequence A to a terminal, if there is a resource C corresponding to an area overlapping with resource B among all resources A, the base station maps symbol sequence A to the entire resource A, but does not perform transmission in the resource area corresponding to resource C, and can perform transmission only for the remaining resource areas of resource A excluding resource C. For example, if symbol sequence A is composed of {symbol #1, symbol #2, symbol #3, symbol #4}, resource A is {resource #1, resource #2, resource #3, resource #4}, and resource B is {resource #3, resource #5}, the base station can map symbol sequence A {symbol #1, symbol #2, symbol #3, symbol #4} to resource A {resource #1, resource #2, resource #3, resource #4}, and transmit only the symbol sequence {symbol #1, symbol #2, symbol #4} corresponding to the remaining resources {resource #1, resource #2, resource #4} excluding {resource #3} corresponding to resource C among resources A, and may not transmit {symbol #3} mapped to {resource #3} corresponding to resource C. As a result, the base station can transmit symbol sequences {symbol #1, symbol #2, symbol #4} by mapping them to {resource #1, resource #2, resource #4}, respectively.

[0164] The terminal can determine resources A and B from scheduling information for symbol sequence A from the base station, and can thereby determine resource C, which is an area where resources A and B overlap. The terminal can receive symbol sequence A assuming that symbol sequence A is mapped to the entire resource A, but is transmitted only in the remaining area of ​​resource area A excluding resource C. For example, if symbol sequence A is composed of {symbol #1, symbol #2, symbol #3, symbol #4}, resource A is {resource #1, resource #2, resource #3, resource #4}, and resource B is {resource #3, resource #5}, the terminal can assume that symbol sequence A {symbol #1, symbol #2, symbol #3, symbol #4} is mapped to resource A {resource #1, resource #2, resource #3, resource #4} respectively, but {symbol #3} mapped to {resource #3} corresponding to resource C is not transmitted, and can receive it assuming that symbol sequence {symbol #1, symbol #2, symbol #4} corresponding to {resource #1, resource #2, resource #4}, which are the remaining resources among resource A except {resource #3} corresponding to resource C, are mapped and transmitted. As a result, the terminal can assume that the symbol sequence {symbol #1, symbol #2, symbol #4} is transmitted by being mapped to {resource #1, resource #2, resource #4}, respectively, and perform a series of subsequent receiving operations.

[0165] Below, we describe a method for configuring rate-matching resources for the purpose of rate-matching in 5G communication systems. Rate-matching refers to adjusting the size of a signal based on the amount of resources available for transmission. For example, rate-matching a data channel may mean adjusting the size of data accordingly, without mapping the data channel to a specific time and frequency resource region.

[0166] FIG. 6 is a diagram for explaining a method for a base station and a terminal to transmit and receive data by taking into account downlink data channels and rate matching resources according to an embodiment of the present disclosure.

[0167] FIG. 6 illustrates a downlink data channel (PDSCH, 601) and a rate matching resource (602). A base station can configure one or more rate matching resources (602) to a terminal through upper layer signaling (e.g., RRC signaling). Rate matching resource (602) configuration information may include time-domain resource allocation information (603), frequency-domain resource allocation information (604), and period information (605). In the following, the bitmap corresponding to the frequency-domain resource allocation information (604) is named “first bitmap,” the bitmap corresponding to the time-domain resource allocation information (603) is named “second bitmap,” and the bitmap corresponding to the period information (605) is named “third bitmap.” If all or part of the time and frequency resources of the scheduled data channel (601) overlap with the set rate matching resources (602), the base station can rate-match and transmit the data channel (601) in the rate matching resource (602) portion, and the terminal can perform reception and decoding after assuming that the data channel (601) is rate-matched in the rate matching resource (602) portion.

[0168] The base station can dynamically notify the terminal via DCI whether to rate-match the data channel in the set rate-matching resource portion through additional configuration (corresponding to the “rate-matching indicator” in the aforementioned DCI format). Specifically, the base station can select some of the set rate-matching resources and group them into rate-matching resource groups, and can use a bitmap to indicate to the terminal via DCI whether the data channel for each rate-matching resource group is rate-matched. For example, if four rate-matching resources, RMR#1, RMR#2, RMR#3, and RMR#4, are set, the base station can set RMG#1={RMR#1, RMR#2}, RMG#2={RMR#3, RMR#4} as the rate-matching groups, and can use two bits in the DCI field to indicate to the terminal whether to rate-match in RMG#1 and RMG#2, respectively, using a bitmap. For example, if rate matching is required, it can be indicated as “1”, and if rate matching is not required, it can be indicated as “0”.

[0169] In 5G systems, granularity at the "RB symbol level" and "RE level" is supported by setting the aforementioned rate matching resources on terminals. More specifically, the following configuration method can be followed.

[0170] A terminal can set up to four RateMatchPatterns for each bandwidth section through upper layer signaling, and one RateMatchPattern can include the following contents.

[0171] - As a reserved resource within the bandwidth section, a resource in which the time and frequency resource domains of the reserved resource are set by combining a bitmap at the RB level and a bitmap at the symbol level along the frequency axis may be included. The reserved resource may span one or two slots. A time domain pattern (periodicityAndPattern) in which the time and frequency domains composed of each RB level and symbol level bitmap pair are repeated may additionally be set.

[0172] - It may include a time and frequency domain resource area set as a control resource set within the bandwidth section and a resource area corresponding to a time domain pattern set as a search space setting in which the resource area is repeated.

[0173] The terminal can be configured with the following contents through upper layer signaling.

[0174] - The configuration information (lte-CRS-ToMatchAround) for RE corresponding to the LTE CRS (Cell-specific Reference Signal or Common Reference Signal) pattern may include the number of LTE CRS ports (nrofCRS-Ports) and the LTE-CRS-vshift(s) value (v-shift), the location information (carrierFreqDL) of the center subcarrier of the LTE carrier from the reference frequency point (e.g., reference point A), the bandwidth size (carrierBandwidthDL) information of the LTE carrier, and the subframe configuration information (mbsfn-SubframConfigList) corresponding to the MBSFN (Multicast-broadcast single-frequency network). Based on the above-described information, the terminal can determine the location of the CRS within the NR slot corresponding to the LTE subframe.

[0175] - It may include configuration information for a set of resources corresponding to one or more ZP (Zero Power) CSI-RSs within the bandwidth section.

[0176] Next, the rate match process for the LTE CRS described above will be described in detail. In order to coexist between LTE (Long Term Evolution) and NR (New RAT) (LTE-NR Coexistence), NR can provide a function to set a pattern of LTE's CRS (Cell Specific Reference Signal) to an NR terminal. More specifically, the CRS pattern can be provided by RRC signaling including at least one parameter in the ServingCellConfig IE (Information Element) or ServingCellConfigCommon IE. Examples of the parameters can include lte-CRS-ToMatchAround, lte-CRS-PatternList1-r16, lte-CRS-PatternList2-r16, crs-RateMatch-PerCORESETPoolIndex-r16, etc.

[0177] In Rel-15 NR, the lte-CRS-ToMatchAround parameter can be used to configure one CRS pattern per serving cell. In Rel-16 NR, the above function has been extended to allow configuration of multiple CRS patterns per serving cell. More specifically, a single-TRP (transmission and reception point) configured terminal can configure one CRS pattern per LTE carrier, and a multi-TRP configured terminal can configure two CRS patterns per LTE carrier. For example, a single-TRP configured terminal can configure up to three CRS patterns per serving cell through the lte-CRS-PatternList1-r16 parameter. As another example, a multi-TRP configured terminal can configure a CRS per TRP. That is, the CRS pattern for TRP1 can be set via the lte-CRS-PatternList1-r16 parameter, and the CRS pattern for TRP2 can be set via the lte-CRS-PatternList2-r16 parameter. Meanwhile, when two TRPs are set as above, whether both the CRS patterns of TRP1 and TRP2 or only the CRS pattern for one TRP is applied to a specific PDSCH (Physical Downlink Shared Channel) can be determined via the crs-RateMatch-PerCORESETPoolIndex-r16 parameter. Here, if the crs-RateMatch-PerCORESETPoolIndex-r16 parameter is set to enabled, only the CRS pattern of one TRP can be applied, and in other cases, the CRS patterns of both TRPs can be applied.

[0178] [Table 15] shows a ServingCellConfig IE including the CRS pattern, and [Table 16] shows a RateMatchPatternLTE-CRS IE including at least one parameter for the CRS pattern.

[0179] ServingCellConfig ::= SEQUENCE {tdd-UL-DL-ConfigurationDedicated TDD-UL-DL-ConfigDedicated OPTIONAL, -- Cond TDDinitialDownlinkBWP BWP-DownlinkDedicated OPTIONAL, -- Need MdownlinkBWP-ToReleaseList SEQUENCE (SIZE (1..maxNrofBWPs)) OF BWP-Id OPTIONAL, -- Need NdownlinkBWP-ToAddModList SEQUENCE (SIZE (1..maxNrofBWPs)) OF BWP-Downlink OPTIONAL, -- Need NfirstActiveDownlinkBWP-Id BWP-Id OPTIONAL, -- Cond SyncAndCellAddbwp-InactivityTimer ENUMERATED {ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30,ms40,ms50, ms60, ms80,ms100, ms200,ms300, ms500,ms750, ms1280, ms1920, ms2560, spare10, spare9, spare8,spare7, spare6, spare5, spare4, spare3, spare2, spare1} OPTIONAL, --Need RdefaultDownlinkBWP-Id BWP-Id OPTIONAL, -- Need SuplinkConfig UplinkConfig OPTIONAL, -- Need MsupplementaryUplink UplinkConfig OPTIONAL, -- Need Mpdcch-ServingCellConfig SetupRelease { PDCCH-ServingCellConfig} OPTIONAL, -- Need Mpdsch-ServingCellConfig SetupRelease { PDSCH-ServingCellConfig} OPTIONAL,-- Need Mcsi-MeasConfig SetupRelease { CSI-MeasConfig} OPTIONAL, -- Need MsCellDeactivationTimer ENUMERATED {ms20, ms40, ms80, ms160, ms200, ms240,ms320, ms400, ms480, ms520, ms640, ms720,ms840, ms1280, spare2,spare1} OPTIONAL, -- Cond ServingCellWithoutPUCCHcrossCarrierSchedulingConfig CrossCarrierSchedulingConfig OPTIONAL, -- Need Mtag-Id TAG-Id,dummy ENUMERATED {enabled} OPTIONAL, -- Need RpathlossReferenceLinking ENUMERATED {spCell, sCell} OPTIONAL, -- Cond SCellOnlyservingCellMO MeasObjectId OPTIONAL, -- Cond MeasObject...,[[lte-CRS-ToMatchAround SetupRelease { RateMatchPatternLTE-CRS} OPTIONAL, -- Need MrateMatchPatternToAddModList SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF RateMatchPattern OPTIONAL, -- Need NrateMatchPatternToReleaseList SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF RateMatchPatternId OPTIONAL, -- Need NdownlinkChannelBW-PerSCS-List SEQUENCE (SIZE (1..maxSCSs)) OF SCS-SpecificCarrier OPTIONAL -- Need S]],[[supplementaryUplinkRelease ENUMERATED {true} OPTIONAL, -- Need Ntdd-UL-DL-ConfigurationDedicated-IAB-MT-r16 TDD-UL-DL-ConfigDedicated-IAB-MT-r16 OPTIONAL, -- Cond TDD_IABdormantBWP-Config-r16 SetupRelease { DormantBWP-Config-r16} OPTIONAL, -- Need Mca-SlotOffset-r16 CHOICE {refSCS15kHz INTEGER (-2..2),refSCS30KHz INTEGER (-5..5),refSCS60KHz INTEGER (-10..10),refSCS120KHz INTEGER (-20..20)} OPTIONAL, -- Cond AsyncCAchannelAccessConfig-r16 SetupRelease { ChannelAccessConfig-r16} OPTIONAL, -- Need MintraCellGuardBandsDL-List-r16 SEQUENCE (SIZE (1..maxSCSs)) OF IntraCellGuardBandsPerSCS-r16 OPTIONAL, -- Need SintraCellGuardBandsUL-List-r16 SEQUENCE (SIZE (1..maxSCSs)) OF IntraCellGuardBandsPerSCS-r16 OPTIONAL, -- Need Scsi-RS-ValidationWith-DCI-r16 ENUMERATED {enabled} OPTIONAL, -- Need Rlte-CRS-PatternList1-r16 SetupRelease { LTE-CRS-PatternList-r16} OPTIONAL, -- Need Mlte-CRS-PatternList2-r16 SetupRelease { LTE-CRS-PatternList-r16} OPTIONAL,-- Need Mcrs-RateMatch-PerCORESETPoolIndex-r16 ENUMERATED {enabled} OPTIONAL, -- Need RenableTwoDefaultTCI-States-r16 ENUMERATED {enabled} OPTIONAL, -- Need RenableDefaultTCI-StatePerCoresetPoolIndex-r16 ENUMERATED {enabled} OPTIONAL, -- Need RenableBeamSwitchTiming-r16 ENUMERATED {true} OPTIONAL, -- Need Rcbg-TxDiffTBsProcessingType1-r16 ENUMERATED {enabled} OPTIONAL, -- Need Rcbg-TxDiffTBsProcessingType2-r16 ENUMERATED {enabled} OPTIONAL -- Need R]]},

[0180]

[0181] FIG. 7 is a diagram illustrating an example of frequency axis resource allocation of PDSCH in a wireless communication system according to an embodiment of the present disclosure.

[0182] FIG. 7 is a diagram illustrating three frequency axis resource allocation methods, type 0 (700), type 1 (705), and dynamic switch (710), which can be set through an upper layer in an NR wireless communication system.

[0183] Referring to Fig. 7, if a terminal is configured to use only resource type 0 through upper layer signaling (700), some downlink control information (DCI) that allocates a PDSCH to the terminal may include a bitmap composed of NRBG bits. The conditions for this will be explained later. In this case, NRBG may mean the number of RBGs (resource block groups) determined as shown in [Table 17] below according to the BWP size allocated by the BWP indicator and the upper layer parameter rbg-Size, and data may be transmitted to an RBG indicated as 1 by the bitmap.

[0184] Bandwidth Part SizeConfiguration 1Configuration 21-362437-724873-144816145-2751616

[0185] If the terminal is configured to use only resource type 1 through upper layer signaling (705), some DCIs that allocate PDSCH to the terminal It may include frequency axis resource allocation information consisting of bits. The conditions for this will be explained later. Through this, the base station can set the starting VRB (720) and the length (725) of frequency axis resources allocated continuously therefrom.

[0186] If a terminal is configured to use both resource type 0 and resource type 1 through upper layer signaling (710), some DCIs that allocate PDSCH to the terminal include frequency-axis resource allocation information composed of bits of a larger value (735) among the payload (715) for configuring resource type 0 and the payload (720, 725) for configuring resource type 1. Conditions for this will be explained later. At this time, one bit may be added to the first part (MSB) of the frequency-axis resource allocation information in the DCI, and if the bit has a value of '0', it may indicate that resource type 0 is used, and if the bit has a value of '1', it may indicate that resource type 1 is used.

[0187] Below, a time domain resource allocation method for data channels in next-generation mobile communication systems (5G or NR systems) is described.

[0188] A base station can set up a table for time domain resource allocation information for a downlink data channel (Physical Downlink Shared Channel, PDSCH) and an uplink data channel (Physical Uplink Shared Channel, PUSCH) to a terminal through higher layer signaling (e.g., RRC signaling). A table with up to maxNrofDL-Allocations=16 entries can be set up for PDSCH, and a table with up to maxNrofUL-Allocations=16 entries can be set up for PUSCH. In one embodiment, the time domain resource allocation information may include PDCCH-to-PDSCH slot timing (corresponding to the time interval in slot units between the time point of receiving a PDCCH and the time point of transmitting a PDSCH scheduled by the received PDCCH, denoted as K0), PDCCH-to-PUSCH slot timing (corresponding to the time interval in slot units between the time point of receiving a PDCCH and the time point of transmitting a PUSCH scheduled by the received PDCCH, denoted as K2), information on the position and length of the start symbol for which a PDSCH or PUSCH is scheduled within a slot, a mapping type of the PDSCH or PUSCH, etc. For example, information such as [Table 18] or [Table 19] below may be transmitted from the base station to the terminal.

[0189] PDSCH-TimeDomainResourceAllocationList information elementPDSCH-TimeDomainResourceAllocationList ::= SEQUENCE (SIZE(1..maxNrofDL-Allocations)) OF PDSCH-TimeDomainResourceAllocationPDSCH-TimeDomainResourceAllocation ::= SEQUENCE {k0 INTEGER(0..32) OPTIONAL, -- Need S(PDCCH-to-PDSCH timing, in slot units)mappingType ENUMERATED {typeA, typeB},(PDSCH mapping type)startSymbolAndLength INTEGER (0..127)(PDSCH start symbol and length)}

[0190] PDSCH-TimeDomainResourceAllocationList information elementPUSCH-TimeDomainResourceAllocationList ::= SEQUENCE (SIZE(1..maxNrofUL-Allocations)) OF PUSCH-TimeDomainResourceAllocationPUSCH-TimeDomainResourceAllocation ::= SEQUENCE {K2 INTEGER(0..32) OPTIONAL, -- Need S(PDCCH-to-PUSCH timing, in slot units)mappingType ENUMERATED {typeA, typeB},(PUSCH mapping type)startSymbolAndLength INTEGER (0..127)(PUSCH start symbol and length)}

[0191] The base station can notify the terminal of one of the entries in the table for the time domain resource allocation information described above via L1 signaling (e.g., DCI). For example, this may be indicated by the "Time Domain Resource Allocation" field in the DCI. The terminal can obtain time domain resource allocation information for the PDSCH or PUSCH based on the DCI received from the base station.

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

[0193] Referring to FIG. 8, the base station uses the upper layer to set the subcarrier spacing (SCS) (μ) of the data channel and the control channel. PDSCH , μ PDCCH ), scheduling offset (K0) value, and the time axis position of the PDSCH resource can be indicated according to the OFDM symbol start position (800) and length (805) within a slot (810) dynamically indicated through DCI.

[0194] FIG. 9 is a diagram illustrating an example of time-domain resource allocation according to subcarrier spacing of a data channel and a control channel in a wireless communication system according to an embodiment of the present disclosure.

[0195] Referring to Fig. 9, when the subcarrier spacing of the data channel and the control channel is the same (900, μ PDSCH = μ PDCCH), since the slot numbers for data and control are the same, the base station and the terminal can generate a scheduling offset according to the predetermined slot offset K0. On the other hand, when the subcarrier spacing of the data channel and the control channel are different (905) (μ PDSCH ≠ μ PDCCH ), since the slot numbers for data and control are different, the base station and the terminal can generate a scheduling offset according to a predetermined slot offset K0 based on the subcarrier interval of the PDCCH.

[0196] Next, we describe the scheduling method for PUSCH transmission. PUSCH transmission can be dynamically scheduled by the UL grant within the DCI or can operate by configured grant Type 1 or Type 2. Dynamic scheduling instructions for PUSCH transmission can be provided in DCI format 0_0 or 0_1.

[0197] Configured grant Type 1 PUSCH transmission can be semi-statically configured by receiving configuredGrantConfig including rrc-ConfiguredUplinkGrant of [Table 20] through higher-order signaling, without receiving UL grant in DCI. Configured grant Type 2 PUSCH transmission can be semi-persistently scheduled by UL grant in DCI after receiving configuredGrantConfig not including rrc-ConfiguredUplinkGrant of [Table 20] through higher-order signaling. When PUSCH transmission operates by configured grant, parameters applied to PUSCH transmission can be applied through configuredGrantConfig of higher-order signaling of [Table 20], except dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, scaling of UCI-OnPUSCH provided by pusch-Config of [Table 21]. If the terminal has been provided with transformPrecoder in configuredGrantConfig, which is the upper signaling of [Table 20], the terminal can apply tp-pi2BPSK in pusch-Config of [Table 21] for PUSCH transmission operated by configured grant.

[0198] ConfiguredGrantConfig ::= SEQUENCE {frequencyHopping ENUMERATED {intraSlot, interSlot} OPTIONAL, -- Need S,cg-DMRS-Configuration DMRS-UplinkConfig,mcs-Table ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need Smcs-TableTransformPrecoder ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need Suci-OnPUSCH SetupRelease { CG-UCI-OnPUSCH} OPTIONAL, -- Need MresourceAllocation ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch},rbg-Size ENUMERATED {config2} OPTIONAL, -- Need SpowerControlLoopToUse ENUMERATED {n0, n1},p0-PUSCH-Alpha P0-PUSCH-AlphaSetId,transformPrecoder ENUMERATED {enabled, disabled} OPTIONAL, -- Need SnrofHARQ-Processes INTEGER(1..16),repK ENUMERATED {n1, n2, n4, n8},repK-RV ENUMERATED {s1-0231, s2-0303, s3-0000} OPTIONAL, -- Need Rperiodicity ENUMERATED {sym2, sym7, sym1x14, sym2x14, sym4x14, sym5x14, sym8x14, sym10x14, sym16x14, sym20x14,sym32x14, sym40x14, sym64x14, sym80x14, sym128x14, sym160x14, sym256x14, sym320x14, sym512x14,sym640x14, sym1024x14, sym1280x14, sym2560x14, sym5120x14,sym6, sym1x12, sym2x12, sym4x12, sym5x12, sym8x12, sym10x12, sym16x12, sym20x12, sym32x12,sym40x12, sym64x12, sym80x12, sym128x12, sym160x12, sym256x12, sym320x12, sym512x12, sym640x12,sym1280x12, sym2560x12},configuredGrantTimer INTEGER (1..64) OPTIONAL, -- Need Rrrc-ConfiguredUplinkGrant SEQUENCE {timeDomainOffset INTEGER (0..5119),timeDomainAllocation INTEGER (0..15),frequencyDomainAllocation BIT STRING (SIZE(18)),antennaPort INTEGER (0..31),dmrs-SeqInitialization INTEGER (0..1) OPTIONAL, -- Need RprecodingAndNumberOfLayers INTEGER (0..63),srs-ResourceIndicator INTEGER (0..15) OPTIONAL, -- Need RmcsAndTBS INTEGER (0..31),frequencyHoppingOffset INTEGER (1.. maxNrofPhysicalResourceBlocks-1) OPTIONAL, -- Need RpathlossReferenceIndex INTEGER (0..maxNrofPUSCH-PathlossReferenceRSs-1),...} OPTIONAL, -- Need R...}.

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

[0200] As described above, PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1, and can be semi-statically configured by configured grant. If the UE is instructed to schedule PUSCH transmission via DCI format 0_0, the UE can perform beam configuration for PUSCH transmission using pucch-spatialRelationInfoID corresponding to the UE-specific PUCCH resource corresponding to the minimum ID within the activated uplink BWP within the serving cell, and in this case, the PUSCH transmission can be based on a single antenna port. The UE may not expect scheduling for PUSCH transmission via DCI format 0_0 within a BWP where a PUCCH resource including pucch-spatialRelationInfo is not configured. If the UE has not configured txConfig in pusch-Config of [Table 21], the UE may not expect to be scheduled with DCI format 0_1.

[0201] PUSCH-Config ::= SEQUENCE {dataScramblingIdentityPUSCH INTEGER (0..1023) OPTIONAL, -- Need StxConfig ENUMERATED {codebook, nonCodebook} OPTIONAL, -- Need Sdmrs-UplinkForPUSCH-MappingTypeA SetupRelease { DMRS-UplinkConfig} OPTIONAL, -- Need Mdmrs-UplinkForPUSCH-MappingTypeB SetupRelease { DMRS-UplinkConfig} OPTIONAL, -- Need Mpusch-PowerControl PUSCH-PowerControl OPTIONAL, -- Need MfrequencyHopping ENUMERATED {intraSlot, interSlot} OPTIONAL, -- Need SfrequencyHoppingOffsetLists SEQUENCE (SIZE (1..4)) OF INTEGER (1..maxNrofPhysicalResourceBlocks-1)OPTIONAL, -- Need MresourceAllocation ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch},pusch-TimeDomainAllocationList SetupRelease { PUSCH-TimeDomainResourceAllocationList} OPTIONAL, -- Need Mpusch-AggregationFactor ENUMERATED { n2, n4, n8} OPTIONAL, -- Need Smcs-Table ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need Smcs-TableTransformPrecoder ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need StransformPrecoder ENUMERATED {enabled, disabled} OPTIONAL, -- Need ScodebookSubset ENUMERATED {fullyAndPartialAndNonCoherent, partialAndNonCoherent,nonCoherent}OPTIONAL, -- Cond codebookBasedmaxRank INTEGER (1..4) OPTIONAL, -- Cond codebookBasedrbg-Size ENUMERATED { config2} OPTIONAL, -- Need Suci-OnPUSCH SetupRelease { UCI-OnPUSCH} OPTIONAL, -- Need Mtp-pi2BPSK ENUMERATED {enabled} OPTIONAL, -- Need S...}.

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

[0203] At this time, the SRI can be given through the SRS resource indicator field in the DCI or configured through the srs-ResourceIndicator higher-level signaling. The UE is configured with at least one SRS resource when transmitting a codebook-based PUSCH, and can be configured with up to two. When the UE receives an SRI through the DCI, the SRS resource indicated by the SRI can refer to an SRS resource corresponding to the SRI among the SRS resources transmitted before the PDCCH containing the SRI. In addition, the TPMI and transmission rank can be given through the precoding information and number of layers fields in the DCI or configured through the precodingAndNumberOfLayers higher-level signaling. The TPMI can be used to indicate the precoder applied to the PUSCH transmission. If the UE is configured with one SRS resource, the TPMI can be used to indicate the precoder to be applied in the configured one SRS resource. When a terminal is configured with multiple SRS resources, TPMI can be used to indicate the precoder to be applied in the SRS resource indicated through SRI.

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

[0205] A terminal can be configured with one SRS resource set in which the usage value in the upper signaling SRS-ResourceSet is set to 'codebook', and one SRS resource within the SRS resource set can be indicated via SRI. If multiple SRS resources are configured in an SRS resource set in which the usage value in the upper signaling SRS-ResourceSet is set to 'codebook', the terminal can expect that the value of nrofSRS-Ports in the upper signaling SRS-Resource is set to the same value for all SRS resources.

[0206] The terminal transmits to the base station one or more SRS resources included in the SRS resource set in which the usage value is set to 'codebook' according to upper signaling, and the base station can select one of the SRS resources transmitted by the terminal and instruct the terminal to perform PUSCH transmission using transmission beam information of the corresponding SRS resource. At this time, in codebook-based PUSCH transmission, the SRI is used as information for selecting an index of one SRS resource and can be included in the DCI. Additionally, the base station can include in the DCI information indicating a TPMI and rank to be used by the terminal for PUSCH transmission. The terminal can perform PUSCH transmission by applying the indicated rank and the precoder indicated by the TPMI based on the transmission beam of the corresponding SRS resource using the SRS resource indicated by the SRI.

[0207] Next, we describe non-codebook-based PUSCH transmission. Non-codebook-based PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1, and can operate semi-statically based on a configured grant. If at least one SRS resource is configured within an SRS resource set in which the usage value in the upper signaling, SRS-ResourceSet, is set to 'nonCodebook', the UE can be scheduled for non-codebook-based PUSCH transmission via DCI format 0_1.

[0208] For an SRS resource set in which the usage value in the upper signaling SRS-ResourceSet is set to 'nonCodebook', the UE can be configured with one connected NZP CSI-RS resource (non-zero power CSI-RS). The UE can perform calculations for a precoder for SRS transmission by measuring the NZP CSI-RS resource connected to the SRS resource set. If the difference between the last received symbol of the aperiodic NZP CSI-RS resource connected to the SRS resource set and the first symbol of the aperiodic SRS transmission at the UE is less than 42 symbols, the UE may not expect that information for the precoder for SRS transmission is updated.

[0209] If the value of resourceType in the upper signaling SRS-ResourceSet is set to 'aperiodic', the connected NZP CSI-RS can be indicated by the SRS request field in DCI format 0_1 ​​or 1_1. At this time, if the connected NZP CSI-RS resource is an aperiodic NZP CSI-RS resource, the presence of the connected NZP CSI-RS is indicated when the value of the SRS request field in DCI format 0_1 ​​or 1_1 is not '00'. At this time, the DCI must not indicate cross-carrier or cross BWP scheduling. In addition, if the value of the SRS request indicates the presence of an NZP CSI-RS, the NZP CSI-RS is located in the slot in which the PDCCH including the SRS request field is transmitted. At this time, the TCI states set for the scheduled subcarriers may not be set to QCL-TypeD.

[0210] If a periodic or semi-persistent SRS resource set is configured, the associated NZP CSI-RS can be indicated through the associatedCSI-RS within the upper-level signaling SRS-ResourceSet. For non-codebook-based transmission, the UE may not expect the upper-level signaling spatialRelationInfo for the SRS resource and the associatedCSI-RS within the upper-level signaling SRS-ResourceSet to be configured together.

[0211] When multiple SRS resources are configured, the UE can determine the precoder and transmission rank to be applied to PUSCH transmission based on the SRI indicated by the base station. At this time, the SRI can be indicated through the SRS resource indicator field in the DCI or set through the upper signaling srs-ResourceIndicator. Similar to the codebook-based PUSCH transmission described above, when the UE receives an SRI through the DCI, the SRS resource indicated by the SRI can refer to an SRS resource corresponding to the SRI among the SRS resources transmitted before the PDCCH containing the SRI. The UE can use one or more SRS resources for SRS transmission, and the maximum number of SRS resources that can be simultaneously transmitted in the same symbol within one SRS resource set and the maximum number of SRS resources can be determined by the UE capability reported by the UE to the base station. At this time, the SRS resources that the UE simultaneously transmits can occupy the same RB. A terminal can configure one SRS port for each SRS resource. Only one SRS resource set with the usage value set to "nonCodebook" in the upper-level signaling SRS-ResourceSet can be configured, and up to four SRS resources for non-codebook-based PUSCH transmission can be configured.

[0212] The base station transmits one NZP-CSI-RS associated with an SRS resource set to the terminal, and the terminal can calculate a precoder to be used when transmitting one or more SRS resources within the SRS resource set based on the result measured upon reception of the NZP-CSI-RS. When the terminal transmits one or more SRS resources within the SRS resource set in which usage is set to 'nonCodebook' to the base station, the terminal applies the calculated precoder, and the base station can select one or more SRS resources from among the received one or more SRS resources. At this time, in non-codebook based PUSCH transmission, the SRI represents an index that can express a combination of one or more SRS resources, and the SRI can be included in the DCI. At this time, the number of SRS resources indicated by the SRI transmitted by the base station can be the number of transmission layers of the PUSCH, and the terminal can transmit the PUSCH by applying the precoder applied to SRS resource transmission to each layer.

[0213] Next, the PUSCH preparation procedure time is described. When the base station schedules a UE to transmit a PUSCH using DCI format 0_0, 0_1, or 0_2, the UE may require a PUSCH preparation procedure time to transmit the PUSCH by applying the transmission method indicated through the DCI (transmission precoding method of SRS resources, number of transmission layers, spatial domain transmission filter). NR takes this into account and defines the PUSCH preparation procedure time. The PUSCH preparation procedure time of the UE can follow the following [Mathematical Formula 2].

[0214]

[0215] T as described in mathematical formula 2 proc,2 In , each variable can have the following meanings:

[0216] - N2: The number of symbols determined by the UE processing capability 1 or 2 and the numerology μ according to the UE capability. If the UE processing capability is reported as 1 according to the UE capability report, it may have the value of [Table 22]. If the UE processing capability is reported as 2 and the availability of UE processing capability 2 is set through upper layer signaling, it may have the value of [Table 23], but is not limited thereto.

[0217]

[0218]

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

[0220] - κ: 64

[0221] - μ: μ DL or μ UL Medium, T proc,2 This follows the larger value μ DL refers to the numerology of the downlink in which the PDCCH containing the DCI scheduling the PUSCH is transmitted, and μ UL It can increase the numerology of the uplink where PUSCH is transmitted.

[0222] - T c : 1 / (Δf max *N f ), Δf max = 480*10 3 Hz, N f =can have 4096.

[0223] - d 2,2 : If the DCI scheduling the PUSCH indicates BWP switching, it follows the BWP switching time, otherwise it can have 0.

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

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

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

[0227] When the base station and the terminal consider the time domain resource mapping information of the PUSCH scheduled through DCI and the influence of the timing advance between uplink and downlink, the base station and the terminal determine T from the last symbol of the PDCCH including the DCI that scheduled the PUSCH. proc,2 If the first symbol of the PUSCH begins before the first uplink symbol of the CP, the PUSCH preparation time may be determined to be insufficient. If this is not the case, the base station and the UE may determine that the PUSCH preparation time is sufficient. The UE transmits the PUSCH only when the PUSCH preparation time is sufficient, and may ignore the DCI scheduling the PUSCH if the PUSCH preparation time is insufficient.

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

[0229] Referring to FIG. 10, the wireless protocol of the next-generation mobile communication system may be composed of NR SDAP (Service Data Adaptation Protocol 1025, 1070), NR PDCP (Packet Data Convergence Protocol 1030, 1065), NR RLC (Radio Link Control 1035, 1060), and NR MAC (Medium Access Control 1040, 1055) in the terminal and NR base station, respectively.

[0230] The main functions of NR SDAP (1025, 1070) may include some of the following functions:

[0231] - Transfer of user plane data

[0232] - Mapping function between QoS flow and data bearer for both DL and UL

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

[0234] - Ability to map reflective QoS flow to data bearer for uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).

[0235] For the above SDAP layer device, the terminal can be configured by RRC message for each PDCP layer device, each bearer, or each logical channel, whether to use the header of the SDAP layer device or whether to use the function of the SDAP layer device, and when the SDAP header is configured, the terminal can instruct the NAS QoS reflection configuration 1-bit indicator (NAS reflective QoS) and the AS QoS reflection configuration 1-bit indicator (AS reflective QoS) of the SDAP header to update or reset the mapping information for the QoS flow and data bearer of the uplink and downlink. The SDAP header can include QoS flow ID information indicating QoS. The QoS information can be used as data processing priority, scheduling information, etc. to support smooth service.

[0236] The main functions of NR PDCP (1030, 1065) may include some of the following functions:

[0237] - Header compression and decompression (ROHC only)

[0238] - User data transfer function

[0239] - In-sequence delivery of upper layer PDUs

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

[0241] - PDCP PDU reordering for reception

[0242] - Duplicate detection of lower layer SDUs

[0243] - Retransmission function (Retransmission of PDCP SDUs)

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

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

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

[0247] The main functions of NR RLC (1035, 1060) may include some of the following functions:

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

[0249] - In-sequence delivery of upper layer PDUs

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

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

[0252] - Concatenation, segmentation and reassembly of RLC SDUs

[0253] - Re-segmentation of RLC data PDUs

[0254] - Reordering of RLC data PDUs

[0255] - Duplicate detection function

[0256] - Protocol error detection

[0257] - RLC SDU discard function

[0258] - RLC re-establishment function

[0259] In the above, the in-sequence delivery function of the NR RLC device refers to the function of sequentially delivering RLC SDUs received from a lower layer to an upper layer. The in-sequence delivery function of the NR RLC device may include a function of reassembling and delivering a single RLC SDU when it is received divided into multiple RLC SDUs, a function of rearranging received RLC PDUs based on the 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 an NR RLC device may include a function to sequentially deliver to the upper layer only the RLC SDUs up to the lost RLC SDU when there is a lost RLC SDU, or may include a function to sequentially deliver to the upper layer all RLC SDUs received before the timer starts if a predetermined timer has expired even if there is a lost RLC SDU. Alternatively, the in-sequence delivery function of an NR RLC device may include a function to sequentially deliver to the upper layer all RLC SDUs received up to the present if a predetermined timer has expired even if there is a lost RLC SDU.In addition, the RLC PDUs may be processed in the order in which they are received (in the order of arrival, regardless of the order of the sequence number) and delivered to the PDCP device out of order (out-of-sequence delivery). In the case of segments, the segments stored in the buffer or to be received later may be received, reconstructed into a complete RLC PDU, processed, and delivered to the PDCP device. The NR RLC layer may not include a concatenation function, and the function may be performed in the NR MAC layer or replaced with a multiplexing function of the NR MAC layer.

[0260] The out-of-sequence delivery function of the NR RLC device mentioned above refers to the function of directly delivering RLC SDUs received from a lower layer to an upper layer regardless of the order, and may include a function of reassembling and delivering RLC SDUs when one RLC SDU is received divided into multiple RLC SDUs, and may include a function of storing and arranging the RLC SN or PDCP SN of received RLC PDUs to record lost RLC PDUs.

[0261] NR MAC (1040, 1055) can be connected to multiple NR RLC layer devices configured in one terminal, and the main functions of NR MAC can include some of the following functions.

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

[0263] - Multiplexing / demultiplexing of MAC SDUs

[0264] - Scheduling information reporting function

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

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

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

[0268] - MBMS service identification function

[0269] - Transport format selection function

[0270] - Padding function

[0271] The NR PHY layer (1045, 1050) can perform operations of channel coding and modulating upper layer data, converting it into OFDM symbols and transmitting it through a wireless channel, or demodulating and channel decoding OFDM symbols received through a wireless channel and transmitting them to a higher layer.

[0272] The above wireless protocol structure can have various detailed structures 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 that has a single structure for each layer, such as 1000. On the other hand, when a base station transmits data to a terminal based on CA (carrier aggregation) that uses multiple carriers in a single TRP, the base station and the terminal use a protocol structure that has a single structure up to RLC, such as 1010, but multiplexes the PHY layer through the MAC layer. As another example, when a base station transmits data to a terminal based on DC (dual connectivity) that uses multiple carriers in multiple TRPs, the base station and the terminal use a protocol structure that has a single structure up to RLC, such as 1020, but multiplexes the PHY layer through the MAC layer.

[0273] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings. The contents of the present disclosure can be applied to FDD and TDD systems. In the present disclosure below, upper signaling (or upper layer signaling) refers to a signal transmission method in which a base station transmits a signal to a terminal using a downlink data channel of a physical layer, or a terminal transmits a signal to a base station using an uplink data channel of a physical layer, and may also be referred to as RRC signaling, PDCP signaling, or MAC (medium access control) control element (MAC control element; MAC CE).

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

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

[0276] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings. Hereinafter, a base station is an entity that performs resource allocation of a terminal, and may be at least one of a gNode B, a gNB, an eNode B, a Node B, a BS (Base Station), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. Although embodiments of the present disclosure are described below using a 5G system as an example, embodiments of the present disclosure may be applied to other communication systems having similar technical backgrounds or channel types. For example, this may include LTE or LTE-A mobile communication and mobile communication technologies developed after 5G. Therefore, embodiments of the present disclosure may be applied to other communication systems with some modifications without significantly departing from the scope of the present disclosure as determined by a person skilled in the art. The contents of the present disclosure are applicable to FDD and TDD systems.

[0277] Additionally, when describing the present disclosure, detailed descriptions of related functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present disclosure. Furthermore, the terms described below are defined based on the functions of the present disclosure and may vary depending on the intent or custom of the user or operator. Therefore, their definitions should be based on the contents of this specification.

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

[0279] - MIB (Master Information Block)

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

[0281] - RRC (Radio Resource Control)

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

[0283] In addition, L1 signaling may be signaling corresponding to at least one or a combination of one or more signaling methods using the physical layer channel or signaling below.

[0284] - PDCCH (Physical Downlink Control Channel)

[0285] - DCI (Downlink Control Information)

[0286] - UE-specific DCI

[0287] - Group common DCI

[0288] - Common DCI

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

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

[0291] - PUCCH (Physical Uplink Control Channel)

[0292] - UCI (Uplink Control Information)

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

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

[0295] According to the NR system, a terminal can receive a master information block (MIB) from a physical broadcast channel (PBCH) included in an SS / PBCH block. The terminal can obtain the location of a frequency domain of a CORESET in which a PDCCH is transmitted from the MIB. The terminal can determine the bandwidth of the CORESET (i.e., the frequency bandwidth from the lowest PRB on the frequency axis to the highest PRB on the frequency axis) as an initial downlink bandwidth part. The terminal can expect that the DCI format received from the CORESET will receive a PDSCH within the initial downlink bandwidth part. That is, when the terminal receives the DCI format and interprets the frequency domain allocation information of the PDSCH scheduled by the DCI format, the interpretation can be based on the initial downlink bandwidth part. Alternatively, the interpretation can be based on the number of RBs included in the initial downlink bandwidth part.

[0296] The MIB may include 4 bits indicating the frequency domain location of the CORESET. The interpretation of the 4 bits may vary depending on the subcarrier spacing of the SS / PBCH, the subcarrier spacing of the CORESET, and the minimum channel bandwidth. For example, [Table 24] is a table for interpreting the 4 bits when the subcarrier spacing of the SS / PBCH is 30 kHz, the subcarrier spacing of the CORESET is 30 kHz, and the minimum channel bandwidth is 5 MHz or 10 MHz. Here, the 4 bits may indicate one of the values ​​0, 1, …, 15.

[0297]

[0298] Referring to [Table 24], the number of CORESETs indicated by the terminal in the MIB ( ) can be 24 or 48. This can be a bandwidth of 8.64 MHz to 17.28 MHz. Accordingly, the terminal can receive a PDCCH from a CORESET within a bandwidth of 8.64 MHz to 17.28 MHz. The PDCCH can include a DCI that schedules a PDSCH including system information.

[0299] FIG. 11 is a diagram illustrating an SS / PBCH block, a CORESET, and a PDSCH according to an embodiment of the present disclosure. Specifically, FIG. 11 illustrates an SS / PBCH block, a CORESET, and a PDSCH when 4 bits indicating the frequency domain location of the CORESET in the MIB indicate index 13.

[0300] Referring to FIG. 11, a terminal may receive an SS / PBCH block (1100). The SS / PBCH block may include a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) for providing downlink synchronization and a cell index, and a PBCH, which is a physical channel for providing MIB, which is key cell information. The MIB may include information as shown in [Table 25]. Here, pdcch-ConfigSIB1 may include 4 bits indicating a location of a frequency domain of CORESET. More specifically, pdcch-COnfigSIB1 may include controlResourceSetZero, and the controlResourceSetZero may be 4 bits indicating one of the values ​​0, 1,…, 15.

[0301] MIB ::= SEQUENCE {systemFrameNumber BIT STRING (SIZE (6)),subCarrierSpacingCommon ENUMERATED {scs15or60, scs30or120},ssb-SubcarrierOffset INTEGER (0..15),dmrs-TypeA-Position ENUMERATED {pos2, pos3},pdcch-ConfigSIB1 PDCCH-ConfigSIB1,cellBarred ENUMERATED {barred, notBarred},intraFreqReselection ENUMERATED {allowed, notAllowed},spare BIT STRING (SIZE (1))}PDCCH-ConfigSIB1 ::= SEQUENCE { controlResourceSetZero ControlResourceSetZero,searchSpaceZero SearchSpaceZero}ControlResourceSetZero ::= INTEGER (0..15)

[0302] The terminal can determine the frequency position or time position of the CORESET (1110) based on the MIB received from the base station. The CORESET may be referred to as CORESET0 (i.e., the index of the CORESET may be 0). The CORESET may be expressed in terms of the frequency axis. ([Table 24] (1140)) RBs. The RBs may be consecutive RBs. The index of the starting RB of the CORESET may be determined based on the frequency position of the SS / PBCH block and Offset=12 of the MIB (Offset (1130) of Table 24). The number of OFDM symbols included in the time axis of the CORESET is 2 (Offset (1130) of Table 24). ) may be.

[0303] The terminal can receive a PDCCH that schedules a PDSCH including a system information block (SIB) from the CORESET. The PDCCH can include a DCI format that schedules the system information block. The DCI format can be CRC scrambled with a specific RNTI. Here, the specific RNTI can be called SI-RNTI (System Information-RNTI), and the value of the SI-RNTI can be a value preset by the base station and the terminal. For example, the value of the SI-RNTI can be '000…0' with a length of 16 bits.

[0304] The DCI format for scheduling the system information block can be composed of the DCI fields in [Table 26]. Here, may be equal to the number of RBs included in the CORESET (1110). Additionally, the DCI format scheduling the system information block may have unused reserved bits (15 bits).

[0305]

[0306] Referring to [Table 26], the DCI format for scheduling the system information block may include a Frequency domain resource assignment (FDRA) field that indicates scheduling information on the frequency axis. The length of the FDRA field is the number of RBs included in the CORESET ( ) may vary. Here, the length of the FDRA field is It could be.

[0307] The FDRA field is a single RB unit, the index of the starting RB (RB start =0,1,…, ) and the number of consecutive RBs (L RBs =1,2,…, ) can be directed. More specifically, the index of the starting RB (RB start ) and the number of consecutive RBs (L RBs ) can be interpreted by joint coding as shown in [Table 27]. In [Table 27] It could be.

[0308] Through the FDRA field, the terminal indicates the index of the starting RB of the PDSCH containing the system information block (RB start ) and the number of consecutive RBs (L RBs ) can be obtained. Here, the index of the starting RB (RB start ) may be equal to the lowest RB on the frequency axis of the CORESET. Here, the CORESET may be the CORESET in which the PDCCH that scheduled the PDSCH is received, or the CORESET indicated in the MIB.

[0309] The terminal can be configured with a separate active downlink bandwidth part. In this case, the terminal can also set the index of the starting RB of the PDSCH including the system information block (RB start ) may be equal to the lowest RB on the frequency axis of the CORESET. This may be applicable when the active downlink bandwidth includes the CORESET or the subcarrier spacing of the CORESET is equal to a portion of the active downlink bandwidth. If this condition is not satisfied, the terminal may set the index (RB) of the start RB of the PDSCH including the system information block. start ) may be equal to the lowest RB on the frequency axis in the active downlink bandwidth portion.

[0310]

[0311] According to the operation of the terminal described above, when the terminal is scheduled for a PDSCH including a system information block, the maximum number of RBs that the PDSCH can occupy is the number of RBs of the CORESET ( , which may be the same as . That is, the bandwidth occupied by the PDSCH including the system information block is 8.64 MHz ( ) to 17.28MHz ( ) may be limited. The above bandwidth may be referred to as the initial downlink bandwidth part (1150).

[0312] The initial downlink bandwidth portion may be smaller than the carrier bandwidth (1160) occupied by the downlink carrier or cell. For example, the initial downlink bandwidth portion may be 17.28 MHz (48 RBs, 30 kHz subcarrier spacing), but the carrier bandwidth may be 98.28 MHz (273 RBs, 30 kHz subcarrier spacing). Therefore, the bandwidth over which the PDSCH, including the system information block, is scheduled may be significantly smaller than the carrier bandwidth.

[0313] To ensure sufficient coverage, the PDSCH, including the system information block, may need to use a sufficiently low code rate. Therefore, increasing the number of resources transmitting the PDSCH can secure high coverage. The number of resources may be proportional to the number of RBs or OFDM symbols scheduled for the PDSCH. Since a UE must transmit a PDSCH within a single slot, it can be scheduled for up to 14 OFDM symbols. However, the UE can only be scheduled for up to 48 RBs, which is significantly less than the carrier bandwidth. Consequently, the UE's PDSCH coverage may be insufficient.

[0314] To reduce base station power consumption, it is desirable for the base station to transmit for the shortest possible time. Therefore, the base station can reduce the number of OFDM symbols containing the PDSCH to transmit the PDSCH, including the system information block, for the shortest possible time. In this case, increasing the number of RBs in the frequency domain can be considered to compensate for the reduced time resources. However, only a significantly smaller number of RBs are used for PDSCH transmission, including the system information block, than the number of RBs contained in the carriers used by the base station for downlink transmission. Therefore, this method may not be able to efficiently reduce base station power consumption, and a solution is needed to address this issue.

[0315] FIG. 12, FIG. 13, and FIG. 14 are diagrams illustrating a wideband CORESET set according to an embodiment of the present disclosure.

[0316] Referring to FIGS. 12, 13, and 14, the CORESET (1250, 1350, 1450) for which the terminal monitors the PDCCH may include more than 48 RBs. For example, the CORESET (1250, 1350, 1450) may be configured to include 96 to 192 RBs or may be configured to include an excess number of RBs. A CORESET including a larger number of RBs compared to a conventional CORESET may be referred to as a wideband CORESET. For convenience of description herein, the bandwidth determined as a wideband CORESET may be referred to as 100 MHz.

[0317] Referring to FIG. 12, a terminal may receive an SS / PBCH block (1200). The SS / PBCH block (1200) may include information indicating the location of the starting RB of a CORESET (1250) or the number of RBs. The terminal may monitor a PDCCH that schedules system information in the COREST (1250).

[0318] Referring to FIG. 12, a cell may include a normal UE whose bandwidth supported by the UE is relatively large and a narrowband UE whose bandwidth supported by the UE is relatively small. In the case of a normal UE, the bandwidth of the CORESET may be included in the bandwidth supported by the UE. Therefore, the normal UE can receive an OFDM symbol corresponding to the bandwidth of the CORESET (e.g., 100 MHz). In the case of a narrowband UE, the bandwidth supported by the UE may be smaller than the bandwidth of the CORESET. Therefore, the narrowband UE can receive only an OFDM symbol corresponding to a portion of the bandwidth of the CORESET (e.g., 100 MHz). Therefore, when using a wideband CORESET, the narrowband UE may not be able to receive a PDCCH with the bandwidth of the CORESET (e.g., 100 MHz).

[0319] Referring to Figures 13 and 14, a base station can communicate with a terminal using multiple bandwidths. According to one embodiment of the present disclosure, the base station can communicate with the terminal using a single mode (wideband mode). Accordingly, the base station can increase throughput by providing the terminal with a large number of RBs. For example, the base station can utilize a 100 MHz bandwidth when communicating with the terminal.

[0320] According to one embodiment of the present disclosure, in another mode (narrowband mode), a base station can perform narrowband communication with a terminal. Accordingly, the base station can communicate with the terminal using a small number of RBs, thereby reducing power consumption of both the base station and the terminal. For example, the base station can utilize a 10MHz bandwidth when communicating with the terminal. Here, the narrowband mode can be referred to as a network energy saving mode.

[0321] Referring to FIG. 13, when a base station uses a wideband mode, the active bandwidth of the base station may include a wideband CORESET. That is, the base station may transmit a PDCCH using a CORESET included within the active bandwidth. For example, time-frequency resources included in the PDCCH may be distributed within the bandwidth of the CORESET. This may be referred to as interleaving. Referring to FIG. 13, a first time-frequency resource (1370) and a second time-frequency resource (1371) included in the PDCCH may be included within the active bandwidth of the base station. Accordingly, the base station may transmit a PDCCH using the first time-frequency resource (1370) and the second time-frequency resource (1371).

[0322] Referring to FIG. 14, when the base station uses a narrowband mode, the active bandwidth of the base station (e.g., 10 MHz) cannot include a wideband CORESET. Therefore, the base station may not be able to transmit a PDCCH with the CORESET. More specifically, the first time-frequency resource (1470) included in the PDCCH is included in the active bandwidth of the base station (e.g., 10 MHz), but the second time-frequency resource (1471) may not be included in the active bandwidth of the base station (e.g., 10 MHz). Therefore, the base station may not be able to transmit a PDCCH composed of the first time-frequency resource (1470) and the second time-frequency resource (1471) to the terminal. Therefore, the base station may need to reduce the bandwidth of the CORESET through separate signaling to the terminal. The above separate signaling may be transmitted via the SS / PBCH block (1400) or via a higher layer signal (e.g., an RRC signal or a MAC-CE signal). This separate signaling must be transmitted to all terminals within the cell, thus incurring significant overhead.

[0323] The base station can configure a first CORESET (a CORESET with a bandwidth of 100 MHz) for a terminal for a wideband mode and a second CORESET (a CORESET with a bandwidth of 10 MHz) for a narrowband mode. In the wideband mode, the PDCCH can be transmitted using the first CORESET corresponding to the wideband mode, and in the narrowband mode, the PDCCH can be transmitted using the second CORESET corresponding to the narrowband mode. However, this method may require that the terminal be able to receive two CORESET settings. If the terminal can receive only one CORESET setting at most, two CORESETs may not be configured for such a terminal.

[0324] FIG. 15 is a diagram illustrating a sub-CORESET set according to an embodiment of the present disclosure.

[0325] In one embodiment of the present disclosure, a terminal may receive a single CORESET configuration from a base station. The single CORESET configuration may include multiple sub-CORESET configurations. Each sub-CORESET configuration may include different frequency axis allocation information.

[0326] For example, referring to FIG. 15(a), a CORESET (1550a) may include a first sub-CORESET and a second sub-CORESET. Here, the first sub-CORESET may include first frequency axis allocation information, and the second sub-CORESET may include second frequency axis allocation information. Here, the first sub-CORESET may be a low bandwidth (e.g., 10 MHz) for a narrowband mode, and the second sub-CORESET may be a high bandwidth (e.g., 90 MHz) for a wideband mode. Here, the first sub-CORESET and the second sub-CORESET may not overlap in the frequency axis.

[0327] More specifically, the signaling by which a terminal receives a CORESET including sub-CORESETs from a base station may be as follows.

[0328] The terminal can receive frequency axis allocation information of CORESET. This can be configured as a bitmap, and each bit can correspond to six consecutive RBs. The length of the bitmap can be 45 bits, and the least significant bit (LSB) can correspond to the six lowest RBs in the frequency axis. Here, the lowest RB in the frequency axis can be the lowest RB of the downlink active bandwidth (BWP).

[0329] In one method, the terminal can receive frequency axis allocation information of the first sub-CORESET. This can be set as a bitmap, and each bit can correspond to six consecutive RBs. The length of the bitmap can be 45 bits, and the least significant bit (LSB) can correspond to the six lowest RBs in the frequency axis. Here, the lowest RB in the frequency axis can be the lowest RB of the downlink active BWP. The six RBs for which the bitmap corresponds to '1' in the first sub-CORESET can also be indicated as '1' in the bitmap of the frequency axis allocation information of the CORESET. Conversely, if the six RBs for which the bitmap corresponds to '1' in the first sub-CORESET are indicated as '0' in the bitmap of the frequency axis allocation information of the CORESET, the terminal can determine this as a miss-configuration. The terminal may determine RBs that are set to CORESET but are not set to the first sub-CORESET as the second sub-CORESET. That is, if 6 RBs whose bitmap corresponds to '0' in the first sub-CORESET are indicated as '1' in the bitmap of the frequency axis allocation information of the CORESET, the 6 RBs may be included in the second sub-CORESET.

[0330] In another way, the terminal can receive information about the frequency axis of the first sub-CORESET within the configuration of the CORESET. More specifically, the information about the frequency axis of the first sub-CORESET can include a value corresponding to the start frequency and a value corresponding to the end frequency of the first sub-CORESET.

[0331] Here, the value corresponding to the start frequency may be the index of the start RB. Here, the value corresponding to the last frequency may be the index of the last RB. That is, the terminal may be configured with the index of the start RB and the index of the last RB of the first sub-CORESET using information on the frequency axis of the first sub-CORESET. Based on the frequency axis allocation information of the CORESET, the terminal may determine the RBs included in the CORESET determined from the start RB index to the last RB index as the first sub-CORESET, and may determine the other RBs as the second sub-CORESET.

[0332] Here, the value corresponding to the start frequency may be the index of the start RB set. Here, the value corresponding to the last frequency may be the index of the last RB set. Here, the RB set may be a set of six consecutive RBs, and may be six RBs corresponding to each bit of the bitmap in the frequency axis allocation information of the CORESET. That is, the terminal may receive the index of the start RB set and the index of the last RB set of the first sub-CORESET as information on the frequency axis of the first sub-CORESET. Based on the frequency axis allocation information of the CORESET, the terminal may determine the RBs included in the CORESET determined from the start RB set index to the last RB set index as the first sub-CORESET, and may determine the other RBs as the second sub-CORESET.

[0333] As another example, referring to FIG. 15(b), a CORESET (1550b) may include a first sub-CORESET and a second sub-CORESET. Here, the first sub-CORESET may include first frequency axis allocation information, and the second sub-CORESET may include second frequency axis allocation information. Here, the first sub-CORESET may be a low bandwidth (e.g., 10 MHz) for a narrowband mode, and the second sub-CORESET may be a high bandwidth (e.g., 100 MHz) for a wideband mode. Here, the first sub-CORESET and the second sub-CORESET may overlap in the frequency axis.

[0334] More specifically, the signaling that the terminal has received from the base station a CORESET including sub-CORESETs may be as follows.

[0335] The terminal can receive frequency axis allocation information of CORESET. This can be configured as a bitmap, and each bit can correspond to six consecutive RBs. The length of the bitmap can be 45 bits, and the least significant bit (LSB) can correspond to the six lowest RBs in the frequency axis. Here, the lowest RB in the frequency axis can be the lowest RB of the downlink active bandwidth (BWP).

[0336] In one method, the terminal can receive frequency axis allocation information of the first sub-CORESET. This can be set as a bitmap, and each bit can correspond to six consecutive RBs. The length of the bitmap can be 45 bits, and the least significant bit (LSB) can correspond to the six lowest RBs in the frequency axis. Here, the lowest RB in the frequency axis can be the lowest RB of the downlink active BWP. The six RBs for which the bitmap corresponds to '1' in the first sub-CORESET can also be indicated as '1' in the bitmap of the frequency axis allocation information of the CORESET. Conversely, if the six RBs for which the bitmap corresponds to '1' in the first sub-CORESET are indicated as '0' in the bitmap of the frequency axis allocation information of the CORESET, the terminal can determine this as a miss-configuration. The terminal can receive frequency axis allocation information of the second sub-CORESET. This can be set as a bitmap, and each bit can correspond to six consecutive RBs. The length of the bitmap can be 45 bits, and the least significant bit (LSB) can correspond to the six lowest RBs in the frequency axis. Here, the lowest RB in the frequency axis can be the lowest RB of the downlink active BWP. The six RBs for which the bitmap corresponds to '1' in the second sub-CORESET can also be indicated as '1' in the bitmap of the frequency axis allocation information of the CORESET. Conversely, if the six RBs for which the bitmap corresponds to '1' in the second sub-CORESET are indicated as '0' in the bitmap of the frequency axis allocation information of the CORESET, the terminal can determine this as a miss-configuration.

[0337] In the example described above, the terminal can receive a bitmap corresponding to frequency axis allocation information of the CORESET, a bitmap corresponding to the first sub-CORESET, and / or a bitmap corresponding to the second sub-CORSET.

[0338] As another example, the terminal may not set a bitmap corresponding to the frequency axis allocation information of the CORESET. In this case, the RBs included in the CORESET may be composed of RBs included in the first sub-CORESET and RBs included in the second sub-CORESET.

[0339] In another way, the terminal can receive information about the frequency axis of the first sub-CORESET and information about the frequency axis of the second sub-CORESET within the configuration of the CORESET. More specifically, the information about the frequency axis of the first sub-CORESET can include a value corresponding to a start frequency and a value corresponding to a last frequency of the first sub-CORESET, and the information about the frequency axis of the second sub-CORESET can include a value corresponding to a start frequency and a value corresponding to a last frequency of the second sub-CORESET.

[0340] Here, the value corresponding to the start frequency may be the index of the start RB. Here, the value corresponding to the last frequency may be the index of the last RB. That is, the terminal can be set the index of the start RB and the index of the last RB of the first sub-CORESET with information on the frequency axis of the first sub-CORESET. The terminal can determine the RBs included from the start RB index to the last RB index among the RBs included in the CORESET determined based on the frequency axis allocation information of the CORESET as the first sub-CORESET. The terminal can be set the index of the start RB and the index of the last RB of the second sub-CORESET with information on the frequency axis of the second sub-CORESET. The terminal can determine the RBs included from the start RB index to the last RB index among the RBs included in the CORESET determined based on the frequency axis allocation information of the CORESET as the second sub-CORESET.

[0341] Here, the value corresponding to the start frequency may be the index of the start RB set. Here, the value corresponding to the last frequency may be the index of the last RB set. Here, the RB set may be a set of six consecutive RBs, and may be six RBs corresponding to each bit of the bitmap in the frequency axis allocation information of the CORESET. That is, the terminal may receive the index of the start RB set and the index of the last RB set of the first sub-CORESET with information on the frequency axis of the first sub-CORESET. The terminal may determine the RBs included in the CORESET determined based on the frequency axis allocation information of the CORESET from the start RB set index to the last RB set index as the first sub-CORESET. And, the other RBs may be determined as the second sub-CORESET. The terminal may receive the index of the start RB set and the index of the last RB set of the second sub-CORESET with information on the frequency axis of the second sub-CORESET. The terminal can determine the RBs included in the CORESET determined based on the frequency axis allocation information of the CORESET from the start RB set index to the last RB set index as the second sub-CORESET.

[0342] FIG. 16 is a diagram illustrating an interleaver configuration corresponding to a sub-CORESET according to an embodiment of the present disclosure. In an embodiment of the present disclosure, a terminal may receive an interleaver configuration corresponding to each sub-CORESET from a base station. For example, a first sub-CORESET may not be configured with interleaving (non-interleaving), and a second sub-CORESET may be configured with interleaving. In another example, a first interleaving may be configured for a first sub-CORESET, and a second interleaving may be configured for a second sub-CORESET. Here, the interleaving configuration may include at least one of the following parameters:

[0343] - REG bundle size (L)

[0344] - Interleaver Size (R)

[0345] - Shift Index (n shift )

[0346] Depending on the above parameters, the interleaver can be performed as follows.

[0347] The k REG bundling size (L) is set to the interleaving setting corresponding to the k sub-CORESET. k ), the k interleaverSize (R k ), and / or the kth shift index (n shift,k ) can be set.

[0348] The terminal may index the REGs included in the kth sub-CORESET in ascending order from 0. Here, REG 0 may be composed of 12 REs located in the first OFDM symbol of the lowest frequency of the kth sub-CORESET. The terminal may index the REGs included in the kth sub-CORESET first in ascending order of time order and then in ascending order of frequency order.

[0349] The terminal is L k Based on the value, REGs {i*L} that belong to REG bundle i of the kth sub-CORESET k , i*L k +1,…, i*L k +L k -1} can be determined. Here, i=0,1,…, -It could be 1. Is It could be. Here is the number of symbols occupied by CORESET, may be the number of RBs included in the k sub-CORESET.

[0350] CCE j of my k sub-CORESET is REG bundles {f(6j / L k ), f(6j / L k +1),…, f(6j / L k +6 / L-1)} can be constructed. Here, f(x) is as follows.

[0351] - If interleaving is not set in the k sub-CORESET (non-interleaving), f(x)=x and L k =6.

[0352] - If interleaving is set in the k sub-CORESET, f(x) can be determined by [Mathematical Formula 3].

[0353]

[0354]

[0355]

[0356]

[0357]

[0358] Referring to FIG. 16, a terminal may receive a CORESET configuration. Depending on the CORESET configuration, CORESET (1600, 1610) may occupy 100 MHz. The CORESET configuration may include a first sub-CORESET configuration and a second sub-CORESET configuration. Here, the first sub-CORESET configuration may be a narrowband (e.g., 10 MHz), and the second sub-CORESET configuration may be a wideband (e.g., 90 MHz). Each sub-CORESET configuration may include an interleaving configuration corresponding to each sub-CORESET.

[0359] Referring to FIG. 16, REGs, REG bundles, and / or CCEs included in a CORESET (1600) may be interleaved, thereby generating an interleaved CORESET (1610). Here, REGs, REG bundles, and / or CCEs included in a first sub-CORESET may be interleaved by a first interleaving setting. Here, the interleaving may be performed within a bandwidth of the first sub-CORESET. REGs, REG bundles, and / or CCEs included in a second sub-CORESET may be interleaved by a second interleaving setting. Here, the interleaving may be performed within a bandwidth of the second sub-CORESET. Interleaving of the first sub-CORESET and interleaving of the second sub-CORESET may be performed independently of each other.

[0360] Referring to FIG. 16, REG bundles (1652, 1653) included in the first sub-CORESET of the CORESET (1600) before interleaving is performed can be interleaved within the bandwidth of the first sub-CORESET. REG bundles (1652, 1653) of the CORESET (1600) before interleaving is performed can correspond to REG bundles (1662, 1663) in the interleaved CORESET (1610). Here, REG bundles (1662, 1663) can be distributed and arranged within the bandwidth of the first sub-CORESET.

[0361] Referring to FIG. 16, REG bundles (1650, 1651) included in the second sub-CORESET of the CORESET (1600) before interleaving is performed can be interleaved within the bandwidth of the second sub-CORESET. REG bundles (1650, 1651) of the CORESET (1600) before interleaving is performed can correspond to REG bundles (1660, 1661) in the interleaved CORESET (1610). Here, REG bundles (1660, 1661) can be distributed and arranged within the bandwidth of the second sub-CORESET.

[0362] A terminal may receive a search space configuration from a base station. The search space configuration may include at least one of an index of a corresponding CORESET, information on PDCCH candidates to be monitored in the CORESET, information on a time domain for monitoring the PDCCH, information on the type of search space (wherein the type may include a common search space or a terminal-specific search space), and information on the type of DCI format included in the PDCCH.

[0363] Information about PDCCH candidates to be monitored in CORESET may be as follows.

[0364] - aggregationLevel1, the number of PDCCH candidates at aggregation level 1.

[0365] - aggregationLevel2, the number of PDCCH candidates with aggregation level 2,

[0366] - aggregationLevel4, the number of PDCCH candidates with aggregation level 4.

[0367] - aggregationLevel8, the number of PDCCH candidates with aggregation level 8.

[0368] - aggregationLevel16, the number of PDCCH candidates with aggregation level 16

[0369] Here, aggregationLevel1, aggregationLevel2, aggregationLevel4, aggregationLevel8, and aggregationLevel16 can each have one of the values ​​1, 2, 3, 4, 5, 6, and 8.

[0370] For a search space s associated with CORESET p, a PDCCH candidate ( The indices of the CCEs included in can be as in [Mathematical Formula 4]. Here, the terminal is a slot PDCCH candidates can be monitored in . PDCCH candidates are n CI It may be for the corresponding cell.

[0371]

[0372] Here, if the search space is a common search space, am.

[0373] Here, if the search space is a terminal-specific search space, , for p such that p mod 3 = 0, , for p such that p mod 3 = 1, , for p mod 3 = 2, , and It could be.

[0374] Here, is the number of CCEs included in CORESET p.

[0375] Here, And, is n CI It can be a value corresponding to the aggregation level L among aggregationLevel1, aggregationLevel2, aggregationLevel4, aggregationLevel8, and aggregationLevel16 of the corresponding cell.

[0376] Here, if the search space is a common search space,

[0377] Here, if the search space is a terminal-specific search space, is all n CI Corresponding to values It can be the maximum value among them.

[0378] Here, can be a C-RNTI value.

[0379] According to the present disclosure, the search space configuration may include information about PDCCH candidates to be monitored for each sub-CORESET. For example, if the CORESET corresponding to the search space configuration includes two sub-CORESETs, the search space configuration may include information about PDCCH candidates corresponding to the first sub-CORESET and information about PDCCH candidates corresponding to the second sub-CORESET. More specifically, the terminal may receive the following information about the PDCCH candidates corresponding to the first sub-CORESET.

[0380] - aggregationLevel1_subCORESET1, the number of PDCCH candidates of aggregation level 1 of the first sub-CORESET,

[0381] - aggregationLevel2_subCORESET1, the number of PDCCH candidates of aggregation level 2 of the first sub-CORESET,

[0382] - aggregationLevel4_subCORESET1, the number of PDCCH candidates of aggregation level 4 of the first sub-CORESET,

[0383] - aggregationLevel8_subCORESET1, the number of PDCCH candidates of aggregation level 8 of the first sub-CORESET,

[0384] - aggregationLevel16_subCORESET1, the number of PDCCH candidates with aggregation level 16 of the first sub-CORESET

[0385] Here, aggregationLevel1_subCORESET1, aggregationLevel2_subCORESET1, aggregationLevel4_subCORESET1, aggregationLevel8_subCORESET1, and aggregationLevel16_subCORESET1 can each have one of the values ​​1, 2, 3, 4, 5, 6, and 8.

[0386] The terminal can be configured with the following information about the PDCCH candidate corresponding to the second sub-CORESET.

[0387] - aggregationLevel1_subCORESET2, the number of PDCCH candidates of aggregation level 1 of the second sub-CORESET,

[0388] - aggregationLevel2_subCORESET2, the number of PDCCH candidates of aggregation level 2 of the second sub-CORESET,

[0389] - aggregationLevel4_subCORESET2, the number of PDCCH candidates of aggregation level 4 of the second sub-CORESET,

[0390] - aggreg-ationLevel8_subCORESET2, the number of PDCCH candidates of aggregation level 8 of the second sub-CORESET,

[0391] - aggregationLevel16_subCORESET2, the number of PDCCH candidates with aggregation level 16 of the second sub-CORESET

[0392] Here, aggregationLevel1_subCORESET2, aggregationLevel2_subCORESET2, aggregationLevel4_subCORESET2, aggregationLevel8_subCORESET2, and aggregationLevel16_subCORESET2 can each have one of the values ​​1, 2, 3, 4, 5, 6, and 8.

[0393] Here, aggregationLevel1_subCORESET1 + aggregationLevel1_subCORESET2, aggregationLevel2_subCORESET1 + aggregationLevel2_subCORESET2, aggregationLevel4_subCORESET1 + aggregationLevel4_subCORESET2, aggregationLevel8_subCORESET1 + aggregationLevel8_subCORESET2 can have one of the values ​​1,2,3,4,5,6,8.

[0394] The terminal can determine a PDCCH candidate for each sub-CORESET.

[0395] For a search space s associated with CORESET p, a PDCCH candidate ( ) with aggregation level L in sub-CORESET k The indices of the CCEs included in can be as in [Mathematical Formula 5]. Here, the terminal is a slot PDCCH candidates can be monitored in . PDCCH candidates are n CIIt may be for a cell corresponding to . Here, the indices of the CCEs included in the sub-CORESET can be assigned to each sub-CORESET.

[0396]

[0397] Here, is the number of CCEs included in the kth sub-CORESET of CORESET p.

[0398] Here, And, is n CI It can be a value corresponding to the aggregation level L among aggregationLevel1_subCORESETk, aggregationLevel2_subCORESETk, aggregationLevel4_subCORESETk, aggregationLevel8_subCORESETk, and aggregationLevel16_subCORESETk of the corresponding cell.

[0399] Here, if the search space is a common search space,

[0400] Here, if the search space is a terminal-specific search space, is all n CI Corresponding to values It can be the maximum value among them.

[0401] According to the present disclosure, a search space configuration may include information about PDCCH candidates in a CORESET. For example, if a CORESET corresponding to a search space configuration includes two sub-CORESETs, the number of PDCCH candidates that a terminal should monitor in the CORESET may be set as aggregationLevel1, aggregationLevel2, aggregationLevel4, aggregationLevel8, and aggregationLevel16. The terminal can determine the number of PDCCH candidates that it should monitor in each sub-CORESET from the above values.

[0402] In one embodiment, the terminal may include the number of CCEs included in the first sub-CORESET ( ) and the number of CCEs included in the second sub-CORESET ( ) can be used to determine the number of PDCCH candidates to be monitored in each sub-CORESET.

[0403] Here, if aggregationLevelL_subCORESETk is determined as the number of PDCCH candidates with aggregation level L that must be monitored in the kth sub-CORESET, aggregationLevelL_subCORESETk can be determined by [Mathematical Formula 6].

[0404]

[0405] X here k is the number of CCEs included in the first sub-CORESET ( ) and the number of CCEs included in the second sub-CORESET ( ) can be determined based on. For example, X k = can be. Here, ceil (rounding up function) can be replaced with floor (rounding down function) or round (rounding function). Here, aggregationLevelL_subCORESET1 can be determined through [Mathematical Formula 6], and can be determined as aggregationLevelL_subCORESET2 = aggregationLevelL - aggregationLevelL_subCORESET1.

[0406] Figure 17 is a flowchart illustrating the operation of a terminal according to the present disclosure.

[0407] In step 1700, the terminal may receive CORESET configuration information from the base station via a higher layer signal (e.g., an RRC signal). Here, the CORESET configuration may include sub-CORESET configuration information. Here, the sub-CORESET configuration information may include frequency axis configuration information of each sub-CORESET and / or interleaving configuration information of each sub-CORESET.

[0408] In step 1710, the terminal may interleave REGs, REG bundles, and / or CCEs of the sub-CORESET based on the interleaving configuration information of the sub-CORESET. Here, interleaving may be performed within the bandwidth of the sub-CORESET. After interleaving, the terminal may determine PDCCH candidates for each sub-CORESET. This can be determined using [Mathematical Formula 5].

[0409] In step 1720, the terminal can determine the number of PDCCH candidates to be monitored in the sub-CORESET. The sub-CORESET configuration information received in step 1700 may include the number of PDCCH candidates to be monitored in the sub-CORESET. Alternatively, the CORESET configuration information received in step 1700 may include the number of PDCCH candidates to be monitored in the CORESET. The terminal can obtain the number of PDCCH candidates to be monitored in each sub-CORESET from the number of PDCCH candidates to be monitored in the CORESET.

[0410] In step 1730, the terminal may blindly decode PDCCH candidates in the CORESET. Here, the terminal may perform blind decoding in each sub-CORESET based on the number of PDCCH candidates corresponding to each sub-CORESET.

[0411] According to the above-described embodiment, the base station can transmit the PDCCH as a PDCCH candidate of the first sub-CORESET (narrowband) or a PDCCH candidate of the second sub-CORESET (wideband). For example, the base station can transmit the PDCCH candidate as the first sub-CORESET (narrowband) to save network energy. Since the terminal cannot know which PDCCH candidates the base station uses to transmit the PDCCH, it must monitor both the PDCCH candidate of the first sub-CORESET (narrowband) and the PDCCH candidate of the second sub-CORESET (wideband). Therefore, the terminal may monitor unnecessary PDCCH candidates of the second sub-CORESET (wideband), which may cause energy waste. A method for solving this is described below.

[0412] FIG. 18 is a diagram illustrating PDCCH candidate monitoring corresponding to a sub-CORESET according to an embodiment of the present disclosure.

[0413] According to one embodiment of the present disclosure, a terminal may receive an instruction from a base station regarding whether to monitor PDCCH candidates corresponding to each sub-CORESET. The terminal may determine whether to monitor PDCCH candidates corresponding to the sub-CORESET based on the instruction received from the base station.

[0414] Referring to FIG. 18, a CORESET may include a first sub-CORESET and a second sub-CORESET. A terminal may receive an indicator (1800) from a base station. The indicator may indicate termination of monitoring of a PDCCH candidate corresponding to the second sub-CORESET. That is, when the terminal receives the indicator (1800), the terminal may no longer monitor the PDCCH candidate in the second sub-CORESET.

[0415] The terminal may receive an indicator (1810) from the base station. The indicator may instruct the resumption of monitoring of the PDCCH candidate corresponding to the second sub-CORESET. That is, when the terminal receives the indicator (1810), the terminal may perform monitoring of the PDCCH candidate in the second sub-CORESET.

[0416] A terminal may receive information about a time interval (hereinafter, time information) from an indicator. The time information may include a start time and an end time. The terminal may perform the instructions of the indicator during the interval corresponding to the time information. For example, the terminal may receive an indicator (1800), and the indicator may include time information about a specific time interval. The terminal may not monitor a PDCCH candidate in the second sub-CORESET within the specific time interval. However, the terminal may monitor a PDCCH candidate in the second sub-CORESET before or after the specific time interval.

[0417] The terminal can determine when an indicator is applied. This can be determined based on the time at which the HARQ-ACK information corresponding to the indicator is transmitted to the base station.

[0418] If the indicator is transmitted on the downlink physical control channel (PDCCH), the terminal can transmit a HARQ-ACK for the PDCCH to the base station. After transmitting the HARQ-ACK, the terminal can perform a terminal operation according to the indicator. For example, if the terminal receives the indicator (1800) through the PDCCH, the PDCCH candidates of the second sub-CORESET may not be monitored after transmitting the HARQ-ACK of the PDCCH to the base station.

[0419] If the indicator is transmitted via MAC-CE, the terminal can transmit a HARQ-ACK for the PDSCH including the MAC-CE to the base station. After transmitting the HARQ-ACK, the terminal can perform a terminal operation according to the indicator. For example, if the terminal receives the indicator (1800) via MAC-CE, the PDCCH candidates of the second sub-CORESET may not be monitored after transmitting the HARQ-ACK of the PDSCH including the MAC-CE to the base station.

[0420] Referring to FIG. 18, when the terminal does not monitor the PDCCH in the second sub-CORESET, the terminal may additionally apply the number of PDCCH candidates set in the second sub-CORESET to the first sub-CORESET. For example, the number of PDCCH candidates monitored in the first sub-CORESET according to the first sub-CORESET configuration and the second sub-CORESET configuration may be referred to as aggregationLevelL_subCORESET1 (aggregation level L), and the number of PDCCH candidates monitored in the second sub-CORESET may be referred to as aggregationLevelL_subCORESET2 (aggregation level L). Here, when the terminal does not monitor the PDCCH in the second sub-CORESET, the terminal may monitor aggregationLevelL_subCORESET1 PDCCH candidates in the first sub-CORESET. Furthermore, the terminal can monitor aggregationLevelL_subCORESET1 + aggregationLevelL_subCORESET2 PDCCH candidates in the first sub-CORESET. Accordingly, the terminal can monitor the same number of PDCCH candidates even when monitoring of the sub-CORESET is terminated.

[0421] FIG. 19 is a diagram illustrating the structure of a terminal in a wireless communication system according to an embodiment of the present disclosure.

[0422] Referring to FIG. 19, the terminal may include a transceiver, which refers to a terminal receiving unit (1900) and a terminal transmitting unit (1910), a memory (not shown), and a terminal processing unit (1905, or a terminal control unit or processor). Depending on the communication method of the terminal described above, the transceiver units (1900, 1910), the memory, and the terminal processing unit (1905) of the terminal may operate. However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more or fewer components than the components described above. In addition, the transceiver unit, the memory, and the processor may be implemented in the form of a single chip.

[0423] A transceiver unit can transmit and receive signals with a base station or other terminals. The signals may include control information and data. To this end, the transceiver unit may include an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and down-converts the frequency of a received signal. However, this is only one embodiment of the transceiver unit, and the components of the transceiver unit are not limited to the RF transmitter and RF receiver.

[0424] Additionally, the transceiver can receive a signal through a wireless channel and output it to the processor, and transmit a signal output from the processor through the wireless channel.

[0425] Memory can store programs and data necessary for the terminal's operation. Furthermore, memory can store control information or data included in signals transmitted and received by the terminal. Memory can be comprised of a storage medium, such as ROM, RAM, a hard disk, CD-ROM, or DVD, or a combination of such storage media. Furthermore, there can be multiple memories.

[0426] Additionally, the processor can control a series of processes to enable the terminal to operate according to the aforementioned embodiments. For example, the processor can receive DCI consisting of two layers and control components of the terminal to simultaneously receive multiple PDSCHs. There may be multiple processors, and the processors can perform terminal component control operations by executing programs stored in memory.

[0427] FIG. 20 is a diagram illustrating the structure of a base station in a wireless communication system according to an embodiment of the present disclosure.

[0428] Referring to FIG. 20, the base station may include a transceiver, which refers to a base station receiver (2000) and a base station transmitter (2010), a memory (not shown), and a base station processor (2005, or a base station control unit or processor). Depending on the communication method of the base station described above, the transceiver (2000, 2010), the memory, and the base station processor (2005) of the base station may operate. However, the components of the base station are not limited to the examples described above. For example, the base station may include more or fewer components than the components described above. In addition, the transceiver, the memory, and the processor may be implemented in the form of a single chip.

[0429] The transceiver unit can transmit and receive signals with a terminal or another base station. The signals may include control information and data. To this end, the transceiver unit may include an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and down-converts the frequency of a received signal. However, this is only one embodiment of the transceiver unit, and the components of the transceiver unit are not limited to the RF transmitter and RF receiver.

[0430] Additionally, the transceiver can receive a signal through a wireless channel and output it to the processor, and transmit the signal output from the processor through the wireless channel.

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

[0432] The processor 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 can configure two layers of DCIs containing allocation information for multiple PDSCHs and control each component of the base station to transmit them. There may be multiple processors, and the processors can perform component control operations of the base station by executing programs stored in memory.

[0433] The 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.

[0434] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. The 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 the present disclosure.

[0435] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage device, compact disc ROM (CD-ROM), digital versatile discs (DVDs) or other forms of optical storage device, magnetic cassette. Or, they may be stored in a memory configured as a combination of some or all of these. In addition, each configuration memory may be included in multiple numbers.

[0436] Additionally, the program may be stored on an attachable storage device that is accessible via a communication network, such as the Internet, an intranet, a local area network (LAN), a wide local area network (WLAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device performing an embodiment of the present disclosure.

[0437] In the specific embodiments of the present disclosure described above, components included in the invention are expressed in the singular or plural form, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in the plural form may be composed of singular elements, or components expressed in the singular form may be composed of plural elements.

[0438] Meanwhile, the embodiments of the present disclosure disclosed in this specification and drawings are only specific examples to easily explain the technical contents of the present disclosure and help understand the present disclosure, and are not intended to limit the scope of the present disclosure. In other words, it will be apparent to those skilled in the art that other modifications based on the technical idea of ​​the present disclosure are possible. In addition, the above-mentioned embodiments can be combined and operated with each other as needed. For example, parts of one embodiment of the present disclosure and parts of another embodiment can be combined with each other to operate a base station and a terminal. For example, parts of the first embodiment and the second embodiment of the present disclosure can be combined with each other to operate a base station and a terminal. In addition, although the above-mentioned embodiments have been presented based on an FDD LTE system, other modifications based on the technical idea of ​​the above-mentioned embodiments can be implemented with other systems such as a TDD LTE system, 5G, or NR system.

[0439] Meanwhile, the order of description in the drawings explaining the method of the present invention does not necessarily correspond to the order of execution, and the order of precedence may be changed or executed in parallel.

[0440] Alternatively, the drawings illustrating the method of the present invention may omit some components and include only some components within a scope that does not harm the essence of the present invention.

[0441] In addition, the method of the present invention may be implemented by combining some or all of the contents included in each embodiment within a scope that does not harm the essence of the invention.

[0442] In the specific embodiments of the present invention described above, components included in the invention are expressed in the singular or plural form depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present invention is not limited to singular or plural components. Even components expressed in the plural form may be composed of singular elements, or even components expressed in the singular form may be composed of plural elements.

[0443] Meanwhile, although specific embodiments have been described in the detailed description of the present invention, it is obvious that various modifications are possible without departing from the scope of the present invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be determined not only by the scope of the following claims but also by equivalents of the scope of the claims. In other words, it will be apparent to those skilled in the art that other modifications based on the technical idea of ​​the present disclosure are possible. In addition, each of the above embodiments can be combined and operated with each other as needed. For example, parts of the methods proposed in the present disclosure can be combined with each other to operate a base station and a terminal. In addition, although the above embodiments have been presented based on a 5G, NR system, other modifications based on the technical idea of ​​the above embodiments can be implemented with other systems such as LTE, LTE-A, and LTE-A-Pro systems.

Claims

1. In a method performed by a terminal of a wireless communication system, A step of receiving CORESET (control resource set) configuration information from a base station; A step of identifying a first sub-CORESET and a second sub-CORESET based on the CORESET setting information, wherein the bandwidth of the first sub-CORESET is narrower than the bandwidth of the second sub-CORESET; A step of determining at least one PDCCH (physical downlink control channel) candidate for the first sub-CORESET and the second sub-CORESET; and A method characterized by comprising the step of performing blind decoding on at least one PDCCH candidate determined above.

2. In paragraph 1, The above CORESET setting information is: A bitmap indicating the frequency resources of each sub-CORESET; or A method characterized in that it includes a start RB (Resource Block) index and a last RB index of each sub CORESET.

3. In paragraph 1, The above CORESET configuration information includes interleaving-related information for each sub-CORESET, A method characterized in that the interleaving-related information includes at least one of information on a REG (Resource Element Group) bundle size, information on an interleaver size, and information on a shift index.

4. In paragraph 1, The above CORESET setting information is: A method characterized by including information indicating the number of PDCCH candidates corresponding to an aggregation level for each sub-CORESET.

5. In a method performed by a base station of a wireless communication system, A step of identifying a first sub CORESET (control resource set) and a second sub CORESET, wherein the bandwidth of the first sub CORESET is narrower than the bandwidth of the second sub CORESET; A step of generating CORESET setting information based on the above identification result; A step of transmitting the above CORESET setting information to a terminal; and A method comprising a step of transmitting at least one physical downlink control channel (PDCCH) to the terminal based on the first sub-CORESET and the second sub-CORESET.

6. In paragraph 1, The above CORESET setting information is: A bitmap indicating the frequency resources of each sub-CORESET; or A method characterized in that it includes a start RB (Resource Block) index and a last RB index of each sub CORESET.

7. In paragraph 1, The above CORESET configuration information includes interleaving-related information for each sub-CORESET, A method characterized in that the interleaving-related information includes at least one of information on a REG (Resource Element Group) bundle size, information on an interleaver size, and information on a shift index.

8. In paragraph 1, The above CORESET setting information is: A method characterized by including information indicating the number of PDCCH candidates corresponding to an aggregation level for each sub-CORESET.

9. In the terminal of a wireless communication system, At least one transceiver; At least one processor communicatively connected to said at least one transceiver; and Communicably connected to at least one processor, and executable individually or in any combination of said at least one processor, such that said terminal, Receive CORESET (control resource set) configuration information from the base station, A step of identifying a first sub-CORESET and a second sub-CORESET based on the CORESET setting information, wherein the bandwidth of the first sub-CORESET is narrower than the bandwidth of the second sub-CORESET, Determine at least one PDCCH (physical downlink control channel) candidate for the first sub-CORESET and the second sub-CORESET, A terminal characterized by performing blind decoding on at least one PDCCH candidate determined above.

10. In paragraph 9, The above CORESET setting information is: A bitmap indicating the frequency resources of each sub-CORESET; or A terminal characterized by including a start RB (Resource Block) index and a last RB index of each sub CORESET.

11. In paragraph 9, The above CORESET configuration information includes interleaving-related information for each sub-CORESET, A terminal characterized in that the interleaving-related information includes at least one of information on a REG (Resource Element Group) bundle size, information on an interleaver size, and information on a shift index.

12. In paragraph 9, The above CORESET setting information is: A terminal characterized by including information indicating the number of PDCCH candidates corresponding to an aggregation level for each sub-CORESET.

13. In a base station of a wireless communication system, At least one transceiver; At least one processor communicatively connected to said at least one transceiver; and Communicably connected to at least one processor, and executable individually or in any combination of said at least one processor, such that said base station, Identifying a first sub CORESET (control resource set) and a second sub CORESET, characterized in that the bandwidth of the first sub CORESET is narrower than the bandwidth of the second sub CORESET, Generate CORESET setting information based on the above identification results, Transmit the above CORESET setting information to the terminal, A base station characterized in that it transmits at least one PDCCH (physical downlink control channel) to the terminal based on the first sub-CORESET and the second sub-CORESET.

14. In paragraph 13, The above CORESET setting information is: A bitmap indicating the frequency resources of each sub-CORESET; or A base station characterized by including a start RB (Resource Block) index and a last RB index of each sub CORESET.

15. In paragraph 13, The above CORESET configuration information includes interleaving-related information for each sub-CORESET or information indicating the number of PDCCH candidates corresponding to the aggregation level for each sub-CORESET. A base station, characterized in that the interleaving-related information includes at least one of information on a REG (Resource Element Group) bundle size, information on an interleaver size, and information on a shift index.

Images