Method for transmission and reception of pdcch and apparatus therefor

Abstract

A method according to an embodiment of the present specification comprises the steps of: receiving an SS / PBCH block; and receiving the PDCCH on the basis of the CORESET. An offset is determined based on a configuration associated with the CORESET. The offset is defined from a minimum RB index of the CORESET to an RB index associated with the SS / PBCH block. Based on i) the channel bandwidth is 3 MHz and ii) the SCS of the SS / PBCH block is 15 kHz and iii) the SCS of the CORESET is 15 kHz: the offset is one of i) 0 and ii) 2, and the RB index is determined based on the first RB of the punctured SS / PBCH block.

Description

TECHNICAL FIELD

[0001] The disclosure relates to a method for transmitting and receiving of PDCCH and an apparatus thereof. BACKGROUND

[0002] Mobile communication systems have evolved to provide voice services while guaranteeing user mobility. However, in mobile communication systems, not only voice services but also data services have been expanded. Currently, due to explosive growth of traffic, resources are in shortage, and users need a faster service. Therefore, a more advanced mobile communication system is required.

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

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

[0005] If the maximum bandwidth is reduced (e.g., 3 MHz), the UE will not be able to receive the entire SSB. To prevent this, the SSB can be transmitted in a resource region that is punctured. In addition, Point A, which serves as a common reference point of a resource block grid, can be obtained based on the lowest subcarrier of the lowest resource block that overlaps with the SSB.

[0006] According to the reduced channel bandwidth, a synchronization raster arranged in a 600 kHz interval narrower than a regular interval of 1.2 MHz is newly supported / defined. The location of control resource set #0 (CORESET #0) in the frequency domain can be determined with respect to the SSB. As a specific example, the interval between the CORESET #0 and the SSB can be based on an offset and k SSB determined. Here, the offset indicates the number of resource blocks, and k SSB indicates the number of subcarriers. SUMMARY

[0007] TECHNICAL PROBLEM

[0008] According to existing technology, the offset is defined as the distance from the smallest RB index of CORESET #0 to the RB index associated with the SSB. Furthermore, the offset is indicated / determined as one of predefined / preconfigured values ​​(e.g., values ​​defined in a table). In this case, the subcarrier spacing (SCS) of the SSB and the subcarrier spacing of the CORESET can be the same (e.g., 15 kHz). Based on the newly introduced / supported synchronization grid, the position of the SSB, which serves as a reference for the frequency domain position of CORESET #0, has changed.

[0009] Therefore, when using the conventional definition and value of the offset directly, the position of CORESET #0 determined based on the corresponding offset may not be aligned with the subcarrier spacing.

[0010] The purpose of this disclosure is to propose a method for solving the above-mentioned problems.

[0011] The technical objectives to be achieved by this disclosure are not limited to those described above, and other technical objectives not described above can be clearly understood by those skilled in the art from the following description.

[0012] Technical solution

[0013] A method performed by a user equipment according to one embodiment of the present disclosure includes the following steps: receiving a synchronization signal / physical broadcast channel (SS / PBCH) block based on a synchronization grid for channel bandwidth; and receiving a physical downlink control channel (PDCCH) based on a control resource set (CORESET).

[0014] The offset is determined based on the configuration associated with CORESET.

[0015] The offset is defined from the smallest resource block (RB) index of CORESET to the RB index associated with the SS / PBCH block.

[0016] Based on i) a channel bandwidth of 3 MHz, ii) a subcarrier spacing (SCS) of 15 kHz for the SS / PBCH block, and iii) a CORESET SCS of 15 kHz: The offset is one of i) 0 and ii) 2, and the RB index is determined based on the first RB of the punched SS / PBCH block.

[0017] The RB index can be the smallest RB index of a common resource block that overlaps with the first RB of the punched SS / PBCH block.

[0018] i) CORESET related configuration and ii) k SSBIt can be based on the Master Information Block (MIB) indication associated with the SS / PBCH block.

[0019] k SSB It can be the subcarrier offset from subcarrier 0 of the common resource block to the lowest numbered subcarrier of the punctured SS / PBCH block.

[0020] Based on the offset being 0, k SSB It can be 8. Based on an offset of 2, k SSB It can be 4.

[0021] The offset can be defined relative to the CORESET's SCS.

[0022] Synchronization grids can be related to the operating frequency band.

[0023] For a channel bandwidth of 3 MHz, the operating frequency band can be n26, n28, n31, n72, n85, n100, or n106.

[0024] The frequency position based on the synchronization grid can be determined based on the following equation.

[0025] [Equation]

[0026] Frequency position = N × 600 kHz + M × 50 kHz + 300 kHz Where N is an integer greater than or equal to 1, and M can be 1, 3 or 5.

[0027] Within the operating frequency band, frequencies based on the channel grid can be defined at 100 kHz intervals.

[0028] The number of RBs based on a 3 MHz channel bandwidth can be 15.

[0029] After punching, the SS / PBCH block can be based on 12 RBs.

[0030] The number of RBs can be determined based on the configuration associated with CORESET, and the number of RBs can be 12 or 24.

[0031] Since the number of RBs is 24, CORESET can include 15 RBs obtained by punching holes in 9 of the 24 RBs.

[0032] A user equipment (UE) 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.

[0033] The instructions are based on all the steps of configuring one or more processors to perform any of the methods in the method, which are executed by one or more processors.

[0034] An apparatus according to another embodiment of this disclosure includes one or more memories and one or more processors operatively connected to the memories. The memories are configured to store instructions executable by the processors, and the instructions are configured to allow the processors to perform all steps of any of the methods described.

[0035] 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 described.

[0036] A method performed by a base station according to another embodiment of the present disclosure includes the following steps: transmitting a synchronization signal / physical broadcast channel (SS / PBCH) block based on a synchronization grid for channel bandwidth; and transmitting a physical downlink control channel (PDCCH) based on a control resource set (CORESET).

[0037] The offset is determined based on the configuration associated with CORESET.

[0038] The offset is defined from the smallest resource block (RB) index of CORESET to the RB index associated with the SS / PBCH block.

[0039] Based on i) a channel bandwidth of 3 MHz, ii) a subcarrier spacing (SCS) of 15 kHz for the SS / PBCH block, and iii) a CORESET SCS of 15 kHz: The offset is one of i) 0 and ii) 2, and the RB index is determined based on the first RB of the punched SS / PBCH block.

[0040] A base station 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 storing instructions.

[0041] The instructions are based on all steps of configuring one or more processors to perform the method, which are executed by one or more processors.

[0042] Beneficial effects

[0043] According to embodiments of this disclosure, the position of CORESET #0 based on the SSB identifier can be determined as a valid position from the perspective of subcarrier spacing. Therefore, the PDCCH reception performance based on CORESET #0 in narrowband can be improved. The UE can stably receive system information (e.g., SIB1) based on the corresponding PDCCH.

[0044] Furthermore, by addressing issues that may arise when supporting narrowband UE / spectrum scenarios, this disclosure can help expand the use case scenarios for NR systems.

[0045] The effects that can be achieved using this disclosure are not limited to those described above by way of example only, and those skilled in the art to which this disclosure pertains will more clearly understand other effects and advantages of this disclosure based on the following description. Attached Figure Description

[0046] FIG. 1 An example of a frame structure in an NR system is shown.

[0047] FIG. 2 An example of a resource grid in NR is shown.

[0048] FIG. 3 The physical channels and general signal transmissions used in the 3GPP system are shown.

[0049] FIG. 4 This is a diagram illustrating the SSB structure to which the method proposed in this disclosure applies.

[0050] FIG. 5 An SSB transmission using the method proposed in this disclosure is illustrated.

[0051] FIG. 6 This is a flowchart illustrating the reception of DL signals / channels during the initial access process to which the method according to embodiments of this disclosure is applicable.

[0052] FIG. 7 An example of the time-frequency structure of an SSB according to an embodiment of the present disclosure is shown.

[0053] FIG. 8 An example of a frequency resource domain for PBCH transmission / reception according to an embodiment of the present disclosure is shown.

[0054] FIG. 9 An example of a frequency resource domain for PBCH transmission / reception according to another embodiment of this disclosure is shown.

[0055] FIG. 10 An example of a synchronization grid according to an embodiment of the present disclosure is illustrated.

[0056] FIG. 11Another example of a synchronization grid according to an embodiment of the present disclosure is illustrated.

[0057] FIG. 12 Point A is illustrated according to the existing method.

[0058] FIG. 13 Point A is illustrated according to an embodiment of the present disclosure.

[0059] FIG. 14 CORESET #0 is illustrated according to one embodiment of this disclosure.

[0060] FIG. 15 An example of a channel grid and a synchronization grid based on an embodiment of the present disclosure is illustrated.

[0061] FIG. 16 Another example of a channel grid and a synchronization grid based on an embodiment of the present disclosure is illustrated.

[0062] FIG. 17 Another example of a channel grid and a synchronization grid based on an embodiment of the present disclosure is illustrated.

[0063] FIG. 18 An example of a valid offset value is shown among the offset values ​​between CORESET #0 and the synchronization grid based on an embodiment of this disclosure.

[0064] FIG. 19 An example of an effective offset value between CORESET #0 and a synchronization grid in a specific frequency band is illustrated based on an embodiment of this disclosure.

[0065] FIG. 20 Another example is illustrated of the effective offset value between CORESET #0 and the synchronization grid in a specific frequency band, based on an embodiment of this disclosure.

[0066] FIG. 21 This is a flowchart illustrating a method performed by a user equipment according to an embodiment of the present disclosure.

[0067] FIG. 22 This is a flowchart illustrating a method performed by a base station according to another embodiment of the present disclosure.

[0068] FIG. 23 The configurations of the first and second devices according to embodiments of the present disclosure are illustrated. Detailed Implementation

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

[0070] The following technologies can be used in various radio access systems, including CDMA, FDMA, TDMA, OFDMA, SC-FDMA, etc. CDMA can be implemented as radio technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented as radio technologies such as Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), and Enhanced Data Rate for GSM Evolution (EDGE). OFDMA can be implemented as radio technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, and Evolved UTRA (E-UTRA). UTRA is part of the Universal Mobile Telecommunications System (UMTS). 3GPP Long Term Evolution (LTE) is part of Evolved UMTS (E-UMTS) using E-UTRA, and LTE-Advanced (A) / LTE-A pro are evolved versions of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an evolution of 3GPP LTE / LTE-A / LTE-Apro.

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

[0072] The background technology, terminology, omissions, etc., used in describing this disclosure may be referenced to the content disclosed in standard documents previously published. For example, the following documents may be consulted.

[0073] 3GPP NR

[0074] - 3GPP TS 38.211: Physical Channels and Modulation

[0075] - 3GPP TS 38.212: Multiplexing and Channel Coding

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

[0077] - 3GPP TS 38.214: Physical Layer Procedures for Data

[0078] - 3GPP TS 38.215: Physical Layer Measurements

[0079] - 3GPP TS 38.300: General Description of NR and NG-RAN

[0080] - 3GPP TS 38.304: User Equipment (UE) Procedures in Idle Mode and RRC Inactive State

[0081] - 3GPP TS 38.321: Media Access Control (MAC) Protocol

[0082] - 3GPP TS 38.322: Radio Link Control (RLC) Protocol

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

[0084] - 3GPP TS 38.331: Radio Resource Control (RRC) Protocol

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

[0086] - 3GPP TS 37.340: Multiple Connectivity; General Description

[0087] - 3GPP TS 23.287: Application layer support for V2X services; functional architecture and information flow

[0088] - 3GPP TS 23.501: System Architecture for 5G Systems

[0089] - 3GPP TS 23.502: Process for 5G Systems

