Puncture assumptions for control channels in narrowband new radio operation.

Abstract

A system, method, apparatus, and computer program product for dynamically changing gap priorities may include detecting a synchronization signal at a synchronization raster point on a band of interest. The method may also include determining a puncture 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 puncture assumption associated with the synchronization raster point.

Description

[Technical Field]

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

[0002] Examples of mobile or wireless telecommunications systems may include Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), LTE Evolved UTRAN (E-UTRAN), LTE Advanced (LTE-A), MultiFire, 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 architectures. 5G network technology is primarily based on New Radio (NR) technology, but 5G (or NG) networks can also be built on E-UTRAN radios. NR can provide bit rates of approximately 10 to 20 Gbit / s or more and is estimated to be able to support at least enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC). NR is expected to provide extreme broadband and ultra-robust, low-latency connectivity and massive networking to support IoT. Summary of the Invention

[0003] Some example embodiments may be directed to a method. The method may include detecting a synchronization signal at a synchronization raster point on a band of interest. The method may also include determining a puncture assumption pattern associated with the synchronization signal for a communication channel based on bits of the radio parameters. The method may further include demodulating and decoding the communication channel based on the puncture assumption associated with the synchronization raster point.

[0004] Another example embodiment may be directed to an apparatus. The apparatus may include at least one processor and at least one memory containing computer program code. The at least one memory and the computer program code may also be configured, with the at least one processor, to cause the apparatus to at least detect a synchronization signal at a synchronization raster point on a band of interest. The apparatus may also be caused to determine a puncture assumption pattern associated with the synchronization signal for the communication channel based on bits of the radio parameters. The apparatus may further be caused to demodulate and decode the communication channel based on the puncture assumption associated with the synchronization raster point.

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

[0006] According to another example embodiment, a non-transitory computer-readable medium may be encoded with instructions that, when executed in hardware, may implement a method. The method may include detecting a synchronization signal at a synchronization raster point on a band of interest. The method may also include determining a puncture assumption pattern associated with the synchronization signal for the communication channel based on bits of the radio parameters. The method may further include demodulating and decoding the communication channel based on the puncture assumption associated with the synchronization raster point.

[0007] Another example embodiment may be directed to a computer program product embodying a method. The method may include detecting a synchronization signal at a synchronization raster point on a band of interest. The method may also include determining a puncture assumption pattern associated with the synchronization signal for the communication channel based on bits of the radio parameters. The method may further include demodulating and decoding the communication channel based on the puncture assumption associated with the synchronization raster point.

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

[0009] For a proper understanding of the example embodiments, reference should be made to the accompanying drawings. [Brief explanation of the drawings]

[0010] [Figure 1A] FIG. 1 is a diagram of an example deployment scenario. [Figure 1B] FIG. 1 is a diagram of an example deployment scenario. [Figure 2] FIG. 1 is a diagram of an example of an existing NR initial access signal and channel with 15 kHz subcarrier spacing. [Figure 3] 1 is a diagram of an example of different puncture patterns for a synchronization signal block (SSB). [Figure 4A] FIG. 10 is a diagram of an example control resource set (CORESET) #0 resource allocation signaling. [Figure 4B] FIG. 10 is a diagram of an example control resource set (CORESET) #0 resource allocation signaling. [Figure 5] FIG. 1 is a diagram of a summary of a set of predefined parameters. [Figure 6] A diagram of the principle of an example of synchronization raster points in the frequency range of 0 to 3000 MHz. [Figure 7] FIG. 10 is a diagram of an example synchronous raster consideration for a 3 MHz bandwidth. [Figure 8] FIG. 10 is a table of valid synchronous raster points for n100 based on a synchronous raster design. [Figure 9] FIG. 10 is a diagram of an example of synchronization raster points for punctured and non-punctured SSB in a band of interest. [Figure 10] FIG. 2 is a diagram of an example of control channel element (CCE) indexes. [Figure 11] FIG. 10 illustrates example performance degradation due to puncturing. [Figure 12] 1 is a diagram of a set of resource blocks and slot symbols for CORESET, in accordance with a particular example embodiment. [Figure 13] FIG. 10 is a diagram of an example relationship between k_ssb and CORESET#0, in accordance with a particular example embodiment. [Figure 14] FIG. 10 is a diagram of an example relationship between k_ssb, CORESET#0, and SSB / CORESET alignment, in accordance with a particular example embodiment. [Figure 15] FIG. 10 is a diagram of example relationships between k_ssb, CORESET#0, SSB / CORESET alignment, and resource element group-to-control channel element (REG-to-CCE) mapping, in accordance with a particular example embodiment. [Figure 16] FIG. 10 is a diagram of an example relationship between k_ssb, CORESET#0, SSB / CORESET alignment, REG to CCE mapping, and PBCH size verification, in accordance with a particular example embodiment. [Figure 17] FIG. 10 is a diagram of an example relationship between k_ssb, CORESET#0, SSB / CORESET alignment, Type 0—physical downlink control channel (PDCCH) repetition, and physical broadcast channel (PBCH) size verification, in accordance with a particular example embodiment. [Figure 18] FIG. 10 is a diagram of an example relationship between k_ssb, CORESET#0, SSB / CORESET alignment, SSB subcarrier offset, and PBCH size verification, in accordance with a particular example embodiment. [Figure 19] 10 is a diagram of an example relationship between k_ssb bits, the number of RBs for CORESET#0, and SSB / CORESET alignment, in accordance with a particular example embodiment. FIG. [Figure 20] FIG. 10 is a diagram of an example relationship between k_ssb, SSB subcarrier offset, number of RBs for CORESET#0, and PBCH size verification, in accordance with a particular example embodiment. [Figure 21] 10 is an example flow diagram of another method in accordance with certain example embodiments. [Figure 22] FIG. 1 is a diagram of a set of devices in accordance with certain example embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0011] It will be readily understood that the components of particular example embodiments, as generally described and illustrated in the Figures herein, may be arranged and designed in a wide variety of different configurations. Following are detailed descriptions of some example embodiments of systems, methods, apparatuses, and computer program products for puncturing assumptions for control channels in NB NR operation. For example, a particular example embodiment may be directed to determining a puncturing assumption for a control channel based on k_ssb NB NR operation.

