Method and device for transmitting signal in wireless communication system

The method and device optimize signal transmission in 5G wireless communication systems by managing overlapping resources for uplink and downlink channels, addressing interference issues and enhancing efficiency through careful scheduling and resource management.

WO2024237421A1PCT designated stage expired Publication Date: 2024-11-21WILUS INSTITUTE OF STANDARDS & TECHNOLOGY INC
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2024/000338
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-07-26
Filing Date
2024-01-08
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

Current wireless communication systems face challenges in efficiently transmitting and receiving signals, particularly in 5G networks, due to overlapping resources in the time domain for physical uplink and downlink shared channels, which can lead to interference and reduced performance.

Method used

A method and device that manage the transmission and reception of signals by using configuration information to schedule physical uplink shared channel (PUSCH) resources within specific bandwidth parts, where resources for PUSCH are scheduled to avoid overlap with physical downlink shared channel (PDSCH) resources, and include timeline conditions for the interval between CORESET#0 reception and PUSCH transmission, allowing for partial or complete cancellation of PUSCH transmission as needed.

Benefits of technology

This approach enhances signal transmission efficiency by minimizing interference and optimizing resource allocation, thereby improving the overall performance and reliability of wireless communication systems, especially in 5G networks with high data traffic demands.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2024000338_21112024_PF_FP_ABST
    Figure KR2024000338_21112024_PF_FP_ABST
Patent Text Reader

Abstract

The present invention relates to a wireless communication system and, more particularly, to a method and a wireless device therefor, the method comprising the steps of: receiving configuration information about a CORESET#0 via an SS / PBCH; and receiving DCI including resource allocation information about a PDSCH in the CORESET#0, wherein if (i) a PUSCH is scheduled within an uplink subband in a BWP, and (ii) the PUSCH overlaps with the PDSCH in a time domain, transmission of the PUSCH is either carried out or canceled on the basis of a condition, wherein the condition includes a timeline condition related to an interval between the CORESET#0 and the PUSCH.
Need to check novelty before this filing date? Find Prior Art

Description

Method and device for transmitting signals in a wireless communication system

[0001] The present invention relates to a wireless communication system. Specifically, the present invention relates to a method for transmitting a signal in a wireless communication system and a device utilizing the same.

[0002] Since the commercialization of 4G (4th generation) communication systems, efforts are being made to develop new 5G (5th generation) communication systems to meet the growing demand for wireless data traffic. 5G communication systems are also referred to as "beyond 4G network" communication systems, "post-LTE" systems, or "new radio" (NR) systems. To achieve high data rates, 5G communication systems include systems operating in the ultra-high frequency (mmWave) band above 6 GHz. Furthermore, for coverage purposes, systems operating in frequency bands below 6 GHz are being considered for implementation at base stations and terminals.

[0003] The 3rd Generation Partnership Project (3GPP) NR system improves network spectral efficiency, enabling carriers to offer more data and voice services within a given bandwidth. Therefore, the 3GPP NR system is designed to meet the demands for high-speed data and media transmission in addition to high-capacity voice support. The advantages of the NR system include high throughput, low latency, support for frequency division duplex (FDD) and time division duplex (TDD) on the same platform, an improved end-user experience, and lower operating costs due to its simple architecture.

[0004] For more efficient data processing, dynamic TDD in NR systems can vary the number of orthogonal frequency division multiplexing (OFDM) symbols available for uplink and downlink transmissions depending on the data traffic direction of users in the cell. For example, when a cell's downlink traffic exceeds its uplink traffic, the base station can allocate multiple downlink OFDM symbols to a slot (or subframe). Information about the slot configuration must be transmitted to terminals.

[0005] To mitigate the path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, beamforming, massive MIMO (massive MIMO), full dimensional MIMO (FD-MIMO), array antenna, analog beamforming, hybrid beamforming that combines analog beamforming and digital beamforming, and large scale antenna technologies are being discussed in 5G communication systems. Additionally, to improve the network of the system, 5G communication systems are developing technologies for advanced small cells, advanced small cells, cloud radio access networks (cloud RAN), ultra-dense networks, device to device communication (D2D), vehicle to everything communication (V2X), wireless backhaul, non-terrestrial network communication (NTN), moving networks, cooperative communication, coordinated multi-points (CoMP), and interference cancellation.In addition, advanced coding modulation (ACM) methods such as hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC), as well as advanced access technologies such as filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA), are being developed in 5G systems.

[0006] Meanwhile, the Internet is evolving from a human-centric network where humans create and consume information to the Internet of Things (IoT), where information is exchanged and processed between distributed components such as objects. The Internet of Everything (IoE), which combines IoT technologies with big data processing technologies through connections to cloud servers, is also emerging. To implement the IoT, technological elements such as sensing technology, wired and wireless communication and network infrastructure, service interface technology, and security technology are required. Recently, research is being conducted on technologies such as sensor networks, machine-to-machine (M2M) communication, and machine-type communication (MTC) for connecting objects. In the IoT environment, intelligent IT (Internet technology) services can be provided that collect and analyze data generated from connected objects to create new value for human life. IoT can be applied to areas such as smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart appliances, and advanced medical services through the convergence and integration of existing IT (information technology) technologies with various industries.

[0007] Accordingly, various attempts are being made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine-to-machine (M2M), and machine-type communication (MTC) are being implemented using 5G communication techniques such as beamforming, MIMO, and array antennas. Cloud RAN, a big data processing technology described above, can also be considered an example of the convergence of 5G and IoT technologies. Mobile communication systems have traditionally been developed to provide voice services while ensuring user activity.

[0008] However, mobile communication systems are gradually expanding beyond voice to include data services, and have now evolved to the point where they can provide high-speed data services. However, resource shortages and user demand for high-speed services in existing mobile communication systems are driving the need for more advanced systems.

[0009] The purpose of the present invention is to provide a method for efficiently transmitting and receiving a signal in a wireless communication system and a device using the same.

[0010] In one aspect of the present invention, a terminal used in a wireless communication system is provided, comprising: a communication module; and a processor controlling the communication module, wherein the processor is configured to receive configuration information regarding reception of a CORESET (control resource set)#0 through reception of an SS / PBCH (synchronization signal / physical broadcast channel) block, and to receive DCI (downlink control information) including resource allocation information for receiving a PDSCH (physical downlink shared channel) through reception of the CORESET#0, wherein (i) transmission of a PUSCH (physical uplink shared channel) is scheduled within an uplink subband within a BWP (bandwidth part), and (ii) when a resource for transmitting the PUSCH overlaps with a resource for receiving the PDSCH in a time domain, transmission of the PUSCH is performed or canceled according to a condition, and the condition includes a timeline condition related to an interval between a resource for receiving the CORESET#0 and a resource for transmitting the PUSCH.

[0011] In another aspect of the present invention, a method used by a terminal in a wireless communication system is provided, comprising: receiving configuration information regarding reception of a CORESET (control resource set)#0 through reception of an SS / PBCH (synchronization signal / physical broadcast channel) block; and receiving DCI (downlink control information) including resource allocation information for receiving a PDSCH (physical downlink shared channel) through reception of the CORESET#0, wherein (i) transmission of a PUSCH (physical uplink shared channel) is scheduled within an uplink subband within a BWP (bandwidth part), and (ii) when a resource for transmitting the PUSCH overlaps with a resource for receiving the PDSCH in a time domain, transmission of the PUSCH is transmitted or canceled according to a condition, and the condition includes a timeline condition related to an interval between a resource for receiving the CORESET#0 and a resource for transmitting the PUSCH.

[0012] In another aspect of the present invention, a base station used in a wireless communication system is provided, comprising: a communication module; and a processor controlling the communication module, wherein the processor is configured to transmit configuration information regarding transmission of a CORESET (control resource set)#0 through transmission of an SS / PBCH (synchronization signal / physical broadcast channel) block, and to transmit downlink control information (DCI) including resource allocation information for transmitting a PDSCH (physical downlink shared channel) through transmission of the CORESET#0, wherein (i) reception of a PUSCH (physical uplink shared channel) is scheduled within an uplink subband within a BWP (bandwidth part), and (ii) when a resource for receiving the PUSCH overlaps with a resource for transmitting the PDSCH in a time domain, reception of the PUSCH is performed or canceled according to a condition, and the condition includes a timeline condition related to an interval between a resource for transmitting the CORESET#0 and a resource for receiving the PUSCH.

[0013] In another aspect of the present invention, a method used by a base station in a wireless communication system is provided, comprising: transmitting configuration information regarding transmission of a CORESET (control resource set)#0 through transmission of an SS / PBCH (synchronization signal / physical broadcast channel) block; and transmitting downlink control information (DCI) including resource allocation information for transmitting a PDSCH (physical downlink shared channel) through transmission of the CORESET#0, wherein (i) reception of a PUSCH (physical uplink shared channel) is scheduled within an uplink subband within a BWP (bandwidth part), and (ii) when a resource for receiving the PUSCH overlaps with a resource for transmitting the PDSCH in a time domain, reception of the PUSCH is performed or canceled according to a condition, and the condition includes a timeline condition related to an interval between a resource for transmitting the CORESET#0 and a resource for receiving the PUSCH.

[0014] Preferably, the timeline condition may include that the start symbol for transmitting the PUSCH is located at least a PUSCH preparation time later than the last symbol for receiving the CORESET#0.

[0015] Preferably, when the above timeline condition is satisfied, the transmission of the PUSCH can be canceled in all resources for transmitting the PUSCH.

[0016] Preferably, when the above timeline condition is satisfied, transmission of the PUSCH may be partially cancelled in symbols overlapping with symbols for receiving the PDSCH and in symbols overlapping with gap symbols following symbols for receiving the PDSCH.

[0017] Preferably, if the above timeline condition is not satisfied, transmission of the PUSCH can be performed on all resources for transmitting the PUSCH.

[0018] Preferably, the condition may further include whether the PUSCH is a DG (dynamic grant) PUSCH or a CG (configured grant) PUSCH.

[0019] Preferably, the condition may further include whether the terminal has indicated PUSCH-partialCancellation capability to the base station.

[0020] The present invention provides a method for efficiently transmitting and receiving a signal in a wireless communication system and a device using the same.

[0021] The effects that can be obtained from the present invention are not limited to the effects mentioned above, and other effects not mentioned can be clearly understood by a person having ordinary skill in the art to which the present invention belongs from the description below.

[0022] Figure 1 shows an example of a radio frame structure used in a wireless communication system.

[0023] Figure 2 shows an example of a downlink (DL) / uplink (UL) slot structure in a wireless communication system.

[0024] Figure 3 is a drawing for explaining a physical channel used in a 3GPP system and a general signal transmission method using the physical channel.

[0025] Figures 4a and 4b illustrate SS / PBCH blocks for initial cell access in a 3GPP NR system.

[0026] Figures 5a and 5b illustrate procedures for transmitting control information and control channels in a 3GPP NR system.

[0027] Figure 6 is a diagram showing a CORESET (control resource set) in which a PDCCH (physical downlink control channel) can be transmitted in a 3GPP NR system.

[0028] FIG. 7 is a diagram illustrating a method for setting a PDCCH search space in a 3GPP NR system.

[0029] Figure 8 is a conceptual diagram explaining carrier aggregation.

[0030] Figure 9 is a diagram for explaining single carrier communication and multi-carrier communication.

[0031] Figure 10 is a diagram illustrating an example in which a cross-carrier scheduling technique is applied.

[0032] Figure 11 is a block diagram showing the configuration of a terminal and a base station according to one embodiment of the present invention.

[0033] Figures 12 to 14 illustrate a method for setting subbands.

[0034] Figures 15 to 18 illustrate an uplink transmission method according to an example of the present invention.

[0035] Figure 19 illustrates the multiplexing pattern of SSB & CORESET0.

[0036] Figures 20 to 24 illustrate an uplink transmission method according to an example of the present invention.

[0037] Figure 25 illustrates a method for setting up CORESET and search space.

[0038] Figure 26 illustrates a problem when a terminal supporting SBFD (non-overlapping subband full duplex) operation receives a PDCCH.

[0039] Figures 27 and 28 illustrate a method for a terminal supporting SBFD operation according to an example of the present invention to set up a CORESET and a search space.

[0040] FIG. 29 illustrates a method for a terminal supporting a BFD operation according to an example of the present invention to determine CCE-to-REG (control channel element to resource element group) mapping to receive a PDCCH.

[0041] The terms used in this specification have been selected from widely used and current terms, taking into account the functions of the present invention. However, these terms may vary depending on the intentions of those skilled in the art, customs, or the emergence of new technologies. Furthermore, in certain cases, the applicant may arbitrarily select terms, in which case their meanings will be described in the description of the relevant invention. Therefore, it should be noted that the terms used in this specification should be interpreted based on their substantive meaning and the overall content of this specification, rather than simply their names.

[0042] Throughout the specification, when a component is said to be "connected" to another component, this includes not only the case where the component is "directly connected," but also the case where the component is "electrically connected" with another component intervening therebetween. Furthermore, when a component is said to "include" a particular component, this does not exclude the other component, but rather allows the other component to be included, unless otherwise specifically stated. Furthermore, the terms "more than" or "less than" based on a specific threshold may be appropriately replaced with "more than" or "less than", respectively, depending on the embodiment.

[0043] The following technologies can be used in various wireless access systems, such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access). CDMA can be implemented with radio technologies such as UTRA (Universal Terrestrial Radio Access) or CDMA2000. TDMA can be implemented with radio technologies such as GSM (Global System for Mobile communications) / GPRS (General Packet Radio Service) / EDGE (Enhanced Data Rates for GSM Evolution). OFDMA can be implemented with radio technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and E-UTRA (Evolved UTRA). UTRA is a part of UMTS (Universal Mobile Telecommunications System). 3GPP (3rd Generation Partnership Project) LTE (long term evolution) is a part of E-UMTS (Evolved UMTS) that uses E-UTRA, and LTE-A (Advanced) is an evolved version of 3GPP LTE.3GPP NR (New Radio) is a system designed separately from LTE / LTE-A to support enhanced Mobile Broadband (eMBB), Ultra-Reliable and Low Latency Communication (URLLC), and massive Machine Type Communication (mMTC) services, which are requirements of IMT-2020. For clarity, the following description focuses on 3GPP NR, but the technical concepts of the present invention are not limited thereto.

[0044] Unless otherwise specified herein, a base station may include a gNB (next generation node B) defined in 3GPP NR. In addition, unless otherwise specified, a terminal may include a UE (user equipment). Hereinafter, to facilitate understanding of the description, each content is described separately as an embodiment, but each embodiment may be used in combination with each other. In the present disclosure, the configuration of a terminal may refer to a configuration by a base station. Specifically, the base station may transmit a channel or signal to the terminal to set the values ​​of parameters used in the operation of the terminal or in a wireless communication system.

[0045] Figure 1 shows an example of a radio frame structure used in a wireless communication system.

[0046] Referring to Figure 1, the radio frame (or radio frame) used in the 3GPP NR system is 10ms (Δf max N f / 100) * T c ) can have a length of . In addition, a radio frame consists of 10 equally sized subframes (SF). Here, Δf max =480*10 3 Hz, N f =4096, T c =1 / (Δfref *N f,ref ), Δf ref =15*10 3 Hz, N f,ref =2048. Each of the 10 subframes within a radio frame can be numbered from 0 to 9. Each subframe has a length of 1ms and can be composed of one or more slots depending on the subcarrier spacing. More specifically, the subcarrier spacing that can be used in the 3GPP NR system is 15*2. μ kHz. μ is the subcarrier spacing configuration, and μ can have a value of 0 to 4. That is, 15 kHz, 30 kHz, 60 kHz, 120 kHz, or 240 kHz can be used as the subcarrier spacing. A 1 ms long subframe is 2 μ It can be composed of slots, where the length of each slot is 2 -μ ms. 2 within one subframe μ The slots of each dog are numbered from 0 to 2 μ - Numbers from 1 to 1 can be assigned. Also, slots within a radio frame are numbered from 0 to 10*2. μ - A number up to 1 may be assigned. Time resources may be distinguished by at least one of a radio frame number (also called a radio frame index), a subframe number (also called a subframe index), and a slot number (or slot index).

[0047] Figure 2 illustrates an example of a downlink (DL) / uplink (UL) slot structure in a wireless communication system. In particular, Figure 2 illustrates the structure of a resource grid of a 3GPP NR system.

[0048] There is one resource grid per antenna port. Referring to Fig. 2, a slot includes multiple OFDM (orthogonal frequency division multiplexing) symbols in the time domain and multiple resource blocks (RBs) in the frequency domain. An OFDM symbol also means one symbol period. Unless otherwise specified, an OFDM symbol may be simply referred to as a symbol. One RB includes 12 consecutive subcarriers in the frequency domain. Referring to Fig. 2, a signal transmitted in each slot is N size,μ grid,x * N RB sc N subcarriers and slot symb It can be expressed as a resource grid consisting of OFDM symbols. Here, when it is a downlink resource grid, x = DL, and when it is an uplink resource grid, x = UL. N size,μ grid,x represents the number of resource blocks (RBs) according to the subcarrier spacing configuration factor μ (x is DL or UL), and N slot symb represents the number of OFDM symbols in a slot. N RB sc N is the number of subcarriers that constitute one RB. RB sc =12. Depending on the multiple access method, an OFDM symbol may be referred to as a CP-OFDM (cyclic prefix OFDM) symbol or a DFT-S-OFDM (discrete Fourier transform spread OFDM) symbol.

[0049] The number of OFDM symbols included in one slot may vary depending on the length of the CP (cyclic prefix). For example, in the case of a normal CP, one slot may include 14 OFDM symbols, but in the case of an extended CP, one slot may include 12 OFDM symbols. In a specific embodiment, the extended CP may be used only at a 60 kHz subcarrier spacing. In Fig. 2, for convenience of explanation, a case in which one slot consists of 14 OFDM symbols is exemplified, but embodiments of the present invention may be applied in the same manner to slots having a different number of OFDM symbols. Referring to Fig. 2, each OFDM symbol is, in the frequency domain, N size,μ grid,x * N RB sc It contains subcarriers. The types of subcarriers can be divided into data subcarriers for data transmission, reference signal subcarriers for reference signal transmission, and guard bands. The carrier frequency is also called the center frequency (fc).

[0050] One RB is N in the frequency domain. RB sc can be defined by a number of consecutive subcarriers (e.g., 12). For reference, a resource consisting of one OFDM symbol and one subcarrier can be referred to as a resource element (RE) or tone. Therefore, one RB is N slot symb * N RB sc It can be composed of resource elements. Each resource element within the resource grid can be uniquely defined by an index pair (k, l) within one slot. k is from 0 to N in the frequency domain. size,μ grid, x * N RBsc - An index is given from 1, and l is from 0 to N in the time domain. slot symb - It can be an index assigned up to 1.

[0051] For a terminal to receive signals from or transmit signals to a base station, its time / frequency synchronization may need to be aligned with that of the base station. Only when the base station and terminal are synchronized can the terminal determine the time and frequency parameters necessary to accurately demodulate DL signals and transmit UL signals.

[0052] Each symbol of a radio frame operating in time division duplex (TDD) or an unpaired spectrum can be composed of at least one of a downlink symbol (DL symbol), an uplink symbol (UL symbol), or a flexible symbol. A radio frame operating as a downlink carrier in frequency division duplex (FDD) or a paired spectrum can be composed of downlink symbols or flexible symbols, and a radio frame operating as an uplink carrier can be composed of uplink symbols or flexible symbols. Downlink transmission is possible in a downlink symbol but uplink transmission is not possible, and uplink transmission is possible in an uplink symbol but downlink transmission is not possible. A flexible symbol can be determined to be used for downlink or uplink depending on a signal.

[0053] Information about the type of each symbol, i.e., information indicating either a downlink symbol, an uplink symbol, or a flexible symbol, may be configured as a cell-specific (or common) radio resource control (RRC) signal. In addition, information about the type of each symbol may be additionally configured as a UE-specific (or dedicated) RRC signal. The base station uses the cell-specific RRC signal to indicate i) the period of the cell-specific slot configuration, ii) the number of slots containing only downlink symbols from the beginning of the period of the cell-specific slot configuration, iii) the number of downlink symbols from the first symbol of the slot immediately following the slot containing only downlink symbols, iv) the number of slots containing only uplink symbols from the end of the period of the cell-specific slot configuration, and v) the number of uplink symbols from the last symbol of the slot immediately preceding the slot containing only uplink symbols. Here, a symbol that is not composed of either an uplink symbol or a downlink symbol is a flexible symbol.

[0054] When information about the symbol type is configured as a terminal-specific RRC signal, the base station can signal whether the flexible symbol is a downlink symbol or an uplink symbol using a cell-specific RRC signal. At this time, the terminal-specific RRC signal cannot change the downlink symbol or uplink symbol configured as the cell-specific RRC signal to a different symbol type. The terminal-specific RRC signal is configured for each slot to be N of the corresponding slot. slot symb Number of downlink symbols in the symbol slot, N slot symbThe number of uplink symbols in the symbol can be signaled. At this time, the downlink symbols of the slot can be configured continuously from the first symbol of the slot to the i-th symbol. In addition, the uplink symbols of the slot can be configured continuously from the j-th symbol of the slot to the last symbol (where, i <j). 슬롯에서 상향링크 심볼과 하향링크 심볼 어느 것으로도 구성되지 않은 심볼은 플렉서블 심볼이다.

[0055] FIG. 3 is a diagram illustrating a physical channel used in a 3GPP system (e.g., NR) and a general signal transmission method using the physical channel.

[0056] When the terminal powers up or enters a new cell, the terminal performs an initial cell search operation (S101). Specifically, the terminal can synchronize with the base station during the initial cell search. To this end, the terminal receives a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) from the base station to synchronize with the base station and obtain information such as a cell index. Thereafter, the terminal can receive a physical broadcast channel from the base station to obtain broadcast information within the cell.

[0057] A terminal that has completed initial cell search can obtain more specific system information than the system information obtained through initial cell search by receiving a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) according to information carried in the PDCCH (S102). The system information received by the terminal here is cell-common system information for the terminal to operate properly in the physical layer of the RRC (Radio Resource Control, RRC), and is referred to as remaining system information or system information block (SIB) 1.

[0058] When a terminal accesses a base station for the first time or there are no radio resources for signal transmission (when the terminal is in RRC_IDLE mode), the terminal may perform a random access procedure for the base station (steps S103 to S106). First, the terminal transmits a preamble through a physical random access channel (PRACH) (S103) and may receive a response message to the preamble from the base station through a PDCCH and a corresponding PDSCH (S104). When a valid random access response message is received by the terminal, the terminal transmits data, including its identifier, to the base station through a physical uplink shared channel (PUSCH) indicated in an uplink grant transmitted from the base station through the PDCCH (S105). Next, the terminal waits for reception of the PDCCH as an instruction from the base station to resolve collisions. When the terminal successfully receives the PDCCH through its identifier (S106), the random access procedure is terminated. During the random access process, the terminal can obtain terminal-specific system information required for proper operation from the RRC layer to the physical layer. Once the terminal obtains terminal-specific system information from the RRC layer, the terminal enters RRC connected mode (RRC_CONNECTED mode).

[0059] The RRC layer is used to generate and manage messages for control between terminals and the Radio Access Network (RAN). More specifically, the base station and terminals can perform broadcasting of cell system information required for all terminals in the cell, management of delivery of paging messages, mobility management and handover, terminal measurement reporting and control thereof, terminal capability management, and storage management including base station management in the RRC layer. In general, since the update of a signal transmitted in the RRC layer (hereinafter, “RRC signal”) is longer than the transmission / reception cycle (i.e., transmission time interval, TTI) in the physical layer, the RRC signal can be maintained without change for a long period.

[0060] After the procedure described above, the terminal can perform the general uplink / downlink signal transmission procedure of receiving PDCCH / PDSCH (S107) and transmitting physical uplink shared channel (PUSCH) / physical uplink control channel (PUCCH) (S108). In particular, the terminal can receive downlink control information (DCI) through the PDCCH. The DCI can include control information such as resource allocation information for the terminal. In addition, the format of the DCI can vary depending on the purpose of use. The uplink control information (UCI) that the terminal transmits to the base station through the uplink can include downlink / uplink ACK / NACK signals, channel quality indicator (CQI), precoding matrix index (PMI), rank indicator (RI), etc. Here, the CQI, PMI, and RI can be included in channel state information (CSI). In the case of a 3GPP NR system, the terminal can transmit control information such as the HARQ-ACK and CSI described above through PUSCH and / or PUCCH.

