NEA-Live and NEA-DVR - Deep Dive

Product Presentation
(Technical deep dive)
October, 2020
Technical deep dive
1. Product Positionning
2. Just in Time Packaging
3. Advanced recording
4. Scalable Architecture
5. Efficient Storage
6. Ad enabling
7. Low Latency
8. Roadmap
9. Use Cases
Technical deep dive
6. Ad enabling
7. Low Latency
8. Roadmap
9. Use Cases
ORIGIN & CDN in Video Delivery Chain
CHANNEL
ORIGINATION DAI
SERVICE
DRM
PLATFORM
LINEAR/VOD ORIGIN CDN PLAYERS

CONTRIBUTION
HEADEND PACKAGING
DISTRIBUTION
BROADCAST CLOUD DVR

STATMUX STORAGE
MULTICAST ABR
& PEER TO PEER
TITAN Solution NEA Solution
Stronger Together ATEME © 1991-2020. Confidential & Proprietary

4
Origin/Packaging
PACKAGER ORIGIN
Package from one pivot format Publish content so multiple users

(TS) to multiple OTT streaming can watch it at the same time (one
protocols (HLS, DASH, MSS). to many).
Allow to reach all screens (Mobile, Source of all OTT streams in the
Tablet, PC, STB, Smart TVs). platform (Live, Catch-up, nPVR,
VOD).

5
NEA-Live & NEA-DVR Origin/Packager
Live & TSTV Live, TSTV, CUTV, cDVR & VOD
• Live & Time shift applications • Live & Time Shift, Catch-Up & Cloud DVR applications
• Just-in-time Packaging & Encryption • VOD applications
• Up to 200 Channels per server • Just-in-time Packaging & Encryption
• Up to 8 hours standard rolling buffer • Up to 300 Channels per cluster
• (1+1) Architecture • Support Standard & Infinite Buffer (several years)
• Embedded Distributed Storage (EDS) available
• Up to 4 PB per cluster
• Dual Site architecture • Can manage millions of assets
• Multi-cluster architecture • Scale-out cluster Architecture
• CMS Integration • Can be used for Ingest / DB / Playout
• Multi-DRM Integration

6
Technical deep dive
6. Ad enabling
7. Low Latency
8. Roadmap
9. Use Cases
JITP – Just In Time Packaging - Overview
NEA-Live Just-In-Time Packaging
• Just in time packaging for live & non-linear services
Multi Audio
• Most popular protocols available (HLS, DASH, MSS) DRM
• Enable Subtitling packaging (Text & Picture)

• Supporting multi-audio and languages
$
• Manifest conditioning ready for DAI SUBTITLES
AD insertion
• Anevia In-house packaging engine design
• Ultra-Low Latency (Roadmap)
Benefits
• Resources optimization (network, CPU)
• Make your service available on all devices
• Future-proofness of the platform
First HEVC HLS fMP4 4K streaming

8
JITP – Input formats
Ingest Protocol
• Live: Multi-Bitrate Transport Stream EBP compliant
- Redundancy built-in
- SCTE-35 markers passthrough with frame accuracy
• File: ismv or fmp4
• Video:
- H264 / HEVC
- HDR Support
- Thumbnails: JPEG, PNG
• Audio
- AAC-LC ADTS
- HE-AAC v1, HE-AAC v2
- Dolby Digital+ (EC-3)

9
JITP – HLS and DASH Packaging
• v1 to v8 (target all devices/players supporting HLS) • $Time$ & $Number$

• TS or fMP4 • DASH Manifest conditioning
• Manifest conditioning (full support for Ad insertion) • Support of multiple video framerates
• Audio Only (No video required) • VOD/nPVR thumbnails
• I-Frame Only (Moving in the video) • Audio Only (No video required)
• Audio/video filtering • Audio/video filtering
• Metadata for HLS live output • Metadata for DASH live output (consistency with HLS)
• Support HDCP - Standard-based
• Shared chunks between stream adaptation - From Web GUI or API
• Low Latency support (roadmap) • CMAF Low latency support

10
JITP – 3D Chunk Sharing
Chunk Sharing between Profiles
NEA-DVR Chunk Sharing