[0012] 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 use of the phrase “particular embodiment,” “example embodiment,” “some embodiments,” or other similar language indicates that a particular feature, structure, or characteristic described with respect to an embodiment throughout this specification may be included in at least one embodiment. Thus, the appearance of the phrase “particular embodiment,” “example embodiment,” “some embodiments,” “other embodiments,” or other similar language does not necessarily refer to the same group of embodiments throughout this specification, and the described features, structures, or characteristics may be combined in any suitable manner in one or more example embodiments. Furthermore, the terms “cell,” “node,” “gNB,” “network,” or other similar language may be used interchangeably throughout this specification.

[0013] As used herein, "at least one of: " and "at least one of " and similar language, when a list of two or more elements is joined by "and" or "or", means at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0014] The specific example embodiments described herein are directed to NB NR, or may otherwise be known as NR support for dedicated spectrum below 5 MHz. NB NR is a merge scenario driven not only by some smart grid operators but also by future rail communication needs. There may also be additional usage scenarios in the future related to rail communication needs (e.g., machine-type communications, or specialized bandwidth scenarios for smartphones).

[0015] There may be specific considerations for the future railway mobile communication system (FRMCS), including, for example, agreement on the use of NR, 2 x 5.6 MHz frequency division duplex (FDD) (874.4-880 MHz / 919.4-925 MHz), a soft transition from the Global System for Mobile Communications - Railway (GSM-R) requiring simultaneous operation of GSM-R and NR, and it can be assumed that in some scenarios NR may be allocated in 3 MHz channels.

[0016] Potential deployment scenarios for NR downlink (DL) / uplink (UL) and GSM-R DL / UL may include adjacent channel deployment, overlay deployment with compact GSM-R channel placement, overlay deployment with GSM-R channels distributed across the 4 MHz core band, and overlay deployment with GSM-R channels distributed across the full extended railway GSM (ER-GSM) band. Adjacent channel deployment of NR and GSM-R may have the advantage of easier implementation for the NR scheduler and a single boundary between NR and GSM-R, leading to simpler and more predictable coexistence.

[0017] Narrowband NR has also been considered for the "smart grid" in the US, including 2x3 MHz FDD in 900 MHz, and for public safety applications in Europe, including 2x3 MHz FDD in Band 28 for public protection and disaster relief (PPDR).

[0018] NR Rel-15 through Rel-17 currently do not support channel bandwidths less than 5 MHz. It has been proposed to adapt NR to the 3-5 MHz spectrum allocation with minimal changes, building on the existing NR ecosystem. Additionally, it has been identified that there are emerging scenarios where it may be beneficial to enable 5G NR operation in narrower bandwidths than the 5 MHz channels for which 5G NR was originally designed. For example, downsizing to 3 MHz and deployment of NR in the 900 MHz FRMCS band is intended to operate with any legacy GSM-R carrier within a 5.6 MHz bandwidth, allowing approximately 3.6 MHz bandwidth to be used for NR. Similarly, there may be some cases where 3 MHz channels are available for NR.

[0019] FIG. 1 illustrates an example deployment scenario. In particular, FIG. 1 illustrates a co-deployment option for NR and GSM-R within the 5.6 MHz DL (left) and UL (right). As illustrated in FIG. 1, adjacent channel deployment of NR and GSM-R may be preferred. Doing so may result in easier implementation for the NR scheduler. Additionally, there may be a boundary between NR and GSM-R that may result in simpler and more predictable coexistence. Furthermore, NB-NR may be connected for smart grid applications, including, for example, 2×3 MHz FDD 900 MHz in the United States. NB-NR may also be considered for public safety applications, including, for example, 2×3 MHz FDD in band 28 for public protection and disaster relief (PPDR). Unlike reduced capability (RedCap) user equipment (UE), the target market does not have significant constraints on device size, complexity, number of antennas, and power consumption. Therefore, optimization of these characteristics may be excessive. NR does not support CBW < 5 MHz, and a general target could be to fit NR into roughly a 3-5 MHz spectrum allocation with minimal changes, thereby building on the existing NR ecosystem.

[0020] Figure 2 illustrates an example of an existing NR initial access signal and channel with 15 kHz subcarrier spacing. In some scenarios, it may be beneficial to enable 5G NR operation in a narrower bandwidth (e.g., down to approximately 3 MHz) than the 5 MHz channel for which 5G NR was originally designed. For example, NR deployment in the 900 MHz FRMCS band may need to occur with legacy GSM-R carriers within the 5.6 MHz bandwidth, allowing approximately 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.

[0021] Essential signals and channels transmitted by NR base stations (gNBs), more particularly synchronization signals and physical broadcast channel (PBCH) block (SSB) signals and channels, are not designed for transmission over such narrow channels.

[0022] After detecting the primary synchronization signal (PSS) and secondary synchronization signal (SSS), the UE may know the slot timing within the 5 ms half-frame and symbol timing, as well as the physical cell ID. The UE can then determine the resource elements for the PBCH demodulation reference signal (DMRS) and data for receiving the PBCH payload. The PBCH can carry master information block (MIB) signaling, which may pertain to frequency location (SSB frequency domain allocation relative to the common resource block (CRB) grid) and timing (half-frame timing and frame timing). Information may be included in the higher layer payload (i.e., MIB), either in the transport block payload or as part of the physical layer bits in the DMRS.

[0023] Figure 3 illustrates examples of different puncture patterns for SSB. A 3 MHz allocation to an NR system may imply a maximum of 15 physical resource block (PRB) channel bandwidth, assuming 90% spectrum utilization. For SSB, this may imply 5 PRB punctures. Since the PSS / SSS may remain unaffected, a maximum of 4 PRB punctures per side may be performed. In other words, applicable puncture patterns may include 1+4, 2+3, 3+2, and 4+1, as illustrated in Figure 3.

[0024] Puncturing a transmit signal can be used to narrow the transmission bandwidth with minimal changes. For example, in a puncturing operation, the base station ignores any signals mapped to specific predefined PRBs that are outside the desired transmission bandwidth. In this way, the base station does not transmit these signals. When a UE receives a transmission with punctured PRBs, the UE can disable the punctured PRBs at the receiver. The UE can also disable the punctured PRBs, for example, by setting the log-likelihood ratio (LLR) to zero in the channel decoder.