[0061] Figures 4a and 4b illustrate SS / PBCH blocks for initial cell access in a 3GPP NR system.

[0062] When a terminal is powered on or attempts to connect to a new cell, it can acquire time and frequency synchronization with the cell and perform an initial cell search process. During the cell search process, the terminal obtains the physical cell identity N of the cell. cell IDcan be detected. To this end, the terminal can synchronize with the base station by receiving synchronization signals, such as a primary synchronization signal (PSS) and a secondary synchronization signal (SSS), from the base station. At this time, the terminal can obtain information such as a cell identifier (ID).

[0063] Referring to Fig. 4a, the synchronization signal (SS) will be described in more detail. The synchronization signal can be divided into PSS and SSS. PSS can be used to obtain time-domain synchronization such as OFDM symbol synchronization and slot synchronization and / or frequency-domain synchronization. SSS can be used to obtain frame synchronization and cell group ID. Referring to Fig. 4a and Table 1, an SS / PBCH block can be composed of 20 consecutive RBs (= 240 subcarriers) in the frequency axis and 4 consecutive OFDM symbols in the time axis. At this time, in the SS / PBCH block, the PSS is transmitted through the 56th to 182nd subcarriers in the first OFDM symbol, and the SSS is transmitted through the 56th to 182nd subcarriers in the third OFDM symbol. Here, the lowest subcarrier index of the SS / PBCH block is numbered from 0. In the first OFDM symbol where PSS is transmitted, the base station does not transmit signals through the remaining subcarriers, i.e., subcarriers 0 to 55 and 183 to 239. Furthermore, in the third OFDM symbol where SSS is transmitted, the base station does not transmit signals through subcarriers 48 to 55 and 183 to 191. The base station transmits the PBCH (physical broadcast channel) through the remaining REs in the SS / PBCH block, excluding the above signals.

[0064] [Correction pursuant to Rule 91, March 13, 2024]

[0065] The SS can be grouped into 336 physical-layer cell-identifier groups, each group containing three unique identifiers, such that each physical-layer cell ID is part of only one physical-layer cell-identifier group, for a total of 1008 unique physical-layer cell IDs through a combination of three PSSs and SSSs. Therefore, the physical-layer cell ID N cell ID = 3N (1) ID + N (2) ID An index N in the range 0 to 335 representing a group of physical-layer cell identifiers. (1) ID and an index N from 0 to 2 representing the physical-layer identifier within the physical-layer cell-identifier group. (2) ID can be uniquely defined by. The terminal can detect the PSS to identify one of three unique physical-layer identifiers. In addition, the terminal can detect the SSS to identify one of 336 physical-layer cell IDs associated with the physical-layer identifier. At this time, the sequence d of the PSS PSS (n) is as follows.

[0066] [Correction pursuant to Rule 91, March 13, 2024]

[0067] [Correction under Rule 91 13.03.2024] Here, And,

[0068] [Correction pursuant to Rule 91, March 13, 2024] is given as

[0069] Also, the sequence d of SSS SSS (n) is as follows.

[0070] [Correction pursuant to Rule 91, March 13, 2024]

[0071] [Correction under Rule 91 13.03.2024] Here, And,

[0072] [Correction pursuant to Rule 91, March 13, 2024] is given as

[0073] A 10ms long radio frame can be divided into two half frames each of 5ms long. Referring to Fig. 4b, the slots in which SS / PBCH blocks are transmitted within each half frame are described. The slots in which SS / PBCH blocks are transmitted can be any one of Cases A, B, C, D, and E. In Case A, the subcarrier spacing is 15kHz, and the starting point of the SS / PBCH block is the {2, 8} + 14*nth symbol. At this time, n can be 0 or 1 for carrier frequencies below 3GHz. In addition, n can be 0, 1, 2, or 3 for carrier frequencies exceeding 3GHz and below 6GHz. In Case B, the subcarrier spacing is 30kHz, and the starting point of the SS / PBCH block is the {4, 8, 16, 20} + 28*nth symbol. At this time, n can be 0 for carrier frequencies below 3GHz. Also, n can be 0, 1 at a carrier frequency exceeding 3 GHz and below 6 GHz. In case C, the subcarrier spacing is 30 kHz, and the starting point of the SS / PBCH block is the {2, 8} + 14*nth symbol. At this time, n can be 0, 1 at a carrier frequency below 3 GHz. Also, n can be 0, 1, 2, 3 at a carrier frequency exceeding 3 GHz and below 6 GHz. In case D, the subcarrier spacing is 120 kHz, and the starting point of the SS / PBCH block is the {4, 8, 16, 20} + 28*nth symbol. At this time, n can be 0, 1, 2, 3, 5, 6, 7, 8, 10, 11, 12, 13, 15, 16, 17, 18 at a carrier frequency above 6 GHz. In Case E, the subcarrier spacing is 240 kHz, and the starting point of the SS / PBCH block is {8, 12, 16, 20, 32, 36, 40, 44} + 56*nth symbol. At this time, n can be 0, 1, 2, 3, 5, 6, 7, or 8 for carrier frequencies above 6 GHz.

[0074] Figures 5a and 5b illustrate a procedure for transmitting control information and a control channel in a 3GPP NR system. Referring to Figure 5a, a base station may add a CRC (cyclic redundancy check) masked (e.g., XOR operation) with a radio network temporary identifier (RNTI) to control information (e.g., downlink control information, DCI) (S202). The base station may scramble the CRC with an RNTI value determined according to the purpose / target of each control information. A common RNTI used by one or more terminals may include at least one of a system information RNTI (SI-RNTI), a paging RNTI (P-RNTI), a random access RNTI (RA-RNTI), and a transmit power control RNTI (TPC-RNTI). In addition, a terminal-specific RNTI may include at least one of a cell temporary RNTI (C-RNTI) and a CS-RNTI. Afterwards, the base station can perform rate matching according to the amount of resource(s) used for PDCCH transmission after performing channel encoding (e.g., polar coding) (S204). Afterwards, the base station can multiplex DCI(s) based on a PDCCH structure based on CCE (control channel element) (S208). In addition, the base station can apply additional processes such as scrambling, modulation (e.g., QPSK), and interleaving (S210) to the multiplexed DCI(s) and then map them to resources to be transmitted. CCE is a basic resource unit for PDCCH, and one CCE can be composed of multiple (e.g., 6) REGs (resource element groups). One REG can be composed of multiple (e.g., 12) REs.The number of CCEs used for a single PDCCH can be defined as an aggregation level. In a 3GPP NR system, aggregation levels of 1, 2, 4, 8, or 16 can be used. Figure 5b is a diagram regarding CCE aggregation levels and PDCCH multiplexing, showing the types of CCE aggregation levels used for a single PDCCH and the CCE(s) transmitted in the control domain accordingly.

[0075] Figure 6 is a diagram showing a CORESET (control resource set) in which a PDCCH (physical downlink control channel) can be transmitted in a 3GPP NR system.

[0076] A CORESET is a time-frequency resource where the PDCCH, a control signal for a terminal, is transmitted. Furthermore, a search space, described below, can be mapped to a single CORESET. Therefore, rather than monitoring the entire frequency band for PDCCH reception, a terminal can monitor the time-frequency domain designated by the CORESET and decode the PDCCH mapped to the CORESET. A base station can configure one or more CORESETs for each cell for the terminal. A CORESET can consist of up to three consecutive symbols along the time axis. Furthermore, a CORESET can be configured in units of six consecutive PRBs along the frequency axis. In the embodiment of FIG. 6, CORESET#1 consists of consecutive PRBs, and CORESET#2 and CORESET#3 consist of non-consecutive PRBs. A CORESET can be located in any symbol within a slot. For example, in the embodiment of FIG. 6, CORESET#1 starts at the first symbol of the slot, CORESET#2 starts at the fifth symbol of the slot, and CORESET#9 starts at the ninth symbol of the slot.

[0077] FIG. 7 is a diagram illustrating a method for setting a PDCCH search space in a 3GPP NR system.

[0078] In order to transmit a PDCCH to a terminal, each CORESET may have at least one search space. In an embodiment of the present invention, the search space is a set of all time-frequency resources (hereinafter, PDCCH candidates) on which the PDCCH of the terminal can be transmitted. The search space may include a common search space that 3GPP NR terminals must commonly search and a terminal-specific or UE-specific search space that a specific terminal must search. In the common search space, a PDCCH that is commonly set for all terminals in a cell belonging to the same base station can be monitored. In addition, a terminal-specific search space may be set for each terminal so that the PDCCH allocated to each terminal can be monitored at different search space locations depending on the terminal. In the case of a terminal-specific search space, the search spaces between terminals may be allocated to partially overlap due to the limited control region to which the PDCCH can be allocated. Monitoring PDCCHs involves blindly decoding PDCCH candidates within the search space. Successful blind decoding is referred to as "successful detection / reception of the PDCCH." Failure to do so is referred to as "non-detection / non-reception of the PDCCH," or "non-successful detection / reception."

[0079] For convenience of explanation, a PDCCH scrambled with a group common (GC) RNTI that one or more terminals already know in order to transmit downlink control information to one or more terminals is referred to as a group common (GC) PDCCH or common PDCCH. In addition, a PDCCH scrambled with a terminal-specific RNTI that a specific terminal already knows in order to transmit uplink scheduling information or downlink scheduling information to a specific terminal is referred to as a terminal-specific PDCCH. The common PDCCH may be included in a common search space, and the terminal-specific PDCCH may be included in either the common search space or the terminal-specific PDCCH.

[0080] The base station can inform each terminal or terminal group of information related to resource allocation of the transmission channel, PCH (paging channel) and DL-SCH (downlink-shared channel) (i.e., DL Grant) or information related to resource allocation of UL-SCH (uplink-shared channel) and HARQ (hybrid automatic repeat request) (i.e., UL Grant) through PDCCH. The base station can transmit PCH transport blocks and DL-SCH transport blocks through PDSCH. The base station can transmit data excluding specific control information or specific service data through PDSCH. In addition, the terminal can receive data excluding specific control information or specific service data through PDSCH.

[0081] The base station can transmit information on the PDCCH, including information about which terminal (one or more terminals) the PDSCH data is transmitted to and how the terminal should receive and decode the PDSCH data. For example, assume that the DCI transmitted through a specific PDCCH is CRC-masked with an RNTI called "A", and that the DCI indicates that the PDSCH is allocated to a radio resource (e.g., frequency location) called "B", and indicates transmission format information (e.g., transmission block size, modulation method, coding information, etc.) called "C". The terminal monitors the PDCCH using the RNTI information it has. In this case, if there is a terminal that blindly decodes the PDCCH using the "A" RNTI, the terminal receives the PDCCH and, based on the information in the received PDCCH, receives the PDSCH indicated by "B" and "C".

[0082] Table 2 shows an example of a physical uplink control channel (PUCCH) used in a wireless communication system.

[0083] [Correction pursuant to Rule 91, March 13, 2024]

[0084] PUCCH can be used to transmit the following uplink control information (UCI):

[0085] - SR (Scheduling Request): Information used to request uplink UL-SCH resources.

[0086] - HARQ-ACK: This is a response to the PDCCH (indicating DL SPS release) and / or a response to a downlink transport block (TB) on the PDSCH. HARQ-ACK indicates whether the information transmitted through the PDCCH or PDSCH was successfully received. The HARQ-ACK response includes positive ACK (simply, ACK), negative ACK (hereinafter, NACK), Discontinuous Transmission (DTX), or NACK / DTX. Here, the term HARQ-ACK is used interchangeably with HARQ-ACK / NACK and ACK / NACK. In general, ACK can be expressed with bit value 1, and NACK can be expressed with bit value 0.

[0087] - CSI (Channel State Information): This is feedback information for the downlink channel. It is generated by the terminal based on the CSI-RS (Reference Signal) transmitted by the base station. MIMO (Multiple Input Multiple Output)-related feedback information includes the RI (Rank Indicator) and PMI (Precoding Matrix Indicator). CSI can be divided into CSI Part 1 and CSI Part 2, depending on the information it represents.

[0088] In 3GPP NR systems, five PUCCH formats can be used to support various service scenarios, channel environments, and frame structures.

[0089] PUCCH format 0 is a format that can transmit 1-bit or 2-bit HARQ-ACK information or SR. PUCCH format 0 can be transmitted through 1 or 2 OFDM symbols in the time axis and 1 PRB in the frequency axis. When PUCCH format 0 is transmitted through two OFDM symbols, the same sequence can be transmitted in different RBs in the two symbols. In this case, the sequence can be a sequence cyclically shifted (CS) from the base sequence used in PUCCH format 0. Through this, the terminal can obtain frequency diversity gain. Specifically, the terminal can receive M bit Beat UCI (M bit = 1 or 2) depending on the cyclic shift (CS) value m cs can be determined. In addition, a base sequence of length 12 is given with a CS value m cs A cyclically shifted sequence based on M can be transmitted by mapping it to 12 REs of 1 OFDM symbol and 1 RB. The number of cyclic shifts available to the terminal is 12, and M bit = 1, 1-bit UCI 0 and 1 can be mapped to two cyclically shifted sequences, each with a cyclic shift value difference of 6. In addition, M bit = 2, 2-bit UCI 00, 01, 11, 10 can be mapped to four cyclically shifted sequences, each with a cyclic shift value difference of 3.

[0090] PUCCH format 1 can carry 1-bit or 2-bit HARQ-ACK information or SR. PUCCH format 1 can be transmitted through consecutive OFDM symbols in the time axis and 1 PRB in the frequency axis. Here, the number of OFDM symbols occupied by PUCCH format 1 can be one of 4 to 14. More specifically, M bit= 1 UCI can be modulated with BPSK. The terminal is M bit =2 UCI can be modulated with QPSK (quadrature phase shift keying). A signal is obtained by multiplying a modulated complex valued symbol d(0) by a sequence of length 12. At this time, the sequence may be a base sequence used in PUCCH format 0. The terminal transmits the obtained signal by spreading it with a time-domain OCC (orthogonal cover code) in the even-numbered OFDM symbols to which PUCCH format 1 is assigned. In PUCCH format 1, the maximum number of different terminals multiplexed into the same RB is determined according to the length of the OCC used. A demodulation reference signal (DMRS) can be mapped by spreading it with the OCC in the odd-numbered OFDM symbols of PUCCH format 1.

[0091] PUCCH format 2 can carry UCI exceeding 2 bits. PUCCH format 2 can be transmitted through 1 or 2 OFDM symbols in the time axis and 1 or multiple RBs in the frequency axis. When PUCCH format 2 is transmitted through 2 OFDM symbols, the same sequence can be transmitted through different RBs through the 2 OFDM symbols. Here, the sequence is a plurality of modulated complex symbols d(0), … , d(M symbol -1) can be. Here, M symbol Silver M bit / 2 can be used. This allows the terminal to obtain frequency diversity gain. More specifically, M bit Beat UCI (M bit >2) is bit-level scrambled, QPSK modulated and mapped to RB(s) of one or two OFDM symbol(s), where the number of RB(s) can be between 1 and 16.

[0092] PUCCH format 3 or PUCCH format 4 can carry UCI exceeding 2 bits. PUCCH format 3 or PUCCH format 4 can be transmitted through consecutive OFDM symbols in the time axis and one PRB in the frequency axis. The number of OFDM symbols occupied by PUCCH format 3 or PUCCH format 4 can be one of 4 to 14. Specifically, the terminal can transmit M bit Beat UCI (M bit >2) is modulated with π / 2-BPSK (Binary Phase Shift Keying) or QPSK to produce complex symbols d(0)~d(M symb -1) can be generated. Here, using π / 2-BPSK, M symb =M bit And, if QPSK is used, M symb =M bit / 2. The terminal may not apply block-wise spreading to PUCCH format 3. However, the terminal may apply block-wise spreading to one RB (i.e., 12 subcarriers) using PreDFT-OCC of length 12 so that PUCCH format 4 can have a multiplexing capacity of 2 or 4. The terminal may transmit the spread signal by transmitting precoding (or DFT-precoding) the spread signal and mapping it to each RE.

[0093] At this time, the number of RBs occupied by PUCCH format 2, PUCCH format 3, or PUCCH format 4 can be determined according to the length of UCI transmitted by the terminal and the maximum code rate. If the terminal uses PUCCH format 2, the terminal can transmit HARQ-ACK information and CSI information together through PUCCH. If the number of RBs that the terminal can transmit is greater than the maximum number of RBs available for PUCCH format 2, PUCCH format 3, or PUCCH format 4, the terminal can transmit only the remaining UCI information without transmitting some UCI information according to the priority of the UCI information.

[0094] PUCCH format 1, PUCCH format 3, or PUCCH format 4 can be configured via RRC signaling to indicate frequency hopping within a slot. When frequency hopping is configured, the index of the RB to be frequency hopped can be configured via RRC signaling. When PUCCH format 1, PUCCH format 3, or PUCCH format 4 is transmitted over N OFDM symbols in the time axis, the first hop can have floor(N / 2) OFDM symbols and the second hop can have ceil(N / 2) OFDM symbols.

[0095] PUCCH format 1, PUCCH format 3, or PUCCH format 4 can be configured to be repeatedly transmitted in multiple slots. In this case, the number K of slots in which the PUCCH is repeatedly transmitted can be configured by an RRC signal. The repeatedly transmitted PUCCH must start from the same OFDM symbol in each slot and have the same length. If any OFDM symbol in the slot in which the UE must transmit the PUCCH is indicated as a DL symbol by an RRC signal, the UE may not transmit the PUCCH in that slot and postpone transmission to the next slot.

[0096] Meanwhile, in the 3GPP NR system, a terminal can perform transmission and reception using a bandwidth that is smaller than or equal to the bandwidth of a carrier (or cell). To this end, the terminal can be configured with a bandwidth part (BWP) consisting of a continuous bandwidth of a portion of the carrier's bandwidth. A terminal operating in TDD or an unpaired spectrum can be configured with up to four DL / UL BWP pairs per carrier (or cell). In addition, the terminal can activate one DL / UL BWP pair. A terminal operating in FDD or a paired spectrum can be configured with up to four DL BWPs per downlink carrier (or cell) and up to four UL BWPs per uplink carrier (or cell). The terminal can activate one DL BWP and one UL BWP per carrier (or cell). A terminal may not receive or transmit on time-frequency resources other than the activated BWP. The activated BWP may be referred to as an active BWP.

[0097] A base station can indicate an activated BWP among the configured BWPs of a terminal through downlink control information (DCI). The BWP indicated through the DCI is activated, and other configured BWP(s) are deactivated. In a carrier (or cell) operating in TDD, the base station can include a bandwidth part indicator (BPI) indicating an activated BWP in the DCI scheduling PDSCH or PUSCH to change the DL / UL BWP pair of the terminal. The terminal can receive the DCI scheduling PDSCH or PUSCH and identify the activated DL / UL BWP pair based on the BPI. In a downlink carrier (or cell) operating in FDD, the base station can include a BPI indicating an activated BWP in the DCI scheduling PDSCH to change the DL BWP of the terminal. For an uplink carrier (or cell) operating in FDD, the base station may include a BPI indicating the BWP to be activated in the DCI scheduling the PUSCH to change the UL BWP of the terminal.

[0098] Figure 8 is a conceptual diagram explaining carrier aggregation.

[0099] Carrier aggregation refers to a method in which a wireless communication system utilizes multiple frequency blocks or (logically speaking) cells composed of uplink resources (or component carriers) and / or downlink resources (or component carriers) as a single large logical frequency band, so that the terminal can utilize a wider frequency band. A single component carrier may also be referred to as a PCell (Primary cell), SCell (Secondary Cell), or PScell ​​(Primary SCell). However, for convenience of explanation, the term "component carrier" will be used hereafter.

[0100] Referring to FIG. 8, as an example of a 3GPP NR system, the entire system bandwidth may include up to 16 component carriers, and each component carrier may have a bandwidth of up to 400 MHz. A component carrier may include one or more physically contiguous subcarriers. Although FIG. 8 illustrates that each component carrier has the same bandwidth, this is merely an example, and each component carrier may have a different bandwidth. In addition, although each component carrier is illustrated as being adjacent to each other on the frequency axis, the drawing is illustrated in a logical concept, and each component carrier may be physically adjacent to each other or may be spaced apart from each other.

[0101] Each component carrier may use a different center frequency. Furthermore, a common center frequency may be used for physically adjacent component carriers. In the embodiment of FIG. 8, assuming that all component carriers are physically adjacent, center frequency A may be used for all component carriers. Furthermore, assuming that each component carrier is not physically adjacent, center frequency A and center frequency B may be used for each component carrier.

[0102] When the overall system bandwidth is expanded by carrier aggregation, the frequency band used for communication with each terminal can be defined in component carrier units. Terminal A can use the entire system bandwidth of 100 MHz and performs communication using all five component carriers. Terminals B1 to B5 can use only a 20 MHz bandwidth and perform communication using one component carrier. Terminals C1 and C2 can use a 40 MHz bandwidth and perform communication using two component carriers each. The two component carriers may or may not be logically / physically adjacent. The embodiment of FIG. 8 illustrates a case where terminal C1 uses two non-adjacent component carriers and terminal C2 uses two adjacent component carriers.

[0103] Figure 9 is a diagram for explaining single-carrier communication and multi-carrier communication. In particular, Figure 9 (a) illustrates the subframe structure of a single carrier, and Figure 9 (b) illustrates the subframe structure of a multi-carrier.

[0104] Referring to (a) of Fig. 9, a typical wireless communication system can perform data transmission or reception through one DL band and one corresponding UL band in the case of FDD mode. In another specific embodiment, the wireless communication system can divide a radio frame into an uplink time unit and a downlink time unit in the time domain in the case of TDD mode, and perform data transmission or reception through the uplink / downlink time units. Referring to (b) of Fig. 9, three 20MHz component carriers (CCs) each in the UL and DL can be aggregated to support a bandwidth of 60MHz. Each CC can be adjacent or non-adjacent in the frequency domain. For convenience, Fig. 9 (b) illustrates a case where the bandwidth of the UL CC and the bandwidth of the DL CC are both equal and symmetrical, but the bandwidth of each CC can be determined independently. In addition, asymmetric carrier aggregation is also possible, where the number of UL CCs and the number of DL CCs are different. A DL / UL CC allocated / configured to a specific terminal through RRC can be called the serving DL / UL CC of the specific terminal.

[0105] A base station can communicate with a terminal by activating some or all of the serving CCs of the terminal or deactivating some CCs. The base station can change the CCs to be activated / deactivated and the number of CCs to be activated / deactivated. When the base station allocates available CCs to the terminal in a cell-specific or terminal-specific manner, at least one of the assigned CCs may not be deactivated unless the CC allocation to the terminal is completely reconfigured or the terminal performs a handover. One CC that is not deactivated for the terminal is called a primary CC (PCC) or PCell (primary cell), and the CC that the base station can freely activate / deactivate is called a secondary CC (SCC) or SCell (secondary cell).

[0106] Meanwhile, 3GPP NR uses the concept of a cell to manage radio resources. A cell is defined as a combination of downlink and uplink resources, i.e., a combination of a DL CC and an UL CC. A cell can consist of only DL resources or a combination of DL and UL resources. When carrier aggregation is supported, the linkage between the carrier frequency of the DL resources (or DL ​​CC) and the carrier frequency of the UL resources (or UL CC) can be indicated by system information. The carrier frequency refers to the center frequency of each cell or CC. The cell corresponding to the PCC is referred to as a PCell, and the cell corresponding to the SCC is referred to as an SCell. The carrier corresponding to the PCell in the downlink is a DL PCC, and the carrier corresponding to the PCell in the uplink is a UL PCC. Similarly, the carrier corresponding to the SCell in the downlink is a DL SCC, and the carrier corresponding to the SCell in the uplink is a UL SCC. Depending on the UE's capabilities, the serving cell(s) may consist of one PCell and zero or more SCells. For UEs in RRC_CONNECTED state but without carrier aggregation configured or supporting carrier aggregation, there is only one serving cell consisting of only PCell.

[0107] As mentioned above, the term "cell" used in carrier aggregation is distinct from the term "cell" which refers to a certain geographic area where communication services are provided by a single base station or a single antenna group. That is, a single component carrier may also be referred to as a scheduling cell, a scheduled cell, a PCell (Primary cell), a SCell (Secondary Cell), or a PScell ​​(Primary SCell). However, in order to distinguish between a cell referring to a certain geographic area and a cell of carrier aggregation, the present invention refers to a cell of carrier aggregation as a CC, and a cell of a geographic area as a cell.

