WO2024104756A1 - Puncturing assumption for control channel in narrowband new radio operation - Google Patents

Abstract

Systems, methods, apparatuses, and computer program products for dynamically changing gap priorities. A method may include detecting a synchronization signal on a synchronization raster point on a band of interest. The method may also include determining a puncturing assumption pattern associated with the synchronization signal for a communication channel based on bits of a radio parameter. The method may further include demodulating and decoding the communication channel based on the puncturing assumption associated with the synchronization raster point.

Description

TITLE:

PUNCTURING ASSUMPTION FOR CONTROL CHANNEL IN

NARROWBAND NEW RADIO OPERATION

FIELD:

[0001] Some example embodiments may generally relate to mobile or wireless telecommunication systems, such as Long Term Evolution (LTE) or fifth generation (5G) new radio (NR) access technology, 5G beyond, 5G-Advanced (NR Rel-18 and beyond), or other communications systems. For example, certain example embodiments may relate to apparatuses, systems, and/or methods for puncturing assumptions for a control channel in narrowband (NB) NR operation.

BACKGROUND:

[0002] Examples of mobile or wireless telecommunication systems may include the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), LTE Evolved UTRAN (E- UTRAN), LTE- Advanced (LTE- A), MulteFire, LTE- A Pro, and/or fifth generation (5G) radio access technology or NR access technology. 5G wireless systems refer to the next generation (NG) of radio systems and network architecture. 5G network technology is mostly based on new radio (NR) technology, but the 5G (or NG) network can also build on E-UTRAN radio. It is estimated that NR may provide bitrates on the order of 10-20 Gbit/s or higher, and may support at least enhanced mobile broadband (eMBB) and ultra-reliable low-latency communication (URLLC) as well as massive machine-type communication (mMTC). NR is expected to deliver extreme broadband and ultra-robust, low-latency connectivity and massive networking to support the loT.

SUMMARY: [0003] Some example embodiments may be directed to a method. The method may include detecting a synchronization signal on a synchronization raster point on a band of interest. The method may also include determining a puncturing assumption pattern associated with the synchronization signal for a communication channel based on bits of a radio parameter. The method may further include demodulating and decoding the communication channel based on the puncturing assumption associated with the synchronization raster point. [0004] Other example embodiments may be directed to an apparatus. The apparatus may include at least one processor and at least one memory including computer program code. The at least one memory and computer program code may also be configured to, with the at least one processor, cause the apparatus at least to detect a synchronization signal on a synchronization raster point on a band of interest. The apparatus may also be caused to determine a puncturing assumption pattern associated with the synchronization signal for a communication channel based on bits of a radio parameter. The apparatus may further be caused to demodulate and decode the communication channel based on the puncturing assumption associated with the synchronization raster point.

[0005] Other example embodiments may be directed to an apparatus. The apparatus may include means for detecting a synchronization signal on a synchronization raster point on a band of interest. The apparatus may also include means for determining a puncturing assumption pattern associated with the synchronization signal for a communication channel based on bits of a radio parameter. The apparatus may further include means for demodulating and decoding the communication channel based on the puncturing assumption associated with the synchronization raster point.

[0006] In accordance with other example embodiments, a non-transitory computer readable medium may be encoded with instructions that may, when executed in hardware, perform a method. The method may include detecting a synchronization signal on a synchronization raster point on a band of interest. The method may also include determining a puncturing assumption pattern associated with the synchronization signal for a communication channel based on bits of a radio parameter. The method may further include demodulating and decoding the communication channel based on the puncturing assumption associated with the synchronization raster point.

[0007] Other example embodiments may be directed to a computer program product that performs a method. The method may include detecting a synchronization signal on a synchronization raster point on a band of interest. The method may also include determining a puncturing assumption pattern associated with the synchronization signal for a communication channel based on bits of a radio parameter. The method may further include demodulating and decoding the communication channel based on the puncturing assumption associated with the synchronization raster point.

[0008] Other example embodiments may be directed to an apparatus that may include circuitry configured to detect a synchronization signal on a synchronization raster point on a band of interest. The apparatus may also include circuitry configured to determine a puncturing assumption pattern associated with the synchronization signal for a communication channel based on bits of a radio parameter. The apparatus may further include circuitry configured to demodulate and decode the communication channel based on the puncturing assumption associated with the synchronization raster point.

BRIEF DESCRIPTION OF THE DRAWINGS:

[0009] For proper understanding of example embodiments, reference should be made to the accompanying drawings, wherein:

[0010] FIG. 1 illustrates an example of deployment scenarios.

[0011] FIG. 2 illustrates an example of existing NR initial access signals and channels with 15 kHz sub-carrier spacing. [0012] FIG. 3 illustrates an example of different puncturing patterns for a synchronization signal block (SSB).

[0013] FIG. 4 illustrates an example control resource set (CORESET) #0 resource allocation signaling.

[0014] FIG. 5 illustrates a summary of a set of predefined parameters.

[0015] FIG. 6 illustrates an example principle of synchronization raster points at a frequency range of 0-3000 MHz.

[0016] FIG. 7 illustrates an example synchronization raster consideration for a 3 MHz bandwidth.

[0017] FIG. 8 illustrates a table of valid synchronization raster points for nlOO based on a synchronization raster design.

[0018] FIG. 9 illustrates an example of synchronization raster points for punctured and non-punctured SSBs in bands of interest.

[0019] FIG. 10 illustrates an example of control channel element (CCE) indexes.

[0020] FIG. 11 illustrates an example performance degradation due to puncturing.

[0021] FIG. 12 illustrates a set of resource blocks and slot symbols of CORESET, according to certain example embodiments.

[0022] FIG. 13 illustrates an example relationship between k_ssb and CORESET#0, according to certain example embodiments.

[0023] FIG. 14 illustrates an example relationship between k_ssb, CORESET#0, and SSB/CORESET alignment, according to certain example embodiments.

[0024] FIG. 15 illustrates an example relationship between k_ssb, CORESET#0, SSB/CORESET alignment, and resource element group-to- control channel element (REG-to-CCE) mapping, according to certain example embodiments.

[0025] FIG. 16 illustrates an example relationship between k_ssb, CORESET#0, SSB/CORESET alignment, REG-to-CCE mapping, andPBCH size verification, according to certain example embodiments.

[0026] FIG. 17 illustrates an example relationship between k_ssb, CORESET#0, SSB/CORESET alignment, TypeO-physical downlink control channel (PDCCH) repetition, and physical broadcast channel (PBCH) size verification, according to certain example embodiments.

[0027] FIG. 18 illustrates an example relationship between k_ssb, CORESET#0, SSB/CORESET alignment, SSB sub-carrier offset, and PBCH size verification, according to certain example embodiments.

[0028] FIG. 19 illustrates an example relationship between k_ssb bits, a number of RBs for CORESET#0, and SSB/CORESET alignment, according to certain example embodiments.

[0029] FIG. 20 illustrates an example relationship between k_ssb, SSB subcarrier offset, number of RBs for CORESET#0, and PBCH size verification, according to certain example embodiments.

[0030] FIG. 21 illustrates an example flow diagram of another method, according to certain example embodiments.

[0031] FIG. 22 illustrates a set of apparatuses, according to certain example embodiments.

DETAILED DESCRIPTION:

