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

Abstract

This method for a user equipment (UE) comprises the steps of: receiving, from a base station, information indicating physical uplink shared channel (PUSCH) repetition type A; on the basis that subband full duplex (SBFD) configuration 2 is not indicated for the UE, determining the validity of a PUSCH resource for PUSCH repetition transmission based on the PUSCH repetition type A; and on the basis that the PUSCH resource is an invalid PUSCH resource, performing an operation in the invalid PUSCH resource on the basis of whether available slot counting is configured.

Description

Method and device for uplink iterative transmission in a communication system supporting SBFD

[0001] The present disclosure relates to an improved communication technology, and more specifically, to a technology for uplink repeated transmission 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, the communication network may support SBFD (subband full duplex) operation. In a communication network that supports SBFD operation, a terminal may perform uplink repeat transmission. Uplink resources for uplink repeat transmission may be configured in N(non)-SBFD symbols or SBFD symbols. Methods for configuring uplink repeat transmission in N-SBFD symbols or SBFD symbols may be required.

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

[0006] A method of a user equipment (UE) according to embodiments of the present disclosure for achieving the above objective comprises: receiving information from a base station indicating a physical uplink shared channel (PUSCH) repeat type A; determining the validity of a first PUSCH resource for a PUSCH repeat transmission based on the PUSCH repeat type A based on the fact that a subband full duplex (SBFD) setting 2 is not indicated to the UE; and not performing a first PUSCH transmission on the invalid PUSCH resource based on the fact that the first PUSCH resource is an invalid PUSCH resource.

[0007] The step of not performing a first PUSCH transmission in the above-mentioned invalid PUSCH resource may include a step of delaying the first PUSCH transmission in the above-mentioned invalid PUSCH resource based on available slot counting set in the UE, and the slot containing the above-mentioned invalid PUSCH resource may not be counted as an available slot.

[0008] The method of the above UE may further include the step of determining the validity of a second PUSCH resource for the PUSCH repeat transmission based on the PUSCH repeat type A; and the step of determining whether to perform a PUSCH repeat transmission in the second PUSCH resource based on the result of determining the validity, wherein the second PUSCH resource may be determined as a valid PUSCH resource based on the fact that the type of symbols set in the second PUSCH resource is the same as the type of symbols set in the first PUSCH resource, and the second PUSCH resource may be determined as an invalid PUSCH resource based on the fact that the type of symbols set in the second PUSCH resource is different from the type of symbols set in the first PUSCH resource.

[0009] The step of not performing a first PUSCH transmission in the above-mentioned invalid PUSCH resource may include the step of dropping a PUSCH transmission in the above-mentioned invalid PUSCH resource based on the fact that available slot counting is not set in the UE, and the PUSCH transmission dropped in the above-mentioned invalid PUSCH resource may be counted as a PUSCH repetition count.

[0010] The fact that the above SBFD setting 2 is not indicated to the above UE may mean that SBFD setting 1 is applied.

[0011] The above method of the UE may further include the step of receiving information from the base station indicating a valid symbol type among the symbol types, and the valid symbol type may be an SBFD symbol or an N(non)-SBFD symbol.

[0012] The step of determining the validity of the first PUSCH resource may include determining the PUSCH resource set in the SBFD symbols as valid and determining the PUSCH resource set in the N-SBFD symbols as invalid, based on the SBFD symbol being indicated as the valid symbol type.

[0013] The step of determining the validity of the first PUSCH resource may include determining the PUSCH resource set in the SBFD symbols as invalid and determining the PUSCH resource set in the N-SBFD symbols as valid, based on the fact that the N-SBFD symbol is indicated as the valid symbol type.

[0014] The step of determining the validity of the first PUSCH resource may include: determining the type of symbols for which the first PUSCH transmission was performed as a valid symbol type; and determining the validity of the first PUSCH resource based on whether there is identity between the type of symbols for which the first PUSCH resource is set and the valid symbol type.

[0015] The step of determining the validity of the first PUSCH resource may include determining the first PUSCH resource as invalid based on the fact that the first PUSCH resource is set across the SBFD symbol and the UL (uplink) symbol.

[0016] The step of determining the validity of the first PUSCH resource may include determining the first PUSCH resource as invalid based on the fact that a portion of the first PUSCH resource does not belong to the UL subband in the frequency domain.

[0017] The step of determining the validity of the first PUSCH resource may include determining the first PUSCH resource as invalid based on the fact that the gap between the DL (downlink) transmission prior to the first PUSCH resource and the first PUSCH resource in the time domain is smaller than the offset.

[0018] The step of determining the validity of the first PUSCH resource may include determining the first PUSCH resource as invalid based on the fact that the first PUSCH resource includes at least one symbol that overlaps with an SSB symbol for SSB (synchronization signal block) transmission.

[0019] 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 receives information from a base station indicating a physical uplink shared channel (PUSCH) repeat type A; determines the validity of a first PUSCH resource for a PUSCH repeat transmission based on the PUSCH repeat type A based on the fact that a subband full duplex (SBFD) setting 2 is not indicated to the UE; and causes not to perform a first PUSCH transmission on the invalid PUSCH resource based on the fact that the first PUSCH resource is an invalid PUSCH resource.

[0020] The operation causing the first PUSCH transmission not to be performed on the above-mentioned invalid PUSCH resource is that the at least one processor may cause the UE to delay the first PUSCH transmission on the above-mentioned invalid PUSCH resource based on available slot counting set on the UE, and the slot containing the above-mentioned invalid PUSCH resource may not be counted as an available slot.

[0021] The above at least one processor may further cause the UE to determine the validity of a second PUSCH resource for a PUSCH repeat transmission based on the PUSCH repeat type A; and to determine whether to perform a PUSCH repeat transmission in the second PUSCH resource based on the result of determining the validity, and the second PUSCH resource may be determined to be a valid PUSCH resource based on the fact that the type of symbols set in the second PUSCH resource is the same as the type of symbols set in the first PUSCH resource, and the second PUSCH resource may be determined to be an invalid PUSCH resource based on the fact that the type of symbols set in the second PUSCH resource is different from the type of symbols set in the first PUSCH resource.

[0022] The operation causing the first PUSCH transmission not to be performed in the above invalid PUSCH resource is that the at least one processor may cause the UE to drop the PUSCH transmission in the above invalid PUSCH resource based on the fact that the available slot counting is not set in the UE, and the PUSCH transmission dropped in the above invalid PUSCH resource may be counted as a PUSCH repetition count.

[0023] The above at least one processor may further cause the UE to receive information from the base station indicating a valid symbol type among the symbol types, and the valid symbol type may be an SBFD symbol or an N(non)-SBFD symbol.