Profile 1 – 5 Mbps
• Different publish point for each device type
• Profiles sharing: different manifests pointing to the same Manifest STB
chunks whenever possible Profile 3 – 1.5 Mbps Shared Chunks
• Services sharing: different services (Live/CUTV/cDVR)
with different manifest pointing to same Live chunks Profile 5 – 0.5 Mbps Manifest Mobile
• DASH and HLS relying on fMP4 sharing (roadmap)
Chunk Sharing between Services
#4 #3 #2 #1 #1
Benefits Live Live User #1
time
Live Chunk
• Better user experience on non-linear services Backbone

Network #1
time
#3 #2 #1
• Strong bandwidth savings on the CDN (up to 30%) CUTV
CUTV User #2
time
#2 #1 #1
Cloud DVR Cloud DVR User #3
ORIGIN SERVER CDN CACHE

11
JITP – Subtitles
Subtitles Input Subtitles output
HLS DASH MSS
WebVTT or 608/708 or
MBTS (EIA-608/708) TTML or EBU-TT TTML or EBU-TT
SMPTE-TT
DVB-SUB passthrough
MBTS (DVB-SUB) SMPTE-TT SMPTE-TT
TTML or SMPTE-TT
ENCODERS DVB-TXT MULTISCREEN

MBTS (DVB-TXT) TTML or EBU-TT TTML or EBU-TT
WebVTT

12
JITP – DRM Integration
Several interfaces are available
• Previous integrations were done on the NEA-DVR itself

• CPIX defines a standard for DRM exchanges between
all the concerned head-end functions
• The DRM-Gateway allows DRM integrations and
updates without impacting the core product
• DRM integration matrix
• Key rotation possible

13
JITP – Ad Enabling
Ad break
#EXTM3U
SCTE CUE-OUT SCTE CUE-IN #EXT-X-VERSION:1
#EXT-X-MEDIA-SEQUENCE:11853650
#EXT-X-TARGETDURATION:2
#1 #2 #3 #4 #5 #6 #7 #8 #9 #10 #EXTINF:2.000, no desc
url-chunk-1.ts
#EXTINF:2.000, no desc
url-chunk-2.ts
SCTE-35 Manifest Conditioning (aka Ad Enabling) url-chunk-3.ts
#EXT-X-CUE-OUT:DURATION=9,ID=2313245786
url-chunk-4.ts
• Detect incoming SCTE-35 markers #EXTINF:2.000, no desc
url-chunk-5.ts
• Create different chunk size to align with markers #EXTINF:2.000, no desc
url-chunk-6.ts
• Add markers in the Manifest #EXTINF:2.000, no desc
url-chunk-7.ts
url-chunk-8.ts
• Manifest ready for: #EXT-X-CUE-IN:DURATION=9,ID=2313245786
ü SSAI – Requires Manifest Manipulator url-chunk-9.ts
ü CSAI – Requires Player functionnality url-chunk-10.ts

14
Technical deep dive
6. Ad enabling
7. Low Latency
8. Roadmap
9. Use Cases
Software technology #2- Recording optimisation
Recording #1 Recording #2 Recording #3 Recording #4 Recording #5 Recording #6
Live channel
Sparse channel Catchup / Start over retention

Segments
With optimised recording, the chunks are stored only once.

16
Recording – Infinite Buffer
NEA-DVR Infinite Buffer
• Relying on an extended circular buffer (can be 2 years)
• Minimum retention time = 100% is recorded
• End of Minimum retention time to end of Maximum
retention time = we keep only what has been recorded
• 10 minutes segments so light overhead
• DB storing assets segments indexing and association
to each user
• Integrated Scheduling capabilities
Benefits
• Field proven and widely deployed technology Example of a Cloud DVR service
• “Shared copy” experience with optimized storage &

minimized bandwidth usage on CDN
• Performance optimization (IOPS – write only once)

17
Recording – Timeshift
NEA-DVR Player
Provide me live channel URL (): manifest_URL
GET manifest URL (): manifest
ß Live Window length à
Open playlist
Maximum retention time Minimum retention time
GET chunk (): chunk
GET chunk (): chunk

