HK1235965B - Enhanced node b (enb) and method for mtc coexistence - Google Patents

Description

Method and enhanced Node B (eNB) for MTC coexistence

Priority Declaration

This patent application claims the benefit of priority to U.S. Application No. 14/667,430, filed on March 24, 2015, which claims the benefit of priority to U.S. Provisional Patent Application No. 62/031,054, filed on July 30, 2014, both of which are incorporated herein by reference in their entirety.

Technical Field

Embodiments relate to wireless communications. Some embodiments relate to cellular communication networks, including 3GPP (3rd Generation Partnership Project) networks, 3GPP LTE (Long Term Evolution) networks, and 3GPP LTE-A (LTE-Advanced), although the scope of the embodiments is not limited in this respect. Some embodiments relate to machine type communications (MTC).

Background Art

Machine-type communication (MTC) is a promising emerging technology that enables ubiquitous computing environments, encompassing the concept of the Internet of Things (IoT). Potential MTC-based applications include smart metering, health monitoring, remote safety monitoring, intelligent transportation systems, and more. Currently, MTC devices are not designed for integration into current and next-generation mobile broadband networks (e.g., LTE and LTE-Advanced).

BRIEF DESCRIPTION OF THE DRAWINGS

In the accompanying drawings (not necessarily drawn to scale), like reference numerals in different views may describe similar components. Like reference numerals with different letter suffixes may represent different instances of similar elements. The accompanying drawings generally illustrate various embodiments discussed in this document by way of example and not limitation.

FIG1 generally illustrates a portion of an end-to-end network architecture of an LTE network having various network components, according to some embodiments.

FIG2 generally illustrates a functional block diagram of a UE according to some embodiments.

3A and 3B generally illustrate diagrams of frequency and time division locations of machine type communication (MTC) zones in a downlink, in accordance with some embodiments.

4A and 4B generally illustrate diagrams of frequency and time division locations of MTC zones in the uplink, according to some embodiments.

FIG5 generally illustrates signaling in an MTC area in a time division scenario according to some embodiments.

FIG6 generally illustrates a first diagram of an MTC Physical Broadcast Channel (M-PBCH) transmission in accordance with some embodiments.

FIG7 generally illustrates a second diagram of an MTC Physical Broadcast Channel (M-PBCH) transmission in accordance with some embodiments.

FIG8 generally illustrates a third diagram of an MTC Physical Broadcast Channel (M-PBCH) transmission in accordance with some embodiments.

FIG9 generally shows a diagram of MTC system information block (M-SIB) transmission in accordance with some embodiments.

10A and 10B generally show diagrams of MTC areas in the downlink, according to some embodiments.

FIG11 generally shows a diagram of an MTC area in uplink according to some embodiments.

FIG12 generally illustrates a flow chart presenting a method of utilizing an MTC user equipment (UE) on a licensed bandwidth in accordance with some embodiments.

FIG. 13 generally illustrates an exemplary block diagram of a machine on which any one or more of the techniques (eg, methodologies) discussed herein may be performed, according to some embodiments.

DETAILED DESCRIPTION

Today's wireless communications include a large number of devices, controllers, methods and systems. For example, wireless communications on licensed bands can involve user equipment (UE) and evolved node B (eNB) of different types and different settings. In an example, a licensed band wireless communication system can include a wireless network operating as a 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) or upgraded LTE network or other cellular telephone network. In an LTE or upgraded LTE network, the minimum bandwidth is 1.4 MHz. In an example, machine type communication (MTC) can have a transmission bandwidth of 1.4 MHz. In other examples, MTC can have a transmission bandwidth of 200 kHz, 300 kHz, 400 kHz, or other values lower or higher than 1.4 MHz. In an example, 200 kHz is approximately the size of a single physical resource block (PRB) in an LTE or upgraded LTE network. MTC can include device-to-device (also known as machine-to-machine) communication, Internet of Things type communication, and the like.

In one example, the control channel is transmitted over the entire system bandwidth. When the system bandwidth is greater than 1.4 MHz, control channel conflicts may occur between LTE or LTE-Advanced system transmissions and MTC transmissions. In another example, existing mobile broadband networks may not be designed or optimized to meet MTC-related requirements.

In an example, a UE, an eNB, or a network may be configured to support MTC. For example, an MTC area may be established for communication. The MTC area may include establishing or modifying time and frequency resource information, signaling, or conflict handling. MTC support may include MTC channel state information (M-CRS) design, MTC physical broadcast channel M-PBCH design, MTC system information block M-SIB design, MTC control channel design (including MTC physical downlink control channel (M-PDCCH) design), MTC physical control format indicator channel (M-PCFICH) design, or MTC physical hybrid automatic repeat request (ARQ) indicator channel (M-PHICH) design, or MTC uplink design.

1 generally illustrates a portion of an end-to-end network architecture of an LTE network with various network components, according to some embodiments. The network 100 includes a radio access network (RAN) (e.g., as depicted, E-UTRAN or Evolved Universal Terrestrial Radio Access Network) 100 and a core network 120 (e.g., shown as an Evolved Packet Core (EPC)), which are coupled together via an S1 interface 115. For convenience and brevity, only a portion of the core network 120 and the RAN 100 are shown.

The core network 120 includes a mobility management entity (MME) 122, a serving gateway (serving GW) 124, and a packet data network gateway (PDN GW) 126. The RAN includes an enhanced Node B (eNB) 104 (which may operate as a base station) for communicating with user equipment (UE) 102. The eNB 104 may include a macro eNB and a low power (LP) eNB.

The MME is functionally similar to the control plane of the legacy Serving GPRS Support Node (SGSN). The MME manages mobility aspects of access, such as gateway selection and tracking area list management. The Serving GW 124 terminates the interface to the RAN 100 and routes data packets between the RAN 100 and the core network 120. In addition, the Serving GW 124 can be the local mobility anchor point for inter-eNB handovers and can also provide an anchor point for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and some policy enforcement. The Serving GW 124 and the MME 122 can be implemented in one physical node or in different physical nodes. The PDN GW 126 terminates the SGi interface to the packet data network (PDN). The PDN GW 126 routes data packets between the EPC 120 and external PDNs and can be a key node for policy enforcement and charging data collection. The PDN GW 126 can also provide an anchor point for mobility for non-LTE accesses. The external PDN may be any type of IP network as well as an IP Multimedia Subsystem (IMS) domain.The PDN GW 126 and the Serving GW 124 may be implemented in one physical node or in different physical nodes.

The eNB 104 (macro and micro eNBs) terminates the air interface protocol and can be the first point of contact for the UE 102. In some embodiments, the eNB 104 can implement various logical functions of the RAN 100, including but not limited to RNC (radio network controller) functions, such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management. According to an embodiment, the UE 102 can be configured to transmit OFDM communication signals with the eNB 104 over a multi-carrier communication channel in accordance with OFDMA communication technology. OFDM signals can include multiple orthogonal subcarriers.

The S1 interface 115 separates the RAN 100 and the EPC 120. The S1 interface 115 is divided into two parts: S1-U, which carries traffic data between the eNB 104 and the Serving GW 124, and S1-MME, which is the signaling interface between the eNB 104 and the MME 122. The X2 interface is an interface between eNBs 104. The X2 interface consists of two parts: X2-C and X2-U. X2-C is the control plane interface between eNBs 104, while X2-U is the user plane interface between eNBs 104.

For cellular networks, LP cells are typically used to extend coverage to indoor areas where outdoor signals don't reach well, or to increase network capacity in areas with high phone usage (e.g., train stations). As used herein, the term low-power (LP) eNB refers to any suitable, relatively low-power eNB used to implement narrower cells (narrower than macrocells), such as femtocells, picocells, or microcells. Femtocell eNBs are typically provided by mobile network operators to their residential or enterprise users. Femtocells are typically the size of a residential gateway or smaller and are typically connected to a user's broadband line. Once powered on, femtocells connect to the mobile operator's mobile network and provide additional coverage to residential femtocells, typically with a range of 30 to 50 meters. Therefore, an LP eNB can be a femtocell eNB because it is coupled through the PDN GW 126. Similarly, a picocell is a wireless communication system that typically covers a small area, such as within a building (office, shopping mall, train station, etc.) or, more recently, on an airplane. A picocell eNB can typically connect to another eNB (e.g., a macro eNB) via its base station controller (BSC) functionality via an X2 link. Thus, a low-end (LP) eNB can be implemented as a picocell eNB, as it is coupled to the macro eNB via the X2 interface. A picocell eNB or other low-end (LP) eNB can include some or all of the functionality of a macro eNB. In some cases, it can be referred to as an access point base station or enterprise femtocell.

In some embodiments, a downlink resource grid can be used for downlink transmission from the eNB to the UE. The grid can be a time-frequency grid (referred to as a resource grid), which is the physical resource of the downlink in each time slot. This time-frequency representation is a common practice in OFDM systems, which makes radio resource allocation more intuitive. Each column and each row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain can correspond to a time slot of a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid includes multiple resource blocks, which describe the mapping of specific physical channels to resource elements. Each resource block includes a set of resource elements, and in the frequency domain, each resource block represents the minimum amount of resources that can currently be allocated. There are several different physical downlink channels that are transmitted using these resource blocks. Two of these physical downlink channels that are particularly relevant to the present disclosure are the physical downlink shared channel and the physical downlink control channel.

The Physical Downlink Shared Channel (PDSCH) carries user data and higher-layer signaling to UE 102 ( FIG. 1 ). The Physical Downlink Control Channel (PDCCH) carries information related to the PDSCH channel, including resource allocation and transport format. The PDCCH also informs the UE about the transport format, resource allocation, and H-ARQ information for the uplink shared channel. Typically, downlink scheduling (allocation of control and shared channel resource blocks to UEs within a cell) is performed at the eNB based on channel quality information fed back from the UE to the eNB. Downlink resource allocation information is then sent to the UE on the control channel (PDCCH) intended for (allocated to) the UE.

PDCCH uses CCE (control channel elements) to convey control information. Before being mapped to resource elements, PDCCH complex symbols are first grouped into quadruplets, and then the quadruplets are arranged using a sub-block interleaver for rate matching. Each PDCCH is transmitted using one or more of these control channel elements (CCEs), where each CCE corresponds to 9 groups of physical resource elements (called resource element groups (REGs)), each with 4 physical resource elements. 4 QPSK symbols are mapped to each REG. Depending on the size of the DCI and the channel conditions, one or more CCEs can be used to transmit the PDCCH. Four or more different PDCCH formats may be defined in LTE, with different numbers of CCEs (e.g., aggregation levels, L=1, 2, 4, or 8).

FIG2 illustrates a functional block diagram of a UE according to some embodiments. UE 200 may be suitable for use as any one or more of UEs 102 shown in FIG1 . UE 200 may include physical layer circuitry 202 for transmitting signals to and receiving signals from eNB 104 ( FIG1 ) using one or more antennas 201. UE 200 may also include medium access control (MAC) layer circuitry 204 for controlling access to a wireless medium. UE 200 may also include processing circuitry 206 and memory 208 arranged to configure various elements of the UE to perform the operations described herein.

FIG2 generally illustrates a functional block diagram of a UE according to some embodiments. UE 200 may be suitable for use as UE 102 ( FIG1 ). UE 200 may include physical layer circuitry 202 for transmitting signals to and receiving signals from eNB 104 ( FIG1 ) using one or more antennas 201. UE 200 may also include medium access control (MAC) layer circuitry 204 for controlling access to a wireless medium. UE 200 may also include processing circuitry 206 and memory 208 arranged to perform the operations described herein.

