CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to U.S. Provisional Patent Application No. 62/292,212 filed on February 5, 2016, the subject matter of which is hereby incorporated by reference in its entirety.

TECHNICAL FIELD

[0002] The disclosed subject matter relates generally to telecommunications. Certain embodiments relate more particularly to certain techniques and technologies for supporting coexistence of Narrowband Internet of Things (NB-IoT) and Enhanced Machine-Type Communications (eMTC) on the same Long Term Evolution (LTE) carrier.

BACKGROUND

[0003] Cellular communication systems are currently being developed and improved for machine type communication (MTC), which is a form of communication characterized by lower demands on data rates than for example mobile broadband, but with higher requirements on e.g. low cost device design, better coverage, and ability to operate for years on batteries without charging or replacing the batteries.

[0004] Currently, the Third Generation Partnership Project (3GPP) is standardizing Enhanced Machine-Type Communications (eMTC) (See e.g., 3GPP Tdoc RP- 150492) as well as Narrowband Internet of Things (NB-IoT) [RP- 152284] as part of LTE Release 13 for satisfying all the requirements put forward by MTC type applications, while maintaining backward compatibility with current LTE radio access technology. eMTC

[0005] The eMTC features discussed in 3 GPP Tdocs RP-152024 and Rl-157926 include a low-complexity user equipment (UE) category called UE category Ml (or Cat-Ml for short) and coverage enhancement (CE) techniques (CE modes A and B) that can be used together with UE category Ml or any other LTE UE category.

[0006] All eMTC features (both Cat-Ml and CE modes A and B) operate using a reduced maximum channel bandwidth compared to normal LTE. The maximum channel bandwidth in eMTC is 1.4 MHz whereas it is up to 20 MHz in normal LTE. The eMTC UEs are still able to operate within the larger LTE system bandwidth without problem. The main difference compared to normal LTE UEs is that the eMTCs can only be scheduled with 6 physical resource blocks (PRBs) of 180 kHz each at a time.

[0007] The restricted channel bandwidth of at most 6 PRBs also means that system information (known as SIB 1 -BR or SIB Ibis) transmissions that are broadcasted to eMTC UEs need to be restricted to a maximum of 6 PRBs.

[0008] To achieve good frequency diversity even though the channel bandwidth is relatively small, frequency hopping across the LTE system bandwidth is applied to the SIB Ibis transmissions. The number of frequency positions that the hopping occurs between depends on the LTE system bandwidth. For the largest system bandwidth of 20 MHz, the SIB Ibis transmission hops between 4 different narrowbands (NBs) of 6 PRBs each.

[0009] 3GPP RAN WG1 meeting #83 agreed on the following frequency hopping for SIB Ibis:

• S is a set of valid DL narrowbands for SIB Ibis, the narrowband is indexed in the order of increasing value

o S = {so, si, S2, ... ., SK-i }, K = number of valid DL narrowbands for

SIB Ibis

• For system BW less than 12 RBs

o SIB Ibis is transmitted in narrowband sj where j = PCID mod K

• For system BW between 12-50 RBs

o 1 st NB is sj where j = PCID mod K

o 2nd NB is (sj + floor(K/2)) mod K

o Starting at SFN mod 8 = 0, SIB Ibis transmission cycles through { 1st NB, 2nd NB}

• For system BW between 51-110 RBs

o 1 st NB is sj where j = PCID mod K

o 2nd NB is (sj + floor(K/4)) mod K

o 3rd NB is (sj + 2*floor(K/4)) mod K

o 4th NB is (sj + 3*floor(K/4)) mod K

o Starting at SFN mod 8 = 0, SIB Ibis transmission cycles through { 1st NB, 2nd NB, 3rd NB, 4th NB}

[0010] Figure (FIG.) 1 illustrates how an LTE system bandwidth of 10 MHz (50 PRBs) is divided into 8 NBs of 6 PRBs each. The remaining 50-8*6=2 PRBs can be found at the band edges (and in case of LTE system bandwidths consisting of an odd number of PRBs, the one PRB at the center of the LTE system bandwidth is also unused). The SIB Ibis is mapped to the NBs that do not overlap with the central 72 subcarriers where the PSS/SSS/PBCH transmissions may occur - this corresponds to the central 6 PRBs in the 10-MHz example in Figure 1 (one PRB consists of 12 subcarriers). This means that in this 10-MHz example, the SIB Ibis transmission can occur in 6 of the 8 NBs, as marked with "narrowband index SIB Ibis" in the 3rd column of FIG. 1. For a cell of 10 MHz (=50 PRBs) system bandwidth, frequency hopping of SIB Ibis occurs between 2 narrowbands. Thus for a given cell of a particular PCID value, frequency hopping of SIB Ibis occurs between 2 narrowbands, which are chosen from the 6 NBs using the equation above.