18
Recording – Replay/Catchup/Start-Over On The Fly
NEA-DVR Player
Provide me live channel URL (): manifest_URL
GET manifest URL (startDate ; endDate ): manifest
ß Requested duration à
Closed playlist
GET chunk (): chunk
GET chunk (): chunk

19
Recording – Cloud-DVR Time-Based recording
NEA-DVR Player
Record event (…)
Record (channelID ; startDate ; endDate ) : assetID
GET my recordings(…) : assetsID
GET manifest URL (assetID): manifest
Closed playlist

20
Technical deep dive
6. Ad enabling
7. Low Latency
8. Roadmap
9. Use Cases
Standalone Architecture
NEA-Live Standalone architecture
• Active – Hot spare redundancy scheme
• Buffer is stored twice
Servers in 1+1 provides all the functions

• Ingest
• Database management & central API interface
• Packaging, scrambling and playout
Performances
• 1+1 redundancy
• Up to 2Gbps of input bandwidth or 200 channels
• Up to 4 Gbps playout capacity
• 8 hours buffer max
• Auto-failover

22
Scalability reminder
Scales with #services
Usage patterns
Live
• Stable & intensive
• Steady growth
Time Time Time
• Variable peaks
Time
• Viewers’ behaviour
ORIGIN
ENCODING STORAGE PACKAGING DELIVERY
Scales with #subscribers

23
The maths behind cloud DVR scalability
A difficult equation

24
Hyper-converged approach
Hyper-converged infrastructure
In a hyper-convergence environment all elements of the storage and compute components are
optimised to work together on a single commodity appliance from a single vendor. The term is a
neologism of converged infrastructure.
Standard infrastructure: Dedicated storage on NAS and Hyper-converged infrastructure: Storage and
compute on commodity HW compute on commodity HW

25
Scale-Out Architecture
CDN
NEA-DVR Scale Out architecture ENCODING
• Scale independently each key sizing factor:

> Channels
> Storage
Shared Storage
> Streaming capacity
• Organized around a shared storage (live buffers & files) INGEST
PLAYOUT
• Dedicated DB servers, up to 12 nodes (ingest/playout)
• Full redundancy (ingest / DB / Playout) DATABASE
Benefits
• Scaling better than 1+1 architecture
• Field proven and widely deployed
• Take full advantage of EDS (cf. next slide)
Flow Service in Telecom Argentina – 2M OTT Subs

26
Scale-Out Architecture (2)
Add a server/Node
• Increase IOPS (streaming)
• Increase CPU (packaging)
• Increase Storage (cDVR)
Ingest Database Playout
• Up to 300 Channels or 3 Gbps for 24 HDDs nodes • Asset information • Up to 5 Gbps for 24 HDDs nodes
• Up to 100 Channels or 1 Gbps for 8 HDDs nodes • Link to Service platform • Up to 3 Gbps for 8 HDDs nodes
• Max 300 channels per cluster recommended • 1+1 redundancy • N+P Redundancy
• 1+1 redundancy • Can be embedded in Playout servers • Storage (option)
• Auto-failover
• Storage (option)
Up to 12 nodes per cluster

Multi-cluster possible
27
Disaster recovery / Dual-site
Same deployment on 2 different sites:

Site A ü Live TV content ingested on both sites
ü Same archives on both sites (chunking synchronization)
ü Double capacity
Redundancy:
ü Synchronisation between sites

ü Self-healing mechanism
ü Active-Active scheme
Site B

28
Disaster recovery / Dual-site (2)
Site A
Main
Timestamps
DB synchronisation
synchronisation
Main
Netplus Dual Site Architecture
Site B

29
MULTI-CLUSTER Deployments
NEA-DVR Multi-Cluster & Dual Site architectures

• NEA-DVR proxy acting as abstraction layer for API
interface with Services Platform
Benefits
• Highly reliable architecture with disaster recovery
• Increase streaming capacity with multi-cluster
architecture
Service Delivery
Platform

30
Easy Ecosystem integration
NEA-DVR Ecosystem Integration
Players
• Open APIs, easy project customization
• DRM Gateway as a multi-DRM connector
• NEA-DVR Proxy as Service Platform connector HLS, DASH
• New DRM or Service Platform integration < 4 weeks

