eNB-MCE Functions, Parameters & Statistics - 20140626 PDF

eNB/MCE functions,
parameters & statistics
June 26 2014
Table of contents
 eMBMS functional diagrams

 eMBMS Channels and signals
 eMBMS scheduling
 eMBMS synchronization
 Session procedures
 MCE Redundancy
 Service Continuity
eMBMS overall function blocks
 eMBMS scheduling block: RLC/MAC scheduling and MTCH/MCCH/P(MCH) control
 Resource allocation block: MBSFN subframe allocation pattern generation
 M2AP/M3AP control block: M2 and M3 message processing
 M2AP control block: M2 message processing
 Session control block: Session admission control

2014 © Samsung Electronics 3
Embms Channels and signals
4
eMBMS channels structure 1/2
 PMCH is used to transfer MCH transport channel that multiplexes MCCH signal
channel and MTCH logical channel .

eMBMS channels structure 2/2
 MCH is RLC-UM mode, no HARQ support

eMBMS related signals and messages
 SYSTEM INFOMRATION BROADCAST signals
 SIB2 : Indicate MBSFN subframe patterns for each MBSFN area
 SIB3 : Indicate neighbor cell MBSFN configuration
 SIB13: Indicate MCCH scheduling information
 SIB15: Indicate SAI of the current and neighbor carrier frequency
 SIB16: Indicate UTC time
 RRC messages over MCCH

 RRC MBMSCountingRequest message
 RRC MBMSInterestIndication message
 RRC MBSFNAreaConfiguration message

UE operations
 Acquire SIB(2,13), SIB15(optional), SIB16 (optional)

 Right after SIB13, The UE applies the MCCH information
acquisition procedure to acquire the MBMS control information
 Acquire PMCH

eMBMS scheduling
9
Session admission control function
Check available MTCH/PMCH channels
TMGI=1111 TMGI=1111
TMGI=1111
Service Area= 1, Service Area= 1, 2
Service Area= 1, 2
2
GBR= 1.5 Mbps GBR= 1.5 Mbps BM-SC
MCE GBR = 1.5 Mbps
Multicast IP addr = ……
Multicast IP addr
100.200.1.2
= 100.200.1.2
……
……
Session start request Session start request
MME MBMS GW
 Once upon received M3 Session start message, MCE runs resource allocation
function
 If physical/logical resource is limited due to previous resource allocation, the newly

requested session will be rejected

Resource Allocation Function (1/4)
 Physical Resources shall be allocated for each MBSFN Area
 maxSubframeNum
— This limits the maximum number of sub-frames per radio frame which are used for eMBMS. This
value must be 2 in the RJIL network.
— MCE decides the number of sub-frames based on the aggregate bit rate required by MBMS
bearers. As a result, MCE generates subframeAllocation pattern(oneFrame) to be broadcast(SIB2)
 RFAP : Radio Frame Allocation Period (n1, n2, n4, n8, n16, n32)
 RFAP Offset : Radio Frame Allocation Offset (0..7)
 This information is broadcast through SIB2 and MCCH message
1 Radio Frame = 10ms

 Available Resources in UL/DL Configuration #2 0 1 2 3 4 5 6 7 8 9
D S U D D D S U D D
 RFAP and RFAP Offset
RFAP=n1, RFAP Offset=0 SFN=0 SFN=1 SFN=2 SFN=3 SFN=4 SFN=5 SFN=6 SFN=7

Resource Allocation Function(2/4)
 Throughput (20MHz BW)
 1 Subframe per 10ms (Kbps)

MCS 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28
PHY 270 350 450 560 710 860 1000 1200 1300 1500 1500 1700 1900 2200 2500 2800 3000 3000 3200 3600 3800 4300 4600 5000 5400 5600 6100 6300 7400
RLC 261 341 441 551 701 851 991 1191 1291 1491 1491 1691 1891 2191 2491 2791 2991 2991 3191 3591 3791 4291 4591 4991 5391 5591 6091 6291 7391
APP 254 331 428 535 680 826 961 1155 1252 1446 1446 1640 1834 2125 2416 2706 2900 2900 3094 3482 3676 4161 4452 4839 5227 5421 5906 6100 7166
FEC 204 265 343 428 544 661 769 924 1002 1157 1157 1312 1468 1700 1933 2165 2320 2320 2476 2786 2941 3329 3562 3872 4182 4337 4725 4880 5733
 2 Subframes per 10ms (Kbps)

MCS 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28
PHY 550 710 900 1100 1400 1700 2000 2400 2700 3100 3100 3400 3900 4500 5000 5600 6000 6000 6500 7200 7700 8600 9200 10100 10900 11300 12200 12600 14900
RLC 537 697 887 1087 1387 1687 1987 2387 2687 3087 3087 3387 3887 4487 4987 5587 5987 5987 6487 7187 7687 8587 9187 10087 10887 11287 12187 12587 14887
APP 521 676 860 1054 1345 1636 1927 2315 2606 2993 2993 3284 3769 4351 4836 5417 5805 5805 6290 6969 7453 8326 8908 9780 10556 10944 11816 12204 14434
FEC 417 541 688 844 1076 1309 1542 1852 2085 2395 2395 2628 3016 3481 3869 4334 4644 4644 5032 5576 5963 6661 7127 7824 8445 8756 9453 9764 11548