[0108] Figure 10 is a diagram illustrating an example in which a cross-carrier scheduling technique is applied. When cross-carrier scheduling is configured, a control channel transmitted through a first CC can schedule a data channel transmitted through the first CC or the second CC using a carrier indicator field (CIF). The CIF is included in the DCI. In other words, a scheduling cell is configured, and a DL grant / UL grant transmitted in the PDCCH region of the scheduling cell schedules the PDSCH / PUSCH of the scheduled cell. In other words, a search region for multiple component carriers exists in the PDCCH region of the scheduling cell. The PCell is basically a scheduling cell, and a specific SCell can be designated as a scheduling cell by a higher layer.

[0109] In the embodiment of FIG. 10, it is assumed that three DL CCs are merged. Here, DL component carrier #0 is assumed to be a DL PCC (or PCell), and DL component carrier #1 and DL component carrier #2 are assumed to be DL SCCs (or SCells). In addition, it is assumed that the DL PCC is configured as a PDCCH monitoring CC. If cross-carrier scheduling is not configured by UE-specific (or UE-group-specific or cell-specific) upper layer signaling, CIF is disabled, and each DL CC can transmit only a PDCCH that schedules its own PDSCH without a CIF according to the NR PDCCH rule (non-cross-carrier scheduling, self-carrier scheduling). On the other hand, when cross-carrier scheduling is configured by terminal-specific (or terminal-group-specific or cell-specific) upper layer signaling, CIF is enabled, and a specific CC (e.g., DL PCC) can transmit not only the PDCCH scheduling the PDSCH of DL CC A but also the PDCCH scheduling the PDSCH of other CCs using CIF (cross-carrier scheduling). On the other hand, PDCCH is not transmitted in other DL CCs. Therefore, depending on whether cross-carrier scheduling is configured for the terminal, the terminal monitors the PDCCH that does not include CIF to receive a self-carrier scheduled PDSCH, or monitors the PDCCH that includes CIF to receive a cross-carrier scheduled PDSCH.

[0110] Meanwhile, although FIGS. 9 and 10 illustrate the subframe structure of a 3GPP LTE-A system, the same or similar configuration can also be applied to a 3GPP NR system. However, in a 3GPP NR system, the subframes of FIGS. 9 and 10 can be replaced with slots.

[0111] Figure 11 is a block diagram showing the configuration of a terminal and a base station according to one embodiment of the present invention.

[0112] In embodiments of the present invention, a terminal may be implemented as various types of wireless communication devices or computing devices that ensure portability and mobility. The terminal may be referred to as a UE (User Equipment), STA (Station), MS (Mobile Subscriber), etc. In addition, in embodiments of the present invention, a base station may control and manage cells (e.g., macro cells, femto cells, pico cells, etc.) corresponding to a service area, and perform functions such as signal transmission, channel designation, channel monitoring, self-diagnosis, and relay. The base station may be referred to as a gNB (next generation NodeB) or an AP (access point).

[0113] As illustrated, a terminal (100) according to one embodiment of the present invention may include a processor (110), a communication module (120), a memory (130), a user interface unit (140), and a display unit (150).

[0114] First, the processor (110) can execute various commands or programs and process data within the terminal (100). In addition, the processor (110) can control the overall operation of the terminal (100), including each unit, and control data transmission and reception between the units. Here, the processor (110) can be configured to perform operations according to the embodiments described in the present invention. For example, the processor (110) can receive slot configuration information, determine the slot configuration based on the information, and perform communication according to the determined slot configuration.

[0115] Next, the communication module (120) may be an integrated module that performs wireless communication using a wireless communication network and wireless LAN access using a wireless LAN. To this end, the communication module (120) may be equipped with a plurality of network interface cards (NICs) in built-in or external form, such as a cellular communication interface card (121, 122) and an unlicensed band communication interface card (123). Although the communication module (120) is illustrated as an integrated module in the drawing, each network interface card may be independently arranged depending on the circuit configuration or purpose, unlike the drawing.

[0116] The cellular communication interface card (121) can transmit and receive wireless signals with at least one of a base station (200), an external device, and a server using a mobile communication network, and can provide a cellular communication service by a first frequency band based on a command of the processor (110). According to one embodiment, the cellular communication interface card (121) can include at least one NIC module that uses a frequency band lower than 6 GHz. At least one NIC module of the cellular communication interface card (121) can independently perform cellular communication with at least one of the base station (200), an external device, and a server according to a cellular communication standard or protocol of a frequency band lower than 6 GHz supported by the corresponding NIC module.

[0117] The cellular communication interface card (122) may transmit and receive wireless signals with at least one of a base station (200), an external device, and a server using a mobile communication network, and may provide a cellular communication service by a second frequency band based on a command of the processor (110). According to one embodiment, the cellular communication interface card (122) may include at least one NIC module that uses a frequency band of 6 GHz or higher. At least one NIC module of the cellular communication interface card (122) may independently perform cellular communication with at least one of the base station (200), an external device, and a server according to a cellular communication standard or protocol of a frequency band of 6 GHz or higher supported by the corresponding NIC module.

[0118] The unlicensed band communication interface card (123) transmits and receives wireless signals with at least one of a base station (200), an external device, and a server using the third frequency band, which is an unlicensed band, and provides an unlicensed band communication service based on a command of the processor (110). The unlicensed band communication interface card (123) may include at least one NIC module that uses an unlicensed band. For example, the unlicensed band may be a band of 2.4 GHz, 5 GHz, 6 GHz, 7 GHz, or 52.6 GHz or higher. At least one NIC module of the unlicensed band communication interface card (123) may independently or dependently perform wireless communication with at least one of the base station (200), an external device, and a server according to an unlicensed band communication standard or protocol of a frequency band supported by the corresponding NIC module.

[0119] Next, the memory (130) stores a control program used in the terminal (100) and various data corresponding thereto. This control program may include a predetermined program required for the terminal (100) to perform wireless communication with at least one of a base station (200), an external device, and a server.

[0120] Next, the user interface (140) includes various types of input / output means provided in the terminal (100). That is, the user interface (140) can receive user input using various input means, and the processor (110) can control the terminal (100) based on the received user input. In addition, the user interface (140) can perform output based on a command of the processor (110) using various output means.

[0121] Next, the display unit (150) outputs various images on the display screen. The display unit (150) can output various display objects, such as content executed by the processor (110) or a user interface based on the control commands of the processor (110).

[0122] Additionally, a base station (200) according to one embodiment of the present invention may include a processor (210), a communication module (220), and a memory (230).

[0123] First, the processor (210) can execute various commands or programs and process data within the base station (200). In addition, the processor (210) can control the overall operation of the base station (200), including each unit, and control data transmission and reception between the units. Here, the processor (210) can be configured to perform operations according to the embodiments described in the present invention. For example, the processor (210) can signal slot configuration information and perform communication according to the signaled slot configuration.

[0124] Next, the communication module (220) may be an integrated module that performs wireless communication using a wireless communication network and wireless LAN access using a wireless LAN. To this end, the communication module (220) may be equipped with multiple network interface cards, such as cellular communication interface cards (221, 222) and unlicensed band communication interface cards (223), in built-in or external form. Although the communication module (220) is depicted as an integrated module in the drawing, each network interface card may be independently arranged depending on the circuit configuration or purpose, unlike the drawing.

[0125] The cellular communication interface card (221) can transmit and receive wireless signals with at least one of the terminal (100), external device, and server described above using a mobile communication network, and can provide a cellular communication service using a first frequency band based on a command of the processor (210). According to one embodiment, the cellular communication interface card (221) can include at least one NIC module using a frequency band lower than 6 GHz. At least one NIC module of the cellular communication interface card (221) can independently perform cellular communication with at least one of the terminal (100), external device, and server according to a cellular communication standard or protocol of a frequency band lower than 6 GHz supported by the corresponding NIC module.

[0126] The cellular communication interface card (222) may transmit and receive wireless signals with at least one of a terminal (100), an external device, and a server using a mobile communication network, and may provide a cellular communication service using a second frequency band based on a command of the processor (210). According to one embodiment, the cellular communication interface card (222) may include at least one NIC module using a frequency band of 6 GHz or higher. At least one NIC module of the cellular communication interface card (222) may independently perform cellular communication with at least one of the terminal (100), an external device, and a server according to a cellular communication standard or protocol of a frequency band of 6 GHz or higher supported by the corresponding NIC module.

[0127] The unlicensed band communication interface card (223) transmits and receives wireless signals with at least one of a terminal (100), an external device, and a server using the third frequency band, which is an unlicensed band, and provides an unlicensed band communication service based on a command of the processor (210). The unlicensed band communication interface card (223) may include at least one NIC module that uses an unlicensed band. For example, the unlicensed band may be a band of 2.4 GHz, 5 GHz, 6 GHz, 7 GHz, or 52.6 GHz or higher. At least one NIC module of the unlicensed band communication interface card (223) may independently or dependently perform wireless communication with at least one of the terminal (100), an external device, and a server according to an unlicensed band communication standard or protocol of a frequency band supported by the corresponding NIC module.

[0128] The terminal (100) and base station (200) illustrated in FIG. 11 are block diagrams according to one embodiment of the present invention, and the blocks shown separately are logically distinguished elements of the device. Accordingly, the elements of the above-described device may be mounted as one chip or multiple chips depending on the design of the device. In addition, some components of the terminal (100), such as the user interface (140) and the display unit (150), may be selectively provided in the terminal (100). In addition, the user interface (140) and the display unit (150), etc. may be additionally provided in the base station (200) as needed.

[0129] A terminal can receive a slot format configuration from a base station in a TDD or unpaired spectrum system. The slot format may indicate the type of symbols within the slot. The symbol type may be at least one of a downlink symbol (DL symbol), an uplink symbol (UL symbol), or a flexible symbol. The terminal can receive a symbol type configuration for a slot within a radio frame from the base station. A flexible symbol may indicate a symbol that is not composed of a downlink symbol or an uplink symbol.

[0130] The terminal can receive information about each symbol type within a slot from the base station through a cell-specific or cell-common radio resource control (RRC) signal (e.g., TDD-ConfigCommon). Alternatively, the terminal can semi-statically receive information about each symbol type within a slot through SIB1. Additionally, the terminal can semi-statically receive information about each symbol type within a slot from the base station through a UE-specific, UE-dedicated RRC signal (e.g., TDD-ConfigDedicated). The base station can use the information about each symbol type within a slot to configure / set each symbol type within the slot for the terminal.

[0131] When the terminal receives information about each symbol type within a slot from the base station as a cell-specific RRC signal, the information about each symbol type may include at least one of: a period of the cell-specific slot, the number of slots consisting of only downlink symbols starting from the cell-specific slot where the period starts, the number of downlink symbols starting from the first symbol of the slot immediately following the last slot consisting of only downlink symbols, the number of slots consisting of only uplink symbols starting from the last cell-specific slot of the period, and the number of uplink symbols immediately preceding the last slot among the slots consisting of only uplink symbols. In addition, when the terminal receives information about each symbol type within a slot from the base station as a cell-specific RRC signal, the information about each symbol type may include at most two slot patterns. In this case, the two respective patterns may be applied consecutively to symbols in the time domain. A downlink symbol, an uplink symbol, and a flexible symbol configured based on a cell-specific RRC signal or SIB1 may be referred to as a cell-specific downlink symbol, a cell-specific uplink symbol, and a cell-specific flexible symbol, respectively.

[0132] When a terminal receives information about each symbol type within a slot from a base station as a terminal-specific RRC signal, a cell-specific flexible symbol may be configured as a downlink symbol or an uplink symbol. At this time, the information configured about each symbol type may include at least one of an index for a slot within a period, the number of downlink symbols starting from the first symbol of the slot indicated by the index, and the number of uplink symbols starting from the last symbol of the slot indicated by the index. In addition, the terminal may be configured so that all symbols within the slot are downlink symbols or all symbols within the slot are uplink symbols. The downlink symbol, uplink symbol, and flexible symbol configured based on the terminal-specific RRC signal may be referred to as a terminal-specific downlink symbol, a terminal-specific uplink symbol, and a terminal-specific flexible symbol, respectively.

[0133] A base station can transmit slot format information to a terminal via a slot format indicator (SFI) of DCI format 2_0 included in the group common (GC)-PDCCH. The GC-PDCCH can be CRC scrambled with an SFI-RNTI for terminals receiving slot format information. Hereinafter, the SFI transmitted via the GC-PDCCH can be described as a dynamic SFI.

[0134] The terminal can receive a dynamic SFI through the GC-PDCCH to be indicated whether the symbols in the slot are downlink symbols, uplink symbols, or flexible symbols, which are cell-specific flexible symbols or terminal-specific flexible symbols. In other words, only the flexible symbols that the terminal has semi-statically configured can be indicated as any of the downlink symbols, uplink symbols, or flexible symbols through the dynamic SFI. The terminal may not expect that the semi-statically configured downlink symbols or uplink symbols will be indicated as a different type of symbol by the dynamic SFI. The terminal can perform blind decoding at every monitoring period set by the base station to receive the GC-PDCCH transmitting the DCI format 2_0 including the dynamic SFI. If the terminal performs blind decoding and successfully receives the GC-PDCCH, the terminal can apply information about the slot format indicated by the dynamic SFI from the slot in which the GC-PDCCH is received.

[0135] A terminal can be configured with a combination of slot formats that can be indicated through a dynamic SFI from a base station. A slot format combination is for each of 1 to 256 slots, and the terminal can be configured with a slot format combination for any one of 1 to 256 slots through a dynamic SFI, and the dynamic SFI can include an index that indicates which slot the slot format combination is applied to. Table 3 is a table showing slot format combinations for each slot (refer to 3GPP TS38.213).

[0136] [Correction pursuant to Rule 91, March 13, 2024]

[0137] In Table 3, D represents a downlink symbol, U represents an uplink symbol, and F represents a flexible symbol. As shown in Table 3, up to two DL / UL switchings are allowed within one slot.

[0138] In this specification, the terms "configure," "set," and "instruct" may be used interchangeably. That is, "configure," "set," and "instruct" may have the same meaning, and similarly, "configured," "set," and "instructed" may have the same meaning.

[0139] Figures 12 to 14 illustrate a subband setting method according to one embodiment of the present invention.

[0140] In a TDD or unpaired spectrum system, when a terminal is configured or instructed to select a slot format, limited time-domain resources may be allocated as uplink resources, which can lead to reduced uplink coverage, increased latency, and reduced capacity. To address these issues, specific time-domain resources within a cell can be used for both downlink reception and uplink transmission. Even if a base station utilizes specific time-domain resources for both downlink reception and uplink transmission, the terminal only supports half-duplex communication, allowing it to perform only one operation, either downlink reception or uplink transmission, within the same specific time-domain resource.

[0141] A specific time domain resource may be a cell-specific flexible symbol within a semi-statically configured slot format. This is to minimize inter-UE interference due to transmission and reception in different symbol types (DL / UL or UL / DL).

[0142] Referring to FIG. 12, a terminal can semi-statically receive a cell-specific slot configuration. The terminal can perform downlink reception or uplink transmission on resources scheduled by the base station. The resources scheduled for PDSCH reception by a first UE and the resources scheduled for PUSCH transmission by a second UE may include the same symbol in the time domain, but may be different RBs in the frequency domain. A method in which a single base station schedules multiple UEs to use specific time-domain resources for both downlink reception and uplink transmission may be inefficient when inter-cell interference, spectrum regulation, and power consumption for PDCCH monitoring by the terminal are taken into account. A method for resolving such inefficiency is described below. A subband in this specification may be configured on frequency-domain resources (slots or symbols) within time-domain resources. In this case, the frequency-domain resources may be included within the carrier bandwidth of the terminal.

[0143] Spectrum partitioning

[0144] A terminal may receive from a base station a specific time-domain resource (cell-specific flexible slot / symbol) that can be used for both downlink reception and uplink transmission, configured in the form of multiple subbands in the frequency domain. The multiple subbands may have the same or different formats. The subband format may include a downlink subband, an uplink subband, and a flexible subband. A downlink subband may be configured with one or more downlink RB(s), an uplink subband may be configured with one or more uplink RB(s), and a flexible subband may be configured with one or more flexible RB(s). The downlink RB(s) may refer to resources available for downlink reception, and the uplink RB(s) may refer to resources available for uplink transmission. The flexible RB(s) may refer to resources available for downlink reception and uplink transmission depending on the settings of the base station.

[0145] (Method 1-1) When a terminal is configured with multiple subbands, the subband of the same format can be at most one. That is, one cell-specific flexible slot / symbol section can be configured with at most one downlink subband, one uplink subband, and one flexible subband each. Referring to FIG. 13, a cell-specific flexible slot / symbol can be configured with multiple subbands. In this case, the multiple subbands can be configured with one downlink subband, one uplink subband, and one flexible subband each. A guard band may be required to minimize the impact of UL / DL interference between downlink subbands and uplink subbands. Limiting the subband of the same format to only one is to minimize the number of guard bands to configure the downlink subband, the uplink subband, and the flexible subband, thereby increasing the efficiency of frequency resources during downlink reception and uplink transmission.

[0146] (Method 1-2) In addition, when a terminal is configured with multiple subbands, there may be multiple subbands of the same format. That is, one cell-specific flexible slot / symbol section may have multiple downlink subbands, uplink subbands, and flexible subbands. Referring to Fig. 14, a cell-specific flexible slot / symbol may be configured with multiple subbands. In this case, the multiple subbands may be configured with one downlink subband, two uplink subbands, and two flexible subbands.

[0147] In methods 1-1 and 1-2, multiple subbands may be composed of non-overlapping RBs in the frequency domain.

[0148] In Methods 1-1 and 1-2, flexible subbands may be configured by considering guard bands between uplink and downlink subbands. That is, at least one flexible subband may exist between an uplink and downlink subband. Method 1-1 may require fewer guard bands than Method 1-2. Therefore, more resources may be available for downlink reception and uplink transmission. In addition, Method 1-1 provides more frequency resources when CORESET resources for PDCCH monitoring are configured for a UE than Method 1-2, so that CORESET can be flexibly configured within a single downlink subband (or flexible subband). In addition, Method 1-1 may also provide more frequency domain resources for uplink transmission than Method 1-2. Therefore, Method 1-1 may be advantageous over Method 1-2 in terms of frequency resource utilization efficiency. The methods described in this specification are based on, but not limited to, method 1-1. In this specification, an RB within a downlink subband may be described as a downlink RB, an RB within an uplink subband may be described as an uplink RB, and an RB within a flexible subband may be described as a flexible RB.

[0149] The method for configuring multiple subbands in the frequency domain can be applied not only to cell-specific flexible slots or symbols, but also to cell-specific downlink slots or symbols or cell-specific uplink slots or symbols. Accordingly, a terminal can configure multiple subbands in the frequency domain for a cell-specific downlink slot or symbol and a cell-specific flexible slot or symbol. Alternatively, the terminal can configure multiple subbands in the frequency domain for a cell-specific uplink slot or symbol and a cell-specific flexible slot or symbol.

[0150] The method for configuring multiple subbands in the above frequency domain can be applied to a terminal-specific flexible slot or symbol. In addition, the method for configuring multiple subbands in the above frequency domain can be applied to a terminal-specific downlink slot or symbol.

[0151] Example: Signal transmission and reception when subbands are configured

[0152] First, let's define the terms used in this specification.

[0153] - SBFD (subband non-overlapping full duplex): This refers to a method of supporting simultaneous transmission and reception operations using subbands within a cell / BWP. Here, a subband refers to a frequency band configured / indicated for SBFD operation within a cell / BWP. One subband can be configured with one continuous (P)RB set. Examples of subband configuration / format can be referred to FIGS. 12 to 14. For example, in case of unpaired spectrum (i.e., TDD cell / BWP), a UL subband can be configured on a DL slot / symbol, or a UL subband can be configured on a flexible slot / symbol. Alternatively, in case of unpaired spectrum, a DL subband can be configured on a flexible slot / symbol. Here, a DL slot / symbol and a flexible slot / symbol can be configured through a cell-specific RRC signal (e.g., TDD-ConfigCommon) and / or a terminal-specific RRC signal (e.g., TDD-ConfigDedicated). When SBFD operation is configured for a cell / BWP, the cell / BWP may contain TDMed SBFD intervals and non-SBFD intervals in the time domain.

[0154] - SBFD interval (or subband interval): refers to a time interval in which a subband is configured / indicated on a cell / BWP. For example, the SBFD interval includes a time interval in which an uplink subband is configured / indicated. For example, the SBFD interval includes a slot in which an uplink subband is configured / indicated. For example, the SBFD interval includes symbol(s) (or symbol set) in which an uplink subband is configured / indicated. The SBFD interval includes an SBFD-slot (or subband slot) and / or an SBFD-symbol (or subband symbol). Here, the SBFD-slot represents a slot in which a subband is configured / indicated, and the SBFD-symbol represents a symbol in which a subband is configured / indicated. The SBFD interval may include one or more subbands in the frequency domain. When multiple subbands are configured in the SBFD interval, the subbands are FDMed. In the SBFD section, multiple subbands (DL subbands or UL subbands) can be configured to be non-overlapping in the frequency domain.

[0155] - Non-SBFD interval (or non-subband interval): refers to a time interval in which a subband is not configured / indicated on a cell / BWP. The non-SBFD interval includes a non-SBFD slot and / or a non-SBFD symbol. Here, a non-SBFD-slot (or non-subband-slot) represents a slot in which a subband is not configured / indicated, and a non-SBFD-symbol (or non-subband symbol) represents a symbol in which a subband is not configured / indicated. The non-SBFD interval refers to a legacy interval or a normal interval. The non-SBFD interval includes at least one of a DL symbol, a flexible symbol, and a UL symbol depending on the slot format.

[0156] - Legacy NR system: This refers to a system that operates in the legacy NR manner because SBFD operation is not supported or configured.

[0157] Below, a method for a terminal to receive or transmit a wireless channel / signal in a wireless communication system supporting SBFD is described.

[0158] [1] SSB and uplink (UL) transmission

[0159] (1-1) Uplink transmission

[0160] This section describes how a terminal transmits a physical uplink shared channel (PUSCH). The terminal can transmit uplink data (e.g., UL-SCH TB) to a base station via the PUSCH. At this time, the terminal can transmit uplink data using a method for scheduling PUSCH obtained from DCI within the PDCCH (DG, dynamic grant) or a method for transmitting PUSCH according to resources and transmission methods preset by the base station (CG, configured grant).

[0161] The DCI that the UE can recognize by decoding the PDCCH may include PUSCH scheduling information. The PUSCH scheduling information may include time-domain resource assignment (TDRA) information and frequency-domain resource assignment (FDRA) information. The UE may interpret the DCI transmitted via the PDCCH based on information about the control resource set (CORESET) and search space, and perform the operation indicated in the DCI. The DCI format for scheduling the PUSCH may be one of DCI formats 0_0, 0_1, or 0_2.

[0162] The time domain information of PUSCH indicated in the TDRA field in DCI format 0_0, 0_1, or 0_2 includes:

[0163] - K2: (i) An offset value between the slot in which the terminal receives a PDCCH from the base station and (ii) the slot in which the terminal transmits a PUSCH to the base station.

[0164] - SLIV (starting and length indication value): This is a jointly coded value of the starting symbol index (S) of the PUSCH and the symbol length (L) of the PUSCH within the slot indicated by the K2 value. The terminal can receive K2 and SLIV from the base station. Alternatively, the terminal can receive K2, S, and L from the base station.

[0165] When the terminal receives DCI scheduling PUSCH (e.g., DCI format 0_0, 0_1, or 0_2) in slot n, it sets slot floor(n*2 μPUSCH / n*2 μPDCCH )+K2 is determined as a slot for transmitting PUSCH. Here, μPUSCH and μPDCCH are the SCS of the cell (or BWP) where the PUSCH is scheduled and the cell (or BWP) that received the PDCCH, respectively.

[0166] PUSCH can be set to either PUSCH mapping Type A or PUSCH mapping Type B. When the UE is set to PUSCH mapping Type A, the UE can only receive PUSCH resource allocation including a DMRS symbol, and the DMRS symbol is located in the third or fourth symbol of the slot indicated by the K2 value depending on the value set by the base station. That is, when the UE is set to PUSCH mapping Type A, the start symbol index (S) of the PUSCH can be set / indicated as 0, the symbol length (L) of the PUSCH can be set / indicated as one of the values ​​from 4 to 14 (12 in case of extended CP), or SLIV can be set / indicated as one of the values ​​from 4 to 14 (12 in case of extended CP). When the UE is configured with PUSCH mapping Type B, the first symbol of the PUSCH is at least a DMRS symbol, the start symbol index of the PUSCH can be set to one of the values ​​from 0 to 13 (11 for extended CP), and the symbol length of the PUSCH can be set to one of the values ​​from 1 to 14 (12 for extended CP). Alternatively, when the UE is configured with PUSCH mapping Type B and PUSCH repetition Type A, SLIV can be set to one of the values ​​from 1 to 14 (12 for extended CP). When the UE is configured with PUSCH mapping Type B and PUSCH repetition Type B, SLIV can be set to one of the values ​​from 1 to 27 (23 for extended CP).