According to some embodiments, the MAC circuit 204 may be arranged to contend for a wireless medium to configure frames or packets for transmission over the wireless medium, and the PHY circuit 202 may be arranged to send and receive signals. The PHY circuit 202 may include circuits for modulation/demodulation, upconversion/downconversion, filtering, amplification, and the like. In some embodiments, the processing circuit 206 of the device 200 may include one or more processors. In some embodiments, two or more antennas may be coupled to a physical layer circuit that is arranged to send and receive signals. The physical layer circuit may include one or more radio devices for communicating according to cellular (e.g., LTE) and WLAN (e.g., IEEE 802.11) technologies. The memory 208 may store information for configuring the processing circuit 206 to perform operations for configuring and sending HEW frames and for performing various operations described herein.

In some embodiments, the UE 200 may be part of a portable wireless communication device, such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capabilities, a web tablet, a wireless phone, a smart phone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a wearable device, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), or other device that can receive and/or send information wirelessly. In some embodiments, the UE 200 may include one or more of a keyboard, a display, a non-volatile memory port, multiple antennas, a graphics processor, an application processor, a speaker, and other mobile device components. The display may be an LCD screen including a touch screen.

The one or more antennas 201 used by the UE 200 may include one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas, or other types of antennas suitable for transmitting RF signals. In some embodiments, instead of two or more antennas, a single antenna with multiple apertures may be used. In these embodiments, each aperture may be considered a separate antenna. In some multiple-input multiple-output (MIMO) embodiments, the antennas may be effectively separated to take advantage of the different channel characteristics and spatial diversity that may be generated between each antenna and the antennas of the transmitting station. In some MIMO embodiments, the antennas may be isolated by a distance of one-tenth of a wavelength or more.

Although UE 200 is shown as having several separate functional elements, one or more of these functional elements may be combined and may be implemented by a combination of software-configured elements (e.g., a processing element including a digital signal processor (DSP)) and/or other hardware elements. For example, some elements may include one or more microprocessors, DSPs, application-specific integrated circuits (ASICs), radio frequency integrated circuits (RFICs), and various hardware and logic circuits for performing at least the functions described herein. In some embodiments, a functional element may refer to one or more processes running on one or more processing elements.

Embodiments can be implemented in one or a combination of hardware, firmware and software. Embodiments can also be implemented as instructions stored on a computer-readable storage medium, which can be read and run by at least one processor to perform the operations described herein. A computer-readable storage medium may include any non-transient mechanism for storing information in a machine (e.g., computer) readable form. For example, a computer-readable storage medium may include a read-only memory (ROM), a random access memory (RAM), a magnetic disk storage medium, an optical storage medium, a flash memory device, and other storage devices and media. In these embodiments, one or more processors may be configured with instructions to perform the operations described herein.

In some embodiments, UE 200 may be configured to receive OFDM communication signals over a multi-carrier communication channel in accordance with OFDMA communication technology. OFDM signals may include multiple orthogonal subcarriers. In some broadband multi-carrier embodiments, the eNB may be part of a broadband wireless access (BWA) network communication network, such as a Worldwide Interoperability for Microwave Access (WiMAX) communication network or a Third Generation Partnership Project (3GPP) Universal Terrestrial Radio Access Network (UTRAN) Long Term Evolution (LTE) or Long Term Evolution (LTE) communication network, but the scope of the present invention is not limited in this respect. In these broadband multi-carrier embodiments, UE 200 and the eNB may be configured to communicate in accordance with Orthogonal Frequency Division Multiple Access (OFDMA) technology.

Figures 3A and 3B generally illustrate diagrams (e.g., 300A and 300B) of frequency and time division locations for machine-type communication (MTC) areas (e.g., 304A and 304B) in the downlink, according to some embodiments. Diagrams 300A and 300B include a control region 302 of an LTE or LTE-Advanced network. In an example, diagram 300A includes an MTC area 304A that is time-division multiplexed with the control region 302. As shown in diagram 300A, the control region 302 appears before the MTC area 304A along the subframe axis. In an example, diagram 300A includes frequency division of the MTC area. In an example, the MTC area 304A can be located within a set of contiguous PRBs (e.g., six or seven PRBs) within the system bandwidth. For example, the MTC area can be located within a set of centered PRBs (e.g., six or seven PRBs) at the edge of the system bandwidth, and so on. In another example, an MTC area may include a set of frequency locations and may be described using subcarrier indices in the downlink or uplink system bandwidth. The uplink frequency locations used for the MTC area may not include a physical uplink control channel (PUCCH) area or a physical random access channel (PRACH) area. For example, a PUCCH or PRACH area may be used for LTE or LTE-Advanced communications and may not be necessary for MTC, or may interfere with MTC and may not be used for MTC.

In another example, diagram 300B includes an MTC region 304B with intra-slot hopping, which is applied to further exploit frequency diversity. In diagram 300B, the control region 302 and the MTC region 304B can be time-division multiplexed, and the MTC region 304B can also include intra-slot hopping (e.g., a first set of frequencies or frequency bands are used for time slot 0, and a second set of frequencies or frequency bands are used for time slot 1). In another example, the MTC region can use intra-subframe hopping.

The time division of Figures 3A and 3B may include orthogonal frequency division multiplexing (OFDM) symbols of the MTC area in the downlink. Illustrations 300A and 300B may include a group of subframes within a frame in the downlink or uplink, which are used for the MTC area. In an example, the starting symbol of the MTC area in the downlink can be predefined. In another example, the starting symbol can be configured as a subframe (or all subframes) within a frame after the PDDCH area. For example, the PDCCH area may include a control area 302, and the MTC area may start after the control area 302 ends. In another example, if a group of centralized PRBs (e.g., six or seven PRBs) are allocated for MTC, subframes that are not allocated for PBCH and primary synchronization signal and secondary synchronization signal (PSS/SSS) transmission can be used for the MTC area in both the downlink and uplink. For example, the MTC area may include subframes that are not used for PSS/SSS.

4A and 4B generally illustrate diagrams (e.g., 400A and 400B) of frequency and time division locations of MTC regions (e.g., 404A and 404B) in the uplink according to some embodiments. In FIG. 4A , diagram 400A illustrates an MTC region 404A located within a set of contiguous frequency ranges (e.g., a set of PRBs (e.g., six or seven PRBs)) within the system bandwidth. The MTC region 404A may not include the PUCCH region 402 or the PRACH region 406. In diagram 400A, the example MTC region 404A is shown as a subframe without intra-slot hopping. In diagram 400B of FIG. 4B , the MTC region 404B includes intra-slot hopping to further exploit frequency diversity. The MTC region may also apply intra-subframe hopping. In an example, intra-slot hopping may use PUCCH-type hopping to achieve maximum frequency diversity.

In another example, the time or frequency location of the MTC area can be different for one or both of the uplink and downlink. A fixed hopping pattern can be used. The fixed hopping pattern can be obtained from the physical cell identifier. In another example, a subframe index can be defined. In the above example, inter-cell interference can be randomized.

In an example, transmissions using LTE or LTE-Advanced type communications may be scheduled in an MTC area. In this example, an eNB may decide resource allocations for UEs using LTE or LTE-Advanced type communications and UEs using MTC.

In an example, the configuration of the MTC area can be predefined. In another example, the configuration of the MTC area can be configured by a higher layer. The configuration information can be predetermined. For example, a concentrated set of PRBs (e.g., six or seven PRBs) can be allocated for the MTC area for the downlink or uplink. In the downlink example, the MTC area starts from the 4th symbol within the subframe except subframes #0 and #5. In other examples, the time and frequency resource information of the MTC area can be indicated in the master information block (MIB). Specifically, the field containing the configuration of the MTC area can occupy Y0 bits of the 10 spare bits in the legacy MIB. This can help with backward compatibility.

In an example, the M-PBCH may be allocated in the same resources (e.g., the same subframe, OFDM symbol, or PRB) as the legacy PBCH. Furthermore, existing channel coding, rate matching, modulation, layer mapping, or precoding used for legacy PBCH transmission may be reused for M-PBCH transmission.

FIG5 generally illustrates signaling in an MTC area 500 in the time domain according to some embodiments. Signaling in an MTC area can effectively adapt to various eNB coordination scenarios and, because the number of configurations is limited, signaling overhead can be reduced. A UE for MTC can receive downlink signals or data or transmit uplink signals or data within an MTC opportunity (e.g., 502A or 502N). In an example, a subframe (e.g., 504A or 504N) may not contain data and the subframe (e.g., 504A or 504N) may be empty. An MTC opportunity (e.g., 502A or 502N) can serve to define a potential area for downlink or uplink scheduling.

Time or frequency resource information for the MTC area 500 may be communicated via the PBCH or M-PBCH and may include a frequency position (e.g., in an RB index region) or a time position (e.g., an OFDM symbol index, a slot index, a subframe index, or a radio frame index). In a specific example of signaling time-related information, the configuration may include a period or subframe offset for the MTC area 500. Subframes used for MTC purposes (e.g., 504A or 504N) may be repeated, for example, in consecutive or non-consecutive subframes for frequency division duplex (FDD), time division duplex (TDD), or half-duplex FDD (HD-FDD). In another example, subframes may be defined in consecutive available downlink subframes for TDD or HD-FDD within each MTC opportunity (e.g., 502A or 502N).

For the first subframe of the downlink subframe 512, the MTC opportunity (e.g., 502A or 502N) may satisfy:

Where _nf is the radio frame number and _ns is the time slot number. In an example, the MTC subframe offset 516 from subframe 0 in radio frame 514 can be predetermined (e.g., Δ _MTC = 0) to reduce signaling overhead. In this example, signaling can be defined as:

Table 1

In the above example, the MTC cycle 508 may be selected as a multiple of 40 ms (e.g., a period during which the same MIB content of the legacy PBCH is conveyed). The above example may assume a fixed (e.g., predetermined) N _MTC . In an example, N _MTC may be equal to 5 (e.g., similar to the SS cycle). In another example, N _MTC may be equal to 4 to avoid subframe 0 or subframe 5 in the radio frame 514 (e.g., a subframe used for SS/PBCH/SIB1/paging). In another example, N _MTC may be equal to 10 (e.g., a radio frame length). In yet another example, N _MTC may be equal to 40 (e.g., consistent with a period during which the same MIB content of the legacy PBCH is conveyed). Other N _MTC values may also be used.

In the case of limited candidates, the MTC subframe offset 516 may also be signaled. For example, _ΔMTC may be 0 or 5.

Table 2

In an example, N _MTC may be signaled (if Δ _MTC =0), for example, N _MTC may be 5 or 10.

Table 3

In an example, a bitmap may be defined for subframe indices allocated for the MTC area 500. Specifically, the bitmap may be defined within an MTC opportunity (e.g., 502A or 502N). For example, for N _MTC = 4, a bitmap of "0011" may be used to indicate that subframes #3 and #4 are allocated for the MTC area 500. In another example, a limited set of bitmaps may be configured along with the MTC opportunity (e.g., 502A or 502N) and the period 508 to reduce signaling overhead.

In another example, the time and frequency resource information of the MTC area 500 can be broadcast in the MTC system information block (M-SIB). In this example, the resource information (e.g., time and resource location) or modulation and coding scheme (MCS) transmitted by the M-SIB can be predefined. In another example, the resource information or MCS transmitted by the MTC master information block (M-MIB) can be configured. In the example of using M-MIB transmission, in order to configure the M-SIB, the field containing the information can occupy Y1 bits of the 10 spare bits of the legacy MIB to ensure backward compatibility. After successfully decoding the M-SIB, the MTC UE can determine the time and frequency information of the MTC area.

In another example, for different configurations of uplink and downlink MTC areas, independent or joint configuration signaling can be used. In the example of independent configuration signaling, a signaling mechanism similar to that described above can be used for both downlink and uplink MTC areas. In the example of joint configuration signaling, a portion of the configuration information (e.g., MTC opportunity) can be used for both uplink and downlink MTC areas. For example, as described above, the MTC opportunity can signal a difference bitmap corresponding to the configuration of the MTC uplink subframe to indicate the MTC downlink or uplink subframe, wherein the MTC uplink subframe is different from the MTC downlink subframe. If the difference bitmap is empty, the example may include an option to configure identical subframes for the MTC downlink and uplink.

