Operation method of device in wireless communication system, and device using same method

Abstract

Provided are an operation method of a device in a wireless communication system, and a device using the method. The method includes: receiving, by a UE, a system information block (SIB), the SIB including sub-band full duplex (SBFD) time information for configuring a time position of cell-specific SBFD sub-band; and receiving, by the UE, downlink control information (DCI) including a slot format indicator (SFI) indicating a slot format including downlink symbols, uplink symbols, and flexible symbols, wherein the UE corresponds to a SBFD aware UE and the UE applies the SFI only to non-SBFD symbols among SBFD symbols based on the SBFD time information and the non-SBFD symbols.

Description

Method of operating a device in a wireless communication system and a device using the method

[0001] The present disclosure relates to a method of operating a device in a wireless communication system and a device using the method.

[0002] As more and more communication devices demand greater communication capacity, the need for improved mobile broadband communications over existing radio access technology (RAT) is emerging. Furthermore, massive Machine Type Communications (MTC), which connects numerous devices and objects to provide diverse services anytime, anywhere, is also a key issue to be considered in next-generation communications. Furthermore, communication system design that considers reliability and latency-sensitive services / terminals is being discussed. The introduction of next-generation radio access technologies that take into account enhanced mobile broadband communications, massive MTC, and URLLC (Ultra-Reliable and Low Latency Communication) is being discussed, and for convenience, these technologies are referred to as new RAT or NR in this disclosure.

[0003] Wireless communication systems, whether NR or later, can perform full duplex (FD) operation. In FD operation, a device can simultaneously perform downlink reception and uplink transmission within a specific time resource. This differs from half duplex (HD) operation, which can perform either downlink reception or uplink transmission within a specific time resource.

[0004] For FD operation, i) some frequency resources in the same time resource may be allocated as downlink subbands and other frequency resources as uplink subbands (this may be referred to as subband FD, or subband full duplex (SBFD), or ii) frequency resources that can be used for both downlink reception and uplink transmission in the same time resource may be allocated (this may be referred to as spectrum shared FD, or spectrum-sharing full duplex (SSFD).

[0005] The current standard does not clearly define how the network will inform UEs of FD resources, such as SBFD resources. Furthermore, slot format indicators (SFIs), which indicate symbols within a slot as downlink symbols, uplink symbols, and flexible symbols, are provided to UEs through dynamic signaling, such as downlink control information (DCI) transmitted over the physical downlink control channel (PDCCH). It is also unclear how these SFIs will be applied in wireless communication systems using SBFD. Furthermore, when repeatedly transmitting uplink data channels, transmission methods can be defined based on available slots. However, the current standard does not consider SBFD resources; it determines whether a specific slot is available and the number of available slots. Therefore, it is difficult to directly apply the current standard to communication systems using SBFD.

[0006] The technical problem to be solved by the present disclosure is to provide a method of operating a device in a wireless communication system and a device using the method.

[0007] A method of operating a device in a wireless communication system and a device using the method are provided. According to the method, a terminal receives a system information block (SIB), wherein the SIB includes subband full duplex (SBFD) time information that sets the time position of a cell-specific subband full duplex (SBFD) subband, and receives downlink control information (DCI) including a slot format indicator (SFI) that indicates a slot format including downlink symbols, uplink symbols, and flexible symbols, wherein the terminal is an SBFD aware UE, and the terminal applies the SFI only to the non-SBFD symbols among the SBFD symbols and non-SBFD symbols based on the SBFD time information.

[0008] In another aspect, a terminal, device, or computer-readable medium for executing the above method is provided.

[0009] In another aspect, a method of operating a base station and a base station using the method are provided. According to the method of operating the base station, the base station transmits a system information block (SIB), the SIB including SBFD time information that sets the time position of a cell-specific subband full duplex (SBFD) subband, and transmits downlink control information (DCI) including a slot format indicator (SFI) that indicates a slot format including downlink symbols, uplink symbols, and flexible symbols to an SBFD-aware UE, and the base station communicates with the SBFD-aware UE based on the SFI being applied only to the non-SBFD symbols among SBFD symbols and non-SBFD symbols based on the SBFD time information.

[0010] According to the method according to the present disclosure, in a wireless communication system where SBFD is used, for SBFD time resources (SBFD symbols) configured via SIB, it is made clear that a dynamically configured slot format indicator (SFI), e.g., an SFI provided via a specific DCI format, is not applied and is only applied to non-SBFD symbols. Accordingly, ambiguity regarding the application of the SFI does not arise between the network and the terminal.

[0011] In addition, in the existing PUSCH repetitive transmission, the available slots were counted without considering the configuration of the SBFD time resource. However, in the method of the present disclosure, the available slot counting is performed by considering the configuration of the SBFD time resource. For example, if a symbol indicated as downlink by a cell-specific TDD configuration in a specific slot is indicated as an SBFD symbol by the SBFD time information of the SIB, even if the SBFD symbol and the PUSCH transmission symbol overlap, the specific slot is not excluded from the available slots for PUSCH transmission. Therefore, more efficient PUSCH repetitive transmission considering the SBFD configuration is possible.

[0012] Figure 1 illustrates a wireless communication system to which the present disclosure can be applied.

[0013] Figure 2 is a block diagram showing a radio protocol architecture for a user plane.

[0014] Figure 3 is a block diagram showing the wireless protocol structure for the control plane.

[0015] Figure 4 illustrates the system architecture of a New Generation Radio Access Network (NG-RAN) to which NR is applied.

[0016] Figure 5 illustrates the functional division between NG-RAN and 5GC.

[0017] Figure 6 illustrates a frame structure that can be applied in NR.

[0018] Figure 7 illustrates a slot structure.

[0019] Figure 8 illustrates a core set.

[0020] Figure 9 illustrates an example of a frame structure for a new wireless access technology.

[0021] Figure 10 illustrates the structure of a self-contained slot.

[0022] Figure 11 illustrates physical channels and general signal transmission.

[0023] Figure 12 is an example of PUSCH repetition type A.

[0024] Figure 13 is an example of PUSCH repetition type B.

[0025] Figure 14 shows examples of how to apply full duplex within a carrier.

[0026] Figure 15 shows examples where time resources operating in HD (half duplex) and time resources operating in FD (full duplex), such as SBFD or SSFD, coexist.

[0027] Figure 16 shows examples of a first time resource, a second time resource, a first frequency resource, and a second frequency resource.

[0028] Figure 17 illustrates another example of a first time resource, a second time resource, a first frequency resource, and a second frequency resource.

[0029] FIG. 18 illustrates terminal operation according to one embodiment of the present disclosure.

[0030] FIG. 19 illustrates a signaling and operation method between a base station and a terminal according to one embodiment of the present disclosure.

[0031] FIG. 20 illustrates an operation method of a base station according to one embodiment of the present disclosure.

[0032] Figure 21 illustrates a wireless device applicable to the present specification.

[0033] Figure 22 illustrates an example of a signal processing module structure.

[0034] Figure 23 illustrates another example of the structure of a signal processing module within a transmission device.

[0035] FIG. 24 illustrates an example of a wireless communication device according to an implementation example of the present disclosure.

[0036] Figure 25 illustrates another example of a wireless device.

[0037] Fig. 26 illustrates a communication system (1) applicable to this specification.

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

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

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

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

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

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

[0044] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals / messages / fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0045] Figure 1 illustrates a wireless communication system to which the present disclosure may be applied. This may also be referred to as an Evolved-UMTS Terrestrial Radio Access Network (E-UTRAN) or a Long Term Evolution (LTE) / LTE-A system.

[0046] E-UTRAN includes a base station (BS) 20 that provides a control plane and a user plane to a user equipment (UE) 10. The UE 10 may be fixed or mobile, and may be referred to by other terms such as a mobile station (MS), a user terminal (UT), a subscriber station (SS), a mobile terminal (MT), a wireless device, or a terminal. The base station (20) refers to a fixed station that communicates with the UE 10, and may be referred to by other terms such as an evolved-NodeB (eNB), a base transceiver system (BTS), or an access point.

[0047] Base stations (20) can be connected to each other via the X2 interface. The base station (20) is connected to an EPC (Evolved Packet Core, 30) via the S1 interface, more specifically, to an MME (Mobility Management Entity) via the S1-MME, and to an S-GW (Serving Gateway) via the S1-U.

[0048] The EPC (30) consists of an MME, an S-GW, and a P-GW (Packet Data Network-Gateway). The MME holds information about terminal access and capabilities, and this information is primarily used for terminal mobility management. The S-GW is a gateway with the E-UTRAN as its endpoint, and the P-GW is a gateway with the PDN as its endpoint.

[0049] The layers of the radio interface protocol between the terminal and the network can be divided into L1 (layer 1), L2 (layer 2), and L3 (layer 3) based on the three lower layers of the Open System Interconnection (OSI) standard model, which is widely known in communication systems. Among these, the physical layer belonging to layer 1 provides information transfer service using physical channels, and the RRC (Radio Resource Control) layer located in layer 3 controls radio resources between the terminal and the network. To this end, the RRC layer exchanges RRC messages between the terminal and the base station.

[0050] Figure 2 is a block diagram illustrating the radio protocol architecture for the user plane. Figure 3 is a block diagram illustrating the radio protocol architecture for the control plane. The user plane is a protocol stack for transmitting user data, and the control plane is a protocol stack for transmitting control signals.

[0051] Referring to Figures 2 and 3, the physical layer (PHY layer) provides information transfer services to upper layers using physical channels. The PHY layer is connected to its upper layer, the Medium Access Control (MAC) layer, through a transport channel. Data is transferred between the MAC layer and the PHY layer via the transport channel. Transport channels are classified based on how and with what characteristics data is transmitted over the wireless interface.

[0052] Data travels between different physical layers, i.e., between the physical layers of a transmitter and receiver, via a physical channel. This physical channel can be modulated using Orthogonal Frequency Division Multiplexing (OFDM) and utilizes time and frequency as radio resources.

[0053] The MAC layer's functions include mapping between logical channels and transport channels, and multiplexing / demultiplexing MAC service data units (SDUs) belonging to logical channels into transport blocks provided as physical channels on the transport channels. The MAC layer provides services to the RLC (Radio Link Control) layer through logical channels.

[0054] The functions of the RLC layer include concatenation, segmentation, and reassembly of RLC SDUs. To guarantee the various Quality of Service (QoS) required by radio bearers (RBs), the RLC layer provides three operating modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). AM RLC provides error correction through automatic repeat request (ARQ).

[0055] The RRC (Radio Resource Control) layer is defined only in the control plane. The RRC layer is responsible for controlling logical, transport, and physical channels, including the configuration, reconfiguration, and release of radio bearers. An RB is a logical path provided by Layer 1 (PHY layer) and Layer 2 (MAC layer, RLC layer, PDCP layer) for data transmission between a terminal and the network.

[0056] The functions of the Packet Data Convergence Protocol (PDCP) layer in the user plane include the transmission of user data, header compression, and ciphering. The functions of the Packet Data Convergence Protocol (PDCP) layer in the control plane include the transmission of control plane data and encryption / integrity protection.

[0057] Establishing an RB refers to the process of defining the characteristics of the radio protocol layer and channel to provide a specific service, and setting specific parameters and operating methods for each. RBs can be further divided into two types: signaling RBs (SRBs) and data RBs (DRBs). SRBs are used as a conduit for transmitting RRC messages in the control plane, while DRBs are used as conduits for transmitting user data in the user plane.

[0058] When an RRC connection is established between the RRC layer of the terminal and the RRC layer of the E-UTRAN, the terminal is in an RRC connected state, otherwise it is in an RRC idle state.

[0059] Downlink transmission channels that transmit data from the network to the terminal include the Broadcast Channel (BCH), which transmits system information, and the downlink Shared Channel (SCH), which transmits user traffic or control messages. Traffic or control messages for downlink multicast or broadcast services may be transmitted through the downlink SCH or a separate downlink Multicast Channel (MCH). Meanwhile, uplink transmission channels that transmit data from the terminal to the network include the Random Access Channel (RACH), which transmits initial control messages, and the uplink Shared Channel (SCH), which transmits user traffic or control messages.

[0060] Logical channels that are located above the transport channel and are mapped to the transport channel include BCCH (Broadcast Control Channel), PCCH (Paging Control Channel), CCCH (Common Control Channel), MCCH (Multicast Control Channel), and MTCH (Multicast Traffic Channel).

[0061] A physical channel consists of multiple OFDM symbols in the time domain and multiple subcarriers in the frequency domain. A single subframe consists of multiple OFDM symbols in the time domain. A resource block is a resource allocation unit and consists of multiple OFDM symbols and multiple subcarriers. Additionally, each subframe can use specific subcarriers of specific OFDM symbols (e.g., the first OFDM symbol) of the subframe for the Physical Downlink Control Channel (PDCCH), i.e., the L1 / L2 control channel. A Transmission Time Interval (TTI) is a unit time for subframe transmission.

[0062] Below, we describe new radio access technology (new RAT, NR).

[0063] As more and more communication devices demand greater communication capacity, the need for improved mobile broadband communications over existing radio access technology (RAT) is emerging. Furthermore, massive Machine Type Communications (MTC), which connects numerous devices and objects to provide diverse services anytime, anywhere, is also a key issue to be considered in next-generation communications. Furthermore, communication system design that considers reliability and latency-sensitive services / terminals is being discussed. The introduction of next-generation radio access technologies that take enhanced mobile broadband communications, massive MTC, and URLLC (Ultra-Reliable and Low Latency Communication) into account is being discussed. For convenience, these technologies are referred to herein as new RAT or NR.

[0064] Figure 4 illustrates the system architecture of a New Generation Radio Access Network (NG-RAN) to which NR is applied.

[0065] Referring to FIG. 4, the NG-RAN may include gNBs and / or eNBs that provide user plane and control plane protocol termination to the UE. FIG. 4 illustrates a case where only gNBs are included. The gNBs (eNBs) are connected to each other via Xn interfaces. The gNBs and eNBs are connected to the 5th generation core network (5G Core Network: 5GC) via the NG interface. More specifically, they are connected to the access and mobility management function (AMF) via the NG-C interface, and to the user plane function (UPF) via the NG-U interface.

[0066] Figure 5 illustrates the functional division between NG-RAN and 5GC.

[0067] Referring to FIG. 5, the gNB can provide functions such as inter-cell radio resource management (Inter Cell RRM), radio bearer management (RB control), connection mobility control (Connection Mobility Control), radio admission control (Radio Admission Control), measurement configuration and provision, and dynamic resource allocation. The AMF can provide functions such as NAS security and idle state mobility processing. The UPF can provide functions such as mobility anchoring and PDU processing. The SMF (Session Management Function) can provide functions such as terminal IP address allocation and PDU session control.

[0068] Figure 6 illustrates a frame structure that can be applied in NR.

[0069] Referring to FIG. 6, a radio frame (hereinafter abbreviated as a frame) can be used for uplink and downlink transmission in NR. A frame has a length of 10 ms and can be defined as two 5 ms half-frames (Half-Frames, HF). A half-frame can be defined as five 1 ms sub-frames (Subframes, SF). A sub-frame can be divided into one or more slots, and the number of slots in a sub-frame depends on the Subcarrier Spacing (SCS). Each slot contains 12 or 14 OFDM (A) symbols depending on the CP (cyclic prefix). 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 can include an OFDM symbol (or a CP-OFDM symbol), an SC-FDMA symbol (or a DFT-s-OFDM symbol).

[0070] Table 1 below illustrates the subcarrier spacing configuration μ (also referred to as subcarrier spacing configuration).

[0071] [Table 1]

[0072]

[0073] Table 2 below shows the number of slots (N) in a frame according to the subcarrier spacing setting μ. frame,μ slot ), number of slots in a subframe (N subframe,μ slot ), number of symbols in the slot (N slot symb ) are examples.

[0074] [Table 2]

[0075]

[0076] In Fig. 6, examples are given for μ=0, 1, 2, and 3.

[0077] Table 2-1 below illustrates that when extended CP is used, the number of symbols per slot, the number of slots per frame, and the number of slots per subframe change depending on the SCS.

[0078] [Table 2-1]

[0079]