[0011] Furthermore, to achieve inter-cell interference randomization between different cells in the network, these up to 4 frequency positions depend on the physical cell identity (PCID) of the cell, which means that the frequency positions for SIB Ibis transmission can be different in different cells.

[0012] The UE knows the PCID of the cell from the synchronization signals (PSS and SSS) in the cell and it knows the LTE system bandwidth and system frame number (SFN) from the master information block (MIB) conveyed on the physical broadcast channel (PBCH) in the cell.

[0013] The eMTC UE furthermore receives information about the SIB Ibis scheduling in the MIB. 5 bits in the MIB are used to encode information about the transmission block size (TBS) of the SIB Ibis and the number of repetitions (R) within an 80-ms scheduling period as described in Table 1. As can be seen from the table, only 19 of the 32 possible values of these 5 bits are currently used. This is described, for instance, in 3GPP Tdoc Rl- 157926, section 7.1.7.2.7.

Table 1: SIB Ibis scheduling information in MIB

[0014] Furthermore, 3GPP RAN WG1 meeting #83 agreed on the following regarding paging-related transmissions:

• How to indicate set of M-PDCCH narrowband(s) for paging

o implicit mapping

^■ 1st narrowband = PCID mod N_NB_paging

^■ Other narrowbands are in consecutive order from 1st narrowband with wrap-around

• When more than one narrowband is configured for M-PDCCH for paging o The narrowband is up to RAN2

[0015] The specifications are not finalized yet but what this means is that also paging- related transmissions may occur in 6-PRB narrowband which is determined by the PCID.

NB-IoT operation modes

[0016] For NB-IoT, three different operation modes are defined, i.e., standalone, guard- band, and in-band. In standalone mode, the NB-IoT system is operated in a dedicated frequency band, e.g., refarming one or more GSM channels and use it as NB-IoT PRB. For in-band operation, the NB-IoT system can be placed inside the frequency bands used by the current LTE system, while in the guard-band mode, the NB-IoT system can be placed in the guard band used by the current LTE system. The NB-IoT has a system bandwidth of 180 kHz, i.e. substantially smaller than the LTE system bandwidth which is in the range from 1.4 MHz to 20 MHz.

[0017] The channel raster of the NB-IoT systems is on a frequency grid of 100 kHz. That is, the NB-IoT devices try to search for the NB-IoT carriers in a step size of 100 kHz. For the standalone deployment where one or more GSM channels are refarmed, this is not a problem since GSM channel bandwidth is 200 kHz and the center frequency is in the 100 kHz grid. But for the in-band and guard-band operations, due to the presence of the DC- carrier and the fact the center of the PRB is in between two sub-carriers, there is no PRB that falls directly on the cell search grid used in LTE in-band operation. The frequency offset to the 100 kHz grid is a minimum of ±2.5 kHz and ±7.5 kHz for even and odd number of PRBs in the LTE system bandwidth, respectively. In an NB-IoT receivers, algorithms can be designed such that the ±2.5 kHz or ±7.5 kHz offset can be handled by the device during the cell search process without degrading the synchronization performance considerably. However, larger offset values are more problematic, and the receiver may not be able to handle larger offsets. Therefore, the NB-IoT carriers are constrained to certain positions for the in-band and guard-band operations.

[0018] After the initial cell search phase, the NB-IoT devices need the knowledge of the operation mode to know the reference signal placements, to avoid collisions with legacy systems, and to decode the received data correctly. For in-band and guard-band operations, additional carrier frequency offset caused by channel raster step size, can cause potential performance degradations for NB-IoT devices to decode the Master Information Block (MIB) carried by the Narrow Band Physical Broadcast CHannel (NB-PBCH), especially the devices in really low SNR. Receiver algorithms can help to reduce the degradation, e.g., the receiver can try to hypothesizing and compensate different offset values before the NB- PBCH decoding.

NB-IoT operation in-band in LTE carrier

[0019] FIG. 2 shows the center frequency offsets for the LTE PRBs closest to the center frequency of the LTE carrier.

NB-IoT operation in LTE guard band

[0020] FIG. 3 illustrates an adjacent LTE PRB for guard band operation in 10 MHz LTE system bandwidth. [0021] In guard band operation, to maintain orthogonality to the LTE carrier and minimize the ACLR to adjacent LTE carrier, placing the NB-IoT PRB on the 15 kHz sub-carrier grid using the 12 "next" subcarriers adjacent to the LTE carrier is desired as shown in FIG. 3 for the 10 MHz LTE system bandwidth.

