没有合适的资源?快使用搜索试试~ 我知道了~
首页SMPTE ST2022-1
资源详情
资源评论
资源推荐

Forward Error Correction for Real-Time Video/Audio Transport Over IP Networks
, :.ST 2022-1:2007
http://standards.smpte.org/content/978-1-61482-615-6/st-2022-1-2007/SEC1
the World Wide Web at:
The online version of this article, along with updated information and services, is located on
@ SMPTE All Rights Reserved 58.251.6. 243Downloaded by guest on 2014-06-25 from IP @ SMPTE All Rights Reserved 58.251.6. 243Downloaded by guest on 2014-06-25 from IP

Copyright © 2007 by THE SOCIETY OF
MOTION PICTURE AND TELEVISION ENGINEERS
595 W. Hartsdale Ave., White Plains, NY 10607
(914) 761
-
1100
Approved
May 24, 2007
Table of Contents Page
Foreword ................................................................................................................................................. 2
Introduction ............................................................................................................................................. 2
1 Scope .................................................................................................................................................. 3
2 Conformance Notation ........................................................................................................................ 3
3 Normative References ........................................................................................................................ 3
4 Acronyms (Informative) ....................................................................................................................... 3
5 Definitions ........................................................................................................................................... 4
5.1 Traffic Shaping ............................................................................................................................. 4
5.2 XOR ............................................................................................................................................. 4
5.3 Latency......................................................................................................................................... 4
5.4 Delay ............................................................................................................................................ 4
6 Background (Informative).................................................................................................................... 4
7 Encapsulation Scheme ....................................................................................................................... 5
7.1 RTP/UDP/IP Layer ....................................................................................................................... 5
8 FEC Scheme....................................................................................................................................... 5
8.1 FEC Packet Arrangement ............................................................................................................ 5
8.2 FEC Buffer Overhead and Latency Implications.......................................................................... 7
8.3 FEC Packet RTP Header Format ................................................................................................ 7
8.4 FEC Header Format..................................................................................................................... 8
8.5 FEC Traffic Shaping Issues ......................................................................................................... 9
8.6 Reorder Tolerance (Informative).................................................................................................. 10
9 System Configuration.......................................................................................................................... 10
Annex A Bibliography (Informative) ...................................................................................................... 11
Annex B Non-Block Aligned FEC Arrangement (Informative) .............................................................. 12
Annex C Block Aligned FEC Arrangement (Informative)...................................................................... 13
Annex D Delay (Informative)................................................................................................................. 15
Page 1 of 15 pages
SMPTE 2022-1-2007
SMPTE STANDARD
Forward Error Correction for
Real-Time Video/Audio
Transport Over IP Networks
@ SMPTE All Rights Reserved 113.194.103.243Downloaded by guest on 2014-06-25 from IP

SMPTE 2022-1-2007
Page 2 of 15 pages
Foreword
SMPTE (the Society of Motion Picture and Television Engineers) is an internationally-recognized standards
developing organization. Headquartered and incorporated in the United States of America, SMPTE has
members in over 80 countries on six continents. SMPTE’s Engineering Documents, including Standards,
Recommended Practices and Engineering Guidelines, are prepared by SMPTE’s Technology Committees.
Participation in these Committees is open to all with a bona fide interest in their work. SMPTE cooperates
closely with other standards-developing organizations, including ISO, IEC and ITU.
SMPTE Engineering Documents are drafted in accordance with the rules given in Part XIII of its
Administrative Practices.
SMPTE 2022-1 was prepared by Technology Committee N26 on File Management and Networking
Techology.
Introduction
This section is entirely informative and does not form an integral part of this document.
IP-based networks have become increasingly important for delivery of compressed content as MPEG-2
Transport Streams. However, existing transport protocols do not fully meet the user requirements, especially
for a standardized forward error correction technique required for interoperability between different
manufacturers. This standard defines a forward error correction technique to be used to correct for errors
induced when video/audio payloads are transported over IP networks.
This document defines a structured mechanism for FEC. Nothing in this standard defines when this FEC
mechanism should be used. It is up to the implementer to determine whether FEC is required over the IP
network in use, and whether the mechanism presented here meets their application requirements.
This standard is intended for real-time audio/video applications such as contribution, distribution, and ”e-
cinema”. The applications addressed by this standard may employ any transport scheme that is supported by
the video/audio transport Standards. This standard defines two levels of FEC – Level A and Level B. Level A
uses one FEC stream and Level B uses two FEC streams.
@ SMPTE All Rights Reserved 113.194.103.243Downloaded by guest on 2014-06-25 from IP

SMPTE 2022-1-2007
Page 3 of 15 pages
1 Scope
This standard defines a forward error correction technique for the carriage of real-time Video/Audio content
over IP networks.
2 Conformance Notation
Normative text is text that describes elements of the design that are indispensable or contains the
conformance language keywords: "shall", "should", or "may". Informative text is text that is potentially helpful
to the user, but not indispensable, and can be removed, changed, or added editorially without affecting
interoperability. Informative text does not contain any conformance keywords.
All text in this document is, by default, normative, except: the Introduction, any section explicitly labeled as
"Informative" or individual paragraphs that start with "Note:”
The keywords "shall" and "shall not" indicate requirements strictly to be followed in order to conform to the
document and from which no deviation is permitted.
The keywords, "should" and "should not" indicate that, among several possibilities, one is recommended as
particularly suitable, without mentioning or excluding others; or that a certain course of action is preferred but
not necessarily required; or that (in the negative form) a certain possibility or course of action is deprecated
but not prohibited.
The keywords "may" and "need not" indicate courses of action permissible within the limits of the document.
The keyword “reserved” indicates a provision that is not defined at this time, shall not be used, and may be
defined in the future. The keyword “forbidden” indicates “reserved” and in addition indicates that the provision
will never be defined in the future.
3 Normative References
The following standards contain provisions which, through reference in this text, constitute provisions of this
recommended practice. At the time of publication, the editions indicated were valid. All standards are subject
to revision, and parties to agreements based on this recommended practice are encouraged to investigate the
possibility of applying the most recent edition of the standards indicated below.
IETF RFC 3550, RTP: A Transport Protocol for Real-Time Applications
IETF RFC 2733, An RTP Payload Format for Generic Forward Error Correction
IETF RFC 4340, Datagram Congestion Control Protocol (DCCP)
4 Acronyms (Informative)
ASI: Asynchronous Serial Interface
CSRC: Contributing Sources List
FEC: Forward Error Correction
IANA: Internet Assigned Numbers Authority
IP: Internet Protocol
RTCP: Real Time Control Protocol
@ SMPTE All Rights Reserved 113.194.103.243Downloaded by guest on 2014-06-25 from IP
剩余15页未读,继续阅读









安全验证
文档复制为VIP权益,开通VIP直接复制

评论0