ATSC Standard: Scheduler / Studio to Transmitter Link

Size: px
Start display at page:

Download "ATSC Standard: Scheduler / Studio to Transmitter Link"

Transcription

1 ATSC Standard: Scheduler / Studio to Transmitter Link Doc. A/324: January 2018 Advanced Television Systems Committee 1776 K Street, N.W. Washington, D.C i

2 The Advanced Television Systems Committee, Inc., is an international, non-profit organization developing voluntary standards for digital television. The ATSC member organizations represent the broadcast, broadcast equipment, motion picture, Data Consumer electronics, computer, cable, satellite, and semiconductor industries. Specifically, ATSC is working to coordinate television standards among different communications media focusing on digital television, interactive systems, and broadband multimedia communications. ATSC is also developing digital television implementation strategies and presenting educational seminars on the ATSC standards. ATSC was formed in 1982 by the member organizations of the Joint Committee on InterSociety Coordination (JCIC): the Electronic Industries Association (EIA), the Institute of Electrical and Electronic Engineers (IEEE), the National Association of Broadcasters (NAB), the National Cable Telecommunications Association (NCTA), and the Society of Motion Picture and Television Engineers (SMPTE). Currently, there are approximately 150 members representing the broadcast, broadcast equipment, motion picture, Data Consumer electronics, computer, cable, satellite, and semiconductor industries. ATSC Digital TV Standards include digital high definition television (HDTV), standard definition television (SDTV), data broadcasting, multichannel surround-sound audio, and satellite direct-to-home broadcasting. Note: The user's attention is called to the possibility that compliance with this standard may require use of an invention covered by patent rights. By publication of this standard, no position is taken with respect to the validity of this claim or of any patent rights in connection therewith. One or more patent holders have, however, filed a statement regarding the terms on which such patent holder(s) may be willing to grant a license under these rights to individuals or entities desiring to obtain such a license. Details may be obtained from the ATSC Secretary and the patent holder. Version Revision History Date Candidate Standard approved 30 September 2016 Updated CS approved 1 November 2017 Standard approved 5 January 2018 ii

3 Table of Contents 1. SCOPE Introduction and Background Organization 2 2. REFERENCES Normative References 2 3. DEFINITION OF TERMS Compliance Notation Treatment of Syntactic Elements Reserved Elements Acronyms and Abbreviation Terms 6 4. SYSTEM OVERVIEW Features System Architecture System Manager Broadcast Gateway Studio to Transmitter(s) Dataflow STL Operation SFN Operation Central Concepts: DSTP IP Multicast Central Concepts: ALPTP IP Multicast Central Concepts: STLTP STLTP Payload Data IP Multicast and Tunneling Error Control Coding Scheme System Time Domains System Manager Configuration Interface Real-Time Control Interface Transmitter Requirements Overview Carrier and Timing Offset for Co-Channel Interference Mitigation SCHEDULER DESCRIPTION AND NORMATIVE REQUIREMENTS Relationship of Broadcast Gateway and Scheduler to the System Scheduler Functionality Preamble Construction Scheduler Management Protocol Data Source Control Protocol (DSCP) DATA SOURCE TRANSPORT PROTOCOL Overview RTP/UDP/IP Multicast Considerations Multicast Addressing DSTP Design 26 iii

4 6.4 Emergency Alert Wakeup RTP Controls ALP TRANSPORT PROTOCOL (ALPTP) Overview RTP/UDP/IP Multicast Considerations Address Assignments Port Assignments ALPTP Design STL TRANSPORT PROTOCOL Address Assignments Port Assignments Preamble Generator Preamble Data Stream Protocol Timing and Management Generator Timing and Management Data Stream Protocol Bootstrap Emission Timing and Frame Identification PLP Data Stream Baseband Packet Data Stream Protocol Studio to Transmitter Link (STL) Protocol Overview SMPTE ST Features / Resources STL Transmission Protocol Design Example SMPTE FEC Encoding Process RTP Header Field Definitions RTP Encapsulation Example TRANSMITTER OPERATION NORMATIVE REQUIREMENTS Timing Manager Preamble Parser Other Requirements Frequency Accuracy Transmitter Timing Offsets Center-Frequency and Network-Timing Offsets for Co-Channel Interference Mitigation 55 ANNEX A : PHYSICAL LAYER CONTROL A.1 PHysical layer resources 57 A.1.1 Bootstrap Signaling 57 A.1.2 L1-Basic Signaling 57 A.1.3 L1-Detail signaling 59 ANNEX B : NETWORK CONFIGURATION EXAMPLES B.1 Example studio Network topologies 63 ANNEX C : SCHEDULER FUNCTIONAL DESCRIPTION C.1 Overview 66 C.1.1 Scheduler Operation 66 C.1.2 Key Concepts of Scheduler Delivery Metadata 67 C.1.3 Handling Boundary Conditions 71 C.1.4 Delivery Order Within and Across Multiple Sessions 72 C.1.5 Timelines and Deadlines 73 iv

5 C.1.6 Concept and Practice of Analyzed Media Duration 73 C.1.7 Sequence of Required Data and Media Events for Acquisition 75 v

6 Index of Figures and Tables Figure 1.1 In-scope interfaces description. 1 Figure 4.1 High-level overview of system configuration. 10 Figure 4.2 System architecture. 13 Figure 8.1 STL Transmission diagram. 45 Figure 8.2 Example FEC encoding process diagram. 47 Figure 8.3 RTP Encapsulation example diagram. 50 Figure 8.4 Tunneled Packet packing details. 51 Figure 9.1 Example use of carrier and timing offsets for neighboring co-channel stations. 56 Figure B.1.1 Simple ALP encapsulation. 63 Figure B.1.2 Multiple PLP example. 64 Figure B.1.3 Fully redundant routing example. 65 Figure C.1.1 Cascade of real-time functions involved with Scheduler. 66 Figure C.1.2 Example depiction of a high-level Scheduler process flow. 67 Figure C.1.3 Illustration of Earliest and Latest Time with a block interleaver. 68 Figure C.1.4 Illustration of Earliest and Latest Time options relative to Media Segment play. 69 Figure C.1.5 Example of MDE and associated Earliest and Latest Times. 70 Figure C.1.6 Relationship of an MDE in LCT packets to IP encapsulation. 71 Figure C.1.7 Media is sent at early boundary; e.g., Period start. 71 Figure C.1.8 Example of ordered delivery across multiple sessions. 72 Figure C.1.9 Explicit delivery order on PLP with multiple sessions. 73 Figure C.1.10 Analyzed Media Duration. 74 Figure C.1.11 Order of events to optimize linear service acquisition w/wo an APP. 77 Table 5.1 Preamble Parameters and Their Sources 22 Table 5.2 Real Time Control Field Definitions 24 Table 6.1 RTP Header Field Definitions for Data Source Transport Protocol 27 Table 6.2 DSTP RTP Packet payload_type Encoding 27 Table 6.3 Timestamp Field Definitions for Data Source Transport 28 Table 6.4 RTP payload_type Wakeup Control Field Definition 29 Table 6.5 Example Wakeup Bit Controls 29 Table 7.1 RTP Header Field Definitions for ALP Encapsulation 32 Table 7.2 ALP RTP Packet payload_type Encoding 33 Table 7.3 Timestamp Field Definitions for ALP Encapsulation 34 Table 8.1 Preamble Payload 36 Table 8.2 RTP Header Timestamp Field Definitions 36 Table 8.3 Timing and Management Stream Packet Payload 39 Table 8.4: RTP Header Field Definitions for STLTP 48 vi

7 ATSC Standard: Scheduler / Studio to Transmitter Link 1. SCOPE This standard specifies the protocol on the Studio-to-Transmitter Link (STL) from studio-side infrastructure to a Single Frequency Network (SFN) of Transmitters. It defines delivery protocols for ALP Transport. The document also defines possible interfaces among the studio infrastructure, for example the interconnection of the ATSC 3.0 Link Layer Protocol (ALP) and a Broadcast Gateway. This document specifies certain constraints on the scheduling of content and signaling on the Physical Layer. The described scheduling process enables Preamble generation and emission time management. It specifies certain aspects of Transmitter behavior and certain parameters of Transmitter operation. Figure 1.1 depicts an example configuration and connection of these entities. This document provides no specification of broadband delivery of ATSC 3.0 media content. Studio Infrastructure System Manager Configuration Interface Quasi-static Configuration Delivery Metadata Content and Signaling Studio Entities Broadcast Gateway Single Transmitter or SFN of Transmitters Studio Interface STL Interface Figure 1.1 In-scope interfaces description. 1.1 Introduction and Background The ATSC 3.0 system comprises a number of layers that must be connected to one another to construct a complete implementation. Two of the layers that must be interconnected are the Transport Layer and the Physical Layer. In addition, the Physical Layer is designed to be implemented partially at the studio or Data Source and partially at one or more Transmitters. To enable the necessary interoperation of the layers and system segments, appropriate protocols are necessary so that equipment from multiple suppliers can be assembled into a working system. This document defines four protocols, the ATSC Link-Layer Protocol Transport Protocol (ALPTP), the Studio-to-Transmitter Link Transport Protocol (STLTP), the Data Source Transport Protocol (DSTP) and the Data Source Control Protocol (DSCP), for carriage of data through specific portions of the system, as well as a number of operational characteristics of the STL and 1