[0022] For the guard-band operation, for an LTE system with 10 or 20 MHz system bandwidth, it is possible to find NB-IoT carrier frequency that is ±2.5 kHz off the 100 kHz frequency raster. For other LTE system bandwidth, the offset to the 100 kHz raster is 52.5 kHz. Therefore, to get within the same ±7.5 kHz to the 100 kHz grid, 3 guard subcarriers are needed. One guard carrier is 15 kHz wide and placed in the same FFT grid at the legacy LTE system that gives orthogonality to the legacy LTE PRB. However, there are no other solutions to put the NB-IoT carriers on the exact 100 kHz raster grids on the LTE guard-band without losing orthogonality to the legacy LTE system.

[0023] Table 2 shows the center frequency offset for this adjacent PRB. Only the higher frequency guard band is shown, but the offset is the same to the adjacent PRB in the lower guard band. The 1.4 MHz system bandwidth has been excluded since guard band operation is not seen as feasible.

Table 2: Center frequency offset of the guard band PRB for different LTE system bandwidths

SUMMARY

[0024] In some embodiments of the disclosed subject matter, a method comprises identifying a subset of physical resource blocks, PRBs, within a Long Term Evolution, LTE, system bandwidth that are eligible for use as narrowband internet of things, NB-IoT, PRBs, wherein the eligibility of PRBs for use as NB-IoT PRBs is determined in relation to at least one machine-type-communication, MTC, narrowband within the LTE system bandwidth, and transmitting or receiving information via at least one of the eligible PRBs that has been allocated as a NB-IoT PRB, or via the at least one MTC narrowband.

[0025] In certain related embodiments, the at least one MTC narrowband comprises an MTC narrowband to be used for transmission of System Information Block 1, SIBlbis.

[0026] In certain related embodiments, the at least one MTC narrowband comprises an MTC narrowband to be used for transmission of paging-related information.

[0027] In certain related embodiments, identifying the eligible PRBs comprises predefining at least one 6-PRB narrowband as invalid for transmission of System Information Block 1, SIB lbis, and identifying at least one PRB within the predefined narrowbands as eligible for use as a NB-IoT PRB.

[0028] In certain related embodiments, identifying the eligible PRBs comprises identifying the eligible PRBs as eligible for use as secondary NB-IoT PRBs, and wherein the at least one of the eligible PRBs is allocated as at least one secondary NB-IoT PRB.

[0029] In certain related embodiments, the subset includes only one or more PRBs defined at the outermost edges of the LTE system bandwidth.

[0030] In certain related embodiments, identifying the eligible PRBs comprises identifying the eligible PRBs based on at least one of (a) whether the LTE system bandwidth includes an odd or even number of PRBS, and (b) a size of the LTE system bandwidth.

[0031] In certain related embodiments, the method further comprises transmitting or receiving configuration signaling indicating whether PRBs identifiable according to a predefined rule are reserved for use as NB-IoT PRBs. The configuration signaling may comprise e.g. particular combinations of values for a set of bits that also indicates scheduling information for a System Information Block 1, SIBlbis.

[0032] In certain related embodiments, the method further comprises transmitting or receiving configuration signaling indicating which PRBs within the LTE system bandwidth are reserved for use as NB-IoT PRBs.

[0033] In certain related embodiments, the method further comprises transmitting or receiving MTC information via the at least one MTC narrowband, by performing puncturing or rate matching to avoid transmission or reception of the MTC information via the at least one of the eligible PRBs allocated as a NB-IoT PRB.

[0034] In certain related embodiments, the method further comprises transmitting or receiving system information or paging-related information via the at least one MTC narrowband according to a frequency hopping pattern which is modified to exclude the at least one of the eligible PRBs allocated as a NB-IoT PRB.

[0035] In certain related embodiments, the method further comprises determining, based on a cell identity of a cell in which MTC information is to be transmitted, one or more MTC narrowbands via which to transmit the MTC information, and transmitting or receiving the MTC information via the one or more MTC narrowbands, except for the subset of PRBs identified as eligible for use as NB-IoT PRBs.

[0036] In certain related embodiments, the MTC information comprises system information or paging-related information for an MTC system.

[0037] In certain related embodiments, the subset of PRBs within the LTE system bandwidth that are eligible for use as NB-IoT PRBs are PRBs that are reserved for use as NB-IoT PRBs.

[0038] In certain related embodiments, the method further comprises allocating the at least one of the eligible PRBs as NB-IoT PRBs.