DRM CPIX
• Many Players validated (Subtitles, Extended playlist,…)
• Non-linear services integration
3rd Party CPIX
API Anevia
API
Anevia
API
3rd Party
Benefits API
• Open and agnostic solution, can fit in any platform

SDP
• All services integration with SDPs (VOD, CUTV, cDVR)
• Unique user experience (e.g. start-over, subtitles, ULL..)

31
Technical deep dive
6. Ad enabling
7. Low Latency
8. Roadmap
9. Use Cases
Capacity vs. IOPS requirements
Video services require different IOPS /

capacity
TIMESHIFT
IOPS REQUIREMENTS
CATCHUP
REPLAY
CLOUD DVR
Most popular
content
CLOUD DVR
old assets
CAPACITY REQUIREMENTS

33
33
Hyper-converged approach benefits of distributed storage
The high number of disks

deployed provides the required
total IOPS for cloud DVR
applications
TIMESHIFT
IOPS REQUIREMENTS
CATCHUP
REPLAY
CLOUD DVR
Most popular
content
CLOUD DVR
old assets
CAPACITY REQUIREMENTS

34
34
Hyper-converged approach: True storage efficiency

35
35
Open Multi-Tier Storage
First Tier « Performance »

§ SSD is used for a few hours after live (e.g. 4 hrs)
Second Tier « Capacity »

§ Using a hyper-converged architecture
§ Using the Embedded Distributed Storage technology
§ Content is recorded in an optimised buffer
Third Tier « Archive »

§ Using a scale-out storage (NAS or object based)
§ Content is extracted to this storage

36
EDS – High Performance & Density Video Storage
EDS CLUSTER Add an EDS server
ARCHITECTURE
NEA-DVR Embedded Distributed Storage • Increase Storage (cDVR)
• Increase IOPS (streaming)
• Distributed storage “cluster” architecture • Increase CPU (packaging)
• Runs on COTS servers with internal HDD storage

• Resilient to the loss of up to 2 servers / cluster
• Easy to grow storage and streaming capabilities
• Up to 4 PB / 50 Gbps streaming in a single cluster
• 3x to 4x better performance than high-end NAS
WINNER
NAS EDS
Benefits 4 PB storage
• High density and high performance compared to NAS

• Easy to scale-up origin for storage & streaming
• Reduce operational costs
300% Performance
50% Rackspace

37
EDS – Erasure coding benefits
= Embedded Distributed Storage
Hyper convergent storage solution

- Disk embedded in the processing nodes
- Saves rack space
- Reduces hardware costs
- Processing capacity used for both functional and storage
Erasure coding protects data by breaking it into shards that are

parity encoded and the stored across multiple locations
Source: sandisk
- Focus on protecting data not hardware
- Only need a subset of the shards to access the data
- In case of hardware failure the data is still accessible
- Storage overhead is low compared to other protections

38
EDS – Erasure coding (2)
File
Played data (play)
EDS layout 0 EDS layout 1

• Minimum cluster size : 4 servers • Minimum cluster size : 8 servers
• Erasure coding 3/2 • Erasure coding 6/4
• Allows the defect of 1 node without data loss • Allows the defect of 2 nodes without data loss

39
EDS – Open Multi-Tier storage
NEA-DVR Multi-Tiers Storage (MTS)
• EDS is a proven and high-performance technology
Tier 1 storage Tier 2 storage Cold storage
• Multi-tiers storage approach is relevant to re-use
existing NAS storage or deal with “cold” content
• MTS still relies upon infinite buffer technology Move files to
Tier 2 storage
• After a period of time (configurable) part of the infinite
buffer will be transferred to external storage
• As of today supporting NFS, S3 (object) is a roadmap
candidate
Minimum retention time

on Tier 1 storage
Benefits High performance storage
• Re-use existing storage capacity
• Secure overall system performance Infinite archive
Storage mover
• Enabling external storage scalability to reduce cost

40
EDS - Production example of performances comparison
Streaming performance ratio = EDS is 3x faster than NAS

