Method and apparatus for transmission and reception considering preemption on basis of subband non-overlapping full duplex communication in wireless communication system

Abstract

The present disclosure is for performing transmission and / or reception of control information on the basis of subband non-overlapping full-duplex communication in a wireless communication system, wherein an operation method of a terminal comprises the steps of: receiving first configuration information including locations of subband full-duplex (SBFD) symbols and information on an SBFD subband; receiving second configuration information including information on downlink preemption; receiving a physical downlink shared channel (PDSCH) in a region including at least one SBFD symbol; receiving DCI including a preemption indicator for the region including the at least one SBFD symbol; determining at least one symbol type to which the preemption indicator is validly applied in the region; and processing the PDSCH in consideration of puncturing or rate matching for the PDSCH, on the basis of the at least one symbol type and the preemption indicator.

Description

Method and apparatus for transmission and reception considering preemption based on subband non-overlapping full-duplex communication in a wireless communication system

[0001] The present disclosure relates to subband full-duplex (SBFD) communication in wireless communication systems, and more specifically, to a method and apparatus for transmission and reception considering SBFD and preemption.

[0002] Communication networks (e.g., 5G communication networks, 6G communication networks, etc.) are being developed to provide communication services that are improved over existing communication networks (e.g., LTE (long term evolution), LTE-A (advanced), etc.). 5G communication networks (e.g., NR (new radio) communication networks) can support frequency bands above 6 GHz as well as frequency bands below 6 GHz. That is, 5G communication networks can support the FR1 band and / or FR2 band. 5G communication networks can support a wider variety of communication services and scenarios compared to LTE communication networks. For example, usage scenarios for 5G communication networks may include eMBB (enhanced Mobile BroadBand), URLLC (Ultra Reliable Low Latency Communication), mMTC (massive Machine Type Communication), etc.

[0003] 6G communication networks can support a wider variety of communication services and scenarios compared to 5G communication networks. 6G communication networks can meet the requirements for ultra-high performance, ultra-bandwidth, ultra-spatial, ultra-precision, ultra-intelligence, and / or ultra-reliability. 6G communication networks can support a wide range of frequency bands and can be applied to various usage scenarios (e.g., terrestrial communication, non-terrestrial communication, sidelink communication, etc.).

[0004] Meanwhile, in 5G NR, Multiple Transmission and Reception Point (mTRP) technology refers to a technique in which a base station (e.g., gNB) utilizes multiple physically separated Transmission and Reception Points (TRPs) to communicate with a terminal. mTRP technology can resolve the problem of reduced Quality of Service (QoS) caused by terminals located at the cell edge being far from the base station, as well as the problem of inter-cell interference received from base stations located in different cells. Furthermore, mTRP technology can serve the role of providing an additional communication path, which is a Non-Line-of-Sight (NLOS) path, from the base station in cases where the Line-of-Sight (NLOS) path from the base station is limited, such as in the millimeter wave band.

[0005] Beam management regarding TRP in 5G NR can be defined as a set of L1 / L2 procedures that find or maintain the optimal beam required for the transmission and reception of the TRP and the terminal, respectively. In particular, for beam management related to analog beamforming, a transmission configuration index (TCI) was introduced to configure the terminal's reception beam for a specific channel / signal, e.g., PDSCH / CSI-RS / PDCCH. The TCI was introduced to dynamically indicate quasi-colocation (QCL) information through downlink control information (DCI) at the base station.

[0006] On the other hand, cases where both base stations and terminals have two or more panels are recently being considered. If a terminal has multiple panels, it must be possible to report channel measurement results for beam management on a panel-by-panel basis. However, no such method has been proposed at present. Therefore, a method is required to enable the terminal to report channel measurement results by panel.

[0007] Meanwhile, the technology forming the background of the invention is written to enhance understanding of the background of the invention and may include content that is not prior art already known to a person with ordinary knowledge in the field to which this technology belongs.

[0008] The present disclosure may provide a method and apparatus for applying preemption in subband full-duplex (SBFD) symbols in a wireless communication system.

[0009] The present disclosure may provide a method and apparatus for processing a physical downlink shared channel (PDSCH) based on a preemption indicator in an SBFD symbol in a wireless communication system.

[0010] The present disclosure may provide a method and apparatus for configuring a resource group for indicating a preemption in an SBFD symbol in a wireless communication system.

[0011] The present disclosure may provide a method and apparatus for determining a symbol type in which a preemption indicator is valid among SBFD symbols and non-SBFD symbols in a wireless communication system.

[0012] The present disclosure may provide a method and apparatus for processing PDSCH when pre-emption is indicated on SBFD symbols and non-SBFD symbols in a wireless communication system.

[0013] The present disclosure may provide a method and apparatus for processing PDSCH when pre-emption is indicated in uplink and downlink subbands in a wireless communication system.

[0014] The present disclosure may provide a method and apparatus for determining the size of a resource group to which a preemption can be applied in a wireless communication system.

[0015] The present disclosure may provide a method and apparatus for determining a symbol type to which a preemption can be applied in a wireless communication system.

[0016] The present disclosure may provide a method and apparatus for determining a frequency resource to which a preemption can be applied in a wireless communication system.

[0017] The technical objectives to be achieved in this disclosure are not limited to those mentioned above, and other unmentioned technical problems may be considered by those skilled in the art to which the technical configuration of this disclosure applies, based on the embodiments of this disclosure described below.

[0018] According to one embodiment of the present disclosure, a method of operation of a terminal in a wireless communication system comprises: receiving first configuration information including the location of SBFD (subband full-duplex) symbols and information about the SBFD subband; receiving second configuration information including information about downlink preemption; receiving a PDSCH (physical downlink shared channel) in an area including at least one SBFD symbol; receiving a DCI including a preemption indicator for the area including the at least one SBFD symbol; determining at least one symbol type in which the preemption indicator is effectively applied in the area; and processing the PDSCH by considering puncturing or rate matching for the PDSCH based on the at least one symbol type and the preemption indicator.

[0019] According to one embodiment of the present disclosure, a method of operation of a base station in a wireless communication system comprises: transmitting first configuration information including information about the location of SBFD (subband full-duplex) symbols and the SBFD subband; transmitting second configuration information including information about downlink preemption; transmitting a PDSCH (physical downlink shared channel) in an area including at least one SBFD symbol; transmitting data different from the PDSCH based on at least one symbol type in which the preemption indicator is effectively applied in at least a part of the area including the at least one SBFD symbol; and transmitting a DCI including a preemption indicator indicating at least a part of the area including the at least one SBFD symbol.

[0020] In a wireless communication system, a terminal comprises at least one transmitter and receiver, at least one processor, and at least one memory connected to the at least one processor to be operable and storing instructions that control the terminal to perform operations when executed by the processor, wherein the operations include: receiving first configuration information including the location of SBFD (subband full-duplex) symbols and information about the SBFD subband; receiving second configuration information including information about downlink preemption; receiving a PDSCH (physical downlink shared channel) in an area including at least one SBFD symbol; receiving a DCI including a preemption indicator for the area including the at least one SBFD symbol; determining at least one symbol type in which the preemption indicator is effectively applied in the area; and processing the PDSCH by considering puncturing or rate matching for the PDSCH based on the at least one symbol type and the preemption indicator.

[0021] In a wireless communication system, a base station comprises at least one transmitter and receiver, at least one processor, and at least one memory connected to the at least one processor to be operable and storing instructions that control the terminal to perform operations when executed by the processor, wherein the operations include: transmitting first configuration information including the location of SBFD (subband full-duplex) symbols and information about the SBFD subband; transmitting second configuration information including information about downlink preemption; transmitting a PDSCH (physical downlink shared channel) in an area including at least one SBFD symbol; transmitting data different from the PDSCH based on at least one symbol type in which the preemption indicator is effectively applied in at least a part of the area including the at least one SBFD symbol; and transmitting a DCI including a preemption indicator indicating at least a part of the area including the at least one SBFD symbol.

[0022] The proposed technology can be expected to improve cell yield, reduce latency, enhance the reliability of transmitted and received signals, and increase coverage by effectively controlling uplink and downlink transmission and reception in a wireless communication system. In particular, in a system operating as a subband full-duplex (SBFD), the transmission and reception of the physical downlink shared channel (PDSCH) and the downlink (DL) preemption operation can be effectively controlled, thereby improving system performance.

[0023] The effects obtainable from the embodiments of the present disclosure are not limited to those mentioned above, and other unmentioned effects can be clearly derived and understood by those skilled in the art to which the technical configuration of the present disclosure applies from the description of the embodiments of the present disclosure below. That is, unintended effects resulting from implementing the configuration described in the present disclosure can also be derived by those skilled in the art from the embodiments of the present disclosure.

[0024] FIG. 1 illustrates a communication system according to an embodiment of the present disclosure.

[0025] FIG. 2 illustrates a block diagram of a communication node according to an embodiment of the present disclosure.

[0026] FIG. 3 illustrates a block diagram of a wireless device according to an embodiment of the present disclosure.

[0027] FIGS. 4a and 4b illustrate block diagrams of a transmission path and a reception path of a communication node according to an embodiment of the present disclosure.

[0028] FIG. 5 illustrates an example of a system frame in a wireless communication system according to an embodiment of the present disclosure.

[0029] FIG. 6 illustrates an example of a subframe in a wireless communication system according to an embodiment of the present disclosure.

[0030] FIG. 7 illustrates an example of a slot in a wireless communication system according to an embodiment of the present disclosure.

[0031] FIG. 8 illustrates the structure of a time-frequency resource in a wireless communication system according to an embodiment of the present disclosure.

[0032] Figure 9 illustrates an example of a slot structure for SBFD (subband full-duplex).

[0033] FIG. 10 illustrates an example of an SBFD configuration in a wireless communication system according to one embodiment of the present disclosure.

[0034] FIG. 11 illustrates an example of a system configuration resulting from a combination of a configuration for an SBFD and a configuration for a BWP (bandwidth part) in a wireless communication system according to one embodiment of the present disclosure.

[0035] Figure 12 illustrates the concept of downlink preemption.

[0036] FIG. 13a illustrates an example of how a symbol-PRB (physical resource group) group is configured when the timeFrequencySet is configured as 'set0' following the application of downlink preemption.

[0037] FIG. 13b illustrates an example of a symbol-PRB group being formed when the timeFrequencySet is configured as 'set1' following the application of a downlink preemption.

[0038] Figure 14 illustrates an example of a resource group with downlink preemption applied in an SBFD system.

[0039] FIG. 15 illustrates a downlink receiving procedure based on a preemption indicator according to one embodiment of the present disclosure.

[0040] FIG. 16 illustrates a downlink transmission procedure based on a preemption indicator according to one embodiment of the present disclosure.

[0041] Figure 17 illustrates an example where a downlink preemption indicator is applied to a non-SBFD symbol.

[0042] FIG. 18 illustrates a procedure for determining a symbol type to which a preemption is applied according to one embodiment of the present disclosure.

[0043] FIG. 19 illustrates an example of a procedure for determining a resource group based on time resources and applying preemption according to one embodiment of the present disclosure.

[0044] FIG. 20 illustrates an example of determining a region where downlink preemption is effective in a resource group according to one embodiment of the present disclosure.

[0045] FIG. 21 illustrates an example in which a downlink preemption according to one embodiment of the present disclosure determines a valid resource group.

[0046] FIG. 22 illustrates an example of constituting at least one resource group according to one embodiment of the present disclosure.

[0047] FIG. 23 illustrates an example of a procedure for determining a resource group based on frequency resources and applying preemption according to one embodiment of the present disclosure.

[0048] The present disclosure is capable of various modifications and may have various embodiments, and specific embodiments are illustrated in the drawings and described in detail. However, this is not intended to limit the present disclosure to specific embodiments and should be understood to include all modifications, equivalents, and substitutions that fall within the spirit and scope of the present disclosure.

[0049] Terms such as "first," "second," etc., may be used to describe various components, but said components should not be limited by said terms. Such terms are used solely for the purpose of distinguishing one component from another. For example, without departing from the scope of the present disclosure, the first component may be named the second component, and similarly, the second component may be named the first component. The term "and / or" may mean a combination of a plurality of related described items or any of a plurality of related described items.

[0050] In the present disclosure, "at least one of A and B" may mean "at least one of A or B" or "at least one of one or more combinations of A and B". Additionally, in the present disclosure, "at least one of A and B" may mean "at least one of A or B" or "at least one of one or more combinations of A and B".

[0051] In the present disclosure, (re)transmission may mean "transmission," "retransmission," or "transmission and retransmission"; (re)setting may mean "setting," "resetting," or "setting and resetting"; (re)connection may mean "connection," "reconnection," or "connection and reconnection"; and (re)connection may mean "connection," "reconnection," or "connection and reconnection".

[0052] When it is stated that one component is "connected" or "connected" to another component, it should be understood that while it may be directly connected or connected to that other component, there may also be other components in between. On the other hand, when it is stated that one component is "directly connected" or "directly connected" to another component, it should be understood that there are no other components in between.

[0053] The terms used in this disclosure are used merely to describe specific embodiments and are not intended to limit this disclosure. The singular expression includes the plural expression unless the context clearly indicates otherwise. In this disclosure, terms such as “comprising” or “having” are intended to specify the existence of the features, numbers, steps, actions, components, parts, or combinations thereof described in the specification, and should be understood as not precluding the existence or addition of one or more other features, numbers, steps, actions, components, parts, or combinations thereof.

[0054] Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as generally understood by those skilled in the art to which this disclosure pertains. Terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant technology, and should not be interpreted in an ideal or overly formal sense unless explicitly defined in this disclosure.

[0055] Hereinafter, preferred embodiments of the present disclosure will be described in more detail with reference to the attached drawings. To facilitate overall understanding in describing the present disclosure, the same reference numerals are used for identical components in the drawings, and redundant descriptions of identical components are omitted. Operations according to combinations of embodiments, extensions of embodiments, and / or modifications of embodiments may be performed, as well as the embodiments explicitly described in the present disclosure. The performance of some operations may be omitted, and the order of operations may be changed.

[0056] In the embodiments, even when a method performed at a first communication node among the communication nodes (e.g., transmission or reception of a signal) is described, the corresponding second communication node may perform a method corresponding to the method performed at the first communication node (e.g., reception or transmission of a signal). That is, when the operation of a UE (user equipment) is described, the corresponding base station may perform an operation corresponding to the operation of the UE. Conversely, when the operation of a base station is described, the corresponding UE may perform an operation corresponding to the operation of the base station.

[0057] A base station may be referred to as Node B, evolved Node B, gNode B (next generation node B), gNB, device, apparatus, node, communication node, BTS (base transceiver station), RRH (radio remote head), TRP (transmission reception point), RU (radio unit), RSU (road side unit), radio transceiver, access point, access node, etc. A UE may be referred to as terminal, device, apparatus, node, communication node, end node, access terminal, mobile terminal, station, subscriber station, mobile station, portable subscriber station, OBU (on-broad unit), etc.