[0167] The frequency domain information of PUSCH indicated in the FDRA field in DCI format 0_0, 0_1, or 0_2 can be divided into two types depending on the uplink resource allocation type.

[0168] In case of uplink resource allocation type 0, a fixed number of PRBs are grouped according to the number of PRBs included in the BWP configured for the terminal to create an RBG (resource block group), and the terminal determines whether to use the corresponding RBG by receiving a bitmap in units of RBGs. The number of PRBs included in one RBG can be configured from the base station. The more PRBs included in the BWP configured for the terminal, the more PRBs can be configured to be included in one RBG. If the bit value indicated by the bitmap is 0, the terminal determines / interprets that PUSCH is not scheduled for any PRB among the PRBs in the corresponding RBG, and if the bit value is 1, the terminal determines / interprets that PUSCH is scheduled for all PRBs in the corresponding RBG. Alternatively, the bit values ​​may be applied in reverse depending on the implementation method.

[0169] In the case of uplink resource allocation type 1, resource allocation information may indicate information on consecutive PRBs allocated for uplink transmission. The resource allocation information includes a resource indication value (RIV) value in which the start index and length of consecutive PRBs in the frequency domain are jointly coded. The RIV value may be defined to indicate the start index and length of consecutive PRBs based on the size of the initial BWP or active BWP of the terminal.

[0170] Limited to DCI format 0_1 ​​or 0_2, the UE may be configured by the base station to use only one of the two uplink resource allocation types, or to dynamically use both types. When configured to dynamically use both uplink resource allocation types, the UE may determine the uplink resource allocation type to be used for PUSCH transmission through the most significant bit (MSB) 1 bit of the FDRA field in DCI format 0_1 ​​or 0_2.

[0171] The NR system supports CG (configured grant)-based PUSCH (hereinafter, CG-PUSCH) transmission to support uplink URLLC transmission, etc. CG-PUSCH transmission is also called grant-free transmission. In CG-PUSCH transmission, the UE receives resources available for PUSCH transmission from the base station in advance through higher layer (e.g., RRC) signals, and transmits PUSCH using those resources. CG-PUSCH transmission can be divided into the following two types depending on whether activation or release is possible through DCI.

[0172] - Type 1 PUSCH transmission with configured grant: The terminal can receive the period, time / frequency resources, and transmission method for PUSCH transmission in advance from the base station through upper layer (e.g., RRC) signals. Here, the transmission method may include MCS (modulation and coding scheme), TBS (TB size), etc.

[0173] - Type 2 PUSCH transmission with configured grant: The terminal receives the period for PUSCH transmission from the base station through a higher layer (e.g., RRC) signal, and the time / frequency resources and transmission method can be indicated through DCI (PDCCH).

[0174] The CG-PUSCH transmission scheme can support repeated PUSCH transmissions in multiple slots to ensure reliable uplink transmission. At this time, the terminal and the base station define the time point that can be assumed as the start of CG-PUSCH transmission as follows. The terminal is configured with one of the RV (redundancy version) sequences {0, 2, 3, 1}, {0, 3, 0, 3}, or {0, 0, 0, 0} for repeated transmission of CG-PUSCH, and uses the RV value corresponding to the {mod(n-1, 4)+1}th value in the nth initial TO (transmission occasion). Here, n is an integer greater than 0. The terminal configured for repeated transmission can start repeated transmission only in slots where the RV value corresponds to 0. However, when the RV sequence is {0, 0, 0, 0} and repeated transmission is performed in 8 slots, repeated transmission cannot start in the 8th slot. A terminal can terminate repeated transmissions when the number of repeated transmissions set in the upper layer is reached or the cycle is exceeded, or when a UL grant with the same HARQ process ID is received. Here, the UL grant refers to the DCI that schedules the PUSCH.

[0175] To improve the reliability of PUSCH transmission and reception between a base station and a terminal in a wireless communication system, the terminal can receive repeated PUSCH transmissions from the base station. The PUSCH repeated transmissions that a terminal can transmit can be divided into two types.

[0176] First, the transmission process of PUSCH repetitive transmission type A of the terminal is as follows. When the terminal receives DCI formats 0_1 to 0_2 from the base station through the PDCCH that schedules the PUSCH, PUSCH repetitive transmission is possible in K consecutive slots. Here, the value of K may be set by a higher layer (e.g., RRC) or may be indicated by the value of the TDRA field of the DCI. For example, assuming that the terminal receives the PDCCH that schedules the PUSCH in slot n, receives 2 as the K2 value from the DCI format received through the PDCCH, and receives 4 as the K value, the terminal starts transmitting the PUSCH in slot n+K2, i.e., n+2, and repeatedly transmits the PUSCH from slot n+2 to slot n+2+K-1, i.e., n+5. At this time, the time / frequency resources in which the PUSCH is transmitted in each slot are identical to the time / frequency resources indicated in the DCI. That is, PUSCH can be repeatedly transmitted in the same symbol and PRB(s) within each slot.

[0177] Next, the transmission process of PUSCH repetition transmission type B to support low-latency PUSCH repetitive transmission to satisfy the requirements of URLLC, etc. is as follows. From the base station, the terminal can be instructed of the start symbol (S) and the length (L) of the PUSCH through the TDRA field. Here, the PUSCH having the start symbol and length indicated by the TDRA field is not an actual PUSCH that is actually transmitted, but a temporarily obtained PUSCH and is called a nominal PUSCH. In addition, the terminal can be instructed of the nominal repetition number (N) of the nominal PUSCH through the TDRA field. Therefore, the terminal can determine N nominal PUSCHs through the TDRA field. The lengths of the N nominal PUSCHs are all the same as L, and the nominal PUSCHs are continuous in the time axis without separate symbols.

[0178] The UE can determine actual PUSCH(s) from nominal PUSCHs. One nominal PUSCH can be determined as one or more actual PUSCHs. The UE can be instructed / configured by the base station for symbols that cannot be used in PUSCH repetition transmission type B. These are called invalid symbols. Invalid symbols can include symbols configured as DL symbols through TDD configuration, symbols configured for SS / PBCH block reception, symbols configured for CORESET reception associated with Type0-PDCCH CSS, and symbols configured for DL-to-UL switching. The UE can exclude invalid symbols from nominal PUSCHs. As mentioned above, nominal PUSCHs are determined as continuous symbols, but if invalid symbols are excluded, they can be determined as discontinuous symbols. The actual PUSCH can be determined as continuous symbols from one nominal PUSCH excluding invalid symbols. Here, if the continuous symbols cross a slot boundary, the actual PUSCH can be divided based on the slot boundary.

[0179] Note that invalid symbols may at least include DL symbols configured by the base station to the terminal.

[0180] When a terminal performs repeated PUSCH transmission, if a symbol scheduled for PUSCH transmission in a specific slot overlaps with a symbol position set for reception of a semi-statically configured DL symbol or SS / PBCH block, the terminal does not transmit the overlapping PUSCH in that slot and does not postpone transmission to the next slot.

[0181] Alternatively, if a symbol scheduled for PUSCH transmission in a specific slot overlaps with a symbol position configured for reception of a semi-statically configured DL symbol or SS / PBCH block for uplink coverage expansion, the terminal may not transmit the overlapping PUSCH in the slot and postpone transmission to the next slot. This may be limited to PUSCH repetition transmission type A.

[0182] The above DL symbol may include a cell-specifically configured or terminal-specifically configured downlink symbol. In addition, the symbol configured for reception of the SS / PBCH block may be a cell-specifically configured or terminal-specific symbol via the RRC parameter ssb-PositionsInBurst.

[0183] Describes how a terminal transmits a physical uplink control channel (PUCCH).

[0184] When a terminal receives a DCI format (e.g., DCI format 1_0, 1_1, or 1_2) for scheduling a PUCCH, the terminal must transmit the scheduled PUCCH. The PUCCH may include UCI, and the UCI may include HARQ-ACK, SR, and / or CSI information. The HARQ-ACK information may be HARQ-ACK information regarding whether reception of two types of channels is successful. As a first type, when a PDSCH is scheduled through DCI format 1_0, 1_1, or 1_2, the HARQ-ACK information may be a HARQ-ACK regarding whether reception of the PDSCH is successful. As a second type, when DCI format 1_0, 1_1 or 1_2 indicates the release of a semi-static physical downlink shared channel (SPS PDSCH) (hereinafter, DL SPS release), the HARQ-ACK information may be a HARQ-ACK regarding the success or failure of reception of the DCI format 1_0, 1_1 or 1_2 (or DL ​​SPS release).

[0185] In order to transmit a PUCCH carrying HARQ-ACK, the PDSCH-to-HARQ_feedback timing indicator field included in DCI format 1_0, 1_1, or 1_2 may indicate a slot offset K1 for a slot in which the scheduled PUCCH should be transmitted. Here, the value of K1 may be a non-negative integer value. The K1 value of DCI format 1_0 may indicate one of {0, 1, 2, 3, 4, 5, 6, 7}. The K1 value that can be indicated in DCI format 1_1 or 1_2 may be configured or set by a higher layer (e.g., RRC).

[0186] The terminal can determine the slot for transmitting the PUCCH including the first type of HARQ-ACK information as follows. The terminal can determine the uplink slot that overlaps with the last symbol of the PDSCH corresponding to the HARQ-ACK information. When the index of the uplink slot is m, the uplink slot in which the terminal transmits the PUCCH including the HARQ-ACK information can be m+K1. Here, the index of the uplink slot is a value according to the subcarrier spacing of the (uplink) BWP in which the PUCCH is transmitted. When the terminal receives downlink slot aggregation, the ending symbol indicates the last symbol of the PDSCH scheduled in the last slot among the slots in which the PDSCH is received.

[0187] In NR systems, to ensure wide coverage, a terminal can be configured to repeatedly transmit a long PUCCH (PUCCH format 1, 3, 4) in 2, 4, or 8 slots. When a terminal is configured to repeatedly transmit a PUCCH, the same UCI can be repeatedly transmitted in each slot. The symbol configuration of the repeatedly transmitted PUCCHs is identical. That is, the repeatedly transmitted PUCCHs start from the same symbol in each slot and consist of the same number of symbols.

[0188] When a terminal repeatedly transmits PUCCH, if the symbol(s) that should transmit PUCCH in a specific slot overlap with an invalid symbol (e.g., a DL symbol that is semi-statically configured through a TDD configuration or a symbol set for reception of an SS / PBCH block), the terminal may not transmit PUCCH in that slot and may postpone PUCCH transmission to the next slot. Thereafter, if the symbol(s) that should transmit PUCCH in the slot where PUCCH transmission is postponed do not overlap with an invalid symbol, the terminal may transmit PUCCH in that slot.

[0189] The above DL symbol may include a cell-specifically configured or terminal-specifically configured downlink symbol. In addition, the symbol configured for reception of the SS / PBCH block may be a cell-specifically configured or terminal-specific symbol via the RRC parameter ssb-PositionsInBurst.

[0190] (1-2) Uplink repeat transmission

[0191] One of the problems addressed in this specification concerns when a UE repeatedly transmits a PUSCH or PUCCH in slots or symbol(s) configured as subbands. Here, the repeated transmission may be PUSCH repeated transmission type A, i.e., inter-slot PUCCH repeated transmission. When a UE is scheduled or configured via RRC to repeatedly transmit a PUSCH or PUCCH in multiple slots, the UE must determine the slots in which repeated transmission is possible.

[0192] Basically, in an NR-based system, a terminal can determine a slot as a slot for repeated transmission only if all of the symbols scheduled for PUSCH or PUCCH transmission or configured via a higher layer (e.g., RRC) are available for uplink transmission. If a symbol scheduled for PUSCH or PUCCH transmission or configured via RRC in a specific slot overlaps with a symbol position configured for reception of a semi-statically configured DL symbol or SS / PBCH block, the terminal may not transmit the overlapping PUSCH or PUCCH in the slot and postpone the transmission to the next slot. In other words, the terminal may not determine the slot as a slot for repeated transmission. Alternatively, the terminal may postpone the transmission of repeated PUCCH transmission to the next slot for repeated transmission, but may not postpone the transmission of repeated PUSCH transmission. In other words, the terminal may perform fewer PUSCH repeated transmissions than the number of repeated transmissions configured or instructed by the base station.

[0193] Referring to FIG. 15, a terminal may be configured or instructed to transmit a PUSCH twice repeatedly with PUSCH repetition transmission type A. Here, normal slot#1 may be a slot or symbol(s) in which the terminal has not been configured with a subband, and SBFD slot#2 may be a slot or symbol(s) in which the terminal has been configured with a subband. Since all resources scheduled to transmit PUSCH in normal slot#1 are uplink symbols, the terminal may determine the corresponding slot as a slot in which PUSCH repetition transmission is possible. However, the symbols in SBFD slot#2 are symbols configured as cell-specific downlink symbols (DL via tdd-ConfigurationCommon) or terminal-specific downlink symbols (DL via tdd-ConfigurationDedicated) by the TDD configuration. Therefore, if the prior art is applied, the terminal cannot determine SBFD slot#2 as a slot in which PUSCH repetition transmission is possible even if the symbols scheduled to transmit PUSCH are symbols included in an uplink subband. That is, although the terminal is configured or instructed to operate in an uplink subband in a downlink or flexible slot to improve uplink performance (e.g., improve coverage, reduce latency, etc.), it may be difficult to expect uplink performance improvement for PUSCH repeated transmissions because the terminal does not determine the slot as a slot capable of repeated transmission.

[0194] In a first method of the present specification to solve this problem, when a terminal is configured or instructed to operate as a subband, the terminal may determine resources available for repeated transmission by additionally considering the availability of resources for repeated transmission in the frequency domain, i.e., RB units, as well as the availability of resources for repeated transmission in the time domain, i.e., slot or symbol units. Specifically, when the terminal is configured or instructed to operate as a subband and all symbols and RBs scheduled for PUSCH or PUCCH repeated transmission or configured via RRC are available for uplink transmission, the terminal may determine the slot as a slot available for repeated transmission. A UE may not determine a slot as a slot for which repeated PUSCH or PUCCH transmission is possible and may postpone the PUSCH or PUCCH transmission to a next slot for which repeated transmission is possible only if the symbols and RBs scheduled for PUSCH or PUCCH transmission in a specific slot or configured via RRC overlap with DL symbols included in an RB other than an uplink subband (i.e., an RB in a downlink subband or a guard band) or symbols configured for reception of SS / PBCH blocks in an RB other than an uplink subband (i.e., an RB in a downlink subband or a guard band). Alternatively, the UE may postpone the transmission of repeated PUCCH transmission to a next slot for which repeated transmission is possible, but may not postpone the transmission of repeated PUSCH transmission. That is, the UE may perform fewer number of repeated PUSCH transmissions than the number of repeated transmissions configured or instructed by the base station.

[0195] Figure 16 illustrates the first method described above. Compared to the method of Figure 15, which only considered the availability of resources for repeated transmission in the time domain, i.e., symbol units, the method of Figure 16 can also consider the availability of resources for repeated transmission in the frequency domain, i.e., RB units. In the case of Figure 16, since the symbols and RBs scheduled for PUSCH transmission or configured via RRC are available for uplink transmission, the UE can determine SBFD slot#2 as a slot capable of repeated PUSCH transmission.

[0196] In the first method, when the resources configured for receiving SS / PBCH blocks overlap with the resources scheduled for repeated transmission of PUSCH or PUCCH or configured via RRC, the operation of the terminal according to the type of SS / PBCH block and the collision situation (symbol unit or RE unit) is proposed below.

[0197] 1) Symbol-level collision situation: Figure 17 illustrates a situation where resources configured for receiving SS / PBCH blocks and resources scheduled for repeated PUSCH or PUCCH transmission or configured via RRC overlap on a symbol-level basis. In this case, the terminal operations according to the SS / PBCH block type are as follows.

[0198] - Cell-specific SS / PBCH block with same PCI from the serving cell:

[0199] A terminal can be cell-specifically configured to receive SS / PBCH blocks having the same physical cell ID (PCI) as the serving cell. Cell-specific resources for receiving SS / PBCH blocks can be configured by the RRC parameter ssb-PositionsInBurst. If the resources cell-specifically configured to receive SS / PBCH blocks and the resources scheduled for transmission in repetitive PUSCH or PUCCH transmission slots / symbols or configured via RRC overlap each other on a symbol-by-symbol basis, the terminal behavior is as follows.

[0200] For example, if a resource that is cell-specifically configured to receive an SS / PBCH block and a resource that is scheduled or configured via RRC to repeatedly transmit a PUSCH or PUCCH overlap each other at the symbol level, the UE can determine the slot as a slot in which repeated PUSCH or PUCCH transmission is possible. In other words, if the UE is scheduled or configured via RRC for a PUSCH or PUCCH from the base station to overlap with a symbol that is cell-specifically configured to receive an SS / PBCH block, it can be determined that the UE is configured or instructed to prioritize PUSCH or PUCCH transmission over reception of the SS / PBCH block in the slot from the UE's perspective. This is a method that allows a specific UE to transmit a PUSCH or PUCCH that is scheduled or configured via RRC in an uplink subband even if other UEs in the cell receive an SS / PBCH block in a downlink subband, since the base station supports a full duplex communication method.

[0201] As another example, if a symbol that is cell-specifically configured to receive an SS / PBCH block overlaps with a resource scheduled for repeated PUSCH or PUCCH transmission or configured via RRC, the UE may determine the slot as a slot capable of repeated PUSCH or PUCCH transmission only when the slot is dynamically scheduled (e.g., through an L1 signal or DCI), and may not determine the slot as a slot capable of repeated PUSCH or PUCCH transmission for the resource configured via RRC. That is, scheduling a PUSCH or PUCCH through dynamic scheduling from the base station to overlap with a symbol that is cell-specifically configured to receive an SS / PBCH block may be determined by the UE to be instructed to prioritize PUSCH or PUCCH transmission over the slot without intending to receive an SS / PBCH block. Meanwhile, the UE may determine that the resource for PUSCH or PUCCH transmission configured via RRC is configured to prioritize reception of an SS / PBCH. This is a method that allows a specific terminal to transmit a PUSCH or PUCCH dynamically scheduled from the base station in an uplink subband even if another terminal in the cell receives an SS / PBCH block in a downlink subband, since the base station supports a full duplex communication method.

[0202] - UE-specific SS / PBCH block with different PCI from the serving cell:

[0203] A terminal may be specifically configured to receive SS / PBCH blocks having PCIs other than serving cell PCIs from multiple transmission and reception points (TRPs). In this case, if resources specifically configured to receive SS / PBCH blocks and resources scheduled for repeated PUSCH or PUCCH transmission or configured via RRC overlap each other on a symbol basis, the terminal operates as follows.

[0204] A terminal may not expect to be instructed to transmit a PUSCH via DCI format 0_0, 0_1, or 0_2 in a symbol configured to receive an SS / PBCH block. This is to prioritize reception of an SS / PBCH block over PUSCH transmission, considering that a terminal operating in a half-duplex mode cannot simultaneously perform transmission and reception in the same symbol, and that the base station has configured the terminal to specifically receive an SS / PBCH block in order to receive PDSCHs transmitted from multiple TRPs of a non-serving cell. Accordingly, a terminal may perform reception of an SS / PBCH block and may not expect to be instructed to transmit a PUSCH such that at least one symbol overlaps with the SS / PBCH block.

[0205] A terminal may not expect to be instructed to transmit a PUCCH via DCI format 1_0, 1_1, or 1_2 in a symbol configured to receive an SS / PBCH block. This is to prioritize reception of an SS / PBCH block over PUCCH transmission, considering that a terminal operating in a half-duplex mode cannot simultaneously transmit and receive in the same symbol, and the base station has configured the terminal to specifically receive an SS / PBCH block in order to receive PDSCHs transmitted from multiple TRPs of a non-serving cell. Accordingly, a terminal may not expect to be instructed to perform reception of an SS / PBCH block and transmit a PUCCH such that at least one symbol overlaps with the SS / PBCH block.

[0206] If the symbol(s) configured to transmit a PUSCH from a higher layer and the symbol(s) configured to receive an SS / PBCH block partially overlap, the UE can receive the SS / PBCH block and transmit the PUSCH in a rate-matched manner. For example, the UE can rate-match the PUSCH for the PUSCH resources configured at the position of the symbol to which the SS / PBCH block is mapped and the DL-to-UL switching gap symbol for RF retuning. Even if the RBs occupied by the symbol(s) configured to transmit a PUSCH from a higher layer and the RBs occupied by the symbol(s) configured to receive an SS / PBCH block do not overlap each other on an RB basis, the UE must operate in a half-duplex manner and therefore cannot perform simultaneous transmission and reception on different frequency resources of the same symbol. This method is a method that can guarantee the downlink reception and uplink transmission configured for the terminal to the maximum extent possible in symbol(s) excluding symbol(s) identical to the SS / PBCH block when the terminal is configured or instructed to operate in a subband.

[0207] If a symbol configured to transmit a PUSCH from a higher layer and a symbol configured to receive an SS / PBCH block completely overlap, the terminal may receive the SS / PBCH block and not transmit the PUSCH. This is to prioritize reception of the SS / PBCH block, considering that a terminal operating in a half-duplex mode cannot simultaneously perform transmission and reception in the same symbol, and the base station has configured the terminal to specifically receive the SS / PBCH block in order to receive PDSCH transmitted from multiple TRPs of a non-serving cell. Therefore, the terminal may receive the SS / PBCH block and not transmit the PUSCH.

[0208] If a symbol configured to transmit a PUCCH from a higher layer and a symbol configured to receive an SS / PBCH partially overlap, the UE may receive an SS / PBCH block and not transmit a PUCCH. Even if the RBs occupied by the symbol(s) configured to transmit a PUCCH from a higher layer and the RBs occupied by the symbol(s) configured to receive an SS / PBCH block do not overlap on an RB basis, the UE operates in a half-duplex manner and therefore cannot perform simultaneous transmission and reception on different frequency resources of the same symbol. In addition, this is to prioritize reception of an SS / PBCH block over PUCCH transmission, considering that the base station has configured the UE to specifically receive an SS / PBCH block in order to receive a PDSCH transmitted from multiple TRPs of a non-serving cell. As mentioned above, it is possible to transmit a PUSCH by rate-matching it on a symbol-by-symbol basis, but a PUCCH may not be available for uplink transmission even for one of the scheduled symbols. In this case, since PUCCH cannot be transmitted in the slot, the terminal may perform reception of the SS / PBCH block and not transmit PUCCH.

[0209] If a symbol configured to transmit a PUCCH from a higher layer and a symbol configured to receive an SS / PBCH completely overlap, the terminal may receive the SS / PBCH block and not transmit the PUCCH. This is to prioritize reception of the SS / PBCH block over transmission of the PUCCH, considering that a terminal operating in a half-duplex mode cannot simultaneously transmit and receive in the same symbol, and the base station has configured the terminal to specifically receive an SS / PBCH block in order to receive PDSCHs transmitted from multiple TRPs of a non-serving cell. Therefore, the terminal may receive the SS / PBCH block and not transmit the PUCCH.

[0210] - UE-specific SS / PBCH block with activated additional PCI:

[0211] A terminal may be specifically configured to receive an SS / PBCH block having an additional PCI associated with an activated Transmission Configuration Indicator (TCI) state among the SS / PBCH blocks received from multiple TRPs. In this case, if a resource specifically configured to receive the SS / PBCH block and a resource scheduled for repeated transmission of a PUSCH or PUCCH or configured via RRC overlap each other on a symbol basis, the terminal operates as follows.

[0212] A terminal may not expect to be instructed to transmit a PUSCH via DCI format 0_0, 0_1, or 0_2 in a symbol configured to receive an SS / PBCH block. A terminal operating in a half-duplex mode cannot perform simultaneous transmission and reception in the same symbol, and the base station prioritizes reception of an SS / PBCH block having a PCI associated with a TCI state that the terminal has activated among the SS / PBCH blocks configured for reception of PDSCHs transmitted from multiple TRPs of a non-serving cell. Therefore, a terminal may not expect to be instructed to perform reception of an SS / PBCH block and transmit a PUSCH such that at least one symbol overlaps.