[0025] An alternative to puncturing may include rate matching, in which input bits are matched to available resources, so that the sequence of rate-matched bits may vary depending on the resource size. With rate matching, the receiver must know the resource size in order to correctly decode the packet.

[0026] Puncturing may also refer to a situation where at least a part of the signal generation process (e.g., encoding and rate matching) is performed according to a particular resource allocation, but a portion of the generated signal is not transmitted. The excluded signal portion may be mapped onto punctured frequency-domain resources (e.g., subcarriers or resource blocks). Puncturing may be performed at a predefined resolution, for example, resource block (RB) resolution or control channel element (CCE) resolution. The resolution may vary from scenario to scenario.

[0027] Figure 4 illustrates example control resource set (CORESET) #0 resource allocation signaling. CORESET may be defined as the set of physical resources and parameters used to carry PDCCH / downlink control information (DCI). It is conceptually equivalent in function to the LTE PDCCH area (the first 1, 2, 3, or 4 OFDM symbols in a subframe). In the LTE PDCCH area, the PDCCH is spread across the entire channel bandwidth, while the NR CORESET area is localized to a specific region in the frequency domain. For CORESET,

number

number

number

[0028] In the CORESET#0 allocation determination by the UE, after the UE detects the PSS and SSS and demodulates the PBCH, the UE can read a configuration index from the PBCH / MIB. The configuration index may refer to the CORESET#0 configuration table and, more specifically, to specific time and frequency resource allocation parameters. One of the parameters may define the RB offset between the first PRB of CORESET#0 and the first PRB in which the first subcarrier of the SSB may be placed (the SSB may be in the same subcarrier raster, but not necessarily in the same RB raster as CORESET#0).

[0029] As mentioned above, the SSB may be in the same subcarrier raster as the common RB grid, but may not be aligned at the RB level. The subcarrier offset between the SSB and the common RB grid may be provided by the 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 the subcarrier offset between the SSB and the common RB grid. Additionally, when the SSB and CORESET#0 have the same SCS, only values ​​0,...,11 may be used.

[0030] In a specific case, CORESET#0 may be used to transmit the PDCCH for system information block 1 (SIB1) scheduling. CORESET#0 may not be configured by radio resource control (RRC) because it is used before the RRC connection is established. Therefore, CORESET#0 may be configured by a separate process and predefined parameters as outlined in FIG. 5. CORESET#0 may also be configured in PDCCH-ConfigCommon included in SIB1 or configured in the UE by dedicated signaling. In particular, the configuration may be obtained by a 4-bit value indicated in a table as an index provided in the MIB.

[0031] Figure 6 illustrates the principle of an example of synchronization raster points in the 0-3000 MHz frequency range. The channel raster may define a subset of radio frequency (RF) reference frequencies that can be used to identify RF channel locations in the UL and DL. The RF reference frequencies of the RF channels may map to resource elements on a carrier. The channel raster for the n8, n26, and n28 bands (intended for FRMC) may be 100 kHz. Additionally, the synchronization raster may indicate the frequency location of a synchronization block that can be used by the UE for system acquisition in the absence of explicit signaling of the synchronization block location. To quickly perform cell search, the synchronization raster may be much sparser than the channel raster. In the band of interest, the channel raster may typically have 100 kHz spacing where synchronization raster points may be defined in clusters of three points, with points within a cluster separated by 100 kHz (with raster offsets within a cluster being 50, 150, and 250 kHz), and the clusters separated from each other by 1200 kHz.

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

[0033] FIG. 8 illustrates a table of valid synchronization raster points for n100 based on a synchronous raster design. For the analysis of band n100, two guard band assumptions may be considered. The first band assumption may include 142.5 kHz assuming a 3 MHz bandwidth allocation, and the second band assumption may include 242.5 kHz assuming a 5 MHz bandwidth allocation. Both assumptions may be made at 90% spectrum utilization (SU). Additionally, valid synchronization raster points for n100 (such that PSS / SSS may be enabled in the band) may be based on the synchronous raster design as illustrated in FIG. 8.

[0034] It can be observed from Figure 8 that the current synchronization raster design in FR1 may not provide a synchronization raster point at n100 to support narrow channel bandwidth allocations at the band edges when assuming a guard band for 5 MHz NR allocations. Additionally, when assuming the guard band required for 3 MHz NR allocations (e.g., 142.5 kHz guard), PSS / SSS may be allocated in the lower portion of the n100 band. Therefore, a new design for the n100 synchronization raster may be required to support NB NR allocations at both ends of the band. Furthermore, synchronization raster points (or clusters) may be placed closer than every 1.2 MHz for 3 MHz NR operation. While it may be desirable to define synchronization raster points on a 100 kHz raster (i.e., the same as the channel raster), only a single SSB puncture pattern for a given SSB Tx bandwidth should need to be defined. As an example, Figure 9 illustrates synchronization raster points for punctured and unpunctured SSBs in a band of interest.

[0035] Figure 10 illustrates example CCE indices. In particular, Figure 10 illustrates CCE indices for interleaved mapping of 2-symbol and 3-symbol CORESETs. Figure 10 also illustrates a possible physical downlink control channel (PDCCH) transmission for CORESET#0. For example, it may be assumed that the transmission bandwidth may be reduced from one side (i.e., from the upper frequency / larger PRB index). Here, CORESET#0 may utilize interleaved mapping between CCEs and resource element group (REG) bundles (consisting of 6 REGs). Nevertheless, utilizing such interleaved mapping may result in some drawbacks.

[0036] For example, for a 2-symbol CORESET, AL8 (aggregation level 8) cannot be sent without puncturing (which specifies a bandwidth less than 4.32 MHz). Additionally, the minimum bandwidth (without puncturing) for AL4 may be 3.24 MHz. At the same time, 1 / 3 of the PRB resources (PRBs 6 to 11 in FIG. 10) may be unused. Furthermore, puncture resolution at the CCE level may be preferable because UEs are expected to average channel estimates within a CCE. Nevertheless, the PRB level may also be considered, allowing for finer granularity than the CCE level.

[0037] As further illustrated in Figure 10, for a 3-symbol CORESET, AL8 may not be sent without puncturing (if the bandwidth is less than 3.6 MHz). At the same time, 20% of the PRB resources may be unused. Furthermore, the minimum bandwidth for AL4 (without puncturing) may be 2.88 MHz, leaving 50% of the PRB resources unused. In this example, puncture resolution at the CCE level may be preferred (because the UE is expected to average channel estimates within a CCE), but the PRB level may also be considered (the PRB level may allow for finer granularity than the CCE level).