[0024] The operation causing the validity of the first PUSCH resource may be such that the at least one processor causes the UE to determine the PUSCH resource set in the SBFD symbols as valid and the PUSCH resource set in the N-SBFD symbols as invalid based on the SBFD symbol being indicated as the valid symbol type, or causes the PUSCH resource set in the SBFD symbols as invalid and the PUSCH resource set in the N-SBFD symbols as valid based on the N-SBFD symbol being indicated as the valid symbol type.

[0025] The operation causing the validity of the first PUSCH resource may cause the at least one processor to cause the UE to determine the type of symbols for which the first PUSCH transmission was performed as a valid symbol type; and to determine the validity of the first PUSCH resource based on whether there is an identity between the type of symbols for which the first PUSCH resource is set and the valid symbol type.

[0026] According to the present disclosure, a terminal can determine the validity of a physical uplink shared channel (PUSCH) resource based on a subband full duplex (SBFD) setting 1 or an SBFD setting 2. If the PUSCH resource is determined to be a valid resource, the terminal can perform a PUSCH transmission on the valid PUSCH resource. If the PUSCH resource is determined to be an invalid resource, the terminal can postpone or drop the PUSCH transmission on the invalid PUSCH resource. Based on the above-described operation, the validity of the PUSCH resource can be clearly determined according to the SBFD setting, and ambiguity in the terminal's operation can be resolved accordingly. Thus, 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. 9 is a conceptual diagram illustrating a method for determining available slots in an N-SBFD terminal.

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

[0038] FIG. 11a is a conceptual diagram illustrating a method for determining available slots in an SBFD terminal in a scenario where SBFD setting 1 is applied.

[0039] FIG. 11b is a conceptual diagram illustrating a method for determining available slots in an SBFD terminal in a scenario where SBFD setting 1 is applied.

[0040] FIG. 11c is a conceptual diagram illustrating a method for determining available slots in an SBFD terminal in a scenario where SBFD setting 1 is applied.

[0041] FIG. 12 is a conceptual diagram illustrating a method for determining available slots in an SBFD terminal in a scenario where SBFD setting 2 is applied.

[0042] FIG. 13 is a conceptual diagram illustrating a method for determining valid symbols at an SBFD terminal in a scenario where SBFD setting 2 is applied.

[0043] Figure 14 is a conceptual diagram illustrating the PUSCH resource configuration.

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

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

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

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

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

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

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

[0051] Hereinafter, preferred embodiments of the present disclosure will be described in more detail with reference to the attached drawings. To facilitate an overall understanding of 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.

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

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

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

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

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

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

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

[0059] Referring to FIG. 1, the communication system (100) may include a plurality of communication nodes (110-1, 110-2, 110-3, 120-1, 120-2, 130-1, 130-2, 130-3, 130-4, 130-5, 130-6). 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.

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

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

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

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

[0064] Referring again to FIG. 1, the communication system (100) may include a plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) and a plurality of terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6). Each of the first base station (110-1), the second base station (110-2), and the third base station (110-3) may form a macro cell. Each of the fourth base station (120-1) and the fifth base station (120-2) may form a small cell. The fourth base station (120-1), the third terminal (130-3), and the fourth terminal (130-4) may be 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).

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

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

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

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

[0069] Each of the first base station (110-1), the second base station (110-2), and the third base station (110-3) can transmit a signal to the fourth terminal (130-4) based on the CoMP 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).

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

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

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

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

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

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

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

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

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

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

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

[0081] Referring to FIGS. 4a and 4b, a transmission path (410) may be implemented 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.

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

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

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

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

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

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

[0088] Referring to FIG. 5, time resources in a communication system can be divided into 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.

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

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

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

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

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

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

[0095]

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

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

[0098] The 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 an "FL slot," and a slot consisting only of a UL symbol may be referred to as an "UL slot."

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

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

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

[0102] Referring to FIG. 8, a resource consisting of one symbol (e.g., an OFDM symbol) in the time domain and one subcarrier in the frequency domain 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.

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

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

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

[0106] CORESET information may include PDCCH DMRS (demodulation reference signal) information, PDCCH precoding information, PDCCH occasion information, etc. The PDCCH DMRS may be a DMRS used to demodulate the PDCCH. 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).

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

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

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

[0110] A communication system may support 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.

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

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

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

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

[0115]

[0116]

[0117]

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

[0119] TDD-UL-DL configuration common information (e.g., TDD-UL-DL-ConfigCommon) may be referred to as "TDD Common" or "TDD Common Information". TDD-UL-DL configuration dedicated information (e.g., TDD-UL-DL-ConfigDedicated) may be referred to as "TDD Dedicated" or "TDD Dedicated Information". 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.

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

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

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

[0123] 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 primarily with respect to PUSCH transmission (e.g., PUSCH iterative transmission), but the embodiments proposed in this disclosure may be applied in the same or similarly to transmission of other uplink channels (e.g., PUCCH) and / or other uplink signals (e.g., SRS) as well as to PUSCH transmission. The embodiments proposed in this disclosure may be applied in the same or similarly to downlink transmission (e.g., downlink iterative transmission) as well as to uplink transmission (e.g., uplink iterative transmission).

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

[0125] 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 long PUSCH transmissions, multiple short PUSCH transmissions may be permitted. It may be permitted to perform multiple short PUSCH transmissions without HARQ (hybrid automatic repeat request) feedback. One short PUSCH transmission may be allocated per slot. Slot-based PUSCH repeat transmissions may be defined as PUSCH repeat type A. In this disclosure, a PUSCH resource may mean a PUSCH transmission occasion or a PUSCH occasion.

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

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

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

[0129] 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). The base station may set (e.g., indicate) an available slot counting parameter (e.g., AvailableSlotCounting) to the terminal via RRC signaling. Having the available slot counting parameter set to the terminal may mean that the available slot counting parameter is enabled. If the available slot counting parameter is enabled, the terminal can count PUSCH repeats (e.g., PUSCH repeat transmissions) in available slots. If the available slot counting parameter is not set to the terminal, the terminal can 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 parameters. 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.

[0130] ■ Proposal #1 (PUSCH Iteration Type A, TBoMS)

[0131] When available slot counting (e.g., available slot counting parameter) is enabled, the terminal can expect to perform PUSCH transmissions (e.g., repeated PUSCH transmissions) in N×K slots. Counting of available slots can be performed at the terminal. The base station can transmit information on pre-configured resources based on a semi-static method per cell or per terminal. Resource patterns may differ per slot, and channel settings may differ per slot. The terminal can determine which slots are capable of PUSCH transmission by considering the resource patterns and / or channel settings in the slots. A slot available to an N-SBFD terminal may be a slot containing symbols that do not overlap with at least one DL symbol and / or at least one SSB symbol.

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

[0133] Referring to FIG. 9, PUSCH resources may be allocated in slot #n, and one of the symbols of the PUSCH resources may overlap with a DL symbol. In this case, the SBFD terminal may determine that slot #n is an unavailable slot and may not perform PUSCH transmission in slot #n. The SBFD terminal may determine whether PUSCH transmission is possible in a slot after slot #n. In other words, the SBFD terminal may determine whether a slot after slot #n is an available slot.

