HK1235981B - Sub-band allocation techniques for reduced-bandwidth machine-type communication (mtc) devices - Google Patents

Description

Subband allocation technique for machine-type communication (MTC) devices to reduce bandwidth

Related cases

This application claims priority to U.S. Provisional Patent Application Serial No. 62/059,745, filed October 3, 2014, which is hereby incorporated by reference in its entirety.

Technical Field

Embodiments herein generally relate to communications between devices in a broadband wireless communication network.

Background Art

Machine-type communications (MTC) is an emerging area of widespread interest in broadband wireless communication networks. MTC generally refers to a type of typically automated wireless communication, such as that performed by "userless" devices such as meters, monitors, and sensors. The nature of wireless communication performed by MTC devices can tend to differ from that performed by non-MTC devices. For non-MTC devices, downlink (DL) and/or uplink (UL) data exchanges may occur relatively frequently, the amount of data transmitted may be relatively large, achieving high data rates may be relatively important, and mobility events may be quite common. In contrast, for many MTC devices, DL and/or UL data exchanges may occur relatively infrequently, the amount of data transmitted may be relatively small, achieving high data rates may be relatively unimportant, and mobility events may be relatively rare. Due to the nature of typical MTC device communications, cost reduction and power conservation can be key objectives in designing MTC devices and the resource allocation schemes by which radio channel resources are used to transmit MTC device data.

Summary of the Invention

According to one aspect of the present application, a user equipment (UE) is provided, comprising: logic, at least a portion of which is located in hardware, the logic being configured to identify a machine type communication (MTC) subband allocation based on received MTC subband allocation information, the MTC subband allocation comprising allocating a plurality of subcarriers to an MTC subband of a system bandwidth of a serving cell of the UE, the MTC subband allocation defining a plurality of MTC direct current (DC) subcarriers among the plurality of subcarriers in the MTC subband, the MTC subband allocation being applied to one or more subframes, wherein for each of the one or more subframes, the definition of the plurality of subcarriers is applied only during an orthogonal frequency division multiplexing (OFDM) symbol following a control region of the subframe, the MTC subband allocation information comprising an MTC allocation duration parameter indicating a duration of the MTC subband allocation, the logic being configured to identify the one or more subframes based on the MTC allocation duration parameter; and a radio interface being configured to receive a transmission via the MTC subband according to the MTC subband allocation.

According to another aspect of the present application, an evolved Node B (eNB) is provided, comprising: logic, at least a portion of which is located in hardware, the logic being configured to determine a machine type communication (MTC) subband allocation, the MTC subband allocation comprising allocating a plurality of subcarriers to an MTC subband of a system bandwidth of the eNB, the MTC subband allocation defining a plurality of MTC direct current (DC) subcarriers among the plurality of subcarriers of the MTC subband, the MTC subband allocation being applied to one or more subframes, wherein for each of the one or more subframes, the definition of the plurality of subcarriers is applied only during an orthogonal frequency division multiplexing (OFDM) symbol following a control region of the subframe, the MTC subband allocation information comprising an MTC allocation duration parameter indicating a duration of the MTC subband allocation; and a radio interface for transmitting a signal comprising the MTC subband allocation information indicating the MTC subband allocation.

According to another aspect of the present application, a wireless communication device is provided, including: a device for assigning a machine type communication (MTC) user equipment (UE) to an MTC subband; a device for sending MTC subband allocation information to indicate the MTC subband allocation for the MTC subband, the MTC subband allocation being used to allocate multiple subcarriers to the MTC subband, and defining multiple MTC direct current (DC) subcarriers among the multiple subcarriers in the MTC subband, the MTC subband allocation being applied to one or more subframes, wherein for each of the one or more subframes, the definition of the multiple subcarriers is applied only during an orthogonal frequency division multiplexing (OFDM) symbol following a control region of the subframe, the MTC subband allocation information including an MTC allocation duration parameter for indicating the duration of the MTC subband allocation; and a device for sending a message including data for the MTC UE through the assigned MTC subband.

According to another aspect of the present application, a wireless communication method is provided, including: assigning a machine type communication (MTC) user equipment (UE) an MTC subband; sending MTC subband allocation information to indicate an MTC subband allocation for the MTC subband, the MTC subband allocation being used to allocate multiple subcarriers to the MTC subband, and defining multiple MTC direct current (DC) subcarriers among the multiple subcarriers in the MTC subband, the MTC subband allocation being applied to one or more subframes, wherein for each of the one or more subframes, the definition of the multiple subcarriers is applied only during an orthogonal frequency division multiplexing (OFDM) symbol following a control region of the subframe, the MTC subband allocation information including an MTC allocation duration parameter for indicating a duration of the MTC subband allocation; and sending a message including data for the MTC UE through the assigned MTC subband.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 illustrates an embodiment of a first operating environment.

FIG2 illustrates an embodiment of a radio resource grid.

FIG3 shows an embodiment of a first radio resource allocation.

FIG4 shows an embodiment of a second radio resource allocation.

FIG5 shows a third embodiment of radio resource allocation.

FIG6 shows a fourth embodiment of radio resource allocation.

FIG7 shows a fifth embodiment of radio resource allocation.

FIG8 shows an embodiment of a sixth radio resource allocation.

FIG9 shows a seventh embodiment of radio resource allocation.

FIG10 illustrates an embodiment of a second operating environment.

FIG11 illustrates an embodiment of a first logic flow.

FIG12 illustrates an embodiment of a second logic flow.

FIG13A shows an embodiment of a first storage medium.

FIG13B shows an embodiment of a second storage medium.

FIG14 shows an embodiment of a device.

FIG15 illustrates an embodiment of a wireless network.

DETAILED DESCRIPTION

Various embodiments may be generally directed to subband allocation techniques for machine-type communication (MTC) devices for reducing bandwidth. In one embodiment, for example, a user equipment (UE) may include: logic, at least a portion of which is in hardware, for identifying a machine-type communication (MTC) subband allocation based on received MTC subband allocation information, the MTC subband allocation comprising allocating a plurality of subcarriers to an MTC subband of a system bandwidth of a serving cell of the UE, the MTC subband allocation defining at least one MTC direct current (DC) subcarrier among the plurality of subcarriers; and a radio interface for receiving transmissions via the MTC subband according to the MTC subband allocation. Other embodiments are also described and claimed.

Various embodiments may include one or more elements. Elements may include any structure that is arranged to perform a specific operation. Each element may be implemented as hardware, software, or any combination thereof according to the needs of a given set of design parameters or performance constraints. Although it may be possible to describe an embodiment by way of example using a limited number of elements in a specific topology, according to the needs of a given implementation, an embodiment may include more or fewer elements in an alternative topology. It is noteworthy that any reference to "an embodiment" or "embodiment" means that the specific features, structures, or characteristics described in conjunction with the embodiment are included in at least one embodiment. The phrases "in one embodiment," "in some embodiments," and "in various embodiments" that appear throughout the specification do not necessarily all refer to the same embodiment.

The technology disclosed herein may involve the transmission of data over one or more wireless connections using one or more wireless mobile broadband technologies. For example, various embodiments may involve transmission over one or more wireless connections based on one or more Third Generation Partnership Project (3GPP), 3GPP Long Term Evolution (LTE), and/or 3GPP LTE-Advanced (LTE-A) technologies and/or standards (including their predecessors, revisions, successors, and/or variants). Some embodiments may more specifically involve wireless communications based on one or more MTC-related 3GPP standards, which may be embodied, for example, in 3GPP Technical Specification (TS) 22.368 Version 13.1.0 (2014-12) and/or 3GPP TS 23.682 Version 13.0.0 (2014-12) (including their predecessors, revisions, successors, and/or variants). Various embodiments may additionally or alternatively relate to transmissions in accordance with one or more of the following technologies and/or standards: Global System for Mobile Communications (GSM)/Enhanced Data Rates for GSM Evolution (EDGE), Universal Mobile Telecommunications System (UMTS)/High Speed Packet Access (HSPA), and/or GSM with General Packet Radio Service (GPRS) system (GSM/GPRS) technologies and/or standards (including predecessors, revisions, successors and/or variants thereof).

Examples of wireless mobile broadband technologies and/or standards may also include, but are not limited to, any of the following: Institute of Electrical and Electronics Engineers (IEEE) 802.16 wireless broadband standards (e.g., IEEE 802.16m and/or 802.16p), International Mobile Telecommunications-Advanced (IMT-ADV), Worldwide Interoperability for Microwave Access (WiMAX) and/or WiMAX II, Code Division Multiple Access (CDMA) 2000 (e.g., CDMA2000 1xRTT, CDMA2000 EV-DO, CDMA EV-DV, etc.), High Performance Radio Metropolitan Area Network (HIPERMAN), Wireless Broadband (WiBro), High Speed Downlink Packet Access (HSDPA), High Speed Orthogonal Frequency Division Multiplexing (OFDM) Packet Access (HSOPA), High Speed Uplink Packet Access (HSUPA) technologies and/or standards (including predecessors, revisions, successors, and/or variants thereof).

Some embodiments may additionally or alternatively involve wireless communications according to other wireless communication technologies and/or standards. Examples of other wireless communication technologies and/or standards that may be used in various embodiments may include, but are not limited to, other IEEE wireless communication standards (e.g., IEEE 802.11, IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, IEEE 802.11u, IEEE 802.11ac, IEEE 802.11ad, IEEE 802.11af, and/or IEEE 802.11ah standards), standards implemented by the IEEE High-efficiency Wi-Fi standards developed by the 802.11 High-Efficiency WLAN (HEW) study group, Wi-Fi Alliance (WFA) wireless communication standards (e.g., Wi-Fi, Wi-Fi Direct, Wi-Fi Direct Service, Wi-Fi Gigabit (WiGig), WiGig Display Extensions (WDE), WiGig Bus Extensions (WBE), WiGig Serial Extensions (WSE) standards, and/or standards developed by the WFA Neighbor Awareness Networking (NAN) Task Group), and/or Near Field Communication (NFC) standards (e.g., standards developed by the NFC Forum), including any predecessor versions, revisions, successors, and/or variants of any of the foregoing standards. Embodiments are not limited to these examples.

In addition to transmission over one or more wireless connections, the technology disclosed herein may involve transmission of content over one or more wired connections via one or more wired communication media. Examples of wired communication media may include wires, cables, metal leads, printed circuit boards (PCBs), backplanes, switch fabrics, semiconductor materials, twisted pairs, coaxial cables, optical fibers, and the like. The embodiments are not limited in this context.

FIG1 illustrates an example of an operating environment 100 that can represent various embodiments. In operating environment 100, an MTC UE 102 is located within a cell 103, which is typically served by an eNB 104. In some embodiments, cell 103 may comprise a cell of an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access Network (E-UTRAN). In various embodiments, eNB 104 may transmit downlink (DL) MTC control information 106 and/or DL MTC data 108 to MTC UE 102 using subcarriers within the system bandwidth of eNB 104. In some embodiments, MTC UE 102 may transmit uplink (UL) MTC control information 110 and/or UL MTC data 112 to eNB 104 using subcarriers within the system bandwidth of eNB 104. The embodiments are not limited in this context.

FIG2 illustrates an example of a radio resource grid 200, which may represent radio resources associated with the system bandwidth of the eNB 104 of FIG1 in various embodiments. More specifically, the radio resource grid 200 may represent radio resources included in the system bandwidth of the eNB 104 during a given subframe. As shown in FIG2 , in the horizontal dimension, the radio resource grid 200 includes a series of orthogonal frequency division multiplexing (OFDM) symbols, which collectively constitute a subframe. In the vertical dimension, the radio resource grid 200 includes a plurality of subcarriers, which collectively constitute a system bandwidth (BW _SYS ) 202. In some embodiments, the BW _SYS 202 may comprise the system bandwidth of a device responsible for allocating radio resources in the radio resource grid 200. In various embodiments, the BW _SYS 202 may comprise the system bandwidth of the eNB 104 of FIG1 . The embodiments are not limited in this context.

