Method and device for resource allocation in communication system supporting SBFD operation

Abstract

Disclosed are a method and a device for resource allocation in a communication system supporting an SBFD operation. A method of a user equipment (UE) comprises the steps of: receiving, from a base station, first configuration information of one or more time division duplexing (TDD)-uplink (UL)-downlink (DL) patterns; determining the time period of a subband full duplex (SBFD) subband on the basis of the period of the one or more TDD-UL-DL patterns indicated by the first configuration information; and communicating with the base station within the time period of the SBFD subband.

Description

Method and device for resource allocation in a communication system supporting SBFD operation

[0001] The present disclosure relates to improved communication technology, and more particularly, to resource allocation technology in a communication system supporting subband full duplex (SBFD) operation.

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

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

[0004] Meanwhile, a communication network may support subband full duplex (SBFD) operation. In a communication network supporting SBFD operation, an uplink (UL) subband may be configured in a downlink (DL) section. The DL section in which the UL subband is configured may be referred to as an SBFD resource. If the frequency resources of a physical channel are configured without considering the SBFD resources, transmission and / or reception on the physical channel may fail due to transmission collision and / or interference. To solve the above problem, methods for allocating frequency resources of a physical channel that consider the SBFD resources may be necessary.

[0005] The purpose of the present disclosure to solve the above problems is to provide a method and device for resource allocation of a physical channel in a communication system supporting subband full duplex (SBFD) operation.

[0006] A method of a UE (user equipment) according to embodiments of the present disclosure for achieving the above object includes the steps of: receiving first configuration information of one or more time division duplexing (TDD)-uplink (UL)-downlink (DL) patterns from a base station; determining a time period of a subband full duplex (SBFD) subband based on a period of the one or more TDD-UL-DL patterns indicated by the first configuration information; and performing communication with the base station within the time period of the SBFD subband.

[0007] Based on the fact that one TDD-UL-DL pattern is indicated to the UE by the first configuration information, the time period of the SBFD subband can be determined to be the same as the period of the one TDD-UL-DL pattern.

[0008] Based on the two TDD-UL-DL patterns being indicated to the UE by the first configuration information, the time period of the SBFD subband can be determined to be equal to the sum of the periods of the two TDD-UL-DL patterns.

[0009] The method of the UE may further include a step of receiving, from the base station, second configuration information of SBFD symbols configured within the period of the one or more TDD-UL-DL patterns.

[0010] The second configuration information may include at least one of an index of a starting slot, an index of a starting symbol within the starting slot, an index of an ending slot, or an index of an ending symbol within the ending slot, wherein the starting slot may be a first slot in which an SBFD symbol is set among slots within the period of the one or more TDD-UL-DL patterns, the starting symbol may be a first SBFD symbol within the starting slot, the ending slot may be a last slot in which the SBFD symbol is set among slots within the period of the one or more TDD-UL-DL patterns, and the ending symbol may be a last SBFD symbol within the ending slot.

[0011] The first configuration information and the second configuration information may be included in the same message or different messages transmitted by the base station, and the same message may be system information, and each of the different messages may be the system information, an RRC (radio resource control) message, a MAC (medium access control) CE (control element), or DCI (downlink control information).

[0012] The communication between the UE and the base station can be performed using the SBFD symbols within the time period of the SBFD subband.

[0013] According to embodiments of the present disclosure for achieving the above object, a method of a base station includes the steps of: determining one or more time division duplexing (TDD)-uplink (UL)-downlink (DL) patterns; transmitting first configuration information of the one or more TDD patterns to a user equipment (UE); and performing communication with the UE within a time period of a subband full duplex (SBFD) subband determined based on a period of the one or more TDD-UL-DL patterns indicated by the first configuration information.

[0014] Based on the fact that one TDD-UL-DL pattern is indicated to the UE by the first configuration information, the time period of the SBFD subband can be determined to be the same as the period of the one TDD-UL-DL pattern.

[0015] Based on the two TDD-UL-DL patterns being indicated to the UE by the first configuration information, the time period of the SBFD subband can be determined to be equal to the sum of the periods of the two TDD-UL-DL patterns.

[0016] The method of the base station may further include the steps of: determining SBFD symbols set within the period of the one or more TDD-UL-DL patterns; and transmitting second configuration information of the SBFD symbols to the UE.

[0017] The second configuration information may include at least one of an index of a starting slot, an index of a starting symbol within the starting slot, an index of an ending slot, or an index of an ending symbol within the ending slot, wherein the starting slot may be a first slot in which an SBFD symbol is set among slots within the period of the one or more TDD-UL-DL patterns, the starting symbol may be a first SBFD symbol within the starting slot, the ending slot may be a last slot in which the SBFD symbol is set among slots within the period of the one or more TDD-UL-DL patterns, and the ending symbol may be a last SBFD symbol within the ending slot.

[0018] The first configuration information and the second configuration information may be included in the same message or different messages transmitted by the base station, and the same message may be system information, and each of the different messages may be the system information, an RRC (radio resource control) message, a MAC (medium access control) CE (control element), or DCI (downlink control information).

[0019] The communication between the base station and the UE can be performed using the SBFD symbols within the time period of the SBFD subband.

[0020] According to embodiments of the present disclosure for achieving the above object, a user equipment (UE) includes at least one processor, wherein the at least one processor causes the UE to receive first configuration information of one or more time division duplexing (TDD)-uplink (UL)-downlink (DL) patterns from a base station; determine a time period of a subband full duplex (SBFD) subband based on a period of the one or more TDD-UL-DL patterns indicated by the first configuration information; and perform communication with the base station within the time period of the SBFD subband.

[0021] Based on the fact that one TDD-UL-DL pattern is indicated to the UE by the first configuration information, the time period of the SBFD subband can be determined to be the same as the period of the one TDD-UL-DL pattern.

[0022] Based on the two TDD-UL-DL patterns being indicated to the UE by the first configuration information, the time period of the SBFD subband can be determined to be equal to the sum of the periods of the two TDD-UL-DL patterns.

[0023] The at least one processor may further cause the UE to receive, from the base station, second configuration information of SBFD symbols configured within the period of the one or more TDD-UL-DL patterns.

[0024] The second configuration information may include at least one of an index of a starting slot, an index of a starting symbol within the starting slot, an index of an ending slot, or an index of an ending symbol within the ending slot, wherein the starting slot may be a first slot in which an SBFD symbol is set among slots within the period of the one or more TDD-UL-DL patterns, the starting symbol may be a first SBFD symbol within the starting slot, the ending slot may be a last slot in which the SBFD symbol is set among slots within the period of the one or more TDD-UL-DL patterns, and the ending symbol may be a last SBFD symbol within the ending slot.

[0025] The first configuration information and the second configuration information may be included in the same message or different messages transmitted by the base station, and the same message may be system information, and each of the different messages may be the system information, an RRC (radio resource control) message, a MAC (medium access control) CE (control element), or DCI (downlink control information).

[0026] According to the present disclosure, the time period of a subband full duplex (SBFD) subband can be determined based on the period(s) of one or more time division duplexing (TDD)-uplink (UL)-downlink (DL) patterns. In this case, separate signaling indicating the time period of the SBFD subband is not necessary, so the efficiency of the communication system can be improved. Since the time period of the SBFD subband is determined based on the period(s) of one or more TDD-UL-DL patterns indicated by the base station, ambiguity regarding the time period of the SBFD subband may not occur at the base station and / or the terminal. Since the positions of SBFD symbols within the period(s) of one or more TDD-UL-DL patterns are indicated by the base station, ambiguity regarding the positions of SBFD symbols may not occur at the base station and / or the terminal. Therefore, the performance of the communication system can be improved.

[0027] Figure 1 is a conceptual diagram illustrating embodiments of a communication system.

[0028] Figure 2 is a block diagram illustrating embodiments of communication nodes constituting a communication system.

[0029] Figure 3 is a block diagram illustrating embodiments of communication nodes that perform communication.

[0030] Figure 4a is a block diagram illustrating embodiments of a transmission path.

[0031] Figure 4b is a block diagram illustrating embodiments of a receiving path.

[0032] Figure 5 is a conceptual diagram illustrating embodiments of system frames in a communication system.

[0033] Figure 6 is a conceptual diagram illustrating embodiments of subframes in a communication system.

[0034] Figure 7 is a conceptual diagram illustrating embodiments of slots in a communication system.

[0035] Figure 8 is a conceptual diagram illustrating embodiments of time-frequency resources in a communication system.

[0036] Figure 9 is a conceptual diagram illustrating a method of setting RBG in scenario #1 where resource allocation type 0 is used.

[0037] Figure 10 is a conceptual diagram illustrating a method for setting RBG (e.g., DL RBG) based on method #1 in scenario #1 where resource allocation type 0 is used.

[0038] Figure 11 is a conceptual diagram illustrating a method for setting RBG (e.g., DL RBG) based on method #2 in scenario #1 where resource allocation type 0 is used.

[0039] Figure 12 is a conceptual diagram illustrating a method for setting RBG (e.g., DL RBG) based on method #2-1 in scenario #1 where resource allocation type 0 is used.

[0040] Figure 13 is a conceptual diagram illustrating a method for setting RBG (e.g., DL RBG) based on method #2-2 in scenario #1 where resource allocation type 0 is used.

[0041] Figure 14 is a conceptual diagram illustrating embodiments based on method #3 in scenario #2 where resource allocation type 1 is used.

[0042] Figure 15 is a conceptual diagram illustrating embodiments based on method #4 in scenario #2 where resource allocation type 1 is used.

[0043] Figure 16 is a flowchart illustrating a method of transmitting and receiving a data channel.

[0044] Figure 17 is a flowchart illustrating a method for setting SBFD resources.

[0045] This disclosure may be subject to various modifications and various embodiments. Specific embodiments are illustrated and described in detail in the drawings. However, this is not intended to limit the disclosure to specific embodiments, but rather to encompass all modifications, equivalents, and alternatives falling within the spirit and technical scope of the disclosure.

[0046] While terms such as "first" and "second" may be used to describe various components, these components should not be limited by these terms. These terms are used solely to distinguish one component from another. For example, without departing from the scope of the present disclosure, a first component could be referred to as a "second component," and similarly, a second component could also be referred to as a "first component." The term "and / or" may refer to a combination of multiple related items described herein or to any of multiple related items described herein.

[0047] 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 combinations of one or more 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 combinations of one or more of A and B.”

[0048] 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.”

[0049] When a component is referred to as being "connected" or "connected" to another component, it should be understood that it may be directly connected or connected to that other component, but that there may be other components intervening. Conversely, when a component is referred to as being "directly connected" or "connected" to another component, it should be understood that there are no other components intervening.

[0050] The terminology used in this disclosure is only used to describe specific embodiments and is not intended to limit the present disclosure. The singular expression includes the plural expression unless the context clearly indicates otherwise. In this disclosure, it should be understood that the terms "comprises" or "has" indicate the presence of a feature, number, step, operation, component, part, or combination thereof described in the specification, but do not preclude the presence or addition of one or more other features, numbers, steps, operations, components, parts, or combinations thereof.

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

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

[0053] In an embodiment, even if a method (e.g., transmitting or receiving a signal) performed by a first communication node among communication nodes is described, a corresponding second communication node can perform a method (e.g., receiving or transmitting a signal) corresponding to the method performed by the first communication node. That is, if an operation of a UE (user equipment) is described, a corresponding base station can perform an operation corresponding to the operation of the UE. Conversely, if an operation of a base station is described, a corresponding UE can perform an operation corresponding to the operation of the base station.

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

[0055] 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 a transmission and reception operation of system information (e.g., a master information block (MIB), a system information block (SIB)) and / or a radio resource control (RRC) message. MAC signaling may refer to a transmission and reception operation of a MAC control element (CE). PHY signaling may refer to a transmission and reception operation of control information (e.g., downlink control information (DCI), uplink control information (UCI), sidelink control information (SCI)).

[0056] In the present disclosure, “an operation (e.g., a transmission operation) is set” may mean that “setting information for the operation (e.g., an information element, a parameter)” and / or “information instructing the performance of the operation” is signaled. “An information element (e.g., a parameter) is set” may mean that the 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.” In the present disclosure, time and time point may be used interchangeably. Time may be interpreted as either time or time point depending on the context, and time point may be interpreted as either time or time point depending on the context.

[0057] 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 the term "communication system."

[0058] Figure 1 is a conceptual diagram illustrating embodiments of a communication system.

[0059] 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). In addition, the communication system (100) may further include a core network (e.g., a serving-gateway (S-GW), a packet data network (PDN)-gateway (P-GW), a mobility management entity (MME)). If the communication system (100) is a 5G communication system (e.g., a new radio (NR) system), the core network may include an access and mobility management function (AMF), a user plane function (UPF), a session management function (SMF), etc.

