Method and device for link direction indication for full-duplex communication in wireless communication system

Abstract

A method performed by a terminal in a wireless communication system comprises the steps of: receiving information associated with a transition guard period from a base station; checking the position of the transition guard period on the basis of the information; and switching from uplink to downlink or from downlink to uplink in the transition guard period, wherein, when switching from downlink to uplink, the position of the transition guard period starts from the first symbol among consecutive symbols capable of uplink transmission, and each of the consecutive symbols capable of uplink transmission may be a symbol corresponding to an uplink sub-band and a downlink sub-band.

Description

Method and device for indicating link direction for full-duplex communication in a wireless communication system

[0001] The present disclosure relates to the operation of a terminal and a base station in a wireless communication system. Specifically, the present disclosure relates to a method for performing subband non-overlapping full duplex (SBFD) transmission and a device therefor.

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

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

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

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

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

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

[0008] As described above and with the development of wireless communication systems, various services have become available, and methods for providing these services smoothly are required.

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

[0010] The present disclosure provides a method for setting time resources in Subband non-overlapping full duplex (SBFD).

[0011] One aspect of one embodiment of the present disclosure provides a method performed by a terminal in a wireless communication system. The method includes the steps of receiving information associated with a transition guard interval from a base station, identifying a location of the transition guard interval based on the information, and switching from uplink to downlink or downlink to uplink in the transition guard interval, wherein, when switching from downlink to uplink, the location of the transition guard interval starts from a first symbol among consecutive symbols capable of uplink transmission, and each of the consecutive symbols capable of uplink transmission may be a symbol corresponding to an uplink subband and a downlink subband.

[0012] Another aspect according to one embodiment of the present disclosure provides a terminal in a wireless communication system. The terminal includes a transceiver and at least one processor operably connected to the transceiver, wherein the at least one processor receives information associated with a transition guard interval from a base station, determines a location of the transition guard interval based on the information, and is configured to switch from uplink to downlink or from downlink to uplink in the transition guard interval, wherein when switching from downlink to uplink, the location of the transition guard interval starts from a first symbol among consecutive symbols capable of uplink transmission, and each of the consecutive symbols capable of uplink transmission may be a symbol corresponding to an uplink subband and a downlink subband.

[0013] Another aspect according to one embodiment of the present disclosure provides a method performed by a base station in a wireless communication system. The method comprises the steps of determining a position of a transition guard interval, generating information associated with the transition guard interval, and transmitting the information associated with the transition guard interval to a terminal, wherein a transition from uplink to downlink or from downlink to uplink occurs in the transition guard interval, and in the case of a transition from downlink to uplink, the position of the transition guard interval starts from a first symbol among consecutive symbols capable of uplink transmission, and each of the consecutive symbols capable of uplink transmission may be a symbol corresponding to an uplink subband and a downlink subband.

[0014] According to one embodiment of the present disclosure, SBFD resources can be set efficiently.

[0015] Additionally, according to one embodiment of the present disclosure, a transition guard section required for switching from uplink to downlink or from downlink to uplink can be set.

[0016] Additionally, according to one embodiment of the present disclosure, resources required for transmission and reception in a wireless communication system can be efficiently used.

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

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

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

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

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

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

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

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

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

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

[0027] FIG. 11 illustrates a random access procedure in a wireless communication system according to an embodiment of the present disclosure.

[0028] FIG. 12 is a diagram illustrating a TDD (time division duplex) setting and an SBFD setting according to an embodiment of the present disclosure.

[0029] FIG. 13 is a diagram illustrating a symbol pattern of a terminal according to an embodiment of the present disclosure.

[0030] FIG. 14 is a diagram illustrating a flowchart of a terminal according to an embodiment of the present disclosure.

[0031] FIG. 15 is a diagram illustrating 14 symbols set as regular CP (cyclic prefix) and 12 symbols set as extended CP in one slot according to one embodiment of the present disclosure.

[0032] FIG. 16 illustrates symbol types of symbols set to regular CP and symbols set to extended CP based on TDD DL (downlink) / UL (uplink) configuration according to one embodiment of the present disclosure.

[0033] FIG. 17 illustrates a first method for determining symbol types of symbols set to regular CP and symbols set to extended CP based on TDD DL / UL settings and SBFD settings according to one embodiment of the present disclosure.

[0034] FIG. 18 illustrates a second method for determining symbol types of symbols set to regular CP and symbols set to extended CP based on TDD DL / UL settings and SBFD settings according to one embodiment of the present disclosure.

[0035] FIG. 19 illustrates a third method for determining symbol types of symbols set to regular CP and symbols set to extended CP based on TDD DL / UL settings and SBFD settings according to one embodiment of the present disclosure.

[0036] FIG. 20 illustrates a fourth method for determining symbol types of symbols set to regular CP and symbols set to extended CP based on TDD DL / UL settings and SBFD settings according to one embodiment of the present disclosure.

[0037] FIG. 21 illustrates a flowchart for determining a symbol type of a symbol set as an extended CP by a terminal according to an embodiment of the present disclosure.

[0038] FIG. 22 is a diagram showing a terminal transmitting and receiving from a first transmission reception point (TRP) and a second TRP according to an embodiment of the present disclosure.

[0039] FIG. 23 is a flowchart illustrating terminal operations for multiple TRPs according to one embodiment of the present disclosure.

[0040] FIG. 24 illustrates a method of changing some of the SBFD symbols into non-SBFD symbols when the SBFD symbols overlap with the OFDM (orthogonal frequency division multiplexing) symbols corresponding to the SSB (synchronization signal block) according to one embodiment of the present disclosure.

[0041] FIG. 25 illustrates a method of changing some of the SBFD symbols into non-SBFD symbols when OFDM symbols corresponding to SSB and SBFD symbols overlap according to an embodiment of the present disclosure.

[0042] FIG. 26 illustrates a method of changing some of the SBFD symbols into non-SBFD symbols when OFDM symbols corresponding to SSB and SBFD symbols overlap according to one embodiment of the present disclosure.

[0043] FIG. 27 illustrates a method of changing some of the SBFD symbols into non-SBFD symbols when the OFDM symbols corresponding to SSB and the SBFD symbols overlap according to one embodiment of the present disclosure.

[0044] FIG. 28 is a diagram illustrating a flowchart of operations performed by a terminal according to an embodiment of the present disclosure.

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

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

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

[0048] 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 more clearly convey the gist of the present disclosure without obscuring it by omitting unnecessary explanations.

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

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

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

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

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

[0054] Here, the term '~ part' used in the present embodiment means software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and the '~ 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. Furthermore, in an embodiment, the '~part' may include one or more processors.

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

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

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

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

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

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

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

[0062] [NR time-frequency resources]

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

[0064] FIG. 1 is a diagram illustrating the basic structure of a time-frequency domain, which is a wireless resource domain in which data or control channels are transmitted, in a wireless communication system according to one embodiment of the present disclosure.

[0065] Referring to Figure 1, the horizontal axis represents the time domain and the vertical axis represents the frequency domain. The basic unit of resources in the time and frequency domains is a resource element (RE, 101), which can be defined as 1 OFDM (Orthogonal Frequency Division Multiplexing) symbol (102) in the time axis and 1 subcarrier (103) in the frequency axis. In the frequency domain (For example, 12) consecutive REs can form one resource block (RB, 104). In the time domain, one subframe (110) can be composed of one or more slots.

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

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

[0068]

[0069] [Bandwidth Part (BWP)]

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

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

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

[0073]

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

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

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

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

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

[0079] Furthermore, in some embodiments, the base station may configure bandwidth portions with different bandwidth sizes for the terminal to reduce power consumption. For example, if the terminal supports a very large bandwidth, such as 100 MHz, and constantly transmits and receives data using that bandwidth, this may result in very high power consumption. In particular, monitoring unnecessary downlink control channels using a large bandwidth of 100 MHz in a traffic-free environment may be very inefficient in terms of power consumption. To reduce power consumption, 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 using the 100 MHz bandwidth portion according to the instructions of the base station.

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

[0081] [Bandwidth Part (BWP) Change]

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

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

[0084]

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

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

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

[0088] [SS / PBCH block]

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

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

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

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

[0093] - PBCH: Provides essential system information required for transmission and reception of data and control channels on 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.

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

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

[0096] [PDCCH: DCI related]

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

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

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

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

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

[0102]

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

[0104]

[0105]

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

[0107]

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

[0109]

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

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

[0112] FIG. 4 is a diagram illustrating an example of a control region (Control Resource Set, CORESET) in which a downlink control channel is transmitted in a wireless communication system according to an embodiment of the present disclosure.

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

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

[0115]

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

[0117] FIG. 5 is a diagram showing an example of a basic unit of time and frequency resources that constitute a downlink control channel in a wireless communication system according to an embodiment of the present disclosure.

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

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

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

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

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

[0123]

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

[0125] According to the configuration information, one or more search space sets may exist in a common search space or a terminal-specific search space. For example, search space set #1 and search space set #2 may be configured as a common search space, and search space set #3 and search space set #4 may be configured as terminal-specific search spaces.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0147]

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

[0149] [Mathematical Formula 1]

[0150]

[0151]

[0152] - L: Integration level

[0153] - : Carrier Index

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

[0155] - : slot index

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

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

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

[0159] - , , , , , D=65537.

[0160] - : Terminal identifier

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

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

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

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

[0165] 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". If all or part of the time and frequency resources of the scheduled data channel (601) overlap with the set rate matching resources (602), the base station can rate-match and transmit the data channel (601) in the rate matching resource (602) portion, and the terminal can perform reception and decoding after assuming that the data channel (601) is rate-matched in the rate matching resource (602) portion.

[0166] 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".

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

[0168] RB symbol level

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

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

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

[0172] RE level

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

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

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

[0176] [PDSCH: Frequency Resource Allocation Related]

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

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

[0179] Referring to Fig. 7, if a 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 includes a bitmap consisting of NRBG bits. The conditions for this will be explained later. At this time, NRBG means the number of RBGs (resource block groups) determined as shown in [Table 11] below according to the BWP size allocated by the BWP indicator and the upper layer parameter rbg-Size, and data is transmitted to the RBG indicated as 1 by the bitmap.

[0180]

[0181] 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 (720) and the length (725) of frequency axis resources allocated continuously therefrom.

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

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

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

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

[0186]

[0187]

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

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

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

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

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

[0193] [PUSCH: Transmission method related]

[0194] Next, we describe the scheduling method for PUSCH transmission. PUSCH transmission can be dynamically scheduled by the UL grant within the DCI or can operate by configured grant Type 1 or Type 2. Dynamic scheduling instructions for PUSCH transmission are possible using DCI formats 0_0 or 0_1.

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

[0196]

[0197] 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 upper signaling, pusch-Config in [Table 15], is 'codebook' or 'nonCodebook'.

[0198] 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 15], the UE does not expect to be scheduled with DCI format 0_1.

[0199]

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

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

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

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

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

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

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

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

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

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

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

[0211] [CA / DC related]

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

[0213] Referring to FIG. 10, the wireless protocol of the next-generation mobile communication system is composed of NR SDAP (Service Data Adaptation Protocol S25, S70), NR PDCP (Packet Data Convergence Protocol S30, S65), NR RLC (Radio Link Control S35, S60), and NR MAC (Medium Access Control S40, S55) in the terminal and NR base station, respectively.

[0214] Key features of NR SDAP (S25, S70) may include some of the following:

[0215] - Transfer of user plane data

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

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

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

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

[0220] The main functions of NR PDCP (S30, S65) may include some of the following functions:

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

[0222] - User data transfer function

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

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

[0225] - PDCP PDU reordering for reception

[0226] - Duplicate detection of lower layer SDUs

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

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

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

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

[0231] The main functions of NR RLC (S35, S60) may include some of the following functions:

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

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

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

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

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

[0237] - Re-segmentation of RLC data PDUs

[0238] - Reordering of RLC data PDUs

[0239] - Duplicate detection function

[0240] - Protocol error detection

[0241] - RLC SDU discard function

[0242] - RLC re-establishment function

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

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

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

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

[0247] - Multiplexing / demultiplexing of MAC SDUs

[0248] - Scheduling information reporting function

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

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

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

[0252] - MBMS service identification function

[0253] - Transport format selection function

[0254] - Padding function

[0255] The NR PHY layer (S45, S50) can perform operations such as channel coding and modulating upper layer data, converting it into OFDM symbols and transmitting it over a wireless channel, or demodulating and channel decoding OFDM symbols received over a wireless channel and transmitting them to a higher layer.

[0256] The above wireless protocol structure can have various detailed structures depending on the carrier (or cell) operation method. For example, when a base station transmits data to a terminal based on a single carrier (or cell), the base station and the terminal use a protocol structure that has a single structure for each layer, such as S00. On the other hand, when a base station transmits data to a terminal based on CA (carrier aggregation) that uses multiple carriers in a single TRP, the base station and the terminal use a protocol structure that has a single structure up to RLC, such as S10, but multiplexes the PHY layer through the MAC layer. As another example, when a base station transmits data to a terminal based on DC (dual connectivity) that uses multiple carriers in multiple TRPs, the base station and the terminal use a protocol structure that has a single structure up to RLC, such as S20, but multiplexes the PHY layer through the MAC layer.

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

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

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

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

[0261] - MIB (Master Information Block)

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

[0263] - RRC (Radio Resource Control)

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

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

[0266] - PDCCH (Physical Downlink Control Channel)

[0267] - DCI (Downlink Control Information)

[0268] - UE-specific DCI

[0269] - Group common DCI

[0270] - Common DCI

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

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

[0273] - PUCCH (Physical Uplink Control Channel)

[0274] - UCI (Uplink Control Information)

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

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

[0277] [SBFD Operation]

[0278] Meanwhile, 3GPP introduced SBFD (Subband Non-Overlapping Full Duplex) as a new NR-based duplex method. SBFD is a technology that utilizes a portion of downlink resources as uplink resources in the TDD band (spectrum) of frequencies below 6 GHz or above 6 GHz, allowing the base station to receive uplink transmissions from terminals equivalent to the increased uplink resources, thereby expanding the uplink coverage of the terminals, and reducing feedback delay by receiving feedback on downlink transmissions from the terminals in the expanded uplink resources.

[0279] In the present disclosure, a terminal that receives information on whether SBFD is supported from a base station and can perform uplink transmission on a portion of downlink resources may be conveniently referred to as an SBFD terminal (SBFD-capable UE). The SBFD method is defined in the standard, and the following methods may be considered for an SBFD terminal to determine whether SBFD is supported in a specific cell (or frequency, frequency band).

