Patent Description:
Aspects of the present disclosure generally relate to wireless communication, and more particularly to techniques and apparatuses for enhanced machine-type communication (eMTC) coexistence between radio access technologies (RATs).

As will be described in more detail herein, a BS may be referred to as a Node B, a gNB, an access point (AP), a radio head, a transmit receive point (TRP), a <NUM> BS, a <NUM> Node B, and/or the like.

The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless communication devices to communicate on a municipal, national, regional, and even global level. <NUM>, which may also be referred to as New Radio (NR), is a set of enhancements to the LTE mobile standard promulgated by the Third Generation Partnership Project (3GPP). <NUM> is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink (DL), using CP-OFDM and/or SC-FDM (e.g., also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink (UL), as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. However, as the demand for mobile broadband access continues to increase, there exists a need for further improvements in LTE and <NUM> technologies. <CIT> describes operation in an environment with two different radio access technologies. <CIT> describes coexistence of narrow-band internet-of-things/enhanced machine type communication and <NUM>. <CIT> describes user terminal, radio base station, and radio communication method.

Enhanced machine-type communication (eMTC) is a framework for low-power and wide-area communication between UEs, such as UEs associated with Internet of Things (IoT) devices. In an LTE deployment, eMTC can be deployed in the LTE spectrum and coexist with other LTE services within the same bandwidth. The eMTC UE may communicate within a bandwidth corresponding to a narrowband of six consecutive physical resource blocks (PRBs), and may switch the narrowband between subframes (i.e., may perform frequency hopping between narrowbands). The LTE primary synchronization signal (PSS), secondary synchronization signal (SSS), and physical broadcast channel (PBCH) may be confined within the narrowband by design, and thus may be reused by LTE eMTC for cell acquisition. The information for a system information block <NUM>-bandwidth reduced (BR) (SIB1-BR) (e.g., transport block size, repetition pattern, etc.) may be signaled in a master
information block (MIB) of the PBCH. In that case, the SIB1-BR may include scheduling information for the remaining system information blocks (SIBs) that are relevant for eMTC UEs.

Some eMTC devices may be deployed in a <NUM> band (e.g., in a <NUM> carrier that includes an LTE bandwidth). For example, these eMTC devices may include legacy devices (e.g., LTE eMTC devices) and devices that can use more flexible bandwidth and resource allocations (e.g., <NUM> eMTC devices). There may be a tradeoff regarding the bandwidth of the LTE cell in which the eMTC UE operates. For example, with a larger bandwidth, more UEs can be scheduled, and frequency diversity may be improved due to frequency hopping. With a smaller bandwidth, it may be easier to handle coexistence with <NUM>, with or without frequency hopping. For example, the cell-specific reference signal bandwidth can be smaller with a smaller bandwidth, thereby using less resources of the <NUM> carrier.

Some techniques and apparatuses described herein allocate and/or transmit a narrower bandwidth value for LTE MTC UEs, such as UEs that operate in a small bandwidth mode (e.g., <NUM>, <NUM>, <NUM>, and/or the like) using LTE procedures, and allocate and/or transmit a wider bandwidth value for <NUM> MTC UEs, such as UEs that can perform hopping and/or use resources outside of a legacy bandwidth. For example, the wider bandwidth value may be associated with a non-LTE carrier (e.g., a <NUM> carrier in a <NUM> bandwidth) with the same center frequency as an LTE carrier associated with the narrower bandwidth value. Some techniques and apparatuses described herein provide for initial access, signaling, paging, random access, unicast communications, frequency hopping, cell-specific reference signaling, narrowband alignment, and/or other coexistence considerations for LTE MTC UEs operating on an LTE carrier and <NUM> MTC UEs operating on a non-LTE carrier with a bandwidth that includes the LTE carrier. Thus, coexistence of LTE MTC UEs and <NUM> MTC UEs is provided in a <NUM> band that includes an LTE carrier for the LTE MTC UEs.

In an aspect of the disclosure, a method, a UE (e.g., an MTC UE), a base station, an apparatus, and a computer program product are provided.

In some aspects, the method may by performed by a base station. The method may include transmitting a bandwidth value for an MTC UE, wherein the bandwidth value is a first bandwidth value when the MTC UE is configured to use a first carrier associated with a first radio access technology, and wherein the bandwidth value is a second bandwidth value when the MTC UE is configured to use a second carrier associated with a second radio access technology; and communicating with the MTC UE using the bandwidth value.

In some aspects, the base station may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to transmit a bandwidth value for an MTC UE, wherein the bandwidth value is a first bandwidth value when the MTC UE is configured to use a first carrier associated with a first radio access technology, and wherein the bandwidth value is a second bandwidth value when the MTC UE is configured to use a second carrier associated with a second radio access technology; and communicate with the MTC UE using the bandwidth value.

In some aspects, the apparatus may include means for transmitting a bandwidth value for an MTC UE, wherein the bandwidth value is a first bandwidth value when the MTC UE is configured to use a first carrier associated with a first radio access technology, and wherein the bandwidth value is a second bandwidth value when the MTC UE is configured to use a second carrier associated with a second radio access technology; and means for communicating with the MTC UE using the bandwidth value.

In some aspects, the computer program product may include a non-transitory computer-readable medium storing one or more instructions. The one or more instructions, when executed by one or more processors of a base station, may cause the one or more processors to transmit a bandwidth value for an MTC UE, wherein the bandwidth value is a first bandwidth value when the MTC UE is configured to use a first carrier associated with a first radio access technology, and wherein the bandwidth value is a second bandwidth value when the MTC UE is configured to use a second carrier associated with a second radio access technology; and communicate with the MTC UE using the bandwidth value.

In some aspects, the method may by performed by an MTC UE. The method may include receiving information identifying a bandwidth value for the MTC UE, wherein the bandwidth value is a first bandwidth value when the MTC UE is configured to use a first carrier associated with a first radio access technology, and wherein the bandwidth value is a second bandwidth value when the MTC UE is configured to use a second carrier associated with a second radio access technology; and communicating using the bandwidth value.

In some aspects, the MTC UE may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to receive information identifying a bandwidth value for the MTC UE, wherein the bandwidth value is a first bandwidth value when the MTC UE is configured to use a first carrier associated with a first radio access technology, and wherein the bandwidth value is a second bandwidth value when the MTC UE is configured to use a second carrier associated with a second radio access technology; and communicate using the bandwidth value.

In some aspects, the apparatus may include means for receiving information identifying a bandwidth value for the apparatus, wherein the bandwidth value is a first bandwidth value when the apparatus is configured to use a first carrier associated with a first radio access technology, and wherein the bandwidth value is a second bandwidth value when the apparatus is configured to use a second carrier associated with a second radio access technology; and means for communicating using the bandwidth value.

In some aspects, the computer program product may include a non-transitory computer-readable medium storing one or more instructions. The one or more instructions, when executed by one or more processors of an MTC UE, may cause the one or more processors to receive information identifying a bandwidth value for the MTC UE, wherein the bandwidth value is a first bandwidth value when the MTC UE is configured to use a first carrier associated with a first radio access technology, and wherein the bandwidth value is a second bandwidth value when the MTC UE is configured to use a second carrier associated with a second radio access technology; and communicate using the bandwidth value.

Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, wireless communication device, and processing system as substantially described herein with reference to and as illustrated by the accompanying drawings and specification.

The network <NUM> may be an LTE network or some other wireless network, such as a <NUM> network. A BS is an entity that communicates with user equipment (UEs) and may also be referred to as a base station, a <NUM> BS, a Node B, a gNB, a <NUM> NB, an access point, a transmit receive point (TRP), and/or the like.

The terms "eNB", "base station", "5GBS", "gNB", "TRP", "AP", "node B", "5GNB", and "cell" may be used interchangeably herein.

A UE may also be referred to as an access terminal, a terminal, a mobile station, a subscriber unit, a station, etc. A UE may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, a biometric sensor or device, a wearable device (smart watches, smart clothing, smart glasses, smart wrist bands, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device, or a satellite radio), a vehicular component or sensor, smart meters/sensors, industrial manufacturing equipment, a global positioning system device, or any other suitable device that is configured to communicate via a wireless or wired medium.

MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., that may communicate with a base station, another device (e.g., remote device), or some other entity.

An LTE MTC UE is an MTC UE that operates only within an LTE bandwidth following legacy procedures. For example, frequency hopping, signaling, scheduling, etc. for an LTE MTC UE may be confined to the LTE bandwidth. A <NUM> MTC UE is a UE that can use more flexible bandwidth and resource allocations than an LTE MTC UE outside an LTE bandwidth. For example, a <NUM> MTC UE may be capable of frequency hopping, scheduling, and communicating data outside of the LTE bandwidth. In some aspects, the larger bandwidth may be associated with a non-LTE carrier (e.g., a <NUM> carrier or another type of carrier) with the same center frequency as the LTE carrier.

Some UEs may be considered Internet-of Things (IoT) devices, and/or may be implemented as may be implemented as NB-IoT (narrowband internet of things) devices.

Transmit processor <NUM> may also process system information (e.g., for semi-static resource partitioning information (SRPI), and/or the like) and control information (e.g., CQI requests, grants, upper layer transmitting, and/or the like) and provide overhead symbols and control symbols.

A receive (RX) processor <NUM> may process (e.g., demodulate and decode) the detected symbols, provide decoded data for UE <NUM> to a data sink <NUM>, and provide decoded control information and system information to a controller/processor <NUM>.

Controller/processor <NUM> of base station <NUM>, controller/processor <NUM> of UE <NUM>, and/or any other component(s) of <FIG> may perform one or more techniques associated with eMTC operation on a non-LTE bandwidth, as described in more detail elsewhere herein. For example, controller/processor <NUM> of base station <NUM>, controller/processor <NUM> of UE <NUM>, and/or any other component(s) of <FIG> may perform or direct operations of, for example, method <NUM> of <FIG>, method <NUM> of <FIG>, and/or other processes as described herein. Memories <NUM> and <NUM> may store data and program codes for BS <NUM> and UE <NUM>, respectively.

<FIG> and <FIG> are diagrams illustrating an example <NUM> of configuration of legacy and <NUM> MTC UEs to operate in a <NUM> carrier. As shown, <FIG> and <FIG> depict a BS <NUM> and a <NUM> MTC UE <NUM>. Some of the operations described in <FIG> and <FIG> are applicable for <NUM> MTC UEs <NUM> and LTE MTC UEs <NUM>, whereas other operations described in <FIG> and <FIG> are applicable only for <NUM> MTC UEs <NUM> (e.g., and not LTE MTC UEs <NUM>). A more detailed description of such alternatives is provided below.

As shown in <FIG>, and by reference number <NUM>, a BS <NUM> may transmit a bandwidth value for the <NUM> MTC UE <NUM>. The bandwidth value may be a first bandwidth value for an LTE MTC UE <NUM>, and may be a second bandwidth value for a <NUM> MTC UE <NUM>. For example, the first bandwidth value may correspond to a first carrier associated with a first RAT, such as an LTE carrier or bandwidth (e.g., a small bandwidth value). In some aspects, the first bandwidth value may correspond to a small bandwidth of a narrowband, such as <NUM>, <NUM>, <NUM>, and/or the like. In this way, a smaller bandwidth is provided for LTE MTC UEs <NUM> than for <NUM> MTC UEs <NUM>.

In some aspects, the second bandwidth value may correspond to a second carrier with a bandwidth that is wider than the LTE carrier or bandwidth (e.g., with a large number of narrowbands, which may be associated with a second RAT, such as a <NUM> carrier or band), and/or which may include the LTE carrier or bandwidth. Refer to <FIG> for examples of the first carrier (e.g., LTE carrier or bandwidth) and the second carrier. In some aspects, the second bandwidth value may be selected from a set of bandwidths. As just one example, the second bandwidth value may be selected from the set of {<NUM><NUM><NUM><NUM>} MHz. In such a case, the signaling for the bandwidth value may include one or more bits that indicate which bandwidth value, of the set, is to be used for the <NUM> MTC UE <NUM>.

In some aspects, the BS <NUM> may transmit a bandwidth of the second carrier, and the <NUM> MTC UE <NUM> may determine the second bandwidth value based at least in part on a center frequency of the first carrier and the bandwidth. For example, the second carrier may be centered with the first carrier, so the <NUM> MTC UE <NUM> may determine the second bandwidth value (and the second carrier) according to the bandwidth and the center frequency. In some aspects, the BS <NUM> may explicitly signal narrowbands outside of the first carrier to identify the second carrier. For example, the narrowbands outside of the first carrier may not be centered on the first carrier. In such a case, the BS <NUM> may provide information identifying a starting physical resource block (PRB) index and the length of a number of consecutive PRBs. In some aspects, the PRB numbering may be common between LTE and <NUM>, independent of the signaled bandwidth of the second carrier. For example, the numbers for both the LTE and <NUM> carrier may be based at least in part on a <NUM> LTE system bandwidth that is centered on the first carrier irrespective of whether the bandwidth of the second carrier is <NUM>. In some aspects, the BS <NUM> may transmit a bandwidth of the second carrier based at least in part on a <NUM> signaling approach. For example, the BS <NUM> may transmit an NR carrier bandwidth, a PRB numbering, and a center frequency, according to the <NUM> signaling approach. The <NUM> MTC UE <NUM> may identify the second carrier based at least in part on the NR carrier bandwidth, the PRB number, and the center frequency.

As shown by reference number <NUM>, the BS <NUM> may signal the bandwidth value for LTE MTC UEs <NUM> using a MIB. This may be advantageous because the MIB may occur within the narrower bandwidth (e.g., the LTE carrier or bandwidth). As further shown, the BS <NUM> may signal the bandwidth value for <NUM> MTC UEs <NUM> using a MIB (e.g., within the LTE carrier or bandwidth) or a SIB <NUM>-BR. For example, the MIB or the SIB1-BR may include the one or more bits described above to indicate which second bandwidth value is to be used for the <NUM> MTC UE <NUM>.

As shown by reference number <NUM>, the BS <NUM> may perform initial access according to the bandwidth value. For example, the UE <NUM> may perform initial access according to the bandwidth value. Initial access may include transmission/reception of a PSS/SSS/PBCH, a SIB <NUM>-BR, and/or other SIBs. In some aspects, the PSS, SSS, and/or PBCH may be transmitted in the first carrier, which may provide access to the PSS, SSS, and/or PBCH for LTE MTC UEs <NUM> and <NUM> MTC UEs <NUM>. In some aspects, the PSS, SSS, and/or PBCH may follow a frequency hopping configuration. For example, the frequency hopping may be performed within the first carrier.

In some aspects, the SIB <NUM>-BR may be transmitted in the first carrier. For example, the SIB <NUM>-BR may follow a frequency hopping configuration that is confined within the first carrier.

In some aspects, the BS <NUM> may transmit one or more repetitions of the SIB <NUM>-BR outside of the first carrier, and the <NUM> MTC UE <NUM> may receive the one or more repetitions of the SIB1-BR outside of the first carrier. For example, the BS <NUM> may transmit the one or more repetitions in the second carrier. In some aspects, the one or more repetitions may be used when the first carrier has a bandwidth of <NUM> or <NUM>, since only a repetition factor of <NUM> may be supported for SIB <NUM>-BR transmission in such bandwidths.

In some aspects, the one or more repetitions of the SIB <NUM>-BR may be signaled using the MIB. For example, the total number of subframes for the additional SIB1-BR transmission may be indicated by <NUM> bits in the MIB. As an example, a first bit value (e.g., <NUM>) may indicate no additional SIB1-BR; a second bit value (e.g., <NUM>) may indicate the same repetition scheme as that of a legacy (e.g., LTE) SIB1-NB transmission (e.g. <NUM> subframes per <NUM> SIB <NUM>-BR periodicity); a third bit value (e.g., <NUM>) may indicate two times that of the legacy SIB <NUM>-NB transmission (e.g. <NUM> subframes per <NUM> SIB <NUM>-BR periodicity); and a fourth bit value (e.g., <NUM>) may indicate four times that of the legacy SIB1-NB transmission (e.g. <NUM> subframes per <NUM> SIB1-BR periodicity). The above is provided as just one example and other examples are contemplated.

In some aspects, the subframe and radio frame location of the one or more repetitions may be based at least in part on the total number of subframes used for the one or more repetitions. As one example, a particular subframe (e.g., subframe #<NUM>) may be used for frequency division duplexing in the case of <NUM> repetitions outside of the second carrier.

In some aspects, the one or more repetitions of the SIB1-BR may be transmitted on two narrowbands adjacent to the first carrier (e.g., the LTE carrier) that do not overlap with the center <NUM> subcarriers. If the additional bandwidth for the second carrier is not signaled in the MIB, then the frequency location of the two narrowbands (e.g., expressed as an offset from a center frequency) may be indicated in the MIB (e.g., using a <NUM>-bit indicator in the MIB). The <NUM>-bit indicator in the MIB may indicate one of two sets of bandwidths. For example, the <NUM>-bit indicator may indicate whether a first set (e.g., {<NUM><NUM>} MHz) or a second set (e.g., {<NUM><NUM>} MHz) is to be used to determine the frequency locations of the two narrowbands.

In some aspects, the BS <NUM> may transmit one or more SIBs other than SIB <NUM>-BR. For example, an LTE MTC UE <NUM> or a <NUM> MTC UE <NUM> may receive the other SIB. As an example, the BS <NUM> may transmit at least legacy transmissions of essential SIBs in the first carrier. In some aspects, the BS <NUM> may schedule one or more repetitions of a SIB outside of the first carrier (e.g., in the second carrier), which may reduce the acquisition time for <NUM> MTC UEs. When the BS <NUM> schedules the one or more repetitions, the BS <NUM> may signal the one or more repetitions in SIB1 (e.g., SIB1-BR).

As shown by reference number <NUM>, the <NUM> MTC UE <NUM> may monitor paging on one or more narrowbands outside of an LTE carrier. For example, the one or more narrowbands may be included in the second carrier and not the first carrier. In some aspects, the <NUM> MTC UE <NUM> may monitor paging in the one or more narrowbands outside of the LTE carrier, or may monitor paging within the LTE carrier, based at least in part on information associated with the <NUM> MTC UE <NUM>, such as a UE identifier. In some aspects, an LTE MTC UE <NUM> may monitor paging in the first carrier. For example, the BS <NUM> may transmit a control channel (e.g., an MTC physical downlink control channel (MPDCCH)) for paging in the first carrier for the LTE MTC UE <NUM>.

As shown by reference number <NUM>, the <NUM> MTC UE <NUM> (and the BS <NUM>) may perform random access on one or more narrowbands outside of an LTE carrier according to the bandwidth value. For example, the BS <NUM> may signal one or more narrowbands (e.g., uplink and/or downlink narrowbands) to use for random access of the <NUM> MTC UE <NUM>. In some aspects, the one or more narrowbands may be within the first carrier or may be outside of the first carrier and within the second carrier. In some aspects, the LTE MTC UE <NUM> and the <NUM> MTC UE <NUM> may use a legacy approach for random access. For example, the LTE MTC UE <NUM> and the <NUM> MTC UE <NUM> may perform random access using the first carrier.

As shown by reference number <NUM>, the <NUM> MTC UE <NUM> may receive unicast signaling on the LTE carrier (e.g., the first carrier) or the wider carrier (e.g., the second carrier; the <NUM> carrier with a bandwidth outside of the LTE carrier) according to downlink control information (DCI). For example, unicast signaling may include a unicast MPDCCH that carries DCI to schedule resources for a unicast physical downlink shared channel (PDSCH). In some aspects, the <NUM> MTC UE <NUM> may receive the unicast MPDCCH outside of the first carrier and within the second carrier. In some aspects, the <NUM> MTC UE <NUM> may receive the unicast PDSCH on a narrowband that is within the first carrier, or that is outside of the first carrier and within the second carrier. In some aspects, the MPDCCH and the PDSCH may be on different carriers. For example, one may be received or transmitted on the first carrier and one may be received or transmitted on the second carrier. Refer to <FIG> for an example of unicast scheduling with regard to the first carrier and the second carrier.

As shown in <FIG>, and by reference number <NUM>, the BS <NUM> may configure frequency hopping for the <NUM> MTC UE <NUM> according to the bandwidth value. As shown by reference number <NUM>, the <NUM> MTC UE <NUM> may perform frequency hopping according to the configuration and/or the bandwidth value. In a first approach, the BS <NUM> may configure the frequency hopping based at least in part on a first narrowband index of the frequency hopping sequence. For example, if the first narrowband index is in the first carrier, then the BS <NUM> (and the <NUM> MTC UE <NUM>) may follow the legacy frequency hopping approach to perform hopping within the first carrier. If the first narrowband index is outside of the first carrier and in the second carrier, the BS <NUM> (and the <NUM> MTC UE <NUM>) may perform frequency hopping outside of the first carrier and within the second carrier. In a second approach, the BS <NUM> (and the <NUM> MTC UE <NUM>) may perform frequency hopping within the first carrier and the second carrier. For example, the BS <NUM> may hop from a first narrowband within the first carrier to a second narrowband outside of the first carrier. In some aspects, an LTE MTC UE <NUM> may perform frequency hopping according to a legacy behavior within the first carrier.

In some aspects, frequency hopping may be configured independently for the first carrier and the second carrier. For example, frequency hopping may be permitted outside of the first carrier and within the second carrier, and may not be permitted within the first carrier. In a case wherein frequency hopping is permitted within the first carrier and the second carrier, then a number of narrowbands over which the MPDCCH/PDSCH hops, and/or the narrowband offset between one narrowband and the next narrowband, may be different for the first carrier and the second carrier. Refer to <FIG> for examples of frequency hopping approaches for the first carrier and the second carrier.

As shown by reference number <NUM>, the BS <NUM> may transmit a demodulation reference signal (DMRS) for a PDSCH transmission on one or more narrowbands that are outside of the LTE carrier. As shown by reference number <NUM>, the <NUM> MTC UE <NUM> may receive the DMRS on the one or more narrowbands that are outside of the LTE carrier. For example, the BS <NUM> may transmit the DMRS without a CRS outside of the first carrier and within the second carrier. For example, the BS <NUM> may transmit the DMRS within a particular temporal range of a transmission (e.g., a set of subframes before and a set of subframes after the associated PDSCH transmission) for the <NUM> MTC UE <NUM>, or within a particular frequency range of a narrowband of the second carrier (e.g., within the <NUM> PRBs +/- <NUM> PRB), based at least in part on identifying one or more narrowbands outside of a bandwidth of the first carrier. In some aspects, the BS <NUM> may transmit the CRS outside of the first carrier and within the second carrier. For example, the BS <NUM> may transmit the CRS within a particular temporal range of a transmission (e.g., a set of subframes before and a few subframes after the associated PDSCH transmission) for the <NUM> MTC UE <NUM>, or within a particular frequency range of a narrowband of the second carrier (e.g., within the <NUM> PRBs +/- <NUM> PRB), based at least in part on identifying one or more narrowbands outside of a bandwidth of the first carrier. In this way, the BS <NUM> may provide a CRS for a PDSCH transmission to a <NUM> MTC UE <NUM> that operates outside of the bandwidth of the first carrier and within the bandwidth of the second carrier. In some aspects, the BS <NUM> may transmit the CRS within the first bandwidth for the LTE MTC UE <NUM>.

In some aspects, the BS <NUM> may transmit a CRS outside of the first carrier. For example, the BS <NUM> may transmit a CRS in a narrowband outside of the first carrier and within the second carrier to enable channel state information (CSI) feedback for the <NUM> MTC UE <NUM>. In some aspects, the BS <NUM> may transmit the CRS outside of the first carrier intermittently or periodically. In some aspects, the BS <NUM> may transmit the CRS outside of the first carrier with a reduced density on both frequency domain and time domain. In some aspects, the <NUM> MTC UE <NUM> may perform radio resource management (RRM) measurement in the first carrier using a CRS that is transmitted within the first carrier.

Other examples may differ from what is described with respect to <FIG> and <FIG>.

<FIG> is a diagram illustrating examples <NUM> of carrier bandwidths for a first carrier, associated with an LTE MTC UE, and a second carrier associated with a <NUM> MTC UE. Reference number <NUM> shows an example wherein the second carrier has a bandwidth value of <NUM>, and reference number <NUM> shows an example wherein the second carrier has a bandwidth value of <NUM>. As shown by reference numbers <NUM>, the first carrier in <FIG> is associated with a bandwidth value of <NUM>. Furthermore, the second carrier in each case is centered on the corresponding first carrier. As further shown, each second carrier includes multiple, different narrowbands. For example, the second carrier shown by reference number <NUM> includes <NUM> narrowbands, and the second carrier shown by reference number <NUM> includes <NUM> narrowbands.

In some aspects, the valid subframe configuration for the first carrier may be different than the valid subframe configuration for the second carrier. For example, the BS <NUM> may configure the valid subframe configuration for the first carrier and/or the second carrier, and/or may transmit information identifying the valid subframe configurations of the first carrier and/or the second carrier. In some aspects, the valid subframe configuration for the first carrier may have a temporal granularity of <NUM>, and the valid subframe configuration for the second carrier may have a temporal granularity of less than <NUM>. In some aspects, the valid subframe configuration for the second carrier may have a temporal granularity of <NUM>, <NUM>, or <NUM>. In some aspects, the physical downlink shared channel or physical uplink shared channel may be configured with <NUM> or more sets of valid subframe configurations and be indicated which set is to use for a particular transmission via <NUM> or more bits in MPDCCH. In some apects, the valid subframe configuration for the second carrier may include also a valid symbol configuration. In some aspects, the BS <NUM> may configure the valid symbol configuration for the second carrier to handle coexistence with <NUM>. In some aspects, a control region of the first carrier may be different than a control region of the second carrier. For example, the first carrier may have a control region of a first size (e.g., <NUM> symbols) and the second carrier may have a control region of a second size (e.g., <NUM> symbols).

<FIG> is a diagram illustrating an example <NUM> of scheduling and data communication for LTE MTC UEs and <NUM> MTC UEs. In <FIG>, the first carrier is denoted by reference number <NUM> (and shown as "LTE bandwidth within NR"). The second carrier is denoted by reference number <NUM> (and shown as "Additional bandwidth for <NUM> MTC UE"). As shown by reference number <NUM>, a MPDCCH and PDSCH for a legacy UE (e.g., an LTE MTC UE) within the NR bandwidth may be provided in the first carrier. As shown by reference number <NUM>, in some aspects, an MPDCCH and/or a PDSCH for a <NUM> MTC UE may be provided in the first carrier and/or in the second carrier. In other words, the control channel and data channel for the <NUM> MTC UE may be provided in different carriers, of the first carrier and the second carrier.

<FIG> is a diagram illustrating an example <NUM> of frequency hopping for LTE MTC UEs and <NUM> MTC UEs. As shown in <FIG>, and by reference number <NUM>, in some aspects, frequency hopping for an LTE MTC UE may be confined to the first carrier (e.g., the LTE bandwidth or the first carrier). As shown by reference number <NUM>, in some aspects, frequency hopping for a <NUM> MTC UE may not be confined to the first carrier or the second carrier. For example, some frequency hops may occur within the first carrier (e.g., a first two frequency hops of UE1) and other frequency hops may occur outside of the first carrier (e.g., a last two frequency hops of UE1). As shown by reference number <NUM>, according to the invention, frequency hopping for a <NUM> MTC UE is confined to the carrier in which a first frequency hop occurred. For example, the frequency hops of UE1 shown in connection with reference number <NUM> are confined to the first carrier, and the frequency hops of UE2 shown in connection with reference number <NUM> are confined to the second carrier and outside of the first carrier.

<FIG> is a diagram illustrating an example <NUM> of a PRB shift for aligning narrowbands for LTE MTC UEs and <NUM> MTC UEs. For some bandwidths, the resource blocks and narrowband of the first carrier and the second carrier may not be aligned with each other due to the extra odd physical resource block. As an example, refer to the LTE system bandwidth with an odd number of RBs shown by reference number <NUM>. This may be, for example, a <NUM> system bandwidth. The RBs for this system bandwidth are shown by reference number <NUM>, and the narrowbands associated with this system bandwidth are shown by reference number <NUM>. Now refer to the LTE system bandwidth with an even number of RBs shown by reference number <NUM>. The default narrowband configuration for this LTE system bandwidth is shown by reference number <NUM>. Notice that NB k-<NUM> of the narrowbands shown by reference number <NUM> partially overlaps with NB k-<NUM> of the narrowbands shown by reference number <NUM>. This may be an issue when the lower set of narrowbands (shown by reference number <NUM>) is used for the second carrier, since there may be misalignment between the narrowbands in the first carrier (shown by reference number <NUM>) and the second carrier (shown by reference number <NUM>).

This narrowband misalignment may cause potential collision between a legacy LTE MTC UE and a <NUM> MTC UE when the <NUM> MTC UE is allocated with a narrowband outside of the first carrier. For example, assume a <NUM> carrier bandwidth for the LTE MTC UE and a <NUM> carrier bandwidth for the <NUM> MTC UE. In such a case, the narrowband #<NUM> in the <NUM> carrier (not shown) may partially overlap narrowbands #<NUM> and #<NUM> of the <NUM> carrier (not shown). In such a case, only the narrowbands not overlapping with the first carrier bandwidth can be configured for the <NUM> MTC UE, resulting in inefficient resource utilization.

Some techniques and apparatuses described herein may align the NBs between the first carrier and the second carrier by shifting narrowbands in the second carrier based at least in part on a predefined value or shift, which may be a function of the two carrier bandwidths and the narrowband location. For example, a shift of +/- <NUM> or half an RB may be applied when a <NUM> or <NUM> carrier bandwidth is configured for the legacy LTE MTC UE, and when a <NUM> or <NUM> carrier bandwidth is configured for the <NUM> MTC UE. In this case, and in the cases described in the next paragraph, the positive aspect of the shift (e.g., +<NUM>) may be used for the upper NBs above the center frequency (e.g., with an NB index between (NRB/<NUM>)/<NUM> and (NRB/<NUM>)-<NUM>), and the negative aspect of the shift (e.g., -<NUM>) may be used for the lower NBs below the center frequency (e.g., with an NB index less than (NRB/<NUM>)/<NUM>)). This shift is shown by reference number <NUM>. As can be seen, NB k-<NUM> shown by reference number <NUM> correctly aligns with NB k-<NUM> shown by reference number <NUM>. Thus, collision of NBs between different carriers is reduced or eliminated.

In some aspects, the value of the narrowband shift may be a function of the bandwidth and the narrowband index. For example, if a <NUM> bandwidth is used for the first carrier and a <NUM> or <NUM> bandwidth is used for the second carrier, the narrowbands in the second carrier may be shifted by +/- <NUM> RBs. If a <NUM> bandwidth is used for the first carrier and a <NUM> or <NUM> bandwidth is used for the second carrier, the narrowbands in the second carrier may be shifted by +/- <NUM> RBs. As another example, if a <NUM> or <NUM> bandwidth is used for the first carrier and a <NUM> or <NUM> bandwidth is used for the second carrier, no shift may be applied. If a <NUM> or <NUM> bandwidth is used for the first carrier and a <NUM> or <NUM> bandwidth is used for the second carrier, the narrowbands in the second carrier may be shifted by +/- <NUM> RBs.

<FIG> is a flow chart of a method <NUM> of wireless communication. The method may be performed by a base station (e.g., the BS <NUM> of <FIG>, apparatus <NUM>/<NUM>', and/or the like). Optional steps of the method <NUM> are indicated by dashed flowchart blocks in <FIG>.

At <NUM>, the base station (e.g., using controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, and/or the like) may transmit a bandwidth value for a machine type communication (MTC) user equipment (UE). For example, the bandwidth value may be a first bandwidth value when the MTC UE is configured to use a first carrier associated with a first radio access technology (e.g., LTE). The bandwidth value may be a second bandwidth value when the MTC UE is configured to use a second carrier associated with a second radio access technology (e.g., <NUM>). In some aspects, the first bandwidth value is signaled using a master information block contained within the first carrier. In some aspects, the second bandwidth value is signaled using a master information block contained within the first carrier or a system information block associated with MTC. In some aspects, the base station may signal information identifying one or more repetitions of a system information block associated with MTC, wherein the one or more repetitions are transmitted outside of a bandwidth of the first carrier and within a bandwidth of the second carrier, and wherein the information identifying the one or more repetitions is signaled using a master information block contained within the first carrier. In some aspects, the one or more repetitions are transmitted in one or more narrowbands adjacent to the first carrier.

At <NUM>, the base station (e.g., using controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, and/or the like) may communicate with the MTC UE using the bandwidth value. For example, the base station may transmit certain signals within the first carrier when the MTC UE is an LTE MTC UE. In some aspects, the base station may transmit certain signals within the first carrier and/or the second carrier when the MTC UE is a <NUM> MTC UE. In some aspects, a valid subframe configuration for a narrowband outside of the bandwidth of the first carrier has a temporal granularity of less than <NUM> millisecond. In some aspects, a control region of the first carrier is of a different size than a control region for the second carrier. In some aspects, narrowbands in the first carrier and narrowbands in the second carrier are aligned with each other based at least in part on a shift that is applied to the narrowbands in the second carrier. In some aspects, the shift is based at least in part on a bandwidth of the first carrier and a bandwidth of the second carrier. In some aspects, the first carrier and the second carrier are centered on the same frequency, and a bandwidth of the first carrier is contained within a bandwidth of the second carrier.

At <NUM>, the base station (e.g., using controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, and/or the like) may transmit a downlink control channel for paging within a bandwidth of the first carrier or within a bandwidth of the second carrier. For example, in some cases, the base station may transmit the downlink control channel for paging in the bandwidth of the first carrier. In other cases, the base station may transmit the downlink control channel for paging in the bandwidth of the second carrier and not the first carrier. This may be based at least in part on a UE identifier of the MTC UE (e.g., the <NUM> MTC UE) and a capability of the MTC UE to use the second carrier for MTC communication.

At <NUM>, the base station (e.g., using controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, and/or the like) may signal information identifying one or more narrowbands for the MTC UE to perform random access. For example, the one or more narrowbands may be within a bandwidth of the second carrier and not the first carrier. In such a case, the MTC UE may be a <NUM> MTC UE.

At <NUM>, the base station (e.g., using controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, and/or the like) may transmit a unicast control channel for the MTC UE within a bandwidth of the second carrier and not the first carrier. For example, the unicast control channel may be transmitted within the bandwidth of the second carrier and not the first carrier based at least in part on the MTC UE being configured to use the second carrier (e.g., based at least in part on the MTC UE being a <NUM> MTC UE). In such a case, the base station may transmit, based at least in part on the unicast control channel, a unicast shared channel corresponding to the unicast control channel in the same carrier as the unicast control channel, within a bandwidth of the first carrier or within the bandwidth of the second carrier.

At <NUM>, the base station (e.g., using controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, and/or the like) may communicate with the MTC UE using frequency hopping in accordance with the bandwidth value. In some aspects, when a first frequency hop is contained within a bandwidth of the first carrier, all frequency hops for the MTC UE are contained within the bandwidth of the first carrier. In some aspects, when a first frequency hop is outside of the bandwidth of the first carrier, all frequency hops for the MTC UE are outside of the bandwidth of the first carrier. In some aspects, one or more frequency hops are within a bandwidth of the first carrier and one or more frequency hops are outside of the bandwidth of the first carrier. In some aspects, at least one of a number of narrowbands for the frequency hopping or an offset between the narrowbands for the frequency hopping is different for the first carrier than for the second carrier.

At <NUM>, the base station (e.g., using controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, and/or the like) may transmit a demodulation reference signal without a cell-specific reference signal on one or more narrowbands. For example, the one or more narrowbands may be outside of a bandwidth of the first carrier. In this case, in some aspects, the base station may only transmit the CRS within the bandwidth of the first carrier.

At <NUM>, the base station (e.g., using controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, and/or the like) may transmit a cell-specific reference signal within a particular temporal range of a transmission for the MTC UE, or within a particular frequency range of a narrowband of the second carrier. For example, when the base station identifies one or more narrowbands outside of a bandwidth of the first carrier, the base station may transmit a cell-specific reference signal within a particular temporal range of a transmission for the MTC UE, or within a particular frequency range of the one or more narrowbands in the second carrier.

In some aspects, the base station (e.g., using controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, and/or the like) may signal information identifying one or more narrowbands outside of a bandwidth of the first carrier. For example, the information may identify at least a first PRB and a number of contiguous PRBs of the one or more narrowbands. The one or more narrowbands may form the second carrier.

Although <FIG> shows example blocks of a method of wireless communication, in some aspects, the method may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those shown in <FIG>. Additionally, or alternatively, two or more blocks shown in <FIG> may be performed in parallel.

<FIG> is a conceptual data flow diagram <NUM> illustrating the data flow between different modules/means/components in an example apparatus <NUM>. The apparatus <NUM> may be an eNB or a gNB such as a base station (e.g., BS <NUM>). In some aspects, the apparatus <NUM> includes a reception module <NUM>, a signaling module <NUM>, a communication module <NUM>, and/or a transmission module <NUM>.

The reception module <NUM> may receive signals <NUM> from a wireless communication device <NUM> (e.g., an MTC UE <NUM>). The reception module <NUM> may provide data <NUM> and/or data <NUM> to the signaling module <NUM> and/or the communication module <NUM>.

The signaling module <NUM> may signal or transmit a bandwidth value for an MTC UE, such as wireless communication device <NUM>, by providing data <NUM> to the transmission module <NUM> for transmission as signals <NUM> to the wireless communication device <NUM>. Additionally, or alternatively, the signaling module <NUM> may signal information identifying one or more narrowbands for the MTC UE to perform random access, or may signal information identifying one or more narrowbands outside of a bandwidth of the first carrier, similarly.

The communication module <NUM> may communicate with the wireless communication device <NUM> (e.g., using the reception module <NUM> and/or the transmission module <NUM>). For example, the communication module <NUM> may provide data <NUM> to the transmission module <NUM> for transmission as signals <NUM> to the wireless communication device <NUM>. In some aspects, the communication module <NUM> may communicate with the wireless communication device <NUM> using frequency hopping in accordance with the bandwidth value.

The transmission module <NUM> may transmit signals <NUM> to the wireless communication device <NUM> based at least in part on the data <NUM>/<NUM>. For example, the transmission module <NUM> may transmit transmitting a downlink control channel for paging within a bandwidth of the first carrier or within a bandwidth of the second carrier and not the first carrier based at least in part on a UE identifier of the wireless communication device <NUM>; may transmit a unicast control channel for the wireless communication device <NUM> within a bandwidth of the second carrier and not the first carrier; may transmit a demodulation reference signal without a cell-specific reference signal on one or more narrowbands outside of a bandwidth of the first carrier; may transmit transmitting a cell-specific reference signal within a particular temporal range of a transmission for the MTC UE, or with a particular frequency range of a narrowband of the second carrier; and/or the like.

The apparatus may include additional modules that perform each of the blocks of the algorithm in the aforementioned method <NUM> of <FIG>, and/or the like. As such, each block in the aforementioned method <NUM> of <FIG> and/or the like may be performed by a module and the apparatus may include one or more of those modules. The modules may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof.

<FIG> is a diagram <NUM> illustrating an example of a hardware implementation for an apparatus <NUM>' employing a processing system <NUM>. The apparatus <NUM>' may be an eNB or a gNB such as a base station (e.g., BS <NUM>).

The processing system <NUM> may be implemented with a bus architecture, represented generally by the bus <NUM>. The bus <NUM> may include any number of interconnecting buses and bridges depending on the specific application of the processing system <NUM> and the overall design constraints. The bus <NUM> links together various circuits including one or more processors and/or hardware modules, represented by the processor <NUM>, the modules <NUM>, <NUM>, <NUM>, <NUM>, and the computer-readable medium / memory <NUM>. The bus <NUM> may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further.

The processing system <NUM> may be coupled to a transceiver <NUM>. The transceiver <NUM> is coupled to one or more antennas <NUM>. The transceiver <NUM> provides a means for communicating with various other apparatus over a transmission medium. The transceiver <NUM> receives a signal from the one or more antennas <NUM>, extracts information from the received signal, and provides the extracted information to the processing system <NUM>, specifically the reception module <NUM>. In addition, the transceiver <NUM> receives information from the processing system <NUM>, specifically the transmission module <NUM>, and based at least in part on the received information, generates a signal to be applied to the one or more antennas <NUM>. The processing system <NUM> includes a processor <NUM> coupled to a computer-readable medium / memory <NUM>. The processor <NUM> is responsible for general processing, including the execution of software stored on the computer-readable medium / memory <NUM>. The software, when executed by the processor <NUM>, causes the processing system <NUM> to perform the various functions described herein for any particular apparatus. The computer-readable medium / memory <NUM> may also be used for storing data that is manipulated by the processor <NUM> when executing software. The processing system further includes at least one of the modules <NUM>, <NUM>, <NUM>, <NUM>. The modules may be software modules running in the processor <NUM>, resident/stored in the computer readable medium / memory <NUM>, one or more hardware modules coupled to the processor <NUM>, or some combination thereof. The processing system <NUM> may be a component of the BS <NUM> and may include the memory <NUM> and/or at least one of the TX MIMO processor <NUM>, the RX processor <NUM>, and/or the controller/processor <NUM>.

In some aspects, the apparatus <NUM>/<NUM>' for wireless communication includes means for transmitting a bandwidth value for an MTC UE, wherein the bandwidth value is a first bandwidth value when the MTC UE is configured to use a first carrier associated with a first radio access technology and wherein the bandwidth value is a second bandwidth value when the MTC UE is configured to use a second carrier associated with a second radio access technology; means for communicating with the MTC UE using the bandwidth value; means for transmitting a downlink control channel for paging within a bandwidth of the first carrier or within a bandwidth of the second carrier and not the first carrier based at least in part on a UE identifier of the MTC UE and a capability of the MTC UE to use the second carrier for MTC communication; means for transmitting information identifying one or more narrowbands for the MTC UE to perform random access, wherein the one or more narrowbands are within a bandwidth of the second carrier and not the first carrier, means for transmitting a unicast control channel for the MTC UE within a bandwidth of the second carrier and not the first carrier, wherein the unicast control channel is transmitted within the bandwidth of the second carrier and not the first carrier based at least in part on the MTC UE being configured to use the second carrier, means for communicating with the MTC UE using frequency hopping, wherein, when a first frequency hop is contained within a bandwidth of the first carrier, all frequency hops for the MTC UE are contained within the bandwidth of the first carrier, and when a first frequency hop is outside of the bandwidth of the first carrier, all frequency hops for the MTC UE are outside of the bandwidth of the first carrier; means for communicating with the MTC UE using frequency hopping, wherein one or more frequency hops are within a bandwidth of the first carrier and one or more frequency hops are outside of the bandwidth of the first carrier; means for communicating with the MTC UE using frequency hopping, wherein at least one of a number of narrowbands for the frequency hopping or an offset between the narrowbands for the frequency hopping is different for the first carrier than for the second carrier; means for transmitting a demodulation reference signal without a cell-specific reference signal on one or more narrowbands outside of a bandwidth of the first carrier; means for transmitting a cell-specific reference signal within a particular temporal range of a transmission for the MTC UE, or with a particular frequency range of a narrowband of the second carrier, based at least in part on identifying one or more narrowbands outside of a bandwidth of the first carrier; means for transmitting information identifying one or more repetitions of a system information block associated with MTC, wherein the one or more repetitions are transmitted outside of a bandwidth of the first carrier and within a bandwidth of the second carrier, and wherein the information identifying the one or more repetitions is signaled using a master information block contained within the first carrier; and means for transmitting information identifying one or more narrowbands outside of a bandwidth of the first carrier, wherein the information indicates at least a first PRB and a number of continuous PRBs. The aforementioned means may be one or more of the aforementioned modules of the apparatus <NUM> and/or the processing system <NUM> of the apparatus <NUM>' configured to perform the functions recited by the aforementioned means. As described supra, the processing system <NUM> may include the TX MIMO processor <NUM>, the receive processor <NUM>, and/or the controller/processor <NUM>. As such, in one configuration, the aforementioned means may be the TX MIMO processor <NUM>, the receive processor <NUM>, and/or the controller/processor <NUM> configured to perform the functions recited by the aforementioned means.

<FIG> is a flow chart of a method <NUM> of wireless communication. The method may be performed by an MTC UE (e.g., the UE <NUM> of <FIG>, the apparatus <NUM>/<NUM>', and/or the like). Optional steps of the method <NUM> are indicated by dashed flowchart blocks in <FIG>.

At <NUM>, the MTC UE (e.g., using antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, controller/processor <NUM>, and/or the like) may receive information identifying a bandwidth value for the MTC UE. For example, the bandwidth value may be a first bandwidth value when the MTC UE is configured to use a first carrier associated with a first radio access technology (e.g., LTE). The bandwidth value may be a second bandwidth value when the MTC UE is configured to use a second carrier associated with a second radio access technology (e.g., <NUM>). In some aspects, the first bandwidth value is signaled using a master information block contained within the first carrier. In some aspects, the second bandwidth value is signaled using a master information block contained within the first carrier or a system information block associated with MTC. In some aspects, one or more repetitions of the system information block associated with MTC are transmitted outside of a bandwidth of the first carrier and within a bandwidth of the second carrier. In some aspects, the one or more repetitions are transmitted in one or more narrowbands adjacent to the first carrier.

At <NUM>, the MTC UE (e.g., using antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, controller/processor <NUM>, and/or the like) may communicate using the bandwidth value. For example, the MTC UE may receive certain signals within the first carrier when the MTC UE is an LTE MTC UE. In some aspects, the user equipment may receive certain signals within the first carrier and/or the second carrier when the MTC UE is a <NUM> MTC UE. In some aspects, a valid subframe configuration for a narrowband outside of the bandwidth of the first carrier has a temporal granularity of less than <NUM> millisecond. In some aspects, a control region of the first carrier is of a different size than a control region for the second carrier. In some aspects, narrowbands in the first carrier and narrowbands in the second carrier are aligned with each other based at least in part on a shift that is applied to the narrowbands in the second carrier. In some aspects, the shift is based at least in part on a bandwidth of the first carrier and a bandwidth of the second carrier. In some aspects, the first carrier and the second carrier are centered on the same frequency, and a bandwidth of the first carrier is contained within a bandwidth of the second carrier.

At <NUM>, the MTC UE (e.g., using antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, controller/processor <NUM>, and/or the like) may receive a downlink control channel for paging within a bandwidth of the first carrier or within a bandwidth of the second carrier. For example, in some cases, the MTC UE may receive the downlink control channel for paging in the bandwidth of the first carrier. In other cases, the MTC UE may receive the downlink control channel for paging in the bandwidth of the second carrier and not the first carrier. This may be based at least in part on a UE identifier of the MTC UE (e.g., the <NUM> MTC UE).

At <NUM>, the MTC UE (e.g., using antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, controller/processor <NUM>, and/or the like) may receive information identifying one or more narrowbands for the MTC UE to perform random access. For example, the one or more narrowbands may be within a bandwidth of the second carrier and not the first carrier. In such a case, the MTC UE may be a <NUM> MTC UE.

At <NUM>, the MTC UE (e.g., using antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, controller/processor <NUM>, and/or the like) may receive a unicast control channel for the MTC UE within a bandwidth of the second carrier and not the first carrier. For example, the unicast control channel may be received within the bandwidth of the second carrier and not the first carrier based at least in part on the MTC UE being configured to use the second carrier (e.g., based at least in part on the MTC UE being a <NUM> MTC UE). In such a case, the MTC UE may receive, based at least in part on the unicast control channel, a unicast shared channel corresponding to the unicast control channel in the same carrier as the unicast control channel, within a bandwidth of the first carrier or within the bandwidth of the second carrier.

At <NUM>, the MTC UE (e.g., using antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, controller/processor <NUM>, and/or the like) may communicate using frequency hopping in accordance with the bandwidth vallue. In some aspects, when a first frequency hop is contained within a bandwidth of the first carrier, all frequency hops for the MTC UE are contained within the bandwidth of the first carrier. In some aspects, when a first frequency hop is outside of the bandwidth of the first carrier, all frequency hops for the MTC UE are outside of the bandwidth of the first carrier. In some aspects, one or more frequency hops are within a bandwidth of the first carrier and one or more frequency hops are outside of the bandwidth of the first carrier. In some aspects, at least one of a number of narrowbands for the frequency hopping or an offset between the narrowbands for the frequency hopping is different for the first carrier than for the second carrier.

At <NUM>, the MTC UE (e.g., using antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, controller/processor <NUM>, and/or the like) may receive a demodulation reference signal without a cell-specific reference signal (CRS) on one or more narrowbands. For example, the one or more narrowbands may be outside of a bandwidth of the first carrier. In this case, in some aspects, the MTC UE may only receive the CRS within the bandwidth of the first carrier.

At <NUM>, the MTC UE (e.g., using antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, controller/processor <NUM>, and/or the like) may receive a cell-specific reference signal within a temporal range of a transmission for the MTC UE, or within a frequency range of a narrowband in the second carrier. For example, when the base station identifies one or more narrowbands outside of a bandwidth of the first carrier, the MTC UE may receive a cell-specific reference signal within a particular temporal range of a transmission for the MTC UE, or within a particular frequency range of the one or more narrowbands in the second carrier.

In some aspects, the MTC UE (e.g., using antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, controller/processor <NUM>, and/or the like) may receive information identifying one or more narrowbands outside of a bandwidth of the first carrier. For example, the information may identify at least a first PRB and a number of contiguous PRBs of the one or more narrowbands. The one or more narrowbands may form the second carrier.

<FIG> is a conceptual data flow diagram <NUM> illustrating the data flow between different modules/means/components in an example apparatus <NUM>. The apparatus <NUM> may be a UE, such as an MTC UE. In some aspects, the apparatus <NUM> includes a reception module <NUM>, a communication module <NUM>, and/or a transmission module <NUM>.

The reception module <NUM> may receive signals <NUM> from a base station <NUM> (e.g., BS <NUM>). The signals <NUM> may be similar to the signals <NUM> described in connection with <FIG>, above. The reception module <NUM> may provide the signals <NUM> to the communication module <NUM> as data <NUM>. In some aspects, the data <NUM> may include information identifying a bandwidth value for the apparatus <NUM>, a downlink control channel for paging, information identifying one or more narrowbands for the apparatus <NUM> to perform random access, a unicast control channel for the apparatus <NUM>, a demodulation reference signal without a cell-specific reference signal on one or more narrowbands outside of a bandwidth of the first carrier, and/or the like.

The communication module <NUM> may communicate with the base station <NUM> using a bandwidth value that is received by the reception module <NUM> and/or using frequency hopping. The communication module <NUM> may communicate with the base station <NUM> using reception module <NUM> and/or transmission module <NUM>. For example, the communication module <NUM> may provide data <NUM> to the transmission module <NUM> for transmission as signals <NUM> to the base station <NUM>.

The apparatus may include additional modules that perform each of the blocks of the algorithm in the aforementioned method <NUM> of <FIG> and/or the like. As such, each block in the aforementioned method <NUM> of <FIG> and/or the like may be performed by a module and the apparatus may include one or more of those modules. The modules may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof.

<FIG> is a diagram <NUM> illustrating an example of a hardware implementation for an apparatus <NUM>' employing a processing system <NUM>. The apparatus <NUM>' may be a UE.

The processing system <NUM> may be implemented with a bus architecture, represented generally by the bus <NUM>. The bus <NUM> may include any number of interconnecting buses and bridges depending on the specific application of the processing system <NUM> and the overall design constraints. The bus <NUM> links together various circuits including one or more processors and/or hardware modules, represented by the processor <NUM>, the modules <NUM>, <NUM>, <NUM>, and the computer-readable medium / memory <NUM>. The bus <NUM> may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further.

The processing system <NUM> may be coupled to a transceiver <NUM>. The transceiver <NUM> is coupled to one or more antennas <NUM>. The transceiver <NUM> provides a means for communicating with various other apparatus over a transmission medium. The transceiver <NUM> receives a signal from the one or more antennas <NUM>, extracts information from the received signal, and provides the extracted information to the processing system <NUM>, specifically the reception module <NUM>. In addition, the transceiver <NUM> receives information from the processing system <NUM>, specifically the transmission module <NUM>, and based at least in part on the received information, generates a signal to be applied to the one or more antennas <NUM>. The processing system <NUM> includes a processor <NUM> coupled to a computer-readable medium / memory <NUM>. The processor <NUM> is responsible for general processing, including the execution of software stored on the computer-readable medium / memory <NUM>. The software, when executed by the processor <NUM>, causes the processing system <NUM> to perform the various functions described supra for any particular apparatus. The computer-readable medium / memory <NUM> may also be used for storing data that is manipulated by the processor <NUM> when executing software. The processing system further includes at least one of the modules <NUM>, <NUM>, and <NUM>. The modules may be software modules running in the processor <NUM>, resident/stored in the computer readable medium / memory <NUM>, one or more hardware modules coupled to the processor <NUM>, or some combination thereof. The processing system <NUM> may be a component of the UE <NUM> and may include the memory <NUM> and/or at least one of the TX MIMO processor <NUM>, the RX processor <NUM>, and/or the controller/processor <NUM>.

In some aspects, the apparatus <NUM>/<NUM>' for wireless communication includes means for receiving information identifying a bandwidth value for the apparatus <NUM>/<NUM>', wherein the bandwidth value is a first bandwidth value when the apparatus <NUM>/<NUM>' is configured to use a first carrier associated with a first radio access technology and wherein the bandwidth value is a second bandwidth value when the apparatus <NUM>/<NUM>' is configured to use a second carrier associated with a second radio access technology; means for communicating using the bandwidth value; means for receiving a downlink control channel for paging within a bandwidth of the first carrier or within a bandwidth of the second carrier and not the first carrier based at least in part on a UE identifier of the apparatus <NUM>/<NUM>' and a capability of the apparatus <NUM>/<NUM>' to use the second carrier for MTC communication; means for receiving information identifying one or more narrowbands for the apparatus <NUM>/<NUM>' to perform random access, wherein the one or more narrowbands are within a bandwidth of the second carrier and not the first carrier; means for receiving a unicast control channel for the apparatus <NUM>/<NUM>' within a bandwidth of the second carrier and not the first carrier, wherein the unicast control channel is transmitted within the bandwidth of the second carrier and not the first carrier based at least in part on the apparatus <NUM>/<NUM>' being configured to use the second carrier; means for communicating using frequency hopping, wherein, when a first frequency hop is contained within a bandwidth of the first carrier, all frequency hops for the apparatus <NUM>/<NUM>' are contained within the bandwidth of the first carrier, and when a first frequency hop is outside of the bandwidth of the first carrier, all frequency hops for the apparatus <NUM>/<NUM>' are outside of the bandwidth of the first carrier; means for communicating using frequency hopping, wherein one or more frequency hops are within a bandwidth of the first carrier and one or more frequency hops are outside of the bandwidth of the first carrier; means for communicating using frequency hopping, wherein at least one of a number of narrowbands for the frequency hopping or an offset between the narrowbands for the frequency hopping is different for the first carrier than for the second carrier; means for receiving a demodulation reference signal without a cell-specific reference signal on one or more narrowbands outside of a bandwidth of the first carrier; and means for receiving a cell-specific reference signal within a particular temporal range of a transmission for the apparatus <NUM>/<NUM>', or with a particular frequency range of a narrowband of the second carrier, based at least in part on identifying one or more narrowbands outside of a bandwidth of the first carrier. The aforementioned means may be one or more of the aforementioned modules of the apparatus <NUM> and/or the processing system <NUM> of the apparatus <NUM>' configured to perform the functions recited by the aforementioned means. As described supra, the processing system <NUM> may include the TX MIMO processor <NUM>, the RX processor <NUM>, and/or the controller/processor <NUM>. As such, in one configuration, the aforementioned means may be the TX MIMO processor <NUM>, the RX processor <NUM>, and/or the controller/processor <NUM> configured to perform the functions recited by the aforementioned means.

It should be understood that the specific order or hierarchy of blocks in the processes / flow charts disclosed is an illustration of example approaches. Based upon design preferences, it is understood that the specific order or hierarchy of blocks in the processes / flow charts may be rearranged.

The description herein is provided in order to enable any person skilled in the art to practice the various aspects described herein. Thus, the claims are not intended to be limited to the aspects shown herein, but are to be accorded the full scope consistent with the language of the claims, wherein reference to an element in the singular is not intended to mean "one and only one" unless specifically so stated, but rather "one or more. " The word "exemplary" is used herein to mean "serving as an example, instance, or illustration. Unless specifically stated otherwise, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C," "at least one of A, B, and C," and "A, B, C, or any combination thereof' include any combination of A, B, and/or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as "at least one of A, B, or C," "at least one of A, B, and C," and "A, B, C, or any combination thereof' may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C.

Claim 1:
A method of wireless communication performed by a base station, comprising:
transmitting (<NUM>) a bandwidth value for a machine type communication, MTC, user equipment, UE, wherein the bandwidth value is a first bandwidth value when the MTC UE is configured to use a first carrier associated with a first radio access technology and wherein the bandwidth value is a second bandwidth value when the MTC UE is configured to use a second carrier associated with a second radio access technology; and
communicating (<NUM>) with the MTC UE using the bandwidth value,
wherein communicating with the MTC UE using the bandwidth value further comprises:
communicating with the MTC UE using frequency hopping, wherein, when a first frequency hop is contained within a bandwidth of the first carrier, all frequency hops for the MTC UE are contained within the bandwidth of the first carrier, and when the first frequency hop is outside of the bandwidth of the first carrier, all frequency hops for the MTC UE are outside of the bandwidth of the first carrier.