[0060] A plurality of communication nodes (110 to 130) can support a communication protocol specified in the 3rd generation partnership project (3GPP) standard (e.g., LTE communication protocol, LTE-A communication protocol, NR communication protocol, etc.). The plurality of communication nodes (110 to 130) may 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 plurality of communication nodes may have the following structure.

[0061] Figure 2 is a block diagram illustrating embodiments of communication nodes constituting a communication system.

[0062] Referring to FIG. 2, a communication node (200) may include at least one processor (210), a memory (220), and a transmission / reception device (230) that is connected to a network and performs communication. In addition, the communication node (200) may further include an input interface device (240), an output interface device (250), a storage device (260), etc. Each component included in the communication node (200) may be connected by a bus (270) and communicate with each other.

[0063] The processor (210) can execute program commands stored in at least one of the memory (220) and the storage device (260). The processor (210) may refer to a central processing unit (CPU), a graphics processing unit (GPU), or a dedicated processor in which the methods according to embodiments of the present disclosure are performed. Each of the memory (220) and the storage device (260) may be configured with at least one of a volatile storage medium and a non-volatile storage medium. For example, the memory (220) may be configured with at least one of a read-only memory (ROM) and a random access memory (RAM).

[0064] 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 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 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 within the cell coverage of the third base station (110-3). The first terminal (130-1) may be within the cell coverage of the fourth base station (120-1). The sixth terminal (130-6) may be within the cell coverage of the fifth base station (120-2).

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

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

[0067] Meanwhile, each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) may operate in a different frequency band or may operate in the same frequency band. Each of the plurality of 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 the ideal backhaul link or the non-ideal backhaul link. Each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) may be connected to the core network via the ideal backhaul link or the non-ideal backhaul link. Each of the plurality of 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.

[0068] Additionally, each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) may support MIMO transmission (e.g., single user (SU)-MIMO, multi user (MU)-MIMO, massive MIMO, etc.), coordinated multipoint (CoMP) transmission, carrier aggregation (CA) transmission, transmission in an unlicensed band, sidelink communication (e.g., device to device communication (D2D), proximity services (ProSe)), Internet of Things (IoT) 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 scheme, and the fourth terminal (130-4) can receive a signal from the second base station (110-2) by the SU-MIMO scheme. Alternatively, the second base station (110-2) can transmit signals 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 signals from the second base station (110-2) based on the MU-MIMO method.

[0069] 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 scheme, 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) based on the CoMP scheme. Each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) can transmit and receive a signal with terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) within its cell coverage based on the CA scheme. 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 under the control of the second base station (110-2) and the third base station (110-3), respectively.

[0070] Meanwhile, communication nodes performing communication in a communication network may be configured as follows. The communication node illustrated in Fig. 3 may be a specific embodiment of the communication node illustrated in Fig. 2.

[0071] Figure 3 is a block diagram illustrating embodiments of communication nodes that perform communication.

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

[0073] The transmitting processor (311) may perform a processing operation on data (e.g., an encoding operation, a symbol mapping operation, etc.) to generate data symbol(s). The transmitting processor (311) may perform a processing operation on control information (e.g., an encoding operation, a symbol mapping operation, etc.) to generate control symbol(s). In addition, the transmitting processor (311) may generate synchronization / reference symbol(s) for a synchronization signal and / or a reference signal.

[0074] The Tx MIMO processor (312) may perform a spatial processing operation (e.g., a precoding operation) on data symbol(s), control symbol(s), and / or synchronization / reference symbol(s). The output (e.g., a symbol stream) of the Tx MIMO processor (312) may be provided to modulators (MODs) included in the transceivers (313a to 313t). The modulators (MODs) may perform a processing operation on the symbol stream to generate modulation symbols, and may perform an additional processing operation (e.g., an analog conversion operation, an amplification operation, a filtering operation, an upconversion operation) on the modulation symbols to generate signals. The signals generated by the modulators (MODs) of the transceivers (313a to 313t) may be transmitted via the antennas (314a to 314t).

[0075] Signals transmitted by the first communication node (300a) may be received by antennas (364a to 364r) of the second communication node (300b). Signals received by the antennas (364a to 364r) may be provided to demodulators (DEMODs) included in transceivers (363a to 363r). The demodulator (DEMOD) may perform a processing operation (e.g., a filtering operation, an amplification operation, a downconversion operation, a digital conversion operation) on the signal to obtain samples. The demodulator (DEMOD) may perform an additional processing operation on the samples to obtain symbols. The MIMO detector (362) may perform a MIMO detection operation on the symbols. The receiving processor (361) may perform a processing operation (e.g., a deinterleaving operation, a decoding operation) on the symbols. The output of the receiving processor (361) may be provided to a data sink (360) and a controller (366). For example, data may be provided to the data sink (360), and control information may be provided to the controller (366).

[0076] Meanwhile, the second communication node (300b) can transmit a signal to the first communication node (300a). The transmitting processor (368) included in the second communication node (300b) can receive data (e.g., data units) from a data source (367) and perform a processing operation on the data to generate data symbol(s). The transmitting processor (368) can receive control information from the controller (366) and perform a processing operation on the control information to generate control symbol(s). In addition, the transmitting processor (368) can perform a processing operation on a reference signal to generate reference symbol(s).

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

[0078] Signals transmitted by the second communication node (300b) may be received by the antennas (314a to 314r) of the first communication node (300a). The signals received by the antennas (314a to 314r) may be provided to demodulators (DEMODs) included in the transceivers (313a to 313r). The demodulator (DEMOD) may perform a processing operation (e.g., a filtering operation, an amplification operation, a downconversion operation, a digital conversion operation) on the signal to obtain samples. The demodulator (DEMOD) may perform an additional processing operation on the samples to obtain symbols. The MIMO detector (320) may perform a MIMO detection operation on the symbols. The receiving processor (319) may perform a processing operation (e.g., a deinterleaving operation, a decoding operation) on the symbols. The output of the receiving processor (319) may be provided to a data sink (318) and a controller (316). For example, data may be provided to the data sink (318) and control information may be provided to the controller (316).

[0079] Memories (315 and 365) can store data, control information, and / or program code. Scheduler (317) can perform scheduling operations for communication. The processors (311, 312, 319, 361, 368, 369) and controllers (316, 366) illustrated in FIG. 3 may be the processor (210) illustrated in FIG. 2 and may be used to perform the methods described in the present disclosure.

[0080] FIG. 4a is a block diagram illustrating embodiments of a transmission path, and FIG. 4b is a block diagram illustrating embodiments of a reception path.

[0081] Referring to FIGS. 4A and 4B, a transmission path (410) may be implemented in a communication node that transmits a signal, and a reception path (420) may be implemented in 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 (414), a CP (cyclic prefix) addition block (415), and an UC (up-converter) (UC) (416). The receiving 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 may be a natural number.

[0082] In the transmission path (410), information bits may be input to a channel coding and modulation block (411). The channel coding and modulation block (411) may perform a coding operation (e.g., a low-density parity check (LDPC) coding operation, a polar coding operation, etc.) and a modulation operation (e.g., a quadrature phase shift keying (QPSK), a quadrature amplitude modulation (QAM), etc.) on the information bits. The output of the channel coding and modulation block (411) may be a sequence of modulation symbols.

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

[0084] The CP addition block (415) can insert a CP into a 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 at the baseband before up-conversion.

[0085] A signal transmitted from a transmission path (410) may be input to a reception path (420). An operation in the reception path (420) may be the reverse operation of the operation in the transmission path (410). A DC (421) may down-convert the frequency of the received signal to a baseband frequency. A CP removal block (422) may remove a CP from a signal. The output of the CP removal block (422) may be a serial signal. An S-to-P block (423) may convert the serial signal into parallel signals. An N FFT block (424) may perform an FFT algorithm to generate N parallel signals. A P-to-S block (425) may convert the parallel signals into a sequence of modulation symbols. A 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 data.

[0086] In FIGS. 4A and 4B , Discrete Fourier Transform (DFT) and Inverse DFT (IDFT) may be used instead of FFT and IFFT. Each of the blocks (e.g., components) in FIGS. 4A and 4B may be implemented by at least one of hardware, software, or firmware. For example, some of the blocks in FIGS. 4A and 4B 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 , a block may be subdivided into multiple blocks, multiple blocks may be integrated into a single block, some blocks may be omitted, and blocks supporting other functions may be added.

[0087] Figure 5 is a conceptual diagram illustrating embodiments of a system frame in a communication system.

[0088] Referring to FIG. 5, time resources in a communication system can be divided into frame units. 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 (milliseconds). 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 the system frame after system frame #1023 can be #0.

[0089] A system frame may include two half frames. A half frame may be 5 ms long. 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 include 10 subframes. A subframe may be 1 ms long. The 10 subframes within a system frame may be referred to as "subframes #0-9."

[0090] Figure 6 is a conceptual diagram illustrating embodiments of subframes in a communication system.

[0091] Referring to FIG. 6, one subframe may include n slots, where n may be a natural number. Accordingly, one subframe may be composed of one or more slots.

[0092] Figure 7 is a conceptual diagram illustrating embodiments of slots in a communication system.

[0093] Referring to FIG. 7, a single slot may include one or more symbols. A single slot illustrated in FIG. 7 may include 14 symbols. The length of a slot may vary depending on the number and length of symbols contained in the slot. Alternatively, the length of a slot may vary depending on numerology.

[0094] In a communication system, the numerology applied to physical signals and channels may be variable. The numerology may be variable to meet various technical requirements of the communication system. In a communication system applying CP (cyclic prefix)-based OFDM waveform technology, the numerology may include subcarrier spacing and CP length (or CP type). Table 1 may be a first embodiment of a method for configuring a numerology for a CP-OFDM-based communication system. At least some of the numerologies in Table 1 may be supported depending on the frequency band in which the communication system operates. In addition, the communication system may additionally support numerologies not listed in Table 1.

[0095]

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

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

[0098] A symbol may be configured as a downlink (DL) symbol, a flexible (FL) symbol, or an uplink (UL) symbol. A slot consisting solely of DL symbols may be referred to as a "DL slot," a slot consisting solely of FL symbols may be referred to as an "FL slot," and a slot consisting solely of UL symbols may be referred to as a "UL slot."

[0099] The slot format can be semi-statically configured by higher layer signaling (e.g., RRC signaling). Information indicating the semi-static slot format can be included in the system information, and the semi-static slot format can be configured cell-specifically. In addition, the semi-static slot format can be additionally configured for each terminal through terminal-specific higher layer signaling (e.g., RRC signaling). The flexible symbol of the cell-specifically configured slot format can be overridden to a downlink symbol or an uplink symbol by terminal-specific higher layer signaling. In addition, the slot format can be dynamically indicated by physical layer signaling (e.g., a slot format indicator (SFI) included in DCI). The semi-statically configured slot format can be overridden by a dynamically indicated slot format. For example, the semi-statically configured flexible symbol can be overridden to a downlink symbol or an uplink symbol by the SFI.

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

[0101] Figure 8 is a conceptual diagram illustrating embodiments of time-frequency resources in a communication system.

[0102] 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 may be defined as a "RE (resource element)". Resources consisting of one OFDM symbol in the time domain and K subcarriers in the frequency domain may be defined as a "REG (resource element group)". A REG may include K REs. A REG may be used as a basic unit for resource allocation in the frequency domain. K may be a natural number. For example, K may be 12. N may be a natural number. In the slot illustrated in FIG. 7, N may be 14. N OFDM symbols may be used as a basic unit for resource allocation in the time domain.

[0103] In the present disclosure, RB may mean CRB (common RB). Alternatively, RB may mean PRB or VRB (virtual RB). In a communication system, CRB may mean RB that constitutes a set of consecutive RBs (e.g., a common RB grid) based on a reference frequency (e.g., point A). Carriers and / or bandwidth portions may be arranged on the common RB grid. That is, the carrier and / or bandwidth portions may be composed of CRB(s). RBs or CRBs that constitute the bandwidth portions may be referred to as PRBs, and within the bandwidth portions, the CRB index may be appropriately converted to the PRB index.

[0104] Downlink data can be transmitted via the PDSCH. The base station can transmit PDSCH configuration information (e.g., scheduling information) to the terminal via the PDCCH. The terminal can obtain the PDSCH configuration information by receiving the PDCCH (e.g., downlink control information (DCI)). For example, the PDSCH configuration information can include the MCS (modulation coding scheme) used for transmitting and receiving the PDSCH, time resource information of the PDSCH, frequency resource information of the PDSCH, feedback resource information for the PDSCH, etc. The PDSCH can refer to a radio resource through which downlink data is transmitted and received. Alternatively, the PDSCH can refer to the downlink data itself. The PDCCH can refer to a radio resource through which downlink control information (e.g., DCI) is transmitted and received. Alternatively, the PDCCH can refer to the downlink control information itself.

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