[0280] First method. In addition to the existing unpaired spectrum (or TDD) or paired spectrum (or 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 as system information. The SBFD terminal may receive the system information including the SBFD support status and determine whether SBFD is supported in the specific cell (or frequency, frequency band).

[0281] Second method. Whether SBFD is additionally supported in a specific frequency or frequency band of an existing unpaired spectrum (or TDD) can be indicated to the terminal 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 system information. The SBFD terminal can receive system information including whether SBFD is supported and determine whether SBFD is supported in the specific cell (or frequency, frequency band).

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

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

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

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

[0286] Alternatively, 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 as the first PDCCH and the second PDCCH, and the CRC (cyclic redundancy code) of the first PDCCH and the second PDCCH can be scrambled with the same RNTI (e.g., SI-RNTI). The search space for monitoring the second PDCCH can be acquired from the system information of the first PDSCH, and if it is not acquired (i.e., the system information of the first PDSCH does not include information about the search space), the terminal can receive the second PDCCH in the same search space as the search space of the first PDCCH.

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

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

[0289] The base station may configure random access resources for TDD terminals and additionally configure separate random access resources for SBFD terminals. Here, SBFD terminals may use the random access resources for TDD terminals, or SBFD terminals may not use the random access resources for TDD terminals. In the latter case, SBFD terminals can only always use the separate random access resources for SBFD terminals.

[0290] The SBFD terminal can be instructed by the base station whether or not it can use random access resources for TDD terminals. This can be indicated by being included in the SIB. That is, separate random access resources for SBFD terminals can be configured in the SIB, and along with the configuration, the availability of random access resources for TDD terminals can be indicated. This can be indicated by 1 bit. If the 1 bit is '0' (or FALSE), the SBFD terminal cannot use random access resources for TDD terminals. If the 1 bit is '1' (or TRUE), the SBFD terminal can use random access resources for TDD terminals.

[0291] The base station can determine the type of terminal attempting to access the cell based on the random access resources used by the terminal. For example, an SBFD terminal can transmit a PRACH through a separate random access resource for SBFD terminals, and the base station can determine that the SBFD terminal is attempting to access the cell when receiving the PRACH. For example, a TDD terminal can transmit a PRACH through a random access resource for TDD terminals, and the base station can determine that the TDD terminal is attempting to access the cell when receiving the PRACH. Note that if an SBFD terminal is allowed to transmit a PRACH through a random access resource for a TDD terminal, the base station may be ambiguous as to whether the type of the terminal transmitting the PRACH is a TDD terminal or an SBFD terminal. In this case, the base station can always assume that the type of the terminal is a TDD terminal.

[0292] When the base station determines that the terminal is an SBFD terminal, the base station may schedule messages 2 (msg2), 3 (msg3), 4 (msg4), etc. to the terminal based on the uplink subband configuration. That is, when the base station schedules reception of msg2 and msg4 to the terminal, the base station may schedule msg2 and msg4 not to be received in the uplink subband (when the terminal receives a PDSCH including msg2 and msg4, the PDSCH is received in a frequency resource excluding the uplink subband). When the base station schedules msg3 PUSCH to the terminal, the base station may schedule msg3 PUSCH to be transmitted within the uplink subband.

[0293] If the base station determines that the terminal is a TDD terminal, the base station cannot use the uplink subband configuration when scheduling msg2, msg3, and msg4 to the terminal. That is, even if the uplink subband is configured in the downlink symbol or flexible symbol, the base station can assume that the terminal cannot obtain the uplink subband configuration information. When the base station schedules msg3 PUSCH to the terminal, the msg3 PUSCH can be scheduled in the flexible symbol or the uplink symbol. In other words, the msg3 PUSCH cannot be scheduled in the uplink subband.

[0294] 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 on the random access resources. Thereafter, the SBFD terminal may complete the random access process and proceed to an RRC connection mode for transmitting and receiving data with the cell. After the RRC connection mode, the SBFD terminal may receive a higher layer signal or a physical signal from the base station that can determine that some frequency resources of the downlink time resources are set uplink resources, and may perform an SBFD operation, for example, transmit an uplink signal on the uplink resources.

[0295] When the SBFD terminal determines that the cell supports SBFD, the terminal may transmit 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 to connect is an SBFD terminal. Alternatively, when half-duplex communication support is a mandatory implementation for the SBFD terminal, whether or not the half-duplex communication is supported may be omitted from the capability information. The SBFD terminal may report the capability information to the base station through a random access procedure, may report to the base station after completing the random access procedure, or may report to the base station after proceeding to an RRC connection mode for transmitting and receiving data with the cell.

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

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

[0298] FIG. 11 illustrates a random access procedure in a wireless communication system according to an embodiment of the present disclosure.

[0299] Referring to FIG. 11, a contention-based random access procedure is illustrated as an example. In addition, although not illustrated in FIG. 11, the base station may transmit a synchronization signal block as described in the above-described embodiments. At this time, the base station may periodically transmit the synchronization signal block using beam sweeping. For example, the base station may transmit a synchronization signal block including a PSS / SSS (synchronization signal) and a PBCH (broadcast channel) signal using up to 64 different beams for 5 ms, and multiple synchronization signal blocks may be transmitted using different beams. The terminal may detect (select) a synchronization signal block having an optimal beam direction (e.g., a beam direction having the strongest received signal strength or greater than a predetermined threshold) and transmit a preamble using a PRACH (physical random access channel) resource associated with the detected synchronization signal block. For example, as a first step (1101) of a random access procedure, a terminal may transmit a random access preamble (or message 1) to a base station. The base station, which receives the random access preamble, may measure a transmission delay value between the terminal and the base station and synchronize uplink. Specifically, the terminal may transmit a random access preamble randomly selected from a random access preamble set given in advance by system information. In addition, the initial transmission power of the random access preamble may be determined according to the path loss between the terminal and the base station measured by the terminal. In addition, the terminal may determine a transmission beam direction (or transmission beam or beam) of the random access preamble based on a synchronization signal block received from the base station, and transmit the random access preamble by applying the determined transmission beam direction.

[0300] In the second step (1102), the base station can transmit a response (random access response, RAR, or message 2 (msg2)) to the terminal for the detected random access attempt. The base station can transmit an uplink transmission timing control command to the terminal based on a transmission delay value measured from the random access preamble received in the first step (1101). In addition, the base station can transmit an uplink resource and power control command to be used by the terminal as scheduling information. The scheduling information can include control information for the uplink transmission beam of the terminal. The RAR is transmitted through the PDSCH and can include at least one of the following information.

[0301] - Random access preamble sequence index detected by the network (or base station)

[0302] - TC-RNTI (temporary cell radio network temporary identifier)

[0303] - Uplink scheduling grant

[0304] - Timing advance value

[0305] If the terminal does not receive RAR, which is scheduling information for message 3, from the base station for a predetermined period of time in the second step (1102), the first step (1101) may be performed again. If the first step is performed again, the terminal increases the transmission power of the random access preamble by a predetermined step and transmits it (this is called power ramping), thereby increasing the probability of the base station receiving the random access preamble.

[0306] In the third step (1103), the terminal may transmit uplink information (scheduled transmission, or message 3) including its terminal identifier (which may be referred to as UE contention resolution identity) (or a valid terminal identifier (C-RNTI) if the terminal already has a valid terminal identifier within the cell before initiating the random access procedure) to the base station through an uplink data channel (physical uplink shared channel, PUSCH) using the uplink resources allocated in the second step (1102). The PUSCH may be referred to as message 3 PUSCH (msg3 PUSCH). The transmission timing of the uplink data channel for transmitting message 3 may follow the uplink transmission timing control command received from the base station in the second step (1102). In addition, the transmission power of the uplink data channel for transmitting message 3 may be determined in consideration of the power control command received from the base station in the second step (1102) and the power ramping value of the random access preamble. The uplink data channel for transmitting the above message 3 may be the first uplink data signal transmitted by the terminal to the base station after the terminal transmits a random access preamble.

[0307] In the fourth step (1104), if the base station determines that the terminal has performed random access without collision with other terminals, it can transmit a message (contention resolution message (CR message), or message 4)) including the identifier of the terminal that transmitted uplink data in the third step (1103) to the terminal. In this regard, if multiple terminals receive the same TC-RNTI in the second step (1102), each of the multiple terminals that received the same TC-RNTI can include its own terminal identifier (UE contention resolution identity) in message 3 in the third step (1103) and transmit it to the base station, and the base station can transmit message 4 (CR message) including the terminal identifier of one of the identifiers of the multiple terminals to resolve contention. When the terminal receives message 4 (CR message) including its terminal identifier from the base station in step 4 (1104) (or transmits message 3 including terminal identifier (C-RNTI) in step 3 (1103) and receives terminal-specific control information including CRC based on the terminal identifier (C-RNTI) through PDCCH in step 4 (1104), the terminal can determine that random access is successful. Accordingly, among multiple terminals that have received the same TC-RNTI from the base station, a terminal that confirms that its terminal identifier is included in message 4 (CR message) can confirm that the contention is successful. In addition, the terminal can transmit HARQ-ACK / NACK indicating whether message 4 was successfully received to the base station through an uplink control channel (physical uplink control channel, PUCCH).

[0308] If the data transmitted by the terminal in step 3 (1103) collides with data from another terminal, causing the base station to fail to receive a data signal from the terminal, the base station may not transmit any more data to the terminal. Accordingly, if the terminal fails to receive data transmitted from the base station in step 4 (1104) for a certain period of time, the random access procedure may be determined to have failed, and the procedure may be restarted from step 1 (1101).

[0309] As described above, in the first step (1101) of the random access process, the terminal can transmit a random access preamble on the PRACH. Each cell has 64 available preamble sequences, and four long preamble formats and nine short preamble formats can be used depending on the transmission type. The terminal generates 64 preamble sequences using the root sequence index and cyclic shift value signaled as system information, and can randomly select one sequence to use as a preamble.

[0310] The base station can inform the terminal of the configuration information for random access resources, for example, the control information (or configuration information) indicating the time-frequency resources that can be used for PRACH, using at least one of SIB, higher layer signaling (RRC (Radio Resource Control) information), or DCI (Downlink Control Information). The frequency resource for PRACH transmission can indicate the start RB point of transmission to the terminal, and the number of RBs used can be determined according to the preamble format transmitted through PRACH and the applied subcarrier spacing. The time resource for PRACH transmission can inform the subframe index and start symbol including the preset PRACH configuration period, PRACH transmission time (PRACH occasion, which can be used interchangeably with transmission time), and the number of PRACH transmission time points in the slot, etc., through the PRACH configuration index (0 to 255), as shown in Table 16 below. The terminal can determine the validity of the PRACH transmission times indicated by the PRACH configuration index, and determine only the valid PRACH transmission times as PRACH transmission times at which the random access preamble can be transmitted. Through the PRACH configuration index, the random access configuration information included in the SIB, and the index of the SSB selected by the terminal, the terminal can check the time and frequency resources for transmitting the random access preamble, and transmit the selected sequence as a preamble to the base station.

[0311]

[0312] Meanwhile, according to an embodiment of the present disclosure, a method of determining the validity of a PRACH transmission time point through a PRACH configuration index and SBFD settings for an SBFD terminal to perform PRACH transmission, and performing PRACH transmission through the PRACH transmission time point determined to be valid, and a procedure of the SBFD terminal is required when the valid PRACH transmission time point and downlink reception overlap.

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

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

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

[0316] Next, in (b) to (d) of FIG. 12, a case is shown where SBFD is operated together with TDD in a specific frequency band.

[0317] Referring to (b) of FIG. 12, the terminal may set a portion of the frequency band of the cell as a frequency band (1210) capable of uplink transmission. This band may be referred to as an uplink subband (UL subband). And the uplink subband (UL subband) may be applied to all symbols of all slots. The terminal may transmit an uplink channel or signal scheduled in the uplink slot (or symbol) (1211) and all symbols (1212) within the subband (UL subband). However, the terminal may not transmit an uplink channel or signal in a band other than the subband (UL subband) in the downlink slot (or symbol) and the flexible slot (or symbol).

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

[0319] Referring to (d) of FIG. 12, a terminal may be configured with time-frequency resources capable of uplink transmission. The terminal may configure one or more time-frequency resources as time-frequency resources capable of uplink transmission. For example, some frequency bands (1232) of the first and second slots may be configured as time-frequency resources capable of uplink transmission. In addition, some frequency bands (1233) of the third slot and some frequency bands (1234) of the fourth slot may be configured as time-frequency resources capable of uplink transmission. The terminal may transmit an uplink channel or signal in an uplink slot (or symbol) (1231), some frequency bands (1232) of the first and second slots, some frequency bands (1233) of the third slot, and some frequency bands (1234) of the fourth slot.

[0320] In the following description, the time-frequency resources that enable uplink transmission in downlink symbols or flexible symbols may be referred to as SBFD resources / UL subbands.

[0321] <Example 1: Determining Link Direction>

[0322] According to an embodiment of the present disclosure, a terminal can determine a transmission symbol and a reception symbol from the terminal's perspective using a single-level signaling method. If a transmission symbol from the terminal's perspective is indicated in the SBFD symbol, uplink transmission is possible in the UL subband of the SBFD symbol, but downlink reception in the DL subband may not be possible. If a reception symbol from the terminal's perspective is indicated in the SBFD symbol, downlink reception is possible in the DL subband of the SBFD symbol, but uplink transmission in the UL subband may not be possible.

[0323] In the first embodiment, a single level of signaling may refer to configuration information transmitted from a base station to a terminal. For example, the signaling may be transmitted via a system information block (SIB), RRC, MAC-CE, or DCI. When transmitted via DCI, the DCI may be a terminal-specific DCI that schedules a PDSCH or PUSCH, or a group-common DCI (e.g., DCI format 2_0) that multiple terminals in a cell monitor.

[0324] In an embodiment, the signaling may include information about one of the following periods (T) (e.g., the first period or the second period).

[0325] The first period may be a period (P, unit ms) included in the TDD DL / UL configuration set by the terminal from the base station. That is, T may be P.

[0326] From the start of 4 frames (one frame is 10ms, 4 frames is 40ms), depending on the TDD DL / UL configuration, the symbols within the cycle can have a pattern (hereinafter referred to as a TDD pattern) of symbol types (downlink symbols, uplink symbols, and flexible symbols) from the base station's perspective, and from the terminal's perspective, the above patterns can be applied according to the cycle. When the cycle included in the TDD DL / UL configuration is P (unit: ms), 40 / P can be a natural number. That is, an integer multiple of P can be 40.

[0327] A TDD DL / UL configuration can include up to two TDD patterns. If the period of the TDD DL / UL configuration is P (ms), the first TDD pattern can include a symbol type from the base station's perspective for the first P1 (ms) of P (ms), and the second TDD pattern can include a symbol type from the base station's perspective for the second P2 (ms) of P (ms). That is, P can be expressed as P1+P2.

[0328] For the second period, the period (P, unit: ms) included in the TDD DL / UL configuration set by the terminal from the base station may be an integer multiple. That is, the terminal may obtain P from the TDD DL / UL configuration and may set or receive an instruction from the base station to apply M to it. That is, T = P*M.

[0329] Here, setting means being set from a higher layer signal of the base station (e.g., a system information block (SIB) or radio resource control (RRC) signal) or a MAC-CE signal), and indication may mean being indicated through an L1 signal (e.g., a terminal-specific DCI format or a terminal common / group common DCI format).

[0330] Here, the M value can be set to one of {1,2,4,5,8,10}.

[0331] Alternatively, the M value can be set to one of the values ​​{1,2,4,5,8,10,16,20}.

[0332] Alternatively, the M value can be set to one of the values ​​{1,2,4,5,8,10,16,20,32,40}.

[0333] Alternatively, the M value can be set to one of the values ​​{1,2,4,5,8,10,16,20,32,40,64,80}.

[0334] Here, the range of the M value can be determined differently depending on at least the period value P of the TDD DL / UL setting. And, when X / P = Y, the divisors of Y can be included in the range of the M value. X can be determined according to the following methods 1-1 to 1-3.

