Method and apparatus for uplink repetition and retransmission in communication system supporting sbfd

Abstract

This method for a user equipment (UE) comprises the steps of: receiving sounding reference signal (SRS) configuration information from a base station; receiving downlink control information (DCI) requesting SRS transmission from the base station; determining the validity of a slot in which SRS resources in an SRS resource set are configured, on the basis of a valid symbol type of the SRS resource set indicated by the SRS configuration information; and performing the SRS transmission in the SRS resources in the valid slot, on the basis of the slot being determined to be a valid slot.

Description

Method and apparatus for uplink repetition and retransmission in a communication system supporting SBFD

[0001] The present disclosure relates to an improved communication technology, and more specifically, to a technology for uplink repetition and retransmission in a communication system that supports SBFD (subband full duplex).

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

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

[0004] Meanwhile, a communication network may support SBFD (subband full duplex) operation. In a communication network that supports SBFD operation, a terminal may perform uplink repeat transmission and uplink retransmission. Uplink resources for uplink repeat transmission and uplink retransmission may be configured in N(non)-SBFD symbols or SBFD symbols. Methods for configuring uplink repeat transmission and uplink retransmission in N-SBFD symbols or SBFD symbols may be required.

[0005] The purpose of the present disclosure to solve the above-mentioned problems is to provide a method and apparatus for uplink repetition and retransmission in a communication system that supports SBFD (subband full duplex).

[0006] A method of user equipment (UE) according to embodiments of the present disclosure for achieving the above objective comprises: receiving sounding reference signal (SRS) setting information from a base station; receiving downlink control information (DCI) requesting SRS transmission from the base station; determining the validity of a slot in which SRS resources within an SRS resource set are configured based on a valid symbol type of an SRS resource set indicated by the SRS setting information; and performing the SRS transmission on the SRS resources within the valid slot based on the determination that the slot is a valid slot.

[0007] The step of determining the validity of the slot may include determining the slot in which the SRS resources in the SRS resource set are configured as the valid slot, based on the fact that the valid symbol type is a subband full duplex (SBFD) symbol, all SRS resources in the SRS resource set are located in the SBFD symbols in the time domain, and the time interval between the DCI and the SRS resources is greater than or equal to the offset.

[0008] The SRS resources within the above valid slots may belong to the UL (uplink) subband in the frequency domain.

[0009] The above offset can be determined based on the time required for receiving processing of the DCI and processing of the SRS transmission in the UE.

[0010] The above offset can be determined by the base station, and the above offset can be included in the SRS setting information.

[0011] The step of determining the validity of the slot may include determining the slot in which the SRS resources in the SRS resource set are set as the valid slot, based on the fact that the valid symbol type is an N(non)-SBFD symbol, all SRS resources in the SRS resource set are located in UL symbols or FL (flexible) symbols that are not set as SBFD symbols in the time domain, and the time interval between the DCI and the SRS resources is greater than or equal to an offset.

[0012] Based on the fact that the above slot is determined to be an invalid slot, the method may further include the step of postponing the SRS transmission from the SRS resources within the invalid slot.

[0013] The method of the above UE may further include the step of determining the validity of the next slot in which SRS resources within the set of SRS resources are configured; and the step of determining whether to perform the SRS transmission in the next slot based on the result of determining the validity.

[0014] The above method of the UE may further include the step of dropping the SRS transmission from the SRS resources within the invalid slot based on the fact that the slot is determined to be an invalid slot.

[0015] The method of the above UE may further include the step of receiving information from the base station indicating that available slot counting is enabled, and based on the fact that available slot counting is enabled, an operation to determine the validity of the slot in which the SRS resources within the SRS resource set are configured may be performed.

[0016] User equipment (UE) according to embodiments of the present disclosure for achieving the above objective comprises at least one processor, wherein the at least one processor causes the UE to receive sounding reference signal (SRS) setting information from a base station; receive downlink control information (DCI) from the base station requesting an SRS transmission; determine the validity of a slot in which SRS resources within an SRS resource set are set based on a valid symbol type of an SRS resource set indicated by the SRS setting information; and cause the SRS transmission to be performed on the SRS resources within the valid slot based on the determination that the slot is a valid slot.

[0017] In determining the validity of the slot, the at least one processor may cause the UE to determine the slot in which the SRS resources in the SRS resource set are configured as the valid slot, based on the fact that the valid symbol type is a subband full duplex (SBFD) symbol, all SRS resources in the SRS resource set are located in the SBFD symbols in the time domain, and the time interval between the DCI and the SRS resources is greater than or equal to the offset.

[0018] The SRS resources within the above valid slots may belong to the UL (uplink) subband in the frequency domain.

[0019] The above offset can be determined based on the time required for receiving processing of the DCI and processing of the SRS transmission in the UE.

[0020] The above offset can be determined by the base station, and the above offset can be included in the SRS setting information.

[0021] In determining the validity of the above slot, the at least one processor may cause the UE to determine the slot in which the SRS resources in the SRS resource set are set as the valid slot, based on the fact that the valid symbol type is an N(non)-SBFD symbol, all SRS resources in the SRS resource set are located in UL symbols or FL(flexible) symbols that are not set as SBFD symbols in the time domain, and the time interval between the DCI and the SRS resources is greater than or equal to an offset.

[0022] The above at least one processor may further cause the UE to postpone the SRS transmission in the SRS resources within the invalid slot based on the fact that the slot is determined to be an invalid slot.

[0023] The above at least one processor may further cause the UE to determine the validity of the next slot in which the SRS resources within the SRS resource set are configured; and to determine whether to perform the SRS transmission in the next slot based on the result of determining the validity.

[0024] The above at least one processor may further cause the UE to drop the SRS transmission from the SRS resources within the invalid slot based on the fact that the slot is determined to be an invalid slot.

[0025] The above at least one processor may further cause the UE to receive information from the base station indicating that available slot counting is enabled, and based on the availability slot counting being enabled, an operation to determine the validity of the slot in which the SRS resources within the SRS resource set are configured may be performed.

[0026] According to the present disclosure, sounding reference signal (SRS) resources may be set in subband full duplex (SBFD) symbols or non-SBFD symbols. A terminal may perform SRS transmission in SRS resources set in SBFD symbols or non-SBFD symbols when pre-set conditions are satisfied. Accordingly, ambiguity regarding the determination of the validity of SRS resources in a communication system supporting SBFD can be resolved, and the performance of the communication system can be improved.

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

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

[0029] FIG. 3 is a block diagram illustrating embodiments of communication nodes performing communication.

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

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

[0032] FIG. 5 is a conceptual diagram illustrating embodiments of a system frame in a communication system.

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

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

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

[0036] FIG. 9a is a conceptual diagram illustrating a method for determining available slots in an SBFD terminal.

[0037] FIG. 9b is a conceptual diagram illustrating a method for determining available slots in an SBFD terminal.

[0038] FIGS. 10a and FIGS. 10b are conceptual diagrams illustrating a method for determining available slots in an SBFD terminal.

[0039] FIG. 11 is a conceptual diagram illustrating a method for determining available slots in an SBFD terminal.

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

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

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

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

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

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

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

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

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

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

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

