Method and apparatus for full duplex communication and fallback operation in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. Specifically, a method performed by a terminal in a wireless communication system according to the present disclosure comprises the operations of: receiving configuration information of a time resource for subband non-overlapping full duplex (SBFD) communication from a base station; identifying an index of at least one symbol or slot corresponding to an available SBFD time resource within a frame configuration period on the basis of the configuration information; performing the SBFD communication according to the identified index; receiving information about a mode change indicator for TDD communication from the base station; and stopping the SBFD communication and performing the TDD communication on the basis of the information about the mode change indicator.

Description

Method and device for full-duplex communication and fallback operation in a wireless communication system

[0001] The present disclosure relates to the operation of a terminal and a base station in a wireless communication system (or mobile communication system). Specifically, the present disclosure relates to a method and device for full duplex communication (or full duplex radio (FDR)) in a wireless communication system (or mobile 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 meet 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 (band-width part), new channel coding methods such as LDPC (low density parity check) codes for large-capacity data transmission and polar codes for reliable transmission of control information, L2 pre-processing, Standardization has been progressed for network slicing, which provides dedicated networks specialized for specific services.

[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 meets 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] Meanwhile, with the development of communication systems, the demand for the development of full-duplex communication is increasing day by day.

[0009] Based on the discussion described above, the present disclosure provides a device and method for effectively providing a service in a wireless communication system.

[0010] In addition, the present disclosure provides a method and device for efficiently setting / allocating time resources for full-duplex communication in a wireless communication system.

[0011] In addition, the present disclosure provides a fallback operation to a TDD (time-division duplex) mode for a terminal operating in SBFD mode in a wireless communication system supporting SBFD (subband non-overlapping full duplex) communication.

[0012] A method performed by a terminal in a wireless communication system according to an embodiment of the present disclosure may include a process of receiving configuration information of time resources for subband non-overlapping full duplex (SBFD) communication from a base station, a process of checking an index of at least one symbol or slot corresponding to available SBFD time resources within a frame configuration period based on the configuration information, a process of performing SBFD communication based on the checked index, a process of receiving information on a mode change indicator for TDD communication from the base station, and a process of stopping SBFD communication and performing TDD communication based on the information on the mode change indicator.

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

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

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

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

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

[0018] FIG. 6 is a diagram for explaining 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.

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

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

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

[0022] FIG. 10 is a diagram illustrating an example of TDD (time division duplex) UL-DL resource allocation according to SBFD resource configuration information according to one embodiment of the present disclosure.

[0023] FIG. 11 illustrates an example of SBFD resource allocation when a symbol that does not support SBFD operation is included in an SBFD system according to an embodiment of the present disclosure.

[0024] FIG. 12 illustrates an example of indicating an SBFD time resource location in an SBFD system according to one embodiment of the present disclosure.

[0025] FIG. 13 illustrates an example of SBFD time resource allocation using multiple indicators in an SBFD system according to one embodiment of the present disclosure.

[0026] FIG. 14 is a diagram showing the end and start of SBFD operation of a base station according to one embodiment of the present disclosure.

[0027] FIG. 15 is a diagram illustrating an operation for setting a change in the TDD mode and SBFD mode of a base station according to one embodiment of the present disclosure.

[0028] FIG. 16 is a diagram illustrating an operation in which a terminal applies a mode change indicator as a starting point according to an embodiment of the present disclosure.

[0029] FIG. 17 is a diagram illustrating an operation in which a terminal applies a mode change indicator as an end point according to an embodiment of the present disclosure.

[0030] FIG. 18 is a diagram illustrating an operation in which a terminal applies a mode change indicator as an end point according to an embodiment of the present disclosure.

[0031] FIG. 19 is a diagram showing the operation of a base station and a terminal when the base station and the terminal transmit and receive a mode change indicator according to one embodiment of the present disclosure.

[0032] FIG. 20 illustrates the structure of a terminal in a wireless communication system according to an embodiment of the present disclosure.

[0033] FIG. 21 illustrates the structure of a base station in a wireless communication system according to an embodiment of the present disclosure.

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

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

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

[0037] 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 these may vary depending on the intention or custom of the user or operator. Therefore, their definitions should be made based on the contents throughout the specification.

[0038] Hereinafter, a 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 wireless access unit, a base station controller, a TRP (transmission and reception point), or a node on a network. A 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, a downlink (DL) refers to a wireless transmission path of a signal transmitted from a base station to a terminal, and an uplink (UL) refers to a wireless transmission path of a signal transmitted from a terminal to a base station.

[0039] Furthermore, while 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 with similar technical backgrounds or channel types. For example, this may include the fifth-generation mobile communication technology (5G, new radio, NR) developed after LTE-A, and the term "5G" below may also encompass existing LTE, LTE-A, and other similar services. Furthermore, the present disclosure may be applied to other communication systems with some modifications within the scope of the present disclosure, as determined by a person with skilled technical knowledge.

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

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

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

[0043] In this disclosure, phrases such as "A or B", "at least one of A and B", "at least one of A or B", "A, B, or C", "at least one of A, B, and C", and "at least one of A, B, or C" can each include any one of the items listed together in that phrase, or all possible combinations thereof. Terms such as "first", "second", or "first" or "second" may be used simply to distinguish the corresponding component from other corresponding components and do not limit the corresponding components in any other respect (e.g., importance or order).

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

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

[0046] Hereinafter, a base station (BS) 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, an eNB, a Node B, a radio access unit, a base station controller, or a node on a network. In addition, the BS may be a network entity including at least one of an IAB-donor (Integrated Access and Backhaul - donor), which is a gNB that provides network access to terminal(s) through a network of backhaul and access links in an NR system, and an IAB-node, which is a radio access network (RAN) node that supports NR access link(s) to the terminal(s) and supports NR backhaul links to the IAB-donor or another IAB-node. A user equipment (UE) may be at least one of a terminal, an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. The terminal is wirelessly connected via an IAB node and can transmit and receive data with an IAB donor connected via a backhaul link to at least one IAB node.

[0047] As a future communication 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-reliable low-latency communication (URLLC).

[0048] 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 a single base station. Furthermore, 5G communication systems must simultaneously provide the peak data rate and an increased user-perceived data rate for terminals. To meet these requirements, improvements in various transmission and reception technologies, including improved multi-input, multi-output (MIMO) transmission technology, are required. Furthermore, while LTE transmits signals using a maximum 20 MHz transmission bandwidth in the 2 GHz band, 5G communication systems can meet the data transmission rates required by 5G communication systems by utilizing a wider frequency bandwidth than 20 MHz in the 3-6 GHz or higher 6 GHz bands.

[0049] 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 Internet of Things, mMTC requires support for large-scale terminal connection within a cell, improved terminal coverage, improved battery life, and reduced terminal costs. The Internet of Things provides communication functions by attaching various sensors and various devices, so a large number of terminals (e.g., 1,000,000 terminals / km) are required within a cell. 2) must be able to support. Furthermore, terminals supporting mMTC are likely to be located in shadow areas not covered by cells, such as basements of buildings, due to the nature of the service, and thus may require wider coverage than other services provided by 5G communication systems. Terminals supporting mMTC must be composed of low-cost terminals, and because it is difficult to frequently replace the terminal's battery, a very long battery life time, such as 10 to 15 years, may be required.

[0050] Finally, URLLC refers to a cellular-based wireless communication service used for a specific purpose (mission-critical). For example, services such as remote control of robots or machinery, industrial automation, unmanned aerial vehicles (UAVs), remote health care, and emergency alerts can be considered. Therefore, the communication provided by URLLC must provide very low latency and very high reliability. For example, a service supporting URLLC must satisfy an air interface latency of less than 0.5 milliseconds and, at the same time, must have a 10 -5 The following packet error rate (PER) requirements apply. Therefore, for services supporting URLLC, 5G systems must provide a smaller transmission 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.

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

[0052] For convenience of explanation, some terms and names defined in the 3GPP standards (standards for 5G, NR, LTE, or similar systems) may be used. However, the present disclosure is not limited to these terms and names, and the present disclosure can be equally applied to systems conforming to other standards. Furthermore, the terms used in the embodiments of the present disclosure below are not limited to these terms, and other terms that refer to objects with equivalent technical meanings may be used.

[0053] [NR time-frequency resources]

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

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

[0056] The horizontal axis of Figure 1 represents the time domain, and the vertical axis represents the frequency domain. The basic unit of resources in the time and frequency domains is a resource element (RE, 101), which can be defined as 1 OFDM (Orthogonal Frequency Division Multiplexing) symbol (102) on the time axis and 1 subcarrier (103) on the frequency axis. In the frequency domain (For example, 12) consecutive REs can form one Resource Block (RB, 104). In Fig. 1. is the number of OFDM symbols per subframe (110) for setting the subcarrier spacing (μ), and a more specific description of the resource structure in a 5G system can be referred to the TS 38.211 section 4 specification.

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

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

[0059]

[0060] [Bandwidth Part (BWP)]

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

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

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

[0064]

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

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

[0067] According to some embodiments, a terminal before an RRC (Radio Resource Control) connection can be configured with 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, during the initial access phase, configuration information about a control resource set (CORESET) and a search space on which a physical downlink control channel (PDCCH) can be transmitted for receiving system information required for initial access (which may correspond to Remaining System Information (RMSI) or System Information Block 1 (SIB1)) through the MIB. The control resource set and the search space configured through the MIB may each be regarded as having an identifier (Identity, ID) 0. The control resource set and the search space configured through the MIB may be referred to as a common control resource set and a common search space, respectively. 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 MIB. In addition, the base station can notify the terminal of configuration information for monitoring cycle and occasion for control region #0, i.e. configuration information for search space #0, through MIB. The terminal can regard the frequency region set as control resource set #0 obtained from the MIB as an initial bandwidth portion for initial access. At this time, the identifier (ID) of the initial bandwidth portion can be regarded as 0. The control resource set may be referred to as a control region, a control resource region, etc.

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

[0069] In some embodiments, when the bandwidth supported by a terminal is smaller than the system bandwidth, this can be supported through bandwidth portion configuration. For example, the base station can configure the frequency location of the bandwidth portion for the terminal, allowing the terminal to transmit and receive data at a specific frequency location within the system bandwidth.

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

[0071] Furthermore, in some embodiments, the base station may configure bandwidth portions with different bandwidth sizes for the terminal for the purpose of reducing power consumption of the terminal. For example, if the terminal supports a very large bandwidth, such as 100 MHz, and constantly transmits and receives data within that bandwidth, very large power consumption may occur. In particular, monitoring unnecessary downlink control channels with a large bandwidth of 100 MHz in a traffic-free environment 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, such as 20 MHz, for the terminal. In a traffic-free environment, the terminal may perform monitoring operations in the 20 MHz bandwidth portion, and when data is generated, it may transmit and receive data in the 100 MHz bandwidth portion according to the instructions of the base station.

[0072] In the method for setting the bandwidth part, terminals before RRC connection (Connected) can receive setting information for the initial bandwidth part (Initial Bandwidth Part) through MIB (Master Information Block) in the initial access stage. More specifically, the terminal can receive a 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 from the MIB of a physical broadcast channel (PBCH). The bandwidth of the control resource set set by the MIB can be regarded as the initial bandwidth part, and the terminal can receive the physical downlink shared channel (PDSCH) 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 (OSI), paging, and random access.

[0073] [Bandwidth Part (BWP) Switching]

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

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

[0076]

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

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

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

[0080] [SS / PBCH block]

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

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

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

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

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

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

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

[0088] [PDCCH: DCI related]

[0089] Next, we will specifically explain downlink control information (DCI) in 5G systems.

[0090] 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 included in DCI and transmitted from the base station to the terminal. The terminal can monitor the DCI format for fallback and the 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.

[0091] DCI can be transmitted over the physical downlink control channel (PDCCH) after going through the channel coding and modulation process. A cyclic redundancy check (CRC) is attached to the DCI message payload, and the CRC can be scrambled with a radio network temporary identifier (RNTI) corresponding to the identity of the UE. Different RNTIs can be used depending on the purpose of the DCI message, such as UE-specific data transmission, power control command, or random access response. That is, the RNTI is not transmitted explicitly, but is included in the CRC calculation process. When the UE receives a DCI message transmitted over the PDCCH, it verifies the CRC using the assigned RNTI. If the CRC verification result is correct, the UE can determine that the message was transmitted to the UE.

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

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

[0094]

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

[0096]

[0097]

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

[0099]

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

[0101]

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

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

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

[0105] The control resource set in the aforementioned 5G can be configured by the base station to the terminal via higher-layer signaling (e.g., SIB, MIB, RRC signaling). Configuring a control resource set for the terminal means providing information such as the control resource set identifier (Identity), the frequency location of the control resource set, and the symbol length of the control resource set. For example, the configuration information for the control resource set may include the information in Table 8.

[0106]

