Method and device for uplink / downlink transmission and reception in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. More specifically, the present disclosure relates to a method performed by a terminal in a wireless communication system, and the method may comprise the steps of: receiving, from a base station, configuration information for a beam pair including a beam related to uplink transmission and a beam related to downlink reception in a subband non-overlapping full duplex (SBFD) slot; receiving, from the base station, information for scheduling of the uplink transmission and the downlink reception in the SBFD slot; and performing the uplink transmission and the downlink reception in the SBFD slot on the basis of a beam pair configured on the basis of the configuration information for the beam pair.

Description

Method and device for uplink and downlink transmission and reception 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. Specifically, the present disclosure relates to a method for uplink and downlink transmission and reception between a base station and a terminal, and a device capable of performing the same.

[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 wireless interface architecture / protocols is in progress for technologies such as intelligent factories (Industrial Internet of Things, IIoT) 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 and Dual Active Protocol Stack (DAPS) handover, and 2-step random access (2-step RACH for NR) that simplifies random access procedures. Standardization is also in progress for system architecture / services such as 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.

[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 disclosed embodiment seeks to provide a device and method capable of effectively providing a service in a mobile communication system.

[0009] The technical problems to be achieved in the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by a person having ordinary skill in the technical field to which the present disclosure belongs from the description below.

[0010] In a method performed by a terminal in a wireless communication system according to an embodiment of the present disclosure for achieving the above-described technical task, the method may include: receiving, from a base station, configuration information for a beam pair including a beam related to uplink transmission and a beam related to downlink reception in a subband non-overlapping full duplex (SBFD) slot; receiving, from the base station, information for scheduling the uplink transmission and the downlink reception in the SBFD slot; and performing the uplink transmission and the downlink reception in the SBFD slot based on a beam pair configured based on the configuration information for the beam pair.

[0011] In addition, the present disclosure provides a method performed by a base station in a wireless communication system, the method comprising: transmitting, to a terminal, configuration information for a beam pair including a beam related to uplink transmission of the terminal in a subband non-overlapping full duplex (SBFD) slot and a beam related to downlink reception of the terminal; transmitting, to the terminal, information for scheduling the uplink transmission of the terminal and the downlink reception of the terminal in the SBFD slot; and performing, based on a beam pair configured based on the configuration information for the beam pair, reception for uplink transmission of the terminal and transmission for downlink reception of the terminal in the SBFD slot.

[0012] In addition, the present disclosure provides a terminal in a wireless communication system, the terminal including: a transceiver; and a controller connected to the transceiver, wherein the controller is configured to receive, from a base station, configuration information for a beam pair including a beam related to uplink transmission in a subband non-overlapping full duplex (SBFD) slot and a beam related to downlink reception, and to receive, from the base station, information for scheduling the uplink transmission and the downlink reception in the SBFD slot, and to perform the uplink transmission and the downlink reception in the SBFD slot based on a beam pair configured based on the configuration information for the beam pair.

[0013] In addition, the present disclosure provides a method for a base station in a wireless communication system, the base station including a transceiver; and a controller connected to the transceiver, wherein the controller transmits, to a terminal, configuration information for a beam pair including a beam related to uplink transmission of the terminal in a subband non-overlapping full duplex (SBFD) slot and a beam related to downlink reception of the terminal, and transmits, to the terminal, information for scheduling the uplink transmission of the terminal and the downlink reception of the terminal in the SBFD slot, and configures, based on a beam pair configured based on the configuration information for the beam pair, to perform reception for uplink transmission of the terminal and transmission for downlink reception of the terminal in the SBFD slot.

[0014] The disclosed embodiment can provide a device and method capable of effectively providing a service in a mobile communication system.

[0015] The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned can be clearly understood by a person having ordinary skill in the art to which the present disclosure belongs from the description below.

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

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

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

[0019] FIG. 4 is a diagram illustrating an example of base station beam allocation according to TCI state setting according to one embodiment of the present disclosure.

[0020] FIG. 5 is a diagram illustrating an example of a control region (Control Resource Set, CORESET) in which a downlink control channel is transmitted in a 5G wireless communication system.

[0021] Figure 6 is a diagram showing an example of a basic unit of time and frequency resources that constitute a downlink control channel that can be used in 5G.

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

[0023] FIG. 8 is a diagram illustrating a TCI indication MAC CE signaling structure for the PDCCH DMRS. FIG. 9 is a diagram illustrating an example of beam configuration of a control resource set (CORESET) and a search space according to the above description. FIG. 10 is a diagram illustrating a method for a terminal to select a receivable control resource set by considering priorities when receiving a downlink control channel in a wireless communication system according to an embodiment of the present disclosure. FIG. 11 is a diagram illustrating an example of time axis resource allocation of a PDSCH in a wireless communication system according to an embodiment of the present disclosure.

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

[0025] FIG. 13 illustrates a process for beam setting and activation of a PDSCH. FIG. 14 is a diagram illustrating a wireless protocol structure of a base station and a terminal in a single cell, carrier aggregation, and dual connectivity situation according to an embodiment of the present disclosure.

[0026] FIG. 15 is a diagram illustrating an example of SBFD operation in a TDD band of a wireless communication system according to an embodiment of the present disclosure.

[0027] FIG. 16 is a diagram illustrating an example of resource setting of SBFD of a wireless communication system according to an embodiment of the present disclosure.

[0028] FIG. 17 is a diagram illustrating an SBFD terminal operation according to an embodiment of the present disclosure.

[0029] FIG. 18 is a diagram illustrating an example of self-interference of a terminal in an SBFD system according to an embodiment of the present disclosure.

[0030] FIG. 19 illustrates an example of a flowchart of self-interference measurement and reporting between a base station and a terminal according to one embodiment of the present disclosure.

[0031] FIG. 20 is a diagram illustrating a method for setting self-interference measurement and reporting according to one embodiment of the present disclosure.

[0032] FIG. 21 is a diagram illustrating a method of setting self-interference measurement and reporting according to one embodiment of the present disclosure.

[0033] FIG. 22 is a diagram illustrating a method of setting self-interference measurement and reporting according to one embodiment of the present disclosure.

[0034] FIG. 23 illustrates a beam relationship between a downlink channel and an uplink channel of a terminal according to an embodiment of the present disclosure.

[0035] FIG. 24 illustrates a beam relationship between a downlink channel and an uplink channel of a terminal according to an embodiment of the present disclosure.

[0036] FIG. 25 illustrates a beam relationship between a downlink channel and an uplink channel of a terminal according to an embodiment of the present disclosure.

[0037] FIG. 26 illustrates a beam relationship between a downlink channel and an uplink channel of a terminal according to an embodiment of the present disclosure.

[0038] FIG. 27 is a diagram illustrating a flowchart for terminal and base station operations according to one embodiment of the present disclosure.

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

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

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

[0042] 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 avoid obscuring the gist of the present disclosure by omitting unnecessary explanations and to convey the gist more clearly.

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

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

[0045] In explaining the embodiments of the present disclosure, the main target is New Radio (NR), which is a wireless access network, and the core network, packet core 5G System, or 5G Core Network, or NG Core (Next Generation Core) in the 5G mobile communication standard specified by 3GPP (3rd Generation Partnership Project), a mobile communication standard standardization organization. However, the main gist of the present disclosure can be applied to other communication systems with similar technical backgrounds with slight modifications within a range that does not significantly deviate from the scope of the present disclosure, and this will be possible at the discretion of a person skilled in the art of the present disclosure.

[0046] For convenience of explanation, some terms and names defined in the 3GPP standards (standards for 5G, NR, LTE, or similar systems) may be used below. However, the present disclosure is not limited by these terms and names, and can be equally applied to systems conforming to other standards.

[0047] Hereinafter, terms used in the description to identify connection nodes, terms referring to network objects (network entities), terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, etc. are provided as examples for convenience of explanation. Therefore, the present disclosure is not limited to the terms used in the present disclosure, and other terms referring to objects with equivalent technical meanings may be used.

[0048] 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 an LTE (Long-Term Evolution) or LTE-A (LTE-advanced) system may be described below as an example, 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.

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

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

[0051] Here, the term '~ part' used in this embodiment means software or hardware components such as FPGA (field programmable gate array) or ASIC (application specific integrated circuit), and the '~ part' performs certain roles. However, the '~ part' is not limited to software or hardware. The '~ part' may be configured to be on an addressable storage medium or may be configured to play one or more processors. Therefore, as an example, the '~ part' 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 '~ parts' may be combined into a smaller number of components and '~ parts' or further separated into additional components and '~ parts'. In addition, the components and '~parts' may be implemented to play one or more central processing units (CPUs) within the device or secure multimedia card. Also, in an embodiment, the '~part' may include one or more processors.

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

[0053] As a representative example of the above broadband wireless communication system, the LTE system adopts the OFDM (Orthogonal Frequency Division Multiplexing) method in the downlink (DL) and the SC-FDMA (Single Carrier Frequency Division Multiple Access) 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 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.

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

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

[0056] 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 / km2) 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, such as basements, beyond cell coverage. This may require broader coverage compared to 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.

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

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

[0059] [NR time-frequency resources]

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

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

[0062] The horizontal axis of Figure 1 represents the time domain, and the vertical axis represents the frequency domain. The basic unit of resources in the time and frequency domains 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).

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

[0064] 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 10 ms. One subframe (201) can be defined as 1 ms, 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 shown in Table 1 below.

[0065]

[0066] [Bandwidth Part (BWP)]

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

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

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

[0070]

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

[0072] According to some embodiments, 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 where a PDCCH for receiving system information (which may correspond to Remaining System Information (RMSI) or System Information Block 1 (SIB1)) required for initial access can be transmitted through the MIB during the initial access phase. The control region and search space configured by the MIB may each be regarded as identifier (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. In addition, the base station can notify the terminal of configuration information for a monitoring cycle and occasion for control region #0, i.e., configuration information for search space #0, through the MIB. The terminal may consider the frequency range set as control area #0 obtained from the MIB as the initial bandwidth portion for initial connection. At this time, the identifier (ID) of the initial bandwidth portion may be considered as 0.

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

[0074] In some embodiments, 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.

[0075] Additionally, in some embodiments, a base station may configure multiple bandwidth segments for a terminal to support different numerologies. For example, to support data transmission and reception using both 15 kHz and 30 kHz subcarrier spacing for a given terminal, two bandwidth segments may be configured with subcarrier spacings of 15 kHz and 30 kHz, respectively. The different bandwidth segments may be frequency-division multiplexed, and when data is to be transmitted and received using a specific subcarrier spacing, the bandwidth segment configured for that subcarrier spacing may be activated.

[0076] Furthermore, in some embodiments, the base station may configure bandwidth portions with different bandwidth sizes for the terminal for the purpose of reducing power consumption of the terminal. For example, if the terminal supports a very large bandwidth, for example, 100 MHz, and constantly transmits and receives data using that bandwidth, very large power consumption may occur. In particular, monitoring unnecessary downlink control channels using a large bandwidth of 100 MHz in a situation where there is no traffic may be very inefficient in terms of power consumption. To reduce power consumption of the terminal, the base station may configure a bandwidth portion with a relatively small bandwidth, for example, 20 MHz, for the terminal. In a situation where there is no traffic, the terminal can perform monitoring operations in the 20 MHz bandwidth portion, and when data is generated, it can transmit and receive data using the 100 MHz bandwidth portion according to the instructions of the base station.

[0077] In the method for setting the bandwidth part, terminals before RRC connection (Connected) can receive setting information for the initial bandwidth part through the MIB (Master Information Block) in the initial access stage. More specifically, the terminal can set 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 the purpose of receiving the SIB, the initial bandwidth part can also be utilized for other system information (Other System Information, OSI), paging, and random access.

[0078] [Bandwidth Part (BWP) Change]

[0079] When one or more bandwidth part values ​​are set for a terminal, the base station can instruct the terminal to change (or switch, transition) the bandwidth part value 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.

[0080] As described above, since DCI-based bandwidth part change can be indicated by DCI scheduling PDSCH or PUSCH, when a terminal receives a bandwidth part change request, it must be able to receive or transmit PDSCH or PUSCH scheduled by the corresponding DCI without difficulty in the changed bandwidth part. To this end, the standard stipulates the delay time (T) required when changing the bandwidth part. BWP ) and can be defined as in Table 3, for example.

[0081]

[0082] The bandwidth-partial change delay time requirement supports 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.

[0083] 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 The completion can be done 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. When 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 the 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 the time domain resource allocation for the data channel. Accordingly, the terminal can determine whether the DCI instructing the 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.

[0084] 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 from the third symbol of the slot in which the PDCCH including the DCI is received to the start point 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).

[0085] [SS / PBCH block]

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

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

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

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

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

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

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

[0093] [QCL, TCI state]

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

[0095]

[0096] The above spatial Rx parameter may collectively refer to some or all of various parameters, such as Angle of Arrival (AoA), Power Angular Spectrum (PAS) of AoA, Angle of Departure (AoD), PAS of AoD, transmit / receive channel correlation, transmit / receive beamforming, and spatial channel correlation.