[0134] DL symbols and / or FL symbols may be configured as SBFD symbols, and UL subbands may be configured from SBFD symbols. Uplink transmission may be possible in the UL subband. A method for counting available slots for an SBFD terminal may be required. If DL symbols and / or FL symbols based on the configuration of a TDD pattern (e.g., a TDD UL / DL pattern) overlap with a PUSCH resource, and said DL symbols and / or said FL symbols are SBFD symbols, the terminal may determine the slot in which said PUSCH resource is configured as an available slot. In other words, the terminal may expect to perform PUSCH transmission from said PUSCH resource. The terminal may determine a slot containing SBFD symbols and consecutive UL symbols following said SBFD symbols as a slot capable of PUSCH transmission.

[0135] DL symbols and / or FL symbols based on the TDD pattern configuration may be configured as SBFD symbols (e.g., overridden). DL symbols that are not configured as SBFD symbols may be defined as N-SBFD DL symbols. FL symbols that are not configured as SBFD symbols may be defined as N-SBFD FL symbols. An SBFD terminal may determine (e.g., determine) a slot in which a PUSCH resource is configured that includes symbols overlapping with N-SBFD DL symbols and / or N-SBFD FL symbols as an unavailable slot. An SBFD terminal may determine a slot in which a PUSCH resource is configured that consists of SBFD symbols and / or UL symbols as an available slot. Determining a slot in which a PUSCH resource is configured as an unavailable slot may mean determining the PUSCH resource as an invalid resource. Determining a slot in which a PUSCH resource is configured as an available slot may mean determining the PUSCH resource as a valid resource.

[0136] When a DL symbol based on the setting of a TDD pattern is set as an SBFD symbol, the SBFD terminal may determine that the slot in which the PUSCH resource containing the SBFD symbol is set is a usable slot. When the PUSCH resource does not overlap with the DL subband in the frequency domain and all of the PUSCH resources belong to the UL subband, the SBFD terminal may determine that the slot in which the PUSCH resource is set is a usable slot. When at least one of the PUSCH resources overlaps with the DL subband in the frequency domain, the SBFD terminal may not determine that the slot in which the PUSCH resource is set is a usable slot. The above-described embodiments may or may not be applied depending on SBFD setting 1 or SBFD setting 2.

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

[0138] Referring to FIG. 10, some symbols in the PUSCH resource may be SBFD symbols, and the terminal may determine slot #n, where the PUSCH resource is configured, as an unavailable slot. The above operation may be inefficient in terms of resources. Therefore, if some symbols in the PUSCH resource are SBFD symbols, the terminal may determine slot #n, where the PUSCH resource is configured, as an available slot. When SBFD configuration 2 is applied, since the terminal can transmit and receive channels and / or signals in symbols having different symbol types, PUSCH transmission in a PUSCH resource containing at least one symbol that overlaps with an SBFD symbol may be allowed. If a DL symbol based on the configuration of a TDD pattern is overwritten by an SBFD symbol, the terminal may determine the slot where the PUSCH resource containing the SBFD symbol is configured as an available slot.

[0139] ■ Proposal #1-1 (SBFD Configuration 1)

[0140] When SBFD setting 1 is applied, the terminal can transmit and receive channels and / or signals on symbols having the same symbol type. The terminal may apply the existing available slot counting method to a transmission resource (e.g., a PUSCH resource) containing N-SBFD symbols, and may not count a slot configured with a PUSCH resource containing at least one symbol that overlaps with an SBFD symbol as an available slot.

[0141] FIG. 11a is a conceptual diagram illustrating a method for determining available slots in an SBFD terminal in a scenario where SBFD setting 1 is applied.

[0142] Referring to FIG. 11a, a PUSCH resource may be set across SBFD symbol(s) and UL symbol(s) within a single slot. If at least one symbol of the PUSCH resource overlaps with an SBFD symbol, the SBFD terminal may not count the slot in which the PUSCH resource is set as a used slot. In other words, the SBFD terminal may determine the PUSCH resource to be an invalid resource and may not perform a PUSCH transmission on the PUSCH resource.

[0143] FIG. 11b is a conceptual diagram illustrating a method for determining available slots in an SBFD terminal in a scenario where SBFD setting 1 is applied.

[0144] Referring to FIG. 11b, in the time domain, PUSCH resources may be set in SBFD symbols, and in the frequency domain, at least one RE (resource element) or at least one RB (resource block) of the PUSCH resources may belong to a DL subband (e.g., a DL available subband). In other words, in the frequency domain, not all PUSCH resources may belong to a UL subband. Under the above circumstances, the SBFD terminal may not count the slot in which the PUSCH resources are set as an available slot. In other words, the SBFD terminal may determine the PUSCH resources to be invalid resources and may not perform PUSCH transmission on the PUSCH resources.

[0145] FIG. 11c is a conceptual diagram illustrating a method for determining available slots in an SBFD terminal in a scenario where SBFD setting 1 is applied.

[0146] Referring to FIG. 11c, in the time domain, a PUSCH resource may be set in SBFD symbols, and in the frequency domain, the PUSCH resource may belong to an UL subband (e.g., an UL available subband), and the difference (e.g., a gap) between the DL symbol prior to the PUSCH resource (e.g., the last symbol in the previous DL transmission) and the first symbol of the PUSCH resource may be smaller than the offset. In the above situation, the SBFD terminal may not count the slot in which the PUSCH resource is set as an available slot. In other words, the SBFD terminal may determine the PUSCH resource to be an invalid resource and may not perform a PUSCH transmission on the PUSCH resource. The offset may be set based on at least one of an RF (radio frequency) switching delay (e.g., the switching delay between the receiving antenna and the transmitting antenna) or a propagation delay. The offset may be set in units of symbols. For example, the offset may be two symbols.

[0147] Even if the PUSCH resource is set within the UL subband of SBFD symbols, the SBFD terminal can determine whether the slot in which the PUSCH resource is set is an available slot by taking into account an offset (e.g., N symbols) that accounts for RF switching delay and / or propagation delay caused by DL transmission (e.g., DL symbols) prior to the UL subband. N can be a natural number.

[0148] Some or all of the embodiments of Proposal #1-1 may be applied to operations according to SBFD configuration #2. The offset (e.g., N symbols) may be set to a fixed value. Alternatively, the base station may set the offset (e.g., N symbols) and transmit the offset to the terminal via signaling (e.g., SI (system information) signaling, RRC signaling). The terminal may check the offset signaled by the base station. In other words, the offset may be changed based on the base station's configuration.

