hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.1.4 Application boundary | The application boundary defines the extent of a DVB-HTML Application. Any content documents outside of the application boundary are considered to not be part of the DVB-HTML Application and shall be unavailable to the referencing DVB-HTML application. An MHP terminal may contain an implementation specific mechanism to... |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.1.4.1 Regular Expression Syntax | A regular expression (RE) specifies a set of character strings to match against. A member of this set of strings is said to be matched by the regular expression. In order for a locator to match a boundary regular expression the whole locator must be matched by the whole regular expression; any parameters (characters in... |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.2 DVB-HTML Application Lifecycle | |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.2.1 Introduction | There are three key parts of the DVB-HTML application lifecycle model: a) How applications are signalled as available to the MHP, and for auto start and prefetch applications how the start time is synchronized with any associated media stream. b) How and when the application manager or other launcher application makes ... |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.2.2 Signalling | The DVB-HTML Application is signalled as described in clause 10, "Application Signalling". The application manager can be requested to start a DVB-HTML application either because it is signalled as auto start, or through the application launching API. On receiving the request that a DVB-HTML application is to be starte... |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.2.3 Lifecycle control | The state model for the DVB-HTML application lifecycle control model described in this clause reflects the signalling (see clause 10.6, "Control of application life cycle") and is an abstract view of how a DVB-HTML application operates, and considers the kinds of resources that a user agent would need in order to funct... |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.2.3.1 State diagram | The following transition diagram summarizes the states and the transitions between them. Figure 10: DVB-HTML application life cycle state diagram |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.3 The State Model | The entry state of the state machine, Loading, is characterized by access to the content resources and signalling resources but does not have or require input and output resources. This implies the actor can prefetch content and receive triggering events for transition to the Active state, but will not be presented to ... |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.3.1 Loading | |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.3.1.1 Name | Loading. |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.3.1.2 Entry actions | Instantiation of an actor. |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.3.1.3 Activities | Waiting for documents to be available and loading documents without rendering them. |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.3.1.4 Resources | Content, signalling, Output. |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.3.1.5 Transitions | Active. preconditions: • Enough data is available to present something sensible. Killed. preconditions: • If the DVB-HTML application is signalled as KILL. Destroyed. preconditions: • If the DVB-HTML application is signalled as DESTROY. |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.3.1.6 Comment | This is the entry state of the state machine This state is entered only once in the lifetime of the DVB-HTML actor. Any start-up phase of a user agent can also be considered as part of this state. When an actor is in this state it is not rendering anything. This state should not be confused with any prefetching of modu... |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.3.2 Active | |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.3.2.1 Name | Active. |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.3.2.2 Activities | Gathering and parsing current document and related resources, rendering document, Maintaining rendered documents. receptive to events, waiting for triggering event to show loaded documents. ETSI ETSI TS 102 727 V1.1.1 (2010-01) 145 |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.3.2.3 Entry actions | If application is signalled as pre-fetch wait for trigger before displaying anything. |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.3.2.4 Resources | Content, signalling, output, input. |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.3.2.5 Transitions | Pause. • If the user agent or application manager puts the DVB-HTML application in PAUSE. Destroyed. • If the DVB-HTML application is signalled as DESTROY. Killed. • If the DVB-HTML application is signalled as KILL. |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.3.2.6 Comment | This state is the steady state, In this state it is user agent specific as to whether a partially loaded document is displayed, or deals with input triggers. If a transition is made to a new document within the application, the actor remains in this state. If a related resource document of the main document changes, th... |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.3.3 Paused | |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.3.3.1 Name | Paused. |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.3.3.2 Activities | DVB-HTML actor should minimize its use of resources. |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.3.3.3 Resources | Application specific. |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.3.3.4 Transitions | Active. • If the DVB-HTML application is resumed. Destroyed. • If the DVB-HTML application is signalled as DESTROY. ETSI ETSI TS 102 727 V1.1.1 (2010-01) 146 Killed. • If the DVB-HTML application is signalled as KILL. |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.3.3.5 Comment | The semantics of this state are both user agent and DVB-HTML application specific. When the DVB-HTML application returns from the "Pause" state, the environment might have changed (loss of resources or network connections) and some events may not have been reported. |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.3.4 Destroyed | |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.3.4.1 Name | Destroyed. |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.3.4.2 Activities | Loading documents. Rendering documents. Consuming events. Interact with the user. |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.3.4.3 Resources | Input and output. |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.3.4.4 Transitions: | Killed. • {If the DVB-HTML application is signalled as KILL} OR {local event forces the actor to terminate, possibly through application manager}. |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.3.4.5 Comment | This state indicates the MHP may no longer be able to access the content resources required to run the DVB-HTML application. It is DVB-HTML application and user agent specific as to whether the actor continues to run, and if it does how the user should be informed if any link is no longer available because the content ... |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.3.5 Killed | |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.3.5.1 Name | Killed. |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.3.5.2 Entry actions | Release of resources. |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.3.5.3 Activities | Termination of the DVB-HTML application. |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.3.5.4 Resources | None. ETSI ETSI TS 102 727 V1.1.1 (2010-01) 147 |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.3.5.5 Transitions | None. |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.3.5.6 Comment | After the activities in this state are finished, the application is no longer running. This state is the exit state of the state machine. |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.4 Application activity events | Each page within an application shall receive load and unload events with the following constraints: • The DVB lifecycle AppActive event precedes the first DVB-HTML load event. • There is no guarantee on the relative ordering of the first DVB-HTML load event and the DVB lifecycle AppStarting event. • When a document is... |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.3.4.1 Event queue handling | The HTML and DOM standards say little about how events are inserted by the User Agent or how they are queued. DVB-HTML User Agents shall observe the following list of clarifications. • After the unload event is sent, no other events shall be sent to the document, so all trigger event listeners may be discarded. (For cl... |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.4 Inter-application resource management | GEM [1], clause 9.4 is included in the present document, with the following notes and modifications. The reference to the application_priority field in the application descriptor is to be interpreted as referring to the application_priority defined in clause 10.4. ETSI ETSI TS 102 727 V1.1.1 (2010-01) 149 |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.5 Life cycle of Xlets embedded in DVB-HTML | The state of an Xlet is influenced by the state of the page that contains it, in addition to being influenced by the state of the containing application. The Xlet's lifecycle is bound by the lifecycle of the HTML application and page, but the Xlet may, through its own actions, be in a less active state than the contain... |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.5.1 Starting embedded Xlets | For each Xlet specified with an object tag, a new classloader shall be created to load its classes. The standard MHP semantics surrounding Xlet classloaders apply. For example, classloaders shall not be shared with other Xlets. When an HTML page is being loaded, any Xlets embedded within that page shall be requested to... |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.5.2 Termination | When a page becomes invisible due to navigation away from that page or when the containing DVB-HTML application becomes paused, all embedded Xlets that are in the active state shall be requested to enter the paused state. It is implementation dependent when an Xlet that was paused due to navigation is transitioned from... |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.5.3 General issues | Multiple Xlets per XHTML document are allowed to the same extent as multiple Xlets are allowed in the same DVB service. Instances of embedded Xlets: • Shall not be listed in the AIT. • Shall not be exposed in the application listing an launching API when launched through a DVB HTML application. ETSI ETSI TS 102 727 V1.... |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.7 Lifecycle of internet access applications | GEM [1], clause 9.7 is included in the present document. |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.8 Plug-ins | GEM [1], clause 9.8 is included in the present document, with the following notes and modifications. In this clause, the terms "AIT" and "application descriptor" are to be interpreted as referring to the application information table defined in clause 10.4 of the present document. |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.9 Stored and cached applications | GEM [1], clause 9.9 is included in the present document. 9.10 Lifecycle interactions between MHP and resident applications GEM [1] clause 9.10 "Lifecycle interactions between GEM and resident applications" is replaced with the following: Running MHP applications shall not be killed as a direct consequence of showing th... |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.11 Providers | GEM [1], clause 9.11 is included in the present document. ETSI ETSI TS 102 727 V1.1.1 (2010-01) 151 |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.12 Impact of graphics constraints on the application model | GEM [1], clause 9.12 is included in the present document. |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.13 Unbound applications | GEM [1], clause 9.13 is included in the present document, with the following notes and modifications. |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.13.1 Introduction to unbound applications (informative) | 9. |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 13.1 Introduction | to unbound applications (informative) GEM [1], clause 9.13.1 is included in the present document. |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.13.2 Service model | GEM [1] clause 9.13.2, "Service model" is replaced by the following: Clause 10.2.2.2 of OCAP [49], "OCAP Service Model" shall be supported. |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.13.3 Application lifecycle | GEM [1] clause 9.13.3, "Application lifecycle" is replaced by the following: Clause 10.2.2.3 OCAP [49], "Application Signaling and Lifecycle" shall be supported. |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 9.13.4 Initialization of MHP Environment | GEM [1], clause 9.13.4 is included in the present document. |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10 Application Signalling | |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.1 Introduction | GEM [1], clause 10.1 and its clauses are included in the present document with the following additions and modifications. This clause covers the following topics: • How the receiver identifies the applications associated with a service and finds the locations from which to retrieve them. • The signalling that enables t... |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.1.1 Summary of requirements on common signalling | The minimum signalling requirements for any MHP applications are summarized as follows: • PMT with Application Signalling Descriptor to identify the service component carrying the Application Information Table. • Application Information Table with the following information in its common descriptor loop: - Transport pro... |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.1.2 Summary of additional signalling for DVB-J applications | The minimum additional signalling required for DVB-J applications are summarized as follows: • Application Information Table with the following information in its application information descriptor loop: - DVB-J application descriptor. - DVB-J application location descriptor. |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.1.3 Summary of additional signalling for DVB-HTML applications | The minimum additional signalling required for DVB-HTML applications are summarized as follows: • Application Information Table with the following information in its application information descriptor loop: - DVB-HTML application descriptor. - DVB-HTML application location descriptor. |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.1.4 Summary of additional signalling for applications carried via OC | In either the "common" (first) descriptor loop or the "application" (inner) descriptors loop: • Transport protocol descriptor, with the selector bytes containing the OC specific information as defined in table 78. |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.1.5 Summary of additional signalling for applications carried via IP | Application Information Table with the following information in its common descriptor loop: • IP signalling descriptor. In either the "common" (first) descriptor loop or the "application" (inner) descriptors loop: • Transport protocol descriptor, with the selector bytes containing the IP specific information as defined... |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.1.6 How to add a new scheme (informative) | The signalling scheme is intended to be extensible with regard to the application representations and transport protocols that are supported. The areas that need to be addressed when doing this are summarized below. To add further transport protocols: • Extend table 77, "Semantics of selector bytes". • Possibly define ... |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.1.7 Service information | See clause 10.12, "Service Information". |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.2 Program Specific Information | GEM [1], clause 10.2 is included in the present document with the following additions and modifications. The elementary stream (inner) loop of the PMT for a DVB service supporting one or more MHP applications must reference streams for the following: • Location of the stream transporting the Application Information Tab... |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.2.1 Application signalling stream | The elementary stream information for the PMT entry describing the elementary stream carrying the Application Information Table has the following characteristics: • The stream_type is set to 0x05 (ISO/IEC 13818-1 [15] private sections). • An Application Signalling Descriptor. There may be more than one elementary strea... |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.2.2 Data broadcast streams | The minimum signalling in the PMT associated with data broadcast components is the value of the PMT stream_type field required by the DVB data broadcasting specification (EN 301 192 [5]) for the transport protocol. The full details of the data broadcast protocol, the location of its "principal" component etc. are provi... |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.3 Notation | |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.3.1 reserved | The term "reserved" when used in the clause defining the coded bit stream, indicates that the value may be used in the future for ISO defined extensions. Unless otherwise specified within the present clause all "reserved" bits shall be set to "1". |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.3.2 reserved_future_use | The term "reserved_future_use", when used in the clause defining the coded bit stream, indicates that the value may be used in the future for ETSI defined extensions. Unless otherwise specified within the present clause all "reserved_future_use" bits shall be set to "1". |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.4 Application Information Table | The Application Information Table (AIT) provides full information on the data broadcast, the required activation state of applications carried by it etc. The AIT comprises the set of AIT sub-tables (see clause 10.4.5) within the selected service which have an application_type that the receiver can decode. Data in the A... |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.4.1 Data errors | AITs which contain errors shall be processed as follows: • An error in a descriptor shall result in that descriptor being silently discarded. Processing of that descriptor loop shall continue with the next descriptor (if any). The scope of error detection of a descriptor should be limited to the application information... |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.4.2 AIT transmission and monitoring | MHP terminals shall monitor the PMT for changes in the number of AIT elementary streams present. Changes shall be detected within 1 second. MHP terminals shall monitor all AIT elementary streams within the selected service, as described in more detail below. The minimum repetition rate for each AIT subtable is 10 secon... |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.4.3 Optimized AIT signalling | The optional AIT_version_number carried by the Application Signalling Descriptor allows a possible optimization of receiver burden as it allows receivers to acquire the AIT only after they see changes in the AIT version advertised in the PMT. See clause 10.7.1, "Application signalling descriptor". |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.4.4 Visibility of AIT | If an application tunes away from a transport stream where its signalling is carried without selecting a new service, it will continue running although the AIT is not visible. In MHP terminals with multiple network interfaces, if the AIT of the selected service is visible via any of them, then the AIT signalling is use... |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.4.5 Definition of sub-table for the AIT | All sections on the same PID with the AIT table_id and the same value of application_type are members of the same sub-table. |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.4.6 Syntax of the AIT | The Application Information Section describes applications and their associated information. Each Application Information Section includes one "common" descriptor loop at the top level for descriptors that are shared between applications of that sub-table and a loop of applications. Each application in the application ... |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.4.7 Use of private descriptors in the AIT | Private descriptors may be included in the AIT provided that they are in the scope of a DVB-SI EN 300 468 [4] private data specifier descriptor. The scope rules for the private data specifier descriptor are as follows: • If this descriptor is located within any descriptor loop of the AIT, then any specifier identified ... |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.4.8 Text encoding in AIT | Unless otherwise specified, all fields interpreted as text strings in the AIT shall be encoded as UTF8 (see clause 7.1.5, "Monomedia format for text"), but shall not include the null character. See also clause 14.5, "Text encoding of application identifiers". |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.4.9 AIT file | |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.4.9.1 Syntax | The interaction channel encoding of the AIT into the AIT file is as follows: • A single file shall contain all of the data. • The file shall contain a concatentation of Application Information Sections (specified in clause 10.4.6 of the present document). • The possibly multiple sections shall be ordered as follows: - ... |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.4.9.2 Syntactic restrictions | |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.4.9.2.1 Transport protocols | The only allowed transport protocol type has id value 0x0003. See table 76, "Protocol_id". |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.4.9.3 Semantics | The AIT file shall be loaded once during service selection. There is no requirement to monitor or poll the AIT file for any subsequent changes except as part of a subsequent service selection operation referring to the same AIT file. Consequences of this are: • Only the AUTOSTART and PRESENT application control codes (... |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.4.9.4 MIME type | The MIME type for an AIT file shall be "application/dvb.ait". The file extension shall be ".ait". |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.5 Application identification | |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.5.1 Encoding | Each application is associated with an application identifier. This is a 6 byte field with the following structure. Table 67: Application identifier syntax No. of Bits Identifier Value application_identifier { organization_id 32 bslbf application_id 16 bslbf } organization_id: An organization_id, as defined in GEM [1],... |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.5.2 Effects on life cycle | The main concepts here are: • On service change, currently running, previously broadcast, applications whose service_bound_flag is set to "0" shall (subject to resource restrictions) continue running if their application identifier is listed in the Application Information Table of the newly selected service. ETSI ETSI ... |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.5.3 Authentication of application identification | See GEM [1], clause 12.5.6, "subject". |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.6 Control of application life cycle | The broadcast signalling provides a mechanism for broadcasters to control the life cycle of standard application types. See also clause 9.1, "Broadcast MHP applications". |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.6.1 Entering and leaving the domain of an application | The domain of an application is defined as the set of services where the application is listed in the AIT. This can be either as applications listed in the application (inner) loop of the AIT or as applications listed in the External application authorization descriptor. Services where the application is not listed in ... |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.6.2 Dynamic control of the application life cycle | The dynamic control of the application life cycle is signalled through the application_control_code for the application in the AIT. This control code allows the broadcaster to signal to the receiver what to do with the application with regard to its lifecycle. The set of codes have some differences between application ... |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.6.2.1 DVB-J application control codes | GEM [1], clause 10.4.3.1 is included in the present document. ETSI ETSI TS 102 727 V1.1.1 (2010-01) 160 |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.6.2.2 DVB-HTML application control codes | The application control codes for DVB-HTML applications are listed in table 68. Table 68: DVB-HTML application control code values Code Identifier Semantics 0x00 Reserved_future_use. 0x01 AUTOSTART The Application Entry Point of the DVB-HTML application is loaded. This is loaded into the user agent, and the DVB-HTML ac... |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.7 Generic descriptors | |
7b7f70c9376325894becb0e57e5b31ab | 102 727 | 10.7.1 Application signalling descriptor | The application signalling descriptor is defined for use in the elementary stream loop of the PMT where the stream_type of the elementary stream is 0x05. It identifies that the elementary stream carries an Application Information Table. The application signalling descriptor optionally carries a loop of application_type... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.