eMBMS Radio Layers

IMPLEMENTATION GUIDELINE
İLKE ALTIN
 eMBMS Radio Layers
The Radio layers for eMBMS implementation is given below in Figure 1. The main changes are in RRC,
MAC, and PHY layers.

Figure 1. eMBMS radio layers.

As specified in the standard, in one radio frame (10ms), there are up to 6 out of 10 subframes can be
allocated to eMBMS services. For FDD (Frequency Division Duplex) LTE, subframes in pre-determined
positions can be assigned for eMBMS transmission as shown in Figure 2. Only 6 subframes can be
used for eMBMS since subframes 0 and 5 carry synchronization signals and broadcast channel, where
subframes 0, 4, 5 and 9 can be used for paging depending on the defined paging cycle. Which of the 6
possible subframes are really used for MBMS is indicated by a bitmap. In terms of four radio frames
being configured this bitmap is 24 bit long, otherwise 6 bit.

Figure 2. eMBMS available subframes

RRC
Background
Similar to system information in unicast transmission, eMBMS control information are transferred
directly from RRC to MAC sublayer via BCCH and MCCH logical channel as described in Figure 1.
The System Information Block Type 2 (SIB Type 2) carries all relevant information about common and
shared channels in LTE. MBSFN-SubframeConfig defines which radio frames contain subframes, that
can be used for MBMS. These so called MBSFN subframes can be used by ALL MBSFN areas. First, the
radio frame allocation period and a radio frame allocation offset are defined to determine the
periodicity, and the offset of the radio frames occur that contain MBSFN subframes. Further,
subframe allocation mode is defined within SIB Type 2. It could be one radio frame or four
consecutive radio frames that allow MBSFN subframes. As indicated in the previous section,
maximum 6 subframes out of a radio frame can be used for MBMS.

Figure 3. MBMS Frame and Subframe Configuration

The System Information Block Type 13 (SIB Type 13) provides information regarding MBSFN areas
such as MBSFN identity (MBSFN ID), non-MBSFN region length (1, 2 OFDM symbols), and MCCH
configuration. MCCH configuration provides information on the repetition period for the MCCH, the
MCCH offset as well as the actual subframe, where the MCCH is transmitted in as well as the MCS
used for the MCCH. For the MCCH four modulation coding schemes are allowed: MCS index 2 (QPSK),
7 (QPSK), 13 (16QAM), 19 (64QAM).
 Figure 4. MCCH Frame and Subframe Configuration

In addition to that, MCCH configuration of SIB 13 provides MCCH Modification Period information.
This period determines the time to wait before applying any change to MCCH.

Figure 5. MCCH Subframe Configuration and Modification Notification

The MCCH message always defines one MBSFN area and carries the Area Configuration information.
Using this information, MBMS services are scheduled in the MBSFN area.

The entity that controls the general resource placement in MCCH is the Common Subframe
Allocation. All MCHs that are part of the same MBSFN area occupy a pattern of MBSFN subframes
known as the Common Subframe Allocation (CSA). The CSA is defined by a CSA period, a radio frame
period, radio frame offset, and a subframe allocation bitmap for different channels. These subframes
are allocated for the MBSFN area from the subframes that are already reserved for eMBMS by SIB 2
message.

The entity that controls the resource allocation per MCH or PMCH is the PMCH Information List. For
each PMCH, the MCH Scheduling Period (MSP) is sent in this entity. MSP is the period of the MCH
Scheduling Information (MSI) message. Second, this entity contains the end subframes for each MCH.
If this value is n for MCH m, at the nth MBMS subframe of the CSA period, the MCH m transmission is
stopped. Finally, MCS information for data is sent in this entity for each PMCH.

