How To Sell VO Part II

How to Sell Video
Optimization: capabilities and

Ericsson solution
Scope and Objective
Objective:
› To learn to sell Video Optimization on MSP
Scope
› VO Technique overview
› Ericsson Solution
– Congestion Detection
– Media Analysis
– Pacing
– Transcoding
– ABR Streaming Control
How to Sell Video Optimization on MSP part 2 | Ericsson Internal | , Rev | 2014-12-31 | Page 2
Video Optimization (VO) techniques
› Pacing
› Caching
– Original video
– TransXed video
› TransXing:
– Transcoding: adapting the compression format of the video
– Transrating: adapting the streaming bit rate of the video
– Transsizing: adapting the video window frame
– Transmuxing/wrapping: adapting the container format or delivery protocol
› Adaptive Streaming Control
› Traffic analytics: can be used to globally enable/disable VO techniques and
adjust parameters
Congestion-Aware VO User Agent
iPad
User Agent
Laptop
Congestion metrics
MIME type
Real-Time User Agent
Decision Engine URL
HTTP,
MPEG-DASH
Radio
Origin Access
Server Video Video Video Congestion
Caching Transcoding Pacing Detection
RAN
Awareness*
Media Analysis User Agent
Android
Vo by business application
Volume Congestion Delivery Method
Reduction Control
RAN Core RAN Core
Pacing X X PD ABR
Transcoding X X PD
Transrating X X PD
Transmuxing X PD ABR
Caching X X PD ABR
Adaptive X ABR
streaming control
Congestion X PD ABR
detection
Analytics X X X X PD ABR
Congestion detection
› Solutions:
– Transport-level metrics
– Application-level metrics
– RAN Probes: Movik Networks, Intucell
– Standards-based: 3GPP UPCON (3GPP TR 23.705)
– Proprietary: Ericsson RAN Feedback
› TCP metrics exposed by Ericsson TCP RNA:
– smooth average round-trip time (SRTT)
– packet loss rate (PLR)
– UE bit rate
Media Analysis
HTTP Layer DPI
Media Container MI
(pacing)
Media Frames MI
(transcoding)
Video pacing
› MSP enables pacing on HTTP progressive download and MPEG-DASH traffic that is sent to
devices over the radio access network
› MSP supports two alternative video pacing methods:
– Media rate Video Pacing (MVP) method
– Radio Friendly video Pacing (RFP) method.
HLR HSS Paced video

delivery, MVP or
RFP
Origin
Radio HTTP server
Access SGSN GGSN
MME MPG MSP
GSM-RBS EPS
WCDMA-RAN
LTE-RAN
SUB
DB
Mediarate Video pacing
› Minimizes waste of network resources when end-users abandon a video clip after just a short play-out time
› After a start-up burst to fill the play-out buffer, the streaming video is delivered as it is played
› Retained end-user experience
– no added startup delay due to video pacing
– no re-buffering and playback stalls.
Start-up burst to fill

the play-out buffer
kbps
Paced video
time
Mediarate Video pacing
› Video clip is 3:36 minutes
› No pacing:
– Total download time is 35 seconds
› With Media rate Video Pacing:
– Download at media rate, after initial burst
MVP – no youtube throttling
MVP – youtube throttling
Radio-friendly Video pacing (RFP)
› Streaming video is delivered in bursts  Utilizes high link-bitrates in the bursts

› Idle duration period is maximized  Saves RAN resources and device battery
› Pacing  Download waste due to abandonment is minimized.
kbps
Idle duration
(configuration parameter)
RFP measurements (3G)
Window
duration
2s
0.450151951
10 s
0.408455248
22 s
0.385180693
30 s
0.382868477
Video Caching
› Caches unmanaged HTTP content