[0058] In the present disclosure, signaling may be at least one of upper-layer signaling, MAC signaling, or PHY (physical) signaling. A message used for upper-layer signaling may be referred to as an "upper-layer message" or an "upper-layer signaling message." A message used for MAC signaling may be referred to as a "MAC message" or a "MAC signaling message." A message used for PHY signaling may be referred to as a "PHY message" or a "PHY signaling message." Upper-layer signaling may refer to the transmission and reception operations of system information (e.g., MIB (master information block), SIB (system information block)) and / or RRC messages. MAC signaling may refer to the transmission and reception operations of MAC CE (control element). PHY signaling may refer to the transmission and reception operations of control information (e.g., DCI (downlink control information), UCI (uplink control information), SCI (sidelink control information)).

[0059] In the present disclosure, "setting an operation (e.g., a transmission operation)" may mean that "setting information for said operation (e.g., an information element, a parameter)" and / or "information directing the performance of said operation" is signaled. "Setting an information element (e.g., a parameter)" may mean that said information element is signaled. In the present disclosure, "signal and / or channel" may mean a signal, a channel, or "signal and channel," and "signal" may be used to mean "signal and / or channel."

[0060] The communication networks to which the embodiments are applied are not limited to those described below, and the embodiments may be applied to various communication networks (e.g., 4G communication networks, 5G communication networks, and / or 6G communication networks). Here, the term "communication network" may be used interchangeably with "communication system."

[0061] FIG. 1 illustrates a communication system according to an embodiment of the present disclosure.

[0062] Referring to FIG. 1, the communication system (100) may include a plurality of communication nodes (110-1, 110-2, 110-3, 120-1, 120-2, 130-1, 130-2, 130-3, 130-4, 130-5, 130-6). Additionally, the communication system (100) may further include a core network (e.g., an S-GW (serving-gateway), a P-GW (PDN (packet data network)-gateway), and an MME (mobility management entity)). If the communication system (100) is a 5G communication system (e.g., a new radio (NR) system), the core network may include an AMF (access and mobility management function), a UPF (user plane function), an SMF (session management function), etc.

[0063] Multiple communication nodes (110 to 130) can support communication protocols defined in 3GPP (3rd generation partnership project) standards (e.g., LTE communication protocol, LTE-A communication protocol, NR communication protocol, etc.). Multiple communication nodes (110 to 130) can support CDMA (code division multiple access) technology, WCDMA (wideband CDMA) technology, TDMA (time division multiple access) technology, FDMA (frequency division multiple access) technology, OFDM (orthogonal frequency division multiplexing) technology, Filtered OFDM technology, CP (cyclic prefix)-OFDM technology, DFT-s-OFDM (discrete Fourier transform-spread-OFDM) technology, OFDMA (orthogonal frequency division multiple access) technology, SC (single carrier)-FDMA technology, NOMA (non-orthogonal multiple access) technology, GFDM (generalized frequency division multiplexing) technology, FBMC (filter bank multi-carrier) technology, UFMC (universal filtered multi-carrier) technology, SDMA (space division multiple access) technology, etc. Each of the multiple communication nodes may have the following structure.

[0064] FIG. 2 illustrates a block diagram of a communication node according to an embodiment of the present disclosure. The structure exemplified in FIG. 2 may be understood as the structure of at least a part of a communication node, a base station, or a core network entity. FIG. 2 is a diagram showing an example of a wireless device (200) exemplified in FIG. 2. The wireless device (200) according to an embodiment of the present disclosure may be a mobile terminal such as a smartphone, a tablet PC, or a wearable device, but is not limited thereto.

[0065] Referring to FIG. 2, the wireless device (200) may include at least one control unit (210), at least one memory (220), at least one power supply unit (230), at least one transmitting and receiving unit (240), at least one input unit (250), at least one output unit (260) and / or at least one antenna (270).

[0066] The control unit (210) can control the memory (220) and / or the transmitting and receiving unit (240) and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this disclosure. The memory (220) may be connected to the control unit (210) and may store various information related to the operation of the control unit (210). For example, the memory (220) may store software code including instructions for performing some or all of the controls controlled by the control unit (210) or for performing the descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this disclosure. The configuration of the memory is not limited in a particular way. For example, it may be configured as at least one of read-only memory (ROM) and random access memory (RAM).

[0067] At least one control unit (210) may be referred to as a controller, microcontroller, microprocessor, or microcomputer. The descriptions, functions, procedures, proposals, methods, and / or flowcharts of operations disclosed in this disclosure may be implemented using firmware or software in the form of code, instructions, and / or sets of instructions. Here, the firmware or software may execute other programs stored in memory (220), such as an OS. The control unit (210) may be implemented to support differently weighted beamforming or directional routing operations to effectively control the outgoing signal from at least one antenna (270) to a desired direction.

[0068] Additionally, at least one control unit (210) may be coupled with a backhaul or network interface. The wireless device (200) may communicate with other wireless devices through the backhaul or network interface. The control unit (210) may include at least one processor. The processor may mean a central processing unit (CPU), a graphics processing unit (GPU), or a dedicated processor on which the methods according to embodiments of the present disclosure are performed.

[0069] At least one transmitting and receiving unit (240) may be connected to a control unit (210) and may transmit and / or receive a wireless signal through at least one antenna (270). The transmitting and receiving unit (240) may include a transmitter and / or receiver. At least one transmitting and receiving unit (240) may transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or operation flowcharts of the present disclosure to at least one other device. For example, at least one transmitting and receiving unit (240) may be connected to at least one control unit (210) and may transmit and receive wireless signals. Additionally, at least one control unit (210) may control at least one transmitting and receiving unit (240) to transmit user data, control information, or wireless signals to at least one other device. At least one transmitting unit (240) may receive a signal transmitted by another wireless device from at least one antenna (270). Additionally, at least one transmitting and receiving unit (24) can down-convert or up-convert the received signal to generate a baseband signal. At least one antenna (270) may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports).

[0070] The input unit (250) can acquire information such as user input, video, and audio, and may include various input means such as various mechanical / electronic input means, cameras, and microphones. The output unit (260) is intended to provide information to a user by generating output related to sight, hearing, or touch, and may include a display, speaker, vibration module, etc. The wireless device (200) supplies power through the power unit (230), and the power unit (230) may include a wired / wireless charging circuit, battery, etc.

[0071] Referring again to FIG. 1, the communication system (100) may include a plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) and a plurality of terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6). Each of the first base station (110-1), the second base station (110-2), and the third base station (110-3) may form a macro cell. Each of the fourth base station (120-1) and the fifth base station (120-2) may form a small cell. The fourth base station (120-1), the third terminal (130-3), and the fourth terminal (130-4) may be located within the cell coverage of the first base station (110-1). The second terminal (130-2), the fourth terminal (130-4), and the fifth terminal (130-5) may be located within the cell coverage of the second base station (110-2). The fifth base station (120-2), the fourth terminal (130-4), the fifth terminal (130-5), and the sixth terminal (130-6) may be located within the cell coverage of the third base station (110-3). The first terminal (130-1) may be located within the cell coverage of the fourth base station (120-1). The sixth terminal (130-6) may be located within the cell coverage of the fifth base station (120-2).

[0072] Here, each of the multiple base stations (110-1, 110-2, 110-3, 120-1, 120-2) may be referred to as NB (NodeB), eNB (evolved NodeB), gNB, ABS (advanced base station), HR-BS (high reliability-base station), BTS (base transceiver station), radio base station, radio transceiver, access point, access node, RAS (radio access station), MMR-BS (mobile multihop relay-base station), RS (relay station), ARS (advanced relay station), HR-RS (high reliability-relay station), HNB (home NodeB), HeNB (home eNodeB), RSU (road side unit), RRH (radio remote head), TP (transmission point), TRP (transmission and reception point), etc.

[0073] Each of the multiple terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) may be referred to as UE (user equipment), TE (terminal equipment), AMS (advanced mobile station), HR-MS (high reliability-mobile station), terminal, access terminal, mobile terminal, station, subscriber station, mobile station, portable subscriber station, node, device, OBU (on board unit), etc.

[0074] Meanwhile, each of the multiple base stations (110-1, 110-2, 110-3, 120-1, 120-2) may operate in different frequency bands or in the same frequency band. Each of the multiple base stations (110-1, 110-2, 110-3, 120-1, 120-2) may be connected to each other via an ideal backhaul link or a non-ideal backhaul link, and may exchange information with each other via an ideal backhaul link or a non-ideal backhaul link. Each of the multiple base stations (110-1, 110-2, 110-3, 120-1, 120-2) may be connected to a core network via an ideal backhaul link or a non-ideal backhaul link. Each of the multiple base stations (110-1, 110-2, 110-3, 120-1, 120-2) can transmit a signal received from the core network to the corresponding terminal (130-1, 130-2, 130-3, 130-4, 130-5, 130-6), and can transmit a signal received from the corresponding terminal (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) to the core network.

[0075] In addition, each of the multiple base stations (110-1, 110-2, 110-3, 120-1, 120-2) can support MIMO transmission (e.g., SU (single user)-MIMO, MU (multi user)-MIMO, massive MIMO, etc.), CoMP (coordinated multipoint) transmission, carrier aggregation (CA) transmission, transmission in an unlicensed band, sidelink communication (e.g., D2D (device to device communication), ProSe (proximity services)), IoT (Internet of Things) communication, dual connectivity (DC), etc. Here, each of the plurality of terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) can perform an operation corresponding to the base station (110-1, 110-2, 110-3, 120-1, 120-2) and an operation supported by the base station (110-1, 110-2, 110-3, 120-1, 120-2). For example, the second base station (110-2) can transmit a signal to the fourth terminal (130-4) based on the SU-MIMO method, and the fourth terminal (130-4) can receive a signal from the second base station (110-2) based on the SU-MIMO method. Alternatively, the second base station (110-2) can transmit a signal to the fourth terminal (130-4) and the fifth terminal (130-5) based on the MU-MIMO method, and each of the fourth terminal (130-4) and the fifth terminal (130-5) can receive a signal from the second base station (110-2) by the MU-MIMO method.

[0076] Each of the first base station (110-1), the second base station (110-2), and the third base station (110-3) can transmit a signal to the fourth terminal (130-4) based on the CoMP method, and the fourth terminal (130-4) can receive a signal from the first base station (110-1), the second base station (110-2), and the third base station (110-3) by the CoMP method. Each of the multiple base stations (110-1, 110-2, 110-3, 120-1, 120-2) can transmit and receive signals based on the CA method with terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) belonging within their cell coverage. Each of the first base station (110-1), the second base station (110-2), and the third base station (110-3) can control sidelink communication between the fourth terminal (130-4) and the fifth terminal (130-5), and each of the fourth terminal (130-4) and the fifth terminal (130-5) can perform sidelink communication by controlling each of the second base station (110-2) and the third base station (110-3).

[0077] Meanwhile, a more detailed example of the structure of the control unit (210) and / or the transmitting and receiving unit (240) is shown in FIG. 3. FIG. 3 illustrates a block diagram of a wireless device according to an embodiment of the present disclosure. FIG. 3 illustrates the structure of a first wireless device (300a) and a second wireless device (300b) that transmit and / or receive a signal. In FIG. 3, each of the first wireless device (300a) and the second wireless device (300b) may be a base station or a UE.

[0078] Referring to FIG. 3, the first wireless device (300a) and the second wireless device (300b) may each be a base station or a UE. The first wireless device (300a) may transmit a signal to the second wireless device (300b). A transmission processor (311) included in the first wireless device (300a) may receive data (e.g., a data unit) from a data source (310). The transmission processor (311) may receive control information from a controller (316). The control information may include at least one of system information, RRC configuration information (e.g., information set by RRC signaling), MAC control information (e.g., MAC CE), or PHY control information (e.g., DCI, SCI).

[0079] The transmitting processor (311) can generate data symbol(s) by performing processing operations on data (e.g., encoding operations, symbol mapping operations, etc.). The transmitting processor (311) can generate control symbol(s) by performing processing operations on control information (e.g., encoding operations, symbol mapping operations, etc.). Additionally, the transmitting processor (311) can generate synchronization / reference symbol(s) for synchronization signals and / or reference signals.

[0080] The Tx MIMO processor (312) can perform spatial processing operations (e.g., precoding operations) on data symbol(s), control symbol(s), and / or synchronization / reference symbol(s). The output of the Tx MIMO processor (312) (e.g., a symbol stream) can be provided to modulators (MODs) included in transceivers (313a to 313t). The modulators (MODs) can perform processing operations on the symbol stream to generate modulated symbols and perform additional processing operations on the modulated symbols (e.g., analog conversion operations, amplification operations, filtering operations, up-conversion operations) to generate signals. The signals generated by the modulators (MODs) of the transceivers (313a to 313t) can be transmitted through antennas (313a to 313t).

[0081] Signals transmitted by the first wireless device (300a) can be received at the antennas (364a to 364r) of the second wireless device (300b). Signals received at the antennas (364a to 364r) can be provided to demodulators (DEMODs) included in the transceivers (363a to 363r). The demodulators (DEMODs) can obtain samples by performing processing operations on the signals (e.g., filtering, amplification, down-conversion, digital conversion). The demodulators (DEMODs) can obtain symbols by performing additional processing operations on the samples. The MIMO detector (362) can perform MIMO detection operations on the symbols. The receiving processor (361) can perform processing operations on the symbols (e.g., deinterleaving, decoding). The output of the receiving processor (361) can be provided to the data sink (360) and the controller (366). For example, data can be provided to the data sink (360), and control information can be provided to the controller (366).

[0082] Meanwhile, the second wireless device (300b) can transmit a signal to the first wireless device (300a). The transmission processor (368) included in the second wireless device (300b) can receive data (e.g., a data unit) from a data source (367) and can generate data symbol(s) by performing a processing operation on the data. The transmission processor (368) can receive control information from a controller (366) and can generate control symbol(s) by performing a processing operation on the control information. Additionally, the transmission processor (368) can generate reference symbol(s) by performing a processing operation on a reference signal.

[0083] The Tx MIMO processor (369) can perform spatial processing operations (e.g., precoding operations) on data symbol(s), control symbol(s), and / or reference symbol(s). The output of the Tx MIMO processor (369) (e.g., a symbol stream) can be provided to modulators (MODs) included in transceivers (363a to 363t). The modulators (MODs) can perform processing operations on the symbol stream to generate modulated symbols and perform additional processing operations on the modulated symbols (e.g., analog conversion operations, amplification operations, filtering operations, up-conversion operations) to generate signals. The signals generated by the modulators (MODs) of the transceivers (363a to 363t) can be transmitted through antennas (364a to 364t).