MCS 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28
PHY 820 1000 1300 1700 2100 2600 3000 3600 4100 4700 4700 5200 5800 6800 7500 8400 9000 9000 9700 10800 11600 13000 13900 15100 16300 17000 18300 18900 22300
RLC 803 983 1283 1683 2083 2583 2983 3583 4083 4683 4683 5183 5783 6783 7483 8383 8983 8983 9683 10783 11583 12983 13883 15083 16283 16983 18283 18883 22283
APP 779 954 1244 1632 2020 2505 2893 3474 3959 4541 4541 5026 5607 6577 7255 8128 8710 8710 9388 10455 11231 12588 13460 14624 15787 16466 17726 18308 21605
FEC 624 764 996 1306 1616 2004 2315 2780 3168 3633 3633 4021 4486 5262 5804 6503 6968 6968 7511 8364 8985 10071 10768 11700 12630 13173 14181 14647 17284

MCS 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28
PHY 1100 1400 1800 2200 2800 3400 4000 4800 5500 6200 6200 6900 7800 9000 10000 11200 12100 12100 13000 14500 15500 17300 18500 20200 21800 22700 24400 25200 29800
RLC 1079 1379 1779 2179 2779 3379 3979 4779 5479 6179 6179 6879 7779 8979 9979 11179 12079 12079 12979 14479 15479 17279 18479 20179 21779 22679 24379 25179 29779
APP 1047 1337 1725 2113 2695 3277 3858 4634 5313 5991 5991 6670 7542 8706 9675 10839 11711 11711 12584 14038 15008 16753 17916 19565 21116 21988 23637 24412 28872
FEC 838 1070 1380 1691 2156 2622 3087 3708 4251 4793 4793 5336 6034 6965 7740 8672 9369 9369 10068 11231 12007 13403 14333 15652 16893 17591 18910 19530 23098

 Interleaving Resource Allocation between Adjacent MBSFN Areas
 When two Adjacent MBSFN Areas have the same eMBMS resource allocation pattern, the
broadcast channels will collide at the boarder and results in data decoding errors.
MBSFN AREA #1
MBSFN AREA #1 MBSFN AREA #2 MBSFN AREA #2
Interference
 Interleaving resource allocation can avoid the interference.
MBSFN AREA #1
maxSubframeNum=4, SFN=0 SFN=1 SFN=2 SFN=3 SFN=4 SFN=5 SFN=6 SFN=7
RFAP=n2, RFAP Offset=0
No Collision
MBSFN AREA #2
0 1 2 3 4 5 6 7 8 9
D S U D D D S U D D

 Inter-MCE Coordinated Resource Allocation
 A large MBSFN Area(e.g. Delhi or Mumbai) requires multiple MCEs to support the same
area. All of the cells shall be contents-synchronized even if they belong to different MCEs.
• All eNBs in the area must be connected to the same

MBSFN AREA #1 MBMS-GW and BMSC.
• Both MCEs are recommend to be located in the same
office with MME and BMSC to minimize the delay.
MCE#1 MCE#2
MBMS GW BMSC
 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 time for the eNBs,
which requires almost same delay between each MCE and BMSC.
0 1 2 3 4 5 6 7 8 9
D S U D D D S U D D
MCE #1
Soft Combining
MCE #2
0 1 2 3 4 5 6 7 8 9
D S U D D D S U D D

Common Subframe Allocation
1 Radioframe : 10ms
SFN 0 SFN 8 SFN 16 SFN 24 SFN 32

CSAP(Common Subframe Allocation Period) : 320ms
 Common Subframe Allocation: It indicate subframes allocated to the MBSFN area
 Common Subrame Allocation Period: It defines the number of radio frames with in
which the allocated subframes are to be divided between the subsequent list of
PMCH.
 The subframe allocation repeat within the period which can be configured with a
value 4, 8, 16, 32, 64 ,128, 256 RF

Radio Frame Allocation Period (RFAP)
1 Radioframe : 10ms
RFAP : 80ms RFAP : 80ms RFAP : 80ms RFAP : 80ms RFAP : 80ms
 System Frame Number (SFN) mod Radio Frame Allocation Period (RFAP) = offset
1 Sub-frame : 1ms
1 Radioframe : 10ms

Example
1 Radioframe : 10ms
RFAP : 80ms RFAP : 80ms RFAP : 80ms RFAP : 80ms RFAP : 80ms
1 Sub-frame : 1ms 1 Sub-frame : 1ms 1 Sub-frame : 1ms 1 Sub-frame : 1ms 1 Sub-frame : 1ms
1 Radioframe : 10ms 1 Radioframe : 10ms 1 Radioframe : 10ms 1 Radioframe : 10ms 1 Radioframe : 10ms
PMCH 0 : MBMS Bearer 1,

 The maximum available MBSFN subframes per common
PMCH 1 : MBMS Bearer 2
PMCH 2 : MBMS Bearer 3

