EMBMS Technical Discussion Session - I - April'17
EMBMS Technical Discussion Session - I - April'17
1.Introduction
2.eMBMS Architecture, Services & Area
Definitions
3.eMBMS Test Scenarios
4.Parameters
5.eMBMS Service Continuity SIB15
6.MOP for eMBMS Testing
IP Unicast End
1 Device
2 Router
3 End
Serv
er
Device
Router
Router
Router End
Router Device
IP Multicast End
Device
Router
1 End
Serv
er
Device
Router
Router
Router End
Router Device
2016 Samsung Electronics. All Rights Reserved. 11
What is eMBMS ?
eNodeBs:
To support eMBMS, eNB is upgraded to support SYNC protocol with BMSC. The eNB
joins IP multicast, terminates the multicast control channel and indicates multicast
session start /stop to mobile devices.
Broadcas Multicast MBMS Unicast
BMSC
UE t eNB
GW
2016 Samsung Electronics. All Rights Reserved. 15
eMBMS Interfaces
MCE-MME Interface (M3):
Allows for MBMS Session Control Signaling (e.g, MBMS Session Start/Stop)
SGi-mb/SG-mb:
It is the reference point between BM-SC and MBMS GW function for MBMS data
delivery.
Sm
It is the reference point for the control plane between MME and MBMS GW.
JIO TV
JIO
Cinema
MBMS Service
Area#1
The geographic area or a set of cells that broadcast the same MBMS service. MBMS Service Areas
can be overlapped.
MBMS Synchronization Area
A set of eNBs that ofer MBMS service by using the same frequency and bandwidth in the same
PLMN ID, and SFN is synchronized.
MBSFN Area
A set of cells that have the same eMBMS scheduling in terms of time and frequency. UE can
combine eMBMS signal from the cells in the same MBSFN Area. The same MBSFN Area cannot
cover multiple MBSFN synchronization area.
One cell support up to 8 MBSFN Areas and 256 MBMS Service Areas as per 3GPP standard.
2016 Samsung Electronics. All Rights Reserved. 21
MBMS Service Area
MBMS Service Area is defined as a geographical area that
provides the same MBMS service.
MBMS Service areas can be overlapped geographically. When
BMSC initiates MBMS Session Start, it decides MBMS Service
Areas where it wants to broadcast MBMS data for the session.
MBMS Service Area ID identifies a group of cells within a PLMN,
which is independent of the physical location of the cells.
MBMS Service Area Design Rules:
MBMS Service Area ID must be unique within a PLMN
MBMS Service Areas can be overlapped
Maximum 256 MBMS SA IDs are allowed per cell
One MBMS Service Area can support multiple MBMS channels at the same
time
MBMS Service Area ID ranges between 0 and 65535 (Two octets long)
The value 0 has a special meaning; it shall denote the whole PLMN as the
MBMS Service Area (Ref: 3GPP TS23.003, TS29.061, TS23.246)
Note:
MBMS Service Area is not meant to do contents-synchronization between all
the cells that belong to the service area. (MBSFN Area do that)
Note:
MBSFN Synchronization Area ID can be configured per eNB
MBSFN Synchronization Area shall not overlap each other
SA ID
=11~32
SA ID SA ID =1010~8880
=1
Zone 1 Mumbai
Circles: 9
BMSC: 5
hi) MCE: 25
Del
(
2
one
Z
1
o n a i)
e Zone 2 Delhi
Z mb
u Circles: 13
(M
BMSC: 3
MCE: 22
RFAP=n1, RFAP
SFN=0 SFN=1 SFN=2 SFN=3 SFN=4 SFN=5 SFN=6 SFN=7
Offset=0
RFAP=n2, RFAP
SFN=0 SFN=1 SFN=2 SFN=3 SFN=4 SFN=5 SFN=6 SFN=7
Offset=0
RFAP=n4, RFAP
SFN=0 SFN=1 SFN=2 SFN=3 SFN=4 SFN=5 SFN=6 SFN=7
Offset=0
RFAP=n4, RFAP
SFN=0 SFN=1 SFN=2 SFN=3 SFN=4 SFN=5 SFN=6 SFN=7
Offset=1
Interferen
ce
MBSFN AREA
#1
maxSubframeNum=4 SFN=0 SFN=1 SFN=2 SFN=3 SFN=4 SFN=5 SFN=6 SFN=7
,
MBSFN
RFAP=n2,AREA
RFAP No
Offset=0
Interleaving resource
Collision allocation can avoid the interference.
#2
maxSubframeNum=4 SFN=0 SFN=1 SFN=2 SFN=3 SFN=4 SFN=5 SFN=6 SFN=7
,
RFAP=n2, RFAP
Offset=1 0 1 2 3 4 5 6 7 8 9
D S U D D D S U D D
Both MCE#1 and MCE#2 must be configured to have the same resource
allocation pattern for MBSFN AREA #1. And, they must command the same
session start 0time
1 2 for
3 4the
5 eNBs,
6 7 8 which
9 requires almost same delay between
D S U D D D S U D D
each
MCE #1MCE and BMSC.
maxSubframeNum=2
, SFN=0 SFN=1 SFN=2 SFN=3 SFN=4 SFN=5 SFN=6 SFN=7
RFAP=n1, RFAP
Soft
Offset=0
MCE #2 Combining
maxSubframeNum=2
, SFN=0 SFN=1 SFN=2 SFN=3 SFN=4 SFN=5 SFN=6 SFN=7
RFAP=n1, RFAP
Offset=0 0 1 2 3 4 5 6 7 8 9
D S U D D D S U D D
At Physical Layer, Turbo Codes are used (Physical Layer- Error Coding
for protecting against corruption) and at Application Layer (For Packet
Loss protection), we use various coding techniques: RS (Reed-
Solomon), Raptor, LDPC.
While normal CP is suitable for urban environment and high data rate
applications, extended CP is for Multimedia Broadcast Multicast
Service (MBMS) and very large cell scenarios with large delay spread.
Extended CP is defined in 15kHz subcarrier spacing and 7.5kHz (not
supported) subcarrier spacing. The duration of extended CP is 16.7 us
for 15 kHz subcarrier spacing and 33.3 us for 7.5 kHz subcarrier
spacing. These durations are equivalent to the distances of 5km and
10km (whereas Normal CP is equivalent to distance ~ 1.4 to 1.6 km)
The MBSFN RSs are spaced more closely in the frequency domain than
for the non-MBSFN transmission, reducing the separation to every
other subcarrier instead of every sixth subcarrier. This improves the
accuracy of the channel estimation that can be achieved for the longer
delay spreads.
MCE and MBMS-GW and BMSC are required. MME and LSM to support
eMBMS
The maximum allowed M2 session start request for MCE to process is
10 request per second, when 3000 eNB is connected to one MCE.
8 MBSFN Areas per Cell
eNB cannot store MBMS data more than 20 seconds due to the
limitation of bufer
-121.36 -0.51
Exit 156 85.71% (Blank)
Buffering (-116.06) Buffering (3.82)
2
41.67
Entry 156 -116.16 4.60
(Buffering)
26.15
-120.74 -0.38
Exit 156 (Buffering)
Buffering (-114.60) Buffering (5.05)
73.91% (Blank)
3
18.57%
Entry 156 -113.77 7.02
(Buffering)
Buffering
Buffering was observed with decrease in RSRP (< -115) and SINR (< 5) along with increase in
PMCH BLER. Also decrease in MAC eMBMS bytes observed during buffering.
First Snap shows eMBMS starts with High Buffering along with High PMCH BLER.
Total bytes transferred is also very less during High BLER scenario.
2016 Samsung Electronics. All Rights Reserved. 55
RB Usage, MCS Comparison
Last 2 columns shows MCS comparison between eMBMS and Unicast session. It clearly shows that buffering
starts when PMCH BLER gets high. Also at that time we can see Unicast MCS dropping below 14.
RB usage (incl. 0) shows usage is approx. 20 RBs with 2 sub-frames configured in our network.
eMBMS Session
FTP Download
at same time
Voice Call
Video Call
During eMBMS Session, voice and video call was received.
At that time session got temporarily suspended and eMBMS MAC bytes
transferred and PMCH throughput was zero.
2016 Samsung Electronics. All Rights Reserved. 59
Incoming VoLTE Call Message Flow
eMBMS Session
VoLTE Call
eMBMS Session
Resumed
UE was in connected mode, so during incoming voice call, RRC connection reconfiguration
is triggered to add the QCI-1 bearer
In RRC Connection Reconfiguration message, we can see the eps-Bearer Identity =8 which is
for QCI-1.
eps-Bearer Identity to QCI mapping can be checked from Activate Dedicated EPS bearer
2016 Samsung Electronics. All Rights Reserved. context request 61
VoLTE: Bearer Activation
Video Call
UE was in connected mode, so during incoming video call, RRC connection reconfiguration
is triggered to add the QCI-2 & QCI-1 bearer
QCI-2
QCI-1
Once RRC Connection Reconfiguration is triggered, we can see QCI-2 & QCI-1 Bearer Activation and on
disconnection, bearer deactivation.
Once the bearers are deactivated, we can see eMBMS services resuming back.
2016 Samsung Electronics. All Rights Reserved. 64
Scenario 5: Outgoing Voice/Video Call (Background)
with eMBMS Session (Foreground)
QCI-1
Bearer
QCI-2
Bearer
1. VoLTE Call was originated from UE and simultaneously after some time, eMBMS session was started. Called Party
could still hear the conversation from Calling Party. Both the services were working fine simultaneously.
2. Video Call was originated from UE and simultaneously after some time, eMBMS session was started. Called Party
could
could still
still hear
hear the
the voice
voice and
and see
see the
the video
video from
from Calling
Calling Party.
Party. Both
Both the
the services
services were
were working
working fine
fine simultaneously.
simultaneously.
** Note: During both the sessions, volume of the eMBMS service was very low which was automatically set by the APP.
2016 Samsung Electronics. All Rights Reserved. 65
Scenario 5: L3 Messages- Voice Call with
eMBMS
QCI-1
Bearer
activation
QCI-1 & 2
Bearer QCI-2
activation
QCI-1
QCI-1 & 2
Bearer
eMBMS Service
deactivation running with Video
Call
Site with
different
MBSFN/Sync
Area
mbsfnareaconfigurati
on
SIB2
SIB1
3
eMBMS equipped
case
No eMBMS
Info
eMBMS
Unequipped case
eMBMS
Services
being used
eMBMS
SIB15 Interest
Indication
EARFCN
EARFCN having
having eMBMS
eMBMS and
SA List
eMBMS
Interest
Indication
Inter-
Frequency
HO
eMBMS
Services
being used
eMBMS
Services
being used
Inter-Frequency
HO from 2300-850
when RSRP went
below -90 dBm even
though the APP was
running on UE
Cell
reselection
from EARFCN
38800 to 1234
due to IMLB
Cell
reselection
from EARFCN
38800 to
39350 due to
IMLB
If the UE using
eMBMS ser-vice
transit to Idle mode,
eNB set the dedicated
prio-rity (using Idle
mobility) of the
eMBMS frequency to
the high ranking in
the RRC Connection
Release msg.
eMBMS
running on
UE, so
EARFCN
given
highest
priority
eMBMS running on UE
No
messages
for eMBMS No eMBMS
(eMBMS running on
App UE,
closed) So no
priority in
release
message