8 Transmitter(s). Also defined are a Scheduler to manage operation of the Physical Layer subsystems and two protocols used by the Scheduler (1) to receive high-level configuration instructions from a System Manager and (2) to provide real-time bit-rate control information to Data Sources sending content through the Transport Layer for emission by the Physical Layer. 1.2 Organization This document is organized as follows: Section 1 Outlines the scope of this document and provides a general introduction. Section 2 Lists references and applicable documents. Section 3 Provides definitions of terms, acronyms, and abbreviations for this document. Section 4 Provides a system overview Section 5 Defines the Scheduler of Physical Layer resources Section 6 Defines the ALP Transfer Protocol (ALPTP) Section 7 Defines the Studio to Transmitter Link Transfer Protocol (STLTP) Section 8 Describes Transmitter operation Annex A Describes the parameters used for Physical Layer control Annex B Provides Network Configuration examples 2. REFERENCES All referenced documents are subject to revision. Users of this Standard are cautioned that newer editions might or might not be compatible. 2.1 Normative References The following documents, in whole or in part, as referenced in this document, contain specific provisions that are to be followed strictly in order to implement a provision of this Standard. [1] IEEE: Use of the International Systems of Units (SI): The Modern Metric System, Doc. SI 10, Institute of Electrical and Electronics Engineers, New York, N.Y. [2] ATSC: ATSC Standard: System Discovery and Signaling, Doc. A/321:2016, Advanced Television Systems Committee, Washington, D.C., 23 March [3] ATSC: ATSC Standard: Physical Layer Protocol, Doc. A/322:2017, Advanced Television Systems Committee, Washington, D.C., 6 June [4] ATSC: ATSC Standard: Signaling, Delivery, Synchronization, and Error Protection, Doc. A/331:2017, Advanced Television Systems Committee, Washington, D.C., 6 December [5] ATSC: ATSC Standard: Link Layer Protocol, Doc. A/330:2016, Advanced Television Systems Committee, Washington, D.C., 19 September [6] IETF: RTP protocol, RFC 3550, Internet Engineering Task Force. [7] IETF: RTP Profile for Audio and Video Conferences with Minimal Control, RFC 3551, Internet Engineering Task Force. [8] SMPTE: Forward Error Correction for Real-Time Video/Audio Transport Over IP Networks, Doc. SMPTE , Society of Motion Picture and Television Engineers, White Plains, NY, [9] IETF: Generic FEC Payload Format, RFC 5109 (which supersedes IETF RFC 2733), Internet Engineering Task Force. 2

9 [10] SMPTE: Broadcast Exchange Format (BXF) Protocol, Doc. SMPTE :2012, Society of Motion Picture and Television Engineers, White Plains, NY, [11] SMPTE: Media Device Control Protocol (MDCP), Doc. SMPTE :2014, Society of Motion Picture and Television Engineers, White Plains, NY, [12] ITU-T, V.41 Data Communication Over the Telephone Network, Code-Independent Error- Control System, 1993 (or later, if available). [13] IEEE: IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems, Doc. 1588, Institute of Electrical and Electronics Engineers, New York, NY, approved 27 March [14] SMPTE: SMPTE Profile for Use of IEEE-1588 Precision Time Protocol in Professional Broadcast Applications, Doc. SMPTE ST , 2015, Society of Motion Picture and Television Engineers, White Plains, NY, [15] IETF: Network Time Protocol Version 4: Protocol and Algorithms Specification, RFC 5905, D. Mills, J. Martin, J. Burbank, W. Kasch, Internet Engineering Task Force, June [16] W3C Date and Time Formats, Misha Wolf, Charles Wicksteed, August 27, [17] International Atomic Time, International Bureau of Weights and Measures. Retrieved 22 February [18] IETF: RObust Header Compression (ROHC), RFC 3095, Internet Engineering Task Force. [19] IETF: Source-Specific Multicast (SSM), RFC 3569, Internet Engineering Task Force. 3. DEFINITION OF TERMS With respect to definition of terms, abbreviations, and units, the practice of the Institute of Electrical and Electronics Engineers (IEEE) as outlined in the Institute s published standards [1] shall be used. Where an abbreviation is not covered by IEEE practice or industry practice differs from IEEE practice, the abbreviation in question is described in Section 3.3 of this document. 3.1 Compliance Notation This section defines compliance terms used in this document: shall This word indicates specific provisions that are to be followed strictly (no deviation is permitted). shall not This phrase indicates specific provisions that are absolutely prohibited. should This word indicates that a certain course of action is preferred but not necessarily required. should not This phrase means a certain possibility or course of action is undesirable but not prohibited. 3.2 Treatment of Syntactic Elements This document contains symbolic references to syntactic elements used in its various subsystems. These references are typographically distinguished by the use of a different font (e.g., restricted), may contain the underscore character (e.g., sequence_end_code) and may consist of character strings that are not English words (e.g., dynrng) Reserved Elements One or more reserved bits, symbols, fields, or ranges of values (i.e., elements) may be present in this document. These elements are used primarily to enable adding new values to a syntactical 3

10 structure without altering its syntax or causing a problem with backwards compatibility, but they also can be used for other reasons. The ATSC default value for reserved bits is 1. There are no default values for other types of reserved elements. Use of reserved elements, except as defined in other ATSC Standards or by another industry standards-setting body, is not permitted. See individual element semantics for mandatory settings and any additional use constraints. As currently-reserved elements may be assigned values and meanings in future versions of this Standard, receiving devices built to this version are expected to ignore all values appearing in currently-reserved elements to avoid possible future failure to function as intended. 3.3 Acronyms and Abbreviation The following acronyms and abbreviations are used within this document. A/V Audio/Video AEA Advanced Emergency Alert AEAT Advanced Emergency Alert Table ALP ATSC 3.0 Link-Layer Protocol ALPTP ALP Transport Protocol ATSC Advanced Television Systems Committee BBP Baseband Packet BCH Bose, Chaudhuri, Hocquenghem BMFF Base Media File Format BPPS Baseband Packetizer Packet Set BRET Bootstrap Reference Emission Time BS Bootstrap BSID Broadcast Stream ID bslbf bit stream, left-most bit first BSR Baseband Sampling Rate BXF Broadcast exchange Format CAP Common Alerting Protocol CRC Cyclic Redundancy Check CSRC Contributing Source Identifier CTI Convolutional Time Interleaver D/A Digital to Analog DASH Dynamic Adaptive Streaming over HTTP db decibel DDE Data Delivery Event Demux Demultiplexer DSCP Data Source Control Protocol DSS Data Source Signaling DSTP Data Source Transport Protocol EA Emergency Alert ECC Error Correction Coding FEC Forward Error Correction 4

11 FFT Fast Fourier Transform FI Frequency Interleaver FIFO First In First Out Gbps Gigabits per second GI Guard Interval GNSS Global Navigation Satellite System GoP Group of Pictures GPS Global Positioning System HTI Hybrid Time Interleaver IDR Instantaneous Decoding Refresh IEEE Institute of Electrical and Electronics Engineers IETF Internet Engineering Task Force IFFT Inverse Fast Fourier Transform IGMP Internet Group Management Protocol IP Internet Protocol IS Initialization Segment ISO International Organization for Standardization LCT Layered Coding Transport LDM Layered-Division Multiplexing LDPC Low Density Parity Check LLS Low-Level Signaling LMT Layer Mapping Table LSB Least Significant Bit MDCoIP Media Device Control over IP MDE Media Delivery Event MHz Megahertz MIMO Multiple Input Multiple Output MISO Multiple Input Single Output MMT MPEG Media Transport MMTP MPEG Media Transport Protocol MPD Media Presentation Description MPEG Moving Picture Experts Group MSB Most Significant Bit MTU Maximum Transfer Unit Mux Multiplexer NAL Network Adaption Layer NoC Number of Carriers NRT Non Real Time OFDM Orthogonal Frequency Division Multiplexing PAPR Peak to Average Power Ratio PHY Physical Layer PLP Physical Layer Pipe 5

12 PT Payload Type PTP Precision Time Protocol QP Quality Point RAP Random Access Point RDT ROHC-U Description Table RF Radio Frequency RFC Request For Comments ROHC-U Robust Header Compression UDP ROUTE Real-time Object delivery over Unidirectional Transport RTP Real-time Transport Protocol SAP Segment Access Point SBS Subframe Boundary Symbol SCT Server Current Time SFN Single Frequency Network SISO Single Input Single Output SLS Service Layer Signaling SLT Service List Table SMPTE Society of Motion Picture and Television Engineers SSM Source-Specific Multicast SSRC Synchronization Source Identifier STL Studio to-transmitter Link STLTP Studio to-transmitter Link Tunneling Protocol T-RAP Transport-Random Access Point TAI Time Atomic International tcimsbf two s complement integer, msb first TxID Transmitter Identification UDP User Datagram Protocol uimsbf unsigned integer, most significant bit first 3.4 Terms The following terms are used within this document. a-millisecond A time interval approximately equal to one millisecond derived from a binary count of nanoseconds and actually equaling 2 20 nanoseconds, which represents 1,048,576 nanoseconds (i.e., having a Period of milliseconds). Advanced Emergency Alert Provides an emergency notification mechanism in ATSC 3.0 that is capable of forwarding a broad range of emergency data. See [4]. Analyzed Media Duration The shortest Period between times at which data segment boundaries in all data Streams on the inputs of a Scheduler align. Data segment boundaries are indicated to the Scheduler by markers carried in the headers of the structures transporting data to the Scheduler. Baseband Packet A set of payload bits that form the input to an FEC encoding process. There is one Baseband Packet per FEC Frame. Baseband Packetizer Functional block that creates Baseband Packets. 6

13 Bootstrap A defined sequence of symbols that introduces each Physical Layer frame and provides a universal entry point into a digital Transmission signal. Each Bootstrap carries a value that serves as an indicator of the format of an immediately following Preamble symbol. Bootstrap Reference Emission Time A time value indicating the instant at which the leading edge of the first symbol of a Bootstrap is to be emitted from the transmitting antenna(s), absent any timing offsets of individual Transmitter(s) in a Network. Broadcast Gateway A Broadcast Gateway converts source file objects, for example media, system information, and other opaque files, into SFN baseband description for distribution to Transmitters. Center Frequency The point in the spectrum of a Physical Layer signal at which equal numbers of carriers are positioned both higher and lower in the spectrum. Data Consumer A device that receives a formatted stream of data and further processes and/or distributes it. Data Producer A device or process that generates a formatted stream of data. Data Source An origination point for data to be transmitted as content by the Physical Layer. Data Source Signaling Information sent from a Data Source to downstream functions to identify specific characteristics of the content of certain packets within the data Stream to provide interlayer communications while avoiding layer violations in the system. Typically, Data Source Signaling information is carried in RTP headers in locations defined in this standard. Earliest Time A time value that accompanies data sent as input to a Broadcast Gateway to indicate the first instant, as determined using TAI, at which the first byte of related data, including all wrappers and encapsulating protocols, may start emission on the Physical Layer. Emission Wakeup Field The two Wakeup Bits in a Bootstrap when treated together as a field. Exciter An element of a Transmitter comprising data processing and signal processing functions including at least framing, error correction coding, waveform generation, modulation, and upconversion to the output RF channel frequency. Latest Time A time value that accompanies data sent as input to a Broadcast Gateway to indicate the last instant, as determined using TAI, by which the last byte of related data, including all wrappers and encapsulating protocols, must complete emission on the Physical Layer. Media Segment A portion of a data Stream that is treated as a unit by a Scheduler for purposes of analysis and Transmission. Multiplex A group of services that are transmitted together over a Network. Network A group of Transmitters delivering the same Multiplex. Packet Set A group of packets carrying segments of a large data structure that has been segmented for the purpose of carriage across a transport connection that is not configured to carry the large data structure. Packetizer A process that treats a collection of data (e.g., a portion of a data Stream) by breaking it into segments and wrapping the segments in a header structure, thereby creating packets for Transmission / delivery. Period A duration of time. Physical Layer A functional protocol that defines the framing, resource allocation, and waveforms of signals emitted for delivery of data and content to receivers. Preamble The portion of a Physical Layer frame that carries L1 signaling data (see [3]) for the frame. 7