[0107] In the above Table 8, the tci-StatesPDCCH (hereinafter simply referred to as TCI (Transmission Configuration Indication) state) configuration information may include information on one or more SS / PBCH 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 resource set.

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

[0109] 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 resource set is established, the corresponding area can be composed of multiple CCEs (504), and a specific downlink control channel can be mapped to one or multiple CCEs (504) and transmitted according to the aggregation level (AL) within the control resource set. CCEs (504) within the control resource set are distinguished by numbers, and the numbers of the CCEs (504) can be assigned according to a logical mapping method.

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

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

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

[0113]

[0114]

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

[0116] According to the above 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 set as a common search space, and search space set #3 and search space set #4 may be set as terminal-specific search spaces.

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

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

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

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

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

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

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

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

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

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

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

[0128] - TC-RNTI (temporary cell RNTI): For terminal-specific PDSCH scheduling purposes

[0129] - CS-RNTI (configured scheduling RNTI): For terminal-specific PDSCH scheduling that is set semi-statically.

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

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

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

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

[0134] - TPC-PUSCH-RNTI (transmit power control for PUSCH RNTI): Used to indicate power control commands for PUSCH.

[0135] - TPC-PUCCH-RNTI (transmit power control for PUCCH RNTI): Used to indicate power control commands for PUCCH.

[0136] - TPC-SRS-RNTI (transmit power control for SRS RNTI): Used to indicate power control commands for SRS.

[0137] The aforementioned specified DCI formats may follow definitions such as the examples in Table 10.

[0138]

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

[0140]

[0141] - : Integration level

[0142] - : Carrier Index

[0143] - : Total number of CCEs existing within the control resource set p

[0144] - : slot index

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

[0146] - PDCCH candidate index for aggregation level L

[0147] -

[0148] -

[0149] - : Terminal identifier

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

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

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

[0153] [PDCCH: BD(blind decoding) / CCE limit]

[0154] When multiple search space sets are set for a terminal, the following conditions may be considered in determining the search space set that the terminal should monitor.

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

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

[0157] As described above, depending on the setting value of the upper layer signaling, the maximum number of PDCCH candidates that the terminal can monitor is M. μ The subcarrier spacing is 15*2 μ When defined by slot in a cell set to kHz, Table 11 below can be followed, and when defined by span, Table 12 below can be followed.

[0158]

[0159]

[0160] [Condition 2: Maximum CCE limit]

[0161] As above, according to the setting value of the upper layer signaling, the maximum number of CCEs that constitute the entire search space (here, the entire search space means the entire set of CCEs corresponding to the union area of ​​multiple search space sets) is C μ The subcarrier spacing is 15*2 μWhen defined by slot in a cell set to kHz, Table 13 below may be followed, and when defined by span, Table 14 below may be followed.

[0162]

[0163]

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

[0165] [PDCCH: Overbooking]

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

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

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

[0169] If all search space sets set as common search spaces are selected (i.e., if the above condition A is satisfied even after selecting all search spaces set as common search spaces), the terminal (or base station) can select search space sets set as terminal-specific search spaces. In this case, if there are multiple search space sets set as terminal-specific search spaces, a search space set with a lower search space set index may have a higher priority. Taking the priority into account, terminal-specific search space sets can be selected within the range where the above condition A is satisfied.

[0170] [Rate matching / Puncturing related]

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

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

[0173] Rate Matching Operation

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

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

[0176] Puncture action

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

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

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

[0180] Figure 6 is a diagram for explaining a method in which a base station and a terminal transmit and receive data by considering downlink data channels and rate matching resources.

[0181] FIG. 6 illustrates a downlink data channel (PDSCH, 601) and a rate matching resource (602). A base station can configure one or more rate matching resources (602) to a terminal through upper layer signaling (e.g., RRC signaling). Rate matching resource (602) configuration information may include time-domain resource allocation information (603), frequency-domain resource allocation information (604), and period information (605). In the following, the bitmap corresponding to the frequency-domain resource allocation information (604) is named "the first bitmap", the bitmap corresponding to the time-domain resource allocation information (603) is named "the second bitmap", and the bitmap corresponding to the period information (605) is named "the third bitmap". When all or part of the time and frequency resources of a 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.

