Method and apparatus for transmitting and receiving pucch in wireless communication system

Abstract

A method performed by a terminal according to an embodiment of the present disclosure comprises the steps of: receiving a PDCCH based on CORESET; and transmitting the PUCCH on the basis of the PUCCH resource. The DCI associated with the PDCCH includes a PRI field. The PUCCH resource is determined based on i) a value of a PRI field, ii) a number of CCEs within the CORESET, and iii) an index of a first CCE for receiving the PDCCH among the CCEs, and the CCEs within the CORESET are obtained before puncturing related to the CORESET.

Description

TECHNICAL FIELD

[0001] The disclosure relates to a method and device for transmitting and receiving a PUCCH in a wireless communication system. BACKGROUND

[0002] A mobile communication system has evolved to provide a voice service while guaranteeing user mobility. However, in the mobile communication system, not only the voice service but also a data service has been expanded. Currently, due to an explosive increase in traffic, resources are in shortage, and users need a faster service. Therefore, a more advanced mobile communication system is required.

[0003] Requirements for a next-generation mobile communication system should be able to support accommodation of explosive data traffic, a significant increase in a per-user data rate, accommodation of a large increase in the number of connected devices, an extremely low end-to-end latency, and high energy efficiency. To this end, various techniques, including dual connectivity, massive multiple input multiple output (MIMO), in-band full duplex, non-orthogonal multiple access (NOMA), ultra-wideband support, device networking, etc., are being researched.

[0004] In order to effectively support various use cases in 5G in terms of cost / complexity, the maximum bandwidth of a newly introduced user equipment (UE) type can be reduced. For example, the maximum bandwidth can be reduced to 3 MHz.

[0005] As described above, since a channel bandwidth of less than 5 MHz is supported, a PDCCH can be received after RBs of a CORESET are punctured. After a corresponding PDCCH (DCI) is received, a PUCCH can be transmitted for HARQ-ACK feedback. SUMMARY

[0006] TECHNICAL PROBLEM

[0007] A factor for determining a PUCCH resource for PUCCH transmission is determined, and a PUCCH resource is determined based on a CCE in a CORESET and As described above, when a PUCCH is transmitted after a PDCCH is received based on a reduced channel bandwidth, it can be ambiguous how to determine a PUCCH resource. That is, it can be ambiguous whether the above-described puncturing should be considered in determining the number of CCEs in a CORESET and a first CCE index for receiving a PDCCH

[0008] ​Specifically, when a CORESET of an existing defined size (e.g., 24 RBs) is reused for PDCCH transmission and reception, the following problem can occur. A PUCCH resource determined by a base station (i.e., a PUCCH resource in which the base station expects to receive a PUCCH from a terminal) can be different from a PUCCH resource determined by a terminal. As an example, the base station determines and while the terminal can determine and without puncturing. In this case, the PUCCH resource determined by the terminal and the PUCCH resource determined by the base station can be different.

[0009] An object of the disclosure is to provide a method of solving the above problem.

[0010] Technical objects to be achieved by the disclosure are not limited to those described only by examples above, and other technical objects not mentioned can be clearly understood by those skilled in the art from the following description.

[0011] Technical solution

[0012] A method performed by a user equipment (UE) in a wireless communication system according to an embodiment of the disclosure includes receiving a physical downlink control channel (PDCCH) based on a control resource set (CORESET), and transmitting a physical uplink control channel (PUCCH) based on a PUCCH resource.

[0013] The CORESET is obtained based on puncturing a highest-numbered resource block among resource blocks according to a frequency domain size of the CORESET.

[0014] Downlink control information (DCI) related to the PDCCH includes a PUCCH resource indicator (PRI) field.

[0015] The PUCCH resource is determined based on i) a value of the PRI field, ii) a number of control channel elements (CCEs) in the CORESET, and iii) an index of a first CCE among the CCEs used for reception of the PDCCH.

[0016] The CCEs in the CORESET are obtained before puncturing.

[0017] The PUCCH resource can be based on i) a common configuration or ii) a dedicated configuration.

[0018] The method can further include receiving the common configuration. The common configuration can include information for an index related to one of the PUCCH resource sets.

[0019] A PUCCH resource can be one of 16 PUCCH resources in an indexed PUCCH resource set.

[0020] The method may also include receiving dedicated configuration. Dedicated configuration may include information for one or more PUCCH resource sets.

[0021] The PUCCH resource set within one or more PUCCH resource sets can be determined based on the number of bits associated with uplink control information (UCI).

[0022] A PUCCH resource can be one of the PUCCH resources within a defined set of PUCCH resources.

[0023] The number of PUCCH resources can be greater than 8.

[0024] The channel bandwidth associated with CORESET can be less than 5 MHz.

[0025] A CORESET can be either i) a first CORESET or ii) a second CORESET configured separately from the first CORESET. The first CORESET can be configured based on the Master Information Block (MIB).

[0026] A user equipment (UE) operating in wireless communication according to another embodiment of the present disclosure includes: one or more transceivers; one or more processors; and one or more memories connected to one or more processors and configured to store instructions.

[0027] The instructions are based on all steps of the one or more processors configured to perform any one of the methods, and are executed by the one or more processors.

[0028] The device according to another embodiment of the present disclosure includes one or more memories and one or more processors operatively connected to one or more memories.

[0029] The one or more memories are configured to store instructions based on instructions executed by the one or more processors, and the instructions are configured to allow the one or more processors to perform all steps of any of the methods.

[0030] One or more non-transitory computer-readable media storage instructions according to another embodiment of this disclosure. The instructions, executable by one or more processors, are configured to allow one or more processors to perform all steps of any of the methods.

[0031] A method performed by a base station in a wireless communication system according to another embodiment of the present disclosure includes: transmitting a physical downlink control channel (PDCCH) based on a control resource set (CORESET); and receiving a physical uplink control channel (PUCCH) based on PUCCH resources.

[0032] The CORESET is obtained by punching holes in the resource block with the highest number based on the frequency domain size of the CORESET.

[0033] Downlink control information (DCI) associated with PDCCH includes the PUCCH resource indicator (PRI) field.

[0034] PUCCH resources are determined based on i) the value of the PRI field, ii) the number of Control Channel Elements (CCEs) in the CORESET, and iii) the index of the first CCE used for receiving PDCCH.

[0035] CCE in CORESET is obtained before drilling.

[0036] A base station operating in wireless communication according to another embodiment of the present disclosure includes: one or more transceivers; one or more processors; and one or more memories connected to one or more processors and configured to store instructions.

[0037] The instructions are configured to allow the one or more processors to perform all steps of any of the methods, based on execution by the one or more processors.

[0038] Beneficial effects

[0039] According to embodiments of this disclosure, a CCE related to the determination of PUCCH resources is obtained before puncturing. When a PDCCH is received in a CORESET with puncturing applied, factors related to the determination of PUCCH resources are defined based on the CCE prior to puncturing. Therefore, the ambiguity of terminal / base station operation related to the determination of PUCCH resources in the signaling process performed based on a CORESET with puncturing applied can be resolved.

[0040] Furthermore, it can improve the reliability of HARQ-ACK feedback performed in narrowband. Additionally, it can address potential issues when supporting narrowband terminals / spectrum scenarios, thereby helping to expand the application use cases of NR systems.

[0041] The effects that can be achieved using this disclosure are not limited to those described above by way of example only. Other effects and advantages of this disclosure will become clearer to those skilled in the art from the following description. Attached Figure Description

[0042] Figure 1 An example of a frame structure in NR system is shown.

[0043] Figure 2 An example of a resource grid in NR is shown.

[0044] Figure 3 Physical channels and general signal transmission used in 3GPP system are shown.

[0045] Figure 4 is a diagram showing an SSB structure to which the method proposed in the disclosure is applicable.

[0046] Figure 5 SSB transmission to which the method proposed in the disclosure is applicable is shown.

[0047] Figure 6 An SSB time-frequency structure according to an embodiment of the disclosure is shown.

[0048] Figure 7 is a flowchart showing a method performed by a user equipment according to an embodiment of the disclosure.

[0049] Figure 8 is a flowchart showing a method performed by a base station according to another embodiment of the disclosure.

[0050] Figure 9 A configuration of a first device and a second device according to an embodiment of the disclosure is shown. DETAILED DESCRIPTION

[0051] Hereinafter, downlink (DL) means communication from a base station to a terminal, and uplink (UL) means communication from a terminal to a base station. In the downlink, a transmitter can be a part of a base station, and a receiver can be a part of a terminal. In the uplink, a transmitter can be a part of a terminal, and a receiver can be a part of a base station. The base station can be denoted as a first communication device, and the terminal can be denoted as a second communication device. The base station (BS) can be replaced with a term including a fixed station, a Node-B, an evolved Node-B (eNB), a next-generation Node-B (gNB), a base transceiver system (BTS), an access point (AP), a network (5G network), an AI system, a roadside unit (RSU), a vehicle, a robot, an unmanned aerial vehicle (UAV), an augmented reality (AR) device, a virtual reality (VR) device, etc. Also, the terminal can be fixed or mobile, and can be replaced with a term including a user equipment (UE), a mobile station (MS), a user terminal (UT), a mobile subscriber station (MSS), a subscriber station (SS), an advanced mobile station (AMS), a wireless terminal (WT), a machine-type communication (MTC) device, a machine-to-machine (M2M) device, and a device-to-device (D2D) device, a vehicle, a robot, an AI module, an unmanned aerial vehicle (UAV), an augmented reality (AR) device, a virtual reality (VR) device, etc.

[0052] The following techniques can be used for various radio access systems including CDMA, FDMA, TDMA, OFDMA, SC-FDMA, etc. CDMA can be implemented as a radio technology such as universal terrestrial radio access (UTRA) or CDMA2000. TDMA can be implemented as a radio technology such as global system for mobile communications (GSM) / general packet radio service (GPRS) / enhanced data rates for GSM evolution (EDGE). OFDMA can be implemented as a radio technology such as institute of electrical and electronics engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, evolved UTRA (E-UTRA), etc. UTRA is a part of universal mobile telecommunications system (UMTS). 3rd generation partnership project (3GPP) long term evolution (LTE) is a part of evolved UMTS (E-UMTS) using E-UTRA, and LTE-Advanced (A) / LTE-A pro is an evolved version of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an evolved version of 3GPP LTE / LTE-A / LTE-A pro.

