Method and apparatus for transmission of full-duplex system in wireless communication system

Abstract

The present disclosure provides a random access method in a wireless communication system. According to various embodiments of the present disclosure, the method performed by a user equipment in a wireless communication system may comprise the steps of: receiving, from a base station, first information for configuring a resource for a first symbol and second information for configuring a resource for a second symbol; receiving, from the base station, first downlink control information (DCI) including a first sounding reference signal resource indicator (SRI) for the first symbol and / or a second SRI for the second symbol; and transmitting, to the base station, a physical uplink shared channel (PUSCH) on the first symbol and / or the second symbol, wherein the first SRI is associated with a first SRS resource before receiving the first DCI, and the symbol type of the first symbol is the same as the symbol type of the first SRS resource, and the second SRI is associated with a second SRS resource before receiving the first DCI, and the symbol type of the second symbol is the same as the symbol type of the second SRS resource.

Description

Method and device for full-duplex system transmission in wireless communication system

[0001] The present disclosure relates generally to a wireless communication system, and more particularly, to a method and apparatus for multiple-input and multiple-output (MIMO) transmission of a terminal supporting full-duplex (FD) communication in a wireless communication system.

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

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

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

[0005] In addition, standardization of 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] As described above and with the development of wireless communication systems, various services have become available, and methods for providing these services smoothly are required.

[0009] Based on the discussion described above, the present disclosure provides a device and method for MIMO (multiple-input and multiple-output) transmission of a terminal supporting SBFD (subband full duplex) communication in a wireless communication system.

[0010] According to various embodiments of the present disclosure, a method performed by a user equipment (UE) in a wireless communication system may include the steps of: receiving, from a base station, first information for setting a resource for a first symbol and second information for setting a resource for a second symbol; receiving, from the base station, a first downlink control information (DCI) including at least one of a first sounding reference signal resource indicator (SRI) for the first symbol or a second SRI for the second symbol; and transmitting, to the base station, a physical uplink shared channel (PUSCH) on at least one of the first symbol or the second symbol, wherein the first SRI is associated with a first SRS resource before receiving the first DCI, and a symbol type of the first symbol is the same as the symbol type of the first SRS resource, and the second SRI is associated with a second SRS resource before receiving the first DCI, and a symbol type of the second symbol is the same as the symbol type of the second SRS resource.

[0011] According to various embodiments of the present disclosure, a method performed by a base station in a wireless communication system may include the steps of: transmitting, to a user equipment (UE), first information for setting up a resource for a first symbol and second information for setting up a resource for a second symbol; transmitting, to the UE, a first downlink control information (DCI) including at least one of a first sounding reference signal resource indicator (SRI) for the first symbol or a second SRI for the second symbol; and receiving, from the UE, a physical uplink shared channel (PUSCH) on at least one of the first symbol or the second symbol, wherein the first SRI is associated with a first SRS resource before receiving the first DCI, and a symbol type of the first symbol is the same as the symbol type of the first SRS resource, and the second SRI is associated with a second SRS resource before receiving the first DCI, and a symbol type of the second symbol is the same as the symbol type of the second SRS resource.

[0012] Through embodiments of the present disclosure, a device and method capable of effectively providing a service in a wireless communication system are provided.

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

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

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

[0016] FIG. 3 illustrates an example of bandwidth portion settings in a wireless communication system according to one embodiment of the present disclosure.

[0017] FIG. 4 illustrates an example of setting a control region of a downlink (DL) control channel in a wireless communication system according to one embodiment of the present disclosure.

[0018] FIG. 5 illustrates the structure of a downlink control channel in a wireless communication system according to one embodiment of the present disclosure.

[0019] FIG. 6 illustrates an example of a method for a base station and a terminal to transmit and receive data in consideration of a downlink data channel and rate matching resources in a wireless communication system according to one embodiment of the present disclosure.

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

[0021] FIG. 8 illustrates an example of time axis resource allocation of PDSCH in a wireless communication system according to one embodiment of the present disclosure.

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

[0023] FIG. 10 illustrates a wireless protocol structure of a base station and a terminal in a single cell, carrier aggregation, and dual connectivity situation in a wireless communication system according to one embodiment of the present disclosure.

[0024] FIG. 11 illustrates an example of a time division duplex (TDD) configuration and a subband full duplex (SBFD) configuration according to one embodiment of the present disclosure.

[0025] FIG. 12 illustrates an example of an SBFD setting according to one embodiment of the present disclosure.

[0026] FIG. 13 illustrates an example of an antenna operation method in a TDD transmission scheme according to one embodiment of the present disclosure.

[0027] FIG. 14 illustrates an example of an antenna operation method in an SBFD transmission scheme according to one embodiment of the present disclosure.

[0028] FIG. 15 illustrates an example of multiple quasi co-located (QCL) assumptions in an SBFD transmission scheme according to one embodiment of the present disclosure.

[0029] FIG. 16 illustrates an example of transmission according to multiple-input and multiple-output (MIMO) parameters according to one embodiment of the present disclosure.

[0030] FIG. 17 illustrates the structure of a terminal in a wireless communication system according to one embodiment of the present disclosure.

[0031] FIG. 18 illustrates the structure of a base station in a wireless communication system according to one embodiment of the present disclosure.

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

[0033] 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 ensure that the gist of the present disclosure is conveyed more clearly without obscuring it by omitting unnecessary explanations.

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

[0035] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided only to ensure that the disclosure of the present disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Like reference numerals designate like elements throughout the specification. In addition, when describing the present disclosure, if a specific description of a related function or configuration is determined to unnecessarily obscure the gist of the present disclosure, the 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, the definitions should be made based on the contents throughout the specification.

[0036] 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, the downlink (DL) refers to a wireless transmission path of a signal transmitted from a base station to a terminal, and the uplink (UL) refers to a wireless transmission path of a signal transmitted from a terminal to a base station. In addition, although the LTE or LTE-A 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, the 5th generation mobile communication technology developed after LTE-A (e.g., 5G NR (new radio)) may be included here, and the 5G below may also be a concept that includes the existing LTE (long-term evolution), LTE-A (advanced), and other similar services. In addition, the present disclosure may be applied to other communication systems with some modifications within a range that does not significantly deviate from the scope of the present disclosure, as determined by a person having skilled technical knowledge.

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

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

[0039] 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'. Additionally, the components and '~parts' may be implemented to activate one or more CPUs within a device or secure multimedia card. In addition, in an embodiment, the '~parts' may include one or more processors.

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

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

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

[0043] 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 provide not only the peak data rate but also the 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.

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

[0045] URLLC is a cellular-based wireless communication service used for specific mission-critical purposes. For example, it can be considered as a service used for remote control of robots or machinery, industrial automation, unmanned aerial vehicles, remote health care, and emergency alerts. Therefore, the communication provided by URLLC must 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, 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.

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

[0047] According to various embodiments of the present disclosure, various schemes for MIMO transmission in a subband full duplex (SBFD) system are described. According to various embodiments, the number of MIMO layers for a downlink symbol of a terminal may be different from the number of MIMO layers for an SBFD symbol. Accordingly, different MIMO transmission modes need to be set for each symbol type, and the terminal can receive a physical downlink shared channel (PDSCH) or transmit a physical uplink shared channel (PUSCH) based on the MIMO setting for each symbol.

[0048] [NR time-frequency resources]

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

[0050] FIG. 1 illustrates the basic structure of the time-frequency domain in a wireless communication system according to one embodiment of the present disclosure. More specifically, FIG. 1 illustrates the basic structure of the time-frequency domain, which is a wireless resource region where data or control channels are transmitted in a 5G system.

[0051] 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) in the time axis and 1 subcarrier (103) in the frequency axis. In the frequency domain (For example, 12) consecutive REs can form one resource block (RB) (104).

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

[0053] FIG. 2 illustrates an example of a structure of a frame (200), a subframe (201), and a 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 (for example, 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.

[0054] Referring to FIG. 2, cases where the subcarrier spacing setting value is μ=0 (204) and μ=1 (205) are illustrated. When μ=0 (204), 1 subframe (201) can be composed of 1 slot (202), and when μ=1 (205), 1 subframe (201) can be composed of 2 slots (203). That is, depending on the setting value μ for the subcarrier spacing, the number of slots per 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.

[0055] μ 0141011142022144043148084141601651432032

[0056] [Bandwidth Part (BWP)]

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

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

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

[0060]

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

[0062] According to some embodiments, a terminal before RRC (Radio Resource Control) connection can receive 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, through the MIB during the initial access phase, configuration information about a control region (Control Resource Set, CORESET) and a search space where a physical downlink control channel (PDCCH) for receiving system information (e.g., Remaining System Information (RMSI) or System Information Block 1 (SIB1)) required for initial access can be transmitted. The control region and search space configured by the MIB can each be regarded as identifier (Identity, ID) 0. The base station can notify the terminal of configuration information such as frequency allocation information, time allocation information, and numerology for control region #0 through the MIB. Additionally, the base station can notify the terminal of the monitoring cycle and occasion settings for control area #0 (e.g., search space #0) via the MIB. The terminal can consider the frequency range designated as control area #0 obtained from the MIB as the initial bandwidth portion for initial access. At this time, the identifier (ID) of the initial bandwidth portion can be considered as 0.

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

[0064] In some embodiments, if the bandwidth supported by the terminal is smaller than the system bandwidth, the base station can support this by configuring the bandwidth portion. For example, the base station can configure the bandwidth portion frequency position (e.g., configuration information 2) for the terminal, thereby allowing the terminal to transmit and receive data at a specific frequency position within the system bandwidth.

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

[0066] Furthermore, in some embodiments, for the purpose of reducing power consumption of the terminal, the base station may configure bandwidth portions with different bandwidth sizes for the terminal. For example, if the terminal supports a very large bandwidth (e.g., 100 MHz bandwidth) 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 (e.g., 20 MHz bandwidth portion) for the terminal. In a situation where there is no traffic, the terminal may perform monitoring operations in the 20 MHz bandwidth portion, and when data is generated, it may transmit and receive data using the 100 MHz bandwidth portion according to the instructions of the base station.

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

[0068] [Bandwidth Part (BWP) Change]

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

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

[0071]

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

[0073] According to the requirement for bandwidth part change delay time mentioned above, when a terminal receives DCI including a bandwidth part change indicator in slot n, it changes to a new bandwidth part indicated by the bandwidth part change indicator in slot n+T. BWP It can be completed at a later time. In addition, the terminal can perform transmission and reception for the data channel scheduled by the corresponding DCI in the changed new bandwidth portion. If the base station wants to schedule a data channel in the new bandwidth portion, it should set the bandwidth portion change delay time (T) of the terminal. BWP ), time domain resource allocation for the data channel can be determined by considering the bandwidth portion change delay time. For example, when the base station schedules a data channel with a new bandwidth portion, the data channel can be scheduled after the bandwidth portion change delay time in the method of determining 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.

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

[0075] [SS / PBCH block]

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

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

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

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

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

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

[0082] The terminal can detect PSS and SSS in the initial access stage, and decode PBCH. The terminal can obtain MIB from PBCH and set control region (Control Resource Set, CORESET) #0 (for example, it may correspond to a control region with a control region index of 0) therefrom. The terminal can assume that the selected SS / PBCH block and the DMRS (Demodulation Reference Signal) transmitted in control region #0 are QCL (Quasi Co Location), and can perform monitoring for control region #0. The terminal can receive system information using 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 which block the terminal has selected among each SS / PBCH block and monitor the control region #0 associated with it.

[0083] [PDCCH: DCI related]

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

[0085] In a 5G system, scheduling information for uplink data (or physical uplink shared channel (PUSCH)) or downlink data (or physical downlink shared channel (PDSCH)) is transmitted from a base station to a terminal via DCI. The terminal can monitor a DCI format for fallback and a DCI format for non-fallback for the PUSCH or PDSCH. The fallback DCI format can be composed of fixed fields predefined between the base station and the terminal, and the non-fallback DCI format can include configurable fields.

[0086] DCI can be transmitted over the Physical Downlink Control Channel (PDCCH) after going through the channel coding and modulation process. A Cyclic Redundancy Check (CRC) can be 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. Here, different RNTIs can be used depending on the purpose of the DCI message (e.g., UE-specific data transmission, power control command, or random access response). For example, the RNTI can be included in the CRC calculation process rather than being transmitted explicitly. A UE that receives a DCI message transmitted over the PDCCH can check the CRC using the assigned RNTI, and if the CRC check result is correct, the UE can know that the message was transmitted to the UE.

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