[0097] The above QCL relationship can be set to the terminal through the RRC parameters TCI-state and QCL-Info as shown in Table 5 below. Referring to [Table 5], the base station can set one or more TCI states to the terminal and inform the RS referencing the ID of the TCI state, i.e., up to two QCL relationships (qcl-Type1, qcl-Type2) for the target RS. At this time, each QCL information (QCL-Info) included in the above TCI state includes the serving cell index and BWP index of the reference RS indicated by the corresponding QCL information, the type and ID of the reference RS, and the QCL type as shown in [Table 5] above.

[0098]

[0099] FIG. 4 is a diagram illustrating an example of base station beam allocation according to TCI state setting according to one embodiment of the present disclosure.

[0100] Referring to FIG. 4, the base station can transmit information about N different beams to the terminal through N different TCI states. For example, in case of N=3 as shown in FIG. 4, the base station can notify that the antenna ports referencing the different TCI states 400, 405, or 410 have different spatial Rx parameters, i.e., are associated with different beams, by setting the qcl-Type2 parameters included in the three TCI states (400, 405, 410) to be associated with CSI-RS or SSB corresponding to different beams and to QCL type D.

[0101] Tables 6 to 10 below show valid TCI state settings according to target antenna port type.

[0102] [Table 6] shows valid TCI state settings when the target antenna port is a CSI-RS for tracking (i.e., TRS). The TRS refers to an NZP CSI-RS with no repetition parameter set and trs-Info set to true among CSI-RSs. Setting 3 in Table 9 can be used for aperiodic TRS.

[0103]

[0104] Table 7 shows examples of valid TCI state settings when the target antenna port is CSI-RS for CSI.

[0105]

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

[0107] Table 8 shows examples of valid TCI state settings when the target antenna port is CSI-RS for BM (for L1 RSRP reporting).

[0108]

[0109] [Table 9] shows the valid TCI state settings when the target antenna port is PDCCH DMRS.

[0110] Table 9 shows the valid TCI state settings when the target antenna port is PDCCH DMRS.

[0111]

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

[0113] Table 10 shows examples of valid TCI state settings when the target antenna port is PDSCH DMRS.

[0114]

[0115] A representative QCL setting method according to the above [Table 6] to [Table 10] is to set and operate the target antenna port and reference antenna port for each step as "SSB" -> "TRS" -> "CSI-RS for CSI, or CSI-RS for BM, or PDCCH DMRS, or PDSCH DMRS." Through this, it is possible to link statistical characteristics that can be measured from SSB and TRS to each antenna port to assist the terminal's receiving operation.

[0116] [PDCCH: DCI related]

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

[0118] 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 defined between the base station and the terminal, and the non-fallback DCI format can include configurable fields.

[0119] DCI can be transmitted through 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 was transmitted to the UE.

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

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

[0122]

[0123] 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 12.

[0124]

[0125]

[0126] 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 13.

[0127]

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

[0129]

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

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

[0132] FIG. 5 is a diagram illustrating 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 (501), Control Region #2 (502)) are set within a UE bandwidth part (510) in the frequency axis and one slot (520) in the time axis. The control regions (501, 502) may be set to specific frequency resources (503) within the entire UE bandwidth part (510) in the frequency axis. The time axis may be set to one or more OFDM symbols, which may be defined as the control region length (Control Resource Set Duration, 504). Referring to the example illustrated in FIG. 5, Control Region #1 (501) is set to a control region length of two symbols, and Control Region #2 (502) is set to a control region length of one symbol.

[0133] In the aforementioned 5G, the control region can be established by the base station to the terminal via higher-layer signaling (e.g., system information, Master Information Block (MIB), Radio Resource Control (RRC) signaling). Establishing a control region for the terminal means providing information such as the control region identifier, 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 15.

[0134]

[0135] In Table 15, 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.

[0136] FIG. 6 is a diagram showing an example of a basic unit of time and frequency resources that constitute a downlink control channel that can be used in 5G. According to FIG. 5, the basic unit of time and frequency resources that constitute a control channel can be referred to as a REG (Resource Element Group, 603), and a REG (603) can be defined as 1 OFDM symbol (601) on the time axis and 1 PRB (Physical Resource Block, 602) on the frequency axis, i.e., 12 subcarriers. A base station can concatenate REGs (603) to constitute a downlink control channel allocation unit.

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

[0138] The basic unit of the downlink control channel illustrated in FIG. 6, that is, the REG (603), may include both the REs to which the DCI is mapped and the areas to which the DMRS (605), which is a reference signal for decoding the REs, is mapped. As shown in FIG. 6, three DMRSs (605) may be transmitted within one REG (603). 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.

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

[0140] In 5G, parameters for the search space for PDCCH can be configured from the base station to the terminal through 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, it can include the information in Table 16.

[0141]

[0142]

[0143] Depending on the configuration information, the base station may configure one or more search space sets for the terminal. In some embodiments, the base station may configure search space set 1 and search space set 2 for the terminal, and may configure the terminal to monitor DCI format A scrambled with X-RNTI in search space set 1 in a common search space, and may configure the terminal to monitor DCI format B scrambled with Y-RNTI in search space set 2 in a terminal-specific search space.

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

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

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

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

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

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

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

[0151] In a terminal-specific search space, the following combinations of DCI formats and RNTIs can be monitored. Of course, the examples below are not limited to these examples.

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

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

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

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

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

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

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

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

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

[0161] INT-RNTI (Interruption RNTI): Used to indicate whether pucturing is in progress for PDSCH.

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

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

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

[0165] The aforementioned specified DCI formats may follow definitions such as those in the example in Table 17.

[0166]

[0167] In 5G, the search space of aggregation level L in the control region p and search space set s can be expressed as in the following mathematical expression 1.

[0168]

[0169] - : Integration level

[0170] - : Carrier Index

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

[0172] - : slot index

[0173] - Number of PDCCH candidates for aggregation level L

[0174] - PDCCH candidate index for aggregation level L

[0175] -

[0176] -

[0177] - : Terminal identifier

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

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

[0180] In 5G, since multiple search space sets can be configured with different parameters, 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 configured with an X-slot period and search space set #2 is configured 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 monitor either search space set #1 or search space set #2 in a specific slot.

[0181] [PDCCH: TCI state related]

[0182] Specifically, the TCI state combinations applicable to the PDCCH DMRS antenna port are as shown in [Table 18] below. The fourth row in [Table 18] is the combination assumed by the terminal before RRC configuration, and configuration after RRC is not possible.

[0183]

[0184] NR supports a hierarchical signaling method as illustrated in FIG. 7 for dynamic allocation of PDCCH beams. Referring to FIG. 7, a base station can set N TCI states (705, 710, ..., 720) to a terminal through RRC signaling (700), and can set some of them as TCI states for CORESET (725). Thereafter, the base station can indicate one of the TCI states (730, 735, 740) for CORESET to the terminal through MAC CE signaling (745). Thereafter, the terminal receives the PDCCH based on beam information included in the TCI state indicated by the MAC CE signaling.

[0185] FIG. 8 is a diagram illustrating a TCI indication MAC CE signaling structure for the PDCCH DMRS. Referring to FIG. 8, the TCI indication MAC CE signaling for the PDCCH DMRS consists of 2 bytes (16 bits) and includes a 5-bit serving cell ID (815), a 4-bit CORESET ID (820), and a 7-bit TCI state ID (825).

[0186] FIG. 9 is a diagram illustrating an example of beam configuration of a control resource set (CORESET) and a search space according to the above description. Referring to FIG. 9, a base station can indicate one of the TCI state lists included in the CORESET (900) configuration through MAC CE signaling (905). Thereafter, until another TCI state is indicated to the corresponding CORESET through another MAC CE signaling, the terminal considers that the same QCL information (beam #1, 905) is applied to all one or more search spaces (910, 915, 920) connected to the CORESET. The above-described PDCCH beam allocation method has a problem in that it is difficult to indicate a beam change faster than the MAC CE signaling delay, and also has a disadvantage in that the same beam is applied to all CORESETs regardless of the search space characteristics, which makes flexible PDCCH beam operation difficult. The embodiments of the present disclosure below provide a more flexible PDCCH beam configuration and operation method. In explaining embodiments of the present disclosure below, several distinct examples are provided for convenience of explanation, but these are not mutually exclusive and can be applied in appropriate combination depending on the situation.

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

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

[0189] For a control region (control region #X) whose index is set to a value other than 0, if the terminal has not set a TCI state for the control region #X, or has set one or more TCI states but has not received a MAC CE activation command to activate one of them, the terminal may assume that the DMRS transmitted in the control region #X is QCL with the SS / PBCH block identified during the initial access process.

[0190] [PDCCH: QCL prioritization related]

[0191] Below, the QCL priority determination operation for PDCCH is described in detail.

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

[0193] - Criterion 1. A set of control resources connected to the common search section with the lowest index within the cell corresponding to the lowest index among the cells containing the common search section.

[0194] - Criterion 2. The control resource set associated with the terminal-specific search section with the lowest index within the cell corresponding to the lowest index among the cells containing the terminal-specific search section.

[0195] As described above, if the above criteria are not met, the following criteria are applied. For example, if control resource sets overlap in time in a specific PDCCH monitoring interval, and if not all control resource sets are connected to a common search interval but to a terminal-specific search interval, i.e., if criterion 1 is not met, the terminal may skip applying criterion 1 and apply criterion 2.

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

[0197] FIG. 10 is a diagram for explaining a method for selecting a control resource set that can be received by a terminal in consideration of priorities when receiving a downlink control channel in a wireless communication system according to an embodiment of the present disclosure. For example, the terminal may be configured to receive multiple control resource sets that overlap in time in a specific PDCCH monitoring section (1010), and these multiple control resource sets may be connected to a common search space or a terminal-specific search space for multiple cells. Within the PDCCH monitoring section, a first control resource set (1015) connected to the first common search space may exist within a first bandwidth portion (1000) of a first cell, and a first control resource set (1020) connected to the first common search space and a second control resource set (1025) connected to the second terminal-specific search space may exist within a first bandwidth portion (1005) of a second cell. Control resource sets (1015) and (1020) may have a relationship of QCL-TypeD with the 1st CSI-RS resource set within the 1st bandwidth portion of the 1st cell, and control resource set (1025) may have a relationship of QCL-TypeD with the 1st CSI-RS resource set within the 1st bandwidth portion of the 2nd cell. Therefore, when criterion 1 is applied to the corresponding PDCCH monitoring section (1010), all other control resource sets having the same QCL-TypeD reference signal as the 1st control resource set (1015) can be received. Therefore, the terminal can receive control resource sets (1015) and (1020) in the corresponding PDCCH monitoring section (1010). As another example, a terminal may be configured to receive multiple control resource sets that overlap in time in a specific PDCCH monitoring interval (1040), and these multiple control resource sets may be associated with a common search space or a terminal-specific search space for multiple cells.Within the corresponding PDCCH monitoring section, within the first bandwidth portion (1030) of the first cell, there may exist a first control resource set (1045) connected to the first terminal-specific search section and a second control resource set (1050) connected to the second terminal-specific search section, and within the first bandwidth portion (1035) of the second cell, there may exist a first control resource set (1055) connected to the first terminal-specific search section and a second control resource set (1060) connected to the third terminal-specific search space. Control resource sets (1045) and (1050) have a relationship with the 1st CSI-RS resource set in the 1st bandwidth part of the 1st cell and QCL-TypeD, control resource set (1055) has a relationship with the 1st CSI-RS resource set in the 1st bandwidth part of the 2nd cell and QCL-TypeD, and control resource set (1060) can have a relationship with the 2nd CSI-RS resource set in the 1st bandwidth part of the 2nd cell and QCL-TypeD. However, if criterion 1 is applied to the corresponding PDCCH monitoring section (1040), there is no common search section, so the next criterion, criterion 2, can be applied. If criterion 2 is applied to the corresponding PDCCH monitoring section (1040), all other control resource sets having the same QCL-TypeD reference signal as the control resource set (1045) can be received. Accordingly, the terminal can receive control resource sets (1045) and (1050) in the corresponding PDCCH monitoring section (1040).

[0198] [PDSCH / PUSCH: Time Resource Allocation Related]

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

[0200] 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 19] or [Table 20] below may be transmitted from the base station to the terminal.

[0201]

[0202]

[0203] The base station may 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) (e.g., indicated by the 'Time Domain Resource Allocation' field in the DCI). The terminal may obtain the time domain resource allocation information for the PDSCH or PUSCH based on the DCI received from the base station.

[0204] FIG. 11 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.

[0205] Referring to Figure 11, 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 (1100) and length (1105) within a slot dynamically indicated through DCI.

[0206] FIG. 12 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.