[0039] In some embodiments of the disclosed subject matter, an apparatus comprises at least one processor configured to identify a subset of physical resource blocks, PRBs, within a Long Term Evolution, LTE, system bandwidth that are eligible for use as narrowband internet of things, NB-IoT, PRBs, wherein the eligibility of PRBs for use as NB-IoT PRBs is determined in relation to at least one machine-type-communication, MTC, narrowband within the LTE system bandwidth, and at least one transmitter or receiver configured to transmit or receive information via at least one of the eligible PRBs that has been allocated as a NB-IoT PRB, or via the at least one MTC narrowband.

[0040] In some embodiments of the disclosed subject matter, an apparatus comprises means for identifying a subset of physical resource blocks, PRBs, within a Long Term Evolution, LTE, system bandwidth that are eligible for use as narrowband internet of things, NB-IoT, PRBs, wherein the eligibility of PRBs for use as NB-IoT PRBs is determined in relation to at least one machine-type-communication, MTC, narrowband within the LTE system bandwidth, and means for transmitting or receiving information via at least one of the eligible PRBs that has been allocated as a NB-IoT PRB, or via the at least one MTC narrowband.

[0041] In some embodiments of the disclosed subject matter, a non-transitory

computer-readable medium has stored thereon a computer program which, when executed by at least one processor of a radio access node, causes the radio access node to identify a subset of physical resource blocks, PRBs, within a Long Term Evolution, LTE, system bandwidth that are eligible for use as narrowband internet of things, NB-IoT, PRBs, wherein the eligibility of PRBs for use as NB-IoT PRBs is determined in relation to at least one machine- type-communication, MTC, narrowband within the LTE system bandwidth, and transmit or receive information via the at least one of the eligible PRBs that has been allocated as a NB- IoT PRB, or via the at least one MTC narrowband.

BRIEF DESCRIPTION OF THE DRAWINGS

[0042] The drawings illustrate selected embodiments of the disclosed subject matter. In the drawings, like reference labels indicate like features.

[0043] FIG. 1 illustrates a 10 MHz LTE system bandwidth with 8 narrowbands for eMTC and 6 narrowbands allowed for SIB Ibis transmission

[0044] FIG. 2 illustrates a center frequency offset of LTE PRBs for even and odd system bandwidths.

[0045] FIG. 3 illustrates an adjacent LTE PRB for guard band operation in 10 MHz LTE system bandwidth.

[0046] FIG. 4 illustrates eMTC SIBbis transmission with no PRB reserved for NB-IoT according to an embodiment of the disclosed subject matter.

[0047] FIG. 5 illustrates eMTC SIBbis transmission with PRB #22 reserved for NB-IoT, and narrowband #3 being treated as an invalid narrowband for SIBbis transmission according to an embodiment of the disclosed subject matter.

[0048] FIG. 6 illustrates eMTC SIBbis transmission with PRB #22 reserved for NB-IoT, with narrowband #3 being treated as a valid narrowband for SIBbis transmission and PRB #22 puncturing SIB Ibis transmission according to an embodiment of the disclosed subject matter.

[0049] FIG. 7 illustrates a communication network according to an embodiment of the disclosed subject matter.

[0050] FIG. 8 illustrates a wireless communication device according to an embodiment of the disclosed subject matter.

[0051] FIG. 9 illustrates a radio access node according to an embodiment of the disclosed subject matter.

[0052] FIG. 10 illustrates a method according to an embodiment of the disclosed subject matter.

DETAILED DESCRIPTION

[0053] The following description presents various embodiments of the disclosed subject matter. These embodiments are presented as teaching examples and are not to be construed as limiting the scope of the disclosed subject matter. For example, certain details of the described embodiments may be modified, omitted, or expanded upon without departing from the scope of the described subject matter.

[0054] In the description that follows, certain embodiments are described with respect to eMTC and related terminology. The described concepts, however, are not limited to eMTC technology. Additionally, the general term "MTC" may be used to refer to any version of MTC technology, including e.g. MTC as defined in 3GPP specifications prior to Release 13, as well as eMTC as defined in Release 13 and onward.

[0055] In conventional approaches, the specified scheduling in the frequency domain of the system information transmission for eMTC prevents NB-IoT from being efficiently supported on the same LTE carrier. The PRBs that are suitable for NB-IoT transmission collide with PRBs that are used for SIB Ibis transmission to eMTC UEs in some cells unless the network planning is arranged such that the PCIDs that cause collision are avoided altogether but this may not be an efficient and practical solution. Similar collision exists for other broadcast type of signal whose narrowbands are determined as a function of PCID, for example, paging transmission.

