Opus专利列表

2023-12-21 20:20
文章标签 列表 专利 opus

本文主要是介绍Opus专利列表,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

https://datatracker.ietf.org/ipr/search/?option=document_search&document_search=draft-ietf-codec-opus

Broacom 的专利是

美国专利号:US 7,353,168

名称:Method and apparatus to eliminate discontinuities in adaptively filtered signals

Gualcomm 的专利是

美国专利号:US 7,519,535;
            US 5 ,579,433; 
            US 5,414,796;
            US 5,657,420;
            US 5,341,456;
            US 5,742,734  

Skype 专利是
PI 0721316-6 (Brazil)
2679476 (Canada)
200780051547.2 (China)
07872475.4 (Europe)
2009-550325 (Japan)
12/006057 (US)

US-2008-0201137-A1
US-2010-0174535-A1
US-2010-0174534-A1
US-2010-0174547-A1
US-2010-0174532-A1
US-2010-0174537-A1
US-2010-0174542-A1
US-2010-0174531-A1
US-2010-0174541-A1
US-2010-0174538-A1
US-2011-0077940-A1

 

 

Opus licensing

Opus has a freely available specification, a BSD licensed, high-quality reference encoder and decoder, and protective, royalty-free licenses for the required patents. The copyright and patent licenses for Opus are automatically granted to everyone and do not require application or approval. The Opus FAQ has more information on why Opus is freely licensed.

 

In brief:
(see below for details)
✔You can encode or decode Opus-compatible streams for any purpose at no cost.
✔You can integrate the reference Opus encoder and decoder in any application, program, or product, even commercially, at no cost.
✔You can create your own compatible implementations of the Opus specification and give them away or sell them.
✘You may not do these things if you engage in Opus-related patent litigation against any user of Opus.

 

Licensing details

Copyright

Specification

The specification is freely available as part of IETF RFC 6716. The RFC includes the reference implementation, which is available under the three-clause BSD license (see below).

Implementation

Both the reference implementation and the revised implementations on opus-codec.org are available under the three-clause BSD license. This BSD license is compatible with all common open source and commercial software licenses.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: - Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. - Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. - Neither the name of Internet Society, IETF or IETF Trust, nor the names of specific contributors, may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Tools

Most of the command-line Ogg-based tools that are shipped as part of the separate opus-tools package are also released under the three-clause BSD license. The only exception is the opusinfo tool, which is released under the GPLv2 license. Proprietary software developers wishing to use Opus may copy code from opusenc and opusdec, but they may not copy code from the opusinfo tool to build their applications.

Patents

Opus is covered by several patents. These patents are available under open-source compatible, royalty-free licenses. If you are not trying to attack Opus with your patents, you will not have problems with these licenses.

Xiph.Org Foundation

The Xiph.Org foundation has several patent applications on techniques used in Opus. When issued, these patents will be automatically available under the terms provided in the below license. The license covers the listed patent applications, along with any other patent or application covering Opus that is owned by Xiph.Org.

Xiph.Org
Patents/Applications covered
  • US 61/284,154
  • US 61/450,041
  • US 61/450,053
  • US 61/450,060
  • and any other applicable

License Grant. Xiph.Org Foundation (“Xiph”) hereby grants to you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this license) license under Licensed Patents to make, have made, use, offer to sell, sell, import, transfer, and otherwise run, modify (in a way that still complies with the Specification), and reproduce any Implementation.

Definitions. Specification means, and includes the following, both individually and collectively, (a) any standard specification of the Opus codec adopted by the IETF Codec Working Group (“Standard”) and (b) any reference implementation (each, a “Reference Implementation”) published by the IETF Codec Working Group in the request for comments (“RFC”) issued by the IETF for the Specification draft for which this License is issued, or any RFC that is issued as an update or new version thereof. An Implementation means any Reference Implementation, or another implementation that complies with the Specification. Licensed Patents means all patents currently owned by Xiph or acquired hereafter that Xiph has the right to license as set forth above and that are necessarily infringed by the Specification, where “necessarily infringed” means: in the case of (a) above, there is no commercially viable means of implementing the Specification without infringing such patent; in the case of (b) above, use of the reference implementation to the extent it infringes such patent.