[0207] Referring to Figure 12, when the subcarrier spacing of the data channel and the control channel is the same (9-00, μ 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, if the subcarrier spacing of the data channel and the control channel are different (9-05, μ 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.

[0208] [PDSCH: TCI state activation MAC-CE]

[0209] Figure 13 illustrates a process for beam configuration and activation of a PDSCH. A list of TCI states for a PDSCH can be indicated through a list of upper layers such as RRC (1300). The list of TCI states can be indicated, for example, as tci-StatesToAddModList and / or tci-StatesToReleaseList in the PDSCH-Config IE for each BWP. Next, some of the list of TCI states can be activated through MAC-CE (1320). Among the TCI states activated through the MAC-CE, a TCI state for the PDSCH can be indicated through DCI (1340). The maximum number of activated TCI states can be determined according to the capability reported by the UE. (1350) illustrates an example of a MAC-CE structure for PDSCH TCI state activation / deactivation.

[0210] The meaning of each field in the above MAC CE and the values ​​that can be set for each field are as follows [Table 21].

[0211]

[0212]

[0213] [PUCCH: Transmitting Beam Related]

[0214] Next, the uplink transmission beam configuration to be used for PUCCH transmission is described. If the UE does not have a dedicated PUCCH resource configuration, the PUCCH resource set is provided through the upper layer signaling, pucch-ResourceCommon, and the beam configuration for PUCCH transmission follows the beam configuration used in the PUSCH transmission scheduled through the Random Access Response (RAR) UL grant. If the UE has a dedicated PUCCH resource configuration, the beam configuration for PUCCH transmission can be provided through the upper layer signaling, pucch-spatialRelationInfoId, included in [Table 22]. If the UE has been configured with multiple pucch-spatialRelationInfoIDs, the UE can be instructed to activate one of the multiple pucch-spatialRelationInfoIDs through the MAC control element (CE). A terminal can receive up to eight pucch-spatialRelationInfoIDs through upper level signaling, and can be instructed to activate only one pucch-spatialRelationInfoID. If the terminal is instructed to activate any pucch-spatialRelationInfoID through MAC CE, the terminal transmits HARQ-ACK for the PDSCH in which the MAC CE containing activation information for the pucch-spatialRelationInfoID is transmitted from the slot in which the terminal transmits. Starting from the first slot that appears after the slot, activation of pucch-spatialRelationInfoID through MAC CE can be applied. μ is the numerology applied to PUCCH transmission, refers to the number of slots per subframe in a given numerology. The upper layer configuration for pucch-spatialRelationInfo can be as shown in [Table 22] below.

[0215]

[0216] According to [Table 22], a specific pucch-spatialRelationInfo setting may have one referenceSignal setting, and the referenceSignal may be ssb-Index indicating a specific SS / PBCH, csi-RS-Index indicating a specific CSI-RS, or srs indicating a specific SRS. If the referenceSignal is set to ssb-Index, the terminal may set the beam used when receiving the SS / PBCH corresponding to the ssb-Index among the SS / PBCHs within the same serving cell as a beam for PUCCH transmission, or, if servingCellId is provided, may set the beam used when receiving the SS / PBCH corresponding to the ssb-Index among the SS / PBCHs within the cell indicated by the servingCellId as a beam for PUCCH transmission. If the referenceSignal is set to csi-RS-Index, the terminal can set the beam used when receiving the CSI-RS corresponding to csi-RS-Index among the CSI-RSs within the same serving cell as the beam for PUCCH transmission, or if servingCellId is provided, the terminal can set the beam used when receiving the CSI-RS corresponding to csi-RS-Index among the CSI-RSs within the cell indicated by servingCellId as the beam for PUCCH transmission.If referenceSignal is set to srs, the UE may set the transmission beam used when transmitting the SRS corresponding to the resource index provided as a higher-order signaling resource within the same serving cell and / or within the activated uplink BWP as a beam for PUCCH transmission, or, if servingCellID and / or uplinkBWP are provided, set the transmission beam used when transmitting the SRS corresponding to the resource index provided through the higher-order signaling resource within the cell indicated by servingCellID and / or uplinkBWP and / or within the uplink BWP as a beam for PUCCH transmission. There can be one pucch-PathlossReferenceRS-Id setting within a specific pucch-spatialRelationInfo setting. The PUCCH-PathlossReferenceRS in [Table 23] can be mapped to the pucch-PathlossReferenceRS-Id in [Table 22], and up to four can be set via pathlossReferenceRS within the higher-order signaling PUCCH-PowerControl in [Table 23]. If PUCCH-PathlossReferenceRS is connected to SS / PBCH through referenceSignal, which is an upper signaling, it can set ssb-Index, and if it is connected to CSI-RS, it can set csi-RS-Index.

[0217]

[0218]

[0219] [PUSCH: Transmission method related]

[0220] 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 are possible in DCI format 0_0 or 0_1.

[0221] Configured grant Type 1 PUSCH transmission can be semi-statically configured by receiving configuredGrantConfig including rrc-ConfiguredUplinkGrant of [Table 24] 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 24] through higher-order signaling. When PUSCH transmission operates by configured grant, parameters applied to PUSCH transmission are applied through configuredGrantConfig of higher-order signaling of [Table 24], except for dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, and scaling of UCI-OnPUSCH provided by pusch-Config of [Table 25]. If the terminal has been provided with transformPrecoder in configuredGrantConfig, which is the upper signaling of [Table 24], the terminal applies tp-pi2BPSK in pusch-Config of [Table 25] to PUSCH transmission operated by the configured grant.

[0222]

[0223]

[0224] Next, the PUSCH transmission method is described. The DMRS antenna port for PUSCH transmission is 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, depending on whether the value of txConfig in the upper signaling, pusch-Config in [Table 25], is 'codebook' or 'nonCodebook'.

[0225] 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 performs 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 the PUSCH transmission is based on a single antenna port. The UE does 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 does not configure txConfig in pusch-Config of [Table 25], the UE does not expect to be scheduled with DCI format 0_1.

[0226]

[0227]

[0228] Next, we describe codebook-based PUSCH transmission. Codebook-based PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1, or 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 determines a precoder for PUSCH transmission based on the SRS Resource Indicator (SRI), Transmission Precoding Matrix Indicator (TPMI), and transmission rank (the number of PUSCH transmission layers).

[0229] 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 refers to the 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 is used to indicate the precoder applied to the PUSCH transmission. If the UE is configured with one SRS resource, the TPMI is used to indicate the precoder to be applied to the configured one SRS resource. When a terminal is configured with multiple SRS resources, TPMI is used to indicate the precoder to be applied in the SRS resource indicated through SRI.

[0230] 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 determines 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 does 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 does 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 does not expect the value of the upper signaling codebookSubset to be set to 'partialAndNonCoherent'.

[0231] The 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 in the SRS resource set can be indicated via SRI. If multiple SRS resources are configured in the SRS resource set in which the usage value in the upper signaling SRS-ResourceSet is set to 'codebook', the terminal expects that the value of nrofSRS-Ports in the upper signaling SRS-Resource is set to the same value for all SRS resources.

[0232] 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 selects one of the SRS resources transmitted by the terminal and instructs 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 is included in the DCI. Additionally, the base station includes in the DCI information indicating the TPMI and rank to be used by the terminal for PUSCH transmission. The terminal performs 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.

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

[0234] 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 does not expect information about the precoder for SRS transmission to be updated.

[0235] If the value of resourceType in the upper signaling SRS-ResourceSet is set to 'aperiodic', the connected NZP CSI-RS is 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 are not set to QCL-TypeD.

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

[0237] 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 srs-ResourceIndicator, which is a higher-order signaling. 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 refers to the 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 are determined by the UE capability reported by the UE to the base station. At this time, the SRS resources that the UE simultaneously transmits occupy the same RB. The UE configures one SRS port for each SRS resource. Only one SRS resource set with the usage value set to 'nonCodebook' in the upper signaling SRS-ResourceSet can be set, and up to four SRS resources for non-codebook based PUSCH transmission can be set.

[0238] The base station transmits one NZP-CSI-RS associated with an SRS resource set to the terminal, and the terminal calculates 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 with usage set to 'nonCodebook' to the base station, the terminal applies the calculated precoder, and the base station selects one or more SRS resources from 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 is 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 transmits the PUSCH by applying the precoder applied to SRS resource transmission to each layer.

[0239] [PUSCH: Preparation time]

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

[0241]

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

[0243] - N2: The number of symbols determined by the UE processing capability (UE processing capability) 1 or 2 and the numerology μ according to the UE capability. If UE processing capability 1 is reported according to the UE capability report, it may have the value in [Table 26]. If UE processing capability 2 is reported and the availability of UE processing capability 2 is set through upper layer signaling, it may have the value in [Table 27].

[0244]

[0245]

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

[0247] - : 64

[0248] - μ: μ 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 refers to the numerology of the uplink in which PUSCH is transmitted.

[0249] - T c : 1 / ( f max *N f ), f max = 480*10 3 Hz, N f =has 4096.

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

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

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

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

[0254] 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 is determined to be insufficient. Otherwise, the base station and the UE 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.

[0255] [PUSCH: Repetitive Transmission Related]

[0256] Next, we will describe in detail the repetitive transmission of uplink data channels in 5G systems. 5G systems support two types of repetitive transmission methods for uplink data channels: PUSCH repetitive transmission type A and PUSCH repetitive transmission type B. A terminal can be configured with either PUSCH repetitive transmission type A or B via higher-layer signaling.

[0257] 1. PUSCH Repetitive Transmission Type A

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

[0259] - The terminal can repeatedly transmit an uplink data channel with the same length and start symbol of the configured uplink data channel based on the number of repeated transmissions received from the base station in consecutive slots. At this time, if at least one symbol among the slots configured by the base station as downlink to the terminal or the symbols of the uplink data channel configured to the terminal is configured as downlink, the terminal skips the uplink data channel transmission, but counts the number of repeated transmissions of the uplink data channel. In other words, although it is included in the number of repeated transmissions of the uplink data channel, the uplink data channel may not be transmitted. On the other hand, a terminal that supports Rel-17 repeated uplink data transmission determines a slot in which repeated uplink data transmission is possible as an available slot, and can count the number of transmissions when repeated uplink data channels are transmitted in slots determined as available slots. In other words, if repeated uplink data channel transmission is omitted in a slot determined as an available slot, the omitted repeated transmission may not be counted, and may be postponed until the next available slot before transmission.

[0260] - In order to determine the available slot, if at least one symbol set to TDRA (time domain resource allocation) for PUSCH in a slot for PUSCH transmission overlaps with a symbol for a purpose other than uplink transmission (e.g., downlink), the slot is determined as an unavailable slot (e.g., a slot that is not an available slot and is determined to be unavailable for PUSCH transmission). In addition, the available slot may be considered as an uplink resource for determining resources for PUSCH transmission and transport block size (TBS) in PDSCH repeated transmission and multi-slot PUSCH transmission consisting of one TB (TBoMS (transport block on multiple slots)).

[0261] 2. PUSCH Repetitive Transmission Type B

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

[0263] - First, the nominal repetition of the uplink data channel is determined based on the start symbol and length of the established uplink data channel as follows. The slot where the nth nominal repetition starts is The symbol given by and starting from that slot is is given by . The slot where the nth nominal repetition ends is The symbol given by and ending in that slot is is given by . Here, n=0,..., numberofrepetitions-1, S represents the start symbol of the established uplink data channel, and L represents the symbol length of the established uplink data channel. indicates the slot in which the PUSCH transmission starts. Indicates the number of symbols per slot.

[0264] - The terminal may determine a specific OFDM symbol as an invalid symbol for the following cases for PUSCH repetitive transmission type B.

[0265] - Symbols set to downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated may be determined as invalid symbols for PUSCH repetitive transmission type B.

[0266] - Symbols indicated by ssb-PositionsInBurst in SIB1 or ssb-PositionsInBurst in ServingCellConfigCommon, which is a higher layer signaling, for SSB reception in unpaired spectrum (TDD spectrum) may be determined as invalid symbols for PUSCH repetition transmission type B.

[0267] - In unpaired spectrum (TDD spectrum), symbols indicated through pdcch-ConfigSIB1 in the MIB to transmit a control resource set associated with a Type0-PDCCH CSS set may be determined as invalid symbols for PUSCH repetition transmission Type B.

[0268] - In unpaired spectrum (TDD spectrum), if the upper layer signaling numberOfInvalidSymbolsForDL-UL-Switching is set, symbols set to downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated for numberOfInvalidSymbolsForDL-UL-Switching can be determined as invalid symbols.

[0269] - Additionally, an invalid symbol can be set in a higher layer parameter (e.g., InvalidSymbolPattern). The higher layer parameter (e.g., InvalidSymbolPattern) provides a symbol-level bitmap spanning one or two slots, where an invalid symbol can be set. Additionally, the periodicity and pattern of the bitmap can be set via a higher layer parameter (e.g., periodicityAndPattern). If the higher layer parameter (e.g., InvalidSymbolPattern) is set and the InvalidSymbolPatternIndicator-ForDCIFormat0_1 or InvalidSymbolPatternIndicator-ForDCIFormat0_2 parameter indicates 1, the terminal applies the invalid symbol pattern, and if the parameter indicates 0, the terminal does not apply the invalid symbol pattern. If a higher layer parameter (e.g., InvalidSymbolPattern) is set and the InvalidSymbolPatternIndicator-ForDCIFormat0_1 or InvalidSymbolPatternIndicator-ForDCIFormat0_2 parameter is not set, the terminal applies an invalid symbol pattern.

[0270] After invalid symbols are determined, for each nominal repetition, the UE may consider symbols other than the invalid symbol as valid symbols. If each nominal repetition contains at least one valid symbol, the nominal repetition may contain one or more actual repetitions. Here, each actual repetition contains a contiguous set of valid symbols that can be used for PUSCH repetitive transmission type B within a single slot. If the OFDM symbol length of the nominal repetition is not 1, the UE may ignore the transmission for the corresponding actual repetition if the actual repetition length is 1.

[0271] FIG. 10 is a diagram illustrating an example of PUSCH repetition transmission type A in a wireless communication system according to one embodiment of the present disclosure.

[0272] When the base station configures uplink resources through upper layer signaling (e.g., tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated) or L1 signaling (e.g., dynamic slot format indicator), the base station and terminal can determine available slots for the configured uplink resources according to the following two methods.

[0273] - Method for determining available slots based on TDD configuration

[0274] - Method for determining available slots considering TDD configuration and time domain resource allocation (TDRA), CG (Configured Grant) configuration, or activation DCI

[0275] As an example of a method for determining available slots based on a TDD configuration, in FIG. 10, when the TDD configuration is set to 'DDFUU' through upper layer signaling, the base station and terminal can determine slot #3 and slot #4 set to uplink 'U' based on the TDD configuration as available slots (1001). At this time, slot #2 (1002) set to flexible slot 'F' based on the TDD configuration can be determined as an unavailable slot or an available slot, and can be predefined, for example, through base station settings.

[0276] As an example of a method for determining available slots considering TDD configuration and time domain resource allocation (TDRA), CG configuration or activation DCI, in FIG. 10, when the TDD configuration is set to 'UUUUU' through upper layer signaling and the SLIV (start and length indicator value) of PUSCH transmission is set to {S: 2, L: 12 symbols} through L1 signaling, the base station and the terminal can determine slot #0, slot #1, slot #3, and slot #4 that satisfy SLIV of PUSCH for the set uplink slot 'U' as available slots. At this time, the base station and the terminal may determine slot #2 ('L=9') that does not satisfy SLIV, which is a TDRA condition for PUSCH transmission. SLIV 'L=12') can be judged as an unavailable slot (1003). This is for illustrative purposes only and does not limit the scope to PUSCH transmission. It can also be applied to PUCCH transmission, PUSCH / PUCCH repeated transmission, nominal repetition of PUSCH repetition type B, and TBoMS.

[0277] FIG. 11 is a diagram illustrating an example of PUSCH repetition transmission type B in a wireless communication system according to an embodiment of the present disclosure.

[0278] FIG. 11 illustrates an example in which a terminal receives a transmission start symbol S set to 0, a transmission symbol length L set to 10, and a number of repeated transmissions set to 10 for a nominal repetition, which can be expressed as N1 to N10 in the drawing (1102). At this time, the terminal can determine an invalid symbol by considering the slot format (1101) and determine the actual repetition, which can be expressed as A1 to A10 in the drawing (1103). At this time, according to the invalid symbol and actual repetition determination method described above, PUSCH repetition type B is not transmitted in a symbol for which the slot format is determined to be downlink, and if a slot boundary exists within the nominal repetition, it can be divided into two actual repetitions based on the slot boundary and transmitted. For example, A1, which means the first actual repetition, can be composed of three OFDM symbols, and A2, which can be transmitted next, can be composed of six OFDM symbols.

[0279] [CA / DC related]

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

[0281] Referring to FIG. 14, the wireless protocol of the next-generation mobile communication system is composed of NR SDAP (Service Data Adaptation Protocol 1425, 1470), NR PDCP (Packet Data Convergence Protocol 1430, 1465), NR RLC (Radio Link Control 1435, 1460), and NR MAC (Medium Access Control 1440, 1455) in the terminal and NR base station, respectively.

[0282] The main functions of NR SDAP (1425, 1470) may include some of the following functions:

[0283] - Transfer of user plane data

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

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

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

[0287] 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 a smooth service.

[0288] The main functions of NR PDCP (1430, 1465) may include some of the following functions:

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

[0290] - User data transfer function

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

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

[0293] - PDCP PDU reordering for reception

[0294] - Duplicate detection of lower layer SDUs

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

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

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

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

[0299] The main functions of NR RLC (1435, 1460) may include some of the following functions:

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

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

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

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

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

[0305] - Re-segmentation of RLC data PDUs

[0306] - Reordering of RLC data PDUs

[0307] - Duplicate detection function

[0308] - Protocol error detection

[0309] - RLC SDU discard function

[0310] - RLC re-establishment function

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

[0312] The out-of-sequence delivery function of the NR RLC device 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 an original RLC SDU is received divided into multiple RLC SDUs, and may include a function of storing the RLC SN or PDCP SN of received RLC PDUs and arranging the order to record lost RLC PDUs.

[0313] NR MAC (1440, 1455) 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.

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

[0315] - Multiplexing / demultiplexing of MAC SDUs

[0316] - Scheduling information reporting function

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

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

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

[0320] - MBMS service identification function

[0321] - Transport format selection function

[0322] - Padding function

[0323] The NR PHY layer (1445, 1450) can perform operations such as 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.

[0324] 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 S00. 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 S10, 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 S20, but multiplexes the PHY layer through the MAC layer.

[0325] Referring to the above-described PDCCH and beam configuration-related descriptions, the current Rel-15 and Rel-16 NR do not support PDCCH repetitive transmission, making it difficult to achieve the required reliability in scenarios requiring high reliability, such as URLLC. The present disclosure provides a method for repetitively transmitting PDCCHs through multiple transmission points (TRPs) to improve PDCCH reception reliability at a terminal. Specific methods are described in detail in the following examples.

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

[0327] In the present disclosure, when determining whether cooperative communication is applied, the terminal may use various methods, such as having the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied have a specific format, or including a specific indicator that indicates whether cooperative communication is applied, or scrambled with a specific RNTI by the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied, or assuming cooperative communication is applied in a specific section indicated by a higher layer. For the convenience of the following description, the case where the terminal receives the PDSCH to which cooperative communication is applied based on conditions similar to the above will be referred to as the NC-JT case.

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

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

[0330] [SBFD related]

[0331] Meanwhile, 3GPP is discussing SBFD (Subband Non-Overlapping Full Duplex) as a new duplex method based on NR. SBFD is a technology that utilizes a portion of downlink resources as uplink resources in the TDD band (spectrum) of frequencies below 6 GHz or above 6 GHz, thereby receiving uplink transmissions from terminals equivalent to the increased uplink resources, thereby expanding the uplink coverage of the terminal, and receiving feedback from the terminal on downlink transmissions using the expanded uplink resources, thereby reducing feedback delay. In the present disclosure, a terminal that receives information on whether SBFD is supported from a base station and can perform uplink transmissions using a portion of downlink resources may be conveniently referred to as an SBFD terminal (SBFD-capable UE). The following methods may be considered for defining the SBFD method in the standard and for an SBFD terminal to determine whether SBFD is supported in a specific cell (or frequency, frequency band).

[0332] First method. In addition to the existing unpaired spectrum (or time division duplex, TDD) or paired spectrum (or frequency division duplex, FDD) frame structure types, another frame structure type (e.g., frame structure type 2) may be introduced to define the above SBFD. The above frame structure type 2 may be defined as being supported in the specific frequency or frequency band, or the base station may indicate to the terminal whether SBFD is supported as system information. The SBFD terminal may receive the system information including whether SBFD is supported and determine whether SBFD is supported in the specific cell (or frequency, frequency band).

[0333] Second method. Whether SBFD is additionally supported in a specific frequency or frequency band of an existing unpaired spectrum (or TDD) can be indicated without defining a new frame structure type. In the second method, whether SBFD is additionally supported in a specific frequency or frequency band of an existing unpaired spectrum can be defined, or the base station can indicate to the terminal whether SBFD is supported as system information. The SBFD terminal can receive system information including whether SBFD is supported and determine whether SBFD is supported in the specific cell (or frequency, frequency band).

[0334] In the first and second methods described above, the information on whether SBFD is supported may be information that indirectly indicates whether SBFD is supported by additionally setting a portion of downlink resources as uplink resources in addition to the TDD UL (uplink)-DL (downlink) resource configuration information indicating downlink slot (or symbol) resources and uplink slot (or symbol) resources of TDD (for example, SBFD resource configuration information in FIG. 15 described below), or may be information that directly indicates whether SBFD is supported.

[0335] In the present disclosure, the SBFD terminal can obtain cell synchronization by receiving a synchronization signal block during the initial cell access for connecting to a cell (or base station). The process for obtaining cell synchronization may be the same for the SBFD terminal and the existing TDD terminal. Thereafter, the SBFD terminal can determine whether the cell supports SBFD through a MIB acquisition process, a SIB acquisition process, or a random access process.

[0336] The system information for transmitting information on whether the above SBFD is supported may be system information transmitted separately from the system information for terminals supporting other versions of the standard within the cell (e.g., existing TDD terminals), and the SBFD terminal may determine whether SBFD is supported by obtaining all or part of the system information for the existing TDD terminal and the separately transmitted system information. If the SBFD terminal obtains only the system information for the existing TDD terminal or obtains system information on non-support of SBFD, the cell (or base station) may determine that it supports only TDD.

[0337] If the information on whether the above SBFD is supported is included in the system information for a terminal that supports a different version of the standard (e.g., an existing TDD terminal), the information on whether the above SBFD is supported may be inserted at the very end so as not to affect the acquisition of system information by the existing TDD terminal. If the SBFD terminal does not obtain the information on whether the above SBFD is supported inserted at the very end, or obtains information that SBFD is not supported, the SBFD terminal can determine that the cell (or base station) only supports TDD.

[0338] If the information on whether the SBFD is supported is included in the system information for a terminal supporting a different version of the standard (e.g., an existing TDD terminal), the information on whether the SBFD is supported may be transmitted through a separate PDSCH so as not to affect the acquisition of system information by the existing TDD terminal. That is, a terminal that does not support SBFD can receive a first SIB (or SIB1) including existing TDD-related system information from a first PDSCH. An SBFD-supporting terminal can receive a first SIB (or SIB) including existing TDD-related system information from a first PDSCH, and a second SIB including SBFD-related system information from a second PDSCH. Here, the first PDSCH and the second PDSCH can be scheduled as the first PDCCH and the second PDCCH, and the CRC (cyclic redundancy code) of the first PDCCH and the second PDCCH can be scrambled with the same RNTI (e.g., SI-RNTI). The search space for monitoring the second PDCCH can be obtained from the system information of the first PDSCH, and if it is not obtained (i.e., the system information of the first PDSCH does not include information about the search space), the second PDCCH can be received in the same search space as the search space of the first PDCCH.

[0339] As described above, when the SBFD terminal determines that the cell (or base station) supports only TDD, the SBFD terminal can perform random access procedures and transmit and receive data / control signals in the same manner as a conventional TDD terminal.

[0340] The base station may configure separate random access resources for each of an existing TDD terminal or an SBFD terminal (e.g., an SBFD terminal supporting duplex communication and an SBFD terminal supporting half-duplex communication), and transmit configuration information (control information or configuration information indicating time-frequency resources that can be used for PRACH) for the random access resources to the SBFD terminal through system information. The system information for transmitting information for the random access resources may be separately transmitted system information that is distinct from system information for terminals supporting different versions of standards within a cell (e.g., an existing TDD terminal).

[0341] The base station may be able to distinguish whether the TDD terminal supporting different versions of the standard performs random access or the SBFD terminal performs random access by setting separate random access resources for the TDD terminal and the SBFD terminal supporting different versions of the standard. For example, the separate random access resource set for the SBFD terminal may be a resource that the existing TDD terminal determines to be a downlink time resource, and the SBFD terminal performs random access through an uplink resource (or a separate random access resource) set to a part of the frequency of the downlink time resource, so that the base station may determine that the terminal attempting random access through the uplink resource is an SBFD terminal.

[0342] Alternatively, the base station may not set up separate random access resources for SBFD terminals, but may set up common random access resources for all terminals within the cell. In this case, configuration information for the random access resources may be transmitted to all terminals within the cell through system information, and the SBFD terminal that has received the system information may perform random access to the random access resources. Thereafter, the SBFD terminal may complete the random access process and proceed to RRC connection mode for transmitting and receiving data with the cell. After the RRC connection mode, the SBFD terminal may receive an upper layer or physical signal from the base station that can determine that some frequency resources of the downlink time resources are set uplink resources, and may perform SBFD operations, for example, transmit uplink signals on the uplink resources.

[0343] When the SBFD terminal determines that the cell supports SBFD, the terminal may transmit capability information to the base station, including at least one or more of whether the terminal supports SBFD, whether full-duplex communication or half-duplex communication is supported, and the number of transmit or receive antennas it has (or supports), thereby notifying the base station that the terminal attempting to connect is an SBFD terminal. Alternatively, when half-duplex communication support is a mandatory implementation for the SBFD terminal, whether or not the half-duplex communication is supported may be omitted from the capability information. The SBFD terminal may report the capability information to the base station through a random access procedure, may report to the base station after completing the random access procedure, or may report to the base station after proceeding to an RRC connection mode for transmitting and receiving data with the cell.

[0344] The above SBFD terminal may support half-duplex communication, which performs only uplink transmission or downlink reception at a time, like a conventional TDD terminal, or may support full-duplex communication, which performs both uplink transmission and downlink reception at a time. Accordingly, whether the above half-duplex communication or full-duplex communication is supported can be reported to the base station by the SBFD terminal through a capability report, and after the report, the base station can configure the SBFD terminal to transmit and receive using half-duplex communication or full-duplex communication. When the SBFD terminal reports the capability for the above half-duplex communication to the base station, since a duplexer generally does not exist, a switching gap may be required to change the RF between transmission and reception when operating in FDD or TDD.

[0345] FIG. 15 is a diagram illustrating an example of SBFD operation in a TDD band of a wireless communication system according to an embodiment of the present disclosure.

[0346] Fig. 15(a) illustrates a case where TDD is operated in a specific frequency band. In a cell where TDD is operated, a base station can transmit and receive signals including data / control information in downlink slots (or symbols), uplink slots (or symbols) (1501), and flexible slots (or symbols) based on settings for TDD UL-DL resource configuration information indicating downlink slot (or symbol) resources and uplink slot (or symbol) resources of TDD with an existing TDD terminal or SBFD terminal.

[0347] In Fig. 15, it can be assumed that the DDDSU slot format is set according to the TDD UL-DL resource configuration information. Here, 'D' is a slot composed entirely of downlink symbols, 'U' is a slot composed entirely of uplink symbols, and 'S' is a slot that is not 'D' or 'U', that is, a slot that includes a downlink symbol or an uplink symbol or a flexible symbol. Here, for convenience, it can be assumed that S is composed of 12 downlink symbols and 2 flexible symbols. In addition, the DDDSU slot format can be repeated according to the TDD UL-DL resource configuration information. That is, the repetition period of the TDD configuration is 5 slots (5 ms for 15 kHz SCS, 2.5 ms for 30 kHz SCS, etc.).

[0348] Next, FIGS. 15(b), 15(c) and 15(d) illustrate cases where SBFD is operated together with TDD in a specific frequency band.

[0349] Referring to FIG. 15(b), the terminal may configure a portion of the frequency band of the cell as a frequency band (1510) capable of uplink transmission. This band may be referred to as an uplink subband (UL subband). The uplink subband (UL subband) may be applied to all symbols of all slots. The terminal may transmit an uplink channel or signal scheduled for all symbols (1512) within the subband (UL subband). However, the terminal may not transmit an uplink channel or signal in a band other than the subband (UL subband).

[0350] Referring to FIG. 15(c), the terminal may set a portion of the frequency band of the cell as a frequency band (1520) capable of uplink transmission, and may set a time region in which the frequency band is activated. Here, this frequency band may be called an uplink subband (UL subband). In FIG. 15(c), the uplink subband (UL subband) is deactivated in the first slot, and the uplink subband (UL subband) may be activated in the remaining slots. Accordingly, the terminal may transmit an uplink channel or signal in the uplink subband (UL subband) (1522) of the remaining slots. Therefore, although the uplink subband (UL subband) is activated in units of slots here, whether it is activated or not may be set in units of symbols.

[0351] Referring to FIG. 15(d), a terminal may be configured with time-frequency resources capable of uplink transmission. The terminal may configure one or more time-frequency resources as time-frequency resources capable of uplink transmission. For example, some frequency bands (1532) of the first and second slots may be configured as time-frequency resources capable of uplink transmission. Additionally, some frequency bands (1533) of the third slot and some frequency bands (1534) of the fourth slot may be configured as time-frequency resources capable of uplink transmission.

[0352] In the following description, a time-frequency resource capable of uplink transmission within a downlink symbol or slot may be referred to as an SBFD resource. Furthermore, a symbol within a downlink symbol for which an uplink subband is configured may be referred to as an SBFD symbol. Furthermore, a time-frequency resource capable of downlink reception within an uplink symbol or slot may be referred to as an SBFD resource. Furthermore, a symbol within an uplink symbol for which a downlink subband is configured may be referred to as an SBFD symbol.

[0353] For convenience, in the present disclosure, a band in which downlink channels or signals can be received, excluding uplink sub-bands, is referred to as a downlink sub-band. A terminal can configure at most one uplink sub-band and at most two downlink sub-bands in one symbol. For example, a terminal can be configured with one of {uplink sub-band, downlink sub-band}, {downlink sub-band, uplink sub-band}, or {first downlink sub-band, uplink sub-band, second downlink sub-band} in the frequency domain.

[0354] FIG. 16 is a diagram illustrating an example of resource setting of SBFD of a wireless communication system according to an embodiment of the present disclosure.

[0355] Fig. 16 is an example, and the present embodiment can be equally applied to other embodiments. Referring to Fig. 16, the terminal can be configured with an uplink symbol, a downlink symbol, or a flexible symbol according to the TDD configuration. Here, the 'D' slot represents a slot in which all symbols in the slot are downlink symbols. The 'U' slot represents a slot in which all symbols in the slot are uplink symbols. The 'S' slot represents a slot that is not a 'D' slot or a 'U' slot. The terminal can be configured with a UL BWP (1620). In addition, the terminal can be configured with a UL subband (1610) within a DL symbol. In the present embodiment, it is assumed that the UL BWP includes 275 RBs, and the UL subband includes 50 RBs. It is assumed that the UL subband is not configured in the first slot. Therefore, the first slot is called a DL slot, and the symbol included in the first slot is called a DL symbol. Assume that the UL subbands are set in the second, third, and fourth slots. Therefore, the second, third, and fourth slots are called SBFD slots, and the symbols contained in the second, third, and fourth slots are called SBFD symbols. The fifth slot is an uplink slot, and the symbols contained in the fifth slot are called UL symbols.

[0356] 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 the embodiments of the present disclosure are described below using a 5G system as an example, the embodiments of the present disclosure may be applied to other communication systems having a similar technical background or channel type. For example, this may include LTE or LTE-A mobile communication and mobile communication technologies developed after 5G. Therefore, the 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 can be applied to FDD and TDD systems.

[0357] 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 overall content of the present disclosure.

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

[0359] - MIB (Master Information Block)

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

[0361] - RRC (Radio Resource Control)

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

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

[0364] - PDCCH (Physical Downlink Control Channel)

[0365] - DCI (Downlink Control Information)

[0366] - UE-specific DCI

[0367] - Group common DCI

[0368] - Common DCI

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

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

[0371] - PUCCH (Physical Uplink Control Channel)

[0372] - UCI (Uplink Control Information)

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

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

[0375] FIG. 17 is a diagram illustrating an SBFD terminal operation according to an embodiment of the present disclosure.

[0376] Base stations (1702, 1704) supporting SBFD can use some frequency bands of the same time resource for downlink transmission and other frequency bands for uplink reception. Referring to Fig. 17(a), it can be assumed that the base station supporting SBFD operates based on the resource configuration as illustrated in (1706). As an example of a terminal connected to the base station (gNB, 1702), there may be an SBFD terminal (1704) supporting half-duplex communication. The SBFD terminal (1704) can receive scheduling information (1708) including resource allocation from the base station (gNB, 1702). According to the scheduling information (1708), the terminal can receive only downlink information during slot periods from (1716) to (1718), and can transmit only uplink information during slot periods from (1712) to (1714). On the other hand, referring to FIG. 17(b), it can be assumed that a base station supporting SBFD is operated with a resource configuration such as (1728). As an example of a terminal connected to a base station (gNB, 1724), there may be an SBFD terminal (1726) supporting dual communication. The SBFD terminal (1726) can receive scheduling information (1738) including resource allocation from the base station (gNB, 1724). According to the scheduling information (1738), the terminal can simultaneously perform downlink information reception and uplink information transmission during slot periods (1740), (1742), (1744), and (1746).

[0377] FIG. 18 is a diagram illustrating an example of self-interference of a terminal in an SBFD system according to an embodiment of the present disclosure.

[0378] More specifically, FIG. 18(a) shows an example of an SBFD terminal supporting half-duplex communication, and the terminal can configure and be allocated resources (1800) from the base station. At this time, the configuration information configured for the terminal may include resources for downlink reception and resources for uplink transmission, and additionally may include beam configuration for uplink / downlink transmission and reception. Specifically, the terminal can receive a downlink channel through the configured downlink reception beam (1810) over slots (1802) to (1804) according to the configured resources (1800). In addition, the terminal can transmit an uplink channel through the configured uplink transmission beam (1812) over slots (1806) to (1808) according to the configured resources (1800). As described above, in an SBFD terminal supporting half-duplex communication, self-interference may not occur because downlink resources (1802, 1804) and uplink resources (1806, 1808) are allocated at different times.

[0379] On the other hand, Fig. 18(b) is an example of an SBFD terminal supporting dual communication, and the terminal can configure and be allocated resources (1814) from the base station. At this time, the configuration information configured for the terminal may include resources for downlink reception and resources for uplink transmission, as well as beam configurations for each transmission and reception. Specifically, the terminal can receive a downlink channel through the configured downlink reception beam (1824) over slots (1816), (1818), (1820), or (1822) according to the configured resource (1814). The terminal can transmit an uplink channel through the configured uplink transmission beam over slots (1816), (1818), (1820), or (1822) according to the configured resource (1814). At this time, the uplink transmission beam may be one of (1826), (1828), or (1830). As described above, in SBFD terminals supporting dual communication, downlink and uplink resources can be allocated at the same time. Uplink channel transmissions established within the same time resource for the terminal can cause self-interference (1832) with the reception of the established downlink channel. Since self-interference within the terminal can degrade the terminal's downlink reception performance, a solution is needed to address this issue.

[0380] In order to secure the performance of an SBFD terminal supporting dual communication, the base station can perform scheduling by considering the self-interference situation of the terminal. For example, the base station can configure self-interference measurement and reporting to identify self-interference within an SBFD terminal supporting dual communication. That is, the base station can configure the terminal with configuration information(s) for measuring self-interference and reporting the measurement result. The terminal can measure and report self-interference according to the configuration information configured by the base station. In addition, the base station can generate configuration information and scheduling information with reference to the self-interference reported by the terminal and configure and instruct the terminal. In order to secure the downlink reception performance of an SBFD terminal supporting dual communication, the base station can configure and instruct the terminal to configure and instruct a downlink-uplink beam pair (hereinafter, may be referred to as a pair for convenience of explanation) within a beam domain.

[0381] In the embodiments of the present disclosure below, for convenience, a base station supporting SBFD may be referred to as at least one of a base station or a gNB. Furthermore, an SBFD terminal supporting dual communication may be referred to as at least one of an SBFD terminal, a terminal, an SBFD UE, or a UE.

[0382] Based on self-interference measurement configuration information established by the base station, the SBFD terminal can measure self-interference and report the measurement results to the base station. The procedures for supporting this are described in detail below.

[0383] FIG. 19 illustrates an example of a flowchart of self-interference measurement and reporting between a base station and a terminal according to one embodiment of the present disclosure.

[0384] According to FIG. 19, a terminal (1904) that supports SBFD and is connected to a base station (1902) that supports SBFD can report its terminal capability to the base station (1906). The terminal capability can include information on whether the terminal supports duplex communication or half-duplex communication. The base station can receive the transmitted terminal capability and determine whether the terminal supports duplex communication or half-duplex communication. The base station (1902) can configure self-interference measurement and reporting for the SBFD terminal (1904) that supports duplex communication (1908). When the base station (1902) configures self-interference measurement for the terminal (1904), the configuration can include at least one of a configuration for downlink resources on which the terminal measures interference, or uplink resource information associated with the self-interference measurement. In addition, when the base station (1902) configures a self-interference report to the terminal (1904), it may include at least one of a configuration for an uplink resource for which the terminal reports interference, or measurement quantity information to be reported by the terminal. The base station may schedule downlink reception and uplink transmission for the terminal. The terminal may measure interference for an uplink channel (1910) transmitted by the terminal in the downlink resources configured and scheduled by the base station (1912). The base station may receive an uplink channel transmitted from the terminal (1910). At this time, the uplink channel transmitted from the terminal may be an uplink channel scheduled by the base station to the terminal to receive an actual uplink channel. Alternatively, the uplink channel transmitted from the terminal may be an uplink channel for the terminal to measure self-interference. The terminal generates information that can be reported to the base station according to the self-interference measurement and reporting configuration information configured by the base station. After this, the terminal can report self-interference measurement information to the base station according to the reporting setting information and scheduling information set by the base station (1914).The base station can check self-interference measurement information reported from the terminal, and the base station can utilize self-interference measurement information reported from the terminal when scheduling for the terminal in the future.

[0385] As mentioned above, the base station may configure self-interference measurement and reporting for the terminal, and the terminal may measure and report self-interference. Below, we will specifically explain what measurement information the base station configures for the terminal, and how the terminal reports what values ​​to the base station.

[0386] In response to a self-interference report from a terminal, the base station may configure and instruct the terminal to calculate and report a self-interference measurement value. In this case, the measurement value may be at least one of Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), and Signal to Interference Noise Ratio (SINR). In addition, the time domain operation for self-interference reporting may be defined / configured by at least one of periodic configuration, semi-persistent configuration, activation / deactivation, dynamic indication, and event triggering.

