STANDARD 0217 - Packing KLV Packets into MPEG-2 Systems Streams Clause Samples

This clause defines the requirements and procedures for encapsulating Key-Length-Value (KLV) data packets within MPEG-2 systems streams. It specifies how KLV metadata should be formatted, aligned, and inserted into the stream to ensure compatibility and interoperability between different systems and devices. For example, it may detail the placement of KLV packets in transport or program streams and outline constraints on packet size or timing. The core function of this clause is to standardize the integration of metadata with video content, thereby facilitating reliable metadata exchange and consistent playback across MPEG-2 compliant platforms.
POPULAR SAMPLE Copied 1 times
STANDARD 0217 - Packing KLV Packets into MPEG-2 Systems Streams. If MPEG-2 is used with Nonsynchronized metadata, SMPTE RP 217-2001, Nonsynchronized Mapping of KLV Packets into MPEG-2 System Streams, is the NATO STANDARD for the non-synchronous encoding of metadata elements into MPEG-2 Systems Streams. Note: To be STANAG compliant, KLV metadata in BOTH the Transport Stream and Program Stream must be identified by the registered format_identifier 0x4B4C5641 (“KLVA”). SMPTE RP 217-2001 states that 0x4B4C5641 is the format_identifier to be used for the Transport Stream, but 0x4B4C5641 or “some other descriptor” may be used for the Program Stream. If MPEG-2 is used with Synchronized metadata, ISO/IEC 13818-1:2000/FPDAM 1: “Information technology -- Generic coding of moving pictures and associated audio information: Systems, AMENDMENT 1: Carriage of metadata over ISO/IEC 13818-1 streams” is mandated for the synchronous encoding of metadata for exchange of motion imagery and metadata files for collaboration of production work in progress among analysts; storage of work in progress for access by multiple users; and permanent archive of all contributions to a finished work.
View Source

Related to STANDARD 0217 - Packing KLV Packets into MPEG-2 Systems Streams

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Freedom has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Freedom. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Freedom (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Freedom, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Freedom will then have the option of paying the one-time SC rates to place the Loop.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes. 11.2 We may (i) compile statistical and other information related to the performance, operation and use of the Services, and (ii) use data from the Services in aggregated form for security and operations management, to create statistical analyses, and for research and development purposes (clauses i and ii are collectively referred to as “Service Analyses”). We may make Service Analyses publicly available; however, Service Analyses will not incorporate Your Content, Personal Data or Confidential Information in a form that could serve to identify You or any individual. We retain all intellectual property rights in Service Analyses. 11.3 We may provide You with the ability to obtain certain Oracle Software (as defined below) for use with the Services. If we provide Oracle Software to You and do not specify separate terms for such software, then such Oracle Software is provided as part of the Services and You have the non-exclusive, worldwide, limited right to use such Oracle Software, subject to the terms of this Agreement and Your order (except for separately licensed elements of the Oracle Software, which separately licensed elements are governed by the applicable separate terms), solely to facilitate Your use of the Services. You may allow Your Users to use the Oracle Software for this purpose, and You are responsible for their compliance with the license terms. Your right to use any Oracle Software will terminate upon the earlier of our notice (by web posting or otherwise) or the end of the Services associated with the Oracle Software. Notwithstanding the foregoing, if Oracle Software is licensed to You under separate terms, then Your use of such software is governed by the separate terms. Your right to use any part of the Oracle Software that is licensed under the separate terms is not restricted in any way by this Agreement.

  • Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

  • Start-Up and Synchronization Consistent with the mutually acceptable procedures of the Developer and Connecting Transmission Owner, the Developer is responsible for the proper synchronization of the Large Generating Facility to the New York State Transmission System in accordance with NYISO and Connecting Transmission Owner procedures and requirements.