Method, apparatus and computer program

Abstract

An apparatus is provided that includes means for detecting a primary synchronization signal and a secondary synchronization signal transmitted from a network node, and means for determining a number of resource blocks to be allocated to a physical broadcast channel using the detected primary synchronization signal and secondary synchronization signal, and means for determining a minimum resource block, in frequency, of the physical broadcast channel, and means for determining a minimum resource block, in frequency, of a control resource set 0 (CORESET#0), that is the same as the determined minimum resource block of the physical broadcast channel.

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to and the benefit of GB Application No. 2214243.4, filed September 29, 2022, which is incorporated herein by reference in its entirety.

[0002] The present application relates to a method, apparatus, and computer program for a wireless communication system. [Background technology]

[0003] A communication system may be a facility that enables communication sessions between two or more entities, such as user terminals, base stations / access points, and / or other nodes, by providing carriers between the various entities involved in the communication paths. A communication system may be provided, for example, by a communication network and one or more compatible communication devices. A communication session may include, for example, communication of data to convey communications such as voice, electronic mail (email), text messages, multimedia, and / or content data. Non-limiting examples of 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

[0004] According to an aspect, an apparatus is provided, the apparatus comprising: means for detecting a primary synchronization signal and a secondary synchronization signal transmitted from a network node; means for determining a number of resource blocks allocated to a physical broadcast channel using the detected primary and secondary synchronization signals; and means for determining a frequency of the physical broadcast channel. in , a means for determining a minimum resource block, and a frequency of a control resource set 0 (CORESET#0) that is the same as the determined minimum resource block of the physical broadcast channel. in , and means for determining a minimum resource block.

[0005] In the example, the physical broadcast channel is transmitted on in The means for determining the minimum resource block is a frequency band on which the physical broadcast channel is transmitted from the network node after the resource block decimation. in , including means for determining a minimum resource block.

[0006] In an example, the apparatus includes means for determining valid resource blocks for CORESET#0 by aligning with valid resource blocks of a physical broadcast channel to determine the size of CORESET#0, and means for determining an allocation of control channel elements for CORESET#0 based on i) the smallest resource block and ii) the valid resource block of CORESET#0.

[0007] In an example, the apparatus includes means for communicating with a network node using the determined CORESET#0.

[0008] In an example, the apparatus includes means for demodulating and decoding an associated physical broadcast channel in response to detecting the primary and secondary synchronization signals.

[0009] In an example, the physical broadcast channel is associated with the detected primary and secondary synchronization signals.

[0010] In an example, the means for determining resource blocks valid for CORESET#0 includes means for determining that resource blocks valid for CORESET#0 are resource blocks with complete control channel elements.

[0011] In an example, the means for determining resource blocks valid for CORESET#0 includes means for determining that the resource blocks valid for CORESET#0 are resource blocks covering 15 resource blocks with full and partial control channel elements.

[0012] In an example, the means for determining the size of CORESET#0 includes one of means for determining the maximum number of full control channel elements that fit into 15 resource blocks, means for determining the maximum number of full and partial control channel elements that fit into 15 resource blocks, means for determining the number of full control channel elements using a predetermined number of control channel elements, and means for determining the number of resource blocks using a predetermined multiple of 6 resource blocks that exceeds the total of 15 resource blocks.

[0013] In an example, the means for determining an allocation of control channel elements for CORESET#0 includes means for determining an allocation of control channel elements for CORESET#0 using a mapping of non-interleaved control channel elements.

[0014] In an example, the apparatus includes means for, in response to determining valid resource blocks for CORESET#0, determining, using a physical broadcast channel, an index providing information regarding allocation of control channel elements within the valid resource blocks of CORESET#0.

[0015] In an example, the apparatus includes means for receiving, from a network node, a configuration associated with a physical downlink control channel, and means for determining, in response to receiving, a CORESET#0 for all search spaces using the CORESET#0 within the initial bandwidth portion.

[0016] In an example, the apparatus 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 in the configuration, determining a further CORESET#0 to be applied to all other search spaces using CORESET#0 except for a Type0 PDCCH search space, wherein the further CORESET#0 used by the other search spaces is more frequency-sensitive than the CORESET#0 used by the Type0-PDCCH. In Broadly, the further CORESET#0 includes resource blocks used by CORESET#0 applied to the Type0 PDCCH search space.

[0017] In an example, the device includes means for receiving from a network node a configuration associated with a physical downlink control channel, and using one or more parameters included in the configuration associated with the physical downlink control channel, in Lower edge, or frequency in and means for determining whether one of the upper edges is aligned with a resource block of a physical broadcast channel.

[0018] In an example, the apparatus includes means for determining a channel bandwidth in which the network node is operating using the detected primary and secondary synchronization signals.

[0019] In an example, the means for determining includes means for determining a synchronization raster point using the detected primary and secondary synchronization signals to determine a channel bandwidth over which the network node is operating.

[0020] In the example, the channel bandwidth is determined to be 3 megahertz.

[0021] In the example, there are 15 resource blocks available for the physical broadcast channel.

[0022] An example is one of the device being for user equipment, the device being located within user equipment, or the device being user equipment.

[0023] According to an aspect, an apparatus is provided that includes at least one processor and at least one memory storing instructions that, when executed by the one or more processors, include detecting a primary synchronization signal and a secondary synchronization signal transmitted from a network node; determining a number of resource blocks allocated to a physical broadcast channel using the detected primary and secondary synchronization signals; and allocating a frequency of the physical broadcast channel to the network node. in , determining the minimum resource block, and the frequency of the control resource set 0 (CORESET#0) that is the same as the determined minimum resource block of the physical broadcast channel. in , and determining the minimum resource block.

[0024] In the example, the physical broadcast channel is transmitted on in ,Determining the minimum resource block is, after the resource block decimation, the network node transmits the physical broadcast channel, in , including determining the smallest resource block.

[0025] In the example, the device determines the available resource blocks for CORESET#0 by aligning with the available resource blocks of the physical broadcast channel to determine the size of CORESET#0, and determines the allocation of control channel elements for CORESET#0 based on i) the smallest resource blocks and ii) the available resource blocks of CORESET#0.

[0026] In the example, the device will use the determined CORESET#0 to communicate with the network node.

[0027] In an example, in response to detecting the primary and secondary synchronization signals, the device is adapted to perform demodulation and decoding of the associated physical broadcast channel.

[0028] In an example, the physical broadcast channel is associated with the detected primary and secondary synchronization signals.

[0029] In the example, determining the resource blocks valid for CORESET#0 includes determining that the resource blocks valid for CORESET#0 are resource blocks with complete control channel elements.

[0030] In the example, determining the resource blocks valid for CORESET#0 includes determining that the resource blocks valid for CORESET#0 are resource blocks covering 15 resource blocks with full and partial control channel elements.

[0031] In an example, determining the size of CORESET#0 includes one of determining the maximum number of full control channel elements that fit into 15 resource blocks, determining the maximum number of full and partial control channel elements that fit into 15 resource blocks, determining the number of full control channel elements using a predetermined number of control channel elements, or determining the number of resource blocks using a predetermined multiple of 6 resource blocks that exceeds the total of 15 resource blocks.

[0032] In an example, determining the allocation of control channel elements for CORESET#0 includes determining the allocation of control channel elements for CORESET#0 using a mapping of non-interleaved control channel elements.

[0033] In an example, in response to determining the resource blocks available for CORESET#0, the device is configured to use a physical broadcast channel to determine an index that provides information regarding the allocation of control channel elements within the resource blocks available for CORESET#0.

[0034] In the example, the device is configured to receive, from a network node, a configuration associated with a physical downlink control channel, and, in response to receiving, determine a CORESET#0 for all search spaces using a CORESET#0 within an initial bandwidth portion.

[0035] In the example, the device is adapted to receive, from a network node, a configuration associated with a physical downlink control channel; and, after receiving the configuration, use parameters included in the configuration to determine a further CORESET#0 to be applied to all other search spaces using CORESET#0 except for a Type0 PDCCH search space, wherein the further CORESET#0 used by the other search spaces is more frequency-sensitive than the CORESET#0 used by the Type0-PDCCH. In Broadly, the further CORESET#0 includes resource blocks used by CORESET#0 applied to the Type0 PDCCH search space.

[0036] In an example, the device may receive a configuration associated with a physical downlink control channel from a network node, and use one or more parameters included in the configuration associated with the physical downlink control channel to select a frequency of CORESET#0. in Lower edge, or frequency in and determining whether one of the upper edges is aligned with a resource block of the physical broadcast channel.

[0037] In an example, the apparatus is adapted to perform determining a channel bandwidth in which the network node is operating using the detected primary and secondary synchronization signals.

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

[0039] In the example, the channel bandwidth is determined to be 3 megahertz.

[0040] In the example, there are 15 resource blocks available for the physical broadcast channel.

[0041] An example is one of the device being for user equipment, the device being located within user equipment, or the device being user equipment.

[0042] According to an aspect, a method is provided, the method comprising: detecting a primary synchronization signal and a secondary synchronization signal transmitted from a network node; determining a number of resource blocks allocated to a physical broadcast channel using the detected primary and secondary synchronization signals; and determining a frequency of the physical broadcast channel. in , determining the minimum resource block, and the frequency of the control resource set 0 (CORESET#0) that is the same as the determined minimum resource block of the physical broadcast channel. in , determining the smallest resource block.

[0043] In the example, the physical broadcast channel is transmitted on in ,Determining the minimum resource block is, after the resource block decimation, the network node transmits the physical broadcast channel, in , including determining the smallest resource block.

[0044] In an example, the method includes determining valid resource blocks for CORESET#0 by aligning with valid resource blocks of a physical broadcast channel to determine the size of CORESET#0, and determining an allocation of control channel elements for CORESET#0 based on i) the smallest resource blocks and ii) the valid resource blocks of CORESET#0.

[0045] In an example, the method includes communicating with a network node using the determined CORESET#0.

[0046] In an example, the method includes, in response to detecting the primary and secondary synchronization signals, demodulating and decoding associated physical broadcast channels.

[0047] In an example, the physical broadcast channel is associated with the detected primary and secondary synchronization signals.

[0048] In the example, determining the resource blocks valid for CORESET#0 includes determining that the resource blocks valid for CORESET#0 are resource blocks with complete control channel elements.

[0049] In the example, determining the resource blocks valid for CORESET#0 includes determining that the resource blocks valid for CORESET#0 are resource blocks covering 15 resource blocks with full and partial control channel elements.

[0050] In an example, determining the size of CORESET#0 includes one of determining the maximum number of full control channel elements that fit into 15 resource blocks, determining the maximum number of full and partial control channel elements that fit into 15 resource blocks, determining the number of full control channel elements using a predetermined number of control channel elements, or determining the number of resource blocks using a predetermined multiple of 6 resource blocks that exceeds the total of 15 resource blocks.

[0051] In an example, determining the allocation of control channel elements for CORESET#0 includes determining the allocation of control channel elements for CORESET#0 using a mapping of non-interleaved control channel elements.

[0052] In an example, the method includes, in response to determining valid resource blocks for CORESET#0, determining, using a physical broadcast channel, an index that provides information regarding allocation of control channel elements within the valid resource blocks of CORESET#0.

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

[0054] In an example, the method includes receiving, from a network node, a configuration associated with a physical downlink control channel; and, after receiving the configuration, using parameters included in the configuration to determine a further CORESET#0 to be applied to all other search spaces using CORESET#0 except for a Type0 PDCCH search space, wherein the further CORESET#0 used by the other search spaces is more frequency-sensitive than the CORESET#0 used by the Type0-PDCCH. In Broadly, the further CORESET#0 includes resource blocks used by CORESET#0 applied to the Type0 PDCCH search space.

[0055] In an 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 in the configuration associated with the physical downlink control channel to select a frequency in Lower edge, or frequency in determining whether one of the upper edges is aligned with a resource block of a physical broadcast channel.

[0056] In an example, the method includes determining a channel bandwidth in which the network node is operating using the detected primary and secondary synchronization signals.

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

[0058] In the example, the channel bandwidth is determined to be 3 megahertz.

[0059] In the example, there are 15 resource blocks available for the physical broadcast channel.

[0060] In an example, the method is performed by a user equipment.

[0061] According to an aspect, a computer program is provided that includes instructions that, when executed by an apparatus, cause the computer program to at least: detect a primary synchronization signal and a secondary synchronization signal transmitted from a network node; determine a number of resource blocks allocated to a physical broadcast channel using the detected primary and secondary synchronization signals; and determine a frequency of the physical broadcast channel. in, determining the minimum resource block, and the frequency of the control resource set 0 (CORESET#0) that is the same as the determined minimum resource block of the physical broadcast channel. in , and determining the minimum resource block.

[0062] According to an aspect, a computer program is provided that includes instructions, the instructions further comprising at least the following: detecting a primary synchronization signal and a secondary synchronization signal transmitted from a network node; determining a number of resource blocks allocated to a physical broadcast channel using the detected primary and secondary synchronization signals; and determining a frequency of the physical broadcast channel. in , determining the minimum resource block, and the frequency of the control resource set 0 (CORESET#0) that is the same as the determined minimum resource block of the physical broadcast channel. in , determining the minimum resource block.

[0063] According to an aspect, a non-transitory computer-readable medium is provided that includes program instructions that, when executed by an apparatus, perform at least the following: detect a primary synchronization signal and a secondary synchronization signal transmitted from a network node; determine a number of resource blocks allocated to a physical broadcast channel using the detected primary and secondary synchronization signals; and determine a frequency of the physical broadcast channel. in , determining the minimum resource block, and the frequency of the control resource set 0 (CORESET#0) that is the same as the determined minimum resource block of the physical broadcast channel. in , and determining the minimum resource block.

[0064] The computer product stored on the medium enables the apparatus to perform the methods described herein.

[0065] A non-transitory computer-readable medium containing program instructions that, when executed by an apparatus, cause the apparatus to perform the methods described herein.

[0066] The electronic device may include the apparatus described herein.

[0067] Various aspects have been described above. It should be understood that any two or more of the various aspects described above may be combined to provide further aspects.

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

[0069] According to some aspects, the subject matter of the independent claims is provided. Some further aspects are defined in the dependent claims. Non-claimed embodiments should be construed as examples useful for understanding the present disclosure.

[0070] List of abbreviations: AF: Application Function

[0071] AL: Aggregation Level

[0072] AMF: Access Management Function

[0073] AN: Access Network

[0074] BD: Blind Detection

[0075] BS:Base Station

[0076] BW: Bandwidth

[0077] CBW: Channel Bandwidth

[0078] CCE: Control Channel Element

[0079] CORESET: Control Resource Set

[0080] CN: Core Network

[0081] DL: Downlink

[0082] DMRS: Demodulation Reference Signal

[0083] eNB: eNodeB

[0084] FR1: Frequency Range 1

[0085] FRMCS: Future Railway Mobile Communication System (next-generation railway mobile communication system)

[0086] gNB: gNodeB

[0087] GSCN: Global Synchronisation Channel Number

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

[0089] IIoT: Industrial Internet of Things

[0090] LTE: Long Term Evolution

[0091] MS:Mobile Station

[0092] MIB: Master Information Block

[0093] NEF: Network Exposure Function

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

[0095] NF: Network Function

[0096] NR:New Radio

[0097] NRF: Network Repository Function

[0098] NW: Network

[0099] PBCH: Physical Broadcast Channel

[0100] PDCCH: Physical Downlink Control Channel

[0101] PCF: Policy Control Function

[0102] PLMN: Public Land Mobile Network

[0103] PRB: Physical Resource Block

[0104] PSS:Primary Synchronization Signal

[0105] RAN: Radio Access Network

[0106] RE: Resource Element

[0107] REG: Resource Element Group

[0108] RF: Radio Frequency

[0109] SCS: Subcarrier Spacing

[0110] SI: System Information

[0111] SIB: System Information Block

[0112] SMF: Session Management Function

[0113] SS:Synchronization Signal

[0114] SSB: Synchronization Signal Block

[0115] SSREF: Frequency position of the Synchronisation Signal

[0116] SSS:Secondary Synchronization Signal

[0117] UE: User Equipment

[0118] UDR: Unified Data Repository

[0119] UDM: Unified Data Management

[0120] UL: Uplink

[0121] UPF: User Plane Function

[0122] 3GPP: 3rd Generation Partnership Project

[0123] 5G: 5th Generation

[0124] 5GC: 5G Core network

[0125] 5G-AN: 5G Radio Access Network

[0126] 5GS: 5G System

[0127] Embodiments will now be described, by way of example only, with reference to the accompanying drawings, in which: [Brief explanation of the drawings]

[0128] [Figure 1] A schematic diagram of a 5G system is shown. [Figure 2] A schematic diagram of a control device is shown. [Figure 3] A schematic diagram of the terminal is shown. [Figure 4]1 shows a schematic diagram of an existing new wireless initial access signal and channel with 15 kHz subcarrier spacing. [Figure 5] 1 shows a schematic diagram of different thinning patterns of synchronization signal blocks; [Figure 6] 1 shows an example diagram of a CORESET resource allocation including resource block offsets. [Figure 7] 1 shows a schematic diagram of a CORESET0 configuration within an initial bandwidth portion of 22 physical resource blocks. [Figure 8a] 10 shows another schematic diagram of a CORESET0 configuration within an initial bandwidth portion of 20 physical resource blocks with an offset of 2 control channel elements. [Figure 8b] 10 shows another schematic diagram of a CORESET0 configuration within an initial bandwidth portion of 24 physical resource blocks with an offset of 2 control channel elements. [Figure 9a] 10 shows a schematic diagram of the alignment between the available physical resource blocks of the physical broadcast channel and the available physical resource blocks of CORESET0. [Figure 9b] 10 shows a schematic diagram of the alignment between the available physical resource blocks of the physical broadcast channel and the available physical resource blocks of CORESET0. [Figure 10] 10 shows a schematic diagram of CORESET0 sizing and CCE allocation options. [Figure 11] 10 illustrates a flow diagram of another exemplary method performed by user equipment. [Figure 12] 12 illustrates a schematic diagram of a non-volatile memory medium storing instructions that, when executed by a processor, enable the processor to perform one or more of the steps of the method of FIG. 11. DETAILED DESCRIPTION OF THE INVENTION

[0129] Before describing some examples of the present disclosure in detail, certain general principles of wireless communication systems and mobile communication devices will be briefly described with reference to FIGS. 1 to 3 to aid in understanding the technology underlying the described examples.

[0130] In a wireless communication system 100 such as that shown in Figure 1, wireless access is provided to mobile communication devices / terminals or user equipment and / or user equipment (UE) and / or machine-type communication devices 102 via at least one base station (not shown) or similar wireless transmitting and / or receiving node or point. The communication devices are provided with appropriate signal transmission and reception equipment to enable communications, e.g., to enable access to a communication network or direct communication with other devices. The communication devices may access a carrier provided by a station or access point to transmit and / or receive communications over the carrier.

[0131] The following specific examples will be described with reference to mobile communication devices capable of communicating via a wireless cellular system, and mobile communication systems that provide services to such mobile communication devices. Before describing the examples of the present disclosure in detail, certain general principles of wireless communication systems, access systems for wireless communication systems, and mobile communication devices will be briefly described with reference to Figures 1, 2, and 3 to facilitate understanding of the technology underlying the described examples.

[0132] 1 shows a schematic diagram of a 5G system (5GS) 100. 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 (NFs), one or more application functions (AFs) 108, and one or more data networks (DNs) 110.

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

[0134] The 5GC 104 may include an Access 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 be applicable to 3GPP 5G standards, including 5G-Advanced. However, some examples may also be applicable to 4G, 3G, and other 3GPP standards.

[0135] In a communication system such as that shown in Figure 1, wireless access is provided to mobile communication devices / terminals or user equipment and / or user equipment (UE) and / or machine-type communication devices via at least one base station or similar wireless transmitting and / or receiving node or point. The terminals are provided with appropriate signal transmission and reception equipment to enable communications, e.g., to enable access to a communication network or direct communication with other devices. The communication devices may access a carrier provided by the base station or access point to transmit and / or receive communications over the carrier.

[0136] FIG. 2 illustrates an example of a controller 200 for controlling functions of a 5G-RAN or 5GC, as shown in FIG. 1. The controller 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, enable execution of one or more steps to perform one or more of the present aspects. The software code 215 may be stored in the ROM 211b. The controller 200 may be interconnected with another controller 200 that controls another function of the 5G-RAN or 5GC. In some examples, each function of the 5G-RAN or 5GC includes a controller 200. In alternative examples, two or more functions of the 5G-RAN or 5GC may share a controller.

[0137] FIG. 3 illustrates an example of a terminal 300, such as the terminal shown in FIG. 1. The terminal 300 may be provided by any device capable of transmitting and receiving wireless signals. Non-limiting examples include user equipment, a mobile station (MS), or a mobile device such as a mobile phone or what is known as a "smartphone," a computer with a wireless interface card or other wireless interface equipment (e.g., a USB dongle), a personal digital assistant (PDA) or tablet with wireless communication capabilities, a machine-type communication (MTC) device, a cellular internet of things (CIoT) device, or any combination thereof. The terminal 300 may provide communication of data, for example, to convey communications. The communications may be one or more of voice, electronic mail (email), text messages, multimedia, data, machine data, etc.

[0138] The terminal 300 may receive signals via an apparatus suitable for reception and may transmit signals via an apparatus suitable for transmission of wireless signals via an air or wireless interface 307. In Figure 3, the transceiver apparatus is indicated schematically by block 306. The transceiver apparatus 306 may be provided, for example, by a radio part and an associated antenna arrangement. The antenna arrangement may be located internal or external to the mobile device.

[0139] The terminal 300 may be equipped with at least one processor 301, at least one memory ROM 302a, at least one RAM 302b, and other possible components 303 used for software and hardware-assisted execution of the tasks it is designed to perform, including controlling access to and communication with access systems 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 may be configured to execute appropriate software code 308. The software code 308 may, for example, enable one or more of the present aspects to be performed. The software code 308 may be stored in the ROM 302a.

[0140] The processor, storage, and other associated controls may be provided on a suitable circuit board and / or within a chipset. This feature is indicated by reference numeral 304. The device may optionally have a user interface such as a keypad 305, a touch-sensitive screen or pad, or a combination thereof. Optionally, depending on the type of device, it may include one or more of a display, a speaker, and a microphone.

[0141] One or more of the following examples are applications of or relate to Narrowband New Radio Operation (NB NR), including NR support in dedicated spectrum below 5 MHz, an emerging scenario driven, for example, by rail communications (global), smart grid operators in the USA, and public safety needs in Europe.

[0142] The next-generation mobile communications system for railways in Europe (FRMCS) has the following considerations: It has been agreed to use NR in the 2 × 5.6 MHz FDD (874.4–880 MHz / 919.4–925 MHz) frequency band, and a soft migration from Global System for Mobile Communications - Railways (GSM-R) is expected to last approximately 10 years (approximately 2025–2035), which will require parallel operation of GSM-R and NR in that band. In some scenarios, it is assumed that NR may be allocated 3 MHz channels. Possible deployment scenarios for NR downlink (DL) / uplink (UL) and GSM-R DL / UL include adjacent channel deployment, overlay deployment with compact GSM-R channels, overlay deployment with GSM-R channels distributed across a 4 MHz core band, and overlay deployment with GSM-R channels distributed across the entire band of Extended GSM for Railways (ER-GSM). Adjacent channel deployment of NR and GSM-R may have the advantage that the NR scheduler is easy to implement and there is only one boundary between NR and GSM-R, making coexistence simple and predictable.

[0143] Narrowband NR is also being considered for "smart grid" applications, including 2 x 3 MHz frequency division duplexing (FDD) within 900 MHz in the USA, and NB NR is also being considered for public safety applications, including 2 x 3 MHz FDD within Band 28 for public protection and disaster relief (PPDR) in Europe.

[0144] NR Rel-15 to Rel-17 currently do not support channel bandwidths (CBW) less than 5 MHz. It is proposed to adapt NR to spectrum allocations of 3-5 MHz with minimal changes, building on the existing NR ecosystem.

[0145] Emerging scenarios have been identified where it may be beneficial to enable 5G NR operation within narrower bandwidths than the 5 MHz channels for which 5G NR was originally designed, such as down to 3 MHz. For example, NR deployment within the 900 MHz Next Generation Mobile Communications System (FRMCS) band would need to operate in parallel with any legacy GSM-R carrier within a 5.6 MHz bandwidth, freeing up approximately 3.6 MHz of bandwidth for NR. Similarly, there are cases where 3 MHz channels are available for NR.

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

[0147] FIG. 4 shows a schematic diagram of existing NR initial access signals and channels with 15 kHz subcarrier spacing.

[0148] A block is provided having a width (frequency domain) of 240 subcarriers (SCs) 401, which is equivalent to 20 physical resource blocks (PRBs). Each PRB contains 12 SCs. This block has a height (time domain) of 4 orthogonal frequency division multiplexing (OFDM) symbols 403.

[0149] The total of 240 SCs 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 SCs (i.e., 4 PRBs). The second bandwidth 407 is 2.16 MHz and 144 SCs (i.e., 12 PRBs). The third bandwidth 409 is 0.72 MHz and 48 SCs (i.e., 4 PRBs). Thus, the total bandwidth is 3.6 MHz.

[0150] One of the four OFDM symbols contains a primary synchronization signal (PSS) 411, which is 127 SCs 413. The other of the four OFDM symbols contains a secondary synchronization signal (SSS) 415, which is also 127 SCs 413.

[0151] The PBCH 417 is provided in three of the OFDM symbols: in some OFDM symbols, the PBCH is provided across all SCs in the block, and in other OFDM symbols, the PBCH is provided across a subset of the total SCs.

[0152] A UE may receive the signals and channels shown in Figure 4. After detecting the PSS and SSS, the UE may know the physical cell identity (ID) (of the cell that transmitted the signal) as well as the slot timing within 5 milliseconds (ms) half-frame and symbol timing. The UE may then determine the resource elements (REs) for the PBCH demodulation reference signal (DMRS) and data to receive the PBCH payload. The PBCH carries a master information block (MIB) that signals system information regarding frequency location (synchronization signal block frequency domain allocation with respect to the common resource block (CRB) grid) and timing (half-frame timing, and frame timing). The information may be included either in the upper layer payload (i.e., MIB) or in the DMRS, as part of the physical layer bits in the transport block payload.

[0153] The 3 MHz allocation for an NR system corresponds to a maximum 15 PRB channel bandwidth. This assumes 90% spectrum utilization. For synchronization signal blocks (SSBs), this results in a decimation of 5 PRBs. Decimation of transmitted signals is used to narrow the transmission bandwidth with minimal change. In decimation operation, the base station blanks any signals mapped to specific, predetermined PRBs that fall outside the desired transmission bandwidth. In this way, the base station does not transmit those signals. When a UE receives a transmission in which PRBs have been decimated, the UE may null the decimated PRBs at the receiver. The UE may null the decimated PRBs, for example, by setting the log-likelihood ratio (LLR) to zero in the channel decoder.

[0154] In another example, if the UE is unaware of the thinned PRB, the UE may receive a transmission on all PRBs used for transmission, including the thinned PRB.

[0155] An alternative to decimation is rate matching, whereby the input bits are matched to the available resources. Thus, the rate-matched sequence of bits depends on the resource size. Rate matching requires the receiver to know the resource size in order to decode the packet correctly.

[0156] In some examples, up to 4 PRB thinning can be performed per SSB side, since the PSS / SSS remains unaffected. In other words, some thinning patterns applicable to 5 PRB thinning include 1+4, 2+3, 3+2, and 4+1, as shown in FIG.

[0157] As noted above, Figure 4 illustrates signals and channels with a subcarrier spacing of 15 kHz. Compared to other SCSs supported by NR, a subcarrier spacing (SCS) of 15 kHz provides a minimum bandwidth (in MHz) for signals defined by a predetermined number of RBs (e.g., PBCH, etc.). As such, a 15 kHz SCS is an appropriate starting point when defining support for NR < 5 MHz. It should be understood that the following examples may also apply to subcarrier spacings above or below 15 kHz.

[0158] FIG. 5 shows a schematic diagram of different thinning patterns of the synchronization signal block.

[0159] Four different thinning patterns 501, 503, 505, and 507 are shown. Each of the thinning patterns 501, 503, 505, and 507 is for an SSB having 20 PRBs. Each block in FIG. 5 represents a PRB. Two thinning lines 509 are shown passing through the PRBs. The thinning lines 509 intersect the PRBs of the four different thinning patterns 501, 503, 505, and 507. Blocks without a pattern (i.e., solid) indicate that they are transmitted. Blocks with a pattern (i.e., diagonal lines) indicate that they are thinned.

[0160] The y-axis corresponds to frequency, with arrows on the y-axis indicating increasing frequency.

[0161] In the first thinning pattern 501, a "1+4" pattern exists. The first PRB (ie, PRB0) and the last four PRBs (ie, PRB16 to PRB19) are thinned out. The remaining PRBs of the SSB are transmitted.

[0162] In the second thinning pattern 503, a "2+3" pattern exists. The first and second PRBs (i.e., PRB0 and PRB1) and the last three PRBs (i.e., PRB17 to PRB19) are thinned out. The remaining PRBs of the SSB are transmitted.

[0163] In the third decimation pattern 505, a "3+2" pattern exists. The first three PRBs (i.e., PRB0 to PRB2) and the last two PRBs (i.e., PRB18 and PRB19) are decimated. The remaining PRBs of the SSB are transmitted.

[0164] In the fourth thinning pattern 507, a "4+1" pattern exists. The first four PRBs (i.e., PRB0 to PRB3) and the last PRB (i.e., PRB19) are thinned out. The remaining PRBs of the SSB are transmitted.

[0165] It should be understood that the SSB bandwidths of 20 PRBs and 15 PRBs, respectively, are used as examples only, and in other examples, SSBs of other suitable lengths can be thinned to other suitable lengths using different decimation patterns 501, 503, 505, 507.

[0166] A control resource set (CORESET) is a set of physical resources and parameters used to carry the physical downlink control channel (PDCCH) / downlink control information. It is conceptually equivalent in function to the LTE PDCCH region (the first 1, 2, 3, or 4 OFDM symbols in a subframe). In the LTE PDCCH region, the PDCCH spans the entire channel bandwidth, while the NR CORESET region spans the frequency domain. in It is localized to specific regions.

[0167] In the case of CORESET,

number

number

number

[0168] The UE may receive signals and channels as shown in Figure 4. First, the UE detects the PSS and SSS. Following this, the UE demodulates / decodes the PBCH. The UE then reads a configuration index from the PBCH / MIB. The configuration index references a CORESET#0 configuration table (such as Table 1 below) and, more specifically, references specific 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 in which the first subcarrier of the SSB is located. This is shown in the fifth column of Table 1 below. The SSBs are in the same subcarrier raster, but not necessarily in the same RB raster as CORESET#0. [Table 1]

[0169] FIG. 6 shows an example diagram of a CORESET resource allocation including resource block offsets.

[0170] The signals and channels are provided for the blocks in Figure 4. For simplicity, the same labels are provided for the blocks in Figure 6 as are used in Figure 4.

[0171] Also provided is a first CORESET configuration 601 having an offset of 0. The offset of 0 may be determined from Table 1, for example, for index 0 or index 3. Also provided is a second CORESET configuration 603 having an offset of 2. The offset of 2 may be determined from Table 1, for example, for index 1 or index 4. Also provided is a third CORESET configuration 605 having an offset of 4. The offset of 4 may be determined from Table 1, for example, for index 2 or index 4. The offset is between the first PRB of CORESET#0 and the first PRB (of the received block) in which the first subcarrier of the SSB is located.

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

[0173] There is a special type of core set called CORESET0 or CORESET#0. This CORESET is the CORESET that transmits the PDCCH for SIB1 scheduling. There are many parameters involved in defining these CORESETs, and these parameters are specified by Radio Resource Control (RRC) messages. However, CORESET0 cannot be specified by RRC because it needs to be used before any RRC message is transmitted. This implies that CORESET0 needs to be configured by some predetermined processes and predetermined parameters. Therefore, CORESET#0 is configured by separate processes and predetermined parameters summarized in the table below. [Table 2]

[0174] CORESET#0 may also be configured in PDCCH-ConfigCommon included in SIB1. Alternatively, CORESET#0 may be configured in the UE by dedicated signaling. In these cases, the configuration may be performed using a 4-bit value shown in the same table as the index provided in the MIB.

[0175] Because CORESET0 is not configured using RRC signaling, deriving the CORESET0 configuration can be difficult in sub-5 MHz scenarios, especially in sub-5 MHz NR scenarios. In some systems, mechanisms to address these scenarios involve increased complexity in the UE and / or proposing significant changes to current standards / specifications. One or more of the following examples aim to minimize the complexity associated with determining the CORESET0 configuration, specifically for scenarios with PBCH bandwidths of less than 20 RBs.

[0176] In the example, a method is provided, in which, when a CORESET0 (CORESET#0) configuration is determined, the determined PBCH (frequency in Based on the minimum resource block, the UE selects the (frequency in ) Determine the minimum RB.

[0177] The minimum RB for the PBCH may be the minimum RB at which the PBCH is transmitted by the network. In some examples, the minimum RB for the PBCH may be the minimum RB at which the PBCH is transmitted after resource block decimation. This determination of the minimum RB may be achieved by a (new) interpretation of the "Offset (RB)" parameter in Table 1 above. This is explained in more detail below.

[0178] In some examples, determining the CORESET0 configuration in this manner may assume a channel bandwidth of 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 channel bandwidth (CBW) of 3 MHz. The CBW may be determined by the UE from the determined synchronization raster point. In the example of a 3 MHz CBW, based on this determination, the UE knows that there are 15 valid RBs available for the PBCH.

[0179] This determination of the CORESET0 configuration is explained in more detail below.

[0180] In some examples, when determining valid PRBs for a CORESET0 configuration, this determination is made from among the RBs that are valid for the PBCH, and the RBs defined as valid for CORESET0 are defined by one of the following: i) the PRBs valid for CORESET0 have full control channel elements (CCEs); and ii) the PRBs valid for CORESET0 cover 15 PRBs (full and partial CCEs). For both options, the time domain of CORESET0 in The same outcome can be achieved if the number of symbols is equal to 2. In CORESET0, the REG bundle size considered is 6. Therefore, one CCE is either 2 symbols x 3 RBs or 3 symbols x 2 RBs. A "perfect" CCE is one that is defined with a resolution of 3 RBs for a 2-symbol CORESET or 2 RBs for a 3-symbol CORESET when defining valid RBs for CORESET0.

[0181] In some examples, upon determining the CORESET0 configuration, the size of CORESET0 is modified by one of the following alternatives. The size modification can occur when monitoring at least a predefined search space. Examples of predefined search spaces include Type0_PDCCH, Type0A_PDCCH, and Type2_PDCCH. The alternatives for the size of CORESET0 include: i) the number of RBs (frequency domain of the CORESET0 configuration) in , i.e.

number

number

number

number

[0182] In some examples, when determining the CORESET0 configuration, the UE assumes that the relevant CCEs follow a non-interleaved CCE / non-interleaved CCE mapping. PDCCH candidates contain consecutive CCE indices. Therefore, the result of non-interleaved CCEs is a contiguous frequency allocation of PDCCH candidates, which maximizes the number of CCEs available for PDCCH candidates when bandwidth is limited. In current systems, only interleaved mapping is supported for CORESET#0. This limits the number of CCEs available per PDCCH candidate for a 3 MHz bandwidth (15 RBs).

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

[0184] In some examples, after receiving PDCCH-ConfigCommon, the UE determines the CORESET0 configuration according to one of the following: a) the same CORESET0 determination (as described above) is used for all search spaces that use CORESET0 in the initial bandwidth portion (BWP), or b) a wider CORESET0 is defined for initial BWP search spaces that use CORESET0 but not Type0_PDCCH. CORESET0 is defined based on the controlResourceSetZero index in PDCCH-ConfigCommon, and interprets Table 1 (shown above) as follows:

[0185] An "Offset (RB)" value of 0 (in Table 1) indicates that the lower edge of CORESET0 and the non-decimated PBCH RBs are aligned. An "Offset (RB)" value of 4 indicates that the upper edge of CORESET0 and the non-decimated PBCH RBs are aligned. This is explained in more detail below and shown in Figure 7.

[0186] An "Offset (RB)" value of 2 (in Table 1) indicates the CCE offset between the lower edge of CORESET0 and the lower edge of the non-decimated PBCH. The CCE offset is an integer value. For example, the integer value is 2. In other examples, the integer value is greater than 2.

[0187] In the example table with alternative values ​​in Table 1, an "Offset (RB)" value of 1 may indicate a CCE offset between the lower edge of CORESET0 and the lower edge of the non-decimated PBCH. The CCE offset is an integer value. For example, the integer value is 1. This can be seen in configuration 1007 of FIG. 10, described in further detail below. In other examples, the integer value is greater than 1. This offset maintains CCE alignment with Type0_PDCCH CORESET0 while substantially centering the CORESET#0 resource (with respect to the PBCH).

[0188] The number of RBs shown in Table 1 (i.e., "Offset (RB)") may, in some examples, be reduced to the number of valid RBs in the initial BWP. Valid PRBs may be defined according to options a) and b) as defined above and applied to the RBs in the initial BWP. For valid RBs, the 2CCE offset according to option a) above is shown in FIG. 8.