[0056] In recognition of at least the above considerations, in certain embodiments of the disclosed subject matter, within the system information transmission for eMTC, one or more physical resource blocks (PRBs) are made available for NB-IoT so that eMTC and NB-IoT can coexist efficiently on the same LTE carrier. Similar design can be applied to paging transmission as well. These and other embodiments can allow NB-IoT and eMTC to coexist efficiently on the same LTE carrier.

[0057] In certain embodiments described below, simultaneous support for eMTC and NB-IoT in a cell is enabled by allowing eNB to arrange downlink transmissions so that collision is avoided between PRBs suitable for NB-IoT deployment and PRBs used for eMTC transmission.

[0058] In various alternative embodiments, NB-IoT PRB may be restricted to certain PRB locations in the system BW, or they may be located at any PRB in the system BW. In the description that follows, these two situations are referred to as Case 1 and Case 2, respectively.

Case 1. NB-IoT PRB can only reside on certain PRB locations in the system BW.

[0059] The NB-IoT PRB contains NB-PBCH, NB-PSS and NB-SSS to ensure that the NB- IoT PRB can be used as anchor PRB if necessary. Only the (relatively few) PRBs that fulfill the criterion that they have 2.5 kHz or 7.5 kHz frequency offset compared to the 100-kHz channel raster can be used as anchor PRBs. In this case, for a given NB-IoT UE, one PRB has to be reserved for the NB-IoT traffic. For all the NB-IoT UEs in the cell, several PRBs can be reserved, with each PRB serving a different group of NB-IoT UEs.

[0060] To ensure that this NB-IoT PRB(s) does not collide with an eMTC SIB Ibis transmission, one of the following methods is used:

1) Predefine one or more 6-PRB narrowbands as invalid for SIB Ibis transmission. One or more PRB(s) in the predefined narrowbands can then be used by NB-IoT UEs. In this method, the invalid narrowbands are fixed and not reconfigurable. While it saves signaling overhead, it has the drawback of inflexibility.

2) Configure one or more PRBs as invalid for SIB Ibis transmission.

3) Configure one or more narrowbands as invalid for SIB Ibis transmission.

[0061] One of these methods can also be used for avoiding a similar risk for collision between NB-IoT anchor PRB and transmission related to paging of eMTC UEs.

[0062] In the following we focus on the second method, i.e. the configuration method, for the SIB Ibis case.

[0063] In one embodiment, one of the unused spare bits in MIB is used for indicating that an eMTC UE can assume that a known PRB or set of PRBs will NOT contain any SIB Ibis transmission. In an affected 6-PRB narrowband, the eMTC UE will only take the remaining (5) PRBs into account when receiving SIB Ibis transmission. The same principle can also be applied to other transmissions than SIB Ibis, although a more practical solution may be to simply avoid scheduling those transmissions in the affected PRB(s).

[0064] In another embodiment, instead of using unused spare bits in MIB, we use the unused combinations of the 5 bits in MIB that are used for SIB Ibis scheduling information (TBS and R). There are 32-19=13 unused combinations that can be used. One example of an extended mapping table is shown in Table 3A. In this example we have chosen to still support all six TBS values but only two of the R values (4 and 8 but not 16) and keep one value reserved.

[0065] When "Value" is in the range of 19-30, eNB indicates: yes, "One or more PRBs configured as invalid for SIB Ibis transmission to allow NB-IoT transmission in those PRB(s)". Then the predefined one or more PRBs are understood to be invalid for eMTC. The predefined configuration provides the indices of the invalid PRBs.

[0066] One example of the predefined rule is based on odd vs even number of PRBs in the system BW: • if the system BW contains even number of PRBs, then PRB of index 2 is reserved for NB-IoT and unusable by eMTC traffic.

• if the system BW contains even number of PRBs, then PRB of index 4 is reserved for NB-IoT and unusable by eMTC traffic.

[0067] Another example of the predefined rule is based on defining a table of PRB indices for each applicable system BW. For example, Table 3B. Note that while Table 3B uses PRB indices, it is possible to define narrowband indices, as in "narrowbands reserved for NB-IoT".

Table 3 A: SIB Ibis scheduling information in MIB

Table 3B

[0068] In yet another method, one or more reserved bits in MIB are used to signal the PRB(s) used for NB-IoT.

• In the frequency hopping pattern of SIB Ibis, narrowbands containing the NB-IoT PRB(s) are then treated as invalid narrowbands for SIB Ibis, and excluded from the frequency hopping pattern.

• The MIB bits can indicate:

o Existence or not of NB-IoT PRBs;

o Number of PRBs for NB-IoT;

o PRB indices reserved for NB-IoT;

