Method and device for scheduling at least one uplink data channel for full-duplex communication

Abstract

Provided are a method and device for performing an operation for physical uplink shared channel (PUSCH) transmission in a wireless communication system. A terminal receives, from a base station, time duplex division (TDD) configuration information, UL bandwidth part (BWP) configuration information, and UL subband configuration information. In addition, the terminal receives, from the base station, downlink control information (DCI) including scheduling information for at least one PUSCH transmission. Then, the terminal determines a slot for the at least one PUSCH transmission on the basis of the received DCI.

Description

Method and device for scheduling at least one uplink data channel for full-duplex communication

[0001] This specification relates to wireless communications applicable to 5G NR, 5G-Advanced and 6G.

[0002] As more and more communication devices demand ever-increasing communication traffic, the need for next-generation 5G systems, which offer enhanced wireless broadband communication capabilities over existing LTE systems, is growing. This next-generation 5G system, known as NewRAT, differentiates communication scenarios into Enhanced Mobile BroadBand (eMBB), Ultra-reliability and low-latency communication (URLLC), and Massive Machine-Type Communications (mMTC).

[0003] Here, eMBB is a next-generation mobile communication scenario with characteristics such as High Spectrum Efficiency, High User Experienced Data Rate, and High Peak Data Rate; URLLC is a next-generation mobile communication scenario with characteristics such as Ultra Reliable, Ultra Low Latency, and Ultra High Availability (e.g., V2X, Emergency Service, and Remote Control); and mMTC is a next-generation mobile communication scenario with characteristics such as Low Cost, Low Energy, Short Packet, and Massive Connectivity (e.g., IoT).

[0004] An object of the present specification is to provide a method and device capable of efficiently performing an operation for allocating at least one uplink data channel for full duplex communication, i.e., a physical uplink shared channel (PUSCH) transmission resource and transmitting PUSCH based thereon.

[0005] One embodiment of the present specification provides a method for providing a wireless communication system, wherein a terminal receives TDD (time duplex division) configuration information, UL BWP (bandwidth part) configuration information, and UL subband configuration information from a base station. Furthermore, the terminal receives DCI (downlink control information) including scheduling information for at least one PUSCH transmission from the base station. Thereafter, the terminal determines a slot for at least one PUSCH transmission based on the received DCI. Here, the slot for the at least one PUSCH transmission is determined by whether an invalid symbol is included in a PUSCH transmission symbol within the slot according to scheduling information included in the DCI, and the invalid symbol is determined based on subband full duplex (SBFD) symbol information according to the UL subband configuration information associated with the TDD configuration information and the UL BWP.

[0006] In addition, one embodiment of the present invention provides a wireless communication system, comprising at least one processor, and at least one memory storing instructions and being operably electrically connected to the at least one processor, wherein operations performed based on the instructions being executed by the at least one processor include: receiving TDD (time duplex division) configuration information, UL BWP (bandwidth part) configuration information, and UL subband configuration information from a base station. In addition, receiving DCI (downlink control information) including scheduling information for at least one PUSCH transmission from the base station. Thereafter, a slot for at least one PUSCH transmission is determined based on the received DCI. Here, a slot for the at least one PUSCH transmission is determined by whether an invalid symbol is included in a PUSCH transmission symbol within the slot according to scheduling information included in the DCI, and the invalid symbol is determined based on subband full duplex (SBFD) symbol information by the TDD configuration information and the UL subband configuration information associated with the UL BWP.

[0007] PUSCH transmission may not be performed in a slot containing the invalid symbol.

[0008] Meanwhile, the invalid symbol may include a non-SBFD symbol for which a UL subband is not configured among downlink (DL) symbols according to the TDD configuration information.

[0009] On the other hand, the invalid symbol may include a symbol in which a UL subband is set among the downlink (DL) symbols according to the TDD setting information, and a symbol instructed and / or set to receive DL by the base station.

[0010] On the other hand, the invalid symbol includes i) a non-SBFD symbol among downlink (DL) symbols according to the TDD configuration information in which a UL subband is not configured, and ii) a symbol among downlink (DL) symbols according to the TDD configuration information in which a UL subband is configured, and a symbol instructed and / or configured to perform DL reception by a base station, and a symbol not included in the invalid symbol may be a valid PUSCH transmission symbol.

[0011] On the other hand, the invalid symbol may be any non-SBFD symbol for which no UL subband is configured, or any SBFD symbol for which the UL subband is configured. Here, whether to transmit PUSCH for the non-SBFD symbol and / or the SBFD symbol may be determined based on i) an indication through the DCI, ii) a symbol type of a first PUSCH transmission by the DCI, or iii) a symbol type in which the DCI is transmitted.

[0012] The above DCI may be in a format including i) a scheduling information area in a slot type composed of SBFD symbols, ii) a scheduling information area in a slot type composed of non-SBFD symbols, and iii) an information area common to the slot types.

[0013] According to the disclosure of the present specification, in a wireless communication system supporting full duplex communication, it is possible to efficiently perform an operation for allocating at least one uplink data channel, i.e., a physical uplink shared channel (PUSCH) transmission resource and transmitting the PUSCH based thereon.

[0014] Figure 1 is a diagram illustrating a wireless communication system.

[0015] Figure 2 illustrates the structure of a radio frame used in NR.

[0016] Figures 3a to 3c are exemplary diagrams showing exemplary architectures for wireless communication services.

[0017] Figure 4 illustrates the slot structure of an NR frame.

[0018] Figure 5 illustrates an example of subframe types in NR.

[0019] Figure 6 illustrates the structure of a self-contained slot.

[0020] Figures 7a and 7b are schematic examples of subband full duplex communication.

[0021] FIGS. 8A and 8B illustrate examples of setting uplink (UL) subbands in downlink (DL) slots according to one embodiment of the present specification.

[0022] Figure 9 illustrates an operation method of a terminal according to one embodiment of the present specification.

[0023] Figure 10 illustrates a device according to one embodiment of the present specification.

[0024] Fig. 11 is a block diagram showing the configuration of a terminal according to one embodiment of the present specification.

[0025] Figure 12 shows a block diagram of a processor in which the disclosure of this specification is implemented.

[0026] FIG. 13 is a block diagram showing in detail the transmitter / receiver of the first device illustrated in FIG. 10 or the transmitter / receiver unit of the device illustrated in FIG. 11.

[0027] It should be noted that the technical terms used in this specification are used merely to describe specific embodiments and are not intended to limit the contents of this specification. In addition, unless specifically defined otherwise herein, the technical terms used in this specification should be interpreted as having a meaning generally understood by those skilled in the art to which this specification pertains, and should not be interpreted in an excessively broad or narrow sense. In addition, if a technical term used in this specification is an incorrect technical term that does not accurately express the contents and ideas of this specification, it should be replaced with a technical term that can be correctly understood by a person skilled in the art. In addition, general terms used in this specification should be interpreted according to their dictionary definitions or according to the preceding and following context, and should not be interpreted in an excessively narrow sense.

[0028] Additionally, the singular expressions used herein include plural expressions unless the context clearly dictates otherwise. In this application, terms such as "consist of" or "have" should not be construed to necessarily include all of the components or steps described in the specification, and should be construed to mean that some of the components or steps may not be included, or that additional components or steps may be included.

[0029] Additionally, terms including ordinal numbers, such as "first" and "second," used herein may be used to describe various components, but these components should not be limited by these terms. These terms are used solely to distinguish one component from another. For example, without departing from the scope of the present invention, a first component could be referred to as a second component, and similarly, a second component could also be referred to as a first component.

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

[0031] Hereinafter, embodiments will be described in detail with reference to the attached drawings. Regardless of the drawing reference numerals, identical or similar components will be given the same reference numerals, and redundant descriptions thereof will be omitted. In addition, when describing the contents of this specification, if a detailed description of a related known technology is judged to obscure the gist of this specification, the detailed description thereof will be omitted. In addition, it should be noted that the attached drawings are only intended to make the contents and ideas of this specification easily understandable, and should not be construed as limiting the contents and ideas of this specification by the attached drawings. The contents and ideas of this specification should be construed to extend to all changes, equivalents, and substitutes other than the attached drawings.

[0032] In this specification, “A or B” can mean “only A,” “only B,” or “both A and B.” In other words, “A or B” in this specification can be interpreted as “A and / or B.” For example, “A, B or C” in this specification can mean “only A,” “only B,” “only C,” or “any combination of A, B, and C.”

[0033] As used herein, a slash ( / ) or a comma can mean "and / or." For example, "A / B" can mean "A and / or B." Accordingly, "A / B" can mean "only A," "only B," or "both A and B." For example, "A, B, C" can mean "A, B, or C."

[0034] In this specification, “at least one of A and B” may mean “only A,” “only B,” or “both A and B.” Additionally, in this specification, the expressions “at least one of A or B” or “at least one of A and / or B” may be interpreted identically to “at least one of A and B.”

[0035] Additionally, in this specification, “at least one of A, B and C” can mean “only A,” “only B,” “only C,” or “any combination of A, B and C.” Additionally, “at least one of A, B or C” or “at least one of A, B and / or C” can mean “at least one of A, B and C.”

[0036] Additionally, parentheses used in this specification may mean “for example.” Specifically, when “control information (PDCCH)” is indicated, “PDCCH (Physical Downlink Control Channel)” may be suggested as an example of “control information.” In other words, “control information” in this specification is not limited to “PDCCH,” and “PDDCH” may be suggested as an example of “control information.” Furthermore, even when indicated as “control information (i.e., PDCCH),” “PDCCH” may be suggested as an example of “control information.”