[0053] For clarity of description, the technical spirit of the disclosure is described based on a 3GPP communication system (e.g., LTE-A or NR), but the technical spirit of the disclosure is not limited thereto. LTE means a technology after Release 8 of 3GPP TS 36.xxx. In particular, LTE technology after Release 10 of 3GPP TS 36.xxx is referred to as LTE-A, and LTE technology after Release 13 of 3GPP TS 36.xxx is referred to as LTE-A pro. 3GPP NR means a technology after Release 15 of TS 38.xxx. LTE / NR can be referred to as a 3GPP system. "xxx" means a detailed standard document number. LTE / NR can be collectively referred to as a 3GPP system.

[0054] The background art, terms, omissions, etc. used in describing the disclosure can refer to the contents disclosed in the standard documents published before the disclosure. For example, the following documents can be referred to.

[0055] 3GPP NR

[0056] - 3GPP TS 38.211: Physical channels and modulation

[0057] - 3GPP TS 38.212: Multiplexing and channel coding

[0058] - 3GPP TS 38.213: Physical layer procedures for control

[0059] - 3GPP TS 38.214: Physical layer procedures for data

[0060] - 3GPP TS 38.215: Physical layer measurements

[0061] - 3GPP TS 38.300: NR and NG-RAN Overall description

[0062] - 3GPP TS 38.304: User Equipment (UE) procedures in idle mode and in RRC inactive state

[0063] - 3GPP TS 38.321: Medium Access Control (MAC) protocol

[0064] - 3GPP TS 38.322: Radio Link Control (RLC) protocol

[0065] - 3GPP TS 38.323: Packet Data Convergence Protocol (PDCP)

[0066] - 3GPP TS 38.331: Radio Resource Control (RRC) protocol

[0067] - 3GPP TS 37.324: Service Data Adaptation Protocol (SDAP)

[0068] - 3GPP TS 37.340: Multi-connectivity; General description

[0069] - 3GPP TS 23.287: Application layer support for V2X services; Functional architecture and information flows

[0070] - 3GPP TS 23.501: System Architecture for the 5G System

[0071] - 3GPP TS 23.502: Procedures for the 5G System

[0072] - 3GPP TS 23.503: Policy and Charging Control Framework for the 5G System; Stage 2

[0073] - 3GPP TS 24.501: Non-Access Stratum (NAS) protocol for the 5G System (5GS); Stage 3

[0074] - 3GPP TS 24.502: Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks

[0075] - 3GPP TS 24.526: User Equipment (UE) policies for the 5G System (5GS); Stage 3

[0076] As more communication devices need more communication capacity, improved mobile broadband communication technology compared to existing radio access technologies (RATs) is required. In addition, massive machine type communications (MTC), which provides various services anytime anywhere by connecting numerous devices and objects, is one of the major issues considered in the next-generation communication. In addition, communication system design considering reliability and latency sensitive services / UEs is also under discussion. The introduction of next-generation radio access technologies considering enhanced mobile broadband communication (eMBB), massive MTC (mMTC), and ultra-reliable and low-latency communication (URLLC) is discussed, and in this disclosure, for convenience, this technology is referred to as new RAT (NR). NR is a representation of an example of a 5G radio access technology (RAT).

[0077] In a new RAT system including NR, an OFDM transmission scheme or a similar transmission scheme is adopted. The new RAT system can follow different OFDM parameters from LTE. Alternatively, the new RAT system can follow the numerology of legacy LTE / LTE-A as it is, or have a larger system bandwidth (e.g., 100 MHz). Alternatively, one cell can support multiple numerologies. In other words, user equipments (UEs) operating with different numerologies can coexist in one cell.

[0078] A numerology corresponds to one subcarrier spacing in the frequency domain. Different numerologies can be defined by scaling a reference subcarrier spacing by an integer N.

[0079] New RAT (NR) numerology and frame structure

[0080] In the NR system, multiple numerologies can be supported. These numerologies can be defined by a subcarrier spacing and a cyclic prefix (CP) overhead. The spacing between multiple subcarriers can be derived by scaling a basic subcarrier spacing by an integer N (or µ). Also, while it is assumed that a very low subcarrier spacing will not be used at a very high subcarrier frequency, the numerology to be used can be selected regardless of a frequency band.

[0081] Also, in the NR system, various frame structures according to multiple numerologies can be supported.

[0082] Hereinafter, orthogonal frequency division multiplexing (OFDM) numerologies and frame structures that can be considered in the NR system will be described.

[0083] Multiple OFDM numerologies supported in the NR system can be defined as in Table 1. µ and a cyclic prefix for a bandwidth part are obtained from an RRC parameter provided by a base station.

[0084] [Table 1]

[0085]

[0086] NR supports multiple numerologies (or subcarrier spacings (SCSs)) to support various 5G services. For example, when the SCS is 15 kHz, a wide area is supported in a legacy cellular band; and when the SCS is 30 kHz / 60 kHz, dense cities, lower latency, and wider carrier bandwidths are supported; and when the SCS is greater than 60 kHz, a bandwidth greater than 24.25 GHz is supported in order to overcome phase noise.

[0087] NR frequency bands are defined as two types of frequency ranges: FR1 and FR2. FR1 can denote a range below 6 GHz, and FR2 can denote a range above 6 GHz, or can mean millimeter wave (mmW).

[0088] Table 2 below shows an example of the definition of NR bands.

[0089] [Table 2]

[0090]

[0091] With respect to the frame structure in the NR system, the size of each field in the time domain is expressed as a multiple of a time unit . In this case and N f = 4096. DL and UL transmissions are configured to have radio frames of segments. The radio frame consists of ten subframes, each of which has segments. In this case, there can be a set of UL frames and a set of DL frames.

[0092] The uplink frame number i for a transmission from a user equipment (UE) shall start before the start of the corresponding downlink frame for the corresponding UE.

[0093] For a numerology µ, the slots are numbered in ascending order of within a subframe and in ascending order of within a radio frame. One slot consists of consecutive OFDM symbols, and is determined depending on the numerology and the slot configuration used. The start of a slot in a subframe is aligned in time with the start of an OFDM symbol in the same subframe.

[0094] Not all UEs can transmit and receive at the same time, which means that not all OFDM symbols in a downlink slot or an uplink slot are available for use.

[0095] Table 3 represents the number of OFDM symbols per slot , the number of slots per radio frame , and the number of slots per subframe in normal CP. Table 4 represents the number of OFDM symbols per slot, the number of slots per radio frame, and the number of slots per subframe in extended CP.

[0096] [Table 3]

[0097]

[0098] [Table 4]

[0099]

[0100] Figure 1 An example of a frame structure in the NR system is illustrated. Figure 1 For convenience of explanation only, and not to limit the scope of the present disclosure.

[0101] In Table 4, in the case of µ = 2, as an example, a subcarrier spacing (SCS) is 60 kHz, one subframe (or frame) can include four slots, and for example, as shown in Figure 1 one subframe = {1, 2, 4} slots, the number of slots that can be included in one subframe can be defined as in Table 3.

[0102] In addition, one mini-slot can be composed of 2 symbols, 4 symbols, or 7 symbols, or can be composed of more or less symbols.

[0103] Regarding physical resources in the NR system, an antenna port, a resource grid, a resource element, a resource block, a carrier part, etc. can be considered.

[0104] The physical resources that can be considered in the NR system are described in detail below.

[0105] Figure 2 An example of a resource grid supported in the NR is shown.

[0106] Referring to Figure 2 , for each subcarrier spacing configuration and carrier, N size,µ grid *N RB sc subcarriers and 14∙2 µ OFDM symbols are defined, where N size,µ grid is indicated by RRC signaling from the BS. N size,µ grid It can be changed between uplink and downlink, and can also be changed with the subcarrier spacing configuration µ.

[0107] Each element in the resource grid for numerology µ and antenna port p is called a resource element, and is uniquely identified by the index pair , where is the index in the frequency domain, and refers to the position of the symbol in the subframe. The index pair is used to refer to a resource element in a slot, where .

[0108] The resource element for numerology µ and antenna port p corresponds to the complex value When there is no confusion risk or a specific antenna port or parameter set is not specified, the indices p and μ can be dropped, and thus the complex value can be or In addition, a physical resource block is defined as consecutive subcarriers in the frequency domain.

[0109] Considering that a UE can not be able to support a wide bandwidth to be supported by an NR system at a time, the UE can be configured to operate in a part of a frequency bandwidth (hereinafter, referred to as a bandwidth part (BWP)) of a cell.

[0110] A resource block of an NR system includes a physical resource block defined in a bandwidth part, and a common resource block numbered from 0 upwards in the frequency domain with respect to a subcarrier spacing configuration µ.

[0111] Point A is used as a common reference point of a resource block grid, and can be obtained as follows.

[0112] - offsetToPointA for PCell downlink indicates a frequency offset between point A and the lowest subcarrier of the lowest resource block overlapping the SS / PBCH block used by the UE for initial cell selection, and is expressed in units of resource blocks, assuming a subcarrier spacing of 15 kHz for FR1 and 60 kHz for FR2;

[0113] - absoluteFrequencyPointA indicates the frequency location of point A, expressed in absolute radio frequency channel number (ARFCN);

[0114] With respect to a subcarrier spacing configuration µ, the common resource blocks are numbered from 0 upwards in the frequency domain.

[0115] With respect to a subcarrier spacing configuration µ, the center of subcarrier 0 of common resource block 0 coincides with "point A". The common resource block number and a resource element (k, l) with respect to a subcarrier spacing configuration µ can be given by Equation 1 below.

[0116] [Equation 1]

[0117]

[0118] Here, k can be defined with respect to point A such that k = 0 corresponds to a subcarrier centered at point A. A physical resource block is defined within a bandwidth part (BWP), and is numbered from 0 to where i is the number of the BWP. The physical resource block in the BWP has a relationship with the common resource block which can be given by Equation 2 below.