[0051] In the present disclosure, "setting an operation (e.g., a transmission operation)" may mean that "setting information for said operation (e.g., an information element, a parameter)" and / or "information directing the performance of said operation" is signaled. "Setting an information element (e.g., a parameter)" may mean that said information element is signaled. In the present disclosure, "signal and / or channel" may mean a signal, a channel, or "signal and channel," and "signal" may be used to mean "signal and / or channel." In the present disclosure, "time" and "time point" may be used interchangeably. "Time" may be interpreted as a time or a time point depending on the context, and "time point" may be interpreted as a time point or a time depending on the context.

[0052] In the present disclosure, a phrase containing "~ case (e.g., when ~)" may be expressed as a phrase containing "~ based on (e.g., based on ~)" or a phrase containing "~ in response to (e.g., in response to ~)". In other words, a phrase containing "~ case" may be interpreted as identical or similar to a phrase containing "~ based on" or a phrase containing "~ in response to".

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

[0054] FIG. 1 is a conceptual diagram illustrating embodiments of a communication system.

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

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

[0057] FIG. 2 is a block diagram illustrating embodiments of communication nodes constituting a communication system.

[0058] Referring to FIG. 2, the communication node (200) may include at least one processor (210), a memory (220), and a transceiver (230) that is connected to a network to perform communication. Additionally, 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) to communicate with one another.

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

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

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

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

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

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

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

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

[0067] FIG. 3 is a block diagram illustrating embodiments of communication nodes performing communication.

[0068] Referring to FIG. 3, the first communication node (300a) and the second communication node (300b) may each be a base station or a UE. The first communication node (300a) may transmit a signal to the second communication node (300b). A 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 a controller (316). The control information may include at least one of system information, RRC setting information (e.g., information set by RRC signaling), MAC control information (e.g., MAC CE), or PHY control information (e.g., DCI, SCI).

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

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

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

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

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

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

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

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

[0077] Referring to FIGS. 4a and 4b, a transmission path (410) may be implemented at a communication node that transmits a signal, and a reception path (420) may be implemented at a communication node that receives a signal. The transmission path (410) may include a channel coding and modulation block (411), an S-to-P (serial-to-parallel) block (412), 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 reception path (420) may include a DC (down-converter) (421), a CP removal block (422), an S-to-P block (423), an N FFT block (424), a P-to-S block (425), and a channel decoding and demodulation block (426). Here, N can be a natural number.

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

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

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

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

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

[0083] FIG. 5 is a conceptual diagram illustrating embodiments of a system frame in a communication system.

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

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

[0086] FIG. 6 is a conceptual diagram illustrating embodiments of subframes in a communication system.

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

[0088] FIG. 7 is a conceptual diagram illustrating embodiments of slots in a communication system.

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

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

[0091]

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

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

[0094] A symbol can be set as a downlink (DL) symbol, a flexible (FL) symbol, or an uplink (UL) symbol. A slot consisting only of a DL symbol may be referred to as a "DL slot," a slot consisting only of an FL symbol may be referred to as a "FL slot," and a slot consisting only of a UL symbol may be referred to as a "UL slot."

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

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

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

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

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

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

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

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

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

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

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

[0106] A communication system may support the time division duplexing (TDD) method. In a communication system that supports the TDD method (hereinafter referred to as the "TDD communication system"), DL (downlink) symbol(s) and UL (uplink) symbol(s) may be set in different time resources within a single carrier. DL symbols and UL symbols may be associated with coverage and / or latency. In a TDD communication system, the base station can utilize resources more efficiently than the frequency division duplexing (FDD) method by considering various use cases. Resource scheduling operations of the base station in a TDD communication system may be important. For enhanced TDD operation, SBFD operations (e.g., SBFD method) may be supported. If SBFD operations are 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, and other subbands may be UL subbands and / or FL subbands. In this disclosure, the DL signal may be interpreted as a DL signal, a DL channel, or "DL signal and DL channel" depending on the context. In this disclosure, the UL signal may be interpreted as a UL signal, a UL channel, or "UL signal and UL channel" depending on the context.

[0107] Symbols to which SBFD operations are applied may be referred to as SBFD symbols. Symbols to which SBFD operations are not applied may be referred to as N(non)-SBFD symbols. N-SBFD symbols may be DL symbols, UL symbols, or FL symbols. In an SBFD symbol, the terminal can perform DL communication and UL communication. In other words, in an SBFD symbol, the terminal can perform full-duplex operation. The base station may assume that DL communication and UL communication are possible in an SBFD symbol. In an N-SBFD symbol, the terminal can perform one of DL communication and UL communication. In other words, in an N-SBFD symbol, the terminal can perform half-duplex operation. An SBFD symbol may be a symbol that includes a subband to which SBFD operations are performed. The subband for SBFD may be referred to or interpreted as a UL subband. The UL subband can exist (e.g., be configured) within the symbol where the SSB (synchronization signal block) is transmitted.

[0108] Resources for SBFD operation (e.g., time resources and / or frequency resources) may be configured in a semi-static manner. In other words, the configuration for SBFD resources may be a semi-static configuration. "That the SBFD resource configuration is a semi-static configuration" may mean that the SBFD resource is configured by semi-static signaling (e.g., system information, RRC messages). In this disclosure, SBFD resources may refer to time resources and / or frequency resources for SBFD operation. UL subbands for SBFD may be SBFD resources. Alternatively, SBFD resources may be configured in a dynamic manner. "That the SBFD resource configuration is a dynamic configuration" may mean that the SBFD resource is configured by dynamic signaling (e.g., MAC CE, DCI, SCI).

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

[0110] TDD-UL-DL configuration common information can be used to configure patterns (e.g., TDD-UL-DL-Pattern) for DL ​​resources and / or UL resources in the time domain of a TDD communication system. Patterns for DL ​​resources and / or UL resources may be referred to as UL / DL patterns. UL / DL patterns may change depending on the environment of the communication system (e.g., TDD communication system). Up to two UL / DL patterns may be configured on a terminal. TDD-UL-DL configuration common information may be cell-specific parameters (e.g., cell-specific configuration information). The base station may change the configuration for symbol(s) (e.g., transmission direction, type) on a terminal-by-terminal basis based on a specific slot within a preset UL / DL pattern. The slot where the symbol configuration (e.g., symbol direction, symbol type) can be changed may 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.

[0111]

[0112]

[0113]

[0114] The UL / DL pattern, configured by the common information of the TDD-UL-DL configuration, may be repeated according to a specific period (e.g., dl-UL-TransmissionPeriodicity). In the time interval where the UL / DL pattern is applied, the leading portion may be configured as a DL resource. In the time interval where the UL / DL pattern is applied, the trailing portion may be configured as a UL resource. Resources that are not configured as DL or UL resources in the time interval where the UL / DL pattern is applied may be FL resources. The period of the UL / DL pattern may 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., DL symbol / slot) to a UL resource (e.g., UL symbol / slot). Since the propagation delay of the DL signal causes interference to the UL resource, a guard time may be required for switching from a DL resource to a UL resource. A separate guard time may not be required for switching from UL resources to DL resources. Since UL signals are transmitted based on TAC (timing advance command) directed by the base station, a guard time may not be required for switching from UL resources to DL resources.

[0115] 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". UL subband may refer to a subband for SBFD. DL symbol(s) and / or DL ​​slot(s) may be referred to as DL area(or DL ​​resource). UL symbol(s) and / or UL slot(s) may be referred to as UL area(or UL resource). FL symbol(s) and / or FL slot(s) may be referred to as FL area(or FL resource). A terminal that supports (e.g. recognizes) SBFD operation may be referred to as an SBFD terminal or SBFD UE. A terminal that does not support (e.g., does not recognize) SBFD operation may be referred to as an N(non)-SBFD terminal or an N-SBFD UE. An N-SBFD terminal may be a legacy terminal (e.g., a legacy UE). In this disclosure, a terminal may be interpreted as an SBFD terminal and / or an N-SBFD terminal depending on the context. Legacy settings (e.g., legacy information, legacy settings information) may be information for an N-SBFD terminal.