[0088] 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 the information in Table 4 below.

[0089]

[0090] 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 the information in Table 5 below.

[0091]

[0092]

[0093] 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 the information in Table 6 below.

[0094]

[0095] 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 the information in Table 7 below.

[0096]

[0097]

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

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

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

[0101] The base station can configure the control region for the terminal in the aforementioned 5G through higher-layer signaling (e.g., system information, master information block (MIB), radio resource control (RRC) signaling). Configuring the control region for the terminal may mean providing information such as the control region identifier (Identity), frequency location of the control region, and symbol length of the control region. For example, the information configuring the control region may include the information in Table 8.

[0102]

[0103] In Table 8, the tci-StatesPDCCH (e.g., referred to as TCI (transmission configuration indicator) state for convenience) 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.

[0104] FIG. 5 illustrates the structure of a downlink control channel in a wireless communication system according to one embodiment of the present disclosure. More specifically, FIG. 5 illustrates an example of the basic units of time and frequency resources that constitute a downlink control channel that can be used in 5G.

[0105] According to FIG. 5, the basic unit of time and frequency resources constituting a control channel can be referred to as a REG (Resource Element Group, 503), and the REG (503) can be defined as 1 OFDM symbol (501) on the time axis and 1 PRB (Physical Resource Block, 502) (e.g., 12 subcarriers) on the frequency axis. A base station can concatenate REGs (503) to configure a downlink control channel allocation unit.

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

[0107] The basic unit of the downlink control channel illustrated in FIG. 5 (e.g., REG (503)) may include both REs to which DCI is mapped and regions to which DMRS (505), which is a reference signal for decoding the REs, is mapped. As in FIG. 5, three DMRSs (505) may be transmitted within one REG (503). The number of CCEs required to transmit a PDCCH may be 1, 2, 4, 8, or 16 depending on the aggregation level, 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.

[0108] A terminal must detect a signal without knowing information about the downlink control channel. For blind decoding, a search space representing a set of CCEs can be defined. The search space can refer to a set of downlink control channel candidates, which are CCEs that the terminal should attempt to decode at a given aggregation level. There can be multiple aggregation levels that create a single bundle of 1, 2, 4, 8, or 16 CCEs, and thus the terminal can have multiple search spaces. A search space set can be defined as a set of search spaces at all configured aggregation levels.

[0109] Search spaces can be classified 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 for system information or paging messages. For example, a UE can receive PDSCH scheduling allocation information for transmitting a SIB, including cell operator information, 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, need to receive the PDCCH, it can be defined as a set of pre-arranged CCEs. A UE can receive scheduling allocation information for a UE-specific PDSCH or PUSCH by searching the UE-specific search space of the PDCCH. The UE-specific search space can be defined UE-specifically based on the identity of the UE and a function of various system parameters.

[0110] In 5G, parameters for the search space for PDCCH can be configured from the base station to the terminal via higher-layer signaling (e.g., SIB, MIB, RRC signaling). For example, the base station can configure the number of PDCCH candidates at each aggregation level L, the monitoring period for the search space, the monitoring occasion for each symbol within the slot for the search space, the search space type (common search space or terminal-specific search space), the combination of DCI format and RNTI to be monitored in the corresponding search space, or the control region index to be monitored for the search space, etc. to the terminal. For example, the parameters for the search space for PDCCH can include the information in Table 9.

[0111]

[0112] 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. The base station 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.

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

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

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

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

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

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

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

[0120] In a terminal-specific search space, the following combinations of DCI formats and RNTIs may be monitored, but these are only examples and are not limited to the examples below.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0134] The aforementioned specified DCI formats may follow the definitions as shown in the example in Table 10.

[0135]

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

[0137] [Mathematical Formula 1]

[0138]

[0139] - L: Integration level

[0140] - n CI : Carrier Index

[0141] - N CCE,p : Total number of CCEs present within control region p

[0142] - : slot index

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

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

[0145] - i = 0, ..., L -1

[0146] - =(A p · )mod D, Y p,-1 =n RNTI ≠0, A p =39827 for pmod3=0, A p =39829 for pmod3=1, A p =39839 for pmod3=2, D=65537

[0147] - n RNTI : Terminal identifier

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

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

[0150] In 5G, since multiple search space sets can be configured with different parameters (e.g., parameters in Table 9), the set of search space sets monitored by a terminal at each point in time can be different. For example, if search space set #1 is 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 can monitor either search space set #1 or search space set #2 in a specific slot.

[0151] FIG. 6 illustrates an example of a method for a base station and a terminal to transmit and receive data in consideration of a downlink data channel and rate matching resources in a wireless communication system according to one embodiment of the present disclosure.

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

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

[0154] 5G supports granularity at the "RB symbol level" and "RE level" by setting the aforementioned rate matching resources on the terminal. More specifically, the following configuration methods can be followed.

[0155] RB symbol level

[0156] A terminal can receive up to four RateMatchPatterns for each bandwidth segment via upper-layer signaling. A single RateMatchPattern can include the following. Of course, the examples below are not limited.

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

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

[0159] RE level

[0160] The terminal can receive the following information via upper-layer signaling. Of course, the information may not be limited to the examples below.

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

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

[0163] [PDSCH / PUSCH: Frequency Resource Allocation Related]

[0164] FIG. 7 illustrates an example of frequency-axis resource allocation for a physical downlink shared channel (PDSCH) in a wireless communication system according to an embodiment of the present disclosure. More specifically, FIG. 7 illustrates an example of frequency-axis resource allocation for a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) in a wireless communication system according to an embodiment of the present disclosure.

[0165] Figure 7 illustrates three frequency axis resource allocation methods, type-0 (700), type-1 (705), and dynamic switch (710), which can be set through an upper layer in an NR wireless communication system.

[0166] Referring to Fig. 7, if the terminal is set to use only type-0 resource allocation through upper layer signaling (700), some downlink control information (DCI) that allocates PDSCH / PUSCH to the terminal is N RBG It may contain a bitmap consisting of N bits. RBG can mean the number of RBGs (resource block groups) determined as shown in [Table 11] below according to the BWP size allocated by the BWP indicator and the upper layer parameter rbg-Size, and data can be transmitted to the RBG indicated as 1 by the bitmap.

[0167]

[0168] The size of the BWP may include the number of RBs included in the BWP. More specifically, when type-0 resource allocation is indicated, the length of the frequency domain resource assignment (FDRA) field of the DCI received by the terminal is the number of RBGs (N RBG ) and It can be. Here the first RBG is It can contain RBs of the dog, and the last RBG is On the other hand, It may contain RBs of dogs, otherwise, may contain RBs. The remaining RBGs may contain P RBs, where P may be the number of nominal RBGs determined according to Table 11.

[0169] If the terminal is configured to use only type-1 resource allocation through upper layer signaling (705), the DCI that allocates PDSCH / PUSCH to the terminal is may include frequency domain resource allocation information (FDRA) consisting of bits. Here, may be the number of RBs included in the BWP. Through this, the base station can set the starting VRB (720) and the length of frequency axis resources (725) allocated sequentially therefrom.

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

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

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

[0173] 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 the PDSCH, and a table with up to maxNrofUL-Allocations=16 entries can be set up for the PUSCH. In one embodiment, the time domain resource allocation information may include PDCCH-to-PDSCH slot timing (the time interval in slot units between the time point at which a PDCCH is received and the time point at which a PDSCH scheduled by the received PDCCH is transmitted, denoted as K0), PDCCH-to-PUSCH slot timing (the time interval in slot units between the time point at which a PDCCH is received and the time point at which a PUSCH scheduled by the received PDCCH is transmitted, denoted as K2), information on the position and length of the start symbol for which a PDSCH or PUSCH is scheduled within a slot, the mapping type of the PDSCH or PUSCH, etc. For example, information such as [Table 12] or [Table 13] below may be transmitted from the base station to the terminal.

[0174]

[0175]

[0176] 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., it may be 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.

[0177] FIG. 8 illustrates an example of time axis resource allocation of PDSCH in a wireless communication system according to one embodiment of the present disclosure.

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

[0179] FIG. 9 illustrates 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 one embodiment of the present disclosure.

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

[0181] [PUSCH: Transmission Method Related]

[0182] Below, the scheduling method for PUSCH transmission is described. PUSCH transmission can be dynamically scheduled by the UL grant in the DCI or can operate by configured grant Type 1 or Type 2. Dynamic scheduling instructions for PUSCH transmission can be enabled in DCI format 0_0 or 0_1.

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

[0184]

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

[0186] 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. When a UE is instructed to schedule a PUSCH transmission via DCI format 0_0, the UE can perform beam configuration for PUSCH transmission using pucch-spatialRelationInfoID corresponding to a UE-specific PUCCH resource corresponding to the minimum ID within an activated uplink BWP within the serving cell. PUSCH transmission can be based on a single antenna port. The UE may not expect scheduling for PUSCH transmission via DCI format 0_0 within a BWP where a PUCCH resource including pucch-spatialRelationInfo is not configured. If the UE does not configure txConfig in pusch-Config of [Table 15], the UE may not expect to be scheduled with DCI format 0_1.

[0187]

[0188] Hereinafter, codebook-based PUSCH transmission is described. Codebook-based PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1, and can operate semi-statically 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, a UE can determine a precoder for PUSCH transmission based on the SRS Resource Indicator (SRI), the Transmit Precoding Matrix Indicator (TPMI), and the transmission rank (e.g., the number of PUSCH transmission layers).

[0189] 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 the SRI through the DCI, the SRS resource indicated by the SRI can refer to an SRS resource corresponding to the SRI among the SRS resources transmitted before the PDCCH containing the SRI. The TPMI and transmission rank can be given through the precoding information and number of layers fields in the DCI or configured through the precodingAndNumberOfLayers higher-level signaling. The TPMI can be used to indicate the precoder applied to the PUSCH transmission. When the UE is configured with one SRS resource, the TPMI can be used to indicate the precoder to be applied to the configured one SRS resource. When a terminal is configured with multiple SRS resources, TPMI can be used to indicate the precoder to be applied in the SRS resource indicated through SRI.

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

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

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

[0193] Hereinafter, non-codebook based PUSCH transmission is described. Non-codebook based PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1 and can operate semi-statically by 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.

[0194] 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 on a precoder for SRS transmission through measurements on the NZP CSI-RS resource connected to the SRS resource set. If the difference between the last received symbol of the aperiodic NZP CSI-RS resource connected to the SRS resource set and the first symbol of the aperiodic SRS transmission at the UE is less than 42 symbols, the UE may not expect that information on the precoder for SRS transmission is updated.

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

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

[0197] 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. The SRI can be indicated through the SRS resource indicator field in the DCI or can be configured through the srs-ResourceIndicator, which is a higher-level 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 can refer to an SRS resource corresponding to the SRI among the SRS resources transmitted before the PDCCH containing the SRI. The UE can use one or more SRS resources for SRS transmission. The maximum number of SRS resources that can be simultaneously transmitted in the same symbol within one SRS resource set and the maximum number of SRS resources can be determined by the UE capability reported by the UE to the base station. SRS resources transmitted simultaneously by the UE can occupy the same RB. The UE can configure 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.

[0198] A base station can transmit one NZP-CSI-RS associated with an SRS resource set to a terminal. The terminal can calculate a precoder to use when transmitting one or more SRS resources within the SRS resource set based on the result measured upon reception of the NZP-CSI-RS. The terminal can apply the calculated precoder when transmitting one or more SRS resources within the SRS resource set with usage set to 'nonCodebook' to the base station. The base station can select one or more SRS resources from the received one or more SRS resources. In non-codebook-based PUSCH transmission, the SRI can indicate an index that can express a combination of one or more SRS resources. The SRI can be included in the DCI. The number of SRS resources indicated by the SRI transmitted by the base station can be the number of PUSCH transmission layers. The terminal can transmit the PUSCH by applying the precoder applied to the SRS resource transmission for each layer.

[0199] [CA / DC related]

[0200] FIG. 10 illustrates a wireless protocol structure of a base station and a terminal in a single cell, carrier aggregation, and dual connectivity situation according to one embodiment of the present disclosure.

[0201] Referring to FIG. 10, the wireless protocol of the next-generation mobile communication system may be composed of NR SDAP (service data adaptation protocol) (1025, 1070), NR PDCP (packet data convergence protocol) (1030, 1065), NR RLC (radio link control) (1035, 1060), and NR MAC (medium access control) (1040, 1055) in the terminal and NR base station, respectively.

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

