Communication method and apparatus for carrier aggregation in wireless communication system

WO2026221434A1PCT designated stage Publication Date: 2026-10-22HYUNDAI MOTOR CO LTD +2
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2026/095890
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-04-16
Filing Date
2026-04-14
Publication Date
2026-10-22

Smart Images

  • Figure KR2026095890_22102026_PF_FP_ABST
    Figure KR2026095890_22102026_PF_FP_ABST
Patent Text Reader

Abstract

The purpose of the present disclosure is to perform communication for carrier aggregation (CA) in a wireless communication system, and a method performed by a terminal may comprise the steps of: receiving configuration information about a plurality of cells for CA; determining the communication direction for at least one symbol on the basis of at least one cell configured with subband full-duplex (SBFD) from among the plurality of cells; and performing communication using the plurality of cells in the at least one symbol, on the basis of the determined communication direction.
Need to check novelty before this filing date? Find Prior Art

Description

Communication method and device for carrier aggregation in a wireless communication system

[0001] The present disclosure relates to subband full-duplex (SBFD) communication in a wireless communication system, and more specifically, to an SBFD-based communication method and apparatus considering carrier aggregation.

[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 performing communication using at least one of SBFD (Subband Full-Duplex) symbols and non-SBFD symbols in a wireless communication system.

[0009] The present disclosure may provide a method and apparatus for resolving conflicts in the communication directions of a plurality of cells for carrier aggregation (CA) in a wireless communication system.

[0010] The present disclosure may provide a method and apparatus for determining the communication direction of a plurality of cells for CA in a wireless communication system.

[0011] The present disclosure may provide a method and apparatus for determining a reference cell for CA based on configuration information related to SBFD in a wireless communication system.

[0012] The present disclosure may provide a method and apparatus for determining the communication direction in a reference cell for CA in a wireless communication system based on configuration information for SBFD.

[0013] The present disclosure may provide a method and apparatus for transmitting capability information of a terminal related to SBFD operation and CA operation in a wireless communication system.

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

[0015] One embodiment of the present disclosure discloses a method performed by a terminal in a wireless communication system. The method performed by the terminal may include the steps of receiving configuration information for a plurality of cells for carrier aggregation (CA), determining a communication direction for at least one symbol based on at least one cell configured as a subband full-duplex (SBFD) among the plurality of cells, and performing communication using the plurality of cells in the at least one symbol based on the determined communication direction.

[0016] One embodiment of the present disclosure discloses a terminal in a wireless communication system. The terminal comprises at least one transceiver, 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 may include: receiving configuration information for a plurality of cells for carrier aggregation (CA); determining a communication direction for at least one symbol based on at least one cell configured as a subband full-duplex (SBFD) among the plurality of cells; and performing communication using the plurality of cells in the at least one symbol based on the determined communication direction.

[0017] According to one embodiment of the present disclosure, a method performed by a base station in a wireless communication system is disclosed. The method performed by the base station includes the steps of receiving capability information of the terminal, determining a plurality of cells for carrier aggregation (CA) based on the capability information of the terminal, and transmitting configuration information for the plurality of cells. The capability information of the terminal may include at least one of information indicating whether the terminal can simultaneously support the subband full-duplex (SBFD) and the CA, or information indicating whether the terminal supports a function to handle collisions regarding the communication direction between a plurality of cells in a CA environment including a cell configured as an SBFD.

[0018] One embodiment of the present disclosure discloses a base station in a wireless communication system. The base station comprises at least one transceiver, 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 base station to perform operations when executed by the processor, wherein the operations include receiving capability information of the terminal, determining a plurality of cells for carrier aggregation (CA) based on the capability information of the terminal, and transmitting configuration information for the plurality of cells, wherein the capability information of the terminal may include at least one of information indicating whether the terminal can simultaneously support the subband full-duplex (SBFD) and the CA, or information indicating whether the terminal supports a function to handle collisions regarding the communication direction between a plurality of cells in a CA environment including a cell configured as an SBFD.

[0019] According to an embodiment of the present disclosure, wireless communication can be efficiently performed based on SBFD.

[0020] 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 a person 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 a person skilled in the art from the embodiments of the present disclosure.

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

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

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

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

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

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

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

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

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

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

[0031] FIG. 11 illustrates an example of a system configuration that appears by a combination of a setting regarding SBFD and a setting regarding active bandwidth in a wireless communication system according to one embodiment of the present disclosure.

[0032] FIG. 12 illustrates an example of carrier aggregation (CA) in a wireless communication system according to one embodiment of the present disclosure.

[0033] FIG. 13 is a flowchart illustrating a method in which a terminal performs communication according to one embodiment of the present disclosure.

[0034] FIG. 14 is a flowchart illustrating a method in which a base station performs communication according to one embodiment of the present disclosure.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0088] Subcarrier spacing 15 kHz 30 kHz 60 kHz 120 kHz 240 kHz 480 kHz OFDM symbol length [μs] 66.73 3.31 6.78 34.22.1 CP length [μs] 4.76 2.38 1.1 90.60 0.3 00.15 1 ms Number of OFDM symbols within 1328 561 1222 4448

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

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

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

[0092] μ Symbols per slot Slots per frame Slots per subframe 0 1 4 1 0 1 1 1 4 2 2 1 4 4 0 4 3 1 4 8 0 8 4 1 4 1 6 0 1 6 5 1 4 3 2 0 3 2 6 1 4 6 4 0 6 4

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

[0094] 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 symbol of the cell-specific slot format can be overridden as a downlink symbol or an uplink symbol 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 symbol can be overridden as a downlink symbol or an uplink symbol by the SFI.

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

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

[0097] A terminal may receive a first slot configuration pattern and a second slot configuration pattern based on upper layer signaling, in which case the second slot configuration pattern may include parameters of the same type as the variable values ​​that the first slot configuration pattern may have. When 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.

[0098] In addition, the terminal may receive an additional TDD-UL-DL-dedicated configuration based on the upper layer signaling ring. When 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.

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

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

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

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

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

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

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

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

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

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

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

[0110] 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 include 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.

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

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

[0113] 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 control resource set (CORESE T) information and search space information.

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

[0115] 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 indicated in slot units. Additionally, the search space information may further include the index of the symbol where the PDCCH monitoring operation starts.

[0116] 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." The number of BWPs configured for a single terminal may be one or more. 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).

[0117] Full-duplex (fd) communication

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

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

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

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

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

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

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

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

[0126] 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 continuous set of RBs for the same transmission direction. Additionally, an SBFD symbol is defined as a symbol containing the subband that the base station uses for SBFD operation.

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

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

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

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

[0131] 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. The terminal can be set in one of four methods, typically according to Table 4 below, while in an RRC connection state.

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

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

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

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

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

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

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

[0139] The terminal may allow UL transmission within the UL subband within the symbol and 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 terminal as SBFD. 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 an SBFD-aware UE may depend on the following options.

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

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

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

[0143] 1. Flexible SBFD Configuration: The terminal is allowed to transmit UL within the UL subband within the symbol, and may allow 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.

[0144] Second Flexible SBFD Configuration: Within a symbol, the terminal is allowed to transmit UL within the UL subband, and may allow DL reception 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.

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

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

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

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

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

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

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

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

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

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

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

[0156] - Option 3: Dynamic SBFD can be set by MAC-CE, which indicates whether a symbol is an SBFD symbol.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0182] Mobile communication systems (e.g., 5G NR (New Ratio) systems) support “subband full-duplex (hereinafter referred to as SBFD)” technology, which allows simultaneous transmission and reception of downlink (hereinafter DL) and uplink (hereinafter UL) signals at the same time in a portion of the total system bandwidth for the purpose of improving cell yield, reducing latency, improving transmission and reception signal reliability, and increasing coverage. The present invention proposes a method for uplink and downlink transmission and reception in a wireless communication system that supports SBFD.

[0183] In the present disclosure, “Active Bandwidth” may refer to a continuous frequency resource region configured for a terminal to perform transmission and / or reception within the carrier bandwidth. In one example, Active Bandwidth may be a concept distinct from Bandwidth Part (BWP). In another example, Active Bandwidth may represent a substantially identical or similar concept to BWP, differing only in name. Alternatively, Active Bandwidth may be referred to by other terms having a similar technical meaning.

[0184] In the present disclosure, “terminal capability information” may be referred to in various ways, such as UE capability information, UE capability, terminal capability, etc.

[0185] In the present disclosure, "TDD (Time Division Duplex) uplink and downlink configuration information" refers to upper-layer configuration information that statically or semi-statically sets the communication direction of time resources (e.g., slots or symbols) within a specific cell or frequency band, and may be variously referred to as TDD-UL-DL configuration, TDD-UL-DL common configuration information, TDD-UL-DL-ConfigCommon, etc.

[0186] In the present disclosure, “communication direction” may refer to an uplink (UL) or a downlink (DL). In one embodiment, “communication direction for a symbol” may be understood as the direction of signal transmission and reception in the symbol, which may mean a state in which either UL transmission or DL ​​reception in the symbol is performed or is scheduled to be performed.

[0187] In the present disclosure, "collision handling" may be referred to in various ways, such as collision resolution, directional collision resolution, or directional collision handling, and can be understood as encompassing the operation of a terminal and / or a base station for coordinating, avoiding, or resolving a situation in which communication directions set between a plurality of cells conflict with each other.