[0335] [Method 1-1]

[0336] For example, when X / P = Y, the divisors of Y can be included in the range of M values. Here, X can be 40. This is because 40 / P is a natural number for all cycles, P, included in the TDD DL / UL configuration.

[0337] For example, when P=2.5, Y=16, and the divisors of 16, 1, 2, 4, 8, 16, can be determined as the range of M values. For example, when P=4, Y=10, and the divisors of 10, 1, 2, 5, 10, can be determined as the range of M values.

[0338] More specifically, Table 17 shows the range of M values ​​determined according to the period value P of the TDD DL / UL configuration and X=40. In Table 17, the period value P of the TDD DL / UL configuration is the applicable subcarrier spacing. This is shown.

[0339] Referring to Table 17, the range of M values ​​corresponding to all period values ​​P of the TDD DL / UL configuration may be as follows.

[0340] M = {1,2,4,5,8,10,16,20,32,40,64,80}

[0341] The terminal can receive P and M values ​​as upper layer signals from the base station. Here, the P value can be set to one of {0.5, 0.625, 1, 1.25, 2, 2.5, 4, 5, 10}, and the M value can be set to one of {1, 2, 4, 5, 8, 10, 16, 20, 32, 40, 64, 80}. In addition, the M value can satisfy a divisor of 40 / P. That is, if a value that is not a divisor of 40 / P is set as the M value, the terminal can determine this as a miss configuration or an error case.

[0342] Only some of the candidate values ​​for the M value in Table 17 can be set. For example, only {1,2,4,8,10} can be included as candidate values ​​for the M value. In other words, by excluding values ​​greater than a certain value from the values ​​in Table 17, a cycle greater than a certain value can be prevented.

[0343]

[0344] [Method 1-2]

[0345] As another example, when X / P = Y, the divisors of Y can be included in the range of M values. For example, X can be the reception period of SSB. Here, X can be the reception period of SSB, and X=20 [ms].

[0346] For example, when P=2.5, Y=8, and the divisors of 8, 1, 2, 4, 8, can be determined as the range of M values. For example, when P=4, Y=5, and the divisors of 5, 1, 5, can be determined as the range of M values.

[0347] More specifically, Table 18 shows the range of M values ​​determined according to the period value P of the TDD DL / UL configuration and X=20. In Table 18, the period value P of the TDD DL / UL configuration is the applicable subcarrier spacing. This is shown.

[0348] Referring to Table 18, the range of M values ​​corresponding to all period values ​​P of the TDD DL / UL configuration may be as follows.

[0349] M = {1,2,4,5,8,10,16,20,32,40}

[0350] The terminal can receive P and M values ​​as upper layer signals from the base station. Here, the P value can be set to one of {0.5, 0.625, 1, 1.25, 2, 2.5, 4, 5, 10}, and the M value can be set to one of {1, 2, 4, 5, 8, 10, 16, 20, 32, 40}. In addition, the M value can satisfy a divisor of 20 / P. That is, if a value that is not a divisor of 20 / P is set as the M value, the terminal can determine this as a miss configuration or an error case.

[0351] Only some of the candidate values ​​for the M value in Table 18 can be set. For example, only {1,2,4,8,10} can be included as candidate values ​​for the M value. In other words, by excluding values ​​greater than a certain value from the values ​​in Table 18, a cycle greater than a certain value can be prevented.

[0352]

[0353] [Method 1-3]

[0354] As another example, when X / P = Y, the divisors of Y can be included in the range of M values. Here, X can be the length of one frame. That is, X=10 [ms].

[0355] For example, when P=2.5, Y=4, and the divisors of 4, 1, 2, and 4, can be determined as the range of the M value. Note that when P=4, Y=2.5. That is, Y may not be an integer. In this case, the terminal may not have an M value defined for the period P.

[0356] More specifically, Table 19 shows the range of M values ​​determined according to the period value P of the TDD DL / UL configuration and X=10. In Table 19, the period value P of the TDD DL / UL configuration is the applicable subcarrier spacing. This is shown.

[0357] Referring to Table 19, the range of M values ​​corresponding to all period values ​​P of the TDD DL / UL configuration may be as follows.

[0358] M = {1,2,4,5,8,10,16,20}

[0359] The terminal can receive the P value and the M value as a higher layer signal from the base station. Here, the P value can be set to one of {0.5, 0.625, 1, 1.25, 2, 2.5, 4, 5, 10}, and the M value can be set to one of {1, 2, 4, 5, 8, 10, 16, 20}. In addition, the M value can satisfy a divisor of 10 / P. That is, if a value that is not a divisor of 10 / P is set as the M value, the terminal can determine that this is a miss configuration or an error case.

[0360] Only some of the candidate values ​​for the M value in Table 19 can be set. For example, only {1,2,4,8,10} can be included as candidate values ​​for the M value. In other words, by excluding values ​​greater than a certain value from the values ​​in Table 19, a cycle greater than a certain value can be prevented.

[0361]

[0362] In the above-described methods 1-1 to 1-3, 40, the SSB period, or the length of one frame were used as the X value. In addition, the period of the PRACH preamble may be used as the X value. Alternatively, the X value may be a value set by the base station.

[0363] In the above-described embodiment, the upper layer signal of the base station may not include 1 as the M value. If the terminal does not receive the M value from the upper layer signal, the terminal may determine that the M value is 1.

[0364] In a first embodiment, the signaling may include information about an offset of one of the following:

[0365] According to the first embodiment, the terminal can obtain a period from the base station. The period may be T [ms]. The terminal can be configured with an offset value for the period. The offset value (hereinafter, O) can be configured using at least one of the following methods.

[0366] In the following description, the symbol pattern may be information about S slots. Specifically, the time (S*) corresponding to S slots ) [ms] can be equal to or less than T. That is, the period is T [ms], but the symbol pattern is S* [ms]. Therefore, in order to determine the symbol pattern within the above period T [ms], S* The position can be indicated by the above offset value.

[0367] [Method 2-1]

[0368] The offset value (O) can be set in units of [ms]. The offset value (O) can be one of the values ​​0, 1, 2, ...., T-1. When the terminal is set to the O value, the terminal can apply the symbol pattern as follows.

[0369] For example, the index of the subframe is N subframe When we say, N subframe A symbol pattern can be applied to S consecutive slots, starting from the first slot among the slots included in a subframe satisfying mod T = O. More specifically, the index of the subframe is N subframe = T*N + O. N can be a non-negative integer. That is, the index of the subframe is N subframe = O, T+O, T*2+O, T*3+O,... can be. The index is N subframe In the subframe It may contain slots, where the index of the first slot is N subframe * It could be slot N subframe * , slot N subframe * +1, ..., slot N subframe * +S-1 can apply the symbol pattern of S slots.

[0370] [Method 2-2]

[0371] The offset value (O) can be set in slot units. And the offset value (O) is 0, 1, 2, ..., T* -1 can be one of the values. If the terminal is set to the value O, the terminal can apply the symbol pattern as follows.

[0372] For example, the index of the slot is N slot When we say, N slot mod T* = Starting from the slot satisfying O, a symbol pattern can be applied to S slots. More specifically, the indices of the slots are N slot = T* *N + O can be expressed as N. N can be a non-negative integer. That is, the index of the slot is N. slot = O, T* +O, T* *2+O, T* *3+O,...can be slot N slot , slot N slot +1, ..., slot N slot +S-1 can apply the symbol pattern of S slots.

[0373] [Method 2-3]

[0374] The offset value (O) can be set in units of the cycle, P [ms], of the TDD DL / UL configuration. The offset value (O) can be one of the values ​​0, 1, 2, ...., T / P-1, where T / P can be a natural number. When the terminal is set to the O value, the terminal can apply the symbol pattern as follows.

[0375] For example, an index can be assigned to each period of TDD DL / UL setting, P [ms], from the start of the frame (frame 0). The index can be assigned starting from 0 and increasing by 1. Here, the symbol direction can be set according to the TDD DL / UL setting in the P [ms] section. The index of the P [ms] section can be N TDD When you say, N TDD Starting from the first slot of the P [ms] interval satisfying mod T / P = O, a symbol pattern can be applied to S consecutive slots. More specifically, the index of the P [ms] interval is N TDD = T / P*N + O. N can be a non-negative integer. That is, the index of the P [ms] interval is N TDD = O, T / P+O, T / P*2+O, T / P*3+O,... can be. The index is N TDD The index of the P [ms] interval is P* It may contain slots, where the index of the first slot is N TDD *P* It could be slot N TDD *P* , slot N TDD *P* +1, ..., slot N TDD *P* +S-1 can apply the symbol pattern of S slots.

[0376] In a first embodiment, signaling may include information about a symbol pattern among the following:

[0377] Based on the information about the above symbol pattern, at least one of the following symbol patterns (e.g., a first symbol pattern, a second symbol pattern, a third symbol pattern, etc.) may be indicated.

[0378] - For example, the first symbol pattern may represent a set of symbols for indicating an SBFD symbol. The terminal may regard the symbol indicated in the first symbol pattern as an SBFD symbol. Some frequency bands of the SBFD symbol may be UL subbands, and other bands may be DL subbands.

[0379] - For another example, the second symbol pattern may represent a set of symbol directions from the perspective of the terminal. The second symbol pattern may include a downlink symbol pattern and an uplink symbol pattern. The terminal may regard the symbol indicated in the downlink symbol pattern as a downlink symbol, and may regard the symbol indicated in the uplink symbol pattern as an uplink symbol. The symbol pattern may include both downlink symbols and uplink symbols. That is, the symbol pattern indicates a symbol, and downlink or uplink may be additionally indicated for the symbol. If the terminal has only half-duplex capability, a symbol determined as a downlink symbol and a symbol determined as an uplink symbol cannot overlap. If the terminal has full-duplex capability, a symbol determined as a downlink symbol and a symbol determined as an uplink symbol may overlap.

[0380] - For another example, the third symbol pattern may represent a set of symbols that can be transmitted or not transmitted from the terminal's perspective. The terminal may consider the symbols indicated in the symbol pattern as symbols that can be used for uplink transmission or downlink reception. Alternatively, the terminal may consider the symbols indicated in the symbol pattern as symbols that cannot be used for uplink transmission or downlink reception.

[0381] For reference, based on the above symbol pattern, the base station and terminal can determine the direction of the symbol (whether it is uplink or downlink). Furthermore, the above symbol pattern can be applied to a specific channel.

[0382] For example, the above symbol pattern can be applied to PDSCH reception. That is, when receiving a PDSCH, if the symbol scheduled for the PDSCH is determined to be a symbol capable of downlink reception according to the above pattern, the terminal can receive the PDSCH. When receiving a PDSCH, if the symbol scheduled for the PDSCH overlaps with a symbol that is not capable of downlink reception according to the above pattern, the terminal may not receive the PDSCH.

[0383] Here, PDSCH can be divided into two types. The first type may be a PDSCH to which the above symbol pattern is applied. The second type may be a PDSCH to which the above symbol pattern is not applied.

[0384] - For example, the above type of distinction can be divided by the presence or absence of a DCI format corresponding to the PDSCH. That is, the first type may include PDSCHs without a corresponding DCI format, and the second type may include PDSCHs with a corresponding DCI format. Here, if the PDSCH is scheduled in a DCI format, it can be said that there is a DCI format corresponding to the PDSCH. If the SPS PDSCH is activated in a DCI format, the first SPS PDSCH (first activated PDSCH) among the SPS PDSCHs can be said to have a corresponding DCI format, and from the second SPS PDSCH onwards, it can be said that there is no corresponding DCI format. If the PDSCH repetition is scheduled in a DCI format, the first PDSCH repetition of the PDSCH repetition can be said to have a corresponding DCI format, and from the second repetition onwards, it can be said that there is no corresponding DCI format.

[0385] - For another example, the above types of distinction can be divided according to the type of PDSCH. That is, the first type can be SPS PDSCHs, and the second type can be DG (dynamic grant) PDSCHs. DG PDSCHs can include PDSCHs or PDSCH repetitions scheduled in DCI format.

[0386] - As another example, the above types of distinction can be divided according to the type of DCI format that schedules or activates the PDSCH. That is, the first type can include PDSCHs scheduled with DCI formats 1_1, 1_2, and 1_3, and the second type can include PDSCHs scheduled with DCI format 1_0.

[0387] - As another example, the above types of distinction can be divided according to the type of scrambling of the DCI format that schedules or activates the PDSCH. That is, the first type can include PDSCHs scheduled with a DCI format in which the CRC (cyclic redundancy code) is scrambled with C-RNTI, MCS-C-RNTI, CS-RNTI, and the second type can include PDSCHs scheduled with a DCI format 1_0 in which the CRC is scrambled with SI-RNTI, RA-RNTI, MsgB-RNTI.

[0388] - For another example, the distinction between the above types may be determined according to the priority of the PDSCH. For example, the first type may include a PDSCH corresponding to a low priority, and the second type may include a PDSCH corresponding to a high priority. The priority of the PDSCH scheduled by the DCI may be indicated through a field of the DCI. The field is a Priority Indicator field, which is a field indicating the priority of HARQ-ACK transmission corresponding to the PDSCH. The priority may be used as the priority of the PDSCH. In the case of the SPS PDSCH, the priority may be included and set in the SPS configuration. If there is no explicit priority indication or configuration corresponding to the scheduled PDSCH or SPS PDSCH, the terminal may determine that the PDSCH or SPS PDSCH has the lowest priority.

[0389] The above methods can be used in combination.

[0390] For example, the above symbol pattern can be applied to PUSCH reception. That is, when transmitting a PUSCH, if the symbol scheduled for the PUSCH is determined to be a symbol capable of uplink transmission according to the above pattern, the terminal can transmit the PUSCH. When transmitting a PUSCH, if the symbol scheduled for the PUSCH overlaps with a symbol that is not capable of uplink transmission according to the above pattern, the terminal may not transmit or receive the PUSCH.

[0391] Here, PUSCH can be divided into two types. The first type may be a PUSCH to which the above symbol pattern is applied. The second type may be a PUSCH to which the above symbol pattern is not applied.

[0392] - For example, the above types can be classified based on the presence or absence of a DCI format corresponding to the PUSCH. That is, the first type may include PDSCHs without a corresponding DCI format, and the second type may include PUSCHs with a corresponding DCI format. Here, if a PUSCH is scheduled with a DCI format, it can be said that there is a DCI format corresponding to the PUSCH. If a Type-2 CG PUSCH is activated with a DCI format, the first CG PUSCH (the first activated PUSCH) among the CG PUSCHs can be said to have a corresponding DCI format, and from the second CG PUSCH onwards, it can be said that there is no corresponding DCI format. Since a Type-1 CG PUSCH is activated by a higher layer signal, it can be said that all CG PUSCHs do not have a corresponding DCI format. When PUSCH repetition is scheduled in a DCI format, the first PUSCH repetition can be said to have a corresponding DCI format, and from the second repetition onwards, it can be said to have no corresponding DCI format.

[0393] - For another example, the above types of distinction can be divided according to the type of PUSCH. That is, the first type can be CG PUSCHs, and the second type can be DG (dynamic grant) PUSCHs. DG PUSCHs can include PUSCHs or PUSCH repetitions scheduled in DCI format.