In an example, transmissions may cause interference or collisions in an MTC area. When transmitting a downlink physical channel in an MTC area, the resource element (RE) mapping for the physical channel transmission may be rate-matched around the CRS or demodulation reference signal (DM-RS). The CRS or DM-RS may depend on the transmission mode. In another example, the MTC area may include collisions between PSS/SSS transmissions and physical channel transmissions. In this example, the RE mapping for the physical channel transmission may be rate-matched around the PSS/SSS transmission.

The MTC area may conflict with the channel state information (CSI) reference signal (CSI-RS). In an example, the resource element (RE) mapping for downlink physical channel transmission in the MTC area may be rate matched around the REs used in the CSI-RS configuration or punctured around the REs used in the CSI-RS configuration. In another example, rate matching or puncturing around the REs used in the CSI-RS configuration may be performed according to the mapping rules described above for the example of the MTC area conflicting with the PSS/SSS transmission. In yet another example, the eNB may avoid conflicts between the CSI-RS transmission and the transmission in the MTC area. The eNB may be configured to avoid conflicts, and the UE may assume that the CSI-RS is not transmitted in the MTC area.

In LTE or upgraded LTE, CRS can be generated based on a pseudo-random sequence. The pseudo-random sequence seed for generating the pseudo-random sequence can be defined as a function of the physical cell identifier, the indication of the cyclic prefix, the symbol index, or the subframe index. In the example, the existing CRS can be reused in the MTC area. For example, frequency domain information (e.g., the PRB index in the MTC area) can be known at the UE. The pseudo-random sequence can be determined by using the information and the system bandwidth, and the pseudo-random sequence can be sent in the MTC area. The UE can learn the system bandwidth from the MIB transmission.

In another example, if the frequency location of the MTC area within the LTE or upgraded LTE system is unknown at the UE device, the UE device may not be able to determine the pseudo-random sequence and may not be able to perform channel estimation. A new MTC CRS (M-CRS) may be defined and specified for UEs performing MTC. Subframes may be allocated for MTC areas. CRS (non-M-CRS) may only be sent in resources that are not allocated to MTC areas. For example, an MTC area may be allocated in a Multimedia Broadcast Single Frequency Network (MBSFN) subframe because CRS may not be sent in the subframe. In this example, the M-CRS pattern may reuse existing CRS transmissions or use a CRS pattern with a different MTC random seed.

The pseudo-random sequence seed may be defined as a function of the indication of the MTC region. For example:

c _init = f(I _MTC )

Where I _MTC is an indication of the MTC area, and for M-CRS transmission, I _MTC = 1. Specific examples where c is a constant may include:

In another example, the resource mapping mode of CRS may be applicable to M-CRS transmission.

In an example, the M-MIB may be carried in a PBCH transmission or an MTC PBCH (M-PBCH) transmission. Several options for including the M-MIB in an MTC PBCH transmission are described below with respect to Figures 4-6.

6 generally illustrates a first diagram 600 of an MTC Physical Broadcast Channel (M-PBCH) transmission 608 in accordance with some embodiments. Diagram 600 includes a legacy (eg, LTE or LTE-Advanced) PBCH transmission subframe 602 and an M-PBCH transmission subframe 604.

In Figure 6, M-PBCH transmission 608 may be transmitted intermittently. M-PBCH transmission subframe 604 may be multiplexed with legacy PBCH transmission subframe 602 in a time-division multiplexed manner. For example, M-PBCH transmission subframe 604 may be used in a narrowband MTC system that coexists with legacy systems. In an example, the period 614 of M-PBCH transmission 608 may be N x 40 ms. Within period 614, M-PBCH transmission 608 may be transmitted M times and have a duration 612 of M x 40 ms. A time slot 606 in either M-PBCH transmission subframe 604 or legacy PBCH transmission subframe 602 may have a duration 610 of 10 ms.

In an example, the M-PBCH transmission 608 can be sent in a legacy PBCH location. In another example, N can be greater than M, which can reduce the impact on legacy LTE systems. In other examples, the eNB can consider and configure various cycle levels (N) and durations (M) of the M-PBCH transmission subframe 604. In an example, the eNB can dynamically adjust the M and N values based on the MTC traffic. The eNB can find a balance between the impact on legacy UEs and the access delay of MTC devices.

FIG7 generally illustrates a second diagram 700 of an MTC physical broadcast channel (M-PBCH) transmission 716 in accordance with some embodiments. In FIG7 , the M-PBCH transmission 716 may be transmitted intermittently and located in addition to the legacy PBCH transmission location 708. FIG7 illustrates the M-PBCH transmission 716 in the context of a narrowband MTC system coexisting with an LTE system. Similar to the period 614 described above with respect to FIG6 , the period 714 and duration 712 of the M-PBCH transmission subframe 704 may be N x 40 ms and M x 40 ms, respectively. In an example, the legacy PBCH transmission 608 may be transmitted during the duration 712 of the M-PBCH transmission subframe 704 to minimize the impact on the legacy system. In another example, the M and N values may be dynamically adjusted by the eNB and may depend on the MTC traffic volume.

In an example, the M-PBCH transmission 716 may be sent in a subframe other than subframe #0. For example, the M-PBCH transmission 716 may be sent in subframe #5. To simplify specification work and implementation costs, the M-PBCH transmission 716 may be allocated in the same resources (e.g., the same OFDM symbol or PRB) as the legacy PBCH transmission 708. In another example, the existing channel coding, rate matching, modulation, layer mapping, or precoding of the legacy PBCH transmission 708 may be reused for the M-PBCH transmission 716.

In another example, the M-PBCH transmission 716 can be sent in subframe #0, similar to the legacy PBCH transmission 708, and the M-PBCH transmission 716 can be allocated in different OFDM symbols. In this example, the existing channel coding, modulation and layer mapping, or precoding can be reused for the M-PBCH transmission 716. After tail-biting convolutional coding, a rate matching operation can be performed to fill the available resource elements, excluding the control region, CRS, PSS/SSS, or PBCH symbols (e.g., excluding resource elements defined separately for the MTC region). In yet another example, a first frequency mapping can be applied to the M-PBCH transmission 716 to align with the legacy PBCH transmission 708. In this example, the starting symbol of the M-PBCH transmission 716 can be predetermined. For example, the M-PBCH transmission 716 can be transmitted starting from OFDM symbol #4.

FIG8 generally illustrates a third diagram 800 of an MTC physical broadcast channel (M-PBCH) transmission 816 in accordance with some embodiments. In an example, the M-PBCH transmission 816 can be transmitted along with the legacy PBCH transmission 808 in all subframes (e.g., subframe 804). For example, the M-PBCH transmission 816 can be transmitted in a different location than the legacy PBCH transmission 808. M-PBCH transmissions 816 by an MTC system with a narrowband deployment can coexist with the legacy system. For example, the M-PBCH transmission 816 scheme described above with respect to FIG7 can be applied to the configuration used in FIG8. Diagram 800 can reduce access latency for MTC devices at the expense of overall system-level spectral efficiency.

In an example, for Figures 7 and 8, M-PBCH transmissions (e.g., 716 and 816) may be sent in a different subframe than legacy PBCH transmissions (e.g., 708 and 808), and several options may be considered for resource allocation of the remaining symbols. In an example, the remaining symbols within the PRB may not be used. In another example, the remaining symbols within the PRB may be used to transmit legacy physical downlink shared channel (PDSCH) transmissions. If the legacy PDSCH is active, the example may include puncturing the four corresponding symbols carrying the M-PBCH transmission. In yet another example, the remaining symbols within the PRB may be used to transmit MTC-specific channels (e.g., M-PDSCH).

Figure 9 generally illustrates an illustration 900 of an MTC system information block (M-SIB) transmission 902, according to some embodiments. In legacy systems such as LTE or LTE-Advanced, a system information block (SIB) may be transmitted on the PDSCH. The PDSCH may be indicated by a corresponding PDCCH that includes a system information radio network temporary identifier (SI-RNTI). The PDCCH may indicate the transport format or PRB resources used for system information transmission. In an example, a UE used for MTC may have narrowband limitations, and scheduling SIBs in the MTC area may be difficult as in legacy systems, but may be a viable option in environments where ease of use is desired. M-SIBs may be used to convey information similar to that of SIBs, without using the same format and transmission system as SIBs. In another example, M-SIBs may include information from existing SIBs with additional MTC information. Information from existing SIBs may be used to ensure that UEs can access the network while using MTC.

In an example, the time domain configuration of the M-SIB transmission 902 may be predefined. In another example, the M-SIB transmission 902 may be configured by a higher layer. The time domain configuration information may include a subframe index and a period 908 of the M-SIB transmission 902.

In the example of the predefined M-SIB transmission 902 above, the M-SIB transmission 902 can be sent in subframe #n of the frame 906 within the MTC area 902. The M-SIB transmission 902 can have a period 908 of Xx10ms. In another example, multiple M-SIB blocks (e.g., B>1) can be sent within the MTC area 904 with a period 908 of Xx10ms. The M-SIB can use autonomous hybrid automatic repeat request (ARQ). Retransmission of the first M-SIB transmission 902 can be used to improve decoding performance (e.g., similar to the existing SIB-1 transmission of the legacy system). In this case, a predefined redundancy version (RV) pattern between multiple M-SIB blocks within Xx10ms can be specified for the M-SIB transmission 902. For example, if B=4, the RV pattern of the M-SIB transmission 902 can be predefined as 0, 2, 3, 1. The RV can include an increased redundancy gain for the M-SIB transmission 902. For example, in the first M-SIB transmission, the RV may be set to 0, in the second M-SIB transmission, the RV may be set to 2, and so on.

In another example, the time domain configuration may be configured by a higher layer and may be broadcasted in the M-MIB. To facilitate backward compatibility, the field containing the time domain configuration may occupy Y2 bits of the 10 spare bits of the legacy MIB.

In an example, frequency domain information of the M-SIB transmission 902 may be predefined or indicated in an EPDCCH or MTC PDCCH (M-PDCCH) with a common search space (CSS). For example, the frequency domain information of the M-SIB transmission 902 may be predefined using available resources in a subframe within an MTC region 904 (e.g., 6 or 7 PRBs of a 1.4 MHz bandwidth) allocated to the M-SIB transmission 902. This can significantly reduce signaling overhead, particularly when considering narrowband deployment of MTC devices.

Figures 10A and 10B generally illustrate diagrams of MTC areas in the downlink (e.g., 1000A and 1000B) according to some embodiments. Legacy PDCCH, PHICH, and PCFICH can be transmitted over the entire system bandwidth. For MTC devices with narrow bandwidth, it may be difficult to correctly receive and decode downlink control channels because the MTC area is a subset of the frequencies of the entire system bandwidth. To address this issue, a new MTC downlink control channel can be added. Figure 10A shows the MTC downlink control channel design in the MTC area. In the example, the MTC downlink control channel or MTC control area 1004A can span the first K OFDM symbols of the MTC area, while the MTC data channel 1006A can occupy the remaining OFDM symbols in the MTC area. In other words, the MTC control area 1004A can be time-division multiplexed with the MTC data channel 1006A. The MTC control area 1004A and the MTC data channel 1006A can be time-division multiplexed with the legacy control area 1002. In diagram 1000B, the MTC control region 1004B and the MTC data channel 1006B may be multiplexed in the frequency domain of the MTC region. The MTC control region 1004B and the MTC data channel 1006B may also be time-division multiplexed with the legacy control region 1002.

In an example, similar to legacy LTE or LTE-Advanced networks, M-PCFICH can be considered in the control channel. In a simplified example, the existing PCFICH design in LTE or LTE-Advanced networks can be used for M-PCFICH design (e.g., channel coding, modulation scheme, layer mapping and precoder, or resource mapping). Specifically, 16 M-PCFICH symbols can be divided into 4 symbol quadruplets, and each symbol quadruplet can be allocated to a resource element group.

