Content for  TS 26.502  Word version:  17.3.0

This example focuses on DASH content distribution with pull-based ingest. The DASH segment packager publishes media segments to an external origin server and the MBSTF pulls them according to the timing model of a DASH presentation specified in an MPD.

The Object ingest base URL remains empty, since the DASH media segments are fetched according to the DASH presentation manifest referenced by the Object Acquisition identifiers property. In this example, the Object ingest base URL and Object distribution base URL are both omitted, resulting in the same URL used for fetching each media segment being used for its distribution.

This example focuses on DASH content distribution with pull-based ingest. The DASH segment packager publishes media segments to an external origin server and the MBSTF pulls them according to the timing model of a DASH presentation specified in an MPD. In this case, the MBS User Service is provisioned to distribute the audio and video segments on separate MBS Distribution Sessions, which are multiplexed onto the same MBS Session.

using separate MBS Distribution Sessions for audio and video The Object ingest base URL is ignored in this case because the media segments are fetched according to the DASH MPD referenced by the Object acquisition identifiers property. In this example, the Object distribution base URL is also omitted, resulting in the same URL used for fetching each media segments being used for its distribution.

This example focuses on generic object distribution using pull-based ingest. In this case, objects are pulled into the MBSTF according to an object manifest.

The URL of the object manifest is provisioned by the MBS Application Provider using the Object acquisition identifiers parameter. In this example, the Object ingest base URL and Object distribution base URL are both omitted, resulting in the same URL used for fetching each object being used for its distribution.