[0394] - For another example, the above types of distinction can be divided according to the type of DCI format that schedules or activates the PUSCH. That is, the first type can include PUSCHs scheduled with DCI format 0_1, 0_2 to 0_3, and the second type can include PUSCHs scheduled with DCI format 0_0. Alternatively, the first type can include PUSCHs scheduled with DCI format 0_0, and the second type can include PUSCHs scheduled with DCI format 0_1, 0_2 to 0_3.

[0395] - As another example, the above types of distinction can be divided according to the type of scrambling of the DCI format for scheduling or activating the PUSCH. That is, the first type can include PUSCHs scheduled in a DCI format in which the CRC (cyclic redundancy code) is scrambled with C-RNTI, MCS-C-RNTI, or CS-RNTI, and the second type can include PUSCHs scheduled in DCI format 1_0 in which the CRC is scrambled with TC-RNTI.

[0396] - For another example, the distinction between the above types may be determined according to the priority of the PUSCH. For example, the first type may include a PUSCH corresponding to a low priority, and the second type may include a PUSCH corresponding to a high priority. The priority of the PUSCH scheduled by the DCI may be indicated through a field of the DCI. The field is a priority indicator field and is a field indicating the priority of the PUSCH. In the case of the CG PUSCH, the priority may be included and set in the CG configuration. If there is no explicit priority indication or configuration corresponding to the scheduled PUSCH or CG PDSCH, the UE may determine that the PUSCH or CG PUSCH has the lowest priority.

[0397] The above methods can be used in combination.

[0398] For example, the above symbol pattern can be applied to PDCCH monitoring. That is, when monitoring the PDCCH, if the symbol on which the PDCCH is scheduled is determined to be a symbol capable of downlink reception according to the above pattern, the terminal can monitor the PDCCH. When monitoring the PDCCH, if the symbol on which the PDCCH is scheduled overlaps with a symbol on which downlink reception is not possible according to the above pattern, the terminal may not monitor the PDCCH.

[0399] Here, the application of the symbol pattern may be determined depending on the type of PDCCH search space. For example, if the search space is a UE-specific search space, the symbol pattern may be applied to PDCCH monitoring of the search space. For example, if the search space is a common search space, the symbol pattern may not be applied to PDCCH monitoring of the search space.

[0400] For example, the above symbol pattern can be applied to CSI-RS reception. That is, when receiving a CSI-RS, if the symbol in which the CSI-RS is scheduled is determined to be a symbol capable of downlink reception according to the above pattern, the terminal can receive the CSI-RS. When receiving a CSI-RS, if the symbol in which the CSI-RS is scheduled overlaps with a symbol in which downlink reception is not possible according to the above pattern, the terminal may not receive the CSI-RS.

[0401] Here, CSI-RS can be divided into two types. The first type may be a CSI-RS to which the above symbol pattern is applied. The second type may be a CSI-RS to which the above symbol pattern is not applied.

[0402] For example, in the case of periodic CSI-RS or semi-persistent CSI-RS set as a higher layer signal, it can be included in the first type, and in the case of aperiodic CSI-RS, it can be included in the second type.

[0403] For example, the above symbol pattern can be applied to SRS transmission. That is, when transmitting an SRS, if the symbol for which the SRS is scheduled is determined to be a symbol capable of uplink transmission according to the above pattern, the terminal can transmit the SRS. When transmitting an SRS, if the symbol for which the SRS is scheduled overlaps with a symbol for which uplink transmission is not possible according to the above pattern, the terminal may not transmit the SRS in the symbol.

[0404] Here, SRS can be divided into two types. The first type may be an SRS to which the above symbol pattern is applied. The second type may be an SRS to which the above symbol pattern is not applied.

[0405] For example, in the case of periodic SRS set as a higher layer signal, it can be included in the first type, and in the case of aperiodic SRS, it can be included in the second type.

[0406] According to one embodiment of the present disclosure, the terminal may apply the symbol pattern to all channels and signals. In this case, the terminal may not receive downlink signals in symbols in which downlink reception is indicated as impossible. The terminal may not transmit uplink signals in symbols in which uplink transmission is indicated as impossible. More specifically, the terminal may deactivate the receiving circuit (including the LNA and down-conversion) and the transmitting circuit (including the PA and up-conversion) to reduce power consumption in symbols in which downlink reception is indicated as impossible and symbols in which uplink transmission is indicated as impossible.

[0407] According to one embodiment of the present disclosure, a terminal may receive symbol patterns set for S slots from a base station. Here, the S symbol patterns may be set in at least one of the following ways.

[0408] [Method 3-1]

[0409] The terminal can be configured with a bitmap as a symbol pattern for symbols included in S slots. The granularity of the bitmap can be a symbol. For example, the S slots can include W=14*S symbols. The terminal can be configured with a bitmap having a size of 14*S from the base station. Each bit of the bitmap can correspond to one of the symbols included in the S slots. The first bit (MSB or LSB) of the bitmap having a size of 14*S can correspond to the symbol that is most forward in time among the 14*S symbols, and the next bit can correspond to the symbol that is second forward in time.

[0410] If the bit is '1', the corresponding symbol can be interpreted as at least one of the following:

[0411] - In case of the first symbol pattern, SBFD symbol;

[0412] - In case of the second symbol pattern, if it is a downlink symbol pattern from the terminal perspective, it is a downlink symbol, and if it is an uplink symbol pattern, it is an uplink symbol; or

[0413] - In the case of the third symbol pattern, if it is a symbol pattern that can (not) be transmitted from the terminal perspective, it is a symbol that can (not) be transmitted, and if it is a symbol pattern that can (not) be received from the terminal perspective, it is a symbol that can (not) be received.

[0414] If the bit is '0', the symbol type may not be set for the corresponding symbol. For example, in the case of the first symbol pattern, it may be a symbol that is not an SBFD symbol, in the case of the second symbol pattern, if it is a downlink symbol pattern from the terminal perspective, it may be a symbol that is not a downlink symbol (flexible or uplink symbol), in the case of an uplink symbol pattern, it may be a symbol that is not an uplink symbol (flexible or downlink symbol), in the case of the third symbol pattern, if it is a transmittable symbol pattern from the terminal perspective, it may be a non-transmittable symbol, if it is a non-receivable symbol pattern from the terminal perspective, it may be a non-receivable symbol, if it is a transmittable symbol pattern from the terminal perspective, it may be a transmittable symbol, and if it is a non-receivable symbol pattern from the terminal perspective, it may be a receivable symbol.

[0415] [Method 3-2]

[0416] The terminal can be configured with a bitmap as a symbol pattern for symbols included in S slots. The granularity of the bitmap can be a slot. For example, S slots can include 14*S symbols. The terminal can be configured with a bitmap of size S from the base station. Each bit of the bitmap can correspond to each of the S slots. The first bit (MSB or LSB) of the bitmap of size S can correspond to the slot that is earliest in time among the S slots, and the next bit can correspond to the slot that is second earliest in time.

[0417] If a bit is '1', the symbols in the corresponding slot can be interpreted as at least one of the following:

[0418] - All symbols included in the above slot can be determined as the same symbol type. For example, in the case of the first symbol pattern, all symbols can be regarded as SBFD symbols. In the case of the second symbol pattern, if it is a downlink symbol pattern from the terminal perspective, all symbols can be regarded as downlink symbols, and if it is an uplink symbol pattern, all symbols can be regarded as uplink symbols. In the case of the third symbol pattern, if it is a transmittable symbol pattern from the terminal perspective, all symbols can be regarded as transmittable symbols, and if it is a receiveable symbol pattern from the terminal perspective, all symbols can be regarded as receiveable symbols.

[0419] - Alternatively, the symbol type may be applied only to some of the symbols included in the slot. And the symbol type may not be applied to the remaining some of the symbols. Here, some of the symbols to which the symbol type is applied may be set by the base station. A specific method will be described later. For example, in the case of the first symbol pattern, some of the symbols may be regarded as SBFD symbols. In the case of the second symbol pattern, if it is a downlink symbol pattern from the perspective of the terminal, some of the symbols may be regarded as downlink symbols, and if it is an uplink symbol pattern, some of the symbols may be regarded as uplink symbols. In the case of the third symbol pattern, if it is a transmittable symbol pattern from the perspective of the terminal, some of the symbols may be regarded as transmittable symbols, and if it is a receiveable symbol pattern from the perspective of the terminal, some of the symbols may be regarded as receiveable symbols.

[0420] If the bit is '0', the symbol type may not be set for the corresponding symbol.

[0421] In the present disclosure, some symbols to which types are applied in slots can be set as follows.

[0422] A terminal may receive a 14-bit bitmap from a base station. Each bit of the 14-bit bitmap may correspond to each of the 14 symbols of a slot. The first bit (MSB or LSB) of the bitmap may correspond to the earliest symbol in time, and the second bit may correspond to the second earliest symbol in time. If the bit is '1', the corresponding symbol may be included in some symbols to which the type is applied. If the bit is '0', the corresponding symbol may be included in some symbols to which the type is not applied.

[0423] The terminal can receive from the base station the index (s) of the starting symbol to which the type is to be applied among the 14 symbols of the slot and the number (L) of consecutive symbols. Here, the symbol index s can be one of the values ​​0, 1, 2, ..., 13, and L can be one of the values ​​1, 2, ..., 14.

[0424] The terminal may be instructed by the base station to configure one of the symbols within a preset slot. The symbols within the preset slot may be configured in the format of Table 20.

[0425]

[0426]

[0427] According to one embodiment of the present disclosure, the symbol pattern for S slots of the terminal may be determined as follows.

[0428] The terminal can receive information about (the index of a slot, the index of a symbol within the slot, and the type of the symbol) from the base station. The information can include at least one of the index of the slot, the index of the symbol within the slot, and / or the type of the symbol.

[0429] The type of the symbol may include at least one of the following: (i) a symbol capable of downlink reception, (ii) a symbol capable of uplink transmission, (iii) a symbol capable of both downlink reception and uplink transmission, or (iv) a symbol capable of neither downlink reception nor uplink transmission.

[0430] The index of a slot is an index within S slots, and can be one of the values ​​0, 1, 2, ..., S-1.

[0431] The symbol index can be one of the values ​​0, 1, 2, ..., 14.

[0432] The terminal can receive one or more (slot index, symbol index within the slot, symbol type) settings from the base station.

[0433] For symbols in S slots, a terminal may apply a default operation to symbols for which (slot index, symbol index within the slot, symbol type) has not been set. Alternatively, the terminal may apply the following default operation prior to receiving the above setting. Here, the default operation may be determined as at least one of the following.

[0434] - For example, if a symbol is considered to be capable of only downlink reception, the terminal can only perform downlink reception in the symbol. If it is an SBFD symbol, only downlink reception is possible within the DL subband. If it is an SBFD symbol, uplink transmission is not possible within the UL subband.

[0435] - Alternatively, if the symbol is considered to be capable of only uplink transmission, the terminal can only perform uplink transmission in the symbol. If it is an SBFD symbol, only uplink transmission is possible within the UL subband. If it is an SBFD symbol, downlink reception is not possible within the DL subband.

[0436] - Alternatively, the terminal may perform downlink reception and uplink transmission in the symbol, assuming that the symbol allows both downlink reception and uplink transmission. For reference, if the terminal has only half-duplex capability, the terminal may select and perform either downlink reception or uplink transmission. This may be determined based on scheduling information. If it is an SBFD symbol, uplink transmission may be performed within the UL subband, or downlink reception may be performed within the DL subband.

[0437] - Alternatively, the terminal may not perform downlink reception or uplink transmission in the symbol, as it may be regarded as a symbol in which both downlink reception and uplink transmission are impossible. In the case of an SBFD symbol, uplink transmission may not be performed within the UL subband, and downlink reception may not be performed within the DL subband.

[0438] FIG. 13 is a diagram illustrating a symbol pattern of a terminal according to an embodiment of the present disclosure.

[0439] Referring to Figure 13, the terminal sets the subcarrier spacing to 30 kHz with TDD DL / UL settings. ) and P=2.5ms. Therefore, one TDD cycle can contain 5 slots.

[0440] Referring to FIG. 13, the terminal may receive symbol pattern setting information, and the symbol pattern information may include M=4. In addition, S=5 slots may be included as the symbol pattern. That is, the symbol pattern for S slots may be repeated every 4 TDD periods (T=M*P=4*2.5=10ms). In addition, depending on the Offset value, the symbols to which the symbol pattern for S slots is to be applied may be determined. Here, the Offset value may be 5 slots (if the unit of Offset is a slot, the Offset value is 5, if the unit of Offset is a TDD period, the Offset value is 1). Therefore, the symbol pattern of S=5 slots may be applied to S=5 slots, slots 20*n+5, 20*n+6, 20*n+7, 20*n+8, 20*n+9 (n=0,1,...).

[0441] [Method 3-3]

[0442] In one embodiment of the present disclosure, S slots are P*2 included in a period (P [ms]) of TDD UL / DL configuration. u dog It can be the same as slot (S=P*2) u ) where u may be the reference subcarrier spacing of the TDD DL / UL configuration.

[0443] In one embodiment of the present disclosure, when one TDD pattern is set in a period (P [ms]) of TDD UL / DL configuration and when two TDD patterns are set, the terminal can receive different signaling.

[0444] More specifically, when one TDD pattern is set in the cycle (P [ms]) of the TDD UL / DL setting, the terminal sets the S=P*2 u Symbols of the dog slot, W=14*P*2 uAmong the S symbols, the index (s) of the starting symbol to which the symbol pattern is to be applied and the number (L) of consecutive symbols can be indicated. The terminal can apply the symbol pattern to L consecutive symbols starting from the symbol with the index s among the S slots. For example, the terminal can regard L consecutive symbols starting from the symbol with the index s among the S slots as SBFD symbols.

[0445] In one embodiment of the present disclosure, the index of the starting symbol (s) and the number of consecutive symbols (L) can be jointly encoded and signaled using SLIV as follows. The terminal can determine the index of the starting symbol (s) and the number of consecutive symbols (L) based on the SLIV signaling.

[0446]

[0447] More specifically, when one TDD pattern is set in the cycle (P [ms]) of the TDD UL / DL setting, the terminal sets the S=P*2 u Symbols of the dog slot, W=14*P*2 u Among the S symbols, the index (s) of the start symbol to which the symbol pattern is to be applied and the index (E) of the last symbol can be indicated. The terminal can apply the symbol pattern from the symbol with the index s to the symbol with the index E among the S slots. For example, the terminal can regard the symbol with the index s to the symbol with the index E among the S slots as SBFD symbols.

[0448] In one embodiment of the present disclosure, the index (s) of the start symbol and the index (E) of the last symbol may be jointly encoded and signaled as a combinatorial index as follows. The terminal may determine the index (s) of the start symbol and the index (E) of the last symbol based on the signaling. Here, s=k0 and E=k1, or s=k0 and E=k1-1.

[0449]

[0450] More specifically, when two TDD patterns are set in a cycle (P [ms]) of TDD UL / DL configuration, the earlier P1 [ms] in time among the cycles (P [ms]) may be the first TDD pattern, and the later P2 [ms] in time may be the second TDD pattern. P = P1 + P2. The first TDD pattern may include S1 slots. Here, S1 = P1 * 2 u The second TDD pattern may contain S2 slots, where S2 = P2 * 2 u is. And the number of slots S=S1+S2. The terminal is W1=14*P1*2 within the first TDD pattern. u The index of the starting symbol to apply the symbol pattern among the symbols (s1) and the number of consecutive symbols (L1), W2=14*P2*2 within the second TDD pattern u Among the dog's symbols, the index (s2) of the starting symbol to which the symbol pattern is to be applied and the number of consecutive symbols (L2) can be set.