[0189] Figure 7 shows a schematic diagram of the CORESET0 configuration within the initial BWP of 22PRB.

[0190] Figure 7 shows a 15 PRB channel bandwidth (CBW) 701. The 15 PRB CBW 701 corresponds to the PBCH. The sequence of 5 CCEs 703 is aligned with the 15 PRB CBW 701 at the lower and upper edges. The 5 CCEs 703 are a (2-symbol) CORESET0 subset available for SIB1 scheduling 705.

[0191] A "Point A" labeled 707 is provided. An initial BWP offset 709 is provided from "Point A" to the initial BWP PRB 711. The initial BWP PRB is 22 PRBs long. The upper edge of the initial BWP PRB is aligned with the 15 PRB CBW 701 and 5 CCE 703.

[0192] A two-symbol CORESET0 configuration 713 is provided, which includes 7 CCEs and an invalid CCE 715 (at the lowest frequency). 7 CCEs and one invalid CCE equal 24 PRBs. The invalid CCE 715 is invalid because there is only a single PRB of the initial BWP 711 available, rather than the required 3 PRBs for a CCE. Thus, the CORESET0 configuration 717 includes 7 CCEs (or 21 PRBs). The upper edge of the CORESET0 configuration 717 is aligned with the 15 PRB CBW.