[0213] A terminal may not expect to be instructed to transmit a PUCCH via DCI format 1_0, 1_1, or 1_2 in a symbol configured to receive an SS / PBCH block. A terminal operating in a half-duplex mode cannot simultaneously transmit and receive in the same symbol, and the base station prioritizes reception of an SS / PBCH block having a PCI associated with an activated TCI state among the SS / PBCH blocks configured for the terminal to receive PDSCHs transmitted from multiple TRPs of a non-serving cell. Therefore, a terminal may not expect to be instructed to perform reception of an SS / PBCH block and transmit a PUCCH such that at least one symbol overlaps.

[0214] If the symbol(s) configured to transmit the PUSCH from the upper layer and the symbol(s) configured to receive the SS / PBCH block partially overlap, the UE can receive the SS / PBCH block. On the other hand, the UE can rate-match the PUSCH and transmit it on the PUSCH resources configured at the positions of the symbols to which the SS / PBCH block is mapped and the downlink-uplink switching gap symbols. Since the base station may have intentionally configured the UE to receive the SS / PBCH block having an additional PCI associated with an activated TCI state among the SS / PBCH blocks received from multiple TRPs, the reception of the SS / PBCH is given priority. In addition, even if the RBs occupied by the PUSCH and the RBs occupied by the SS / PBCH block do not overlap each other in RB units, the UE must operate in a half-duplex manner and therefore cannot simultaneously transmit and receive on different frequency resources of the same symbol. This method can guarantee the maximum downlink reception and uplink transmission configured for the terminal when the terminal is configured or instructed to use a subband.

[0215] If a symbol configured to transmit a PUSCH from a higher layer and a symbol configured to receive an SS / PBCH block completely overlap, the terminal may receive the SS / PBCH block and not transmit the PUSCH. A terminal operating in a half-duplex mode cannot perform simultaneous transmission and reception in the same symbol, and the base station configures the terminal to specifically receive an SS / PBCH block to give priority to reception of an SS / PBCH block having a PCI associated with an activated TCI state for the terminal among the SS / PBCH blocks configured by the base station for receiving PDSCHs transmitted from multiple TRPs of a non-serving cell, over transmission of a PUSCH. Therefore, the terminal may perform reception of the SS / PBCH block and not transmit the PUSCH.

[0216] If a symbol configured to transmit a PUCCH from a higher layer overlaps with a symbol configured to receive an SS / PBCH, the UE may receive an SS / PBCH block and not transmit a PUCCH. Even if the RBs occupied by the symbol(s) configured to transmit a PUCCH from a higher layer and the RBs occupied by the symbol(s) configured to receive an SS / PBCH block do not overlap with each other at the RB level, the UE must operate in a half-duplex manner and therefore cannot perform simultaneous transmission and reception on different frequency resources of the same symbol. In addition, the reason why the base station is configured to receive an SS / PBCH block specifically for the UE is to give priority to reception of an SS / PBCH block having a PCI associated with an activated TCI state for the UE among the SS / PBCH blocks configured by the base station for receiving a PDSCH transmitted from multiple TRPs of a non-serving cell, over PUCCH transmission. Meanwhile, PUSCH can be transmitted by rate-matching on a symbol-by-symbol basis, but PUCCH cannot be transmitted in the corresponding slot if even one of the scheduled symbols cannot be used for uplink transmission. Therefore, the terminal may perform reception of SS / PBCH blocks and not transmit PUCCH.

[0217] If a symbol configured to transmit a PUCCH from a higher layer and a symbol configured to receive a SS / PBCH completely overlap, the terminal may receive an SS / PBCH block and not transmit a PUCCH. A terminal operating in a half-duplex mode cannot perform simultaneous transmission and reception in the same symbol, and the reason why the base station configures the terminal to specifically receive an SS / PBCH block is to give priority to reception of an SS / PBCH block having a PCI associated with an activated TCI state for the terminal among the SS / PBCH blocks configured by the base station for receiving PDSCHs transmitted from multiple TRPs of a non-serving cell, over PUCCH transmission. Therefore, the terminal may perform reception of an SS / PBCH block and not transmit a PUCCH.

[0218] - UE-specific SS / PBCH block with non-activated additional PCI:

[0219] As an example, if a resource specifically configured for the terminal to receive an SS / PBCH block having an additional PCI associated with an inactive TCI state among SS / PBCH blocks received from multiple TRPs and a resource scheduled or configured via RRC to repeatedly transmit a PUSCH or PUCCH overlap with each other at the symbol level, the terminal may determine the slot as a slot in which repeated PUSCH or PUCCH transmission is possible. That is, the terminal may determine that the slot in which the PUSCH or PUCCH is scheduled or configured via a higher layer (e.g., RRC) to overlap with the symbol(s) specifically configured for the terminal to receive an SS / PBCH block having an additional PCI associated with an inactive TCI state is configured or instructed to prioritize PUSCH or PUCCH transmission over receiving an SS / PBCH block in the slot.

[0220] As another example, if a resource configured through RRC or a symbol(s) specifically configured for a terminal to receive an SS / PBCH block having an additional PCI associated with an inactive TCI state among SS / PBCH blocks received from multiple TRPs and is scheduled to repeatedly transmit a PUSCH or PUCCH overlaps with each other on a symbol basis, the slot may be determined as a slot capable of repeated PUSCH or PUCCH transmission only if the slot is dynamically (e.g., DCI) scheduled, and the slot may not be determined as a slot capable of repeated PUSCH or PUCCH transmission for a resource configured through a higher layer (e.g., RRC). That is, when a base station dynamically schedules a PUSCH or PUCCH to overlap with symbol(s) specifically configured for the terminal to receive an SS / PBCH block having an additional PCI associated with an inactive TCI state, the terminal may determine, from the perspective of the terminal, that it does not intend to receive the SS / PBCH block in that slot and has been instructed to prioritize PUSCH or PUCCH transmission. On the other hand, the terminal may determine that it has been configured to prioritize reception of SS / PBCH for resources for PUSCH or PUCCH transmission configured through a higher layer (e.g., RRC).

[0221] - UE-specific SS / PBCH block for L1 beam measurement / reporting:

[0222] When resources specifically configured for a terminal to receive SS / PBCH blocks for link recovery and resources scheduled or configured via RRC to repeatedly transmit PUSCH or PUCCH overlap each other on a symbol basis, the terminal behavior is as follows.

[0223] The terminal may not expect to be instructed to transmit a PUSCH via DCI format 0_0, 0_1, or 0_2 in a symbol configured to receive an SS / PBCH block. This is because a terminal operating in a half-duplex mode cannot perform simultaneous transmission and reception in the same symbol, and considering that the base station has configured the terminal to receive a SS / PBCH block specifically for link recovery, the reception of the SS / PBCH block is to be prioritized over the PUSCH transmission. Therefore, the terminal may perform reception of an SS / PBCH block and may not expect to be instructed to transmit a PUSCH such that at least one symbol overlaps with the SS / PBCH block.

[0224] The terminal may not expect to be instructed to transmit a PUCCH via DCI format 1_0, 1_1, or 1_2 in a symbol configured to receive an SS / PBCH block. This is because a terminal operating in a half-duplex mode cannot perform simultaneous transmission and reception in the same symbol, and the base station may prioritize reception of an SS / PBCH block over PUCCH transmission, considering that the terminal has been configured to receive a SS / PBCH block specifically for link recovery. Therefore, the terminal may not expect to be instructed to perform reception of an SS / PBCH block and transmit a PUCCH such that at least one symbol overlaps with the SS / PBCH block.

[0225] If the symbol(s) configured to transmit a PUSCH from a higher layer and the symbol(s) configured to receive a SS / PBCH block partially overlap, the UE may receive the SS / PBCH block and rate-match and transmit the PUSCH on the PUSCH resources configured at the positions of the symbols to which the SS / PBCH block is mapped and the downlink-uplink switching gap symbols. Since the base station may have intentionally configured the UE to receive the SS / PBCH on the symbol(s) specifically configured to receive the SS / PBCH block for link recovery, the reception of the SS / PBCH is prioritized over the transmission of the PUSCH. Even if the RBs occupied by the symbol(s) configured to transmit a PUSCH from a higher layer and the RBs occupied by the symbol(s) configured to receive an SS / PBCH block do not overlap each other at the RB level, the UE must operate in a half-duplex manner and therefore cannot perform simultaneous transmission and reception on different frequency resources of the same symbol. This method is a method that can guarantee downlink reception and uplink transmission configured for the terminal to the maximum extent possible in symbol(s) excluding the same symbol(s) when the terminal is configured or instructed to use a subband.

[0226] If a symbol configured to transmit a PUSCH from a higher layer and a symbol configured to receive an SS / PBCH block completely overlap, the terminal may receive the SS / PBCH block and not transmit the PUSCH. This is to prioritize reception of the SS / PBCH block over PUSCH transmission, considering that a terminal operating in a half-duplex mode cannot simultaneously transmit and receive in the same symbol, and the base station has configured the terminal to receive a SS / PBCH block specifically for link recovery. Therefore, the terminal may receive the SS / PBCH block and not transmit the PUSCH.

[0227] If a symbol configured to transmit a PUCCH from a higher layer overlaps with a symbol configured to receive an SS / PBCH, the UE may receive an SS / PBCH block and not transmit a PUCCH. This is because, even if the RBs occupied by the symbol(s) configured to transmit a PUCCH from a higher layer and the RBs occupied by the symbol(s) configured to receive an SS / PBCH block do not overlap in units of RBs, the UE must operate in a half-duplex manner and therefore cannot perform simultaneous transmission and reception on different frequency resources of the same symbol. In addition, this is to prioritize reception of an SS / PBCH block over PUCCH transmission, considering that the base station has configured the UE to receive an SS / PBCH block specifically for link recovery. Meanwhile, while it is possible to transmit a PUSCH by rate-matching it on a symbol-by-symbol basis, if even one of the scheduled symbols cannot be used for uplink transmission, the PUCCH cannot be transmitted in the corresponding slot. Therefore, the terminal may perform reception of SS / PBCH blocks and not transmit PUCCH.

[0228] If the symbol configured to transmit a PUCCH from a higher layer and the symbol configured to receive an SS / PBCH completely overlap, the terminal may receive an SS / PBCH block and not transmit a PUCCH. This is to prioritize reception of an SS / PBCH block over transmission of a PUCCH, considering that a terminal operating in a half-duplex mode cannot simultaneously transmit and receive in the same symbol, and that the base station has configured the terminal to receive a SS / PBCH block specifically for link recovery. Therefore, the terminal may receive an SS / PBCH block and not transmit a PUCCH.

[0229] 2) RE (resource element) unit collision situation: Figure 18 illustrates a situation where (i) resources configured for receiving SS / PBCH blocks and (ii) resources scheduled for repeated PUSCH or PUCCH transmission or configured through a higher layer (e.g., RRC) overlap each other at the RE unit. In this case, terminal operations according to the type of SS / PBCH block are as follows.

[0230] - Cell-specific SS / PBCH block with same PCI from the serving cell:

[0231] When (i) resources specifically configured to receive SS / PBCH blocks and (ii) resources scheduled or configured via a higher layer (e.g., RRC) to repeatedly transmit PUSCH or PUCCH overlap each other in RE units, the UE behavior is as follows.

[0232] The UE may not expect to be instructed to transmit a PUSCH via DCI format 0_0, 0_1, or 0_2 on an RE configured to receive an SS / PBCH block. This is because a UE operating in a half-duplex mode cannot simultaneously transmit and receive on the same RE, and the base station may prioritize reception of an SS / PBCH block over PUSCH transmission, considering that the UE is configured to receive a cell-specific SS / PBCH block for periodic synchronization. Therefore, the UE may not expect to be instructed to receive an SS / PBCH block and transmit a PUSCH such that at least one RE overlaps with the SS / PBCH block.

[0233] The UE may not expect to be instructed to transmit a PUCCH via DCI format 1_0, 1_1, or 1_2 on an RE configured to receive an SS / PBCH block. This is because a UE operating in a half-duplex mode cannot simultaneously transmit and receive on the same RE, and the base station may prioritize reception of an SS / PBCH block over PUCCH transmission, considering that the UE is configured to receive a cell-specific SS / PBCH block for periodic synchronization. Therefore, the UE may not expect to be instructed to receive an SS / PBCH block and transmit a PUCCH such that the SS / PBCH block overlaps with at least one RE.

[0234] When the RE(s) configured to transmit PUSCH from a higher layer and the RE(s) configured to receive SS / PBCH blocks partially overlap, the UE can receive the SS / PBCH block and rate-match and transmit the PUSCH for the RE to which the SS / PBCH block is mapped and the downlink-uplink switching gap symbol. This is because, from the perspective of a UE, it must operate in a half-duplex manner and therefore cannot perform simultaneous transmission and reception in the same RE unit. This method is a method that can guarantee the configured downlink reception and uplink transmission for the UE to the greatest extent possible in the symbol(s) excluding the same RE(s) when the UE is configured or instructed to operate in a subband.

[0235] If the RE configured to transmit the PUSCH from the upper layer and the RE configured to receive the SS / PBCH block completely overlap, the UE may receive the SS / PBCH block and not transmit the PUSCH. A UE operating in a half-duplex mode cannot perform simultaneous transmission and reception on the same RE, and the reason the base station configures the SS / PBCH block to be cell-specific is to prioritize the reception of the SS / PBCH block over the transmission of the PUSCH, considering that the base station has configured the UE for periodic synchronization. Therefore, the UE may receive the SS / PBCH block and not transmit the PUSCH.

[0236] If a terminal has an RE configured to transmit a PUCCH from a higher layer and an RE configured to receive a SS / PBCH partially overlap, the terminal may receive a SS / PBCH block and not transmit a PUCCH. This is because, from the terminal's perspective, it must operate in a half-duplex manner and therefore cannot perform simultaneous transmission and reception in the same RE unit. In addition, the reason why the base station is configured to receive a SS / PBCH block in a cell-specific manner is to give priority to the reception of a SS / PBCH block over PUCCH transmission for periodic synchronization with the terminal. It is possible to rate-match a PUSCH and transmit it on an RE basis, but if even one of the scheduled symbols of a PUCCH cannot be used for uplink transmission, the PUCCH cannot be transmitted in that slot. Therefore, the terminal may receive a SS / PBCH block and not transmit a PUCCH.

[0237] If the RE configured to transmit PUCCH from the upper layer and the RE configured to receive SS / PBCH completely overlap, the UE may receive the SS / PBCH block and not transmit the PUCCH. A UE operating in a half-duplex mode cannot simultaneously transmit and receive on the same RE, and the reason the base station is configured to receive the SS / PBCH block in a cell-specific manner is to prioritize the reception of the SS / PBCH block over the transmission of the PUCCH, considering that the base station has configured the UE for periodic synchronization. Therefore, the UE may receive the SS / PBCH block and not transmit the PUCCH.

[0238] - UE-specific SS / PBCH block with different PCI from the serving cell:

[0239] (i) When resources specifically configured for a terminal to receive SS / PBCH blocks having different PCIs than the serving cell PCIs (physical cell IDs) received from multiple TRPs and (ii) resources scheduled or configured via RRC to repeatedly transmit PUSCH or PUCCH overlap with each other in RE units, the terminal behavior is as follows.

[0240] A terminal may not expect to be instructed to transmit a PUSCH via DCI format 0_0, 0_1, or 0_2 on an RE configured to receive an SS / PBCH block. A terminal operating in a half-duplex mode cannot simultaneously transmit and receive on the same RE, and the reason why the base station configures the terminal to specifically receive an SS / PBCH block is to prioritize reception of the SS / PBCH block, considering that the base station has configured the terminal to receive PDSCH transmitted from multiple TRPs of a cell other than the serving cell. Therefore, a terminal may not expect to be instructed to perform reception of an SS / PBCH block and transmit a PUSCH such that at least one RE overlaps.

[0241] A terminal may not expect to be instructed to transmit a PUCCH via DCI format 1_0, 1_1, or 1_2 on an RE configured to receive an SS / PBCH block. A terminal operating in a half-duplex mode cannot simultaneously transmit and receive on the same RE, and the reason why the base station configures the terminal to specifically receive an SS / PBCH block is to prioritize reception of the SS / PBCH block, considering that the base station has configured the terminal to receive PDSCH transmitted from multiple TRPs of a cell other than the serving cell. Therefore, a terminal may not expect to be instructed to perform reception of an SS / PBCH block and transmit a PUCCH such that at least one RE overlaps.

[0242] If the RE(s) configured to transmit PUSCH from a higher layer and the RE(s) configured to receive SS / PBCH blocks partially overlap, the UE can receive the SS / PBCH blocks and transmit the PUSCH in a rate-matched manner. For example, the UE can rate-match the PUSCH for the RE to which the SS / PBCH blocks are mapped and the downlink-uplink switching gap symbol. This is because the UE must operate in a half-duplex manner and therefore cannot perform simultaneous transmission and reception in the same RE unit. This method is a method that can guarantee the configured downlink reception and uplink transmission for the UE to the greatest extent possible in the symbol(s) excluding the same RE(s) when the UE is configured or instructed to operate in a subband.

[0243] If the RE configured to transmit a PUSCH from a higher layer and the RE configured to receive an SS / PBCH block completely overlap, the UE may receive the SS / PBCH block and not transmit the PUSCH. This is to prioritize reception of the SS / PBCH block, considering that a UE operating in a half-duplex mode cannot simultaneously transmit and receive on the same RE, and the base station has configured the UE to specifically receive the SS / PBCH block in order to receive PDSCH transmitted from multiple TRPs of a non-serving cell. Therefore, the UE may receive the SS / PBCH block and not transmit the PUSCH.

[0244] If a terminal is configured to transmit a PUCCH from an upper layer and an RE configured to receive a SS / PBCH overlap partially, the terminal may receive a SS / PBCH block and not transmit a PUCCH. This is because the terminal must operate in a half-duplex manner and therefore cannot perform simultaneous transmission and reception in the same RE unit. In addition, this is to prioritize reception of the SS / PBCH block, considering that the base station is configured to receive a SS / PBCH block specifically for the terminal in order to receive a PDSCH transmitted from multiple TRPs of a non-serving cell. Meanwhile, while it is possible to transmit a PUSCH by rate-matching it on an RE basis, a PUCCH cannot be transmitted in a slot if even one of the scheduled symbols cannot be used for uplink transmission. Therefore, the terminal may receive a SS / PBCH block and not transmit a PUCCH.

[0245] If the RE configured to transmit PUCCH from the upper layer and the RE configured to receive SS / PBCH completely overlap, the UE may receive the SS / PBCH block and not transmit the PUCCH. This is to prioritize the reception of the SS / PBCH block over the transmission of the PUCCH, considering that a UE operating in a half-duplex mode cannot simultaneously transmit and receive on the same RE, and the base station has configured the UE to specifically receive the SS / PBCH block in order to receive PDSCH transmitted from multiple TRPs of a non-serving cell. Therefore, the UE may receive the SS / PBCH block and not transmit the PUCCH.

[0246] - UE-specific SS / PBCH block for L1 beam measurement / reporting:

[0247] (i) When resources specifically configured for a terminal to receive SS / PBCH blocks for link recovery and (ii) resources scheduled or configured via a higher layer (e.g., RRC) to repeatedly transmit PUSCH or PUCCH overlap each other in RE units, the terminal behavior is as follows.

[0248] The terminal may not expect to be instructed to transmit a PUSCH via DCI format 0_0, 0_1, or 0_2 on an RE configured to receive an SS / PBCH block. This is because a terminal operating in a half-duplex mode cannot perform simultaneous transmission and reception on the same RE, and considering that the base station has configured the terminal to specifically receive an SS / PBCH block for link recovery, reception of the SS / PBCH block is to be prioritized over PUSCH transmission. Therefore, the terminal may perform reception of an SS / PBCH block and may not expect to be instructed to transmit a PUSCH such that at least one RE overlaps with the SS / PBCH block.

[0249] The terminal may not expect to be instructed to transmit a PUCCH via DCI format 1_0, 1_1, or 1_2 on an RE configured to receive an SS / PBCH block. This is because a terminal operating in a half-duplex mode cannot simultaneously transmit and receive on the same RE, and considering that the base station has configured the terminal to specifically receive an SS / PBCH block for link recovery, reception of the SS / PBCH block is to be prioritized over PUCCH transmission. Therefore, the terminal may perform reception of an SS / PBCH block and may not expect to be instructed to transmit a PUCCH such that at least one RE overlaps with the SS / PBCH block.

[0250] If RE(s) configured to transmit PUSCH from upper layer and RE(s) configured to receive SS / PBCH block partially overlap, UE can receive SS / PBCH block and transmit PUSCH in rate-matched manner. For example, UE can transmit PUSCH in rate-matched manner for RE to which SS / PBCH block is mapped and downlink-uplink switching gap symbol. This is because UE must operate in half-duplex mode and therefore cannot perform simultaneous transmission and reception in the same RE unit. This method can guarantee downlink reception and uplink transmission configured for UE to the greatest extent possible in resource(s) excluding colliding RE(s) when UE is configured or instructed to operate in subband.

[0251] If the RE configured to transmit a PUSCH from a higher layer and the RE configured to receive an SS / PBCH block completely overlap, the UE may receive the SS / PBCH block and not transmit the PUSCH. This is because a UE operating in a half-duplex mode cannot perform simultaneous transmission and reception on the same RE, and considering that the base station has configured the UE to specifically receive SS / PBCH blocks for link recovery, the reception of the SS / PBCH block is prioritized over PUSCH transmission. Therefore, the UE may receive the SS / PBCH block and not transmit the PUSCH.

[0252] If a UE has an RE configured to transmit a PUCCH from a higher layer and an RE configured to receive a SS / PBCH partially overlap, the UE may receive an SS / PBCH block and not transmit a PUCCH. This is because the UE must operate in a half-duplex manner and therefore cannot perform simultaneous transmission and reception in the same RE unit. In addition, this is to prioritize reception of SS / PBCH blocks over PUCCH transmission, considering that the base station has configured the UE to specifically receive SS / PBCH blocks for link recovery. Meanwhile, while PUSCH can be transmitted by rate-matching on an RE basis, if even one of the scheduled symbols of PUCCH cannot be used for uplink transmission, the PUCCH cannot be transmitted in the corresponding slot. Therefore, the UE may receive an SS / PBCH block and not transmit a PUCCH.

[0253] If the RE configured to transmit PUCCH from the upper layer and the RE configured to receive SS / PBCH completely overlap, the UE may receive the SS / PBCH block and not transmit the PUCCH. This is to prioritize reception of the SS / PBCH block over PUCCH transmission, considering that a UE operating in a half-duplex mode cannot simultaneously transmit and receive on the same RE, and the base station has configured the UE to specifically receive SS / PBCH blocks for link recovery. Therefore, the UE may receive the SS / PBCH block and not transmit the PUCCH.

[0254] In the above symbol unit or RE unit collision situation, if the PUSCH is the first repetitive transmission, the terminal can transmit the remaining repetitive transmissions by rate-matching them as if they were the first repetitive transmission. This is to facilitate soft combining of the repetitive transmissions of the PUSCH at the base station by having the terminal determine the TBS (TB size) for the repetitive PUSCH transmissions to be the same and transmit them.

[0255] In the above collision situation, if the PUSCH is not the first repetitive transmission, the terminal may not determine that the slot is eligible for repetitive transmission and thus may not transmit the PUSCH. This is to facilitate soft combining of repetitive PUSCH transmissions at the base station by having the terminal determine and transmit the same TBS for the repetitive PUSCH transmissions.

[0256] According to the second method, the terminal may not always determine the slots operating as subbands as slots capable of repeated transmission. That is, if the terminal is configured or instructed to perform repeated PUSCH or PUCCH transmissions in multiple slots, it may determine only the slots not operating as subbands as slots capable of repeated transmission.

[0257] (1-3) Cases other than uplink repeat transmission

[0258] The problem to be solved in the present invention is about the operation of a terminal when resources scheduled to transmit an uplink signal / channel in a symbol configured to receive an SS / PBCH block or configured via RRC overlap each other on a symbol-by-symbol basis. A terminal operating in a half-duplex mode cannot perform simultaneous transmission and reception in the same symbol. In the following, we propose terminal operation according to whether the uplink transmission is semi-statically configured via a higher layer (e.g., RRC) signal or dynamically scheduled via DCI, and terminal operation according to the type of SS / PBCH block.