In some embodiments, some radio resources within radio resource grid 200 may be designated for the transmission of control messages. For example, in various embodiments, radio resources within control region 204 may be designated for control message transmission, where control region 204 includes resource elements (REs) for each subcarrier during a specific number of initial OFDM symbols at the beginning of a subframe spanned by radio resource grid 200. In some embodiments, a subcarrier substantially centrally located among a plurality of subcarriers in BW _SYS 202 may be defined as a direct current (DC) subcarrier 206. In various embodiments, DC subcarrier 206 may include subcarriers that are not actually used when performing transmissions via BW _SYS 202. In some/various embodiments, DC subcarrier 206 may be implemented to mitigate DC offset issues that may arise at direct conversion receivers when converting RF signals received via BW _SYS 202 to baseband. The embodiments are not limited in this context.

In some embodiments, when an eNB uses resources of radio resource grid 200 to transmit control information or data to UEs within its cell, the eNB can use all subcarriers of system bandwidth 204 for that purpose. In various embodiments, if the eNB is permitted to use any particular set of subcarriers of its choice to exchange control information or data with a given UE, the UE may be required to be able to communicate using each of the multiple subcarriers included in BW _SYS 202, such that the UE can access any particular subcarrier that the eNB may allocate for its communications during any particular time frame.

As mentioned above, cost reduction and power conservation may be key objectives for designing MTC devices and resource allocation schemes according to which radio channel resources are used to transmit MTC device data. Therefore, in some embodiments, it may be desirable to configure MTC UEs to communicate using a reduced bandwidth that is less than the typical system bandwidth of the cell that can serve these MTC UEs. For example, it may be desirable to configure MTC UEs to use a reduced bandwidth of 1.4 MHz, which corresponds to the defined minimum LTE system bandwidth. In various embodiments, implementing such a reduced bandwidth may reduce power consumption at the MTC UEs because these MTC UEs may not be required to monitor as many subcarriers. In some embodiments, implementing such a reduced bandwidth may also enable reduction and/or simplification of signal processing circuitry of the MTC UEs, which in turn may enable reduction in cost for the MTC UEs. The embodiments are not limited in this context.

FIG3 illustrates an example of a radio resource allocation 300, which may represent an implementation of a subband allocation technique for MTC devices for reducing bandwidth in various embodiments. According to the radio resource allocation 300, an MTC subband 302 is defined as comprising a subset of subcarriers within the BW _SYS 202. More specifically, the MTC subband 302 comprises the DC subcarrier 206 and 36 consecutive subcarriers on either side of the DC subcarrier 206. As reflected in FIG3, a resource block (RB) may comprise a bandwidth of 12 subcarriers, such that the MTC subband 302 may comprise the DC subcarrier 206 and three consecutive RBs on either side of the DC subcarrier 206. In other words, the MTC subband 302 may comprise the six central resource blocks of the BW _SYS 202 and the DC subcarrier 206. In some embodiments, for DL transmission, the MTC subband 302 may be defined only during the OFDM symbol following the control region 204, and the control region 204 may be reserved to facilitate seamless coexistence between existing protocols and MTC protocols using a reduced MTC bandwidth. The embodiments are not limited in this context.

Based on various subband allocation techniques for MTC devices with reduced bandwidth, an eNB may be configured to define multiple MTC subbands within its system bandwidth, thereby supporting a larger number of MTC UEs using reduced bandwidth. In some embodiments, each MTC subband may include a bandwidth substantially equal to the reduced bandwidth of the MTC UE. In various embodiments, the eNB may be allowed to define overlapping MTC subbands, such that multiple MTC subbands may include the same specific subcarrier. In some other embodiments, MTC subbands may be required to be disjoint, such that any specific subcarrier may be included in at most one MTC subband. The embodiments are not limited in this context.

FIG4 illustrates an example of a radio resource allocation 400, which may represent an implementation of a subband allocation technique for MTC devices for bandwidth reduction in various embodiments. More specifically, radio resource allocation 400 may represent embodiments in which MTC subbands are allowed to overlap. According to radio resource allocation 400, three MTC subbands 402, 404, and 406 are defined within BW _SYS 202. Although MTC subband 402 is disjoint with respect to MTC subbands 404 and 406, MTC subbands 404 and 406 overlap in overlap region 408. MTC subbands 402 and 406 do not include DC subcarrier 206. MTC subband 404 includes DC subcarrier 206, but DC subcarrier 206 is not essentially central within MTC subband 404. Embodiments are not limited to this example.

Figure 5 illustrates an example of a radio resource allocation 500, which may represent an implementation of a subband allocation technique for MTC devices for bandwidth reduction in various embodiments. More specifically, radio resource allocation 500 may represent embodiments in which MTC subbands are required to be disjoint. Radio resource allocation 500 includes MTC subband 302 of Figure 3, which may include DC subcarrier 206 and three consecutive RBs located on either side of DC subcarrier 206. Radio resource allocation 500 also defines MTC subbands 502 and 504, which are disjoint with respect to each other and to MTC subband 302. MTC subband 302 includes DC subcarrier 206, which is located substantially at the center of MTC subband 302. MTC subbands 502 and 504 do not include DC subcarrier 206. In the example of radio resource allocation 500, MTC subband 502 can be considered adjacent to MTC subband 302, and MTC subband 302 can be considered adjacent to MTC subband 504, in the sense that there are no unallocated subcarriers between the respective pairs of these subbands. However, it is worth noting that the requirement for MTC subbands to be non-intersecting does not necessarily require that these MTC subbands be adjacent, and in various embodiments, radio resource allocation can be implemented to define non-adjacent and non-intersecting MTC subbands. The embodiments are not limited in this context.

FIG6 illustrates an example of a radio resource allocation 600, which may represent an implementation of a subband allocation technique for MTC devices for bandwidth reduction in some embodiments. More specifically, radio resource allocation 600 may represent various embodiments implementing a radio resource allocation in which none of the multiple defined MTC subbands includes the DC subcarrier of the system bandwidth in which they are defined. In the example of FIG6 , BW _SYS 202 may be sized such that it includes precisely enough subcarriers to define four disjoint MTC subbands within BW _SYS 202. That is, two disjoint but adjacent MTC subbands 602 and 604 may be defined on one side of the DC subcarrier 206, and two disjoint but adjacent MTC subbands 606 and 608 may be defined on the other side of the DC subcarrier 206. In some embodiments, an advantage associated with wireless resource allocation 600 relative to wireless resource allocation 500 of FIG5 may be that wireless resource allocation 600 accommodates four disjoint MTC subbands within BW _SYS 202, whereas wireless resource allocation 500 only accommodates three disjoint MTC subbands. However, while one of the MTC subbands defined by wireless resource allocation 500 includes a substantially central DC subcarrier, none of the MTC subbands defined by wireless resource allocation 600 includes a substantially central DC subcarrier. Embodiments are not limited to this example.

In various embodiments, it may be desirable for any given MTC subband to include a substantially centrally located DC subcarrier for substantially the same reasons that it may be desirable for a system bandwidth, such as BW _SYS 202 of Figures 2-5, to include a substantially centrally located DC subcarrier, such as DC subcarrier 206. However, as illustrated in the aforementioned examples, in some embodiments, the substantially centrally located DC subcarrier of the system bandwidth may not be substantially centrally located within one or more MTC subbands defined within the system bandwidth, or may not even be included within the one or more MTC subbands. Thus, according to the subband allocation techniques for reduced bandwidth MTC devices disclosed in various embodiments, one or more MTC DC subcarriers may be defined among the multiple subcarriers in a given MTC subband.

FIG7 illustrates an example of a radio resource allocation 700, which may represent an implementation of a subband allocation technique for MTC devices for bandwidth reduction in some embodiments. More specifically, radio resource allocation 700 may represent various embodiments in which a corresponding MTC DC subcarrier is defined within each of a plurality of disjoint MTC subbands. As shown in FIG7 , radio resource allocation 700 defines the same MTC subbands 602, 604, 606, and 608 as radio resource allocation 600 of FIG6 . However, according to radio resource allocation 700, the substantially central subcarriers within MTC subbands 602, 604, 606, and 608 are defined as MTC DC subcarriers 702, 704, 706, and 708. In some embodiments, multiple corresponding substantially central MTC DC subcarriers may be defined for any particular MTC subband. In an example, each of the three substantially central subcarriers within the MTC subband 602 (rather than the single MTC DC subcarrier 702 defined for the MTC subband 602) may be defined as an MTC DC subcarrier. The embodiments are not limited to this example.

It is noteworthy that in various embodiments, as reflected in radio resource allocation 700, the definition of MTC DC subcarriers may be applied only during those OFDM symbols following the OFDM symbols of the control region 204. In some embodiments, limiting the defined MTC DC subcarriers to the OFDM symbols following the control region 204 preserves the legacy usage of those subcarriers during the control region 204, which may minimize the impact on legacy devices associated with implementing the disclosed subband allocation techniques for reduced bandwidth MTC devices. The embodiments are not limited in this context.

FIG8 illustrates an example of a radio resource allocation 800, which may represent an implementation of a subband allocation technique for MTC devices for bandwidth reduction in various embodiments. More specifically, radio resource allocation 800 may represent embodiments in which a corresponding MTC DC subcarrier is defined within each of a plurality of MTC subbands, including overlapping MTC subbands. As shown in FIG8 , radio resource allocation 800 defines the same MTC subbands 402, 404, and 406 as radio resource allocation 400 of FIG4 . However, according to radio resource allocation 800, subcarriers substantially centrally located within MTC subbands 402, 404, and 406 are defined as MTC DC subcarriers 802, 804, and 806. As previously mentioned, in various embodiments, multiple MTC DC subcarriers, each substantially centrally located, may be defined for any particular MTC subband. Thus, for example, each of the three substantially central subcarriers within the MTC subband 402 (rather than the single MTC DC subcarrier 802 defined for the MTC subband 402) may be defined as an MTC DC subcarrier. The embodiments are not limited to this example.

It is noteworthy that in some embodiments, as reflected in radio resource allocation 800, one or more MTC DC subcarriers can be defined within an MTC subband that also includes a DC subcarrier of the system bandwidth. For example, according to radio resource allocation 800, a subcarrier that is substantially centrally located within MTC subband 404 is defined as MTC DC subcarrier 804, while another subcarrier that is not centrally located within MTC subband 404 is defined as DC subcarrier 206 of BW _SYS 202. In various embodiments, both DC subcarrier 206 and MTC DC subcarrier 804 can be treated as DC subcarriers with respect to transmission/reception on MTC subband 404. In some other embodiments, only MTC DC subcarrier 804 can be treated as a DC subcarrier with respect to transmission/reception on MTC subband 404. The embodiments are not limited in this context.