[0387] FIG. 20 is a diagram illustrating a method for setting self-interference measurement and reporting according to one embodiment of the present disclosure.

[0388] Referring to FIG. 20, a terminal may receive (or be able to receive) configuration information related to uplink transmission and downlink reception from a base station (2002). The configuration information that the base station sets for the terminal may include at least one of self-interference measurement configuration, downlink channel resource information for self-interference measurement, uplink channel resource information related to a downlink channel for self-interference measurement, and self-interference measurement value reporting configuration information. The terminal may set and receive scheduling information for uplink channel transmission, downlink channel reception, self-interference measurement, and reporting from the base station (2004). Thereafter, the terminal may determine whether self-interference measurement and reporting are set (2006). At this time, if the base station has not set or instructed self-interference measurement and reporting to the terminal (2008), the terminal may not measure self-interference and may not calculate measurement values ​​for reporting. Alternatively, if the base station has set or instructed self-interference measurement and reporting to the terminal, the terminal may measure self-interference according to the set or instructed information. The terminal can calculate a self-interference measurement value according to the constantly configured or instructed information (2010). At this time, the self-interference measurement value can be at least one of RSRP, RSRQ, or SINR. The terminal can report the calculated self-interference measurement value to the base station according to the configured or instructed reporting information (2012).

