WO2024210667A1 - Method and apparatus for repeatedly transmitting and receiving uplink data channel in full duplex communication - Google Patents

Abstract

The present embodiments provide a method by which a terminal transmits an uplink data channel in full duplex communication, comprising the steps of: receiving TDD configuration information and sub-band configuration information; receiving PUSCH configuration information including repeated transmission information of a PUSCH; determining a plurality of valid slots for repeatedly transmitting the PUSCH on the basis of the PUSCH configuration information; and transmitting the PUSCH through at least some slots from among the determined plurality of valid slots.

Description

Method and device for repeatedly transmitting and receiving uplink data channel in full-duplex communication

The present embodiments propose a method and device for repeatedly transmitting and receiving an uplink data channel in a next-generation wireless access network (hereinafter referred to as “NR [New Radio]”).

3GPP recently approved the "Study on New Radio Access Technology," a study item for research on the next-generation radio access technology (i.e., 5G radio access technology), and based on this, RAN WG1 is designing the frame structure, channel coding & modulation, waveform & multiple access scheme, etc. for NR (New Radio). NR is required to be designed to satisfy not only improved data transmission rate compared to LTE, but also various QoS requirements required for each segmented and specific usage scenario.

eMBB (enhancement Mobile BroadBand), mMTC (massive Machine Type Communication), and URLLC (Ultra Reliable and Low Latency Communications) have been defined as representative usage scenarios of NR, and a flexible frame structure design compared to LTE is required to satisfy the requirements of each usage scenario.

Since each usage scenario has different requirements for data rates, latency, reliability, coverage, etc., there is a need for a method to efficiently multiplex radio resource units based on different numerologies (e.g., subcarrier spacing, subframe, TTI (Transmission Time Interval), etc.) to efficiently satisfy the requirements of each usage scenario through the frequency band that constitutes an arbitrary NR system.

As part of this aspect, a specific design is required to efficiently perform repetitive transmission and reception of uplink data channels in symbols where full-duplex communication is applied in wireless networks.

Embodiments of the present disclosure can provide a method and device for repeatedly transmitting and receiving an uplink data channel in full-duplex communication.

In one aspect, the present embodiments provide a method for transmitting an uplink data channel (Physical Uplink Shared Channel; PUSCH) by a terminal in full duplex communication, the method comprising the steps of: receiving TDD (Time Division Duplex) configuration information and subband configuration information; receiving PUSCH configuration information including repeated transmission information of the PUSCH; determining a plurality of available slots for repeatedly transmitting the PUSCH based on the PUSCH configuration information; and transmitting the PUSCH through at least some of the determined plurality of available slots, wherein the plurality of available slots include at least one of slots in which symbols allocated for PUSCH transmission in each slot are all set to uplink (UL) or flexible non-SBFD (subband full duplex) symbols by TDD configuration information that do not include SSB reception symbols, or slots set to downlink (DL) by TDD configuration information and reset to SBFD symbols in which an uplink subband is configured by subband configuration information.

In another aspect, the present embodiments provide a method for a base station to receive an uplink data channel (Physical Uplink Shared Channel; PUSCH) in a full duplex communication, the method including the steps of transmitting TDD (Time Division Duplex) configuration information and subband configuration information, transmitting PUSCH configuration information including repeated transmission information of the PUSCH, setting whether to activate repeated transmission of the PUSCH through slots of different slot types, and receiving the PUSCH through at least some of slots among a plurality of available slots determined based on whether to activate repeated transmission of the PUSCH, wherein the plurality of available slots include at least one of slots in which symbols allocated for PUSCH transmission in each slot are all set to uplink (UL) or flexible non-SBFD (subband full duplex) symbols by TDD configuration information that do not include SSB reception symbols, or slots set to downlink (DL) by TDD configuration information and reset to SBFD symbols in which an uplink subband is configured by subband configuration information.

In another aspect, the present embodiments provide a terminal for transmitting an uplink data channel (Physical Uplink Shared Channel; PUSCH) in full duplex communication, comprising a transmitter, a receiver, and a control unit for controlling operations of the transmitter and the receiver, wherein the control unit receives TDD (Time Division Duplex) configuration information and subband configuration information, receives PUSCH configuration information including repeated transmission information of the PUSCH, determines a plurality of available slots for repeatedly transmitting the PUSCH based on the PUSCH configuration information, and transmits the PUSCH through at least some of the determined plurality of available slots, and the plurality of available slots include at least one of slots in which symbols allocated for PUSCH transmission in each slot are all set to uplink (UL) or flexible non-SBFD (subband full duplex) symbols by TDD configuration information that do not include SSB reception symbols, or slots set to downlink (DL) by TDD configuration information and reset to SBFD symbols in which an uplink subband is configured by subband configuration information. A terminal including the above can be provided.

In another aspect, the present embodiments provide a base station for receiving an uplink data channel (Physical Uplink Shared Channel; PUSCH) in full duplex communication, comprising a transmitter, a receiver, and a control unit for controlling operations of the transmitter and the receiver, wherein the control unit transmits TDD (Time Division Duplex) configuration information and subband configuration information, transmits PUSCH configuration information including repeated transmission information of the PUSCH, sets whether to activate repeated transmission of the PUSCH through slots of different slot types, and receives the PUSCH through at least some slots among a plurality of available slots determined based on whether to activate repeated transmission of the PUSCH, wherein the plurality of available slots are slots in which all symbols allocated for PUSCH transmission in each slot are set to uplink (UL) or flexible non-SBFD (subband full duplex) symbols by TDD configuration information that do not include SSB reception symbols, or SBFD symbols set to downlink (DL) by TDD configuration information and an uplink subband is configured by subband configuration information. A base station can be provided that includes at least one of the slots reset with a symbol.

According to the present embodiments, a method and device for efficiently performing repeated transmission and reception of an uplink data channel in a slot or symbol to which full-duplex communication is applied can be provided.

FIG. 1 is a diagram briefly illustrating the structure of an NR wireless communication system to which the present embodiment can be applied.

FIG. 2 is a drawing for explaining a frame structure in an NR system to which the present embodiment can be applied.

FIG. 3 is a diagram for explaining a resource grid supported by a wireless access technology to which the present embodiment can be applied.

FIG. 4 is a diagram for explaining a bandwidth part supported by a wireless access technology to which the present embodiment can be applied.

FIG. 5 is a diagram exemplarily illustrating a synchronization signal block in a wireless access technology to which the present embodiment can be applied.

FIG. 6 is a diagram for explaining a random access procedure in a wireless access technology to which the present embodiment can be applied.

Figure 7 is a drawing for explaining CORESET.

FIG. 8 is a diagram illustrating a procedure for a terminal to repeatedly transmit an uplink data channel according to one embodiment.

FIG. 9 is a diagram illustrating a procedure for a base station to repeatedly receive an uplink data channel according to one embodiment.

FIGS. 10 and 11 are diagrams for explaining a TDD frame in which an uplink subband is set in a downlink slot according to one embodiment.

Fig. 12 is a drawing showing the configuration of a terminal according to another embodiment.

Fig. 13 is a diagram showing the configuration of a base station according to another embodiment.

Hereinafter, some embodiments of the present disclosure will be described in detail with reference to exemplary drawings. When adding reference numerals to components of each drawing, the same components may have the same numerals as much as possible even if they are shown in different drawings. In addition, when describing the present embodiments, if it is determined that a specific description of a related known configuration or function may obscure the gist of the technical idea of the present invention, the detailed description thereof may be omitted. When "includes," "has," "consists of," etc. are used in this specification, other parts may be added unless "only" is used. When a component is expressed in the singular, it may include a case where it includes plural unless there is a special explicit description.

Additionally, in describing components of the present disclosure, terms such as first, second, A, B, (a), (b), etc. may be used. These terms are only intended to distinguish the components from other components, and the nature, order, sequence, or number of the components are not limited by the terms.

In a description of the positional relationship of components, when it is described that two or more components are "connected", "combined" or "connected", it should be understood that the two or more components may be directly "connected", "combined" or "connected", but the two or more components and another component may be further "interposed" to be "connected", "combined" or "connected". Here, the other component may be included in one or more of the two or more components that are "connected", "combined" or "connected" to each other.

In the description of the temporal flow relationship related to components, operation methods, or manufacturing methods, for example, when the temporal chronological relationship or the chronological flow relationship is described as "after", "following", "next to", or "before", it can also include cases where it is not continuous, as long as "immediately" or "directly" is not used.

Meanwhile, when a numerical value or its corresponding information (e.g., level, etc.) for a component is mentioned, even if there is no separate explicit description, the numerical value or its corresponding information may be interpreted as including an error range that may occur due to various factors (e.g., process factors, internal or external impact, noise, etc.).

The wireless communication system in this specification means a system for providing various communication services, such as voice and data packets, using wireless resources, and may include a terminal, a base station, or a core network.

The embodiments disclosed below can be applied to wireless communication systems using various wireless access technologies. For example, the embodiments can be applied to various wireless access technologies such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (timedivision multiple access), OFDMA (orthogonal frequency division multiple access), SC-FDMA (singlecarrier frequency division multiple access), or NOMA (non-orthogonal multiple access). In addition, the wireless access technology may mean not only a specific access technology, but also each generation communication technology established by various communication agreement organizations such as 3GPP, 3GPP2, WiFi, Bluetooth, IEEE, and ITU. For example, CDMA can be implemented with a wireless technology such as UTRA (universal terrestrial radio access) or CDMA2000. TDMA can be implemented with a wireless technology such as GSM (global system for mobile communications)/GPRS (general packet radio service)/EDGE (enhanced datarates for GSM evolution). OFDMA can be implemented in wireless technologies such as IEEE (Institute of Electrical and Electronic Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, E-UTRA (evolved UTRA), etc. IEEE 802.16m is an evolution of IEEE 802.16e and provides backward compatibility with systems based on IEEE 802.16e. UTRA is a part of UMTS (universal mobile telecommunications system). 3GPP (3rd generation partnership project) LTE (long term evolution) is a part of E-UMTS (evolved UMTS) that uses E-UTRA (evolved-UMTSterrestrial radio access), and employs OFDMA in downlink and SC-FDMA in uplink. In this way, the present embodiments can be applied to wireless access technologies that are currently disclosed or commercialized, and can also be applied to wireless access technologies that are currently under development or will be developed in the future.

Meanwhile, the terminal in this specification is a comprehensive concept meaning a device including a wireless communication module that performs communication with a base station in a wireless communication system, and should be interpreted as a concept including not only UE (User Equipment) in WCDMA, LTE, NR, HSPA, and IMT-2020 (5G or New Radio), but also MS (Mobile Station), UT (User Terminal), SS (Subscriber Station), and wireless device in GSM. In addition, the terminal may be a user portable device such as a smart phone depending on the usage type, and in a V2X communication system, it may mean a vehicle, a device including a wireless communication module in a vehicle, etc. In addition, in the case of a Machine Type Communication system, it may mean an MTC terminal, M2M terminal, URLLC terminal, etc. equipped with a communication module to perform machine type communication.

The base station or cell in this specification refers to an end that communicates with a terminal in terms of a network, and includes a Node-B, an evolved Node-B (eNB), a gNode-B (gNB), a Low Power Node (LPN), a sector, a site, various types of antennas, a Base Transceiver System (BTS), an Access Point, points (e.g., a transmission point, a reception point, a transceiver point), a relay node, a mega cell, a macro cell, a micro cell, a pico cell, a femto cell, a Remote Radio Head (RRH), a Radio Unit (RU), a small cell, and various coverage areas. In addition, a cell may mean a Bandwidth Part (BWP) in a frequency domain. For example, a serving cell may mean an Activation BWP of a terminal.

The various cells listed above have a base station that controls one or more cells, so the base station can be interpreted in two meanings. 1) It can be a device itself that provides a mega cell, a macro cell, a micro cell, a pico cell, a femto cell, or a small cell in relation to a wireless area, or 2) It can indicate the wireless area itself. In 1), all devices that provide a given wireless area are controlled by the same entity or interact to cooperatively configure the wireless area are all indicated as a base station. Depending on the configuration method of the wireless area, a point, a transceiver point, a transmission point, a reception point, etc. become an embodiment of a base station. In 2), the wireless area itself that receives or transmits a signal from the perspective of a user terminal or a neighboring base station can also be indicated as a base station.

In this specification, a cell may mean a component carrier having coverage of a signal transmitted from a transmission/reception point or coverage of a signal transmitted from a transmission/reception point, or the transmission/reception point itself.

Uplink (UL, or uplink) refers to a method of transmitting and receiving data from a terminal to a base station, and downlink (DL, or downlink) refers to a method of transmitting and receiving data from a base station to a terminal. Downlink may refer to communication or a communication path from multiple transmission/reception points to a terminal, and uplink may refer to communication or a communication path from a terminal to multiple transmission/reception points. In this case, in the downlink, the transmitter may be part of the multiple transmission/reception points, and the receiver may be part of the terminal. In addition, in the uplink, the transmitter may be part of the terminal, and the receiver may be part of the multiple transmission/reception points.

Uplink and downlink transmit and receive control information through control channels such as PDCCH (Physical Downlink Control CHannel) and PUCCH (Physical Uplink Control CHannel), and transmit and receive data by configuring data channels such as PDSCH (Physical Downlink Shared CHannel) and PUSCH (Physical Uplink Shared CHannel). Hereinafter, the situation in which signals are transmitted and received through channels such as PUCCH, PUSCH, PDCCH, and PDSCH is also expressed in the form of 'transmitting and receiving PUCCH, PUSCH, PDCCH, and PDSCH'.

For clarity of explanation, the technical idea of this technology is described below mainly with reference to the 3GPP LTE/LTE-A/NR (New RAT) communication system, but the technical features of this technology are not limited to the communication system.

After studying 4G (4th-Generation) communication technology, 3GPP develops 5G (5th-Generation) communication technology to meet the requirements of the next-generation wireless access technology of ITU-R. Specifically, 3GPP develops LTE-A pro, which enhances LTE-Advanced technology to meet the requirements of ITU-R, as a 5G communication technology, and NR, a new communication technology separate from 4G communication technology. Both LTE-A pro and NR refer to 5G communication technology, and in the following, 5G communication technology is explained with NR as the center, unless a specific communication technology is specified.

The operating scenario in NR defines various operation scenarios by adding considerations for satellites, automobiles, and new verticals to the existing 4G LTE scenario, and supports the eMBB (Enhanced Mobile Broadband) scenario in terms of service, the mMTC (Massive Machine Communication) scenario that has high terminal density but is deployed over a wide area and requires low data rate and asynchronous access, and the URLLC (Ultra Reliability and Low Latency) scenario that requires high responsiveness and reliability and can support high-speed mobility.

To satisfy these scenarios, NR introduces a wireless communication system that applies new waveform and frame structure technologies, low latency technologies, ultra-high frequency band (mmWave) support technologies, and forward compatibility technologies. In particular, the NR system presents various technological changes in terms of flexibility to provide forward compatibility. The main technological features of NR are explained below with reference to the drawings.

<NR System General>

Figure 1 is a schematic diagram illustrating the structure of an NR system to which the present embodiment can be applied.

Referring to Fig. 1, the NR system is divided into 5GC (5G Core Network) and NR-RAN parts, and the NG-RAN is composed of gNBs and ng-eNBs that provide user plane (SDAP/PDCP/RLC/MAC/PHY) and control plane (RRC) protocol termination for UE (User Equipment). The gNBs or the gNBs and ng-eNBs are interconnected via the Xn interface. The gNBs and ng-eNBs are each connected to the 5GC via the NG interface. The 5GC can be configured to include an AMF (Access and Mobility Management Function) that is responsible for the control plane such as terminal access and mobility control functions, and a UPF (User Plane Function) that is responsible for the control function for user data. NR includes support for both frequency bands below 6 GHz (FR1, Frequency Range 1) and frequency bands above 6 GHz (FR2, Frequency Range 2).

gNB refers to a base station that provides NR user plane and control plane protocol termination to terminals, and ng-eNB refers to a base station that provides E-UTRA user plane and control plane protocol termination to terminals. The base station described in this specification should be understood to encompass gNB and ng-eNB, and may also be used to refer to gNB or ng-eNB separately as needed.

