Method, apparatus and computer program

Abstract

There is provided an apparatus comprising means for detecting a primary synchronization signal and a secondary synchronization signal transmitted from a network node; and means for determining the number of resource blocks allocated for the physical broadcast channel using the detected primary synchronization signal and secondary synchronization signal. The apparatus further comprises means for determining a lowest frequency resource block of the physical broadcast channel; and means for determining the lowest frequency resource block of the control resource set 0CORESET # 0 as the same as the determined lowest resource block of the physical broadcast channel.

Description

[0001] Cross - reference to related applications

[0002] This application claims the priority and benefit of UK Application No. 2214243.4, filed on September 29, 2022, which is incorporated herein by reference in its entirety. Technical field

[0003] This application relates to a method, device, and computer program for a wireless communication system. Background art

[0004] A communication system can be a facility that enables a communication session between two or more entities (such as user terminals, base stations / access points, and / or other nodes) by providing a carrier between various entities involved in the communication path. The communication system can be provided, for example, by means of a communication network and one or more compatible communication devices. The communication session can include, for example, communication for carrying data for communication (such as voice, email, text messages, multimedia, and / or content data, etc.). Non - limiting examples of the services provided include two - way or multi - way calls, data communication, or multimedia services, and access to a data network system (such as the Internet). Summary of the invention