[0451] In one embodiment of the present disclosure, the index of the start symbol (s1, s2) and the number of consecutive symbols (L1, L2) can be jointly encoded and signaled as SLIV1 and SLIV2, respectively, as follows. The terminal can determine the index of the start symbol (s1, s2) and the number of consecutive symbols (L1, L2) based on the SLIV1 and SLIV2 signaling.

[0452]

[0453] In one embodiment of the present disclosure, SLIV1 and SLIV2 may be additionally joint encoded. For example, SLIV_joint may be expressed as SLIV1*X + SLIV2, where X is a value that is 1 greater than the maximum value of SLIV2, such as X=W2*(W2+1) / 2. As another example, SLIV_joint may be expressed as SLIV1 + SLIV2*Y, where Y is a value that is 1 greater than the maximum value of SLIV1, such as Y=W1*(W1+1) / 2. More specifically, when two TDD patterns are set in a period (P [ms]) of a TDD UL / DL configuration, the period (P [ms]) in time, P1 [ms], may be a first TDD pattern, and the period (P [ms]) in time, P2 [ms], may be a second TDD pattern. P=P1+P2. The first TDD pattern may contain S1 slots, where S1 = P1 * 2 u The second TDD pattern may contain S2 slots, where S2 = P2 * 2 u is. And the number of slots S=S1+S2. The terminal is W1=14*P1*2 within the first TDD pattern. u Among the symbols, the index of the start symbol (s1) and the index of the last symbol (E1) to which the symbol pattern is to be applied, W2=14*P2*2 within the second TDD pattern u Among the dog's symbols, the index of the start symbol (s2) and the index of the last symbol (E2) to which the symbol pattern is to be applied can be set.

[0454] In one embodiment of the present disclosure, the indices (s1, s2) of the start symbol and the indices (E1, E2) of the last symbol may be jointly encoded and signaled as a combinatorial index as follows. The terminal may determine the indices (s1, s2) of the start symbol and the indices (E1, E2) of the last symbol based on the signaling. Here, s1=k0, E1=k1, s2=k2, E2=k3, or s1=k0, E1=k1-1, s2=k2, E2=k3-1. It could be.

[0455]

[0456] FIG. 14 is a diagram illustrating a flowchart of a terminal according to an embodiment of the present disclosure.

[0457] Referring to FIG. 14, at step 1400, the terminal may receive TDD DL / UL configuration information from the base station. The TDD DL / UL configuration information may include a reference subcarrier interval (u) and a period (P [ms]).

[0458] At step 1410, the terminal may receive information about a symbol pattern from the base station. The information about the symbol pattern may be received from a higher layer signal of the base station, or may be included in an L1 signal of the base station (a DCI format transmitted via a PDCCH, e.g., a UE-specific DCI format or a group-common DCI format). The information about the symbol pattern may include the symbol pattern of S slots, an M value, and an Offset value. Here, the S, M, and Offset values ​​may satisfy the following conditions:

[0459] - M is the value of one of the divisors of X / P, X=40 or 20 or 10;

[0460] - S is the number of slots included in the TDD DL / UL configuration cycle (P), i.e., P*2u ; and

[0461] - If the unit of offset is slot, the offset value is 0, 1, 2,..., M*P*2 u One of the values ​​-1 (or 0, P*2 u , 2*P*2 u ,..., (M-1)*P*2 u one of the values); or.

[0462] - The unit of offset is TDD DL / UL setting cycle (P), i.e. P*2 u If the unit is slot, the Offset value is 0, 1, 2,...,M-1.

[0463] At step 1420, the terminal can determine the period (T [ms]) to which the symbol pattern is to be applied and the indices of the slots to which the symbol pattern of S slots is to be applied based on the information about the symbol pattern. For example, the period (T [ms]) to which the symbol pattern is to be applied is M*P [ms], and the indices of the slots to which the symbol pattern of S slots is to be applied can be determined as {N, N+1, ..., N+S-1}, where N = (n*M+Offset)*P*2 u , n=0,1,2,... For reference, if the unit of Offset is slot unit, N = n*M*P*2 u +Offset, n=0,1,2,... can be.

[0464] At step 1430, the terminal can determine the symbol type of the symbols based on the symbol pattern. For example, the symbol type may determine that it is an SBFD symbol. For example, the symbol type may determine that it is a symbol capable of downlink reception. The symbol type may determine that it is a symbol capable of uplink transmission. For reference, if the symbol type in the SBFD symbol is determined to be a symbol capable of downlink reception, the terminal can perform downlink reception in the DL subband. If the symbol type in the SBFD symbol is determined to be a symbol capable of uplink transmission, the terminal can perform uplink transmission in the UL subband.

[0465] <Example 2: Method for Determining Transition Guard Symbols>

[0466] In one embodiment of the present disclosure, when a symbol pattern is set, a terminal may require a Transition Guard symbol for transitioning from a downlink symbol to an uplink transmission symbol or from an uplink transmission symbol to a downlink symbol. A method for determining a Transition Guard symbol is disclosed. Transitioning from downlink to uplink or from uplink to downlink in a transition guard period may mean that the terminal does not perform uplink transmission or downlink reception in the transition guard period. In other words, uplink transmission or downlink reception may be skipped in the transition guard period.

[0467] In one embodiment of the present disclosure, a terminal may receive a first upper layer signal from a base station. The first upper layer signal may include a symbol pattern configuration. According to the symbol pattern configuration, the terminal may be configured with symbol patterns. Through the symbol pattern configuration, the terminal may be instructed whether the SBFD symbol is a symbol capable of downlink reception by the terminal (i.e., a downlink-only SBFD symbol) or whether the SBFD symbol is a symbol capable of uplink transmission by the terminal (i.e., an uplink-only SBFD symbol).

[0468] The terminal may receive a second upper layer signal from the base station. The second upper layer signal may include at least one of the following settings (e.g., a first setting, a second setting, etc.).

[0469] As a first setting, the number of symbols included in the Transition Guard symbol (N Guard ) can be set. For example, the number of symbols included in the Transition Guard symbol, N Guard= 0, 1, 2, 3, 4 can be set. The above numbers are just examples and can include other numbers.

[0470] In the second setting, information corresponding to the position of the Transition Guard symbol can be set. The setting may include at least one of the following examples.

[0471] For example, Transition Guard symbols can be located after or before certain symbols, for example, after the last symbol of consecutive downlink-only SBFD symbols, and N Guard Symbols can be included in the Transition Guard symbol. This can be applied when switching from downlink to uplink. For example, N symbols after the last symbol of consecutive uplink-only SBFD symbols Guard Symbols can be included in the Transition Guard symbol. This can be applied when switching from uplink to downlink. For example, N symbols can be included before the first symbol of consecutive downlink-only SBFD symbols. Guard Symbols can be included in the Transition Guard symbol. This can be applied when switching from uplink to downlink. For example, N symbols can be included before the first symbol of consecutive uplink-only SBFD symbols. Guard Symbols can be included in the Transition Guard symbol, which can be applied when switching from downlink to uplink.

[0472] For example, Transition Guard symbols may be located within specific symbols, e.g., from the last symbol of consecutive downlink-only SBFD symbols to the previous N GuardSymbols can be included in the Transition Guard symbol. This can be applied when switching from downlink to uplink. For example, from the last symbol of consecutive uplink-only SBFD symbols to the previous N Guard Symbols can be included in the Transition Guard symbol. This can be applied when switching from uplink to downlink. For example, from the first symbol of consecutive downlink-only SBFD symbols to the following N Guard Symbols can be included in the Transition Guard symbol. This can be applied when switching from uplink to downlink. For example, from the first symbol of consecutive uplink-only SBFD symbols to the following N Guard Symbols can be included in the Transition Guard symbol, which can be applied when switching from downlink to uplink.

[0473] In the first and second settings described above, the terminal is connected to the base station with one N router. Guard can be set. However, this is only an example, and in another embodiment, the terminal can receive multiple N from the base station. Guard can also be set. For example, the terminal may have two N Guard can be set. This is the first symbol number N Guard (1) and the second symbol number N Guard (2) can be expressed as follows. The terminal transmits N symbols starting from the last symbol of the consecutive downlink-only SBFD symbols. Guard (1) Symbols can be included in the Transition Guard symbol. N symbols starting from the last symbol of consecutive uplink-only SBFD symbols. Guard(2) Symbols may be included in the Transition Guard symbol. That is, the first symbol number may be used to determine the Transition Guard symbol when transitioning from downlink symbols to uplink symbols, and the second symbol number may be used to determine the Transition Guard symbol when transitioning from uplink symbols to downlink symbols.

[0474] The number of symbols included in the Transition Guard symbol of the first setting described above (N) Guard ) can be set. This may be the same as the reference subcarrier interval set when configuring TDD DL / UL. Alternatively, the reference subcarrier interval may be a value set separately by the base station. The above value may be different from the reference subcarrier interval set when configuring TDD DL / UL.

[0475] The number of symbols included in the Transition Guard symbol of the first setting described above (N) Guard ) may be a value that can be determined according to the terminal's capabilities (i.e., the terminal's implementation). To this end, the terminal and base station may perform the following process.

[0476] When a terminal initially accesses a cell, the terminal may report its capabilities to the base station. When reporting the capabilities of the terminal, the terminal may report to the base station the minimum value of the number of symbols included in the Transition Guard symbol requested by the terminal. The value may be reported according to the subcarrier interval. For example, the minimum value of the number of symbols included in the first Transition Guard symbol corresponding to the first subcarrier interval (e.g., 15 kHz) and the minimum value of the number of symbols included in the second Transition Guard symbol corresponding to the second subcarrier interval (e.g., 30 kHz) may be reported. As the value, the minimum value of the number of symbols included in the Transition Guard symbol corresponding to one reference subcarrier interval may be reported. Here, one reference subcarrier interval may be determined by the terminal and included in the terminal capability report. Alternatively, a reference subcarrier interval set by the base station when configuring TDD DL / UL may be used as one reference subcarrier interval. In this case, the terminal report may not include information about the reference subcarrier spacing.

[0477] For example, if a base station has multiple N Guard When applying, the terminal can report multiple values.

[0478] The base station can receive from the terminal the minimum value of the number of symbols included in the Transition Guard symbol requested by the terminal. The base station can set the number of symbols included in the Transition Guard symbol to a number that is not less than (greater than or equal to) the minimum value. When the base station sets the number of symbols included in the Transition Guard symbol, the reference subcarrier spacing of the number of symbols can use the subcarrier spacing of the BWP. In other words, the base station can set the number of symbols included in the Transition Guard symbol for each BWP, and the reference subcarrier spacing of the number of symbols included in the Transition Guard symbol can be the subcarrier spacing of the BWP.

[0479] <Example 3: Method for determining SBFD symbols in case of extended CP>

[0480] In one embodiment of the present disclosure, a terminal may receive a symbol pattern of a normal CP length from a base station. However, an extended CP may be set in the terminal's active BWP. In this case, the terminal may determine the type of symbols set as the extended CP from the symbol pattern set as the normal CP.

[0481] FIG. 15 is a diagram illustrating 14 symbols set as regular CPs and 12 symbols set as extended CPs in one slot according to one embodiment of the present disclosure.

[0482] Referring to Figure 15, when set to regular CP, one slot contains 14 symbols. When set to extended CP, one slot contains 12 symbols. Therefore, one symbol set to regular CP can overlap two symbols set to extended CP. Furthermore, two symbols set to regular CP can overlap one symbol set to extended CP.

[0483] In the present disclosure, when two symbols set as an extended CP and a symbol set as a regular CP overlap, a first symbol set as a regular CP is of a first symbol type and a second symbol set as a regular CP is of a second symbol type, and they are different from each other, a method for determining a symbol type of a symbol set as an extended CP is provided.

[0484] FIG. 16 illustrates the symbol types of symbols set to regular CP and symbols set to extended CP based on the TDD DL / UL configuration according to an embodiment of the present disclosure. Table 21 illustrates the symbol types of symbols set to regular CP and symbols set to extended CP based on the TDD DL / UL configuration according to an embodiment of the present disclosure.

[0485] Referring to Table 21 and Fig. 16, if all symbols set to regular CP that overlap with a symbol set to extended CP are DL symbols, the symbol set to extended CP may be a DL symbol. If all symbols set to regular CP that overlap with a symbol set to extended CP are UL symbols, the symbol set to extended CP may be a UL symbol. If at least one symbol among the symbols set to regular CP that overlap with a symbol set to extended CP is an F (flexible) symbol, the symbol set to extended CP may be an F symbol. If symbols of different types are included among the symbols set to regular CP that overlap with a symbol set to extended CP, the symbol set to extended CP may be an F symbol.

[0486] First symbol type set to regular CPSecond symbol type set to regular CPSymbol type of symbol set to extended CPDL symbolDL symbolDL symbolUL symbolUL symbolUL symbolDL symbolF symbolF symbolUL symbolF symbolF symbolF symbolF symbol

[0487] FIG. 17 illustrates a first method for determining symbol types of symbols set to regular CP and symbols set to extended CP based on TDD DL / UL configuration and SBFD configuration according to an embodiment of the present disclosure. Table 22 shows symbol types determined according to the first method for determining symbol types of symbols set to regular CP and symbols set to extended CP according to an embodiment of the present disclosure.

[0488] In a first method, if at least one symbol among the symbols set to regular CP that overlaps with a symbol set to extended CP is an SBFD symbol, the symbol set to extended CP may be an SBFD symbol. Referring to FIG. 17 and Table 22, for example, if the first symbol type set to regular CP is an SBFD symbol, the symbol set to extended CP may be an SBFD symbol regardless of the second symbol type set to regular CP. According to the first method, among the symbol types of the symbols set to regular CP, the SBFD symbol may be prioritized and determined as the symbol type of the extended CP.

[0489] First symbol type set to regular CPSecond symbol type set to regular CPSymbol type of symbol set to extended CPSBFD symbolDL symbolSBFD symbolSBFD symbolF symbolSBFD symbolSBFD symbolUL symbolSBFD symbolSBFD symbolSBFD symbol

[0490] FIG. 18 illustrates a second method for determining the symbol types of symbols set to regular CP and symbols set to extended CP based on TDD DL / UL configuration and SBFD configuration according to an embodiment of the present disclosure. Table 23 shows the symbol types determined according to the second method for determining the symbol types of symbols set to regular CP and symbols set to extended CP according to an embodiment of the present disclosure.

[0491] In a second method, if at least one symbol among the symbols set to regular CP that overlaps with a symbol set to extended CP is an SBFD symbol, the symbol set to extended CP may be an SBFD symbol. Exceptionally, if at least one symbol among the symbols set to regular CP that overlaps with a symbol set to extended CP is an UL symbol, the symbol set to extended CP may be a non-SBFD symbol. According to the second method, except when at least one symbol type among the symbols set to regular CP is a UL symbol, an SBFD symbol among the symbol types of the symbols set to regular CP may be prioritized and determined as the symbol type of the extended CP. When at least one symbol type among the symbols set to regular CP is a UL symbol, the symbol type of the extended CP may be determined as a non-SBFD symbol (e.g., an F symbol).