[0038] As described herein, excessive puncturing can reduce PDCCH coverage. In particular, PDCCH detection performance can be expected to suffer from puncturing, and the impact of puncturing can be significant, especially for high AL PDCCH candidates. Similar findings can also be found from PBCH simulations.

[0039] For PBCH simulations in unknown puncture scenarios, the UE may experience significant performance degradation, as shown in Figure 11. In particular, Figure 11 illustrates a simulation case with unilateral puncturing of the PBCH. Additionally, additive white Gaussian noise (AWGN) interference may be used to mimic GSM-R interference, and the gNB may not transmit the PBCH on these GSM-R PRBs. Furthermore, the UE may perform detection assuming an improper PBCH Tx bandwidth (BW). As illustrated in Figure 11, the degradation in the signal-to-noise ratio (dSNR) required for sufficient PBCH detection performance is shown for different amounts of PRB puncturing (i.e., 2, 4, and 6 PRBs). Depending on the interference power, the PBCH detection performance may be degraded by more than 5 dB. This may suggest that the UE cannot frequently access the cell. It may also be noted that in deployment scenarios such as GSM-R refarming, GSM and NR BSs are likely to be co-located at the same site, making higher GSM power levels more likely.

[0040] Based on the above drawbacks, there may be a need for PDCCH performance improvement. However, problems may arise when using only AL4 and AL8. For example, 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 greater than 3 dB. Regarding the issue of using AL8, aggregation level 8 may not be used without puncturing. Based on PBCH results, 25% puncturing in a scenario where the UE does not know the actual puncturing pattern may be greater than 5 dB (see Figure 11). This may be a typical amount of puncturing for NB NR, as shown in Figure 7.

[0041] Another issue that may arise may arise from the need to support different deployment options. For example, a 3 MHz channel bandwidth and a maximum Tx BW of 15 RBs may be sufficient for use cases related to the n8, n26, and n28 bands. For these bands, there may be no motivation to consider a maximum Tx BW narrower than 15 RBs due to the coverage drawbacks of a narrower BW. Nevertheless, the 5.6 MHz band n100 allocated to railway mobile radio may require further consideration, as a BW of 5 MHz or less may be required during the transition from GSM-R to FRMCS. For example, it can be expected that many different types of transition scenarios may exist, depending on the operation and characteristics of the associated railway and GSM-R network deployments. This may suggest that a variety of BWs may be available for FRMCS.

[0042] For example, an NR design with a 20-RB SSB can function as such when the available BW is between 4 MHz and 5 MHz (i.e., up to 20-25 RBs). That is, the system may occupy a small portion of the 5 MHz channel BW. Nevertheless, the CORESET#0 configuration may not be fully compatible with bandwidths below 24 RBs. On the other hand, when the available BW is between 3 MHz and less than 4 MHz (i.e., up to 15-19 RBs), the UE can assume a 3 MHz / 15 RB BW for SSB acquisition. Nevertheless, having unreasonable assumptions on PDCCH puncturing can further degrade performance and prevent access to the system.

[0043] Traditionally, roughly 10 to 14 GSM-R carriers may be required for secure railway communications in band n100. These 10 to 14 GSM-R carriers may occupy 2 to 2.8 MHz, leaving 3.6 to 2.8 MHz for NR-based FRMCS and the necessary guard band. While a 15 TB BW may be narrow enough to leave enough space for 10 GSM-R carriers, it may be too wide to facilitate coexistence with 14 GSM-R carriers. Therefore, it may be reasonable to consider an optional second, narrower BW for SSBs up to 15 RB Tx BW. For example, at the lower edge of n100, as well as between GSM-R and NR, a 12- or 13-RB BW may be considered as an optional second, narrower BW, leaving a total of 640 kHz or 460 kHz for the guard band.

[0044] According to a particular example embodiment, based on the considered synchronization raster design of FIG. 7, when having different synchronization raster points for punctured and non-punctured SSBs, a punctured SSB using the full transmission bandwidth (e.g., all 15 RBs in a 15-RB channel bandwidth) means that the subcarrier offset between the first subcarrier of the SSB and the first subcarrier of an RB in the common RB (CRB) grid can be zero. In other words, the L1 parameter k SSBmay be zero. In other example embodiments, the considered NB NR synchronization raster design may support multiple transmission bandwidths with even and odd numbers of RBs. In a particular example embodiment, when the transmission bandwidth (e.g., 18 RBs) is wider than the SSB BW (e.g., 15 RBs) and the number of RBs in the Tx BW has a different parity than the number of RBs in the SSB, a 6 subcarrier offset may be used between the SSB and CRB grids. According to a particular example embodiment, the use of a 6 subcarrier offset may result from a 90 kHz or 1 / 2 PRB offset between the channel raster and the synchronization raster. In this example embodiment, the L1 parameter k SSB can support values ​​0 and 6.

[0045] In a particular illustrative embodiment, the UE may select a synchronization raster point for the NB operation where the offset between the first subcarrier of the SSB and the first subcarrier of the CRB is 0 (i.e., k SSB = 0). SSB For example, conditional diversion may address the need to fully (or nearly fully) utilize the transmission bandwidth, reduce possible offsets, or align the CRB and SSB grids. As mentioned above, conditional diversion may be based on a considered synchronization raster design. Additionally, in some example embodiments, the condition may be that the UE is on a predefined band (e.g., n100) and has detected a PSS / SSS on a synchronization raster used with punctured SSBs. For diversion, the UE may detect a different k sigma than when an SSB is detected on an old synchronization raster point, in this case. SSB In another example embodiment, the subcarrier offset can be 0 for a Tx BW with the same RB parity as the SSB, or an offset of 6 for a Tx BW with a different RB parity than the SSB. SSBmay be considered a conditional diversion for k SSB The parity of the CORESET#0 RB indicated by k also indicates the SSB subcarrier offset (which may implicitly assume that CORESET#0 spans the entire Tx BW). SSB A subset of bits (e.g., one bit) from CORESET#0 may be conditionally diverted. In this example embodiment, CORESET#0 may not need to span the entire Tx BW. Additionally, in some example embodiments, k SSB The conditional diversion of a subset of bits from may mean that at least the UE is on a predefined band (e.g., n100) and the UE can determine that the SSB is to be punctured based on, for example, the detected PSS / SSS location (a synchronization raster point or a frequency location near the edge of the band) or based on the decoded PBCH content or detected PBCH DMRS.