In various embodiments, an eNB that defines one or more MTC subbands within its system bandwidth may allocate bandwidth to those MTC subbands based on a minimum system bandwidth according to a legacy protocol. For example, an eNB may allocate bandwidth to MTC subbands based on a defined minimum LTE system bandwidth of 1.4 MHz. In some embodiments, according to a legacy protocol, the minimum system bandwidth may include a central DC subcarrier (e.g., DC subcarrier 206) and a specific number of resource blocks (in the frequency dimension) on either side of the central DC subcarrier. For example, a 1.4 MHz LTE system bandwidth may include a central DC subcarrier and three resource blocks (in the frequency dimension) on either side of the central DC subcarrier. In various embodiments, an eNB that allocates bandwidth to MTC subbands based on a minimum system bandwidth according to a legacy protocol may allocate the same number of contiguous resource blocks to each MTC subband as the number of resource blocks included in the minimum system bandwidth according to the legacy protocol. For example, based on a minimum LTE system bandwidth of 1.4 MHz (which includes three resource blocks on either side of the central DC subcarrier), the eNB may define each MTC subband as six contiguous resource blocks in the frequency dimension. In some embodiments, the MTC subband defined in this manner may include a different number of subcarriers than the number of subcarriers included in the minimum system bandwidth of the legacy protocol.

Figure 9 shows an example of a radio resource allocation 900 that can represent such an embodiment. In Figure 9, the minimum system bandwidth (MSB) subband 902 is depicted as representing radio resources for communication according to the minimum system bandwidth of the traditional protocol. In various embodiments, the MSB subband 902 can represent radio resources for communication according to the minimum LTE system bandwidth of 1.4 MHz. As shown in Figure 9, in the frequency dimension, the MSB subband 902 includes a central DC subcarrier 206 and a total of six resource blocks, with three resource blocks on either side of the central DC subcarrier 206. Each resource block includes 12 subcarriers, so that the MSB subband 902 includes 72 available subcarriers and one DC subcarrier, or a total of 73 subcarriers. The MTC subband 904 is defined as also including six resource blocks. More specifically, the MTC subband 904 includes six consecutive resource blocks. Unlike the MSB subband 902, the MTC subband 904 does not include the DC subcarrier 206, and thus the MTC subband 904 only includes a total of 72 subcarriers instead of 73 subcarriers. If one or more MTC DC subcarriers are defined within the MTC subband 904, the number of subcarriers available in the MTC subband 904 will be less than 72 - that is, the number of subcarriers available in the MTC subband 904 will be 72 minus the number of MTC DC subcarriers defined within the MTC subband 904. It is worth noting that in some embodiments, 1.4 MHz may be allocated for a given MTC subband instead of six consecutive resource blocks. In various such embodiments, one MTC DC subcarrier may be defined within the MTC subband, and the number of subcarriers available in the MTC subband may actually be equal to 72. The embodiments are not limited in this context.

FIG10 illustrates an example operating environment 1000, which may represent embodiments in which the MTC UE 102 and the eNB 104 of FIG1 implement subband allocation techniques for reducing bandwidth for MTC devices. In the operating environment 1000, one or more MTC subbands may be defined within the system bandwidth of the eNB 104. In various embodiments, each MTC subband may be defined by a corresponding MTC subband allocation. In some embodiments, each MTC subband allocation may include allocating multiple subcarriers to the corresponding MTC subband. In various embodiments, any particular MTC subband allocation may define one or more MTC DC subcarriers among the multiple subcarriers in its corresponding MTC subband. In some embodiments, the eNB 104 may transmit MTC subband allocation information 1006 to enable the MTC UE 102 to identify any particular MTC subband allocation.

In some embodiments, any particular MTC subband allocation may comprise a predefined allocation for the system bandwidth used by the eNB 104. In some embodiments, the MTC subband allocation information 1006 sent by the eNB 104 to inform the MTC UE 102 of such predefined allocation may simply include a system bandwidth parameter indicating the system bandwidth of the eNB 104. In various embodiments, for example, the eNB 104 may inform the MTC UE 102 of a given MTC subband allocation by including a system bandwidth parameter indicating its system bandwidth in a master information block (MIB). It is noteworthy that in some such embodiments, the system bandwidth parameter may comprise a conventional parameter included by the eNB 104 in the MIB, regardless of whether the eNB 104 implements subband allocation techniques for MTC devices with reduced bandwidth. The embodiments are not limited in this context.

In various embodiments, any particular MTC subband allocation may be semi-statically configured by the eNB 104. For example, in some embodiments, the eNB 104 may semi-statically configure a given MTC subband allocation to span a specific number of subframes within each radio frame or to apply to a specific set of subframes within each radio frame. In various embodiments, the MTC subband allocation information 1006 transmitted by the eNB 104 to notify the MTC UE 102 of such a semi-static allocation may include one or more parameters included by the eNB 104 in a system information block (SIB). In one example, the eNB 104 may include an MTC allocation duration parameter in the SIB to specify a number of subframes during which the semi-static MTC subband allocation applies in each radio frame. In another example, the eNB 104 may include an MTC allocation subframe bitmap in the SIB to indicate one or more subframes to which the MTC subband allocation applies during each radio frame. In some embodiments, conventional SIBs may be enhanced to convey the MTC subband allocation information 1006 for semi-static MTC subband allocations. In various other embodiments, a new SIB may be defined for transmitting MTC subband allocation information 1006 for semi-static MTC subband allocation. The embodiments are not limited in this context.

In some embodiments, any specific MTC subband allocation may be dynamically configured by the eNB 104. For example, in various embodiments, the eNB 104 may dynamically configure the MTC subband allocation for a given radio frame. In some embodiments, the eNB 104 may use Layer 1 signaling to provide the MTC UE 102 with MTC subband allocation information 1006 for the dynamically configured MTC subband allocation. In various embodiments, the eNB 104 may provide the MTC subband allocation information 1006 for the dynamically configured MTC subband allocation to the MTC UE 102 by including the MTC subband allocation information 1006 in a radio resource control (RRC) message that the eNB 104 sends to the MTC UE 102. In some embodiments, the MTC subband allocation information 1006 sent by the eNB 104 to the MTC UE 102 may specify specific resources of the MTC subband that have been allocated for the MTC UE 102. The embodiments are not limited in this context.

In various embodiments, each MTC subband may include the same predefined size and number of MTC DC subcarriers. In some such embodiments, the eNB 104 may notify the MTC UE 102 of a specific MTC subband allocation by sending MTC subband allocation information 1006, where the MTC subband allocation information 1006 includes only the starting frequency position of the allocated MTC subband. In various embodiments, based on the received MTC subband allocation information 1006 indicating the starting frequency position of the MTC subband and based on the known defined MTC subband size and MTC DC subcarrier count, the MTC UE 102 may identify the subcarriers included in the allocated MTC subband and identify the MTC DC subcarrier among the subcarriers. The embodiments are not limited in this context.

In some embodiments, after transmitting MTC subband allocation information 1006 to notify MTC UE 102 of the allocation of a given MTC subband, eNB 104 may transmit data 1008 to MTC UE 102 using the MTC subband. More specifically, eNB 104 may transmit a signal including the data 1008 to MTC UE 102 via the MTC subband. As mentioned above with respect to radio resource allocation 900 of FIG. 9 , in various embodiments, an MTC subband defined as having a size substantially corresponding to the size of a minimum system bandwidth according to a conventional protocol may include a different number of subcarriers than the number of subcarriers used for transmission over the minimum system bandwidth according to the conventional protocol. Thus, in some embodiments, MTC UE 102 may receive a signal including the data 1008 via a different number of subcarriers than the number of subcarriers over which it receives a signal transmitted over the minimum system bandwidth. For example, although the MTC UE 102 may be configured to receive transmissions via 73 subcarriers over a minimum LTE system bandwidth of 1.4 MHz, the MTC UE 102 may only receive signals including the data 1008 via 72 subcarriers. The embodiments are not limited to this example.

In various embodiments, the eNB 104 may generate a coded bit stream based on the data 1008, generate a modulated symbol stream based on the coded bit stream, generate a signal based on the modulated symbol stream, and transmit the signal over the MTC subband to the MTC UE 102. In some embodiments, the eNB 104 may define one or more MTC DC subcarriers within the MTC subband during the process of generating the signal.

In various embodiments, the eNB 104 may generate one or more MTC DC subcarriers in conjunction with applying rate matching to the coded bit stream prior to modulation. In some such embodiments, the eNB 104 may perform rate matching and, based on the rate matching performed, exclude resource elements (REs) of the MTC DC subcarriers for purposes of calculating the number of coded bits to be obtained by rate matching. In various embodiments, the eNB 104 may apply puncturing for subframes during which legacy transmissions would collide on the MTC DC subcarriers. Examples of such legacy transmissions may include, but are not limited to, reference signals such as a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), and a demodulation reference signal (DM-RS). In some embodiments, after rate matching, the eNB 104 may perform modulation to generate a modulated symbol stream and generate a signal comprising data 1008 based on the modulated symbol stream. The embodiments are not limited in this context.

In various other embodiments, the eNB 104 may generate one or more MTC DC subcarriers after modulation. In some such embodiments, the eNB 104 may perform rate matching, including the REs of the MTC DC subcarriers according to the rate matching performed for purposes of calculating the number of coded bits to be obtained by the rate matching. In various embodiments, the eNB 104 may then perform modulation to generate a modulated symbol stream, perform symbol puncturing on the symbols corresponding to the MTC DC subcarriers to obtain a punctured and modulated symbol stream, and generate a signal comprising data 1008 based on the punctured and modulated symbol stream. In some embodiments, the eNB 104 may apply puncturing for subframes during which legacy transmissions would collide on the MTC DC subcarriers. Examples of such legacy transmissions may include, but are not limited to, reference signals such as CRS, CSI-RS, and DM-RS. The embodiments are not limited in this context.

In various embodiments, it may be desirable for the eNB 104 to switch the MTC subband assignment for the MTC UE 102 from one MTC subband to another. In some embodiments, each time the MTC subband assignment for the MTC UE 102 changes, the MTC UE 102 may need to perform a receive retuning before it can begin receiving transmissions over the newly assigned MTC subband. The amount of time it takes the MTC UE 102 to complete a receive retuning for the newly assigned MTC subband may be referred to as the retuning time for the newly assigned MTC subband. The amount of time that elapses between the assignment of a new MTC subband and the next assignment of a different MTC subband may be referred to as the assignment duration for the newly assigned MTC subband.

With respect to any given MTC subband that may be assigned to an MTC UE 102, the larger the retuning time relative to the assignment duration, the greater the portion of the assignment duration that is wasted, in the sense that the assigned MTC subband cannot actually be used during the retuning time. Therefore, in various embodiments, the eNB 104 may be configured to observe a minimum switching time with respect to MTC subband assignments for any particular UE (e.g., MTC UE 102). In some embodiments, the eNB 104 may be configured to observe a minimum switching time with respect to both resource allocations for unicast and broadcast DL transmissions and resource allocations for unicast UL transmissions. For example, in various embodiments, the eNB 104 may assign MTC subbands to the MTC UE 102 in such a manner that the MTC UE 102 will be associated with any particular assigned DL or UL MTC subband for at least the minimum switching time. In some embodiments, the eNB 104 may allocate MTC subband resources with a granularity that matches the minimum switching time in the time dimension. For example, in various embodiments where the minimum switching time is one radio frame, the eNB 104 may allocate MTC subband resources on a radio frame by radio frame basis.The embodiments are not limited to this example.

In some embodiments, such as in the aforementioned example, a minimum switching time of one radio frame may be implemented. In various other embodiments, the minimum switching time may include an integer number of radio frames greater than one. In still other embodiments, the minimum switching time may include a positive integer number of subframes or OFDM symbols. In still other embodiments, the minimum switching time may be defined based on some other time units, and may or may not include a positive integer number of such time units. In some embodiments, a given defined minimum switching time may be specific to a specific UE, a specific group of UEs, a specific MTC subband, or a specific group of MTC subbands. Embodiments are not limited to these examples.