[0149] In the present disclosure, handling of unavailable slots may be based on the setting of available slot counting (e.g., enabled or disabled). Available slot counting being disabled may mean that available slot counting is not indicated (e.g., set) to the terminal. If available slot counting is enabled, the terminal may determine in the next slot whether to count the unavailable slot as an available slot. If available slot counting is disabled, the terminal may immediately drop a transmission (e.g., PUSCH transmission) from the unavailable slot.

[0150] The operation based on the aforementioned proposal #1-1 can be performed as follows.

[0151] The base station may instruct the terminal to PUSCH repeat type A via signaling. The terminal can confirm that PUSCH repeat type A is being instructed via the base station's signaling. The base station may instruct the terminal to SBFD setting 1 via signaling. The terminal can confirm that SBFD setting 1 is being instructed via the base station's signaling. Instructing the terminal to SBFD setting 1 may mean that SBFD setting 2 is not being instructed to the terminal. If SBFD setting 2 is not being instructed to the terminal, SBFD setting 1 may be applied. In other words, SBFD setting 1 may not be explicitly instructed to the terminal, and if SBFD setting 2 is not being instructed to the terminal, the terminal may determine that SBFD setting 1 is applied. PUSCH repeat transmission may be performed on symbols having different symbol types in different slots. PUSCH repeat transmission may be performed in any slot consisting entirely of SBFD symbols and / or in another slot consisting entirely of N-SBFD symbols.

[0152] Based on the fact that PUSCH repeat type A is indicated to the terminal and SBFD setting 2 is not indicated to the terminal, the terminal can determine the validity of the PUSCH resource. In other words, the terminal can determine the validity of the PUSCH resource for PUSCH repeat transmission based on PUSCH repeat type A. Based on the determination that the PUSCH resource is valid, the terminal can perform PUSCH transmission (e.g., PUSCH repeat transmission) on the PUSCH resource. If the PUSCH resource is determined to be invalid, the operation of the terminal may vary based on whether the available slot counting is set. The available slot counting can be set to the terminal by the signaling of the base station. The setting of the available slot counting to the terminal may mean that the available slot counting is enabled. For example, the base station may transmit information indicating that the available slot counting is enabled to the terminal via signaling. Alternatively, the base station may not instruct (e.g., set) the terminal to count available slots.

[0153] Based on the determination that a PUSCH resource is invalid and the available slot counting is set in the terminal, the terminal may postpone PUSCH transmission from the invalid PUSCH resource (e.g., invalid symbol type). In other words, PUSCH transmission from the invalid PUSCH resource may not be dropped, and the available slot counter may be maintained until a valid PUSCH resource exists. A slot containing an invalid PUSCH resource may not be counted as an available slot. In other words, actual PUSCH transmission may not be performed in a slot containing an invalid PUSCH resource, and the PUSCH repetition count may not be increased. The terminal may determine the validity of the next PUSCH resource in the slot where the next PUSCH resource is set, and may decide to perform or postpone PUSCH transmission based on the result of the validity determination.

[0154] The terminal can determine the validity of the next PUSCH resource based on whether the type of symbols set in the previous PUSCH resource (e.g., the first PUSCH resource for the first PUSCH transmission) is the same as the type of symbols set in the next PUSCH resource. Based on whether the symbol type of the next PUSCH resource (e.g., SBFD symbol or N-SBFD symbol) is the same as the symbol type of the previous PUSCH resource (e.g., the first PUSCH resource), the terminal can determine the next PUSCH resource to be a valid PUSCH resource and perform PUSCH transmission (e.g., PUSCH repeated transmission) on the next PUSCH resource. Based on the fact that the symbol type of the next PUSCH resource (e.g., SBFD symbol or N-SBFD symbol) is different from the symbol type of the previous PUSCH resource (e.g., the first PUSCH resource), the terminal may determine the next PUSCH resource to be an invalid PUSCH resource and may defer or drop the PUSCH transmission (e.g., PUSCH repeated transmission) from the next PUSCH resource.

[0155] Based on the fact that a PUSCH resource is determined to be invalid and available slot counting is not set on the terminal, the terminal may drop a PUSCH transmission from an invalid PUSCH resource (e.g., an invalid symbol type). In other words, a PUSCH transmission from an invalid PUSCH resource may not be deferred. The number of PUSCH repetitions in a slot containing an invalid PUSCH resource may be counted. In other words, the number of PUSCH repetitions may be increased even if an actual PUSCH transmission is not performed in a slot containing an invalid PUSCH resource.

[0156] In the above-described embodiment (e.g., a situation where SBFD configuration 1 is applied), the validity of uplink resources (e.g., PUSCH resources and / or PUCCH resources) may be determined as follows. In SBFD configuration 1, the transmit operation and / or receive operation may be limited to being performed on SBFD symbols or N-SBFD symbols. In this case, the valid symbol type for the transmit operation and / or receive operation (e.g., SBFD symbols or N-SBFD symbols) may be determined based on the following method.

[0157] In semi-static transmission operations without active DCI (e.g., CG-based transmission operations) and / or semi-static reception operations (e.g., SPS (semi-persistent scheduling)-based reception operations), a valid symbol type may be indicated by the base station's RRC signaling. The base station may use RRC signaling to indicate a valid symbol type as an SBFD symbol. In this case, the terminal may determine, based on the base station's indication, that the SBFD symbol is a valid symbol type for semi-static transmission operations and / or semi-static reception operations, and may perform semi-static transmission operations and / or semi-static reception operations on the SBFD symbols. As another example, the base station may use RRC signaling to indicate a valid symbol type as an N-SBFD symbol. In this case, the terminal may determine, based on the base station's indication, that the N-SBFD symbol is a valid symbol type for semi-static transmission operations and / or semi-static reception operations, and may perform semi-static transmission operations and / or semi-static reception operations on the N-SBFD symbols.

[0158] In a transmission operation based on dynamic scheduling, a communication node (e.g., a base station and / or a terminal) may determine the symbol type of the first transmission as a valid symbol. If the symbol type of the first transmission is an SBFD symbol, the terminal may determine the SBFD symbol as a valid symbol type and perform a transmission operation on the SBFD symbols. As another example, if the symbol type of the first transmission is an N-SBFD symbol, the terminal may determine the N-SBFD symbol as a valid symbol type and perform a transmission operation on the N-SBFD symbols.

[0159] In a dynamic scheduling-based receive operation, a communication node (e.g., a base station and / or a terminal) may determine the symbol type of the first reception as a valid symbol. If the symbol type of the first reception is an SBFD symbol, the terminal may determine the SBFD symbol as a valid symbol type and perform a receive operation on the SBFD symbols. As another example, if the symbol type of the first reception is an N-SBFD symbol, the terminal may determine the N-SBFD symbol as a valid symbol type and perform a receive operation on the N-SBFD symbols.

[0160] ■ Proposal #1-2 (SBFD Configuration 2)

