hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AD Application Descriptor DD Deployment Descriptor EUT Equipment Under Test GCM Grid Component Model MET Maximum Execution Time MiB MebiByte VN Virtual Node XML eXtensible Markup Language |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 4 About GCM Interoperability testing | The present document describes interoperability tests for the Grid Component Model (GCM) standards. The main purpose of the tests is the assessment of the standardized GCM Deployment Descriptor (DD) [1] and Application Descriptor (AD) [2]. The method and criteria how these tests have been derived is explained in detail... |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 5 Test Configurations | This clause introduces the GCM test configurations used in the TDs described in clause 7. The test configurations include the entities infrastructure, deployment manager and input/output data servers. |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 5.1 Entities | In this clause, the entities used in the test configurations are explained. |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 5.1.1 Infrastructure including frontend | In the GCM DD, resources of infrastructures can be requested for deploying the GCM infrastructure. These resources of an infrastructure have to be accessible either in a direct or indirect manner. While infrastructures with indirect resource access offer a frontend that contacts a job scheduler and grants access to res... |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 5.1.2 Deployment Manager | The deployment manager (which can also be a human being) establishes the GCM infrastructure by converting GCM DD information into specific service calls or commands which are supported by the underlying infrastructure. After that, the test application with its parameters and infrastructure parameters can be submitted, ... |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 5.1.3 Input and output data server(s) | Input and output data servers are used to store input and/or output data of GCM applications independent of the infrastructure on which it runs on. Input and output data servers can be access independently using a supported file access protocol such as http, ftp, sftp, or file. Depending on the protocol, the data is ac... |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 5.2 Single Infrastructure | In the test configuration depicted in Figure 1, the Equipment Under Test (EUT) [4] contains a single infrastructure and the deployment manager. Access to the deployment manager, the infrastructure, the application, the GCM DD, and the GCM AD are available from one single physical machine. The user uses the deployment m... |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 5.3 Single Infrastructure with a bridge | The test configuration depicted in Figure 2 extends the test configuration described in clause 5.2 with a bridge. This test configuration has two EUTs, whereas EUT A contains the deployment manager and EUT B contains a single infrastructure. The deployment manager is only able to access the infrastructure via a bridge.... |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 5.4 Two Infrastructures and bridges | The test configuration depicted in Figure 3 extends the test configuration described in clause 5.3 with a second infrastructure and bridge. This test configuration has three EUTs, whereas EUT A contains the deployment manager, EUT B contains the infrastructure X, and EUT C contains the infrastructure Y. Since the deplo... |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 5.5 Single Infrastructure with input and output data server(s) | The test configuration depicted in Figure 4 extends the test configuration described in clause 5.1 with input and output data servers. Here, the application can access the input/output data servers from the infrastructure. Depending on the type of the resource access provided by the infrastructure, a frontend may or ma... |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 6 Test Applications | This clause describes test applications used in GCM interoperability tests to assess if requirements have been fulfilled as specified by the GCM standard(s). Example implementations of these test applications can be found in the electronic attachments GCM_Plugtests_DD_files_v010101.zip contained in archive ts_102811v01... |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 6.1 Single process batch job | This test application starts a single process batch job on a single processor. This job is a simple application that consumes CPU and memory for a given amount of time. Its behavior can be controlled by the following parameters: • execTime: execution time in seconds, • memoryConsumption: the amount of memory that has t... |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 6.2 Parallel job | This test application starts a job that uses multiple processes. Each process is mapped to a single processor. The multiple processor application consists of one master process and multiple worker processes. The worker processes communicate with the master process so that the master process receives notifications from ... |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 6.3 Virtual Node GCM Application | This test application starts a deployment as specified in the GCM AD and DD. Once the deployment has been performed, it prints the information provided by each virtual node either to the standard output or a file. For each virtual node, the following information is mandatory: • virtual node name, • current number of no... |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 6.4 Data Manipulation GCM Application | This test application starts a deployment as specified in the GCM AD and DD. It deploys a worker on every node it gets. Each worker reads the same input file from the remote or local input location as specified in the GCM AD. It creates a file with the same content as the input file into the remote or local output loca... |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 7 GCM Test Descriptions | The GCM test descriptions describe interoperability tests for GCM DD and AD. Each test requires a test configuration that is described in clause 5 and, in addition, a test application as explained in clause 6. Example implementations of these test applications can be found in the electronic attachments GCM_Plugtests_DD... |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 7.1 GCM Deployment Descriptor | |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 7.1.1 Direct access | |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 7.1.1.1 Processor allocation | |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 7.1.1.1.1 Single processor with direct resource access | Interoperability Test Description Identifier: TD_GCM_DD_DA_PA_001 Summary: Ensure that an infrastructure with direct resource access provides a single processor as specified in the GCM DD Configuration: Single Infrastructure or single Infrastructure with a bridge Specification References GCM DD clause 7.1 Test Applicat... |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 7.1.1.1.2 Single processor with multiple threads with direct resource access | Interoperability Test Description Identifier: TD_GCM_DD_DA_PA_002 Summary: Ensure that an infrastructure with direct resource access provides a single processor with multiple threads as specified in the GCM DD Configuration: Single Infrastructure or single Infrastructure with a bridge Specification References GCM DD cl... |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 7.1.1.1.3 Multiple processors on a single host with direct resource access | Interoperability Test Description Identifier: TD_GCM_DD_DA_PA_003 Summary: Ensure that an infrastructure with direct resource access provides multiple processors for a parallel application on a single host as specified in the GCM DD Configuration: Single Infrastructure or single Infrastructure with a bridge Specificati... |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 7.1.1.1.4 Multiple processors on multiple hosts with direct resource access | Interoperability Test Description Identifier: TD_GCM_DD_DA_PA_004 Summary: Ensure that an infrastructure with direct resource access provides multiple processors for a parallel application on multiple hosts as specified in the GCM DD Configuration: Single Infrastructure or single Infrastructure with a bridge Specificat... |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 7.1.1.1.5 Multiple processors in two infrastructures with direct resource access | Interoperability Test Description Identifier: TD_GCM_DD_DA_PA_005 Summary: Ensure that two infrastructures with direct resource access provide multiple processors for a parallel application as specified in the GCM DD Configuration: Two Infrastructures and bridges Specification References GCM DD clause 7.1 Test Applicat... |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 7.1.2 Indirect access | |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 7.1.2.1 Processor allocation | |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 7.1.2.1.1 Single processor with indirect resource access | Interoperability Test Description Identifier: TD_GCM_DD_IA_PA_001 Summary: Ensure that an infrastructure with indirect resource access provides a single processor as specified in the GCM DD Configuration: Single Infrastructure or single Infrastructure with a bridge Specification References GCM DD clause 7.2 Test Applic... |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 7.1.2.1.2 Multiple processors with indirect resource access | Interoperability Test Description Identifier: TD_GCM_DD_IA_PA_002 Summary: Ensure that an infrastructure with indirect resource access provides multiple processors for a parallel application as specified in the GCM DD Configuration: Single Infrastructure or single Infrastructure with a bridge Specification References G... |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 7.1.2.1.3 Multiple processors in two infrastructures with indirect resource access | Interoperability Test Description Identifier: TD_GCM_DD_IA_PA_003 Summary: Ensure that two infrastructures with indirect resource access provide multiple processors for a parallel application as specified in the GCM DD Configuration: Two Infrastructures and bridges Specification References GCM DD clause 7.2 Test Applic... |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 7.1.2.2 Infrastructure properties | |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 7.1.2.2.1 Termination before the maximum execution time | Interoperability Test Description Identifier: TD_GCM_DD_IA_IP_001 Summary: Ensure that in an infrastructure with indirect resource access, an application terminates as expected within the maximum execution time (MET) as specified in the GCM DD Configuration: Single Infrastructure or single Infrastructure with a bridge ... |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 7.1.2.2.2 Exceeding the maximum execution time | Interoperability Test Description Identifier: TD_GCM_DD_IA_IP_002 Summary: Ensure that in an infrastructure with indirect resource access, any application that exceeds the maximum execution time (MET) as specified in the GCM DD is killed. Configuration: Single Infrastructure or single Infrastructure with a bridge Speci... |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 7.1.2.2.3 Job queues | Interoperability Test Description Identifier: TD_GCM_DD_IA_IP_003 Summary: Ensure that an infrastructure with indirect resource access handles job queue parameters as specified in the GCM DD Configuration: Single Infrastructure or single Infrastructure with a bridge Specification References GCM DD clause 7.2 Test Appli... |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 7.1.2.2.4 Redirection of standard output | Interoperability Test Description Identifier: TD_GCM_DD_IA_IP_004 Summary: Ensure that an infrastructure with indirect resource access supports standard output redirection as specified in the GCM DD Configuration: Single Infrastructure or single Infrastructure with a bridge Specification References GCM DD clause 7.2 Te... |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 7.1.2.2.5 Memory specification | Interoperability Test Description Identifier: TD_GCM_DD_IA_IP_005 Summary: Ensure that an infrastructure with indirect resource access selects resources according to memory specification as specified in the GCM DD Configuration: Single Infrastructure or single Infrastructure with a bridge Specification References GCM D... |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 7.1.2.2.6 Specified memory exceeds maximum amount of memory | Interoperability Test Description Identifier: TD_GCM_DD_IA_IP_006 Summary: Ensure that an infrastructure with indirect resource access does not assign resources if the memory specification as specified in the GCM DD exceeds the maximum amount of physical main memory. Configuration: Single Infrastructure or single Infra... |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 7.1.2.2.7 Memory limitation | Interoperability Test Description Identifier: TD_GCM_DD_IA_IP_007 Summary: Ensure that an infrastructure with indirect resources access enforces memory limitation as specified in the GCM DD Configuration: Single Infrastructure or single Infrastructure with a bridge Specification References GCM DD clause 7.2 Test Applic... |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 7.1.3 Direct and indirect access | |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 7.1.3.1 Processor allocation | |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 7.1.3.1.1 Multiple processors in an infrastructures with indirect and direct resource access | Interoperability Test Description Identifier: TD_GCM_DD_DA_IA_PA_001 Summary: Ensure that an infrastructure with indirect resource access and an infrastructure with direct resource access provide multiple processors for a parallel application as specified in the GCM DD Configuration: Two Infrastructures and bridges Spe... |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 7.2 GCM Application Descriptor | |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 7.2.1 Virtual node | |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 7.2.1.1 Specific capacity of a single virtual node | Interoperability Test Description Identifier: TD_GCM_AD_VN_001 Summary: Ensure that a specific capacity of a virtual node (VN) is enforced as specified in the GCM AD Configuration: Single Infrastructure or single Infrastructure with a bridge Specification References GCM AD clause 5.2.2 Test Application Virtual Node GCM... |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 7.2.1.2 Maximum capacity of a single virtual node | Interoperability Test Description Identifier: TD_GCM_AD_VN_002 Summary: Ensure that a maximum capacity of a virtual node (VN) is enforced as specified in the GCM AD Configuration: Single Infrastructure or single Infrastructure with a bridge Specification References GCM AD clause 5.2.2 Test Application Virtual Node GCM ... |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 7.2.1.3 Specific capacities of two virtual nodes | Interoperability Test Description Identifier: TD_GCM_AD_VN_003 Summary: Ensure that specific capacities of two virtual nodes (VNs) are enforced as specified in the GCM AD Configuration: Single Infrastructure or single Infrastructure with a bridge Specification References GCM AD clause 5.2.2 Test Application Virtual Nod... |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 7.2.1.4 Maximum capacities of two virtual nodes | Interoperability Test Description Identifier: TD_GCM_AD_VN_004 Summary: Ensure that when two virtual nodes (VNs) request maximum capacities, then nodes are assigned fairly Configuration: Single Infrastructure or single Infrastructure with a bridge Specification References GCM AD clause 5.2.2 Test Application Virtual No... |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 7.2.1.5 Maximum and specific capacities of two virtual nodes | Interoperability Test Description Identifier: TD_GCM_AD_VN_005 Summary: Ensure that when a specific capacity of a virtual node (VN) and a maximum capacity of another virtual node are requested, nodes are assigned firstly to the VN that requests a specific capacity and the remaining nodes to the VN that request a maximu... |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 7.2.2 Data location | |
b50875d5e3ea9346837a4cdeb041edf8 | 102 811 | 7.2.2.1 Default input and output data | Interoperability Test Description Identifier: TD_GCM_AD_DL_001 Summary: Ensure that default input data can be read and default output data can be written for a specific file access protocol as specified in the GCM AD Configuration: Single Infrastructure with input and output data servers Specification References GCM AD... |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 1 Scope | The present document describes a method by which auxiliary data, which needs to be synchronized with linear components of a service, such as video and audio streams, may be carried in a DVB transport stream. |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 2 References | |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 3 Definition of terms, symbols and abbreviations | |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 3.1 Terms | For the purposes of the present document, the following terms apply: broadcast timeline: stream of data which conveys a metadata content timeline during the broadcast of an item of content NOTE: See clause A.2. metadata content timeline: conceptual progress of time inherent in an item of content, which may be referred ... |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 3.2 Symbols | Void. |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: CRC Cyclic Redundancy Check CRID Content Reference Identifier DSM-CC Digital Storage Media - Command & Control NOTE: Defined in ISO/IEC 13818-6 [i.1]. DVB Digital Video Broadcasting MPEG Moving Pictures Expert group NPT Normal Play Time NOTE: ... |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 4 Carriage of synchronized auxiliary data | |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 4.1 Introduction | Synchronized auxiliary data that needs to be delivered in such a way so as to ensure a fixed timing relationship with other linear streams within a DVB service, e.g. video and audio, shall be conveyed in Packetized Elementary Stream (PES) packets, which are carried by Transport Stream (TS) packets as defined in ISO/IEC... |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 4.2 Transport Stream (TS) packet format | The standard TS packet syntax and semantics are followed. |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 4.3 PES packet format | The standard PES packet syntax and semantics are followed noting the following constraints: stream_id Set to "1011 1101" (0xBD) meaning "private_stream_1". data_alignment_indicator Set to "1". PES_packet_data_byte These bytes are coded in accordance with the auxiliary data structure (see clause 4.5). PTS This should be... |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 4.4 Stream location | An elementary stream carrying synchronized auxiliary data will have the stream_type value 0x06 (see clause 4.1) and stream_id value 0xBD (see clause 4.3). However, this information may not always be sufficient to unambiguously locate a specific synchronized auxiliary data stream as there may be more than one elementary... |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 4.5 Auxiliary data structure | The syntax for this structure is defined by table 1. Table 1: auxiliary_data_structure Syntax No. of bits Identifier auxiliary_data_structure() { payload_format 4 uimsbf Reserved 3 uimsbf CRC_flag 1 uimsbf for (i=0; i<N; i++) { payload_byte 8 uimsbf } if ( CRC_flag == '1') { CRC_32 32 uimsbf } } NOTE: Since this struct... |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 5 Descriptors | |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 5.1 Descriptor identification | The payload field of the auxiliary data structure (see clause 4.5) may contain zero or more of the descriptors listed in table 3. Table 3: Descriptors for use in auxiliary data structure Tag value Identifier 0x00 DVB reserved 0x01 TVA_id_descriptor 0x02 broadcast_timeline_descriptor 0x03 time_base_mapping_descriptor 0x... |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 5.2 Descriptor definitions | |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 5.2.1 TVA_id descriptor | |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 5.2.1.1 Usage | The intended use for this descriptor is defined in ETSI TS 102 323 [5], clause 11.2.4. The minimum repetition rate for instances of this descriptor relating to a particular value of TVA_id is at least once every 2 seconds. |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 5.2.1.2 Syntax | The syntax of this descriptor is defined in ETSI TS 102 323 [5], clause 11.2.4. |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 5.2.1.3 Semantics | The basic semantics of this descriptor are defined in ETSI TS 102 323 [5], clause 11.2.4. In addition when this descriptor is carried in synchronized auxiliary data with the payload_format set to 0x1, the following shall apply: descriptor_tag: This 8-bit field shall be set to the value 0x01, overriding the value define... |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 5.2.2 Broadcast timeline descriptor | |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 5.2.2.1 Introduction | An item of linear content has an inherent timeline that advances in sync with its flow. To enable control over the presentation of an item of content by a (metadata) application this inherent timeline can be expressed in terms of what MPEG refers to (in ISO/IEC 13818-1 [1]) as the metadata content timeline (see clause ... |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 5.2.2.2 Usage | When carried within synchronized auxiliary data the broadcast timeline descriptor provides a means to accurately associate a value of time with a specific point in the broadcast. This provides a means to describe a broadcast timeline. The broadcast timeline descriptor defines time in terms of a count of ticks. This unf... |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 5.2.2.3 Syntax | The syntax for this descriptor is defined by table 4. Table 4: broadcast_timeline_descriptor Syntax No. of bits Identifier broadcast_timeline_descriptor() { descriptor_tag 8 uimsbf descriptor_length 8 uimsbf broadcast_timeline_id 8 uimsbf reserved 1 uimsbf broadcast_timeline_type 1 uimsbf continuity_indicator 1 uimsbf ... |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 5.2.2.4 Semantics | descriptor_tag: This 8-bit field shall be set to the value 0x02. descriptor_length: This 8-bit field specifies the total number of bytes of the data portion of the descriptor following the byte defining the value of this field. broadcast_timeline_id: This 8-bit field shall be used to uniquely identify the broadcast tim... |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 5.2.3 Time base mapping descriptor | |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 5.2.3.1 Usage | The time base mapping descriptor provides a means to explicitly associate an external time base with a broadcast timeline. The minimum repetition rate for instances of this descriptor relating to a particular value of time_base_mapping_id is at least once every 5 seconds. |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 5.2.3.2 Syntax | The syntax for this descriptor is defined by table 7. Table 7: time_base_mapping_descriptor Syntax No. of bits Identifier time_base_mapping_descriptor() { descriptor_tag 8 uimsbf descriptor_length 8 uimsbf time_base_mapping_id 8 uimsbf reserved 1 uimsbf num_time_bases 7 uimsbf for (i=0; i<num_time_base; i++) { time_bas... |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 5.2.3.3 Semantics | descriptor_tag: This 8-bit field shall be set to the value 0x03. descriptor_length: This 8-bit field specifies the total number of bytes of the data portion of the descriptor following the byte defining the value of this field. time_base_mapping_id: This 8-bit field shall be used to uniquely identify a set of mappings ... |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 5.2.4 Content labelling descriptor | |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 5.2.4.1 Usage | The content labelling descriptor provides a means to associate a label, in the form of an identifier, to an item of content. This label can be used by metadata to reference the associated content. The format of the identifier can vary depending on the metadata application. Within a particular synchronized auxiliary dat... |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 5.2.4.2 Syntax | The syntax for this descriptor is defined in ISO/IEC 13818-1 [1]. |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 5.2.4.3 Semantics | The basic semantics for this descriptor are defined in ISO/IEC 13818-1 [1]. Within DVB systems the following additional semantics shall apply: metadata_application_format: This field shall be encoded according to table 8. Table 8: metadata_application_format Value Description 0x0000-0x00FF MPEG reserved 0x0100 TVA meta... |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 5.2.4.4 PSI Signalling | To indicate that an elementary stream being used for synchronized auxiliary data conveys one or more content labelling descriptors relating to a particular metadata application (i.e. the same encoded metadata application format) a concise form of the content labelling descriptor may be placed in the corresponding ES_in... |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 5.2.5 Synchronized event descriptor | |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 5.2.5.1 Usage | The synchronized event descriptor contains information allowing the transmission of an application-specific event, the temporal reference of which needs to be synchronized with other components of the broadcast stream, i.e. a synchronized event. NOTE: The definition of event in this context is a discrete temporal event... |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 5.2.5.2 Syntax | The syntax for this descriptor is defined by table 11. Table 11: synchronised_event_descriptor Syntax No. of bits Identifier synchronised_event_descriptor(){ descriptor_tag 8 uimsbf descriptor_length 8 uimsbf synchronised_event_context 8 uimsbf synchronised_event_id 16 uimsbf synchronised_event_id_instance 8 uimsbf Res... |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 5.2.5.3 Semantics | descriptor_tag: This 8-bit field shall be set to the value 0x05. descriptor_length: This 8-bit field specifies the total number of bytes of the data portion of the descriptor following the byte defining the value of this field. synchronised_event_context: This 8-bit field shall identify the application-specific context... |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 5.2.6 Synchronized event cancel descriptor | |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 5.2.6.1 Usage | The synchronized event cancel descriptor provides a means to cancel synchronized events whose temporal reference has been defined (using the synchronized event descriptor) but not yet reached, i.e. the synchronized event is defined to happen at some point in the future and so shall be referred to as "pending". For exam... |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 5.2.6.2 Syntax | The syntax for this descriptor is defined by table 12. Table 12: synchronised_event_cancel_descriptor Syntax No. of bits Identifier synchronised_event_cancel_descriptor(){ descriptor_tag 8 uimsbf descriptor_length 8 uimsbf synchronised_event_context 8 uimsbf synchronised_event_id 16 uimsbf } |
380606ddbbfc567cf1c897a46f2078f3 | 102 823 | 5.2.6.3 Semantics | descriptor_tag: This 8-bit field shall be set to the value 0x06. descriptor_length: This 8-bit field specifies the total number of bytes of the data portion of the descriptor following the byte defining the value of this field. ETSI ETSI TS 102 823 V1.3.1 (2022-09) 24 synchronised_event_context: This 8-bit field shall ... |
f8ca67144ad9abf1f1869e5caac05c87 | 102 804 | 1 Scope | The present document specifies the European performance and functional requirements of multi-operation DSL equipment as defined in clause 3.1 and applied to Line Termination Units (such as an exchange-based or cabinet-based DSLAM) and Network Termination Units (such as a CPE) equipment. Auto-mode operation and autosens... |
f8ca67144ad9abf1f1869e5caac05c87 | 102 804 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
f8ca67144ad9abf1f1869e5caac05c87 | 102 804 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] Recommendation ITU-T G.992.5: "Asymmetric digital subscriber line 2 transceivers (ADSL2)- Extended bandwidth ADSL2 (ADSL2plus)". [2] Recommendation ITU-T G.993.2: "Very high speed subscriber line transceivers 2 (VDSL2)". [... |
f8ca67144ad9abf1f1869e5caac05c87 | 102 804 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] Recommendation ITU-T G.994.1: "Handshake procedures for digital subscriber line transceivers". |
f8ca67144ad9abf1f1869e5caac05c87 | 102 804 | 3 Definitions and abbreviations | |
f8ca67144ad9abf1f1869e5caac05c87 | 102 804 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: generic mode: operation mode of the DSL equipment (ADSL2plus or VDSL2) as defined in Recommendations ITU-T G.992.5 [1] and ITU-T G.993.2 [2] ETSI ETSI TS 102 804 V1.1.1 (2013-09) 6 multi-operation DSL equipment: equipment which is comp... |
f8ca67144ad9abf1f1869e5caac05c87 | 102 804 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ADSL Asymmetric Digital Subscriber Line ATM Asynchronous Transfer Mode ATU ADSL2plus Transceiver Unit NOTE: According to [1]. CPE Customer Premises Equipment DSL Digital Subscriber Line DSLAM Digital Subscriber Line Access Multiplexer LT Line ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.