[0032] It will be readily understood that the components of certain example embodiments, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. The following is a detailed description of some example embodiments of systems, methods, apparatuses, and computer program products for puncturing assumption for a control channel in NB NR operation. For instance, certain example embodiments may be directed to determining a puncturing assumption for the control channel based on k_ssb NB NR operation. [0033] The features, structures, or characteristics of example embodiments described throughout this specification may be combined in any suitable manner in one or more example embodiments. For example, the usage of the phrases “certain embodiments,” “an example embodiment,” “some embodiments,” or other similar language, throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment. Thus, appearances of the phrases “in certain embodiments,” “an example embodiment,” “in some embodiments,” “in other embodiments,” or other similar language, throughout this specification do not necessarily refer to the same group of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more example embodiments. Further, the terms “cell”, “node”, “gNB”, “network” or other similar language throughout this specification may be used interchangeably.

[0034] As used herein, “at least one of the following: <a list of two or more elements>” and “at least one of <a list of two or more elements>” and similar wording, where the list of two or more elements are 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 the elements.

[0035] Certain example embodiments described herein may be directed to NB NR, or otherwise known as NR support for dedicated spectrum less than 5 MHz. NB NR is an merging scenario driven by the future of railway communications needs, as well as some smart grid operators. It may also be possible that there are additional usage scenarios in the future (e.g., machinetype communication, or special bandwidth scenarios for smartphones) related to railway communication needs.

[0036] The future railway mobile communication system (FRMCS) may have certain considerations including, for example, an agreement on using NR, 2x5.6 MHz frequency division duplex (FDD) (874.4 - 880 MHz / 919.4 - 925 MHz), soft migration from a global system for mobile communications- railway (GSM-R) requiring parallel operation of GSM-R and NR, and in some scenarios, it may be assumed that the NR may be allocated at a 3 MHz channel. [0037] Potential deployment scenarios may include, for NR downlink (DL)/uplink (UL) and GSM-R DL/UL: an adjacent channel deployment, an overlay deployment with compact GSM-R channel placement, an overlay deployment with GSM-R channels distributed over 4 MHz core band, and an overlay deployment with GSM-R channels distributed over full extended railways GSM (ER-GSM) band. An adjacent channel deployment of NR and GSM-R may have advantages of an easier implementation for NR scheduler, and only one boundary between NR and GSM-R leading to a simpler and more predictable co-existence.

[0038] Narrowband NR has also been considered for ‘Smart grids’ including 2x3 MHz FDD in 900MHz in the USA. 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.

[0039] In NR Rel-15 to Rel-17, channel bandwidths (CBWs) under 5MHz are not currently supported. It has been proposed to adapt NR to the 3-5 MHz spectrum allocations with minimal changes, building on the existing NR ecosystem. Additionally, it has been identified that there are scenarios that are emerging in which it may be beneficial to enable the operation of 5G NR in a narrower bandwidth than the 5MHz channels for which it was originally designed. For example, operation down to 3 MHz, and deployment of NR in the 900 MHz FRMCS band is to operate alongside any legacy GSM-R carriers within a 5.6MHz bandwidth, which permits approximately 3.6 MHz bandwidth to be used for NR. Similarly, there may be some cases whereby 3 MHz channels are available for NR.

[0040] FIG. 1 illustrates an example of deployment scenarios. In particular, FIG. 1 illustrates simultaneous deployment options for NR and GSM-R within a 5.6 MHz DL (left), and UL (right). As illustrated in FIG. 1, adjacent channel deployment of NR and GSM-R may be preferred. In doing so, it may be possible to achieve easier implementation for an NR scheduler. Additionally, there may be one boundary between NR and GSM-R, which may result in a simpler and more predictable co-existence. Furthermore, NB- NR may be connected for smart grids including, for example, a 2x3 MHz FDD 900 MHz in the US. The NB NR may also be considered for public safety measures including, for example, a 2x3 MHz FDD in band 28 for public protection and disaster relieve (PPDR). Unlike reduced capability (RedCap) user equipment (UEs), the target markets do not have significant constraints on device size, complexity, number of antennas, and power consumptions. As such, optimization for these characteristics may be superfluous. In NR, CBWs <5 MHz are not supported, and the general target may be to adapt NR to approximately 3-5 MHz spectrum allocations with minimal changes, thereby building on the existing NR ecosystem.

[0041] FIG. 2 illustrates an example of existing NR initial access signals and channels with 15 kHz sub-carrier spacing. In some scenarios, it may be beneficial to enable the operation of 5G NR in a narrower bandwidth than the 5 MHz channels for which it was originally designed (e.g., down to approximately 3 MHz). For example, deployment of NR in the 900 MHz FRMCS band may need to take place alongside legacy GSM-R carriers within a 5.6 MHz bandwidth, which permits about 3.6 MHz to be used for NR. Similarly, there may be some cases where only 3 MHz channels or even narrower channels are available for NR.

[0042] The essential signals and channels transmitted, more specifically, signals and channels of the synchronization signal and physical broadcast channel (PBCH) block (SSB), by the NR base stations (gNBs) are not designed for transmission in such narrow channels. [0043] After detecting the primary synchronization signal (PSS) and the secondary synchronization signal (SSS), the UE may know, in addition to a physical cell ID, the slot timing within a 5 ms half frame and symbol timing. The UE may then determine resource elements for the PBCH demodulation reference signal (DMRS), and data to receive PBCH payload. The PBCH may carry a master information block (MIB) signaling, which may be related to the frequency position (SSB frequency domain allocation related to a common resource block (CRB) grid), and timing (half frame timing and frame timing). The information may be contained either in a higher layer payload (i.e., MIB), as part of the physical layer bits in the transport block payload, or in DMRS.

[0044] FIG. 3 illustrates an example of different puncturing patterns for an SSB. A 3 MHz allocation to an NR system may mean max 15 physical resource block (PRB) channel bandwidth, assuming 90% spectrum utilization. For SSB, this may suggest a 5 PRB puncturing. Since a PSS/ SSS may remain unaffected, a max 4 PRB puncturing per side may take place. In other words, applicable puncturing patterns may include 1+4, 2+3, 3+2, and 4+1, as illustrated in FIG. 3. a

[0045] Puncturing of transmitted signals may be used to narrow down a transmission bandwidth with minimum change. For example, in a puncturing operation, a base station blanks any signals mapped on certain predefined PRBs that fall outside a desired transmission bandwidth. In this way, the base station will not transmit those signals. When a UE receives the transmission with punctured PRBs, the UE may null the punctured PRBs at the receiver. The UE may also null the punctured PRBs by, for example, setting the loglikelihood ratios (LLRs) to zero in the channel decoder.

[0046] An alternative to puncturing may include rate matching whereby input bits are matched to the available resources. Due to that, the sequence of rate matched bits may vary according to the resource size. With rate matching a receiver should know the resource size, in order to decode the packet correctly. [0047] Puncturing may also refer to a situation where at least part of signal generation processes (e.g., encoding and rate matching) is carried out according to a certain resource allocation but a portion of the generated signal is not transmitted. The dropped signal portion may be mapped on the frequency domain resources (e.g., subcarriers or resource blocks) that are punctured. Puncturing may be carried out with a predefined resolution, for example, with resource block (RB) resolution, or with control channel element (CCE) resolution. The resolution may vary from scenario to another.

