hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.3.3.3 Background state | The terminal shall move the operator application to this state when any of the following are true: • The operator application is in any other state and it makes a successful call to the opAppRequestBackground method. • The operator application is in the transient or overlaid transient state and the countdown timer set ... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.3.3.4 Transient state | The terminal shall move the operator application to this state when any of the following are true: • The operator application is in the foreground or background state and it makes a successful call to the opAppRequestTransient method: - The call shall be successful if it was made within a handler for ChannelChangeSucce... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.3.3.5 Overlaid foreground state | The terminal shall move the operator application to this state when any of the following are true: • The terminal is displaying some UI and the operator application is in the background or overlaid transient state and it makes a successful call to the opAppRequestForeground method: - The call shall be successful if and... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.3.3.6 Overlaid transient state | The terminal shall move the operator application to this state when any of the following are true: • The terminal is displaying some UI and the operator application is in the overlaid foreground or background state and it makes a successful call to the opAppRequestTransient method: - The call shall be successful if and... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.3.4 Standby states | Privileged and operator-specific applications shall not run when the terminal is entering in PASSIVE_STANDBY as defined in clause 7.3.3.1 of [15] or PASSIVE_STANDBY_HIBERNATE as defined in clause 7.3.3.1 of [15] states. When entering the passive states, the terminal shall stop executing any running operator application... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.4 UI elements provided by an operator application | Table A.2 identifies some groups of UI elements that may be suppressed by the terminal in order to be replaced by an operator application. Terminals shall support suppression of those groups of UI elements marked as "M" in that table. Subject to the bilateral agreement, terminals may support suppression of other groups... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.5 Regular HbbTV® application signalling and lifecycle | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.5.1 Application signalling | Terminals shall monitor and act on the HbbTV® application signalling, as defined in clause 7.2.3.1 of ETSI TS 102 796 [1], depending on the state of the operator application as follows: • Foreground state and overlaid foreground state: terminals shall detect the presence of an application overlay descriptor (see clause... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.5.2 Starting and stopping regular HbbTV® applications | The following requirements are in addition to those defined in clause 6.2 of ETSI TS 102 796 [1]: • Operator applications shall be able to launch regular HbbTV® broadcast-independent applications as defined in clause A.2.2.2 of the present document. As defined in clause 6.2.2.6.1 of ETSI TS 102 796 [1], any current bro... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.5.4 Application signalling for operator application created channels | When an operator application created channel is selected, terminals shall act upon any application signalling that was included in the metadata for that channel when the Channel object was created. Such signalling shall be processed as specified for a DVB-I service instance delivered by MPEG DASH in ETSI TS 102 796 [1]... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.6 Multiple operator applications | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.6.1 Supported operators | Terminals shall include a list of those operators where a bilateral agreement is in place (see annex D). This list shall be populated with at least the following information necessary for the installation of operator applications: • Which of the discovery methods in clause 6.1.2 are applicable to the operator including... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.6.2 Adding operators and operator applications to terminals | In order to enable adding operators and operator applications to terminals that are already in the market, the following are recommended: • That terminals support all applicable discovery methods defined in clause 6.1. NOTE: Discovery based on DVB-SI NIT/BAT would not be applicable to a pure IPTV set-top box. Discovery... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.6.3 Installed operator applications | A terminal may have multiple installed operator applications. The user will typically be able to switch between them using the source selection menu (see clause 5.2.1) including starting them if they are not running. NOTE 1: The present document does not require terminals to be able to have multiple operator applicatio... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.7 Removal of operator applications | Once installed, operator applications may be removed by two mechanisms as follows: • Terminals supporting privileged operator applications shall provide the user with a mechanism to remove them. NOTE: Since an operator-specific operator application provides the user interface dedicated to that operator, removing one ma... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 7 Formats and protocols | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 7.1 Operator application signalling | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 7.1.1 Launch and startup context signalling | A terminal may provide multiple entry points to the same operator application from different parts of the terminal UI. Depending on which entry point they use, the user may have different expectations. In these circumstances, the operator application needs to understand the user's expectations in order to be able to pr... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 7.1.2 Status launch parameter | The terminal shall use the parameter status to provide additional information to the operator application in the form "status=<status>" with supported values as defined in table 12. The terminal shall add the status query parameter at the end of the operator application URL, using either a "?" or a "&" character in ord... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 7.2 Extensions to broadcast signalling | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 7.2.1 Application overlay descriptor | The broadcast application signalling defined in clause 7.2.3.1 of ETSI TS 102 796 [1] shall be extended with the application overlay descriptor as defined in table 13. This descriptor is intended as a last resort in the event of inappropriate use of overlays by an operator and is not a substitute for constructive comme... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 7.2.2 Application version descriptor | The broadcast application signalling defined in clause 7.2.3.1 of ETSI TS 102 796 [1] shall be extended with the application version descriptor as defined in table 14. This descriptor provides the version and minimum version for an operator application that is signalled using a broadcast AIT (see clause 6.1.5.2) to be ... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 7.3 Extensions to broadcast-independent application signalling | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 7.3.1 Minimum application version | When used for operator applications, the broadcast-independent application signalling defined in clause 7.2.3.2 of ETSI TS 102 796 [1] shall be extended as follows to enable the signalling of a minimum version for the application. As defined in clause 6.1.8, when installing a software update for an operator application... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 7.4 Operator application ZIP File | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 7.4.1 Operator application ZIP File Format | The operator application ZIP File shall conform to ISO/IEC 21320-1 [9]. ETSI ETSI TS 103 606 V1.2.1 (2024-03) 52 |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 7.4.2 Interoperability Considerations | Some issues can arise with regards to character encodings and length of file names and relative paths of files on terminals. This clause is intended to help operators avoid potential interoperability issues on terminals. Operators shall restrict file and folder names to characters in the US-ASCII range. Operators shall... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 7.4.3 Operator application ZIP File failure conditions | Terminals shall fail the extraction process under the following conditions; • The operator application ZIP File is not conformant with clause 7.4.1 and clause 7.4.2. • The extracted file size would exceed the available storage size available on the terminal. ETSI ETSI TS 103 606 V1.2.1 (2024-03) 53 • A checksum error o... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 7.4.4 Application ZIP file contents | The application ZIP file shall contain an index.html in the top level directory. The terminal shall use the initial index.html as defined in clause 6.3.2.2. The application ZIP package shall include a copy of the XML AIT file in the root folder with a filename opapp.aitx if the encrypted operator application package ca... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 7.6 Metadata for operator application created channels | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 7.6.1 Overview (informative) | Operator applications may support the discovery of IP-delivered services that are in addition to those that the terminal discovers itself. Such operator application created channels (see clause 9.2.2) are created by passing channel metadata to the ChannelConfig.createChannelList(String) method and using the resulting C... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 7.6.2 DVB-I profile | The ChannelConfig.createChannelList(String) method shall support XML documents that satisfy the following requirements: • The XML document is a valid DVB-I Service Discovery document conforming to ETSI TS 103 770 [28]. • The document contains one or more Service elements and zero or one LCNTable elements. • The documen... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 8 Browser application environment | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 8.1 Execution model | The HTML 5 specification which is indirectly referenced through ETSI TS 102 796 [1] defines the concept of browsing contexts (see W3C Recommendation [29]) - "an environment in which Document objects are presented to the user". It further defines other related concepts including top-level browsing contexts, nested brows... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 8.2 DAE specification usage | Clause A.1 defines additional APIs from the OIPF DAE specification beyond those required by ETSI TS 102 796 [1]. That clause makes some of those additional APIs mandatory depending on a terminal's support for privileged operator applications and for operator-specific operator applications. Some of those additional APIs... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 8.3 New JavaScript APIs | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 8.3.1 APIs for access to proprietary functions | 8.3.1.1 The ProprietaryFunctionProvider class This clause is only applicable to operator-specific operator applications (as defined in clause 4.1.2). The oipfObjectFactory shall be extended to support a createProprietaryFunctionProvider method with no arguments that shall return an instance of the ProprietaryFunctionPr... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 8.3.1.2 Deprecated functions | The following functions are defined on the global JavaScript context to support proprietary features of the terminal. They are deprecated and optional: • A function named getTVProprietaryFunctions that is identical to the method getFunctions defined above except for the name. • A function named queryTVProprietaryFuncti... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 8.4 Web APIs | 8.4.1 Web Notifications |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 8.4.1.1 Requirements | • Terminals supporting service workers [i.10] shall support the WHATWG version of the Notifications API [24]. Terminals not supporting service workers shall support at least the older W3C version of the Web Notifications specification [i.3]. Whichever notifications specification is supported, it shall be supported with... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 8.4.1.2 Usage guidelines | Notifications are intended for time-critical messaging from the operator application to the user resulting from previous user actions when an operator application is in the background state. Some examples include the following: • Reminders set in an EPG which are imminent. • Previously booked live pay-per-view events t... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 8.5 APIs defined in ETSI TS 102 796 | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 8.5.1 Modification to terminalChannel | Clause 8.2.5 of ETSI TS 102 796 [1] adds a new read-only property, terminalChannel, to the Channel class. In order to allow an operator application to change the numbering of channels within the terminal channel list, an operator application shall be able to update the value of this property with any change being store... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9 System integration | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.1 Media decoder and tuner resource conflict resolution | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.1.1 Overview (informative) | The present document defines 3 ways in which broadcast video may be presented: by a regular HbbTV® application, by an operator application and the terminal itself. • Broadcast video presentation by a regular HbbTV® application is defined in ETSI TS 102 796 [1] and referenced specifications. • Broadcast video presentati... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.1.2 Sharing resources for a video/broadcast object | While the operator application is in the background, transient or overlaid transient state, any video/broadcast object in the application shall be in the Unrealized state, as defined in clause A.2.4.1. While the operator application is in the foreground or overlaid foreground state, the rules defined in ETSI TS 102 796... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.1.3 Sharing resources for other media decoders | When the selected channel is an operator application presented channel (see clause 9.9.2), the operator application may present broadband delivered media using the mechanism defined in clause 9.9. When any other type of channel is selected or no channel is selected, or when any other method of media presentation is att... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.1.4 Broadcast video presentation and privileged operator applications | When a privileged operator application is in the foreground or overlaid foreground states, the presentation of broadcast video shall be blocked and the video completely replaced by transparency if any of the following are true: • The broadcast video is being presented by a video/broadcast object in the operator applica... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.2 Channel lists (informative) | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.2.1 Background | HbbTV® terminals maintain a list of broadcast channels that can be accessed by applications. The process by which this is created and maintained is outside the scope of both ETSI TS 102 796 [1] and the present document. That process may be manufacturer specific, network/operator specific or some combination of the two.... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.2.2 Operator applications and channel lists | An operator application can offer the user content from a variety of different sources in its channel list UI as follows: 1) Channels from the terminal channel list. 2) 'Locally defined channels' - broadcast channels that may not be in the terminal channel list but that, except for this, can be used with all the HbbTV®... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.3 Display model | The display model defined in clause H.1 of the OIPF DAE specification [29] shall also apply to the present document with the following clarifications: • The main window of an operator application shall be displayed using either the "Platform-specific application graphic plane" or the "DAE application graphic plane" as ... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.4 URLs | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.4.1 Origin for an installed operator application | The origin (see [i.5]) for resources loaded from an installed operator application shall be as follows: hbbtv-package://appid.orgid where appid and orgid are the values of the application_id and organisation_id from the AIT or XML AIT from which the application was installed. Both shall be encoded as hexadecimal using ... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.4.2 Referencing installed operator applications and resources | An operator application shall be able to reference installed operator applications and resources using the hbbtv-package URL scheme defined in clause 9.4.1 as follows: • hbbtv-package://appid.orgid • hbbtv-package://appid.orgid/index.html • hbbtv-package://appid.orgid/applications/my-other-application.html An operator ... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.5 Access to broadcast carousels | Privileged or operator-specific operator applications shall be able to mount and access broadcast carousels as defined in clause 7.2.5 of ETSI TS 102 796 [1] subject to the following constraints: • Privileged operator applications shall not be able to access any carousel from a service that carries an AIT sub-table wit... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.6 Operator applications and DVB-I | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.6.1 Overview (informative) | Annex O of ETSI TS 102 796 [25] V1.7.1 defines how DVB-I service discovery can be used with HbbTV® and how DVB-I signalling can drive HbbTV® application lifecycle. Behaviour is defined for two types of linked application: "Applications with media in parallel", where the terminal handles the media presentation for the D... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.6.2 Operator application presentation of DVB-I services | Where a DVB-I service instance or its parent service has one or more linked applications of type "Operator application controlling media presentation" (see clause 7.5.1), then the Channel representing that service instance shall be considered an operator application presented channel as defined in clause 9.9 if any of ... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.6.3 Linkage of both regular and operator applications | A DVB-I service may have one or more regular HbbTV® applications linked to it as well as one or more operator applications. If one or more "Operator applications controlling media presentation" are linked together with an "Application controlling media presentation" or "Application with media in parallel", terminals sh... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.6.4 Example usage (informative) | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.6.4.1 Example 1 | A number of broadband-delivered services are included in a DVB-I service list and are managed by an operator who provides an operator application that performs all the authorization, content protection, media selection and metrics reporting functions necessary to present those services. The services are signalled with ... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.6.4.2 Example 2 | A number of broadband-delivered DVB-I services rely on an application to perform authorization, content protection, media selection and metrics reporting for the service. The services are used in a territory where an operator application is deployed for some terminals and not for others. The services are signalled with... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.7 Parental Controls | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.7.1 General | Privileged or operator-specific operator applications may require the ability to control presentation of media components via blocking and unblocking a channel subject to the bilateral agreement. This may be based on signalling associated with the media or explicit manual input from the end-user independent of the medi... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.7.2 Examples (informative) | Terminals may use the following use cases as guidance, but are not limited to only these examples. Sequence diagrams for some of these examples and other examples are in clause G.1. EXAMPLE 1: An operator has a bilateral agreement with the manufacturer to always block AV on startup of the terminal prior to starting the... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.8 WebSocket Server and JSON-RPC Implementation | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.8.1 WebSocket server | Terminals shall implement a WebSocket Server for JSON-RPC requests as defined in clause 9.9 of ETSI TS 102 796 V1.7.1 [25]. The server shall be available at all times when an operator application is running. The server shall be discoverable by presence of the json_rpc_server element in the XML capabilities document exp... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.8.2 Operator application usage | The present document defines APIs that are expressed as JSON-RPC messages sent over the WebSocket connection defined in clause 9.8.1. ETSI TS 102 796 [25] version 1.7.1 and later also define APIs that use JSON-RPC over WebSocket. Table 16a contains a summary of JSON-RPC API usage. Table 16a: JSON-RPC usage JSON-RPC API... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.8.3 API access | Terminals shall ensure that APIs that are restricted to operator applications (see table 16a) are not made available to regular HbbTV® applications and that attempts by regular HbbTV® applications to negotiate their use using the request capability negotiation mechanism defined in clause 9.9.5 of ETSI TS 102 796 [25] V... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.9 Operator application presented channels | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.9.1 Overview (informative) | Certain types of channels are designated by clause 9.9.2 as "operator application presented channels". For these channels, the terminal does not handle any video or audio presentation directly. Instead, the operator application implements the media presentation for the channel in JavaScript. Operator applications are a... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.9.2 Scope | The following channels shall be operator application presented channels: • DVB-I service instances for which the DVB-I metadata indicates that the operator application is able to handle media presentation (see clauses 9.6.2 and 7.5.1). • Operator application created channels (see clause 9.2.2) for which the DVB-I metad... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.9.3 Operator application video window | Operator applications shall at all times have access to an additional window, termed the operator application video window, into which a document can be loaded to present the media for an operator application presented channel. A document is loaded into this window (replacing any previously loaded document) as follows:... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.9.4 API for operator application presented channels | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.9.4.1 Introduction (informative) | In order to allow operator application presented channels to appear similar to broadcast channels and natively-presented IP channels, both to regular HbbTV® applications and to the user, an API is defined by which the terminal (on behalf of the user, a regular HbbTV® application or the user interface of an operator app... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.9.4.2 JSON-RPC usage | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.9.4.2.1 Supported methods | The methods defined in clauses 9.9.4.4 and 9.9.4.5 shall be supported for operator applications. except as defined in clause 10.1.1.6, these are only intended to be used by the operator application video window and should not be used by the operator application main window. Any such use should be highlighted in the bil... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.9.4.2.2 Request capability negotiation | The negotiation mechanism defined in clause 9.9.5 of ETSI TS 102 796 V1.7.1 [25] shall support the JSON-RPC requests defined in clauses 9.9.4.4 and 9.9.4.5.Terminals shall not send JSON-RPC requests defined in clause 9.9.4.5 unless the operator application video window has indicated support for the request via capabili... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.9.4.2.3 Application and terminal responses | All method calls defined in this section return a result or error property. These responses shall conform to a schema whose normative definition is found in the electronic attachments - see Annex H of the present document. The value of the result property is an object with the following properties: • The method propert... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.9.4.3 Concepts | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.9.4.3.1 Channel selection and channel sessions | Operator applications are responsible for the media presentation of an operator application presented channel. Presentation of such channels is initiated and controlled within a 'channel session'. Whenever an operator application presented channel is newly selected, whether by the user or by a regular HbbTV® applicatio... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.9.4.3.2 Channel status | A state variable called the operator application channel status is associated with a channel session and is used to inform the terminal when an operator application presented channel's media is being presented by the operator application. This allows the terminal to communicate appropriate state transitions to applicat... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.9.4.3.3 Session identifier | When an operator application creates a session to present a channel, it returns a session identifier (sessionID) value that is then passed in subsequent method calls relating to that channel selection. Session identifiers shall be positive, non- zero integers less than 2^31. A sessionID is considered valid if it matche... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.9.4.4 Operator application video window to terminal JSON-RPC requests | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.9.4.4.1 org.hbbtv.ipplayback.statusUpdate | Sets the operator application channel status (see clause 9.9.4.3.2) for an operator application presented channel session, allowing the terminal to transition the state of any video/broadcast objects bound to the channel as well as reporting the transition to any BroadcastSupervisor object in use. These requests shall ... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.9.4.4.2 org.hbbtv.ipplayback.mediaPositionUpdate | Updates the play position and related parameters for the presentation of an operator application presented channel, allowing the terminal to update the corresponding properties of any video/broadcast objects bound to the channel and any BroadcastSupervisor object in use. Terminals shall fire any video/broadcast and/or ... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.9.4.4.3 org.hbbtv.ipplayback.setComponents | Updates the set of audio, video and subtitle components that are available in the media of an operator application presented channel, allowing the terminal to update the corresponding properties of any video/broadcast objects bound to the channel and any BroadcastSupervisor object in use, as well as allowing the termin... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.9.4.4.4 org.hbbtv.ipplayback.setTimelineMapping | Provides synchronisation timeline mapping information for an operator application presented channel. These requests shall conform to a schema whose normative definition is found in Annex H of the present document. It is expected that this method will be called in response to an org.hbbtv.ipplayer.resolveTimeline reques... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.9.4.4.5 org.hbbtv.ipplayback.setPresentFollowing | Updates the current and next programme metadata of the current channel. The metadata provided allows the terminal to update the corresponding programmes property of the video/broadcast and BroadcastSupervisor objects, as well as allowing the terminal to populate any 'now and next' user interface elements that have not ... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.9.4.5 Terminal to operator application video window JSON-RPC requests | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.9.4.5.1 org.hbbtv.ipplayer.selectChannel | Informs the operator application that a new operator application presented channel has been selected and requests the operator application create a new channel session and start playback. These requests and responses shall conform to a schema whose normative definition is found in Annex H of the present document. This ... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.9.4.5.2 org.hbbtv.ipplayer.stop | Requests the operator application stop presentation of an operator application presented channel, releasing associated resources. These requests shall conform to a schema whose normative definition is found in Annex H of the present document. This method is called when the terminal needs to stop the presentation of the... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.9.4.5.3 org.hbbtv.ipplayer.play | Requests the operator application to re-start playback of the currently-selected operator application presented channel. These requests shall conform to a schema whose normative definition is found in Annex H of the present document. This method is called when the terminal needs to start presentation for any reason, in... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.9.4.5.4 org.hbbtv.ipplayer.setVideoWindow | Instructs the player to position the video for an operator application presented channel at a specified location. These requests shall conform to a schema whose normative definition is found in Annex H of the present document. This method is called by the terminal whenever the video size and position needs to change. E... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.9.4.5.5 org.hbbtv.ipplayer.setRelativeVolume | Instructs the player to adjust the relative volume for an operator application presented channel. These requests shall conform to a schema whose normative definition is found in Annex H of the present document. This method is called by the terminal whenever the relative volume needs to change. Example of when this may ... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.9.4.5.6 org.hbbtv.ipplayer.pause | Requests the player to pause playback. These requests shall conform to a schema whose normative definition is found in Annex H of the present document. This method is called when the pause method is called on a video/broadcast object bound to an operator application presented channel. The operator application should re... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.9.4.5.7 org.hbbtv.ipplayer.resume | Requests the player to resume playback after a pause. These requests shall conform to a schema whose normative definition is found in Annex H of the present document. This method is called when the resume method is called on a video/broadcast object bound to an operator application presented channel. The operator appli... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.9.4.5.8 org.hbbtv.ipplayer.seek | Requests the player to seek to a new position. These requests shall conform to a schema whose normative definition is found in Annex H of the present document. This method is called when the seek method is called on a video/broadcast object bound to an operator application presented channel. The operator application sh... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.