[0193] FIG. 8a shows another schematic diagram of the CORESET0 configuration in an initial BWP of 20 PRB with a 2 CCE offset.

[0194] As noted above, the "Offset (RB)" value of 2 indicates the CCE offset between the lower edge of CORESET0 and the lower edge of the non-decimated PBCH. In the example of Figure 8a, this CCE offset is 2.

[0195] 8a shows a 15PRB CBW 801. The sequence of 5CCEs 803 is aligned at the lower and upper edges with the 15PRB CBW 801. The 5CCEs 803 are a (2-symbol) CORESET0 subset of the SIB1 scheduling 805.

[0196] A "Point A" is provided, labeled 807. An initial BWP offset 809 is provided from "Point A" to the initial BWP PRB 811. The initial BWP PRB is 20 PRBs long.

[0197] A two-symbol CORESET0 configuration 813 is provided that includes (at the lowest frequency) six CCEs and two invalid CCEs 815. The invalid CCEs 815 are invalid because there are only two PRBs of the initial BWP 711 available, rather than the six PRBs required for two aligned CCEs.

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

[0199] FIG. 8b shows another schematic diagram of the CORESET0 configuration in an initial BWP of 24 PRB with a 2 CCE offset.

[0200] As noted above, the "Offset (RB)" value of 2 indicates the CCE offset between the lower edge of CORESET0 and the lower edge of the non-decimated PBCH. In the example of Figure 8b, this CCE offset is 2.