[0048] FIG. 4 illustrates an example control resource set (CORESET) #0 resource allocation signaling. A CORESET may be defined as a set of physical resources and a set of parameters that is used to carry PDCCH/downlink control information (DCI). It is conceptually equivalent, in function, to the LTE PDCCH area (the first 1,2, 3, 4 OFDM symbols in a subframe). In LTE PDCCH region, the PDCCH is spread across the whole channel bandwidth, but the NR CORESET region is localized to a specific region in frequency domain. For a CORESET, N^^RESET is the number of RBs in the frequency domain of the CORESET. Nsymb^SET is the number of symbols in the time domain of the CORESET. N^°^RESET is the number of resource element groups (REGs) in a CORESET. Additionally, L is the REG bundle size, which may be set by the parameter CORESET-REG-bundle-size.

[0049] In CORESET #0 allocation determination by the UE, after the UE has detected PSS and SSS, and demodulated PBCH, the UE may read a configuration index from the PBCH/MIB. The configuration index may refer to a CORESET#0 configuration table, and more specifically to certain time and frequency resource allocation parameters. One of the parameters may define a RB offset between the first PRB of the CORESET#0 and the first PRB in which the first sub-carrier of the SSB may be located (SSB may be in the same sub-carrier raster, but not necessarily in the same RB raster as CORESET#0). [0050] As noted above, the SSB may be in the same sub-carrier raster as a common RB grid, but may not be aligned in the RB level. Sub-carrier offset between the SSB and common RB grid may be provided with a k_SSB parameter provided in the MIB. The k_SSB parameter may have several characteristics; for example, the k_SSB parameter in frequency range 1 (FR1) may have 5 bits with values from 0 to 23 used to indicate sub-carrier offset between the SSB and common RB grid. Additionally, when the SSB and CORESET #0 have the same SCS, only values 0, ... , 11 may be used.

[0051] In certain cases, CORESET#0 may be the one used for transmitting PDCCH for system information block 1 (SIB1) scheduling. CORESET#0 may not be configured by radio resource control (RRC) since it is used before the RRC connection is established. Thus, CORESET#0 may be configured by a separate process and predefined parameters, as summarized in FIG. 5. CORESET#0 may also be configured in PDCCH-Config ommon contained within SIB1, or configured to the UE with dedicated signaling. In particular, the configuration may be accomplished with a 4-bit value indicating to a table as the index provided in the MIB.

[0052] FIG. 6 illustrates an example principle of synchronization raster points at a frequency range of 0-3000 MHz. A channel raster may define a subset of radio frequency (RF) reference frequencies that may be used to identify the RF channel position in the UL and DL. The RF reference frequency for an RF channel may map to a resource element on the carrier. The channel raster for n8, n26, and n28 bands (intended for FRMC) may be 100 kHz. Additionally, the synchronization raster may indicate that the frequency positions of the synchronization block that may be used by the UE for system acquisition when explicit signaling of the synchronization block position is not present. In order to expedite cell searches, the synchronization raster may be much sparser than the channel raster. In the bands of interest, the channel raster may typically have a 100 kHz spacing the synchronization raster points may be defined in clusters of three points where the points in the cluster are separated by 100 kHz (the raster offsets within a cluster are 50, 150, and 250 kHz), and the clusters may be separated 1200 kHz from each other.

[0053] FIG. 7 illustrates an example synchronization raster consideration for a 3 MHz bandwidth. As illustrated in FIG. 7, for an allowed bandwidth of 3 MHz, and with the principle of not modifying PSS and SSS, the clusters of synchronization raster points may be separated by less than 1.2 MHz to facilitate two synchronization clusters. In FIG. 7, two channels of 3 MHz bandwidth are separated by 100 kHz, and the synchronization raster may be redesigned for NB NR operation. For a bandwidth of 3 MHz, and when the PSS and SSS are not modified, the clusters of synchronization raster points may be separated by less than 1.2 MHz in order to have at least one valid synchronization raster point for each 3 MHz channel when a 100 kHz channel raster is applied.

[0054] FIG. 8 illustrates a table of valid synchronization raster points for nlOO based on a synchronization raster design. For an analysis of a band nlOO, two guard band assumptions may be considered. A first band assumption may include 142.5 kHz assuming 3 MHz bandwidth allocation, and a second band assumption may include a 242.5 kHz assuming 5 MHz bandwidth allocation. Both assumptions may be made with a 90% spectrum utilization (SU). Additionally, valid synchronization raster points (so that PSS/SSS may be allowed in the band) for nl 00 may be based on a synchronization raster design, as illustrated in FIG. 8.

[0055] It may be observed from FIG. 8 that the current synchronization raster design in FR1 may not provide synchronization raster points in nlOO to support narrow channel bandwidth allocation in either of the edges of the band when assuming guard bands of 5 MHz NR allocation. Additionally, when assuming guard bands necessary for 3 MHz NR allocation (e.g., 142.5 kHz guard), PSS/SSS may be allocated in the lower part of the nlOO band. Thus, a new design may be needed for an nl 00 synchronization raster to support NB NR allocation in both ends of the band. Further, the synchronization raster points (or clusters) may be placed more closely than every 1.2 MHz for 3MHz NR operation. Although it may be desirable to define synchronization raster points with 100 kHz raster (i.e., same as channel raster), only a single SSB puncturing pattern for a given SSB Tx bandwidth would need to be defined. As an example, FIG. 9 illustrates synchronization raster points for punctured and non-punctured SSBs in bands of interest.

[0056] FIG. 10 illustrates an example of CCE indexes. In particular, FIG. 10 illustrates CCE indexes for a 2-symbol and a 3-symbol CORESET, interleaved mapping. FIG. 10 also illustrates the possible physical downlink control channel (PDCCH) transmissions for CORESET#0. For instance, it may be assumed that the transmission bandwidth may be reduced from one side (i.e., from upper frequencies/larger PRB indices). Here, CORESET#0 may utilize an interleaved mapping between CCE and resource element group (REG) bundle (consisting of 6 REGs). However, utilization of such interleaved mapping may result in some drawbacks.

[0057] For example, for a 2-symbol CORESET, AL8 (aggregation level 8) cannot be sent without puncturing (provide that the bandwidth is less than 4.32 MHz). Additionally, the minimum bandwidth for AL4 (without puncturing) may be 3.24 MHz. At the same time, 1/3 of the PRB resources (PRBs 6-11 in FIG. 10) may be unused. Further, the puncturing resolution at the CCE-level may be preferable since the UE is expected to average channel estimates within a CCE. However, the PRB level may also be considered, where the PRB level allows finer granularity than the CCE level.

[0058] As further illustrated in FIG. 10, with a 3-symbol CORESET, the AL8 may not be sent without puncturing (provided that the bandwidth is less than 3.6 MHz). At the same time, 20% of the PRB resources may be unused. Further, the minimum bandwidth for AL4 (without puncturing) may be 2.88 MHz, where 50% of the PRB resources may be unused. In this example, a puncturing resolution at the CCE-level may be preferable (since the UE is expected to average channel estimates within a CCE), but the PRB level may also be considered (PRB level may allow finer granularity than the CCE level). [0059] As described herein, excessive puncturing may reduce PDCCH coverage. In particular, PDCCH detection performance may be expected to suffer from the puncturing, and especially on high AL PDCCH candidates, the impact of puncturing may be significant. Similar findings may also be found from PBCH simulations.