[0116] An SBFD resource may be located adjacent to (e.g., contiguously) an N-SBFD resource. An SBFD resource may refer to an SBFD symbol and / or an SBFD slot. An N-SBFD resource may refer to an N-SBFD symbol and / or an N-SBFD slot. In adjacent slots (e.g., contiguous slots), an SBFD symbol and an N-SBFD symbol may exist adjacently. The types of adjacent symbols (e.g., SBFD symbols or N-SBFD symbols) may be the same or different. The operation of the terminal may vary based on the types of adjacent symbols (e.g., the same symbol type or different symbol types).

[0117] A communication system supporting SBFD may support two types of SBFD configurations (e.g., SBFD configuration 1, SBFD configuration 2). SBFD configuration 1 may be referred to as configuration 1, SBFD transmission configuration 1, or SBFD configuration 1 transmission. SBFD configuration 2 may be referred to as configuration 2, SBFD transmission configuration 2, or SBFD configuration 2 transmission. If SBFD configuration 1 is configured on a terminal (e.g., indicated), the terminal may perform communication (e.g., downlink communication and / or uplink communication) using the same symbol type (e.g., SBFD symbol or N-SBFD symbol). If SBFD configuration 2 is configured on a terminal (e.g., indicated), the terminal may perform communication (e.g., downlink communication and / or uplink communication) using different symbol types (e.g., SBFD symbol and N-SBFD symbol). Symbol types may be classified into SBFD symbols and N-SBFD symbols. A symbol type may be interpreted as a symbol (e.g., a resource) having the said symbol type depending on the context. In the present disclosure, uplink communication (e.g., uplink transmission) may include PUCCH transmission (e.g., PUCCH repeated transmission), PUSCH transmission (e.g., PUSCH repeated transmission), and / or UL RS (reference signal) transmission (e.g., SRS transmission).

[0118] The last part of the first slot of two adjacent slots may be set to UL symbols, and uplink transmission may be performed on said UL symbols. SBFD symbols may exist in the second slot of said two adjacent slots. Under the above-described situation, based on SBFD setting 1, the terminal may not expect to perform uplink transmission on said SBFD symbols in said second slot. Under the above-described situation, based on SBFD setting 2, the terminal may perform uplink transmission on said SBFD symbols in said second slot. In other words, even if the symbol types for the symbols on which uplink transmission is performed are different, the base station may instruct (e.g., set) the terminal to perform uplink transmission on symbols having different symbol types.

[0119] In this disclosure, resource allocation methods for uplink iterative transmission, operations of a terminal for uplink iterative transmission, and / or operations of a base station for uplink iterative transmission will be described. In this disclosure, uplink iterative transmission is described with reference to PUSCH, but the embodiments proposed in this disclosure may be applied in the same or similarly to the iterative transmission of other uplink channels (e.g., PUCCH) and / or other uplink signals (e.g., SRS) as well as to PUSCH iterative transmission. The embodiments proposed in this disclosure may be applied in the same or similarly to downlink iterative transmission as well as uplink iterative transmission.

[0120] PUSCH transmissions can be classified into DG (dynamic grant) based PUSCH transmissions and CG (configured grant) based PUSCH transmissions. In DG-based PUSCH transmissions, PUSCH can be transmitted using dynamically allocated resources. For example, DG-based PUSCH transmissions can be performed based on DCI. In CG-based PUSCH transmissions, PUSCH can be transmitted using pre-configured resources. CG-based PUSCH transmissions can be performed based on at least one of RRC messages or DCI. For example, resources for CG-based PUSCH transmissions can be set by RRC messages, and DCI can direct the execution of CG-based PUSCH transmissions.

[0121] A base station may use a single DCI to direct (e.g., allocate) to a terminal not only a single PUSCH resource (e.g., a single PUSCH transmission) but also multiple PUSCH resources (e.g., multiple PUSCH transmissions). In existing communication systems, it may not be permitted for PUSCH resources for DG-based PUSCH transmissions and PUSCH resources for CG-based PUSCH transmissions to be configured across adjacent slots. In other words, long PUSCH transmissions may not be permitted. Instead of a long PUSCH transmission, multiple short PUSCH transmissions may be permitted. Transmitting multiple short PUSCHs without HARQ (hybrid automatic repeat request) feedback may be permitted. One short PUSCH transmission may be allocated per slot. Slot-based PUSCH repeat transmissions may be defined as PUSCH repeat type A.

[0122] In PUSCH repeat type A, gaps may exist between PUSCH repeat transmissions, and transmission delays may occur due to said gaps. To address the aforementioned problems, PUSCH repeat type B may be proposed. In PUSCH repeat type B, PUSCH repeat transmissions may be performed within a single slot. PUSCH repeat transmissions may be continuous or discontinuous within a single slot. The configuration (e.g., instruction) of PUSCH repeat type B may be based on DCI (e.g., DCI format 0_1, DCI format 0_2). Transport Block over Multiple Slots (TBOMS) may be introduced in the communication system. In TBoMS, a single TB may be transmitted across multiple slots.

[0123] An SBFD terminal can perform uplink transmission on SBFD symbols as well as N-SBFD symbols. To support the operation of the SBFD terminal, definitions for resource allocation methods, transmission methods, and / or reception methods for symbols having different symbol types may be required. Definitions for the above methods may be required for a single uplink transmission as well as for repeated uplink transmissions.

[0124] In this disclosure, a method for setting up repeat transmissions (e.g., a plurality of transmissions) considering a symbol type (e.g., a setting of a symbol type) and the operation of a terminal and / or base station based on the setting of repeat transmissions will be described. The operation will be described in terms of the frequency domain. PUSCH repeat transmissions may be performed based on PUSCH repeat type A, PUSCH repeat type B, or TboMS. In this disclosure, slot counting may be related to a transmission direction such as a symbol pattern (e.g., DL (downlink), UL (uplink), or FL (flexible)). Unless otherwise noted in this disclosure, DL symbols may include SSB symbols. SSB symbols may be symbols in which SSB is transmitted.

[0125] Frequency resources for PUSCH transmission can be configured based on one of three types (e.g., Type 0, Type 1, Type 2). In Type 0 (e.g., UL resource allocation Type 0), PUSCH frequency resources can be indicated by a bitmap. Each bit of the bitmap can indicate a resource block group (RBG). An RBG can include a plurality of consecutive RBs (e.g., virtual resource blocks (VRBs)). In Type 1 (e.g., UL resource allocation Type 1), PUSCH frequency resources can be indicated by a resource indication value (RIV), and the RIV can indicate the starting position (e.g., start RB) and length of a set of uninterleaved consecutive RBs (e.g., VRBs). In Type 2 (e.g., UL resource allocation Type 2), PUSCH frequency resources may be indicated by a RIV, and the RIV may indicate the starting position (e.g., starting RB) and length of a set of interleaved consecutive RBs (e.g., VRBs). Where multiple PUSCH transmissions are performed in the UL subband based on PUSCH repeated transmission or TboMS, resource allocation methods, resource determination methods, base station operations, and / or terminal operations in terms of the frequency domain will be described.

