ISO/IEC/IEEE 8802-1BA:2016

INTERNATIONAL ISO/IEC/
STANDARD IEEE
8802-1BA
First edition
2016-10-15
Information technology —
Telecommunications and information
exchange between systems — Local
and metropolitan area networks —
Specific requirements —
Part 1BA:
Audio video bridging (AVB) systems
Technologies de l’information — Télécommunications et échange
d’informations entre systèmes — Réseaux de zones locales et
métropolitaines — Exigences spécifiques —
Partie 1BA: Systèmes de pontage audio-vidéo (AVB)
Reference number
© IEEE 2011 – All rights reserved

© IEEE 2011
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form
or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior
written permission. Permission can be requested from ISO or IEEE at the respective address below or ISO's member body in
the country of the requester.
ISO copyright office Institute of Electrical and Electronics Engineers, Inc
Ch. de Blandonnet 8 • CP 401 3 Park Avenue, New York
CH-1214 Vernier, Geneva, Switzerland NY 10016-5997, USA
Tel. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org stds.ipr@ieee.org
www.iso.org www.ieee.org
© IEEE 2011 – All rights reserved
ii
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are members of
ISO or IEC participate in the development of International Standards through technical committees established
by the respective organization to deal with particular fields of technical activity. ISO and IEC technical
committees collaborate in fields of mutual interest. Other international organizations, governmental and non-
governmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO
and IEC have established a joint technical committee, ISO/IEC JTC 1.
IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating
Committees of the IEEE Standards Association (IEEE-SA) Standards Board. The IEEE develops its standards
through a consensus development process, approved by the American National Standards Institute, which
brings together volunteers representing varied viewpoints and interests to achieve the final product. Volunteers
are not necessarily members of the Institute and serve without compensation. While the IEEE administers the
process and establishes rules to promote fairness in the consensus development process, the IEEE does not
independently evaluate, test, or verify the accuracy of any of the information contained in its standards.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of ISO/IEC JTC 1 is to prepare International Standards. Draft International Standards adopted
by the joint technical committee are circulated to national bodies for voting. Publication as an International
Standard requires approval by at least 75 % of the national bodies casting a vote.
Attention is called to the possibility that implementation of this standard may require the use of subject matter
covered by patent rights. By publication of this standard, no position is taken with respect to the existence or
validity of any patent rights in connection therewith. ISO/IEEE is not responsible for identifying essential
patents or patent claims for which a license may be required, for conducting inquiries into the legal validity or
scope of patents or patent claims or determining whether any licensing terms or conditions provided in
connection with submission of a Letter of Assurance or a Patent Statement and Licensing Declaration Form, if
any, or in any licensing agreements are reasonable or non-discriminatory. Users of this standard are expressly
advised that determination of the validity of any patent rights, and the risk of infringement of such rights, is
entirely their own responsibility. Further information may be obtained from ISO or the IEEE Standards
Association.
ISO/IEC/IEEE 8802-1BA was prepared by Joint Technical Committee ISO/IEC JTC 1, Information Technology,
Subcommittee SC 6, Telecommunications and information exchange between systems in cooperation with the
Systems and Software Engineering Standards Committee of the IEEE Computer Society, under the Partner
Standards Development Organization cooperation agreement between ISO and IEEE.
© IEEE 2011 – All rights reserved
iii

IEEE Standard for
Local and metropolitan area networks—
Audio Video Bridging (AVB) Systems





IEEE Computer Society
Sponsored by the
LAN/MAN Standards Committee

IEEE
IEEE Std 802.1BA™Ǧ2011
3 Park Avenue
New York, NY 10016-5997
USA
30 September 2011
™
IEEE Std 802.1BA -2011
IEEE Standard for
Local and metropolitan area networks—
Audio Video Bridging (AVB) Systems
Sponsor
LAN/MAN Standards Committee
of the
IEEE Computer Society
Approved 10 September 2011
IEEE-SA Standards Board
© IEEE 2011 – All rights reserved

Abstract: Profiles that select features, options, configurations, defaults, protocols and procedures
of bridges, stations and LANs that are necessary to build networks that are capable of transporting
time-sensitive audio and/or video data streams are defined in this standard.
Keywords: audio video bridging, AVB, Bridged Local Area Networks, IEEE 802.1BA, LANs, local
area networks, MAC Bridges, MANs, metropolitan area networks, time sensitive data streams,
Virtual Bridged Local Area Networks, virtual LANs
The Institute of Electrical and Electronics Engineers, Inc.
3 Park Avenue, New York, NY 10016-5997, USA
All rights reserved. Published 30 September 2011. Printed in the United States of America.
IEEE and 802 are registered trademarks in the U.S. Patent & Trademark Office, owned by The Institute of Electrical and
Electronics Engineers, Incorporated.
PDF: ISBN 978-0-7381-6739-8 STD97154
Print: ISBN 978-0-7381-6740-4 STDPD97154
IEEE prohibits discrimination, harassment and bullying. For more information, visit http://www.ieee.org/web/aboutus/whatis/policies/p9-
26.html.
No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior written permission
of the publisher.
© IEEE 2011 – All rights reserved

IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating Committees of the
IEEE Standards Association (IEEE-SA) Standards Board. The IEEE develops its standards through a consensus
development process, approved by the American National Standards Institute, which brings together volunteers
representing varied viewpoints and interests to achieve the final product. Volunteers are not necessarily members of the
Institute and serve without compensation. While the IEEE administers the process and establishes rules to promote fairness
in the consensus development process, the IEEE does not independently evaluate, test, or verify the accuracy of any of the
information or the soundness of any judgments contained in its standards.
Use of an IEEE Standard is wholly voluntary. The IEEE disclaims liability for any personal injury, property or other
damage, of any nature whatsoever, whether special, indirect, consequential, or compensatory, directly or indirectly resulting
from the publication, use of, or reliance upon this, or any other IEEE Standard document.
The IEEE does not warrant or represent the accuracy or content of the material contained herein, and expressly disclaims
any express or implied warranty, including any implied warranty of merchantability or fitness for a specific purpose, or that
the use of the material contained herein is free from patent infringement. IEEE Standards documents are supplied “AS IS.”
The existence of an IEEE Standard does not imply that there are no other ways to produce, test, measure, purchase, market,
or provide other goods and services related to the scope of the IEEE Standard. Furthermore, the viewpoint expressed at the
time a standard is approved and issued is subject to change brought about through developments in the state of the art and
comments received from users of the standard. Every IEEE Standard is subjected to review at least every five years for
revision or reaffirmation, or every ten years for stabilization. When a document is more than five years old and has not been
reaffirmed, or more than ten years old and has not been stabilized, it is reasonable to conclude that its contents, although still
of some value, do not wholly reflect the present state of the art. Users are cautioned to check to determine that they have the
latest edition of any IEEE Standard.
In publishing and making this document available, the IEEE is not suggesting or rendering professional or other services
for, or on behalf of, any person or entity. Nor is the IEEE undertaking to perform any duty owed by any other person or
entity to another. Any person utilizing this, and any other IEEE Standards document, should rely upon the advice of a
competent professional in determining the exercise of reasonable care in any given circumstances.
Interpretations: Occasionally questions may arise regarding the meaning of portions of standards as they relate to specific
applications. When the need for interpretations is brought to the attention of IEEE, the Institute will initiate action to prepare
appropriate responses. Since IEEE Standards represent a consensus of concerned interests, it is important to ensure that any
interpretation has also received the concurrence of a balance of interests.For this reason, IEEE and the members of its
societies and Standards Coordinating Committees are not able to provide an instant response to interpretation requests
except in those cases where the matter has previously received formal consideration. A statement, written or oral, that is not
processed in accordance with the IEEE-SA Standards Board Operations Manual shall not be considered the official position
of IEEE or any of its committees and shall not be considered to be, nor be relied upon as, a formal interpretation of the
IEEE.At lectures, symposia, seminars, or educational courses, an individual presenting information on IEEE standards shall
make it clear that his or her views should be considered the personal views of that individual rather than the formal position,
explanation, or interpretation of the IEEE. Comments for revision of IEEE Standards are welcome from any interested
party, regardless of membership affiliation with IEEE. Suggestions for changes in documents should be in the form of a
proposed change of text, together with appropriate supporting comments. Recommendations to change the status of a
stabilized standard should include a rationale as to why a revision or withdrawal is required.
Comments and recommendations on standards, and requests for interpretations should be addressed to:
Secretary, IEEE-SA Standards Board
445 Hoes Lane
Piscataway, NJ 08854
USA
Authorization to photocopy portions of any individual standard for internal or personal use is granted by the Institute of
Electrical and Electronics Engineers, Inc., provided that the appropriate fee is paid to Copyright Clearance Center. To
arrange for payment of licensing fee, please contact Copyright Clearance Center, Customer Service, 222 Rosewood Drive,
Danvers, MA 01923 USA; +1 978 750 8400. Permission to photocopy portions of any individual standard for educational
classroom use can also be obtained through the Copyright Clearance Center.
© IEEE 2011 – All rights reserved

