hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.7.1.2 HTML5 media element | An HTML5 media element that is passed to the initMediaSynchroniser() or addMediaObject() methods shall have the readyState property set to HAVE_CURRENT_DATA, HAVE_FUTURE_DATA or HAVE_ENOUGH_DATA. The media element shall be playing or paused. The controller property of the media element shall be null or undefined. Passi... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.7.1.3 A/V Control object | An A/V Control object that is passed to the initMediaSynchroniser() or addMediaObject() methods shall be in the connecting, buffering, paused or playing states. Passing an A/V Control object in any other state to these methods shall result in an error being dispatched with error number 9 or 16. NOTE: In the single deco... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.7.2 Tolerance | The synchronization tolerance defines the maximum time by which the presentation of two media streams can be out of sync but still considered synchronized. While a video and a corresponding audio stream usually require tight synchronization, an application may choose to loosen this requirement for certain combinations ... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.7.3 Timeline availability | If at any time the timeline selected by the application for that media stream is determined to be unavailable while the terminal is attempting to synchronize the presentation of a media stream, then: • If the stream is the master media (it was passed to the MediaSynchroniser via the initMediaSynchroniser() method) then... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.7.4 Minimum synchronization accuracy | The minimum accuracy for multi-stream and inter-device synchronization for a given terminal is the largest of: • 10 ms (being the duration of 1/2 a frame of video at 50 fps); • the duration of 1/2 tick of any timeline selected (during the corresponding initMediaSynchroniser() or addMediaObject() method call) by the Hbb... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.8 Reliability and resilience | Terminals shall operate reliably in response to rapid user interaction. Specifically, the terminal shall remain fully functional in the following circumstances. Fully functional in this case means at least that the appropriate application at the end of each sequence starts successfully, that it functions as designed an... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 10 Capabilities | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 10.1 Display model | This clause is replaced by annex H, "Display Model" of the OIPF DAE specification [1]. |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 10.2 Terminal capabilities and functions | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 10.2.1 Minimum terminal capabilities | Minimum terminal capabilities which shall be available to applications are listed in Table 11 for general capabilities. Additional capabilities shall be signalled as defined in clause 10.2.4. Table 11: Minimum terminal capabilities Value Additional information HbbTV® application graphic plane resolution 1 280 pixels ho... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 10.2.2 User input | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 10.2.2.1 Key events | Implementations shall provide a mechanism for the end user to generate key events as defined in Table 12. Table 12: Key events and their status Button (for conventional remote controls) DOM-2 Key event Status Availability 4 colour buttons (red, green, yellow, blue) VK_RED, VK_GREEN, VK_YELLOW, VK_BLUE Mandatory Always ... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 10.2.2.2 Mouse and wheel events | If a terminal indicates that it has pointer support in the capability profile as defined in clause 9 of the OIPF DAE specification [1], implementations shall provide a mechanism for the end user to generate mouse events and may provide a mechanism for the end user to generate wheel events as defined in clause 9.3.24 of... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 10.2.3 Terminal functions | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 10.2.3.1 Favourites and bookmarks | The terminal should provide a feature to organize frequently used broadcast-independent interactive applications as bookmarks or favourites. For the presentation of applications on manufacturer portals or in favourite lists the terminal may use a title and an icon specified in the HTML head section and the URL of the i... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 10.2.3.2 Streaming and Download | Terminals shall not permit persistent storage of broadband delivered content whose delivery was initiated using the streaming APIs (the A/V Control object or an HTML5 media element) whether streamed adaptively using MPEG DASH as defined in annex E or non-adaptively. Service providers who want to offer content for persi... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 10.2.3.3 PVR | It is up to the terminal to decide whether PVR feature related calls are executed directly or if additional means to determine whether to allow the call for the application are employed, such as opening a dialog to query the user. |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 10.2.3.4 Download via broadcast using FDP | When the resources of the terminal (e.g. tuners) are concurrently required for performing a download via FDP and for TV viewing, priority shall always be granted to TV Viewing. However, the present document is intentionally silent about priorities between download via FDP and PVR recording. The terminal shall be able t... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 10.2.4 HbbTV® reported capabilities and option strings | The xmlCapabilities property of the application/oipfCapabilities embedded object shall describe an XML document that conforms to the schema defined in clause A.2.15. Some of the capabilities reported are dynamic for some classes of terminal. For example, a drm element needs to be included to describe the CA capabilitie... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 10.2.5 Void | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 10.2.6 Parental access control | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 10.2.6.1 Broadcast channel | Terminals shall support parental access control for the broadcast TV content and application as required for the markets in which the products are to be sold or deployed. The details of this are outside the scope of the present document. Typically the end user may have to enter the appropriate PIN in order to obtain ac... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 10.2.6.2 Broadband delivered content | Applications offering access to streaming on-demand content shall obtain the parental rating system threshold set on the terminal and only stream appropriate content to the terminal. In spite of the above, the present document requires the terminal to react to signalled parental rating information in some circumstances... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 10.2.6.3 Downloaded content | Broadcasters and service providers offering content for download shall populate the otherwise optional <parentalRating> element in the content access descriptor with the correct value for each content item downloaded. When playing back a downloaded content item, terminals shall compare the value in the <parentalRating>... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 10.2.6.4 PVR | Broadcasters and service providers whose applications create Programme objects and pass them to the record(Programme programme) method of the application/oipfRecordingScheduler object shall populate the parentalRating property of the Programme object. Terminals shall obtain the parental rating information from DVB-SI (... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 10.2.6.5 Synchronization and parental access control | If access to media content presented by a video/broadcast object, an HTML5 media element or an A/V Control object is blocked by the terminal due to parental access control then: • If it represents master media (it was passed to a MediaSynchroniser via the initMediaSynchroniser() method) then this shall result in a perm... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 10.2.7 Component selection | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 10.2.7.1 General | Where more than one component of a media type (i.e. video, audio, subtitles) is available, selection of which one or ones should be presented may be done either by the HbbTV® terminal or by the HbbTV® application or by both. The terminal shall always perform a default selection of components to present from all of the ... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 10.2.7.2 Component selection by the terminal | It is the responsibility of the terminal to choose for presentation to the user the most appropriate default components from those available in the media object(s), based on the user's preferences (e.g. audio language). The terminal shall present to the user the default components of those component types which are sel... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 10.2.7.3 Component selection by the application | Terminals shall allow applications to change the terminal-derived component selection and discover the presentation status using the methods defined in clause 7.16.5 of OIPF DAE [1] and in clauses 4.7.10.10.1 and 4.7.10.12.5 of HTML5 [54]. If selection of one or more media type has been done by the application on a med... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 10.2.7.4 Single decoder model | The rules defined in clauses 10.2.7.2 and 10.2.7.3 shall apply when the terminal has sufficient decoder resources to be able to independently present only one media object, where that media object could be an HTML5 media element, an A/V Control object, a video/broadcast object or a MediaSynchroniser object. EXAMPLE: If... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 10.2.7.5 Multi-decoder model | When the terminal has sufficient decoder resources to be able to independently present more than one media object (where that media object could be an HTML5 media element, an A/V Control object or a video/broadcast object), the rules defined in clauses 10.2.7.2 and 10.2.7.3 shall apply to each media object separately. ... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 10.2.8 Multi-stream media synchronization | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 10.2.8.1 General | The HbbTV® terminal shall support decoding and rendering of A/V content delivered as multiple streams over broadband and broadcast networks as defined in this clause. This capability is known as multi-stream synchronization and clause 13.2 describes an architecture for it. The HbbTV® terminal shall support the combinat... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 10.2.8.2 Synchronization using gen-locked STC | This clause applies to the synchronization of one broadcast service with at least one broadband stream, where the broadband streams are MPEG transport stream based and share the STC with the broadcast service. NOTE: Two streams sharing the same STC means that the encoder clocks of both are gen-locked and that the PTS o... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 10.2.8.3 Other synchronization cases | This clause applies to the synchronization of one broadcast service with one or more broadband streams where the streams may have different system formats or different types of timelines. In case the broadband stream is MPEG transport stream based, its STC can be independent from the STC of the broadcast service. Termi... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 10.2.8.4 Supported combinations | HbbTV® terminals shall support the presentation of at least the combinations of media type, systems layer, timeline and delivery protocol for multi-stream synchronization, as shown in Table 14. NOTE 1: Table 14 does not apply when inter-device synchronization is being performed without multi-stream synchronization. All... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 10.2.9 Inter-device media synchronization | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 10.2.9.1 General | The HbbTV® terminal shall support decoding and rendering of A/V content delivered by broadcast or broadband networks in a manner where presentation is time synchronized with another HbbTV® terminal or a Companion Screen application. This feature is known as inter-device synchronization. Clause 13.2 describes an archite... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 10.2.9.2 Master terminal | An HbbTV® terminal shall be able to act in the role of a master terminal. To implement this: • The terminal shall implement the MediaSynchroniser API defined in clause 8.2.3. • The terminal shall support generation of timestamps as defined in clause 13.4.1 and should support interpretation of timestamps as defined in c... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 10.2.9.3 Slave terminal | An HbbTV® terminal may have the capability to act as a slave terminal, and this shall be signalled by the inclusion of the appropriate option string defined in Table 13 in clause 10.2.4. For a terminal with the capability to act as a slave terminal: • The terminal shall implement the functionality and interfaces for a ... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 11 Security | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 11.1 Application and service security | The present document defines two levels of trust for applications - trusted and not trusted. The features only available to trusted applications are listed in Table A.1. By default, broadcast related applications shall be trusted and broadcast-independent applications shall not be trusted. This may be modified as follo... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 11.2 TLS and Root Certificates | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 11.2.1 TLS support | HTTP over TLS as defined in IETF RFC 2818 [7] shall be supported for transporting application files over broadband. TLS version 1.2 as defined in IETF RFC 5246 [8] shall be supported. Terminals shall not set the client_version field of the ClientHello message to less than { 3, 3 } (TLS 1.2). ETSI ETSI TS 102 796 V1.5.1... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 11.2.2 Cipher suites | The cipher suite requirements are specified in Table 15a. The cipher suites are defined in IETF RFC 5246 [8] and IETF RFC 5289 [57]. Terminals should prioritize these cipher suites in the order shown. Terminals shall implement all cipher suites marked mandatory and shall not implement any cipher suites marked forbidden... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 11.2.3 Root certificates | A list of root certificates is maintained at http://www.hbbtv.org/spec/certificates.html. The policy by which this list has been derived is outlined in annex D. Terminals shall trust all root certificates identified as mandatory and may support those certificates identified as optional on that list, subject to the cond... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 11.2.4 Signature algorithms | The algorithm requirements for signature verification are specified in Table 15b. Terminals shall not trust any signature that uses an algorithm designated as forbidden. Table 15b: Signature algorithms and their status Algorithm name TLS 1.2 identifier Status md5WithRSAEncryption 0x0101 Forbidden sha1WithRSAEncryption ... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 11.2.5 Key sizes and elliptic curves | Terminals shall support RSA keys with modulus size between 2 048 and 4 096 bits. Terminals shall not trust RSA signatures that are less than 2 048 bits in size. The requirements for elliptic curves are specified in Table 15c. The curves are defined in IETF RFC 4492 [55]. Curves marked mandatory shall be supported for s... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 11.2.6 Backward compatibility | Service providers should be aware that earlier versions of the present document contained different mandatory TLS versions, extensions and cipher suites. Where TLS servers need to retain support for terminals conforming to earlier versions, they should: • be able to negotiate a TLS session using TLS 1.0, 1.1 or 1.2; • ... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 11.3 TLS client certificates | In HTTP over TLS, the use of a client certificate authenticates the client to a service provider. Some business models require that an HbbTV® application is delivered exclusively to trusted HbbTV® terminal implementations. To support these, terminals may support use of client certificates. Negotiation and delivery of c... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 11.4 CI Plus | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 11.4.1 CI Plus communication | Terminals supporting CI Plus for protected content via broadcast shall support the following mapping from the application/oipfDrmAgent embedded object to the CI Plus protocol as defined by clause 4.2.3 "CI+ based Gateway" of the OIPF CSP specification [5]: • 4.2.3.1 Mandatory. • 4.2.3.2 Mandatory. • 4.2.3.3 Mandatory. ... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 11.4.2 IP delivery Host player mode | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 11.4.2.1 Error handling in "IP delivery Host player mode" | Terminals supporting the "IP delivery Host player mode" as defined in the DVB Extensions to CI Plus ETSI TS 103 205 [37] shall map the following values of drm_status in the sd_start_reply APDU to the errorState argument of onDRMRightsError. Table 16: onDRMRightsError errorState values drm_status errorState Decryption p... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 11.4.2.2 DRM metadata source | Table 34 in clause 7.4.4 of the DVB Extensions to CI Plus ETSI TS 103 205 [37] identifies 7 sources for DRM metadata. Of those 7 sources, the present document requires support for 0x03 "Common Encryption (CENC)" and 0x04 "Media Presentation Description (MPD)". The present document is intentionally silent about support ... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 11.4.3 Auxiliary file system | When the CICAM Auxiliary File System is implemented as specified in the DVB Extensions to CI Plus ETSI TS 103 205 [37], the Terminal shall declare the Auxiliary File System resource identifier in the list of the resources that it provides. The HbbTV® Application Domain is defined as: "HbbTVEngineProfile1", i.e. the val... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 11.4.4 Virtual channel | When the terminal supports the CICAM Virtual Channel as specified in clauses 14 and 15.3 of the DVB Extensions to CI Plus ETSI TS 103 205 [37], the Terminal shall support launching an HbbTV application when the virtual channel is selected. The details of how the HbbTV application is launched shall be as defined in clau... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 11.4.5 IP Delivery CICAM player mode | Terminals supporting the "IP delivery CICAM player mode" as defined in the DVB Extensions to CI Plus ETSI TS 103 205 [37] shall support the use of "Host-initiated playback" (as defined in clause 8.3.2 of [37]) in combination with the HTML5 video element as defined in annex K of the present document. |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 11.5 Protected content via broadband | Terminals that support the "IP delivery Host player mode" as defined in the DVB Extensions to CI Plus ETSI TS 103 205 [37] shall support the decryption of protected content delivered via the broadband channel as defined in clause 7 of the DVB Extensions to CI Plus ETSI TS 103 205 [37] where that content is provided in ... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 11.6 Protected content via download | Terminals that support the "IP delivery Host player mode" as defined in the DVB Extensions to CI Plus ETSI TS 103 205 [37] and also the download optional feature shall support the decryption of protected content as defined in clause 7 of the DVB Extensions to CI Plus ETSI TS 103 205 [37] where that content is provided ... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 11.7 Terminal WebSocket service endpoints | All WebSockets endpoint URLs for application to application communication and inter-device synchronization shall include a randomly-generated part. The URLs shall be static for at least the lifetime of an HbbTV® application and shall be regenerated every time the terminal starts. The URLs should have at least 128 bits ... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 11.8 Cookie storage | Content providers may use cookies as part of a content protection solution and may include tokens that they do not want to be user-accessible or transferrable between devices. The following requirements apply to HTTP cookies that have the Secure attribute set as defined in IETF RFC 6265 [24] and are stored by the brows... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 12 Privacy | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 12.0 Overview | This clause addresses privacy related terminal functions as well as privacy related measures on the application level. |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 12.1 Terminal privacy features | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 12.1.1 Tracking preference expression (DNT) | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 12.1.1.0 Background | The tracking preference expression mechanism defined in the present clause is a compatible subset of the W3C Working Draft for Tracking Preference Expression (DNT) [i.9]. It is intended that the present clause will be updated to reference that W3C specification, once it has been published as a W3C Technical Recommendat... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 12.1.1.1 Principles | Clause 12.1.1.2 defines the DNT (do not track) header field for HTTP requests as a mechanism for expressing the user's preference regarding their behaviour being tracked (or not). The goal of this protocol is to allow HbbTV® terminals to express the user's personal preference regarding tracking to each server and web a... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 12.1.1.2 Expressing a tracking preference | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 12.1.1.2.1 Expression format | When a user has enabled a tracking preference, that preference needs to be expressed to all mechanisms that might perform or initiate tracking directly or by third parties, including sites that the HbbTV® terminal communicates with via HTTP. When enabled, a tracking preference shall be expressed according to Table 17. ... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 12.1.1.2.2 DNT header field for HTTP requests | HbbTV® terminals shall insert the DNT field into all outgoing HTTP requests made on behalf of an HbbTV® application as the means for expressing a user's tracking preference via HTTP. NOTE 1: This does not apply to HTTP requests made by the media player or the DRM agent. It shall be encoded as follows: DNT-field-name = ... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 12.1.2 Third party cookies | Third party cookies are generally considered problematic in a privacy context. According to clause 7.1 of IETF RFC 6265 [24] the implementation of third party cookies is optional. Manufacturers of HbbTV® terminals may block all third party cookies. If they do not, then they shall provide the user the option of doing so... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 12.1.3 Blocking tracking websites | Tracking scripts can be problematic in a privacy context, especially when used in autostart applications. To provide additional protection to users, terminals may offer the possibility of blocking requests to tracking websites. Manufacturers of HbbTV® terminals should consider providing the option of disallowing reques... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 12.1.4 Persistent storage | Terminals may offer the user the option to disable persistent storage (cookies, Web Storage) on a per-application or per-site basis. While this may improve user privacy, it will likely result in a worse user-experience, for example loss of personalization and inability to remember a user's agreement to a site's terms a... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 12.1.5 Distinctive identifiers | Terminals shall implement the extensions to the Configuration class for distinctive identifiers as defined in clause A.2.20.5 and as required in this clause. These extensions support a per-origin, non-associable, user-clearable identifier (these terms are used in W3C EME [66]). ETSI ETSI TS 102 796 V1.5.1 (2018-09) 147... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 12.2 Respecting privacy in applications | Application developers are responsible to comply with all applicable legislation and regulation, particularly concerning user privacy. Actions taken by broadcast-related autostart applications before the user has pressed the red button (or equivalent) are particularly sensitive since they occur unnoticed by the user, a... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13 Media synchronization | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.1 General (informative) | Clause 13 describes and defines how a terminal supports multi-stream and inter-device synchronization features and also the application to media synchronization feature. Clauses 10.2.8, 10.2.9 and 10.2.10 define the terminal requirements to implement these features. Clause 13.2 describes a unified architectural model f... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.2 Architecture (informative) | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.2.1 General | The terminal performs multi-stream and/or inter-device synchronization functionality on behalf of the HbbTV® application. Both multi-stream and inter-device synchronization functionality are controlled by the HbbTV® application through the MediaSynchroniser object defined in clause 8.2.3. The HbbTV® application directs... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.2.2 Multi-stream synchronization | Figure 17 illustrates the relationship between HbbTV® application and MediaSynchroniser object for multi-stream synchronization. ETSI ETSI TS 102 796 V1.5.1 (2018-09) 149 Figure 17: Relationship between MediaSynchroniser object and HbbTV® application for multi-stream synchronization A terminal is deemed to be performin... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.2.3 Inter-device synchronization | Figure 19 and Figure 20 illustrate the relationship between MediaSynchroniser object and HbbTV® application for inter-device synchronization. A terminal is acting in the role of a master that dictates the timing of the presentation for all media streams. In Figure 19 a Companion Screen application is a slave whose timi... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.2.4 Master media and other media | The media object passed as an argument to the initMediaSynchroniser() method is the master media being presented by the HbbTV® terminal. Media objects passed as arguments to the addMediaObject() method are other media. From the perspective of a slave terminal, the master terminal is presenting the master media and medi... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.3 Media synchronization states and transitions | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.3.1 States overview (informative) | Multi-stream and inter-device synchronization functionality is controlled via the MediaSynchroniser object. Figure 23 shows the states of the terminal and MediaSynchroniser object: Figure 23: Media Synchronization states When a MediaSynchroniser object is created, it is not yet initialized. Once a method call to initia... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.3.2 Multi-stream synchronization | While the MediaSynchroniser object is initialized, a terminal shall attempt to perform multi-stream synchronization while: • if the MediaSynchroniser was initialized using initMediaSynchroniser() method, at least one media object has been added using the addMediaObject() method; • or if the MediaSynchroniser was initia... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.3.3 Becoming a master terminal | If inter-device synchronization is enabled for a MediaSynchroniser object that was initialized using the initMediaSynchroniser() method then the terminal shall ensure that the following protocol endpoints are active: • a DVB CSS-CII protocol endpoint as described in clause 13.6.2; • a DVB CSS-WC protocol endpoint as de... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.3.4 Ceasing to be a master terminal | A terminal shall cease to be a master terminal if: • the disableInterDeviceSync() method is called on the MediaSynchroniser object (see clause 8.2.3.2.2); or • there is a permanent error of the MediaSynchroniser object (see clause 13.3.8); or • the MediaSynchroniser object is destroyed; or • another MediaSynchroniser o... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.3.5 Becoming a slave terminal | If inter-device synchronization is enabled for a MediaSynchroniser object that was initialized using the initSlaveMediaSynchroniser() method then the terminal shall: • connect to the master terminal CSS-CII protocol endpoint as described in clause 13.6.3 (if it has not already done so); then • communicate with the mast... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.3.6 Ceasing to be a slave terminal | A terminal shall cease to be a slave terminal if: • the disableInterDeviceSync() method is called on the MediaSynchroniser object (see clause 8.2.3.2.2); or • there is a permanent error of the MediaSynchroniser object (e.g. because the master terminal ceases to be a master terminal, or the timeline is no longer availab... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.3.7 Transient errors | When a transient error of the MediaSynchroniser occurs the MediaSynchroniser shall continue to attempt to perform multi-stream and/or inter-device synchronization if it is already doing so. The following situations shall cause a transient error of the MediaSynchroniser: • the combination of media streams being requeste... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.3.8 Permanent errors | When a permanent error of the MediaSynchroniser occurs, the MediaSynchroniser shall enter the permanent error state. As specified in clauses 13.3.2, 13.3.4, and 13.3.6, this shall cause the terminal to cease to perform multi-stream synchronization if it is currently performing it. If the terminal is a master terminal o... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.4 Timelines and timestamping | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.4.1 Reference point for timestamping | The reference point for generation and interpretation of Timestamps by the HbbTV® terminal and Companion Screen application used in inter-device synchronization is as defined in clause 5.7.2 of ETSI TS 103 286-2 [47]. ETSI ETSI TS 102 796 V1.5.1 (2018-09) 159 The terminal is responsible for compensating for any extra t... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.4.2 Supported timelines and their selection | A Timeline is the reference frame for measuring the progress of time for a given media stream. How a timeline is to be derived for a given media stream is described by a Timeline Selector as defined in clause 5.3 of ETSI TS 103 286-2 [47]. For multi-stream and inter-device synchronization, the terminal shall support th... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.4.3 Synchronization timeline | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.4.3.1 Timelines for the MediaSynchroniser API | The Timeline to be used by the MediaSynchroniser API within a master terminal is the timeline selected for the master media in the call to the initMediaSynchroniser() method of the MediaSynchroniser object. For a slave terminal, the Timeline to be used by the MediaSynchroniser API is the same Timeline that is used by t... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.4.3.2 Synchronization timeline for Inter-device synchronization | For inter-device synchronization, the Synchronization Timeline is the reference frame for contentTime values in timestamp messages exchanged between a master terminal and a slave terminal (or CSA) via the CSS-TS protocol (as described in clauses 5.7 and 9 of ETSI TS 103 286-2 [47]). Where timestamps are being exchanged... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.5 Buffer for media synchronization |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.