hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.2.11.3 XML encoding | The XML encoding of the storage capabilities for an application is given by the StorageCapabilities element: <xsd:complexType name="StorageCapabilities"> <xsd:sequence minOccurs="0"> <xsd:element name="storageProperty" type="mhp:StorageType"/> <xsd:element name="isStorable" type="xsd:boolean"/> <xsd:element name="canCa... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.2.12 Application Description File | |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.2.12.1 Description | The Application Description File (ADF) provides the list of files that need to be stored for an application as well as other related necessary information. The notation uses an XML-based syntax. For those applications that can be stored, an Application Description File shall be placed in the same carousel as the applic... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.2.12.2 Application description file name and location | The location of an ADF should be defined in a platform specification. By convention, the name of an ADF is: 'dvb.storage.oooooooo.aaaa' where: oooooooo is the organisation_id of the application as a 8 character hexadecimal string aaaa is the application_id as a 4 character hexadecimal string The organisation_id and app... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.2.12.3 Syntax | The syntax of the Application Description File is defined by the following XML DTD. The PublicLiteral to be used for specifying this DTD in document type declarations of the XML files is: "-//DVB//DTD Application Description File 1.0//EN" and the URL for the SystemLiteral is: "http://www.dvb.org/mhp/dtd/applicationdesc... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.2.12.4 Semantics | Version: A decimal integer denoting the version number of this application. The value of this attribute shall not contain leading zeros (unless it is "0"). The value of this attribute shall also match the version number signalled in the version field of the application storage descriptor in the AIT entry of this applic... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3 MPEG-2 table and section syntax | |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.1 Summary | |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.1.1 Summary of common signalling | The minimum signalling requirements for any applications are summarized as follows: • PMT with application signalling descriptor to identify the service component(s) carrying the Application Information Table. • Application Information Table with the following information in its common descriptor loop: - transport_prot... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.1.2 Summary of additional signalling for applications carried via OC | In either the "common" (first) descriptor loop or the "application" (inner) descriptor loop: • transport_protocol_descriptor, with the selector bytes containing the OC specific information as defined in table 31. |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.1.3 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 30 "Semantics of selector bytes". • Possibly define f... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.2 Program specific information | |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.2.0 Introduction | The elementary stream (inner) loop of the PMT for a DVB service supporting one or more applications shall reference streams for the following: • Location of the stream(s) transporting the Application Information Table. • Location of the stream(s) transporting the application code and data. ETSI ETSI TS 102 809 V1.3.1 (... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.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 [3], private sections). • An application_signalling_descriptor (see clause 5.3.5.1). There may be more than... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.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 (ETSI EN 301 192 [2]) for the transport protocol. The full details of the data broadcast protocol, the location of its "principal" component etc. are ... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.3 Notation | |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.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". |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.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". |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.4 Application Information Table | |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.4.0 Introduction | 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 5.3.4.5) within the selected service which have an application_type that the receiver can decode. Data in the... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.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... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.4.2 AIT transmission and monitoring | Receivers shall monitor the PMT for changes in the number of AIT elementary streams present. The time within which changes shall be detected is application type dependent. Receivers shall monitor all AIT elementary streams within the selected service, as described in more detail below. The minimum repetition rate for e... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.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 5.3.5.1 "Application signalling descriptor". |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.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 receivers with multiple network interfaces, if the AIT of the selected service is visible via any of them, then the AIT signalling is used as... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.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. |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.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 ... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.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 ETSI EN 300 468 [1] 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 identi... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.4.8 Text encoding in AIT | Unless otherwise specified, all fields interpreted as text strings in the AIT shall be encoded as UTF8, but shall not include the null character. |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.4.9 Access to an MPEG-2 format AIT via a broadband connection | |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.4.9.0 Introduction | The AIT file contains the MPEG-2 encoding of an AIT in a form that may be loaded via HTTP and is used to group applications that are not associated with a broadcast service. ETSI ETSI TS 102 809 V1.3.1 (2017-06) 36 NOTE: Platform specifications which include support for the AIT file should define how this is used; for ... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.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 concatenation of Application Information Sections (specified in clause 5.3 of the present document). • The possibly multiple sections shall be ordered as follows: - Asce... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.4.9.2 Syntactic restrictions | |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.4.9.2.1 Transport protocols | The only allowed protocol_id has the value 0x0003. See table 29 "Protocol_id". |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.4.9.3 MIME type | The MIME type for an AIT file shall be "application/vnd.dvb.ait". The file extension shall be ".ait". Implementations may also encounter the MIME type "application/dvb.ai" for the AIT used for backwards compatibility. Use of this MIME type is not recommended for new applications, deployments of services. |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.5 Generic descriptors | |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.5.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... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.5.2 Data broadcast id descriptor | |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.5.2.0 Introduction | The data_broadcast_id_descriptor is defined for use in the elementary stream information of the PMT. The descriptor identifies: • The transport format of the data broadcast whose "principal component" is on this elementary stream. • The semantics of "principal component" is transport protocol specific. • The set of app... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.5.2.1 Generic descriptor | The data_broadcast_id_descriptor is defined in a generic form by ETSI EN 300 468 [1] (illustrated in table 18). Where no "id specific data" is provided the descriptor just identifies the "principal" component of a data broadcast. Table 18: Generic data broadcast id descriptor syntax No.of bits Identifier Value data_bro... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.5.2.2 Data broadcast id descriptor for interactive application | When the data_broadcast_id is 0x00F0 or 0x00F1, (see table 38) the syntax of the data_broadcast_id_descriptor is as shown in table 19. This extends the generic descriptor with an optional list of application types for which autostart applications may exist within the data broadcast. This list provides a hint to allow t... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.5.3 Application descriptor | Exactly one instance of the application_descriptor shall be contained in every "application" (inner) descriptor loop of the AIT. Table 20: Application descriptor syntax No.of bits Identifier Value application_descriptor() { descriptor_tag 8 uimsbf 0x00 descriptor_length 8 uimsbf application_profiles_length 8 uimsbf for... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.5.4 Application recording descriptor | The application_recording_descriptor can be signalled in the application descriptor loop of the AIT. This descriptor contains extra information on application life cycle indicating in particular if an application is appropriate to use in conditions of trick-mode playback. It indicates whether this application shall or ... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.5.5 Application usage descriptor | The application_usage_descriptor identifies that the application provides a specific, well-known, service; for example teletext, EPG or chat. Receivers may include a shortcut to start these services, for example a remote control key. Receivers may also include a native UI offering access to these services. If no applic... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.5.6 User information descriptors | |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.5.6.0 Introduction | The user information descriptors complement the application_descriptor by providing information suitable for presentation to the user (where the application_descriptor provides technical information for automatic use by the receiver). These descriptors are defined for use in the "application" (inner) descriptor loop of... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.5.6.1 Application name descriptor | Exactly one instance of this descriptor shall be included in the "application" (inner) descriptor loop. The application name shall distinguish the application and shall be informative to the user. Table 24: Application name descriptor syntax No.of bits Identifier Value application_name_descriptor() { descriptor_tag 8 u... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.5.6.2 Application icons descriptor | Zero or one instance of this descriptor shall be included in the "application" (inner) descriptor loop. It allows icons to be associated with the application. ETSI ETSI TS 102 809 V1.3.1 (2017-06) 43 Table 25: Application icons descriptor syntax No.of bits Identifier Value application_icons_descriptor() { descriptor_ta... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.5.7 External application authorization descriptor | The "common" (first) descriptor loop of the Application Information Table may contain zero or more external_application_authorization_descriptors. Each descriptor contains information about external applications that are allowed to continue to run with the applications listed in this Application Information Table sub-t... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.5.8 Graphics constraints descriptor | The graphics_constraints_descriptor defines the circumstances under which an application can work (or has been tested to work). These circumstances are: • which full screen graphics resolutions an application supports; • whether an application can work when its video is controlled (e.g. scaled to less than full screen ... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.6 Transport protocol descriptors | |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.6.0 Introduction | The transport_protocol_descriptor identifies the transport protocol associated with a service component and possibly provides protocol dependent information. The descriptor may be used in either the "common" (outer) descriptor loop or the "application" (inner) descriptor loop. When in the "common" loop it applies to al... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.6.1 Syntax of selector bytes for OC transport | When the protocol ID is 0x0001 the selector bytes in the transport_protocol_descriptor shall be as shown in table 31. Table 31: Syntax of selector bytes for OC transport Syntax Bits Identifier remote_connection 1 bslbf reserved_future_use 7 bslbf if( remote_connection == "1" ) { original_network_id 16 uimsbf transport_... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.6.2 Syntax of selector bytes for interaction channel transport | When the protocol ID is 0x0003 the selector bytes in the transport_protocol_descriptor shall be as shown in table 32 "Syntax of selector bytes for interaction transport". This allows encoding of a number of URLs. The descriptor can also be used in a simplified form where only one URL is encoded. For efficiency when enc... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.7 Simple application location descriptor | |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.7.0 Introduction | One instance of this descriptor shall be contained in the "application" (inner) descriptor loop of the AIT for each application. Table 33: Simple application location descriptor syntax No.of bits Identifier Value simple_application_location_descriptor () { descriptor_tag 8 uimsbf 0x15 descriptor_length 8 uimsbf for(i=0... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.7.1 Example | The following example describes the usage of the simple_application_location_descriptor. An application author designs an application in the following manner: • The application data is distributed among several directories, for instance an "image" directory and a "main" directory. • The application entry point is a doc... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.8 Simple application boundary descriptor | This descriptor is defined for use in the application loop of the AIT. It provides a set of prefixes that describe the data elements that form the application. This descriptor is optional. When absent, the application boundary defaults to the complete set of all content coming from the transport signalled in the transp... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.9 Service information | |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.9.1 Data broadcast descriptor for interactive application announcement | The generic data_broadcast_descriptor is defined in ETSI EN 300 468 [1]. This clause defines the syntax and semantics of the selector bytes when the data broadcast id has the value 0x00F2 (see table 36). In this case the selector bytes provide a list of interactive applications and information about each application. Z... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.10 Stored applications | |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.3.10.1 Application storage descriptor | This application_storage_descriptor advertises that an application can be stored and provides some indications of its properties. The presence of this descriptor indicates that an Application Description File is provided for the application (see clause 5.2.11). For a storable application a single application_storage_de... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.4 XML-based syntax | |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.4.0 Introduction | This clause defines an XML encoding for the AIT in addition to the MPEG-2 table and section based encoding defined in clause 5.3 of the present document. Since the intended use for this XML encoding is in conjunction with the SD&S defined in ETSI TS 102 034 [6], this encoding follows the same format and re-uses already... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.4.1 Service bound application signalling | Service bound applications shall be signalled by including an ApplicationList element in either the IPService or the Package elements of SD&S (see ETSI TS 102 034 [6]). This is fully specified in clauses 5.4.3.2 and 5.4.3.1 respectively of the present document. Applications are either defined inline within the Applicat... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.4.2 Signalling of unbound applications | Unbound applications (i.e. applications which are not associated with a specific service) shall be signalled by including one or more AbstractIPService elements in the SD&S service provider discovery record (see ETSI TS 102 034 [6]). This is fully specified in clause 5.4.3.3. Applications are either defined inline with... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.4.3 Extensions to defined SD&S elements | |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.4.3.1 Package | The application list signalled in the package contains a set of applications which are available for all the IPServices signalled in the package. The ApplicationList is added as an extension to the Package type defined in ETSI TS 102 034 [6]. <xsd:complexType name="PackageType"> <xsd:complexContent> <xsd:extension base... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.4.3.2 IP Service | Service bound applications for single services are signalled by an extension of the IPService type defined in ETSI TS 102 034 [6]. <xsd:complexType name="IPServiceType"> <xsd:complexContent> <xsd:extension base="ipi:IPService"> <xsd:choice> <xsd:element name="ApplicationList" type="mhp:ApplicationList" minOccurs="0"/> ... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.4.3.3 ServiceProvider | Unbound applications are signalled by an extension of the ServiceProviderType type as defined in ETSI TS 102 034 [6]. <xsd:complexType name="ServiceProviderType"> <xsd:complexContent> <xsd:extension base="ipi:ServiceProviderType"> <xsd:sequence> <xsd:element name="AbstractService" type="mhp:AbstractIPService" maxOccurs... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.4.4 New XML element definitions | |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.4.4.1 ApplicationList | <xsd:complexType name="ApplicationList"> <xsd:sequence minOccurs="0" maxOccurs="unbounded"> <xsd:element name="application" type="mhp:Application" minOccurs="0" maxOccurs="unbounded"/> <xsd:element name="ApplicationReference" type="mhp:ApplicationIdentifier" minOccurs="0" maxOccurs="unbounded"> </xsd:sequence> </xsd:co... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.4.4.2 Application | |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.4.4.2.0 Overview | <xsd:complexType name="Application"> <xsd:sequence> <xsd:element name="appName" type="ipi:MultilingualType" maxOccurs="unbounded"/> <xsd:element name="applicationIdentifier" type="mhp:ApplicationIdentifier"/> <xsd:element name="applicationDescriptor" type="mhp:ApplicationDescriptor"/> <xsd:element name="applicationSpec... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.4.4.2.1 Application Specific Information (informative) | Some platform specifications may choose to describe, or require, extra information to be communicated to the receiver that is outside the scope of information currently carried in the Application element, for example additional transport protocol information or security related information. To enable this, the Applicat... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.4.4.3 ApplicationIdentifier | <xsd:complexType name="ApplicationIdentifier"> <xsd:sequence> <xsd:element name="orgId" type="xsd:unsignedInt"/> <xsd:element name="appId" type="xsd:unsignedShort"/> </xsd:sequence> </xsd:complexType> As defined in clause 5.2.3 "Application identification", an application is uniquely identified by: • OrgId, a globally ... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.4.4.4 ApplicationDescriptor | <xsd:complexType name="ApplicationDescriptor"> <xsd:sequence> <xsd:element name="type" type="mhp:ApplicationType"/> <xsd:element name="controlCode" type="mhp:ApplicationControlCode"/> <xsd:element name="visibility" type="mhp:VisibilityDescriptor" minOccurs="0"/> <xsd:element name="serviceBound" type="xsd:boolean" defau... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.4.4.5 VisibilityDescriptor | <xsd:simpleType name="VisibilityDescriptor"> <xsd:restriction base="xsd:string"> <xsd:enumeration value="NOT_VISIBLE_ALL"/> <xsd:enumeration value="NOT_VISIBLE_USERS "/> <xsd:enumeration value="VISIBLE_ALL"/> </xsd:restriction> </xsd:simpleType> These values are defined in table 5 in clause 5.2.6.1 "Semantics". |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.4.4.6 IconDescriptor | <xsd:complexType name="IconDescriptor"> <xsd:attribute name="filename" type="xsd:string" use="required"/> <xsd:attribute name="size" type="xsd:unsignedShort" use="optional"/> <xsd:attribute name="aspectRatio" type="mhp:AspectRatio" use="optional"/> </xsd:complexType> As defined in clause 5.2.8 "Application icons" the I... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.4.4.7 AspectRatio | <xsd:simpleType name="AspectRatio"> <xsd:restriction base="xsd:string"> <xsd:enumeration value="4_3"/> <xsd:enumeration value="16_9"/> <xsd:enumeration value="1_1"/> </xsd:restriction> </xsd:simpleType> These aspect ratios are the set of aspect ratios used in table 7 in clause 5.2.8 "Application icons". |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.4.4.8 MhpVersion | <xsd:complexType name="MhpVersion"> <xsd:sequence minOccurs="1"> <xsd:element name="profile" type="ipi:Hexadecimal16bit "/> <xsd:element name="versionMajor" type="ipi:Hexadecimal8bit "/> <xsd:element name="versionMinor" type="ipi:Hexadecimal8bit "/> <xsd:element name="versionMicro" type="ipi:Hexadecimal8bit "/> </xsd:s... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.4.4.9 StorageCapabilities | <xsd:complexType name="StorageCapabilities"> <xsd:sequence minOccurs="0"> <xsd:element name="storageProperty" type="mhp:StorageType"/> </xsd:sequence> <xsd:attribute name="launchableFromBroadcast" type="xsd:boolean" use="required"/> <xsd:attribute name="launchableCompletelyFromCache" type="xsd:boolean" use="required"/>... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.4.4.10 StorageType | <xsd:simpleType name="StorageType"> <xsd:restriction base="xsd:string"> <xsd:enumeration value="BROADCAST-RELATED"/> <xsd:enumeration value="STANDALONE"/> </xsd:restriction> </xsd:simpleType> See clause 5.2.11.1.1 "Lifecycle of stored applications". |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.4.4.11 ApplicationType | <xsd:complexType name="ApplicationType"> <xsd:choice> <xsd:element name="DvbApp" type="mhp:DvbApplicationType"/> <xsd:element name="OtherApp" type="mpeg7:mimeType"/> </xsd:choice> </xsd:complexType> See clause 5.2.2 "Application types". |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.4.4.12 DvbApplicationType | <xsd:simpleType name="DvbApplicationType"> <xsd:restriction base="xsd:string"> <xsd:enumeration value="DVB-J"/> <xsd:enumeration value="DVB-HTML"/> </xsd:restriction> </xsd:simpleType> |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.4.4.13 ApplicationControlCode | <xsd:simpleType name="ApplicationControlCode"> <xsd:restriction base="xsd:string"> <xsd:enumeration value="AUTOSTART"/> <xsd:enumeration value="PRESENT"/> <xsd:enumeration value="DESTROY"/> <xsd:enumeration value="KILL"/> <xsd:enumeration value="PREFETCH"/> <xsd:enumeration value="REMOTE"/> <xsd:enumeration value="DISA... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.4.4.14 ApplicationSpecificDescriptor | <xsd:complexType name="ApplicationSpecificDescriptor"> <xsd:choice> <xsd:element name="dvbjDescriptor" type="mhp:DVBJDescriptor"/> <xsd:element name="htmlDescriptor" type="mhp:DVBHtmlDescriptor"/> <xsd:element name="otherDescriptor" type="mhp:OtherDescriptor"/> </xsd:choice> </xsd:complexType> <xsd:complexType name="Ot... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.4.4.15 AbstractIPService | <xsd:complexType name="AbstractIPService"> <xsd:sequence> <xsd:element name="svcName" type="ipi:MultilingualType" maxOccurs="unbounded"/> <xsd:element name="svcId" type="mhp:Hexadecimal24bit"/> <xsd:element name="isAutoSelect" type="xsd:boolean"/> <xsd:element name="ApplicationList" type="mhp:ApplicationList" minOccurs... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.4.4.16 ApplicationOfferingType | <xsd:complexType name="ApplicationOfferingType"> <xsd:complexContent> <xsd:extension base="ipi:OfferingBase"> <xsd:sequence> <xsd:element name="ApplicationList" maxOccurs="unbounded"> <xsd:complexType> <xsd:sequence> <xsd:element name="Application" type="mhp:Application" maxOccurs="unbounded"/> </xsd:sequence> </xsd:co... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.4.4.17 ServiceDiscovery | <xsd:element name="ServiceDiscovery"> <xsd:complexType> <xsd:choice> <xsd:element name="ApplicationDiscovery" type="mhp:ApplicationOfferingType" maxOccurs="unbounded"/> ETSI ETSI TS 102 809 V1.3.1 (2017-06) 58 </xsd:choice> </xsd:complexType> </xsd:element> NOTE: This element forms the root element of an SD&S XML insta... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.4.4.18 ApplicationUsageDescriptor | <xsd:complexType name="ApplicationUsageDescriptor"> <xsd:sequence> <xsd:element name="ApplicationUsage" type="xsd:anyURI" minOccurs="0" maxOccurs="unbounded"/> </xsd:sequence> </xsd:complexType> See clause 5.2.10.3 for the definition of the semantics of this element. |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.4.4.19 TransportProtocolDescriptorType | <xsd:complexType name="TransportProtocolDescriptorType" abstract="true" /> This type defines the base class for a transport protocol descriptor. This is an abstract type - subclasses of this type are defined to support specific transport protocols. See clause 5.3.6 for a wider discussion of transport protocol descripto... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.4.4.20 HTTPTransportType | <xsd:complexType name="HTTPTransportType"> <xsd:complexContent> <xsd:extension base="mhp:TransportProtocolDescriptorType"> <xsd:sequence> <xsd:element name="URLBase" type="xsd:anyURI" minOccurs="1" maxOccurs="1" /> <xsd:element name="URLExtension" type="xsd:anyURI" minOccurs="0" maxOccurs="unbounded" /> </xsd:sequence>... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.4.4.21 OCTransportType | <xsd:complexType name="OCTransportType"> <xsd:complexContent> <xsd:extension base="mhp:TransportProtocolDescriptorType"> <xsd:sequence> <xsd:choice maxOccurs="1" minOccurs="0"> <xsd:element name="DvbTriplet" type="ipi:DVBTriplet"> </xsd:element> <xsd:element name="TextualId" type="ipi:TextualIdentifier"> </xsd:element>... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.4.4.22 ComponentTagType | <xsd:complexType name="ComponentTagType"> <xsd:attribute name="ComponentTag" type="ipi:Hexadecimal8bit"> </xsd:attribute> </xsd:complexType> This type defines the representation of an DVB component tag. |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.4.4.23 SimpleApplicationLocationDescriptorType | <xsd:simpleType name="SimpleApplicationLocationDescriptorType"> <xsd:restriction base="xsd:anyURI" /> </xsd:simpleType> This descriptor is defined in clause 5.3.7. |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.4.4.24 SimpleApplicationBoundaryDescriptorType | <xsd:complexType name="SimpleApplicationBoundaryDescriptorType"> <xsd:sequence> <xsd:element name="BoundaryExtension" type="xsd:anyURI" minOccurs="1" maxOccurs="unbounded"/> </xsd:sequence> </xsd:complexType> This descriptor provides a set of prefixes that describe the data elements that form the application. See claus... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.4.5 ApplicationDiscovery record | An ApplicationDiscovery record is an instantiation of the ApplicationOfferingType carried in ServiceDiscovery element as specified by clauses 5.4.4.16 and 5.4.4.17. The presence and retrieval location of an ApplicationDiscovery record is signalled from the ServiceProviderDiscovery record using the OfferingListType (see... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 5.5 Constant values | Table 38: Registry of constant values Where used Type Value Where Defined Scope Private data specifier descriptor descriptor tag 0x5F PSI and SI tables SI Data broadcast id descriptor 0x66 PMT Application Signalling Descriptor 0x6F PMT Service identifier descriptor 0x71 SDT Caching priority descriptor descriptor tag 0x... |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 6 Referencing DVB services | |
c08f9f65f04bba26a6f110caaf2548ca | 102 809 | 6.1 DVB URL syntax and semantics | The syntax and semantics of the "dvb:" URL scheme are defined in [20]. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.