Standard-Essential Patents in Software: FRAND Licensing and Interoperability

Standard-essential patents sit at the intersection of innovation and interoperability. When an industry standard body adopts a technology that is covered by a patent, that patent becomes "essential" to implementing the standard. Anyone building products that comply with the standard may need a license.

This guide explains how SEPs work, what obligations they create, and how software companies can manage their exposure.

What Are Standard-Essential Patents

A standard-essential patent covers technology that is technically necessary to implement a recognized industry standard. Standards bodies like IEEE, ETSI, W3C, and IETF develop these standards to enable interoperability across products and vendors.

• Wireless connectivity: Wi-Fi (IEEE 802.11), Bluetooth, 4G/5G cellular standards
• Video and audio: H.264, H.265, MPEG codecs, and emerging media formats
• Web protocols: HTTP/2, WebSocket, TLS implementations
• Data formats: Certain compression, encoding, or serialization standards

FRAND Licensing Obligations

When patent holders contribute technology to a standards body, they typically commit to licensing on FRAND terms: Fair, Reasonable, and Non-Discriminatory. This commitment is intended to balance the patent holder's right to compensation with the implementer's need for access.

1. Fair and Reasonable: License fees should reflect the value of the patented technology, not the value of being included in the standard itself
2. Non-Discriminatory: Similar licensees should receive similar terms, preventing favoritism toward certain competitors
3. Good faith negotiation: Both parties are generally expected to engage in negotiation before resorting to litigation

How SEPs Affect Software Companies

Software companies encounter SEP obligations in several common scenarios:

• Implementing connectivity protocols that rely on patented radio or networking technologies
• Using media codecs for video or audio processing in applications
• Building on web standards that incorporate patented compression or security methods
• Deploying IoT devices that implement wireless communication standards

Navigating SEP Licensing

Several frameworks exist for resolving SEP licensing discussions:

1. Patent pools: Organizations like MPEG LA and Via Licensing aggregate SEPs from multiple holders into single license programs, simplifying access for implementers
2. Bilateral negotiation: Direct discussions between the patent holder and the implementer, guided by FRAND principles
3. Court-determined rates: When parties cannot agree, courts may set FRAND rates based on comparable license analysis and technical apportionment
4. Standards body dispute resolution: Some standards organizations offer mediation or arbitration processes

SEP Risk Management for Software Companies

1. Conduct a standards audit. Identify which industry standards your products implement, directly or through third-party libraries
2. Map SEP exposure. Review the patent declarations associated with each standard to understand the licensing landscape
3. Evaluate existing licenses. Determine whether your chip suppliers, SDK providers, or platform vendors already hold licenses that cover your use
4. Engage proactively. If you identify unresolved SEP exposure, initiating contact with the patent holder or pool administrator may be advantageous
5. Consider freedom-to-operate analysis as part of your product launch planning

Sources

• DOJ/USPTO Policy Statement on SEPs (2019)
• IEEE Patent Policy
• Idea Partnership: Software Patent Development