WO2018031927A1

WO2018031927A1 - Narrowband definitions, resource allocation, and frequency hopping for user equipment

Info

Publication number: WO2018031927A1
Application number: PCT/US2017/046580
Authority: WO
Inventors: Seunghee Han; Debdeep CHATTERJEE; Qiaoyang Ye
Original assignee: Intel IP Corporation
Priority date: 2016-08-12
Filing date: 2017-08-11
Publication date: 2018-02-15
Also published as: CN109479280B; CN109479280A

Abstract

Described is an apparatus of a User Equipment (UE). The apparatus may comprise a first circuitry and a second circuitry. The first circuitry may be operable to define a first set of one or more Extended Narrowbands (ENBs) for Downlink (DL) transmissions spanning a first set of more than six Resource Blocks (RBs) of the system bandwidth. The second circuitry may be operable to define a second set of one or more ENBs for Uplink (UL) transmissions spanning a second set of more than six RBs of the system bandwidth. The apparatus may also comprise a memory to store one or more parameters of the first set of ENBs and one or more parameters of the second set of ENBs.asdf

Description

NARROWBAND DEFINITIONS, RESOURCE ALLOCATION,

AND FREQUENCY HOPPING FOR USER EQUIPMENT

CLAIM OF PRIORITY

[0001] The present application claims priority under 35 U.S.C § 119(e) to United

States Provisional Patent Application Serial Number 62/374,627 filed August 12, 2016 and entitled "Narrowband Definitions, Resource Allocation, And Frequency Hopping For Further Enhanced Machine Type Communication User Equipment With Larger Bandwidth Support," and to United States Provisional Patent Application Serial Number 62/401,431 filed

September 29, 2016 and entitled "Narrowband Definitions, Resource Allocation, And Frequency Hopping For FeMTC UEs With Larger Bandwidth Support," which are herein incorporated by reference in their entirety.

BACKGROUND

[0002] A variety of wireless cellular communication systems have been implemented or are being proposed, including a 3rd Generation Partnership Project (3GPP) Universal Mobile Telecommunications System (UMTS), a 3GPP Long-Term Evolution (LTE) system, and a 3GPP LTE-Advanced (LTE-A) system. Next-generation wireless cellular

communication systems based upon LTE and LTE-A systems are being developed, such as a fifth generation (5G) wireless system / 5G mobile networks system. Next-generation wireless cellular communication systems may provide support for massive numbers of user devices like Narrowband Internet-of-Things (NB-IoT) devices, Cellular Internet-of-Things (CIoT) devices, or Machine-Type Communication (MTC) devices. Such devices may have very low device complexity, may be latency -tolerant, and may be designed for low throughput and very low power consumption.

BRIEF DESCRIPTION OF THE DRAWINGS

[0003] The embodiments of the disclosure will be understood more fully from the detailed description given below and from the accompanying drawings of various embodiments of the disclosure. However, while the drawings are to aid in explanation and understanding, they are only an aid, and should not be taken to limit the disclosure to the specific embodiments depicted therein.

l [0004] Figs. 1A-1B illustrate narrowbands (NBs) for Bandwidth reduced Low complexity (BL) User Equipments (UEs) for different LTE system bandwidths (BWs), in accordance with some embodiments of the disclosure.

[0005] Fig. 2 illustrates Extended Narrowband (ENB) definitions for a 15 megahertz

(MHz) system BW, in accordance with some embodiments of the disclosure.

[0006] Fig. 3 illustrates ENB definitions for a 15 MHz system BW and a 20 MHz system BW, in accordance with some embodiments of the disclosure.

[0007] Fig. 4 illustrates fragmentation of Physical Downlink Shared Channel

(PDSCH) / Physical Uplink Shared Channel (PUSCH) allocation with Frequency Hopping

(FH) with fragmentation at a band edge, in accordance with some embodiments of the disclosure.

[0008] Fig. 5 illustrates PDSCH / PUSCH allocation with FH based on a reference

NB, in accordance with some embodiments of the disclosure.

[0009] Fig. 6 illustrates an Evolved Node B (eNodeB) and a UE, in accordance with some embodiments of the disclosure.

[0010] Fig. 7 illustrates hardware processing circuitries for a UE for supporting

ENBs, in accordance with some embodiments of the disclosure.

[0011] Fig. 8 illustrates hardware processing circuitries for an eNodeB for supporting

ENBs, in accordance with some embodiments of the disclosure.

[0012] Fig. 9 illustrates methods for a UE for supporting ENBs, in accordance with some embodiments of the disclosure.

[0013] Fig. 10 illustrates methods for an eNodeB for supporting ENBs, in accordance with some embodiments of the disclosure.

[0014] Fig. 11 illustrates example components of a device, in accordance with some embodiments of the disclosure.

[0015] Fig. 12 illustrates example interfaces of baseband circuitry, in accordance with some embodiments of the disclosure.

DETAILED DESCRIPTION

[0016] Various wireless cellular communication systems have been implemented or are being proposed, including a 3rd Generation Partnership Project (3GPP) Universal Mobile Telecommunications System (UMTS), a 3GPP Long-Term Evolution (LTE) system, a 3GPP LTE-Advanced system, and a 5th Generation wireless system / 5th Generation mobile networks (5G) system / 5th Generation new radio (NR) system. [0017] Some objectives for Further Enhanced Machine-Type Communication

(FeMTC) may include: higher data rates; specification of Hybrid Automatic Repeat Request (HARQ) Acknowledgement (HARQ-ACK) bundling in Coverage Enhancement (CE) mode A in Half-Duplex Frequency -Division Duplex (HD-FDD); larger maximum Transport Block Size (TBS), larger maximum Physical Downlink Shared Channel (PDSCH) / Physical Uplink Shared Channel (PUSCH) channel bandwidth in a connected mode (at least in CE mode A, which may enhance support for voice, audio streaming, or other applications and scenarios); and up to 10 Downlink (DL) HARQ processes in CE mode A in Full-Duplex Frequency- Division Duplex (FD-FDD).

[0018] Based upon up to 5 megahertz (MHz) bandwidth (BW) for a higher data rate operation of FeMTC, two classes of FeMTC devices may be envisioned: those that support this feature, and those that don't. Devices that support this feature will have to operate at a maximum BW, and PDSCH and PUSCH resource allocations in frequency dimension may span more than a single narrowband (NB), as defined by a set of 6 contiguous-in-frequency Physical Resource Blocks (PRBs). (While this new class of devices might have a maximum supported BW of 5 MHz, the embodiments discussed herein may be straightforwardly applied to other values of supported max UE BW greater than 1.4 MHz.)

[0019] In 3GPP Release- 13 enhanced Machine-Type Communication (eMTC),

Bandwidth reduced Low complexity (BL) User Equipments (UEs), or UEs in coverage enhancement (CE UEs), may support frequency hopping (FH) for MTC Physical Downlink Control Channel (MPDCCH) and PDSCH in the DL over either 2 or 4 NBs, and for PUSCH in the UL over 2 NBs over an entire LTE system BW. An initial location of the NB may be determined based on an indication in Downlink Control Information (DCI) while cell-specific offsets may be used to determine the other NBs. A frequency hopping may occur in a cyclic manner (e.g., as a first NB, a second NB, the first NB, and so on for a case of 2 NBs, or as a first NB, a second NB, a third NB, a fourth NB, the first NB, and so on for a case of 4 NBs).

[0020] An enabling or disabling of FH may be configured via UE-specific higher layer signaling (e.g., dedicated Radio Resource Control (RRC) signaling). Furthermore, for unicast PDSCH and PUSCH, UEs in CE mode A (e.g., UEs requiring no repetitions, or a relatively small number of repetitions) may be instructed to use FH, or to not use FH (once enabled by a higher-layer configuration) in a dynamic manner via DCI indicating a DL assignment or an Uplink (UL) grant. [0021] A cell-specifically configured offset for FH may be indicated in terms of NBs, and a wrap-around may be applied at one or more edges (or ends) of an LTE band. For instance, if an initial NB is NBO, then a hopped NB may be given by:

NB1 = (NBO + FH_offset) modulo N_NB

Where: FH offset may be a cell-specific configured FH offset; and N NB may be the number of 6-PRB NBs in an LTE system BW.

[0022] For a class of FeMTC UEs supporting larger BW for PDSCH and PUSCH, a resource allocation may be larger than a single NB. In such cases, direct application of FH as defined for 3GPP Release-13 BL/CE UEs may result in fragmentation of a PDSCH or PUSCH bandwidth at one or more LTE band edges due to a wrap-around operation.

[0023] Discussed herein are Extended Narrowbands (ENBs) for such UEs. Also discussed herein are new resource allocation mechanisms based on ENBs. Additionally, methods to support FH for FeMTC UEs with larger BW support are discussed herein, wherein some of the options may be based on ENBs.

[0024] In the following description, numerous details are discussed to provide a more thorough explanation of embodiments of the present disclosure. It will be apparent to one skilled in the art, however, that embodiments of the present disclosure may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form, rather than in detail, in order to avoid obscuring embodiments of the present disclosure.

[0025] Note that in the corresponding drawings of the embodiments, signals are represented with lines. Some lines may be thicker, to indicate a greater number of constituent signal paths, and/or have arrows at one or more ends, to indicate a direction of information flow. Such indications are not intended to be limiting. Rather, the lines are used in connection with one or more exemplary embodiments to facilitate easier understanding of a circuit or a logical unit. Any represented signal, as dictated by design needs or preferences, may actually comprise one or more signals that may travel in either direction and may be implemented with any suitable type of signal scheme.

[0026] Throughout the specification, and in the claims, the term "connected" means a direct electrical, mechanical, or magnetic connection between the things that are connected, without any intermediary devices. The term "coupled" means either a direct electrical, mechanical, or magnetic connection between the things that are connected or an indirect connection through one or more passive or active intermediary devices. The term "circuit" or "module" may refer to one or more passive and/or active components that are arranged to cooperate with one another to provide a desired function. The term "signal" may refer to at least one current signal, voltage signal, magnetic signal, or data/clock signal. The meaning of "a," "an," and "the" include plural references. The meaning of "in" includes "in" and "on."

[0027] The terms "substantially," "close," "approximately," "near," and "about" generally refer to being within +/- 10% of a target value. Unless otherwise specified the use of the ordinal adjectives "first," "second," and "third," etc., to describe a common object, merely indicate that different instances of like objects are being referred to, and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner.

[0028] It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments of the invention described herein are, for example, capable of operation in other orientations than those illustrated or otherwise described herein.

[0029] The terms "left," "right," "front," "back," "top," "bottom," "over," "under," and the like in the description and in the claims, if any, are used for descriptive purposes and not necessarily for describing permanent relative positions.

[0030] For purposes of the embodiments, the transistors in various circuits, modules, and logic blocks are Tunneling FETs (TFETs). Some transistors of various embodiments may comprise metal oxide semiconductor (MOS) transistors, which include drain, source, gate, and bulk terminals. The transistors may also include Tri-Gate and FinFET transistors, Gate All Around Cylindrical Transistors, Square Wire, or Rectangular Ribbon Transistors or other devices implementing transistor functionality like carbon nanotubes or spintronic devices. MOSFET symmetrical source and drain terminals i.e., are identical terminals and are interchangeably used here. A TFET device, on the other hand, has asymmetric Source and Drain terminals. Those skilled in the art will appreciate that other transistors, for example, Bi-polar junction transistors-BJT PNP/NPN, BiCMOS, CMOS, etc., may be used for some transistors without departing from the scope of the disclosure.

[0031] For the purposes of the present disclosure, the phrases "A and/or B" and "A or

B" mean (A), (B), or (A and B). For the purposes of the present disclosure, the phrase "A, B, and/or C" means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B and C).

[0032] In addition, the various elements of combinatorial logic and sequential logic discussed in the present disclosure may pertain both to physical structures (such as AND gates, OR gates, or XOR gates), or to synthesized or otherwise optimized collections of devices implementing the logical structures that are Boolean equivalents of the logic under discussion.

[0033] In addition, for purposes of the present disclosure, the term "eNodeB" may refer to a legacy LTE capable Evolved Node-B (eNodeB), a next-generation or 5G capable eNodeB, a millimeter-wave (mmWave) capable eNodeB or an mmWave small cell, an Access Point (AP), a Narrowband Internet-of-Things (NB-IoT) capable eNodeB, a Cellular Intemet-of-Things (CIoT) capable eNodeB, a Machine-Type Communication (MTC) capable eNodeB, and/or another base station for a wireless communication system. For purposes of the present disclosure, the term "UE" may refer to a legacy LTE capable UE, a next- generation or 5G capable UE, an mmWave capable UE, a Station (STA), an NB-IoT capable UE, a CIoT capable UE, an MTC capable UE, and/or another mobile equipment for a wireless communication system.

[0034] Various embodiments of eNodeBs and/or UEs discussed below may process one or more transmissions of various types. Some processing of a transmission may comprise demodulating, decoding, detecting, parsing, and/or otherwise handling a transmission that has been received. In some embodiments, an eNodeB or UE processing a transmission may determine or recognize the transmission's type and/or a condition associated with the transmission. For some embodiments, an eNodeB or UE processing a transmission may act in accordance with the transmission's type, and/or may act

conditionally based upon the transmission's type. An eNodeB or UE processing a transmission may also recognize one or more values or fields of data carried by the transmission. Processing a transmission may comprise moving the transmission through one or more layers of a protocol stack (which may be implemented in, e.g., hardware and/or software-configured elements), such as by moving a transmission that has been received by an eNodeB or a UE through one or more layers of a protocol stack.

[0035] Various embodiments of eNodeBs and/or UEs discussed below may also generate one or more transmissions of various types. Some generating of a transmission may comprise modulating, encoding, formatting, assembling, and/or otherwise handling a transmission that is to be transmitted. In some embodiments, an eNodeB or UE generating a transmission may establish the transmission's type and/or a condition associated with the transmission. For some embodiments, an eNodeB or UE generating a transmission may act in accordance with the transmission's type, and/or may act conditionally based upon the transmission's type. An eNodeB or UE generating a transmission may also determine one or more values or fields of data carried by the transmission. Generating a transmission may comprise moving the transmission through one or more layers of a protocol stack (which may be implemented in, e.g., hardware and/or software-configured elements), such as by moving a transmission to be sent by an eNodeB or a UE through one or more layers of a protocol stack.

[0036] In various embodiments, resources may span various Resource Blocks (RBs),

Physical Resource Blocks (PRBs), and/or time periods (e.g., frames, subframes, and/or slots) of a wireless communication system. In some contexts, allocated resources (e.g., channels, Orthogonal Frequency -Division Multiplexing (OFMD) symbols, subcarrier frequencies, resource elements (REs), and/or portions thereof) may be formatted for (and prior to) transmission over a wireless communication link. In other contexts, allocated resources (e.g., channels, OFDM symbols, subcarrier frequencies, REs, and/or portions thereof) may be detected from (and subsequent to) reception over a wireless communication link.

[0037] Various embodiments discussed herein may pertain to extended NBs for

FeMTC UEs with UE BW larger than 6 PRBs. In some embodiments, for 3 GPP Release- 13 BL/CE UEs, an NB may be defined as a set of 6 contiguous PRBs. NBs may be non-overlapping. A total number of DL NBs in a system bandwidth may be fixed ⁶ and a total number of UL NBs in a system bandwidth is fixed at

In various embodiments, remaining RBs may be divided evenly at both edges (or ends) of the system bandwidth, with an extra odd PRB for some system BWs (e.g. , 3 MHz, 5 MHz, and 15 MHz) being located at a center of the system BW. The NBs may be numbered in order of increasing PRB number.

[0038] Figs. 1A-1B illustrate NBs for Bandwidth reduced Low complexity (BL) User

Equipments (UEs) for different LTE system bandwidths (BWs), in accordance with some embodiments of the disclosure. A first system BW 110, which may be 3 MHz, may comprise a plurality of PRBs 1 12 and a plurality of 6-PRB NBs 1 14. A second system BW 120, which may be 5 MHz, may comprise a plurality of PRBs 122 and a plurality of 6-PRB NBs 124.

[0039] A third system BW 130, which may be 10 MHz, may comprise a plurality of

PRBs 132 and a plurality of 6-PRB NBs 134. A fourth system BW 140, which may be 15 MHz, may comprise a plurality of PRBs 142 and a plurality of 6-PRB NBs 144. A fifth system BW 150, which may be 20 MHz, may comprise a plurality of PRBs 152 and a plurality of 6-PRB NBs 154.

[0040] Regarding extended NBs for FeMTC UEs with UE BW larger than 6

PRBs, in a first variety of designs, a maximum UE BW may be 5 MHz, which may correspond with 25 PRBs, and in a second variety of designs, a maximum UE BW may be 20 MHz, which may correspond with 100 PRBs.

[0041] For the first variety of designs having a maximum UE BW of 5 MHz, an ENB may be defined as an aggregation of more than 6 PRBs that are contiguous-in-frequency, wherein the number of PRBs aggregated may depend upon an LTE system BW. Note that this definition of an ENB may apply merely to LTE systems having a BW greater than 1.4 MHz. For LTE systems having a BW equal to 1.4 MHz, the ENB definition may degenerate to the definition of an NB (e.g., 6 PRBs that are contiguous-in-frequency).

[0042] For LTE system BWs of 3 MHz and 5 MHz, in various embodiments, for both

DL and UL, an ENB may be defined to span all PRBs in the LTE system BW, and a single ENB may accordingly be defined. For some embodiments, for system BWs of 3 MHz, this may imply a single ENB spanning 15 PRBs, which may include two 6-PRB NBs, as well as 3 LTE PRBs that are not part of any 6-PRB NB. Alternatively, PRBs at the edge of the system BW may not be included in the ENB, and thus the single ENB may span 13 PRBs. In some embodiments, for system BWs of 5 MHz, a single ENB may span 25 PRBs, including four 6-PRB NBs and one LTE PRB at a center of the system BW.

[0043] For some embodiments, an ENB definition and mapping may be different between DL and UL. The DL ENB definition may be similar to the same as described above for LTE system BWs of 3 MHz and/or 5 MHz. However, while the ENB definition may be the same as for the DL for 3 MHz system BW, the ENB definition may be different for 5 MHz system BWs. For 5MHz system BWs, two ENBs may be defined, each of which may span 12 PRBs or 2 6-PRB NBs. One ENB may correspond to NBs #0 and #1 and another ENB may correspond to NBs #2 and #3.

[0044] In some embodiments, for 5 MHz system BWs, two ENBs may be defined.

One ENB may correspond to two 6-PRB NBs, and another ENB may correspond to two 6-PRB NBs and a central PRB (which might not belong to any 6-PRB NB).