In Figure 6, a MCH placement is shown with a radio frame allocation of an identified four radio frame
bitmap. This allocation is repeated with a period of 8 radio frames. The CSA period of 16 radio
frames, and the PMCH end subframes are given as 8, 14, 19 for MCH 1, 2, and 3 respectively. It can
be observed that in a single CSA period, subframes 0-8 are reserved for MCH 1, subframes 9-14 are
reserved for MCH 2, and subframes 15-19 are reserved for MCH 3.

The first element of the MCH is an MSI if the MSP period has elapsed. MCCH is also scheduled using
the same resources, with its own periodicity, which can be observed.

Figure 6. MCH placement according to MCCH and System Information Blocks

Implementation
Bearer Configuration: RRC configures the data bearers for eMBMS services at PDCP and RLC sublayer
using the parameters sent by MCE.

SIB 2: MBSFN-SubframeConfig defines which radio frames contain subframes, that can be used for
MBMS. MBSFN subframes are indicated by a bitmap for the one or four radio frames that are
configured. In terms of four radio frames being configured this bitmap is 24 bit long, otherwise 6 bit.

SIB 13: MCCH repetition period, and MCCH repetition offset determines the frames that MCCH
occurs. MCCH subframe allocation bitmap gives the subframe that MCCH will be sent. MCS setting (2,
7, 13, 19). for MCCH is also selected here. Finally MCCH modification period is set in this message.

MCCH: commonSF-Alloc defines the CSA period, and the resource mapping for the MBSFN area.
There is one point to be clarified here: Why is the subframe configuration of the MCCH created as a
list? Each MCCH shall correspond to a single MBSFN Area. PMCH-Info of each PMCH defines
subframe that the allocation ends, and the MSI period.

PDCP
Background
PDCP is not used for eMBMS, therefore the PDCP is configured in transparent mode. PDCP
functionalities such as Robust Header Compression, and RAN security are not applied for MBMS.

Implementation
Transparent mode: Protocol Data Unit (PDU) is handed directly to RLC in eNB without any PDCP
related header and trailer appended.

RLC
Background
RLC layer uses the unacknowledged mode for both eMBMS user and control plane. Since there is no
feedback for the broadcasting operation, this is expected.

Implementation
Unacknowledged mode: These RLC instants are responsible for segmenting the received SDU into
smaller packets depend on the size demanded by MAC. They also add few bits for RLC header in
these packets and then send them to MAC via MTCH and MCCH logical channels in the transmitter
side.

Counter reset: At the beginning of the modification period for MCCH and scheduling period of MTCH,
the corresponding VT(US) counters shall be reset. To implement this, the current subframe number
and radio frame number shall be known. In addition to this, the periodicity of the aforementioned
events shall be calculated.
MAC
Background
The subframes are configured by the RRC layer, and the configuration is sent via the MCCH channel
of RLC layer. The corresponding data is sent via the MTCH of RLC layer.

A single MCH may contain multiple services of one MBSFN area, each synchronized in time and
frequency. In all of the eNBs of one MBSFN area the same MCH is created and broadcast.

The radio frames and the subframes that are allocated in a MBSFN area is uniquely arranged by MCE.
This common pattern of the MCH of each cell of the MBSFN area is called the Common Subframe
Allocation (CSA) that is carried in SIB 2 message. The CSA pattern is periodic with a predefined CSA
period in SIB 2 message also.

Transmission of a specific MCH follows the specific MCH subframe allocation (MSA). The MSA is
periodic with MCH Scheduling Period (MSP). At the beginning of each MSA, the MCH Scheduling
Information (MSI) is sent via a MAC control element. The MSI indicates which subframes are used for
a certain MTCH in the upcoming scheduling period. If a smaller number than allocated to an MCH is
required by the MTCH(s), the MSI indicates the last MCH subframe to be used for this particular
MTCH (MSA end in Figure 15.5).

The different MCHs are transmitted in consecutive order within a CSA period – e.g., all subframes
used by MCH 1 in a CSA are transmitted before the subframes used for MCH 2 in the same CSA
period.