<NR Waveform, Numerology and Frame Structure>

NR uses CP-OFDM waveforms with cyclic prefix for downlink transmission, and CP-OFDM or DFT-s-OFDM for uplink transmission. OFDM technology is easy to combine with MIMO (Multiple Input Multiple Output) and has the advantage of being able to use low-complexity receivers along with high frequency efficiency.

Meanwhile, in NR, since the requirements for data rate, delay rate, coverage, etc. are different for each of the three scenarios mentioned above, it is necessary to efficiently satisfy the requirements for each scenario through the frequency band that constitutes an arbitrary NR system. To this end, a technology for efficiently multiplexing wireless resources based on multiple different numerologies has been proposed.

Specifically, the NR transmission numerology is determined based on the sub-carrier spacing and the cyclic prefix (CP), and is exponentially changed using the μ value as an exponent value of 2 based on 15 kHz, as shown in Table 1 below.

μ Subcarrier spacing Cyclic prefix Supported for data Supported for synch 0 15 Normal Yes Yes 1 30 Normal Yes Yes 2 60 Normal, Extended Yes No 3 120 Normal Yes Yes 4 240 Normal No Yes

As shown in Table 1 above, the numerology of NR can be divided into five types according to the subcarrier spacing. This is different from the subcarrier spacing of LTE, one of the 4G communication technologies, which is fixed to 15 kHz. Specifically, the subcarrier spacings used for data transmission in NR are 15, 30, 60, and 120 kHz, and the subcarrier spacings used for synchronization signal transmission are 15, 30, 12, and 240 kHz. In addition, the extended CP is applied only to the 60 kHz subcarrier spacing. Meanwhile, the frame structure in NR is defined as a frame with a length of 10 ms, which consists of 10 subframes with the same length of 1 ms. One frame can be divided into half frames of 5 ms, and each half frame includes 5 subframes. In the case of a 15 kHz subcarrier spacing, one subframe consists of one slot, and each slot consists of 14 OFDM symbols. FIG. 2 is a diagram for explaining a frame structure in an NR system to which the present embodiment can be applied. Referring to FIG. 2, a slot is fixedly composed of 14 OFDM symbols in the case of a normal CP, but the length of the slot in the time domain may vary depending on the subcarrier spacing. For example, in the case of a numerology having a 15 kHz subcarrier spacing, a slot is composed of 1 ms, which is the same length as a subframe. In contrast, in the case of a numerology having a 30 kHz subcarrier spacing, a slot is composed of 14 OFDM symbols, but two slots can be included in one subframe with a length of 0.5 ms. That is, a subframe and a frame are defined with a fixed time length, and a slot is defined by the number of symbols, so the time length may vary depending on the subcarrier spacing.

Meanwhile, NR defines the basic unit of scheduling as a slot, and also introduces a mini-slot (or sub-slot, or non-slot based schedule) to reduce transmission delay in the wireless section. Using a wide sub-carrier interval reduces the length of one slot inversely, so transmission delay in the wireless section can be reduced. Mini-slots (or sub-slots) are for efficient support of URLLC scenarios, and scheduling is possible in units of 2, 4, and 7 symbols.

In addition, unlike LTE, NR defines uplink and downlink resource allocation at the symbol level within a single slot. In order to reduce HARQ delay, a slot structure that can transmit HARQ ACK/NACK directly within a transmission slot is defined, and this slot structure is named and explained as a self-contained structure.

NR is designed to support a total of 256 slot formats, of which 62 slot formats are used in 3GPP Rel-15. In addition, it supports a common frame structure that configures an FDD or TDD frame through various combinations of slots. For example, it supports a slot structure in which all symbols of a slot are set to downlink, a slot structure in which all symbols are set to uplink, and a slot structure in which downlink symbols and uplink symbols are combined. In addition, NR supports data transmission being distributed and scheduled to one or more slots. Therefore, a base station can inform a UE whether a slot is a downlink slot, an uplink slot, or a flexible slot using a slot format indicator (SFI). A base station can indicate a slot format by indicating an index of a table configured through UE-specific RRC signaling using SFI, and can also indicate it dynamically through DCI (Downlink Control Information) or statically or semi-statically through RRC.

<NR Physical Resources>

In relation to physical resources in NR, antenna ports, resource grids, resource elements, resource blocks, and bandwidth parts are considered.

Antenna ports are defined such that the channel through which a symbol on an antenna port is carried can be inferred from the channel through which another symbol on the same antenna port is carried. Two antenna ports are said to be in a QC/QCL (quasi co-located or quasi co-location) relationship if large-scale properties of the channel through which a symbol on one antenna port is carried can be inferred from the channel through which a symbol on the other antenna port is carried. Here, the large-scale properties include one or more of delay spread, Doppler spread, frequency shift, average received power, and received timing.

FIG. 3 is a diagram for explaining a resource grid supported by a wireless access technology to which the present embodiment can be applied.

Referring to FIG. 3, a resource grid may exist for each numeral because NR supports multiple numerals in the same carrier. In addition, a resource grid may exist for each antenna port, subcarrier spacing, and transmission direction.

A resource block consists of 12 subcarriers and is defined only in the frequency domain. In addition, a resource element consists of one OFDM symbol and one subcarrier. Therefore, as shown in Fig. 3, the size of one resource block can vary depending on the subcarrier spacing. In addition, NR defines "Point A", which serves as a common reference point for the resource block grid, common resource blocks, virtual resource blocks, etc.

FIG. 4 is a diagram for explaining a bandwidth part supported by a wireless access technology to which the present embodiment can be applied.

In NR, unlike LTE where the carrier bandwidth is fixed at 20 MHz, the maximum carrier bandwidth is set from 50 MHz to 400 MHz for each subcarrier interval. Therefore, it is not assumed that all terminals use all of this carrier bandwidth. Accordingly, in NR, as illustrated in Fig. 4, a bandwidth part (BWP) can be designated within the carrier bandwidth for use by the terminal. In addition, a bandwidth part is linked to one numerology and consists of a subset of consecutive common resource blocks, and can be dynamically activated over time. A terminal is configured with up to four bandwidth parts for each of the uplink and downlink, and data is transmitted and received using the bandwidth part activated at a given time.

In the case of a paired spectrum, the uplink and downlink bandwidth parts are set independently, and in the case of an unpaired spectrum, the bandwidth parts of the downlink and uplink are set as pairs so that they can share a center frequency to prevent unnecessary frequency re-tuning between downlink and uplink operations.

<NR Initial Access>

In NR, a terminal performs cell search and random access procedures to connect to a base station and perform communication.

Cell search is a procedure in which a terminal synchronizes to a cell of a corresponding base station, obtains a physical layer cell ID, and obtains system information using a synchronization signal block (SSB) transmitted by the base station.

FIG. 5 is a diagram exemplarily illustrating a synchronization signal block in a wireless access technology to which the present embodiment can be applied.

Referring to FIG. 5, the SSB is composed of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS), each occupying 1 symbol and 127 subcarriers, and a PBCH spanning 3 OFDM symbols and 240 subcarriers.

The terminal receives SSB by monitoring SSB in the time and frequency domain.

SSB can be transmitted up to 64 times during 5ms. Multiple SSBs are transmitted with different transmission beams within 5ms, and the terminal performs detection assuming that SSBs are transmitted every 20ms based on a specific beam used for transmission. The number of beams that can be used for SSB transmission within 5ms can increase as the frequency band increases. For example, up to 4 SSB beams can be transmitted below 3GHz, up to 8 different beams can be used for SSB transmission in the frequency band of 3 to 6GHz, and up to 64 different beams can be used for SSB transmission in the frequency band of 6GHz or higher.

SSB contains two in one slot, and the start symbol and repetition number within the slot are determined as follows depending on the subcarrier spacing.

Meanwhile, SSB, unlike SS of conventional LTE, is not transmitted at the center frequency of the carrier bandwidth. That is, SSB can be transmitted even in a location other than the center of the system band, and multiple SSBs can be transmitted on the frequency domain when wideband operation is supported. Accordingly, the terminal monitors SSB using the synchronization raster, which is a candidate frequency location for monitoring SSB. The carrier raster and synchronization raster, which are center frequency location information of the channel for initial access, are newly defined in NR, and the synchronization raster can support fast SSB search of the terminal because the frequency interval of the synchronization raster is set wider than that of the carrier raster.

A terminal can obtain a MIB through a PBCH of an SSB. The MIB (Master Information Block) includes minimum information for the terminal to receive remaining system information (RMSI, Remaining Minimum System Information) broadcast by the network. In addition, the PBCH may include information on a position of a first DM-RS symbol in the time domain, information for the terminal to monitor SIB1 (e.g., SIB1 numerology information, information related to SIB1 CORESET, search space information, PDCCH related parameter information, etc.), offset information between a common resource block and an SSB (the absolute position of an SSB within a carrier is transmitted through SIB1), etc. Here, the SIB1 numerology information is equally applied to some messages used in a random access procedure for accessing a base station after the terminal completes a cell search procedure. For example, the numerology information of SIB1 may be applied to at least one of messages 1 to 4 for the random access procedure.

The aforementioned RMSI may mean SIB1 (System Information Block 1), and SIB1 is broadcasted periodically (ex, 160 ms) in the cell. SIB1 includes information required for the terminal to perform an initial random access procedure, and is transmitted periodically through PDSCH. In order for the terminal to receive SIB1, it must receive numerology information used for transmitting SIB1 and CORESET (Control Resource Set) information used for scheduling SIB1 through PBCH. The terminal checks scheduling information for SIB1 using SI-RNTI in CORESET, and acquires SIB1 on PDSCH according to the scheduling information. The remaining SIBs except SIB1 may be transmitted periodically or may be transmitted according to the request of the terminal.

FIG. 6 is a diagram for explaining a random access procedure in a wireless access technology to which the present embodiment can be applied.

Referring to FIG. 6, when cell search is completed, the terminal transmits a random access preamble for random access to the base station. The random access preamble is transmitted through PRACH. Specifically, the random access preamble is transmitted to the base station through PRACH, which consists of consecutive radio resources in a specific slot that is repeated periodically. In general, when the terminal initially accesses a cell, a contention-based random access procedure is performed, and when random access is performed for beam failure recovery (BFR), a non-contention-based random access procedure is performed.

A terminal receives a random access response to a transmitted random access preamble. The random access response may include a random access preamble identifier (ID), an UL Grant (uplink radio resource), a temporary C-RNTI (Temporary Cell - Radio Network Temporary Identifier) and a TAC (Time Alignment Command). Since one random access response may include random access response information for one or more terminals, the random access preamble identifier may be included to indicate to which terminal the included UL Grant, temporary C-RNTI and TAC are valid. The random access preamble identifier may be an identifier for a random access preamble received by a base station. The TAC may be included as information for the terminal to adjust uplink synchronization. The random access response may be indicated by a random access identifier on a PDCCH, i.e., an RA-RNTI (Random Access - Radio Network Temporary Identifier).

The terminal that receives a valid random access response processes the information contained in the random access response and performs scheduled transmission to the base station. For example, the terminal applies TAC and stores a temporary C-RNTI. In addition, it transmits data stored in the terminal's buffer or newly generated data to the base station using the UL Grant. In this case, information that can identify the terminal must be included.

Finally, the terminal receives a downlink message for contention resolution.

<NR CORESET>

The downlink control channel in NR is transmitted in a CORESET (Control Resource Set) with a length of 1 to 3 symbols, and transmits uplink/downlink scheduling information, SFI (Slot format Index), and TPC (Transmit Power Control) information.

In order to secure the flexibility of the system, NR introduces the CORESET concept. CORESET (Control Resource Set) means time-frequency resources for downlink control signals. A terminal can decode control channel candidates using one or more search spaces in the CORESET time-frequency resources. A QCL (Quasi CoLocation) assumption is set for each CORESET, and this is used for the purpose of informing the characteristics of the analog beam direction in addition to the delay spread, Doppler spread, Doppler shift, and average delay, which are the characteristics assumed by the conventional QCL.

Figure 7 is a drawing for explaining CORESET.

Referring to FIG. 7, a CORESET can exist in various forms within a carrier bandwidth within one slot, and a CORESET can consist of a maximum of three OFDM symbols in the time domain. In addition, a CORESET is defined as a multiple of six resource blocks up to the carrier bandwidth in the frequency domain.

The first CORESET is indicated via MIB as part of the initial bandwidth part configuration to enable receiving additional configuration information and system information from the network. After establishing a connection with the base station, the terminal can receive and configure one or more CORESET information via RRC signaling.

Wider bandwidth operations

In the case of the existing LTE system, scalable bandwidth operation was supported for an arbitrary LTC CC (Component Carrier). That is, depending on the frequency deployment scenario, an arbitrary LTE operator could configure a bandwidth of a minimum of 1.4 MHz and a maximum of 20 MHz when configuring an LTE CC, and a normal LTE terminal supported a transmission/reception capability of 20 MHz bandwidth for an LTE CC.

However, in the case of NR, the design is made to support NR terminals having different transmit/receive bandwidth capabilities through a single wideband NR CC, and accordingly, one or more bandwidth parts (BWPs, bandwidth part(s)) consisting of segmented bandwidths are configured for any NR CC, and it is required to support flexible wider bandwidth operation through different bandwidth part configurations and activations for each terminal.

Specifically, in NR, one or more bandwidth parts can be configured through one serving cell configured from a terminal perspective, and the terminal is defined to activate one downlink bandwidth part (DL bandwidth part) and one uplink bandwidth part (UL bandwidth part) in the serving cell to use them for uplink/downlink data transmission and reception. In addition, in the case where multiple serving cells are configured for the terminal, that is, for the terminal to which CA is applied, it is defined to activate one downlink bandwidth part and/or uplink bandwidth part for each serving cell to use the radio resources of the serving cell to use them for uplink/downlink data transmission and reception.

Specifically, an initial bandwidth part for an initial access procedure of a UE in a given serving cell is defined, one or more UE-specific bandwidth part(s) are configured for each UE through dedicated RRC signaling, and a default bandwidth part for a fallback operation can also be defined for each UE.

However, although it can be defined that multiple downlink and/or uplink bandwidth parts can be activated and used simultaneously depending on the capability and bandwidth part(s) configuration of the terminal in any serving cell, in NR rel-15, it is defined that only one downlink bandwidth part (DL bandwidth part) and one uplink bandwidth part (UL bandwidth part) can be activated and used by any terminal at any time.

In this specification, frequencies, frames, subframes, resources, resource blocks, regions, bands, subbands, control channels, data channels, synchronization signals, various reference signals, various signals or various messages related to NR (New Radio) may be interpreted as having past or present meanings or various meanings used in the future.

Below, a method for a terminal to repeatedly transmit an uplink data channel in full duplex communication will be described with reference to related drawings.

FIG. 8 is a diagram illustrating a procedure (800) in which a terminal repeatedly transmits an uplink data channel according to one embodiment.

Referring to FIG. 8, the terminal can receive TDD (Time Division Duplex) configuration information and subband configuration information (S810).

TDD (Time Division Duplex) is a method of using time-interval radio resources by dividing them into downlink slots and uplink slots, and a terminal can receive TDD configuration information from a base station to determine the format of a symbol in a slot. In this case, the TDD configuration information can include configuration information regarding the format of a slot and configuration information for determining the format of a symbol in a slot, and the information can be received through upper layer signaling or physical layer (L1) signaling.

That is, a downlink symbol, an uplink symbol, and a flexible symbol whose transmission direction is not determined can be set for a certain period through an RRC message for setting the corresponding UL-DL slot. In addition, the terminal can receive terminal-specific RRC signaling for reallocating flexible symbols among the symbols set through cell-specific RRC signaling to uplink symbols, downlink symbols, or flexible symbols for each terminal.

Alternatively, the UE may be instructed of a dynamic slot format via a UE-group common PDCCH. As an example, the UE may be instructed of a slot format dynamically via DCI format 2_0.

Full-duplex communication is a technology in which a base station performs downlink transmission and uplink reception simultaneously on the same radio resources. A terminal can also perform downlink reception and uplink transmission simultaneously. When a base station supports full-duplex communication based on subband non-overlapping, a specific frequency resource within the same symbol in a TDD carrier can be used for downlink transmission, and other frequency resources can be used for uplink reception. That is, within a TDD carrier, some frequency resources in a certain downlink slot or downlink symbol can be utilized for uplink transmission of a terminal, or can be configured to be utilized as a flexible symbol for downlink/uplink transition.

