Transcript Why do we need MEDIEVAL?

MultimEDia transport for mobIlE
Video AppLications
9 th Concertation Meeting
Brussels, 13th February 2012
MEDIEVAL Consortium
1
Outline
• The MEDIEVAL project
• Planned demos and services
• Dissemination summary
February 13th, 2012
9th Concertation Meeting
2
MEDIEVAL Objectives
• Video is a major challenge for the future Internet
• Current mobile Internet IS NOT designed for video
• Specific enhancements for video should be introduced at all
layers of the protocol stack where needed
• MEDIEVAL : Evolutionary path for a truly video-for-all
philosophy
–
–
–
–
Evolved cross-layer algorithms and mechanisms
Quality of Experience based solutions for mobile video delivery
Flat mobility architecture based on a distributed DMM concept
MT multi homed through an innovative Abstract Interface; mechanisms to
optimize Video transmission over heterogeneous air interfaces
– a mobile CDN (i.e. adding of new CDN entities in the mobile network)
concept for efficient media delivery
February 13th, 2012
9th Concertation Meeting
3
MEDIEVAL network deployment
Administrative
Domain 2
Video Content & Services
Content Providers
PB
S(
Over The Top (OTT)
Video Servers
Personal
Broadcasters
Administrative
Domain 1
Network Transport
mu
ltic
as
t
tra
ffi
c)
Core Router
CDN node
Internet
Core Router
CDN node
CDN node
CDN node
Core Router
Core Router
Core Router
Session
Management
ISP
Video Server
MIIS Server
Provisioning Video Service
Platform
Portal
ALTO Server
Local Mobility
Domain 2
Local Mobility
Domain
CDN
CDN
CDN
MAR
CDN
MAR
PoA
MAR
LTE
PoA
PoA
PoA
MN
February 13th, 2012
PoA LTE
PoA
MN PoA
PoA
WLAN
PoA
PoA
WLAN
PoA
PoA
LTE
mMAR
PoA
MAR
PoA
PoA
PoA
PoA
PoA
PoA
mMAR
9th Concertation
MN
LTE
PoA
MN
MN
Meeting
4
The MEDIEVAL project
• MEDIEVAL is an operator-driven project
specifying and demonstrating a mobile video
architecture with cross-layer mechanisms to
provide high quality of experience to users
February 13th, 2012
9th Concertation Meeting
5
MEDIEVAL Architecture
• Medieval architecture is divided into 4 subsystems
– Video Service Control (WP2)
• Links the applications and services to the underlying network delivery
entities
– Transport Optimization (WP5)
• Provides optimized video traffic in the mobile operator's core network
– Mobility Management (WP4)
• Evolves today's mobile Internet architecture to more efficiently
support growth of video services, based on flow mobility and DMM
– Wireless Access (WP3)
• Provides enhanced video delivery in the last (wireless) hop, mainly
focusing on novel access techniques and technology abstraction
• Strong level of cross-layer interactions between the
subsystems
February 13th, 2012
9th Concertation Meeting
6
MEDIEVAL Architecture
February 13th, 2012
9th Concertation Meeting
7
Planned demo 1 : VOD Scenario
VOD server
cache2
cache1
Step 1: MN2 connects to MAR1 and gets video2 (from cache1 or
VOD Server)
Step 2: MN2 gets another flow (e.g.: VoIP)
Step 3: MN2 discovers a WiFi coverage (MAR2)
Step 4: MN2 moves out of WLAN coverage, and goes under
MAR3 and changes cache . The video-flow comes from cache3,
VoIP is anchored to MAR1
cache3
3G
Video 2
Main features of this demonstrator are:
ftp
Video 2
February 13th, 2012
DMM based intra-domain handover
(both between homogeneous and
heterogeneous PoAs),
WiFi Offload support
CDN solutions
9th Concertation Meeting
8
Planned demo 2 : PBS Scenario
Step1: LiveU SW sends in uplink the contents over
multilink to the LiveU node.
Step2: The LiveU node sends the content to the
Unicast/Multicast translation node
Step3: The Unicast to Multicast Translation sends
the content in multicast
Step 4: mobile terminals receive the content in
multicast (multicast receivers)
Step 5: mobile receivers will move (mobile-initiated
multicast receiver mobility)
5
4
1
2
3
Main features of this demonstrator are:
Multicast listener mobility
Multilink transmission
eMBMS
February 13th, 2012
9th Concertation Meeting
9
Planned demo 3: Inter-operator
Video Service provided by domain operator A (VoD)
Step1: VOD service activation by MN1
Step2: Congestion in the RAN is detected and Transport Optimization
triggers layer dropping in the LTE cell; As congestion does not improve,
traffic shaping is triggered in the Core network.
Step3: MN moves to WIFI Operator B ;
Tunnel is setup to allow session continuity (same IP address as before);
MN keeps on downloading the same video but traffic optimization is not
possible;
Step4: WIFI gets congested and the QoE is not acceptable as compared to
what was shown in step 2
Main features of this demonstrator are:
Packet marking and dropping in LTE
access
Traffic shaping in the Core Network
Inter-operator mobility
Benefits from MEDIEVAL architecture on
the QoE
February 13th, 2012
9th Concertation Meeting
10
Dissemination Summary
• Publications
– Y1 : top workshops and conferences (18); leading
journals (9)
– Y2 : top workshops and conferences (8 + 4
submitted); leading journals (8 + 7 submitted)
• Standards
– IEEE : Active in 802.21 (MIH), evaluation of 802.11aa
(Video Streams Transport)
– IETF : Active in NETEXT, MEXT, MULTIMOB, ALTO
– 3GPP : Contributions to SA1 / SA2
• 3 patents applications filed
February 13th, 2012
9th Concertation Meeting
11
Thank you for your attention
http://www.ict-medieval.eu/
The research leading to these results has received
funding from the European Community's Seventh
Framework Programme (FP7-ICT-2009-5) under grant
agreement n. 258053 (MEDIEVAL project).
February 13th, 2012
9th Concertation Meeting
12