[0005] According to one aspect, there is provided a device including: means for detecting a primary synchronization signal and a secondary synchronization signal transmitted from a network node; means for using the detected primary synchronization signal and secondary synchronization signal to determine the number of resource blocks allocated for a physical broadcast channel; means for determining the lowest - frequency resource block of the physical broadcast channel; and means for determining the lowest - frequency resource block of control resource set 0 (CORESET#0) to be the same as the determined lowest resource block of the physical broadcast channel.

[0006] In one example, the means for determining the lowest - frequency resource block on which the physical broadcast channel is transmitted includes: means for determining, after puncturing the resource blocks, the lowest - frequency resource block on which the physical broadcast channel is transmitted from the network node.

[0007] In one example, the device includes: means for determining the valid resource blocks of CORESET#0 by aligning with the valid resource blocks of the physical broadcast channel to determine the size of CORESET#0; and means for determining the control channel element allocation of CORESET#0 based on i) the lowest resource block and ii) the valid resource blocks of CORESET#0.

[0008] In one example, the device includes: means for communicating with the network node using the determined CORESET#0.

[0009] In one example, the device includes: means for demodulating and decoding an associated physical broadcast channel in response to detecting a primary synchronization signal and a secondary synchronization signal.

[0010] In one example, the physical broadcast channel is associated with the detected primary synchronization signal and secondary synchronization signal.

[0011] In one example, the means for determining the valid resource blocks of CORESET#0 includes: means for determining that the valid resource blocks of CORESET#0 are the resource blocks having complete control channel units.

[0012] In one example, the means for determining the valid resource blocks of CORESET#0 includes: means for determining that the valid resource blocks of CORESET#0 are the resource blocks covering fifteen resource blocks having complete and partial control channel units.

[0013] In one example, the means for determining the size of CORESET#0 includes one of the following: means for determining the maximum number of complete control channel units suitable for fifteen resource blocks; means for determining the maximum number of complete and partial control channel units suitable for fifteen resource blocks; means for determining the number of complete control channel units using a predetermined number of control channel units; means for determining the number of resource blocks using a predefined multiple of six resource blocks higher than a total of fifteen resource blocks.

[0014] In one example, the means for determining the control channel unit allocation of CORESET#0 includes: means for determining the control channel unit allocation of CORESET#0 using non-interleaved control channel unit mapping.

[0015] In one example, the device includes: means for determining an index providing information on the control channel unit allocation within the valid resource blocks of CORESET#0 using the physical broadcast channel in response to determining the valid resource blocks of CORESET#0.

[0016] In one example, the device includes: means for receiving a configuration associated with a physical downlink control channel from a network node; and means for determining CORESET#0 of all search spaces using CORESET#0 in an initial bandwidth part in response to the reception.

[0017] In one example, the device includes: means for receiving, from a network node, a configuration associated with a physical downlink control channel; and means for, after receiving the configuration, using parameters included within the configuration to determine an additional CORESET #0, the additional CORESET #0 being applied to all other search spaces using CORESET #0 except for the Type0 PDCCH search space, wherein the additional CORESET #0 used by the other search spaces is wider in frequency than the CORESET #0 used by the Type0-PDCCH, and wherein the additional CORESET #0 includes resource blocks used by the CORESET #0 applied to the Type0 PDCCH search space.

[0018] In one example, the device includes: means for receiving, from a network node, a configuration associated with a physical downlink control channel; and means for using one or more parameters included within the configuration associated with the physical downlink control channel to determine whether one of a lower frequency edge or a higher frequency edge of CORESET #0 will be aligned with resource blocks of a physical broadcast channel.

[0019] In one example, the device includes: means for using detected primary synchronization signals and secondary synchronization signals to determine a channel bandwidth on which a network node is operating.

[0020] In one example, the means for determining includes means for using detected primary synchronization signals and secondary synchronization signals to determine synchronization grid points to determine a channel bandwidth on which a network node is operating.

[0021] In one example, the channel bandwidth is determined to be three megahertz.

[0022] In one example, there are fifteen resource blocks available for the physical broadcast channel.

[0023] In one example, one of the following: the device is for a user equipment, the device is located within a user equipment, or the device is a user equipment.

[0024] According to one aspect, there is provided a device including: at least one processor and at least one memory, the at least one memory storing instructions that, when executed by one or more processors, cause the device to perform the following operations: detect primary synchronization signals and secondary synchronization signals transmitted from a network node; use the detected primary synchronization signals and secondary synchronization signals to determine a number of resource blocks allocated for a physical broadcast channel; determine a lowest frequency resource block of the physical broadcast channel; and determine a lowest frequency resource block of control resource set 0 CORESET #0 to be the same as the determined lowest resource block of the physical broadcast channel.

[0025] In one example, determining the lowest-frequency resource block on which the physical broadcast channel is transmitted includes: after puncturing the resource blocks, determining from a network node the lowest-frequency resource block on which the physical broadcast channel is transmitted.

[0026] In one example, causing the device to perform: determining the valid resource blocks of CORESET#0 by aligning with the valid resource blocks of the physical broadcast channel to determine the size of CORESET#0; and determining the control channel element allocation of CORESET#0 based on i) the lowest resource block and ii) the valid resource blocks of CORESET#0.

[0027] In one example, causing the device to perform: communicating with a network node using the determined CORESET#0.

[0028] In one example, causing the device to perform: demodulating and decoding an associated physical broadcast channel in response to detecting a primary synchronization signal and a secondary synchronization signal.

[0029] In one example, the physical broadcast channel is associated with the detected primary synchronization signal and secondary synchronization signal.

[0030] In one example, determining the valid resource blocks of CORESET#0 includes: determining that the valid resource blocks of CORESET#0 are resource blocks with complete control channel elements.

[0031] In one example, determining the valid resource blocks of CORESET#0 includes: determining that the valid resource blocks of CORESET#0 are resource blocks covering fifteen resource blocks with complete and partial control channel elements.

[0032] In one example, determining the size of CORESET#0 includes one of the following: determining the maximum number of complete control channel elements suitable for fifteen resource blocks; determining the maximum number of complete and partial control channel elements suitable for fifteen resource blocks; determining the number of complete control channel elements using a predetermined number of control channel elements; determining the number of resource blocks using a predefined multiple of six resource blocks higher than a total of fifteen resource blocks.

[0033] In one example, determining the control channel element allocation of CORESET#0 includes: determining the control channel element allocation of CORESET#0 using non-interleaved control channel element mapping.

[0034] In one example, causing the device to perform: in response to determining the valid resource blocks of CORESET#0, using the physical broadcast channel to determine an index providing information about the control channel element allocation within the valid resource blocks of CORESET#0.

[0035] In one example, cause the device to perform: receive a configuration associated with a physical downlink control channel from a network node; and in response to the reception, determine CORESET #0 for all search spaces using CORESET #0 in an initial bandwidth part.

[0036] In one example, cause the device to perform: receive a configuration associated with a physical downlink control channel from a network node; and after receiving the configuration, determine an additional CORESET #0 using parameters included within the configuration, the additional CORESET #0 being applied to all other search spaces that use CORESET #0 except for the Type0 PDCCH search space, wherein the additional CORESET #0 used by the other search spaces is wider in frequency than the CORESET #0 used by the Type0-PDCCH, and wherein the additional CORESET #0 includes resource blocks used by the CORESET #0 applied to the Type0 PDCCH search space.

[0037] In one example, cause the device to perform: receive a configuration associated with a physical downlink control channel from a network node; and use one or more parameters included within the configuration associated with the physical downlink control channel to determine whether either the lower frequency edge or the higher frequency edge of CORESET #0 will be aligned with a resource block of a physical broadcast channel.

[0038] In one example, cause the device to perform: determine a channel bandwidth on which a network node is operating using detected primary and secondary synchronization signals.

[0039] In one example, the determining includes: determining a synchronization grid point using the detected primary and secondary synchronization signals to determine a channel bandwidth on which a network node is operating.

[0040] In one example, the channel bandwidth is determined to be three megahertz.

[0041] In one example, there are fifteen resource blocks available for a physical broadcast channel.

[0042] In one example, one of the following: the device is for a user equipment, the device is located within a user equipment, or the device is a user equipment.

[0043] According to one aspect, there is provided a method including: detecting a primary synchronization signal and a secondary synchronization signal transmitted from a network node; using the detected primary and secondary synchronization signals to determine a number of resource blocks allocated for a physical broadcast channel; determining a lowest frequency resource block of the physical broadcast channel; and determining a lowest frequency resource block of control resource set 0 CORESET #0 to be the same as the determined lowest resource block of the physical broadcast channel.

[0044] In one example, determining the lowest-frequency resource block on which a physical broadcast channel is transmitted includes: after puncturing the resource blocks, determining from a network node the lowest-frequency resource block on which the physical broadcast channel is transmitted.

[0045] In one example, the method includes: determining the valid resource blocks of CORESET#0 by aligning with the valid resource blocks of the physical broadcast channel to determine the size of CORESET#0; and determining the control channel element allocation of CORESET#0 based on i) the lowest resource block and ii) the valid resource blocks of CORESET#0.

[0046] In one example, the method includes: communicating with a network node using the determined CORESET#0.

[0047] In one example, the method includes: demodulating and decoding an associated physical broadcast channel in response to detecting a primary synchronization signal and a secondary synchronization signal.

[0048] In one example, the physical broadcast channel is associated with the detected primary synchronization signal and secondary synchronization signal.

[0049] In one example, determining the valid resource blocks of CORESET#0 includes: determining that the valid resource blocks of CORESET#0 are resource blocks with complete control channel elements.

[0050] In one example, determining the valid resource blocks of CORESET#0 includes: determining that the valid resource blocks of CORESET#0 are resource blocks covering fifteen resource blocks with complete and partial control channel elements.

[0051] In one example, determining the size of CORESET#0 includes one of the following: determining the maximum number of complete control channel elements suitable for fifteen resource blocks; determining the maximum number of complete and partial control channel elements suitable for fifteen resource blocks; determining the number of complete control channel elements using a predetermined number of control channel elements; determining the number of resource blocks using a predefined multiple of six resource blocks higher than a total of fifteen resource blocks.

[0052] In one example, determining the control channel element allocation of CORESET#0 includes: determining the control channel element allocation of CORESET#0 using non-interleaved control channel element mapping.

[0053] In one example, the method includes: in response to determining the valid resource blocks of CORESET#0, using the physical broadcast channel to determine an index providing information about the control channel element allocation within the valid resource blocks of CORESET#0.

[0054] In one example, the method includes: receiving, from a network node, a configuration associated with a physical downlink control channel; and in response to the receiving, determining CORESET #0 for all search spaces using CORESET #0 in an initial bandwidth part.

[0055] In one example, the method includes: receiving, from a network node, a configuration associated with a physical downlink control channel; and after receiving the configuration, determining an additional CORESET #0 using parameters included within the configuration, the additional CORESET #0 being applied to all other search spaces that use CORESET #0 other than the Type0 PDCCH search space, wherein the additional CORESET #0 used by the other search spaces is wider in frequency than the CORESET #0 used by the Type0-PDCCH, and wherein the additional CORESET #0 includes resource blocks used by the CORESET #0 applied to the Type0 PDCCH search space.

[0056] In one example, the method includes: receiving, from a network node, a configuration associated with a physical downlink control channel; and using one or more parameters included within the configuration associated with the physical downlink control channel to determine whether either a lower frequency edge or a higher frequency edge of CORESET #0 will be aligned with resource blocks of a physical broadcast channel.

[0057] In one example, the method includes: determining a channel bandwidth on which a network node is operating using detected primary synchronization signals and secondary synchronization signals.

[0058] In one example, the determining includes: determining synchronization grid points using detected primary synchronization signals and secondary synchronization signals to determine a channel bandwidth on which a network node is operating.

[0059] In one example, the channel bandwidth is determined to be three megahertz.

[0060] In one example, there are fifteen resource blocks available for a physical broadcast channel.

[0061] In one example, the method is performed by a user equipment.

[0062] According to one aspect, there is provided a computer program comprising instructions which, when executed by a device, cause the device to perform at least the following operations: detecting a primary synchronization signal and a secondary synchronization signal transmitted from a network node; using the detected primary synchronization signal and secondary synchronization signal to determine the number of resource blocks allocated for a physical broadcast channel; determining the lowest-frequency resource block of the physical broadcast channel; and determining the lowest-frequency resource block of control resource set 0 (CORESET#0) to be the same as the determined lowest resource block of the physical broadcast channel.

[0063] According to one aspect, there is provided a computer program comprising instructions stored thereon to perform at least the following operations: detecting a primary synchronization signal and a secondary synchronization signal transmitted from a network node; using the detected primary synchronization signal and secondary synchronization signal to determine the number of resource blocks allocated for a physical broadcast channel; determining the lowest-frequency resource block of the physical broadcast channel; and determining the lowest-frequency resource block of control resource set 0 (CORESET#0) to be the same as the determined lowest resource block of the physical broadcast channel.

[0064] According to one aspect, there is provided a non-transitory computer-readable medium comprising program instructions which, when executed by a device, cause the device to perform at least the following operations: detecting a primary synchronization signal and a secondary synchronization signal transmitted from a network node; using the detected primary synchronization signal and secondary synchronization signal to determine the number of resource blocks allocated for a physical broadcast channel; determining the lowest-frequency resource block of the physical broadcast channel; and determining the lowest-frequency resource block of control resource set 0 (CORESET#0) to be the same as the determined lowest resource block of the physical broadcast channel.

[0065] A computer product stored on a medium can cause a device to perform the methods described herein.

[0066] A non-transitory computer-readable medium comprises program instructions which, when executed by a device, cause the device to perform the methods described herein.

[0067] An electronic device may include a device as described herein.

[0068] Above, various aspects have been described. It should be understood that additional aspects can be provided by any combination of two or more of the above various aspects.

[0069] Various other aspects and additional embodiments are also described in the following detailed description and the appended claims.

[0070] According to some aspects, the subject matter of the independent claims is provided. Some additional aspects are defined in the dependent claims. Embodiments not within the scope of the claims should be construed as examples useful for understanding the present disclosure.

[0071] Abbreviation List:

[0072] AF: Application Function

[0073] AL: Aggregation Level

[0074] AMF: Access and Mobility Management Function

[0075] AN: Access Network

[0076] BD: Blind Detection

[0077] BS: Base Station

[0078] BW: Bandwidth

[0079] CBW: Channel Bandwidth

[0080] CCE: Control Channel Element

[0081] CORESET: Control Resource Set

[0082] CN: Core Network

[0083] DL: Downlink

[0084] DMRS: Demodulation Reference Signal

[0085] eNB: eNodeB

[0086] FR1: Frequency Range 1

[0087] FRMCS: Future Railway Mobile Communication System

[0088] gNB: gNodeB

[0089] GSCN: Global Synchronization Channel Number

[0090] GSM-R: Global System for Mobile Communications - Railway

[0091] IIoT: Industrial Internet of Things

[0092] LTE: Long Term Evolution

[0093] MS: Mobile Station

[0094] MIB: Master Information Block

[0095] NEF: Network Exposure Function

[0096] NG-RAN: Next Generation Radio Access Network

[0097] NF: Network Function

[0098] NR: New Radio

[0099] NRF: Network Repository Function

[0100] NW: Network

[0101] PBCH: Physical Broadcast Channel

[0102] PDCCH: Physical Downlink Control Channel

[0103] PCF Policy Control Function

[0104] PLMN: Public Land Mobile Network

[0105] PRB: Physical Resource Block

[0106] PSS: Primary Synchronization Signal

[0107] RAN: Radio Access Network

[0108] RE: Resource Element

[0109] REG: Resource Element Group

[0110] RF: Radio Frequency

[0111] SCS: Subcarrier Spacing

[0112] SI: System Information

[0113] SIB: System Information Block

[0114] SMF: Session Management Function

[0115] SS: Synchronization Signal

[0116] SSB: Synchronization Signal Block

[0117] SSREF: Frequency Position of Synchronization Signal

[0118] SSS: Secondary Synchronization Signal

[0119] UE: User Equipment

[0120] UDR: Unified Data Repository

[0121] UDM: Unified Data Management

[0122] UL: Uplink

[0123] UPF: User Plane Function

[0124] 3GPP: 3rd Generation Partnership Project

[0125] 5G: 5th Generation

[0126] 5GC: 5G Core Network

[0127] 5G-AN: 5G Radio Access Network 5GS: 5G System Description of the Drawings

[0128] The embodiments will now be described by way of example only with reference to the accompanying drawings, in which:

[0129] Figure 1 A schematic diagram of a 5G system is shown;

[0130] Figure 2 A schematic diagram of a control device is shown;

[0131] Figure 3 A schematic diagram of a terminal is shown;

[0132] Figure 4 A schematic diagram of an existing New Radio initial access signal and channel with a 15 kHz subcarrier spacing is shown;

[0133] Figure 5 A schematic diagram of different puncturing patterns of a synchronization signal block is shown;

[0134] Figure 6 An example representation of CORESET resource allocation including resource block offset is shown;

[0135] Figure 7 A schematic diagram of the CORESET 0 configuration within the initial bandwidth part of 22 physical resource blocks is shown;

[0136] Figure 8a Another schematic diagram of the CORESET 0 configuration within the initial bandwidth part of 20 physical resource blocks with an offset of 2 control channel units is shown;

[0137] Figure 8b Another schematic diagram of the CORESET 0 configuration within the initial bandwidth part of 24 physical resource blocks with an offset of 2 control channel units is shown;

[0138] Figure 9a and Figure 9b A schematic diagram of the alignment between the valid physical resource blocks of the physical broadcast channel and the valid physical resource blocks of CORES ET 0 is shown;

[0139] Figure 10 A schematic diagram of CORESET 0 size determination and CCE allocation options is shown;

[0140] Figure 11 Another example method flowchart executed by a user equipment is shown; and

[0141] Figure 12A schematic diagram of a non-volatile memory medium storing instructions which, when executed by a processor, allow the processor to execute Figure 11 one or more steps of the method of Detailed implementation mode

[0142] Before explaining some examples of the present disclosure in detail, refer to Figures 1 to 3 Briefly explain some general principles of wireless communication systems and mobile communication devices to help understand the underlying technology of the described examples.

[0143] In a wireless communication system such as Figure 1 as shown in the wireless communication system 100, wireless access is provided to a mobile communication device / terminal or user equipment, and / or user equipment (UE), and / or machine-type communication device 102 via at least one base station (not shown) or similar wireless transmitting and / or receiving node or point. The communication device is equipped with appropriate signal receiving and transmitting equipment for realizing communication (e.g., realizing access to a communication network and / or direct communication with other devices). The communication device can access a carrier provided by a station or access point and transmit and / or receive communication on the carrier.

[0144] Hereinafter, some examples are explained with reference to a mobile communication device capable of communicating via a wireless cellular system and a mobile communication system serving such a mobile communication device. Before explaining the examples of the present disclosure in detail, refer to Figure 1 、 Figure 2 and Figure 3 Briefly explain some general principles of wireless communication systems, their access systems and mobile communication devices to help understand the underlying technology of the described examples.

[0145] Figure 1 A schematic diagram of a 5G system (5GS) 100 is shown. The 5GS may include a device 102, such as a user equipment or terminal, a 5G radio access network (5G-RAN) 106, a 5G core network (5GC) 104, one or more network functions (NF), one or more application functions (AF) 108, and one or more data networks (DN) 110.

[0146] The 5G-RAN 106 may include one or more gNodeB (gNB) distributed unit functions connected to one or more gNodeB (gNB) centralized unit functions.

[0147] 5GC 104 may include an Access and Mobility Management Function (AMF) 112, a Session Management Function (SMF) 114, an Authentication Server Function (AUSF) 116, a User Data Management (UDM) 118, a User Plane Function (UPF) 120, a Network Exposure Function (NEF) 122, and / or other NFs. Some of the examples shown below may apply to the 3GPP 5G standards, including 5G-Advanced. However, some examples may also apply to 4G, 3G, and other 3GPP standards.

[0148] In a communication system such as Figure 1 shown, wireless access is provided to a mobile communication device / terminal or user equipment, and / or user equipment (UE), and / or machine-type communication device via at least one base station or similar wireless transmitting and / or receiving node or point. The terminal is equipped with appropriate signal receiving and transmitting equipment for implementing communication (e.g., implementing access to a communication network or direct communication with other devices). The communication device can access a carrier provided by a base station or access point and transmit and / or receive communication on the carrier.

[0149] Figure 2 An example of a control device 200 for controlling the functions of a 5G-RAN or 5GC such as Figure 1 shown is presented. The control device may include at least one Random Access Memory (RAM) 211a, at least one Read-Only Memory (ROM) 211b, at least one processor 212, 213, and an input / output interface 214. The at least one processor 212, 213 may be coupled to the RAM 211a and the ROM 211b. The at least one processor 212, 213 may be configured to execute appropriate software code 215. The software code 215 may, for example, allow the execution of one or more steps to perform one or more of the aspects of the present invention. The software code 215 may be stored in the ROM 211b. The control device 200 may be interconnected with another control device 200 that controls another function of the 5G-AN or 5GC. In some examples, each function of the 5G-AN or 5GC includes a control device 200. In alternative examples, two or more functions of the 5G-AN or 5GC may share a control device.

[0150] Figure 3 An example of a terminal 300 such as Figure 1An example of the terminal shown). The terminal 300 can be provided by any device capable of sending and receiving radio signals. Non-limiting examples include user equipment, a mobile station (MS) or a mobile device (such as a mobile phone or a so-called 'smartphone'), a computer equipped with a wireless interface card or other wireless interface facilities (e.g., a USB dongle), a personal digital assistant (PDA) or a tablet computer with wireless communication capabilities, a machine-type communication (MTC) device, a cellular Internet of Things (CIoT) device, or any combination of these devices, etc. The terminal 300 can provide, for example, communication for carrying data of a communication. The communication can be one or more of voice, email, text message, multimedia, data, machine data, etc.

[0151] The terminal 300 can receive signals via an appropriate device for reception over the air or a radio interface 307, and can transmit signals via an appropriate device for transmitting radio signals. In Figure 3 it, the transceiver device is schematically marked by the block 306. The transceiver device 306 can be provided, for example, by means of a radio part and an associated antenna arrangement. The antenna arrangement can be arranged inside or outside the mobile device.

[0152] The terminal 300 can include at least one processor 301, at least one memory ROM 302a, at least one RAM 302b, and other possible components 303 for use in the software and hardware assisted execution of the tasks it is designed to perform, the tasks including controlling access to an access system and other communication devices and communicating with the access system and other communication devices. The at least one processor 301 is coupled to the RAM 302b and the ROM 302a. The at least one processor 301 can be configured to execute appropriate software code 308. The software code 308 can, for example, allow the execution of one or more of the aspects of the present invention. The software code 308 can be stored in the ROM 302a.

[0153] The processor, storage device, and other related control devices can be provided on an appropriate circuit board and / or chipset. This feature is marked by the reference numeral 304. The device can optionally have a user interface, such as a keypad 305, a touch-sensitive screen or a touchpad, a combination thereof, etc. Optionally, one or more of a display, a speaker, and a microphone can be provided depending on the type of the device.

[0154] One or more of the following examples apply to or are related to narrowband new radio operation (NB NR), including NR support for dedicated spectra less than 5 MHz. This is an emerging scenario driven by, for example, the needs of railway communication (globally), US smart grid operators, and European public safety.

[0155] The Future Railway Mobile Communication System (FRMCS) in Europe has the following considerations: It is agreed to use NR in the 2x5.6 MHz FDD (874.4 - 880 MHz / 919.4 - 925 MHz) band. The soft migration from Global System for Mobile Communications - Railway (GSM-R) requires the parallel operation of GSM-R and NR in the band, and it is expected to last for about 10 years (~2025 - ~2035). In some scenarios, it is assumed that a 3 MHz channel can be allocated to NR. For NR downlink (DL) / uplink (UL) and GSM-R DL / UL, potential deployment scenarios include: adjacent channel deployment, coverage deployment with compact GSM-R channel placement, coverage deployment with GSM-R channels distributed over a 4 MHz core band, and coverage deployment with GSM-R channels distributed over the full Extended Railway GSM (ER-GSM) band. The adjacent channel deployment of NR and GSM-R may have the advantage that the NR scheduler is easier to implement, and there is only one boundary between NR and GSM-R, enabling simpler and more predictable coexistence.

[0156] Narrowband NR has also been considered for the 'Smart Grid', including 2x3 MHz Frequency Division Duplex (FDD) in the 900 MHz band in the United States. NB NR has also been considered for public safety applications, including 2x3 MHz FDD in Band 28 for Public Protection and Disaster Relief (PPDR) in Europe.

[0157] In NR Rel-15 to Rel-17, channel bandwidths (CBW) below 5 MHz are not currently supported. It has been proposed to adapt NR to 3 - 5 MHz spectrum allocation with minimal changes based on the existing NR ecosystem.

[0158] It has been identified that in emerging scenarios, it may be beneficial to operate 5G NR in a bandwidth narrower than the initially designed 5 MHz channels. For example, operation as low as 3 MHz. For example, deploying NR in the 900 MHz Future Railway Mobile Communication System (FRMCS) band will operate with any traditional GSM-R carrier within a 5.6 MHz bandwidth, which allows approximately 3.6 MHz bandwidth for NR. Similarly, in some cases, a 3 MHz channel can be used for NR.

[0159] However, one or more signals and channels transmitted by an NR base station (gNB), including the signals and channels of the synchronization signal and the Physical Broadcast Channel (PBCH) block, are not designed for transmission in such narrow channels.

[0160] Figure 4 A schematic diagram of the existing NR initial access signals and channels with a 15 kHz subcarrier spacing is shown.

[0161] A block with a width (frequency domain) of 240 sub - carriers (SC) 401 is provided, which is equivalent to 20 physical resource blocks (PRB). Each PRB includes 12 SC. The height (time domain) of the block is 4 orthogonal frequency - division multiplexing (OFDM) symbols 403.

[0162] A total of 240 SC 401 are divided into a first bandwidth 405, a second bandwidth 407, and a third bandwidth 409. The first bandwidth 405 is 0.72 MHz and 48 SC (i.e., 4 PRB). The second bandwidth 407 is 2.16 MHz and 144 SC (i.e., 12 PRB). The third bandwidth 409 is 0.72 MHz and 48 SC (i.e., 4 PRB). Thus, the total bandwidth is 3.6 MHz.

[0163] In one of the 4 OFDM symbols, there is a primary synchronization signal (PSS) 411, which is 127 SC 413. In another of the 4 OFDM symbols, there is a secondary synchronization signal (SSS) 415, which is also 127 SC 413.

[0164] The PBCH 417 is provided in three OFDM symbols. The PBCH is provided across all SC of the block in some OFDM symbols and across a partial number of SC out of the total SC in another OFDM symbol.

[0165] The UE can receive signals and channels as Figure 4 shown. After detecting the PSS and SSS, in addition to the physical cell identity (ID) of the cell (from which the signal is transmitted), the UE can also know the slot timing and symbol timing within a 5 - millisecond (ms) half - frame. Then, the UE can determine the resource elements (RE) for the PBCH demodulation reference signal (DMRS) and data to receive the PBCH payload. The PBCH carries the master information block (MIB), and the MIB signals system information related to the frequency position (synchronization signal block frequency - domain allocation related to the common resource block (CRB) grid) and timing (half - frame timing and frame timing). This information can be included in the higher - layer payload (i.e., the MIB), as part of the physical - layer bits in the transport - block payload, or included in the DMRS.

[0166] Allocating 3 MHz for the NR system would be equivalent to a maximum 15 PRB channel bandwidth. This would assume 90% spectrum utilization. For the Synchronization Signal Block (SSB), this would result in 5 PRB puncturing. Puncturing of the transmitted signal is used to reduce the transmission bandwidth with minimal changes. In the puncturing operation, the base station clears any signals beyond the required transmission bandwidth that are mapped to certain predefined PRBs. In this way, the base station will not transmit those signals. When the UE receives a transmission with punctured PRBs, the UE can zero out the punctured PRBs at the receiver. The UE can zero out the punctured PRBs by, for example, setting the Log-Likelihood Ratio (LLR) to zero in the channel decoder.

[0167] In other examples, if the UE does not know the punctured PRBs, the UE can receive the transmission on all PRBs including the punctured PRBs used for transmission.

[0168] An alternative to puncturing is rate matching, whereby the input bits are matched to the available resources. Thus, the sequence of rate-matched bits varies according to the resource size. With rate matching, the receiver should know the resource size in order to correctly decode the packet.

[0169] Since the PSS / SSS should remain unaffected, in some examples, up to 4 PRB puncturing can be performed on each side of the SSB. In other words, some applicable puncturing patterns for 5 PRB puncturing include 1+4, 2+3, 3+2, 4+1, as Figure 5 shown.

[0170] As described above, Figure 4 signals and channels with a subcarrier spacing of 15 kHz are shown. Compared to other SCSs supported by NR, the 15 kHz subcarrier spacing (SCS) provides the minimum bandwidth (in MHz) for signals defined by a predefined number of RBs (such as, for example, the PBCH). Thus, the 15 kHz SCS is a suitable starting point when defining support for NR < 5 MHz. It should be understood that the following examples can also be applied to subcarrier spacings higher or lower than 15 kHz.

[0171] Figure 5 A schematic diagram showing different puncturing patterns of the Synchronization Signal Block is shown.

[0172] Four different puncturing patterns 501, 503, 505, 507 are shown. Each of the puncturing patterns 501, 503, 505, 507 is used for an SSB with 20 PRBs. Figure 5 Each block in represents one PRB. Two puncturing lines 509 passing through the PRBs are shown. The puncturing lines 509 intersect the PRBs of the four different puncturing patterns 501, 503, 505, 507. Blocks without a pattern (i.e., pure) indicate that they have been transmitted. Blocks with a pattern (i.e., hatched) indicate that they have been punctured.

[0173] The y-axis corresponding to the frequency is shown. The arrow on the y-axis indicates an increasing frequency.

[0174] In the first puncturing pattern 501, there is a '1 + 4' pattern. The first PRB (i.e., PRB 0) and the last four PRBs (i.e., PRBs 16 to 19) are punctured. The remaining PRBs for transmitting the SSB are transmitted.

[0175] In the second puncturing pattern 503, there is a '2 + 3' pattern. The first PRB and the second PRB (i.e., PRB 0 and PRB 1) and the last three PRBs (i.e., PRBs 17 to 19) are punctured. The remaining PRBs for transmitting the SSB are transmitted.

[0176] In the third puncturing pattern 505, there is a '3 + 2' pattern. The first three PRBs (i.e., PRBs 0 to PRB 2) and the last two PRBs (i.e., PRB 18 and PRB 19) are punctured. The remaining PRBs for transmitting the SSB are transmitted.

[0177] In the fourth puncturing pattern 507, there is a '4 + 1' pattern. The first four PRBs (i.e., PRBs 0 to PRB 3) and the last one PRB (i.e., PRB 19) are punctured. The remaining PRBs for transmitting the SSB are transmitted.

[0178] It should be understood that the SSB bandwidths of 20 PRBs and 15 PRBs are only used as examples respectively. In other examples, different puncturing patterns 501, 503, 505, 507 can be used to puncture SSBs of other suitable lengths into other suitable lengths.

[0179] A control resource set (CORESET) is a set of physical resources and a set of parameters used to carry the physical downlink control channel (PDCCH) / downlink control information. Functionally, it is conceptually equivalent to the LTE PDCCH region (the first 1, 2, 3, 4 OFDM symbols in a subframe). In the LTE PDCCH region, the PDCCH is distributed across the entire channel bandwidth, but the NR CORESET region is located in a specific region in the frequency domain.

[0180] For the CORESET, is the number of resource blocks (RBs) in the frequency domain of the CORESET. is the number of symbols in the time domain of the CORESET. is the number of resource element groups (REGs) in the CORESET. L is the REG bundle size, which can be set by the parameter CORESET-REG-bundle-size.

[0181] The UE can receive signals and channels as Figure 4 shown. First, the UE detects the PSS and SSS. Subsequently, the UE demodulates / decodes the PBCH. Then, the UE reads the configuration index from the PBCH / MIB. The configuration index refers to the CORESET #0 configuration table (such as Table 1 below), and more specifically, refers to certain time and frequency resource allocation parameters. One of the parameters defines the resource block (RB) offset between the first PRB of CORESET #0 and the first PRB where the first subcarrier of the SSB is located. This is shown in the fifth column of Table 1 below. The SSB is in the same subcarrier grid, but not necessarily in the same RB grid as CORESET #0.

[0182]

[0183]

[0184] Table 1: Resource block and time slot symbol sets of CORESET for Type0-PDCCH search space set when the {SS / PBCH block, PDCCH} SCS of the frequency band with a minimum channel bandwidth of 5 MHz or 10 MHz is {15, 15} kHz

[0185] Figure 6 An example representation of the CORESET resource allocation including the resource block offset is shown.

[0186] Figure 4 Signals and channels are provided in the block of. For convenience, Figure 6 the same labels as those used in Figure 4 are provided for this block.

[0187] A first CORESET configuration 601 with an offset of 0 is also provided. For example, for index 0 or index 3, the offset 0 can be determined according to Table 1. A second CORESET configuration 603 with an offset of 2 is also provided. For example, for index 1 or index 4, the offset 2 can be determined according to Table 1. A third CORESET configuration 605 with an offset of 4 is also provided. For example, for index 2 or index 4, the offset 4 can be determined according to Table 1. The offset is between the first PRB of CORESET #0 and the first PRB where the first subcarrier of the SSB (of the received block) is located.

[0188] The SSB is in the same subcarrier grid as the common RB grid, but may not be aligned at the RB level. The subcarrier offset between the SSB and the common RB grid is provided by the k_SSB parameter provided in the MIB. It has the following characteristics: The k_SSB parameter in FR1 has 5 bits, with values from 0 to 23, used to indicate the subcarrier offset between the SSB and the common RB grid, and when the SSB and CORESET #0 have the same SCS, values from 0 to 11 are used.

[0189] There is a special type of core set called CORESET 0 or CORESET #0. This CORESET is the core set for transmitting the PDCCH for SIB1 scheduling. Defining those CORESETS involves many parameters and those parameters are specified by radio resource control (RRC) messages. However, CORESET 0 cannot be specified by RRC because it should be used before any RRC messages are transmitted. This means that CORESET 0 should be configured by some predefined procedures and predefined parameters. Therefore, CORESET 0 is configured by a separate procedure and the predefined parameters summarized in the following table.

[0190]

[0191] Table 2: Parameters and Values for Determining CORESET 0

[0192] CORESET #0 can also be configured in PDCCH-ConfigCommon included within SIB1. Alternatively, CORESET #0 can be configured for the UE with dedicated signaling. In these cases, a 4-bit value can be used for configuration, and the value indicates the same table as the index provided in the MIB.

[0193] Since CORESET 0 is not configured using RRC signaling, it may be difficult to derive the CORESET 0 configuration in scenarios below 5 MHz. Especially in the NR scenario below 5 MHz. In some systems, the mechanisms to address these scenarios involve increasing the complexity of the UE and / or making significant modifications to the current standards / specifications. One or more of the following examples aim to minimize the complexity associated with determining the CORESET 0 configuration. Especially for scenarios involving a PBCH bandwidth of less than 20 RBs.

[0194] In the example, a method is provided where when determining the CORESET 0 (CORESET #0) configuration, the UE determines the lowest RB (in frequency) of the CORESET 0 configuration based on the determined lowest resource block (in frequency) of the PBCH.

[0195] The lowest RB of the PBCH can be the lowest RB on which the network transmits the PBCH. In some examples, the lowest RB of the PBCH can be the lowest RB on which the PBCH is transmitted after puncturing of the resource blocks. This determination of the lowest RB can be achieved due to the (new) interpretation of the "Offset (RB)" parameter in Table 1 above. This will be described in more detail below.

[0196] In some examples, it may be assumed that when determining the CORESET 0 configuration in this way, the channel bandwidth is 3 MHz. However, it should be understood that in some other examples, the CBW may be higher or lower than 3 MHz. The UE may determine the CBW after detecting the SSB. This may allow the UE to determine that the associated network node / cell operates according to a 3 MHz channel bandwidth (CBW). The CBW may be determined by the UE based on the determined synchronization grid points. In an example of 3 MHz CBW, based on this determination, the UE knows that there are 15 available RBs for the PBCH.

[0197] This determination of the CORESET 0 configuration will be described in more detail below.

[0198] In some examples, when determining the valid PRBs of the CORESET 0 configuration, the determination is made from the RBs valid for the PBCH, and the RBs defined as valid for CORESET 0 are defined by one of the following: i) The valid PRBs of CORESET 0 are the PRBs with a complete control channel element (CCE), and ii) The valid PRBs of CORESET 0 cover 15 PRBs (with complete and partial CCEs). For both options, the same result may be achieved when the number of symbols in the time domain of CORESET 0 is equal to two. For CORESET 0, the considered REG bundle size is 6. Thus, one CCE is 2 symbols multiplied by 3 RBs, or 3 symbols multiplied by 2 RBs. When defining the valid RBs of CORESET0, a 'complete' CCE is a CCE defined using the following resolution: 2-symbol CORESET is 3 RBs, or 3-symbol CORESET is 2 RBs.

[0199] In some examples, when determining the CORESET 0 configuration, the CORESET 0 size is modified by one of the following alternatives. The size modification may occur at least when monitoring the predefined search space. Examples of the predefined search space include Type0_PDCCH, Type0A_PDCCH, and Type2_PDCCH. The alternatives for the CORESET 0 size include one of the following: i) The number of RBs (in the frequency domain of the CORESET 0 configuration, i.e., ) is determined according to the maximum number of complete CCEs suitable for 15 PRBs, ii) The number of RBs is determined according to the maximum (complete or partial) number of CCEs suitable for 15 PRBs, iii) The number of RBs is determined according to the predefined number of complete CCEs (e.g., 8 CCEs), and iv) The number of RBs is a predefined multiple number of 6 RBs that is greater than or equal to 15 (e.g., 18 RBs).

