ANSI SCTE 214-1 pdf free download

ANSI SCTE 214-1 pdf free download.MPEG DASH for IP-Based Cable Services Part 1: MPD Constraints and Extensions.
8. Signaling Asset Identification 8.1. General AssetIdenti fier elements are used in ISO/IEC 23009-1 to uniquely identify content in periods. This section identifies schemes that may be used in content compliant to this specification. There may be several alternative identifiers applicable to the same content. AssetIdenti fier elements are used for grouping periods with the same content and indicates to DASH client that one is ; continuation of the other. Thus choice of main identifier (carried in AssetIdenti fier) needs to reflect continuity in terms of user interface, random access, and trick modes. Alternate identifiers (carried in Supp1ementalProper ty) are informational and may be used for reporting purposes. As an example, when the same advertisement is shown multiple times, its instances will have same value of Ad-ID, but different AiringID. Use of Ad-ID as AssetIdenti fier will result in DASH client considering the second instance of the advertisement a continuation of the first. In this case, e.g. the UI may show at the start of the second instance progress bar at 50% and advertisement duration of twice its actual duration. Thus AiringID should be used as As setIdenti fier, while Ad-ID should be used as an alternative identifier carried in SupplementalProperty with the same value of @ scheme IdUri In the opposite case, when two periods cary same in-network content which has the same EIDR and a period between them is an advertisement, the two in-network periods are continuation of each other and thus EIDR should be used in AssetIdenti fier, while AiringID of these periods will be different and, if used, it should be used in Suppl ementalProperty Note 1: Alternative single identifier scheme is defined in DASH-IF IOP.9.3. Bandwidth, size, and buffering 9.3.1. Introduction This section formalizes the relationship between the declared bandwidth BW[R], MBT, and segment sizes. The derivations below are a straightforward, albeit lengthy, translation of the requirement in ISO/IEC 23009-1 that if segments of representation R are delivered over a constant bitrate channel with bitrate equal to BW[R] attribute, then each sample with decoding time DT is available for decoding at the media engine by time DT + MBT. Note: In many cases the latter may be a stricter limitation that the ones stated in the sections below, as the discussion below applies to complete (sub)segments, rather than samples. While MBT does specify minimum time sufficient for ensuring continuous playout of a representation, it describes content encoding properties, rather than expected network behavior. Hence a player implementation has to account for realistic network conditions, and this specification provides neither restrictions nor any guidance on these issues.10.1.2. Resolutions and frame rates This specification neither specifies nor requires support for specific operating points (i.e., combination of resolution, frame rate and aspect ratio). The input to encoding process is expected to be in one of the production formats specified in SCTE 215-1 sec. 6.0. At least one representation should have the resolution, frame rate, and aspect ratio listed in SCTE 215-1 Appendix A. Note: Some of the possible derived operating points are specified in ETSI TS 103 285. The latter does not cover some of US-specific operating points.
ANSI SCTE 214-1  pdf download.