[0119] [Formula 2]

[0120]

[0121] Here, may be a common resource block, where the BWP starts with respect to common resource block 0.

[0122] Bandwidth Part (BWP)

[0123] In the NR system, each carrier can support up to 400 MHz. If a UE operating in such a wideband carrier always operates with RF modules turned on for all carriers, the battery consumption of the UE can increase. Alternatively, considering several use cases (e.g., eMBB, URLLC, mMTC, V2X, etc.) operating in one wideband carrier, different numerologies (e.g., subcarrier spacing) can be supported for each band in the corresponding carrier. Alternatively, the capability of each UE can be different for the maximum bandwidth. Considering this, a base station (BS) can instruct a UE to operate only in a partial bandwidth of the wideband carrier, not in the entire bandwidth, and the partial bandwidth is defined as a bandwidth part (BWP). A BWP is a subset of contiguous common resource blocks within a bandwidth part i on a carrier, defined for a numerology µi in the frequency domain, and one numerology (e.g., subcarrier spacing, CP length, slot / minislot duration) can be configured.

[0124] A BS can configure one or more BWPs within one carrier configured for a UE. Alternatively, if UEs are concentrated on a specific BWP, some UEs can be transferred to a different BWP for load balancing. Alternatively, two BWPs can be configured in the same slot, excluding some center spectrum of the entire bandwidth, considering frequency-domain inter-cell interference cancellation between neighboring cells, etc. That is, a BS can configure at least one DL / UL BWP to a UE associated with a wideband carrier, can activate at least one of the configured DL / UL BWPs at a specific time (through L1 signaling (which is a physical layer control signal), a MAC control element (CE) (which is a MAC layer control signal), or RRC signaling, etc.), and instruct switching to other configured DL / UL BWPs (through L1 signaling, MAC CE, or RRC signaling, etc.), or if a timer value is set and the timer has expired, the UE can switch to a given DL / UL BWP. The activated DL / UL BWP is defined as an active DL / UL BWP. When a UE is in an initial access procedure or has not yet established an RRC connection, the UE can not be able to receive a configuration for a DL / UL BWP. In this case, the DL / UL BWP assumed by the UE is defined as an initial active DL / UL BWP.

[0125] Physical channels and general signal transmission

[0126] Figure 3 Physical channels and general signal transmission used in the 3GPP system are shown. In a wireless communication system, a UE receives information from an eNB through a downlink (DL) and transmits information to the eNB through an uplink (UL). The information that the eNB and the UE transmit and receive includes data and various control information, and there are various physical channels according to the type / use of the information that the eNB and the UE transmit and receive.

[0127] When the UE is powered on or newly enters a cell, the UE performs an initial cell search operation, for example, synchronization with the eNB (S301). To this end, the UE can receive a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) from the eNB and synchronize with the eNB and acquire information such as a cell ID. Thereafter, the UE can receive a physical broadcast channel (PBCH) from the eNB and acquire in-cell broadcast information. The UE receives a downlink reference signal (DL RS) in the initial cell search step to check a downlink channel state.

[0128] The UE that has completed the initial cell search receives a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) according to information loaded on the PDCCH to acquire more specific system information (S302).

[0129] When there is no radio resource first accessing the eNB or for signal transmission, the UE can perform a random access procedure (RACH) with the eNB (S303 to S306). To this end, the UE can transmit a specific sequence in the form of a preamble through a physical random access channel (PRACH) (S303 and S305) and receive a response message (random access response (RAR) message) for the preamble through a PDCCH and a corresponding PDSCH. In the case of a contention-based RACH, a contention resolution procedure can also be performed (S306).

[0130] The UE that has performed the above-described procedure can subsequently perform PDCCH / PDSCH reception (S307) and physical uplink shared channel (PUSCH) / physical uplink control channel (PUCCH) transmission (S308) like a general uplink / downlink signal transmission procedure. Specifically, the UE can receive downlink control information (DCI) through a PDCCH.

[0131] A UE monitors a set of PDCCH candidates in monitoring occasions of one or more sets of control elements (CORESETs) configured on a serving cell based on a corresponding search space configuration. The set of PDCCH candidates to be monitored by the UE is defined according to a search space set, which can be a common search space set or a UE-specific search space set. A CORESET is composed of a set of (physical) resource blocks with a duration of 1 to 3 OFDM symbols. The network can configure the UE with multiple CORESETs. The UE monitors PDCCH candidates in one or more search space sets. Here, monitoring means attempting to decode the PDCCH candidates in the search space. If the UE successfully decodes one of the PDCCH candidates in the search space, the UE determines that a PDCCH has been detected from the PDCCH candidate, and performs PDSCH reception or PUSCH transmission based on the DCI within the detected PDCCH.

[0132] A PDCCH can be used to schedule DL transmission on a PDSCH and UL transmission on a PUSCH. A DCI on a PDCCH includes a downlink assignment (i.e., DL grant) related to a downlink shared channel, and includes at least modulation and coding format and resource allocation information; or an uplink grant (UL grant) related to an uplink shared channel, and includes modulation and coding format and resource allocation information. The DCI has different formats according to its use.

[0133] Control information transmitted by the UE to the eNB through an uplink or received by the UE from the eNB can include a downlink / uplink ACK / NACK signal, a channel quality indicator (CQI), a precoding matrix index (PMI), a rank indicator (RI), etc. The UE can transmit control information such as CQI / PMI / RI through a PUSCH and / or a PUCCH.

[0134] Synchronization signal block (SSB) transmission and related operations

[0135] Figure 4 An SSB structure to which the method proposed in the disclosure can be applied is shown. A UE can perform cell search, system information acquisition, beam alignment for initial access, DL measurement, etc. based on an SSB. An SSB can be used interchangeably with a synchronization signal / physical broadcast channel (SS / PBCH) block.

[0136] Reference Figure 4 The SSB includes a PSS, an SSS, and a PBCH. The SSB is composed of four consecutive OFDM symbols, on each of which a PSS, a PBCH, an SSS / PBCH, or a PBCH is transmitted. The PSS and the SSS are each composed of one OFDM symbol and 127 subcarriers, and the PBCH is composed of 3 OFDM symbols and 576 subcarriers.

[0137] Polar coding and quadrature phase shift keying (QPSK) are applied to PBCH. PBCH consists of data REs and demodulation reference signal (DMRS) REs on each OFDM symbol. There are three DMRS REs in each RB, and there are three data REs between the DMRS REs.

[0138] Figure 5 SSB transmission to which the method proposed in the disclosure can be applied is shown.

[0139] SSBs are periodically transmitted according to an SSB period. A default SSB period assumed by a UE during initial cell search is defined as 20 ms. After cell access, a network (e.g., BS) can set the SSB period to one of {5 ms, 10 ms, 20 ms, 40 ms, 80 ms, 160 ms}. An SSB burst set is configured at the beginning of the SSB period. An SSB burst set includes a time window of 5 ms (i.e., a half frame), and SSBs can be transmitted up to N times within the SSB burst set. The maximum number of transmissions L of SSBs can be given according to the frequency band of the carrier as follows. One slot includes up to two SSBs.

[0140] - For a frequency range of up to 3 GHz, L = 4

[0141] - For a frequency range of 3 GHz to 6 GHz, L = 8

[0142] - For a frequency range of 6 GHz to 52.6 GHz, L = 64

[0143] The time location of an SSB candidate within an SSB burst set can be defined according to the SCS as follows. The time location of an SSB candidate is indexed from 0 to L-1 based on the time order within the SSB burst set (i.e., a half frame) (SSB index).

[0144] Multiple SSBs can be transmitted within the frequency span of a carrier. The physical layer cell identifiers of these SSBs need not be unique, and other SSBs can have other physical layer cell identifiers.

[0145] A UE can acquire DL synchronization by detecting an SSB. The UE can identify the structure of an SSB burst set based on the detected SSB (time) index, and thus can detect symbol / slot / half frame boundaries. System frame number (SFN) information and half frame indication information can be used to identify the number of a frame / half frame to which the detected SSB belongs.

[0146] The above-described content can be combined and applied to the methods described below in the present disclosure, or can be supplemented to clarify the technical features of the methods described in the present disclosure. The methods described below are distinguished only for the convenience of explanation. Therefore, it is obvious that the partial configuration of any method can be replaced or combined with that of another method.

[0147] Technical terms used in the present disclosure

[0148] UE: User Equipment

[0149] SSB: Synchronization Signal Block

[0150] MIB: Master Information Block

[0151] RMSI: Remaining Minimum System Information

[0152] FR1: Frequency Range 1. It refers to a frequency area of 6 GHz or lower (e.g., 450 MHz to 6,000 MHz).

[0153] FR2: Frequency Range 2. It refers to a millimeter wave (mmWave) frequency area of 24 GHz or higher (e.g., 24,250 MHz to 52,600 MHz).

[0154] BW: Bandwidth

[0155] BWP: Bandwidth Part

[0156] RNTI: Radio Network Temporary Identifier

[0157] CRC: Cyclic Redundancy Check

[0158] SIB: System Information Block

[0159] SIB1: SIB1 for NR device = RMSI (Remaining Minimum System Information). It broadcasts information required for cell access of NR UE, etc.

[0160] CORESET (Control Resource Set, COntrol REsource SET): Time / frequency resources in which an NR UE attempts candidate PDCCH decoding

[0161] CORESET#0: CORESET for Type0-PDCCH CSS set for NR device (configured in MIB)

[0162] Type0-PDCCH CSS set: Search space set in which an NR UE monitors a set of PDCCH candidates for DCI format with CRC scrambled by SI-RNTI.

[0163] MO: PDCCH monitoring occasion for Type0-PDCCH CSS set

[0164] SIB1-R: (additional) SIB1 for reduced capability NR devices. It can be limited when generated using a different TB than SIB1 and transmitted on a separate PDSCH.

[0165] CORESET#0-R: CORESET#0 for reduced capability NR devices