[0037] Technical features individually described in a single drawing in this specification may be implemented individually or simultaneously.

[0038] Although the attached drawing illustrates a UE (User Equipment) as an example, the illustrated UE may also be referred to as a terminal, ME (Mobile Equipment), etc. In addition, the UE may be a portable device such as a laptop, mobile phone, PDA, smart phone, multimedia device, etc., or a non-portable device such as a PC or vehicle-mounted device.

[0039] Hereinafter, the term "UE" is used as an example of a device capable of wireless communication (e.g., a wireless communication device, a wireless device, or a wireless device). The operations performed by the UE can be performed by any device capable of wireless communication. A device capable of wireless communication may also be referred to as a wireless communication device, a wireless device, or a wireless device.

[0040] The term base station used below generally refers to a fixed station that communicates with wireless devices, and can be used as a comprehensive term that includes eNodeB (evolved-NodeB), eNB (evolved-NodeB), BTS (Base Transceiver System), Access Point, gNB (Next generation NodeB), RRH (remote radio head), TP (transmission point), RP (reception point), relay, etc.

[0041] Although this specification describes embodiments using LTE systems, LTE-A systems, and NR systems, these embodiments may be applied to any communication system falling within the above definitions.

[0042] Wireless Communication System

[0043] Building on the success of LTE (long term evolution) / LTE-Advanced (LTE-A) for 4th generation mobile communications, commercialization of the next generation, or 5th generation (so-called 5G) mobile communications, and follow-up research are also ongoing.

[0044] The International Telecommunication Union (ITU) defines 5G mobile communications as providing data transfer speeds of up to 20 Gbps and a perceived transmission speed of at least 100 Mbps everywhere. Its official name is "IMT-2020."

[0045] ITU proposes three usage scenarios: eMBB (enhanced Mobile BroadBand), mMTC (massive Machine Type Communication), and URLLC (Ultra Reliable and Low Latency Communications).

[0046] URLLC addresses usage scenarios that require high reliability and low latency. For example, services such as autonomous driving, factory automation, and augmented reality require high reliability and low latency (e.g., sub-1ms). Current 4G (LTE) latency is statistically 21-43ms (best 10%) and 33-75ms (median). This is insufficient to support services requiring sub-1ms latency. Next, eMBB usage scenarios address usage scenarios that require mobile ultra-wideband.

[0047] In other words, the 5th generation mobile communication system can support higher capacity than the current 4G LTE, increase the density of mobile broadband users, and support D2D (Device to Device), high reliability, and MTC (Machine-type communication). 5G research and development also aims for lower latency and lower battery consumption than 4G mobile communication systems to better implement the Internet of Things. For this 5G mobile communication, a new radio access technology (New RAT or NR) may be proposed.

[0048] The NR frequency band can be defined by two types of frequency ranges (FR1, FR2). The numerical values ​​of the frequency ranges can be changed, and for example, the two types of frequency ranges (FR1, FR2) can be as shown in Table 1 below. For convenience of explanation, among the frequency ranges used in the NR system, FR1 can mean the “sub 6 GHz range”, and FR2 can mean the “above 6 GHz range” and can be called millimeter wave (mmW).

[0049] Frequency Range designationCorresponding frequency rangeSubcarrier SpacingFR1410MHz - 7125MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0050] The numerical value of the frequency range of the NR system can be changed. For example, FR1 can include a band from 410 MHz to 7125 MHz, as shown in Table 1. That is, FR1 can include frequency bands above 6 GHz (or 5850, 5900, 5925 MHz, etc.). For example, the frequency bands above 6 GHz (or 5850, 5900, 5925 MHz, etc.) included within FR1 can include unlicensed bands. Unlicensed bands can be used for various purposes, such as for vehicle communications (e.g., autonomous driving).

[0051] Meanwhile, 3GPP-based communication standards define downlink physical channels corresponding to resource elements that carry information originating from upper layers, and downlink physical signals corresponding to resource elements that are used by the physical layer but do not carry information originating from upper layers. For example, the physical downlink shared channel (PDSCH), physical broadcast channel (PBCH), physical multicast channel (PMCH), physical control format indicator channel (PCFICH), physical downlink control channel (PDCCH), and physical hybrid ARQ indicator channel (PHICH) are defined as downlink physical channels, and reference signals and synchronization signals are defined as downlink physical signals. A reference signal (RS), also referred to as a pilot, is a signal with a special predefined waveform known to the gNB and the UE. For example, cell specific RS, UE-specific RS (UE-RS), positioning RS (PRS), and channel state information RS (CSI-RS) are defined as downlink reference signals. The 3GPP LTE / LTE-A standard defines uplink physical channels corresponding to resource elements carrying information originating from higher layers, and uplink physical signals corresponding to resource elements used by the physical layer but not carrying information originating from higher layers.For example, a physical uplink shared channel (PUSCH), a physical uplink control channel (PUCCH), and a physical random access channel (PRACH) are defined as uplink physical channels, and a demodulation reference signal (DMRS) for uplink control / data signals and a sounding reference signal (SRS) used for uplink channel measurement are defined.