[0080] In an NR system, OFDM(A) numerologies (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.

[0081] Figure 7 illustrates a slot structure.

[0082] A slot can contain multiple symbols in the time domain. For example, in the case of a normal CP, one slot can contain 14 symbols (or 7 symbols), but in the case of an extended CP, one slot can contain 12 symbols (or 6 symbols). A carrier can contain multiple subcarriers in the frequency domain. A Resource Block (RB) can be defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A Bandwidth Part (BWP) can be defined as multiple consecutive (P)RBs in the frequency domain, and can correspond to a single numerology (e.g., SCS, CP length, etc.). A carrier can contain up to N BWPs (e.g., 4 or 5). Data communication is performed through activated BWPs, and only one BWP can be activated for a single terminal. In the resource grid, each element is referred to as a Resource Element (RE), to which one complex symbol can be mapped.

[0083] A PDCCH (physical downlink control channel) may be composed of one or more CCEs (control channel elements) as shown in Table 3 below.

[0084] [Table 3]

[0085]

[0086] That is, the PDCCH can be transmitted through a resource consisting of 1, 2, 4, 8, or 16 CCEs. Here, the CCEs are composed of 6 REGs (resource element groups), and one REG consists of one resource block in the frequency domain and one OFDM (orthogonal frequency division multiplexing) symbol in the time domain.

[0087] Monitoring refers to decoding each PDCCH candidate according to the DCI (downlink control information) format. The terminal monitors a set of PDCCH candidates in one or more core sets (CORESETs, described below) on the active DL BWP of each activated serving cell for which PDCCH monitoring is configured, according to the corresponding search space set.

[0088] In NR, a new unit called a control resource set (CORESET) can be introduced. A terminal can receive PDCCHs in a CORESET.

[0089] Figure 8 illustrates a core set.

[0090] Referring to Figure 8, the coreset is N in the frequency domain. CORESET RB It consists of N resource blocks and is in the time domain. CORESET symb ∈ {1, 2, 3} symbols. N CORESET RB, N CORESET symb can be provided by the base station via upper layer signals. As illustrated in Fig. 8, a core set may include multiple CCEs (or REGs).

[0091] A terminal may attempt PDCCH detection in units of 1, 2, 4, 8, or 16 CCEs within a core set. One or more CCEs for which PDCCH detection can be attempted may be referred to as PDCCH candidates.

[0092] A terminal can be configured with multiple core sets.

[0093] In conventional wireless communication systems (e.g., LTE / LTE-A), the control domain spans the entire system bandwidth used by the base station. Except for some terminals that support only narrow bandwidths (e.g., eMTC / NB-IoT terminals), all terminals must be able to receive radio signals across the entire system bandwidth of the base station to properly receive / decode the control information transmitted by the base station.

[0094] In contrast, NR introduces the aforementioned core set. A core set is a radio resource for control information that a terminal must receive. It can utilize only a portion of the system bandwidth in the frequency domain, rather than the entire bandwidth. Furthermore, it can utilize only a portion of the symbols within a slot in the time domain. The base station can assign a core set to each terminal and transmit control information through the assigned core set. In NR, a terminal can receive control information from the base station without necessarily receiving the entire system bandwidth.

[0095] The core set may include a terminal-specific core set for transmitting terminal-specific control information and a common core set for transmitting control information common to all terminals.

[0096] Meanwhile, in NR, depending on the application field, high reliability may be required, and in such a situation, the target block error rate (BLER) for downlink control information (DCI) transmitted through a downlink control channel (e.g., physical downlink control channel: PDCCH) may be significantly lower than in the prior art. One example of a method for satisfying such a requirement requiring high reliability is to reduce the amount of content included in the DCI and / or increase the amount of resources used when transmitting the DCI. In this case, the resources may include at least one of time domain resources, frequency domain resources, code domain resources, and spatial domain resources.

[0097] The following technologies / features can be applied in NR:

[0098] Self-contained subframe structure

[0099] Figure 9 illustrates an example of a frame structure for a new wireless access technology.

[0100] In NR, for the purpose of minimizing latency, a structure in which a control channel and a data channel are time-division multiplexed (TDM) within one TTI, as shown in Fig. 9, can be considered as one of the frame structures.

[0101] Figure 9 shows an example in which a downlink control region is located at the front of the TTI and an uplink control region is located at the back of the TTI. The region between the downlink control region and the uplink control region can be used for downlink data (DL data) transmission or uplink data (UL data) transmission. A characteristic of this structure is that downlink (DL) reception and uplink (UL) transmission are sequentially performed within a single subframe / slot, so that DL data can be received and UL ACK / NACK (Acknowledgement / Not-acknowledgement) can be transmitted within a single subframe / slot. As a result, the time required for data retransmission when a data transmission error occurs is reduced, thereby minimizing the latency of the final data transmission.

[0102] In this way, in a data and control TDMed subframe structure, a time gap is required for the base station and terminal to transition from transmission mode to reception mode or from reception mode to transmission mode. To this end, some OFDM symbols at the point of transition from DL to UL in a self-contained subframe structure can be set as a guard period (GP).

[0103] Figure 10 illustrates the structure of a self-contained slot.

[0104] In an NR system, a single slot may contain a DL control channel, DL or UL data, and a UL control channel. For example, the first N symbols in a slot may be used to transmit a DL control channel (hereinafter, referred to as a DL control region), and the last M symbols in the slot may 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. A resource region (hereinafter, referred to as a data region) between the DL control region and the UL control region may be used for DL ​​data transmission or UL data transmission. As an example, the following configuration may be considered. Each section is listed in chronological order.

[0105] 1. DL only configuration

[0106] 2. UL only configuration

[0107] 3. Mixed UL-DL configuration

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

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

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

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

[0112] In the DL control region, a PDCCH can be transmitted, and in the DL data region, a PDSCH (physical downlink shared channel) can be transmitted. In the UL control region, a PUCCH (physical uplink control channel) can be transmitted, and in the UL data region, a PUSCH (physical uplink shared channel) can be transmitted. In the PDCCH, downlink control information (DCI), such as DL data scheduling information and UL data scheduling information, can be transmitted. In the PUCCH, uplink control information (UCI), such as ACK / NACK (Positive Acknowledgement / Negative Acknowledgement) information for DL ​​data, CSI (Channel State Information) information, and SR (Scheduling Request), can be transmitted. GP provides a time gap when a base station and a terminal switch from transmission mode to reception mode or 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.

[0113] Analog Beamforming #1

[0114] In millimeter wave (mmW), the wavelength is shortened, allowing for the installation of multiple antenna elements in the same area. That is, in the 30 GHz band, the wavelength is 1 cm, allowing for a total of 100 antenna elements to be installed in a two-dimensional array at 0.5 wavelength (lambda) intervals on a 5 x 5 cm panel. Therefore, in mmW, multiple antenna elements are used to increase beamforming (BF) gain, thereby increasing coverage or throughput.

[0115] In this case, if there is a transceiver unit (TXRU) that allows transmission power and phase control for each antenna element, independent beamforming is possible for each frequency resource. However, it is not practical in terms of cost to install a TXRU for all 100 or so antenna elements. Therefore, a method of mapping multiple antenna elements to a single TXRU and controlling the direction of the beam with an analog phase shifter is being considered. This analog beamforming method has the disadvantage of being unable to perform frequency-selective beamforming because it can only create one beam direction for the entire band.

[0116] Hybrid beamforming (hybrid BF), which has B TXRUs, which is less than Q antenna elements, can be considered as an intermediate form between digital beamforming (Digital BF) and analog beamforming (Analog BF). In this case, depending on the connection method of the B TXRUs and Q antenna elements, the number of beam directions that can be transmitted simultaneously is limited to B or fewer.

[0117] Analog Beamforming #2

[0118] In NR systems, when multiple antennas are used, a hybrid beamforming technique that combines digital beamforming and analog beamforming is emerging. In this case, analog beamforming (or RF beamforming) performs precoding (or combining) at the RF end, which has the advantage of achieving performance close to digital beamforming while reducing the number of RF chains and D / A (or A / D) converters. For convenience, the hybrid beamforming structure can be expressed as N TXRUs and M physical antennas. Then, the digital beamforming for L data layers to be transmitted from the transmitter can be expressed as an N by L matrix, and the N converted digital signals are converted into analog signals through the TXRU, and then analog beamforming expressed as an M by N matrix is ​​applied.

[0119] System information of an NR system can be transmitted in a broadcasting manner. At this time, analog beams belonging to different antenna panels within one symbol can be transmitted simultaneously, and a method of introducing a beam reference signal (BRS), which is a reference signal (RS) transmitted by applying a single analog beam (corresponding to a specific antenna panel) to measure a channel for each analog beam, is being discussed. The BRS can be defined for multiple antenna ports, and each antenna port of the BRS can correspond to a single analog beam. At this time, unlike the BRS, a synchronization signal or xPBCH can be transmitted by applying all analog beams within an analog beam group so that any terminal can receive it well.

[0120] In NR, a synchronization signal block (SSB, or may be referred to as a synchronization signal and physical broadcast channel (SS / PBCH) in the time domain) may be composed of four OFDM symbols numbered in ascending order from 0 to 3 within the synchronization signal block, and a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a PBCH associated with a demodulation reference signal (DMRS) may be mapped to the symbols. As described above, the synchronization signal block may also be referred to as an SS / PBCH block.

[0121] In NR, multiple synchronization signal blocks can be transmitted at different times, and SSB can be used to perform initial access (IA), serving cell measurement, etc. Therefore, when the transmission timing and resources overlap with other signals, it is desirable to transmit SSB preferentially. To achieve this, the network can broadcast SSB transmission timing and resource information or indicate it through UE-specific RRC signaling.

[0122] NR can perform beam-based transmission and reception operations. If the reception performance of the current serving beam degrades, a process called beam failure recovery (BFR) can be used to find a new beam.

[0123] Since BFR is not a process for declaring an error / failure in the link between the network and the terminal, it can be assumed that the connection with the current serving cell is maintained even when the BFR process is performed. During the BFR process, measurements are performed on different beams set by the network (a beam can be expressed as a CSI-RS port or an SSB (synchronization signal block) index, etc.) and the best beam for the terminal is selected. The terminal can proceed with the BFR process by performing the RACH process associated with the beam with the best measurement result.

[0124] Now, we will describe the Transmission Configuration Indicator (TCI) state. The TCI state can be set for each core set of the control channel, and parameters for determining the terminal's receive (Rx) beam can be determined based on the TCI state.

[0125] For each downlink bandwidth portion (DL BWP) of a serving cell, a terminal may be configured with up to three core sets. Additionally, for each core set, the terminal may be provided with the following information:

[0126] 1) Coreset index p (e.g., one from 0 to 11, where the index of each coreset can be uniquely determined among the BWPs of a serving cell),

[0127] 2) PDCCH DM-RS scrambling sequence initialization value,

[0128] 3) Interval in the time domain of the core set (can be given in symbol units),

[0129] 4) A set of resource blocks,

[0130] 5) CCE-to-REG mapping parameters,

[0131] 6) Antenna port quasi co-location (QCL) information indicating quasi co-location (QCL) information of DM-RS antenna ports for PDCCH reception in each core set (from a set of antenna port quasi co-locations provided by a higher layer parameter called 'TCI-State');

[0132] 7) Indicating the presence or absence of a transmission configuration indication (TCI) field for a specific DCI format transmitted by PDCCH in the core set, etc.

[0133] Let's explain QCL. If the characteristics of the channel through which a symbol on one antenna port is transmitted can be inferred from the characteristics of the channel through which a symbol on another antenna port is transmitted, then the two antenna ports are said to be in quasi-co-location (QCL). For example, if two signals (A and B) are transmitted from the same transmit antenna array with identical / similar spatial filters applied, the two signals may experience identical / similar channel conditions. From the receiver's perspective, if one of the two signals is received, the channel characteristics of the received signal can be used to detect the other signal.

[0134] In this sense, the fact that A and B are QCL may mean that A and B experienced similar channel conditions, and thus, the channel information estimated to detect A is also useful for detecting B. Here, the channel conditions may be defined by, for example, Doppler shift, Doppler spread, average delay, delay spread, spatial reception parameters, etc.

[0135] The 'TCI-State' parameter associates one or two downlink reference signals with a corresponding QCL type (there are QCL types A, B, C, and D, see Table 4).

[0136] [Table 4]

[0137]

[0138] Each 'TCI-State' may include parameters for establishing a quasi-colocation (QCL) relationship between one or two downlink reference signals and a DM-RS port of a PDSCH (or PDCCH), or a CSI-RS port of a CSI-RS resource.

[0139] Meanwhile, in each DL BWP configured for a terminal in a serving cell, the terminal may be provided with up to 10 search space sets. For each search space set, the terminal may be provided with at least one of the following pieces of information:

[0140] 1) Search space set index s (0≤s<40), 2) Association between core set P and search space set s, 3) PDCCH monitoring period and PDCCH monitoring offset (slot unit), 4) PDCCH monitoring pattern within a slot (e.g., indicating the first symbol of the core set within a slot for PDCCH monitoring), 5) Number of slots in which search space set s exists, 6) Number of PDCCH candidates per CCE aggregation level, 7) Information indicating whether search space set s is CSS (common search space) or USS (UE-specific search space), etc.

[0141] In NR, core set #0 can be configured by PBCH (or terminal-specific signaling for handover, PSCell configuration, or BWP configuration). The search space (SS) set #0 configured by PBCH can have different monitoring offsets (e.g., slot offset, symbol offset) for each associated SSB. This may be necessary to minimize the search space occasions that the terminal must monitor. Alternatively, it may also be necessary to provide a beam sweeping control / data area that can transmit control / data for each beam so that communication with the terminal can be continuously performed in a situation where the best beam of the terminal dynamically changes.

[0142] Figure 11 illustrates physical channels and general signal transmission.

[0143] Referring to Figure 11, in a wireless communication system, a terminal receives information from a base station via the downlink (DL), and the terminal transmits information to the base station via the uplink (UL). The information transmitted and received between the base station and the terminal includes data and various control information, and various physical channels exist depending on the type and purpose of the information they transmit and receive.

[0144] When a terminal is powered on again from a powered-off state or newly enters a cell, it performs an initial cell search operation, such as synchronizing with the base station (S11). To this end, the terminal receives the PSCH (Primary Synchronization Channel) and SSCH (Secondary Synchronization Channel) from the base station to synchronize with the base station and obtain information such as the cell ID (cell identity). In addition, the terminal can obtain broadcast information within the cell by receiving the PBCH (Physical Broadcast Channel) from the base station. In addition, the terminal can receive the DL RS (Downlink Reference Signal) during the initial cell search phase to check the downlink channel status.

[0145] (Initial) cell search can be defined as a procedure in which a terminal acquires time and frequency synchronization with a cell and detects the cell ID of the cell. Cell search can be based on the primary synchronization signal and secondary synchronization signal of the cell, and the PBCH DMRS.

[0146] A terminal that has completed initial cell search can obtain more specific system information by receiving a PDCCH (Physical Downlink Control Channel) and a corresponding PDSCH (Physical Downlink Control Channel) (S12).

[0147] Thereafter, the terminal can perform a random access procedure (Random Access Procedure) to complete connection to the base station (S13-S16). Specifically, the terminal can transmit a preamble through a Physical Random Access Channel (PRACH) (S13) and receive a Random Access Response (RAR) for the preamble through a PDCCH and a corresponding PDSCH (S14). Thereafter, the terminal can transmit a Physical Uplink Shared Channel (PUSCH) using scheduling information in the RAR (S15) and perform a contention resolution procedure (Contention Resolution Procedure) such as a PDCCH and a corresponding PDSCH (which can be considered a process of receiving a contention resolution message) (S16).

[0148] A terminal that has performed the above-described procedure can then perform PDCCH / PDSCH reception (S17) and PUSCH / PUCCH (Physical Uplink Control Channel) transmission (S18) as general uplink / downlink signal transmission procedures. Control information that the terminal transmits to the base station is referred to as UCI (Uplink Control Information). UCI includes HARQ ACK / NACK (Hybrid Automatic Repeat and reQuest Acknowledgement / Negative-ACK), SR (Scheduling Request), CSI (Channel State Information), etc. CSI includes CQI (Channel Quality Indicator), PMI (Precoding Matrix Indicator), RI (Rank Indication), etc. UCI is generally transmitted through PUCCH, but can be transmitted through PUSCH when control information and data must be transmitted simultaneously. In addition, the terminal can aperiodically transmit UCI through PUSCH according to a request / instruction of the network.

[0149] To enable reasonable battery consumption when BA (bandwidth adaptation) is configured, only one uplink BWP and one downlink BWP, or only one downlink / uplink BWP pair, for each uplink carrier can be activated at a time within an active serving cell, while all other BWPs configured in the UE are deactivated. In deactivated BWPs, the UE does not monitor the PDCCH and does not transmit on the PUCCH, PRACH, and UL-SCH.

[0150] For BA, the receive and transmit bandwidth of the terminal need not be as wide as the cell bandwidth and can be adjusted: the width can be commanded to change (e.g., shrinking during periods of low activity to save power), the location in the frequency domain can be moved (e.g., to increase scheduling flexibility), and the subcarrier spacing can be commanded to change (e.g., to allow different services). A subset of the total cell bandwidth of a cell is referred to as a bandwidth part (BWP), and a BA is obtained by setting BWP(s) to the terminal and notifying the terminal which of the set BWPs is currently active. Once a BA is set, the terminal only needs to monitor the PDCCH on one active BWP. That is, there is no need to monitor the PDCCH on the entire downlink frequency of the cell. A BWP inactive timer (independent of the DRX inactive timer described above) is used to switch an active BWP to a default BWP: the timer is restarted upon successful PDCCH decoding, and a switch to the default BWP occurs when the timer expires.

[0151] Below, we describe the integrated access and backhaul link (IAB). For convenience, the proposed approach is based on the new RAT (NR) system. However, the scope of the proposed approach can be expanded to include other systems, such as 3GPP LTE / LTE-A systems, in addition to NR systems.

[0152] One potential technology that aims to enable future cellular network deployment scenarios and applications is support for wireless backhaul and relay links, enabling flexible and very dense deployment of NR cells without the need to proportionally densify the transport network.

[0153] The expected availability of greater bandwidth in NR compared to LTE (e.g., in the mmWave spectrum), along with the native deployment of massive MIMO or multi-beam systems, creates opportunities for the development and deployment of integrated access and backhaul links. This allows for easier deployment of dense networks of self-backhauled NR cells in a more integrated manner by establishing multiple control and data channels / procedures defined to provide connectivity or access to terminals. Such systems are referred to as integrated access and backhaul links (IAB).

[0154] In this disclosure, the following are defined:

[0155] - AC(x): Access link between node(x) and terminal(s).

[0156] - BH(xy): Backhaul link between node(x) and node(y).

[0157] At this time, the node may refer to a DgNB (donor gNB) or a relay node (RN). Here, the DgNB or donor node may be a gNB that provides a function to support backhaul for IAB nodes.

[0158] When relay node 1 and relay node 2 exist, and relay node 1 is connected to relay node 2 via a backhaul link and relays data transmitted and received to relay node 2, relay node 1 is called the parent node of relay node 2, and relay node 2 is called the child node of relay node 1.

[0159] <PUSCH 반복(repetitions)>

[0160] PUSCH repetition types A and B were introduced in the standard specifications (e.g., NR Rel-15 / 16). Transmission is performed as follows depending on the PUSCH repetition type.

[0161] 1) PUSCH repetition type A

[0162] Figure 12 is an example of PUSCH repetition type A.

[0163] Referring to FIG. 12, PUSCH repetition type A is a slot-based PUSCH repetition transmission, and repetition is performed with the same PUSCH transmission start symbol position and PUSCH transmission symbol length for each slot, as illustrated in FIG. 12. At this time, if there is an invalid symbol that cannot be used for PUSCH transmission among the symbol resources constituting a specific PUSCH repetition, the transmission of the corresponding PUSCH repetition is dropped and not performed. For example, when a total of four PUSCH repetition transmissions of Rep0, Rep1, Rep2, and Rep3 are performed in slots N, N+1, N+2, and N+3 (one PUSCH repetition is transmitted in each slot), if an invalid symbol is included in the symbol resources constituting Rep1, the transmission of Rep1 is dropped, and only the transmissions of Rep0, Rep2, and Rep3 are performed. Therefore, the actual number of repetitions performed may be less than the set number of repetitions.

[0164] For PUSCH repetition type A, frequency hopping can be configured for the UE by upper layer parameters. One of two frequency hopping modes can be configured.

[0165] i) Frequency hopping within a slot is applicable to single slot and multi-slot PUSCH transmission.

[0166] ii) Inter-slot frequency hopping is applicable to multi-slot PUSCH transmission.

[0167] 2) PUSCH repetition type B

[0168] Figure 13 is an example of PUSCH repetition type B.