[0188]

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

[0190] 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 composed of a full-duplex subband (hereinafter, "non-SBFD symbol").

[0191] According to one example of the present disclosure, a time domain pattern and period for at least one SBFD symbol may be set. For example, a specific SBFD symbol pattern may be set continuously within a TDD UL / DL area set in an upper layer. For example, the SBFD symbol pattern may be set 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, in order to set a pattern in the time domain for the SBFD symbol, setting 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.

[0192] According to one example of the present disclosure, frequency positions corresponding to UL / DL subbands within an SBFD symbol may be explicitly set through upper-level signaling. For example, the frequency position and bandwidth size of the UL subband, and the frequency position and bandwidth size of the DL subband, may each be set 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 set as a UL subband or a DL subband. The frequency positions of the UL / DL subbands may be set independently according to the subcarrier spacing (SCS) value. In other words, UL / DL subbands with different SCS values ​​may have different frequency positions. Alternatively, UL / DL subbands with different SCS values ​​may have the same frequency position. For setting the UL / DL subbands within an SBFD symbol, a starting PRB index and the bandwidth size of 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.

[0193] 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. Herein, 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.

[0194] - Configuration 1: UL transmission or DL ​​reception may be performed on only one of 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 configured or implicitly determined based on scheduling information for UL and / or DL ​​transmission and reception.

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

[0196] The aforementioned configuration 1 or configuration 2 may be signaled by a base station. In other words, a terminal may decide, upon the instructions of the base station, whether to operate based on configuration 1 or based on configuration 2. 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 set by cell-specific signaling, terminals included in a single cell may operate based on the same configuration. If configuration 1 or configuration 2 is set 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 settings may be performed for each physical layer channel (e.g., PDSCH, PDCCH, PUCCH, PUSCH, SRS, CSI-RS). For example, a terminal may perform reception of PDSCH based on setting 1 and transmission of PUSCH based on setting 2, and these settings may be set per terminal or per cell. That is, cell-specific signaling and terminal-specific signaling may include physical layer channel-specific settings.

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

[0198] Meanwhile, in a wireless communication system (e.g., a 5G NR system), a Bandwidth Part (hereinafter BWP) or active bandwidth can be configured from the total system bandwidth for purposes such as improving cell yield, reducing latency, and reducing terminal power consumption. A base station can configure one or more active bandwidths (or BWPs) for UL and DL transmission and reception to a terminal, and can perform communication by activating one of the bandwidths. A terminal can receive one or more active bandwidths (or BWPs) from the base station and can perform communication with the base station using one of the activated bandwidths.

[0199] As an example of setting an active bandwidth (or BWP), for each DL active bandwidth (or BWP) and UL active bandwidth (or BWP), the terminal may receive the following parameters.

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

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

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

[0203] - ID of each active bandwidth (or BWP)

[0204] When the terminal and / or base station operate in the TDD band, the DL active band (or BWP) and UL active band (or BWP) set with the same active band (or BWP) ID are connected to each other, and the DL active band (or BWP) and UL active band (or BWP) having the same active band (or BWP) ID can be activated. Additionally, when the terminal and / or base station operate in the TDD band, the center frequencies of the DL active band (or BWP) and UL active band (or BWP) are the same.

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

[0206] FIG. 11 illustrates an example of a system configuration resulting from a combination of a configuration for SBFD and a configuration for BWP in a wireless communication system according to an 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.

[0207] An embodiment of FIG. 11 shows a state in which a plurality of active bandwidths (or BWPs), e.g., active bandwidth (or BWP)#1 and active bandwidth (or BWP)#2 are configured, active bandwidth (or BWP)#1 is enabled, and active bandwidth (or BWP)#2 is disabled. Additionally, UL / DL subbands for SBFDs are configured in the second and third slots. Here, for SBFD symbols for which UL / DL subbands are configured, resource areas (e.g., Physical Resource Blocks (PRBs)) available for actual UL / DL transmission and / or reception can be defined as follows.

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

[0209] - DL Available PRB: DL subband frequency resource area within the active DL bandwidth (or BWP).

[0210] That is, the base station and the terminal can perform uplink transmission and / or reception for SBFD symbols through UL available PRBs within the active UL active bandwidth (or BWP), and can perform downlink transmission and / or reception through DL available PRBs within the active DL active bandwidth (or BWP).

[0211] For UL / DL transmission and reception scheduled across SBFD symbols and non-SBFD symbols within a single slot, the terminal may not perform transmission and reception for the corresponding UL / DL in that slot. However, UL transmission operation may be exceptionally permitted in the following cases.

[0212] - For a PRACH (Physical Random Access Channel) in a valid RO (Random Access Occasion) set across SBFD symbols and non-SBFD symbols, the terminal can perform transmission.

[0213] - For PUSCH repetition type B, the terminal can perform transmission.

[0214] For UL / DL transmits and receives scheduled across SBFD and non-SBFD symbols in different slots, whether the transmits and receives are performed based on Config #1 or based on Config #2 can be configured per UL / DL active bandwidth (or BWP). In this case, the terminal may support Config #1 as a default capability. Alternatively, whether the terminal supports Config #2 may be known to the base station through a UE capability report. The base station may configure Config #2 per active bandwidth (or BWP) for terminals that support Config #2. If a specific DL active bandwidth (or BWP) is configured as Config #2, the terminal may perform operations based on Config #2 when performing DL reception in that DL active bandwidth (or BWP). For example, the terminal may perform operations based on Config #2 only for PDSCH reception in the DL active bandwidth (or BWP). If a specific UL active bandwidth (or BWP) is set to Config #2, the terminal may perform operations based on Config #2 when performing UL transmission in the UL active bandwidth (or BWP). Even if the UL active bandwidth (or BWP) is set to Config #2, the terminal may perform operations based on Config #1 for SRS (sounding reference signal) transmission.

[0215]

[0216] For Configuration #1, the valid symbol type can be determined in the following way.

[0217] - For UL transmissions and / or DL ​​receptions scheduled by DCI, the valid symbol type is determined by the symbol type assigned at the first transmission and / or reception time at which the UL transmission and / or DL ​​reception is scheduled.

[0218] ▪ At this time, the terminal does not expect that the first transmission and / or reception will be scheduled across SBFD symbols and non-SBFD symbols for UL transmission and / or DL ​​reception scheduled through DCI.

[0219] - For UL transmission and / or DL ​​reception configured semi-static without an enabled DCI instruction, the valid symbol type is explicitly set by RRC signaling. For example, for a configured Grant Type 1 PUSCH, the valid symbol type can be explicitly indicated by the RRC setting.

[0220] - For UL transmissions and / or DL ​​receptions configured semi-statically with an activating DCI instruction, the valid symbol type is determined by the symbol type assigned at the time of the first transmission and / or reception of the UL and / or DL ​​scheduled by the corresponding activating DCI. For example, for a configured Grant Type 2 PUSCH (Type 2 CG PUSCH) or Semi-Persistent Scheduling (SPS) PDSCH (SPS PDSCH), the valid symbol type may be determined by the symbol type assigned at the time of the first transmission and / or reception of the UL and / or DL ​​scheduled by the corresponding activating DCI.

[0221]

[0222] For Config #1, the following operations may be performed for UL transmission and / or DL ​​reception assigned to an invalid symbol type.

[0223] - For PUSCH repetitive transmission type A with available slot counting, Aperiodic-SRS with available slot counting, TBoMS (Transmission Block over Multiple Slots), and PUCCH repetitive transmission, the terminal can postpone transmissions assigned to invalid symbol types.

[0224] For configured Grant (CG) PUSCH, SPS PDSCH, Periodic / Semi-Persistent (P / SP) SRS, P / SP CSI-RS, P / SP PUCCH, Semi-Persistent CSI on PUSCH (SP-CSI on PUSCH), PUSCH recurring transmission type A without available slot counting, multi-PUSCH / PDSCH scheduled by a single DCI, and PDSCH recurring transmissions, the terminal may drop transmissions assigned to invalid symbol types.

[0225] For Config #2, if CG PUSCH, PUSCH repetition, and / or multi-slot PUSCH transmissions are scheduled across SBFD symbols and non-SBFD symbols, the frequency axis start PRB position of the PUSCH assigned to the SBFD symbol ( In determining ), the starting PRB position in one or more non-SBFD symbols ( Offset value from ) ) can be set. Specifically, the starting PRB position in the SBFD symbol can be determined as shown in [Equation 1] below.

[0226]

[0227] In [Mathematical Formula 1], is the starting PRB index of PUSCH within the SBFD symbol based on the starting point of the UL active BWP, is the starting PRB index of PUSCH within the non-SBFD symbol based on the starting point of the UL active BWP, is the starting PRB index of UL usable PRBs based on the starting point of the UL active BWP, is the number (or size) of the PRBs of the UL BWP, is the number (or size) of PRBs among UL available PRBs, and is the number (or size) of PRBs for PUSCH transmission.

[0228] if If the value is not set, the terminal It can be assumed that the frequency domain resource allocation (FDRA) of PUSCH in non-SBFD symbols can be determined in the same way as before. The number of PRBs allocated to PUSCH can be determined in the same way as before for both SBFD and non-SBFD symbols.

