Anritsu MD8430/RTD eMBMS

solution

Copyright© ANRITSU
Agenda
• Anritsu eMBMS solution for MD8430/RTD
• Why a server solution?
• Why EXPWAY Server?

Copyright© ANRITSU
 Anritsu’s eMBMS Solution Overview
- MD8430A with RTD
Test LTE layer 1 and 2 signaling End to end solution with BM-SC Server
• Schedule multicast channels • Simulate application layer functionality
– Verify protocol implementation and channel – Test file download and streaming
acquisition – Verify middleware behaviour
• Transmit eMBMS info in System Information (SIB) • RTD integration & control of BM-SC server in TC’s
– Test configuration changes, UTC and local time
• Enable to control BM-SC server from RTD for
synchronization
eMBMS testing (Start , Stop, Select Data stream)
• Configure MAC layer scheduling
– Test data reception, service continuity and channel
capacity

Data Server
(Customer-supplied)
eCast™
BM-SC Server

Slide 3
Copyright© ANRITSU
 Anritsu’s eMBMS
• Anritsu’s MD8430 eMBMS solution provides robust test capabilities
with real network simulations:

Download Streaming
Security Services Services

Applications

File Repair
Discovery
Service
Security Codecs MD8430A + RTD +BMSC

PTM
Service
layer

MTK DASH

MIKEY FLUTE
RTP/RTCP
protocols

UDP
IP

IP
MD8430A + RTD
protocols

Layer 2 (MAC/RLC UM)

Radio

Physical Layer

Provides full range of simulation and testing

Slide Title or URL
4 Copyright© ANRITSU
Why Server Based Testing?
• File Repair and Reception Reporting
– Very difficult to simulate through prerecorded captures
– Two features constitute a large portion of the BMSC specifications
– Need to be able to turn those two features on and off at specific times as for many
scenarios
– VZW test cases for File Repair : 15% of functional test cases
– VZW test cases for Reception Reporting : 12% of functional test cases
• Greatly reduced number of test files needed
– Example: Encoding rates, DASH segment sizes, FEC level and dropped symbols
(i.e. signal errors)
– Simple scenario :
• 3 video encoding rates (500 Kbps, 800 Kbps, 1,5 Mbps)
• Dash segment sizes (1s, 2s, 5s)
• FEC level (5%, 10%, 15%)
• FLUTE symbol dropped (10%, 20%, 30%)
– Number of BMSC input files required : 9 generic video files
– Number of PCAPs required : 81 specific files (about 8100 MB of data)

Slide Title or URL

5 Copyright© ANRITSU
Why Server Based Testing?
• Branching : with PCAPs, cannot test, learn, and refine
– Who creates all those PCAPs on demand ?
– How long does it take ?
– How long will they support you for those requests ?
• Flexiblity in testing
– Overall, the BMSC exposes over 60 parameters related to service
announcement, FEC, FLUTE parameters, live DASH streams and file
services
– Creates a large set of permutations that cannot be captured by PCAPS
– Many permutations will directly or indirectly affect how the device behaves

Slide Title or URL

6 Copyright© ANRITSU
Why EXPWAY Server?
• EXPWAY are makers of eMBMS BMSC and middleware
• They are gaining traction in market for their BMSC solution:
– ALU is using the EXPWAY FLUTE server for ALL of their eMBMS
deployments (white label with ALU branding):
• VzW,
• AT&T,
• France Telecom (Orange)
– Huawei is using EXPWAY BMSC
• China Telecom,
• ICS Costa Rica
• EE UK
• Bell Mobility Canada is implementing a full server through One2Many
using EXPWAY. (http://www.one2many.eu/en/)

Slide Title or URL

7 Copyright© ANRITSU
 Slide Title or URL
8 Copyright© ANRITSU