[0052] In this specification, PDCCH (Physical Downlink Control CHannel) / PCFICH (Physical Control Format Indicator CHannel) / PHICH ((Physical Hybrid automatic retransmit request Indicator CHannel) / PDSCH (Physical Downlink Shared CHannel) mean a set of time-frequency resources or a set of resource elements that carry DCI (Downlink Control Information) / CFI (Control Format Indicator) / downlink ACK / NACK (ACKnowlegement / Negative ACK) / downlink data, respectively. In addition, PUCCH (Physical Uplink Control CHannel) / PUSCH (Physical Uplink Shared CHannel) / PRACH (Physical Random Access CHannel) mean a set of time-frequency resources or a set of resource elements that carry UCI (Uplink Control Information) / uplink data / random access signals, respectively.

[0053] Figure 1 is a diagram illustrating a wireless communication system.

[0054] As can be seen from FIG. 1, the wireless communication system includes at least one base station (BS). The BS is divided into a gNodeB (or gNB) (20a) and an eNodeB (or eNB) (20b). The gNB (20a) supports 5th generation mobile communications. The eNB (20b) supports 4th generation mobile communications, i.e., long term evolution (LTE).

[0055] Each base station (20a and 20b) provides communication services for a specific geographic area (commonly referred to as a cell) (20-1, 20-2, 20-3). The cell may be further divided into multiple areas (referred to as sectors).

[0056] A UE (user equipment) typically belongs to a single cell, and the cell to which the UE belongs is called a serving cell. The base station that provides communication services for the serving cell is called a serving base station (BS). Since the wireless communication system is a cellular system, there are other cells adjacent to the serving cell. These other cells adjacent to the serving cell are called neighbor cells. The base station that provides communication services to the neighbor cell is called a neighbor BS. The serving cell and neighbor cells are determined relative to the UE.

[0057] Hereinafter, downlink refers to communication from a base station (20) to a UE (10), and uplink refers to communication from a UE (10) to a base station (20). In downlink, the transmitter may be part of the base station (20), and the receiver may be part of the UE (10). In uplink, the transmitter may be part of the UE (10), and the receiver may be part of the base station (20).

[0058] Meanwhile, wireless communication systems can be broadly divided into frequency division duplex (FDD) and time division duplex (TDD). In FDD, uplink and downlink transmissions occupy different frequency bands and occur at different times. In TDD, uplink and downlink transmissions occupy the same frequency band but occur at different times. The channel response in TDD is essentially reciprocal, meaning that the downlink and uplink channel responses are nearly identical in a given frequency range. Therefore, in TDD-based wireless communication systems, the downlink channel response can be derived from the uplink channel response, which is advantageous. In TDD, uplink and downlink transmissions are time-divided across the entire frequency band, so downlink transmission by the base station and uplink transmission by the UE cannot be performed simultaneously. In TDD systems, where uplink and downlink transmissions are divided into subframes, uplink and downlink transmissions are performed in different subframes.

[0059] Figure 2 illustrates the structure of a radio frame used in NR.

[0060] In NR, uplink and downlink transmissions are structured as frames. A radio frame is 10ms long and is defined by two 5ms half-frames (HF). Each half-frame is defined by five 1ms subframes (SF). A subframe is divided into one or more slots, and the number of slots in a subframe depends on the subcarrier spacing (SCS). Each slot contains 12 or 14 OFDM(A) symbols, depending on the cyclic prefix (CP). When a normal CP is used, each slot contains 14 symbols. When an extended CP is used, each slot contains 12 symbols. Here, the symbols may include OFDM symbols (or CP-OFDM symbols), SC-FDMA symbols (or DFT-s-OFDM symbols).

[0061] Support for various numerologies

[0062] In NR systems, multiple numerologies may be provided to terminals as wireless communication technologies advance. For example, an SCS of 15 kHz supports a wide area in traditional cellular bands. An SCS of 30 kHz / 60 kHz supports dense urban environments, lower latency, and wider carrier bandwidth. An SCS of 60 kHz or higher supports a bandwidth greater than 24.25 GHz to overcome phase noise.

[0063] The above numerology can be defined by the cycle prefix (CP) length and subcarrier spacing (SCS). A single cell can provide multiple numerologies to a terminal. When the numerology index is represented by μ, each subcarrier spacing and the corresponding CP length can be as shown in the table below.

[0064] μ△f=2 μ 15 [kHz]CP015 General 130 General 260 General, Extended 3120 General 4240 General 5480 General 6960 General

[0065] For general CP, when the index of the numerology is represented by μ, the number of OFDM symbols per slot (N slot symb ), number of slots per frame (N frame,μ slot ) and the number of slots per subframe (N subframe,μ slot ) is as shown in the table below.

[0066] μ△f=2 μ 15 [kHz]N slot symb N frame,μ slot N subframe,μ slot 015141011301420226014404312014808424014160165480143203269601464064

[0067] For extended CP, when the index of the numerology is represented by μ, the number of OFDM symbols per slot (N slot symb ), number of slots per frame (N frame,μ slot ) and the number of slots per subframe (N subframe,μ slot ) is as shown in the table below.

[0068] μSCS (15*2 u )N slot symb N frame,μ slot N subframe,μslot 260KHz (u=2)12404

[0069] In an NR system, OFDM(A) numerology (e.g., SCS, CP length, etc.) may be set differently between multiple cells that are merged into a single terminal. Accordingly, the (absolute time) interval of a time resource (e.g., SF, slot, or TTI) (conveniently referred to as TU (Time Unit)) consisting of the same number of symbols may be set differently between the merged cells.

[0070] Figures 3a to 3c are exemplary diagrams showing exemplary architectures for wireless communication services.

[0071] Referring to FIG. 3a, the UE is connected to an LTE / LTE-A-based cell and an NR-based cell in a DC (dual connectivity) manner.

[0072] The above NR-based cell is connected to the core network for existing 4th generation mobile communication, i.e. Evolved Packet Core (EPC).

[0073] Referring to FIG. 3b, unlike FIG. 3a, the LTE / LTE-A-based cell is connected to a core network for 5th generation mobile communication, i.e., a 5G core network.

[0074] A service method based on an architecture as illustrated in Figures 3a and 3b above is called NSA (non-standalone).

[0075] Referring to Figure 3c, the UE is connected only to NR-based cells. A service method based on this architecture is called SA (standalone).

[0076] Meanwhile, in the above NR, it may be considered that reception from the base station utilizes a downlink subframe, and transmission to the base station utilizes an uplink subframe. This method can be applied to paired and unpaired spectrums. A pair of spectrums means that two carrier spectrums are included for downlink and uplink operations. For example, in a pair of spectrums, one carrier may include a downlink band and an uplink band that are paired with each other.

[0077] Figure 4 illustrates the slot structure of an NR frame.

[0078] A slot contains multiple symbols in the time domain. For example, in the case of a normal CP, one slot contains 14 symbols, but in the case of an extended CP, one slot contains 12 symbols. A carrier contains multiple subcarriers in the frequency domain. An RB (Resource Block) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A BWP (Bandwidth Part) is defined as multiple consecutive (physical, P)RBs in the frequency domain, and can correspond to a single numerology (e.g., SCS, CP length, etc.). A terminal can be configured with up to N (e.g., 4) BWPs in the downlink and uplink, respectively. Downlink or uplink transmission is performed through an activated BWP, and at a given time, only one BWP among the BWPs configured for the terminal can be activated. In the resource grid, each element is referred to as a Resource Element (RE), to which one complex symbol can be mapped.

[0079] Figure 5 illustrates an example of subframe types in NR.

[0080] The transmission time interval (TTI) illustrated in FIG. 5 may be referred to as a subframe or slot for NR (or new RAT). The subframe (or slot) of FIG. 5 may be used in a TDD system of NR (or new RAT) to minimize data transmission delay. As illustrated in FIG. 5, a subframe (or slot) includes 14 symbols. The symbols in the front of the subframe (or slot) may be used for a downlink (DL) control channel, and the symbols in the back of the subframe (or slot) may be used for an uplink (UL) control channel. The remaining symbols may be used for DL ​​data transmission or UL data transmission. According to this subframe (or slot) structure, downlink transmission and uplink transmission may be sequentially performed in one subframe (or slot). Therefore, downlink data may be received within a subframe (or slot), and an uplink acknowledgment (ACK / NACK) may be transmitted within the subframe (or slot).

[0081] The structure of these subframes (or slots) can be called self-contained subframes (or slots).

[0082] Specifically, the first N symbols in a slot are used to transmit a DL control channel (hereinafter, DL control region), and the last M symbols in the slot can be used to transmit a UL control channel (hereinafter, UL control region). N and M are each integers greater than or equal to 0. A resource region (hereinafter, data region) between the DL control region and the UL control region can be used for DL ​​data transmission or UL data transmission. For example, a physical downlink control channel (PDCCH) can be transmitted in the DL control region, and a physical downlink shared channel (PDSCH) can be transmitted in the DL data region. A physical uplink control channel (PUCCH) can be transmitted in the UL control region, and a physical uplink shared channel (PUSCH) can be transmitted in the UL data region.

[0083] Using this subframe (or slot) structure has the advantage of minimizing the final data transmission latency by reducing the time required to retransmit data that has experienced reception errors. In this self-contained subframe (or slot) structure, a time gap may be required during the transition from transmit mode to receive mode or from receive mode to transmit mode. To this end, some OFDM symbols during the transition from DL to UL in the subframe structure can be designated as a guard period (GP).

[0084] Figure 6 illustrates the structure of a self-contained slot.

[0085] In an NR system, a frame is characterized by a self-contained structure in which a DL control channel, DL or UL data, and a UL control channel can all be included within a single slot. For example, the first N symbols within a slot can be used to transmit a DL control channel (hereinafter, referred to as a DL control region), and the last M symbols within a slot can be used to transmit a UL control channel (hereinafter, referred to as a UL control region). N and M are each integers greater than or equal to 0. The resource region (hereinafter, referred to as a data region) between the DL control region and the UL control region can be used for DL ​​data transmission or UL data transmission. As an example, the following configuration can be considered. Each section is listed in chronological order.

[0086] 1. DL only configuration

[0087] 2. UL only configuration

[0088] 3. Mixed UL-DL configuration

[0089] - DL area + GP (Guard Period) + UL control area

[0090] - DL control area + GP + UL area

[0091] DL area: (i) DL data area, (ii) DL control area + DL data area

[0092] UL domain: (i) UL data domain, (ii) UL data domain + UL control domain

[0093] In the DL control region, a PDCCH can be transmitted, and in the DL data region, a PDSCH can be transmitted. In the UL control region, a PUCCH can be transmitted, and in the UL data region, a PUSCH can be transmitted. In the PDCCH, downlink control information (DCI), for example, DL data scheduling information, UL data scheduling information, etc., can be transmitted. In the PUCCH, uplink control information (UCI), for example, ACK / NACK (Positive Acknowledgement / Negative Acknowledgement) information for DL ​​data, CSI (Channel State Information) information, SR (Scheduling Request), etc., can be transmitted. GP provides a time gap when a base station and a terminal switch from transmission mode to reception mode or when switching from reception mode to transmission mode. Some symbols at the time of switching from DL to UL within a subframe can be set as GP.

[0094] In this specification, we propose a resource allocation method for uplink data channel (PUSCH) transmission of a terminal in a base station / cell in which uplink (UL) subband or downlink (DL) subband configuration is performed to support full duplex communication in a wireless mobile communication system. In particular, when scheduling for one or more PUSCH transmissions is configured through one downlink control information (DCI) in the terminal, we propose a method for transmitting multiple PUSCHs through a subband full duplex (SBFD) slot including a UL subband and a non-SBFD slot (e.g., a conventional UL slot).

[0095] Time Division Duplex (TDD) is a duplexing method widely used in commercial New Radio (NR) and 5G mobile communication systems. In TDD, time-slot radio resources are divided into downlink and uplink slots. Typically, downlink slots are distributed at a higher rate than uplink slots, depending on the distribution ratio of uplink to downlink traffic. However, this limitation of uplink slots negatively impacts coverage and latency. Full duplex communication has recently attracted attention as a technology to address these issues.

[0096] Full duplex is a technology that allows gNBs (base stations) to simultaneously perform DL transmission and UL reception via the same (or fixed) radio resources. DL and UL transmission can also be performed simultaneously at the terminal. In other words, both the base station and the terminal can support full duplex communication. However, unlike base stations, which are structurally prone to self-interference cancellation, the terminal's DL reception performance is susceptible to self-interference of UL transmission signals. Therefore, a scenario in which the gNB operates in full duplex communication and the terminal operates in half duplex communication is generally considered. Additionally, in order to reduce the impact of self-interference in gNB, a subband non-overlapping full duplex communication method that performs DL transmission and UL reception simultaneously, but transmits and receives by distinguishing frequency resources that are not the same resources between DL and UL, can be considered as a primary method.

[0097] Figures 7a and 7b are schematic examples of subband full duplex communication.

[0098] Subband full duplex may be referred to as subband full duplex (SBFD) or full duplex subband (FDSB).

[0099] In subband full duplex communications, some of the time-frequency resources on a given carrier are used for downlink, and some of the time-frequency resources on the same carrier are used for uplink. Specifically, downlink and uplink resources are separated in the frequency domain and used for transmission and reception.

[0100] Figures 7a and 7b illustrate examples of subband full duplex, where in the frequency domain, Figure 7a illustrates an example where an uplink subband is positioned between downlink subbands, and Figure 7b illustrates an example where a downlink subband is positioned between uplink subbands. Although not illustrated in the drawings, a guard band or guard period may be positioned between the downlink subband and the uplink subband to reduce interference.

[0101] FIGS. 8A and 8B illustrate examples of setting uplink (UL) subbands in downlink (DL) slots according to one embodiment of the present specification.

[0102] Referring to FIGS. 8A and 8B, in order to support full duplex operation, any frequency resource, i.e., a subband, may be supported to support a transmission (Tx) direction in a direction other than that set by slot configuration information (i.e., DL, UL, or flexible). That is, as shown in FIGS. 8A and 8B, some frequency resources in any DL slot or DL ​​symbol may be defined to be utilized as flexible symbols for UL transmission or DL / UL transition of a terminal. Alternatively, some frequency resources in any UL slot or UL symbol may be defined to be utilized for DL ​​transmission of a base station.

[0103] FIGS. 8A and 8B illustrate examples of configuring UL subbands to support UL transmission of a terminal in some (or all) of the DL slots when a TDD configuration is made in an arbitrary NR frequency band in which DL slots and UL slots have a ratio of 4:1 (provided that some symbols of the last DL slot are special slots including flexible symbols for DL / UL transition). When a UL subband is configured in an arbitrary DL slot, the UL subband may be configured in the center or edge of the frequency band, and a guard band may be configured between the UL subband and the DL subband in the slot.

[0104] Meanwhile, frequency resources other than the UL subband and guard band can be utilized as DL subbands for DL ​​transmission and reception according to the existing slot / symbol configuration information. As shown in Fig. 8a, if the UL subband is configured around the center of the frequency band, two guard bands, one each above and below the UL subband, can be configured, and then similarly, two DL subbands, one each above and below the UL subband, can be configured. Alternatively, as shown in Fig. 8b, if the UL subband is configured at the edge of the frequency band, one guard band and one DL subband can be configured following the UL subband.

[0105] The UL-DL slot configuration defined in the existing NR is defined to be done on a cell-by-cell basis through cell-specific RRC signaling. That is, the pattern of DL symbols, UL symbols, and flexible symbols for a certain period is set through 'tdd-UL-DL-ConfigurationCommon', which is an RRC message / information for the corresponding UL-DL slot configuration. Additionally, only the flexible symbols set through the 'tdd-UL-DL-ConfigurationCommon' can be reallocated to UL symbols, DL symbols, or flexible symbols for each UE through 'tdd-UL-DL-ConfigurationDedicated', which is a UE-specific RRC signaling. Alternatively, a method for indicating a dynamic slot format through 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.

[0106] According to the existing slot configuration method described above, any one symbol can be set or indicated as one of DL, UL, or flexible. For example, as shown in Fig. 8a, any slot format can be set to DDDSU through the existing slot configuration. D refers to a downlink slot, meaning that all OFDM symbols constituting the slot are set to DL. U refers to an uplink slot, meaning that all OFDM symbols constituting the slot are set to UL. S refers to a special slot, meaning that a slot includes a flexible symbol for DL / UL transition. Typically, in the case of a normal CP, the special slot can be composed of 12 DL symbols and 2 flexible symbols out of a total of 14 symbols. Alternatively, it may consist of 10 DL symbols, 2 flexible symbols, and 2 UL symbols. That is, within any one TDD carrier, a symbol is set or indicated to be only one of DL, UL, or flexible.

[0107] However, if a UL subband is configured in any DL slot as shown in FIGS. 8A and 8B, DL transmission or UL transmission can 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 an SBFD slot or SBFD symbol in this specification.

[0108] In addition, in this specification, a slot composed only of 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 that do not include a UL subband, a DL subband, and a guard band) is referred to as a non-SBFD slot.

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