[0045] For some embodiments, for LTE system BWs of 5 MHz, two ENBs may be defined for DL as well, in a manner similar to a UL definition. Each ENB may span 12 contiguous-in-frequency PRBs, or two 6-PRB NBs. One ENB may correspond to NBs #0 and #1, and another ENB may correspond to NBs #2 and #3.

[0046] In various embodiments, for LTE deployments with even system BWs, DL

ENBs and UL ENBs may be aligned, but for odd system BWs (e.g., 3 MHz, 5 MHz, and/or 15 MHz), UL ENBs may be formed merely from one or more contiguous-in-frequency 6-PRB NBs. In various embodiments, it may be desirable to align DL ENBs and UL ENBs, which may advantageously avoid additional frequency retiming during UL-to-DL and/or DL- to-UL switching in Time-Division Duplex (TDD) systems.

[0047] For LTE system BWs of 10 MHz and 20 MHz, in various embodiments, two

ENBs or four ENBs may be defined, any of which may comprise 4 contiguous-in-frequency 6-PRB NBs, and may be the same for DL and UL.

[0048] For LTE system BWs of 15 MHz, in some embodiments, ENBs may be defined such that there may be 2 ENBs in common for both DL and UL. For example, there may be an ENB #0 spanning an NB #0, an NB #1, an NB #2, and an NB #3, and there may be an ENB #1 spanning an NB #8, an NB #9, an NB #10, and an NB #11.

[0049] Fig. 2 illustrates ENB definitions for a 15 MHz system BW, in accordance with some embodiments of the disclosure. A system BW 240, which may be 15 MHz, may comprise a plurality of PRBs 242, a plurality of 6-PRB NBs 244, and a plurality of ENBs 246. For some embodiments, for 15 MHz LTE system BWs, 3 ENBs may be defined for both DL and UL. An ENB #0 may span an NB #0, an NB #1, an NB #2, and an NB #3, an ENB #1 may span an NB #4, an NB #5, an NB #6, an NB #7, and a PRB at a center of the system BW (which might not belong to any 6-PRB NB), and an ENB #2 spanning an NB #8, an NB #9, an NB #10, and an NB #11. This is shown in Figure 2 below.