[0259] - Cell-specific SS / PBCH block with same PCI from the serving cell:

[0260] (i) When resources configured for cell-common reception of SS / PBCH blocks for the purpose of initial access to a cell and acquisition of initial cell information for the terminal and (ii) resources scheduled or configured via RRC to transmit uplink signals / channels overlap each other in symbol units, the terminal operation is as follows.

[0261] 1) CG (configured grant) PUSCH Type 1 or CG PUSCH Type 2: If CG PUSCH Type 1 or CG PUSCH Type 2, that is, symbol(s) configured to transmit PUSCH via RRC and symbol(s) configured to receive SS / PBCH blocks partially overlap, the UE may receive the SS / PBCH block and rate-match the PUSCH for the PUSCH resources configured in the symbol overlapping with the SS / PBCH block and the position of the DL-to-UL switching gap symbol. This is because, even if the RBs occupied by the symbol(s) configured to transmit PUSCH from the upper layer and the RBs occupied by the symbol(s) configured to receive SS / PBCH blocks do not overlap each other, a UE operating in a half-duplex mode cannot simultaneously transmit and receive on different frequency resources of the same symbol. This method can guarantee the downlink reception and uplink transmission configured for the terminal to the maximum extent possible in symbol(s) excluding the same symbol(s) when the terminal is configured or instructed to operate in a subband.

[0262] If a symbol configured to transmit a PUSCH from a higher layer and a symbol configured to receive an SS / PBCH block completely overlap, the terminal may receive the SS / PBCH block but not the PUSCH. This is to prioritize reception of the SS / PBCH block, as a terminal operating in half-duplex mode cannot simultaneously transmit and receive in the same symbol.

[0263] 2) DG (dynamic grant) PUSCH: A UE may not expect to be instructed to transmit a PUSCH via DCI format 0_0, 0_1, or 0_2 in a symbol configured to receive an SS / PBCH block. This is to prioritize reception of SS / PBCH blocks, as a UE operating in half-duplex mode cannot simultaneously transmit and receive in the same symbol.

[0264] 3) RRC configured PUCCH: If the symbol specifically configured to receive SS / PBCH blocks and the resource configured via RRC to transmit PUCCH overlap each other on a symbol basis, the terminal may not transmit PUCCH in that slot. This is to prioritize reception of SS / PBCH blocks, as a terminal operating in a half-duplex mode cannot simultaneously transmit and receive in the same symbol.

[0265] 4) DCI indicated PUCCH: The UE may not expect to be instructed to transmit PUCCH via DCI format 1_0, 1_1, or 1_2 in a symbol configured to receive SS / PBCH blocks. This is to prioritize reception of SS / PBCH blocks, as a UE operating in half-duplex mode cannot simultaneously transmit and receive in the same symbol.

[0266] 5) RRC configured SRS: If the symbols specifically configured to receive SS / PBCH blocks and the resources configured via RRC to transmit SRS partially overlap in units of symbols, the terminal can receive SS / PBCH blocks in the overlapping symbol(s) and transmit SRS in the non-overlapping symbol(s). At this time, the terminal can receive SS / PBCH blocks and transmit SRS while considering the downlink-uplink switching gap symbol. That is, the terminal can receive SS / PBCH blocks in the overlapping symbol(s) and transmit SRS in the symbol(s) excluding the switching gap symbol among the non-overlapping symbol(s). Since the terminal can cancel or transmit the SRS on a symbol-by-symbol basis from the symbol(s) configured for SRS transmission, if the resources configured for the terminal to receive the SS / PBCH block and the resources configured for SRS transmission partially overlap in the time domain, the terminal can be guaranteed the maximum downlink reception and uplink transmission configured for the terminal.

[0267] If a symbol configured to transmit an SRS from a higher layer and a symbol configured to receive an SS / PBCH block completely overlap, the terminal may receive the SS / PBCH block but not the SRS. This is to prioritize reception of the SS / PBCH block, as a terminal operating in half-duplex mode cannot simultaneously transmit and receive in the same symbol.

[0268] 6) DCI indicated SRS: The UE may not expect to be instructed to transmit SRS via DCI format 0_0, 1_1, 0_1, 0_2 (if SRS request field is present) or 1_2 (if SRS request field is present) in a symbol configured to receive an SS / PBCH block. This is to prioritize reception of SS / PBCH blocks, as a UE operating in half-duplex mode cannot perform simultaneous transmission and reception in the same symbol.

[0269] - UE-specific SS / PBCH block with activated additional PCI:

[0270] (i) When resources specifically configured for the terminal to receive SS / PBCH blocks having additional PCI associated with activated TCI states among SS / PBCH blocks received from multiple TRPs for inter-cell beam management and (ii) resources scheduled or configured via RRC to transmit uplink signals / channels overlap each other on a symbol basis, the terminal operation is as follows.

[0271] 1) CG (configured grant) PUSCH Type 1 or CG PUSCH Type 2: If CG PUSCH Type 1 or CG PUSCH Type 2, that is, symbol(s) configured to transmit PUSCH via RRC and symbol(s) configured to receive SS / PBCH blocks partially overlap, the UE may receive the SS / PBCH block and rate-match the PUSCH for the PUSCH resources configured in the symbols overlapping with the SS / PBCH blocks and the positions of the downlink-uplink switching gap symbols. This is because, even if the RBs occupied by the symbol(s) configured to transmit PUSCH from the upper layer and the RBs occupied by the symbol(s) configured to receive SS / PBCH blocks do not overlap each other, a UE operating in a half-duplex mode cannot simultaneously transmit and receive on different frequency resources of the same symbol. This method can guarantee the downlink reception and uplink transmission configured for the terminal to the maximum extent possible in symbol(s) excluding the same symbol(s) when the terminal is configured or instructed to operate in a subband.

[0272] If a symbol configured to transmit a PUSCH from a higher layer and a symbol configured to receive an SS / PBCH block completely overlap, the terminal may receive the SS / PBCH block but not the PUSCH. This is to prioritize reception of the SS / PBCH block, as a terminal operating in half-duplex mode cannot simultaneously transmit and receive in the same symbol.

[0273] 2) DG (dynamic grant) PUSCH: A UE may not expect to be instructed to transmit a PUSCH via DCI format 0_0, 0_1, or 0_2 in a symbol configured to receive an SS / PBCH block. This is to prioritize reception of SS / PBCH blocks, as a UE operating in half-duplex mode cannot simultaneously transmit and receive in the same symbol.

[0274] 3) RRC configured PUCCH: If the symbol specifically configured to receive SS / PBCH blocks and the resource configured via RRC to transmit PUCCH overlap each other on a symbol basis, the terminal may not transmit PUCCH in that slot. This is to prioritize reception of SS / PBCH blocks, as a terminal operating in a half-duplex mode cannot simultaneously transmit and receive in the same symbol.

[0275] 4) DCI indicated PUCCH: The UE may not expect to be instructed to transmit PUCCH via DCI format 1_0, 1_1, or 1_2 in a symbol configured to receive SS / PBCH blocks. This is to prioritize reception of SS / PBCH blocks, as a UE operating in half-duplex mode cannot simultaneously transmit and receive in the same symbol.

[0276] 5) RRC configured SRS: If a symbol specifically configured to receive an SS / PBCH block and a resource configured via RRC to transmit an SRS partially overlap on a symbol basis, the UE can receive the SS / PBCH block on the overlapping symbol(s) and transmit the SRS on the non-overlapping symbol(s). At this time, the UE can receive the SS / PBCH block and transmit the SRS considering the downlink-uplink switching gap symbol. That is, the UE can receive the SS / PBCH block on the overlapping symbol(s) and transmit the SRS on the symbol(s) excluding the switching gap symbol among the non-overlapping symbol(s). Since the UE can cancel or transmit the SRS on a symbol basis in the symbol(s) configured for SRS transmission, the UE can guarantee the configured downlink reception and uplink transmission to the maximum extent when the resource configured to receive an SS / PBCH block and the resource configured to transmit an SRS partially overlap in the time domain.

[0277] If a symbol configured to transmit an SRS from a higher layer and a symbol configured to receive an SS / PBCH block completely overlap, the terminal may receive the SS / PBCH block but not the SRS. This is to prioritize reception of the SS / PBCH block, as a terminal operating in half-duplex mode cannot simultaneously transmit and receive in the same symbol.

[0278] 6) DCI indicated SRS: The UE may not expect to be instructed to transmit SRS via DCI format 0_0, 1_1, 0_1, 0_2 (if SRS request field is present) or 1_2 (if SRS request field is present) in a symbol configured to receive an SS / PBCH block. This is to prioritize reception of SS / PBCH blocks, as a UE operating in half-duplex mode cannot perform simultaneous transmission and reception in the same symbol.

[0279] - UE-specific SS / PBCH block with non-activated additional PCI:

[0280] (i) When resources specifically configured for the terminal to receive SS / PBCH blocks having additional PCI associated with inactive TCI states among SS / PBCH blocks received from multiple TRPs for inter-cell beam management and (ii) resources scheduled or configured via RRC to transmit uplink signals / channels overlap each other on a symbol basis, the terminal operation is as follows.

[0281] 1) CG (configured grant) PUSCH Type 1 or CG PUSCH Type 2: If CG PUSCH Type 1 or CG PUSCH Type 2, i.e., symbol(s) configured to transmit PUSCH via RRC and symbol(s) configured to receive SS / PBCH block partially or completely overlap, the UE may transmit PUSCH in that slot. That is, if the UE is configured via RRC to transmit PUSCH to overlap with symbol(s) specifically configured to receive SS / PBCH block with additional PCI associated with inactive TCI state, the UE may determine that the UE is configured to give priority to PUSCH transmission without receiving SS / PBCH block in that slot.

[0282] 2) DG (dynamic grant) PUSCH: When instructed to transmit PUSCH through DCI format 0_0, 0_1, or 0_2 in a symbol configured to receive an SS / PBCH block, the UE can transmit the PUSCH without receiving the SS / PBCH block in the corresponding slot. That is, from the perspective of a specific UE, scheduling PUSCH through dynamic scheduling from the base station to overlap with a symbol specifically configured for the UE to receive an SS / PBCH block can be determined as an instruction to give priority to PUSCH transmission without intending to receive an SS / PBCH block in the corresponding slot from the perspective of the specific UE. This is a method that allows the specific UE to transmit the PUSCH if it is dynamically scheduled by the base station in the uplink subband even if other UEs in the cell receive an SS / PBCH block in the downlink subband, since the base station supports a full-duplex communication method.

[0283] 3) RRC configured PUCCH: If the symbol specifically configured to receive SS / PBCH blocks and the resource configured via RRC to transmit PUCCH overlap each other on a symbol basis, the UE can transmit PUCCH in that slot. That is, if the UE is configured via RRC to transmit PUCCH to overlap with the symbol(s) specifically configured to receive SS / PBCH blocks with additional PCI associated with an inactive TCI state, the UE can determine that the UE is configured to give priority to PUCCH transmission and not receive SS / PBCH blocks in that slot.

[0284] 4) DCI indicated PUCCH: If the terminal is instructed to transmit a PUCCH through DCI format 1_0, 1_1, or 1_2 in a symbol configured to receive an SS / PBCH block, the terminal may transmit a PUCCH without receiving an SS / PBCH block in the corresponding slot. That is, from the perspective of a specific terminal, dynamic scheduling from the base station to overlap with a symbol specifically configured for the terminal to receive an SS / PBCH block may determine that the specific terminal is instructed to give priority to PUCCH transmission in the corresponding slot without intending to receive an SS / PBCH block from the perspective of the specific terminal. This is a method that allows the terminal to transmit the PUCCH if the specific terminal is dynamically scheduled by the base station in the uplink subband, even if other terminals in the cell receive an SS / PBCH block in the downlink subband, since the base station supports a full-duplex communication method.

[0285] 5) RRC configured SRS: If a symbol specifically configured to receive an SS / PBCH block and a resource configured via RRC to transmit an SRS partially or completely overlap on a symbol basis, the UE may transmit an SRS without receiving an SS / PBCH block in the overlapping symbol(s). That is, the UE may determine that a symbol configured via RRC to transmit an SRS to overlap with a symbol(s) specifically configured to receive an SS / PBCH block with an additional PCI associated with an inactive TCI state is configured to give priority to SRS transmission over receiving an SS / PBCH block in the slot.

[0286] 6) DCI indicated SRS: If the terminal is instructed to transmit SRS in a symbol configured to receive an SS / PBCH block through DCI format 0_0, 1_1, 0_1, 0_2 (if SRS request field is present) or 1_2 (if SRS request field is present), the terminal may transmit SRS without receiving the SS / PBCH block in the overlapping symbol(s). That is, from the perspective of a specific terminal, dynamic scheduling from the base station to overlap with a symbol specifically configured for the terminal to receive an SS / PBCH block may determine that the specific terminal does not intend to receive an SS / PBCH block in the slot and is instructed to give priority to SRS transmission. This is a method that allows the terminal to transmit the SRS if the specific terminal is dynamically scheduled by the base station in the uplink subband, even if other terminals in the cell receive an SS / PBCH block in the downlink subband, since the base station supports a full-duplex communication method.

[0287] - UE-specific SS / PBCH block for L1 beam measurement / reporting:

[0288] (i) When resources specifically configured for the terminal to receive SS / PBCH blocks for link recovery and (ii) resources scheduled or configured via RRC to transmit uplink signals / channels overlap each other on a symbol basis, the terminal behavior is as follows.

[0289] 1) CG (configured grant) PUSCH Type 1 or CG PUSCH Type 2: If the symbol(s) configured to transmit the PUSCH through RRC overlap with the symbol(s) configured to receive the SS / PBCH block, the UE may receive the SS / PBCH block and rate-match the PUSCH for the PUSCH resources configured in the symbol overlapping with the SS / PBCH block and the position of the DL-to-UL switching gap symbol. This is because, even if the RBs occupied by the symbol(s) configured to transmit the PUSCH from the upper layer and the RBs occupied by the symbol(s) configured to receive the SS / PBCH block do not overlap with each other, a UE operating in a half-duplex mode cannot simultaneously transmit and receive on different frequency resources of the same symbol. This method can guarantee the downlink reception and uplink transmission configured for the terminal to the maximum extent possible in symbol(s) excluding the same symbol(s) when the terminal is configured or instructed to operate in a subband.

[0290] If a symbol configured to transmit a PUSCH from a higher layer and a symbol configured to receive an SS / PBCH block completely overlap, the terminal may receive the SS / PBCH block but not the PUSCH. This is to prioritize reception of the SS / PBCH block, as a terminal operating in half-duplex mode cannot simultaneously transmit and receive in the same symbol.

[0291] 2) DG (dynamic grant) PUSCH: If a terminal is instructed to transmit a PUSCH through DCI format 0_0, 0_1, or 0_2 in a symbol configured to receive an SS / PBCH block, the terminal may transmit the PUSCH without receiving an SS / PBCH block in the corresponding slot. That is, from the perspective of a specific terminal, dynamic scheduling from the base station to overlap with a symbol specifically configured for the terminal to receive an SS / PBCH block may determine that the specific terminal does not intend to receive an SS / PBCH block in the corresponding slot and is instructed to give priority to PUSCH transmission. This is a method that allows the terminal to transmit the PUSCH if the specific terminal is dynamically scheduled by the base station in the uplink subband, even if other terminals in the cell receive an SS / PBCH block in the downlink subband, since the base station supports a full-duplex communication method.

[0292] 3) RRC configured PUCCH: If the symbol specifically configured to receive SS / PBCH blocks and the resource configured via RRC to transmit PUCCH overlap each other on a symbol basis, the terminal may not transmit PUCCH in that slot. This is to prioritize reception of SS / PBCH blocks, as a terminal operating in a half-duplex mode cannot simultaneously transmit and receive in the same symbol.

[0293] 4) DCI indicated PUCCH: If the terminal is instructed to transmit a PUCCH through DCI format 1_0, 1_1, or 1_2 in a symbol configured to receive an SS / PBCH block, the terminal may transmit a PUCCH without receiving an SS / PBCH block in the corresponding slot. That is, from the perspective of a specific terminal, dynamic scheduling from the base station to overlap with a symbol specifically configured for the terminal to receive an SS / PBCH block may determine that the specific terminal is instructed to give priority to PUCCH transmission in the corresponding slot without intending to receive an SS / PBCH block from the perspective of the specific terminal. This is a method that allows the terminal to transmit the PUCCH if the specific terminal is dynamically scheduled by the base station in the uplink subband, even if other terminals in the cell receive an SS / PBCH block in the downlink subband, since the base station supports a full-duplex communication method.

[0294] 5) RRC configured SRS: If a symbol specifically configured to receive an SS / PBCH block and a resource configured via RRC to transmit an SRS partially overlap in symbol units, the UE can receive the SS / PBCH block in the overlapping symbol(s) and transmit the SRS in the non-overlapping symbol(s). At this time, the UE can receive the SS / PBCH block and transmit the SRS considering the downlink-uplink switching gap symbol. That is, the UE can receive the SS / PBCH block in the overlapping symbol(s) and transmit the SRS in the symbol(s) excluding the switching gap symbol among the non-overlapping symbol(s). Since the UE can cancel or transmit the SRS in symbol units in the symbol(s) configured for SRS transmission, if the resource configured to receive an SS / PBCH block and the resource configured to transmit an SRS partially overlap in the time domain, the configured downlink reception and uplink transmission of the UE can be guaranteed to the greatest extent possible.

[0295] If a symbol configured to transmit an SRS from a higher layer and a symbol configured to receive an SS / PBCH block completely overlap, the terminal may receive the SS / PBCH block but not the SRS. This is to prioritize reception of the SS / PBCH block, as a terminal operating in half-duplex mode cannot simultaneously transmit and receive in the same symbol.

[0296] 6) DCI indicated SRS: If the terminal is instructed to transmit SRS in a symbol configured to receive an SS / PBCH block through DCI format 0_0, 1_1, 0_1, 0_2 (if SRS request field is present) or 1_2 (if SRS request field is present), the terminal may transmit SRS without receiving the SS / PBCH block in the overlapping symbol(s). That is, from the perspective of a specific terminal, dynamic scheduling from the base station to overlap with a symbol specifically configured for the terminal to receive an SS / PBCH block may determine that the specific terminal does not intend to receive an SS / PBCH block in the slot and is instructed to give priority to SRS transmission. This is a method that allows the terminal to transmit the SRS if the specific terminal is dynamically scheduled by the base station in the uplink subband, even if other terminals in the cell receive an SS / PBCH block in the downlink subband, since the base station supports a full-duplex communication method.

[0297] - UE-specific SS / PBCH block for SMTC (SSB-based measurement timing configuration):

[0298] (i) When resources specifically configured for the terminal to additionally receive SS / PBCH blocks within a terminal-specific SMTC window from a base station for measuring downlink channel states received from a serving cell and / or neighboring cells and (ii) resources scheduled or configured via RRC to transmit uplink signals / channels overlap each other on a symbol basis, the terminal operation is as follows.

[0299] 1) CG (configured grant) PUSCH Type 1 or CG PUSCH Type 2: If CG PUSCH Type 1 or CG PUSCH Type 2, that is, symbol(s) configured to transmit PUSCH via RRC and symbol(s) configured to receive SS / PBCH blocks partially overlap, the UE may receive the SS / PBCH block and rate-match the PUSCH for the PUSCH resources configured in the symbols overlapping with the SS / PBCH blocks and the positions of the downlink-uplink switching gap symbols. This is because, even if the RBs occupied by the symbol(s) configured to transmit PUSCH from the upper layer and the RBs occupied by the symbol(s) configured to receive SS / PBCH blocks do not overlap each other, a UE operating in a half-duplex mode cannot simultaneously transmit and receive on different frequency resources of the same symbol. This method can guarantee the downlink reception and uplink transmission configured for the terminal to the maximum extent possible in symbol(s) excluding the same symbol(s) when the terminal is configured or instructed to operate in a subband.

[0300] If a symbol configured to transmit a PUSCH from a higher layer and a symbol configured to receive an SS / PBCH block completely overlap, the terminal may receive the SS / PBCH block but not the PUSCH. This is to prioritize reception of the SS / PBCH block, as a terminal operating in half-duplex mode cannot simultaneously transmit and receive in the same symbol.

[0301] 2) DG (dynamic grant) PUSCH: When instructed to transmit PUSCH through DCI format 0_0, 0_1, or 0_2 in a symbol configured to receive an SS / PBCH block, the UE can transmit the PUSCH without receiving the SS / PBCH block in the corresponding slot. That is, from the perspective of a specific UE, scheduling PUSCH through dynamic scheduling from the base station to overlap with a symbol specifically configured for the UE to receive an SS / PBCH block can be determined as an instruction to give priority to PUSCH transmission without intending to receive an SS / PBCH block in the corresponding slot from the perspective of the specific UE. This is a method that allows the specific UE to transmit the PUSCH if it is dynamically scheduled by the base station in the uplink subband even if other UEs in the cell receive an SS / PBCH block in the downlink subband, since the base station supports a full-duplex communication method.

[0302] 3) RRC configured PUCCH: If the symbol specifically configured to receive SS / PBCH blocks and the resource configured via RRC to transmit PUCCH overlap each other on a symbol basis, the terminal may not transmit PUCCH in that slot. This is to prioritize reception of SS / PBCH blocks, as a terminal operating in a half-duplex mode cannot simultaneously transmit and receive in the same symbol.

[0303] 4) DCI indicated PUCCH: If the terminal is instructed to transmit a PUCCH through DCI format 1_0, 1_1, or 1_2 in a symbol configured to receive an SS / PBCH block, the terminal may transmit a PUCCH without receiving an SS / PBCH block in the corresponding slot. That is, from the perspective of a specific terminal, dynamic scheduling from the base station to overlap with a symbol specifically configured for the terminal to receive an SS / PBCH block may determine that the specific terminal is instructed to give priority to PUCCH transmission in the corresponding slot without intending to receive an SS / PBCH block from the perspective of the specific terminal. This is a method that allows the terminal to transmit the PUCCH if the specific terminal is dynamically scheduled by the base station in the uplink subband, even if other terminals in the cell receive an SS / PBCH block in the downlink subband, since the base station supports a full-duplex communication method.

[0304] 5) RRC configured SRS: If the symbols configured cell-specifically to receive SS / PBCH blocks and the resources configured via RRC to transmit SRS partially overlap in units of symbols, the terminal can receive SS / PBCH blocks in the overlapping symbol(s) and transmit SRS in the non-overlapping symbol(s). At this time, the terminal can receive SS / PBCH blocks and transmit SRS while considering downlink-uplink switching gap symbols. That is, the terminal can receive SS / PBCH blocks in the overlapping symbol(s) and transmit SRS in the symbol(s) excluding the switching gap symbol among the non-overlapping symbol(s). Since the terminal can cancel or transmit the SRS on a symbol-by-symbol basis in the symbol(s) configured for SRS transmission, if the resources configured to receive the SS / PBCH block and the resources configured to transmit the SRS overlap in the time domain, the terminal can be guaranteed the maximum downlink reception and uplink transmission configured for the terminal.

[0305] If a symbol configured to transmit an SRS from a higher layer and a symbol configured to receive an SS / PBCH block completely overlap, the terminal may receive the SS / PBCH block but not the SRS. This is to prioritize reception of the SS / PBCH block, as a terminal operating in half-duplex mode cannot simultaneously transmit and receive in the same symbol.

[0306] 6) DCI indicated SRS: If the terminal is instructed to transmit SRS in a symbol configured to receive an SS / PBCH block through DCI format 0_0, 1_1, 0_1, 0_2 (if SRS request field is present) or 1_2 (if SRS request field is present), the terminal may transmit SRS without receiving the SS / PBCH block in the overlapping symbol(s). That is, from the perspective of a specific terminal, dynamic scheduling from the base station to overlap with a symbol specifically configured for the terminal to receive an SS / PBCH block may determine that the specific terminal does not intend to receive an SS / PBCH block in the slot and is instructed to give priority to SRS transmission. This is a method that allows the terminal to transmit the SRS if the specific terminal is dynamically scheduled by the base station in the uplink subband, even if other terminals in the cell receive an SS / PBCH block in the downlink subband, since the base station supports a full-duplex communication method.

[0307] [2] Uplink transmission

[0308] In the NR system, the terminal receives SS / PBCH blocks (or SSBs) from the base station to perform initial cell access, radio resource management (RRM), radio link monitoring (RLM), beam management, and mobility management.