Several services requiring the same QoS class are transported within the same MCH, resources
allocation for a particular service is performed as follows. Each service corresponds to a Multicast
Traffic Channel (MTCH) and the eNB multiplexes these MTCHs at MAC layer. The scheduling
information is provided repeatedly in a MAC control element called MCH Scheduling Information
(MSI).

Figure 7. eMBMS MCH in Radio Frame and Subframe structure

MAC layer shall schedule the eMBMS frames and subframes according to the MSI. The logical IDs and
the corresponding subframe to stop the specific MTCH is given in the MSI information.

7 6 5 4 3 2 1 0
LCID 1 Stop MTCH 1

Stop MTCH 1
LCID 2 Stop MTCH 2

Stop MTCH 2
LCID 3 Stop MTCH 3

Stop MTCH 3
LCID n Stop MTCH n

Stop MTCH n
The logical ID values are given in the table below.
Index LCID values
00000 MCCH (see note)
00001-11100 MTCH
11101 Reserved
11110 MCH Scheduling Information or
Extended MCH Scheduling
Information
11111 Padding
NOTE: If there is no MCCH on MCH, an
MTCH could use this value.

Implementation
Mapping: Control information and user data packets are multiplexed into different transport
channels before being transfered to physical layer. The MCCH and MTCHs will be mapped onto
different MCHs at this sublayer regarding their services.

MAC CE: Depending on the number of MCH channels (eMBMS service groups), one or more MSI
control elements (CE) are periodically created for each MCH channel. Each MAC CE contains the
resource allocation information of services in the corresponding group such as Logical Channel
IDentity (LCID) and the last position of each service.

Change Notification: MAC shall notify the UE of any MCCH changes using DCI format 1C.

Scheduling: A new scheduling unit for multiplexing MSI, MCCH and MTCHs shall be implemented. A
single MAC Protocol Data Unit should carry data of only one MCH, which means there could be
several services (MTCHs) that have the same quality requirement and maybe MCCH plus MSI CE in
one MAC packet for eMBMS. The scheduling should be modified so that it will not affect the unicast
traffic. The eMBMS scheduling function in MAC uses the parameters sent by RRC to identify which
subframes carry eMBMS data. If a subframe is reserved for eMBMS, no unicast data can be
scheduled except the notification for uplink assignment which is transported on PDCCH in the two
first OFDM symbols of that subframe. MAC will create the control element MSI or get the MCCH
control information and MTCH user data from RRC and RLC regarding the multiplexing – if periodic
MSI shall be sent, then MSI is sent. The Transport Block Size (TBS) as well as Modulation Coding
Scheme (MCS) shall be calculated afterwards. Finally, the MAC header shall be generated and added
to the Service Data Unit (SDU) to complete the PDU and send it to PHY through MCH transport
channel. It is worth noting that the Hybrid Automatic Repeat Request (HARQ) is not used in eMBMS.
PHY
Background
When a subframe is used for simulcast transmission, all the resource blocks are configured to
support MCH. Other LTE downlink transport channels like DLSCH, PCH and BCH cannot be mapped to
this subframe. However, the first two symbols convey reference signals, and PDCCH to have the
same structure as any subframe of the LTE radio interface to support scheduling of other subframes,
and ther control related information – including some control information related to MBMS. The
resource block for MBSFN subframe comprises then two parts: the standard unicast part and the
MBSFN part. The Cyclic Prefix (CP) used by the MBSFN part is longer in time and is called extended
CP. The Unicast part uses the same CP as any non-MBSFN subframe would use, therefore there might
be a hole in the subframe.

Figure 8. MBMS subframe resource block structure