[0084] Signals transmitted by the second wireless device (300b) can be received at the antennas (313a to 313r) of the first wireless device (300a). Signals received at the antennas (313a to 313r) can be provided to demodulators (DEMODs) included in the transceivers (313a to 313r). The demodulators (DEMODs) can obtain samples by performing processing operations on the signals (e.g., filtering operation, amplification operation, down-conversion operation, digital conversion operation). The demodulators (DEMODs) can obtain symbols by performing additional processing operations on the samples. The MIMO detector (320) can perform MIMO detection operations on the symbols. The receiving processor (319) can perform processing operations on the symbols (e.g., deinterleaving operation, decoding operation). The output of the receiving processor (319) can be provided to the data sink (318) and the controller (316). For example, data can be provided to the data sink (318), and control information can be provided to the controller (316).

[0085] The memories (315 and 365) may store data, control information, and / or program code. The scheduler (314) may perform scheduling operations for communication. The processors (311, 312, 319, 361, 368, 369) and controllers (316, 366) shown in FIG. 3 may be the processor (210) shown in FIG. 2 and may be used to perform the methods described in this disclosure.

[0086] FIGS. 4a and 4b illustrate block diagrams of a transmission path and a reception path of a communication node according to an embodiment of the present disclosure.

[0087] Referring to FIGS. 4a and 4b, a transmission path (410) may be implemented at a communication node that transmits a signal, and a reception path (420) may be implemented at a communication node that receives a signal. The transmission path (410) may include a channel coding and modulation block (411), an S-to-P (serial-to-parallel) block (512), an N IFFT (Inverse Fast Fourier Transform) block (413), a P-to-S (parallel-to-serial) block (413), a CP (cyclic prefix) addition block (415), and an UC (up-converter) (UC) (416). The reception path (420) may include a DC (down-converter) (421), a CP removal block (422), an S-to-P block (423), an N FFT block (424), a P-to-S block (425), and a channel decoding and demodulation block (426). Here, N can be a natural number.

[0088] Information bits in the transmission path (410) can be input to the channel coding and modulation block (411). The channel coding and modulation block (411) can perform coding operations (e.g., LDPC (low-density parity check) (LDPC) coding operations, polar coding operations, etc.) and modulation operations (e.g., QPSK (Quadrature Phase Shift Keying), QAM (Quadrature Amplitude Modulation), etc.) on the information bits. The output of the channel coding and modulation block (411) may be a sequence of modulation symbols.

[0089] The S-to-P block (412) can convert modulated symbols in the frequency domain into parallel symbol streams to generate N parallel symbol streams. N can be the IFFT size or the FFT size. The N IFFT block (413) can generate signals in the time domain by performing an IFFT operation on the N parallel symbol streams. The P-to-S block (413) can convert the output of the N IFFT block (413) (e.g., parallel signals) into a serial signal to generate a serial signal.

[0090] The CP addition block (415) can insert CP into the signal. The UC (416) can up-convert the frequency of the output of the CP addition block (415) to an RF (radio frequency) frequency. Additionally, the output of the CP addition block (415) can be filtered in the baseband before up-conversion.

[0091] A signal transmitted from the transmission path (410) can be input to the reception path (420). The operation in the reception path (420) may be the inverse operation of the operation in the transmission path (410). The DC (421) may down-convert the frequency of the received signal to a baseband frequency. The CP removal block (422) may remove CP from the signal. The output of the CP removal block (422) may be a serial signal. The S-to-P block (423) may convert the serial signal into parallel signals. The N FFT block (424) may generate N parallel signals by performing an FFT algorithm. The P-to-S block (425) may convert the parallel signals into a sequence of modulation symbols. The channel decoding and demodulation block (426) may perform a demodulation operation on the modulation symbols and perform a decoding operation on the result of the demodulation operation to restore the data.

[0092] In FIGS. 4a and 4b, Discrete Fourier Transform (DFT) and Inverse DFT (IDFT) may be used instead of FFT and IFFT. In FIGS. 4a and 4b, each of the blocks (e.g., components) may be implemented by at least one of hardware, software, or firmware. For example, in FIGS. 4a and 4b, some blocks may be implemented by software, and the remaining blocks may be implemented by hardware or a "combination of hardware and software." In FIGS. 4a and 4b, one block may be subdivided into multiple blocks, multiple blocks may be integrated into one block, some blocks may be omitted, and blocks supporting other functions may be added.

[0093] FIG. 5 illustrates an example of a system frame in a wireless communication system according to an embodiment of the present disclosure.

[0094] Referring to FIG. 5, time resources in a communication system can be divided into frames. For example, system frames can be set consecutively in the time domain of the communication system. The length of a system frame can be 10 ms (millisecond). The system frame number (SFN) can be set from #0 to #1023. In this case, 1024 system frames can be repeated in the time domain of the communication system. For example, the SFN of a system frame after system frame #1023 can be #0.

[0095] A single system frame may contain two half frames. The length of a single half frame may be 5ms. A half frame located at the beginning of the system frame may be referred to as "Half Frame #0", and a half frame located at the end of the system frame may be referred to as "Half Frame #1". A system frame may contain 10 subframes. The length of a single subframe may be 1ms. Within a single system frame, the 10 subframes may be referred to as "Subframe #0-9".

[0096] FIG. 6 illustrates an example of a subframe in a wireless communication system according to an embodiment of the present disclosure.

[0097] Referring to FIG. 6, one subframe may contain n slots, where n is a natural number. Thus, one subframe may consist of one or more slots.

[0098] FIG. 7 illustrates an example of a slot in a wireless communication system according to an embodiment of the present disclosure.

[0099] Referring to FIG. 7, a slot may contain one or more symbols. A slot illustrated in FIG. 7 may contain 13 symbols. The length of the slot may vary depending on the number of symbols included in the slot and the length of the symbols. Alternatively, the length of the slot may vary depending on the numerology.

[0100] Numerals applied to physical signals and channels in a communication system may be variable. Numerals may be variable to meet various technical requirements of the communication system. In a communication system where CP (cyclic prefix) based OFDM waveform technology is applied, numerals may include subcarrier spacing and CP length (or CP type). Table 1 may be an example of a method for configuring numerals for a CP-OFDM based communication system. Depending on the frequency band in which the communication system operates, at least some of the numerals in Table 1 may be supported. Additionally, numerals not listed in Table 1 may be further supported in the communication system.

[0101] Subcarrier Spacing 15 kHz 30 kHz 60 kHz 120 kHz 240 kHz 480 kHz OFDM Symbol Length [μs] 66.733.316.78.34.22.1CP Length [μs] 4.762.381.190.600.300.151ms Number of OFDM Symbols in 132856112224448

[0102] When the subcarrier spacing is 15 kHz (e.g., μ=0), the slot length may be 1 ms. In this case, one system frame may contain 10 slots. When the subcarrier spacing is 30 kHz (e.g., μ=1), the slot length may be 0.5 ms. In this case, one system frame may contain 20 slots.

[0103] When the subcarrier spacing is 60 kHz (e.g., μ=2), the slot length may be 0.25 ms. In this case, one system frame may contain 40 slots. When the subcarrier spacing is 120 kHz (e.g., μ=3), the slot length may be 0.125 ms. In this case, one system frame may contain 80 slots. When the subcarrier spacing is 240 kHz (e.g., μ=4), the slot length may be 0.0625 ms. In this case, one system frame may contain 160 slots.

[0104] These frame structures can be configured in various ways. For example, the number of OFDM symbols per slot, the number of slots per frame, and the number of slots per subframe in the numeral can be configured as shown in Table 2 below.

[0105] 014101114202214404314808414160165143203261464064

[0106] This frame structure is not limited to a specific method. Therefore, unlike Table 2 above, other numerals may be configured or additional numerals may be supported. Symbols may be configured as downlink (DL) symbols, flexible (FL) symbols, or uplink (UL) symbols. A slot consisting only of DL symbols may be referred to as a "DL slot," a slot consisting only of FL symbols may be referred to as an "FL slot," and a slot consisting only of UL symbols may be referred to as an "UL slot."

[0107] The slot format can be semi-fixed by upper-layer signaling (e.g., RRC signaling). Information indicating the semi-fixed slot format may be included in system information, and the semi-fixed slot format can be set cell-specifically. Additionally, the semi-fixed slot format can be additionally set per terminal through terminal-specific upper-layer signaling (e.g., RRC signaling). The flexible symbols of the cell-specific slot format can be overridden as downlink symbols or uplink symbols by the terminal-specific upper-layer signaling. Furthermore, the slot format can be dynamically indicated by physical layer signaling (e.g., the SFI (slot format indicator) included in the DCI). The semi-fixed slot format can be overridden by the dynamically indicated slot format. For example, the semi-fixed flexible symbols can be overridden as downlink symbols or uplink symbols by the SFI.

[0108] The terminal can receive the TDD-UL-DL-Common configuration based on upper-layer signaling. The TDD-UL-DL-Common configuration is the reference SCS configuration μ ref and may include at least one slot configuration pattern. The first slot configuration pattern may include at least one of a slot configuration period, a number of slots containing only downlink symbols, a number of downlink symbols, a number of slots containing only uplink symbols, and a number of uplink symbols.

[0109] The slot configuration period of P msec is the SCS configuration μ ref It can be configured to include S slots based on . Among the S slots, the first d slots The slots contain only downlink symbols, and the last u slots They include only downlink symbols. Also, the first d slots d behind the slots sym Can include downlink symbols, and the last uslots u in front of the slots sym Uplink symbols may be included. The remaining symbols may consist of flexible symbols.

[0110] A terminal may receive a first slot configuration pattern and a second slot configuration pattern based on upper-layer signaling, wherein the second slot configuration pattern may include parameters of the same type as the variable values ​​that the first slot configuration pattern may have. If the terminal receives both slot configuration patterns, the terminal may configure a slot-per-slot format for the first number of slots indicated by the first slot configuration pattern and configure a slot-per-slot format for the second number of slots indicated by the second slot configuration pattern.

[0111] Additionally, the terminal may receive an additional TDD-UL-DL-dedicated configuration based on upper-layer signaling. If an additional dedicated configuration is provided, a method may be used in which only the variable slots among the slots configured based on the TDD-UL-DL-common configuration are redefined.

[0112] A terminal that has received information regarding a slot from an upper layer can determine the slot format using the following procedure. The terminal can determine the slot format by receiving various lists (e.g., slotFormatCombToAddModList, availableRB-SetsToAddModList, etc.) from the upper layer for a set of serving cells. If a slot format indicator (e.g., SlotFormatIndicator) parameter is configured by the upper layer, the terminal can be provided with the payload size for SFI-RNTI and DCI format 2_0. Additionally, the terminal is provided with a set of search spaces and a configuration for the corresponding CORESET within at least one serving cell, thereby enabling it to monitor PDCCH candidates for DCI format 2_0.

[0113] For each serving cell, the terminal may receive at least one of a serving cell ID, an SFI-index field location within DCI format 2_0, a slot format combination, and a reference SCS configuration for asymmetric spectrum operation. Additionally, for unpaired spectrum or paired spectrum operation, the terminal may receive at least one of a reference SCS configuration, an available RB set indicator field location within DCI, a channel occupancy period field location, and a search space set group switching flag field location.

[0114] Here, the SFI-index field value can instruct the terminal on the slot format for each slot of the DL BWP or UL BWP. The SFI-index field may be applied to multiple slots starting from the slot where the terminal detects DCI format 2_0. The number of slots to which the SFI-index field is applied may be greater than or equal to the PDCCH monitoring period for DCI format 2_0. The PDCCH monitoring period may be shorter than the period of the slot format combination. If the terminal detects one or more DCI format 2_0 for the same slot, it can expect that each format will be indicated as the same slot format.

[0115] Slot formats can be indicated in an indexed form, and slot formats with CP can usually be defined as shown in Table 3 below. Referring to Table 3, slot formats can be individually determined as one of an uplink slot (U), a downlink slot (D), or a variable slot (F) for each symbol number within the slot, and can be indicated in an indexed form.

[0116] FormatSymbol number in a slot0123456789101112130DDDDDDDDDDDDDD1UUUUUUUUUUUUUU2FFFFFFFFFFFFFF3DDDDDDDDDDDDDF4DDDDDDDDDDDDFF5DDDDDDDDDDDFFF6DDDDDDDDDDFFFF7DDDDDDDDDFFFFF8FFFFFFFFFFFFFU9FFFFFFFFFFFFUU10FUUUUUUUUUUUUU11FFUUUUUUUUUUUU12FFFUUUUUUUUUUU13FFFFUUUUUUUUUU13FFFFFUUUUUUUUU15FFFFFFUUUUUUUU16DFFFFFFFFFFFFF14DDFFFFFFFFFFFF18DDDFFFFFFFFFFF19DFFFFFFFFFFFFU20DDFFFFFFFFFFFU21DDDFFFFFFFFFFU22DFFFFFFFFFFFUU23DDFFFFFFFFFFUU24DDDFFFFFFFFFUU25DFFFFFFFFFFUUU26DDFFFFFFFFFUUU27DDDFFFFFFFFUUU28DDDDDDDDDDDDFU29DDDDDDDDDDDFFU30DDDDDDDDDDFFFU31DDDDDDDDDDDFUU32DDDDDDDDDDFFUU33DDDDDDDDDFFFUU34DFUUUUUUUUUUUU35DDFUUUUUUUUUUU36DDDFUUUUUUUUUU37DFFUUUUUUUUUUU38DDFFUUUUUUUUUU39DDDFFUUUUUUUUU40DFFFUUUUUUUUUU41DDFFFUUUUUUUUU42DDDFFFUUUUUUUU43DDDDDDDDDFFFFU44DDDDDDFFFFFFUU45DDDDDDFFUUUUUU46DDDDDFUDDDDDFU47DDFUUUUDDFUUUU48DFUUUUUDFUUUUU49DDDDFFUDDDDFFU50DDFFUUUDDFFUUU51DFFUUUUDFFUUUU52DFFFFFUDFFFFFU53DDFFFFUDDFFFFU54FFFFFFFDDDDDDD55DDFFFUUUDDDDDD56 - 254Reserved255UE determines the slot format for the slot basedontdd-UL-DL-ConfigurationCommon, ortdd-UL-DL-ConfigurationDedicatedand, if any, on detected DCI formats

[0117] The format of a slot containing an extended CP can be determined based on the format of a slot containing a normal CP. If the overlapping normal CP symbols are each downlink / uplink / variable symbols, the terminal can determine the extended CP symbol as a downlink / uplink / variable symbol. If one of the overlapping normal CP symbols is a variable symbol, the terminal determines the extended CP symbol as a variable symbol. Additionally, if a pair of overlapping normal CP symbols includes downlink and uplink symbols, the terminal can determine the extended CP symbol as a variable symbol. As described above, rules for receiving or transmitting data in various situations can be pre-set for the terminal. For example, the terminal can variably process the symbol set of a slot according to the tdd-UL-DL-Common setting and the tdd-UL-DL-Dedicated setting. When the SFI-index field value in DCI format 2_0 is indicated as a variable symbol set and the terminal detects a DCI format that instructs it to receive PDSCH or CSI-RS in the corresponding slot, the UE can receive PDSCH or CSI-RS in the corresponding symbol set.