[0126] Resource indication (e.g., setting) for PUSCH repeat type A may be based on DCI (e.g., DCI format 0_1, 0_2, 0_3). Available slot counting (e.g., AvailableSlotCounting) may be set (e.g., indicated) to the terminal via RRC signaling from the base station. Having available slot counting (e.g., AvailableSlotCounting parameter) set to the terminal may mean that available slot counting is enabled. If available slot counting is enabled, the terminal may count PUSCH repeats (e.g., PUSCH repeat transmissions) in available slots. If available slot counting is not set to the terminal, the terminal may count PUSCH repeats (e.g., PUSCH repeat transmissions) in unavailable slots as well as available slots. The base station can perform scheduling for PUSCH repetitive transmissions based on the setting of available slot counting. PUSCH repetitive transmissions can be performed in N×K slots. N may represent the number of slots used to determine the transport block size (TBS). In PUSCH repetitive type A, N may be 1. K may represent the repetition factor. The repetition factor may represent the number of repetitions.

[0127] ■ Proposal #1

[0128] If available slot counting is enabled, an N-SBFD terminal (e.g., a legacy terminal) can expect PUSCH transmissions in N×K available slots. An available slot may be a slot that does not contain at least one symbol that overlaps with a DL symbol (e.g., an N-SBFD symbol) and / or an SSB symbol. An available slot may be a slot corresponding to an actual PUSCH transmission. An SBFD terminal can perform uplink transmissions in a resource (e.g., a UL subband) configured in a DL symbol and / or FL symbol. In other words, uplink transmissions of an SBFD terminal can be performed in a UL subband configured in SBFD symbols.

[0129] If a DL symbol based on a TDD pattern setting is set to an SBFD symbol (e.g., overridden), the terminal can perform uplink transmission on said DL symbol. Therefore, additional conditions for available slot counting may be required. In other words, a method for counting available slots considering resource settings in the time domain, as well as a method for counting available slots considering resource settings in the frequency domain, may be required. An SBFD terminal can transmit and receive channels and / or signals in different frequency bands (e.g., frequency resources, frequency domains). A method for counting available slots considering the operation of the SBFD terminal may be required.

[0130] If a UL subband is set in DL symbols and / or FL (flexible) symbols based on a TDD pattern setting, and a PUSCH resource completely falls within said UL subband, the SBFD terminal may determine (e.g., count, determine) the slot in which the PUSCH resource is set as an available slot. If a UL subband is set in DL symbols and / or FL symbols based on a TDD pattern setting, and some frequency resources of the PUSCH resource (e.g., at least one RE (resource element) or at least one RB (resource block)) fall within the DL subband, the SBFD terminal may not expect to determine the slot in which the PUSCH resource is set as an available slot. In other words, the SBFD terminal may determine the slot in which the PUSCH resource is set as an invalid slot.

[0131] FIG. 9a is a conceptual diagram illustrating a method for determining available slots in an SBFD terminal.

[0132] Referring to FIG. 9a, the UL subband can be set in SBFD symbols, and the PUSCH resource can belong to the UL subband. In other words, the PUSCH resource may not include frequency resources belonging to the DL subband. In this case, the SBFD terminal can determine slot #n, where the PUSCH resource is set, as an available slot.

[0133] FIG. 9b is a conceptual diagram illustrating a method for determining available slots in an SBFD terminal.

[0134] Referring to FIG. 9b, the UL subband can be configured in SBFD symbols, and some frequency resources of the PUSCH resources may belong to the DL subband. In other words, the PUSCH resources can be configured across the UL subband and the DL subband. In this case, the SBFD terminal may not determine slot #n, where the PUSCH resources are configured, as an available slot.

[0135] The SBFD terminal can determine whether the PUSCH resource belongs entirely to the UL subband in the time domain as well as in the frequency domain. For example, the SBFD terminal can determine whether the PUSCH resource belongs to the UL subband by considering SBFD setting 1 or SBFD setting 2.

[0136] ■ Proposal #2

[0137] If a PUSCH resource includes at least one symbol that overlaps with an SSB symbol, the SBFD terminal may not determine that the slot in which the PUSCH resource is set is an available slot. If an SSB is transmitted in an SBFD symbol, and a PUSCH resource exists after the SBFD symbol in which the SSB transmission is set, the terminal may not perform a PUSCH transmission in the PUSCH resource set consecutively with the SSB symbol because the priority of the SSB transmission is higher than the priority of other transmissions. To perform a PUSCH transmission after receiving an SSB, an offset corresponding to the RF (radio frequency) switching time and / or propagation delay may be required. The offset may be set on a per-symbol basis. For example, the offset may be N symbols. N may be a natural number. The offset (e.g., N symbols) may be defined in the technical specifications. Alternatively, a base station may set the offset (e.g., N symbols) and transmit the offset to the terminal via signaling. The terminal may check the offset through the base station's signaling. The signaling can be at least one of SI signaling, RRC signaling, MAC signaling, or PHY signaling.

[0138] If at least one of N symbols within an offset from an SSB resource (e.g., the last SSB symbol) is included in a PUSCH resource, the SBFD terminal may not determine that the slot in which the PUSCH resource is set is an available slot.

[0139] FIGS. 10a and FIGS. 10a are conceptual diagrams illustrating a method for determining available slots in an SBFD terminal.

[0140] Referring to FIGS. 10a and 10b, an SSB resource can be set in four symbols, and a PUSCH resource can be set consecutively to the SSB resource in the time domain. If the PUSCH resource is set after an offset from the SSB resource (e.g., the last SSB symbol), the SBFD terminal may determine the PUSCH resource to be an available slot and perform a PUSCH transmission on the PUSCH resource. The offset may be one symbol. If the PUSCH resource is set within an offset from the SSB resource (e.g., the last SSB symbol), the SBFD terminal may determine the PUSCH resource to be an unavailable slot and may not perform a PUSCH transmission on the PUSCH resource. In other words, if at least one of the symbols within an offset from the SSB resource (e.g., the last SSB symbol) is included in the PUSCH resource, the SBFD terminal may not determine the slot on which the PUSCH resource is set to be an available slot.

[0141] ■ Proposal #3

[0142] The base station may perform persistent DL transmission, semi-persistent DL transmission, and / or aperioditic DL transmission in the DL subband. DL transmission may include the transmission of channels and / or signals. Signals may include CSI-RS, PT (phase tracking)-RS, PL (path loss)-RS, etc. The base station may perform collision handling considering the characteristics of SBFD operation. Considering various environments such as repetitive transmission, UL subband configuration (e.g., patterns), and TDD patterns, the overhead of collision handling at the base station may be high. PUSCH resources may be pre-configured, in which case performing immediate collision handling may be difficult. PUSCH resources may be configured in the form of a list.

[0143] An SBFD terminal may prioritize a specific DL transmission type among multiple DL transmission types (e.g., continuous DL transmission, semi-continuous DL transmission, aperiodic DL transmission) and expect to receive a DL transmission having said specific DL transmission type. If a PUSCH resource contains at least one symbol that overlaps with symbol(s) within an offset from a DL transmission (e.g., the end time of the DL resource where the DL transmission is set), the SBFD terminal may not determine the slot where the PUSCH resource is set as an available slot. The offset may be set in units of symbols. For example, the offset may be N symbols. N may be a natural number. The offset may be set independently for each DL transmission type (e.g., continuous DL transmission, semi-continuous DL transmission, aperiodic DL transmission). In other words, the offset may be set differently for each DL transmission type. The generation time and / or generation time of the data transmitted by the terminal may vary depending on the DL transmission type. Therefore, the offset can be set independently for each DL transmission type.