41
Technical deep dive
6. Ad enabling
7. Low Latency
8. Roadmap
9. Use Cases
Manifest Conditionning
Ad break
#EXTM3U
SCTE CUE-OUT SCTE CUE-IN #EXT-X-VERSION:1
#1 #2 #3 #4 #5 #6 #7 #8 #9 #10 #EXTINF:2.000, no desc
url-chunk-1.ts
url-chunk-2.ts
SCTE-35 Manifest Conditioning (aka Ad Enabling) #EXTINF:1.200, no desc
url-chunk-3.ts
• Detect incoming SCTE-35 markers url-chunk-4.ts
url-chunk-5.ts
• Create different chunk size to align with markers #EXTINF:2.000, no desc
url-chunk-6.ts
• Add markers in the Manifest #EXTINF:2.000, no desc
url-chunk-7.ts
url-chunk-8.ts
• Manifest ready for: #EXT-X-CUE-IN:DURATION=9,ID=2313245786
ü SSAI – Requires Manifest Manipulator url-chunk-9.ts
ü CSAI – Requires Player functionnality url-chunk-10.ts

43
Stream Conditionning Requirements
#EXTM3U
Stream Conditioning Requirements #EXT-X-VERSION:1
• SCTE-35 IDR inputs #EXTINF:2.000, no desc
url-chunk-1.ts
• EBP markers are mandatory #EXTINF:2.000, no desc
url-chunk-2.ts
• Frame accurate (EBP needs to be set correctly by the encoder) #EXTINF:1.200, no desc
url-chunk-3.ts
• Encoder must put IDR + EBP immediately after splice #EXTINF:2.000, no desc
url-chunk-4.ts
• SCTE-35 CUE OUT must provide the break duration (for the MM) #EXTINF:2.000, no desc
url-chunk-5.ts
• SCTE-35 CUE IN is mandatory (for the MM) #EXTINF:2.000, no desc
url-chunk-6.ts
url-chunk-7.ts
url-chunk-8.ts
#EXT-X-CUE-IN:DURATION=9,ID=2313245786
url-chunk-9.ts
url-chunk-10.ts

44
HLS & DASH Support
• HLS
• TS (muxed or demuxed)
• Fmp4
• DASH
• $time only
• Multi-period

45
Technical deep dive
6. Ad enabling
7. Low Latency
8. Roadmap
9. Use Cases
Latencies in the ecosystem
less impact
4. CDN
• Typically ~200ms
3. Encoder
• Processing latency video quality
• Typically ~1-5 sec
2. OTT Packager
• Bufferizes to create OTT segments
• Typically ~6 sec. (if segment size is 6 sec)
1. Player
• Bufferizes for resiliency
• Typically ~30 sec.
greater impact

47
Solutions
Existing LIVE ULL solution relies on
Ultra low latency OTT
• NEA-LIVE Push (embedded packager) Encoder Packager Origin CDN
• NEA-CDN with ULL features: NEA-CDN 5.2 + pusher

• Supported format: LL-DASH only
• Low latency tested players:
Optimized setup for lowest overall latency
Next steps on LIVE ULL solution relies on PUSH
• GENOVA-Live + NEA-LIVE (Separate packager)

• NEA-CDN with ULL features: NEA-CDN 5.3 or Akamai
• Targeted formats:
• Q4 2020: LL-HLS (official specs)
• H1-2021: LL-DASH
• Low latency targeted players: Quicktime on safari

48
Technical deep dive
6. Ad enabling
7. Low Latency
8. Roadmap
9. Use Cases
ROADMAP
NEA-LIVE/DVR 4.8 NEA-LIVE/DVR 4.9 NEA-LIVE/DVR 4.10 NEA-LIVE/DVR

PACKAGER
• Multi-tier storage management • LL-HLS initial support • LL-HLS updates • ULL updates
ORIGIN
• Thumbnail tiling (mosaic) for nPVR & VOD • Chunk concatenation (DASH $Time$) • LL-DASH • CPIX 2.1 Step 1
• Multicast input redundancy • Wipe synchro master-slave • Per track HDCP mode • Multi codec channels
• Chunk sharing enhancements • Prometheus monitoring (System) • CMAF chunk sharing (HLS fMP4 – DASH)
• Fractional HLS chunk duration • CBCS for DASH
• HDR support (HDR,HLG,PQ10,HDR10) • ISMC1
• DASH multiple MPD Periods key rotation
2020 2021
Micro Services Transformation
Delivered On-going Scheduled