[0110] PUSCH transmission based on dynamic scheduling 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 DCI format. Accordingly, PUSCH transmission resource allocation in an SBFD slot consisting of SBFD symbols and PUSCH transmission resource allocation in a non-SBFD slot, such as an UL slot, can be performed through separate DCI transmissions.

[0111] However, for PUSCH transmissions 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 is configured / indicated, or multiple PUSCH transmissions are scheduled through a single DCI.

[0112] In the present invention, when PUSCH transmission with dynamic scheduling through a single DCI is instructed to be performed through one or more slots, and the slots include both SBFD slots and non-SBFD slots, a method for defining specific PUSCH transmission slots is proposed. In particular, when multi-PUSCH scheduling is performed through a single DCI for an arbitrary terminal, a method for determining a slot in which the multi-PUSCH transmission is performed is proposed.

[0113] In the present invention, the term 'slot type' is used to distinguish between SBFD slots and non-SBFD slots, but the present invention is not limited by specific names.

[0114] An NR base station can transmit scheduling control information for one or more PUSCH transmissions to a terminal through a single UL grant DCI (e.g., DCI format 0_1). Specifically, the base station can configure a time domain resource allocation table in which one row has one or more SLIVs (start and length indicator values) through the RRC parameter 'pusch-TimeDomainAllocationListForMultiPUSCH' setting, and based on this, can allocate each PUSCH transmission resource in one or more slots (up to 8) through the time domain resource assignment indication information of DCI format 0_1. The following is related to the 'pusch-TimeDomainAllocationListForMultiPUSCH' setting defined in the 3GPP TS 38.331 standard document.

[0115] pusch-TimeDomainAllocationListForMultiPUSCH

[0116] Configuring the Time Domain Resource Allocation (TDRA) table for multi-PUSCH (see TS 38.214, clause 6.1.2). The network configures up to 16 rows in this TDRA table in the PUSCH-TimeDomainResourceAllocationList-r16 field, which is configured with this field. This field is not configured simultaneously with push-AggregationFactor. The network does not configure pusch-TimeDomainAllocationListForMultiPUSCH-r16 simultaneously with pusch-TimeDomainAllocationListDCI-0-1-r16. (Configuration of the time domain resource allocation (TDRA) table for multiple PUSCH (see TS 38.214

[0019] , clause 6.1.2). The network configures at most 16 rows in this TDRA table in PUSCH-TimeDomainResourceAllocationList-r16 configured by this field. This field is not configured simultaneously with pusch-AggregationFactor. The network does not configure the pusch-TimeDomainAllocationListForMultiPUSCH-r16 simultaneously with the pusch-TimeDomainAllocationListDCI-0-1-r16.)

[0117] Table 5 below shows the RRC parameters for configuring a time domain resource allocation table for multi-PUSCH scheduling.

[0118] PUSCH-TimeDomainResourceAllocation information element-- ASN1START-- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STARTPUSCH-TimeDomainResourceAllocationList ::= SEQUENCE (SIZE(1..maxNrofUL-Allocations)) OF PUSCH-TimeDomainResourceAllocationPUSCH-TimeDomainResourceAllocation ::= SEQUENCE {k2 INTEGER(0..32) OPTIONAL, -- Need SmappingType ENUMERATED {typeA, typeB},startSymbolAndLength INTEGER (0..127)}PUSCH-TimeDomainResourceAllocationList-r16 ::= SEQUENCE (SIZE(1..maxNrofUL-Allocations-r16)) OF PUSCH-TimeDomainResourceAllocation-r16PUSCH-TimeDomainResourceAllocation-r16 ::= SEQUENCE {k2-r16 INTEGER(0..32) OPTIONAL, -- Need SpuschAllocationList-r16 SEQUENCE (SIZE(1..maxNrofMultiplePUSCHs-r16)) OF PUSCH-Allocation-r16,...}PUSCH-Allocation-r16 ::= SEQUENCE {mappingType-r16 ENUMERATED {typeA, typeB} OPTIONAL, -- Cond NotFormat01-02-Or-TypeAstartSymbolAndLength-r16 INTEGER (0..127) OPTIONAL, -- Cond NotFormat01-02-Or-TypeAstartSymbol-r16 INTEGER (0..13) OPTIONAL, -- Cond RepTypeBlength-r16 INTEGER (1..14) OPTIONAL, -- Cond RepTypeBnumberOfRepetitions-r16 ENUMERATED {n1, n2, n3, n4, n7, n8, n12, n16} OPTIONAL, -- Cond Format01-02...}-- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STOP-- ASN1STOP.

[0119] As shown in Table 5, the base station can set the K2 value, mapping type value, and SLIV value for each PUSCH when configuring a TDRA (time domain resource allocation) table for an arbitrary terminal for multi-PUSCH scheduling.

[0120] Based on this, the base station can explicitly indicate slots (extendedK2) for one or more PUSCH transmissions and symbol (SLIV) allocation information within the slots through a UL grant such as DCI format 0_1. However, according to the existing PUSCH transmission method of the terminal, when scheduling for PUSCH transmission in multiple slots is performed by one DCI format, if at least one symbol among the symbols allocated for PUSCH transmission in any one of the multiple slots is indicated as DL by 'tdd-UL-DL-ConfigurationCommon' or 'tdd-UL-DL-ConfigurationDedicated', the PUSCH is defined not to be transmitted in the slot.

[0121] Accordingly, according to the existing multi-PUSCH scheduling method, even if the UE can perform PUSCH transmission through the UL subband in any SBFD slot to which the PUSCH transmission resource is allocated by the UL grant (e.g., DCI format 0_1, etc.) including the multi-PUSCH scheduling control information, if at least one symbol allocated for PUSCH transmission in the slot is set to DL by the legacy slot configuration, the UE does not perform PUSCH transmission. Here, the legacy slot configuration in the present specification refers to the slot configuration by 'tdd-UL-DL-ConfigurationCommon' or 'tdd-UL-DL-ConfigurationDedicated' as the legacy slot configuration, or additionally, the dynamic slot format setting by DCI format 2_0 is also referred to as the legacy slot configuration.