[0090] - 3GPP TS 23.503: Policy and Charging Control Framework for 5G Systems; Phase 2

[0091] - 3GPP TS 24.501: Non-Access Stratum (NAS) Protocol for 5G Systems (5GS); Phase 3

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

[0093] - 3GPP TS 24.526: User Equipment (UE) Policy for 5G Systems (5GS); Phase 3

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

[0095] New RAT systems, including NR, employ OFDM or similar transmission schemes. These new RAT systems can follow different OFDM parameters than LTE. Alternatively, they can retain the traditional LTE / LTE-A parameter sets (numerology) or have a larger system bandwidth (e.g., 100 MHz). Alternatively, a single cell can support multiple parameter sets. In other words, user equipment (UEs) operating with different parameter sets can coexist within a single cell.

[0096] The parameter set corresponds to a subcarrier spacing in the frequency domain. Different parameter sets can be defined by scaling the reference subcarrier spacing to an integer N.

[0097] New RAT (NR) numerologies and frame structure

[0098] In NR systems, multiple parameter sets can be supported. These parameter sets can be defined by subcarrier spacing and cyclic prefix (CP) overhead. The spacing between multiple subcarriers can be derived by scaling the basic subcarrier spacing to an integer N (or µ). Furthermore, although it is assumed that very low subcarrier spacings will not be used at very high subcarrier frequencies, the parameter set to be used can be selected band-independently.

[0099] Furthermore, the NR system can support various frame structures based on multiple parameter sets.

[0100] The following section describes the set of orthogonal frequency division multiplexing (OFDM) parameters and frame structures that can be considered in NR systems.

[0101] Multiple OFDM parameter sets supported in the NR system can be defined as shown in Table 1. The μ and cyclic prefix for the bandwidth portion are obtained from the RRC parameters provided by the base station.

[0102] [Table 1]

[0103] NR supports multiple parameter sets (or subcarrier spacing (SCS)) to support a variety of 5G services. For example, when the SCS is 15 kHz, it supports wide areas in traditional cellular bands; and when the SCS is 30 kHz / 60 kHz, it supports dense urban areas, lower latency, and wider carrier bandwidth; and when the SCS is greater than 60 kHz, it supports bandwidths greater than 24.25 GHz to overcome phase noise.

[0104] The NR band is defined as two types of frequency ranges: FR1 and FR2. FR1 can represent the range below 6 GHz, while FR2 can represent the range above 6 GHz, and can also refer to millimeter waves (mmW).

[0105] Table 2 below shows an example of the definition of the NR band.

[0106] [Table 2]

[0107] Regarding the frame structure in the NR system, the size of each field in the time domain is represented as a time unit. Multiples of. In this case... and N f =4096. DL and UL transmissions are configured to have The radio frame consists of ten subframes, each with [specific characteristics]. In this case, there can be a set of UL frames and a set of DL frames.

[0108] The uplink frame number i used for transmissions from a user equipment (UE) should be before the start of the corresponding downlink frame for the corresponding UE. start.

[0109] For parameter set µ, within the subframe, according to The time slots are numbered in ascending order and within the radio frame according to... The time slots are numbered in ascending order. A time slot consists of... Composed of consecutive OFDM symbols, and The time slot is determined by the parameter set and time slot configuration used. (Time slot in subframe) The start of OFDM symbols in the same subframe The beginnings are aligned in time.

[0110] Not all UEs can transmit and receive simultaneously, which means that not all OFDM symbols in the downlink or uplink slots are available.

[0111] Table 3 shows the number of OFDM symbols in each time slot during normal CP. Number of time slots per radio frame and the number of time slots in each subframe Table 4 shows the number of OFDM symbols in each time slot, the number of time slots in each radio frame, and the number of time slots in each subframe in the extended CP.

[0112] [Table 3]

[0113] [Table 4]

[0114] FIG. 1 An example of a frame structure in an NR system is shown.FIG. 1 This disclosure is for illustrative purposes only and does not limit the scope of this disclosure.

[0115] In Table 4, with µ = 2, as an example, the subcarrier spacing (SCS) is 60 kHz. Referring to Table 3, a subframe (or frame) can include four time slots, and for example, as shown... FIG. 1 As shown, a subframe = {1, 2, 4} time slots, and the number of time slots that a subframe can include can be defined as shown in Table 3.

[0116] Furthermore, a mini-slot can consist of 2, 4, or 7 symbols, or it can consist of more or fewer symbols.

[0117] Regarding physical resources in an NR system, one can consider antenna ports, resource grids, resource elements, resource blocks, carrier components, etc.

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

[0119] FIG. 2 An example of a resource grid supported in NR is shown.

[0120] Reference FIG. 2 For each subcarrier spacing configuration and carrier, the following is defined: Subcarriers and A resource grid of OFDM symbols, wherein Instructed by RRC signaling from BS. It can be changed between uplink and downlink, or configured with subcarrier spacing. Change.

[0121] For parameter sets in the resource grid Each element of the antenna port p is called a resource element, and is indexed by a pair. Uniquely identified, among which It is an index in the frequency domain, and This refers to the position of the symbol within the subframe. Index pair Used to refer to resource elements in a time slot, where .

[0122] For parameter set and resource elements of antenna port p Corresponding to complex value When there is no risk of confusion or when no specific antenna port or parameter set is specified, index p can be discarded. Therefore, complex values ​​can be or Furthermore, physical resource blocks are defined in the frequency domain. A series of consecutive subcarriers.

[0123] Considering that the UE may not be able to support the wide bandwidth that the NR system needs to support at once, the UE can be configured to operate in a portion of the cell's frequency bandwidth (hereinafter referred to as the Bandwidth Part (BWP)).

[0124] The resource blocks of an NR system include physical resource blocks defined in the bandwidth section, and configurations for subcarrier spacing. Public resource blocks numbered from 0 upwards in the frequency domain.

[0125] Point A is used as a common reference point for the resource block grid and can be obtained as follows.

[0126] - For the PCell downlink, offsetToPointA represents the frequency offset between point A and the lowest subcarrier of the lowest resource block that overlaps with the SS / PBCH block used by the UE for initial cell selection, and is expressed in units of resource blocks. It is assumed that the subcarrier spacing for FR1 is 15 kHz and the subcarrier spacing for FR2 is 60 kHz. - absoluteFrequencyPointA represents the frequency location of point A, expressed as the absolute radio frequency channel number (ARFCN); configuration of subcarrier spacing In the frequency domain, public resource blocks are numbered starting from 0 and moving upwards.

[0127] configuration of subcarrier spacing The center of subcarrier 0 of common resource block 0 coincides with "point A". Common resource block numbering in the frequency domain. The resource elements (k, l) configured for subcarrier spacing µ can be given by Equation 1 below.

[0128] [Formula 1]

[0129] Here, k can be defined relative to point A, such that k=0 corresponds to a subcarrier centered at point A. The physical resource block is defined within the bandwidth portion (BWP) and ranges from 0 to... Number, where i is the BWP number. BWP Physical resource blocks in With public resource blocks The relationship between them can be given by Equation 2 below.

[0130] [Equation 2]

[0131] here, It can be a public resource block, where BWP starts relative to public resource block 0.

[0132] Bandwidth Part (BWP)

[0133] In NR systems, each carrier can support up to 400 MHz. If a UE operating on such a wideband carrier always operates with the radio frequency (RF) module enabled for all carriers, the UE's battery consumption may increase. Alternatively, considering several use cases operating on a wideband carrier (e.g., eMBB, URLLC, mMTC, V2X, etc.), different sets of parameters (e.g., subcarrier spacing) can be supported for each frequency band within the corresponding carrier. Alternatively, each UE's capability for the maximum bandwidth may differ. With this in mind, the base station (BS) can instruct the UE to operate only within a portion of the wideband carrier's bandwidth, rather than the entire bandwidth, and this portion of bandwidth is defined as the bandwidth portion (BWP). In the frequency domain, the BWP is a subset of adjacent common resource blocks defined for the parameter set µi within the bandwidth portion i on the carrier, and a set of parameters (e.g., subcarrier spacing, CP length, slot / mini-slot duration) can be configured.

