AVB | |
---|---|
Manufacturer Info | |
Manufacturer | IEEE, AVnu |
Development date | September 2011 |
Network Compatibility | |
Switchable | Yes |
Routable | No |
Ethernet data rates | Agnostic |
Audio Specifications | |
Minimum latency | 2 ms (maximum) [1] |
Maximum channels per link | 256 |
Maximum sampling rate | 192 kHz [2] |
Maximum bit depth | 32-bit floating point [2] : clause 8.3 |
Audio Video Bridging (AVB) is a common name for a set of technical standards that provide improved synchronization, low latency, and reliability for switched Ethernet networks. [3] AVB embodies the following technologies and standards:
IEEE 802.1Qat and 802.1Qav amendments have been incorporated to the base IEEE 802.1Q-2011 document, which specifies the operation of Media Access Control (MAC) Bridges and Virtual Bridged Local Area Networks.
AVB was initially developed by the Institute of Electrical and Electronics Engineers (IEEE) Audio Video Bridging task group of the IEEE 802.1 standards committee. In November 2012, Audio Video Bridging task group was renamed to Time-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 through IEEE 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, the AVnu 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 as S/PDIF for audio and the serial 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 as IEEE 1394 (FireWire), and included adaptation of standard switched computer network technologies such as Audio over Ethernet and Audio 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 tight quality of service with strict timing and predictable or bounded latency. [7]
To overcome these limitations, Audio Video Bridging networks transmit multiple audiovisual streams through standard Ethernet switches (i.e. MAC bridges) connected in a hierarchical tree topology. AVB includes layer 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 for lip 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 new layer-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 a Layer 2 Audio Video Transport Protocol (AVTP) defines details for transmitting IEEE 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 a Layer 3 protocol profile for Real-time Transport Protocol (RTP) applications with a RTCP 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 over UDP/IP and IEEE 1588 Precision 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, the Avnu 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 AVTP IEC 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]
This section needs expansion. You can help by adding to it. (August 2019) |
The IETF Deterministic 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-wide Intranet 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 provide IntServ and DiffServ 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 the ESPN SportsCenter "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 custom software-defined networking router is required. [20] [21]
The work on A/V streaming started at the IEEE 802.3re 'Residential Ethernet' study group in July 2004. [22] In November 2005, it was moved to the IEEE 802.1 committee responsible for cross-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 and Virtual 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 |
IEEE 802.1 is a working group of the IEEE 802 project of the IEEE Standards Association.
Clock synchronization is a topic in computer science and engineering that aims to coordinate otherwise independent clocks. Even when initially set accurately, real clocks will differ after some amount of time due to clock drift, caused by clocks counting time at slightly different rates. There are several problems that occur as a result of clock rate differences and several solutions, some being more acceptable than others in certain contexts.
The Precision Time Protocol (PTP) is a protocol for clock synchronization throughout a computer network with relatively high precision and therefore potentially high accuracy. In a local area network (LAN), accuracy can be sub-microsecond – making it suitable for measurement and control systems. PTP is used to synchronize financial transactions, mobile phone tower transmissions, sub-sea acoustic arrays, and networks that require precise timing but lack access to satellite navigation signals.
Profinet is an industry technical standard for data communication over Industrial Ethernet, designed for collecting data from, and controlling equipment in industrial systems, with a particular strength in delivering data under tight time constraints. The standard is maintained and supported by Profibus and Profinet International, an umbrella organization headquartered in Karlsruhe, Germany.
EtherCAT is an Ethernet-based fieldbus system developed by Beckhoff Automation. The protocol is standardized in IEC 61158 and is suitable for both hard and soft real-time computing requirements in automation technology.
In audio and broadcast engineering, audio over Ethernet (AoE) is the use of an Ethernet-based network to distribute real-time digital audio. AoE replaces bulky snake cables or audio-specific installed low-voltage wiring with standard network structured cabling in a facility. AoE provides a reliable backbone for any audio application, such as for large-scale sound reinforcement in stadiums, airports and convention centers, multiple studios or stages.
Carrier Ethernet is a marketing term for extensions to Ethernet for communications service providers that utilize Ethernet technology in their networks.
Stream Reservation Protocol (SRP) is an enhancement to Ethernet that implements admission control. In September 2010 SRP was standardized as IEEE 802.1Qat which has subsequently been incorporated into IEEE 802.1Q-2011. SRP defines the concept of streams at layer 2 of the OSI model. Also provided is a mechanism for end-to-end management of the streams' resources, to guarantee quality of service (QoS).
The Time-Triggered Ethernet standard defines a fault-tolerant synchronization strategy for building and maintaining synchronized time in Ethernet networks, and outlines mechanisms required for synchronous time-triggered packet switching for critical integrated applications and integrated modular avionics (IMA) architectures. SAE International released SAE AS6802 in November 2011.
Synchronous Ethernet, also referred as SyncE, is an ITU-T standard for computer networking that facilitates the transference of clock signals over the Ethernet physical layer. This signal can then be made traceable to an external clock.
HDBaseT is a consumer electronic (CE) and commercial connectivity standard for transmission of uncompressed ultra-high-definition video, digital audio, DC power, Ethernet, USB 2.0, and other control communication over a single category cable up to 100 m (328 ft) in length, terminated using 8P8C modular connectors. The conductors, cable, and connectors are as used in Ethernet networks, but are not otherwise exchangeable. HDBaseT technology is promoted and advanced by the HDBaseT Alliance.
Media-accelerated Global Information Carrier (MaGIC) is an audio over Ethernet protocol developed by Gibson Guitar Corporation in partnership with 3COM. It allows bidirectional transmission of multichannel audio data, control data, and instrument power.
White Rabbit is the name of a collaborative project including CERN, GSI Helmholtz Centre for Heavy Ion Research and other partners from universities and industry to develop a fully deterministic Ethernet-based network for general purpose data transfer and sub-nanosecond accuracy time transfer. Its initial use was as a timing distribution network for control and data acquisition timing of the accelerator sites at CERN as well as in GSI's Facility for Antiproton and Ion Research (FAIR) project. The hardware designs as well as the source code are publicly available. The name of the project is a reference to the White Rabbit appearing in Lewis Carroll's novel Alice's Adventures in Wonderland.
RTP-MIDI is a protocol to transport MIDI messages within Real-time Transport Protocol (RTP) packets over Ethernet and WiFi networks. It is completely open and free, and is compatible both with LAN and WAN application fields. Compared to MIDI 1.0, RTP-MIDI includes new features like session management, device synchronization and detection of lost packets, with automatic regeneration of lost data. RTP-MIDI is compatible with real-time applications, and supports sample-accurate synchronization for each MIDI message.
Avnu Alliance is a consortium of member companies working together to create an interoperable ecosystem of low-latency, time-synchronized, highly reliable networking devices using the IEEE open standard, Time-Sensitive Networking (TSN) and its Pro AV networking protocol, Milan. Avnu Alliance creates comprehensive certification programs to ensure interoperability of network devices. In the Professional Audio Video (AV) industry, Alliance member companies worked together to develop Milan: a standards-based, user-driven deterministic network protocol for professional media, that through certification, assures devices will work together at new levels of convenience, reliability, and functionality. Milan™ is a standards-based deterministic network protocol for real time media. Avnu Members may use the Avnu-certified or Milan-certified logo on devices that pass the conformance tests from Avnu. Not every device based on AVB or TSN is submitted for certification to the Avnu Alliance. The lack of the Avnu logo does not necessarily imply a device is incompatible with other Avnu-certified devices. The Alliance, in conjunction with other complimentary standards bodies and alliances, provides a united network foundation for use in professional AV, automotive, industrial control and consumer segments.
AES67 is a technical standard for audio over IP and audio over Ethernet (AoE) interoperability. The standard was developed by the Audio Engineering Society and first published in September 2013. It is a layer 3 protocol suite based on existing standards and is designed to allow interoperability between various IP-based audio networking systems such as RAVENNA, Wheatnet, Livewire, Q-LAN and Dante.
Time-Sensitive Networking (TSN) is a set of standards under development by the Time-Sensitive Networking task group of the IEEE 802.1 working group. The TSN task group was formed in November 2012 by renaming the existing Audio Video Bridging Task Group and continuing its work. The name changed as a result of the extension of the working area of the standardization group. The standards define mechanisms for the time-sensitive transmission of data over deterministic Ethernet networks.
The following is a comparison of audio over Ethernet and audio over IP audio network protocols and systems.
Industrial automation systems consisting of several distributed controllers need a precise synchronization for commands, events and process data. For instance, motors for newspaper printing are synchronized within some 5 microseconds to ensure that the color pixels in the different cylinders come within 0.1 mm at a paper speed of some 20 m/s. Similar requirements exist in high-power semiconductors and in drive-by-wire vehicles. This synchronisation is provided by the communication network, in most cases Industrial Ethernet. Many ad-hoc synchronization schemes exist, so IEEE published a standard Precision Time Protocol IEEE 1588 or "PTP", which allows sub-microsecond synchronization of clocks. PTP is formulated generally, so concrete applications need a stricter profile. In particular, PTP does not specify how the clocks should operate when the network is duplicated for better resilience to failures.
Deterministic Networking (DetNet) is an effort by the IETF DetNet Working Group to study implementation of deterministic data paths for real-time applications with extremely low data loss rates, packet delay variation (jitter), and bounded latency, such as audio and video streaming, industrial automation, and vehicle control.