Introduction
This introduction is not part of IEEE Std 802.1BA-2011, IEEE Standard for Local and metropolitan area networks—
Audio Video Bridging (AVB) Systems.
This standard contains state-of-the-art material. The area covered by this standard is undergoing evolution.
Revisions are anticipated within the next few years to clarify existing material, to correct possible errors, and
to incorporate new related material. Information on the current revision state of this and other IEEE 802
standards may be obtained from
Secretary, IEEE-SA Standards Board
445 Hoes Lane
Piscataway, NJ 08854
USA
Notice to users
Laws and regulations
Users of these documents should consult all applicable laws and regulations. Compliance with the
provisions of this standard does not imply compliance to any applicable regulatory requirements.
Implementers of the standard are responsible for observing or referring to the applicable regulatory
requirements. IEEE does not, by the publication of its standards, intend to urge action that is not in
compliance with applicable laws, and these documents may not be construed as doing so.
Copyrights
This document is copyrighted by the IEEE. It is made available for a wide variety of both public and private
uses. These include both use, by reference, in laws and regulations, and use in private self-regulation,
standardization, and the promotion of engineering practices and methods. By making this document
available for use and adoption by public authorities and private users, the IEEE does not waive any rights in
copyright to this document.
Updating of IEEE documents
Users of IEEE standards should be aware that these documents may be superseded at any time by the
issuance of new editions or may be amended from time to time through the issuance of amendments,
corrigenda, or errata. An official IEEE document at any point in time consists of the current edition of the
document together with any amendments, corrigenda, or errata then in effect. In order to determine whether
a given document is the current edition and whether it has been amended through the issuance of
amendments, corrigenda, or errata, visit the IEEE Standards Association website at http://
ieeexplore.ieee.org/xpl/standards.jsp, or contact the IEEE at the address listed previously.
For more information about the IEEE Standards Association or the IEEE standards development process,
visit the IEEE-SA website at http://standards.ieee.org.
iv
© IEEE 2011 – All rights reserved

Errata
Errata, if any, for this and all other standards can be accessed at the following URL: http://
standards.ieee.org/findstds/errata/index.html. Users are encouraged to check this URL for errata
periodically.
Interpretations
Current interpretations can be accessed at the following URL: http://standards.ieee.org/findstds/interps/in-
dex.html.
Patents
Attention is called to the possibility that implementation of this amendment may require use of subject
matter covered by patent rights. By publication of this amendment, no position is taken with respect to the
existence or validity of any patent rights in connection therewith. The IEEE is not responsible for identifying
Essential Patent Claims for which a license may be required, for conducting inquiries into the legal validity
or scope of Patents Claims or determining whether any licensing terms or conditions provided in connection
with submission of a Letter of Assurance, if any, or in any licensing agreements are reasonable or non-
discriminatory. Users of this amendment are expressly advised that determination of the validity of any
patent rights, and the risk of infringement of such rights, is entirely their own responsibility. Further
information may be obtained from the IEEE Standards Association.
v
© IEEE 2011 – All rights reserved

Participants
At the time this standard was submitted to the IEEE-SA for approval, the IEEE 802.1 Working Group had
the following membership:
Tony Jeffree, Chair and Editor
Paul Congdon, Vice Chair
Michael Johas Teener, Chair, AV Bridging Task Group
Zehavit Alon Eric Gray David Olsen
Yafan An Yingjie Gu Donald Pannell
Craig Gunther
Ting Ao Glenn Parsons
Stephen Haddock
Peter Ashwood-Smith Mark Pearson
Hitoshi Hayakawa
Christian Boiger Joseph Pelissier
Hal Keen
Paul Bottorff Rene Raeber
Rudolf Brandner Srikanth Keesara Karen Randall
Craig Carlson Yongbum Kim Josef Roese
Rodney Cummings Philippe Klein Dan Romascanu
Claudio Desanti Oliver Kleineberg Jessy Rouyer
Zhemin Ding Michael Krause Ali Sajassi
Donald Eastlake, III Lin Li Panagiotis Saltsidis
Janos Farkas Jeff Lynch Michael Seaman
Donald Fedyk Ben Mack-Crane Rakesh Sharma
Norman Finn David Martin Kevin Stanton
Ilango Ganga John Messenger Robert Sultan
Geoffrey Garner John Morris PatriciaThaler
Anoop Ghanwani Eric Multanen Chait Tumuluri
Mark Gravel Maarten Vissers
vi
© IEEE 2011 – All rights reserved