[0169] Referring to Fig. 13, PUSCH repetition type B is repeated in units of the symbol length in which the actual PUSCH is transmitted. For example, as in (a) of Fig. 13, when the PUSCH is transmitted through 10 symbols, PUSCH repetition is performed in units of 10 consecutive symbols. At this time, the repetition that determines the PUSCH repetition transmission time resource without considering slot boundaries, invalid symbols, etc. is called nominal repetition. In Fig. 13 (a), three nominal repetitions (N0, N 1, An example is shown where N2 is set.

[0170] However, in the case of actual PUSCH repetition, a single PUSCH cannot be transmitted while including a slot boundary. That is, if a nominal PUSCH transmission includes a slot boundary (e.g., N0, N2 in (a) of FIG. 13), two actual repetitions are performed with the slot boundary as the boundary, as in (b) of FIG. 13. For example, a nominal repetition N0 is performed with two actual repetitions, such as A0, A1, with the slot boundary as the boundary.

[0171] Additionally, a single PUSCH transmission can only be performed using consecutive symbols. If an invalid symbol exists in the time resource where a PUSCH repetition should be transmitted, the actual repetition is formed using consecutive symbols with the invalid symbol as the boundary. For example, if symbols #0 to #9 constitute a nominal repetition and symbols #3 to #5 are invalid symbols, symbols #0 to #2 and symbols #6 to #9, excluding the invalid symbol, each constitute an actual repetition.

[0172] Invalid symbols may include the following:

[0173] i) Downlink symbol set by semi-static TDD UL-DL setting,

[0174] ii) an invalid symbol pattern set by RRC (which may be set by the invalid symbol pattern indicator);

[0175] iii) SSB symbol set by SIB1, SSB symbol set by 'ServngCellConfigCommon',

[0176] iv) Symbol for PDCCH for SIB1,

[0177] v) Invalid symbol for DL-UL switching set by RRC.

[0178] If a symbol that cannot be used for PUSCH transmission (e.g., a DL symbol indicated by DCI format 2_0) is included within one actual repetition resource, the corresponding actual repetition transmission is dropped and not performed.

[0179] Now, we describe full duplex operation.

[0180] 5G is giving rise to new service types, such as extended reality (XR), AI-based services, and self-driving cars. These services feature dynamic traffic in both downlink (DL) and uplink (UL) directions, and require low latency for traffic transmission (e.g., packets). 5G services will experience explosive growth in traffic to support these diverse new use cases.

[0181] Existing semi-static or dynamic TDD UL / DL configurations suffer from transmission delays and interference between operators. Existing FDD schemes also face limitations in efficient frequency resource utilization in the DL / UL directions. Therefore, the introduction of full-duplex operation within a single carrier is being discussed to achieve low latency and efficient resource utilization in NR.

[0182] Figure 14 shows examples of how to apply full duplex within a carrier.

[0183] Referring to FIG. 14, in the full duplex method, subband-wise full duplex (hereinafter, referred to as subband full duplex or SBFD) as in (a) of FIG. 14 and spectrum-sharing full duplex (hereinafter, referred to as SSFD) as in (b) of FIG. 14 can be considered.

[0184] In the case of SBFD, DL and UL transmission and reception are performed through different frequency resources within the same carrier (e.g., carrier #0). That is, different frequency resources are used for DL ​​and UL for the same time resource.

[0185] In SSFD, DL and UL transmission and reception are performed through the same frequency resources or overlapping frequency resources within the same carrier (e.g., carrier #0). That is, DL and UL can use the same or overlapping frequency resources for the same time resource.

[0186] This full-duplex (FD) operation can also be combined with existing half-duplex (HD) operation. For example, among the time resources used for existing half-duplex-based TDD operation, some of the time resources can be used for full-duplex operation. For example, SBFD or SSFD operation can be performed on the time resources performing full-duplex operation.

[0187] Figure 15 shows examples where time resources operating in HD (half duplex) and time resources operating in FD (full duplex), such as SBFD or SSFD, coexist.

[0188] In (a) of Fig. 15, some time resources operating in SBFD are indicated as SBFD, and time resources operating in half-duplex are indicated as HD. In (b) of Fig. 15, some time resources operating in SSFD are indicated as SSFD, and time resources operating in half-duplex are indicated as HD. The unit of the time resource may be, for example, a slot or a symbol.

[0189] In a time resource operating under SBFD, some frequency resources are used as DL resources, while others are used as UL resources. Between the DL and UL frequency resources, there may be a guard subband that is unused for both DL and UL and remains empty. The guard subband may also be referred to by other terms, such as guard frequency resources or guard subcarrier(s).

[0190] In a time resource operating in SSFD, the entire frequency resource can be used for both DL and UL. Alternatively, to reduce the impact of interference from other adjacent carriers (which may be referred to as adjacent carrier interference (ACI)), some frequency resources at one or both ends of the carrier can be left unused for DL ​​and / or UL. That is, one or both ends of the carrier can be used as guard bands (guard subbands) that are not used for both DL and UL. Alternatively, to reduce the impact of ACI on UL reception, one or both ends of the carrier can be used exclusively for DL ​​transmission.

[0191] In this disclosure, a slot resource operating in half-duplex is referred to as an HD slot, and a slot resource operating in SBFD and a slot resource operating in SSFD are referred to as an SBFD slot (SBFD slot) and an SSFD slot (SSFD slot), respectively. In addition, an SSFD slot and an SSFD slot are collectively referred to as an FD slot.

[0192] In the present disclosure, in a time resource operating as FD, a frequency resource operating as DL among the entire frequency resources is conveniently called a DL subband, and a frequency resource operating as UL may also be called a UL subband.

[0193] In full-duplex operation, both the base station and the terminal can perform full-duplex operation. That is, both the base station and the terminal can simultaneously transmit and receive DL and UL using the same or different frequency resources in the same time resource.

[0194] Alternatively, only the base station can perform full-duplex operation, while the terminals can perform half-duplex operation. The base station can simultaneously transmit and receive DL and UL signals using the same or different frequency resources in the same time resource, but the terminals perform only DL reception or UL transmission in specific time resources. In this case, the base station performs full-duplex operation by performing DL transmission and UL reception with different terminals at the same time.

[0195] In the present disclosure, the base station may perform / support full duplex operation, while the terminal may perform / support half duplex operation. Alternatively, in the present disclosure, both the base station and the terminal may perform / support full duplex operation.

[0196] <SBFD 및 SSFD 동작을 위한 DL / UL 시간 / 주파수 자원의 특성>

[0197] A cell (base station) can perform both DL transmission and UL reception in the same time resource in a FD manner, such as SBFD or SSFD. For example, the base station can perform HD operation in the first time resource and FD operation in the second time resource (which may be any time resource other than the first time resource).

[0198] Through this operation, the network can change the time resource for performing transmission and reception between the first time resource and the second time resource depending on the type of signal / channel being transmitted and received or the terminal performing the transmission and reception. For example, in the case of important signals / channels (e.g., SSB, PRACH) that require high transmission and reception performance with less influence from interference, the resources can be set to transmit and receive only on the first time resource that operates only in half duplex. This allows the transmission and reception performance of the corresponding signals / channels to be maintained while applying full duplex to the cell. Alternatively, in the case of a terminal that cannot properly transmit and receive due to the significant influence of cross link interference (CLI) when operating in full duplex on the second time resource, the transmission and reception performance for the terminal can be guaranteed by setting the resources to perform transmission and reception on the first time resource.

[0199] The terminal / base station performs DL or UL operations across the entire frequency resources that constitute the entire system bandwidth in the first time resource where the HD operation is performed. Within the first time resource where the HD operation is performed, the network performs DL operations through the 1-1 time resource and UL operations through the 1-2 time resource. At this time, the 1-1 time resource and the 1-2 time resource do not overlap with each other.

[0200] The terminal / base station performs FD operation in the second time resource, and the network performs DL operation through all or part of the frequency resources (first frequency resources) among the frequency resources constituting the system band of the cell, and performs UL operation through all or part of the frequency resources (second frequency resources).

[0201] Figure 16 shows examples of a first time resource, a second time resource, a first frequency resource, and a second frequency resource.

[0202] Referring to (a) of FIG. 16, in the first time resource (indicated by A), the device operates in half-duplex. In the second time resource (indicated by B), the device may operate in, for example, SBFD. The resource indicated by DL in the first time resource corresponds to the aforementioned 1-1 time resource, and the resource indicated by UL corresponds to the aforementioned 1-2 time resource.

[0203] Referring to (b) of Fig. 16, the frequency resource operating as DL in the second time resource corresponds to the first frequency resource described above, and the frequency resource operating as UL corresponds to the second frequency resource described above.

[0204] Figure 17 illustrates another example of a first time resource, a second time resource, a first frequency resource, and a second frequency resource.

[0205] Referring to (a) of FIG. 17, in the first time resource (indicated by A), the device operates in half-duplex. In the second time resource (indicated by B), for example, it may operate in SSFD. The resource indicated by DL in the first time resource corresponds to the aforementioned 1-1 time resource, and the resource indicated by UL corresponds to the aforementioned 1-2 time resource.

[0206] Referring to (b) of Fig. 17, the frequency resources operating as DL and DL+UL in the second time resource correspond to the first frequency resource described above, and the frequency resources operating as DL+UL correspond to the second frequency resource described above.

[0207] The first frequency resource and / or the second frequency resource may have all or some of the following characteristics:

[0208] 1) When performing SBFD operation, the first frequency resource and the second frequency resource do not overlap with each other. This is to ensure that DL and UL operations are performed through different frequency resources. At this time, there may be frequency resources that do not correspond to either the first or second frequency resources, and such frequency resources are called guard subbands or guard frequency resources. Such guard frequency resources may be necessary to reduce interference between DL transmission and UL reception. The guard frequency resource may be located between the first and second frequency resources.

[0209] 2) When performing SSFD operation, the first frequency resource and the second frequency resource may overlap. In this case, there may be frequency resources that do not correspond to either the first frequency resource or the second frequency resource, and such frequency resources are called guard subbands or guard frequency resources. Such guard frequency resources may be necessary to reduce interference between DL transmissions on adjacent carriers and / or between DL transmissions and UL reception on adjacent carriers.

[0210] 3) When performing the SBFD operation, the second frequency resource may be configured with continuous frequency resources, and the first frequency resource may be configured with non-contiguous frequency resources. In this case, the first frequency resource may be configured with multiple (for example, two) non-contiguous sets, and each set may be configured with continuous frequency resources. This is to reduce interference of DL transmission on adjacent carriers to UL resources by positioning the second frequency resource used for UL at the center of the frequency resources constituting the cell. Conversely, the first frequency resource may be configured with continuous frequency resources, and the second frequency resource may be configured with non-contiguous frequency resources. In this case, the second frequency resource may be configured with multiple (for example, two) non-contiguous sets, and each set may be configured with continuous frequency resources. This is to reduce interference of DL transmission on UL resources on adjacent carriers by positioning the second frequency resource used for DL ​​at the center of the frequency resources constituting the cell.

[0211] 4) When performing SSFD operation, the second frequency resource may be configured with a portion of the frequency resources of the first frequency resource. In this case, the second frequency resource may be configured with X PRBs (physical resource blocks) less than the first frequency resource for one or both edge portions of the carrier. This is to reduce interference between DL transmission on adjacent carriers and UL reception.

[0212] Through the above operation, the base station can perform a half-duplex operation in which only one of DL transmission or UL reception is performed in the entire frequency resources constituting the cell in the first time resource, and a full-duplex operation in which DL transmission is performed through the first frequency resource within the frequency resources constituting the cell and UL reception is simultaneously performed through the second frequency resource within the frequency resources constituting the cell in the second time resource.

[0213] The network can determine / judge the 'first time resource' and the 'second time resource', and the 'first frequency resource' and the 'second frequency resource' as described above, and provide all or part of the corresponding information to the terminal. The network can perform DL transmission to the terminal in the '1-1 time resource within the first time' and the '1 frequency resource within the second time resource', and perform UL reception from the terminal in the '1-2 time resource within the first time resource' and the '2 frequency resource within the second time resource'.

[0214] The terminal can receive all or part of the information about the 'first time resource' and the 'second time resource' and the 'first frequency resource' and the 'second frequency resource' from the network, and determine the location of the resources. The terminal can perform DL reception from the network through all or part of the '1-1 time resource within the first time' and the '1 frequency resource within the second time resource', and perform UL transmission to the network through the '1-2 time resource within the first time resource' and the '2 frequency resource within the second time resource'.

[0215] Hereinafter, at least one of the following resources may mean a first time resource: 1) a time resource operating in TDD, 2) a time resource operating in HD, 3) a time resource operating in Non-SBFD, 4) a TDD symbol, 5) an HD symbol, 6) a Non-SBFD symbol.

[0216] Hereinafter, at least one of the following resources may mean a second time resource: 1) a time resource operating as SBFD and / or SSFD, 2) an SBFD symbol and / or an SSFD symbol.

[0217] Meanwhile, in existing NR TDD carriers, the base station performs only downlink or uplink operations in a specific time resource. In this case, the base station always operates in downlink in the time resource where SSB is transmitted.

[0218] For terminals operating in existing TDD, the following is assumed for symbols in which SSB (SS / PBCH) is transmitted.

[0219] 1) SS / PBCH transmission symbols cannot be configured for uplink by TDD configuration (e.g., 'TDD-UL-DL-ConfigCommon' and / or 'TDD-UL-DL-ConfigDedicated').

[0220] 2) SS / PBCH transmission symbols cannot be set to uplink in SFI (slot format indication) by DCI format 2_0.

[0221] 3) When SS / PBCH is transmitted in a symbol set to flexible by TDD configuration (e.g., 'TDD-UL-DL-ConfigCommon' and / or 'TDD-UL-DL-ConfigDedicated'), if the uplink transmission of the terminal overlaps with the SS / PBCH symbol, the uplink transmission is not performed. In case of SRS, if it overlaps with the SS / PBCH symbol in the flexible symbol, SRS transmission is not performed in the overlapped symbol(s).

[0222] Meanwhile, in FDs such as SBFD and SSFD, both DL and UL resources can exist in the same time resource from the cell's perspective. Therefore, the base station can simultaneously perform downlink transmission and uplink reception. Therefore, even if SS / PBCH are transmitted in the time resource where the cell is performing FD operation, the base station can perform uplink reception while transmitting SS / PBCH.

[0223] Meanwhile, under the current standard, a terminal cannot perform uplink transmission on symbol resources where SS / PBCH is transmitted. In other words, a terminal cannot perform FD operations on the SS / PBCH transmission time resources of a base station.

[0224] When a specific time resource is configured as a time resource operating in SBFD (SBFD symbol), both DL and UL resources can exist in that time resource. In this case, if there is no UL signal to be received by the base station in that time resource, the base station can only perform DL transmission. In SBFD resources, DL transmission occurs only within the DL subband. Therefore, even if there is no UL signal transmitted in the UL subband, DL transmission can only be performed within the DL subband.

[0225] In this case, even if a specific time resource is determined to be an SBFD symbol, if there is no UL transmission to be received by the base station, it may be considered to perform DL transmission not only on the DL subband but also outside the DL subband to improve DL throughput. In other words, it may be considered to perform DL transmission over the entire bandwidth.

[0226] That is, a fallback to TDD operation that performs DL or UL operation over the entire band, rather than SBFD operation over DL / UL subbands, can be considered for resources judged as SBFD symbols.

[0227] In this disclosure, we assume and describe SBFD operation, in which a cell performs DL and UL simultaneously using different frequency resources (e.g., subbands) within the same time resource. However, the contents of this disclosure can also be applied to a cell performing SSFD operation.

[0228] In a wireless communication system, i) the base station may perform full duplex operation and the terminal may perform half duplex operation, ii) the base station may perform half duplex operation and the terminal may perform full duplex operation, or iii) both the base station and the terminal may support full duplex operation.

[0229] A terminal that knows that the base station can perform full duplex operation may be referred to as an FD-aware terminal hereinafter. A terminal that knows that the base station can perform SBFD operation may be referred to as an SBFD-aware terminal hereinafter. A terminal that knows that the base station can perform SSFD operation may be referred to as an SSFD-aware terminal hereinafter.

[0230] If a base station supports both half-duplex and full-duplex operation, it can inform the terminal of the resources (time or frequency, or both) on which it can (or expects to) perform half-duplex and full-duplex.

[0231] If the base station is a full-duplex base station capable of SSFD operation, UL reception may be possible simultaneously on some or all of the frequency resources available for DL ​​transmission at the base station. In other words, some frequency resources may support both DL transmission / reception and UL reception / transmission. In this case, information about frequency resources capable of SSFD can be communicated to the terminal. Furthermore, information about time resources capable of SSFD can be communicated to the terminal.

[0232] In the case of a full-duplex terminal, UL transmission may be possible simultaneously on some or all of the frequency resources available for DL ​​reception of the terminal. In the present disclosure, a terminal that performs half-duplex operation may be referred to as an HD terminal, and a terminal that can (or does) perform full-duplex operation may be referred to as an FD terminal.

[0233] When a base station performs full duplex operation such as SBFD or SSFD, it may perform SSFD and / or SBFD operation only for some time / frequency resources. When an SBFD-aware terminal and / or an SSFD-aware terminal knows the time / frequency resources on which a cell performs SSFD and / or SBFD operation, the terminal may perform the operation differently depending on whether the cell operates in half duplex (HD) or SBFD or SSFD. For example, the terminal may perform transmission and reception by differently determining the time / frequency resources on which it performs reception of a DL signal / channel and / or transmission of a UL signal / channel as HD resources, SBFD resources, or SSFD resources.

[0234] The base station may perform a half-duplex operation in which only one of DL transmission or UL reception is performed in the entire frequency resources constituting the cell in the time resources operating in HD, and may perform a full-duplex operation in which DL transmission is performed through the first frequency resource (i.e., DL subband resource) within the frequency resources constituting the cell and UL reception is simultaneously performed through the second frequency resource (i.e., UL subband resource) within the frequency resources constituting the cell in the time resources operating in SBFD and SSFD.

[0235] To this end, the base station determines / determines time resources corresponding to the first time resource (i.e., HD symbol) and the second time resource (i.e., FD symbol) and transmits configuration information regarding the first time resource (i.e., HD symbol) and / or the second time resource (i.e., FD symbol) to the terminal. The FD symbol may include both the SBFD symbol and the SSFD symbol. More specifically, the base station may determine / determine time resources corresponding to the HD symbol, the SBFD symbol, and / or the SSFD symbol, and transmit configuration information regarding the HD symbol, the SBFD symbol, and / or the SSFD symbol to the terminal.