[0200] In some examples, when determining the CORESET 0 configuration, the UE assumes that the CCEs involved follow non-interleaved CCE / non-interleaved CCE mapping. The PDCCH candidates include consecutive CCE indices. Thus, non-interleaved CCE results in consecutive frequency allocation of PDCCH candidates, which in turn can maximize the number of CCEs available for PDCCH candidates when the bandwidth is limited. In the current system, CORESET#0 only supports interleaved mapping. This limits the number of CCEs available for each PDCCH candidate in a 3 MHz bandwidth (15 RBs).

[0201] In some examples, after determining the valid PRBs of the CORESET 0 configuration, the UE determines an index from the PBCH, and the index provides the UE with information about the CCE allocation within the valid PRBs. The PBCH provides indices of predefined options, including: 2-symbol CORESET, 3-symbol CORESET (full CCE), 3-symbol CORESET with 1 RB offset (full) CCE, 3-symbol CORESET (partial CCE). This is shown in more detail in Figure 10 which is shown in more detail in

[0202] In some examples, after receiving PDCCH-ConfigCommon, the UE determines the CORESET 0 configuration according to one of the following: a) the same CORESET 0 determination (as described above) for all search spaces using CORESET 0 in the initial bandwidth part (BWP), b) for the initial BWP search spaces using CORESET 0 other than Type0_PDCCH, define a wider CORESET 0. CORESET 0 is defined based on the controlResourceSetZero index in PDCCH-ConfigCommon, and the interpretation of Table 1 (shown above) is as follows