[0389] Below, the criteria for generating calculated measurement values ​​and reporting information for measurement values ​​related to self-interference by the terminal are specifically described.

[0390] According to one embodiment of the present disclosure, when a terminal generates a calculated measurement value and report information about the measurement value in relation to self-interference, the terminal may report to the base station at most Y measurement values ​​sorted in descending order among the set uplink channel resources.

[0391] More specifically, the measurement values ​​reported by the terminal to the base station may be at most Y descending sorted measurement values ​​among the measured interference uplink resources. The N measured measurement values ​​may be defined as a value of at most K bits. For example, if (1) the terminal is configured by the base station to measure self-interference from four uplink channels for one downlink channel resource, and (2) is configured to report self-interference measurement values ​​for two uplink channels among the four uplink channels for the configured self-interference measurement, the terminal may measure self-interference from the above configuration and then select two uplink resources that generate the largest self-interference. The terminal may report the two selected self-interference measurement values ​​to the base station through the defined K bits.

[0392] Additionally, according to one embodiment of the present disclosure, when a terminal generates a calculated measurement value and report information for the measurement value in relation to self-interference, the terminal may report one measurement value to the base station.

[0393] More specifically, the base station can configure one uplink resource associated with a self-interference measurement downlink resource for the terminal, and the measurement value reported by the terminal to the base station can be one self-interference measurement value. At this time, the report information transmitted by the terminal to the base station can be defined as a value of up to K bits. For example, if the terminal receives self-interference measurement configuration from one uplink channel for one downlink channel resource from the base station, the terminal can determine that self-interference measurement has been configured for one uplink channel in the self-interference measurement downlink resource. At this time, the terminal can measure self-interference from the configuration and then generate a measurement report value for one uplink resource, and the terminal can report the selected self-interference measurement report value to the base station through the defined K bits.