[0144] An offset (e.g., N symbols) may be defined in the technical specifications. Alternatively, a base station may set an offset (e.g., N symbols) and transmit the offset to a terminal via signaling. The terminal can check the offset via the base station's signaling. The signaling may be at least one of SI signaling, RRC signaling, MAC signaling, or PHY signaling. A priority for DL ​​transmission types may be defined in the technical specifications. Alternatively, a base station may set a priority for DL ​​transmission types and transmit the priority for DL ​​transmission types to a terminal via signaling. The terminal can check the priority for DL ​​transmission types via the base station's signaling.

[0145] The terminal may not expect to receive a DL transmission based on a DL transmission type having a low priority, and may expect to perform a PUSCH transmission from a preset PUSCH resource. For collision handling, priorities between UL transmissions, priorities between DL transmissions, and / or priorities between UL transmissions and DL transmissions may be set. The terminal may determine available slots by taking into account the priorities for collision handling. If a DL transmission based on a DL transmission type having a high priority ends immediately before a PUSCH resource (e.g., a PUSCH transmission), the SBFD terminal may expect to receive said DL transmission, and the SBFD terminal may not determine as available slots a PUSCH resource that includes at least one symbol that overlaps with symbols within an offset from said DL transmission (e.g., the time when the DL transmission ends in the preset DL resource).

[0146] If a DL transmission based on a DL transmission type having a lower priority terminates immediately before a PUSCH resource (e.g., a PUSCH transmission), the SBFD terminal may not expect to receive said DL transmission, and the SBFD terminal may determine that the slot where the PUSCH resource is set is an available slot and expect to perform a PUSCH transmission on the PUSCH resource. Alternatively, the SBFD terminal may expect to transmit and receive channels and / or signals based on the priorities of DL transmissions and UL transmissions. The priority of DL transmissions may be set higher than the priority of UL transmissions. In the above situation, if a PUSCH resource exists after the DL transmission and said PUSCH resource contains at least one symbol that overlaps with symbols within an offset from said DL transmission, the SBFD terminal may not count the slot where the PUSCH resource is set as an available slot.

[0147] ■ Proposal #4

[0148] In PUSCH repeat type A or TBoMS, an N-SBFD terminal can expect PUSCH resources to be assigned to the same symbol in the slots. An UL subband may be additionally configured on the SBFD terminal, and delays may occur between repeat transmissions to determine slots having the same valid resources in the time domain and the frequency domain. The time position and / or frequency position of the PUSCH resources in the slots may differ, and the time size (e.g., number of symbols) and / or frequency size (e.g., number of RBs) of the PUSCH resources in the slots may be the same. Under the above circumstances, it may be permitted for the SBFD terminal to perform PUSCH repeat transmissions.

[0149] When SBFD setting 2 is applied, PUSCH resources belonging to the UL subband in the frequency domain may be set on symbols having different symbol types. An RB offset may be introduced so that the PUSCH resources belong to the UL subband. PUSCH resources set on the same time resource in slots may be set apart by an RB offset in the frequency domain. The SBFD terminal may determine the slots in which the above-described PUSCH resources are set as available slots.

[0150] FIG. 11 is a conceptual diagram illustrating a method for determining available slots in an SBFD terminal.

[0151] Referring to FIG. 11, PUSCH resources may be set in the same time resources (e.g., the same symbols) in slot #n and slot #n+1, and said PUSCH resources may be set in different frequency resources. The difference between the frequency resource where the PUSCH resource is set in slot #n and the frequency resource where the PUSCH resource is set in slot #n+1 may be an RB offset. In the above-described situation, the SBFD terminal may determine slot #n and slot #n+1 where the PUSCH resources are set as available slots and may perform PUSCH transmission in slot #n and slot #n+1.

[0152] ■ Proposal #4-1

[0153] A PUSCH resource can be configured in N-SBFD symbols, and the PUSCH resource can be shifted using an RB offset to belong to the UL subband. The PUSCH resource can be configured to belong to the UL subband. In this case, the base station can shift the PUSCH resource belonging to the UL subband to be identical to the frequency position of the PUSCH resource configured in the N-SBFD symbols based on the setting of the RB offset. The base station can set different RB offsets for PUSCH resources configured in different symbol types. If the configuration of PUSCH resources differs in slots, the SBFD terminal may not determine the slots in which the PUSCH resources are configured as available slots. The position of the PUSCH resource in the time domain and the frequency domain may be based on the slot in which the terminal expects the first PUSCH transmission (e.g., the configuration of the PUSCH resource in the slot).

[0154] ■ Proposal #4-2

[0155] An SBFD terminal may operate based on Proposal #4 or Proposal #4-1 based on the location of the UL subband. If the UL subband in the frequency domain includes the frequency range of the PUSCH resource set in the N-SBFD symbols, the SBFD terminal may be expected to operate based on Proposal #4-1. If the UL subband in the frequency domain does not include the frequency range of the PUSCH resource set in the N-SBFD symbols, the SBFD terminal may be expected to operate based on Proposal #4.

[0156] In PUSCH repeat type A and TBoMS, there may be one PUSCH occurrence (e.g., one PUSCH repeat, one PUSCH resource) per slot. In PUSCH repeat type B, multiple PUSCH occurrences (e.g., multiple PUSCH repeats, multiple PUSCH resources) may exist in a single slot. In PUSCH repeat type B, the validity of a PUSCH repeat (e.g., a PUSCH transfer, a PUSCH resource) can be determined on a symbol-by-symbol basis.

[0157] In PUSCH repetition type B, the PUSCH resource can be determined based on mapping type B among mapping types A and B of time domain resource allocation. In mapping type A of time domain resource allocation, the starting symbol of the PUSCH resource can be the first symbol of the slot, and the PUSCH resource can be set within a single slot. In mapping type B of time domain resource allocation, the starting symbol of the PUSCH resource can be any symbol within the slot, and the PUSCH resource can be set across multiple slots. For example, the PUSCH resource can be set across up to two slots. In PUSCH repetition type B, the PUSCH resource can also be set within a single slot. Thus, some or all of the embodiments of Proposal #1 can be applied to embodiments based on PUSCH repetition type B.

[0158] In PUSCH repetition type B, PUSCH resources can be set in up to two consecutive slots. To reduce the burden of resource setting, invalid resources can be indicated (e.g., set) to the terminal on a symbol basis. The terminal can determine (e.g., determine) the validity of a symbol (e.g., PUSCH resource) based on specific rules. The terminal may not expect PUSCH transmission on a symbol determined to be invalid.

[0159] ■ Proposal #5

[0160] PUSCH resources can be configured in SBFD symbols, and in the frequency domain, some of the PUSCH resources (e.g., at least one RE) may belong to the DL subband. In this case, the SBFD terminal may determine the PUSCH resources as invalid resources.

[0161] ■ Proposal #6