[0236] At this time, the DL subband resources and / or UL subband resources may be configured differently in the time resources operating in SBFD and in the time resources operating in SSFD. In the time resources operating in SBFD, the DL subband resources and UL subband resources are configured so as not to overlap each other. On the other hand, in the time resources operating in SSFD, the DL subband resources and UL subband resources may be configured so as to overlap each other. The DL subband / UL subband resources may be configured with a portion of the frequency resources of the system bandwidth or with the entire frequency resources.

[0237] The terminal receives configuration information about an HD symbol, an SBFD symbol, and / or an SSFD symbol from the network, and determines the positions of the HD symbol, the SBFD symbol, and / or the SSFD symbol. At this time, the terminal performs DL reception (UL transmission) through the entire frequency resources for which the terminal is configured to operate DL reception (UL transmission) in the HD symbol. And, in the SBFD symbol and / or the SSFD symbol, the terminal performs DL reception (UL transmission) through DL subband (UL subband) resources that are the same as or limited (smaller) to the frequency resources for which the terminal performs DL reception (UL transmission) in the HD symbol. In this case, even if the terminal configures frequency resources that do not correspond to DL subband resources (UL subband resources) in the SBFD symbol and / or SSFD symbol resources for DL ​​reception (UL transmission), the terminal does not perform DL reception (UL transmission) in the frequency resources that do not correspond to DL subband resources (UL subband resources).

[0238] In the following, the term "network" may be interpreted as a base station, gNB, or CU / DU. Furthermore, the term "terminal (UE)" may be interpreted as a mobile terminal (MT) of an IAB node.

[0239] Below we describe the SBFD operations that can be applied.

[0240] In time division duplex (TDD), time-domain resources are divided into downlink and uplink. Allocating a limited time slot to the uplink in TDD reduces coverage, increases latency, and reduces capacity. To address these limitations of existing TDD operations, allowing simultaneous downlink and uplink operations within the existing TDD band—i.e., full duplex, or more specifically, subband full duplex—has been considered. The TDD standard allows for dynamic and flexible time allocation for downlink and uplink, and introduces cross-link interference (CLI) handling and remote interference management (RIM).

[0241] For SBFD operation within a TDD carrier, the base station can semi-statically indicate the time position of the SBFD subband to a UE in RRC_CONNECTED mode. For example, the base station can inform the UE of the time position of the SBFD subband in the system information block (SIB).

[0242] In RRC_CONNECTED mode, the base station can semi-statically inform the UE of the frequency domain location of the SBFD subband. For example, the base station can inform the UE of the frequency location of the SBFD subband in the system information block (SIB).

[0243] A base station can specify SBFD operation to support random access of SBFD symbols by a terminal in RRC CONNECTED mode.

[0244] The base station may review the SBFD behavior for the terminal for random access in RRC_IDLE / INACTIVE mode and, if justified, specify such behavior.

[0245] For SBFD-aware terminals, a base station can specify terminal transmission, reception, and measurement operations and procedures in SBFD symbols and / or non-SBFD symbols.

[0246] For example, transmission and reception operations in SBFD subbands composed of downlink symbols and / or flexible symbols can be indicated by 'TDD-UL-DL-ConfigCommon'. In this case, UL transmission can be performed only within the UL subband, and DL reception can be performed only within the DL subband. When flexible symbols are used, legacy uplink symbols are not (or are expected not to be) converted into downlink / SBFD symbols.

[0247] In frequency-domain resource allocation of the SBFD symbol, frequency-domain resources for PDSCH / CSI-RS may be allocated across two DL subbands in the SBFD symbol. Additionally, the base station may provide additional instructions for handling unaligned boundaries between the SBFD subband and the RBG, CSI reporting subband, CSI-RS resources, and PRG.

[0248] Within a single slot, transmission and reception may be performed using either all SBFD symbols or all non-SBFD symbols, but transmission and reception of physical signals / channels may be performed through slots that include different types of symbols. For example, an operation may be directed / performed in which transmission and reception is performed using only SBFD symbols in a first slot, and transmission and reception is performed using only non-SBFD symbols in a second slot, but signal / channel transmission and reception is performed across the first and second slots.

[0249] Frequency-domain resource allocation for transmission or reception of SBFD and non-SBFD symbols with different available frequency resources in different slots may be supported. CSI reporting in which related CSI-RS instances occur in both SBFD and non-SBFD symbols in different slots may also be supported.

[0250] Settings for SRS, PUCCH and PUSCH of SBFD symbols and non-SBFD symbols, such as resources, frequency hopping parameters, UL power control parameters and / or beam / space relationships, may be provided to the terminal by the base station.

[0251] Additionally, collision handling between DL reception in the DL subband and UL transmission in the UL subband in the SBFD symbol can also be instructed to the terminal by the base station.

[0252] In the following, it is assumed that the time and frequency locations of subbands for SBFD operation are known to SBFD-aware terminals. In a cell operating in SBFD, non-SBFD-aware terminals (i.e., legacy terminals) and SBFD-aware terminals can coexist.

[0253] For convenience, it may be assumed that there is one UL subband for SBFD operation in an SBFD symbol within a TDD carrier, but this is not a limitation.

[0254] Below, based on the aforementioned discussion, a method for determining the size of a resource block group (RBG) applied to an SBFD symbol during intra-carrier full duplex operation is described.

[0255] The terminal may be located in a symbol resource that is a SBFD symbol in which the cell operates as SBFD, a symbol set to DL by TDD-UL-DL-ConfigCommon, or a symbol set / determined as flexible by TDD-UL-DL-ConfigCommon.

[0256] <TDD-UL-DL-ConfigCommon에서 하향링크로 설정된 심볼들에서의 SBFD 동작(SBFD operation in symbols configured as DL in TDD-UL-DL-ConfigCommon)>

[0257] SBFD symbols may be set, for example, by a system information block (more specifically, a system information block 1 (SIB1) that contains information relevant to evaluating whether a terminal is allowed cell access and defines scheduling of other system information).

[0258] Additionally, symbols within a slot can be configured as downlink, uplink, or flexible by a TDD configuration (e.g., TDD-UL-DL-ConfigCommon) that sets cell-specific downlink / uplink resources.

[0259] However, there may also be cases where a symbol set as downlink by TDD-UL-DL-ConfigCommon is set as an SBFD symbol by the aforementioned SIB1. Such an SBFD symbol may be referred to as an SBFD symbol set as downlink by TDD-UL-DL-ConfigCommon hereinafter. Similarly, a symbol set as flexibly by TDD-UL-DL-ConfigCommon may be set as an SBFD symbol by the aforementioned SIB1, and such an SBFD symbol may be referred to as an SBFD symbol set as flexibly by TDD-UL-DL-ConfigCommon hereinafter.

[0260] In the case of an SBFD-aware UE in which a UL subband is semi-statically configured in an SBFD symbol configured as downlink in TDD-UL-DL-ConfigCommon, UL transmission within the UL subband is allowed in the SBFD symbol. UL transmission outside the UL subband is not allowed in the SBFD symbol. The frequency location of the DL subband in the SBFD symbol is known to the SBFD-aware UE. The frequency location of the DL subband can be explicitly indicated or implicitly derived. DL reception within the DL subband is allowed in the SBFD symbol. In the SBFD symbol, the UL transmission is performed within an active UL BWP, and the DL reception is performed within an active DL BWP.

[0261] Additionally, it can be checked whether DL reception outside of the semi-statically configured DL subband is allowed in the symbol configured for downlink by TDD-UL-DL-ConfigCommon for the SBFD-aware terminal according to at least one of the following options.

[0262] Option 1 (Semi-static SBFD): DL reception outside the semi-statically configured DL subbands is not allowed.

[0263] Option 2 (Dynamic SBFD): DL reception outside the semi-statically configured DL subbands is allowed.

[0264] <TDD-UL-DL-ConfigCommon에서 플렉서블로 설정된 심볼의 SBFD 동작(SBFD operation in symbols configured as flexible in TDD-UL-DL-ConfigCommon)>

[0265] For SBFD operation in a symbol set as flexible by TDD-UL-DL-ConfigCommon, an SBFD-aware terminal can operate by at least one of the following:

[0266] Alt 1: UL transmission within the UL subband is permitted in the symbol. UL transmission outside the UL subband is not permitted in the symbol. The frequency location of the DL subband is known to the SBFD-aware terminal. DL reception within the DL subband is permitted in the symbol.

[0267] Alt 2: UL transmission within the UL subband is allowed in the symbol. In the symbol, resource blocks outside the UL subband can be used as UL or DL ​​from the perspective of the base station (excluding the guard band), and the transmission direction of the resource blocks is the same. The frequency location of the DL subband is known to the SBFD-aware terminal. DL reception within the DL subband is allowed in the symbol.

[0268] In both options, UL transmission in the above symbol is within the active UL BWP, and DL reception is within the active DL BWP. For any resource blocks outside the UL subband, the terminal cannot use separate RBs (resource blocks) for DL ​​and UL simultaneously.

[0269] Additionally, whether DL reception outside of the semi-statically configured DL subband and UL transmission outside of the semi-statically configured UL subband are allowed in symbols flexibly set by TDD-UL-DL-ConfigCommon for SBFD-aware terminals may depend on one of the following options:

[0270] Option 1 (Semi-static): DL reception outside of the semi-statically configured DL subbands is not allowed, and UL transmission outside of the semi-statically configured UL subbands is not allowed.

[0271] Option 2 (Dynamic SBFD): DL reception outside of the semi-statically configured DL subbands is permitted. UL transmission outside of the semi-statically configured UL subbands is not permitted.

[0272] Option 3 (Dynamic SBFD): DL reception outside of the semi-statically configured DL subbands is allowed. UL transmission outside of the semi-statically configured UL subbands is allowed.

[0273] The terminal can perform DL reception using frequency resources within the DL subband in the SBFD symbol. The terminal can perform UL transmission using frequency resources within the UL subband in the SBFD symbol.

[0274] Therefore, if the SBFD symbol is located in a symbol set to DL by TDD-UL-DL-ConfigCommon, the terminal must be able to perform UL transmission using frequency resources within the UL subband even in the SBFD symbol.

[0275] However, according to the current standard, the terminal does not perform transmission of PUSCH, PUCCH, PRACH, or SRS in the symbol set to DL by TDD-UL-DL-ConfigCommo.

[0276] For example, for a set of symbols of a slot indicated to a terminal as downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, the standard stipulates that if PUSCH, PUCCH, PRACH or SRS overlaps even partially with the set of symbols of the slot, the terminal does not transmit PUSCH, PUCCH, PRACH or SRS. Therefore, an enhancement is required for the terminal to perform UL transmission when the SBFD symbol is located in a symbol configured / indicated as DL by TDD-UL-DL-ConfigurationCommon. tdd-UL-DL-ConfigurationCommon is an example of a cell-specific TDD configuration, and tdd-UL-DL-ConfigurationDedicated is an example of a terminal-specific TDD configuration.

[0277] Based on this discussion, the present disclosure describes a method for determining a time resource for a terminal to transmit a UL signal / channel by considering an SBFD symbol during intra-carrier full duplex operation.

[0278] The present disclosure assumes SBFD operation, where a cell performs DL and UL operations simultaneously using different frequency resources (e.g., subbands) within the same time resource. However, the contents of the present disclosure can also be applied to a cell performing SS-FD operation.

[0279] The base station may perform full duplex operation and the terminal may perform half duplex operation, or the base station may perform half duplex operation and the terminal may perform full duplex operation. Alternatively, both the base station and the terminal may support full duplex operation.

[0280] A UE that knows that the base station can perform full duplex operation may be referred to as an FD-aware UE. A UE that knows that the base station can perform subband non-overlapping full duplex (e.g., the aforementioned SBFD) operation and that this information is known may be referred to as an 'SBFD-aware UE.'

[0281] A base station can perform spectrum sharing (or subband overlapping) full duplex (e.g., SSFD as described above) operation, and a terminal that is aware of this information can be referred to as an SSFD-aware UE.

[0282] If a base station supports both half-duplex and full-duplex operation, it can inform the terminal of the resources (time or frequency, or both) on which it can (or is expected to) perform half-duplex and full-duplex.

[0283] If a base station is capable of SSFD operation, and in the case of a full-duplex base station, UL reception can be enabled simultaneously on some or all of the frequency resources available for DL ​​transmission at the base station. In other words, some frequency resources may allow for UL reception / transmission as well as DL transmission / reception. In this case, in the case of SSFD, information about the frequency resources available for SSFD can be communicated. In addition, information about the time resources available for SSFD can be communicated.

[0284] In the case of a full-duplex terminal, UL transmission can be enabled simultaneously on some or all of the frequency resources available for DL ​​reception of the terminal. In the present disclosure, a terminal that performs half-duplex operation is referred to as an HD terminal, and a terminal that can (or does) perform full-duplex operation is referred to as an FD terminal.

[0285] When a base station performs full duplex operation such as SBFD or SSFD, it may perform SSFD and / or SBFD operation only for some time / frequency resources. For SBFD-aware terminals and / or SSFD-aware UEs, if the cell knows the time / frequency resources on which it performs SSFD and / or SBFD operation, the cell may perform the UE operation differently depending on whether the cell operates in half duplex (HD), operates in SBFD, or operates in SSFD.

[0286] For example, the terminal may perform transmission and reception by differently determining the time / frequency resources for receiving DL signals / channels and / or transmitting UL signals / channels according to HD resources, SBFD resources, and SSFD resources.

[0287] The base station may perform a half-duplex operation in which only one of DL transmission or UL reception is performed in the entire frequency resources constituting the cell in the time resources operating in HD, and may perform a full-duplex operation in which DL transmission is performed through a first frequency resource (e.g., a DL subband resource) within the frequency resources constituting the cell and UL reception is simultaneously performed through a second frequency resource (e.g., a UL subband resource) within the frequency resources constituting the cell in the time resources operating in SBFD and SSFD.

[0288] To this end, the base station determines / determines time resources corresponding to the first time resource (e.g., HD symbol) and the second time resource (e.g., FD symbol) and transmits configuration information regarding the first time resource (e.g., HD symbol) and / or the second time resource (e.g., FD symbol) to the terminal. The FD symbol may include both the SBFD symbol and the SSFD symbol. More specifically, the base station may determine / determine time resources corresponding to the HD symbol, the SBFD symbol, and / or the SSFD symbol, and transmit configuration information regarding the HD symbol, the SBFD symbol, and / or the SSFD symbol to the terminal.

[0289] At this time, the DL subband resources and / or UL subband resources may be configured differently in the time resources operating in SBFD and in the time resources operating in SSFD. In the time resources operating in SBFD, the DL subband resources and UL subband resources are configured so as not to overlap each other. In the time resources operating in SSFD, the DL subband resources and UL subband resources may be configured so as to overlap each other. The DL subband / UL subband resources may be configured with all frequency resources as well as some frequency resources of the system band.

[0290] The terminal receives configuration information about an HD symbol, an SBFD symbol, and / or an SSFD symbol from the network, and determines the positions of the HD symbol, the SBFD symbol, and / or the SSFD symbol. At this time, the terminal performs DL reception (UL transmission) through the entire frequency resources for which the terminal is configured to operate DL reception (UL transmission) in the HD symbol, and performs DL reception (UL transmission) through DL subband (UL subband) resources that are the same as or limited to the frequency resources for which the terminal performs DL reception (UL transmission) in the HD symbol in the SBFD symbol and / or SSFD symbol. In this case, even if the terminal is configured to perform DL reception (UL transmission) in a frequency resource that does not correspond to a DL subband resource (UL subband resource) in the SBFD symbol and / or SSFD symbol resource, the terminal does not perform DL reception (UL transmission) in a frequency resource that does not correspond to a DL subband resource (UL subband resource).

[0291] In an SBFD symbol, unlike in a non-SBFD symbol, a terminal can perform DL reception using frequency resources within a DL subband and perform UL transmission using frequency resources within a UL subband.

[0292] Therefore, if the SBFD symbol is located in a symbol set to DL by TDD-UL-DL-ConfigCommon, the terminal must be able to perform UL transmission using frequency resources within the UL subband even in the SBFD symbol.

[0293] To this end, improvements are needed to perform UL transmission when the terminal is located in a symbol where the SBFD symbol is set to DL by TDD-UL-DL-ConfigCommon.

[0294] Below, a method for determining a time resource for a terminal to transmit a UL signal / channel by considering the SBFD symbol during full duplex operation within a carrier is described.

[0295] Basically, the terminal can flexibly schedule DL signals / channels and UL signals / channels in SBFD symbols, and can consider performing scheduled DL Rx or UL Tx operations without any separate restrictions. Meanwhile, according to the current standard, the terminal does not perform reception of DL signals / channels in symbols set to UL. Therefore, for SBFD-aware terminals, unlike existing terminals, an operation of performing UL transmission in symbols set to DL by TDD-UL-DL-ConfigCommon must be supported.

[0296] To this end, if a symbol set as DL by TDD-UL-DL-ConfigCommon is set / judged as an SBFD symbol, 1) an SBFD-aware terminal can process / handle the symbol in the same way as a symbol set as flexibly by TDD-UL-DL-ConfigCommon. That is, an SBFD-aware terminal can operate in the same way as in a symbol set as flexibly by TDD-UL-DL-ConfigCommon. 2) An SBFD-aware terminal can convert the symbol in the same way as in a symbol set as flexibly by TDD-UL-DL-ConfigCommon.

[0297] Alternatively, if a symbol set as DL by TDD-UL-DL-ConfigCommon is set / determined as an SBFD symbol, the terminal determines the symbol as a DL symbol, but must be able to perform UL transmission on the symbol. In this case, the contents of sections (1)-(4) proposed in the present disclosure may be applied so that the terminal can perform UL transmission on a symbol determined to be a DL symbol.

[0298] Additionally, for existing terminals, whether the terminal performs DL reception or UL transmission in a specific symbol is determined through additional signaling, such as TDD-UL-DL-ConfigDedicated and slot format indication information. Meanwhile, for SBFD-aware terminals, it is necessary to clarify how to interpret TDD-UL-DL-ConfigDedicated and slot format indication information in SBFD symbols.

[0299] Method 1. As one method, an SBFD-aware terminal may not be instructed with TDD-UL-DL-ConfigDedicated and / or slot format indication information that previously restricted the DL-Rx / UL-Tx operation of the terminal. Even if instructed with such information, an SBFD-aware terminal may ignore the information.