subframe allocation period is 1536

MCH Scheduling Period (MSP)
MSP MSP
MSI MCCH MTCH MSI MCCH MTCH
LCID 1 Stop MTCH 1 Oct 1
Stop MTCH 1 Oct 2
LCID 2 Stop MTCH 2 Oct 3
Stop MTCH 2 Oct 4
...
LCID n Stop MTCH n Oct 2n-1
Stop MTCH n Oct 2n
 MSPs are RF8, RF16, RF32, RF64, RF 128, RF 256, RF 512, RF 1024, rf16, rf32, rf64, rf1
28, rf256, rf512, rf1024 rf8, r
MCCH scheduling
 The MCCH is broadcast during radio frames which satisfy:
 SFN mod MCCH Repetition Period = MCCH Offset
 MCCH Repetition periods are 32,64, 128 or 256 Radio Frames.

eMBMS synchronization
20
SYNC, SYNC, SYNC
 For eMBMS service, eNBs that belong to the same MBSFN Area must broadcast the
same eMBMS data at the same time, so eMBMS UEs in the boarder area of eNBs can
combine radio signals from multiple eNBs to decode MBMS data without
interference. For this, the eNBs should be basically synchronized in terms of SFN.
 SYNCHRONIZATION
 System Frame Number synchronization among eNBs (GPS ToD)
 M2 control message synchronization
 eMBMS content transmission synchronization

M2 control message synchronization 1/2
 Both eNB and MCE shall have the synchronized SFN
 SFN management function in MCE shall exchange messages to synchronize SFN (every
60 seconds)
Elementary Initial Messag Successful outcome Unsuccessful outcome

Procedure e
MSFN SYN msg_enb_sfn_r msg_enb_SFN_rsp Msg_enb_SFN_failure
C eq
MSFN SYNC msg_enb_test_ msg_enb_test_taget_ msg_enb_test_taget_SF
target_SFN_req SFN_rep N_failure
SFN Offset computation
Slave Master
t1
t2
t3
t4
 Two delay paths must be calculated, the Master to Slave and the Slave to Master.
Offset = ((T2 - T1) - (T4 - T3)) / 2

M2 control message synchronization 2/2
 BCCH Modification and MCCH Modification
BCCH modification period (n) BCCH modification period (n+1)

Paging cycle(rf256)
… …
MCCH modification period (n) MCCH modification period (n+1)
… …
 Timely decoding of MCCH control information, it is recommended

to coincide BCCH and MCCH modification period
 MCCH Modification Period options : rf512, rf1024 (SIB13)

eMBMS content Tx synchronization 1/3
 SYNC Period is 60000 ms

 SYNC frame handler function
Ex) SFNTX = Time Stamp + Offset(=30)

Synchronization Sequence Length = 32
eNB#1
32 32 64 64
eNB#2
MBMS-GW BMSC
32 LOST 32 64 64
eNB#3
32 32 64
SFN=62
 Due to backhaul delay from BM-SC to each eNB, a content synchronization method is
required
 3GPP has defined SYNC protocol (TS 25.446)
 With help from BM-SC that put time stamp for each SYNC packet, the SYNC frame
handler function at eNB can synchronize eMBMS transmission time for any eNB in the
same MBSFN area
Arrival of
MBMS SESSION START
REQUEST 0 10 20 30
5 seconds
Time
MCCH Modification Modified MCCH

Session Request arrival
Notification
New Channel Open

(MCCH Update Time)
SFN
 eNB sends the MBMS packet in the radio frame of SFN = (Timestamp + Offset) % 4096

SYNC PDU TYPE 1 PDU format
Bits
Number of
Octets
7 6 5 4 3 2 1 0
PDU Type (=1) spare 1 Frame

Control
Part
Time Stamp 2
Packet Number 2
Elapsed Octet Counter 4
Header CRC Payload CRC 2 Frame

Check
Payload CRC Sum Part
Payload Fields 1–n Frame

Payload
part
Payload Fields Padding
Spare extension 0-4

SYNC PDU TYPE 0 PDU format
Bits
Number of
Octets
7 6 5 4 3 2 1 0
PDU Type (=0) spare 1 Frame

Control
Part
Time Stamp 2
Packet Number 2
Elapsed Octet Counter 4
Total Number Of Packet 3
Total Number Of Octet 5
Header CRC Padding 1 Frame

Check
Sum Part

Statistics and counter
Family Name Counter Name Description
MBMS_ENB_SYNC SyncPDU_Type0_RxCount Number of SYNC PDU Type 0
received by the SYNC handler
SyncPDU_Type1_RxCount Number of SYNC PDU Type 1

SyncPDU_Type3_RxCount Number of SYNC PDU Type 3

DroppedSyncSequenceCount S1 uplink forwarding (transmitting)

packet counts when S1 Handover
DroppedSyncPDUCount_INVALI Number of sync sequences discarde

D_TEID d
DroppedSyncPDUByte_INVALID_ Byte of SYNC PDUs arrived as invali
TEID d TEIDs