[0166] Type0-PDCCH-R CSS set: Search space set where reduced capability (Redcap) UEs monitor a set of PDCCH candidates for DCI format with CRC scrambled by SI-RNTI.

[0167] MO-R: PDCCH monitoring occasion for Type0-PDCCH CSS set.

[0168] Cell-defining SSB (CD-SSB): SSB among NR SSBs that includes RMSI scheduling information.

[0169] Non-cell-defining SSB (non-CD-SSB): SSB that has been deployed on the NR synchronization raster but does not include RMSI scheduling information of the corresponding cell to be measured. However, the SSB can include information informing the location of the cell-defining SSB.

[0170] SCS: Subcarrier Spacing

[0171] SI-RNTI: System Information Radio Network Temporary Identifier

[0172] Camp on: "Camp on" refers to the state in which the UE stays on a cell and is ready to initiate potential dedicated services or receive ongoing broadcast services.

[0173] TB: Transport Block

[0174] RSA (Redcap standalone): Cell that supports only Redcap devices or services

[0175] SIB1(-R)-PDSCH: PDSCH transmitting SIB1(-R)

[0176] SIB1(-R)-DCI: DCI scheduling SIB1(-R)-PDSCH. DCI format 1_0 with CRC scrambled by SI-RNTI.

[0177] SIB1(-R)-PDCCH: PDCCH transmitting SIB1(-R)-DCI

[0178] FDRA: Frequency Domain Resource Allocation

[0179] TDRA: Time Domain Resource Allocation

[0180] RA: Random Access

[0181] MSGA: Preamble and payload transmission for 2-step RA type random access procedure.

[0182] MSGB: Response to MSGA in 2-step random access procedure. MSGB can contain response for contention resolution, backoff indication and backoff indication.

[0183] RO-N: RACH Occasion (RO) for normal UE 4-step RACH and 2-step RACH (if configured)

[0184] RO-N1, RO-N2: If separate RO is configured for normal UE 2-step RACH, split into RO-N1 (4-step) and RO-N2 (2-step).

[0185] RO-R: RACH Occasion (RO) for Redcap UE 4-step RACH and 2-step RACH (if configured) configured separately from RO-N

[0186] RO-R1, RO-R2: If separate RO is configured for Redcap UE 2-step RACH, split into RO-R1 (4-step) and RO-R2 (2-step).

[0187] PG-R: MsgA Preamble Group for RedCap UE

[0188] RAR: Random Access Response

[0189] RAR window: Time window for monitoring RA response

[0190] FH: Frequency Hopping

[0191] iBWP: Initial BWP

[0192] iBWP-DL(-UL): Initial DL(UL) BWP

[0193] iBWP-DL(-UL)-R: (Separate) DL(UL) BWP for RedCap

[0194] CS: Cyclic Shift

[0195] NB: Narrow Band

[0196] TO: Traffic Offload

[0197] mMTC; Massive Machine Type Communication

[0198] eMBB: enhanced mobile broadband communication

[0199] URLLC: ultra-reliable low-latency communication

[0200] RedCap: reduced capability

[0201] eRedCap: enhanced RedCap

[0202] FDD: frequency division duplex

[0203] HD-FDD: half duplex FDD

[0204] DRX: discontinuous reception

[0205] RRC: radio resource control

[0206] RRM: radio resource management

[0207] IWSN: industrial wireless sensor network

[0208] LPWA: low power wide area

[0209] RB: resource block

[0210] CCE: control channel element

[0211] AL: aggregation level

[0212] PRG: physical resource block group

[0213] DFT-s-OFDM: DFT-spread OFDM

[0214] PBCH: physical broadcast channel

[0215] A-PBCH: additional PBCH

[0216] BD: blind detection

[0217] EPRE: energy per RE

[0218] SNR: signal-to-noise ratio

[0219] TDM: time division multiplexing

[0220] DMRS: demodulation reference signal

[0221] TDD: time division duplex

[0222] FDM: frequency division multiplexing

[0223] PRI: PUCCH resource indicator

[0224] SS: search space

[0225] In the disclosure, “( )” can be interpreted as excluding the content in the parentheses, or as including the content in the parentheses.

[0226] In the disclosure, “ / ” can be interpreted as including all the content separated by “ / ” (and), or as including only a part of the separated content (or).

[0227] Compared to the previous generation wireless communication system (e.g., LTE, GSM), the 5G wireless communication system is characterized by efficiently supporting use cases such as mMTC, eMBB, and URLLC. Due to these advantages, the 5G wireless communication system is expected to create new use cases and gradually replace the previous generation wireless communication system for various use cases.

[0228] Specifically, the features of the 5G wireless communication system such as enhanced low latency, high reliability, massive connectivity, etc., can be very useful for services / use cases (hereinafter referred to as NB services / use cases) that have been supported in the existing narrowband (NB) dedicated spectrum, as follows.

[0229] [Examples of services / use cases to which the disclosure is applicable]

[0230] i) Railway mobile communication

[0231] ii) Utility / infrastructure network

[0232] iii) Mobile communication for public safety

[0233] The NB services / use cases have been supported using the previous generation wireless communication system in the frequency band less than 1 GHz in the FDD dedicated spectrum with a bandwidth of about 3 MHz or more and less than 5 MHz.

[0234] Consider a method of supporting NB services / use cases in the 5G wireless communication system in the same environment (i.e., in the frequency band less than 1 GHz in the FDD dedicated spectrum with a bandwidth of about 3 MHz or more and less than 5 MHz). To this end, it can be necessary to support a channel bandwidth less than 5 MHz in the 5G NR standard. The minimum channel bandwidth currently supported in the 5G NR standard is 5 MHz.

[0235] [Examples of 5G NR bands for supporting NB services / use cases (TS 38.101-1)]

[0236] For example, the NB services / use cases can be supported in the following NR operating bands defined in the NR standard TS 38.101-1.

[0237] [Table 5]

[0238]

[0239] Table 5 shows UL / DL operating bands defined per NR operating band for frequency range 1 FR1.

[0240] [Example of definition of sub-5 MHz channel BW for supporting NB service / use case]

[0241] Table 6 shows an example of maximum configurable number of resource blocks (N RB ) per channel BW. According to Table 6, in order to support 5G NR based NB service / use case, 3 MHz channel BW is defined along with maximum configurable number of resource blocks (N RB ) (= 15) in 3 MHz channel BW, and in this case, resource utilization (or RU) is defined. RU can be defined as follows.

[0242] RU = (N RB (in MHz)) / (channel BW (in MHz))

[0243] [Table 6]

[0244]

[0245] For example, for newly defined 3 MHz channel BW, considering interference between adjacent channels and resource utilization, one of N RB values shown in Table 7 below can be defined and used. For example, multiple values among N RB values shown in Table 7 below can be supported in NR standard, and base station configuration can support / use them.

[0246] [Table 7]

[0247]

[0248] For example, channel BW / N RB may be applied to DL and UL with the same value. For example, channel BW / N RB may be configured / supported respectively / independently for DL and UL. The method according to the second example can be applied to the following situation. The method can be applicable when the following condition is intended to be applied: in determining N RB value, only additional DFT precoding on UL is applied while considering interference between adjacent channels and resource utilization, maximum channel BW / N RB value is supported in both DL and UL.

[0249] If a channel BW less than 5 MHz is newly supported in the NR standard, reception of the existing NR common / broadcast signal / channel can be problematic. For example, if the SSB transmission bandwidth exceeds the newly supported minimum channel bandwidth (BW), it can not be possible to transmit / receive the entire SSB. This will be described in detail with reference to Figure 6 .

[0250] Figure 6 An example of an SSB time-frequency structure according to an embodiment of the disclosure is illustrated. Specifically, Figure 6 a plurality of REs / a plurality of RBs in the time-frequency structure are added for each region. Referring to Figure 4 , the frequency domain (bandwidth) for PSS and SSS is composed of 127 resource elements (REs). The frequency domain (bandwidth) for PBCH is composed of 20 resource blocks (RBs) (= 144 REs) or 4 RBs (= 48 REs). Figure 6

[0251] As shown in Tables 6 and 7, N RB may be determined as one value among {12, 13, 14, 15}. For example, assume that N RB is 12 (12 PRBs = 2.16 MHz) and the SSB has a 15 kHz SCS (subcarrier spacing). The entire PSS / SSS bandwidth (127 REs = 1.905 MHz) can be transmitted / received, but it can not be possible to entirely transmit / receive for PBCH (20 PRBs = 3.6 MHz).

[0252] In this case, the UE can normally receive PSS / SSS through the UE operation defined in the existing NR standard (without reception coverage loss). On the other hand, for PBCH, reception coverage loss can be inevitable. This can result in total reception coverage loss of the UE operating in a narrow band.

[0253] In order to receive SIB1-PDCCH in a narrow band, the UE can receive CORESET#0 and Type0-PDCCH CSS set information through MIB transmitted via PBCH. Since the bandwidth of CORESET#0 supported by the current NR standard is 24 PRBs (4.32 MHz) based on 15 kHz SCS, it can exceed the narrow band channel BW shown in Tables 6 and 7. In this case, the base station can transmit only PDCCH transmission REs belonging to the channel BW after mapping the PDCCH transmission REs to CORESET#0. That is, the remaining part can be transmitted by puncturing / truncating the PDCCH transmission REs exceeding the channel BW. Puncturing related to CORESET can be performed based on the following Table 8. ​

[0254] [Table 8]

[0255]

[0256]

[0257] The disclosure proposes a method for determining a PUCCH transmission resource when a CORESET #0 or a CORESET exceeds a narrowband channel BW or a maximum transmission BW defined for the narrowband in a narrowband.

[0258] In the disclosure, a narrowband and NB can be interchangeable and applicable / interpretable. Also, a channel BW and a maximum transmission BW (max transmission BW) can be interchangeable and applicable / interpretable.

[0259] In the disclosure, broadcast signaling includes a signaling method using system information including SIB1, MIB, a PBCH payload generated in a PHY layer other than MIB, and PBCH scrambling sequence and PBCH DMRS sequence initialization information.

[0260] PUCCH transmission method in a narrowband