[0203] - Transfer of user plane data

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

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

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

[0207] For an SDAP layer device, the terminal can be configured by an 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. When the SDAP header is configured, the RRC message can instruct the terminal to update or reset the mapping information for the QoS flow and data bearer of the uplink and downlink using the NAS reflective QoS 1-bit indicator and the AS reflective QoS 1-bit indicator in the SDAP header. 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.

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

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

[0210] - User data transfer function

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

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

[0213] - PDCP PDU reordering for reception

[0214] - Duplicate detection of lower layer SDUs

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

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

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

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

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

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

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

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

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

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

[0225] - Re-segmentation of RLC data PDUs

[0226] - Reordering of RLC data PDUs

[0227] - Duplicate detection function

[0228] - Protocol error detection

[0229] - RLC SDU discard function

[0230] - RLC re-establishment function

[0231] The in-sequence delivery function of the NR RLC device described above may refer to a 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 multiple RLC SDUs when an original RLC SDU is received divided into multiple RLC SDUs. The in-sequence delivery function of the NR RLC device may include a function of reordering the received RLC PDUs based on the RLC SN (sequence number) or PDCP SN (sequence number), and may include a function of recording lost RLC PDUs by rearranging the order. The in-sequence delivery function of the NR RLC device may include a function of reporting a status on lost RLC PDUs to the transmitting side, and may include 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. 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 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 (e.g., in the order of arrival, regardless of the order of the sequence number) and delivered to the PDCP device regardless of the order (out-of-sequence delivery).The sequential forwarding function of NR RLC devices can receive segments that are stored in the buffer or will be received later, reassemble them into a complete RLC PDU, process them, and forward them to the PDCP device. The NR RLC layer may not include a concatenation function, and the above-described functions can be performed in the NR MAC layer or replaced with the multiplexing function of the NR MAC layer.

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

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

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

[0235] - Multiplexing / demultiplexing of MAC SDUs

[0236] - Scheduling information reporting function

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

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

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

[0240] - MBMS service identification function

[0241] - Transport format selection function

[0242] - Padding function

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

[0244] The above-described wireless protocol structure may have various detailed structures depending on the carrier (or cell) operation method. According to one embodiment, when a base station transmits data to a terminal based on a single carrier (or cell), the base station and the terminal may use a protocol structure having a single structure for each layer (1010). When a base station transmits data to a terminal based on carrier aggregation (CA) using multiple carriers in a single TRP, the base station and the terminal may use a protocol structure having a single structure up to the RLC but multiplexing the PHY layer through the MAC layer (1020). According to another embodiment, when a base station transmits data to a terminal based on dual connectivity (DC) using multiple carriers in multiple TRPs, the base station and the terminal may use a protocol structure having a single structure up to the RLC but multiplexing the PHY layer through the MAC layer (1030).

[0245] Referring to the above-described PDCCH and beam configuration-related descriptions, the current Rel-15 and Rel-16 NR do not support repeated PDCCH transmission, making it difficult to achieve the required reliability in scenarios requiring high reliability, such as URLLC. The present invention provides a method for repeated PDCCH transmission through multiple transmission and reception points (TRPs), thereby improving the reliability of PDCCH reception by a terminal. The specific method is described in detail in the embodiments below.

[0246] 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 (frequency division duplex) and TDD (time division duplex) systems. In the present disclosure below, upper signaling (or upper layer signaling) refers to a signal transmission method in which a downlink data channel of a physical layer of a base station is used to transmit a signal to a terminal, or an uplink data channel of a physical layer of a terminal is used to transmit a signal to a base station, and may also be referred to as RRC signaling, PDCP signaling, or a MAC (medium access control) control element (MAC control element, MAC CE).

[0247] 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 scramble the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied with a specific RNTI, or assuming cooperative communication is applied in a specific section indicated by a higher layer. For the convenience of the following description, a case in which the terminal receives a PDSCH to which cooperative communication is applied based on conditions similar to the above may be referred to as an NC-JT case.

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

[0249] In the present disclosure below, the above-described 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.

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

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

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

[0253] - MIB (Master Information Block)

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

[0255] - RRC (Radio Resource Control)

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

[0257] Additionally, L1 signaling may include signaling corresponding to at least one or a combination of one or more of the signaling methods using the physical layer channels or signaling below.

[0258] - PDCCH (Physical Downlink Control Channel)

[0259] - DCI (Downlink Control Information)

[0260] - UE-specific DCI

[0261] - Group common DCI

[0262] - Common DCI

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

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

[0265] - PUCCH (Physical Uplink Control Channel)

[0266] - UCI (Uplink Control Information)

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

[0268] In the present disclosure below, the above-described 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.

[0269] [SBFD related]

[0270] Meanwhile, 3GPP is discussing subband full duplex (SBFD) 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 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 reducing feedback delay by receiving feedback from the terminal regarding downlink transmissions using the expanded uplink resources. 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).

[0271] - As a 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 SBFD described above. Frame structure type 2 may be defined to be supported in a specific frequency or frequency band. Alternatively, the base station may indicate to the terminal whether SBFD is supported through system information. The SBFD terminal may receive the system information including whether SBFD is supported, and determine whether SBFD is supported in a specific cell (or frequency, frequency band).

[0272] - As a 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. According to 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 or not through system information. The SBFD terminal can receive the system information including whether SBFD is supported and determine whether SBFD is supported in a specific cell (or frequency, frequency band).

[0273] In the first and second methods described above, information on whether SBFD is supported may include, in addition to the TDD UL (uplink)-DL (downlink) resource configuration information indicating TDD downlink slot (or symbol) resources and uplink slot (or symbol) resources, information that indirectly indicates whether SBFD is supported by configuring a portion of downlink resources as uplink resources (e.g., SBFD resource configuration information in FIG. 11 described below), or information that directly indicates whether SBFD is supported.

[0274] In the present disclosure, an SBFD terminal can acquire cell synchronization by receiving a synchronization signal block during initial cell access to connect to a cell (or base station). The process of acquiring cell synchronization can be applied equally to both SBFD terminals and existing TDD terminals. Thereafter, the SBFD terminal can determine whether the cell supports SBFD through MIB acquisition, SIB acquisition, or random access procedures.

[0275] According to one embodiment, the system information for transmitting information on whether SBFD is supported may be system information transmitted separately from system information for terminals supporting a different version of the standard within the cell (e.g., existing TDD terminals). The SBFD terminal may determine whether SBFD is supported by obtaining all or part of the system information transmitted separately from the system information for the existing TDD terminals. If the SBFD terminal obtains only the system information for the existing TDD terminals or obtains system information on non-support of SBFD, the SBFD terminal may determine that the cell (or base station) supports only TDD.

[0276] In one embodiment, when information on whether SBFD is supported is included in system information for a terminal supporting a different version of the standard (e.g., a legacy TDD terminal), the information on whether SBFD is supported may be inserted at the very end so as not to affect the acquisition of system information by the legacy TDD terminal. If the SBFD terminal does not obtain the information on whether SBFD is supported inserted at the very end, or obtains information indicating that SBFD is not supported, the SBFD terminal may determine that the cell (or base station) only supports TDD.