[0106] 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. The PDCCH occasion may be a region where the PDCCH can exist. That is, the PDCCH occasion may be a region where DCI can be transmitted. The PDCCH occasion may be referred to as a PDCCH candidate. The 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., in PRB (physical resource block) units or CRB (common resource block) units).

[0107] The search space information may include a coreset identifier (ID) associated with the search space, a period of PDCCH monitoring, and / or an offset. Each of the PDCCH monitoring period and offset may be indicated on a slot-by-slot basis. In addition, the search space information may further include an index of the symbol at which the PDCCH monitoring operation begins.

[0108] A base station can configure a bandwidth part (BWP) for downlink communication. The BWP can be configured differently for each terminal. The base station can inform the terminal of the BWP configuration information using higher layer signaling. The higher layer signaling can mean "transmission operation of system information" and / or "transmission operation of RRC (radio resource control) message." The number of BWPs configured for one terminal can be one or more. The terminal can receive BWP configuration information from the base station and check the BWP(s) configured by the base station based on the BWP configuration information. When multiple BWPs are configured for downlink communication, the base station can activate one or more BWPs among the multiple BWPs. The base station can transmit the configuration information of the activated BWP(s) to the terminal using at least one of higher layer signaling, a medium access control (MAC) control element (CE), or DCI. The base station can 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 perform a downlink reception operation in the activated BWP(s).

[0109] Meanwhile, communication systems (e.g., NR communication systems, 5G communication systems, 6G communication systems) can support usage scenarios such as eMBB (enhanced Mobile Broadband), URLLC (Ultra Reliable Low Latency Communication), and mMTC (massive Machine Type Communication). Communication systems (e.g., communication networks) can support SBFD (subband full duplex) operation.

[0110] A communication system may support TDD (time division duplexing). In a communication system supporting TDD (hereinafter referred to as a "TDD communication system"), downlink (DL) symbol(s) and uplink (UL) symbol(s) may be configured in different time resources within a single carrier. DL and UL symbols may be associated with coverage and / or latency. In a TDD communication system, a base station can utilize resources more efficiently than in a frequency division duplexing (FDD) scheme by considering various use cases. Resource scheduling operations of the base station may be important in a TDD communication system. For improved TDD operation, SBFD operation (e.g., SBFD operation) may be supported. When SBFD operation is supported in a TDD communication system, DL communication (e.g., transmission and reception of DL signals) and UL communication (e.g., transmission and reception of UL signals) may be performed simultaneously within the same time resource. For example, within the same time resource, some subbands may be DL subbands, while other subbands may be UL subbands and / or FL subbands. In the present disclosure, a DL signal may be interpreted as a DL signal, a DL channel, or "a DL signal and a DL channel" depending on the context. In the present disclosure, a UL signal may be interpreted as a UL signal, an UL channel, or "a UL signal and a UL channel" depending on the context.

[0111] A symbol to which the SBFD operation is applied may be referred to as an SBFD symbol. A symbol to which the SBFD operation is not applied may be referred to as an N(non)-SBFD symbol. An N-SBFD symbol may be a DL symbol, an UL symbol, or an FL symbol. In an SBFD symbol, a terminal may perform DL communication and UL communication. In other words, in an SBFD symbol, a terminal may perform full duplex operation. In an N-SBFD symbol, a terminal may perform one of DL communication and UL communication. In other words, in an N-SBFD symbol, a terminal may perform half duplex operation. An SBFD symbol may be a symbol including a subband on which an SBFD operation is performed. A subband for SBFD may be referred to or interpreted as a UL subband. A UL subband may be present (e.g., configured) in a symbol in which an SSB (synchronization signal block) is transmitted.

[0112] Resources (e.g., time resources and / or frequency resources) for SBFD operation can be configured in a semi-static manner. In other words, the configuration for SBFD resources can be a semi-static configuration. "The SBFD resource configuration being a semi-static configuration" can mean "the SBFD resource is configured by semi-static signaling (e.g., system information, RRC message)." In the present disclosure, SBFD resources can mean time resources and / or frequency resources for SBFD operation. A UL subband for SBFD can be an SBFD resource. Alternatively, SBFD resources can be configured in a dynamic manner. "The SBFD resource configuration being a dynamic configuration" can mean "the SBFD resource is configured by dynamic signaling (e.g., MAC CE, DCI, SCI)."

[0113] SBFD resources (e.g., UL subbands, SBFD symbols) can be configured within DL resources and / or FL (flexible) resources configured by TDD-UL-DL configuration common information (e.g., TDD-UL-DL-configCommon). The transition point from an N-SBFD symbol to an SBFD symbol in the time domain can be limited to one. The transition point from an SBFD symbol to an N-SBFD symbol in the time domain can be limited to one. With respect to resource configuration of a subband for SBFD, it may be desirable for a terminal to recognize resource configuration information of a subband for SBFD in advance.

[0114] The TDD-UL-DL configuration common information can be used to configure a pattern (e.g., TDD-UL-DL-Pattern) for DL ​​resources and / or UL resources in the time domain of a TDD communication system. The pattern for DL ​​resources and / or UL resources can be referred to as a UL / DL pattern. The UL / DL pattern can be changed according to the environment of the communication system (e.g., TDD communication system). Up to two UL / DL patterns can be configured for a terminal. The TDD-UL-DL configuration common information can be a cell-specific parameter (e.g., cell-specific configuration information). The base station can change the configuration (e.g., transmission direction, type) for symbol(s) for each terminal based on a specific slot within a preset UL / DL pattern. A slot for which the symbol configuration (e.g., symbol direction, symbol type) can be changed can be a slot configured as an FL resource by the TDD-UL-DL configuration common information. The symbol direction (e.g., symbol transmission direction) and / or symbol type may be DL, UL, or FL. The RRC signaling used to change the configuration of an FL slot (e.g., FL resource) may be TDD-UL-DL configuration dedicated information (e.g., TDD-UL-DL-ConfigDedicated). Table 2 may be TDD-UL-DL configuration common information, and Tables 3 and 4 may be TDD-UL-DL configuration dedicated information.

[0115]

[0116]

[0117]

[0118] The UL / DL pattern configured by the TDD-UL-DL configuration common information can be repeated according to a specific period (e.g., dl-UL-TransmissionPeriodicity). In the time period to which the UL / DL pattern is applied, the front region can be configured as a DL resource. In the time period to which the UL / DL pattern is applied, the rear region can be configured as a UL resource. In the time period to which the UL / DL pattern is applied, resources that are not configured as DL resources or UL resources can be FL resources. The period of the UL / DL pattern can vary depending on the reference numerology. A guard time (e.g., a guard gap) may be required for switching (e.g., transition) from a DL resource (e.g., a DL symbol / slot) to a UL resource (e.g., a UL symbol / slot). Since the propagation delay of DL signals causes interference to UL resources, a guard time may be required for switching from DL resources to UL resources. A separate guard time may not be required for switching from UL resources to DL resources. Since UL signals are transmitted based on the timing advance command (TAC) indicated by the base station, a guard time may not be required for switching from UL resources to DL resources.

[0119] TDD-UL-DL configuration common information (e.g., TDD-UL-DL-ConfigCommon) may be referred to as "TDD common" or "TDD common information". TDD-UL-DL configuration dedicated information (e.g., TDD-UL-DL-ConfigDedicated) may be referred to as "TDD dedicated" or "TDD dedicated information". A UL subband may mean a subband for SBFD. DL symbol(s) and / or DL ​​slot(s) may be referred to as a DL region (or DL ​​resource). UL symbol(s) and / or UL slot(s) may be referred to as a UL region (or UL resource). FL symbol(s) and / or FL slot(s) may be referred to as an FL region (or FL resource). A terminal that supports (e.g., recognizes) the SBFD operation may be referred to as an SBFD terminal or SBFD UE. A terminal that does not support (e.g., is not aware of) SBFD operation may be referred to as an N(non)-SBFD terminal or N-SBFD UE. An N-SBFD terminal may be a legacy terminal (e.g., a legacy UE). In the present disclosure, a terminal may be interpreted as an SBFD terminal and / or an N-SBFD terminal depending on the context. Legacy configuration (e.g., legacy information, legacy configuration information) may be information for an N-SBFD terminal. SBFD configuration (e.g., SBFD information, SBFD configuration information) may be information for an SBFD terminal.

[0120] To support SBFD operation, a base station can configure a UL subband within a DL region (e.g., DL resources) and transmit configuration information (e.g., SBFD configuration information) of the UL subband to a terminal via signaling. The terminal can receive the configuration information of the UL subband from the base station and identify the UL subband based on the configuration information. After the UL subband is configured, the scheduling operation of the PDSCH and / or PUSCH can be performed considering the UL subband. By configuring the UL subband, some resources of the frequency band can be UL subbands (e.g., UL usable PRB(s)), and other some resources of the frequency band can be DL subbands (e.g., DL usable PRB(s)). In the present disclosure, the usable PRB(s) can mean UL usable PRB(s) and / or DL ​​usable PRB(s).

[0121] UL communication (e.g., UL transmission and / or UL reception) may be permitted in UL-available PRB(s). In other words, UL communication may not be permitted outside of the UL-available PRB(s). The UL-available PRB(s) may include UL subbands within a broadband work period (BWP). DL communication (e.g., DL transmission and / or DL ​​reception) may be permitted in DL-available PRB(s). In other words, DL communication may not be permitted outside of the DL-available PRB(s). The DL-available PRB(s) may include frequency domains (e.g., frequency resources) excluding UL subbands within a broadband work period (BWP). In other words, the DL-available PRB(s) may be PRB(s) that do not include UL subbands within a broadband work period (BWP). The DL-available PRB(s) may refer to valid frequency domains. Within an active UL BWP, a UL subband (e.g., UL subband frequency resources) may be referred to as UL usable PRB(s). The UL usable PRB(s) may refer to PRB(s) that include a UL subband within the BWP. The UL usable PRB(s) may refer to a valid frequency region. Within an active DL BWP, a DL subband (e.g., DL subband frequency resources) may be referred to as DL usable PRB(s). The following options may be considered to determine the UL / DL usable PRB(s). The UL / DL usable PRB(s) may refer to UL usable PRB(s) and / or DL ​​usable PRB(s).

[0122] - Option 1: UL usable PRB(s) may be determined as the overlap region between the active UL BWP and cell-specific UL subband(s) within the SBFD symbols. DL usable PRB(s) may be determined as the overlap region between the active DL BWP and cell-specific DL subband(s) within the SBFD symbols.

[0123] - Option 2: UL available PRB(s) can be explicitly set in the active UL BWP within the SBFD symbols. DL available PRB(s) can be explicitly set in the active DL BWP within the SBFD symbols. In other words, UL / DL available PRB(s) can be explicitly set (e.g., indicated) by the base station.

[0124] PDSCH transmission and / or PUSCH transmission may be performed in units of resource block groups (RBGs) or physical resource blocks (PRBs). DL RBGs may be RBGs used for PDSCH transmission. UL RBGs may be RBGs used for PUSCH transmission. An RBG may include one or more RBs (e.g., one or more PRBs). RBG indexing may vary depending on the BWP size and / or BWP type. Therefore, when a UL subband is configured, it may be necessary to redefine the allocation method of RBGs required for PDSCH transmission and / or PUSCH transmission.

[0125] The allocation method of frequency resources of a data channel can be classified into resource allocation type 0 and resource allocation type 1. In the present disclosure, the data channel may mean a PDSCH and / or a PUSCH. When resource allocation type 0 is used, frequency resources (e.g., RBGs) used for transmission of the data channel may be indicated by a bitmap. For example, a bit set to a first value (e.g., 0) in the bitmap may indicate that the RBG mapped to (e.g., corresponding to) the bit is not used for transmission of the data channel. A bit set to a second value (e.g., 1) in the bitmap may indicate that the RBG mapped to (e.g., corresponding to) the bit is used for transmission of the data channel. When resource allocation type 1 is used, frequency resources (e.g., PRBs) used for transmission of the data channel may be indicated by a resource indication value (RIV). The RIV may indicate a start RB and the number of RBs. The RB(s) (e.g., RBG(s)) indicated by the start RB) and the number of RBs can be used for transmission of a data channel. In the present disclosure, RB can be interpreted as a physical resource block (PRB) or a virtual resource block (VRB) depending on the context.