The following members of the individual balloting committee voted on this standard. Balloters may have
voted for approval, disapproval, or abstention.
Thomas Alexander Randall Groves Nick S. A. Nikjoo
Mark Anderson Ashwin Gumaste
Paul Nikolich
Butch Anton Craig Gunther
Satoshi Obara
Lee Armstrong Oliver Hoffmann
David Olsen
Hugh Barrass David Hunter
Glenn Parsons
Atsushi Ito
Robert Boatright
Maximilian Riegel
Tomo Bogataj Raj Jain
Robert Robinson
Junghoon Jee
Nancy Bravin
Benjamin Rolfe
William Byrd Anthony Jeffree
Jessy Rouyer
James Carlo Michael Johas Teener
Randall Safier
Juan Carreon Vincent Jones
Peter Saunderson
David Chalupsky Shinkyo Kaku
Bartien Sayogo
Keith Chow Piotr Karocki
Gil Shultz
Henrik Christensen Stuart J. Kerry
Kapil Sood
Charles Cook Max Kicherer
Amjad Soomro
Rodney Cummings Yongbum Kim
Kevin B. Stanton
Fumio Daido Jeff Koftinoff
Thomas Starai
Wael Diab Bruce Kraemer
Adrian Stephens
Patrick Diamond David Landry
Walter Struppler
Russell Dietz Juan L. Lazaro
Joseph Tardo
Thomas Dineen Michael Lerer
Patricia Thaler
Sourav Dutta Shen Loh
David Thompson
John Egan Greg Luri
Geoffrey Thompson
C. Fitzgerald Elvis Maculuba
Scott Valcourt
Yukihiro Fujimoto Arthur Marris
Prabodh Varshney
John Fuller Jonathon Mclendon
Karl Weber
Geoffrey Garner Matthew Mora
Devon Gayle Michael S. Newman Oren Yuen
David Goodall Charles Ngethe George Zimmerman
vii
© IEEE 2011 – All rights reserved

When the IEEE-SA Standards Board approved this standard on 10 September 2011, it had the following
membership:
Richard H. Hulett, Chair
John Kulick, Vice Chair
Robert M. Grow, Past Chair
Judith Gorman, Secretary
Masayuki Ariyoshi
Jim Hughes Gary Robinson
William Bartley
Jon Walter Rosdahl
Joseph L. Koepfinger*
Ted Burse
Sam Sciacca
David J. Law
Clint Chaplin
Mike Seavey
Thomas Lee
Wael Diab
Hung Ling Curtis Siller
Jean-Philippe Faure
Oleg Logvinov Phil Winston
Alexander Gelman
Ted Olsen Howard L. Wolfman
Paul Houzé
Don Wright
*Member Emeritus
Also included are the following nonvoting IEEE-SA Standards Board liaisons:
Satish Aggarwal, NRC Representative
Richard DeBlasio, DOE Representative
Michael Janezic, NIST Representative
Catherine Berger
IEEE Project Editor
Patricia Gerdon
IEEE Standards Program Manager, Technical Program Development
viii
© IEEE 2011 – All rights reserved

Contents
1. Overview. 1
1.1 Scope. 1
1.2 Purpose. 1
1.3 Introduction. 1
1.4 Objectives . 2
2. Normative references. 3
3. Definitions . 5
4. Acronyms and abbreviations . 6
5. Architecture of AVB networks . 7
6. AVB functions . 11
6.1 Energy Efficient Ethernet . 11
6.2 Flow control. 11
6.3 Frame sizes . 12
6.4 Detection of AVB domains. 12
6.5 Meeting latency targets for SR classes A and B. 13
6.6 Variable data rate LANs . 16
6.7 Basic support for streams. 17
6.8 Minimum Bridge requirements. 18
6.9 IEEE 802.1AS time-synchronization event message transmission interval . 19
6.10 Effect of hop count on IEEE 802.1AS accuracy . 19
7. AVB profiles. 20
7.1 Introduction to PCS proformas . 20
7.2 Abbreviations and special symbols. 21
7.3 Instructions for completing the PCS proforma . 21
7.4 Common requirements . 23
Annex A (informative) Bibliography . 31
ix
© IEEE 2011 – All rights reserved

List of figures
Figure 5-1 An AVB network . 7
Figure 5-2 AVB domain boundaries created by non-AVB systems. 8
Figure 5-3 AVB domain boundaries created by different SR class A priorities . 9
Figure 5-4 AVB domain boundaries created by different SR class B priorities. 10
x
© IEEE 2011 – All rights reserved

List of tables
Table 6-1 AVB support in LAN technologies . 13
Table 6-2 Latency targets for SR classes A and B. 14
xi
© IEEE 2011 – All rights reserved

© IEEE 2011 – All rights reserved

