[go: up one dir, main page]

WO2024237421A1 - Procédé et dispositif de transmission de signal dans un système de communication sans fil - Google Patents

Procédé et dispositif de transmission de signal dans un système de communication sans fil Download PDF

Info

Publication number
WO2024237421A1
WO2024237421A1 PCT/KR2024/000338 KR2024000338W WO2024237421A1 WO 2024237421 A1 WO2024237421 A1 WO 2024237421A1 KR 2024000338 W KR2024000338 W KR 2024000338W WO 2024237421 A1 WO2024237421 A1 WO 2024237421A1
Authority
WO
WIPO (PCT)
Prior art keywords
pusch
symbol
terminal
transmission
reception
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/KR2024/000338
Other languages
English (en)
Korean (ko)
Inventor
석근영
노민석
윤영준
손주형
곽진삼
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Wilus Institute of Standards and Technology Inc
Original Assignee
Wilus Institute of Standards and Technology Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Wilus Institute of Standards and Technology Inc filed Critical Wilus Institute of Standards and Technology Inc
Publication of WO2024237421A1 publication Critical patent/WO2024237421A1/fr
Anticipated expiration legal-status Critical
Pending legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/14—Two-way operation using the same type of signal, i.e. duplex
    • H04L5/16—Half-duplex systems; Simplex/duplex switching; Transmission of break signals non-automatically inverting the direction of transmission
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H04W72/232—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the physical layer, e.g. DCI signalling