[0162] An SSB resource (e.g., an SSB symbol) may be set in an SBFD symbol. An SSB transmission (e.g., an SSB reception) may have a high priority. Therefore, if a PUSCH resource is set consecutively after an SSB resource, the SBFD terminal may not perform a PUSCH transmission from said PUSCH resource. If an SSB transmission (e.g., an SSB resource) exists, an offset between the SSB transmission and the PUSCH transmission following said SSB transmission may be required. The offset may be set considering RF switching time and / or propagation delay. The offset may be set on a symbol-by-symbol basis. For example, the offset may be set to N symbols. N may be a natural number. If a PUSCH resource is set within an UL subband and said PUSCH resource includes at least one symbol that overlaps with a symbol(s) within an offset from an SSB transmission, the SBFD terminal may determine the PUSCH resource (e.g., at least one symbol that overlaps with a symbol(s) within an offset) as an invalid resource.

[0163] The offset (e.g., N symbols) may be defined in the technical specifications. Alternatively, the base station may set the offset (e.g., N symbols) and transmit the offset to the terminal via signaling. The terminal may check the offset via the base station's signaling. The signaling may be at least one of SI signaling, RRC signaling, MAC signaling, or PHY signaling. In Proposal #6, N may be the same as or different from N in Proposal #2. In PUSCH repeat type B, multiple PUSCH resources within a single slot may be set, and for fine-grained control of PUSCH repeat transmission, N in Proposal #6 may be set conservatively (e.g., smaller) than N in Proposal #2.

[0164] ■ Proposal #7

[0165] A base station may perform continuous DL transmission, semi-continuous DL transmission, and / or aperiodic DL transmission in a DL subband. DL transmission may include the transmission of a channel and / or a signal. The signal may include CSI-RS, PT-RS, PL-RS, etc. An SBFD terminal may prioritize a specific DL transmission type among a plurality of DL transmission types (e.g., continuous DL transmission, semi-continuous DL transmission, aperiodic DL transmission) and may expect to receive a DL transmission having said specific DL transmission type. If a PUSCH resource contains at least one symbol that overlaps with a symbol(s) within an offset from a DL transmission (e.g., the end time of a DL resource where the DL transmission is configured), the SBFD terminal may determine said PUSCH resource (e.g., at least one symbol that overlaps with a symbol(s) within an offset) as an invalid resource.

[0166] The offset can be set in units of symbols. For example, the offset can be N symbols. N can be a natural number. The offset can be set independently for each DL transmission type (e.g., continuous DL transmission, semi-continuous DL transmission, aperiodic DL transmission). In other words, the offset can be set differently for each DL transmission type. The generation time and / or generation time of the data transmitted by the terminal may vary depending on the DL transmission type. Therefore, the offset can be set independently for each DL transmission type.

[0167] An offset (e.g., N symbols) may be defined in the technical specifications. Alternatively, a base station may set an offset (e.g., N symbols) and transmit the offset to a terminal via signaling. The terminal can check the offset via the base station's signaling. The signaling may be at least one of SI signaling, RRC signaling, MAC signaling, or PHY signaling. A priority for DL ​​transmission types may be defined in the technical specifications. Alternatively, a base station may set a priority for DL ​​transmission types and transmit the priority for DL ​​transmission types to a terminal via signaling. The terminal can check the priority for DL ​​transmission types via the base station's signaling.

[0168] The terminal may not expect to receive a DL transmission based on a DL transmission type having a low priority, and may expect to perform a PUSCH transmission from a preset PUSCH resource. For collision handling, priorities between UL transmissions, priorities between DL transmissions, and / or priorities between UL transmissions and DL transmissions may be set. The terminal may perform checking by considering the priorities for collision handling. If a DL transmission based on a DL transmission type having a high priority ends immediately before a PUSCH resource (e.g., a PUSCH transmission), the SBFD terminal may expect to receive said DL transmission, and the SBFD terminal may determine that a PUSCH resource containing at least one symbol that overlaps with symbols within an offset from said DL transmission (e.g., the time when the DL transmission ends in the preset DL resource) is an invalid resource. In other words, the SBFD terminal may determine that at least one symbol among the symbols constituting the PUSCH resource that overlaps with symbols within an offset from the DL transmission is an invalid symbol.

[0169] Alternatively, the SBFD terminal may expect to transmit and receive channels and / or signals based on the priorities of DL transmissions and UL transmissions. The priority of DL transmissions may be set higher than the priority of UL transmissions. In the above situation, if a PUSCH resource exists after a DL transmission and the PUSCH resource contains at least one symbol that overlaps with symbols within an offset from the DL transmission, the SBFD terminal may determine the PUSCH resource (e.g., at least one symbol that overlaps with symbols within an offset) as an invalid resource.

[0170] Meanwhile, SRS resources can be configured per symbol type. The base station can independently signal to the terminal the SRS resources configured in N-SBFD symbols (e.g., a set of SRS resources) and the SRS resources configured in SBFD symbols (e.g., a set of SRS resources). When SBFD configuration 2 is applied, the SBFD terminal can transmit and receive channels and / or signals in symbols having different symbol types. A method for counting available symbols in the above-described situation may be required.

[0171] A base station may generate SRS configuration information (e.g., SRS-Config). The SRS configuration information may include SRS resource set information (e.g., SRS-ResourceSet) and SRS resource information (e.g., SRS-Resource). The SRS resource set information may include information indicating the type of an SRS resource set (e.g., SRS transmission) (e.g., periodic, non-periodic, or semi-continuous), information indicating valid symbol types of the SRS resource set (e.g., SBFD symbols or N-SBFD symbols), etc. Valid symbol types may be set as units of the SRS resource set. The SRS resource information may include time resource information, frequency resource information, sequence information, transmission power information, etc. The base station may transmit the SRS configuration information to a terminal via signaling. The terminal may receive the SRS configuration information via the base station's signaling.

[0172] The base station may set available slot counting on the terminal. Setting available slot counting on the terminal may mean that the terminal is indicated that available slot counting is enabled. If the base station does not set available slot counting on the terminal, available slot counting may be interpreted as disabled. The terminal may confirm that available slot counting has been set by the base station. If available slot counting is set on the terminal, the terminal may count (e.g., determine, decide) available slots for SRS transmission.

[0173] SRS settings may direct non-periodic SRS transmission. Counting of available slots for SRS transmission may be configured. The terminal may receive a DCI requesting SRS transmission (e.g., a triggering PDCCH) from the base station. In the above-described situation, the terminal may determine available slots for SRS transmission based on valid symbol types of the SRS resource set (e.g., SBFD symbols or N-SBFD symbols).

[0174] [Scenario where the valid symbol type of the SRS resource set is an SBFD symbol]

[0175] If the valid symbol type of the SRS resource set is an SBFD symbol, the terminal may determine that the slot where the SRS resources are set is a usable slot (e.g., a valid slot) if it satisfies the following two conditions (e.g., SBFD conditions 1 and 2).

[0176] - SBFD Condition 1: All SRS resources within the SRS resource set are located at SBFD symbols in the time domain (e.g., configured)

[0177] - SBFD Condition 2: The time interval between the triggering DCI (e.g., the end time of the DCI requesting the SRS transmission) and all SRS resources belonging to the SRS resource set satisfies the minimum timing requirement.

[0178] In the above-described SBFD condition 1, whether all SRS resources within the SRS resource set belong to the UL subband may be further considered. If all SRS resources within the SRS resource set are located in the SBFD symbols in the time domain and all SRS resources within the SRS resource set belong to the UL subband, the terminal may determine that the above-described SBFD condition 1 is satisfied. Alternatively, in the above-described SBFD condition 1, whether SRS resources among all SRS resources within the SRS resource set that are associated with an SRS transmission requested by a DCI (e.g., triggering PDCCH) belong to the UL subband may be further considered. If all SRS resources within the SRS resource set are located in the SBFD symbols in the time domain and all SRS resources among all SRS resources within the SRS resource set that are associated with an SRS transmission requested by a DCI (e.g., triggering PDCCH) belong to the UL subband, the terminal may determine that the above-described SBFD condition 1 is satisfied.