[0261] For a common PUCCH transmission in a narrowband through an initial UL BWP, a base station selects one of 16 PUCCH resource sets defined in the following Table 9, and transmits an index (0 to 15) value corresponding to the selected PUCCH resource set through broadcast signaling (in this case, SIB1). The UE determines a common PUCCH resource set to be used for a common PUCCH transmission by referring to the PUCCH resource set index value transmitted by the base station through broadcast signaling and the table of the following Table 9. In the disclosure, a common PUCCH transmission can refer to a PUCCH transmission before a dedicated PUCCH resource configuration is received.

[0262] [Table 9]

[0263]

[0264] When a base station / UE transmits a common PUCCH, the following Table 10 shows a scheme for determining a resource for transmitting a common PUCCH.

[0265] [Table 10]

[0266]

[0267] That is, a PUCCH transmission resource for transmitting a common PUCCH is dynamically indicated / determined based on a 3-bit PUCCH resource indicator (PRI) indicated through DCI, and is defined in Table 10 and .

[0268] As described above, the entire CORESET#0 can not be included in the narrowband channel BW due to the reason that the CORESET#0 exceeds the narrowband channel BW in the narrowband. In this case, the base station can perform RE mapping for the PDCCH on the entire CORESET#0 in the legacy scheme and then transmit only the PDCCH transmission REs belonging to the narrowband channel BW in the unit of RE / REG / CCE / RB (or the base station can puncture and transmit the PDCCH transmission REs not belonging to the narrowband channel BW in the unit of RE / REG / CCE / RB). In the case where some of the PDCCH transmission REs are punctured by the CORESET#0, the base station / UE can indicate / determine values (and ) to select the common PUCCH transmission resource corresponding to the case.