[0060] With PBCH simulations in a scenario of unknown puncturing, the UE may suffer from significant performance degradation, as shown in FIG. 11. In particular, FIG. 11 illustrates a simulation case where there is one-sided puncturing of PBCH. Additionally, additive white Gaussian noise (AWGN) interference may be used to mimic GSM-R interference, and the gNB may not transmit PBCH on those GSM-R PRBs. Further, the UE may perform detection assuming a wrong PBCH Tx bandwidth (BW). As illustrated in FIG. 11 , degradation on signal-to-noise ratio (dSNR) that is needed for adequate PBCH detection performance is shown for different amounts of PRB puncturing (i.e., 2, 4, and 6 PRBs). Depending on the interference power, PBCH detection performance may be degraded by more than 5 dB. This may suggest that the UE is frequently unable to access the cell. It may also be noted that in deployment scenarios such as GSM-R refarming, GSM and NR BS may likely be co-located to the same sites, making the higher GSM power levels more probable.

[0061] Based on the above drawbacks, there may be a need for PDCCH performance improvements. However, problems may arise when using only AL4 and AL8. For instance, when using only AL4 to support more used CCEs with a given minimum BW, the difference in link performance between AL4 and AL8 may be more than 3 dB. As to the problem of using AL8, aggregation level 8 may not be used without puncturing. Based on PBCH results, 25% puncturing in the scenario where the UE does not know the actual puncturing pattern may be more than 5 dB (see FIG. 11). This may be a typical amount of puncturing for NB NR, as shown in FIG. 7.

[0062] Another problem that may arise may stem from the need to support different deployment options. For instance, a 3 MHz channel bandwidth and a maximum Tx BW of 15 RBs may be a sufficient assumption for the use cases relevant for bands of n8, n26, and n28. For these bands, there may be no motivation to consider narrower max Tx BWs than 15 RBs due to coverage drawbacks of narrower BWs. However, band nl 00 of 5.6 MHz, allocated to railway mobile radio, may need further consideration since the sub-5 MHz BW may be needed during the migration from GSM-R to FRMCS. It may be anticipated that numerous different kinds of migration scenarios may exist depending, for example, on the operation and characteristics of the related railway and GSM-R network deployments. This may suggest that a variety of BWs may be available for FRMCS.

[0063] When the available BW is between 4 MHz and 5 MHz (i.e., from 20 to 25 RBs), the NR design with, for example, 20 RB SSBs works as such. That is, the system may occupy a fraction of the 5 MHz channel BW. However, the CORESET#0 configuration may not be fully compatible with a bandwidth below 24 RBs. On the other hand, when the available BW is between 3 MHz and less than 4 MHz (i.e., from 15 to 19 RBs), the UE may assume 3 MHz / 15 RB BW for SSB acquisition. However, having the wrong assumption in PDCCH puncturing may degrade the performance further, and prevent access to the system.

[0064] Conventionally, roughly 10-14 GSM-R carriers may be needed for safe railway communications on band nlOO. 10-14 GSM-R carriers may occupy 2- 2.8 MHz, which leaves 3.6-2.8 MHz for the NR-based FRMCS, and necessary guard bands. While 15 TB BW may be narrow enough to leave sufficient space for 10 GSM-R carriers, it may be too wide to facilitate coexistence with 14 GSM-R carriers. Thus, it may be reasonable to consider an optional second narrower BW for SSB to the 15 RB Tx BW. For instance, a 12 or 13 RB BW may be considered as the optional second narrow BW, leaving a total of 640 kHz or 460 kHz for the guard bands at the nl 00 lower edge, as well as between GSM-R and NR.

[0065] According to certain example embodiments, based on the considered synchronization raster design of FIG.7, having different synchronization raster points for punctured SSB and non-punctured SSB, a punctured SSB using full transmission bandwidth (e.g., 15 entire RBs within a 15 RB channel bandwidth) means that the sub-carrier offset between the first sub-carrier of the SSB and the first sub-carrier of the RB of the common RB (CRB) grid may be zero. In other words, the LI parameter kssB may be zero. In other example embodiments, NB NR with the considered synchronization raster design may support multiple transmission bandwidths with an even and odd number of RBs. In certain example embodiments, when a transmission bandwidth (e.g., 18 RBs) is wider than the SSB BW (e.g., 15 RBs), and the number of RBs of the Tx BW has a different parity than the number of RBs of the SSB, 6 subcarrier offsets may be used between the SSB and the CRB grid. According to certain example embodiments, use of a 6 sub-carrier offset may come from the 90 kHz or % PRB offset between the channel raster and the synchronization raster. In this example embodiment, the LI parameter kssB may support values 0 and 6.

[0066] In certain example embodiments, the UE may be instructed (or may determine by itself) to make an assumption that for the additional synchronization raster points intended for the NB operation, the offset between the first sub-carrier of the SSB and the first sub-carrier of the CRB may be 0 (i.e., kssB = 0). This may be seen as a conditional re-purposing for kssB. For instance, the conditional re-purposing may correspond to a need to utilize the transmission bandwidth fully (or almost fully), reducing possible offsets or aligning the CRB and SSB grid. As described above, conditional repurposing may be based on the considered synchronization raster design. Additionally, in some example embodiments, the conditions may be that the UE is on a predefined band (e.g., nlOO), and has detected PSS/SSS on the synchronization raster used with punctured SSB. As to re-purposing, the UE may interpret kssB bits different in this case than when the SSB is detected on the legacy synchronization raster point(s). In other example embodiments, the sub-carrier offset may be 0 for Tx BWs having the same parity of RBs as the SSB, and the offset of 6 for Tx BWs with a different parity of RBs as the SSB. In other example embodiments, this may be seen as a conditional re-purposing for kssB where the parity of CORESET#0 RBs indicated by kssB also indicates the SSB sub-carrier offset (this may implicitly assume that CORESET#0 spans the entire Tx BW). In further example embodiments, a subset of bits (e.g., one bit) from kssB may be conditionally re-purposed. In this example embodiment, the CORESET#0 may not need to span the entire Tx BW. Additionally, in some example embodiments, the conditionally re-purposing of the subset of bits from the kssB may mean that at least the UE is on a predefined band (e.g., nlOO), and the UE may determine that the SSB is punctured based on, for example, the detected PSS/SSS location (either synchronization raster point or frequency location near the edge of the band), or on decoded PBCH content or detected PBCH DMRS.

[0067] According to certain example embodiments, the bits used to indicate the offset, ksBB, or a predetermined subset of the ksBB bits, may be re-purposed to carry different, additional information to facilitate the NR NB operation. For instance, the information may include, but not be limited to, at least one of: valid RBs of CORESET#0; at least one parameter indicative to size; location or structure of the CORESET#0; PBCH puncturing pattern (i.e., valid RBs of PBCH for confirmation); whether CORESET#0 resources for TypeO- PDCCH are interleaved or not; whether TypeO-PDCCH is transmitted in repetition or not; or transmission bandwidth in terms of RBs, or delta between the transmission bandwidth and the channel bandwidth. Thus, according to certain example embodiments the UE may assume, for the synchronization raster points determined for NB NR operation that the offset between the first sub-carrier of the SSB and the first sub-carrier of the CRB is 0 (or a limited set of values). Additionally, bits in the PBCH that were used to carry ksBB may be re-purposed (i.e., re-used) to carry new additional information.