[0134] The BS can configure one or more BWPs within a carrier configured for the UE. Alternatively, if UEs are concentrated on a specific BWP, some UEs can be transferred to different BWPs for load balancing. Alternatively, two BWPs can be configured in the same time slot, excluding some central spectrum of the entire bandwidth, taking into account frequency domain inter-cell interference cancellation between adjacent cells. That is, the BS can configure at least one DL / UL BWP for a UE associated with a broadband carrier, activate at least one of the configured DL / UL BWPs at a specific time (via L1 signaling (which is a physical layer control signal), MAC control element (CE) (which is a MAC layer control signal), or RRC signaling, etc.), and instruct the UE to switch to other configured DL / UL BWPs (via 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 the active DL / UL BWP. When the UE is in the initial access procedure or has not yet established an RRC connection, the UE may not be able to receive configuration for the DL / UL BWP. In this case, the DL / UL BWP assumed by the UE is defined as the initial active DL / UL BWP.

[0135] Physical channels and general signal transmission

[0136] FIG. 3This illustrates the physical channels and general signal transmissions used in a 3GPP system. In a wireless communication system, the UE receives information from the eNB via the downlink (DL) and transmits information to the eNB via the uplink (UL). The information transmitted and received by the eNB and UE includes data and various control information, and various physical channels exist depending on the type / purpose of the information transmitted and received by the eNB and UE.

[0137] When the UE powers on or enters a new cell, it performs an initial cell search operation, such as synchronizing with the eNB (S301). To do this, the UE can receive the primary synchronization signal (PSS) and secondary synchronization signal (SSS) from the eNB, synchronize with the eNB, and obtain information such as the cell ID. Subsequently, the UE can receive the physical broadcast channel (PBCH) from the eNB and obtain intra-cell broadcast information. During the initial cell search step, the UE receives a downlink reference signal (DL RS) to check the downlink channel state.

[0138] After completing the initial cell search, the UE receives the Physical Downlink Control Channel (PDCCH) and the Physical Downlink Shared Channel (PDSCH) based on the information loaded on the PDCCH to obtain more specific system information S302.

[0139] When no radio resources are available for initial access to the eNB or for signal transmission, the UE can perform random access procedures (RACH) S303 to S306 with the eNB. For this purpose, the UE can transmit a specific sequence S303 and S305 in the form of a preamble via the Physical Random Access Channel (PRACH), and receive a response message (Random Access Response (RAR) message) for that preamble via the PDCCH and the corresponding PDSCH. In the case of a contention-based RACH, a contention resolution procedure S306 can also be performed.

[0140] The UE that performs the above procedure can then perform PDCCH / PDSCH reception (S307) and Physical Uplink Shared Channel (PUSCH) / Physical Uplink Control Channel (PUCCH) transmission (S308) in the same manner as the general uplink / downlink signal transmission procedure. Specifically, the UE can receive downlink control information (DCI) via PDCCH.

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

[0142] The PDCCH can be used to schedule DL transmissions on the PDSCH and UL transmissions on the PUSCH. The DCI on the PDCCH includes downlink assignment (i.e., DL grant) related to the downlink shared channel, and at least includes modulation and coding scheme and resource allocation information; or uplink grant (UL grant) related to the uplink shared channel, and includes modulation and coding scheme and resource allocation information. The DCI has different formats depending on its purpose.

[0143] Control information sent by the UE to the eNB via the uplink or received by the UE from the eNB may include downlink / uplink ACK / NACK signals, channel quality indicator (CQI), precoding matrix index (PMI), rank indicator (RI), etc. The UE can send control information such as CQI / PMI / RI via PUSCH and / or PUCCH.

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

[0145] FIG. 4 An SSB structure in which the methods proposed in this disclosure can be applied is shown. The UE can perform cell search, system information acquisition, beam alignment for initial access, DL measurements, etc., based on the SSB. The SSB can be used interchangeably with the Synchronization Signal / Physical Broadcast Channel (SS / PBCH) block.

[0146] Reference FIG. 4 The SSB includes the PSS, SSS, and PBCH. The SSB consists of four consecutive OFDM symbols, on which the PSS, PBCH, SSS / PBCH, or PBCH are transmitted. The PSS and SSS each consist of one OFDM symbol and 127 subcarriers, and the PBCH consists of three OFDM symbols and 576 subcarriers.

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

[0148] FIG. 5 An SSB transmission to which the methods proposed in this disclosure can be applied is shown.

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

[0150] - For frequency ranges up to 3 GHz, L = 4

[0151] - For the frequency range of 3 GHz to 6 GHz, L = 8

[0152] - For the frequency range of 6 GHz to 52.6 GHz, L = 64

[0153] The temporal position of an SSB candidate within an SSB burst set can be defined as follows: The temporal position of an SSB candidate is indexed from 0 to L-1 based on the temporal order within the SSB burst set (i.e., half-frame) (SSB index).

[0154] Multiple SSBs can be transmitted within the carrier's frequency span. The physical layer cell identifiers of these SSBs do not need to be unique, and other SSBs can have different physical layer cell identifiers.

[0155] The UE can obtain DL synchronization by detecting SSBs. The UE can identify the structure of the SSB burst set based on the detected SSB (time) index, thereby detecting symbol / slot / half-frame boundaries. System Frame Number (SFN) information and half-frame indication information can be used to identify the frame / half-frame number to which the detected SSB belongs.

[0156] The foregoing can be combined and applied to the methods described below in this disclosure, or can be supplemented to clarify the technical features of the methods described in this disclosure. The methods described below are distinguished only for ease of explanation. Therefore, it is obvious that any part of the configuration of one method can be replaced or combined with a part of the configuration of another method.

[0157] Technical terms used in the present disclosure

[0158] UE: User Equipment

[0159] SSB: Synchronization Signal Block

[0160] MIB: Master Information Block

[0161] RMSI: Residual Minimum System Information

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

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

[0164] BW: Bandwidth

[0165] BWP: Bandwidth section

[0166] RNTI: Temporary Identifier for Radio Networks

[0167] CRC: Cyclic Redundancy Check

[0168] SIB: System Information Block

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

[0170] CORESET (Control Resource Set): The time / frequency resources for the NR UE to attempt candidate PDCCH decoding.

[0171] CORESET #0: CORESET for the Type0-PDCCH CSS set of NR devices (configured in MIB)

[0172] Type0-PDCCH CSS set: Search space set, where the NR UE monitors the set of PDCCH candidates for DCI format with CRC scrambled by SI-RNTI.

[0173] MO: PDCCH monitoring timing for Type 0-PDCCH CSS set

[0174] SIB1-R: (Additional) SIB1 for NR devices with reduced capabilities. It may be limited when generated using a different TB than SIB1 and transmitted on a separate PDSCH.

[0175] CORESET #0-R: CORESET #0 for NR devices with reduced capabilities.

[0176] Type 0-PDCCH-R CSS set: Search space set, in which a capability-reduced (Redcap) UE monitors a set of PDCCH candidates for DCI format with CRC scrambled by SI-RNTI.

[0177] MO-R: PDCCH monitoring timing for the Type0-PDCCH CSS set.

[0178] Cell-limited SSB (CD-SSB): An SSB in the NR SSB that includes RMSI scheduling information.

[0179] Non-Cell-Defined SSB (Non-CD-SSB): An SSB deployed on the NR synchronization grid but which does not include the RMSI scheduling information of the corresponding cell to be measured. However, the SSB may include information notifying the location of the cell-defined SSB.

[0180] SCS: Subcarrier Spacing

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

[0182] Camp on: "Camp on" refers to the state in which a UE remains on a cell and is ready to initiate a potential dedicated service or receive an ongoing broadcast service.

[0183] TB: Transport Block

[0184] RSA (Redcap Standalone): A cell that only supports Redcap devices or services.

[0185] SIB1(-R)-PDSCH: PDSCH sends SIB1(-R)

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

[0187] SIB1(-R)-PDCCH: PDCCH sends SIB1(-R)-DCI

[0188] FDRA: Frequency Domain Resource Allocation

[0189] TDRA: Time Domain Resource Allocation

[0190] RA: Random Access

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

[0192] MSGB: Response to MSGA during the 2-step random access process. MSGB may include responses for contention resolution, backoff instructions, and avoidance instructions.

[0193] RO-N: RACH timing (RO) for normal UE 4-step RACH and 2-step RACH (if configured).

[0194] RO-N1, RO-N2: If a separate RO is configured for a normal UE 2-step RACH, it is divided into RO-N1 (4 steps) and RO-N2 (2 steps).

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

[0196] RO-R1, RO-R2: If a separate RO is configured for Redcap UE 2-step RACH, it is divided into RO-R1 (4 steps) and RO-R2 (2 steps).

[0197] PG-R: MsgA preamble group for RedCap UE

[0198] RAR: Random Access Response

[0199] RAR window: A time window used to monitor RA response.

[0200] FH: Frequency jump

[0201] iBWP: Initial BWP

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

[0203] iBWP-DL(-UL)-R: (Standalone) DL(UL) BWP for RedCap

[0204] CS: Circular shift

[0205] NB: Narrowband

[0206] TO: Traffic Offloading

[0207] mMTC; Massive Machine Type Communication

[0208] eMBB: Enhanced Mobile Broadband Communication

[0209] URLLC: Ultra-Reliable Low-Latency Communication

[0210] RedCap: Reduced Capability

[0211] eRedCap: Enhanced RedCap

[0212] FDD: Frequency Division Duplex

[0213] HD-FDD: Half-duplex FDD

[0214] DRX: Discontinuous Receiver

[0215] RRC: Radio Resource Control

[0216] RRM: Radio Resource Management

[0217] IWSN: Industrial Wireless Sensor Network

[0218] LPWA: Low Power Wide Area Network

[0219] RB: Resource Block

[0220] CCE: Control Channel Unit

[0221] AL: Aggregation Level

[0222] PRG: Physical Resource Block Group

[0223] DFT-s-OFDM: DFT spread spectrum OFDM

[0224] PBCH: Physical Broadcast Channel

[0225] A-PBCH: Additional PBCH

[0226] BD: Blind Testing

[0227] EPRE: Energy per RE

[0228] SNR: Signal-to-noise ratio

[0229] TDM: Time Division Multiplexing

[0230] DMRS: Demodulation Reference Signal

[0231] TDD: Time Division Duplex

[0232] In this disclosure, “()” can be interpreted as either excluding the content within the parentheses or including the content within the parentheses.

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

[0234] Compared to previous generation wireless communication systems (such as LTE and GSM), 5G wireless communication systems are characterized by their efficient support for use cases such as mMTC, eMBB, and URLLC. Due to these advantages, 5G wireless communication systems are expected to create new use cases and gradually replace previous generation wireless communication systems for a wide range of applications.

[0235] The enhanced low latency, high reliability, and massive connectivity features of 5G wireless communication systems can be applied to use cases that were previously supported in narrowband (NB) (hereinafter referred to as NB use cases), as shown below.

[0236] [Example of a narrowband-based use case (NB use case)]

[0237] i) Railway mobile communication

[0238] ii) Utility / Infrastructure Network

[0239] iii) Public safety mobile communications

[0240] These NB use cases have previously been supported using previous-generation wireless communication systems in frequency bands below 1 GHz with a bandwidth of approximately 3 MHz. Similarly, when 5G wireless communication systems are intended to support NB use cases, these cases can be supported, for example, in the same frequency band (below 1 GHz) with a similar frequency bandwidth (approximately 3 MHz and below 5 MHz). However, since the minimum channel bandwidth (BW) supported by the current 5G NR standard is 5 MHz, channel bandwidths below 5 MHz should be supported first.

[0241] [Example of 5G NR bands supported for NB use cases (TS38.101-1)]

[0242] NB use cases can be supported in the following NR operating bands defined in NR standard TS38.101-1.

[0243] [Table 5]

[0244] Table 5 shows the UL / DL operating bands defined by the NR operating band in frequency range 1 FR1.

[0245] [Example of channel BW definition for NB use cases supporting channels smaller than 5 MHz]

[0246] Table 6 shows the maximum number of configurable resource blocks (N) for each UE channel BW. RBExample of ). According to Table 6, in order to support NB use cases based on 5G NR, a 3 MHz UE channel BW is defined and the maximum number of configurable resource blocks (N) in the 3 MHz UE channel BW is defined. RB The value is defined as 15, and in this case, the resource utilization rate (or RU) (%) is defined. RU can be defined as follows.

[0247] [Table 6]

[0248] Furthermore, for the newly defined 3 MHz UE channel BW, considering interference between adjacent channels and resource utilization, other N values ​​shown in Table 7 below can be defined and used. RB value.

[0249] [Table 7]

[0250] For example, channel BW / N RB The same value can be applied to DL and UL. For example, channel BW / N RB DL and UL can be configured / supported separately / independently. The method described in the second example can be applied in the following situations. This method can be applied when the following conditions are intended: when N is determined... RB When the value is set, additional DFT precoding is applied only on UL, while considering interference between adjacent channels and resource utilization, supporting the maximum channel BW / N between DL and UL. RB value.

[0251] FIG. 6 This is a flowchart illustrating the reception of DL signals / channels during the initial access process to which the method according to embodiments of this disclosure is applicable. (Refer to...) FIG. 6 During the initial access process, a 5G NR UE can receive DL signals / channels in the order of S610 to S640. Specific details regarding the initial access process are as follows... FIG. 3 to FIG. 5 The descriptions in the text are the same, so repeated descriptions will be omitted.

[0252] Existing NR UEs can receive CORESET #0 information via the Master Information Block (MIB) transmitted on the PBCH, and receive the initial DL signal / channel via the CORESET #0 band during initial access. However, considering the channel bandwidths (BW) shown in Tables 6 and 7 and the CORESET #0 bandwidth supported in the NR standard, the operation according to the above conventional method may be inefficient.

[0253] In view of this situation, this disclosure proposes a method for effectively supporting NR DL control channels for initial access in narrowband.

[0254] In this disclosure, narrowband and NB can be interpreted / applied interchangeably. Furthermore, channel BW, N... RB The allowed / supported transfer BW, (punched / non-punched) PBCH BW, and maximum transfer BW can be interpreted / applied interchangeably.

[0255] In this disclosure, in addition to system information including SIB1 and MIB, broadcast signaling also includes a signaling method that uses PBCH payload, PBCH scrambling sequence and PBCH DMRS sequence initialization information generated in the PHY layer.

[0256] In this disclosure, broadcast signaling may include different definitions or interpretations of existing bits / fields. For example, if it is no longer necessary to signal some of the signaling methods based on the MIB used for existing broadcast signaling, the PBCH payload generated in the PHY layer in addition to the MIB, and the PBCH scrambling sequence and PBCH DMRS sequence initialization information, then broadcast signaling may include newly defined bits / fields and signaling the corresponding bits / fields. For example, broadcast signaling may include the signaling of bits / fields in the MIB... subCarrierSpacingCommon (1 bit, {15kHz, 30kHz}) is used for other 1-bit broadcast signaling purposes in narrowband bands that only support 15kHz SCS. If it is possible to schedule DCI transmissions for PBCH / SIB1 / SIB1 for new UEs without affecting legacy UEs through frequency bands, dedicated spectrum, dedicated synchronization grids, etc., the aforementioned broadcast signaling may include signaling methods performed by redefining and differently interpreting bits / fields already used for broadcast signaling purposes in existing legacy UEs.