Definitions

  • 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 using the same.
  • the 5G communication system is also called a communication system beyond 4G network, a post-LTE system, or a new radio (NR) system.
  • the 5G communication system includes a system that operates using an ultra-high frequency (mmWave) band of 6 GHz or higher, and in terms of securing coverage, implementation in base stations and terminals is being considered, including a communication system that operates using a frequency band of 6 GHz or lower.
  • mmWave ultra-high frequency
  • the 3rd generation partnership project (3GPP) NR system improves the spectral efficiency of networks, allowing carriers to provide 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 large-capacity voice support.
  • the advantages of the NR system include high throughput, low latency, support for FDD (frequency division duplex) and TDD (time division duplex) on the same platform, improved end-user experience, and low operating costs with a simple architecture.
  • dynamic TDD of NR system can use a method to change the number of OFDM (orthogonal frequency division multiplexing) symbols that can be used for uplink and downlink according to the data traffic direction of users of the cell. For example, when the downlink traffic of the cell is more than the uplink traffic, the base station can allocate multiple downlink OFDM symbols to a slot (or subframe). Information about the slot configuration should be transmitted to the terminals.
  • OFDM orthogonal frequency division multiplexing
  • ACM advanced coding modulation
  • FQAM hybrid FSK and QAM modulation
  • SWSC sliding window superposition coding
  • 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.
  • IoT Internet of Things
  • M2M machine-to-machine communication
  • MTC machine type communication
  • IoT intelligent IT (Internet technology) services can be provided that collect and analyze data generated from connected objects to create new values for human life.
  • IoT can be applied to fields such as smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart home appliances, and advanced medical services through convergence and combination between existing IT (information technology) technologies and various industries.
  • 5G communication systems to IoT networks.
  • technologies such as sensor networks, machine-to-machine (M2M), and machine type communication (MTC) are being implemented by techniques such as beamforming, MIMO, and array antennas, which are 5G communication technologies.
  • cloud radio access networks as a big data processing technology described above, can be said to be an example of the convergence of 5G and IoT technologies.
  • mobile communication systems have been developed to provide voice services while ensuring user activity.
  • 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.
  • a terminal used in a wireless communication system 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 in 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.
  • the condition includes a timeline condition related to an interval between a resource
  • a method used by a terminal in a wireless communication system 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 in a BWP (bandwidth part), and (ii) if 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.
  • a base station used in a wireless communication system 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 in 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.
  • DCI downlink control information
  • a method used by a base station in a wireless communication system 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 DCI (downlink control information) 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 in a BWP (bandwidth part), and (ii) if 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.
  • 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.
  • the transmission of the PUSCH can be canceled in all resources for transmitting the PUSCH.
  • transmission of the PUSCH can 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.
  • transmission of the PUSCH can be performed on all resources for transmitting the PUSCH.
  • the condition may further include whether the PUSCH is a DG (dynamic grant) PUSCH or a CG (configured grant) PUSCH.
  • DG dynamic grant
  • CG configured grant
  • condition may further include whether the terminal has indicated PUSCH-partialCancellation capability to the base station.
  • the present invention provides a method for efficiently transmitting and receiving a signal in a wireless communication system and a device using the same.
  • Figure 1 shows an example of a radio frame structure used in a wireless communication system.
  • Figure 2 shows an example of a downlink (DL)/uplink (UL) slot structure in a wireless communication system.
  • 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.
  • Figures 4a and 4b illustrate SS/PBCH blocks for initial cell access in a 3GPP NR system.
  • Figures 5a and 5b illustrate procedures for control information and control channel transmission in a 3GPP NR system.
  • 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.
  • CORESET control resource set
  • PDCCH physical downlink control channel
  • FIG. 7 is a diagram illustrating a method for setting a PDCCH search space in a 3GPP NR system.
  • Figure 8 is a conceptual diagram explaining carrier aggregation.
  • Figure 9 is a diagram for explaining single-carrier communication and multi-carrier communication.
  • Figure 10 is a diagram illustrating an example in which a cross-carrier scheduling technique is applied.
  • Figure 11 is a block diagram showing the configuration of a terminal and a base station according to one embodiment of the present invention.
  • Figures 12 to 14 illustrate a method for setting subbands.
  • FIGS 15 to 18 illustrate an uplink transmission method according to an example of the present invention.
  • Figure 19 illustrates the multiplexing pattern of SSB & CORESET0.
  • FIGS 20 to 24 illustrate an uplink transmission method according to an example of the present invention.
  • Figure 25 illustrates how to set up CORESET and search space.
  • Figure 26 illustrates a problem when a terminal supporting SBFD (non-overlapping subband full duplex) operation receives a PDCCH.
  • SBFD non-overlapping subband full duplex
  • Figures 27 and 28 illustrate a method for a terminal supporting an SBFD operation according to an example of the present invention to set a CORESET and a search space.
  • 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.
  • CCE-to-REG control channel element to resource element group
  • CDMA code division multiple access
  • FDMA frequency division multiple access
  • TDMA time division multiple access
  • OFDMA orthogonal frequency division multiple access
  • 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, 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
  • LTE-A(Advanced) is an evolved version of 3GPP LTE.
  • 3GPP NR New Radio
  • eMBB encoded Mobile BroadBand
  • URLLC Ultra-Reliable and Low Latency Communication
  • mMTC massive Machine Type Communication
  • a base station may include a gNB (next generation node B) defined in 3GPP NR.
  • a terminal may include a UE (user equipment).
  • the configuration of a terminal may refer to a configuration by a base station. Specifically, the base station may transmit a channel or a signal to the terminal to set the values of parameters used in the operation of the terminal or in a wireless communication system.
  • Figure 1 shows an example of a radio frame structure used in a wireless communication system.
  • a radio frame (or radio frame) used in a 3GPP NR system can have a length of 10 ms ( ⁇ f max N f / 100) * T c ).
  • the radio frame is composed of 10 equally sized subframes (subframes, SF).
  • ⁇ f max 480 * 10 3 Hz
  • N f 4096
  • T c 1 / ( ⁇ f ref * N f,ref )
  • ⁇ f ref 15 * 10 3 Hz
  • N f,ref 2048.
  • Each of the 10 subframes in one radio frame can be numbered from 0 to 9.
  • Each subframe has a length of 1 ms and can be composed of one or more slots depending on the subcarrier spacing.
  • the subcarrier spacing that can be used in the 3GPP NR system is 15 * 2 ⁇ kHz.
  • a 1 ms long subframe can be composed of 2 ⁇ slots. In this case, the length of each slot is 2 - ⁇ ms.
  • the 2 ⁇ slots in one subframe can be numbered from 0 to 2 ⁇ - 1, respectively. Additionally, the slots in one radio frame can be numbered from 0 to 10*2 ⁇ - 1, respectively.
  • a time resource can be distinguished by at least one of a radio frame number (or radio frame index), a subframe number (or subframe index), and a slot number (or slot index).
  • Fig. 2 shows an example of a downlink (DL)/uplink (UL) slot structure in a wireless communication system.
  • Fig. 2 shows the structure of a resource grid of a 3GPP NR system.
  • a slot includes a plurality of orthogonal frequency division multiplexing (OFDM) symbols in the time domain and a plurality of resource blocks (RBs) in the frequency domain.
  • An OFDM symbol also means one symbol interval. Unless otherwise specified, an OFDM symbol may be simply referred to as a symbol.
  • One RB includes 12 consecutive subcarriers in the frequency domain.
  • a signal transmitted in each slot can be expressed as a resource grid consisting of N size, ⁇ grid,x * N RB sc subcarriers and N slot symb OFDM symbols.
  • x DL
  • x UL.
  • N size, ⁇ grid,x represents the number of resource blocks (RBs) according to the subcarrier spacing factor ⁇ (x is DL or UL), and N slot symb represents the number of OFDM symbols in a slot.
  • 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 depending on a multiple access method.
  • 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 interval.
  • FIG. 2 illustrates a case where one slot consists of 14 OFDM symbols, but the embodiments of the present invention may be applied in the same manner to slots having a different number of OFDM symbols.
  • each OFDM symbol includes N size, ⁇ grid,x * N RB sc subcarriers in the frequency domain.
  • the types of subcarriers may be divided into data subcarriers for data transmission, reference signal subcarriers for reference signal transmission, and guard bands.
  • the carrier frequency is also called a center frequency (fc).
  • An RB can be defined by N RB sc (for example, 12) consecutive subcarriers in the frequency domain.
  • N RB sc for example, 12
  • a resource composed of one OFDM symbol and one subcarrier can be referred to as a resource element (RE) or a tone. Therefore, an RB can be composed of N slot symb * N RB sc resource elements.
  • Each resource element in a resource grid can be uniquely defined by an index pair (k, l) in one slot. k is an index assigned from 0 to N size, ⁇ grid, x * N RB sc - 1 in the frequency domain, and l is an index assigned from 0 to N slot symb - 1 in the time domain.
  • the time/frequency synchronization of the terminal may need to be aligned with the time/frequency synchronization of the base station. This is because only when the base station and the terminal are synchronized can the terminal determine the time and frequency parameters necessary to perform demodulation of a DL signal and transmission of a UL signal at an accurate time.
  • Each symbol of a radio frame operating in TDD (time division duplex) or 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 FDD (frequency division duplex) or 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 whether to be used for a downlink or an uplink depending on a signal.
  • Information about the type of each symbol i.e., information indicating one of a downlink symbol, an uplink symbol, and a flexible symbol, may be configured as a cell-specific (or common) radio resource control (RRC) signal.
  • RRC radio resource control
  • information about the type of each symbol may additionally be configured as a UE-specific (or dedicated) RRC signal.
  • a base station uses the cell-specific RRC signal to indicate i) a period of a cell-specific slot configuration, ii) the number of slots having 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 a slot immediately following a slot having only downlink symbols, iv) the number of slots having 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 a slot immediately preceding a slot having only uplink symbols.
  • a symbol that is not configured as either an uplink symbol or a downlink symbol is a flexible symbol.
  • the base station can signal whether a flexible symbol is a downlink symbol or an uplink symbol as a cell-specific RRC signal. At this time, the terminal-specific RRC signal cannot change a downlink symbol or an uplink symbol configured as a cell-specific RRC signal to another symbol type.
  • the terminal-specific RRC signal can signal the number of downlink symbols among N slot symb symbols of the corresponding slot, and the number of uplink symbols among N slot symb symbols of the corresponding slot, for each slot. At this time, the downlink symbols of the slot can be configured continuously from the first symbol to the i-th symbol of the slot.
  • the uplink symbols of the slot can be configured continuously from the j-th symbol to the last symbol of the slot (where, i ⁇ j).
  • a symbol in a slot that is not configured as either an uplink symbol or a downlink symbol is a flexible symbol.
  • 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.
  • a 3GPP system e.g., NR
  • 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 is cell-common system information for the terminal to operate properly in the physical layer of an RRC (Radio Resource Control, RRC), and is referred to as remaining system information or system information block (SIB) 1.
  • RRC Radio Resource Control
  • the terminal may perform a random access procedure for the base station (steps S103 to S106).
  • the terminal may transmit a preamble through a physical random access channel (PRACH) (S103) and receive a response message to the preamble from the base station through a PDCCH and a corresponding PDSCH (S104).
  • PRACH physical random access channel
  • S104 receive a response message to the preamble from the base station through a PDCCH and a corresponding PDSCH
  • the terminal transmits data including its identifier, etc. 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).
  • PUSCH physical uplink shared channel
  • the terminal waits for reception of the PDCCH as an instruction of the base station for collision resolution.
  • the terminal successfully receives the PDCCH through its identifier S106
  • the random access procedure is terminated.
  • the terminal can obtain terminal-specific system information required for the terminal to operate properly from the physical layer to the RRC layer.
  • the terminal obtains terminal-specific system information from the RRC layer, the terminal enters the RRC connected mode (RRC_CONNECTED mode).
  • the RRC layer is used to generate and manage messages for control between terminals and a radio access network (RAN). More specifically, the base station and terminals can perform, in the RRC layer, broadcasting of cell system information required for all terminals in a 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.
  • RRC signal since the update of a signal transmitted in the RRC layer (hereinafter, “RRC signal”) is longer than a 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.
  • the terminal can perform PDCCH/PDSCH reception (S107) and physical uplink shared channel (PUSCH)/physical uplink control channel (PUCCH) transmission (S108) as a general uplink/downlink signal transmission procedure.
  • 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.
  • 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 a downlink/uplink ACK/NACK signal, a channel quality indicator (CQI), a precoding matrix index (PMI), a rank indicator (RI), etc.
  • CQI channel quality indicator
  • PMI precoding matrix index
  • RI rank indicator
  • the CQI, the PMI, and the RI can be included in the channel state information (CSI).
  • the terminal can transmit control information such as HARQ-ACK and CSI described above through PUSCH and/or PUCCH.
  • Figures 4a and 4b illustrate SS/PBCH blocks for initial cell access in a 3GPP NR system.
  • the terminal When the terminal is powered on or attempts to access a new cell, the terminal can acquire time and frequency synchronization with the cell and perform an initial cell search process.
  • the terminal can detect the physical cell identity (N cell ID ) of the cell during the cell search process.
  • the terminal can receive synchronization signals, such as a primary synchronization signal (PSS) and a secondary synchronization signal (SSS), from the base station to synchronize with the base station.
  • PSS primary synchronization signal
  • SSS secondary synchronization signal
  • the terminal can acquire information such as a cell identity (ID).
  • ID cell identity
  • a synchronization signal can be divided into PSS and SSS.
  • the PSS can be used to obtain time domain synchronization such as OFDM symbol synchronization, slot synchronization, and/or frequency domain synchronization.
  • the SSS can be used to obtain frame synchronization and cell group ID.
  • the PSS is transmitted through the first OFDM symbol, and the SSS is transmitted through the 56th to 182nd subcarriers in the third OFDM symbol.
  • the lowest subcarrier index of the SS/PBCH block is numbered from 0.
  • the base station does not transmit signals through the remaining subcarriers, that is, subcarriers 0 to 55 and 183 to 239.
  • the base station does not transmit signals through subcarriers 48 to 55 and 183 to 191.
  • the base station transmits PBCH (physical broadcast channel) through the remaining REs excluding the above signals in the SS/PBCH block.
  • PBCH physical broadcast channel
  • the SS can be grouped into 336 physical-layer cell-identifier groups, each group including three unique identifiers, such that each physical-layer cell ID is part of only one physical-layer cell-identifier group, through a combination of three PSSs and SSSs, for a total of 1008 unique physical-layer cell IDs.
  • a terminal can detect a PSS to identify one of the three unique physical-layer identifiers.
  • a terminal can detect a SSS to identify one of the 336 physical-layer cell IDs associated with the physical-layer identifier.
  • the sequence d PSS (n) of PSS is as follows.
  • sequence d SSS (n) of SSS is as follows.
  • a 10 ms long radio frame can be divided into two half frames each of 5 ms long.
  • the slot in which the SS/PBCH block is transmitted can be any one of Cases A, B, C, D, and E.
  • the subcarrier spacing is 15 kHz
  • the start point of the SS/PBCH block is the ⁇ 2, 8 ⁇ + 14*nth symbol.
  • n can be 0, 1 for a carrier frequency of 3 GHz or less.
  • n can be 0, 1, 2, 3 for a carrier frequency exceeding 3 GHz and equal to or less than 6 GHz.
  • the subcarrier spacing is 30 kHz, and the start point of the SS/PBCH block is the ⁇ 4, 8, 16, 20 ⁇ + 28*nth symbol.
  • n can be 0 for a carrier frequency of 3 GHz or less.
  • n can be 0, 1 for a carrier frequency exceeding 3 GHz and less than or equal to 6 GHz.
  • the subcarrier spacing is 30 kHz, and the starting point of the SS/PBCH block is the ⁇ 2, 8 ⁇ + 14*n-th symbol. In this case, n can be 0, 1 for a carrier frequency exceeding 3 GHz and less than or equal to 6 GHz.
  • the subcarrier spacing is 120 kHz, and the starting point of the SS/PBCH block is the ⁇ 4, 8, 16, 20 ⁇ + 28*n-th symbol.
  • n can be 0, 1, 2, 3 for a carrier frequency exceeding 6 GHz and less than or equal to 6 GHz.
  • the subcarrier spacing is 240 kHz, and the start point of the SS/PBCH block is ⁇ 8, 12, 16, 20, 32, 36, 40, 44 ⁇ + 56*nth symbol. In this case, n can be 0, 1, 2, 3, 5, 6, 7, 8 for carrier frequencies above 6 GHz.
  • FIG. 5A and FIG. 5B illustrate a procedure for transmitting control information and control channels in a 3GPP NR system.
  • 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).
  • RNTI radio network temporary identifier
  • 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).
  • SI-RNTI system information RNTI
  • P-RNTI paging RNTI
  • RA-RNTI random access RNTI
  • TPC-RNTI transmit power control RNTI
  • a terminal-specific RNTI may include at least one of a cell temporary RNTI (C-RNTI) and a CS-RNTI.
  • the base station can perform rate-matching according to the amount of resource(s) used for PDCCH transmission (S206) after performing channel encoding (e.g., polar coding) (S204).
  • channel encoding e.g., polar coding
  • the base station can multiplex DCI(s) based on a PDCCH structure based on CCE (control channel element) (S208).
  • 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 one PDCCH can be defined as an aggregation level.
  • aggregation levels of 1, 2, 4, 8, or 16 can be used.
  • Fig. 5b is a diagram regarding CCE aggregation levels and multiplexing of PDCCHs, showing the types of CCE aggregation levels used for one PDCCH and the CCE(s) transmitted in the control domain accordingly.
  • 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.
  • CORESET control resource set
  • PDCCH physical downlink control channel
  • CORESET is a time-frequency resource in which PDCCH, which is a control signal for a terminal, is transmitted.
  • a search space described below can be mapped to one CORESET. Therefore, the terminal does not monitor all frequency bands for PDCCH reception, but monitors the time-frequency domain designated as the CORESET to decode the PDCCH mapped to the CORESET.
  • the base station can configure one or more CORESETs for each cell for the terminal.
  • a CORESET can be composed of up to three consecutive symbols in the time axis.
  • a CORESET can be composed of six consecutive PRBs in the frequency axis. In the embodiment of Fig.
  • CORESET#1 is composed of consecutive PRBs
  • CORESET#2 and CORESET#3 are composed of discontinuous PRBs.
  • a CORESET can be located in any symbol in 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.
  • Figure 7 is a diagram illustrating a method for setting a PDCCH search space in a 3GPP NR system.
  • each CORESET may have at least one search space.
  • the search space is a set of all time-frequency resources (hereinafter, PDCCH candidates) to which the PDCCH of the terminal can be transmitted.
  • the search space may include a common search space that 3GPP NR terminals should commonly search and a terminal-specific or UE-specific search space that a specific terminal should search.
  • the common search space a PDCCH that is set to be commonly searched by all terminals in a cell belonging to the same base station can be monitored.
  • the terminal-specific search space can 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.
  • the search spaces between terminals may be allocated to partially overlap due to a limited control region to which the PDCCH can be allocated.
  • Monitoring PDCCH involves blind decoding PDCCH candidates within the search space. If blind decoding is successful, the PDCCH is expressed as (successfully) detected/received, and if blind decoding fails, the PDCCH can be expressed as not detected/not received, or not successfully detected/received.
  • 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.
  • 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.
  • the base station can inform each terminal or terminal group of information related to resource allocation of the transmission channels, 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.
  • the terminal can receive data excluding specific control information or specific service data through PDSCH.
  • the base station can transmit, in the PDCCH, information indicating to which terminal (one or more terminals) the PDSCH data is transmitted and how the corresponding terminal should receive and decode the PDSCH data. For example, it is assumed that 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 called "B" (e.g., frequency location) and indicates transmission format information called "C” (e.g., transmission block size, modulation method, coding information, etc.). The terminal monitors the PDCCH using the RNTI information it has.
  • the terminal receives the PDCCH and receives the PDSCH indicated by "B" and "C" through the information of the received PDCCH.
  • Table 2 shows an example of a physical uplink control channel (PUCCH) used in a wireless communication system.
  • PUCCH physical uplink control channel
  • PUCCH can be used to transmit the following uplink control information (UCI):
  • UCI uplink control information
  • HARQ-ACK 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.
  • NACK negative ACK
  • DTX Discontinuous Transmission
  • NACK/DTX NACK/DTX
  • the term HARQ-ACK is used interchangeably with HARQ-ACK/NACK and ACK/NACK.
  • ACK can be expressed with bit value 1
  • NACK can be expressed with bit value 0.
  • CSI Channel State Information: Feedback information for the downlink channel.
  • the terminal generates it based on the CSI-RS(Reference Signal) transmitted by the base station.
  • MIMO(Multiple Input Multiple Output)-related feedback information includes RI(Rank Indicator) and PMI(Precoding Matrix Indicator).
  • CSI can be divided into CSI Part 1 and CSI Part 2 according to the information that CSI indicates.
  • five PUCCH formats can be used to support various service scenarios, various channel environments, and frame structures.
  • 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.
  • the sequence can be a sequence cyclically shifted (CS) from a base sequence used in PUCCH format 0.
  • a sequence cyclically shifted based on a determined CS value m cs of a base sequence having a length of 12 can be transmitted by mapping it to 1 OFDM symbol and 12 REs of 1 RB.
  • M bit 1
  • 1-bit UCI 0 and 1 can be mapped to two cyclically shifted sequences each having a cyclic shift value difference of 6.
  • M bit 2
  • 2-bit UCI 00, 01, 11, 10 can be mapped to four cyclically shifted sequences each having a cyclic shift value difference of 3.
  • PUCCH format 1 can convey 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.
  • the number of OFDM symbols occupied by PUCCH format 1 can be one of 4 to 14.
  • a signal is obtained by multiplying the modulated complex valued symbol d(0) by a sequence having a length of 12. At this time, the sequence can be a base sequence used for PUCCH format 0.
  • the terminal transmits the obtained signal by spreading it with a time-axis OCC (orthogonal cover code) on even-numbered OFDM symbols to which PUCCH format 1 is assigned.
  • PUCCH format 1 determines the maximum number of different terminals that can be multiplexed into the same RB based on the length of the OCC used.
  • a demodulation reference signal DMRS
  • DMRS demodulation reference signal
  • 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.
  • the same sequence can be transmitted through different RBs through the two OFDM symbols.
  • the sequence can be a plurality of modulated complex symbols d(0), ..., d(M symbol -1).
  • M symbol can be M bit /2.
  • the terminal can obtain frequency diversity gain. More specifically, the M bit UCI (M bit >2) is bit-level scrambled and QPSK modulated and mapped to RB(s) of 1 or 2 OFDM symbol(s).
  • the number of RBs can be one of 1 to 16.
  • 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 from 4 to 14.
  • the terminal can generate complex symbols d(0) to d(M symb -1) by modulating M bit UCI (M bit >2) with ⁇ /2-BPSK (Binary Phase Shift Keying) or QPSK.
  • M symb M bit when ⁇ /2-BPSK is used
  • M symb M bit /2 when QPSK is used.
  • 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 precoding (or DFT-precoding) the spread signal and map it to each RE to transmit the spread signal.
  • 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 not transmit some UCI information and transmit only the remaining UCI information according to the priority of the UCI information.
  • PUCCH format 1, PUCCH format 3, or PUCCH format 4 can be configured via RRC signaling to indicate frequency hopping within a slot.
  • an index of an RB to be frequency hopped can be configured via RRC signaling.
  • 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.
  • PUCCH format 1, PUCCH format 3, or PUCCH format 4 may be configured to be repeatedly transmitted in multiple slots.
  • the number K of slots in which PUCCH is repeatedly transmitted may be configured by an RRC signal.
  • the PUCCH to be repeatedly transmitted must start from the OFDM symbol at the same position in each slot and must have the same length. If any OFDM symbol among the OFDM symbols of a slot in which a terminal must transmit a PUCCH is indicated as a DL symbol by an RRC signal, the terminal may not transmit the PUCCH in the corresponding slot and may postpone transmission to the next slot.
  • a terminal can perform transmission and reception using a bandwidth that is smaller than or equal to the bandwidth of a carrier (or cell).
  • the terminal can be configured with a bandwidth part (BWP) consisting of a continuous bandwidth of a portion of the bandwidth of the carrier.
  • BWP bandwidth part
  • a terminal operating in TDD or in an unpaired spectrum can be configured with up to four DL/UL BWP pairs for one carrier (or cell).
  • the terminal can activate one DL/UL BWP pair.
  • a terminal operating in FDD or in a paired spectrum can be configured with up to four DL BWPs for a downlink carrier (or cell) and can be configured with up to four UL BWPs for an uplink carrier (or cell).
  • the terminal can activate one DL BWP and one UL BWP for each 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.
  • a base station can indicate an activated BWP among the configured BWPs of a terminal through downlink control information (DCI).
  • DCI downlink control information
  • a BWP indicated through the DCI is activated, and other configured BWP(s) are deactivated.
  • the base station can include a BPI (bandwidth part indicator) indicating an activated BWP in the DCI scheduling a PDSCH or PUSCH to change a DL/UL BWP pair of the terminal.
  • the terminal can receive the DCI scheduling the PDSCH or PUSCH and identify the activated DL/UL BWP pair based on the BPI.
  • the base station can include a BPI indicating an activated BWP in the DCI scheduling a PDSCH to change a DL BWP of the terminal.
  • 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.
  • Figure 8 is a conceptual diagram explaining carrier aggregation.
  • Carrier aggregation refers to a method in which a wireless communication system uses multiple frequency blocks or (logically meaningful) cells composed of uplink resources (or component carriers) and/or downlink resources (or component carriers) as a single large logical frequency band in order to use 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).
  • PCell Primary cell
  • SCell Secondary Cell
  • PScell Primary SCell
  • 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 B 1 to B 5 can use only a 20 MHz bandwidth and perform communication using one component carrier.
  • Terminals C 1 and C 2 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.
  • FIG. 8 shows a case where terminal C 1 uses two non-adjacent component carriers and terminal C 2 uses two adjacent component carriers.
  • FIG. 9 is a diagram for explaining single-carrier communication and multi-carrier communication.
  • FIG. 9 (a) illustrates the subframe structure of a single carrier
  • FIG. 9 (b) illustrates the subframe structure of a multi-carrier.
  • a general wireless communication system can perform data transmission or reception through one DL band and one UL band corresponding thereto in the case of FDD mode.
  • 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.
  • 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.
  • FIG. 9 (b) illustrates a case where the bandwidth of the UL CC and the bandwidth of the DL CC are both the same and symmetrical, but the bandwidth of each CC can be determined independently.
  • asymmetric carrier aggregation where the number of UL CCs and the number of DL CCs are different is also possible.
  • a DL/UL CC allocated/configured to a specific terminal through RRC can be called the serving DL/UL CC of the specific terminal.
  • a base station can communicate with a terminal by activating some or all of the serving CCs of the terminal or deactivating some of the CCs.
  • the base station can change the CCs to be activated/deactivated and the number of CCs to be activated/deactivated.
  • 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 is handed over.
  • a cell is defined as a combination of downlink resources and uplink resources, that is, a combination of DL CC and UL CC.
  • a cell may consist of only DL resources, or a combination of DL resources and UL resources.
  • 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 means the center frequency of each cell or CC.
  • a cell corresponding to a PCC is referred to as a PCell, and a cell corresponding to an SCC is referred to as an SCell.
  • a carrier corresponding to a PCell in downlink is a DL PCC
  • a carrier corresponding to a PCell in uplink is a UL PCC
  • a carrier corresponding to an SCell in downlink is a DL SCC
  • a carrier corresponding to an SCell in uplink is a UL SCC.
  • the serving cell(s) may consist of one PCell and zero or more SCells. For a UE that is in RRC_CONNECTED state but has not been configured for carrier aggregation or does not support carrier aggregation, there is only one serving cell consisting of PCell only.
  • the term cell used in carrier aggregation is distinguished from the term cell, which refers to a certain geographical area in which communication services are provided by one base station or one antenna group. That is, one 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).
  • a scheduling cell a scheduled cell
  • PCell Primary cell
  • SCell Secondary Cell
  • PScell Primary SCell
  • the present invention refers to a cell of carrier aggregation as a CC, and a cell of a geographical area is referred to as a cell.
  • FIG. 10 is a diagram illustrating an example to which a cross-carrier scheduling technique is applied.
  • 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.
  • a scheduling cell is set, and a DL grant/UL grant transmitted in a PDCCH region of the scheduling cell schedules a PDSCH/PUSCH of a scheduled cell. That is, a search region for multiple component carriers exists in the PDCCH region of the scheduling cell.
  • a PCell is basically a scheduling cell, and a specific SCell can be designated as a scheduling cell by a higher layer.
  • DL component carrier #0 is assumed as a DL PCC (or PCell)
  • DL component carrier #1 and DL component carrier #2 are assumed as DL SCCs (or SCell).
  • 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 CIF according to the NR PDCCH rule (non-cross-carrier scheduling, self-carrier scheduling).
  • a specific CC e.g., DL PCC
  • the terminal monitors PDCCH not including CIF to receive self-carrier scheduled PDSCH, or monitors PDCCH including CIF to receive cross-carrier scheduled PDSCH, depending on whether cross-carrier scheduling is configured for the terminal.
  • 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.
  • the subframes of FIGS. 9 and 10 can be replaced with slots.
  • a terminal (100) may include a processor (110), a communication module (120), a memory (130), a user interface unit (140), and a display unit (150).
  • the processor (110) can execute various commands or programs and process data within the terminal (100).
  • the processor (110) can control the overall operation including each unit of the terminal (100) and control data transmission and reception between the units.
  • the processor (110) can be configured to perform an operation according to the embodiment described in the present invention.
  • the processor (110) can receive slot configuration information, determine the configuration of the slot based on the information, and perform communication according to the determined slot configuration.
  • 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.
  • the communication module (120) may be equipped with a plurality of network interface cards (NICs) such as a cellular communication interface card (121, 122) and an unlicensed band communication interface card (123) in a built-in or external form.
  • NICs network interface cards
  • the communication module (120) is depicted as an integrated module, but each network interface card may be arranged independently depending on the circuit configuration or purpose, unlike the drawing.
  • the cellular communication interface card (121) may transmit and receive a wireless signal 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 first frequency band based on a command of the processor (110).
  • the cellular communication interface card (121) may 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) 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 lower than 6 GHz supported by the corresponding NIC module.
  • the cellular communication interface card (122) may transmit and receive a wireless signal 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).
  • the cellular communication interface card (122) 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 (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.
  • the unlicensed band communication interface card (123) uses the third frequency band, which is an unlicensed band, to transmit and receive wireless signals with at least one of a base station (200), an external device, and a server, 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.
  • 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.
  • the memory (130) stores a control program used in the terminal (100) and various data according to the control program.
  • the 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.
  • 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.
  • 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 a control command of the processor (110).
  • a base station (200) may include a processor (210), a communication module (220), and a memory (230).
  • the processor (210) can execute various commands or programs and process data within the base station (200).
  • the processor (210) can control the overall operation including each unit of the base station (200) and control data transmission and reception between the units.
  • the processor (210) can be configured to perform an operation according to the embodiment described in the present invention.
  • the processor (210) can signal slot configuration information and perform communication according to the signaled slot configuration.
  • 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.
  • the communication module (220) may be equipped with a plurality of network interface cards, such as a cellular communication interface card (221, 222) and an unlicensed band communication interface card (223), in a built-in or external form.
  • the communication module (220) is depicted as an integrated module, but each network interface card may be arranged independently according to the circuit configuration or purpose, unlike the drawing.
  • the cellular communication interface card (221) may transmit and receive a wireless signal with at least one of the terminal (100), the external device, and the server described above using a mobile communication network, and may provide a cellular communication service by the first frequency band based on a command of the processor (210).
  • the cellular communication interface card (221) may 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) may independently perform cellular communication with at least one of the terminal (100), the external device, and the server according to a cellular communication standard or protocol of a frequency band lower than 6 GHz supported by the corresponding NIC module.
  • the cellular communication interface card (222) may transmit and receive a wireless signal with at least one of a terminal (100), an external device, and a server by using a mobile communication network, and may provide a cellular communication service by a second frequency band based on a command of the processor (210).
  • the cellular communication interface card (222) 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 (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.
  • the unlicensed band communication interface card (223) transmits and receives a wireless signal with at least one of a terminal (100), an external device, and a server by 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.
  • the unlicensed band may be a band of 2.4 GHz, 5 GHz, 6 GHz, 7 GHz, or 52.6 GHz or higher.
  • 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 shown to logically distinguish elements of the device. Accordingly, the elements of the device described above may be mounted as one chip or as 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), may be additionally provided in the base station (200) as needed.
  • a terminal can be configured with a slot format from a base station in a TDD or unpaired spectrum system.
  • the slot format can mean a type of symbols in a slot.
  • the symbol type can be at least one of a downlink symbol (DL symbol), an uplink symbol (UL symbol), or a flexible symbol.
  • the terminal can be configured with a symbol type for a slot in a radio frame from the base station.
  • a flexible symbol can mean a symbol that is not composed of a downlink symbol or an uplink symbol.
  • the two respective patterns may be applied consecutively to symbols in the time domain, respectively.
  • 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.
  • a cell-specific flexible symbol may be set as a downlink symbol or an uplink symbol.
  • the information about each symbol type may include at least one of an index for a slot in a period, the number of downlink symbols starting from a first symbol of the slot indicated by the index, and the number of uplink symbols starting from a last symbol of the slot indicated by the index.
  • the terminal may be set so that all symbols in the slot are downlink symbols or so that all symbols in 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.
  • the base station can transmit information about the slot format to the terminal through the SFI (slot format indicator) of DCI format 2_0 included in the group common (GC)-PDCCH.
  • SFI slot format indicator
  • the GC-PDCCH can be CRC scrambled with SFI-RNTI for the terminals receiving the information about the slot format.
  • SFI transmitted through the GC-PDCCH can be described as a dynamic SFI.
  • the terminal can be indicated by the dynamic SFI through the GC-PDCCH whether the symbols in the slot are the cell-specific flexible symbol or the terminal-specific flexible symbol, the downlink symbol, the uplink symbol, or the flexible symbol. In other words, only the flexible symbol that the terminal has been semi-statically configured can be indicated as any one of the downlink symbol, the uplink symbol, and the flexible symbol through the dynamic SFI. The terminal may not expect that the downlink symbol or the uplink symbol that has been semi-statically configured 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 in order to receive the GC-PDCCH transmitting the DCI format 2_0 including the dynamic SFI. If the terminal performs the blind decoding and succeeds in receiving 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.
  • the terminal can be configured with a combination of slot formats that can be indicated from the base station via dynamic SFI.
  • the slot format combination is for each of one or more and 256 or fewer slots, and the terminal can be configured with a slot format combination for any one of one or more and 256 or fewer slots via dynamic SFI, and the dynamic SFI can include an index indicating to which slot the slot format combination is applied.
  • Table 3 is a table showing slot format combinations for each slot (refer to 3GPP TS38.213).
  • D represents a downlink symbol
  • U represents an uplink symbol
  • F represents a flexible symbol.
  • up to two DL/UL switchings can be allowed within one slot.
  • configuration, setting, and instruction may be used interchangeably. That is, the terms configured, set, and instruction may have the same meaning, and similarly, the terms configured, set, and instruction may have the same meaning.
  • Figures 12 to 14 illustrate a subband setting method according to one embodiment of the present invention.
  • a terminal when a terminal is configured or instructed with a slot format, if limited time domain resources are allocated as uplink resources, problems of reduced uplink coverage, increased latency, and reduced capacity may occur.
  • specific time domain resources within a cell can be used for both downlink reception and uplink transmission. Even if a base station uses specific time domain resources for both downlink reception and uplink transmission, the terminal supports only a half-duplex communication method, so that only one operation, either downlink reception or uplink transmission, can be performed in the same specific time domain resource.
  • a specific time domain resource can be a cell-specific flexible symbol among the semi-statically configured slot formats, to minimize inter-UE interference due to transmission and reception in different symbol types (DL/UL or UL/DL).
  • a terminal can receive a cell-specific slot configuration semi-statically.
  • the terminal can perform downlink reception or uplink transmission on resources scheduled from a base station.
  • Resources scheduled for PDSCH reception to a first UE and resources scheduled for PUSCH transmission to 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 one 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 of the terminal are taken into account.
  • a subband in this specification may be set on a frequency-domain resource (slot or symbol) within a time-domain resource. In this case, the frequency-domain resource may be included within a carrier bandwidth of the terminal.
  • 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 a plurality of subbands in the frequency domain.
  • the plurality of 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)
  • 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.
  • the subband of the same format can be at most 1. That is, one cell-specific flexible slot/symbol section can be configured with at most 1 downlink subband, 1 uplink subband, and 1 flexible subband each. Referring to FIG. 13, a cell-specific flexible slot/symbol can be configured with multiple subbands. At this time, the multiple subbands can be configured with 1 downlink subband, 1 uplink subband, and 1 flexible subband each. A guard band may be required to minimize the impact of UL/DL interference between the downlink subband and the uplink subband. 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.
  • a terminal 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.
  • multiple subbands may be composed of non-overlapping RBs in the frequency domain.
  • a flexible subband may be configured by considering a guard band between an uplink subband and a downlink subband. That is, at least one flexible subband may exist between an uplink subband and a downlink subband. Method 1-1 may require a smaller number of guard bands than Method 1-2. Accordingly, more resources may be available for downlink reception and uplink transmission. In addition, since Method 1-1 provides more frequency resources when a CORESET resource for PDCCH monitoring is set to a UE than Method 1-2, CORESET may be flexibly configured within one downlink subband (or flexible subband). In addition, Method 1-1 may also provide more frequency domain resources available for uplink transmission than Method 1-2.
  • Method 1-1 may be advantageous over Method 1-2 in terms of frequency resource usage efficiency.
  • the methods described in this specification below are based on, but are not limited to, method 1-1.
  • 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
  • an RB within a flexible subband may be described as a flexible RB.
  • a method for configuring multiple subbands in a frequency domain can be applied to a cell-specific flexible slot or symbol, as well as a cell-specific downlink slot or symbol or a cell-specific uplink slot or symbol. 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.
  • the method of configuring multiple subbands in the above frequency domain can be applied to a terminal-specific flexible slot or symbol.
  • the method of configuring multiple subbands in the above frequency domain can be applied to a terminal-specific downlink slot or symbol.
  • - SBFD subband non-overlapping full duplex
  • the 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.
  • a UL subband can be configured on a DL slot/symbol, or a UL subband can be configured on a flexible slot/symbol.
  • a DL subband can be configured on a flexible slot/symbol.
  • the DL slot/symbol and the flexible slot/symbol can be configured through a cell-specific RRC signal (e.g., TDD-ConfigCommon) and/or a UE-specific RRC signal (e.g., TDD-ConfigDedicated).
  • TDD-ConfigCommon a cell-specific RRC signal
  • UE-ConfigDedicated e.g., TDD-ConfigDedicated
  • - SBFD interval (or subband interval): It means a time interval in which a subband is configured/indicated on a cell/BWP.
  • the SBFD interval includes a time interval in which an uplink subband is configured/indicated.
  • the SBFD interval includes a slot in which an uplink subband is configured/indicated.
  • 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).
  • Non-SBFD interval (or non-subband interval): It means 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.
  • a non-SBFD-slot (or non-subband-slot) represents a slot in which a subband is not configured/indicated
  • a non-SBFD-symbol (or non-subband symbol) represents a symbol in which a subband is not configured/indicated.
  • the non-SBFD interval means 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.
  • Legacy NR system refers to a system that operates in the legacy NR manner because SBFD operation is not supported or set.
  • a method for a terminal to transmit a physical uplink shared channel is described.
  • the terminal can transmit uplink data (e.g., UL-SCH TB) to a base station through the PUSCH.
  • the terminal can transmit uplink data by using a method for scheduling PUSCH obtained from DCI in PDCCH (DG, dynamic grant) or a method for transmitting PUSCH according to resources and transmission methods preset by the base station (CG, configured grant).
  • DG DCI in PDCCH
  • CG configured grant
  • the DCI that the terminal can recognize by decoding the PDCCH may include PUSCH scheduling information.
  • the PUSCH scheduling information may include information on the time domain (hereinafter referred to as TDRA, time-domain resource assignment) and information on the frequency domain (hereinafter referred to as FDRA, frequency-domain resource assignment).
  • the terminal may interpret the DCI transmitted through the PDCCH based on information on the control resource set (CORESET) and the search space, and perform an operation indicated in the DCI.
  • the DCI format for scheduling the PUSCH may be one of the DCI formats 0_0, 0_1, or 0_2.
  • the time domain information of PUSCH indicated in the TDRA field in DCI format 0_0, 0_1, or 0_2 includes:
  • the terminal can be set to K2 and SLIV from the base station. Alternatively, the terminal can be set to K2, S, and L from the base station.
  • ⁇ PUSCH and ⁇ PDCCH are the SCS of the cell (or BWP) where the PUSCH is scheduled and the cell (or BWP) that receives the PDCCH, respectively.
  • PUSCH can be set to either PUSCH mapping Type A or PUSCH mapping Type B.
  • 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 from 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).
  • 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)
  • the symbol length of the PUSCH can be set to one of the values from 1 to 14 (12 for extended CP).
  • SLIV can be set to one of the values from 1 to 14 (12 for extended CP).
  • SLIV can be set to one of the values from 1 to 27 (23 for extended CP).
  • 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.
  • 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 being instructed with a bitmap per RBG.
  • the number of PRBs included in one RBG can be configured from the base station.
  • the terminal determines/interprets that PUSCH is not scheduled for any PRB among the PRBs in the corresponding RBG if the bit value indicated by the bitmap is 0, and determines/interprets that PUSCH is scheduled for all PRBs in the corresponding RBG if the bit value is 1.
  • the bit values can be applied in the opposite direction depending on the implementation method.
  • resource allocation information may indicate information of consecutive PRBs allocated for uplink transmission.
  • the resource allocation information includes a RIV (resource indication value) 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 the active BWP of the terminal.
  • 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.
  • 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.
  • MSB most significant bit
  • the NR system supports CG (configured grant)-based PUSCH (hereinafter, CG-PUSCH) transmission scheme to support uplink URLLC transmission, etc.
  • CG-PUSCH transmission scheme is also called grant-free transmission scheme.
  • the CG-PUSCH transmission scheme is a scheme in which a terminal receives resources that can be used for PUSCH transmission from a base station in advance through a higher layer (e.g., RRC) signal and transmits PUSCH through the corresponding resources.
  • the CG-PUSCH transmission scheme can be divided into the following two types depending on whether activation or release is possible through DCI.
  • the terminal can receive in advance the period, time/frequency resources, and transmission method for PUSCH transmission from the base station through upper layer (e.g., RRC) signals.
  • the transmission method can include MCS (modulation and coding scheme), TBS (TB size), etc.
  • 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).
  • a higher layer e.g. RRC
  • PDCH DCI
  • the CG-PUSCH transmission scheme can support repeated PUSCH transmission in multiple slots to ensure reliable uplink transmission.
  • 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).
  • 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.
  • the terminal can end the repeated transmission 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.
  • the UL grant means the DCI that schedules the PUSCH.
  • the transmission process of PUSCH repetition transmission type A of the terminal is as follows.
  • the terminal receives DCI format 0_1 to 0_2 through the PDCCH for scheduling the PUSCH from the base station, PUSCH repetition transmission is possible in K consecutive slots.
  • 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.
  • the terminal receives the PDCCH for scheduling 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.
  • the time/frequency resources over which the PUSCH is transmitted in each slot are identical to the time/frequency resources indicated by the DCI. That is, PUSCH can be repeatedly transmitted in the same symbol and PRB(s) within each slot.
  • the transmission process of PUSCH repetition transmission type B to support low-latency PUSCH repetition transmission to satisfy requirements of URLLC, etc. is as follows.
  • the terminal can be indicated with the start symbol (S) of the PUSCH and the length (L) of the PUSCH through the TDRA field.
  • the PUSCH having the start symbol and the 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.
  • the terminal can be indicated with 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.
  • 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.
  • nominal PUSCHs are determined as continuous symbols, but can be determined as discontinuous symbols if invalid symbols are excluded.
  • the actual PUSCH can be determined as continuous symbols in one nominal PUSCH excluding invalid symbols. Here, if continuous symbols cross a slot boundary, the actual PUSCH can be divided based on the slot boundary.
  • invalid symbols may at least include DL symbols configured by the base station to the terminal.
  • a terminal 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 the slot and does not postpone transmission to the next slot.
  • 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.
  • the above DL symbol may include a cell-specifically configured or terminal-specifically configured downlink symbol.
  • 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 .
  • a terminal transmits a physical uplink control channel (PUCCH).
  • PUCCH physical uplink control channel
  • the terminal 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 about 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 HARQ-ACK about whether reception of the PDSCH is successful.
  • HARQ-ACK information may be a HARQ-ACK regarding the successful reception of the DCI format 1_0, 1_1 or 1_2 (or, DL SPS release).
  • SPS PDSCH semi-static physical downlink shared channel
  • 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 a scheduled PUCCH should be transmitted.
  • the value of K1 may be a non-negative integer value.
  • the K1 value of DCI format 1_0 may indicate one of the values ⁇ 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 from a higher layer (e.g., RRC).
  • the terminal can determine a slot for transmitting a PUCCH including the first type of HARQ-ACK information as follows.
  • the terminal can determine an uplink slot overlapping with the last symbol of a PDSCH corresponding to the HARQ-ACK information.
  • the uplink slot for the terminal to transmit a PUCCH including HARQ-ACK information can be m+K1.
  • the index of the uplink slot is a value according to the subcarrier spacing of the (uplink) BWP in which the PUCCH is transmitted.
  • the ending symbol indicates the last symbol of the PDSCH scheduled in the last slot among the slots in which the PDSCH is received.
  • a terminal may be configured to repeatedly transmit a long PUCCH (PUCCH format 1, 3, 4) in 2, 4, or 8 slots.
  • PUCCH format 1, 3, 4 When a terminal is configured to repeatedly transmit a PUCCH, the same UCI may be repeatedly transmitted in every slot.
  • the symbol configuration of the repeatedly transmitted PUCCHs is the same. That is, the repeatedly transmitted PUCCHs start from the same symbol in each slot and consist of the same number of symbols.
  • a terminal When a terminal performs repeated PUCCH transmission, if the symbol(s) on which PUCCH should be transmitted in a specific slot overlaps with an invalid symbol (e.g., a DL symbol configured semi-statically through a TDD configuration or a symbol configured for reception of an SS/PBCH block), the terminal may not transmit PUCCH in the slot and may postpone PUCCH transmission to the next slot. Thereafter, if the symbol(s) on which PUCCH should be transmitted in the slot in which PUCCH transmission is postponed does not overlap with an invalid symbol, the terminal may transmit PUCCH in the slot.
  • an invalid symbol e.g., a DL symbol configured semi-statically through a TDD configuration or a symbol configured for reception of an SS/PBCH block
  • the above DL symbol may include a cell-specifically configured or terminal-specifically configured downlink symbol.
  • 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 .
  • the repeated transmission may be a PUSCH repeated transmission type A, i.e., inter-slot PUCCH repeated transmission.
  • the terminal When a terminal is scheduled or configured via RRC to repeatedly transmit a PUSCH or PUCCH in multiple slots, the terminal must determine a slot in which repeated transmission is possible.
  • a terminal can determine a slot as a slot for repeated transmission only when all symbol(s) 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 transmission to a next slot. That is, the terminal may not determine the slot as a slot for repeated transmission.
  • a higher layer e.g., RRC
  • the terminal may postpone transmission of repeated PUCCH transmission to the next slot for repeated transmission, but may not postpone transmission of repeated PUSCH transmission. That is, the terminal may perform fewer PUSCH repeated transmissions than the number of repeated transmissions configured or instructed by the base station.
  • a terminal may be configured or instructed to transmit a PUSCH twice repeatedly with PUSCH repetition transmission type A.
  • normal slot#1 may be a slot or symbol(s) in which the terminal is not configured with a subband
  • SBFD slot#2 may be a slot or symbol(s) in which the terminal is configured with a subband. Since all resources scheduled to transmit a 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.
  • 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.
  • the terminal cannot determine SBFD slot#2 as a slot in which PUSCH repetition transmission is possible even if the symbols scheduled to transmit a 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 repeated PUSCH transmissions because the slot is not determined as a slot capable of repeated transmission.
  • the terminal when a terminal is configured or instructed to operate in a subband, the terminal may additionally consider 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, to determine resources available for repeated transmission. Specifically, when all symbols and RBs scheduled for PUSCH or PUCCH repeated transmission or configured via RRC in a slot or symbol(s) configured or instructed to operate in a subband 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 in which PUSCH or PUCCH repeated transmission is possible and may postpone PUSCH or PUCCH transmission to a next slot in which repeated transmission is possible only if a symbol and an RB scheduled for PUSCH or PUCCH transmission or configured via RRC overlap with a DL symbol included in an RB other than an uplink subband (i.e., an RB in a downlink subband or a guard band) or a symbol configured for reception of an SS/PBCH block in an RB other than an uplink subband (i.e., an RB in a downlink subband or a guard band).
  • the UE may postpone transmission of PUCCH repeated transmission to a next slot in which repeated transmission is possible but may not postpone transmission of PUSCH repeated transmission. That is, the UE may perform PUSCH repeated transmission as many times as the number of repeated transmissions configured or instructed by the base station.
  • Fig. 16 illustrates the first method described above. Compared with the method of Fig. 15, which only considered the availability of resources for repeated transmission in the time domain, i.e., symbol units, the method of Fig. 16 can also consider the availability of resources for repeated transmission in the frequency domain, i.e., RB units. In the case of Fig. 16, since symbols and RBs scheduled to transmit PUSCH or configured via RRC are available for uplink transmission, the terminal can determine SBFD slot#2 as a slot in which PUSCH repeated transmission is possible.
  • Fig. 17 illustrates a situation where resources configured for reception of SS/PBCH blocks and resources scheduled for repeated transmission of PUSCH or PUCCH or configured via RRC overlap each other in symbol units.
  • terminal operations according to the type of SS/PBCH block are as follows.
  • a terminal can be cell-specifically configured to receive an SS/PBCH block having a PCI (physical cell ID) that is the same as the PCI of the serving cell.
  • a cell-specific resource for receiving an SS/PBCH block can be configured by an RRC parameter, ssb-PositionsInBurst. If the resource cell-specifically configured to receive an SS/PBCH block and the resource scheduled or configured via RRC to transmit in repetitive transmission slots/symbols of a PUSCH or PUCCH overlap each other on a symbol-by-symbol basis, the terminal behavior is as follows.
  • the UE can determine the corresponding slot as a slot in which PUSCH or PUCCH repeated transmission is possible. That is, 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, from the perspective of the UE, the UE is configured or instructed to prioritize PUSCH or PUCCH transmission over the corresponding slot without intending to receive an SS/PBCH block.
  • 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., via 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.
  • scheduling a PUSCH or PUCCH from the base station through dynamic scheduling to overlap with a symbol that is cell-specifically configured to receive an SS/PBCH block may be determined as an instruction from the UE to prioritize PUSCH or PUCCH transmission over the slot without intending to receive an SS/PBCH block.
  • the UE may determine that the resource for PUSCH or PUCCH transmission configured via RRC is configured to prioritize reception of SS/PBCH. This is a method that allows a specific terminal to transmit a PUSCH or PUCCH dynamically scheduled by the base station in an uplink subband even if other terminals in the cell receive SS/PBCH blocks in a downlink subband, since the base station supports a full-duplex communication method.
  • the terminal may be specifically configured to receive SS/PBCH blocks having non-serving cell PCIs from multiple TRPs (transmission and reception points).
  • TRPs transmission and reception points
  • the terminal behavior is as follows.
  • 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 a PUSCH resource configured in a position of a symbol to which an SS/PBCH block is mapped and a DL-to-UL switching gap symbol for RF retuning.
  • the terminal may receive the SS/PBCH block and not transmit the PUSCH.
  • the terminal operating in a half-duplex mode cannot perform transmission and reception simultaneously in the same symbol, and considering 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, the terminal prioritizes reception of the SS/PBCH block. Therefore, the terminal may perform reception of the SS/PBCH block and not transmit the PUSCH.
  • 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 each other in units of RBs, the UE cannot perform simultaneous transmission and reception on different frequency resources of the same symbol since the UE operates in a half-duplex manner.
  • this is to prioritize reception of the SS/PBCH block over PUCCH transmission in consideration of the fact that the base station is configured to specifically receive an SS/PBCH block for the UE in order to receive PDSCHs transmitted from multiple TRPs of a non-serving cell.
  • the base station is configured to specifically receive an SS/PBCH block for the UE in order to receive PDSCHs transmitted from multiple TRPs of a non-serving cell.
  • the terminal since PUCCH cannot be transmitted in the corresponding slot, the terminal may perform reception of SS/PBCH blocks and not transmit PUCCH.
  • the terminal may be specifically configured to receive an SS/PBCH block having an additional PCI associated with an activated TCI (Transmission Configuration Indicator) state among the SS/PBCH blocks received from multiple TRPs.
  • TCI Transmission Configuration Indicator
  • the terminal operation is as follows.
  • 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 a base station gives priority to reception of an SS/PBCH block having a PCI associated with a TCI state activated by the terminal among SS/PBCH blocks configured by the base station for reception of PDSCHs transmitted from multiple TRPs of a non-serving cell. Therefore, the 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.
  • the terminal 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 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 gives 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 for reception of PDSCHs transmitted from multiple TRPs of a non-serving cell. 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.
  • the terminal can receive SS/PBCH block.
  • the terminal can rate-match and transmit PUSCH for PUSCH resource configured in the position of symbol to which SS/PBCH block is mapped and downlink-uplink switching gap symbol. Since the base station may have intentionally configured the terminal to receive SS/PBCH for SS/PBCH block having additional PCI associated with activated TCI state among SS/PBCH blocks received from multiple TRPs, the reception of SS/PBCH is given priority.
  • the terminal since RBs occupied by PUSCH and RBs occupied by SS/PBCH block do not overlap each other in RB unit, the terminal must operate in half-duplex mode and therefore cannot perform simultaneous transmission and reception on different frequency resources of the same symbol.
  • This method can guarantee the maximum downlink reception and uplink transmission configured to the terminal when the terminal is configured or instructed to do so in a subband.
  • 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 base station configures the terminal to specifically receive an SS/PBCH block so that the base station gives 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 reception of PDSCHs transmitted from multiple TRPs of a non-serving cell, over transmission of a PUCCH. Therefore, the terminal may perform reception of an SS/PBCH block and not transmit a PUCCH.
  • the terminal may determine that the resource scheduled or configured via a higher layer (e.g., RRC) for a PUSCH or PUCCH 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 not to receive the SS/PBCH block in the slot and to give priority to PUSCH or PUCCH transmission.
  • a higher layer e.g., RRC
  • 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 resources configured via a higher layer (e.g., RRC).
  • a higher layer e.g., RRC
  • the terminal behavior is as follows.
  • the terminal 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 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 configures the terminal to receive an SS/PBCH block specifically for link recovery, the reception of the SS/PBCH block is to be prioritized over the PUCCH transmission. 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.
  • 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 the same symbol(s) when the terminal is configured or instructed to use a subband.
  • 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 perform transmission and reception simultaneously in the same symbol and that the base station configures the terminal to receive a SS/PBCH block specifically for link recovery. Therefore, the terminal may perform reception of the SS/PBCH block and not transmit the PUSCH.
  • the terminal 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 each other in units of RBs, the terminal must operate in a half-duplex manner and therefore cannot perform simultaneous transmission and reception on different frequency resources of the same symbol.
  • the terminal may receive an SS/PBCH block and not transmit a PUCCH.
  • a terminal operating in a half-duplex mode cannot perform transmission and reception simultaneously in the same symbol, and considering that the base station configures the terminal to receive an SS/PBCH block specifically for link recovery, the reception of the SS/PBCH block is to be given priority over the transmission of the PUCCH. Therefore, the terminal may perform reception of an SS/PBCH block and not transmit a PUCCH.
  • Fig. 18 illustrates a situation where (i) resources configured for reception of SS/PBCH blocks and (ii) resources scheduled for repeated transmission of PUSCH or PUCCH or configured through a higher layer (e.g., RRC) overlap each other in RE units.
  • terminal operations according to the type of SS/PBCH block are as follows.
  • the UE actions are as follows.
  • the UE may not expect to be instructed to transmit PUCCH via DCI format 1_0, 1_1, or 1_2 on an RE configured to receive SS/PBCH blocks. This is to prioritize reception of SS/PBCH blocks over PUCCH transmission, considering that a UE operating in a half-duplex mode cannot perform simultaneous transmission and reception on the same RE and that the base station configures the UE to receive SS/PBCH blocks cell-specifically for periodic synchronization. Therefore, the UE may not expect to be instructed to perform reception of SS/PBCH blocks and transmit PUCCH such that at least one RE overlaps with the SS/PBCH blocks.
  • the UE can receive SS/PBCH blocks and transmit PUSCH by rate-matching it for REs to which SS/PBCH blocks are mapped and downlink-uplink switching gap symbols. This is because, from the perspective of a UE, it must operate in a half-duplex manner and therefore the UE cannot perform transmission and reception simultaneously in the same RE unit.
  • This method is a method that can guarantee downlink reception and uplink transmission configured for the UE to the greatest extent possible in symbol(s) excluding the same RE(s) when the UE is configured or instructed to operate in a subband.
  • 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 base station is configured to receive a cell-specific SS/PBCH block in order to prioritize reception of the SS/PBCH block over PUSCH transmission, considering that the base station has configured the UE for periodic synchronization. Therefore, the UE may perform reception of the SS/PBCH block and not transmit the PUSCH.
  • a terminal may receive an SS/PBCH block and not transmit a PUCCH. This is because, from the perspective of a terminal, the terminal cannot perform simultaneous transmission and reception in the same RE unit since the terminal must operate in a half-duplex manner.
  • the base station is configured to receive a SS/PBCH block cell-specifically because the base station gives priority to the reception of a SS/PBCH block over the transmission of a PUCCH for periodic synchronization with the terminal.
  • the terminal may perform reception of an SS/PBCH block and not transmit a PUCCH.
  • the UE may receive an SS/PBCH block and not transmit a PUCCH.
  • a UE operating in a semi-duplex mode cannot perform simultaneous transmission and reception on the same RE, and the base station is configured to receive a cell-specific SS/PBCH block in order to prioritize reception of the SS/PBCH block over transmission of the PUCCH, considering that the base station has configured the UE for periodic synchronization. Therefore, the UE may perform reception of an SS/PBCH block and not transmit a PUCCH.
  • the UE may not expect to be instructed to transmit PUSCH via DCI format 0_0, 0_1, or 0_2 on an RE configured to receive SS/PBCH blocks.
  • a UE operating in a half-duplex mode cannot perform simultaneous transmission and reception on the same RE, and the reason why the eNB configures the UE to specifically receive SS/PBCH blocks is to prioritize reception of SS/PBCH blocks, considering that the eNB configures the UE to receive PDSCH transmitted from multiple TRPs of a cell other than the serving cell. Therefore, the UE may not expect to be instructed to perform reception of SS/PBCH blocks and transmit PUSCH such that at least one RE overlaps.
  • the terminal behavior is as follows.
  • 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. 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 configures the terminal to specifically receive an SS/PBCH block for link recovery, reception of an SS/PBCH block is to be prioritized over PUSCH transmission. Therefore, the 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 the SS/PBCH block.
  • 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 a 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 configures the terminal to specifically receive an SS/PBCH block for link recovery, reception of an SS/PBCH block is to be prioritized over PUCCH transmission. Accordingly, 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 RE overlaps the SS/PBCH block.
  • the UE can receive SS/PBCH block and transmit PUSCH in rate-matching manner. For example, the UE can transmit PUSCH in rate-matching manner for RE to which SS/PBCH block is mapped and downlink-uplink switching gap symbol. This is because the UE must operate in half-duplex mode and therefore cannot perform simultaneous transmission and reception in the same RE unit.
  • This method is a method that can guarantee downlink reception and uplink transmission configured for the UE to the greatest extent possible in resource(s) excluding colliding RE(s) when the UE is configured or instructed to operate in subband.
  • the UE may receive the SS/PBCH block and not transmit the PUSCH.
  • a UE operating in a half-duplex mode cannot perform transmission and reception simultaneously on the same RE, and considering that the base station configures the UE to specifically receive an SS/PBCH block for link recovery, the reception of the SS/PBCH block is to be prioritized over the PUSCH transmission. Therefore, the UE may perform reception of the SS/PBCH block and not transmit the PUSCH.
  • 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 an SS/PBCH block over PUCCH transmission in consideration of the fact that the base station is configured to receive a SS/PBCH block specifically for the UE for link recovery. Meanwhile, although it is possible to transmit a PUSCH by rate-matching it on an RE basis, if even one of the PUCCH symbols cannot be used for uplink transmission, the PUCCH cannot be transmitted in the corresponding slot. Therefore, the UE may perform reception of an SS/PBCH block and not transmit a PUCCH.
  • the UE may receive an SS/PBCH block and not transmit a PUCCH.
  • a UE operating in a semi-duplex mode cannot perform simultaneous transmission and reception on the same RE, and considering that the base station configures the UE to specifically receive an SS/PBCH block for link recovery, the reception of an SS/PBCH block is to be prioritized over PUCCH transmission. Therefore, the UE may perform reception of an SS/PBCH block and not transmit a PUCCH.
  • the terminal can transmit the remaining repetitive transmissions by rate-matching them like the first repetitive transmission. This is to facilitate soft combining of repetitive transmissions of PUSCH at the base station by having the terminal determine the TBS (TB size) for the PUSCH repetitive transmissions to be the same and transmit them.
  • TBS TB size
  • the terminal may not determine that the slot is a slot that allows repetitive transmission and thus may not transmit the PUSCH. This is to facilitate soft combining of repetitive transmissions of the PUSCH at the base station by having the terminal determine and transmit the TBS for the repetitive PUSCH transmissions in the same manner.
  • the terminal may not always determine the slot operating as a subband as a slot capable of repeated transmission. That is, when the terminal is configured or instructed to repeatedly transmit PUSCH or PUCCH in multiple slots, it may determine only the slots not operating as subbands as slots capable of repeated transmission.
  • 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 basis.
  • a terminal operating in a half-duplex manner cannot perform transmission and reception simultaneously in the same symbol.
  • the operation of the terminal according to whether the uplink transmission is semi-statically configured as a higher layer (e.g., RRC) signal or dynamically scheduled via DCI for each uplink signal/channel, and the operation of the terminal according to the type of the SS/PBCH block are proposed.
  • the terminal operations are as follows.
  • 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 and transmit the PUSCH for the PUSCH resources configured in the position of the symbol overlapping with the SS/PBCH block and the DL-to-UL switching gap symbol.
  • This method can ensure that the terminal can receive downlink and transmit uplink as configured in symbol(s) except for the same symbol(s) as the terminal is configured or instructed to operate in a subband.
  • the terminal may receive the SS/PBCH block and not transmit the PUSCH. This is to prioritize reception of the SS/PBCH block since a terminal operating in a half-duplex mode cannot perform transmission and reception simultaneously in the same symbol.
  • 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 since a UE operating in a half-duplex mode cannot perform simultaneous transmission and reception in the same symbol.
  • RRC configured PUCCH If a symbol configured cell-specifically to receive SS/PBCH blocks and a resource configured via RRC to transmit PUCCH overlap each other in symbol units, 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 perform simultaneous transmission and reception in the same symbol.
  • 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 since a UE operating in half-duplex mode cannot perform simultaneous transmission and reception in the same symbol.
  • 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 terminal 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 terminal can receive the SS/PBCH block and transmit the SRS by considering the downlink-uplink switching gap symbol. That is, the terminal 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).
  • 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 for the terminal to receive SS/PBCH blocks and the resources configured for SRS transmission partially overlap in the time domain, the configured downlink reception and uplink transmission for the terminal can be guaranteed to the maximum extent.
  • the terminal may receive the SS/PBCH block and not transmit the SRS. This is to prioritize reception of the SS/PBCH block since a terminal operating in a half-duplex mode cannot perform transmission and reception simultaneously in the same symbol.
  • DCI indicated SRS The UE may not expect to be instructed to transmit SRS in a symbol configured to receive an SS/PBCH block 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). This is to prioritize reception of SS/PBCH blocks since a UE operating in half-duplex mode cannot perform simultaneous transmission and reception in the same symbol.
  • the terminal operation is as follows.
  • 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 and transmit the PUSCH for the PUSCH resources configured in the symbol overlapping with the SS/PBCH block and the position of the downlink-uplink switching gap symbol.
  • This method can ensure that the terminal can receive downlink and transmit uplink as configured in symbol(s) except for the same symbol(s) as the terminal is configured or instructed to operate in a subband.
  • the terminal may receive the SS/PBCH block and not transmit the PUSCH. This is to prioritize reception of the SS/PBCH block since a terminal operating in a half-duplex mode cannot perform transmission and reception simultaneously in the same symbol.
  • 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 since a UE operating in a half-duplex mode cannot perform simultaneous transmission and reception in the same symbol.
  • RRC configured PUCCH If a symbol configured cell-specifically to receive SS/PBCH blocks and a resource configured via RRC to transmit PUCCH overlap each other in symbol units, 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 perform simultaneous transmission and reception in the same symbol.
  • 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 since a UE operating in half-duplex mode cannot perform simultaneous transmission and reception in the same symbol.
  • 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 terminal 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 terminal can receive the SS/PBCH block and transmit the SRS considering the downlink-uplink switching gap symbol. That is, the terminal can receive the SS/PBCH block for the overlapping symbol(s) and transmit the SRS in the symbol(s) excluding the switching gap symbol among the non-overlapping symbol(s).
  • the terminal can cancel or transmit the SRS in symbol units in the symbol(s) configured for SRS transmission, the terminal 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.
  • the terminal may receive the SS/PBCH block and not transmit the SRS. This is to prioritize reception of the SS/PBCH block since a terminal operating in a half-duplex mode cannot perform transmission and reception simultaneously in the same symbol.
  • DCI indicated SRS The UE may not expect to be instructed to transmit SRS in a symbol configured to receive an SS/PBCH block 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). This is to prioritize reception of SS/PBCH blocks since a UE operating in half-duplex mode cannot perform simultaneous transmission and reception in the same symbol.
  • the terminal operation is as follows.
  • 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 can transmit PUSCH in the corresponding 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 inactivated TCI state, the UE can determine that the UE is configured to give priority to PUSCH transmission over SS/PBCH block in the corresponding slot.
  • DG(dynamic grant) PUSCH If a PUSCH is instructed to be transmitted 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 the PUSCH through dynamic scheduling from the base station to overlap with a symbol specifically configured for the UE to receive an SS/PBCH block may determine that the specific UE does not intend to receive the SS/PBCH block in the corresponding slot and is instructed to give priority to PUSCH transmission.
  • DCI indicated PUCCH If a symbol configured to receive an SS/PBCH block is instructed to transmit a PUCCH via DCI format 1_0, 1_1 or 1_2, the terminal can 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 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 prioritize PUCCH transmission.
  • DCI indicated SRS If the terminal is instructed to transmit SRS in a symbol configured to receive an SS/PBCH block 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), the terminal can transmit SRS without receiving SS/PBCH block in the overlapping symbol(s). That is, from the perspective of a specific terminal, the base station dynamically schedules SRS to overlap with a symbol specifically configured for the terminal to receive an SS/PBCH block, and it can be determined that the specific terminal does not intend to receive an SS/PBCH block in the slot and is instructed to prioritize SRS transmission.
  • the terminal operation is as follows.
  • CG (configured grant) PUSCH Type 1 or CG PUSCH Type 2 If the symbol(s) configured to transmit PUSCH via RRC, i.e., CG PUSCH Type 1 or CG PUSCH Type 2, partially overlaps with the symbol(s) configured to receive SS/PBCH blocks, the UE may receive the SS/PBCH blocks and rate-match and transmit the PUSCH for the PUSCH resources configured in the symbols overlapping with the SS/PBCH blocks and the positions of DL-to-UL switching gap symbols.
  • This method can ensure that the terminal can receive downlink and transmit uplink as configured in symbol(s) except for the same symbol(s) as the terminal is configured or instructed to operate in a subband.
  • the terminal may receive the SS/PBCH block and not transmit the PUSCH. This is to prioritize reception of the SS/PBCH block since a terminal operating in a half-duplex mode cannot perform transmission and reception simultaneously in the same symbol.
  • RRC configured PUCCH If a symbol configured cell-specifically to receive SS/PBCH blocks and a resource configured via RRC to transmit PUCCH overlap each other in symbol units, 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 perform simultaneous transmission and reception in the same symbol.
  • DCI indicated PUCCH If a symbol configured to receive an SS/PBCH block is instructed to transmit a PUCCH via DCI format 1_0, 1_1 or 1_2, the terminal can 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 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 prioritize PUCCH transmission.
  • 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 terminal 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 terminal can receive the SS/PBCH block and transmit the SRS considering the downlink-uplink switching gap symbol. That is, the terminal 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).
  • the terminal 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 downlink reception and uplink transmission configured for the terminal can be guaranteed to the maximum extent.
  • the terminal may receive the SS/PBCH block and not transmit the SRS. This is to prioritize reception of the SS/PBCH block since a terminal operating in a half-duplex mode cannot perform transmission and reception simultaneously in the same symbol.
  • DCI indicated SRS If the terminal is instructed to transmit SRS in a symbol configured to receive an SS/PBCH block 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), the terminal can transmit SRS without receiving SS/PBCH block in the overlapping symbol(s). That is, from the perspective of a specific terminal, the base station dynamically schedules SRS to overlap with a symbol specifically configured for the terminal to receive an SS/PBCH block, and it can be determined 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.
  • the terminal operation is as follows.
  • 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 and transmit the PUSCH for the PUSCH resources configured in the symbol overlapping with the SS/PBCH block and the position of the downlink-uplink switching gap symbol.
  • the terminal may receive the SS/PBCH block and not transmit the PUSCH. This is to prioritize reception of the SS/PBCH block since a terminal operating in a half-duplex mode cannot perform transmission and reception simultaneously in the same symbol.
  • DCI indicated PUCCH If a symbol configured to receive an SS/PBCH block is instructed to transmit a PUCCH via DCI format 1_0, 1_1 or 1_2, the terminal can 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 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 prioritize PUCCH transmission.
  • RRC configured SRS If the UE has resources configured via RRC to transmit SRS and symbols specifically configured to receive SS/PBCH blocks partially overlap in symbol units, the UE can receive SS/PBCH blocks in the overlapping symbol(s) and transmit SRS in the non-overlapping symbol(s). At this time, the UE can receive SS/PBCH blocks and transmit SRS by considering downlink-uplink switching gap symbols. That is, the UE can receive SS/PBCH blocks in the overlapping symbol(s) and transmit SRS in symbol(s) excluding the switching gap symbol among the non-overlapping symbol(s).
  • 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 SS/PBCH blocks and the resources configured to transmit SRS partially overlap in the time domain, the terminal can be guaranteed the configured downlink reception and uplink transmission to the maximum extent possible.
  • the terminal may receive the SS/PBCH block and not transmit the SRS. This is to prioritize reception of the SS/PBCH block since a terminal operating in a half-duplex mode cannot perform transmission and reception simultaneously in the same symbol.
  • DCI indicated SRS If the terminal is instructed to transmit SRS in a symbol configured to receive an SS/PBCH block 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), the terminal can transmit SRS without receiving SS/PBCH block in the overlapping symbol(s). That is, from the perspective of a specific terminal, the base station dynamically schedules SRS to overlap with a symbol specifically configured for the terminal to receive an SS/PBCH block, and it can be determined that the specific terminal does not intend to receive an SS/PBCH block in the slot and is instructed to prioritize SRS transmission.
  • a terminal receives SS/PBCH blocks (or SSBs) from a base station to perform initial cell access, radio resource management (RRM), radio link monitoring (RLM), beam management, and mobility management.
  • RRM radio resource management
  • RLM radio link monitoring
  • the terminal may acquire scheduling information of a PDSCH including SIB1 (hereinafter, PDSCH with SIB1; or simply referred to as PDSCH depending on the context).
  • a CORESET associated with a Type0-PDCCH CSS set is referred to as CORESET0 or CORESET#0.
  • the SSB is called NCD-SSB (non cell-defining SSB).
  • PCell always includes CD-SSB in the synchronization raster. That is, CD-SSB can be transmitted in any frequency domain in the synchronization raster in PCell.
  • a PDSCH including CORESET0 and (ii) SIB1 can be TDM or FDM with CD-SSB.
  • a terminal can determine one of multiplexing patterns 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 a frequency band of a 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.
  • 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.
  • 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 SSB, the number of CSS sets in a slot of a Type0-PDCCH CSS set, the monitoring period and offset per slot, and the first symbol index in the slot.
  • 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.
  • 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
  • Fig. 20(b) illustrates SSB & CORESET0 multiplexing pattern 1.
  • a terminal When a terminal is configured or instructed to operate in a subband for increasing uplink coverage, reducing uplink latency, or increasing uplink capacity, the terminal may be scheduled to transmit uplink signals/channels by maximizing uplink subband resources.
  • a symbol operating in a subband may include at least a cell-specific downlink/flexible symbol. Accordingly, a symbol configured to receive CORESET0 and a symbol configured or instructed to transmit an uplink signal/channel may overlap in the same resource. Since a terminal supporting half-duplex operation supports only one operation of downlink reception or uplink transmission in the same resource, a method is proposed to solve this problem.
  • the terminal can monitor PDCCH in a resource configured with CORESET0.
  • the terminal After completing RRC connection, the terminal is configured to periodically monitor PDCCH in a Type0-PDCCH CSS set associated with CORESET0 to receive SIB1 in order to receive other system information (OSI), validate public land mobile network selection (PLMN) identity, etc.
  • OSI system information
  • PLMN public land mobile network selection
  • Fig. 21 shows an example proposed in the present invention.
  • a terminal may be configured or scheduled to transmit an uplink signal/channel over 14 symbols in an uplink subband within a slot in which the terminal is configured or instructed to operate as a subband.
  • 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 PDCCH in CORESET0 to receive DCI in order to know the time/frequency domain location of the PDSCH.
  • a symbol instructed to receive PDSCH is included in a 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 DL-to-UL 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 operations according to uplink signals/channels in symbols excluding invalid symbols are as follows.
  • 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 positions of the SSB symbol, the symbol configured to receive CORESET0 and the DL-to-UL switching gap symbol.
  • the UE can transmit the PUSCH in 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 the PUSCH.
  • 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 DL-to-UL switching gap symbol among 14 symbols instructed or configured to transmit the PUSCH.
  • the UE can transmit the PUSCH in 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 the PUSCH.
  • the present method can guarantee the configured downlink reception and uplink transmission to the terminal to the maximum extent possible in symbol(s) excluding symbol(s) 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.
  • 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.
  • 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.
  • 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 configured downlink reception and uplink transmission to the terminal to the maximum extent possible in symbol(s) excluding symbol(s) 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.
  • SSB & CORESET0 Multiplexing Pattern 1 Unlike SSB & CORESET0 Multiplexing Patterns 2/3, in Multiplexing Pattern 1, since SSB/CORESET0/PDSCH are TDM, the UE cannot know the time/frequency domain location of 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 PDSCH.
  • 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 as a subband.
  • 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.
  • the UE can rate-match and transmit the PUSCH for the PUSCH resources instructed through the DCI format (e.g., DCI format 0_0, 0_1, or 0_2) or configured from a higher layer (e.g., RRC) 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.
  • the PUSCH can be transmitted in 10 symbols excluding 3 symbols configured to receive CORESET0 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 UE to the greatest extent possible in the symbol(s) excluding the symbol for downlink reception and the symbol(s) overlapping with the DL-to-UL switching gap symbol when the UE is configured or instructed to operate in a subband.
  • the UE can transmit SRS in the remaining symbols except for 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).
  • the SRS can be transmitted within 10 symbols excluding 3 symbols configured to receive CORESET0 and 1 symbol of the DL-to-UL switching gap among 14 symbols instructed or configured to transmit SRS.
  • the present method can guarantee the downlink reception and uplink transmission configured for the UE to the maximum extent possible in the symbol(s) excluding the symbol for downlink reception and the symbol(s) overlapping with the DL-to-UL switching gap symbol when the UE is configured or instructed to operate in a subband.
  • FIGS 23 and 24 show examples proposed in the present invention.
  • FIG. 23 illustrates a situation where 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 over 8 symbols in an uplink subband within a slot configured or instructed to operate in a subband.
  • 2 symbols out of the 8 symbols may be symbols instructed to the terminal to receive a PDSCH with SIB1.
  • 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.
  • 2 symbols out of 8 symbols may be symbols instructed to receive PDSCH with SIB1 for the terminal.
  • the terminal may transmit an uplink signal/channel in a symbol other than a symbol instructed to receive PDSCH with SIB1 and a gap symbol (e.g., a DL-to-UL switching gap symbol).
  • the terminal operation according to the uplink signal/channel may additionally consider whether the gap 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 may be determined according to T proc,2, which is a PUSCH preparation time according to the terminal processing capability.
  • T proc,2 is defined as follows:
  • the terminal operations according to the uplink signal/channel are as follows.
  • DCI format 0_0, 0_1, or 0_2 DCI format 0_0, 0_1, or 0_2
  • the UE may not expect to cancel the PUSCH transmission in the corresponding slot. That is, the UE may transmit the PUSCH in the corresponding slot and not receive the PDSCH with SIB1.
  • the UE since the timeline condition between the last symbol configured to receive a CORESET0 and the first symbol configured or instructed to transmit a PUSCH is not satisfied, the UE may transmit the PUSCH in the corresponding slot and not receive the PDSCH with SIB1.
  • the partialCancellation capability refers to the capability of the terminal to cancel uplink transmission in some symbol(s) of an uplink channel (PUSCH, PUCCH or PRACH) configured or instructed by the base station, and perform uplink transmission in the remaining symbol(s) when uplink transmission is impossible in those symbol(s).
  • PUSCH uplink channel
  • PUCCH Physical Uplink channel
  • the UE may transmit the PUSCH in a rate-matched manner.
  • the UE may transmit the PUSCH in 5 symbols excluding 2 symbols configured to receive PDSCH with SIB1 and 1 symbol of DL-to-UL switching gap among 8 symbols instructed to transmit the PUSCH.
  • the UE may transmit the PUSCH in symbols subsequent to reception of PDSCH with SIB1 and 1 symbol of DL-to-UL switching gap.
  • PUSCH can be transmitted in the following 4 symbols excluding 2 symbols configured to receive PDSCH with SIB1 and 1 symbol of DL-to-UL switching gap. That is, PUSCH transmission can be canceled (e.g., rate-matched) in the 2 symbols configured to receive PDSCH with SIB1 and 1 symbol of DL-to-UL switching gap.
  • PUSCH transmission can be canceled (e.g., rate-matched) in the 2 symbols configured to receive PDSCH with SIB1 and 1 symbol of DL-to-UL switching gap.
  • a timeline condition if a terminal is configured or instructed to operate in a subband, downlink reception and uplink transmission configured for the terminal can be guaranteed to the maximum extent possible in symbol(s) excluding symbol(s) overlapping with symbols for downlink reception and DL-to-UL switching gap symbols.
  • This example can be equally applied to the case where 1) the terminal indicates partialCancellation capability to the base station, and 2) the first symbol instructed to transmit PUSCH is the symbol after T proc,2 from the last symbol of the CORESET that detected the PDCCH including the DCI format indicating reception of PDSCH with SIB1.
  • the UE may not expect to cancel the PUSCH transmission in those symbols. That is, the UE may transmit the PUSCH in those symbols.
  • the UE can rate-match and transmit the PUSCH considering resources overlapping with the PDSCH with SIB1 resource for the symbols after T proc,2 . That is, the UE can cancel (e.g., rate-match) PUSCH transmission in the resources overlapping with the PDSCH with SIB1 resource for the symbols after T proc,2 .
  • the UE may not perform PDSCH reception in the symbol, and may perform PDSCH reception and PUSCH transmission in the symbols after T proc,2 .
  • the UE can transmit the PUSCH in 5 symbols excluding 2 symbols configured to receive PDSCH with SIB1 and 1 symbol of DL-to-UL switching gap among 8 symbols instructed to transmit the PUSCH.
  • the UE can transmit the PUSCH in 2 symbols before T proc,2 among 10 symbols instructed to transmit the PUSCH, and can transmit the PUSCH in 5 symbols excluding 2 symbols configured to receive PDSCH with SIB1 and 1 symbol of DL-to-UL switching gap among 8 symbols after T proc,2 .
  • the UE can transmit the PUSCH in the symbols following the reception of PDSCH with SIB1 and one symbol of DL-to-UL switching gap.
  • the UE can transmit the PUSCH in the four symbols following the excluding two symbols configured to receive PDSCH with SIB1 and one symbol of DL-to-UL switching gap among the eight symbols instructed to transmit the PUSCH.
  • the UE can transmit the PUSCH in the four symbols following the excluding two symbols configured to receive PDSCH with SIB1 and one symbol of DL-to-UL switching gap among the ten symbols instructed to transmit the PUSCH.
  • the UE When the symbol instructed to receive PDSCH with SIB1 by the UE and the PUSCH resource configured from the upper layer overlap at the position of the DL-to-UL switching gap symbol, the UE operates as follows.
  • the UE may not determine the slot as a valid opportunity for PUSCH transmission. That is, the UE may receive the PDSCH with SIB1 in the slot and not transmit the PUSCH.
  • the UE may not determine the slot as a valid opportunity for PUSCH transmission and may receive the PDSCH with SIB1.
  • the UE may rate-match and transmit the PUSCH. Accordingly, the UE may cancel PUSCH transmission in some symbols. Referring to FIG. 23, the UE may transmit the PUSCH in 5 symbols excluding 2 symbols configured to receive PDSCH with SIB1 and 1 symbol of DL-to-UL switching gap among 8 symbols instructed to transmit the PUSCH.
  • the UE may transmit the PUSCH in symbols subsequent to reception of the PDSCH with SIB1 and 1 symbol of DL-to-UL switching gap.
  • PUSCH can be transmitted in 4 symbols after excluding 2 symbols configured to receive PDSCH and 1 symbol of DL-to-UL switching gap.
  • a timeline condition if a terminal is configured or instructed to operate in a subband, downlink reception and uplink transmission configured for the terminal can be guaranteed to the maximum extent in the symbol(s) excluding the symbol for downlink reception and the symbol(s) overlapping with the DL-to-UL switching gap symbol.
  • This example can be equally applied to the case where 1) the terminal indicates partialCancellation capability to the base station, and 2) the first symbol instructed to transmit PUSCH is a symbol after T proc,2 from the last symbol of the CORESET that detected the PDCCH including the DCI format instructing reception of PDSCH with SIB1.
  • the UE may not expect to cancel the PUSCH transmission in the corresponding symbol. That is, the UE may transmit the PUSCH in the corresponding symbols.
  • the UE may transmit the PUSCH in 10 symbols, excluding 2 symbols configured to receive PDSCH with SIB1 among 8 symbols instructed to transmit the PUSCH, symbols for downlink reception, and 1 symbol of DL-to-UL switching gap.
  • the UE can transmit the PUSCH in five symbols excluding two symbols configured to receive PDSCH with SIB1 and symbols for downlink reception and one symbol for DL-to-UL switching gap among eight symbols instructed to transmit the PUSCH.
  • the UE can transmit the PUSCH in two symbols before T proc,2 among ten symbols instructed to transmit the PUSCH, and can transmit the PUSCH in five symbols excluding two symbols configured to receive PDSCH with SIB1 and one symbol for DL-to-UL switching gap among eight symbols after T proc, 2.
  • the UE 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.
  • the UE 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.
  • the UE 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.
  • the UE 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.
  • the UE can transmit SRS in the remaining symbols except for the symbols instructed to receive PDSCH with SIB1 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).
  • the UE can transmit SRS in the five symbols excluding the two symbols configured to receive PDSCH with SIB1 and the one DL-to-UL switching gap symbol among the eight symbols instructed or configured to transmit SRS.
  • the present method can guarantee the downlink reception and uplink transmission configured for the UE to the maximum extent possible in the symbol(s) excluding the symbols for downlink reception and the symbol(s) overlapping with the DL-to-UL switching gap symbols when the UE is configured or instructed to operate in a subband.
  • the UE may not expect that the symbol configured or instructed to transmit the uplink signal/channel overlaps both the symbol configured for CORESET0 and the symbol 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 symbol configured or instructed for reception of CORESET0 and PDSCH with SIB1, additional DL-to-UL switching gap symbols (switching gap symbols between reception of CORESET0 and transmission of UL signal/channel, switching gap symbols between reception of PDSCH and transmission of UL signal/channel) must be considered, 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 symbol configured or instructed for reception of CORESET0 and PDSCH with SIB1.
  • the terminal can receive a PDCCH transmitted from a base station.
  • the terminal can set information such as CORESET and search space to receive the PDCCH from the base station.
  • CORESET may include information on a frequency domain in which PDCCH should be received.
  • the base station may provide information on CORESET to the terminal, and the information on CORESET may include an index of PRB (Physical Resource Block) sets in which the terminal should receive PDCCH and the number of consecutive symbols.
  • PRB Physical Resource Block
  • the number of consecutive symbols may be one of 1, 2, and 3.
  • the base station can transmit information about the CORESET and information about the search space to the terminal.
  • the information about the CORESET is described below.
  • the resources that constitute the CORESET may have the same meaning as the resources included in the CORESET.
  • the first information about the CORESET may be an index of PRB sets constituting the CORESET in which the PDCCH is transmitted.
  • the PRB set may be 6 consecutive PRBs.
  • the indexes of the PRB sets may be set in a bitmap form. 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.
  • the first information for the CORESET may set the indices of the 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.
  • the base station may set the indices of the P PRBs as PRB#0, PRB#1, ...., PRB#(P-1), and P may be a multiple of 6. In this case, the PRBs may or may not be consecutive in the frequency domain.
  • the second information for the 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 be configured with resources through which the PDCCHs are transmitted from the base station based on the first information and the second information.
  • Resources corresponding to P PRBs and S symbols constituting CORESET can be configured as REG (resource element group).
  • 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 configure one REG bundle.
  • the method of bundling 2, 3, or 6 REGs can be determined according to the length (number of symbols) of CORESET and the mapping method (interleaved mapping/non-interleaved mapping).
  • 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 each 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.
  • the 3 REGs of symbol A and the 3 REGs of symbol B can be located on 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, thereby bundling 6 REGs in total (2 REGs per each symbol * 3 symbols).
  • 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 C symbol can be continuous in frequency domain
  • the 2 REGs of D symbol can be continuous in frequency domain
  • the 2 REGs of E symbol can be continuous in frequency domain.
  • the 2 REGs of C symbol, 2 REGs of D symbol, and 2 REGs of E symbol can be located on the same frequency domain.
  • 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.
  • CCE can be generated by bundling REG bundles generated by the above-described method. At this time, CCE can be composed of 6 REGs. Since REG bundle is composed of 2, 3 or 6 REGs, CCE can be composed of 3, 2 or 1 REG bundle. In case of non-interleaved mapping, REG bundle is composed of 6 REGs regardless of the number of symbols of CORESET. At this time, CCE can be composed of 1 REG bundle.
  • Information about the search space may include time information at which a set of PRBs indicated by CORESET should be received.
  • 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 information about a periodicity and an offset.
  • the period and the offset may be set in units of a slot, a sub-slot, a symbol, a symbol set, or a slot set.
  • the information about the search space may include a CCE aggregation level (AL) received by the terminal, the number of PDCCHs monitored by the terminal for each CCE aggregation level, a search space type, a DCI format monitored by the terminal, and RNTI information.
  • A CCE aggregation level
  • 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.
  • the search space can be divided into two types. Specifically, the types of the search space 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 UE may monitor candidates for PDCCH (e.g., a PDCCH conveying a DCI having a CRC scrambled with at least one RNTI among the SI-RNTI, the RA-RNTI, the MsgB-RNTI, the P-RNTI, the TC-RNTI, the INT-RNTI, the SFI-RNTI, the TPC-PUSCH-RNTI, the TPC-PUCCH-RNTI, the TPC-SRS-RNTI, the CI-RNTI, the C-RNTI, the MCS-C-RNTI, the CS-RNTI(s), or the PS-RNTI) broadcast to all UEs in a cell or some UEs in a cell and receive the PDCCH in the common search space.
  • PDCCH e.g., a PDCCH conveying a DCI having a CRC scrambled with at least one RNTI among the SI-RNTI, the RA-RNTI, the MsgB-RNTI,
  • the terminal-specific search space may be a search space in which a specific terminal monitors a PDCCH.
  • the specific terminal may monitor candidates for PDCCHs (e.g., a PDCCH conveying a DCI having a CRC scrambled with at least one RNTI among the C-RNTI, the MCS-C-RNTI, the SP-CSI-RNTI, the CS-RNTI(s), the SL-RNTI, the SL-CS-RNTI, or the SL-L-CS-RNTI) transmitted to the specific terminal in the terminal-specific search space and receive the PDCCH.
  • 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.
  • the CCEs composing the PDCCH candidate m s,nCI of the slot n s,f ⁇ included in the search space s of the CORESET p can be determined by the hashing function of mathematical expression 1.
  • the aggregation level of the PDCCH candidate can be L.
  • 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 equal to n RNTI and is 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 can be the number of CCEs constituting the CORESET.
  • M (L) s,max can be the number of repetitive PDCCH candidates whose aggregation level is L monitored by the UE.
  • n CI can be a value indicated by a carrier indicator field.
  • FIGS 25 and 26 illustrate the problems to be solved in this specification.
  • 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.
  • 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.
  • the terminal may be configured to monitor a PDCCH in CORESET#1 of search space#1 of slot n to slot n+3 from the base station in the same manner as in FIG. 25.
  • the terminal supporting the SBFD operation may be configured with a plurality of subbands (two downlink subbands and one uplink subband) in the frequency domain of slot n+2 to slot n+3.
  • CORESET#1 of slot n+2 to slot n+3 may overlap with some uplink subbands in the frequency domain. Since the terminal supporting the SBFD operation cannot perform downlink reception in the uplink subband, it cannot perform PDCCH reception in slot n+2 to slot n+3.
  • examples for solving this problem are disclosed.
  • a time domain section in which a terminal supporting SBFD operation receives 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 subband is not received in the frequency domain is called a non-SBFD section (slot n to slot n+1 in FIG. 26).
  • a terminal may be configured to associate two CORESETs in one search space.
  • a terminal may be configured to associate one CORESET in one 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.
  • 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 monitored in the SBFD section, and that CORESET#2 is the CORESET monitored in the non-SBFD section.
  • CORESET#0 can be a CORESET configured through PBCH for initial cell access of the terminal. Therefore, the above example is a method that requires additional capability of the terminal, since at least two CORESETs must be set for each BWP in the cell, excluding CORESET#0.
  • the terminal can be configured with separate configuration information applied to the SBFD section and the non-SBFD section for one CORESET.
  • the separate configuration information can be configured through a separate RRC signal.
  • the terminal can be configured with separate frequencyDomainResources for the SBFD section and the non-SBFD section.
  • the 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 CORESET is not allocated to the corresponding PRB set, and if the bit value is '1', it can be configured that the CORESET is allocated to the corresponding PRB set.
  • the terminal can be configured with separate CCE aggregation levels (ALs) for the SBFD section and the non-SBFD section, and the number of PDCCHs that the terminal monitors for each CCE aggregation level.
  • As CCE aggregation levels
  • separate configuration information applied to the SBFD interval and the non-SBFD interval for one CORESET may be configuration information for the CORESET or configuration information for the search space.
  • frequencyDomainResources is 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 configuration information for the search space.
  • CORESET is configured in the interleaved mapping manner in the above example, some REG bundles within the CCE may be included in the uplink subband or guard band.
  • 3 REG bundles configure one CCE.
  • 1 REG bundle may be included in the uplink and guard band, and in CCE#0 to CCE#3, PDCCH may be received in 2 REG bundles, respectively. This may cause PDCCH reception performance degradation.
  • the terminal can determine resource mapping for separate PDCCH reception for SBFD intervals and non-SBFD intervals.
  • the 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 intervals and CCE-to-REG mapping in non-SBFD intervals).
  • 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.
  • the terminal may not increase the (REG) index for symbols and PRBs included in the uplink subband or guard band. That is, since the symbols and PRBs included in the uplink subband or guard band cannot receive PDCCH, the symbols and PRBs may be excluded from the REG and not indexed.
  • 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.
  • the terminal supporting the SBFD operation may not index the symbols and PRBs by excluding them from the REG, and may sequentially increase the (REG) index for only the remaining symbols and PRBs in a time-first manner.
  • REGs constituting one CORESET are indexed as 0 for the first OFDM symbol and the PRB with the lowest index in the CORESET, and the index increases sequentially in a time-first manner. At this time, REG indexing is performed for all resources in the CORESET.
  • the UE can determine resource mapping for separate PDCCH reception for SBFD intervals and non-SBFD intervals, and also set separate configuration information for SBFD intervals and non-SBFD intervals.
  • frequencyDomainResources can be set as separate configuration information for CORESET
  • the CCE aggregation level (AL) and the number of PDCCHs that the UE monitors for each CCE aggregation level can be set as configuration information for the search space.
  • the terminal can determine two CCE-to-REG mappings for one CORESET. Accordingly, it can have separate CCE aggregation levels, CCE counts, and PDCCH candidate counts to monitor per CCE aggregation level in SBFD and non-SBFD sections.
  • m s,nCI,j can be a PDCCH candidate in the SBFD interval or a PDCCH candidate in the non-SBFD interval depending on the value of j.
  • m s,nCI,0 can be a PDCCH candidate in the SBFD interval
  • m s,nCI,1 can be a PDCCH candidate in the non-SBFD interval
  • m s,nCI,1 can be a PDCCH candidate in the SBFD interval
  • m s,nCI,0 can be a PDCCH candidate in the non-SBFD interval.
  • L j can be a CCE aggregation level in an SBFD section or a CCE aggregation level in a non-SBFD section, depending on the value of j.
  • L 0 can be a CCE aggregation level in an SBFD section
  • L 1 can be a CCE aggregation level in a non-SBFD section.
  • L 1 can be a CCE aggregation level in an SBFD section
  • L 0 can be a CCE aggregation level in a non-SBFD section.
  • Mathematical expression 2 can determine the hashing function.
  • 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 equal to n RNTI and is 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 can be a value indicated by the carrier indicator field.
  • N CCE,p,j can be the number of CCEs constituting the CORESET in the SBFD interval or the number of CCEs constituting the CORESET in the non-SBFD interval, depending on the value of j.
  • N CCE,p,0 can be the number of CCEs constituting the CORESET in the SBFD interval
  • N CCE,p,1 can be the number of CCEs constituting the CORESET in the non-SBFD interval.
  • N CCE,p,1 can be the number of CCEs constituting the CORESET in the SBFD interval
  • N CCE,p,0 can be the number of CCEs constituting the CORESET in the non-SBFD interval.
  • the terminal may be the number of repetitive PDCCH candidates whose aggregation level is L j monitored by the terminal.
  • j it can be the number of repeating PDCCH candidates with an aggregation level of L 0 in the SBFD section or the number of repeating PDCCH candidates with an aggregation level of L 1 in the non-SBFD section.
  • j it can be the number of repetitive PDCCH candidates with an aggregation level of L 1 in the SBFD section or the number of repetitive PDCCH candidates with an aggregation level of L 0 in the non-SBFD section.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne un système de communication sans fil et, plus particulièrement, un procédé et un dispositif sans fil associé, le procédé comprenant les étapes consistant à : recevoir des informations de configuration concernant un CORESET#0 par l'intermédiaire d'un SS/PBCH ; et recevoir des DCI comprenant des informations d'attribution de ressources concernant un PDSCH dans le CORESET#0, si (i) un PUSCH est planifié dans une sous-bande de liaison montante dans une BWP, et (ii) que le PUSCH chevauche le PDSCH dans un domaine temporel, la transmission du PUSCH est soit effectuée soit annulée sur la base d'une condition, la condition comprenant une condition de chronologie relative à un intervalle entre le CORESET#0 et le PUSCH.