Session procedures
31
eMBMS Cell initialization
Non-
MBSFN
Cell MBSFN
Cell
MBSFN
Cell
LSM MBSFN
Cell
Service area,
Reserved cells, MBSFN
SYNC area Cell
configuration MBSFN
can be set at Cell
LSM MBSFN
Cell

eNB Cell Provisioning
 To Enable eMBMS for Each Cell and Configure MBSFN Synchronization Area
 Command: CHG-ENB-MBMSINFO, RTRV-ENB-MBMSINFO
Parameters Value Range Description

CELL_NUM 0~35 Max 36 cells per eNB
Indicates whether the cell is able to support eMBMS or not
STATUS 0~1
0 : Not Equip, 1 : Equip
Indicates whether the cell is providing eMBMS service or not
MBMS_SERVICE_STATE 0~1
0 : Inactive, 1 : Active
MBSFN_SYNC_AREA_ID 0~65535 MBSFN Synchronization Area ID (확인)
 To Configure MBMS Service Area ID

 Command: CHG-MBSFN-INFO, RTRV-MBSFN-INFO
Parameters Value Range Description
CELL_NUM 0~35 Max 36 cells per eNB
MBMS_SERVICE_AREA 1~65535 MBMS Service Area ID
MBMS_SERVICE_AREA 1~65535 MBMS Service Area ID
……
…… MAX_MBMS_SERVICE_AREA is 256
[MAX_MBMS_SERVICE_AREA]

MCE Provisioning for MBSFN Areas
 MBSFN Area Configuration in LSM
 Command: CHG-MBSFN-MAPPINGINFO, RTRV-MBSFN-MAPPINGINFO
Parameters Value Description

MBSFN_AREA_ID 0~255 Index for MBSFN Area ID
Indicate the status of MBSFN_AREA_ID
STATUS 0~1
0 : Not Configured, 1: Configured
MBSFN_SYNC_AREA_ID 0~65535 MBSFN Synchronization Area ID of MBSFN_AREA_ID
MBMS_SERVICE_AREA_ID 1~65535 MBMS Service Area ID supported by MBSFN_AREA_ID
MBMS_SERVICE_AREA_ID 1~65535 MBMS Service Area ID supported by MBSFN_AREA_ID
…… …… Maximum 256 MBMS_SERVICE_AREA_ID s can be configured

M2AP management function
eNB
MBSFN MCE
Cell #2
M2 non-service
MBSFN
Cell #1 Associated
MBSFN
Cell
M2 SETUP REQUEST
M2 SETUP RESPONSE
Non MBMS-Service-Ass
ociated M2AP MBMS SCHEDULING INFORMATION
MBMS SCHEDULING INFORMATION

RESPONSE

M2 SET UP
 M2 set up request message enables eNB to indicate the MBMS service area per each
cell and the reserved cell.
 Upon receiving M2 setup request, MCE shall return control channel information
(MCCH related BCCH Configuration) for each MBSFN area
M2 SETUP REQUEST IE
IE/Group Name Presence Range IE type and Semantics d Criticality Assigned Cr
reference escription iticality
Message Type M 9.2.1.1 YES reject

Global MCE ID M 9.2.1.10 YES reject
eNB Name O Printable Stri YES ignore
ng (1..150,...
)
eNB MBMS Configuration 1 Yes reject

data per cell
>> MCCH related BCCH 1 to <maxnoofC EACH reject

Configuration Item ells>
>>eNB MBMS M 9.2.1.12 -

Configuration data item
IE/Group Name Presence Range IE type and reference

E-UTRAN CGI M 9.2.1.11
MBSFN Synchronization Area Id M 9.2.1.20
MBMS Service Area List
>MBMS Service Area Item 1 to <maxnoofMBMS
<maxnoofMBMSServ ServiceAreasPer
iceAreasPerCell> Cell>= 256
>> MBMS Service Area 9.2.3.6

M2 SETUP RESPONSE IE
IE/Group Name Presence Range IE type and Semantics d Criticality Assigned Cr
reference escription iticality

Global MCE ID M 9.2.1.16 YES reject
MCE Name O Printable Stri YES ignore
ng (1..150,...
)
MCCH related BCCH Conf 1 YES reject

iguration data per MBSFN
area
>MCCH related BCCH C 1 to <maxnoofM EACH reject

onfiguration data Item IE BSFNareas>=
s 256
>> MCCH related BCCH M 9.2.1.13 -

Configuration Item
Criticality Diagnostics O 9.2.1.7 YES ignore