Termination. If you, directly or indirectly via controlled affiliate or subsidiary, agent, or exclusive licensee, file a Claim for patent infringement against any entity alleging that an Implementation in whole or in part constitutes direct or contributory patent infringement, or inducement of patent infringement (a “Claim”), provided that a Reference Implementation also infringes the patents asserted in the Claim, then any patent rights granted to you under this License shall automatically terminate retroactively as of the date you first received the grant. Claims made against an Implementation in part will only trigger termination if the Implementation in part was done for the purpose of combining it with other technology that complies with the Specification so that the technology’s ultimate use will be consistent with the Standard as a whole.

This license is also filed on the  IETF site

Broadcom

Broadcom has both issued patents and outstanding applications covering Opus. These are available under the same license as the Xiph.Org patents. The license covers the listed patents and patent applications, along with any other patent or application covering Opus that is owned by Broadcom.

Broadcom
Patents/Applications covered
  • US 61/406,106
  • US 61/394,842
  • US 7,353,168
  • and any other applicable

License Grant. Broadcom Corporation (“Broadcom”) hereby grants to you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this license) license under Licensed Patents to make, have made, use, offer to sell, sell, import, transfer, and otherwise run, modify (in a way that still complies with the Specification), and reproduce any Implementation.

Definitions. Specification means, and includes the following, both individually and collectively, (a) any standard specification of the Opus codec adopted by the IETF Codec Working Group (“Standard”) and (b) any reference implementation (each, a “Reference Implementation”) published by the IETF Codec Working Group in the request for comments (“RFC”) issued by the IETF for the Specification draft for which this License is issued, or any RFC that is issued as an update or new version thereof. An Implementation means any Reference Implementation, or another implementation that complies with the Specification. Licensed Patents means all patents currently owned by Broadcom or acquired hereafter that Broadcom has the right to license as set forth above and that are necessarily infringed by the Specification, where “necessarily infringed” means: in the case of (a) above, there is no commercially viable means of implementing the Specification without infringing such patent; in the case of (b) above, use of the reference implementation to the extent it infringes such patent.

Termination. If you, directly or indirectly via controlled affiliate or subsidiary, agent, or exclusive licensee, file a Claim for patent infringement against any entity alleging that an Implementation in whole or in part constitutes direct or contributory patent infringement, or inducement of patent infringement (a “Claim”), provided that a Reference Implementation also infringes the patents asserted in the Claim, then any patent rights granted to you under this License shall automatically terminate retroactively as of the date you first received the grant. Claims made against an Implementation in part will only trigger termination if the Implementation in part was done for the purpose of combining it with other technology that complies with the Specification so that the technology’s ultimate use will be consistent with the Standard as a whole.

This license is also filed on the  IETF site

Microsoft

Microsoft acquired patents and applications related to Opus through their purchase of Skype. These patents (and any other Microsoft might have had) are available under a different, but still royalty-free, license detailed below. The license covers the listed patent applications, along with any other patent or application covering Opus that is owned by Microsoft.

Microsoft
Patents/Applications covered
  • US-2008-0201137-A1
  • US-2010-0174535-A1
  • US-2010-0174534-A1
  • US-2010-0174547-A1
  • US-2010-0174532-A1
  • US-2010-0174537-A1
  • US-2010-0174542-A1
  • US-2010-0174531-A1
  • US-2010-0174541-A1
  • US-2010-0174538-A1
  • US-2011-0077940-A1
  • and any other applicable

Microsoft Patent Terms for draft-ietf-codec-opus-10 Date: 1-25-12

1. Patent Promise.

1.1. Patent Promise Grant. Subject to all the terms and conditions of this Agreement, I make the following promises:

1.1.1. Decoder Patent Promise. I, on behalf of myself and my successors in interest and assigns, irrevocably promise not to assert my Necessary Decoder Claims against you for your Decoder Implementation, subject to the following. This is a personal promise directly from me to you, and you acknowledge as a condition of benefiting from it that no rights from me are received from suppliers, distributors, or otherwise in connection with this promise. This promise also applies to your making, using, selling, offering for sale, importing or distributing an implementation of any subsequent version of the Decoder Specification published by the IETF Codec Working Group 1) only to the extent that it implements the Decoder Specification, and 2) so long as all required portions of the Decoder Specification are implemented. This promise does not extend to any portion of a subsequent version of the Decoder Specification published by the IETF Codec Working Group that was not included in the Decoder Specification.

1.1.2. Encoder Patent Promise. I, on behalf of myself and my successors in interest and assigns, irrevocably promise not to assert my Necessary Encoder Claims against you for your Encoder Implementation, subject to the following. This is a personal promise directly from me to you, and you acknowledge as a condition of benefiting from it that no rights from me are received from suppliers, distributors, or otherwise in connection with this promise. This promise also applies to your making, using, selling, offering for sale, importing or distributing an Encoder Implementation that also produces a bitstream that can be decoded by any subsequent version of the Decoder Specification published by the IETF Codec Working Group only to the extent that the Encoder Implementation produces a bitstream that can be decoded by a Decoder Implementation. This promise does not extend to any portion of an Encoder Implementation that is not included in the Reference Implementation.

1.2. Conditions.

1.2.1. Availability. If you have Necessary Decoder Claims or Necessary Encoder Claims, the promises set forth in Section 1 will become effective starting on the date that you make your Necessary Decoder Claims available, via a publicly available written statement, to all implementers for Decoder Implementations and your Necessary Encoder Claims available, via a publicly available written statement, to all implementers for Encoder Implementations on reasonable and non-discriminatory royalty-free licensing terms. The promises set forth in Section 1 will remain in effect so long as you continue to make such claims available for Decoder Implementations and Encoder Implementations under reasonable and non-discriminatory royalty-free licensing terms.

1.2.2. Additional Conditions. This promise is not an assurance (i) that any of my issued patent claims covers a Decoder Implementation or an Encoder Implementation or are enforceable or (ii) that a Decoder Implementation or an Encoder Implementation would not infringe intellectual property rights of any third party. Notwithstanding the personal nature of my promise, this promise is intended to be binding on any future owner, assignee or exclusive licensee who has been given the right to enforce any Necessary Claims against third parties.

1.3. Termination. All rights, grants, and promises made by me to you under Section 1 are immediately terminated if you or your agent file, maintain, or voluntarily participate in a lawsuit against me or any person or entity asserting that its Decoder Implementation infringes Necessary Decoder Claims or its Encoder Implementation infringes Necessary Encoder Claims, unless that suit was in response to a corresponding suit regarding a Decoder Implementation or Encoder Implementation first brought against you. In addition, all rights, grants, and promises made by me to you under Section 1 are terminated if you or your agent seek to license Necessary Decoder Claims for Decoder Implementations or Necessary Encoder Claims for Encoder Implementations on a royalty-bearing basis. This Agreement may also be terminated, including back to the date of non-compliance, because of non-compliance with any other term or condition of this Agreement.

1.4. Bankruptcy. Solely for purposes of Section 365(n) of Title 11, United States Bankruptcy Code and any equivalent law in any foreign jurisdiction, this promise will be treated as if it were a license and you may elect to retain your rights under this promise if I (or any owner of any patents or patent applications referenced herein), as a debtor in possession, or a bankruptcy trustee, reject this non-assert.

2. Patent License Commitment. On behalf of me and my successors in interest and assigns, I agree to offer alternative reasonable and non-discriminatory royalty-bearing licensing terms 1) to my Necessary Decoder Claims solely for your Decoder Implementation and 2) to my Necessary Encoder Claims solely for your Encoder Implementation.

3. Past Skype Declarations. You may, at your option, continue to rely on the terms set forth in Skype’s past declarations made to IETF for the Opus Audio Codec, subject to the terms of those declarations and in lieu of the terms of this Agreement solely for the patents set forth in those declarations.