[0300] That is, if the terminal determines a specific symbol as an SBFD symbol, it can perform DL Rx or UL Tx operation on the symbol regardless of TDD-UL-DL-ConfigDedicated and / or slot format indication information.

[0301] Method 2. If an SBFD-aware terminal is instructed to indicate TDD-UL-DL-ConfigDedicated and / or slot format, it may not apply the information to SBFD symbols. This information may only be applied to non-SBFD symbols.

[0302] That is, if the terminal determines a specific symbol as an SBFD symbol, it can perform DL Rx or UL Tx operation on the symbol regardless of TDD-UL-DL-ConfigDedicated and / or slot format indication information.

[0303] FIG. 18 illustrates terminal operation according to one embodiment of the present disclosure.

[0304] Referring to FIG. 18, a terminal receives a system information block (SIB), wherein the SIB includes subband full duplex (SBFD) time information that sets the time position of a cell-specific subband full duplex (SBFD) subband (S181). The SIB can be provided to the terminal from the network via the BCCH. The terminal is an SBFD-aware UE.

[0305] For example, the SIB may be SIB1, which includes information relevant to determining whether a terminal is permitted to access a cell and defines the scheduling of other system information. SIB1 may include resource allocation information and barring information common to terminals. SBFD time information, which sets the time position of cell-specific SBFD subband(s), may be added to SIB1 and provided to the terminal.

[0306] For example, SBFD timing information can explicitly or implicitly indicate the location of a symbol (which may be referred to as an SBFD symbol) in which an SBFD subband exists. Based on the SBFD timing information, the terminal can identify SBFD symbols and non-SBFD symbols. For example, the terminal can identify symbols that are not SBFD symbols as non-SBFD symbols.

[0307] The terminal receives downlink control information (DCI) including a slot format indicator (SFI) indicating a slot format including downlink symbols, uplink symbols, and flexible symbols (S182). For example, the DCI may be DCI format 2_0. DCI format 2_0 may be a DCI format used to indicate a slot format, a COT (Channel Occupancy Time) interval, a set of available resource blocks, and search space set group switching.

[0308] The terminal applies the SFI only to the non-SBFD symbols among the SBFD symbols and non-SBFD symbols based on the SBFD time information (S183). The fact that the terminal applies the SFI only to the non-SBFD symbols among the SBFD symbols and non-SBFD symbols based on the SBFD time information can be expressed in other ways. For example, the terminal (SBFD-aware terminal) ignores the SFI in SBFD symbols, or the terminal (SBFD-aware terminal) does not apply the SFI in SBFD symbols.

[0309] Although not shown in FIG. 18, the terminal may further receive cell-specific uplink / downlink TDD (time division duplex) configuration (e.g., TDD-UL-DL-ConfigCommon).

[0310] In the above cell-specific uplink / downlink TDD configuration, the terminal is allowed to perform uplink transmission within the uplink subband within the SBFD symbol set as downlink. The terminal is not allowed to perform uplink transmission outside the uplink subband. The terminal is allowed to perform downlink reception within the downlink subband within the SBFD symbol.

[0311] In the above cell-specific uplink / downlink TDD configuration, the terminal is allowed to perform uplink transmission within the uplink subband within the SBFD symbol that is set to flexible. The terminal is not allowed to perform uplink transmission outside the uplink subband. The terminal is allowed to perform downlink reception within the downlink subband within the SBFD symbol.

[0312] Among the SBFD symbols and the non-SBFD symbols, for specific non-SBFD symbols set as downlink by the cell-specific uplink / downlink TDD setting, if a physical uplink shared channel (PUSCH), a physical uplink control channel (PUCCH), a physical random access channel (PRACH) or a sounding refernece signal (SRS) overlaps even partially with the specific non-SBFD symbols, the terminal skips transmission of the PUSCH, the PUCCH, the PRACH or the SRS (i.e., does not transmit the PUSCH, the PUCCH, the PRACH or the SRS).

[0313] In an embodiment, when PUSCH repetitive transmission is performed based on available slots, if at least one symbol among the symbols allocated to PUSCH transmission in a specific slot is set to downlink by the cell-specific uplink / downlink TDD configuration and overlaps with the non-SBFD symbols, the specific slot is excluded from the count of the available slots.

[0314] In some embodiments, the terminal may further receive terminal-specific uplink / downlink TDD configuration (e.g., TDD-UL-DL-ConfigDedicated). In this case, if at least one symbol among the symbols allocated for PUSCH transmission in a specific slot is configured as downlink by the terminal-specific uplink / downlink TDD configuration and overlaps with the non-SBFD symbols, the specific slot is excluded from the count of available slots for the PUSCH transmission.

[0315] As mentioned above, the current standard does not clearly define how the network will inform the UE of FD resources, such as SBFD resources. Furthermore, the slot format indicator (SFI), which identifies symbols within a slot as downlink symbols, uplink symbols, or flexible symbols, is provided to the UE through dynamic signaling, such as downlink control information (DCI) transmitted over the physical downlink control channel (PDCCH). It is also unclear how this SFI would be applied in a wireless communication system using SBFD. Furthermore, when repeatedly transmitting uplink data channels, a transmission method can be defined based on available slots. However, the current standard determines whether a specific slot is available and the number of available slots without considering SBFD resources. Therefore, it is difficult to directly apply the current standard to a communication system using SBFD.

[0316] According to the method of FIG. 18, in a wireless communication system where SBFD is used, SBFD resources (e.g., SBFD symbols and / or SBFD frequency resources) can be announced through a SIB (more specifically, SIB1). In addition, for SBFD time resources (e.g., SBFD symbols) configured through the SIB, it is made clear that a dynamically configured slot format indicator (SFI), e.g., an SFI provided through a specific DCI format, is not applied and is applied only to non-SBFD symbols (as described above, this can be expressed as a terminal (an SBFD-aware terminal) ignoring the SFI in SBFD symbols or a terminal (an SBFD-aware terminal) not applying the SFI in SBFD symbols). Therefore, no ambiguity arises between a network and a terminal as to whether or not an SFI is applied.

[0317] In addition, in the determination / counting of available slots in conventional PUSCH repetitive transmission, the available slots were determined / counted without considering the configuration of SBFD time resources. However, in the method of the present disclosure, the determination / counting of available slots is performed by considering the configuration of SBFD time resources. For example, if a symbol indicated as downlink by cell-specific TDD configuration in a specific slot is indicated as an SBFD symbol by the SBFD time information of the SIB, even if the SBFD symbol and the PUSCH transmission symbol overlap, the specific slot is not excluded from the available slots for PUSCH transmission. Therefore, more efficient PUSCH repetitive transmission considering the SBFD configuration is possible.

[0318] FIG. 19 illustrates a signaling and operation method between a base station and a terminal according to one embodiment of the present disclosure.

[0319] Referring to Figure 19, the base station provides a system information block to the terminal (S191). The system information block includes SBFD time information. The system information block may be, for example, SIB1. The terminal is an SBFD-aware terminal.

[0320] The base station transmits DCI including a slot format indicator (SFI) to the terminal (S192).

[0321] The terminal applies the SFI only to the non-SBFD symbols among the SBFD symbols and non-SBFD symbols based on the SBFD time information (S193). This step may be expressed as the terminal (SBFD-aware terminal) ignoring the SFI in the SBFD symbols among the SBFD symbols and non-SBFD symbols based on the SBFD time information, or the terminal (SBFD-aware terminal) not applying the SFI in the SBFD symbols among the SBFD symbols and non-SBFD symbols based on the SBFD time information.

[0322] The base station and the terminal communicate using SBFD symbols and non-SBFD symbols to which SFI is applied (S194).

[0323] FIG. 20 illustrates an operation method of a base station according to one embodiment of the present disclosure.

[0324] Referring to FIG. 20, a base station transmits a system information block (SIB), wherein the SIB includes subband full duplex (SBFD) time information that sets the time position of a cell-specific SBFD subband (S201). The SIB may be transmitted via the BCCH. For example, the SIB may be SIB1. A terminal receiving the SIB1 may be an SBFD-aware terminal.

[0325] The base station transmits downlink control information (DCI) including a slot format indicator (SFI) that informs the terminal of a slot format including downlink symbols, uplink symbols, and flexible symbols (S202). For example, the DCI may be DCI format 2_0. The terminal may be an SBFD-aware terminal.

[0326] The base station communicates with the SBFD-aware terminal based on the application of the SFI only to the non-SBFD symbols among the SBFD symbols and non-SBFD symbols based on the SBFD time information (S203).

[0327] Method 3. Additional signaling, such as TDD-UL-DL-ConfigDedicated and / or slot format indication, can be used to determine whether the SBFD symbol is used as a DL symbol or an UL symbol. Even if the terminal configures / determines the SBFD symbol as a DL symbol through signaling of TDD-UL-DL-ConfigDedicated and / or slot format indication, the terminal can perform DL Rx or UL Tx operations on the symbol.

[0328] That is, if the terminal determines a specific symbol as an SBFD symbol, it can perform DL Rx or UL Tx operation on the symbol regardless of TDD-UL-DL-ConfigDedicated and / or slot format indication information.

[0329] Method 4. It may be considered to restrict the Tx / Rx direction of the UE in the SBFD symbol through additional signaling such as TDD-UL-DL-ConfigDedicated and / or slot format indication. For example, if the UE configures a specific SBFD symbol as a DL symbol by TDD-UL-DL-ConfigDedicated or slot format indication, the UE may perform only DL reception within the DL subband in the symbol and not perform UL transmission operation.

[0330] In other words, even if the terminal determines a specific symbol to be an SBFD symbol, it can perform only a DL Rx operation or only a UL Tx operation according to the TDD-UL-DL-ConfigDedicated and / or slot format indication information applied to the symbol.

[0331] (1) Allow UL transmission in DL symbols

[0332] The standard describes the UL operation of a terminal in a symbol indicated as downlink by tdd-UL-DL-ConfigurationCommon. For example, the standard stipulates that, for a set of symbols of a slot indicated as downlink to the terminal by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, if a PUSCH, PUCCH, PRACH or SRS overlaps even partially with the set of symbols of the slot, the terminal does not transmit a PUSCH, PUCCH, PRACH or SRS.

[0333] According to these standards, if a transmission symbol of PUSCH, PUCCH, PRACH, or SRS in a specific slot overlaps with a DL symbol indicated by TDD-UL-DL-ConfigCommon, the UE shall not transmit the corresponding PUSCH, PUCCH, PRACH, or SRS.

[0334] However, if the DL symbol indicated by TDD-UL-DL-ConfigCommon is set to an SBFD symbol, it is necessary that the symbol be capable of transmitting the UL signal / channel of the terminal.

[0335] To this end, in the case of an SBFD-aware terminal, it can be determined that the terminal does not perform UL transmission only when the symbol indicated as DL by TDD-UL-DL-ConfigCommon is a non-SBFD symbol.

[0336] If a transmission symbol of PUSCH, PUCCH, PRACH, or SRS in a specific slot overlaps with a symbol that is indicated as DL by TDD-UL-DL-ConfigCommon and is not indicated as an SBFD symbol, the terminal does not transmit the corresponding PUSCH, PUCCH, PRACH, or SRS.

[0337] In other words, in the case of a symbol indicated as DL by TDD-UL-DL-ConfigCommon but indicated as an SBFD symbol, even if it overlaps with a transmission symbol of PUSCH, PUCCH, PRACH, or SRS, the terminal does not determine that it is not performing transmission of PUSCH, PUCCH, PRACH, or SRS.

[0338] Meanwhile, in the case of a symbol indicated as DL by TDD-UL-DL-ConfigDedicated, even if the symbol is indicated as an SBFD symbol, it may be considered that the terminal can perform only DL reception through the DL subband in the symbol as before. Alternatively, even if the symbol is indicated as DL by TDD-UL-DL-ConfigDedicated, even if the symbol is indicated as an SBFD symbol, it may be considered that the terminal can perform both DL reception using frequency resources within the DL subband and UL transmission using frequency resources within the UL subband in the symbol.

[0339] For this purpose, in the case of an SBFD-aware terminal, it is possible to determine whether the terminal's UL signal / channel can be transmitted in a symbol indicated as DL by TDD-UL-DL-ConfigDedicated.

[0340] Alt 1. If a terminal can only perform DL reception in an SBFD symbol indicated as DL by TDD-UL-DL-ConfigDedicated, and if a transmission symbol of PUSCH, PUCCH, PRACH, or SRS in a specific slot overlaps with a symbol indicated as DL by TDD-UL-DL-ConfigDedicated, the terminal does not perform transmission of the PUSCH, PUCCH, PRACH, or SRS. In other words, if a symbol indicated as DL by TDD-UL-DL-ConfigDedicated (even if the symbol is indicated as an SBFD symbol) overlaps with a transmission symbol of PUSCH, PUCCH, PRACH, or SRS, the terminal does not determine that it does not perform transmission of the PUSCH, PUCCH, PRACH, or SRS.

[0341] Alt 2. When a terminal can perform DL reception or UL transmission in an SBFD symbol indicated as DL by TDD-UL-DL-ConfigDedicated, if a transmission symbol of PUSCH, PUCCH, PRACH, or SRS in a specific slot overlaps with a symbol indicated as DL by TDD-UL-DL-ConfigDedicated and not indicated as an SBFD symbol, the terminal does not perform transmission of the PUSCH, PUCCH, PRACH, or SRS. In other words, in the case of a symbol indicated as DL by TDD-UL-DL-ConfigDedicated but indicated as an SBFD symbol, even if it overlaps with a transmission symbol of PUSCH, PUCCH, PRACH, or SRS, the terminal does not determine that it does not perform transmission of the PUSCH, PUCCH, PRACH, or SRS.

[0342] (2) Count the available slots for PUSCH repetition type A transmission even when DL symbols and PUSCH symbols overlap.

[0343] The standard describes the operation of a terminal for determining slot resources that constitute a PUSCH transmission using PUSCH repetition type A. In the present disclosure, PUSCH transmission using PUSCH repetition type A includes TB processing over multi-slots (TBoMS) transmission.

[0344] For unpaired spectrum: If AvailableSlotCounting is enabled and K > 1, the UE may determine N·K slots for PUSCH transmission of PUSCH repetition type A scheduled by DCI format 0_1 ​​or 0_2 based on the values ​​of tdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationDedicated and ssb-PositionsInBurst and the time domain resource assignment (TDRA) information field of DCI format 0_1 ​​or 0_2.

[0345] If at least one symbol among the symbols indicated by the index row of the resource allocation table used in the slot overlaps with a DL symbol indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated (if provided) or a symbol of an SS / PBCH block with an index provided by ssb-PositionsInBurst, the slot is not counted in the number of N·K slots for PUSCH transmission of PUSCH repetition type A scheduled by DCI format 0_1 ​​or 0_2.

[0346] Otherwise, the terminal determines N·K consecutive slots for PUSCH transmission of PUSCH repetition type A scheduled by DCI format 0_1 ​​or 0_2 according to the TDRA information field value of DCI format 0_1 ​​or 0_2.

[0347] The terminal determines N·K slots for PUSCH transmission of TB processing over multiple slots (TBoMS) scheduled by DCI format 0_1 ​​or 0_2 based on the values ​​of tdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationDedicated, and ssb-PositionsInBurst and the TDRA information field of DCI format 0_1 ​​or 0_2.

[0348] If at least one symbol among the symbols indicated by the index row of the resource allocation table used in the slot overlaps with a DL symbol indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated or a symbol of an SS / PBCH block with an index provided by ssb-PositionsInBurst, the slot is not counted in the number of N·K slots for TBoMS PUSCH transmission.

[0349] The terminal determines N·K slots for PUSCH transmission of PUSCH repetition type A scheduled by the random access response (RAR) UL grant based on the values ​​of tdd-UL-DL-ConfigurationCommon and ssb-PositionsInBurst and the TDRA information field of the RAR UL grant.

[0350] If at least one symbol among the symbols indicated by the index row of the resource allocation table used in the slot overlaps with a DL symbol indicated by tdd-UL-DL-ConfigurationCommon or a symbol of an SS / PBCH block with an index provided in ssb-PositionsInBurst, the slot is not counted in the number of N·K slots for PUSCH transmission of PUSCH repetition type A scheduled by the RAR UL grant.

[0351] The terminal determines N·K slots for PUSCH transmission of PUSCH repetition type A scheduled by DCI format 0_0 using CRC scrambled by TC-RNTI, based on the values ​​of tdd-UL-DL-ConfigurationCommon and ssb-PositionsInBurst and the TDRA information field of the DCI scheduling the PUSCH.

[0352] If at least one symbol among the symbols indicated by the index row of the resource allocation table used in the slot overlaps with a DL symbol indicated by tdd-UL-DL-ConfigurationCommon (if provided) or a symbol of an SS / PBCH block with an index provided by ssb-PositionsInBurst, it is not included in the number of N·K slots for a PUSCH transmission of PUSCH repetition type A scheduled by DCI format 0_0 scrambled by TC-RNTI.

[0353] According to the above, when PUSCH transmission using PUSCH repetition type A is performed based on available slots (i.e., when AvailableSlotCounting is enabled), when the terminal counts N*K available slots for transmitting PUSCH, if at least one symbol among the symbols allocated to PUSCH transmission in a specific slot is included in the next symbol, the slot is not counted as an available slot.

[0354] 1) DL symbol indicated by TDD-UL-DL-ConfigCommon

[0355] 2) DL symbol indicated by TDD-UL-DL-ConfigDedicated

[0356] 3) Symbol of SS / PBCH block with index provided by ssb-PositionInBurst.

[0357] However, if the DL symbol indicated by TDD-UL-DL-ConfigCommon is set to an SBFD symbol, the slot must not be excluded from the available slots for PUSCH transmission even if the symbol allocated for PUSCH transmission in a specific slot overlaps with that symbol.

[0358] Considering this, in the case of an SBFD-aware terminal, if PUSCH transmission using PUSCH repetition type A is performed based on available slots, the following operations can be performed.

[0359] If at least one symbol among the symbols allocated for PUSCH transmission in a specific slot is a DL symbol indicated by TDD-UL-DL-ConfigCommon and overlaps with a symbol that is not set as an SBFD symbol, the slot is not counted as an available slot.

[0360] In addition, if the terminal can perform DL reception or UL transmission in an SBFD symbol indicated as DL by TDD-UL-DL-ConfigDedicated, i.e., if the terminal can perform UL transmission in the symbol even if the symbol is indicated as DL by TDD-UL-DL-ConfigDedicated in the case of an SBFD symbol, the symbol allocated for PUSCH transmission must not be excluded from the available slots for PUSCH transmission even if it overlaps with the symbol.