50
Technical deep dive
6. Ad enabling
7. Low Latency
8. Roadmap
9. Use Cases
myCANAL OTT Service (1)
ID Card
Services Deployed
• 1st PayTV operator in France
• 2nd Pay TV in Poland • Live TV – 400+ Channels
• 5M subs in France, 4M Overseas • TimeShift / Restart

• Services on Sat, IPTV, DTT, OTT • Catch-Up TV – 8 hours
• More than 1M active OTT users • VOD

• Download to Go
Why Anevia?
Multiscreen Availabillity
• OTT expertise since 2011
• 1st Just-In-Time Packaging • Canal+ OTT STBs
Ecosystem • Mobile / Tablets
• Multiple protocols / DRM support
• Extended Live Window • PC
• Integration & Local support • Apple TV 4K

52
myCANAL OTT Service (2)
Origin/Packager System
• 6+6 NEA-LIVE appliances IN HQ
• NEA-LIVE appliance in Overseas sites
• NEA-DVR virtualized for VOD
Origin/Packager features
• 400+ Live Channels
• LiveTV Timeshift 8h
• Frame-accurate Startover
• Full HD and 4K Services
• HLS, MSS, DASH & Multi DRM
• Subtitles (WebVTT, TTML)
Architecture & CDN
• Shield Cache, multi CDN
• Distributed CDN
• Dual Site architecture

53
BliBlaBlo OTT Service
ID Card Services Deployed
• Best TV Service in Switzerland

• Live TV – 200+ Channels
• OTT Service on all devices
• Startover / Time Shift TV
• Delivered to more than 13 cable
• Catch TV 7 Days
operators in Switzerland
• Cloud DVR 130 Channels
• More than 150K subscribers
• PPV on Sport Events
• Exclusive rights for sports
• Cloud DVR launched in 2011
Multiscreen Availabillity
Why Anevia?
• Android TV STB
• Long term partnership • Mobile / Tablets (iOS / Android)
Ecosystem • PC / browsers
• Cloud DVR expertise
• Disaster recovery solution
• Scalable CDN
• Local support & track records

54
BliBlaBlo OTT Service
• USAGE
72k CDVR subscribers
20K CDVR recordings per day
90k Replay sessions per day
80 Gbps streaming at peak
Move to Diskless STBs: Return rate divided by 10
• NEA-DVR/NEA-DB
Packaging to HLS, MSS
Tier 1 storage – SSD in NEA-CACHE
Tier 2 storage: EDS in NEA-DVR – Contents < 90 days
Tier 3 storage: Scality Ring – Contents > 90 days
• NEA-CACHE/NEA-BALANCER
CDN Layer 1: SHIELD cache protect the Origins
CDN Layer 2: 8 EDGE servers close to the end-users
NEA-CDN BALANCER on two sites
• Disaster Recovery / dual site architecture

55
Conclusion
Just in Time Advanced Scalable Efficient Ad enabling Low Latency

Packaging recording Architecture Storage

56
YOUR NEXT GENERATION TV, NOW
FACT SHEET Stronger Together
• Application: Live, PauseTV, Start-Over • Input format: Multi Bitrate TS
• Versions: NEA-Live Push (pure Packager) & • Output format: HLS, DASH, MSS
NEA-Live (Origin/Packager) – embedded GUI
• Recording: up to 8 Hours, standard rolling buffer
• Running environment: Bare metal (HPE) or
Virtual Machine • DRM supported: Fairplay, Widevine, Playready
• Capabilities: Up to 200 Channels per server • Input capacity (HPE): up to 2 Gbps
• Redundancy / Architecture : 1+1 active/active • Output Capacity (HPE) : 4 Gbps ~4K concurrent sessions
with dual input capabilities
FACT SHEET Stronger Together
• Application: Live, TSTV, CUTV, cDVR & VOD • Input format: Multi Bitrate TS
• Running environment: Bare metal (HPE • Output format: HLS, DASH, MSS
recommended)
• DRM supported: Fairplay, Widevine, Playready
• Capabilities: Up to 300 Channels per Cluster
recommended • Input capacity (HPE): up to 3 Gbps per pair of ingesters
• Architecture : Cluster architecture. 1+1 for ingest • Storage capacity (HPE): up to 4 PB per cluster (2.4 PB
and DB, N+P for playout effective)
• Scalablity: no limit thanks to multi-cluster solution • Output Capacity (HPE): 50 Gbps ~ 50K concurrent
sessions per cluster
• Recording: limited by storage capacity mainly,
supports standard buffer and infinite buffer