[0069] A table using 3 reserved MIB bits is illustrated in Table 4. Note that while Table 4 uses PRB indices, it is possible to define narrowband indices, as in "narrowbands reserved for NB-IoT". Table 4

[0070] Note that any PRBs (or narrowbands) indicated as "reserved for NB-IoT" in MIB are then treated by eMTC (UE as well as eNB) as unavailable for eMTC transmission. Either puncturing or rate matching can be applied to avoid the "reserved for NB-IoT" PRBs (or narrowbands).

Case 2. NB-IoT PRB can be any PRB in the system BW.

[0071] This is possible when the NB-IoT system is able to operate in the multi-PRB manner, where 2 or more PRBs are used in combination to support NB-IoT UEs.

[0072] One PRB is the anchor PRB. Anchor PRB contains NB-PBCH, NB-PSS, NB-SSS. Thus the UE can perform cell search and cell attachment via the anchor PRB. The anchor PRB resides in the guard band.

[0073] Another PRB is the secondary PRB. The secondary PRB does not have to contain NB-PBCH, NB-PSS, NB-SSS, although it is allowed to. Thus secondary PRB can use any PRB in band.

[0074] As discussed, the secondary PRB can be any PRB in the LTE system bandwidth. Thus it can use any one of the PRB unused by MTC narrowbands at the cell edge. This setup has the benefit that no changes or limitations or signaling are required of the eMTC UEs. The only technique is to allocate the secondary PRBs to a few eligible PRBs. The eligible PRBs are illustrated in Table 5.

Table 5. Indices of PRBs usable as a secondary PRB in a multi-PRB setup ofNB-IoT LTE system BW Indices of PRBs usable as Comment (MHz) secondary PRB

3 0, 14 One lowest indexed, and one highest indexed PRB in the system BW

5 N/A

10 0, 49 One lowest indexed, and one highest indexed PRB in the system BW

15 0, 74 One lowest indexed, and one highest indexed PRB in the system BW

20 0, 1, 98, 99 Two lowest indexed, and two highest indexed PRB in the system BW

Processing ofPRB(s) reserved for NB-IoT.

[0075] FIG. 4 illustrates a normal SIB Ibis transmission where SIB Ibis is transmitted in two configured narrowbands. In other words, FIG. 4 illustrates eMTC SIBbis transmission with no PRB reserved for NB-IoT. FIG. 5 illustrates eMTC SIBbis transmission with PRB #22 reserved for NB-IoT, and narrowband #3 being treated as invalid narrowband for SIBbis transmission. FIG. 6 illustrates eMTC SIBbis transmission with PRB #22 reserved for NB- IoT. Narrowband #3 is treated as valid narrowband for SIBbis transmission, but PRB #22 punctures SIB Ibis transmission.

[0076] Referring to FIGS. 5 and 6, the PRB(s) reserved for NB-IoT can be processed at least with two options. In a first option shown in FIG. 5, eMTC SIBbis transmission with PRB(s) reserved for NB-IoT, and the corresponding narrowband is treated as invalid narrowband for SIBbis transmission. Both eNodeB and the eMTC UE are award the SIBbis transmission avoids the narrowband(s) that contain the PRB(s) reserved for NB-IoT. In a second option illustrated in FIG. 6, eMTC SIBbis transmission with PRB(s) reserved for NB-IoT, and the corresponding Narrowband is still treated as valid narrowband for SIBbis transmission, but the PRB(s) reserved for NB-IoT punctures SIB Ibis transmission. The UE should be aware of the location of the PRB(s) reserved for NB-IoT, so that the eMTC UE can take the puncturing into account in its receiver. That is, the eMTC UE discard the symbols transmitted over the PRB(s) reserved for NB-IoT.

[0077] The described embodiments may be implemented in any appropriate type of communication system supporting any suitable communication standards and using any suitable components. As one example, certain embodiments may be implemented in an LTE network, such as that illustrated in FIG. 7.

[0078] FIG. 7 illustrates a communication network 700 according to an embodiment of the disclosed subject matter.

[0079] Referring to FIG. 7, a communication network 700 comprises a plurality of wireless communication devices 705 (e.g., conventional UEs, machine type communication [MTC] / machine-to-machine [M2M] UEs) and a plurality of radio access nodes 710 (e.g., eNodeBs or other base stations). Communication network 700 is organized into cells 715, which are connected to a core network 720 via corresponding to radio access nodes 710. Radio access nodes 710 are capable of communicating with wireless communication devices 705 along with any additional elements suitable to support communication between wireless communication devices or between a wireless communication device and another communication device (such as a landline telephone).