[0394] Additionally, according to one embodiment of the present disclosure, when the terminal generates a calculated measurement value and report information about the measurement value in relation to self-interference, the terminal may report one maximum self-interference measurement value and N differential values ​​to the base station among uplink channel resources.

[0395] More specifically, the base station can configure N+1 uplink resources associated with self-interference measurement downlink resources for the terminal, and the measurement values ​​reported by the terminal to the base station can include one maximum self-interference measurement value and a differential value compared to the N maximum self-interference measurement values. At this time, the report information transmitted by the terminal to the base station can be defined as a value of up to K bits for the maximum self-interference measurement value, and can be defined as a value of Q bits for the differential value. The bit values ​​K and Q can be the same or different. For example, when the terminal receives self-interference measurement from two uplink channels for one downlink channel resource from the base station, the terminal can determine that self-interference measurement has been configured for two uplink channels in the self-interference measurement downlink resource. At this time, the terminal can measure self-interference from the above settings, and then generate a measurement report value for one maximum self-interference measurement value and one differential value compared to the maximum measurement value, and the terminal can report the calculated maximum self-interference measurement report value to the base station through K bits and the differential value through Q bits.

[0396] In addition, according to one embodiment of the present disclosure, the base station can estimate the amount of self-interference of the terminal through CQI information reported by the terminal. That is, in response to a self-interference report from the terminal, the base station can configure and instruct the terminal to calculate and report a CQI including self-interference. When configuring or instructing the terminal to report CSI, the base station can cause the terminal to report a CQI measured and calculated in a self-interference measurement downlink channel. In this case, the frequency resource configuration of the self-interference measurement downlink channel may be the same resource as the frequency resource configuration of the CSI downlink channel regardless of self-interference. For example, the base station can receive a CQI measured and calculated in a situation where there is no self-interference from the terminal. In addition, the base station can receive a CQI measured and calculated in a situation where there is self-interference from the terminal. The base station can estimate the amount of self-interference of the terminal by comparing two CQI criteria reported in situations without self-interference and with self-interference, and the CQI index in the situation with self-interference with the CQI index in the situation without self-interference. From the perspective of the terminal, the terminal can report to the base station the CQI measured and calculated in the situation without self-interference. Furthermore, the terminal can report to the base station the CQI measured and calculated in the situation with self-interference. The two CQI criteria reported by the terminal in situations without self-interference and with self-interference, and the CQI index in the situation with self-interference with the CQI index in the situation without self-interference, can be used to estimate the amount of self-interference of the terminal.

[0397] FIG. 21 is a diagram illustrating a method of setting self-interference measurement and reporting according to one embodiment of the present disclosure.

[0398] Referring to FIG. 21, a terminal can receive configuration information related to uplink transmission and downlink reception from a base station (2102). The configuration information that the base station sets for the terminal may include at least one of self-interference measurement configuration, downlink channel resource information for self-interference measurement, uplink channel resource information related to a downlink channel for self-interference measurement, and self-interference measurement value reporting configuration information. The terminal can set and receive scheduling information for uplink channel transmission, downlink channel reception, self-interference measurement, and reporting from the base station (2104). Thereafter, the terminal can determine whether self-interference measurement and reporting are set (2106). If the base station has not set or instructed self-interference measurement and reporting to the terminal (2108), the terminal can perform CQI calculation and CSI reporting according to the set downlink channel configuration and scheduling information. Alternatively, if the base station has configured or instructed the terminal to perform CQI-based self-interference measurement and reporting, the terminal may perform CQI calculation and CSI reporting according to the configured downlink channel configuration and scheduling information (2110). At this time, the CQI calculated in operation 2110 may be a value for a channel that does not include self-interference. Thereafter, the terminal may calculate CQI including self-interference in the self-interference measurement downlink channel according to the configuration or scheduling information (2112). The terminal may report the calculated self-interference measurement value to the base station according to the configured or instructed reporting information (2014). The base station may estimate the amount of self-interference of the terminal by comparing two CQI criteria reported in situations without self-interference and in situations with self-interference, the CQI index (2110) in the situation without self-interference and the CQI index (2112) in the situation with self-interference.

[0399] In addition, according to one embodiment of the present disclosure, the base station can estimate the amount of self-interference of the terminal through a beam failure report reported from the terminal. That is, the terminal can perform a beam failure report to the base station, and the beam failure report can be used for the base station to estimate the amount of self-interference of the terminal. More specifically, when the base station configures a beam failure report to the terminal, at least one of a self-interference measurement downlink channel resource, an uplink channel resource associated with the corresponding downlink channel resource, and threshold information for determining beam failure can be configured. The terminal can perform a beam failure reporting operation according to the self-interference measurement information configured or instructed by the base station. At this time, the time domain operation of the beam failure measurement considering self-interference can be defined / configured by at least one of a periodic configuration, a semi-persistent configuration, and activation / deactivation, and a dynamic indication. Unlike the time-domain operation of beam failure measurement considering self-interference, the time-domain operation of beam failure reporting can be event-triggered. The terminal can measure self-interference based on a threshold set by the base station. If the measured value does not exceed the threshold, a beam failure report may not be performed. Alternatively, if the measured value exceeds the threshold, a beam failure report may be performed. If the base station receives a beam failure report from the terminal, it can estimate the amount of self-interference of the terminal based on the set threshold.

[0400] FIG. 22 is a diagram illustrating a method of setting self-interference measurement and reporting according to one embodiment of the present disclosure.

[0401] Referring to FIG. 22, a terminal may receive (or be able to receive) configuration information related to uplink transmission and downlink reception from a base station (2202). The configuration information that the base station sets for the terminal may include at least one of: whether beam failure recovery-based self-interference measurement is set, downlink channel resource information for self-interference measurement, uplink channel resource information associated with a downlink channel for self-interference measurement, or threshold information for self-interference measurement. The terminal may set and receive scheduling information for uplink channel transmission, downlink channel reception, self-interference measurement, and reporting from the base station (2204). Thereafter, the terminal may measure self-interference to determine whether to perform a beam failure reporting operation (2206). If beam failure reporting-based self-interference measurement is not set for the terminal from the base station, the terminal may not perform a beam failure reporting operation (2208). Alternatively, if beam failure reporting-based self-interference measurement is set for the terminal from the base station, the terminal may perform a beam failure reporting operation (2210). A terminal can measure self-interference from an uplink channel associated with a downlink channel in a self-interference measurement downlink channel resource configured by a base station (2212). At this time, if the self-interference measurement value does not exceed a threshold, the terminal can repeat self-interference measurement according to time resource configuration information configured by the base station (2214). Alternatively, if the self-interference measurement value exceeds the threshold, the terminal can report a beam failure to the base station (2216). The base station can receive a beam failure report from the terminal and estimate the amount of self-interference of the terminal based on the report and the previously configured threshold.

[0402] Below, the time domain operation method of beam failure reporting of a terminal is described.

[0403] When a base station sets a beam failure report to a terminal, a maximum of N measurement counts can be set for the terminal. The terminal can measure self-interference for the set N measurement counts during a time resource in which measurement is allowed, and count the number of times that a threshold is exceeded. At this time, if the measurement count value counted by the terminal exceeds N set for the terminal from the base station, the terminal can report a beam failure to the base station. Alternatively, if the number of self-interference measurements (measurement count value) counted by the terminal during the time resource in which measurement is allowed does not exceed N set by the base station, the terminal may not report a beam failure to the base station and may initialize the corresponding count number.

[0404] A beam failure report of a terminal may be reported by at least one uplink channel among non-contension based PRACH (physical random access channel), contension based PRACH, PUCCH (physical uplink control channel), and PUSCH (physical uplink shared channel).

[0405] Below, a method for setting self-interference measurement downlink resources for an SBFD terminal is described.

[0406] If a terminal receives self-interference reporting-related settings from a base station via higher-layer signaling, is instructed via L1 signaling, or is configured via higher-layer signaling and instructed via L1 signaling, the terminal can perform self-interference measurements. At this time, downlink resources related to self-interference measurements can be configured for the terminal, and it is necessary to define / configure what information the terminal should reference to measure self-interference.

[0407] According to one embodiment of the present disclosure, when a base station sets self-interference measurement resources for a terminal, downlink channel resource setting information for self-interference measurement can be defined by at least one of the following methods.

[0408] Method 1: The base station can configure up to N resource sets from among the downlink status information channel measurement resource sets for the terminal as the terminal's self-interference measurement resource set. At this time, up to K resources can be configured as self-interference measurement resources within the resource set configured as the self-interference measurement resource set. If the self-interference measurement resource set is configured for the terminal, the terminal can perform self-interference measurement without receiving a downlink channel including a separate downlink reference signal from the self-interference measurement resource.

[0409] The configuration information of the self-interference measurement resource may include at least one of an index for the self-interference measurement resource, a time and frequency location for the self-interference measurement resource, or a TCI-state index.

[0410] Additionally, the configuration information of the self-interference measurement resource may include uplink channel information associated with the self-interference measurement. The uplink channel information associated with the self-interference measurement resource may be at least one of a single uplink channel resource, a list including multiple uplink channel resources, or a set of uplink channel resources.

[0411] Method 2: The base station can configure up to N resource sets from among the downlink state information interference measurement sets for the terminal as self-interference measurement resource sets for the terminal. At this time, up to K resources can be configured as self-interference measurement resources within the resource sets configured as self-interference measurement resource sets. If the self-interference measurement resource set is configured for the terminal, the terminal can perform self-interference measurement without receiving a downlink channel including a separate downlink reference signal from the self-interference measurement resources.

[0412] The configuration information of the self-interference measurement resource may include at least one of an index for the self-interference measurement resource, a time and frequency location for the self-interference measurement resource, or a TCI-state index.

[0413] Additionally, the configuration information of the self-interference measurement resource may include uplink channel information associated with the self-interference measurement. The uplink channel information associated with the self-interference measurement resource may be at least one of a single uplink channel resource, a list including multiple uplink channel resources, or a set of uplink channel resources.

[0414] Method 3: The base station can configure separate configuration information for self-interference measurement downlink resources to the terminal. Up to N resources can be configured as separately configured self-interference measurement downlink resources. The base station can explicitly configure whether to perform self-interference measurement to the terminal through upper layer signaling, but can also implicitly configure whether to perform self-interference measurement to the terminal by configuring the corresponding resource (i.e., downlink resource for self-interference measurement). That is, if a separate self-interference measurement downlink resource is configured, the terminal can implicitly interpret this configuration as indicating self-interference measurement.

[0415] The above self-interference measurement resource configuration information may include at least one of an index for a self-interference measurement downlink resource, a subcarrier spacing (SCS) of the self-interference measurement downlink resource, a frequency start RB point of the self-interference measurement downlink resource, a frequency RB length of the self-interference measurement downlink resource, a time domain start symbol position of the self-interference measurement downlink resource, a time domain symbol length of the self-interference measurement downlink resource, a periodicity and offset of the self-interference measurement downlink resource, a serving cell index of the self-interference measurement downlink resource, or a TCI state index.

[0416] Additionally, the configuration information of the self-interference measurement resource may include uplink channel information associated with the self-interference measurement. The uplink channel information associated with the self-interference measurement resource may be at least one of a single uplink channel resource, a list including multiple uplink channel resources, or a set of uplink channel resources.