[0269] Hereinafter, for convenience of description, the indication / determination of values will be mainly described, but the scope of application of the embodiments to be described below is not limited to only the indication / determination of values. That is, it is obvious that the embodiments / methods described below can be widely applied to the indication / determination of at least one of the values ( , , and / or ) related to the determination of the PUCCH resource defined in Table 10. As a specific example, when the number of CCEs within the CORESET (for example, CORESET#0 and CORESET#p) changes, the CCE index (for example, and ) can also change. Therefore, the embodiments / methods described below can be applied to the indication / determination of ( ) and / or . In the method #1 to the method #4, the indication / determination of the value of can be interpreted / interchanged as the indication / determination of the value of or the indication / determination of and .

[0270] [Method #1]

[0271] When the entire CORESET#0 is not included in the narrowband channel BW and some PDCCH transmission REs are punctured and PDCCH is transmitted / received, the value of

[0272] As an example, the value of may be determined based on CCE indices in the PDCCH RE mapping step of the whole CORESET#0 before performing PDCCH puncturing. As an example, the value of may be determined based on CCE indices in the PDCCH RE mapping step of the whole CORESET#0 before performing PDCCH puncturing.

[0273] That is, even in the case that some of the PDCCH transmission REs through the actual CORESET#0 are punctured and transmitted / received, the base station / UE can assume that the puncturing is not applied regardless of whether the puncturing is applied or not, and indicate / determine the value of According to embodiments, may be the number of CCEs in the CORESET#0 before performing PDCCH puncturing.

[0274] [Method #2]

[0275] When the whole of the CORESET#0 is not included in the narrowband channel BW and some of the PDCCH transmission REs are punctured and PDCCH is transmitted / received, the value of may be indicated / determined based on CCE indices after PDCCH puncturing.

[0276] Specifically, when some of the PDCCH transmission REs through the actual CORESET#0 are punctured and transmitted / received, the value of may be indicated / determined as follows. As an example, the value of may be indicated / determined in a state excluding some or all of the punctured CCE indices. As an example, the value of may be indicated / determined among all of the transmitted / received CCE indices without puncturing.

[0277] Alternatively, when some of the PDCCH transmission REs through the actual CORESET#0 are punctured and transmitted / received, the value of may be indicated / determined as follows. As an example, the value of may be indicated / determined in a state excluding all of the punctured CCE indices. As an example, the value of may be indicated / determined among some or all of the received CCE indices.

[0278] According to embodiments, may be the number of CCEs in the CORESET#0 before performing PDCCH puncturing.

[0279] The methods (Method #1 and Method #2) are not limited to common PUCCH transmission, and can also be applied to dedicated PUCCH transmission after receiving the dedicated PUCCH resource configuration. Further, in these methods, CORESET #0 can be interchanged, and is interpreted / applied as other general CORESET, i.e., CORESET #p (p is 1, 2, etc.).

[0280] After receiving the dedicated PUCCH resource configuration, the UE determines the PUCCH resource set for PUCCH transmission for HARQ ACK feedback according to the scheme shown in Table 11 below.

[0281] [Table 11]

[0282]

[0283] In the case of the first PUCCH resource set, up to 32 PUCCH resources can be configured. When the number of PUCCH resources in the first PUCCH resource set is greater than 8, the PUCCH resources in the first PUCCH resource set are determined according to the scheme shown in Table 12 below.

[0284] [Table 12]

[0285]

[0286] That is, the PUCCH resources for the dedicated PUCCH can be indicated / determined similarly to the PUCCH resource indication / determination method for common PUCCH transmission. Specifically, the corresponding PUCCH resources are dynamically indicated / determined by the 3-bit PUCCH resource indicator indicated by the DCI, and (and ) are defined in Table 11 and Table 12. Therefore, even in dedicated PUCCH transmission, when the number of PUCCH resources in the PUCCH resource set exceeds 8, a similar method to that in common PUCCH transmission can be applied as follows.

[0287] As described above, the entire CORESET #p can not be included in the narrowband channel BW due to the CORESET #p exceeding the narrowband channel BW in the narrowband. The base station can perform RE mapping for PDCCH with respect to the entire CORESET #p in a regular scheme for the entire CORESET #p, and then transmit only the PDCCH transmission RE belonging to the narrowband channel BW in units of RE / REG / CCE / RB (or the base station can puncture and transmit the PDCCH transmission RE not belonging to the narrowband channel BW). In this way, in the case where some of the PDCCH transmission REs are punctured by the CORESET #p, the base station / UE can indicate / determine value of the PUCCH transmission resource corresponding to the case.

[0288] [Method #3]

[0289] When the entire CORESET #p is not included in the narrowband channel BW and some of the PDCCH transmission REs are punctured and PDCCH is transmitted / received, the value of the PUCCH transmission resource corresponding to the case can be indicated / determined as follows.

[0290] As an example, the value of the PUCCH transmission resource corresponding to the case can be determined based on the CCE index before the PDCCH puncturing is performed. As an example, the value of the PUCCH transmission resource corresponding to the case can be determined based on the CCE index in the PDCCH RE mapping step for the entire CORESET #p.

[0291] That is, even in the case where some of the PDCCH transmission REs through the actual CORESET #p are punctured and are transmitted / received, the base station / UE can assume that the puncturing is not applied regardless of whether the puncturing is applied, and indicate / determine the value of the PUCCH transmission resource corresponding to the case. may be the number of CCEs in the CORESET #p before the PDCCH puncturing is performed.

[0292] [Method #4]

[0293] When the entire CORESET #p is not included in the narrowband channel BW and some of the PDCCH transmission REs are punctured and PDCCH is transmitted / received, the value of the PUCCH transmission resource corresponding to the case can be indicated / determined based on the CCE index after the PDCCH puncturing.

[0294] Specifically, when some of the PDCCH transmission REs through the actual CORESET #p are punctured and are transmitted / received, the value of the PUCCH transmission resource corresponding to the case can be indicated / determined as follows. As an example, the value of the PUCCH transmission resource corresponding to the case can be indicated / determined in a state excluding some or all of the punctured CCE indices. As an example, the value of the PUCCH transmission resource corresponding to the case can be indicated / determined among all of the transmitted / received CCE indices without puncturing.

[0295] Alternatively, when some of the PDCCH transmission REs through the actual CORESET #p are punctured and are transmitted / received, the value of the PUCCH transmission resource corresponding to the case can be indicated / determined as follows. As an example, the value of the PUCCH transmission resource corresponding to the case can be indicated / determined in a state excluding only all of the punctured CCE indices. As an example, the value of the PUCCH transmission resource corresponding to the case can be indicated / determined among some or all of the received CCE indices. ​​​​​​​​​ the value of the CORESET#p.

[0296] According to embodiments, may be the number of CCEs in the CORESET#p after performing PDCCH puncturing.

[0297] Hereinafter, the PUCCH resource determination method considering the scheme using a new CORESET#0 or the scheme reusing a regular CORESET#0 when the narrow channel BW is less than the minimum bandwidth will be described in more detail.

[0298] As described above, the narrow band channel BW can be less than the minimum bandwidth of the regular CORESET#0 designed considering the general bandwidth. In this case, the CORESET#0 bandwidth can exceed the narrow band channel BW. For example, since the bandwidth of the CORESET#0 supported by the current NR standard is 24 PRBs (4.32 MHz) based on 15 kHz SCS, it can exceed the narrow band channel BW shown in Table 6 and Table 7. To support this case, the following two schemes are proposed.

[0299] [#1] New CORESET#0 reuse scheme

[0300] According to this scheme, a new CORESET#0 having a small bandwidth included in the narrow band channel BW is defined and used, and the PDCCH is transmitted through the newly defined CORESET#0.

[0301] [Example #1] A CORESET#0 having a 12-PRB bandwidth less than 24 PRBs as a regular bandwidth can be newly defined in order to support a 3 MHz channel bandwidth.

[0302] [#2] Regular CORESET#0 reuse scheme

[0303] According to this scheme, the regular CORESET#0 can be reused, and the PDCCH can be transmitted by excluding the part mapped as REs by exceeding the narrow band channel BW, or the PDCCH can be transmitted by puncturing / truncating the part mapped as REs by exceeding the narrow band channel BW.

[0304] That is, the base station performs PDCCH RE mapping on the entire regular CORESET#0 bandwidth in the regular scheme. The base station can transmit only the PDCCH transmission RE / RB / REG / REG bundle / CCE included in the narrow band channel BW (i.e., transmit the PDCCH based on the PDCCH transmission RE / RB / REG / REG bundle / CCE included in the narrow band channel BW). In this case, the meaning of "include" can include the meaning of "partially include" or "entirely include".

[0305] [Example #1] An existing 24-PRB CORESET#0 defined in the table (see Table 13 below) can be reused in order to support a 3-MHz channel bandwidth. For PDCCH transmission REs / RBs / REGs / REG bundles / CCEs (e.g., 15 PRBs based on 15 kHz SCS) mapped over 3 MHz bandwidth, PDCCH can be transmitted without puncturing / truncation, or a UE can not expect / request PDCCH reception.

[0306] [Table 13]

[0307]

[0308] A base station / UE can determine / indicate PUCCH resources for transmitting a common PUCCH in a narrowband wireless communication system including and A common PUCCH transmission resource determination procedure can be determined / indicated in a narrowband wireless communication system following an existing definition (e.g., Table 10) of a scenario by the following methods. In addition, for parts not separately described in the present disclosure, an existing defined / regulation common PUCCH transmission resource determination procedure can be followed.

[0309] When the entire CORESET#0 is used for transmitting PDCCH by applying a new CORESET#0 usage scheme, there can be no problem in applying a regular scheme. That is, in this case, a base station / UE can determine / indicate and based on the regular scheme. That is, the number of CCEs in CORESET#0 (CORESET#0) can be determined / indicated based on the CORESET#0 bandwidth, and the first CCE index of PDCCH (PDCCH) can be determined / indicated by the CCE frequency location of PDCCH. Meanwhile, in a scenario in which a regular CORESET#0 reuse scheme is applied, the entire CORESET#0 can not be used for transmitting PDCCH. In this case, there can be confusion in the determination / indication of and

[0310] between a base station and a UE or between UEs. There can be a problem in transmitting / receiving a common PUCCH. In order to solve such a problem, the following methods are proposed, and the transmission of a common PUCCH is supported. A method of determining and

[0311] based on PDCCH transmission / reception bandwidth can be considered.

[0312] A method of determining and based on PDCCH transmission / reception bandwidth can be considered.

[0313] According to a conventional scheme, defined as the number of CCEs in the CORESET for PDCCH reception. As exemplified in the scenario where the conventional CORESET#0 reuse scheme is applied, when the entire CORESET#0 bandwidth is not used for PDCCH transmission / reception, it can be determined / indicated as follows and .

[0314] Based on the "PDCCH transmission / reception bandwidth", i.e., the bandwidth in which actual PDCCH transmission / reception is enabled in the CORESET#0 bandwidth, the base station / UE can determine / indicate and In this case, the PDCCH transmission / reception bandwidth in the CORESET#0 bandwidth can be determined to be a value less than or equal to i) the (maximum / supported) transmission bandwidth supported by the narrowband or ii) the (maximum / supported) channel bandwidth. The latter case can include the case where the PBCH transmission / reception bandwidth is defined as the PDCCH transmission / reception bandwidth.

[0315] In the scenario where the conventional CORESET#0 reuse scheme is applied, the base station can perform PDCCH RE mapping according to the existing regulation procedure for the entire CORESET#0 bandwidth. The base station can transmit all PDCCH transmission REs. Alternatively, the base station can transmit (all or some of) the PDCCH transmission REs included in the PDCCH transmission / reception bandwidth in units of RE / RB / REG / REG bundle / CCE. In the present disclosure, "transmission of PDCCH transmission REs" can mean "PDCCH transmission in REs for PDCCH transmission".

[0316] At the receiver, the UE can expect to receive only the PDCCH transmitted by the base station in the scheme for (all or some of) the PDCCH transmission REs / RBs / REGs / REG bundles / CCEs included in the PDCCH transmission / reception bandwidth. Alternatively, the UE can be required to perform a corresponding reception operation.

[0317] That is, when receiving the PDCCH, it can not be required or expected for the terminal to perform reception for the PDCCH transmission REs / RBs / REGs / REG bundles / CCEs mapped by the base station to outside the PDCCH transmission / reception bandwidth, regardless of whether actual transmission is performed.

[0318] When the base station / UE transmitting / receiving the PDCCH in the scheme determines / indicates the common PUCCH transmission resource by applying Method #5, the base station / UE can determine / indicate and That is, based on the PDCCH transmission / reception bandwidth rather than the entire CORESET#0 bandwidth, it is possible to determine and to generate / determine the CCE index based on It is possible to determine based on the PDCCH CCE frequency location where the DCI is received. In this case, the first CCE index of the PDCCH corresponding to the received DCI can be determined as It can be the first CCE index of the PDCCH actually transmitted / received (i.e., after applying puncturing / truncation) among the CCE indexes generated / determined in the PDCCH transmission / reception bandwidth.

[0319] [Example #1 in Method #5] In [Example #1] of the conventional CORESET#0 reuse scheme, it can be assumed that the channel bandwidth is 15 PRBs, and the CORESET#0 is 24 PRBs and 3 symbols. When the Method #5 is applied to determine the common PUCCH transmission resource, may be determined as 6 (= 2*3), and may be determined as one of the values from 0 to 5 according to the PDCCH CCE frequency location where the DCI is received. Alternatively, when the CCE index is generated / determined by allowing the PDCCH to be partially transmitted in the same scenario, may be determined as 9 (= 3*3), and may be determined as one of the values from 0 to 8 according to the PDCCH CCE frequency location where the DCI is received.

[0320] [Example #2 in Method #5] For example, it can be assumed that a scenario for supporting a partial bandwidth in a 5-MHz channel bandwidth for NR is supported. Specifically, in a scenario in which the bandwidth supporting NR is 20 PRBs, it can be assumed that the CORESET#0 is the case of 24 PRBs and 3 symbols. When the Method #5 is applied to determine the common PUCCH transmission resource, may be determined as 9 (= 3*3), and may be determined as one of the values from 0 to 8 according to the PDCCH CCE frequency location where the DCI is received. Alternatively, when the CCE index is generated / determined by allowing the PDCCH to be partially transmitted in the same scenario, may be determined as 12 (= 4*3), and may be determined as one of the values from 0 to 11 according to the PDCCH CCE frequency location where the DCI is received.

[0321] [Method #6]

[0322] It can be considered to determine and​ a method.

[0323] As exemplified in the scenario where the conventional CORESET#0 reuse scheme is applied, when the entire CORESET#0 bandwidth is not used for PDCCH transmission / reception, the and may be determined / indicated based on the CORESET#0 bandwidth.

[0324] In the scenario where the conventional CORESET#0 reuse scheme is applied, the base station can perform PDCCH RE mapping according to the existing regulation procedure for the entire CORESET#0 bandwidth. The base station can transmit all PDCCH transmission REs. Alternatively, the base station can transmit (all or some of) PDCCH transmission REs included in the PDCCH transmission / reception bandwidth in units of RE / RB / REG / REG bundle / CCE. In the present disclosure, "transmission of PDCCH transmission RE" can mean "PDCCH transmission in REs for PDCCH transmission".

[0325] At the receiver, the UE can expect to receive only PDCCHs transmitted by the base station in the scheme for (all or some of) PDCCH transmission REs / RBs / REGs / REG bundles / CCEs included in the PDCCH transmission / reception bandwidth. Alternatively, the UE can be required to perform a corresponding reception operation.

[0326] That is, when receiving a PDCCH, the UE can not be required or expected to receive PDCCH transmission REs / RBs / REGs / REG bundles / CCEs mapped by the base station to outside the PDCCH transmission / reception bandwidth (whether or not actual transmission is performed).

[0327] When the base station / UE transmitting / receiving a PDCCH in the scheme determines / indicates a common PUCCH transmission resource by applying Method #6, the and may be determined / indicated as follows. By assuming that the PDCCH is continuously transmitted / received in the entire CORESET#0 bandwidth, and and may be determined / indicated. That is, based on the entire CORESET#0 bandwidth rather than the PDCCH transmission / reception bandwidth, the may be determined, and the CCE index can be generated / determined based on . may be determined based on the PDCCH CCE frequency location in which the DCI is received. In this case, the may be i) the first CCE index of the PDCCH actually transmitted / received (i.e., after applying puncturing / truncation) in the PDCCH transmission / reception bandwidth, or ii) the first CCE index of the PDCCH in terms of PDCCH RE mapping (i.e., before applying puncturing / truncation).

[0328] [Example #1 in Method #6] In [Example #1] of the regular CORESET#0 reuse scheme, it can be assumed that the channel bandwidth is 15 PRBs, and CORESET#0 is 24 PRBs and 3 symbols. When applying Method #6 to determine the common PUCCH transmission resource, may be determined as 12 (= 4*3), and may be determined as one of the values from 0 to 11 according to the PDCCH CCE frequency location where the DCI is received.

[0329] [Example #2 in Method #6] For example, a scenario supporting a partial bandwidth in a 5 MHz channel bandwidth for NR can be envisaged. Specifically, in a scenario where the bandwidth supporting NR is 20 PRBs, it can be assumed that CORESET#0 is the case of 24 PRBs and 3 symbols. When applying Method #6 to determine the common PUCCH transmission resource, may be determined as 12 (= 4*3), and may be determined as one of the values from 0 to 11 according to the PDCCH CCE frequency location where the DCI is received.

[0330] [Method #7]

[0331] Methods for determining based on the CORESET#0 bandwidth and based on the PDCCH transmission / reception bandwidth can be considered.

[0332] In addition, other than the above-described Method #5 and Method #6, when the entire CORESET#0 bandwidth is not used for PDCCH transmission / reception, the and may be determined / indicated as follows.

[0333] The base station / UE can determine based on the CORESET#0 bandwidth. In addition, the base station / UE can determine based on the PDCCH transmission / reception bandwidth.

[0334] In a scenario where a conventional CORESET#0 reuse scheme is applied, the base station can perform PDCCH RE mapping according to the existing regulation procedure for the entire CORESET#0 bandwidth. The base station can transmit all PDCCH transmission REs. Alternatively, the base station can transmit (all or some) PDCCH transmission REs included in the PDCCH transmission / reception bandwidth in units of RE / RB / REG / REG bundle / CCE.

[0335] At the receiver, the UE can expect to receive only PDCCHs transmitted by the base station in the scheme for (all or some) PDCCH transmission REs / RBs / REGs / REG bundles / CCEs included in the PDCCH transmission / reception bandwidth. Alternatively, the UE can be required to perform a corresponding reception operation.

[0336] That is, when receiving a PDCCH, the UE can not be required or expected to receive PDCCH transmission REs / RBs / REGs / REG bundles / CCEs mapped by the base station outside the PDCCH transmission / reception bandwidth (whether or not actual transmission is performed).

[0337] When the base station / UE transmitting / receiving a PDCCH in the scheme determines a common PUCCH transmission resource by applying Method #7, the following can be determined / indicated and By assuming that the PDCCH is transmitted / received continuously in the entire CORESET#0 bandwidth, the following can be determined / indicated That is, the following can be determined / indicated based on the entire CORESET#0 bandwidth rather than the PDCCH transmission / reception bandwidth Meanwhile, the CCE index can be generated / determined based on the PDCCH transmission / reception bandwidth. In this case, when the total number of CCEs calculated based on the PDCCH transmission / reception bandwidth is ( ), the CCE index can have a value of 0 to Based on the generated CCE index, the following can be determined based on the PDCCH CCE frequency position of the received DCI In this case, the corresponding to the received DCI can be the first CCE index of the PDCCH actually transmitted / received (i.e., after applying puncturing / truncation) in the PDCCH transmission / reception bandwidth.

[0338] [Example #1 in Method #7] In [Example #1] of the conventional CORESET#0 reuse scheme, it can be assumed that the channel bandwidth is 15 PRBs and the CORESET#0 is 24 PRBs and 3 symbols. When Method #7 is applied to determine a common PUCCH transmission resource, may be determined as 12 (= 4*3), may be determined as 6 (= 2*3), and may be one of values from 0 to 5 according to the PDCCH CCE frequency location where the DCI is received.

[0339] [Example #2 in Method #7] For example, a scenario supporting a partial bandwidth in a 5 MHz channel bandwidth for NR can be assumed. Specifically, in a scenario where a bandwidth supporting NR is 20 PRBs, a case where CORESET #0 is 24 PRBs and 3 symbols can be assumed. When Method #7 is applied to determine a common PUCCH transmission resource, may be determined as 12 (= 4*3), may be determined as 9 (= 3*3), and may be one of values from 0 to 8 according to the PDCCH CCE frequency location where the DCI is received.

[0340] The overall base station / UE operation flow applying the described methods can be as follows.

[0341] [1] The base station determines one of the above-described methods (Method #1 to Method #7). The base station transmits a PUCCH resource based on the determined method and / or information related to the PUCCH resource determination scheme through broadcast signaling.

[0342] [2] The UE determines a PUCCH transmission resource in the same method as the determination method of the base station by referring to the information received through broadcast signaling and other information.

[0343] [3] The UE transmits a PUCCH based on the determined PUCCH transmission resource. The base station determines a PUCCH resource of a target UE based on the method (PUCCH resource determination method) configured / indicated through broadcast signaling and receives a PUCCH on the corresponding PUCCH resource.

[0344] As described above with reference to Table 11 and Table 12, the methods (Method #5 to Method #7) are not limited to common PUCCH transmission, but can also be applied to dedicated PUCCH transmission likewise after receiving a dedicated PUCCH resource configuration. In addition, in these methods, CORESET #0 can be interchanged and interpreted / applied as other general CORESET, i.e., CORESET #p (p is 1, 2, etc.).

[0345] Therefore, even in dedicated PUCCH transmission, when the number of PUCCH resources in a PUCCH resource set exceeds 8, a PUCCH transmission resource can be determined by applying the same method as in common PUCCH transmission.

[0346] As an example, in order to improve network flexibility, a method preferred by the base station among the above-described methods (Method #1 to Method #7) can be selected / applied.

[0347] As an example, the base station can transmit information about configuration or indication related to at least one of the above-described methods (Method #1 to Method #7) to the UE based on at least one of broadcast signaling, dedicated RRC signaling, a MAC CE, and / or DCI.

[0348] In implementation aspects, the operations of the base station / UE according to the above-described embodiments (e.g., operations based on at least one of Method #1 to #7) can be processed by the apparatuses (e.g., the processors 110 and 210 in Figure 9 ). Figure 9

[0349] Further, the operations of the base station / UE according to the above-described embodiments (e.g., operations based on at least one of Method #1 to #7) can be stored in the form of instructions / programs (e.g., instructions or executable codes) for driving at least one processor (e.g., 110 and 210 in Figure 9 ) in the memory (e.g., 140 and 240 in Figure 9 ).

[0350] Hereinafter, the above-described embodiments will be described in detail with respect to operations of the UE and the base station. Figure 7 and Figure 8 The above-described embodiments will be described in detail with respect to operations of the UE and the base station. The methods to be described are merely distinguished for convenience, and it goes without saying that some components of any one method can be replaced with some components of another method or can be applied in combination with each other.

[0351] Figure 7 is a flowchart for describing a method performed by a user equipment (UE) according to an embodiment of the disclosure.

[0352] Referring to Figure 7 , a method performed by a UE in a wireless communication system according to an embodiment of the disclosure includes a step of receiving a PDCCH based on a CORESET (S710) and a step of transmitting a PUCCH (S720).

[0353] In S710, the UE receives a physical downlink control channel (PDCCH) from the base station based on a control resource set (CORESET).

[0354] ​The CORESET can be obtained based on puncturing the highest-numbered resource block among the resource blocks based on the frequency-domain size of the CORESET. That is, the puncturing can be performed when the channel bandwidth supported by the UE is narrowband. For example, the puncturing can be performed based on Table 8. As a specific example, among 24 resource blocks, the remaining 9 resource blocks except for 15 resource blocks based on the channel bandwidth can be punctured. The 9 resource blocks can be determined in descending order of RB index. In other words, the 9 resource blocks can include 9 resource blocks selected from the highest RB index.

[0355] Downlink control information (DCI) related to the PDCCH can include a PUCCH resource indicator (PRI) field. As an example, the number of bits of the PRI field can be 3. In this case, one of eight PUCCH resources can be indicated by the PRI field. However, when the number of PUCCH resources in the PUCCH resource set exceeds 8 (e.g., 16, 32, etc.), the PUCCH resource can not be determined only by the PRI field. In this case, the PUCCH resource can be determined based on the number of CCEs and the CCE index (Table 10 or Table 12). More details will be described below.

[0356] According to an embodiment, the number of resource blocks based on the channel bandwidth can be less than the number of resource blocks based on the frequency-domain size of the CORESET. As an example, the channel bandwidth associated with the CORESET can be less than 5 MHz.

[0357] According to an embodiment, the CORESET can be one of i) a first CORESET or ii) a second CORESET configured separately from the first CORESET. The first CORESET can be configured based on a master information block (MIB). That is, the first CORESET can be the above-described CORESET#0. The second CORESET can be the above-described CORESET#p.

[0358] In S720, the UE transmits a physical uplink control channel (PUCCH) based on a PUCCH resource.

[0359] According to an embodiment, the PUCCH resource can be determined based on i) a value of a PRI field (e.g., ), ii) a number of control channel elements (CCEs) in a CORESET (e.g., or ), and iii) an index of a first CCE among the CCEs for receiving the PDCCH (e.g., or ). The embodiment can be based on at least one of Method #1 to Method #7.

[0360] As an example, the CCEs in the CORESET can be obtained before puncturing. The implementation can be based on Method #1.

[0361] As an example, the PUCCH resource can be a common PUCCH resource or a dedicated PUCCH resource. Specifically, the PUCCH resource can be based on i) a common configuration or ii) a dedicated configuration.

[0362] According to the implementation, the method can further include a step of receiving the common configuration. Specifically, the UE can receive the common configuration from the base station.

[0363] As an example, the common configuration (e.g., PUCCH-ConfigCommon) can be received based on broadcast signaling (e.g., broadcast control channel (BCCH)). More specifically, the common configuration can be received based on a system information block (SIB) (e.g., SIB1). That is, the SIB includes the common configuration (e.g., SIB1 -> UplinkConfigCommon -> initialUplinkBWP (BWP-UplinkCommon) -> pucch-ConfigCommon).

[0364] As an example, the common configuration can include information for an index related to one of the PUCCH resource sets (e.g., pucch-ResourceCommon).

[0365] That is, referring to Table 9, the PUCCH resource set can be a PUCCH resource set before the dedicated PUCCH resource configuration. The index can be one of 0 to 15. The PUCCH resource can be one of 16 PUCCH resources within the index-based PUCCH resource set. The index-based PUCCH resource set / PUCCH resource can be used until the dedicated configuration is received.

[0366] According to the implementation, the method can further include a step of receiving the dedicated configuration. Specifically, the UE receives the dedicated configuration from the base station. The dedicated configuration (e.g., PUCCH-config) can include information (e.g., resourceSetToAddModList) for one or more PUCCH resource sets (e.g., up to 4 PUCCH resource sets). In this case, the PUCCH resource set among the one or more PUCCH resource sets can be determined based on the number of bits related to the uplink control information (UCI) (see Table 11). The number of bits related to the UCI can refer to the .

[0367] As an example, the PUCCH resource can be one of the PUCCH resources within the determined PUCCH resource set. The number of PUCCH resources can be greater than 8 (e.g., Table 12).

[0368] The above-described operations based on S710 and S720, the common configuration reception step, and the dedicated configuration reception step can be implemented by an apparatus in Figure 9 For example, the UE 200 can control the one or more transceivers 230 and / or the one or more memories 240 to perform operations based on S710 and S720, the common configuration reception step, and the dedicated configuration reception step.

[0369] Hereinafter, the above-described embodiments will be specifically described in terms of operations of a base station.

[0370] The following described S810 and S820, the configuration information transmission step, and the dedicated configuration transmission step correspond to S710 and S720, the configuration information reception step, and the dedicated configuration reception step described in Figure 7 By considering the correspondence, redundant descriptions are omitted. That is, the following specific description of the base station operations can be replaced with the description / embodiment of Figure 7

[0371] Figure 8 is a flowchart for describing a method performed by a base station according to another embodiment of the disclosure.

[0372] Referring to Figure 8 , a method performed by a base station according to another embodiment of the disclosure includes a step of transmitting a PDCCH based on a CORESET (S810) and a step of receiving a PUCCH (S820).

[0373] In S810, the base station transmits a physical downlink control channel (PDCCH) to a UE based on a control resource set (CORESET).

[0374] The CORESET is obtained based on puncturing a highest-numbered resource block among resource blocks according to a frequency domain size of the CORESET. That is, when a channel bandwidth supported by the UE is a narrow band, puncturing can be performed. For example, puncturing can be performed based on Table 9.

[0375] Downlink control information (DCI) related to the PDCCH can include a PUCCH resource indicator (PRI) field.

[0376] In S820, the base station receives a physical uplink control channel (PUCCH) from the UE based on the PUCCH resource.

[0377] ​According to embodiments, the method can further include a step of transmitting the common configuration. Specifically, the base station transmits the common configuration to the UE.

[0378] According to embodiments, the method can further include a step of transmitting the dedicated configuration. Specifically, the base station transmits the dedicated configuration to the UE.

[0379] The above-described operations based on S810 and S820, the common configuration transmission step, and the dedicated configuration transmission step can be implemented by an apparatus in Figure 9 For example, the base station 100 can control the one or more transceivers 130 and / or the one or more memories 140 to perform operations based on S810 and S820, the common configuration transmission step, and the dedicated configuration transmission step.

[0380] Embodiments of the present disclosure are described below with reference to Figure 9 An apparatus to which embodiments of the present disclosure are applicable (an apparatus that implements a method / operation according to embodiments of the present disclosure) is described below.

[0381] Figure 9 The configuration of the first apparatus and the second apparatus according to embodiments of the present disclosure is exemplified.

[0382] The first apparatus 100 can include a processor 110, an antenna unit 120, a transceiver 130, and a memory 140.

[0383] The processor 110 can perform baseband-related signal processing and include a higher layer processing unit 111 and a physical layer processing unit 115. The higher layer processing unit 111 can process operations of a MAC layer, an RRC layer, or a higher layer. The physical layer processing unit 115 can process operations of a PHY layer. For example, if the first apparatus 100 is a base station (BS) apparatus in BS-UE communication, the physical layer processing unit 115 can perform uplink reception signal processing, downlink transmission signal processing, etc. For example, if the first apparatus 100 is a first UE apparatus in inter-UE communication, the physical layer processing unit 115 can perform downlink reception signal processing, uplink transmission signal processing, sidelink transmission signal processing, etc. In addition to performing baseband-related signal processing, the processor 110 can control overall operations of the first apparatus 100.

[0384] The antenna unit 120 can include one or more physical antennas, and if the antenna unit 120 includes a plurality of antennas, MIMO transmission / reception is supported. The transceiver 130 can include a radio frequency (RF) transmitter and an RF receiver. The memory 140 can store information processed by the processor 110 and software, an operating system, and applications related to operations of the first apparatus 100. The memory 140 can further include components such as a buffer.

[0385] In the embodiments described in the disclosure, the processor 110 of the first device 100 can be configured to implement the operation of the BS in BS-UE communication (or the operation of the first UE device in inter-UE communication).

[0386] The second device 200 can include a processor 210, an antenna unit 220, a transceiver 230, and a memory 240.

[0387] The processor 210 can perform baseband-related signal processing and include a higher layer processing unit 211 and a physical layer processing unit 215. The higher layer processing unit 211 can process the operation of the MAC layer, the RRC layer, or a higher layer. The physical layer processing unit 215 can process the operation of the PHY layer. For example, if the second device 200 is a UE device in BS-UE communication, the physical layer processing unit 215 can perform downlink reception signal processing, uplink transmission signal processing, etc. For example, if the second device 200 is a second UE device in inter-UE communication, the physical layer processing unit 215 can perform downlink reception signal processing, uplink transmission signal processing, sidelink reception signal processing, etc. In addition to performing baseband-related signal processing, the processor 210 can control the overall operation of the second device 200.

[0388] The antenna unit 220 can include one or more physical antennas, and if the antenna unit 220 includes a plurality of antennas, MIMO transmission / reception is supported. The transceiver 230 can include an RF transmitter and an RF receiver. The memory 240 can store information processed by the processor 210 and software, an operating system, and applications related to the operation of the second device 200. The memory 240 can further include components such as a buffer.

[0389] In the embodiments described in the disclosure, the processor 210 of the second device 200 can be configured to implement the operation of the UE in BS-UE communication (or the operation of the second UE device in inter-UE communication).

[0390] The description of the BS and the UE in BS-UE communication (or the first UE device and the second UE device in inter-UE communication) in the examples of the disclosure can be equally applied to the operation of the first device 100 and the second device 200, and redundant descriptions are omitted.

[0391] In addition to LTE, NR, and 6G, the wireless communication technology implemented in the device 100 and the device 200 according to the disclosure can further include Narrow Band Internet of Things (NB-IoT) for low-power communication. For example, the NB-IoT technology can be an example of a Low-Power Wide-Area Network (LPWAN) technology, and can be implemented in standards such as LTE Cat NB1 and / or LTE Cat NB2. The NB-IoT technology is not limited to the above-mentioned names.

[0392] Additionally or alternatively, the wireless communication technology implemented in the apparatus 100 and the apparatus 200 according to the present disclosure can perform communication based on LTE-M technology. For example, the LTE-M technology can be an example of LPWAN technology, and can be referred to by various names such as enhanced machine type communication (eMTC). For example, the LTE-M technology can be implemented in at least one of various standards such as 1) LTE CAT0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-bandwidth limited), 5) LTE-MTC, 6) LTE machine type communication, and / or 7) LTE M. The LTE-M technology is not limited to the above names.

[0393] Additionally or alternatively, the wireless communication technology implemented in the apparatus 100 and the apparatus 200 according to the present disclosure can include at least one of ZigBee, Bluetooth, and low power wide area network (LPWAN) in consideration of low power communication, and is not limited to the above names. For example, the ZigBee technology can create a personal area network (PAN) related to small / low power digital communication based on various standards such as IEEE 802.15.4, and can be referred to by various names.

Claims

1. A method performed by a user equipment (UE) in a wireless communication system, the method comprising: receiving a physical downlink control channel (PDCCH) based on a control resource set (CORESET), wherein the CORESET is obtained based on puncturing a highest-numbered resource block among resource blocks according to a frequency domain size of the CORESET, wherein downlink control information (DCI) related to the PDCCH includes a PUCCH resource indicator (PRI) field; and transmitting a physical uplink control channel (PUCCH) based on a PUCCH resource, wherein the PUCCH resource is determined based on i) a value of the PRI field, ii) a number of control channel elements (CCEs) in the CORESET, and iii) an index of a first CCE among the CCEs used to receive the PDCCH, wherein the CCEs in the CORESET are obtained before the puncturing.

2. The method of claim 1, wherein, The PUCCH resource is based on i) a common configuration or ii) a dedicated configuration. 3.The method of claim 2, the method further comprising: receiving the common configuration, wherein the common configuration includes information for an index related to one of PUCCH resource sets.

4. The method of claim 3, wherein, The PUCCH resource is one of 16 PUCCH resources in a PUCCH resource set based on the index. 5.The method of claim 2, the method further comprising: receiving the dedicated configuration, wherein the dedicated configuration includes information for one or more PUCCH resource sets.

6. The method of claim 5, wherein, determining a PUCCH resource set among the one or more PUCCH resource sets based on a number of bits related to uplink control information (UCI).

7. The method of claim 6, wherein, The PUCCH resource is one of PUCCH resources in the determined PUCCH resource set.

8. The method of claim 7, wherein, The number of PUCCH resources is greater than 8.

9. The method of claim 1, wherein, A channel bandwidth related to the CORESET is less than 5 MHz.

10. The method of claim 9, wherein, The CORESET is one of i) a first CORESET or ii) a second CORESET configured separately from the first CORESET, and wherein the first CORESET is configured based on a master information block (MIB). 11.A user equipment (UE) operating in a wireless communication system, the UE comprising: one or more transceivers; one or more processors; and one or more memories connected to the one or more processors and storing instructions, wherein the instructions, based on being executed by the one or more processors, configure the one or more processors to perform all the steps of the method according to any one of claims 1 to 10. 12.An apparatus, the apparatus comprising: one or more memories; and one or more processors operatively connected to the one or more memories, wherein the one or more memories store instructions that, based on execution of the instructions by the one or more processors, configure the one or more processors to perform all the steps of the method according to any one of claims 1 to 10.

13. One or more non-transitory computer-readable media storing instructions, wherein, the instructions executable by one or more processors configure the one or more processors to perform all the steps of the method according to any one of claims 1 to 10.

14. A method performed by a base station in a wireless communication system, the method comprising: transmitting a physical downlink control channel (PDCCH) based on a control resource set (CORESET), wherein the CORESET is obtained based on puncturing a highest-numbered resource block among resource blocks according to a frequency domain size of the CORESET, wherein downlink control information (DCI) related to the PDCCH includes a PUCCH resource indicator (PRI) field; and receiving a PUCCH based on a physical uplink control channel (PUCCH) resource, wherein the PUCCH resource is determined based on i) a value of the PRI field, ii) a number of control channel elements (CCEs) in the CORESET, and iii) an index of a first CCE among the CCEs used to receive the PDCCH, wherein the CCEs in the CORESET are obtained prior to the puncturing.

15. A base station operating in a wireless communication system, the base station comprising: one or more transceivers; one or more processors; and one or more memories connected to the one or more processors and storing instructions, wherein the instructions, based on execution of the instructions by the one or more processors, configure the one or more processors to perform all the steps of the method according to claim 14.

Images