hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
077cc2fe8c4c016045fdddf02703eea4 | 102 797-3 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ISO 24102-4 [1], ISO 24102-5 [2], TS 102 797-1 [3], TS 102 797-2 [4], ISO/IEC 9646-1 [5], ISO/IEC 9646-2 [6], ETS 300 406 [7], ES 201 873-1 [8], ES 201 873-7 [9], ES 202 784 [10], ISO 24102-3 [i.1], ISO 21217 [i.2], ISO 21218 [i.3] and EG 202 798 [i.4... |
077cc2fe8c4c016045fdddf02703eea4 | 102 797-3 | 4 Abstract protocol tester | In general, the conformance test system architecture as illustrated in the ITS testing framework EG 202 798 [i.4], see figure 1, applies. For the present document, the IUT is given by protocols located in the ITS-S management entity, thus several types of IUTs need to be considered. The "Upper tester application" allow... |
077cc2fe8c4c016045fdddf02703eea4 | 102 797-3 | 5 Abstract test method for FSAP | |
077cc2fe8c4c016045fdddf02703eea4 | 102 797-3 | 5.1 Abstract protocol tester | SUTs which support the "ITS station-Internal management Communications Protocol" (IICP) ISO 24102-4 [1] may benefit from the conformance test system architecture illustrated in figure 2, where the access to the IUT from top, i.e. in general via the upper tester application, is performed via management SAPs. Codec M F-S... |
077cc2fe8c4c016045fdddf02703eea4 | 102 797-3 | 5.2 Test configurations | |
077cc2fe8c4c016045fdddf02703eea4 | 102 797-3 | 5.2.1 Roles of an ITS-SCU | The test suite for FSAP uses two test configurations in order to cover the different test scenarios. Distinction between the two configurations is given by the two possible implementation scenarios for an ITS station, i.e. a single-unit implementation, or an implementation with several "ITS station communication units"... |
077cc2fe8c4c016045fdddf02703eea4 | 102 797-3 | 5.2.2 Test configuration CF01: No ITS station-internal network | In test configuration CF01 the roles of ITS-S host and ITS-S router are implemented in a single ITS-SCU as illustrated in figure 3. Consequently the whole supported functionality of FSAP is given in a single ITS-SCU and no station- internal forwarding between ITS-S host and ITS-S router is needed. Networking & transpor... |
077cc2fe8c4c016045fdddf02703eea4 | 102 797-3 | 5.2.3 Test configuration CF02: ITS station-internal network | In test configuration CF02, the roles of ITS-S host and ITS-S router are implemented in different ITS-SCUs as illustrated in figure 4. Consequently there is communications needed between the ITS-SCU with host functionality and the ITS-SCU with router functionality. This communication goes via the ITS station-internal n... |
077cc2fe8c4c016045fdddf02703eea4 | 102 797-3 | 5.3 Test architecture | The present document implements the general TTCN-3 test architecture described in EG 202 798 [i.4], clauses 6.3.2 and 8.3.1. Figure 5 shows the TTCN-3 test architecture used for the FSAP ATS. • The MTC is of type ItsFSAP and communicates with the SUT over fsapPort in order to exchange FSAP messages (SAM, CTX) between t... |
077cc2fe8c4c016045fdddf02703eea4 | 102 797-3 | 5.4 Ports and abstract service primitives | |
077cc2fe8c4c016045fdddf02703eea4 | 102 797-3 | 5.4.1 Overview | The following TTCN-3 ports are used by the FSAP ATS: • fsapPort of type FsapPort is used to receive messages from and transmit messages to the IUT (via MF-SAP). • utPort of type UpperTesterPort is used to receive service message from and transmit service messages to the IUT (via MF-SAP). Every port provides "Abstract S... |
077cc2fe8c4c016045fdddf02703eea4 | 102 797-3 | 5.4.2 ASPs of the fsapPort | The following ASPs are used in the fsapPort: • The FsapReq primitive used to send messages of type NFsapPrimitivesUp or INsapPrimitivesUp sent by the IUT. • The FsapInd primitive used to receive messages of type NFsapPrimitivesDown or INsapPrimitivesDown from the IUT. ETSI ETSI TS 102 797-3 V1.2.1 (2014-06) 12 |
077cc2fe8c4c016045fdddf02703eea4 | 102 797-3 | 5.4.3 ASPs of the utPort | The following ASPs are used in the utPort: • The UtInitialize primitive is used to initialize IUT. • The FAsapPrimitivesDown primitive is used to send FA-SAP service primitives to the IUT. • The FAsapPrimitivesUp primitive is used to receive FA-SAP service primitives from the IUT. |
077cc2fe8c4c016045fdddf02703eea4 | 102 797-3 | 6 Abstract Test Method for IICP | |
077cc2fe8c4c016045fdddf02703eea4 | 102 797-3 | 6.1 Abstract protocol tester | SUTs which support the "ITS station-Internal management Communications Protocol" (IICP) ISO 24102-4 [1] may benefit from the conformance test system architecture illustrated in figure 6, where the access to the IUT from top, i.e. in general via the upper tester application, is performed via management SAPs. Codec M F-S... |
077cc2fe8c4c016045fdddf02703eea4 | 102 797-3 | 6.2 Test configurations | IICP becomes applicable once an ITS station-internal network is available. This results in the basic configuration illustrated in figure 7, where the SUT is an ITS-SCU which either has the role of an ITS-S router, or an ITS-S host, or a combined ITS-S host and router and where the ITS test system simulates such an ITS-... |
077cc2fe8c4c016045fdddf02703eea4 | 102 797-3 | 6.3 Test architecture | The present document implements the general TTCN-3 test architecture described in EG 202 798 [i.4], clauses 6.3.2 and 8.3.1. Figure 8 shows the TTCN-3 test architecture used for the IICP ATS. • The MTC is of type ItsIICP and communicates with the SUT over iicpPort in order to exchange IICP PDUs between the IICP test co... |
077cc2fe8c4c016045fdddf02703eea4 | 102 797-3 | 6.4 Ports and abstract service primitives | |
077cc2fe8c4c016045fdddf02703eea4 | 102 797-3 | 6.4.1 Overview | The following TTCN-3 ports are used by the IICP ATS: • iicpPort of type IicpPort is used to receive messages from and transmit messages to the IUT (via MF-SAP). • utPort of type UpperTesterPort is used to receive service message from and transmit service messages to the IUT. • cfPort of type CfPort is used to configure... |
077cc2fe8c4c016045fdddf02703eea4 | 102 797-3 | 6.4.2 ASPs of the iicpPort | Two ASPs are used in the iicpPort: • The IicpReq primitive used to receive messages of type IIC-Request or IIC-Response sent to the IICA by the IUT. • The IicpResp primitive used to send messages of type IIC-Request or IIC-Response received from the IUT. These primitives use IICP types, which are declared in the CALMii... |
077cc2fe8c4c016045fdddf02703eea4 | 102 797-3 | 6.4.3 ASPs of the utPort | The following ASPs are used in the utPort: • The UtInitialize primitive is used to initialize IUT. • The MX-Command-request, MX-Request, MI-Get-request, MI-Set-Request and McmdRq primitives are used to send service primitives. |
077cc2fe8c4c016045fdddf02703eea4 | 102 797-3 | 7 ATS conventions | |
077cc2fe8c4c016045fdddf02703eea4 | 102 797-3 | 7.1 Testing conventions | |
077cc2fe8c4c016045fdddf02703eea4 | 102 797-3 | 7.1.1 Testing states | |
077cc2fe8c4c016045fdddf02703eea4 | 102 797-3 | 7.1.1.1 Initial state | All test cases start with the function f_prInitialState. This function brings the IUT in an "initialized" state by invoking the upper tester primitive UtInitialize. |
077cc2fe8c4c016045fdddf02703eea4 | 102 797-3 | 7.1.1.2 Final state | All test cases end with the function f_poDefault. This function brings the IUT back in an "idle" state. As no specific actions are required for the idle state in the base standards ISO 24102-4 [1] and ISO 24102-5 [2], the function f_poDefault does not invoke any action. As necessary, further actions may be included in ... |
077cc2fe8c4c016045fdddf02703eea4 | 102 797-3 | 7.1.2 Message types - ASN.1 definitions | Message types are defined in ASN.1. ASN.1 definitions from the base standards ISO 24102-4 [1] and ISO 24102-5 [2] are directly imported in TTCN-3 using the ASN.1 import method specified in ES 201 873-7 [9]. The following example shows the TTCN-3 import statement used to import ASN.1 definitions from ISO 24102-5 [2] in ... |
077cc2fe8c4c016045fdddf02703eea4 | 102 797-3 | 7.2 Naming conventions | |
077cc2fe8c4c016045fdddf02703eea4 | 102 797-3 | 7.2.1 General guidelines | This test suite follows the naming convention guidelines provided in EG 202 798 [i.4]. |
077cc2fe8c4c016045fdddf02703eea4 | 102 797-3 | 7.2.2 Usage of Log statements | All TTCN-3 log statements use the following format: • Three asterisks followed by a blank character. • The TTCN-3 test case or function identifier in which the log statement is defined followed by a colon and a blank character. • One of the log categories: INFO, WARNING, ERROR, PASS, FAIL, INCONC, TIMEOUT followed by a... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 1 Scope | The present document defines a platform for signalling, transport and presentation of enhanced and interactive applications designed for running on hybrid terminals that include both a DVB compliant broadcast connection and a broadband connection to the internet. |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 2 References | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 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... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 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... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 3 Definitions and abbreviations | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: application data: set of files comprising an application, including HTML, JavaScript, CSS and non-streamed multimedia files broadband: always-on bi-directional IP connection with sufficient bandwidth for streaming or downloading A/V co... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: A/V Audio Video AAC Advanced Audio Coding AD Audio Description AES Advanced Encryption Standard AFD Active Format Description AFS Auxiliary File System AG Application Gateway AIT Application Information Table APDU Application Protocol Data Uni... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 4 Overview | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 4.1 Applications | The web-based Hybrid Broadcast Broadband terminal as defined in the present document provides download and execution of applications which are defined as a collection of documents constituting a self-contained enhanced or interactive service. The documents of an application are HTML, JavaScript, CSS, XML and multimedia... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 4.2 Architecture (informative) | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 4.2.1 Introduction | This clause gives an overview of the system architecture and explains the necessary functional components inside a hybrid terminal. The level of detail of this explanation is general and abstract. Details about the internal structure of the components (e.g. whether the DSM-CC client has an integrated cache or not) or a... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 4.2.2 System overview | A hybrid terminal has the capability to be connected to two networks in parallel. On the one side it can be connected to a broadcast DVB network (e.g. DVB-T, DVB-S or DVB-C). Via this broadcast connection the hybrid terminal can receive standard broadcast A/V (i.e. linear A/V content), non-realtime A/V content, applica... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 4.2.3 Functional terminal components | Figure 2 depicts an overview of the relevant functional components inside of a hybrid terminal. These components are described below the figure. ETSI ETSI TS 102 796 V1.5.1 (2018-09) 28 Figure 2: Functional components of a hybrid terminal Via the Broadcast Interface the terminal receives AIT data, linear A/V content, n... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 4.3 Terminal capabilities and extensions | The present document defines a base level (or set of capabilities for terminals) which shall be supported in all terminals. This base level supports interactive applications: • Which do not use video as part of their UI. • Which use broadcast video as part of their UI. • Which use unicast streaming content on demand as... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 4.4 Specification overview | The present document specifies the technical requirements for the system described in the previous clauses. It largely references parts of already available standards and specifications and adapts these parts where necessary. The most significant referenced documents are the following: • W3C HTML5 [54], as profiled by ... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 4.5 Referenced W3C Specifications | The present document requires support for the OIPF DAE Web Standards TV Profile (see clause A.1). Some normative references in that document are to W3C specifications which have not yet been fully approved or which might still be under development. In these cases, the reference is to a specific dated version of the spe... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 5 User experience (informative) | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 5.0 Introduction | This clause describes the behaviour of the terminal as seen by the end-user. It should be considered as usability guidelines for implementing interactivity. However, the described behaviour usually results from the functionality coded into the broadcast application, rather than the terminal. A homogenous user experienc... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 5.1 Visual appearance of interactive applications | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 5.1.1 Balance of video and application | Table 1 illustrates the range of different visual appearances the end user might experience. Each "screen" shows a different balance between "conventional TV" content and information delivered by an interactive application. ETSI ETSI TS 102 796 V1.5.1 (2018-09) 32 Table 1: Typical range of programme types perceived by ... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 5.1.2 Service selection and event change | The end-user may see a change in appearance either when she/he changes channel or when a service changes through time. ETSI ETSI TS 102 796 V1.5.1 (2018-09) 33 TV Service 1 TV Service 2 Radio Service Figure 4: What might be seen across channels and through time |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 5.2 User input | The user controls interactive applications using a user input device typically supplied with the terminal. This may be a conventional remote control or an alternative input device such as a game controller, touch screen, wand or drastically reduced remote control. NOTE: While the alternative input devices do not have b... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 5.3 Access to interactive applications | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 5.3.1 Overview of ways of access | The end user can access interactive applications via the following ways: • Accessing a typical broadcast-related autostart application by pressing the visually indicated "Red Button" (see clause 5.3.3.2). • Starting a digital teletext application by pressing the TEXT button (see clause 5.3.4). • Starting a broadcast-in... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 5.3.2 Inaccessibility of applications | If a non-autostart application (e.g. a digital teletext application) is not available via the broadcast channel but only via broadband and the terminal is not connected to a broadband network, the terminal should display a suitable error message encouraging the end user to connect the device to one. Technical error mes... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 5.3.3 Starting broadcast-related autostart applications | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 5.3.3.1 Possible states of an autostart application | Broadcast-related autostart applications are usually associated with a broadcast channel or an event (or part of an event) on that channel. In the first case, they start as soon as the channel is selected. In the second case, they start through an AIT update (usually co-incident with the start of the event). Broadcast-... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 5.3.3.2 "Red Button" applications | This type of broadcast-related autostart application indicates its availability by displaying a "Red Button" icon on the screen. This icon is displayed for a time period and then it may disappear. Pressing the "Red Button" on the RCU always displays the full user interface of the application (see Figure 5), whether the... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 5.3.4 Starting digital teletext applications | A digital teletext application is a special broadcast-related application which is started by pressing the TEXT button on the RCU. Depending on the provision of a digital teletext application and of standard teletext the reaction on pressing the TEXT button differs. Case A: If only the standard teletext is available on... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 5.3.5 Starting broadcast-independent applications | Broadcast-independent applications are started via a running application or an Internet TV Portal. An Internet TV Portal is an application which provides a type of start page where broadcast-independent applications are sorted and offered in an appropriate and useful way to the end user. The Internet TV Portal may be o... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 5.4 Exiting and hiding broadcast-related applications | According to the technical definitions of the application lifecycle in clause 6, applications may be stopped when they launch other applications or a channel change is performed. Applications may also kill themselves, either as a result of a request by the end-user or as a consequence of some internal logic. Pressing t... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 5.5 Companion Screens | HbbTV® applications may launch, or be launched by Companion Screen applications. Once launched, they may communicate using application specific messages either directly (application to application communication - see clause 14.5) or indirectly (e.g. through the cloud). There may be a multiplicity of Companion Screen ap... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 5.6 User interface issues | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 5.6.1 Advertising broadcast applications | The user interface displayed on channel change (and when the "Info" button is pressed) is the responsibility of the terminal manufacturer but typically includes the title and synopsis of the current event. It is recommended that the presence of HbbTV® applications signalled in the broadcast is indicated to the user in ... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 5.6.2 Co-existence with CI and CI Plus MMI | A CICAM may request the terminal to display an MMI screen or dialogue at any time. The terminal has to respect the mandatory requirements of the CI and CI Plus specifications (see clauses 12.3.3 and 12.6.1.1 of CI Plus [12]) and clause 12.4 of the DVB CI Plus Extensions ETSI TS 103 205 [37]. Working within those constr... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 5.6.3 Encrypted channels | Terminals may wish to display a message to the user that the channel is encrypted and cannot be displayed (see clause 6.2.2.8). If they do so, they should be aware that applications may wish to present some relevant information for this scenario. Hence any native UI should not remain on screen permanently or should giv... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 6 Service and application model | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 6.1 Application model | The present document defines a model which supports one HbbTV® application visible at one time. Two types of applications are supported: • Broadcast-related applications. These are signalled as part of a broadcast channel as defined in clause 7.2.3.1 and follow the lifecycle rules defined in clauses 6.2.2.2 and 6.2.2.3... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 6.2 Application lifecycle | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 6.2.1 Introduction | The application lifecycle is determined by the following four factors: 1) The application model. 2) The currently selected broadcast service (if any) and changes to it. 3) The applications signalled as part of the currently selected broadcast service. 4) The signalled application control code (as defined in clause 7.2.... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 6.2.2 Starting and stopping applications | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 6.2.2.1 Summary (Informative) | Starting an application may be initiated in the following ways: • Directly by the end-user (e.g. by using dedicated buttons on the remote control or an equivalent menu provided by the terminal). • In response to signalling in a broadcast service (e.g. automatically starting a broadcast-related autostart application). •... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 6.2.2.2 Behaviour when selecting a broadcast service | Figure 13 shows the rules that shall apply when the selected broadcast service changes. Figure 13: Behaviour when selecting a broadcast service ETSI ETSI TS 102 796 V1.5.1 (2018-09) 42 NOTE 1: It is strongly recommended that broadcasters only signal one autostart application per broadcast service. NOTE 2: The selection... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 6.2.2.3 Behaviour while a broadcast service is selected | Figure 14 shows the rules that shall apply if the AIT changes or a broadcast-related application exits while a broadcast service is selected. Figure 14: Behaviour while a broadcast service is selected ETSI ETSI TS 102 796 V1.5.1 (2018-09) 44 No application shall be launched by the terminal if it would be blocked by par... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 6.2.2.4 Time-shifting behaviour | If the terminal initiates time-shifting of the currently selected broadcast service, an application may get out of sync with the presentation of the audio-video components of this service. An HbbTV® application shall be terminated if it is not safe to run it on a time-shifted broadcast service. An application is safe t... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 6.2.2.5 Simultaneous broadcast/broadband/CI Plus application signalling | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 6.2.2.5.1 Priority | Broadcast, broadband and CI Plus transport protocols may be specified simultaneously for a given application. The priority by which the transport protocols shall be used is determined by the order in which the transport_protocol_labels are listed in the application_descriptor, with the first being the highest priority. |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 6.2.2.5.2 Not currently operational broadband connection | Where a terminal does not have a currently operational broadband connection and an application to be launched is signalled to be: • Available through broadband and one or more other protocols (either broadcast or CI Plus): the terminal shall disregard the signalling for the broadband transport protocol. ETSI ETSI TS 10... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 6.2.2.5.3 Currently operational broadband connection and error accessing initial page | Where a terminal has a currently operational broadband connection but there is an error (asynchronous due to the nature of the HTTP protocol) accessing the initial page of a broadband application and an application to be launched is signalled as: • Available through broadband as top priority and then through another pr... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 6.2.2.5.4 Not currently operational CI Plus protocol | Where a terminal does not have a currently operational CI Plus File System and an application to be launched is signalled to be: • Available through CI Plus protocol and one or more other protocols (either broadcast or broadband): the terminal shall disregard the signalling for the CI Plus transport protocol. • Availab... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 6.2.2.5.5 Currently operational CI Plus connection and error accessing file system | Where a terminal has a currently operational CI Plus File System with HbbTV® Application Domain but there is an error accessing the initial page of a CI Plus application and an application to be launched is signalled as: • Available through CI Plus protocol and one or more other protocols (either broadcast or broadband... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 6.2.2.5.6 Application launch failure | If the application cannot ultimately be loaded from either broadcast or broadband or CI Plus and the application was launched by a call to createApplication(), an ApplicationLoadError shall be dispatched. Once the initial page of an application has been successfully loaded, the present document does not specify how ter... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 6.2.2.6 Broadcast-independent applications | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 6.2.2.6.1 Lifecycle issues | A broadcast-independent application can be created in one of the following ways: • By calling the Application.createApplication() method with either an HTTP or an HTTPS URL. The URL shall refer to either an HTML page or an XML AIT (see clause 7.2.3.2). • Optionally from a terminal specific application like an Internet ... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 6.2.2.6.2 Launch context signalling (informative) | As defined in clause 6.2.2.6.1, broadcast-independent applications may be launched from terminal-specific applications. These could include Internet TV portals, programme guides, related content panels, search results, channel banners, voice activation, etc. ETSI ETSI TS 102 796 V1.5.1 (2018-09) 48 Where many launch ro... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 6.2.2.7 Access to broadcast resources while presenting broadband-delivered A/V | Terminals shall be able to present broadband delivered video at the same time as demultiplexing MPEG-2 sections from the broadcast. In particular, the following examples shall apply: • AIT monitoring shall continue. • Files in a carousel shall be accessible including updates. • DSM-CC stream event monitoring shall cont... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 6.2.2.8 Behaviour on encrypted broadcast services | Some channels may have the broadcast content encrypted, preventing those terminals without the appropriate CAS and rights from decoding and presenting the content. In these cases, clauses 6.2.2.2 and 6.2.2.3 remain applicable even when the terminal fails to decode some or all of the components. In particular, terminals... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 6.2.2.9 Applications launched from non-HbbTV® application environments | Terminals may support broadcast application types other than HbbTV® applications and may provide a mechanism for an HbbTV® application to be launched from those application types. The following clauses apply where an HbbTV® application is launched using an XML AIT from an application that is signalled in a broadcast se... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 6.2.2.10 Parental ratings | When an attempt is made to launch an application using any of the mechanisms defined in clause 6.2.2, the terminal shall enforce parental access control on the application being launched using any parental rating information carried in the AIT. The decision making process and any UI should be the same as that which the... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 6.2.2.11 Other general behaviour | Any application shall be stopped under the following circumstances: • The application itself exits using the Application.destroyApplication() method (as defined in clause 7.2.2 of the OIPF DAE specification [1]). • In response to changes in the application signalling as defined in clauses 6.2.2.2 and 6.2.2.3 for broadc... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 6.2.3 Application lifecycle example (informative) | Figure 15 and Table 3 illustrate the application model defined above. Figure 15: Application model examples ETSI ETSI TS 102 796 V1.5.1 (2018-09) 52 Table 3: Descriptions of actions and resulting state changes Starting state Action Resulting state Initial State: Application 1 is running 2: User presses "TEXT" key State... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 6.3 Application boundary | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 6.3.1 Introduction | Every application is associated with an application boundary. The application boundary is based on origins of the application resources like HTML documents. |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 6.3.2 Origin | • For resources loaded via HTTP and HTTPS, the origin shall be as defined in clause 5.3 of the HTML5 Recommendation [54]. An HbbTV application shall not be considered a "privacy-sensitive" context for the purposes of clause 7.3 of IETF RFC 6454 [25] and an Origin header shall be included in HTTP requests made on behalf... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 6.3.3 Application boundary definition | The application boundary is defined as follows: • An application boundary is a set of origins where each origin is as defined above. • If the origin of a URL is the same as one of the origins in the application boundary, that URL is said to be inside the application boundary. • For applications loaded via DSM-CC, the d... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7 Formats and protocols | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.1 General formats and protocols | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.1.1 Graphic formats | The graphics formats used shall comply with clause 9.1 of the OIPF media formats specification [2]. Table 4 lists the graphics formats that shall be supported. Table 4: Graphics formats Image Format MIME Type JPEG image/jpeg GIF image/gif PNG image/png |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.1.2 Audio description | For the broadcast connection, signalling of audio description is defined by the appropriate specifications for each market where the terminals are to be deployed. Signalling of audio description for MPEG-2 transport streams delivered by the broadband connection shall follow the specification for the broadcast connectio... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.2 Broadcast-specific format and protocols |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.