14 Preamble Generator A function within a Broadcast Gateway that accepts instructions from a Scheduler, creates and formats Preamble Packets according to those instructions, and releases the Preamble Packets in the form of a Preamble Stream that can be multiplexed with other data Streams for delivery to the Transmitter(s) under control of the Broadcast Gateway. Preamble Packet A packet of data that provides a complete set of information necessary for Transmission following the Bootstrap of a Physical Layer frame to instruct receivers regarding the necessary receiver data processing to permit recovery of the data contained within the frame. The packet also serves to instruct Transmitters with respect to the configuration of the Physical Layer frame that is to be emitted so that the Exciter data processing for the frame can be properly configured. Preamble Parser A function within an Exciter that receives Preamble Streams, extracts from them Preamble Payload data, and stores the Preamble Payload data until the time for its emission as part of a broadcast signal. The Preamble Parser then makes the Preamble Payload data available to the Exciter control system for use in configuring the data- and waveformprocessing of the Exciter, and outputs individual Preamble Packets at the correct times for their inclusion in the emission of the Physical Layer frames the configurations of which they define. Preamble Payload The L1 data carried in a Physical Layer frame to define the structure of the frame and to specify the modulation, coding, and other parameters used in delivery of the frame. Preamble Stream A data Stream carrying Preamble Packets, comparable to the data Streams carrying data for PLPs and for Timing and Management functionality, that can be multiplexed with other Streams and delivered as a combined data Stream that is tunneled through the STLTP. reserved Set aside for future use by a Standard. Scheduler A Studio side-function that allocates physical capacity to data Streams based on instructions from the System Manager combined with the capabilities of the specific system. Single Frequency Network Multiple Transmitters in proximity to one another radiating the same waveform and sharing a frequency. STL Interface The STL Interface is the origin point for the Studio-to-Transmitter Link Tunneling Protocol (STLTP). Stream A sequential set of packets carrying data from a Data Source to one or more Data Consumers. Studio Interface The Studio Interface is the termination point for the ALP Transport Protocol (ALPTP) and/or the Data Source Transport Protocol (DSTP). System Manager The System Manager is a conceptual subsystem outside the Transport and Physical Layers and responsible for coordinating the functions of at least those two layers and the static and quasi-static configurations of various system aspects, for example definition of PLPs or assignment of IP addresses and port numbers to Services. The System Manager does not manage real-time traffic directly. Timing and Management Data A collection of data sent from a Timing and Management Generator in a Broadcast Gateway to the Transmitter(s) under control of the Broadcast Gateway for purposes of controlling the emission times of Physical Layer frames, establishing various Transmitter configurations, and setting various Transmitter parameters, independent of the configurations of the frames and waveforms of the emitted signal itself. 8

15 Timing and Management Generator A function within a Broadcast Gateway that accepts instructions from a Scheduler, creates and formats Timing and Management Data according to those instructions, and releases the Timing and Management Data in the form of a Timing and Management Stream that can be multiplexed with other data Streams for delivery to the Transmitter(s) under control of the Broadcast Gateway. Timing and Management Stream A data Stream carrying Timing and Management Data, comparable to the data Streams carrying data for PLPs and for Preambles, that can be multiplexed with other Streams and delivered as a combined data Stream that is tunneled through the STLTP. Transmission The signal that is emitted by a Transmitter and the synchronized signal that is emitted by all Transmitters in a Network. Transmitter An individual emitter at a specific geographic location on a specific frequency. Transport Layer A functional protocol that defines the formatting of data that will be delivered to receivers after its recovery from the formatting required for its physical delivery by the Physical Layer. It provides logical communication between application processes running on different hosts within a layered architecture of protocols and other network components. Tunnel Packet A packet that carries in its payload the contents of one or more multiplexed packet Streams, including the corresponding headers and any other structural elements, i.e., a packet in the outer layer of a packet Tunneling system. Tunneled Data Stream A Stream of multiplexed Tunneled Packets carried within an STLTP encapsulation for ECC processing. Tunneled Packet A packet within a multiplexed group of packet Streams carried in a Tunnel Packet, i.e., a packet in the inner layer of a packet Tunneling system. Tunneling A process by which a group of parallel and independent packet Streams are carried within a single packet Stream so that they can be processed, transported, and otherwise treated as a single Stream entity. Tuple The combination of Internet Protocol (IP) addresses and port numbers. Wakeup Alert The occurrence of an AEA message requesting the setting of a non-zero value for the Emission Wakeup Field. Wakeup Bits The bits in Bootstrap Symbols 1 and 2 that are used to indicate to receivers that there is high-priority emergency information included in the broadcast. See [4]. 4. SYSTEM OVERVIEW 4.1 Features The STL subsystem exists between the Transport Layer, which creates ATSC 3.0 Link-Layer Protocol (ALP) packets, and the Physical Layer, which formats Streams of ALP packets for Transmission in particular Physical Layer Pipes (PLPs) in an emission configuration specified continuously in detail by a Scheduler. Documents [4] and [5] define the ALP and other Transport Layer protocols. Documents [2] and [3] define the Physical Layer protocols. Figure 4.1 shows a high-level overview of the system configuration with applicable document numbers for the adjoining subsystems not defined herein. As depicted in the figure, data to be transmitted enters a Broadcast Gateway using either ALPTP (defined herein) or DSTP (defined herein) in the lower left of the diagram. Other inputs to the Broadcast Gateway are instructions from a System Manager. A Scheduler internal to the Broadcast Gateway controls the pre-processing functions 9

16 that occur before delivery of the data and various control information to the Transmitter(s). Delivery of the combined data and instructions to the Transmitter(s) occurs in the lower right of the figure using STLTP (defined herein) with optional ECC applied. At the Transmitter across the top of the figure, the data and instructions from the studio are separated, buffered, and used to control the Transmitter as well as to construct the waveform to be emitted to receivers. B U F F E R Timing Manager B U F F E R ATSC A/321 and A/322 Physical Layer Preamble Parser Input Formatting Coded Modulation Framing/ Structure Waveform Generation Buffer System Manager Broadcast Gateway w/internal ALP Gen. Configuration Mgr /Scheduler Broadcast Gateway ATSC A/330 ALP and A/331 Signaling, etc. Transport Layer Data Sources ALPs IP UDP RTP ALPs PLPs Preamble Information Timing & Mgt Information IP UDP RTP STL Link IP/UDP/RTP IP UDP RTP ALP Generation ALPTP Formatting ALPTP Receiver STL Pre-Processor STLTP Formatting and ECC Encoding STL Xmtr Microwave/Satellite/Fiber STL Rcvr ECC Decoding and STLTP Demultiplexing DSTP ALPTP STLTP STLTP Figure 4.1 High-level overview of system configuration. There is a one-to-one correspondence between individual Streams of ALP packets and individual PLPs. To prepare ALP packets for Transmission, in the Broadcast Gateway, the ALP packets are encapsulated in Baseband Packets (BBPs), which have defined sizes that are determined by a parameter (Kpayload) related to the specific characteristics of the particular PLP(s) in which they will be carried. The sizes of the BBPs in a given Stream are set to ensure that the assigned capacity of the related PLP in a frame is filled by the BBPs derived from an associated ALP packet Stream. ALP packets either are segmented or are concatenated so that they fill the allocated space in the BBPs carrying them as completely as possible without overflowing the available space. To manage the flow of data through the system, several buffers are required to hold data for purposes of time alignment of data emission. Buffering also is required in certain instances to enable information to be obtained from a data Stream and used to control particular functionality of the system before the corresponding data is processed further. Two specific instances of such buffering exist in the system. The first buffer inserts at least one Physical Layer frame of delay in the STL Pre-Processor to enable sending Preamble information for a given Physical Layer frame 10

