hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 11 Timelines in Transport Stream adaptation fields | |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 11.1 General | This clause defines a mechanism for the carriage of a timeline in the adaptation header of transport stream packets: • Clause 11.3 defines the use of a mechanism published by MPEG in July 2015 as an amendment to ISO/IEC 13818-1 [6]. NOTE: Clause 11.2 in an earlier version of the present document defined another mechani... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 11.2 Void | |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 11.3 Timed External Media Information (TEMI) | |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 11.3.1 General | Adaption field descriptors for Timed External Media Information (TEMI) is a Draft Amendment (DAM) to the MPEG Systems specification ISO/IEC 13818-1 [6] that defines a mechanism for carriage of a timeline in the adaptation field of a transport stream packet that contains a PES stream with PTS declared in the PES header.... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 11.3.2 Timeline Selector for an MPEG TEMI timeline | The format for a timeline selector for a temi_timeline is shown by the following Augmented BNF (as defined in IETF RFC 5234 [4]) rule definition for temi-timeline-selector: temi-timeline-selector = "urn:dvb:css:timeline:temi:" component-tag ":" timeline-id component-tag is the base-ten integer representation of the val... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 11.3.3 Interpretation of a temi_timeline_descriptor | The TV Device shall decode a temi_timeline_descriptors as defined in [25]. If the has_timestamp field of a temi_timeline_descriptor is 1 or 2 then the timeline tick value is taken from the media_timestamp field and the tick rate is determined from the timescale field. The unitsPerTick of the timeline shall be 1 and the... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 11.3.4 Determining Disappearance of a TEMI timeline (informative) | A TV Device is faced with the challenge of deciding both when a previously seen TEMI timeline has disappeared, and when a TEMI timeline that it is looking for is not present. Firstly, as the use of PMT signalling to indicate the TEMI timeline is not required, there is no explicit in stream signalling of the presence or... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 11.3.5 TEMI timelines and bitstream manipulation (informative) | Certain operations in the transmission of content, e.g. splicing of a video component might result in the temporary disappearance of a TEMI timeline. As a TV Device is unable to differentiate between the end of a TEMI timeline (especially if it has only just tuned to a channel) and one that is temporarily disappeared w... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 12 Connection and playback session management | A TV Device and a CSA engaged in synchronized playback normally use the CSS-WC interface (see clause 8), in conjunction with at least either the CSS-CII interface (see clause 6), the CSS-TS interface (see clause 9), or the CSS-TE interface (see clause 10). Under certain circumstances, they may also use all four interfa... |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 1 Scope | The scope of the present document is to describe the framework and architecture used by subsequent parts of this multi- part deliverable that allow for new user experiences through companion devices to be provided to the full set of DVB services. As such, the present document is abstracted from any one delivery mechani... |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 2 References | |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. NOTE: While any hyperlinks in... |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply: CDN Content Delivery Network CoD Content on Demand CORS Cross Origin Resource Sharing CSA Companion Screen Application CSS-CII Interface for Content Identification and other Information CSS-DA Interface for Discovery and Association CSS-LP Int... |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 4 Overview | |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 4.1 General | The various parts that make up this multi-part deliverable provide a complementary set of solutions that can be combined to enable companion devices to support new user experiences for broadcast and Content on Demand (CoD) service consumption. There is no requirement that all parts be implemented as the parts provide a... |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 4.2 Background | In the generic architecture used for this multi-part deliverable, the presence of internet connections to all devices is assumed. From this assumption, it follows that services can be provided to devices from the internet, e.g. cloud services, and that these services can be used to augment existing broadcast and CoD se... |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 4.3 Document structure | The remainder of the present document covers two areas. The first area is covered in clauses 5 and 6 and it provides the descriptions of key concepts (in clause 5) and the generic architecture (in clause 6). The second area, covered in clause 7 onwards, describes and introduces the functionality provided by each part o... |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 5 Functional roles, concepts and relationships | |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 5.1 General | This clause describes key concepts used by this multi-part deliverable that are then used in the generic architecture in the following clause 6. Clause 5 is structured as follows: • Clause 5.2 introduces the concepts that represent intangible components of the architectures. ETSI ETSI TS 103 286-1 V1.1.1 (2015-05) 9 • ... |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 5.2 Concepts | |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 5.2.1 Content and timed content | A concept repeatedly used above is that of content. Content can refer both to the broadcasts made by an operator, e.g. a television programme transmitted to the audience, as well as extra content that a broadcaster makes available to go with the programme. This extra content may be generic information, such as websites... |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 5.2.2 Timelines | A timeline represents a way of describing the progress of presentation of content or a time position in the content, and therefore it enables synchronizing with content. Typically, content will have many timelines, corresponding to different points in its production and eventual delivery. EXAMPLE: Consider a television... |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 5.2.3 Companion screen application | The companion device is assumed to provide the companion experience via an application that runs on the device. This enhances or extends the content experience delivered by the TV Device. This companion screen application (CSA) can be specific to a given programme or show, or can be more generic covering a channel or s... |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 5.3 Roles | |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 5.3.1 Broadcaster | The role of the broadcaster is that of providing content, i.e. supporting a broadcast service. In this context they may not actually broadcast the content (that may be handled by the role of the delivery service provider), and the content may not be broadcast, e.g. it may be provided as CoD. In the model of the present... |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 5.3.2 Delivery Service Provider | The role of the delivery service provider is that of conveying the content to the consumer, and covers a very wide range such as Television Service Providers, Internet Service Providers and CDN Service Providers. In many cases the broadcaster will also be the delivery service provider but this is not required. However,... |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 5.3.3 Consumer | The final role is that of the consumer who owns the TV Device, as described in clause 5.4.1, that presents the content and owns one or more companion devices such as tablets or smart phones running CSAs that will be part of the enhanced content experience. For convenience, the specifications series is generally written... |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 5.4 Devices | |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 5.4.1 TV Device | The TV Device is either a television or a device such as a set-top box (STB) that is connected to a television. It is also assumed that the TV Device represents a "single output" device, i.e. it presents a single item of content at a time. If a single physical device supports multiple outputs (e.g. a multi-output STB),... |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 5.4.2 Companion Device | The companion device is a generic term for a device owned by the consumer such as (but not limited to) a smart phone or a tablet that is used by the consumer whilst consuming content. The companion device is typically connected to the home network, and thence to the internet. The alternative model where the companion d... |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 5.5 Relationship of concepts, roles and devices | Figure 5.5.1 shows the connections between the concepts, functional roles (and their services) and the devices assumed by this multi-part deliverable, and as described by clauses 5.2 to 5.4. Broadcaster Consumer TV Device Delivery Service Provider Content, Timed Content and related information Companion Device Companio... |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 6 General architecture | |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 6.1 Introduction | The general architectural framework is shown in figure 6.1.1. This illustrates the main components of the architecture and the information flows between them. Each of the parts within this multi-part deliverable works inside this framework. This is done by taking the framework and • tailoring certain components, or • a... |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 6.2 Companion Services | The interactions between the CSA and the TV device allow the CSA access to certain aspects of information carried by the broadcast or CoD service. This information may not provide enough information or content required to build the companion experience. Thus the purpose of the companion services is to provide any addit... |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 6.3 Link Proxy | The link proxy is the architectural component that supports indirect communications between the TV Device and the companion screen applications, assuming that both are connected to the internet. Although the model shows a single link proxy entity, it is likely that any definition will support a more flexible and comple... |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 6.4 Defined Interfaces | Figure 6.4.1 details all the currently defined interfaces within this multi-part deliverable with the abbreviations by which they are known and the typical components they are used between. Also shown in this diagram is the broadcast content or CoD delivered to the TV Device via a broadcast platform or the internet. Wh... |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 7.1 General | |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 7.1.1 Overview | Clause 7 describes the specific interfaces that enable a Companion Screen Application (CSA) to synchronize its presentation of Timed Content with the presentation of Timed Content by a TV Device. These are illustrated in figure 7.1.1.1. Figure 7.1.1.1: Interfaces for Content Identification and Media Synchronization The... |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 7.1.2 Optionality of specification components | A TV Device that is compliant with ETSI TS 103 286-2 [i.2] normally implements at least the CSS-CII interface. A TV Device that enables a CSA to use Timelines to synchronize its presentation with the TV Device provides (via the CSS-CII interface) the location of an endpoint for an implementation of the CSS-TS interface... |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 7.1.3 Recommendations for profiling | To make use of ETSI TS 103 286-2 [i.2] it is recommended that a profile be defined. In any profile it is recommended to define: • the interfaces to be implemented and where the endpoints for the interfaces are located; • the types of Timed Content that the TV Device may present and any Content Identifiers for types of ... |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 7.2 CSS-CII - Content Identification and other Information | The CSS-CII interface exists between the TV Device and the Companion Screen Application. It has the following functions: • Retrieving Content Identifier(s) from the TV Device. • Retrieving information on the status of presentation from the TV Device. • Retrieving the CSS-MRS endpoint name or address from the TV Device.... |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 7.3 CSS-MRS - Material Resolution Service | The CSS-MRS interface exists between the Companion Screen Application and the Material Resolution Service. It has the following functions: • Retrieving Material Information from the Material Resolution Service (MRS). • Providing updates to the Material Information. • Providing correlation timestamps (the mapping betwee... |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 7.4 CSS-WC - Wall Clock | The CSS-WC interface exists between the Wall Clock Server (WC Server) elementary function of the TV Device and the Wall Clock Client (WC Client) elementary function of the Companion Screen Application. It has the following function: • Creating an estimate at the CSA of the Wall Clock at the TV Device. Both the WC Serve... |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 7.5 CSS-TS - Timeline Synchronization | The CSS-TS interface exists between the MSAS elementary function of the TV Device and the SC elementary function of the Companion Screen Application. It has the function of Timeline Synchronization between SC and MSAS, comprising: • the SC function selecting a Timeline that is being signalled in the broadcast; and • th... |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 7.6 CSS-TE - Trigger Event | The CSS-TE interface exists between the TV Device and the Companion Screen application. It has the following function: • Subscription to Trigger Event sources. • Notification of Trigger Events. • Notification of changes to subscriptions (e.g. when a specific event source "disappears"). • Private data. The mechanisms fo... |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 8 Interfaces for Discovery | |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 8.1 General | Clause 8 describes the interface defined in ETSI TS 103 286-3 [i.3] that enable a CSA to find and associate with a TV Device. This interface allows the CSA to establish communications via the discovery of the relevant interface end- points needed by this multi-part deliverable, e.g. the CSS-CII described in clause 7, a... |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 8.2 CSS-DA - Discovery and Association | The CSS-DA interface exists between the TV Device and the Companion Screen Application. It has the following function: • discovery • association methods that avoid the need to re-discover on all communications The CSS-DA interface is defined in ETSI TS 103 286-3 [i.3], and shown in figure 8.2.1. Figure 8.2.1: Interface... |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 9 Interfaces for indirect communication | |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 9.1 General | Although normally the devices in the home will be connected to a common home network allowing them to communicate with each other (and that supports functionality such as the ability to send multicast messages that reach all clients on the network), this need not always be the case. For instance a companion device may ... |
ffaeed3a9fdadba6b30dbdd6a9ecbd02 | 103 286-1 | 9.2 CSS-LP - Link Proxy | The CSS-LP interface exists between the TV Device and CSA, via an internet based proxy service, and serves to provide a means of supporting all other TV Device and CSA communications when direct communications are not possible (e.g. where the two parties do not possess a direct communication path). It is expected that ... |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 1 Scope | The present document defines the delivery of TV content via HTTP adaptive streaming building on the MPEG DASH specification [1]. In order to improve interoperability, additional constraints and requirements are defined and a selection of the video and audio codecs from the DVB toolbox are referenced that are technicall... |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 2 References | |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 3 Definition of terms, symbols and abbreviations | |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 3.1 Terms | For the purposes of the present document, the following terms apply: access unit: unit of a media stream with an assigned Media Presentation time accessibility: degree to which a media content or certain media content components are available to as many people as possible adaptation set: set of interchangeable encoded ... |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 3.2 Symbols | Void. |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply. 4CC Four Character Code AAC Advanced Audio Coding AAC-LC Advanced Audio Coding - Low Complexity ABNF Augmented Backus-Naur Form AC-3 Dolby AC-3 audio coding system NOTE: According to ETSI TS 102 366 [10]. AC-4 Dolby AC-4 audio coding system NO... |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 4.1 DVB Profile of MPEG-DASH | The DVB Profile of MPEG-DASH, known as an "interoperability point" by MPEG, is based on the merging of the ISO/IEC 23009-1 [1], ISO Base media file format live profile and ISO Base media file format On Demand profile. In addition it includes "xlink" but only in combination with the actuate property set to "onLoad". The... |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 4.2 Media Presentation Description Constraints | |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 4.2.1 General | The MPD shall conform to the constraints in clause 4.2 in addition to the rules for the MPD as defined in ISO/IEC 23009-1 [1], clause 7.3. ETSI ETSI TS 103 285 V1.3.1 (2020-02) 18 NOTE: MPDs, or their constituent parts, which do not conform to the constraints in clause 4.2 may be ignored by the client. MPDs shall not c... |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 4.2.2 Constraints on Period elements (common Period constraints) | • The Subset element may be ignored. • The Period.SegmentList element shall not be present. • If a Period element contains multiple Adaptation Sets with @contentType="video" then at least one Adaptation Set shall contain a Role element with @schemeIdUri="urn:mpeg:dash:role:2011" and @value="main". • Remote elements wit... |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 4.2.3 Constraints on Period elements conforming to Live profile | • AdaptationSet elements that do not conform to clause 4.2.4 may be ignored. |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 4.2.4 Constraints on AdaptationSet elements (for Live Periods) | • The @group attribute may be ignored. • Adaptation Sets which contain BaseURL elements with Absolute BaseURLs may be ignored. • Any AdaptationSet with a ContentComponent element may be ignored. NOTE 1: This is so that Adaptation Sets with multiplexed media streams may be ignored. • AdaptationSet element can be ignored... |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 4.2.5 Constraints on Representation elements (for Live Periods) | • Representations with a value of the @mimeType attribute starting with a string other than "xxx/mp4" where xxx is one of "video", "audio", "application" or "text" may be ignored. Additional profile or codec specific parameters may be added to the end of the value of the @mimeType attribute. • Representations not infer... |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 4.2.6 Constraints on Period elements conforming to On Demand profile | • The Period.SegmentTemplate element shall not be present. • AdaptationSet elements that do not conform to clause 4.2.7 may be ignored. |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 4.2.7 Constraints on AdaptationSet element (On Demand) | • The @group attribute may be ignored. • Any AdaptationSet with a ContentComponent element may be ignored. NOTE 1: This is so that Adaptation Sets with multiplexed media streams may be ignored. • AdaptationSet element can be ignored unless for each Representation within this Adaptation Set Representation.BaseURL is pre... |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 4.2.8 Constraints on Representation element (On Demand) | • Representations with a value of the @mimeType attribute starting with a string other than "xxx/mp4" where xxx is one of "video", "audio", "application" or "text" may be ignored. Additional profile or codec specific parameters may be added to the end of the value of the @mimeType attribute. • Representations not infer... |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 4.2.9 Constraints for low latency content | • Low latency content using chunked segments (see clause11.18.1) that are available to players before they are complete is signalled using the SegmentTemplate@availabilityTimeOffset attribute in combination with the SegmentTemplate@availabilityTimeComplete attribute set to "false". NOTE: The similarly named BaseURL@ava... |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 4.3 Segment Format Constraints | For Representations and Segments referred to by the Representations in the profile-specific MPD for this profile, the following constraints shall be met: • For Periods conforming to clause 4.2.3 or 4.2.6: - Representations and segments shall comply with the formats defined in ISO/IEC 23009-1 [1], clause 7.3. - In Media... |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 4.4 Presence of Attributes and Elements | Elements and attributes are expected to be present for certain Adaptation Sets and Representations to enable suitable initial selection and switching. Specifically the following applies: • For any Adaptation Sets with @contentType="video" the following attributes should be present: - @maxWidth (or @width if all Represe... |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 4.5 Dimension Constraints | It is mandatory that: • The MPD size before and after xlink resolution shall not exceed 256 Kbytes. • The MPD has a maximum of 64 periods before and after xlink resolution. • The MPD has a maximum of 16 adaptation sets per period. • The MPD has a maximum of 16 representations per adaptation set. • Segment duration shal... |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 4.6 Server Requirements | Servers shall support HTTP 1.1 as defined in IETF RFC 7230 [17] and the use of Cookies as specified in IETF RFC 6265 [18]. 4.7 Availability Time Synchronization between Player and Server |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 4.7.1 Background | MPEG DASH includes provision for MPDs and segments that appear and disappear over time. In order to properly access these, DASH servers and Players should synchronize their clocks to a globally accurate time standard. Specifically Segment Availability Times are expected to be accurately announced in the MPD and the Pla... |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 4.7.2 Service Provider Requirements | If the MPD is dynamic or if the MPD@availabilityStartTime is present then the service provider shall provide an MPD as follows: • The MPD should contain at least one UTCTiming element (as defined in ISO/IEC 23009-1 [1]) with the @schemeIdURI attribute set to one of the following: - urn:mpeg:dash:utc:ntp:2014 - urn:mpeg... |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 4.7.3 Player Requirements | If the MPD is dynamic or if the MPD@availabilityStartTime is present, then the Player does the following: • If the MPD does not contain any UTCTiming elements (as defined in ISO/IEC 23009-1 [1]), the Player should acquire an accurate wall-clock time from its system. The anticipated inaccuracy of the timing source shoul... |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 5 DASH Specific Aspects for Video | |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 5.1 DASH Specific Aspects for H.264/AVC Video | |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 5.1.1 Profiles Supported | Video encoded with H.264/AVC shall comply with the limitations set out in ETSI TS 101 154 [3], clause L.3.2. DVB-DASH MPDs that include video encoded with AVC shall include content compatible with the avc_hd_50_level40 or avc_hd_60_level40 player conformance points from ETSI TS 101 154 [3] unless targeting devices that... |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 5.1.2 H.264/AVC Specifics | The encapsulation of H.264/AVC video data is based on the ISO BMFF as defined in ISO/IEC 14496-15 [4]. Segments shall start with SAP types 1 or 2 as described in ISO/IEC 14496-12 [6]. Players which support H.264 shall support both sample entries using 'avc1' and 'avc3' (both storage for SPS/PPS within the initializatio... |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 5.1.3 Signalling of the Codec Profile | For representations in the scope of DVB-DASH 2014 profile, the video codec profile, level and constraints should be signalled within the MPD using the @codecs attribute. For representations in the scope of the DVB-DASH 2017 profile, these shall be signalled. If present, the value of the @codecs attribute shall be set i... |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 5.1.4 Signalling within the AVCSampleEntry in an initialization segment | The AVCSampleEntry contained within the initialization segment of an H.264/AVC track contains a number of values indicating information about the encoded video. These values shall always be set such that the encoded video in all Representations using this initialization segment does not exceed the size, profile, level ... |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 5.2 DASH Specific Aspects for HEVC Video | |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 5.2.1 HEVC Specifics | The encapsulation of HEVC video data in ISO BMFF is defined in ISO/IEC 14496-15 [4]. Players which support HEVC shall support both sample entries using 'hvc1' and 'hev1' (both storage for VPS/SPS/PPS within the initialization segment or inband within the media segment). Segments shall start with SAP types 1 or 2 as des... |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 5.2.2 Signalling of the Codec Profile | For representations in the scope of the DVB-DASH 2014 profile, the video codec profile, level and constraints should be signalled within the MPD using the @codecs attribute. For representations in the scope of the DVB-DASH 2017 profile, these shall be signalled. If present, the value of the @codecs attribute shall be s... |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 5.2.3 Profiles Supported | Video encoded with HEVC shall comply with the limitations set out in ETSI TS 101 154 [3], clause L.3.3 DVB-DASH MPDs that include video encoded with HEVC shall include content compatible with at least one of the HEVC player conformance points from ETSI TS 101 154 [3] unless targeting devices that are known to support o... |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 5.2.4 Location of SEI messages | ISO/IEC 14496-15 [4] clauses 8.3.2 and 4.3.2 allow for SEI messages in general to be contained in parameter set arrays or in media samples. Where it is necessary to include SEI messages in a Representation to give information which alters or supplements that specified in VPS, SPS or PPS (for example updates to transfer... |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 5.2.5 Colour format and transfer characteristics signalling | Information on colour primaries, matrix coefficients and transfer characteristics may be signalled using EssentialProperty or SupplementalProperty descriptors applied to an AdaptationSet as defined in this clause. Table 3 lists the @schemeIdUri attribute values defined for this signalling, and the associated semantics ... |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 5.2.6 High Dynamic Range using HLG10 | The bitstream format for HLG10 shall be as defined in clause L.3.3 of ETSI TS 101 154 [3], particularly clause L.3.3.6. Clause 5.2.4 contains guidance on the location of certain types of SEI message. The alternative_transfer_characteristics SEI message shall be located in accordance with that guidance. Except where a D... |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 5.2.7 High Dynamic Range using PQ10 | The bitstream format for PQ10 shall be as defined in clause L.3.3 of ETSI TS 101 154 [3], particularly clauses L.3.3.6 and L.3.3.10. Use of PQ10 within an AdaptationSet shall be signalled as follows: • MPD and AdaptationSet profile signalling in accordance with clause 4.1 indicating urn:dvb:dash:profile:dvb- dash:2017 ... |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 5.2.8 Temporal Layers | |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 5.2.8.1 Introduction | 5.2. |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 8.1 Introduction | HEVC coding has a concept of temporal layers (also called sub layers) which allow the encoding of video such that a lower frame rate and a higher frame rate can be encoded together, allowing the player to decode either the temporal layer in the encoded bitstream carrying just the lower frame rate or the entire encoded ... |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 5.2.8.2 Signalling of Temporal Layers | Where HEVC video has been encoded using temporal layers, every Representation shall include a SupplementalProperty Descriptor indicating the HighestTid (Highest Temporal ID) present in the Representation, either by explicit signalling on the Representation or inheritance from the containing Adaptation Set. DVB DASH def... |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 5.2.8.3 Temporal Layers Carried in a Single Representation | Representations may contain NAL units from more than one temporal layer. In this case the Highest Temporal ID signalled shall be that of the highest temporal layer in the Representation, and the @frameRate attribute of the Representation element (or inherited from the Adaptation Set) shall refer to the highest temporal... |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 5.2.8.4 Temporal Layers Carried in Separate Representations | The present document does not support Temporal layers carried in separate representations. |
4b4fc3ef15bd130cba301739db0df1c6 | 103 285 | 6 DASH Specific Aspects for Audio |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.