[0361] Considering this, in the case of an SBFD-aware terminal, if PUSCH transmission using PUSCH repetition type A is performed based on available slots, it can operate as follows.

[0362] Alt 1. If the terminal can only perform DL reception in an SBFD symbol indicated as DL by TDD-UL-DL-ConfigDedicated, 1) if at least one symbol among the symbols allocated for PUSCH transmission in a specific slot overlaps with a DL symbol indicated by TDD-UL-DL-ConfigDedicated, the slot is not counted as an available slot. In other words, if the slot is indicated as DL by TDD-UL-DL-ConfigDedicated (even if the symbol is indicated as an SBFD symbol), even if at least one symbol among the symbols allocated for PUSCH transmission in a specific slot overlaps with the symbol, the terminal does not determine that the slot is excluded from the available slots.

[0363] Alt 2. When a terminal can perform DL reception or UL transmission in an SBFD symbol indicated as DL by TDD-UL-DL-ConfigDedicated, if at least one symbol among the symbols allocated for PUSCH transmission in a specific slot is a DL symbol indicated by TDD-UL-DL-ConfigDedicated and overlaps with a symbol that is not set as an SBFD symbol, the terminal does not count the slot as an available slot. In other words, in the case of a symbol indicated as DL by TDD-UL-DL-ConfigDedicated but is indicated as an SBFD symbol, even if at least one symbol among the symbols allocated for PUSCH transmission in a specific slot overlaps with the symbol, the terminal does not determine that the slot is excluded from the available slots.

[0364] (3) Include DL symbols in the symbols that constitute the actual repetition of PUSCH repetition type B transmission.

[0365] The standard describes the operation of a terminal to determine an invalid symbol to configure actual repetitions for PUSCH transmission using PUSCH repetition type B as follows.

[0366] For PUSCH repetition type B, the terminal can determine an invalid symbol for PUSCH repetition type B transmission as follows.

[0367] Symbols indicated for downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated are considered invalid symbols for PUSCH repetition type B transmission.

[0368] For operation in unpaired spectrum, symbols indicated by ssb-PositionsInBurst of SIB1 or ssb-PositionsInBurst of ServingCellConfigCommon for reception of SS / PBCH blocks are considered invalid symbols for PUSCH repetition type B transmission.

[0369] When operating in unpaired spectrum, the symbols indicated by pdcch-ConfigSIB1 in the MIB for the core set of the Type0-PDCCH CSS set are considered invalid symbols for PUSCH repeat Type B transmissions.

[0370] According to the above, in case of PUSCH transmission using PUSCH repetition type B, the following symbols are included in the invalid symbols excluded from the actual repetition configuration.

[0371] 1) DL symbol indicated by TDD-UL-DL-ConfigCommon

[0372] 2) DL symbol indicated by TDD-UL-DL-ConfigDedicated

[0373] 3) Symbol of SS / PBCH block with index provided by ssb-PositionInBurst of SIB1 or ssb-PositionsInBurst of ServingCellConfigCommon.

[0374] 4) Symbol(s) indicated by pdcch-ConfigSIB1 in MIB for CORESET for Type0-PDCCH CSS set.

[0375] If a DL symbol indicated by TDD-UL-DL-ConfigCommon is set to an SBFD symbol, the symbol must be included in the symbols that constitute the actual repetition. Therefore, for SBFD-aware terminals, the following actions are proposed to determine invalid symbols.

[0376] If the DL symbol indicated by TDD-UL-DL-ConfigCommon is set to an SBFD symbol, the symbol is determined not to be included in the invalid symbols. In other words, if the DL symbol indicated by TDD-UL-DL-ConfigCommon is indicated / determined to be a non-SBFD symbol, the terminal determines the symbol to be an invalid symbol.

[0377] Additionally, if the terminal can perform DL reception or UL transmission in an SBFD symbol indicated as DL by TDD-UL-DL-ConfigDedicated, i.e., if the terminal can perform UL transmission in the symbol even if the symbol is indicated as DL by TDD-UL-DL-ConfigDedicated in the case of an SBFD symbol, the symbol must be included in the symbols composing the actual repetition.

[0378] Considering this, SBFD-aware terminals can operate as follows to determine invalid symbols.

[0379] Alt 1. If the terminal can only perform DL reception in an SBFD symbol indicated as DL by TDD-UL-DL-ConfigDedicated, the terminal determines the DL symbol indicated by TDD-UL-DL-ConfigDedicated as an invalid symbol. In other words, even if the DL symbol indicated by TDD-UL-DL-ConfigDedicated is indicated as an SBFD symbol, the terminal does not determine that the symbol is excluded from the invalid symbols.

[0380] Alt 2. If the terminal can perform DL reception or UL transmission in an SBFD symbol indicated as DL by TDD-UL-DL-ConfigDedicated, and if the DL symbol indicated by TDD-UL-DL-ConfigDedicated is set to an SBFD symbol, the terminal determines that the symbol is not included in the invalid symbols. In other words, if the DL symbol indicated by TDD-UL-DL-ConfigDedicated is indicated / determined as a non-SBFD symbol, the terminal determines the symbol as an invalid symbol.

[0381] (4) Even if the DL symbol and the PUCCH symbol overlap, they are included in the slot that constitutes the PUCCH transmission.

[0382] The terminal performs PUCH transmission as follows: PUCCH repeat You can judge the slots of the dog.

[0383] For unpaired spectrum, the terminal shall send N for PUCCH transmission starting from the slot indicated to the terminal for HARQ-ACK reporting (or SR reporting, CSI reporting). PUCCH repeatDetermine the slots. The slots have flexible symbols other than UL symbols or SS / PBCH block symbols provided by startingSymbolIndex as the first symbol, and also have flexible symbols other than consecutive UL symbols or SS / PBCH block symbols starting from the first symbol, such that the number of consecutive UL symbols or flexible symbols is equal to or greater than the number of symbols provided by nrofsymbols.

[0384] According to the above, in case of PUCCH transmission through PUCCH repetition, the terminal transmits the PUCCH in N PUCCH repeat When determining the slots of a dog, if all symbols allocated to PUCCH transmission are included in one of the following symbols, the slot is included in the PUCCH transmission slot.

[0385] 1) UL symbol indicated by TDD-UL-DL-ConfigCommon

[0386] 2) UL symbol indicated by TDD-UL-DL-ConfigDedicated

[0387] 3) Flexible symbols other than SS / PBCH block symbols.

[0388] However, if the DL symbol indicated by TDD-UL-DL-ConfigCommon is set to an SBFD symbol, the slot is not used for PUCCH transmission even if the symbol allocated for PUCCH transmission in a specific slot overlaps with that symbol. PUCCH repeat The dog must not be excluded from the slot.

[0389] In other words, in the case of an SBFD-aware terminal, if the symbol indicated to DL by TDD-UL-DL-ConfigCommon is an SBFD symbol, the symbol must be included in the symbols that can transmit PUCCH.

[0390] For this purpose, in the case of an SBFD-aware terminal, if the symbol indicated as DL by TDD-UL-DL-ConfigCommon is a non-SBFD symbol, the symbol can be determined as a symbol capable of transmitting PUCCH.

[0391] N where the terminal transmits PUCCH PUCCH repeat When determining the slots of a dog, if all symbols allocated to PUCCH transmission are included in one of the following symbols, the slot is included in the PUCCH transmission slot.

[0392] 1) UL symbol indicated by TDD-UL-DL-ConfigCommon

[0393] 2) UL symbol indicated by TDD-UL-DL-ConfigDedicated

[0394] 3) Flexible symbols other than SS / PBCH block symbols

[0395] 4) Symbols indicated as DL by TDD-UL-DL-ConfigCommon and indicated / determined as SBFD symbols.

[0396] In other words, the symbols allocated to PUCCH transmission for a specific slot to be included in the PUCCH transmission slot may include symbols indicated as DL by TDD-UL-DL-ConfigCommon and indicated / determined as SBFD symbols.

[0397] In other words, if at least one symbol among the symbols allocated for PUCCH transmission in a specific slot is a DL symbol indicated by TDD-UL-DL-ConfigCommon and overlaps with a symbol that is not set as an SBFD symbol, the slot is not included in the slots in which PUCCH transmission is performed.

[0398] In addition, if the terminal can perform DL reception or UL transmission in an SBFD symbol indicated as DL by TDD-UL-DL-ConfigDedicated, in other words, if the terminal can perform UL transmission in the symbol even if the symbol is indicated as DL by TDD-UL-DL-ConfigDedicated in the case of an SBFD symbol, the symbol can be determined as a symbol capable of transmitting PUCCH.

[0399] Considering this, in the case of an SBFD-aware terminal, the following operations can be performed to determine PUCCH transmission slots through PUCCH repetition.

[0400] Alt 1. If the terminal can only perform DL reception in the SBFD symbol indicated as DL by TDD-UL-DL-ConfigDedicated, the terminal transmits PUCCH in N PUCCH repeat When judging the slots of the dog, as before, a specific slot is N PUCCH repeat In order to be included in slots, all symbols allocated to PUCCH transmission must not be included in symbols indicated as DL by TDD-UL-DL-ConfigDedicated. In other words, if at least one symbol among the symbols allocated to PUCCH transmission in a specific slot overlaps with a DL symbol indicated by TDD-UL-DL-ConfigDedicated, the slot is not included in the slots in which PUCCH transmission is performed.

[0401] Alt 2. If the terminal can perform DL reception or UL transmission in the SBFD symbol indicated as DL by TDD-UL-DL-ConfigDedicated, the terminal transmits PUCCH in N PUCCH repeat When determining the slots of a dog, if all symbols allocated to PUCCH transmission are included in one of the following symbols, the slot is included in the PUCCH transmission slot.

[0402] 1) UL symbol indicated by TDD-UL-DL-ConfigCommon

[0403] 2) UL symbol indicated by TDD-UL-DL-ConfigDedicated

[0404] 3) Flexible symbols other than SS / PBCH block symbols

[0405] 4) Symbols indicated as DL by TDD-UL-DL-ConfigDedicated and indicated / determined as SBFD symbols.

[0406] In other words, in order for a specific slot to be included in a PUCCH transmission slot, the symbols allocated to PUCCH transmission may include a symbol that is indicated as DL by TDD-UL-DL-ConfigDedicated and indicated / determined as an SBFD symbol. In other words, if at least one symbol among the symbols allocated to PUCCH transmission in a specific slot is a DL symbol indicated by TDD-UL-DL-ConfigDedicated and overlaps with a symbol that is not set as an SBFD symbol, the slot is not included in the slots in which PUCCH transmission is performed.

[0407] Below, the operation of a terminal when a collision occurs between DL reception and UL transmission in an SBFD symbol during full duplex operation within a carrier is described.

[0408] The SBFD symbol can be located in a symbol set to DL by TDD-UL-DL-ConfigCommon or a symbol set / determined as flexible by TDD-UL-DL-ConfigCommon.

[0409] In an SBFD symbol, a terminal can perform DL reception in a DL subband and / or UL transmission in a UL subband. For a half-duplex (HD) terminal, a DL reception operation in a DL subband or a UL transmission operation in a UL subband can be performed in an SBFD symbol.

[0410] If a terminal cannot simultaneously receive a DL signal / channel and transmit a UL signal / channel in a specific symbol, the terminal can only perform one of the two operations. In this case, a method is needed to determine which operation the terminal will perform: receiving a DL signal / channel or transmitting a UL signal / channel.

[0411] Hereinafter, a terminal that recognizes that a base station performs an SBFD operation, determines an SBFD operation time resource and an SBFD operation subband resource, and performs a transmission and reception operation in a subband in an SBFD symbol may be referred to as an SBFD-aware terminal. Hereinafter, the terminal may mean an SBFD-aware terminal.

[0412] An SBFD-aware terminal can operate as follows:

[0413] Case 1. Operation on DL symbols by TDD-UL-DL-ConfigCommon.

[0414] The terminal can configure or determine the DL symbol as an SBFD symbol through TDD-UL-DL-ConfigCommon. The terminal must be able to perform DL reception and UL transmission in the SBFD symbol. To this end, the following approaches can be considered.

[0415] Approach 1. If a specific symbol is set as a SBFD symbol even though it is set as a DL symbol by TDD-UL-DL-ConfigCommon, the terminal can transmit a UL signal / channel in that symbol.

[0416] In this case, a collision may occur between the reception of DL signals / channels and the transmission of UL signals / channels from the perspective of a specific terminal. In such cases, collision handling between the terminal's reception of DL signals / channels and its transmission of UL signals / channels is required.

[0417] Approach 2. The terminal can process / handle the symbol in question in the same way as a symbol set as flexible by TDD-UL-DL-ConfigCommon. In other words, an SBFD-aware terminal can operate in the symbol in question in the same way as it operates in a symbol set as flexible by TDD-UL-DL-ConfigCommon.

[0418] Alternatively, the terminal can convert the symbol into a flexible symbol. In other words, an SBFD-aware terminal can determine that the symbol is a symbol configured as flexible by TDD-UL-DL-ConfigCommon. In this case, the terminal can perform DL Rx or UL Tx operations on the symbol. Therefore, collision handling between the terminal's reception of DL signals / channels and transmission of UL signals / channels is required.

[0419] Case 2. Operation on flexible symbols by TDD-UL-DL-ConfigCommon.

[0420] The terminal can set or determine a flexible symbol by TDD-UL-DL-ConfigCommon as an SBFD symbol. In this case, a flexible symbol by TDD-UL-DL-ConfigCommon may mean a symbol that is not set as DL or UL by TDD-UL-DL-ConfigCommon.

[0421] The terminal must be able to perform DL reception and UL transmission in SBFD symbols.

[0422] Meanwhile, for existing terminals, whether a terminal performs DL reception or UL transmission in a specific symbol is determined through additional signaling, such as TDD-UL-DL-ConfigDedicated and slot format indication information. For SBFD-aware terminals, it is necessary to clarify how to interpret TDD-UL-DL-ConfigDedicated and slot format indication information in SBFD symbols. To this end, the following approaches can be considered.

[0423] When a specific SBFD symbol is a flexible symbol by TDD-UL-DL-ConfigCommon, the terminal may operate as follows with respect to the application of TDD-UL-DL-ConfigDedicated and slot format indication information in the symbol.

[0424] Additionally, the terminal may operate as follows with respect to the application of TDD-UL-DL-ConfigDedicated and slot format indication information to a specific SBFD symbol, even if the symbol is a DL symbol by TDD-UL-DL-ConfigCommon.

[0425] Approach 1. SBFD-aware terminals may not be instructed to receive TDD-UL-DL-ConfigDedicated and / or slot format indication information, which previously restricted the terminal's DL-Rx / UL-Tx operations. SBFD-aware terminals may ignore such information even if instructed to do so.

[0426] Alternatively, if an SBFD-aware terminal is instructed to provide TDD-UL-DL-ConfigDedicated and / or slot format indication, the terminal may not apply the information to SBFD symbols. In other words, the TDD-UL-DL-ConfigDedicated and / or slot format indication information may be applied only to non-SBFD symbols.

[0427] In such cases, the terminal can perform DL Rx or UL Tx operations on the corresponding symbol. Therefore, collision handling between the terminal's reception of DL signals / channels and transmission of UL signals / channels is required.

[0428] Approach 2. The terminal can determine whether the SBFD symbol is used as a DL symbol or an UL symbol through TDD-UL-DL-ConfigDedicated and / or slot format indication information. In this case, the terminal can perform DL Rx or UL Tx operations on the SBFD symbol, even though it has been configured as a DL symbol or UL symbol through TDD-UL-DL-ConfigDedicated and / or slot format indication.

[0429] At this time, the TDD-UL-DL-ConfigDedicated and / or slot format indication information may be applied only to flexible symbols by TDD-UL-DL-ConfigCommon. Alternatively, the TDD-UL-DL-ConfigDedicated information may also be applied to DL symbols and / or slot format indications by TDD-UL-DL-ConfigCommon indicated by the SBFD symbol.

[0430] Case a-1. If a terminal is instructed to DL a specific SBFD symbol by TDD-UL-DL-ConfigDedicated and / or slot format indication, the terminal may perform DL Rx or UL Tx operation on the symbol.

[0431] In this case, a collision may occur between the reception of DL signals / channels and the transmission of UL signals / channels from the terminal's perspective. In such cases, collision handling between the terminal's reception of DL signals / channels and the transmission of UL signals / channels is required.

[0432] Case a-2. If a terminal is directed to UL for a specific SBFD symbol by TDD-UL-DL-ConfigDedicated and / or slot format indication, the terminal can perform DL Rx or UL Tx operation on the symbol.

[0433] In this case, a collision may occur between the reception of DL signals / channels and the transmission of UL signals / channels from the terminal's perspective. In such cases, collision handling between the terminal's reception of DL signals / channels and the transmission of UL signals / channels is required.

[0434] Case a-3. If a terminal is flexibly instructed to use a specific SBFD symbol via the TDD-UL-DL-ConfigDedicated and / or slot format instructions, the terminal may perform DL Rx or UL Tx operations on that symbol. In this case, a collision may occur between the reception of DL signals / channels and the transmission of UL signals / channels from the terminal's perspective.

[0435] Approach 3. The Tx / Rx direction of a terminal in an SBFD symbol can be restricted through TDD-UL-DL-ConfigDedicated and / or slot format indication information. The terminal can determine whether the SBFD symbol is used as a DL symbol or an UL symbol through TDD-UL-DL-ConfigDedicated and / or slot format indication information.

[0436] At this time, TDD-UL-DL-ConfigDedicated and / or slot format indication information may be applied only to flexible symbols by TDD-UL-DL-ConfigCommon. Alternatively, TDD-UL-DL-ConfigDedicated and / or slot format indication information may also be applied to DL symbols by TDD-UL-DL-ConfigCommon indicated by SBFD symbols.

[0437] Case b-1. If a terminal is instructed to DL a specific SBFD symbol by TDD-UL-DL-ConfigDedicated and / or slot format indication, the terminal can perform DL reception (within the DL subband) operation on the symbol, but cannot perform UL transmission (within the UL subband) operation.

[0438] Case b-2. If a terminal is instructed to transmit a specific SBFD symbol to UL by TDD-UL-DL-ConfigDedicated and / or slot format indication, the terminal can perform UL transmission (within the UL subband) operation in the symbol, but cannot perform DL reception (within the DL subband) operation.