[0068] FIG. 12 illustrates an example set of RBs and slot symbols of CORESET. In particular, FIG. 12 illustrates a set of RBs and slot symbols of CORESET for TypeO-PDCCH search space set when (SS/PBCH block, PDCCH) SCS is { 15, 15} kHz for frequency bands with a minimum channel bandwidth of 5 MHz or 10 MHz. As described in the example embodiments below, there may be several ways to indicate valid RBs for CORESET#0. For instance, in certain example embodiments, FIG. 12 defines the location of CORESET#0 with respect to legacy (i.e., operation according to SSB with 20 RBs) SSB. Additionally, kssB may define valid (non-punctured) RBs of CORESET#0 (a similar outcome may be achieved if kssB defines invalid (punctured) RBs of CORESET#0). In other example embodiments, kssB may indicate at least one property of CORESET#0 (while some parameters may still be derived based on FIG. 12). The at least one property may include CORESET#0 size (this may replace “Number of RBs” in FIG. 12), CORESET#0 location with respect to punctured SSB (this may replace offset (RBs) in FIG. 12), and/or Reg-to-CCE mapping correspond to interleaved vs. non- interleaved. As described below, the examples illustrated in FIGs. 13-16 may be interpreted according to the options to indicate valid RBs for CORESET#0 described above.

[0069] FIG. 13 illustrates an example relationship between k_ssb and CORESET#0, according to certain example embodiments. In this example, the relationship between k_ssb and CORESET#0 may be tabulated according to the table illustrated in FIG. 13. Specifically, in this example, CORESET#0 may be aligned with the lowest RB of the punctured SSB, and the size of the punctured SSB in this example may be 12.

[0070] FIG. 14 illustrates an example relationship between k_ssb, CORESET#0, and SSB/CORESET alignment, according to certain example embodiments. As illustrated in FIG. 14, the difference between the table in FIG. 14 and the table in FIG. 13 is that two alternative ways to align punctured SSB and CORESET#0 may be considered. For instance, in one alternative, the punctured SSB and the CORESET#0 may be aligned according to the lowest RB of the punctured SSB. Alternatively, another alternative alignment may be according to the highest RB of the punctured SSB.

[0071] FIG. 15 illustrates an example relationship between k_ssb, CORESET#0, SSB/CORESET alignment, and REG-to-CCE mapping, according to certain example embodiments. In particular, the difference between the table of FIG. 14 is that in FIG. 15, k_ssb may indicate not only the CORESET location with respect to the punctured SSB, but also the REG- to-CCE mapping for CORESET#0 (interleaved vs. non-interleaved). Further, FIG. 16 illustrates an example relationship between k_ssb, CORESET#0, SSB/CORESET alignment, REG-to-CCE mapping, and PBCH size verification, according to certain example embodiments. In particular, compared to the table of FIG. 15, k ssb in FIG. 16 may also indicate the PBCH size (verification). Here, it may be assumed that for the considered synchronization raster point, there may be two valid PBCH size options: 12 (or 13) RBs and 15 RBs. Additionally, the UE may (occasionally) succeed to decode PBCH correctly even with a wrong assumption of the PBCH size. Additionally, PBCH size verification in Fig. 16 may ensure that the UE obtains the right knowledge of the PBCH size (this information may be critical as it may be used for other scenarios, such as, for example, for determining valid RBs for CORESET#0).

[0072] FIG. 17 illustrates an example relationship between k_ssb, CORESET#0, SSB/CORESET alignment, TypeO-PDCCH repetition, and PBCH size verification, according to certain example embodiments. As illustrated in FIG. 17, the difference compared to the table of FIG. 16 is that k ssb may indicate whether TypeO-PDCCH is transmitted in repetition or not (instead of indicating REG-to-CCE mapping). In certain example embodiments, when TypeO-PDCCH is transmitted in repetition, the same TypeO-PDCCH may be repeated in consecutive TypeO-PDCCH occasions. According to certain example embodiments, the repetition pattern may be predetermined and bound to the slot index, and the repetition may be limited to certain PDCCH candidates (e.g., having AL8).

[0073] FIG. 18 illustrates an example relationship between k_ssb, CORESET#0, SSB/CORESET alignment, SSB sub-carrier offset, and PBCH size verification, according to certain example embodiments. As illustrated in FIG. 18, CORESET#0 may span the entire Tx BW. In certain example embodiments, it may be assumed that for the considered synchronization raster point, there may be two valid PBCH (or SSB) size options such as, for example, 13 RBs and 15 RBs.

[0074] FIG. 19 illustrates an example relationship between k_ssb bits, a number of RBs for CORESET#0, and SSB/CORESET alignment, according to certain example embodiments. In particular, FIG. 19 illustrates an example with 20 RB SSBs. Further, FIG. 20 illustrates an example relationship between k ssb, SSB sub-carrier offset, number of RBs for CORESET#0, and PBCH size verification, according to certain example embodiments. According to the legacy /Rel 15, the NR synchronization raster may be used for NB NR operation. For example, the NR synchronization raster may be used with 4.4 MHz Tx BW implying 22 RB CORESET#0. Alternatively, the NR synchronization raster may be used for NB NR operation considering 100 kHz synchronization raster is not adopted, but Rel 15 NR synchronization raster or a variant of that is used. In such a case, certain example embodiments may assume that the set of SSB sub-carrier offsets that may be indicated with k_ssb may be reduced. For example, as illustrated in FIGs. 19 and 20, k_ssb may be reduced to 4, 6, 8 sub-carriers (requiring 2 bits), or to 2, 4, 6, 8, 10 sub-carriers. Additionally, in such cases, some of the k_ssb bits or signaling states may be re-purposed for indicating CORESET#0 related information. Alternatively, in such cases, k_ssb bits may be re-purposed for indicating jointly CORESET#0 related information as well as SSB sub-carrier offsets. Although FIGs. 12-19 illustrate some example embodiments, in other example embodiments, different modifications may be possible. For instance, in some example embodiments, it may be possible to combine entries from two or more tables (e.g., to create a new table). Furthermore, in other example embodiments, it may be possible to use a subset of an existing table to create a new table. Additionally, in further example embodiments, it may be possible to use k ssb (and the principle of conditional repurposing) to indicate additional properties for CORESET#0, TypeO PDCCH, or other use cases.

[0075] FIG. 21 illustrates an example flow diagram of a method, according to certain example embodiments. In an example embodiment, the method of FIG. 21 may be performed by a network entity, or a group of multiple network elements in a 3GPP system, such as LTE or 5G-NR. For instance, in an example embodiment, the method of FIG. 21 may be performed by a UE similar to one of apparatuses 10 or 20 illustrated in FIG. 22.

[0076] According to certain example embodiments, the method of FIG. 21 may include, at 100, detecting a synchronization signal on a synchronization raster point on a band of interest. The method may also include, at 105, determining a puncturing assumption pattern associated with the synchronization signal for a communication channel based on bits of a radio parameter. The method may further include, at 110, demodulating and decoding the communication channel based on the puncturing assumption associated with the synchronization raster point.