[0229] For configuration #2, when SPS PDSCH, PDSCH iteration, and / or multi-slot PDSCH transmissions are scheduled across SBFD symbols and non-SBFD symbols, among the PRBs assigned within the SBFD symbols, only the PRBs assigned to DL available PRBs can be determined to be valid.

[0230]

[0231] Meanwhile, 3GPP Rel-16 supports a technology for resolving collision issues in a half-duplex (HD) TDD Carrier Aggregation (CA) environment. Specifically, for multiple cells configured with the same Subcarrier Spacing (SCS), if a directional collision handling parameter is set to active (e.g., directionalCollisionHanling = enable), the HD terminal can resolve directional collision issues occurring between multiple cells based on specific rules. To this end, the terminal first determines one cell among the multiple cells configured for CA as a reference cell, and then resolves directional collision issues between the reference cell and other cells. Specifically, the terminal may follow the operations shown in Table 5 below.

[0232] If a UE- is configured with multiple serving cells and is provided withdirectionalCollisionHandling-r16= 'enabled' for a set of serving cell(s) among the multiple serving cells, and- indicates support ofhalf-DuplexTDD-CA-SameSCS-r16capability, and- is not configured to monitor PDCCH for detection of DCI format 2_0 on any of the multiple serving cells,for a set of symbols of a slot that are indicated to the UE for reception of SS / PBCH blocks in a first cell of the multiple serving cells byssb-PositionsInBurstinSystemInformationBlockType1or byssb-PositionsInBurstinServingCellConfigCommon, when provided to the UE, the UE does not transmit PUSCH, PUCCH, or PRACH in the slot if a transmission would overlap with any symbol from the set of symbols, and the UE does not transmit SRS in the set of symbols of the slot in- any of the multiple serving cells if the UE is not capable of simultaneous transmission and reception as indicated bysimultaneousRxTxInterBandCAamong the multiple serving cells,and- any one of the cells corresponding to the same band as the first cell, irrespective of any capability indicated bysimultaneousRxTxInterBandCA.For a set of symbols of a slot corresponding to a valid PRACH occasion and N, gapsymbols before the valid PRACH occasion, as described in clause 8.1, the UE does not receive PDCCH, PDSCH, or CSI-RS in the slot if a reception would overlap with any symbol from the set of symbols. The UE does not expect the set of symbols of the slot to be indicated as downlink bytdd-UL-DL-ConfigurationCommonortdd-UL-DL-ConfigurationDedicated.For a set of symbols of a slot indicated to a UE bypdcch-ConfigSIB1inMIBfor a CORESET for Type0-PDCCH CSS set, the UE does not expect the set of symbols to be indicated as uplink bytdd-UL-DL-ConfigurationCommon, ortdd-UL-DL-ConfigurationDedicated.If a UE is scheduled by a DCI format to receive PDSCH over multiple slots, and iftdd-UL-DL-ConfigurationCommon, ortdd-UL-DL-ConfigurationDedicated, indicate that, for a slot from the multiple slots, at least one symbol from a set of symbols where the UE is scheduled PDSCH reception in the slot is an uplink symbol,the UE does not receive the PDSCH in the slot.If a UE is scheduled by a DCI format to transmit PUSCH over multiple slots, and iftdd-UL-DL-ConfigurationCommon, ortdd-UL-DL-ConfigurationDedicated, indicatesthat, for a slot from the multiple slots, at least one symbol from a set of symbols where the UE is scheduled PUSCH transmission in the slot is a downlink symbol, the UE does not transmit the PUSCH in the slot.If a UE- is configured with multiple serving cells and is provided withdirectionalCollisionHandling-r16= 'enabled' for a set of serving cell(s) among the configured multiple serving cells, and- indicates support ofhalf-DuplexTDD-CA-SameSCS-r16capability, and- is not configured to monitor PDCCH for detection of DCI format 2_0 on any of the multiple serving cells,the UE determines a reference cell for a symbol as an active cell with the smallest cell index among- the configured multiple serving cells if the UE is not capable of simultaneous transmission and reception as indicated bysimultaneousRxTxInterBandCAamong the multiple serving cells, and- the cells of each band respectively if the UE is capable of simultaneous transmission and reception bysimultaneousRxTxInterBandCAfor the configured multiple serving cells,where the symbol is configured as- downlink, or uplink, as indicated bytdd-UL-DL-ConfigurationCommonortdd-UL-DL-ConfigurationDedicated- uplink, if the symbol is flexible and the UE is configured to transmit SRS, PUCCH, PUSCH, or PRACH on the symbol- downlink, if the symbol is flexible and the UE is configuredto receive PDCCH, PDSCH or CSI-RS on the symbol.And if another cell among the cells configured withdirectionalCollisionHandling-r16operates in the same frequency band as the reference cell,the UE does not expect- a symbol to be indicated as downlink or uplink on the reference cell and as uplink or downlink on another cell, respectively, bytdd-UL-DL-ConfigurationCommonor bytdd-UL-DL-ConfigurationDedicated,-tdd-UL-DL-ConfigurationCommonortdd-UL-DL-ConfigurationDedicatedto indicate a symbol as downlink on the reference cell and to detect a DCI format scheduling a transmission on the symbol on another cell, and- to be configured by higher layers to receivePDCCH, PDSCH, or CSI-RS on a flexible symbol on the reference cell and to detect a DCI format scheduling a transmission on the symbol on another cell,if the reference cell and another cell among the cells configured withdirectionalCollisionHandling-r16operate in different frequency bands,the UE- assumes symbol as flexible, is not required to receive higher layer configuredPDCCH, PDSCH, or CSI-RS and not expected to transmit higher layer configured SRS, PUCCH, PUSCH, or PRACH,whentdd-UL-DL-ConfigurationCommonortdd-UL-DL-ConfigurationDedicatedindicates symbol as downlink or uplink on another cell and as uplink or downlink for the reference cell, respectively,- transmits a signal / channel scheduled by a DCI format on a symbol of another cell when the symbol is indicated as downlink bytdd-UL-DL-ConfigurationCommonortdd-UL-DL-ConfigurationDedicatedfor the reference cell,- is not required to receive a higher layer configuredPDCCH, PDSCH, or CSI-RS on flexible symbols on the reference cell in a set of symbols, if the UE detects a DCI format scheduling a transmission on one or more symbols in the set of symbols on another cell,and regardless of whether the reference cell and another cell operate in same or different frequency bands,the UE- does not expecttdd-UL-DL-ConfigurationCommonortdd-UL-DL-ConfigurationDedicatedfor the reference cell to indicate a symbol as uplink and to detect a DCI format scheduling a reception on the symbol on another cell- does not expect to be configured by higher layers to transmit SRS, PUCCH, PUSCH, or PRACH on a flexible symbol on the reference cell and to detect a DCI format scheduling a reception on the symbol on another cell- does not transmit a PUCCH, PUSCH or PRACH that is configured by higher layers on a set of symbols on another cell if at least one symbol from the set of symbols is indicated as downlink bytdd-UL-DL-ConfigurationCommonortdd-UL-DL-ConfigurationDedicatedor is a symbol corresponding to a PDCCH, PDSCH,or CSI-RS reception that is configured by higher layers on the reference cell- does not transmit a SRS that is configured by higher layers on a set of symbols on another cell if the set of symbols is indicated as downlink bytdd-UL-DL-ConfigurationCommonortdd-UL-DL-ConfigurationDedicatedor corresponds to a PDCCH, PDSCH or CSI-RS reception that is configured by higher layers on the reference cell- does not receive a PDCCH, PDSCH or CSI-RS that is configured by higher layers on a set of symbols on another cell if at least one symbol from the set of symbols is indicated as uplink bytdd-UL-DL-ConfigurationCommonortdd-UL-DL-ConfigurationDedicatedor is a symbol corresponding to a SRS, PUCCH, PUSCH, or PRACH transmission that is configured by higher layers on the reference cell- assumes a symbol indicated as downlink or uplink bytdd-UL-DL-ConfigurationCommonortdd-UL-DL-ConfigurationDedicatedon another cell to be flexible, if the UE is respectively configured by higher layers to transmit SRS,PUCCH, PUSCH, or PRACH or to receive PDCCH, PDSCH, or CSI-RS on the reference cell- does not expect to detect a first DCI format scheduling a transmission or reception on a symbol on a first cell and a second DCI format scheduling a reception or transmission on the symbol on a second cell, respectively. After the UE applies the procedures described above for directional collision handling within the set of cells that have been configured with directionalCollisionHandling-r16, the UE does not expect any directional collision among the serving cells that the UE is not capable of simultaneous transmission and reception.,

[0233]

[0234] Meanwhile, when DL reception and UL transmission occur simultaneously in an SBFD symbol, the HD terminal can only perform transmission and reception in one direction due to hardware constraints. Accordingly, the directional conflict problem arising from the scheduling type assigned to the SBFD symbol can be resolved based on the following rules.

[0235] Case 1: Dynamically scheduled DL reception vs. Semi-statically configured UL transmission

[0236] - Example: When dynamic PDSCH or CSI-RS conflicts with an configured SRS, PUCCH, or CG PUSCH

[0237] - If the cancellation time requirement is satisfied, the UL transmission is canceled. This is the same as the collision handling method in conventional flexible symbols.

[0238] Case 2: Semi-statically configured DL reception vs. Dynamically scheduled UL transmission