In another example, the number of OFDM symbols allocated for M-PDCCH or the starting symbol of M-PDSCH transmission may be predefined. In yet another example, the number or starting symbol may be configured by a higher layer. In a second example, the control channel design may not require M-PCFICH. In an example, sending an M-PCFICH transmission may include determining that the number of OFDM symbols allocated for MTC Physical Downlink Control Channel (M-PDCCH) and the starting symbol of MTC Physical Downlink Shared Channel (M-PDSCH) transmission are not predefined.

In an example, M-PHICH may be supported to carry hybrid ARQ ACK/NACK (ACK/NACK), where the hybrid ARQ ACK/NACK may indicate whether the eNB has correctly received a transmission on the PUSCH. The M-PHICH configuration may include the duration of the M-PHICH transmission. In another example, multiple M-PHICH groups may be predefined. In yet another example, multiple M-PHICH groups may be configured by higher layers. For example, the configuration information may be broadcast in the M-SIB. The M-PHICH configuration may follow the existing PHICH configuration in legacy LTE or LTE-Advanced networks. In an example using a legacy network, the 3-bit PHICH configuration in the MIB may be reused for the M-PHICH to save overhead. In another example, the M-PHICH configuration may be indicated in 10 spare bits in the MIB, and separate configurations for the PHICH in the legacy LTE or LTE-Advanced system and the M-PHICH in the MTC system may be signaled.

In another example, the existing PHICH design in the legacy LTE or LTE-Advanced specifications can be reused for the M-PHICH design (e.g., channel coding, modulation scheme, layer mapping and precoder, or resource mapping). In this example, the 12 symbols of an M-PHICH group can be grouped into three symbol quadruplets, and each symbol quadruplet can be allocated to a resource element group. In another example, the MTC control channel design may not include (e.g., not require) the M-PHICH. If the M-PHICH functionality can be replaced by the M-PDCCH, the M-PHICH may not be included.

In the example of MTC control region design, the existing PDCCH design can be reused for M-PDCCH design. The M-PDCCH design may include legacy downlink control information (DCI) format, channel coding, modulation, layer mapping and precoding, resource mapping, etc. In another example, the existing hash tables for common search space (CSS) and UE-specific search space (USS) can be reused for M-PDCCH design. In yet another example of MTC control region design, the existing EPDCCH can be reused for M-PDCCH design.

In the example of MTC control region design, MTC resource element groups (M-REGs) can be defined similar to existing REGs in the current LTE or LTE-Advanced specifications. The MTC control region may conflict with PSS/SSS or CSI-RS transmissions. In the M-REG design, updated resource mapping rules can be considered to handle conflicts. For example, if the MTC control region conflicts with PSS/SSS, M-REGs can be defined for resource elements that are not allocated for PSS/SSS transmission. If the MTC control region conflicts with CSI-RS transmission, M-REGs may not be defined for resource elements used for CSI-RS configuration.

FIG11 generally illustrates an MTC area in the uplink 1100, according to some embodiments. In an example, MTC PRACH (M-PRACH) 1106, MTC PUSCH (M-PUSCH) 1110, or MTC PUCCH (M-PUCCH) 1108 resource allocation may follow existing LTE or LTE-Advanced type designs, e.g., 1.4 MHz bandwidth. In an example, to minimize regulatory impact and implementation cost, physical layer processing for M-PRACH 1106, M-PUCCH 1108, or M-PUSCH 1110 may follow existing designs for legacy PRACH 1104, legacy PUCCH 1102, or legacy PUSCH (not shown) in LTE or LTE-Advanced systems.

FIG12 generally illustrates a flow chart presenting a method 1200 for utilizing a machine type communication (MTC) user equipment (UE) on a licensed frequency band, in accordance with some embodiments. In an example, the method 1200 may include a method 1200 for execution by circuitry of an evolved Node B (eNB) to configure a user equipment (UE) for communication. The method 1200 may include an operation 1202 of broadcasting a physical downlink control channel (PDCCH) transmission from the eNB on the licensed frequency band. The method 1200 may include an operation 1204 of transmitting, from the eNB to the UE, a machine type communication (MTC) physical broadcast channel (PBCH) transmission multiplexed with a PBCH transmission (M-PBCH), the M-PBCH transmission including an MTC master information block (M-MIB) in an MTC region of the licensed frequency band, wherein the MTC region includes a subset of frequencies of the licensed frequency band. The method 1200 may include an operation 1206 of transmitting, from the eNB to the UE, a first data transmission on a downlink in the MTC region.

Figure 13 generally illustrates an example of a block diagram of a machine 1300, according to some embodiments, on which any one or more of the techniques (e.g., methods) discussed herein may be performed. In alternative embodiments, the machine 1300 may operate as a standalone device or may be connected (e.g., networked) to other machines for operation. In a networked deployment, the machine 1300 may operate as a server machine, a client machine, or both in a server-client network environment. In an example, the machine 1300 may operate as a peer machine in a peer-to-peer (P2P) (or other distributed) network environment. The machine 1300 may be a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a mobile phone, a web appliance, a network router, a switch or a bridge, or any machine capable of executing (sequentially or otherwise) instructions specifying an action to be taken by the machine. Further, while a single machine is illustrated, the term "machine" shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, e.g., cloud computing, Software as a Service (SaaS), or other computer cluster configurations.

The examples described herein may include logic, or multiple components, modules, or mechanisms, or may operate on logic, or multiple components, modules, or mechanisms. A module is a tangible entity (e.g., hardware) that is capable of performing a specified operation when in operation. A module includes hardware. In an example, the hardware may be configured to perform a specific operation (e.g., hard-wired) in a specified manner. In an example, the hardware may include a configurable execution unit (e.g., a transistor, a circuit, etc.) and a computer-readable medium containing instructions, wherein the instructions configure the execution unit to perform a specific operation at runtime. Configuration may occur under the guidance of the execution unit or a loading mechanism. Accordingly, when the device operates, the execution unit is communicatively coupled to the computer-readable medium. In this example, the execution unit may be a member of more than one module. For example, in operation, the execution unit may be configured by a first set of instructions to implement a first module at a point in time, and may be reconfigured by a second set of instructions to implement a second module at a second point in time.

The machine (e.g., a computer system) 1300 may include a hardware processor 1302 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 1304, and a static memory 1306, some or all of which may communicate with each other via an interconnection link (e.g., a bus) 1308. The machine 1300 may also include a display unit 1310, an alphanumeric input device 1312 (e.g., a keyboard), and a user interface (UI) navigation device 1314 (e.g., a mouse). In an example, the display unit 1310, the alphanumeric input device 1312, and the UI navigation device 1314 may be a touch screen display. The machine 1300 may also include a storage device (i.e., a drive unit) 1316, a signal generating device 1318 (e.g., a speaker), a network interface device 1320, and one or more sensors 1321 (e.g., a global positioning system (GPS) sensor, a compass, an accelerometer, or other sensors). The machine 1300 may include an output controller 1328 (e.g., a serial (e.g., universal serial bus (USB)), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC)), etc.) connection) to control or communicate with one or more peripheral devices (e.g., a printer, a card reader, etc.).

The storage device 1316 may include a machine-readable medium 1322 on which is stored one or more sets of data structures or instructions 1324 (e.g., software) that implement (or are utilized by) any one or more of the techniques or functionality described herein. The instructions 1324 may also reside, completely or at least partially, within the main memory 1304, within the static memory 1306, or within the hardware processor 1302 during execution by the machine 1300. In an example, one or any combination of the hardware processor 1302, the main memory 1304, the static memory 1306, or the storage device 1316 may constitute a machine-readable medium.

Although the machine-readable medium 1322 is shown as a single medium, the term "machine-readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store one or more instructions 1324.

The term "machine-readable medium" may include any medium capable of storing, encoding, or carrying instructions 1324 for execution by the machine 1300, and wherein the instructions cause the machine 1300 to perform any one or more of the techniques disclosed herein; or storing, encoding, or carrying data structures used by or associated with such instructions 1324. Non-limiting examples of machine-readable media may include solid-state memory, as well as optical and magnetic media. In an example, a bulk machine-readable medium includes a machine-readable medium having a plurality of particles having a constant (e.g., stationary) mass. Thus, a bulk machine-readable medium is not a transient propagating signal. Specific examples of bulk machine-readable media may include non-volatile memory such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM)) and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.

Instructions 1324 may also be sent or received over a communication network 1326 using a transmission medium via the network interface device 1320 using any of a number of transmission protocols (e.g., frame relay, Internet Protocol (IP), Transmission Control Protocol (TCP), User Datagram Protocol (UDP), Hypertext Transfer Protocol (HTTP), etc.). Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), a mobile phone network (e.g., a cellular network), a plain old telephone (POTS) network, a wireless data network (e.g., the Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards (referred to as IEEE), the IEEE 802.16 family of standards (referred to as IEEE), the IEEE 802.15.4 family of standards, and a peer-to-peer (P2P) network, among others. In an example, the network interface device 1320 may include one or more physical jacks (e.g., Ethernet, coaxial, or telephone jacks) or one or more antennas to connect to the communication network 1326. In an example, the network interface device 1320 may include multiple antennas to enable wireless communication using at least one of single-input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) technology. The term "transmission medium" shall be taken to include any intangible medium that can store, encode, or carry instructions for execution by the machine 1300, and includes digital or analog communication signals or other intangible media to facilitate communication of such software.

Various notes and examples

Each of the following non-limiting examples may stand alone or may be combined in various permutations or combinations with one or more of the other examples.

Example 1 includes subject matter embodied by an evolved Node B (eNB) configured to communicate with a user equipment (UE) on a licensed frequency band, the eNB comprising circuitry configured to: send a physical downlink control channel (PDCCH) transmission on the licensed frequency band; send a machine type communication (MTC) system information block (M-SIB) to the UE, the M-SIB comprising configuration information for configuring an MTC area of the licensed frequency band, wherein the MTC area comprises a subset of frequencies of the licensed frequency band; and send a first data transmission to the UE on the MTC area in a downlink; and receive a second data transmission from the UE on the MTC area in an uplink.

In Example 2, the subject matter of Example 1 can optionally include, wherein to transmit the first data transmission, the circuit is configured to transmit the first data transmission multiplexed with a third data transmission.

In Example 3, the subject matter of one or any combination of Examples 1-2 can optionally include, wherein the first data transmission and the third data transmission are multiplexed in a time division manner.

In Example 4, the subject matter of one or any combination of Examples 1-3 can optionally include, wherein the first data transmission and the third data transmission are multiplexed in a frequency division manner.

In Example 5, the subject matter of one or any combination of Examples 1-4 can optionally include, wherein to receive the second data transmission, the circuit is configured to receive the second data transmission multiplexed with a fourth data transmission.

In Example 6, the subject matter of one or any combination of Examples 1-5 may optionally include, wherein to send the first transmission, the circuitry is configured to send the first data transmission using intra-slot hopping.

In Example 7, the subject matter of one or any combination of Examples 1-6 may optionally include, wherein to receive the second data transmission, the circuit is configured to receive the second data transmission multiplexed in a frequency division manner with a transmission on a physical uplink control channel (PUCCH) or a physical random access channel (PRACH).

In Example 8, the subject matter of one or any combination of Examples 1-7 can optionally include, wherein to receive the second data transmission, the circuit is further configured to receive the second data transmission in an intra-slot frequency hopping transmission.

In Example 9, the subject matter of one or any combination of Examples 1-8 may optionally include, wherein the intra-slot frequency hopping transmission comprises a fixed hopping pattern.

In Example 10, the subject matter of one or any combination of Examples 1-9 may optionally include, wherein the fixed hopping pattern includes information about a physical cell identity.

In Example 11, the subject matter of one or any combination of Examples 1-10 may optionally include, wherein the fixed skip pattern includes information about a subframe index.

In Example 12, the subject matter of one or any combination of Examples 1-11 may optionally include, wherein the MTC area is predefined.

