Primary and backup HDS stream URLs

Publish HDS streaming content to primary and backup locations.

To avoid interruptions in the distributed system, encoders should be capable of publishing the same content to primary and backup locations.

Encoders should be able to input primary and backup publishing and playback hostnames and primary and backup paths for a given stream. The same content (set-level manifest, stream-level manifest, DRM metadata files, fragments, and bootstrap) should be simultaneously published to primary and backup paths.

Publish URLs

Use this syntax to publish primary and backup streams.

Stream type Hostname Path Example
Primary p-ep{stream_id}.i.akamaientrypoint.net hds/[stream_id]/[event_name] https://p-ep50002.i.akamaientrypoint.net/hds/50002/test79
Backup b-ep{stream_id}.i.akamaientrypoint.net hds/[stream_id]-b/[event_name] https://b-ep50002.i.akamaientrypoint.net/hds/50002-b/test79

Playback URLs

Configure your encoder to generate playback URLs for HDS.
  • Primary Playback path: hds/live/{streamID}/{eventname}/{object}

    Examples:

    • https://testconfig-i.akamaihd.net/hds/live/50002/test79/test79.f4m
    • https://testconfig-i.akamaihd.net/hds/live/50002/test79/5000kbpsSeg100Frag10
  • Backup Playback Path: hds/live/{streamID}-b/{eventname}/{object}

    Examples:

    • https://testconfig-i.akamaihd.net/hds/live/50002-b/test79/test79.f4m
    • https://testconfig-i.akamaihd.net/hds/live/50002-b/test79/5000kbpsSeg100Frag10
  • Base Playback URL: {customerhostname}.-i.akamaihd.net

The HDS player requests the stream-level manifest using the URLs. It then parses information in the stream-level manifest and requests object names by appending to the base URLs in stream-level manifests. The player uses one of these HTTP error responses from the server to request the backup stream content:

  • https://testconfig-i.akamaihd.net/hds/live/50002-b/test79/5000kbpsSeg24Frag41
  • https://testconfig-i.akamaihd.net/hds/live/50002-b/test79/5000kbps.drmmeta