[0417] Below, a method for setting up a beam pair for an SBFD terminal is described.

[0418] When a base station schedules downlink and uplink channels to a terminal in the same time resource, the base station can mitigate self-interference of the terminal by utilizing the beam relationship between the downlink and uplink channels. To utilize the beam relationship between the uplink and downlink channels of the terminal, the base station can define / configure a beam pair consisting of a beam for the downlink channel and a beam for the uplink channel.

[0419] According to one embodiment of the present disclosure, a base station can define / set beam relationships between uplink and downlink channels of a terminal by making pairs between all beams scheduled for downlink reception and all beams scheduled for uplink transmission at the same time.

[0420] FIG. 23 illustrates a beam relationship between a downlink channel and an uplink channel of a terminal according to an embodiment of the present disclosure.

[0421] Referring to FIG. 23, a terminal can set and schedule downlink channel resources from a base station, and the scheduling information may include beam information (2302, 2304, or 2306) for downlink reception. In addition, the terminal can set and schedule uplink channel resources from the base station, and the scheduling information may include beam information (2308, 2310, or 2312) for uplink transmission. The base station can define / set beam pairs between uplink and downlink channels of the terminal. For example, the base station can define / set the beam relationship between the uplink and downlink channels by associating the 0th downlink reception beam (2302) in the downlink channel scheduling information scheduled at the same time as the uplink channel to the terminal, the 0th beam pair (2314) of the corresponding beam (2302) with the 0th uplink transmission beam (2308), the 1st beam pair (2316) of the corresponding beam with the 1st uplink transmission beam (2310), and the 2nd beam pair (2318) of the corresponding beam with the 2nd uplink transmission beam (2312). The base station can schedule a beam pair suitable for each channel when scheduling downlink reception and uplink transmission at the same time using the beam pair generated by the method described above.

[0422] According to one embodiment of the present disclosure, a base station can define / set a beam relationship between uplink and downlink channels of a terminal by creating a pair for beams other than an uplink transmission beam with strong self-interference with respect to a scheduling beam for downlink reception at the same time.

[0423] FIG. 24 illustrates a beam relationship between a downlink channel and an uplink channel of a terminal according to an embodiment of the present disclosure.

[0424] Referring to FIG. 24, the terminal can receive downlink channel resource configuration and scheduling from the base station, and the corresponding scheduling information may include beam information (2302, 2304, or 2306) for downlink reception. In addition, the terminal can receive uplink channel resource configuration and scheduling from the base station, and the corresponding scheduling information may include beam information (2308, 2310, or 2312) for uplink transmission. The base station can identify an uplink beam with strong self-interference through the method for measuring and reporting self-interference for the SBFD terminal described above, the method for setting self-interference reporting for the SBFD terminal, and the method for setting self-interference measurement downlink resources for the SBFD terminal. At this time, the base station can generate a beam pair excluding the uplink beam that has the greatest self-interference effect on the downlink reception beam. For example, the base station may know that the uplink transmission beam with the strongest self-interference for the 0th downlink reception beam (2402) is the 0th uplink transmission beam (2408). At this time, when generating a beam pair for the 0th downlink reception beam (2402), the base station may define / set the beam relationship between the uplink and downlink channels by setting the 0th beam pair (2416) to the 1st uplink transmission beam (2410) and the 1st beam pair (2418) to the 2nd uplink transmission beam (2412).

[0425] According to one embodiment of the present disclosure, a base station can define / set up beam relationships between uplink and downlink channels of a terminal by making pairs for a preferred (least self-interference) uplink transmission beam for scheduling beams for downlink reception at the same time.

[0426] FIG. 25 illustrates a beam relationship between a downlink channel and an uplink channel of a terminal according to an embodiment of the present disclosure.

[0427] Referring to FIG. 25, the terminal can receive downlink channel resource configuration and scheduling from the base station, and the corresponding scheduling information may include beam information (2502, 2504, or 2506) for downlink reception. In addition, the terminal can receive uplink channel resource configuration and scheduling from the base station, and the corresponding scheduling information may include beam information (2508, 2510, or 2512) for uplink transmission. The base station can know the amount of self-interference for each beam through the method for self-interference measurement and reporting for the SBFD terminal described above, the method for setting self-interference reporting for the SBFD terminal, and the method for setting self-interference measurement downlink resources for the SBFD terminal. At this time, the base station can generate a beam pair for the downlink reception beam and the uplink reception beam most suitable for the corresponding beam. For example, the base station may know that the uplink transmission beam with the weakest self-interference for the downlink reception beam number 0 (2502) is the uplink transmission beam number 1 (2510). At this time, when the base station generates a beam pair for the downlink reception beam number 0 (2502), the beam pair (2516) may be set to the uplink transmission beam number 1 (2510). Accordingly, when the base station schedules downlink transmission and uplink reception to a terminal in the same time resource, if the scheduled downlink reception beam is beam number 0 (2502), the base station may refer to the set beam pair (2516) to cause the terminal to transmit uplink using beam number 1 (2510) as the uplink transmission beam.

[0428] According to one embodiment of the present disclosure, a base station can define / set up a beam relationship between uplink and downlink channels of a terminal by making a pair for an uplink transmission beam that is restricted (with the strongest self-interference) to a scheduling beam for downlink reception at the same time.

[0429] Referring to FIG. 26, the terminal can receive downlink channel resource configuration and scheduling from the base station, and the corresponding scheduling information may include beam information (2602, 2604, or 2606) for downlink reception. In addition, the terminal can receive uplink channel resource configuration and scheduling from the base station, and the corresponding scheduling information may include beam information (2608, 2610, or 2612) for uplink transmission. The amount of self-interference for each beam can be known through the method for measuring and reporting self-interference for the SBFD terminal described above, the method for setting self-interference reporting for the SBFD terminal, and the method for setting self-interference measurement downlink resources for the SBFD terminal. At this time, the base station can generate a beam pair for the downlink reception beam and the uplink reception beam with the strongest self-interference to the corresponding beam. For example, the base station may know that the uplink transmission beam with the strongest self-interference for the downlink reception beam number 0 (2602) is the uplink transmission beam number 1 (2610). At this time, when generating a beam pair for the downlink reception beam number 0 (2602), the base station may define / set the beam relationship between the uplink and downlink channels by setting the beam pair (2616) to the uplink transmission beam number 1 (2610). Accordingly, when the base station schedules downlink transmission and uplink reception to a terminal in the same time resource, if the scheduled downlink reception beam is beam number 0 (2602), the base station may schedule an uplink beam other than beam number 1 (2610) as the uplink transmission beam for the terminal by referring to the set beam pair (2616), thereby allowing the terminal to transmit the uplink.

[0430] Below, a method for defining the beam domain operation of an SBFD terminal is described.

[0431] Based on the beam pairs established according to the method described above, the terminal can convert the uplink transmission beam according to the downlink reception beam. If the terminal has received a preferred beam pair from the base station, the terminal can convert the beam information of the uplink channel according to the beam information of the downlink channel scheduled for the same time resource.

[0432] According to one embodiment of the present disclosure, when a base station schedules a configured grant (hereinafter, CG) PUSCH to a terminal in an uplink subband, the base station can schedule the terminal to transmit an uplink signal on uplink beam 0. At this time, it is assumed that a downlink channel is not scheduled. Thereafter, the base station can schedule a downlink channel to the terminal in the same time resource in which the CG-PUSCH is transmitted. At this time, when the base station schedules the terminal to receive the downlink channel, the base station can schedule reception beam 0 as a downlink reception beam for the terminal. If the pair with downlink beam 0 set by the base station to the terminal is uplink beam 1, not uplink beam 0 set in the CG-PUSCH, the terminal can perform CG-PUSCH transmission by converting / switching uplink beam 0 to uplink beam 1.

[0433] According to one embodiment of the present disclosure, when a terminal receives a limited beam pair from a base station, the terminal can drop transmission of an uplink channel according to beam information of a downlink channel scheduled for the same time resource.

[0434] For example, when a base station schedules a CG PUSCH to a terminal in an uplink subband, the base station can schedule the terminal to transmit an uplink signal on uplink beam 0. At this time, it is assumed that a downlink channel is not scheduled. Thereafter, the base station can schedule a downlink channel to the terminal in the same time resource in which the CG-PUSCH is transmitted. At this time, when the base station schedules the terminal to receive a downlink channel, the base station can schedule receive beam 0 as the downlink receive beam for the terminal. If the pair with downlink beam 0 set by the base station to the terminal was uplink transmit beam 0, the terminal can drop the corresponding uplink transmission.

[0435] Alternatively, if a limited beam pair is set by the base station, the terminal can transmit the beam of the uplink channel using the beam scheduled immediately before the current beam, rather than dropping the transmission of the uplink channel, according to the beam information of the downlink channel scheduled for the same time resource.

[0436] More specifically, when scheduling a CG PUSCH to a terminal in an uplink subband, the base station can schedule it to be transmitted on uplink beam 0. At this time, it is assumed that a downlink channel is not scheduled. Thereafter, the base station can schedule a downlink channel to the terminal in the same time resource in which the CG-PUSCH is transmitted. When the base station schedules downlink channel reception to the terminal, the base station can schedule downlink reception beam 0. If the pair with downlink beam 0 set by the base station to the terminal was uplink transmission beam 0, the terminal can perform uplink transmission by converting to the beam state used for the uplink transmission, which was in the state immediately before being converted to transmission beam 0. That is, if receiving beam 0 and transmitting beam 0 are set as a limited beam pair, and downlink receiving beam 0 is scheduled at the same time and uplink transmitting beam 0 is scheduled, and the transmitting beam used in the uplink transmission performed before the current uplink transmission is transmitting beam 1, the transmitting beam for the current uplink transmission can be switched to transmitting beam 1, and the current uplink transmission can be performed.

[0437] Below, a method for mitigating self-interference of an SBFD terminal is described.

[0438] According to one embodiment of the present disclosure, a base station may set a minimum (frequency) interval in frequency resources between a downlink channel and an uplink channel to mitigate self-interference of a terminal. In this case, the minimum interval may be the interval between the end point of the frequency resource of an uplink channel scheduled in the same time resource and the start point of the frequency resource of the downlink channel. Alternatively, it may be the interval between the end point of the frequency resource of a downlink channel scheduled in the same time resource and the start point of the frequency resource of the uplink channel. In addition, the unit of the minimum interval may be an RB unit. The terminal may minimize self-interference caused by downlink reception from uplink transmission scheduled at the same time through the minimum interval set in RB units. However, the minimum interval may be set to N or more RBs and may be set by higher layer signaling. Alternatively, the minimum interval of N or more RBs may be set dynamically.

[0439] In order to provide more downlink transmissions to a terminal, a base station may schedule an uplink channel and a downlink channel in the same time resource at intervals less than or equal to the minimum interval described above. If, when a terminal receives a downlink channel schedule from a base station, the RB interval between the end point of an uplink channel scheduled in the same time resource and the start point of a downlink (or, the end point of a downlink channel and the start point of an uplink) is less than or equal to the configured minimum interval, the terminal may perform a self-interference mitigation operation configured by the base station.

[0440] Alternatively, the base station may set a maximum self-interference tolerance for the terminal. When the terminal measures self-interference and reaches the maximum self-interference tolerance, the terminal may perform self-interference mitigation operations set by the base station.

[0441] The self-interference mitigation operation set from the base station to the terminal may include at least one of the following operations.

[0442] Action 1: The terminal may cancel downlink reception if the measured maximum self-interference exceeds the allowable value.

[0443] Action 2: The terminal may cancel uplink transmission if the measured maximum self-interference exceeds the allowable value.

[0444] Step 3: The base station can preset another maximum uplink transmission power for the terminal. If the maximum self-interference measured by the terminal exceeds the allowable level, the terminal can change its current maximum transmission power to another preset maximum uplink transmission power.

[0445] Step 4: The base station can preset uplink power control parameters for the terminal. This power control parameter can mean reducing the current uplink transmission power by a control parameter (i.e., a back-off parameter). If the maximum self-interference measured by the terminal exceeds the allowable value, the terminal can perform uplink transmission at a power reduced by the back-off parameter from the current uplink transmission power.

[0446] Step 5: The base station can preset an MCS offset for the terminal. If the maximum self-interference measured by the terminal exceeds the allowable value, the terminal can receive the downlink channel by applying an MCS reduced by the MCS offset from the current MCS used for downlink reception.

[0447] Below, the beam decision priority method of the SBFD terminal is described.

[0448] A terminal can be scheduled for uplink channel transmission and downlink channel reception at the same time from a base station, and the terminal can change the uplink channel transmission beam and / or downlink channel reception beam of the terminal according to the priority. At this time, the change of the uplink channel transmission beam and / or downlink channel reception beam can be performed according to a preset beam determination priority. At this time, the beam determination priority can be an index value and can be set to a maximum N bit value. For example, assuming that the beam determination priority is designed using a maximum of 1 bit, an index of 0 can represent the lowest priority, and an index of 1 can represent the highest priority. Alternatively, it can be designed with information opposite to this.