MCCH related BCCH Configuration Item
IE/Group Name Presence Range IE type and Semantics description
reference
MBSFN Area Id M 9.2.1.14
PDCCH Length M ENUMERAT This IE is encoded along the
ED (s1, number of OFDM symbols for
s2,…) PDCCH as of table 6.7-1. in
TS 36.211 [12].
Repetition Period M ENUMERAT The same encoding as the
ED (rf32, mcch-RepetitionPeriod in
rf64, rf128, mcch-Config as specified in
rf256) TS 36.331 [11]
Offset M INTEGER The same encoding as the
(0..10) mcch-Offset in mcch-Config as
specified in TS 36.331 [11]
Modification Period M ENUMERAT The same encoding as the
ED (rf512, mcch-ModificationPeriod in
rf1024) mcch-Config as specified in
TS 36.331 [11]
Subframe Allocation Info M BIT STRING The same encoding as the sf-
(SIZE(6)) AllocInfo specified in TS
36.331 [11]
Modulation and Coding M ENUMERAT The same encoding as the
Scheme ED (n2, n7, signallingMCS specified in TS
n13, n19) 36.331 [11]
Cell Information List 0..1
>Cell Information 1 to
<maxnoofCells>
>>E-UTRAN CGI M 9.2.1.11
>>Cell Reservation Info M ENUMERAT
ED
(reservedCel
l,
nonReserve
dCell, …)

BCCH SystemInformation Block Type 13
 IE contains the information required to acquire the MBMS control information
associated with one or more MBSFN area
-- ASN1START
SystemInformationBlockType13-r9 ::= SEQUENCE {
mbsfn-AreaInfoList-r9 MBSFN-AreaInfoList-r9,
notificationConfig-r9 MBMS-NotificationConfig-r9,
lateNonCriticalExtension OCTET STRING OPTIONAL, -- Need OP
...
}
-- ASN1STOP

Mbsfn-AreaInfoList IE
 SytemInformationBlcokType 13 Information Element
 Mbsfn-AreaInfoList-r9 ( TS 36.331 Page 237, MBMS Information Elements)
-- ASN1START
MBSFN-AreaInfoList-r9 ::= SEQUENCE (SIZE(1..maxMBSFN-Area)) OF MBSFN-AreaInfo-r9
MBSFN-AreaInfo-r9 ::= SEQUENCE {
mbsfn-AreaId-r9 INTEGER (0..255),
non-MBSFNregionLength ENUMERATED {s1, s2},
notificationIndicator-r9 INTEGER (0..7),
mcch-Config-r9 SEQUENCE {
mcch-RepetitionPeriod-r9 ENUMERATED {rf32, rf64, rf128, rf256},
mcch-Offset-r9 INTEGER (0..10),
mcch-ModificationPeriod-r9 ENUMERATED {rf512, rf1024},
sf-AllocInfo-r9 BIT STRING (SIZE(6)),
signallingMCS-r9 ENUMERATED {n2, n7, n13, n19}
},
...
}
-- ASN1STOP

Mbsfn-AreaInfoList IE
 Mbsfn-AreaId: Indicates the MBSFN area ID
 signallingMCS: Indicates the modulation and Coding Sceheme (MCS) applicable for
the subframes indicated by the field sf-AllocInfo and for the first subframe of each
MCH scheduling period.
 Sf-AllocInfo: Indicates the subframes of the radio frames indicated by the mcch-
RepetitioPeriod and the mcch-Offset, that may carry MCCH.

UE eNB MCE MME MBMS-GW BM-SC
1. MBMS Scheduling
Information
2. MBMS Scheduling
Information Response
 M2 MBMS scheduling information message enable eNB to indicate MBSFN subframe

configuration pattern at SIB2 message.
 It also deliver PMCH configuration, MBMS session list per PMCH, Common subframe
allocation period per MBSFN area for MCCH RRC MBMSAreaConfiguration message.

IE/Group Name Presence Range IE type and r Semantics d Criticality Assigned Cri
eference escription ticality
MCCH Update Time M 9.2.1.19 YES reject
MBSFN Area Configuration L 1 YES reject
ist
>MBSFN Area Configuratio 1 to <maxnoofMB EACH reject
n Item IEs SFNareas>
>>PMCH Configuration Li 1 YES reject
st
>>>PMCH Configuration 0 to <maxnoofPM EACH reject
Item IEs CHsperMBSFNar
ea>
>>>>PMCH Configuration M 9.2.1.8 -
>>>>MBMS Session List per P M 9.2.1.9 -
MCH
>>Subframes Configuratio 1 YES reject
n List
>>>Subframes Configura 1 to <maxnoofMB EACH reject
tion Item IEs SFNallocations>
>>>>MBSFN Subframe Config M 9.2.1.17 -

uration
>>Common Subframe Alloc M 9.2.1.18 YES reject
ation Period
>>MBSFN Area ID M .14 YES reject
PMCH configuration
IE/Group Name Presence Range IE type and r Semantics description
eference
Allocated Subframes End M INTEGER (0.. Encoded as the sf-AllocEnd
1535) IE in TS 36.331 [11]
Modulation and Coding Scheme M INTEGER (0.. Encoded as the dataMCS
28) IE in TS 36.331 [11]
MCH Scheduling Period M ENUMERATE Encoded as the mch-Schedulin
D (rf8, rf16, rf gPeriod IE in TS 36.331 [11]
32, rf64, rf128
, rf256, rf512,
rf1024)
SAMSUNG CONFIDENTIAL © 2009 Electronics.