[0203] A 'Offset (RB)' value of 0 (in Table 1) indicates that the lower edge of CORESET 0 is aligned with the non-punctured PBCH RB. A 'Offset (RB)' value of 4 indicates that the upper edge of CORESET 0 is aligned with the non-punctured PBCH RB. This is described in more detail below and shown in Figure 7 which is shown in

[0204] A 'Offset (RB)' value of 2 (in Table 1) indicates the CCE offset between the lower edge of CORESET 0 and the lower edge of the non-punctured PBCH. The CCE offset is an integer value. For example, the integer value is two. In other examples, the integer value is higher than two.

[0205] For an example table with the alternative values of Table 1, a ‘Offset (RB)’ value of 1 may indicate the CCE offset between the lower edge of CORESET 0 and the lower edge of the non-punctured PBCH. The CCE offset is an integer value. For example, the integer value is one. This can be seen in Figure 10 Configuration 1007, which will be described in further detail below. In other examples, the integer value is higher than one. This offset remains aligned with the CCEs of Type0_PDCCH CORESET 0 while essentially centering the CORESET#0 resources (relative to the PBCH).

[0206] In some examples, the number of RBs indicated in Table 1 (i.e., ‘Offset (RB)’) may be reduced to the number of valid RBs of the initial BWP. The valid PRBs can be defined according to options a) and b) defined above and applied to the RBs of the initial BWP. The offset of 2 CCEs using option a) for the valid RBs is shown in FIG. 8.