[0201] 8b shows 15PRB CBW 851. The sequence of 5CCE 853 is aligned at the lower and upper edges with 15PRB CBW 851. 5CCE 853 is a (2-symbol) CORESET0 subset of SIB1 scheduling 855.

[0202] A "Point A" is provided, labeled 857. An initial BWP offset 859 is provided from "Point A" to the initial BWP PRB 861. The initial BWP PRB is 24 PRBs long.

[0203] A two-symbol CORESET0 configuration 863 is provided, which includes 8 CCEs. Thus, the CORESET0 configuration 867 includes 8 CCEs (or 24 PRBs). The lower and upper edges of the CORESET0 configuration 867 are aligned with the 24 PRB initial BWP 861. There is a 2 CCE offset 865 between the lower edge of the CORESET0 configuration 867 and the lower edges of the 15 PRB CBW 851 and 5 CCEs 853.

[0204] As described above, a method is provided, and by this method, after determining a CORESET0 (CORESET#0) configuration, the UE determines a (frequency) minimum resource block of the CORESET0 configuration based on the determined minimum resource block of the non-thinned PBCH. in ) determine the minimum PRB. In the following example, it is assumed that the number of RBs in CORESET0 is 24. In other examples, more or less than 24 RBs are used for CORESET0. This determination of CORESET0 by the UE or another suitable device may include one or more of the following steps: i) Receiving or detecting an initial access signal and / or channel from a network node, for example as shown in FIG. ii) Upon detecting the PSS and SSS at a particular synchronization raster point, determining that the PBCH is transmitted using a 15 PRB allocation, which may mean that the UE can determine a particular decimation pattern for the PBCH. iii) CORESET0 (frequency in ) determining the minimum PRB, which may include setting the minimum PRB of CORESET0 to be the same as the minimum RB of the non-thinned PBCH, or an RB on a common grid having subcarriers of the minimum RB of the non-thinned PBCH. iv) Determining valid PRBs for CORESET0 based on the PBCH and initial BWP. Determining CORESET0 size based on the PBCH and initial BWP. v) Determining the CCE allocation for CORESET0 based on determining the size of the valid PRBs and CORESET0.

[0205] 9a and 9b show schematic diagrams of the alignment between valid PRBs of CORESET0 and valid PRBs of the PBCH, where each block / square in these diagrams represents a PRB.

[0206] Both Figures 9a and 9b show a common RB grid 901 of 15 PRBs for reference. Channel raster points 903 are provided in the center of the 15 PRBs, i.e., 7.5 PRBs in this example. The channel raster is in the center of the carrier. The synchronization raster is in the center of the PSS / SSS. The channel and synchronization rasters may be offset from each other.

[0207] For blocks / squares, checkerboard pattern represents common RB. Brick pattern represents PSS. Dot pattern represents SSS. Vertical stripe pattern represents PBCH. Solid blocks represent thinned PRB. Alignment between options (and PRBs) indicates alignment in frequency between the option and the reference.

[0208] The first option 905 has a "2+3" decimation pattern. The first option 905 has a PSS 907 and an SSS 909, each containing 12 PRBs (each of which is greater than one symbol). A PBCH 911 is also provided with lower and upper edges aligned with the common RB grid 901. The synchronization raster point 913 of the first option 905 is offset from the channel raster 903 by +90 kHz, which corresponds to six subcarriers (SC).

[0209] The second option 915 has a "3+2" decimation pattern. The second option 915 has a PSS 917 and an SSS 919, each containing 12 PRBs (each of which is greater than one symbol). A PBCH 921 is also provided with lower and upper edges aligned with the common RB grid 901. The synchronization raster point 923 of the second option 915 is offset from the channel raster 903 by -90 kHz, which corresponds to six subcarriers (SC).

[0210] In Figure 9b, the third option 925 has a "4+1" thinning pattern. The third option 925 has a PSS 927 and an SSS 929, each containing 12 PRBs (each of which is greater than one symbol). A PBCH 931 is also provided, with its lower and upper edges aligned with the common RB grid 901. The synchronization raster point 933 of the second option 925 is offset from the channel raster 903 by -270 kHz, which corresponds to 18 subcarriers (SC).

[0211] The fourth option 935 has a "1+4" decimation pattern. The fourth option 935 has a PSS 937 and an SSS 939, each containing 12 PRBs (each one symbol more). A PBCH 941 is also provided with lower and upper edges aligned with the common RB grid 901. The synchronization raster point 943 of the second option 935 is offset from the channel raster 903 by +270 kHz, which corresponds to 18 subcarriers (SC).

[0212] FIG. 10 shows a schematic diagram of CORESET0 sizing and CCE allocation options.

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

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

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

[0216] The fourth CORESET0 configuration 1009 includes 3 symbols and 8 CCEs. Each CCE corresponds to 2 PRBs. Thus, the fourth CORESET0 configuration 1009 includes 16 PRBs. Because the PBCH 1001 includes 15 PRBs, one resource block is thinned out (1011) (i.e., 16-15=1 RB). The lower edge of the second CORESET0 configuration 1005 is aligned with the lower edge of the PBCH 1001.

[0217] One or more of the above examples has the advantage of having little impact on current specifications / standards, especially in the case of 3 MHz scenarios. The advantage of this approach is that it is not necessary to redefine / modify Table 1 included above (which is the same as Table 13-1 in the 3GPP TS38.213 specification). In this case, it is sufficient to add a new interpretation to certain rows of the table (at least indexes [0,3]). Furthermore, one or more of the examples requires only minor changes to the implementation, and for example, changes to the interleaving pattern can be avoided. This optimizes (and improves) performance. One or more of the examples enables UE multiplexing by allowing candidate / CCE alignment with other CORESETs.

[0218] 11 illustrates an exemplary method flow performed by an apparatus. The apparatus may be included in a user equipment. In an example, the apparatus may be a user equipment. In an example, the apparatus may be for a user equipment.

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

[0220] At S1103, the method includes determining a number of resource blocks allocated to the physical broadcast channel using the detected primary and secondary synchronization signals.

[0221] In S1105, the method includes: in , including determining the smallest resource block.

[0222] In S1107, the method includes: determining a frequency of a control resource set 0 (CORESET#0) that is the same as the determined minimum resource block of the physical broadcast channel; in , including determining the smallest resource block.

[0223] FIG. 12 shows 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) memory stick) that store instructions and / or parameters 1202 that, when executed by a processor, enable the processor to perform one or more of the steps of the method of FIG. 11.