IEEE Standard for
Local and metropolitan area networks—
Audio Video Bridging (AVB) Systems
IMPORTANT NOTICE: This standard is not intended to ensure safety, security, health, or environmental protection.
Implementers of the standard are responsible for determining appropriate safety, security, environmental, and health
practices or regulatory requirements.
This IEEE document is made available for use subject to important notices and legal disclaimers. These notices and
disclaimers appear in all publications containing this document and may be found under the heading “Important
Notice” or “Important Notices and Disclaimers Concerning IEEE Documents.” They can also be obtained on request
from IEEE or viewed at http://standards.ieee.org/IPR/disclaimers.html.
1. Overview
1.1 Scope
This standard defines profiles that select features, options, configurations, defaults, protocols and procedures
of bridges, stations and LANs that are necessary to build networks that are capable of transporting time
sensitive audio and/or video data streams.
1.2 Purpose
The purpose of this standard is to specify defaults and profiles that manufacturers of LAN equipment can
use to develop AVB-compatible LAN components, and to enable a person not skilled in networking to build
a network, using those components, that does not require configuration to provide working audio and/or
video services.
1.3 Introduction
The successful support of time sensitive audio and/or video data streams in a Bridged LAN requires the
selection of specific features and options that are specified in a number of different standards, some of which
are standards developed in IEEE 802, and others (in particular, those that relate to functionality in OSI layer
3 and above ISO/IEC 7498-1:1994 [B3]) that are developed by other bodies. In this standard, it is the
selection of features and options that support OSI layer 1 and 2 LAN functionality that is of interest, in order
to specify the requirements for LAN support both in Bridges and the end stations that attach to them.
The standards from which features and options are selected by this standard are as follows:
a) The VLAN Bridge specification in IEEE Std 802.1Q.
© IEEE 2011 – All rights reserved

IEEE Std 802.1BA-2011 LOCAL AND METROPOLITAN AREA NETWORKS
b) The time synchronization standard, IEEE Std 802.1AS.
c) The MAC and PHY standards specified for the various LAN MAC/PHY technologies, such as IEEE
Std 802.3, IEEE Std 802.11, ITU-T G.9960 and ITU-T G.9961 (Powerline), and MoCA.
These features and options are selected by means of the profiles described in Clause 7. These profiles
support specific functions within an AVB network, such as the Bridges and LAN technologies used to carry
the AV streams, and the end stations that attach to the LAN and that provide the source(s) and the
destination(s) of the stream data.
In some cases, there are functions that are needed in order to construct a usable AVB network, but that are
not described in any other standard. In those cases, the technical specification is included in Clause 6 of this
standard, along with a statement of the conformance requirements associated with the function, so that the
function can be referenced by a profile in the same way as functions defined in any other standard.
Clause 5 introduces the architecture for AVB systems and AVB networks, and some of the terminology used
in describing them.
1.4 Objectives
The architecture described in Clause 5, the AVB functions specified in Clause 6, and the profiles specified in
Clause 7, are intended to meet the following objectives:
a) Describe the components that can be combined to form an AVB network (i.e., a network whose
components cooperate and interoperate to allow the transmission of AV streams) and how those
components can be combined.
b) Describe some of the consequences and limitations for AVB streaming that result from the
incorporation of non-AV capable devices in an AVB network.
c) Define additional functions that are required for AVB operation that are not otherwise documented
in contributing standards.
d) Provide guidance in terms of meeting the end-to-end latency requirements for successful AVB
operation.
e) Define conformance requirements for AVB systems, in terms of the standards to which conformance
is required for the various system components and the optional features of those standards that are
required to be implemented. These conformance requirements address the guaranteed delivery, end-
to-end latency, and time synchronization requirements for successful AVB operation.
© IEEE 2011 – All rights reserved