4. Good Faith Obligation. I agree that I have not and will not knowingly take any action for the purpose of circumventing my obligations under this Agreement.

5. Disclaimers. I expressly disclaim any warranties (express, implied, or otherwise), including implied warranties of merchantability, non-infringement, fitness for a particular purpose, or title, related to the Decoder Specification or Reference Implementation. The entire risk as to implementing or otherwise using the Decoder Specification, Decoder Implementation, Reference Implementation, or Encoder Implementation is assumed by the implementer and user. IN NO EVENT WILL ANY PARTY BE LIABLE TO ANY OTHER PARTY FOR LOST PROFITS OR ANY FORM OF INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER FROM ANY CAUSES OF ACTION OF ANY KIND WITH RESPECT TO THIS AGREEMENT, WHETHER BASED ON BREACH OF CONTRACT, TORT (INCLUDING NEGLIGENCE), OR OTHERWISE, AND WHETHER OR NOT THE OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. All of my obligations under Section 1 and 2 regarding the transfer, successors in interest, or assignment of Necessary Claims will be satisfied if I notify the transferee or assignee of any patent that I know contains Necessary Decoder Claims or Necessary Encoder Claims of the obligations under Sections 1 and 2. Nothing in this Agreement requires me to undertake a patent search.

6. Definitions.

6.1. Agreement. “Agreement” means this document, which sets forth the rights, grants, promises, limitations, conditions, obligations, and disclaimers made available for the particular Specification.

6.2. Control. “Control” means direct or indirect control of more than 50% of the voting power to elect directors of that corporation, or for any other entity, the power to direct management of such entity.

6.3. Decoder Implementation. “Decoder Implementation” means making, using, selling, offering for sale, importing or distributing any conformant implementation of the Decoder Specification 1) only to the extent it implements the Decoder Specification and 2) so long as all required portions of the Decoder Specification are implemented.

6.4. Decoder Specification. “Specification” means draft-ietf-codec-opus-10 specification.

6.5. Encoder Implementation. “Encoder Implementation” means making, using, selling, offering for sale, importing or distributing a 1) software implementation that produces a bitstream that can be decoded by a Decoder Implementation, and 2) where the purpose of the Encoder Implementation is to produce a bitstream for decoding by a Decoder Implementation.

6.6. I, Me, or My. “I,” “me,” or “my” refers to the party making this declaration, and any entity that I Control.

6.7. Necessary Decoder Claims. “Necessary Claims” are those patent claims that a party owns or controls, including those claims acquired after the date of this declaration, that are necessary to implement the required portions (including the required elements of optional portions) of the Decoder Specification that are described in detail and not merely referenced in the Specification.

6.8. Necessary Encoder Claims. “Necessary Encoder Claims” are those patent claims that a party owns or controls, including those claims acquired after the date of this declaration, that are necessarily infringed by the Reference Implementation.

6.9. Reference Implementation. “Reference Implementation” means the reference encoder version in draft-ietf-codec-opus-10 as published by the IETF Codec Working Group as of October 31, 2011.

6.10. You or Your. “You,” “you,” or “your” means any person or entity who exercises patent rights granted under this Agreement, and any person or entity you Control.

转载于:https://www.cnblogs.com/gaozehua/archive/2011/12/04/2275145.html

这篇关于Opus专利列表的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/521373

相关文章

c++的初始化列表与const成员

初始化列表与const成员 const成员 使用const修饰的类、结构、联合的成员变量,在类对象创建完成前一定要初始化。 不能在构造函数中初始化const成员,因为执行构造函数时,类对象已经创建完成,只有类对象创建完成才能调用成员函数,构造函数虽然特殊但也是成员函数。 在定义const成员时进行初始化,该语法只有在C11语法标准下才支持。 初始化列表 在构造函数小括号后面,主要用于给

Spring+MyBatis+jeasyui 功能树列表

