Audio networking technologies have fundamentally shifted how audio signals are transported, routed, and managed across professional and consumer environments. From live sound reinforcement and broadcast studios to corporate AV systems and home installations, these networked systems offer unprecedented flexibility, scalability, and interoperability. However, the rapid adoption of protocols such as AES67, Dante, AVB, and Milan has introduced a complex web of legal and licensing considerations. Manufacturers, system integrators, and end users must navigate intellectual property rights, standards compliance, and contractual obligations to avoid infringement, ensure lawful operation, and protect investments. This article provides a comprehensive examination of the legal and licensing landscape surrounding audio networking technologies, offering actionable insights for stakeholders at every level.

The legal environment for audio networking is multilayered, encompassing patent law, copyright, trade secrets, and contract law. Companies that develop hardware or software for networked audio must rigorously assess their exposure to third-party intellectual property claims. Equally important is compliance with mandatory standards, which often carry licensing requirements enforced by standards development organizations (SDOs) or patent pools.

Intellectual Property Rights: Patents and Copyrights

Patents are the dominant form of IP protection in audio networking. Protocol-level innovations—such as synchronization mechanisms, clock recovery algorithms, and packet prioritization schemes—are frequently protected by granted patents. Manufacturers integrating these features into their products must secure patent licenses from the rights holders or through licensing pools. Failure to do so can result in costly litigation, import bans, or exclusion from key markets.

Copyright protection applies to firmware, driver software, management applications, and digital audio files transmitted over the network. Open-source licenses, such as the GNU General Public License (GPL) or Apache 2.0, may be used for certain components, but compliance with their terms is non-negotiable. Mixing proprietary and open-source code without understanding license compatibility can create legal exposure for both developers and users.

Patent Thickets and Licensing Pools

Audio networking technologies often involve dozens of overlapping patents held by multiple entities—a situation known as a patent thicket. To reduce transaction costs and litigation risks, many rights holders participate in patent pools. For example, the Via Licensing pool covers essential patents for audio codecs and networking protocols. Manufacturers can obtain a single license covering all pool patents, simplifying compliance. However, not all relevant patents may be included, and companies must evaluate pools alongside bilateral licensing strategies.

Software Licensing and Open Source

Software plays an increasingly critical role in audio networking, from embedded control systems to full-featured mixing and routing applications. Licensing models vary widely: some vendors offer per-device perpetual licenses, others use subscription-based models, and a growing number release core protocol stacks under permissive open-source licenses (e.g., MIT or BSD). The AES67 Linux implementation, for instance, is distributed under a BSD-style license, encouraging adoption while protecting contributors. End users must verify that their software licenses permit the intended use—commercial deployment often requires a different license than personal or educational use.

Importance of Standards Compliance

Standards are the bedrock of interoperability in audio networking. Without widely adopted specifications, devices from different manufacturers could not exchange audio and control data reliably. Standards bodies such as the Audio Engineering Society (AES), IEEE, and AVnu Alliance develop and maintain these specifications. Compliance is not only a technical best practice but often a legal or contractual necessity.

AES67 and Dante: Dominant Standards Compared

AES67 is a core standard for high-performance audio-over-IP interoperability. It defines transport, synchronization, and clocking parameters, enabling devices from different vendors to work together. The standard itself is available from the AES Standards website and is freely accessible; however, implementing AES67 may require licenses for underlying patented technologies. Many manufacturers choose to test and certify products through the AES67 interoperability program, which carries a fee and requires adherence to specific testing procedures.

Dante, developed by Audinate, is a proprietary protocol that has become a de facto standard in many industries. Unlike AES67, Dante is not an open standard—it is owned and controlled by Audinate. Manufacturers must sign a licensing agreement and pay royalties per device to use Dante. This model ensures interoperability across all Dante-enabled products but creates a dependency that some companies seek to avoid by using AES67 or other open alternatives. Audinate provides extensive developer licensing information on its website.

AVB/TSN and IEEE 1722

Audio Video Bridging (AVB) and its successor Time-Sensitive Networking (TSN) are IEEE standards that provide deterministic, low-latency transport over Ethernet. IEEE 1722 defines the Layer-2 packet format for AVB audio streams. While IEEE standards are openly available, implementations may use patented technology, and licensing terms vary. The Wikipedia page on Audio Video Bridging offers a helpful overview of the standards ecosystem. The AVnu Alliance provides certification programs that require license fees and demonstrate conformity to the standards.

Milan: A User-Led Interoperability Layer

Milan is a protocol specification built on AVB/TSN, created by a consortium of AV industry leaders. It adds a mandatory device behavior and interoperability layer that simplifies system design. Milan certification requires manufacturers to license the specification from the AVnu Alliance and pass compliance testing. For end users, specifying Milan-certified devices reduces integration risk, but the licensing costs for manufacturers may be passed downstream.