[0207] Figure 7 A schematic diagram of the CORESET 0 configuration within a 22PRB initial BWP is shown.

[0208] Figure 7 A 15PRB channel bandwidth (CBW) 701 is shown. The 15PRB CBW 701 corresponds to the PBCH. A sequence of 5 CCEs 703 is aligned with the 15PRB CBW 701 at the lower edge and the lower edge. The 5 CCEs 703 are a (2-symbol) CORESET 0 subset available for SIB1 scheduling 705.

[0209] ‘Point A’ labeled 707 is provided. An initial BWP offset 709 is provided from ‘Point A’ to the initial BWP PRB 711. The length of the initial BWP PRB is 22 PRBs. The higher edge of the initial BWP PRB is aligned with the 15PRB CBW 701 and the 5 CCEs 703.

[0210] A 2-symbol CORESET 0 configuration 713 is provided, which includes 7 CCEs and an invalid CCE 715 (at the lowest frequency). The 7 CCEs and 1 invalid CCE correspond to 24 PRBs. The invalid CCE 715 is invalid because only a single PRB is available in the initial BWP 711 instead of the 3 PRBs required for a CCE. Thus, the CORESET 0 configuration 717 includes 7 CCEs (or 21 PRBs). The higher edge of the CORESET 0 configuration 717 is aligned with the 15PRB CBW.