[0080] Although wireless communication devices 705 may represent communication devices that include any suitable combination of hardware and/or software, these wireless communication devices may, in certain embodiments, represent devices such as an example wireless communication device illustrated in greater detail by FIG. 8. Similarly, although the illustrated radio access node may represent network nodes that include any suitable combination of hardware and/or software, these nodes may, in particular embodiments, represent devices such as the example radio access node illustrated in greater detail by FIG. 9.

[0081] FIG. 8 illustrates a wireless communication device 800 according to an embodiment of the disclosed subject matter.

[0082] Referring to FIG. 8, a wireless communication device 800 comprises a processor 805, a memory, a transceiver 815, and an antenna 820. In certain embodiments, some or all of the functionality described as being provided by UEs, MTC or M2M devices, and/or any other types of wireless communication devices may be provided by the device processor executing instructions stored on a computer-readable medium, such as the memory shown in FIG. 8. Alternative embodiments may include additional components beyond those shown in FIG. 8 that may be responsible for providing certain aspects of the device's functionality, including any of the functionality described herein.

[0083] FIG. 9 illustrates a radio access node 900 according to an embodiment of the disclosed subject matter.

[0084] Referring to FIG. 9, a radio access node 900 comprises a node processor 905, a memory 910, a network interface 915, a transceiver 920, and an antenna 925. In certain embodiments, some or all of the functionality described as being provided by a base station, a node B, an enodeB, and/or any other type of network node may be provided by node processor 905 executing instructions stored on a computer-readable medium, such as memory 910 shown in FIG. 9. Alternative embodiments of radio access node 900 may comprise additional components to provide additional functionality, such as the functionality described herein and/or related supporting functionality.

[0085] FIG. 10 is a flowchart illustrating a method 1000 of operating a radio access node or a wireless communication device according to an embodiment of the disclosed subject matter. The method could be performed, for instance, by a radio access node or wireless

communication device such as those illustrated in any of FIGS. 7-9.

[0086] Referring to FIG. 10, the method comprises identifying a subset of PRBs within an LTE system bandwidth that are eligible for use as narrowband internet of things, NB-IoT, PRBs, wherein the eligibility of PRBs for use as NB-IoT PRBs is determined in relation to at least one machine-type-communication, MTC, narrowband within the LTE system bandwidth (S1005). In some embodiments, the eligibility of a PRB for use as an NB-IoT PRB is determined according to whether the PRBs is reserved for use as an NB-IoT PRB, to the exclusion of MTC narrowbands. The method further comprises transmitting or receiving information via at least one of the eligible PRBs that has been allocated as a NB-IoT PRB, or via the at least one MTC narrowband (S1010). For instance, a NB-IoT device may transmit or receive information using the eligible PRBs, or an eMTC device may transmit or receive information using the at least one MTC narrowband.

[0087] In some embodiments, the at least one MTC narrowband comprises an MTC narrowband to be used for transmission of System Information Block 1, SIBlbis. In certain alternative embodiments, the at least one MTC narrowband comprises an MTC narrowband to be used for transmission of paging-related information.

[0088] In some embodiments, identifying the eligible PRBs comprises predefining at least one 6-PRB narrowband as invalid for transmission of System Information Block 1, SIB lbis, and identifying at least one PRB within the predefined narrowbands as eligible for use as a NB-IoT PRB.

[0089] In some embodiments, identifying the eligible PRBs comprises identifying the eligible PRBs as eligible for use as secondary NB-IoT PRBs, and wherein the at least one of the eligible PRBs is allocated as at least one secondary NB-IoT PRB.

[0090] In some embodiments, the subset includes only one or more PRBs defined at the outermost edges of the LTE system bandwidth.

[0091] In some embodiments, identifying the eligible PRBs comprises identifying the eligible PRBs based on whether the LTE system bandwidth includes an odd or even number of PRBS and/or a size of the LTE system bandwidth.

[0092] In some embodiments, the method still further comprises transmitting or receiving configuration signaling indicating whether PRBs identifiable according to a predefined rule are reserved for use as NB-IoT PRBs. The configuration signaling may comprise e.g.

particular combinations of values for a set of bits that also indicates scheduling information for a System Information Block 1, SIB Ibis.

[0093] In some embodiments, the method still further comprises transmitting or receiving configuration signaling indicating which PRBs within the LTE system bandwidth are reserved for use as NB-IoT PRBs.