[0492] Referring to FIG. 18 and Table 23, for example, if the first symbol type set to regular CP is an SBFD symbol and the second symbol type set to regular CP is a symbol other than an UL symbol, the symbol set to extended CP may be an SBFD symbol. If the first symbol type set to regular CP is an SBFD symbol and the second symbol type set to regular CP is a UL symbol, the symbol set to extended CP may be a non-SBFD symbol. Here, the non-SBFD symbol may be determined to be an F symbol.

[0493] First symbol type set to regular CPSecond symbol type set to regular CPSymbol type of symbol set to extended CPSBFD symbolDL symbolSBFD symbolSBFD symbolF symbolSBFD symbolSBFD symbolUL symbolNon-SBFD symbol (F symbol)SBFD symbolSBFD symbolSBFD symbol

[0494] FIG. 19 illustrates a third method for determining the symbol types of symbols set to regular CP and symbols set to extended CP based on TDD DL / UL configuration and SBFD configuration according to an embodiment of the present disclosure. Table 24 shows the symbol types determined according to the third method for determining the symbol types of symbols set to regular CP and symbols set to extended CP according to an embodiment of the present disclosure.

[0495] In a third method, if at least one symbol among the symbols set to regular CP that overlaps with a symbol set to extended CP is an SBFD symbol, the symbol set to extended CP may be an SBFD symbol. Exceptionally, if at least one symbol among the symbols set to regular CP that overlaps with a symbol set to extended CP is an UL symbol or an F symbol, the symbol set to extended CP may be a non-SBFD symbol. According to the third method, except when at least one symbol type of the symbols set to regular CP is a UL symbol or an F symbol, an SBFD symbol among the symbol types of the symbols set to regular CP may be prioritized and determined as the symbol type of the extended CP. When at least one symbol type of the symbols set to regular CP is a UL symbol or an F symbol, the symbol type of the extended CP may be determined as a non-SBFD symbol (e.g., an F symbol).

[0496] Referring to FIG. 19 and Table 24, for example, if the first symbol type set to regular CP is an SBFD symbol and the second symbol type set to regular CP is a symbol other than a UL symbol or an F symbol, the symbol set to extended CP may be an SBFD symbol. If the first symbol type set to regular CP is an SBFD symbol and the second symbol type set to regular CP is a UL symbol or an F symbol, the symbol set to extended CP may be a non-SBFD symbol. Here, the non-SBFD symbol may be determined to be an F symbol.

[0497] First symbol type set to regular CPSecond symbol type set to regular CPSymbol type of symbol set to extended CPSBFD symbolDL symbolSBFD symbolSBFD symbolF symbolF symbolSBFD symbolUL symbolUL symbolSBFD symbolSBFD symbol

[0498] FIG. 20 illustrates a fourth method for determining the symbol types of symbols set to regular CP and symbols set to extended CP based on TDD DL / UL configuration and SBFD configuration according to an embodiment of the present disclosure. Table 25 shows the symbol types determined according to the fourth method for determining the symbol types of symbols set to regular CP and symbols set to extended CP according to an embodiment of the present disclosure.

[0499] In a fourth method, if all symbols set to regular CP that overlap with a symbol set to extended CP are SBFD symbols, the symbol set to extended CP may be an SBFD symbol. Referring to FIG. 20 and Table 25, for example, if the first symbol type set to regular CP is an SBFD symbol and the second symbol type set to regular CP is an SBFD symbol, the symbol set to extended CP may be an SBFD symbol. If at least one symbol among the symbols set to regular CP that overlap with a symbol set to extended CP is a non-SBFD symbol (a DL symbol, an F symbol, or a UL symbol), the terminal may determine the symbol set to extended CP as a non-SBFD symbol.

[0500] The above non-SBFD symbol can have its symbol type determined as follows.

[0501] Before being determined as an SBFD symbol, the direction of a non-SBFD symbol can be determined based on the type of symbol (DL symbol, F symbol, UL symbol) set as a regular CP, depending on the TDD DL / UL setting.

[0502] - For example, before being determined as an SBFD symbol, if the first symbol type set to regular CP is a DL symbol and the second symbol type set to regular CP is a DL symbol, according to the TDD DL / UL setting, the Non-SBFD symbol can be determined as a DL symbol.

[0503] - For example, before being determined as an SBFD symbol, if the first symbol type set as a regular CP is a DL symbol and the second symbol type set as a regular CP is an F symbol, according to the TDD DL / UL setting, the Non-SBFD symbol can be determined as an F symbol.

[0504] - For example, before being determined as an SBFD symbol, if the first symbol type set as a regular CP is an F symbol and the second symbol type set as a regular CP is a DL symbol, according to the TDD DL / UL setting, the Non-SBFD symbol can be determined as an F symbol.

[0505] - For example, before being determined as an SBFD symbol, if the first symbol type set as a regular CP is an F symbol and the second symbol type set as a regular CP is an F symbol, depending on the TDD DL / UL setting, the Non-SBFD symbol can be determined as an F symbol.

[0506] First symbol type set to regular CPSecond symbol type set to regular CPSymbol type of symbol set to extended CPSBFD symbolDL symbolNon-SBFD symbolSBFD symbolF symbolNon-SBFD symbolSBFD symbolUL symbolNon-SBFD symbolSBFD symbolSBFD symbol

[0507] FIG. 21 illustrates a flowchart for determining a symbol type of a symbol set as an extended CP by a terminal according to an embodiment of the present disclosure.

[0508] Referring to FIG. 21, in operation 2110, the terminal may receive TDD UL / DL symbol pattern configuration information for a regular CP and SBFD symbol pattern configuration information for a regular CP from the base station. The information may be included in the upper layer information (e.g., SIB, or RRC) of the base station.

[0509] In operation 2120, the terminal can determine one Active DL BWP and one Active UL BWP. In TDD operation (unpaired spectrum), DL BWP and UL BWP with the same index can be activated. The Active DL BWP and Active UL BWP can have the same subcarrier spacing and CP type. The terminal can determine whether a regular CP or an extended CP is set for the Active DL BWP and Active UL BWP.

[0510] In operation 2130, if a regular CP is set for Active DL BWP and Active UL BWP, one slot can contain 14 symbols. Then, the terminal can determine the symbol type by applying a symbol pattern based on the configuration information.

[0511] In operation 2140, if extended CP is configured for Active DL BWP and Active UL BWP, one slot can contain 12 symbols. Then, the terminal can determine the symbol type of the regular CP symbols by applying the TDD and SBFD symbol patterns for the regular CP symbols (14 symbols in one slot) based on the configuration information. Then, the terminal can determine the symbol type of the extended CP symbols based on the symbol patterns of the regular CP symbols that overlap with the extended CP symbols.

[0512] In operation 2150, the terminal can perform terminal transmission and reception according to a set symbol pattern.

[0513] <Example 4: Setting and Using Symbol Patterns for Multiple TRPs>

[0514] In one embodiment of the present disclosure, a terminal may be configured to transmit and receive data through multiple transmission and reception points (TRPs) from a base station. For convenience, the following description will assume that the terminal is configured to transmit and receive data through two TRPs. However, this disclosure can also be applied to terminals that transmit and receive data through three or more TRPs.

[0515] FIG. 22 is a diagram showing a terminal transmitting and receiving from a first TRP (i.e., TRP 1) and a second TRP (i.e., TRP 2) according to one embodiment of the present disclosure.

[0516] The terminal can receive symbol patterns to be applied to each TRP from the base station. That is, the terminal can receive a first symbol pattern to be applied to the first TRP from the base station, and a second symbol pattern to be applied to the second TRP from the base station. The first and second symbol patterns set by the terminal may be the same or different.

[0517] Referring to FIG. 22, the terminal may be configured with a first TDD pattern as a first symbol pattern. Here, the first TDD pattern (2200) may be DDDSU (D is a slot in which all 14 symbols of the slot are downlink symbols, U is a slot in which all 14 symbols of the slot are uplink symbols, and S is a symbol in which all 14 symbols of the slot are not downlink symbols or not all uplink symbols).

[0518] The terminal may be configured with a second TDD pattern using a second symbol pattern. Here, the second TDD pattern (2210) may be DDSUU. Here, the first TDD pattern and the second TDD pattern may be different patterns.

[0519] Alternatively, the terminal may be configured with a first TDD pattern and an offset value as a second symbol pattern. Here, the second TRP may use the same first TDD pattern (2200) as the first TRP, but an offset value may be applied. The second symbol pattern may be a pattern (2211) in which the first TDD pattern is cyclically shifted according to the offset value. For example, the one-slot cyclically rotated pattern (2211) may be UDDDS.

[0520] Information about the SBFD symbol may be added to the second symbol pattern. That is, a pattern (2212) with an SBFD setting added may be applied to the second symbol pattern for the second TRP. Note that information about the SBFD symbol may also be added to the first symbol pattern for the first TRP. In this case, information about the SBFD symbol of the first TRP may be different from information about the SBFD symbol of the second TRP.

[0521] The terminal can determine from which TRP a signal is transmitted / received based on the scheduling information of the base station. The terminal can determine from which TRP a signal is transmitted / received based on the index of the CORESET (or the index of the CORESET Pool associated with the index) for which the scheduling information is scheduled or the transmission configuration index (TCI). Other methods may also be used for determination.

[0522] When the terminal determines a TRP to be transmitted and received based on scheduling information, the terminal can determine whether transmission and reception of the scheduled channel or signal is possible based on the symbol format setting of the corresponding TRP. For example, when uplink transmission is scheduled in the first TRP, the terminal can determine whether the scheduled uplink transmission is possible based on the first symbol pattern of the first TRP, for example, DDDSU (2200). If the uplink transmission is scheduled in the preceding three slots (slots corresponding to DDD of DDDSU), the terminal may not perform the uplink transmission. When uplink transmission is scheduled in the second TRP, the terminal can determine whether the scheduled uplink transmission is possible based on the second symbol pattern of the second TRP, for example, UDDDS (2211). That is, if the uplink transmission is scheduled in the first slot, the terminal can perform the uplink transmission.

[0523] If a terminal is scheduled to transmit and receive simultaneously from a first TRP and a second TRP, the terminal can determine whether transmission and reception are possible by considering both the first symbol pattern of the first TRP and the second symbol pattern of the second TRP. For example, if the first symbol pattern of the first TRP is DDDSU (2200), the second symbol pattern of the second TRP is DDSUU (2210), and the terminal is scheduled for uplink transmission with a length of 14 symbols in the fourth slot, the terminal may not perform uplink transmission because the second symbol pattern of the second TRP is U, but the first symbol pattern of the first TRP is not U. If the terminal is scheduled for uplink transmission with a length of 14 symbols in the fifth slot, the terminal can perform uplink transmission because the first symbol pattern of the first TRP and the second symbol pattern of the second TRP are both U.

[0524] FIG. 23 is a flowchart illustrating terminal operations for multiple TRPs according to one embodiment of the present disclosure.

[0525] Referring to FIG. 23, at step 2300, the terminal can receive information about the first symbol pattern of the first TRP and the second symbol pattern of the second TRP from the base station.

[0526] At step 2310, based on the scheduling information, the terminal can determine whether transmission / reception is from the first TRP, transmission / reception is from the second TRP, or transmission / reception is from the first TRP and the second TRP simultaneously. This can be determined based on the index of the CORSET corresponding to the scheduling information, the index of the CORESET Pool, or the TCI value.

[0527] At step 2320, if transmission / reception is from the first TRP, the terminal can determine whether transmission / reception is possible based on the first symbol pattern of the first TRP. If transmission / reception is from the second TRP, the terminal can determine whether transmission / reception is possible based on the second symbol pattern of the second TRP. If transmission / reception is from the first TRP and the second TRP simultaneously, the terminal can determine whether transmission / reception is possible based on the first symbol pattern of the first TRP and the second symbol pattern of the second TRP.

[0528] At step 2330, depending on whether transmission / reception is possible, the terminal can perform scheduled uplink transmission or downlink reception.

[0529] <Example 5: SBFD Symbol Determination Method>

[0530] As an embodiment of the present disclosure, a terminal may provide a method for determining an SBFD symbol.

[0531] More specifically, the terminal may receive multiple configuration information from the base station via a higher layer signal. For example, the multiple configuration information (e.g., first higher layer configuration information, second higher layer configuration information, third higher layer configuration information) may include the following:

[0532] As the first upper layer configuration information, TDD DL / UL configuration information may be included. The TDD DL / UL configuration information may include up to two TDD patterns for the TDD DL / UL configuration. If the period of the TDD DL / UL configuration is P (ms), the first TDD pattern may include a symbol type from the base station's perspective for the earlier P1 (ms) among the P (ms), and the second TDD pattern may include a symbol type from the base station's perspective for the later P2 (ms) among the P (ms). That is, P may be represented as P1+P2. Each TDD pattern may include downlink symbols, uplink symbols, or flexible symbols. The TDD DL / UL configuration may be a configuration commonly applied to a cell. The TDD DL / UL configuration may be included in SIB1.

[0533] Second upper layer configuration information may include SSB configuration information. The SSB configuration information may include an SSB period. For example, the SSB period may have one of the following values: 5 ms, 10 ms, 20 ms, 40 ms, 80 ms, and 160 ms. If the terminal does not receive the SSB configuration information (for example, in the case of an initial cell access terminal), the terminal may receive the SSB by assuming the SSB period to be a specific value (for example, 20 ms). An SSB block consists of four consecutive symbols, and symbols included in an SSB block may be called an SSB symbol. The position of the first symbol of an SSB block within a 5 ms long half frame may be as shown in Table 26. Here, index 0 may correspond to the first symbol of the first slot of the half frame. The terminal may not expect the SSB symbols determined according to the above configuration to be uplink symbols according to the TDD DL / UL configuration. That is, the terminal can expect the SSB symbols to be downlink symbols or flexible symbols according to the TDD DL / UL configuration. The SSB configuration may be a configuration commonly applied to the cell. The SSB configuration may be included in SIB1. The SSB configuration may be a cell-defining SSB configuration. The SSB configuration may be a configuration for SSBs including PBCH.

[0534]

[0535] Third upper layer configuration information may include SBFD configuration information. The SBFD configuration information may configure SBFD symbols from downlink symbols or flexible symbols configured in the TDD DL / UL configuration. When the TDD DL / UL configuration has one TDD pattern, the SBFD configuration may include an index for a start symbol and an index for a last symbol (or an index for a start symbol and the number of consecutive symbols) among the symbols in the one TDD pattern. In addition, the period of the SBFD configuration may be the same as the period (P) of the TDD DL / UL configuration. That is, the SBFD symbols determined by the SBFD configuration may be repeated for each TDD pattern.

[0536] For example, when the TDD DL / UL configuration has two TDD patterns, the SBFD configuration may include an index for a start symbol and an index for a last symbol (or an index for a start symbol and the number of consecutive symbols) among symbols in the first TDD pattern and an index for a start symbol and an index for a last symbol (or an index for a start symbol and the number of consecutive symbols) among symbols in the second TDD pattern. The period of the SBFD configuration may be the same as the period of the TDD DL / UL configuration (P=P1+P2). Here, P1 may be a period of the first TDD pattern, and P2 may be a period of the second TDD pattern.