[0122] Therefore, there is a need to define a PUSCH transmission method based on a new multi-PUSCH scheduling to overcome the above limitations.

[0123] Below, we propose various methods to address the aforementioned issues. Each of the methods proposed below can be applied independently or in a combination of one or more methods to address the aforementioned issues, all of which fall within the scope of the present invention.

[0124] Option 1: Extended slot format configuration

[0125] A base station can explicitly define or instruct a terminal to transmit in an arbitrary SBFD slot or SBFD symbol. Here, the transmission direction of the terminal can be referred to by various names such as extended slot configuration, extended slot format, etc. The base station can configure or instruct a terminal to perform a DL reception operation or an UL transmission operation in an SBFD symbol or slot. For example, the base station can define to transmit UL-DL configuration information of an SBFD slot or symbol to the terminal through UE-specific or cell-specific RRC signaling. The configuration information may be based on period information of an SBFD slot or symbol according to a UL subband configuration, so that UL and DL configurations are made for the corresponding SBFD slots or symbols, and may implicitly mean that an SBFD symbol that is not explicitly configured as UL or DL ​​is configured as a flexible symbol. Alternatively, the base station may transmit UL-DL indication information of the corresponding SBFD slot or SBFD symbol to the UE through L1 control signaling. In this case, the UL-DL indication information in the corresponding SBFD slot or SBFD symbol may be indicated through UE-specific DCI or UE-group common DCI.

[0126] The transmission direction setting or indication information of the 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.

[0127] Alternatively, the transmission direction in any SBFD slot or symbol may be implicitly configured 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 may implicitly perform a UL transmission operation in the corresponding SBFD slot or symbol. Conversely, if a DL subband is configured, the terminal may perform a DL reception operation in the corresponding SBFD slot or symbol.

[0128] Meanwhile, if the transmission direction for a terminal in an SBFD slot or symbol is not set to DL, i.e., UL or flexible, the terminal supports PUSCH transmission in the SBFD slot or symbol.

[0129] In another way, if UL subband configuration is performed for a symbol set to DL or flexible by 'tdd-UL-DL-ConfigurationCommon' or 'tdd-UL-DL-ConfigurationDedicated', it can be defined that the symbol is reset to a symbol capable of UL transmission according to scheduling control information of the base station at the terminal. That is, the terminal can reset any DL or flexible symbol reset to an SBFD symbol to a symbol capable of PUSCH or PUCCH / SRS transmission according to scheduling control information of a DCI format transmitted from the base station.

[0130] When PUSCH transmission is instructed in any SBFD slot according to multi-PUSCH scheduling information, the UE performs PUSCH transmission operation in the SBFD slot as described in detail below.

[0131] A terminal may support multi-PUSCH transmission according to multi-PUSCH scheduling including an SBFD slot including an SBFD symbol and a non-SBFD slot composed of non-SBFD symbols (in particular, composed of non-SBFD UL symbols or flexible symbols), when a UL subband configuration for SBFD operation is valid in an activated UL BWP (bandwidth part). Here, the case where the activated UL BWP has a valid UL subband configuration for SBFD operation may mean a UL BWP associated with a UL subband configuration for supporting SBFD operation among one or more UL BWPs configured for the terminal, or a UL BWP in which a UL subband configuration is performed.

[0132] In this case, the frequency allocation resource by the FDRA (frequency domain resource assignment) information area included in the DCI format transmitting the multi-PUSCH scheduling control information can be restricted to completely belong to the frequency area of ​​the UL subband where UL transmission is possible in the SBFD symbol. Alternatively, the DCI format transmitting the multi-PUSCH scheduling control information can include control information for PUSCH transmission in a SBFD symbol that is separate from the control information for PUSCH transmission in a non-SBFD symbol. As an example, for PUSCH transmission by the multi-PUSCH scheduling DCI format, the information area such as the FDRA, TCI (transmission configuration indicator) field, etc. for PUSCH transmission in a SBFD symbol can be further included that is separate from the information area such as the FDRA, TCI (transmission configuration indicator) field, etc. for PUSCH transmission in a non-SBFD symbol.

[0133] Alternatively, when including multiple PUSCH transmissions through different slot types, scheduling control information may be restricted to be configured based on a specific slot type. For example, the configuration of FDRA, TCI fields, etc. included in the DCI format for the multi-PUSCH scheduling may be configured at the base station based on 'PUSCH-config' valid in the SBFD symbol, i.e., based on UL subbands rather than UL BWP, and may be interpreted at the terminal. For example, in configuring 'PUSCH-config' configuration information for PUSCH transmission of the terminal, in addition to 'PUSCH-config' for PUSCH transmission in the existing non-SBFD symbol, separate 'PUSCH-config' configuration information for PUSCH transmission in the SBFD symbol (for example, separate PUSCH-config_SBFD configuration information) may be configured by the base station and transmitted to the terminal. Alternatively, some parameters included in 'PUSCH-config' may further include configuration values ​​for PUSCH transmission in SBFD symbols, together with configuration values ​​for PUSCH transmission in non-SBFD symbols. Accordingly, when PUSCH transmission according to a multi-PUSCH scheduling DCI format includes both the SBFD slot and the non-SBFD slot, control information included in the DCI format may be indicated based on 'PUSCH-config' configuration information of a specific slot type. For example, it may be restricted to be indicated based on 'PUSCH-config' configuration information for an SBFD symbol.

[0134] In this way, in order for PUSCH transmission according to multi-PUSCH scheduling to be performed in both the non-SBFD slot and the SBFD slot, the terminal performs PUSCH transmission according to symbol settings as described below.

[0135] When scheduling is performed for PUSCH transmission in multiple slots by one DCI format for a terminal, if at least one symbol among the 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 a UE-specific or cell-specific extended slot configuration, it can be defined that PUSCH is not transmitted in the slot.

[0136] That is, when scheduling for PUSCH transmission in multiple slots is performed by one DCI format for a 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 been configured to perform DL reception operation in the symbol, the terminal may not transmit PUSCH in the slot.

[0137] Alternatively, all SBFD symbols for which UL subband configuration has been performed may be implicitly reset to symbols capable of UL transmission in the UE. In this case, if multi-PUSCH transmission is instructed for the UE by one DCI format, at least one symbol among the symbols allocated for PUSCH transmission in any one slot among the slots in which the plurality of PUSCH transmissions are performed (or at least one symbol among the symbols in which any one of the plurality of PUSCH transmissions is performed) is set to DL by 'tdd-UL-DL-ConfigurationCommon' or 'tdd-UL-DL-ConfigurationDedicated', and if UL subband configuration has not been performed in the symbol, the UE may skip the PUSCH transmission.

[0138] For cases other than those described above, the UE can be defined to perform PUSCH transmission in an arbitrary SBFD slot according to multi-PUSCH scheduling information. That is, when scheduling for PUSCH transmission in multiple slots is performed for the UE by one DCI format, for any one of the multiple slots, if at least one symbol among the symbols allocated for PUSCH transmission in the slot is indicated as DL by 'tdd-UL-DL-ConfigurationCommon' or 'tdd-UL-DL-ConfigurationDedicated', and if at least one symbol includes a UL subband (i.e., is an SBFD symbol) and the base station explicitly or implicitly configures / instructs the UE to perform UL transmission operation in the symbol, the UE can be defined to perform PUSCH transmission in the slot.

[0139] Option 2: Setting PUSCH transmission limits across different slot types

[0140] Even in cases where PUSCH transmission according to multi-PUSCH scheduling is possible based on transmission direction setting or instruction information for a terminal in an SBFD slot or symbol, the base station can additionally explicitly or implicitly set or instruct whether to transmit PUSCH according to multi-PUSCH scheduling for each slot type.

[0141] As an example of an explicit configuration method, the configuration information can be defined to be semi-statically configured and transmitted to the terminal by the base station through RRC signaling. That is, when multi-PUSCH scheduling through multiple slots for the terminal is triggered by the base station, and slots configured or indicated for UL transmission of the terminal include SBFD slots and non-SBFD slots, it can be defined to configure whether the base station supports PUSCH transmission of the terminal through the different slot types. That is, the base station can configure PUSCH transmission according to multi-PUSCH scheduling for the terminal to be limited to SBFD slots or non-SBFD slots through UE-specific or cell-specific RRC signaling. For example, PUSCH transmission according to multi-PUSCH scheduling can be limited to non-SBFD slots, in which case, whether to transmit PUSCH in any slot according to multi-PUSCH scheduling can be determined according to the existing PUSCH transmission decision method. That is, when scheduling for PUSCH transmission in multiple slots is performed by one DCI format, the UE can follow the existing operation of not transmitting PUSCH in any one of the multiple slots if at least one symbol among the symbols allocated for PUSCH transmission in the slot is indicated as DL by 'tdd-UL-DL-ConfigurationCommon' or 'tdd-UL-DL-ConfigurationDedicated'.

[0142] As another explicit method, the base station can define to dynamically indicate whether to support transmission through different slot types for PUSCH transmission according to multi-PUSCH scheduling through 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.). That is, when the base station instructs a UE to transmit PUSCH according to multi-PUSCH scheduling through a UL grant, the UL grant can be defined to dynamically indicate whether to transmit PUSCH through different slot types or whether to restrict PUSCH transmission according to the multi-PUSCH scheduling only to a specific slot type. Alternatively, the corresponding indication information can be defined to be indicated to specific UEs through UE-group common DCI.