[0439] Case b-3. If a terminal is flexibly instructed to use a specific SBFD symbol via TDD-UL-DL-ConfigDedicated and / or slot format instructions, the terminal may perform DL Rx or UL Tx operations on that symbol. In this case, a collision may occur between the reception of DL signals / channels and the transmission of UL signals / channels from the terminal's perspective. In such cases, collision handling between the reception of DL signals / channels and the transmission of UL signals / channels is required.

[0440] Below, we propose the operation of a terminal when a collision occurs between DL reception and UL transmission in an SBFD symbol during full duplex operation within a carrier.

[0441] When a collision occurs between DL reception and UL transmission in a particular SBFD symbol, the terminal may behave as follows.

[0442] Method 1. How to apply collision handling behavior to semi-static flexible symbols of legacy terminals.

[0443] An SBFD-aware terminal can follow the behavior of a legacy UE (e.g., a legacy terminal operating in an unpaired spectrum) in the semi-static flexible symbols when a collision occurs between DL reception and UL transmission.

[0444] Method 2. How to give priority to DL reception.

[0445] An SBFD-aware terminal can prioritize DL reception over UL transmission when a collision occurs between DL reception and UL transmission. More specifically, the terminal can operate as follows.

[0446] Method 2-1. If a collision occurs between the reception of a DL signal / channel and the transmission of a UL signal / channel, the terminal performs DL reception and does not perform UL transmission. Additionally, if the transmission of a UL signal / channel in a specific SBFD symbol affects (causes problems / interferences) the reception of DL signals / channels in surrounding SBFD symbols, the terminal does not perform transmission of the corresponding UL signal / channel.

[0447] Method 2-2. The terminal applies Method 2-1, but when transmitting a specific UL signal / channel, it prioritizes the transmission of the UL signal / channel over the reception of the DL signal / channel. In other words, when transmitting a specific UL signal / channel, the terminal transmits the UL signal / channel without receiving the DL signal / channel.

[0448] Additionally, if the transmission of a specific UL signal / channel in a specific SBFD symbol affects (causes problems / interferences with) the reception of a DL signal / channel in a surrounding SBFD symbol, the terminal transmits the UL signal / channel and does not receive the DL signal / channel.

[0449] Specific UL signals / channels that are given priority over reception of these DL signals / channels may include all or some of the following:

[0450] 1) PRACH

[0451] 2) Aperiodic PUCCH

[0452] 3) PUSCH scheduled by DCI

[0453] 4) PUSCH with priority flag. When scheduling a PUSCH, information regarding the priority of PUSCH transmission may be indicated. If this priority information indicates that the PUSCH has priority over the reception of DL signals / channels, the PUSCH is called a PUSCH with a priority flag.

[0454] Method 2-3. This method includes cases where the contents of this method are applied only to some / specific conflict situations among the conflict situations included below.

[0455] 1) Conflict between configured UL and configured DL.

[0456] If a collision occurs between transmission of a UL signal / channel (e.g., configured UL) established by upper layer signaling such as RRC, MAC-CE, etc. and reception of a DL signal / channel (e.g., configured DL) established by upper layer signaling, the terminal performs reception of the established DL and does not perform transmission of the established UL.

[0457] Additionally, the terminal does not perform transmission of the configured UL in a specific SBFD symbol if the transmission affects (causes problems / interferences with) the reception of the configured DL in the surrounding SBFD symbols.

[0458] 2) Conflict between established UL / DL and dynamic DL / UL.

[0459] If a collision occurs between a signal / channel set by upper layer signaling, such as RRC or MAC-CE, and a signal / channel indicated by L1 signaling, such as DCI, the terminal performs transmission / reception of the signal / channel indicated by L1 signaling and does not perform transmission / reception of the signal / channel set by upper layer signaling.

[0460] If a collision occurs between transmission of a UL signal / channel (e.g., established UL) established by upper layer signaling such as RRC, MAC-CE, etc. and reception of a DL signal / channel (e.g., dynamic DL) indicated by L1 signaling such as DCI, etc., the terminal performs reception of the dynamic DL and does not perform transmission of the established UL.

[0461] If a collision occurs between the reception of a DL signal / channel (e.g., established DL) established by upper layer signaling such as RRC, MAC-CE, etc. and the transmission of a UL signal / channel (e.g., dynamic UL) indicated by L1 signaling such as DCI, etc., the terminal performs transmission of the dynamic UL and does not perform reception of the established DL.

[0462] Additionally, the terminal does not transmit the configured UL in a specific SBFD symbol if the transmission affects (causes problems / interferences with) the reception of dynamic DL in surrounding SBFD symbols.

[0463] The terminal does not perform reception of the configured DL in a specific SBFD symbol if the reception of the configured DL affects (causes problems / interferences with) the transmission of dynamic UL in the surrounding SBFD symbols.

[0464] 3) Conflict between dynamic UL and dynamic DL.

[0465] If a collision occurs between transmission of a UL signal / channel (e.g., dynamic UL) indicated by L1 signaling such as DCI and reception of a DL signal / channel (e.g., dynamic DL) indicated by L1 signaling, the terminal performs reception of the dynamic DL and does not perform transmission of the dynamic UL.

[0466] Additionally, the terminal does not transmit dynamic UL in a specific SBFD symbol if the transmission of the dynamic UL in that SBFD symbol affects (causes problems / interferences) the reception of dynamic DL in surrounding SBFD symbols.

[0467] Method 3. How to give priority to UL transmission.

[0468] An SBFD-aware terminal can prioritize UL transmission over DL reception when a collision occurs between DL reception and UL transmission. More specifically, the terminal can operate as follows.

[0469] Method 3-1. If a collision occurs between the reception of a DL signal / channel and the transmission of a UL signal / channel, the terminal performs UL transmission and does not perform DL reception. Additionally, if the reception of a DL signal / channel in a specific SBFD symbol affects (causes problems / interferences) the transmission of a UL signal / channel in a neighboring SBFD symbol, the terminal does not perform reception of the corresponding DL signal / channel.

[0470] Method 3-2. The terminal applies Method 3-1, but when receiving a specific DL signal / channel, it prioritizes the reception of the DL signal / channel over the transmission of the UL signal / channel. In other words, when receiving a specific DL signal / channel, the terminal performs reception of the DL signal / channel without transmitting the UL signal / channel.

[0471] Additionally, if the reception of a specific DL signal / channel in a specific SBFD symbol affects (causes problems / interferences with) the transmission of a UL signal / channel in a surrounding SBFD symbol, the terminal performs reception of the DL signal / channel and does not perform transmission of the UL signal / channel.

[0472] Specific DL signals / channels that take precedence over the transmission of these UL signals / channels may include all or part of the following:

[0473] 1) SS / PBCH

[0474] 2) PDSCH scheduled by DCI

[0475] 3) PDSCH with priority flag. When scheduling a PDSCH, information regarding the priority of PDSCH transmission may be indicated. If this priority information indicates that the PDSCH has priority over transmission of UL signals / channels, such a PDSCH is called a PDSCH with a priority flag.

[0476] Method 3-3. This method includes cases where the contents of this method are applied only to some / specific conflict situations among the conflict situations included below.

[0477] 1) Conflict between the set UL and the set DL.

[0478] If a collision occurs between transmission of a UL signal / channel (e.g., configured UL) established by upper layer signaling such as RRC, MAC-CE, etc. and reception of a DL signal / channel (e.g., configured DL) established by upper layer signaling, the terminal performs transmission of the established UL and does not perform transmission of the established DL.

[0479] Additionally, the terminal does not perform reception of the configured DL in a specific SBFD symbol if the reception of the configured DL in the surrounding SBFD symbols affects (causes problems / interferences) transmission of the configured UL.

[0480] 2) Conflict between established UL / DL and dynamic DL / UL.

[0481] If a collision occurs between a signal / channel set by upper layer signaling, such as RRC or MAC-CE, and a signal / channel indicated by L1 signaling, such as DCI, the terminal performs transmission / reception of the signal / channel indicated by L1 signaling and does not perform transmission / reception of the signal / channel set by upper layer signaling.

[0482] If a collision occurs between transmission of a UL signal / channel (e.g., established UL) established by upper layer signaling such as RRC, MAC-CE, etc. and reception of a DL signal / channel (e.g., dynamic DL) indicated by L1 signaling such as DCI, etc., the terminal performs reception of the dynamic DL and does not perform transmission of the established UL.

[0483] If a collision occurs between the reception of a DL signal / channel (e.g., established DL) established by upper layer signaling such as RRC, MAC-CE, etc. and the transmission of a UL signal / channel (e.g., dynamic UL) indicated by L1 signaling such as DCI, etc., the terminal performs transmission of the dynamic UL and does not perform reception of the established DL.

[0484] Additionally, the terminal does not transmit the configured UL in a specific SBFD symbol if the transmission affects (causes problems / interferences with) the reception of dynamic DL in surrounding SBFD symbols.

[0485] The terminal does not perform reception of the configured DL in a specific SBFD symbol if the reception of the configured DL affects (causes problems / interferences with) the transmission of dynamic UL in the surrounding SBFD symbols.

[0486] 3) Conflict between dynamic UL and dynamic DL.

[0487] If a collision occurs between transmission of a UL signal / channel (e.g., dynamic UL) indicated by L1 signaling such as DCI and reception of a DL signal / channel (e.g., dynamic DL) indicated by L1 signaling, the terminal performs transmission of the dynamic UL and does not perform reception of the dynamic DL.

[0488] Additionally, the terminal does not perform reception of a dynamic DL if reception of the dynamic DL in a specific SBFD symbol affects (causes problems / interferences with) transmission of the dynamic UL in surrounding SBFD symbols.

[0489] At this time, different methods may be applied depending on the symbol.

[0490] Example 1.

[0491] If a specific SBFD symbol is a symbol indicated as DL by TDD-UL-DL-ConfigCommon, TDD-UL-DL-ConfigDedicated and / or slot format indication (indicated as a DL symbol), the terminal applies method 2 above.

[0492] If a specific SBFD symbol is a symbol indicated as UL by TDD-UL-DL-ConfigCommon, TDD-UL-DL-ConfigDedicated and / or slot format indication (if indicated as a UL symbol), the terminal applies method 3 above.

[0493] If a specific SBFD symbol is a symbol for which DL or UL information is not indicated by TDD-UL-DL-ConfigCommon, TDD-UL-DL-ConfigDedicated and / or slot format indication (indicated as a flexible symbol), the terminal applies Method 1 above.

[0494] Example 2.

[0495] If a specific SBFD symbol is a symbol indicated as DL by TDD-UL-DL-ConfigCommon, TDD-UL-DL-ConfigDedicated and / or slot format indication (indicated as a DL symbol), the terminal applies method 2 above.

[0496] If a specific SBFD symbol is a symbol indicated as UL by TDD-UL-DL-ConfigCommon, TDD-UL-DL-ConfigDedicated and / or slot format indication (indicated as a UL symbol) or a symbol for which DL or UL information is not indicated (indicated as a flexible symbol), the terminal applies method 3 above.

[0497] Example 3.

[0498] If a specific SBFD symbol is a symbol indicated as DL by TDD-UL-DL-ConfigCommon, the terminal applies method 2 above.

[0499] If a specific SBFD symbol is a symbol indicated as flexible by TDD-UL-DL-ConfigCommon, the terminal applies method 3 above.

[0500] Example 4.

[0501] If a specific SBFD symbol is a symbol indicated as DL by TDD-UL-DL-ConfigCommon, the terminal applies method 2 above.

[0502] If a specific SBFD symbol is a symbol indicated as flexible by TDD-UL-DL-ConfigCommon, the terminal applies Method 1 above.

[0503] Figure 21 illustrates a wireless device applicable to the present specification.

[0504] Referring to FIG. 21, the first wireless device (100) and the second wireless device (200) can transmit and receive wireless signals through various wireless access technologies (e.g., LTE, NR).

[0505] A first wireless device (100) includes at least one processor (102) and at least one memory (104), and may further include at least one transceiver (106) and / or at least one antenna (108). The at least one processor (102, hereinafter simply referred to as a processor) controls at least one memory (104, hereinafter simply referred to as a memory) and / or at least one transceiver (106, hereinafter simply referred to as a transceiver or a transceiver), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (102) may process information in the memory (104) to generate first information / signal, and then transmit a wireless signal including the first information / signal via the transceiver (106). In addition, the processor (102) may receive a wireless signal including second information / signal through the transceiver (106), and then store information obtained from signal processing of the second information / signal in the memory (104). The memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, the memory (104) may perform some or all of the processes controlled by the processor (102), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver (106) may be connected to the processor (102) and may transmit and / or receive a wireless signal through one or more antennas (108). The transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used interchangeably with an RF (Radio Frequency) unit.In this specification, wireless device may also mean a communication modem / circuit / chip.

[0506] A processor (102) receives a system information block (SIB), wherein the SIB includes SBFD time information that sets the time position of a cell-specific subband full duplex (SBFD) subband, and receives downlink control information (DCI) including a slot format indicator (SFI) that indicates a slot format including downlink symbols, uplink symbols, and flexible symbols. The processor (102) is included in an SBFD aware UE, and is characterized in that it applies the SFI only to non-SBFD symbols among SBFD symbols and non-SBFD symbols based on the SBFD time information. The specific operation thereof has been described with reference to FIGS. 18 to 20.

[0507] A second wireless device (200) includes at least one processor (202), at least one memory (204), and may further include at least one transceiver (206) and / or at least one antenna (208). The processor (202) controls the memory (204) and / or the transceiver (206), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (202) may process information in the memory (204) to generate third information / signal, and then transmit a wireless signal including the third information / signal via the transceiver (206). In addition, the processor (202) may receive a wireless signal including fourth information / signal via the transceiver (206), and then store information obtained from signal processing of the fourth information / signal in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may perform some or all of the processes controlled by the processor (202), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via one or more antennas (208). The transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with an RF unit. In this specification, a wireless device may also mean a communication modem / circuit / chip.

[0508] The processor (202) transmits a system information block (SIB), wherein the SIB includes SBFD time information that sets the time position of a cell-specific subband full duplex (SBFD) subband, and transmits downlink control information (DCI) including a slot format indicator (SFI) that indicates a slot format including downlink symbols, uplink symbols, and flexible symbols to an SBFD aware UE, and communicates with the SBFD aware UE based on the SFI being applied only to the non-SBFD symbols among SBFD symbols and non-SBFD symbols based on the SBFD time information. The specific operation has been described with reference to FIGS. 18 to 20.

[0509] Hereinafter, the hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors (102, 202) may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors (102, 202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors (102, 202) can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed herein, and provide the signals to one or more transceivers (106, 206). One or more processors (102, 202) can receive signals (e.g., baseband signals) from one or more transceivers (106, 206) and obtain PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein.

[0510] The one or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. The one or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in the one or more processors (102, 202). The one or more processors (102, 202) may also be implemented by at least one computer-readable medium (CRM) containing instructions based on which at least one processor is executed.

[0511] In other words, at least one computer readable medium (CRM) including instructions based on being executed by at least one processor receives a system information block (SIB), wherein the SIB includes SBFD time information that sets a time position of a cell-specific subband full duplex (SBFD) subband, and receives downlink control information (DCI) including a slot format indicator (SFI) that indicates a slot format including downlink symbols, uplink symbols, and flexible symbols, wherein the at least one processor is included in an SBFD aware UE, and the at least one processor is characterized in that it applies the SFI only to the non-SBFD symbols among the SBFD symbols and non-SBFD symbols based on the SBFD time information. The specific operation thereof has been described with reference to FIGS. 18 to 20.

[0512] The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software in the form of codes, instructions and / or sets of instructions. The firmware or software configured to perform the descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be included in one or more processors (102, 202) or stored in one or more memories (104, 204) and executed by one or more processors (102, 202). The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software in the form of codes, instructions and / or sets of instructions.

[0513] One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories (104, 204) may be configured as ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories (104, 204) may be located internally and / or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections.

[0514] One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or flowcharts of this document, to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or flowcharts of this document, from one or more other devices. For example, one or more transceivers (106, 206) can be connected to one or more processors (102, 202) and can transmit and receive wireless signals. For example, one or more processors (102, 202) can control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be coupled to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, or the like, as referred to in the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein, via one or more antennas (108, 208). In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) can convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202).One or more transceivers (106, 206) may convert user data, control information, wireless signals / channels, etc. processed by one or more processors (102, 202) from baseband signals to RF band signals. For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or filter.

[0515] Fig. 22 illustrates an example of a signal processing module structure. Here, signal processing may be performed in the processor (102, 202) of Fig. 21.

[0516] Referring to FIG. 22, a transmission device (e.g., a processor, a processor and a memory, or a processor and a transceiver) within a terminal or a base station may include a scrambler (301), a modulator (302), a layer mapper (303), an antenna port mapper (304), a resource block mapper (305), and a signal generator (306).

[0517] A transmitting device can transmit one or more codewords. The coded bits within each codeword are scrambled by a scrambler (301) and transmitted over a physical channel. A codeword may also be referred to as a data string and may be equivalent to a transport block, which is a data block provided by the MAC layer.

[0518] The scrambled bits are modulated into complex-valued modulation symbols by a modulator (302). The modulator (302) can modulate the scrambled bits according to a modulation scheme and arrange them into complex-valued modulation symbols that represent positions on a signal constellation. There is no limitation on the modulation scheme, and m-PSK (m-Phase Shift Keying) or m-QAM (m-Quadrature Amplitude Modulation) can be used to modulate the encoded data. The modulator may be referred to as a modulation mapper.

[0519] The complex modulation symbols may be mapped to one or more transmission layers by a layer mapper (303). The complex modulation symbols on each layer may be mapped by an antenna port mapper (304) for transmission on an antenna port.

[0520] The resource block mapper (305) can map the complex modulation symbol for each antenna port to an appropriate resource element within a virtual resource block (VRB) allocated for transmission. The resource block mapper can map the VRB to a physical resource block (PRB) according to an appropriate mapping scheme. The resource block mapper (305) can assign the complex modulation symbol for each antenna port to an appropriate subcarrier and multiplex it according to the user.

[0521] The signal generator (306) can generate a complex-valued time domain OFDM symbol signal by modulating a complex modulation symbol for each antenna port, that is, an antenna-specific symbol, with a specific modulation method, for example, an Orthogonal Frequency Division Multiplexing (OFDM) method. The signal generator can perform an Inverse Fast Fourier Transform (IFFT) on the antenna-specific symbol, and a Cyclic Prefix (CP) can be inserted into the time domain symbol on which the IFFT is performed. The OFDM symbol is transmitted to a receiving device through each transmitting antenna through digital-to-analog conversion, frequency up-conversion, etc. The signal generator can include an IFFT module, a CP inserter, a Digital-to-Analog Converter (DAC), a frequency uplink converter, etc.

