Skip to content

StreamPackage Overview โ€‹

Updated

StreamPackage is a packaging / origin service that takes an encoded live stream and serves playlists and segments for playback. If StreamLive is the stage that produces the resolutions and bitrates, StreamPackage is the stage that makes those results available for players and CDN to pull.

End-to-End Flow โ€‹

For example, you send the 1080p and 720p outputs produced by StreamLive to StreamPackage. The player first reads the list of renditions from the HLS master playlist, then requests the media playlist and segments of the selected rendition in turn. Once CDN is attached, viewer requests are served through CDN.

Packaging and viewer distribution

The per-rendition encoding must be prepared upstream.

The Four Console Components โ€‹

ComponentRoleValues to check
ChannelThe management unit that binds inputs and outputs togetherRegion, channel ID, input protocol
InputThe ingest point where the publishing system pushes the streamThe two auto-generated input addresses and the HTTP authentication status
Output EndpointThe point where players and CDN pull the streamOutput type, playback list name, playback URL
CDNThe distribution path that reaches viewersCSS integration permissions, playback domain, DNS, HTTPS

Input addresses are for publishing, endpoint addresses are for playback, and the channel ID identifies the resource.

TaskScreen to openResult
Create an input channelChannel management โ†’ Create ChannelA channel ID and two input addresses
Input authenticationChannel details โ†’ Input โ†’ AuthenticationThe HTTP authentication to apply on the publishing side
Create a playback addressChannel details โ†’ Output Endpoint โ†’ Create Output EndpointA HLS/DASH or supported CMAF output address
Play back a past point in timeTime-shifted Viewing in Output EndpointPlayback from a specified point within the retention window
CSS distributionChannel details โ†’ CDNCross-service permissions and playback domain binding
Save a past segmentHarvest JobsA job that stores a specified range in COS
Ad insertionServer-Side Ad InsertionA separate ad configuration linking ADS / source / sessions
Scheduled channelChannel Linear AssemblyBuilding a linear channel from sources and program scheduling
Operational checksUsage Statistics / Log ManagementReviewing usage and request / processing logs

The basic integration is completed on three screens: the channel's Input, Output Endpoint, and CDN. Harvest, ad insertion, and scheduled channels are separate features. Review the screens and input values in the order Create a channel โ†’ Endpoints โ†’ CDN.

Basic Setup Order โ€‹

  1. Create a channel: Select the region and the input protocol.
  2. Connect publishing: Specify the StreamPackage channel ID in the StreamLive output group, or configure the input address and required credentials in your external publishing system.
  3. Create an endpoint: Specify the output type and the playback list name.
  4. Verify input / output: Send a real signal and confirm that the playlist and segments are being updated.
  5. Attach CDN: Bind the cross-service permissions and the playback domain, then verify DNS / HTTPS / playback.

For a first-time setup, confirm basic playback with a HLS input and a HLS output first.

Input and Output Formats โ€‹

ItemExample supported configurationSelection criteria
Channel inputHLS, DASHThe protocol your publishing system sends
Basic outputThe HLS or DASH that corresponds to the input protocolTarget player compatibility
Additional outputs for a HLS inputCMAF-HLS, CMAF-DASHRepackaging and target device support

The console distinguishes between the CMAF-HLS and CMAF-DASH output types. CMAF repackaging of DRM inputs and similar cases have restrictions, so check Endpoint configuration.

Extensions Beyond Basic Playback โ€‹

  • Time shifting: Play back from a past point within the retention window.
  • Harvest Job: Store a specified past segment in COS.
  • SSAI: Integrate with an ad server to assemble ad paths into the playlist for each viewing session.

The following figure shows how the plain playback path and the ad insertion path differ in role.

Plain playback and ad insertion paths

Criteria for a Completed Setup โ€‹

Verify source ingest, playlist updates, segment responses, and playback over the CDN domain separately. If you need redundancy, send the signal to both inputs and verify failover separately as well.

Next Steps and Reference Documents โ€‹

Built with VitePress ยท Deployed on Tencent EdgeOne Pages