In Example 13, the subject matter of one or any combination of Examples 1-12 may optionally include, wherein the M-SIB includes time and frequency resource information of an MTC area for the UE.

In Example 14, the subject matter of one or any combination of Examples 1-13 can optionally include, wherein the circuitry is further configured to send independent signaling configurations for the uplink MTC area and the downlink MTC area to the UE.

In Example 15, the subject matter of one or any combination of Examples 1-14 may optionally include, wherein the circuitry is further configured to send a joint signaling configuration for the uplink MTC area and the downlink MTC area to the UE.

In Example 16, the subject matter of one or any combination of Examples 1-15 can optionally include, wherein the circuit is further configured to transmit a primary synchronization signal and a secondary synchronization signal (PSS/SSS) to the UE.

In Example 17, the subject matter of one or any combination of Examples 1-16 may optionally include, wherein the circuitry is further configured to rate match the resource element mapping to around the PSS/SSS within the MTC area.

In Example 18, the subject matter of one or any combination of Examples 1-17 can optionally include, wherein the circuit is further configured to transmit a channel state information reference signal (CSI-RS) to the UE.

In Example 19, the subject matter of one or any combination of Examples 1-18 may optionally include, wherein the circuitry is further configured to rate match the resource element mapping around the CSI-RS within the MTC area.

In Example 20, the subject matter of one or any combination of Examples 1-19 may optionally include, wherein the circuit is further configured to avoid collisions between the CSI-RS and transmissions in the MTC area.

In Example 21, the subject matter of one or any combination of Examples 1-20 may optionally include, wherein the circuit is further configured to send a cell-specific reference signal to the UE.

In Example 22, the subject matter of one or any combination of Examples 1-21 may optionally include, wherein the cell-specific reference signal is transmitted in a multimedia broadcast single frequency network subframe within the MTC area.

In Example 23, the subject matter of one or any combination of Examples 1-22 may optionally include, wherein the cell-specific reference signal comprises a resource mapping pattern using an MTC random seed.

In Example 24, the subject matter of one or any combination of Examples 1-23 can optionally include, wherein the circuitry is further configured to send an MTC Master Information Block (M-MIB) to the UE.

In Example 25, the subject matter of one or any combination of Examples 1-24 can optionally include, wherein to transmit the M-MIB, the circuitry is further configured to transmit the M-MIB in a subframe in a frame within the MTC area.

In Example 26, the subject matter of one or any combination of Examples 1-25 may optionally include, wherein the M-MIB includes time and frequency resource information of the UE.

In Example 27, the subject matter of one or any combination of Examples 1-26 may optionally include, wherein to transmit the M-MIB, the circuitry is further configured to transmit the M-MIB using an MTC physical broadcast channel (M-PBCH).

In Example 28, the subject matter of one or any combination of Examples 1-27 may optionally include, wherein the circuit is further configured to send an MTC Physical Broadcast Channel (M-PBCH) transmission in the subframe.

In Example 29, the subject matter of one or any combination of Examples 1-28 may optionally include, wherein the subframe comprises a subframe not used for a primary synchronization signal and a secondary synchronization signal (PSS/SSS).

In Example 30, the subject matter of one or any combination of Examples 1-29 may optionally include, wherein the circuit is further configured to transmit a second subframe to the UE, the second subframe including a physical broadcast channel (PBCH) transmission different from the M-PBCH transmission.

In Example 31, the subject matter of one or any combination of Examples 1-30 may optionally include, wherein the PBCH transmission and the M-PBCH transmission are time division multiplexed between the subframe and the second subframe, and wherein the PBCH transmission and the M-PBCH transmission are allocated in the same resources.

In Example 32, the subject matter of one or any combination of Examples 1-31 may optionally include, wherein the circuit is further configured to send a physical broadcast channel (PBCH) transmission different from the M-PBCH transmission in the subframe.

In Example 33, the subject matter of one or any combination of Examples 1-32 may optionally include, wherein the PBCH transmission and the M-PBCH transmission are time division multiplexed within the subframe.

In Example 34, the subject matter of one or any combination of Examples 1-33 may optionally include, wherein the circuitry is further configured to send an MTC Physical Control Format Indicator Channel (PCFICH) transmission to the UE.

In Example 35, the subject matter of one or any combination of Examples 1-34 may optionally include, wherein to send the MTC PCFICH transmission, the circuit is further configured to determine the number of orthogonal frequency division multiplexing (OFDM) symbols allocated for the MTC physical downlink control channel (M-PDCCH) and the starting symbol of the MTC physical downlink shared channel (M-PDSCH) transmission is not predefined.

In Example 36, the subject matter of one or any combination of Examples 1-35 can optionally include, wherein the circuitry is further configured to send a Physical Hybrid Automatic Repeat Request (ARQ) Indicator Channel (M-PHICH) transmission to the UE.

In Example 37, the subject matter of one or any combination of Examples 1-36 may optionally include, wherein to transmit the M-PHICH, the circuitry is further configured to transmit configuration information to the UE in a system information block (SIB) or a master information block (MIB).

In Example 38, the subject matter of one or any combination of Examples 1-37 may optionally include, wherein to transmit the M-PHICH, the circuitry is further configured to determine that an MTC physical downlink control channel (M-PDCCH) does not replace the M-PHICH functionality.

In Example 39, the subject matter of one or any combination of Examples 1-38 may optionally include, wherein the circuit is further configured to send an MTC physical downlink control channel (M-PDCCH) transmission to the UE in the MTC area.

In Example 40, the subject matter of one or any combination of Examples 1-39 may optionally include, wherein the M-PDCCH comprises an existing enhanced physical downlink control channel (EPDCCH).

In Example 41, the subject matter of one or any combination of Examples 1-40 may optionally include, wherein the circuit is further configured to receive an MTC physical random access channel (M-PRACH) transmission from the UE.

In Example 42, the subject matter of one or any combination of Examples 1-41 may optionally include, wherein the M-PRACH transmission is time division multiplexed with the MTC physical uplink control channel (M-PUCCH) transmission and the MTC physical uplink shared channel (M-PUSCH) transmission in the MTC area.

In Example 43, the subject matter of one or any combination of Examples 1-42 may optionally include, wherein the M-PUCCH transmission and the M-PUSCH transmission are frequency division multiplexed in the MTC area.

Example 44 includes subject matter embodied by an evolved Node B (eNB) configured to communicate with a user equipment (UE) on a licensed band, the eNB comprising circuitry configured to: send a physical downlink control channel (PDCCH) transmission on the licensed band; send a machine type communication (MTC) master information block (M-MIB) to the UE, the M-MIB comprising configuration information for configuring an MTC area of the licensed band, wherein the MTC area comprises a subset of frequencies of the licensed band; and send a first data transmission to the UE on the MTC area in a downlink; and receive a second data transmission from the UE on the MTC area in an uplink.

In Example 45, the subject matter of Example 44 may optionally include, wherein the circuitry is further configured to send an MTC system information block (M-SIB) to the UE.

In Example 46, the subject matter of one or any combination of Examples 44-45 may optionally include, wherein to transmit the M-SIB, the circuit is further configured to transmit the M-SIB in a subframe in a frame within the MTC area.

In Example 47, the subject matter of one or any combination of Examples 44-46 may optionally include, wherein the M-SIB includes time and frequency resource information for the UE.

Example 48 includes a subject matter embodied by a user equipment (UE) configured to operate on a machine type communication (MTC) MTC area of a wireless spectrum, comprising: a transceiver configured to: receive a physical downlink control channel (PDCCH) transmission from an evolved Node B (eNB) on a licensed band; receive an MTC system information block (M-SIB) from the eNB, the M-SIB including configuration information for configuring the MTC area; and receive a first data transmission on the MTC area in a downlink, wherein the MTC area includes a subset of frequencies of the licensed band; and send a second data transmission on the MTC area in an uplink.

In Example 49, the subject matter of Example 48 can optionally include, wherein to receive the first data transmission, the transceiver is configured to receive the first data transmission multiplexed with a third data transmission.

In Example 50, the subject matter of one or any combination of Examples 48-49 may optionally include, wherein the first data transmission and the third data transmission are multiplexed in a time division manner.

In Example 51, the subject matter of one or any combination of Examples 48-50 may optionally include, wherein the first data transmission and the third data transmission are multiplexed in a frequency division manner.

In Example 52, the subject matter of one or any combination of Examples 48-51 can optionally include, wherein to transmit the second data transmission, the transceiver is configured to transmit the second data transmission multiplexed with a fourth data transmission.

In Example 53, the subject matter of one or any combination of Examples 48-52 may optionally include, wherein to receive the first data transmission, the transceiver is configured to receive the first data transmission using intra-slot hopping.

In Example 54, the subject matter of one or any combination of Examples 48-53 optionally includes, wherein to send the second data transmission, the transceiver is configured to send the second data transmission multiplexed in a frequency division manner with a transmission on a physical uplink control channel (PUCCH) or a physical random access channel (PRACH).

In Example 55, the subject matter of one or any combination of Examples 48-54 can optionally include, wherein to transmit the second data transmission, the transceiver is further configured to transmit the second data transmission in an intra-slot frequency hopping transmission.

In Example 56, the subject matter of one or any combination of Examples 48-55 may optionally include, wherein the intra-slot frequency hopping transmission comprises a fixed hopping pattern.

In Example 57, the subject matter of one or any combination of Examples 48-56 may optionally include, wherein the fixed hopping pattern includes information about a physical cell identity.

In Example 58, the subject matter of one or any combination of Examples 48-57 may optionally include, wherein the fixed skip pattern includes information about a subframe index.

In Example 59, the subject matter of one or any combination of Examples 48-58 may optionally include, wherein the MTC area is predefined.

In Example 60, the subject matter of one or any combination of Examples 48-59 may optionally include, wherein the SIB includes time and frequency resource information of the MTC area for the UE.

In Example 61, the subject matter of one or any combination of Examples 48-60 may optionally include, wherein the transceiver is further configured to receive independent signaling configurations for the uplink MTC area and the downlink MTC area from the eNB.

In Example 62, the subject matter of one or any combination of Examples 48-61 may optionally include, wherein the transceiver is further configured to receive a joint signaling configuration for the uplink MTC area and the downlink MTC area from the eNB.

In Example 63, the subject matter of one or any combination of Examples 48-62 may optionally include, wherein the transceiver is further configured to receive a primary synchronization signal and a secondary synchronization signal (PSS/SSS) from the eNB.

In Example 64, the subject matter of one or any combination of Examples 48-63 may optionally include, wherein the transceiver is further configured to rate match the resource element mapping to around the PSS/SSS within the MTC area.

In Example 65, the subject matter of one or any combination of Examples 48-64 may optionally include, wherein the transceiver is further configured to receive a channel state information reference signal (CSI-RS) from the eNB.

In Example 66, the subject matter of one or any combination of Examples 48-65 may optionally include, wherein the transceiver is further configured to rate match the resource element mapping around the CSI-RS of the MTC area.

In Example 67, the subject matter of one or any combination of Examples 48-66 may optionally include, wherein the transceiver is further configured to avoid collisions between the CSI-RS and transmissions in the MTC area.

In Example 68, the subject matter of one or any combination of Examples 48-67 may optionally include, wherein the transceiver is further configured to receive a cell-specific reference signal from the eNB.

In Example 69, the subject matter of one or any combination of Examples 48-68 may optionally include, wherein the cell-specific reference signal is received in a multimedia broadcast single frequency network subframe within the MTC area.

In Example 70, the subject matter of one or any combination of Examples 48-69 may optionally include, wherein the cell-specific reference signal comprises a resource mapping pattern using an MTC random seed.

In Example 71, the subject matter of one or any combination of Examples 48-70 may optionally include, wherein the transceiver is further configured to receive an MTC Master Information Block (M-MIB) from the eNB.

