1 / 6

CDNI Extended Design Team Meeting Virtual Meeting May 29, 2012

Models for adaptive -streaming-aware CDNI - Content Purge draft -brandenburg-cdni-has- 01, section 3.6. CDNI Extended Design Team Meeting Virtual Meeting May 29, 2012 Ray van Brandenburg (ray.vanbrandenburg@tno.nl). Key Considerations regarding Content Purge.

deidra
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-Content Purgedraft-brandenburg-cdni-has-01, section 3.6 CDNI Extended Design Team Meeting Virtual Meeting May 29, 2012 Ray van Brandenburg (ray.vanbrandenburg@tno.nl)

  2. Key Considerations regarding Content Purge • Content Collection may consists of very large number of files (e.g. 100s to 1000s) • Content Provider might ask uCDN to remove all files making up content item X • Depending on how content was ingested from Content Provider to uCDN • uCDN needs to able to relay this information to dCDN

  3. Option 6.1: “Do-Nothing” Approach - 1 • Assumes no HAS awareness in uCDN/dCDN and no additions to CDNI Interfaces • Result: the uCDN will send a individual content purge request to the dCDN for every file making up the Content Collection • i.e. 1000 chunks results in 1000 content purge requests between dCDN and uCDN

  4. Option 6.1: “Do-Nothing” Approach - 2 Effect on CDNI Interfaces: • None Advantages/Drawbacks: + Does not require changes to the CDNI Interfaces or HAS awareness - Large signalling overhead between dCDN and uCDN

  5. Option 6.2: “Purge Identifiers” - 1 • Might be useful to allow uCDN to request removal of all files related to a given Content Collection • By adding single metadata field (i.e. Content Purge ID, CPID), virtual groups of files can be created • CPID can for example be random number • Content Purge Requests can reference this CPID to request removal of all content containing CPID

  6. Option 6.2: “Purge Identifiers” - 2 Effect on CDNI Interfaces: • CDNI Metadata Interface: Add metadata field for indicating Purge Identifier • CDNI Control Interface: Add functionality to be able to send content purge requests containing Purge Identifiers Advantages/Drawbacks: + Allows for efficient purging of content from a dCDN + Does not require HAS awareness on part of dCDN

More Related