1 / 7

CDNI Extended Design Team Meeting Virtual Meeting May 29, 2012

Models for adaptive -streaming-aware CDNI - Introduction draft -brandenburg-cdni-has- 01, section 1 & 2. CDNI Extended Design Team Meeting Virtual Meeting May 29, 2012 Ray van Brandenburg (ray.vanbrandenburg@tno.nl). Why this draft?.

halil
Download Presentation

CDNI Extended Design Team Meeting Virtual Meeting May 29, 2012

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Models for adaptive-streaming-aware CDNI-Introductiondraft-brandenburg-cdni-has-01, section 1 & 2 CDNI Extended Design Team Meeting Virtual Meeting May 29, 2012 Ray van Brandenburg (ray.vanbrandenburg@tno.nl)

  2. Why this draft? • Although CDNI should be content-agnostic, HAS content poses some unique challenges • Very large number of (possibly distributed) files • Session-less nature makes logging difficult • Manifest file poses problems for Request Routing • Etc… • This draft… • Is meant to spur discussion on HAS and CDNI • Introduces terminology • Discusses some of the problem areas when combing HAS and CDNI • Introduces different options for level of HAS awareness in CDNI • Allows WG to make well-informed decision on which models to support

  3. Background - 1 • HAS as an umbrella term for: • Apple HLS, MPEG DASH, Microsoft Smooth Streaming, Adobe HDS, etc… • Characteristics: • Session less, pull-based, adaptive-bitrate, chunked

  4. Background - 2 • With traditional (non-HAS) media delivery methods: • Content ≈ single file/stream • With HAS: • Content ≠ single file/stream • Content Collection ≡ Set of all files making up the same content item Original Content Manifest Representation 1 Manifest Segment 1 Segment 2 Segment n Representation 2 Manifest Fragment n Fragment 1 Fragment 2

  5. Background - 3 • Three different methods of identifying chunks in a manifest file are in use: • Relative Locator segments/segment1_1.ts (relative to location of manifest file) • Absolute URL with Redirection http://req-routing.cdn.example.com/content_req?content=content_1&segment=seg1_1.ts • Absolute URL without Redirection http://surrogate.cdn.example. com/content_1/segments/segment1_1.ts

  6. CDNI aspects affected by HAS Six potential problem areas have been defined: • File Management (section 3.1) • Content Acquisition (section 3.2) • Content Purge (section 3.6) • Request Routing (section 3.3) • Logging (section 3.4) • URL Signing (section 3.5)

  7. Structure • Several options are presented for dealing with each potential problem area • Goal: • Allow CDNI to support HAS in a scalable manner (necessary) • Finding right balance between adding complexity to CDNI Interfaces and allowing for additional efficiency and flexibility (nice to have) • Presented options range from having no HAS awareness at all to ‘Full’ HAS awareness

More Related