PCT/KR2024/000338 2023-05-14 2024-01-08 Procédé et dispositif de transmission de signal dans un système de communication sans fil Pending WO2024237421A1 (fr)

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
KR20230062106 2023-05-14
KR10-2023-0062106 2023-05-14
KR20230083617 2023-06-28
KR10-2023-0083617 2023-06-28
KR10-2023-0097338 2023-07-26
KR20230097338 2023-07-26

Publications (1)

Publication Number Publication Date
WO2024237421A1 true WO2024237421A1 (fr) 2024-11-21

Family

ID=93519178

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2024/000338 Pending WO2024237421A1 (fr) 2023-05-14 2024-01-08 Procédé et dispositif de transmission de signal dans un système de communication sans fil

Country Status (1)

Country Link
WO (1) WO2024237421A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20190017675A (ko) * 2017-08-11 2019-02-20 한국전자통신연구원 하향링크 제어 채널의 송수신 방법 및 이를 이용하는 장치
KR20190129721A (ko) * 2018-05-11 2019-11-20 한국전자통신연구원 고신뢰 및 저지연 통신을 위한 신호의 송수신 방법
KR20200034506A (ko) * 2018-09-21 2020-03-31 삼성전자주식회사 무선 통신 시스템에서 저지연 및 고신뢰도 데이터 전송을 위한 방법 및 장치
KR20200060255A (ko) * 2018-11-21 2020-05-29 한국전자통신연구원 통신 시스템에서 데이터 채널의 송수신 방법 및 장치
WO2022152922A1 (fr) * 2021-01-18 2022-07-21 Telefonaktiebolaget Lm Ericsson (Publ) Gestion de collisions de liaison descendante et de liaison montante dans un équipement utilisateur en duplex par répartition en fréquence en semi-duplex

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20190017675A (ko) * 2017-08-11 2019-02-20 한국전자통신연구원 하향링크 제어 채널의 송수신 방법 및 이를 이용하는 장치
KR20190129721A (ko) * 2018-05-11 2019-11-20 한국전자통신연구원 고신뢰 및 저지연 통신을 위한 신호의 송수신 방법
KR20200034506A (ko) * 2018-09-21 2020-03-31 삼성전자주식회사 무선 통신 시스템에서 저지연 및 고신뢰도 데이터 전송을 위한 방법 및 장치
KR20200060255A (ko) * 2018-11-21 2020-05-29 한국전자통신연구원 통신 시스템에서 데이터 채널의 송수신 방법 및 장치
WO2022152922A1 (fr) * 2021-01-18 2022-07-21 Telefonaktiebolaget Lm Ericsson (Publ) Gestion de collisions de liaison descendante et de liaison montante dans un équipement utilisateur en duplex par répartition en fréquence en semi-duplex