In Example 72, the subject matter of one or any combination of Examples 48-71 can optionally include, wherein to receive the M-MIB, the transceiver is further configured to receive the M-MIB in a subframe in a frame within the MTC area.

In Example 73, the subject matter of one or any combination of Examples 48-72 may optionally include, wherein the M-MIB includes time and frequency resource information of the UE.

In Example 74, the subject matter of one or any combination of Examples 48-73 may optionally include, wherein to receive the M-MIB, the transceiver is further configured to receive the M-MIB on an MTC physical broadcast channel (M-PBCH).

In Example 75, the subject matter of one or any combination of Examples 48-74 may optionally include, wherein the transceiver is further configured to receive an MTC Physical Broadcast Channel (M-PBCH) transmission in the subframe.

In Example 76, the subject matter of one or any combination of Examples 48-75 may optionally include, wherein the subframe comprises a subframe not used for a primary synchronization signal and a secondary synchronization signal (PSS/SSS).

In Example 77, the subject matter of one or any combination of Examples 48-76 may optionally include, wherein the transceiver is further configured to receive a second subframe from the UE, the second subframe including a physical broadcast channel (PBCH) transmission different from the M-PBCH transmission.

In Example 78, the subject matter of one or any combination of Examples 48-77 may optionally include, wherein the PBCH transmission and the M-PBCH transmission are time division multiplexed between the subframe and the second subframe, and wherein the PBCH transmission and the M-PBCH transmission are allocated in the same resources.

In Example 79, the subject matter of one or any combination of Examples 48-78 may optionally include, wherein the transceiver is further configured to receive a physical broadcast channel (PBCH) transmission other than the M-PBCH transmission in the subframe.

In Example 80, the subject matter of one or any combination of Examples 48-79 may optionally include, wherein the PBCH transmission and the M-PBCH transmission are time division multiplexed within the subframe.

In Example 81, the subject matter of one or any combination of Examples 48-80 may optionally include, wherein the transceiver is further configured to receive an MTC Physical Control Format Indicator Channel (PCFICH) transmission from the eNB.

In Example 82, the subject matter of one or any combination of Examples 48-81 optionally includes, wherein to receive the MTC PCFICH transmission, the transceiver is further configured to determine that the number of orthogonal frequency division multiplexing (OFDM) symbols allocated for the MTC physical downlink control channel (M-PDCCH) and the starting symbol of the MTC physical downlink shared channel (M-PDSCH) transmission are not predefined.

In Example 83, the subject matter of one or any combination of Examples 48-82 can optionally include, wherein the transceiver is further configured to receive a Physical Hybrid Automatic Repeat Request (ARQ) Indicator Channel (M-PHICH) transmission from the eNB.

In Example 84, the subject matter of one or any combination of Examples 48-83 may optionally include, wherein to receive the M-PHICH, the transceiver is further configured to receive configuration information from the eNB in a system information block (SIB) or a master information block (MIB).

In Example 85, the subject matter of one or any combination of Examples 48-84 may optionally include, wherein to receive the M-PHICH, the transceiver is further configured to determine that an MTC physical downlink control channel (M-PDCCH) does not replace the M-PHICH functionality.

In Example 86, the subject matter of one or any combination of Examples 48-85 can optionally include, wherein the transceiver is further configured to receive an MTC physical downlink control channel (M-PDCCH) transmission from an eNB in the MTC area.

In Example 87, the subject matter of one or any combination of Examples 48-86 may optionally include, wherein the M-PDCCH comprises an existing enhanced physical downlink control channel (EPDCCH).

In Example 88, the subject matter of one or any combination of Examples 48-87 can optionally include, wherein the transceiver is further configured to transmit an MTC physical random access channel (M-PRACH) transmission.

In Example 89, the subject matter of one or any combination of Examples 48-88 may optionally include, wherein the M-PRACH transmission is time division multiplexed with the MTC physical uplink control channel (M-PUCCH) transmission and the MTC physical uplink shared channel (M-PUSCH) transmission in the MTC area.

In Example 90, the subject matter of one or any combination of Examples 48-89 may optionally include, wherein the M-PUCCH transmission and the M-PUSCH transmission are frequency division multiplexed in the MTC area.

Example 91 includes a subject matter embodied by a user equipment (UE) configured to operate on a machine type communication (MTC) MTC area of a wireless spectrum, comprising a transceiver configured to: receive a physical downlink control channel (PDCCH) transmission from an evolved Node B (eNB) on a licensed band; receive an MTC master information block (M-MIB) from the eNB, the M-MIB including configuration information for configuring the MTC area; and receive a first data transmission on the MTC area in a downlink, wherein the MTC area includes a subset of frequencies of the licensed band; and send a second data transmission on the MTC area in an uplink.

In Example 92, the subject matter of Example 91 may optionally include, wherein the transceiver is further configured to receive an MTC system information block (M-SIB) from the eNB.

In Example 93, the subject matter of one or any combination of Examples 91-92 may optionally include, wherein to receive the M-SIB, the transceiver is further configured to receive the M-SIB in a subframe in a frame within the MTC area.

In Example 94, the subject matter of one or any combination of Examples 91-93 may optionally include, wherein the M-SIB includes time and frequency resource information of the UE.

Example 95 includes subject matter embodied by a method performed by circuitry of an evolved Node B (eNB) for configuring a user equipment (UE) for communication, the method comprising: broadcasting a physical downlink control channel (PDCCH) transmission from the eNB on a licensed frequency band; sending a machine type communication (MTC) physical broadcast channel (M-PBCH) transmission multiplexed with a PBCH transmission from the eNB to the UE, the M-PBCH transmission comprising an MTC system information block (M-SIB), the M-SIB comprising configuration information for configuring an MTC area of the licensed frequency band, wherein the MTC area comprises a subset of frequencies of the licensed frequency band; and sending a first data transmission from the eNB to the UE on the MTC area in a downlink.

In Example 96, the subject matter of Example 95 may optionally include, wherein the method further comprises receiving a second data transmission from the UE on the MTC area on the uplink.

In Example 97, the subject matter of one or any combination of Examples 95-96 may optionally include, wherein receiving the second data transmission comprises receiving the second data transmission multiplexed with a physical uplink control channel (PUCCH) or a physical random access channel (PRACH) in a frequency division manner.

In Example 98, the subject matter of one or any combination of Examples 95-97 may optionally include, wherein receiving the second data transmission comprises receiving the second data transmission in an intra-slot frequency hopping transmission.

In Example 99, the subject matter of one or any combination of Examples 95-98 may optionally include, further comprising multiplexing the first data transmission and the third data transmission in a time division manner.

In Example 100, the subject matter of one or any combination of Examples 95-99 may optionally include further comprising multiplexing the first data transmission and the third data transmission in a frequency division manner.

In Example 101, the subject matter of one or any combination of Examples 95-100 may optionally include, wherein sending the first data transmission comprises sending the first data transmission using intra-slot hopping.

In Example 102, the subject matter of one or any combination of Examples 95-101 may optionally include, wherein the intra-slot frequency hopping transmission comprises a fixed hopping pattern.

In Example 103, the subject matter of one or any combination of Examples 95-102 may optionally include, wherein the fixed hopping pattern includes information about a physical cell identity.

In Example 104, the subject matter of one or any combination of Examples 95-103 may optionally include, wherein the fixed skip pattern includes information about a subframe index.

In Example 105, the subject matter of one or any combination of Examples 95-104 may optionally include, wherein the MTC area is predefined.

In Example 106, the subject matter of one or any combination of Examples 95-105 may optionally include, wherein the SIB includes time and frequency resource information for the UE.

In Example 107, the subject matter of one or any combination of Examples 95-106 may optionally include, further comprising sending independent signaling configurations for the uplink MTC area and the downlink MTC area to the UE.

In Example 108, the subject matter of one or any combination of Examples 95-107 may optionally include, further comprising sending a joint signaling configuration for the uplink MTC area and the downlink MTC area to the UE.

In Example 109, the subject matter of one or any combination of Examples 95-108 may optionally include, further comprising sending a primary synchronization signal and a secondary synchronization signal (PSS/SSS) to the UE.

In Example 110, the subject matter of one or any combination of Examples 95-109 may optionally include, further comprising rate matching resource element mapping to around a PSS/SSS within the MTC area.

In Example 111, the subject matter of one or any combination of Examples 95-110 may optionally include, further comprising sending a channel state information reference signal (CSI-RS) to the UE.

In Example 112, the subject matter of one or any combination of Examples 95-111 may optionally include, further comprising rate matching resource element mapping to around a CSI-RS of the MTC area.

In Example 113, the subject matter of one or any combination of Examples 95-112 may optionally include, further comprising avoiding collisions between CSI-RS and transmissions in the MTC area.

In Example 114, the subject matter of one or any combination of Examples 95-113 may optionally include, further comprising sending a cell-specific reference signal to the UE.

In Example 115, the subject matter of one or any combination of Examples 95-114 may optionally include, wherein the cell-specific reference signal is transmitted in a multimedia broadcast single frequency network subframe within the MTC area.

In Example 116, the subject matter of one or any combination of Examples 95-115 may optionally include, wherein the cell-specific reference signal comprises a resource mapping pattern using an MTC random seed.

In Example 117, the subject matter of one or any combination of Examples 95-116 may optionally include, further comprising sending an MTC Master Information Block (M-MIB) to the UE.

In Example 118, the subject matter of one or any combination of Examples 95-117 may optionally include, wherein transmitting the M-MIB comprises transmitting the M-MIB in a subframe in a frame within the MTC area.

In Example 119, the subject matter of one or any combination of Examples 95-118 may optionally include, wherein the M-MIB includes time and frequency resource information of the UE.

In Example 120, the subject matter of one or any combination of Examples 95-119 may optionally include, wherein transmitting the M-MIB comprises transmitting the M-MIB on an MTC physical broadcast channel (M-PBCH).

In Example 121, the subject matter of one or any combination of Examples 95-120 may optionally include, wherein transmitting the M-PBCH comprises transmitting the M-PBCH in a subframe.

In Example 122, the subject matter of one or any combination of Examples 95-121 may optionally include, wherein the subframe comprises a subframe not used for a primary synchronization signal and a secondary synchronization signal (PSS/SSS).

In Example 123, the subject matter of one or any combination of Examples 95-122 may optionally include, further comprising sending a second subframe to the UE, the second subframe comprising a physical broadcast channel (PBCH) transmission different from the M-PBCH transmission.

In Example 124, the subject matter of one or any combination of Examples 95-123 may optionally include, wherein the PBCH transmission and the M-PBCH transmission are time division multiplexed between the subframe and the second subframe, and wherein the PBCH transmission and the M-PBCH transmission are allocated in the same resources.

In Example 125, the subject matter of one or any combination of Examples 95-124 can optionally include further comprising sending a physical broadcast channel (PBCH) transmission different from the M-PBCH transmission in the subframe.

In Example 126, the subject matter of one or any combination of Examples 95-125 may optionally include, wherein the PBCH transmission and the M-PBCH transmission are time division multiplexed within the subframe.

In Example 127, the subject matter of one or any combination of Examples 95-126 may optionally include, further comprising sending an MTC Physical Control Format Indicator Channel (PCFICH) transmission to the UE.

In Example 128, the subject matter of one or any combination of Examples 95-127 may optionally include, wherein sending an MTC PCFICH transmission includes determining a number of orthogonal frequency division multiplexing (OFDM) symbols allocated for an MTC physical downlink control channel (M-PDCCH) and a starting symbol for an MTC physical downlink shared channel (M-PDSCH) transmission is not predefined.

In Example 129, the subject matter of one or any combination of Examples 95-128 can optionally include, further comprising sending a Physical Hybrid Automatic Repeat Request (ARQ) Indicator Channel (M-PHICH) transmission to the UE.

In Example 130, the subject matter of one or any combination of Examples 95-129 may optionally include, wherein sending the M-PHICH comprises sending configuration information to the UE in a system information block (SIB) or a master information block (MIB).