[0126] Either resource allocation type 0 or resource allocation type 1 can be used to indicate frequency resources for transmission of a data channel. The resource allocation type (e.g., 0 or 1) can be implicitly indicated by the DCI format. For example, the UE can infer the resource allocation type (e.g., 0 or 1) based on the DCI format. Alternatively, the base station can indicate the resource allocation type (e.g., 0 or 1) to the UE through an RRC configuration and / or DCI. For example, resourceAllocation included in the RRC message can be set to resourceAllocationType0 or resourceAllocationType1. The most significant bit (MSB) of the FDRA (frequency domain resource assignment) field included in the DCI (e.g., DCI format 0_x, DCI format 1_x) can indicate resource allocation type 0 or resource allocation type 1. x can be an integer greater than or equal to 0.

[0127] When DCI format 1_0, 4_0, or 4_1 including scheduling information (e.g., DL grant) for PDSCH is received, the UE can expect that resources for PDSCH are configured based on resource allocation type 1. Alternatively, the use of resource allocation type 0 and resource allocation type 1 can be dynamically switched. For example, the base station can set resourceAllocation to dynamicSwitch via RRC signaling. The base station can indicate to the UE the use of resource allocation type 0 or resource allocation type 1 via the MSB of the FDRA field included in the DCI (e.g., DCI format 0_x, DCI format 1_x). For example, an MBS set to a first value (e.g., 0) can indicate resource allocation type 0, and an MBS set to a second value (e.g., 1) can indicate resource allocation type 0. The terminal can check the resource allocation type based on RRC signaling and DCI.

[0128] In this disclosure, frequency resource allocation methods for data channel transmission according to resource allocation types considering UL subbands will be proposed. The frequency resource allocation method of PDSCH in this disclosure can be applied identically or similarly to frequency resource allocation of other channels (e.g., PUSCH). The frequency resource allocation method of PUSCH in this disclosure can be applied identically or similarly to frequency resource allocation of other channels (e.g., PDSCH). The frequency resource allocation method proposed in this disclosure can be applied to different scenarios. For example, in scenario #1 assuming resource allocation type 0, method #2-2 can be used to determine (e.g., calculate) VRB in scenario #2. In this disclosure, an SBFD symbol can mean the same symbol (e.g., a single symbol) in which bidirectional links (e.g., uplink and downlink) exist.

[0129] ● Scenario #1: Resource Allocation Type 0

[0130] When resource allocation type 0 is used, a communication node can configure consecutive RBs (e.g., consecutive VRBs) as one RBG, and can use one or more RBGs for transmitting and receiving a data channel. A communication node may mean a base station and / or a terminal. In other words, a communication node may be interpreted as a base station or a terminal depending on the context. The number of RBs that can be included in one RBG can be configured in a terminal by RRC signaling. For example, a base station can indicate a configuration index (e.g., configuration 1, configuration 2, or configuration 3) to a terminal in Table 5 below. The nominal RBG size (P) can be configured based on Table 5 below. For example, if the value according to configuration 1 is 2, one RBG can include two PRBs. If the value according to configuration 2 is 8, one RBG can include eight PRBs.

[0131]

[0132] When resource allocation type 0 is used, frequency resources for transmitting and receiving data channels (e.g., PDSCH and / or PUSCH) may be indicated by a bitmap. The size of the bitmap may be equal to the number of RBGs (e.g., valid RBGs) configured within a frequency band (e.g., UL BWP, active UL BWP, DL BWP, active DL BWP). One bit in the bitmap may be mapped to (e.g., corresponds to) one RBG. The base station may use the bitmap to indicate to the terminal whether each RBG is used for transmitting and receiving data channels. In Table 5, configuration 1, configuration 2, or configuration 3 may be a configuration index configured by RRC signaling. For example, in Table 5, setting 1 may be setting index 1 set by RRC signaling, setting 2 may be setting index 2 set by RRC signaling, and setting 3 may be setting index 3 set by RRC signaling.

[0133] Among the RBGs in a BWP, the sizes of RBGs excluding the start RBG and / or the last RBG may be the same. A BWP may mean a UL BWP, an active UL BWP, a DL BWP, or an active DL BWP depending on the context. The start RBG may be an RBG with the lowest frequency among the RBGs in the BWP. The last RBG may be an RBG with the highest frequency among the RBGs in the BWP. RBG indexing may be performed in ascending order based on the lowest frequency in the BWP. RBG indexing may be performed at each of the base station and the terminal. The MSB in the bitmap may be mapped to RBG #0, and the LSB in the bitmap may be mapped to RBG #(n-1). n may be the total number of RBGs in the BWP.

[0134] Figure 9 is a conceptual diagram illustrating a method of setting RBG in scenario #1 where resource allocation type 0 is used.