To this end, the terminal may receive subband configuration information for full-duplex communication. That is, the terminal may receive configuration information for configuring a downlink subband in an uplink slot or for configuring an uplink subband in a downlink slot. The subband configuration information may include information about a frequency domain in which an uplink subband or a downlink subband is configured and information about a time domain. Alternatively, the subband configuration information may include information about a frequency domain in which a guard band is configured and information about a time domain.

The subband configuration information can be transmitted through a broadcasting method that is transmitted to all terminals in the cell. Alternatively, it can be transmitted through a multicasting method that is transmitted to terminals that require full-duplex communication mode operation, or a unicasting method that is transmitted only to specific terminals. The terminal can receive the corresponding configuration information according to the set method.

For example, when an uplink subband is set in a downlink slot, the uplink subband may be set at the center of the corresponding frequency band, or may be set at the edge of the corresponding frequency band. In this case, a guard band may be set between the uplink subband and the downlink subband in the corresponding slot (e.g., a frequency band other than the uplink subband and the guard band among the frequency bands allocated to the terminal).

In this way, a downlink slot or symbol including an uplink subband and an uplink slot or symbol including a downlink subband are referred to as a SBFD (subband full duplex) slot or SBFD symbol in the present disclosure. However, the term SBFD is for convenience of explanation, and the scope of the present disclosure is not limited by this term, and may be referred to by another term as needed. In addition, a slot that is not an SBFD slot, i.e., a slot in which subbands of different transmission directions are not configured, may be referred to as a non-SBFD slot.

That is, a downlink slot or downlink symbol configured for a terminal may include an SBFD symbol in which an uplink subband for full-duplex communication is configured. In other words, an uplink subband may be configured for at least some of the downlink slots or downlink symbols configured for the terminal, and in this case, an uplink subband, a downlink subband, and/or a guard band may be configured for the corresponding slot or symbol.

Similarly, an uplink slot or uplink symbol configured for a terminal may include an SBFD symbol in which a downlink subband for full-duplex communication is configured. In other words, a downlink subband may be configured for at least some of the uplink slots or uplink symbols configured for the terminal, and in this case, an uplink subband, a downlink subband, and/or a guard band may be configured for the corresponding slot or symbol.

Referring again to FIG. 8, the terminal can receive PUSCH configuration information including PUSCH repetition transmission information (S820).

The terminal may receive PUSCH configuration information from the base station that sets or instructs repeated transmission of the PUSCH. In one example, repeated transmission of the PUSCH may mean that one PUSCH transmission is performed over multiple slots. For example, this may include cases where PUSCH repetition is set or instructed, TBoMS (TB processing over multiple slots) is set or instructed, or multiple PUSCH transmissions are scheduled over one DCI.

For example, the UE may receive, from the eNB, a configuration of pusch-AggregationFactor, which is an RRC parameter for semi-statically configuring repeated transmission for PUSCH. Alternatively, the UE may be dynamically instructed to perform repeated transmission for PUSCH by the eNB through a time domain resource allocation (TDRA) indication information field of an uplink grant (UL grant). That is, the eNB may indicate time domain resource allocation information of one of the TDRA tables configured by PUSCH-TimeDomainResourceAllocationList through the TDRA indication information field of the uplink grant. In this case, if the time domain resource allocation information includes repetition count information or slot count information in TBoMS, the eNB may indicate one or more PUSCH repetitions according to the corresponding setting value. For example, it is possible to indicate PUSCH repetitions of 1, 2, 3, 4, 7, 8, 12, 16, 24, 28, and 32. That is, the terminal can receive repetition count setting information for PUSCH repetitions through RRC signaling or through TDRA in DCI format.

Depending on the mapping type of a PUSCH transmission, PUSCH repetition can be classified into slot-based PUSCH repetition type A and non-slot-based, i.e., mini-slot or sub-slot-based PUSCH repetition type B. Hereinafter, PUSCH repetition can include both PUSCH repetition type A and PUSCH repetition type B.

In this way, through PUSCH configuration information, one PUSCH transmission can be set or instructed to be performed through multiple slots.

Referring again to FIG. 8, the terminal determines a plurality of available slots for repeatedly transmitting a PUSCH based on PUSCH configuration information (S830), and can transmit the PUSCH through at least some of the determined plurality of available slots (S840).

The plurality of valid slots may be slots in which all symbols allocated for PUSCH transmission in each slot are set to uplink (UL) or flexible non-SBFD (subband full duplex) symbols by TDD configuration information that do not include SSB reception symbols. Alternatively, the plurality of valid slots may be slots in which symbols allocated for PUSCH transmission in each slot are set to downlink (DL) symbols by TDD configuration information and are reset to SBFD symbols in which an uplink subband is configured by subband configuration information. Alternatively, the plurality of valid slots may include both slots in which symbols allocated for PUSCH transmission in each slot are set to non-SBFD symbols and slots reset to SBFD symbols.

That is, multiple valid slots to be used for PUSCH repeated transmission must not include SSB reception symbols among the symbols allocated for PUSCH transmission within the slots, and can be set to include only one of non-SBFD slots or SBFD slots, or both. Here, SBFD slots and non-SBFD slots can each mean a type of slot.

Accordingly, the terminal can determine the plurality of valid slots based on whether to include both a slot consisting of SBFD symbols (SBFD slot) and a slot consisting of non-SBFD symbols (non-SBFD slot) in the plurality of valid slots based on the configuration of the base station. To this end, the terminal can receive enable/disable information of PUSCH repeated transmission through different slot types explicitly or implicitly from the base station.

The UE can be explicitly configured to activate PUSCH repeated transmission through different slot types by the eNB through cell-specific or UE-specific RRC signaling. Alternatively, the UE can be explicitly instructed to activate PUSCH repeated transmission through different slot types by the eNB through a DCI format or an uplink grant of RAR. Alternatively, the activation of PUSCH repeated transmission through different slot types can be implicitly configured by FDRA information for PUSCH transmission, type information of a first PUSCH transmission slot, information of a DCI format reception slot type including PUSCH scheduling control information, etc. Alternatively, it can be configured in the form of a combination of the explicit and implicit configurations described above.

When PUSCH repetitive transmission through different slot types is enabled, the terminal may include non-SBFD slots and SBFD slots together when counting multiple valid slots in which PUSCH transmission is possible. However, the terminal may determine multiple valid slots excluding slots in which symbols allocated for PUSCH transmission in the slot include symbols set or instructed by the base station to receive downlink among SBFD symbols.

That is, the SBFD symbol in the SBFD slot includes both an uplink subband and a downlink subband based on the TDD configuration information and the subband configuration information, and the base station can set or indicate the transmission direction of the SBFD symbol to UL or DL. Accordingly, if at least one SBFD symbol allocated for PUSCH transmission in the SBFD slot has its transmission direction set or indicated to DL by the base station, the slot including the corresponding symbol can be excluded when counting a plurality of valid slots. This can be equally applied when PUSCH repeated transmission through different slot types is disabled and the SBFD slot type is set for PUSCH repeated transmission.

Below, a specific example of determining multiple valid slots used for PUSCH repeated transmission when PUSCH repeated transmission through different slot types is enabled is described.

For example, the terminal may receive AvailableSlotCounting information from the base station. When AvailableSlotCounting is activated, the terminal may perform slot counting for PUSCH transmission according to the set or indicated PUSCH repetition number and K value when receiving DCI format 0_1 or DCI format 0_2 from the base station. Specifically, when the terminal counts N K slots for PUSCH transmission based on the DCI format reception information, the terminal may determine N K slots, excluding the slots below, as slots for PUSCH repeated transmission. Here, N may be a slot number setting value set in relation to TBoMS. If a PUSCH transmission symbol allocated by DCI format 0_1 or 0_2 in each slot includes a non-SBFD symbol that is set to DL by TDD configuration information and for which an uplink subband is not set, it may be excluded from slot counting. In addition, if a PUSCH transmission symbol includes an SBFD symbol for which DL reception is configured by the base station, the corresponding slot may be excluded from slot counting. In addition, if a PUSCH transmission symbol includes an SS/PBCH block by SSB-PositionInBurst, the corresponding slot may be excluded from slot counting. In other cases, the terminal may configure N·K consecutive slots as slots for PUSCH repetition.

For example, a terminal may receive PUSCH repetition indication information from a base station through an RAR uplink grant. In this case, when receiving the RAR uplink grant, the terminal may perform slot counting for PUSCH transmission according to the configured or configured PUSCH repetition number and K value. Specifically, when counting N K slots for PUSCH transmission based on the RAR uplink grant reception information, the terminal may determine N K slots, excluding the slots below, as slots for PUSCH repetition transmission. If a PUSCH transmission symbol allocated by the RAR uplink grant in each slot includes a non-SBFD symbol for which DL is set by TDD configuration information and an uplink subband is not set, the slot may be excluded from slot counting. In addition, if a PUSCH transmission symbol includes an SBFD symbol for which DL reception is set by the base station, the corresponding slot may be excluded from slot counting. Additionally, if a PUSCH transmission symbol includes an SS/PBCH block by SSB-PositionInBurst, the corresponding slot may be excluded from slot counting.

For example, the terminal may receive PUSCH repetition indication information from the base station through the DCI format 0_0 that is CRC scrambled based on the TC-RNTI. In this case, when the DCI format 0_0 is received, the terminal may perform slot counting in which PUSCH transmission is possible according to the set or indicated number of PUSCH repetitions and the value K. Specifically, when the terminal counts N K slots for PUSCH transmission based on the DCI format 0_0 reception information, the terminal may determine N K slots excluding the slots below as slots for PUSCH repetition transmission. If a PUSCH transmission symbol allocated by the DCI format 0_0 in each slot includes a non-SBFD symbol that is set to DL by the TDD configuration information and for which an uplink subband is not set, it may be excluded from slot counting. In addition, if a PUSCH transmission symbol includes an SBFD symbol for which DL reception is configured by the base station, the corresponding slot may be excluded from slot counting. In addition, if a PUSCH transmission symbol includes an SS/PBCH block by SSB-PositionInBurst, the corresponding slot may be excluded from slot counting.

In another example, when PUSCH repetitive transmission through different slot types is disabled, the UE may determine a plurality of valid slots based on only one of the slot types distinguished as a slot including an SBFD symbol or a slot including a non-SBFD symbol. That is, the plurality of valid slots used for the repetitive transmission of the PUSCH may be counted as only SBFD slots or as only non-SBFD slots.

In this case, the slot type for determining the plurality of valid slots used for the repeated transmission of the PUSCH may be set or indicated by the base station, determined by the type of a symbol in which downlink control information including scheduling information of the PUSCH is received, or determined by the symbol type of the first slot among the plurality of valid slots. That is, when the repeated transmission of PUSCH through different slot types is disabled, the slot type in which the PUSCH repetition is performed may be determined by the reception slot type of the DCI format including the scheduling control information for the corresponding PUSCH, or determined by the first PUSCH transmission slot type by the DCI format. Alternatively, the slot type setting information or indication information for the PUSCH repetition may be transmitted by the base station through RRC signaling or through the corresponding DCI format.

Below, a specific example of determining multiple valid slots used for PUSCH repetition transmission is described when PUSCH repetition transmission through different slot types is disabled and the slot type used for PUSCH repetition is set or indicated as a non-SBFD slot.

For example, the terminal may receive AvailableSlotCounting information from the base station. When AvailableSlotCounting enable is activated, the terminal may perform slot counting for PUSCH transmission according to the set or indicated PUSCH repetition number and K value when receiving DCI format 0_1 or DCI format 0_2 from the base station. Specifically, when the terminal counts N K slots for PUSCH transmission based on the DCI format reception information, the terminal may determine N K slots, excluding the slots below, as slots for PUSCH repeated transmission. Here, N may be a slot number setting value set in relation to TBoMS. If a PUSCH transmission symbol allocated by DCI format 0_1 or 0_2 in each slot includes a symbol set to DL by TDD configuration information, it may be excluded from slot counting. In addition, if a PUSCH transmission symbol includes an SS/PBCH block by SSB-PositionInBurst, the corresponding slot may be excluded from slot counting. In other cases, the terminal may set N·K consecutive slots as slots for PUSCH repetition.

For example, a terminal may receive PUSCH repetition indication information from a base station through a RAR uplink grant. In this case, when receiving the RAR uplink grant, the terminal may perform slot counting for PUSCH transmission according to the set or indicated number of PUSCH repetitions and the K value. Specifically, when counting N K slots for PUSCH transmission based on the RAR uplink grant reception information, the terminal may determine N K slots, excluding the slots below, as slots for PUSCH repetition transmission. If a PUSCH transmission symbol allocated by the RAR uplink grant in each slot includes a symbol set to DL by TDD configuration information, it may be excluded from slot counting. In addition, if a PUSCH transmission symbol includes an SS/PBCH block by SSB-PositionInBurst, the corresponding slot may be excluded from slot counting.

For example, a terminal may receive PUSCH repetition indication information from a base station through a DCI format 0_0 that is CRC scrambled based on a TC-RNTI. In this case, when receiving the DCI format 0_0, the terminal may perform slot counting in which PUSCH transmission is possible according to the set or indicated number of PUSCH repetitions and the value K. Specifically, when counting N K slots for PUSCH transmission based on the DCI format 0_0 reception information, the terminal may determine N K slots excluding the slots below as slots for PUSCH repetition transmission. If a PUSCH transmission symbol allocated by the DCI format 0_0 in each slot includes a symbol set to DL by the TDD configuration information, it may be excluded from slot counting. In addition, if a PUSCH transmission symbol includes an SS/PBCH block by SSB-PositionInBurst, the corresponding slot may be excluded from slot counting.

Below, a specific example of determining multiple valid slots used for PUSCH repetition transmission is described when PUSCH repetition transmission through different slot types is disabled and the slot type used for PUSCH repetition is set or indicated as an SBFD slot.

For example, the terminal may receive AvailableSlotCounting information from the base station. When AvailableSlotCounting is activated, the terminal may perform slot counting for PUSCH transmission according to the configured or instructed PUSCH repetition number and K value when receiving DCI format 0_1 or DCI format 0_2 from the base station. Specifically, when the terminal counts N K slots for PUSCH transmission based on the DCI format reception information, the terminal may determine N K slots, excluding the slots below, as slots for PUSCH repeated transmission. Here, N may be a slot number setting value configured in relation to TBoMS. If a PUSCH transmission symbol allocated by DCI format 0_1 or 0_2 in each slot includes a non-SBFD symbol for which an uplink subband is not configured, it may be excluded from slot counting. In addition, if a PUSCH transmission symbol includes an SS/PBCH block by SSB-PositionInBurst, the corresponding slot may be excluded from slot counting. In addition, if a PUSCH transmission symbol includes an SBFD symbol for which DL reception is configured by the base station, the corresponding slot may be excluded from slot counting. In other cases, the terminal may configure N·K consecutive slots as slots for PUSCH repetition.

For example, a terminal may receive PUSCH repetition indication information from a base station through a RAR uplink grant. In this case, when receiving the RAR uplink grant, the terminal may perform slot counting in which PUSCH transmission is possible according to the configured or configured PUSCH repetition number and K value. Specifically, when counting N K slots for PUSCH transmission based on the RAR uplink grant reception information, the terminal may determine N K slots, excluding the slots below, as slots for PUSCH repetition transmission. If a PUSCH transmission symbol allocated by the RAR uplink grant in each slot includes a non-SBFD symbol for which an uplink subband is not configured, the slot may be excluded from slot counting. In addition, if a PUSCH transmission symbol includes an SS/PBCH block by SSB-PositionInBurst, the corresponding slot may be excluded from slot counting. Additionally, if a PUSCH transmission symbol includes an SBFD symbol for which DL reception is configured by the base station, the corresponding slot may be excluded from slot counting.