[0522] Fig. 23 illustrates another example of a signal processing module structure within a transmission device. Here, signal processing may be performed in a processor of a terminal / base station, such as the processor (102, 202) of Fig. 21.

[0523] Referring to FIG. 23, a transmission device (e.g., a processor, a processor and a memory, or a processor and a transceiver) in a terminal or a base station may include a scrambler (401), a modulator (402), a layer mapper (403), a precoder (404), a resource block mapper (405), and a signal generator (406).

[0524] The transmitting device can transmit coded bits within a codeword through a physical channel after scrambling the coded bits within the codeword by a scrambler (401).

[0525] The scrambled bits are modulated into complex modulation symbols by a modulator (402). The modulator can modulate the scrambled bits according to a predetermined modulation scheme and arrange them into complex modulation symbols representing positions on a signal constellation. There is no limitation on the modulation scheme, and pi / 2-BPSK (pi / 2-Binary Phase Shift Keying), m-PSK (m-Phase Shift Keying), or m-QAM (m-Quadrature Amplitude Modulation) can be used to modulate the encoded data.

[0526] The above complex modulation symbol can be mapped to one or more transmission layers by the layer mapper (403).

[0527] The complex modulation symbols on each layer can be precoded by the precoder (404) for transmission on the antenna ports. Here, the precoder may perform precoding after performing transform precoding on the complex modulation symbols. Alternatively, the precoder may perform precoding without performing transform precoding. The precoder (404) may process the complex modulation symbols in a MIMO manner according to multiple transmission antennas to output antenna-specific symbols and distribute the antenna-specific symbols to the corresponding resource block mapper (405). The output z of the precoder (404) can be obtained by multiplying the output y of the layer mapper (403) by the precoding matrix W of NХM. Here, N is the number of antenna ports and M is the number of layers.

[0528] The resource block mapper (405) maps the demodulation modulation symbol for each antenna port to the appropriate resource element within the virtual resource block allocated for transmission.

[0529] The resource block mapper (405) can assign complex modulation symbols to appropriate subcarriers and multiplex them according to the user.

[0530] The signal generator (406) can generate a complex-valued time domain OFDM (Orthogonal Frequency Division Multiplexing) symbol signal by modulating a complex modulation symbol with a specific modulation method, for example, OFDM. The signal generator (406) can perform an Inverse Fast Fourier Transform (IFFT) on an antenna-specific symbol, and a Cyclic Prefix (CP) can be inserted into the time domain symbol on which the IFFT has been performed. The OFDM symbol is transmitted to a receiving device through each transmitting antenna after going through digital-to-analog conversion, frequency upconversion, etc. The signal generator (406) can include an IFFT module, a CP inserter, a Digital-to-Analog Converter (DAC), a frequency uplink converter, etc.

[0531] The signal processing process of the receiving device may be configured in reverse order of the signal processing process of the transmitter. Specifically, the processor of the receiving device performs decoding and demodulation on a wireless signal received externally through the antenna port(s) of the transceiver. The receiving device may include a plurality of multiple receiving antennas, and each signal received through the receiving antenna is restored to a baseband signal and then multiplexed and MIMO demodulated to be restored to a data sequence originally intended to be transmitted by the transmitting device. The receiving device (1820) may include a signal restorer for restoring the received signal to a baseband signal, a multiplexer for combining and multiplexing the received and processed signals, and a channel demodulator for demodulating the multiplexed signal sequence into a corresponding codeword. The signal restorer, the multiplexer, and the channel demodulator may be configured as an integrated module performing their functions or as individual modules. More specifically, the signal restorer may include an analog-to-digital converter (ADC) that converts an analog signal into a digital signal, a CP remover that removes a CP from the digital signal, an FFT module that applies an FFT (fast Fourier transform) to a signal from which the CP has been removed to output a frequency domain symbol, and a resource element demapper / equalizer that restores the frequency domain symbol to an antenna-specific symbol. The antenna-specific symbol is restored to a transmission layer by a multiplexer, and the transmission layer is restored to a codeword that the transmitter intended to transmit by a channel demodulator.

[0532] FIG. 24 illustrates an example of a wireless communication device according to an implementation example of the present disclosure.

[0533] Referring to FIG. 24, a wireless communication device, for example, a terminal, may include at least one of a processor (2310) such as a digital signal processor (DSP) or a microprocessor, a transceiver (2335), a power management module (2305), an antenna (2340), a battery (2355), a display (2315), a keypad (2320), a global positioning system (GPS) chip (2360), a sensor (2365), a memory (2330), a subscriber identification module (SIM) card (2325), a speaker (2345), and a microphone (2350). There may be a plurality of antennas and processors.

[0534] The processor (2310) can implement the functions, procedures, and methods described in this specification. The processor (2310) of FIG. 24 may be the processor (102, 202) of FIG. 21.

[0535] Memory (2330) is connected to the processor (2310) and stores information related to the processor's operation. The memory may be located internally or externally to the processor and may be connected to the processor via various technologies, such as wired or wireless connections. The memory (2330) of FIG. 24 may be the memory (104, 204) of FIG. 21.

[0536] A user may input various types of information, such as a phone number, using various techniques, such as pressing buttons on a keypad (2320) or activating sound using a microphone (2350). The processor (2310) may receive and process the user's information and perform an appropriate function, such as dialing the entered phone number. In some scenarios, data may be retrieved from a SIM card (2325) or memory (2330) to perform the appropriate function. In some scenarios, the processor (2310) may display various types of information and data on a display (2315) for the user's convenience.

[0537] A transceiver (2335) is coupled to a processor (2310) and transmits and / or receives wireless signals, such as radio frequency (RF) signals. The processor may control the transceiver to initiate communication or transmit wireless signals containing various types of information or data, such as voice communication data. The transceiver includes a transmitter and a receiver for transmitting and receiving wireless signals. An antenna (2340) may facilitate the transmission and reception of wireless signals. In some implementations, upon receiving a wireless signal, the transceiver may forward and convert the signal to a baseband frequency for processing by the processor. The processed signal may be processed by various techniques, such as being converted into audible or readable information for output through a speaker (2345). The transceiver of FIG. 24 may be the transceiver (106, 206) of FIG. 29.

[0538] Although not shown in FIG. 24, various components, such as a camera and a Universal Serial Bus (USB) port, may be additionally included in the terminal. For example, the camera may be connected to the processor (2310).

[0539] Figure 24 is only one implementation example for a terminal, and the implementation examples are not limited thereto. The terminal does not necessarily have to include all the elements of Figure 24. In other words, some components, such as the keypad (2320), the Global Positioning System (GPS) chip (2360), the sensor (2365), and the SIM card (2325), may not be essential elements, and in such cases, may not be included in the terminal.

[0540] Figure 25 illustrates another example of a wireless device.

[0541] According to FIG. 25, the wireless device may include at least one processor (102, 202), at least one memory (104, 204), at least one transceiver (106, 206), and one or more antennas (108, 208).

[0542] The difference between the example of the wireless device described in FIG. 21 and the example of the wireless device in FIG. 25 is that in FIG. 21, the processor (102, 202) and the memory (104, 204) are separated, whereas in the example of FIG. 25, the memory (104, 204) is included in the processor (102, 202). In other words, the processor and the memory may constitute a single chipset.

[0543] Fig. 26 illustrates a communication system (1) applicable to this specification.

[0544] Referring to FIG. 26, a communication system (1) applied to the present specification includes a wireless device, a base station, and a network. Here, the wireless device refers to a device that performs communication using a wireless access technology (e.g., 5G NR (New RAT), LTE (Long Term Evolution)) and may be referred to as a communication / wireless / 5G device. Although not limited thereto, the wireless device may include a robot (100a), a vehicle (100b-1, 100b-2), an XR (eXtended Reality) device (100c), a hand-held device (100d), a home appliance (100e), an IoT (Internet of Things) device (100f), and an AI device / server (400). For example, the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, a vehicle capable of performing vehicle-to-vehicle communication, etc. Here, the vehicle may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone). XR devices include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices, and can be implemented in the form of HMD (Head-Mounted Device), HUD (Head-Up Display) installed in a vehicle, television, smartphone, computer, wearable device, home appliance, digital signage, vehicle, robot, etc. Mobile devices can include smartphone, smart pad, wearable device (e.g., smart watch, smart glass), computer (e.g., laptop, etc.), etc. Home appliances can include TV, refrigerator, washing machine, etc. IoT devices can include sensors, smart meters, etc. For example, base stations and networks can also be implemented as wireless devices, and a specific wireless device (200a) can act as a base station / network node to other wireless devices.

[0545] Wireless devices (100a to 100f) can be connected to a network (300) via a base station (200). Artificial Intelligence (AI) technology can be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) via the network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, etc. The wireless devices (100a to 100f) can communicate with each other via the base station (200) / network (300), but can also communicate directly (e.g., sidelink communication) without going through the base station / network. For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to Everything) communication). In addition, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0546] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a~100f) / base stations (200), and base stations (200) / base stations (200). Here, wireless communication / connection can be achieved through various wireless access technologies (e.g., 5G NR) such as uplink / downlink communication (150a), sidelink communication (150b) (or, D2D communication), and communication between base stations (150c) (e.g., relay, IAB (Integrated Access Backhaul). Through wireless communication / connection (150a, 150b, 150c), wireless devices and base stations / wireless devices, and base stations and base stations can transmit / receive wireless signals to each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, at least some of various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation processes can be performed based on various proposals of the present specification.

[0547] Meanwhile, NR supports multiple numerologies (or subcarrier spacing (SCS)) to support various 5G services. 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 areas, lower latency, and wider carrier bandwidth; and an SCS of 60 kHz or higher supports a bandwidth greater than 24.25 GHz to overcome phase noise.

[0548] 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 frequency ranges of the two types (FR1, FR2) can be as shown in Table 5 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).

[0549] [Table 5]

[0550]

[0551] As described above, the numerical value of the frequency range of the NR system can be changed. For example, FR1 may include a band from 410 MHz to 7125 MHz, as shown in Table 6 below. In other words, FR1 may include a frequency band above 6 GHz (or 5850, 5900, 5925 MHz, etc.). For example, the frequency band above 6 GHz (or 5850, 5900, 5925 MHz, etc.) included within FR1 may include an unlicensed band. The unlicensed band may be used for various purposes, such as for vehicle communications (e.g., autonomous driving).

[0552] [Table 6]

[0553]

[0554] 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 the method, A user equipment (UE) receives a system information block (SIB), wherein the SIB includes subband full duplex (SBFD) time information that sets the time position of a cell-specific subband full duplex (SBFD) subband, and The terminal receives downlink control information (DCI) including a slot format indicator (SFI) indicating a slot format including downlink symbols, uplink symbols, and flexible symbols, The above terminal is an SBFD aware UE, A method characterized in that the terminal applies the SFI only to the non-SBFD symbols among the SBFD symbols and non-SBFD symbols based on the SBFD time information.

2. A method according to claim 1, characterized in that the terminal further receives cell-specific uplink / downlink TDD (time division duplex) settings.

3. A method according to claim 2, characterized in that the terminal is allowed to perform uplink transmission within an uplink subband within an SBFD symbol set as downlink in the cell-specific uplink / downlink TDD setting.

4. A method according to claim 3, characterized in that the terminal is not permitted to perform uplink transmission outside the uplink subband.

5. A method according to claim 3, characterized in that the terminal is allowed to perform downlink reception within a downlink subband within the SBFD symbol.

6. A method according to claim 2, characterized in that the terminal is allowed to perform uplink transmission within an uplink subband within an SBFD symbol that is flexibly set in the cell-specific uplink / downlink TDD setting.

7. A method according to claim 6, characterized in that the terminal is not permitted to perform uplink transmission outside the uplink subband.

8. A method according to claim 6, characterized in that the terminal is allowed to perform downlink reception within a downlink subband within the SBFD symbol.

9. In the second paragraph, a method characterized in that, for specific non-SBFD symbols set as downlink by the cell-specific uplink / downlink TDD setting among the SBFD symbols and the non-SBFD symbols, the terminal skips transmission of the PUSCH (physical uplink shared channel), the PUCCH (physical uplink control channel), the PRACH (physical random access channel) or the SRS (sounding reference signal) based on whether the PUSCH, the PUCCH, the PRACH or the SRS overlaps at least partly with the specific non-SBFD symbols.

10. In the second paragraph, when PUSCH repetitive transmission is performed based on available slots, a method characterized in that if at least one symbol among the symbols allocated to PUSCH transmission in a specific slot is set to downlink by the cell-specific uplink / downlink TDD setting and overlaps with the non-SBFD symbols, the specific slot is excluded from the count of the available slots.

11. A method according to claim 1, characterized in that the terminal further receives terminal-specific uplink / downlink TDD settings.

12. In paragraph 11, A method characterized in that, if at least one symbol among the symbols allocated for PUSCH transmission in a specific slot is set to downlink by the terminal-specific uplink / downlink TDD setting and overlaps with the non-SBFD symbols, the specific slot is excluded from the count of available slots for PUSCH transmission.

13. The terminal is, At least one transceiver; At least one memory; and At least one processor operably coupled with said at least one memory and said at least one transceiver, wherein said at least one memory comprises instructions that are executed by said at least one processor to perform operations, The above actions are, A user equipment (UE) receives a system information block (SIB), wherein the SIB includes subband full duplex (SBFD) time information that sets the time position of a cell-specific subband full duplex (SBFD) subband, and The terminal receives downlink control information (DCI) including a slot format indicator (SFI) indicating a slot format including downlink symbols, uplink symbols, and flexible symbols, The above terminal is an SBFD aware UE, A terminal characterized in that the terminal applies the SFI only to the non-SBFD symbols among the SBFD symbols and non-SBFD symbols based on the SBFD time information.

14. A terminal according to claim 13, characterized in that the terminal further receives cell-specific uplink / downlink TDD (time division duplex) settings.

15. A terminal characterized in that, in the 14th paragraph, the terminal is allowed to perform uplink transmission within an uplink subband within an SBFD symbol set as downlink in the cell-specific uplink / downlink TDD setting.

16. A terminal according to claim 15, characterized in that the terminal is not permitted to perform uplink transmission outside the uplink subband.

17. A terminal according to claim 15, characterized in that the terminal is allowed to perform downlink reception within a downlink subband within the SBFD symbol.

18. A terminal characterized in that, in the 14th paragraph, the terminal is allowed to perform uplink transmission within an uplink subband within an SBFD symbol that is flexibly set in the cell-specific uplink / downlink TDD setting.

19. A terminal characterized in that, in paragraph 18, the terminal is not permitted to perform uplink transmission outside the uplink subband.

20. A terminal characterized in that, in paragraph 18, the terminal is allowed to perform downlink reception within a downlink subband within the SBFD symbol.

21. In the 14th paragraph, a terminal characterized in that, for specific non-SBFD symbols set as downlink by the cell-specific uplink / downlink TDD setting among the SBFD symbols and the non-SBFD symbols, the terminal skips transmission of the PUSCH (physical uplink shared channel), the PUCCH (physical uplink control channel), the PRACH (physical random access channel) or the SRS (sounding reference signal) based on whether the PUSCH, the PUCCH, the PRACH or the SRS overlaps at least partly with the specific non-SBFD symbols.

22. In the 14th paragraph, when PUSCH repetitive transmission is performed based on available slots, if at least one symbol among the symbols allocated to PUSCH transmission in a specific slot is set to downlink by the cell-specific uplink / downlink TDD setting and overlaps with the non-SBFD symbols, the terminal is characterized in that the specific slot is excluded from the count of the available slots.

23. A terminal according to claim 13, characterized in that at least one processor further receives terminal-specific uplink / downlink TDD settings.

24. A terminal characterized in that, in paragraph 23, if at least one symbol among the symbols allocated for PUSCH transmission in a specific slot is set to downlink by the terminal-specific uplink / downlink TDD setting and overlaps with the non-SBFD symbols, the specific slot is excluded from the count of available slots for PUSCH transmission.

25. The device, At least one memory; and At least one processor operably coupled to at least one memory, wherein said at least one memory comprises instructions that are executed by said at least one processor to perform operations, The above actions are, Receive a system information block (SIB), wherein the SIB includes subband full duplex (SBFD) time information that sets the time position of a cell-specific subband full duplex (SBFD) subband, and Receive downlink control information (DCI) including a slot format indicator (SFI) indicating a slot format including downlink symbols, uplink symbols, and flexible symbols, The at least one processor is included in an SBFD aware UE, A device characterized in that the at least one processor applies the SFI only to the non-SBFD symbols among the SBFD symbols and non-SBFD symbols based on the SBFD time information.

26. At least one computer readable medium (CRM) containing instructions based on being executed by at least one processor, Receive a system information block (SIB), wherein the SIB includes subband full duplex (SBFD) time information that sets the time position of a cell-specific subband full duplex (SBFD) subband, and Receive downlink control information (DCI) including a slot format indicator (SFI) indicating a slot format including downlink symbols, uplink symbols, and flexible symbols, The at least one processor is included in an SBFD aware UE, A CRM characterized in that the at least one processor applies the SFI only to the non-SBFD symbols among the SBFD symbols and non-SBFD symbols based on the SBFD time information.

27. In the method, A base station transmits a system information block (SIB), wherein the SIB includes subband full duplex (SBFD) time information that sets the time position of a cell-specific subband full duplex (SBFD) subband, and The base station transmits downlink control information (DCI) including a slot format indicator (SFI) indicating a slot format including downlink symbols, uplink symbols, and flexible symbols to an SBFD aware UE, A method characterized in that the base station communicates with the SBFD-aware terminal based on the application of the SFI only to the non-SBFD symbols among the SBFD symbols and non-SBFD symbols based on the SBFD time information.

28. The base station, At least one transceiver; At least one memory; and At least one processor operably coupled with said at least one memory and said at least one transceiver, wherein said at least one memory comprises instructions that are executed by said at least one processor to perform operations, The above actions are, A base station transmits a system information block (SIB), wherein the SIB includes subband full duplex (SBFD) time information that sets the time position of a cell-specific subband full duplex (SBFD) subband, and The base station transmits downlink control information (DCI) including a slot format indicator (SFI) indicating a slot format including downlink symbols, uplink symbols, and flexible symbols to an SBFD aware UE, A base station characterized in that the base station communicates with the SBFD-aware terminal based on the application of the SFI only to the non-SBFD symbols among the SBFD symbols and non-SBFD symbols based on the SBFD time information.

Images