AUDIO VIDEO BRIDGING (AVB) SYSTEMS IEEE Std 802.1BA-2011
2. Normative references
The following referenced documents are indispensable for the application of this document (i.e., they must
be understood and used, so each referenced document is cited in the text and its relationship to this
document is explained). For dated references, only the edition cited applies. For undated references, the
latest edition of the referenced document (including any amendments or corrigenda) applies.
1, 2 ®
IEEE Std 802 , IEEE Standard for Local and Metropolitan Area Networks: Overview and Architecture.
TM
IEEE Std 802.1Q , IEEE Standards for Local and Metropolitan Area Networks: Virtual Bridged Local Area
Networks.
TM
IEEE Std 802.1Qbb , IEEE Standards for Local and Metropolitan Area Networks: Virtual Bridged Local
Area Networks—Amendment: Priority-based Flow Control.
TM
IEEE Std 802.1AS , IEEE Standards for Local and Metropolitan Area Networks: Timing and
Synchronization for Time-Sensitive Applications in Bridged Local Area Networks.
TM
IEEE Std 802.3 , Information technology—Telecommunications and information exchange between
systems—Local and metropolitan area networks—Specific requirements—Part 3: Carrier sense multiple
access with collision detection (CSMA/CD) access method and physical layer specifications.
TM
IEEE Std 802.3az , Information technology—Telecommunications and information exchange between
systems—Local and metropolitan area networks—Specific requirements—Part 3: Carrier sense multiple
access with collision detection (CSMA/CD) access method and physical layer specifications—Amendment
5: Media Access Control Parameters, Physical Layers, and Management Parameters for Energy-Efficient
Ethernet.
TM
IEEE Std 802.11 , IEEE Standards for Local and Metropolitan Area Networks: Wireless LAN Medium
Access Control (MAC) and Physical Layer (PHY) specifications.
TM
IEEE Std 802.11n , IEEE Standards for Local and Metropolitan Area Networks: Wireless LAN Medium
Access Control (MAC) and Physical Layer (PHY) specifications—Amendment 5: Enhancements for Higher
Throughput.
TM
IEEE Std 802.11v , IEEE Standards for Local and Metropolitan Area Networks: Wireless LAN Medium
Access Control (MAC) and Physical Layer (PHY) specifications—Amendment 8: IEEE 802.11 Wireless
Network Management.
TM
IEEE P802.11aa /D5.0, IEEE Standards for Local and Metropolitan Area Networks: Wireless LAN
Medium Access Control (MAC) and Physical Layer (PHY) specifications—Amendment 2: MAC
Enhancements for Robust Audio Video Streaming.
ITU-T G.9960 (06/2010) Unified high-speed wireline based home networking transceivers—Revision 1.
IEEE publications are available from the Institute of Electrical and Electronics Engineers, Inc., 445 Hoes Lane, Piscataway, NJ 08854,
USA (http://standards.ieee.org/).
The IEEE standards or products referred to in this clause are trademarks of the Institute of Electrical and Electronics Engineers, Inc.
This IEEE standards project was not approved by the IEEE-SA Standards Board at the time this publication went to press. For
information about obtaining a draft, contact the IEEE.
ITU-T publications are available from the International Telecommunications Union, Place des Nations, CH-1211, Geneva 20,
Switzerland/Suisse (http://www.itu.int/).
© IEEE 2011 – All rights reserved

IEEE Std 802.1BA-2011 LOCAL AND METROPOLITAN AREA NETWORKS
ITU-T G.9961 (06/2010) Data link layer (DLL) for unified high-speed wire-line based home networking
transceivers.
MoCA MAC/PHY SPECIFICATION v2.0, (MoCA-M/P-SPEC-V2.0-20100507) Multimedia over Coax
Alliance (www.mocalliance.org).
© IEEE 2011 – All rights reserved

AUDIO VIDEO BRIDGING (AVB) SYSTEMS IEEE Std 802.1BA-2011
3. Definitions
For the purposes of this document, the following terms and definitions apply. The IEEE Standards
Dictionary: Glossary of Terms & Definitions should be consulted for terms not defined in this clause.
AV Bridge: relay device (e.g., an IEEE 802.1Q Bridge or an IEEE 802.11 access point) that conforms to the
requirements stated in the AVB profile for a Bridge as specified in this standard.
AVB domain: The intersection of an SRP domain and a gPTP domain.
NOTE—The term “SRP domain” is defined in IEEE Std 802.1Q. The term “gPTP domain” is defined in IEEE Std
802.1AS.
AVB network: A contiguous set of Bridges and end stations that meet the conformance requirements of this
standard.
AVB stream: A data stream associated with a stream reservation established using the Stream Reservation
Protocol (SRP).
AVB system: A system (a piece of equipment that implements Bridge and/or end station functionality) that
meets the conformance requirements for an AVB profile.
AVB profile: A set of feature and option selections that specifies aspects of Bridge and end station
operation, and states the conformance requirements for support of AVB functionality for a specific class of
user applications.
end station, station: These terms are defined in IEEE Std 802.
MRP participant: The MRP state machine that participates in MRP protocol, as defined in IEEE Std
802.1Q, Clause 10. There are four variants as follows:
a) Full Participant
b) Full Participant, point-to-point subset
c) Applicant-only Participant
d) Simple-Applicant Participant
Listener: An end station that is the destination, receiver, or consumer of a stream.
Talker: An end station that is the source, transmitter, or producer of a stream.
The IEEE Standards Dictionary: Glossary of Terms & Definitions is available at http://shop.ieee.org/.
Notes in text, tables, and figures are given for information only and do not contain requirements needed to implement the standard.
© IEEE 2011 – All rights reserved