[0239] - Example: When SPS PDSCH conflicts with dynamic PUSCH or PUCCH

[0240] - The terminal does not perform DL reception. This is the same as the collision handling method in conventional flexible symbols.

[0241] Case 3: Semi-statically configured DL reception vs. Semi-statically configured UL transmission

[0242] - This corresponds to an error case, and the terminal does not expect such a setting.

[0243] Case 4: Dynamically scheduled DL reception vs. Dynamically scheduled UL transmission

[0244] - This corresponds to an error case, and the terminal does not expect such a setting.

[0245] Case 5: SSB vs. Dynamically Scheduled or Configured UL Transmission

[0246] - Example: When SSB conflicts with PUSCH, PUCCH, PRACH, or SRS

[0247] - SSB is received before UL transmission.

[0248] - Symbols in which an SSB is configured within the SBFD subband are considered SBFD symbols. DL reception is allowed only in DL usable PRBs. It is assumed that the SSB always exists within the DL subband.

[0249] Case 6: Dynamic or semi-static DL vs. Valid RACH Occasion

[0250] - The terminal does not expect a situation where PRACH transmission and dynamic DL reception triggered by the PDCCH order conflict.

[0251] - If a PRACH transmission triggered by a PDCCH order conflicts with a quasi-static DL reception, the PRACH transmission takes precedence and the DL reception is not performed.

[0252] - In the event that a PRACH transmission and a DL reception triggered by an upper layer conflict, the terminal implementation determines whether to transmit the PRACH or receive the DL.

[0253]

[0254] Meanwhile, in a multi-carrier scenario operating as CA, SBFD operation can be supported on at least one TDD carrier.

[0255] FIG. 12 illustrates an example of carrier aggregation (CA) in a wireless communication system according to one embodiment of the present disclosure.