[0257] [Methods for transmitting PBCH in narrowband]

[0258] To support NR DL broadcast signal reception in a narrowband with a bandwidth of 5 MHz, a subset of PBCH transport resource blocks (RBs) can be transmitted. In this disclosure, "transmitting a subset of PBCH transport RBs" can mean "transmitting the PBCH based on a subset of the RBs allocated to the PBCH".

[0259] In this disclosure, the PBCH transmission RB can refer to the time-frequency structure of the SS / PBCH (e.g., see [reference]). FIG. 7 The RBs associated with or allocated to the PBCH in the PBCH. In this disclosure, "PBCH transport RB subset" may mean the RB subset associated with or allocated to the PBCH.

[0260] In this disclosure, the PSS / SSS transmission RB can refer to the time-frequency structure of the SS / PBCH (e.g., see [reference]). FIG. 7RBs associated with PSS / SSS or RBs assigned to PSS / SSS.

[0261] In this disclosure, a resource block (RB) may be interpreted / replaced as a physical resource block (PRB) or a common resource block (CRB).

[0262] FIG. 7 An example of the time-frequency structure of an SSB according to an embodiment of this disclosure is shown. For example, the time-frequency structure of an SSB may be defined in the NR standard.

[0263] Specifically, FIG. 7 It shows the results for each domain in FIG. 4 The time-frequency structure includes the number of REs / RBs. (Refer to...) FIG. 7 The frequency domain (bandwidth) used for PSS and SSS consists of 127 resource elements (REs). The frequency domain (bandwidth) of PBCH consists of 20 resource blocks (RBs) (=144 REs) or 4 RBs (=48 REs).

[0264] For example, a base station may need to exclude or puncture at least five PBCHs from a PBCH consisting of 20 PRBs to transmit RBs, and transmit the remaining RBs in order to support the specification of N. RB =PBCH transmission / reception in a 3MHz channel BW of 15 PRBs. That is, the base station can transmit a subset of up to 15 of the total 20 PBCH transmission RBs. In addition, all PSS / SSS transmission RBs can be transmitted for the same level of synchronization and measurement performance as existing NR UEs. In this case, the minimum PBCH transmission RBs can be 12 RBs including PSS / SSS.

[0265] In this disclosure, "punctured" PBCH or a subset of PBCH transport RBs refers to the PBCH actually transmitted after the puncturing application when a subset of the PBCH transport RBs is punctured and transmitted. Therefore, "punctured PBCH" and "subset of PBCH transport RBs" can be interpreted / used interchangeably.

[0266] As specified in the example above, N RB In a 3MHz channel BW with 15 PRBs, the BS / UE can configure a PBCH transmission RB subset using 12 to 15 PRBs. The methods for configuring the PBCH transmission RB subset using 12 and 15 PRBs are described in detail below.