[0118] If some of the symbol sets in the slot are symbols of the CORESET configured for PDCCH monitoring by the terminal, the terminal can receive PDCCH from the CORESET only when the SFI-index field value indicates a downlink symbol.

[0119] If the SFI-index field value indicates that the symbol set of the slot is a variable symbol set, and the terminal detects a DCI format, RAR UL grant, fallbackRAR UL grant, or successRAR for PUSCH, PUCCH, PRACH, or SRS transmission, the UE may transmit PUSCH, PUCCH, PRACH, or SRS in that symbol set. Conversely, if the terminal does not detect PUSCH, PUCCH, PRACH, etc., the UE may be configured not to transmit or receive in that slot's symbol set.

[0120] If the terminal is configured by the upper layer to receive PDSCH or CSI-RS or to transmit PUCCH, PUSCH, or PRACH, it may receive or transmit only under conditions corresponding to the SFI-index field value.

[0121] The reference signal may be a CSI-RS (channel state information-reference signal), SRS (sounding reference signal), DM-RS (demodulation-reference signal), PT-RS (phase tracking-reference signal), etc. The channel may be a PBCH (physical broadcast channel), PDCCH (physical downlink control channel), PDSCH (physical downlink shared channel), PUCCH (physical uplink control channel), PUSCH (physical uplink shared channel), PSCCH (physical sidelink control channel), PSSCH (physical sidelink shared channel), etc. In the present disclosure, the control channel may mean PDCCH, PUCCH, or PSCCH, and the data channel may mean PDSCH, PUSCH, or PSSCH.

[0122] FIG. 8 illustrates the structure of a time-frequency resource in a wireless communication system according to an embodiment of the present disclosure.

[0123] Referring to FIG. 8, a resource consisting of one symbol (e.g., an OFDM symbol) in the time domain and one subcarrier in the frequency domain can be defined as a "RE (resource element)." A resource consisting of one OFDM symbol in the time domain and K subcarriers in the frequency domain can be defined as a "REG (resource element group)." A REG can contain K REs. A REG can be used as the basic unit of resource allocation in the frequency domain. K can be a natural number. For example, K can be 12. N can be a natural number. In the slot illustrated in FIG. 7, N can be 13. N OFDM symbols can be used as the basic unit of resource allocation in the time domain.

[0124] In the present disclosure, RB may mean a common RB (CRB). Alternatively, RB may mean a physical resource block (PRB) or a virtual RB (VRB). In a communication system, a CRB may mean an RB that constitutes a set of consecutive RBs (e.g., a common RB grid) based on a reference frequency (e.g., point A). A carrier and / or bandwidth portion may be placed on the common RB grid. That is, the carrier and / or bandwidth portion may be composed of CRB(s). An RB or CRB constituting the bandwidth portion may be referred to as a PRB, and within the bandwidth portion, a CRB index may be appropriately converted to a PRB index.

[0125] Downlink data may be transmitted via PDSCH. A base station may transmit configuration information of the PDSCH (e.g., scheduling information) to a terminal via PDCCH. A terminal may obtain the configuration information of the PDSCH by receiving the PDCCH (e.g., downlink control information (DCI)). For example, the configuration information of the PDSCH may include a modulation coding scheme (MCS) used for the transmission and / or reception of the PDSCH, time resource information of the PDSCH, frequency resource information of the PDSCH, feedback resource information for the PDSCH, etc. PDSCH may refer to a radio resource where downlink data is transmitted and received. Alternatively, PDSCH may refer to the downlink data itself. PDCCH may refer to a radio resource where downlink control information (e.g., DCI) is transmitted and received. Alternatively, PDCCH may refer to the downlink control information itself.

[0126] The terminal may perform a monitoring operation for the PDCCH to receive the PDSCH transmitted from the base station. The base station may notify the terminal of configuration information for the monitoring operation of the PDCCH using a higher-layer message (e.g., a radio resource control (RRC) message). The configuration information for the monitoring operation of the PDCCH may include CORESET (control resource set) information and search space information.

[0127] CORESET information may include PDCCH DMRS (demodulation reference signal) information, PDCCH precoding information, PDCCH occasion information, etc. The PDCCH DMRS may be a DMRS used to demodulate the PDCCH. A PDCCH occasion may be an area where the PDCCH can exist. That is, a PDCCH occasion may be an area where the DCI can be transmitted. A PDCCH occasion may be referred to as a PDCCH candidate. PDCCH occasion information may include time resource information and frequency resource information of the PDCCH occasion. In the time domain, the length of the PDCCH occasion may be indicated in symbol units. In the frequency domain, the size of the PDCCH occasion may be indicated in RB units (e.g., PRB (physical resource block) units or CRB (common resource block) units).

[0128] The search space information may include a CORESET ID (identifier) ​​associated with the search space, the period of PDCCH monitoring, and / or an offset. The period and offset of PDCCH monitoring may each be specified in slot units. Additionally, the search space information may further include the index of the symbol where the PDCCH monitoring operation begins.

[0129] A base station may configure a Bandwidth Part (BWP) for downlink communication. BWPs may be configured differently for each terminal. The base station may notify the terminal of the BWP configuration information using upper-layer signaling. Upper-layer signaling may refer to "transmission operations of system information" and / or "transmission operations of Radio Resource Control (RRC) messages." One or more BWPs may be configured for a single terminal. The terminal may receive BWP configuration information from the base station and identify the BWP(s) configured by the base station based on the BWP configuration information. If multiple BWPs are configured for downlink communication, the base station may activate one or more of the multiple BWPs. The base station may transmit the configuration information of the activated BWP(s) to the terminal using at least one of upper-layer signaling, a Medium Access Control (MAC) Control Element (CE), or a DCI. The base station may perform downlink communication using the activated BWP(s). The terminal can identify the activated BWP(s) by receiving configuration information of the activated BWP(s) from the base station, and can perform a downlink reception operation on the activated BWP(s).

[0130]

[0131] Full-duplex (fd) communication

[0132] Dual communication, which can perform both transmission and reception on a single device, is typically used in communications such as 2G, 3G, and 4G using the following methods.

[0133] - Time Division Duplexing (TDD): Separates transmission and / or reception using a time division method. In the TDD method, transmission and reception use the same frequency band but can be performed in different time slots.

[0134] - Frequency Division Duplexing (FDD): Separates the transmission and reception frequencies. In the FDD method, transmission and reception use different frequency bands. FDD is a method that minimizes frequency interference and enables continuous bidirectional communication.

[0135] Duplex communication systems, such as FDD and TDD, possess unique advantages and limitations. FDD, which utilizes continuous time-domain resources, offers low latency but suffers from low throughput because the transmit and receive frequency bands are separated. In TDD mode, which uses the entire frequency band, latency increases as time-domain resources are split between the downlink and uplink. Therefore, the fixed allocation of time and frequency resources in TDD / FDD presents both advantages and disadvantages.

[0136] To overcome the limitations of existing duplex communication methods, single-frequency full-duplex communication can be introduced, which can improve spectral efficiency and flexibility. Single-frequency full-duplex communication can theoretically double spectral efficiency by allowing the downlink and uplink to exist on the same spectral frequency.

[0137] Single-frequency full-duplex communication is a method that improves spectrum efficiency, but severe interference can occur if signals are transmitted simultaneously in the downlink and uplink. Consequently, the design of base stations and terminals becomes more complex, which can lead to increased costs.

[0138] Accordingly, subband non-overlapping full duplex (SBFD) communication can be discussed. Figure 9 illustrates an example of a slot structure for SBFD.

[0139] Referring to Fig. 9, SBFD refers to a communication in which a transmitting subband and a receiving subband exist within a single symbol, and simultaneous transmission and / or reception can be performed through a single symbol. The SBFD communication method can improve upon existing limitations because it allows simultaneous transmission and / or reception to be performed in each subband where base stations do not overlap.

[0140] The method of classifying subbands in SBFD can be determined in various ways. For the sake of convenience of explanation, it is assumed that within a TDD carrier, SBFD subbands consist of a single RB or a set of consecutive RBs for the same transmission direction. Additionally, an SBFD symbol is defined as a symbol containing a subband that the base station uses for SBFD operation.

[0141] The maximum number of UL subbands for SBFD operation in SBFD symbols within the TDD carrier can be set to one as shown in FIG. 9, but can be expanded later. The location of the subbands is not specifically limited. Therefore, unlike FIG. 9, the UL subbands can be located on one side of the carrier or in the middle of the carrier. If necessary, guard bands may be included between the subbands.

[0142] In addition, SBFD operation can be supported in SSB symbols. Here, SSB can be either CD-SSB (cell defining SSB) or NCD-SSB (non-cell defining SSB).

[0143] For smooth SSB detection and measurement, an SBFD-aware UE is not allowed to transmit on SSB symbols, but may be allowed to receive within the DL BWP of SSB symbols. In this case, there is a disadvantage that the UL opportunity may be reduced. To improve this, the SBFD-aware UE may be allowed to transmit on SSB symbols. In this case, the UE may be configured to transmit UL only in the UL subband based on scheduling, configuration, UE measurement, or priority rules by the base station. If the SBFD-aware UE performs transmission on SSB symbols, it may have a negative impact on SSB detection and measurement.

[0144] It may be permitted to configure SBFD symbols and non-SBFD symbols within a single slot. However, if the frequency of transitions between SBFD and non-SBFD symbols is high, implementation complexity increases, and interruptions in transmission and reception may occur during transitions. Therefore, to avoid frequent transitions between SBFD and non-SBFD symbols, limitations on the maximum number of transition points between SBFD and non-SBFD symbols may be considered from the perspective of SBFD subband configuration. For example, within the TDD UL / DL pattern period, up to two transition points—such as one transition point from a non-SBFD symbol to an SBFD symbol and one transition point from an SBFD symbol to a non-SBFD symbol—can be configured to be placed at the slot boundary or within the slot. Depending on channel conditions and implementation, it may also be necessary to set a guard period between SBFD and non-SBFD symbols.

[0145] The time and frequency positions of subbands within the TDD carrier can be set in various ways. Additionally, whether the base station instructs the terminal on the time and / or frequency positions of the subbands to be used for SBFD operation can also be determined in various ways. In the RRC connection state, the terminal can be configured in one of four methods, typically according to Table 4 below.

[0146] Information regarding subbands notified to the terminal Operation method of the terminal 1st SBFD Operation Option: None (Existing method) 2nd SBFD Operation Option: None SBFD-aware terminal: Introduction of new operation related to SBFD SBFD-non-aware terminal: Existing method 3rd SBFD Operation Option: Subband time location SBFD-aware terminal: Introduction of new operation related to SBFD SBFD-non-aware terminal: Existing method 4th SBFD Operation Option: Subband time location and frequency location SBFD-aware terminal: Introduction of new operation related to SBFD SBFD-non-aware terminal: Existing method

[0147] Among the four options, the fourth SBFD operation option can be set as the criterion for SBFD operation in at least the RRC connection state. SBFD symbols can be used in the random access phase. If random access in SBFD symbols is allowed for SBFD-aware terminals, random access latency can be reduced, the probability of PRACH collisions can be reduced, and the coverage of PRACH and Msg3 can be improved. However, the transmission of PRACH and Msg3 in the UL subband of SBFD symbols may cause cross-link interference (CLI) between terminals. Therefore, additional signaling may be required to compensate for this. For example, a method may be used in which random access in SBFD symbols is allowed only for the transmission of PRACH and Msg3 of symbols configured from TDD-UL- to DL.

[0148] Semi-static configurations of subband time and frequency positions may be used to indicate subband positions for SBFD operation. In the case of semi-static configurations of subband time positions for SBFD operation, the SBFD subband time position may be explicitly or implicitly indicated within a certain period. Additionally, in the case of semi-static configurations of subband frequency positions for SBFD operation, the frequency position of at least the UL subband may be explicitly or implicitly indicated. Typically, for semi-static SBFD, settings regarding the DL subband and guard band may be used as follows. Here, the settings regarding the guard band may be applied only if a guard band exists.

[0149] - 1st DL subband option: The frequency position of the DL subband is explicitly set. The guard band may be implicitly passed to an RB that does not belong to the UL subband or the DL subband.

[0150] - 2nd DL subband option: The number of RBs for the guard band is explicitly set. The DL subband may be implicitly passed to an RB that does not belong to the UL subband or guard band.

[0151] Here, in the case of a semi-static SBFD, the SBFD-aware terminal does not transmit UL channel / signals or receive DL channel / signals in the aware guard band. For a semi-static configuration of subband frequency positions for SBFD operation, the frequency positions of the UL / DL subbands can be transmitted using a Common Resource Block (CRB) grid. For a semi-static configuration of subband positions, the same subband frequency resource can be considered as a baseline in different SBFD symbols.

[0152] An SBFD-aware terminal semi-statically configured as a UL subband within an SBFD symbol configured as a downlink can be configured as follows.

[0153] The terminal may allow UL transmission within the UL subband within the symbol and allow DL reception within the DL subband within the symbol. UL transmission outside the UL subband is not allowed within the symbol. The frequency location of the DL subband may be known to the SBFD-aware terminal. The frequency location of the DL subband may be conveyed to the terminal explicitly or implicitly. Here, within the symbol, UL transmission is within the active UL BWP and DL reception is within the active DL BWP. Whether DL reception outside the semi-statically configured DL subband is allowed in a symbol configured as a downlink for the SBFD-aware UE may depend on the following options.

[0154] - Option 1 (Semi-static SBFD): DL reception outside the semi-statically configured DL subband is not allowed.

[0155] - Option 2: (Dynamic SBFD): DL reception outside of the semi-statically configured DL subband is allowed.

[0156] In addition, for SBFD operation in a flexibly configured symbol, the SBFD recognition terminal can be operated through the first flexible SBFD setting and the second flexible SBFD setting as follows.

[0157] 1. Flexible SBFD Configuration: The terminal is allowed to transmit UL within the UL subband within the symbol, and may be allowed to receive DL within the DL subband within the symbol. However, UL transmission outside the UL subband is not allowed within the symbol. The frequency location of the DL subband may be known to the UE regarding the SBFD. Whether DL reception outside the DL subband is allowed within the symbol can be configured in various ways and is not limited to a specific method.

[0158] Second Flexible SBFD Configuration: Within a symbol, the terminal is allowed to transmit UL within the UL subband, and may allow to receive DL within the DL subband. The frequency location of the DL subband may be known to the SBFD-aware UE. RBs outside the UL subband may be used as UL or DL, excluding guard bands, and from the base station's perspective, the transmission direction of all RBs within a symbol is used identically.