Licensing Models in Practice

Understanding the different licensing models used in audio networking is essential for procurement and deployment planning. The costs and obligations associated with each model can significantly affect total cost of ownership.

Per-Device Royalties

This is the most common model for proprietary protocols like Dante. The manufacturer pays a royalty to the protocol owner for each device that implements the technology. The amount may vary based on device type (e.g., microphone, amplifier, DSP) and volume. These costs are typically factored into the product's selling price, so end users indirectly bear them. Licensing agreements often include audit rights, requiring manufacturers to report sales volumes accurately.

Subscription-Based or Perpetual Licensing for Software

Software defined audio networks, such as those using Q-SYS or Dante Virtual Soundcard, often offer subscription or perpetual licenses. Subscriptions provide lower upfront costs but ongoing expense, while perpetual licenses require a larger initial payment but no recurring fees. End users must ensure that licenses cover the intended number of channels, devices, or endpoints. Over-provisioning can lead to compliance breaches, while under-licensing may disable features.

Open Source and Royalty-Free Models

Some protocols, such as RTSP, RTP, and certain audio codecs (e.g., Opus), are royalty-free or covered by open-source licenses that do not restrict commercial use. However, even royalty-free standards may involve patent claims that require defensible non-assert agreements. For example, the AES67 implementation distributed under a BSD license does not grant patent immunity; implementers must independently clear patents.

Implications for System Integrators and End Users

Legal and licensing considerations are not the sole domain of manufacturers. Integrators and end users can face significant liability if they deploy systems that infringe on IP or violate license terms. Due diligence is essential.

Due Diligence Checklist for Procurement

  • Verify that all hardware and software used in the system is covered by appropriate licenses for the intended commercial application.
  • Request written confirmation from manufacturers that their products are licensed for the protocols they support—especially for Dante, Milan, or AVB.
  • Review end-user license agreements (EULAs) for DSP software, control applications, and digital audio workstations to ensure no restrictions on networked use.
  • Confirm that firmware updates and software patches are included in the license without additional fees.
  • For open-source components, obtain a bill of materials and check for license compatibility (e.g., copyleft vs. permissive).

Risk Mitigation Strategies

To minimize legal exposure, integrators should contractually require manufacturers and vendors to indemnify them against third-party IP claims. Insurance policies that cover intellectual property infringement may also be warranted for large-scale deployments. In multi-vendor environments, using a common standards-based protocol like AES67 can reduce reliance on a single proprietary license, lowering overall risk.

Regional and Export Considerations

Audio networking technologies are global, but legal requirements differ by jurisdiction. The United States, European Union, China, and Japan each have distinct patent enforcement regimes, standards compliance mandates, and data privacy laws.

In the EU, the General Data Protection Regulation (GDPR) may apply if audio networking systems capture or transmit personally identifiable information (e.g., VoIP or intercom systems). In China, encryption and network access controls may require compliance with local standards such as GM/T or GB/T. Export controls, particularly for encryption hardware, can restrict the sale of audio network devices to certain countries. Manufacturers and distributors must ensure they have the necessary export licenses and country-specific certifications (e.g., CE, FCC, CCC).

As audio networking moves toward higher channel counts, lower latency, and cloud-managed infrastructures, new legal challenges emerge. The rise of Audio-over-IP (AoIP) in broadcast, automotive, and IoT applications will likely attract more patent litigation. Standards bodies are exploring more flexible licensing terms, such as the "reasonable and non-discriminatory" (RAND) model used by IEEE for some TSN patents. Meanwhile, the open-source movement continues to push for fully royalty-free alternatives, exemplified by the Network Audio Group's work on the milan-over-tsn specification.

End users should monitor the evolution of protocol licensing because changes can affect compatibility and upgrade costs. For example, if a previously royalty-free protocol becomes encumbered by new patent claims, manufacturers may need to alter their product lines. Staying informed through industry bodies such as the AES, AVnu Alliance, and open-source communities is essential for long-term planning.

Conclusion

Navigating the legal and licensing aspects of audio networking technologies requires a strategic approach that balances innovation with risk management. Manufacturers must secure patent licenses, comply with standards, and carefully choose between proprietary and open-source models. Integrators and end users must perform thorough due diligence, understand contractual obligations, and anticipate regional variations. By prioritizing legal clarity and proactive compliance, all stakeholders can enjoy the operational benefits of networked audio while minimizing exposure to disputes and unexpected costs. As the ecosystem continues to expand, staying educated on these issues will remain a cornerstone of successful audio system deployment.