[0046] According to a particular example embodiment, the bit k used to indicate the offset SBB , or k SBB A predetermined subset of bits may be repurposed to carry different additional information to facilitate NR NB operation. For example, the information may include, without limitation, at least one parameter indicative of the valid RBs of CORESET#0, the size, location or structure of CORESET#0, the PBCH puncture pattern (i.e., the valid RBs of the PBCH for confirmation), whether CORESET#0 resources for Type 0-PDCCH are interleaved, whether Type 0-PDCCH is repeatedly transmitted, or at least one of the transmission bandwidth in terms of RBs or the delta between the transmission bandwidth and the channel bandwidth. Thus, according to a specific example embodiment, the UE may assume that, for the synchronization raster point determined for NB NR operation, the offset between the first subcarrier of the SSB and the first subcarrier of the CRB is 0 (or a limited set of values). Additionally, kSBB The bits in the PBCH used to carry the new additional information may be repurposed (ie, reused) to carry the new additional information.

[0047] Figure 12 illustrates an example set of RBs and slot symbols of CORESET. In particular, Figure 12 illustrates a set of RBs and slot symbols of CORESET for a Type 0-PDCCH search space set when the (SS / PBCH block, PDCCH) SCS is {15,15} kHz for a frequency band having a minimum channel bandwidth of 5 MHz or 10 MHz. As described in the example embodiment below, there may be several ways to indicate valid RBs for CORESET#0. For example, in a particular example embodiment, Figure 12 defines the location of CORESET#0 for a legacy SSB (i.e., operation according to an SSB with 20 RBs). Additionally, k SSB may define the valid (non-punctured) RBs of CORESET#0 (k SSB (Similar consequences may occur if k defines an invalid (punctured) RB for CORESET#0.) In another example embodiment, k SSB 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 (which may replace "Number of RBs" in FIG. 12), CORESET#0 location relative to punctured SSBs (which may replace Offset(RB) in FIG. 12), and / or REG-to-CCE mapping corresponding to interleaving versus non-interleaving. As described below, the examples illustrated in FIGS. 13-16 may be interpreted according to the options for indicating valid RBs for CORESET#0 described above.

[0048] 13 illustrates an example relationship between k_ssb and CORESET#0 according to a particular example embodiment. 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 smallest RB of the punctured SSB, and the size of the punctured SSB in this example may be 12.

[0049] Figure 14 illustrates example relationships between k_ssb, CORESET#0, and SSB / CORESET alignment, according to a particular example embodiment. As illustrated in Figure 14, the difference between the table of Figure 14 and the table of Figure 13 is that two alternative schemes for aligning the punctured SSB and CORESET#0 may be considered. For example, in one alternative, the punctured SSB and CORESET#0 may be aligned according to the minimum RB of the punctured SSB. Alternatively, another alternative alignment may be according to the maximum RB of the punctured SSB.

[0050] Figure 15 illustrates an example relationship between k_ssb, CORESET#0, SSB / CORESET alignment, and REG-to-CCE mapping according to a particular example embodiment. In particular, a difference from the table of Figure 14 is that in Figure 15, k_ssb may indicate not only the CORESET location for the punctured SSB, but also the REG-to-CCE mapping for CORESET#0 (interleaved vs. non-interleaved). Furthermore, Figure 16 illustrates an example relationship between k_ssb, CORESET#0, SSB / CORESET alignment, REG-to-CCE mapping, and PBCH size verification according to a particular example embodiment. In particular, compared with the table of Figure 15, k_ssb in Figure 16 may also indicate PBCH size (verification). Here, it may be assumed that for the considered synchronization raster point, there may be two valid PBCH size options, namely, 12 (or 13) RBs and 15 RBs. Additionally, the UE may (occasionally) succeed in correctly decoding the PBCH even with invalid assumptions about the PBCH size. Additionally, the PBCH size verification in Figure 16 may ensure that the UE obtains correct knowledge about the PBCH size (which may be important since this information may be used for other scenarios, such as determining valid RBs for CORESET#0).

[0051] Figure 17 illustrates an example relationship between k_ssb, CORESET#0, SSB / CORESET alignment, Type 0-PDCCH repetition, and PBCH size verification, according to a particular example embodiment. As illustrated in Figure 17, the difference compared to the table of Figure 16 is that k_ssb may indicate whether a Type 0-PDCCH is repeatedly transmitted (instead of indicating REG-to-CCE mapping). In a particular example embodiment, when a Type 0-PDCCH is repeatedly transmitted, the same Type 0-PDCCH may be repeated on consecutive Type 0-PDCCH opportunities. According to a particular example embodiment, the repetition pattern may be predetermined and tied to a slot index, and the repetition may be limited to a particular PDCCH candidate (e.g., with AL8).

[0052] Figure 18 illustrates example relationships between k_ssb, CORESET#0, SSB / CORESET alignment, SSB subcarrier offset, and PBCH size verification, according to a particular example embodiment. As illustrated in Figure 18, CORESET#0 may span the entire Tx BW. In a particular example embodiment, it may be assumed that for the considered synchronization raster point, there may be two valid PBCH (or SSB) size options, e.g., 13 RBs and 15 RBs.