[0179] In the above-described SBFD Condition 1, if at least one SRS resource within the SRS resource set is not located in the SBFD symbol, the terminal may determine that SBFD Condition 1 is not satisfied. In SBFD Condition 2, the minimum timing requirement may be determined based on the terminal's capabilities. The minimum timing requirement may be the minimum time required for DCI reception processing and SRS transmission processing. The terminal may determine the offset based on the minimum timing requirement. Alternatively, the offset may be determined by the base station. The base station may transmit the offset to the terminal via signaling. The terminal may check the offset through the base station's signaling. The offset may be included in the SRS configuration information. If the time interval between the triggering DCI and all SRS resources belonging to the SRS resource set is greater than or equal to the offset, the terminal may determine that SBFD Condition 2 is satisfied.

[0180] Based on the fact that the valid symbol type of the SRS resource set is an SBFD symbol and that SBFD conditions 1 and 2 are satisfied, the terminal can determine (e.g., determine) that the slot in which the SRS resources belonging to the SRS resource set are configured is a valid slot. The terminal can perform SRS transmissions on the SRS resources within the valid slot. The base station can expect to receive SRS transmissions on the SRS resources within the valid slot.

[0181] Based on the fact that the valid symbol type of the SRS resource set is an SBFD symbol and that at least one of SBFD conditions 1 or 2 is not satisfied, the terminal may determine that the slot in which the SRS resources belonging to the SRS resource set are configured is an invalid slot. The terminal may postpone SRS transmissions from the SRS resources within the invalid slot. In this case, the terminal may determine the validity of the next slot in which the SRS resources are configured and, based on the result of the validity determination, determine whether to perform SRS transmissions in the next slot. In the procedure for determining slot validity, the terminal may determine whether SBFD conditions 1 and 2 are satisfied. Alternatively, the terminal may drop SRS transmissions from the SRS resources within the invalid slot.

[0182] [Scenario where the valid symbol type of the SRS resource set is an N-SBFD symbol]

[0183] If the valid symbol type of the SRS resource set is an N-SBFD symbol, the terminal may determine that the slot where the SRS resources are set is an available slot if it satisfies the following two conditions (e.g., N-SBFD conditions 1 and 2).

[0184] - N-SBFD Condition 1: All SRS resources within the SRS resource set are located on UL symbols and / or FL symbols in the time domain that are not set to SBFD symbols (e.g., set).

[0185] - N-SBFD Condition 2: The time interval between the triggering DCI (e.g., the end time of the DCI requesting the SRS transmission) and all SRS resources belonging to the SRS resource set satisfies the minimum timing requirement.

[0186] In the above-described N-SBFD Condition 1, if at least one SRS resource within the SRS resource set is located at the SBFD symbol, the terminal may determine that N-SBFD Condition 1 is not satisfied. In N-SBFD Condition 2, the minimum timing requirement may be determined based on the terminal's capabilities. The minimum timing requirement may be the minimum time required for DCI reception processing and SRS transmission processing. The terminal may determine an offset based on the minimum timing requirement. Alternatively, the offset may be determined by the base station. The base station may transmit the offset to the terminal via signaling. The terminal may check the offset through the base station's signaling. The offset may be included in the SRS configuration information. If the time interval between the triggering DCI and all SRS resources belonging to the SRS resource set is greater than or equal to a preset offset, the terminal may determine that N-SBFD Condition 2 is satisfied.

[0187] Based on the fact that the valid symbol type of the SRS resource set is an N-SBFD symbol and N-SBFD conditions 1 and 2 are satisfied, the terminal can determine (e.g., determine) that the slot in which the SRS resources belonging to the SRS resource set are configured is a valid slot. The terminal can perform SRS transmissions on the SRS resources within the valid slot. The base station can expect to receive SRS transmissions on the SRS resources within the valid slot.

[0188] Based on the fact that the valid symbol type of the SRS resource set is an N-SBFD symbol and that at least one of N-SBFD conditions 1 or 2 is not satisfied, the terminal may determine that the slot in which the SRS resources belonging to the SRS resource set are configured is an invalid slot. The terminal may defer SRS transmission from the SRS resources within the invalid slot. In this case, the terminal may determine the validity of the next slot in which the SRS resources are configured and, based on the result of the validity determination, determine whether to perform SRS transmission in the next slot. In the slot validity determination procedure, the terminal may determine whether N-SBFD conditions 1 and 2 are satisfied. Alternatively, the terminal may drop SRS transmission from the SRS resources within the invalid slot.

[0189] ■ Proposal #8

[0190] Considering the overhead of the communication system, an SBFD terminal may have one available slot counter, similar to an N-SBFD terminal. This one available slot counter may be referred to as a common counter. For example, regardless of the symbol type, if a slot containing symbols configured for a transmission (e.g., SRS transmission, PUSCH transmission) is available, the terminal may increment or sustain the common counter. In this case, transmissions may be performed only for specific symbol types depending on the UL subband configuration. To address the aforementioned problem, an available slot counter for each symbol type may be configured. For example, the terminal may use an available slot counter for SBFD symbols in SBFD symbols and an available slot counter for N-SBFD symbols in N-SBFD symbols. The base station may configure the number of repeated transmissions (e.g., the number of available slots) for each symbol type in the terminal.

[0191] ■ Proposal #9

[0192] To prevent synchronization loss at the terminal, the terminal may not expect to receive specific settings. Alternatively, constraints such as a timer that allows monitoring of a minimum number of SSBs may be applied.

[0193] A base station may set a condition (e.g., a timer or threshold) on a terminal in the time domain. The terminal may check the condition in the time domain set by the base station. The timer may be set in units of symbols, slots, or frames. The above-mentioned condition may be defined in technical specifications. Alternatively, the base station may transmit the above-mentioned condition to the terminal via signaling. The signaling may include at least one of SI signaling, RRC signaling, MAC signaling, or PHY signaling.

[0194] When the timer expires or when a time based on a threshold has passed, the terminal may perform monitoring for SSB reception in an SSB resource that overlaps with the UL subband. Alternatively, even when an SSB resource existing just before the timer expires or an SSB resource existing just before a time based on a threshold has passed overlaps with the UL subband, the terminal may perform monitoring for SSB reception in said SSB resource.

[0195] The base station may transmit an instruction to turn ON or OFF regarding the above-described operation to the terminal via signaling. The terminal may confirm the instruction from the base station and, based on the instruction, may or may not perform the above-described operation. If an ON instruction regarding the above-described operation is received, the terminal may perform the above-described operation. If an OFF instruction regarding the above-described operation is received, the terminal may not perform the above-described operation.