[0224] Although exemplary embodiments have been described above, it should be noted that several variations and modifications may be made to the disclosed solutions without departing from the scope of the present invention.

[0225] Thus, examples may vary within the scope of the appended claims. In general, some embodiments may be implemented in hardware or special purpose circuits, software, logic, or any combination thereof. For example, certain aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device, but embodiments are not limited thereto. While various embodiments may be illustrated and described as block diagrams, flowcharts, or using some other graphical representations, it is well understood that these blocks, apparatus, systems, techniques, or methods described herein may be implemented in, by way of non-limiting example, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing device, or some combination thereof.

[0226] Examples may be implemented by computer software stored in memory and executable by at least one data processor of the relevant entity, or by hardware, or by a combination of software and hardware. Furthermore, in this regard, it should be noted that any of the procedures may represent program steps, or interconnected logic circuits, blocks, and functions, or a combination of program steps and logic circuits, blocks, and functions. Software may be stored on physical media, such as memory chips or blocks implemented within a processor, magnetic media, such as hard disks or floppy disks, and optical media, such as DVDs and their data variants, CDs.

[0227] As used herein, the term "non-transitory" is not a limitation regarding the permanence of the data storage (eg, RAM vs. ROM), but rather a limitation of the medium itself (ie, tangible rather than signal).