[0267] [Example #P1]

[0268] One approach could be to use 12 PRBs, including PSS / SSS, to configure the PBCH to transmit a subset of RBs.

[0269] Example #P1 is the case where only 12 PRBs, including PSS / SSS, are used to configure a subset of RBs for PBCH transport. That is, a subset of RBs for PBCH transport can be configured using the minimum subset of RBs that includes all PSS / SSS (e.g., FIG. 8 Example #P1 can be efficient when the aim is to apply it to all kinds of narrowband channel BWs by defining a punched PBCH or a subset of PBCH transmission RBs.

[0270] FIG. 8 An example of a frequency resource domain for PBCH transmission / reception according to an embodiment of the present disclosure is illustrated. Specifically, FIG. 8 An example of a PBCH transport RB subset based on example #P1 is shown.

[0271] [Example #P2]

[0272] One approach could be to use 15 PRBs, including PSS / SSS, to configure the PBCH to transmit a subset of RBs.

[0273] Example #P2 is a case where 15 PRBs, including PSS / SSS, are used to configure the PBCH to transport a subset of RBs.

[0274] The PBCH transmission RB subset (i.e., detailed configuration of 15 PRBs) according to embodiments of this disclosure can be determined based on one of the following configurations #P2-1 to #P2-4.

[0275] Configuration #P2-1: Center 12 PRB (for PSS / SSS) + Lower 3 PRB

[0276] Configuration #P2-2: Center 12 PRB (for PSS / SSS) + Higher 3 PRB

[0277] Configuration #P2-3: Center 12 PRB (for PSS / SSS) + Lower 2 PRB + Higher 1 PRB

[0278] Configuration #P2-4: Center 12 PRB (for PSS / SSS) + Higher 2 PRB + Lower 1 PRB

[0279] Due to the characteristics of PBCH RE mapping, prioritizing the transmission of lower RBs in the PBCH transmission may offer a slight performance advantage. Therefore, all other things being equal, configuring #P2-1 instead of #P2-2 may have an advantage in PBCH reception performance. Additionally, configuring #P2-3 instead of #P2-4 may have an advantage in PBCH reception performance.

[0280] In cases where the PSS / SSS is exposed to interference from continuous channels / bands due to its exposure to the band edge, configurations #P2-1 and #P2-2 may negatively impact synchronization and measurement performance. If the impact of interference is anticipated, configurations #P2-3 or #2-4 can be considered. In configurations #P2-3 or #2-4, the PSS / SSS can be further positioned within the channel band (BW), thus protecting the PSS / SSS from interference from continuous channels / bands. See below for reference. FIG. 9 This needs to be explained.

[0281] FIG. 9 An example of a frequency resource domain for PBCH transmission / reception according to another embodiment of this disclosure is illustrated.

[0282] FIG. 9 Example (a) illustrates configuration #P2-1. In this case, the PBCH transport RB subset may include a central 12 PRBs (for PSS / SSS) + a lower 3 PRBs.

[0283] FIG. 9 Example (b) illustrates configuration #P2-3. In this case, the PBCH transport RB subset may include a central 12 PRBs (for PSS / SSS) + two lower PRBs + one higher PRB.

[0284] NR PDCCH transmission method

[0285] The following two narrowband scenarios are considered important in the 3GPP Rel-18 standardization.

[0286] [Narrowband Scene #1]

[0287] Typical narrowband scenarios

[0288] - It is expected that scenario #1 will be supported in at least n8 / n26 / n28 of the NR operating frequency bands defined in TS 38.101-1. At this time, the frequency bands supporting narrowband scenarios may also include n100.

[0289] - RF channel BW=3 MHz, nRB=15 PRBs (with 15 kHz SCS), 12-PRB PBCH, finer synchronization grid.

[0290] To address the issue that using a conventional 1.2 MHz synchronization grid dot spacing cannot consistently limit the SSB to fall within the narrowband channel bounding width (BW), a finer synchronization grid specifically designed for narrowband has been introduced. The frequency location based on this finer synchronization grid can be determined using Equation 3 below.

[0291] [Equation 3]

[0292] A finer synchronization grid is defined as being as far apart as possible from the regular 1.2 MHz synchronization grid in the frequency domain. Specifically, frequency positions based on the finer synchronization grid can be determined at 600 kHz intervals. In other words, three frequency positions (M=1, 3, 5) based on the finer synchronization grid can be determined / defined at 600 kHz intervals.

[0293] [Narrowband Scene #2]

[0294] GSM to NR migration scenario (a scenario in which GSM is gradually converted to NR by gradually expanding the NR transmission BW while currently using GSM).

[0295] - Scenario #2 is expected to be supported in at least n100 of the NR operating bands defined in TS 38.101-1.

[0296] - For 3 MHz and 5 MHz channel BW, consider the following two sub-scenarios.

[0297] Narrowband scenario #2-1: RF channel BW=3 MHz, NR transmission BW=12 PRBs (with 15 kHz SCS), 12-PRBPBCH, with an additional synchronization grid for 3 MHz.

[0298] Narrowband scenario #2-2: RF channel BW=5 MHz, NR transmission BW=20 PRBs (with 15 kHz SCS), 20-PRBPBCH, with an additional synchronization grid for 5 MHz.

[0299] For example, NR transmission BW can be a concept different from nRB. When some RBs within an nRB, rather than the entire nRB, are used for actual NR transmission, NR transmission BW can be used to distinguish between RBs and nRBs.

[0300] In narrowband scenario #2, due to the characteristics of the scenario, it may be necessary to set the 12-PRB PBCH or 20-PRB PBCH as close to the narrowband edge as possible. In the case of n100, additional synchronization grids can be supported at locations considering the adjacent channel environment. This will be discussed in the following sections. FIG. 10 and 11 Describes the additional synchronization grid for n100.

[0301] FIG. 10 An example of a synchronization grid according to an embodiment of the present disclosure is illustrated.

[0302] Reference FIG. 10The frequency location associated with scenario #2-1 could be 920.73 MHz. Additional synchronization grids can be supported at the corresponding frequency location. 10A can indicate the minimum interval (e.g., 100 kHz) between a conventional synchronization grid and a finer synchronization grid. 10B can indicate the minimum interval (e.g., 20 kHz) between a synchronization grid based on 12 PRB PBCH and a channel grid (15 PRB) defined / determined in units of 100 kHz. In other words, 10B can indicate the minimum interval that allows setting the synchronization grid with respect to the channel grid based on the subcarrier spacing (SCS) (e.g., 15 kHz).

[0303] FIG. 11 Another example of a synchronization grid according to an embodiment of the present disclosure is illustrated.

[0304] Reference FIG. 11 The frequency location associated with scenario #2-2 could be 921.45 MHz. Additional synchronization grids can be supported at the corresponding frequency location. 11A can indicate the minimum spacing (e.g., 100 kHz) between a conventional synchronization grid and a finer synchronization grid. 11B can indicate the minimum spacing (e.g., 0 kHz) between a synchronization grid based on 20 PRB PBCH and a channel grid (25 PRB) defined / determined in units of 100 kHz.

[0305] Furthermore, as mentioned above, the narrowband channel bandwidth (BW) can be smaller than the minimum bandwidth of a conventional CORESET #0 designed considering general bandwidth. In this case, the CORESET #0 bandwidth may exceed the narrowband channel bandwidth (BW). For example, since the CORESET #0 bandwidth supported in the current NR standard is 24 PRBs (4.32 MHz) based on a 15 kHz SCS, the CORESET #0 bandwidth may exceed the narrowband channel bandwidth (BW) shown in Tables 6 and 7. To support this scenario, the following two methods are proposed: [Method #1] Using the new CORESET #0 method A new CORESET #0 can be defined with a small bandwidth included in the narrowband channel BW. PDCCH can be sent based on the newly defined CORESET #0.

[0306] [Example #1 of Method #1] To support a 3 MHz channel bandwidth, a 15-PRB transmission bandwidth or a 12-PRB transmission bandwidth, the following CORESET #0 can be defined / supported. A new CORESET #0 with a bandwidth of 12 PRBs can be defined, which is less than the conventional minimum bandwidth of 24 PRBs. In other words, the frequency domain size of CORESET #0... It can be 12.

[0307] [Example #2 of Method #1] To support a 5 MHz channel bandwidth and a 20-PRB transmission bandwidth, the following CORESET #0 can be defined / supported. A new CORESET #0 with a bandwidth of 18 PRBs can be defined, which is less than the standard minimum bandwidth of 24 PRBs. In other words, the frequency domain size of CORESET #0... It can be 18.

[0308] [Method #2] Reuse the regular CORESET #0 method

[0309] When reusing the regular CORESET #0, the PDCCH can be transmitted by excluding resource areas where RE mapping is performed outside the narrowband channel BW. For example, puncturing (truncation) can be performed on RBs exceeding the narrowband channel BW (e.g., 3 MHz, 15 PRBs). As a concrete example, when the frequency domain size... When the time is 24, CORESET #0 can be obtained by punching holes in the 9 highest-numbered RBs out of the 24 RBs.

[0310] For example, a base station can perform PDCCH RE mapping for the entire conventional CORESET #0 bandwidth according to the conventional method specified in TS 38.213. The base station can transmit PDCCH based on the PDCCH included in the narrowband channel BW, specifically RE / RB / REG / REG bundle / CCE. In this case, "includes" can indicate either "partially included" or "fully included".

[0311] [Example #1 of Method #2] To support a 3 MHz channel bandwidth, the 24-PRB CORESET #0 defined in Table 13-1 of TS 38.213 can be reused. In this case, the PDCCH transmission RE / RB / REG / REG bundle / CCE mapped to REs outside the transmission BW (12 or 15 PRBs) can be transmitted without puncturing / truncating, or even if transmitted, UE reception of them can be undesirable / unnecessary. For example, the 12 RBs (or 9 RBs) with the highest / lowest numbers out of the 24 PRBs can be punctured.

[0312] [Example #2 of Method #2] To support a 5 MHz channel bandwidth and a 20-PRB NR transmission BW, the 24-PRB CORESET #0 defined in Table 13-1 of TS38.213 can be reused. In this case, the PDCCH transmission RE / RB / REG / REG bundle / CCE mapped to REs outside the transmission BW (20 PRBs) can be transmitted without puncturing / truncating, or even if transmitted, UE reception of them can be undesirable / unnecessary. For example, the four RBs with the highest / lowest numbers in the 24-PRB can be punctured.

[0313] The position of CORESET #0 can be defined / determined relative to the SSB. Specifically, the relative position of CORESET #0 can be determined using offset parameters and... k SSB The parameters are determined as shown in Table 8. In other words, they can be based on the offset parameter (RB offset) and k SSB The parameter (subcarrier offset) determines the interval between CORESET #0 and SSB.

[0314] [Table 8]

[0315] k SSB This can be indicated by the ssb-SubcarrierOffset parameter in the system information block (e.g., MIB). For example, k SSB It can be indicated by an integer from 0 to 15. If the ssb-SubcarrierOffset parameter is not set, it can be derived from the frequency difference between the SS / PBCH block and point A. k SSB .

[0316] It can be defined based on one of the embodiments described later (e.g., method #A or method #B). k SSB Parameters. For example, they can be defined based on the SS / PBCH block in the same manner as in existing methods. k SSB Parameters (method #A). For example, they can be defined based on the punched SS / PBCH block. k SSB Parameters (Method #B). Refer to the following text. FIG. 12 and FIG. 13 Description and k SSB Point A, which is related to the parameters.

[0317] FIG. 12Point A is illustrated using the existing method. Specifically, FIG. 12 An example of offsetToPointA is shown. See [reference] FIG. 12 , offsetToPointA represents the frequency offset between point A and the lowest subcarrier (subcarrier 0) of the lowest resource block (CRB#8) that overlaps with the SS / PBCH block. k SSB This indicates the lowest subcarrier number (subcarrier 0) of the SS / PBCH block and the common resource block ( Subcarrier offsets between subcarriers 0 in the common resource block () ) is obtained from offsetToPointA. That is to say, the public resource block ( It can be the lowest resource block that overlaps with the SS / PBCH block based on offsetToPointA.

[0318] FIG. 13 Point A is illustrated according to an embodiment of this disclosure. Reference numerals are omitted. FIG. 12 The given descriptions overlap. (Refer to...) FIG. 13 The punched SS / PBCH block can consist of 12 resource blocks. According to an embodiment of this disclosure, offsetToPoint A represents point A and the lowest-numbered resource block overlapping with the punched SS / PBCH block. The frequency offset between the lowest numbered subcarrier (subcarrier 0) of CRB#12.

[0319] The following describes an implementation of the criteria relating to the relative positions (e.g., the offsets in Table 8) of CORESET #0 in methods #A to #C.

[0320] [Method #A]

[0321] Even when PBCH and PDCCH are transmitted in narrowband based on the method proposed in this disclosure, the relative positional relationship between SSB and CORESET #0 and its signaling method can still follow existing standards. In other words, the "minimum RB index of the CORESET for the Type0-PDCCH CSS set" and the "first RB corresponding to the SS / PBCH block" described in the above standard can be defined based on the SSB (PBCH) / CORESET #0 BW before puncturing.

[0322] Specifically, even if no actual transmission / reception is performed due to subset transmission for narrowband transmission, puncturing, etc., the offsets in Table 8 can be defined based on the entire PBCH BW (before puncturing) and the entire CORESET #0 BW (before puncturing).

[0323] [Method #B]

[0324] The "first RB corresponding to the SS / PBCH block" can be defined based on the actual PBCH transmission RBs sent / received. The actual PBCH transmission RBs sent / received can mean the RBs after puncturing (or a subset thereof).

[0325] In other words, the offsets in Table 8 can be defined based on the punched PBCH (i.e., the punched SS / PBCH block).

[0326] For example, in the case of 12-RB PBCH, "the first RB corresponding to the SS / PBCH block" can refer to one of the following items i) to iv).

[0327] i) "Corresponding to the first RB of the (actually) transmitted SS / PBCH block"

[0328] ii) "The first RB of the SS / PBCH block after drilling"

[0329] iii) "The first RB corresponding to the "non-drilled" SS / PBCH block", iv) "Subcarrier number 48 corresponding to the SS / PBCH block" The following will refer to FIG. 14 Description of CORESET #0.

[0330] FIG. 14 CORESET #0 is illustrated according to one embodiment of this disclosure. See also... FIG. 14 When supporting 12-RB PBCH in a narrowband transmission BW with 12 PRBs, CORESET #0 with a size of 12 PRBs can be applied.

[0331] According to the definition of method #B, the RB offset value can be defined as follows (the offset in Table 8).

[0332] For example, the RB offset value can be 0. In other words, the minimum RB index of the CRB that overlaps with the minimum RB index of the punched SSB (the index of the first RB) can be aligned with the minimum RB index of CORESET #0.

[0333] For example, when a punctured PBCH occupies the entire maximum transmission BW, or when CORESET #0 is transmitted without puncturing within the maximum transmission BW and / or the punctured PBCH BW, the RB offset value can be defined as follows. The RB offset value can be defined as a value that aligns the "highest" RB index of the CRB that overlaps with the minimum RB index of the punctured SSB with the minimum RB index of CORESET #0.

[0334] To support via method #AFIG. 14 For example, the RB offset value can be defined as a negative (-) value. Specifically, when the RB offset value is -4, the minimum RB index of the CRB that overlaps with the minimum RB index of the punched SSB can be aligned with the minimum RB index of CORESET #0.

[0335] [Method #C]

[0336] The aforementioned offset can be defined based on the minimum RB index, according to a standard different from the criteria for non-punctured PBCH (Method #A) or punctured PBCH (Method #B). The offset can be defined based on the minimum RB index among the RBs (or CRBs) defined within the maximum transmission BW or among the RBs (or CRBs) where DL reception is possible. In this case, based on the offset value of 0, the minimum RB index among the RBs (or CRBs) defined within the maximum transmission BW or among the RBs (or CRBs) where DL reception is possible can be aligned with the minimum RB index of CORESET #0.

[0337] The parameters used to support the methods described above (method #A / method #B / method #C) can be indicated / configured via broadcast signaling (e.g., MIB). These parameters may include all or some of the parameters, including the application method and offset parameters within the method.

[0338] According to one implementation, the highest RB index of CORESET #0 can be determined without separate signaling. For example, the highest RB index of CORESET #0 can be determined based on the highest RB index of the CRB that does not exceed the maximum transmission BW. As another example, the highest RB index of CORESET #0 can be determined based on the highest RB index of the CRB that does not exceed the punctured PBCH BW.

[0339] At this point, the highest RB index for CORESET #0 can be determined in units of RB / REG / REG bundle / CCE. When configuring the highest RB index for CORESET #0 in units of REG bundle / CCE, the total number of RBs in CORESET #0 can be limited to a multiple of the number of RBs constituting the REG bundle / CCE.

[0340] According to one implementation, the highest RB index for CORESET #0 can be configured via broadcast signaling. For example, the base station can indicate / configure one of the predefined supported CORESET #0 BW values ​​in the standard to the UE based on broadcast signaling. The supported CORESET #0 BW in narrowband can have BWP sizes that are not supported by traditional UEs, but new UEs supporting narrowband operation can be configured / implemented to force support of the supported CORESET #0 BW size in narrowband.

[0341] In the following text, methods for supporting PDCCH transmission in narrowband scenarios will be described with consideration of the aforementioned narrowband scenarios (Scenario #1 / Scenario #2 / Scenario #2-1 / Scenario #2-2) and methods #1 and #2 related to CORESET #0.

[0342] The position of CORESET #0 in the frequency domain is determined by the offset parameter. The value of the offset parameter can vary according to offset definition method #A / method #B / method #C.

[0343] The methods described below will focus on offset definition method #A (the conventional method, based on the PBCH BW before punching and the CORESET #0 BW before punching). This is merely for ease of description and is not intended to limit the application of the implementations described later to method #A. Even in the case of offset definition methods #B / #C, the methods proposed below can be applied in the same way, where only the offset values ​​differ.

[0344] [Method to use 15-PRB CORESET #0 with drilling support]

[0345] In narrowband scenarios other than narrowband scenario #2-1, 15-PRB CORESET #0 can be supported. 15-PRB CORESET #0 can be supported by reusing the regular 24-PRB CORESET #0. In other words, after performing PDCCH RE mapping based on 24-PRB CORESET #0, PDCCH can be transmitted based on RE / RB / REG / REG bundles / CCE in the 15-PRB CORESET #0 frequency domain. Due to the bandwidth difference between 24-PRB CORESET #0 and 15-PRB CORESET #0 before puncturing, offsets can be configured / defined / applied using values ​​in the range of 5 to -2 in all supported scenarios. If the performance difference based on the offset value is not significant, a subset of values ​​within the above range (e.g., offset parameter value 0) can be set as the offset value in the CORESET #0 table. When multiple offset values ​​are available, a single value can be configured / indicated to the UE based on the base station's broadcast signaling.

[0346] [Method for supporting the new (non-drilled) 12-PRB CORESET #0]

[0347] For all the narrowband scenarios mentioned above, 12-PRB CORESET #0 can be supported. In this case, to implement narrowband scenarios #2-1, it may be necessary to support allocations that align the minimum RB index of 12-PRB CORESET #0 with the minimum RB index of 12-PRB PBCH. It may be necessary to force support for offset parameter values ​​of -4 and...k SSB The value is 0. Similarly, assuming method #B is used, the offset parameter value of 0 can be forced to be supported. k SSB Value 0. The following will refer to... FIG. 15 to FIG. 17 The above allocation method is described in detail.

[0348] FIG. 15 An example of a channel grid and a synchronization grid based on an embodiment of this disclosure is illustrated. (Refer to...) FIG. 15 The RB offset from the minimum RB index of 12-PRB CORESET #0 to the minimum RB index of the CRB overlapping with the first RB of the pre-punch SSB (PBCH) can be -4. In the case of method #B, the RB offset from the minimum RB index of 12-PRB CORESET #0 to the minimum RB index of the CRB overlapping with the first RB of the post-punch SSB (PBCH) can be 0. In this case, k SSB The value can be 0.

[0349] FIG. 16 Another example of a channel grid and a synchronization grid based on an embodiment of the present disclosure is illustrated. FIG. 17 Another example of a channel grid and a synchronization grid based on an embodiment of the present disclosure is illustrated.

[0350] In narrowband scenario #1, considering the relationship between all the finer synchronization grids (e.g., frequency positions based on Equation 3) and the 100kHz channel grid, the following offset parameter values ​​can be additionally / selectively supported. k SSB This value is used to provide network flexibility to base stations.

[0351] Reference FIG. 16 It supports offset parameter values ​​of -4 and k SSB Value 8. Assuming method #B is used, offset parameter values ​​of 0 and 8 are supported. k SSB Value 8.

[0352] Reference FIG. 17 It supports offset parameter values ​​of -2 and k SSB Value 4. Assuming method #B is used, offset parameter values ​​of 2 and 4 are supported. k SSB Value 4.

[0353] As mentioned above, based on the offset parameter and k SSBThe parameters determine the relative position between the SSB and CORESET #0. Therefore, the combination of channel grids and synchronization grids that can be supported for each NR operating band can be limited to cases where the spacing between them is a multiple of the subcarrier spacing. This will be referred to below. FIG. 18 to FIG. 20 Detailed description.

[0354] FIG. 18 An example of a valid offset value is shown among the offset values ​​between CORESET #0 and the synchronization grid based on an embodiment of this disclosure.

[0355] Reference FIG. 18 18A represents the channel bandwidth (15 PRBs) with a channel center frequency based on a channel grid of 100 kHz. 18B represents 15-PRB CORESET #0. 18C represents 12-PRB PBCHs based on six offset values. Although not shown in the figure, the six 12-PRB PBCHs based on offset values ​​1 to 6 can be referred to as 18C-1 to 18C-6.

[0356] 18D indicates the effective synchronization grid range. Specifically, the effective synchronization grid range can refer to the range from "channel center frequency -270 kHz (1.5 PRB)" to "channel center frequency +270 kHz (1.5 PRB)".

[0357] 18E indicates the potential frequency location based on the aforementioned finer synchronization grid.

[0358] 18F indicates the index (1 to 6) of the six 12-PRB PBCH frequency positions within the effective synchronization grid range that is allowed for channel bandwidth. Specifically, in indices 1 to 6, indices 2 and 5 are those where the interval between the channel center frequency and the frequency position is a multiple of the subcarrier spacing (SCS) (15 kHz). This will be described in detail below.

[0359] Of the six frequency positions, only the two frequency positions based on indices 2 and 5 are allowed for channel bandwidth.

[0360] In the case of index 2, the offset value is 120 kHz. Since 120 kHz = 0... (12 SCS) 15 kHz) +8 15kHz, therefore, the RB offset corresponding to an offset value of 120 kHz is 0, and k SSB It's 8.

[0361] In the case of index 5, the offset is 420 kHz. Since 420 kHz = 2... (12 SCS) 15 kHz) +4 15kHz, therefore, the RB offset corresponding to the offset value of 420 kHz is 2, and k SSB It is 4.

[0362] The remaining four frequency positions (index 1, index 3, index 4, index 6) are not allowed because their offset values ​​are not multiples of the SCS (15 kHz). In other words, CORESET #0 and 12-PRB PBCH (12 RB SS / PBCH block) are allowed to be set at SCS-based frequency positions only at some offset values ​​of 120 kHz (index 2) and 420 kHz (index 5), and frequency positions based on other offset values ​​may not be allowed because they are not set at SCS-based frequency positions.

[0363] FIG. 19 An example of an effective offset value between CORESET #0 and a synchronization grid in a specific frequency band is shown based on an embodiment of this disclosure.

[0364] Reference FIG. 19 19A indicates that it has a channel center frequency (936.6 MHz = 9366) for the operating frequency band n106. 100kHz) channel BW (15 PRBs).

[0365] 19B indicates 15-PRB CORESET #0. 19C indicates 12-PRB PBCH based on the effective offset value of 120kHz (=8 SCS) among the above six offset values.

[0366] 19D indicates the effective synchronization grid range.

[0367] 19E represents the frequency position based on the finer synchronization grid described above. Referring to Equation 3, the frequency position can be calculated as follows.

[0368]

[0369] 19F indicates the index (2) of the three 12-PRB PBCH frequency positions within the effective synchronization grid range, which is allowed for a channel bandwidth with a center frequency of 936.6 MHz.

[0370] Specifically, the three frequency positions belonging to 19D can be calculated based on N=1560 and M=1, 3, 5 as shown in (1) to (3) below.

[0371] (1) 936,350 kHz (936.35 MHz), N=1560, M=1 / interval: 0.25 MHz (250 kHz)

[0372] (2) 936,450 kHz (936.45 MHz), N=1560, M=3 / interval: 0.15 MHz (150 kHz)

[0373] (3) 936,550 kHz (936.55 MHz), N=1560, M=5 / Interval: 0.05 MHz (50 kHz)

[0374] Among the three frequency positions, the frequency position that is a multiple of SCS (15 kHz) from the channel center frequency of 936.6 MHz is (2) 936.45 kHz.

[0375] As described above, for a channel bandwidth with a center frequency of 936.6 MHz in the n106 band, only frequency positions with an offset value of 120 kHz are allowed. In this case, the RB offset is 0, and k SSB It's 8.

[0376] FIG. 20 Another example is illustrated of the effective offset value between CORESET #0 and the synchronization grid in a specific frequency band, based on an embodiment of this disclosure.

[0377] Reference FIG. 20 20A indicates that it has a channel center frequency (860.6 MHz = 8606) for the operating frequency band n26. The channel bandwidth is 100kHz (15 PRBs). 20B indicates 15-PRB CORESET #0.

[0378] 20C indicates 12-PRBPBCH based on the effective offset value of 420 kHz (=28 SCS) among the six offset values ​​mentioned above.

[0379] 20D indicates the effective synchronization grid range

[0380] 20E represents the frequency position based on the finer synchronization grid described above. Referring to Equation 3, the frequency position can be calculated as follows.

[0381]

[0382] 19F indicates the index (5) of the three 12-PRB PBCH frequency positions within the effective synchronization grid range, which is allowed for a channel bandwidth with a center frequency of 860.6 MHz.

[0383] Specifically, the three frequency positions belonging to 20D can be calculated as shown in (1) to (3) below.

[0384] (1) 860,250 kHz (860.25 MHz), N=1433, M=3 / interval: 0.35 MHz (350 kHz)

[0385] (2) 860,750 kHz (860.75 MHz), N=1434, M=1 / interval: 0.15 MHz (150 kHz)

[0386] (3) 860,850 kHz (860.85 MHz), N=1434, M=3 / interval: 0.25 MHz (250 kHz)

[0387] Among the three frequency positions, the frequency position that is a multiple of SCS (15 kHz) from the channel center frequency of 860.6 MHz is (2) 860.75 kHz.

[0388] As described above, for a channel bandwidth with a center frequency of 860.6 MHz in the n26 band, only frequency positions with an offset value of 420 kHz are allowed. In this case, the RB offset is 2, and k SSB It is 4.

[0389] It can support offset parameter values ​​by default and k SSB Combinations of values, or based on FIG. 18 to FIG. 19 The conditions described in [the document] (where the interval is a multiple of the subcarrier interval) further support the aforementioned combination. For SCS (15 kHz), the allowed / supported {offset values,} k SSB The value can be {0, 8} or {2, 4}.

[0390] The above method (i.e., the method described in [Method for supporting the new (non-drilled) 12-PRB CORESET #0]) and the corresponding RB offset and k SSB The value can be applied not only to the new (non-punched) CORESET #0, but also to the method presented below for supporting CORESET #0 with punching.

[0391] [Method for using 20-PRB CORESET #0 to support punching]

[0392] For narrowband scenario #2-2, 20-PRB CORESET #0 can be supported. 20-PRB CORESET #0 can be supported by reusing the regular 24-PRB CORESET #0. In other words, after performing PDCCHRE mapping based on 24-PRB CORESET #0, PDCCH can be transmitted based on RE / RB / REG / REG bundles / CCE within the 20-PRB CORESET #0 frequency domain. Due to the bandwidth difference between 24-PRB CORESET #0 and 20-PRB CORESET #0 before puncturing, the offset parameter can be applied using values ​​in the range of 0 to 4 in all supported scenarios. If the performance difference based on the offset value is not significant, a subset of values ​​within the above range (e.g., offset parameter value 0) can be set as the offset value in the CORESET #0 table. When multiple offset values ​​are available, a single value can be configured / indicated to the UE based on the base station's broadcast signaling.

[0393] [Method for using 18-PRB CORESET #0 to support punching]

[0394] For narrowband scenario #2-2, 18-PRB CORESET #0 can be supported. 18-PRB CORESET #0 can be supported by reusing the regular 24-PRB CORESET #0. In other words, after performing PDCCHRE mapping based on 24-PRB CORESET #0, PDCCH can be transmitted based on the RE / RB / REG / REG bundles / CCE in the frequency domain of 18-PRB CORESET #0. At this time, due to the bandwidth difference between 24-PRB CORESET #0 and 18-PRB CORESET #0 before puncturing, the offset parameter can be applied using values ​​in the range of 6 to -2 in all supported scenarios. If the performance difference based on the offset value is not significant, a portion of the values ​​within the above range (e.g., offset parameter value 0) can be set as the offset value in the CORESET #0 table. When multiple offset values ​​are available, a single value can be configured / indicated to the UE based on the base station's broadcast signaling.

[0395] [Method for supporting the new (non-drilled) 18-PRB CORESET #0]

[0396] Instead of reusing the regular 24-PRB CORESET #0, a newly defined CORESET #0 can be used to support 18-PRB CORESET #0. Specifically, similar to the new 12-PRB CORESET #0, a new CORESET #0 of 18 PRB size can be supported. In other words, a CORESET #0 of 18-PRB size can be indicated without punching. For the new 18-PRB CORESET #0, the traditional interleaved CORESET CCE to REG mapping can be supported selectively or always. When mapping is supported, unlike the new 12-PRB CORESET #0 (where R=2), R=3 can be supported. When supporting 20-PRB transmission BW in narrowband scenario #2-2, offset parameter values ​​in the range of 0 to -2 can be applied. If the performance difference based on the offset value is not significant, a portion of the values ​​in the above range (e.g., offset parameter value 0) can be set as the offset value of the CORESET #0 table. When multiple offset values ​​are available, a single value can be configured / indicated to the UE based on the base station's broadcast signaling.

[0397] [Method for configuring the new CORESET table (TS 38.213 Table 13-0)]

[0398] Based on representative narrowband scenarios and considering the method of supporting CORESET #0 in the corresponding scenarios, a new CORESET #0 table (TS 38.213 Table 13-0) for PDCCH transmission in narrowband can be configured as shown in Table 9 below.

[0399] [Table 9]

[0400] The reason for needing the entries in Table 9 has been described in the proposed method for CORESET #0 above. The entries in Table 9 are defined to ensure as many reserved fields as possible by using only those entries absolutely necessary for forward compatibility. As previously stated, the offset values ​​are based on offset definition method #A (the traditional method, based on the pre-punch PBCH BW and the pre-punch CORESET #0 BW), but the proposed method can be applied, and is not limited to a specific offset definition method. For example, the offset values ​​in Table 9 can be replaced with those based on method #B. As a specific example, the offset value -4 can be replaced with 0, which is a value based on method #B.

[0401] To support more diverse configurations for CORESET #0 in narrowband, some of the CORESET #0 configuration parameters can be set / indicated via broadcast signaling. CORESET #0 configuration parameters may include the following.

[0402] - 24-PRB CORESET #0 punch pattern

[0403] For example, parameters related to the punching pattern can represent 15-PRB or 20-PRB after punching.

[0404] - Additional offset for the same CORESET #0 size

[0405] For example, the additional offset can be 0 or 4. In this case, the UE can calculate the offset value by adding the additional offset to the offset value in Table 9 (e.g., the offset of 24-PRB CORESET #0).

[0406] - The number of symbols for CORESET #0 (e.g., 2 or 3).

[0407] - Interleaved CCE to REG mappings and non-interleaved CCE to REG mappings

[0408] For example, parameters associated with a mapping can indicate an interleaved or non-interleaved mapping.

[0409] - n shift control

[0410] For example, with n shift The relevant parameters can indicate n shift Value (0 or half the size of CORESET #0 before punching) or n shift Offset value (to be added) n shift Offset value).

[0411] In narrowband, the UE can determine the CORESET #0 table for PDCCH reception (between the existing table and Table 9) based on the following synchronization grid, through which the UE acquires the SSB during the cell search process. In other words, when accessing via a more refined synchronization grid newly defined for narrowband, the UE can obtain CORESET #0 information by referring to Table 9. In narrowband scenario #2, Table 9 is supported, and when accessing via an additional synchronization grid, CORESET #0 information can be obtained by referring to Table 9. Alternatively, when Table 9 is supported only under specific conditions in narrowband scenario #2, or when Table 9 is supported by selection by the base station, the use of Table 9 or the existing table (Table 13-1 of TS 38.213) can be configured / indicated via broadcast signaling.

[0412] Alternatively, when access is made via a specific frequency band within the NR operating band, it can be indicated that CORESET #0 Table 9 is always used. In this case, the specific frequency band can be n8 / n26 / n28 or n8 / n26 / n28 / n100.

[0413] The entire base station / UE operation process using the above method can be as follows.

[0414] - Considering the narrowband scenario described above, the base station selects one of the entries in CORESET #0 Table 9 (or the existing Table 13-1).

[0415] - The base station configures / indicates the selected CORESET #0 table entry information (e.g., index 0 of table 9) based on broadcast signaling (e.g., MIB).

[0416] - The base station configures CORESET #0 based on the selected CORESET #0 configuration and sends PDCCH.

[0417] The UE obtains CORESET #0 related information by referring to broadcast signaling (e.g., index 0) and the CORESET #0 table (e.g., table 9). CORESET #0 related information may include the multiplexing mode and the number of RBs defined in table 9. Number of symbols And offset.

[0418] - The UE receives the PDCCH based on the obtained CORESET #0 related information (e.g., offset).

[0419] - Subsequently, the UE performs operations including receiving SIB1, receiving paging, and transmitting PRACH for random access.

[0420] [Methods for generating PDCCH DMRS]

[0421] According to existing definitions (Table 10 below), the reference point used to generate the PDCCHDMRS sequence during PDCCH transmission via CORESET #0 is... k It is subcarrier 0 of the lowest RB index of CORESET #0.

[0422] [Table 10]

[0423] When transmitting PDCCH via CORESET #0 in narrowband, ambiguity may arise in generating the PDCCH DMRS sequence during PDCCH transmission via CORESET #0, considering the possibility of transmitting PDCCH via a portion of CORESET #0. To eliminate this ambiguity, the reference point for generating the PDCCH DMRS sequence during PDCCH transmission via CORESET #0 in narrowband can be determined using the following method. k .

[0424] For example, when applying method #1 (using the new CORESET #0) in narrowband, the subcarrier 0 with the lowest RB index of the new CORESET #0 can be determined as the reference point for generating the PDCCH DMRS sequence. k Subsequently, a PDCCH DMRS sequence can be generated based on the method defined in Table 10, and PDCCH transmission can be performed based on the generated PDCCH DMRS sequence.

[0425] For example, when applying method #2 (reusing the conventional CORESET #0 method) in narrowband, the subcarrier 0 with the lowest RB index of the pre-punch CORESET #0 can be determined as the reference point for generating the PDCCH DMRS sequence. k Subsequently, a PDCCH DMRS sequence can be generated as defined in Table 10, and RE mapping can be performed. During PDCCH transmission, puncturing / truncation / discarding can be performed along with the PDCCH.

[0426] For example, when applying method #2 (reusing the conventional CORESET #0 method) in narrowband, the punctured CORESET #0 or the lowest-indexed subcarrier 0 of the PDCCH transmit / receive band can be determined as the reference point for generating the PDCCHDMRS sequence. k Subsequently, a PDCCH DMRS sequence is generated as defined in Table 10, and RE mapping is performed. Afterward, PDCCH transmission can be performed. This implementation method can be applicable only to scenarios where no UE receives PDCCH throughout CORESET #0, i.e., a method applicable to dedicated frequency bands that only support narrowband operation.

[0427] In terms of implementation, the operation of the base station / UE according to the above embodiments (e.g., operation based on at least one of method #1, method #2, method #A, method #B, method #C, method for supporting CORESET #0, method for supporting a new CORESET #0, and method for generating PDCCH DMRS) can be described later. FIG. 23Devices (e.g., FIG. 23 Processors 110 and 210 are used to process it.

[0428] Furthermore, the operation of the base station / UE according to the above embodiments (e.g., operation based on at least one of method #1, method #2, method #A, method #B, method #C, method for supporting CORESET #0 with puncturing, method for supporting a new CORESET #0, and method for generating PDCCH DMRS) can be used to drive at least one processor (e.g., FIG. 23 The instructions / programs (e.g., instructions or executable code) of the 110 and 210 are stored in memory (e.g., FIG. 23 (140 and 240)

[0429] In the following text, reference will be made to FIG. 21 and FIG. 22 The above implementation methods are described in detail from the perspective of UE / base station operation. The methods described below are presented separately for ease of description only, and it should be understood that a part of one method can be replaced by a part of another method, or they can be applied in combination with each other.

[0430] FIG. 21 This is a flowchart illustrating a method executed by a UE according to an embodiment of the present disclosure.

[0431] Reference FIG. 21 According to one embodiment of the present disclosure, a method performed by a UE includes receiving an SS / PBCH block S2110 and receiving a PDCCH S2120.

[0432] In step S2110, the UE receives a synchronization signal / physical broadcast channel (SS / PBCH) block from the base station based on the synchronization grid for the channel bandwidth.

[0433] For example, the channel bandwidth can be narrowband. As a specific example, the channel bandwidth can be 3 MHz. The number of resource blocks (RBs) based on the channel bandwidth can be 15.

[0434] For example, the SS / PBCH block can be a punched SS / PBCH block based on at least one of the embodiments described above. Specifically, the time-frequency structure associated with the SS / PBCH block (e.g., refer to...) FIG. 8 , FIG. 9 and FIG. 13 It can be based on punching.

[0435] The punched SS / PBCH block can be based on 12 resource blocks (RBs). These 12 resource blocks can be derived from a time-frequency structure based on a regular SS / PBCH block (e.g., FIG. 7The remaining resource blocks are the 20 resource blocks excluding 8 resource blocks. As a specific example, 12 resource blocks can be the remaining resource blocks within four orthogonal frequency division multiplexing (OFDM) symbols, based on subcarrier numbers 0 to 239, excluding subcarrier numbers 0 to 47 and 192 to 239.

[0436] The channel bandwidth associated with cell search based on SS / PBCH blocks can be less than 5 MHz. For example, the channel bandwidth can be 3 MHz.

[0437] In step S2120, the UE receives the Physical Downlink Control Channel (PDCCH) from the base station based on the Control Resource Set (CORESET).

[0438] For example, based on one of the above embodiments, CORESET can be CORESET #0.

[0439] For example, offsets can be determined based on configurations associated with the CORESET (e.g., indexes in Table 9). Offsets can be defined from the smallest resource block (RB) index of the CORESET to the RB index associated with the SS / PBCH block. In other words, offsets can be values ​​in RB units.

[0440] According to one implementation, based on i) a channel bandwidth of 3 MHz, ii) a subcarrier spacing (SCS) of 15 kHz for the SS / PBCH block, and iii) a CORESET SCS of 15 kHz: the offset can be either i) 0 or ii) 2, and the RB index can be determined based on the first RB of the punctured SS / PBCH block. This implementation can be based on method #B and a method for supporting a new (non-punctured) 12-RB CORESET #0. The offset can refer to an offset parameter value or an RB offset. The offset can be defined relative to the CORESET SCS.

[0441] Specifically, the RB index can be the smallest RB index of the common resource block (CRB) that overlaps with the first RB of the punched SS / PBCH block. Here, the common resource block can represent the one in Table 8. .

[0442] For example, broadcast signaling can be used to indicate configurations related to CORESET and k SSB Specifically, the configuration related to the CORESET can be indicated based on the Master Information Block (MIB) associated with the SS / PBCH block, i) and ii) the configuration related to the SS / PBCH block. k SSB .

[0443] For example, the configuration related to CORESET can be determined by the controlResourceSetZero included in the PDCCH-ConfigSIB1 parameter within the MIB. controlResourceSetZero represents one of the indices 0 to 15 in Table 9. k SSB This can be indicated by the ssb-SubcarrierOffset parameter in the MIB. The ssb-SubcarrierOffset parameter can be set to an integer from 0 to 15.

[0444] k SSB It can be from a public resource block (e.g., in Table 8) The subcarrier offset from subcarrier 0 to the lowest numbered subcarrier of the punctured SS / PBCH block.

[0445] As mentioned above, it can be based on offset and k SSB Determine the relative position / gap between the punctured SS / PBCH block and the CORESET. For example, the number of RBs from the lowest RB of the CORESET to the RBs of the common resource block is determined by the offset, and the number of subcarriers from the lowest-numbered subcarrier of the common resource block to the lowest-numbered subcarrier of the punctured SS / PBCH block is determined by... k SSB Confirmed. When the SS / PBCH block and the CORESET's SCS are the same at 15 kHz, based on the offset and k SSB The interval of the sum must also be a multiple of SCS (15 kHz). The offsets that satisfy the above conditions will be described in detail below. k SSB The combination of .

[0446] According to one implementation, based on an offset of 0, k SSB It could be 8 (refer to) FIG. 19 In this case, the interval can be 120 kHz (8). 15 kHz). Based on an offset of 2, k SSB It can be 4 (refer to) FIG. 20 An RB is defined as 12 consecutive subcarriers. The spacing can be 420 kHz (2). 12 15 (=360) kHz+4 15 (=60) kHz).

[0447] According to one implementation, the synchronization grid can be associated with the operating frequency band. For a channel bandwidth of 3 MHz, the operating frequency band can be n26, n28, n31, n72, n85, n100, or n106.

[0448] The frequency position based on the synchronization grid can be determined based on the following equation.

[0449] [Equation]

[0450] Frequency position = N 600 kHz+M 50 kHz + 300 kHz

[0451] Here, N is an integer of 1 or greater, and M can be 1, 3, or 5.

[0452] It can be at 100 kHz intervals (e.g., in Table 11 below). Define the frequency based on the channel grid within the operating frequency band.

[0453] Table 11 below illustrates the operating frequency bands and channel grid-based frequencies (e.g., reference frequencies) according to conventional definitions.

[0454] [Table 11]

[0455] For example, the number of RBs based on a 3 MHz channel bandwidth can be 15.

[0456] For example, a punched SS / PBCH block can be based on 12 RBs.

[0457] The offsets related to the conditions of the SCS described with reference to Table 11 will be described in detail. k SSB Examples of combinations. When the channel bandwidth is 3 MHz and the operating frequency band is n106, the frequency based on the channel grid can be 938 MHz (5 187600 = 938,000 kHz). Since the channel bandwidth is 15 RB, the starting frequency of the channel bandwidth can be 938 MHz - 1.35 MHz (7.5 RB) = 936.65 MHz.

[0458] Considering the initial frequency FIG. 18The six intervals shown (20 kHz to 520 kHz) and the frequency positions of the six 12-RBSS / PBCH blocks (12-RB PBCH) can be 1) 937.75 MHz, 2) 937.85 MHz, 3) 937.95 MHz, 4) 938.05 MHz, 5) 938.15 MHz, and 6) 938.25 MHz. Among the six frequency positions, the frequency positions that can be calculated according to the equation are 1) 937.75 MHz, 5) 938.15 MHz, and 6) 938.25 MHz.

[0459]

[0460] Of the three frequency positions, the frequency position based on the interval (420 kHz) as a multiple of SCS is 5) 938.15 MHz. In other words, for a channel bandwidth of 3 MHz in the operating frequency band n106, according to MIB, the offset can be indicated as 2, and k SSB It can be indicated as 4.

[0461] A core set can include 12 or 15 RBs. The RBs included in a core set can be those obtained after drilling. This will be described in detail below.

[0462] For example, the number of RBs can be determined based on the configuration associated with CORESET. The number of RBs can be 12 or 24. For example, the number of RBs can be referenced in Table 9. .

[0463] According to one implementation, based on the number of RBs being 12, a CORESET can include 12 RBs. This implementation can employ method #1 and a method for supporting the new (non-drilled) 12-PRB CORESET #0.

[0464] According to one implementation, based on the number of RBs being 24, the CORESET may include 15 RBs obtained by punching holes in 9 of the 24 RBs. This implementation may be based on method #2 and the method for supporting punching 15-PRBCORESET #0.

[0465] The operations based on the above steps S2110 to S2120 can be performed by... FIG. 23 This can be achieved through a device. For example, UE 200 can control one or more transceivers 230 and / or one or more memories 240 to perform operations based on steps S2110 to S2120.

[0466] The above implementation method will be described in detail below from the perspective of base station operation.

[0467] Steps S2210 to S2220, which will be described later, correspond to FIG. 21 Steps S2110 to S2120 described herein. Considering this correspondence, repeated descriptions will be omitted. In other words, the specific description of the base station operation described later can be replaced with the corresponding base station operation... FIG. 21 Description / implementation method.

[0468] FIG. 22 This is a flowchart illustrating a method performed by a base station according to another embodiment of the present disclosure.

[0469] Reference FIG. 22 According to another embodiment of the present disclosure, the method performed by the base station includes: transmitting SS / PBCH block S2210 and transmitting PDCCH S2220.

[0470] In step S2210, the base station sends a synchronization signal / physical broadcast channel (SS / PBCH) block to the UE based on the synchronization grid for the channel bandwidth.

[0471] In step S2220, the base station sends the Physical Downlink Control Channel (PDCCH) to the UE based on the Control Resource Set (CORESET).

[0472] For example, offsets can be determined based on configurations associated with the CORESET (e.g., indexes in Table 9). Offsets can be defined from the smallest resource block (RB) index of the CORESET to the RB index associated with the SS / PBCH block. In other words, offsets can be values ​​in RB units.

[0473] According to one implementation, based on i) the channel bandwidth is 3 MHz, ii) the subcarrier spacing (SCS) of the SS / PBCH block is 15 kHz, and iii) the SCS of the CORESET is 15 kHz: the offset can be either i) 0 or ii) 2, and the RB index can be determined based on the first RB of the punctured SS / PBCH block.