[0211] Figure 8aAnother schematic diagram showing the CORESET 0 configuration within the initial BWP of 20 PRBs, with an offset of 2 CCEs.

[0212] As discussed above, an 'offset (RB)' value of 2 indicates the CCE offset between the lower edge of CORESET 0 and the lower edge of the non-punctured PBCH. In Figure 8a the example, this CCE offset is 2.

[0213] Figure 8a Shows a 15 PRB CBW 801. A sequence of 5 CCEs 803 is aligned with the 15 PRB CBW 801 at the lower and upper edges. The 5 CCEs 803 are a (2-symbol) CORESET 0 subset for SIB1 scheduling 805.

[0214] Provides a 'point A' labeled 807. An initial BWP offset 809 is provided from 'point A' to the initial BWP PRB 811. The length of the initial BWP PRB is 20 PRBs.

[0215] Provides a 2-symbol CORESET 0 configuration 813, which includes 6 CCEs and two invalid CCEs 815 (at the lowest frequency). The invalid CCEs 815 are invalid because only two PRBs are available in the initial BWP 711, rather than the 6 PRBs required for two aligned CCEs.

[0216] Thus, the CORSET 0 configuration 817 includes 6 CCEs (or 18 PRBs). The upper edge of the CORE SET 0 configuration 817 is aligned with the 20 PRB initial BWP 811. There is a 2 CCE offset between the lower edge of the CORE SET 0 configuration 817 and the lower edge of the 15 PRB CBW 801 and the 5 CCEs 803.

[0217] Figure 8b Another schematic diagram showing the CORESET 0 configuration within the initial BWP of 24 PRBs, with an offset of 2 CCEs.

[0218] As discussed above, an 'offset (RB)' value of 2 indicates the CCE offset between the lower edge of CORESET 0 and the lower edge of the non-punctured PBCH. In Figure 8b the example, this CCE offset is 2.

[0219] Figure 8b Shows a 15 PRB CBW 851. A sequence of 5 CCEs 853 is aligned with the 15 PRB CBW 851 at the lower and upper edges. The 5 CCEs 853 are a (2-symbol) CORESET 0 subset for SIB1 scheduling 855.

[0220] Provide 'Point A' labeled 857. Provide the initial BWP offset 859 from 'Point A' to the initial BWP PRB 861. The length of the initial BWP PRB is 24 PRBs.

[0221] Provide a 2-symbol CORESET 0 configuration 863 including 8 CCEs. Thus, the CORSET 0 configuration 867 includes 8 CCEs (or 24 PRBs). The lower and upper edges of the CORESET 0 configuration 867 are aligned with the 24 PRB initial BWP 861. There is a 2 CCE offset 865 between the lower edge of the CORESET 0 configuration 867 and the lower edge of the 15 PRB CBW 851 and 5 CCEs 853.

[0222] As discussed above, a method is provided in which when determining the CORESET 0 (CORESET#0) configuration, the UE determines the lowest PRB (in frequency) of the CORESET 0 configuration based on the determined lowest resource block of the non-punctured PBCH. In the following example, it is assumed that the number of RBs of CORESET 0 is 24. In other examples, more or fewer than 24 RBs are used for CORESET 0. Such determination of CORESET 0 by the UE or other suitable device may include one or more of the following steps:

[0223] i) Receive or detect an initial access signal and / or channel from a network node. Such as, for example Figure 4 those shown.

[0224] ii) After detecting the PSS and SSS at certain synchronization grid points, determine that the PBCH is transmitted using a 15 PRB allocation. This may mean that the UE can determine a certain puncturing pattern of the PBCH.

[0225] iii) Determine the lowest PRB (in frequency) of CORESET 0, where the determination includes setting the lowest PRB of CORESET 0 to be the same as the lowest RB of the non-punctured PBCH. Or, the RB on the common grid of the subcarriers of the lowest RB of the non-punctured PBCH.

[0226] iv) Determine the valid PRBs of CORESET 0 based on the PBCH and the initial BWP. Determine the size of CORESET 0 based on the PBCH and the initial BWP.

[0227] v) Determine the CCE allocation of CORESET 0 based on the valid PRBs and the size of CORESET 0.

[0228] Figure 9a and Figure 9bA schematic diagram showing the alignment between the valid PRBs of PBCH and the valid PRBs of CORESET 0. Each block / square in these figures represents a PRB.

[0229] Figure 9a and Figure 9b Shows the 15 PRB common RB grid 901 as a reference. In this example, the channel grid point 903 is set in the middle of 15 PRBs, i.e., at 7.5 PRBs. The channel grid is in the middle of the carrier. The synchronization grid is in the middle of PSS / SSS. The channel and synchronization grids may be offset from each other.