Ⓒ 2010 SAMSUNG SAMSUNGAll Electronics. All rights reserved.
rights reserved. 45
MBMS Session List per PMCH
IE/Group Name Presence Range IE type and Semantics descriptio
reference n
MBMS Session List per PMCH item IE M 1 to maxnoofsessionsperP
s <maxnoofsessionsper MCH = 29
PMCH>
> MBMS Service Identity M TMGI
9.2.3.3
> LCID M Integer Logical channel ID
SAMSUNG CONFIDENTIAL © 2009 Electronics.

Ⓒ 2010 SAMSUNG SAMSUNGAll Electronics. All rights reserved.
rights reserved. 46
BCCH SystemInformationBlock Type 2
 It contains radio resource configuration info that is common in all UE
 MBSFN-SubframeConfig of MBSFN-SubframeConfigList System Information Block: IE

that defines subframes that are reserved for MBSFN in downlink (TS 36.331 Page 238)
MBSFN-SubframeConfigList ::=
SEQUENCE (SIZE (1..maxMBSFN-Allocations)) OF MBSFN-SubframeConfig
-- ASN1START
MBSFN-SubframeConfig ::= SEQUENCE {

radioframeAllocationPeriod ENUMERATED {n1, n2, n4, n8, n16, n32},
radioframeAllocationOffset INTEGER (0..7),
subframeAllocation CHOICE {
oneFrame BIT
STRING (SIZE(6)),
fourFrames BIT
STRING (SIZE(24))
}
}
-- ASN1STOP

RRC MCCH-Message
 The MCCH-Message class is the set of RRC messages sent from the E-UTRAN to the
UE on the MCCH logical channel (Page 107)
-- ASN1START
MCCH-Message ::= SEQUENCE {
message MCCH-MessageType
}
MCCH-MessageType ::= CHOICE {
c1 CHOICE {
mbsfnAreaConfiguration-r9 MBSFNAreaConfiguration-r9
},
later CHOICE {
c2 CHOICE{
mbmsCountingRequest-r10 MBMSCountingRequest-r10
},
messageClassExtensionSEQUENCE {}
}
}
-- ASN1STOP

RRC MBSFNAreaConfiguration message
 The MCCH carries the MBSFNAreaConfiguration message
 MBSFNAreaConfiguration message: It contains the MBMS control information

applicable for an MBSFN area. E-UTRAN configures an MCCH for each MBSFN area
(Page 118)
-- ASN1START
MBSFNAreaConfiguration-r9 ::= SEQUENCE {
commonSF-Alloc-r9 CommonSF-AllocPatternList-r9,
commonSF-AllocPeriod-r9 ENUMERATED {
rf4, rf8, rf16, rf32, rf64, rf128, rf256},
pmch-InfoList-r9 PMCH-InfoList-r9,
nonCriticalExtension MBSFNAreaConfiguration-v930-IEs OPTIONAL
}
MBSFNAreaConfiguration-v930-IEs ::= SEQUENCE {
lateNonCriticalExtension OCTET STRING OPTIONAL, -- Need OP
nonCriticalExtension SEQUENCE {} OPTIONAL -- Need OP
}
CommonSF-AllocPatternList-r9 ::=SEQUENCE (SIZE (1..maxMBSFN-Allocations)) OF MBSFN-SubframeConfig
-- ASN1STOP

MBSFN-SubframeConfig IE
 The IE MBSFN-SubframeConfig defines subframes that are reserved fro MBSFN in
downlink
-- ASN1START
MBSFN-SubframeConfig ::= SEQUENCE {
radioframeAllocationPeriod ENUMERATED {n1, n2, n4, n8, n16, n32},
radioframeAllocationOffset INTEGER (0..7),
subframeAllocation CHOICE {
oneFrame BIT STRING (SIZE(6)),
fourFrames BIT STRING (SIZE(24))
}
}
-- ASN1STOP

PMCH-InfoList (TS 36.331 Page 239)
-- ASN1START
PMCH-InfoList-r9 ::= SEQUENCE (SIZE (0..maxPMCH-PerMBSFN)) OF PMCH-Info-r9
 This IE
PMCH-Info-r9 ::= SEQUENCE {
pmch-Config-r9 PMCH-Config-r9,
specifies
mbms-SessionInfoList-r9 MBMS-SessionInfoList-r9,
...
configuration
}
MBMS-SessionInfoList-r9 ::= SEQUENCE (SIZE (0..maxSessionPerPMCH)) OF MBMS-SessionInfo-r9
of all PMCHs
MBMS-SessionInfo-r9 ::= SEQUENCE {
tmgi-r9 TMGI-r9,
of an MBSFN
sessionId-r9 OCTET STRING (SIZE (1)) OPTIONAL, -- Need OR
logicalChannelIdentity-r9 INTEGER (0..maxSessionPerPMCH-1),
area
...
}  TMGI:
PMCH-Config-r9 ::= SEQUENCE {
sf-AllocEnd-r9 INTEGER (0..1535), Temporary
dataMCS-r9 INTEGER (0..28),
mch-SchedulingPeriod-r9 ENUMERATED { Mobile Group
rf8, rf16, rf32, rf64, rf128, rf256, rf512, rf1024},
... ID
}
TMGI-r9 ::= SEQUENCE {  MCH
plmn-Id-r9 CHOICE {
plmn-Index-r9 INTEGER (1..6), Scheduling
explicitValue-r9 PLMN-Identity
}, Period (MSP)
serviceId-r9 OCTET STRING (SIZE (3))
}
-- ASN1STOP