In Example 131, the subject matter of one or any combination of Examples 95-130 may optionally include, wherein transmitting the M-PHICH comprises determining that an MTC physical downlink control channel (M-PDCCH) does not replace M-PHICH functionality.

In Example 132, the subject matter of one or any combination of Examples 95-131 may optionally include, further comprising sending an MTC physical downlink control channel (M-PDCCH) transmission to the UE in the MTC area.

In Example 133, the subject matter of one or any combination of Examples 95-132 may optionally include, wherein the M-PDCCH comprises an existing enhanced physical downlink control channel (EPDCCH).

In Example 134, the subject matter of one or any combination of Examples 95-133 may optionally include, further comprising receiving an MTC physical random access channel (M-PRACH) transmission from the UE.

In Example 135, the subject matter of one or any combination of Examples 95-134 may optionally include, wherein the M-PRACH transmission is time division multiplexed with the MTC physical uplink control channel (M-PUCCH) transmission and the MTC physical uplink shared channel (M-PUSCH) transmission in the MTC area.

In Example 136, the subject matter of one or any combination of Examples 95-135 may optionally include, wherein the M-PUCCH transmission and the M-PUSCH transmission are frequency division multiplexed in the MTC area.

Example 137 includes an apparatus comprising means for performing the method of any of claims 95-136.

Example 138 includes at least one machine-readable medium including instructions for operating a computer system, which instructions, when executed by the machine, cause the machine to perform the method of any one of claims 95-136.

Example 139 includes a subject matter embodied by an apparatus for configuring a user equipment (UE) for communication, the apparatus comprising: means for broadcasting a physical downlink control channel (PDCCH) transmission from an evolved Node B (eNB) on a licensed frequency band; means for sending a machine type communication (MTC) physical broadcast channel (M-PBCH) transmission multiplexed with a PBCH transmission from the eNB to the UE, the M-PBCH transmission comprising an MTC system information block (M-SIB), the M-SIB comprising configuration information for configuring an MTC area of the licensed frequency band, wherein the MTC area comprises a subset of frequencies of the licensed frequency band; and means for sending a first data transmission from the eNB to the UE on the MTC area in a downlink.

Example 140 includes subject matter embodied by at least one machine-readable medium comprising instructions for operating a computing system, the instructions, when executed by the machine, causing the machine to perform the following operations: broadcasting a physical downlink control channel (PDCCH) transmission from an evolved Node B (eNB) on a licensed frequency band; sending a machine-type communication (MTC) physical broadcast channel (M-PBCH) transmission multiplexed with a PBCH transmission from the eNB to a UE, the M-PBCH transmission comprising an MTC system information block (M-SIB), the M-SIB comprising configuration information for configuring an MTC area of the licensed frequency band, wherein the MTC area comprises a subset of frequencies of the licensed frequency band; and sending a first data transmission from the eNB to the UE on the MTC area in a downlink.

Example 141 includes subject matter embodied by a method for configuring a user equipment (UE) to operate on an MTC area of a wireless spectrum, the method comprising: receiving, at the UE, a physical downlink control channel (PDCCH) transmission from an evolved Node B (eNB) on a licensed band; receiving, at the UE, a machine type communication (MTC) physical broadcast channel (M-PBCH) transmission from the eNB on the MTC area, including an MTC system information block (M-SIB); and sending a data transmission from the UE on the MTC area in an uplink, wherein the MTC area includes a subset of frequencies of the licensed band.

In Example 142, the subject matter of Example 140 may optionally include, wherein sending the data transmission comprises sending the data transmission multiplexed with a second data transmission.

In Example 143, the subject matter of one or any combination of Examples 141-142 may optionally include, wherein the data transmission and the second data transmission are multiplexed in a time division manner.

In Example 144, the subject matter of one or any combination of Examples 141-143 may optionally include, wherein the data transmission and the second data transmission are multiplexed in a frequency division manner.

In Example 145, the subject matter of one or any combination of Examples 141-144 may optionally include, wherein sending the data transmission comprises sending the data transmission using intra-slot hopping.

In Example 146, the subject matter of one or any combination of Examples 141-145 may optionally include further comprising receiving a third data transmission from the eNB over the MTC area in a downlink.

In Example 147, the subject matter of one or any combination of Examples 141-146 may optionally include, wherein receiving the third data transmission comprises receiving the third data transmission in an intra-slot frequency hopping transmission.

In Example 148, the subject matter of one or any combination of Examples 141-147 may optionally include, wherein the intra-slot frequency hopping transmission comprises a fixed hopping pattern.

In Example 149, the subject matter of one or any combination of Examples 141-148 may optionally include, wherein the fixed hopping pattern includes information about a physical cell identity.

In Example 150, the subject matter of one or any combination of Examples 141-149 may optionally include, wherein the fixed skip pattern includes information about a subframe index.

In Example 151, the subject matter of one or any combination of Examples 141-150 may optionally include, wherein the MTC area is predefined.

In Example 152, the subject matter of one or any combination of Examples 141-151 may optionally include, wherein the SIB includes time and frequency resource information for the UE.

In Example 153, the subject matter of one or any combination of Examples 141-152 may optionally include, further comprising receiving independent signaling configurations for the uplink MTC area and the downlink MTC area from the eNB.

In Example 154, the subject matter of one or any combination of Examples 141-153 may optionally include, further comprising receiving a joint signaling configuration for the uplink MTC area and the downlink MTC area from the eNB.

In Example 155, the subject matter of one or any combination of Examples 141-154 may optionally include, further comprising receiving a primary synchronization signal and a secondary synchronization signal (PSS/SSS) from the eNB.

In Example 156, the subject matter of one or any combination of Examples 141-155 may optionally include, further comprising rate matching resource element mapping to around a PSS/SSS within the MTC area.

In Example 157, the subject matter of one or any combination of Examples 141-156 may optionally include, further comprising receiving a channel state information reference signal (CSI-RS) from the eNB.

In Example 158, the subject matter of one or any combination of Examples 141-157 may optionally include, further comprising rate matching resource element mapping to around a CSI-RS of the MTC area.

In Example 159, the subject matter of one or any combination of Examples 141-158 may optionally include, further comprising avoiding collisions between CSI-RS and transmissions in the MTC area.

In Example 160, the subject matter of one or any combination of Examples 141-159 may optionally include further comprising receiving a cell-specific reference signal from the eNB.

In Example 161, the subject matter of one or any combination of Examples 141-160 may optionally include, wherein the cell-specific reference signal is received in a multimedia broadcast single frequency network subframe within the MTC area.

In Example 162, the subject matter of one or any combination of Examples 141-161 may optionally include, wherein the cell-specific reference signal comprises a resource mapping pattern using an MTC random seed.

In Example 163, the subject matter of one or any combination of Examples 141-162 may optionally include, further comprising receiving an MTC Master Information Block (M-MIB) from the eNB.

In Example 164, the subject matter of one or any combination of Examples 141-163 may optionally include, wherein receiving the M-MIB comprises receiving the M-MIB in a subframe in a frame within the MTC area.

In Example 165, the subject matter of one or any combination of Examples 141-164 may optionally include, wherein the M-MIB includes time and frequency resource information of the UE.

In Example 166, the subject matter of one or any combination of Examples 141-165 may optionally include, wherein receiving the M-MIB comprises receiving the M-MIB on an MTC Physical Broadcast Channel (M-PBCH).

In Example 167, the subject matter of one or any combination of Examples 141-166 may optionally include, wherein receiving the M-PBCH comprises receiving the M-PBCH in a subframe.

In Example 168, the subject matter of one or any combination of Examples 141-167 may optionally include, wherein the subframe comprises a subframe not used for a primary synchronization signal and a secondary synchronization signal (PSS/SSS).

In Example 169, the subject matter of one or any combination of Examples 141-168 may optionally include, further comprising receiving a second subframe from the UE, the second subframe including a physical broadcast channel (PBCH) transmission different from the M-PBCH transmission.

In Example 170, the subject matter of one or any combination of Examples 141-169 may optionally include, wherein the PBCH transmission and the M-PBCH transmission are time division multiplexed between the subframe and the second subframe, and wherein the PBCH transmission and the M-PBCH transmission are allocated in the same resources.

In Example 171, the subject matter of one or any combination of Examples 141-170 may optionally include further comprising receiving a physical broadcast channel (PBCH) transmission other than an M-PBCH transmission in the subframe.

In Example 172, the subject matter of one or any combination of Examples 141-171 may optionally include, wherein the PBCH transmission and the M-PBCH transmission are time division multiplexed within the subframe.

In Example 173, the subject matter of one or any combination of Examples 141-172 may optionally include, further comprising receiving an MTC Physical Control Format Indicator Channel (PCFICH) transmission from the eNB.

In Example 174, the subject matter of one or any combination of Examples 141-173 may optionally include, wherein receiving an MTC PCFICH transmission includes determining a number of orthogonal frequency division multiplexing (OFDM) symbols allocated for an MTC physical downlink control channel (M-PDCCH) and a starting symbol for an MTC physical downlink shared channel (M-PDSCH) transmission is not predefined.

In Example 175, the subject matter of one or any combination of Examples 141-174 can optionally include further comprising receiving a Physical Hybrid Automatic Repeat Request (ARQ) Indicator Channel (M-PHICH) transmission from the eNB.

In Example 176, the subject matter of one or any combination of Examples 141-175 may optionally include, wherein receiving the M-PHICH comprises receiving configuration information from the eNB in a system information block (SIB) or a master information block (MIB).

In Example 177, the subject matter of one or any combination of Examples 141-176 may optionally include, wherein receiving the M-PHICH comprises determining that an MTC physical downlink control channel (M-PDCCH) does not replace M-PHICH functionality.

In Example 178, the subject matter of one or any combination of Examples 141-177 may optionally include, further comprising receiving an MTC physical downlink control channel (M-PDCCH) transmission from an eNB in the MTC area.

In Example 179, the subject matter of one or any combination of Examples 141-178 may optionally include, wherein the M-PDCCH comprises an existing enhanced physical downlink control channel (EPDCCH).

In Example 180, the subject matter of one or any combination of Examples 141-179 may optionally include further comprising transmitting an MTC physical random access channel (M-PRACH) transmission.

In Example 181, the subject matter of one or any combination of Examples 141-180 may optionally include, wherein the M-PRACH transmission is time division multiplexed with the MTC physical uplink control channel (M-PUCCH) transmission and the MTC physical uplink shared channel (M-PUSCH) transmission in the MTC area.

In Example 182, the subject matter of one or any combination of Examples 141-181 may optionally include, wherein the M-PUCCH transmission and the M-PUSCH transmission are frequency division multiplexed in the MTC area.

Example 183 includes an apparatus comprising means for performing the method of any of claims 141-182.

Example 184 includes at least one machine-readable medium including instructions for operating a computer system, which instructions, when executed by the machine, cause the machine to perform the method of any one of claims 141-182.

Example 185 includes a subject matter embodied by at least one machine-readable medium, the at least one machine-readable medium comprising instructions for operating a computing system, which, when executed by the machine, causes the machine to perform the following operations: receiving a physical downlink control channel (PDCCH) transmission from an evolved Node B (eNB) on a licensed frequency band at a UE; receiving a machine-type communication (MTC) physical broadcast channel (M-PBCH) transmission from the eNB at the UE, including an MTC system information block (M-SIB), the SIB including configuration information for configuring an MTC area of the licensed frequency band, wherein the MTC area includes a subset of frequencies of the licensed frequency band; and sending a data transmission from the UE on the MTC area in an uplink.

In Example 186, the subject matter of Example 185 may optionally include, wherein the operation of receiving the data transmission comprises the operation of receiving the data transmission using intra-slot hopping.