For example, a terminal may receive PUSCH repetition indication information from a base station through a CRC scrambled DCI format 0_0 based on TC-RNTI. In this case, when receiving the DCI format 0_0, the terminal may perform slot counting in which PUSCH transmission is possible according to the configured or configured PUSCH repetition number and K value. Specifically, when counting N K slots for PUSCH transmission based on the DCI format 0_0 reception information, the terminal may determine N K slots excluding the slots below as slots for PUSCH repetition transmission. If a PUSCH transmission symbol allocated by the DCI format 0_0 in each slot includes a non-SBFD symbol for which an uplink subband is not configured, the slot may be excluded from slot counting. In addition, if a PUSCH transmission symbol includes an SS/PBCH block by SSB-PositionInBurst, the corresponding slot may be excluded from slot counting. Additionally, if a PUSCH transmission symbol includes an SBFD symbol for which DL reception is configured by the base station, the corresponding slot may be excluded from slot counting.

For example, if a plurality of valid slots for repeated transmission of a PUSCH include both slots including SBFD symbols and slots including non-SBFD symbols, the terminal may transmit the PUSCH according to downlink control information defined separately for repeated transmission of the PUSCH.

That is, when PUSCH repetition is set for a terminal and PUSCH repetition through different slot types is explicitly or implicitly activated by the base station, a separate DCI format, such as DCI format 0_x, may be newly defined for this purpose. When the DCI format is defined separately, the information field of the corresponding DCI format may be configured to be divided into a slot-type common information area and a slot-type specific information area.

In this case, the slot type common information area may be an information area that can be set and applied identically to PUSCH transmission in a non-SBFD slot and PUSCH transmission in an SBFD slot. Accordingly, it may have a single setting value within the corresponding DCI format. For example, the TDRA information area, etc. may be a slot type common information area, and may include a single information area as before.

On the other hand, the slot type-specific information area may be an information area that is separately set and applied for PUSCH transmission in a non-SBFD slot and PUSCH transmission in an SBFD slot, respectively. Accordingly, the same information area may have a setting value for a non-SBFD slot and a setting value for a separate SBFD slot, respectively. For example, FDRA, TCI fields, etc. may be slot type-specific information areas.

However, the above-mentioned content is an example, and all combinations in which, when configuring DCI format 0_x, a specific information area is applied commonly to slot types through setting values and other information areas are set separately for each slot type can be included in the present invention.

After determining a plurality of valid slots for repetitive transmission of a PUSCH, the terminal can repeatedly transmit the PUSCH to the base station through at least some of the determined plurality of valid slots. That is, the terminal counts a plurality of valid slots that can be used for repetitive transmission of the PUSCH, and can repeatedly transmit the PUSCH using all or some of the plurality of valid slots according to a situation set for the terminal thereafter. For example, in a situation such as when a PUCCH transmission with a higher priority is instructed, the PUSCH transmission can be dropped for a slot allocated to PUCCH transmission among the determined valid slots.

According to this, a method and device for efficiently performing repeated transmission and reception of an uplink data channel in a slot or symbol to which full-duplex communication is applied can be provided.

FIG. 9 is a diagram illustrating a procedure (900) for a base station to repeatedly receive an uplink data channel according to one embodiment. The description given above in FIG. 8 may be omitted to avoid redundant description, and in this case, the omitted content may be substantially equally applied to the base station as long as it does not contradict the technical idea of the invention.

Referring to FIG. 9, the base station can transmit TDD (Time Division Duplex) configuration information and subband configuration information (S910).

TDD (Time Division Duplex) is a method of using time-interval radio resources by dividing them into downlink slots and uplink slots, and a base station can transmit TDD configuration information to a terminal to determine the format of a symbol in a slot. In this case, the TDD configuration information can include configuration information regarding the format of a slot and configuration information for determining the format of a symbol in a slot, and the information can be received through upper layer signaling or physical layer (L1) signaling.

That is, a downlink symbol, an uplink symbol, and a flexible symbol whose transmission direction is not determined can be set for a certain period through an RRC message for setting the corresponding UL-DL slot. In addition, the base station can transmit a terminal-specific RRC signaling for re-allocating flexible symbols among the symbols set through cell-specific RRC signaling to uplink symbols, downlink symbols, or flexible symbols for each terminal.

Alternatively, the base station may indicate a dynamic slot format via a UE-group common PDCCH. As an example, the base station may indicate a slot format dynamically via DCI format 2_0.

The base station can transmit subband configuration information for full-duplex communication to the terminal. That is, configuration information for configuring a downlink subband in an uplink slot or configuring an uplink subband in a downlink slot can be transmitted. The subband configuration information can include information about a frequency domain in which an uplink subband or a downlink subband is configured and information about a time domain. Alternatively, the subband configuration information can include information about a frequency domain in which a guard band is configured and information about a time domain.

The subband configuration information can be transmitted through a broadcasting method that is transmitted to all terminals in the cell. Alternatively, it can be transmitted through a multicasting method that is transmitted to terminals that require full-duplex communication mode operation, or a unicasting method that is transmitted only to specific terminals. The base station can transmit the corresponding configuration information according to the set method.

That is, a downlink slot or downlink symbol configured for a terminal may include an SBFD symbol in which an uplink subband for full-duplex communication is configured. In other words, an uplink subband may be configured for at least some of the downlink slots or downlink symbols configured for the terminal, and in this case, an uplink subband, a downlink subband, and/or a guard band may be configured for the corresponding slot or symbol.

Similarly, an uplink slot or uplink symbol configured for a terminal may include an SBFD symbol in which a downlink subband for full-duplex communication is configured. In other words, a downlink subband may be configured for at least some of the uplink slots or uplink symbols configured for the terminal, and in this case, an uplink subband, a downlink subband, and/or a guard band may be configured for the corresponding slot or symbol.

Referring again to FIG. 9, the base station can transmit PUSCH configuration information including PUSCH repetition transmission information (S920).

The base station may transmit PUSCH configuration information that sets or instructs repeated transmission of the PUSCH to the terminal. In one example, repeated transmission of the PUSCH may mean a case where one PUSCH transmission is performed over multiple slots. For example, this may include a case where PUSCH repetition is set or instructed, a case where TBoMS (TB processing over multiple slots) is set or instructed, or a case where multiple PUSCH transmissions are scheduled over one DCI.

For example, the base station may transmit, to the terminal, a configuration of pusch-AggregationFactor, which is an RRC parameter for semi-statically configuring repeated transmission for PUSCH. Alternatively, the base station may dynamically indicate repeated transmission for PUSCH through a time domain resource allocation (TDRA) indication information field of an uplink grant (UL grant). That is, the base station may indicate time domain resource allocation information of one of the TDRA tables configured by PUSCH-TimeDomainResourceAllocationList through the TDRA indication information field of the uplink grant. In this case, if the time domain resource allocation information includes repetition count information or slot count information in TBoMS, the base station may indicate one or more PUSCH repetitions according to the corresponding setting value.

In this way, through PUSCH configuration information, one PUSCH transmission can be set or instructed to be performed through multiple slots.

Referring again to FIG. 9, the base station sets whether to enable repetitive transmission of PUSCH through slots of different slot types (S930), and can receive PUSCH through at least some of the slots among a plurality of available slots determined based on whether to enable repetitive transmission of PUSCH (S940).

The plurality of valid slots may be slots in which all symbols allocated for PUSCH transmission in each slot are set to uplink (UL) or flexible non-SBFD (subband full duplex) symbols by TDD configuration information that do not include SSB reception symbols. Alternatively, the plurality of valid slots may be slots in which symbols allocated for PUSCH transmission in each slot are set to downlink (DL) symbols by TDD configuration information and are reset to SBFD symbols in which an uplink subband is configured by subband configuration information. Alternatively, the plurality of valid slots may include both slots in which symbols allocated for PUSCH transmission in each slot are set to non-SBFD symbols and slots reset to SBFD symbols.

That is, multiple valid slots to be used for PUSCH repeated transmission must not include SSB reception symbols among the symbols allocated for PUSCH transmission within the slots, and can be set to include only one of non-SBFD slots or SBFD slots, or both. Here, SBFD slots and non-SBFD slots can each mean a type of slot.

Accordingly, the terminal can determine the plurality of valid slots based on whether to include both a slot consisting of SBFD symbols (SBFD slot) and a slot consisting of non-SBFD symbols (non-SBFD slot) in the plurality of valid slots based on the configuration of the base station. To this end, the base station can explicitly or implicitly transmit to the terminal information on enabling/disabling PUSCH repeated transmission through different slot types.

The base station can explicitly configure the activation of PUSCH repeated transmission through different slot types via cell-specific or UE-specific RRC signaling. Or, the base station can explicitly indicate the activation of PUSCH repeated transmission through different slot types via a DCI format or an uplink grant of an RAR. Or, the activation of PUSCH repeated transmission through different slot types can be implicitly configured by FDRA information for PUSCH transmission, type information of a first PUSCH transmission slot, information of a DCI format reception slot type including PUSCH scheduling control information, etc. Or, it can be configured in the form of a combination of the explicit configuration and the implicit configuration as described above.

When PUSCH repetitive transmission through different slot types is enabled, the terminal may include non-SBFD slots and SBFD slots together when counting multiple valid slots in which PUSCH transmission is possible. However, the terminal may determine multiple valid slots excluding slots in which symbols allocated for PUSCH transmission in the slot include symbols set or instructed by the base station to receive downlink among SBFD symbols.

That is, the SBFD symbol in the SBFD slot includes both an uplink subband and a downlink subband based on the TDD configuration information and the subband configuration information, and the base station can set or indicate the transmission direction of the SBFD symbol to UL or DL. Accordingly, if at least one SBFD symbol allocated for PUSCH transmission in the SBFD slot has its transmission direction set or indicated to DL by the base station, the slot including the corresponding symbol can be excluded when counting a plurality of valid slots. This can be equally applied when PUSCH repeated transmission through different slot types is disabled and the SBFD slot type is set for PUSCH repeated transmission.

Below, a specific example of determining multiple valid slots used for PUSCH repeated transmission when PUSCH repeated transmission through different slot types is enabled is described.

For example, the base station may transmit AvailableSlotCounting information to the terminal. When AvailableSlotCounting is activated, the terminal may perform slot counting for PUSCH transmission according to the configured or instructed PUSCH repetition number and K value when receiving DCI format 0_1 or DCI format 0_2 from the base station. Specifically, when the terminal counts N K slots for PUSCH transmission based on the DCI format reception information, the terminal may determine N K slots, excluding the slots below, as slots for PUSCH repeated transmission. Here, N may be a slot number setting value configured in relation to TBoMS. If a PUSCH transmission symbol in each slot includes a non-SBFD symbol that is set to DL by TDD configuration information and for which an uplink subband is not configured, if it includes an SBFD symbol for which DL reception is configured by the base station, or if it includes an SS/PBCH block by SSB-PositionInBurst, the slot may be excluded from slot counting.

For example, the base station may transmit PUSCH repetition indication information to the terminal through the RAR uplink grant. In this case, the terminal may perform slot counting in which PUSCH transmission is possible according to the configured or configured PUSCH repetition number and K value when receiving the RAR uplink grant. Specifically, when the terminal counts N K slots for PUSCH transmission based on the RAR uplink grant reception information, the terminal may determine N K slots, excluding the slots below, as slots for PUSCH repetition transmission. If a PUSCH transmission symbol in each slot includes a non-SBFD symbol that is set to DL by TDD configuration information and for which an uplink subband is not configured, if it includes an SBFD symbol for which DL reception is configured by the base station, or if it includes an SS/PBCH block by SSB-PositionInBurst, the slot may be excluded from slot counting.

For example, the base station may transmit PUSCH repetition indication information to the terminal through the DCI format 0_0 that is CRC scrambled based on the TC-RNTI. In this case, the terminal may perform slot counting in which PUSCH transmission is possible according to the set or indicated number of PUSCH repetitions and the value K when receiving the DCI format 0_0. Specifically, when the terminal counts N K slots for PUSCH transmission based on the DCI format 0_0 reception information, the terminal may determine N K slots, excluding the slots below, as slots for PUSCH repetition transmission. If a PUSCH transmission symbol in each slot includes a non-SBFD symbol that is set to DL by TDD configuration information and for which an uplink subband is not set, if it includes an SBFD symbol for which DL reception is set by the base station, or if it includes an SS/PBCH block by SSB-PositionInBurst, the slot may be excluded from slot counting.

In another example, when PUSCH repetitive transmission through different slot types is disabled, the UE may determine a plurality of valid slots based on only one of the slot types distinguished as a slot including an SBFD symbol or a slot including a non-SBFD symbol. That is, the plurality of valid slots used for the repetitive transmission of the PUSCH may be counted as only SBFD slots or as only non-SBFD slots.

In this case, the slot type for determining a plurality of valid slots used for repeated transmission of the PUSCH may be set or indicated by the base station, determined by the type of a symbol in which downlink control information including scheduling information of the PUSCH is received, or determined by the symbol type of the first slot among the plurality of valid slots.

Below, a specific example of determining multiple valid slots used for PUSCH repetition transmission is described when PUSCH repetition transmission through different slot types is disabled and the slot type used for PUSCH repetition is set or indicated as a non-SBFD slot.

For example, the base station may transmit AvailableSlotCounting information to the terminal. When AvailableSlotCounting is enabled, the terminal may perform slot counting for PUSCH transmission according to the set or indicated PUSCH repetition number and K value when receiving DCI format 0_1 or DCI format 0_2 from the base station. Specifically, when the terminal counts N K slots for PUSCH transmission based on the DCI format reception information, the terminal may determine N K slots, excluding the slots below, as slots for PUSCH repeated transmission. Here, N may be a slot number setting value set in relation to TBoMS. If a PUSCH transmission symbol in each slot includes a symbol set to DL by TDD configuration information or includes an SS/PBCH block by SSB-PositionInBurst, the corresponding slot may be excluded from slot counting.

For example, the base station may transmit PUSCH repetition indication information to the terminal through the RAR uplink grant. In this case, the terminal may perform slot counting for PUSCH transmission according to the set or indicated number of PUSCH repetitions and the K value when receiving the RAR uplink grant. Specifically, when the terminal counts N K slots for PUSCH transmission based on the RAR uplink grant reception information, the terminal may determine N K slots, excluding the slots below, as slots for PUSCH repetition transmission. If a PUSCH transmission symbol in each slot includes a symbol set to DL by TDD configuration information or includes an SS/PBCH block by SSB-PositionInBurst, the corresponding slot may be excluded from slot counting.

For example, the base station may transmit PUSCH repetition indication information to the terminal through the DCI format 0_0 that is CRC scrambled based on the TC-RNTI. In this case, the terminal may perform slot counting in which PUSCH transmission is possible according to the set or indicated number of PUSCH repetitions and the value K when receiving the DCI format 0_0. Specifically, when the terminal counts N K slots for PUSCH transmission based on the DCI format 0_0 reception information, the terminal may determine N K slots excluding the slots below as slots for PUSCH repetition transmission. If a PUSCH transmission symbol in each slot includes a symbol set to DL by TDD configuration information or includes an SS/PBCH block by SSB-PositionInBurst, the corresponding slot may be excluded from slot counting.

Below, a specific example of determining multiple valid slots used for PUSCH repetition transmission is described when PUSCH repetition transmission through different slot types is disabled and the slot type used for PUSCH repetition is set or indicated as an SBFD slot.

For example, the base station may transmit AvailableSlotCounting information to the terminal. When AvailableSlotCounting is activated, the terminal may perform slot counting for PUSCH transmission according to the configured or instructed PUSCH repetition number and K value when receiving DCI format 0_1 or DCI format 0_2 from the base station. Specifically, when the terminal counts N K slots for PUSCH transmission based on the DCI format reception information, the terminal may determine N K slots, excluding the slots below, as slots for PUSCH repeated transmission. Here, N may be a slot number setting value configured in relation to TBoMS. If a PUSCH transmission symbol in each slot includes a non-SBFD symbol for which an uplink subband is not configured, includes an SS/PBCH block by SSB-PositionInBurst, or includes an SBFD symbol for which DL reception is configured by the base station, the corresponding slot may be excluded from slot counting.