[0474] The operations based on the above steps S2210 to S2220 can be performed by... FIG. 23 This can be achieved using a device. For example, base station 100 can control one or more transceivers 130 and / or one or more memories 140 to perform operations based on steps S2210 to S2220.

[0475] In the following text, refer to FIG. 23 Describes the apparatus to which embodiments of this disclosure are applicable (apparatus for implementing the methods / operations according to embodiments of this disclosure).

[0476] FIG. 23The configurations of the first and second devices according to embodiments of the present disclosure are illustrated.

[0477] The first device 100 may include a processor 110, an antenna unit 120, a transceiver 130, and a memory 140.

[0478] Processor 110 can perform baseband-related signal processing and includes a higher-layer processing unit 111 and a physical layer processing unit 115. Higher-layer processing unit 111 can handle operations at the MAC layer, RRC layer, or higher layers. Physical layer processing unit 115 can handle PHY layer operations. For example, if the first device 100 is a base station (BS) device in BS-UE communication, physical layer processing unit 115 can perform uplink receive signal processing, downlink transmit signal processing, etc. For example, if the first device 100 is a first UE device in UE-to-UE communication, physical layer processing unit 115 can perform downlink receive signal processing, uplink transmit signal processing, sidelink transmit signal processing, etc. In addition to performing baseband-related signal processing, processor 110 can also control the overall operation of the first device 100.