[0050] In some embodiments, ENBs for DL and UL might be not aligned. For example, the UL may have 2 ENBs, each of which may consist of 4 contiguous-in-frequency 6 PRB NBs (e.g., an ENB #0 spanning an NB #0, an NB #1, an NB #2, and an NB #3, and an ENB #1 spanning an NB #8, an NB #9, an NB #10, and an NB #11), while the DL may have 3 ENBs (e.g., an ENB #0 spanning an NB #0, an NB #1, an NB #2, and an NB #3, an ENB #1 spanning an NB #4, an NB #5, an NB #6, an NB #7, and a PRB at a center of the system BW (which might not belong to any 6-PRB NB), and an ENB #2 spanning an NB #8, an NB #9, an NB #10, and an NB #11), or vice versa.

[0051] Moreover, in various embodiments, one or more edge PRBs, which might not be a part of any NBs, may also be included in an ENB. For example, when an ENB comprises NBs next to an edge PRB that does not belong to any NB, the edge PRB may also be included in that ENB.

[0052] Various potential ENB definitions are summarized in Table 1 below. In various embodiments. In some embodiments, the DL ENB definitions and the UL ENB definitions may be the same). For the last column, the numbers in parentheses may indicate a number of PRBs that may make up an ENB ((NRB^{xl"e b}) (XL = DL or UL)) in each case. Table 1 : Numbers of PRBs, NBs and ENBs corresponding to various LTE system BWs, where maximum UE BW is 5 MHz

[0053] For the second variety of designs having a maximum UE BW of 20 MHz, an

ENB may be defined as an aggregation of more than 6 PRBs that may be contiguous-in- frequency, wherein the number of PRBs aggregated may depend upon an LTE system BW. The number of ENBs in different system BWs are summarized in Table 2. There may be edge PRBs that are not a part of any NB for system BWs of 3 MHz, 10 MHz, 15 MHz and 20 MHz. In some embodiments, these edge PRBs might not be counted in any ENB. For some embodiments, these edge PRBs may be counted in various ENBs.

Table 2: Numbers of PRBs, NBs, and ENBs corresponding to various LTE system BWs, where maximum UE BW is 20 MHz

[0054] Fig. 3 illustrates ENB definitions for a 15 MHz system BW and a 20 MHz system BW, in accordance with some embodiments of the disclosure. A first system BW 340, which may be 15 MHz, may comprise a plurality of PRBs 342, a plurality of NBs 344, and one or more ENBs 346. A second system BW 350, which may be 20 MHz, may comprise a plurality of PRBs 352, a plurality of NBs 354, and one or more ENBs 356.

[0055] In various embodiments in which maximum UE BW is 20 MHz, edge PRBs might not be counted in any ENB. Alternatively, one or more edge RBs which do not belong to any NB may be included in an ENB.

[0056] Regarding extended NBs for FeMTC UEs with UE BW larger than 6

PRBs, for the first variety of design and the second variety of design, where ENBs are defined to comprise not only 6-PRB NBs but also central PRBs that are not part of any 6-PRB NB, in some embodiments, an additional PRB may be available for both DL and UL resource allocation. For some embodiments, the additional PRB might not be available for DL scheduling, but may be available for UL scheduling, thereby allowing alignment with PRBs that are available for PDSCH scheduling for 3 GPP Release 13 BL/CE UEs, while at the same time allowing single-carrier PUSCH transmissions (based on Single-Carrier Frequency-Division Multiple Access (SC-FDMA)) spanning up to the entire set of available resources within ENBs containing central PRBs that are not part of 6-PRB NBs.

[0057] For some embodiments, there may be edge PRBs that do not belong to any NB in certain system BWs. In some embodiments, these edge PRBs might not be included in an ENB. Alternatively, these edge PRBs may be included in an ENB, and may be available for resource allocation. They may be available for both DL and UL transmission, or only for DL transmission, or only for UL transmission.

[0058] In some embodiments, ENBs may be indexed in increasing order of PRBs similar to an indexing of NBs.

[0059] In various embodiments, such definitions of ENBs may apply only to LTE systems having BWs greater than 1.4 MHz. For LTE systems having BW of 1.4 MHz, an ENB definition may degenerate to a definition of an NB (e.g., 6 PRBs that are contiguous -in- frequency).

[0060] Various embodiments discussed herein may pertain to resource allocation options for PDSCH and/or PUSCH based on ENB for CE mode A. Various resource allocation mechanisms for PDSCH and PUSCH may incorporate ENBs.

[0061] In some embodiments, DCI formats 6-1 A (with DL assignment) and 6-0 A

(with UL grant) may indicate an ENB index using ceil( log2(NENB^KL ) ) most significant bits (MSBs) of the existing resource block assignment field, with XL = DL and UL for DCI 6-1 A and 6-0 A, respectively, and where NENB^xl may be a total number of ENBs in a system BW for XL = DL or UL.

[0062] Further, allocated frequency domain resources within an ENB may be indicated with a granularity of NBs using a next ceil( log2(NNB^XL~ENB ) ) MSBs of the resource block assignment field, where NNB^^"™³ may indicate a number of NBs within an ENB, and may be given by

may denote a number of RBs within an ENB. The number of NBs indicated by NNB^31'™ may be contiguous-in- frequency, and may start from a first (lowest) NB, or may be contiguous -in-frequency and may end at a last (highest) NB within the ENB. In other words, a reference NB may be either a first (lowest) NB (as the start of a set of assigned NBs) or a last (highest) NB (as the end of a set of assigned NBs).

[0063] Alternatively, a reference NB may be any NB within an ENB, and the assigned NBs may be either all prior NBs or all later NBs with respect to the reference NB within the ENB. The indication of reference NB may use

bits, where NN^^L~Ref~NB may indicate a number of possible reference NBs. In some exemplary embodiments, ΝΝΒ^^^' = NNI ^L-^ENB. The selection of "prior" NBs or "later" NBs with respect to the reference NB may be predetermined or predefined (e.g., fixed), or may be dynamically configured (e.g., via an additional 1 bit in DCI), or may be semi-statically configured (e.g., via higher-layer signaling such as RRC signaling). For embodiments in which a reference NB is either a first NB or a last NB within the ENB, an indication of "prior" NB and "later" NBs may be implicitly indicated when the reference NB is indicated, "prior" for the reference NB being the last NB, and "later" for the reference NB being the first NB.

[0064] Moreover, in some embodiments, as another alternative to assigning NBs within an ENB, a starting NB index and a number of NBs to be assigned may be indicated. The starting NBs may be a first (lowest) NB or a last (highest) NB within an ENB. Table 3 below provides examples of possible starting NB indices and lengths of NBs. Table 3. Illustration of ossible NB assi nments within an ENB

[0065] A number of bits used for an indication of NBs within an ENB may be ceil(log₂((NA'i? ^I'^"£A'^iJ+l)/2* NNB ¹^⁸))) bits. For example, when an ΕΝΒ consists of 4 NBs, the number of bits for the NB allocation within the ENB in this embodiment may be 4.

[0066] In various embodiments, a number of NBs which may be a multiple of 7 may be excluded for PUSCH transmission, since a DFT size may be limited to multiples of 2, 3, and/or 5. Thus, a number of bits used may be further reduced for UL.

Alternatively, the combinations including a number of NBs which may be a multiple of 7 may be reused to indicate a distributed NB allocation, which may advantageously improve a scheduling flexibility.

[0067] For example, when a maximum UE BW is 20 MHz, and an ENB is defined to comprise 16 NBs, a resource allocation excluding a number of NBs that may be multiples of 7 may be as listed follows:

[0068] A starting NB may be 0, and a number of NBs may be any value within the set { 1 , 2, 6, 8, 9, 13, 15, 16} .

[0069] A starting NB may be 1 , and a number of NBs may be any value within the set { 1 , 2, 6, 8, 9, 13, 15} .

[0070] A starting NB may be 2, and a number of NBs may be any value within the set { 1 , 2, 6, 8, 9, 13 } .

[0071] A starting NB may be x, where x may be within the set {3, 4, ... , 8} , and a number of NBs may be any value within the set { 1 , 2, ... , 6, 8, ... , 16-x} .

[0072] A starting NB may be 9, and a number of NBs may be any value within the set { 1, 2, 6} .

[0073] A starting NB may be x, where x may be within the set { 10, ... , 15 }, and a number of NBs may be any value within the set { 1 , 2, 16-x} .

[0074] The number of possible combinations above may be 123, and thus 7 bits may be enough for the indicator. There may be 5 more resource allocations available for a 7-bit resource allocation. These 5 may be reserved, or may be used to indicate a distributed NB allocation. In some embodiments, if all numbers of NBs are supported, a number of possible combinations for ENB comprising 16 NBs may be 136, and thus a number of needed bits for an NB indicator may be ceil(log2((NA¾ ^i_£A¾+l)/2* NNE?^1' ^ENB))) =8 bits.

[0075] For some embodiments, for at least for the case of DL scheduling (e.g., for

PDSCH), allocated NBs may be indicated using a bitmap of length equal to NNB^XL~ENB. For example, for an ENB comprising four NBs, a bitmap of 1001 may indicate that the first and last NBs in the ENB are allocated.

[0076] In some embodiments, to reduce a number of bits for an NB allocation, a predetermined or predefined set of NBs may be used. For example, when an ENBcomprises 4 NBs in a system (e.g., for systems with BW of 10 MHz, 15 MHz, or 20 MHz), reusing the bits indicating the NB index to indicate the ENB index, there may be 2 bits left for NB allocation within the ENB. In one embodiment, these 2 bits may be used to indicate one of the following NB allocations: {0, 1 } , {2, 3 }, {0, 1, 2} , or {0, 1 , 2, 3} .

[0077] For some embodiments, PRBs allocated within a 6-PRB NB may be indicated using the last 5 bits of a resource block assignment field in DCI 6-OA and/or DCI 6-1 A, and the same allocation of PRBs in each of the 6-PRB NBs may be assumed. While this approach may work for DL, such an approach might not be desirable for UL resource allocation if all PRBs in an NB are not allocated to the UE due to violation of the single- carrier property for SC-FDMA based transmissions.

[0078] In some embodiments, an alternative to address this may be to interpret the last 5 bits of a resource block assignment field to indicate the PRBs used for the first NB allocated or the last NB allocated within an ENB, and interpret that all PRBs in the later NBs (if the RB assignment indicates the RBs within the first NB) or preceding NBs (if the RB assignment indicates the RBs within the last NB) within the ENB are also allocated. This alternative may be applied merely to UL (e.g., for PUSCH), while the previous alternative (e.g., of the same PRB assignment within each NB of an ENB) may be applied for DL (PDSCH), or the alternative interpretation may be applied to both UL (PUSCH) and DL (PDSCH) resource allocations.

[0079] For some embodiments, additional fields may not be needed in DCI formats 6-

0A and 6-1 A, as a UE may re-interpret a resource block assignment as described above when configured to operate in an "aggregated BW mode" or a "higher BW mode" via higher-layer signaling. Alternatively, an FeMTC UE with larger than 1.4 MHz BW support may be specified to always interpret a resource allocation field in DCI formats 6-OA and 6-1A as described above, instead of the interpretation according to a 3 GPP Release- 13 definition of the respective DCI formats.

[0080] Following the above approach, it might not be possible to explicitly indicate an additional central PRB for the cases of odd system BWs if the ENB definition includes the central PRB (which does not belong to any 6-PRB NB). However, it may still be possible to allocate the central PRB implicitly by defining the behavior that if the NBs flanking the central PRB are allocated to the UE, the central PRB may also be assumed to be allocated to the UE. Such an approach may be appropriate especially for PUSCH scheduling due to the single-carrier constraint.

[0081] Alternatively, an allocation (or not) of the central PRB may be indicated using a new 1-bit field, or by extending an existing resource block assignment field by 1 bit, at the expense of an increase in DCI size. Such an approach may merely be taken for scheduling of PDSCH (i.e., DCI 6-1A), and might not be taken for UL grant for PUSCH transmissions.

[0082] Edge PRBs which do not belong to any NBs in certain system BWs may also be included in ENBs, and may be allocated to UEs. An indication of edge-PRB allocation may be either implicit or explicit (as with a central PRB allocation). For an implicit indication, the following behavior can be defined: If a first NB or last NB which is next to an edge PRBs which does not belong any NBs are allocated, the edge PRBs next to the allocated NBs may also allocated. For an explicit indication, a 1-bit field may be added to DCI for the indication. Note that if the edge PRBs are available only for DL or UL transmission, this resource allocation for edge PRBs may apply to the corresponding DL or UL transmissions.

[0083] For some embodiments, in addition to a re-interpretation of a resource allocation field in DCI formats 6-0 A and 6-1 A, one or more new fields may be introduced to provide additional flexibility in frequency domain resource allocation within each of the NBs comprising an ENB.

[0084] In some embodiments, the frequency domain resource allocation may be done by indicating an ENB index within a system BW using ceil( log2(NENB^XL ) ) bits, and resources within the ENB may be indicated using DL resource allocation type 2 with a granularity of NN^^L'ENB RBS, where ΝΝΒ^^'ΕΝΒ is the number of NBs in an ENB for the corresponding system BW. Thus, 5 bits (as in a DCI format 6-1 A) may be used to indicate a resource allocation within an ENB. For some embodiments based on this approach of using DL resource allocation type 2, a granularity of resource allocation may be defined as k RBs, where k may be predetermined or predefined (e.g., specified); for example, k may be predetermined to be 2. [0085] Different combinations of the options discussed herein to indicate NBs inside an ENB and resource allocation within an NB may be supported as well.

[0086] Various embodiments discussed herein may pertain to resource allocation options for PDSCH and PUSCH based on ENB for CE Mode B.

[0087] Resource allocation mechanisms for PDSCH and PUSCH may use ENBs for CE Mode B UEs, based on DCI formats 6-1B and 6-OB. The number of bits in a resource allocation field for DCI formats 6- IB and 6-OB may be ceil( log2(NNB^DL)) + lbit and ceil( log2(NNB^UL)) + 3 bits, respectively, where NNB^xl may denotes a number of NBs in XL, with XL = DL for format 6- IB and XL=UL for format 6-OB.

[0088] While in the following both DL and UL scheduling options are presented, in some embodiments, an applicability of larger than 6-PRB NBs with UE channel BW greater than 1.4 MHz may merely be supported for unicast PDSCH, and might not be supported for not unicast PUSCH transmissions when the UE is in CE Mode B.

[0089] In some embodiments, for NB allocation, various methods may be considered. For some embodiments, DCI formats 6- IB (with DL assignment) and 6-OB (with UL grant) may indicate an ENB index using ceil( log2(NENB^XL ) ) most significant bits (MSBs) of the existing resource block assignment field, with XL = DL and UL for DCI 6-1B and 6-OB respectively, where NENB^xl may be a total number of ENBs in a system BW for XL = DL or UL. With this method, a total number of remaining available bits besides ENB index may be ceil( log2(NNB^KL )) - ceil( log2(NENB^XL)) + y bits, where y=l for DL and 3 for UL.

[0090] Moreover, an allocation of NBs within an ENB may be based on various methods. Note that with certain methods discussed herein, or with certain maximum UE channel BW (e.g., 20 MHz), remaining available bits in a resource allocation field might not be sufficient, and additional bits/fields may be needed.

[0091] In some embodiments, a frequency domain resource within an ENB may be indicated with the granularity of NBs using next ceil( log2(NNB^XL~ENB ) ) MSBs of the resource block assignment field. NNB^xl"enb may indicate a number of NBs within an ENB, and may be given by NN^^l'enb = floor (NR^^L~mB/6), where NRB*^L~ENB may denote a number of RBs within an ENB. The number of NBs indicated by NNB^xl"enb may be contiguous -in-frequency, and may start from the first (lowest) NB, or may be contiguous -in-frequency and may end at the last (highest) NB within the ENB. In other words, a reference NB may be either a first (lowest) NB (as the start of the set of assigned NBs) or a last (highest) NB (as the end of the set of assigned NBs). For maximum UE channel BW of 5 MHz, the remaining available bits may be at least 2 + y bits, which is sufficient for ceil( log2(NNB^XL~ENB )) .

[0092] For some embodiments, a reference NB may be any NB within an ENB, and the assigned NBs may be either all prior or all later NBs with respect to the reference NB within the ENB. An indication of reference NB may use ceil(log2(NNB^XL~ Ref-NB kj_{ts^ w}h_ere N_NBxL-Ref-NB _may indicate a number of possible reference NBs and, in one example, NNB^XL'REF'NB = ΝΝΒ^-^'^. A selection of "prior" or "later" NBs with respect to a reference NB, may be predetermined or predefined (e.g., fixed), or may be dynamically configured (e.g., an additional 1 bit in DCI), or may be semi-statically configured (e.g., via higher-layer signaling, such as RRC signaling). For embodiments in which a reference NB is either a first NB or a last NB, an indication of "prior" and "later" NBs may be implicitly indicated when the reference NB is indicated, with "prior" for reference NB being the last NB, and "later" for reference NB being the first NB.

[0093] In some embodiments, for maximum UE channel BW of 5 MHz, the remaining available bits may be at least 2 bits, which may be enough for ceil( log2(N_NB^XL-^REF-^NB)) if a reference NB can be any NB, and the "prior" NB or "later" NB may be predetermined or predefined, or semi-statically configured via higher-layer signaling. If a selection of "prior" or "later" is indicated by DCI, then the possible set of reference NBs may be limited to 2.

[0094] For some embodiments, to assign NBs within an ENB, merely the starting

NB index and a number of NBs to be assigned may be indicated. The starting NBs may be a first (lowest) NB or a last (highest) NB within an ENB. This allocation method may be able to assign continuous NB allocation.

[0095] Table 4 below may provide an example of possible starting NB index and length of NBs.

Table 4. Illustration of possible NB assignments within an ENB

[0096] A number of bits for an indication of NBs within an ENB may be ceil(log₂((NA¾ ⁱ-^ia¾+l)/2* NmP-¹*"*))) bits. For example, when an ΕΝΒ comprises 4 NBs, a number of bits for the NB allocation within the ENB may be 4. Note that a number of NBs which is multiple of 7 may be excluded for PUSCH transmission, since the DFT size is limited to multiples of 2, 3, and 5. Thus, a number of needed bits may be further reduced for UL. Alternatively, the combinations including a number of NBs which is a multiple of 7 may be reused to indicate distributed NB allocation, which may advantageously improve a scheduling flexibility.

[0097] For example, when a maximum UE BW is 20 MHz, and an ENB is defined to comprise 16 NBs, a resource allocation excluding a number of NBs that may be multiples of 7 may be as listed follows :

[0098] A starting NB may be 0, and a number of NBs may be any value within the set { 1 , 2, 6, 8, 9, 13, 15, 16} .

[0099] A starting NB may be 1 , and a number of NBs may be any value within the set { 1 , 2, 6, 8, 9, 13, 15 } .

[00100] A starting NB may be 2, and a number of NBs may be any value within the set { 1 , 2, 6, 8, 9, 13 } .

[00101] A starting NB may be x, where x may be within the set {3, 4, ... , 8 } , and a number of NBs may be any value within the set { 1 , 2, ... , 6, 8, ... , 16-x} .

[00102] A starting NB may be 9, and a number of NBs may be any value within the set { 1 , 2, 6} .

[00103] A starting NB may be x, where x may be within the set { 10, ... , 15 } , and a number of NBs may be any value within the set { 1 , 2, 16-x} .

[00104] The number of possible combinations above may be 123, and thus 7 bits may be enough for the indicator. There may be 5 more resource allocations available for a 7-bit resource allocation. These 5 may be reserved, or may be used to indicate a distributed NB allocation. In some embodiments, if all numbers of NBs are supported, a number of possible combinations for ENB comprising 16 NBs may be 136, and thus a number of needed bits for an NB indicator may be ceil(log2((NA¾ ^i_£A¾+l)/2* NNE?^1' ^ENB))) =8 bits.

[00105] In some embodiments, for scenarios in which maximum UE BW is 5 MHz and the NNB^xl~enb=4, a number of needed bits may be 4 bits. The remaining available bits might not be enough. Some embodiments may add additional bits/fields for the ΝΒ allocation indication. [00106] For some embodiments, to minimize a number of bits for an NB allocation, some predetermined or predefined set of NBs may be used. For example, when the ENBs comprise 4 NBs in the system (e.g. , for systems with BW of 10 MHz, 15 MHz, or 20 MHz), reusing the bits indicating the NB index to indicate the ENB index, there may be 2 bits left for an NB allocation within the ENB. In one

embodiment, these 2 bits may be used to indicate one of the following NB allocations : {0, 1 } , {2, 3 } , {0, 1 , 2} , or {0, 1 , 2, 3 } .

[00107] For some embodiments, for at least for the case of DL scheduling (e.g., for

[00108] In some embodiments, to indicate a PRB allocation within a NB, various methods may be considered. For some embodiments, PRBs allocated within a 6-PRB NB may follow DCI 6-OB and DCI 6- I B design, where 3 bits may be used for RB assignment in DCI 6-OB and 1 bit to indicate RBs {0, 1 , ... , 5 } or {0, 1 , 2, 3 } may be used in DCI 6- 1 B. The same allocation of PRBs in each of the 6-PRB NBs may be assumed. While this approach may work for DL, such an approach may not be suitable for UL resource allocation if all PRBs in an NB are not allocated to the UE due to violation of the single-carrier property for SC-FDMA based transmissions.

[00109] For some embodiments, an alternative to address this may be to interpret a resource block assignment field to indicate the PRBs allocated for the first NB or the last NB allocated within an ENB, and to interpret that all PRBs in the later NBs (if the RB assignment indicates the RBs within the first NB) or preceding NBs (if the RB assignment indicates the RBs within the last NB) within the ENB may also be allocated. This alternative interpretation may be applied to UL (PUSCH), while the previous interpretation (e.g., of the same PRB assignment within each NB of an ENB) for DL (PDSCH) or the alternative interpretation may be applied to both UL (PUSCH) and DL (PDSCH) resource allocations.

[00110] In some embodiments, in such cases, additional fields may not be needed in DCI formats 6-OB and 6- I B, as a UE may re-interpret a resource block assignment as described above when configured to operate in an "aggregated BW mode" or a "higher BW mode" via higher-layer signaling. Alternatively, an FeMTC UE with larger than 1.4 MHz BW support may be specified to always interpret a resource allocation field in DCI formats 6-OB and 6-1B as described above, instead of the interpretation according to a 3GPP Release-13 definition of the respective DCI formats.

[00111] Following the above approach, it might not be possible to explicitly indicate an additional central PRB for the cases of odd system BWs if the ENB definition includes the central PRB (which does not belong to any 6-PRB NB). However, it may still be possible to allocate the central PRB implicitly by defining the behavior that if the NBs flanking the central PRB are allocated to the UE, the central PRB may also be assumed to be allocated to the UE. Such an approach may be appropriate especially for PUSCH scheduling due to the single-carrier constraint.

[00112] Alternatively, an allocation (or not) of the central PRB may be indicated using a new 1-bit field, or by extending an existing resource block assignment field by 1 bit, at the expense of an increase in DCI size. Such an approach may merely be taken for scheduling of PDSCH (i.e., DCI 6-1B), and might not be taken for UL grant for PUSCH transmissions.

[00113] Edge PRBs which do not belong to any NBs in certain system BWs may also be included in ENBs, and may be allocated to UEs. An indication of edge-PRB allocation may be either implicit or explicit (as with a central PRB allocation). For an implicit indication, the following behavior can be defined: If a first NB or last NB which is next to an edge PRBs which does not belong any NBs are allocated, the edge PRBs next to the allocated NBs may also allocated. For an explicit indication, a 1-bit field may be added to DCI for the indication. Note that if the edge PRBs are available only for DL or UL transmission, this resource allocation for edge PRBs may apply to the corresponding DL or UL transmissions.

[00114] For some embodiments, in addition to a re-interpretation of a resource allocation field in DCI formats 6-OB and 6-1B, one or more new fields may be introduced to provide additional flexibility in frequency domain resource allocation within each of the NBs comprising an ENB.

[00115] In some embodiments, the frequency domain resource allocation may be done by indicating an ENB index within a system BW using ceil( log2(NENB^XL ) ) bits, and resources within the ENB may be indicated using DL resource allocation type 2 with a granularity of NN^^L'ENB RBS, where ΝΝΒ^^'ΕΝΒ is the number of NBs in an ENB for the corresponding system BW. Thus, 3 bits (as in a DCI format 6-OB), in addition to remaining bits in NB index indication, i.e., ceil( log2(NNB^XL )) - ceil( log2(NENB^XL ) ) bits, may be used to indicate a resource allocation within an ENB for PUSCH. For PDSCH, a number of bits in a resource allocation field may be 2 bits less than PUSCH. The following methods may be adopted to reduce a number of needed bits. In another embodiment based on this approach of using DL resource allocation type 2, a granularity of resource allocation may be defined as k RBs, where k may be predetermined or pre-defined (e.g., by specification). For example, k may be 2. Alternatively, additional bits may be added.

[00116] Different combinations of the options discussed herein to indicate NBs inside an ENB and resource allocation within an NB may be supported as well.

[00117] Various embodiments discussed herein may pertain to mechanisms and methods to support FH for PDSCH and PUSCH for FeMTC UEs with UE BW larger than 6

PRBs.

[00118] In some cases for FeMTC UEs with larger than 1.4 MHz BW support, such as when PDSCH/PUSCH allocations may span more than a single 6 PRB NB, there may be problematic behavior when FH is configured due to a wrap-around at the band edges while determining the NBs being hopped to, based on an initial allocation and a frequency offset configured.

[00119] For a UE BW of 5 MHz for FeMTC UEs with larger BW support, and for system BWs of 10 MHz, 15 MHz, and 20 MHz, allocated resources for PDSCH and/or PUSCH may be fragmented across two edges of a system BW, and therefore only one part of the entire allocation may be accessible by the UE. This may be because FH may be defined with an NB granularity.

[00120] Fig. 4 illustrates fragmentation of Physical Downlink Shared Channel

(PDSCH) / Physical Uplink Shared Channel (PUSCH) allocation with Frequency Hopping (FH) with fragmentation at a band edge, in accordance with some embodiments of the disclosure. A first system BW 410, which may be 10 MHz, may comprise a plurality of PRBs 412, a plurality of 6-PRB NBs 414, and one or more ENBs 416. A second system BW 420, which may be 10 MHz, may comprise a plurality of PRBs 422 and a plurality of 6-PRB NBs 424.

[00121] It may be possible that merely a subset of NBs (rather than all NBs) within an

ENB may be allocated for transmission. The ENB #1 (comprising NB #4 through NB #7) may be assigned for PDSCH and/or PUSCH transmission. With an FH offset of 2 NBs, fragmentation may occur at the band edge.

[00122] In some embodiments, a first solution to the above problem may be to rely on an eNodeB scheduler implementation that would ensure that the resulting NBs for a particular configured FH offset for FeMTC UEs with larger BW support would not be impacted by the wrap around. For instance, an FH field in DCI may be used to disable a FH for allocations in which the wrap around may cause the above-described fragmentation. A drawback of the first solution is a potential impact to a scheduling flexibility, not only for FeMTC UEs but also for other UEs (e.g., 3 GPP Release-13 BL/CE UEs) that may collide with FeMTC allocations that do not hop unless these UEs are scheduled carefully with additional constraints (if FH is enabled for these UEs).

[00123] To address this shortcoming, for some embodiments, a second solution to the above problem may be to use an ENB-based resource allocation and FH for FeMTC UEs with larger BW support, at least when these UEs are scheduled with more than 6 PRBs of frequency domain resources for PDSCH and/or PUSCH.

[00124] Accordingly, in some embodiments, an initial resource block assignment for

PDSCH and/or PUSCH may be defined in terms of ENBs (as described in the previous subsections), and an FH offset (which may be indicated in terms of NBs) may be defined as an integer multiple of a number of NBs in an ENB (as defined for the particular system BW), thereby avoiding any issues with wrapping around the system BW edges. Thus, a UE may not expect to be configured with an FH offset value that is not an integer multiple of the number of NBs in an ENB for the corresponding system BW.

[00125] Note that the same FH offset may be applicable to 3 GPP Release- 13 BL/CE and other BL/CE UEs that support no more than 1.4 MHz UE BW. Additionally, collisions between FeMTC UEs with larger than 6 PRB allocations and other UEs may advantageously be avoided.

[00126] In some embodiments, a third solution to the above problem may be to define an initial resource block assignment for PDSCH and/or PUSCH in terms of ENBs as described in the previous sub-sections, and employ an FH offset that is not constrained to be multiples of ENB size. In such embodiments, the application of FH may be defined such that the ENB to hop to from the initial allocation may be determined based on a first NB in the ENB, and the FH rule may be defined such that the UE may choose an ENB #j from ENB #i (e.g., an initial assignment) such that the NB (which may be an NB NB_i + FH_offset) may fall within ENB #j, where NB_i may be a first NB (or last NB, or an NB at any particular specified position) of ENB #i. Thus, the FH offset FH offset may be configured with an NB granularity (instead of an ENB granularity), and a UE may decide to hop (or to not hop) to a different ENB depending on whether the application of the FH offset to the reference NB within the ENB results in translation to a different ENB or not.

[00127] Fig. 5 illustrates PDSCH / PUSCH allocation with FH based on a reference

NB, in accordance with some embodiments of the disclosure. A first system BW 510, which may be 10 MHz, may comprise a plurality of PRBs 512, a plurality of 6-PRB NBs 514, and one or more ENBs 516. A second system BW 520, which may be 10 MHz, may comprise a plurality of PRBs 522 and a plurality of 6-PRB NBs 524.

[00128] Fig. 5 depicts a scenario of FH with NB i being the first NB of an ENB #i. In this scenario, an FeMTC UE may not hop at all for certain (small) values of FH offset. An eNodeB scheduler might ensure that the frequency domain resources for ENB #i are not allocated to other UEs in the subframes when the FH is supposed to be applied. Otherwise, there may be collisions between FeMTC UEs with larger BW support that effectively do not hop to a different set of frequency resources and other UEs that actually change their frequency location at the FH boundaries.

[00129] Furthermore, in some embodiments that may pertain to the second solution and the third solution, an FH unit may be in terms of k NBs rather than ENBs. A granularity of frequency hopping resources may be k contiguous NBs, while an offset of frequency hopping may be either a k-NB segment (which may pertain to the second solution) or any number of NBs (which may pertain to the third solution). Instead of defining an ENB size as a maximum number of contiguous NBs that a UE with larger than a 1.4 MHz UE channel BW may support, a k-NB segment may be interpreted as ENBs that are defined to comprise k contiguous NBs, where k may be no larger than a maximum number of contiguous NBs that a UE with a larger than 1.4 MHz UE channel BW may support.

[00130] The parameter k may be predetermined or predefined, semi-statically configured (e.g., by higher-layer signaling), or may be dynamically indicated by adding additional bits in DCI. For example, k may be any value within the set { 1, 2, 4, 8}, in which case 2 bits may be disposed to being added to DCI for the dynamic indication. Alternatively, k may be implicitly indicated (e.g., by setting k equal to a number of NBs allocated for transmission). Such a mechanism may be applied in scenarios in which an ENB-based FH method would lead to no FH at all. Fr example, such a mechanism may apply in scenarios where a max UE channel BW may equal 20 MHz, or where a system BW may be small (e.g., 3 MHz or 5 MHz).

[00131] Moreover, combinations of various mechanisms may be specified such that a specific mechanism may apply depending on a system BW, a max UE channel BW, and so forth.

[00132] Specifically, for the second solution, the k-NBs based FH may be used for

FeMTC UEs with larger BW support, at least when these UEs are scheduled with more than 6 PRBs of frequency domain resources for PDSCH and/or PUSCH. In this solution, the granularity of hopped resources may be k contiguous NBs, and the FH offset may also be k contiguous NBs. When k is no less than the number of NBs that are allocated for the transmission, any issues with wrapping around the system BW edges may be avoided.

[00133] For the third solution, total frequency resources may be separated into floor(NNB/k) parts, where NNB may denote a total number of NBs in the system. In this solution, the granularity of hopped resource may be k contiguous NBs, and the FH offset may be any number of NBs. The application of FH may be defined such that the k NBs to hop to from an initial allocation are determined based on the first NB allocated for transmission, and the FH rule may be defined such that the UE chooses a k-NB # j (e.g., a j-th partition or segment with k contiguous NBs) from k-NB #i (e.g.., an initial assignment). The NB (NBJ + FH offset) may fall within the k-NB # j, where NBJ may be a first NB (or a last NB, or an NB at any particular specified position) of k-NB #i.

[00134] Thus, an FH offset (FH offset) may be configured with a granularity of NBs, and the UE may decide to hop (or not) to a different k-NB depending on whether the application of the FH offset to the reference NB within the k-NB results in translation to a different k-NB or not. The allocated NBs within the k-NB may be the same before and after FH. The eNodeB scheduler may be disposed to ensuring that frequency domain resources (at least the NBs allocated for the transmission within the k-NB #i) are not allocated to other UEs in the subframes when the FH is supposed to be applied. Otherwise, there may be collisions between FeMTC UEs with larger BW support that effectively do not hop to a different set of frequency resources, and other UEs that may actually change their frequency location at the FH boundaries. Note that k may be disposed to being equal to or greater than the number of NBs allocated for transmissions.

[00135] Fig. 6 illustrates an eNodeB and a UE, in accordance with some embodiments of the disclosure. Fig. 6 includes block diagrams of an eNodeB 610 and a UE 630 which are operable to co-exist with each other and other elements of an LTE network. High-level, simplified architectures of eNodeB 610 and UE 630 are described so as not to obscure the embodiments. It should be noted that in some embodiments, eNodeB 610 may be a stationary non-mobile device.

[00136] eNodeB 610 is coupled to one or more antennas 605, and UE 630 is similarly coupled to one or more antennas 625. However, in some embodiments, eNodeB 610 may incorporate or comprise antennas 605, and UE 630 in various embodiments may incorporate or comprise antennas 625. [00137] In some embodiments, antennas 605 and/or antennas 625 may comprise one or more directional or omni-directional antennas, including monopole antennas, dipole antennas, loop antennas, patch antennas, microstrip antennas, coplanar wave antennas, or other types of antennas suitable for transmission of RF signals. In some MIMO (multiple-input and multiple output) embodiments, antennas 605 are separated to take advantage of spatial diversity.

[00138] eNodeB 610 and UE 630 are operable to communicate with each other on a network, such as a wireless network. eNodeB 610 and UE 630 may be in communication with each other over a wireless communication channel 650, which has both a downlink path from eNodeB 610 to UE 630 and an uplink path from UE 630 to eNodeB 610.

[00139] As illustrated in Fig. 6, in some embodiments, eNodeB 610 may include a physical layer circuitry 612, a MAC (media access control) circuitry 614, a processor 616, a memory 618, and a hardware processing circuitry 620. A person skilled in the art will appreciate that other components not shown may be used in addition to the components shown to form a complete eNodeB.

[00140] In some embodiments, physical layer circuitry 612 includes a transceiver 613 for providing signals to and from UE 630. Transceiver 613 provides signals to and from UEs or other devices using one or more antennas 605. In some embodiments, MAC circuitry 614 controls access to the wireless medium. Memory 618 may be, or may include, a storage media/medium such as a magnetic storage media (e.g., magnetic tapes or magnetic disks), an optical storage media (e.g., optical discs), an electronic storage media (e.g., conventional hard disk drives, solid-state disk drives, or flash-memory-based storage media), or any tangible storage media or non-transitory storage media. Hardware processing circuitry 620 may comprise logic devices or circuitry to perform various operations. In some embodiments, processor 616 and memory 618 are arranged to perform the operations of hardware processing circuitry 620, such as operations described herein with reference to logic devices and circuitry within eNodeB 610 and/or hardware processing circuitry 620.

[00141] Accordingly, in some embodiments, eNodeB 610 may be a device comprising an application processor, a memory, one or more antenna ports, and an interface for allowing the application processor to communicate with another device.

[00142] As is also illustrated in Fig. 6, in some embodiments, UE 630 may include a physical layer circuitry 632, a MAC circuitry 634, a processor 636, a memory 638, a hardware processing circuitry 640, a wireless interface 642, and a display 644. A person skilled in the art would appreciate that other components not shown may be used in addition to the components shown to form a complete UE.

[00143] In some embodiments, physical layer circuitry 632 includes a transceiver 633 for providing signals to and from eNodeB 610 (as well as other eNodeBs). Transceiver 633 provides signals to and from eNodeBs or other devices using one or more antennas 625. In some embodiments, MAC circuitry 634 controls access to the wireless medium. Memory 638 may be, or may include, a storage media/medium such as a magnetic storage media (e.g., magnetic tapes or magnetic disks), an optical storage media (e.g., optical discs), an electronic storage media (e.g., conventional hard disk drives, solid-state disk drives, or flash-memory - based storage media), or any tangible storage media or non-transitory storage media.

Wireless interface 642 may be arranged to allow the processor to communicate with another device. Display 644 may provide a visual and/or tactile display for a user to interact with UE 630, such as a touch-screen display. Hardware processing circuitry 640 may comprise logic devices or circuitry to perform various operations. In some embodiments, processor 636 and memory 638 may be arranged to perform the operations of hardware processing circuitry 640, such as operations described herein with reference to logic devices and circuitry within UE 630 and/or hardware processing circuitry 640.

[00144] Accordingly, in some embodiments, UE 630 may be a device comprising an application processor, a memory, one or more antennas, a wireless interface for allowing the application processor to communicate with another device, and a touch-screen display.

[00145] Elements of Fig. 6, and elements of other figures having the same names or reference numbers, can operate or function in the manner described herein with respect to any such figures (although the operation and function of such elements is not limited to such descriptions). For example, Figs. 7-8 and 11-12 also depict embodiments of eNodeBs, hardware processing circuitry of eNodeBs, UEs, and/or hardware processing circuitry of UEs, and the embodiments described with respect to Fig. 6 and Figs. 7-8 and 11-12 can operate or function in the manner described herein with respect to any of the figures.

[00146] In addition, although eNodeB 610 and UE 630 are each described as having several separate functional elements, one or more of the functional elements may be combined and may be implemented by combinations of software-configured elements and/or other hardware elements. In some embodiments of this disclosure, the functional elements can refer to one or more processes operating on one or more processing elements. Examples of software and/or hardware configured elements include Digital Signal Processors (DSPs), one or more microprocessors, DSPs, Field-Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Radio-Frequency Integrated Circuits (RFICs), and so on.

[00147] Fig. 7 illustrates hardware processing circuitries for a UE for supporting

ENBs, in accordance with some embodiments of the disclosure. With reference to Fig. 6, a UE may include various hardware processing circuitries discussed herein (such as hardware processing circuitry 700 of Fig. 7), which may in turn comprise logic devices and/or circuitry operable to perform various operations. For example, in Fig. 6, UE 630 (or various elements or components therein, such as hardware processing circuitry 640, or combinations of elements or components therein) may include part of, or all of, these hardware processing circuitries.

[00148] In some embodiments, one or more devices or circuitries within these hardware processing circuitries may be implemented by combinations of software-configured elements and/or other hardware elements. For example, processor 636 (and/or one or more other processors which UE 630 may comprise), memory 638, and/or other elements or components of UE 630 (which may include hardware processing circuitry 640) may be arranged to perform the operations of these hardware processing circuitries, such as operations described herein with reference to devices and circuitry within these hardware processing circuitries. In some embodiments, processor 636 (and/or one or more other processors which UE 630 may comprise) may be a baseband processor.

[00149] Returning to Fig. 7, an apparatus of UE 630 (or another UE or mobile handset), which may be operable to communicate with one or more eNodeBs on a wireless network, may comprise hardware processing circuitry 700. In some embodiments, hardware processing circuitry 700 may comprise one or more antenna ports 705 operable to provide various transmissions over a wireless communication channel (such as wireless

communication channel 650). Antenna ports 705 may be coupled to one or more antennas 707 (which may be antennas 625). In some embodiments, hardware processing circuitry 700 may incorporate antennas 707, while in other embodiments, hardware processing circuitry 700 may merely be coupled to antennas 707.

[00150] Antenna ports 705 and antennas 707 may be operable to provide signals from a UE to a wireless communications channel and/or an eNodeB, and may be operable to provide signals from an eNodeB and/or a wireless communications channel to a UE. For example, antenna ports 705 and antennas 707 may be operable to provide transmissions from UE 630 to wireless communication channel 650 (and from there to eNodeB 610, or to another eNodeB). Similarly, antennas 707 and antenna ports 705 may be operable to provide transmissions from a wireless communication channel 650 (and beyond that, from eNodeB 610, or another eNodeB) to UE 630.

[00151] Hardware processing circuitry 700 may comprise various circuitries operable in accordance with the various embodiments discussed herein. With reference to Fig. 7, hardware processing circuitry 700 may comprise a first circuitry 710, a second circuitry 720, a third circuitry 730, and/or a fourth circuitry 740. First circuitry 710 may be operable to define a first set of one or more ENBs for DL transmissions spanning a first set of more than six RBs of the system bandwidth. First circuitry 710 may also be operable to define a second set of one or more ENBs for UL transmissions spanning a second set of more than six RBs of the system bandwidth. Second circuitry 720 may be operable to store one or more parameters of the first set of ENBs and one or more parameters of the second set of ENBs. For example, the parameters may be stored in any type of memory discussed herein. First circuitry 710 may be operable to provide one or more parameters of the first set of ENBs and one or more parameters of the second set of ENBs to second circuitry 720 via an interface 712.

[00152] In some embodiments, at least one of the first set of more than six RBs or the second set of more than six RBs may span more than six contiguous RBs of the system bandwidth. For some embodiments, the system bandwidth may comprise a plurality of NBs, and an ENB of the first set of ENBs may be defined to include the plurality of NBs for the DL. In some embodiments, the system bandwidth may comprise a plurality of NBs, and an ENB of the second set of ENBs may be defined to include the plurality of NBs for the UL. For some embodiments, the plurality of NBs in the UL may be contiguous. In some embodiments, the system bandwidth may be 3 MHz, 5 MHz, 10 MHz, 15 MHz, or 20 MHz.

[00153] For some embodiments, the system bandwidth may be at least 3 MHz, and at least one ENB of the first set of ENBs or the second set of ENBs may be defined to include at least 2 NBs. In some embodiments, the system bandwidth may be at least 5 MHz, and at least one ENB of the first set of ENBs or the second set of ENBs may be defined to include at least 4 NBs. For some embodiments, the system bandwidth may be at least 15 MHz, and at least one ENB of the first set of ENBs or the second set of ENBs may be defined to include at least 6 NBs. In some embodiments, the system bandwidth may be at least 20 MHz, and at least one ENB of the first set of ENBs or the second set of ENBs may be defined to include at least 8 NBs. For some embodiments, at least one ENB of the first set of ENBs or the second set of ENBs may be defined to include a plurality of NBs and also spans one or more RBs outside the plurality of NBs. [00154] In some embodiments, the one or more RBs outside the plurality of NBs may comprise an RB at an edge of the system bandwidth and/or an RB at a middle of the system bandwidth. For some embodiments, the first set of ENBs may be defined to include all RBs of the system bandwidth except for an RB at an edge of the system bandwidth and/or an RB at a middle of the system bandwidth. In some embodiments, a number of RBs spanned by the first set of ENBs matches a number of RBs spanned by the second set of ENBs. For some embodiments, the system bandwidth may be even, while in other embodiments, the system bandwidth may be odd.

[00155] For some embodiments, third circuitry 730 may be operable to process a transmission carrying one or more resource assignment indicators, the transmission being of: a DCI format 6-1 A, a DCI format 6-OA, a DCI format 6-1B, or a DCI format 6-OB. Third circuitry 730 may be operable to provide the one or more resource assignment indicators to first circuitry 710 via an interface 732.

[00156] In some embodiments, the ENBs of the first set of ENBs may have an increasing index matching an increasing index of the RBs of the first set of ENBs, and the ENBs of the second set of ENBs may have an increasing index matching an increasing index of the RBs of the second set of ENBs. For some embodiments, the one or more resource assignment indicators may comprise an ENB index indicator having a number of most significant bits of an RB assignment field based on a total number of ENBs in the first set of ENBs and/or the second set of ENBs. In some embodiments, the one or more resource assignment indicators may comprise a frequency resource indicator having a number of bits of an RB assignment field based on a number of NBs in an ENB of the first set of ENBs and/or an ENB of the second set of ENBs. For some embodiments, the frequency resource indicator may indicate a number of NBs starting from a reference NB. In some

embodiments, the one or more resource assignment indicators may comprise a reference NB indicator indicating the reference RB.

[00157] For some embodiments, the one or more resource assignment indicators may comprise a resource allocation bitmap indicator having at least a number of bits equal to a number of NBs in an ENB of the first set of ENBs and/or an ENB of the second set of ENBs. In some embodiments, the one or more resource assignment indicators may comprise a resource allocation indicator having a plurality of values respectively corresponding to a plurality of predetermined resource assignments. For some embodiments, the one or more resource assignment indicators may comprise a central PRB allocation indicator and/or an edge PRB allocation indicator. [00158] In some embodiments, fourth circuitry 740 may be operable to determine a hopped ENB frequency for an ENB of the first set of ENBs or the second set of ENBs in accordance with an ENB-granularity frequency -hopping offset. For some embodiments, third circuitry 730 may be operable to process a DCI transmission, and the DCI transmission may carry a frequency -hopping indicator to disable frequency hopping for allocations for which a frequency -hopping wrap-around could fragment an ENB.

[00159] For some embodiments, fourth circuitry 740 may be operable to determine a hopped NB frequency for an NB within one of the first set of ENBs or the second set of ENBs in accordance with an NB-granularity frequency-hopping offset. In some

embodiments, fourth circuitry 740 may be operable to determine a hopped ENB frequency for one of the first set of ENBs or the second set of ENBs, the hopped ENB encompassing the hopped NB frequency. First circuitry 710 may be operable to provide an ENB-granularity frequency -hopping offset and/or an NB-granularity frequency -hopping offset to fourth circuitry 740 via an interface 714.

[00160] In some embodiments, first circuitry 710, second circuitry 720, third circuitry

730, and/or fourth circuitry 740 may be implemented as separate circuitries. In other embodiments, first circuitry 710, second circuitry 720, third circuitry 730, and/or fourth circuitry 740 may be combined and implemented together in a circuitry without altering the essence of the embodiments.

[00161] Fig. 8 illustrates hardware processing circuitries for an eNodeB for supporting

ENBs, in accordance with some embodiments of the disclosure. With reference to Fig. 6, an eNodeB may include various hardware processing circuitries discussed herein (such as hardware processing circuitry 800 of Fig. 8), which may in turn comprise logic devices and/or circuitry operable to perform various operations. For example, in Fig. 6, eNodeB 610 (or various elements or components therein, such as hardware processing circuitry 620, or combinations of elements or components therein) may include part of, or all of, these hardware processing circuitries.

[00162] In some embodiments, one or more devices or circuitries within these hardware processing circuitries may be implemented by combinations of software-configured elements and/or other hardware elements. For example, processor 616 (and/or one or more other processors which eNodeB 610 may comprise), memory 618, and/or other elements or components of eNodeB 610 (which may include hardware processing circuitry 620) may be arranged to perform the operations of these hardware processing circuitries, such as operations described herein with reference to devices and circuitry within these hardware processing circuitries. In some embodiments, processor 616 (and/or one or more other processors which eNodeB 610 may comprise) may be a baseband processor.

[00163] Returning to Fig. 8, an apparatus of eNodeB 610 (or another eNodeB or base station), which may be operable to communicate with one or more UEs on a wireless network, may comprise hardware processing circuitry 800. In some embodiments, hardware processing circuitry 800 may comprise one or more antenna ports 805 operable to provide various transmissions over a wireless communication channel (such as wireless

communication channel 650). Antenna ports 805 may be coupled to one or more antennas 807 (which may be antennas 605). In some embodiments, hardware processing circuitry 800 may incorporate antennas 807, while in other embodiments, hardware processing circuitry 800 may merely be coupled to antennas 807.

[00164] Antenna ports 805 and antennas 807 may be operable to provide signals from an eNodeB to a wireless communications channel and/or a UE, and may be operable to provide signals from a UE and/or a wireless communications channel to an eNodeB. For example, antenna ports 805 and antennas 807 may be operable to provide transmissions from eNodeB 610 to wireless communication channel 650 (and from there to UE 630, or to another UE). Similarly, antennas 807 and antenna ports 805 may be operable to provide

transmissions from a wireless communication channel 650 (and beyond that, from UE 630, or another UE) to eNodeB 610.

[00165] Hardware processing circuitry 800 may comprise various circuitries operable in accordance with the various embodiments discussed herein. With reference to Fig. 8, hardware processing circuitry 800 may comprise a first circuitry 810, a second circuitry 820, a third circuitry 830, and/or a fourth circuitry 840. First circuitry 810 may be operable to define a first set of one or more ENBs for DL transmissions spanning a first set of more than six RBs of the system bandwidth. First circuitry 810 may also be operable to define a second set of one or more ENBs for UL transmissions spanning a second set of more than six RBs of the system bandwidth. Second circuitry 820 may be operable to store one or more parameters of the first set of ENBs and one or more parameters of the second set of ENBs. For example, the parameters may be stored in any type of memory discussed herein. First circuitry 810 may be operable to provide one or more parameters of the first set of ENBs and one or more parameters of the second set of ENBs to second circuitry 820 via an interface 812.

[00166] In some embodiments, at least one of the first set of more than six RBs or the second set of more than six RBs may span more than six contiguous RBs of the system bandwidth. For some embodiments, the system bandwidth may comprise a plurality of NBs, and an ENB of the first set of ENBs may be defined to include the plurality of NBs for the DL. In some embodiments, the system bandwidth may comprise a plurality of NBs, and an ENB of the second set of ENBs may be defined to include the plurality of NBs for the UL. For some embodiments, the plurality of NBs in the UL may be contiguous. In some embodiments, the system bandwidth may be 3 MHz, 5 MHz, 10 MHz, 15 MHz, or 20 MHz.

[00167] For some embodiments, the system bandwidth may be at least 3 MHz, and at least one ENB of the first set of ENBs or the second set of ENBs may be defined to include at least 2 NBs. In some embodiments, the system bandwidth may be at least 5 MHz, and at least one ENB of the first set of ENBs or the second set of ENBs may be defined to include at least 4 NBs. For some embodiments, the system bandwidth may be at least 15 MHz, and at least one ENB of the first set of ENBs or the second set of ENBs may be defined to include at least 6 NBs. In some embodiments, the system bandwidth may be at least 20 MHz, and at least one ENB of the first set of ENBs or the second set of ENBs may be defined to include at least 8 NBs. For some embodiments, at least one ENB of the first set of ENBs or the second set of ENBs may be defined to include a plurality of NBs and also spans one or more RBs outside the plurality of NBs.

[00168] In some embodiments, the one or more RBs outside the plurality of NBs may comprise an RB at an edge of the system bandwidth and/or an RB at a middle of the system bandwidth. For some embodiments, the first set of ENBs may be defined to include all RBs of the system bandwidth except for an RB at an edge of the system bandwidth and/or an RB at a middle of the system bandwidth. In some embodiments, a number of RBs spanned by the first set of ENBs matches a number of RBs spanned by the second set of ENBs. For some embodiments, the system bandwidth may be even, while in other embodiments, the system bandwidth may be odd.

[00169] For some embodiments, third circuitry 830 may be operable to generate a transmission carrying one or more resource assignment indicators, the transmission being of: a DCI format 6-1 A, a DCI format 6-OA, a DCI format 6-1B, or a DCI format 6-OB. First circuitry 810 may be operable to provide the one or more resource assignment indicators to third circuitry 830 via an interface 814.

[00170] In some embodiments, the ENBs of the first set of ENBs may have an increasing index matching an increasing index of the RBs of the first set of ENBs, and the ENBs of the second set of ENBs may have an increasing index matching an increasing index of the RBs of the second set of ENBs. For some embodiments, the one or more resource assignment indicators may comprise an ENB index indicator having a number of most significant bits of an RB assignment field based on a total number of ENBs in the first set of ENBs and/or the second set of ENBs. In some embodiments, the one or more resource assignment indicators may comprise a frequency resource indicator having a number of bits of an RB assignment field based on a number of NBs in an ENB of the first set of ENBs and/or an ENB of the second set of ENBs. For some embodiments, the frequency resource indicator may indicate a number of NBs starting from a reference NB. In some

[00171] For some embodiments, the one or more resource assignment indicators may comprise a resource allocation bitmap indicator having at least a number of bits equal to a number of NBs in an ENB of the first set of ENBs and/or an ENB of the second set of ENBs. In some embodiments, the one or more resource assignment indicators may comprise a resource allocation indicator having a plurality of values respectively corresponding to a plurality of predetermined resource assignments. For some embodiments, the one or more resource assignment indicators may comprise a central PRB allocation indicator and/or an edge PRB allocation indicator.

[00172] In some embodiments, fourth circuitry 840 may be operable to determine a hopped ENB frequency for an ENB of the first set of ENBs or the second set of ENBs in accordance with an ENB-granularity frequency -hopping offset. For some embodiments, third circuitry 830 may be operable to generate a DCI transmission, and the DCI transmission may carry a frequency -hopping indicator to disable frequency hopping for allocations for which a frequency -hopping wrap-around could fragment an ENB.

[00173] For some embodiments, fourth circuitry 840 may be operable to determine a hopped NB frequency for an NB within one of the first set of ENBs or the second set of ENBs in accordance with an NB-granularity frequency-hopping offset. In some

embodiments, fourth circuitry 840 may be operable to determine a hopped ENB frequency for one of the first set of ENBs or the second set of ENBs, the hopped ENB encompassing the hopped NB frequency. First circuitry 810 may be operable to provide an ENB-granularity frequency -hopping offset and/or an NB-granularity frequency -hopping offset to fourth circuitry 840 via an interface 716.

[00174] In some embodiments, first circuitry 810, second circuitry 820, third circuitry

830, and/or fourth circuitry 840 may be implemented as separate circuitries. In other embodiments, first circuitry 810, second circuitry 820, third circuitry 830, and/or fourth circuitry 840 may be combined and implemented together in a circuitry without altering the essence of the embodiments.

[00175] Fig. 9 illustrates methods for a UE for supporting ENBs, in accordance with some embodiments of the disclosure. With reference to Fig. 6, methods that may relate to UE 630 and hardware processing circuitry 640 are discussed herein. Although the actions in the method 900 of Fig. 9 and method 1000 of Fig. 10 are shown in a particular order, the order of the actions can be modified. Thus, the illustrated embodiments can be performed in a different order, and some actions may be performed in parallel. Some of the actions and/or operations listed in Figs. 9 and 10 are optional in accordance with certain embodiments. The numbering of the actions presented is for the sake of clarity and is not intended to prescribe an order of operations in which the various actions must occur. Additionally, operations from the various flows may be utilized in a variety of combinations.

[00176] Moreover, in some embodiments, machine readable storage media may have executable instructions that, when executed, cause UE 630 and/or hardware processing circuitry 640 to perform an operation comprising the methods of Figs. 9 and 10. Such machine readable storage media may include any of a variety of storage media, like magnetic storage media (e.g., magnetic tapes or magnetic disks), optical storage media (e.g., optical discs), electronic storage media (e.g., conventional hard disk drives, solid-state disk drives, or fiash-memory-based storage media), or any other tangible storage media or non-transitory storage media.

[00177] In some embodiments, an apparatus may comprise means for performing various actions and/or operations of the methods of Figs. 9 and 10.

[00178] Returning to Fig. 9, various methods may be in accordance with the various embodiments discussed herein. A method 900 may comprise a defining 910, a defining 915, and a storing 920. In various embodiments, method 900 may also comprise a processing 930, a determining 940, a processing 950, a determining 960, and/or a determining 965.

[00179] In defining 910, a first set of one or more ENBs for DL transmissions may be defined, spanning a first set of more than six RBs of the system bandwidth. In defining 915, a second set of one or more ENBs for UL transmissions may be defined, spanning a second set of more than six RBs of the system bandwidth. In storing 920, one or more parameters of the first set of ENBs and one or more parameters of the second set of ENBs may be stored.

[00180] In some embodiments, at least one of the first set of more than six RBs or the second set of more than six RBs may span more than six contiguous RBs of the system bandwidth. For some embodiments, the system bandwidth may comprise a plurality of NBs, and an ENB of the first set of ENBs may be defined to include the plurality of NBs for the DL. In some embodiments, the system bandwidth may comprise a plurality of NBs, and an ENB of the second set of ENBs may be defined to include the plurality of NBs for the UL. For some embodiments, the plurality of NBs in the UL may be contiguous. In some embodiments, the system bandwidth may be 3 MHz, 5 MHz, 10 MHz, 15 MHz, or 20 MHz.

[00181] For some embodiments, the system bandwidth may be at least 3 MHz, and at least one ENB of the first set of ENBs or the second set of ENBs may be defined to include at least 2 NBs. In some embodiments, the system bandwidth may be at least 5 MHz, and at least one ENB of the first set of ENBs or the second set of ENBs may be defined to include at least 4 NBs. For some embodiments, the system bandwidth may be at least 15 MHz, and at least one ENB of the first set of ENBs or the second set of ENBs may be defined to include at least 6 NBs. In some embodiments, the system bandwidth may be at least 20 MHz, and at least one ENB of the first set of ENBs or the second set of ENBs may be defined to include at least 8 NBs. For some embodiments, at least one ENB of the first set of ENBs or the second set of ENBs may be defined to include a plurality of NBs and also spans one or more RBs outside the plurality of NBs.

[00182] In some embodiments, the one or more RBs outside the plurality of NBs may comprise an RB at an edge of the system bandwidth and/or an RB at a middle of the system bandwidth. For some embodiments, the first set of ENBs may be defined to include all RBs of the system bandwidth except for an RB at an edge of the system bandwidth and/or an RB at a middle of the system bandwidth. In some embodiments, a number of RBs spanned by the first set of ENBs matches a number of RBs spanned by the second set of ENBs. For some embodiments, the system bandwidth may be even, while in other embodiments, the system bandwidth may be odd.

[00183] For some embodiments, in processing 930, a transmission carrying one or more resource assignment indicators may be processed, the transmission being of: a DCI format 6-1 A, a DCI format 6-OA, a DCI format 6-1B, or a DCI format 6-OB.

[00184] In some embodiments, the ENBs of the first set of ENBs may have an increasing index matching an increasing index of the RBs of the first set of ENBs, and the ENBs of the second set of ENBs may have an increasing index matching an increasing index of the RBs of the second set of ENBs. For some embodiments, the one or more resource assignment indicators may comprise an ENB index indicator having a number of most significant bits of an RB assignment field based on a total number of ENBs in the first set of ENBs and/or the second set of ENBs. In some embodiments, the one or more resource assignment indicators may comprise a frequency resource indicator having a number of bits of an RB assignment field based on a number of NBs in an ENB of the first set of ENBs and/or an ENB of the second set of ENBs. For some embodiments, the frequency resource indicator may indicate a number of NBs starting from a reference NB. In some

[00185] For some embodiments, the one or more resource assignment indicators may comprise a resource allocation bitmap indicator having at least a number of bits equal to a number of NBs in an ENB of the first set of ENBs and/or an ENB of the second set of ENBs. In some embodiments, the one or more resource assignment indicators may comprise a resource allocation indicator having a plurality of values respectively corresponding to a plurality of predetermined resource assignments. For some embodiments, the one or more resource assignment indicators may comprise a central PRB allocation indicator and/or an edge PRB allocation indicator.

[00186] In some embodiments, in determining 940, a hopped ENB frequency for an

ENB of the first set of ENBs or the second set of ENBs may be determined in accordance with an ENB-granularity frequency -hopping offset. For some embodiments, in processing 950, a DCI transmission may be processed, and the DCI transmission may carry a frequency- hopping indicator to disable frequency hopping for allocations for which a frequency- hopping wrap-around could fragment an ENB.

[00187] For some embodiments, in determining 960, a hopped NB frequency for an

NB within one of the first set of ENBs or the second set of ENBs may be determined in accordance with an NB-granularity frequency-hopping offset. In determining 965, a hopped ENB frequency for one of the first set of ENBs or the second set of ENBs may be determined, the hopped ENB encompassing the hopped NB frequency.

[00188] Fig. 10 illustrates methods for an eNodeB for supporting ENBs, in accordance with some embodiments of the disclosure. With reference to Fig. 6, various methods that may relate to eNodeB 610 and hardware processing circuitry 620 are discussed herein.

Although the actions in method 1000 of Fig. 10 are shown in a particular order, the order of the actions can be modified. Thus, the illustrated embodiments can be performed in a different order, and some actions may be performed in parallel. Some of the actions and/or operations listed in Fig. 10 are optional in accordance with certain embodiments. The numbering of the actions presented is for the sake of clarity and is not intended to prescribe an order of operations in which the various actions must occur. Additionally, operations from the various flows may be utilized in a variety of combinations.

[00189] Moreover, in some embodiments, machine readable storage media may have executable instructions that, when executed, cause eNodeB 610 and/or hardware processing circuitry 620 to perform an operation comprising the methods of Fig. 10. Such machine readable storage media may include any of a variety of storage media, like magnetic storage media (e.g., magnetic tapes or magnetic disks), optical storage media (e.g., optical discs), electronic storage media (e.g., conventional hard disk drives, solid-state disk drives, or flash- memory-based storage media), or any other tangible storage media or non-transitory storage media.

[00190] In some embodiments, an apparatus may comprise means for performing various actions and/or operations of the methods of Fig. 10.

[00191] Returning to Fig. 10, various methods may be in accordance with the various embodiments discussed herein. A method 1000 may comprise a defining 1010, a defining 1015, and a storing 1020. In various embodiments, method 1000 may also comprise a generating 1030, a determining 1040, a generating 1050, a determining 1060, and/or a determining 1065.

[00192] In defining 1010, a first set of one or more ENBs for DL transmissions may be defined, spanning a first set of more than six RBs of the system bandwidth. In defining 1015, a second set of one or more ENBs for UL transmissions may be defined, spanning a second set of more than six RBs of the system bandwidth. In storing 1020, one or more parameters of the first set of ENBs and one or more parameters of the second set of ENBs may be stored.

[00193] In some embodiments, at least one of the first set of more than six RBs or the second set of more than six RBs may span more than six contiguous RBs of the system bandwidth. For some embodiments, the system bandwidth may comprise a plurality of NBs, and an ENB of the first set of ENBs may be defined to include the plurality of NBs for the DL. In some embodiments, the system bandwidth may comprise a plurality of NBs, and an ENB of the second set of ENBs may be defined to include the plurality of NBs for the UL. For some embodiments, the plurality of NBs in the UL may be contiguous. In some embodiments, the system bandwidth may be 3 MHz, 5 MHz, 10 MHz, 15 MHz, or 20 MHz.

[00194] For some embodiments, the system bandwidth may be at least 3 MHz, and at least one ENB of the first set of ENBs or the second set of ENBs may be defined to include at least 2 NBs. In some embodiments, the system bandwidth may be at least 5 MHz, and at least one ENB of the first set of ENBs or the second set of ENBs may be defined to include at least 4 NBs. For some embodiments, the system bandwidth may be at least 15 MHz, and at least one ENB of the first set of ENBs or the second set of ENBs may be defined to include at least 6 NBs. In some embodiments, the system bandwidth may be at least 20 MHz, and at least one ENB of the first set of ENBs or the second set of ENBs may be defined to include at least 8 NBs. For some embodiments, at least one ENB of the first set of ENBs or the second set of ENBs may be defined to include a plurality of NBs and also spans one or more RBs outside the plurality of NBs.

[00195] In some embodiments, the one or more RBs outside the plurality of NBs may comprise an RB at an edge of the system bandwidth and/or an RB at a middle of the system bandwidth. For some embodiments, the first set of ENBs may be defined to include all RBs of the system bandwidth except for an RB at an edge of the system bandwidth and/or an RB at a middle of the system bandwidth. In some embodiments, a number of RBs spanned by the first set of ENBs matches a number of RBs spanned by the second set of ENBs. For some embodiments, the system bandwidth may be even, while in other embodiments, the system bandwidth may be odd.

[00196] In generating 1030, a transmission carrying one or more resource assignment indicators may be generated, the transmission being of: a DCI format 6-1A, a DCI format 6- 0A, a DCI format 6-1B, or a DCI format 6-OB.

[00197] In some embodiments, the ENBs of the first set of ENBs may have an increasing index matching an increasing index of the RBs of the first set of ENBs, and the ENBs of the second set of ENBs may have an increasing index matching an increasing index of the RBs of the second set of ENBs. For some embodiments, the one or more resource assignment indicators may comprise an ENB index indicator having a number of most significant bits of an RB assignment field based on a total number of ENBs in the first set of ENBs and/or the second set of ENBs. In some embodiments, the one or more resource assignment indicators may comprise a frequency resource indicator having a number of bits of an RB assignment field based on a number of NBs in an ENB of the first set of ENBs and/or an ENB of the second set of ENBs. For some embodiments, the frequency resource indicator may indicate a number of NBs starting from a reference NB. In some

[00198] For some embodiments, the one or more resource assignment indicators may comprise a resource allocation bitmap indicator having at least a number of bits equal to a number of NBs in an ENB of the first set of ENBs and/or an ENB of the second set of ENBs. In some embodiments, the one or more resource assignment indicators may comprise a resource allocation indicator having a plurality of values respectively corresponding to a plurality of predetermined resource assignments. For some embodiments, the one or more resource assignment indicators may comprise a central PRB allocation indicator and/or an edge PRB allocation indicator.

[00199] In determining 1040, a hopped ENB frequency for an ENB of the first set of

ENBs or the second set of ENBs in accordance with an ENB -granularity frequency -hopping offset. For some embodiments, in generating 1050, a DCI transmission may be generated, and the DCI transmission may carry a frequency -hopping indicator to disable frequency hopping for allocations for which a frequency -hopping wrap-around could fragment an ENB.

[00200] For some embodiments, in determining 1060, a hopped NB frequency for an

NB within one of the first set of ENBs or the second set of ENBs may be determined in accordance with an NB-granularity frequency -hopping offset. In determining 1065, a hopped ENB frequency for one of the first set of ENBs or the second set of ENBs may be determined, the hopped ENB encompassing the hopped NB frequency.

[00201] Fig. 11 illustrates example components of a device, in accordance with some embodiments of the disclosure. In some embodiments, the device 1 100 may include application circuitry 1 102, baseband circuitry 1104, Radio Frequency (RF) circuitry 1 106, front-end module (FEM) circuitry 1108, one or more antennas 11 10, and power management circuitry (PMC) 1 112 coupled together at least as shown. The components of the illustrated device 1100 may be included in a UE or a RAN node. In some embodiments, the device 1 100 may include less elements (e.g., a RAN node may not utilize application circuitry 1102, and instead include a processor/controller to process IP data received from an EPC). In some embodiments, the device 1 100 may include additional elements such as, for example, memory /storage, display, camera, sensor, or input/output (I/O) interface. In other embodiments, the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud-RAN (C- RAN) implementations).

[00202] The application circuitry 1 102 may include one or more application processors. For example, the application circuitry 1102 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors may be coupled with or may include memory /storage and may be configured to execute instructions stored in the memory /storage to enable various applications or operating systems to run on the device 1100. In some embodiments, processors of application circuitry 1102 may process IP data packets received from an EPC.

[00203] The baseband circuitry 1104 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 1104 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 1106 and to generate baseband signals for a transmit signal path of the RF circuitry 1106. Baseband processing circuity 1104 may interface with the application circuitry 1102 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 1106. For example, in some embodiments, the baseband circuitry 1104 may include a third generation (3G) baseband processor 1104A, a fourth generation (4G) baseband processor 1104B, a fifth generation (5G) baseband processor 1104C, or other baseband processor(s) 1104D for other existing generations, generations in development or to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuitry 1104 (e.g., one or more of baseband processors 1104A-D) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 1106. In other embodiments, some or all of the functionality of baseband processors 1104A-D may be included in modules stored in the memory 1104G and executed via a Central Processing Unit (CPU) 1104E. The radio control functions may include, but are not limited to, signal modulation/demodulation,

encoding/decoding, radio frequency shifting, etc. In some embodiments,

modulation/demodulation circuitry of the baseband circuitry 1104 may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry 1104 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and

encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.

[00204] In some embodiments, the baseband circuitry 1104 may include one or more audio digital signal processor(s) (DSP) 1104F. The audio DSP(s) 1104F may be include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments. Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuitry 1104 and the application circuitry 1102 may be implemented together such as, for example, on a system on a chip (SOC).

[00205] In some embodiments, the baseband circuitry 1 104 may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 1 104 may support communication with an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN). Embodiments in which the baseband circuitry 1 104 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[00206] RF circuitry 1 106 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 1106 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 1 106 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 1108 and provide baseband signals to the baseband circuitry 1104. RF circuitry 1 106 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 1 104 and provide RF output signals to the FEM circuitry 1 108 for transmission.

[00207] In some embodiments, the receive signal path of the RF circuitry 1 106 may include mixer circuitry 1106 A, amplifier circuitry 1106B and filter circuitry 1106C. In some embodiments, the transmit signal path of the RF circuitry 1106 may include filter circuitry 1 106C and mixer circuitry 1 106A. RF circuitry 1 106 may also include synthesizer circuitry 1 106D for synthesizing a frequency for use by the mixer circuitry 1106 A of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 1 106A of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 1 108 based on the synthesized frequency provided by synthesizer circuitry 1106D. The amplifier circuitry 1106B may be configured to amplify the down-converted signals and the filter circuitry 1 106C may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry 1104 for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals, although this is not a requirement. In some embodiments, mixer circuitry 1106 A of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.

[00208] In some embodiments, the mixer circuitry 1106A of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 1106D to generate RF output signals for the FEM circuitry 1108. The baseband signals may be provided by the baseband circuitry 1 104 and may be filtered by filter circuitry 1 106C.

[00209] In some embodiments, the mixer circuitry 1106A of the receive signal path and the mixer circuitry 1 106A of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively. In some embodiments, the mixer circuitry 1106 A of the receive signal path and the mixer circuitry 1 106A of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 1 106 A of the receive signal path and the mixer circuitry 1106 A may be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuitry 1 106A of the receive signal path and the mixer circuitry 1106A of the transmit signal path may be configured for super-heterodyne operation.

[00210] In some embodiments, the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternate embodiments, the RF circuitry 1 106 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 1 104 may include a digital baseband interface to communicate with the RF circuitry 1106.

[00211] In some dual-mode embodiments, a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.

[00212] In some embodiments, the synthesizer circuitry 1 106D may be a fractional-N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry 1106D may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

[00213] The synthesizer circuitry 1 106D may be configured to synthesize an output frequency for use by the mixer circuitry 1 106 A of the RF circuitry 1 106 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 1106D may be a fractional N/N+l synthesizer.

[00214] In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement. Divider control input may be provided by either the baseband circuitry 1104 or the applications processor 1 102 depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the applications processor 1 102.

[00215] Synthesizer circuitry 1 106D of the RF circuitry 1 106 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DP A). In some embodiments, the DMD may be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these embodiments, the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[00216] In some embodiments, synthesizer circuitry 1106D may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some embodiments, the output frequency may be a LO frequency (fLO). In some embodiments, the RF circuitry 1 106 may include an IQ/polar converter.

[00217] FEM circuitry 1 108 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 11 10, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 1 106 for further processing. FEM circuitry 1 108 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 1106 for transmission by one or more of the one or more antennas 11 10. In various embodiments, the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 1106, solely in the FEM 1108, or in both the RF circuitry 1106 and the FEM 1108.

[00218] In some embodiments, the FEM circuitry 1108 may include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 1106). The transmit signal path of the FEM circuitry 1108 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 1106), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 1110).

[00219] In some embodiments, the PMC 1112 may manage power provided to the baseband circuitry 1104. In particular, the PMC 1112 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion. The PMC 1112 may often be included when the device 1100 is capable of being powered by a battery, for example, when the device is included in a UE. The PMC 1112 may increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.

[00220] While Fig. 11 shows the PMC 1112 coupled only with the baseband circuitry 1104. However, in other embodiments, the PMC 1112 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 1102, RF circuitry 1106, or FEM 1108.

[00221] In some embodiments, the PMC 1112 may control, or otherwise be part of, various power saving mechanisms of the device 1100. For example, if the device 1100 is in an RRC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device 1100 may power down for brief intervals of time and thus save power.

[00222] If there is no data traffic activity for an extended period of time, then the device 1100 may transition off to an RRC Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The device 1100 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again. The device 1100 may not receive data in this state, in order to receive data, it must transition back to RRC Connected state. [00223] An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.

[00224] Processors of the application circuitry 1102 and processors of the baseband circuitry 1104 may be used to execute elements of one or more instances of a protocol stack. For example, processors of the baseband circuitry 1 104, alone or in combination, may be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 1 104 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers). As referred to herein, Layer 3 may comprise a radio resource control (RRC) layer, described in further detail below. As referred to herein, Layer 2 may comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below. As referred to herein, Layer 1 may comprise a physical (PHY) layer of a UE/RAN node, described in further detail below.

[00225] Fig. 12 illustrates example interfaces of baseband circuitry, in accordance with some embodiments of the disclosure. As discussed above, the baseband circuitry 1 104 of Fig. 11 may comprise processors 1 104A-1 104E and a memory 1104G utilized by said processors. Each of the processors 1 104A-1 104E may include a memory interface, 1204A- 1204E, respectively, to send/receive data to/from the memory 1104G.

[00226] The baseband circuitry 1104 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 1212 (e.g., an interface to send/receive data to/from memory extemal to the baseband circuitry 1104), an application circuitry interface 1214 (e.g., an interface to send/receive data to/from the application circuitry 1102 of Fig. 11), an RF circuitry interface 1216 (e.g., an interface to send/receive data to/from RF circuitry 1106 of Fig. 11), a wireless hardware connectivity interface 1218 (e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components), and a power management interface 1220 (e.g., an interface to send/receive power or control signals to/from the PMC 1 112.

[00227] It is pointed out that elements of any of the Figures herein having the same reference numbers and/or names as elements of any other Figure herein may, in various embodiments, operate or function in a manner similar those elements of the other Figure (without being limited to operating or functioning in such a manner).

[00228] Reference in the specification to "an embodiment," "one embodiment," "some embodiments," or "other embodiments" means that a particular feature, structure, or characteristic described in connection with the embodiments is included in at least some embodiments, but not necessarily all embodiments. The various appearances of "an embodiment," "one embodiment," or "some embodiments" are not necessarily all referring to the same embodiments. If the specification states a component, feature, structure, or characteristic "may," "might," or "could" be included, that particular component, feature, structure, or characteristic is not required to be included. If the specification or claim refers to "a" or "an" element, that does not mean there is only one of the elements. If the specification or claims refer to "an additional" element, that does not preclude there being more than one of the additional element.

[00229] Furthermore, the particular features, structures, functions, or characteristics may be combined in any suitable manner in one or more embodiments. For example, a first embodiment may be combined with a second embodiment anywhere the particular features, structures, functions, or characteristics associated with the two embodiments are not mutually exclusive.

[00230] While the disclosure has been described in conjunction with specific embodiments thereof, many alternatives, modifications and variations of such embodiments will be apparent to those of ordinary skill in the art in light of the foregoing description. For example, other memory architectures e.g., Dynamic RAM (DRAM) may use the

embodiments discussed. The embodiments of the disclosure are intended to embrace all such alternatives, modifications, and variations as to fall within the broad scope of the appended claims.

[00231] In addition, well known power/ground connections to integrated circuit (IC) chips and other components may or may not be shown within the presented figures, for simplicity of illustration and discussion, and so as not to obscure the disclosure. Further, arrangements may be shown in block diagram form in order to avoid obscuring the disclosure, and also in view of the fact that specifics with respect to implementation of such block diagram arrangements are highly dependent upon the platform within which the present disclosure is to be implemented (i.e., such specifics should be well within purview of one skilled in the art). Where specific details (e.g., circuits) are set forth in order to describe example embodiments of the disclosure, it should be apparent to one skilled in the art that the disclosure can be practiced without, or with variation of, these specific details. The description is thus to be regarded as illustrative instead of limiting.

[00232] The following examples pertain to further embodiments. Specifics in the examples may be used anywhere in one or more embodiments. All optional features of the apparatus described herein may also be implemented with respect to a method or process.

[00233] Example 1 provides an apparatus of a Machine-Type Communication (MTC) capable User Equipment (UE) operable to communicate with an MTC-capable Evolved Node B (eNodeB) on a wireless network spanning a system bandwidth, comprising: one or more processors to: define a first set of one or more Extended Narrowbands (ENBs) for Downlink (DL) transmissions spanning a first set of more than six Resource Blocks (RBs) of the system bandwidth; and define a second set of one or more ENBs for Uplink (UL) transmissions spanning a second set of more than six RBs of the system bandwidth, and a memory to: store one or more parameters of the first set of ENBs and one or more parameters of the second set of ENBs.

[00234] In example 2, the apparatus of example 1 , wherein at least one of the first set of more than six RBs or the second set of more than six RBs spans more than six contiguous RBs of the system bandwidth.

[00235] In example 3, the apparatus of either of examples 1 or 2, wherein the system bandwidth comprises a plurality of Narrowbands (NBs); and wherein an ENB of the first set of ENBs is defined to include the plurality of NBs for the DL.

[00236] In example 4, the apparatus of any of examples 1 through 3, wherein the system bandwidth comprises a plurality of Narrowbands (NBs); and wherein an ENB of the second set of ENBs is defined to include the plurality of NBs for the UL.

[00237] In example 5, the apparatus of example 4, wherein the plurality of NBs in the

UL are contiguous.

[00238] In example 6, the apparatus of any of examples 1 through 5, wherein the system bandwidth is one of: 3 megahertz (MHz), 5 MHz, 10 MHz, 15 MHz, or 20 MHz.

[00239] In example 7, the apparatus of any of examples 1 through 6, wherein the system bandwidth is at least 3 megahertz (MHz); and wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include at least 2 Narrowbands (NBs).

[00240] In example 8, the apparatus of any of examples 1 through 7, wherein the system bandwidth is at least 5 megahertz (MHz); and wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include at least 4 Narrowbands (NBs). [00241] In example 9, the apparatus of any of examples 1 through 8, wherein the system bandwidth is at least 15 megahertz (MHz); and wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include at least 6 Narrowbands (NBs).

[00242] In example 10, the apparatus of any of examples 1 through 9, wherein the system bandwidth is at least 20 megahertz (MHz); and wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include at least 8 Narrowbands (NBs).

[00243] In example 11 , the apparatus of any of examples 1 through 10, wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include a plurality of Narrowbands (NBs) and also spans one or more RBs outside the plurality of NBs.

[00244] In example 12, the apparatus of example 11 , wherein the one or more RBs outside the plurality of NBs comprises at least one of: an RB at an edge of the system bandwidth, or an RB at a middle of the system bandwidth.

[00245] In example 13, the apparatus of any of examples 1 through 12, wherein the first set of ENBs is defined to include all RBs of the system bandwidth except for one or more of: an RB at an edge of the system bandwidth, or an RB at a middle of the system bandwidth.

[00246] In example 14, the apparatus of any of examples 1 through 13, wherein a number of RBs spanned by the first set of ENBs matches a number of RBs spanned by the second set of ENBs.

[00247] In example 15, the apparatus of example 14, wherein the system bandwidth is even.

[00248] In example 16, the apparatus of any of examples 1 through 15, wherein the one or more processors are to: process a transmission carrying one or more resource assignment indicators, the transmission being of: a Downlink Control Information (DCI) format 6-1 A, a DCI format 6-OA, a DCI format 6-1B, or a DCI format 6-OB.

[00249] In example 17, the apparatus of example 16, wherein the ENBs of the first set of ENBs have an increasing index matching an increasing index of the RBs of the first set of ENBs; and wherein the ENBs of the second set of ENBs have an increasing index matching an increasing index of the RBs of the second set of ENBs.

[00250] In example 18, the apparatus of example 16, wherein the one or more resource assignment indicators comprises an ENB index indicator having a number of most significant bits of an RB assignment field based on a total number of ENBs in one of: the first set of ENBs, or the second set of ENBs. [00251] In example 19, the apparatus of example 16, wherein the one or more resource assignment indicators comprises a frequency resource indicator having a number of bits of an RB assignment field based on a number of Narrowbands (NBs) in one of: an ENB of the first set of ENBs, or an ENB of the second set of ENBs.

[00252] In example 20, the apparatus of example 19, wherein the frequency resource indicator indicates a number of NBs starting from a reference NB.

[00253] In example 21 , the apparatus of example 20, wherein the one or more resource assignment indicators comprises a reference NB indicator indicating the reference RB.

[00254] In example 22, the apparatus of example 16, wherein the one or more resource assignment indicators comprises a resource allocation bitmap indicator having at least a number of bits equal to a number of Narrowbands (NBs) in one of: an ENB of the first set of ENBs, or an ENB of the second set of ENBs.

[00255] In example 23, the apparatus any of examples 16 through 22, wherein the one or more resource assignment indicators comprises a resource allocation indicator having a plurality of values respectively corresponding to a plurality of predetermined resource assignments.

[00256] In example 24, the apparatus of any of examples 16 through 23, wherein the one or more resource assignment indicators comprises at least one of: a central PRB allocation indicator, or an edge PRB allocation indicator.

[00257] In example 25, the apparatus of any of examples 1 through 24, wherein the one or more processors are to: determine a hopped ENB frequency for an ENB of the first set of ENBs or the second set of ENBs in accordance with an ENB-granularity frequency- hopping offset.

[00258] In example 26, the apparatus of any of examples 1 through 25, wherein the one or more processors are to: process a Downlink Control Information (DCI) transmission, wherein the DCI transmission carries a frequency -hopping indicator to disable frequency hopping for allocations for which a frequency -hopping wrap-around could fragment an ENB.

[00259] In example 27, the apparatus of any of examples 1 through 26, wherein the one or more processors are to: determine a hopped NB frequency for an NB within one of the first set of ENBs or the second set of ENBs in accordance with an NB-granularity frequency- hopping offset; and determine a hopped ENB frequency for one of the first set of ENBs or the second set of ENBs, the hopped ENB encompassing the hopped NB frequency.

[00260] Example 28 provides a User Equipment (UE) device comprising an application processor, a memory, one or more antennas, a wireless interface for allowing the application processor to communicate with another device, and a touch-screen display, the UE device including the apparatus of any of examples 1 through 26.

[00261] Example 29 provides a method comprising: defining, for a User Equipment

(UE), a first set of one or more Extended Narrowbands (ENBs) for Downlink (DL) transmissions spanning a first set of more than six Resource Blocks (RBs) of the system bandwidth; defining a second set of one or more ENBs for Uplink (UL) transmissions spanning a second set of more than six RBs of the system bandwidth; and storing one or more parameters of the first set of ENBs and one or more parameters of the second set of ENBs.

[00262] In example 30, the method of example 29, wherein at least one of the first set of more than six RBs or the second set of more than six RBs spans more than six contiguous RBs of the system bandwidth.

[00263] In example 31, the method of either of examples 29 or 30, wherein the system bandwidth comprises a plurality of Narrowbands (NBs); and wherein an ENB of the first set of ENBs is defined to include the plurality of NBs for the DL.

[00264] In example 32, the method of any of examples 29 through 31 , wherein the system bandwidth comprises a plurality of Narrowbands (NBs); and wherein an ENB of the second set of ENBs is defined to include the plurality of NBs for the UL.

[00265] In example 33, the method of example 32, wherein the plurality of NBs in the

UL are contiguous.

[00266] In example 34, the method of any of examples 29 through 33, wherein the system bandwidth is one of: 3 megahertz (MHz), 5 MHz, 10 MHz, 15 MHz, or 20 MHz.

[00267] In example 35, the method of any of examples 29 through 34, wherein the system bandwidth is at least 3 megahertz (MHz); and wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include at least 2 Narrowbands (NBs).

[00268] In example 36, the method of any of examples 29 through 35, wherein the system bandwidth is at least 5 megahertz (MHz); and wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include at least 4 Narrowbands (NBs).

[00269] In example 37, the method of any of examples 29 through 36, wherein the system bandwidth is at least 15 megahertz (MHz); and wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include at least 6 Narrowbands (NBs).

[00270] In example 38, the method of any of examples 29 through 37, wherein the system bandwidth is at least 20 megahertz (MHz); and wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include at least 8 Narrowbands (NBs). [00271] In example 39, the method of any of examples 29 through 38, wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include a plurality of Narrowbands (NBs) and also spans one or more RBs outside the plurality of NBs.

[00272] In example 40, the method of example 39, wherein the one or more RBs outside the plurality of NBs comprises at least one of: an RB at an edge of the system bandwidth, or an RB at a middle of the system bandwidth.

[00273] In example 41 , the method of any of examples 29 through 40, wherein the first set of ENBs is defined to include all RBs of the system bandwidth except for one or more of: an RB at an edge of the system bandwidth, or an RB at a middle of the system bandwidth.

[00274] In example 42, the method of any of examples 29 through 41 , wherein a number of RBs spanned by the first set of ENBs matches a number of RBs spanned by the second set of ENBs.

[00275] In example 43, the method of example 42, wherein the system bandwidth is even.

[00276] In example 44, the method of any of examples 29 through 43, comprising: processing a transmission carrying one or more resource assignment indicators, the transmission being of: a Downlink Control Information (DCI) format 6-1 A, a DCI format 6- 0A, a DCI format 6-1B, or a DCI format 6-OB.

[00277] In example 45, the method of example 44, wherein the ENBs of the first set of

ENBs have an increasing index matching an increasing index of the RBs of the first set of ENBs; and wherein the ENBs of the second set of ENBs have an increasing index matching an increasing index of the RBs of the second set of ENBs.

[00278] In example 46, the method of example 44, wherein the one or more resource assignment indicators comprises an ENB index indicator having a number of most significant bits of an RB assignment field based on a total number of ENBs in one of: the first set of ENBs, or the second set of ENBs.

[00279] In example 47, the method of example 44, wherein the one or more resource assignment indicators comprises a frequency resource indicator having a number of bits of an RB assignment field based on a number of Narrowbands (NBs) in one of: an ENB of the first set of ENBs, or an ENB of the second set of ENBs.

[00280] In example 48, the method of example 47, wherein the frequency resource indicator indicates a number of NBs starting from a reference NB.

[00281] In example 49, the method of example 48, wherein the one or more resource assignment indicators comprises a reference NB indicator indicating the reference RB. [00282] In example 50, the method of example 44, wherein the one or more resource assignment indicators comprises a resource allocation bitmap indicator having at least a number of bits equal to a number of Narrowbands (NBs) in one of: an ENB of the first set of ENBs, or an ENB of the second set of ENBs.

[00283] In example 51 , the method of any of examples 44 through 50, wherein the one or more resource assignment indicators comprises a resource allocation indicator having a plurality of values respectively corresponding to a plurality of predetermined resource assignments.

[00284] In example 52, the method of any of examples 44 through 51 , wherein the one or more resource assignment indicators comprises at least one of: a central PRB allocation indicator, or an edge PRB allocation indicator.

[00285] In example 53, the method of any of examples 29 through 52, comprising: determining a hopped ENB frequency for an ENB of the first set of ENBs or the second set of ENBs in accordance with an ENB-granularity frequency -hopping offset.

[00286] In example 54, the method of any of examples 29 through 53, comprising: processing a Downlink Control Information (DCI) transmission, wherein the DCI transmission carries a frequency -hopping indicator to disable frequency hopping for allocations for which a frequency-hopping wrap-around could fragment an ENB.

[00287] In example 55, the method of any of examples 29 through 54, comprising: determining a hopped NB frequency for an NB within one of the first set of ENBs or the second set of ENBs in accordance with an NB-granularity frequency -hopping offset; and determining a hopped ENB frequency for one of the first set of ENBs or the second set of ENBs, the hopped ENB encompassing the hopped NB frequency.

[00288] Example 56 provides machine readable storage media having machine executable instructions stored thereon that, when executed, cause one or more processors to perform a method according to any of examples 29 through 55.

[00289] Example 57 provides an apparatus of a Machine-Type Communication (MTC) capable User Equipment (UE) operable to communicate with an MTC-capable Evolved Node B (eNodeB) on a wireless network spanning a system bandwidth, comprising: means for defining a first set of one or more Extended Narrowbands (ENBs) for Downlink (DL) transmissions spanning a first set of more than six Resource Blocks (RBs) of the system bandwidth; means for defining a second set of one or more ENBs for Uplink (UL) transmissions spanning a second set of more than six RBs of the system bandwidth; and means for storing one or more parameters of the first set of ENBs and one or more parameters of the second set of ENBs.

[00290] In example 58, the apparatus of example 57, wherein at least one of the first set of more than six RBs or the second set of more than six RBs spans more than six contiguous RBs of the system bandwidth.

[00291] In example 59, the apparatus of either of examples 57 or 58, wherein the system bandwidth comprises a plurality of Narrowbands (NBs); and wherein an ENB of the first set of ENBs is defined to include the plurality of NBs for the DL.

[00292] In example 60, the apparatus of any of examples 57 through 59, wherein the system bandwidth comprises a plurality of Narrowbands (NBs); and wherein an ENB of the second set of ENBs is defined to include the plurality of NBs for the UL.

[00293] In example 61, the apparatus of example 60, wherein the plurality of NBs in the UL are contiguous.

[00294] In example 62, the apparatus of any of examples 57 through 61, wherein the system bandwidth is one of: 3 megahertz (MHz), 5 MHz, 10 MHz, 15 MHz, or 20 MHz.

[00295] In example 63, the apparatus of any of examples 57 through 62, wherein the system bandwidth is at least 3 megahertz (MHz); and wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include at least 2 Narrowbands (NBs).

[00296] In example 64, the apparatus of any of examples 57 through 63, wherein the system bandwidth is at least 5 megahertz (MHz); and wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include at least 4 Narrowbands (NBs).

[00297] In example 65, the apparatus of any of examples 57 through 64, wherein the system bandwidth is at least 15 megahertz (MHz); and wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include at least 6 Narrowbands (NBs).

[00298] In example 66, the apparatus of any of examples 57 through 65, wherein the system bandwidth is at least 20 megahertz (MHz); and wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include at least 8 Narrowbands (NBs).

[00299] In example 67, the apparatus of any of examples 57 through 66, wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include a plurality of Narrowbands (NBs) and also spans one or more RBs outside the plurality of NBs.

[00300] In example 68, the apparatus of example 67, wherein the one or more RBs outside the plurality of NBs comprises at least one of: an RB at an edge of the system bandwidth, or an RB at a middle of the system bandwidth. [00301] In example 69, the apparatus of any of examples 57 through 68, wherein the first set of ENBs is defined to include all RBs of the system bandwidth except for one or more of: an RB at an edge of the system bandwidth, or an RB at a middle of the system bandwidth.

[00302] In example 70, the apparatus of any of examples 57 through 69, wherein a number of RBs spanned by the first set of ENBs matches a number of RBs spanned by the second set of ENBs.

[00303] In example 71 , the apparatus of example 70, wherein the system bandwidth is even.

[00304] In example 72, the apparatus of any of examples 57 through 71 , comprising: means for processing a transmission carrying one or more resource assignment indicators, the transmission being of: a Downlink Control Information (DCI) format 6-1 A, a DCI format 6- 0A, a DCI format 6-1B, or a DCI format 6-OB.

[00305] In example 73, the apparatus of example 72, wherein the ENBs of the first set of ENBs have an increasing index matching an increasing index of the RBs of the first set of ENBs; and wherein the ENBs of the second set of ENBs have an increasing index matching an increasing index of the RBs of the second set of ENBs.

[00306] In example 74, the apparatus of example 72, wherein the one or more resource assignment indicators comprises an ENB index indicator having a number of most significant bits of an RB assignment field based on a total number of ENBs in one of: the first set of ENBs, or the second set of ENBs.

[00307] In example 75, the apparatus of example 72, wherein the one or more resource assignment indicators comprises a frequency resource indicator having a number of bits of an RB assignment field based on a number of Narrowbands (NBs) in one of: an ENB of the first set of ENBs, or an ENB of the second set of ENBs.

[00308] In example 76, the apparatus of example 75, wherein the frequency resource indicator indicates a number of NBs starting from a reference NB.

[00309] In example 77, the apparatus of example 76, wherein the one or more resource assignment indicators comprises a reference NB indicator indicating the reference RB.

[00310] In example 78, the apparatus of example 72, wherein the one or more resource assignment indicators comprises a resource allocation bitmap indicator having at least a number of bits equal to a number of Narrowbands (NBs) in one of: an ENB of the first set of ENBs, or an ENB of the second set of ENBs. [00311] In example 79, the apparatus of any of examples 72 through 78, wherein the one or more resource assignment indicators comprises a resource allocation indicator having a plurality of values respectively corresponding to a plurality of predetermined resource assignments.

[00312] In example 80, the apparatus of any of examples 72 through 79, wherein the one or more resource assignment indicators comprises at least one of: a central PRB allocation indicator, or an edge PRB allocation indicator.

[00313] In example 81 , the apparatus of any of examples 57 through 80, comprising: means for determining a hopped ENB frequency for an ENB of the first set of ENBs or the second set of ENBs in accordance with an ENB-granularity frequency -hopping offset.

[00314] In example 82, the apparatus of any of examples 57 through 81 , comprising: means for processing a Downlink Control Information (DCI) transmission, wherein the DCI transmission carries a frequency -hopping indicator to disable frequency hopping for allocations for which a frequency-hopping wrap-around could fragment an ENB.

[00315] In example 83, the apparatus of any of examples 57 through 82, comprising: means for determining a hopped NB frequency for an NB within one of the first set of ENBs or the second set of ENBs in accordance with an NB-granularity frequency -hopping offset; and means for determining a hopped ENB frequency for one of the first set of ENBs or the second set of ENBs, the hopped ENB encompassing the hopped NB frequency.

[00316] Example 84 provides machine readable storage media having machine executable instructions that, when executed, cause one or more processors of a Machine-Type Communication (MTC) capable User Equipment (UE) operable to communicate with an MTC-capable Evolved Node-B (eNodeB) on a wireless network spanning a system bandwidth to perform an operation comprising: define a first set of one or more Extended Narrowbands (ENBs) for Downlink (DL) transmissions spanning a first set of more than six Resource Blocks (RBs) of the system bandwidth; define a second set of one or more ENBs for Uplink (UL) transmissions spanning a second set of more than six RBs of the system bandwidth; and store one or more parameters of the first set of ENBs and one or more parameters of the second set of ENBs.

[00317] In example 85, the machine readable storage media of example 84, wherein at least one of the first set of more than six RBs or the second set of more than six RBs spans more than six contiguous RBs of the system bandwidth. [00318] In example 86, the machine readable storage media of either of examples 84 or

85, wherein the system bandwidth comprises a plurality of Narrowbands (NBs); and wherein an ENB of the first set of ENBs is defined to include the plurality of NBs for the DL.

[00319] In example 87, the machine readable storage media of any of examples 84 through 86, wherein the system bandwidth comprises a plurality of Narrowbands (NBs); and wherein an ENB of the second set of ENBs is defined to include the plurality of NBs for the UL.

[00320] In example 88, the machine readable storage media of example 87, wherein the plurality of NBs in the UL are contiguous.

[00321] In example 89, the machine readable storage media of any of examples 84 through 88, wherein the system bandwidth is one of: 3 megahertz (MHz), 5 MHz, 10 MHz, 15 MHz, or 20 MHz.

[00322] In example 90, the machine readable storage media of any of examples 84 through 89, wherein the system bandwidth is at least 3 megahertz (MHz); and wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include at least 2 Narrowbands (NBs).

[00323] In example 91, the machine readable storage media of any of examples 84 through 90, wherein the system bandwidth is at least 5 megahertz (MHz); and wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include at least 4 Narrowbands (NBs).

[00324] In example 92, the machine readable storage media of any of examples 84 through 91, wherein the system bandwidth is at least 15 megahertz (MHz); and wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include at least 6 Narrowbands (NBs).

[00325] In example 93, the machine readable storage media of any of examples 84 through 92, wherein the system bandwidth is at least 20 megahertz (MHz); and wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include at least 8 Narrowbands (NBs).

[00326] In example 94, the machine readable storage media of any of examples 84 through 93, wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include a plurality of Narrowbands (NBs) and also spans one or more RBs outside the plurality of NBs. [00327] In example 95, the machine readable storage media of example 94, wherein the one or more RBs outside the plurality of NBs comprises at least one of: an RB at an edge of the system bandwidth, or an RB at a middle of the system bandwidth.

[00328] In example 96, the machine readable storage media of any of examples 84 through 95, wherein the first set of ENBs is defined to include all RBs of the system bandwidth except for one or more of: an RB at an edge of the system bandwidth, or an RB at a middle of the system bandwidth.

[00329] In example 97, the machine readable storage media of any of examples 84 through 96, wherein a number of RBs spanned by the first set of ENBs matches a number of RBs spanned by the second set of ENBs.

[00330] In example 98, the machine readable storage media of example 97, wherein the system bandwidth is even.

[00331] In example 99, the machine readable storage media of any of examples 84 through 98, the operation comprising: process a transmission carrying one or more resource assignment indicators, the transmission being of: a Downlink Control Information (DCI) format 6-1 A, a DCI format 6-OA, a DCI format 6-1B, or a DCI format 6-OB.

[00332] In example 100, the machine readable storage media of example 99, wherein the ENBs of the first set of ENBs have an increasing index matching an increasing index of the RBs of the first set of ENBs; and wherein the ENBs of the second set of ENBs have an increasing index matching an increasing index of the RBs of the second set of ENBs.

[00333] In example 101, the machine readable storage media of example 99, wherein the one or more resource assignment indicators comprises an ENB index indicator having a number of most significant bits of an RB assignment field based on a total number of ENBs in one of: the first set of ENBs, or the second set of ENBs.

[00334] In example 102, the machine readable storage media of example 99, wherein the one or more resource assignment indicators comprises a frequency resource indicator having a number of bits of an RB assignment field based on a number of Narrowbands (NBs) in one of: an ENB of the first set of ENBs, or an ENB of the second set of ENBs.

[00335] In example 103, the machine readable storage media of example 102, wherein the frequency resource indicator indicates a number of NBs starting from a reference NB.

[00336] In example 104, the machine readable storage media of example 103, wherein the one or more resource assignment indicators comprises a reference NB indicator indicating the reference RB. [00337] In example 105, the machine readable storage media of example 99, wherein the one or more resource assignment indicators comprises a resource allocation bitmap indicator having at least a number of bits equal to a number of Narrowbands (NBs) in one of: an ENB of the first set of ENBs, or an ENB of the second set of ENBs.

[00338] In example 106, the machine readable storage media of any of examples 99 through 105, wherein the one or more resource assignment indicators comprises a resource allocation indicator having a plurality of values respectively corresponding to a plurality of predetermined resource assignments.

[00339] In example 107, the machine readable storage media of any of examples 99 through 106, wherein the one or more resource assignment indicators comprises at least one of: a central PRB allocation indicator, or an edge PRB allocation indicator.

[00340] In example 108, the machine readable storage media of any of examples 84 through 107, the operation comprising: determine a hopped ENB frequency for an ENB of the first set of ENBs or the second set of ENBs in accordance with an ENB -granularity frequency -hopping offset.

[00341] In example 109, the machine readable storage media of any of examples 84 through 108, the operation comprising: process a Downlink Control Information (DCI) transmission, wherein the DCI transmission carries a frequency-hopping indicator to disable frequency hopping for allocations for which a frequency -hopping wrap-around could fragment an ENB.

[00342] In example 110, the machine readable storage media of any of examples 84 through 109, the operation comprising: determine a hopped NB frequency for an NB within one of the first set of ENBs or the second set of ENBs in accordance with an NB-granularity frequency -hopping offset; and determine a hopped ENB frequency for one of the first set of ENBs or the second set of ENBs, the hopped ENB encompassing the hopped NB frequency.

[00343] Example 11 1 provides an apparatus of a Machine-Type Communication

(MTC) capable Evolved Node B (eNodeB) operable to communicate with an MTC-capable User Equipment (UE) on a wireless network spanning a system bandwidth, comprising: one or more processors to: define a first set of one or more Extended Narrowbands (ENBs) for Downlink (DL) transmissions spanning a first set of more than six Resource Blocks (RBs) of the system bandwidth; and define a second set of one or more ENBs for Uplink (UL) transmissions spanning a second set of more than six RBs of the system bandwidth, and a memory to: store one or more parameters of the first set of ENBs and one or more parameters of the second set of ENBs. [00344] In example 112, the apparatus of example 111, wherein at least one of the first set of more than six RBs or the second set of more than six RBs spans more than six contiguous RBs of the system bandwidth.

[00345] In example 113, the apparatus of either of examples 111 or 112, wherein the system bandwidth comprises a plurality of Narrowbands (NBs); and wherein an ENB of the first set of ENBs is defined to include the plurality of NBs for the DL.

[00346] In example 114, the apparatus of any of examples 111 through 113, wherein the system bandwidth comprises a plurality of Narrowbands (NBs); and wherein an ENB of the second set of ENBs is defined to include the plurality of NBs for the UL.

[00347] In example 115, the apparatus of example 114, wherein the plurality of NBs in the UL are contiguous.

[00348] In example 116, the apparatus of any of examples 111 through 115, wherein the system bandwidth is one of: 3 megahertz (MHz), 5 MHz, 10 MHz, 15 MHz, or 20 MHz.

[00349] In example 117, the apparatus of any of examples 111 through 116, wherein the system bandwidth is at least 3 megahertz (MHz); and wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include at least 2 Narrowbands (NBs).

[00350] In example 118, the apparatus of any of examples 111 through 117, wherein the system bandwidth is at least 5 megahertz (MHz); and wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include least 4 Narrowbands (NBs).

[00351] In example 119, the apparatus of any of examples 111 through 118, wherein the system bandwidth is at least 15 megahertz (MHz); and wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include at least 6 Narrowbands (NBs).

[00352] In example 120, the apparatus of any of examples 111 through 119, wherein the system bandwidth is at least 20 megahertz (MHz); and wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include at least 8 Narrowbands (NBs).

[00353] In example 121, the apparatus of any of examples 111 through 120, wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include a plurality of Narrowbands (NBs) and also spans one or more RBs outside the plurality of NBs.

[00354] In example 122, the apparatus of example 121, wherein the one or more RBs outside the plurality of NBs comprises at least one of: an RB at an edge of the system bandwidth, or an RB at a middle of the system bandwidth. [00355] In example 123, the apparatus of any of examples 1 11 through 122, wherein the first set of ENBs is defined to include all RBs of the system bandwidth except for one or more of: an RB at an edge of the system bandwidth, or an RB at a middle of the system bandwidth.

[00356] In example 124, the apparatus of any of examples 1 11 through 123, wherein a number of RBs spanned by the first set of ENBs matches a number of RBs spanned by the second set of ENBs.

[00357] In example 125, the apparatus of example 124, wherein the system bandwidth is even.

[00358] In example 126, the apparatus of any of examples 1 11 through 125, wherein the one or more processors are to: generate a transmission carrying one or more resource assignment indicators, the transmission being of: a Downlink Control Information (DCI) format 6-1 A, a DCI format 6-OA, a DCI format 6-1B, or a DCI format 6-OB.

[00359] In example 127, the apparatus of example 126, wherein the ENBs of the first set of ENBs have an increasing index matching an increasing index of the RBs of the first set of ENBs; and wherein the ENBs of the second set of ENBs have an increasing index matching an increasing index of the RBs of the second set of ENBs.

[00360] In example 128, the apparatus of example 126, wherein the one or more resource assignment indicators comprises an ENB index indicator having a number of most significant bits of an RB assignment field based on a total number of ENBs in one of: the first set of ENBs, or the second set of ENBs.

[00361] In example 129, the apparatus of example 126, wherein the one or more resource assignment indicators comprises a frequency resource indicator having a number of bits of an RB assignment field based on a number of Narrowbands (NBs) in one of: an ENB of the first set of ENBs, or an ENB of the second set of ENBs.

[00362] In example 130, the apparatus of example 129, wherein the frequency resource indicator indicates a number of NBs starting from a reference NB.

[00363] In example 131, the apparatus of example 130, wherein the one or more resource assignment indicators comprises a reference NB indicator indicating the reference

RB.

[00364] In example 132, the apparatus of example 126, wherein the one or more resource assignment indicators comprises a resource allocation bitmap indicator having at least a number of bits equal to a number of Narrowbands (NBs) in one of: an ENB of the first set of ENBs, or an ENB of the second set of ENBs. [00365] In example 133, the apparatus of any of examples 126 through 132, wherein the one or more resource assignment indicators comprises a resource allocation indicator having a plurality of values respectively corresponding to a plurality of predetermined resource assignments.

[00366] In example 134, the apparatus of any of examples 126 through 133, wherein the one or more resource assignment indicators comprises at least one of: a central PRB allocation indicator, or an edge PRB allocation indicator.

[00367] In example 135, the apparatus of any of examples 1 11 through 134, wherein the one or more processors are to: determine a hopped ENB frequency for an ENB of the first set of ENBs or the second set of ENBs in accordance with an ENB-granularity frequency- hopping offset.

[00368] In example 136, the apparatus of any of examples 1 11 through 135, wherein the one or more processors are to: generate a Downlink Control Information (DCI) transmission, wherein the DCI transmission carries a frequency-hopping indicator to disable frequency hopping for allocations for which a frequency -hopping wrap-around could fragment an ENB.

[00369] In example 137, the apparatus of any of examples 1 11 through 136, wherein the one or more processors are to: determine a hopped NB frequency for an NB within one of the first set of ENBs or the second set of ENBs in accordance with an NB-granularity frequency -hopping offset; and determine a hopped ENB frequency for one of the first set of ENBs or the second set of ENBs, the hopped ENB encompassing the hopped NB frequency.

[00370] Example 138 provides a Machine-Type Communication (MTC) capable

Evolved Node B (eNodeB) device comprising an application processor, a memory, one or more antenna ports, and an interface for allowing the application processor to communicate with another device, the eNodeB device including the apparatus of any of examples 11 1 through 137.

[00371] Example 139 provides a method comprising: defining, for an Evolved Node-B

(eNodeB), a first set of one or more Extended Narrowbands (ENBs) for Downlink (DL) transmissions spanning a first set of more than six Resource Blocks (RBs) of the system bandwidth; defining a second set of one or more ENBs for Uplink (UL) transmissions spanning a second set of more than six RBs of the system bandwidth; and storing one or more parameters of the first set of ENBs and one or more parameters of the second set of ENBs. [00372] In example 140, the method of example 139, wherein at least one of the first set of more than six RBs or the second set of more than six RBs spans more than six contiguous RBs of the system bandwidth.

[00373] In example 141, the method of either of examples 139 or 140, wherein the system bandwidth comprises a plurality of Narrowbands (NBs); and wherein an ENB of the first set of ENBs is defined to include the plurality of NBs for the DL.

[00374] In example 142, the method of any of examples 139 through 141, wherein the system bandwidth comprises a plurality of Narrowbands (NBs); and wherein an ENB of the second set of ENBs is defined to include the plurality of NBs for the UL.

[00375] In example 143, the method of example 142, wherein the plurality of NBs in the UL are contiguous.

[00376] In example 144, the method of any of examples 139 through 143, wherein the system bandwidth is one of: 3 megahertz (MHz), 5 MHz, 10 MHz, 15 MHz, or 20 MHz.

[00377] In example 145, the method of any of examples 139 through 144, wherein the system bandwidth is at least 3 megahertz (MHz); and wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include at least 2 Narrowbands (NBs).

[00378] In example 146, the method of any of examples 139 through 145, wherein the system bandwidth is at least 5 megahertz (MHz); and wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include at least 4 Narrowbands (NBs).

[00379] In example 147, the method of any of examples 139 through 146, wherein the system bandwidth is at least 15 megahertz (MHz); and wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include at least 6 Narrowbands (NBs).

[00380] In example 148, the method of any of examples 139 through 147, wherein the system bandwidth is at least 20 megahertz (MHz); and wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include at least 8 Narrowbands (NBs).

[00381] In example 149, the method of any of examples 139 through 148, wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include a plurality of Narrowbands (NBs) and also spans one or more RBs outside the plurality of NBs.

[00382] In example 150, the method of example 149, wherein the one or more RBs outside the plurality of NBs comprises at least one of: an RB at an edge of the system bandwidth, or an RB at a middle of the system bandwidth.

[00383] In example 151, the method of any of examples 139 through 150, wherein the first set of ENBs is defined to include all RBs of the system bandwidth except for one of more of: an RB at an edge of the system bandwidth, or an RB at a middle of the system bandwidth.

[00384] In example 152, the method of any of examples 139 through 151 , wherein a number of RBs spanned by the first set of ENBs matches a number of RBs spanned by the second set of ENBs.

[00385] In example 153, the method of example 152, wherein the system bandwidth is even.

[00386] In example 154, the method of any of examples 139 through 153, the operation comprising: generating a transmission carrying one or more resource assignment indicators, the transmission being of: a Downlink Control Information (DCI) format 6-1 A, a DCI format 6-0 A, a DCI format 6-1B, or a DCI format 6-OB.

[00387] In example 155, the method of example 154, wherein the ENBs of the first set of ENBs have an increasing index matching an increasing index of the RBs of the first set of ENBs; and wherein the ENBs of the second set of ENBs have an increasing index matching an increasing index of the RBs of the second set of ENBs.

[00388] In example 156, the method of example 154, wherein the one or more resource assignment indicators comprises an ENB index indicator having a number of most significant bits of an RB assignment field based on a total number of ENBs in one of: the first set of ENBs, or the second set of ENB.

[00389] In example 157, the method of example 154, wherein the one or more resource assignment indicators comprises a frequency resource indicator having a number of bits of an RB assignment field based on a number of Narrowbands (NBs) in one of: an ENB of the first set of ENBs, or an ENB of the second set of ENBs.

[00390] In example 158, the method of example 157, wherein the frequency resource indicator indicates a number of NBs starting from a reference NB.

[00391] In example 159, the method of example 158, wherein the one or more resource assignment indicators comprises a reference NB indicator indicating the reference RB.

[00392] In example 160, the method of example 154, wherein the one or more resource assignment indicators comprises a resource allocation bitmap indicator having at least a number of bits equal to a number of Narrowbands (NBs) in one of: an ENB of the first set of ENBs, or an ENB of the second set of ENBs.

[00393] In example 161, the method of any of examples 154 through 160, wherein the one or more resource assignment indicators comprises a resource allocation indicator having a plurality of values respectively corresponding to a plurality of predetermined resource assignments.

[00394] In example 162, the method of any of examples 154 through 161 , wherein the one or more resource assignment indicators comprises at least one of: a central PRB allocation indicator, or an edge PRB allocation indicator.

[00395] In example 163, the method of any of examples 139 through 162, the operation comprising: determining a hopped ENB frequency for an ENB of the first set of ENBs or the second set of ENBs in accordance with an ENB -granularity frequency -hopping offset.

[00396] In example 164, the method of any of examples 139 through 163, the operation comprising: generating a Downlink Control Information (DCI) transmission, wherein the DCI transmission carries a frequency -hopping indicator to disable frequency hopping for allocations for which a frequency -hopping wrap-around could fragment an ENB.

[00397] In example 165, the method of any of examples 139 through 164, the operation comprising: determining a hopped NB frequency for an NB within one of the first set of ENBs or the second set of ENBs in accordance with an NB-granularity frequency- hopping offset; and determining a hopped ENB frequency for one of the first set of ENBs or the second set of ENBs, the hopped ENB encompassing the hopped NB frequency.

[00398] Example 166 provides machine readable storage media having machine executable instructions stored thereon that, when executed, cause one or more processors to perform a method according to any of examples 139 through 165.

[00399] Example 167 provides an apparatus of a Machine-Type Communication

(MTC) capable Evolved Node B (eNodeB) operable to communicate with an MTC-capable User Equipment (UE) on a wireless network spanning a system bandwidth, comprising: means for defining a first set of one or more Extended Narrowbands (ENBs) for Downlink (DL) transmissions spanning a first set of more than six Resource Blocks (RBs) of the system bandwidth; means for defining a second set of one or more ENBs for Uplink (UL) transmissions spanning a second set of more than six RBs of the system bandwidth; and means for storing one or more parameters of the first set of ENBs and one or more parameters of the second set of ENBs.

[00400] In example 168, the apparatus of example 167, wherein at least one of the first set of more than six RBs or the second set of more than six RBs spans more than six contiguous RBs of the system bandwidth. [00401] In example 169, the apparatus of either of examples 167 or 168, wherein the system bandwidth comprises a plurality of Narrowbands (NBs); and wherein an ENB of the first set of ENBs is defined to include the plurality of NBs for the DL.

[00402] In example 170, the apparatus of any of examples 167 through 169, wherein the system bandwidth comprises a plurality of Narrowbands (NBs); and wherein an ENB of the second set of ENBs is defined to include the plurality of NBs for the UL.

[00403] In example 171, the apparatus of example 170, wherein the plurality of NBs in the UL are contiguous.

[00404] In example 172, the apparatus of any of examples 167 through 171, wherein the system bandwidth is one of: 3 megahertz (MHz), 5 MHz, 10 MHz, 15 MHz, or 20 MHz.

[00405] In example 173, the apparatus of any of examples 167 through 172, wherein the system bandwidth is at least 3 megahertz (MHz); and wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include at least 2 Narrowbands (NBs).

[00406] In example 174, the apparatus of any of examples 167 through 173, wherein the system bandwidth is at least 5 megahertz (MHz); and wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include at least 4 Narrowbands (NBs).

[00407] In example 175, the apparatus of any of examples 167 through 174, wherein the system bandwidth is at least 15 megahertz (MHz); and wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include at least 6 Narrowbands (NBs).

[00408] In example 176, the apparatus of any of examples 167 through 175, wherein the system bandwidth is at least 20 megahertz (MHz); and wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include at least 8 Narrowbands (NBs).

[00409] In example 177, the apparatus of any of examples 167 through 176, wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include a plurality of Narrowbands (NBs) and also spans one or more RBs outside the plurality of NBs.

[00410] In example 178, the apparatus of example 177, wherein the one or more RBs outside the plurality of NBs comprises at least one of: an RB at an edge of the system bandwidth, or an RB at a middle of the system bandwidth.

[00411] In example 179, the apparatus of any of examples 167 through 178, wherein the first set of ENBs is defined to include all RBs of the system bandwidth except for one of more of: an RB at an edge of the system bandwidth, or an RB at a middle of the system bandwidth.

[00412] In example 180, the apparatus of any of examples 167 through 179, wherein a number of RBs spanned by the first set of ENBs matches a number of RBs spanned by the second set of ENBs.

[00413] In example 181 , the apparatus of example 180, wherein the system bandwidth is even.

[00414] In example 182, the apparatus of any of examples 167 through 181 , the operation comprising: means for generating a transmission carrying one or more resource assignment indicators, the transmission being of: a Downlink Control Information (DCI) format 6-1 A, a DCI format 6-OA, a DCI format 6-1B, or a DCI format 6-OB.

[00415] In example 183, the apparatus of example 182, wherein the ENBs of the first set of ENBs have an increasing index matching an increasing index of the RBs of the first set of ENBs; and wherein the ENBs of the second set of ENBs have an increasing index matching an increasing index of the RBs of the second set of ENBs.

[00416] In example 184, the apparatus of example 182, wherein the one or more resource assignment indicators comprises an ENB index indicator having a number of most significant bits of an RB assignment field based on a total number of ENBs in one of: the first set of ENBs, or the second set of ENB.

[00417] In example 185, the apparatus of example 182, wherein the one or more resource assignment indicators comprises a frequency resource indicator having a number of bits of an RB assignment field based on a number of Narrowbands (NBs) in one of: an ENB of the first set of ENBs, or an ENB of the second set of ENBs.

[00418] In example 186, the apparatus of example 185, wherein the frequency resource indicator indicates a number of NBs starting from a reference NB.

[00419] In example 187, the apparatus of example 186, wherein the one or more resource assignment indicators comprises a reference NB indicator indicating the reference

RB.

[00420] In example 188, the apparatus of example 182, wherein the one or more resource assignment indicators comprises a resource allocation bitmap indicator having at least a number of bits equal to a number of Narrowbands (NBs) in one of: an ENB of the first set of ENBs, or an ENB of the second set of ENBs.

[00421] In example 189, the apparatus of any of examples 182 through 188, wherein the one or more resource assignment indicators comprises a resource allocation indicator having a plurality of values respectively corresponding to a plurality of predetermined resource assignments.

[00422] In example 190, the apparatus of any of examples 182 through 189, wherein the one or more resource assignment indicators comprises at least one of: a central PRB allocation indicator, or an edge PRB allocation indicator.

[00423] In example 191, the apparatus of any of examples 167 through 190, the operation comprising: means for determining a hopped ENB frequency for an ENB of the first set of ENBs or the second set of ENBs in accordance 182an ENB-granularity frequency- hopping offset.

[00424] In example 192, the apparatus of any of examples 167 through 191 , the operation comprising: means for generating a Downlink Control Information (DCI) transmission, wherein the DCI transmission carries a frequency-hopping indicator to disable frequency hopping for allocations for which a frequency -hopping wrap-around could fragment an ENB.

[00425] In example 193, the apparatus of any of examples 167 through 192, the operation comprising: means for determining a hopped NB frequency for an NB within one of the first set of ENBs or the second set of ENBs in accordance with an NB-granularity frequency -hopping offset; and means for determining a hopped ENB frequency for one of the first set of ENBs or the second set of ENBs, the hopped ENB encompassing the hopped NB frequency.

[00426] Example 194 provides machine readable storage media having machine executable instructions that, when executed, cause one or more processors of a Machine-Type Communication (MTC) capable Evolved Node B (eNodeB) operable to communicate with an MTC-capable User Equipment (UE) on a wireless network spanning a system bandwidth to perform an operation comprising: define a first set of one or more Extended Narrowbands (ENBs) for Downlink (DL) transmissions spanning a first set of more than six Resource Blocks (RBs) of the system bandwidth; define a second set of one or more ENBs for Uplink (UL) transmissions spanning a second set of more than six RBs of the system bandwidth; and store one or more parameters of the first set of ENBs and one or more parameters of the second set of ENBs.

[00427] In example 195, the machine readable storage media of example 194, wherein at least one of the first set of more than six RBs or the second set of more than six RBs spans more than six contiguous RBs of the system bandwidth. [00428] In example 196, the machine readable storage media of either of examples 194 or 195, wherein the system bandwidth comprises a plurality of Narrowbands (NBs); and wherein an ENB of the first set of ENBs is defined to include the plurality of NBs for the DL.

[00429] In example 197, the machine readable storage media of any of examples 194 through 196, wherein the system bandwidth comprises a plurality of Narrowbands (NBs); and wherein an ENB of the second set of ENBs is defined to include the plurality of NBs for the UL.

[00430] In example 198, the machine readable storage media of example 197, wherein the plurality of NBs in the UL are contiguous.

[00431] In example 199, the machine readable storage media of any of examples 194 through 198, wherein the system bandwidth is one of: 3 megahertz (MHz), 5 MHz, 10 MHz, 15 MHz, or 20 MHz.

[00432] In example 200, the machine readable storage media of any of examples 194 through 199, wherein the system bandwidth is at least 3 megahertz (MHz); and wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include at least 2 Narrowbands (NBs).

[00433] In example 201, the machine readable storage media of any of examples 194 through 200, wherein the system bandwidth is at least 5 megahertz (MHz); and wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include at least 4 Narrowbands (NBs).

[00434] In example 202, the machine readable storage media of any of examples 194 through 201, wherein the system bandwidth is at least 15 megahertz (MHz); and wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include at least 6 Narrowbands (NBs).

[00435] In example 203, the machine readable storage media of any of examples 194 through 202, wherein the system bandwidth is at least 20 megahertz (MHz); and wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include at least 8 Narrowbands (NBs).

[00436] In example 204, the machine readable storage media of any of examples 194 through 203, wherein at least one ENB of the first set of ENBs or the second set of ENBs is defined to include a plurality of Narrowbands (NBs) and also spans one or more RBs outside the plurality of NBs. [00437] In example 205, the machine readable storage media of example 204, wherein the one or more RBs outside the plurality of NBs comprises at least one of: an RB at an edge of the system bandwidth, or an RB at a middle of the system bandwidth.

[00438] In example 206, the machine readable storage media of any of examples 194 through 205, wherein the first set of ENBs is defined to include all RBs of the system bandwidth except for one of more of: an RB at an edge of the system bandwidth, or an RB at a middle of the system bandwidth.

[00439] In example 207, the machine readable storage media of any of examples 194 through 206, wherein a number of RBs spanned by the first set of ENBs matches a number of RBs spanned by the second set of ENBs.

[00440] In example 208, the machine readable storage media of example 207, wherein the system bandwidth is even.

[00441] In example 209, the machine readable storage media of any of examples 194 through 208, the operation comprising: generate a transmission carrying one or more resource assignment indicators, the transmission being of: a Downlink Control Information (DCI) format 6-1 A, a DCI format 6-OA, a DCI format 6-1B, or a DCI format 6-OB.

[00442] In example 210, the machine readable storage media of example 209, wherein the ENBs of the first set of ENBs have an increasing index matching an increasing index of the RBs of the first set of ENBs; and wherein the ENBs of the second set of ENBs have an increasing index matching an increasing index of the RBs of the second set of ENBs.

[00443] In example 21 1, the machine readable storage media of example 209, wherein the one or more resource assignment indicators comprises an ENB index indicator having a number of most significant bits of an RB assignment field based on a total number of ENBs in one of: the first set of ENBs, or the second set of ENB.

[00444] In example 212, the machine readable storage media of example 209, wherein the one or more resource assignment indicators comprises a frequency resource indicator having a number of bits of an RB assignment field based on a number of Narrowbands (NBs) in one of: an ENB of the first set of ENBs, or an ENB of the second set of ENBs.

[00445] In example 213, the machine readable storage media of example 212, wherein the frequency resource indicator indicates a number of NBs starting from a reference NB.

[00446] In example 214, the machine readable storage media of example 213, wherein the one or more resource assignment indicators comprises a reference NB indicator indicating the reference RB. [00447] In example 215, the machine readable storage media of example 209, wherein the one or more resource assignment indicators comprises a resource allocation bitmap indicator having at least a number of bits equal to a number of Narrowbands (NBs) in one of: an ENB of the first set of ENBs, or an ENB of the second set of ENBs.

[00448] In example 216, the machine readable storage media of any of examples 209 through 215, wherein the one or more resource assignment indicators comprises a resource allocation indicator having a plurality of values respectively corresponding to a plurality of predetermined resource assignments.

[00449] In example 217, the machine readable storage media of any of examples 209 through 216, wherein the one or more resource assignment indicators comprises at least one of: a central PRB allocation indicator, or an edge PRB allocation indicator.

[00450] In example 218, the machine readable storage media of any of examples 194 through 217, the operation comprising: determine a hopped ENB frequency for an ENB of the first set of ENBs or the second set of ENBs in accordance with an ENB -granularity frequency -hopping offset.

[00451] In example 219, the machine readable storage media of any of examples 194 through 218, the operation comprising: generate a Downlink Control Information (DCI) transmission, wherein the DCI transmission carries a frequency-hopping indicator to disable frequency hopping for allocations for which a frequency -hopping wrap-around could fragment an ENB.

[00452] In example 220, the machine readable storage media of any of examples 194 through 219, the operation comprising: determine a hopped NB frequency for an NB within one of the first set of ENBs or the second set of ENBs in accordance with an NB-granularity frequency -hopping offset; and determine a hopped ENB frequency for one of the first set of ENBs or the second set of ENBs, the hopped ENB encompassing the hopped NB frequency.

[00453] In example 221, the apparatus of any of examples 1 through 27 and 11 1 through 137, wherein the one or more processors comprise a baseband processor.

[00454] In example 222, the apparatus of any of examples 1 through 27 and 11 1 through 137, comprising a memory for storing instructions, the memory being coupled to the one or more processors.

[00455] In example 223, the apparatus of any of examples 1 through 27 and 11 1 through 137, comprising a transceiver circuitry for at least one of: generating transmissions, encoding transmissions, processing transmissions, or decoding transmissions. [00456] In example 224, the apparatus of any of examples 1 through 27 and 11 1 through 137, comprising a transceiver circuitry for generating transmissions and processing transmissions.

[00457] An abstract is provided that will allow the reader to ascertain the nature and gist of the technical disclosure. The abstract is submitted with the understanding that it will not be used to limit the scope or meaning of the claims. The following claims are hereby incorporated into the detailed description, with each claim standing on its own as a separate embodiment.

Claims

We claim:

An apparatus of a Machine-Type Communication (MTC) capable User Equipment (UE) operable to communicate with an MTC-capable Evolved Node-B (eNodeB) on a wireless network spanning a system bandwidth, comprising:

one or more processors to:

define a first set of one or more Extended Narrowbands (ENBs) for Downlink (DL) transmissions spanning a first set of more than six Resource Blocks (RBs) of the system bandwidth; and

define a second set of one or more ENBs for Uplink (UL) transmissions spanning a second set of more than six RBs of the system bandwidth, and a memory to:

store one or more parameters of the first set of ENBs and one or more parameters of the second set of ENBs.

The apparatus of claim 1 ,

wherein at least one of the first set of more than six RBs or the second set of more than six RBs spans more than six contiguous RBs of the system bandwidth.

The apparatus of either of claims 1 or 2,

wherein the system bandwidth comprises a plurality of Narrowbands (NBs); and wherein an ENB of the first set of ENBs is defined to include the plurality of NBs for the DL.

The apparatus of either of claims 1 or 2,

wherein the system bandwidth comprises a plurality of Narrowbands (NBs); and wherein an ENB of the second set of ENBs is defined to include the plurality of NBs for the UL.

The apparatus of claim 4,

wherein the plurality of NBs in the UL are contiguous.

6. The apparatus of either of claims 1 or 2,

wherein the system bandwidth is one of: 3 megahertz (MHz), 5 MHz, 10 MHz, 15 MHz, or 20 MHz.

7. Machine readable storage media having machine executable instructions that, when

executed, cause one or more processors of a Machine-Type Communication (MTC) capable User Equipment (UE) operable to communicate with an MTC-capable Evolved Node-B (eNodeB) on a wireless network spanning a system bandwidth to perform an operation comprising:

define a first set of one or more Extended Narrowbands (ENBs) for Downlink (DL) transmissions spanning a first set of more than six Resource Blocks (RBs) of the system bandwidth;

define a second set of one or more ENBs for Uplink (UL) transmissions spanning a second set of more than six RBs of the system bandwidth; and

8. The machine readable storage media of claim 7,

9. The machine readable storage media of either of claims 7 or 8,

10. The machine readable storage media of either of claims 7 or 8,

1 1. The machine readable storage media of claim 10,

wherein the plurality of NBs in the UL are contiguous.

12. The machine readable storage media of either of claims 7 or 8,

13. An apparatus of a Machine-Type Communication (MTC) capable Evolved Node-B

(eNodeB) operable to communicate with an MTC-capable User Equipment (UE) on a wireless network spanning a system bandwidth, comprising:

one or more processors to:

14. The apparatus of claim 13,

15. The apparatus of either of claims 13 or 14,

16. The apparatus of either of claims 13 or 14,

17. The apparatus of claim 16,

wherein the plurality of NBs in the UL are contiguous.

18. The apparatus of either of claims 13 or 14,

19. Machine readable storage media having machine executable instructions that, when

executed, cause one or more processors of a Machine-Type Communication (MTC) capable Evolved Node-B (eNodeB) operable to communicate with an MTC-capable User Equipment (UE) on a wireless network spanning a system bandwidth to perform an operation comprising:

20. The machine readable storage media of claim 19,

21. The machine readable storage media of either of claims 19 or 20,

22. The machine readable storage media of either of claims 19 or 20,

23. The machine readable storage media of claim 22,

wherein the plurality of NBs in the UL are contiguous.

24. The machine readable storage media of either of claims 19 or 20, wherein the system bandwidth is one of: 3 megahertz (MHz), 5 MHz, 10 MHz, 15 MHz, or 20 MHz.