For example, the base station may transmit PUSCH repetition indication information to the terminal through the RAR uplink grant. In this case, the terminal may perform slot counting for PUSCH transmission according to the configured or configured PUSCH repetition number and K value when receiving the RAR uplink grant. Specifically, when the terminal counts N K slots for PUSCH transmission based on the RAR uplink grant reception information, the terminal may determine N K slots, excluding the slots below, as slots for PUSCH repetition transmission. If a PUSCH transmission symbol in each slot includes a non-SBFD symbol for which an uplink subband is not configured, includes an SS/PBCH block by SSB-PositionInBurst, or includes an SBFD symbol for which DL reception is configured by the base station, the corresponding slot may be excluded from slot counting.

For example, the base station may transmit PUSCH repetition indication information to the terminal through the DCI format 0_0 that is CRC scrambled based on the TC-RNTI. In this case, the terminal may perform slot counting in which PUSCH transmission is possible according to the configured or configured PUSCH repetition number and K value when receiving the DCI format 0_0. Specifically, when the terminal counts N K slots for PUSCH transmission based on the DCI format 0_0 reception information, the terminal may determine N K slots excluding the slots below as slots for PUSCH repetition transmission. If a PUSCH transmission symbol in each slot includes a non-SBFD symbol for which an uplink subband is not configured, if it includes an SS/PBCH block by SSB-PositionInBurst, or if it includes an SBFD symbol for which DL reception is configured by the base station, the corresponding slot may be excluded from slot counting.

For example, if a plurality of valid slots for repeated transmission of a PUSCH include both slots including SBFD symbols and slots including non-SBFD symbols, the base station may define separate downlink control information for repeated transmission of the PUSCH.

That is, when PUSCH repetition is set for a terminal and PUSCH repetition through different slot types is explicitly or implicitly activated by the base station, a separate DCI format, such as DCI format 0_x, may be newly defined for this purpose. When the DCI format is defined separately, the information field of the corresponding DCI format may be configured to be divided into a slot-type common information area and a slot-type specific information area.

In this case, the slot type common information area may be an information area that can be set and applied identically to PUSCH transmission in a non-SBFD slot and PUSCH transmission in an SBFD slot. Accordingly, it may have a single setting value within the corresponding DCI format. For example, the TDRA information area, etc. may be a slot type common information area, and may include a single information area as before.

On the other hand, the slot type-specific information area may be an information area that is separately set and applied for PUSCH transmission in a non-SBFD slot and PUSCH transmission in an SBFD slot, respectively. Accordingly, the same information area may have a setting value for a non-SBFD slot and a setting value for a separate SBFD slot, respectively. For example, FDRA, TCI fields, etc. may be slot type-specific information areas.

However, the above-mentioned content is an example, and all combinations in which, when configuring DCI format 0_x, a specific information area is applied commonly to slot types through setting values and other information areas are set separately for each slot type can be included in the present invention.

When multiple valid slots for repeatedly transmitting PUSCH are determined from a terminal, the base station can repeatedly receive PUSCH through at least some of the determined multiple valid slots. That is, the base station can repeatedly receive PUSCH using all or some of the multiple valid slots that can be used for repeatedly transmitting PUSCH counted from the terminal. For example, in a situation such as when PUCCH transmission with a higher priority is indicated, PUSCH transmission can be dropped for a slot allocated to PUCCH transmission among the determined multiple valid slots.

According to this, a method and device for efficiently performing repeated transmission and reception of an uplink data channel in a slot or symbol to which full-duplex communication is applied can be provided.

Hereinafter, with reference to the relevant drawings, each embodiment related to a method for repeatedly transmitting and receiving an uplink data channel in full-duplex communication will be specifically described.

The present disclosure proposes a resource allocation method for uplink data channel, i.e., PUSCH transmission, of a terminal in an arbitrary base station/cell in which an uplink subband (UL subband) or a downlink subband (DL subband) is configured to support full duplex communication in a wireless mobile communication system. In particular, when repetition is configured/instructed for an arbitrary PUSCH transmission and the corresponding PUSCH transmission is transmitted through a plurality of slots, a method for supporting the corresponding PUSCH repetition transmission through an SBFD slot including an UL subband and a non-SBFD slot (e.g., a conventional UL slot) is proposed.

TDD (Time Division Duplex) is a duplexing method widely used in commercial NR (New Radio), i.e., 5G mobile communication systems. In TDD, time-interval radio resources are divided into downlink slots and uplink slots and used, and usually, downlink slots are distributed at a higher ratio than uplink slots depending on the distribution ratio of uplink traffic and downlink traffic. However, this limitation of uplink slots has a negative impact in terms of coverage and delay time. Full-duplex communication can be applied as a technology to solve this problem.

Full-duplex communication is a technology that performs DL transmission and UL reception simultaneously on the same radio resources, specifically, at the gNB, i.e., the base station. DL reception and UL transmission can also be performed simultaneously at the terminal side. In other words, both the base station and the terminal can support full duplex. However, unlike the base station which is structurally easy to cancel self-interference, the DL reception performance of the terminal is easily affected by the self-interference of the UL transmission signal. Therefore, it is generally considered that the base station operates in full-duplex communication and the terminal operates in half-duplex communication. Additionally, in order to reduce the influence of self-interference at the base station, a subband non-overlapping full-duplex method can be primarily considered, in which DL transmission and UL reception are performed simultaneously but frequency resources are distinguished and not the same resources for DL/UL to be transmitted and received.

That is, FIGS. 10 and 11 illustrate examples in which DL slots and UL slots are configured in a ratio of 4:1 in an arbitrary NR frequency band. However, some symbols of the last DL slot may be a special slot including a flexible symbol for DL/UL transition. In this way, when a TDD (Time Division Duplex) configuration is made, an uplink subband (UL subband) may be set in some (or all) of the DL slots to support UL transmission of a terminal. When a UL subband is set in an arbitrary DL slot, the UL subband may be set at the center of the frequency band, as in FIG. 10, or at the edge of the frequency band, as in FIG. 11. In this case, a guard band may be set between the UL subband and the downlink subband (DL subband) in the slot.

In the present disclosure, when any base station/network supports sub-band non-overlapping full duplex, a BWP setting and a method of transmitting/receiving uplink/downlink radio signals (DM-RS, CSI-RS, SRS, PSS/SSS, etc.) and radio channels (e.g., PDCCH/PDSCH and PUSCH/PUCCH, etc.) between a base station and a terminal are proposed. However, the contents described in the present disclosure can be substantially equally applied to various other full duplex application scenarios. For example, a full duplex application scenario can include a full duplex operation in an unpaired spectrum and a full duplex operation in a downlink (DL) frequency band or an uplink (UL) frequency band of a paired spectrum. In addition, as described above, the contents of the present disclosure can be substantially equally applied to a scenario where only the base station supports sub-band non-overlapping full duplex or pure form full duplex (i.e., simultaneous DL transmission and UL reception on the same frequency resource) and the terminal performs half duplex operation. In addition, the contents of the present disclosure can be substantially equally applied to a scenario where not only the base station but also the terminal supports sub-band non-overlapping full duplex or pure form full duplex.

The UL-DL slot configuration defined in NR is defined to be done on a cell-by-cell basis via cell-specific RRC signaling. That is, a pattern of DL symbols, UL symbols, and flexible symbols for a certain period is configured via the RRC message ' tdd-UL-DL-ConfigurationCommon ' for the corresponding UL-DL slot configuration. Additionally, through the UE-specific RRC signaling ' tdd-UL-DL-ConfigurationDedicated ', only the flexible symbols configured via the ' tdd-UL-DL-ConfigurationCommon ' can be reallocated to UL symbols, DL symbols, or flexible symbols for each UE. Alternatively, a method of indicating a dynamic slot format via a UE-group common PDCCH is also defined. For this purpose, NR also supports a dynamic slot format indication method through DCI format 2_0.

According to the slot configuration method described above, any one symbol can be set or indicated as one of DL, UL, or Flexible. Fig. 10 is an example in which an arbitrary slot format is set to DDDSU through the existing slot configuration. D refers to a down link slot, which means that all OFDM symbols constituting the slot are set to DL. U refers to an uplink slot, which means that all OFDM symbols constituting the slot are set to UL. S refers to a special slot, which means a slot that includes a flexible symbol for DL/UL transition. In general, in the case of a normal CP, the special slot can be configured with 12 DL symbols and 2 flexible symbols out of a total of 14 symbols. Or, it can be configured with 10 DL symbols, 2 flexible symbols, and 2 UL symbols. That is, one symbol in any one TDD carrier is configured or indicated as only one of DL, UL, or flexible.

However, when a UL subband is configured in a random DL slot as in FIG. 10 and FIG. 11, DL transmission or UL transmission may occur simultaneously for each frequency resource in the symbol. In this way, a DL slot or symbol including a UL subband, or a UL slot or symbol including a DL subband, is referred to as a SBFD (subband full duplex) slot or SBFD symbol in the present disclosure.

In addition, in the present disclosure, a slot composed only of the SBFD symbols is referred to as an SBFD slot, and a slot composed only of symbols according to the existing symbol setting (i.e., a slot composed only of symbols not including a UL subband, a DL subband, and a guardband) is referred to as a non-SBFD slot. Alternatively, a slot including at least one SBFD symbol may be referred to as an SBFD slot.

Alternatively, in any terminal, an SBFD slot may mean a slot in which all symbols are SBFD symbols, as described above, and for which fallback is not instructed by the base station as a legacy slot configuration.

Alternatively, in any terminal, an SBFD slot may mean a slot in which all symbols are SBFD symbols, as described above, and in which the terminal is explicitly set or instructed by the base station to perform a UL transmission operation in the corresponding SBFD symbol.

Alternatively, an SBFD slot in any terminal may mean a slot in which all symbols are SBFD symbols, as described above, and in which the terminal is not explicitly set or instructed by the base station to perform a DL reception operation in the corresponding SBFD symbol.

Alternatively, in any terminal, an SBFD slot may mean a slot in which all symbols are SBFD symbols, as described above, and the terminal is explicitly set or instructed by the base station to perform a UL transmission operation in the corresponding SBFD symbol, and also a slot in which fallback is not instructed by the base station as a legacy slot configuration.

Alternatively, an SBFD slot in any terminal may mean a slot in which all symbols are SBFD symbols, as described above, and the terminal is not explicitly set or instructed by the base station to perform a DL reception operation in the corresponding SBFD symbol, and also a slot in which fallback is not instructed by the base station to a legacy slot configuration.

According to the PUSCH transmission method of the terminal defined in the existing 5G NR, any terminal supports PUSCH transmission based on dynamic scheduling through UL grant of DCI (Downlink Control Information) transmitted by the base station through PDCCH and PUSCH transmission based on configured grant based on RRC. In particular, the PUSCH transmission based on configured grant includes configured grant type 1 by higher layer parameter ' configuredGrantConfig ' including ' rrc-ConfiguredUplinkGrant ' without activation through separate DCI, and configured grant type 2 activated through DCI according to the semi-persistent scheduling method of the existing LTE.

The above dynamic scheduling-based PUSCH transmission basically transmits a DCI format (e.g., DCI format 0_0, 0_1, 0_2, etc.) for resource allocation for each PUSCH transmission in units of slots or sub-slots, and PUSCH transmission is performed based on the resource allocation information included in the corresponding DCI format. Accordingly, PUSCH transmission resource allocation in an SBFD slot consisting of SBFD symbols as described above and PUSCH transmission resource allocation in a non-SBFD slot such as a UL slot can be performed through separate DCI transmissions.

However, in case of PUSCH transmission based on specific dynamic scheduling, PUSCH transmissions in different types of slots may be triggered through a single DCI. For example, this may include cases where PUSCH repetition is configured/indicated, TB processing over multiple slots (TBoMS) is configured/indicated, or scheduling for multiple PUSCH transmissions is performed through a single DCI.

In this disclosure, we propose a specific method for supporting, when an arbitrary PUSCH transmission with dynamic scheduling through a single DCI is instructed to be performed over one or more slots, particularly when PUSCH repetition is set/instructed, to be performed across different types of slots, i.e., including SBFD slots and non-SBFD slots.

In this disclosure, the term 'slot type' is used to distinguish between SBFD slots and non-SBFD slots, but the present invention is not limited by the specific name.

A base station can set or instruct repetition of PUSCH transmission for an arbitrary terminal. For example, the base station can semi-statically set the repetition for PUSCH transmission of an arbitrary terminal by configuring the RRC parameter pusch-AggregationFactor . Alternatively, the base station can dynamically instruct repetition for PUSCH transmission based on a corresponding UL grant through a time domain resource assignment (TDRA) indication information field of a UL grant. That is, the base station indicates time domain resource allocation information of one of the time domain resource allocation tables configured by the RRC configured PUSCH-TimeDomainResourceAllocationList through the time domain resource assignment indication information field of the UL grant. At this time, the base station may indicate one or more (e.g., 1, 2, 3, 4, 7, 8, 12, 16, 24, 28, 32) PUSCH repetitions depending on the setting value if the time domain allocation information includes numberOfRepetitions-r16 or numberOfSlotsTBoMS-r17.

PUSCH repetition can be classified into PUSCH repetition type A (slot-based) and PUSCH repetition type B (non-slot-based, i.e., mini-slot or sub-slot-based) depending on the mapping type of a PUSCH transmission.

Hereinafter, PUSCH repetition may include both PUSCH repetition type A and PUSCH repetition type B.

In this way, a single PUSCH transmission can be set/instructed to be performed over multiple slots through arbitrary PUSCH repetition settings/instructions. At this time, slots corresponding to the repetition number set or instructed by the base station are determined, and if the symbols allocated according to symbol allocation information for PUSCH transmission (i.e., TDRA of the UL grant) in the determined slot are suitable for UL transmission, PUSCH transmission is actually performed in the corresponding slot.

At this time, the method of determining PUSCH repetition slots varies depending on whether the RRC parameter AvailableSlotCounting is enabled.

1. When AvailableSlotCounting is enabled, the UE determines PUSCH transmission slots for PUSCH repetition scheduled by DCI format 0_1 or DCI format 0_2, excluding slots satisfying the conditions below, and counts N K slots according to the PUSCH repetition number, K. (Here, N is the number of slots in which transmission for one TB occurs when TB processing over multiple slots is configured and TDRA including numberOfSlotsTBoMS is configured and instructed.)

a. If at least one symbol among the symbols according to the time domain resource allocation information for the corresponding PUSCH repetition for any slot is indicated as a DL symbol by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

b. If at least one symbol among the symbols according to the time domain resource allocation information for the corresponding PUSCH repetition for any slot is indicated as an SS/PBCH block symbol by the index information of ssb-PositionsInBurst.

2. On the other hand, if the AvailableSlotCounting is not enabled, PUSCH transmission slots for PUSCH repetition scheduled by DCI format 0_1 or DCI format 0_2 consist of consecutive N·K slots regardless of the above conditions.

In this way, when slots for performing PUSCH repetition are determined according to the above conditions, whether or not to transmit actual PUSCH in the corresponding slot is additionally determined by the following conditions according to the legacy slot configuration. (However, in the present invention, the legacy slot configuration refers to the slot configuration by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated as the legacy slot configuration, or may also refer to the slot configuration by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated as well as the dynamic slot format setting by DCI format 2_0 as the legacy slot configuration.)

1. If at least one symbol among the symbols allocated for PUSCH transmission in any one of the N·K slots above is indicated as DL by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated , PUSCH is not transmitted in the slot.

However, as described above, even for a slot or symbol set to downlink (DL) by legacy slot configuration in any slot, if the UL subband is set by the base station (i.e., set to an SBFD slot or symbol), PUSCH transmission may be possible from any terminal.

Therefore, the present disclosure proposes a method for determining a PUSCH repetition slot for performing a PUSCH repetition operation of a terminal when an SBFD slot is set by a base station, and a method for transmitting a PUSCH of the terminal in the determined slot.

The methods proposed below can solve the above problem by each method being applied completely/independently or as a combination of one or more methods, and all of these cases are included in the scope of the present invention.

Example 1. Method for determining PUSCH repetition slots

When PUSCH repetition is set/indicated for one PUSCH transmission allocated to a certain terminal, it can be defined that the base station explicitly or implicitly sets whether or not to restrict according to the slot type when determining PUSCH transmission slots for the corresponding PUSCH repetition.

Below we will describe the explicit setup/direction method.