[0159] SBFD-aware UE operation, whether signaling of the guard band is required, and whether symbols can be converted into DL-only symbols can be configured in various ways and are not limited to any specific method.

[0160] Here, in both the first dynamic SBFD configuration and the second dynamic SBFD configuration, within a symbol, UL transmission is within the active UL BWP and DL reception is within the active DL BWP. For all RBs outside the UL subband, the terminal may be configured so that it cannot simultaneously use separate RBs for DL ​​and UL.

[0161] In addition, whether DL reception outside the semi-statically configured DL subband and UL transmission outside the semi-statically configured UL subband are allowed in dynamically configured symbols for SBFD-aware UEs may depend on the following options.

[0162] - Option 1 (Semi-static): DL reception outside the semi-statically configured DL subband is not allowed, and UL transmission outside the semi-statically configured UL subband is not allowed.

[0163] - Option 2 (Dynamic SBFD): DL reception outside the semi-statically configured DL subband is allowed. However, UL transmission outside the semi-statically configured UL subband is not allowed.

[0164] - Option 3 (Dynamic SBFD): DL reception outside the semi-statically configured DL subband is allowed, and UL transmission outside the semi-statically configured UL subband is allowed.

[0165] When using dynamic SBFD configuration instead of semi-static SBFD configuration, the following phenomena may occur. Compared to semi-static SBFD, dynamic SBFD can adapt better to UL / DL resource requirements based on UL / DL traffic load.

[0166] Dynamic SBFD increases base station implementation complexity due to dynamic antenna / panel switching and filter / RF tuning, and may result in resource loss due to switching times. Additionally, the CLI between base stations increases, and scheduling complexity increases. If a terminal supports dynamic SBFD, UE implementation complexity may increase, and the CLI between terminals may increase due to dynamic SBFD.

[0167] If dynamic SBFD is supported, the following options may be considered.

[0168] Option 1: Dynamic SBFD can be configured via DCI used to schedule DL reception outside the semi-statically configured SBFD DL subband and / or UL transmission outside the semi-statically configured SBFD UL subband.

[0169] - Option 2: Dynamic SBFDs can be configured via a non-scheduling DCI. The non-scheduling DCI can indicate whether a symbol is an SBFD symbol.

[0170] - Option 3: Dynamic SBFD can be set by MAC-CE indicating whether a symbol is an SBFD symbol.

[0171] In addition, inter-slot / in-slot / inter-repetition / inter-group frequency hopping using PUSCH / PUCCH DMRS bundling can be further considered. Accordingly, resource allocation in the frequency domain including frequency hopping, resource allocation in the time domain, and procedures regarding the power and spatial domains can be improved.

[0172] If the boundary between the RBG and SBFD subbands is not aligned, it may be determined whether the DL RBG portion inside / outside the DL subband and the UL RBG portion inside / outside the UL subband can be used for resource allocation within the frequency domain. For an SBFD-aware terminal, the DL RBG portion inside the DL subband and the UL RBG portion inside the UL subband may be used for better resource utilization. However, at least for a semi-static SBFD, the RBG portion outside the DL subband may not be used for DL ​​reception and the RBG portion outside the UL subband may not be used for UL transmission.

[0173] In the case of semi-static SBFD, for CSI reporting subbands that overlap with SBFD subband boundaries, CSI reporting may be performed for the SBFD-aware terminal based on CSI-RS resources excluding CSI-RS resources outside the DL subband. In the case of semi-static SBFD, for CSI-RS resources that overlap with SBFD subband boundaries, only CSI-RS resources within the DL subband may be valid for the SBFD-aware terminal. For the SBFD-aware terminal, PRG(s) with a size of 2 and 4 overlapping with subband boundaries for PDSCH, and settings for broadband precoders in the case of discontinuous DL subbands may also be additionally configured.

[0174] In the case of PRGs that overlap with subband boundaries, if a portion of the DL PRG within the DL subband can be used, scheduling flexibility and resource utilization can be improved, but the channel estimation quality is degraded compared to the PRG due to the limited RB of the partial PRG, and UE complexity may increase to implement these functions.

[0175] If the PRG is determined to be broadband, the following two options may be considered. The first is an option where non-contiguous frequency resources are allocated across two DL subbands, but adjacent frequency resources can be allocated within each DL subband. The second is an option where discontinuous frequency resources cannot be allocated across two DL subbands.

[0176] For frequency resource allocation for CSI-RS in the downlink subband for SBFD-aware terminals, the following four options may be considered, and the CSI-RS sequence generation procedure may be applied as is with the existing procedure.

[0177] - Option 1: Two connected adjacent CSI-RS resources

[0178] - Option 2: One CSI-RS resource

[0179] - Option 2-1: Allocation of non-contiguous CSI-RS resources

[0180] - Option 2-2: Allocation of a single continuous CSI-RS resource along with the discontinuous CSI-RS resource derived by excluding frequency resources outside the DL subband

[0181] For UL transmission and DL reception via SBFD and non-SBFD symbols in different slots (each transmission / reception within the slot contains either all SBFD symbols or all non-SBFD symbols), the following methods may be considered. First, a method may be considered where transmission / reception is performed using only SBFD symbols or only non-SBFD symbols. In this case, a procedure may be used to indicate that the transmission / reception status is valid within one symbol type and invalid within another. Second, a method may be considered where transmission / reception is performed using both SBFD and non-SBFD symbols. Which method is used can be determined through base station configuration or scheduling. Frequency resources, power control, and beam / space relationships regarding all transmissions / receptions may be the same for the first method, but may be configured differently for the second method and may require additional signaling.

[0182] Frequency resource allocation for an SBFD-aware terminal can be performed in the following way. First, frequency domain resource allocation for SBFD slots and non-SBFD slots can be determined separately. In this case, separate frequency domain resource allocation settings / indications for SBFD slots and non-SBFD slots can be performed, or separate frequency resources for SBFD slots and non-SBFD slots can be determined according to a single frequency domain resource allocation setting / indication, and a single frequency domain resource allocation setting / indication and RB offset can be used.

[0183] Secondly, rate matching or puncturing may be performed on DL / UL channels / signals at RBs outside the DL / UL subband. Thirdly, DL / UL channels / signals that overlap with RBs outside the DL / UL subband in SBFD slots may be deleted or deferred.

[0184] If there are physical channels / signals mapped to SBFD and non-SBFD symbols within a slot, the terminal may transmit or not transmit the physical channels / signals within the slot, or transmit or receive the physical channels / signals within the slot only under specific conditions. Here, specific conditions may depend on whether phase continuity can be maintained between SBFD and non-SBFD symbols, whether transmit and receive parameters such as power control, space / QCL, and UL timing applied to SBFD and non-SBFD symbols are the same or different, and whether there is a guard period between SBFD and non-SBFD symbols.

[0185] For SBFD-aware terminals, two CSI reporting configurations are delivered to the terminal for CSI reports associated with periodic / semi-permanent CSI-RS, and one configuration may be associated with SBFD symbols and the other with non-SBFD symbols. In this case, the CSI-RS associated with each CSI-ReportConfig can be limited to only SBFD symbols or non-SBFD symbols through the appropriate periodic base station configuration. However, this method may limit the flexibility of base station configuration. Additionally, a single CSI reporting configuration may be associated with both SBFD symbols and non-SBFD symbols. In this case, measurement limits may be configured according to existing standards so that the terminal does not average CSI measurements across SBFD and non-SBFD symbols.

[0186] For SRS, PUCCH, and PUSCH of SBFD symbols and non-SBFD symbols in different slots, they can be configured to have separate resources, FH parameters, UL power control parameters, and / or beam / space relationships.

[0187] The base station can configure the CORESET and search space in such a way that the MO of the search space occurs in either an SBFD or non-SBFD symbol, or the MO of the search space occurs in both SBFD and non-SBFD symbols, but the associated CORESET does not overlap with the DL subband boundary of the SBFD symbol.

[0188] When configuring the CORESET and search space such that MOs of the search space occur in both SBFD and non-SBFD symbols and the associated CORESET overlaps with the DL subband boundary of the SBFD symbol, the following options may be considered.

[0189] - Option 1: Separate valid resources for CORESET from SBFD symbols and non-SBFD symbols

[0190] - Option 2: Rate matching or punching in the REG of the PDCCH outside the DL subband

[0191] - Option 3: If a PDCCH candidate is mapped to one or more REs that overlap with REs outside the DL subband, the terminal does not monitor the PDCCH candidate.

[0192] - Option 4: Delete the search space if the connected CORESET overlaps with an RB outside the DL subband.

[0193] - Option 5: Separate the search space associated with the CORESET of SBFD and non-SBFD symbols

[0194] Interference within the base station itself due to time misalignment can also be considered. Time misalignment between UL reception and DL transmission caused by the setting of non-zero timing advance at the terminal can cause increased interference, assuming there is no base station transmission chain failure and no filtering of the DL subband in the base station reception chain.

[0195] The increase in self-interference of the UL subband due to time misalignment between UL reception and DL transmission at the base station can be very small (~1 dB) considering the failure of the base station transmission chain and the filtering of the DL subband at the base station reception chain. Filtering to suppress self-interference of the DL subband at the base station reception chain may result in some switching time / delay to bypass the filter in UL symbols and may result in insertion loss.

[0196] The present disclosure describes a technology related to subbad full-duplex (SBFD) in a wireless communication system. In particular, the present disclosure proposes various embodiments related to signaling and procedures involving SBFD symbols and non-SBFD symbols. Here, SBFD refers to a technology that allows simultaneous transmission and / or reception of downlink (hereinafter 'DL') and uplink (hereinafter 'UL') in a portion of the total system bandwidth. Through SBFD, cell yield can be improved, latency reduced, transmission and reception signal reliability improved, and coverage increased.

[0197]

[0198] FIG. 10 illustrates an example of SBFD configuration in a wireless communication system according to one embodiment of the present disclosure. Referring to FIG. 10, a portion of the system bandwidth may be configured as a DL subband and a UL subband for SBFD. A base station may transmit configuration information regarding the UL / DL subbands associated with SBFD to a terminal via upper-layer signaling (e.g., SIB, RRC, etc.). The terminal may perform transmit and / or receive operations based on the UL / DL subband configuration information configured by the base station. For example, the terminal may receive or transmit data from a base station or another terminal based on the UL / DL subband configuration information configured by the base station.

[0199] As an example of UL / DL subband configuration for SBFD operation, the UL / DL subband may be configured on a carrier operating in TDD. The UL / DL subband may be configured on a slot or symbol configured as downlink or flexible among TDD slots or symbols. One slot may be configured with an OFDM (Orthogonal Frequency Division Multiplexing) symbol configured as a UL / DL subband (hereinafter, “SBFD symbol”) and a symbol not configured as a full-duplex subband (hereinafter, “non-SBFD symbol”).

[0200] According to one example of the present disclosure, a time domain pattern and period for at least one SBFD symbol may be configured. For example, a specific SBFD symbol pattern may be configured continuously within a TDD UL / DL area configured in an upper layer. For example, the SBFD symbol pattern may be configured continuously according to the pattern and period of the TDD UL / DL (e.g., parameters configured by TDD-UL-DL-Config, TDD-UL-DL-ConfigCommon, etc.). For example, the SBFD symbol pattern may be repeated periodically. In this case, the period of the SBFD symbol pattern may be the same as the period of the TDD UL / DL pattern. Here, configuration information for at least one of a start slot index, a start symbol index within the start slot index, a last slot index, or a last symbol index within the last slot index may be provided to set the pattern in the time domain for the SBFD symbol.

[0201] According to one example of the present disclosure, frequency positions corresponding to UL / DL subbands within an SBFD symbol may be explicitly configured through upper-level signaling. For example, the frequency positions and bandwidth sizes of UL subbands, and the frequency positions and bandwidth sizes of DL subbands, may each be configured through upper-level signaling. Here, a guardband may be located between the UL subband and the DL subband. For example, the guardband may correspond to a band that is not composed of the UL subband and the DL subband. The frequency positions of UL / DL subbands may be configured independently according to the subcarrier spacing (SCS) value. In other words, UL / DL subbands with different SCS values ​​may have different frequency positions. Conversely, UL / DL subbands with different SCS values ​​may have the same frequency position. For the configuration of UL / DL subbands within an SBFD symbol, a starting PRB index and a bandwidth size for each subband may be indicated for each subband. For setting UL and / or DL ​​subbands within the SBFD symbol, a start PRB index and a bandwidth size for each subband may be indicated for each subband.

[0202]

[0203] According to one example of the present disclosure, resources may be allocated for UL transmission and DL reception. The allocated resources may be scheduled across SBFD symbols and non-SBFD symbols. Here, the SBFD symbols and non-SBFD symbols may be symbols located in different slots. In this case, the terminal may receive a configuration for resource allocation from signaling. For example, the configuration for resource allocation may be as follows.

[0204] - Configuration 1: UL transmission or DL ​​reception may be performed on only one of either SBFD symbols or non-SBFD symbols. That is, the terminal may determine that only the resources assigned to one symbol type among the resources allocated across SBFD symbols or non-SBFD symbols are valid. For example, the terminal may perform UL transmission or DL ​​reception using only the resources assigned to SBFD symbols. As another example, the terminal may perform UL transmission or DL ​​reception using only the resources assigned to non-SBFD symbols. In the case of Configuration 1, the valid symbol type (e.g., whether the valid symbol type is an SBFD symbol or a non-SBFD symbol) may be additionally explicitly set or implicitly determined based on scheduling information for UL and / or DL ​​transmission and reception.

[0205] -Configuration 2: UL transmission or DL ​​reception can be performed on SBFD symbols and non-SBFD symbols. That is, the terminal can determine that resources allocated across SBFD symbols or non-SBFD symbols are valid. For example, the terminal can perform communication using resources allocated to SBFD symbols and resources allocated to non-SBFD symbols. In this case, the terminal can use resources allocated to SBFD symbols and resources allocated to non-SBFD symbols without distinction.

[0206]

[0207] The aforementioned Configuration 1 or Configuration 2 may be signaled by a base station. In other words, a terminal may decide whether to operate based on Configuration 1 or based on Configuration 2 according to instructions from the base station. The signaling may include upper-layer signaling (e.g., signaling using RRC messages), MAC signaling (e.g., signaling using MAC CE), or physical layer signaling. The signaling for indicating Configuration 1 or Configuration 2 may include cell-specific signaling or terminal-specific signaling. For example, if Configuration 1 or Configuration 2 is configured by cell-specific signaling, terminals included in a single cell may operate based on the same Configuration. If Configuration 1 or Configuration 2 is configured by terminal-specific signaling, each terminal may operate based on Configuration 1 or Configuration 2 based on the received signaling. As another example, the signaling may indicate different Configurations for each physical layer channel. In other words, transmission or reception based on different configurations can be performed for each physical layer channel (e.g., PDSCH, PDCCH, PUCCH, PUSCH, SRS, CSI-RS). For example, a terminal can perform reception of PDSCH based on configuration 1 and transmission of PUSCH based on configuration 2, and these configurations can be configured per terminal or per cell. That is, cell-specific signaling and terminal-specific signaling may include physical layer channel-specific configurations.