[0053] Figure 19 illustrates example relationships between the k_ssb bit, the number of RBs for CORESET#0, and SSB / CORESET alignment, according to a particular example embodiment. In particular, Figure 19 illustrates an example for a 20-RB SSB. Furthermore, Figure 20 illustrates example relationships between the k_ssb, SSB subcarrier offset, the number of RBs for CORESET#0, and PBCH size verification, according to a particular example embodiment. According to Legacy / Rel15, the NR synchronization raster may be used for NB NR operation. For example, the NR synchronization raster may be used for a 4.4 MHz Tx BW, which suggests a 22-RB CORESET#0. Alternatively, the NR synchronization raster may be used for NB NR operation, given that the 100 kHz synchronization raster is not employed and the Rel15 NR synchronization raster or a variant thereof is used. In such cases, certain example embodiments may contemplate that the set of SSB subcarrier offsets that can be indicated in k_ssb may be reduced. For example, as illustrated in Figures 19 and 20, k_ssb may be reduced to 4, 6, or 8 subcarriers (requiring 2 bits), or 2, 4, 6, 8, or 10 subcarriers. Additionally, in such cases, some of the k_ssb bits or signaling states may be repurposed to indicate CORESET#0-related information. Alternatively, in such cases, the k_ssb bits may be repurposed to jointly indicate CORESET#0-related information and SSB subcarrier offsets. While Figures 12-19 illustrate some example embodiments, different modifications may be possible in other example embodiments. For example, 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 existing tables to create a new table. Additionally, in further example embodiments, it may be possible to use k_ssb (and the conditional diversion principle) to indicate additional properties for CORESET#0, Type 0_PDCCH, or other use cases.

[0054] 21 illustrates an example flow diagram of a method according to a particular example embodiment. In one 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 example, in one example embodiment, the method of FIG. 21 may be performed by a UE similar to one of the apparatuses 10 or 20 illustrated in FIG. 22.

[0055] According to a particular example embodiment, the method of Figure 21 may include detecting a synchronization signal at a synchronization raster point on a band of interest, at 100. The method may also include determining a puncture assumption pattern associated with the synchronization signal for the communication channel based on bits of the radio parameters, at 105. The method may further include demodulating and decoding the communication channel based on the puncture assumption associated with the synchronization raster point, at 110.

[0056] According to certain example embodiments, the method may further include determining whether the synchronization raster point is associated with narrowband new radio operation in response to detecting the synchronization signal. In some example embodiments, the synchronization raster frequency location may be determined by specification and may be specifically associated with one or more frequency bands. Thus, when the UE conveys a search, the UE may search for a specific synchronization raster point associated with a particular band (e.g., intended for NB NR operation). According to some example embodiments, bits of the radio parameters may indicate a synchronization signal subcarrier offset and information facilitating narrowband new radio operation. According to other example embodiments, the method may also include diverting a portion of the bits of the radio parameters to convey information facilitating narrowband new radio operation. In certain example embodiments, a first subset of bits from the bits of the radio parameters may be reserved to indicate a synchronization signal subcarrier offset. In other example embodiments, a second subset of bits from the bits of the radio parameters may be conditionally diverted.

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

[0058] 22 illustrates sets of apparatus 10 and 20 according to a particular example embodiment. In a particular example embodiment, apparatus 10 may be an element in a communications network or an element associated with such a network, such as a UE, mobile equipment (ME), mobile station, mobile device, fixed device, IoT device, mounted mobile device, or other similar device. Note that one skilled in the art would understand that apparatus 10 may include components or features not shown in FIG. 22 .

[0059] In some example embodiments, device 10 may include one or more processors, one or more computer-readable storage media (e.g., memory, storage, etc.), one or more wireless access components (e.g., modem, transceiver, etc.), and / or a user interface. In some example embodiments, device 10 may be configured to operate using one or more wireless access technologies, such as GSM, LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-IoT, Bluetooth, NFC, MulteFire, and / or any other wireless access technology. Note that one skilled in the art would understand that device 10 may include components or features not shown in FIG. 22 .

[0060] As illustrated in the example of FIG. 22 , device 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-purpose or special-purpose processor. Indeed, processor 12 may include, by way of example, one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), and a processor based on a multi-core processor architecture. 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, device 10 may include two or more processors that may form a multiprocessor system that may support multiprocessing (e.g., in this case, processor 12 may represent a multiprocessor). According to certain example embodiments, the multiprocessor system may be tightly coupled (e.g., to form a computer cluster) or loosely coupled.

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

[0062] Apparatus 10 may further include or be coupled to 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 may be of any type appropriate to the local application environment and may be implemented using any suitable volatile or non-volatile data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and / or removable memory. For example, memory 14 may include any combination of random access memory (RAM), read-only memory (ROM), static storage such as a magnetic or optical disk, a hard disk drive (HDD), or any other type of non-transitory machine- or computer-readable medium. The instructions stored in memory 14 may include program instructions or computer program code that, when executed by processor 12, enable apparatus 10 to perform tasks as described herein.

[0063] In certain illustrative embodiments, device 10 may further include or be coupled to a drive or port (internal or external) configured to accept and read an external computer-readable storage medium, such as an optical disk, a USB drive, a 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 device 10 to perform any of the methods and examples illustrated in FIGS. 1-21.

[0064] In some example embodiments, device 10 may also include or be coupled to one or more antennas 15 for receiving downlink signals and transmitting from device 10 over the UL. Device 10 may further include a transceiver 18 configured to transmit and receive information. Transceiver 18 may also include a radio interface (e.g., a modem) coupled to antenna 15. The radio interface may support multiple radio access technologies including one or more of GSM, LTE, LTE-A, 5G, NR, WLAN, NB-IoT, Bluetooth, BT-LE, NFC, RFID, UWB, etc. The radio interface may include other components, such as filters, converters (e.g., digital-to-analog converters, etc.), symbol demappers, signal shaping components, inverse fast Fourier transform (IFFT) modules, etc., for processing symbols, such as OFDMA symbols, carried by the downlink or UL.

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

[0066] In particular 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 to device 10. The memory may also store one or more functional modules, such as applications or programs, for providing additional functionality to device 10. Components of device 10 may be implemented in hardware or as any suitable combination of hardware and software. According to particular example embodiments, device 10 may optionally be configured to communicate with device 20 via a wireless or wired communication link 70 using any radio access technology, such as NR.

[0067] According to particular example embodiments, the processor 12 and memory 14 may be included in or form part of processing or control circuitry. Additionally, in some example embodiments, the transceiver 18 may be included in or form part of transmitting and receiving circuitry.

[0068] For example, in a particular illustrative embodiment, apparatus 10 may be controlled by memory 14 and processor 12 to detect synchronization signals at synchronization raster points on a band of interest. Apparatus 10 may also be controlled by memory 14 and processor 12 to determine a puncture 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 puncture assumption associated with the synchronization raster point.

[0069] As illustrated in the example of Figure 22, the apparatus 20 may be a network, a core network element, or an element within or associated with a communications network, such as a gNB, NW, base station (BS), access point (AP), or similar device. Note that one skilled in the art would understand that the apparatus 20 may include components or features not shown in Figure 22.