An additional information area for determining a PUSCH transmission slot for PUSCH repetition at a base station, i.e., for the PUSCH repetition slot counting, can be defined, and whether PUSCH transmission for a certain slot type is enabled can be set through the information area. For example, a new information area, extendedavailableslotcounting (this name is only an example, and the present invention is not limited thereby) can be defined. The information can be set or instructed by the base station as a parameter for determining whether a specific slot type is determined by a terminal as a slot where PUSCH repetition transmission is enabled (i.e., whether to include or exclude it from the available slot counting where PUSCH repetition is enabled), and can be interpreted by the terminal.

For example, in case of a non-SBFD slot, whether to be included in a PUSCH transmission slot for PUSCH repetitions is determined according to the above-described determination method depending on whether the existing availableslotcounting is enabled, and additionally, whether to exclude (or include) an SBFD slot can be determined through extendedavailableslotcounting. For example, if the extendedavailableslotcounting is set or enabled, an SBFD slot can be excluded from a slot for the corresponding PUSCH repetitions. In this case, the UE can determine a PUSCH transmission slot for the corresponding PUSCH repetitions based only on the non-SBFD slot. Or, conversely, if extendedavailableslotcounting is set or enabled, an SBFD slot can be included in a slot for the corresponding PUSCH repetitions.

Alternatively, extendedavailableslotcounting may be configuration information on whether to repeat through different slot types. In this case, a slot type that is the same as the first slot where PUSCH repetition by DCI format starts may be counted as a slot for PUSCH transmission. In this case, whether to include (or exclude) a PUSCH transmission slot for a slot of a different type from the corresponding PUSCH repetition start slot type may be determined based on whether the extendedavailableslotcounting is set and enabled. That is, when the PUSCH repetition start slot type is an SBFD slot, the SBFD slot may be included in the PUSCH transmission slot for PUSCH repetition, but for a non-SBFD slot, whether to include a PUSCH transmission slot may be determined based on whether extendedavailableslotcounting is set and enabled. Conversely, if the PUSCH repetition start slot type is a non-SBFD slot, the non-SBFD slot is included in the PUSCH transmission slot for PUSCH repetition, but in the case of the SBFD slot, whether or not to include the PUSCH transmission slot can be determined by whether extendedavailableslotcounting is set and enabled.

The above new information field, extendedavailableslotcounting, can be semi-statically set by the base station and transmitted via UE-specific or cell-specific RRC signaling. In this case, the new RRC parameter, extendedavailableslotcounting, can be included in an existing RRC message (e.g., PUSCH-config, etc.), or a new RRC message (e.g., UL subband configuration message, etc.) can be defined and included therein.

The above new information area, extendedavailableslotcounting, can be dynamically set by the base station and transmitted to the terminal through physical layer control signaling (L1 control signaling). For example, the base station can define to include the corresponding indication information in the DCI format for UL grant transmission (e.g., DCI format 0_0, 0_1, 0_2, etc.), or to transmit the corresponding indication information through UE-group common DCI.

In addition, various combinations of the above explicit signaling methods may also be included in the present disclosure. For example, for any terminal, it may be configured via RRC signaling whether to include an indication information area for the extendedavailableslotcounting in a specific DCI format for the terminal (e.g., DCI format 0_1, 0_2 for UL grant transmission, or UE-group common DCI format, etc.), and if the indication information area is configured to be included, it may be defined to dynamically indicate whether to include a PUSCH transmission slot for the PUSCH repetition.

Below we describe the implicit setting/instruction method.

In particular, the implicit setting/instruction method below can be applied as a method for determining whether to include the SBFD slot in determining a slot for PUSCH repetition.

As an example of an implicit configuration method, it can be determined by whether there is an overlap between a frequency resource of an activated uplink bandwidth part (UL BWP) for a certain terminal and a frequency resource of a UL subband configured by a base station. That is, whether the active UL BWP and the UL subband fully or partially overlap or do not overlap in the frequency axis can be used to determine whether to include an SBFD slot when determining a slot for PUSCH repetition. At this time, the target of the overlap determination can be the frequency resource of the active UL BWP. That is, if the frequency resource of the activated UL BWP for a certain terminal fully belongs to the UL subband, the terminal can be defined to include the SBFD slot when determining a PUSCH transmission slot for PUSCH repetition. On the other hand, in the case of partially over or non-overlap, the terminal can be defined not to include the SBFD slot when determining a PUSCH transmission slot for PUSCH repetition.

Alternatively, the target of the frequency resource overlap judgment may be a UL subband. That is, if the frequency resource of the UL subband for any terminal fully belongs to the activated UL BWP, the terminal may be defined to include the SBFD slot when determining the PUSCH repetition transmission slot. On the other hand, in the case of partially over or non-overlap, the SBFD slot may not be included when determining the PUSCH transmission slot for PUSCH repetition.

In another way, it can be implicitly determined by whether the frequency resource allocated by the frequency domain resource assignment (FDRA) information field, i.e., the frequency resource allocation information included in the DCI format, for a UL grant for a certain PUSCH transmission, is included in the UL subband. For example, if the frequency resource according to the frequency domain resource assignment information for PUSCH repetition transmission fully belongs to the UL subband, the UE can define the SBFD slot to be included in determining the PUSCH repetition transmission slot. However, if intra-slot or inter-slot frequency hopping is configured, the present method can be limited to the case where the frequency resources of each frequency hop all belong to the UL subband or when frequency hopping is not configured.

Alternatively, whether to include an SBFD slot can be determined by the slot type of the first slot from which the corresponding PUSCH repetition transmission starts. For example, if a PUSCH repetition is set/indicated for any PUSCH transmission and a slot from which the corresponding PUSCH transmission starts is an SBFD slot by time domain resource assignment information, the UE can be defined to include the SBFD slot when determining a PUSCH repetition transmission slot. On the other hand, in the opposite case, that is, if a PUSCH repetition is set/indicated for any PUSCH transmission and a slot from which the corresponding PUSCH transmission starts is a non-SBFD slot by time domain resource assignment information, the SBFD slot can be not included when determining a PUSCH transmission slot for PUSCH repetition.

In addition, various combinations of the above implicit configuration methods may also be included in the present disclosure. For example, if a slot in which a PUSCH transmission for which PUSCH repetition is set/indicated starts is an SBFD slot, the SBFD slot may be included in determining a PUSCH transmission slot for PUSCH repetition. On the other hand, if the start slot is a non-SBFD slot, whether or not to include the SBFD slot may be additionally determined in determining a PUSCH transmission slot for PUSCH repetition depending on whether a frequency resource allocated for the corresponding PUSCH transmission fully overlaps a UL subband. For example, if fully overlapped, the SBFD slot may be included in determining a PUSCH transmission slot for PUSCH repetition, but if not (i.e., partially overlap or non-overlap), the SBFD slot may not be included in determining a PUSCH transmission slot for PUSCH repetition.

In addition, all combinations of the above explicit setting/indication methods and implicit setting/indication methods may also be included in the scope of the present disclosure. For example, even if the support for PUSCH repetition for the SBFD slot is explicitly set or indicated, whether to include the SBFD slot may be determined when additionally determining a PUSCH transmission slot for PUSCH repetition according to the implicit method. For example, even if the SBFD slot is explicitly set to be included (i.e., not excluded) when determining a PUSCH transmission slot for PUSCH repetition, if the PRB for PUSCH transmission according to the FDRA information of the DCI format does not belong to a UL subband, the SBFD slot may not be included when determining a PUSCH transmission slot for PUSCH repetition (i.e., not included in counting the N K slots for PUSCH repetition).

Additionally, when PUSCH repetition transmission through different slot types is configured/indicated to be supported or when PUSCH repetition transmission support through an SBFD slot is configured/indicated, a new rule for association (or mapping) between frequency resources between a non-SBFD slot and an SBFD slot may be configured or defined. For example, in case of a non-SBFD slot (e.g., a UL slot), frequency resource allocation for PUSCH transmission of a UE in the slot may be performed based on the activated UL BWP of the UE. On the other hand, in an SBFD slot, UL transmission can be performed only through an overlapping region of an activated UL BWP and a UL subband.

Accordingly, when PUSCH repetition transmission through the different slot types is set/instructed to be supported, a frequency domain resource set for PUSCH transmission across the SBFD slot and the non-SBFD slot can be configured in the UL BWP of the corresponding UE. Accordingly, an association (mapping) is made between the PRB of the configured resource set and the PRB constituting the UL subband, or the overlapping PRB (physical resource block) between the UL subband and the UL BWP. At this time, only one resource set is set for any UL BWP, or one or more resource sets are configured so that all frequency resources of the UL BWP, i.e., PRBs, belong to at least one resource set. When one or more resource sets are configured, an association (mapping) is made between the PRB of each resource set and the PRB constituting the UL subband, or the overlapping PRB between the UL subband and the UL BWP. Any resource set configuration information includes start resource block (RB) information and size information on the frequency axis, or includes only start RB information, and the size information can be determined by the size of the UL subband or the size of the frequency resource overlapping the UL subband and the UL BWP.

Additionally, when PUSCH repetition and TB processing over multiple slots are configured/instructed at the same time, the above contents can be equally applied to PUSCH transmission slots according to all TB processing over multiplex slots configurations/instructions belonging to each PUSCH repetition.

In addition, the PUSCH transmission based on the different slot types described above may vary depending on whether intra-slot/inter-slot frequency hopping is applied. For example, the PUSCH transmission based on the different slot types described above may be limited to be supported only when frequency hopping is not applied.

Example 2. Extended slot format configuration

A base station can explicitly define to set or instruct a transmission direction (or extended slot configuration, extended slot format, etc., and is not limited to a specific name) of a terminal in a corresponding slot or symbol for an arbitrary SBFD slot or SBFD symbol. That is, the base station can set or instruct whether a terminal performs a DL reception operation or a UL transmission operation in an SBFD symbol or slot for an arbitrary terminal. For example, the base station can define to transmit UL-DL configuration information of an SBFD slot or symbol to an arbitrary terminal through UE-specific or cell-specific RRC signaling. The configuration information allows UL and DL configuration for the corresponding SBFD slots or symbols based on period information of the SBFD slot or symbol according to the UL subband configuration, and can implicitly mean that an SBFD symbol that is not explicitly set to UL or DL is set to a flexible symbol. Alternatively, the base station may transmit the UL-DL indication information of the corresponding SBFD slot or SBFD symbol to the UE via L1 control signaling. In this case, the UL-DL indication information of the corresponding SBFD slot or SBFD symbol may be indicated via UE-specific DCI or UE-group common DCI.

The transmission direction setting or indication information of the above SBFD slot or symbol may be included in the existing RRC signaling or DCI format, or a separate RRC signaling or DCI format may be defined.

Alternatively, the transmission direction in any SBFD slot or symbol can be implicitly set by the UL subband configuration information. For example, if a UL subband is configured in a DL slot/symbol or a flexible slot/symbol by legacy slot configuration for any terminal, the terminal can implicitly perform a UL transmission operation in the corresponding SBFD slot or symbol. Conversely, if a DL subband is configured, the terminal can perform a DL reception operation in the corresponding SBFD slot or symbol.

As described above, if the transmission direction for any terminal in any SBFD slot or symbol is not set to DL, i.e., UL or flexible, the terminal supports PUSCH transmission in the corresponding SBFD slot or symbol.

Accordingly, when a PUSCH transmission slot is determined in any SBFD slot according to the method of determining a slot for PUSCH transmission for PUSCH repetition by UL grant (e.g., DCI format 0_1, 0_2, etc.) of the aforementioned embodiment 1, the UE can propose the following for the PUSCH transmission operation in the corresponding SBFD slot.

When scheduling for PUSCH transmission in multiple slots by one DCI format for a given UE, if at least one symbol among symbols allocated for PUSCH transmission in any one of the multiple slots is a non-SBFD symbol indicated as DL by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated , or if at least one symbol is an SBFD symbol indicated as DL by the UE-specific or cell-specific extended slot configuration, it can be defined not to transmit PUSCH in the corresponding slot.

That is, when scheduling for PUSCH transmission in multiple slots is performed by one DCI format for a given terminal, if at least one symbol among the symbols allocated for PUSCH transmission in any one of the multiple slots is a symbol indicated as DL by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated for which UL subband configuration has not been performed, or if UL subband configuration has been performed but the base station has configured the symbol to perform DL reception operation, the terminal may not transmit PUSCH in the corresponding slot.

Accordingly, the terminal can define not to perform PUSCH transmission in a slot if at least one or more of the symbols allocated for PUSCH transmission in the slot is set to DL by the extended slot configuration when any SBFD slot is determined as a PUSCH repetition slot by embodiment 1.

Hereinafter, a specific PUSCH repetition operation of a terminal according to the aforementioned method will be described. The terminal receives one or more UL BWP configuration information for uplink transmission from a base station. Additionally, the terminal can receive one UL subband configuration information for uplink transmission and/or SBFD symbol configuration information according to the UL subband configuration information from the base station. The UL subband configuration can be configured in a symbol configured as a DL or flexible symbol by tdd-UL-DL-ConfigurationCommon . The terminal receives activation indication information for one DL BWP and UL BWP pair for uplink transmission from the base station. If UL subband configuration for supporting the SBFD operation is configured in the activated DL/UL BWP pair, or if a DL/UL BWP pair associated with the UL subband configuration is activated, the terminal can additionally receive transmission direction (Tx direction) configuration information in the SBFD symbol.

Any terminal receives the repetition count setting information for PUSCH repetition as described above through RRC signaling or through TDRA in DCI format.

The terminal explicitly or implicitly receives PUSCH repetition enable/disable information from the base station through the different slot types. The different slot types mean an SBFD slot consisting of the SBFD symbols and a non-SBFD slot consisting of non-SBFD symbols. When PUSCH repetition through different slot types is enabled, the terminal can perform repetition across the non-SBFD slot and the SBFD slot for PUSCH repetition based on DCI format 0_1 or 0_2. Additionally, when PUSCH repetition through different slot types is enabled, the terminal can perform repetition across the non-SBFD slot and the SBFD slot for PUSCH repetition based on RAR UL grant. Additionally, when PUSCH repetition through different slot types is enabled, the UE can perform repetition across the non-SBFD slot and the SBFD slot for PUSCH repetition based on reception of DCI format 0_0 scrambled with TC-RNTI.

The repetition enable setting through the different slot types above can be explicitly set by the base station through cell-specific or UE-specific RRC signaling. The repetition enable setting through the different slot types can be explicitly indicated by the base station through the DCI format or UL grant of RAR. Alternatively, the PUSCH repetition enable setting through the different slot types can be implicitly set by FDRA information for the corresponding PUSCH transmission, type information of the first PUSCH transmission slot, information of the DCI format reception slot type including PUSCH scheduling control information, etc. Alternatively, it can be set in the form of a combination of the explicit setting and the implicit setting.

When repetition is disabled through the above different slot types, the slot type in which a random PUSCH repetition is performed can be determined by the reception slot type of the DCI format including the corresponding PUSCH scheduling control information, or by the first PUSCH transmission slot type by the DCI format. Alternatively, the PUSCH repetition slot type setting/indication information can be transmitted by the base station through RRC signaling or through the corresponding DCI format.

Below, specific PUSCH repetition slot counting and PUSCH repetition slot determination methods according to PUSCH repetition enable/disable through the above different slot types are described.

Example 3. When PUSCH repetition through different slot types is disabled and the PUSCH repetition slot is a non-SBFD slot

The terminal receives AvailableSlotCounting information from the base station. If the AvailableSlotCounting is enabled, the terminal can perform slot counting for PUSCH transmission according to the set/indicated PUSCH repetition count and k value when receiving DCI format 0_1, 0_2 from the base station. Specifically, when the terminal counts N K slots for PUSCH transmission based on the DCI format 0_1, 0_2 reception information, the terminal can set N K slots excluding the following slots as PUSCH repetition slots. (Where, N is a TBoMS setting value) If a PUSCH transmission symbol allocated by the DCI format 0_1, 0_2 in any slot includes a symbol set to DL by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, or includes an SS/PBCH block by SSB-PositionInBurst, the slot can be excluded. In other cases, the terminal can set N·K consecutive slots as slots for the corresponding PUSCH repetition.