[0230] For the blocks / squares, the checkerboard pattern represents the common RBs. The brick pattern represents PSS. The dotted pattern represents SSS. The vertical line pattern indicates PBCH. The blank blocks represent the punctured PRBs. The alignment between the options (and PRBs) indicates the frequency alignment between the options and the reference.

[0231] The first option 905 has a '2+3' puncturing pattern. The first option 905 has PSS 907 and SSS 909, each including 12 PRBs (each occupying 1 symbol). PBCH 911 is also provided, whose lower and upper edges are aligned with the common RB grid 901. The synchronization grid point 913 of the first option 905 is offset from the channel grid 903 by +90 kHz, equivalent to 6 subcarriers (SCs).

[0232] The second option 915 has a '3+2' puncturing pattern. The second option 915 has PSS 917 and SSS 919, each including 12 PRBs (each occupying 1 symbol). PBCH 921 is also provided, whose lower and upper edges are aligned with the common RB grid 901. The synchronization grid point 923 of the second option 915 is offset from the channel grid 903 by -90 kHz, equivalent to 6 subcarriers (SCs).

[0233] In Figure 9b the third option 925 has a '4+1' puncturing pattern. The third option 925 has PSS 927 and SSS 929, each including 12 PRBs (each occupying 1 symbol). PBCH 931 is also provided, whose lower and upper edges are aligned with the common RB grid 901. The synchronization grid point 933 of the second option 925 is offset from the channel grid 903 by -270 kHz, equivalent to 18 subcarriers (SCs).

[0234] The fourth option 935 has a '1 + 4' puncturing pattern. The fourth option 935 has a PSS 937 and an SSS 939, each including 12 PRBs (each occupying 1 symbol). A PBCH 941 is also provided, whose lower edge and upper edge are aligned with the common RB grid 901. The synchronization grid point 943 of the second option 935 is offset from the channel grid 903 by +270 kHz, corresponding to 18 subcarriers (SCs).

[0235] Figure 10 A schematic diagram showing the CORESET 0 size determination and CCE allocation options.

[0236] A PBCH 1001 is provided. The PBCH includes 15 RBs. The first CORESET 0 configuration 1003 includes 2 symbols and 5 CCEs. Each CCE corresponds to 3 PRBs. Thus, the first CORESET 0 configuration 1003 includes 15 PRBs. The lower edge and upper edge of the first CORESET 0 configuration 1003 are aligned with the lower edge and upper edge of the PBCH 1001.

[0237] The second CORESET 0 configuration 1005 includes 3 symbols and 7 CCEs. Each CCE corresponds to 2 PRBs. Thus, the second CORESET 0 configuration 1005 includes 14 PRBs. The lower edge of the second CORESET 0 configuration 1005 is aligned with the lower edge of the PBCH 1001.

[0238] The third CORESET 0 configuration 1007 includes 3 symbols and 7 CCEs. Each CCE corresponds to 2 PRBs. Thus, the third CORESET 0 configuration 1007 includes 14 PRBs. The upper edge of the second CORESET 0 configuration 1005 is aligned with the upper edge of the PBCH 1001.

[0239] The fourth CORESET 0 configuration 1009 includes 3 symbols and 8 CCEs. Each CCE corresponds to 2 PRBs. Thus, the fourth CORESET 0 configuration 1009 includes 16 PRBs. Since the PBCH 1001 includes 15 PRBs, one resource block is punctured 1011 (i.e., 16 – 15 = 1 RB). The lower edge of the second CORESET 0 configuration 1005 is aligned with the lower edge of the PBCH 1001.

[0240] The advantage of the one or more examples above is that they have less impact on the current specifications / standards. Especially for the 3 MHz scenario. The benefit of this method is that it is not necessary to redefine / change Table 1, as described above (the same as Table 13-1 in 3GPP TS 38.213 specification). In this case, it is sufficient to have a new interpretation for some rows in the table (at least for indices [0,3]). In addition, the one or more examples will only result in small changes in the implementation. For example, changes to the interleaving pattern can be avoided. This leads to the best (and improved) performance. The one or more examples align the candidate / CCE with other CORESETs, enabling UE reuse.

[0241] Figure 11 An example method flow executed by a device is shown. The device may be included within a user equipment. In one example, the device may be a user equipment. In one example, the device may be used for a user equipment.

[0242] At S1101, the method includes detecting a primary synchronization signal and a secondary synchronization signal transmitted from a network node.

[0243] At S1103, the method includes using the detected primary synchronization signal and secondary synchronization signal to determine the number of resource blocks allocated for a physical broadcast channel.

[0244] At S1105, the method includes determining the lowest frequency resource block of the physical broadcast channel.

[0245] At S1107, the method includes determining the lowest frequency resource block of control resource set 0 (CORESET#0) to be the same as the determined lowest resource block of the physical broadcast channel.

[0246] Figure 12 A schematic diagram of non-volatile memory media 1200a (e.g., a computer disk (CD) or a digital versatile disk (DVD)) and 1200b (e.g., a universal serial bus (USB) storage stick) storing instructions and / or parameters 1202 is shown. The instructions and / or parameters, when executed by a processor, allow the processor to execute Figure 11 one or more steps of the method steps.

[0247] Note that although example embodiments are described above, various changes and modifications can be made to the disclosed solutions without departing from the scope of the present invention.

[0248] Examples may thus vary within the scope of the appended claims. In general, some implementations may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software executable by a controller, microprocessor, or other computing device, but the implementations are not limited thereto. Although various implementations may be shown and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that, as non-limiting examples, the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general-purpose hardware or controllers, or other computing devices, or some combination thereof.

[0249] Examples may be implemented by computer software stored in a memory and executable by at least one data processor of the entity involved, or by hardware, or by a combination of software and hardware. In addition, in this regard, it should be noted that any process may represent program steps, or interconnected logic circuits, blocks, and functions, or a combination of program steps and logic circuits, blocks, and functions. The software may be stored on a physical medium such as a memory chip or a memory block implemented within a processor, a magnetic medium such as a hard disk or a floppy disk, and an optical medium such as a DVD and its data variants, a CD.

[0250] The term "non-transitory" as used herein is a limitation of the medium itself (i.e., tangible, rather than a signal), rather than a limitation on the persistence of data storage (e.g., RAM vs. ROM).

[0251] As used herein, "at least one of the following: <list of two or more elements>" and "one of the following: <list of two or more elements>" and similar phrases, where the list of two or more elements is joined by "and" or "or", means at least any one element, or at least any two or more elements, or at least all elements.

[0252] The memory can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology (such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory). The data processor can be of any type suitable for the local technical environment and, as non-limiting examples, may include one or more of the following: general-purpose computers, dedicated computers, microprocessors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), gate-level circuits, and processors based on multi-core processor architectures.

[0253] Alternatively or additionally, circuitry may be used to implement some examples. The circuitry may be configured to perform one or more of the functions and / or method steps described previously. The circuitry may be provided in a base station and / or in a communication device.

[0254] As used in this application, the term "circuitry" may refer to one or more or all of the following:

[0255] (a) an implementation in pure hardware circuitry, such as an implementation in only analog and / or digital circuitry;

[0256] (b) a combination of hardware circuitry and software, such as:

[0257] (i) a combination of analog and / or digital hardware circuitry and software / firmware, and

[0258] (ii) any part of a hardware processor with software (including a digital signal processor), the software and memory, which work together to cause a device, such as a communication device or a base station, to perform the various functions described previously; and

[0259] (c) a hardware circuitry and / or a processor, such as a microprocessor or a part of a microprocessor, which requires software (e.g., firmware) to operate, but the software may be absent when not needed to operate.

[0260] This definition of circuitry applies to all uses of the term in this application (including in any claims). As another example, as used in this application, the term circuitry also covers an implementation of only hardware circuitry or a processor (or processors) or a part of hardware circuitry or a processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example, an integrated device.

[0261] The foregoing description has provided a complete and rich description of some embodiments by way of example and not limitation. However, various changes and modifications may become apparent to those skilled in the art in light of the foregoing description when read in conjunction with the accompanying drawings and the appended claims. However, all such and similar modifications of the teachings will still fall within the scope as defined by the appended claims.

Claims