[0143] In addition, various combinations of the above-described explicit signaling methods may also be included in the present invention. For example, if an indication information area is set for whether different slot types are supported or whether slot types are limited 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.) through RRC signaling for the terminal, and the indication information area is set to be included, it can be defined to indicate whether different slot types are supported or whether slot types are limited for PUSCH transmission according to dynamic multi-PUSCH scheduling.

[0144] As described above, when multi-PUSCH transmission is instructed from a base station to a terminal, the slot type setting / instruction information for which the multi-PUSCH transmission is valid can be transmitted to the terminal through explicit RRC signaling or L1 control signaling.

[0145] Below we describe the implicit setting / instruction method.

[0146] As an example of an implicit configuration method, it can be determined by whether there is an overlap between the frequency resources of the UL BWP activated for the terminal and the frequency resources of the UL subband configured by the base station. That is, it can be defined that whether PUSCH repetition transmission through different slot types is supported is determined by whether the active UL BWP and the UL subband fully or partially overlap or do not overlap on the frequency axis. In this case, the target of overlap determination can be the frequency resources of the active UL BWP. That is, if the frequency resources of the UL BWP activated for the terminal fully belong to the UL subband, the terminal can be defined to support different slot type-based transmissions for PUSCH transmission according to multi-PUSCH scheduling. On the other hand, in case of partially overlapping or non-overlapping, different type-based transmissions may not be supported for PUSCH repetition transmissions.

[0147] Alternatively, the target of the frequency resource overlap determination may be a UL subband. That is, if the frequency resources of the UL subband for the UE fully belong to the activated UL BWP, the UE may be defined to support different slot type-based transmissions for PUSCH transmissions according to multi-PUSCH scheduling. On the other hand, in the case of partial overlapping or non-overlapping, different slot type-based transmissions may not be supported for PUSCH transmissions according to multi-PUSCH scheduling.

[0148] Alternatively, the UL grant for PUSCH transmission, i.e., the frequency resource allocation information included in the DCI format, i.e., the frequency domain resource assignment information, can be implicitly determined based on whether the frequency resources allocated by the frequency domain resource assignment information area include UL subbands. For example, if the frequency resources according to the frequency domain resource allocation information for PUSCH transmission according to multi-PUSCH scheduling fully belong to UL subbands, transmission based on different types can be defined to be supported, and otherwise, this can be defined not to be supported (i.e., transmission can only be performed for the same slot type). However, if intra-slot or inter-slot frequency hopping is configured, this method can be limited to cases where the frequency resources of each frequency hop all belong to UL subbands, or only when frequency hopping is not configured.

[0149] Alternatively, the slot type of the first slot in which PUSCH transmission according to multi-PUSCH scheduling starts may determine whether PUSCH transmission is supported through different types of slots. For example, if PUSCH transmission according to multi-PUSCH scheduling is configured / indicated for PUSCH transmission and the slot in which the first PUSCH transmission is performed is an SBFD slot according to time domain resource assignment information, the PUSCH transmission may be defined to be able to be transmitted through a non-SBFD slot as well. Conversely, in the opposite case, that is, if PUSCH transmission according to multi-PUSCH scheduling is configured / indicated for PUSCH transmission and the slot in which the PUSCH transmission is performed is a non-SBFD slot according to time domain resource assignment information, the PUSCH transmission may be defined to be able to be performed only through a non-SBFD slot. (Or, conversely, if a non-SBFD slot is the starting slot, transmissions through different slot types can be supported, and if a SBFD slot is the starting slot, transmissions can be defined only through the SBFD slot.)

[0150] In addition, various combinations of implicit configuration methods may also be included in the present invention. For example, if the slot in which the first PUSCH transmission according to multi-PUSCH scheduling is an SBFD slot, the PUSCH transmission is configured to support transmission through different slot types (i.e., transmission is also performed through non-SBFD slots). On the other hand, if the starting slot is a non-SBFD slot, the frequency resources allocated for the PUSCH transmission may be defined to fully overlap with the UL subband, and if so, transmission through different slot types may be supported (i.e., transmission is also performed through SBFD slots). Otherwise (i.e., partial overlap or non-overlap), transmission through different slot types may not be supported (i.e., the PUSCH transmission is only performed through non-SBFD slots).

[0151] Whether PUSCH transmission is supported in different slot types by the aforementioned explicit or implicit configuration / indication methods may be limited to specific slot types. For example, for non-SBFD slots, PUSCH transmission is supported if it is not configured as DL according to the legacy slot configuration. Additionally, whether PUSCH transmission is supported only for certain SBFD slots may be defined to be determined by the aforementioned explicit or implicit methods.

[0152] In addition, a combination of the explicit configuration / indication method and the implicit configuration / indication method described above may also be included in the scope of the present invention. For example, even if the base station explicitly configures / indicates to support PUSCH transmission according to multi-PUSCH scheduling through different slot types (or, if the base station explicitly configures / indicates to support PUSCH transmission according to multi-PUSCH scheduling in the SBFD slot), if the frequency resource allocation information for PUSCH transmission does not completely belong to the corresponding UL subband, PUSCH transmission through the corresponding SBFD slot may not be performed.

[0153] Additionally, when PUSCH transmission in an SBFD slot is configured / instructed to be supported according to the aforementioned methods, a new rule may be configured or defined for association (or mapping) between UL subbands and UL BWPs (between frequency resources of an SBFD slot and a non-SBFD slot) so that UL subband PRB (physical resource block) resources in the SBFD slot are always provided according to frequency resource allocation information for the corresponding PUSCH transmission.

[0154] As one method for this, a frequency domain resource set can be configured to map PRBs in the UL BWP of a terminal to PRBs of UL subbands. Accordingly, association / mapping is performed between PRBs of the configured resource set and PRBs constituting the UL subband, or between PRBs overlapping between the UL subband and the UL BWP. At this time, only one resource set can be configured for the UL BWP, or more than one resource set can be 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, association / mapping is performed between the PRB of each resource set and the PRB constituting the UL subband, or the PRB overlapping between the UL subband and the UL BWP. The resource set configuration information includes the start RB (resource block) information and the size information of the frequency axis, or includes only the 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.

[0155] Although the above examples have been described in terms of slots on the time axis, the same content can be applied to various time resource units such as symbols, subframes, and frames.

[0156] Below, the PUSCH transmission method of the terminal according to the above-described method is described in detail.

[0157] The terminal receives cell-specific and / or UE-specific TDD configuration information for uplink transmission and downlink reception from the base station. Additionally, the terminal receives UL subband and DL subband configuration information (or guard band configuration information) to support SBFD operation. Based on the TDD configuration information and the UL subband and DL subband configuration information, the terminal can determine symbols and slots capable of UL transmission.

[0158] Symbols and slots capable of UL transmission may be symbols that are not set to DL according to the TDD configuration, and slots composed of such symbols. Additionally, symbols and slots capable of UL transmission may be SBFD symbols with UL subband configuration among symbols set to DL according to the TDD configuration. However, for the terminal, symbols capable of UL transmission through the UL subband among the SBFD symbols may be explicitly configured.

[0159] When a terminal receives a DCI format including multi-PUSCH scheduling control information from a base station, the terminal receives symbol allocation information for each PUSCH transmission according to the TDRA information included in the DCI format.

[0160] At this time, PUSCH transmission according to multi-PUSCH scheduling can be restricted to be performed only with the same symbol type. That is, each symbol allocated for each PUSCH transmission according to the multi-PUSCH scheduling can be restricted to be either all non-SBFD symbols or all SBFD symbols. That is, the UE can prevent the UE from expecting that each PUSCH transmission symbol includes both non-SBFD symbols and SBFD symbols for one or more PUSCH transmissions based on the multi-PUSCH scheduling DCI format. The symbol type for PUSCH transmission according to the multi-PUSCH scheduling DCI format can be determined by the symbol type for the first PUSCH transmission according to the corresponding DCI format. Alternatively, the DCI format may include the corresponding symbol type configuration information, or the DCI format may be determined by the transmitted symbol type.

[0161] Accordingly, the terminal can determine common invalid symbols and symbol type-specific invalid symbols for each PUSCH transmission according to the multi-PUSCH DCI format. The common invalid symbols include non-SBFD symbols set to DL according to TDD configuration information, i.e., DL symbols for which UL subband configuration has not been performed. Additionally, the common invalid symbols may further include symbols for which DL reception has been explicitly configured by the base station among SBFD symbols for which UL subband configuration has been performed.

[0162] In addition to common invalid symbols, symbol type-specific invalid symbols may be determined. Symbol type-specific invalid symbols may be determined by each PUSCH transmission symbol type according to multi-PUSCH scheduling. For example, if the symbol type for one or more PUSCH transmissions according to any multi-PUSCH scheduling is determined to be a non-SBFD symbol, all SBFD symbols may be determined to be invalid symbols. As another example, if the symbol type for at least one PUSCH transmission according to multi-PUSCH scheduling is determined to be an SBFD symbol, all non-SBFD symbols, including symbols configured as UL symbols by TDD configuration or symbols for which UL subband configuration is not performed among flexible symbols, may be determined to be invalid symbols. Accordingly, when transmitting a PUSCH based on reception of a multi-PUSCH DCI format, the terminal may drop / skip the PUSCH transmission if the PUSCH transmission includes at least one invalid symbol among common invalid symbols and symbol type-specific invalid symbols.