17 to Transmitters prior to arrival of the data to fill that Physical Layer frame. The second buffer accommodates a delay of up to one second to enable synchronization of frame emission timing in the Physical Layer when the delivery delay to each of the Transmitters in a Network is different. Maintaining the one-to-one correspondence between particular ALP packet Streams and their assigned PLPs through the system requires a method for identifying both the ALP and PLP data Streams. Since the ATSC 3.0 system works in an Internet Protocol (IP) environment, IP tools and resources are used for Stream identification purposes. Specifically, RTP/UDP/IP multicast stacks are used in both of the ALPTP and STLTP structures, with specific UDP port numbers assigned to particular PLP identifiers and used in both protocols. Thus, for example, an ALP packet Stream designated to be carried in PLP 07 will be carried in an ALPTP Stream with a UDP port value ending in 07, and the Baseband Packet Stream derived from that ALP Stream and to be carried in PLP 07 will be carried within an STLTP Stream with a UDP port value also ending in 07. When the emission operates in Single-PLP mode, all of the data to be transmitted will be carried in only a single ALP Stream, and all of that data will be transmitted with the same level of robustness. When multiple PLP Streams are used, each can have a different tradeoff of data rate versus robustness, and data Streams can be assigned to appropriate combinations by the System Manager. If the ALP Stream(s) is (are) created within the same equipment that provides the Broadcast Gateway functionality, use of ALPTP may not be necessary. Figure 4.1 shows a single path carrying the ALP packet Stream(s) and then the PLP packet Stream(s) on its (their) way(s) from the ALP generator(s) to the Transmitter(s). In reality, if there are multiple Streams at any point in the system, the processing for each of the ALP packet Streams and/or Baseband Packet (BBP) Streams is applied separately to each of the Streams destined for a different PLP. This separation of processes is diagrammed using parallel paths throughout the remainder of this document, starting with the detailed examination of Figure 4.2. To manage all of the characteristics of the emission and to coordinate all of the elements of the Physical Layer subsystem with respect to their parameter settings and times of operation, a Scheduler function is included in the Broadcast Gateway. The Scheduler manages the operation of a buffer for each ALP Stream, controls the generation of BBPs destined for each PLP, and creates the signaling data transmitted in the Preamble as well as signaling data that controls creation of Bootstrap signals by the Transmitter(s) and the timing of their emission. To perform its functions, the Scheduler communicates with a System Manager to receive instructions and with the source(s) of the ALP packets both to receive necessary information and to control the rate(s) of their data delivery. One form of data relationship that the Scheduler must establish is signaling, in the Preamble of any given Physical Layer frame, the presence of Low-Level Signaling (LLS) data in specific PLPs within that frame. To enable the Scheduler to meet that requirement, upstream ALP generators in turn are required to signal to the Scheduler the presence of LLS data in specific ALP packets. When ALPTP is used (i.e., when ALP generators and the Scheduler are in separate equipment units), such signaling takes place in the RTP header that is part of the RTP/UDP/IP multicast stack that comprises ALPTP. This method avoids the layer violation that would occur if the Scheduler had to determine the presence of LLS by inspecting the content of the ALP packets and also covers cases in which the content of the ALP packets is not IP packets. One of the principal functions of the Scheduler is to generate Preamble data for the Transmitter(s) that it controls. Conceptually, as shown in Figure 4.2, the Preamble generation function is assigned to a Preamble Generator, which is part of the Broadcast Gateway. The Preamble Generator outputs the data that is to be transmitted to receivers to allow their 11

18 configurations to match the processes and parameters that will be used in Transmission. As the Transmitter(s) process the Preamble data for emission to receivers, the Preamble data also will be used by the Transmitter(s) to set up the Input Formatting, Coded Modulation, Framing/Structure, and Waveform Generation so that the emitted waveform will match what receivers will be instructed by the Preamble to receive. The exact format for the Preamble data is specified in [3]. Similarly, the Scheduler must control the generation and emission of Bootstrap waveforms by the Transmitter(s). To accomplish this, a data structure, similar to the Preamble, is defined in this document to carry Timing and Management data to the Transmitters. Conceptually, as shown in Figure 4.2, a Timing and Management Generator is included in the Broadcast Gateway and provides the function under control of the Scheduler. BBP data is carried across the STL in an RTP/UDP/IP multicast Stream for each PLP. These Streams are multiplexed into a single RTP/UDP/IP multicast Stream for each broadcast emission to enable reliable delivery to the Transmitter(s) of correctly identified and ordered BBPs. Conceptually, the BBP data Streams, as well as the Preamble Stream and the Timing and Management Stream, are encapsulated as an inner Stream carried through the outer Stream formed by the STLTP. Both inner and outer Streams use IP multicast. The inner Stream provides addressing of BBP Streams to their respective PLPs through use of UDP port numbers. The outer protocol, STLTP, provides maintenance of packet order through use of RTP header packet sequence numbering. The STLTP also enables use of (SMPTE ) ECC to maintain reliability of Stream delivery under conditions of imperfectly reliable STL Networks. At the Transmitter(s), an input buffer is used for each PLP to hold BBP data until it is needed for Transmission. There also are FIFO buffers for the Preamble Stream and the Timing and Management Stream. The Preamble Stream processing includes a Preamble Parser that collects all of the configuration information for the next and possibly several upcoming Physical Layer frames to use in configuring the Transmitter data processing for those frames. Preamble data is scheduled to arrive at the Transmitter input at least one full Physical Layer frame Period prior to the first byte of the associated payload to provide time for the Transmitter data processing to be configured properly. Preamble data also can be sent multiple times in advance to enable acquisition of the data with improved reliability. The same considerations also are applicable to the Timing and Management Data; i.e., it is scheduled to arrive at the Transmitter input at least one Physical Layer frame Period prior to the first byte of the associated payload (+processing delay) it describes, and it can be sent multiple times to enable improved reliability of its acquisition. 4.2 System Architecture The Studio to Transmitter Link (STL) interface is typically located between the Baseband Packetizer and the Forward Error Correction (FEC) block. There only needs to be one Scheduler and one Baseband Packetizer per RF emission. Multiplexing of multiple Services among stations sharing one RF emission can be accommodated on the input side of the Scheduler. 12

19 GNSS Time B U F F E R Timing Manager B U F F E R Preamble Parser TAD Legend ALP Packets Baseband Packets Preamble Data Packets Timing Data Packets Timing Data Preamble Data Timing Instructions Configuration Instructions Emission-Formatted Preamble Data PLPs PLPs PLPs PLPs PLPs PLPs PLPs PLPs PHY Fr PHY Fr PHY Fr PHY Fr PHY Fr PHY Fr PHY Fr PHY Fr 1sec Network Comp. Buffers Scrambler Bit Int l FEC Mapper LDM MIMO Time Int l OFDM Framer/ Preamble Inserter Freq Int l Pilot/ Tone Reserve MISO IFFT PAPR GI Bootstrap/ Spectrum Shaping D/A From/To System Manager (BXF) To/From Data Sources (MDCoIP) Broadcast Gateway w/internal ALP Gen Configuration Mgr LLS Ind. Preamble Generator Broadcast Gateway w/external ALP Gen Timing and Mgt Generator EAS Trig. IP UDP RTP Data Source Data Source Data Source Data Source ALPs IP UDP RTP Scheduler ALPs ALPs 1 Phy Frame Delay ( 5secs) PLPs PLPs IP UDP RTP IP UDP RTP STL Link IP/UDP/RTP IP UDP RTP IP UDP RTP ALP Encapsulation ALP Mux ALP Demux ALP Buffers Baseband Packetizers IP Packetizers PLP Mux SMPTE ST ECC Encoder STL Xmtr Microwave/Satellite/Fiber STL Rcvr SMPTE ST ECC Decoder PLP Demux IP (ROUTE/MMT), TS, Generic Data In DSTP Payloads ALP Payload (ALPTP) STL Payload (STLTP) STL Payload (STLTP) Figure 4.2 System architecture. Figure 4.2 shows a possible system architecture; other configurations are possible. When considering system configurations, data rates and interfaces between functional blocks must be taken into account in developing practical implementations System Manager Configuration aspects of the overall system are controlled by a single entity called a System Manager, which is represented in Figure 4.2 only as a connection to the Configuration Manager in the Broadcast Gateway. A System Manager can be anything from a web-page based setup screen with manual data entry to a fully automated system; its scope is control of an overall facility or system. The System Manager provides high-level configuration parameters for numerous system functions. The System Manager controls static or quasi-static configurations of the Transmission chain. It controls the Physical Layer configuration with respect to how many PLPs operate and the configurations of the individual PLPs, the Services supplied on those PLPs, and the delivery sessions that support the Services that run in the PLPs. A System Manager can establish a predetermined schedule for system re-configuration, sending instructions to various system devices and subsystems for delayed execution at specified times. All configuration parameters sent by a System Manager to a Configuration Manager are derived from the Preamble parameter set described in [3] Section 9 and listed in Table 5.1 herein. In response, the Configuration Manager provides feedback of Physical Layer capabilities or structure details of selected Physical Layer frame types. Instructions to the Configuration Manager for these changes in configuration must be sufficiently in advance of the time of emission change. The required minimum advance notice of configuration change time depends on the total reconfiguration latency of the combination of the Configuration Manager and the Scheduler. Further descriptions of Scheduler functionality appear in Sections and

20 Data Sources feeding the Broadcast Gateway are identified to it by the System Manager using IP addresses and port numbers, with one IP address and port combination (i.e., one Tuple) associated with each Data Source or ALP Stream. These Data Sources also can have separate control IP addresses, in which case the IP addresses of the control connections are indicated to the Broadcast Gateway by the System Manager at most one per ALP Stream. The operation of the Data Source control interface and the messages that cross it are described in overview in Section 4.8 and in detail in Section 5.5. For each input Data Source or ALP Stream, the System Manager assigns a specific PLP number, which is related to the UDP port address used, as described in Section Broadcast Gateway A Broadcast Gateway is an equipment item that incorporates a number of the conceptual functions necessary in processing data prior to its delivery over an STL to one or more Transmitters. Broadcast Gateways can be implemented in two primary ways, differing primarily in the location of one processing function and the type of interface used to deliver data Streams for Transmission by the Physical Layer subsystem. Both configurations of a Broadcast Gateway are shown in Figure 4.2. In the Broadcast Gateway outlined with a solid-line, an external function, upstream in the system, generates ATSC 3.0 Link-layer Protocol (ALP) packets [5] by encapsulating the data that is to be transmitted in specific PLPs. With external generation of ALP packets, those packets are delivered to the Broadcast Gateway using an ALP Transport Protocol (ALPTP) defined herein, and metadata associated with particular ALP packets and necessary for their Transmission is carried with the packets in their ALPTP headers. In the Broadcast Gateway outlined by the combination of the solid and dashed lines, a function within the Broadcast Gateway performs the ALP packet generation, and a slightly different Data Source Transport Protocol (DSTP) is used to carry both content data and related metadata, the latter of which again is carried in the headers of the DSTP packets Configuration Manager The conceptual Configuration Manager within a Broadcast Gateway provides a configuration resource to the System Manager that can accept general waveform structure requirements and from them develop a complete description of the frame structure and waveform that is to be emitted by the Physical Layer. It can inform the System Manager of the capabilities of the system and can provide trial frame structure and waveform details to the System Manager for approval. It also can accept from the System Manager an operational schedule based on use of predefined configurations that the Configuration Manager and the System Manager both have accepted and stored for later use with a naming convention for reference to the predefined configurations. The Configuration Manager provides instructions to the Scheduler, at appropriate times, with respect to the detailed frame structure and waveform that are to be adopted starting at a particular instant and continuing until further instructions are given Scheduler The Scheduler within a Broadcast Gateway receives an input of configuration instructions from the Configuration Manager and determines both the frame structure and timing and the waveform details for the next and subsequent Physical Layer frames. The Scheduler must look ahead in time in developing the details of a sequence of Physical Layer frames since instructions about the structures and emission timing of future frames must be sent to Transmitters in advance of arrival of the content data to be transmitted in them. The Scheduler also manages a demultiplexer and a buffer that process data arriving in the form of ALP packets or DSTP packets and any associated 14