[0070] As illustrated in the example of FIG. 22 , device 20 may include processor 22 for processing information and executing instructions or operations. Processor 22 may be any type of general-purpose or special-purpose processor. For example, processor 22 may include, by way of example, one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), and a processor based on a multi-core processor architecture. While a single processor 22 is shown in FIG. 22 , multiple processors may be utilized depending on other example embodiments. For example, it should be understood that in certain example embodiments, device 20 may include two or more processors that may form a multiprocessor system that may support multiprocessing (e.g., in this case, processor 22 may represent a multiprocessor). In certain example embodiments, the multiprocessor system may be tightly coupled (e.g., to form a computer cluster) or loosely coupled.

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

[0072] Apparatus 20 may further include or be coupled to 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 may be of any type appropriate to the local application environment and may be implemented using any suitable volatile or non-volatile data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and / or removable memory. For example, memory 24 may include any combination of random access memory (RAM), read-only memory (ROM), static storage such as a magnetic or optical disk, a hard disk drive (HDD), or any other type of non-transitory machine- or computer-readable medium. The instructions stored in memory 24 may include program instructions or computer program code that, when executed by processor 22, enable apparatus 20 to perform tasks as described herein.

[0073] In certain illustrative embodiments, device 20 may further include or be coupled to a drive or port (internal or external) configured to receive and read an external computer-readable storage medium, such as an optical disk, a USB drive, a 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 device 20 to implement the methods and examples illustrated in FIGS. 1-20.

[0074] In certain illustrative embodiments, device 20 may also include or be coupled to one or more antennas 25 for transmitting and receiving signals and / or data to and from device 20. Device 20 may further include or be coupled to a transceiver 28 configured to transmit and receive information. Transceiver 28 may include multiple wireless interfaces, which may be coupled to antenna 25, for example. The wireless interfaces may support multiple wireless access technologies, including one or more of GSM, NB-IoT, LTE, 5G, WLAN, Bluetooth, BT-LE, NFC, radio frequency identification (RFID), ultra-wideband (UWB), MulteFire, etc. The wireless interfaces may include components, such as filters, converters (e.g., digital-to-analog converters), mappers, fast Fourier transform (FFT) modules, etc., for generating symbols for transmission over one or more downlinks and for receiving symbols (e.g., via the UL).

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

[0076] In particular illustrative embodiments, 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 to device 20. Memory may also store one or more functional modules, such as applications or programs, for providing additional functionality to device 20. Components of device 20 may be implemented in hardware or as any suitable combination of hardware and software.

[0077] According to some example embodiments, the processor 22 and memory 24 may be included in or form part of processing or control circuitry. Additionally, in some example embodiments, the transceiver 28 may be included in or form part of transmitting and receiving circuitry.

[0078] As used herein, the term “circuit equipment” may refer to a hardware-only circuit equipment implementation (e.g., analog and / or digital circuit equipment), a combination of hardware circuitry and software, a combination of analog and / or digital hardware circuitry and software / firmware, any portion of a hardware processor with software (including a digital signal processor) that work together to cause a device (e.g., devices 10 and 20) to perform various functions, and / or a hardware circuit and / or processor, or portion thereof, that uses software for operation but may not be present when software is not necessary for operation. As a further example, as used herein, the term “circuit equipment” may also cover the mere implementation of a hardware circuit or processor (or multiple processors), or a portion of a hardware circuit or processor, and its accompanying software and / or firmware. The term circuit equipment may also cover, for example, a baseband integrated circuit in a server, a cellular network node or device, or other computing or network device.

[0079] In some example embodiments, an apparatus (e.g., apparatus 10 and / or apparatus 20) may include means for performing any of the methods, processes, or variations discussed herein. Examples of means may include one or more processors, memories, controllers, transmitters, receivers, and / or computer program code for causing the performance of operations.

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

