hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
238e580d718f360a78b094505f1c62e3 | 102 728 | 7.1.1.1 Image encoding restrictions | Any indications in the transmitted image with respect to pixel scaling, colour space or gamma are to be ignored in the presenting of the image. One image pixel shall be mapped to one graphics pixel in the current graphics configuration, unless otherwise scaled by the application directly. See also clause 7.5, "Colour r... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 7.1.1.2 JPEG | JPEG as defined in ISO/IEC 10918-1 [33] using the JFIF [41] file exchange format. Only coding using sequential DCT-based mode or progressive DCT-based mode is required to be supported by implementations. Specifically, lossless and hierarchical modes and arithmetic coding of DCT coefficients need not be supported. The t... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 7.1.1.3 PNG | PNG is defined as in PNG Version 1.0 [42] with the following notes and modifications: • Later versions of PNG introduce additional chunk types, which are not required to be supported. • See also clause 15.1, "PNG - restrictions". • GEM terminal specifications may allow or require processing of colour space or gamma inf... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 7.1.1.4 GIF | GIF is defined as in GIF 89a [32]. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 7.1.2 MPEG-2 I-Frames | MPEG-2 I-Frames are defined as in ISO/IEC 13818-2 [36]. The payload of a file delivering an MPEG-2 I frame shall: • Be a valid video_sequence() including a sequence_extension(). • Contain one I frame only, i.e. one picture_header(), one picture_coding_extension(), and one picture_data() encoded as an intra coded frame,... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 7.1.3 MPEG-2 Video "drips" | The drip feed mode consists of letting an application progressively feed the MPEG-2 video decoder with chunks of an MPEG-2 video stream. In this mode, it is only required for the decoder to handle I and P frames (i.e. not B frame). Each chunk shall contain one frame and a certain number of syntactic elements (as descri... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 7.1.4 Monomedia format for audio clips | The format for audio clips is MPEG-1 Audio (Layer 1 and 2) ES data as defined as in ISO/IEC 11172-3 [34] and constrained in TS 101 154 [2]. Each "file" of audio content is a binary data file carrying Audio elementary stream data. Each "file" delivers an integer number of audio access units and the first byte of each fi... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 7.1.5 Monomedia format for text | Java modified UTF-8 as defined in the specification of the method java.io.DataOutput.writeUTF. NOTE: Based on ISO/IEC 10646-1 [15] but modified with respect to the encoding of the character code zero. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 7.1.5.1 Built-in character set | See Annex E, "Character set". ETSI ETSI TS 102 728 V1.2.1 (2011-09) 71 |
238e580d718f360a78b094505f1c62e3 | 102 728 | 7.2 Media streaming formats | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 7.2.1 Audio | At least one format for streaming audio shall be specified in a GEM terminal specification. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 7.2.2 Video | At least one format for delivering standard definition streaming video shall be specified in a GEM terminal specification. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 7.2.3 Subtitles | Support for DVB subtitles, teletext subtitles or any other form of subtitles is optional in the present document. NOTE: OCAP [5] does not include support for subtitles. It does include US closed-captioning which is somewhat similar, but has different regulatory requirements and usage models. The content formats support... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 7.2.3.1 DVB Subtitles | DVB Subtitles are defined as in EN 300 743 [i.7]. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 7.2.3.2 Teletext | Transmission of the text is as defined in EN 300 472 [i.6]. The data format is as defined in ETS 300 706 [55] but restricted to presentation level 1,5 or lower. Signalling of the Teletext subtitle page will be via the Teletext descriptor as defined in EN 300 468 [14]. Within the GEM specification Teletext is only suppo... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 7.2.4 Containers | A Container is what in MPEG is called the "system layer", i.e. a means for multiplexing and synchronizing multiple media streams with associated system information (metadata). Examples of widely used containers are MPEG-2 TS on the broadcast side and MP4 on the internet for streaming purposes. At least one container fo... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 7.3 Resident fonts | The inclusion of resident fonts is not required for GEM terminal specifications for packaged media targets. This clause shall apply to GEM terminal specifications that include the functional equivalent named "Resident Fonts" as specified in clause 15.6, "Functional equivalents". For GEM terminal specifications that do ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 7.4 Downloadable fonts | A GEM terminal specification may define a way to check the name, style and size parameters of a FontFactory.createFont() call on validity with respect to the data present in the font file from which the font should be created. A GEM terminal specification may require this check for a FontFactory constructed for a singl... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 7.4.1 PFR | Use of the PFR downloadable font format as defined here is not required for GEM terminal specifications for packaged media targets. This clause shall apply to GEM terminal specifications that include the functional equivalent named "Downloadable Fonts" as specified in clause 15.6, "Functional equivalents". GEM terminal... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 7.4.2 OpenType | OpenType is standardized in ISO/IEC 14496-18 [74] as the font format for MPEG-4, and is a full-featured font format that supports advanced typographic features, multi-lingual text processing and international character sets. ISO/IEC 14496-18 [74] defines different MPEG text profiles and levels of functionality. GEM rec... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 7.5 Colour representation | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 7.5.1 Background (informative) | The method of colour encoding is critical to how consistently the colours in an image can be reproduced across different systems. The description must be cast in a way which is independent of the mechanisms by which it will finally be reproduced for the viewer. The International Colour Consortium (ICC) has proposed a t... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 7.5.2 Specification | All images transmitted shall be within the gamut encompassed by the sRGB colourspace. Where possible this should be coded so that the terminal does not have to translate. Where this is impractical the sRGB image may be transcoded into a different colourspace provided the gamut assumption is not violated (i.e. to be con... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 7.5.2.1 The sRGB Reference Viewing Environment | The reference display conditions and viewing environment for sRGB are partly described in table 4. A reference viewing environment must be provided to allow for the unambiguous definition of colour, the sRGB reference viewing environment corresponds to conditions typical of indoor viewing of CRTs - further details can ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 7.5.2.2 Colourimetric Definitions and Encodings | sRGB tristimulus values can be computed as follows, firstly linear sRGB tristimulus are computed as linear combinations of the 1931 CIE XYZ (CIE 15 [23]) values using the following relationship. In the encoding process, negative sRGB tristimulus values, and sRGB tristimulus values greater than 1,00 are not retained. Th... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 7.6 MIME types | Table 7: File type identification MIME type Extension (note) Definition of content "image/jpeg" ".jpg" As defined in clause 7.1.1.2, "JPEG". "image/png" ".png" As defined in clause 7.1.1.3, "PNG" possibly with a constrained profile as defined in clause 15.1, "PNG - restrictions". "image/gif" ".gif" As defined in clause... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 7.6.1 Rationale | The MIME types are defined to reserve a name space for the possible future support of downloadable JMF players. The file name extensions shall be included in broadcasts to assist receivers identify the type of the content. For DVB-J applications, this is described in table 30, "Return types of URL.getContent()". Not al... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 8 Void | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9 Application model | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.1 Service-bound GEM applications | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.1.1 Basic lifecycle control | The basic control of the lifecycle of service-bound GEM applications is through the selection of services. Selection of a service can be initiated by the user of the GEM terminal using the navigator as well as by GEM applications offering service selection functionality. For broadcast and IPTV applications, service sel... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.1.2 Starting applications | When a service is selected, applications which are listed in the Application Description of the service and identified as auto-start shall be launched as described in clause 10.4.3.1 without explicit intervention of the user. Applications which are started after the selection of a service will be controlled by signalli... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.1.3 Support for execution of multiple simultaneous applications | The set of applications that are signalled within a service can be presented and executed concurrently. GEM terminals shall be able to support applications from that set (using the same screen) at least as defined in Annex G, "Minimum platform capabilities". GEM terminals are required to support execution of the set of... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.1.4 Stopping applications | GEM applications may stop themselves voluntarily using the GEM APIs or may be stopped by the GEM terminal in a number of situations. Examples of situations where this shall be allowed include: |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.1.4.1 A new service being selected replacing a previously selected one | When a new service is selected and replaces a previously selected one, applications from the former service shall only continue to execute where they are signalled in the new service. If an application is not signalled in that signalling then it will be stopped by the GEM terminal. Where an application is known to be b... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.1.4.2 The stopping of an application by another application | Subject to the security policy of a GEM terminal, one application may request to stop another application. In such a case, the resident Application Manager, after a successful security check, kills the application; otherwise that application shall continue running, without interruption. 9.1.4.3 Changes in the applicati... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.1.4.4 Stopping by the GEM terminal due to a shortage of resources | Where a GEM terminal has insufficient resources (e.g. memory, CPU and resources managed by the resource management API) to continue the execution of one of the running applications, the GEM terminal is allowed to decide to stop a GEM application without user intervention. NOTE: The precise resources of a GEM terminal a... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.1.5 Persistence of Applications Across Service Boundaries | Where a running application is signalled in both the new service and the former service, and is not signalled as service bound in the former service, it shall continue to run and shall not be restarted. In this case, the running application shall become controlled by the application signalling of the new service where ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.1.6 Management of autostarting | The receiver shall launch autostart applications under the following conditions: • The signalling indicates that the application can be supported by the receiver, as defined by the application profile and versioning information contained in the Application Description. • Only a single application with a given Applicati... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.1.7 Tuning without service selection | GEM applications may cause tuning to another transport stream by mechanisms other than service selection. Usage of these mechanisms does not constitute service selection and therefore no applications from the target transport stream or service shall be started either by the GEM terminal or by GEM applications. The GEM ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.1.8 GEM Applications and Service Selection | GEM applications may select services using the service selection API. The service selection API includes a class ServiceContext to represent environments in which services may be presented. Calling the select() method on a ServiceContext causes a new service to be presented in that context and any former service being ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.1.9 Cached applications | When an application is signalled in the Application Description of a service in the usual way, and that Application Description entry also contains an application_storage_descriptor, the terminal may use files that have been stored on the terminal to accelerate the loading of that application. These files may have been... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.1.9.1 Version management | If the application has not_launchable_from_broadcast set to '0' then the service-bound version shall be used regardless of the value of is_launchable_with_older_version. If the application has not_launchable_from_broadcast set to '1' and: • is_launchable_with_older_version is set to '0', it shall not be launched at all... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.1.9.2 Proactive caching | If a storable application is signalled, terminals are allowed to proactively store any files that are indicated in the ADF. Terminals do not have to honour the requested priority when proactively caching files. In particular, note that proactive caching is not required to store all files with critical priority (but in ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.2 DVB-J Model | GEM terminal specifications based on the packaged media profile or the IPTV profile may not support the dynamic update of a service's Application Description. In such a case, corresponding language in clause 9 and its subclauses does not apply. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.2.1 Starting DVB-J Applications | DVB-J applications may be started by any of the means defined for general GEM applications. The application listing and launching API defined in Annex S, "Application listing and launching" allows one GEM application to start another GEM application subject to security policy. The start() method of the AppProxy interfa... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.2.2 Stopping a DVB-J Application | DVB-J applications may stop for any of the reasons listed for general GEM applications. An application shall be able to notify that it is stopped by finishing its execution and informing the Application Manager through the notifyDestroyed() method on the javax.tv.xlet.XletContext interface. This interface also includes... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.2.3 DVB-J Application Lifecycle | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.2.3.1 Introduction | This clause describes the Xlet lifecycle model for the DVB-J API. This describes the capabilities of the Xlet in each state and the methods by which the application manager influences the life cycle state. This clause is not directly related to other aspects of a system, such as graphics or shared resource allocation/m... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.2.3.2 Lifecycle state machine for DVB-J application instances | The Xlet state machine ensures that the behaviour of an Xlet is close to the behaviour that television viewers expect, specifically: • The perceived start-up latency of an Xlet can be very short. • It is possible to put an Xlet into a state where it is not providing its service. • It is possible to destroy an Xlet at a... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.2.4 Xlet API | The Xlet API provides GEM application developers with an API that provides life cycle signalling. The Xlet API uses the callback approach to signal state changes. This API is specified in clause 11.7.1, "APIs to support DVB-J application lifecycle". |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.2.4.1 Xlet State Change Semantics | An Xlet's state can change either by having one of the methods on its Xlet Interface called, or by making an internal state transition and notifying the application manager via the XletContext Object. The semantics of when that state change actually happens are important: • Calls to Xlet: this interface indicates a suc... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.2.4.2 Xlet state change requests | Table 9 defines the previous states in which calls to the methods on XletContext relating to state management are valid; NOTE: These methods are called after the Xlet has changed its state. ETSI ETSI TS 102 728 V1.2.1 (2011-09) 87 Table 9: States for valid state management calls Call State notifyDestroyed all states no... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.2.5 Multiple application environment support | The DVB-J platform allows for the simultaneous execution of several DVB-J applications. Allowing several DVB-J applications to run simultaneously implies that some rules be defined for these DVB-J applications to share the resources of the MHP, and in particular for them to share the Input Focus and the Output Focus. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.2.5.1 Control of DVB-J applications by other DVB-J applications | The present document provides support for control of the lifetime of a DVB-J application by another DVB-J application. This feature enables service providers to write their own "Launcher applications" that take care of the presentation to the user of the availability of DVB-J applications, and that enables eventually t... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.2.5.2 Input Focus management | The input focus is defined as follows: • The application that has input focus is in principle able to receive user-input events. • Other applications not having the input focus can request to receive a subset of user-input events via a dedicated API. See clause 11.3.2.2, "org.dvb.event". A DVB-J application has input f... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.2.5.3 Other resources management | The APIs defined in the present document provide support for resource allocation/revocation and resource revocation notification. The semantics of the APIs, however does not define under which circumstances an access to a resource is granted or revoked. While it is well understood that in most cases, it is up to the GE... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.2.5.4 VM implementation | Where there are multiple DVB-J applications being executed as part of the same service, GEM terminals are allowed implement these in a single actual virtual machine instance. Regardless this shall conform to clause 11.2.1, "Basic Considerations". |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.3 Void | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.4 Inter-application resource management | Some downloaded resident applications specified as extensions to the present document may perform some of the functions of the navigator, e.g. the monitor application defined OCAP [5]. In this case, such downloaded software shall implement a policy that is consistent with the requirements of the present document. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.4.1 Application instances running in the same service context | Where there is a resource conflict between two applications signalled as part of the same service and running in the same service context, this shall be resolved using the priority signalled in the application_priority field in the Application Description for each application. When comparing two applications, the one w... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.4.2 Application instances not running in the same service context | The present document intentionally does not specify resource management policy or algorithms other than as above. The service level resource priority (as set by the setPriority() method on UnboundApplicationService or DvbServiceContext.setPriority()) is one input to the resource management algorithm. Another input may ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.5 Void | 9.6 Services and applications not related to conventional services Clause 9.1, "Service-bound GEM applications" describes applications whose lifecycle is controlled through services. The present document additionally supports applications whose lifecycle is not bound to that of services. These include: • Applications s... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.6.1 Applications loaded from the interaction channel | In this scenario the application signalling comes from the interaction channel rather than the broadcast channel. In overview: • Data equivalent to the service-bound Application Description is provided from the interaction channel in the AIT File. The connection to the server that provides the data is analogous to a co... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.6.2 Stored services | Stored services are an encapsulation of one or more applications. The lifecycle of a stored service shall obey the same rules as defined for a service in clause 9.1, "Service-bound GEM applications". So, for example, currently running applications will be stopped if they are not listed to be runable in the stored servi... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.6.3 DVB-J Model | This clause is applicable only if clause 9.6.1 or 9.6.2 is required by the GEM terminal specification. For DVB-J applications, APIs required to include some support for these applications include the following. • Service selection API (see clause 11.6.2). • "Content referencing" (see clause 11.7.6) as described in clau... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.6.4 Common behaviour | This clause is applicable only if clause 9.6.1 or 9.6.2 is required by the GEM terminal specification. The environment in which stand-alone GEM applications are presented or executed shall be the same as for applications related to a conventional service except as detailed below. • Any existing video and audio running ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.7 Lifecycle of internet access applications | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.7.1 General issues | GEM terminals supporting internet access applications shall support at least the execution of one internet access application at one time. There is no requirement to support the execution of more than one internet access application at one time. There is no requirement to support the execution of internet access applic... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.7.2 Starting internet access applications from GEM applications | Where GEM terminals support simultaneous execution of internet access applications and GEM applications at the same time, then the internet access application shall start when requested. The internet access application shall be considered to be a peer of the GEM application and not a child of it. The lifecycle of the i... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.7.3 Selecting DVB services from internet access applications | In GEM, internet access applications shall support end user starting of DVB services (i.e. using the 'dvb:' URL) and GEM applications signalled over the interaction channel (i.e. using an application description file referenced by an HTTP URL). This shall be handled by the normal service selection mechanism used elsewh... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.8 Plug-ins | Attention is drawn to the general rules in clause 4.2. Clause 5.4, "Plug-ins" of the present document defines the concept of plug-ins for use in migration situations, for the support of applications in existing content formats. Services and networks using such an approach to migration have a number of choices defined b... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.9 Stored and cached applications | This clause describes the common storage behaviour that applies to all stored applications. See clause 9.1.9, "Cached applications" and clause 9.6.2, "Stored services". |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.9.1 Storing files | When a file that forms part of an application is stored, the following metadata shall be stored with the file: • The application type. • The Application identification. • The version information from the Application storage descriptor (see clause 10.8.2, "Application storage descriptor"). • If the Application descripti... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.9.2 Version management | To be eligible for any kind of application storage, an application must be signalled with an application_storage_descriptor. This contains the version number for the application. A stored application is uniquely identified by an organisation_id, application_id, version number triple. Terminals shall support storing mul... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.9.3 Removing stored applications | If an application is running (i.e. in any state other than DESTROYED or NOT_LOADED), the terminal shall not remove it from storage or cache. The API methods to remove an application from storage or cache shall work normally and shall not fail just because the application is running. When the application terminates, onl... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.9.4 Interrupted downloads | Storing or caching an application may be interrupted, e.g. if the application that requested the storing or caching terminates or is terminated. (For example, if the user zaps to a service whilst a download is in progress.) If storing or caching an application is interrupted before all critical files are downloaded, te... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.9.5 Dynamic behaviour | If an application that was not previously stored becomes stored, the following shall apply: • An AppsDatabaseEvent with event id APP_ADDED shall be sent for that application. • If the application was signalled in the current service as both AUTOSTART and not_launchable_from_broadcast, it shall be started. ETSI ETSI TS ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.11 Providers | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.11.1 Introduction (informative) | Providers is a term used in Java SE for extensions to platform facilities exposed via standardised APIs. These are often adaptors between implementations of standard APIs and market specific protocols. They use standard APIs and are independent of any particular implementation and hence can be deployed by operators dir... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.11.2 Lifecycle of xlet bound providers | When an instance of an application with one or more provider usage descriptors in its Application Description starts, the implementation shall attempt to find a provider for each signalled provider name by matching the provider names. For each matching provider, the following shall be done: • The classes of the applica... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.11.3 Lifecycle of system bound providers | These are registered by the application containing the provider. The Xlet which registered the provider may unregister it. Otherwise the provider will be unregistered when the Xlet which contains it terminates. NOTE: Xlets containing system bound providers would typically be unbound applications without any user interf... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.12 Impact of graphics constraints on the application model | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.12.1 Impact on generic applications | The graphics constraints descriptor (clause 10.4.3.3, "Graphics constraints descriptor") shall be used in the following ways: a) Selecting the default graphics configuration for an application when an instance of that application starts or deciding not to start the application. b) Defining whether an application can co... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.12.2 Impact on DVB-J applications | The default graphics configuration of the application shall be used for the HScene returned by the implementation of the following methods: • org.havi.ui.HSceneFactory.getDefaultHScene() • org.havi.ui.HSceneFactory.getDefaultHScene(HScreen) • javax.tv.graphics.TVContainer.getRootContainer() • javax.microedition.xlet.Xl... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.13 Unbound Applications | This clause is optional in all profiles of GEM. GEM terminal specifications may include all or part of the specification elements of this clause, or may include none at all. If specification elements are included, functional equivalents may be specified where necessary. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.13.1 Introduction to unbound applications (informative) | 9. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.1 Introduction | to unbound applications (informative) |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.13.1.1 Scope | Unbound applications are ones whose lifecycle is not bound to the presentation of a particular piece of content, either a service or content provided on demand. This is in contrast to broadcast GEM applications (see clause 9.1, "Service-bound GEM applications") which are bound to one or more TV channels by signalling a... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.13.1.2 Divergences from OCAP Solution | The GEM design is based as closely as possible on OCAP [5] however some technical changes were found to be necessary to address different market requirements. These are as follows: • Service bound applications are more important in GEM than in OCAP. One specific concern with unbound applications is their impact on the ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.13.1.3 Overview | The present document defines a single environment within which there are multiple service contexts. These may include: • Service contexts presenting broadcast services. • Service contexts presenting stored application services. • Service contexts presenting return channel signalled services. • Service contexts presenti... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.13.2 Service model | Clause 10.2.2.2 of OCAP [5] "OCAP Service Model" may be supported. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.13.3 Application lifecycle | Clause 10.2.2.3 OCAP [5] "Application Signalling and Lifecycle" may be supported. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 9.13.4 Initialization of GEM Environment | When the GEM environment is initialized, (either from scratch or after a re-start) the following steps shall apply: • The XAIT shall be loaded and parsed including updating the service list and the applications database. • The most recent initial monitor application (if any) shall be identified (either signalled in the... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 10 Application signalling | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 10.1 Introduction | This clause covers the following topics: • Identification and launching of applications associated with a service. • Requirements on the signalling that enables a broadcast to manage the lifecycle of applications. MHP [1] contains a model of signalling that fulfils the requirements of GEM, but other signalling is possi... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 10.1.1 Summary of requirements on common signalling | The minimum signalling requirements for any GEM application are summarized as follows: • Some form of Application Description (see clause 10.4) with information sufficient to: - identify the source of the application code and other assets; - identify the application's application ID and organisation ID; - identify the ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 10.1.2 Summary of additional signalling for DVB-J applications | The minimum additional signalling requirements for DVB-J applications are summarized as follows: • A DVB-J Specific Application Description (see clause 10.5) with information sufficient to: - signal parameters to the application; - indicate the initial class of the application. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 10.2 Program specific information | A service carrying GEM applications shall contain information sufficient to locate the following: • the Application Description (see clause 10.4) for each application in the service; • the source of the application code and data. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 10.3 Locators within an Application Description | Some fields of the Application Description contain locators, e.g. locators to a directory containing certain kinds of files. These locators can be to any transport defined within a GEM terminal specification, e.g. they can be locators to an object carousel, part of a data carousel, an http URL, etc. GEM does not mandat... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.