hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
d3083915de487502dfd3dbd7175d6266 | 103 607 | 6.7.3 Attenuation Range in Receive Direction during Double Talk | Requirement: Based on the level variation in receive direction during double talk AH,R,dt the behaviour of the terminal can be classified according to Table 6.6. Table 6.6: Category Classification of Receive Attenuation Range Category (according to Recommendation ITU-T P.340 [9]) 1 2a 2b 2c 3 Full Duplex Capability Par... |
d3083915de487502dfd3dbd7175d6266 | 103 607 | 6.7.4 Detection of echo components during Double Talk | Requirement: "Echo Loss" (EL) is the echo suppression provided by the terminal measured at the electrical reference point. Under these conditions the requirements given in Table 6.7 are applicable (more information can be found in annex A of the Recommendation ITU-T P.340 [9]). Table 6.7: Echo Classification during Dou... |
d3083915de487502dfd3dbd7175d6266 | 103 607 | 6.8 Switching parameters | |
d3083915de487502dfd3dbd7175d6266 | 103 607 | 6.8.1 Activation in Send Direction | The activation in send direction is mainly determined by the built-up time Tr,S,min and the minimum activation level (LS,min). The minimum activation level is the level required to remove the inserted attenuation in send direction during idle mode. The built-up time is determined for the test signal burst which is appl... |
d3083915de487502dfd3dbd7175d6266 | 103 607 | 6.9 Background noise performance | |
d3083915de487502dfd3dbd7175d6266 | 103 607 | 6.9.1 Performance in send direction in the presence of background noise | Requirement: The level of comfort noise, if implemented, shall be within a range of +2 dB and -5 dB compared to the original (transmitted) background noise. The noise level is calculated with A weighting. NOTE 1: It is advisable that the comfort noise matches the original signal as much as possible perceptually. The sp... |
d3083915de487502dfd3dbd7175d6266 | 103 607 | 6.9.2 Speech Quality in the Presence of Background Noise | Requirement: Speech Quality for wideband systems can be tested based on ETSI TS 103 106 [18]. The test method described leads to three MOS-LQO quality numbers: • N-MOS-LQOwb: Transmission quality of the background noise. • S-MOS-LQOwb: Transmission quality of the speech. • G-MOS-LQOwb: Overall transmission quality. For... |
d3083915de487502dfd3dbd7175d6266 | 103 607 | 6.9.3 Quality of Background Noise Transmission (with Far End Speech) | Requirement: The test is carried out applying a speech signal in receive direction. The test is carried out by comparing the noise level transmitted in the sending direction under reference conditions with no far end speech, to the noise level transmitted in the sending direction under test conditions including far end... |
d3083915de487502dfd3dbd7175d6266 | 103 607 | 6.10 Quality of echo cancellation | |
d3083915de487502dfd3dbd7175d6266 | 103 607 | 6.10.1 Temporal echo effects | Requirement: This test is intended to verify that the system will maintain sufficient echo attenuation during single talk. The measured echo attenuation during single talk should not decrease by more than 6 dB from the maximum measured echo attenuation. ETSI ETSI TS 103 607 V1.1.1 (2024-07) 31 Measurement method: Test ... |
d3083915de487502dfd3dbd7175d6266 | 103 607 | 6.10.2 Spectral Echo Attenuation | Requirement: The echo attenuation vs. frequency shall be below the tolerance mask given in Table 6.11. Table 6.11: Spectral Echo Loss Limits Frequency Limit 100 Hz -41 dB 1 300 Hz 3 450 Hz -41 dB -46 dB 5 200 Hz -46 dB 7 500 Hz 8 000 Hz -37 dB -37 dB NOTE 1: All sensitivity values are expressed in dB on an arbitrary sc... |
d3083915de487502dfd3dbd7175d6266 | 103 607 | 6.10.3 Variable echo path | Requirement The echo level measured with a time varying echo path shall not increase by more than 6 dB compared to the echo level observed under steady state conditions. Measurement method The test setup is described in clause 5.2.3. 1) Before conducting the test, the echo canceller shall be fully converged. 2) The tes... |
d3083915de487502dfd3dbd7175d6266 | 103 607 | 6.11 Send and receive delay or round trip delay | Requirement: Send and receive delays are tested separately but the requirement is defined for the combination of send and receive delays (round-trip delay). It is recognised that the end-to-end delay should be as small as possible in order to ensure high quality of the communication. The round-trip delay Trtd (sum of s... |
d3083915de487502dfd3dbd7175d6266 | 103 607 | 7.1 Speech Coders | The present document is intended to be applicable for different speech coders implemented in access networks and additional links. Table 7.1 defines a list of speech coders implemented (non exhaustive). Table 7.1: List of speech coders System Codec GSM 850, 900, 1 800, 1 900 AMR-WB ETSI TS 126.171 [1] UMTS (WCDMA), VoL... |
d3083915de487502dfd3dbd7175d6266 | 103 607 | 7.2 Objective listening Quality in send and receive direction | |
d3083915de487502dfd3dbd7175d6266 | 103 607 | 7.2.1 Objective listening quality MOS-LQO in send direction | The listening speech quality tests are conducted under clean network conditions. Performance Objective The performance objective for the objective listening speech quality in send direction (MOS-LQO) is equal or greater than 4.0, i.e. "Good" in the Mean Opinion Score scale. NOTE: Not sufficient experience is available ... |
d3083915de487502dfd3dbd7175d6266 | 103 607 | 7.2.2 Objective listening quality MOS-LQO in receive direction | The listening speech quality tests are conducted under clean network conditions. Performance Objectives The performance objective for the listening speech quality (MOS-LQO) in receive direction is equal or greater than 3.0, i.e. "Fair" in Mean Opinion Score scale. NOTE: Not sufficient experience is available so far wit... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 1 Scope | The present document specifies a platform, based on the existing HbbTV® specification ETSI TS 102 796 [1], that supports the signalling, transport and presentation of an operator application. The operator application is able to replace some of the terminal's user interface. The extent to which the terminal user interfa... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 2 References | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 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... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 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... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 3 Definition of terms, symbols and abbreviations | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 3.1 Terms | For the purposes of the present document, the following terms apply: bilateral agreement: agreement between a terminal manufacturer and an operator defining commercial, operational, technical and user interface arrangements for the use of an operator application broadband: bi-directional IP connection with sufficient b... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 3.2 Symbols | Void. |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AIT Application Information Table APDU Application Protocol Data Unit API Application Programme Interface A/V Audio/Video ASCII American Standard Code for Information Interchange BAT Bouquet Association Table CA Certificate Authority CSP Conte... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 4 Overview | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 4.1 Operator applications (informative) | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 4.1.1 Scope and motivation | Operator applications replace parts or all of the user interface that is otherwise provided by the Terminal. Typically, this includes UI elements of TV watching mode (e.g. channel info banner and channel selection) and the electronic program guide (EPG). Using operator applications allows for: • Implementation of a hom... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 4.1.2 Types of operator applications | There are three types of operator applications as shown in table 1. Table 1: Types of Operator Applications Standard Standard operator applications are HbbTV® applications as defined in ETSI TS 102 796 [1]. They do not replace UI elements of the terminal but may provide alternatives to some of them. The present documen... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 4.1.3 Standard operator applications | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 4.1.3.1 Introduction | To a certain degree it is possible to use regular HbbTV® applications to implement typical features provided by an operator. Such applications (referred to as standard operator applications) are usually broadcast-related, and they are signalled on all channels of the operator. The following clauses describe the user ex... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 4.1.3.2 Features of standard operator applications | Standard operator applications cannot replace UI elements of the terminal but may provide alternatives to some of them such as: • EPG. • Channel list. • List of other applications of the operator. • Promotion of the operator and its content. |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 4.1.3.3 Design policy for standard operator applications | The design of a standard operator application is solely under the responsibility of the operator. |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 4.1.3.4 TV channels | A standard operator application is usually only available on channels of the operator. As soon as the user selects a channel that is not offered by the operator, the standard operator application is terminated. The user may set up a favourite channel list including all channels of the operator. In that case, zapping th... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 4.1.3.5 Activating and launching of standard operator applications | It is neither possible nor required for the user to activate a standard operator application before it is actually launched. The operator and the broadcaster decide how the operator's standard operator application is launched. It may be one of the following: • The operator application is launched automatically as soon ... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 4.1.3.6 User input for standard operator applications | Standard operator applications can only use key events of buttons as defined for regular HbbTV® applications. ETSI ETSI TS 103 606 V1.2.1 (2024-03) 17 |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 4.1.4 Privileged operator applications | A privileged operator application replaces some parts of the user interface of the terminal. Typically, that includes content related UI elements in TV watching mode such as: • Channel info banner. • Channel selection: - Channel list. - Channel number input. - Zapping. • Component selection: - Audio stream selection. -... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 4.1.5 Operator-specific operator applications | An operator-specific operator application can implement all features of privileged operator applications but it can also replace further parts or even all of the user interface of the terminal. It can provide a user experience comparable to that of set-top boxes of PayTV providers. ETSI ETSI TS 103 606 V1.2.1 (2024-03)... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 4.1.6 Coexistence between multiple types of operator application | Standard operator applications, privileged operator applications and operator-specific operator applications may be mixed in a single market or deployment. This could enable a baseline user experience for consumers using a standard HbbTV® terminal and an enhanced user experience for consumers using an implementation of... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 4.1.7 Operator applications and channel binding | In contrast to the concept for channel binding of regular HbbTV® broadcast-related applications as defined in ETSI TS 102 796 [1], the present document does not define any technical means to bind an operator application to a group of channels. It is the operator's responsibility to ensure that no legal or business rule... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 4.1.8 Enabling operator applications to be installed and run | The present document does not require terminals to automatically install every privileged or operator-specific operator application which is signalled on the network or which is otherwise detected. An operator cannot expect that its operator application automatically runs on every terminal even if the terminal in princ... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 4.1.9 Number of operator applications | A terminal may support only one or several privileged or operator-specific operator applications. In any case only one of these operator applications can run at a certain time. If several operator applications are supported and available, the terminal provides a method to select one, usually using one of the following ... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 4.2 Architecture (informative) | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 4.2.1 Introduction | This clause gives an overview of a system architecture of a terminal. The architecture which allows for the provision of operator applications comprises a browser, application signalling via broadcast, broadband and from a companion device, application transport via broadcast, broadband and from a CICAM, and synchroniz... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 4.2.2 System overview | Regarding the usage of operator applications a terminal has the capability to be connected to two networks in parallel. On one side it can be connected to a broadcast DVB network. Via this broadcast connection the terminal can receive operator applications as well as regular HbbTV® applications. Due to the uni-directio... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 4.3 Referenced W3C and WHATWG Specifications | Clause 4.5 of ETSI TS 102 796 [1] concerning references to W3C and WHATWG specifications shall also apply to W3C and WHATWG specifications referenced from the present document. Figure 1: System overview for an operator application terminal |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 4.4 Dependencies | Operator applications shall be able to successfully call all APIs and successfully use all features and functions that a regular HbbTV® application on the same terminal is able to use, unless otherwise stated in the present document. For example, the ability to present broadcast and broadband delivered video and audio ... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 8.4.1 Web Notifications | API availability. |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 9.9.6 Resource management considerations | A.2.1 Configuration class: • runningOperatorApplication property A.2.2 Application class: • opAppState property • createApplication() method • getApp2OpAppBaseUrl() method |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 5 User experience (informative) | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 5.1 Introduction | This clause describes the usage of operator applications as seen by the end-user. It should be considered as guidelines for implementing operator applications and for setting up the bilateral agreements between manufacturer and operator. |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 5.2 Using operator applications | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 5.2.1 Activation and deactivation | The terminal provides means to activate an operator application. The provided method may depend on the following: • Types of supported operator applications • Number of supported operator applications • Requirements of the target markets • User interaction paradigms of the terminal Table 2 introduces some typical metho... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 5.2.2 User input | The user controls operator applications using a user input device typically supplied with the terminal. This may be a conventional remote control or an alternative input device. Table 3 describes the buttons or key events that are relevant for the end user when using operator applications. Which of these buttons are ac... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 5.3 Displaying operator applications | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 5.3.1 General visibility of operator applications | If an operator application is activated, it is not automatically visible to the user. Instead, the operator application can become visible in cases like the following: • The operator application has been selected as a source. • The user has left an application of the terminal (e.g. Set-up or HbbTV® application menu) an... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 5.3.2 Start page | The operator application may have different start pages depending on the launch and/or startup contexts. For example: • Selecting the operator application in the source selection menu may lead to decoding a TV channel and showing the channel info banner of the operator application. • Pressing the GUIDE button while usi... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 5.3.4 Co-existence of operator application and terminal UI | If the operator application does not provide all UI elements of TV watching mode, the UI of the operator application may be overlaid with UI of the terminal in certain cases. Typical examples are system messages or the volume control banner or a parental control dialogue. If the operator application provides all necess... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 5.4 Design policy | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 5.4.1 Branding | Usually, an operator application is designed and branded by the operator in agreement with the manufacturer. Due to market specific regulations it may be necessary to offer the operator application with a branded and a neutral design for channels of the operator and other channels, respectively. |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 5.4.2 User interface design constraints | If broadcast content is running, the display of graphics by privileged operator applications is limited to the following: • UI responses to user input for up to 60s using the Transient state defined in clause 6.3.3.4. • Display of a channel information banner when the channel is changed, also using the Transient state.... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 5.5 Further concepts | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 5.5.1 Channels not offered by the operator | Central elements of operator applications such as the channel info banner are usually displayed in parallel or on top of a TV channel. Due to legal or business requirements it might be necessary to prevent the operator application from showing its user interface on channels not offered by the operator. There are four t... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6 Service and application model | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.1 Operator application discovery and installation | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.1.1 Overview | The following clause describes the process the terminal shall perform to discover, retrieve and install an operator application. The present document allows deployment scenarios both with and without an operational broadband connection. In both scenarios, an operator application is described by an AIT (either in binary... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.1.2 Triggering operator application discovery | The process of operator application discovery shall be triggered by the conditions listed in table 6. ETSI ETSI TS 103 606 V1.2.1 (2024-03) 26 Table 6: Triggering operator application discovery process Trigger Scope of resulting discovery Terminal is being installed and there is at least one applicable operator applica... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.1.3 Operator application discovery methods | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.1.3.1 Introduction | The terminal discovers and retrieves the location of the (XML) AIT as represented by a URI. The URI shall adhere to rules specified in clause 9.2 of ETSI TS 102 796 [1]. The location of the (XML) AIT is signalled by the operator using one or more of the following methods: 1) Broadcast NIT/BAT containing a URI_linkage_d... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.1.3.2 Broadcast NIT/BAT with URI_linkage_descriptor with operator FQDN | The terminal shall parse the first loop of the broadcast NIT/BAT used for service discovery to locate the URI_linkage_descriptors matching the profile in Annex B and with a scheme of "dns" in the uri_char. If any are found, the terminal shall extract the FQDN from the uri_char of each of them, which should each be a DN... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.1.3.3 Broadcast NIT/BAT with URI_linkage_descriptor with URI of AIT | The terminal shall parse the first loop of the broadcast NIT/BAT used for service discovery to locate the URI_linkage_descriptors matching the profile in Annex B and with a scheme of "dvb" in the uri_char. If any are found, the terminal shall extract the DVB URI from the uri_char of each of them and perform the process... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.1.3.4 NIT from CICAM with uri_linkage_descriptor with URI of XML AIT | If the terminal supports Operator Profile (as specified in CI Plus Specification vV1.3.2 [5]) and the CICAM reports a profile_type of 1, the terminal shall parse the first loop of the NIT from the CICAM to locate the URI_linkage_descriptors matching the profile in Annex B and with a scheme of either "https" or "ci://" ... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.1.3.5 Hardwired in terminal with operator FQDN | If the terminal is provisioned with an operator FQDN appropriate for the country for which the terminal is configured, then the terminal shall perform the process defined in clause 6.1.4. NOTE: The bilateral agreement where the operator FQDN is specified may define which countries are appropriate for its use. |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.1.3.6 Hardwired in terminal with URI of XML AIT | If the terminal is provisioned with URI to an XML AIT appropriate for the country for which the terminal is configured, then the terminal shall perform the process defined in clause 6.1.5.1. This shall be an "https://" URI. NOTE: The bilateral agreement where the operator XML AIT is specified may define which countries... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.1.3.7 DNS SRV lookup to a standardized address | The terminal shall use the FQDN "hbbtvopapps.org" and shall perform the process defined in clause 6.1.4. NOTE: This mechanism is intended for use only within an operator's IP network and would likely not work in the open internet. This FQDN is deliberately different from that used in ETSI TS 103 464 [i.1] which will be... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.1.5 (XML) AIT acquisition and download | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.1.5.1 XML AIT acquisition | If the terminal discovers the location of an XML AIT using DNS SRV as defined in clause 6.1.4, the terminal shall perform a HTTP GET request based on the priority and weighting of the returned SRV records as specified in IETF RFC 2782 [6]. If an HTTP GET request for one XML AIT fails, the terminal shall perform another... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.1.5.2 AIT Acquisition | The terminal shall tune to the DVB services identified by the DVB URIs discovered in clause 6.1.2 and search for an AIT table with the application type 0x10 according to the rules specified in clause 7.2.3 of ETSI TS 102 796 [1]. The terminal shall look for AIT entries with application usage types supported by the term... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.1.6 Deciding which operator applications to install | The result of the previous processes is a number of (XML) AITs each corresponding to an operator application where a bilateral agreement is in place for the terminal. Which of these are installed depends on a number of factors: • For operator-specific operator applications, the appropriate operator-specific operator ap... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.1.7 Encrypted application package download | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.1.7.1 Introduction (informative) | The present document defines three mechanisms by which an encrypted application package can be downloaded: • HTTP over TLS via broadband IP; • DSM-CC object carousel over broadcast, and • CIPlus Auxiliary File System. Each of these is described in more detail below. ETSI ETSI TS 103 606 V1.2.1 (2024-03) 32 |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.1.7.2 Encrypted application package download via IP | The terminal shall perform an HTTP GET request to download the encrypted application package from the URI defined in the location descriptor of the retrieved XML AIT (see clause 6.1.5.1). The terminal shall provide the HTTP User-Agent as defined in clause 7.3.2.4 of ETSI TS 102 796 [1] when requesting the encrypted app... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.1.7.3 Encrypted application package download via DSM-CC object carousel | The terminal shall use the simple application location descriptor in the retrieved AIT (see clause 6.1.5.2) to download the encrypted application package onto the terminal. The terminal shall decrypt and verify the encrypted application package as defined in clause 6.1.8. If the DSM-CC object cannot be accessed (e.g. t... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.1.7.4 Encrypted application package download from CI Plus AuxFS | When the applicationTransport field in the XML AIT is set to CITransportType, the Terminal shall use the applicationLocation element as the reference of the encrypted application package to be obtained from the CI Plus Auxiliary File System. The terminal shall decrypt and verify the encrypted application package as def... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.1.8 Decrypt, verify, unpack and installation of the application package | The terminal shall decrypt the encrypted application package as defined in clause 11.3.4.4 using the Terminal Packaging Certificate and corresponding private key. The terminal shall verify the signature of the decrypted application ZIP package as specified in clause 11.3.4.5. The terminal shall consider the application... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.1.9 Installation failures | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.1.9.1 Installation failure overview | During the discovery and installation of an operator application, there are several points in the process where failures may occur. These failure conditions can be divided into two categories: a) If the installation request is initiated for the first time and there is no previous operator application from this operator... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.1.9.2 Failure handling on first-time installation | Terminals may encounter failure conditions during the first-time installation of an operator application. This clause outlines how a terminal handles the failure. Terminals may have initiated the first-time installation of the operator application as described by clause 5.2.1. If a failure occurs during a user-initiate... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.1.9.3 Failure handling when updating an operator application | Terminals may encounter installation failures during an update requested by the operator application using the opAppRequestUpdate() method defined in clause A.2.2.2. The method allows for the action to take place immediately or at a time convenient to the user. If the operator application update was requested to occur ... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.2 Updating operator applications | Once an operator application has been installed, it is solely responsible for updates, the present document does not define any mechanism or responsibility for the terminal to initiate the update of an operator application. Operator applications are able to request they be updated by calling the opAppRequestUpdate meth... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.3 Operator application lifecycle | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.3.1 Introduction | The operator application lifecycle is determined by the following four factors: 1) The application state model. 2) The activation of the operator application by the user or by some other means. 3) The termination of the operator application under certain conditions. 4) The terminal entering and leaving modes where line... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.3.2 Starting and stopping operator applications | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.3.2.1 Summary (Informative) | A number of ways are defined by which an operator application can be started. Directly by the end-user (e.g. by using a 'select source' menu to switch to the operator application 'source' or by pressing an operator application key (see clause 10.1.3) like EPG or channel list or by pressing a dedicated operator key). A ... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.3.2.2 Starting operator applications | The initial document of an operator application shall be "index.html" in the top level directory of the application ZIP file. When starting an installed operator application, the terminal shall load and run this "index.html" file. The "index.html" shall be run using a URL constructed according to clause 9.4.2 with the ... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.3.2.3 Stopping operator applications | If an operator application is stopped by the terminal under error conditions (e.g. out of memory) then the operator application shall be restarted. If an operator application is stopped for either of the following reasons then the behaviour will be determined by the bilateral agreement: • By the operator application it... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.3.2.4 Co-existence of multiple operator applications | Two operator applications cannot run at the same time. One operator application can launch another one. In that case the first operator application is terminated. Terminals may support simultaneous installation of more than one operator application including but not limited to the following scenarios: • operator applic... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.3.3 Operator application states | |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.3.3.1 Introduction | A running operator application shall be in one of five states: background state, foreground state, transient state, overlaid foreground state or overlaid transient state. These states are listed for information in table 9. Table 9: Operator application states (informative) State Example Focus opAppState property (See c... |
fd24fad8e043d577082e42a39705c6c2 | 103 606 | 6.3.3.2 Foreground state | The terminal shall move the operator application to this state when any of the following are true: • The operator application is in the background or transient state and it makes a successful call to the opAppRequestForeground method: - The call shall be successful if it was made within a handler for keydown, keyup or ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.