This file is raw output from pdftotext and may not be ideal for distribution. If you are a maintainer for Hackipedia, please sit down when you have time and clean this text version up. Source PDF: /mnt/main/jmc-storage/docs/SCTE/ANSI SCTE 042 IP Multicast for Digital MPEG Networks (2008).pdf Like all conversions the text below should be fully readable as UTF-8 unicode text. --------------------------------------------------------------- ENGINEERING COMMITTEE Digital Video Subcommittee AMERICAN NATIONAL STANDARD ANSI/SCTE 42 2008 IP MULTICAST FOR DIGITAL MPEG NETWORKS NOTICE The Society of Cable Telecommunications Engineers (SCTE) Standards are intended to serve the public interest by providing specifications, test methods and procedures that promote uniformity of product, interchangeability and ultimately the long term reliability of broadband communications facilities. These documents shall not in any way preclude any member or non- member of SCTE from manufacturing or selling products not conforming to such documents, nor shall the existence of such standards preclude their voluntary use by those other than SCTE members, whether used domestically or internationally. SCTE assumes no obligations or liability whatsoever to any party who may adopt the Standards. Such adopting party assumes all risks associated with adoption of these Standards, and accepts full responsibility for any damage and/or claims arising from the adoption of such Standards. Attention is called to the possibility that implementation of this standard may require the use of subject matter covered by patent rights. By publication of this standard, no position is taken with respect to the existence or validity of any patent rights in connection therewith. SCTE shall not be responsible for identifying patents for which a license may be required or for conducting inquiries into the legal validity or scope of those patents that are brought to its attention. Patent holders who believe that they hold patents which are essential to the implementation of this standard have been requested to provide information about those patents and any related licensing terms and conditions. Any such declarations made before or after publication of this document are available on the SCTE web site at http://www.scte.org. All Rights Reserved © Society of Cable Telecommunications Engineers, Inc. 2008 140 Philips Road Exton, PA 19341 i TABLE OF CONTENTS 1  INTRODUCTION .........................................................................................................1  1.1  SCOPE ..............................................................................................................1  2  REFERENCES ..............................................................................................................1  2.1  NORMATIVE REFERENCES ..................................................................................1  2.2  INFORMATIVE REFERENCES ................................................................................2  2.3  ACRONYMS AND ABBREVIATIONS........................................................................2  2.4  GLOBAL TERMS ................................................................................................3  3  MULTICAST IP DATA ENCAPSULATION ............................................................5  3.1  DVB MPE DATAGRAM ......................................................................................5  3.1.1  DVB Datagram Section Field constraints (Normative) ....................................6  3.2  ATSC MPE DATAGRAM ....................................................................................7  3.3  ATSC AND DVB COMPARISON (INFORMATIVE) ...............................................8  3.4  FORMULATION OF THE MAC_ADDRESS / DEVICEID (NORMATIVE) ...........................8  4  TRANSPORTING IP DATA OVER MPEG ............................................................10  4.1  DSM-CC STREAM TYPE .................................................................................. 11  4.2  MAC_ADDRESS_LIST_DESCRIPTOR() ............................................................... 11  4.2.1  MAC_Address_List_Descriptor() Field Definitions ....................................... 13  4.3  BUFFER MODEL .............................................................................................. 14  4.4  DEFINITION OF IP NETWORK ..................................................................... 15  ANNEX A: COORDINATION OF IP ADDRESS RANGES (INFORMATIVE) ..........16  ANNEX B: INCLUDING ATVEF DATA WITHIN AN MPEG PROGRAM (INFORMATIVE)........................................................................................................................17  ANNEX C: IP MULTICAST BUFFER MODEL (INFORMATIVE) .............................20  List of Figures FIGURE 1. CARRYING MULTICAST IP DATAGRAMS OVER MPEG ..................................................10 FIGURE 2. IP MULTICAST SERVERS ................................................................................................16 FIGURE 3. ANNOUNCEMENT, TRIGGER AND RESOURCE DATA CARRIED ON A SINGLE PID STREAM .................................................................................................................................................17 FIGURE 4. ANNOUNCEMENT CARRIED SEPARATELY FROM TRIGGERS AND RESOURCES ................18 FIGURE 5. SHARING TRIGGERS AND RESOURCES ............................................................................19 FIGURE 6. APPLICATION BUFFER MODEL FOR THE ACQUISITION OF IP MULTICAST DATA ..............20 List of Tables TABLE 1. ENCAPSULATION USING DVB MPE DATAGRAM SECTION ...............................................5 TABLE 2. ENCAPSULATION USING ATSC MPE DATAGRAM SECTION .............................................7 TABLE 3. MPE COMPARISON ............................................................................................................8 TABLE 4. MAC_ADDRESS_LIST_DESCRIPTOR() ............................................................................12 ii TABLE 5. CODING OF THE PDU_SIZE FIELD .....................................................................................13 iii 1 INTRODUCTION 1.1 SCOPE The document describes two methods to transmit multicast IP datagrams over MPEG 2 digital transport streams. It describes the use of Digital Video Broadcasting (DVB) Multi-Protocol Encapsulation (MPE) Datagram Sections and the Advanced Television Systems Committee's (ATSC) Addressable Sections, to encapsulate IP datagrams for subsequent segmentation into fixed length MPEG transport packets. It also describes how the encapsulated data will be included within an MPEG Program in a manner that allows a digital MPEG Decoder to efficiently locate the data PID streams carrying multicast IP content. This document does not cover how the multicast IP data is used in conjunction with the audio / visual content of an MPEG program. 2 REFERENCES 2.1 NORMATIVE REFERENCES [1] Information Technology - Generic coding of moving pictures and associated audio information, Part 6: Extensions for DSM-CC, ISO/IEC 13818-6: 1998/Amd. 1:2000(E) [2] ISO/IEC 8802-1 and 2: "Information technology; Telecommunications and information exchange between systems; Local and metropolitan area networks; Specific requirements; Part 1: Overview of Local Area Network Standards, Part 2: Logical Link Control" [3] Host Extensions for IP Multicasting, IETF RFC 1112, S. Deering, August 1989 [4] Assigned Numbers, IETF RFC 1700, J. Reynolds and J. Postel, October 1994 1 [5] ISO/IEC 13818-1 | ITU-T Rec. H.222.0:2007, Information Technology — Generic coding of moving pictures and associated audio — Part 1: systems. [6] Digital Video Broadcasting (DVB); DVB Specification for data broadcasting, ETSI EN 301 192 v1.4.1 (2004-11) [7] ATSC Data Broadcast Specification, ATSC A/90, December 2000 with Amendment 1 (14 May 2002) and Corrigendum 1 and 2 (1 April 2002) 2.2 INFORMATIVE REFERENCES [8] SMPTE Standard 357M Declarative Data Essence, IP Multicast Encapsulation. [9] Advanced Television Enhancement Forum Specification (ATVEF), Draft Version 1.1r26, updated 02/02/99 2.3 ACRONYMS AND ABBREVIATIONS The following acronyms and abbreviations are used within this specification: ATSC Advanced Television Systems Committee ATVEF Advanced Television Enhancement Forum bslbf bit serial, leftmost bit first CRC Cyclic Redundancy Check DSM-CC Digital Storage Media Command and Control DVB Digital Video Broadcasting FRAGnkj IP fragmentation buffer for fragment identifier j, multicast address k, in elementary stream n. IETF Internet Engineering Task Force IP Internet Protocol IPM IP Multicast IPGRMBnk IP datagram buffer for k-th IP multicast address in the n-th elementary stream MAC Media Access Control MPE Multi-Protocol Encapsulation MPEG Moving Picture Experts Group MTU Maximum Transmission Unit PAT Program Association Table PDU Protocol Data Unit PID Packet Identifier PMT Program Map Table RFC Request for comments 2 SBn Smoothing Buffer for the n-th elementary stream TBn Transport Buffer for the n-th elementary stream TS Transport Stream uimsbf Unsigned Integer, Most Significant Bit First UDP User Datagram Protocol UDPnkji UDP buffer for port i, fragment identifier j, IP multicast address k, in elementary stream 2.4 GLOBAL TERMS The following terms are used throughout this document: bit rate: The rate at which the compressed bit stream is delivered from the channel to the input of a decoder. bps: Bits per second. byte-aligned: A bit in a coded bit stream is byte-aligned if its position is a multiple of 8-bits from the first bit in the stream. CRC: The cyclic redundancy check used to verify the correctness of the data. datagram: A datagram is the fundamental protocol data unit in a packet-oriented data delivery protocol. Typically, a datagram is divided into header and data areas, where the header contains full addressing information (source and destination IP addresses) with each data unit. Datagrams are most often associated with connectionless network and transport layer services. elementary stream (ES): A generic term for one of the coded video, coded audio or other coded bit streams. One elementary stream is carried in a sequence of PES packets with one and only one stream_id. IP Multicast data stream: A collection of IP packets with the same IP Multicast address and port number. kbps: 1,000 bits per second. Maximum Transmission Unit: The largest amount of data that can be transferred in a single unit across a specific physical connection. When using the Internet Protocol, this translates to the largest IP datagram size allowed. Mbps: 1,000,000 bits per second. MPEG-2: Refers to the collection of ISO/IEC standards 13818-1 through 13818-6. Multiprotocol encapsulation: The encapsulation or splitting of datagrams in DSM-CC private sections. 3 packet: A packet is a set of contiguous bytes consisting of a header followed by its payload. packet identifier (PID): A unique integer value used to associate elementary streams of a program in a single or multi-program transport stream. payload: Payload refers to the bytes following the header byte in a packet. program: A collection of Program Elements. Program Elements may be elementary streams. Program Elements need not have any defined time base; those that do have a common time base and are intended for synchronized presentation. program element: A generic term for one of the elementary streams or other data streams that may be included in an ISO/IEC 13818-1 (MPEG-2) Program. The MPEG-2 Transport Stream packets conveying a Program Element are referenced by a unique PID value in the MPEG-2 Program. Transport Stream: Refers to the MPEG-2 Transport Stream syntax for the packetization and multiplexing of video, audio, and data signals for digital broadcast systems. 4 3 MULTICAST IP DATA ENCAPSULATION For IP datagram carriage, this standard defines two encapsulation protocols based on the DVB Multi- protocol encapsulation (MPE) and the ATSC/DSM-CC addressable sections. A given program shall carry IP data using either one of the encapsulation protocols, but not both. Changes to the protocol encapsulation may occur at any time within a program The minor variations between MPE techniques are presented below. The overall transport of IP data over MPEG streams is specified in Section 4, in conjunction with the support of both MPE techniques. 3.1 DVB MPE DATAGRAM This DVB MPE format is compliant with the DSM_CC Sections format for private data (see reference [1]). The table_id field shall be set to 0x3E, which indicates that this is a DSM_CC Section containing private data. However the DVB specification for data broadcasting (see reference [6]) utilizes table_id 0x3E to indicate MPE Datagram Sections. The DVB MPE format listed in Table 1 is included for the reader’s convenience only, and should not be considered a normative part of this specification. Consult reference [6] for the normative definition of the DVB MPE format. Table 1. DVB MPE Datagram Section Format (Informative) Syntax No. of Mnemonic bits datagram_section() { table_id 8 uimsbf section_syntax_indicator 1 bslbf private_indicator 1 bslbf Reserved 2 bslbf section_length 12 uimsbf MAC_address_6 8 uimsbf MAC_address_5 8 uimsbf Reserved 2 bslbf payload_scrambling_control 2 bslbf address_scrambling_control 2 bslbf LLC_SNAP_flag 1 bslbf current_next_indicator 1 bslbf section_number 8 uimsbf last_section_number 8 uimsbf 5 MAC_address_4 8 uimsbf MAC_address_3 8 uimsbf MAC_address_2 8 uimsbf MAC_address_1 8 uimsbf if (LLC_SNAP_flag == "1") { LLC_SNAP() } else { For (j=0;j