IEEE Std 802.1BA-2011 LOCAL AND METROPOLITAN AREA NETWORKS
4. Acronyms and abbreviations
AV audio/video
AVB audio/video bridging
C-VLAN Customer VLAN (IEEE Std 802.1Q)
CSN coordinated shared network
EISS Extended Internal Sublayer Service (IEEE Std 802.1Q)
IPG inter packet gap
FID Filtering Identifier (IEEE Std 802.1Q)
FQTSS Forwarding and Queuing Enhancements for Time Sensitive Streams (IEEE Std 802.1Q)
G.hn ITU-T G.9960 and ITU-T G.9961
gPTP generalized precision time protocol
LAN Local Area Network (IEEE Std 802.1Q)
MTIE Maximum Time Interval Error
PCS Profile Conformance Statement
PICS Protocol Implementation Conformance Statement
PVID Port VLAN identifier (IEEE Std 802.1Q)
SFD start-of-frame delimiter
SR stream reservation (IEEE Std 802.1Q)
SR_PVID Stream Reservation Port VLAN Identifier (IEEE Std 802.1Q)
SRP Stream Reservation Protocol (IEEE Std 802.1Q)
MAC Media Access Control
MMRP Multiple MAC Registration Protocol (IEEE Std 802.1Q)
MSRP Multiple Stream Registration Protocol (IEEE Std 802.1Q)
MVRP Multiple VLAN Registration Protocol (IEEE Std 802.1Q)
TSpec traffic specification (IEEE Std 802.1Q)
VID VLAN identifier (IEEE Std 802.1Q)
VLAN Virtual LAN (IEEE Std 802.1Q)
© IEEE 2011 – All rights reserved

AUDIO VIDEO BRIDGING (AVB) SYSTEMS IEEE Std 802.1BA-2011
5. Architecture of AVB networks
This standard is concerned with the requirements for layer 2 support in bridged networks that support AV
traffic. In that context, an AVB network is considered to consist of the following:
a) End stations that act as Talkers
b) End stations that act as Listeners
c) End stations that act as both Talkers and Listeners
d) MAC Bridges that support the bridging requirements of the AVB network
e) Individual LANs that interconnect the Bridges, Talkers, and Listeners
NOTE—A non-exhaustive list of LAN technologies can be found in Table 6-1. For the purposes of this standard, LANs
are taken to include IEEE 802 LANs and any other LAN technologies that are able to provide the internal sublayer
service (ISS) defined in Clause 6 of IEEE Std 802.1Q.
Figure 5-1 gives an example of how these components can be combined in an AVB network.
Listener
end Talker &
Talker
Listener
station
end
end
station
station
AV AV AV AV
Bridge
Bridge Bridge Bridge
Listener
end
Listener Talker
station
end end
station station
AV
Bridge
AV
Listener
Bridge
Talker
end
end
station
station
Talker &
Listener
Listener
end
end
station
station
LAN
Figure 5-1—An AVB network
Practical installations of AVB equipment frequently include non-AVB components (Bridges and end
stations) that are connected to the AVB network, but do not themselves participate in the transmission, relay,
or receipt of AV traffic.
Figure 5-2 illustrates the effect of the establishment of AVB domains (6.4) on the ability of AVB systems to
communicate streams. End stations 1 and 2 are within AVB domain 1, and can therefore communicate
stream traffic between them, via the AV Bridge that connects them. Similarly, end stations 3, 4, and 5 are all
within AVB domain 2, and can therefore communicate stream traffic among them. However, because end
stations 1 and 3 are connected via a region of the network that is not AVB-capable, they are in distinct AVB
© IEEE 2011 – All rights reserved