[0277] In one embodiment, when information on whether SBFD is supported is included in system information for a terminal supporting a different version of the standard (e.g., a legacy TDD terminal), the information on whether SBFD is supported may be transmitted via a separate PDSCH so as not to affect acquisition of system information by the legacy TDD terminal. For example, a terminal that does not support SBFD may receive a first SIB (or SIB1) including legacy TDD-related system information on a first PDSCH. An SBFD-supporting terminal may receive a first SIB (or SIB) including legacy TDD-related system information on a first PDSCH, and a second SIB including SBFD-related system information on a second PDSCH. Here, the first PDSCH and the second PDSCH may be scheduled as the first PDCCH and the second PDCCH, and the CRCs (cyclic redundancy codes) of the first PDCCH and the second PDCCH may 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 (for example, if 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.

[0278] As described above, when an SBFD terminal determines that a 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.

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

[0280] According to one embodiment, the base station can 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 supporting different versions of the standard and the SBFD terminal. 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 can perform 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 the base station can determine that the terminal attempting random access in the uplink resource is an SBFD terminal.

[0281] According to one embodiment, the base station may configure a common random access resource for all terminals within a cell without configuring a separate random access resource for the SBFD terminal. In this case, configuration information for the random access resource 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 on the random access resource. Thereafter, the SBFD terminal may complete the random access process and proceed to an 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 a part of the frequency resource of the downlink time resource is configured as an uplink resource, and accordingly perform an SBFD operation (e.g., transmitting an uplink signal on the uplink resource).

[0282] According to one embodiment, when an SBFD terminal determines that a cell supports SBFD, the SBFD terminal may notify the base station that the terminal attempting to connect is an SBFD terminal by transmitting capability information to the base station, the capability information including at least one of whether the terminal supports SBFD, whether the terminal supports full-duplex communication or half-duplex communication, or the number of transmit or receive antennas that the terminal has (or supports). Alternatively, if half-duplex communication support is a mandatory implementation for the SBFD terminal, whether the terminal supports half-duplex communication may be omitted from the capability information. The SBFD terminal may report 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.

[0283] In one embodiment, an SBFD terminal may support half-duplex communication, which performs only uplink transmission or downlink reception at certain moments, like a conventional TDD terminal, or may support full-duplex communication, which performs both uplink transmission and downlink reception at certain moments. Accordingly, an SBFD terminal may report to a base station whether it supports half-duplex communication or full-duplex communication through a capability report. After the report, the base station may configure the SBFD terminal to transmit and receive using half-duplex communication or full-duplex communication. When an SBFD terminal reports a capability for half-duplex communication to a base station, a switching gap may be required to change the RF between transmission and reception when operating in FDD or TDD, since a duplexer is generally not present.

[0284] FIG. 11 illustrates an example of a time division duplex (TDD) configuration and a subband full duplex (SBFD) configuration according to one embodiment of the present disclosure. More specifically, FIG. 11 illustrates an example of SBFD operating in a TDD band of a wireless communication system to which the present disclosure is applied.

[0285] In Fig. 11 (a), a case where TDD is operated in a specific frequency band is illustrated. In a cell where TDD is operated, a base station can transmit and receive signals including data / control information in a downlink slot (or symbol), an uplink slot (or symbol) (1101), and a flexible slot (or symbol) based on settings according to TDD UL-DL resource configuration information indicating TDD downlink slot (or symbol) resources and uplink slot (or symbol) resources with an existing TDD terminal or an SBFD terminal.

[0286] In one embodiment, it may be assumed that the DDDSU slot format is configured according to the TDD UL-DL resource configuration information in FIG. 11. Here, 'D' represents a slot composed entirely of downlink symbols, 'U' represents a slot composed entirely of uplink symbols, and 'S' may represent a slot other than 'D' or 'U' (e.g., a slot including downlink symbols or uplink symbols or including flexible symbols). For convenience, it may be assumed that S comprises 12 downlink symbols and 2 flexible symbols, but this is merely an example and is not limited to the above-described example. The DDDSU slot format may be repeated according to the TDD UL-DL resource configuration information. For example, the repetition period of the TDD configuration may include 5 slots (e.g., 5 ms for 15 kHz SCS, 2.5 ms for 30 kHz SCS, etc.).

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

[0288] Referring to (b) of FIG. 11, the terminal may configure a portion of the frequency band of the cell as a frequency band (1110) capable of uplink transmission. Such a 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 (1112) within the uplink subband (UL subband). However, the terminal cannot transmit an uplink channel or signal in a band other than the uplink subband (UL subband).

[0289] Referring to (c) of Fig. 11, the terminal may set some of the frequency bands of the cell as frequency bands (1120) capable of uplink transmission, and may set a time region in which the frequency bands are activated. Here, the frequency bands described above may be called uplink subbands (UL subbands). Referring to (c) of Fig. 11, the uplink subband (UL subband) on the first slot may be deactivated, and the uplink subbands (UL subbands) on the remaining slots may be activated. Accordingly, the terminal may transmit an uplink channel or signal on the uplink subbands (UL subbands) (1122) of the remaining slots. That is, although (c) of Fig. 11 illustrates an example in which the uplink subband (UL subband) is activated on a slot-by-slot basis, this is merely an example, and it is of course possible to set whether or not to activate it on a symbol-by-symbol basis.

[0290] Referring to (d) of FIG. 11, the 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, the terminal may configure some frequency bands (1132) of the first and second slots as time-frequency resources capable of uplink transmission. In addition, the terminal may configure some frequency bands (1133) of the third slot and some frequency bands (1134) of the fourth slot as time-frequency resources capable of uplink transmission.

[0291] 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. And a symbol within a downlink symbol for which an uplink subband is configured may be referred to as an SBFD symbol. In addition, a time-frequency resource capable of downlink reception within an uplink symbol or slot may be referred to as an SBFD resource. And a symbol within an uplink symbol for which a downlink subband is configured may be referred to as an SBFD symbol.

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

[0293] FIG. 12 illustrates an example of an SBFD configuration according to one embodiment of the present disclosure. More specifically, FIG. 12 is referred to for a description of the present embodiment.

[0294] According to various embodiments, FIG. 12 is an example, and the same may be applied to other embodiments with reference to FIG. 12. Referring to FIG. 12, a terminal may be configured with an uplink symbol, a downlink symbol, or a flexible symbol according to a TDD configuration. Here, a 'D' slot may include a downlink symbol in all symbols of the slot. A 'U' slot may include an uplink symbol in all symbols of the slot. An 'S' slot may include a slot other than a 'D' slot or a 'U' slot. The terminal may be configured with a UL BWP (1220). In addition, the terminal may be configured with a UL subband (1210) within a DL symbol. In this embodiment, it is assumed that the UL BWP includes 275 RBs and the UL subband includes 50 RBs, but this is only an example and is not limited thereto. It is assumed that no UL subband is configured in the first slot. Therefore, the first slot can be referred to as a DL slot, and the symbols contained therein can be referred to as DL symbols. It is assumed that UL subbands are configured in the second, third, and fourth slots. Therefore, the second, third, and fourth slots can be referred to as SBFD slots, and the symbols contained therein can be referred to as SBFD symbols. The fifth slot is an uplink slot, and the symbols contained in the uplink slot can be referred to as uplink symbols.

[0295] According to various embodiments, the antenna of a base station may be composed of two antenna panels. The antenna panel may include one or more antenna elements. For convenience, the term "antenna panel" is used herein, but the panel may be equally referred to by other terms such as "antenna group" or "panel group." One of the two antenna panels may be referred to as a first panel, and the other may be referred to as a second panel. The two antenna panels may include the same number of antenna elements, or different numbers of antenna elements. Furthermore, the two antenna panels may include the same number of transceiver units (TxRUs), or different numbers of TxRUs. While the present disclosure describes two antenna panels, the specific embodiments are not limited thereto and may be applied to a plurality of antenna panels as well.

[0296] FIG. 13 illustrates an example of an antenna operation method in a TDD transmission scheme according to an embodiment of the present disclosure. More specifically, referring to FIG. 13, the antenna structure of a base station for TDD operation is determined as follows. In the case of a TDD configuration, the first four slots may include downlink slots, and the last slot may include an uplink slot. The base station may use both antenna panels for downlink transmission on a downlink slot or downlink symbol. Additionally, the base station may use both antenna panels for uplink reception on an uplink slot or uplink symbol.

[0297] According to FIG. 13, the antenna panels used on symbols capable of downlink transmission may always be the same as two panels. Furthermore, the antenna panels used on symbols capable of uplink reception may always be the same as two panels. Furthermore, the base station may use the same antenna panels used for downlink transmission for uplink reception. For example, the base station may use the same antenna panels for downlink transmission and uplink reception.

[0298] [Antenna operation method for SBFD operation]

[0299] FIG. 14 illustrates an example of an antenna operation method in an SBFD transmission scheme according to one embodiment of the present disclosure. More specifically, the structure of the antenna of a base station for SBFD operation can be determined as follows.

[0300] According to one embodiment, a base station can perform SBFD operation using two antenna panels in various ways. The antenna operation methods described below may refer to antenna panels used depending on the type or purpose of symbols in SBFD operation.

[0301] - In the first antenna operation method, referring to FIG. 14(a), when the base station transmits a downlink channel / signal on a downlink symbol / slot, both the first antenna panel and the second antenna panel can be used for downlink transmission. When the base station receives an uplink channel / signal on an uplink symbol / slot, both the first panel and the second panel can be used for uplink reception. When the base station transmits a downlink channel / signal and receives an uplink channel / signal on an SBFD symbol / slot, the first panel can be used for downlink transmission and the second panel can be used for uplink reception. According to the first method, the number of antenna elements or the number of antenna panels used for downlink transmission on a downlink symbol / slot can be greater than the number of antenna elements or the number of antenna panels used for downlink transmission on an SBFD symbol / slot. In addition, the number of antenna elements or antenna panels used for uplink reception on an uplink symbol / slot may be greater than the number of antenna elements or antenna panels used for uplink reception on an SBFD symbol / slot. Therefore, depending on which symbol the downlink channel / signal received by the terminal is transmitted on, the number of antenna elements or antenna panels used for downlink transmission may vary, and accordingly, the characteristics of the transmission signal of the base station may vary. Therefore, the terminal needs to know which antenna mode the base station uses (for example, the antenna mode means the number of panels, the number of antenna elements used for downlink transmission, and the number of panels, the number of antenna elements used for uplink reception, etc., depending on the antenna operating method). This can be equally applied to the uplink.For example, depending on which symbol the uplink channel / signal transmitted by the terminal is transmitted on, the number of antenna elements or antenna panels used for uplink transmission may vary, and accordingly, the characteristics of the received signal of the base station may vary.

[0302] - In the second antenna operation method, referring to FIG. 14(b), when the base station transmits a downlink channel / signal on a downlink symbol / slot, the first panel can be used for downlink transmission. When the base station transmits an uplink channel / signal on an uplink symbol / slot, the first panel can be used for uplink reception. When the base station transmits a downlink channel / signal and receives an uplink channel / signal on an SBFD symbol / slot, the first panel can be used for downlink transmission and the second panel can be used for uplink reception. Referring to the second antenna operation method, the antenna panels or antenna elements used by the base station for downlink transmission may include the same number of antenna panels or antenna elements on the downlink symbol / slot or the SBFD symbol / slot. However, the antenna panels or antenna elements used by the base station for uplink reception may include different numbers of antenna panels or antenna elements on the uplink symbol / slot or the SBFD symbol / slot, respectively. Accordingly, the antenna element used for uplink transmission may vary depending on which symbol the uplink channel / signal transmitted by the terminal is transmitted on, and accordingly, the characteristics of the signal received at the base station may vary.

[0303] In the third antenna operation method, referring to FIG. 14(c), when the base station transmits a downlink channel / signal on a downlink symbol / slot, the first panel can be used for downlink transmission. When the base station transmits an uplink channel / signal on an uplink symbol / slot, the first panel can be used for uplink reception. When the base station transmits a downlink channel / signal and receives an uplink channel / signal on an SBFD symbol / slot, the first panel can be used for uplink reception and the second panel can be used for downlink transmission. Referring to the third antenna operation method, the antenna panels or antenna elements that the base station uses for uplink reception may include the same number of antenna panels or antenna elements on the uplink symbol / slot or the SBFD symbol / slot. However, the antenna panels or antenna elements that the base station uses for downlink transmission may include different numbers of antenna panels or antenna elements on the downlink symbol / slot or the SBFD symbol / slot. Accordingly, depending on which symbol the downlink channel / signal received by the terminal is transmitted on, the antenna element used for downlink transmission may vary, and accordingly, the characteristics of the transmitted signal at the base station may vary.

[0304] In the fourth antenna operation method, referring to FIG. 14(d), when the base station transmits a downlink channel / signal on a downlink symbol / slot, the first panel may be used for downlink transmission. When the base station transmits an uplink channel / signal on an uplink symbol / slot, the second panel may be used for uplink reception. When the base station transmits a downlink channel / signal and receives an uplink channel / signal on an SBFD symbol / slot, the first panel may be used for downlink transmission and the second panel may be used for uplink reception. Referring to the fourth antenna operation method, the antenna panels or antenna elements used by the base station for downlink transmission may include the same number of antenna panels or antenna elements on the downlink symbol / slot or the SBFD symbol / slot. In addition, the antenna panels or antenna elements used by the base station for uplink reception may include the same number of antenna panels or antenna elements on the uplink symbol / slot or the SBFD symbol / slot. Therefore, the terminal may not request separate information about the antenna mode.

[0305] The above-described methods are merely examples of antenna operation methods for various SBFD operations, and various embodiments of the present disclosure are not limited to the four antenna operation methods described above.

[0306] FIG. 15 illustrates an example of multiple quasi co-located (QCL) assumptions in an SBFD transmission scheme according to one embodiment of the present disclosure.

[0307] According to various embodiments of the present disclosure, when a terminal receives a PDSCH or transmits a PUSCH through a single DCI format, each signal may be scheduled to a different symbol type. For example, referring to FIG. 15(a), the terminal may be instructed to repeatedly receive a PDSCH in multiple slots through a DCI format. Here, the terminal may be instructed to repeatedly receive a PDSCH in four slots through the DCI format, among which the first PDSCH repetition (PDSCH rep#0) may overlap a downlink symbol, and the remaining three PDSCH repetitions (PDSCH rep#1, PDSCH rep#2, PDSCH rep#3) may overlap a SBFD symbol. Through the above embodiments, the base station may set different settings for the antenna panel used on the downlink symbol and the antenna panel used on the SBFD symbol.

[0308] For example, when a base station has two antenna panels, the base station can use both antenna panels for downlink transmission on a downlink symbol, but can use only one of the two antenna panels for downlink transmission on an SBFD symbol. Therefore, beam-related information (e.g., resource-related information) applied on a downlink symbol and beam-related information applied on an SBFD symbol may be different. Here, the beam-related information may include QCL (Quasi-co-located) information. Here, the QCL information may be as follows.

[0309] - QCL typeA: {Doppler shift, Doppler spread, average delay, delay spread}

[0310] - QCL typeB: {Doppler shift, Doppler spread}

[0311] - QCL typeC: {Doppler shit, average delay}

[0312] -QCL typeD: {Spatial Rx parameter}

[0313] According to one embodiment, the base station must indicate to the terminal a QCL assumption suitable for the downlink symbol and the SBFD symbol in relation to the beam (or resource). A specific method for this is described below. Depending on the QCL assumption, the terminal can determine a reception filter or a transmission filter. Depending on the QCL assumption, the terminal can determine a reception beam or a transmission beam. In the following description, the QCL assumption may be interpreted as being replaced with a transmission configuration indicator (TCI), a reception filter / transmission filter, or a reception beam / transmission beam. In addition, it should be understood that according to various embodiments of the present disclosure, a beam may be replaced with a resource through which a signal is transmitted and received, corresponding to each beam.

[0314] In one embodiment, the base station may indicate two QCL assumptions to the terminal via the DCI format. For convenience, the first QCL assumption may be a QCL assumption suitable for antenna panels used for downlink symbols, and the second QCL assumption may be a QCL assumption suitable for antenna panels used for SBFD symbols. When the terminal receives the DCI format and the DCI format instructs to repeatedly receive a PDSCH in multiple slots, the terminal may receive a PDSCH overlapping a downlink symbol by applying the first QCL assumption, and may receive a PDSCH overlapping a SBFD symbol by applying the second QCL assumption.

[0315] A concrete way to indicate two QCL assumptions through the DCI format is as follows.

[0316] - The DCI format may include an N-bit field. The N-bit field may be a field that indicates a QCL hypothesis to the terminal. The base station may set up a table with rows containing at most two QCL hypotheses. Here, any row of the table may contain only one QCL hypothesis, and another arbitrary row may contain two QCL hypotheses. For example, if the terminal is instructed to a code point corresponding to a row containing two QCL hypotheses in the N-bit field, the terminal may obtain two QCL hypotheses. Note that although it is described here that two QCL hypotheses are set in a row of one table, the base station may of course set up two tables containing one QCL hypothesis for the terminal in another way. For example, the terminal may obtain two QCL hypotheses from rows corresponding to code points in the N-bit field in both tables.

[0317] - The DCI format may include an N-bit field. The N-bit field may be a field indicating a QCL assumption to the terminal. The base station may set up a table having a row including one QCL assumption. One QCL assumption may be a QCL assumption to be used for a first symbol type (e.g., a downlink symbol or an SBFD symbol). The base station may set a QCL assumption to be used for a second symbol type (e.g., an SBFD symbol or a downlink symbol) corresponding to the QCL assumption used for the first symbol type through a higher layer signal. The terminal may obtain the QCL assumption to be used for the first symbol type from a row of the table corresponding to the code point indicated by the N-bit field. In addition, the terminal may obtain the QCL assumption to be used for the second symbol type corresponding to the indicated QCL assumption according to a higher layer signal.

[0318] Although the embodiment described above describes PDSCH reception by a terminal, the same method can of course be applied to reception of other channels as well.

[0319] Referring to Fig. 15(b), when a terminal receives a DCI format (DCI format 1_0, 1_1, or 1_2) that activates a semi-persistent scheduling (SPS) PDSCH, the terminal may periodically receive the PDSCH. At this time, some of the SPS PDSCHs may overlap with downlink symbols, and other SPS PDSCHs may overlap with SBFD symbols. Therefore, similar to the method of repeatedly receiving PDSCHs with one DCI format above, beam-related information applied to a downlink symbol and beam-related information applied to a SBFD symbol may include different information.

[0320] Referring to Fig. 15(c), when a terminal receives a DCI format for repeatedly transmitting a PUSCH, the terminal must repeatedly transmit the PUSCH in multiple slots. Similar to the repeated transmission of the PDSCH, some of the repeatedly transmitted PUSCHs may overlap with uplink symbols, and others may overlap with SBFD symbols. Since the beam-related information applied to the uplink symbol and the beam-related information applied to the SBFD symbol may be different, multiple QCL assumptions may be required.

[0321] Referring to FIG. 15(d), when a terminal receives a DCI format (DCI format 0_0, 0_1, or 0_2) that activates a CG (configured grant) PUSCH, the terminal may periodically transmit a PUSCH. Similar to receiving an SPS PDSCH, some of the CG PUSCHs may overlap with uplink symbols, and others may overlap with SBFD symbols. Since the beam-related information applied in the uplink symbols and the beam-related information applied in the SBFD symbols may be different, multiple QCL assumptions may be required.

[0322] For reference, the above-described embodiment can also be applied to DCI scheduling one PDSCH or one PUSCH.

[0323] <Transmit / Receive set to upper layer>

[0324] The various examples of FIG. 15 above may include cases where transmission or reception is indicated in the DCI format. In addition, there may be channels or signals for which transmission or reception is indicated through higher layers. For example, signals indicated through higher layers may include PDCCHs, CSI-RSs, etc. that the terminal receives in the downlink, or SRSs, etc. that are transmitted in the uplink. Some of the channels or signals for which transmission or reception is indicated through higher layers may overlap with SBFD symbols, and some may overlap with symbols other than SBFD symbols (e.g., downlink symbols or uplink symbols). In this case, the base station may include up to two QCL assumptions when configuring the above-described channels / signals.

[0325] In one embodiment, for PDCCH, the base station and the terminal may use different QCL assumptions depending on the type of search space.

[0326] According to one embodiment, the type of search space may include at least:

[0327] - Type 0 common search space: Contains PDCCH that schedules PDSCH carrying SIB1.

[0328] - Type0A common search space: Includes PDCCH that schedules PDSCH that carries other system information blocks other than SIB1.

[0329] - Type 1 common search space: Includes PDCCH for random cell access.

[0330] - Type 2 common search space: Contains PDCCH related to paging.

[0331] - Type 3 common search space: Includes group common PDCCH

[0332] Here, some search spaces may include PDCCHs conveying key information of the system. For example, Type 0, 0A, 1, and 2 may be determined to be PDCCHs conveying key information of the cell. The UE can always use the antenna configuration corresponding to the downlink symbol, regardless of the symbol type, on the symbol receiving the PDCCH. This is because the antenna configuration corresponding to the downlink symbol can guarantee higher downlink coverage and received signal quality than the antenna configuration corresponding to the SBFD symbol.

[0333] In one embodiment, for CSI-RS, different QCL assumptions may be used depending on the intended use of the CSI-RS.

[0334] For example, when a terminal uses QCL assumptions for TRS (tracking RS) purposes among CSI-RS, higher downlink coverage and received signal quality are required. Therefore, similar to the PDCCH, which conveys key system information, the symbol for which the CSI-RS is configured for TRS purposes can be based on the antenna configuration corresponding to the downlink symbol, regardless of symbol type.

[0335] [MIMO Transmission Method for SBFD Operation]

[0336] <Separate MIMO parameter 설정 및 PDSCH / PUSCH 전송 방법>

[0337] According to the above, the downlink QCL assumption of the terminal may be different on the downlink symbol and the SBFD symbol. Therefore, the terminal may obtain both the first QCL assumption for the downlink symbol and the second QCL assumption for the SBFD symbol from the DCI format or the upper layer signal. The terminal may receive the downlink channel or signal with the first reception filter or the first reception beam determined according to the first QCL assumption on the downlink symbol. The terminal may receive the downlink channel or signal with the second reception filter or the second reception beam determined according to the second QCL assumption on the SBFD symbol.

[0338] In one embodiment, the channel between the base station and the terminal when the terminal receives the first reception beam on the downlink symbol may be referred to as the first channel, and the channel between the base station and the terminal when the terminal receives the second reception beam on the SBFD symbol may be referred to as the second channel. Note that the number of antenna panels used by the base station on the downlink symbol may be different from the number of antenna panels used on the SBFD symbol. Therefore, the first channel and the second channel may have different characteristics.

[0339] The maximum number of MIMO layers for the first and second channels may differ. For example, for the first channel, the base station may use more antenna panels and instruct the terminal to use the corresponding first QCL assumption, resulting in a higher channel rank. However, for the second channel, the base station may use fewer antenna panels and instruct the terminal to use the corresponding second QCL assumption, resulting in a lower channel rank. Therefore, the base station may instruct the terminal to use different maximum numbers of MIMO layers for the first and second channels.

[0340] According to one embodiment of the present disclosure, a terminal may be configured with a maximum number of MIMO layers (maxMIMO-Layers) for a downlink symbol. In addition, the terminal may be configured with a maximum number of MIMO layers (maxMIMO-Layers) for an SBFD symbol. If the maximum number of MIMO layers for an SBFD symbol is not configured, the terminal may determine the maximum number of MIMO layers for the downlink symbol as the maximum number of MIMO layers for the SBFD symbol. For example, the maximum number of MIMO layers for the SBFD symbol configured by the terminal may be less than or equal to the maximum number of MIMO layers for the downlink symbol. This is because the number of antenna panels used by the base station in the SBFD symbol may be small, and thus the channel rank of the second channel may be low.

[0341] According to one embodiment, when a terminal receives a downlink channel or signal (e.g., PDSCH) on a downlink symbol, the terminal may receive the signal based on the maximum number of MIMO layers for the downlink symbol. Furthermore, when identifying fields of a DCI that schedules a downlink channel or signal (e.g., PDSCH) on a downlink symbol, the fields of the DCI may be identified based on the maximum number of MIMO layers.

[0342] According to one embodiment, when a terminal receives a downlink channel or signal (e.g., PDSCH) on an SBFD symbol, the terminal may receive the signal based on the maximum number of MIMO layers for the SBFD symbol. Furthermore, when interpreting fields of DCI scheduling a downlink channel or signal (e.g., PDSCH) on an SBFD symbol, the terminal may interpret the fields of the DCI based on the maximum number of MIMO layers.

[0343] According to one embodiment, the terminal may receive from the base station a configuration for the maximum number of codewords (maxNrofCodeWordsScheduledByDCI) that may be included in a PDSCH. The maximum number of codewords may be one of 1 or 2. If the maximum number of codewords is 1, the PDSCH may include one codeword. If the maximum number of codewords is 2, the PDSCH may include at most two codewords. According to one embodiment, if the maximum number of codewords is 2, the number of codewords actually included in the PDSCH may be determined according to a combination of values ​​of fields of the DCI that schedules the PDSCH. According to one embodiment, when the number of downlink MIMO layers of the terminal is greater than 4, the PDSCH may include two codewords, and when the number of downlink MIMO layers of the terminal is less than or equal to 4, the PDSCH may include one codeword.

[0344] According to one embodiment, the DCI may include a first MCS field, a first RV field, and a first NDI field for a first codeword. Additionally, the DCI may include a second MCS field, a second RV field, and a second NDI field for a second codeword. The number of codewords included in the PDSCH may be determined by a combination of values ​​of the second MCS field, the second RV field, and the second NDI fields for the second codeword. The second MCS field for the second codeword may be set to a specific value (e.g., I MCS =26), and the second RV field is a specific value (e.g., rv id =1), the terminal may determine that the second codeword is deactivated, and the PDSCH may contain only the first codeword.

[0345] According to one embodiment of the present disclosure, a terminal may be configured with a maximum number of codewords for a PDSCH received in a downlink symbol. In addition, the terminal may be configured with a maximum number of codewords for an SBFD symbol. If the maximum number of codewords for an SBFD symbol is not configured, the terminal may determine the maximum number of codewords for the downlink symbol as the maximum number of codewords for the SBFD symbol. For example, the maximum number of codewords for the SBFD symbol configured by the terminal may be less than or equal to the maximum number of codewords for the downlink symbol. This is because the number of antenna panels used by the base station in the SBFD symbol may be small, and thus the channel rank of the second channel may be low.

[0346] According to one embodiment, a terminal may be instructed to receive PDSCH repetitions or SPS PDSCHs through a single DCI. Some of the PDSCH repetitions or SPS PDSCHs may overlap with downlink symbols, and some may overlap with SBFD symbols. Assuming that the maximum number of codewords of PDSCHs received in downlink symbols is 2, and the maximum number of codewords of PDSCHs received in SBFD symbols is set to 1, the terminal needs to determine the number of codewords included in the PDSCHs received on downlink symbols and the number of codewords of the PDSCHs received on SBFD symbols from a single DCI. A specific method for determining the number of codewords is described below.

[0347] According to the first method, a single DCI received by a terminal can be expected to schedule a PDSCH that always includes a single codeword. More specifically, if the PDSCH scheduled by the DCI received by the terminal is scheduled only on a downlink symbol, the scheduled PDSCH may include a codeword based on a value corresponding to the maximum number of codewords for the downlink symbol. For example, if the value of the maximum number of codewords for the downlink symbol is 2, the PDSCH may include a maximum of 2 codewords. In one embodiment, the number of codewords actually included in the PDSCH may vary depending on the combination of fields in the DCI. If the PDSCH scheduled by the DCI received by the terminal is scheduled on at least one SBFD symbol, the scheduled PDSCH may include a codeword based on a value corresponding to the maximum number of codewords for the SBFD symbol. For example, if the value of the maximum number of codewords for the SBFD symbol is 1, the PDSCH may always include a single codeword.

[0348] According to various embodiments, the first method described above may mean a case where the maximum number of codewords for an SBFD symbol is less than the maximum number of codewords for a downlink symbol. In general, the first method may be as follows. According to one embodiment, if a PDSCH scheduled by a DCI received by a terminal is scheduled for only one symbol type, the scheduled PDSCH may include codewords based on a value corresponding to the maximum number of codewords corresponding to one symbol type. For example, if one symbol type is a downlink symbol type, the number of codewords included in the PDSCH may be determined based on the maximum number of codewords for the downlink symbol. If one symbol type is an SBFD symbol type, the number of codewords included in the PDSCH may be determined based on the maximum number of codewords for the SBFD symbol. According to one embodiment, if the PDSCH scheduled by the DCI received by the terminal is scheduled for only two symbol types, the scheduled PDSCH may be determined based on the minimum value of the maximum number of codewords corresponding to the first symbol type and the maximum number of codewords corresponding to the second symbol type.

[0349] According to various embodiments, the DCI may include a first MCS field, a first RV field, and a first NDI field for a first codeword. If the maximum number of codewords is two, the DCI field may include a second MCS field, a second RV field, and a second NDI field for a second codeword. Accordingly, the length (payload size) of the DCI may vary depending on the maximum number of codewords. According to one embodiment, in the first method, the maximum number of codewords may be determined after interpreting the DCI. For example, the terminal may interpret the DCI to determine the types of symbols for which the PDSCH is scheduled. Therefore, an assumption may be required for determining the DCI length before interpreting the DCI. In one method of the present disclosure, to determine the DCI length, the terminal may base the maximum value of the maximum number of codewords corresponding to the first symbol type and the maximum number of codewords corresponding to the second symbol type. For example, if the maximum number of codewords for a downlink symbol is 2 and the maximum number of codewords for an SBFD symbol is 1, the DCI length can be determined assuming the maximum number of codewords to be 2. That is, the DCI can include a first MCS field, a first RV field, and a first NDI field for a first codeword, and a second MCS field, a second RV field, and a second NDI field for a second codeword.

[0350] According to various embodiments of the present disclosure, the length of the DCI may be determined according to the maximum value of the maximum number of codewords corresponding to the first symbol type and the maximum number of codewords corresponding to the second symbol type. The PDSCH scheduled by the DCI may be determined according to the minimum value of the maximum number of codewords corresponding to the first symbol type and the maximum number of codewords corresponding to the second symbol type, if the two symbol types overlap. For example, the length of the DCI is determined assuming that the maximum number of codewords is 2, but the DCI may schedule a PDSCH including only one codeword. According to various embodiments, in this case, the interpretation of the DCI by the terminal may be as follows.

[0351] - The terminal may ignore the second MCS field, the second RV field, and the second NDI field for the second codeword. For example, regardless of what values ​​are indicated in the second MCS field, the second RV field, and the second NDI field, the terminal may determine that only one codeword is scheduled when the PDSCH is scheduled across two symbol types.

[0352] - If the combination of the second MCS field, the second RV field, and the second NDI field for the second codeword indicates that the above-described codeword is deactivated, the terminal may receive the PDSCH scheduled across the two symbol types. Conversely, if the combination of the second MCS field, the second RV field, and the second NDI field for the second codeword indicates that the above-described codeword is activated, the terminal may not receive the PDSCH scheduled across the two symbol types. For example, the terminal may determine that the DCI is an invalid DCI. If the DCI is determined to be an invalid DCI, the terminal may not apply the information indicated in the DCI. This is because, although the DCI indicates that two codewords are activated, the PDSCH scheduled by the DCI is scheduled across the two symbol types, and thus may ultimately include only one codeword.

[0353] According to various embodiments, as a second method, when a PDSCH scheduled by a DCI is scheduled across two symbol types, the maximum number of codewords included in the PDSCH may be equal to the maximum number of codewords set for the symbol types. For example, with respect to a PDSCH scheduled in a downlink symbol, the maximum number of codewords may be determined based on the maximum number of codewords for the downlink symbol, and with respect to a PDSCH scheduled in an SBFD symbol, the maximum number of codewords may be determined based on the maximum number of codewords for the SBFD symbol. In other words, a PDSCH scheduled in a downlink symbol may include at most two codewords, and a PDSCH scheduled in an SBFD symbol may include at most one codeword.

[0354] According to one embodiment, according to the second method, when a terminal receives a PDSCH in a downlink symbol, it may expect a PDSCH including at most two codewords, but when a terminal receives a PDSCH in a SBFD symbol, it may expect a PDSCH including at most one codeword. If the DCI relates to repeated transmission of the PDSCH, a PDSCH including at most two codewords may be received in the downlink symbol, but a PDSCH including only one of the two codewords may be received in the SBFD symbol. If the DCI schedules an SPS PDSCH or a multi-PDSCH, a PDSCH including at most two codewords may be received in the downlink symbol, and a PDSCH including at most one codeword may be received in the SBFD symbol.

[0355] According to one embodiment, according to the second method, if the value of the maximum number of codewords for at least one symbol type among the two symbol types is set to 2, the DCI may include a first MCS field, a first RV field, and a first NDI field for the first codeword and a second MCS field, a first RV field, and a second NDI field for the second codeword. The above-described method of interpreting the DCI may be as follows.

[0356] - When all PDSCHs scheduled by DCI overlap with one symbol type and the maximum number of codewords of one symbol type is 2, the terminal can obtain scheduling information of the first codeword based on the first MCS field, the first RV field, and the first NDI field for the first codeword, and can obtain scheduling information of the second codeword based on the second MCS field, the second RV field, and the second NDI field for the second codeword. In addition, one of the two codewords can be deactivated.

[0357] - When all PDSCHs scheduled by the DCI overlap with one symbol type and the maximum number of codewords of one symbol type is 1, and when the PDSCHs scheduled by the DCI overlap with two symbol types and the maximum number of codewords of at least one symbol type is 1, the terminal may obtain scheduling information of the first codeword based on the first MCS field, the first RV field, and the first NDI field for the first codeword. If the DCI includes the second MCS field, the second RV field, and the second NDI field for the second codeword, the terminal may ignore the second MCS field, the second RV field, and the second NDI field for the second codeword included in the DCI. According to one embodiment, the information about the second codeword may be used when all PDSCHs scheduled by the DCI overlap with one symbol type and the maximum number of codewords of one symbol type is 2.

[0358] According to various embodiments, as a third method, the terminal may assume that the DCI can always schedule the PDSCH on symbols having the same maximum codeword number. More specifically, if the DCI schedules the PDSCH on symbols having different maximum codeword numbers, the terminal may determine that the DCI is invalid. For example, if the PDSCH scheduled by the DCI overlaps with a downlink symbol and an SBFD symbol, and if one or two maximum codewords are set identically for the downlink symbol and the SBFD symbol, the terminal may receive the PDSCH. Conversely, if two maximum codewords are set identically for the downlink symbol and one maximum codeword is set identically for the SBFD symbol, the terminal may not receive the PDSCH scheduled by the DCI.

[0359] According to various embodiments, as a fourth method, the terminal may not receive the PDSCH on symbols having a maximum number of codewords that are not the same as the DCI. More specifically, the terminal may determine the number of codewords included in the PDSCH based on the DCI. If the number of codewords is 2, the terminal may not receive the PDSCH in a symbol type in which the maximum number of codewords is set to 1. And the PDSCH may be received in a symbol type in which the maximum number of codewords is set to 2. If the number of codewords is 1, as a first operation, the terminal may receive the PDSCH only in a symbol type in which the maximum number of codewords is set to 1. As a second operation, the terminal may receive the PDSCH in a symbol type in which the maximum number of codewords is 1 or greater than 1.

[0360] FIG. 16 illustrates an example of transmission according to multiple-input and multiple-output (MIMO) parameters according to one embodiment of the present disclosure.

[0361] More specifically, referring to (a) and (b) of FIG. 16, the DCI indicates that the PDSCH includes two codewords and indicates reception of the PDSCH on four slots. Referring to (c) and (d) of FIG. 16, the DCI indicates that the PDSCH includes one codeword and indicates reception of the PDSCH on four slots. In FIG. 16, the PDSCH may include at most two codewords in a downlink symbol and at most one codeword in an SBFD symbol.

[0362] According to one embodiment, (a) of FIG. 16 corresponds to the operation of the terminal according to the second method described above. Since the DCI includes two codewords, a PDSCH including two codewords is received in a downlink symbol (slot 0, slot 3) where a PDSCH including two codewords can be received, and a PDSCH including one codeword can be received in an SBFD symbol (slot 1, slot 2) where a PDSCH including one codeword can be received.

[0363] According to one embodiment, FIG. 16(b), FIG. 16(c), and FIG. 16(d) correspond to the operation of the terminal according to the fourth method. Referring to FIG. 16(b), if the DCI received by the terminal schedules two codewords, the terminal can receive the PDSCH only in the symbol type in which the two codewords can be scheduled. For example, the terminal can receive the PDSCH only in the downlink symbol. Accordingly, the terminal can receive the PDSCH including two codewords in slot 0 and slot 3. In addition, the terminal may not receive the PDSCH in the SBFD symbol. Referring to FIG. 16(c), if the DCI received by the terminal schedules one codeword, the terminal can receive the PDSCH only in the SBFD symbol (slot 1, slot 2) in which the maximum number of codewords is set to 1. And, the terminal may not receive the PDSCH in the downlink symbol (slot 0, slot 3) in which the maximum number of codewords is set to 2 (first operation). Referring to Fig. 16(d), if the DCI received by the terminal schedules one codeword, the terminal may receive the PDSCH in the SBFD symbol (slot 1, slot 2) in which the maximum number of codewords is set to 1 and the downlink symbol (slot 0, slot 3) in which the maximum number of codewords is set to a value greater than 1 (second operation).

[0364] According to one embodiment, (e) of FIG. 16 corresponds to the operation of the terminal according to the third method. Here, the terminal can receive the PDSCH on symbols for which the same maximum number of codewords is set. The terminal can receive the PDSCH only on symbol types having the same number of codewords as the maximum number of codewords of one symbol type scheduled by the DCI (e.g., the symbol type overlapping with the first PDSCH in time). Referring to FIG. 16 (e), since the maximum number of codewords of one symbol type scheduled by the DCI (e.g., the symbol type overlapping with the first PDSCH in time) is 2, the terminal can receive the PDSCH on symbols (slot 0, slot 3) for which the maximum number of codewords is 2. Note that the above-described method can be applied regardless of the number of codewords scheduled by the DCI. For example, even if DCI schedules one codeword, the terminal can receive the PDSCH only in symbols where the maximum number of codewords is 2.

[0365] Although the description above is based on the PDSCH, various embodiments of the present disclosure can also be applied to the PUSCH. In this case, the downlink symbol can be interpreted as being replaced with the uplink symbol. When applied to the PUSCH, the maximum number of codewords that can be included in the PUSCH can be determined by the maximum uplink rank (maxRank) or the maximum number of uplink MIMO layers (maxMIMO-Layer). For example, the first maximum uplink rank or the first maximum number of uplink MIMO layers can be set in the uplink symbol, and the second maximum uplink rank or the second maximum number of uplink MIMO layers can be set in the SBFD symbol. If the maximum uplink rank or the maximum number of uplink MIMO layers exceeds 4, the maximum number of codewords can be 2, and if the maximum uplink rank or the maximum number of uplink MIMO layers is 4 or less, the maximum number of codewords can be 1.

[0366] As described above, the number of the first maximum MIMO layers (maxMIMO-Layers) or the number of the first maximum codewords (maxNrofCodeWordsScheduledByDCI) may be set on the downlink symbol, and the number of the second maximum MIMO layers (maxMIMO-Layers) or the number of the second maximum codewords (maxNrofCodeWordsScheduledByDCI) may be set on the SBFD symbol. The maximum number of MIMO layers and the maximum number of codewords are just examples, and parameters related to other MIMO settings may be set for the downlink symbol and the SBFD symbol, respectively. For example, information related to the Antenna port field of the downlink DCI (DCI format 0_1, 1_1, 2_1, etc.) and information related to the PRB bundling size indicator field may be set for the downlink symbol and the SBFD symbol, respectively.

[0367] As described above, the first maximum number of MIMO layers (maxMIMO-Layers) or the first maximum uplink rank (maxRank) may be set in the uplink symbol, and the second maximum number of MIMO layers (maxMIMO-Layers) or the second maximum uplink rank (maxRank) may be set in the SBFD symbol. The maximum number of MIMO layers and the maximum uplink rank are examples, and parameters related to other MIMO settings may be set for the uplink symbol and the SBFD symbol, respectively. For example, information related to the SRS resource set indicator field of the uplink DCI (DCI format 0_0, 1_0, 2_0, etc.), information related to the SRS resource indicator field, information related to the Precoding information and number of layers field, and information related to the Antenna port field may be set for each of the uplink symbol and the SBFD symbol, respectively.

[0368] <Separate MIMO parameter 설정 및 단말 보고>

[0369] Hereinafter, a method and operation for receiving a PDSCH on a downlink symbol and an SBFD symbol are described, but it should be understood that various embodiments of the present disclosure may also be interpreted as a method and operation for transmitting a PUSCH on an uplink symbol and an SBFD symbol. For example, in the following description, a downlink symbol may be replaced with an uplink symbol, a PDSCH may be replaced with a PUSCH, and reception may be replaced with transmission.

[0370] As described above, the first QCL setting of the downlink symbol and the second QCL setting of the SBFD symbol may be the same or different. When the terminal receives a PDSCH in the downlink, the terminal may use a reception filter corresponding to the QCL setting. Accordingly, when the terminal receives a PDSCH in the downlink symbol, the terminal may receive it using the first reception filter corresponding to the first QCL setting, and when the terminal receives a PDSCH in the SBFD symbol, the terminal may receive it using the second reception filter corresponding to the second QCL setting. However, in order to perform the above-described operation, the terminal needs to change the reception filter corresponding to the QCL setting between the downlink symbol and the SBFD symbol.

[0371] According to one embodiment, the receiving filter corresponding to the above-described QCL setting may include an analog filter or a digital filter. If the receiving filter is an analog filter, sufficient time may be required to switch between the first and second receiving filters. The time required for the above-described filter change (e.g., filter transition time) may vary depending on the implementation of the terminal. Therefore, the base station may need to perform scheduling that takes the above-described filter transition time into account. Methods for meeting the above-described requirements are described below.

[0372] According to various embodiments of the present disclosure, a terminal may report terminal capabilities to a base station during initial cell access. The terminal capability report may include at least one of the following pieces of information:

[0373] - As the first information, the terminal capability report may include information on whether different QCL settings are possible for the downlink symbol and the SBFD symbol. In one embodiment, if the terminal reports through the terminal capability report that different QCL settings are not possible, the terminal may expect to always receive the same QCL settings from the base station for the downlink symbol and the SBFD symbol. Accordingly, the first QCL setting and the second QCL setting of the terminal capability report may always be the same. In one embodiment, if the terminal reports through the terminal capability report that different QCL settings are possible, the terminal may expect to receive the same QCL settings or different QCL settings from the base station for the downlink symbol and the SBFD symbol. Accordingly, the first QCL setting and the second QCL setting may be the same or different.

[0374] - As the second information, the terminal capability report may include a minimum filter change time between the first QCL configuration and the second QCL configuration. In one embodiment, when the terminal reports the minimum filter change time through the terminal capability report, the terminal may not expect that the change between the first QCL configuration and the second QCL configuration will be performed within a time shorter than the minimum filter change time. The minimum filter change time may be reported based on an absolute time (e.g., in units of ms or us), based on a reference subcarrier spacing and a number of symbols, or based on a reference subcarrier spacing and a number of slots. Here, the reference subcarrier spacing may include 15 kHz, 30 kHz, 60 kHz, 120 kHz, 480 kHz, or 960 kHz. In one embodiment, the terminal may report a plurality of filter change times according to the reference subcarrier spacing through the terminal capability report. For example, the number of first symbols (or the number of first slots) when the reference subcarrier spacing is 15 kHz or the number of second symbols (or the number of second slots) when the reference subcarrier spacing is 30 kHz may be reported. The terminal may also report, through the terminal report, that there is no need for a filter change time. For example, if the time required for a filter change is very short, the terminal may receive or transmit signals with different QCL settings without a filter change time. According to one embodiment, as a method of reporting that there is no need for a filter change time, the terminal may explicitly report this through the terminal capability report or may report it by not including the second information through the terminal capability report. The terminal may report one of the first filter change time and the second filter change time through the terminal report. The first filter change time and the second filter change time may be values ​​agreed upon in advance between the base station and the terminal.Although described here based on the first filter change time and the second filter change time, it is of course generally possible for a terminal to report one of N filter change times.

[0375] - As the third information, the terminal may report whether repetitive PDSCH reception (or repetitive PUSCH transmission) is possible only in the same QCL configuration, or whether repetitive PDSCH reception (or repetitive PUSCH reception) is possible in different QCL configurations. According to one embodiment, if the terminal reports through the terminal capability report that repetitive PDSCH reception (repetitive PUSCH transmission) is possible only in the same QCL configuration, the terminal may receive repetitive PDSCHs corresponding to only one QCL configuration when receiving repetitive PDSCHs (when transmitting repetitive PUSCHs), and may not receive repetitive PDSCHs corresponding to another QCL configuration. According to one embodiment, if the terminal reports through the terminal capability report that repetitive PDSCH reception (repetitive PUSCH transmission) is possible in different QCL configurations, the terminal may receive repetitive PDSCHs corresponding to the first QCL configuration when receiving repetitive PDSCHs (when transmitting repetitive PUSCHs), and may also receive PDSCHs corresponding to the second QCL configuration. Below, a more specific method is described.

[0376] According to various embodiments, the above-described QCL setting may of course be interpreted as a transmission configuration indicator (TCI) state, a receive beam (e.g., when describing a downlink reception), a transmit beam (e.g., when describing an uplink transmission), or a corresponding resource (e.g., SSB, CSI-RS, when describing a downlink reception, or SRS when describing an uplink transmission).

[0377] According to various embodiments, the above-described QCL settings may be applied by being replaced with other MIMO parameters. For example, the first QCL setting may be applied by being replaced with the first MIMO parameter (e.g., maxMIMO-Layers, maxNrofCodeWords, ScheduledByDCI, maxRank, etc.), and the second QCL setting may be applied by being replaced with the second MIMO parameter.

[0378] <Separate MIMO parameter 설정 제약>

[0379] As described above, the first QCL configuration of a downlink symbol and the second QCL configuration of an SBFD symbol may be the same or different. When a terminal receives a PDSCH in downlink, the terminal may use a reception filter corresponding to the QCL configuration. Accordingly, when the terminal receives a PDSCH in a downlink symbol, the terminal may receive the PDSCH using the first reception filter corresponding to the first QCL configuration, and when the terminal receives the PDSCH in an SBFD symbol, the terminal may receive the PDSCH using the second reception filter corresponding to the second QCL configuration. There may be a relationship or constraint between the first QCL configuration and the second QCL configuration. Hereinafter, the relationship or constraint between the two settings described above will be specifically described in the present disclosure.

[0380] In various embodiments, for convenience, the QCL setting is described as a TCI state.

[0381] According to one embodiment, N first TCI states may be set for PDSCH reception (or PUSCH transmission) in a downlink symbol (or an uplink symbol). The N first TCI states may be set by a higher layer signal (e.g., an RRC signal) from a base station. In addition, at least one of one, some, or all of the N first TCI states may be changed via a MAC-CE signal. A change in a TCI state may mean that an index corresponding to the TCI state is maintained, and a downlink resource (e.g., SSB or CSI-RS) or an uplink resource (e.g., SRS) corresponding to the TCI state is changed.

[0382] In one embodiment of the present disclosure, N second TCI states may be set for PDSCH reception (or PUSCH transmission) in an SBFD symbol.

[0383] - As a first method, the terminal may assume that the N second TCI states in the SBFD symbol are identical to the N first TCI states of the downlink symbol (or the uplink symbol). For example, the terminal may determine the second TCI states of the SBFD symbol without receiving a separate upper layer signal (e.g., an RRC signal) from the base station. The first TCI states may each have a unique index. The unique index may be determined as 0, 1, ..., N-1. The second TCI states may each have a unique index. The unique index may be determined as 0, 1, ..., N-1. According to various embodiments of the present disclosure, the first TCI state and the second TCI state for the same index (e.g., index 0) may be different from each other.

[0384] If one, some, or all of the first TCI states are changed through the MAC-CE signal, such change may be equally applied to the second TCI states. For example, the MAC-CE signal may change the first TCI states and the second TCI states simultaneously. Alternatively, the MAC-CE signal may include first information regarding whether one, some, or all of the first TCI states are changed through the MAC-CE signal, and second information regarding whether one, some, or all of the second TCI states are changed through the MAC-CE signal. It should be understood that the first information and the second information may always be included in the MAC-CE signal simultaneously, or only one of the two pieces of information may be included in the MAC-CE signal. Upon receiving the MAC-CE signal including the first information, the terminal may change one, some, or all of the first TCI states. Such change may not be applied to the second TCI state. Upon receiving a MAC-CE signal including second information, the terminal may change one, some, or all of the second TCI states. Such changes may not be applied to the first TCI state. For example, depending on the MAC-CE signal, the first TCI states and the second TCI states may differ from each other.

[0385] - As a second method, the terminal may assume that the N second TCI states in the SBFD symbol and the N first TCI states of the downlink symbol (or the uplink symbol) are different from each other. The terminal may receive the N second TCI states in the SBFD symbol from a higher layer signal (RRC signal). For example, the terminal may separately receive the N first TCI states in the downlink symbol (or the uplink symbol) and the N second TCI states in the SBFD symbol from a higher layer signal (RRC signal). The first TCI states may each have a unique index. The unique index may include 0, 1, ..., N-1. The second TCI states may each have a unique index. The unique index may include 0, 1, ..., N-1. According to various embodiments of the present disclosure, the first TCI state and the second TCI state for the same index (e.g., index 0) may be different from each other.

[0386] - As a third method, the terminal may assume that some of the N second TCI states in the SBFD symbol are the same as, or different from, the N first TCI states of the downlink symbol (or the uplink symbol). Each of the first TCI states may have a unique index. The unique index may include 0, 1, ..., N-1. Each of the second TCI states may have a unique index. The unique index may include 0, 1, ..., N-1. According to various embodiments of the present disclosure, the first TCI state and the second TCI state may be the same with respect to any index. The first TCI state and the second TCI state may be different with respect to another index. The base station may configure the terminal to, through a higher layer signal (RRC signal), ensure that at least one of the N second TCI states in the SBFD symbol has the same index as the first TCI states on the downlink symbol (or the uplink symbol). For example, if the set index includes '0', the second TCI state whose index is '0' among the second TCI states may be identical to the first TCI state for the same index (index is '0'). The base station may set the second TCI state for the above-described index to the terminal by a higher layer signal (RRC signal) such that at least one of the N second TCI states in the SBFD symbol may have a different index from the first TCI states on the downlink symbol (or the uplink symbol). For example, if the index includes '1', the second TCI state whose index corresponds to '1' among the second TCI states may be set by a higher layer signal, which may be different from the first TCI state whose index corresponds to '1'.

[0387] In one embodiment, if the MAC-CE signal changes the state of a TCI whose index is set such that the first TCI state and the second TCI state are identical, such change may be applied equally to the first TCI state and the second TCI state.

[0388] In one embodiment, a terminal may receive a DCI scheduling PDSCH reception (or PUSCH transmission). The DCI received by the terminal may include a TCI field. Here, the length of the TCI field may be determined based on N. More specifically, the length of the TCI field may be determined as ceil(log2(N)).

[0389] In one embodiment of the present disclosure, M second TCI states may be set for PDSCH reception (or PUSCH transmission) in an SBFD symbol, where M may be a number different from N, or M may be a natural number less than N.

[0390] According to various embodiments, the M second TCI states may be determined as follows.

[0391] In one embodiment, the terminal may use M of the N first TCI states as second TCI states. For example, the second TCI states may be composed of a subset of the first TCI states. Here, the M second TCI states may be identical to the first TCI states of a specific index. The specific index may include 0, 1, ..., M-1. For example, the M second TCI states may be identical to the first TCI states whose indices are 0, 1, ..., M-1. The specific indices may be set by the base station. The terminal may receive the M indices and use the first TCI state corresponding to the received indices for the second TCI state.

[0392] In one embodiment, the terminal may additionally receive K second TCI configurations from the base station. The K additional TCI states may include TCI states that are different from the first TCI states. Accordingly, the number of second TCI configurations received by the terminal may be M+K.

[0393] According to one embodiment, a terminal may receive a DCI for scheduling PDSCH reception (or PUSCH transmission). The DCI received by the terminal may include a TCI field. Here, the length of the TCI field may be determined based on the number of first TCI states (N) and the number of second TCI states (M or M+K). More specifically, the length of the TCI field may be determined based on a larger value among the number of first TCI states (N) and the number of second TCI states (M or M+K). The length of the TCI field may be determined as ceil(log2(max{N,M})) or ceil(log2(max{N,M+K})).

[0394] According to various embodiments, a terminal may be configured with second TCI states for PDSCH reception (or PUSCH transmission) on an SBFD symbol. One or some of the configured second TCI states may cause self-interference or inter-base station interference depending on the mobility of the terminal or channel change. Therefore, the terminal may disable one or some of the configured second TCI states. Here, deactivation of a TCI state may mean that the terminal does not perform PDSCH reception (or PUSCH transmission) based on the TCI state. According to one embodiment, even if the terminal is scheduled to perform PDSCH reception (or PUSCH transmission) according to the TCI state, the terminal may cancel (or drop, or skip) the PDSCH reception (or PUSCH transmission) without performing the PDSCH reception. Alternatively, the terminal may not expect to be scheduled to perform PDSCH reception (or PUSCH transmission) according to the TCI state. That is, when a terminal receives a DCI that schedules PDSCH reception (or PUSCH transmission) according to a TCI state, the terminal may determine that the received DCI is invalid DCI and may not perform the operations indicated by the DCI. This series of processes may be expressed as discarding the DCI. According to one embodiment, the base station may indicate to the terminal second TCI states to be deactivated. The second TCI states to be deactivated may be indicated via a MAC-CE signal. According to one embodiment, the first TCI state may not be deactivated according to the above-described indication. That is, the TCI states deactivated by the MAC-CE may be limited to the second TCI states.

[0395] According to various embodiments of the present disclosure, a base station may indicate to a terminal which second TCI states are activated. The second TCI states to be activated may be indicated via a MAC-CE signal. In one embodiment, the first TCI state may not be activated according to the above-described indication. That is, the TCI states activated by the MAC-CE may be limited to the second TCI states. In one embodiment, the activation of a TCI state may mean that the terminal can perform PDSCH reception (or PUSCH transmission) via the TCI state.

[0396] According to one embodiment, a terminal may receive a MAC-CE via a PDSCH. The terminal may transmit information on successful reception of the PDSCH to a base station. Successful reception may mean 'ACK' among HARQ-ACK information. The terminal may transmit the HARQ-ACK information to the base station via a PUCCH. The terminal may apply deactivation or activation of the second TCI states indicated by the MAC-CE from a certain point in time after PUCCH transmission. According to one embodiment, the certain point in time may mean a point in time at which deactivation or activation of the TCI states is applied from 3*N_subframe OFDM symbols after PUCCH transmission (or from the slot in which the PUCCH is transmitted) (or from the first slot after 3*N_subframe OFDM symbols). The terminal may not apply deactivation or activation of the second TCI states indicated by the MAC-CE until the above-described point in time.

[0397] According to one embodiment, if the PDSCH reception (PUSCH transmission) already scheduled before the above-described time corresponds to a disabled second TCI state, the terminal may not cancel the PDSCH reception (PUSCH transmission). For example, the terminal may apply the deactivation or activation of the second TCI states indicated by the MAC-CE only to the PDSCH reception (PUSCH transmission) scheduled after the above-described time. Since the above-described scheduling may be applied through the PDCCH including the DCI, if the PDCCH reception time (e.g., the first symbol or the last symbol) is before the above-described time, the terminal may not apply the deactivation or activation of the second TCI states indicated by the MAC-CE. If the PDCCH reception time (e.g., the first symbol or the last symbol) is after the above-described time, the terminal may apply the deactivation or activation of the second TCI states indicated by the MAC-CE.

[0398] According to one embodiment, if the second TCI state corresponds to a state in which PDSCH reception (PUSCH transmission) already scheduled before the above-described time is disabled, the terminal may or may not cancel the PDSCH reception (PUSCH transmission) based on the processing time. The terminal may not cancel the PDSCH reception (PUSCH transmission) within X ms or X OFDM symbols after a reference time (e.g., the last symbol or slot of PUCCH transmission, or the above-described time). According to one embodiment, the terminal may cancel the PDSCH reception (PUSCH transmission) after the reference time. Here, X may be a time required to cancel the PDSCH reception (PUSCH reception).

[0399] <Separate MIMO parameter 설정 및 HARQ-ACK codebook 생성 방법>

[0400] According to various embodiments of the present disclosure, a terminal may transmit hybrid automatic repeat request (HARQ)-acknowledgement (ACK) information of a PDSCH to a base station. If the maximum number of codewords configured for the terminal is 2, the PDSCH includes two codewords, and thus the terminal needs to transmit HARQ-ACK information corresponding to the two codewords to the base station. According to one embodiment, if the maximum number of codewords configured for the terminal is 1, the PDSCH includes one codeword, and thus the terminal needs to transmit HARQ-ACK information corresponding to one codeword to the base station.

[0401] According to various embodiments of the present disclosure, a base station may set different maximum codeword numbers for different symbol types. For example, the maximum codeword number may be set to 2 for a downlink symbol, and the maximum codeword number may be set to 1 for an SBFD symbol. When a terminal receives a PDSCH, the number of codewords contained in the PDSCH may vary depending on the scheduled symbol type. Accordingly, the number of HARQ-ACK information that the terminal must report to the base station may also vary.

[0402] According to one embodiment, the terminal may report HARQ-ACK information to the base station based on a Type-1 HARQ-ACK codebook or a Type-2 HARQ-ACK codebook. The Type-1 HARQ-ACK codebook or the Type-2 HARQ-ACK codebook needs to include not only HARQ-ACK information of a PDSCH that the terminal has successfully received, but also HARQ-ACK information of a PDSCH that the terminal has failed to receive but that the base station has scheduled. Here, the HARQ-ACK information of the PDSCH that the terminal has failed to receive but that the base station has scheduled may be configured as a NACK (negative ACK). However, the terminal may not recognize the length of the HARQ-ACK information of the PDSCH that the base station has failed to receive. As described above, this is because the number of HARQ-ACK information reported by the base station is determined according to the maximum number of codewords.

[0403] In order to solve the above problem, when the terminal generates a Type-1 HARQ-ACK codebook or a Type-2 HARQ-ACK codebook, the number of codewords included in the PDSCH can always be assumed to be a larger value between the maximum numbers of codewords set for the two symbol types. For example, if the terminal sets the maximum number of codewords to 1 for both symbol types, the terminal can generate HARQ-ACK information assuming that the PDSCH always includes one codeword. According to one embodiment, if the terminal sets the maximum number of codewords to 2 for at least one symbol type among the two symbol types, the terminal can generate HARQ-ACK information assuming that the PDSCH includes two codewords. If the PDSCH actually received by the terminal includes only one codeword, the HARQ-ACK information for the one codeword that is not included can be configured as a NACK. In one embodiment, the terminal may generate HARQ-ACK information for two codewords, assuming that the PDSCH scheduled by the base station always contains two codewords, even though reception has failed.

[0404] FIG. 17 is a diagram illustrating the structure of a terminal in a wireless communication system according to one embodiment of the present disclosure.

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

[0406] 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 merely one embodiment of the transceiver unit, and the components of the transceiver unit are not limited to the RF transmitter and RF receiver.

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

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

[0409] Additionally, the processor (or controller) can control a series of processes so that the terminal can 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 component control operations of the terminal by executing programs stored in memory.

[0410] FIG. 18 is a diagram illustrating the structure of a base station in a wireless communication system according to one embodiment of the present disclosure.

[0411] Referring to FIG. 18, the base station may include a transceiver, which refers to a base station receiver (1830) and a base station transmitter (1810), a memory (not shown), and a base station processor (1805, or a base station control unit or processor). According to the communication method of the base station described above, the transceiver (1800, 1810), the memory, and the base station processor (1805) 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.

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

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

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

[0415] A processor (or controller) can control a series of processes so that a base station can 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.

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

[0417] 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 embodiments described in the claims or specification of the present disclosure.

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

[0419] 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 implementing 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 implementing an embodiment of the present disclosure.

[0420] In the specific embodiments of the present disclosure described above, components included in the invention are expressed singularly or plurally, 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 plural may be composed of singular elements, or components expressed in singular may be composed of plural elements.

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

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

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

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

[0425] 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. In a wireless communication system, the terminal (user equipment) is transceiver; and Including a controller coupled to the above transmitter and receiver, The above controller, Receive, from a base station, first information for setting resources for a first symbol and second information for setting second resources for a second symbol, Receive, from the base station, a first downlink control information (DCI) including at least one of a first sounding reference signal resource indicator (SRI) for the first symbol or a second SRI for the second symbol, and configured to transmit a PUSCH (physical uplink shared channel) to the base station on at least one of the first symbol or the second symbol, The first SRI is associated with a first SRS resource before receiving the first DCI, and the symbol type of the first symbol is the same as the symbol type of the first SRS resource, and The second SRI is associated with a second SRS resource before receiving the first DCI, and the symbol type of the second symbol is the same as the symbol type of the second SRS resource.

2. In claim 1, The symbol type of the above first symbol is a SBFD (subband full duplex) symbol, and The symbol type of the above second symbol is a terminal that is a non-SBFD symbol.

3. A terminal according to claim 1, wherein the first DCI further includes at least one of a first transmit precoding matrix indicator (TPMI) corresponding to the first SRS resource or a second TPMI corresponding to the second SRS resource.

4. In claim 1, the controller, Receive a second DCI from the base station, the second DCI including a code point associated with a first transmission configuration indicator (TCI) state for a third symbol and a second TCI state for a fourth symbol, and Further configured to receive a PDSCH (physical downlink shared channel) from the base station on at least one of the third symbol or the fourth symbol, The symbol type of the above third symbol is an SBFD symbol, and The symbol type of the above fourth symbol is a terminal that is a non-SBFD symbol.

5. In a wireless communication system, the base station is transceiver; and Including a controller coupled to the above transmitter and receiver, The above controller, Transmitting to the terminal (user equipment) first information setting resources for the first symbol and second information setting resources for the second symbol, Transmitting to the terminal a first DCI (downlink control information) including at least one of a first SRI (sounding reference signal resource indicator) for the first symbol or a second SRI for the second symbol, and configured to receive a PUSCH (physical uplink shared channel) from the terminal on at least one of the first symbol or the second symbol, The first SRI is associated with a first SRS resource before receiving the first DCI, and the symbol type of the first symbol is the same as the symbol type of the first SRS resource, and The second SRI is associated with a second SRS resource before receiving the first DCI, and the symbol type of the second symbol is the same as the symbol type of the second SRS resource.

6. In claim 5, The symbol type of the above first symbol is a SBFD (subband full duplex) symbol, and A base station in which the symbol type of the second symbol is a non-SBFD symbol.

7. A base station according to claim 5, wherein the first DCI further includes at least one of a first transmit precoding matrix indicator (TPMI) corresponding to the first SRS resource or a second TPMI corresponding to the second SRS resource.

8. In claim 5, the controller, Transmitting to the terminal a second DCI including a code point associated with a first transmission configuration indicator (TCI) state for a third symbol and a second TCI state for a fourth symbol, and The terminal is further configured to transmit a PDSCH (physical downlink shared channel) on at least one of the third symbol or the fourth symbol, The symbol type of the above third symbol is an SBFD symbol, and A base station in which the symbol type of the fourth symbol is a non-SBFD symbol.

9. A method performed by a terminal (user equipment) in a wireless communication system, A step of receiving, from a base station, first information for setting resources for a first symbol and second information for setting resources for a second symbol; A step of receiving, from the base station, a first downlink control information (DCI) including at least one of a first sounding reference signal resource indicator (SRI) for the first symbol or a second SRI for the second symbol; and A step of transmitting a PUSCH (physical uplink shared channel) to the base station on at least one of the first symbol or the second symbol, The first SRI is associated with a first SRS resource before receiving the first DCI, and the symbol type of the first symbol is the same as the symbol type of the first SRS resource, and The second SRI is associated with a second SRS resource before receiving the first DCI, and the symbol type of the second symbol is the same as the symbol type of the second SRS resource.

10. In claim 9, The symbol type of the above first symbol is a SBFD (subband full duplex) symbol, and A method in which the symbol type of the second symbol is a non-SBFD symbol.

11. A method according to claim 9, wherein the first DCI further includes at least one of a first transmit precoding matrix indicator (TPMI) corresponding to the first SRS resource or a second TPMI corresponding to the second SRS resource.

12. In claim 9, the method comprises: A step of receiving a second DCI from the base station, the second DCI including a code point associated with a first transmission configuration indicator (TCI) state for a third symbol and a second TCI state for a fourth symbol; and Further comprising a step of receiving a physical downlink shared channel (PDSCH) from the base station on at least one of the third symbol or the fourth symbol, The symbol type of the above third symbol is an SBFD symbol, and A method in which the symbol type of the fourth symbol is a non-SBFD symbol.

13. A method performed by a base station in a wireless communication system, A step of transmitting, to a terminal (user equipment), first information for setting resources for a first symbol and second information for setting resources for a second symbol; A step of transmitting, to the terminal, a first downlink control information (DCI) including at least one of a first sounding reference signal resource indicator (SRI) for the first symbol or a second SRI for the second symbol; and A step of receiving a PUSCH (physical uplink shared channel) from the terminal on at least one of the first symbol or the second symbol, The first SRI is associated with a first SRS resource before receiving the first DCI, and the symbol type of the first symbol is the same as the symbol type of the first SRS resource, and The second SRI is associated with a second SRS resource before receiving the first DCI, and the symbol type of the second symbol is the same as the symbol type of the second SRS resource.

14. In claim 13, The symbol type of the above first symbol is a SBFD (subband full duplex) symbol, and A method in which the symbol type of the second symbol is a non-SBFD symbol.

15. A method according to claim 13, wherein the first DCI further includes at least one of a first transmit precoding matrix indicator (TPMI) corresponding to the first SRS resource or a second TPMI corresponding to the second SRS resource.

Images