[0228] As used herein, "at least one of: " and "at least one of " and similar expressions where a list of two or more elements is joined by "and" or "or" mean at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0229] The memory may be of any type suitable for the local technology environment and may 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 may be of any type suitable for the local technology environment and may include, by way of non-limiting example, one or more of a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), gate-level circuitry, and a processor based on a multi-core processor architecture.

[0230] Alternatively, or in addition, some examples may be implemented using circuitry that may be configured to perform one or more of the functions and / or method steps described above, and that may be provided in a base station and / or a communications device.

[0231] As used in this application, the term "circuitry" may refer to one or more or all of the following: (a) hardware-only circuit implementations (e.g., implementations in analog and / or digital circuitry only); (b) a combination of hardware circuitry and software, such as: (i) a combination of analog and / or digital hardware circuitry(s) and software / firmware; and (ii) any portion of hardware processor(s) (including digital signal processor(s)) with software, software, and memory(s) that cooperate to cause an apparatus, such as a communications device or base station, to perform the various functions described above; and (c) Hardware circuit(s) and / or processor(s), such as microprocessor(s) or part of microprocessor(s), that require software (e.g., firmware) for operation, although software may not be present if not necessary for operation.

[0232] This definition of circuit applies to all uses of the term in this application, including any claims. As a further example, the term "circuit," as used in this application, covers implementations of simply a hardware circuit or processor (or processors), or of portions of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term "circuit" also encompasses, for example, integrated devices.