[0077] According to certain example embodiments, the method may further include determining, in response to detecting the synchronization signal, whether the synchronization raster point is associated with a narrowband new radio operation. In some example embodiments, the synchronization raster frequency locations may be determined by specification, and may be unambiguously associated with one or more frequency bands. Thus, when the UE carries the search, the UE may search certain synchronization raster points associated with certain band(s) (e.g., intended for NB NR operation). According to some example embodiments, the bits of the radio parameter may indicate a synchronization signal sub-carrier offset and information facilitating the narrowband new radio operation. According to other example embodiments, the method may also include re-purposing a portion of the bits of the radio parameter to carry information facilitating the narrowband new radio operation. In certain example embodiments, a first subset of bits from the bits of the radio parameter may be reserved for indicating a synchronization signal block sub-carrier offset. In other example embodiments, a second subset of bits from the bits of the radio parameter may be conditionally re-purposed.

[0078] In certain example embodiments, the information may include at least one of valid resource blocks of a control resource set, at least one parameter indicative of a size, a location, or a structure of the control resource set, a physical broadcast channel puncturing pattern, whether resources of the control resource set for a physical downlink control channel are interleaved, whether the physical downlink control channel is transmitted in repetition, or a transmission bandwidth in terms of resource blocks, or in terms of a change between the transmission bandwidth and a channel bandwidth. In other example embodiments, a narrowband new radio associated with the synchronization raster point may support a plurality of transmission bandwidths comprising an even and an odd number of resource blocks. In some example embodiments, the method may further include performing a conditional re-purposing for the bits of the radio parameter. According to certain example embodiments, performing the conditional re-purposing for the bits of the radio parameter may include making an assumption that for additional synchronization raster points intended for the narrowband new radio operation, an offset between a first sub-carrier of a synchronization signal block and a first sub-carrier of a common resource block is zero.

[0079] FIG. 22 illustrates a set of apparatuses 10 and 20 according to certain example embodiments. In certain example embodiments, the apparatus 10 may be an element in a communications network or associated with such a network, such as a UE, mobile equipment (ME), mobile station, mobile device, stationary device, loT device, a mounted mobile device, or other similar device. It should be noted that one of ordinary skill in the art would understand that apparatus 10 may include components or features not shown in FIG. 22.

[0080] In some example embodiments, apparatus 10 may include one or more processors, one or more computer-readable storage medium (for example, memory, storage, or the like), one or more radio access components (for example, a modem, a transceiver, or the like), and/or a user interface. In some example embodiments, apparatus 10 may be configured to operate using one or more radio access technologies, such as GSM, LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-IoT, Bluetooth, NFC, MulteFire, and/or any other radio access technologies. It should be noted that one of ordinary skill in the art would understand that apparatus 10 may include components or features not shown in FIG. 22.

[0081] As illustrated in the example of FIG. 22, apparatus 10 may include or be coupled to a processor 12 for processing information and executing instructions or operations. Processor 12 may be any type of general or specific purpose processor. In fact, processor 12 may include one or more of general- purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, as examples. While a single processor 12 is shown in FIG. 22, multiple processors may be utilized according to other example embodiments. For example, it should be understood that, in certain example embodiments, apparatus 10 may include two or more processors that may form a multiprocessor system (e.g., in this case processor 12 may represent a multiprocessor) that may support multiprocessing. According to certain example embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0082] Processor 12 may perform functions associated with the operation of apparatus 10 including, as some examples, precoding of antenna gain/phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatus 10, including processes and examples illustrated in FIGs. 1-21.

[0083] Apparatus 10 may further include or be coupled to a memory 14 (internal or external), which may be coupled to processor 12, for storing information and instructions that may be executed by processor 12. Memory 14 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and/or removable memory. For example, memory 14 can be comprised of any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, hard disk drive (HDD), or any other type of non-transitory machine or computer readable media. The instructions stored in memory 14 may include program instructions or computer program code that, when executed by processor 12, enable the apparatus 10 to perform tasks as described herein.

[0084] In certain example embodiments, apparatus 10 may further include or be coupled to (internal or external) a drive or port that is configured to accept and read an external computer readable storage medium, such as an optical disc, USB drive, flash drive, or any other storage medium. For example, the external computer readable storage medium may store a computer program or software for execution by processor 12 and/or apparatus 10 to perform any of the methods and examples illustrated in FIGs. 1-21.

[0085] In some example embodiments, apparatus 10 may also include or be coupled to one or more antennas 15 for receiving a downlink signal and for transmitting via an UL from apparatus 10. Apparatus 10 may further include a transceiver 18 configured to transmit and receive information. The transceiver 18 may also include a radio interface (e.g., a modem) coupled to the antenna 15. The radio interface may correspond to a plurality of radio access technologies including one or more of GSM, LTE, LTE-A, 5G, NR, WLAN, NB-IoT, Bluetooth, BT-LE, NFC, RFID, UWB, and the like. The radio interface may include other components, such as filters, converters (for example, digital-to-analog converters and the like), symbol demappers, signal shaping components, an Inverse Fast Fourier Transform (IFFT) module, and the like, to process symbols, such as OFDMA symbols, carried by a downlink or an UL.

[0086] For instance, transceiver 18 may be configured to modulate information on to a carrier waveform for transmission by the antenna(s) 15 and demodulate information received via the antenna(s) 15 for further processing by other elements of apparatus 10. In other example embodiments, transceiver 18 may be capable of transmitting and receiving signals or data directly. Additionally or alternatively, in some example embodiments, apparatus 10 may include an input and/or output device (I/O device). In certain example embodiments, apparatus 10 may further include a user interface, such as a graphical user interface or touchscreen.

[0087] In certain example embodiments, memory 14 stores software modules that provide functionality when executed by processor 12. The modules may include, for example, an operating system that provides operating system functionality for apparatus 10. The memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatus 10. The components of apparatus 10 may be implemented in hardware, or as any suitable combination of hardware and software. According to certain example embodiments, apparatus 10 may optionally be configured to communicate with apparatus 20 via a wireless or wired communications link 70 according to any radio access technology, such as NR.

[0088] According to certain example embodiments, processor 12 and memory 14 may be included in or may form a part of processing circuitry or control circuitry. In addition, in some example embodiments, transceiver 18 may be included in or may form a part of transceiving circuitry.

[0089] For instance, in certain example embodiments, apparatus 10 may be controlled by memory 14 and processor 12 to detect a synchronization signal on a synchronization raster point on a band of interest. Apparatus 10 may also be controlled by memory 14 and processor 12 to determine a puncturing assumption pattern associated with the synchronization signal for a communication channel based on bits of a radio parameter. Apparatus 10 may further be controlled by memory 14 and processor 12 to demodulate and decode the communication channel based on the puncturing assumption associated with the synchronization raster point.

[0090] As illustrated in the example of FIG. 22, apparatus 20 may be a network, core network element, or element in a communications network or associated with such a network, such as a gNB, NW, base station (BS), access point (AP), or similar device. It should be noted that one of ordinary skill in the art would understand that apparatus 20 may include components or features not shown in FIG. 22.

[0091] As illustrated in the example of FIG. 22, apparatus 20 may include a processor 22 for processing information and executing instructions or operations. Processor 22 may be any type of general or specific purpose processor. For example, processor 22 may include one or more of general- purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, as examples. While a single processor 22 is shown in FIG. 22, multiple processors may be utilized according to other example embodiments. For example, it should be understood that, in certain example embodiments, apparatus 20 may include two or more processors that may form a multiprocessor system (e.g., in this case processor 22 may represent a multiprocessor) that may support multiprocessing. In certain example embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0092] According to certain example embodiments, processor 22 may perform functions associated with the operation of apparatus 20, which may include, for example, precoding of antenna gain/phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatus 20, including processes and examples illustrated in FIGs. 1-20.