MCH is transmitted by means of MBSFN from the set of cells that are part of the corresponding
MBSFN area. Thus, as seen from the terminal point of view, the radio channel that the MCH has
propagated over is the aggregation of the channels of each cell within the MBSFN area. For channel
estimation for coherent demodulation of the MCH, the terminal can thus not rely on the normal cell-
specific reference signals transmitted from each cell. Rather, in order to enable coherent
demodulation for MCH, special MBSFN reference symbols are inserted within the MBSFN part of the
MBSFN subframe. These reference symbols are transmitted by means of MBSFN over the set of cells
that constitute the MBSFN area – that is, they are transmitted at the same time–frequency position
and with the same reference-symbol values from each cell. Channel estimation using these reference
symbols will thus correctly reflect the overall aggregated channel corresponding to the MCH
transmissions of all cells that are part of the MBSFN area.

Figure 9. MBMS Reference Signals

MBSFN reference signals shall only be transmitted in subframes allocated for MBSFN transmissions.
MBSFN reference signals are defined for extended cyclic prefix only, and they are transmitted on
antenna port 4. MBSFN reference signals have a tighter spacing in the frequency domain due to the
frequency-selective nature of the radio channel.

Figure 10. MBMS Reference Signal Placement

The initialization sequence for the MBSFN reference signal pattern depends on MBSFN identity, in
contrast to the cell-specific reference signals that depend on the physical cell identity. The MBSFN
Identity is provided by System Information Block Type 13. In the equations below, ns is the slot
number, and l is the time domain index (symbol number).

The scrambling for the PMCH is also based on the MBSFN identity.

Implementation
At physical layer, most of PHY procedures for eMBMS are the same with those for unicast downlink
transmission.

Scrambling: There is a difference in calculating the initial value of scrambling sequence for eMBMS

MCS: Three modulation schemes (QPSK, 16QAM and 64QAM) are available for PMCH which is the
same as PDSCH. Only four MCS (2, 7, 9 and 13) values can be used in the subframe carrying MCCH or
MSI control element, while with subframe transporting eMBMS data, all MCS values are eligible.

Reference Signals: The biggest difference in PHY for eMBMS is the reference signals which are
generated for channel estimation purpose. These MBSFN reference signals shall be transmitted at
MBSFN region on antenna port 4 with a special pattern given in the previous section and its
sequence generating is also defined in the same document. At MBSFN subframe, the cell-specific
reference signal can be generated at non-MBSFN region (2 first symbols). The PMCH can only be
transmitted at MBSFN region in MBSFN subrame and the extended cyclic prefix should be used.
References
[1] LTE Release 9 Technology Introduction Whitepaper. M Kottkamp, A Rossler, J Schlienz, J Schütz
Rohde & Schwarz, 12/2011.

[2] Anis, Muhammad Moiz, Xavier Lagrange, and Ramesh Pyndiah. Overview of evolved Multimedia
Broadcast Multicast Services (eMBMS), 2016.

[3] http://www.sharetechnote.com/html/Handbook_LTE_MBSFN.html

[4] Nguyen, Ngoc-Duy, et al. "Implementation and validation of multimedia broadcast multicast
service for LTE/LTE-advanced in OpenAirInterface platform." Local Computer Networks Workshops
(LCN Workshops), 2013 IEEE 38th Conference on. IEEE, 2013.

[5] Network, Evolved Universal Terrestrial Radio Access. "General aspects and principals for
interfaces supporting Multimedia Broadcast Multicast Service (MBMS) with E-UTRAN (Release 10),
3GPP TS 36.440." V10 1 (2011): 11.

[6] Calabuig, Jorge, et al. "Al-fec for streaming services in lte e-mbms." EURASIP Journal on Wireless
Communications and Networking 2013.1 (2013): 73.

[7] Christodoulou, Louis, et al. "Adaptive subframe allocation for next generation multimedia delivery
over hybrid LTE unicast broadcast." IEEE Transactions on Broadcasting 62.3 (2016): 540-551.

[8] Dahlman, Erik, Stefan Parkvall, and Johan Skold. 4G: LTE/LTE-advanced for mobile broadband.
Academic press, 2013.