[0161] When SBFD setting 2 is applied, the terminal can transmit and receive channels and / or signals not only for symbols of the same symbol type but also for symbols of different symbol types. The terminal may apply the existing available slot counting method to transmission resources (e.g., PUSCH resources) containing N-SBFD symbols. The terminal may determine whether to count a slot in which a PUSCH resource is configured as an available slot based on the following methods. Available slots may be determined by considering the location of the UL subband.

[0162] In CG-based PUSCH transmission, PUSCH resources can be pre-configured at a terminal via RRC signaling. All of the pre-configured PUSCH resources may belong to the UL subband (hereinafter referred to as Case 1). Alternatively, at least one of some time resources or some frequency resources among the pre-configured PUSCH resources may be located outside the UL subband (hereinafter referred to as Case 2).

[0163] In Case 1, the SBFD terminal can count the slot where the PUSCH resource is set as an available slot. In Case 2, if at least one of the PUSCH resources is set in a DL symbol, FL symbol, or SSB symbol outside the UL subband, the SBFD terminal can determine that the slot where the PUSCH resource is set is an unavailable slot.

[0164] FIG. 12 is a conceptual diagram illustrating a method for determining available slots in an SBFD terminal in a scenario where SBFD setting 2 is applied.

[0165] Referring to FIG. 12, PUSCH resources can be set in symbols having different symbol types. PUSCH resources can be set in symbols #5 through #9. Since symbol #5 is an SBFD symbol and symbols #7 through #9 are UL symbols, but symbol #6 is a DL symbol, the SBFD terminal can determine that the slot where the PUSCH resources are set is an unavailable slot. The SBFD terminal can drop a PUSCH transmission in the slot where the PUSCH resources are set. If available slot counting is enabled, the terminal can determine in the next slot whether to count the unavailable slot as an available slot. If available slot counting is disabled, the terminal can immediately drop a transmission (e.g., a PUSCH transmission) in the unavailable slot.

[0166] ■ Proposal #1-3

[0167] The period of the TDD pattern may be the same as the period of the UL subband. The position of the UL subband may differ from slot to slot. In PUSCH repetition type A and TBoMS, the time position of the PUSCH resource may be the same in the slots where repeated transmissions are performed. Symbols having different symbol types may exist in each slot, and at least one of said symbols may overlap with the PUSCH resource. In this case, the terminal may determine that the slot in which the PUSCH resource is set is an unavailable slot. In other words, the terminal may determine that the PUSCH resource consisting of symbols having different symbol types is an invalid resource.

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

[0169] 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 may also be set within a single slot. Some or all of the embodiments of Proposal #1 may be applied to embodiments based on PUSCH repetition type B.

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

[0171] ■ Proposal #2 (PUSCH Repeat Type B)

[0172] If a DL symbol (e.g., DL transmission) exists prior to the UL subband, and a PUSCH resource is established that includes at least one symbol overlapping with a symbol within an offset from said DL symbol, the SBFD terminal may determine said PUSCH resource as an invalid resource (e.g., an invalid symbol). The offset may be established on a symbol-by-symbol basis. The offset may consist of N symbols. N may be a natural number. The offset may be established based on at least one of RF switching delay or propagation delay. In other words, the offset may be established by taking into account the time that downlink reception at the terminal affects uplink transmission. The base station may establish the offset and transmit the offset to the terminal via signaling (e.g., SI signaling, RRC signaling). The terminal may check the offset via the base station's signaling. Alternatively, the offset may be defined in the technical specifications.

[0173] When a signaling (e.g., RRC signaling, MAC signaling (e.g., MAC-CE), PHY signaling (e.g., DCI)) indicating the activity (e.g., instruction) of a preset PUSCH resource is received, the terminal may generate data for uplink transmission after receiving said signaling. Accordingly, time (e.g., symbol(s) or slot(s)) for processing uplink transmission may be required. The number of symbol(s) or slot(s) for processing uplink transmission may be defined as P. P may be a natural number. The terminal may determine that the symbols belonging to P symbol(s) or P slot(s) are invalid symbol(s) and may not perform uplink transmission on the invalid symbol(s).

[0174] ■ Proposal #2-1

[0175] The period of the TDD pattern may be the same as the period of the UL subband. The position of the UL subband may vary from slot to slot. In PUSCH repeat type B, the PUSCH resource may be set across up to two consecutive slots. Therefore, the position of the SBFD symbol between slots may be important. During the time that a PUSCH repeat transmission based on PUSCH repeat type B is performed, the position of the SBFD symbol may be the same in the slots where the PUSCH repeat transmission is performed. If the symbol type differs at the same position in each of multiple slots, the terminal may determine that the symbols having different symbol types at the same position are invalid symbols.

[0176] FIG. 13 is a conceptual diagram illustrating a method for determining valid symbols at an SBFD terminal in a scenario where SBFD setting 2 is applied.

[0177] Referring to FIG. 13, the PUSCH resource can be set in cycles of two consecutive slots (e.g., "slot #n and slot #n+1", "slot #n+2 and slot #n+3"). Based on the setting of the UL subband, the PUSCH resource can be set repeatedly in units of two slots. The positions of the UL subbands in the slots where the PUSCH resource is set repeatedly may differ. For example, the UL subband may be set to symbols #9 through #13 in slot #n, but the UL subband may not be set to symbols #9 and #10 in slot #n+2. In slot #n+2, the UL subband may be set to symbols #11 through #13. In other words, the symbol type may be changed at the same positions (e.g., symbols #9 and #10) in slot #n and slot #n+2. In this case, the terminal can determine symbols #9 and #10 in slot #n and slot #n+2 as invalid symbols.

[0178] ■ Proposal #2-2

[0179] An SBFD terminal may determine all symbols containing the UL subband as valid symbols or invalid symbols. Alternatively, a base station may transmit information to the SBFD terminal via signaling that instructs it to determine all symbols containing the UL subband as valid symbols or invalid symbols. The SBFD terminal may determine all symbols containing the UL subband as valid symbols or invalid symbols based on the information received via the base station's signaling. Information instructing it to determine all symbols containing the UL subband as valid symbols or invalid symbols may be transmitted via SI signaling or RRC signaling. Alternatively, information instructing it to determine all symbols containing the UL subband as valid symbols or invalid symbols may be transmitted via RRC signaling, and a MAC-CE or DCI may instruct a change (e.g., an update) to the information instructing it to determine all symbols containing the UL subband as valid symbols or invalid symbols.

[0180] A base station can transmit pattern information of the UL subband and resource validity information to a terminal through signaling. A terminal can receive pattern information of the UL subband and resource validity information through the signaling of the base station. Resource validity information may include at least one of information indicating whether a slot is a valid slot or an invalid slot, information indicating whether a symbol included in the slot is a valid symbol or an invalid symbol, information indicating a valid symbol type, information indicating an invalid symbol type, or information indicating whether a symbol is a valid symbol or an invalid symbol.