NEA-Live and NEA-DVR - Deep Dive

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NEA-Live and NEA-DVR - Deep Dive

Uploaded by

Copyright:

Available Formats

Product Presentation

(Technical deep dive)

LINEAR/VOD ORIGIN CDN PLAYERS

BROADCAST CLOUD DVR

TITAN Solution NEA Solution

Stronger Together ATEME © 1991-2020. Confidential & Proprietary

Package from one pivot format Publish content so multiple users

Stronger Together ATEME © 1991-2020. Confidential & Proprietary

Live & TSTV Live, TSTV, CUTV, cDVR & VOD

Stronger Together ATEME © 1991-2020. Confidential & Proprietary

• Enable Subtitling packaging (Text & Picture)

First HEVC HLS fMP4 4K streaming

Stronger Together ATEME © 1991-2020. Confidential & Proprietary

• File: ismv or fmp4

Stronger Together ATEME © 1991-2020. Confidential & Proprietary

• v1 to v8 (target all devices/players supporting HLS) • $Time$ & $Number$

Stronger Together ATEME © 1991-2020. Confidential & Proprietary

NEA-DVR Chunk Sharing

• DASH and HLS relying on fMP4 sharing (roadmap)

Chunk Sharing between Services

• Better user experience on non-linear services Backbone

Stronger Together ATEME © 1991-2020. Confidential & Proprietary

Subtitles Input Subtitles output

HLS DASH MSS

ENCODERS DVB-TXT MULTISCREEN

Stronger Together ATEME © 1991-2020. Confidential & Proprietary

Several interfaces are available

• Previous integrations were done on the NEA-DVR itself

• DRM integration matrix

• Key rotation possible

Stronger Together ATEME © 1991-2020. Confidential & Proprietary

Stronger Together ATEME © 1991-2020. Confidential & Proprietary

Recording #1 Recording #2 Recording #3 Recording #4 Recording #5 Recording #6

Sparse channel Catchup / Start over retention

With optimised recording, the chunks are stored only once.

Stronger Together ATEME © 1991-2020. Confidential & Proprietary

• “Shared copy” experience with optimized storage &

Stronger Together ATEME © 1991-2020. Confidential & Proprietary

Provide me live channel URL (): manifest_URL

GET manifest URL (): manifest

ß Live Window length à

GET chunk (): chunk

GET chunk (): chunk

Stronger Together ATEME © 1991-2020. Confidential & Proprietary

Provide me live channel URL (): manifest_URL

GET manifest URL (startDate ; endDate ): manifest

GET chunk (): chunk

GET chunk (): chunk

Stronger Together ATEME © 1991-2020. Confidential & Proprietary

Record event (…)

Record (channelID ; startDate ; endDate ) : assetID

GET my recordings(…) : assetsID

GET manifest URL (assetID): manifest

Stronger Together ATEME © 1991-2020. Confidential & Proprietary

Servers in 1+1 provides all the functions

Stronger Together ATEME © 1991-2020. Confidential & Proprietary

Scales with #services

Scales with #subscribers

Stronger Together ATEME © 1991-2020. Confidential & Proprietary

Stronger Together ATEME © 1991-2020. Confidential & Proprietary

Stronger Together ATEME © 1991-2020. Confidential & Proprietary

• Scale independently each key sizing factor:

Flow Service in Telecom Argentina – 2M OTT Subs

Stronger Together ATEME © 1991-2020. Confidential & Proprietary