[0309] When SSB is associated with RMSI (remaining system information), the SSB is referred to as CD-SSB (Cell-Defining SS / PBCH block). Here, RMSI may include SIB1 (system information block 1). SIB1 is information that the UE receives from the base station for synchronization acquisition, system information acquisition, etc., and may be received by being included in the PDSCH. In order to receive a PDSCH including SIB1, the UE may monitor a CORESET associated with a Type0-PDCCH CSS (common search space) set to receive a PDCCH, and decode the PDCCH to obtain DCI. Through the DCI, the UE may obtain scheduling information of a PDSCH including SIB1 (hereinafter, PDSCH with SIB1; or simply referred to as PDSCH depending on the context). Hereinafter, a CORESET associated with a Type0-PDCCH CSS set is referred to as CORESET0 or CORESET#0. As the opposite concept of CD-SSB, when an SSB is not associated with RMSI, it is called NCD-SSB (non-cell-defining SSB). PCell always includes CD-SSB within the synchronization raster. That is, CD-SSB can be transmitted in any frequency range within the synchronization raster in PCell.

[0310] Referring to FIG. 19, (i) PDSCH including CORESET0 and (ii) SIB1 can be TDM or FDM with CD-SSB. The terminal can determine one of multiplexing pattern 1 in which SSB, CORESET0 and PDSCH are TDM, multiplexing pattern 2 in which SSB and CORESET0 are TDM and SSB and PDSCH are FDM, and multiplexing pattern 3 in which SSB, CORESET0 and PDSCH are FDM, which can be determined according to the frequency band of the cell in which the terminal operates. If the frequency band of the cell in which the terminal operates is 6 GHz or less, multiplexing pattern 1 is used. If the frequency band of the cell in which the terminal operates is 6 GHz or more, one of multiplexing patterns 1 to 3 can be used. If the terminal is before the RRC connection, the time / frequency domain position for receiving the multiplexing pattern and CORESET0 can be determined based on information received through the MIB (master information block) and PBCH payload received through the PBCH. If the terminal is after the RRC connection, the time / frequency domain position for receiving the multiplexing pattern and CORESET0 can be determined based on information configured through the RRC signal. Here, the time / frequency domain position for receiving CORESET0 can include the number of symbols of CORESET0, the number of RBs, the RB offset with respect to the SSB, the number of CSS sets within a slot of the Type0-PDCCH CSS set, the monitoring period and offset per slot, and the first symbol index within the slot.

[0311] The problem to be solved in the present invention is about the operation of a terminal when a symbol configured to receive CORESET0 to obtain RMSI associated with CD-SSB is included in an uplink subband or guard band and uplink transmission is scheduled on the corresponding resource when a terminal that has completed an RRC connection is configured or instructed to operate as a subband. Referring to Fig. 20, in a terminal configured or instructed to operate as a subband, a symbol configured to receive CORESET0 associated with CD-SSB may overlap with a symbol allocated to an uplink subband. Fig. 20(a) illustrates SSB & CORESET0 multiplexing pattern 3, and Fig. 20(b) illustrates SSB & CORESET0 multiplexing pattern 1. When a terminal is configured or instructed to operate in a subband to increase uplink coverage, reduce uplink latency, or increase uplink capacity, the terminal may be scheduled to transmit uplink signals / channels by maximizing uplink subband resources. Here, the symbols operating in the subband may include at least cell-specific downlink / flexible symbols. Therefore, symbols configured to receive CORESET0 and symbols configured or instructed to transmit uplink signals / channels may overlap in the same resource. Since a terminal supporting half-duplex operation supports only one of downlink reception or uplink transmission operations in the same resource, a method is proposed to address this issue.

[0312] For example, a terminal may monitor PDCCH in a resource configured with CORESET0. Even after completing the RRC connection, the terminal is configured to periodically monitor PDCCH in the Type0-PDCCH CSS set associated with CORESET0 to receive SIB1 for purposes such as receiving other system information (OSI) and validating public land mobile network selection (PLMN) identity. Accordingly, even if a resource configured with CORESET0 is included in an uplink subband or guard band, PDCCH monitoring may be performed and uplink signals / channels may not be transmitted.

[0313] According to the above example, when a terminal performs PDCCH monitoring in a symbol overlapping with a symbol configured to receive CORESET0 among symbols scheduled for uplink signal / channel transmission, the terminal can receive a PDSCH including SIB1 based on scheduling information in the DCI received by decoding the corresponding PDCCH. At this time, the terminal can perform transmission of some uplink signals / channels in symbols other than the symbol configured to receive CORESET0 and the symbol instructed to receive a PDSCH including SIB1 among symbols scheduled for uplink signal / channel transmission. Hereinafter, a terminal operation according to an SSB & CORESET0 multiplexing pattern and an uplink signal / channel is proposed.

[0314] 1) SSB & CORESET0 Multiplexing Pattern 2 / 3: Fig. 21 shows an example proposed in the present invention. A terminal may be configured to operate in a subband or may be scheduled to transmit an uplink signal / channel over 14 symbols in an uplink subband within an instructed slot. Fig. 21(a) illustrates SSB & CORESET0 Multiplexing Pattern 2, and may be configured to receive CORESET0 over 1 symbol and SSB and PDSCH over 4 symbols. Fig. 21(b) illustrates SSB & CORESET0 Multiplexing Pattern 3, and may be configured to receive SSB, CORESET0, and PDSCH over 4 symbols. The terminal must monitor the PDCCH in CORESET0 to receive DCI to know the time / frequency domain location of the PDSCH. However, in SSB & CORESET0 multiplexing patterns 2 / 3, the symbol instructed to receive PDSCH is included in the symbol configured to receive CD-SSB. Therefore, even before receiving DCI, the terminal may determine only the configured SSB symbol, the symbol configured to receive CORESET0, and the switching gap symbol between downlink reception and uplink transmission for RF retuning of the terminal as invalid symbols for uplink transmission and may not perform uplink transmission in the corresponding symbols. The terminal operation according to the uplink signal / channel in the symbols excluding the invalid symbols is as follows.

[0315] - PUSCH: The UE can rate-match and transmit the PUSCH for the PUSCH resources instructed by DCI format 0_0, 0_1, or 0_2 or configured from a higher layer at the locations of the SSB symbol, the symbol configured to receive CORESET0, and the DL-to-UL switching gap symbol. Referring to Fig. 21(a), the UE can transmit the PUSCH in 8 symbols excluding 1 symbol configured to receive CORESET0, 4 symbols configured to receive SSB, and 1 symbol of DL-to-UL switching gap among 14 symbols instructed or configured to transmit the PUSCH. Referring to Fig. 21(b), the UE can transmit the PUSCH in 9 symbols excluding 4 symbols configured to receive CORESET0 and SSB, and 1 symbol of DL-to-UL switching gap among 14 symbols instructed or configured to transmit the PUSCH. The present method can guarantee the downlink reception and uplink transmission configured for the terminal to the maximum extent possible in symbol(s) excluding symbols for downlink reception and symbol(s) overlapping with DL-to-UL switching gap symbols when the terminal is configured or instructed to operate in a subband.

[0316] - SRS: The UE can transmit SRS in symbols excluding SSB symbols, symbols configured to receive CORESET0, and DL-to-UL switching gap symbols among SRS resources instructed through DCI format 0_0, 0_1, or 0_2 or configured from a higher layer. Referring to Fig. 21(a), the UE can transmit SRS within 8 symbols excluding 1 symbol configured to receive CORESET0, 4 symbols configured to receive SSB, and 1 DL-to-UL switching gap symbol among 14 symbols instructed or configured to transmit SRS. Referring to Fig. 21(b), the UE can transmit SRS within 9 symbols excluding 4 symbols configured to receive CORESET0 and SSB, and 1 DL-to-UL switching gap symbol among 14 symbols instructed or configured to transmit SRS. The present method can guarantee the downlink reception and uplink transmission configured for the terminal to the maximum extent possible in symbol(s) excluding symbols for downlink reception and symbol(s) overlapping with DL-to-UL switching gap symbols when the terminal is configured or instructed to operate in a subband.

[0317] 2) SSB & CORESET0 Multiplexing Pattern 1: Unlike SSB & CORESET0 Multiplexing Patterns 2 / 3, in Multiplexing Pattern 1, SSB / CORESET0 / PDSCH are TDM, so the UE cannot know the time / frequency domain location of the PDSCH before receiving CORESET0. The present invention proposes methods depending on whether a symbol configured or instructed to transmit an uplink signal / channel overlaps with a symbol configured to receive CORESET0 and / or overlaps with a symbol instructed to receive a PDSCH.

[0318] Fig. 22 shows an example proposed in the present invention. Fig. 22 shows a situation where a symbol configured to receive CORESET0 associated with CD-SSB overlaps with a symbol configured or instructed to transmit an uplink signal / channel in an uplink subband, assuming SSB & CORESET multiplexing pattern 1. The terminal may be scheduled to transmit an uplink signal / channel through 14 symbols in an uplink subband within a slot configured or instructed to operate in a subband. Here, 3 symbols out of the 14 symbols may be symbols configured to receive CORESET0 for the terminal. The terminal may transmit an uplink signal / channel in symbols other than the symbol configured to receive CORESET0 and the DL-to-UL switching gap symbol. The terminal operation according to the uplink signal / channel is as follows.

[0319] - PUSCH: The UE can rate-match and transmit the PUSCH for the PUSCH resource configured by the upper layer (e.g., RRC) or instructed through the DCI format (e.g., DCI format 0_0, 0_1, or 0_2) at the symbol configured to receive CORESET0 and the position of the DL-to-UL switching gap symbol. Accordingly, the PUSCH transmission on the corresponding PUSCH resource can be canceled. In FIG. 22, among the 14 symbols instructed or configured to transmit the PUSCH, the PUSCH can be transmitted in 10 symbols excluding 3 symbols configured to receive CORESET0 and 1 symbol of the DL-to-UL switching gap. When the UE is configured or instructed to operate in a subband, the present method can guarantee the downlink reception and uplink transmission configured for the UE to the greatest extent possible in the symbol(s) excluding the symbol(s) for downlink reception and the symbol(s) overlapping with the DL-to-UL switching gap symbol.

[0320] - SRS: The terminal can transmit SRS in the remaining symbols excluding the symbols configured to receive CORESET0 and the DL-to-UL switching gap symbols among the SRS resources instructed through the DCI format (e.g., DCI format 0_0, 0_1, or 0_2) or configured from the upper layer (e.g., RRC). In FIG. 22, the SRS can be transmitted within 10 symbols excluding the 3 symbols configured to receive CORESET0 and the 1 symbol of the DL-to-UL switching gap among the 14 symbols instructed or configured to transmit SRS. When the terminal is configured or instructed to operate in a subband, the present method can guarantee the downlink reception and uplink transmission configured for the terminal to the greatest extent possible in the symbol(s) excluding the symbol(s) for downlink reception and the symbol(s) overlapping with the DL-to-UL switching gap symbol.

[0321] Figures 23 and 24 show examples proposed in the present invention.

[0322] FIG. 23 illustrates a situation in which a symbol instructed to receive a PDSCH (i.e., PDSCH with SIB1) scheduled by CORESET0 associated with a CD-SSB overlaps with a symbol configured or instructed to transmit an uplink signal / channel in an uplink subband, assuming SSB & CORESET multiplexing pattern 1. The terminal may be scheduled to transmit an uplink signal / channel through 8 symbols in an uplink subband within a slot configured or instructed to operate in a subband. Here, 2 of the 8 symbols may be symbols instructed to receive a PDSCH with SIB1 for the terminal.

[0323] FIG. 24 illustrates a situation where a symbol instructed to receive PDSCH with SIB1 scheduled by CORESET0 associated with CD-SSB overlaps with a symbol configured or instructed to transmit an uplink signal / channel in an uplink subband, assuming SSB & CORESET multiplexing pattern 1. The terminal may be scheduled to transmit an uplink signal / channel through 10 symbols in an uplink subband within a slot configured or instructed to operate in a subband. Here, 2 of the 8 symbols may be symbols instructed to receive PDSCH with SIB1 for the terminal.

[0324] In FIGS. 23 and 24, the terminal may transmit an uplink signal / channel in a symbol other than a symbol and a gap symbol (e.g., a DL-to-UL switching gap symbol) instructed to receive PDSCH with SIB1. At this time, the terminal operation according to the uplink signal / channel may additionally consider whether the interval between the last symbol configured to receive CORESET0 and the first symbol configured or instructed to transmit PUSCH satisfies a timeline condition. The timeline condition is T, which is a PUSCH preparation time according to the terminal processing capability. proc,2 It can be decided according to .

[0325] Refer to 3GPP TS 38.214 Rel-15 for T proc,2 is defined as follows:

[0326]

[0327]

[0328]

[0329] Hereinafter, when additional timeline conditions are considered in this specification, terminal operations according to uplink signals / channels are as follows.

[0330] - DG (dynamic grant) PUSCH: If the PUSCH resource indicated through the DCI format (e.g., DCI format 0_0, 0_1, or 0_2) for PUSCH scheduling overlaps with the symbol indicated to the UE to receive PDSCH with SIB1 and the position of the DL-to-UL switching gap symbol, the UE operates as follows.

[0331] For example, if 1) the terminal does not indicate partialCancellation capability to the base station, and 2) the first symbol instructed to transmit PUSCH is the last symbol of the CORESET that detects the PDCCH including the DCI format indicating reception of PDSCH with SIB1, then T proc,2 If the symbol is within, the terminal may not expect to cancel the PUSCH transmission in the slot. That is, the terminal may transmit the PUSCH in the slot and not receive the PDSCH with SIB1. In FIG. 24, since the timeline condition between the last symbol configured to receive CORESET0 and the first symbol configured or instructed to transmit the PUSCH is not satisfied, the terminal may transmit the PUSCH in the slot and not receive the PDSCH with SIB1. Here, the partialCancellation capability is a capability of the terminal to cancel the uplink transmission in the symbol(s) and perform the uplink transmission in the remaining symbol(s) when the uplink transmission is impossible in some symbol(s) during the transmission of the uplink channel (PUSCH, PUCCH, or PRACH) configured or instructed by the terminal from the base station.

[0332] For example, if 1) the terminal does not indicate partialCancellation capability to the base station, and 2) the first symbol instructed to transmit PUSCH is the last symbol of the CORESET that detects the PDCCH including the DCI format indicating reception of PDSCH with SIB1, then T proc,2 In the case of the subsequent symbols, the UE can transmit the PUSCH by rate-matching it. Referring to FIG. 23, the UE can transmit the PUSCH in five symbols, excluding two symbols configured to receive PDSCH with SIB1 and one symbol of DL-to-UL switching gap, among eight symbols instructed to transmit the PUSCH. Alternatively, the UE can transmit the PUSCH in symbols following the reception of PDSCH with SIB1 and one symbol of DL-to-UL switching gap. For example, referring to FIG. 23, the UE can transmit the PUSCH in four symbols following two symbols configured to receive PDSCH with SIB1 and one symbol of DL-to-UL switching gap, among eight symbols instructed to transmit the PUSCH. That is, PUSCH transmission can be canceled (e.g., rate-matched) in two symbols configured to receive PDSCH with SIB1 and one symbol of DL-to-UL switching gap. The present method can guarantee the downlink reception and uplink transmission configured for the terminal to the maximum extent possible in the symbol(s) excluding the symbol(s) overlapping with the symbol for downlink reception and the DL-to-UL switching gap symbol, when the timeline condition is satisfied and the terminal is configured or instructed to operate in a subband. This example is for the case where 1) the terminal indicates partialCancellation capability to the base station, and 2) the first symbol instructed to transmit PUSCH includes a DCI format indicating reception of PDSCH with SIB1, starting from the last symbol of the CORESET that detects the PDCCH. proc,2The same can be applied to subsequent symbols.

[0333] For example, if 1) the terminal has indicated partialCancellation capability to the base station, and 2) the first symbol instructed to transmit PUSCH is the last symbol of the CORESET that detects the PDCCH including the DCI format indicating reception of PDSCH with SIB1, then T proc,2 If the symbols are within the range, the terminal may not expect to cancel PUSCH transmission in those symbols. That is, the terminal may transmit PUSCH in those symbols.

[0334] However, among the symbols for one PUSCH transmission, T proc,2 Symbols within and T proc,2 If there is a symbol after T proc,2 For subsequent symbols, the terminal can rate-match and transmit the PUSCH by considering resources overlapping with the PDSCH with SIB1 resources. That is, T proc,2 For subsequent symbols, the terminal may cancel PUSCH transmission (e.g., rate-matching) in resources that overlap with PDSCH with SIB1 resources. In this case, the terminal may detect a PDCCH including a DCI format indicating PDSCH reception starting from the last symbol of the CORESET in which the symbol instructed to transmit the PUSCH includes a PDCCH instructing PDSCH reception. proc,2 If the symbol is within T, the terminal does not perform PDSCH reception in the symbol. proc,2 In the following symbols, PDSCH reception and PUSCH transmission can be performed. Referring to FIG. 23, the terminal can transmit the PUSCH in five symbols, excluding two symbols configured to receive PDSCH with SIB1 and one symbol of DL-to-UL switching gap, among eight symbols instructed to transmit the PUSCH. Referring to FIG. 24, the terminal can transmit the PUSCH in T among ten symbols instructed to transmit the PUSCH. proc,2Transmit PUSCH in the previous two symbols, and T proc,2 Among the following eight symbols, PUSCH can be transmitted in five symbols, excluding two symbols configured to receive PDSCH with SIB1 and one symbol for DL-to-UL switching gap.

[0335] Additionally, the UE can transmit the PUSCH in the symbols following the reception of the PDSCH with SIB1 and the DL-to-UL switching gap of one symbol. Referring to FIG. 23, the UE can transmit the PUSCH in the 4 symbols following the 2 symbols configured to receive the PDSCH with SIB1 and the 1 symbol of the DL-to-UL switching gap among the 8 symbols instructed to transmit the PUSCH. Referring to FIG. 24, the UE can transmit the PUSCH in the 4 symbols following the 2 symbols configured to receive the PDSCH with SIB1 and the 1 symbol of the DL-to-UL switching gap among the 10 symbols instructed to transmit the PUSCH.

[0336] - CG (configured grant) PUSCH: When the symbol instructing the terminal to receive PDSCH with SIB1 and the PUSCH resource configured from the upper layer overlap at the position of the DL-to-UL switching gap symbol, the terminal operation is as follows.

[0337] For example, if 1) the terminal has not indicated partialCancellation capability to the base station, and 2) the first symbol configured to transmit PUSCH is the last symbol of the CORESET that detects the PDCCH including the DCI format indicating reception of PDSCH with SIB1, then T proc,2If the symbol is within, the terminal may not determine the slot as a valid opportunity for PUSCH transmission. That is, the terminal may receive PDSCH with SIB1 in the slot and not transmit PUSCH. Referring to FIG. 24, since the timeline condition between the last symbol configured to receive CORESET0 and the first symbol configured or instructed to transmit PUSCH is not satisfied, the terminal may not determine the slot as a valid opportunity for PUSCH transmission and may receive PDSCH with SIB1.

[0338] For example, if 1) the terminal has not indicated partialCancellation capability to the base station, and 2) the first symbol configured to transmit PUSCH is the last symbol of the CORESET that detects the PDCCH including the DCI format indicating reception of PDSCH with SIB1, then T proc,2In the case of the subsequent symbols, the UE can rate-match and transmit the PUSCH. Accordingly, the UE can cancel PUSCH transmission in some symbols. Referring to FIG. 23, the UE can transmit the PUSCH in five symbols, excluding two symbols configured to receive PDSCH with SIB1 and one symbol of DL-to-UL switching gap, among eight symbols instructed to transmit the PUSCH. Alternatively, the UE can transmit the PUSCH in symbols following reception of the PDSCH with SIB1 and one symbol of DL-to-UL switching gap. For example, referring to FIG. 23, the UE can transmit the PUSCH in four symbols following two symbols configured to receive PDSCH and one symbol of DL-to-UL switching gap, among eight symbols instructed to transmit the PUSCH. The present method can guarantee the downlink reception and uplink transmission configured for the terminal to the maximum extent possible in the symbol(s) excluding the symbol(s) overlapping with the symbol for downlink reception and the DL-to-UL switching gap symbol when the timeline condition is satisfied and the terminal is configured or instructed to operate in a subband. In this example, 1) the terminal indicates partialCancellation capability to the base station, and 2) the first symbol instructed to transmit the PUSCH includes a DCI format indicating reception of the PDSCH with SIB1, starting from the last symbol of the CORESET that detects the PDCCH. proc,2 The same can be applied to subsequent symbols.

[0339] For example, if 1) the terminal has indicated partialCancellation capability to the base station, and 2) the first symbol instructed to transmit PUSCH is the last symbol of the CORESET that detects the PDCCH including the DCI format indicating reception of PDSCH with SIB1, then T proc,2If the symbol is within the range, the terminal may not expect to cancel the PUSCH transmission in that symbol. That is, the terminal may transmit the PUSCH in those symbols.

[0340] However, among the symbols for one PUSCH transmission, T proc,2 Symbols within and T proc,2 T if there is a symbol after proc,2 In subsequent symbols, the terminal can rate-match and transmit the PUSCH by considering resources overlapping with the PDSCH with SIB1 resources. In this case, the terminal detects the PDCCH including the DCI format indicating PDSCH reception from the last symbol of the CORESET in which the symbol instructed to transmit the PUSCH is T proc,2 If the symbol is within T, the terminal does not perform PDSCH with SIB1 reception in the symbol. proc,2 In the following symbols, PDSCH with SIB1 reception and PUSCH transmission can be performed. Referring to FIG. 23, the UE can transmit the PUSCH in 10 symbols excluding 2 symbols configured to receive PDSCH with SIB1 and symbols for downlink reception and 1 symbol for DL-to-UL switching gap among 8 symbols instructed to transmit the PUSCH. Referring to FIG. 23, the UE can transmit the PUSCH in 5 symbols excluding 2 symbols configured to receive PDSCH with SIB1 and symbols for downlink reception and 1 symbol for DL-to-UL switching gap among 8 symbols instructed to transmit the PUSCH. Referring to FIG. 24, the UE can transmit the PUSCH in T among 10 symbols instructed to transmit the PUSCH. proc,2 Transmit PUSCH in the previous two symbols, and T proc,2 Among the following eight symbols, PUSCH can be transmitted in five symbols, excluding two symbols configured to receive PDSCH with SIB1 and one symbol for DL-to-UL switching gap.

[0341] In addition, the terminal can transmit the PUSCH in the symbols following the reception of the PDSCH with SIB1 and one symbol of the DL-to-UL switching gap. Referring to FIG. 23, the terminal can transmit the PUSCH in the four symbols following the excluding two symbols configured to receive the PDSCH with SIB1 and one symbol of the DL-to-UL switching gap among the eight symbols instructed to transmit the PUSCH. In addition, the terminal can transmit the PUSCH in the symbols following the reception of the PDSCH with SIB1 and one symbol of the DL-to-UL switching gap. Referring to FIG. 24, the terminal can transmit the PUSCH in the four symbols following the excluding two symbols configured to receive the PDSCH with SIB1 and one symbol of the DL-to-UL switching gap among the ten symbols instructed to transmit the PUSCH.

[0342] - SRS: The UE can transmit SRS in symbols excluding symbols instructed to receive PDSCH with SIB1 and DL-to-UL switching gap symbols among SRS resources instructed through DCI format (e.g., DCI format 0_0, 0_1, or 0_2) or configured from a higher layer (e.g., RRC). Referring to FIG. 23, the UE can transmit SRS in five symbols excluding two symbols configured to receive PDSCH with SIB1 and one DL-to-UL switching gap symbol among eight symbols instructed or configured to transmit SRS. When the UE is configured or instructed to operate in a subband, the present method can guarantee downlink reception and uplink transmission configured for the UE to the greatest extent possible in symbol(s) excluding symbols for downlink reception and symbol(s) overlapping with DL-to-UL switching gap symbols.

[0343] In addition, the UE may not expect that the symbols configured or instructed to transmit the uplink signal / channel overlap both the symbols configured for CORESET0 and the symbols instructed to receive the PDSCH (i.e., PDSCH with SIB1). If the UE schedules the transmission of the uplink signal / channel to overlap both the symbols configured or instructed for reception of the CORESET0 and the PDSCH with SIB1, additional DL-to-UL switching gap symbols (switching gap symbols between reception of the CORESET0 and transmission of the UL signal / channel, switching gap symbols between reception of the PDSCH and transmission of the UL signal / channel) must be taken into account, resulting in insufficient resources available for data transmission and reception. Therefore, the UE may not expect that the transmission of the uplink signal / channel is scheduled to overlap both the symbols configured or instructed for reception of the CORESET0 and the PDSCH with SIB1.