[0135] Referring to FIG. 9, a BWP may include 21 RBs. In other words, the BWP size may be 21. Setting 2 may be applied. In this case, a communication node (e.g., a base station and / or a terminal) may configure 6 RBGs within the BWP. Each of the RBGs within the BWP, excluding a start RBG (e.g., RBG #0) and an end RBG (e.g., RBG #5), may include 4 RBs. The start RBG (e.g., RBG #0) may include 3 RBs. The end RBG (e.g., RBG #5) may include 2 RBs. When a UL subband is configured within the BWP, the communication node may reconfigure the RBGs considering the UL subband. A method (e.g., a configuration rule) for configuring RBGs considering the UL subband may be as follows. The method proposed in Scenario #1 (e.g., Method #1, Method #2, Method #2-1, and / or Method #2-2) may be applied when an allocated RBG (e.g., an RBG set within a BWP) overlaps with a UL subband (e.g., a boundary of a UL subband). In the method proposed in Scenario #1 (e.g., Method #1, Method #2, Method #2-1, and / or Method #2-2), the number of PRBs for determining a transport block size (TBS) (e.g., calculating a TBS) may be based on the PRBs within the DL-available PRBs (e.g., DL-available PRBs for a PDSCH). In other words, the PRBs for determining the TBS may belong to the DL-available PRBs. In the method proposed in Scenario #1 (e.g., Method #1, Method #2, Method #2-1, and / or Method #2-2), the number of PRBs for TBS determination (e.g., TBS calculation) may be based on the PRBs within the UL available PRBs (e.g., UL available PRBs for PUSCH).In other words, PRBs for TBS determination may belong to UL-available PRBs.

[0136] ■ Method #1: The communication node can preferentially allocate RBGs based on existing rules, and can reset RBGs for the remaining RBs (e.g., DL available PRBs) excluding RBs that overlap with UL subbands within the BWP. Alternatively, the communication node can reset RBGs for RBs that include UL subbands within the BWP (e.g., UL available PRBs).

[0137] The communication node can configure the RBG based on the BWP size (e.g., the BWP size defined in Table 5), the configuration index (e.g., the configuration defined in Table 5), and / or the parameter(s) for RBG configuration without considering the UL subband within the BWP. The RBG can be configured based on an existing rule. The existing rule can be an existing RBG indexing rule (e.g., an existing RBG indexing method) and / or a VRB to PRB mapping rule (e.g., a VRB to PRB mapping method). Information for RBG configuration (e.g., the index, the configuration, the parameters) can be configured to the terminal by RRC signaling of the base station. Thereafter, the communication node can reconfigure the RBG based on valid RBs excluding frequency resources (e.g., RBGs and / or RBs) that overlap with the UL subband within the BWP. In other words, the RBG can be configured only with valid RBs. The valid RBs can be valid frequency domains or valid frequency resources. In DL communication, valid RBs may be DL-available PRBs (e.g., DL subbands). In UL communication, a communication node may reconfigure RBGs for valid RBs (e.g., UL-available PRBs) that include UL subbands within the BWP. A method for configuring RBGs based on Method #1 may be as follows.

[0138] Figure 10 is a conceptual diagram illustrating a method for setting RBG (e.g., DL RBG) based on method #1 in scenario #1 where resource allocation type 0 is used.

[0139] Referring to FIG. 10, a BWP may include 21 RBs. In other words, the BWP size may be 21. Configuration 2 may be applied. In step 1, a communication node may configure RBGs within a BWP based on existing rules without considering UL subbands. In this case, six RBGs may be configured within the BWP. Each of the RBGs within the BWP, excluding a start RBG (e.g., RBG #0) and an end RBG (e.g., RBG #5), may include four RBs. The start RBG (e.g., RBG #0) may include three RBs. The end RBG (e.g., RBG #5) may include two RBs.

[0140] If a UL subband is configured, in step 2, the communication node can reconfigure RBGs within the BWP by considering the UL subband. The communication node can determine (e.g., judge) an RB (e.g., an RBG) that overlaps with the UL subband within the BWL as an invalid RB (e.g., an invalid RBG). In other words, the communication node can determine (e.g., judge) an RB (e.g., an RBG) that does not overlap with the UL subband within the BWL as a valid RB (e.g., a valid RBG). The communication node can exclude the invalid RB (e.g., the invalid RBG) from the RBGs determined in step 1, and can re-perform RBG indexing for the remaining RBGs (e.g., valid RBGs) other than the excluded RBGs. In other words, the communication node can re-perform RBG indexing for the valid RBGs. A communication node may not assign indices (e.g., numbers) to invalid RBGs, and may assign indices (e.g., numbers) to valid RBGs. RBG indexing may be performed based on existing rules. For example, RBG indexing may be performed in ascending order, starting from the lowest RB within the BWP.

[0141] Since RB #22 of RBG #1 belongs to the UL subband, the communication node can determine RB #22 as an invalid RB. The communication node can configure RBG #1, which is composed of RB #19 to RB #21, excluding the invalid RB #22 among RB #19 to RB #22. Since RBG #2 and RBG #3 belong entirely to the UL subband, the communication node can determine RBG #2 and RBG #3 as invalid RBGs. The communication node can re-index RBGs for RBG #4 and RBG #5, which are located after the invalid RBGs in the frequency domain. The communication node can re-configure RBG #4 to RBG #2, and can re-configure RBG #5 to RBG #3. The number of PRBs for TBS determination (e.g., TBS calculation) may be based on the PRBs within the DL-available PRBs (e.g., DL-available PRBs for PDSCH). In other words, the PRBs for TBS determination may belong to the DL-available PRBs. The number of PRBs for TBS determination (e.g., TBS calculation) may be based on the PRBs within the UL-available PRBs (e.g., UL-available PRBs for PUSCH). In other words, the PRBs for TBS determination may belong to the UL-available PRBs. According to method #1, without configuring additional parameters, the communication node may reconfigure the RBGs considering the UL subband.

[0142] ■ Method #2: A communication node can identify one or more RB regions excluding the UL subband within the BWP, and can set an RBG in each of the one or more RB regions based on existing rules. An RB region can be a region composed of contiguous RBs. An RB region can be a valid DL resource. A valid DL resource can mean DL-available PRBs (e.g., DL subbands).

[0143] In the above-described method #1, the existing configuration can be used as is, but an additional step (e.g., step 2) for RBG reconfiguration may be required. In step 2, the communication node can determine valid RB(s) (e.g., valid RBG(s)) and perform RBG indexing for the valid RB(s) (e.g., valid RBG(s)). Unlike method #1, in method #2, the communication node can perform RBG configuration for one or more RB regions. In method #2, the existing rule can be used, and the existing rule can be applied to the RB region (e.g., DL subband) instead of the BWP.

[0144] Depending on the configuration of the UL subband, at least two RB regions (e.g., at least two DL subbands) can exist within a BWP. Considering at least two RB regions, one RBG can be configured to include a small number of RBs. In Table 5, the number of RBs per RBG configured for each BWP size can be 2, 4, 8, or 16 according to configuration 1. Considering at least two RB regions (e.g., at least two DL subbands) existing within a BWP, a new configuration indicating the number of RBs per RBG can be added. As shown in Table 6 below, a new configuration, Configuration 0, can be added. In Table 6, the number of RBs per RBG configured for each BWP size can be 1, 2, 4, or 8 according to configuration 0. The configuration based on Table 6 can be configured to the terminal by signaling from the base station.

[0145]

[0146] Some values ​​in Table 6 may not be used. Or, some values ​​in Table 6 may be set to different values. The number of DL subbands (e.g., RB regions) may vary depending on the location of the UL subband within the BWP. If a UL subband including a start RB or an end RB within the BWP is configured, one DL subband may exist within the BWP. If a UL subband configured within the BWP does not include the start RB or the end RB of the BWP, two DL subbands may exist within the BWP. Referring to the embodiment of FIG. 10, two DL subbands may exist within the BWP depending on the configuration of the UL subband.

[0147] Figure 11 is a conceptual diagram illustrating a method for setting RBG (e.g., DL RBG) based on method #2 in scenario #1 where resource allocation type 0 is used.

[0148] Referring to FIG. 11, a BWP may include 21 RBs, and UL subbands may be configured in RB #22 to RB #30 within the BWP. A communication node may determine that two DL subbands exist within the BWP by the UL subbands. Each of the two DL subbands may be referred to as sub-DL BWP #1 and sub-DL BWP #2. The communication node may perform RBG configuration for sub-DL BWP #1 based on existing rules. The communication node may perform RBG configuration for sub-DL BWP #2 based on existing rules. The same RRC configuration (e.g., configuration index) may be applied to the two DL subbands. In this case, an increase in signaling overhead may be prevented.

[0149] In the embodiment of FIG. 11, a BWP may include 21 RBs, and configuration 2 may be applied. Sub-DL BWP #1 and sub-DL BWP #2 may each include 6 RBs. The communication node may configure RBG #0, RBG #1, and RBG #2 by performing RBG configuration for sub-DL BWP #1. Each of RBG #0, RBG #1, and RBG #2 may include 2 RBs. The communication node may configure RBG #3, RBG #4, and RBG #5 by performing RBG configuration for sub-DL BWP #2. Each of RBG #3, RBG #4, and RBG #5 may include 2 RBs. The existing rule for RBG configuration may be set as shown in Mathematical Expression 1 below.

[0150]

[0151] Is PRBs of dogs (e.g., It can mean the total number of RBGs in BWP(i) having RBs. can mean the size of CFR (common frequency resource). can mean the starting PRB of the CFR. P can mean the size of all other RBGs. may mean the size of the first RBG. may mean the size of the last RBG.

[0152] If method #2 is used, the communicating node Instead, we can compute Equation 1 using the size of each DL subband (e.g., the number of RBs included in each DL subband). In other words, in Equation 1, the node Instead, the size of each DL subband can be applied.

[0153] ■ Method #2-1: The base station can transmit to the terminal through signaling the configuration index for each DL subband generated by the UL subband configured within the BWP. The terminal can receive the configuration index for each DL subband through signaling from the base station. The communication node (e.g., the base station and / or the terminal) can configure the RBGs for each DL subband based on the size and configuration index of each DL subband.

[0154] In the above-described method #2, the same configuration index can be applied to DL subbands. In method #2, DL resources can be evenly distributed across DL subbands. In method #2-1, the base station can configure (e.g., instruct) the terminal to configure the configuration index for each DL subband through signaling (e.g., RRC signaling). In other words, the base station can transmit to the terminal through signaling (e.g., RRC signaling) as many configuration indices as the number of DL subbands generated by the UL subband configured within the BWP (e.g., the maximum number). The terminal can receive as many configuration indices as the number of DL subbands (e.g., the maximum number) through signaling from the base station. The communication node (e.g., the base station and / or the terminal) can configure RBGs for each of the DL subbands based on the configuration index of each of the DL subbands.

[0155] Figure 12 is a conceptual diagram illustrating a method for setting RBG (e.g., DL RBG) based on method #2-1 in scenario #1 where resource allocation type 0 is used.

[0156] Referring to FIG. 12, a BWP may include 21 RBs, and UL subbands may be configured in RB #22 to RB #30 within the BWP. Two DL subbands may exist within the BWP by the UL subband. Each of the two DL subbands may be referred to as sub-DL BWP #1 and sub-DL BWP #2. The base station may transmit a configuration index for sub-DL BWP #1 (e.g., configuration 1 in Table 5 or Table 6) and a configuration index for sub-DL BWP #2 (e.g., configuration 2 in Table 5 or Table 6) to the terminal through signaling. The terminal may check the configuration index for sub-DL BWP #1 (e.g., configuration 1 in Table 5 or Table 6) and the configuration index for sub-DL BWP #2 (e.g., configuration 2 in Table 5 or Table 6) through signaling from the base station. A communication node (e.g., a base station and / or a terminal) may configure RBGs for sub-DL BWP #1 based on configuration 1. A communication node (e.g., a base station and / or a terminal) may configure RBGs for sub-DL BWP #2 based on configuration 2.

[0157] ■ Method #2-2: A communication node can set up consecutive RBs (e.g., consecutive VRBs) based on valid RBs (e.g., valid DL resources) excluding frequency resources corresponding to UL subbands within a BWP, and can set up RBGs for the consecutive RBs.

[0158] Figure 13 is a conceptual diagram illustrating a method for setting RBG (e.g., DL RBG) based on method #2-2 in scenario #1 where resource allocation type 0 is used.

[0159] Referring to FIG. 13, a BWP may include 21 RBs, and UL subbands may be configured in RBs #22 to #30 within the BWP. The base station may transmit a configuration index to the terminal via signaling (e.g., RRC signaling). The terminal may confirm a configuration index via signaling from the base station. In step 1, a communication node (e.g., a base station and / or a terminal) may assume contiguous RBs based on valid RBs (e.g., valid sub-DL BWPs) excluding RBs corresponding to UL subbands within the BWP. The contiguous RBs may be logically contiguous RBs. In other words, the contiguous RBs may not be physically contiguous. The contiguous RBs may be a set of VRBs.

[0160] In step 2, the communication node can determine the RBG size (e.g., 4 RBs) for the VRB set based on the configuration index (e.g., configuration 2), and can configure the RBGs for the VRB set based on the RBG size. The RBGs can be configured sequentially in the frequency domain. In step 2, RBG #0, RBG #1, and RBG #2 can be configured.

[0161] In step 3, the communication node can reset an RBG composed of physically non-contiguous RBs into RBGs composed of physically contiguous RBs, and perform RBG indexing on the reset RBGs again. RBG #1 can include physically non-contiguous RBs (e.g., RB #20, RB #21, RB #31, and RB #32). The communication node can reset RBG #1 to an RBG including RB #20 and RB #21 and an RBG including RB #31 and RB #32, and set the RBG including RB #20 and RB #21 as RBG #1, and set the RBG including RB #31 and RB #32 as RBG #2. In other words, RBG #1 set in step 2 can be split into RBG #1 and RBG #2. Indexing of RBGs after RBG #1 can be performed again. The communication node can reset the index of RBG #2 set in step 2 to RBG #3.

[0162] When method #2-2 is used, the communication node can configure RBGs by performing steps 1, 2, and 3. In this case, RBGs physically separated by UL subbands within the BWP may have different indices. Alternatively, when method #2-2 is used, the communication node can configure RBGs by performing steps 1 and 2. In other words, step 3 may be omitted. In this case, RBs physically separated by UL subbands within the BWP may be included in RBGs having the same index.

[0163] ● Scenario #2: Resource Allocation Type 1

[0164] When resource allocation type 1 is used, frequency resources can be indicated by RIV. The size of RIV (e.g., number of bits) can be smaller than the size of bitmap (e.g., number of bits) in resource allocation type 0. RIV can indicate a starting RB and the number of RBs (e.g., RB length). One value can be set to indicate the starting RB and the number of RBs. Resource allocation type 1 (e.g., RIV) can be used to indicate interleaved RBs or non-interleaved RBs. Resource allocation based on resource allocation type #1 can be performed through two steps. In the first step, a communication node (e.g., a base station and / or a terminal) can determine virtual RBs based on RIV. The virtual RBs can be determined based on a starting RB (e.g., a starting position) and the number of RBs (e.g., RB length). The actual mapping of VRBs to PRBs can be performed in the second step. The communication node can map VRBs to PRBs in an interleaved manner. This mapping operation can be an interleaved VRB-to-PRB mapping operation. The communication node can sequentially map VRBs to PRBs. This mapping operation can be a non-interleaved VRB-to-PRB mapping operation.

[0165] UL subbands can be configured, and frequency resources for transmission of data channels (e.g., PDSCH and / or PUSCH) can be indicated based on resource allocation type 1. In this case, the frequency resources of the data channels can be configured as follows. The frequency resources of the data channels can be configured by a single method or a combination of multiple methods. The configuration of VRBs and RIVs based on scheduling grants such as DCI format 1_2 or DCI format 1_3 can be performed based on a single method or a combination of multiple methods among the methods of Scenario #1. This is because in the case of non-interleaved VRBs, the calculated VRBs can be interpreted as being the same as the RBGs based on Scenario #1. The methods proposed in Scenario #2 (e.g., Method #3, Method #4, and / or Method #5) can be applied when an RB (e.g., an RB in a BWP) overlaps with a UL subband (e.g., a boundary of a UL subband). In the methods proposed in Scenario #2 (e.g., Method #3, Method #4, and / or Method #5), the number of PRBs for TBS determination (e.g., TBS calculation) may be based on PRBs within DL-available PRBs (e.g., DL-available PRBs for PDSCH). In other words, PRBs for TBS determination may belong to DL-available PRBs. In the methods proposed in Scenario #2 (e.g., Method #3, Method #4, and / or Method #5), the number of PRBs for TBS determination (e.g., TBS calculation) may be based on PRBs within UL-available PRBs (e.g., UL-available PRBs for PUSCH). In other words, PRBs for TBS determination may belong to UL-available PRBs.

[0166] ■ Method #3: A communication node (e.g., a base station and / or a terminal) can determine (e.g., calculate) and / or interpret the RIV based on the size of valid DL resources or the size of valid UL resources instead of the BWP size. Valid DL resources can be included in DL-available PRBs. Valid UL resources can be included in UL-available PRBs.

[0167] A valid DL resource may be a DL resource excluding a UL subband within a BWP. In other words, a valid DL resource may refer to a frequency region (e.g., frequency resource) within a BWP where actual DL transmission is possible, excluding a UL subband, UL resource, and / or guard band. A valid UL resource may be a UL resource including a UL subband within a BWP. In other words, a valid UL resource may refer to a frequency region (e.g., frequency resource) within a BWP where actual UL transmission is possible. For example, the RIV indicating the frequency resource of a data channel may be determined and / or interpreted based on the following mathematical formula.

[0168]

[0169] may mean the length (e.g., number) of consecutive RBs. can be 1 or more, may not exceed . can mean the size of the BWP. may mean the starting RB. If a UL subband is set within the BWP, can be interpreted as meaning the length (e.g., number) of physically non-contiguous RBs. In other words, can be interpreted to mean the length (e.g., number) of logically consecutive RBs. In the frequency domain excluding the UL subband and / or the area where DL communication is not possible within the BWP. can be expected to indicate the length of consecutive RBs (e.g., logically consecutive RBs).

[0170] Figure 14 is a conceptual diagram illustrating embodiments based on method #3 in scenario #2 where resource allocation type 1 is used.

[0171] Referring to FIG. 14, a BWP may include 21 RBs, and UL subbands may be configured within the BWP. The BWP may include RB #16 to RB #36. The UL subbands may be configured from RB #25 to RB #27. A communication node may determine RBs excluding the UL subbands within the BWP as valid RBs (e.g., DL subbands), and may determine RBs for transmitting a data channel among the valid RBs. The RBs for transmitting the data channel may be determined as RB #19 to RB #24, and RB #28 to RB #30. The communication node may generate an RIV indicating the RBs for transmitting the data channel (e.g., RB #19 to RB #24, and RB #28 to RB #30). The starting RB indicated by RIV may be RB #19, and the length (e.g., number) of RBs indicated by RIV may be 9.

[0172] A communication node receiving a RIV can check a start RB (e.g., RB #19) and the length of RBs (e.g., 9) based on the RIV. Since UL subbands are set to RB #25 to RB #27 in the BWP, the communication node can determine RBs (e.g., RB #19 to RB #24 and RB #28 to RB #30) indicated by the RIV by considering the UL subband. In method #3, the RIV can be determined and / or interpreted based on an existing rule (e.g., mathematical expression 2). In other words, one or more PRBs indicated by the RIV can be determined by reusing an existing PRB indexing rule and / or an existing VRB to PRB mapping rule. In other words, indexing for one or more PRBs can be performed based on an existing PRB indexing rule, and VRP to PRB mapping for one or more PRBs can be performed based on an existing VRB to PRB mapping rule. The existing PRB indexing rules and the existing VRB to PRB mapping rules may be applied when no UL subband is configured within the BWP. The existing PRB indexing rules and / or the existing VRB to PRB mapping rules may be reused (e.g., applied) in both resource allocation type 1 and resource allocation type 0.

[0173] ■ Method #4: When a UL subband is configured within a BWP, there may be two or more RB sets (e.g., DL subbands) composed of consecutive RBs by the UL subband. In this case, a communication node (e.g., a base station and / or a terminal) may determine (e.g., calculate) and / or interpret an RIV for each of the RB sets. For example, the communication node may determine and / or interpret a first RIV for a first RB set, and may determine and / or interpret a second RIV for a second RB set. The RB set may mean a DL subband. One or more PRBs indicated by each of the first RIV and the second RIV may be determined by reusing an existing PRB indexing rule and / or an existing VRB to PRB mapping rule. In other words, indexing of one or more PRBs may be performed based on existing PRB indexing rules, and VRP to PRB mapping of one or more PRBs may be performed based on existing VRB to PRB mapping rules. The existing PRB indexing rules and the existing VRB to PRB mapping rules may be rules applied when no UL subband is configured within a BWP. The existing PRB indexing rules and / or the existing VRB to PRB mapping rules may be reused (e.g., applied) in resource allocation type 0 as well as resource allocation type 1.

[0174] Figure 15 is a conceptual diagram illustrating embodiments based on method #4 in scenario #2 where resource allocation type 1 is used.

[0175] Referring to FIG. 15, a BWP may include 21 RBs, and a UL subband may be configured within the BWP. The BWP may include RB #16 to RB #36. The UL subband may be configured from RB #25 to RB #27. In this case, two RB sets consisting of consecutive RBs may exist within the BWP. A first RB set (e.g., a first DL subband) may include RB #16 to RB #24. A second RB set (e.g., a second DL subband) may include RB #28 to RB #31. A communication node may determine (e.g., generate) a first RIV indicating RB #19 to RB #24. A starting RB indicated by the first RIV may be RB #19. The number of RBs indicated by the first RIV may be 6. A communication node can determine (e.g., generate) a second RIV indicating RB #28 to RB #31. The starting RB indicated by the second RIV may be RB #27. The number of RBs indicated by the second RIV may be 4. The RBs indicated by the first RIV and the second RIV may be used for transmitting and receiving a data channel. A communication node that receives the first RIV can determine that RB #19 to RB #24 are used for transmitting and receiving a data channel based on the first RIV. A communication node that receives the second RIV can determine that RB #28 to RB #31 are used for transmitting and receiving a data channel based on the second RIV.

[0176] ■ Method #5: In interleaved VRB to PRB mapping, the base station can determine the RBG bundling size by considering the possibility of equal division in the frequency domain excluding the UL subband and / or guard band within the BWP, and can transmit information about the RBG bundling size to the terminal through signaling. The terminal can receive information about the RBG bundling size through signaling from the base station. The terminal can expect that the RBG bundling size is set so that RBG bundling is performed evenly in RBs used for PDSCH transmission (or PUSCH transmission) within the BWP. The RBG bundling size can satisfy the condition according to the following mathematical expression 3.

[0177]

[0178] A may be a basic unit of a precoding operation in a terminal (e.g., the number of PRGs (precoding resource groups)). B may be an RBG bundling size (e.g., the number of PRGs, the value of the PRGs). The RBG bundling size may be set to a value that can evenly divide the RBGs available for actual PDSCH transmission (or actual PUSCH transmission). As in the embodiments of FIGS. 14 and / or 15, multiple DL subbands may be generated by UL subbands set in a BWP. The communication node may calculate a value for equal division of each DL subband, and may set a divisor(s) of the minimum value among the values ​​for equal division as the RBG bundling size.

[0179] For example, in the embodiments of FIGS. 14 and / or 15, RB #19 to RB #24 may be assumed as sub-DL BWP #1, and RB #28 to RB #31 may be assumed as sub-DL BWP #2. When PRG is 2, the RBG bundling size for sub-DL BWP #1 may be set to 2 or 6. If there is a condition that the RBG bundling size must have a value that is an exponentiation of 2, 6 may be excluded from the RBG bundling size for sub-DL BWP #1. When PRG is 2, the RBG bundling size for sub-DL BWP #2 may be set to 2 or 4. When interleaving operation is required, the communication node may determine the RBG bundling size as a divisor of the minimum value (e.g., 2) among the RBG bundling sizes (e.g., 2, 6) for sub-DL BWP #1 and the RBG bundling sizes (e.g., 2, 4) for sub-DL BWP #2. Considering that the PRG is 2, the remaining values ​​excluding 2 cannot be set as the RBG bundling size. The RBG bundling size may be greater than or equal to the PRG. The base station may set the value (e.g., the number) of the PRG to the terminal through signaling. The terminal may check the value (e.g., the number) of the PRG through signaling from the base station.

[0180] An RIV may be configured for each of the DL subbands, and PRB mapping, RBG bundling, and / or interleaving may be performed on each of the DL subbands. In this case, the RBG bundling size may be configured independently. The base station may indicate (e.g., configure) the PRB (e.g., PRB mapping) and / or value(s) considering equal division to the terminal through signaling. The terminal may confirm the PRB (e.g., PRB mapping) and / or value(s) considering equal division through signaling from the base station.

[0181] Figure 16 is a flowchart illustrating a method of transmitting and receiving a data channel.

[0182] Referring to FIG. 16, a base station may generate BWP configuration information. The BWP configuration information may include DL BWP configuration information and / or UL BWP configuration information. The base station may transmit the BWP configuration information to a terminal via signaling (S1601). The terminal may receive the BWP configuration information via signaling from the base station (S1601). The base station may generate SBFD configuration information (e.g., UL subband configuration information). The base station may transmit the SBFD configuration information to the terminal via signaling (S1602). The terminal may receive the SBFD configuration information via signaling from the base station (S1602). A communication node (e.g., a base station and / or a terminal) may identify a UL subband configured within a BWP indicated by the BWP configuration information. The UL subband may be indicated by the SBFD configuration information transmitted and received in S1602. The UL subband within the BWP may be configured as in the embodiments of FIGS. 10 to 15. A communication node can determine DL available PRB(s) and / or UL available PRB(s) based on BWP configuration information and / or SBFD configuration information. The DL available PRB(s) can be determined based on BWP configuration information, SBFD configuration information, and / or DL ​​DCI (e.g., FDRA included in DL DCI). The DL available PRB(s) can include frequency resources excluding UL subbands within the BWP. The DL DCI can be DCI for scheduling DL communications. The UL available PRB(s) can be determined based on BWP configuration information, SBFD configuration information, and / or UL DCI (e.g., FDRA included in UL DCI). The UL available PRB(s) can be frequency resources including UL subbands within the BWP. The UL DCI can be DCI for scheduling UL communications.

[0183] ■ DL communication (resource allocation type 0)

[0184] A base station can generate DCI for DL ​​communication. The DCI for DL ​​communication can include scheduling information of a PDSCH. The base station can determine an FDRA (e.g., an FDRA field) based on Method #1, Method #2-1, or Method #2-2. The FDRA can include a bitmap indicating whether to allocate each RBG composed of PRBs belonging to DL-available PRBs. The RBGs indicated by the bitmap can belong to DL-available PRBs. The base station can allocate the PRBs belonging to DL-available PRBs as frequency resources for transmitting and receiving a PDSCH. The base station can transmit a DCI including an FDRA to a terminal (S1603). The terminal can receive the DCI from the base station and check the information included in the DCI (S1603). The terminal can check the frequency resources for transmitting and receiving a PDSCH based on the FDRA (e.g., a bitmap) included in the DCI. The terminal can interpret the FDRA (e.g., bitmap) based on Method #1, Method #2-1, or Method #2-2. The terminal can expect that PRBs belonging to DL-available PRBs are allocated as frequency resources for transmitting and receiving PDSCH. The terminal can regard PRBs within the DL-available PRBs as valid PRBs for PDSCH reception. In other words, the terminal may not expect that PRBs that do not belong to the DL-available PRBs (e.g., RBG(s) existing outside the DL-available PRBs) are allocated as frequency resources for transmitting and receiving PDSCH. At least one PRB within an RBG existing outside the DL-available PRBs may not overlap with the DL-available PRBs. The base station and the terminal can perform DL communication based on the DCI (S1604).In other words, the base station and the terminal can perform DL communication using one or more PRBs (e.g., valid PRB(s)) among the DL-available PRBs.

[0185] ■ DL communication (resource allocation type 1)

[0186] A base station can generate DCI for DL ​​communication. The DCI for DL ​​communication can include scheduling information of a PDSCH. The base station can determine a FDRA (e.g., an FDRA field) based on method #3, method #4, or method #5. The FDRA can include a RIV indicating PRBs belonging to DL-available PRBs. The PRBs indicated by the RIV can belong to DL-available PRBs. The PRG for the RIV can be set to one of 2 or 4. The base station can allocate PRBs belonging to DL-available PRBs as frequency resources for transmitting and receiving a PDSCH. The base station can transmit a DCI including an FDRA to a terminal (S1603). The terminal can receive the DCI from the base station and check the information included in the DCI (S1603). The terminal can check frequency resources for transmitting and receiving PDSCH based on FDRA (e.g., RIV) included in DCI. The terminal can interpret FDRA (e.g., RIV) based on method #3, method #4, or method #5. The terminal can expect that PRBs belonging to DL-available PRBs are allocated as frequency resources for transmitting and receiving PDSCH. The terminal can regard PRBs within DL-available PRBs as valid PRBs for PDSCH reception. In other words, the terminal may not expect that PRBs that do not belong to DL-available PRBs (e.g., RBG(s) existing outside DL-available PRBs) are allocated as frequency resources for transmitting and receiving PDSCH. At least one PRB within an RBG existing outside DL-available PRBs may not overlap with the DL-available PRBs. The base station and the terminal can perform DL communication based on the DCI (S1604).In other words, the base station and the terminal can perform DL communication using one or more PRBs (e.g., valid PRB(s)) among the DL-available PRBs.

[0187] ■ UL Communication (Resource Allocation Type 0)

[0188] A base station can generate DCI for UL communication. The DCI for UL communication can include scheduling information of a PUSCH. The base station can determine an FDRA (e.g., an FDRA field) based on Method #1, Method #2-1, or Method #2-2. The FDRA can include a bitmap indicating whether to allocate each RBG composed of PRBs belonging to UL-available PRBs. The RBGs indicated by the bitmap can belong to UL-available PRBs. The base station can allocate the PRBs belonging to the UL-available PRBs as frequency resources for transmitting and receiving a PDSCH. The base station can transmit a DCI including an FDRA to a terminal (S1603). The terminal can receive the DCI from the base station and check the information included in the DCI (S1603). The terminal can check the frequency resources for transmitting and receiving a PUSCH based on the FDRA (e.g., a bitmap) included in the DCI. The terminal can interpret the FDRA (e.g., bitmap) based on Method #1, Method #2-1, or Method #2-2. The terminal can expect that PRBs belonging to UL-available PRBs are allocated as frequency resources for transmitting and receiving PUSCH. The terminal can regard PRBs within the UL-available PRBs as valid PRBs for PUSCH transmission. In other words, the terminal may not expect that PRBs that do not belong to the UL-available PRBs (e.g., RBG(s) existing outside the UL-available PRBs) are allocated as frequency resources for transmitting and receiving PUSCH. At least one PRB within an RBG existing outside the UL-available PRBs may not overlap with the UL-available PRBs. The base station and the terminal can perform UL communication based on the DCI (S1604).In other words, the base station and the terminal can perform UL communication using one or more PRBs (e.g., valid PRB(s)) among the UL available PRBs.

[0189] ■ UL Communication (Resource Allocation Type 1)

[0190] A base station can generate DCI for UL communication. The DCI for UL communication can include scheduling information of a PUSCH. The base station can determine a FDRA (e.g., an FDRA field) based on method #3, method #4, or method #5. The FDRA can include a RIV indicating PRBs belonging to UL-available PRBs. The PRBs indicated by the RIV can belong to the UL-available PRBs. The PRG for the RIV can be set to one of 2 or 4. The base station can allocate PRBs belonging to the UL-available PRBs as frequency resources for transmitting and receiving a PUSCH. The base station can transmit a DCI including an FDRA to a terminal (S1603). The terminal can receive the DCI from the base station and check the information included in the DCI (S1603). The terminal can check frequency resources for transmitting and receiving PUSCH based on FDRA (e.g., RIV) included in DCI. The terminal can interpret FDRA (e.g., RIV) based on method #3, method #4, or method #5. The terminal can expect that PRBs belonging to UL-available PRBs are allocated as frequency resources for transmitting and receiving PUSCH. The terminal can regard PRBs within the UL-available PRBs as valid PRBs for PUSCH transmission. In other words, the terminal may not expect that PRBs that do not belong to the UL-available PRBs (e.g., RBG(s) existing outside the UL-available PRBs) are allocated as frequency resources for transmitting and receiving PUSCH. At least one PRB within an RBG existing outside the UL-available PRBs may not overlap with the UL-available PRBs. The base station and the terminal can perform UL communication based on the DCI (S1604).In other words, the base station and the terminal can perform UL communication using one or more PRBs (e.g., valid PRB(s)) among the UL available PRBs.

[0191] In the present disclosure, resources used for UL subbands may be UL available PRB(s), and resources used for DL ​​subbands may be DL available PRB(s). An area (e.g., the entire area) available for DL ​​communication of a terminal (e.g., DL communication directly performed by the terminal) may be interpreted as a DL subband. An area (e.g., the entire area) available for UL communication of a terminal (e.g., UL communication directly performed by the terminal) may be interpreted as a UL subband. The RBG size may be set based on the size of the DL BWP and / or the UL BWP. Alternatively, the RBG size may be set based on the size of the UL available PRB(s) and / or the DL available PRB(s).

[0192] ● Instruction method for SBFD subband (e.g. UL subband)

[0193] ■ Time domain

[0194] ◆ Method #6: The method of setting up time resources of the SBFD subband (e.g., the indication method) may be the same as the method of setting up the TDD-UL-DL pattern (e.g., the indication method).

[0195] When a TDD-UL-DL pattern is configured for a terminal, the time period of the SBFD subband may be the same as the period of the TDD-UL-DL pattern. The time period may mean a time segment, and the period may mean an segment. The period of the TDD-UL-DL pattern may be indicated by dl-UL-TransmissionPeriodicity included in TDD-UL-DL-ConfigCommon (e.g., TDD-UL-DL-ConfigCommon). In the case where the configuration frequency of the SBFD subband is low (e.g., a different configuration frequency according to the request of the SBFD subband), the time period of the SBFD subband may be set to N times the period of the TDD-UL-DL pattern. In other words, the time period of the SBFD subband may be set to N times the period indicated by dl-UL-TransmissionPeriodicity. N may be an integer.

[0196] The base station can transmit the value of N to the terminal through signaling (e.g., system information, RRC message). The terminal can receive the value of N through signaling from the base station. The value of N (e.g., the value of N set by the base station) can be dynamically changed. The base station can transmit the changed value of N (e.g., an indication to change the value of N) to the terminal through signaling (e.g., MAC CE, DCI). The terminal can receive the changed value of N through signaling from the base station.

[0197] ◆ Method #7: Two TDD-UL-DL patterns can be configured in the terminal, and the time resource of the SBFD subband can be configured by considering the two TDD-UL-DL patterns.

[0198] Two TDD-UL-DL patterns can be configured in a terminal, and the two TDD-UL-DL patterns can be consecutive in the time domain, and an SBFD subband can exist within a section corresponding to a sum length of the two TDD-UL-DL patterns. A time period of the SBFD subband can be equal to the sum of the period of TDD-UL-DL pattern 1 and the period of TDD-UL-DL pattern 2. Alternatively, the time period of the SBFD subband can be set to N times the sum of the period of TDD-UL-DL pattern 1 and the period of TDD-UL-DL pattern 2. N can be an integer.

[0199] The base station can transmit the value of N to the terminal through signaling (e.g., system information, RRC message). The terminal can receive the value of N through signaling from the base station. The value of N (e.g., the value of N set by the base station) can be dynamically changed. The base station can transmit the changed value of N (e.g., an indication to change the value of N) to the terminal through signaling (e.g., MAC CE, DCI). The terminal can receive the changed value of N through signaling from the base station.

[0200] Within the period of the TDD-UL-DL pattern (or the period of TDD-UL-DL pattern 1 + the period of TDD-UL-DL pattern 2), the time resource (e.g., SBFD symbol) of the SBFD subband can be configured based on at least one of the following parameters. The base station can transmit the following parameter(s) to the terminal through signaling. The terminal can check the following parameter(s) through the signaling of the base station, and check the time resource of the SBFD subband based on the following parameter(s).

[0201] - Index of the starting slot

[0202] - Index of the starting symbol within the starting slot

[0203] - Index of the end slot

[0204] - Index of the termination symbol within the termination slot

[0205] - Length of time resource of SBFD subband

[0206] - Location of the N-SBFD symbol

[0207] A start slot may refer to a first slot among one or more slots in which an SBFD subband (e.g., an SBFD symbol) is configured. An end slot may refer to a last slot among one or more slots in which an SBFD subband (e.g., an SBFD symbol) is configured. A start symbol may refer to a first SBFD symbol among the SBFD symbols. An end symbol may refer to a last SBFD symbol among the SBFD symbols. A time resource of an SBFD subband may be configured in units of SBFD symbols. A length of a time resource of an SBFD subband may refer to the number of SBFD symbols.

[0208] For example, the base station can signal the index of the start symbol (e.g., the start SBFD symbol) and the length of the time resource of the SBFD subband to the terminal. The terminal can determine the time resource of the SBFD subband within the period of the TDD-UL-DL pattern (or the period of TDD-UL-DL pattern 1 + the period of TDD-UL-DL pattern 2) based on the information indicated by the signaling of the base station. For another example, the base station can signal the index of the start symbol (e.g., the start SBFD symbol) and the index of the end symbol (e.g., the end SBFD symbol) to the terminal. The terminal can determine the time resource of the SBFD subband within the period of the TDD-UL-DL pattern (or the period of TDD-UL-DL pattern 1 + the period of TDD-UL-DL pattern 2) based on the information indicated by the signaling of the base station. For another example, the base station can signal the location of the N-SBFD symbol to the terminal. The terminal can determine a time resource other than the N-SBFD symbol indicated by the signaling of the base station as a time resource of the SBFD subband.

[0209] ◆ Method #8: A guard period may be established before and / or after the SBFD symbol in the time domain. The SBFD symbol may be established based on the method(s) described above. The guard period may consist of n symbols, where n may be a natural number. The base station and / or the terminal may expect not to perform DL communication and / or UL communication during the guard period.

[0210] A guard interval may be set to accommodate the processing delay required for physical RF (radio frequency) switching at the terminal and / or the processing delay required for data processing. Considering interference caused by propagation delay, certain symbols before and / or after the SBFD symbol in the time domain may be set as resources not used for communication (e.g., a guard interval, n symbols). Even if the resources within the guard interval are allocated for DL ​​communication by the base station's scheduling, the terminal can expect not to perform DL communication within the guard interval. Even if the resources within the guard interval are allocated for UL communication by the base station's scheduling, the terminal can expect not to perform UL communication within the guard interval.

[0211] ■ Frequency domain

[0212] ◆ Method #9: The frequency resources of the SBFD subband (e.g., the UL subband) can be configured by cell-specific signaling. For efficient resource utilization, the SBFD subband can be configured by UE-specific signaling. In this case, the SBFD subband can be configured independently for each UE. For example, the SBFD subband of a first UE can be configured differently from the SBFD subband of a second UE.

[0213] In the frequency domain, a guard band can be configured. The guard band can be configured on an RB basis or a subcarrier basis. The guard band size can be set to a fixed value. For example, the guard band size can be set to a fixed value through cell-specific signaling (e.g., cell-specific parameters). Alternatively, the guard band size can have a fixed value specified in the technical specifications.

[0214] The guard band can be set by UE-specific signaling (e.g., UE-specific parameters). The size of the guard band can be a variable value. When the guard band is set by cell-specific signaling and / or when the guard band is set by UE-specific signaling, the base station can use dynamic signaling (e.g., MAC CE, DCI) to indicate to the terminal whether the guard band is used, whether the guard band is set, and / or whether the guard band is turned on / off. The terminal can determine whether the guard band is used, whether the guard band is set, and / or whether the guard band is turned on / off based on the signaling of the base station.

[0215] ■ Transmitting and / or receiving operations

[0216] ◆ Method #10: The terminal may expect to perform DL communication and / or UL communication according to the DL symbol, UL symbol, DL slot, and / or UL slot based on the TDD-UL-DL pattern. Resources based on the TDD-UL-DL pattern may be changed to SBFD symbols by configuring the SBFD subband. In this case, the terminal may expect to perform UL communication in the resource(s) changed to SBFD symbols by configuring the SBFD subband among the resources based on the TDD-UL-DL pattern.

[0217] Alternatively, among the resources based on the TDD-UL-DL pattern, in the resource(s) changed to the SBFD symbol by the configuration of the SBFD subband, the UE may expect to perform DL communication and / or UL communication based on the scheduling of the base station. The UE may expect to perform DL communication and / or UL communication based on the type of communication scheduled by the DCI (e.g., DL communication or UL communication) and the type of subband within the SBFD symbol (e.g., DL subband or UL subband). For example, if the DCI schedules DL communication, the UE may expect to perform DL communication in the DL subband within the SBFD symbol. If the DCI schedules UL communication, the UE may expect to perform UL communication in the UL subband within the SBFD symbol.

[0218] A base station can set up repetitive transmissions for a terminal. Repetitive transmissions can be performed in SBFD symbols and N-SBFD symbols. For example, a first transmission can be set up in an SBFD symbol, and repetitive transmissions for the first transmission can be set up in an N-SBFD symbol. For another example, a first transmission can be set up in an N-SBFD symbol, and repetitive transmissions for the first transmission can be set up in an SBFD symbol. In the above-described situation, the terminal may not perform repetitive transmissions in the SBFD symbol and the N-SBFD symbol. In other words, neither the SBFD symbol nor the N-SBFD symbol may be used for repetitive transmissions. Alternatively, in the above-described situation, it may be allowed for a repetitive transmission operation to be completed based on a previously performed DL communication or UL communication.

[0219] Figure 17 is a flowchart illustrating a method for setting SBFD resources.

[0220] Referring to FIG. 17, a base station may determine one or more TDD-UL-DL patterns and generate configuration information of one or more TDD-UL-DL patterns (S1701). The configuration information of one or more TDD-UL-DL patterns may be included in TDD-UL-DL configuration common information (e.g., TDD-UL-DL-ConfigCommon information element). The one or more TDD-UL-DL patterns may include at least one of TDD-UL-DL pattern 1 or TDD-UL-DL pattern 2. The TDD-UL-DL configuration common information may include configuration information of one TDD-UL-DL pattern (e.g., TDD-UL-DL pattern 1). In other words, the base station may configure one TDD-UL-DL pattern to a terminal. When a single TDD-UL-DL pattern is configured for a terminal (e.g., based on a single TDD-UL-DL pattern being indicated to the terminal), the time period of the SBFD subband may be determined to be the same as the period of the single TDD-UL-DL pattern. In other words, the base station may determine that the time period of the SBFD subband is the same as the period of the single TDD-UL-DL pattern. A time period may be interpreted as a time interval, and a period may be interpreted as an interval.

[0221] Alternatively, the TDD-UL-DL configuration common information may include configuration information for each of two TDD-UL-DL patterns (e.g., TDD-UL-DL pattern 1 and TDD-UL-DL pattern 2). In other words, the base station may configure two TDD-UL-DL patterns to the terminal. When two TDD-UL-DL patterns are configured to the terminal (e.g., based on two TDD-UL-DL patterns being indicated to the terminal), the time period of the SBFD subband may be determined to be equal to the sum of the periods of the two TDD-UL-DL patterns (e.g., the period of TDD-UL-DL pattern 1 + the period of TDD-UL-DL pattern 2). In other words, the base station may determine that the time period of the SBFD subband is equal to the sum of the periods of the two TDD-UL-DL patterns. The configuration information of each TDD-UL-DL pattern may include one or more pieces of information defined in Table 7 below.

[0222]

[0223] The DL-UL-Transmission Period (e.g., dl-UL-TransmissionPeriodicity) can indicate the period of a TDD-UL-DL pattern (e.g., a DL-UL pattern). The period can be interpreted as an interval (e.g., a time interval). The DL-UL-Transmission Period can be set to 0.5ms (millisecond), 0.625ms, 1ms, 2ms, 2.5ms, 5ms, or 10ms. The number of DL slots (e.g., noofDownlinkSlots) can indicate the number of consecutive full DL slots at the beginning of a TDD-UL-DL pattern (e.g., a DL-UL pattern). Full DL slots can mean DL slots that consist of only DL symbols. The number of DL symbols (e.g., nrofDownlinkSymbols) may indicate the number of consecutive DL symbols at the start of the slot following the last full DL slot. The number of UL slots (e.g., nrofUplinkSlots) may indicate the number of consecutive full UL slots at the end of a TDD-UL-DL pattern (e.g., a DL-UL pattern). Full UL slots may mean UL slots consisting of only UL symbols. The number of UL symbols (e.g., nrofUplinkSymbols) may indicate the number of consecutive UL symbols at the end of a slot prior to the first full UL slot.

[0224] The base station can determine SBFD symbols within a period of a TDD-UL-DL pattern and generate configuration information of the SBFD symbols (S1702). The positions of the SBFD symbols within the period of the TDD-UL-DL pattern can be indicated (e.g., determined) by the configuration information of the SBFD symbols. The base station can confirm the positions of the SBFD symbols within the period of the TDD-UL-DL pattern based on the configuration information of the SBFD symbols. One or more SBFD symbols can be configured within the period of the TDD-UL-DL pattern. When one TDD-UL-DL pattern is configured, the period of the TDD-UL-DL pattern in which one or more SBFD symbols are configured can be a period of one TDD-UL-DL pattern (e.g., TDD-UL-DL pattern 1). When two TDD-UL-DL patterns are set, the period of the TDD-UL-DL patterns for which one or more SBFD symbols are set may be the sum of the periods of the two TDD-UL-DL patterns (e.g., TDD-UL-DL pattern 1 + TDD-UL-DL pattern 2). The setting information of the SBFD symbols may include one or more pieces of information defined in Table 8 below.

[0225]

[0226] A starting slot may refer to the first slot in which an SBFD symbol is set among the slots in a cycle of a TDD-UL-DL pattern. Within a starting slot, a starting symbol may refer to the first SBFD symbol in the first slot in which an SBFD symbol is set. An ending slot may refer to the last slot in which an SBFD symbol is set among the slots in a cycle of a TDD-UL-DL pattern. Within an ending slot, an ending symbol may refer to the last SBFD symbol in the last slot in which an SBFD symbol is set.

[0227] The base station can transmit configuration information of one or more TDD-UL-DL patterns and configuration information of SBFD symbols to the terminal through signaling (e.g., system information, RRC message, MAC CE, and / or DCI) (S1703). The terminal can receive configuration information of one or more TDD-UL-DL patterns and configuration information of SBFD symbols through signaling of the base station (S1703). The configuration information of one or more TDD-UL-DL patterns and configuration information of SBFD symbols can be included in the same message. For example, the TDD-UL-DL configuration common information can include configuration information of one or more TDD-UL-DL patterns and configuration information of SBFD symbols, and the base station can transmit system information (e.g., SIB1) including the TDD-UL-DL configuration common information to the terminal. Alternatively, the configuration information of one or more TDD-UL-DL patterns and the configuration information of SBFD symbols can be included in different messages. For example, a base station may transmit a first message including configuration information of one or more TDD-UL-DL patterns to a terminal, and a second message including configuration information of SBFD symbols to the terminal. The first message may be system information, and the second message may be an RRC message, MAC CE, or DCI.

[0228] The terminal can identify one or more TDD-UL-DL patterns based on configuration information of one or more TDD-UL-DL patterns, and can determine the time period of the SBFD subband based on the period(s) of the one or more TDD-UL-DL patterns (S1704). Communication between the terminal and the base station can be performed within the time period of the SBFD subband. If one TDD-UL-DL pattern is configured for the terminal (e.g., based on one TDD-UL-DL pattern being indicated to the terminal), the time period of the SBFD subband can be determined to be the same as the period of the one TDD-UL-DL pattern. In other words, the terminal can determine that the time period of the SBFD subband is the same as the period of the one TDD-UL-DL pattern. Alternatively, if two TDD-UL-DL patterns are configured for the terminal (e.g., based on two TDD-UL-DL patterns being indicated to the terminal), the time period of the SBFD subband may be determined to be equal to the sum of the periods of the two TDD-UL-DL patterns (e.g., the period of TDD-UL-DL pattern 1 + the period of TDD-UL-DL pattern 2). In other words, the terminal may determine that the time period of the SBFD subband is equal to the sum of the periods of the two TDD-UL-DL patterns.

[0229] The terminal can determine (e.g., confirm) the positions of SBFD symbols within the period of the TDD-UL-DL pattern based on the configuration information of the SBFD symbols (S1705). For example, the terminal can confirm the positions of SBFD symbols within the period of the TDD-UL-DL pattern based on the index of the starting slot, the index of the starting symbol within the starting slot, the index of the ending slot, and / or the index of the ending symbol within the ending slot. Communication between the terminal and the base station can be performed using SBFD symbols. One or more SBFD symbols can be configured within the period of the TDD-UL-DL pattern. When one TDD-UL-DL pattern is configured, the period of the TDD-UL-DL pattern in which one or more SBFD symbols are configured can be the period of one TDD-UL-DL pattern (e.g., TDD-UL-DL pattern 1). When two TDD-UL-DL patterns are set, the period of the TDD-UL-DL patterns for which one or more SBFD symbols are set may be the sum of the periods of the two TDD-UL-DL patterns (e.g., TDD-UL-DL pattern 1 + TDD-UL-DL pattern 2).

[0230] A base station and a terminal can perform communication (e.g., DL communication and / or UL communication) using one or more SBFD symbols determined based on configuration information of SBFD symbols within a time interval of an SBFD subband determined based on configuration information of one or more TDD-UL-DL patterns.

[0231] Although the embodiments in this disclosure have been described with a focus on PDSCH (e.g., resource allocation of PDSCH), the embodiments can be applied to other downlink channels (e.g., resource allocation of other downlink channels) and / or uplink channels (e.g., resource allocation of uplink channels). The embodiments proposed in this disclosure can be commonly applied to downlink channels and / or uplink channels. In this disclosure, a UL subband may mean a UL subband for SBFD operation. In this disclosure, a terminal may transmit information indicating whether to support the function(s) proposed in this disclosure to a base station. The information indicating whether to support the function(s) may be included in a UE capability report. The base station may receive the UE capability report from the terminal, and perform signaling and / or operations based on information included in the UE capability information (e.g., information indicating whether to support the function(s).

[0232] Configurations for UL subbands (e.g., SBFD configurations) can be transmitted via signaling (e.g., RRC signaling). The SBFD configurations can be transmitted after transmission of the TDD common configurations. The methods proposed in this disclosure can be applied to licensed bands as well as unlicensed bands. The methods proposed in this disclosure can be applied to sidelink and / or supplementary uplink (SUL). For example, the methods proposed in this disclosure can be applied for operation in sidelink and / or SUL. Each of the proposals in this disclosure can be applied independently, or a combination of the proposals in this disclosure can be applied. Some proposals in this disclosure can be applied to other proposals.

[0233] The operations of the method according to the present disclosure can be implemented as a computer-readable program or code on a computer-readable recording medium. A computer-readable recording medium includes any type of recording device that stores information readable by a computer system. Furthermore, a computer-readable recording medium can be distributed across network-connected computer systems, allowing the computer-readable program or code to be stored and executed in a distributed manner.

[0234] Additionally, the computer-readable recording medium may include hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, flash memory, etc. The program instructions may include not only machine language codes produced by a compiler, but also high-level language codes that can be executed by a computer using an interpreter, etc.

[0235] While some aspects of the present disclosure have been described in the context of a device, they may also represent a description of 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 as 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 or more of the most significant method steps may be performed by such a device.

[0236] 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 the present disclosure. The field-programmable gate array may operate in conjunction with a microprocessor to perform one of the methods described in the present disclosure. In general, the methods are preferably performed by some hardware device.

[0237] Although the present disclosure has been described with reference to preferred embodiments thereof, it will be understood by those skilled in the art that various modifications and changes may be made to the present disclosure without departing from the spirit and scope of the present disclosure as set forth in the claims below.

Claims

1. As a method of UE (user equipment), A step of receiving first configuration information of one or more TDD (time division duplexing)-UL (uplink)-DL (downlink) patterns from a base station; A step of determining a time period of a subband full duplex (SBFD) subband based on a period of one or more TDD-UL-DL patterns indicated by the first setting information; and Comprising a step of performing communication with the base station within the time period of the SBFD subband, UE's method.

2. In claim 1, Based on the fact that one TDD-UL-DL pattern is indicated to the UE by the first configuration information, the time period of the SBFD subband is determined to be the same as the period of the one TDD-UL-DL pattern. UE's method.

3. In claim 1, Based on the two TDD-UL-DL patterns being indicated to the UE by the first configuration information, the time period of the SBFD subband is determined to be equal to the sum of the periods of the two TDD-UL-DL patterns. UE's method.

4. In claim 1, Further comprising a step of receiving second configuration information of SBFD symbols set within the period of the one or more TDD-UL-DL patterns from the base station, UE's method.

5. In claim 4, The second configuration information includes at least one of an index of a start slot, an index of a start symbol within the start slot, an index of an end slot, or an index of an end symbol within the end slot, wherein the start slot is a first slot in which an SBFD symbol is set among slots within the period of the one or more TDD-UL-DL patterns, the start symbol is a first SBFD symbol within the start slot, the end slot is a last slot in which the SBFD symbol is set among slots within the period of the one or more TDD-UL-DL patterns, and the end symbol is a last SBFD symbol within the end slot. UE's method.

6. In claim 4, The first configuration information and the second configuration information are included in the same message or different messages transmitted by the base station, the same message is system information, and each of the different messages is the system information, an RRC (radio resource control) message, a MAC (medium access control) CE (control element), or DCI (downlink control information). UE's method.

7. In claim 4, The communication between the UE and the base station is performed using the SBFD symbols within the time period of the SBFD subband. UE's method.

8. As a method of base station, A step of determining one or more TDD (time division duplexing)-UL (uplink)-DL (downlink) patterns; A step of transmitting first configuration information of one or more TDD patterns to a UE (user equipment); A step of performing communication with the UE within a time period of a subband full duplex (SBFD) subband determined based on a period of the one or more TDD-UL-DL patterns indicated by the first setting information, Base station method.

9. In claim 8, Based on the fact that one TDD-UL-DL pattern is indicated to the UE by the first configuration information, the time period of the SBFD subband is determined to be the same as the period of the one TDD-UL-DL pattern. Base station method.

10. In claim 8, Based on the two TDD-UL-DL patterns being indicated to the UE by the first configuration information, the time period of the SBFD subband is determined to be equal to the sum of the periods of the two TDD-UL-DL patterns. Base station method.

11. In claim 8, A step of determining SBFD symbols set within the period of one or more TDD-UL-DL patterns; and Further comprising a step of transmitting second configuration information of the SBFD symbols to the UE, Base station method.

12. In claim 11, The second configuration information includes at least one of an index of a start slot, an index of a start symbol within the start slot, an index of an end slot, or an index of an end symbol within the end slot, wherein the start slot is a first slot in which an SBFD symbol is set among slots within the period of the one or more TDD-UL-DL patterns, the start symbol is a first SBFD symbol within the start slot, the end slot is a last slot in which the SBFD symbol is set among slots within the period of the one or more TDD-UL-DL patterns, and the end symbol is a last SBFD symbol within the end slot. Base station method.

13. In claim 11, The first configuration information and the second configuration information are included in the same message or different messages transmitted by the base station, the same message is system information, and each of the different messages is the system information, an RRC (radio resource control) message, a MAC (medium access control) CE (control element), or DCI (downlink control information). Base station method.

14. In claim 11, The communication between the base station and the UE is performed using the SBFD symbols within the time period of the SBFD subband. Base station method.

15. As UE (user equipment), Contains at least one processor, At least one of the above processors is configured such that the UE, Receive first configuration information of one or more TDD (time division duplexing)-UL (uplink)-DL (downlink) patterns from a base station; Determine the time period of the SBFD (subband full duplex) subband based on the period of the one or more TDD-UL-DL patterns indicated by the first setting information; and Causing communication with the base station to be performed within the time period of the SBFD subband; UE.

16. In claim 15, Based on the fact that one TDD-UL-DL pattern is indicated to the UE by the first configuration information, the time period of the SBFD subband is determined to be the same as the period of the one TDD-UL-DL pattern. UE.

17. In claim 15, Based on the two TDD-UL-DL patterns being indicated to the UE by the first configuration information, the time period of the SBFD subband is determined to be equal to the sum of the periods of the two TDD-UL-DL patterns. UE.

18. In claim 15, At least one of the above processors is configured such that the UE, Further causing the base station to receive second configuration information of SBFD symbols set within the period of the one or more TDD-UL-DL patterns, UE.

19. In claim 18, The second configuration information includes at least one of an index of a start slot, an index of a start symbol within the start slot, an index of an end slot, or an index of an end symbol within the end slot, wherein the start slot is a first slot in which an SBFD symbol is set among slots within the period of the one or more TDD-UL-DL patterns, the start symbol is a first SBFD symbol within the start slot, the end slot is a last slot in which the SBFD symbol is set among slots within the period of the one or more TDD-UL-DL patterns, and the end symbol is a last SBFD symbol within the end slot. UE.

20. In claim 18, The first configuration information and the second configuration information are included in the same message or different messages transmitted by the base station, the same message is system information, and each of the different messages is the system information, an RRC (radio resource control) message, a MAC (medium access control) CE (control element), or DCI (downlink control information). UE.

Images