M2AP session management function
eNB
MBSFN MCE
Cell #2
M2 service
MBSFN
Cell #1 Associated
MBSFN
Cell
MBMS SESSION START REQUEST
MBMS SESSION START RESPONSE

MBMS-Service-
Associated M2AP
MBMS SESSION START FAILURE
MBMS SESSION STOP REQUEST

MBMS SESSION START
 M2 MBMS session start message shall indicate which TMGI in MBMS service ID will
be delivered over which IP multicast address

eMBMS QoS
 eMBMS bearers (or MBMS bearer) shall be GBR bearers and associated with the
following QoS parameters.
 QoS class Identifier (QCI)
 Allocation and Retention Priority (ARP) (Currently not supported)
 Maximum Bit Rate (MBR), which should be set to the same as GBR
 Guarnteed Bit Rate (GBR)
 QCI defines a MCS level according to a QCI-MCS level mapping table that operator
pre-configured in MCE. eMBMS QCI Resource Type MCS Level Comment
128 GBR 11
129 GBR 12
130 GBR 13
131 GBR 14
132 GBR 24
133 GBR 25
134 GBR 26
135 GBR 27
136 GBR 28
Default MCS value is u
Default GBR 13 sed when QCI is not sp
ecified.

Statistics and counter (eNB)
Counter Name Description
M2ConnEstabAtt Count of M2 session setup attempts transmitted by the
eNB
M2ConnEstabSucc Count of M2 session setup successes received by the eNB
M2ConnEstabFail_M2AP_CU_FAIL A call is released due to the M2 specification cause during

the M2 session setup.
M2ConnEstabFail_M2AP_LINK_FAIL A call is released due to M2 SCTP Link failure during the
M2 session setup
SessionStartAtt Count of M2 MBMS session start request attempts
received by the eNB
SessionStartSucc Count of M2 MBMS session start response successes
received by the eNB
SessionStartFail_M2AP_CU_FAIL A call is released due to the M2 specification cause during
the M2 session setup.
SessionStartFail_M2AP_LINK_FAIL A call is released due to M2 SCTP Link failure during the
M2 session setup
SessionStopAtt Count of M2 MBMS session stop request attempts
received by the eNB
SessionStopSucc Count of M2 MBMS session stop response successes
transmitted by the Enb
SessionStoptFail_CP_CC_FAIL A call is released due to reset notification (eNB failure or
block restart) from ECMB or by ECCB during the M2
session stop procedure.
SessionStopFail_M2AP_LINK_FAIL A call is released due to M2 SCTP Link failure during M2
session stop.
Statistics and counter (MCE)
Counter Name Description
SessionStartAtt MCE M2 MBMS Session Start Request count
SessionStartSucc MCE M2 MBMS Session Start Response count
SessionStartFail_CP_CC_FAIL M2 MBMS Session Start fail by Reset
SessionStartFail_CP_CAPA_CAC_F
M2 MBMS Session Start fail by MCE resource allocation failure
AIL
SessionStartFail_M2AP_CU_FAIL During M2 Session Setup, the set up fail per cause defined IE
SessionStartFail_M2AP_LINK_FAIL During M2 Session Setup, the set up fail due to M2 SCTP Link fail
SessionStopAtt MCE M2 MBMS Session Stop Request count
SessionStopSucc MCE M2 MBMS Session Stop Response successful count
SessionStopFail_CP_CC_FAIL M2 MBMS Session Stop fail by reset MCE failure cause
SessionStopFail_M2AP_LINK_FAIL During M2 Session Stop process, M2 SCTP Link fail

M3AP session management function
MCE MME
M3 service
Associated
MBMS SESSION START REQUEST
MBMS SESSION START RESPONSE

MBMS-Service-
Associated M3AP
MBMS SESSION START FAILURE
MBMS SESSION STOP REQUEST

Overall procedures
UE eNB MCE MME MBMS-GW BMSC
Service Announcement (Service ID, Multicast IP Address, Time of transmission) (HTTP, Announcement
SMS, etc) Function
HTTP Digest AKA, establish Ks Key Request

Function
HTTP POST Registration
HTTP 401 WWW-Authenticate
HTTP POST Authorization Request Key
Management
HTTP 200 OK Authentication-Info
Function
MIKEY (MSK)/UDP), MIKEY ACK
RAR Start
Session MBMS Session
Session Start Start RAA Start Transmission
MBMS Session
Function
Start
IGMPv3 Join Multicast
Router
MBMS Scheduling
BCCH SIB2/3/13 Info
MCCH
(Multicast) (Unicast) MBMS Delivery
Multicast (Multicast)
(Broadcast) Router Function

MCE Redundancy
59
MCE Redundancy
 MCE servers packed in a shelf cover 5,000 eNBs, which requires a more