1. An apparatus, the apparatus comprises: means for detecting a primary synchronization signal and a secondary synchronization signal received from a network node; means for using the detected primary synchronization signal and secondary synchronization signal to determine the number of resource blocks allocated for a physical broadcast channel; means for determining the lowest-frequency resource block of the physical broadcast channel; and means for determining the lowest-frequency resource block of control resource set 0 (CORESET#0) of a physical downlink control channel as the same as the determined lowest resource block of the physical broadcast channel.

2. The apparatus according to claim 1, further comprises: means for determining the valid resource blocks of the CORESET#0 of the physical downlink control channel by aligning with the valid resource blocks of the physical broadcast channel to determine the size of the CORESET#0 of the physical downlink control channel; and means for determining the control channel element allocation of the CORESET#0 of the physical downlink control channel based on i) the lowest resource block and ii) the valid resource blocks of the CORESET#0.

3. The apparatus according to claim 1 or claim 2, further comprises: means for communicating with the network node using the CORESET#0 of the physical downlink control channel.

4. The apparatus according to claim 2 or claim 3, wherein the means for determining the valid resource blocks of the CORESET#0 comprises: means for determining that the valid resource blocks of the CORESET#0 of the physical downlink control channel are resource blocks having complete control channel elements.

5. The apparatus according to claim 2 or claim 3, wherein the means for determining the valid resource blocks of the CORESET#0 of the physical downlink control channel comprises: means for determining that the valid resource blocks of the CORESET#0 of the physical downlink control channel are resource blocks covering fifteen resource blocks having complete control channel elements and partial control channel elements.

6. The apparatus according to any one of claims 2 to 3, wherein the means for determining the size of the CORESET#0 of the physical downlink control channel comprises one of the following: means for determining the maximum number of complete control channel elements suitable for fifteen resource blocks; means for determining the maximum number of the complete control channel elements and the partial control channel elements suitable for the fifteen resource blocks; means for determining the number of complete control channel elements using a predetermined number of control channel elements; means for determining the number of resource blocks using a predefined multiple of six resource blocks higher than the total of the fifteen resource blocks.

7. The apparatus according to any one of claims 2 to 6, wherein the means for determining the control channel element allocation of the CORESET#0 of the physical downlink control channel comprises: A component for determining the control channel element allocation of the CORESET #0 of the physical downlink control channel using non-interleaved control channel element mapping.

8. The apparatus according to any one of claims 2 to 7, wherein the apparatus further comprises: A component for determining, in response to determining the valid resource blocks of the CORESET #0 of the physical downlink control channel, an index of information providing the control channel element allocation within the valid resource blocks of the CORESET #0 of the physical downlink control channel using the physical broadcast channel.

9. The apparatus according to any one of claims 2 to 8, wherein the apparatus further comprises: A component for receiving a configuration associated with the physical downlink control channel from the network node; and A component for determining, in response to the reception, the CORESET #0 of all search spaces of the physical downlink control channel using the CORESET #0 in the initial bandwidth part.

10. The apparatus according to any one of claims 2 to 8, wherein the apparatus further comprises: A component for receiving a configuration associated with the physical downlink control channel from the network node; and A component for determining whether one of the lower frequency edge or the higher frequency edge of the CORESET #0 of the physical downlink control channel will be aligned with the resource blocks of the physical broadcast channel using one or more parameters included in the configuration associated with the physical downlink control channel.

11. The apparatus according to any one of claims 1 to 10, wherein the apparatus further comprises: A component for determining the channel bandwidth in which the network node is operating using the detected primary synchronization signal and secondary synchronization signal.

12. The apparatus according to claim 11, wherein the component for determining comprises a component for determining synchronization grid points using the detected primary synchronization signal and secondary synchronization signal to determine the channel bandwidth in which the network node is operating.

13. The apparatus according to any one of claims 1 to 12, wherein one of the following: the apparatus is for the user equipment, the apparatus is located within the user equipment, or the apparatus is the user equipment.

14. A method, the method comprises: Detecting a primary synchronization signal and a secondary synchronization signal received from a network node; Using the detected primary synchronization signal and secondary synchronization signal to determine the number of resource blocks allocated for the physical broadcast channel; Determining the lowest frequency resource block of the physical broadcast channel; and Determining the lowest frequency resource block of the control resource set 0 CORESET #0 of the physical downlink control channel to be the same as the determined lowest resource block of the physical broadcast channel.

15. The method according to claim 14, further comprises: Determine the valid resource blocks of the CORESET#0 of the physical downlink control channel by aligning with the valid resource blocks of the physical broadcast channel to determine the size of the CORESET#0 of the physical downlink control channel; and Determine the control channel element allocation of the CORESET#0 of the physical downlink control channel based on i) the lowest resource block and ii) the valid resource blocks of the CORESET#0.

16. The method according to claim 14 or claim 15, further comprising: Communicate with the network node using the determined CORESET#0 of the physical downlink control channel.

17. The method according to claim 15 or claim 16, wherein determining the valid resource blocks of the CORESET#0 comprises: Determine that the valid resource blocks of the CORESET#0 of the physical downlink control channel are resource blocks with complete control channel elements.

18. The method according to claim 15 or claim 16, wherein determining the valid resource blocks of the CORESET#0 comprises: Determine that the valid resource blocks of the CORESET#0 of the physical downlink control channel are resource blocks covering fifteen resource blocks with complete control channel elements and partial control channel elements.

19. The method according to claims 15 to 16, wherein determining the size of the CORESET#0 of the physical downlink control channel comprises one of the following: Determine the maximum number of complete control channel elements suitable for fifteen resource blocks; Determine the maximum number of the complete control channel elements and the partial control channel elements suitable for the fifteen resource blocks; Determine the number of complete control channel elements using a predetermined number of control channel elements; Determine the number of resource blocks using a predefined multiple higher than six resource blocks of the total fifteen resource blocks.

20. The method according to any one of claims 15 to 19, wherein determining the control channel element allocation of the CORESET#0 of the physical downlink control channel comprises: Determine the control channel element allocation of the CORESET#0 of the physical downlink control channel using non-interleaved control channel element mapping.

21. The method according to any one of claims 15 to 20, further comprising: In response to determining the valid resource blocks of the CORESET#0, use the physical broadcast channel to determine an index providing information about the control channel element allocation within the valid resource blocks of the CORESET#0 of the physical downlink control channel.

22. The method according to any one of claims 15 to 21, further comprising: Receive a configuration associated with the physical downlink control channel from the network node; and In response to the reception, determine CORESET #0 of all search spaces of the physical downlink control channel using the CORESET #0 in the initial bandwidth part.

23. The method according to any one of claims 15 to 21, further comprising: receiving, from the network node, a configuration associated with the physical downlink control channel; and using one or more parameters included in the configuration associated with the physical downlink control channel to determine whether one of the lower frequency edge or the higher frequency edge of the CORESET #0 of the physical downlink control channel will be aligned with a resource block of the physical broadcast channel.

24. The method according to any one of claims 14 to 23, further comprising: using the detected primary synchronization signal and secondary synchronization signal to determine the channel bandwidth in which the network node is operating.

25. The method according to claim 24, wherein the determination comprises using the detected primary synchronization signal and secondary synchronization signal to determine a synchronization grid point to determine the channel bandwidth in which the network node is operating.

26. The method according to any one of claims 14 to 25, wherein one of the following: the method is performed by user equipment.

27. A device, the device comprising: at least one processor; and at least one memory storing instructions which, when executed by the at least one processor, cause the device to at least: detect a primary synchronization signal and a secondary synchronization signal received from a network node; use the detected primary synchronization signal and secondary synchronization signal to determine the number of resource blocks allocated for the physical broadcast channel; determine the lowest frequency resource block of the physical broadcast channel; and determine the lowest frequency resource block of the control resource set 0 CORESET #0 of the physical downlink control channel to be the same as the determined lowest resource block of the physical broadcast channel.

28. A computer program comprising instructions which, when executed by a device, cause the device to at least perform the following operations: detect a primary synchronization signal and a secondary synchronization signal received from a network node; use the detected primary synchronization signal and secondary synchronization signal to determine the number of resource blocks allocated for the physical broadcast channel; determine the lowest frequency resource block of the physical broadcast channel; and determine the lowest frequency resource block of the control resource set 0 CORESET #0 to be the same as the determined lowest resource block of the physical broadcast channel.

Images