[0081] Certain example embodiments described herein provide several technical improvements, enhancements, and / or advantages. For example, in some example embodiments, it may be possible for the UE to explicitly determine the assumed puncture pattern for the PDCCH (e.g., on CORESET#0) and also for the PBCH when monitored after or during initial access (e.g., PDCCH monitoring for SIB1 scheduling). Additionally, the UE may also be capable of performing optimal demodulation and decoding. In other example embodiments, it may be possible to have different puncture assumptions for SSB and PDCCH (CORESET#0). In further example embodiments, it may be possible to provide better performance for PDCCH (CORESET#0) detection via correct puncture assumptions for different bandwidth options depending on the deployment. Additionally, it may be possible for the UE to avoid hardware modifications.

[0082] The computer program product may include one or more computer-executable components configured to perform some example embodiments when the program is executed. The one or more computer-executable components may be at least one software code or a portion thereof. Modifications and configurations required to perform the functions of a particular example embodiment may be implemented as routines that may be executed as additional or updated software routines. The software routines may be downloaded to a device.

[0083] By way of example, the software or computer program code, or portions thereof, may be in source code form, object code form, or some intermediate form, and may be stored on some kind of carrier, distribution medium, or computer-readable medium, which may be any entity or device capable of carrying a program. Such carriers may include, for example, recording media, computer memory, read-only memory, optical-electronic and / or electrical carrier signals, telecommunications signals, and software distribution packages. Depending on the processing power required, the computer program may be executed in a single electronic digital computer or distributed among several computers. The computer-readable medium or computer-readable storage medium may be a non-transitory medium.

[0084] In other example embodiments, the functions may be implemented by hardware or circuitry included in a device (e.g., device 10 or device 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 functions may be implemented as signals that are non-tangible means that may be carried by electromagnetic signals downloaded from the Internet or other network.

[0085] According to certain example embodiments, an apparatus such as a node, device, or corresponding component may be configured as a circuit apparatus, computer, or microprocessor, such as a single-chip computer element, or as a chipset that includes at least a memory to provide storage capacity used for arithmetic operations, and an operating processor to perform the arithmetic operations.

[0086] Those skilled in the art will readily understand that the present disclosure as discussed above may be practiced in a different order of steps and / or with hardware elements in different configurations than those disclosed. Thus, while the present disclosure has been described based on these example embodiments, it will be apparent to those skilled in the art that certain modifications, variations, and alternative constructions will be apparent while remaining within the spirit and scope of the example embodiments. Although the above embodiments refer to 5G NR and LTE technologies, the above embodiments may also apply to any other current or future 3GPP technologies, such as LTE-Advanced, and / or fourth-generation (4G) technologies.

[0087] Partial glossary

[0088] 3GPP 3rd Generation Partnership Project

[0089] 5G (5th Generation)

[0090] 5GCN 5G Core Network

[0091] 5GS 5G System

[0092] BS base station

[0093] CBW Channel Bandwidth

[0094] DCI Downlink Control Information

[0095] DL Downlink

[0096] DMRS demodulation reference signal

[0097] eNB Enhanced Node B

[0098] E-UTRAN Evolved UTRAN

[0099] gNB 5G or Next Generation Node B

[0100] LTE Long Term Evolution

[0101] MIB Master Information Block

[0102] NB Narrowband

[0103] NR new radio

[0104] NW Network

[0105] OFDM Orthogonal Frequency Domain Multiplexing

[0106] PBCH Physical Broadcast Channel

[0107] PRB Physical Resource Block

[0108] PSS primary synchronization signal

[0109] RE resource element

[0110] RB Resource Block

[0111] RRC Radio Resource Control

[0112] SCS Subcarrier Spacing

[0113] SIB System Information Block

[0114] SSB sync signal block

[0115] SSS secondary synchronization signal

[0116] UE User Equipment

[0117] UL Uplink

Claims

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

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

3. 3. The method of claim 1, wherein the bits of the radio parameters indicate a synchronization signal subcarrier offset and information facilitating the narrowband new radio operation.

4. diverting a portion of the bits of the radio parameters to carry information facilitating the narrowband new radio operation. further comprising a first subset of bits from the bits of the radio parameter is reserved for indicating a synchronization signal block subcarrier offset; The method according to any of claims 1 to 3, wherein a second subset of bits from said bits of said radio parameters is conditionally diverted.

5. The information is valid resource blocks of the control resource set; At least one parameter indicative of the size, location, or structure of the control resource set; Physical broadcast channel puncture pattern, whether the resources of the control resource set for physical downlink control channels are interleaved; whether the physical downlink control channel is repeatedly transmitted; or the transmission bandwidth in terms of resource blocks or in terms of the change between the transmission bandwidth and the channel bandwidth The method of claim 3 or 4, comprising at least one of:

6. The method according to any one of claims 1 to 5, wherein the narrowband new radio associated with said synchronization raster point supports multiple transmission bandwidths comprising even and odd numbers of resource blocks.

7. performing a conditional diversion for said bits of said radio parameters. further comprising performing the conditional repurposing for the bits of the radio parameter includes making an assumption that an offset between a first subcarrier of a synchronization signal block and a first subcarrier of a common resource block is zero for additional synchronization raster points intended for the narrowband new radio operation; The method according to any one of claims 1 to 6.

8. at least one processor; at least one memory containing computer program code; An apparatus comprising: The at least one memory and the computer program code, when executed by the at least one processor, at least detecting a synchronization signal at a synchronization raster point on a band of interest; determining a puncturing 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 a puncture assumption associated with the synchronization raster point; 11. An apparatus comprising: a storage instruction for causing said apparatus to:

9. The at least one memory and the computer program code, when executed by the at least one processor, at least determining whether the synchronization raster point is associated with narrowband new radio operation in response to detecting the synchronization signal; 9. The apparatus of claim 8, further comprising stored instructions that cause the apparatus to:

10. 10. The apparatus of claim 8 or 9, wherein the bits of the radio parameters indicate a synchronization signal subcarrier offset and information facilitating the narrowband new radio operation.

11. The at least one memory and the computer program code, when executed by the at least one processor, at least diverting a portion of the bits of the radio parameters to carry information facilitating the narrowband new radio operation; and further comprising stored instructions that cause the device to: a first subset of bits from the bits of the radio parameter is reserved for indicating a synchronization signal block subcarrier offset; The device according to any of claims 8 to 10, wherein a second subset of bits from said bits of said radio parameters is conditionally diverted.

12. The information is valid resource blocks of the control resource set; At least one parameter indicative of the size, location, or structure of the control resource set; Physical broadcast channel puncture pattern, whether the resources of the control resource set for physical downlink control channels are interleaved; whether the physical downlink control channel is repeatedly transmitted; or the transmission bandwidth in terms of resource blocks or in terms of the change between the transmission bandwidth and the channel bandwidth The apparatus of claim 11 , comprising at least one of:

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

14. The at least one memory and the computer program code, when executed by the at least one processor, at least performing conditional diversion for the bits of the radio parameters; and further comprising stored instructions that cause the device to:

14. The apparatus of claim 8, wherein performing the conditional repurposing 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 subcarrier of a synchronization signal block and a first subcarrier of a common resource block is zero.

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

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

17. 17. The apparatus of claim 15 or 16, wherein the bits of the radio parameters indicate a synchronization signal subcarrier offset and information facilitating the narrowband new radio operation.

18. means for diverting a portion of the bits of the radio parameters to carry information facilitating the narrowband new radio operation; Furthermore, a first subset of bits from the bits of the radio parameter is reserved for indicating a synchronization signal block subcarrier offset; a second subset of bits from the bits of the radio parameter are conditionally diverted; 18. The device according to any one of claims 15 to 17.

19. The information is valid resource blocks of the control resource set; At least one parameter indicative of the size, location, or structure of the control resource set; Physical broadcast channel puncture pattern, whether the resources of the control resource set for physical downlink control channels are interleaved; whether the physical downlink control channel is repeatedly transmitted; or the transmission bandwidth in terms of resource blocks or in terms of the change between the transmission bandwidth and the channel bandwidth 20. The apparatus of claim 18, comprising at least one of:

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

21. means for implementing conditional diversion for said bits of said radio parameters; Furthermore, performing the conditional repurposing for the bits of the radio parameter includes making an assumption that an offset between a first subcarrier of a synchronization signal block and a first subcarrier of a common resource block is zero for additional synchronization raster points intended for the narrowband new radio operation. An apparatus according to any one of claims 15 to 20.

22. A non-transitory computer readable medium having stored thereon program instructions for carrying out the method of any of claims 1 to 7.

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

Images