[0094] In some embodiments, the method still further comprises transmitting or receiving MTC information via the at least one MTC narrowband, by performing puncturing or rate matching to avoid transmission or reception of the MTC information via the at least one of the eligible PRBs allocated as a NB-IoT PRB. In some embodiments, the method still further comprises transmitting or receiving system information or paging -related information via the at least one MTC narrowband according to a frequency hopping pattern which is modified to exclude the at least one of the eligible PRBs allocated as a NB-IoT PRB. In some embodiments, the method still further comprises determining, based on a cell identity of a cell in which MTC information is to be transmitted, one or more MTC narrowbands via which to transmit the MTC information, and transmitting or receiving the MTC information via the one or more MTC narrowbands, except for the subset of PRBs identified as eligible for use as NB-IoT PRBs. In some embodiments, the MTC information comprises system information or paging-related information for an MTC system.

[0095] In some embodiments, the subset of PRBs within the LTE system bandwidth that are eligible for use as NB-IoT PRBs are PRBs that are reserved for use as NB-IoT PRBs. [0096] In some embodiments, the method still further comprises allocating the at least one of the eligible PRBs as NB-IoT PRBs.

[0097] In some embodiments, the method of FIG. 10 may be implemented in an apparatus that comprises at least one processor and at least one transmitter or receiver collectively configured to perform the indicated functions. For instance, the at least one processor may be configured to identify a subset of physical resource blocks, PRBs, within a Long Term Evolution, LTE, system bandwidth that are eligible for use as narrowband internet of things, NB-IoT, PRBs, wherein the eligibility of PRBs for use as NB-IoT PRBs is determined in relation to at least one machine-type-communication, MTC, narrowband within the LTE system bandwidth. The at least one transmitter or receiver may be configured to transmit or receive information via at least one of the eligible PRBs that has been allocated as a NB-IoT PRB, or via the at least one MTC narrowband. Such an apparatus may be, for instance, a base station or a UE. More generally, the apparatus may include any means for performing the indicated functions, such as a means for identifying a subset of physical resource blocks, PRBs, within a Long Term Evolution, LTE, system bandwidth that are eligible for use as narrowband internet of things, NB-IoT, PRBs, wherein the eligibility of PRBs for use as NB- IoT PRBs is determined in relation to at least one machine-type-communication, MTC, narrowband within the LTE system bandwidth; and means for transmitting or receiving information via at least one of the eligible PRBs that has been allocated as a NB-IoT PRB, or via the at least one MTC narrowband. Such means may include, for instance, at least one processor and at least one transmitter or receiver as described above. More generally, such means may include any suitable combination of hardware and/or software capable of performing the indicated functions. Such hardware may include e.g. various forms of general purpose or application specific integrated circuits, field programmable gate arrays (FPGAs), and other forms of electronic circuitry.

[0098] In still other embodiments, the method of FIG. 10 may be implemented using a computer program comprising instructions which, when executed by at least one processor of a radio access node or wireless communication device, causes the radio access node or wireless communication device to perform the method. In still other embodiments, the method of FIG. 10 may be implemented using a non-transitory computer-readable medium, having stored thereon a computer program which, when executed by at least one processor of a radio access node or wireless communication device, causes the radio access node or wireless communication device to identify a subset of physical resource blocks, PRBs, within a Long Term Evolution, LTE, system bandwidth that are eligible for use as narrowband internet of things, NB-IoT, PRBs, wherein the eligibility of PRBs for use as NB-IoT PRBs is determined in relation to at least one machine-type-communication, MTC, narrowband within the LTE system bandwidth, and transmit or receive information via the at least one of the eligible PRBs that has been allocated as a NB-IoT PRB, or via the at least one MTC narrowband.

[0099] The following abbreviations may be used in this description.

NB Narrow band

NB-IoT Narrowband Internet of Things

MTC Machine Type Communications

PSS Primary Synchronization Sequence

sss Secondary Synchronization Sequence

SIM Subscriber Identity Module or Subscriber Identification Module

CRC Cyclic Redundancy Check

NB-PSS NB-IoT Primary Synchronization Sequence

NB-SSS NB-IoT Secondary Synchronization Sequence

LTE Long Term Evolution

DFT Discrete Fourier Transform

IFFT Inverse fast fourier transform

CRS Cell Specific Reference Signals

PDCCH Physical Data Control Channel

CP Cyclic prefix

FDD Frequency-division duplex

TDD Time-division duplex

NB-PBCH NB-IoT Physical Broadcast Channel

SNR signal to noise ratios

OFDM Orthogonal frequency-division multiplexing

ZC Zadoff-Chu

CSS common search space (CSS)

USS UE-specific search space (USS)

[00100] While the disclosed subject matter has been presented above with reference to various embodiments, it will be understood that various changes in form and details may be made to the described embodiments without departing from the overall scope of the disclosed subject matter.