[0537] Downlink and uplink subbands can be configured for the frequency carrier corresponding to the SBFD symbol determined according to the SBFD setting. A terminal can perform downlink reception in the downlink subband but cannot perform uplink transmission, and can perform uplink transmission in the uplink subband but cannot perform downlink reception.

[0538] Depending on the SBFD configuration, a symbol other than an SBFD symbol may be called a non-SBFD symbol. A non-SBFD symbol may include a downlink symbol, a flexible symbol, or an uplink symbol, depending on the TDD DL / UL configuration. In a downlink symbol, a terminal can perform downlink reception in all frequency bands, but cannot perform uplink transmission, and in an uplink symbol, a terminal can perform uplink transmission in all frequency bands, but cannot perform downlink reception. In a flexible symbol, a terminal can perform either downlink reception or uplink transmission.

[0539] The SSB symbol and the SBFD symbol determined by the terminal may overlap. In this case, the terminal must receive the SSB in the SBFD symbol. According to the SBFD operation, the terminal still supports only the half-duplex mode, so the terminal cannot perform uplink transmission while receiving the SSB. The terminal can receive another downlink signal or channel while receiving the SSB in the SBFD symbol. However, since the frequency resources for receiving the downlink in the SBFD symbol are limited to the SBFD downlink subband, the downlink cannot be received in the frequency resources (e.g., the uplink subband and the guard band) excluding the downlink subband. Therefore, the frequency resources excluding the downlink subband may be unused and wasted.

[0540] Methods for solving the above problems are specifically described.

[0541] In one method of the present disclosure, when an SBFD symbol and an SSB symbol overlap, the terminal can change the SBFD symbol to a non-SBFD symbol. A non-SBFD symbol is a symbol that is determined as a downlink symbol, a flexible symbol, or an uplink symbol according to a TDD DL / UL configuration. That is, the terminal determines the symbol as an SBFD symbol according to the SBFD configuration, but can ignore the SBFD configuration (assuming that the SBFD configuration is not provided for the symbol) and determine it as a downlink symbol, a flexible symbol, or an uplink symbol.

[0542] In one method of the present disclosure, when an SBFD symbol and an SSB symbol overlap, the terminal can change the SBFD symbol to a downlink symbol. That is, although the symbol type (e.g., downlink symbol, flexible symbol, or uplink symbol) is set according to the TDD DL / UL setting, the symbol can be determined as a downlink symbol, ignoring the TDD DL / UL setting.

[0543] In one method of the present disclosure, a terminal can be configured through a higher layer signal to use a symbol overlapping with SSB as an SBFD symbol or a non-SBFD symbol.

[0544] In one embodiment, the terminal may receive a dedicated TDD configuration via an RRC signal. Here, the dedicated TDD configuration may indicate a flexible symbol indicated in the cell-common TDD DL / UL configuration as a downlink symbol or an uplink symbol. Through the dedicated TDD configuration, an SBFD symbol overlapping with an SSB symbol may be indicated as a downlink symbol. In this case, the terminal may regard the SBFD symbol as a downlink symbol according to the dedicated TDD configuration. That is, the terminal may determine the symbol as an SBFD symbol according to the SBFD configuration, but may ignore the SBFD configuration and regard it as a downlink symbol.

[0545] A Dedicated TDD configuration may include at least one of the following information (i), (ii), or (iii):

[0546] (i) the index of the slot, (ii) whether all symbols contained in the slot are downlink or uplink, or (iii) the number of downlink symbols and the number of uplink symbols.

[0547] Here, the slot index may be the index of slots included in the period (P) of the cell common TDD DL / UL configuration. Here, the index of the first slot of the period of the cell common TDD DL / UL configuration may be 0.

[0548] Here, if the number of downlink symbols included in the slot is indicated, the symbols corresponding to the number in chronological order starting from the first symbol of the slot can be determined as downlink. Here, if the number of uplink symbols included in the slot is indicated, the symbols corresponding to the number in chronological order starting from the last symbol of the slot can be determined as uplink symbols.

[0549] For SBFD symbols that do not overlap with SSB, if they are set as downlink symbols or uplink symbols according to dedicated TDD settings, the terminal can perform one of the following actions.

[0550] - When set to a downlink symbol, the terminal may only be able to receive downlink through the downlink subband in the SBFD symbol. That is, the terminal may not transmit uplink through the uplink subband in the SBFD symbol. If transmission of an uplink channel or signal is indicated in the SBFD symbol, the terminal may drop or skip without transmitting the uplink channel or signal.

[0551] - When set to an uplink symbol, the terminal may only be able to transmit uplink through the uplink subband in the SBFD symbol. That is, the terminal may not receive downlink through the downlink subband in the SBFD symbol. If reception of a downlink channel or signal is indicated in the SBFD symbol, the terminal may drop or skip without receiving the downlink channel or signal.

[0552] Alternatively, in the case of an SBFD symbol overlapping with an SSB, if a downlink symbol is set according to a dedicated TDD setting, the terminal may regard the SBFD symbol as a downlink symbol and receive a downlink channel or signal in all frequency bands of the symbol.

[0553] In one embodiment, a terminal may obtain upper layer configuration information for SSB. The upper layer configuration information may include information indicating whether an SBFD symbol overlapping with an SSB symbol corresponding to each SSB index is to be used as an SBFD symbol or a non-SBFD symbol. Based on the upper layer configuration information, the terminal may determine whether an SBFD symbol overlapping with an SSB symbol is to be used as an SBFD symbol.

[0554] For example, the upper layer configuration information corresponding to the SSB index may be configured as a bitmap. Each bit may correspond to one SSB index. The length of the bitmap may be equal to the number of SSBs in the half frame. The indexes of the SSBs in the half frame may be sequentially numbered from 0 in time order. If the value of the bit corresponding to the first SSB index is the first value (e.g., '0'), the terminal may regard the SBFD symbol overlapping with the SSB symbol of the first SSB index as the SBFD symbol. That is, the terminal may perform downlink reception only in the downlink subband in the SBFD symbol. If the value of the bit corresponding to the second SSB index is the second value (e.g., '1'), the terminal may regard the SBFD symbol overlapping with the SSB symbol of the second SSB index as a non-SBFD symbol. That is, since the terminal regards the SBFD symbol as a non-SBFD symbol, it can receive downlink in all frequency bands. According to this example, different terminal operations can be performed for each SSB index.

[0555] For another example, the upper layer configuration information may include SSB indices. The terminal may regard an SBFD symbol that overlaps with an SSB symbol corresponding to the SSB indices included in the upper layer configuration information as a non-SBFD symbol. If the SSB index of the SSB symbol that overlaps with the SBFD is not included in the upper layer configuration information, the terminal may regard the SBFD symbol that overlaps with the SSB symbol as an SBFD symbol.

[0556] For another example, the upper layer configuration information may include SSB indices. If the SSB index of an SSB symbol overlapping with an SBFD is not included in the upper layer configuration information, the terminal may regard the SBFD symbol overlapping with the SSB symbol as a non-SBFD symbol. The terminal may regard the SBFD symbol overlapping with the SSB symbol corresponding to the SSB indices included in the upper layer configuration information as an SBFD symbol.

[0557] In the above-described embodiment, methods for changing an SBFD symbol overlapping with an SSB symbol into a non-SBFD symbol have been described. In the above-described embodiment, an SBFD symbol overlapping with an SSB symbol can be determined by at least one of the following methods.

[0558] In the first method, if the OFDM symbol corresponding to the SSB and the OFDM symbol corresponding to the SBFD symbol are the same, the terminal can determine that the SSB symbol and the SBFD symbol overlap. That is, according to the first method, the above-described operation can be applied to the SBFD symbols that overlap the OFDM symbol corresponding to the SSB.

[0559] - In method 1-1, when two SSB blocks are included in one slot, if an SBFD symbol is set in a symbol between the two SSB blocks, the terminal can also determine that the SBFD symbols are SBFD symbols that overlap with the SSB symbols.

[0560] - In method 1-2, when an SSB block is included in one slot, when the index of the start symbol of the SSB block in the slot is 2, and the symbol whose symbol index is 0 or 1 (the symbol before the SSB block in the slot) is an SBFD symbol, the terminal can determine that the SBFD symbol overlaps with the SSB symbol.

[0561] - In method 1-3, when an SSB block is included in one slot, the SBFD symbol included between the first symbol in the slot and the last SSB symbol in the slot can be determined to overlap with the SSB symbol.

[0562] - In method 1-4, when an SSB block is included in one slot, and the index of the last symbol of the SSB block in the slot is 11, if the symbol whose symbol index is 12 or 13 (the symbol after the SSB block in the slot) is an SBFD symbol, the terminal can determine that the SBFD symbol overlaps with the SSB symbol.

[0563] - In method 1-5, when an SSB block is included in one slot, the SBFD symbol included between the first SSB symbol in the slot and the last symbol of the slot can be determined to overlap with the SSB symbol.

[0564] - In method 1-6, when an SSB is included in a TDD pattern, the terminal can determine that the SBFD symbols included between the first symbol in the TDD pattern and the last symbol of the SSB overlap with the SSB symbol. Here, the SSB may be the last SSB in time order in the TDD pattern.

[0565] - In method 1-7, when an SSB is included in a TDD pattern, the terminal can determine that the SBFD symbols included between the first symbol of the SSB and the last symbol in the TDD pattern overlap with the SSB symbol. Here, the SSB may be the earliest SSB in time order in the TDD pattern.

[0566] In a second method, the terminal can determine that the SSB symbol and the SBFD symbol overlap with respect to the SBFD symbols in the slot including the SSB. That is, according to the second method, the above-described operation can be applied to the SBFD symbols in the slot including the SSB.

[0567] - In method 2-1, when a slot including an SSB is included in a TDD pattern, it can be determined that the SBFD symbols included in the section from the first slot in the TDD pattern to the slot including the SSB overlap with the SSB symbol. Here, the SSB may be the last SSB in time order in the TDD pattern.

[0568] - In method 2-2, when a slot including an SSB is included in a TDD pattern, it can be determined that the SBFD symbols included from the slot including the SSB to the last slot in the TDD pattern overlap with the SSB symbol. Here, the SSB may be the earliest SSB in time order in the TDD pattern.

[0569] In a third method, the terminal can determine that the SSB symbol and the SBFD symbol overlap with respect to the SBFD symbols in the TDD pattern including the SSB. That is, according to the third method, the above-described operation can be applied to the SBFD symbols in the TDD pattern including the SSB.

[0570] In a fourth method, the terminal can determine that an SSB symbol and an SBFD symbol overlap with respect to SBFD symbols within a TDD period (including two TDD patterns) that includes SSB. That is, according to the fourth method, the above-described operation can be applied to SBFD symbols within a TDD period (including two TDD patterns) that includes SSB.

[0571] The above-described SSB may be a Cell-defining (CD) SSB. That is, the terminal may perform the first to fourth methods described above based on the CD SSB. However, the terminal may not perform the first to fourth methods described above on a non-cell defining (NCD) SSB. That is, even if the NCD (non-cell defining) SSB symbol and the SBFD symbol overlap, the terminal may regard the symbol as an SBFD symbol and receive a downlink signal in a downlink subband. Here, the CD SSB may be an SSB determined according to SSB information included in SIB1. The terminal may obtain a physical cell identity and cell information through the CD SSB. The CD SSB may be an SSB including a PBCH.

[0572] FIG. 24 illustrates a method of changing some of the SBFD symbols into non-SBFD symbols when the OFDM symbols corresponding to SSB and the SBFD symbols overlap according to one embodiment of the present disclosure.

[0573] Figure 24 is based on the third method described above. That is, the terminal can determine that the SSB symbol and the SBFD symbol overlap with respect to the SBFD symbols in the TDD pattern including the SSB.

[0574] Referring to FIG. 24, SSB may be included in the first TDD pattern but not in the second TDD pattern. The terminal may determine an SBFD symbol based on a higher layer signal. The terminal may determine SBFD symbols in the first TDD pattern and the second TDD pattern. The terminal may change SBFD symbols in the first TDD pattern including SSB into non-SBFD symbols. That is, SBFD symbols in the first TDD pattern including SSB may be changed into downlink symbols. The terminal may receive a downlink channel or signal in all frequency bands from the symbols changed into non-SBFD symbols (e.g., downlink symbols). SBFD symbols in the second TDD pattern that do not include SSB may still be regarded as SBFD symbols. The terminal may receive a downlink channel or signal in a downlink subband from the SBFD symbols in the second TDD pattern, and may receive an uplink channel or signal in an uplink subband.

[0575] FIG. 25 illustrates a method of changing some of the SBFD symbols into non-SBFD symbols when OFDM symbols corresponding to SSB and SBFD symbols overlap according to an embodiment of the present disclosure.

[0576] Fig. 25 is based on the second method described above. That is, it can be determined that the SSB symbol and the SBFD symbol overlap with respect to the SBFD symbols in the slot including the SSB.

[0577] Referring to FIG. 25, an SSB may be included in a specific slot (2500). The terminal may determine an SBFD symbol based on a higher layer signal. The terminal may determine SBFD symbols included in a slot (2500) including an SSB. The terminal may change the SBFD symbols included in the slot (2500) including the SSB to non-SBFD symbols. That is, the SBFD symbols included in the slot (2500) including the SSB may be changed to downlink symbols. The terminal may receive a downlink channel or signal in all frequency bands from the symbols changed to non-SBFD symbols (e.g., downlink symbols). SBFD symbols included in slots not including an SSB may still be regarded as SBFD symbols. The terminal may receive a downlink channel or signal in a downlink subband from the SBFD symbols, and may receive an uplink channel or signal in an uplink subband.

[0578] FIG. 26 illustrates a method of changing some of the SBFD symbols into non-SBFD symbols when OFDM symbols corresponding to SSB and SBFD symbols overlap according to one embodiment of the present disclosure.

[0579] Figure 26 is based on the aforementioned method 2-1. When a slot containing an SSB is included in a TDD pattern, the terminal can determine that the SBFD symbols included in the section from the first slot in the TDD pattern to the slot containing the SSB overlap with the SSB symbol. Here, the SSB may be the last SSB in chronological order in the TDD pattern.

[0580] Referring to FIG. 26, SSB may be included in a specific slot (2600). The terminal may determine an SBFD symbol based on a higher layer signal. The terminal may determine SBFD symbols included in slots (2600) containing SSB from the first slot in the TDD pattern. The terminal may change the SBFD symbols to non-SBFD symbols. That is, the terminal may change the SBFD symbols included from the first slot in the TDD pattern to slots (2600) containing SSB into downlink symbols. The terminal may receive a downlink channel or signal in all frequency bands from the symbols changed to non-SBFD symbols (e.g., downlink symbols). SBFD symbols included in slots after the slot (2600) containing SSB may still be regarded as SBFD symbols. The terminal may receive a downlink channel or signal in a downlink subband from the SBFD symbols, and may receive an uplink channel or signal in an uplink subband.

[0581] FIG. 27 illustrates a method of changing some of the SBFD symbols into non-SBFD symbols when the OFDM symbols corresponding to SSB and the SBFD symbols overlap according to one embodiment of the present disclosure.