› Supported HTTP requests for caching:
– HTTP Download
– HTTP Progressive download
– HTTP Adaptive Bitrate requests
› Transparent towards mobile device and origin server
› Accessed using a workflow script in MSP
› Content owner friendly
– Sending HEAD/GET requests on cache hits allow Content Providers to maintain proper
content statistics, business models, etc.
Video Caching
› Some caching mechanisms have been implemented specifically to support

streaming video content:
– Unique ID generation for videos with dynamic URLs: Several sites, such as Dailymotion
and Vimeo, use dynamic URLs to deliver video content, and require special handling.
– Cache control directives: Flexible cache control directives can override the default, global
directives, in order to allow caching of content that requires special handling
– Cache validation mechanisms: Some video domains do not accept HEAD requests, hence
byte range GET requests are allowed instead for cache validation
– Byte range support: Many video sites deliver content as byte ranges
Video transcoding
› Transcoding can be done on-the-fly (very CPU intensive), or from cached
content
› QoE is key: the quality should not be perceptibly degraded
Offline video transcoding
› Some of the cached video content can be asynchronously transcoded for later
delivery at a reduced rate or using a different video format
› MSP periodically decides which videos are candidates for offline transcoding
› The transcoding process is executed by the VOM virtual machine, which also
determines which videos are transcodable
› Transcoding profiles are stored in the system and used to determine the
characteristics of the output video file
› The full file must be available for offline transcoding to be possible. If necessary
(e.g. when a video is delivered via byte ranges), the full file can be pre-fetched
by MSP even though it has not been fully requested by the device, thus allowing
an earlier transcoding
Popularity metrics
› Popularity metrics of the cached videos are used to rank the video files by
popularity. Once a video’s popularity metric has reached a certain threshold, a
request will be made to a pool of VOMs for offline transcoding
› The solution allows specifying the popularity thresholds that will the trigger the
offline generation of a transcoded version of an original video
On-the-fly video transcoding
Advantages of OTF transcoding :
› content does not need to be stored and available in cache to be served in
transcoded format
› only ranges that are served to the device are transcoded
› possible to turn on/off transcoding based on network conditions, for example
congestion level
Drawbacks :
› it is very CPU intensive
› the compression efficiency is typically lower than for offline transcoding
› not all videos can be transcoded in real-time due to issues with format or
delivery protocol
On-the-fly video transcoding
› The transformations that can be done on video content include:

– Change of bit rate
– Change of resolution
– Change of video container format
– Change of video codec
– Change of video size
Video transcoding
Method Entropy Open-loop Fast pixel domain Cascaded Pixel Full
transform transrating (OLT) transrating (FPDT) Domain transcode
(ET) Transrating (CPDT) (FT)
Description Re-encode Re-quantization Correction loop Re-use prediction Decoding to

CAVLC to applied to OLT and motion YUV to
CABAC vectors in full re-encoding
transcode
Complexity Lowest Low Higher than OLT Less than FT Highest
Quality No Drift causes ~10 Remaining drift ~1-2 dB Low

degradation dB degradation causes ~5-7 dB degradation degradation
degradation
Conclusion Not usable Enhancements: re- Enhancements:
encode intra MBs, motion estimation
motion compensation refinements
refinements
Adaptive video streaming protocols
› Apple HTTP Live Streaming (HLS) protocol:
– Uses MPEG-TS/H.264 video, and iOS-based clients.
– Has seen wide adoption due to the proliferation of Apple devices (iPhone). (36% of video traffic
in one study)
› The Microsoft Smooth Streaming (MSS) protocol:
– Uses fMP4/H.264(VC1) video, and the Silverlight client.
– In the wired space, it is widely used (e.g. Netflix).
– In the wireless space, it was initially used only on Windows phones. However, MSS streams can
now be converted to MPEG-TS for streaming to Apple devices.
› The Adobe HTTP Dynamic Streaming (HDS) protocol:
– Uses F4F/H.264(VP6) video, and a Flash Player client.
– Has not seen wide adoption in the wireless space.
› MPEG-DASH (Dynamic Adaptive Streaming over HTTP)
Mpeg-dash standard
› Standard ISO/IEC 23009-1 (August 2011)
› Defines a manifest model: Media Presentation Description (MPD)
› Standardized profiles:
– MPEG-2 TS (Main, Simple)
– ISO Base Media File Format (BMFF) (On demand, Live)
› Codec independent (supports H.264, H.265, MPEG-4, …)