[0163] As another example, PUSCH transmission according to multi-PUSCH scheduling via different symbol types can be supported. In this case, whether multi-PUSCH scheduling via the different symbol types is supported may be explicitly set by the base station or may be implicitly determined by the symbol type in which the first PUSCH transmission is performed or whether there is overlap between PUSCH transmission frequency resource allocation information by FDRA and UL subband frequency resources. In this way, when PUSCH transmission according to multi-PUSCH scheduling via different symbol types is supported, when transmitting a PUSCH based on reception of a DCI format including the multi-PUSCH scheduling information, if any PUSCH transmission includes a common invalid symbol, the PUSCH transmission can be dropped / skiped.

[0164] Additionally, if multi-PUSCH transmission through different symbol types is supported according to some method or combination of methods described above, a separate DCI format (e.g., DCI format 0_x) for the multi-PUSCH scheduling can be newly defined. In this case, the information field of the DCI format can 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 has a single setting value within the DCI format. For example, a TDRA information area, etc. can be a slot-type common information area, and includes a single information area as before. On the other hand, a 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 a SBFD slot, and the same information area has a setting value for a non-SBFD slot and a separate setting value for an SBFD slot. For example, FDRA, TCI field, etc. can be slot type specific information areas. Regardless of the above example, when configuring DCI format 0_x, a combination in which a specific information area is commonly applied to the slot type through a setting value and some other information areas are set separately for each slot type can also be included in the scope of the present invention.

[0165] Figure 9 illustrates an operation method of a terminal according to one embodiment of the present specification.

[0166] Referring to FIG. 9, a terminal receives TDD (time duplex division) configuration information, UL BWP (bandwidth part) configuration information, and UL subband configuration information from a base station (S901). In addition, the terminal receives DCI (downlink control information) including scheduling information for at least one PUSCH transmission from the base station (S902). Thereafter, the terminal determines a slot for at least one PUSCH transmission based on the received DCI (S903). Here, the slot for at least one PUSCH transmission is determined by whether an invalid symbol is included in a PUSCH transmission symbol within the slot according to scheduling information included in the DCI, and the invalid symbol may be determined based on subband full duplex (SBFD) symbol information according to the UL subband configuration information associated with the TDD configuration information and the UL BWP.

[0167] PUSCH transmission may not be performed in slots containing invalid symbols.

[0168] Meanwhile, the invalid symbol may include a non-SBFD symbol for which a UL subband is not configured among downlink (DL) symbols according to the TDD configuration information.

[0169] On the other hand, the invalid symbol may include a symbol in which a UL subband is set among the downlink (DL) symbols according to the TDD setting information, and a symbol instructed and / or set to receive DL by the base station.

[0170] On the other hand, the invalid symbol includes i) a non-SBFD symbol among downlink (DL) symbols according to the TDD configuration information in which a UL subband is not configured, and ii) a symbol among downlink (DL) symbols according to the TDD configuration information in which a UL subband is configured, and a symbol instructed and / or configured to perform DL reception by a base station, and a symbol not included in the invalid symbol may be a valid PUSCH transmission symbol.

[0171] On the other hand, the invalid symbol may be any non-SBFD symbol for which no UL subband is configured, or any SBFD symbol for which the UL subband is configured. Here, whether to transmit PUSCH for the non-SBFD symbol and / or the SBFD symbol may be determined based on i) an indication through the DCI, ii) a symbol type of a first PUSCH transmission by the DCI, or iii) a symbol type in which the DCI is transmitted.

[0172] The above DCI may be in a format including i) a scheduling information area in a slot type composed of SBFD symbols, ii) a scheduling information area in a slot type composed of non-SBFD symbols, and iii) an information area common to the slot types.

[0173] The concepts disclosed in this specification can be applied independently or combined and operated in any form. Furthermore, while this specification is based on a 5G NR system, the scope of this specification encompasses all cases where the concepts of this specification apply, regardless of the specific wireless communication technology.

[0174] Figure 10 illustrates a device according to one embodiment of the present specification.

[0175] Referring to FIG. 10, a wireless communication system may include a first device (100a) and a second device (100b).

[0176] The first device (100a) may be a base station, a network node, a transmitting terminal, a receiving terminal, a wireless device, a wireless communication device, a vehicle, a vehicle equipped with an autonomous driving function, a connected car, a drone (Unmanned Aerial Vehicle, UAV), an AI (Artificial Intelligence) module, a robot, an AR (Augmented Reality) device, a VR (Virtual Reality) device, an MR (Mixed Reality) device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a fintech device (or a financial device), a security device, a climate / environmental device, a device related to 5G services, or any other device related to the 4th industrial revolution field.

[0177] The second device (100b) may be a base station, a network node, a transmitting terminal, a receiving terminal, a wireless device, a wireless communication device, a vehicle, a vehicle equipped with an autonomous driving function, a connected car, a drone (Unmanned Aerial Vehicle, UAV), an AI (Artificial Intelligence) module, a robot, an AR (Augmented Reality) device, a VR (Virtual Reality) device, an MR (Mixed Reality) device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a fintech device (or a financial device), a security device, a climate / environmental device, a device related to 5G services, or any other device related to the 4th industrial revolution field.

[0178] The first device (100a) may include at least one processor, such as a processor (1020a), at least one memory, such as a memory (1010a), and at least one transceiver, such as a transceiver (1031a). The processor (1020a) may perform the functions, procedures, and / or methods described above. The processor (1020a) may perform one or more protocols. For example, the processor (1020a) may perform one or more layers of a wireless interface protocol. The memory (1010a) may be connected to the processor (1020a) and may store various types of information and / or commands. The transceiver (1031a) may be connected to the processor (1020a) and may be controlled to transmit and receive wireless signals.

[0179] The second device (100b) may include at least one processor, such as a processor (1020b), at least one memory device, such as a memory (1010b), and at least one transceiver, such as a transceiver (1031b). The processor (1020b) may perform the functions, procedures, and / or methods described above. The processor (1020b) may implement one or more protocols. For example, the processor (1020b) may implement one or more layers of a wireless interface protocol. The memory (1010b) may be connected to the processor (1020b) and may store various types of information and / or commands. The transceiver (1031b) may be connected to the processor (1020b) and may be controlled to transmit and receive wireless signals.

[0180] The memory (1010a) and / or the memory (1010b) may be connected internally or externally to the processor (1020a) and / or the processor (1020b), or may be connected to another processor via various technologies such as a wired or wireless connection.

[0181] The first device (100a) and / or the second device (100b) may have one or more antennas. For example, the antenna (1036a) and / or the antenna (1036b) may be configured to transmit and receive wireless signals.

[0182] Fig. 11 is a block diagram showing the configuration of a terminal according to one embodiment of the present specification.

[0183] In particular, FIG. 11 is a drawing illustrating the device of FIG. 10 in more detail.

[0184] The device includes a memory (1010), a processor (1020), a transceiver (1031), a power management module (1091), a battery (1092), a display (1041), an input unit (1053), a speaker (1042), and a microphone (1052), a subscriber identification module (SIM) card, and one or more antennas.

[0185] The processor (1020) may be configured to implement the proposed functions, procedures, and / or methods described herein. Layers of a radio interface protocol may be implemented in the processor (1020). The processor (1020) may include an application-specific integrated circuit (ASIC), other chipsets, logic circuits, and / or data processing devices. The processor (1020) may be an application processor (AP). The processor (1020) may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modem (modulator and demodulator). Examples of the processor (1020) may be a SNAPDRAGON™ series processor manufactured by Qualcomm®, an EXYNOSTM series processor manufactured by Samsung®, an A series processor manufactured by Apple®, a HELIO™ series processor manufactured by MediaTek®, an ATOM™ series processor manufactured by INTEL®, a KIRINTM series processor manufactured by HiSilicon®, or a corresponding next-generation processor.

[0186] The power management module (1091) manages power to the processor (1020) and / or the transceiver (1031). The battery (1092) supplies power to the power management module (1091). The display (1041) outputs the results processed by the processor (1020). The input unit (1053) receives input to be used by the processor (1020). The input unit (1053) can be displayed on the display (1041). A SIM card is an integrated circuit used to securely store an international mobile subscriber identity (IMSI) and its associated keys, which are used to identify and authenticate subscribers in mobile devices such as mobile phones and computers. Contact information can also be stored on many SIM cards.

[0187] The memory (1010) is operably coupled to the processor (1020) and stores various information for operating the processor (610). The memory (1010) may include a read-only memory (ROM), a random access memory (RAM), flash memory, a memory card, a storage medium, and / or other storage devices. When the embodiment is implemented in software, the techniques described herein may be implemented as modules (e.g., procedures, functions, etc.) that perform the functions described herein. The modules may be stored in the memory (1010) and executed by the processor (1020). The memory (1010) may be implemented within the processor (1020). Alternatively, the memory (1010) may be implemented external to the processor (1020) and communicatively connected to the processor (1020) via various means known in the art.

[0188] The transceiver (1031) is operably coupled to the processor (1020) and transmits and / or receives a radio signal. The transceiver (1031) includes a transmitter and a receiver. The transceiver (1031) may include baseband circuitry for processing a radio frequency signal. The transceiver controls one or more antennas to transmit and / or receive a radio signal. The processor (1020) transmits command information to the transceiver (1031) to initiate communication, for example, to transmit a radio signal constituting voice communication data. The antenna functions to transmit and receive radio signals. Upon receiving a radio signal, the transceiver (1031) may transmit the signal to the processor (1020) for processing and convert the signal to baseband. The processed signal may be converted into audible or readable information output through the speaker (1042).