[0479] Antenna unit 120 may include one or more physical antennas, and if antenna unit 120 includes multiple antennas, MIMO transmission / reception is supported. Transceiver 130 may include a radio frequency (RF) transmitter and an RF receiver. Memory 140 may store information processed by processor 110, as well as software, operating system, and applications related to the operation of first device 100. Memory 140 may also include components such as buffers.

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

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

[0482] Processor 210 can perform baseband-related signal processing and includes a higher-layer processing unit 211 and a physical layer processing unit 215. Higher-layer processing unit 211 can handle operations at the MAC layer, RRC layer, or higher layers. Physical layer processing unit 215 can handle PHY layer operations. For example, if the second device 200 is a UE device in BS-UE communication, physical layer processing unit 215 can perform downlink receive signal processing, uplink transmit signal processing, etc. For example, if the second device 200 is a second UE device in inter-UE communication, physical layer processing unit 215 can perform downlink receive signal processing, uplink transmit signal processing, sidelink receive signal processing, etc. In addition to performing baseband-related signal processing, processor 210 can also control the overall operation of the second device 200.

[0483] Antenna unit 220 may include one or more physical antennas, and if antenna unit 220 includes multiple antennas, MIMO transmission / reception is supported. Transceiver 230 may include an RF transmitter and an RF receiver. Memory 240 may store information processed by processor 210, as well as software, operating system, and applications related to the operation of second device 200. Memory 240 may also include components such as buffers.