[0208]

[0209] The UL / DL subband for SBFD operation can be configured via cell-specific signaling (e.g., SIB or cell-common RRC) or terminal-specific signaling (e.g., terminal-specific RRC). Here, the configuration and subcarrier spacing of the UL / DL subband for SBFD can be configured via the same type of signaling. For example, if the UL / DL subband configuration for SBFD is configured by cell-specific signaling, the subcarrier spacing of the corresponding UL / DL subband can also be configured via cell-specific signaling. As an example, the SCS of the UL / DL subband can follow the SCS configuration value included in the TDD configuration configured for cell-common (e.g., the value configured by referenceSubcarrierSpacing in the TDD-UL-DL-ConfigCommon configuration information).

[0210] Meanwhile, in a wireless communication system (e.g., a 5G NR system), a Bandwidth Part (hereinafter BWP) to be used for actual transmission and reception within the total system bandwidth may be configured for purposes such as improving cell yield, reducing latency, and reducing terminal power consumption. A base station may configure one or more BWPs for the terminal for transmission and / or reception in the UL and DL. At least one BWP may be configured from the base station to the terminal. One of the configured BWPs may be activated. The terminal and the base station may perform communication using the activated BWP.

[0211] For example, the following parameters may be configured for each DL BWP and UL BWP for the terminal.

[0212] - Subcarrier spacing (e.g., subcarrierSpacing)

[0213] - CP (cyclic prefix) length (e.g., cyclicPrefix)

[0214] - Frequency location and bandwidth of each BWP (e.g., locationAndBandwidth)

[0215] - ID of each BWP (e.g., BWP-Id)

[0216] When the terminal and / or base station operates in the TDD band, DL BWP and UL BWP configured with the same BWP ID are connected to each other, and DL BWP and UL BWP having the same BWP ID can be activated. Additionally, when the terminal and / or base station operates in the TDD band, the center frequencies of DL BWP and UL BWP may be the same.

[0217] A terminal can receive a downlink physical layer channel (e.g., PDCCH (Physical Downlink Control Channel) or PDSCH (Physical Downlink Shared Channel)) based on the SCS value and CP length value configured in the DL BWP at the activated DL BWP. Hereinafter, receiving or transmitting a physical layer channel may refer to receiving or transmitting a signal through the physical layer channel. Receiving or transmitting at the activated BWP may refer to receiving or transmitting using resources within the activated BWP. Likewise, a terminal can transmit an uplink physical layer channel (e.g., PUCCH (Physical Uplink Control Channel) or PUSCH (Physical Uplink Shared Channel)) based on the SCS value and CP length value configured in the UL BWP at the activated UL BWP.

[0218]

[0219] FIG. 11 illustrates an example of a system configuration that appears by a combination of a configuration for SBFD and a configuration for BWP in a wireless communication system according to one embodiment of the present disclosure. Hereinafter, the configuration for SBFD may be referred to as the SBFD configuration, and the configuration for BWP may be referred to as the BWP configuration.

[0220] Referring to FIG. 11, multiple BWPs, e.g., BWP#1 and BWP#2, are configured, BWP#1 is activated, and BWP#2 is deactivated. Additionally, in the example of FIG. 11, UL / DL subbands for SBFDs are configured in the second and third slots. Here, for SBFD symbols configured with UL / DL subbands, resource areas (e.g., Physical Resource Blocks (PRBs)) available for actual UL / DL transmission and / or reception can be defined as follows.

[0221] - UL Usable PRB: UL subband frequency resource area within an activated UL BWP

[0222] - DL Available PRB: DL subband frequency resource area within an active DL BWP

[0223] That is, the base station and the terminal can perform uplink transmission and / or reception for SBFD symbols through the UL available PRB in the active UL BWP, and perform downlink transmission and / or reception through the DL available PRB in the active DL BWP.

[0224]

[0225] In the following, a procedure for applying downlink preemption in a wireless communication system with SBFD applied is described. The procedure for applying downlink preemption may be performed based on configuration information related to preemption and / or configuration information related to SBFD. When downlink preemption is applied, the terminal may receive and decode PDSCH based on downlink preemption, and the base station may schedule and transmit PDSCH based on downlink preemption.

[0226]

[0227] A mobile communication system (e.g., a 5G NR system) supports a downlink preemption operation that directs the interruption of a portion of an existing scheduled downlink transmission. FIG. 12 illustrates the concept of downlink preemption. Referring to FIG. 12, if a new downlink transmission (e.g., urgent data traffic for URLLC (Ultra Reliable Low Latency Communication)) occurs after an existing scheduled downlink transmission has started, this new downlink transmission may be scheduled and transmitted in a portion of the resource area for the existing scheduled downlink transmission. In this case, a portion of the resource area of ​​the existing scheduled downlink transmission may be punctured, and the transmission of the new downlink data may be prioritized. To this end, the base station may transmit a DCI (Downlink control information) format 2_1 to the terminal, which directs that a portion of the existing downlink transmission has been interrupted. Based on the information indicated by DCI format 2_1, the terminal can determine that the previously received downlink transmission was not transmitted in some resource areas.

[0228] For downlink preemption operation, the base station can configure the following parameters to the terminal through upper-layer signaling.

[0229] int-RNTI: RNTI value applied to DCI format 2_1

[0230] timeFrequencySet: Time and frequency resource granularity for interpreting transmission interruption indicators

[0231] dci-PayloadSize: Payload size of DCI format 2_1

[0232] int-ConfigurationPerServingCell: Indicator field location per cell

[0233]

[0234] A method for determining the time and frequency resource units to which DCI Format 2_1 is applied is proposed as follows. Frequency axis PRB set (RB set In the method of configuring ), the terminal may assume the PRB sets as activated DL BWPs. In this case, RB set The number of PRBs existing within is B INT It is defined as. Symbol set (S set In the method of configuring ), if the terminal receives DCI format 2_1 via a PDCCH transmitted in a specific slot, the terminal prior to the first symbol of the slot in which the PDCCH was received Symbols symbol set (S set It can be defined as ). Here, T INT is the PDCCH monitoring cycle, is the number of symbols per slot, is the SCS (subcarrier spacing) setting of the serving cell mapped to each field of DCI format 2_1, corresponds to the SCS setting value configured in the downlink BWP that received the corresponding PDCCH. If there are symbols within the above symbol set that are configured as uplink symbols from TDD UL / DL pattern configuration information (e.g., tdd-UL-DL-ConfigurationCommon), the terminal [represents] the corresponding uplink symbols in the above symbol set S setIt can be excluded from. The finally determined symbol set S set The number of symbols included is N INT It is defined as.

[0235] The method of applying the above downlink preemption may be based on configuration information. For example, downlink preemption may be controlled differently depending on the timeFrequencySet field of the configuration information.

[0236] FIG. 13a illustrates an example of how a symbol-PRB group is configured when the timeFrequencySet is configured as 'set0' following the application of downlink preemption. Referring to FIG. 13a, when the timeFrequencySet is configured as 'set0', the terminal can map the 14 bits of the Most Significant Bit (MSB) of the field in DCI format 2_1 one-to-one for each of 14 consecutive symbol groups. In this case, each symbol group is N INT / 14 symbols are included. If the MSB bit value is indicated as 1, the terminal may assume that there was no downlink transmission in the symbol group mapped to that bit. In other words, the symbol group mapped to that bit may be a symbol group with downlink preemption applied. If the MSB bit value is indicated as 0, it may assume that there was a downlink transmission in the symbol group mapped to that bit. In other words, the symbol group mapped to that bit may be a symbol group without downlink preemption applied.