[0449] According to one embodiment of the present disclosure, when scheduling uplink channel transmission and downlink channel transmission in the same time resource to a terminal, a base station may set a beam determination priority index by including it in higher layer signaling configuration information. The terminal may determine an uplink transmission beam and a downlink reception beam through the beam determination priority index set by the base station. For example, the base station may set ConfiguredGrantConfig for uplink channel configuration in the same time resource to the terminal, and may include a beam determination priority index in the configuration information. At the same time, the base station may set SPS-Config for downlink channel configuration, and may include a beam determination priority index in the configuration information. When setting ConfiguredGrantConfig configuration information to the terminal, the base station may set the beam determination priority index to 0. When setting SPS-Config configuration information to the terminal, the base station may set the beam determination priority index to 1. Through this, in the same time resource, the terminal can determine a downlink channel reception beam, and transmit the uplink channel using a beam with the least self-interference with the downlink channel reception beam among the uplink channel transmission beams associated therewith. As another example, when the base station sets the ConfiguredGrantConfig configuration information to the terminal, the beam determination priority index can be set to 1. When the base station sets the SPS-Config configuration information to the terminal, the beam determination priority index can be set to 0. Through this, the terminal can preferentially determine the uplink channel transmission beam in the same time resource. At this time, the downlink reception beam of the terminal can be determined as a downlink beam that can receive the least self-interference with respect to the associated uplink transmission beam. Alternatively, the downlink beam can be determined regardless of the uplink transmission beam.

[0450] According to one embodiment of the present disclosure, when scheduling uplink channel transmission and downlink channel reception in the same time resource for a terminal, a base station may configure a beam determination priority index by including it in higher layer signaling configuration information. The terminal may determine an uplink transmission beam and a downlink reception beam through the beam determination priority index configured by the base station. For example, the base station may configure ConfiguredGrantConfig for uplink channel configuration in the same time resource for the terminal, and may include a beam determination priority index in the configuration information. Simultaneously, the base station may configure SPS-Config for downlink channel configuration, and may include a beam determination priority index in the configuration information. When configuring ConfiguredGrantConfig configuration information for the terminal, the base station may set the beam determination priority index to 0. When configuring SPS-Config configuration information for the terminal, the base station may set the beam determination priority index to 0. If the base station indicates a beam determination priority index of 1 for uplink channel transmission through L1 signaling, the terminal may preferentially determine an uplink channel transmission beam. At this time, the downlink reception beam of the terminal may be determined as the downlink beam that can cause the least self-interference with respect to the associated uplink transmission beam. Alternatively, the downlink beam may be determined regardless of the uplink transmission beam. As another example, if the base station indicates a beam determination priority index of 1 for downlink channel reception through L1 signaling, the terminal may preferentially determine the downlink channel reception beam. At this time, the uplink channel transmission beam may be determined as the beam that causes the least self-interference with respect to the associated downlink channel reception beam.

[0451] According to one embodiment of the present disclosure, when a base station schedules an uplink channel (e.g., PUSCH transmission scheduling or aperiodic SRS transmission) to a terminal, the base station may schedule the uplink channel by including a beam determination priority index in a DCI format. For example, it is assumed that the terminal is transmitting a semi-persistent downlink channel with a beam determination priority index of 1. If the base station indicates a beam determination priority index of 1 when scheduling an uplink channel (e.g., PUSCH transmission or aperiodic SRS transmission) to the terminal at the same time, the beam determination priority of the terminal for the downlink channel may be changed to 0. Accordingly, the terminal may determine an uplink channel transmission beam according to a TCI state indicated by L1 signaling from the base station. The downlink reception beam of the terminal may be determined as a downlink beam that may receive the least self-interference with respect to an associated uplink transmission beam. Alternatively, the downlink beam may be determined regardless of the uplink transmission beam. As another example, when a base station schedules a downlink channel (e.g., PDSCH reception scheduling or aperiodic CSI-RS reception) to a terminal, the base station may schedule the downlink channel by including a beam determination priority index in the DCI format. As an example, it is assumed that a configured grant uplink channel with a beam determination priority index of 1 is being transmitted. If the base station schedules a downlink channel (e.g., PDSCH reception scheduling or aperiodic CSI-RS reception) to the terminal at the same time and indicates the beam determination priority index as 1, the terminal may change the beam determination priority for uplink channel transmission to 0. Accordingly, the terminal may determine a downlink channel reception beam according to the TCI state indicated by L1 signaling from the base station.The uplink transmission beam of the terminal may be determined as the uplink beam that causes the least self-interference with respect to the scheduled downlink reception beam.

[0452] FIG. 27 is a diagram illustrating a flowchart for terminal and base station operations according to one embodiment of the present disclosure.

[0453] First, referring to FIG. 27(a), the terminal can transmit terminal capabilities (2702) to the serving base station. The terminal can receive upper layer signaling transmitted from the base station (2704) and check whether self-interference measurement and reporting are configured and information within the configuration information. Thereafter, as previously described, the terminal can transmit an uplink channel based on the configured self-interference measurement and reporting information and measure self-interference in the self-interference measurement downlink resource in the same time resource (2706). Thereafter, the terminal can perform self-interference reporting as previously described.

[0454] Next, referring to FIG. 27(b), the base station can receive terminal capabilities (2710) from the terminal. When transmitting upper layer signaling (2712) to the terminal, the base station can transmit self-interference measurement and reporting configuration information and uplink / downlink scheduling information. Thereafter, the base station can receive the uplink channel transmitted from the terminal (2714). Thereafter, the base station can receive the self-interference report transmitted from the terminal (2716). The base station can perform scheduling with reference to the self-interference amount of the terminal reported by the terminal.

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

[0456] Referring to FIG. 28, the terminal may include a transceiver, which refers to a terminal receiving unit (2800) and a terminal transmitting unit (2810), a memory (not shown), and a terminal processing unit (2805, or a terminal control unit or processor). Depending on the communication method of the terminal described above, the transceiver units (2800, 2810), the memory, and the terminal processing unit (2805) 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.

[0457] A transceiver unit can transmit and receive signals to and from a 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.

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

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

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

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

[0462] Referring to FIG. 29, the base station may include a transceiver, which refers to a base station receiver (2900) and a base station transmitter (2910), a memory (not shown), and a base station processor (2905, or a base station control unit or processor). Depending on the communication method of the base station described above, the transceiver (2900, 2910), the memory, and the base station processor (2905) 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.

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

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

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

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

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

[0468] 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 claims or embodiments of the present disclosure.

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

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

[0471] In the specific embodiments of the present disclosure described above, components included in the disclosure 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.

[0472] Meanwhile, the embodiments of the present disclosure disclosed in the present disclosure and the 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 to fifth embodiments 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.

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

[0474] Alternatively, the drawings illustrating the method of the present disclosure may omit some components and include only some components without detracting from the essence of the present disclosure.

[0475] In addition, the method of the present disclosure 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 disclosure.

[0476] Various embodiments of the present disclosure have been described above. The foregoing description of the present disclosure is for illustrative purposes only, and the embodiments of the present disclosure are not limited to the disclosed embodiments. Those skilled in the art will appreciate that the present disclosure can be readily modified into other specific forms without altering the technical spirit or essential characteristics of the present disclosure. The scope of the present disclosure is indicated by the claims described below rather than the detailed description above, and all changes or modifications derived from the meaning and scope of the claims and their equivalents should be construed as being included within the scope of the present disclosure.

Claims

1. A method performed by a terminal in a wireless communication system, the method comprising: A step of receiving, from a base station, configuration information for a beam pair including a beam related to uplink transmission in a Subband non-overlapping Full Duplex (SBFD) slot and a beam related to downlink reception; A step of receiving information for scheduling the uplink transmission and the downlink reception in the SBFD slot from the base station; and A method comprising the step of performing the uplink transmission and the downlink reception in the SBFD slot based on a beam pair configured based on the configuration information for the beam pair.

2. In paragraph 1, A method wherein, when the beam related to the uplink transmission and the beam related to the downlink reception included in the beam pair are composed of beams having the smallest degree of interference with each other, the uplink transmission and the downlink reception in the SBFD slot are performed based on the beam related to the uplink transmission and the beam related to the downlink reception, respectively.

3. In paragraph 2, A method wherein, when the beams related to the uplink transmission and the beams related to the downlink reception included in the beam pair are configured as beams having the smallest degree of interference with each other, the uplink transmission in the SBFD slot is performed based on a beam other than the beam related to the uplink transmission, and the downlink reception is performed based on the beam related to the downlink reception.

4. In paragraph 3, A step of receiving, from the base station, setup information for interference measurement between a beam related to the uplink transmission in the SBFD slot and a beam related to the downlink reception; and A step of performing the interference measurement on the resource for the interference measurement based on the setting information for the interference measurement, A method in which the degree of interference between a beam associated with the uplink transmission and a beam associated with the downlink reception included in the beam pair is obtained based on the interference measurement.

5. A method performed by a base station in a wireless communication system, the method comprising: A step of transmitting, to a terminal, configuration information for a beam pair including a beam related to uplink transmission of the terminal in a Subband non-overlapping Full Duplex (SBFD) slot and a beam related to downlink reception of the terminal; A step of transmitting information for scheduling the uplink transmission of the terminal and the downlink reception of the terminal in the SBFD slot to the terminal; and A method comprising the step of performing reception for uplink transmission of the terminal and transmission for downlink reception of the terminal in the SBFD slot based on a beam pair configured based on setting information for the beam pair.

6. In paragraph 5, A method in which, when the beam related to the uplink transmission of the terminal included in the beam pair and the beam related to the downlink reception of the terminal are composed of beams having the smallest degree of interference with each other, the uplink transmission of the terminal and the downlink reception of the terminal in the SBFD slot are performed based on the beam related to the uplink transmission of the terminal and the beam related to the downlink reception of the terminal, respectively.

7. In paragraph 6, A method wherein, when a beam related to uplink transmission of the terminal included in the beam pair and a beam related to downlink reception of the terminal are configured as beams having the smallest degree of interference with each other, the uplink transmission of the terminal in the SBFD slot is performed based on a beam other than the beam related to uplink transmission of the terminal, and the downlink reception of the terminal is performed based on the beam related to downlink reception of the terminal.

8. In paragraph 7, A step of transmitting, to the terminal, configuration information for interference measurement between a beam related to uplink transmission of the terminal in the SBFD slot and a beam related to downlink reception of the terminal; and A method in which the degree of interference between a beam related to uplink transmission of the terminal included in the beam pair and a beam related to downlink reception of the terminal is obtained based on the interference measurement performed on the resource for the interference measurement based on the setup information for the interference measurement.

9. In a wireless communication system, the terminal comprises: transceiver; and Including a controller connected to the above transceiver, The above controller, Receive configuration information for a beam pair including a beam related to uplink transmission and a beam related to downlink reception in a Subband non-overlapping Full Duplex (SBFD) slot from a base station, Receive information from the base station for scheduling the uplink transmission and the downlink reception in the SBFD slot, A terminal configured to perform the uplink transmission and the downlink reception in the SBFD slot based on a beam pair configured based on the configuration information for the beam pair.

10. In paragraph 9, In the case where the beam related to the uplink transmission and the beam related to the downlink reception included in the beam pair are composed of beams having the smallest degree of interference with each other, the uplink transmission and the downlink reception in the SBFD slot are performed based on the beam related to the uplink transmission and the beam related to the downlink reception, respectively, of the terminal.

11. In Article 10, A terminal wherein, when the beam related to the uplink transmission and the beam related to the downlink reception included in the beam pair are configured as beams having the smallest degree of interference with each other, the uplink transmission in the SBFD slot is performed based on a beam other than the beam related to the uplink transmission, and the downlink reception is performed based on the beam related to the downlink reception.

12. In the 11th paragraph, the controller, Receive, from the base station, setup information for interference measurement between a beam related to the uplink transmission in the SBFD slot and a beam related to the downlink reception, Further configured to perform the interference measurement on the resource for the interference measurement based on the setup information for the interference measurement, A terminal, wherein the degree of interference between a beam related to the uplink transmission and a beam related to the downlink reception included in the beam pair is obtained based on the interference measurement.

13. In a wireless communication system, at a base station, the base station, transceiver; and Including a controller connected to the above transceiver, The above controller, Transmitting configuration information for a beam pair including a beam related to uplink transmission of the terminal in a Subband non-overlapping Full Duplex (SBFD) slot and a beam related to downlink reception of the terminal to the terminal, Transmitting information for scheduling the uplink transmission of the terminal and the downlink reception of the terminal in the SBFD slot to the terminal; A method for configuring reception for uplink transmission of the terminal and transmission for downlink reception of the terminal to be performed based on a beam pair configured based on setting information for the beam pair in the SBFD slot.

14. In paragraph 13, A base station, wherein, when the beam related to the uplink transmission of the terminal included in the beam pair and the beam related to the downlink reception of the terminal are configured as beams having the smallest degree of interference with each other, the uplink transmission of the terminal and the downlink reception of the terminal in the SBFD slot are performed based on the beam related to the uplink transmission of the terminal and the beam related to the downlink reception of the terminal, respectively.

15. In paragraph 14, A base station, wherein, when a beam related to uplink transmission of the terminal included in the beam pair and a beam related to downlink reception of the terminal are configured as beams having the smallest degree of interference with each other, the uplink transmission of the terminal in the SBFD slot is performed based on a beam other than the beam related to uplink transmission of the terminal, and the downlink reception of the terminal is performed based on the beam related to downlink reception of the terminal.

Images