[0484] In the embodiments described in this disclosure, the processor 210 of the second device 200 may 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).

[0485] The descriptions of the BS and UE (or the first UE device and the second UE device in inter-UE communication) in the examples of this disclosure are equivalent to those for the operation of the first device 100 and the second device 200, and redundant descriptions are omitted.

[0486] In addition to LTE, NR, and 6G, the wireless communication technologies implemented in apparatus 100 and apparatus 200 according to this disclosure may also include narrowband Internet of Things (NB-IoT) for low-power communication. For example, NB-IoT technology may be an example of low-power wide-area network (LPWAN) technology and may be implemented in standards such as LTE Cat NB1 and / or LTE Cat NB2. NB-IoT technology is not limited to the names mentioned above.

[0487] Additionally or alternatively, the wireless communication technology implemented in apparatus 100 and apparatus 200 according to this disclosure may be based on LTE-M technology to perform communication. For example, LTE-M technology may be an example of LPWAN technology and may be referred to by various names, such as enhanced machine-type communication (eMTC). For example, LTE-M technology may be implemented using 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. LTE-M technology is not limited to the names mentioned above.

[0488] Additionally or alternatively, considering low-power communication, the wireless communication technologies implemented in apparatus 100 and apparatus 200 according to this disclosure may include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN), and are not limited to the aforementioned names. For example, ZigBee technology can be based on various standards such as IEEE 802.15.4 to create personal area networks (PANs) associated with small / low-power digital communication, and may be referred to by various names.

Claims

1. A method performed by a user equipment (UE), the method comprising the following steps: Based on the synchronization grid received for channel bandwidth, the synchronization signal / physical broadcast channel SS / PBCH block is used. as well as The Physical Downlink Control Channel (PDCCH) is received based on the Control Resource Set (CORESET). The offset is determined based on the configuration associated with the CORESET. The offset is defined from the minimum resource block RB index of the CORESET to the RB index associated with the SS / PBCH block. Wherein, i) the channel bandwidth is 3 MHz, ii) the subcarrier spacing (SCS) of the SS / PBCH block is 15 kHz, and iii) the SCS of the CORESET is 15 kHz: The offset is one of i) 0 and ii) 2. The RB index is determined based on the first RB of the punched SS / PBCH block.

2. The method according to claim 1, wherein, The RB index is the minimum RB index of the common resource block that overlaps with the first RB of the punched SS / PBCH block.

3. The method according to claim 2, wherein, i) the configuration associated with the CORESET and ii) k SSB It is based on the Master Information Block (MIB) indication associated with the SS / PBCH block. Among them, the k SSB It is the subcarrier offset from subcarrier 0 in the public resource block to the lowest numbered subcarrier of the punctured SS / PBCH block.

4. The method according to claim 3, wherein, Based on the fact that the offset is 0, the k SSB It is 8, and Based on the offset being 2, the k SSB It is 4.

5. The method according to claim 1, wherein, The offset is defined relative to the SCS of the CORESET.

6. The method according to claim 1, wherein, The synchronization grid is related to the operating frequency band.

7. The method according to claim 6, wherein, For the channel bandwidth of 3 MHz, the operating frequency band is n26, n28, n31, n72, n85, n100, or n106.

8. The method according to claim 7, wherein, The frequency position based on the synchronization grid is determined based on the following equation: [Equation] Frequency position = N × 600 kHz + M × 50 kHz + 300 kHz Where N is an integer greater than or equal to 1, and M can be 1, 3 or 5.

9. The method according to claim 8, wherein, Within the operating frequency band, frequencies based on the channel grid are defined at 100 kHz intervals.

10. The method according to claim 1, wherein, The number of RBs based on the 3 MHz channel bandwidth is 15.

11. The method according to claim 1, wherein, After the drilling, the SS / PBCH block is based on 12 RBs.

12. The method according to claim 1, wherein, The number of RBs is determined based on the configuration associated with the CORESET, and The number of RBs is 12 or 24.

13. The method according to claim 12, wherein, The number of RBs is 24, and the CORESET includes 15 RBs obtained by punching holes in 9 of the 24 RBs.

14. A user equipment (UE), the UE comprising: One or more transceivers; One or more processors; as well as One or more memories, said one or more memories being connected to said one or more processors and storing instructions. The instructions are based on the one or more processors being executed to configure the one or more processors to perform all the steps of the method according to any one of claims 1 to 13.

15. An apparatus comprising: One or more memory units; as well as One or more processors, said one or more processors being operatively connected to said one or more memories, The one or more memory storage instructions are based on the one or more processors executing to configure the one or more processors to perform all the steps of the method according to any one of claims 1 to 13.

16. One or more non-transitory computer-readable media storing instructions, in, The instructions, which can be executed 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 13.

17. A method performed by a base station, the method comprising: Synchronization signals / physical broadcast channel SS / PBCH blocks are transmitted based on the synchronization grid for the channel bandwidth; as well as The Physical Downlink Control Channel (PDCCH) is transmitted based on the Control Resource Set (CORESET). The offset is determined based on the configuration associated with the CORESET. The offset is defined from the minimum resource block RB index of the CORESET to the RB index associated with the SS / PBCH block. Wherein, i) the channel bandwidth is 3 MHz, ii) the subcarrier spacing (SCS) of the SS / PBCH block is 15 kHz, and iii) the SCS of the CORESET is 15 kHz: The offset is one of i) 0 and ii) 2. The RB index is determined based on the first RB of the punched SS / PBCH block.

18. A base station, the base station comprising: One or more transceivers; One or more processors; as well as One or more memories, said one or more memories being connected to said one or more processors and storing instructions. The instructions are based on the one or more processors executing to configure the base station to perform all the steps of the method according to claim 17.

Images