The operation of the above embodiments may also be described with reference to the following figures and accompanying examples. Some of the figures in the accompanying drawings may include logic flows. Although such figures presented herein may include specific logic flows, it is understood that the logic flows merely provide examples of how the general functionality described herein can be implemented. In addition, unless otherwise indicated, a given logic flow does not necessarily have to be executed in the order presented. Furthermore, a given logic flow may be implemented by hardware elements, software elements executed by a processor, and any combination thereof. The embodiments are not limited to this context.

FIG11 illustrates an example of a logic flow 1100, which may represent operations that may be performed in conjunction with implementations of subband allocation techniques for MTC devices for reduced bandwidth in various embodiments. For example, logic flow 1100 may represent operations that may be performed by MTC UE 102 in the operating environment 1000 of FIG10 in some embodiments. As shown in FIG11 , at 1102, MTC subband allocation information may be received. For example, in the operating environment 1000 of FIG10 , MTC UE 102 may receive MTC subband allocation information 1006 from eNB 104. At 1104, an MTC subband allocation may be identified based on the MTC subband allocation information. In various embodiments, the MTC subband allocation may include allocating a plurality of subcarriers to an MTC subband of the system bandwidth, and at least one MTC DC subcarrier may be defined within the plurality of subcarriers. For example, in the operating environment 1000 of FIG. 10 , the MTC UE 102 may identify an MTC subband allocation based on received MTC subband allocation information 1006. The MTC subband allocation may include allocating a plurality of subcarriers to an MTC subband of the system bandwidth of the eNB 104, and may define at least one MTC DC subcarrier within the plurality of subcarriers. At 1106, a transmission may be received via the MTC subband according to the MTC subband allocation. For example, in the operating environment 1000 of FIG. 10 , the MTC UE 102 may receive a transmission including data 1008 via the MTC subband according to the identified MTC subband allocation for the MTC subband. Embodiments are not limited to these examples.

FIG12 illustrates an example of a logic flow 1200, which may represent operations that may be performed in conjunction with implementations of subband allocation techniques for MTC devices with reduced bandwidth in some embodiments. For example, logic flow 1200 may represent operations that may be performed by eNB 104 in operating environment 1000 of FIG10 in various embodiments. As shown in FIG12 , at 1202, an MTC subband allocation for an MTC subband may be determined. In some embodiments, the MTC subband allocation may include allocating a plurality of subcarriers to an MTC subband of the system bandwidth, and defining at least one MTC DC subcarrier within the plurality of subcarriers. For example, in operating environment 1000 of FIG10 , eNB 104 may determine an MTC subband allocation, including allocating a plurality of subcarriers to an MTC subband of the system bandwidth of eNB 104, and defining at least one MTC DC subcarrier within the plurality of subcarriers. At 1204, MTC subband allocation information indicating the MTC subband allocation may be transmitted. For example, in the operating environment 1000 of FIG. 10 , the eNB 104 may transmit MTC subband allocation information 1006, which indicates an MTC subband allocation for an MTC subband within the system bandwidth of the eNB 104. At 1206, data for the MTC UE may be transmitted over the MTC subband according to the MTC subband allocation. For example, in the operating environment 1000 of FIG. 10 , the eNB 104 may generate a signal including data 1008 based on the MTC subband allocation for the MTC subband, and may transmit the signal to the MTC UE 102 via the MTC subband. Embodiments are not limited to these examples.

FIG13A illustrates an embodiment of a storage medium 1300. Storage medium 1300 may include any non-transitory computer-readable storage medium or machine-readable storage medium, such as an optical storage medium, a magnetic storage medium, or a semiconductor storage medium. In various embodiments, storage medium 1300 may include an article of manufacture. In some embodiments, storage medium 1300 may store computer-executable instructions for execution at an MTC UE. In various embodiments, storage medium 1300 may store computer-executable instructions for implementing the logic flow 1100 of FIG11 . Examples of computer-readable or machine-readable storage media may include any tangible medium capable of storing electronic data, including volatile or non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writable or rewritable memory, and the like. Examples of computer-executable instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, object-oriented code, visual code, and the like. The embodiments are not limited in this context.

FIG13B illustrates an embodiment of a storage medium 1350. Storage medium 1350 may include any non-transitory computer-readable storage medium or machine-readable storage medium, such as an optical storage medium, a magnetic storage medium, or a semiconductor storage medium. In various embodiments, storage medium 1350 may include an article of manufacture. In some embodiments, storage medium 1350 may store computer-executable instructions for execution at an eNB. In various embodiments, storage medium 1350 may store computer-executable instructions for implementing logic flow 1200 in FIG12 . Examples of computer-readable storage media or machine-readable storage media, or examples of computer-readable instructions, may include, but are not limited to, any of the various examples described above with reference to storage medium 1300 in FIG13A . The embodiments are not limited in this context.

FIG14 illustrates an embodiment of a communications device 1400, wherein the communications device 1400 may implement one or more of the following: the MTC UE 102 and eNB 104 of FIG1 and FIG10, the logic flow 1100 of FIG11, the logic flow 1200 of FIG12, the storage medium 1300 of FIG13A, and the storage medium 1350 of FIG13B. In various embodiments, the device 1400 may include logic circuitry 1428. The logic circuitry 1428 may include physical circuitry configured to perform, for example, the operations described with respect to one or more of the MTC UE 102 and eNB 104 of FIG1 and FIG10, the logic flow 1100 of FIG11, and the logic flow 1200 of FIG12. As shown in FIG14, the device 1400 may include a radio interface 1410, baseband circuitry 1420, and a computing platform 1430, although embodiments are not limited to this configuration.

The device 1400 may implement some or all of the structures and/or operations for one or more of the MTC UE 102 and eNB 104 of Figures 1 and 10, the logic flow 1100 of Figure 11, the logic flow 1200 of Figure 12, the storage medium 1300 of Figure 13A, the storage medium 1350 of Figure 13B, and the logic circuit 1428 in a single computing entity (e.g., entirely within a single device). Alternatively, the device 1400 may distribute a portion of the structure and/or operations for one or more of the MTC UE 102 and eNB 104 of Figures 1 and 10, the logic flow 1100 of Figure 11, the logic flow 1200 of Figure 12, the storage medium 1300 of Figure 13A, the storage medium 1350 of Figure 13B, and the logic circuit 1428 across multiple computing entities using a distributed system architecture, such as a client-server architecture, a 3-tier architecture, an N-tier architecture, a tightly coupled or clustered architecture, a peer-to-peer architecture, a master-slave architecture, a shared database architecture, and other types of distributed systems. The embodiments are not limited in this context.

In one embodiment, the radio interface 1410 may include a component or combination of components suitable for transmitting and/or receiving single-carrier or multi-carrier modulated signals (e.g., including complementary code keying (CCK), orthogonal frequency division multiplexing (OFDM), and/or single-carrier frequency division multiple access (SC-FDMA) symbols), but embodiments are not limited to any particular air interface or modulation scheme. The radio interface 1410 may include, for example, a receiver 1412, a frequency synthesizer 1414, and/or a transmitter 1416. The radio interface 1410 may include bias control, a crystal oscillator, and/or one or more antennas 1418-f. In another embodiment, the radio interface 1410 may use an external voltage-controlled oscillator (VCO), a surface acoustic wave filter, an intermediate frequency (IF) filter, and/or an RF filter as needed. Due to the diversity of potential RF interface designs, further description thereof is omitted.

The baseband circuitry 1420 can communicate with the radio interface 1410 to process received and/or transmitted signals and can include, for example, a mixer for downconverting received RF signals, an analog-to-digital converter 1422 for converting analog signals to digital form, a digital-to-analog converter 1424 for converting digital signals to analog form, and a mixer for upconverting signals for transmission. Furthermore, the baseband circuitry 1420 can include baseband or PHY processing circuitry 1426 for physical layer (PHY) link layer processing of corresponding received/transmitted signals. The baseband circuitry 1420 can include, for example, medium access control (MAC) processing circuitry 1427 for MAC/data link layer processing. The baseband circuitry 1420 can include a memory controller 1432 for communicating with the MAC processing circuitry 1427 and/or the computing platform 1430, for example, via one or more interfaces 1434.

In some embodiments, PHY processing circuitry 1426 may include a frame construction and/or detection module in conjunction with additional circuitry such as a buffer memory to construct and/or deconstruct communication frames. Alternatively or additionally, MAC processing circuitry 1427 may share processing for some of these functions or perform these processes independently of PHY processing circuitry 1426. In some embodiments, MAC and PHY processing may be integrated into a single circuit.

The computing platform 1430 can provide computing functionality for the device 1400. As shown, the computing platform 1430 can include a processing component 1440. In addition to or in lieu of the baseband circuitry 1420, the device 1400 can use the processing component 1440 to perform processing operations or logic for one or more of the MTC UE 102 and eNB 104 of Figures 1 and 10, the logic flow 1100 of Figure 11, the logic flow 1200 of Figure 12, the storage medium 1300 of Figure 13A, the storage medium 1350 of Figure 13B, and the logic circuitry 1428. The processing component 1440 (and/or the PHY 1426 and/or the MAC 1427) can include various hardware elements, software elements, or a combination of both. Examples of hardware elements may include devices, logic devices, components, processors, microprocessors, circuits, processor circuits, circuit elements (e.g., transistors, resistors, capacitors, inductors, etc.), integrated circuits, application specific integrated circuits (ASICs), programmable logic devices (PLDs), digital signal processors (DSPs), field programmable gate arrays (FPGAs), memory cells, logic gates, registers, semiconductor devices, chips, microchips, chipsets, etc. Examples of software elements may include software components, programs, applications, computer programs, applications, system programs, software development programs, machine programs, operating system software, middleware, firmware, software modules, routines, subroutines, functions, methods, processes, software interfaces, application program interfaces (APIs), instruction sets, computing codes, computer codes, code segments, computer code segments, words, values, symbols, or any combination thereof. Determining whether an embodiment is implemented using hardware elements and/or software elements may vary according to any number of factors as required for a given implementation, such as desired computing rates, power levels, thermal tolerances, processing cycle budgets, input data rates, output data rates, memory resources, data bus speeds, and other design or performance constraints.