[0196] In this disclosure, a higher proposal (e.g., Proposal #1, Proposal #2, Proposal #3, Proposal #4, etc.) and a lower proposal associated with said higher proposal have been described. A lower proposal(s) associated with any higher proposal may be applied to another higher proposal. A combination of some or all of the higher proposals and the lower proposals associated with said higher proposals may be utilized. For example, some or all of the proposals may be applied regardless of the PUSCH iteration type. Or, some or all of the proposals may be applied only to a specific PUSCH iteration type.

[0197] Embodiments of the present disclosure may be used with rules, methods, and / or conditions for setting up PUSCH resources in the time domain.

[0198] In the present disclosure, the UL subband may be a time domain and frequency domain where uplink communication is possible in DL symbol(s) and / or FL symbol(s). The UL available PRBs may be an overlapping area between the UL subband and an active UL BWP. In the present disclosure, the DL subband may be a time domain and frequency domain where downlink communication is possible in DL symbol(s) and / or FL symbol(s). The DL available PRBs may be an overlapping area between the DL subband and a BWP (e.g., an active DL BWP).

[0199] In the present disclosure, a terminal may transmit information to a base station indicating whether it supports the function(s) proposed in the present disclosure. Information indicating whether it supports the function(s) may be included in a UE capability report. A base station may receive a UE capability report from a terminal and perform signaling and / or operations based on the information included in the UE capability information (e.g., information indicating whether it supports the function(s).

[0200] Settings for the UL subband (e.g., SBFD settings) can be transmitted via signaling (e.g., RRC signaling). SBFD settings can be transmitted after the transmission of TDD common settings. The methods proposed in this disclosure can be applied to unlicensed bands as well as licensed bands. The methods proposed in this disclosure can be applied to sidelinks and / or supplementary uplinks (SUL). For example, the methods proposed in this disclosure can be applied to determine transmit power in sidelinks and / or SULs.

[0201] Each of the proposals of the present disclosure may be applied independently. Or a combination of the proposals of the present disclosure may be applied. Some proposals of the present disclosure may be applied to other proposals. Each of the options of the present disclosure may be applied independently. Or a combination of the options of the present disclosure may be applied. Some options of the present disclosure may be applied to other options. The proposals and / or options of the present disclosure may be applied regardless of the RRC state of the terminal. For example, a terminal in an RRC idle state, a terminal in an RRC inactive state, and / or a terminal in an RRC connected state may perform the proposals and / or options of the present disclosure. A base station may perform the proposals and / or options of the present disclosure for a terminal in an RRC idle state, a terminal in an RRC inactive state, and / or a terminal in an RRC connected state.

[0202] The channels / signals to which the proposals of the present disclosure apply may not be limited to specific channels / signals. In other words, the proposals of the present disclosure may be applied in the same or similarly to all channels / signals (e.g., all uplink channels, all uplink signals, all downlink channels, all downlink signals).

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

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

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

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

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

Claims

1. As a method of UE (user equipment), A step of receiving SRS (sounding reference signal) setting information from a base station; A step of receiving DCI (downlink control information) requesting SRS transmission from the base station; A step of determining the validity of a slot in which SRS resources within an SRS resource set are configured based on a valid symbol type of an SRS resource set indicated by the above SRS setting information; and Based on the fact that the above slot is determined to be a valid slot, the step of performing the SRS transmission on the SRS resources within the valid slot, UE's method.

2. In Claim 1, The step of determining the validity of the above slot is, Based on the fact that the valid symbol type is a subband full duplex (SBFD) symbol, all SRS resources within the SRS resource set are located at the SBFD symbols in the time domain, and the time interval between the DCI and the SRS resources is greater than or equal to the offset, the method comprises the step of determining the slot in which the SRS resources within the SRS resource set are configured as the valid slot. UE's method.

3. In Claim 2, The SRS resources within the above valid slots belong to the UL (uplink) subband in the frequency domain, UE's method.

4. In Claim 2, The above offset is determined based on the time required for receiving processing of the DCI and processing of the SRS transmission in the UE, UE's method.

5. In Claim 2, The above offset is determined by the base station, and the above offset is included in the SRS setting information, UE's method.

6. In Claim 1, The step of determining the validity of the above slot is, The method comprises the step of determining the slot in which the SRS resources in the SRS resource set are configured as the valid slot, based on the fact that the valid symbol type is an N(non)-SBFD symbol, all SRS resources in the SRS resource set are located in UL symbols or FL (flexible) symbols that are not set as SBFD symbols in the time domain, and the time interval between the DCI and the SRS resources is greater than or equal to an offset. UE's method.

7. In Claim 1, Based on the fact that the above slot is determined to be an invalid slot, the method further includes the step of postponing the SRS transmission in the SRS resources within the invalid slot. UE's method.

8. In Claim 7, A step of determining the validity of the next slot in which SRS resources within the above SRS resource set are configured; and A step further comprising determining whether to perform the SRS transmission in the next slot based on the result of determining the validity above, UE's method.

9. In Claim 1, Based on the fact that the above slot is determined to be an invalid slot, the method further includes the step of dropping the SRS transmission from the SRS resources within the invalid slot. UE's method.

10. In Claim 1, The method further includes the step of receiving information from the base station indicating that available slot counting is enabled, Based on the fact that the above available slot counting is enabled, an operation is performed to determine the validity of the slot set by the SRS resources within the above SRS resource set. UE's method.

11. As UE (user equipment), It includes at least one processor, wherein the at least one processor is the UE, Receive SRS (sounding reference signal) configuration information from the base station; Receive DCI (downlink control information) requesting SRS transmission from the base station; Determining the validity of slots in which SRS resources within the SRS resource set are configured based on valid symbol types of the SRS resource set indicated by the above SRS setting information; and Based on the fact that the above slot is determined to be a valid slot, causing the SRS transmission to be performed on the SRS resources within the valid slot, UE.

12. In Claim 11, In determining the validity of the above slot, the at least one processor is the UE, Based on the fact that the above valid symbol type is an SBFD (subband full duplex) symbol, all SRS resources within the above SRS resource set are located on SBFD symbols in the time domain, and the time interval between the DCI and the above SRS resources is greater than or equal to an offset, causing the above SRS resources within the above SRS resource set to determine the slot set as the valid slot, UE.

13. In Claim 12, The SRS resources within the above valid slots belong to the UL (uplink) subband in the frequency domain, UE.

14. In Claim 12, The above offset is determined based on the time required for receiving processing of the DCI and processing of the SRS transmission in the UE, UE.

15. In Claim 12, The above offset is determined by the base station, and the above offset is included in the SRS setting information, UE.

16. In Claim 11, In determining the validity of the above slot, the at least one processor is the UE, Based on the fact that the valid symbol type is an N(non)-SBFD symbol, and all SRS resources within the SRS resource set are located on UL symbols or FL (flexible) symbols that are not set as SBFD symbols in the time domain, and the time interval between the DCI and the SRS resources is greater than or equal to an offset, causing the slot in which the SRS resources within the SRS resource set are set to be determined as the valid slot, UE.

17. In Claim 11, The above at least one processor is the UE, Based on the fact that the above slot is determined to be an invalid slot, causing further delay (postpone) of the SRS transmission in the SRS resources within the above invalid slot, UE.

18. In Claim 17, The above at least one processor is the UE, Determines the validity of the next slot in which the SRS resources within the above SRS resource set are configured; and Further causing to determine whether to perform the SRS transmission in the next slot based on the result of determining the validity above, UE.

19. In Claim 11, The above at least one processor is the UE, Based on the fact that the above slot is determined to be an invalid slot, further causing the SRS transmission to be dropped from the SRS resources within the said invalid slot, UE.

20. In Claim 11, The above at least one processor is the UE, It further causes receiving information from the base station indicating that available slot counting is enabled, Based on the fact that the above available slot counting is enabled, an operation is performed to determine the validity of the slot set by the SRS resources within the above SRS resource set. UE.

Images