[0582] Figure 27 is based on the method 1-6 described above. If the OFDM symbol corresponding to the SSB and the OFDM symbol corresponding to the SBFD symbol are the same, the terminal can determine that the SSB symbol and the SBFD symbol overlap. If the SSB is included in the TDD pattern, the terminal can determine that the SBFD symbols included between the first symbol in the TDD pattern and the last symbol of the SSB overlap with the SSB symbol. Here, the SSB may be the last SSB in time order in the TDD pattern.

[0583] Referring to FIG. 27, a terminal can determine an SBFD symbol based on a higher layer signal. The terminal can determine SBFD symbols included from the first symbol in the TDD pattern to the last symbol in time of SSB. The terminal can change the SBFD symbols included from the first symbol in the TDD pattern to the last symbol in time of SSB into non-SBFD symbols. That is, the terminal can change the SBFD symbols included from the first symbol in the TDD pattern to the last symbol in time of SSB into downlink symbols. The terminal can receive a downlink channel or signal in all frequency bands from the symbols changed to non-SBFD symbols (e.g., downlink symbols). SBFD symbols included in symbols that do not include SSB can still be regarded as SBFD symbols. The terminal can receive a downlink channel or signal in a downlink subband from the SBFD symbols, and can receive an uplink channel or signal in an uplink subband.

[0584] According to one embodiment of the present disclosure, the terminal can perform the above-described operation only when the conditions described below are satisfied.

[0585] In one embodiment, the terminal may receive upper layer information from the base station indicating whether to perform the above-described operation. Based on the upper layer information, the terminal may determine whether to change or not to change an SBFD symbol that overlaps with an SSB symbol into a non-SBFD symbol.

[0586] For example, the upper layer information may be composed of 1 bit, and if the value is a first value (e.g., '0'), the terminal may perform a change application of an SBFD symbol overlapping with an SSB symbol to a non-SBFD symbol. If the value is a second value (e.g., '1'), the terminal may not perform a change application of an SBFD symbol overlapping with an SSB symbol to a non-SBFD symbol.

[0587] Alternatively, if the above-mentioned upper layer information is set, the terminal may perform application of changing an SBFD symbol overlapping with an SSB symbol to a non-SBFD symbol. If the above-mentioned upper layer information is not set, the terminal may not perform application of changing an SBFD symbol overlapping with an SSB symbol to a non-SBFD symbol.

[0588] As an example, the terminal may determine whether to perform the above-described operation based on the number of transient points.

[0589] For example, the terminal can determine whether to perform the above-described operation based on the number of transient points within the TDD pattern. Here, a transient point may mean a boundary between an SBFD symbol and a non-SBFD symbol (e.g., a non-SBFD symbol is located after an SBFD symbol, or an SBFD symbol is located after a non-SBFD symbol). The terminal can receive a configuration of the maximum number of transient points within the TDD pattern from the base station. Alternatively, the terminal can assume a maximum of two transient points within the TDD pattern. Accordingly, according to the above-described embodiment, the number of transient points can be determined based on the determined SBFD symbols (i.e., after converting an SBFD symbol overlapping with an SSB symbol into a non-SBFD symbol). If the number of transient points exceeds the maximum value (e.g., 2), the terminal may not convert an SBFD symbol overlapping with an SSB symbol into a non-SBFD symbol. If the number of transient points is less than or equal to the maximum value (e.g., 2), the terminal can change the SBFD symbol overlapping with the SSB symbol to a non-SBFD symbol. That is, only when the condition of the number of transient points is satisfied, the terminal can change the SBFD symbol overlapping with the SSB symbol to a non-SBFD symbol.

[0590] In one embodiment, the terminal may determine whether to perform the above-described operation based on the SSB period. For example, if the SSB period is set to a value smaller than a certain value, the terminal may perform application of changing the SBFD symbol overlapping with the SSB symbol to a non-SBFD symbol. If the SSB period is set to a value equal to or larger than the certain value, the terminal may not perform application of changing the SBFD symbol overlapping with the SSB symbol to a non-SBFD symbol.

[0591] For example, a predetermined value of the SSB period may be 20 ms. That is, when the SSB period is 5 ms or 10 ms, the terminal may perform a change application of an SBFD symbol that overlaps with an SSB symbol to a non-SBFD symbol.

[0592] As another example, the constant value of the SSB period may be 10 ms. That is, when the SSB period is 5 ms, the terminal may perform a change application of SBFD symbols overlapping with SSB symbols to non-SBFD symbols.

[0593] This is because when the SSB period is small, SSB blocks and SBFD symbols may overlap more frequently.

[0594] In one embodiment, the terminal may determine whether to perform the above-described operation based on the number of SSBs within the SSB cycle. For example, if the number of SSBs within the SSB cycle is set to a value greater than a certain value, the terminal may perform application of changing SBFD symbols overlapping with SSB symbols to non-SBFD symbols. If the number of SSBs within the SSB cycle is set to a value less than or equal to the certain value, the terminal may not perform application of changing SBFD symbols overlapping with SSB symbols to non-SBFD symbols.

[0595] Here, the number of SSBs can be 4. That is, when the number of SSBs is 8, the terminal can change the SBFD symbol overlapping with the SSB symbol into a non-SBFD symbol.

[0596] This is because the greater the number of SSBs within an SSB cycle, the more frequently SSB blocks and SBFD symbols may overlap.

[0597] Figure 28 is a flowchart illustrating operations performed by a terminal according to an embodiment of the present disclosure. The operations in Figure 28 may be combined and performed as a single step, or some operations may be omitted. Furthermore, the order of operations in Figure 28 may be interchanged.

[0598] Referring to FIG. 28, at step 2800, the terminal can receive a first upper layer configuration including TDD DL / UL configuration information from the base station.

[0599] At step 2810, the terminal can receive a second upper layer configuration including SSB configuration information from the base station.

[0600] At step 2820, the terminal may receive a third upper layer configuration including SBFD configuration information from the base station.

[0601] In step 2830, the terminal can determine the location of the SBFD symbol based on the first upper layer setting and the third upper layer setting, and can determine the location of the SSB symbol based on the second upper layer setting and the third upper layer setting.

[0602] In step 2840, the terminal can check whether the SSB symbol and the SBFD symbol overlap. If the SSB symbol and the SBFD symbol overlap, the terminal can change the SBFD symbol to a non-SBFD symbol according to an embodiment of the present disclosure. That is, if the SSB symbol and the SBFD symbol overlap, the terminal can regard the SBFD symbol as a non-SBFD symbol according to an embodiment of the present disclosure.

[0603] Additionally, the terminal can obtain fourth upper layer information from the base station. Based on the fourth upper layer information, the terminal can determine whether to change an SBFD symbol overlapping with an SSB symbol to a non-SBFD symbol.

[0604] Additionally, based on at least one of the number of transient points, the period of the SSB, or the number of SSBs within the SSB period, the terminal may determine whether to change an SBFD symbol overlapping with an SSB symbol to a non-SBFD symbol.

[0605] Additionally, the terminal can determine, based on the fifth upper layer information, whether to change an SBFD symbol that overlaps with an SSB symbol of a specific index among the SSBs received by the terminal into a non-SBFD symbol.

[0606] Additionally, the terminal can be configured to determine whether the SBFD symbol is an SBFD symbol or a downlink symbol based on the sixth upper layer information. For example, the sixth upper layer information may be a dedicated TDD configuration.

[0607] The embodiments and / or methods of the present disclosure described above can be performed by the terminal of FIG. 29 and the base station of FIG. 30.

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

[0609] Referring to FIG. 29, the terminal may include a transceiver, which refers to a terminal receiving unit (2900) and a terminal transmitting unit (2910), a memory (not shown), and a terminal processing unit (2905, or a terminal control unit or processor). Depending on the communication method of the terminal described above, the transceiver units (2900, 2910), the memory, and the terminal processing unit (2905) of the terminal may operate. The terminal processing unit (2905, 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.

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

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

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

[0613] Additionally, the terminal processing unit (2905, or processor) may control a series of processes so that the terminal can operate according to the aforementioned embodiments. For example, the processor may control components of the terminal to perform embodiments and / or methods of the present disclosure (e.g., the first embodiment / the second embodiment / the third embodiment / the fourth embodiment / the fifth embodiment, etc.). There may be multiple processors, and the processors may perform component control operations of the terminal by executing programs stored in memory.

[0614] For example, the terminal processing unit (2905, or processor) may be configured to receive information associated with a transition guard interval from a base station, determine the location of the transition guard interval based on the information, and switch from uplink to downlink or downlink to uplink in the transition guard interval. When switching from downlink to uplink, the location of the transition guard interval may start from the first symbol among consecutive symbols capable of uplink transmission, and each of the consecutive symbols capable of uplink transmission may be a symbol corresponding to an uplink subband and a downlink subband. The information associated with the transition guard interval may include first information indicating the length of the transition guard interval and second information indicating the location of the transition guard interval. For example, the transition guard interval may include N symbols (N is a natural number). When switching from downlink to uplink, the position of the transition guard interval may correspond to N symbols from the first symbol among the consecutive symbols that can be transmitted in the uplink, and when switching from uplink to downlink, the position of the transition guard interval may correspond to N symbols prior to the last symbol among the consecutive symbols that can be transmitted in the uplink.

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

[0616] Referring to FIG. 30, the base station may include a transceiver, which refers to a base station receiver (3000) and a base station transmitter (3010), a memory (not shown), and a base station processor (3005, or base station control unit or processor). According to the communication method of the base station described above, the transceiver (3000, 3010), the memory, and the base station processor (3005) of the base station may operate. The base station processor (3005, 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.

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

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

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

[0620] The base station processing unit (3005, or processor) can control a series of processes so that the base station can operate according to the embodiments of the present disclosure described above. For example, the processor can control each component of the base station to perform the embodiments and / or methods of the present disclosure (e.g., the first embodiment / the second embodiment / the third embodiment / the fourth embodiment / the fifth embodiment, etc.). There may be multiple processors, and the processors can perform the component control operations of the base station by executing a program stored in a memory.

[0621] For example, the base station processing unit (3005, or processor) may be configured to determine the location of a transition guard interval, generate information associated with the transition guard interval, and transmit the information associated with the transition guard interval to the terminal. In the transition guard interval, a transition from uplink to downlink or from downlink to uplink occurs, and in the case of a transition from downlink to uplink, the location of the transition guard interval may start from the first symbol among consecutive symbols capable of uplink transmission, and each of the consecutive symbols capable of uplink transmission may be a symbol corresponding to an uplink subband and a downlink subband.

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

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

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

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

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

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

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

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

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

Claims

1. In a method performed by a terminal in a wireless communication system, A step of receiving information associated with a transition guard interval from a base station; A step of confirming the location of the transition guard section based on the above information; and Including a step of switching from uplink to downlink or from downlink to uplink in the above transition guard section, When switching from downlink to uplink, the position of the transition guard interval starts from the first symbol among the consecutive symbols that can be transmitted in uplink, and A method wherein each of the consecutive symbols capable of uplink transmission is a symbol corresponding to an uplink subband and a downlink subband.

2. In paragraph 1, The above transition guard interval contains N symbols, where N is a natural number, When switching from downlink to uplink, the position of the transition guard interval corresponds to N symbols from the first symbol among consecutive symbols that can be transmitted in uplink, and A method characterized in that, when switching from uplink to downlink, the location of the transition guard interval corresponds to the N symbols preceding the last symbol among consecutive symbols capable of uplink transmission.

3. In paragraph 1, The step of switching from uplink to downlink or from downlink to uplink in the above transition guard period includes a step of not performing uplink transmission or downlink reception in the above transition guard period, and A method characterized in that the above information includes first information indicating the length of the transition guard section and second information indicating the position of the transition guard section.

4. In paragraph 3, A method characterized in that the length of the above transition guard interval is related to the subcarrier spacing of a bandwidth part (BWP).

5. In paragraph 1, Further comprising a step of transmitting capability information of the terminal to the base station, The above capability information includes information on the minimum value of the length of the transition guard interval required by the terminal, and A method characterized in that the above minimum value is determined according to the subcarrier spacing.

6. In paragraph 1, Further comprising a step of receiving information about a symbol pattern, The symbols corresponding to the above uplink sub-band and downlink sub-band are SBFD symbols, and A method characterized in that the above symbol pattern indicates SBFD symbols.

7. In paragraph 6, A method characterized by further comprising the step of receiving an index of a start symbol and an index of a last symbol to which the symbol pattern is to be applied.

8. In a wireless communication system, at the terminal, Transmitter and receiver; and At least one processor operably connected to the transceiver, wherein the at least one processor comprises: Receive information related to the transition guard interval from the base station, Based on the above information, the location of the transition guard section is confirmed, and In the above transition guard section, it is set to switch from uplink to downlink or from downlink to uplink, When switching from downlink to uplink, the position of the transition guard interval starts from the first symbol among the consecutive symbols that can be transmitted in uplink, and A terminal in which each of the consecutive symbols capable of uplink transmission corresponds to an uplink subband and a downlink subband.

9. In paragraph 8, The above transition guard interval contains N symbols, where N is a natural number, When switching from downlink to uplink, the position of the transition guard interval corresponds to N symbols from the first symbol among consecutive symbols that can be transmitted in uplink, and A terminal characterized in that, when switching from uplink to downlink, the position of the transition guard interval corresponds to the N symbols preceding the last symbol among consecutive symbols capable of uplink transmission.

10. In paragraph 8, In order to switch from uplink to downlink or from downlink to uplink in the above transition guard period, the at least one processor is configured not to perform uplink transmission or downlink reception in the above transition guard period, and A terminal characterized in that the above information includes first information indicating the length of the transition guard section and second information indicating the location of the transition guard section.

11. In paragraph 10, A terminal characterized in that the length of the above transition guard interval is related to the subcarrier spacing of a bandwidth part (BWP).

12. In paragraph 8, The at least one processor is further configured to transmit capability information of the terminal to the base station, The above capability information includes information on the minimum value of the length of the transition guard interval required by the terminal, and A terminal characterized in that the above minimum value is determined according to the subcarrier spacing.

13. In paragraph 8, the at least one processor: Receive information about symbol patterns, and It is further set to receive the index of the start symbol and the index of the last symbol to which the above symbol pattern is to be applied, The symbols corresponding to the above uplink sub-band and downlink sub-band are SBFD symbols, and A method characterized in that the above symbol pattern indicates SBFD symbols.

14. In a method performed by a base station in a wireless communication system, A step for determining the location of a transition guard section; A step of generating information associated with the above transition guard section; and A step of transmitting information associated with the transition guard section to the terminal, In the above transition guard section, a transition occurs from uplink to downlink or from downlink to uplink, In case of a transition from downlink to uplink, the position of the transition guard interval starts from the first symbol among the consecutive symbols that can be transmitted in uplink, and A method wherein each of the consecutive symbols capable of uplink transmission is a symbol corresponding to an uplink subband and a downlink subband.

15. In paragraph 14, Further comprising a step of receiving capability information of the terminal from the terminal, The above capability information includes information on the minimum value of the length of the transition guard interval required by the terminal, The above minimum value is determined by the subcarrier spacing, The above transition guard interval contains N symbols, where N is a natural number, When switching from downlink to uplink, the position of the transition guard interval corresponds to N symbols from the first symbol among consecutive symbols that can be transmitted in uplink, and A method characterized in that, when switching from uplink to downlink, the location of the transition guard interval corresponds to the N symbols preceding the last symbol among consecutive symbols capable of uplink transmission.

Images