The above detailed description includes reference to the accompanying drawings that form a part of the specific embodiment. The accompanying drawings show specific embodiments by explanation. These embodiments are also referred to as "examples" in this article. Such examples may include elements other than the elements shown or described. However, the inventors of the present invention also consider examples in which only those elements shown or described are provided. In addition, whether for the specific examples (or one or more aspects thereof) shown or described herein or for other examples (or one or more aspects thereof), the inventors of the present invention also consider examples using any combination or arrangement of those elements shown or described (or one or more aspects thereof).

In the event of a conflicting usage between this document and those documents incorporated herein by reference, the usage in this document controls.

In this document, as is common in patent documents, the words "a" or "an" are used to include one or more than one, independent of any other instance or usage of "at least one" or "one or more". In this document, unless otherwise indicated, the word "or" is used to refer to a non-exclusive or, such that "A or B" includes "A not B", "B not A", and "A and B". In this document, the words "including" and "in which" are used as the literal English equivalents of the words "comprising" and "wherein", respectively. In addition, in the claims that follow, the words "including" and "comprising" are open-ended, that is, systems, devices, articles, compositions, compositions or processes that include other elements in addition to those elements listed after such words in the claims are also considered to fall within the scope of the claims. In addition, in the claims that follow, the words "first", "second", and "third", etc. are used merely as labels and are not intended to impose numerical requirements on their objects.

The method examples described herein may be at least partially machine or computer-implemented. Some examples may include a computer-readable storage medium or machine-readable storage medium encoded with instructions, which may be operable to configure an electronic device to perform the methods described in the above examples. The implementation of such methods may include code, such as microcode, assembly language code, higher-level language code, etc. Such code may include computer-readable instructions for performing various methods. The code may form part of a computer program product. In addition, in an example, the code may be tangibly stored on one or more volatile, non-transitory or non-volatile tangible computer-readable media, for example, during execution or at other times. Examples of these tangible computer-readable storage media may include, but are not limited to, hard disks, removable disks, removable optical disks (e.g., optical disks and digital video disks), magnetic tape cassettes, memory cards or sticks, random access memories (RAMs), read-only memories (ROMs), etc.

The above description is intended to be illustrative, not restrictive. For example, the above examples (or one or more aspects thereof) may be used in combination with each other. For example, other embodiments may be used by one of ordinary skill in the art after reviewing the above description. The abstract is provided to comply with the provisions of Section 1.72(b) of 37 C.F.R. to allow the reader to quickly determine the nature of the present disclosure. Its submission will be understood not to be used to interpret or limit the scope or meaning of the claims. In addition, in the above detailed description, various features may be grouped together to streamline the disclosure. This should not be interpreted to mean that features disclosed but not included in the claims are essential to any claim. On the contrary, the subject matter of the invention may include fewer features than all the features of a particular disclosed embodiment. Therefore, the appended claims are incorporated into the detailed description as examples or embodiments, wherein each claim exists independently as a separate embodiment, and it is conceivable that such embodiments may be combined with each other into various combinations or arrangements.

Claims (32)

1. An evolved Node B (eNB) configured to communicate with a User Equipment (UE) on a licensed frequency band, the eNB including circuitry configured to: Transmit physical downlink control channel (PDCCH) transmissions on the licensed frequency band; Send a Machine-Type Communication (MTC) System Information Block (M-SIB) to the UE, the M-SIB including configuration information for configuring an MTC region of the licensed frequency band, wherein the MTC region includes a subset of the frequencies of the licensed frequency band; The Channel State Information Reference Signal (CSI-RS) is transmitted to the UE within the MTC area; By performing rate matching on the resource element mapping around the CSI-RS within the MTC area, conflicts between the CSI-RS and the transmissions within the MTC area can be avoided. Sending the first data transmission to the UE in the MTC area of the downlink; and The second data transmission from the UE is received in the MTC area of the uplink. 2. The eNB of claim 1, wherein, in order to transmit the first data transmission, the circuit is configured to transmit the first data transmission multiplexed with the third data transmission. 3. The eNB as claimed in claim 2, wherein the first data transmission and the third data transmission are multiplexed in a time-division manner. 4. The eNB of claim 1, wherein, in order to receive the second data transmission, the circuitry is configured to receive the second data transmission multiplexed in frequency division with transmissions on the Physical Uplink Control Channel (PUCCH) or Physical Random Access Channel (PRACH). 5. The eNB as claimed in claim 1, wherein the M-SIB includes time and frequency resource information for the MTC area of the UE. 6. The eNB of claim 1, wherein the circuitry is further configured to send a primary synchronization signal and a secondary synchronization signal (PSS/SSS) to the UE. 7. The eNB of claim 6, wherein the circuitry is further configured to rate-match resource element mapping to the vicinity of the PSS/SSS within the MTC region. 8. The eNB of claim 1, wherein the circuitry is further configured to transmit a cell-specific reference signal to the UE. 9. The eNB of claim 1, wherein the circuitry is further configured to send an MTC master information block (M-MIB) to the UE. 10. The eNB of claim 9, wherein, in order to transmit the M-MIB, the circuitry is further configured to transmit the M-MIB in a subframe within a frame in the MTC area. 11. The eNB of claim 1, wherein the circuitry is further configured to transmit MTC Physical Broadcast Channel (M-PBCH) transmissions in a subframe. 12. The eNB of claim 11, wherein the circuitry is further configured to send a second subframe to the UE, the second subframe including a Physical Broadcast Channel (PBCH) transmission different from the M-PBCH transmission. 13. The eNB of claim 12, wherein the PBCH transmission and the M-PBCH transmission are time-division multiplexed between the subframe and the second subframe, and wherein the PBCH transmission and the M-PBCH transmission are allocated in the same resource. 14. The eNB of claim 11, wherein the circuitry is further configured to transmit a Physical Broadcast Channel (PBCH) transmission in the subframe that is different from the M-PBCH transmission. 15. A user equipment (UE) configured to operate in a machine-type communication (MTC) area of the radio spectrum, comprising: The transceiver is configured as follows: Receive physical downlink control channel (PDCCH) transmissions from evolved Node B (eNB) on the licensed frequency band; Receive an MTC System Information Block (M-SIB) from the eNB, the M-SIB including configuration information for configuring the MTC region; Channel State Information Reference Signal (CSI-RS) is received from the eNB within the MTC area, wherein resource element mapping around the CSI-RS within the MTC area is rate-matched to avoid conflicts between the CSI-RS and transmissions within the MTC area; Receive the first data transmission in the MTC area of the downlink; and Send the second data transmission in the MTC area of the uplink. The MTC region includes a subset of the frequencies of the licensed frequency band. 16. The UE of claim 15, wherein the transceiver is further configured to transmit MTC Physical Random Access Channel (M-PRACH) transmissions. 17. The UE of claim 16, wherein the M-PRACH transmission is time-division multiplexed with the MTC Physical Uplink Control Channel (M-PUCCH) transmission and the MTC Physical Uplink Shared Channel (M-PUSCH) transmission in the MTC area. 18. The UE of claim 15, further comprising one or more antennas coupled to the transceiver. 19. A method for configuring a user equipment (UE) to communicate, performed by a circuit of an evolved Node B (eNB), the method comprising: Transmitted from the eNB via the Physical Downlink Control Channel (PDCCH) on the licensed frequency band; The eNB sends a PBCH transmission multiplexed with Machine Type Communication (MTC) Physical Broadcast Channel (PBCH) (M-PBCH) transmission to the UE. The M-PBCH transmission includes an MTC System Information Block (M-SIB), which includes configuration information for configuring an MTC region of the licensed frequency band, wherein the MTC region includes a subset of the frequencies of the licensed frequency band. The channel state information reference signal (CSI-RS) is sent to the UE within the MTC area; Rate matching is performed on the resource element mapping around the CSI-RS within the MTC area to avoid conflicts between the CSI-RS and transmissions within the MTC area; and The first data transmission is sent from the eNB to the UE in the MTC area of the downlink. 20. The method of claim 19, further comprising sending a Physical Hybrid Automatic Repeat Request (ARQ) indicator channel M-PHICH transmission to the UE. 21. The method of claim 20, wherein sending the M-PHICH includes sending configuration information to the UE in a System Information Block (SIB) or Master Information Block (MIB). 22. At least one machine-readable medium comprising instructions for operating a computer system, said instructions, when executed by a machine, causing the machine to perform the method of any one of claims 19-21. 23. An apparatus for configuring a user equipment (UE) to communicate, performed by a circuit of an evolved Node B (eNB), the apparatus comprising: A means for broadcasting physical downlink control channel (PDCCH) transmissions from the eNB over a licensed frequency band; A means for transmitting from the eNB to the UE a PBCH transmission multiplexed with a Machine Type Communication (MTC) Physical Broadcast Channel (PBCH) (M-PBCH) transmission, the M-PBCH transmission including an MTC System Information Block (M-SIB) including configuration information for configuring an MTC region of the licensed frequency band, wherein the MTC region includes a subset of frequencies of the licensed frequency band; A means for transmitting a Channel State Information Reference Signal (CSI-RS) to the UE within the MTC area; A means for avoiding conflicts between the CSI-RS and transmissions in the MTC area by rate matching of resource element mapping around the CSI-RS within the MTC area; and A means for transmitting a first data transmission from the eNB to the UE in the MTC area of the downlink. 24. The apparatus of claim 23, further comprising: means for transmitting a Physical Hybrid Automatic Repeat Request (ARQ) indicator channel M-PHICH transmission to the UE. 25. The device of claim 24, wherein sending the M-PHICH includes sending configuration information to the UE in a System Information Block (SIB) or Master Information Block (MIB). 26. A method performed by a user equipment (UE) to configure the UE to operate in a machine-type communication (MTC) area of the radio spectrum, comprising: Receive physical downlink control channel (PDCCH) transmissions from evolved Node B (eNB) on the licensed frequency band; Receive an MTC System Information Block (M-SIB) from the eNB, the M-SIB including configuration information for configuring the MTC region; Channel State Information Reference Signal (CSI-RS) is received from the eNB within the MTC area, wherein resource element mapping around the CSI-RS within the MTC area is rate-matched to avoid conflicts between the CSI-RS and transmissions within the MTC area; Receive the first data transmission in the MTC area of the downlink; and Send the second data transmission in the MTC area of the uplink. The MTC region includes a subset of the frequencies of the licensed frequency band. 27. The method of claim 26, further comprising: transmitting MTC Physical Random Access Channel (M-PRACH) transmission. 28. The method of claim 27, wherein the M-PRACH transmission is time-division multiplexed with the MTC Physical Uplink Control Channel (M-PUCCH) transmission and the MTC Physical Uplink Shared Channel (M-PUSCH) transmission in the MTC area. 29. An apparatus for configuring a user equipment (UE) to operate in a machine-type communication (MTC) area of a radio spectrum, performed by a user equipment (UE), comprising: Apparatus for receiving physical downlink control channel (PDCCH) transmissions from evolved Node B (eNB) on a licensed frequency band; A means for receiving an MTC system information block (M-SIB) from the eNB, the M-SIB including configuration information for configuring the MTC area; A means for receiving a Channel State Information Reference Signal (CSI-RS) from an eNB within the MTC area, wherein resource element mappings around the CSI-RS within the MTC area are rate-matched to avoid conflicts between the CSI-RS and transmissions within the MTC area; A means for receiving a first data transmission over an MTC area in a downlink, wherein the MTC area comprises a subset of frequencies of the licensed frequency band; and A means for transmitting a second data transmission over an MTC area in an uplink. 30. The apparatus of claim 29, further comprising: means for transmitting MTC Physical Random Access Channel (M-PRACH) transmissions. 31. The device of claim 30, wherein the M-PRACH transmission is time-division multiplexed with the MTC Physical Uplink Control Channel (M-PUCCH) transmission and the MTC Physical Uplink Shared Channel (M-PUSCH) transmission in the MTC area. 32. At least one machine-readable medium comprising instructions for operating a computer system, said instructions, when executed by a machine, causing the machine to perform the method of any one of claims 26-28.