[0182] The base station can dynamically notify the terminal via DCI whether to rate-match the data channel in the set rate-matching resource portion through additional configuration (corresponding to the "rate-matching indicator" in the 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, and can use a bitmap to indicate to the terminal via DCI whether the data channel for each rate-matching resource group is rate-matched. For example, if four rate-matching resources, RMR#1, RMR#2, RMR#3, and RMR#4, are set, the base station can set RMG#1={RMR#1, RMR#2}, RMG#2={RMR#3, RMR#4} as the rate-matching groups, and can use two bits in the DCI field to indicate to the terminal whether to rate-match in RMG#1 and RMG#2, respectively, using a bitmap. For example, if rate matching is required, it can be indicated as "1", and if rate matching is not required, it can be indicated as "0".

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

[0184] RB symbol level

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

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

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

[0188] RE level

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

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

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

[0192] [Regarding LTE CRS rate match]

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

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

[0195] Table 15 shows a ServingCellConfig IE that includes the above CRS pattern, and Table 16 shows a RateMatchPatternLTE-CRS IE that includes at least one parameter for the CRS pattern.

[0196] [Table 15]

[0197]

[0198]

[0199] [Table 16]

[0200]

[0201] [PDSCH: Frequency Resource Allocation Related]

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

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

[0204] Referring to Fig. 7, if the terminal is set to use only resource type 0 through upper layer signaling (700), some downlink control information (DCI) that allocates PDSCH to the terminal is N RBG It includes a bitmap (715) consisting of N bits. The conditions for this will be explained later. At this time, N RBGrefers to the number of RBGs (resource block groups) determined as shown in [Table 17] below according to the BWP size allocated by the BWP indicator and the upper layer parameter rbg-Size, and data is transmitted to the RBG indicated as 1 by the bitmap.

[0205]

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

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

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

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

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

[0211]

[0212]

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

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

[0215] Referring to FIG. 8, the base station uses upper layer signaling to establish a subcarrier spacing (SCS) (μ) of a data channel and a 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.

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

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

[0218] [PUSCH: Transmission Method Related]

[0219] Next, the scheduling method for PUSCH transmission is described. PUSCH transmission can be dynamically scheduled by the UL grant in the DCI or can be operated by the configured grant Type 1 or Type 2. Dynamic scheduling instructions for PUSCH transmission are possible in DCI format 0_0 or 0_1.

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

[0221]

[0222]

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

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

[0225] [Table 21]

[0226]

[0227] Next, we describe codebook-based PUSCH transmission. Codebook-based PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1, or can be semi-statically operated by a configured grant. When codebook-based PUSCH is dynamically scheduled via DCI format 0_1 ​​or semi-statically configured via a configured grant, the UE determines a precoder for PUSCH transmission based on the SRS Resource Indicator (SRI), the transmission precoding matrix indicator (TPMI), and the transmission rank (the number of PUSCH transmission layers).

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

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

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

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

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

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

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

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

[0236] When multiple SRS resources are configured, the UE can determine the precoder and transmission rank to be applied to PUSCH transmission based on the SRI indicated by the base station. At this time, the SRI can be indicated through the SRS resource indicator field in the DCI or can be set 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 refers to the SRS resource corresponding to the SRI among the SRS resources transmitted before the PDCCH containing the SRI. The UE can use one or more SRS resources for SRS transmission, and the maximum number of SRS resources that can be simultaneously transmitted in the same symbol within one SRS resource set and the maximum number of SRS resources are determined by the UE capability reported by the UE to the base station. At this time, the SRS resources that the UE simultaneously transmits occupy the same RB. The UE configures one SRS port for each SRS resource. Only one SRS resource set with the usage value set to 'nonCodebook' in the upper signaling SRS-ResourceSet can be set, and up to four SRS resources for non-codebook based PUSCH transmission can be set.

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

[0238] [PUSCH: Preparation time]

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

[0240]

[0241] T in the above mathematical formula 2 proc,2 In , each variable can have the following meanings:

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

[0243]

[0244]

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

[0246] - : 64

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

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

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

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

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

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

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

[0254] [SBFD: SBFD Overview]

[0255] Meanwhile, 3GPP is discussing Subband Non-Overlapping Full Duplex (SBFD) as a new NR-based full duplex communication method. 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. This expands the uplink coverage of the terminal by the amount of increased uplink transmission resources, and the base station can reduce feedback delay by receiving feedback from the terminal regarding downlink transmission using the expanded uplink resources. In the present disclosure, the terminal receives information on whether SBFD is supported from the base station, and a terminal capable of performing uplink transmission using a portion of downlink resources may be conveniently referred to as an SBFD terminal (SBFD-capable UE). The following methods may be considered to define the SBFD method in the standard and for the SBFD terminal to determine whether SBFD is supported in a specific cell (or frequency, frequency band).

[0256] First method: In addition to the existing unpaired spectrum (or time division duplex, TDD) or paired spectrum (or frequency division duplex, FDD) frame structure types, another frame structure type (e.g., frame structure type 2) may be introduced to define the above SBFD. The above frame structure type 2 may be defined to be supported in the specific frequency or frequency band, or the base station may indicate to the terminal whether SBFD is supported through at least one of system information or the above-mentioned higher layer signaling. The SBFD terminal may receive system information including whether SBFD is supported and determine whether SBFD is supported in the specific cell (or frequency, frequency band).

[0257] Second method: Whether SBFD is additionally supported in a specific frequency or frequency band of an existing unpaired spectrum (or TDD) can be indicated without defining a new frame structure type. In the second method, whether SBFD is additionally supported in a specific frequency or frequency band of an existing unpaired spectrum can be defined, or the base station can indicate to the terminal whether SBFD is supported through at least one of system information or the above-mentioned higher layer signaling. The SBFD terminal can receive system information including whether SBFD is supported and determine whether SBFD is supported in the specific cell (or frequency, frequency band).

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

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

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

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

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

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

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

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

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

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

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

[0269] Typically, a terminal can establish a wireless link with a network through a random access procedure based on synchronization with the network and system information acquired during the cell search process. Random access can be either contention-based or contention-free. Contention-based random access can be used when a terminal performs cell selection and reselection during the initial cell access phase, for example, when moving from the RRC_IDLE state to the RRC_CONNECTED state. Contention-free random access can be used to reestablish uplink synchronization when downlink data arrives, in the case of a handover, or in the case of position measurement.

[0270] [SBFD: Time resource allocation related to SBFD operation]

[0271] An SBFD terminal can be configured with time resources that enable SBFD operation from a base station, and some slots or some symbols within the configured period can be configured as SBFD slots or SBFD symbols. The terminal can transmit a signal on an uplink channel through an SBFD uplink subband within the configured SBFD time resources. The configured period can be a period of a TDD structure used in a conventional wireless communication system, an SSB transmission period of a base station, a frame period (e.g., 10 ms), an integer multiple of a frame period (e.g., 20 ms), a period of a frame structure type newly defined for SBFD operation, or a period determined by a combination of the above periods. SBFD time resource allocation can be performed by additionally indicating whether SBFD is supported in the TDD structure, or by defining a slot type dedicated to SBFD operation in addition to downlink, uplink, and special slots, and using this in a conventional TDD time resource allocation process.

[0272] When additionally indicating whether SBFD is supported in the conventional TDD structure, the SBD time resource setting cycle may be a multiple of the TDD time resource setting cycle for time alignment with the TDD system. In this case, within the SBFD setting cycle, after indicating SBFD time resources within the TDD setting cycle length, whether SBFD is supported may be determined for each TDD setting cycle length unit.

[0273] FIG. 10 is a diagram illustrating an example of time resource allocation according to SBFD time resource configuration information according to an embodiment of the present disclosure, and FIG. 10 illustrates an embodiment of a method for additionally indicating whether SBFD is supported in an existing TDD structure. In (a), (b), (c), and (d) of FIG. 10, reference symbol "D" indicates a DL slot to which only DL symbols are allocated in a TDD structure, "U" indicates a UL slot to which only UL symbols are allocated in a TDD structure, and "S" indicates a special slot to which both DL symbols and UL symbols are allocated in a TDD structure.

[0274] Referring to FIG. 10, (a) of FIG. 10 illustrates a basic TDD resource allocation method, and (b), (c), and (d) of FIG. 10 illustrate an example of an SBFD resource allocation method according to SBFD resource configuration information 1, 2, and 3. A TDD period may include UL slots (1001, 1011, 1021, 1031), and an uplink subband (1010, 1020) may be allocated within the frequency resources of a DL slot or a special slot. A symbol to which an uplink subband is allocated may be referred to as an SBFD symbol, and a slot including the SBFD symbol may be referred to as an SBFD slot.

[0275] SBFD symbols can be allocated in various patterns (1012, 1022, 1032, 1033, 1034) within a TDD period, as shown in examples of (b), (c), and (d) of Fig. 10. All or part of the symbols within a slot can be allocated as SBFD symbols. Fig. 10 (d) illustrates a method of setting SBFD time resources within a TDD period and then indicating whether or not to operate the SBFD for each TDD period. Whether or not to operate the SBFD for each TDD period can be indicated using a bitmap method in which the first TDD period within the SBFD setting period is set to index 0 and the SBFD operation for each index is indicated by bit, or a SLIV (start and length indicator value) method in which the start index and the length of the TDD period in which the SBFD operation is performed are encoded together. For example, in (d) of Fig. 10, whether SBFD operation is performed or not can be indicated for each TDD period using a bitmap method as '1100', or using a SLIV method using a start index of 0 and a length of 2. The SBFD terminal can receive time resource information for an SBFD symbol or slot within the SBFD configuration period from the base station before uplink transmission.

[0276] In a 5G wireless communication system, a symbol can be divided into a DL (downlink) symbol to support downlink transmission, a UL (uplink) symbol to support uplink transmission, and an F (flexible) symbol that can be set in either the downlink or uplink direction. When the SBFD operation is additionally indicated in the TDD structure, if the symbol for which the base station indicates the SBFD operation includes a UL or F symbol, the SBFD configuration information can have priority only for the DL symbol. For example, if the SBFD operation is set for the UL or F symbol, the SBFD configuration information can be ignored and only the existing symbol configuration can be followed. Alternatively, the base station can indicate the SBFD operation only for the time resource set as the DL symbol.

[0277] For example, if the configuration (or setting) of time resources follows {Symbol#0(DL), Symbol#1(DL), Symbol#2(DL), Symbol#3(UL), Symbol#4(F), Symbol#5(DL), Symbol#6(DL)}, and the base station instructs SBFD operation for symbol indices '0~3', the configuration of time resources may be {Symbol#0(SBFD), Symbol#1(SBFD), Symbol#2(SBFD), Symbol#3(UL), Symbol#4(F), Symbol#5(SBFD), Symbol#6(DL)}. Alternatively, the base station may provide information about SBFD operation instruction only for DL ​​symbols excluding UL symbols and F symbols. For example, when the configuration of time resources is {Symbol #0 (DL), Symbol #1 (DL), Symbol #2 (DL), Symbol #3 (DL), Symbol #4 (DL), Symbol #5 (UL), Symbol #6 (UL)}, and the base station wants to instruct SBFD operation using the index of the symbol, the index that the base station can set can only have a value between 0 and 4. The following examples can be given as the SBFD time resource setting method.

[0278] In the following, an example of a method for setting SBFD time resources using the number of consecutive slots and the starting slot position is described when additionally indicating whether SBFD operation is performed in the TDD structure.

[0279] In this example, the length of consecutive slots in the SBFD system ( ) and starting slot ( ) is used to describe a method for indicating SBFD time resource information. In this example, the method for defining the resource indication value (start and length indicator value, SLIV) indicating SBFD time resource information is as shown in [Table 24] below. Through the above example, the base station can indicate to the terminal the location of consecutive slots for SBFD operation within the SBFD cycle.

[0280]

[0281] The above SBFD setting cycle is [ms], subcarrier spacing numerology When the total number of slots within the above setting period is )cast can be calculated as follows. At this time, the slots within the cycle T[ms] can be indexed in ascending order of time. Among the slots of T[ms] within the cycle, the index of the first slot in time is 0 and the index of the last slot is Based on the above index, in Table 24, S may indicate the index of a slot in which an SBFD subband exists, and L may indicate the number of consecutive slots.

[0282] For reference, the present disclosure is described based on the SLIV method of Table 24 above, but can be expressed in the following manner. In the SLIV method, the start index S of the slot where the SBFD subband exists and the number L of consecutive slots where the SBFD subband exists are jointly encoded, but can be directed separately. That is, the terminal is ( ) can be set, and S = 0,1, ... is one of the values, L = 1,2,... is one of the values, silver Must be less than or equal to.

[0283] For reference, in Table 24 above is the SBFD setting cycle ( [ms]) is defined as the number of all slots. However, when setting the SBFD UL sub-band, the slots in which the SBFD UL sub-band can be set can be defined. In this case, is the SBFD setting cycle ( [ms]) can be defined as slots in which SBFD UL sub-bands can be set.

[0284] A slot for which an SBFD UL subband can be configured may be a slot including at least one downlink symbol and a flexible symbol. That is, a slot for which an SBFD UL subband cannot be configured may be a slot in which all symbols of the slot are uplink symbols. Here, the downlink symbol, the flexible symbol, and / or the uplink symbol may be configured in a TDD configuration transmitted in a system information block (SIB). Here, the downlink symbol, the flexible symbol, and / or the uplink symbol may be configured in a TDD configuration transmitted in a dedicated RRC (RRC) signal of a terminal.

[0285] A slot for which an SBFD UL sub-band can be configured may be a slot that does not include an uplink symbol. In other words, a slot for which an SBFD UL sub-band cannot be configured may be a slot that includes at least one uplink symbol. Here, the downlink symbol, the flexible symbol, and / or the uplink symbol may be configured in the TDD configuration transmitted in the SIB (system information block). Here, the downlink symbol, the flexible symbol, and / or the uplink symbol may be configured in the TDD configuration transmitted in the dedicated RRC signal of the terminal.

[0286] A slot in which an SBFD UL sub-band cannot be configured may be a slot in which an SS / PBCH is received. The terminal can receive the SS / PBCH to measure Radio Link Failure (RLF) or downlink signal quality. If the symbol in which the SS / PBCH is received is configured as a UL sub-band, the SS / PBCH reception quality of the terminal may deteriorate due to uplink transmissions from other terminals. Therefore, the slot in which an SS / PCBH is received may not be included in the slots in which an SBFD UL sub-band can be configured.

[0287] A slot in which an SBFD UL sub-band cannot be configured may be a slot that includes a symbol for monitoring a Type0-PDCCH CSS set. Here, the PDCCH received in the Type0-PDCCH CSS set is a PDCCH that schedules a PDSCH transmitting SIB1. If the PDCCH is not received in the Type0-PDCCH CSS set, the UE cannot obtain information for cell access. Therefore, a slot including a symbol for monitoring the Type0-PDCCH CSS set may not be included in a slot in which an SBFD UL sub-band can be configured.

[0288] A slot for which the SBFD UL subband cannot be configured may include a symbol configured as CSI-RS for tracking. Here, CSI-RS for tracking is a reference signal configured by the base station to monitor time-frequency changes in the downlink channel. In order for terminals within the cell to successfully monitor time-frequency changes in the downlink channel, a slot including a symbol configured as CSI-RS for tracking may not be included in the symbols for which the SBFD UL subband can be configured.

[0289] so, is the SBFD setting cycle ( When the slots within [ms] are defined as slots for which SBFD UL sub-bands can be set, the slot index can be assigned only to slots for which SBFD UL sub-bands can be set.

[0290] In the following, an example of a method for setting SBFD time resources using the number of consecutive symbols and the starting symbol position is described when additionally indicating whether SBFD operation is performed in the TDD structure in the present disclosure.

[0291] In this example, the length of consecutive symbols in the SBFD system shown in (a) of Fig. 12 ( , 1212) and the start symbol ( , 1213) is used to describe a method for indicating SBFD time resource information. In this example, the method for defining the resource indication value indicating SBFD time resource information is as shown in [Table 25] below. can be determined as 12 or 14 depending on the type of CP (cyclic prefix) set by the base station, which is ECP (extended CP) or NCP (normal CP). Through the above example, the base station can indicate to the terminal the location of consecutive symbols for SBFD operation within the SBFD cycle.

[0292]

[0293] The above SBFD setting cycle is [ms], subcarrier spacing numerology , and the total number of symbols in one slot is When the dog is, the total number of symbols within the above setting period ( )cast can be calculated as follows. At this time, the symbols within the period T[ms] can be indexed in ascending order of time. Among the T[ms] symbols within the period, the index of the first symbol in time is 0 and the index of the last symbol is Based on the above index, in Table 25, S may indicate the index of a symbol in which an SBFD subband exists, and L may indicate the number of consecutive symbols.

[0294] For reference, the present disclosure is based on the SLIV scheme of Table 25, but can be expressed as follows. In the SLIV scheme, the start index S of a symbol in which an SBFD subband exists and the number L of consecutive symbols in which an SBFD subband exists are jointly encoded, but S and L can be indicated separately. That is, the terminal can receive (S, L) from the base station, and S = 0, 1, ... is one of the values, L=1,2, ..., is one of the values, and S+L is Must be less than or equal to.

[0295] For reference, in Table 25 above is the SBFD setting cycle ( [ms]) is defined as the number of all symbols. However, when setting the SBFD UL subband, the symbols for which the SBFD UL subband can be set can be defined. In this case, is the SBFD setting cycle ( [ms]) can be defined as symbols for which the SBFD UL sub-band can be set.

[0296] The symbols for which the SBFD UL subband can be configured may include downlink symbols and flexible symbols. That is, the symbols for which the SBFD UL subband cannot be configured may be uplink symbols. Here, the downlink symbols, flexible symbols, and / or uplink symbols can be configured in the TDD settings transmitted in the SIB (system information block). Here, the downlink symbols, flexible symbols, and / or uplink symbols can be configured in the TDD settings transmitted in the dedicated RRC signal of the terminal.

[0297] A symbol for which the SBFD UL subband cannot be configured may be a symbol for which an SS / PBCH is received. The terminal can receive the SS / PBCH to measure Radio Link Failure (RLF) or downlink signal quality. If the symbol for which the SS / PBCH is received is configured as a UL subband, the SS / PBCH reception quality of the terminal may deteriorate due to uplink transmissions from other terminals. Therefore, the symbol for which the SS / PCBH is received may not be included in the symbols for which the SBFD UL subband can be configured.

[0298] A symbol for which the SBFD UL subband cannot be configured may be a symbol monitoring the Type0-PDCCH CSS set. Here, the PDCCH received in the Type0-PDCCH CSS set is a PDCCH that schedules the PDSCH transmitting SIB1. If the PDCCH is not received in the Type0-PDCCH CSS set, the UE cannot obtain information for cell access. Therefore, the symbol monitoring the Type0-PDCCH CSS set may not be included in the symbols for which the SBFD UL subband can be configured.

[0299] Symbols for which SBFD UL subbands cannot be configured may be symbols configured with CSI-RS for tracking. Here, CSI-RS for tracking is a reference signal configured by the base station to monitor time-frequency changes in the downlink channel. In order for terminals within the cell to successfully monitor time-frequency changes in the downlink channel, symbols configured with CSI-RS for tracking may not be included in symbols for which SBFD UL subbands can be configured.

[0300] Additionally, the symbols for which the SBFD UL subband cannot be set are the N symbols immediately following the symbols for which the SBFD UL subband cannot be set as defined above (SS / PBCH symbols, Type0-PDCCH CSS set symbols, CSI-RS for tracking symbols, etc.). gap,1 Symbol or just before N gap,2 It may be a symbol. This means that if there is an SBFD UL subband immediately after or immediately before the symbols, the terminal or base station cannot satisfy the TX-to-RX switching gap or the RX-to-TX switching gap. Therefore, some symbols immediately after or immediately before the symbol may not be used as SBFD UL subbands.

[0301] so, is the SBFD setting cycle ( When the symbols within [ms] are defined as symbols for which the SBFD UL sub-band can be set, the symbol index can be assigned only to symbols for which the SBFD UL sub-band can be set.

[0302] Hereinafter, in the present disclosure, when additionally indicating whether SBFD operation is performed in a TDD structure, an example of a method for setting SBFD time resources using the number of consecutive slots, the starting slot position, and the length of symbols within the slots at both ends will be described.

[0303] In this example, the length of consecutive slots in the SBFD system shown in (b) of Fig. 12 ( , 1223), starting slot ( , 1222) and a method of indicating SBFD time resource information using the length of consecutive symbols (1224, 1225) within the slots at both ends is described. The SBFD setting cycle [ms], subcarrier spacing numerology , and the total number of slots within the above setting cycle ( )cast It can be calculated as follows. The total number of symbols in one slot is can be 12 or 14 depending on the type of CP (cyclic prefix) set by the base station, which is ECP (extended CP) or NCP (normal CP). In this example, the base station can represent SBFD slot information including one or more SBFD symbols as SLIV according to the formula of [Table 24] above. In addition, the base station can indicate to the terminal the location of consecutive symbols for SBFD operation within the SBFD period by representing the lengths of symbols that do not perform SBFD operation from the last symbols of both end slots as A and B, respectively. At this time, the lengths of the two consecutive symbols (1224, 1225) can be expressed as natural numbers between 0 and 14, integers between 0 and 13, or 0 to X-1 (X is a natural number greater than or equal to 2).

[0304] In the following, an example of a method for setting SBFD time resources using the length of consecutive slots and symbols is described when additionally indicating whether SBFD operation is performed in the TDD structure.

[0305] This example describes a method of indicating SBFD time resource information using the length of consecutive slots and symbols in the SBFD system illustrated in (c) of FIG. 12. The base station can indicate the position of consecutive symbols for SBFD operation within the SBFD period to the terminal by indicating the length of consecutive slots (1233, 1236) that do not include SBFD symbols from both ends of the SBFD configuration period and the length of consecutive symbols (1234, 1235) that do not perform SBFD operation from the end point of the consecutive slots. The length of the consecutive slots (1233, 1236) is determined by the length of the SBFD configuration period. [ms], subcarrier spacing numerology When, from 0 It can be a natural number between 0 and 14, and the length of the two consecutive symbols (1234, 1235) can be a natural number between 0 and 14.

[0306] In the following, in the present disclosure, when additionally indicating whether SBFD operation is performed in the TDD structure, an example of a method for setting SBFD time resources using the start position of SBFD time resources within the SBFD setting cycle will be described.

[0307] This example describes a method of indicating SBFD time resource information using the start index of consecutive SBFD symbols within the SBFD period in the SBFD system shown in (d) of Fig. 12. The SBFD setting period is [ms], subcarrier spacing numerology , and the total number of symbols in one slot is When the dog is, the total number of symbols within the above setting period ( )cast It can be calculated as follows. It can be determined as 12 or 14 depending on the type of CP (cyclic prefix) set from the base station, which is ECP (extended CP) or NCP (normal CP).

[0308] When the base station designates the first symbol index as 0 within the SBFD period, it may indicate to the terminal the index of the first symbol among the consecutive SBFD symbols, and assume that all symbols before an uplink or flexible symbol appears within the SBFD period are SBFD symbols. In the case of (d) of Fig. 12, all symbols from the symbol having symbol index #12 (1242) to the symbol immediately preceding the uplink symbol (1249) may be indicated as SBFD symbols.

[0309] Within an SBFD time resource configuration cycle, there may be one or more indicators indicating SBFD time resources. Each indicator may represent a different SBFD time resource allocated consecutively within the SBFD time resource configuration cycle. In the case of an SBFD configuration that additionally indicates whether SBFD is supported in a conventional TDD system, different indicators may be designated according to each slot pattern of the TDD system. Alternatively, multiple indicators may be used within the SBFD configuration cycle to indicate one or more consecutive SBFD time resource groups.

[0310] FIG. 13 is a diagram illustrating an example of SBFD time resource allocation using multiple indicators according to one embodiment of the present disclosure.

[0311] FIG. 13 (a) is a diagram illustrating an example of indicating whether SBFD operation is performed for each pattern in a TDD structure in which two TDD patterns are used according to an embodiment of the present disclosure. In this example, two indicators may be used, one for the SBFD time resource area indicated by pattern 1 (1301, 1303) and one for the SBFD time resource area indicated by pattern 2 (1302, 1304). FIG. 13 (b) is a diagram illustrating an example of indicating whether SBFD operation is performed for a TDD structure using four indicators (1311, 1312, 1313, 1314) within an SBFD setting period according to an embodiment of the present disclosure. Using each indicator, a total of four groups of SBFD time resource areas may be indicated within the SBFD setting period.

[0312] According to one embodiment of the present disclosure, the SBFD time resource configuration cycle may be identical to the TDD configuration cycle. When two TDD patterns exist in the TDD configuration cycle, the terminal may be configured with indicators indicating two SBFD time resources. Among the two SBFD time resources, the first SBFD time resource may be applied to the first TDD pattern among the two TDD patterns, and the second SBFD time resource may be applied to the second TDD pattern.

[0313] Here, the first TDD pattern may have a period of P1 [ms], the second TDD pattern may have a period of P2 [ms], and the TDD setting period may be P1+P2 [ms]. The first TDD pattern includes information for setting whether symbols included in P1 [ms] are downlink, uplink, or flexible symbols, and the second TDD pattern includes information for setting whether symbols included in P2 [ms] are downlink, uplink, or flexible symbols. The terminal may apply the first TDD pattern to the symbols included in P1 [ms] first among the symbols included in P [ms], and apply the second TDD pattern to the symbols included in P2 [ms] later.

[0314] Accordingly, the terminal can be set to the first SBFD time resource within P1 [ms] and to the second SBFD time resource within P2 [ms]. The first SBFD time resource setting and the second SBFD time resource setting can be instructed based on the SLIV formula.

[0315] Referring to Table 24, the first SBFD time resource setting and the second SBFD time resource setting can be indicated by slot-based SLIV. In the first method, in the SLIV indicating the first SBFD time resource setting and the SLIV indicating the second SBFD time resource setting, may be the number of slots included in P [ms]. The first slot among the slots included in the period P [ms] may be considered as 0, and the slots may be indexed in ascending order of time. S determined from SLIV indicating the first SBFD time resource setting is the index of the slot where the first SBFD time resource starts, and L is the number of consecutive slots where the first SBFD time resource exists. S determined from SLIV indicating the second SBFD time resource setting is the index of the slot where the second SBFD time resource starts, and L is the number of consecutive slots where the first SBFD time resource exists.

[0316] In the second method, in SLIV, which indicates the first SBFD time resource setting, may be the number of slots included in P1 [ms]. In SLIV which indicates the second SBFD time resource setting. may be the number of slots included in P2 [ms]. When interpreting the SLIV indicating the first SBFD time resource setting, the first slot among the slots included in the period P1 [ms] may be considered as 0, and an index may be assigned to each slot in ascending chronological order. S determined from the SLIV indicating the first SBFD time resource setting is the index of the slot where the first SBFD time resource starts, and L is the number of consecutive slots in which the first SBFD time resource exists. When interpreting the SLIV indicating the second SBFD time resource setting, based on the index, the first slot among the slots included in the period P2 [ms] may be considered as 0, and an index may be assigned to each slot in ascending chronological order. S, determined from SLIV indicating the second SBFD time resource setting, is the index of the slot where the second SBFD time resource starts, and based on the index, L is the number of consecutive slots where the first SBFD time resource exists.

[0317] When a terminal is configured with two SBFD time resources, an SBFD frequency resource corresponding to each SBFD time resource can be configured. According to the present disclosure, even if a terminal is configured with two SBFD time resources, the SBFD frequency resources corresponding to each SBFD time resource can be the same. That is, the base station can configure one SBFD frequency resource and two SBFD time resources. The terminal can determine a first SBFD resource (time-frequency resource) with the one SBFD frequency resource and the first SBFD time resource. In addition, the terminal can determine a second SBFD resource (time-frequency resource) with the one SBFD frequency resource and the second SBFD time resource.

[0318] The above SBFD time resource configuration information can be included in one or more messages among RRC or MAC (medium access control) CE (control element) or DCI to limit a UE group using the same SBFD time resource configuration information or to determine a configuration information update cycle. For example, the SBFD time resource configuration information included in a SIB1 message can be cell-specific information that applies to all UEs included in the corresponding cell. Next, the SBFD time resource configuration information belonging to a dedicated RRC (dedicated RRC) message can be UE-specific information. The SBFD time resource configuration information of a DCI or MAC CE message can be used to update the SBFD time resource configuration within a shorter time than the SBFD time resource configuration information. In the case of dynamic SBFD time resource allocation using the DCI or MAC CE message, the SBFD time resource information can be indicated using a slot format indocator. An example of a SBFD time resource configuration method using the slot format indocter can be as follows. The above slot type indicator may be transmitted to the terminal as a direct value or indirectly to the terminal through another indicator set by the base station.

[0319] In the following, an example of a method for setting SBFD time resources using a predefined time domain pattern for all symbols within a slot is described.

[0320] This example describes an example of setting SBFD time resources using a predefined time resource pattern for symbols within a slot. The pattern can be a pattern indicating whether SBFD operation is performed for symbols within a slot in a method of additionally indicating whether SBFD is supported in a TDD structure, or a pattern indicating information about downlink, uplink, flexible, and SBFD symbol allocation within a slot in a method of defining slots and symbol types dedicated to SBFD operation and using them in a conventional TDD time resource allocation process. To indicate the pattern, the base station can use an indication value assigned to each pattern. Table 26 below shows examples of patterns and indication values ​​that can be used when additionally indicating whether SBFD is supported in a TDD structure for symbols within a slot. 0 and 1 in each row can represent a symbol that does not perform SBFD operation and a symbol that is instructed to perform SBFD operation.

[0321]

[0322] In the case of the above dynamic SBFD time resource configuration method, the minimum time (hereinafter, application time) and update cycle required to apply the dynamically indicated new SBFD time resource configuration information can be considered. In the case of the application time, the updated SBFD time resource configuration information can be applied to the terminal operation immediately after receiving the updated SBFD time resource configuration information, after a certain slot length, a certain symbol length, or a certain delay time. The terminal can update the SBFD time resource configuration information and use it for actual communication immediately after the application time, the TDD period immediately after the application time, the slot immediately after the application time, or after a certain time designated from the upper level. In the above dynamic SBFD time resource configuration method, the SBFD time resource configuration information can be dynamically changed based on scheduling information without considering the application time or update cycle. For example, different SBFD time resource configuration information can be indicated for each BWP, and the SBFD time resource configuration used can be changed according to BWP switching. When the SBFD time resource setting of a terminal is updated and the DL reception resource belonging to the area where the SBFD uplink sub-band is designated cannot be used, the terminal may follow the following example to process the data sequence mapped to the DL reception resource. The terminal may not receive the data sequence of all downlink channels mapped to the DL reception resource, or may not operate for reception of only some data sequences among the data sequences of the downlink channels received semi-statically or dynamically.

[0323] In a 5G wireless communication system, when additionally indicating whether or not to perform SBFD operation in a conventional TDD structure, some time resources may not support SBFD operation due to reasons such as initial access, random access, and transmission of reference signals. In the case of the unavailable symbol, even if the SBFD operation is indicated through the SBFD setting, it may not be followed. That is, even if the SBFD setting information of the base station includes an SBFD operation indication for the unavailable symbol, the unavailable symbol may be a symbol that does not perform the SBFD operation. The operation for the unavailable symbol may be performed in the following manner.

[0324] First, the SBFD setting instruction can be ignored only for the above-mentioned unavailable symbols. FIG. 11 is a diagram illustrating an example of time domain resource allocation in a case where symbols that do not support the SBFD operation are included due to initial access, random access, transmission of a reference signal, etc., when setting time resources for SBFD operation in an SBFD system according to an embodiment of the present disclosure. FIG. 11 (a) illustrates an example of conventional TDD time resource allocation in which SBFD resources are not allocated. FIG. 11 (b), (c), and (d) illustrate examples of time resource allocation including SBFD symbols that may occur in a terminal when SBFD operation is indicated for all DL symbols belonging to the TDD structure. FIG. 11 (b) is a diagram illustrating an example in which the SBFD operation is not performed only for the unavailable symbol, FIG. 11 (c) is a diagram illustrating an example in which the SBFD operation is not performed for the entire slot including the unavailable symbol, and FIG. 11 (d) is a diagram illustrating an example in which the SBFD operation is performed only for symbols before the resource mapped to the unavailable symbol exists within the slot in which the unavailable symbol exists. The SBFD operation may or may not be performed on a symbol or terminal basis for the unavailable symbol and the symbol including the unavailable symbol.

[0325] [SBFD: Determine the SBFD application slot / symbol within the set SBFD time resource]

[0326] Through the above embodiments, the terminal can determine a slot / symbol for which an SBFD time resource is set. However, the terminal may not always be able to transmit and receive through an SBFD subband in the set slot / symbol. That is, some of the set slots / symbols may be interpreted as symbols for which an SBFD subband is not set, and the terminal may assume that some of the slots / symbols are slots / symbols for which an SBFD time resource is set, but there is no SBFD subband. The absence of an SBFD subband in a specific symbol / slot may include that the terminal has received an SBFD subband set for the symbol from the base station, but does not transmit an uplink signal in the SBFD subband (for example, if at least one symbol among channels such as PUSCH / PUCCH, for which transmission is indicated within the SBFD subband, overlaps with a specific symbol / slot, the PUSCH / PUCCH, etc., is not transmitted).

[0327] In a first method, the terminal can assume that symbols overlapping with specific symbols do not have SBFD subbands. That is, if a slot / symbol for which SBFD time resources are set includes the specific symbols, the symbols can be excluded.

[0328] A specific symbol may include at least one of a symbol for receiving SS / PBCH, a symbol for monitoring a Type0-PDCCH CSS set, and a symbol for receiving CSI-RS for tracking. In addition, the symbol may include symbols immediately preceding or immediately following the symbols.

[0329] In a second method, the terminal can assume that there is no SBFD subband in a slot where a specific symbol exists. That is, if the specific symbol is included in a slot for which SBFD time resources are set, the slot can be excluded. In this method, the terminal can determine whether an SBFD subband exists on a slot-by-slot basis. If an SBFD subband can exist on a symbol-by-symbol basis within a slot, the terminal may experience frequent TX-to-RX switching or RX-to-TX switching. This not only increases the complexity of the terminal but also requires a TX-to-RX switching gap or an RX-to-TX switching gap.

[0330] As a third method, the terminal can assume that there are no SBFD subbands in the symbols following a specific symbol in a slot in which a specific symbol exists. That is, if the specific symbol is included in a slot in which SBFD time resources are set, the symbol and the symbols following the symbol can be excluded.

[0331] In a fourth method, the terminal can assume that there are no SBFD subbands in the symbols preceding the specific symbol in a slot in which the specific symbol exists. That is, if the specific symbol is included in a slot in which SBFD time resources are set, the symbol and the symbols preceding the symbol can be excluded.

[0332] The third and fourth methods can reduce the complexity of the terminal or the TX-to-RX switching gap or the RX-to-TX switching gap by allowing only one TX-to-RX switching or RX-to-TX switching to the terminal.

[0333] [SBFD: Subcarrier spacing within SBFD time resources]

[0334] The subcarrier interval used for time resource allocation of the above SBFD system can be determined as follows.

[0335] First, the subcarrier spacing is the first of the initial DL BWP, and it can be assumed that the subcarrier spacing is the same as the subcarrier spacing of the initial DL BWP. Here, the initial DL BWP is the BWP from which the terminal acquires SIB scheduling information when initially accessing the cell. Therefore, all terminals within the cell can acquire the same subcarrier spacing.

[0336] Second, it can be assumed that the subcarrier spacing is the same as the subcarrier spacing of the initial UL BWP. Here, the terminal can receive the subcarrier spacing of the initial UL BWP in SIB1. The initial UL BWP is a BWP that can be used for PRACH (physical random access channel) transmission, msg3 PUSCH transmission, msg4 PDSCH HARQ-ACK transmission, etc. Here, msg3 and msg4 are well-known messages transmitted and received between the terminal and the base station for contention resolution in the random access procedure.

[0337] Third, the subcarrier spacing can be determined based on the smaller value between the subcarrier spacing of the initial DL BWP and the subcarrier spacing of the initial UL BWP. This means that the symbol corresponding to the smaller subcarrier spacing can completely include the symbol corresponding to the larger subcarrier spacing in the time domain. However, the symbol corresponding to the larger subcarrier spacing cannot completely include the symbol corresponding to the smaller subcarrier spacing in the symbol time domain. Therefore, to solve this problem, the subcarrier spacing can be determined based on the smaller value between the subcarrier spacing of the initial DL BWP and the subcarrier spacing of the initial UL BWP.

[0338] Fourth, the subcarrier spacing can be separately set by the base station to the terminal. Here, the subcarrier spacing can be set to satisfy at least one of the following conditions 1, 2, and 3.

[0339] * Condition 1: The subcarrier interval set above can be determined as a value equal to or smaller than the smallest value among the subcarrier intervals that can be set for DL ​​BWP and the subcarrier intervals that can be set for UL BWP.

[0340] * Condition 2: The subcarrier interval set above can be determined as a value equal to or smaller than the smallest value among the subcarrier intervals that can be set in DL BWP.

[0341] * Condition 3: The subcarrier spacing set above can be determined as a value equal to or smaller than the smallest value among the subcarrier spacings that can be set in the UL BWP.

[0342] Under the above conditions, the subcarrier spacing that can be set in the UL BWP can be included in the IE (information element) of the upper layer signal, FrequencyInfoUL, FrequencyInfoUL-SIB, and the subcarrier spacing that can be set in the DL BWP can be included in the upper layer signal, FrequencyInfoDL, FrequencyInfoDL-SIB.

[0343] Fifth, the subcarrier spacing may be the same as the subcarrier spacing used in the TDD configuration. Here, the subcarrier spacing used in the TDD configuration is a value set by a higher layer signal (referenceSubcarrierSpacing).

[0344] Additionally, in the case of a cell-specific SBFD system, one cell may have more than one BWP, and each BWP may be configured with a different subcarrier spacing. In this case, when configuring SBFD time resources, the smallest value among the subcarrier spacings available in the valid cell may be used to avoid resource grid alignment issues.

[0345] [Fallback mode and upper layer settings]

[0346] A terminal supporting SBFD operation (SBFD-capable terminal or SBFD-aware terminal) can perform SBFD operation by receiving a higher layer signal related to SBFD operation from a base station. Here, the higher layer signal configured from the base station may be a configuration related to an SBFD subband (frequency position of the SBFD subband or symbol / slot position of the SBFD subband) and uplink transmission and downlink reception parameters considering the SBFD subband. Hereinafter, a higher layer configuration configured only for SBFD operation will be referred to as an SBFD configuration. For reference, a terminal supporting SBFD operation in the present disclosure may also support a TDD operation. Here, the TDD operation may be an operation of the terminal when the SBFD configuration is not configured.

[0347] A base station supporting SBFD operation can transmit SBFD configuration to a terminal supporting SBFD operation. Then, the terminal can transmit downlink in SBFD downlink subbands in SBFD symbols / slots and receive uplink in SBFD uplink subbands. However, a base station supporting SBFD operation may not be able to perform SBFD operation or may not require SBFD operation depending on the situation.

[0348] For example, if the base station's self-interference signal size exceeds a predetermined value, it may become difficult to receive uplink signals in the SBFD uplink subband. Therefore, in this case, SBFD operation cannot be maintained.

[0349] For example, a base station may have difficulty receiving uplink signals in the SBFD uplink subband due to interference signals from adjacent base stations (downlink signal transmissions from adjacent base stations acting as interference). Therefore, in this case, SBFD operation cannot be maintained.

[0350] For example, if a terminal requesting uplink transmission (or requesting uplink coverage enhancement) is no longer within the cell served by the base station, the terminal may no longer need uplink transmission via the SBFD uplink subband. In this case, SBFD operation may not be required.

[0351] If the SBFD operation cannot be performed in this way or the SBFD operation is not required, the base station can terminate the SBFD operation. The SBFD operation can be terminated.

[0352] Conversely, a base station that has terminated the SBFD operation may initiate the SBFD operation. This can correspond to the opposite situation where the SBFD operation was previously not performed or was not required.

[0353] FIG. 14 is a diagram showing the end and start of SBFD operation of a base station according to one embodiment of the present disclosure.

[0354] Referring to FIG. 14, termination of SBFD operation of a base station may include at least one of the following two things.

[0355] As a first method, referring to FIG. 14(a), the base station can change between SBFD mode and TDD mode. Here, the SBFD mode can refer to an operation in which the base station is allowed to receive uplink in the SBFD uplink subband and transmit downlink in the SBFD downlink subband based on the SBFD setting. In addition, the SBFD mode can refer to an operation in which the terminal is allowed to transmit uplink in the SBFD uplink subband and receive downlink in the SBFD downlink subband based on the SBFD setting. Here, the TDD mode can refer to an operation of the base station and the terminal when the SBFD setting is not present. That is, in the TDD mode, the base station and the terminal can transmit and receive downlink signals in DL symbols, and receive and transmit uplink signals in UL symbols. Here, changing from SBFD mode to TDD mode can be called a fallback.

[0356] As a second method, referring to FIG. 14(b), the base station can allow / disallow operation of the SBFD sub-band on a per-SBFD sub-band basis. For example, the base station can change from a mode that allows uplink transmission of a terminal in the SBFD uplink sub-band (SBFD mode-uplink sub-band On mode) to a mode that disallows uplink transmission of a terminal in the SBFD uplink sub-band (SBFD mode-uplink sub-band Off mode). In the 'SBFD-mode-uplink sub-band On mode', the base station can indicate an operation that allows receiving uplink in the SBFD uplink sub-band and transmitting downlink in the SBFD downlink sub-band based on the SBFD setting. In addition, the SBFD mode can indicate an operation that allows a terminal to transmit uplink in the SBFD uplink sub-band and receive downlink in the SBFD downlink sub-band based on the SBFD setting. That is, in the first method, the SBFD mode may be the same as 'SBFD-mode-uplink sub-band On mode'. In 'SBFD-mode-uplink sub-band Off mode', the base station may indicate an operation in which, based on the SBFD configuration, the base station is allowed to transmit downlink in the SBFD downlink sub-band, but is not allowed to transmit uplink in the SBFD uplink sub-band. In addition, 'SBFD-mode-uplink sub-band Off mode' may indicate an operation in which, based on the SBFD configuration, the terminal is allowed to receive downlink in the SBFD downlink sub-band, but is not allowed to transmit uplink in the SBFD uplink sub-band. Therefore, the terminal may not transmit channels / signals instructed to be transmitted in the SBFD uplink sub-band.

[0357] Although the second method described above has been described with respect to an example of allowing / disallowing uplink transmission of a terminal in an SBFD uplink subband, it can be extended to an example of allowing / disallowing downlink reception of a terminal in an SBFD downlink subband. If one or more subbands are configured as SBFD downlink subbands for a terminal, the terminal can allow / disallow downlink reception for all downlink subbands simultaneously. In addition, if one or more subbands are configured as SBFD downlink subbands for a terminal, the terminal can allow / disallow downlink reception for each downlink subband simultaneously.

[0358] In the following description, unless otherwise specified, a method for changing between SBFD mode and TDD mode according to the first method, and hereinafter, a method for changing modes, will be disclosed. Unless otherwise specified, a fallback operation means a change from SBFD mode to TDD mode. A non-fallback operation means a change from TDD mode to SBFD mode. When the present disclosure is applied to the second method, the SBFD mode can be interpreted as a case where uplink transmission is permitted in an SBFD uplink subband, and the TDD mode can be interpreted as a case where uplink transmission is not permitted in an SBFD uplink subband. When the present disclosure is applied to the second method, the SBFD mode can be interpreted as a case where transmission and reception are permitted in an SBFD symbol (a symbol in which an SBFD uplink subband or an SBFD downlink subband is configured), and the TDD mode can be interpreted as a case where transmission and reception are not permitted in an SBFD symbol.

[0359] Unless otherwise specified in the following description, the mode is applied to all symbols of the cell. However, the embodiments of the present disclosure may be applied only to a specific symbol set. The symbol set may include symbols set by the base station, symbols to which the channel / signal set by the base station is mapped, or symbols excluding symbols to which the channel / signal set by the base station is mapped. Here, the channel / signal set by the base station may include one of SSB (synchronization signal block), a symbol corresponding to Type-0 search space, PRACH, TRS (a signal set for tracking purposes among CSI-RS as a tracking reference signal), etc.

[0360] FIG. 15 is a diagram illustrating an operation for setting a change in the TDD mode and SBFD mode of a base station according to one embodiment of the present disclosure.

[0361] Referring to FIG. 15, according to the present disclosure, a terminal can receive a higher layer signal for TDD mode operation and a higher layer signal for SBFD mode operation from a base station. For a mode change method, the base station can set a higher layer signal to the terminal in at least one of the following ways.

[0362] - In a first method, different modes may be set for each BWP. That is, a higher layer signal for TDD mode operation may be set for the first BWP, and a higher layer signal for SBFD mode operation may be set for the second BWP. That is, the second BWP may include an SBFD configuration. More specifically, the terminal may receive at least two BWPs from the base station for mode change. The first BWP may be set with higher layer signals for TDD mode operation (PDSCH-config for PDSCH reception in a downlink symbol or PDCCH-config for PDCCH reception, PUSCH-config for PUSCH reception in an uplink symbol or PUCCH-config for PUCCH reception). The second BWP may be configured with upper layer signals for SBFD mode operation (PDSCH-config for PDSCH reception in a downlink symbol or SBFD downlink subband or PDCCH-config for PDCCH reception, PUSCH-config for PUSCH reception in an uplink symbol or SBFD uplink subband or PUCCH-config for PUCCH reception).

[0363] - In a second method, upper layer signals for TDD mode (PDSCH-config for PDSCH reception in a downlink symbol or PDCCH-config for PDCCH reception, PUSCH-config for PUSCH reception in an uplink symbol or PUCCH-config for PUCCH reception) may be configured within one BWP. Upper layer configurations for SBFD mode (PDSCH-config_SBFD for PDSCH reception in a downlink symbol or SBFD downlink subband or PDCCH-config_SBFD for PDCCH reception, PUSCH-config_SBFD for PUSCH reception in an uplink symbol or SBFD uplink subband or PUCCH-config_SBFD for PUCCH reception) may be configured.

[0364] A terminal can have one mode activated within a BWP. If one of the activated modes is a TDD mode, higher layer signals for the TDD mode (PDSCH-config for PDSCH reception or PDCCH-config for PDCCH reception in a downlink symbol, PUSCH-config for PUSCH reception or PUCCH-config for PUCCH reception in an uplink symbol) can be activated. That is, the terminal can transmit and receive signals based on higher layer signals for the TDD mode within the BWP. If one of the activated modes is an SBFD mode, higher layer signals for the SBFD mode (PDSCH-config for PDSCH reception or PDCCH-config for PDCCH reception in a downlink symbol or an SBFD downlink subband, PUSCH-config for PUSCH reception or PUCCH-config for PUCCH reception in an uplink symbol or an SBFD uplink subband) can be activated. That is, the terminal can transmit and receive signals based on upper layer signals for SBFD mode within the BWP.

[0365] - In a third method, a configuration for SBFD mode and a configuration for TDD configuration may be included in one upper layer signal within one BWP. More specifically, frequency hopping parameters may be configured in a PUSCH transmission upper layer signal (PUSCH-config) within one BWP. Up to four frequency hopping parameters may be configured. The frequency hopping parameters may be parameters for the TDD mode and parameters for the SBFD mode. Here, the parameter for the TDD mode may indicate a frequency hopping value of an uplink symbol (an uplink symbol for which a downlink SBFD subband is not configured), and the parameter for the SBFD mode may indicate a frequency hopping value of an SBFD uplink subband and a frequency hopping value of an uplink symbol (an uplink symbol for which a downlink SBFD subband is not configured). The frequency hopping parameter is one example, and other uplink transmission power values, uplink resources, etc. may be configured for each of the TDD mode and the SBFD mode.

[0366] A terminal can activate one mode within a BWP. The terminal can activate upper layer parameters corresponding to one mode. If the activated mode is TDD mode, parameters for TDD mode (e.g., frequency hopping parameters for TDD mode) can be activated. If the activated mode is SBFD mode, parameters for SBFD mode (e.g., frequency hopping parameters for SBFD mode) can be activated.

[0367] - In the fourth method, settings related to the TDD mode (PDSCH-config for PDSCH reception in a downlink symbol or PDCCH-config for PDCCH reception, PUSCH-config for PUSCH reception in an uplink symbol or PUCCH-config for PUCCH reception) can be set within one BWP. And, settings related to the SBFD mode (PDSCH-config for PDSCH reception in a downlink symbol or SBFD downlink subband or PDCCH-config for PDCCH reception, PUSCH-config for PUSCH reception in an uplink symbol or SBFD uplink subband or PUCCH-config for PUCCH reception) can be set within a separate setting. A terminal can activate one mode within one BWP. If the activated mode is the TDD mode, the separate setting can be ignored. That is, only settings related to the TDD mode can be activated within the BWP. If the activated mode is SBFD mode, the above separate settings may be activated. Here, parameters set in SBFD mode may take precedence over the values ​​of parameters set in the settings related to TDD mode. In other words, the settings in SBFD mode may have a higher priority.

[0368] A terminal can only have one mode activated at a time. That is, either TDD mode or SBFD mode can be activated at a time. The present disclosure relates to a method for determining the activated mode of a terminal.

[0369] When the mode is set for each BWP as in the first method, the terminal can change the mode by changing the BWP. More specifically, the terminal can receive a DCI format for scheduling a PDSCH or a DCI format for scheduling a PUSCH. The DCI format can include a BWP indicator field. The terminal can be instructed on a BWP for receiving or transmitting the scheduled PDSCH or PUSCH through the BWP indicator field. If the BWP is the first BWP, the terminal can determine that it is in TDD mode. That is, in the first BWP, the terminal may not perform operations related to SBFD. If the BWP is the second BWP, the terminal can determine that it is in SBFD mode. That is, in the second BWP, the terminal can perform operations related to SBFD according to the SBFD setting.

[0370] The following description discloses a method in which one mode is indicated when the TDD mode and the SBFD mode are set to the terminal in the first method, the second method, the third method, and the fourth method.

[0371] [How to receive a mode change indicator]

[0372] A terminal can receive an instruction indicating a mode change via DCI. The DCI can be one of the following:

[0373] - Group common DCI (DCI format 2_X, CRC is scrambled with a value defined for each DCI format)

[0374] - UE-specific DCI (DCI format 0_X, 1_X, CRC scrambled with C-RNTI)

[0375] - System information carrying DCI (DCI format 1_0, CRC is scrambled with SI-RNTI or RNTI value determined commonly by the cell)

[0376] In the above DCI, the mode change indicator can be indicated as follows.

[0377] - (Explicit method, 1 bit) The DCI may include a 1-bit indicator as an explicit indication method. The 1-bit indicator may indicate whether the indicated mode is the TDD mode or the SBFD mode. The 1-bit indicator may indicate whether the indicated mode is the same as the currently used mode or a changed mode. For example, '0' of 1 bit may indicate maintaining the currently used mode, and '1' may indicate a mode change. For example, if the currently used mode is the SBFD mode, '1' may indicate a change to the TDD mode. For example, if the currently used mode is the TDD mode, '1' may indicate a change to the SBFD mode.

[0378] - (Explicit method, N bits) In an explicit method, the DCI may include an indicator of N bits. The indicator of N bits may indicate the mode to be indicated and additional information. For example, the additional information may include at least one of the following:

[0379] - The mode indicated by the first additional information may indicate the point in time at which the start is applied (starting time). The indicated mode may be activated after the start application point.

[0380] - The mode indicated by the second additional information may indicate the point in time at which the termination is applied (ending time, ending time). The indicated mode may be terminated after the ending time. For example, if the currently activated mode is SBFD mode and the indicated mode is TDD mode, TDD mode may be applied for a certain time period (from the start time to the end time), but SBFD mode may be activated again after the ending time. Instead of the ending time, the duration of the indicated mode may be set. In other words, the ending time may be derived from the starting time and the duration.

[0381] - As a third additional information, multiple mode patterns can be indicated within the start and end points. For example, some time intervals (e.g., a symbol, a set of symbols, a slot or a set of slots, a frame, a set of frames, a period of a TDD pattern, a set of periods of a TDD pattern, an SSB period, a set of SSB periods) can be divided into the start and end points, and the modes corresponding to each of the intervals can be indicated.

[0382] - Additionally, in a situation where multiple carriers / cells are combined (carrier aggregation), first additional information to third additional information may be included for each cell.

[0383] - Additional information 1 to 3 are described in more detail below.

[0384] - The explicit method can newly add a field for the 1-bit to N-bit indication to the DCI format, or reinterpret and use existing fields. The existing field of the UE-specific DCI can be represented by at least one or a combination of the FDRA field, the MCS field, the RV field, and the NDI field. For example, in the case of the UE-specific DCI, if the FDRA (frequency domain resource assignment) field indicates an invalid value and the MCS and RV are specific values ​​(for example, both '1'), it can be indicated in the NDI (new data indication) field. That is, 1 bit can be indicated through the NDI field. And the DCI may not schedule the PDSCH or PUSCH.

[0385] - (Implicit method) In the implicit method, if the fields of the DCI format indicate a specific combination of values, the UE can determine that the DCI indicates a mode change. The existing fields of the UE-specific DCI can be represented by at least one or a combination of the FDRA field, the RV field, and the NDI field. For example, in the case of the UE-specific DCI, if the FDRA (frequency domain resource assignment) field indicates an invalid value and the MCS and RV are specific values ​​(e.g., both '1'), the UE can determine that a mode change is indicated. Accordingly, if the current mode is the TDD mode, it can be changed to the SBFD mode, or if the current mode is the SBFD mode, it can be changed to the TDD mode.

[0386] When a mode change is indicated implicitly, additional information in the mode change indicator, such as the start and end times, can be set as upper layer signals.

[0387] The terminal can receive an indicator indicating a mode change via MAC-CE. Here, MAC-CE can be received as follows.

[0388] - MAC-CE information transmitted through PDSCH scheduled in UE-specific DCI (where UE-specific DCI and PDSCH are scrambled with the terminal's C-RNTI)

[0389] - MAC-CE information transmitted through PDSCH scheduled in Group common DCI (where Group common DCI and PDSCH are scrambled with Group common RNTI)

[0390] - MAC-CE information transmitted through PDSCH scheduled in System information carrying DCI (here, System information carrying DCI and PDSCH are scrambled with SI-RNTI or RNTI value determined in common by the cell)

[0391] [Start point of application of mode change directive]

[0392] FIG. 16 is a diagram illustrating an operation in which a terminal applies a mode change indicator as a starting point according to an embodiment of the present disclosure.

[0393] When a terminal receives an instruction indicating a mode change, it can determine a starting time for applying the received instruction. The starting time can be determined based on at least one of the following methods.

[0394] When a terminal receives an indicator through DCI, the indicated mode can be applied from the first second time interval after the first time interval from the symbol in which the DCI is received. Here, the first time interval can include at least one of X symbols, X slots, X frames, X TDD periods, X SSB periods, and X ms (milliseconds), and the second time interval can include at least one of Y symbols, Y slots, Y frames, Y TDD periods, Y SSB periods, and X ms (milliseconds). Here, the unit of the first time interval (symbol / slot / frame / TDD period / SSB period / absolute time (ms, millisecond)) and the unit of the second time interval (symbol / slot / frame / TDD period / SSB period / absolute time (ms, millisecond)) can be the same as or different from each other. Here, the value of X and the value of Y can be the same as or different from each other.

[0395] In one embodiment, a first time interval may be represented by X symbols, and a second time interval may be represented by Y=1 frames. According to this embodiment, a terminal may receive DCI and determine a received symbol. Here, the received symbol may be the last symbol (or the first symbol) of a PDCCH on which the DCI is transmitted. The terminal may activate the indicated mode in the frame starting for the first time after X symbols from the last symbol. That is, the currently activated mode may be activated up to the frame, and the indicated mode may be activated from the frame.

[0396] In one embodiment, a first time interval may be represented by X slots, and a second time interval may be represented by Y frames. For convenience of description, a set of frames that bundles Y consecutive frames may be called a super frame. Here, super frame 0 may be generated by bundling frame 0, frame 1, ..., frame Y-1. According to the present embodiment, a terminal may receive DCI and determine a received slot. The terminal may activate a mode indicated in a super frame that starts for the first time after X slots from the slot. That is, a currently activated mode may be activated up to the super frame, and the indicated mode may be activated from the super frame.

[0397] In one embodiment, a first time interval may be represented by X ms, and a second time interval may be represented by Y frames. For convenience of description, a set of frames that bundles Y consecutive frames may be called a super frame. Here, super frame 0 may be generated by bundling frame 0, frame 1, ..., frame Y-1. According to the present embodiment, a terminal may receive DCI and determine a received slot. The terminal may activate a mode indicated in a super frame that starts for the first time after X ms from the slot. That is, a currently activated mode may be activated before the super frame, and the indicated mode may be activated from the super frame.

[0398] When the terminal receives the indicator through MAC-CE, the indicated mode can be applied from the first second time interval after the first time interval from the symbol (last symbol or first symbol) or slot in which the PDSCH transmitting the MAC-CE is received. Here, the first time interval can include at least one of X symbols, X slots, X frames, X TDD periods, X SSB periods, X ms (milliseconds), and the second time interval can include at least one of Y symbols, Y slots, Y frames, Y TDD periods, Y SSB periods, X ms (milliseconds). Here, the unit of the first time interval (symbol / slot / frame / TDD period / SSB period / absolute time (ms, millisecond)) and the unit of the second time interval (symbol / slot / frame / TDD period / SSB period / absolute time (ms, millisecond)) can be the same as or different from each other. Here, the X and Y values ​​can be equal or different.

[0399] When the terminal receives the indicator through MAC-CE, the indicated mode may be applied from the first second time interval after the first time interval from the symbol (last symbol or first symbol) or slot that transmitted the PUCCH that transmits whether the PDSCH transmitting the MAC-CE was successfully received. Here, the first time interval may include at least one of X symbols, X slots, X frames, X TDD periods, X SSB periods, and X ms (milliseconds), and the second time interval may include at least one of Y symbols, Y slots, Y frames, Y TDD periods, Y SSB periods, and X ms (milliseconds). Here, the unit of the first time interval (symbol / slot / frame / TDD period / SSB period / absolute time (ms, millisecond)) and the unit of the second time interval (symbol / slot / frame / TDD period / SSB period / absolute time (ms, millisecond)) may be the same or different. Here, the X value and the Y value may be the same or different.

[0400] For reference, if the success or failure of reception of the PDSCH transmitting the MAC-CE is not transmitted on the PUCCH, the PUCCH for reference can be determined based on the PRI (PUCCH resource indicator) field indicated in the DCI scheduling the PDSCH transmitting the MAC-CE.

[0401] If the indicated information does not contain the first additional information, the indicated mode may be applied at the determined start time. If the indicated information contains the first additional information, the start time may be determined based on the determined start time and the first additional information.

[0402] More specifically, the terminal can start the indicated information at a point in time later than the determined start time as indicated in the first additional information. The first additional information may be expressed in units of a third time interval (symbol / slot / frame / TDD period / SSB period / absolute time (ms, millisecond)). For example, let's say the determined start time is frame f. The terminal can activate the indicated mode at a point in time later than the third time interval unit (symbol / slot / frame / TDD period / SSB period / absolute time (ms, millisecond)) indicated in the first additional information from frame f.

[0403] For example, let's say the third time interval unit is a slot. And let's assume that three slots are indicated by the first additional information. In this case, the terminal can activate the indicated mode in slot 3 (the fourth slot) of frame f.

[0404] For example, let's say the third time interval unit is a frame. And let's assume that three frames are indicated by the first additional information. In this case, the terminal can activate the indicated mode in frame f+3.

[0405] Alternatively, the terminal may activate the mode indicated in the second time interval unit (symbol / slot / frame / TDD period / SSB period / absolute time (ms, millisecond)) starting earliest from the third time interval unit (symbol / slot / frame / TDD period / SSB period / absolute time (ms, millisecond)) indicated in the first additional information from frame f.

[0406] [Whether other instructions are allowed in the Mode Change Directive]

[0407] A terminal may receive multiple indicators for the same time point mode. Referring to FIG. 16, at PDCCH reception opportunities 1600, 1601, 1602, 1603, 1604, 1605, and 1606, the terminal may receive DCI including a mode indicator. The mode indicators included in the DCI may indicate the mode at the same starting time point. Here, multiple indicators indicating the mode at a single time point may indicate the mode according to one of the following methods.

[0408] In the first method, the terminal can expect that multiple indicators indicating a mode at a given point in time will always indicate the same mode. That is, when the terminal receives multiple indicators indicating a mode at a given point in time, the modes indicated by the indicators can all be identical. Accordingly, the terminal's operation can be as follows.

[0409] A terminal can determine a PDCCH reception opportunity of multiple indicators indicating a mode at a given point in time. In FIG. 16, the terminal can determine PDCCH reception opportunities 1600, 1601, 1602, 1603, 1604, 1605, and 1606. If the terminal receives an indicator in at least one of the PDCCH reception opportunities, the terminal can determine the mode at the given point in time based on the indicator. In addition, the terminal may not monitor other PDCCH reception opportunities. For example, if the terminal receives a mode change indicator in PDCCH reception opportunity 1600, the terminal may not receive PDCCH reception opportunities 1601, 1602, 1603, 1604, 1605, and 1606.

[0410] In a second method, the terminal can determine the mode based on the most recently received indicator among multiple indicators indicating the mode at a single point in time. That is, if the terminal receives one indicator during one PDCCH reception opportunity and another indicator during another PDCCH reception opportunity, the two received indicators may indicate different modes, and the terminal can determine the mode based on the information in the most recently received indicator.

[0411] Note that if a terminal does not receive any indicators for a given point in time, the terminal's behavior may be delayed by at least one next week.

[0412] In a first method, the terminal can operate in a default mode. The default mode may be TDD mode. The default mode may be SBFD mode. The default mode may be a mode set by the base station. For example, the base station may set one of the TDD mode and SBFD mode as the default mode.

[0413] As a second method, the terminal can maintain the most recently used mode without changing it. For example, assume that the terminal has received the mode for the most recent time interval (symbol / slot / frame / TDD cycle / SSB cycle / absolute time (ms, milliseconds)) through another received indicator. The terminal can continue to maintain this mode and determine the mode for time intervals without a corresponding indicator.

[0414] The base station can set one of the first method and the second method to the terminal.

[0415] [End point of application of mode change directive]

[0416] FIG. 17 is a diagram illustrating an operation in which a terminal applies a mode change indicator as an end point according to an embodiment of the present disclosure.

[0417] When a terminal receives an instruction indicating a mode change, it can determine an ending time based on the received instruction. The ending time can be determined based on at least one of the following methods.

[0418] In the first method, when a terminal receives an indicator indicating a mode change, the changed mode can be maintained continuously from the start point. That is, the terminal can continue to maintain the changed mode according to the mode change indicator unless another mode change is indicated.

[0419] In a second method, when the terminal receives an indication indicating a mode change, the terminal may use the indicated mode for Z fourth time intervals according to the second additional information, and may change to another mode after the end time. Here, the other mode may be the mode used before the change (original mode) or the default mode set by the base station to the terminal. Here, the fourth time interval may have at least one time unit among symbol / slot / frame / TDD period / SSB period / absolute time (ms, millisecond). According to one embodiment of the present disclosure, the fourth time interval may be the same as the second time interval.

[0420] [Upper layer channel / signal suspend / release decision upon receiving mode change indicator]

[0421] When a mode is changed, the terminal must determine whether to use the signal set by the upper layer prior to the change in the new mode. This section discloses embodiments related to this. For convenience, the description is based on a change from SBFD mode to TDD mode, but the same method can also be applied to a change from TDD mode to SBFD mode.

[0422] Fig. 18 is a diagram illustrating a terminal according to an embodiment of the present disclosure in which a change from SBFD mode to TDD mode is instructed according to a mode change indicator. According to Fig. 18, the terminal can change from SBFD mode to TDD mode after a starting time, and can change from TDD mode to SBFD mode at an ending time.

[0423] Referring to FIG. 18, when a terminal receives an indicator indicating a mode change, the terminal may change from SBFD mode before the start time to TDD mode after the start time. Furthermore, the changed TDD mode may be maintained continuously unless the terminal receives an additional indicator indicating a mode change.

[0424] In one example, if a terminal receives an indicator indicating a mode change, the terminal may continue to maintain the changed mode after the start time. That is, the terminal may continue to maintain the changed mode according to the mode change indicator unless another mode change is indicated. Referring to FIG. 18, if the terminal receives an indicator indicating a mode change, the terminal may change from SBFD mode before the start time to TDD mode after the start time. Furthermore, the changed TDD mode may be continuously maintained unless the terminal receives an additional indicator indicating a mode change.

[0425] In one example, when a terminal receives an indication indicating a Mode change, the terminal may use the indicated Mode for Z fifth time intervals according to the second additional information, and may change to another Mode after the end time. Here, the other Mode may be the Mode used before the change (original Mode) or the default Mode set by the base station to the terminal. Here, the fifth time interval may have at least one time unit among symbol / slot / frame / TDD period / SSB period / absolute time (ms, millisecond).

[0426] When the terminal operates in SBFD mode, transmission and reception of periodic channels / signals can be configured through a higher layer configuration signal. For example, SPS PDSCH configuration, CSI-RS configuration, PDCCH configuration, etc. can be configured and activated as downlink configuration of the higher layer. CG-PUSCH configuration, SRS configuration, PUCCH configuration (CSI reporting and HARQ-ACK transmission of SPS PDSCH), PRACH, etc. can be configured and activated as uplink configuration of the higher layer. When operating in SBFD mode, according to the above configuration, SPS PDSCH, CSI-RS, PDCCH can be received in a downlink symbol or SBFD downlink subband, and CG-PUSCH, SRS, PUCCH, PRACH, etc. can be transmitted in an uplink symbol or an uplink SBFD uplink subband.

[0427] When the terminal is instructed to change from SBFD mode to TDD mode, the terminal may release or suspend some or all of the above settings, according to the following embodiments.

[0428] In the first method, CG-PUSCH settings, SRS settings, PUCCH settings, PRACH settings, etc. transmitted according to the uplink settings of the upper layer in the SBFD uplink subband and SPS PDSCH settings, CSI-RS settings, PDCCH settings, etc. received according to the downlink settings of the upper layer in the SBFD subband can be released or suspended. In other words, all channels / signals configured by the upper layer in the SBFD mode can be released or suspended.

[0429] In the second method, the CG-PUSCH configuration, SRS configuration, PUCCH configuration, and PRACH configuration transmitted according to the uplink configuration of the upper layer in the SBFD uplink subband can be released or suspended. However, the SPS PDSCH configuration, CSI-RS configuration, PDCCH configuration, etc. received according to the downlink configuration of the upper layer in the SBFD subband can be continuously activated without being released or suspended. For reference, the terminal may have CG-PUSCH, SRS, PUCCH, and PRACH configured for transmission only in the SBFD uplink subband from the base station, and the channels / signals can be released or suspended. Here, the channels / signals configured for transmission only in the SBFD uplink subband cannot be transmitted in the TDD mode without the SBFD subband.

[0430] In a third method, SPS PDSCH settings, CSI-RS settings, and PDCCH settings received in the SBFD downlink subband according to the downlink settings of the upper layer can be released or suspended. However, CG-PUSCH settings, SRS settings, PUCCH settings, PRACH settings, etc. received in the SBFD subband according to the uplink settings of the upper layer may not be released or suspended and may continue to be activated. For reference, the terminal may have SPS PDSCH, CSI-RS, and PDCCH that are set to be received only in the SBFD downlink subband from the base station, and the above channels / signals may be released or suspended.

[0431] In the fourth method, in the TDD mode, the CG-PUSCH configuration, SRS configuration, PUCCH configuration, and PRACH configuration can be released or suspended if all occasions are invalid. In the TDD mode, there is no SBFD uplink subband, and uplink transmission is possible in an uplink symbol (or including a flexible symbol), and uplink transmission may not be possible in a downlink symbol. If all the CG PUSCH occasions determined according to the CG-PUSCH configuration overlap with a downlink symbol, the UE has no occasions that can be transmitted among the CG-PUSCH occasions determined according to the CG-PUSCH configuration, and thus the CG-PUSCH configuration can be released or suspended.

[0432] In the fifth method, in TDD mode, the SPS PDSCH configuration, CSI-RS configuration, and PDCCH configuration can be released or suspended if all occasions are invalid. In TDD mode, downlink reception is possible in a downlink symbol (or including a flexible symbol), and downlink reception may not be possible in an uplink symbol. If all the occasions of the SPS PDSCH determined according to the SPS PDSCH configuration overlap with the uplink symbol, the UE cannot receive any of the occasions of the SPS PDSCH determined according to the SPS PDSCH configuration, and thus the SPS PDSCH configuration can be released or suspended.

[0433] In a sixth method, if at least one of the occasions according to the CG-PUSCH configuration, SRS configuration, PUCCH configuration, and PRACH configuration in the TDD mode is invalid, the configuration may be released or suspended. In the TDD mode, there is no SBFD uplink subband, uplink transmission may be possible in an uplink symbol (or including a flexible symbol), and uplink transmission may not be possible in a downlink symbol. If at least one of the occasions of the CG PUSCH determined according to the CG-PUSCH configuration overlaps with a downlink symbol, the CG-PUSCH configuration may be released or suspended.

[0434] In the seventh method, if at least one of the occasions according to the SPS PDSCH configuration, CSI-RS configuration, and PDCCH configuration in the TDD mode is invalid, the configuration may be released or suspended. In the TDD mode, downlink reception may be possible in the downlink symbol (or including the flexible symbol), and downlink reception may not be possible in the uplink symbol. If at least one of the occasions of the SPS PDSCH determined according to the SPS PDSCH configuration overlaps with an uplink symbol, the SPS PUSCH configuration may be released or suspended.

[0435] In the eighth method, an available mode can be set in the upper layer configuration. For example, in the configuration of CG-PUSCH, a valid mode for the CG-PUSCH can be set. One of usable only in SBFD mode, usable only in TDD mode, or usable in both SBFD mode and TDD mode can be set. If usable only in SBFD mode, the UE transmits the CG PUSCH with the setting activated in SBFD mode, but can release or suspend the CG PUSCH when the mode is changed to TDD mode. If it is set to be usable in both SBFD mode and TDD mode, the setting is activated in SBFD mode to transmit the CG PUSCH, and even when the mode is changed to TDD, the CG PUSCH can continue to be activated without being released or suspended. In other words, the CG PUSCH can continue to be transmitted even in TDD mode.

[0436] In the previous methods, settings are expressed as being released or suspended when the mode changes. Here, the release of settings when the mode changes means the following.

[0437] - When changing from SBFD mode to TDD mode, if the channel / signal set in SBFD mode is released, the channel / signal according to the above setting may not be transmitted or received in TDD mode. In addition, even if the mode is changed back from TDD mode to SBFD mode, since the above-set channel / signal has already been released, it may not be transmitted or received in SBFD mode either.

[0438] - When changing from SBFD mode to TDD mode, if the channel / signal set in SBFD mode is suspended, the channel / signal according to the above setting may not be transmitted or received in TDD mode. However, when changing from TDD mode to SBFD mode again, the suspended set channel / signal is reactivated and can be transmitted or received in SBFD mode as well. In other words, in case of suspension, it continues to be valid in the same mode, and may be invalid in other modes.

[0439] FIG. 19 is a diagram showing the operation of a base station and a terminal when the base station and the terminal transmit and receive a mode change indicator according to one embodiment of the present disclosure.

[0440] Referring to FIG. 19(a), when a terminal is operating in mode 1 (e.g., SBFD mode), a base station may transmit a mode change indicator to the terminal. The mode change indicator may indicate a change from mode 1 to mode 2 (e.g., TDD mode). In addition, the mode change indicator may indicate a time t1, which is a start time of the indicated mode 2, through first additional information. If the mode change indicator does not include the first additional information, the terminal may determine a time t1, which is a start time of the indicated mode 2, according to a previously determined rule. The terminal may communicate with the base station using mode 2 after time t1. When the terminal is operating in mode 2, the base station may transmit a mode change indicator to the terminal. The mode change indicator may indicate a change from mode 2 to mode 1.

[0441] When the terminal is operating in mode 1 at time 1, the terminal may suspend the activated upper layer channel and signal that it was using. The upper layer channel and signal may be determined by one of the preceding embodiments. When the terminal is operating in mode 2 after time 1, the terminal may not transmit or receive the suspended upper layer channel and signal. When the terminal changes back to mode 1 after time 2, the terminal may resume the suspended upper layer channel and signal at time t1.

[0442] Referring to FIG. 19(b), when a terminal is operating in mode 1 (e.g., SBFD mode), a base station may transmit a mode change indicator to the terminal. The mode change indicator may simultaneously indicate a change from mode 1 to mode 2 (e.g., TDD mode) and a change from mode 2 to mode 1. For example, the mode change indicator may include first additional information and second additional information. The mode change indicator may indicate to the terminal, through the first additional information, time t1, which is a time point at which the indicated mode 2 starts. If the mode change indicator does not include the first additional information, the terminal may determine time t1, which is a time point at which the indicated mode 2 starts, according to a previously determined rule. The terminal may be indicated, through the second additional information, time t2, which is a time point at which the indicated mode 2 ends. In the absence of the second additional information, the terminal can determine time t2, which is the point in time at which the above-described mode 2 ends, according to the previously determined rules.

[0443] When the terminal is operating in mode 1 at time 1, the terminal may suspend the activated upper layer channel and signal that it was using. The upper layer channel and signal may be determined by one of the preceding embodiments. When the terminal is operating in mode 2 after time 1, the terminal may not transmit or receive the suspended upper layer channel and signal. When the terminal changes back to mode 1 after time 2, the terminal may resume the suspended upper layer channel and signal at time t1.

[0444] [UE-initiate Mode Switch]

[0445] A terminal operating in the SBFD Mode of a base station may receive inter-terminal interference from adjacent terminals. If the inter-terminal interference received by a terminal operating in the SBFD Mode of the base station exceeds a certain level, the terminal can receive downlink signals from the base station without issue. Therefore, the terminal may request the base station to terminate the SBFD Mode (use TDD mode instead of SBFD mode).

[0446] As another example, a terminal operating in SBFD Mode of a base station can be either Half-duplex or Full-duplex. That is, since the base station operates in SBFD Mode, the base station can simultaneously perform uplink reception from a terminal and downlink transmission to the terminal at the same time. However, in the case of a Half-duplex terminal, the terminal can perform only one of uplink transmission or downlink reception at a time, whereas in the case of a Full-duplex terminal, the terminal can perform both uplink transmission and downlink reception at the same time. In the case of a Full-duplex terminal, the terminal's uplink transmission may interfere with the terminal's downlink reception. Therefore, a Full-duplex terminal can request the base station to change its mode to Half-duplex if the interference is significant. In addition, a Full-duplex terminal can request the base station to operate in TDD Mode instead of SBFD Mode if the interference from an adjacent terminal is significant.

[0447] A method for a terminal to transmit the above request is disclosed.

[0448] The terminal may receive uplink channel / signal resources from the base station for requesting the above mode change. The uplink channel / signal may include at least one of the following:

[0449] - PUCCH resources for scheduling request (SR) transmission

[0450] - PRACH resources for PRACH transmission

[0451] - PUSCH resources for CG PUSCH transmission

[0452] Here, the terminal can transmit uplink using PUCCH resources for SR transmission and PRACH resources for PRACH transmission to request a mode change. If the base station receives the PUCCH and PRACH configured above, the base station can determine that the terminal is requesting a mode change.

[0453] Here, the terminal can multiplex and transmit UCI including an indicator requesting the mode change to the CG PUSCH. The indicator requesting the mode change may be 1 bit. If it is 1 bit, it may indicate whether or not the mode change is requested ('0' means not requested, '1' means requested). The indicator requesting the mode change may be N bits (N>1). Here, the N bits may be a value set between the base station and the terminal (or a value set by a higher layer). The N bits may include at least one of the following information: a start time and an end time desired by the terminal, UE-UE interference measured by the terminal, an unusable transmission beam (transmission TCI, QCL) or reception beam (reception TCI, QCL) measured by the terminal, along with the mode change request. When the information is multiplexed into the CG PUSCH, it may be multiplexed in the same manner as HARQ-ACK information. When the above information is multiplexed with HARQ-ACK information into a CG PUSCH, the above information and HARQ-ACK information can be multiplexed in the same manner as HARQ-ACK by joint coding (performing polar coding by grouping them into the same codeword).

[0454] Additionally, the base station may request the terminal for information on mode change (or the above N bits). This may be transmitted through at least one of the following channels: PUSCH or PUCCH. If the base station includes information on mode change in the DCI (DCI format 1_0, 1_1, 1_2, 1_3) that schedules the PDSCH, the terminal may transmit the information through the PUCCH. If the base station includes information on mode change in the DCI (DCI format 0_0, 0_1, 0_2, 0_3) that schedules the PUSCH, the terminal may transmit the information through the PUSCH.

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

[0456] Referring to FIG. 20, the terminal may include a transceiver, which refers to a terminal receiving unit (2000) and a terminal transmitting unit (2010), a memory (not shown), and a terminal processing unit (2005, or a terminal control unit or processor). Depending on the communication method of the terminal described above, the transceiver units (2000, 2010), the memory, and the terminal processing unit (2005) of the terminal may operate. The terminal processing unit (2005, or processor) may control the operation of the terminal according to each of the above-described embodiments as well as a combination of at least one embodiment. However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more or fewer components than the components described above. In addition, the transceiver, the memory, and the processor may be implemented in the form of a single chip.

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

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

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

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

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

[0462] Referring to FIG. 21, the base station may include a transceiver, which refers to a base station receiver (2100) and a base station transmitter (2110), a memory (not shown), and a base station processor (2105, or base station control unit or processor). According to the communication method of the base station described above, the transceiver (2100, 2110), the memory, and the base station processor (2105) of the base station may operate. The base station processor (1505, or processor) may control the operation of the base station according to each of the above-described embodiments as well as a combination of at least one embodiment. However, the components of the base station are not limited to the above-described examples. For example, the base station may include more or fewer components than the above-described components. In addition, the transceiver, the memory, and the processor may be implemented in the form of a single chip.

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

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

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

[0466] The processor can control a series of processes to enable the base station to operate according to the embodiments of the present disclosure described above. For example, the processor can configure two layers of DCIs containing allocation information for multiple PDSCHs and control each component of the base station to transmit them. There may be multiple processors, and the processors can perform component control operations of the base station by executing programs stored in memory.

[0467] The methods according to the 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.

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

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

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

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

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

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

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

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

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

Claims

1. A method performed by a terminal (user equipment) in a wireless communication system, A step of receiving, from a base station, first configuration information for a first operation mode and second configuration information for a second operation mode for one BWP (bandwidth part) through RRC (radio resource control) signaling; A step of activating the first operation mode for the one BWP based on the first setting information; A step of receiving, from the base station, a first DCI (downlink control information) including a first indicator indicating a change in an operation mode; A step of identifying whether to change the operation mode from the first operation mode to the second operation mode based on the first indicator; and A method comprising the step of activating the first operation mode or the second operation mode based on the identification.

2. In claim 1, The above first operation mode is either SBFD (subband full duplex) mode or TDD (time-domain duplex) mode, The second operation mode is one of the SBFD mode or the TDD mode, A method wherein the second operation mode is a different operation mode from the first operation mode.

3. In claim 1, the step of identifying whether to change the operation mode from the first operation mode to the second operation mode is as follows: a step of identifying a change of the operation mode from the first operation mode to the second operation mode, when the first instruction indicates the second operation mode; and A method comprising: a step of identifying maintenance of the first operating mode when the first directive indicates a first operating mode.

4. In claim 3, the method comprises: Further comprising the step of receiving a second DCI including a second indicator for changing the operation mode from the base station, When the first instruction indicates the second operation mode and the second instruction indicates the first operation mode, Before the second operation mode is activated based on the first directive, the channel and signal for the higher layer established while the first operation mode is activated are released or suspended, A method wherein channels and signals for the upper layer that were released or suspended are re-activated before the first mode is activated in the second operation mode based on the second indicator.

5. In claim 1, The above first DCI includes information about the starting time of the indicated operation mode, A method in which, when the first instruction indicates a second operation mode, the second operation mode is activated from a start time indicated by the information about the start time.

6. In a wireless communication system, in the terminal (user equipment), transceiver; and A controller coupled with the above transmitter and receiver is included, The above controller, From a base station, first configuration information for a first operation mode and second configuration information for a second operation mode for one BWP (bandwidth part) are received through RRC (radio resource control) signaling, Activating the first operation mode for the one BWP based on the first setting information; Receive from the base station a first DCI (downlink control information) including a first indicator indicating a change in the operation mode, Identifying whether to change the operation mode from the first operation mode to the second operation mode based on the first indicator; A terminal configured to activate the first operation mode or the second operation mode based on the above identification.

7. In claim 6, The above first operation mode is either SBFD (subband full duplex) mode or TDD (time-domain duplex) mode, The second operation mode is one of the SBFD mode or the TDD mode, The second operation mode is a terminal that is a different operation mode from the first operation mode.

8. In claim 6, the controller, When the first instruction indicates the second operation mode, identifying a change in the operation mode from the first operation mode to the second operation mode; A terminal configured to identify the maintenance of the first operation mode when the first indicator indicates the first operation mode.

9. In claim 6, the controller, Further configured to receive a second DCI including a second indicator for changing the operation mode from the base station, When the first instruction indicates the second operation mode and the second instruction indicates the first operation mode, Before the second operation mode is activated based on the first directive, the channel and signal for the higher layer established while the first operation mode is activated are released or suspended, A terminal in which channels and signals for the upper layer that were released or suspended are reactivated before the first mode is activated in the second operation mode based on the second indicator.

10. In claim 8, The above first DCI includes information about the starting time of the indicated operation mode, A terminal in which the second operation mode is activated from the start time indicated by the information about the start time when the first instruction indicates the second operation mode.

11. A method performed by a base station in a wireless communication system, A step of transmitting, to a terminal (user equipment), first configuration information for a first operation mode and second configuration information for a second operation mode for one BWP (bandwidth part) through RRC (radio resource control) signaling; and A step of receiving, to the terminal, a first DCI (downlink control information) including a first indicator instructing a change in the operation mode, Based on the above first setting information, the first operation mode for the one BWP is activated, A method wherein the first instruction is associated with a change of the operating mode from the first operating mode to the second operating mode.

12. In claim 11, The above first operation mode is either SBFD (subband full duplex) mode or TDD (time-domain duplex) mode, The second operation mode is one of the SBFD mode or the TDD mode, A method wherein the second operation mode is a different operation mode from the first operation mode.

13. In claim 11, the method comprises: Further comprising the step of transmitting a second DCI including a second indicator for changing the operation mode to the terminal; When the first instruction indicates the second operation mode and the second instruction indicates the first operation mode, Before the second operation mode is activated based on the first directive, the channel and signal for the higher layer established while the first operation mode is activated are released or suspended, A method wherein channels and signals for the upper layer that were released or suspended are re-activated before the first mode is activated in the second operation mode based on the second indicator.

14. In a base station in a wireless communication system, transceiver; and A controller coupled with the above transmitter and receiver is included, The above controller, Transmitting first configuration information for a first operation mode and second configuration information for a second operation mode for one BWP (bandwidth part) to a terminal (user equipment) through RRC (radio resource control) signaling, The terminal is configured to receive a first DCI (downlink control information) including a first indicator instructing a change in the operation mode, Based on the above first setting information, the first operation mode for the one BWP is activated, The above first indicator is a base station associated with a change of the operating mode from the first operating mode to the second operating mode.

15. In claim 14, the controller, Further configured to transmit a second DCI including a second indicator for changing the operation mode to the terminal; When the first instruction indicates the second operation mode and the second instruction indicates the first operation mode, Before the second operation mode is activated based on the first directive, the channel and signal for the higher layer established while the first operation mode is activated are released or suspended, Based on the second directive, before the first mode is activated in the second operation mode, the channel and signal for the upper layer that were released or suspended are reactivated, The above first operation mode is either SBFD (subband full duplex) mode or TDD (time-domain duplex) mode, The second operation mode is one of the SBFD mode or the TDD mode, A base station, wherein the second operation mode is a different operation mode from the first operation mode.

Images