[0093] Apparatus 20 may further include or be coupled to a memory 24 (internal or external), which may be coupled to processor 22, for storing information and instructions that may be executed by processor 22. Memory 24 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and/or removable memory. For example, memory 24 can be comprised of any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, hard disk drive (HDD), or any other type of non-transitory machine or computer readable media. The instructions stored in memory 24 may include program instructions or computer program code that, when executed by processor 22, enable the apparatus 20 to perform tasks as described herein.

[0094] In certain example embodiments, apparatus 20 may further include or be coupled to (internal or external) a drive or port that is configured to accept and read an external computer readable storage medium, such as an optical disc, USB drive, flash drive, or any other storage medium. For example, the external computer readable storage medium may store a computer program or software for execution by processor 22 and/or apparatus 20 to perform the methods and examples illustrated in FIGs. 1-20.

[0095] In certain example embodiments, apparatus 20 may also include or be coupled to one or more antennas 25 for transmitting and receiving signals and/or data to and from apparatus 20. Apparatus 20 may further include or be coupled to a transceiver 28 configured to transmit and receive information. The transceiver 28 may include, for example, a plurality of radio interfaces that may be coupled to the antenna(s) 25. The radio interfaces may correspond to a plurality of radio access technologies including one or more of GSM, NB- loT, LTE, 5G, WLAN, Bluetooth, BT-LE, NFC, radio frequency identifier (RFID), ultrawideband (UWB), MulteFire, and the like. The radio interface may include components, such as filters, converters (for example, digital-to- analog converters and the like), mappers, a Fast Fourier Transform (FFT) module, and the like, to generate symbols for a transmission via one or more downlinks and to receive symbols (for example, via an UL).

[0096] As such, transceiver 28 may be configured to modulate information on to a carrier waveform for transmission by the antenna(s) 25 and demodulate information received via the antenna(s) 25 for further processing by other elements of apparatus 20. In other example embodiments, transceiver 18 may be capable of transmitting and receiving signals or data directly. Additionally or alternatively, in some example embodiments, apparatus 20 may include an input and/or output device (I/O device).

[0097] In certain example embodiment, memory 24 may store software modules that provide functionality when executed by processor 22. The modules may include, for example, an operating system that provides operating system functionality for apparatus 20. The memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatus 20. The components of apparatus 20 may be implemented in hardware, or as any suitable combination of hardware and software.

[0098] According to some example embodiments, processor 22 and memory 24 may be included in or may form a part of processing circuitry or control circuitry. In addition, in some example embodiments, transceiver 28 may be included in or may form a part of transceiving circuitry.

[0099] As used herein, the term “circuitry” may refer to hardware-only circuitry implementations (e.g., analog and/or digital circuitry), combinations of hardware circuits and software, combinations of analog and/or digital hardware circuits with software/firmware, any portions of hardware processor(s) with software (including digital signal processors) that work together to cause an apparatus (e.g., apparatus 10 and 20) to perform various functions, and/or hardware circuit(s) and/or processor(s), or portions thereof, that use software for operation but where the software may not be present when it is not needed for operation. As a further example, as used herein, the term “circuitry” may also cover an implementation of merely a hardware circuit or processor (or multiple processors), or portion of a hardware circuit or processor, and its accompanying software and/or firmware. The term circuitry may also cover, for example, a baseband integrated circuit in a server, cellular network node or device, or other computing or network device.

[0100] In some example embodiments, an apparatus (e.g., apparatus 10 and/or apparatus 20) may include means for performing a method, a process, or any of the variants discussed herein. Examples of the means may include one or more processors, memory, controllers, transmitters, receivers, and/or computer program code for causing the performance of the operations.

[0101] Certain example embodiments may be directed to an apparatus that includes means for performing any of the methods described herein including, for example, means for detecting a synchronization signal on a synchronization raster point on a band of interest. The apparatus may also include means for determining a puncturing assumption pattern associated with the synchronization signal for a communication channel based on bits of a radio parameter. The apparatus may further include means for demodulating and decoding the communication channel based on the puncturing assumption associated with the synchronization raster point.

