3855 SW 153rd Dr.
Beaverton, OR 97006 USA
Tel: +1 503-619-0571
Fax: +1 503-644-6708
Please find below a collection of documents available for public download to include organization documents, technical whitepapers, and other industry resources.
If you are interested in contributing material for posting on the AVnu Alliance web site, please view the Requirements for Posting.
AVnu Alliance Best Practices
- Stream Reservation Protocol
In 2007, the IEEE 802.1 “Audio/Video Bridging Task Group” started developing a series of specifications targeted to optimize time-synchronized low-latency media streaming services through IEEE 802 networks. One of these specifications, now a part of 802.1Q-2011, describes a protocol known as the Stream Reservation Protocol (SRP) that allows network endpoints to reserve bandwidth across a compliant network. This document provides a high-level overview of the SRP protocol, focusing primarily on the application interfaces that it provides to end points and the way that the protocol propagates information about streams throughout the network. Detailed descriptions of the low-level operational details are mostly ignored, except in cases where the details place restrictions on how the higher-level interfaces can be used. The descriptions in this document are meant as a guide to implementers of end point software and should not be taken as a normative specification. Other methods of interpreting the standards may also be valid, and readers of this document are encouraged to refer to 802.1Q-2011 for the precise specification details. Read More >>>
- AVB Software Interfaces and Endpoint Architecture Guidelines
Starting in 2007, the IEEE Std. 802.1 “AV Bridging Task Group” developed a series of specifications to optimize time-synchronized, low latency media streaming services through IEEE 802 networks. The working group produced companion specifications IEEE Std. 802.1AS™-2011 (for time synchronization), IEEE Std. 802.1Qav™-2009 for traffic shaping, and IEEE Std. 802.1Qat™-2010 for resource reservation. These protocols are merged into IEEE Std. 802.1BA™-2011, IEEE Std. 802.1Q™-2011 and IEEE Std. 802.1AS™-2011 – which are collectively referred to as “AVB”. This document provides a suggested architecture for implementing the components of an AVB endpoint. It provides some background material that motivates the design of the AVB protocols, briefly describes the hardware and software components involved in an AVB endpoint, and then gives a detailed look at the interfaces and dynamic behavior of the core AVB protocols. Many valid implementations can be realized with different combinations of operating system-specific features and hardware-optimized solutions to address the needs of specific market segments. At present, the scope of the detailed protocol descriptions extends only to the highest-level interface of each of the core protocols. Higher-level management protocols, ancillary utility protocols, and lower-level protocols that the core protocols are built upon are not described in detail. Those may be dealt with in future revisions of this document or other documents yet to be published. Read More >>>
Contents herein are not necessarily endorsed by AVnu Alliance, and solely represent respective authors or companies' views.