Similar Documents

Publication Publication Date Title
WO2020222575A1 (fr) Procédé et appareil pour la transmission et la réception de rétroaction de liaison latérale dans un système de communication sans fil
WO2020145704A1 (fr) Procédé et dispositif d'émission de canal de commande de liaison montante dans un système de communication sans fil
WO2021020955A1 (fr) Procédé, dispositif et système d'émission ou de réception d'un canal partagé de liaison montante physique (pusch) dans un système de communication sans fil
WO2020222625A1 (fr) Procédé de transmission et de réception de canal partagé dans un système de communication sans fil, et dispositif prenant en charge ce procédé
WO2019050381A1 (fr) Procédé, dispositif et système de transmission montante et de réception descendante dans un système de communication sans fil
WO2022031062A1 (fr) Procédé, appareil et système d'accès initial à une cellule dans un système de communication sans fil
WO2017122959A1 (fr) Procédé et équipement d'utilisateur permettant de recevoir un canal de liaison descendante, et procédé et station de base permettant de transmettre un canal de liaison descendante
WO2020222624A1 (fr) Procédé, dispositif et système de réception de données de liaison descendante et de transmission harq-ack dans un système de communication sans fil
WO2019139444A1 (fr) Procédé, dispositif et système d'attribution de ressources pour système de communication sans fil
WO2022080840A1 (fr) Procédé, dispositif et système de transmission d'un canal physique de commande de liaison montante dans un système de communication sans fil
WO2020032603A1 (fr) Appareil et procédé d'attribution de ressources dans un système de communication sans fil
WO2019050371A1 (fr) Procédé de transmission et procédé de réception de données pour système de communication sans fil et appareil utilisant les procédés
WO2021034063A1 (fr) Procédé, dispositif et système de transmission ou de réception d'un canal physique partagé de liaison montante (pusch) dans un système de communication sans fil
WO2018143756A1 (fr) Procédé, dispositif et système pour émettre et recevoir un signal de référence et un canal de données dans un système de communication sans fil
WO2022015125A1 (fr) Procédé de transmission de canal de commande de liaison descendante physique et dispositif pour ledit procédé dans un système de communication sans fil
WO2016018125A1 (fr) Procédé et dispositif pour configurer une période d'opportunité d'émission dans un système d'accès sans fil prenant en charge une bande non autorisée
WO2020204682A1 (fr) Procédé d'attribution de ressources permettant l'exécution d'une transmission dans une bande sans licence, et dispositif utilisant ledit procédé
WO2022075828A1 (fr) Procédé de transmission de canal de liaison montante dans un système de communication sans fil et appareil associé
WO2016099196A1 (fr) Procédé destiné à l'attribution de ressources de transmission dans un système de communication sans fil prenant en charge une communication de dispositif à dispositif (d2d)
WO2022025740A1 (fr) Procédé de transmission de canal de liaison montante dans un système de communication sans fil et dispositif associé
WO2022065963A1 (fr) Procédé, appareil, et système de génération d'un livre de codes harq-ack dans un système de communication sans fil
WO2020145772A1 (fr) Procédé et équipement utilisateur pour effectuer une transmission de liaison montante, et procédé pour effectuer une réception de liaison montante
WO2019194545A1 (fr) Procédé permettant d'émettre et de recevoir un préambule d'accès aléatoire dans un système de communication sans fil et appareil associé
WO2022031102A1 (fr) Procédé de transmission de canal de liaison montante, dispositif utilisateur, dispositif de traitement, support de stockage, programme informatique, procédé de réception de canal de liaison montante, et station de base
WO2023219398A1 (fr) Procédé de configuration de sous-bande dans un système de communication sans fil et dispositif associé

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24807305

Country of ref document: EP

Kind code of ref document: A1