21 metadata in the packet headers. DSTP-delivered data will be encapsulated into ALP packets before reaching the Scheduler, and its associated metadata will be passed to the Scheduler in much the same way as metadata arriving in ALPTP packet headers. The metadata arriving with the content data is needed by the Scheduler for making a number of decisions. Included are decisions to send Wake-Up bits in the emitted Bootstrap of a Physical Layer frame and to signal the presence of various forms of table data (e.g., LLS) in a frame and in a particular PLP within that frame. The Scheduler also controls the Baseband Packetizer blocks, causing them to create Baseband Packets of one of two available sizes according to the characteristics of the specific Physical Layer Pipes (PLPs) into which their Baseband Packets will be sent. Adjuncts to the Scheduler are a Preamble Generator and a Timing and Management Generator. The Scheduler determines the data to be sent to the Transmitter(s) for inclusion in the transmitted Preamble, and it similarly determines the data to be sent to the Transmitter(s) for control of their operation. The Preamble Generator uses instructions from the Scheduler to form and format a packet Stream to be sent in parallel with the PLP packet Streams to the Transmitter(s) for use by the Transmitters in configuring their operation and for emission to receivers to announce the signal configuration to be received and demodulated. The Timing and Management Generator similarly uses instructions from the Scheduler to form and format a packet Stream to be sent in parallel with the PLP packet Streams to the Transmitter(s) for control of their operations. Unlike the Preamble Stream, the Timing and Management Stream is not broadcast but rather is consumed by the Transmitter(s) where it is used to control the timing of its (their) emissions and other functions either as a group or individually by Transmitter Studio to Transmitter(s) Dataflow The studio to Transmitter link (STL) may operate on any of fiber, satellite or microwave links. STL redundancy is possible, but is out of scope for this document. Internet Protocol (IP) is supported on all link types. Because of its exposure on any of the delivery means to potential security breaches, it is important that the data traversing the STL be protected by a security mechanism. Work is under way on such a system within ATSC STL Operation Broadcasters have a need to send studio-generated data to their Transmitters. Usually those Transmitters are not co-located at the studio. An STL Interface from the studio to the Transmitter(s) is needed. Requirements for such an interface include: 1) Support for Real-Time Protocol / User Datagram Protocol / Internet Protocol (RTP/UDP/IP) IPv4 and addressing 2) Encapsulation of data for the link 3) Providing a synchronization method to TAI for both data and control 4) Providing signaling of the Transmitter time synchronization for data and control 5) Having measurable maximum latency to allow the emission times to be correct 6) Allowing for redundancy of the delivery channel SFN Operation Certain specifications in this standard enable Single Frequency Network (SFN) operations, and the protocol for data carriage from the studio to the Transmitter(s) has the capability to support delivery of certain control data individually to each Transmitter in an SFN. Specifically included are the following specifications and capabilities: 15

ATSC Standard: Link-Layer Protocol (A/330)

ATSC Standard: Link-Layer Protocol (A/330) ATSC Standard: Link-Layer Protocol (A/330) Doc. A/330:2016 19 September 2016 Advanced Television Systems Committee 1776 K Street, N.W. Washington, D.C. 20006 202-872-9160 i The Advanced Television Systems

More information

ATSC Candidate Standard: A/341 Amendment

ATSC Candidate Standard: A/341 Amendment ATSC Candidate Standard: A/341 Amendment 2094-40 Doc. S34-301r2 20 February 2018 Advanced Television Systems Committee 1776 K Street, N.W. Washington, D.C. 20006 202-872-9160 i The Advanced Television

More information

ATSC Standard: A/342 Part 2, AC-4 System

ATSC Standard: A/342 Part 2, AC-4 System ATSC Standard: A/342 Part 2, AC-4 System Doc. A/342-2:2017 23 February 2017 Advanced Television Systems Committee 1776 K Street, N.W. Washington, D.C. 20006 202-872-9160 i The Advanced Television Systems

More information

ATSC Standard: A/342 Part 3, MPEG-H System

ATSC Standard: A/342 Part 3, MPEG-H System ATSC Standard: A/342 Part 3, MPEG-H System Doc. A/342-3:2017 3 March 2017 Advanced Television Systems Committee 1776 K Street, N.W. Washington, D.C. 20006 202-872-9160 i The Advanced Television Systems

More information

ATSC Candidate Standard: A/342 Part 3, MPEG-H System

ATSC Candidate Standard: A/342 Part 3, MPEG-H System ATSC Candidate Standard: A/342 Part 3, MPEG-H System Doc. S34-189r3 3 May 2016 Advanced Television Systems Committee 1776 K Street, N.W. Washington, D.C. 20006 202-872-9160 i The Advanced Television Systems

More information

ATSC Standard: Captions and Subtitles (A/343)

ATSC Standard: Captions and Subtitles (A/343) ATSC Standard: Captions and Subtitles (A/343) Doc. A/343:2017 18 September 2017 Advanced Television Systems Committee 1776 K Street, N.W. Washington, D.C. 20006 202-872-9160 i The Advanced Television Systems

More information

ATSC Candidate Standard: A/341 Amendment:

ATSC Candidate Standard: A/341 Amendment: ATSC Candidate Standard: A/341 Amendment: 2094-10 Doc. S34-262r1 18 May 2017 Advanced Television Systems Committee 1776 K Street, N.W. Washington, D.C. 20006 202-872-9160 i The Advanced Television Systems

More information

ATSC Standard: Signaling, Delivery, Synchronization, and Error Protection

ATSC Standard: Signaling, Delivery, Synchronization, and Error Protection ATSC Standard: Signaling, Delivery, Synchronization, and Error Protection Doc. A/331:2017 6 December 2017 Advanced Television Systems Committee 1776 K Street, N.W. Washington, D.C. 20006 202-872-9160 i

More information

ATSC Mobile DTV Standard: A/153 Part 3, Service Multiplex and Transport Subsystem Characteristics

ATSC Mobile DTV Standard: A/153 Part 3, Service Multiplex and Transport Subsystem Characteristics ATSC Mobile DTV Standard: A/153 Part 3, Service Multiplex and Transport Subsystem Characteristics Doc. A/153 Part 3:2013 29 October 2013 Advanced Television Systems Committee 1776 K Street, N.W. Washington,

More information

ATSC Standard: Content Recovery in Redistribution Scenarios

ATSC Standard: Content Recovery in Redistribution Scenarios ATSC Standard: Content Recovery in Redistribution Scenarios Doc. A/336:2018 24 April 2018 Advanced Television Systems Committee 1776 K Street, N.W. Washington, D.C. 20006 202-872-9160 i The Advanced Television

More information

AMERICAN NATIONAL STANDARD

AMERICAN NATIONAL STANDARD Digital Video Subcommittee AMERICAN NATIONAL STANDARD Methods for Isochronous Data Services Transport NOTICE The Society of Cable Telecommunications Engineers (SCTE) / International Society of Broadband

More information

ITU-T J.288. Encapsulation of type length value (TLV) packet for cable transmission systems

ITU-T J.288. Encapsulation of type length value (TLV) packet for cable transmission systems I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n ITU-T J.288 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (03/2016) SERIES J: CABLE NETWORKS AND TRANSMISSION OF TELEVISION, SOUND

More information

SERIES J: CABLE NETWORKS AND TRANSMISSION OF TELEVISION, SOUND PROGRAMME AND OTHER MULTIMEDIA SIGNALS Digital transmission of television signals

SERIES J: CABLE NETWORKS AND TRANSMISSION OF TELEVISION, SOUND PROGRAMME AND OTHER MULTIMEDIA SIGNALS Digital transmission of television signals International Telecommunication Union ITU-T J.281 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (03/2005) SERIES J: CABLE NETWORKS AND TRANSMISSION OF TELEVISION, SOUND PROGRAMME AND OTHER MULTIMEDIA

More information

ATSC Standard: Service Usage Reporting (A/333)

ATSC Standard: Service Usage Reporting (A/333) ATSC Standard: Service Usage Reporting (A/333) Doc. A/333:2017 4 January 2017 Advanced Television Systems Committee 1776 K Street, N.W. Washington, D.C. 20006 202-872-9160 i The Advanced Television Systems

More information

ATSC Candidate Standard: A/342 Part 2, AC-4 System

ATSC Candidate Standard: A/342 Part 2, AC-4 System ATSC Candidate Standard: A/342 Part 2, AC-4 System Doc. S34-188r3 3 May 2016 Advanced Television Systems Committee 1776 K Street, N.W. Washington, D.C. 20006 202-872-9160 i The Advanced Television Systems

More information

ANSI/SCTE

ANSI/SCTE Digital Video Subcommittee AMERICAN NATIONAL STANDARD ANSI/SCTE 243-3 2017 Next Generation Audio Carriage Constraints for Cable Systems: Part 3 MPEG-H Audio Carriage Constraints NOTICE The Society of Cable

More information

ENGINEERING COMMITTEE Digital Video Subcommittee

ENGINEERING COMMITTEE Digital Video Subcommittee ENGINEERING COMMITTEE Digital Video Subcommittee SCTE 164 2010 Emergency Alert Metadata Descriptor NOTICE The Society of Cable Telecommunications Engineers (SCTE) Standards are intended to serve the public

More information

ELEC 691X/498X Broadcast Signal Transmission Winter 2018

ELEC 691X/498X Broadcast Signal Transmission Winter 2018 ELEC 691X/498X Broadcast Signal Transmission Winter 2018 Instructor: DR. Reza Soleymani, Office: EV 5.125, Telephone: 848 2424 ext.: 4103. Office Hours: Wednesday, Thursday, 14:00 15:00 Slide 1 In this

More information

ANSI/SCTE