IEEE Std 802.1BA-2011 LOCAL AND METROPOLITAN AREA NETWORKS
domains, and therefore cannot establish AVB stream communication between them, but all non-AVB
communications can and will continue between these end stations. End station 6 is the only device within
AVB domain 3, and therefore cannot establish AVB stream communication with any other AVB end station.
AVB end station 7 and AVB end station 8 are connected only to each other and form AVB domain 4, which
is isolated; stations 7 and 8 can only communicate with each other.
NOTE—Domain boundaries are detected; they are not created as a consequence of a registration process. A
consequence of the detection mechanism is that a given end station can only be a member of a single domain.
The non-AV Bridges shown in Figure 5-2 could either be conformant IEEE 802.1D or IEEE 802.1Q Bridges
that do not meet the minimum requirements of the AVB profile in use in the network, or they could be non-
conformant bridges that forward frames addressed to the reserved addresses in Table 8-1, Table 8-2, and
Table 8-3 of IEEE Std 802.1Q. In the former case, the detection of the domain boundary is the result of the
operation of MSRP; in the latter case, the boundary detection is achieved by the determination of
“asCapable” by the generalized precision time protocol (gPTP) defined in IEEE Std 802.1AS (see 10.2.4.1
of IEEE Std 802.1AS).
AVB domain 2
non-AVB
AVB
end
end
station
AVB
station 3
end
station 5
non-AV AV
Bridge Bridge
AV
Bridge
AV
non-AVB
Bridge
end
station AVB
end
station 4
AV
Bridge
non-AVB
non-AV
end
AVB
Bridge
AVB
station
end
end
station 6
station 1
AVB
AVB AVB
end
AVB domain 3
non- AVB
end end
station 2
end
station 7 station 8
station
AVB domain 1
AVB domain boundary port
AVB domain 4
LAN carrying non-AVB traffic
LAN carrying AVB traffic
Figure 5-2—AVB domain boundaries created by non-AVB systems
© IEEE 2011 – All rights reserved

AUDIO VIDEO BRIDGING (AVB) SYSTEMS IEEE Std 802.1BA-2011
AVB domain boundaries can also be created in a network if the priority to SR class associations are not
consistent across the network. For example, if some Bridges use the default values shown in Table 6-6 of
IEEE Std 802.1Q, where priority 3 is associated with SR Class A traffic and priority 2 is associated with SR
class B traffic, and others associate, say, priority 4 with SR class A traffic and priority 2 with SR class B
traffic, then, because AVB domains are created per SR class, all of the devices will be in the same AVB
domain for SR class B traffic, but adjacent devices that use different priorities for SR Class A traffic will be
in different AVB domains for SR class A traffic. This is illustrated in Figure 5-3, where the Bridges and end
stations in AVB domains 2 and 3 use priority 3 with SR class A, whereas AVB domain 4 uses priority 4 and
AVB domain 1 uses priority 5. AVB stream communication using SR class A cannot take place between end
stations in different AVB domains, regardless of the fact that all of the devices in the network are AVB-
capable (but non-AVB stream communication can take place). Even though AVB domain 2 and 3 both use
priority 3 for SR class A traffic, AVB streams cannot flow between the two domains because the AV Bridge
in AVB domain 1 does not use priority 3 for SR class A traffic and is therefore an AVB domain boundary
between AVB domains 2 and 3.
AVB domain 2
AVB domain 1
AVB
end
AVB
AVB
station 3
end
end
station 8
station 5
AV AV AV AV
Bridge Bridge Bridge Bridge
AVB
end
AVB AVB
SR class A
station 7
end end
uses priority 5
SR class A
station 4 station 9
uses priority 3
SR class A
uses priority 3
SR class A
AV
uses priority 4
Bridge
AV
AVB
Bridge
AVB
end
end
AVB domain boundary port
station 6
station 1
LAN carrying non-AVB traffic
AVB
end
LAN carrying AVB traffic
AVB
station 2
end
station 10
AVB domain 3 AVB domain 4
Figure 5-3—AVB domain boundaries created by different SR class A priorities
© IEEE 2011 – All rights reserved

IEEE Std 802.1BA-2011 LOCAL AND METROPOLITAN AREA NETWORKS
AVB domain boundaries can be different for different SR classes, because they are created as a consequence
of the priority values associated with each SR class in each AVB system. This is illustrated in Figure 5-4,
where the AVB domain boundaries for SR class B are different from those shown in Figure 5-3 for SR class
A, despite the underlying network connectivity being identical in both figures. Hence, end stations 2 and 7
(for example) can communicate using AVB stream traffic on SR class B, whereas they are not able to do so
using SR class A.
AVB domain 5
AVB domain 6
AVB
end
AVB
AVB
station 3
end
end
station 8
station 5
AV
AV AV AV
Bridge Bridge Bridge Bridge
AVB
end
AVB AVB
station 7
end end
SR class B
station 4 station 9
uses priority 4
AV
SR class B
Bridge uses priority 3
AV
AVB
AVB
end Bridge
end
station 1
AVB domain boundary port
station 6
AVB
LAN carrying non-AVB traffic
end
station 2
LAN carrying AVB traffic
AVB
SR class B
uses priority 2 end station
AVB domain 7
Figure 5-4—AVB domain boundaries created by different SR class B priorities
© IEEE 2011 – All rights reserved

AUDIO VIDEO BRIDGING (AVB) SYSTEMS IEEE Std 802.1BA-2011
6. AVB functions
This clause specifies additional functions that are important to the operation of an AVB system, but that are
not specified in the base standards that are used in constructing AVB systems.
6.1 En
...