Computing platform 1430 may also include other platform components 1450. Other platform components 1450 include common computing elements such as one or more processors, multi-core processors, coprocessors, memory units, chipsets, controllers, peripherals, interfaces, oscillators, timing devices, video cards, audio cards, multimedia input/output (I/O) components (e.g., digital displays), power supplies, and the like. Examples of memory cells may include, but are not limited to, various types of computer-readable and machine-readable storage media in the form of one or more higher-speed memory cells, such as read-only memory (ROM), random-access memory (RAM), dynamic RAM (DRAM), double data rate DRAM (DDRAM), synchronous DRAM (SDRAM), static RAM (SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory, polymer memory such as ferroelectric polymer memory, Austenite memory, phase change or ferroelectric memory, silicon-oxide-nitride-oxide-silicon (SONOS) memory, magnetic or optical cards, device arrays such as redundant array of independent disks (RAID) drives, solid-state memory devices (e.g., USB memory), solid-state drives (SSDs), and any other type of storage medium suitable for storing information.

Device 1400 can be, for example, an ultra-mobile device, a mobile device, a fixed device, a machine-to-machine (M2M) device, a personal digital assistant (PDA), a mobile computing device, a smartphone, a telephone, a digital telephone, a cellular phone, a user device, an eBook reader, a handheld device, a one-way pager, a two-way pager, a messaging device, a computer, a personal computer (PC), a desktop computer, a laptop computer, a notebook computer, a netbook computer, a handheld computer, a tablet computer, a server, a server array or server farm, a web server, a network server, an internet server, a workstation, a minicomputer, a mainframe computer, a supercomputer, a network appliance, a web appliance, a distributed computing system, a multi-processor system, a processor-based system, a consumer electronics product, a programmable consumer electronics product, a gaming device, a display, a television, a digital television, a set-top box, a wireless access point, a base station, a node B, a subscriber station, a mobile subscriber center, a radio network controller, a router, a hub, a gateway, a bridge, a switch, a machine, or a combination thereof. Accordingly, the functions and/or specific configurations of the device 1400 described herein may be included in various embodiments of the device 1400 or omitted in various embodiments of the device 1400 as appropriately required.

Embodiments of the device 1400 may be implemented using a single-input single-output (SISO) architecture. However, some embodiments may include multiple antennas (e.g., antennas 1418-f) that transmit and/or receive using adaptive antenna techniques for beamforming or spatial division multiple access (SDMA) and/or using MIMO communication techniques.

The components and features of device 1400 may be implemented using any combination of discrete circuits, application specific integrated circuits (ASICs), logic gates, and/or single-chip architectures. Additionally, the features of device 1400 may be implemented using a microcontroller, a programmable logic array, and/or a microprocessor, or any combination thereof, where appropriate. Note that hardware, firmware, and/or software elements may be collectively or individually referred to herein as "logic" or "circuitry."

It should be understood that the exemplary device 1400 shown in the block diagram of Figure 14 may represent a functionally descriptive example of many potential implementations. Accordingly, the division, omission, or inclusion of block functions depicted in the figures does not imply that hardware components, circuits, software, and/or elements for implementing these functions must be divided, omitted, or included in the embodiment.

FIG15 illustrates an embodiment of a broadband wireless access system 1500. As shown in FIG15 , broadband wireless access system 1500 may be an Internet Protocol (IP)-based network, including, for example, an Internet 1510-type network capable of supporting mobile wireless access and/or fixed wireless access to the Internet 1510. In one or more embodiments, broadband wireless access system 1500 may include any type of wireless network based on orthogonal frequency division multiple access (OFDMA) or single-carrier frequency division multiple access (SC-FDMA), such as a system compliant with one or more of the 3GPP LTE specifications and/or the IEEE 802.16 standard, although the scope of the claimed subject matter is not limited in these respects.

In exemplary broadband wireless access system 1500, radio access networks (RANs) 1512 and 1518 can be coupled with evolved Node Bs (eNBs) 1514 and 1520, respectively, to provide wireless communication between one or more fixed devices 1516 and the Internet 1510, and/or between one or more mobile devices 1522 and the Internet 1510. An example of fixed device 1516 and mobile device 1522 is device 1400 of FIG. 14 , where fixed device 1516 comprises a static version of device 1400 and mobile device 1522 comprises a mobile version of device 1400. RANs 1512 and 1518 can implement profiles that define the mapping of network functions to one or more physical entities on broadband wireless access system 1500. eNBs 1514 and 1520 may include radio equipment to provide RF communications with fixed devices 1516 and/or mobile devices 1522 (e.g., as described with reference to device 1400), and may include, for example, PHY and MAC layer equipment compliant with the 3GPP LTE specification or the IEEE 802.16 standard. eNBs 1514 and 1520 may also include an IP backplane coupled to the Internet 1510 via RANs 1512 and 1518, respectively, although the scope of the claimed subject matter is not limited in these respects.

The broadband wireless access system 1500 may further include a visitor core network (CN) 1524 and/or a home CN 1526, each of which may be capable of providing one or more network functions, including but not limited to proxy and/or relay-type functions, such as authentication, authorization, and accounting (AAA) functions, dynamic host configuration protocol (DHCP) functions or domain name service control, domain gateways such as public switched telephone network (PSTN) gateways or voice over internet protocol (VoIP) gateways, and/or internet protocol (IP)-type server functions, etc. However, these are merely examples of the types of functions that may be provided by the visitor CN 1524 and/or home CN 1526, and the scope of the claimed subject matter is not limited in these respects. The visited CN 1524 may be referred to as a visited CN when the visited CN 1524 is not part of the regular service provider for the fixed device 1516 or mobile device 1522, for example, when the fixed device 1516 or mobile device 1522 roams away from its corresponding home CN 1526, or when the broadband wireless access system 1500 is part of the regular service provider for the fixed device 1516 or mobile device 1522, but the broadband wireless access system 1500 may be in another location or state that is not the primary or home location for the fixed device 1516 or mobile device 1522. The embodiments are not limited in this context.

Fixed device 1516 can be located anywhere within range of one or both of eNBs 1514 and 1520 (e.g., in or near a home or business) to provide broadband access to the Internet 1510 to home or business customers via eNBs 1514 and 1520, RANs 1512 and 1518, and home CN 1526, respectively. It is worth noting that while fixed device 1516 is typically deployed in a static location, it can be moved to different locations as needed. For example, if mobile device 1522 is within range of one or both of eNBs 1514 and 1520, mobile device 1522 can be utilized at one or more locations. According to one or more embodiments, an operations support system (OSS) 1528 can be part of broadband wireless access system 1500 to provide management functions for broadband wireless access system 1500 and to provide interfaces between functional entities of broadband wireless access system 1500. Broadband wireless access system 1500 of FIG. 15 is merely one type of wireless network illustrating a certain number of components of broadband wireless access system 1500 , but the scope of the claimed subject matter is not limited in these respects.

Each embodiment can be realized using hardware elements, software elements or a combination thereof.The example of hardware elements can include processors, microprocessors, circuits, circuit elements (for example, transistors, resistors, capacitors, inductors, etc.), integrated circuits, application specific integrated circuits (ASICs), programmable logic devices (PLDs), digital signal processors (DSPs), field programmable gate arrays (FPGAs), logic gates, registers, semiconductor devices, chips, microchips, chipsets, etc. The example of software can include software components, programs, applications, computer programs, application programs, system programs, machine programs, operating system software, middleware, firmware, software modules, routines, subroutines, functions, methods, processes, software interfaces, application program interfaces (APIs), instruction sets, computing codes, computer codes, code segments, computer code segments, words, values, symbols or any combination thereof. Determine whether an embodiment is realized using hardware elements and/or software elements and can vary according to any number of factors, such as desired computing speed, power level, thermal tolerance, processing cycle budget, input data rate, output data rate, memory resources, data bus speed and other design or performance constraints.

One or more aspects of at least one embodiment may be implemented by representative instructions stored on a machine-readable medium, which represent various logics within the processor and, when read by a machine, cause the machine to manufacture logic to perform the techniques described herein. Such representations, referred to as “IP cores,” may be stored on tangible machine-readable media and supplied to various customers or production facilities to be loaded into manufacturing machines that actually manufacture the logic or processor. Some embodiments may be implemented, for example, using a machine-readable medium or article, which may store instructions or instruction sets that, when executed by a machine, cause the machine to perform the methods and/or operations according to the embodiments. Such machines may include, for example, any suitable processing platform, computing platform, computing device, processing device, computing system, processing system, computer, processor, etc., and may be implemented using any suitable combination of hardware and/or software. The machine-readable medium or article may include, for example, any suitable type of memory unit, memory device, memory article, memory medium, storage device, storage article, storage medium and/or storage unit, such as memory, removable or non-removable media, erasable or non-erasable media, writable or rewritable media, digital or analog media, hard disk, floppy disk, compact disk read only memory (CD-ROM), compact disk recordable (CD-R), compact disk rewritable (CD-RW), optical disk, magnetic media, magneto-optical media, removable memory cards or disks, various types of digital versatile disks (DVDs), magnetic tape, cartridges, etc. The instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, encrypted code, etc., implemented using any suitable high-level, low-level, object-oriented, visual, compiled and/or interpreted programming language.

Example 1 is a user equipment (UE) comprising: logic, at least a portion of which is located in hardware, the logic being configured to identify a machine type communication (MTC) subband allocation based on received MTC subband allocation information, the MTC subband allocation comprising allocating a plurality of subcarriers to an MTC subband of a system bandwidth of a serving cell of the UE, the MTC subband allocation defining at least one MTC direct current (DC) subcarrier among the plurality of subcarriers; and a radio interface for receiving transmissions via the MTC subband according to the MTC subband allocation.

Example 2 is the UE of Example 1, the MTC subband allocation information includes a system bandwidth parameter identifying a system bandwidth, and the logic identifies the MTC subband allocation based on the system bandwidth parameter.

Example 3 is the UE of Example 1, applying the MTC subband allocation to the one or more subframes, the logic identifying the one or more subframes based on the MTC subband allocation information.

Example 4 is the UE of Example 3, wherein the MTC subband allocation information includes an MTC allocation duration parameter for indicating a duration of the MTC subband allocation, and the logic identifies one or more subframes based on the MTC allocation duration parameter.

Example 5 is the UE of Example 3, wherein the MTC subband allocation information includes an MTC allocated subframe bitmap, and the logic identifies one or more subframes based on the MTC allocated subframe bitmap.

Example 6 is the UE of Example 1, and the received MTC subband allocation information is included in a received master information block (MIB).

Example 7 is the UE of Example 1, and the received MTC subband allocation information is included in a received system information block (SIB).

Example 8 is the UE of Example 1, wherein the received MTC subband allocation information is included in a received radio resource control (RRC) message.

Example 9 is the UE of Example 1, comprising a touch screen display.

Example 10 is an evolved Node B (eNB), comprising: logic, at least a portion of which is located in hardware, the logic being configured to determine a machine type communication (MTC) subband allocation, the MTC subband allocation comprising allocating a plurality of subcarriers to an MTC subband of a system bandwidth of the eNB, the MTC subband allocation defining one or more MTC direct current (DC) subcarriers among the plurality of subcarriers; and a radio interface for transmitting a signal comprising MTC subband allocation information indicating the MTC subband allocation.

Example 11 is the eNB of Example 10, the logic being configured to generate a coded bit stream comprising data for an MTC user equipment (UE), and to generate a modulated symbol stream based on the coded bit stream, the radio interface generating a second signal comprising data for the MTC UE based on the modulated symbol stream and transmitting the second signal.

Example 12 is the eNB of Example 11, the logic being to generate a rate-matched and coded bit stream based on the coded bit stream by applying rate matching to one or more MTC DC subcarriers, and generating a modulated symbol stream based on the rate-matched and coded bit stream.

Example 13 is the eNB of Example 11, the logic to generate a burst of symbols based on the coded bit stream, and puncture the burst of symbols by applying puncturing to one or more MTC DC subcarriers to obtain a modulated symbol stream.

Example 14 is the eNB of Example 10, wherein the MTC subband allocation includes a predefined MTC subband allocation for a system bandwidth, and the MTC subband allocation information includes a system bandwidth parameter for indicating the system bandwidth.

Example 15 is the eNB of Example 10, and the MTC subband allocation information is used to indicate a duration of the MTC subband allocation.

Example 16 is the eNB of Example 10, the MTC subband allocation information includes an MTC allocated subframe bitmap indicating one or more subframes to which the MTC subband allocation is applied.

Example 17 is the eNB of Example 10, wherein the MTC subband allocation includes dynamically configured MTC subband allocation for a user equipment (UE).

Example 18 is at least one non-transitory computer-readable storage medium comprising a set of wireless communication instructions, which, in response to being executed at an evolved Node B (eNB), causes the eNB to perform the following operations: assigning an MTC subband to a machine type communication (MTC) user equipment (UE); sending MTC subband allocation information to indicate an MTC subband allocation for the MTC subband, the MTC subband allocation being used to allocate multiple subcarriers to the MTC subband and defining one or more MTC direct current (DC) subcarriers among the multiple subcarriers; and sending a message including data for the MTC UE via the assigned MTC subband.

Example 19 is the at least one non-transitory computer-readable storage medium of Example 18, comprising wireless communication instructions that, in response to being executed at an eNB, cause the eNB to select the assigned MTC subband from a plurality of defined MTC subbands within a system bandwidth of the eNB.

Example 20 is the at least one non-transitory computer-readable storage medium of Example 19, at least one MTC subband of the plurality of defined MTC subbands overlapping with at least one other MTC subband of the plurality of defined MTC subbands.

Example 21 is the at least one non-transitory computer-readable storage medium of Example 19, at least one MTC subband of the plurality of defined MTC subbands comprising a plurality of MTC DC subcarriers.

Example 22 is the at least one non-transitory computer-readable storage medium of Example 19, at least one MTC subband of the plurality of defined MTC subbands overlapping with a DC subcarrier of a system bandwidth of the eNB.

Example 23 is the at least one non-transitory computer-readable storage medium of Example 19, comprising wireless communication instructions that, in response to being executed at an eNB, cause the eNB to dynamically configure a plurality of defined subbands.

Example 24 is the at least one non-transitory computer-readable storage medium of Example 18, the MTC subband allocation information being used to identify a starting frequency position of the assigned MTC subband.

Example 25 is at least one non-transitory computer-readable storage medium of Example 18, comprising wireless communication instructions that, in response to being executed at an eNB, cause the eNB to determine a subsequent time based on a minimum switching time for the MTC subband assignment, at which subsequent time a second MTC subband is assigned to the MTC UE.

Example 26 is a wireless communication device comprising: a device for determining a machine type communication (MTC) subband allocation, the MTC subband allocation comprising allocating multiple subcarriers to an MTC subband of a system bandwidth of an evolved Node B (eNB), the MTC subband allocation defining one or more MTC direct current (DC) subcarriers among the multiple subcarriers; and a device for sending a signal comprising MTC subband allocation information for indicating the MTC subband allocation.

Example 27 is a wireless communication device of Example 26, comprising: a device for generating an encoded bit stream including data for an MTC user equipment (UE); a device for generating a modulated symbol stream based on the encoded bit stream; a device for generating a second signal including data for the MTC UE based on the modulated symbol stream; and a device for sending the second signal.

Example 28 is a wireless communication device of Example 27, comprising: a device for generating a rate-matched and coded bit stream based on the coded bit stream by applying rate matching to one or more MTC DC subcarriers, and a device for generating a modulated symbol stream based on the rate-matched and coded bit stream.

Example 29 is a wireless communication device of Example 27, comprising: a device for generating a string of symbols based on a coded bit stream, and a device for puncturing the string of symbols by applying puncturing to one or more MTC DC subcarriers to obtain a modulated symbol stream.

Example 30 is the wireless communication device of Example 26, the MTC subband allocation comprises a predefined MTC subband allocation for a system bandwidth, and the MTC subband allocation information comprises a system bandwidth parameter for indicating the system bandwidth.

Example 31 is the wireless communication device of Example 26, wherein the MTC subband allocation information is used to indicate a duration of the MTC subband allocation.

Example 32 is the wireless communication device of Example 26, the MTC subband allocation information comprising an MTC allocated subframe bitmap indicating one or more subframes to which the MTC subband allocation is applied.

Example 33 is the wireless communication device of Example 26, the MTC subband allocation comprising a dynamically configured MTC subband allocation for a user equipment (UE).

Example 34 is a system comprising: a wireless communication device according to any of Examples 26 to 33, at least one radio frequency (RF) transceiver, and at least one RF antenna.

Example 35 is a wireless communication method, comprising: assigning, by a processing circuit at an evolved Node B (eNB), an MTC subband to a machine type communication (MTC) user equipment (UE); sending MTC subband allocation information to indicate an MTC subband allocation for the MTC subband, the MTC subband allocation being used to allocate multiple subcarriers to the MTC subband and defining one or more MTC direct current (DC) subcarriers among the multiple subcarriers; and sending a message including data for the MTC UE via the assigned MTC subband.

Example 36 is the wireless communication method of Example 35, comprising selecting the assigned MTC subband from a plurality of defined MTC subbands within a system bandwidth of the eNB.

Example 37 is the wireless communication method of Example 36, at least one of the plurality of defined MTC subbands overlapping with at least one other of the plurality of defined MTC subbands.

Example 38 is the wireless communication method of Example 36, wherein at least one of the plurality of defined MTC subbands comprises a plurality of MTC DC subcarriers.

Example 39 is the wireless communication method of Example 36, wherein at least one of the plurality of defined MTC subbands overlaps with a DC subcarrier of a system bandwidth of the eNB.

Example 40 is the wireless communication method of Example 36, comprising dynamically configuring the plurality of defined subbands.

Example 41 is the wireless communication method of Example 35, wherein the MTC subband allocation information is used to identify a starting frequency position of the assigned MTC subband.

Example 42 is the wireless communication method of Example 35, comprising determining a subsequent time at which to assign a second MTC subband to the MTC UE based on a minimum switching time of the MTC subband assignment.

Example 43 is at least one non-transitory computer-readable storage medium comprising a set of instructions that, in response to being executed on a computing device, causes the computing device to perform a wireless communication method according to any of Examples 35 to 42.

Example 44 is an apparatus comprising means for performing a wireless communication method according to any of Examples 35 to 42.

Example 45 is a system comprising the apparatus of Example 44, at least one radio frequency (RF) transceiver, and at least one RF antenna.

Example 46 is at least one non-transitory computer-readable storage medium comprising a set of wireless communication instructions, which in response to being executed on a user equipment (UE) causes the UE to perform the following operations: identifying a machine type communication (MTC) subband allocation based on received MTC subband allocation information, the MTC subband allocation comprising allocating multiple subcarriers to an MTC subband of a system bandwidth of a serving cell of the UE, the MTC subband allocation defining at least one MTC direct current (DC) subcarrier among the multiple subcarriers; and receiving a transmission via the MTC subband according to the MTC subband allocation.

Example 47 is at least one non-transitory computer-readable storage medium of Example 46, comprising wireless communication instructions that, in response to being executed at a UE, cause the UE to identify the MTC subband allocation based on a system bandwidth parameter included in the MTC subband allocation information, the system bandwidth parameter being used to identify the system bandwidth.

Example 48 is the at least one non-transitory computer-readable storage medium of Example 46, comprising wireless communication instructions that, in response to being executed at a UE, cause the UE to identify one or more subframes to which the MTC subband allocation is to be applied based on the MTC subband allocation information.

Example 49 is at least one non-transitory computer-readable storage medium of Example 48, comprising wireless communication instructions that, in response to being executed at a UE, cause the UE to identify one or more subframes based on an MTC allocation duration parameter included in the MTC subband allocation information, the MTC allocation duration parameter being used to indicate a duration of the MTC subband allocation.

Example 50 is at least one non-transitory computer-readable storage medium of Example 48, comprising wireless communication instructions that, in response to being executed at a UE, cause the UE to identify one or more subframes based on an MTC allocated subframe bitmap included in the MTC subband allocation information.

Example 51 is the at least one non-transitory computer-readable storage medium of Example 46, the received MTC subband allocation information being included in a received master information block (MIB).

Example 52 is the at least one non-transitory computer-readable storage medium of Example 46, the received MTC subband allocation information being included in a received system information block (SIB).

Example 53 is the at least one non-transitory computer-readable storage medium of Example 46, the received MTC subband allocation information being included in a received radio resource control (RRC) message.

Example 54 is a wireless communication device comprising: a device for assigning a machine type communication (MTC) user equipment (UE) to an MTC subband; a device for sending MTC subband allocation information to indicate an MTC subband allocation for the MTC subband, the MTC subband allocation being used to allocate multiple subcarriers to the MTC subband and defining one or more MTC direct current (DC) subcarriers among the multiple subcarriers; and a device for sending a message including data for the MTC UE via the assigned MTC subband.

Example 55 is the wireless communication device of Example 54, comprising means for selecting the assigned MTC subband from a plurality of defined MTC subbands within a system bandwidth of an evolved Node B (eNB).

Example 56 is the wireless communication device of Example 55, at least one of the plurality of defined MTC subbands overlapping with at least one other of the plurality of defined MTC subbands.

Example 57 is the wireless communication device of Example 55, wherein at least one of the plurality of defined MTC subbands comprises a plurality of MTC DC subcarriers.

Example 58 is the wireless communication device of Example 55, wherein at least one of the plurality of defined MTC subbands overlaps with a DC subcarrier of a system bandwidth of the eNB.

Example 59 is the wireless communication device of Example 55, comprising means for dynamically configuring a plurality of defined subbands.

Example 60 is the wireless communication device of Example 54, wherein the MTC subband allocation information is used to identify a starting frequency position of the assigned MTC subband.

Example 61 is the wireless communication apparatus of Example 54, comprising means for determining a subsequent time based on a minimum switching time of the MTC subband assignment, wherein the second MTC subband is assigned to the MTC UE at the subsequent time.

Example 62 is a system comprising the wireless communication device according to any of Examples 54 to 61, at least one radio frequency (RF) transceiver, and at least one RF antenna.

Example 63 is a wireless communication method, comprising: identifying, by a processing circuit at a user equipment (UE), a machine type communication (MTC) subband allocation based on received MTC subband allocation information, the MTC subband allocation comprising allocating multiple subcarriers to an MTC subband of a system bandwidth of a serving cell of the UE, the MTC subband allocation defining at least one MTC direct current (DC) subcarrier among the multiple subcarriers; and receiving a transmission via the MTC subband according to the MTC subband allocation.

Example 64 is the wireless communication method of Example 63, comprising identifying the MTC subband allocation based on a system bandwidth parameter included in the MTC subband allocation information, the system bandwidth parameter being used to identify the system bandwidth.

Example 65 is the wireless communication method of Example 63, comprising identifying one or more subframes to which the MTC subband allocation is to be applied based on the MTC subband allocation information.

Example 66 is the wireless communication method of Example 65, comprising identifying one or more subframes based on an MTC allocation duration parameter included in the MTC subband allocation information, the MTC allocation duration parameter being used to indicate a duration of the MTC subband allocation.

Example 67 is the wireless communication method of Example 65, comprising identifying one or more subframes based on an MTC allocated subframe bitmap included in the MTC subband allocation information.

Example 68 is the wireless communication method of Example 63, wherein the received MTC subband allocation information is included in a received master information block (MIB).

Example 69 is the wireless communication method of Example 63, wherein the received MTC subband allocation information is included in a received system information block (SIB).

Example 70 is the wireless communication method of Example 63, wherein the received MTC subband allocation information is included in a received radio resource control (RRC) message.

Example 71 is at least one non-transitory computer-readable storage medium comprising a set of instructions that, in response to being executed on a computing device, causes the computing device to perform a wireless communication method according to any of Examples 63 to 70.

Example 72 is an apparatus comprising means for performing a wireless communication method according to any of Examples 63 to 70.

Example 73 is a system comprising the apparatus of Example 72, at least one radio frequency (RF) transceiver, and at least one RF antenna.

Example 74 is the system of Example 73, comprising a touch screen display.

Example 75 is at least one non-transitory computer-readable storage medium comprising a set of wireless communication instructions, which, in response to being executed at an evolved Node B (eNB), causes the eNB to perform the following operations: determine a machine type communication (MTC) subband allocation, the MTC subband allocation comprising allocating multiple subcarriers to an MTC subband of a system bandwidth of the eNB, the MTC subband allocation defining one or more MTC direct current (DC) subcarriers among the multiple subcarriers; and send a signal comprising MTC subband allocation information for indicating the MTC subband allocation.

Example 76 is at least one non-transitory computer-readable storage medium of Example 75, comprising wireless communication instructions that, in response to being executed at an eNB, cause the eNB to generate an encoded bit stream comprising data for an MTC user equipment (UE), generate a modulated symbol stream based on the encoded bit stream, generate a second signal comprising data for the MTC UE based on the modulated symbol stream, and send the second signal.

Example 77 is at least one non-transitory computer-readable storage medium of Example 76, comprising wireless communication instructions that, in response to being executed at an eNB, cause the eNB to generate a rate-matched and coded bit stream based on the coded bit stream by applying rate matching to one or more MTC DC subcarriers, and generate a modulated symbol stream based on the rate-matched and coded bit stream.

Example 78 is at least one non-transitory computer-readable storage medium of Example 76, comprising wireless communication instructions that, in response to being executed at an eNB, cause the eNB to generate a stream of symbols based on the coded bit stream, and puncture the stream of symbols by applying puncturing to one or more MTC DC subcarriers to obtain a modulated symbol stream.

Example 79 is the at least one non-transitory computer-readable storage medium of Example 75, the MTC subband allocation comprising a predefined MTC subband allocation for a system bandwidth, the MTC subband allocation information comprising a system bandwidth parameter indicating the system bandwidth.

Example 80 is the at least one non-transitory computer-readable storage medium of Example 75, the MTC subband allocation information being configured to indicate a duration of the MTC subband allocation.

Example 81 is the at least one non-transitory computer-readable storage medium of Example 75, the MTC subband allocation information comprising an MTC allocation subframe bitmap indicating one or more subframes to which the MTC subband allocation is applied.

Example 82 is the at least one non-transitory computer-readable storage medium of Example 75, the MTC subband allocation comprising a dynamically configured MTC subband allocation for a user equipment (UE).

Example 83 is a wireless communication device comprising: a device for identifying a machine type communication (MTC) subband allocation based on received MTC subband allocation information, the MTC subband allocation comprising allocating multiple subcarriers to an MTC subband of a system bandwidth of a serving cell of a user equipment (UE), the MTC subband allocation defining at least one MTC direct current (DC) subcarrier among the multiple subcarriers; and a device for receiving transmissions via the MTC subband according to the MTC subband allocation.

Example 84 is the wireless communication device of Example 83, comprising: a device for identifying the MTC subband allocation based on a system bandwidth parameter included in the MTC subband allocation information, the system bandwidth parameter being used to identify the system bandwidth.

Example 85 is the wireless communication apparatus of Example 83, comprising means for identifying one or more subframes to which the MTC subband allocation is to be applied based on the MTC subband allocation information.

Example 86 is the wireless communication apparatus of Example 85, comprising means for identifying one or more subframes based on an MTC allocation duration parameter included in the MTC subband allocation information, the MTC allocation duration parameter being used to indicate a duration of the MTC subband allocation.

Example 87 is the wireless communication apparatus of Example 85, comprising means for identifying one or more subframes based on an MTC allocated subframe bitmap included in the MTC subband allocation information.

Example 88 is the wireless communication device of Example 83, wherein the received MTC subband allocation information is included in a received master information block (MIB).

Example 89 is the wireless communication device of Example 83, wherein the received MTC subband allocation information is included in a received system information block (SIB).

Example 90 is the wireless communication device of Example 83, the received MTC subband allocation information being included in a received radio resource control (RRC) message.

Example 91 is a system comprising: a wireless communication device according to any of Examples 83 to 90, at least one radio frequency (RF) transceiver, and at least one RF antenna.

Example 92 is the system of Example 91, comprising a touch screen display.

Example 93 is a wireless communication method, comprising: determining, by a processing circuit at an evolved Node B (eNB), a machine type communication (MTC) subband allocation, the MTC subband allocation comprising allocating multiple subcarriers to an MTC subband of a system bandwidth of the eNB, the MTC subband allocation being used to define one or more MTC direct current (DC) subcarriers among the multiple subcarriers; and sending a signal comprising MTC subband allocation information indicating the MTC subband allocation.

Example 94 is the wireless communication method of Example 93, comprising: generating an encoded bit stream including data for an MTC user equipment (UE), generating a modulated symbol stream based on the encoded bit stream, generating a second signal including data for the MTC UE based on the modulated symbol stream, and sending the second signal.

Example 95 is the wireless communication method of Example 94, comprising: applying rate matching to one or more MTC DC subcarriers, generating a rate-matched and coded bit stream based on the coded bit stream, and generating a modulated symbol stream based on the rate-matched and coded bit stream.

Example 96 is the wireless communication method of Example 94, comprising: generating a stream of symbols based on the coded bit stream, and puncturing the stream of symbols by applying puncturing to one or more MTC DC subcarriers to obtain a modulated symbol stream.

Example 97 is the wireless communication method of Example 93, wherein the MTC subband allocation includes a predefined MTC subband allocation for a system bandwidth, and the MTC subband allocation information includes a system bandwidth parameter for indicating the system bandwidth.

Example 98 is the wireless communication method of Example 93, wherein the MTC subband allocation information is used to indicate a duration of the MTC subband allocation.

Example 99 is the wireless communication method of Example 93, the MTC subband allocation information comprising an MTC allocated subframe bitmap indicating one or more subframes to which the MTC subband allocation is applied.

Example 100 is the wireless communication method of Example 93, the MTC subband allocation comprising dynamically configured MTC subband allocation for a user equipment (UE).

Example 101 is at least one non-transitory computer-readable storage medium comprising a set of instructions that, in response to being executed on a computing device, cause the computing device to perform a wireless communication method according to any of Examples 93 to 100.

Example 102 is an apparatus comprising means for performing a wireless communication method according to any of Examples 93 to 100.

Example 103 is a system comprising: the device of Example 102, at least one radio frequency (RF) transceiver, and at least one RF antenna.

Example 104 is an evolved Node B (eNB) comprising logic, at least a portion of which is located in hardware, for assigning a machine type communication (MTC) user equipment (UE) to an MTC subband; sending MTC subband allocation information to indicate an MTC subband allocation for the MTC subband, the MTC subband allocation being used to allocate multiple subcarriers to the MTC subband and define one or more MTC direct current (DC) subcarriers among the multiple subcarriers; and the logic being used to send a message including data for the MTC UE via the assigned MTC subband.

Example 105 is the eNB of Example 104, the logic being to select the assigned MTC subband from a plurality of defined MTC subbands within a system bandwidth of the eNB.

Example 106 is the eNB of Example 105, at least one of the plurality of defined MTC subbands overlapping with at least one other of the plurality of defined MTC subbands.

Example 107 is the eNB of Example 105, at least one of the plurality of defined MTC subbands comprising a plurality of MTC DC subcarriers.

Example 108 is the eNB of Example 105, wherein at least one of the plurality of defined MTC subbands overlaps with a DC subcarrier of a system bandwidth of the eNB.

Example 109 is the eNB of example 105, the logic being to dynamically configure the plurality of defined subbands.

Example 110 is the eNB of Example 104, and the MTC subband allocation information is used to identify a starting frequency position of the assigned MTC subband.

Example 111 is the eNB of Example 104, the logic being to determine a subsequent time at which to assign a second MTC subband to the MTC UE based on a minimum switching time of the MTC subband assignment.

Example 112 is the eNB of any of Examples 104 to 111, comprising at least one radio frequency (RF) transceiver and at least one RF antenna.

Example 113 is a user equipment (UE) comprising: logic, at least a portion of which is located in hardware, the logic being used to independently identify a machine type communication (MTC) subband allocation for both a downlink (DL) and an uplink (UL) based on received MTC subband allocation information, the MTC subband allocation comprising independently allocating multiple subcarriers to an MTC subband of a system bandwidth of a serving cell of the UE for both the downlink (DL) and the uplink (UL), the MTC subband allocation being used to define at least one MTC direct current (DC) subcarrier among the multiple subcarriers for the downlink (DL); and a radio interface for receiving transmissions via the MTC subband according to the MTC subband allocation.

Example 114 is the UE of Example 113, the MTC subband allocation information comprises a system bandwidth parameter identifying a system bandwidth, and the logic identifies the MTC subband allocation based on the system bandwidth parameter.

Example 115 is the UE of Example 113, wherein the MTC subband allocation applies to the one or more subframes, and the logic identifies the one or more subframes based on the MTC subband allocation information.

Example 116 is the UE of Example 115, the MTC subband allocation information comprising an MTC allocation duration parameter for indicating a duration of the MTC subband allocation, the logic identifying the one or more subframes based on the MTC allocation duration parameter.

Example 117 is the UE of Example 113, the MTC subband allocation information comprises an MTC allocated subframe bitmap, and the logic identifies one or more subframes based on the MTC allocated subframe bitmap.

Example 118 is the UE of Example 113, the received MTC subband allocation information being included in a received master information block (MIB).

Example 119 is the UE of Example 113, wherein the received MTC subband allocation information is included in a received system information block (SIB).

Example 120 is the UE of Example 119, wherein the received system information block (SIB) is a new SIB defined for the MTC UE in addition to or instead of one or more legacy SIBs.

Example 121 is the UE of Example 113, wherein the received MTC subband allocation information is included in a received radio resource control (RRC) message.

Example 122 is the UE of Example 113, comprising a touch screen display.

Example 123 is an evolved Node B (eNB) comprising: logic, at least a portion of which is located in hardware, the logic for independently determining a machine type communication (MTC) subband allocation for both a downlink (DL) and an uplink (UL), the MTC subband allocation comprising allocating a plurality of subcarriers to an MTC subband of a system bandwidth of the eNB, the MTC subband allocation being used to define one or more MTC direct current (DC) subcarriers in the plurality of subcarriers for the downlink (DL); and a radio interface for sending a signal comprising MTC subband allocation information indicating the MTC subband allocation.

Example 124 is the eNB of Example 123, the logic being configured to generate a coded bit stream comprising data for an MTC user equipment (UE), and to generate a modulated symbol stream based on the coded bit stream, the radio interface generating a second signal comprising data for the MTC UE based on the modulated symbol stream and transmitting the second signal.

Example 125 is the eNB of example 124, the logic being for generating a rate-matched and coded bit stream based on the coded bit stream by applying rate matching to one or more MTC DC subcarriers, and generating a modulated symbol stream based on the rate-matched and coded bit stream.

Example 126 is the eNB of Example 124, the logic to generate a burst of symbols based on the coded bit stream, and puncture the burst of symbols by applying puncturing to one or more MTC DC subcarriers to obtain a modulated symbol stream.

Example 127 is the eNB of Example 123, the MTC subband allocation comprises a predefined MTC subband allocation for a system bandwidth, and the MTC subband allocation information comprises a system bandwidth parameter for indicating the system bandwidth.

Example 128 is the eNB of Example 123, and the MTC subband allocation information is used to indicate a duration of the MTC subband allocation.

Example 129 is the eNB of Example 123, the MTC subband allocation information comprising an MTC allocated subframe bitmap indicating one or more subframes to which the MTC subband allocation is applied.

Example 130 is the eNB of Example 123, the MTC subband allocation comprising dynamically configured MTC subband allocation for a user equipment (UE).

Example 131 is at least one non-transitory computer-readable storage medium comprising a set of instructions that, in response to being executed at an evolved Node B (eNB), cause the eNB to perform the following operations: independently assigning MTC subbands to machine type communication (MTC) user equipment (UE) for both downlink (DL) and uplink (UL); sending MTC subband allocation information to indicate an MTC subband allocation for the MTC subband, the MTC subband allocation being used to allocate multiple subcarriers to the MTC subband and defining one or more MTC direct current (DC) subcarriers among the multiple subcarriers, sending a message including data or a physical signal for the MTC UE via the assigned MTC subband on the downlink (DL), and receiving a message including data or a physical signal from the MTC UE via the assigned MTC subband on the uplink (UL).

Example 132 is the at least one non-transitory computer-readable storage medium of Example 131, comprising instructions that, in response to being executed at an eNB, cause the eNB to select the assigned MTC subband from a plurality of defined MTC subbands within a system bandwidth of the eNB.

Example 133 is the at least one non-transitory computer-readable storage medium of Example 132, at least one MTC subband of the plurality of defined MTC subbands overlapping with at least one other MTC subband of the plurality of defined MTC subbands.

Example 134 is the at least one non-transitory computer-readable storage medium of Example 132, at least one MTC subband of the plurality of defined MTC subbands comprising a plurality of MTC DC subcarriers.

Example 135 is the at least one non-transitory computer-readable storage medium of Example 132, at least one MTC subband of the plurality of defined MTC subbands overlapping with a DC subcarrier of a system bandwidth of the eNB.

Example 136 is the at least one non-transitory computer-readable storage medium of Example 132, comprising instructions that, in response to being executed at an eNB, cause the eNB to dynamically configure a plurality of defined subbands.

Example 137 is at least one non-transitory computer-readable storage medium of Example 131, comprising instructions that, in response to being executed at an eNB, cause the eNB to configure one or more subbands using dedicated RRC signaling or layer 1 signaling in a UE-specific manner.

Example 138 is the at least one non-transitory computer-readable storage medium of Example 131, the MTC subband allocation information being for identifying a starting frequency position of the assigned MTC subband.

Example 139 is at least one non-transitory computer-readable storage medium of Example 131, comprising instructions that, in response to being executed at an eNB, cause the eNB to determine a subsequent time at which to assign a second MTC subband to the MTC UE based on a minimum switching time for the MTC subband assignment.

Example 140 is the at least one non-transitory computer-readable storage medium of Example 139, wherein a switching time from one MTC subband to another MTC subband within the system bandwidth does not occur one or more subframes or radio frames earlier.

Example 141 is the at least one non-transitory computer-readable storage medium of Example 139, wherein the switching time is predefined, or indicated via higher layer signaling, or indicated via dynamic signaling.

Many specific details have been set forth herein to provide a thorough understanding of the embodiments. However, those skilled in the art will appreciate that the embodiments may be implemented without these specific details. In other instances, well-known operations, components, and circuits are not described in detail to avoid obscuring the embodiments. It will be understood that the specific structural and functional details disclosed herein may be representative and do not necessarily limit the scope of the embodiments.

Some embodiments may be described using the expressions "coupled" and "connected" and their derivatives. These terms are not intended to be synonymous with each other. For example, some embodiments may be described using the terms "connected" and/or "coupled" to indicate that two or more elements are in direct physical or electrical contact with each other. However, the term "coupled" may also mean that two or more elements are not in direct contact with each other, but still cooperate or interact with each other.

Unless specifically stated otherwise, it is understood that terms such as "process," "calculate," "calculate," "determine," etc. refer to the following actions and/or processes of a computer or computing system or similar electronic computing device: these actions and/or processes manipulate and/or transform data represented as physical quantities (e.g., electronic) within the registers and/or memories of the computing system into other data similarly represented as physical quantities within the memories, registers, or other such information storage, transmission, or display devices of the computing system. The embodiments are not limited in this context.

It should be noted that the methods described herein do not have to be executed in the order described or in any particular order. In addition, the various activities described for the methods identified herein can be executed in serial or parallel fashion.

Although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement intended to achieve the same purpose may replace the specific embodiments shown. This disclosure is intended to encompass any and all adaptations or variations of the various embodiments. It will be understood that the above description is provided in an illustrative and non-restrictive manner. Other embodiments and combinations of the above embodiments not specifically described herein will be apparent to those skilled in the art upon reading the above description. Thus, the scope of each embodiment includes any other application using the above compositions, structures, and methods.

It is emphasized that the Abstract of the present disclosure is provided to comply with 37 C.F.R. §1.72(b), which requires that the abstract will allow the reader to quickly ascertain the nature of the technical disclosure. The Abstract is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. Furthermore, in the foregoing Detailed Description, it can be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Accordingly, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate preferred embodiment. In the appended claims, the terms "including" and "in which" are used as plain-English equivalents of the respective terms "comprising" and "wherein," respectively. Moreover, the terms "first," "second," and "third," etc. are used merely as labels and are not intended to impose numerical requirements on their objects.

Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims (30)

1. A user equipment (UE), comprising: The logic, at least a portion of which resides in hardware, is used to identify an MTC subband allocation based on received Machine Type Communication (MTC) subband allocation information. The MTC subband allocation includes allocating multiple subcarriers to an MTC subband of the system bandwidth of the UE's serving cell. The MTC subband allocation defines multiple MTC DC subcarriers among the multiple subcarriers in the MTC subband. The MTC subband allocation is applied to one or more subframes, wherein for each of the one or more subframes, the definition of the multiple subcarriers is applied only during an Orthogonal Frequency Division Multiplexing (OFDM) symbol following the control region of that subframe. The MTC subband allocation information includes an MTC allocation duration parameter indicating the duration of the MTC subband allocation. The logic is used to identify the one or more subframes based on the MTC allocation duration parameter. A radio interface for receiving transmissions via the MTC subband according to the allocation of the MTC subband. 2. The UE as described in claim 1, wherein the MTC subband allocation information includes a system bandwidth parameter that identifies the system bandwidth, and the logic is used to identify the MTC subband allocation based on the system bandwidth parameter. 3. The UE as described in claim 1, wherein the logic is used to identify the one or more subframes based on the MTC subband allocation information. 4. The UE as described in claim 1, wherein the MTC subband allocation information includes an MTC allocation subframe bitmap, and the logic is used to identify the one or more subframes based on the MTC allocation subframe bitmap. 5. The UE as described in claim 1, wherein the received MTC subband allocation information is included in the received main information block (MIB). 6. The UE as described in claim 1, wherein the received MTC subband allocation information is included in the received System Information Block (SIB). 7. The UE as described in claim 1, wherein the received MTC subband allocation information is included in the received Radio Resource Control (RRC) message. 8. The UE as claimed in any one of claims 1-7, comprising a touchscreen display. 9. An evolved node B, or eNB, includes: Logic, at least a portion of which resides in hardware, is used to determine machine-type communication (MTC) subband allocation, the MTC subband allocation comprising allocating multiple subcarriers to an MTC subband of the eNB's system bandwidth, the MTC subband allocation defining multiple MTC DC subcarriers among the multiple subcarriers of the MTC subband, the MTC subband allocation being applied to one or more subframes, wherein for each of the one or more subframes, the definition of the multiple subcarriers is applied only during an Orthogonal Frequency Division Multiplexing (OFDM) symbol following the control region of that subframe, the MTC subband allocation information including an MTC allocation duration parameter indicating the duration of the MTC subband allocation; and A radio interface for transmitting signals, including MTC subband allocation information for indicating the MTC subband allocation. 10. The eNB of claim 9, wherein the logic is configured to generate an encoded bit stream comprising data for an MTC user equipment (UE), and to generate a modulated symbol stream based on the encoded bit stream, and the radio interface is configured to generate a second signal comprising data for the MTC UE based on the modulated symbol stream and to transmit the second signal. 11. The eNB of claim 10, wherein the logic is configured to generate a rate-matched encoded bit stream based on the encoded bit stream by applying rate matching to the one or more MTC DC subcarriers, and to generate the modulated symbol stream based on the rate-matched and encoded bit streams. 12. The eNB of claim 10, wherein the logic is configured to generate a string of symbols based on the encoded bit stream, and to puncture the string of symbols by applying puncturing to the one or more MTC DC subcarriers to obtain the modulated symbol stream. 13. The eNB of claim 9, wherein the MTC subband allocation includes a predefined MTC subband allocation for the system bandwidth, and the MTC subband allocation information includes system bandwidth parameters for indicating the system bandwidth. 14. The eNB of claim 9, wherein the MTC subband allocation information includes an MTC allocation subframe bitmap, the MTC allocation subframe bitmap indicating one or more subframes to which the MTC subband allocation is applied. 15. The eNB of claim 9, wherein the MTC subband allocation includes dynamically configured MTC subband allocation for the user equipment (UE). 16. A wireless communication device, comprising: Apparatus for assigning MTC subbands to machine-type communication MTC user equipment (UE); Means for transmitting MTC subband allocation information to indicate MTC subband allocation for the MTC subband, the MTC subband allocation being used to allocate a plurality of subcarriers to the MTC subband, and defining a plurality of MTC DC subcarriers among the plurality of subcarriers in the MTC subband, the MTC subband allocation being applied to one or more subframes, wherein for each of the one or more subframes, the definition of the plurality of subcarriers is applied only during an Orthogonal Frequency Division Multiplexing (OFDM) symbol following the control region of that subframe, the MTC subband allocation information including an MTC allocation duration parameter indicating the duration of the MTC subband allocation; and A means for transmitting a message including data for the MTC UE via an assigned MTC subband. 17. The wireless communication device of claim 16, further comprising means for selecting the assigned MTC subband from a plurality of defined MTC subbands within the system bandwidth of the evolved Node B, i.e., the eNB. 18. The wireless communication device of claim 17, wherein at least one of the plurality of defined MTC subbands overlaps with at least one other MTC subband among the plurality of defined MTC subbands. 19. The wireless communication device of claim 17, wherein at least one of the plurality of defined MTC subbands overlaps with the DC subcarrier of the system bandwidth of the eNB. 20. The wireless communication device of claim 17, further comprising means for dynamically configuring a plurality of defined subbands. 21. The wireless communication device of claim 16, wherein the MTC subband allocation information is used to identify the starting frequency position of the assigned MTC subband. 22. The wireless communication device of claim 16, further comprising means for determining a subsequent time based on a minimum handover time for MTC subband assignment, at which a second MTC subband is assigned to the MTC UE. 23. A wireless communication method, comprising: Assign MTC subbands to machine-type communication MTC user equipment (UE); MTC subband allocation information is sent to indicate an MTC subband allocation for the MTC subband, the MTC subband allocation being used to allocate multiple subcarriers to the MTC subband, and defining multiple MTC DC subcarriers among the multiple subcarriers in the MTC subband, the MTC subband allocation being applied to one or more subframes, wherein for each of the one or more subframes, the definition of the multiple subcarriers is applied only during the Orthogonal Frequency Division Multiplexing (OFDM) symbol following the control region of that subframe, the MTC subband allocation information including an MTC allocation duration parameter indicating the duration of the MTC subband allocation; and Messages containing data for the MTC UE are transmitted via the assigned MTC subband. 24. The wireless communication method of claim 23, comprising selecting the assigned MTC subband from a plurality of defined MTC subbands within the system bandwidth of the evolved Node B, i.e., the eNB. 25. The wireless communication method of claim 24, wherein at least one of the plurality of defined MTC subbands overlaps with at least one other MTC subband among the plurality of defined MTC subbands. 26. The wireless communication method of claim 24, wherein at least one of the plurality of defined MTC subbands overlaps with the DC subcarrier of the system bandwidth of the eNB. 27. The wireless communication method of claim 24, comprising dynamically configuring a plurality of defined subbands. 28. The wireless communication method of claim 23, wherein the MTC subband allocation information is used to identify the starting frequency position of the assigned MTC subband. 29. The wireless communication method of claim 23, further comprising determining a subsequent time based on the minimum handover time of MTC subband assignment, and assigning a second MTC subband to the MTC UE at the subsequent time. 30. At least one non-transitory computer-readable storage medium comprising a set of instructions that, in response to being executed at an evolved Node B, i.e., an eNB, causes the eNB to perform the wireless communication method of any one of claims 23-29.