ANSI/SCTE ENGINEERING COMMITTEE Digital Video Subcommittee AMERICAN NATIONAL STANDARD ANSI/SCTE 194-2 2013 DTS-HD AUDIO SYSTEM Part 2: Constraints for Carriage over MPEG-2 Transport NOTICE The Society of Cable Telecommunications

More information

Triveni Digital Inc. MPEG Technology Series. MPEG 101 (MPEG 2 with a dash of MPEG 4 thrown in) Copyright 2011 Triveni Digital, Inc.

Triveni Digital Inc. MPEG Technology Series. MPEG 101 (MPEG 2 with a dash of MPEG 4 thrown in) Copyright 2011 Triveni Digital, Inc. Triveni Digital Inc. MPEG Technology Series MPEG 101 (MPEG 2 with a dash of MPEG 4 thrown in) An LG Electronics Company Copyright 2011 Triveni Digital, Inc. Course Sections Encoding Basics Transport Stream

More information

MISB EG Motion Imagery Standards Board Engineering Guideline. 24 April Delivery of Low Bandwidth Motion Imagery. 1 Scope.

MISB EG Motion Imagery Standards Board Engineering Guideline. 24 April Delivery of Low Bandwidth Motion Imagery. 1 Scope. Motion Imagery Standards Board Engineering Guideline Delivery of Low Bandwidth Motion Imagery MISB EG 0803 24 April 2008 1 Scope This Motion Imagery Standards Board (MISB) Engineering Guideline (EG) provides

More information

ATSC Candidate Standard: Application Signaling (A/337)

ATSC Candidate Standard: Application Signaling (A/337) ATSC Candidate Standard: Application Signaling (A/337) Doc. S33-215r2 19 April 2017 Advanced Television Systems Committee 1776 K Street, N.W. Washington, D.C. 20006 202-872-9160 i The Advanced Television

More information

PROXIMITY-1 SPACE LINK PROTOCOL CODING AND SYNCHRONIZATION SUBLAYER

PROXIMITY-1 SPACE LINK PROTOCOL CODING AND SYNCHRONIZATION SUBLAYER Draft Recommendation for Space Data System Standards PROXIMITY-1 SPACE LINK PROTOCOL CODING AND SYNCHRONIZATION SUBLAYER DRAFT RECOMMENDED STANDARD CCSDS 211.2-P-2.1 PINK SHEETS March 2019 Draft Recommendation

More information

I Voice Trunking Format over MPLS Implementation Agreement. MPLS /Frame Relay Alliance 5.0.0

I Voice Trunking Format over MPLS Implementation Agreement. MPLS /Frame Relay Alliance 5.0.0 I.366.2 Voice Trunking Format over MPLS Implementation Agreement MPLS /Frame Relay Alliance 5.0.0 MPLS /Frame Relay Alliance Technical Committee August 2003 I.366.2 Voice Trunking Format over MPLS Implementation

More information

IP Video Network Gateway Solutions

IP Video Network Gateway Solutions IP Video Network Gateway Solutions INTRODUCTION The broadcast systems of today exist in two separate and largely disconnected worlds: a network-based world where audio/video information is stored and passed

More information

4 rd class Department of Network College of IT- University of Babylon

4 rd class Department of Network College of IT- University of Babylon 1. INTRODUCTION We can divide audio and video services into three broad categories: streaming stored audio/video, streaming live audio/video, and interactive audio/video. Streaming means a user can listen

More information

RECOMMENDATION ITU-R BS.776 * Format for user data channel of the digital audio interface **

RECOMMENDATION ITU-R BS.776 * Format for user data channel of the digital audio interface ** Rec. ITU-R BS.776 1 RECOMMENDATION ITU-R BS.776 * Format for user data channel of the digital audio interface ** The ITU Radiocommunication Assembly considering (1992) a) that there is a real need for

More information

RECOMMENDATION ITU-R BT.1720 *