reliable system.
 Two blades serve as one MCE server; Active and Standby respectively
 Up to 5 redundant MCE sets in one shelf
 Link Redundancy supported
 SCTP multi-homing supported between MCE and eNB/MME
 Dual IPC Switch for internal communication
IP1 (M2)
IP2 (M3)
IP3 (OAM)
IPC M M M M M M M M M M
Switch C C C C C C C C C C
E E E E E E E E E E
Switch#3 1 1 2 2 3 3 4 4 5 5 Switch#1
NOT USED
(M2) IP4 A S A S A S A S A S
(M3) IP5
(OAM) IP6
IPC
#1 #2 #3 #4 #5 #6 #7 #8 #9 #10 #11 #12 Switch
Switch#2 Switch#4
© SAMSUNG Electronics Co., Ltd. Confidential and Proprietary

Switch Over between Active and Standby
 Standby takes over Active when:
 SW Block Failure
 HW Failure
 Board Reset
 Command by Operator
 No Response from Active
— Due to hardware or software or link failure
— For dual active state due to any reason, the server that lives longer will take the “Active” Role. The
other blade will change its state to “Standby”.
© SAMSUNG Electronics Co., Ltd. Confidential and Proprietary

eMBMS Service Continuity
62
Inter-Frequency handover
 This feature allows UEs to connect to the MBMS in an MBMS coverage area
regardless of the frequency of the MBMS in the multi-frequency environment.

Copyright and Confidentiality
Copyright © 2014, SAMSUNG Electronics Co., Ltd. SAMSUNG Electronics reserves the right to make changes to the specifications of
the products detailed in this document at any time without notice and obligation to notify any person of such changes. Information
in this document is proprietary to SAMSUNG Electronics Co., Ltd. No information contained here may be copied, translated,
transcribed or duplicated by any form without the prior written consent of SAMSUNG Electronics.

eNB-MCE Functions, Parameters & Statistics - 20140626 PDF

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

eNB-MCE Functions, Parameters & Statistics - 20140626 PDF

Transféré par

Droits d'auteur :

Formats disponibles

eNB/MCE functions,

parameters & statistics

 eMBMS functional diagrams

 eMBMS scheduling block: RLC/MAC scheduling and MTCH/MCCH/P(MCH) control

 Resource allocation block: MBSFN subframe allocation pattern generation

 M2AP/M3AP control block: M2 and M3 message processing

 M2AP control block: M2 message processing

 Session control block: Session admission control

2014 © Samsung Electronics 5

 MCH is RLC-UM mode, no HARQ support

2014 © Samsung Electronics 6

 SIB3 : Indicate neighbor cell MBSFN configuration

 SIB13: Indicate MCCH scheduling information

 SIB15: Indicate SAI of the current and neighbor carrier frequency

 SIB16: Indicate UTC time

 RRC messages over MCCH

 RRC MBMSInterestIndication message

 RRC MBSFNAreaConfiguration message

2014 © Samsung Electronics 7

 Acquire SIB(2,13), SIB15(optional), SIB16 (optional)

2014 © Samsung Electronics 8

Session start request Session start request

 If physical/logical resource is limited due to previous resource allocation, the newly

2014 © Samsung Electronics 10

1 Radio Frame = 10ms

2014 © Samsung Electronics 11

 1 Subframe per 10ms (Kbps)

 2 Subframes per 10ms (Kbps)

 3 Subframes per 10ms (Kbps)

 4 Subframes per 10ms (Kbps)

2014 © Samsung Electronics 12

MBSFN AREA #1 MBSFN AREA #2 MBSFN AREA #2

 Interleaving resource allocation can avoid the interference.

2014 © Samsung Electronics 13

• All eNBs in the area must be connected to the same

2014 © Samsung Electronics 14

SFN 0 SFN 8 SFN 16 SFN 24 SFN 32

 Common Subframe Allocation: It indicate subframes allocated to the MBSFN area

2014 © Samsung Electronics 15

CSAP(Common Subframe Allocation Period) : 320ms

2014 © Samsung Electronics 16

CSAP(Common Subframe Allocation Period) : 320ms

PMCH 0 : MBMS Bearer 1,

PMCH 2 : MBMS Bearer 3

2014 © Samsung Electronics 17

MSI MCCH MTCH MSI MCCH MTCH

LCID 1 Stop MTCH 1 Oct 1

Stop MTCH 1 Oct 2

LCID 2 Stop MTCH 2 Oct 3

Stop MTCH 2 Oct 4

Stop MTCH n Oct 2n

 MCCH Repetition periods are 32,64, 128 or 256 Radio Frames.

2014 © Samsung Electronics 19

 M2 control message synchronization

 eMBMS content transmission synchronization

2014 © Samsung Electronics 21

Elementary Initial Messag Successful outcome Unsuccessful outcome

Offset = ((T2 - T1) - (T4 - T3)) / 2

2014 © Samsung Electronics 23

BCCH modification period (n) BCCH modification period (n+1)

MCCH modification period (n) MCCH modification period (n+1)

 Timely decoding of MCCH control information, it is recommended

 MCCH Modification Period options : rf512, rf1024 (SIB13)