| AVB | |
|---|---|
 AVnu certification mark | |
| Manufacturer info | |
| Manufacturer | IEEE, AVnu |
| Development date | September 2011; 13 years ago (September 2011) |
| Network compatibility | |
| Switchable | Yes |
| Routable | No |
| Ethernetdata rates | Agnostic |
| Audio specifications | |
| Minimumlatency | 2 ms (maximum)[1] |
| Maximum channels per link | 256 |
| Maximumsampling rate | 192kHz[2] |
| Maximumbit depth | 32-bit floating point[2]: clause 8.3 |
Audio Video Bridging (AVB) is a common name for a set oftechnical standards that provide improved synchronization, low latency, and reliability forswitchedEthernet networks.[3] AVB embodies the following technologies and standards:
IEEE 802.1Qat and 802.1Qav amendments have been incorporated to the baseIEEE 802.1Q-2011 document, which specifies the operation ofMedia Access Control (MAC) Bridges andVirtual Bridged Local Area Networks.
AVB was initially developed by theInstitute of Electrical and Electronics Engineers (IEEE) Audio Video Bridging task group of theIEEE 802.1 standards committee. In November 2012, Audio Video Bridging task group was renamed toTime-Sensitive Networking task group to reflect the expanded scope of its work, which is to "provide the specifications that will allow time-synchronized low latency streaming services throughIEEE 802 networks".[5] Further standardization efforts are ongoing in IEEE 802.1 TSN task group.
To help ensure interoperability between devices that implement the AVB and TSN standards, theAVnu Alliance develops device certification for the automotive, consumer, and professional audio and video markets.[6]
Analog audio video (AV) equipment historically used one-way, single-purpose, point-to-point connections. Even digital AV standards, such asS/PDIF for audio and theserial digital interface (SDI) for video, retain these properties. This connection model results in large masses of cables, especially in professional applications and high-end audio.[7]
Attempts to solve these problems were based on multi-point network topologies, such asIEEE 1394 (FireWire), and included adaptation of standard switchedcomputer network technologies such asAudio over Ethernet andAudio over IP. Professional, home, and automotive AV solutions came to use specialized protocols that do not interoperate between each other or standard IT protocols, while standard computer networks did not provide tightquality of service with strict timing and predictable or bounded latency.[7]
To overcome these limitations, Audio Video Bridging networks transmit multiple audiovisual streams through standardEthernet switches (i.e.MAC bridges) connected in ahierarchical tree topology. AVB includeslayer 2 protocols to reserve connection bandwidth and prioritise network traffic, which guarantee precise sync clock and low transmission latency for each stream.[7]
Tight sync between multiple AV streams is needed forlip sync between video and related audio streams, to keep multiple digitally connected speakers in phase in a professional environment (which requires 1 μs precision), and to prevent audio or video packets from arriving late to the endpoint, resulting in a dropped frame of video and unwanted audio glitches such as a pop or silence. Worst-case delay, including source and destination buffering, is required to be low and deterministic: the user-interface delay shall be around 50 ms, so that the pressing of a button and the resulting action are perceived as happening instantly, and 2 ms for live performance or studio work.[7]
Audio Video Bridging is implemented as a switched Ethernet network that works by reserving a fraction of the available Ethernet for AV traffic. The AVB architecture introduces three primary differences:
The IEEE 802.1BA is an umbrella standard for these three principal technologies, which defines application-specific configurations and operation procedures for devices in switched audio video networks.
The newlayer-2 configuration protocols work with backward-compatible extensions to the Ethernet 802.1 frame format; such minimal changes allow AVB devices to coexist and communicate in standard IT networks, however, only AVB-capable switches and endpoint can reserve network resources with admission control and synchronize local time to a master clock, which is required for low latency time-sensitive traffic.
AVB traffic is replicated in a multicast manner, with one talker (stream initiator) and multiple listeners. AVB packets are sent at regular intervals in the allocated time slots, preventing collisions for AV traffic. AVB guarantees a latency of 2 ms for Class A traffic and 50 ms for Class B traffic over a maximum of 7 hops, with a transmission period of 125 μs for Class A and 250 μs for Class B traffic.
An IEEE 802.1AS network timing domain includes all devices that communicate using the gPTP protocol. The grandmaster is a device chosen as the reference clock; the 802.1BA specification requires every talker and network bridge to be grandmaster capable.
802.3 link management and 802.1AS link delay measurement protocols calculate the round-trip delay to the AVB endpoint; this needs to be better than worst-case wire delay from the 802.1AS peer delay algorithm.
Higher-level protocols may use 802.1AS clock information to set the exact presentation time for each AV stream.
IEEE Std 1722-2011[8] for aLayer 2 Audio Video Transport Protocol (AVTP) defines details for transmittingIEEE 1394/IEC 61883 streams and other AV formats, setting the presentation time for each AV stream, and manage latencies from worst case delay calculated by the gPTP protocol.
IEEE Std 1722.1-2013[9] is a standard that provides AVB discovery, enumeration, connection management, and control (AVDECC) of devices using IEEE Std 1722-2011. AVDECC defines operations to discover device addition and removal, retrieve device entity model, connect and disconnect streams, manage device and connection status, and remote control devices.
Higher layer services can improve synchronisation and latency of media transmission by mapping the AVB Stream ID to internal stream identifiers to and basing internal timestamps on gPTP master clock.
IEEE Std 1733-2011[10] defines aLayer 3 protocol profile forReal-time Transport Protocol (RTP) applications with aRTCP payload format, which assigns the Stream ID from SRP to the RTP's Synchronization source identifier (SSRC), and correlates RTP timestamps for presentation time with 802.1AS gPTP master clock.
AES67 is based on standard RTP overUDP/IP and IEEE 1588Precision Time Protocol (PTPv2) for timing; interoperability with AVB/TSN can be achieved by linking IEEE 802.1AS timing information to AES67 PTPv2 payload data.[11][12][13][14]
AES67 implementation with AVB interoperability has been demoed at InfoComm 2016.[15][16]
In 2018, theAvnu Alliance announced the Milan initiative to promote interoperability of AVB devices and provide product certification and testing.[17]
The specification requires media clocking based on the AVTP CRF (Clock Reference Format) and sample rate of 48 kHz (optionally 96 and 192 kHz); audio stream format is based on AVTPIEC 61883-6 32-bit Standard AAF Audio Format with 1 to 8 audio channels per stream (optionally, 24- and 32-bit High Capacity Format with 56 and 64 channels). Redundancy is provided with two independent logical networks for every endpoint and a seamless switchover mechanism.[17]
![[icon]](/mt/?noimg=&dark=on&url=https%3a%2f%2fwikipedia.org%2fwiki%2fFile%3aWiki_letter_w_cropped.svg) | This sectionneeds expansion. You can help byadding to it.(August 2019) |
The IETFDeterministic Networking (DetNet) Working Group is working to define deterministic data paths with bounds on latency, loss, and packet delay variation (jitter), and high reliability. DetNet shall operate over both Layer 2 bridged segments and Layer 3 routed segments, relying on interoperability with AVB/TSN switches when possible.[18]
One of the possible application of DetNet is professional audio/video, such as music and film production, broadcast, cinema, live sound, and large venue (stadiums, halls, conference centers, theme parks, airports, train terminals, etc.) systems for public addressing, media streaming and emergency announcement. The stated goal is to enable geographically distributed, campus- or enterprise-wideIntranet for content delivery with bounded low latency (10-15 ms). A single network shall handle both A/V and IT traffic, with Layer 3 routing on top of AVB QoS networks to enable sharing content between Layer 2 AVB segments, and provideIntServ andDiffServ integration with AVB where possible. Unused reserved bandwidth shall be released for best-effort traffic. The protocol stack shall have Plug-and-play capabilities from top to bottom to reduce manual setup and administration, allow quick changes of network devices and network topology.[19]
Large-scale AVB networks, like those used by theESPNSportsCenter "Digital Center 2" broadcast facility, which hosts multiple individual studios, are laid with many miles of fiber and have ten Tbit/s of bandwidth for a hundred thousand signals transmitted simultaneously; in the absence of standards-based solution to interconnect individual AVB segments, a customsoftware-defined networking router is required.[20][21]
The work on A/V streaming started at theIEEE 802.3re 'ResidentialEthernet' study group in July 2004.[22] In November 2005, it was moved to theIEEE 802.1 committee responsible forcross-network bridging standards.[23]
| Standard | Title | Status | Publication Date |
|---|---|---|---|
| Audio Video Bridging (AVB) specifications | |||
| IEEE 802.1BA-2011 | Audio Video Bridging (AVB) Systems | Superseded by IEEE 802.1BA-2021 | 30 September 2011 |
| IEEE 802.1Qav-2009 | Forwarding and Queuing Enhancements for Time-Sensitive Streams (FQTSS) | Incorporated into IEEE 802.1Q-2011 Clause 34 | 5 January 2010 |
| IEEE 802.1Qat-2010 | Stream Reservation Protocol (SRP) | Incorporated into IEEE 802.1Q-2011 Clause 35 | 30 September 2010 |
| IEEE 802.1Q-2011 | Media Access Control (MAC) Bridges andVirtual Bridged Local Area Networks(incorporates IEEE 802.1Qav and 802.1Qat amendmends) | Superseded by IEEE 802.1Q-2014/2018/2022 | 31 August 2011 |
| IEEE 802.1AS-2011 | Timing and Synchronization for Time-Sensitive Applications in Bridged Local Area Networks (gPTP) | Superseded by IEEE 802.1AS-2020 | 30 March 2011 |
| Time-Sensitive Networking (TSN) specifications | |||
| IEEE 802.1AS-2020 | Timing and Synchronization for Time-Sensitive Applications (gPTP) | Current,[24][25] amended by 802.1AS-2020/Cor1-2021[26] | 30 January 2020 |
| IEEE 802.1BA-2021 | TSN profile for Audio Video Bridging (AVB) Systems | Current[27] | 12 December 2021 |
| IEEE 802.1Q-2022 | Bridges and Bridged Networks | Current[28] | 22 December 2022 |
| Audio Video Transport Protocol (AVTP) and AVDECC specifications | |||
| IEEE 1733-2011 | Layer 3 Transport Protocol for Time-Sensitive Applications in Local Area Networks (RTP) | Current | 25 April 2011 |
| IEEE 1722-2011 | Layer 2 Transport Protocol for Time-Sensitive Applications in a Bridged Local Area Network (AVTP) | Superseded by IEEE 1722-2016 | 6 May 2011 |
| IEEE 1722-2016 | Layer 2 Transport Protocol for Time-Sensitive Applications in a Bridged Local Area Network (AVTP) | Current | 16 December 2016 |
| IEEE P1722b | AVTP - Amendment: New and Extended Streaming Formats | preparation | - |
| IEEE 1722.1-2013 | Device Discovery, Enumeration, Connection Management and Control Protocol (AVDECC) | Current | 23 August 2013 |