› Supporters: Adobe, Akamai, Cisco, Dolby, DTS, Ericsson, Harmonic, Microsoft,
Netflix, Qualcomm, Samsung, …
MPEG-DASH optimization
› Studies on DASH behavior have indicated that purely client-based control of
rate adaptation can lead to adverse behavior (oscillation)
› With client-based rate adaptation, the operator cannot enforce policies on its
users
› A proxy can be used to enforce congestion control by overriding client
commands
Pacing
› Applying sufficient pacing to the video will lead to the client reducing its bit
rate
› Once pacing is removed or decreased the client will switch back to a higher
bit rate
› This could work also for encrypted streams
Manifest re-write
› MSP intercepts MPD file from server
› MSP rewrites MPD by only keeping wanted representations
› Client only “sees” the representations that haven’t been filtered out
› Note: If all representations are eliminated, the YouTube server returns HTTP
progressive download instead
› Risk: If MPD is encrypted (e.g. via HTTPS), this will not be possible
Not implemented
Analytics
› Caching KPIs: e.g.:

– Byte cache hit ratio,
– Video byte cache hit ratio,
– HTTP request cache hit ratio,
– HTTP request cache hit ratio – video
› Video Optimization KPIs: e.g.:

– On-the-fly transcoding compression ratio,
– Offline transcoding compression ratio,
– Overall transcoding compression ratio
Deployment
› Each host (blade) comprises an SLB, a TS and
a VOM
› Each SLB load balances HTTP requests across
the TSs
› Each TS load balances on-the-fly transcoding
requests to a pool of VOMs via ICAP
› Each TS further load balances offline
transcoding requests to a pool of VOMs via
ICAP
› MSP load balances the requests for OTF
transcoding by assigning each session to a
VOM virtual machine in a uniform distribution.
Hence each device IP will always use the same
VOM to allow session management, but all
device IPs will be distributed across the VOMs
in the pool
VO ROADMAP
Available Now (7.0 CP02 GA) Planned 7.1 Roadmap Candidates
Video Optimization Enhanced Video Caching
Radio Friendly Pacing Improved TIC

Dynamic Transcoding
Media Rate Video Pacing
Dynamic Pacing
Caching of Video Content
Rate Control of HLS
Rate Control of MPEG-DASH
Internet Radio Optimization
On-the-fly Transcoding (OEM)
Advanced Analytics
Offline Transcoding (OEM)
Cloud Deployment
Analytics (KPIs)
Cloud Deployment
Virtualized Deployment
Summary
› All techniques available on MSP

› Ericsson touch – integration with RAN
› Virtualized environment

How To Sell VO Part II

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

How To Sell VO Part II

Încărcat de

Drepturi de autor:

Formate disponibile

How to Sell Video

Optimization: capabilities and

HTTP Layer DPI

HLR HSS Paced video

Start-up burst to fill

› Streaming video is delivered in bursts  Utilizes high link-bitrates in the bursts

› Caches unmanaged HTTP content

› Some caching mechanisms have been implemented specifically to support

› The transformations that can be done on video content include:

Description Re-encode Re-quantization Correction loop Re-use prediction Decoding to

Quality No Drift causes ~10 Remaining drift ~1-2 dB Low

– ISO Base Media File Format (BMFF) (On demand, Live)

› Codec independent (supports H.264, H.265, MPEG-4, …)

› Caching KPIs: e.g.:

› Video Optimization KPIs: e.g.:

Radio Friendly Pacing Improved TIC

› All techniques available on MSP

S-ar putea să vă placă și