[0189] The speaker (1042) outputs sound-related results processed by the processor (1020). The microphone (1052) receives sound-related input to be used by the processor (1020).

[0190] A user inputs command information, such as a phone number, for example, by pressing (or touching) a button on an input unit (1053) or by voice activation using a microphone (1052). The processor (1020) receives this command information and processes it to perform an appropriate function, such as dialing a phone number. Operational data can be extracted from a SIM card or memory (1010). In addition, the processor (1020) can display command information or operation information on a display (1041) for the user's recognition and convenience.

[0191] Figure 12 shows a block diagram of a processor in which the disclosure of this specification is implemented.

[0192] As can be seen from FIG. 12, the processor (1020) implementing the disclosure of the present specification may include multiple circuits to implement the proposed functions, procedures, and / or methods described herein. For example, the processor (1020) may include a first circuit (1020-1), a second circuit (1020-2), and a third circuit (1020-3). Furthermore, although not shown, the processor (1020) may include more circuits. Each circuit may include multiple transistors.

[0193] The above processor (1020) may be called an application-specific integrated circuit (ASIC) or an application processor (AP), and may include at least one of a digital signal processor (DSP), a central processing unit (CPU), and a graphics processing unit (GPU).

[0194] FIG. 13 is a block diagram showing in detail the transmitter / receiver of the first device illustrated in FIG. 10 or the transmitter / receiver unit of the device illustrated in FIG. 11.

[0195] Referring to FIG. 13, the transceiver unit (1031) includes a transmitter (1031-1) and a receiver (1031-2). The transmitter (1031-1) includes a Discrete Fourier Transform (DFT) unit (1031-11), a subcarrier mapper (1031-12), an IFFT unit (1031-13), a CP insertion unit (1031-14), and a wireless transmitter unit (1031-15). The transmitter (1031-1) may further include a modulator. In addition, for example, the transmitter may further include a scramble unit (not shown), a modulation mapper (not shown), a layer mapper (not shown), and a layer permutator (not shown), which may be arranged before the DFT unit (1031-11). That is, in order to prevent an increase in PAPR (peak-to-average power ratio), the transmitter (1031-1) first passes the information through a DFT (1031-11) before mapping the signal to a subcarrier. The signal spread (or precoded in the same sense) by the DFT unit (1031-11) is mapped to a subcarrier through a subcarrier mapper (1031-12) and then passes through an IFFT (Inverse Fast Fourier Transform) unit (1031-13) to be converted into a signal on the time axis.

[0196] The DFT unit (1031-11) performs DFT on the input symbols and outputs complex-valued symbols. For example, if Ntx symbols are input (where Ntx is a natural number), the DFT size is Ntx. The DFT unit (1031-11) may be called a transform precoder. The subcarrier mapper (1031-12) maps the complex symbols to each subcarrier in the frequency domain. The complex symbols may be mapped to resource elements corresponding to resource blocks allocated for data transmission. The subcarrier mapper (1031-12) may be called a resource element mapper. The IFFT unit (1031-13) performs IFFT on the input symbols and outputs a baseband signal for data, which is a time-domain signal. The CP insertion unit (1031-14) copies a portion of the rear portion of the baseband signal for data and inserts it into the front portion of the baseband signal for data. CP insertion prevents ISI (Inter-Symbol Interference) and ICI (Inter-Carrier Interference), thereby maintaining orthogonality even in multipath channels.

[0197] On the other hand, the receiver (1031-2) includes a wireless reception unit (1031-21), a CP removal unit (1031-22), an FFT unit (1031-23), and an equalization unit (1031-24). The wireless reception unit (1031-21), the CP removal unit (1031-22), and the FFT unit (1031-23) of the receiver (1031-2) perform the inverse functions of the wireless transmission unit (1031-15), the CP insertion unit (1031-14), and the IFF unit (1031-13) of the transmitter (1031-1). The receiver (1031-2) may further include a demodulator.

[0198] Although the preferred embodiments have been described above by way of example, the disclosure of this specification is not limited to such specific embodiments, and may be modified, changed, or improved in various forms within the scope described in the spirit and claims of this specification.

[0199] In the exemplary system described above, the methods are described based on a flowchart as a series of steps or blocks. However, the order of the steps described is not limited, and some steps may occur in a different order or simultaneously with other steps described above. Furthermore, those skilled in the art will understand that the steps depicted in the flowchart are not exclusive, and other steps may be included, or one or more steps in the flowchart may be deleted without affecting the scope of the invention.

[0200] The claims set forth in this specification may be combined in various ways. For example, the technical features of the method claims of this specification may be combined and implemented as a device, and the technical features of the device claims of this specification may be combined and implemented as a method. Furthermore, the technical features of the method claims and the technical features of the device claims of this specification may be combined and implemented as a device, and the technical features of the method claims and the technical features of the device claims of this specification may be combined and implemented as a method.

Claims

1. In a method for a terminal to perform an operation for PUSCH (physical uplink shared channel) transmission in a wireless communication system, A step of receiving TDD (time duplex division) setting information, UL BWP (bandwidth part) setting information, and UL subband setting information; A step of receiving downlink control information (DCI) including scheduling information for at least one PUSCH transmission; A step of determining a slot for at least one PUSCH transmission based on the DCI, The slot for the at least one PUSCH transmission is determined by whether the PUSCH transmission symbol in the slot includes an invalid symbol according to the scheduling information included in the DCI, A method in which the invalid symbol is determined based on subband full duplex (SBFD) symbol information by the TDD configuration information and the UL subband configuration information associated with the UL BWP.

2. In paragraph 1, A method in which PUSCH transmission is not performed in a slot including the invalid symbol.

3. In paragraph 1, The method wherein the invalid symbol includes a non-SBFD symbol among the downlink (DL) symbols for which a UL subband is not configured according to the TDD configuration information.

4. In paragraph 1, The method according to claim 1, wherein the invalid symbol includes a symbol in which a UL subband is set among the downlink (DL) symbols according to the TDD setting information, and a symbol instructed and / or set to receive DL by the base station.

5. In paragraph 1, The invalid symbol includes i) a non-SBFD symbol in which a UL subband is not set among the downlink (DL) symbols according to the TDD configuration information, and ii) a symbol in which a UL subband is set among the downlink (DL) symbols according to the TDD configuration information, and a symbol in which DL reception is instructed and / or set by the base station. A method in which a symbol not included in the above invalid symbols is a valid PUSCH transmission symbol.

6. In paragraph 1, A method wherein the invalid symbol is any non-SBFD symbol for which the UL subband is not configured, or any SBFD symbol for which the UL subband is configured.

7. In paragraph 6, Whether PUSCH transmission is performed for the above non-SBFD symbol and / or the above SBFD symbol, i) determined based on instructions through the above DCI, or ii) determined by the symbol type of the first PUSCH transmission by the above DCI, or iii) A method in which the DCI is determined by the symbol type transmitted.

8. In paragraph 1, A method in which the DCI is in a format including i) a scheduling information area in a slot type composed of SBFD symbols, ii) a scheduling information area in a slot type composed of non-SBFD symbols, and iii) an information area common to the slot types.

9. As a communication device in a wireless communication system, at least one processor; and At least one memory storing instructions and being operably electrically connectable to the at least one processor, wherein the operations performed based on the instructions being executed by the at least one processor are: A step of receiving TDD (time duplex division) setting information, UL BWP (bandwidth part) setting information, and UL subband setting information, A step of receiving downlink control information (DCI) including scheduling information for at least one PUSCH transmission, and A step of determining a slot for at least one PUSCH transmission based on the DCI, The slot for the at least one PUSCH transmission is determined by whether the PUSCH transmission symbol in the slot includes an invalid symbol according to the scheduling information included in the DCI, A communication device, wherein the invalid symbol is determined based on subband full duplex (SBFD) symbol information by the TDD configuration information and the UL subband configuration information associated with the UL BWP.

10. In paragraph 9, A communication device in which PUSCH transmission is not performed in a slot including the invalid symbol.

11. In paragraph 9, The above invalid symbol is a communication device including a non-SBFD symbol for which a UL subband is not set among downlink (DL) symbols according to the TDD setting information.

12. In paragraph 9, The above invalid symbol is a communication device, wherein a symbol in which a UL subband is set among downlink (DL) symbols according to the TDD setting information is a symbol instructed and / or set to receive DL by a base station.

13. In paragraph 9, The invalid symbol includes i) a non-SBFD symbol in which a UL subband is not set among the downlink (DL) symbols according to the TDD configuration information, and ii) a symbol in which a UL subband is set among the downlink (DL) symbols according to the TDD configuration information, and a symbol in which DL reception is instructed and / or set by the base station. A communication device, wherein a symbol not included in the above invalid symbols is a valid PUSCH transmission symbol.

14. In paragraph 9, A communication device wherein the invalid symbol is any non-SBFD symbol for which the UL subband is not configured, or any SBFD symbol for which the UL subband is configured.

15. In paragraph 14, Whether PUSCH transmission is performed for the above non-SBFD symbol and / or the above SBFD symbol, i) determined based on instructions through the above DCI, or ii) determined by the symbol type of the first PUSCH transmission by the above DCI, or iii) A communication device, wherein the DCI is determined by the symbol type transmitted.

16. In paragraph 9, A communication device, wherein the DCI is a format including i) a scheduling information area in a slot type composed of SBFD symbols, ii) a scheduling information area in a slot type composed of non-SBFD symbols, and iii) an information area common to the slot type.

Images