[0102] Certain example embodiments described herein provide several technical improvements, enhancements, and /or advantages. For instance, in some example embodiments, it may be possible for the UE to unambiguously determine the puncturing pattern assumed for the PDCCH (e.g., on CORESET#0), and PBCH as well, when monitored after or during (e.g., PDCCH monitoring for SIB1 scheduling) initial access. Additionally, the UE may also be able to perform optimal demodulation and decoding. In other example embodiments it may be possible to enable having different puncturing assumptions on SSB and PDCCH (CORESET#0). In further example embodiments, it may be possible to achieve better performance to PDCCH (CORESET#0) detection via correct puncturing assumption for different bandwidth options for different deployments. Additionally, it may be possible for the UE to avoid hardware changes.

[0103] A computer program product may include one or more computerexecutable components which, when the program is run, are configured to carry out some example embodiments. The one or more computer-executable components may be at least one software code or portions of it. Modifications and configurations required for implementing functionality of certain example embodiments may be performed as routine(s), which may be implemented as added or updated software routine(s). Software routine(s) may be downloaded into the apparatus.

[0104] As an example, software or a computer program code or portions of it may be in a source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program. Such carriers may include a record medium, computer memory, read-only memory, photoelectrical and/or electrical carrier signal, telecommunications signal, and software distribution package, for example. Depending on the processing power needed, the computer program may be executed in a single electronic digital computer or it may be distributed amongst a number of computers. The computer readable medium or computer readable storage medium may be a non-transitory medium.

[0105] In other example embodiments, the functionality may be performed by hardware or circuitry included in an apparatus (e.g., apparatus 10 or apparatus 20), for example through the use of an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array (FPGA), or any other combination of hardware and software. In yet another example embodiment, the functionality may be implemented as a signal, a non-tangible means that can be carried by an electromagnetic signal downloaded from the Internet or other network.

[0106] According to certain example embodiments, an apparatus, such as a node, device, or a corresponding component, may be configured as circuitry, a computer or a microprocessor, such as single-chip computer element, or as a chipset, including at least a memory for providing storage capacity used for arithmetic operation and an operation processor for executing the arithmetic operation.

[0107] One having ordinary skill in the art will readily understand that the disclosure as discussed above may be practiced with procedures in a different order, and/or with hardware elements in configurations which are different than those which are disclosed. Therefore, although the disclosure has been described based upon these example embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of example embodiments. Although the above embodiments refer to 5G NR and LTE technology, the above embodiments may also apply to any other present or future 3 GPP technology, such as LTE-advanced, and/or fourth generation (4G) technology.

[0108] Partial Glossary:

[0109] 3GPP 3rd Generation Partnership Project

[0110] 5G 5th Generation

[0111] 5GCN 5G Core Network

[0112] 5GS 5G System

[0113] BS Base Station

[0114] CBW Channel Bandwidth

[0115] DCI Downlink Control Information

[0116] DL Downlink

[0117] DMRS Demodulation Reference Signal

[0118] eNB Enhanced Node B [0119] E-UTRAN Evolved UTRAN

[0120] gNB 5G or Next Generation NodeB

[0121] LTE Long Term Evolution

[0122] MIB Master Information Block

[0123] NB Narrowband

[0124] NR New Radio

[0125] NW Network

[0126] OFDM Orthogonal Frequency Domain Multilexing

[0127] PBCH Physical Broadcast channel

[0128] PRB Physical Resource Block

[0129] PSS Primary Synchronization Signal

[0130] RE Resource element

[0131] RB Resource Block

[0132] RRC Radio Resource Control

[0133] SCS Subcarrier Spacing

[0134] SIB System Information Block

[0135] SSB Synchronization Signal Block

[0136] SSS Secondary Synchronization Signal

[0137] UE User Equipment

[0138] UL Uplink

Claims

WE CLAIM:

1. A method comprising: detecting a synchronization signal on a synchronization raster point on a band of interest; determining a puncturing assumption pattern associated with the synchronization signal for a communication channel based on bits of a radio parameter; and demodulating and decoding the communication channel based on the puncturing assumption associated with the synchronization raster point.

2. The method according to claim 1 , further comprising: determining, in response to detecting the synchronization signal, whether the synchronization raster point is associated with a narrowband new radio operation.

3. The method according to claim 1 or 2, wherein the bits of the radio parameter indicate a synchronization signal sub-carrier offset and information facilitating the narrowband new radio operation.

4. The method according to any of claims 1-3, further comprising: re-purposing a portion of the bits of the radio parameter to carry information facilitating the narrowband new radio operation, wherein a first subset of bits from the bits of the radio parameter is reserved for indicating a synchronization signal block sub-carrier offset, and wherein a second subset of bits from the bits of the radio parameter are conditionally re-purposed.

5. The method according to claim 3 or 4, wherein the information comprises at least one of the following: valid resource blocks of a control resource set, at least one parameter indicative of a size, a location, or a structure of the control resource set, a physical broadcast channel puncturing pattern, whether resources of the control resource set for a physical downlink control channel are interleaved, whether the physical downlink control channel is transmitted in repetition, or a transmission bandwidth in terms of resource blocks, or in terms of a change between the transmission bandwidth and a channel bandwidth.

6. The method according to any of claims 1 -5, wherein a narrowband new radio associated with the synchronization raster point supports a plurality of transmission bandwidths comprising an even and an odd number of resource blocks.

7. The method according to any of claims 1-6, further comprising: performing a conditional re-purposing for the bits of the radio parameter, wherein performing the conditional re-purposing for the bits of the radio parameter comprises making an assumption that for additional synchronization raster points intended for the narrowband new radio operation, an offset between a first sub-carrier of a synchronization signal block and a first sub-carrier of a common resource block is zero.

8. An apparatus, comprising: at least one processor; and at least one memory comprising computer program code, the at least one memory and the computer program code configured to, with storing instructions that, when executed by the at least one processor, cause the apparatus at least to: detect a synchronization signal on a synchronization raster point on a band of interest; determine a puncturing assumption pattern associated with the synchronization signal for a communication channel based on bits of a radio parameter; and demodulate and decode the communication channel based on the puncturing assumption associated with the synchronization raster point.

9. The apparatus according to claim 8, wherein the at least one memory and the computer program code are further configured to, with storing instructions that, when executed by the at least one processor, cause the apparatus at least to: determine, in response to detecting the synchronization signal, whether the synchronization raster point is associated with a narrowband new radio operation.

10. The apparatus according to claim 8 or 9, wherein the bits of the radio parameter indicate a synchronization signal sub-carrier offset and information facilitating the narrowband new radio operation.

11. The apparatus according to any of claims 8-10, wherein the at least one memory and the computer program code are further configured to, with storing instructions that, when executed by the at least one processor, cause the apparatus at least to: re-purpose a portion of the bits of the radio parameter to carry information facilitating the narrowband new radio operation, wherein a first subset of bits from the bits of the radio parameter is reserved for indicating a synchronization signal block sub-carrier offset, and wherein a second subset of bits from the bits of the radio parameter are conditionally re-purposed.

12. The apparatus according to claim 11, wherein the information comprises at least one of the following: valid resource blocks of a control resource set, at least one parameter indicative of a size, a location, or a structure of the control resource set, a physical broadcast channel puncturing pattern, whether resources of the control resource set for a physical downlink control channel are interleaved, whether the physical downlink control channel is transmitted in repetition, or a transmission bandwidth in terms of resource blocks, or in terms of a change between the transmission bandwidth and a channel bandwidth.

13. The apparatus according to any of claims 8-12, wherein a narrowband new radio associated with the synchronization raster point supports a plurality of transmission bandwidths comprising an even and an odd number of resource blocks.

14. The apparatus according to any of claims 8-13, wherein the at least one memory and the computer program code are further configured to, with storing instructions that, when executed by the at least one processor, cause the apparatus at least to: perform a conditional re-purposing for the bits of the radio parameter, wherein performance of the conditional re-purposing for the bits of the radio parameter comprises making an assumption that for additional synchronization raster points intended for the narrowband new radio operation, an offset between a first sub-carrier of a synchronization signal block and a first sub-carrier of a common resource block is zero.

15. An apparatus, comprising : means for detecting a synchronization signal on a synchronization raster point on a band of interest; means for determining a puncturing assumption pattern associated with the synchronization signal for a communication channel based on bits of a radio parameter; and means for demodulating and decoding the communication channel based on the puncturing assumption associated with the synchronization raster point.

16. The apparatus according to claim 15, further comprising: means for determining, in response to detecting the synchronization signal, whether the synchronization raster point is associated with a narrowband new radio operation.

17. The apparatus according to claim 15 or 16, wherein the bits of the radio parameter indicate a synchronization signal sub-carrier offset and information facilitating the narrowband new radio operation.

18. The apparatus according to any of claims 15-17, further comprising: means for re-purposing a portion of the bits of the radio parameter to carry information facilitating the narrowband new radio operation, wherein a first subset of bits from the bits of the radio parameter is reserved for indicating a synchronization signal block sub-carrier offset, and wherein a second subset of bits from the bits of the radio parameter are conditionally re-purposed.

19. The apparatus according to claim 18, wherein the information comprises at least one of the following: valid resource blocks of a control resource set, at least one parameter indicative of a size, a location, or a structure of the control resource set, a physical broadcast channel puncturing pattern, whether resources of the control resource set for a physical downlink control channel are interleaved, whether the physical downlink control channel is transmitted in repetition, or a transmission bandwidth in terms of resource blocks, or in terms of a change between the transmission bandwidth and a channel bandwidth.

20. The apparatus according to any of claims 15-19, wherein a narrowband new radio associated with the synchronization raster point supports a plurality of transmission bandwidths comprising an even and an odd number of resource blocks.

21. The apparatus according to any of claims 15-20, further comprising: means for performing a conditional re-purposing for the bits of the radio parameter, wherein performing the conditional re-purposing for the bits of the radio parameter comprises making an assumption that for additional synchronization raster points intended for the narrowband new radio operation, an offset between a first sub-carrier of a synchronization signal block and a first sub-carrier of a common resource block is zero.

22. A non- transitory computer readable medium comprising program instructions stored thereon for performing the method according to any of claims 1-7.

23. An apparatus comprising circuitry configured to cause the apparatus to perform a process according to any of claims 1-7.