[0181] A base station may generate cell-specific PUSCH configuration information or UE-specific PUSCH configuration information. The PUSCH configuration information may include information on valid or invalid symbols for UL subbands (e.g., resource validity information). The base station may transmit the PUSCH configuration information to a terminal via signaling. The terminal may receive the PUSCH configuration information via the base station's signaling and verify the information on valid or invalid symbols for UL subbands included in the PUSCH configuration information.

[0182] Resource validity information may include a slot number (e.g., slot index) and a symbol number (e.g., symbol index) associated with said slot number. For example, resource validity information may include {slot #n, symbol #m}. n and m may each be an integer greater than or equal to 0. Alternatively, resource validity information may include a reference point and an offset from said reference point. The reference point may be a reference slot or a reference symbol. The offset may be a slot offset or a symbol offset. A base station may generate a set comprising one reference point and multiple offsets from said reference point. A base station may generate one or more sets. Each of the one or more sets may include one reference point and multiple offsets associated with said reference point. A base station may transmit one or more sets to a terminal via signaling. A terminal may receive one or more sets via the signaling of the base station. A base station may transmit information about invalid symbols to a terminal. A terminal may receive information about invalid symbols from the base station. In this case, even in a situation where a symbol indicated by information of an invalid symbol can be determined to be a valid symbol, the terminal can determine the symbol to be an invalid symbol based on instructions from the base station.

[0183] Alternatively, resource validity information may indicate a valid symbol type among the symbol types. For example, resource validity information may indicate that an SBFD symbol or an N-SBFD symbol is a valid resource (e.g., a valid symbol). Based on the fact that an SBFD symbol is indicated as a valid resource, the terminal may determine that the PUSCH resource set in the SBFD symbols is the valid resource among the PUSCH resources set in the SBFD symbols and the PUSCH resources set in the N-SBFD symbols, and may perform a PUSCH transmission (e.g., a PUSCH repeat transmission) on the valid PUSCH resource. If the PUSCH resource set in the N-SBFD symbols is an invalid resource, the terminal may drop or postpone the PUSCH transmission on the invalid PUSCH resource.

[0184] Based on the fact that the N-SBFD symbol indicates a valid resource, the terminal may determine that the PUSCH resource set in the N-SBFD symbol is the valid resource among the PUSCH resources set in the SBFD symbols and the PUSCH resources set in the N-SBFD symbols, and may perform a PUSCH transmission (e.g., a repeated PUSCH transmission) on the valid PUSCH resource. If the PUSCH resource set in the SBFD symbols is an invalid resource, the terminal may drop or postpone the PUSCH transmission on the invalid PUSCH resource.

[0185] Alternatively, resource validity information may indicate an invalid symbol type among the symbol types. For example, resource validity information may indicate that an SBFD symbol or an N-SBFD symbol is an invalid resource (e.g., an invalid symbol). Based on the fact that an SBFD symbol is indicated as an invalid resource, the terminal may determine that the PUSCH resource set in the N-SBFD symbols is a valid resource among the PUSCH resources set in the SBFD symbols and the PUSCH resources set in the N-SBFD symbols, and may perform a PUSCH transmission (e.g., a PUSCH repeat transmission) on the valid PUSCH resource. If the PUSCH resource set in the SBFD symbols is an invalid resource, the terminal may drop or postpone the PUSCH transmission on the invalid PUSCH resource.

[0186] Based on the fact that the N-SBFD symbol indicates an invalid resource, the terminal may determine that the PUSCH resource set in the SBFD symbols is a valid resource among the PUSCH resources set in the SBFD symbols and the PUSCH resources set in the N-SBFD symbols, and may perform a PUSCH transmission (e.g., a repeated PUSCH transmission) on the valid PUSCH resource. If the PUSCH resource set in the N-SBFD symbols is an invalid resource, the terminal may drop or postpone the PUSCH transmission on the invalid PUSCH resource.

[0187] ■ Proposal #2-3

[0188] An SBFD terminal may determine symbol validity differently based on operation settings according to the symbol type (e.g., SBFD Setting 1 or SBFD Setting 2). The criteria for determining symbol validity (e.g., conditions) may differ. When SBFD Setting 1 is applied, the terminal may perform channel and / or signal transmission and reception operations on symbols having the same symbol type. When SBFD Setting 1 is applied, the resource configuration constraints of the base station may be greater than those of the base station when SBFD Setting 2 is applied. When SBFD Setting 1 is applied, the terminal may determine all SBFD symbols as invalid symbols by considering the complexity of the communication system. When SBFD Setting 2 is applied, the terminal may assume all SBFD symbols as valid symbols and perform validity determination on SBFD symbols as necessary. When SBFD Setting 1 is applied, the criteria for determining symbol validity (e.g., conditions) may differ from the criteria for determining symbol validity (e.g., conditions) when SBFD Setting 2 is applied.

[0189] ■ Proposal #2-4

[0190] According to the TDD pattern and the UL subband configuration, the terminal can perform uplink transmission on DL resources and / or FL resources. DL resources and / or FL resources may be configured based on a specific pattern. When data transmission is performed on consecutive resources, propagation delay and / or interference may be reduced. If a symbol having a specific symbol type (e.g., SBFD symbol) does not exist in N symbols and / or N slots, the terminal may determine N-1 symbols and / or N-1 slots as invalid resources. N may be a natural number. N may be configured per subcarrier spacing (SCS). N may be defined in the technical specifications. Alternatively, the base station may transmit N to the terminal via signaling. The terminal may identify N through the base station's signaling. The signaling may be at least one of SI signaling, RRC signaling, MAC signaling, or PHY signaling.

[0191] ■ Proposal #2-5

[0192] Due to the configuration of the UL subband, switching between symbol types may occur frequently. For example, a symbol type may switch from an SBFD symbol to an N-SBFD symbol. Alternatively, a symbol type may switch from an N-SBFD symbol to an SBFD symbol. The time required for a symbol type switch (e.g., RF switching) at the terminal, the time required to ensure reception of the base station's downlink transmission (e.g., a time gap), etc., may be additionally defined. The aforementioned time may be referred to as the symbol type switching time. The time gap may be set on a per-symbol basis. The symbol type switching time may be the same as the symbol gap that guarantees the switching between the downlink and uplink according to the TDD pattern. The symbol type switching time may be set separately for an SBFD terminal. The base station may transmit information regarding the symbol type switching time to the terminal via signaling. The terminal may check information regarding the symbol type switching time through the base station's signaling. The signaling may be at least one of RRC signaling, MAC signaling, or PHY signaling. The terminal may determine that symbols are invalid from the time of the symbol type transition during the symbol type transition time. A symbol type transition time may be required for transitioning from an N-SBFD DL symbol to a UL symbol (e.g., an N-SBFD UL symbol). The terminal may determine that one or more SBFD symbols within the symbol type transition time among the SBFD symbols of the UL subband are invalid.

[0193] ■ Proposal #3

[0194] PUSCH repeated transmission can be performed based on a configured grant (CG). The base station can pre-allocate PUSCH resources for PUSCH repeated transmission to the terminal via signaling. The terminal can identify the PUSCH resources for PUSCH repeated transmission through the base station's signaling. The PUSCH resources may be resources that consider only TDD patterns (e.g., TDD UL / DL patterns). Within a slot, symbols may be set in the order of DL symbol → FL symbol → UL symbol. PUSCH resource information may be listed considering time resources based on the existing frame structure. A frequency offset for PUSCH transmission within the UL subband may be introduced. In PUSCH repeated transmission, the resource pattern resulting from the frequency offset may differ.

[0195] The base station can transmit legacy PUSCH resource information as well as SBFD PUSCH resource information for an SBFD terminal (e.g., PUSCH transmission in the UL subband) to the terminal via signaling. The terminal can receive legacy PUSCH resource information and SBFD PUSCH resource information via the base station's signaling. Each of the legacy PUSCH resource information and SBFD PUSCH resource information may be time domain resource allocation information. The legacy PUSCH resource information and SBFD PUSCH resource information may be configured in the form of a list.

[0196] If a resource indicated by DCI (e.g., a PUSCH resource) belongs to a UL subband, the terminal may expect PUSCH transmission from said resource. SBFD PUSCH resource information may be configured in the terminal, and at least one of the PUSCH resources indicated by the SBFD PUSCH resource information may not belong to a UL subband. In this case, the terminal may not expect PUSCH transmission from the entirety of the PUSCH resources, including at least one resource that does not belong to a UL subband.

[0197] A base station may transmit to a terminal not only SBFD PUSCH resource information but also an indicator (hereinafter referred to as an SBFD indicator) indicating whether the PUSCH resource indicated by the SBFD PUSCH resource information is being utilized. The SBFD indicator may be transmitted via an RRC message, MAC-CE, or DCI. The base station may transmit legacy PUSCH resource information and SBFD PUSCH resource information to the terminal, and may transmit to the terminal an SBFD indicator indicating the use of either the legacy PUSCH resource information or the SBFD PUSCH resource information. An SBFD indicator set to ON may indicate the use of SBFD PUSCH resource information. An SBFD indicator set to OFF may indicate the use of legacy PUSCH resource information.

[0198] Figure 14 is a conceptual diagram illustrating the PUSCH resource configuration.

[0199] Referring to FIG. 14, the PUSCH-TimeDomainResourceAllocationList may include a PUSCH-TimeDomainResourceAllocation_Normal and a PUSCH-TimeDomainResourceAllocation_SBFD. The PUSCH-TimeDomainResourceAllocation_Normal may refer to legacy PUSCH resource information. The PUSCH-TimeDomainResourceAllocation_SBFD may refer to SBFD PUSCH resource information. The PUSCH-TimeDomainResourceAllocation_Normal may indicate a PUSCH resource configured in N-SBFD symbols. The PUSCH-TimeDomainResourceAllocation_SBFD may indicate a PUSCH resource configured in SBFD symbols.

[0200] The base station may transmit legacy PUSCH resource information and SBFD PUSCH resource information to the terminal via signaling. The base station may instruct the terminal to use legacy PUSCH resource information or SBFD PUSCH resource information by transmitting an SBFD indicator. The terminal may receive legacy PUSCH resource information and SBFD PUSCH resource information via the base station's signaling and may use the PUSCH resource information indicated by the SBFD indicator received from the base station. Bit(s) indicating legacy time domain resource allocation (TDRA) included in the DCI may be used for the SBFD indicator. In other words, the TDRA field included in the DCI may be set as the SBFD indicator. The terminal may determine which PUSCH resource information to refer to based on the SBFD indicator. Alternatively, additional fields (e.g., additional bit(s)) may be defined in the existing DCI, and these additional fields may be used to instruct the use of SBFD PUSCH resource information. Alternatively, the terminal can determine which PUSCH resource information to refer to based on whether it supports SBFD.

[0201] Embodiments of the present disclosure may be applied to PUSCH resource allocation methods based on mapping type B of time domain resource allocation. Some or all of the embodiments of the present disclosure may also be applied to PUSCH resource allocation methods based on mapping type A of time domain resource allocation.

[0202] ■ Proposal #4

[0203] A counter for the number of PUSCH repeat transmissions can be associated with an uplink beam. An uplink can be associated with an SRS resource set. In PUSCH repeat type A, the unit of a PUSCH repeat transmission can be a PUSCH occupation. In PUSCH repeat type B, the unit of a PUSCH repeat transmission can be an actual repeat (e.g., a PUSCH actual repeat). PUSCH transmissions using a different beam than the one used for the PUSCH transmission in the first PUSCH occupation (e.g., a previous PUSCH occupation) or the first actual repeat (e.g., a previous actual repeat) can be counted.

[0204] In PUSCH repeat type B, multiple actual repeats may exist within a slot. Actual repeats may exist within SBFD symbols or N-SBFD symbols. Alternatively, actual repeats may exist across SBFD symbols and N-SBFD symbols. Legacy rules may apply to SBFD operations. Regardless of symbol type, PUSCH transmissions using a beam different from the beam used for the PUSCH transmission in the first PUSCH occlusion (e.g., previous PUSCH occlusion) or the first PUSCH repeat (e.g., previous PUSCH repeat) may be counted. Regardless of symbol type, the redundancy version (RV) in consecutive PUSCH occlusions or consecutive PUSCH repeats (e.g., actual repeats) may be determined based on existing rules.

[0205] The terminal may determine a resource for PUSCH transmission after determining the validity of transmittable symbols and / or transmittable slots. The SBFD terminal may be unable to perform PUSCH transmission on a PUSCH resource depending on the operation setting based on the symbol type (e.g., SBFD setting 1 or SBFD setting 2). An ambiguity issue may arise regarding the counting of PUSCH resources where PUSCH transmission was not performed due to the operation setting based on the symbol type. This ambiguity issue may arise due to a trade-off between delay and reliability.

[0206] If a transmittable PUSCH resource is allocated to the terminal but a PUSCH transmission is not performed from the said PUSCH resource due to operation settings based on the symbol type, the terminal may or may not count the number of repeated PUSCH transmissions. If a PUSCH transmission is not performed but the beam is changed, the terminal may or may not count the number of repeated PUSCH transmissions.

[0207] In this disclosure, a higher proposal (e.g., Proposal #1, Proposal #2, Proposal #3, Proposal #4) 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.

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

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

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

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

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

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

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

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

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

[0217] 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 information from a base station indicating PUSCH (physical uplink shared channel) repetition type A; A step of determining the validity of a first PUSCH resource for a PUSCH repeat transmission based on the PUSCH repeat type A, based on the fact that SBFD (subband full duplex) setting 2 is not indicated to the UE; and Based on the fact that the first PUSCH resource is an invalid PUSCH resource, the method includes the step of not performing a first PUSCH transmission on the invalid PUSCH resource. UE's method.

2. In Claim 1, The step of not performing the first PUSCH transmission on the above-mentioned invalid PUSCH resource is, Based on available slot counting set in the UE, the method includes the step of delaying the first PUSCH transmission in the invalid PUSCH resource, and Slots containing the above invalid PUSCH resources are not counted as available slots, UE's method.

3. In Claim 2, A step of determining the validity of a second PUSCH resource for the PUSCH repetition transmission based on the above PUSCH repetition type A; and The method further includes a step of determining whether to perform repeated PUSCH transmissions in the second PUSCH resource based on the result of determining the validity above, and Based on the fact that the type of symbols for which the second PUSCH resource is set is the same as the type of symbols for which the first PUSCH resource is set, the second PUSCH resource is determined to be a valid PUSCH resource, and Based on the fact that the type of symbols for which the second PUSCH resource is set is different from the type of symbols for which the first PUSCH resource is set, the second PUSCH resource is determined to be an invalid PUSCH resource. UE's method.

4. In Claim 1, The step of not performing the first PUSCH transmission on the above-mentioned invalid PUSCH resource is, Based on the fact that available slot counting is not set in the UE, the method includes the step of dropping a PUSCH transmission from the invalid PUSCH resource, and PUSCH transmissions dropped from the above invalid PUSCH resource are counted as PUSCH iterations, UE's method.

5. In Claim 1, The fact that the above SBFD setting 2 is not indicated to the above UE means that SBFD setting 1 is applied, UE's method.

6. In Claim 1, The method further includes the step of receiving information from the base station indicating a valid symbol type among the symbol types, The above valid symbol type is an SBFD symbol or an N(non)-SBFD symbol, UE's method.

7. In Claim 6, The step of determining the validity of the above-mentioned first PUSCH resource is, Based on the fact that the above SBFD symbol is indicated by the above valid symbol type, the step of determining the PUSCH resources set in the SBFD symbols as valid and determining the PUSCH resources set in the N-SBFD symbols as invalid UE's method.

8. In Claim 6, The step of determining the validity of the above-mentioned first PUSCH resource is, Based on the fact that the above N-SBFD symbol is indicated by the above valid symbol type, the step of determining the PUSCH resource set in the SBFD symbols as invalid and determining the PUSCH resource set in the N-SBFD symbols as valid, comprising UE's method.

9. In Claim 1, The step of determining the validity of the above-mentioned first PUSCH resource is, A step of determining the type of symbols for which the first PUSCH transmission was performed as a valid symbol type; and A step of determining the validity of the first PUSCH resource based on whether there is identity between the types of symbols for which the first PUSCH resource is set and the valid symbol types, UE's method.

10. In Claim 1, The step of determining the validity of the above-mentioned first PUSCH resource is, A step comprising determining the first PUSCH resource as invalid based on the fact that the first PUSCH resource is set across the SBFD symbol and the UL (uplink) symbol, UE's method.

11. In Claim 1, The step of determining the validity of the above-mentioned first PUSCH resource is, A step comprising determining the first PUSCH resource as invalid based on the fact that a portion of the first PUSCH resource does not belong to the UL subband in the frequency domain, UE's method.

12. In Claim 1, The step of determining the validity of the above-mentioned first PUSCH resource is, A step comprising determining the first PUSCH resource as invalid based on the fact that the gap between the DL (downlink) transmission prior to the first PUSCH resource and the first PUSCH resource in the time domain is smaller than the offset, UE's method.

13. In Claim 1, The step of determining the validity of the above-mentioned first PUSCH resource is, The method comprises the step of determining that the first PUSCH resource is invalid based on the fact that the first PUSCH resource includes at least one symbol that overlaps with an SSB symbol for SSB (synchronization signal block) transmission. UE's method.

14. As UE (user equipment), It includes at least one processor, wherein the at least one processor is the UE, Receive information from a base station indicating PUSCH (physical uplink shared channel) repetition type A; Based on the fact that SBFD (subband full duplex) setting 2 is not indicated to the UE, determine the validity of the first PUSCH resource for a PUSCH repeat transmission based on the PUSCH repeat type A; and Based on the fact that the first PUSCH resource is an invalid PUSCH resource, causing the first PUSCH transmission not to be performed on the invalid PUSCH resource, UE.

15. In Claim 14, The operation that causes the first PUSCH transmission not to be performed on the above-mentioned invalid PUSCH resource is that the at least one processor, the UE, Based on the available slot counting set in the UE, it causes the first PUSCH transmission to be delayed in the invalid PUSCH resource, and Slots containing the above invalid PUSCH resources are not counted as available slots, UE.

16. In Claim 15, The above at least one processor is the UE, Determining the validity of a second PUSCH resource for the transmission of the PUSCH repetition based on the above PUSCH repetition type A; and Based on the result of determining the validity above, it further causes to determine whether to perform repeated PUSCH transmissions in the second PUSCH resource, and Based on the fact that the type of symbols for which the second PUSCH resource is set is the same as the type of symbols for which the first PUSCH resource is set, the second PUSCH resource is determined to be a valid PUSCH resource, and Based on the fact that the type of symbols for which the second PUSCH resource is set is different from the type of symbols for which the first PUSCH resource is set, the second PUSCH resource is determined to be an invalid PUSCH resource. UE.

17. In Claim 14, The operation that causes the first PUSCH transmission not to be performed on the above-mentioned invalid PUSCH resource is that the at least one processor, the UE, Based on the fact that available slot counting is not set in the above UE, it causes to drop PUSCH transmissions from the above invalid PUSCH resource, and PUSCH transmissions dropped from the above invalid PUSCH resource are counted as PUSCH iterations, UE.

18. In Claim 14, The above at least one processor is the UE, It further causes receiving information from the base station indicating a valid symbol type among the symbol types, The above valid symbol type is an SBFD symbol or an N(non)-SBFD symbol, UE.

19. In Claim 18, The operation causing the above first PUSCH resource to be valid is that the at least one processor is the UE, Based on the fact that the above SBFD symbol is indicated by the above valid symbol type, cause to determine the PUSCH resources set in the SBFD symbols as valid and the PUSCH resources set in the N-SBFD symbols as invalid, or Based on the fact that the above N-SBFD symbol is indicated by the above valid symbol type, determining the PUSCH resources set in the SBFD symbols as invalid and causing the PUSCH resources set in the N-SBFD symbols to be determined as valid, UE.

20. In Claim 14, The operation causing the above first PUSCH resource to be valid is that the at least one processor is the UE, Determine the type of symbols for which the first PUSCH transmission was performed as a valid symbol type; and Causing to determine the validity of the first PUSCH resource based on whether there is identity between the types of symbols set by the first PUSCH resource and the valid symbol type, UE.

Images