The terminal can receive PUSCH repetition indication information from the base station through the RAR UL grant. In this case, when the terminal receives the corresponding RAR UL grant, the terminal can perform slot counting in which PUSCH transmission is possible according to the set/indicated PUSCH repetition number and k value. Specifically, when the terminal counts N K slots for PUSCH transmission based on the RAR UL grant reception information, the terminal can set N K slots excluding the following slots as PUSCH repetition slots. If a PUSCH transmission symbol allocated by the RAR UL grant in any slot includes a symbol set to DL by tdd-UL-DL-ConfigurationCommon or includes an SS/PBCH block by SSB-PositionInBurst, the slot can be excluded.

The terminal can receive PUSCH repetition indication information from the base station through CRC scrambled DCI format 0_0 based on TC-RNTI. In this case, when receiving the DCI format 0_0, the terminal can perform slot counting in which PUSCH transmission is possible corresponding to the set/indicated PUSCH repetition count and k value. Specifically, when the terminal counts N K slots for PUSCH transmission based on the DCI format 0_0 reception information, the terminal can set N K slots excluding the following slots as PUSCH repetition slots. If a PUSCH transmission symbol allocated by the DCI format 0_0 in any slot includes a symbol set to DL by tdd-UL-DL-ConfigurationCommon or includes an SS/PBCH block by SSB-PositionInBurst, the slot can be excluded.

Example 4. When PUSCH repetition through different slot types is disabled and the PUSCH repetition slot is an SBFD slot

The terminal receives AvailableSlotCounting information from the base station. If the AvailableSlotCounting is enabled, the terminal can perform slot counting for PUSCH transmission according to the configured/indicated PUSCH repetition count and k value when receiving DCI format 0_1, 0_2 from the base station. Specifically, when the terminal counts N K slots for PUSCH transmission based on the DCI format 0_1, 0_2 reception information, the terminal can set N K slots excluding the following slots as PUSCH repetition slots. (However, N is a TBoMS setting value) If a PUSCH transmission symbol allocated by the DCI format 0_1, 0_2 in any slot includes a non-SBFD symbol for which the UL subband is not configured, an SS/PBCH block by SSB-PositionInBurst, or an SBFD symbol for which DL reception is configured by the base station, the slot is excluded. In other cases, the terminal can set N·K consecutive slots as slots for the corresponding PUSCH repetition.

The terminal can receive PUSCH repetition indication information from the base station through the RAR UL grant. In this case, when the terminal receives the corresponding RAR UL grant, the terminal can perform slot counting in which PUSCH transmission is possible according to the configured/indicated PUSCH repetition number and k value. Specifically, when the terminal counts N K slots for PUSCH transmission based on the RAR UL grant reception information, the terminal can set N K slots excluding the following slots as PUSCH repetition slots. If a PUSCH transmission symbol allocated by the RAR UL grant in any slot includes a non-SBFD symbol for which the UL subband is not configured, an SS/PBCH block by SSB-PositionInBurst, or an SBFD symbol for which DL reception is configured by the base station, the slot can be excluded.

A terminal can receive PUSCH repetition indication information from a base station through CRC scrambled DCI format 0_0 based on TC-RNTI. In this case, when receiving the DCI format 0_0, the terminal can perform slot counting in which PUSCH transmission is possible corresponding to the set/indicated PUSCH repetition count and k value. Specifically, when the terminal counts N K slots for PUSCH transmission based on the DCI format 0_0 reception information, the terminal can set N K slots excluding the following slots as PUSCH repetition slots. If a PUSCH transmission symbol allocated by the DCI format 0_0 in any slot includes a non-SBFD symbol for which the UL subband is not configured, an SS/PBCH block by SSB-PositionInBurst, or an SBFD symbol for which DL reception is configured by the base station, the slot can be excluded.

Example 5. When PUSCH repetition is enabled through different slot types

The terminal can receive AvailableSlotCounting information from the base station. If the AvailableSlotCounting is enabled, the terminal can perform slot counting for PUSCH transmission according to the set/indicated PUSCH repetition count and k value when receiving DCI format 0_1, 0_2 from the base station. Specifically, when counting N K slots for PUSCH transmission based on the DCI format 0_1, 0_2 reception information, the terminal can set N K slots excluding the following slots as PUSCH repetition slots. (Where N is a TBoMS setting value) If a PUSCH transmission symbol allocated by the DCI format 0_1, 0_2 in any slot includes a non-SBFD symbol for which a UL subband is not set to DL by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated , or includes an SBFD symbol for which DL reception is set by the base station, or includes an SS/PBCH block by SSB-PositionInBurst, the slot can be excluded. In other cases, the UE can set N·K consecutive slots as slots for the corresponding PUSCH repetition.

The terminal can receive PUSCH repetition indication information from the base station through the RAR UL grant. In this case, when the terminal receives the corresponding RAR UL grant, the terminal can perform slot counting in which PUSCH transmission is possible according to the set/indicated PUSCH repetition number and k value. Specifically, when the terminal counts N K slots for PUSCH transmission based on the RAR UL grant reception information, the terminal can set N K slots excluding the following slots as PUSCH repetition slots. If a PUSCH transmission symbol allocated by the RAR UL grant in any slot includes a non-SBFD symbol in which a UL subband is not set to DL by tdd-UL-DL-ConfigurationCommon , an SBFD symbol in which DL reception is set by the base station, or an SS/PBCH block by SSB-PositionInBurst, the slot can be excluded.

The terminal can receive PUSCH repetition indication information from the base station through CRC scrambled DCI format 0_0 based on TC-RNTI. In this case, when the terminal receives the DCI format 0_0, the terminal can perform slot counting in which PUSCH transmission is possible corresponding to the set/indicated PUSCH repetition count and k value. Specifically, when the terminal counts N K slots for PUSCH transmission based on the DCI format 0_0 reception information, the terminal can set N K slots excluding the following slots as PUSCH repetition slots. If a PUSCH transmission symbol allocated by the DCI format 0_0 in any slot includes a non-SBFD symbol in which a UL subband is not configured as DL by tdd-UL-DL-ConfigurationCommon, an SBFD symbol in which DL reception is configured by the base station, or an SS/PBCH block by SSB-PositionInBurst, the slot can be excluded.

Additionally, when PUSCH repetition is set for an arbitrary terminal and PUSCH repetition through different slot types is explicitly or implicitly enabled by the base station, a separate DCI format (e.g., DCI format 0_x) may be newly defined for this. When the corresponding DCI format is defined, the information field of the corresponding DCI format may be divided into a slot-type common information area and a slot-type specific information area. The slot-type common information area is an information area that can be set and applied identically to PUSCH transmission in a non-SBFD slot and PUSCH transmission in an SBFD slot and may have a single setting value within the corresponding DCI format. For example, a TDRA information area may be a slot-type common information area and may include a single information area as in the past. On the other hand, the slot type specific information area is an information area that is separately set and applied for PUSCH transmission in a non-SBFD slot and PUSCH transmission in an SBFD slot, and the same information area can have a setting value for a non-SBFD slot and a separate setting value for an SBFD slot, respectively. For example, FDRA, TCI field, etc. can be slot type specific information areas. However, regardless of the above example, when configuring DCI format 0_x, all combinations in which a specific information area is commonly applied to the slot type through a setting value and some other information areas are separately set for each slot type can be included in the present invention.

All of the above examples have been described with respect to slots on the time axis, but the same can be applied to various time resource units such as symbols, subframes, and frames.

With respect to the above-described embodiments, each embodiment is included in the scope of the invention according to the present disclosure not only when it is independent, but also when all examples formed by a combination of the embodiments are included.

Hereinafter, the configuration of a terminal and a base station capable of performing some or all of the embodiments described with reference to FIGS. 1 to 11 will be described with reference to the drawings. The above description may be omitted to avoid redundant description, and in this case, the omitted content may be substantially equally applied to the following description as long as it does not contradict the technical idea of the invention.

Fig. 12 is a drawing showing the configuration of a terminal (1200) according to another embodiment.

Referring to FIG. 12, a terminal (1200) according to another embodiment includes a transmitter (1220), a receiver (1230), and a control unit (1210) that controls the operations of the transmitter and receiver.

The control unit (1210) controls the overall operation of the terminal (1200) according to the method of repeatedly transmitting an uplink data channel in full-duplex communication required to perform the present invention described above.

The control unit (1210) can receive TDD (Time Division Duplex) configuration information and subband configuration information. The control unit (1210) can receive TDD configuration information from a base station to determine a format of a symbol. In this case, the TDD configuration information can include configuration information regarding a format of a slot and configuration information for determining a format of a symbol within a slot, and the information can be received through upper layer signaling or physical layer (L1) signaling.

In addition, the control unit (1210) can receive terminal-specific RRC signaling that reassigns flexible symbols among symbols set through cell-specific RRC signaling to uplink symbols, downlink symbols, or flexible symbols for each terminal.

Alternatively, the control unit (1210) may be instructed to a dynamic slot format via a UE-group common PDCCH. As an example, the control unit (1210) may be instructed to a slot format dynamically via DCI format 2_0.

The control unit (1210) may receive subband configuration information for full-duplex communication. That is, it may receive configuration information for configuring a downlink subband in an uplink slot or configuring an uplink subband in a downlink slot. The subband configuration information may include information about a frequency domain in which an uplink subband or a downlink subband is configured and information about a time domain. Alternatively, the subband configuration information may include information about a frequency domain in which a guard band is configured and information about a time domain.

The control unit (1210) may receive PUSCH configuration information including PUSCH repetitive transmission information. The control unit (1210) may receive PUSCH configuration information that sets or instructs repetitive transmission of the PUSCH from the base station. According to an example, repetitive transmission of the PUSCH may mean a case where one PUSCH transmission is made through multiple slots.

For example, the UE may receive, from the base station, a pusch-AggregationFactor configuration, which is an RRC parameter for semi-statically configuring repetitive transmission for PUSCH. Alternatively, the UE may receive, from the base station, a dynamic indication of repetitive transmission for PUSCH through a time domain resource allocation (TDRA) indication information field of an uplink grant (UL grant).

In this way, through PUSCH configuration information, one PUSCH transmission can be set or instructed to be performed through multiple slots.

The control unit (1210) may determine a plurality of valid slots for repeatedly transmitting a PUSCH based on the PUSCH configuration information. In addition, the control unit (1210) may transmit the PUSCH through at least some of the determined plurality of valid slots. The plurality of valid slots may be slots in which all symbols allocated for PUSCH transmission in each slot are set to uplink (UL) or flexible non-SBFD (subband full duplex) symbols by TDD configuration information that do not include SSB reception symbols. Alternatively, the plurality of valid slots may be slots set to downlink (DL) by TDD configuration information and reset to SBFD symbols in which an uplink subband is configured by subband configuration information. Alternatively, the plurality of valid slots may include both slots in which symbols allocated for PUSCH transmission in each slot are set to non-SBFD symbols and slots reset to SBFD symbols.

Accordingly, the control unit (1210) can determine the plurality of valid slots based on the configuration of the base station, depending on whether to include both a slot consisting of SBFD symbols (SBFD slot) and a slot consisting of non-SBFD symbols (non-SBFD slot). To this end, the control unit (1210) can receive enable/disable information of PUSCH repetitive transmission through different slot types explicitly or implicitly from the base station.

The control unit (1210) can explicitly receive the activation of PUSCH repeated transmission through different slot types from the base station through cell-specific or UE-specific RRC signaling. Alternatively, the control unit (1210) can explicitly receive the activation of PUSCH repeated transmission through different slot types from the base station through a DCI format or an uplink grant of RAR. Alternatively, the activation of PUSCH repeated transmission through different slot types can be implicitly set by FDRA information for PUSCH transmission, type information of a first PUSCH transmission slot, information of a DCI format reception slot type including PUSCH scheduling control information, etc. Alternatively, it can be set in the form of a combination of the explicit and implicit settings described above.

When PUSCH repetitive transmission through different slot types is activated, the control unit (1210) may include non-SBFD slots and SBFD slots together when counting multiple valid slots in which PUSCH transmission is possible. However, the control unit (1210) may determine multiple valid slots excluding slots in which symbols allocated for PUSCH transmission within a slot include symbols set or instructed to be received for downlink by a base station among SBFD symbols.

When PUSCH repetition transmission through different slot types is enabled, the control unit (1210) can perform repetition transmission across non-SBFD slots and SBFD slots for PUSCH repetition based on DCI format 0_1 or 0_2. In addition, when PUSCH repetition transmission through different slot types is enabled, the control unit (1210) can perform repetition transmission across non-SBFD slots and SBFD slots for PUSCH repetition based on RAR uplink grant. Additionally, when PUSCH repetition transmission through different slot types is enabled, the control unit (1210) can perform repetition transmission across non-SBFD slots and SBFD slots for PUSCH repetition based on reception of DCI format 0_0 scrambled with TC-RNTI.

In another example, when PUSCH repetitive transmission through different slot types is disabled, the control unit (1210) may determine a plurality of valid slots based on only one of the slot types distinguished as a slot including an SBFD symbol or a slot including a non-SBFD symbol. That is, the plurality of valid slots used for repetitive transmission of the PUSCH may be counted only as SBFD slots or only as non-SBFD slots.

In this case, the slot type for determining a plurality of valid slots used for repeated transmission of the PUSCH may be set or indicated by the base station, determined by the type of a symbol in which downlink control information including scheduling information of the PUSCH is received, or determined by the symbol type of the first slot among the plurality of valid slots.

If PUSCH repetition transmission through different slot types is disabled, the control unit (1210) can perform repetition transmission across any one of slot types among non-SBFD slots and SBFD slots for PUSCH repetition based on DCI format 0_1 or 0_2. In addition, if PUSCH repetition transmission through different slot types is disabled, the control unit (1210) can perform repetition transmission across any one of slot types among non-SBFD slots and SBFD slots for PUSCH repetition based on RAR uplink grant. Additionally, if PUSCH repetition transmission through different slot types is disabled, the control unit (1210) can perform repetition transmission across any one of slot types among non-SBFD slots and SBFD slots for PUSCH repetition based on reception of DCI format 0_0 scrambled with TC-RNTI.

For example, when a plurality of valid slots for repeated transmission of a PUSCH include both slots including SBFD symbols and slots including non-SBFD symbols, the control unit (1210) may transmit the PUSCH according to downlink control information defined separately for repeated transmission of the PUSCH.

That is, when PUSCH repetition is set for a terminal and PUSCH repetition through different slot types is explicitly or implicitly activated by the base station, a separate DCI format, such as DCI format 0_x, may be newly defined for this purpose. When the DCI format is defined separately, the information field of the corresponding DCI format may be configured to be divided into a slot-type common information area and a slot-type specific information area.

In this case, the slot type common information area may be an information area that can be set and applied identically to PUSCH transmission in a non-SBFD slot and PUSCH transmission in an SBFD slot. Accordingly, it may have one setting value within the corresponding DCI format.

On the other hand, a slot type-specific information area may be an information area that is separately set and applied for PUSCH transmission in a non-SBFD slot and PUSCH transmission in an SBFD slot, respectively. Accordingly, the same information area may have a setting value for a non-SBFD slot and a separate setting value for an SBFD slot, respectively.

However, the above-mentioned content is an example, and all combinations in which, when configuring DCI format 0_x, a specific information area is applied commonly to slot types through setting values and other information areas are set separately for each slot type can be included in the present invention.

After determining a plurality of valid slots for repeatedly transmitting a PUSCH, the control unit (1210) can repeatedly transmit the PUSCH to the base station through at least some of the determined plurality of valid slots. That is, the terminal counts a plurality of valid slots that can be used for repeatedly transmitting a PUSCH, and can repeatedly transmit the PUSCH using all or some of the plurality of valid slots according to a situation set for the terminal.

According to this, a method and device for efficiently performing repeated transmission and reception of an uplink data channel in a slot or symbol to which full-duplex communication is applied can be provided.

Fig. 13 is a drawing showing the configuration of a base station (1300) according to another embodiment.

Referring to FIG. 13, a base station (1300) according to another embodiment includes a transmitter (1320), a receiver (1330), and a control unit (1310) that controls the operations of the transmitter and receiver.