java代码@EnablePaging@RequestMapping(value = "/queryFunctionList.html")@ResponseBodypublic Map<String, Object> queryFunctionList() {String parentId = "";List<FunctionDisplay> tables = query(parent

Exchange 服务器地址列表的配置方法与注意事项

Exchange Server 是微软推出的一款企业级邮件服务器软件,广泛应用于企业内部邮件系统的搭建与管理。配置 Exchange 服务器地址列表是其中一个关键环节。本文将详细介绍 Exchange 服务器地址列表的配置方法与注意事项,帮助系统管理员顺利完成这一任务。 内容目录 1. 引言 2. 准备工作 3. 配置地址列表 3.1 创建地址列表 3.2 使用 Exchange

Python--列表简介

列表是什么 列表让你能够在⼀个地方存储成组的信息,其中既可以只包含几个元素,也可以包含数百万个元素。列表是新手可直接使用的最强大的Python 功能之⼀。 列表(list)是一种可变的序列类型,用于存储一系列有序的元素。这些元素可以是任何类型,包括整数、浮点数、字符串、其他列表(即嵌套列表)等。列表是动态的,可以在运行时增加或删除元素。 用方括号([ ])表示列表,用逗号分隔其中的元素。

移动UI:分类列表页、筛选页的设计揭秘。

移动UI的列表页设计需要考虑用户体验和界面美观性,以下是一些建议的设计要点: 1. 列表项的展示: 列表页应该清晰地展示各个列表项,包括标题、副标题、缩略图等内容,以便用户快速浏览和识别。可以使用卡片式布局或者简洁的列表布局。 2. 搜索和筛选: 如果列表项较多,应该提供搜索和筛选功能,方便用户查找感兴趣的内容。搜索框和筛选条件可以放置在页面顶部或者底部,以便用户方便操作。

【语句】如何将列表拼接成字符串并截取20个字符后面的

base_info = "".join(tree.xpath('/html/head/script[4]/text()'))[20:] 以下是对这个语句的详细讲解: tree.xpath('/html/head/script[4]/text()')部分: tree:通常是一个已经构建好的 HTML 文档树对象,它是通过相关的 HTML 解析库(比如 lxml)对 HTML 文档进行解

Python中如何实现列表推导式(List Comprehension)

Python中的列表推导式(List Comprehension)是一种简洁且高效的方式来创建列表。它不仅让代码更加简洁,而且通常比使用循环和条件语句生成列表更快。列表推导式的基本形式允许你从现有的列表或其他可迭代对象中创建新的列表,同时应用过滤和转换操作。下面我将详细解释列表推导式的概念、基本语法、高级用法以及其在实际应用中的优势。 一、列表推导式的基本概念 列表推导式是Python中的一种

【R语言数据类型】深入了解 向量、矩阵、数据框、列表

R语言数据类型有向量、矩阵、数据框、列表。下面我们来深入了解下: vector 的划分 R中的vector分为两类,atomic和list,二者的区别在于,前者元素类型必须相同,后者可以不同。前者的代表是向量和矩阵,后者的代表是list和数据框。 创建向量、矩阵、数据框、列表 # atomica <- 1:5b <- letters[1:5]c <- 1:10mat <- matr

【oracle sql错误】ORA-01795: 列表中的最大表达式数为 1000

select SOURCE_ID,FILTER_TEXT from TEXT_CENTER where SOURCE_ID in() in后面的括号里的数目超过1000条。 问题描述: SQL进行IN查询时,IN中的数据量不能超过1000条。 解决办法: 拆分:id in (1,2,3,4,5,,,,999) or id in(1000,1001,1002,1003,1004,,,,,,

macos系统内置php文件列表 系统自带php卸载方法

在macos系统中, 自带已经安装了php, 根据不同的macos版本php的版本号可能不同, 我们可以通过 which php 命令来查看mac自带的默认php安装路径, 不过注意这个只是php的执行文件路径. 系统自带php文件列表 一下就是macos默认安装的php文件列表. macos 10.15内置PHP文件列表配置文件 /private/etc/php-fpm.conf.def