[0237] FIG. 13b illustrates an example of how a symbol-PRB group is configured when the timeFrequencySet is set to 'set1' following the application of downlink preemption. If the timeFrequencySet is set to 'set1', the terminal can regard the 14 bits of the Most Significant Bit (MSB) of the field in DCI format 2_1 as seven bit pairs, each consisting of 2 bits. Here, each bit pair can be mapped one-to-one to seven consecutive symbol groups. In this case, each symbol group is N INT It contains 7 symbols. The first bit of each bit pair is B within the symbol group corresponding to that bit pair. INT It can correspond to the first PRB group (e.g., RBset#1) consisting of / 2 PRBs, and the second bit is B within the symbol group corresponding to that bit pair. INT It may correspond to a second PRB group (e.g., RBset#2) composed of / 2 PRBs. Here, the first PRB group may include PRBs that have higher values ​​in the frequency resource domain than the second PRB group. If the bit value of the MSB is indicated as 1, the terminal may assume that there was no downlink transmission in the symbol group mapped to that bit. In other words, the symbol group mapped to that bit may be a symbol group with downlink preemption applied. If the bit value of the MSB is indicated as 0, it may assume that there was a downlink transmission in the symbol group mapped to that bit. In other words, the symbol group mapped to that bit may be a symbol group without downlink preemption applied.

[0238] More specific details regarding downlink pre-amplification operation are shown in Table 5.

[0239] 11.2Interrupted transmission indicationIf a UE is providedDownlinkPreemption, the UE is configured with an INT-RNTI provided byint-RNTIfor monitoring PDCCH conveying DCI format 2_1 [5, TS 38.212]. The UE is additionally configured with- a set of serving cells byint-ConfigurationPerServingCellthat includes a set of serving cell indexes provided by correspondingservingCellIdand a corresponding set of locations for fields in DCI format 2_1 bypositionInDCI- an information payload size for DCI format 2_1 bydci-PayloadSize- an indication granularity for time-frequency resources bytimeFrequencySetIf a UE detects a DCI format 2_1 for a serving cell from the configured set of serving cells, the UE may assume that no transmission to the UE is present in PRBs and in symbols that are indicated by the DCI format 2_1, from a set of PRBs and a set of symbols of the last monitoring period. The indication by the DCI format 2_1 is not applicable to receptions of SS / PBCH blocks.The set of PRBs is equal to the active DL BWP as defined in clause 12 and includes. PRBs.If a UE detects a DCI format 2_1 in a PDCCH reception in a slot, the set of symbols is the last symbols prior to the first symbol of the PDCCH reception in the slot where is the PDCCH monitoring periodicity provided by the value ofmonitoringSlotPeriodicityAndOffset,as described in clause 10.1, is the number of symbols per slot, is the SCS configuration for a serving cell with mapping to a respective field in the DCI format 2_1, is the SCS configuration of the DL BWP where the UE receives the PDCCH with the DCI format 2_1. If the UE is providedtdd-UL-DL-ConfigurationCommon, symbols indicated as uplink bytdd-UL-DL-ConfigurationCommonare excluded from the last symbols prior to the first symbol of the PDCCH reception in the slot. The resulting set of symbols includes a number of symbols that is denoted as .The UE does not expect to be provided values of , , and resulting to a value of that is not an integer. The UE does not expect to be configured bymonitoringSymbolsWithinSlotwith more than one PDCCH monitoring occasion for DCI format 2_1 in a slot.A UE is provided the indication granularity for the set of PRBs and for the set of symbols bytimeFrequencySet.If the value oftimeFrequencySetis 'set0', 14 bits from MSB of a field in DCI format 2_1 have a one-to-one mapping with 14 groups of consecutive symbols from the set of symbols where each of the first symbol groups includes symbols, each of the last symbol groups includes symbols, a bit value of 0 indicates transmission to the UE in the corresponding symbol group and a bit value of 1 indicates no transmission to the UE in the corresponding symbol group.If the value oftimeFrequencySetis 'set1', 7 pairs of bits from MSB of a field in the DCI format 2_1 have a one-to-one mapping with 7 groups of consecutive symbols where each of the first symbol groups includes symbols, each of the last symbol groups includes symbols, a first bit in a pair of bits for a symbol group is applicable to the subset of first PRBs from the set of PRBs, a second bit in the pair of bits for the symbol group is applicable to the subset of last PRBs from the set of PRBs, a bit value of 0 indicates transmission to the UE in the corresponding symbol group and subset of PRBs, and a bit value of 1 indicates no transmission to the UE in the corresponding symbol group and subset of PRBs.

[0240]

[0241] FIG. 14 illustrates an example of a resource group to which downlink preemption is applied in an SBFD system. Referring to FIG. 14, a downlink transmission interruption instruction (hereinafter referred to as the preemption instruction) indicated by DCI format 2_1 may indicate that downlink transmission has been interrupted in a symbol or symbol group set with an SBFD symbol. In this case, at least one symbol and PRB group mapped to each bit of the preemption instruction field may include PRBs that do not exist within the downlink subband. That is, the downlink preemption instruction may indicate a preemption operation for PRBs included in the uplink subband rather than downlink resources (e.g., PRBs existing within the downlink subband). In this case, a new terminal operation is required to determine at least one symbol and PRB group mapped to the field value of the preemption instruction, or to identify a downlink transmission interruption based on the preemption instruction field value. The present disclosure proposes techniques to solve this problem.

[0242]

[0243] FIG. 15 illustrates a downlink reception procedure based on a preemption indicator according to one embodiment of the present disclosure. The procedure of FIG. 15 may be performed by a terminal. The terminal may be understood as a UE.

[0244] Referring to FIG. 15, in step S1501, the terminal receives first configuration information. The first configuration information may include information related to SBFD. For example, the first configuration information may include information about the locations of SBFD symbols and SBFD subbands.

[0245] In step S1503, the terminal receives second configuration information. The second configuration information may include information related to preemption. For example, the second configuration information may include information related to a resource group (e.g., a symbol-PRB group) which is a unit for applying preemption. For example, the second configuration information may include information related to the frequency axis and time axis sizes of the resource group.

[0246] In step S1505, the terminal may receive PDSCH and control information (e.g., DCI). The control information may include a preemption indicator. The preemption indicator may include information indicating a resource group (e.g., a symbol-PRB group) to which downlink preemption is applied. The PDSCH and control information may be received through a downlink resource. The downlink resource may include at least one of a downlink band or a downlink subband in the frequency domain. The downlink resource may include at least one of an SBFD symbol or a non-SBFD symbol in the time domain.

[0247] In step S1507, the terminal can determine a resource group to which the preemption indicator is effectively applied. For example, the resource group to which the preemption indicator is effectively applied may be indicated by the base station. As another example, the resource group to which the preemption indicator is effectively applied may be predetermined. The resource group to which the preemption indicator is effectively applied may include at least one of a resource group located in an SBFD symbol or a resource group located in a non-SBFD symbol. In other words, the resource group to which the preemption indicator is effectively applied may be determined according to the type of symbol.

[0248] In step S1509, the terminal can process PDSCH based on preemption indicators and symbol types. For example, the terminal can process PDSCH in a resource group determined based on preemption indicators and symbol types. Here, the terminal can perform rate matching or puncturing to decode PDSCH. In other words, the terminal can process PDSCH by taking rate matching or puncturing into account.

[0249]

[0250] FIG. 16 illustrates a downlink transmission procedure based on a preemption indicator according to one embodiment of the present disclosure. The procedure of FIG. 16 may be performed by a base station. The base station may be understood as an NB, eNB, or gNB.

[0251] Referring to FIG. 16, in step S1601, the base station transmits first configuration information. The first configuration information may include information related to SBFD. For example, the first configuration information may include information about the locations of SBFD symbols and SBFD subbands.

[0252] In step S1603, the base station transmits second configuration information. The second configuration information may include information related to preemption. For example, the second configuration information may include information related to a resource group (e.g., a symbol-PRB group) which is a unit to which downlink preemption can be applied. For example, the second configuration information may include information related to the magnitude of the frequency axis and time axis of the resource group.

[0253] In step S1605, the base station may determine to apply preemption and transmit PDSCH. For example, the base station may transmit PDSCH based on resources excluding the resource group to which preemption is applied. The base station may schedule and transmit emergency data traffic to the resource group to which preemption is applied. Here, PDSCH and emergency data traffic may be transmitted to different terminals or to the same terminal.

[0254] In step S1607, the base station may transmit a preemption indicator. The preemption indicator may include information indicating a resource group to which preemption is applied. The preemption indicator may indicate at least one of the resource groups according to the second configuration information. The preemption indicator may be transmitted via the DCI. In other words, the preemption indicator may be included in the DCI.

[0255]

[0256] Detailed embodiments for processing a preempted PDSCH based on a preemption indicator are described below. A terminal can identify a resource group to which a preemption is applied based on a preemption indicator and process the PDSCH based on the identified resource group. Detailed procedures for configuring, identifying, or determining the validity of a resource group or a preemption indicator are proposed by the following embodiments.

[0257]

[0258] <1st Embodiment: Method for Determining Symbol Type to Which Preemption Indicator Is Applied>

[0259] According to one embodiment of the present invention, the symbol type to which the downlink preemption indicator is applied may be limited to one of an SBFD symbol or a non-SBFD symbol.

[0260] For example, a downlink preemption indicator may be applied only to non-SBFD symbols. FIG. 17 illustrates an example where a downlink preemption indicator is applied to non-SBFD symbols. Referring to FIG. 17, DCI format 2_1 transmitted in slot 5 indicates a preemption for Symbol-RPB Group #1 present in slot 0 and Symbol-PRB Group #3 present in slot 1. In this case, the terminal may apply the preemption indicator only to PDSCH#1 transmitted in slot 0, which corresponds to non-SBFD symbols. That is, the terminal may consider that there is no downlink transmission in the time and frequency resources corresponding to Symbol-PRB Group #1 for PDSCH#1. For example, the terminal may ignore the indicated information for Symbol-PRB Group #3 for which a downlink preemption is indicated. That is, the terminal may consider that there is a downlink transmission for PDSCH#2. As another example, the terminal may expect that DCI format 2_1 indicates a downlink preemption only for symbol-PRB groups present in non-SBFD symbols (e.g., the bit value of the preemption indicator is 1), and may not expect a downlink preemption to be indicated for symbol-PRB groups present in SBFD symbols.

[0261] As another example, a downlink preemption indicator may be applied only to SBFD symbols. In the example illustrated in FIG. 17, DCI format 2_1 transmitted in slot 5 indicates a preemption for Symbol-RPB Group #1 in slot 0 and Symbol-PRB Group #3 in slot 1. In this case, the terminal can apply the corresponding preemption indicator only to PDSCH#2 transmitted in slot 1, which corresponds to the SBFD symbols. That is, the terminal can assume that no downlink transmission occurred in the time and frequency resources corresponding to Symbol-PRB Group #3 for PDSCH#2. The terminal can ignore the indicated information for Symbol-PRB Group #1, for which a downlink preemption was indicated. That is, the terminal can assume that all downlink transmissions occurred for PDSCH#1. In another example, the terminal may expect that DCI format 2_1 indicates downlink preemption (indicates bit value as 1) only for symbol-PRB groups present in SBFD symbols, and may not expect that downlink preemption (indicates bit value as 1) is indicated for symbol-PRBs present in non-SBFD symbols.

[0262] As another example, a downlink preemption indicator may be applied to either a non-SBFD symbol or an SBFD symbol. The valid symbol type to which the downlink preemption indicator is applied may be indicated via MAC CE signaling. Specifically, a terminal may receive from a base station via MAC CE whether the symbol type to which the downlink preemption indicator is to be applied is an SBFD symbol or a non-SBFD symbol. Subsequently, the terminal may apply the contents of the downlink preemption indicator indicated by the DCI to the symbol corresponding to the valid symbol type.

[0263] As another example, the symbol type to which the downlink preemption indicator is to be applied may be explicitly configured. For example, a base station may configure information regarding the valid symbol type (e.g., SBFD symbol or non-SBFD symbol) to which downlink preemption is to be applied to a terminal through upper-layer signaling. For example, configuration information regarding the valid symbol type may be included as part of the downlink preemption configuration information (e.g., DownlinkPreemption). The valid symbol type may be configured as at least one of the following: SBFD symbol is valid, non-SBFD symbol is valid, or both SBFD symbol and non-SBFD symbol are valid.

[0264] As another example, whether to apply downlink preemption indicator content may be determined based on the valid symbol type configuration configured in the PDSCH. For example, the configuration information for SBFD may include configuration information for one of the following configurations for uplink transmission and / or downlink reception. Alternatively, if neither of the following configuration #1 or configuration #2 is included, the terminal may perform a default operation. For example, the default operation may be an operation that considers a valid symbol type based on configuration #1 as an SBFD symbol, an operation that considers a valid symbol type based on configuration #1 as a non-SBFD symbol, or an operation based on configuration #2.

[0265] Configuration #1: Uplink transmission and / or downlink reception may be restricted to only one symbol type, either SBFD symbols or non-SBFD symbols. That is, for uplink transmission and / or downlink reception scheduled across SBFD symbols and non-SBFD symbols, transmission and / or reception may be performed only if transmission and / or reception existing in one symbol type, either SBFD symbols or non-SBFD symbols, are determined to be valid. In the case of Configuration #1, the valid symbol type (e.g., SBFD symbols or non-SBFD symbols) may be explicitly configured by additional configuration information or implicitly determined based on scheduling information for uplink transmission and / or downlink reception.

[0266] Configuration #2: Uplink transmission and / or downlink reception are considered valid for both SBFD symbols and non-SBFD symbols. That is, uplink transmission and / or downlink reception scheduled across SBFD symbols and non-SBFD symbols are all determined to be valid, and such transmission and reception can be performed.

[0267] If the terminal determines that the valid symbol type for the PDSCH configured as Configuration #1 is configured or determined to be an SBFD symbol (i.e., pre-emption is valid for non-SBFD symbols), it may apply the contents of the downlink pre-emption indicator in a limited manner only to the valid symbol types for transmission and / or reception. Otherwise, it may ignore the contents of the downlink pre-emption indicator or not perform monitoring for DCI format 2_1.

[0268] As another example, the symbol type to which the downlink preemption indicator is to be applied may be implicitly determined based on SBFD configuration information. The base station may configure the terminal with the above configuration #1 or configuration #2 as part of the SBFD configuration information. If configured with configuration #1 and the valid symbol type is configured as SBFD, the terminal may consider the valid symbol type to which the downlink preemption is to be applied as an SBFD symbol. If configured with configuration #2 and the valid symbol type is configured as non-SBFD, the terminal may consider the valid symbol type to which the downlink preemption is to be applied as a non-SBFD symbol. If configured with configuration #2, the terminal may consider the valid symbol type to which the downlink preemption is to be applied as both an SBFD symbol and a non-SBFD symbol.

[0269] FIG. 18 illustrates a procedure for determining a symbol type to which a preemption is applied according to one embodiment of the present disclosure. The procedure of FIG. 18 may be performed by a terminal.

[0270] In step S1801, the terminal receives first configuration information and second configuration information. The first configuration information may include information related to SBFD. The second configuration information may include information regarding downlink preemption.

[0271] In step S1803, the terminal receives a PDSCH and a preemption indicator. The PDSCH may be preempted by a base station. The preemption indicator may be included in the DCI. In other words, the DCI may include information indicating a preempted resource group (e.g., a symbol-PRB group) among the resource regions scheduled for the PDSCH.

[0272] In step S1805, the terminal determines the symbol type to which preemption is applied. The symbol type to which preemption is applied may include at least one of SBFD symbols or non-SBFD symbols. The symbol type to which preemption is applied may be indicated based on DCI, MAC CE, RRC signaling, or second configuration information. The symbol type to which preemption is applied may be explicitly indicated, or may be implicitly indicated based on the symbol type for which PDSCH is valid. For example, the symbol type for which PDSCH is valid may be determined as the symbol type to which preemption is applied.

[0273] In step S1807, the terminal processes the PDSCH based on the preemption indicator and symbol type. The terminal may process the PDSCH received in step S1803 based on the preemption indicator and symbol type. For example, the terminal may perform puncturing or rate matching and decoding on the PDSCH based on the preemption indicator and symbol type.

[0274]

[0275] <Second Embodiment: Downlink Preemption Operation in Non-SBFD Symbols>

[0276] According to one embodiment of the present invention, when a downlink preemption operation is performed in an SBFD system, a downlink preemption operation may be performed for symbols corresponding to non-SBFD symbols.

[0277] According to one embodiment of the present invention, a symbol-PRB group mapped to a downlink preemption indicator field can be determined based on SBFD configuration information. For example, the symbol-PRB group can be determined according to the symbol type. As an example, an SBFD symbol is a symbol set S set It can be excluded from. More specifically, PRB set RB in the frequency domain. setIn the method of configuring, the terminal may assume the PRB sets as active downlink BWPs. Here, RB set The number of PRBs existing within is B INT It is defined as. Symbol set (S set In the method of configuring ), if the terminal receives DCI format 2_1 via a PDCCH transmitted in a specific slot, the terminal prior to the first symbol of the slot in which the PDCCH was received Symbols symbol set (S set It can be defined as ). Here, T INT is the PDCCH monitoring cycle, is the number of symbols per slot, is the SCS (subcarrier spacing) configuration of the serving cell mapped to each field of DCI format 2_1, corresponds to the SCS configuration value configured in the downlink BWP that received the corresponding PDCCH. If there are symbols within the above symbol set configured as uplink symbols based on TDD UL / DL pattern configuration (tdd-UL-DL-ConfigurationCommon) information, the terminal [represents] the uplink symbols in the above symbol set S set They can be excluded from. Additionally, if there are symbols within the symbol set configured as SBFD symbols by SBFD configuration information, the terminal [requires] the corresponding SBFD symbols in the symbol set S. set It can be excluded from. In other words, the determined symbol set S set It may not include SBFD symbols and uplink symbols. The finally determined symbol set S set The number of symbols included is N INT It is defined as such. Downlink preemption operation can be controlled based on the above-determined symbol-PRB group method.

[0278] According to one embodiment of the present invention, the contents of a downlink preemption indicator field can be interpreted differently based on SBFD configuration information. For example, if at least one SBFD symbol exists within a symbol-PRB group mapped to a specific downlink preemption indicator bit value, the terminal may ignore the downlink preemption indication for that symbol-PRB group. For another example, if at least one SBFD symbol exists within a symbol-PRB group mapped to a specific downlink preemption indicator bit value, the terminal may not expect a downlink preemption to be indicated for that symbol-PRB group. For yet another example, if at least one SBFD symbol exists within a symbol-PRB group corresponding to a specific downlink preemption indicator bit value, the terminal may apply the downlink preemption indication only to non-SBFD symbols existing in that symbol-PRB group, and may not apply the downlink preemption indication to SBFD symbols existing in that symbol-PRB group.

[0279]

[0280] FIG. 19 illustrates an example of a procedure for determining a resource group based on time resources and applying a preemption according to one embodiment of the present disclosure. The procedure of FIG. 19 can be performed by a terminal.

[0281] Referring to FIG. 19, at step S1901, the terminal receives first configuration information and second configuration information. The first configuration information may include information related to SBFD. The second configuration information may include information regarding downlink preemption.

[0282] In step S1903, the terminal receives a PDSCH and a preemption indicator. The PDSCH may be preempted by a base station. The preemption indicator may be included in the DCI. In other words, the DCI may include information indicating a group of resources (e.g., a symbol-PRB group) to which preemption has been applied among the resource regions scheduled for the PDSCH.

[0283] In step S1905, the terminal determines a resource group to which preemption is applied based on a time resource. The resource group to which preemption is applied may be a resource group according to a symbol type. For example, the resource group to which preemption is applied may be a resource group according to the second configuration information excluding SBFD symbols. As another example, the resource group to which preemption is applied may be resource groups according to the second configuration information.

[0284] In step S1907, the terminal processes the PDSCH based on the determined resource group and the preemption indicator. For example, if the determined resource group is indicated by the preemption indicator, the terminal may process the PDSCH by excluding downlink transmissions received from the determined resource group. As another example, if the determined resource group is indicated by the preemption indicator, the terminal may ignore the preemption indicator if the determined resource group contains an SBFD symbol. As yet another example, if the determined resource group is indicated by the preemption indicator, the terminal may determine that the preemption indicator is valid only for downlink resources among the resources of the determined resource group. In other words, the preemption indicator is valid only within the downlink resource range, and the preemption indicator may be ignored for resources outside the downlink resource range. Processing of the PDSCH may include rate matching or puncturing.

[0285]

[0286] <Third Embodiment: Downlink Preemption Operation in SBFD Symbols>

[0287] In one embodiment of the present invention, when a downlink preemption operation is performed in an SBFD system, the downlink preemption operation may be performed for symbols corresponding to SBFD symbols. To this end, the following operations may be considered.

[0288] FIG. 20 illustrates an example of determining a region where downlink preemption is valid in a resource group according to one embodiment of the present disclosure. Referring to FIG. 20, the terminal may interpret the contents of a downlink preemption indicator field differently based on SBFD configuration information. In a method for determining a symbol-PRB group corresponding to a downlink preemption indicator bit value, RB, which is a frequency axis PRB set set can be considered a downlink BWP, and the number of PRBs existing within the RBset is B INT It can be defined as follows. In this case, PRBs existing outside the downlink subband may be included within the symbol-PRB group. That is, PRBs that are not downlink usable PRBs may be included in the symbol-PRB group. In this case, the RBs existing within the said symbol-PRB group set Among the PRBs present in the group, only the PRBs corresponding to the downlink-available PRBs can be considered valid, and PRBs that are not downlink-available PRBs can be considered invalid. Therefore, if a terminal receives bit information indicating a downlink preemption from DCI format 2_1 and a PRB other than a downlink-available PRB is included in the symbol-PRB group corresponding to the bit, the terminal can determine that it is valid only for the downlink-available PRBs and determine that downlink transmission has been interrupted only in that area.

[0289]

[0290] FIG. 21 illustrates an example of determining a resource group where downlink preemption is valid according to one embodiment of the present disclosure. Referring to FIG. 21, a symbol-PRB group corresponding to a downlink preemption indicator field can be determined based on SBFD configuration information. As an example, RB set It can be composed only of PRBs corresponding to downlink-enabled PRBs, and PRBs that do not correspond to downlink-enabled PRBs are PRB set RB set It may be excluded from. Specifically, the frequency axis PRB set RB set In the method of configuring, the terminal may assume PRB sets as active downlink BWPs. If SBFD subbands (e.g., downlink subband and uplink subband) exist within the active downlink BWP, the RB set Among the PRBs existing within, all PRBs that do not correspond to PRBs eligible for downlinks can be excluded. The finally determined set of PRBs RB set B the number of PRBs included INT It can be defined as such. Downlink preemption operation can be controlled based on the above-determined symbol-PRB group method.

[0291]

[0292] In one embodiment of the present invention, a symbol-PRB group corresponding to a downlink preemption indicator field can be determined based on SBFD configuration information, and the contents of the received downlink preemption indicator field can be interpreted differently.

[0293] FIG. 22 illustrates an example of configuring at least one resource group according to one embodiment of the present disclosure. Referring to FIG. 22, in a method for determining a symbol-PRB group corresponding to a downlink preemption indicator bit value when one downlink subband is configured, the method comprises a frequency axis PRB set RB set It can be considered as a pre-configured downlink subband. In this case, RBset B, the number of PRB existing within INT can be defined as the number of PRBs existing within the downlink subband (e.g., number of available downlink PRBs). If timeFrequencySet is configured as 'set0', the terminal can map each of the 14 MSB bits of the DCI format 2_1 field one-to-one to 14 consecutive symbol groups. In this case, each symbol group is N INT It contains / 14 symbols. If the bit value is indicated as 1, the terminal can assume that there was no downlink transmission in the symbol group corresponding to that bit, and if the bit value is indicated as 0, it can assume that there was a downlink transmission in the symbol group corresponding to that bit. If timeFrequencySet is configured as 'set1', the terminal can regard the 14 bits of the MSB (Most Significant Bit) of the DCI format 2_1 field as 7 pairs, each consisting of 2 bits, and each bit pair can be mapped one-to-one to 7 consecutive symbol groups. In this case, each symbol group is N INT It can contain / 7 symbols. The first bit of each bit pair is the first B within the mapped symbol group. INT It can correspond to a PRB group (RBset#1) containing / 2 PRBs, and the second bit is the second B within the mapped symbol group. INT / 2 It can correspond to a PRB group (RBset#2) consisting of PRBs. Here, B INT / 2 PRBs may be consecutive PRBs in the frequency domain. If the bit value is indicated as 1, the terminal may assume that there was no downlink transmission in the symbol and PRB group mapped to that bit, and if the bit value is indicated as 0, it may assume that there was a downlink transmission in the symbol and PRB group mapped to that bit.

[0294] As another example, in a method for determining a symbol-PRB group corresponding to a downlink preemption indicator bit value when two downlink subbands are configured (i.e., downlink subband #1 and downlink subband #2), the frequency axis PRB set RB set Multiple sets (e.g., RBset#1, RBset#2) may be defined. In this case, RBset#1 may consist of downlink-available PRBs existing in the pre-configured downlink subband#1, and RBset#2 may consist of downlink-available PRBs existing in the pre-configured downlink subband#2. In this case, the number of PRBs existing in RBset#1 is B INT It can be defined as #1, and the number of PRBs existing in RBset#2 is B INT It can be defined as #2. If two downlink subbands are configured, the downlink preemption status can be indicated for each downlink subband separately. For example, if two downlink subbands are configured, timeFrequencySet can be configured as 'set1', and the terminal can regard the MSB 14 bits of the DCI format 2_1 field as 7 pairs, each consisting of 2 bits, and each bit pair can be mapped one-to-one to 7 consecutive symbol groups. In this case, each symbol group is N INT It can be composed of 7 symbols. The first bit of each bit pair is B corresponding to RBset#1 of the downlink subband#1 mapped to that bit pair. INT #1 can correspond to PRBs, and the second bit is the RB of downlink subband #2 mapped to that bit pair. set B corresponding to #2 INT#2 It may correspond to PRBs. If the bit value is indicated as 1, the terminal may assume that there was no downlink transmission in the symbol and PRB group mapped to that bit, and if the bit value is indicated as 0, it may assume that there was a downlink transmission in the symbol and PRB group mapped to that bit. In other words, preemption may be valid in the resource group (e.g., symbol and PRB group) mapped to the bit indicated as 1.

[0295]

[0296] FIG. 23 illustrates an example of a procedure for determining a resource group based on frequency resources and applying a preemption according to one embodiment of the present disclosure. The procedure of FIG. 23 can be performed by a terminal.

[0297] Referring to FIG. 23, in step S2301, the terminal receives first configuration information and second configuration information. The first configuration information may include information related to SBFD. The second configuration information may include information regarding downlink preemption.

[0298] In step S2303, the terminal receives a PDSCH and a preemption indicator. The PDSCH may be preempted by a base station. The preemption indicator may be included in the DCI. In other words, the DCI may include information indicating at least one group of resources (e.g., a symbol-PRB group) to which preemption has been applied among the resources scheduled for the PDSCH.

[0299] In step S2305, the terminal determines a resource group to which preemption is applied based on frequency resources. For example, the resource group may be determined based on the SBFD subband included in the first configuration information. The resource group to which preemption is applied may be a resource group that includes only downlink PRBs. For example, the resource group to which preemption is applied may be the resource groups according to the second configuration information excluding the uplink PRBs and the PRBs of the guard bands. As another example, the resource group to which preemption is applied may be resource groups according to the second configuration information. The resource group to which preemption is applied may include only continuous downlink resources in the frequency domain. Alternatively, the resource group to which preemption is applied may include discontinuous downlink resources in the frequency domain. For example, the resource group to which preemption is applied may include a resource group that includes a downlink resource having the same frequency axis size as one of two available downlink resources (e.g., downlink subband #1 and downlink subband #2 of FIG. 22) and a resource group that includes a downlink resource having the same frequency axis size as the other one.

[0300] In step S2307, the terminal processes the PDSCH based on the determined resource group and the preemption indicator. For example, if the determined resource group is indicated by the preemption indicator, the terminal may process the PDSCH by excluding downlink transmissions received from the determined resource group. As another example, if the determined resource group is indicated by the preemption indicator, the terminal may ignore the preemption indicator if the determined resource group includes resources other than downlink available resources. As yet another example, if the determined resource group is indicated by the preemption indicator, the terminal may determine that the preemption indicator is valid only for downlink resources among the resources of the determined resource group. In other words, the preemption indicator is valid only within the downlink resource range, and the preemption indicator may be ignored for resources outside the downlink resource range. That is, the interpretation of the preemption indicator may be performed based on the first configuration information. Processing of the PDSCH may include rate matching or puncturing.

[0301]

[0302] The embodiments corresponding to at least one of the first, second, or third embodiments may be implemented in combination with each other. Additionally, it may be determined which operation to perform among at least one of the first, second, or third embodiments based on explicit or implicit information of the base station. Furthermore, it may be determined which operation to perform based on the terminal capability related to whether the operation corresponding to at least one of the first, second, or third embodiments can be performed. To this end, the base station may request a capability report from the terminal. In addition, the terminal may report a capability to the base station regarding at least one supported operation among at least one of the first, second, or third embodiments, and the base station may set which operation to perform based on the capability reported by the terminal.

[0303] Through embodiments of the present invention, uplink and downlink transmission and reception in a wireless communication system can be effectively controlled. Accordingly, improved cell yield, reduced latency, improved reliability of transmitted and received signals, and increased coverage are expected. In particular, PDCCH transmission and reception in a system operating as an SBFD can be effectively controlled, thereby improving system performance.

[0304]

[0305] The operation of the method according to the present disclosure can be implemented as a computer-readable program or code on a computer-readable recording medium. A computer-readable recording medium includes any type of recording device in which information that can be read by a computer system is stored. Additionally, a computer-readable recording medium may be distributed across networked computer systems, allowing the computer-readable program or code to be stored and executed in a distributed manner.

[0306] In addition, computer-readable recording media may include hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, and flash memory. Program instructions may include machine code, such as that generated by a compiler, as well as high-level language code that can be executed by a computer using an interpreter, etc.

[0307] Some aspects of the present disclosure have been described in the context of a device, but may also be described according to a corresponding method, wherein a block or device corresponds to a method step or a feature of a method step. Similarly, aspects described in the context of a method may also be described according to a corresponding block or item or a feature of a corresponding device. Some or all of the method steps may be performed by (or using) a hardware device, such as, for example, a microprocessor, a programmable computer, or an electronic circuit. In some embodiments, at least one of the most important method steps may be performed by such a device.

[0308] A programmable logic device (e.g., a field-programmable gate array) may be used to perform some or all of the functions of the methods described in this disclosure. A field-programmable gate array may operate with a microprocessor to perform one of the methods described in this disclosure. Generally, it is preferable that the methods be performed by some hardware device.

[0309] Although the present disclosure has been described with reference to preferred embodiments, those skilled in the art will understand that various modifications and changes can be made to the present disclosure without departing from the spirit and scope of the present disclosure as set forth in the following claims.

Claims

1. In a method of operation of a terminal in a wireless communication system, A step of receiving first configuration information including the locations of SBFD (subband full-duplex) symbols and information about the SBFD subband; A step of receiving second configuration information including information about downlink preemption; A step of receiving a PDSCH (physical downlink shared channel) in an area containing at least one SBFD symbol; A step of receiving downlink control information (DCI) including a preemption indicator for a region containing at least one SBFD symbol; A step of determining at least one symbol type in which the preemption indicator is effectively applied among the above regions; and A method comprising the step of processing the PDSCH by considering puncturing or rate matching for the PDSCH based on at least one symbol type and the preemption indicator.

2. In Claim 1, A method in which at least one symbol type is determined to be at least one of an SBFD symbol or a non-SBFD symbol.

3. In Claim 1, A method in which at least one symbol type to which the above-mentioned preemption indicator is effectively applied is indicated by DCI, MAC (media access control), CE (control element), RRC (radio resource control) signaling from a base station, or second configuration information.

4. In Claim 1, A method comprising at least one symbol type, wherein if scheduling for PDSCH is performed across a symbol of the first type and a symbol of the second type, the scheduling is configured to be valid only in the symbol of the first type.

5. In Claim 1, A method in which a symbol set for the above-mentioned preemption indicator is configured to include non-SBFD symbols, excluding SBFD symbols.

6. In Claim 1, A method in which, if a resource group indicated by the above preemption indicator includes at least a portion of an SBFD symbol, the indication of the preemption for the resource group is ignored.

7. In Claim 1, A method in which, if a resource group indicated by the above preemption indicator includes resources other than DL (downlink) available resources, the preemption indication for said resource group is ignored within the range of resources other than DL available resources.

8. In Claim 1, A method in which the resource set for the above preemption indicator is determined to exclude resources other than the DL-available resources of the SBFD symbol.

9. In Claim 1, A method comprising a resource set for the above preemption indicator, the first resource groups having the same frequency axis size as the first DL available resource of the SBFD symbol, and second resource groups having the same frequency axis size as the second DL available resource of the SBFD symbol.

10. In Claim 1, The above-mentioned preemption indicator indicates at least one of a plurality of resource groups, and A method in which the plurality of resource groups are configured based on the locations of the SBFD symbols and information about the SBFD subbands.

11. In Claim 1, A method in which the above preemption indicator is interpreted based on information regarding the locations of the above SBFD symbols and the above SBFD subbands.

12. In a method of operation of a base station in a wireless communication system, A step of transmitting first configuration information including the locations of SBFD (subband full-duplex) symbols and information about the SBFD subband; A step of transmitting second configuration information including information about downlink preemption; A step of transmitting a PDSCH (physical downlink shared channel) in an area containing at least one SBFD symbol; A step of transmitting data different from the PDSCH based on at least one symbol type to which the preemption indicator is effectively applied in at least a portion of the region including the at least one SBFD symbol; and A method comprising the step of transmitting a DCI including a preemption indicator indicating at least a portion of a region including at least one SBFD symbol.

13. In Claim 12, A method in which at least one symbol type is determined to be at least one of an SBFD symbol or a non-SBFD symbol.

14. In Claim 12, A method in which at least one symbol type to which the above-mentioned preemption indicator is effectively applied is indicated to a terminal by DCI, MAC CE, RRC signaling, or second configuration information.

15. In Claim 12, A method comprising at least one symbol type, wherein if scheduling for the PDSCH is performed across a symbol of the first type and a symbol of the second type, the scheduling is configured to be valid only in the symbol of the first type.

16. In Claim 12, A method in which a symbol set for the above-mentioned preemption indicator is configured to include non-SBFD symbols, excluding SBFD symbols.

17. In Claim 12, A method in which at least a portion of the region containing at least one SBFD symbol contains only non-SBFD symbols.

18. In Claim 12, A method in which at least a portion of the region containing at least one SBFD symbol includes non-SBFD symbols and DL-available resources located in the SBFD symbol.

19. In a terminal of a wireless communication system, At least one transmitter and receiver; At least one processor; and It includes at least one memory connected to the above-mentioned at least one processor to enable operation, and storing instructions that control the terminal to perform operations when executed by the processor. The above operations are, A step of receiving first configuration information including the locations of SBFD (subband full-duplex) symbols and information about the SBFD subband; A step of receiving second configuration information including information about downlink preemption; A step of receiving a PDSCH (physical downlink shared channel) in an area containing at least one SBFD symbol; A step of receiving a DCI including a preemption indicator for a region including at least one SBFD symbol; A step of determining at least one symbol type in which the preemption indicator is effectively applied among the above regions; and A terminal comprising the step of processing the PDSCH by considering puncturing or rate matching for the PDSCH based on the at least one symbol type and the preemption indicator.

20. In a base station of a wireless communication system, At least one transmitter and receiver; At least one processor; and It includes at least one memory connected to the above-mentioned at least one processor to enable operation, and storing instructions that control the terminal to perform operations when executed by the processor. The above operations are, A step of transmitting first configuration information including the locations of SBFD (subband full-duplex) symbols and information about the SBFD subband; A step of transmitting second configuration information including information about downlink preemption; A step of transmitting a PDSCH (physical downlink shared channel) in an area containing at least one SBFD symbol; A step of transmitting data different from the PDSCH based on at least one symbol type to which the preemption indicator is effectively applied in at least a portion of the region including the at least one SBFD symbol; and A base station comprising the step of transmitting a DCI including a preemption indicator indicating at least a portion of a region including at least one SBFD symbol.

Images