[0233] The foregoing description has provided a complete and informative description of several embodiments by way of exemplary and non-limiting examples. However, various modifications and adaptations 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 are still intended to be included within the scope defined by the appended claims.

Claims

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

2. means for determining valid resource blocks for the CORESET#0 of the physical downlink control channel by aligning with valid resource blocks of the physical broadcast channel to determine the size of the CORESET#0 of the physical downlink control channel; means for determining an allocation of control channel elements of the CORESET#0 of the physical downlink control channel based on i) the smallest resource block and ii) the available resource block of the CORESET#0; The apparatus of claim 1 further comprising:

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

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

5. 4. The apparatus according to claim 2, wherein the means for determining valid resource blocks for the CORESET #0 of the physical downlink control channel comprises means for determining that the valid resource blocks for the CORESET #0 of the physical downlink control channel are resource blocks covering 15 resource blocks, including full control channel elements and partial control channel elements.

6. The means for determining the size of the CORESET#0 of the physical downlink control channel comprises: means for determining the maximum number of complete control channel elements that can fit into 15 resource blocks; means for determining the maximum number of full and partial control channel elements that will fit into the 15 resource blocks; means for determining the number of complete control channel elements using a predetermined number of control channel elements; means for determining a number of resource blocks using a predetermined multiple of six resource blocks that exceeds said total of fifteen resource blocks; The device according to any one of claims 2 to 3, comprising one of:

7. 7. The apparatus of claim 2, wherein the means for determining an allocation of the control channel elements of the CORESET #0 of the physical downlink control channel comprises means for determining an allocation of the control channel elements of the CORESET #0 of the physical downlink control channel using a mapping of non-interleaved control channel elements.

8. 8. The apparatus according to claim 2, further comprising: means for, in response to determining the valid resource blocks in the CORESET #0 of the physical downlink control channel, determining, using the physical broadcast channel, an index providing information regarding allocation of the control channel elements in the valid resource blocks of the CORESET #0 of the physical downlink control channel.

9. The device comprises: means for receiving, from said network node, a configuration associated with said physical downlink control channel; means for determining the CORESET#0 of all search spaces of the physical downlink control channel using the CORESET#0 within an initial bandwidth portion in response to said receiving; The apparatus of any one of claims 2 to 8, further comprising:

10. The device comprises: means for receiving, from said network node, a configuration associated with said physical downlink control channel; means for determining, using one or more parameters included in the configuration associated with the physical downlink control channel, whether one of a lower edge in frequency or an upper edge in frequency of the CORESET#0 of the physical downlink control channel is aligned with a resource block of the physical broadcast channel; The apparatus of any one of claims 2 to 8, further comprising:

11. 11. The apparatus of claim 1, further comprising means for determining a channel bandwidth in which the network node is operating using the detected primary and secondary synchronization signals.

12. 12. The apparatus of claim 11, wherein the means for determining comprises means for determining a synchronization raster point using the detected primary and secondary synchronization signals to determine the channel bandwidth on which the network node is operating.

13. The apparatus of any preceding claim, wherein the apparatus is one of: for a user equipment; the apparatus is located within the user equipment; or the apparatus is the user equipment.

14. Detecting primary and secondary synchronization signals received from a network node; determining a number of resource blocks allocated to a physical broadcast channel using the detected primary and secondary synchronization signals; determining a minimum resource block in frequency of the physical broadcast channel; determining a minimum resource block in frequency of a control resource set 0 (CORESET#0) of the physical downlink control channel, the minimum resource block being the same as the determined minimum resource block of the physical broadcast channel; A method comprising:

15. determining valid resource blocks for the CORESET#0 of the physical downlink control channel by aligning with valid resource blocks of the physical broadcast channel to determine the size of the CORESET#0 of the physical downlink control channel; determining an allocation of control channel elements of the CORESET#0 of the physical downlink control channel based on i) the smallest resource blocks and ii) the available resource blocks of the CORESET#0; 15. The method of claim 14, further comprising:

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

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

18. 17. The method of claim 15 or 16, wherein determining the valid resource blocks in the CORESET #0 comprises determining that the valid resource blocks in the CORESET #0 of the physical downlink control channel are resource blocks covering 15 resource blocks with full control channel elements and partial control channel elements.

19. determining the size of the CORESET#0 of the physical downlink control channel, determining the maximum number of complete control channel elements that can fit into 15 resource blocks; determining a maximum number of the full and partial control channel elements that will fit into the 15 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 predetermined multiple of six resource blocks that is greater than the total of 15 resource blocks; The method according to claims 15 to 16, comprising one of the following:

20. 20. The method of claim 15, wherein determining the allocation of the control channel elements of the CORESET #0 of the physical downlink control channel comprises determining the allocation of the control channel elements of the CORESET #0 of the physical downlink control channel using a mapping of non-interleaved control channel elements.

21. 21. The method of claim 15, further comprising, in response to determining the valid resource blocks in the CORESET #0, using the physical broadcast channel to determine an index providing information about allocation of the control channel elements within the valid resource blocks of the CORESET #0 of the physical downlink control channel.

22. receiving, from the network node, a configuration associated with a physical downlink control channel; In response to receiving, determining the CORESET#0 of all search spaces of the physical downlink control channel using the CORESET#0 within an initial bandwidth portion; The method of any one of claims 15 to 21, further comprising:

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

24. The method of any of claims 14 to 23, further comprising determining a channel bandwidth in which the network node is operating using the detected primary and secondary synchronization signals.

25. 25. The method of claim 24, wherein said determining comprises determining a synchronization raster point using the detected primary and secondary synchronization signals to determine the channel bandwidth on which the network node is operating.

26. The method according to any of claims 14 to 25, wherein said method is one of those performed by a user equipment.

27. at least one processor; at least one memory for storing instructions; An apparatus comprising: The instructions, when executed by the at least one processor, cause at least Detecting primary and secondary synchronization signals received from a network node; determining a number of resource blocks allocated to a physical broadcast channel using the detected primary and secondary synchronization signals; determining a minimum resource block in frequency of the physical broadcast channel; determining a minimum resource block in frequency of a control resource set 0 (CORESET#0) of the physical downlink control channel, the minimum resource block being the same as the determined minimum resource block of the physical broadcast channel; causing the device to

28. A computer program comprising instructions, The instructions, when executed by the device, perform at least the following: Detecting primary and secondary synchronization signals received from a network node; determining a number of resource blocks allocated to a physical broadcast channel using the detected primary and secondary synchronization signals; determining a minimum resource block in frequency of the physical broadcast channel; determining a minimum resource block in frequency of a control resource set 0 (CORESET#0) that is the same as the determined minimum resource block of the physical broadcast channel; The computer program causes the device to execute the above.

Images