eMTC Technology

Enhanced Machine-Type Communication

Definition

eMTC (enhanced Machine-Type Communications), also known as LTE-M, is a cellular IoT technology defined by 3GPP R13. It operates on a 1.4 MHz narrowband, coexisting with LTE broadband on the same carrier, supporting handover, roaming, VoLTE, and is a mainstream LPWAN technology alongside NB-IoT. eMTC is suitable for scenarios requiring mobility or voice capability, such as wearables, vehicle tracking, and mobile payments.

Comparison with NB-IoT

  • eMTC: Supports mobility, handover, VoLTE, with a peak rate of about 1 Mbps and slightly less coverage than NB-IoT.
  • NB-IoT: More power-efficient, deeper coverage (+20dB gain), lower cost, but does not support mobility
  • Co-deployment: Both can be deployed on different PRBs of the same LTE carrier, and operators often deploy them simultaneously.

Technical Features

eMTC uses 1.4 MHz narrowband, repeated transmission, and CE mode (Coverage Enhancement) to enhance coverage, supporting PSM and eDRX power saving. Compared with Cat.1, eMTC is more power-efficient and has a lower rate; compared with NB-IoT, eMTC supports mobility and voice.

Typical Use Cases

Wearable devices, vehicle tracking, mobile payments, smart meters (mobile scenarios), industrial IoT mobile terminals, etc. SimtoLink provides eMTC IoT SIM cards, forming a complete product portfolio with NB-IoT and Cat.1.

eMTC (LTE-M) is one of SimtoLink's important technology choices in low-power IoT scenarios. For scenarios requiring mobility and voice capabilities, such as wearables and vehicle tracking, SimtoLink can provide IoT SIM cards and connectivity solutions based on eMTC. The SimtoLink cloud platform supports the lifecycle management of eMTC devices, forming a complete cellular IoT product portfolio together with NB-IoT and Cat.1.

Raise the coverage-enhancement level and the repetition count multiplies

eMTC works on a narrowband of about 1.4 MHz and trades repeated transmission for deeper coverage. When the coverage-enhancement level rises, the same transport block is repeated across more subframes. Air time stretches roughly with the repetition factor, throughput falls, and the time the radio stays awake rises. To see whether a device has fallen into a high-repetition level, read whether the repetition count and the reference-signal level get worse together, not only whether an acknowledgement arrived in the end. A device that stays at high repetition underground or inside a cabinet for a long time needs its battery budget built for the worst level, not for one test in an open field.

Repetition is air-interface behavior. Application retransmission is another layer. If both are on, one report multiplies the same data on the air once more. In a weak field, keep the air-interface repetition and tighten the application timeout, so the timeout does not fire before air-interface repetition has finished.

Half-duplex keeps uplink and downlink off the same subframe

Many eMTC modules are half-duplex: transmit and receive share one radio path and cannot both run in the same subframe. The scheduler has to leave a turnaround time between uplink and downlink. If the service is designed to wait for a response the moment sending finishes, the turnaround gap is counted into delay. Voice or push-to-talk is sensitive to that gap. A pure report is less affected. Selection should see whether the module is half-duplex or full-duplex, and the network scheduler must be configured for the same capability. Otherwise an uplink grant arrives while the device is still receiving downlink, and the two are out of step.

Half-duplex does not mean mobility is impossible. Measurement gaps needed for handover are inserted further between receive and transmit, so delay while moving is longer than while stationary. Promising a vehicle tracker the delay measured on a stationary meter ignores the half-duplex gap.

Once mobility is on, tracking-area updates spend the power saving

Compared with a still narrower machine technology, an important difference of eMTC is that it can hand over while connected and do a normal location update while idle. When a vehicle or a person carries the device across a tracking area, it updates on a cycle. That signaling carries no service data, and it still has to turn the radio on. Power-saving mode and extended discontinuous reception remain available, but an update interrupts a long sleep. To tell whether the battery fell because there is more service or more movement, count service packets and location updates separately. If updates dominate, enlarge the tracking area or shorten the path across areas, rather than only stretching the report period.

If SimtoLink supplies an eMTC card, it fits a device that needs mobility or voice and still wants to use less power than a broadband module. The card’s power-saving timers have to be designed together with tracking-area size and the report period. If the timer is longer than the service cycle, the device is off the network most of the time, and a downlink command waits for the next wake. If the timer is shorter than the time to cross an area, updates caused by movement cancel the power saving. The platform should show the radio standard, the coverage-enhancement level, and the latest location update together, so an eMTC device is not operated as a narrowband terminal that does not support mobility.

When the coverage level changes, a power-saving cycle that is already counting gets interrupted

After the device enters power saving or extended discontinuous reception, the radio wakes on the agreed window. If the coverage-enhancement level rises between windows, the next wake has to finish synchronization and data with more repetitions first, and a server wait designed for a short window times out first. The server thinks the device did not wake. The device is still repeating the transmission. When the level falls, the opposite happens: the device finishes quickly and still waits empty on the high-repetition rhythm. A level change should be reported as an event, and the server wait should follow the current level, not only the step measured at the factory.

If the level jumps back and forth at the cell edge, power saving is as good as cancelled, because every jump has to synchronize again. Change the installation or accept a higher average current, rather than setting the power-saving timer even longer. A SimtoLink eMTC card provides the subscription and the access for this radio standard. The level is set by the radio environment. If the platform sees the level changing often and power use rising together, handle coverage first, rather than switching to a plan with a longer cycle. The plan does not change the repetition count.


Related Links

Return to the communications knowledge base