RECOMMENDATION ITU-R BT.1720 * Rec. ITU-R BT.1720 1 RECOMMENDATION ITU-R BT.1720 * Quality of service ranking and measurement methods for digital video broadcasting services delivered over broadband Internet protocol networks (Question

More information

ST2110 and High Bitrate Media Transport over IP Networks

ST2110 and High Bitrate Media Transport over IP Networks broadcast communications Zetrox Broadcast Communications Archer Lodge, Chequers Road, Basingstoke, Hampshire, RG21 7PU, United Kingdom training@zetrox.com; Tel. / Fax.: +44 (0)1256 328484 Training Course

More information

MISB ST STANDARD. MPEG-2 Transport Stream for Class 1/Class 2 Motion Imagery, Audio and Metadata. 25 February Scope.

MISB ST STANDARD. MPEG-2 Transport Stream for Class 1/Class 2 Motion Imagery, Audio and Metadata. 25 February Scope. MISB ST 1402.1 STANDARD MPEG-2 Transport Stream for Class 1/Class 2 Motion Imagery, Audio and Metadata 25 February 2016 1 Scope This standard provides guidance and specifies requirements for encapsulating

More information

ISO IEC. INTERNATIONAL ISO/IEC STANDARD Information technology Fibre Distributed Data Interface (FDDI) Part 5: Hybrid Ring Control (HRC)

ISO IEC. INTERNATIONAL ISO/IEC STANDARD Information technology Fibre Distributed Data Interface (FDDI) Part 5: Hybrid Ring Control (HRC) INTERNATIONAL ISO/IEC STANDARD 9314-5 First edition 1995-02-01 Information technology Fibre Distributed Data Interface (FDDI) Part 5: Hybrid Ring Control (HRC) Technologies de l'information Interface de

More information

OSI Layer OSI Name Units Implementation Description 7 Application Data PCs Network services such as file, print,

OSI Layer OSI Name Units Implementation Description 7 Application Data PCs Network services such as file, print, ANNEX B - Communications Protocol Overheads The OSI Model is a conceptual model that standardizes the functions of a telecommunication or computing system without regard of their underlying internal structure

More information

DAB. Digital Audio Broadcasting

DAB. Digital Audio Broadcasting DAB Digital Audio Broadcasting DAB history DAB has been under development since 1981 at the Institut für Rundfunktechnik (IRT). In 1985 the first DAB demonstrations were held at the WARC-ORB in Geneva

More information

INTERNATIONAL TELECOMMUNICATION UNION

INTERNATIONAL TELECOMMUNICATION UNION INTERNATIONAL TELECOMMUNICATION UNION ITU-T J.189 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (07/2002) SERIES J: CABLE NETWORKS AND TRANSMISSION OF TELEVISION, SOUND PROGRAMME AND OTHER MULTIMEDIA

More information

RTP. Prof. C. Noronha RTP. Real-Time Transport Protocol RFC 1889

RTP. Prof. C. Noronha RTP. Real-Time Transport Protocol RFC 1889 RTP Real-Time Transport Protocol RFC 1889 1 What is RTP? Primary objective: stream continuous media over a best-effort packet-switched network in an interoperable way. Protocol requirements: Payload Type

More information

Material Exchange Format Timecode Implementation

Material Exchange Format Timecode Implementation EBU Recommendation R 122 Material Exchange Format Timecode Implementation Version 2.0 Source: EC-I SP/HIPS MXF Geneva November 2010 1 Page intentionally left blank. This document is paginated for two sided

More information

Request for Comments: 4425 Category: Standards Track February 2006

Request for Comments: 4425 Category: Standards Track February 2006 Network Working Group A. Klemets Request for Comments: 4425 Microsoft Category: Standards Track February 2006 Status of This Memo RTP Payload Format for Video Codec 1 (VC-1) This document specifies an

More information

Need For Protocol Architecture

Need For Protocol Architecture Chapter 2 CS420/520 Axel Krings Page 1 Need For Protocol Architecture E.g. File transfer Source must activate communications path or inform network of destination Source must check destination is prepared

More information

Request for Comments: 5109 December 2007 Obsoletes: 2733, 3009 Category: Standards Track. RTP Payload Format for Generic Forward Error Correction

Request for Comments: 5109 December 2007 Obsoletes: 2733, 3009 Category: Standards Track. RTP Payload Format for Generic Forward Error Correction Network Working Group A. Li, Ed. Request for Comments: 5109 December 2007 Obsoletes: 2733, 3009 Category: Standards Track RTP Payload Format for Generic Forward Error Correction Status of This Memo This

More information

Need For Protocol Architecture

Need For Protocol Architecture Chapter 2 CS420/520 Axel Krings Page 1 Need For Protocol Architecture E.g. File transfer Source must activate communications path or inform network of destination Source must check destination is prepared

More information

Optical Data Interface ODI-2.1 High Speed Data Formats Preliminary Specification. Revision Date

Optical Data Interface ODI-2.1 High Speed Data Formats Preliminary Specification. Revision Date Optical Data Interface O-2.1 High Speed Data Formats Preliminary Specification Revision Date 171002 2 O 3-part Specification O-2.1: High-Speed Formats 8 to 16 bit data formats Packing Methods Optimized

More information

AES standard for digital audio engineering - High-resolution multi-channel audio interconnection (HRMAI) Preview only

AES standard for digital audio engineering - High-resolution multi-channel audio interconnection (HRMAI) Preview only (revision of AES50-2005) AES standard for digital audio engineering - High-resolution multi-channel audio interconnection (HRMAI) Published by Audio Engineering Society, Inc. Copyright 2011 by the Audio

More information

ISO/IEC INTERNATIONAL STANDARD

ISO/IEC INTERNATIONAL STANDARD INTERNATIONAL STANDARD ISO/IEC 23009-1 First edition 2012-04-01 Information technology Dynamic adaptive streaming over HTTP (DASH) Part 1: Media presentation description and segment formats Technologies

More information

MISB ST STANDARD. MPEG-2 Transport Stream for Class 1/Class 2 Motion Imagery, Audio and Metadata. 27 October Scope.

MISB ST STANDARD. MPEG-2 Transport Stream for Class 1/Class 2 Motion Imagery, Audio and Metadata. 27 October Scope. MISB ST 1402.2 STANDARD MPEG-2 Transport Stream for Class 1/Class 2 Motion Imagery, Audio and Metadata 27 October 2016 1 Scope This standard provides guidance and specifies requirements for encapsulating

More information

ST2110 and High Bitrate Media Transport over IP Networks

ST2110 and High Bitrate Media Transport over IP Networks broadcast communications Zetrox Broadcast Communications Archer Lodge, Chequers Road, Basingstoke, Hampshire, RG21 7PU, United Kingdom training@zetrox.com; Tel. / Fax.: +44 (0)1256 328484 Training Course

More information

ITU-T G (07/2010) Gigabit-capable passive optical networks (GPON): Long reach

ITU-T G (07/2010) Gigabit-capable passive optical networks (GPON): Long reach International Telecommunication Union ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU G.984.7 (07/2010) SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS Digital sections and

More information

BLM6196 COMPUTER NETWORKS AND COMMUNICATION PROTOCOLS

BLM6196 COMPUTER NETWORKS AND COMMUNICATION PROTOCOLS BLM6196 COMPUTER NETWORKS AND COMMUNICATION PROTOCOLS Prof. Dr. Hasan Hüseyin BALIK (2 nd Week) 2. Protocol Architecture, TCP/IP, and Internet-Based Applications 2.Outline The Need for a Protocol Architecture

More information

Data encoding protocol using key-length-value

Data encoding protocol using key-length-value Recommendation ITU-R BT.1563-1 (03/2011) Data encoding protocol using key-length-value BT Series Broadcasting service (television) ii Rec. ITU-R BT.1563-1 Foreword The role of the Radiocommunication Sector

More information

Development of System for Simultaneously Present Multiple Videos That Enables Search by Absolute Time

Development of System for Simultaneously Present Multiple Videos That Enables Search by Absolute Time Journal of Electrical Engineering 6 (2018) 33-39 doi: 10.17265/2328-2223/2018.01.005 D DAVID PUBLISHING Development of System for Simultaneously Present Multiple Videos Kazuhiro OTSUKI 1 and Yoshihiro

More information

A PROPOSED REVISION TO IRIG 218 BASED ON REAL WORLD EXPERIENCE Gary A. Thom GDP Space Systems 300 Welsh Road, Horsham, PA

A PROPOSED REVISION TO IRIG 218 BASED ON REAL WORLD EXPERIENCE Gary A. Thom GDP Space Systems 300 Welsh Road, Horsham, PA Abstract A PROPOSED REVISION TO IRIG 218 BASED ON REAL WORLD EXPERIENCE Gary A. Thom GDP Space Systems 300 Welsh Road, Horsham, PA 19044 gthom@delta-info.com The Range Commanders Council has been attempting

More information

ATSC 3.0 Update RICH CHERNOCK ATSC TG3 CHAIR TRIVENI DIGITAL CSO ADVANCED TELEVISION SYSTEMS COMMITTEE

ATSC 3.0 Update RICH CHERNOCK ATSC TG3 CHAIR TRIVENI DIGITAL CSO ADVANCED TELEVISION SYSTEMS COMMITTEE ATSC 3.0 Update RICH CHERNOCK ATSC TG3 CHAIR TRIVENI DIGITAL CSO ADVANCED TELEVISION SYSTEMS COMMITTEE ATSC etc. Constrained Maxed-Out Inefficient Fixed TV-Centric ATSC 3.0 Configurable Scalable Efficient

More information

SERIES Q: SWITCHING AND SIGNALLING Signalling requirements and protocols for the NGN Service and session control protocols supplementary services

SERIES Q: SWITCHING AND SIGNALLING Signalling requirements and protocols for the NGN Service and session control protocols supplementary services International Telecommunication Union ITU-T Q.3613 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (05/2012) SERIES Q: SWITCHING AND SIGNALLING Signalling requirements and protocols for the NGN Service

More information

PROPOSED SMPTE STANDARD for Television Material Exchange Format (MXF) Operational pattern 1A (Single Item, Single Package)

PROPOSED SMPTE STANDARD for Television Material Exchange Format (MXF) Operational pattern 1A (Single Item, Single Package) PROPOSED STE STANDARD for Television Material Exchange Format (MXF) Operational pattern 1A (Single Item, Single Package) STE 378M Page 1 of 9 pages Table of contents 1 Scope 2 Normative reference 3 Glossary

More information

Optical Data Interface ODI-2 Transport Layer Preliminary Specification

Optical Data Interface ODI-2 Transport Layer Preliminary Specification Optical Data Interface O-2 Transport Layer Preliminary Specification Revision 2, Date 180420 The O Specification is managed by the AXIe Consortium. For more information about O, go to http://axiestandard.org/odispecifications.html

More information

INTERNATIONAL TELECOMMUNICATION UNION. SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS Digital networks General aspects

INTERNATIONAL TELECOMMUNICATION UNION. SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS Digital networks General aspects INTERNATIONAL TELECOMMUNICATION UNION ITU-T G.804 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (06/2004) SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS Digital networks General

More information

HD Radio Air Interface Design Description Layer 2 Channel Multiplex Rev. I August 23, 2011

HD Radio Air Interface Design Description Layer 2 Channel Multiplex Rev. I August 23, 2011 HD Radio Air Interface Design Description Layer 2 Multiplex Rev. I August 23, 2011 SY_IDD_1014s TRADEMARKS HD Radio and the HD, HD Radio, and Arc logos are proprietary trademarks of ibiquity Digital Corporation.

More information

On Distributed Communications, Rand Report RM-3420-PR, Paul Baran, August 1964

On Distributed Communications, Rand Report RM-3420-PR, Paul Baran, August 1964 The requirements for a future all-digital-data distributed network which provides common user service for a wide range of users having different requirements is considered. The use of a standard format

More information

MA5400 IP Video Gateway. Introduction. Summary of Features

MA5400 IP Video Gateway. Introduction. Summary of Features MA5400 IP Video Gateway Introduction The MA5400 IP Video Gateway bridges the gap between the MPEG-2 and IP domains providing an innovative solution to the need to transport real-time broadcast quality

More information

Introduction to LAN/WAN. Application Layer 4

Introduction to LAN/WAN. Application Layer 4 Introduction to LAN/WAN Application Layer 4 Multimedia Multimedia: Audio + video Human ear: 20Hz 20kHz, Dogs hear higher freqs DAC converts audio waves to digital E.g PCM uses 8-bit samples 8000 times

More information

ET4254 Communications and Networking 1

ET4254 Communications and Networking 1 Topic 9 Internet Protocols Aims:- basic protocol functions internetworking principles connectionless internetworking IP IPv6 IPSec 1 Protocol Functions have a small set of functions that form basis of

More information

HSTP-IPTV-GUIDE.1 IPTV

HSTP-IPTV-GUIDE.1 IPTV I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Technical Paper (27 October 2017) HSTP-IPTV-GUIDE.1 IPTV service deployment scenarios

More information

SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS Infrastructure of audiovisual services Communication procedures

SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS Infrastructure of audiovisual services Communication procedures I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU H.248.57 (10/2014) SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS Infrastructure

More information

SMPTE STANDARD. for Television Bit Digital Audio Format for HDTV Bit-Serial Interface ANSI/SMPTE 299M Scope. 3 Definition of terms

SMPTE STANDARD. for Television Bit Digital Audio Format for HDTV Bit-Serial Interface ANSI/SMPTE 299M Scope. 3 Definition of terms SMPTE STANDARD ANSI/SMPTE 299M-1997 for Television ---- 24-Bit Digital Audio Format for HDTV Bit-Serial Interface 1 Scope 1.1 This standard defines the mapping of 24-bit AES digital audio data and associated

More information

[1] ISO/IEC :2007 Information technology - Generic coding of moving pictures and associated audio information: Systems

[1] ISO/IEC :2007 Information technology - Generic coding of moving pictures and associated audio information: Systems MISB Standard 0604.1 STANDARD Time Stamping and Transport of Compressed Motion Imagery and Metadata 30 September 2010 1 Scope This STANDARD defines methods to time stamp compressed video streams and to

More information

Data Broadcasting Solutions for Broadcasters

Data Broadcasting Solutions for Broadcasters Data Broadcasting Solutions for Broadcasters by Brett Jenkins Thomcast Communications, Inc. Southwick, MA SMPTE Technical Conference 2000 Pasadena, CA page 1 Data Broadcasting - What Is It? Multimedia

More information

Networking Applications

Networking Applications Networking Dr. Ayman A. Abdel-Hamid College of Computing and Information Technology Arab Academy for Science & Technology and Maritime Transport Multimedia Multimedia 1 Outline Audio and Video Services

More information

Configuring RTP Header Compression

Configuring RTP Header Compression Header compression is a mechanism that compresses the IP header in a packet before the packet is transmitted. Header compression reduces network overhead and speeds up the transmission of either Real-Time

More information

Configuring RTP Header Compression

Configuring RTP Header Compression Configuring RTP Header Compression First Published: January 30, 2006 Last Updated: July 23, 2010 Header compression is a mechanism that compresses the IP header in a packet before the packet is transmitted.

More information

Internet Streaming Media Alliance Ultravox Provisional Specification Version 1.0 November 2007

Internet Streaming Media Alliance Ultravox Provisional Specification Version 1.0 November 2007 Internet Streaming Media Alliance Ultravox Provisional Specification Version 1.0 November 2007 ISMA Ultravox Part 1: Introduction Page 1 of 6 November 2007 ISMA SPECIFICATION LIMITATIONS AND CONDITIONS

More information

draft-begen-fecframe-interleaved-fec-scheme-00 IETF 72 July 2008 Ali C. Begen

draft-begen-fecframe-interleaved-fec-scheme-00 IETF 72 July 2008 Ali C. Begen 1-D Interleaved Parity FEC draft-begen-fecframe-interleaved-fec-scheme-00 IETF 72 July 2008 Ali C. Begen abegen@cisco.com Introduction 1-D interleaved parity code Is a systematic FEC code of decent complexity

More information

Cobalt Digital Inc Galen Drive Champaign, IL USA

Cobalt Digital Inc Galen Drive Champaign, IL USA Cobalt Digital White Paper IP Video Transport Protocols Knowing What To Use When and Why Cobalt Digital Inc. 2506 Galen Drive Champaign, IL 61821 USA 1-217-344-1243 www.cobaltdigital.com support@cobaltdigital.com

More information

Multi-Service Interworking Frame Relay and ATM Service Interworking over MPLS. MFA Forum

Multi-Service Interworking Frame Relay and ATM Service Interworking over MPLS. MFA Forum Multi-Service Interworking Frame Relay and Service Interworking over MFA Forum 15.0.0 MFA Forum Technical Committee January 2007 and Service Interworking over MFA Forum 15.0.0 Note: The user s attention

More information

ATSC 3.0 Next Generation Television

ATSC 3.0 Next Generation Television ATSC 3.0 Next Generation Television Where are We and Where are We Headed? Rich Chernock JUNE 8, 2018 ATSC 3.0 has been released! What we ve achieved Extensibility / Flexibility Bootstrap (A/321) starting

More information

Switched Multimegabit Data Service (SMDS)

Switched Multimegabit Data Service (SMDS) CHAPTER 14 Switched Multimegabit Data Service (SMDS) Background Switched Multimegabit Data Service (SMDS) is a high-speed, packet-switched, datagram-based WAN networking technology used for communication

More information

Optical Data Interface ODI-2.1 High Speed Data Formats Preliminary Specification

Optical Data Interface ODI-2.1 High Speed Data Formats Preliminary Specification Optical Data Interface O-2.1 High Speed Data Formats Preliminary Specification Revision 2, Date 1842 The O Specification is managed by the AXIe Consortium. For more information about O, go to http://axiestandard.org/odispecifications.html

More information

Using RTSP with Firewalls, Proxies, and Other Intermediary Network Devices

Using RTSP with Firewalls, Proxies, and Other Intermediary Network Devices Using with Firewalls, Proxies, and Other Intermediary Network Devices Version 2.0/rev.2 Introduction This white paper provides information to developers and implementers about the incorporation of Real

More information

INTERNATIONAL STANDARD

INTERNATIONAL STANDARD INTERNATIONAL STANDARD ISO/IEC 9314-7 First edition 1998-08 Information technology Fibre distributed data interface (FDDI) Part 7: Physical Layer Protocol (PHY-2) Reference number ISO/IEC 9314-7:1998(E)

More information

SPACE DATA LINK PROTOCOLS SUMMARY OF CONCEPT AND RATIONALE

SPACE DATA LINK PROTOCOLS SUMMARY OF CONCEPT AND RATIONALE Report Concerning Space Data System Standards SPACE DATA LINK PROTOCOLS SUMMARY OF CONCEPT AND RATIONALE INFORMATIONAL REPORT CCSDS 130.2-G-3 GREEN BOOK September 2015 Report Concerning Space Data System

More information

ECMA-397. Short Distance Visible Light Communication (SDVLC) 1 st Edition / December Reference number ECMA-123:2010

ECMA-397. Short Distance Visible Light Communication (SDVLC) 1 st Edition / December Reference number ECMA-123:2010 ECMA-397 1 st Edition / December 2010 Short Distance Visible Light Communication (SDVLC) Reference number ECMA-123:2010 Ecma International 2010 COPYRIGHT PROTECTED DOCUMENT Ecma International 2010 Contents

More information

HD Radio Air Interface Design Description Layer 2 Channel Multiplex Rev. J December 14, 2016

HD Radio Air Interface Design Description Layer 2 Channel Multiplex Rev. J December 14, 2016 HD Radio Air Interface Design Description Layer 2 Multiplex Rev. J December 14, 2016 SY_IDD_1014s TRADEMARKS HD Radio and the HD, HD Radio, and Arc logos are proprietary trademarks of ibiquity Digital

More information

ANSI/SCTE

ANSI/SCTE ENGINEERING COMMITTEE Digital Video Subcommittee AMERICAN NATIONAL STANDARD ANSI/SCTE 87-2 202 Stereoscopic 3D PSI Signaling NOTICE The Society of Cable Telecommunications Engineers (SCTE) Standards and

More information

Internet Engineering Task Force (IETF) Request for Comments: 6015 Category: Standards Track October 2010 ISSN:

Internet Engineering Task Force (IETF) Request for Comments: 6015 Category: Standards Track October 2010 ISSN: Internet Engineering Task Force (IETF) A. Begen Request for Comments: 6015 Cisco Category: Standards Track October 2010 ISSN: 2070-1721 Abstract RTP Payload Format for 1-D Interleaved Parity Forward Error

More information

Basic elements of file-based broadcasting systems

Basic elements of file-based broadcasting systems Recommendation ITU-R BT.1888 (03/2011) Basic elements of file-based broadcasting systems BT Series Broadcasting service (television) ii Rec. ITU-R BT.1888 Foreword The role of the Radiocommunication Sector

More information

Internet Engineering Task Force (IETF) Request for Comments: R. Jesup WorldGate Communications May 2011

Internet Engineering Task Force (IETF) Request for Comments: R. Jesup WorldGate Communications May 2011 Internet Engineering Task Force (IETF) Request for Comments: 6184 Obsoletes: 3984 Category: Standards Track ISSN: 2070-1721 Y.-K. Wang R. Even Huawei Technologies T. Kristensen Tandberg R. Jesup WorldGate

More information

Communication Networks

Communication Networks Communication Networks Chapter 3 Multiplexing Frequency Division Multiplexing (FDM) Useful bandwidth of medium exceeds required bandwidth of channel Each signal is modulated to a different carrier frequency

More information

ISO/IEC INTERNATIONAL STANDARD. Information technology Multimedia content description interface Part 1: Systems

ISO/IEC INTERNATIONAL STANDARD. Information technology Multimedia content description interface Part 1: Systems INTERNATIONAL STANDARD ISO/IEC 15938-1 First edition 2002-07-01 Information technology Multimedia content description interface Part 1: Systems Technologies de l'information Interface de description du

More information

Multimedia in the Internet

Multimedia in the Internet Protocols for multimedia in the Internet Andrea Bianco Telecommunication Network Group firstname.lastname@polito.it http://www.telematica.polito.it/ > 4 4 3 < 2 Applications and protocol stack DNS Telnet

More information

SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS Infrastructure of audiovisual services Coding of moving video

SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS Infrastructure of audiovisual services Coding of moving video I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU H.265.2 (12/2016) SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS Infrastructure

More information

ISO/IEC INTERNATIONAL STANDARD. Information technology Multimedia content description interface Part 5: Multimedia description schemes

ISO/IEC INTERNATIONAL STANDARD. Information technology Multimedia content description interface Part 5: Multimedia description schemes INTERNATIONAL STANDARD ISO/IEC 15938-5 First edition 2003-05-15 Information technology Multimedia content description interface Part 5: Multimedia description schemes Technologies de l'information Interface

More information

ITU-T G.832. Transport of SDH elements on PDH networks Frame and multiplexing structures

ITU-T G.832. Transport of SDH elements on PDH networks Frame and multiplexing structures INTERNATIONAL TELECOMMUNICATION UNION ITU-T G.832 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (10/98) SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS Digital transmission systems

More information

INTERNATIONAL TELECOMMUNICATION UNION

INTERNATIONAL TELECOMMUNICATION UNION INTERNATIONAL TELECOMMUNICATION UNION ITU-T H.323 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Annex G (02/00) SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS Infrastructure of audiovisual services Systems

More information

The Transformation of Media & Broadcast Video Production to a Professional Media Network

The Transformation of Media & Broadcast Video Production to a Professional Media Network The Transformation of Media & Broadcast Video Production to a Professional Media Network Subha Dhesikan, Principal Engineer Cisco Spark How Questions? Use Cisco Spark to communicate with the speaker after

More information

[MS-RTPRADEX]: RTP Payload for Redundant Audio Data Extensions. Intellectual Property Rights Notice for Open Specifications Documentation

[MS-RTPRADEX]: RTP Payload for Redundant Audio Data Extensions. Intellectual Property Rights Notice for Open Specifications Documentation [MS-RTPRADEX]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation ( this documentation ) for protocols,

More information

A Converged Content Delivery Platform for IP and QAM Video

A Converged Content Delivery Platform for IP and QAM Video A Converged Delivery Platform for IP and QAM Video Abstract James Barkley, Weidong Mao Comcast Cable HTTP based Adaptive Bit Rate (ABR) video delivery to IP enabled CPEs via Delivery Network (CDN) for

More information

Internet Engineering Task Force (IETF) Category: Standards Track ISSN: March 2014

Internet Engineering Task Force (IETF) Category: Standards Track ISSN: March 2014 Internet Engineering Task Force (IETF) K. Gross Request for Comments: 7164 AVA Networks Updates: 3550 R. van Brandenburg Category: Standards Track TNO ISSN: 2070-1721 March 2014 Abstract RTP and Leap Seconds

More information

Annotation Universal Metadata Set. 1 Scope. 2 References. 3 Introduction. Motion Imagery Standards Board Recommended Practice MISB RP 0602.

Annotation Universal Metadata Set. 1 Scope. 2 References. 3 Introduction. Motion Imagery Standards Board Recommended Practice MISB RP 0602. Motion Imagery Standards Board Recommended Practice Annotation Universal Metadata Set MISB RP 0602.1 13 June 2007 1 Scope This Recommended Practice documents the basic SMPTE KLV metadata sets used to encode

More information

MISB ST STANDARD. 27 February Ancillary Text Metadata Sets. 1 Scope. 2 References. 2.1 Normative References.

MISB ST STANDARD. 27 February Ancillary Text Metadata Sets. 1 Scope. 2 References. 2.1 Normative References. MISB ST 0808.1 STANDARD Ancillary Text Metadata Sets 27 February 2014 1 Scope This Standard documents the SMPTE KLV metadata sets used to encode text data associated with a motion imagery data stream.

More information

Data Communication and Network. Introducing Networks

Data Communication and Network. Introducing Networks Data Communication and Network Introducing Networks Introduction to Networking Computer network, or simply network Refers to the connection of two or more computers by some type of medium You can connect

More information

ISO/IEC INTERNATIONAL STANDARD

ISO/IEC INTERNATIONAL STANDARD NTERNATONAL STANDARD SO/EC 11172-1 First edition 1993-08-0 1 nformation technology - Coding of moving pictures and associated audio for digital storage media at up to about 1,5 Mbit/s - Part 1: Systems

More information

RECOMMENDATION ITU-R BT.1126 *

RECOMMENDATION ITU-R BT.1126 * Rec. ITU-R BT.1126 1 RECOMMENDATION ITU-R BT.1126 * Data transmission protocols and transmission control scheme for data broadcasting systems using a data channel in satellite television broadcasting (1994)

More information