[0344] [3] PDCCH reception on SBFD operation

[0345] The terminal can receive a PDCCH transmitted from the base station. The terminal can set information such as a CORESET and a search space to receive the PDCCH from the base station.

[0346] A CORESET may include information about the frequency domain in which the PDCCH should be received. Specifically, the base station may provide information about the CORESET to the terminal, and the information about the CORESET may include the index of the sets of Physical Resource Blocks (PRBs) in which the terminal should receive the PDCCH and the number of consecutive symbols. In this case, the number of consecutive symbols may be one of 1, 2, or 3.

[0347] A base station can transmit information about the CORESET and the search space to the terminal. Information about the CORESET is described below. In this specification, the resources that constitute the CORESET may have the same meaning as the resources included in the CORESET.

[0348] The first information about the CORESET may be the index of the PRB sets constituting the CORESET in which the PDCCH is transmitted. The PRB set may be six consecutive PRBs. The indexes of the PRB sets may be set in the form of a bitmap. For example, if the bit value is 1, the corresponding PRB set may correspond to the CORESET for receiving the PDCCH. If the bit value is 0, the corresponding PRB set may not correspond to the CORESET for receiving the PDCCH. The second information about the CORESET may be the number of symbols in which the PDCCH is transmitted. In this case, the number of symbols may be one of 1, 2, and 3, and the symbols may be consecutive symbols. The terminal may determine the resource in which the PDCCH is transmitted by receiving information about the CORESET from the base station.

[0349] Specifically, the first information for CORESET may set the indices of PRBs as PRB#(6*n), PRB#(6*n+1), PRB#(6*n+2), PRB#(6*n+3), PRB#(6*n+4), PRB#(6*n+5), and n may be an integer. Specifically, the base station may set the indices of P PRBs as PRB#0, PRB#1, ...., PRB#(P-1), and P may be a multiple of 6. At this time, the PRBs may or may not be consecutive in the frequency domain. The second information for CORESET is the number of symbols (S) through which the PDCCH is transmitted, and S may be one of 1, 2, and 3. That is, the terminal may receive from the base station a resource through which the PDCCHs are transmitted based on the first information and the second information.

[0350] Resources corresponding to P PRBs and S symbols constituting a CORESET can be configured as a REG (resource element group). One REG can be one PRB and one symbol. That is, P PRBs and S symbols can be configured as P*S REGs. Adjacent 2, 3, or 6 REGs can be bundled to form one REG bundle. The method of bundling 2, 3, or 6 REGs can be determined depending on the length (number of symbols) of the CORESET and the mapping method (interleaved mapping / non-interleaved mapping).

[0351] If the mapping method is non-interleaved and the length of the CORESET is 1 symbol, one REG bundle can be generated by bundling 6 consecutive REGs in the frequency domain. If the mapping method is non-interleaved and the length of the CORESET is 2 symbols, one REG bundle can be generated by bundling 3 REGs in each symbol, for a total of 6 REGs (3 REGs per symbol * 2 symbols). For convenience, when each symbol in the 2 symbols is referred to as symbol A and symbol B, the 3 REGs in symbol A can be consecutive to each other in the frequency domain, and the 3 REGs in symbol B can be consecutive to each other in the frequency domain. In addition, the 3 REGs in symbol A and the 3 REGs in symbol B can be located in the same frequency domain. If it is a non-interleaved mapping method and the length of CORESET is 3 symbols, one REG bundle can be generated by bundling 2 REGs from each symbol, thus bundling 6 REGs in total (2 REGs per each symbol * 3 symbols). For convenience, when the length of CORESET is 3 symbols and each symbol of CORESET is represented as C symbol, D symbol, and E symbol, the 2 REGs of the C symbol can be consecutive in the frequency domain, the 2 REGs of the D symbol can be consecutive in the frequency domain, and the 2 REGs of the E symbol can be consecutive to each other in the frequency domain. In addition, the 2 REGs of the C symbol, the 2 REGs of the D symbol, and the 2 REGs of the E symbol can be located in the same frequency domain.

[0352] If the mapping method is interleaved and the length of CORESET is 1 symbol, i) a REG bundle can be generated by bundling 6 consecutive REGs in the frequency domain, or ii) a REG bundle can be generated by bundling 2 consecutive REGs in the frequency domain. If the mapping method is interleaved and the length of CORESET is 2 symbols, a REG bundle can be generated by bundling 1 REG of each symbol. In this case, 1 REG of each symbol can be located on the same frequency domain. If the mapping method is interleaved and the length of CORESET is 3 symbols, a REG bundle can be generated by bundling 1 REG of each symbol. In this case, 1 REG of each symbol can be located on the same frequency domain.

[0353] A CCE can be generated by bundling REG bundles generated using the above-described method. In this case, the CCE can be composed of six REGs. Since a REG bundle is composed of two, three, or six REGs, a CCE can be composed of three, two, or one REG bundle. In the case of non-interleaved mapping, a REG bundle is composed of six REGs regardless of the number of symbols in the CORESET. In this case, a CCE can be composed of one REG bundle.

[0354] Information about the search space may include time information at which a set of PRBs indicated by CORESET must be received. Specifically, the base station may provide information about the search space to the terminal, and the information about the search space may include at least one of periodicity and offset. Here, the period and offset may be set in units of slots, sub-slots, symbols, symbol sets, or slot sets. The information about the search space may include the CCE aggregation level (AL) received by the terminal, the number of PDCCHs monitored by the terminal for each CCE aggregation level, the search space type, the DCI format monitored by the terminal, and RNTI information.

[0355] The CCE aggregation level can have at least one of the values ​​1, 2, 4, 8, and 16. The terminal can monitor the PDCCH in the same number of CCEs as the value of the CCE aggregation level.

[0356] The search space can be divided into two types. Specifically, the search space types can be divided into a common search space (CSS) and a UE-specific search space. The common search space may be a search space in which all UEs in a cell or some UEs in a cell commonly monitor a PDCCH. The UEs can monitor candidates for PDCCHs (e.g., a PDCCH carrying a DCI having a CRC scrambled with at least one RNTI selected from the SI-RNTI, RA-RNTI, MsgB-RNTI, P-RNTI, TC-RNTI, INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, CI-RNTI, C-RNTI, MCS-C-RNTI, CS-RNTI(s), or PS-RNTI) broadcast to all UEs in a cell or some UEs in a cell in the common search space and receive the PDCCH. A terminal-specific search space may be a search space in which a specific terminal monitors a PDCCH. A specific terminal may monitor candidates for a PDCCH transmitted to a specific terminal in the terminal-specific search space (e.g., a PDCCH carrying a DCI having a CRC scrambled with at least one RNTI among a C-RNTI, an MCS-C-RNTI, an SP-CSI-RNTI, a CS-RNTI(s), an SL-RNTI, an SL-CS-RNTI, and an SL-L-CS-RNTI) and receive the PDCCH. In addition, the terminal may receive a PDCCH including a DCI indicating reception of a PDSCH, transmission of a PUCCH, or transmission of a PUSCH in the common search space and the terminal-specific search space.

[0357] Slot n included in the search space s of CORESET p s,f μ PDCCH candidate m s,nCIThe CCEs constituting the PDCCH can be determined by the hashing function of mathematical expression 1. At this time, the aggregation level of the PDCCH candidate can be L.

[0358]

[0359] If the search space s is a common search space, can be 0. If the search space s is a terminal-specific search space, Is and Y p,-1 is n RNTI is equal to and not 0. A p can be 39827 when p mod 3 is 0, 39829 when p mod 3 is 1, and 39839 when p mod 3 is 2. D can be 65537. n RNTI can be a C-RNTI value. N CCE,p M can be the number of CCEs that make up the CORESET. (L) s,max may be the number of repetitive PDCCH candidates whose aggregation level is L monitored by the terminal. n CI may be a value indicated by the carrier indicator field.

[0360] Figures 25 and 26 illustrate the problems to be solved in this specification.

[0361] Referring to FIG. 25, a terminal may be configured to monitor a PDCCH in CORESET#1 of search space#1 of slot n to slot n+3 from a base station. Here, search space#1 may be configured with a period of one slot. The terminal may monitor PDCCH#1A in CORESET#1 of search space#1 of slot n, the terminal may monitor PDCCH#1B in CORESET#1 of search space#1 of slot n+1, the terminal may monitor PDCCH#1C in CORESET#1 of search space#1 of slot n+2, and the terminal may monitor PDCCH#1D in CORESET#1 of search space#1 of slot n+3. PDCCH#1A to PDCCH#1D may include the same DCI.

[0362] Referring to FIG. 26, a terminal may be configured to monitor a PDCCH in CORESET#1 of search space#1 of slot n to slot n+3 from a base station in the same manner as in FIG. 25. A terminal supporting SBFD operation may be configured with multiple subbands (two downlink subbands and one uplink subband) in the frequency domain of slot n+2 to slot n+3. In this case, CORESET#1 of slot n+2 to slot n+3 may overlap with some uplink subbands in the frequency domain. A terminal supporting SBFD operation cannot perform downlink reception in the uplink subband, and therefore cannot perform PDCCH reception in slot n+2 to slot n+3. Examples for solving this problem are disclosed below. For convenience of explanation, a time domain section in which a terminal supporting SBFD operation has configured multiple subbands in the frequency domain is called an SBFD section (slot n+2 to slot n+3 in FIG. 26), and a time domain section in which a terminal has not configured subbands in the frequency domain is called a non-SBFD section (slot n to slot n+1 in FIG. 26).

[0363] For example, a terminal may be configured to associate two CORESETs in a single search space. In the conventional method, a terminal may be configured to associate one CORESET in a single search space, but a terminal supporting SBFD operation may be configured to apply different CORESETs in the SBFD section and the non-SBFD section, respectively. For example, a terminal supporting SBFD operation may be configured to associate CORESET#1 and CORESET#2 with respect to search space #1. The terminal may determine that CORESET#1 is the CORESET to monitor in the SBFD section, and that CORESET#2 is the CORESET to monitor in the non-SBFD section.

[0364] In the existing NR system, a terminal can be configured with up to one CORESET per BWP, excluding CORESET#0, in a cell operating at FR1. Here, CORESET#0 may be a CORESET configured via PBCH for the terminal's initial cell access. Therefore, the above example is a method that requires additional capabilities of the terminal, since at least two CORESETs, excluding CORESET#0, must be configured per BWP in the cell.

[0365] As an example to solve this, the terminal can be configured with separate configuration information applied to the SBFD section and non-SBFD section for one CORESET. Here, the separate configuration information can be configured through a separate RRC signal. For example, the terminal can be configured with separate frequencyDomainResources for the SBFD section and non-SBFD section. Here, frequencyDomainResources can be information on whether the corresponding CORESET is allocated to 6 consecutive PRBs in the frequency domain. If the bit value is '0', it can be configured that the corresponding PRB set is not allocated to the corresponding CORESET, and if the bit value is '1', it can be configured that the corresponding PRB set is allocated to the corresponding CORESET. For example, the terminal can be configured with separate CCE aggregation levels (ALs) for the SBFD section and non-SBFD section, and the number of PDCCHs that the terminal monitors for each CCE aggregation level. Referring to FIG. 27, the terminal may be configured with frequencyDomainResources= 11111111, CCE aggregation level=16, and the number of PDCCHs monitored at the corresponding CCE aggregation level=1 (PDCCH#1) for the non-SBFD section for CORESET#1. The terminal may be configured with frequencyDomainResources= 11100111, CCE aggregation level=2, and the number of PDCCHs monitored at the corresponding CCE aggregation level=6 (PDCCH#2 to PDCCH#7) for the SBFD section for CORESET#1. That is, since the frequency domain resources available for DL ​​reception are different in the non-SBFD section and the SBFD section, the terminal may receive different configuration information from the base station for the two sections.Here, the separate configuration information applied to the SBFD and non-SBFD sections for a single CORESET may be configuration information for the CORESET or configuration information for the search space. For example, frequencyDomainResources may be configuration information for the CORESET, and the CCE aggregation level (AL) and the number of PDCCHs monitored by the UE for each CCE aggregation level may be configuration information for the search space.

[0366] However, referring to FIG. 28, if the CORESET in the above example is configured in an interleaved mapping manner, some REG bundles within the CCE may be included in an uplink subband or guard band. In FIG. 28, if the interleaved mapping manner is used and two symbols and one PRB are configured as one REG bundle, three REG bundles constitute one CCE. Referring to FIG. 28, in CCE#0 to CCE#3, one REG bundle may be included in the uplink and guard band, and in CCE#0 to CCE#3, PDCCH may be received in two REG bundles, respectively. This may cause degradation of PDCCH reception performance.

[0367] As an example to address this, a terminal can determine resource mapping for separate PDCCH reception for SBFD and non-SBFD periods. In other words, a terminal supporting SBFD operation can determine that one CORESET is associated with two CCE-to-REG mappings (e.g., CCE-to-REG mapping in SBFD period and CCE-to-REG mapping in non-SBFD period).

[0368] For example, in the SBFD section, the REG constituting one CORESET is indexed as 0 for the first OFDM symbol and the PRB with the lowest index in the CORESET, and the index is sequentially increased in a time-first manner. At this time, the terminal may not increase the (REG) index for symbols and PRBs included in the uplink subband or guard band. That is, since PDCCH reception is not possible for symbols and PRBs included in the uplink subband or guard band, the symbols and PRBs may be excluded from the REG and not indexed. Referring to FIG. 29, one CORESET is composed of two symbols and 16 PRBs, and some symbols and PRBs (e.g., 2 symbols x 4 PRBs) may be included in the uplink subband or guard band. A terminal supporting the SBFD operation may not index the symbols and PRBs included in the REG and sequentially increase the (REG) index for the remaining symbols and PRBs in a time-first manner.

[0369] Meanwhile, in the non-SBFD section, the REGs constituting a CORESET are indexed as 0 for the first OFDM symbol and the PRB with the lowest index within the CORESET, and the indices sequentially increase in a time-first manner. At this time, REG indexing is performed for all resources within the CORESET.

[0370] In the above example, the terminal can not only determine resource mapping for separate PDCCH reception for SBFD and non-SBFD intervals, but also receive separate configuration information for the SBFD and non-SBFD intervals. For example, frequencyDomainResources can be set as separate configuration information for CORESET, and the CCE aggregation level (AL) and the number of PDCCHs that the terminal monitors for each CCE aggregation level can be set as configuration information for the search space.

[0371] Through the above example, a terminal can determine two CCE-to-REG mappings for a single CORESET. Therefore, separate CCE aggregation levels, CCE counts, and the number of PDCCH candidates monitored per CCE aggregation level can be established for SBFD and non-SBFD periods.

[0372] Below, a terminal supporting SBFD operation is included in slot n of search space s of CORESET p. s,f μ PDCCH candidate m s,nCI,j The integration level that constitutes L j Explains how to determine CCEs.

[0373] m s,nCI,j Depending on the value of j, it can be a PDCCH candidate in the SBFD section or a PDCCH candidate in the non-SBFD section. For example, m s,nCI,0 can be a PDCCH candidate in the SBFD section, and m s,nCI,1 can be a PDCCH candidate in the non-SBFD section. As another example, m s,nCI,1 can be a PDCCH candidate in the SBFD section, and m s,nCI,0 may be a PDCCH candidate in the non-SBFD section.

[0374] L jDepending on the value of j, L0 can be a CCE aggregation level in an SBFD section or a CCE aggregation level in a non-SBFD section. For example, L0 can be a CCE aggregation level in an SBFD section, and L1 can be a CCE aggregation level in a non-SBFD section. As another example, L1 can be a CCE aggregation level in an SBFD section, and L0 can be a CCE aggregation level in a non-SBFD section.

[0375] Mathematical expression 2 can determine the hashing function.

[0376]

[0377] If the search space s is a common search space, can be 0. If the search space s is a terminal-specific search space, Is and Y p,-1 is n RNRI is equal to and not 0. A p can be 39827 when p mod 3 is 0, 39829 when p mod 3 is 1, and 39839 when p mod 3 is 2. D can be 65537. n RNTI can be a C-RNTI value.n CI may be a value indicated by the carrier indicator field.

[0378] N CCE,p,j Depending on the value of j, it can be the number of CCEs that constitute a CORESET in the SBFD interval or the number of CCEs that constitute a CORESET in the non-SBFD interval. For example, N CCE,p,0 can be the number of CCEs that constitute the CORESET in the SBFD section, and N CCE,p,1 can be the number of CCEs that constitute a CORESET in a non-SBFD interval. As another example, N CCE,p,1 can be the number of CCEs that constitute the CORESET in the SBFD section, and NCCE,p,0 may be the number of CCEs that constitute the CORESET in the non-SBFD section.

[0379] The integration level monitored by the terminal is L j The number of repeated PDCCH candidates may be, for example, Depending on the value of j, it can be the number of repetitive PDCCH candidates with an aggregation level of L0 in the SBFD section or the number of repetitive PDCCH candidates with an aggregation level of L1 in the non-SBFD section. As another example, Depending on the value of j, it can be the number of repetitive PDCCH candidates with an aggregation level of L1 in the SBFD section or the number of repetitive PDCCH candidates with an aggregation level of L0 in the non-SBFD section.

[0380] The above method is a method of determining separate CCEs in SBFD and non-SBFD sections, since two CCE-to-REG mappings are determined for one CORESET.

[0381] Although the methods and systems of the present invention have been described with respect to specific embodiments, some or all of their components or operations may be implemented using a computing system having a general-purpose hardware architecture.

[0382] The foregoing description of the present invention is for illustrative purposes only, and those skilled in the art will readily appreciate that the present invention can be readily modified into other specific forms without altering the technical spirit or essential characteristics of the present invention. Therefore, the embodiments described above should be understood as illustrative in all respects and not restrictive. For example, each component described as a single entity may be implemented in a distributed manner, and similarly, components described as distributed may be implemented in a combined manner.

[0383] The scope of the present invention is indicated by the claims described below rather than the detailed description above, and all changes or modifications derived from the meaning and scope of the claims and their equivalent concepts should be interpreted as being included in the scope of the present invention.

Claims

1. In a terminal used in a wireless communication system, Communication module; and including a processor that controls the above communication module, The above processor, Receive configuration information regarding reception of CORESET (control resource set)#0 through reception of SS / PBCH (synchronization signal / physical broadcast channel) block, It is configured to receive DCI (downlink control information) including resource allocation information for receiving PDSCH (physical downlink shared channel) through reception of the above CORESET#0, (i) A terminal in which transmission of a physical uplink shared channel (PUSCH) is scheduled within an uplink subband within a bandwidth part (BWP), and (ii) when a resource for transmitting the PUSCH overlaps with a resource for receiving the PDSCH in the time domain, transmission of the PUSCH is performed or canceled according to a condition, and the condition includes a timeline condition related to an interval between a resource for receiving the CORESET#0 and a resource for transmitting the PUSCH.

2. In paragraph 1, The above timeline condition is a terminal including a start symbol for transmitting the PUSCH being located at least after the PUSCH preparation time from the last symbol for receiving the CORESET#0.

3. In paragraph 2, A terminal for which the transmission of the PUSCH is canceled in all resources for transmitting the PUSCH when the above timeline condition is satisfied.

4. In paragraph 2, A terminal in which, when the above timeline condition is satisfied, transmission of the PUSCH is partially canceled in a symbol overlapping with a symbol for receiving the PDSCH and a symbol overlapping with a gap symbol following a symbol for receiving the PDSCH.

5. In paragraph 2, A terminal in which PUSCH transmission is performed on all resources for transmitting the PUSCH when the above timeline condition is not satisfied.

6. In a method used by a terminal in a wireless communication system, A step of receiving configuration information regarding reception of CORESET (control resource set)#0 through reception of SS / PBCH (synchronization signal / physical broadcast channel) block; and A step of receiving DCI (downlink control information) including resource allocation information for receiving PDSCH (physical downlink shared channel) through reception of the above CORESET#0, (i) A method in which transmission of a physical uplink shared channel (PUSCH) is scheduled within an uplink subband within a bandwidth part (BWP), and (ii) when a resource for transmitting the PUSCH overlaps with a resource for receiving the PDSCH in the time domain, transmission of the PUSCH is transmitted or canceled according to a condition, and the condition includes a timeline condition related to an interval between a resource for receiving the CORESET#0 and a resource for transmitting the PUSCH.

7. In paragraph 6, A method in which the above timeline condition includes that the start symbol for transmitting the PUSCH is located at least a PUSCH preparation time later than the last symbol for receiving the CORESET#0.

8. In paragraph 7, A method in which, when the above timeline condition is satisfied, transmission of the PUSCH is completely canceled in all resources for transmitting the PUSCH.

9. In paragraph 7, A method in which, when the above timeline condition is satisfied, transmission of the PUSCH is partially canceled in symbols overlapping with symbols for receiving the PDSCH and in symbols overlapping with gap symbols following symbols for receiving the PDSCH.

10. In paragraph 7, A method in which transmission of the PUSCH is performed in all resources for transmitting the PUSCH when the above timeline condition is not satisfied.

11. In a base station used in a wireless communication system, Communication module; and including a processor that controls the above communication module, The above processor, Transmit configuration information regarding the transmission of CORESET (control resource set)#0 through transmission of SS / PBCH (synchronization signal / physical broadcast channel) block, It is configured to transmit DCI (downlink control information) including resource allocation information for transmitting PDSCH (physical downlink shared channel) through transmission of the above CORESET#0, (i) A base station in which reception of a physical uplink shared channel (PUSCH) is scheduled within an uplink subband within a bandwidth part (BWP), and (ii) when a resource for receiving the PUSCH overlaps with a resource for transmitting the PDSCH in the time domain, reception of the PUSCH is performed or canceled according to a condition, and the condition includes a timeline condition related to an interval between a resource for transmitting the CORESET#0 and a resource for receiving the PUSCH.

12. In paragraph 11, A base station wherein the above timeline condition includes that the start symbol for receiving the PUSCH is located at least a PUSCH preparation time later than the last symbol for transmitting the CORESET#0.

13. In paragraph 12, A base station in which reception of the PUSCH is completely canceled in all resources for receiving the PUSCH when the above timeline condition is satisfied.

14. In paragraph 12, A base station in which, when the above timeline condition is satisfied, reception of the PUSCH is partially canceled in symbols overlapping with symbols for transmitting the PDSCH and in symbols overlapping with gap symbols following symbols for transmitting the PDSCH.

15. In paragraph 12, A base station where reception of the PUSCH is performed in all resources for receiving the PUSCH when the above timeline condition is not satisfied.

16. In a method used by a base station in a wireless communication system, A step of transmitting configuration information regarding transmission of CORESET (control resource set)#0 through transmission of SS / PBCH (synchronization signal / physical broadcast channel) block; and A step of transmitting DCI (downlink control information) including resource allocation information for transmitting PDSCH (physical downlink shared channel) through transmission of the above CORESET#0 is included, (i) A method in which reception of a physical uplink shared channel (PUSCH) is scheduled within an uplink subband within a bandwidth part (BWP), and (ii) when a resource for receiving the PUSCH overlaps with a resource for transmitting the PDSCH in the time domain, reception of the PUSCH is performed or canceled according to a condition, and the condition includes a timeline condition related to an interval between a resource for transmitting the CORESET#0 and a resource for receiving the PUSCH.

17. In paragraph 11, A method in which the above timeline condition includes that the start symbol for receiving the PUSCH is located at least after the PUSCH preparation time from the last symbol for transmitting the CORESET#0.

18. In paragraph 17, A method in which reception of the PUSCH is completely canceled in all resources for receiving the PUSCH when the above timeline condition is satisfied.

19. In paragraph 17, A method in which, when the above timeline condition is satisfied, reception of the PUSCH is partially canceled in symbols overlapping with symbols for transmitting the PDSCH and in symbols overlapping with gap symbols following symbols for transmitting the PDSCH.

20. In paragraph 17, A method in which reception of the PUSCH is performed in all resources for receiving the PUSCH when the above timeline condition is not satisfied.

Citation Information

Patent Citations

  • Systems and methods for inspecting wear of safegy suit

    KR1020210117789A

  • Aquaculture pipes and manufacturing methods thereof

    KR102282654B1

  • Handling downlink and uplink collisions in half duplex frequency division duplex user equipment

    WO2022152922A1

  • KR20190017675A

  • KR20190129721A