[0256] The embodiment of FIG. 12 shows an example of CA between a first CC (Component Carrier) (CC#1) with SBFD configured and a second CC (CC#2) without an SBFD subband configured. In this case, a directional collision problem may occur between the transmission and / or reception of the SBFD symbol in CC#1 and the transmission and / or reception in CC#2. In particular, since the SBFD subband can be configured in a symbol configured as DL or flexible in the TDD configuration, there is a problem in that collision resolution rules based on conventional TDD UL and / or DL ​​symbol configurations are difficult to apply. Accordingly, the present disclosure proposes various embodiments for solving the directional collision problem in an SBFD system operating with multiple carriers.

[0257]

[0258] [1st Embodiment: Method for Determining Reference Cells]

[0259] According to one embodiment of the present disclosure, a terminal can receive configuration information for a plurality of cells from a base station. In other words, the base station can configure a plurality of cells for the terminal. At this time, at least one of the configured plurality of cells may be a cell configured as an SBFD. The terminal can determine a reference cell for directional collision handling between the plurality of cells based on whether each of the plurality of cells is configured as an SBFD.

[0260] Specifically, the terminal can determine a reference cell among multiple cells when the following conditions are satisfied.

[0261] - Condition 1: Multiple serving cells are configured, and among the configured multiple serving cells, the directional collision handling parameter of a specific set of cells is set to active (e.g., directionalCollisionHandling-r16='enabled').

[0262] - Condition 2: Instruct the base station to support half-duplex capability information for TDD CA based on the same subcarrier spacing (e.g., half-DuplexTDD-CA-SameSCS-r16 capability information).

[0263] - Condition 3: Not configured to monitor PDCCH for DCI format 2_0 in configured serving cells.

[0264] - Condition 4: A specific set of cells contains at least one cell set to SBFD. Here, the specific set of cells may refer to the set of cells where the directional collision handling parameter is set to active in Condition 1.

[0265] If the aforementioned conditions are satisfied, the terminal can determine a reference cell based on any one of methods #1-1 to #1-4.

[0266] [Method #1-1]

[0267] - The terminal may determine as a reference cell a cell set to SBFD or a cell having a cell index satisfying a predetermined condition, based on whether there is a cell set to SBFD among the cells activated for a specific symbol. For example, if there is a cell set to SBFD among the cells activated for a specific symbol, the terminal may determine as a reference cell a cell set to SBFD among the cells activated for the specific symbol, regardless of the cell index. As another example, if there is no cell set to SBFD among the activated cells, the terminal may determine as a reference cell a cell having the smallest cell index among the cells activated for the specific symbol.

[0268] [Method #1-2]

[0269] - The terminal can determine a cell having a cell index that satisfies a predetermined condition among the cells activated for a specific symbol as a reference cell. For example, the terminal can determine a cell having the smallest cell index among the cells activated for a specific symbol as a reference cell. According to one embodiment, if there is a cell set as SBFD among a plurality of cells set, the terminal can expect that the cell set as SBFD among the activated cells will be set as the smallest cell index.

[0270] The aforementioned methods #1-1 and #1-2 correspond to an operation in which, among the cells activated for a specific symbol, the cell configured as SBFD has the highest priority, and the cell configured as SBFD with the highest priority is determined as the reference cell. The cell configured as SBFD may have less UL coverage than other cells. Therefore, by prioritizing the communication direction of the cell configured as SBFD, it is possible to address directional conflict issues where the communication directions between cells conflict.

[0271] [Method #1-3]

[0272] - If there is a cell set to SBFD among the cells activated for a specific symbol, the terminal may determine as a reference cell a cell having a cell index satisfying a predetermined condition among the remaining cells excluding the cell set to SBFD. For example, the terminal may determine as a reference cell a cell having the smallest cell index among the remaining cells, excluding the cell set to SBFD among the cells activated for a specific symbol.

[0273] [Method #1-4]

[0274] - The terminal may determine a cell having a cell index that satisfies a predetermined condition among the cells activated for a specific symbol as a reference cell. For example, the terminal may determine a cell having the smallest cell index among the cells activated for a specific symbol as a reference cell. According to one embodiment, if there is a cell set as SBFD among a plurality of set cells, the terminal may not expect the cell set as SBFD to be set as the smallest cell index.

[0275] The aforementioned methods #1-3 and #1-4 assume that among the cells activated for a specific symbol, the cell configured as SBFD has the lowest priority, and the cell with relatively higher priority determines another cell as the reference cell. The cell configured as SBFD allows for more flexible allocation for UL transmission and / or DL ​​reception than other cells. Therefore, directional conflicts that may occur due to the cell operating as SBFD can be avoided through scheduling.

[0276] According to one embodiment of the present disclosure, a base station may provide information related to reference cell determination criteria through upper layer signaling. For example, the base station may transmit configuration information to a terminal through upper layer signaling that indicates whether to prioritize consideration of a cell configured as SBFD in determining the reference cell. Based on the configuration information of the base station, the terminal may determine whether to prioritize consideration of a cell configured as SBFD when determining the reference cell.

[0277]

[0278] [Second Embodiment: Method for Determining Direction]

[0279] According to one embodiment of the present disclosure, a terminal may receive configuration information for a plurality of cells from a base station, and the plurality of cells may include at least one cell configured as an SBFD. For directional collision processing for the plurality of cells, the terminal may determine one cell among the plurality of cells that satisfies a predetermined condition as a reference cell. According to one embodiment, the predetermined condition may include a condition described in any one of methods #1-1 to #1-4 (e.g., whether the cell is configured as an SBFD, or a cell index condition, etc.).

[0280] When a cell set to SBFD among the cells activated for a specific symbol is determined as the reference cell, the communication direction for the corresponding symbol in the reference cell can be determined as follows.

[0281] [Method #2-1]

[0282] The terminal may determine one cell configured as SBFD among the cells activated for a specific symbol as the reference cell. At this time, the communication direction of the corresponding symbol in the reference cell may be determined as follows.

[0283] - If indicated by a UL symbol or a DL symbol by a TDD uplink / downlink configuration (e.g., TDD-UL-DL configuration), the communication direction may be determined by the UL or DL ​​indicated by the uplink / downlink configuration.

[0284] - If the symbol is a flexible symbol and UL transmission (e.g., SRS, PUCCH, PUSCH, or PRACH) is set or scheduled for the symbol, the communication direction may be determined to UL.

[0285] - If the symbol is a flexible symbol and DL reception (e.g., PDCCH, PDSCH, or CSI-RS) is set or scheduled for the symbol, the communication direction may be determined to be DL.

[0286] - If a symbol is an SBFD symbol and a UL transmission (e.g., SRS, PUCCH, PUSCH, or PRACH) is set or scheduled for that symbol, the communication direction may be determined to be UL.

[0287] - If the symbol is an SBFD symbol and DL reception (e.g., PDCCH, PDSCH, or CSI-RS) is established or scheduled for that symbol, the communication direction may be determined to be DL.

[0288] The above-described method #2-1 corresponds to an operation in which an SBFD symbol is considered a flexible symbol and the symbol is defined as a UL or DL ​​symbol according to the UL transmission and DL reception settings. Since both UL transmission and DL reception are possible with SBFD symbols, SBFD symbols can be considered identical to flexible symbols in existing TDD UL / DL.

[0289] [Method #2-2]

[0290] The terminal may determine one cell configured as SBFD among the cells activated for a specific symbol as the reference cell. At this time, the communication direction of the corresponding symbol in the reference cell may be determined as follows.

[0291] - If indicated by a UL symbol or a DL symbol by a TDD uplink / downlink configuration (e.g., TDD-UL-DL configuration), the communication direction may be determined by the UL or DL ​​indicated by the uplink / downlink configuration.

[0292] - If the symbol is a flexible symbol and UL transmission (e.g., SRS, PUCCH, PUSCH, or PRACH) is set or scheduled for the symbol, the communication direction may be determined to UL.

[0293] - If the symbol is a flexible symbol and DL reception (e.g., PDCCH, PDSCH, or CSI-RS) is set or scheduled for the symbol, the communication direction may be determined to be DL.

[0294] - If the symbol is an SBFD symbol, the communication direction can be determined based on the TDD uplink / downlink configuration for the symbol (e.g., TDD-UL-DL configuration).

[0295] ▪ If the corresponding SBFD symbol is indicated as DL by the TDD uplink / downlink configuration, the communication direction can be determined as DL.

[0296] ▪ If the corresponding SBFD symbol is indicated as flexible by the TDD uplink / downlink settings, the communication direction can be determined as flexible.

[0297] The above-described method #2-2 corresponds to a method for determining the communication direction based on the originally configured TDD uplink / downlink settings for an SBFD symbol. If the SBFD symbol is configured to DL by the TDD uplink / downlink settings, the communication direction is determined to DL, and if the SBFD symbol is configured to flexibly by the TDD uplink / downlink settings, the communication direction can be determined to flexibly. When the communication direction is determined to be flexibly, the terminal can finally determine the communication direction to UL or DL ​​based on the UL transmission or DL ​​reception configured by the RRC. According to one embodiment, the UL transmission or DL ​​reception configured by the RRC may include the UL transmission or DL ​​reception indicated by the semi-persistent settings. For example, the UL transmission may include the semi-persistently configured SRS, PUCCH, PUSCH, or PRACH, and the DL reception may include the semi-persistently configured PDCCH, PDSCH, or CSI-RS.

[0298]

[0299] [Method #2-3]

[0300] The terminal may determine one cell configured as SBFD among the cells activated for a specific symbol as the reference cell. At this time, the communication direction of the corresponding symbol in the reference cell may be determined as follows.

[0301] - If indicated by a UL symbol or a DL symbol by a TDD uplink / downlink configuration (e.g., TDD-UL-DL configuration), the communication direction may be determined by the UL or DL ​​indicated by the uplink / downlink configuration.

[0302] - If the symbol is a flexible symbol and UL transmission (e.g., SRS, PUCCH, PUSCH, or PRACH) is set or scheduled for the symbol, the communication direction may be determined to UL.

[0303] - If the symbol is a flexible symbol and DL reception (e.g., PDCCH, PDSCH, or CSI-RS) is set or scheduled for the symbol, the communication direction may be determined to be DL.

[0304] - If the symbol is an SBFD symbol, the communication direction can be determined as UL.

[0305] The above-described method #2-3 corresponds to an operation that prioritizes uplink transmission by determining the communication direction of all SBFD symbols to UL. Since the cell configured as SBFD is utilized for the purpose of extending UL coverage, the communication direction can be determined by prioritizing UL transmission.

[0306] [Method #2-4]

[0307] A terminal may determine one cell configured as SBFD among the cells activated for a specific symbol as a reference cell. In this case, the communication direction of the SBFD symbol may be pre-configured by the base station. In other words, if the reference cell is a cell configured as SBFD, the base station may pre-configure the communication direction for the SBFD symbol. For example, the base station may set the communication direction of the SBFD symbol to UL and signal configuration information including this to the terminal. The terminal may determine the communication direction of the SBFD symbol as UL based on the base station's configuration. Alternatively, the base station may set the communication direction of the SBFD symbol to DL and signal configuration information including this to the terminal. The terminal may determine the communication direction of the SBFD symbol as DL based on the base station's configuration. Alternatively, the base station may set the communication direction of the SBFD symbol to Flexible and signal configuration information including this to the terminal. The terminal may determine the communication direction of the SBFD symbol as Flexible based on the base station's configuration. If the communication direction of an SBFD symbol is set to flexible, the terminal can finally determine the communication direction of the SBFD symbol in the following way.

[0308] - If a symbol is a flexible symbol and UL transmission (e.g., SRS, PUCCH, PUSCH, or PRACH) is set or scheduled for the symbol, the communication direction of the symbol may be determined by UL.

[0309] - If a symbol is a flexible symbol and DL reception (e.g., PDCCH, PDSCH, or CSI-RS) is set or scheduled for that symbol, the communication direction of that symbol may be determined to be DL.

[0310]

[0311] [Third Embodiment: Collision Resolution Method]

[0312] According to one embodiment of the present disclosure, a terminal may receive configuration information for a plurality of cells from a base station, and the plurality of cells may include at least one cell configured as an SBFD. The terminal supports half-duplex communication and may determine a reference cell based on a predetermined rule. The terminal may determine whether there is a conflict in the communication direction between the reference cell and other cells and perform an operation to resolve the conflict. For example, the terminal may check whether the communication direction of the reference cell and the communication direction of other cells for a specific symbol are configured and / or determined differently from each other, and if the communication direction of the reference cell and the communication direction of other cells are different from each other, it may perform an operation to resolve this. Specifically, the terminal may perform operations to resolve the conflict based on whether the reference cell is a cell configured as an SBFD, or whether the symbol that caused the conflict is an SBFD symbol. For example, operations to resolve the conflict may include the following. Here, a collision may be understood to include a situation in which the communication direction of a reference cell and the communication direction of at least one other cell excluding the reference cell among a plurality of cells are set and / or determined differently for a specific symbol, and may be referred to as a directional collision, a communication direction collision, a transmission / reception direction collision, or other terms having substantially similar technical meanings.

[0313] - If the reference cell is a cell set to SBFD and the collision occurrence symbol is the SBFD symbol, the terminal can resolve the collision problem based on operation A.

[0314] ▪ For example, operation A may include a method of assigning a higher priority to UL transmission and / or DL ​​reception of a cell configured as SBFD.

[0315] - If the reference cell is a cell set to SBFD and the collision occurrence symbol is a non-SBFD symbol, the terminal can resolve the collision problem based on operation B.

[0316] ▪ For example, Action B may include a predefined collision resolution action. For example, a predefined collision resolution action may include the actions in Table 5.

[0317] - In a situation where the reference cell is not a cell set to SBFD, and another cell is a cell set to SBFD, if the collision occurrence symbol is an SBFD symbol, the terminal can resolve the collision problem based on operation C.

[0318] ▪ For example, operation C may include a method of assigning a higher priority to UL transmission and / or DL ​​reception of a cell configured as SBFD.

[0319] - In a situation where the reference cell is not a cell set to SBFD and another cell is a cell set to SBFD, if the collision symbol is a non-SBFD symbol, the terminal can resolve the collision problem based on operation D.

[0320] ▪ For example, Action D may include a predefined collision resolution action. For example, a predefined collision resolution action may include the actions in Table 5.

[0321] As a specific action for resolving directional collisions as described above, the following Method #3-1 or Method #3-2 may be considered.

[0322] [Method #3-1]

[0323] If the reference cell is a cell set to SBFD and the collision occurrence symbol is set to the SBFD symbol in the reference cell, the following collision resolution operations may be performed based on the communication direction of each cell.

[0324] - If UL transmission is enabled for the SBFD symbol of the reference cell,

[0325] ▪ If the other cell and the reference cell are cells in the same frequency band (e.g., if the reference cell and the other cell are cells for intra-band CA), the terminal may perform the following collision resolution actions. For example, if the TDD uplink / downlink setting in the other cell for the collision symbol is a DL symbol, the terminal may consider the collision symbol as a UL symbol. Or, if the TDD uplink / downlink setting in the other cell for the collision symbol is set to a flexible symbol and DL reception is configured by the RRC setting, the terminal may drop the DL reception in the other cell for the collision symbol. In this case, the terminal may not expect dynamic DL to be scheduled in the other cell for the collision symbol.

[0326] ▪ If the other cell and the reference cell are cells in different frequency bands (e.g., if the reference cell and the other cell are cells for inter-band CA), the terminal may perform the following collision resolution actions. For example, if the TDD uplink / downlink setting in the other cell for the collision symbol is a DL symbol, the terminal may consider the collision symbol as a UL symbol rather than a DL. Or, if the TDD uplink / downlink setting in the other cell for the collision symbol is set to a flexible symbol and DL reception is configured by the RRC setting, the terminal may drop the DL reception in the other cell for the collision symbol. In this case, the terminal may not expect dynamic DL to be scheduled in the other cell for the collision symbol.

[0327] - If DL transmission is set for the SBFD symbol of the reference cell,

[0328] ▪ If the other cell and the reference cell are cells in the same frequency band (e.g., if the reference cell and the other cell are cells for intra-band CA), the terminal may perform the following collision resolution operations. For example, if the TDD uplink / downlink configuration in the other cell for the collision symbol is a UL symbol, the terminal may treat the collision symbol as a DL symbol. Or, if the TDD uplink / downlink configuration in the other cell for the collision symbol is set to a flexible symbol and UL transmission is set by the RRC configuration, the terminal may drop the other cell's UL transmission. In this case, the terminal may not expect the other cell's dynamic UL to be scheduled on the collision symbol.

[0329] ▪ If the other cell and the reference cell are cells in different frequency bands (e.g., if the reference cell and the other cell are cells for inter-band CA), the terminal may perform the following collision resolution operations. For example, if the TDD uplink / downlink configuration in the other cell for the collision symbol is a UL symbol, the terminal may treat the collision symbol as a DL symbol. Or, if the TDD uplink / downlink configuration in the other cell for the collision symbol is set to a flexible symbol and UL transmission is set by the RRC configuration, the terminal may drop the other cell's UL transmission. In this case, the terminal may not expect the other cell's dynamic UL to be scheduled on the collision symbol.

[0330] [Method #3-2]

[0331] If the reference cell is a cell that is not set to SBFD, another cell is a cell that is set to SBFD, and the collision occurrence symbol is set to an SBFD symbol in another cell, the following collision resolution operations may be performed based on the communication direction of each cell.

[0332] - If the TDD uplink / downlink setting in the reference cell for the crash-occurring symbol is set to DL,

[0333] ▪ If the other cell and the reference cell are cells in the same frequency band (e.g., if the reference cell and the other cell are cells for intra-band CA), the terminal may perform the following collision resolution operations. For example, if there is a UL transmission set by the RRC in the other cell for a collision symbol, the terminal may consider the collision symbol as a UL symbol. Or, if a dynamic UL is scheduled in the other cell for a collision symbol, the terminal may consider the collision symbol as a UL symbol and perform a dynamic UL transmission in the other cell.

[0334] ▪ If the other cell and the reference cell are cells in different frequency bands (e.g., if the reference cell and the other cell are cells for inter-band CA), the terminal may perform the following collision resolution operations. For example, if there is a UL transmission set by the RRC in the other cell for a collision symbol, the terminal may consider the collision symbol as a UL symbol. Or, if a dynamic UL is scheduled in the other cell for a collision symbol, the terminal may consider the collision symbol as a UL symbol and perform a dynamic UL transmission in the other cell.

[0335] - If the TDD uplink / downlink setting in the reference cell is set to flexible for the collision symbol, and DL reception is set by RRC,

[0336] ▪ If the other cell and the reference cell are cells in the same frequency band (e.g., if the reference cell and the other cell are cells for intra-band CA), the terminal may perform the following collision resolution operations. For example, if there is a UL transmission set by the RRC of the other cell for the collision symbol, the terminal may drop the DL reception set by the RRC of the reference cell for the collision symbol and perform the UL transmission set by the RRC of the other cell. If a dynamic UL is scheduled by the other cell for the collision symbol, the terminal may drop the DL reception set by the RRC of the reference cell for the collision symbol and perform the dynamic UL transmission of the other cell.

[0337] ▪ If the other cell and the reference cell are cells in different frequency bands (e.g., if the reference cell and the other cell are cells for inter-band CA), the terminal may perform the following collision resolution operations. For example, if there is a UL transmission set by the RRC in the other cell for a collision symbol, the terminal may drop the DL reception set by the RRC of the reference cell for the collision symbol and transmit the UL set by the RRC of the other cell. If a dynamic UL is scheduled in the other cell for a collision symbol, the terminal may drop the DL reception set by the RRC of the reference cell for the collision symbol and transmit the dynamic UL of the other cell.

[0338] - If the TDD uplink / downlink setting in the reference cell for the collision occurrence symbol is set to UL,

[0339] ▪ If the other cell and the reference cell are cells in the same frequency band (e.g., if the reference cell and the other cell are cells for intra-band CA), the terminal may not expect the TDD uplink / downlink configuration in the other cell for the collision symbol to be DL or flexible. That is, if the collision symbol is a UL symbol in the reference cell, it corresponds to a non-SBFD symbol in the other cell, and accordingly, the terminal may not expect a collision to occur between the reference cell and the other cell.

[0340] ▪ If the other cell and the reference cell are cells of different frequency bands (e.g., if the reference cell and the other cell are cells for inter-band CA), based on the existence of a DL reception set by the RRC in the other cell for the collision symbol, the terminal may drop the DL reception set by the RRC in the other cell for the collision symbol and assume that the symbol is UL. The terminal may not expect a dynamic DL to be scheduled in the other cell for the collision symbol.

[0341] - If the TDD uplink / downlink setting in the reference cell is set to flexible for the collision symbol, and UL transmission is set by RRC,

[0342] ▪ If the other cell and the reference cell are cells in the same frequency band (e.g., if the reference cell and the other cell are cells for intra-band CA), the terminal may perform the following collision resolution operations. For example, if there is a DL reception set by the RRC in the other cell for a collision symbol, the terminal may drop the UL transmission set by the RRC in the reference cell for the collision symbol and perform the DL reception set by the RRC in the other cell. Or, if there is a dynamically scheduled DL reception in the other cell for a collision symbol, the terminal may drop the UL transmission set by the RRC in the reference cell for the collision symbol and receive the dynamically scheduled DL in the other cell.

[0343] ▪ If the other cell and the reference cell are cells in different frequency bands (e.g., if the reference cell and the other cell are cells for inter-band CA), the terminal may perform the following collision resolution operations. For example, if there is a DL reception set by the RRC in the other cell for a collision symbol, the terminal may drop the UL transmission set by the RRC in the reference cell for the collision symbol and perform the DL reception set by the RRC in the other cell. Or, if there is a dynamically scheduled DL reception in the other cell for a collision symbol, the terminal may drop the UL transmission set by the RRC in the reference cell for the collision symbol and receive the dynamically scheduled DL in the other cell.

[0344] [Fourth Embodiment: Terminal Capability Report]

[0345] According to one embodiment of the present disclosure, a terminal may report its capability (UE capability) information to a base station. The capability information of the terminal may include information indicating whether the terminal is capable of performing SBFD operations and CA operations simultaneously. Being capable of performing SBFD operations and CA operations simultaneously may be understood as allowing simultaneous operation of SBFD and CA. For example, the terminal may transmit capability information to a base station indicating that the terminal allows simultaneous SBFD operations and CA operations. Based on capability information received from the terminal, the base station may set a plurality of cells, including at least one cell configured as SBFD, as cells for the terminal's CA. Alternatively, the terminal may transmit terminal capability information to a base station indicating that the terminal does not allow simultaneous SBFD operations and CA operations. Based on capability information received from the terminal, the base station may set a plurality of cells that do not include a cell configured as SBFD as cells for the terminal's CA. If the terminal is not capable of performing SBFD operations and CA operations simultaneously, the plurality of cells for the terminal's CA may all be cells that are not configured as SBFD.

[0346] According to one embodiment of the present disclosure, a terminal may report capability information of the terminal to a base station. The capability information of the terminal may include whether the terminal can perform collision handling in a CA environment using a plurality of cells including a cell configured as an SBFD. Collision handling may be understood as resolving or solving a collision problem for a specific symbol. For example, the terminal may transmit capability information to a base station indicating that it can perform collision handling in a situation where it performs a CA operation using a plurality of cells including a cell configured as an SBFD. Based on the capability information received from the terminal, the base station may enable the collision handling function for the terminal's communication direction via an RRC message. For example, the base station may configure the terminal to perform a collision handling operation by transmitting an RRC message to the terminal in which a directional collision handling parameter is set to active (e.g., directionalCollisionHanling = enable). As another example, the terminal may transmit capability information to a base station indicating that it cannot perform collision handling in a situation where it performs a CA operation using a plurality of cells including a cell configured as an SBFD. Based on capability information received from a terminal, the base station can control the configuration and scheduling of each symbol to prevent directional collision problems between multiple cells.

[0347] The embodiments of the present disclosure described above may each be implemented independently, or two or more embodiments may be implemented in combination with each other. Additionally, the applicability of each embodiment may be determined based on the settings or instructions of a base station. For example, the applicability of each embodiment may be determined based on instructions from upper-layer signaling or control signals from a base station.

[0348] Through the embodiments of the present invention, by effectively controlling uplink transmission and reception in a wireless communication system, it is expected that cell yield will be improved, latency will be reduced, transmission and reception signal reliability will be improved, and coverage will be increased. In particular, by effectively handling the problem of uplink directional collision between multiple cells in a system operating as an SBFD, uplink transmission can be optimized and the resource utilization efficiency of the entire system can be maximized.

[0349]

[0350] FIG. 13 is a flowchart illustrating a method in which a terminal performs communication according to one embodiment of the present disclosure.

[0351] The operations disclosed in the procedure of FIG. 13 may be performed in combination with various embodiments of the present disclosure. In one example, the operations disclosed in the flowchart of FIG. 13 may be performed based on at least one of the devices shown in FIG. 1 through 4b. In one example, the terminal of FIG. 13 may correspond to the second wireless device (300b) of FIG. 3, and the base station may correspond to the first wireless device (300a) of FIG. 3. In another example, the terminal of FIG. 13 may correspond to the first wireless device (300a) of FIG. 3, and the base station may correspond to the second wireless device (300b) of FIG. 3. In another example, the terminal of FIG. 13 may correspond to at least one of the terminals shown in FIG. 1, and the base station may correspond to at least one of the base stations shown in FIG. 1.

[0352] Referring to FIG. 13, in step S1301, the terminal receives configuration information. The terminal may receive configuration information for a plurality of cells for carrier aggregation (CA) from a base station. According to one embodiment, the plurality of cells for CA may include at least one cell configured to operate as Subband Full-Duplex (SBFD). Here, the cell configured to operate as SBFD can be understood as a cell configured as SBFD.

[0353] According to one embodiment, configuration information for a plurality of cells may include configuration information for each cell included in the plurality of cells. Configuration information for each cell may include at least one of information related to whether the cell is configured as SBFD, TDD uplink / downlink configuration information (e.g., TDD-UL-DL configuration), or configuration information related to the communication direction of at least one symbol.

[0354] According to one embodiment, the configuration information related to the communication direction of at least one symbol may include communication direction configuration information determined by a base station for an SBFD symbol, and semi-static configuration information for setting uplink transmission or downlink reception of at least one symbol.

[0355] According to one embodiment, the setting information may further include at least one of setting information for directional collision handling (e.g., directionalCollisionHandling-r16) or information related to determining a reference cell (e.g., information indicating whether to prioritize the cell set by SBFD).

[0356] In step S1303, the terminal determines the communication direction. The terminal may determine the communication direction for at least one symbol based on at least one cell among a plurality of cells that is set as SBFD. According to one embodiment, the terminal may identify the cells that are activated for at least one symbol among a plurality of cells for CA, and determine the communication direction for at least one symbol as an uplink or a downlink based on the configuration information for at least one cell among the activated cells that is set as SBFD.

[0357] According to one embodiment, a terminal determines a cell satisfying a predetermined condition among a plurality of cells as a reference cell, and can determine a communication direction based on at least one of a symbol direction or a symbol type set in the reference cell for at least one symbol. The symbol direction may include at least one of uplink (UL), downlink (DL), or flexible. The symbol type may include at least one of SBFD or non-SBFD. In the present disclosure, a symbol with a symbol direction set to uplink may be referred to as an UL symbol, a symbol with a symbol direction set to downlink may be referred to as a DL symbol, and a symbol with a symbol direction set to flexible may be referred to as a flexible symbol. Additionally, in the present disclosure, a symbol with a symbol type set to SBFD may be referred to as an SBFD symbol, and a symbol with a symbol type set to non-SBFD may be referred to as a non-SBFD symbol. According to one embodiment, the symbol direction or symbol type may be set by upper layer signaling.

[0358] According to one embodiment, a predetermined condition may include at least one of whether the cell is activated for at least one symbol, whether the cell is set to SBFD, or a condition for a cell index. For example, the terminal may determine a reference cell among a plurality of cells as described in Example #1.

[0359] According to one embodiment, if the determined reference cell is a cell configured as SBFD, the terminal can determine the communication direction for at least one symbol based on the symbol direction configured by the TDD uplink / downlink configuration information (TDD-UL-DL configuration) of the reference cell for at least one symbol. For example, if the symbol direction of a specific symbol configured by the TDD uplink / downlink configuration information in the reference cell is UL, the terminal can determine the communication direction of the corresponding symbol as uplink. Or, if the symbol direction of a specific symbol configured by the TDD uplink / downlink configuration information in the reference cell is DL, the terminal can determine the communication direction of the corresponding symbol as downlink. For example, the terminal can determine the communication direction of at least one symbol based on the TDD uplink / downlink configuration information as described in Method #2-1, Method #2-2, and / or Method #2-3 of Example #2.

[0360] According to one embodiment, when the symbol direction set by the TDD uplink / downlink configuration information (TDD-UL-DL configuration) of a reference cell for at least one symbol is flexible, the terminal can determine the communication direction for at least one symbol based on uplink transmission or downlink reception indicated by at least one of dynamic scheduling or semi-static configuration for at least one symbol. For example, when at least one symbol is a flexible symbol, the terminal can determine at least one communication direction as UL transmission based on UL transmission (e.g., SRS, PUCCH, PUSCH, or PRACH) being set or scheduled for at least one symbol, and determine at least one communication direction as DL based on DL reception (e.g., PDCCH, PDSCH, or CSI-RS) being set or scheduled for at least one symbol. For example, the terminal may determine the communication direction of the corresponding symbol based on UL transmission or DL ​​reception set or scheduled for the flexible symbol, as described in Method #2-1, Method #2-2, and / or Method #2-3 of Example #2.

[0361] According to one embodiment, if the symbol type of at least one symbol is an SBFD symbol, the terminal may determine the communication direction for at least one symbol based on uplink transmission or downlink reception indicated by dynamic scheduling or quasi-static setting for at least one symbol. For example, if at least one symbol is an SBFD symbol, the terminal may determine at least one communication direction as UL transmission based on UL transmission (e.g., SRS, PUCCH, PUSCH, or PRACH) being set or scheduled for at least one symbol, and determine at least one communication direction as DL based on DL reception (e.g., PDCCH, PDSCH, or CSI-RS) being set or scheduled for at least one symbol. For example, the terminal may determine the communication direction of the corresponding symbol based on UL transmission or DL ​​reception set or scheduled for the SBFD symbol, as described in Method #2-1 of Example #2.

[0362] According to one embodiment, if the symbol type of at least one symbol is an SBFD symbol, the terminal can determine the communication direction for at least one symbol based on the symbol direction set by the TDD uplink / downlink configuration information (TDD-UL-DL configuration) of the reference cell for at least one symbol. For example, if the symbol direction set by the TDD uplink / downlink configuration information in the reference cell for at least one symbol that is an SBFD symbol is DL, the terminal can determine the communication direction of the corresponding SBFD symbol as a downlink. According to one embodiment, if the symbol direction set by the TDD uplink / downlink configuration information in the reference cell for at least one symbol that is an SBFD symbol is flexible, the terminal can determine the communication direction for the corresponding SBFD symbol based on uplink transmission or downlink reception indicated by dynamic scheduling or quasi-static configuration. For example, as described in Method #2-2 of Example #2, if at least one symbol is an SBFD symbol, the terminal can determine the communication direction of at least one symbol based on the TDD uplink / downlink configuration information.

[0363] According to one embodiment, if the symbol type of at least one symbol is an SBFD symbol, the terminal can determine the communication direction for at least one symbol as an uplink. For example, the terminal can determine the communication direction for at least one symbol as an uplink, as described in Method #2-3 of Example #2.

[0364] According to one embodiment, based on the fact that the symbol type of at least one symbol is an SBFD symbol, the terminal can receive information from a base station indicating the communication direction for at least one symbol. The terminal can determine the communication direction indicated by the information received from the base station as the communication direction for at least one symbol.

[0365] According to one embodiment, a terminal can determine whether the communication directions of a reference cell and at least one other cell conflict. Here, the at least one other cell may include other active cells excluding the reference cell among the cells included in a plurality of cells. If the communication direction of the reference cell and the communication direction of at least one other cell for a specific cell are set differently and / or determined, the terminal can determine that the communication directions conflict at a specific symbol. In this case, the symbol in which the communication directions of the reference cell and at least one other cell conflict may be referred to as the conflict occurrence symbol. When the communication directions of the reference cell and at least one other cell conflict, the terminal can control the communication direction of the conflict occurrence symbol based on whether the conflict occurrence symbol is an SBFD symbol. That the conflict occurrence symbol is an SBFD symbol can be understood as the symbol being set as an SBFD symbol in the reference cell or set as an SBFD in at least one other cell. For example, as described in Example #3, the terminal can control the communication direction of the conflict occurrence symbol based on whether the conflict occurrence symbol is an SBFD symbol. According to one embodiment, controlling the communication direction of a collision occurrence symbol can be understood as dropping, adjusting, changing, and / or redetermining the communication direction set and / or determined in each of the reference cell and at least one other cell for the collision occurrence symbol.

[0366] According to one embodiment, if the collision symbol is an SBFD symbol, the terminal may assign a higher priority to the cell set as SBFD or the communication direction of the cell set as SBFD among the reference cell and at least one other cell. For example, if the reference cell is a cell set as SBFD, the terminal may control the reference cell to have a higher priority than at least one other cell regarding the collision symbol. Alternatively, if the reference cell is a cell set as SBFD, the terminal may control the communication direction of the reference cell regarding the collision symbol to have a higher priority than the communication direction of at least one other cell regarding the collision symbol.

[0367] According to one embodiment, if the collision symbol is an SBFD symbol, the terminal may drop transmission or reception in either the reference cell or at least one other cell based on whether the reference cell and at least one other cell are cells set as SBFD, or based on the priority for the reference cell and at least one other cell. For example, if the reference cell is a cell set as SBFD and the collision symbol is set as an SBFD symbol in the reference cell, UL transmission or DL ​​reception according to the communication direction set and / or determined in the reference cell for the collision symbol may be performed, and UL transmission or DL ​​reception in at least one other cell may be dropped. As another example, if the reference cell is not a cell set as SBFD, and at least one other cell is a cell set as SBFD, and the collision symbol is set as an SBFD symbol in at least one other cell, UL transmission or DL ​​reception according to the communication direction set and / or determined in at least one cell for the collision symbol may be performed, and UL transmission or DL ​​reception in the reference cell may be dropped. For example, the terminal can prevent a collision from occurring during actual transmission or reception at a said symbol by controlling the communication direction of a reference cell and at least one other cell for a collision-occurring symbol, as described in Method #3-1 and / or Method #3-2 of Example #3.

[0368] In step S1305, the terminal performs communication based on the communication direction. The terminal may perform communication using multiple cells in at least one symbol based on the determined communication direction. For example, in step S1303, the terminal may perform UL transmission or DL ​​reception in a reference cell and / or at least one cell based on the communication direction determined for at least one symbol based on at least one cell set as SBFD.

[0369] According to one embodiment, the terminal may transmit capability information of the terminal to a base station. The capability information of the terminal may include at least one of information indicating whether the terminal can simultaneously support the SBFD and the CA, or information indicating whether the terminal supports a function to handle collisions regarding the communication direction between multiple cells in a CA environment including a cell configured as an SBFD. According to one embodiment, the capability information of the terminal may be transmitted to the base station before configuration information for multiple cells for CA is received.

[0370]

[0371] FIG. 14 is a flowchart illustrating a method in which a base station performs communication according to one embodiment of the present disclosure.

[0372] The operations disclosed in the flowchart of FIG. 14 may be performed in combination with various embodiments of the present disclosure. In one example, the operations disclosed in the flowchart of FIG. 14 may be performed based on at least one of the devices shown in FIG. 1 to FIG. 4b. In one example, the base station of FIG. 14 may correspond to the second wireless device (300b) of FIG. 3, and the terminal may correspond to the first wireless device (300a) of FIG. 3. In another example, the base station of FIG. 14 may correspond to the first wireless device (300a) of FIG. 3, and the terminal may correspond to the second wireless device (300b) of FIG. 3. In another example, the base station of FIG. 14 may correspond to at least one of the terminals shown in FIG. 1, and the terminal may correspond to at least one of the base stations shown in FIG. 1.

[0373] Referring to FIG. 14, in step S1401, the base station receives capability information. The base station may receive capability information of the terminal. According to one embodiment, the capability information of the terminal may include at least one of information indicating whether the terminal can simultaneously support SBFD (Subband Full-Duplex) and CA (Carrier Aggregation), or information indicating whether the terminal supports a function to handle collisions regarding the communication direction between multiple cells in a CA environment including a cell set as SBFD.

[0374] In step S1403, the base station determines a plurality of cells for CA. The base station may determine a plurality of cells for CA based on the terminal's capability information. According to one embodiment, the base station may determine whether the terminal is capable of simultaneous support for SBFD and CA based on the terminal's capability information, and may determine a plurality of cells for CA based on whether simultaneous support for SBFD and CA is possible. For example, based on the determination that the terminal is capable of simultaneous support for SBFD and CA, the base station may determine a plurality of cells including at least one cell configured as SBFD as a plurality of cells for CA. Alternatively, based on the determination that the terminal is not capable of simultaneous support for SBFD and CA, a plurality of cells not including at least one cell configured as SBFD may be determined as a plurality of cells for CA. In other words, if simultaneous support for SBFD and CA is not possible for the terminal, the plurality of cells for CA of the terminal may include only cells that are not configured as SBFD.

[0375] In step S1403, the base station transmits configuration information. The base station may transmit configuration information for a plurality of cells for CA to a terminal. According to one embodiment, the plurality of cells for CA may include at least one cell configured to operate as Subband Full-Duplex (SBFD). Here, the cell configured to operate as SBFD can be understood as a cell configured as SBFD.

[0376] According to one embodiment, configuration information for a plurality of cells may include configuration information for each cell included in the plurality of cells. Configuration information for each cell may include at least one of information related to whether the cell is configured as SBFD, TDD uplink / downlink configuration information (e.g., TDD-UL-DL configuration), or configuration information related to the communication direction of at least one symbol.

[0377] According to one embodiment, the configuration information related to the communication direction of at least one symbol may include communication direction configuration information determined by a base station for an SBFD symbol, and semi-static configuration information for setting uplink transmission or downlink reception of at least one symbol.

[0378] According to one embodiment, the setting information may further include at least one of setting information for directional collision handling (e.g., directionalCollisionHandling-r16) or information related to determining a reference cell (e.g., information indicating whether to prioritize the cell set by SBFD).

[0379]

[0380]

[0381]

[0382] 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 all types of recording devices 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, and a computer-readable program or code may be stored and executed in a distributed manner.

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

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

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

[0386] 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 performed by a terminal in a wireless communication system, A step of receiving configuration information for multiple cells for CA (carrier aggregation); A step of determining a communication direction for at least one symbol based on at least one cell configured as SBFD (Subband Full-Duplex) among the plurality of cells; and A method comprising the step of performing communication using the plurality of cells in the at least one symbol based on the communication direction determined above.

2. In Claim 1, The step of determining the communication direction for the above at least one symbol is, A step of determining a cell satisfying a predetermined condition among the plurality of cells above as a reference cell; and The method includes the step of determining a communication direction for at least one symbol based on at least one of a symbol direction or a symbol type set in the reference cell for at least one symbol, and The above symbol direction includes at least one of an upward link, a downward link, or a flexible, and The above symbol type comprises at least one of SBFD or non-SBFD, a method.

3. In Claim 2, A method in which the above-determined condition includes at least one of whether the cell is activated for the at least one symbol, whether the cell is set to SBFD, or a condition for the cell index.

4. In Claim 2, A method in which, based on the fact that the reference cell is a cell set as the SBFD, the communication direction for the at least one symbol is determined based on the symbol direction set by the TDD (Time Division Duplex) uplink / downlink configuration information (TDD-UL-DL configuration information) for the at least one symbol.

5. In Claim 2, A method in which the reference cell is a cell configured as the SBFD, and the symbol direction configured by Time Division Duplex (TDD) uplink / downlink configuration information (TDD-UL-DL configuration information) for the at least one symbol is flexible, wherein the communication direction for the at least one symbol is determined based on uplink transmission or downlink reception indicated by dynamic scheduling or semi-static configuration for the at least one symbol.

6. In Claim 2, A method in which, based on the fact that the symbol type of at least one symbol is an SBFD symbol, the communication direction for the at least one symbol is determined based on at least one of uplink transmission or downlink reception indicated by dynamic scheduling or semi-static configuration, or the symbol direction set by TDD uplink / downlink configuration information for the at least one symbol.

7. In Claim 2, A method in which, based on the fact that the type of at least one symbol is an SBFD symbol, the communication direction for the at least one symbol is determined to be an uplink.

8. In Claim 2, The step of determining the communication direction for the at least one symbol based on at least one of the symbol direction or symbol type set in the reference cell for the at least one symbol, A step of receiving information from a base station indicating a communication direction for the at least one symbol based on the fact that the at least one symbol type is the SBFD symbol type; and A method comprising the step of determining the communication direction indicated above as a communication direction for at least one symbol.

9. In Claim 2, The method further includes a step of determining whether the communication direction of at least one other cell among the reference cell and the plurality of cells, excluding the reference cell, conflicts. A method in which the communication direction of the reference cell and the at least one other cell collides, wherein the communication direction in the at least one symbol is controlled based on whether the colliding symbol is an SBFD symbol.

10. In Claim 2, The method further includes a step of determining whether the communication direction of at least one other cell among the reference cell and the plurality of cells, excluding the reference cell, conflicts. A method in which, based on the fact that the communication directions of the reference cell and the at least one other cell collide and the collide occurrence symbol is an SBFD symbol, a higher priority is assigned to the communication direction of the cell set as SBFD than to the priority for the communication direction of the cell not set as SBFD among the reference cell and the at least one other cell.

11. In Claim 2, The method further includes a step of determining whether the communication direction of at least one other cell among the reference cell and the plurality of cells, excluding the reference cell, conflicts. A method of dropping transmission or reception in either the reference cell or the at least one other cell based on whether the reference cell and the at least one other cell are cells set as SBFD, or based on the priority for the reference cell and the at least one other cell, based on the communication direction of the reference cell and the at least one other cell colliding and the collision occurrence symbol being an SBFD symbol.

12. In Claim 1, The method further includes the step of transmitting capability information of the above terminal to a base station, A method comprising at least one of the above capability information, wherein the above capability information includes information indicating whether the terminal is capable of simultaneous support for SBFD and CA, or information indicating whether it supports a function to handle communication direction collisions in a CA environment including a cell set as SBFD.

13. In Claim 1, A method further comprising the step of receiving a message from a base station that enables a collision handling function for the communication direction of multiple cells.

14. In a terminal of a wireless communication system, At least one transceiver; 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 configuration information for multiple cells for CA (carrier aggregation); A step of determining a communication direction for at least one symbol based on at least one cell configured as SBFD (Subband Full-Duplex) among the plurality of cells; and A terminal comprising the step of performing communication using the plurality of cells in the at least one symbol based on the communication direction determined above.

15. In a base station of a wireless communication system, At least one transceiver; At least one processor; and It includes at least one memory connected to the above-mentioned at least one processor to be operable, and storing instructions that control the base station to perform operations when executed by the processor, wherein The above operations are, Step of receiving capability information of the terminal; A step of determining a plurality of cells for CA (carrier aggregation) based on capability information of the above terminal; and It includes the step of transmitting setting information for the plurality of cells mentioned above, A base station, wherein capability information of the terminal comprises at least one of information indicating whether the terminal can simultaneously support SBFD (Subband Full-Duplex) and CA, or information indicating whether it supports a function to handle collisions regarding the communication direction between multiple cells in a CA environment including a cell configured as SBFD.