1178.4301.02 | Version 15 | Cellular IoT eMTC and NB-IoT
The following abbreviations are used throughout this manual: R&S®SMW200A is abbreviated as R&S SMW, R&S®WinIQSIM2 is
abbreviated as R&S WinIQSIM2; the license types 02/03/07/11/13/16/12 are abbreviated as xx.
ContentsCellular IoT eMTC and NB-IoT
Contents
1Welcome to the cellular IoT option.....................................................11
Welcome to the cellular IoT optionCellular IoT eMTC and NB-IoT
1Welcome to the cellular IoT option
The R&S SMW-K115/143/-K146 are a firmware application that adds functionality to
generate signals in accordance with the 3GPP specifications.
1.1Key features
If option R&S SMW-K143 is installed, the eMTC and NB-IoT features are in line with
3GPP Release 15. The following official 3GPP specifications are implemented:
●
3GPP TS 36.211, version 15.6.0
●
3GPP TS 36.212, version 15.6.0
●
3GPP TS 36.213, version 15.6.0
The R&S SMW-K115 key features
Key features
The R&S SMW simulates eMTC and NB-IoT at the physical channel level. The following is an overview of provided functions:
●
Supports uplink eMTC and NB-IoT configuration, as well as downlink NB-IoT configuration
●
Supports IoT standalone configuration and mixed configuration with LTE
●
Supports NB-IoT in-band and guard band opiating modes, incl. suppression of LTE
channels in in-band operating
●
Intuitive user interface with graphical display of time plan
●
Support of coverage enhancement CE modes A and B and CE levels 0 to 3
●
Support of the new NB channels and synchronization signals (NPSS, NSSS and
DL reference signal derived from NCell ID)
●
Support of PBCH (including SIB type 1), PDSCH and the new eMTC channel
MPDCCH
●
DCI-based configuration of NPDCCH/NPDSCH and MPDCCH/PDSCH
●
Channel coding and scrambling for NPDCCH, NPDSCH and NPBCH (including
SIB type 1)
●
Supports NPUSCH with channel coding and scrambling
●
NPRACH configuration
●
Manual NPUSCH scheduling
●
Support of all specified modulation schemes
The R&S SMW-K143 key features
This option extends the R&SSMW-K115 with 3GPP Rel. 14 features:
●
Supports uplink eMTC wideband operation, incl. configuration of the retuning symbols
●
Supports downlink eMTC wideband operation
●
Support of eMTC SRS configuration
11User Manual 1178.4301.02 ─ 15
Welcome to the cellular IoT optionCellular IoT eMTC and NB-IoT
Accessing the eMTC/NB-IoT dialog
●
DCI format N0 and N1 extended to support the Rel. 14 fields
●
Support of extended transport block sizes and PUCCH/PUSCH repetitions.
The R&S SMW-K146 key features
This option extends the R&SSMW-K115 with 3GPP Rel. 15 features:
●
Supports uplink NB-IoT operation in TDD mode, incl. NPUSCH
●
Supports FDD NPRACH formats
●
Supports NB-IoT wake up signal
●
Supports early data transmission in uplink
●
Supports scheduling request in uplink for NPUSCH format 2
This user manual contains a description of the functionality that the application provides, including remote control operation.
All functions not discussed in this manual are the same as in the base unit and are
described in the R&S SMW user manual. The latest version is available at:
www.rohde-schwarz.com/manual/SMW200A
Installation
You can find detailed installation instructions in the delivery of the option or in the
R&S SMW service manual.
1.2What's new
This documentation describes version 5.00.166 and higher of the cellular IoT eMTC
and NB-IoT firmware application. Compared to version 5.00.044 it provides it provides
the following new features and changes:
●
Option R&S SMW-K175 for O-RAN U-plane data, see:
–Chapter 7, "Generating user plane data", on page 348
–"U-Plane Generation"on page 62
●
Support of test models for O-RAN, see "Test Models"on page 59
1.3Accessing the eMTC/NB-IoT dialog
To open the dialog with eMTC/NB-IoT settings
1. In the block diagram of the R&S SMW, select "Baseband > EUTRA/LTE/IoT".
2. In the "General" tab, select "Mode > eMTC/NB-IoT or LTE/eMTC/NB-IoT"
A dialog box opens that display the provided general settings.
12User Manual 1178.4301.02 ─ 15
The signal generation is not started immediately. To start signal generation with the
default settings, select "State > On".
1.4Documentation overview
This section provides an overview of the R&S SMW user documentation. Unless specified otherwise, you find the documents on the R&S SMW product page at:
www.rohde-schwarz.com/manual/smw200a
1.4.1Getting started manual
Introduces the R&S SMW and describes how to set up and start working with the product. Includes basic operations, typical measurement examples, and general information, e.g. safety instructions, etc. A printed version is delivered with the instrument.
Welcome to the cellular IoT optionCellular IoT eMTC and NB-IoT
Documentation overview
1.4.2User manuals and help
Separate manuals for the base unit and the software options are provided for download:
●
Base unit manual
Contains the description of all instrument modes and functions. It also provides an
introduction to remote control, a complete description of the remote control commands with programming examples, and information on maintenance, instrument
interfaces and error messages. Includes the contents of the getting started manual.
●
Software option manual
Contains the description of the specific functions of an option. Basic information on
operating the R&S SMW is not included.
The contents of the user manuals are available as help in the R&S SMW. The help
offers quick, context-sensitive access to the complete information for the base unit and
the software options.
All user manuals are also available for download or for immediate display on the Internet.
1.4.3Tutorials
The R&S SMW provides interactive examples and demonstrations on operating the
instrument in form of tutorials. A set of tutorials is available directly on the instrument.
1.4.4Service manual
Describes the performance test for checking compliance with rated specifications, firmware update, troubleshooting, adjustments, installing options and maintenance.
13User Manual 1178.4301.02 ─ 15
The service manual is available for registered users on the global Rohde & Schwarz
information system (GLORIS):
https://gloris.rohde-schwarz.com
1.4.5Instrument security procedures
Deals with security issues when working with the R&S SMW in secure areas. It is available for download on the Internet.
1.4.6Printed safety instructions
Provides safety information in many languages. The printed document is delivered with
the product.
1.4.7Data sheets and brochures
Welcome to the cellular IoT optionCellular IoT eMTC and NB-IoT
Documentation overview
The data sheet contains the technical specifications of the R&S SMW. It also lists the
options and their order numbers and optional accessories.
The brochure provides an overview of the instrument and deals with the specific characteristics.
See www.rohde-schwarz.com/brochure-datasheet/smw200a
1.4.8Release notes and open source acknowledgment (OSA)
The release notes list new features, improvements and known issues of the current
firmware version, and describe the firmware installation.
The open-source acknowledgment document provides verbatim license texts of the
used open source software.
See www.rohde-schwarz.com/firmware/smw200a
1.4.9Application notes, application cards, white papers, etc.
These documents deal with special applications or background information on particular topics.
See www.rohde-schwarz.com/application/smw200a and www.rohde-schwarz.com/
manual/smw200a
14User Manual 1178.4301.02 ─ 15
1.5Scope
Tasks (in manual or remote operation) that are also performed in the base unit in the
same way are not described here.
In particular, it includes:
●
Managing settings and data lists, like saving and loading settings, creating and
accessing data lists, or accessing files in a particular directory.
●
Information on regular trigger, marker and clock signals and filter settings, if appropriate.
●
General instrument configuration, such as checking the system configuration, configuring networks and remote operation
●
Using the common status registers
For a description of such tasks, see the R&S SMW user manual.
Welcome to the cellular IoT optionCellular IoT eMTC and NB-IoT
Notes on screenshots
1.6Notes on screenshots
When describing the functions of the product, we use sample screenshots. These
screenshots are meant to illustrate as many as possible of the provided functions and
possible interdependencies between parameters. The shown values may not represent
realistic usage scenarios.
The screenshots usually show a fully equipped product, that is: with all options installed. Thus, some functions shown in the screenshots may not be available in your particular product configuration.
15User Manual 1178.4301.02 ─ 15
About the internet of things (IoT)Cellular IoT eMTC and NB-IoT
2About the internet of things (IoT)
The introduction of mobile communications extended the variety and the requirements
on the way machines communicate with each other. The machine communication is
known as machine type communication (MTC), the machine to machine communication (M2M) or the Internet of things (IoT).
Related 3GPP specifications
Because LTE was primarily optimized for the mobile broadband market, the specifications had to be extended to cover possible MTC solution. The following specifications
specify IoT related features:
●
3GPP LTE Rel. 12 (MTC)
First MTC specification, based on the existing LTE standard. Introduces new type
CAT0 devices
●
3GPP LTE Rel. 13 (eMTC or LTE-M)
Further development of MTC to eMTC (enhanced MTC). Introduces new type CATM1 devices.
●
3GPP LTE Rel. 13 (NB-IoT)
First dedicated IoT specification, regarded as new radio access technology.
Introduces new type CAT-NB1 devices.
●
3GPP LTE Rel. 14 (eMTC and NB-IoT)
Introduces eMTC widebands and new types CAT-M2 and CAT-NB2 devices.
●
3GPP LTE Rel. 15 (NB-IoT)
Introduces NB-IoT TDD mode in UL, FDD NPRACH formats, early data transmission, NB-IoT wake up signal and scheduling request in uplink for NPUSCH F2.
●
3GPP GERAN(EC-GSM)
Extension in the GSM standard
Overview of the main characteristics
Based onexisting LTE standardnew radio access technology
UE categoryCAT0
Channel bandwidth1.4 MHz180 KHz
Number of RB61
Coverage extension (CE)CE mode A and CE mode BCE level 0, CE level 1 and CE
eMTC (LTE-M)NB-IoT
CAT-NB1
CAT-M1
CAT-M2
CAT-NB2
level 2
LTE features not supported by eMTC or NB-IoT
Consider the following differences between eMTC and LTE/LTE-A.
●
eMTC does not support:
16User Manual 1178.4301.02 ─ 15
–Spatial multiplexing
–Simultaneous PUCCH/PUSCH
–Higher-order modulation schemes
–CSI feedback
–Transmission modes 3, 4, 8 and 10
–PUCCH format 3, 4 and 5
–ACK/NACK bundling multiplexing in TDD
●
eMTC supports:
–2 HARQ processes
–Contiguous resource allocations for UL and DL
●
Among other, NB-IoT does not support:
–Carrier aggregation
–Home eNB, closed subscriber group (CSG)
–Relaying
–Dual connectivity
–MBMS/eMBMS
About the internet of things (IoT)Cellular IoT eMTC and NB-IoT
Required options
Scope of this description
This section gives a brief description of the LTE Rel. 13 and somer Rel. 14 features
that are related to the eMTC and NB-IoT technology. The following section list the subset of features that are covered by the software option R&S SMW-K115/-K143:
●
Chapter 2.2, "About eMTC", on page 18
●
Chapter 2.3, "About NB-IoT", on page 34
For an insight description of the NB-IoT features, refer to:
●
White Paper 1MA266 "Narrowband Internet of Things"
●
Application Note 1MA296 "Narrowband Internet of Things Measurements"
2.1Required options
The basic equipment layout for generating eMTC/NB-IoT signals includes the options:
●
Standard or wideband Baseband Generator (R&SSMW-B10/-B9)
●
Baseband Main Module (R&S SMW-B13) or Wideband baseband main module
(R&S SMW-B13XT)
Optional, option LTE closed loop BS test (R&SSMW-K69)
17User Manual 1178.4301.02 ─ 15
You can generate signals via play-back of waveform files at the signal generator. To
create the waveform file using R&S WinIQSIM2, you do not need a specific option.
To play back the waveform file at the signal generator, you have two options:
●
Install the R&S WinIQSIM2 option of the digital standard, e.g. R&S SMW-K255 for
playing LTE waveforms
●
If supported, install the real-time option of the digital standard, e.g. R&S SMW-K55
for playing LTE waveforms
For more information, see data sheet.
2.2About eMTC
Short summary
eMTC is an extension of the LTE standard.
About the internet of things (IoT)Cellular IoT eMTC and NB-IoT
About eMTC
eMTC main characteristics are:
●
Channel bandwidth splitting into narrowbands
Min channel bandwidth is a narrowband with 1.4 MHz or 6 RBs. 16 narrowbands
can be allocated within the 20 MHz channel bandwidth.
●
Four non-overlapping consequent narrowbands can be grouped into wideband with
5 MHz carrier bandwidth or 24 RBs
●
Two coverage extension (CE) modes: CEModeA and CEModeB
Coverage extension modes
CE modeCE levelDescriptionOptional/mandatory
CEModeA0, 1Supports small number of PUSCH or
PUCCH repetitions
CEModeB2, 3Enables large number of PUSCH or PUCCH
repetitions
Mandatory in eMTC Rel. 13
Optional in eMTC Rel. 13
Overview of the physical signals and channels
Because eMTC is an extension of the LTE standard, it reuses the LTE concept, including reference signals and channels. eMTC, however, does not support MIMO and
MBFSN.
eMTC uses the following signals and channels:
●
UL reference signals: SRS, DMRS
●
DL physical channels:
PDSCH, PBCH, PDCCH, and the new MPDCCH (MTC physical downlink control
channel)
●
UL physical channels:
PUSCH (modulation QPSK, 16QAM, 64QAM), PUCCH, PRACH
18User Manual 1178.4301.02 ─ 15
See:
–Chapter 2.2.5, "PUSCH", on page 29
–Chapter 2.2.6, "PUCCH", on page 32
–Chapter 2.2.7, "PRACH", on page 33
Guard period for narrowband and wideband retunning
According to TS 36.211, an eMTC transmission cannot switch the used narrowband/
wideband immediately but it needs time to retune to the new frequency. This retuning
time is referred as guard time and is defined as number of unused symbols depending
on the channel type and the link direction. In any of the combinations, two symbols are
left unused, see the illustrations in Table 2-1.
Table 2-1: Symbols used as guard period for retuning
Link directionTransitionVisualization on the "Time Plan"
ULPUSCH-to-PUSCH
About the internet of things (IoT)Cellular IoT eMTC and NB-IoT
About eMTC
PUCCH-to-PUCCH
PUCCH-to-PUSCH
PUSCH-to-PUCCH
Related settings
●
" Retuning Symbols"on page 166
2.2.1Physical layer
Narrowbands
In eMTC, a narrowband is defined as a set of six non-overlapping consecutive physical
resource blocks in the frequency domain. The number of narrowbands NNB is calcula-
ted as follows:
NNB = NRB / 6, where NRB is the number of the available resource blocks.
19User Manual 1178.4301.02 ─ 15
Figure 2-1: eMTC narrowbands
About the internet of things (IoT)Cellular IoT eMTC and NB-IoT
About eMTC
NB#= Narrowband number
RB= Resource block number
1= "Channel Bandwidth = 1.4 MHz", NRB = 6, NNB = 1
eMTC transmission is always subframe-wise. That is, the smallest resource that can
be allocated is 1 RB and one subframe.
Related settings
●
Chapter 3.8, "eMTC DL valid subframes and frequency hopping", on page 115
●
"Number of eMTC Narrowbands"on page 162
●
"Valid Subframes"on page 166
Widebands
Four non-overlapping consequent narrowbands can be grouped into wideband with 5
MHz carrier bandwidth or 24 RBs. If the number of narrowband NNB ≥ 4, the number of
widebands NWB is calculated as follows:
NWB = NNB / 4, where NRB is the number of the available resource blocks.
If the number of narrowband NNB < 4, all available resource blocks are allocated to the
same wideband.
Related settings
●
"Wideband Config"on page 163
●
"Number of eMTC Widebands"on page 162
20User Manual 1178.4301.02 ─ 15
2.2.2PBCH
eMTC reuses the PBCH structure of LTE and is hence backward compatible. The
PBCH in eMTC supports merely additional repetitions for enhanced frequency tracking.
A further difference is the PBCH content (i.e. MIB), that is extended with a information
regarding the scheduling of the SIB1-BR paging message.
If enabled, PBCH is repeated in subframe#0 and one additional subframe in all subframes in every 40ms cycle. The additional subframe is subframe#9 for FDD or subframe#5 for TDD.
PBCH repetition is not supported if the occupied bandwidth is 1.4 MHz.
Related settings
●
Chapter 3.10.5, "PBCH channel coding and SIB-BR configuration", on page 145
2.2.3PDSCH
About the internet of things (IoT)Cellular IoT eMTC and NB-IoT
About eMTC
A block of N
scrambling sequence is function of the N
subframes is scrambled with the PDSCH scrambling sequence. The
acc
ID and the N
Cell
PDSCH,abs
.
Where:
●
N
PDSCH,abs
is the number of consecutive subframes that the PDSCH transmission
spans, including the invalid subframes.
●
Invalid are subframes in that the PDSCH transmission is postponed.
According to TS 36.211, N
depends on the CE mode and the frame type as listed in
acc
Table 2-2.
Table 2-2: N
CE modeCE levelFrame type 1Frame type 2
CEModeA0, 111
CEModeB2, 3410
For example on the N
on page 29. N
depending on the CE level and frame type
acc
calculation, see Example "Calculation of N
PDSCH,abs
PDSCH,abs
is calculated similar to N
PUSCH,abs
PUSCH,abs
"
.
PDSCH start subframe
The PDSCH transmission starts two valid subframes after the end of the last repetition
of the scheduling MPDCCH, see Figure 2-4.
Repetition of PDSCH not carrying SIB1-BR
The PDSCH repetition is defined as combination of cell-specific higher-level parameters pdsch-maxNumRepetitionCEmodeA/pdsch-maxNumRepetitionCEmodeB
and the UE-specific parameter PDSCH repetition number. The latter is part of the DCI
formats 6-1A/B or 6-2.
21User Manual 1178.4301.02 ─ 15
About the internet of things (IoT)Cellular IoT eMTC and NB-IoT
About eMTC
TS 36.211 specifies the PDSCH repetition levels for all three DCI format. Table 2-3
show an example of the DCI format 6-1A case.
Table 2-3: PDSCH repetition levels, defined with DCI format 6-1A [TS 36.211]
Higher-level parameter
pdsch-maxNumRepetitionCEmodeA
(cell-specific)
Not configured1, 2, 4, 8
161, 4, 8, 16
321, 4, 16, 32
PDSCH Repetition Number n1 to n4
(UE-specific)
For information on the PDSCH repetitions, if PDSCH carries SIB1-BR, see "System
information MIB"on page 23.
PDSCH hopping
PDSCH hopping is the process where the PDSCH changes the occupied narrowband
on a per subframe basis. The occupied physical resource blocks (PRB) within the narrowband are maintained, merely changed is the narrowband.
Two hopping rules are defined depending on whether the PDSCH carries or not system information SIB1-BR:
●
PDSCH not carrying SIB1-BR
Information on the PRB within a narrowband on that the PDSCH is mapped in the
first subframe is transmitted by the DCI.
The hopping pattern is defined as a function of the absolute subframe number i
and the cell-specific higher-layer parameters N
NB
ch,DL
, N
NB,hop
ch,DL
and f
NB,hop
DL
0
,
where:
–
ch,DL
N
is the number of consecutive subframes during which MPDCCH or
NB
PDSCH stays at the same narrowband before hopping to another narrowband
N
NB,hop
ch,DL
is the number of narrowbands over which MPDCCH or PDSCH
–
hops
f
NB,hop
DL
is the hopping offset, i.e. number of narrowbands between two consec-
–
utive MPDCCH or PDSCH hops
See Example "PDSCH not carrying SIB1-BR hopping"on page 24.
●
PDSCH carrying SIB1-BR
PDSCH transmission is repeated periodically, every 8 radio frames. If nf is the sys-
tem frame number (SFN), a period starts at frames for that nfmod8 = 0.
About the internet of things (IoT)Cellular IoT eMTC and NB-IoT
About eMTC
SFN= System frame number
1= PDSCH period starts at frames for that nfmod8 = 0
2= Period of 8 radio frames
PDSCH #1 to #4 = 4 PDSCH repetitions, configured with the parameter "eMTC > Bitmap > Schedulung
Info SIB1-BR = 1", see Table 2-5.
Within each period, the PDSCH is repeated N
PDSCH
SIB1-BR
times, where the set of
used frames and subframes nsf depends on the channel bandwidth, the cell ID
cell
N
and the frame structure type, see Table 2-4.
ID
Table 2-4: Set of frames and subframes nsf for SIB1-BR [TS 36.211]
Channel
bandwidth
DL
N
≤ 15
RB
DL
N
> 15
RB
SIB1bis
N
PDSCH
400415
411415
400415
411410
800, 140, 15
810, 190, 10
1600, 14, 90, 10, 5
1610, 10, 90, 10, 5
cell
N
mod 2
ID
Frame
structure 1
nf mod 2
Frame
structure 1
n
sf
Frame
structure 2
nf mod 2
System information MIB
Frame
structure 2
n
sf
PDSCH carries the system information SIB1-BR
(SystemInformationBlockType1-BR). The PDSCH allocation that carries the
SIB1-BR block comprises of six contiguous localized RB within a narrowband and is
repeated as defined with the parameter schedulingInfoSIB1-BR-r13.
See:
●
Table 2-5
●
Figure 2-2
Table 2-5: Number of repetitions for PDSCH carrying SIB1-BR [TS 36.213]
Value of schedulingInfoSIB1-BR-r13Number of PDSCH repetitions
0SIB1-BR is not scheduled
1, 4, 7, 10, 13, 164
2, 5, 8, 11, 14, 178
3, 6, 9, 12, 15, 1816
19 to 31Reserved
23User Manual 1178.4301.02 ─ 15
About the internet of things (IoT)Cellular IoT eMTC and NB-IoT
About eMTC
Example: PDSCH not carrying SIB1-BR hopping
Configure for example:
●
"User 1 > 3GPP Release = eMTC CE: A"
●
"Channel Bandwidth = 10 MHz" or "Number of Narrowbands = 8".
●
"eMTC > Narrowband > Number of Narrowbands for Hopping N
●
"eMTC > Narrowband > Hopping Offset f
●
"eMTC > Narrowband > Hopping Interval for CE Mode A N
●
"eMTC > Bitmap > Bitmap Subframes = 10" and "SF#0 to SF#9 = On".
●
"eMTC > Search Space > Max. Repetition of PDSCH for CE Mode A = 32"
●
"eMTC > DCI Configuration > User 1 > DCI format 6-1A > Config > PDSCH Fre-
NB,hop
DL
= 2"
NB
ch,DL
NB,hop
= 4"
ch,DL
= 4"
quency Hopping > On", "Repetition Number = 2" and "Ressource Block Assigment
= 32".
Hence, the n3 value from Table 2-3 is used and "Repetitions of PDSCH = 16".
In this configuration, the first used narrowband is NB#1.
●
"eMTC > Allocations > PDSCH > Num. Abs. SF N
PDSCH,abs
= 16", i.e. one PDSCH
transmission last 16 subframes
●
"eMTC > Allocations > PDSCH > Start Subframe = 3"
Figure 2-3: Example of PDSCH hopping
ABF= Absolute subframe number, counted from the first subframe in SFN = 0.
NB= Narrowband
#0 to #7 = Narrowband number, calculated automatically for the selected channel bandwidth
MPDCCH = One single repetition and "Start Subframe = 0"
NB#1= "Start NB = 1", as set with the DCI field "Ressource Block Assigment".
1=
2=
3=
N
NB,hop
f
NB,hop
N
NB
ch,DL
DL
ch,DL
= 2
= 4
= 4
24User Manual 1178.4301.02 ─ 15
4= PDSCH always starts 2 subframes after the last repetition of the MPDCCH the shared channel
5= "PDSCH Start Subframe = 3" i.e. 2 subframes after the MPDCCH transmission
6= N
Related settings
●
"Narrowbands"on page 118
●
"Max. Repetitions of PDSCH for CE Mode A/B"on page 126
●
"DCI Format 6-1A/6-1B"on page 134
●
Chapter 3.10.6, "PDSCH channel coding and scrambling", on page 148
●
Chapter 3.10.4, "eMTC allocations (PBCH, MPDCCH, PDSCH)", on page 141
2.2.4MPDCCH
The eMTC physical downlink shared channel MPDCCH in eMTC is similar to the LTE
EPDCCH in terms of structure and purpose. In both cases, this control channel carries
scheduling assignments. It is transmitted in an MPDCCH set, mapped to group of
resource elements called ECCEs (enhanced control channel elements) and it can use
localized or distributed transmission scheme. EPDCCH is user-specific but MPDCCH
also includes common search spaces (Type1 and Type2).
is scheduled
= 16
PDSCH,abs
About the internet of things (IoT)Cellular IoT eMTC and NB-IoT
About eMTC
Other than in LTE, in eMTC the MPDCCH set consists of 2, 4, or 6 physical resource
block (PRB) pairs. There is also the additional MPDCCH format 5, see Table 2-6.
Table 2-6: MPDCCH formats and number of ECCEs for one MPDCCH N
MPDCCH formatCase ACase B
021
142
284
3168
432*16*
52412
MPDCCH
[TS 36.211]
ECCE
*) MPDCCH format 4 is supported if distributed transmission is used.
The MPDCCH is transmitted over N
and spans N
MPDCCH,abs
consecutive subframes, including the invalid subframes where
MPDCCH
rep
consecutive valid downlink subframes
the transmission is postponed.
MPDCCH hopping
If frequency hopping is enabled, the narrowband for the MPDCCH transmission
(NB
) in the first subframe is given by higher-layer; it can be different per MPDCCH
start
set. The hopping pattern is defined as a function of the absolute subframe number i
and the cell-specific higher-layer parameters N
NB
ch,DL
0
25User Manual 1178.4301.02 ─ 15
About the internet of things (IoT)Cellular IoT eMTC and NB-IoT
About eMTC
(interval-DLHoppingConfigCommon), N
(mpdcch-pdsch-HoppingNB-r13) and f
NB,hop
(mpdcch-pdsch-HoppingOffset-r13), where N
NB,hop
DL
ch,DL
NB,hop
ch,DL
= 2 or 4 narrowbands.
See Example "PDSCH not carrying SIB1-BR hopping"on page 24.
Search spaces
eMTC UE monitors the following MPDCCH search spaces:
●
Type 0 common search space, if configured with CE Mode A
●
Type 1 common search space, used for paging
●
Type 2 common search space, used for random access (RA)
●
UE-specific search space
The search space defines the MPDCCH candidates that the UE has to monitor. The
UE is expected to decode only the control information on an MPDCCH that is transmitted over ECCEs within the search space the UE monitors.
MPDCCH starting subframe
The MPDCCH starting subframe depends on the used search space and is calculated
similar to the NPDCCH starting subframe, see "Calculating the NPDCCH starting sub-
frame"on page 42.
MPDCCH repetition number
The number of times the MPDCCH is repeated N
the R
●
value and the repetition level r1 to r4, where:
max
R
gives the maximum number of MPDCCH repetitions and is defiend per search
max
MPDCCH
rep
is defined as a function of
space, see Table 2-8 and Table 2-9.
●
Repetition level is set by the DCI field "Subframe Repetition Number" of the corresponding DCI format, see Table 2-7.
Table 2-7: Repetition level r1 to r4 as function of the DCI subframe repetition number field
Rr1r2r3r4
"DCI Subframe Repetition
Number"
Table 2-8: MPDCCH repetition number for Search Space = UE-specific or Type 0/Type 2 Common
R
max
11
212
4124
≥ 8R
r1r2r3r4
max
0123
/8R
/4R
max
/2R
max
max
26User Manual 1178.4301.02 ─ 15
About the internet of things (IoT)Cellular IoT eMTC and NB-IoT
Table 2-9: MPDCCH repetition number for Search Space = Type 1 Common
"User Configuration > User 1 > MPDCCH Config:": "Max. Repetition of MPDCCH
Rmax (User-Specific search space) = 4", "MPDCCH Hopping > On" and "Search
Space Start Subframe = 1".
●
"eMTC > DCI Configuration > User 1 > DCI format 6-1A > Search Space = UESpecific" and " DCI format 6-1A > Config > DCI Subframe Repetition Number = 2".
Hence the r3 value from Table 2-8 is used and "MPDCCH Repetitions = 4".
Figure 2-4: Example of MPDCCH repetitions and PDSCH cross-scheduling (UE-specific search space)
1 = MPDCCH start subframe
2 = MPDCCH Repetitions
3 = PDSCH always starts 2 subframes after the last repetition of the MPDCCH the shared channel is sched-
uled
DCI formats, decoding and content
Table 2-10 gives an overview of the defined DCI formats.
27User Manual 1178.4301.02 ─ 15
Table 2-10: DCI formats
About the internet of things (IoT)Cellular IoT eMTC and NB-IoT
About eMTC
DCI
format
3
3A
6-0AScheduling of PUSCH in one UL cell
6-0BScheduling of PUSCH in one UL cell
6-1AScheduling of one PUSCH codeword in one cell
6-1BScheduling of one PUSCH codeword in one cell
6-2Paging and direct indication-P-RNTIType 1 common
PurposeCE Mode"User x"/ P-
RNTI/ RA-RNTI
As in LTE
Transmission of TPC Commands for MPUCCH and MPUSCH
2 bits and 1-bit power adjustment respectively
Resource allocation type 0
Resource allocation type 2, without TPC and CSI request
Random access procedure initiated by a PDSCH order
Resource allocation type 2
Random access procedure initiated by a PDSCH order
Resource allocation with 1 bit
CE Mode A"User x"UE-specific
CE Mode A"User x"UE-specific
CE Mode B"User x"UE-specific
CE Mode A"User x"
RA-RNTI
CE Mode B"User x"
RA-RNTI
Search space
Type 2 common
Type 0 common
UE-specific
Type 0 common
Type 2 common
UE-specific
Type 2 common
Table 2-11 gives the DCI formats decoding for MPDCCH and PDSCH.