26.04.2013 Views

TS 102 323 - V1.4.1 - Digital Video Broadcasting (DVB ... - ETSI

TS 102 323 - V1.4.1 - Digital Video Broadcasting (DVB ... - ETSI

TS 102 323 - V1.4.1 - Digital Video Broadcasting (DVB ... - ETSI

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

20<br />

Table 5: Permitted locations of the metadata pointer descriptor<br />

E<strong>TS</strong>I<br />

E<strong>TS</strong>I <strong>TS</strong> <strong>102</strong> <strong>323</strong> <strong>V1.4.1</strong> (2010-01)<br />

Scope Linkage location Example metadata fragment types<br />

Global BAT, NIT, common descriptor loop of the<br />

RNT, resolution provider descriptor loop of<br />

the RNT<br />

BroadcastEvent, Schedule, ServiceInformation,<br />

ProgramInformation, GroupInformation, Review,<br />

SegmentInformation, SegmentGroupInformation,<br />

PersonName, OrganizationName.<br />

<strong>DVB</strong> Service Service loop of the SDT BroadcastEvent, Schedule, ServiceInformation.<br />

CRID authority CRID authority descriptor loop of the RNT ProgramInformation, GroupInformation, Review,<br />

SegmentInformation, SegmentGroupInformation,<br />

PersonName, OrganizationName.<br />

5.3.3.2 Semantics<br />

This clause defines the use and additional semantics of fields of the metadata pointer descriptor.<br />

See ISO/IEC 13818-1 [9], clause 2.6.58 for the format and basic semantics of this descriptor.<br />

This descriptor shall be used with the constraints given below when associating an entity in a <strong>DVB</strong> network with a<br />

metadata service delivering relevant TV-Anytime metadata.<br />

metadata_application_format: This field shall have the same value as encoded in the metadata_application_format<br />

field of the metadata descriptor describing the target metadata service (see clause 5.3.4), that is the metadata descriptor<br />

with matching metadata_service_id carried in the PMT sub_table indicated by this descriptor.<br />

metadata_application_format_identifier: This field shall not be used.<br />

metadata_format: The value of this field shall be set according to table 6. If the metadata service is delivered in a<br />

<strong>DVB</strong> transport stream, the value of this field shall match the value of the metadata_format field in the metadata<br />

descriptor with a matching value of metadata_service_id in the PMT sub_table identified by this descriptor (see<br />

clause 5.3.4).<br />

Table 6: metadata_format<br />

Value Semantics<br />

0x00 to 0x3E Not used in the present document.<br />

0x3F Defined by metadata application format.<br />

0x40 to 0xEF User defined.<br />

0xF0 The encoding and encapsulation format as defined in<br />

clauses 9.3 and 9.4 of the present document.<br />

0xF1 to 0xF7 <strong>DVB</strong> Reserved.<br />

0xF8 to 0xFE User defined.<br />

0xFF Not used in the present document.<br />

metadata_format_identifier: This field shall not be used.<br />

metadata_service_id: This field shall be used to identify which metadata service this descriptor references. When that<br />

metadata service is delivered in a <strong>DVB</strong> transport stream, the target metadata service shall be described by a metadata<br />

descriptor with a matching value of metadata_service_id in the PMT sub_table identified by this descriptor (see<br />

clause 5.3.4).<br />

metadata_locator_record_flag: This field shall be set to '0' if this descriptor references a metadata service delivered in<br />

a <strong>DVB</strong> transport stream. Otherwise, this field shall be set to '1' (for example, if delivered over bi-directional IP<br />

according to <strong>TS</strong> <strong>102</strong> 822-6-1 [18]). If the metadata_format field is set to 0xF1 then this field shall be set to '1'.<br />

metadata_locator_record_length, metadata_locator_record: An option that may be used to point to an arbitrary<br />

URL not within a <strong>DVB</strong> network. If it is used the metadata locator record shall contain a compliant URI (see<br />

RFC 3986 [2]) which shall be encoded as described in clause 6.2. If this field contains a HTTP URL as specified in<br />

RFC 1945 [19], then that URL shall reference a metadata service that conforms to <strong>TS</strong> <strong>102</strong> 822-6-1 [18].<br />

MPEG_carriage_flags: A 2-bit field that shall be coded according to table 7. If the metadata_locator_record_flag is set<br />

to '1' then this field shall be set to 3. Otherwise, this field shall be set to either 0 or 1.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!