The control unit (1310) controls the overall operation of the base station (1300) according to the method of repeatedly receiving an uplink data channel in full-duplex communication required to perform the above-described present invention. The transmitter (1320) transmits downlink control information, data, and messages to the terminal through the corresponding channel. The receiver (1330) receives uplink control information, data, and messages from the terminal through the corresponding channel.

The control unit (1310) can transmit TDD (Time Division Duplex) configuration information and subband configuration information. The control unit (1310) can transmit TDD configuration information to the terminal to determine the format of a symbol in a slot. In this case, the TDD configuration information can include configuration information regarding the format of the slot and configuration information for determining the format of a symbol in the slot, and the corresponding information can be received through upper layer signaling or physical layer (L1) signaling.

Alternatively, the control unit (1310) may indicate a dynamic slot format via a UE-group common PDCCH. As an example, the control unit (1310) may indicate a slot format dynamically via DCI format 2_0.

The control unit (1310) may transmit subband configuration information for full-duplex communication to the terminal. That is, configuration information for configuring a downlink subband in an uplink slot or configuring an uplink subband in a downlink slot may be transmitted. The subband configuration information may include information about a frequency domain in which an uplink subband or a downlink subband is configured and information about a time domain. Alternatively, the subband configuration information may include information about a frequency domain in which a guard band is configured and information about a time domain.

The control unit (1310) may transmit PUSCH configuration information including PUSCH repetitive transmission information. The control unit (1310) may transmit PUSCH configuration information that sets or instructs repetitive transmission of the PUSCH to the terminal. According to an example, repetitive transmission of the PUSCH may mean a case where one PUSCH transmission is made through multiple valid slots.

For example, the base station may transmit to the terminal the pusch-AggregationFactor setting, which is an RRC parameter for semi-statically setting repetitive transmission for PUSCH. Alternatively, the base station may dynamically indicate repetitive transmission for PUSCH through the time domain resource allocation (TDRA) indication information field of the uplink grant (UL grant).

In this way, through PUSCH configuration information, one PUSCH transmission can be set or instructed to be performed through multiple valid slots.

The control unit (1310) can set whether to activate repetitive transmission of PUSCH through slots of different slot types. In addition, the control unit (1310) can receive PUSCH through a plurality of valid slots determined based on whether to activate repetitive transmission of PUSCH. The plurality of valid slots may be slots in which symbols allocated for PUSCH transmission in each slot are all set to uplink (UL) or flexible non-SBFD (subband full duplex) symbols by TDD configuration information that do not include SSB reception symbols. Alternatively, the plurality of valid slots may be slots set to downlink (DL) by TDD configuration information and reset to SBFD symbols in which uplink subbands are configured by subband configuration information. Alternatively, the plurality of valid slots may include both slots in which symbols allocated for PUSCH transmission in each slot are set to non-SBFD symbols and slots reset to SBFD symbols.

Accordingly, the terminal can determine the plurality of valid slots based on whether to include both a slot consisting of SBFD symbols (SBFD slot) and a slot consisting of non-SBFD symbols (non-SBFD slot) in the plurality of valid slots based on the configuration of the base station. To this end, the control unit (1310) can explicitly or implicitly transmit to the terminal information on enabling/disabling PUSCH repeated transmission through different slot types.

The control unit (1310) can explicitly set the activation of PUSCH repeated transmission through different slot types through cell-specific or UE-specific RRC signaling. Alternatively, the control unit (1310) can explicitly indicate the activation of PUSCH repeated transmission through different slot types through a DCI format or an uplink grant of an RAR. Alternatively, the activation of PUSCH repeated transmission through different slot types can be implicitly set by FDRA information for PUSCH transmission, type information of a first PUSCH transmission slot, information of a DCI format reception slot type including PUSCH scheduling control information, etc. Alternatively, it can be set in the form of a combination of the explicit and implicit settings described above.

When PUSCH repetitive transmission through different slot types is activated, the terminal may include non-SBFD slots and SBFD slots together when counting multiple valid slots in which PUSCH transmission is possible. However, the terminal may determine multiple valid slots excluding slots in which symbols allocated for PUSCH transmission within a slot include symbols set or instructed to receive downlink by the control unit (1310) among SBFD symbols.

When PUSCH repetition transmission through different slot types is enabled, the control unit (1310) can perform repetition reception across non-SBFD slots and SBFD slots for PUSCH repetitions based on DCI format 0_1 or 0_2. In addition, when PUSCH repetition transmission through different slot types is enabled, the control unit (1310) can perform repetition reception across non-SBFD slots and SBFD slots for PUSCH repetitions based on RAR uplink grant. Additionally, when PUSCH repetition transmission through different slot types is enabled, the control unit (1310) can perform repetition reception across non-SBFD slots and SBFD slots for PUSCH repetitions based on DCI format 0_0 transmission scrambled with TC-RNTI.

In another example, when PUSCH repetitive transmission through different slot types is disabled, the UE may determine a plurality of valid slots based on only one of the slot types distinguished as a slot including an SBFD symbol or a slot including a non-SBFD symbol. That is, the plurality of valid slots used for the repetitive transmission of the PUSCH may be counted as only SBFD slots or as only non-SBFD slots.

In this case, the slot type for determining a plurality of valid slots used for repeated transmission of the PUSCH may be set or indicated by the base station, determined by the type of a symbol in which downlink control information including scheduling information of the PUSCH is received, or determined by the symbol type of the first slot among the plurality of valid slots.

When PUSCH repetition transmission through different slot types is disabled, the control unit (1310) can perform repetition reception across any one of the slot types of the non-SBFD slot and the SBFD slot for PUSCH repetition based on DCI format 0_1 or 0_2. In addition, when PUSCH repetition transmission through different slot types is disabled, the control unit (1310) can perform repetition reception across any one of the slot types of the non-SBFD slot and the SBFD slot for PUSCH repetition based on RAR uplink grant. Additionally, when PUSCH repetition transmission through different slot types is disabled, the control unit (1310) can perform repetition reception across any one of the slot types of the non-SBFD slot and the SBFD slot for PUSCH repetition based on DCI format 0_0 transmission scrambled with TC-RNTI.

For example, if a plurality of valid slots for repeated transmission of a PUSCH include both slots including SBFD symbols and slots including non-SBFD symbols, the control unit (1310) may define separate downlink control information for repeated transmission of the PUSCH.

That is, when PUSCH repetition is set for a terminal and PUSCH repetition through different slot types is explicitly or implicitly activated by the control unit (1310), a separate DCI format, for example, DCI format 0_x, may be newly defined for this purpose. When the DCI format is defined separately, the information field of the corresponding DCI format may be configured to be divided into a slot-type common information area and a slot-type specific information area.

In this case, the slot type common information area may be an information area that can be set and applied identically to PUSCH transmission in a non-SBFD slot and PUSCH transmission in an SBFD slot. Accordingly, it may have one setting value within the corresponding DCI format.

On the other hand, a slot type-specific information area may be an information area that is separately set and applied for PUSCH transmission in a non-SBFD slot and PUSCH transmission in an SBFD slot, respectively. Accordingly, the same information area may have a setting value for a non-SBFD slot and a separate setting value for an SBFD slot, respectively.

However, the above-mentioned content is an example, and all combinations in which, when configuring DCI format 0_x, a specific information area is applied commonly to slot types through setting values and other information areas are set separately for each slot type can be included in the present invention.

When multiple valid slots for repeated transmission of PUSCH are determined from the terminal, the control unit (1310) can repeatedly receive PUSCH through at least some of the determined multiple valid slots. That is, the base station can repeatedly receive PUSCH using all or some of the multiple valid slots that can be used for repeated transmission of PUSCH counted from the terminal.

According to this, a method and device for efficiently performing repeated transmission and reception of an uplink data channel in a slot or symbol to which full-duplex communication is applied can be provided.

The above-described embodiments can be supported by standard documents disclosed in at least one of the wireless access systems IEEE 802, 3GPP and 3GPP2. That is, steps, components and parts that are not described in order to clearly reveal the technical idea of the present embodiments can be supported by the above-described standard documents. In addition, all terms disclosed in the present specification can be explained by the above-described standard documents.

The above-described embodiments can be implemented through various means. For example, the embodiments can be implemented by hardware, firmware, software, or a combination thereof.

In the case of hardware implementation, the method according to the present embodiments can be implemented by one or more ASICs (Application Specific Integrated Circuits), DSPs (Digital Signal Processors), DSPDs (Digital Signal Processing Devices), PLDs (Programmable Logic Devices), FPGAs (Field Programmable Gate Arrays), processors, controllers, microcontrollers, or microprocessors.

In the case of implementation by firmware or software, the method according to the present embodiments may be implemented in the form of a device, procedure, or function that performs the functions or operations described above. The software code may be stored in a memory unit and may be driven by a processor. The memory unit may be located inside or outside the processor and may exchange data with the processor by various means already known.

Additionally, the terms "system", "processor", "controller", "component", "module", "interface", "model", or "unit" as described above may generally refer to a computer-related entity hardware, a combination of hardware and software, software, or software in execution. For example, the aforementioned components may be, but are not limited to, a process driven by a processor, a processor, a controller, a control processor, an object, a thread of execution, a program, and/or a computer. For example, an application running on a controller or a processor and the controller or the processor can both be components. One or more components may be within a process and/or thread of execution, and the components may be located on a single device (e.g., a system, a computing device, etc.) or distributed across two or more devices.

The above description is merely an example of the technical idea of the present disclosure, and those skilled in the art to which the present disclosure pertains may make various modifications and variations without departing from the essential characteristics of the technical idea of the present disclosure. In addition, the present embodiments are not intended to limit the technical idea of the present disclosure but to explain it, and therefore the scope of the technical idea of the present disclosure is not limited by these embodiments. The protection scope of the present disclosure should be interpreted by the claims below, and all technical ideas within a scope equivalent thereto should be interpreted as being included in the scope of the rights of the present disclosure.

CROSS-REFERENCE TO RELATED APPLICATION

This patent application claims the benefit of, under 35 U.S.C. §119(a) of, Korean patent application No. 10-2023-0046110, filed in Korea on April 7, 2023, and Korean patent application No. 10-2024-0046574, filed in Korea on April 5, 2024, the entire contents of which are incorporated herein by reference. In addition, this patent application claims priority with respect to countries other than the United States for the same reasons, the entire contents of which are incorporated herein by reference.

Claims (20)

In a method for a terminal to transmit an uplink data channel (Physical Uplink Shared Channel; PUSCH) in full duplex communication, A step of receiving TDD (Time Division Duplex) configuration information and subband configuration information; A step of receiving PUSCH configuration information including PUSCH repetition transmission information; A step of determining a plurality of available slots for repeatedly transmitting the PUSCH based on the PUSCH configuration information; and Including a step of transmitting the PUSCH through at least some slots among the determined plurality of valid slots, A method wherein the plurality of valid slots include at least one of slots in which a symbol allocated for the PUSCH transmission within each slot is set to an uplink (UL) or flexible non-SBFD (subband full duplex) symbol by the TDD configuration information that does not include an SSB reception symbol, or a slot set to a downlink (DL) symbol by the TDD configuration information and reset to an SBFD symbol in which an uplink subband is configured by the subband configuration information. In the first paragraph, The step of determining the above multiple valid slots is: A method for determining the plurality of valid slots based on the configuration of the base station, depending on whether the plurality of valid slots include both slots composed of the SBFD symbols and slots composed of the non-SBFD symbols. In the first paragraph, The step of determining the above multiple valid slots is: A method for determining a plurality of valid slots, excluding slots that include symbols set or instructed to receive downlink by a base station among the SBFD symbols, for the PUSCH transmission. In the first paragraph, The step of determining the above multiple valid slots is: A method for determining the plurality of valid slots based on only one of slot types, which is distinguished as a slot including the SBFD symbol or a slot including the non-SBFD symbol. In paragraph 4, The above slot types are, A method in which downlink control information including scheduling information of the PUSCH is determined by the type of a symbol received, or by the symbol type of a first slot among the plurality of valid slots, or is set or instructed by a base station. In the first paragraph, The step of transmitting the above PUSCH is: A method for transmitting the PUSCH according to downlink control information separately defined for repeated transmission of the PUSCH, when the plurality of valid slots include both slots including the SBFD symbol and slots including the non-SBFD symbol. In Article 6 The separately defined downlink control information above is: A method of dividing into a slot type common information area and a slot type specific information area. In a method for a base station to receive an uplink data channel (Physical Uplink Shared Channel; PUSCH) in full duplex communication, A step for transmitting TDD (Time Division Duplex) configuration information and subband configuration information; A step of transmitting PUSCH configuration information including PUSCH repetition transmission information; A step for setting whether to enable repeated transmission of the PUSCH through slots of different slot types; and A step of receiving the PUSCH through at least some of the slots among a plurality of available slots determined based on whether the repeated transmission of the PUSCH is activated, A method wherein the plurality of valid slots include at least one of slots in which a symbol allocated for the PUSCH transmission within each slot is set to an uplink (UL) or flexible non-SBFD (subband full duplex) symbol by the TDD configuration information that does not include an SSB reception symbol, or a slot set to a downlink (DL) symbol by the TDD configuration information and reset to an SBFD symbol in which an uplink subband is configured by the subband configuration information. In Article 8, The above multiple valid slots are, A method for determining whether to include both slots composed of the SBFD symbols and slots composed of the non-SBFD symbols in the plurality of valid slots based on the configuration of the base station. In Article 8, The above multiple valid slots are, A method in which a slot including a symbol set or instructed to receive downlink by the base station among the SBFD symbols is excluded from the symbols allocated for the PUSCH transmission. In Article 8, The above multiple valid slots are, A method determined based on only one of slot types, which is distinguished as a slot including the above SBFD symbol or a slot including the above non-SBFD symbol. In Article 11, The above slot types are, A method in which downlink control information including scheduling information of the PUSCH is determined by the type of a symbol received, or by the symbol type of a first slot among the plurality of valid slots, or is set or instructed by a base station. In Article 8, The step of receiving the above PUSCH is: A method for receiving the PUSCH according to downlink control information separately defined for the PUSCH repetition transmission, when the plurality of valid slots include both slots including the SBFD symbol and slots including the non-SBFD symbol. In Article 13 The separately defined downlink control information above is: A method of dividing into a slot type common information area and a slot type specific information area. In a terminal transmitting an uplink data channel (Physical Uplink Shared Channel; PUSCH) in full duplex communication, Transmitter; Receiver; and Including a control unit that controls the operation of the above transmitter and the above receiver, The above control unit, Receive TDD (Time Division Duplex) configuration information and subband configuration information, receive PUSCH configuration information including PUSCH repetition transmission information, determine a plurality of available slots for repeatedly transmitting the PUSCH based on the PUSCH configuration information, and transmit the PUSCH through at least some of the determined plurality of available slots. The terminal wherein the plurality of available slots include at least one of slots in which a symbol allocated for the PUSCH transmission within each slot is set to an uplink (UL) or flexible non-SBFD (subband full duplex) symbol by the TDD configuration information that does not include an SSB reception symbol, or a slot set to a downlink (DL) symbol by the TDD configuration information and reset to an SBFD symbol in which an uplink subband is configured by the subband configuration information. In Article 15, The above control unit, A terminal that determines the plurality of valid slots based on whether to include both a slot composed of the SBFD symbols and a slot composed of the non-SBFD symbols in the plurality of valid slots, based on the settings of the base station. In Article 15, The above control unit, A terminal for determining the plurality of valid slots, excluding slots including symbols set or instructed to receive downlink by a base station among the SBFD symbols, for the PUSCH transmission. In Article 15, The above control unit, A terminal that determines the plurality of valid slots based on only one of slot types, which is distinguished as a slot including the SBFD symbol or a slot including the non-SBFD symbol. In Article 18, The above slot types are, A terminal whose downlink control information including scheduling information of the PUSCH is determined by the type of symbol received, or which is set or instructed by the base station, or which is determined by the symbol type of the first slot among the plurality of valid slots. In Article 15, The above control unit, A terminal that transmits the PUSCH according to downlink control information separately defined for the PUSCH repetition transmission, when the plurality of valid slots include both slots including the SBFD symbol and slots including the non-SBFD symbol.

Images