Internet Engineering Task Force (IETF) V. Chen, Ed.
Request for Comments: 7545 Google
Category: Standards Track S. Das
ISSN: 2070-1721 Applied Communication Sciences
L. Zhu
Huawei
J. Malyar
iconectiv
P. McCann
Huawei
May 2015
Internet Engineering Task Force (IETF) V. Chen, Ed.
Request for Comments: 7545 Google
Category: Standards Track S. Das
ISSN: 2070-1721 Applied Communication Sciences
L. Zhu
Huawei
J. Malyar
iconectiv
P. McCann
Huawei
May 2015
Protocol to Access White-Space (PAWS) Databases
访问空白（PAWS）数据库的协议
Abstract
摘要
Portions of the radio spectrum that are allocated to licensees are available for non-interfering use. This available spectrum is called "white space". Allowing secondary users access to available spectrum "unlocks" existing spectrum to maximize its utilization and to provide opportunities for innovation, resulting in greater overall spectrum utilization.
分配给被许可方的无线电频谱部分可用于非干扰使用。这种可用的频谱称为“空白”。允许二级用户访问可用频谱“解锁”现有频谱，以最大限度地提高其利用率，并提供创新机会，从而提高总体频谱利用率。
One approach to managing spectrum sharing uses databases to report spectrum availability to devices. To achieve interoperability among multiple devices and databases, a standardized protocol must be defined and implemented. This document defines such a protocol, the "Protocol to Access White-Space (PAWS) Databases".
管理频谱共享的一种方法是使用数据库向设备报告频谱可用性。为了实现多个设备和数据库之间的互操作性，必须定义和实施标准化协议。本文件定义了这样一个协议，即“访问空白（PAWS）数据库的协议”。
Status of This Memo
关于下段备忘
This is an Internet Standards Track document.
这是一份互联网标准跟踪文件。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。有关互联网标准的更多信息，请参见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7545.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc7545.
Copyright Notice
版权公告
Copyright (c) 2015 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2015 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Conventions and Terminology . . . . . . . . . . . . . . . . . 5
2.1. Conventions Used in This Document . . . . . . . . . . . . 5
2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 6
3. Protocol Overview . . . . . . . . . . . . . . . . . . . . . . 7
3.1. Multi-ruleset Support . . . . . . . . . . . . . . . . . . 8
4. Protocol Functionalities . . . . . . . . . . . . . . . . . . 9
4.1. Database Discovery . . . . . . . . . . . . . . . . . . . 11
4.1.1. Preconfiguration . . . . . . . . . . . . . . . . . . 11
4.1.2. Configuration Update: Database URI Changes . . . . . 11
4.1.3. Error Handling . . . . . . . . . . . . . . . . . . . 12
4.2. PAWS Version . . . . . . . . . . . . . . . . . . . . . . 12
4.3. Initialization . . . . . . . . . . . . . . . . . . . . . 12
4.3.1. INIT_REQ . . . . . . . . . . . . . . . . . . . . . . 13
4.3.2. INIT_RESP . . . . . . . . . . . . . . . . . . . . . . 14
4.4. Device Registration . . . . . . . . . . . . . . . . . . . 15
4.4.1. REGISTRATION_REQ . . . . . . . . . . . . . . . . . . 16
4.4.2. REGISTRATION_RESP . . . . . . . . . . . . . . . . . . 17
4.5. Available Spectrum Query . . . . . . . . . . . . . . . . 18
4.5.1. AVAIL_SPECTRUM_REQ . . . . . . . . . . . . . . . . . 21
4.5.2. AVAIL_SPECTRUM_RESP . . . . . . . . . . . . . . . . . 23
4.5.3. AVAIL_SPECTRUM_BATCH_REQ . . . . . . . . . . . . . . 26
4.5.4. AVAIL_SPECTRUM_BATCH_RESP . . . . . . . . . . . . . . 28
4.5.5. SPECTRUM_USE_NOTIFY . . . . . . . . . . . . . . . . . 29
4.5.6. SPECTRUM_USE_RESP . . . . . . . . . . . . . . . . . . 31
4.6. Device Validation . . . . . . . . . . . . . . . . . . . . 31
4.6.1. DEV_VALID_REQ . . . . . . . . . . . . . . . . . . . . 32
4.6.2. DEV_VALID_RESP . . . . . . . . . . . . . . . . . . . 33
5. Protocol Parameters . . . . . . . . . . . . . . . . . . . . . 34
5.1. GeoLocation . . . . . . . . . . . . . . . . . . . . . . . 34
5.2. DeviceDescriptor . . . . . . . . . . . . . . . . . . . . 37
5.3. AntennaCharacteristics . . . . . . . . . . . . . . . . . 38
5.4. DeviceCapabilities . . . . . . . . . . . . . . . . . . . 39
5.5. DeviceOwner . . . . . . . . . . . . . . . . . . . . . . . 39
5.6. RulesetInfo . . . . . . . . . . . . . . . . . . . . . . . 40
5.7. DbUpdateSpec . . . . . . . . . . . . . . . . . . . . . . 41
5.8. DatabaseSpec . . . . . . . . . . . . . . . . . . . . . . 42
5.9. SpectrumSpec . . . . . . . . . . . . . . . . . . . . . . 42
5.10. SpectrumSchedule . . . . . . . . . . . . . . . . . . . . 44
5.11. Spectrum . . . . . . . . . . . . . . . . . . . . . . . . 44
5.12. SpectrumProfile . . . . . . . . . . . . . . . . . . . . . 50
5.13. FrequencyRange . . . . . . . . . . . . . . . . . . . . . 51
5.14. EventTime . . . . . . . . . . . . . . . . . . . . . . . . 51
5.15. GeoSpectrumSpec . . . . . . . . . . . . . . . . . . . . . 52
5.16. DeviceValidity . . . . . . . . . . . . . . . . . . . . . 53
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Conventions and Terminology . . . . . . . . . . . . . . . . . 5
2.1. Conventions Used in This Document . . . . . . . . . . . . 5
2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 6
3. Protocol Overview . . . . . . . . . . . . . . . . . . . . . . 7
3.1. Multi-ruleset Support . . . . . . . . . . . . . . . . . . 8
4. Protocol Functionalities . . . . . . . . . . . . . . . . . . 9
4.1. Database Discovery . . . . . . . . . . . . . . . . . . . 11
4.1.1. Preconfiguration . . . . . . . . . . . . . . . . . . 11
4.1.2. Configuration Update: Database URI Changes . . . . . 11
4.1.3. Error Handling . . . . . . . . . . . . . . . . . . . 12
4.2. PAWS Version . . . . . . . . . . . . . . . . . . . . . . 12
4.3. Initialization . . . . . . . . . . . . . . . . . . . . . 12
4.3.1. INIT_REQ . . . . . . . . . . . . . . . . . . . . . . 13
4.3.2. INIT_RESP . . . . . . . . . . . . . . . . . . . . . . 14
4.4. Device Registration . . . . . . . . . . . . . . . . . . . 15
4.4.1. REGISTRATION_REQ . . . . . . . . . . . . . . . . . . 16
4.4.2. REGISTRATION_RESP . . . . . . . . . . . . . . . . . . 17
4.5. Available Spectrum Query . . . . . . . . . . . . . . . . 18
4.5.1. AVAIL_SPECTRUM_REQ . . . . . . . . . . . . . . . . . 21
4.5.2. AVAIL_SPECTRUM_RESP . . . . . . . . . . . . . . . . . 23
4.5.3. AVAIL_SPECTRUM_BATCH_REQ . . . . . . . . . . . . . . 26
4.5.4. AVAIL_SPECTRUM_BATCH_RESP . . . . . . . . . . . . . . 28
4.5.5. SPECTRUM_USE_NOTIFY . . . . . . . . . . . . . . . . . 29
4.5.6. SPECTRUM_USE_RESP . . . . . . . . . . . . . . . . . . 31
4.6. Device Validation . . . . . . . . . . . . . . . . . . . . 31
4.6.1. DEV_VALID_REQ . . . . . . . . . . . . . . . . . . . . 32
4.6.2. DEV_VALID_RESP . . . . . . . . . . . . . . . . . . . 33
5. Protocol Parameters . . . . . . . . . . . . . . . . . . . . . 34
5.1. GeoLocation . . . . . . . . . . . . . . . . . . . . . . . 34
5.2. DeviceDescriptor . . . . . . . . . . . . . . . . . . . . 37
5.3. AntennaCharacteristics . . . . . . . . . . . . . . . . . 38
5.4. DeviceCapabilities . . . . . . . . . . . . . . . . . . . 39
5.5. DeviceOwner . . . . . . . . . . . . . . . . . . . . . . . 39
5.6. RulesetInfo . . . . . . . . . . . . . . . . . . . . . . . 40
5.7. DbUpdateSpec . . . . . . . . . . . . . . . . . . . . . . 41
5.8. DatabaseSpec . . . . . . . . . . . . . . . . . . . . . . 42
5.9. SpectrumSpec . . . . . . . . . . . . . . . . . . . . . . 42
5.10. SpectrumSchedule . . . . . . . . . . . . . . . . . . . . 44
5.11. Spectrum . . . . . . . . . . . . . . . . . . . . . . . . 44
5.12. SpectrumProfile . . . . . . . . . . . . . . . . . . . . . 50
5.13. FrequencyRange . . . . . . . . . . . . . . . . . . . . . 51
5.14. EventTime . . . . . . . . . . . . . . . . . . . . . . . . 51
5.15. GeoSpectrumSpec . . . . . . . . . . . . . . . . . . . . . 52
5.16. DeviceValidity . . . . . . . . . . . . . . . . . . . . . 53
5.17. Error Element . . . . . . . . . . . . . . . . . . . . . . 53
5.17.1. OUTSIDE_COVERAGE Error . . . . . . . . . . . . . . . 55
5.17.2. DATABASE_CHANGE Error . . . . . . . . . . . . . . . 56
5.17.3. MISSING Error . . . . . . . . . . . . . . . . . . . 56
6. Message Encoding . . . . . . . . . . . . . . . . . . . . . . 57
6.1. JSON-RPC Binding . . . . . . . . . . . . . . . . . . . . 57
6.1.1. Method Names . . . . . . . . . . . . . . . . . . . . 59
6.1.2. JSON Encoding of Data Models . . . . . . . . . . . . 59
6.2. Example Encoding: spectrum.paws.init Method . . . . . . . 61
6.3. Example Encoding: spectrum.paws.getSpectrum Method . . . 62
6.4. Example Encoding: DeviceOwner vCard . . . . . . . . . . . 66
7. HTTPS Binding . . . . . . . . . . . . . . . . . . . . . . . . 66
8. Extensibility . . . . . . . . . . . . . . . . . . . . . . . . 68
8.1. Defining Ruleset Identifiers . . . . . . . . . . . . . . 68
8.2. Defining New Message Parameters . . . . . . . . . . . . . 69
8.3. Defining Additional Error Codes . . . . . . . . . . . . . 69
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 69
9.1. PAWS Ruleset ID Registry . . . . . . . . . . . . . . . . 70
9.1.1. Registration Template . . . . . . . . . . . . . . . . 70
9.1.2. Initial Registry Contents . . . . . . . . . . . . . . 72
9.2. PAWS Parameters Registry . . . . . . . . . . . . . . . . 78
9.2.1. Registration Template . . . . . . . . . . . . . . . . 78
9.2.2. Initial Registry Contents . . . . . . . . . . . . . . 78
9.3. PAWS Error Code Registry . . . . . . . . . . . . . . . . 80
9.3.1. Registration Template . . . . . . . . . . . . . . . . 81
9.3.2. Initial Registry Contents . . . . . . . . . . . . . . 81
10. Security Considerations . . . . . . . . . . . . . . . . . . . 81
10.1. Assurance of Proper Database . . . . . . . . . . . . . . 83
10.2. Protection against Modification . . . . . . . . . . . . 84
10.3. Protection against Eavesdropping . . . . . . . . . . . . 84
10.4. Client Authentication Considerations . . . . . . . . . . 84
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 85
11.1. Normative References . . . . . . . . . . . . . . . . . . 85
11.2. Informative References . . . . . . . . . . . . . . . . . 86
Appendix A. Database Listing Server Support . . . . . . . . . . 88
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 89
Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 90
5.17. Error Element . . . . . . . . . . . . . . . . . . . . . . 53
5.17.1. OUTSIDE_COVERAGE Error . . . . . . . . . . . . . . . 55
5.17.2. DATABASE_CHANGE Error . . . . . . . . . . . . . . . 56
5.17.3. MISSING Error . . . . . . . . . . . . . . . . . . . 56
6. Message Encoding . . . . . . . . . . . . . . . . . . . . . . 57
6.1. JSON-RPC Binding . . . . . . . . . . . . . . . . . . . . 57
6.1.1. Method Names . . . . . . . . . . . . . . . . . . . . 59
6.1.2. JSON Encoding of Data Models . . . . . . . . . . . . 59
6.2. Example Encoding: spectrum.paws.init Method . . . . . . . 61
6.3. Example Encoding: spectrum.paws.getSpectrum Method . . . 62
6.4. Example Encoding: DeviceOwner vCard . . . . . . . . . . . 66
7. HTTPS Binding . . . . . . . . . . . . . . . . . . . . . . . . 66
8. Extensibility . . . . . . . . . . . . . . . . . . . . . . . . 68
8.1. Defining Ruleset Identifiers . . . . . . . . . . . . . . 68
8.2. Defining New Message Parameters . . . . . . . . . . . . . 69
8.3. Defining Additional Error Codes . . . . . . . . . . . . . 69
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 69
9.1. PAWS Ruleset ID Registry . . . . . . . . . . . . . . . . 70
9.1.1. Registration Template . . . . . . . . . . . . . . . . 70
9.1.2. Initial Registry Contents . . . . . . . . . . . . . . 72
9.2. PAWS Parameters Registry . . . . . . . . . . . . . . . . 78
9.2.1. Registration Template . . . . . . . . . . . . . . . . 78
9.2.2. Initial Registry Contents . . . . . . . . . . . . . . 78
9.3. PAWS Error Code Registry . . . . . . . . . . . . . . . . 80
9.3.1. Registration Template . . . . . . . . . . . . . . . . 81
9.3.2. Initial Registry Contents . . . . . . . . . . . . . . 81
10. Security Considerations . . . . . . . . . . . . . . . . . . . 81
10.1. Assurance of Proper Database . . . . . . . . . . . . . . 83
10.2. Protection against Modification . . . . . . . . . . . . 84
10.3. Protection against Eavesdropping . . . . . . . . . . . . 84
10.4. Client Authentication Considerations . . . . . . . . . . 84
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 85
11.1. Normative References . . . . . . . . . . . . . . . . . . 85
11.2. Informative References . . . . . . . . . . . . . . . . . 86
Appendix A. Database Listing Server Support . . . . . . . . . . 88
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 89
Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 90
This section provides some high-level introductory material. Readers are strongly encouraged to read "Protocol to Access White-Space (PAWS) Databases: Use Cases and Requirements" [RFC6953] for use cases, requirements, and additional background.
本节提供一些高级介绍材料。强烈鼓励读者阅读“访问空白空间（PAWS）数据库的协议：用例和需求”[RFC6953]，了解用例、需求和其他背景。
A geospatial database can track available spectrum (in accordance with the rules of one or more regulatory domains) and make this information available to devices. This approach shifts the complexity of spectrum-policy conformance out of the device and into the database. This approach also simplifies adoption of policy changes, limiting updates to a handful of databases, rather than numerous devices. It opens the door for innovations in spectrum management that can incorporate a variety of parameters, including user location and time. In the future, it also can include other parameters, such as user priority, signal type and power, spectrum supply and demand, payment or micro-auction bidding, and more.
地理空间数据库可以跟踪可用频谱（根据一个或多个监管领域的规则），并将此信息提供给设备。这种方法将频谱策略一致性的复杂性从设备转移到数据库中。这种方法还简化了策略更改的采用，将更新限制在少数数据库上，而不是许多设备上。它为频谱管理创新打开了大门，频谱管理可以包含各种参数，包括用户位置和时间。未来，它还可以包括其他参数，如用户优先级、信号类型和功率、频谱供需、支付或微拍卖竞价等。
In providing this service, a database records and updates information necessary to protect primary users -- for example, this information may include parameters such as a fixed transmitter's call sign, its geolocation, antenna height, power, and periods of operation. The rules that the database is required to follow, including its schedule for obtaining and updating protection information, protection rules, and information reported to devices, vary according to regulatory domain. Such variations, however, should be handled by each database and hidden from devices to the maximum extent possible.
在提供此服务时，数据库记录并更新保护主要用户所需的信息——例如，此信息可能包括固定发射机的呼号、其地理位置、天线高度、功率和工作周期等参数。数据库需要遵循的规则，包括获取和更新保护信息的时间表、保护规则以及报告给设备的信息，因监管领域而异。但是，这些变化应由每个数据库处理，并尽可能对设备隐藏。
This specification defines an extensible protocol, built on top of HTTP and TLS, to obtain available spectrum from a geospatial database by a device with geolocation capability. It enables a device to operate in a regulatory domain that implements this protocol.
本规范定义了一个可扩展协议，建立在HTTP和TLS之上，通过具有地理定位功能的设备从地理空间数据库获取可用频谱。它使设备能够在实施此协议的监管域中运行。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in "Key words for use in RFCs to Indicate Requirement Levels" [RFC2119].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照“RFC中用于指示需求水平的关键词”[RFC2119]中的描述进行解释。
Database or Spectrum Database: A Database is an entity that contains current information about available spectrum at a given location and time, as well as other types of information related to spectrum availability and usage.
数据库或频谱数据库：数据库是一个实体，包含给定位置和时间的可用频谱的当前信息，以及与频谱可用性和使用相关的其他类型的信息。
Device ID: An identifier for a device.
设备ID：设备的标识符。
EIRP: Effective Isotropically Radiated Power
EIRP：有效各向同性辐射功率
ETSI: European Telecommunications Standards Institute
(http://www.etsi.org)
ETSI: European Telecommunications Standards Institute
(http://www.etsi.org)
FCC: The U.S. Federal Communications Commission
(http://www.fcc.gov)
FCC: The U.S. Federal Communications Commission
(http://www.fcc.gov)
Listing server: A server that provides the URIs for one or more Spectrum Databases. A regulator, for example, may operate a Database Listing Server to publish the list of authorized Spectrum Databases for its regulatory domain.
列表服务器：为一个或多个频谱数据库提供URI的服务器。例如，监管机构可以操作数据库列表服务器来发布其监管域的授权频谱数据库列表。
Master Device: A device that queries the Database, on its own behalf and/or on behalf of a slave device, to obtain available spectrum information.
主设备：代表其自身和/或代表从属设备查询数据库以获取可用频谱信息的设备。
Regulatory Domain: A location where certain rules apply to the use of white-space spectrum, including the operation of Databases and devices involved in its use. A regulatory domain is normally defined by a unit of government for a particular country, but PAWS is agnostic as to how a regulatory domain is constructed.
监管领域：特定规则适用于空白频谱使用的位置，包括数据库和设备的操作。监管领域通常由特定国家的政府单位定义，但PAWS对监管领域的构建方式不可知。
Ruleset: A ruleset represents a set of rules that governs the operation of white-space devices and Spectrum Databases. A regulatory authority can define its own set of rules or adopt an existing ruleset. When a Database or device is said to "support a ruleset", it means that it contains out-of-band knowledge of the rules and that its hardware and software implementations conform to those rules.
规则集：规则集表示一组控制空白设备和频谱数据库操作的规则。监管机构可以定义自己的规则集或采用现有的规则集。当数据库或设备被称为“支持规则集”时，这意味着它包含规则的带外知识，并且其硬件和软件实现符合这些规则。
Ruleset Identifier: A ruleset can be identified by an IANA-registered identifier (see PAWS Ruleset ID Registry (Section 9.1)). When a Database or device indicates it supports a ruleset identifier, it means that it conforms to the rules associated with that identifier. A regulatory authority can define and register its own ruleset identifiers, or it can use a previously registered identifier if it adopts an existing ruleset.
规则集标识符：规则集可以由IANA注册标识符标识（参见PAWS规则集ID注册表（第9.1节））。当数据库或设备指示它支持规则集标识符时，表示它符合与该标识符关联的规则。监管机构可以定义并注册自己的规则集标识符，或者如果采用现有规则集，则可以使用以前注册的标识符。
Slave Device: A device that queries the Database through a master device.
从设备：通过主设备查询数据库的设备。
A Master Device uses PAWS to obtain a schedule of available spectrum at its location. The security necessary to ensure the accuracy, privacy, and confidentiality of the device's location is described in the Security Considerations (Section 10). This document assumes that the Master Device and the Database are connected to the Internet.
主设备使用PAWS获取其所在位置的可用频谱计划。安全注意事项（第10节）中描述了确保设备位置的准确性、隐私性和机密性所需的安全性。本文档假定主设备和数据库已连接到Internet。
A typical sequence of PAWS operations is outlined as follows. See "Protocol Functionalities" (Section 4) and "Protocol Parameters" (Section 5) for details:
爪操作的典型顺序概述如下。详见“协议功能”（第4节）和“协议参数”（第5节）：
1. The Master Device obtains (statically or dynamically) the URI for a Database appropriate for its location, to which to send subsequent PAWS messages.
1. 主设备（静态或动态）获取适合其位置的数据库的URI，并向其发送后续PAWS消息。
2. The Master Device establishes an HTTPS session with the Database.
2. 主设备与数据库建立HTTPS会话。
3. The Master Device optionally sends an initialization message to the Database to exchange capabilities.
3. 主设备选择性地向数据库发送初始化消息以交换功能。
4. If the Database receives an initialization message, it responds with an initialization-response message in the body of the HTTP response.
4. 如果数据库接收到初始化消息，它将在HTTP响应的主体中使用初始化响应消息进行响应。
5. The Database may require the Master Device to be registered before providing service.
5. 数据库可能要求在提供服务之前注册主设备。
6. The Master Device sends an available-spectrum request message to the Database. The message may be on behalf of a Slave Device that made a request to the Master Device.
6. 主设备向数据库发送可用频谱请求消息。该消息可以代表向主设备发出请求的从设备。
7. If the Master Device is making a request on behalf of a Slave Device, the Master Device may verify with the Database that the Slave Device is permitted to operate.
7. 如果主设备代表从设备发出请求，则主设备可以使用数据库验证是否允许从设备操作。
8. The Database responds with an available-spectrum response message in the body of the HTTP response.
8. 数据库使用HTTP响应主体中的可用频谱响应消息进行响应。
9. The Master Device may send a spectrum-usage notification message to the Database. The notification is purely informational; it notifies the Database what spectrum the Master Device intends to use and is not a request to the Database to get permission to use that spectrum. Some Databases may require spectrum-usage notification.
9. 主设备可以向数据库发送频谱使用通知消息。通知纯粹是信息性的；它通知数据库主设备打算使用什么频谱，而不是请求数据库获得使用该频谱的权限。某些数据库可能需要频谱使用通知。
10. If the Database receives a spectrum-usage notification message, it responds by sending the Master Device a spectrum-usage acknowledgement message. Since the notification is purely informational, the Master Device does not need to process the database response.
10. 如果数据库接收到频谱使用通知消息，它将通过向主设备发送频谱使用确认消息来响应。由于通知纯粹是信息性的，因此主设备不需要处理数据库响应。
Different regulatory domains may impose particular requirements, such as requiring Master Devices to register with the Database, performing Slave Device verification, and sending spectrum-usage notifications.
不同的监管领域可能会施加特定要求，例如要求主设备向数据库注册、执行从设备验证以及发送频谱使用通知。
For a Master Device that supports multiple rulesets and operates with multiple Databases, PAWS supports the following sequence of operations for each request by the Master Device:
对于支持多个规则集并使用多个数据库操作的主设备，PAWS支持主设备对每个请求的以下操作序列：
1. The Master Device includes in its request its location and optionally includes the identifier of all the rulesets it supports and any parameter values it might need for the request.
1. 主设备在其请求中包括其位置，并可选地包括其支持的所有规则集的标识符以及请求可能需要的任何参数值。
2. The Database uses the device location and also may use the ruleset list to determine its response, for example, to select the list of required parameters.
2. 数据库使用设备位置，也可以使用规则集列表来确定其响应，例如，选择所需参数的列表。
3. If required parameters are missing from the request, the Database responds with an error and a list of names of the missing parameters.
3. 如果请求中缺少必需的参数，数据库将以错误和缺少参数的名称列表进行响应。
4. The Master Device makes the request again, adding the missing parameter values.
4. 主设备再次发出请求，添加缺少的参数值。
5. The Database responds to the request, including the identifier of the applicable ruleset.
5. 数据库响应请求，包括适用规则集的标识符。
6. The Master Device uses the indicated ruleset to determine how to interpret the database response.
6. 主设备使用指示的规则集来确定如何解释数据库响应。
NOTE: Some regulatory domains specify sets of requirements for device behavior that may be complex and not easily parameterized. The ruleset-id parameter provides a mechanism for the Database to inform the Master Device of an applicable ruleset, and, for devices with
注意：一些监管领域规定了设备行为的一系列要求，这些要求可能很复杂，不容易参数化。ruleset id参数为数据库提供了一种机制，用于通知主设备适用的规则集，对于具有
out-of-band knowledge of the particular regulatory domain requirements, to satisfy those requirements without having to specify the device-side behavior within the protocol. Ruleset identifiers will normally contain the name of the regulatory body that established the rules and version information, such as "FccTvBandWhiteSpace-2010".
特定监管领域要求的带外知识，以满足这些要求，而无需指定协议内的设备端行为。规则集标识符通常包含制定规则的监管机构的名称和版本信息，如“FccTvBandWhiteSpace-2010”。
By separating the regulatory "authority" from the "ruleset-id", it allows the protocol to support multiple regulatory authorities that use the same device-side ruleset. It also allows support for a single authority to define multiple rulesets.
通过将监管“机构”与“规则集id”分离，它允许协议支持使用同一设备端规则集的多个监管机构。它还允许支持单个机构定义多个规则集。
PAWS consists of several components. As noted below, some regulatory domains or database implementations may mandate the use of a component, even when its use is not mandated by PAWS.
爪由几个部件组成。如下所述，一些监管域或数据库实现可能会强制使用组件，即使PAWS未强制使用组件。
o Database Discovery (Section 4.1) is a required component for the Master Device.
o 数据库发现（第4.1节）是主设备所必需的组件。
o Initialization (Section 4.3) is a required component for the Database. Its use allows the Master Device to determine necessary information that has not been preconfigured.
o 初始化（第4.3节）是数据库的必需组件。它的使用允许主设备确定未预配置的必要信息。
o Device Registration (Section 4.4) is an optional component for the Database. It can be implemented as a separate component or as part of the Available Spectrum Query (Section 4.5) component. It is used by the Master Device when the Database requires it. Note that some regulators require device registration for only specific device types, such as higher-power fixed (as opposed to mobile) devices, to allow them to contact the operators to resolve any interference issues.
o 设备注册（第4.4节）是数据库的可选组件。它可以作为单独的组件实现，也可以作为可用频谱查询（第4.5节）组件的一部分实现。当数据库需要时，它由主设备使用。请注意，一些监管机构仅要求特定设备类型的设备注册，例如更高功率的固定（相对于移动）设备，以允许他们联系运营商解决任何干扰问题。
o Available Spectrum Query (Section 4.5) is a required component for the Master Device and the Database.
o 可用频谱查询（第4.5节）是主设备和数据库的必需组件。
o Spectrum Use Notify (Section 4.5.5) is an optional component for the Master Device and the Database. When it is required, the Database informs the Master Device via its response to the Available Spectrum Query (Section 4.5).
o 频谱使用通知（第4.5.5节）是主设备和数据库的可选组件。当需要时，数据库通过其对可用频谱查询的响应通知主设备（第4.5节）。
o Device Validation (Section 4.6) as a separate component is optional for the Master Device and Database. When implemented by the Database, its use allows the Master Device to validate Slave Devices without having to use the full Available Spectrum Query.
o 对于主设备和数据库，设备验证（第4.6节）作为单独的组件是可选的。当由数据库实现时，它的使用允许主设备验证从设备，而不必使用完整的可用频谱查询。
This section describes the protocol components and their messages. "Protocol Parameters" (Section 5) contains a more thorough discussion of the parameters that make up the PAWS request and response messages. "Message Encoding" (Section 6) provides examples of message encodings. "HTTPS Binding" (Section 7) describes the use of HTTPS ("HTTP Over TLS" [RFC2818]) for transferring PAWS messages and optional device authentication.
本节介绍协议组件及其消息。“协议参数”（第5节）对构成PAWS请求和响应消息的参数进行了更深入的讨论。“消息编码”（第6节）提供了消息编码的示例。“HTTPS绑定”（第7节）描述了HTTPS（“HTTP Over TLS”[RFC2818]）用于传输PAWS消息和可选设备身份验证。
The parameter tables in this section and "Protocol Parameters" (Section 5) are for reference and contain the name of each parameter, the data type of each parameter, and whether the existence of the parameter is required for the protocol transaction in question. The diagrams are loosely based on the Unified Modeling Language (UML), and the data types are defined either in "Protocol Parameters" (Section 5) or are one of the following primitive or structured types:
本节和“协议参数”（第5节）中的参数表仅供参考，包含每个参数的名称、每个参数的数据类型，以及相关协议事务是否需要存在该参数。这些图松散地基于统一建模语言（UML），数据类型在“协议参数”（第5节）中定义，或者是以下基本类型或结构化类型之一：
string: A string, as defined by JSON [RFC7159], restricted to the UTF-8 encoding.
字符串：由JSON[RFC7159]定义的字符串，仅限于UTF-8编码。
int: A number, as defined by JSON [RFC7159], without a fractional or exponent part.
int：一个由JSON[RFC7159]定义的数字，没有分数或指数部分。
float: A number, as defined by JSON [RFC7159].
float：一个由JSON[RFC7159]定义的数字。
boolean: A boolean, as defined by JSON [RFC7159].
boolean：由JSON[RFC7159]定义的布尔值。
list: A structured type that represents a list of elements, as defined by JSON [RFC7159] array type. All elements of the list are of the same data type, which is indicated in its diagram and description. The diagram notation and description may include additional constraints, such as minimum or maximum number of elements.
list：表示元素列表的结构化类型，由JSON[RFC7159]数组类型定义。列表的所有元素都具有相同的数据类型，如图和说明所示。图表符号和描述可能包括附加约束，例如元素的最小或最大数量。
Also:
也：
o All parameter names are case sensitive. Unless stated otherwise, all string values are case sensitive.
o 所有参数名称都区分大小写。除非另有说明，否则所有字符串值都区分大小写。
o All timestamps are in UTC and are expressed using exactly the form, YYYY-MM-DDThh:mm:ssZ, as defined by "Date and Time on the Internet: Timestamps" [RFC3339].
o 所有时间戳均以UTC为单位，并使用“互联网上的日期和时间：时间戳”[RFC3339]定义的格式YYYY-MM-DDThh:MM:ssZ表示。
In some cases, specific rulesets may place additional requirements on message parameters. These additional requirements will be documented in the IANA PAWS Ruleset ID Registry (Section 9.1). When a request message sent to the Database has missing parameters, whether they are
在某些情况下，特定规则集可能会对消息参数提出附加要求。这些附加要求将记录在IANA PAWS规则集ID注册表中（第9.1节）。当发送到数据库的请求消息缺少参数时，无论是否
required by PAWS or the applicable ruleset, the Database returns the MISSING error (see Section 5.17.3), along with data indicating the missing parameters.
根据PAWS或适用规则集的要求，数据库返回缺失错误（见第5.17.3节），以及指示缺失参数的数据。
The Master Device can be provisioned statically (preconfigured) with the URI of one or more Databases. For example, in a particular regulatory domain, there may be a number of certified Databases that any device operating in that domain is permitted to connect to, and those URIs can be preconfigured in the device.
可以使用一个或多个数据库的URI静态（预配置）配置主设备。例如，在特定的监管域中，可能存在允许在该域中运行的任何设备连接的多个经认证的数据库，并且可以在该设备中预配置这些URI。
Listing Server Support: As an alternative to preconfiguring devices with a list of certified Databases, some regulatory domains support the preconfiguration of devices with the URI of a certified listing server, to which devices can connect to obtain the list of certified Databases. See "Database Listing Server Support" (Appendix A) for further information.
列表服务器支持：作为使用认证数据库列表预配置设备的替代方案，一些监管域支持使用认证列表服务器的URI预配置设备，设备可以连接到该服务器以获取认证数据库列表。有关更多信息，请参阅“数据库列表服务器支持”（附录A）。
To adapt to changes in the list of certified or approved Databases, the device needs to update its preconfigured list of Databases.
为了适应认证或批准的数据库列表中的更改，设备需要更新其预配置的数据库列表。
A Database MAY change its URI, but before it changes its URI, it MUST indicate the upcoming change by including the URI of one or more alternate Databases using DbUpdateSpec (Section 5.7) in its responses to devices. The Database MUST reply with DbUpdateSpec for a minimum of 2 weeks before disabling the old URI. A device will update its preconfigured entry for the Database sending the DbUpdateSpec by replacing this entry with the alternate Databases listed in the DbUpdateSpec; the list of alternate Databases does not affect any other entries. Note that the ordering of Databases in the list does not imply any preference and does not need to remain the same for every request. The device SHOULD detect infinite redirection loops; if a suitable Database cannot be contacted, the device MUST treat this as equivalent to a response indicating no available spectrum. This database-change mechanism is used, for example, before a Database ceases operation; it is not intended to be used for dynamic load balancing.
数据库可能会更改其URI，但在更改其URI之前，它必须通过在对设备的响应中使用DbUpdateSpec（第5.7节）包含一个或多个备用数据库的URI来指示即将发生的更改。在禁用旧URI之前，数据库必须使用DbUpdateSpec回复至少2周。设备将更新发送DbUpdateSpec的数据库的预配置条目，方法是将该条目替换为DbUpdateSpec中列出的备用数据库；备用数据库列表不影响任何其他条目。请注意，列表中数据库的顺序并不意味着任何偏好，也不需要对每个请求都保持相同。设备应检测无限重定向循环；如果无法联系到合适的数据库，设备必须将其视为等同于指示没有可用频谱的响应。例如，在数据库停止操作之前使用此数据库更改机制；它不打算用于动态负载平衡。
The device SHOULD select another Database from its list of preconfigured Databases if:
在以下情况下，设备应从其预配置数据库列表中选择另一个数据库：
o The selected Database is unreachable or does not respond.
o 所选数据库无法访问或没有响应。
o The selected Database returns an UNSUPPORTED error (see "Error Codes" (Section 5.17)), which indicates the Database does not support the device (based on its device type, model, etc.) or supports none of the rulesets specified in the request.
o 所选数据库返回不受支持的错误（请参阅“错误代码”（第5.17节）），这表明数据库不支持该设备（基于其设备类型、型号等），或者不支持请求中指定的任何规则集。
If a suitable Database cannot be contacted, the device MUST treat this as equivalent to a response indicating no available spectrum. If the device had previously contacted a Database to get available spectrum, but subsequently fails to contact a suitable Database, the spectrum the device is currently using can be used for as long as the spectrum data is valid. However, after that period, the device will no longer have valid spectrum to use. Some regulatory domains may have specific rules regarding how long the spectrum data remains valid in these cases.
如果无法联系到合适的数据库，设备必须将其视为等同于指示没有可用频谱的响应。如果设备先前已联系数据库以获取可用频谱，但随后未能联系合适的数据库，则只要频谱数据有效，设备当前使用的频谱就可以使用。然而，在这段时间之后，设备将不再具有可使用的有效频谱。在这些情况下，一些监管领域可能有关于频谱数据有效期的特定规则。
PAWS version uses a "<major>.<minor>" numbering scheme to indicate versions of the protocol. The protocol versioning policy is intended to allow the device or Database to indicate the format of a message and its understanding of PAWS functionality defined by that version. No change is made to the version string for the addition of message components that only add to extensible parameter values. The <minor> number is incremented when the changes made to the protocol add functionalities (methods) but do not change the existing functionalities. The <major> number is incremented when incompatible changes are made to existing functionality.
PAWS版本使用“<major><minor>”编号方案来表示协议的版本。协议版本控制策略旨在允许设备或数据库指示消息的格式及其对该版本定义的PAWS功能的理解。对于添加仅添加到可扩展参数值的消息组件，不更改版本字符串。当对协议所做的更改添加了功能（方法），但未更改现有功能时，<minor>数字将增加。当对现有功能进行不兼容的更改时，<major>数字将增加。
The current PAWS version is "1.0".
当前PAWS版本为“1.0”。
A Master Device SHOULD use the initialization procedure to exchange capability information with the Database whenever the Master Device powers up or initiates communication with the Database. The initialization response informs the Master Device of specific parameterized-rule values for each supported ruleset, such as threshold distances and time periods beyond which the device must update its available-spectrum data (see "RuleSetInfo" (Section 5.6)).
当主设备通电或启动与数据库的通信时，主设备应使用初始化过程与数据库交换能力信息。初始化响应通知主设备每个受支持规则集的特定参数化规则值，如阈值距离和时间段，超过该时间段，设备必须更新其可用频谱数据（请参阅“规则集信息”（第5.6节））。
When parameterized-rule values are not preconfigured for the applicable ruleset at the specified location, a Master Device MUST use the initialization procedure.
如果未在指定位置为适用规则集预配置参数化规则值，则主设备必须使用初始化过程。
It is important to note that, when parameterized-rule values are preconfigured in a Master Device, they are preconfigured on a per-ruleset basis. That is, values preconfigured for one ruleset are not applicable to any other ruleset.
需要注意的是，当在主设备中预配置参数化规则值时，它们是基于每个规则集预配置的。也就是说，为一个规则集预配置的值不适用于任何其他规则集。
For database implementations that require it, the initialization message also enables extra database-specific or ruleset-specific handshake parameters to be communicated before allowing available-spectrum requests.
对于需要它的数据库实现，初始化消息还允许在允许可用频谱请求之前传递额外的特定于数据库或特定于规则集的握手参数。
The Initialization request procedure is depicted in Figure 1.
初始化请求过程如图1所示。
o INIT_REQ (Section 4.3.1) is the initialization request message
o INIT_REQ（第4.3.1节）是初始化请求消息
o INIT_RESP (Section 4.3.2) is the initialization response message
o INIT_RESP（第4.3.2节）是初始化响应消息
+---------------+ +-------------------+
| Master Device | | Spectrum Database |
+---------------+ +-------------------+
| |
| INIT_REQ |
|-------------------->|
| |
| INIT_RESP |
|<--------------------|
| |
+---------------+ +-------------------+
| Master Device | | Spectrum Database |
+---------------+ +-------------------+
| |
| INIT_REQ |
|-------------------->|
| |
| INIT_RESP |
|<--------------------|
| |
Figure 1
图1
The initialization request message allows the Master Device to initiate exchange of capabilities with the Database.
初始化请求消息允许主设备启动与数据库的功能交换。
+---------------------------------------+
|INIT_REQ |
+----------------------------+----------|
|deviceDesc:DeviceDescriptor | REQUIRED |
|location:GeoLocation | REQUIRED |
|.......................................|
|*other:any | OPTIONAL |
+----------------------------+----------+
+---------------------------------------+
|INIT_REQ |
+----------------------------+----------|
|deviceDesc:DeviceDescriptor | REQUIRED |
|location:GeoLocation | REQUIRED |
|.......................................|
|*other:any | OPTIONAL |
+----------------------------+----------+
Parameters:
参数：
deviceDesc: The DeviceDescriptor (Section 5.2) for the device is REQUIRED. If the device descriptor does not contain any ruleset IDs, the Master Device is asking the Database to return a RulesetInfo (Section 5.6) list that specifies the rulesets that it supports at the specified location.
deviceDesc：需要设备的DeviceDescriptor（第5.2节）。如果设备描述符不包含任何规则集ID，则主设备将要求数据库返回RulesetInfo（第5.6节）列表，该列表指定它在指定位置支持的规则集。
location: The GeoLocation (Section 5.1) of the device is REQUIRED. If the location is outside all regulatory domain supported by the Database, the Database MUST respond with an OUTSIDE_COVERAGE error (see Table 1).
位置：需要设备的地理位置（第5.1节）。如果该位置位于数据库支持的所有监管域之外，则数据库必须以“外部覆盖范围”错误进行响应（见表1）。
other: The Master Device MAY specify additional handshake parameters in the INIT_REQ message. The Database MUST ignore all parameters it does not understand. To simplify its initialization logic, a Master Device that supports multiple Databases and rulesets can include the union of all required parameters for all its supported rulesets. Consult the PAWS Parameters Registry (Section 9.2) for possible additional parameters.
其他：主设备可以在INIT_REQ消息中指定额外的握手参数。数据库必须忽略它不理解的所有参数。为了简化其初始化逻辑，支持多个数据库和规则集的主设备可以包含其所有受支持规则集的所有必需参数的并集。有关可能的其他参数，请参阅PAWS参数注册表（第9.2节）。
The initialization response message communicates database parameters to the requesting device. This response is returned only when there is at least one ruleset. Otherwise, the Database returns an error response, as described in INIT_REQ (Section 4.3.1).
初始化响应消息将数据库参数传送给请求设备。仅当至少存在一个规则集时，才会返回此响应。否则，数据库将返回一个错误响应，如INIT_REQ（第4.3.1节）所述。
+---------------------------------------+
|INIT_RESP |
+----------------------------+----------+ 1..* +-------------+
|rulesetInfos:list | REQUIRED |------->| RulesetInfo |
|databaseChange:DbUpdateSpec | OPTIONAL | +-------------+
|.......................................|
|*other:any | OPTIONAL |
+----------------------------+----------+
+---------------------------------------+
|INIT_RESP |
+----------------------------+----------+ 1..* +-------------+
|rulesetInfos:list | REQUIRED |------->| RulesetInfo |
|databaseChange:DbUpdateSpec | OPTIONAL | +-------------+
|.......................................|
|*other:any | OPTIONAL |
+----------------------------+----------+
Parameters:
参数：
rulesetInfos: A RulesetInfo (Section 5.6) list MUST be included in the response. Each RulesetInfo corresponds to a ruleset supported by the Database and is applicable to the location specified in the INIT_REQ (Section 4.3.1) message.
RulesetInfo：响应中必须包含RulesetInfo（第5.6节）列表。每个RulesetInfo对应于数据库支持的规则集，并适用于INIT_REQ（第4.3.1节）消息中指定的位置。
If the device included a list of ruleset IDs in the DeviceDescriptor of its INIT_REQ message, each RulesetInfo in the response MUST match one of the specified ruleset IDs.
如果设备在其INIT_REQ消息的DeviceDescriptor中包含规则集ID列表，则响应中的每个规则集信息必须与指定的规则集ID之一匹配。
If the DeviceDescriptor did not contain any ruleset IDs, the Database SHOULD include in the rulesetInfos list a RulesetInfo for each ruleset it supports at the specified location.
如果DeviceDescriptor不包含任何规则集ID，则数据库应在rulesetInfos列表中包含其在指定位置支持的每个规则集的RulesetInfo。
If the Database does not support the device or supports none of the rulesets specified in the DeviceDescriptor, it MUST instead return an error with the UNSUPPORTED code (see Table 1) in the error response.
如果数据库不支持该设备或不支持DeviceDescriptor中指定的任何规则集，则必须在错误响应中返回一个包含不支持代码的错误（请参见表1）。
databaseChange: The Database MAY include a DbUpdateSpec (Section 5.7) to notify the Master Device of a change to the database URI, providing one or more alternate database URIs. The device needs to update its preconfigured entry for the responding Database with the alternate Databases listed in the DbUpdateSpec.
databaseChange：数据库可能包括一个DbUpdateSpec（第5.7节），用于通知主设备数据库URI的更改，提供一个或多个备用数据库URI。设备需要使用DbUpdateSpec中列出的备用数据库更新其响应数据库的预配置条目。
other: The Database MAY include additional handshake parameters in the INIT_RESP (Section 4.3.2) message. The Master Device MUST ignore all parameters it does not understand. Consult the PAWS Parameters Registry (Section 9.2) for possible additional parameters.
其他：数据库可能在INIT_RESP（第4.3.2节）消息中包含其他握手参数。主设备必须忽略其不了解的所有参数。有关可能的其他参数，请参阅PAWS参数注册表（第9.2节）。
Some rulesets require a Master Device to send its registration information to the Database in order to establish certain operational parameters. FCC rules, for example, require that a 'Fixed Device' register its owner and operator contact information, its device identifier, its location, and its antenna height (see FCC CFR47-15H [FCC-CFR47-15H]).
有些规则集要求主设备将其注册信息发送到数据库，以便建立某些操作参数。例如，FCC规则要求“固定设备”登记其所有者和运营商联系信息、设备标识符、位置和天线高度（见FCC CFR47-15H[FCC-CFR47-15H]）。
The Database MAY implement device registration as a separate Device Registration request, or as part of the available-spectrum request. If the Database does not implement a separate Device Registration request, it MUST return an error with the UNIMPLEMENTED code (see Table 1) in the error-response message.
数据库可以实现作为单独的设备注册请求的设备注册，或者作为可用频谱请求的一部分的设备注册。如果数据库未实现单独的设备注册请求，则必须在错误响应消息中返回带有未实现代码的错误（参见表1）。
The Device Registration request procedure is depicted in Figure 2.
设备注册请求过程如图2所示。
o REGISTRATION_REQ (Section 4.4.1) is the device-registration request message
o 注册请求（第4.4.1节）是设备注册请求消息
o REGISTRATION_RESP (Section 4.4.2) is the device-registration response message
o 注册响应（第4.4.2节）是设备注册响应消息
+---------------+ +-------------------+
| Master Device | | Spectrum Database |
+---------------+ +-------------------+
| |
| REGISTRATION_REQ |
|------------------------>|
| |
| REGISTRATION_RESP |
|<------------------------|
| |
+---------------+ +-------------------+
| Master Device | | Spectrum Database |
+---------------+ +-------------------+
| |
| REGISTRATION_REQ |
|------------------------>|
| |
| REGISTRATION_RESP |
|<------------------------|
| |
Figure 2
图2
The registration request message contains the required registration parameters. A parameter marked as optional may be required by some rulesets.
注册请求消息包含所需的注册参数。某些规则集可能需要标记为可选的参数。
+-------------------------------------------+
|REGISTRATION_REQ |
+-------------------------------+-----------+
|deviceDesc:DeviceDescriptor | REQUIRED |
|location:GeoLocation | REQUIRED |
|deviceOwner:DeviceOwner | OPTIONAL |
|antenna:AntennaCharacteristics | OPTIONAL |
|...........................................|
|*other:any | OPTIONAL |
+-------------------------------+-----------+
+-------------------------------------------+
|REGISTRATION_REQ |
+-------------------------------+-----------+
|deviceDesc:DeviceDescriptor | REQUIRED |
|location:GeoLocation | REQUIRED |
|deviceOwner:DeviceOwner | OPTIONAL |
|antenna:AntennaCharacteristics | OPTIONAL |
|...........................................|
|*other:any | OPTIONAL |
+-------------------------------+-----------+
Parameters:
参数：
deviceDesc: The DeviceDescriptor (Section 5.2) for the Master Device is REQUIRED. The ruleset IDs included in the DeviceDescriptor indicate the rulesets for which the device wishes to register.
deviceDesc：主设备需要DeviceDescriptor（第5.2节）。DeviceDescriptor中包含的规则集ID表示设备希望注册的规则集。
location: The GeoLocation (Section 5.1) for the device is REQUIRED. More precisely, this is the location at which the device intends to operate. If the location is outside all regulatory domains supported by the Database, the Database MUST respond with an OUTSIDE_COVERAGE error (see Table 1).
位置：需要设备的地理位置（第5.1节）。更准确地说，这是设备打算操作的位置。如果该位置位于数据库支持的所有监管域之外，则数据库必须以外部覆盖率错误响应（请参见表1）。
deviceOwner: The DeviceOwner (Section 5.5) information is OPTIONAL. Some rulesets may require deviceOwner information under certain conditions. See PAWS Ruleset ID Registry (Section 9.1) for ruleset-specific requirements.
deviceOwner：deviceOwner（第5.5节）信息是可选的。某些规则集在某些情况下可能需要设备所有者信息。有关规则集的具体要求，请参见PAWS规则集ID注册表（第9.1节）。
antenna: The AntennaCharacteristics (Section 5.3) is OPTIONAL.
天线：天线特性（第5.3节）是可选的。
other: Rulesets and database implementations may require additional registration parameters. To simplify its registration logic, the Master Device MAY send a union of the registration information required by all supported rulesets. The Database MUST ignore all parameters it does not understand. Consult the PAWS Parameters Registry (Section 9.2) for possible additional parameters.
其他：规则集和数据库实现可能需要额外的注册参数。为了简化注册逻辑，主设备可以发送所有受支持规则集所需的注册信息的并集。数据库必须忽略它不理解的所有参数。有关可能的其他参数，请参阅PAWS参数注册表（第9.2节）。
The registration response message acknowledges successful registration by including a RulesetInfo message for each ruleset in which the registration is accepted. If the Database accepts the registration for none of the specified rulesets, the Database MUST return the NOT_REGISTERED error (see "Error Codes" (Section 5.17)).
注册响应消息通过为接受注册的每个规则集包含RulesetInfo消息来确认注册成功。如果数据库不接受任何指定规则集的注册，则数据库必须返回未注册的错误（请参阅“错误代码”（第5.17节））。
+---------------------------------------+
|REGISTRATION_RESP |
+----------------------------+----------+ 1..* +-------------+
|rulesetInfos:list | REQUIRED |------->| RulesetInfo |
|databaseChange:DbUpdateSpec | OPTIONAL | +-------------+
|............................|..........|
|*other:any | OPTIONAL |
+----------------------------+----------+
+---------------------------------------+
|REGISTRATION_RESP |
+----------------------------+----------+ 1..* +-------------+
|rulesetInfos:list | REQUIRED |------->| RulesetInfo |
|databaseChange:DbUpdateSpec | OPTIONAL | +-------------+
|............................|..........|
|*other:any | OPTIONAL |
+----------------------------+----------+
Parameters:
参数：
rulesetInfos: A RulesetInfo (Section 5.6) list MUST be included in the response. Each entry corresponds to a ruleset for which the registration was accepted. The list MUST contain at least one entry.
RulesetInfo：响应中必须包含RulesetInfo（第5.6节）列表。每个条目对应一个接受注册的规则集。列表必须至少包含一个条目。
Each RulesetInfo in the response MUST match one of the ruleset IDs specified in the DeviceDescriptor of REGISTRATION_REQ.
响应中的每个RulesetInfo必须与注册请求的DeviceDescriptor中指定的一个规则集ID匹配。
If the Database does not support the device or supports none of the rulesets specified in the DeviceDescriptor, it MUST instead return an error with the UNSUPPORTED code (see Table 1) in the error response.
如果数据库不支持该设备或不支持DeviceDescriptor中指定的任何规则集，则必须在错误响应中返回一个包含不支持代码的错误（请参见表1）。
databaseChange: The Database MAY include a DbUpdateSpec (Section 5.7) to notify the Master Device of a change to the database URI, providing one or more alternate database URIs. The device needs to update its preconfigured entry for the responding Database with the alternate Databases listed in the DbUpdateSpec.
databaseChange：数据库可能包括一个DbUpdateSpec（第5.7节），用于通知主设备数据库URI的更改，提供一个或多个备用数据库URI。设备需要使用DbUpdateSpec中列出的备用数据库更新其响应数据库的预配置条目。
other: Database implementations MAY return additional parameters in the registration response. The Master Device MUST ignore any parameters it does not understand. Consult the PAWS Parameters Registry (Section 9.2) for possible additional parameters.
其他：数据库实现可能会在注册响应中返回其他参数。主设备必须忽略其不了解的任何参数。有关可能的其他参数，请参阅PAWS参数注册表（第9.2节）。
To obtain the available spectrum from the Database, a Master Device sends a request that contains its geolocation and any parameters required by the ruleset (such as device identifier, capabilities, and characteristics). The Database returns a response that describes which frequencies are available, at what permissible operating power levels, and a schedule of when they are available.
为了从数据库获取可用频谱，主设备发送一个请求，其中包含其地理位置和规则集所需的任何参数（如设备标识符、能力和特征）。数据库返回一个响应，描述哪些频率可用，在什么允许的工作功率水平下，以及它们可用的时间表。
The Available Spectrum Query procedure is depicted in Figure 3.
可用的频谱查询过程如图3所示。
o AVAIL_SPECTRUM_REQ (Section 4.5.1) is the available-spectrum request message.
o AVAIL_SPECTRUM_REQ（第4.5.1节）是可用的频谱请求消息。
o AVAIL_SPECTRUM_RESP (Section 4.5.2) is the available-spectrum response message.
o AVAIL_SPECTRUM_RESP（第4.5.2节）是可用的频谱响应信息。
o AVAIL_SPECTRUM_BATCH_REQ (Section 4.5.3) is an OPTIONAL batch version of the available-spectrum request message that allows multiple locations to be specified in the request.
o AVAIL_SPECTRUM_BATCH_REQ（第4.5.3节）是可用频谱请求消息的可选批量版本，允许在请求中指定多个位置。
o AVAIL_SPECTRUM_BATCH_RESP (Section 4.5.4) is the response message for the batch version of the available-spectrum request that contains available spectrum for each location in the request.
o AVAIL_SPECTRUM_BATCH_RESP（第4.5.4节）是可用频谱请求批次版本的响应消息，其中包含请求中每个位置的可用频谱。
o SPECTRUM_USE_NOTIFY (Section 4.5.5) is the spectrum-usage notification message.
o 频谱使用通知（第4.5.5节）是频谱使用通知消息。
o SPECTRUM_USE_RESP (Section 4.5.6) is the spectrum-usage acknowledgment message.
o 频谱使用响应（第4.5.6节）是频谱使用确认消息。
+---------------+ +-------------------+
| Master Device | | Spectrum Database |
+---------------+ +-------------------+
| |
| AVAIL_SPECTRUM_REQ |
| (AVAIL_SPECTRUM_BATCH_REQ) |
|--------------------------->|
| |
| AVAIL_SPECTRUM_RESP |
| (AVAIL_SPECTRUM_BATCH_RESP)|
|<---------------------------|
| |
| (SPECTRUM_USE_NOTIFY) |
|--------------------------->|
| |
| (SPECTRUM_USE_RESP) |
|<---------------------------|
| |
+---------------+ +-------------------+
| Master Device | | Spectrum Database |
+---------------+ +-------------------+
| |
| AVAIL_SPECTRUM_REQ |
| (AVAIL_SPECTRUM_BATCH_REQ) |
|--------------------------->|
| |
| AVAIL_SPECTRUM_RESP |
| (AVAIL_SPECTRUM_BATCH_RESP)|
|<---------------------------|
| |
| (SPECTRUM_USE_NOTIFY) |
|--------------------------->|
| |
| (SPECTRUM_USE_RESP) |
|<---------------------------|
| |
Figure 3
图3
1. First, the Master Device sends an available-spectrum request message to the Database.
1. 首先，主设备向数据库发送可用频谱请求消息。
2. The Database MUST respond with an error using the NOT_REGISTERED code (see Table 1) if:
2. 在以下情况下，数据库必须使用未注册代码（见表1）以错误响应：
* registration information is required, and
* 需要注册信息，以及
* the request does not include registration information, and
* 请求不包括注册信息，以及
* the device has not previously registered with the Database
* 该设备以前未在数据库中注册
3. If the location specified in the request is outside the regulatory domain supported by the Database, the Database MUST respond with an OUTSIDE_COVERAGE error (see Table 1). If some, but not all, locations within a batch request are outside the regulatory domain supported by the Database, the Database MUST return an OK response with available spectrum for only the valid locations; otherwise, if all locations within a batch request are outside the regulatory domain, the Database MUST respond with an OUTSIDE_COVERAGE error.
3. 如果请求中指定的位置在数据库支持的监管域之外，则数据库必须以外部覆盖率错误响应（请参见表1）。如果批处理请求中的一些（但不是全部）位置不在数据库支持的监管域内，则数据库必须返回一个OK响应，该响应仅包含有效位置的可用频谱；否则，如果批处理请求中的所有位置都在管理域之外，则数据库必须以外部覆盖错误响应。
4. The Database MAY perform other validation of the request, (e.g., checking for missing required parameters or authorizations). If validation fails, the Database returns an appropriate error code (Table 1). If the request is missing required parameters, the Database MUST respond with a MISSING error (see Table 1) and SHOULD include a list of the missing parameters.
4. 数据库可以对请求执行其他验证（例如，检查缺少的所需参数或授权）。如果验证失败，数据库将返回相应的错误代码（表1）。如果请求缺少必需的参数，则数据库必须响应缺少的错误（参见表1），并应包括缺少的参数列表。
5. If the request is valid, the Database responds with an available-spectrum response message. If the ruleset requires that devices must report anticipated spectrum usage, the Database will indicate so in the response message.
5. 如果请求有效，数据库将使用可用的频谱响应消息进行响应。如果规则集要求设备必须报告预期的频谱使用情况，则数据库将在响应消息中指示。
6. If the available-spectrum response indicates that the Master Device must send a spectrum-usage notification message, the Master Device sends the notification message to the Database. Even when not required by the Database, the Master Device MAY send a notification message.
6. 如果可用频谱响应指示主设备必须发送频谱使用通知消息，则主设备将通知消息发送到数据库。即使数据库不需要，主设备也可以发送通知消息。
7. If the Database receives a spectrum-usage notification message, it MUST send a spectrum-usage acknowledgment message to the Master Device.
7. 如果数据库收到频谱使用通知消息，则必须向主设备发送频谱使用确认消息。
The procedure for a Master Device to ask for available spectrum on behalf of a Slave Device is similar, except that the process is initiated by the Slave Device. The device identifier, capabilities, and characteristics communicated in the AVAIL_SPECTRUM_REQ message MUST be those of the Slave Device, and:
主设备代表从设备请求可用频谱的过程类似，只是该过程由从设备启动。AVAIL_SPECTRUM_REQ消息中传达的设备标识符、能力和特征必须是从设备的标识符、能力和特征，并且：
o The "masterDeviceLocation" field specifying the location of the Master Device is REQUIRED.
o “masterDeviceLocation”字段指定主设备的位置是必需的。
o The "location" field specifying the location of the Slave Device is OPTIONAL, since the Slave Device may not have location-sensing capabilities.
o 指定从设备位置的“位置”字段是可选的，因为从设备可能没有位置感应功能。
Although the communication and protocol between the Slave Device and Master Device are outside the scope of this document (represented as dotted lines), the expected message sequence is shown in Figure 4.
尽管从设备和主设备之间的通信和协议不在本文档的范围内（用虚线表示），但预期的消息序列如图4所示。
+------------+ +---------------+ +-------------------+
|Slave Device| | Master Device | | Spectrum Database |
+------------+ +---------------+ +-------------------+
| | |
| AVAIL_SPEC_REQ | |
|................>| |
| | |
| | AVAIL_SPECTRUM_REQ |
| |-------------------------->|
| | |
| | AVAIL_SPECTRUM_RESP |
| |<--------------------------|
| AVAIL_SPEC_RESP | |
|<................| |
| | |
| (SPECTRUM_USE) | |
|................>| (SPECTRUM_USE_NOTIFY) |
| |-------------------------->|
| | |
| | (SPECTRUM_USE_RESP) |
| |<--------------------------|
| | |
+------------+ +---------------+ +-------------------+
|Slave Device| | Master Device | | Spectrum Database |
+------------+ +---------------+ +-------------------+
| | |
| AVAIL_SPEC_REQ | |
|................>| |
| | |
| | AVAIL_SPECTRUM_REQ |
| |-------------------------->|
| | |
| | AVAIL_SPECTRUM_RESP |
| |<--------------------------|
| AVAIL_SPEC_RESP | |
|<................| |
| | |
| (SPECTRUM_USE) | |
|................>| (SPECTRUM_USE_NOTIFY) |
| |-------------------------->|
| | |
| | (SPECTRUM_USE_RESP) |
| |<--------------------------|
| | |
Figure 4
图4
The request message for the Available Spectrum Query protocol MUST include a geolocation. Rulesets may mandate that it be the device's current location or allow it to be an anticipated location. A parameter marked as optional may be required by some rulesets.
可用频谱查询协议的请求消息必须包括地理位置。规则集可以要求它是设备的当前位置，也可以允许它是预期的位置。某些规则集可能需要标记为可选的参数。
+----------------------------------------------------+
|AVAIL_SPECTRUM_REQ |
+----------------------------------+-----------------+
|deviceDesc:DeviceDescriptor | see description |
|location:GeoLocation | see description |
|owner:DeviceOwner | OPTIONAL |
|antenna:AntennaCharacteristics | OPTIONAL |
|capabilities:DeviceCapabilities | OPTIONAL |
|masterDeviceDesc:DeviceDescriptor | OPTIONAL |
|masterDeviceLocation:GeoLocation | see description |
|requestType:string | OPTIONAL |
|..................................|.................|
|*other:any | OPTIONAL |
+----------------------------------+-----------------+
+----------------------------------------------------+
|AVAIL_SPECTRUM_REQ |
+----------------------------------+-----------------+
|deviceDesc:DeviceDescriptor | see description |
|location:GeoLocation | see description |
|owner:DeviceOwner | OPTIONAL |
|antenna:AntennaCharacteristics | OPTIONAL |
|capabilities:DeviceCapabilities | OPTIONAL |
|masterDeviceDesc:DeviceDescriptor | OPTIONAL |
|masterDeviceLocation:GeoLocation | see description |
|requestType:string | OPTIONAL |
|..................................|.................|
|*other:any | OPTIONAL |
+----------------------------------+-----------------+
Parameters:
参数：
deviceDesc: The DeviceDescriptor (Section 5.2) for the device requesting available spectrum. When the request is made by a Master Device on its own behalf, the descriptor is that of the Master Device, and it is REQUIRED. When the request is made on behalf of a Slave Device, the descriptor is that of the Slave Device, and it is REQUIRED if the "requestType" parameter is not specified. The deviceDesc parameter may be OPTIONAL for some values of requestType.
deviceDesc：用于请求可用频谱的设备的DeviceDescriptor（第5.2节）。当主设备代表其自身发出请求时，描述符是主设备的描述符，并且是必需的。当代表从设备发出请求时，描述符是从设备的描述符，如果未指定“requestType”参数，则需要该描述符。对于某些requestType值，deviceDesc参数可能是可选的。
location: The GeoLocation (Section 5.1) for the device requesting available spectrum. More precisely, this is the location at which the device intends to operate. When the request is made by the Master Device on its own behalf, the location is that of the Master Device, and it is REQUIRED. When the request is made by the Master Device on behalf of a Slave Device, the location is that of the Slave Device, and it is OPTIONAL (see also masterDeviceLocation). The location may be an anticipated position of the device to support mobile devices, but its use depends on the ruleset. If the location specifies a region, rather than a point, the Database MAY return an error with the UNIMPLEMENTED code (see Table 1), if it does not implement query by region.
位置：请求可用频谱的设备的地理位置（第5.1节）。更准确地说，这是设备打算操作的位置。当主设备代表其自身发出请求时，位置是主设备的位置，并且是必需的。当主设备代表从设备发出请求时，位置是从设备的位置，并且是可选的（另请参见主设备位置）。该位置可能是设备支持移动设备的预期位置，但其使用取决于规则集。如果该位置指定了一个区域，而不是一个点，则数据库可能会返回一个带有未实现代码的错误（请参见表1），如果它没有实现按区域的查询。
NOTE: Technically, this is the location of the radiation center of the device's antenna, but that distinction may be relevant only for fixed devices.
注：从技术上讲，这是设备天线辐射中心的位置，但这种区别可能仅与固定设备相关。
owner: The DeviceOwner (Section 5.5) information MAY be included to register the device with the Database. This enables the device to register and get spectrum-availability information in a single request. Some rulesets mandate registration for specific device types.
所有者：可以包括设备所有者（第5.5节）信息，以便在数据库中注册设备。这使设备能够在单个请求中注册和获取频谱可用性信息。某些规则集要求注册特定的设备类型。
antenna: The AntennaCharacteristics (Section 5.3) is OPTIONAL.
天线：天线特性（第5.3节）是可选的。
capabilities: The Master Device MAY include its DeviceCapabilities (Section 5.4) to limit the available-spectrum response to the spectrum that is compatible with its capabilities. The Database SHOULD NOT return spectrum that is not compatible with the specified capabilities.
能力：主设备可包括其设备能力（第5.4节），以将可用频谱响应限制为与其能力兼容的频谱。数据库不应返回与指定功能不兼容的频谱。
masterDeviceDesc: When the request is made by the Master Device on behalf of a Slave Device, the Master Device MAY provide its own descriptor.
masterDeviceDesc：当主设备代表从设备发出请求时，主设备可以提供自己的描述符。
masterDeviceLocation: When the request is made by the Master Device on behalf of a Slave Device, the Master Device MUST provide its own GeoLocation (Section 5.1).
主设备定位：当主设备代表从设备发出请求时，主设备必须提供自己的地理位置（第5.1节）。
requestType: The request type is OPTIONAL; it may be used to modify the request, but its use depends on the applicable ruleset. The request type may be used, for example, to indicate that the response should include generic Slave Device parameters without having to specify the device descriptor for a specific device. When requestType is missing, the request is for a specific device (Master or Slave), so deviceDesc is REQUIRED. The maximum length of the value is 64 octets. See the specifics in the Initial Registry Contents (Section 9.1.2) for the Ruleset ID Registry.
requestType：请求类型为可选；它可用于修改请求，但其使用取决于适用的规则集。例如，请求类型可用于指示响应应包括通用从属设备参数，而不必为特定设备指定设备描述符。如果缺少requestType，则请求是针对特定设备（主设备或从设备），因此需要deviceDesc。该值的最大长度为64个八位字节。有关规则集ID注册表，请参阅初始注册表内容（第9.1.2节）中的详细信息。
other: Rulesets and database implementations may require additional request parameters. The Database MUST ignore all parameters it does not understand. Consult the PAWS Parameters Registry (Section 9.2) for possible additional parameters.
其他：规则集和数据库实现可能需要额外的请求参数。数据库必须忽略它不理解的所有参数。有关可能的其他参数，请参阅PAWS参数注册表（第9.2节）。
The response message for the Available Spectrum Query contains one or more SpectrumSpec (Section 5.9) elements, one for each ruleset supported at the location specified in the corresponding AVAIL_SPECTRUM_REQ (Section 4.5.1) message. Each SpectrumSpec element contains a list of one or more spectrum schedules, representing permissible power levels over time:
可用频谱查询的响应消息包含一个或多个SpectrumSpec（第5.9节）元素，每个元素对应于相应AVAIL_Spectrum_REQ（第4.5.1节）消息中指定位置处支持的每个规则集。每个SpectrumSpec元素包含一个或多个频谱计划的列表，表示一段时间内允许的功率水平：
o Each spectrum schedule specifies the permissible power level for a duration defined by a pair of start and stop times. The power levels refer to permissible EIRP over a resolution bandwidth.
o 每个频谱计划规定了由一对启动和停止时间定义的持续时间内的允许功率水平。功率水平指分辨率带宽上允许的EIRP。
o Within each list of schedules, event-time intervals MUST be disjoint and MUST be sorted in increasing time.
o 在每个计划列表中，事件时间间隔必须是不相交的，并且必须按递增的时间进行排序。
o A gap in the time schedule means no spectrum is available for that time interval.
o 时间表中的间隔意味着该时间间隔没有可用的频谱。
Consider a Database that provides a schedule of available spectrum for the next 24 hours. If spectrum availability were to be different at different times of day, the response would contain a list of schedules, each transition representing some change to the spectrum availability. A device might use different strategies to select which spectrum to use, e.g.:
考虑一个数据库，它提供了未来24小时可用频谱的时间表。如果频谱可用性在一天中的不同时间不同，则响应将包含一个时间表列表，每个转换代表频谱可用性的一些变化。设备可能会使用不同的策略来选择要使用的频谱，例如：
o Always use the frequencies that permit the highest power
o 始终使用允许最高功率的频率
o Use the frequencies that are available for the longest period of time.
o 使用最长时间内可用的频率。
o Just use the first set of frequencies that matches its needs.
o 只需使用符合其需要的第一组频率。
+---------------------------------------+
|AVAIL_SPECTRUM_RESP |
+----------------------------+----------+
|timestamp:string | REQUIRED |
|deviceDesc:DeviceDescriptor | REQUIRED |
|spectrumSpecs:list | REQUIRED |-------+
|............................|..........| |
|databaseChange:DbUpdateSpec | OPTIONAL | |
|*other:any | OPTIONAL | |
+----------------------------+----------+ | 1..*
V
+-----------------------------------+
|SpectrumSpec |
+------------------------+----------+
|rulesetInfo:RulesetInfo | REQUIRED |
|spectrumSchedules:list | REQUIRED |-+
|timeRange:EventTime | OPTIONAL | |
|frequencyRanges:list | OPTIONAL | |
|needsSpectrumReport:bool| OPTIONAL | |
|maxTotalBwHz:float | OPTIONAL | |
|maxContiguousBwHz:float | OPTIONAL | |
+------------------------+----------+ |
+--------------------+
| 1..*
V
+-------------------------------+
|SpectrumSchedule |
+--------------------+----------+
|eventTime:EventTime | REQUIRED |
|spectra:list | REQUIRED |
+--------------------+----------+
+---------------------------------------+
|AVAIL_SPECTRUM_RESP |
+----------------------------+----------+
|timestamp:string | REQUIRED |
|deviceDesc:DeviceDescriptor | REQUIRED |
|spectrumSpecs:list | REQUIRED |-------+
|............................|..........| |
|databaseChange:DbUpdateSpec | OPTIONAL | |
|*other:any | OPTIONAL | |
+----------------------------+----------+ | 1..*
V
+-----------------------------------+
|SpectrumSpec |
+------------------------+----------+
|rulesetInfo:RulesetInfo | REQUIRED |
|spectrumSchedules:list | REQUIRED |-+
|timeRange:EventTime | OPTIONAL | |
|frequencyRanges:list | OPTIONAL | |
|needsSpectrumReport:bool| OPTIONAL | |
|maxTotalBwHz:float | OPTIONAL | |
|maxContiguousBwHz:float | OPTIONAL | |
+------------------------+----------+ |
+--------------------+
| 1..*
V
+-------------------------------+
|SpectrumSchedule |
+--------------------+----------+
|eventTime:EventTime | REQUIRED |
|spectra:list | REQUIRED |
+--------------------+----------+
Parameters:
参数：
timestamp: Timestamp of the response is expressed in UTC using the form, YYYY-MM-DDThh:mm:ssZ, as defined by "Date and Time on the Internet: Timestamps" [RFC3339]. This can be used by the device as a reference for the start and stop times in the spectrum schedules.
时间戳：响应的时间戳以UTC表示，格式为YYYY-MM-DDThh:MM:ssZ，由“互联网上的日期和时间：时间戳”[RFC3339]定义。设备可将其用作频谱计划中开始和停止时间的参考。
deviceDesc: The Database MUST include the DeviceDescriptor (Section 5.2) specified in the AVAIL_SPECTRUM_REQ message.
deviceDesc：数据库必须包括AVAIL_SPECTRUM_REQ消息中指定的DeviceDescriptor（第5.2节）。
spectrumSpecs: The SpectrumSpec (Section 5.9) list MUST include at least one entry. Each entry contains the schedules of available spectrum for a ruleset. The Database MAY return more than one SpectrumSpec to represent available spectrum for multiple rulesets at the specified location.
spectrumSpecs：SpectrumSpec（第5.9节）列表必须至少包含一个条目。每个条目都包含一个规则集的可用频谱计划。数据库可能返回多个SpectrumSpec，以表示指定位置多个规则集的可用频谱。
databaseChange: The Database MAY include a DbUpdateSpec (Section 5.7) to notify the device of a change to the database URI, providing one or more alternate database URIs. The device needs to update its preconfigured entry for the responding Database with the alternate Databases listed in the DbUpdateSpec.
databaseChange：数据库可能包括一个DbUpdateSpec（第5.7节），用于通知设备数据库URI的更改，提供一个或多个备用数据库URI。设备需要使用DbUpdateSpec中列出的备用数据库更新其响应数据库的预配置条目。
other: Database implementations MAY return additional parameters in the response. The device MUST ignore any parameters that it does not understand. Consult the PAWS Parameters Registry (Section 9.2) for possible additional parameters and requirements they place on the device.
其他：数据库实现可能会在响应中返回其他参数。设备必须忽略其无法理解的任何参数。查阅PAWS参数注册表（第9.2节），了解可能的附加参数及其对设备的要求。
When the stop time specified in the schedule has been reached, the device:
当达到时间表中规定的停止时间时，设备：
o MUST obtain a new spectrum-availability schedule, either by using the next one in the list (if provided) or making another Available Spectrum Query (Section 4.5).
o 必须通过使用列表中的下一个（如果提供）或进行另一个可用频谱查询（第4.5节），获得新的频谱可用性计划。
o If the device is unable to contact the Database to obtain a new schedule, it MUST treat this as equivalent to a response with no available spectrum.
o 如果设备无法联系数据库以获取新计划，则必须将其视为等同于没有可用频谱的响应。
Some rulesets also mandate that a device must obtain a new spectrum-availability schedule if the device moves beyond a threshold distance (established by the ruleset) from the actual location and all anticipated location(s) it reported in previous AVAIL_SPECTRUM_REQ or AVAIL_SPECTRUM_BATCH_REQ messages (see "maxLocationChange" in RulesetInfo (Section 5.6)). If the device is unable to contact the Database to obtain a new schedule, it MUST treat this as equivalent to a response with no available spectrum.
一些规则集还规定，如果设备从实际位置移动超过阈值距离（由规则集确定），并且在以前的AVAIL_spectrum_REQ或AVAIL_spectrum_BATCH_REQ消息中报告的所有预期位置（请参阅RulesetInfo中的“maxLocationChange”），则设备必须获得新的频谱可用性计划（第5.6节））。如果设备无法联系数据库以获取新计划，则必须将其视为等同于没有可用频谱的响应。
NOTE: The ruleset determines required device behavior when spectrum is no longer available. The ruleset also governs whether a device may request and use spectrum at anticipated locations beyond the threshold distance from its current location.
注：当频谱不再可用时，规则集确定所需的设备行为。该规则集还控制设备是否可以在超出其当前位置阈值距离的预期位置请求和使用频谱。
The Database MAY implement the batch request that allows multiple locations to be specified. This enables a portable Master Device, for example, to get available spectrum for a sequence of anticipated locations using a single request. The Database interprets each location in the batch request as if it were an independent request and returns results consistent with multiple individual AVAIL_SPECTRUM_REQ (Section 4.5.1) messages, but it returns these results in a batched response (Section 4.5.4). The request message for the batch Available Spectrum Query protocol MUST include at least one GeoLocation (Section 5.1). If the Database does not implement batch requests, it MUST return an UNIMPLEMENTED error (see Table 1).
数据库可以实现允许指定多个位置的批处理请求。例如，这使得便携式主设备能够使用单个请求获得预期位置序列的可用频谱。数据库将批处理请求中的每个位置解释为一个独立的请求，并返回与多个单独的AVAIL_SPECTRUM__REQ（第4.5.1节）消息一致的结果，但在批处理响应中返回这些结果（第4.5.4节）。批量可用频谱查询协议的请求消息必须至少包括一个地理位置（第5.1节）。如果数据库没有实现批处理请求，它必须返回一个未实现的错误（参见表1）。
NOTE: Whether anticipated locations are allowed depends on the specified ruleset. A parameter marked as optional may be required by some rulesets.
注意：是否允许预期位置取决于指定的规则集。某些规则集可能需要标记为可选的参数。
+---------------------------------------------------+
|AVAIL_SPECTRUM_BATCH_REQ |
+---------------------------------+-----------------+
|deviceDesc:DeviceDescriptor | see description |
|locations:list | REQUIRED |--+
|owner:DeviceOwner | OPTIONAL | |
|antenna:AntennaCharacteristics | OPTIONAL | |
|capabilities:DeviceCapabilities | OPTIONAL | |
|masterDeviceDesc:DeviceDescriptor| OPTIONAL | |
|masterDeviceLocation:GeoLocation | see description | |
|requestType:string | OPTIONAL | |
+.................................+.................+ |
|*other:any | OPTIONAL | |
+---------------------------------+-----------------+ |
|
1..* V
+-------------+
| GeoLocation |
+-------------+
+---------------------------------------------------+
|AVAIL_SPECTRUM_BATCH_REQ |
+---------------------------------+-----------------+
|deviceDesc:DeviceDescriptor | see description |
|locations:list | REQUIRED |--+
|owner:DeviceOwner | OPTIONAL | |
|antenna:AntennaCharacteristics | OPTIONAL | |
|capabilities:DeviceCapabilities | OPTIONAL | |
|masterDeviceDesc:DeviceDescriptor| OPTIONAL | |
|masterDeviceLocation:GeoLocation | see description | |
|requestType:string | OPTIONAL | |
+.................................+.................+ |
|*other:any | OPTIONAL | |
+---------------------------------+-----------------+ |
|
1..* V
+-------------+
| GeoLocation |
+-------------+
Parameters:
参数：
deviceDesc: The DeviceDescriptor (Section 5.2) for the device requesting available spectrum. When the request is made by a Master Device on its own behalf, the descriptor is that of the Master Device, and it is REQUIRED. When the request is made on behalf of a Slave Device, the descriptor is that of the Slave Device, and it is REQUIRED if the "requestType" parameter is not specified. The deviceDesc parameter may be OPTIONAL for some values of requestType.
deviceDesc：用于请求可用频谱的设备的DeviceDescriptor（第5.2节）。当主设备代表其自身发出请求时，描述符是主设备的描述符，并且是必需的。当代表从设备发出请求时，描述符是从设备的描述符，如果未指定“requestType”参数，则需要该描述符。对于某些requestType值，deviceDesc参数可能是可选的。
locations: The GeoLocation (Section 5.1) list for the device is REQUIRED. This allows the device to specify its actual location plus additional anticipated locations. At least one location MUST be included. This specification places no upper limit on the number of locations, but the Database MAY restrict the number of locations it supports by returning a response with fewer locations than specified in the request. If the locations specify regions, rather than points, the Database MAY return an error with the UNIMPLEMENTED code (see Table 1), if it does not implement query by region. When the request is made by a Master Device on its own behalf, the locations are those of the Master Device. When the request is made by the Master Device on behalf of a Slave Device, the locations are those of the Slave Device (see also masterDeviceLocation).
位置：需要设备的地理位置（第5.1节）列表。这允许设备指定其实际位置和其他预期位置。必须至少包括一个位置。此规范对位置的数量没有上限，但数据库可能会通过返回位置少于请求中指定位置的响应来限制其支持的位置数量。如果位置指定了区域而不是点，则数据库可能会返回未实现代码的错误（请参见表1），如果它没有实现按区域的查询。当主设备代表其自身发出请求时，位置为主设备的位置。当主设备代表从设备发出请求时，位置为从设备的位置（另请参见主设备位置）。
owner: The DeviceOwner (Section 5.5) information MAY be included to register the device with the Database. This enables the device to register and get spectrum-availability information in a single request. Some rulesets mandate registration for specific device types.
所有者：可以包括设备所有者（第5.5节）信息，以便在数据库中注册设备。这使设备能够在单个请求中注册和获取频谱可用性信息。某些规则集要求注册特定的设备类型。
antenna: The AntennaCharacteristics (Section 5.3) is OPTIONAL.
天线：天线特性（第5.3节）是可选的。
capabilities: The Master Device MAY include its DeviceCapabilities (Section 5.4) to limit the available-spectrum response to the spectrum that is compatible with its capabilities. The Database SHOULD NOT return spectrum that is not compatible with the specified capabilities.
能力：主设备可包括其设备能力（第5.4节），以将可用频谱响应限制为与其能力兼容的频谱。数据库不应返回与指定功能不兼容的频谱。
masterDeviceDesc: When the request is made by the Master Device on behalf of a Slave Device, the Master Device MAY provide its own descriptor.
masterDeviceDesc：当主设备代表从设备发出请求时，主设备可以提供自己的描述符。
masterDeviceLocation: When the request is made by the Master Device on behalf of a Slave Device, the Master Device MUST provide its own GeoLocation (Section 5.1).
主设备定位：当主设备代表从设备发出请求时，主设备必须提供自己的地理位置（第5.1节）。
requestType: The request type is an OPTIONAL parameter that may be used to modify the request, but its use depends on the applicable ruleset. The request type may be used, for example, to request generic Slave Device parameters without having to specify the device descriptor for a specific device. When the requestType parameter is missing, the request is for a specific device (Master or Slave), so deviceDesc is REQUIRED. The maximum length is 64 octets. See the ruleset specifics in the Initial Registry Contents (Section 9.1.2) for the Ruleset ID Registry.
requestType：请求类型是一个可选参数，可用于修改请求，但其使用取决于适用的规则集。例如，可以使用请求类型来请求通用从属设备参数，而不必为特定设备指定设备描述符。如果缺少requestType参数，则请求是针对特定设备（主设备或从设备），因此需要deviceDesc。最大长度为64个八位字节。有关规则集ID注册表，请参见初始注册表内容（第9.1.2节）中的规则集详细信息。
other: Rulesets and database implementations may require additional request parameters. The Database MUST ignore all parameters it does not understand. Consult the PAWS Parameters Registry (Section 9.2) for possible additional parameters.
其他：规则集和数据库实现可能需要额外的请求参数。数据库必须忽略它不理解的所有参数。有关可能的其他参数，请参阅PAWS参数注册表（第9.2节）。
The response message for the batch Available Spectrum Query contains a schedule of available spectrum for the device at multiple locations.
批次可用频谱查询的响应消息包含设备在多个位置的可用频谱计划。
+---------------------------------------+
|AVAIL_SPECTRUM_BATCH_RESP |
+----------------------------+----------+
|timestamp:string | REQUIRED |
|deviceDesc:DeviceDescriptor | REQUIRED |
|geoSpectrumSpecs:list | REQUIRED |-------+
|............................|..........| |
|databaseChange:DbUpdateSpec | OPTIONAL | |
|*other:any | OPTIONAL | |
+----------------------------+----------+ | 0..*
V
+---------------------------------+
|GeoSpectrumSpec |
+----------------------+----------+
|location:GeoLocation | REQUIRED |
|spectrumSpecs:list | REQUIRED |
+----------------------+----------+
+---------------------------------------+
|AVAIL_SPECTRUM_BATCH_RESP |
+----------------------------+----------+
|timestamp:string | REQUIRED |
|deviceDesc:DeviceDescriptor | REQUIRED |
|geoSpectrumSpecs:list | REQUIRED |-------+
|............................|..........| |
|databaseChange:DbUpdateSpec | OPTIONAL | |
|*other:any | OPTIONAL | |
+----------------------------+----------+ | 0..*
V
+---------------------------------+
|GeoSpectrumSpec |
+----------------------+----------+
|location:GeoLocation | REQUIRED |
|spectrumSpecs:list | REQUIRED |
+----------------------+----------+
Parameters:
参数：
timestamp: Timestamp of the response of the form, YYYY-MM-DDThh:mm:ssZ, as defined by "Date and Time on the Internet: Timestamps" [RFC3339]. This can be used by the device as a reference for the start and stop times in the spectrum schedules.
timestamp：表单响应的时间戳，YYYY-MM-DDThh:MM:ssZ，由“Internet上的日期和时间：时间戳”[RFC3339]定义。设备可将其用作频谱计划中开始和停止时间的参考。
deviceDesc: The Database MUST include the DeviceDescriptor (Section 5.2) specified in the AVAIL_SPECTRUM_BATCH_REQ message.
deviceDesc：数据库必须包括AVAIL_SPECTRUM_BATCH_REQ消息中指定的DeviceDescriptor（第5.2节）。
geoSpectrumSpecs: The geoSpectrumSpecs (Section 5.15) list is REQUIRED (although it MAY be empty if spectrum is unavailable). For each location, the Database MAY return one or more SpectrumSpecs (Section 5.9) to represent available spectrum for one or more rulesets. The Database MAY return available spectrum for fewer locations than requested. The order of the entries in
geoSpectrumSpecs：需要geoSpectrumSpecs（第5.15节）列表（如果光谱不可用，则该列表可能为空）。对于每个位置，数据库可能返回一个或多个SpectrumSpec（第5.9节），以表示一个或多个规则集的可用频谱。数据库返回的可用频谱可能少于请求的位置。中条目的顺序
the list is not significant, and the device MUST use the location value in each GeoSpectrumSpec entry to match available spectrum to a location.
该列表不重要，设备必须使用每个GeoSpectrumSpec条目中的位置值，以将可用光谱与位置匹配。
databaseChange: The Database MAY include a DbUpdateSpec (Section 5.7) to notify the device of a change to the database URI, providing one or more alternate database URIs. The device needs to update its preconfigured entry for the responding Database with the alternate Databases listed in the DbUpdateSpec.
databaseChange：数据库可能包括一个DbUpdateSpec（第5.7节），用于通知设备数据库URI的更改，提供一个或多个备用数据库URI。设备需要使用DbUpdateSpec中列出的备用数据库更新其响应数据库的预配置条目。
other: Database implementations MAY return additional parameters in the response. Consult the PAWS Parameters Registry (Section 9.2) for possible additional parameters and requirements they place on the device.
其他：数据库实现可能会在响应中返回其他参数。查阅PAWS参数注册表（第9.2节），了解可能的附加参数及其对设备的要求。
See "Update Requirements" (Section 4.5.2.1) for when the device must update its available spectrum data.
有关设备必须更新其可用光谱数据的时间，请参见“更新要求”（第4.5.2.1节）。
The spectrum-use notification message indicates the spectrum anticipated to be used by the device.
频谱使用通知消息指示设备预期使用的频谱。
+---------------------------------------------------+
|SPECTRUM_USE_NOTIFY |
+---------------------------------+-----------------+
|deviceDesc:DeviceDescriptor | REQUIRED |
|location:GeoLocation | see description |
|masterDeviceDesc:DeviceDescriptor| OPTIONAL |
|masterDeviceLocation:GeoLocation | see description |
|spectra:list | REQUIRED |--+
|...................................................| |
|*other:any | OPTIONAL | |
+---------------------------------+-----------------+ | 0..*
V
+--------------------------------+
|Spectrum |
+---------------------+----------+
|resolutionBwHz:float | REQUIRED |
|profiles:list | REQUIRED |
+---------------------+----------+
+---------------------------------------------------+
|SPECTRUM_USE_NOTIFY |
+---------------------------------+-----------------+
|deviceDesc:DeviceDescriptor | REQUIRED |
|location:GeoLocation | see description |
|masterDeviceDesc:DeviceDescriptor| OPTIONAL |
|masterDeviceLocation:GeoLocation | see description |
|spectra:list | REQUIRED |--+
|...................................................| |
|*other:any | OPTIONAL | |
+---------------------------------+-----------------+ | 0..*
V
+--------------------------------+
|Spectrum |
+---------------------+----------+
|resolutionBwHz:float | REQUIRED |
|profiles:list | REQUIRED |
+---------------------+----------+
Parameters:
参数：
deviceDesc: The DeviceDescriptor (Section 5.2) for the device is REQUIRED.
deviceDesc：需要设备的DeviceDescriptor（第5.2节）。
location: The GeoLocation (Section 5.1) for the device. When the notification is made by a Master Device on its own behalf, the location is that of the Master Device and is REQUIRED. When the notification is made by a Master Device on behalf of a Slave Device, the location is that of the Slave Device and is OPTIONAL but may be required by some rulesets.
位置：设备的地理位置（第5.1节）。当主设备代表其自身发出通知时，位置是主设备的位置，并且是必需的。当主设备代表从设备发出通知时，位置是从设备的位置，是可选的，但某些规则集可能需要该位置。
spectra: The Spectrum (Section 5.11) list is REQUIRED and specifies the spectrum anticipated to be used by the device; this includes profiles of frequencies and power levels. The list MAY be empty, if the device decides not to use any spectrum. For consistency, the resolution bandwidth value, "resolutionBwHz", MUST match that from one of the Spectrum (Section 5.11) elements in the corresponding AVAIL_SPECTRUM_RESP message, and the maximum power levels in the Spectrum element MUST be expressed as power (EIRP) over the specified "resolutionBwHz" value. The actual bandwidth to be used (as computed from the start and stop frequencies) MAY be different from the "resolutionBwHz" value. As an example, when the ruleset expresses maximum power spectral density in terms of maximum power over any 100 kHz band, then the "resolutionBwHz" value should be set to 100 kHz, even though the actual bandwidth used can be 20 kHz.
光谱：需要光谱（第5.11节）列表，并指定设备预期使用的光谱；这包括频率和功率级别的配置文件。如果设备决定不使用任何频谱，则列表可能为空。为保持一致性，分辨率带宽值“resolutionBwHz”必须与相应AVAIL_Spectrum_RESP消息中的一个频谱（第5.11节）元素匹配，并且频谱元素中的最大功率级必须表示为超过指定“resolutionBwHz”值的功率（EIRP）。要使用的实际带宽（根据开始和停止频率计算）可能不同于“resolutionBwHz”值。例如，当规则集以任何100 kHz频带上的最大功率表示最大功率谱密度时，“resolutionBwHz”值应设置为100 kHz，即使实际使用的带宽可能为20 kHz。
masterDeviceDesc: When the notification is made by the Master Device on behalf of a Slave Device, the Master Device MAY provide its own descriptor.
masterDeviceDesc：当主设备代表从设备发出通知时，主设备可以提供自己的描述符。
masterDeviceLocation: When the notification is made by the Master Device on behalf of a Slave Device, the Master Device MUST include its own GeoLocation (Section 5.1).
主设备位置：当主设备代表从设备发出通知时，主设备必须包括其自身的地理位置（第5.1节）。
other: Depending on the ruleset, other parameters may be required. To simplify its logic, the device MAY include the union of all parameters required by all supported rulesets. The Database MUST ignore all parameters it does not understand.
其他：根据规则集，可能需要其他参数。为了简化其逻辑，设备可以包括所有受支持规则集所需的所有参数的并集。数据库必须忽略它不理解的所有参数。
The spectrum-use response message simply acknowledges receipt of the notification.
频谱使用响应消息只是确认收到通知。
+---------------------------------------+
|SPECTRUM_USE_RESP |
+----------------------------+----------+
|databaseChange:DbUpdateSpec | OPTIONAL |
|.......................................|
|*other:any | OPTIONAL |
+----------------------------+----------+
+---------------------------------------+
|SPECTRUM_USE_RESP |
+----------------------------+----------+
|databaseChange:DbUpdateSpec | OPTIONAL |
|.......................................|
|*other:any | OPTIONAL |
+----------------------------+----------+
Parameters:
参数：
databaseChange: The Database MAY include a DbUpdateSpec (Section 5.7) to notify the device of a change to the database URI, providing one or more alternate database URIs. The device needs to update its preconfigured entry for the responding Database with the alternate Databases listed in the DbUpdateSpec.
databaseChange：数据库可能包括一个DbUpdateSpec（第5.7节），用于通知设备数据库URI的更改，提供一个或多个备用数据库URI。设备需要使用DbUpdateSpec中列出的备用数据库更新其响应数据库的预配置条目。
other: Database implementations MAY return additional parameters in the response. Consult the PAWS Parameters Registry (Section 9.2) for possible additional parameters.
其他：数据库实现可能会在响应中返回其他参数。有关可能的其他参数，请参阅PAWS参数注册表（第9.2节）。
A Slave Device needs a Master Device to ask the Database on its behalf for available spectrum. Depending on the ruleset, the Master Device also must validate with the Database that the Slave Device is permitted to operate. When the ruleset allows a Master Device to "cache" the available spectrum for a period of time, the Master Device may use the simpler Device Validation component, instead of the full Available Spectrum Query component, to validate a Slave Device.
从设备需要一个主设备代表其请求数据库提供可用频谱。根据规则集，主设备还必须使用数据库验证是否允许从设备运行。当规则集允许主设备在一段时间内“缓存”可用频谱时，主设备可以使用更简单的设备验证组件（而不是完全可用频谱查询组件）来验证从属设备。
When validating one or more Slave Devices, the Master Device sends the Database a request that includes the device identifier -- and any other parameters required by the ruleset -- for each Slave Device. The Database MUST return a response with an entry for each device to indicate whether it is permitted to use the spectrum.
验证一个或多个从属设备时，主设备向数据库发送一个请求，其中包括每个从属设备的设备标识符以及规则集所需的任何其他参数。数据库必须为每个设备返回一个带有条目的响应，以指示是否允许使用频谱。
A typical sequence for using the Device Validation request is illustrated in Figure 5, where the Master Device already has a valid set of available spectrum for Slave Devices. Note that the communication and protocol between the Slave Device and Master Device are outside the scope of this document.
使用设备验证请求的典型序列如图5所示，其中主设备已经有一组有效的从设备可用频谱。请注意，从设备和主设备之间的通信和协议不在本文档范围内。
o DEV_VALID_REQ (Section 4.6.1) is the device-validation request message.
o DEV_VALID_REQ（第4.6.1节）是设备验证请求消息。
o DEV_VALID_RESP (Section 4.6.2) is the device-validation response message.
o DEV_VALID_RESP（第4.6.2节）是设备验证响应消息。
+------------+ +---------------+ +-------------------+
|Slave Device| | Master Device | | Spectrum Database |
+------------+ +---------------+ +-------------------+
| | |
| AVAIL_SPEC_REQ | |
|................>| |
| | |
| | DEV_VALID_REQ |
| |-------------------------->|
| | |
| | DEV_VALID_RESP |
| |<--------------------------|
| AVAIL_SPEC_RESP | |
|<................| |
| | |
| (SPECTRUM_USE) | |
|................>| (SPECTRUM_USE_NOTIFY) |
| |-------------------------->|
| | |
| | (SPECTRUM_USE_RESP) |
| |<--------------------------|
+------------+ +---------------+ +-------------------+
|Slave Device| | Master Device | | Spectrum Database |
+------------+ +---------------+ +-------------------+
| | |
| AVAIL_SPEC_REQ | |
|................>| |
| | |
| | DEV_VALID_REQ |
| |-------------------------->|
| | |
| | DEV_VALID_RESP |
| |<--------------------------|
| AVAIL_SPEC_RESP | |
|<................| |
| | |
| (SPECTRUM_USE) | |
|................>| (SPECTRUM_USE_NOTIFY) |
| |-------------------------->|
| | |
| | (SPECTRUM_USE_RESP) |
| |<--------------------------|
Figure 5
图5
This request is used by a Master Device to determine which Slave Devices are permitted to operate.
主设备使用此请求来确定允许哪些从属设备操作。
+---------------------------------------------+
|DEV_VALID_REQ |
+----------------------------------+----------+
|deviceDescs:list | REQUIRED |---+
|masterDeviceDesc:DeviceDescriptor | OPTIONAL | |
+----------------------------------+----------+ |
V 1..*
+----------------------+
|DeviceDescriptor |
+----------------------+
+---------------------------------------------+
|DEV_VALID_REQ |
+----------------------------------+----------+
|deviceDescs:list | REQUIRED |---+
|masterDeviceDesc:DeviceDescriptor | OPTIONAL | |
+----------------------------------+----------+ |
V 1..*
+----------------------+
|DeviceDescriptor |
+----------------------+
Parameters:
参数：
deviceDescs: A DeviceDescriptor (Section 5.2) list is REQUIRED; it specifies the list of Slave Devices that are to be validated.
DeviceDescriptor：需要DeviceDescriptor（第5.2节）列表；它指定要验证的从属设备的列表。
masterDeviceDesc: The Master Device MAY provide its own descriptor.
masterDeviceDesc：主设备可以提供自己的描述符。
+---------------------------------------+
|DEV_VALID_RESP |
+----------------------------+----------+
|deviceValidities:list | REQUIRED |----
|databaseChange:DbUpdateSpec | OPTIONAL | |
+----------------------------+----------+ |
V 1..*
+---------------------------------------+
|DeviceValidity |
+----------------------------+----------+
|deviceDesc:DeviceDescriptor | REQUIRED |
|isValid:boolean | REQUIRED |
|reason:string | OPTIONAL |
+----------------------------+----------+
+---------------------------------------+
|DEV_VALID_RESP |
+----------------------------+----------+
|deviceValidities:list | REQUIRED |----
|databaseChange:DbUpdateSpec | OPTIONAL | |
+----------------------------+----------+ |
V 1..*
+---------------------------------------+
|DeviceValidity |
+----------------------------+----------+
|deviceDesc:DeviceDescriptor | REQUIRED |
|isValid:boolean | REQUIRED |
|reason:string | OPTIONAL |
+----------------------------+----------+
Parameters:
参数：
deviceValidities: A DeviceValidities (Section 5.16) list is REQUIRED to report the list of Slave Devices and whether each listed device is valid. The number of entries MUST match the number of DeviceDescriptors (Section 5.2) listed in the DEV_VALID_REQ message.
deviceValidities：需要deviceValidities（第5.16节）列表来报告从属设备的列表以及每个列出的设备是否有效。条目的数量必须与DEV_VALID_REQ消息中列出的DeviceDescriptor（第5.2节）的数量相匹配。
databaseChange: The Database MAY include a DbUpdateSpec (Section 5.7) to notify the device of a change to the database URI, providing one or more alternate database URIs. The device needs to update its preconfigured entry for the responding Database with the alternate Databases listed in the DbUpdateSpec.
databaseChange：数据库可能包括一个DbUpdateSpec（第5.7节），用于通知设备数据库URI的更改，提供一个或多个备用数据库URI。设备需要使用DbUpdateSpec中列出的备用数据库更新其响应数据库的预配置条目。
This section presents more details of the parameters that make up the PAWS request and response messages. It also includes a subsection that defines response codes.
本节介绍构成PAWS请求和响应消息的参数的更多详细信息。它还包括一个定义响应代码的小节。
GeoLocation is used to specify one of the following:
地理位置用于指定以下内容之一：
o a single point with optional uncertainty
o 具有可选不确定性的单点
o a region described by a polygon
o 由多边形描述的区域
These are represented using geometric shapes defined in Section 5 of "GEOPRIV Presence Information Data Format Location Object" [RFC5491], where:
使用“GEOPRIV存在信息数据格式位置对象”[RFC5491]第5节中定义的几何形状表示，其中：
o A "point" with uncertainty is represented using the Ellipse shape.
o 具有不确定性的“点”使用椭圆形状表示。
o A region is represented using the Polygon shape.
o 区域使用多边形形状表示。
The coordinates are expressed using the WGS84 datum [WGS-84], and units are degrees or meters. GeoLocation MAY also include a confidence level, expressed as a percentage. The confidence and uncertainty parameters may be required by some rulesets (see also [RFC7459]).
坐标使用WGS84基准[WGS-84]表示，单位为度或米。地理定位还可以包括置信水平，以百分比表示。某些规则集可能需要置信度和不确定性参数（另请参见[RFC7459]）。
The data model for GeoLocation is illustrated below:
地理定位的数据模型如下所示：
+------------------------------------+
|GeoLocation |
+------------------+-----------------+
|point:Ellipse | see description |
|region:Polygon | see description |
|confidence:int | OPTIONAL |
+------------------+-----------------+
Note: Point and region are mutually exclusive. Exactly one must
be present.
+------------------------------------+
|GeoLocation |
+------------------+-----------------+
|point:Ellipse | see description |
|region:Polygon | see description |
|confidence:int | OPTIONAL |
+------------------+-----------------+
Note: Point and region are mutually exclusive. Exactly one must
be present.
+-------------------------------+
|Ellipse |
+--------------------+----------+
|center:Point | REQUIRED |--+
|semiMajorAxis:float | OPTIONAL | |
|semiMinorAxis:float | OPTIONAL | |
|orientation:float | OPTIONAL | |
+--------------------+----------+ v
+---------------------------+
|Point |
+----------------+----------+
|latitude:float | REQUIRED |
|longitude:float | REQUIRED |
+----------------+----------+
+-------------------------------+
|Ellipse |
+--------------------+----------+
|center:Point | REQUIRED |--+
|semiMajorAxis:float | OPTIONAL | |
|semiMinorAxis:float | OPTIONAL | |
|orientation:float | OPTIONAL | |
+--------------------+----------+ v
+---------------------------+
|Point |
+----------------+----------+
|latitude:float | REQUIRED |
|longitude:float | REQUIRED |
+----------------+----------+
+-------------------------------+
|Polygon |
+-------------------+-----------+ 4..* +---------------------------+
|exterior:list | REQUIRED |------>|Point |
+-------------------+-----------+ +----------------+----------+
|latitude:float | REQUIRED |
|longitude:float | REQUIRED |
+----------------+----------+
+-------------------------------+
|Polygon |
+-------------------+-----------+ 4..* +---------------------------+
|exterior:list | REQUIRED |------>|Point |
+-------------------+-----------+ +----------------+----------+
|latitude:float | REQUIRED |
|longitude:float | REQUIRED |
+----------------+----------+
Parameters:
参数：
point: If present, it specifies the GeoLocation as a point. Paradoxically, a "point" is parameterized using an Ellipse, where the center represents the location of the point and the distances along the major and minor axes represent the uncertainty. The uncertainty values may be required, depending on the ruleset. Exactly one of "point" or "region" MUST be present.
点：如果存在，它将地理位置指定为点。矛盾的是，“点”是用椭圆参数化的，其中中心表示点的位置，沿长轴和短轴的距离表示不确定性。根据规则集，可能需要不确定度值。必须存在“点”或“区域”中的一个。
region: If present, it specifies the GeoLocation as a region. Exactly one of "point" or "region" MUST be present.
区域：如果存在，则将地理位置指定为区域。必须存在“点”或“区域”中的一个。
center: The center refers to the location of a GeoLocation point and is represented as the center of an ellipse.
中心：中心指地理定位点的位置，表示为椭圆的中心。
latitude, longitude: Floating-point numbers that express the latitude and longitude in degrees using the WGS84 datum [WGS-84].
纬度，经度：使用WGS84基准[WGS-84]以度表示纬度和经度的浮点数。
semiMajorAxis, semiMinorAxis: This OPTIONAL parameter expresses the location uncertainty, in meters. It is parameterized using distances along the major and minor axes of the ellipse. The default value for each parameter is 0.
semiMajorAxis，semiMinorAxis：此可选参数表示位置不确定性，单位为米。它使用沿椭圆长轴和短轴的距离进行参数化。每个参数的默认值为0。
orientation: This defines the orientation of the ellipse, expressed as the rotation, in degrees, of the semi-major axis from North towards the East. For example, when the uncertainty is greatest along the North-South direction, orientation is 0 degrees; conversely, if the uncertainty is greatest along the East-West direction, orientation is 90 degrees. When orientation is not present, the default value is 0.
方向：定义椭圆的方向，表示为半长轴从北向东的旋转（以度为单位）。例如，当南北方向的不确定性最大时，方向为0度；相反，如果东西方向的不确定性最大，则方向为90度。不存在方向时，默认值为0。
exterior: When GeoLocation describes a region, the "exterior" parameter refers to a list of latitude and longitude points that represents the vertices of a polygon. The first and last points MUST be the same. Thus, a minimum of 4 points is required. The following polygon restrictions from [RFC5491] apply:
外部：当地理位置描述区域时，“外部”参数指的是表示多边形顶点的纬度和经度点列表。第一点和最后一点必须相同。因此，至少需要4分。[RFC5491]中的以下多边形限制适用：
* A connecting line SHALL NOT cross another connecting line of the same polygon.
* 一条连接线不得与同一多边形的另一条连接线交叉。
* The vertices MUST be defined in a counter-clockwise direction, looking at them from above.
* 顶点必须以逆时针方向定义，从上面看。
* The edges of a polygon are defined by the shortest path between two points in space (not a geodesic curve). Consequently, the length between two adjacent vertices SHOULD be restricted to a maximum of 130 km.
* 多边形的边由空间中两点之间的最短路径（不是测地曲线）定义。因此，两个相邻顶点之间的长度应限制为最大130 km。
* Polygon shapes SHOULD be restricted to a maximum of 15 vertices (16 points that includes the repeated vertex).
* 多边形形状最多应限制为15个顶点（包括重复顶点的16个点）。
Additionally, all vertices are assumed to be at the same altitude.
此外，假设所有顶点处于相同的高度。
confidence: The location confidence level, as a percentage, MAY be provided. When this parameter is not provided, the default value is 95. Valid values range from 0 to 100, but, in practice, 100% confidence is not achievable. The confidence value is meaningful only when GeoLocation refers to a point with uncertainty.
置信度：可以提供位置置信度（百分比）。未提供此参数时，默认值为95。有效值的范围从0到100，但实际上，100%的置信度是不可能实现的。只有当地理位置指的是具有不确定性的点时，置信值才有意义。
The device descriptor contains parameters that identify the specific device, such as its manufacturer serial number, manufacturer's ID, and any other device characteristics required by ruleset.
设备描述符包含标识特定设备的参数，例如其制造商序列号、制造商ID和规则集要求的任何其他设备特征。
+--------------------------------+
|DeviceDescriptor |
+---------------------+----------+
|serialNumber:string | OPTIONAL |
|manufacturerId:string| OPTIONAL |
|modelId:string | OPTIONAL | 1..*
|rulesetIds:list | OPTIONAL |------>string
|.....................|..........|
|*other:any | OPTIONAL |
+---------------------+----------+
+--------------------------------+
|DeviceDescriptor |
+---------------------+----------+
|serialNumber:string | OPTIONAL |
|manufacturerId:string| OPTIONAL |
|modelId:string | OPTIONAL | 1..*
|rulesetIds:list | OPTIONAL |------>string
|.....................|..........|
|*other:any | OPTIONAL |
+---------------------+----------+
Parameters:
参数：
serialNumber: The manufacturer's device serial number is OPTIONAL, although rulesets typically require it. Its maximum length is 64 octets.
serialNumber：制造商的设备序列号是可选的，尽管规则集通常需要它。其最大长度为64个八位字节。
manufacturerId: The manufacturer's ID is OPTIONAL but may be required by some rulesets. This represents the name of the device manufacturer, and therefore ought to be consistent across all devices from the same manufacturer and distinct from that of other manufacturers. Its maximum length is 64 octets.
manufacturerId：制造商ID是可选的，但某些规则集可能需要。这代表设备制造商的名称，因此应在同一制造商的所有设备上保持一致，并与其他制造商的名称不同。其最大长度为64个八位字节。
modelId: The device's model ID is OPTIONAL but may be required by some rulesets. Its maximum length is 64 octets.
modelId：设备的型号ID是可选的，但某些规则集可能需要。其最大长度为64个八位字节。
rulesetIds: The list of identifiers for rulesets supported by the device (see Ruleset ID Registry (Section 9.1)). A Database MAY require that the device provides this list before servicing the device requests. If the Database supports none of the rulesets specified in the list, the Database MAY refuse to service the device requests. See RulesetInfo (Section 5.6) for discussion on ruleset identifiers. If present, the list MUST contain at least one entry.
RuleSetId：设备支持的规则集标识符列表（参见规则集ID注册表（第9.1节））。在为设备请求提供服务之前，数据库可能要求设备提供此列表。如果数据库不支持列表中指定的任何规则集，则数据库可能会拒绝为设备请求提供服务。有关规则集标识符的讨论，请参见规则集信息（第5.6节）。如果存在，列表必须至少包含一个条目。
other: Depending on the ruleset, other parameters may be required. The Database MUST ignore all parameters in the message it does not understand. See PAWS Parameters Registry (Section 9.2) for additional valid parameters and for the process for extending the message with more parameters. Additionally, see PAWS Ruleset ID Registry (Section 9.1) for the valid set of parameters for each ruleset.
其他：根据规则集，可能需要其他参数。数据库必须忽略它无法理解的消息中的所有参数。有关其他有效参数和使用更多参数扩展消息的过程，请参阅PAWS参数注册表（第9.2节）。此外，有关每个规则集的有效参数集，请参见PAWS规则集ID注册表（第9.1节）。
Antenna characteristics provide additional information, such as the antenna height, antenna type, etc. Whether antenna characteristics must be provided in a request depends on the device type and ruleset. Additionally, a parameter marked as optional may be required by some rulesets.
天线特性提供附加信息，如天线高度、天线类型等。是否必须在请求中提供天线特性取决于设备类型和规则集。此外，某些规则集可能需要标记为可选的参数。
+------------------------------------+
|AntennaCharacteristics |
+-------------------------+----------+
|height:float | OPTIONAL |
|heightType:enum | OPTIONAL |
|heightUncertainty:float | OPTIONAL |
|.........................|..........|
|*characteristics: | OPTIONAL |
| various | |
+-------------------------+----------+
+------------------------------------+
|AntennaCharacteristics |
+-------------------------+----------+
|height:float | OPTIONAL |
|heightType:enum | OPTIONAL |
|heightUncertainty:float | OPTIONAL |
|.........................|..........|
|*characteristics: | OPTIONAL |
| various | |
+-------------------------+----------+
Parameters:
参数：
height: The antenna height in meters. Note that the height may be negative.
高度：以米为单位的天线高度。请注意，高度可能为负值。
heightType: Valid values are:
heightType:有效值为：
AGL - Above Ground Level (default)
航空地面照明-地面以上（默认）
AMSL - Above Mean Sea Level
AMSL-高于平均海平面
heightUncertainty: The height uncertainty in meters.
高度不确定性：以米为单位的高度不确定性。
NOTE: Depending on the ruleset, additional antenna characteristics may be required, such as:
注：根据规则集，可能需要额外的天线特性，例如：
o antenna direction
o 天线方向
o antenna radiation pattern
o 天线辐射方向图
o antenna gain
o 天线增益
o antenna polarization
o 天线极化
These are not defined by the base protocol but may be added to the PAWS Parameters Registry, as needed.
这些参数不由基本协议定义，但可以根据需要添加到PAWS参数注册表中。
Device capabilities provide additional information that may be used by the device to provide additional information to the Database that can help it to determine available spectrum. If the Database does not support device capabilities, it MUST ignore the parameter altogether.
设备功能提供附加信息，设备可使用这些信息向数据库提供附加信息，以帮助其确定可用频谱。如果数据库不支持设备功能，则必须完全忽略该参数。
+-------------------------------+
|DeviceCapabilities |
+---------------------+---------+
|frequencyRanges:list |OPTIONAL |--+
|.....................|.........| |
|*other:any |OPTIONAL | |
+---------------------+---------+ | 0..*
V
+--------------------------------+
|FrequencyRange |
+----------------------+---------+
|startHz:float |REQUIRED |
|stopHz:float |REQUIRED |
+----------------------+---------+
+-------------------------------+
|DeviceCapabilities |
+---------------------+---------+
|frequencyRanges:list |OPTIONAL |--+
|.....................|.........| |
|*other:any |OPTIONAL | |
+---------------------+---------+ | 0..*
V
+--------------------------------+
|FrequencyRange |
+----------------------+---------+
|startHz:float |REQUIRED |
|stopHz:float |REQUIRED |
+----------------------+---------+
Parameters:
参数：
frequencyRanges: Optional FrequencyRange (Section 5.13) list. Each FrequencyRange element contains start and stop frequencies in which the device can operate. When specified, the Database SHOULD NOT return available spectrum that falls outside these ranges.
频率范围：可选频率范围（第5.13节）列表。每个FrequencyRange元素包含设备可以运行的启动和停止频率。指定时，数据库不应返回超出这些范围的可用频谱。
other Consult the PAWS Parameters Registry (Section 9.2) for possible additional parameters. The Database MUST ignore all parameters it does not understand.
其他参考PAWS参数注册表（第9.2节），了解可能的其他参数。数据库必须忽略它不理解的所有参数。
DeviceOwner contains information on device ownership that is provided as part of device registration. Some rulesets may require additional parameters.
DeviceOwner包含作为设备注册的一部分提供的有关设备所有权的信息。某些规则集可能需要其他参数。
+-----------------------------+
|DeviceOwner |
+------------------+----------+
|owner:vcard | REQUIRED |
|operator:vcard | OPTIONAL |
+------------------+----------+
+-----------------------------+
|DeviceOwner |
+------------------+----------+
|owner:vcard | REQUIRED |
|operator:vcard | OPTIONAL |
+------------------+----------+
Parameters:
参数：
owner: The vCard contact information for the individual or business that owns the device is REQUIRED.
所有者：需要拥有设备的个人或企业的vCard联系信息。
operator: The vCard contact information for the device operator is OPTIONAL but may be required by specific rulesets.
操作员：设备操作员的vCard联系信息是可选的，但可能是特定规则集所要求的。
See PAWS Ruleset ID Registry (Section 9.1) for ruleset-specific requirements on mandatory vCard properties. Depending on the ruleset, the Database may be required to validate the device-owner information. In these cases, the Database MUST respond with an INVALID_VALUE error (see "Error Codes" (Section 5.17)) if validation fails.
有关强制vCard属性的规则集特定要求，请参见PAWS规则集ID注册表（第9.1节）。根据规则集，可能需要数据库来验证设备所有者信息。在这些情况下，如果验证失败，数据库必须响应无效的_值错误（请参阅“错误代码”（第5.17节））。
All contact information MUST be expressed using the structure defined by the "vCard Format Specification" [RFC6350], encoded in JSON [RFC7095]. Note that the vCard specification defines maximum lengths for each parameter.
所有联系信息必须使用“vCard格式规范”[RFC6350]定义的结构表示，并用JSON[RFC7095]编码。请注意，vCard规范定义了每个参数的最大长度。
RulesetInfo contains parameters for the ruleset of a regulatory domain that is communicated using the Initialization (Section 4.3), Device Registration (Section 4.4), and Available Spectrum Query (Section 4.5) components.
RulesetInfo包含使用初始化（第4.3节）、设备注册（第4.4节）和可用频谱查询（第4.5节）组件进行通信的监管域规则集的参数。
+------------------------------------------+
|RulesetInfo |
+------------------------------------------+
|authority:string | REQUIRED |
|rulesetId:string | REQUIRED |
|maxLocationChange:float | see description |
|maxPollingSecs:int | see description |
|..........................................|
|*other:any | OPTIONAL |
+------------------------+-----------------+
+------------------------------------------+
|RulesetInfo |
+------------------------------------------+
|authority:string | REQUIRED |
|rulesetId:string | REQUIRED |
|maxLocationChange:float | see description |
|maxPollingSecs:int | see description |
|..........................................|
|*other:any | OPTIONAL |
+------------------------+-----------------+
Parameters:
参数：
authority: A string that indicates the regulatory domain to which the ruleset applies is REQUIRED. It will normally be a 2-letter country code defined by Country Codes - ISO 3166 [ISO3166-1].
权限：一个字符串，指示规则集所适用的监管域是必需的。它通常是由国家代码ISO 3166[ISO3166-1]定义的两个字母的国家代码。
rulesetId: The ID of a ruleset for the specified authority (see Ruleset ID Registry (Section 9.1)). The device can use this to determine additional device behavior required by the associated ruleset. To define new ruleset IDs, see "Defining Ruleset Identifiers" (Section 8.1).
rulesetId：指定权限的规则集ID（参见规则集ID注册表（第9.1节））。设备可以使用此选项来确定关联规则集所需的其他设备行为。要定义新的规则集ID，请参阅“定义规则集标识符”（第8.1节）。
maxLocationChange: The maximum location change in meters is REQUIRED for the Initialization Response (Section 4.3.2), but OPTIONAL otherwise. Some regulatory domains mandate that, when the device changes location by more than this specified distance, it contact the Database to get the available spectrum for the new location. If this value is provided by the Database within the context of an Available Spectrum Response (Section 4.5.2), it takes precedence over the value within the Initialization Response (Section 4.3.2).
maxLocationChange：初始化响应（第4.3.2节）需要以米为单位的最大位置变化，但在其他情况下是可选的。一些监管领域要求，当设备改变位置超过此指定距离时，它会联系数据库以获取新位置的可用频谱。如果该值由数据库在可用频谱响应（第4.5.2节）的上下文中提供，则其优先于初始化响应（第4.3.2节）中的值。
maxPollingSecs: The maximum duration, in seconds, between requests for available spectrum is REQUIRED for the Initialization Response (Section 4.3.2), but OPTIONAL otherwise. The device MUST contact the Database to get available spectrum no less frequently than this duration. If this value is provided within the context of an Available Spectrum Response (Section 4.5.2), it takes precedence over the value within the Initialization Response (Section 4.3.2).
maxPollingSecs：初始化响应需要可用频谱请求之间的最长持续时间（以秒为单位）（第4.3.2节），否则为可选。设备必须与数据库联系，以获得不低于此持续时间的可用频谱。如果该值是在可用频谱响应（第4.5.2节）的上下文中提供的，则其优先于初始化响应（第4.3.2节）中的值。
other: Depending on the ruleset, other parameters may be required. The device MUST ignore all parameters in the message it does not understand. Consult the PAWS Parameters Registry (Section 9.2) for possible additional parameters.
其他：根据规则集，可能需要其他参数。设备必须忽略其无法理解的消息中的所有参数。有关可能的其他参数，请参阅PAWS参数注册表（第9.2节）。
This element is provided by the Database to notify devices of an upcoming change to the database URI.
该元素由数据库提供，用于通知设备即将对数据库URI进行的更改。
+-------------------------------+
|DbUpdateSpec |
+---------------------+---------+ +--------------------------+
|databases:list |REQUIRED |------>|DatabaseSpec |
+---------------------+---------+ 1..* +---------------+----------+
|name:string | REQUIRED |
|uri:string | REQUIRED |
+---------------+----------+
+-------------------------------+
|DbUpdateSpec |
+---------------------+---------+ +--------------------------+
|databases:list |REQUIRED |------>|DatabaseSpec |
+---------------------+---------+ 1..* +---------------+----------+
|name:string | REQUIRED |
|uri:string | REQUIRED |
+---------------+----------+
Parameters:
参数：
databases: List of one or more DatabaseSpec (Section 5.8) entries. A device needs to update its preconfigured entry for the responding Database with the alternate Databases listed in the DbUpdateSpec.
数据库：一个或多个DatabaseSpec（第5.8节）条目的列表。设备需要使用DbUpdateSpec中列出的备用数据库更新其响应数据库的预配置条目。
This element contains the name and URI of a Database.
此元素包含数据库的名称和URI。
+--------------------------+
|DatabaseSpec |
+---------------+----------+
|name:string | REQUIRED |
|uri:string | REQUIRED |
+---------------+----------+
+--------------------------+
|DatabaseSpec |
+---------------+----------+
|name:string | REQUIRED |
|uri:string | REQUIRED |
+---------------+----------+
Parameters:
参数：
name: The display name. Its maximum length is 64 octets.
名称：显示名称。其最大长度为64个八位字节。
uri: The corresponding URI of the Database. Its maximum length is 1024 octets.
uri：数据库的对应uri。其最大长度为1024个八位字节。
The SpectrumSpec element encapsulates the schedule of available spectrum for a ruleset.
SpectrumSpec元素封装了规则集的可用频谱计划。
+---------------------------------------+
|SpectrumSpec |
+----------------------------+----------+
|rulesetInfo:RulesetInfo | REQUIRED |
|spectrumSchedules:list | REQUIRED |-----+
|timeRange:EventTime | OPTIONAL | |
|frequencyRanges:list | OPTIONAL | |
|needsSpectrumReport:boolean | OPTIONAL | |
|maxTotalBwHz:float | OPTIONAL | |
|maxContiguousBwHz:float | OPTIONAL | |
+----------------------------+----------+ |
| 1..*
V
+-------------------------------+
|SpectrumSchedule |
+--------------------+----------+
|eventTime:EventTime | REQUIRED |
|spectra:list | REQUIRED |
+--------------------+----------+
+---------------------------------------+
|SpectrumSpec |
+----------------------------+----------+
|rulesetInfo:RulesetInfo | REQUIRED |
|spectrumSchedules:list | REQUIRED |-----+
|timeRange:EventTime | OPTIONAL | |
|frequencyRanges:list | OPTIONAL | |
|needsSpectrumReport:boolean | OPTIONAL | |
|maxTotalBwHz:float | OPTIONAL | |
|maxContiguousBwHz:float | OPTIONAL | |
+----------------------------+----------+ |
| 1..*
V
+-------------------------------+
|SpectrumSchedule |
+--------------------+----------+
|eventTime:EventTime | REQUIRED |
|spectra:list | REQUIRED |
+--------------------+----------+
Parameters:
参数：
rulesetInfo: RulesetInfo (Section 5.6) is REQUIRED to identify the regulatory domain and ruleset to which the spectrum schedule applies (see Ruleset ID Registry (Section 9.1)). The device needs to use the corresponding ruleset to interpret the response. Values provided within rulesetInfo, such as maxLocationChange, take precedence over the values provided by the Initialization Procedure (Section 4.3).
rulesetInfo:rulesetInfo（第5.6节）用于识别频谱计划适用的监管域和规则集（见规则集ID注册表（第9.1节））。设备需要使用相应的规则集来解释响应。rulesetInfo中提供的值（如maxLocationChange）优先于初始化过程（第4.3节）提供的值。
spectrumSchedules: The SpectrumSchedule (Section 5.10) list is REQUIRED. At least one schedule MUST be included. More than one schedule MAY be included to represent future changes to the available spectrum. How far in advance a schedule may be provided depends on the ruleset. If more than one schedule is included, the eventTime intervals MUST be disjoint and MUST be sorted in increasing time. A gap in the time schedule indicates no available spectrum during that time-interval gap.
频谱计划：需要频谱计划（第5.10节）列表。必须至少包含一个计划。可以包括多个时间表，以表示可用频谱的未来变化。时间表提前多少取决于规则集。如果包含多个计划，则eventTime间隔必须是不相交的，并且必须按递增时间进行排序。时间表中的间隔表示在该时间间隔间隔期间没有可用频谱。
timeRange: The time range for which the specification is comprehensive is OPTIONAL. When specified, any gaps in time intervals within the spectrumSchedules element that overlap with the range specified by "timeRange" are interpreted by the device as time intervals in which there is no available spectrum.
时间范围：规范全面的时间范围是可选的。当指定时，spectrumSchedules元素中与“timeRange”指定的范围重叠的任何时间间隔间隔由设备解释为没有可用频谱的时间间隔。
frequencyRanges: Specifying the frequency ranges for which the specification is comprehensive is OPTIONAL. It is a list of disjoint FrequencyRange (Section 5.13) entries. When specified, it typically corresponds to the frequency ranges governed by the ruleset, e.g., for TV white space, the frequency ranges can correspond to the VHF and UHF bands of the associated regulatory domain. A device can combine this information with the available-spectrum specification within the spectrumSchedules element to distinguish between "unavailable spectrum" and "spectrum for which no information has been provided".
frequencyRanges：指定规范全面的频率范围是可选的。它是不相交的频率范围（第5.13节）条目列表。如有规定，其通常对应于规则集管辖的频率范围，例如，对于电视空白，频率范围可对应于相关监管域的VHF和UHF频段。设备可将该信息与spectrumSchedules元素内的可用频谱规范相结合，以区分“不可用频谱”和“未提供信息的频谱”。
needsSpectrumReport: The Database MAY return true for this parameter if spectrumSchedules list is non-empty; otherwise, the Database MAY omit this parameter altogether, in which case, the default value is false. If this parameter is present and its value is true, the device sends a SPECTRUM_USE_NOTIFY (Section 4.5.5) message to the Database; otherwise, the device SHOULD NOT send the SPECTRUM_USE_NOTIFY message. Some rulesets mandate this value be set to true.
needsSpectrumReport：如果spectrumSchedules列表非空，则数据库可能会对此参数返回true；否则，数据库可能会完全忽略此参数，在这种情况下，默认值为false。如果该参数存在且其值为真，则设备向数据库发送频谱使用通知（第4.5.5节）消息；否则，设备不应发送频谱使用通知消息。某些规则集要求将此值设置为true。
maxTotalBwHz: The Database MAY return a constraint on the maximum total bandwidth (in hertz) allowed, which may or may not be contiguous. Some rulesets mandate the Database to return this parameter. When present in the response, the device needs to apply this constraint to its spectrum-selection logic to ensure total bandwidth does not exceed this value.
maxTotalBwHz：数据库可能会返回允许的最大总带宽（以赫兹为单位）的约束，该约束可能是连续的，也可能不是连续的。某些规则集要求数据库返回此参数。当响应中存在时，设备需要将此约束应用于其频谱选择逻辑，以确保总带宽不超过此值。
maxContiguousBwHz: The Database MAY return a constraint on the maximum contiguous bandwidth (in hertz) allowed. Some rulesets mandate the Database to return this parameter. When present in the response, the device needs to apply this constraint to its spectrum-selection logic to ensure no single block of spectrum has bandwidth that exceeds this value.
MaxContinguousBWHZ：数据库可能返回允许的最大连续带宽（以赫兹为单位）的约束。某些规则集要求数据库返回此参数。当响应中存在时，设备需要将此约束应用于其频谱选择逻辑，以确保没有单个频谱块的带宽超过此值。
The SpectrumSchedule element combines EventTime (Section 5.14) with Spectrum (Section 5.11) to define a time period in which the spectrum is valid.
SpectrumSchedule元素将事件时间（第5.14节）与频谱（第5.11节）相结合，以定义频谱有效的时间段。
+-------------------------------+
|SpectrumSchedule |
+--------------------+----------+
|eventTime:EventTime | REQUIRED | +--------------------+
|spectra:list | REQUIRED |------->|Spectrum |
+--------------------+----------+ 0..* +--------------------+
|resolutionBwHz:float|
|profiles:list |
+--------------------+
+-------------------------------+
|SpectrumSchedule |
+--------------------+----------+
|eventTime:EventTime | REQUIRED | +--------------------+
|spectra:list | REQUIRED |------->|Spectrum |
+--------------------+----------+ 0..* +--------------------+
|resolutionBwHz:float|
|profiles:list |
+--------------------+
Parameters:
参数：
eventTime: The EventTime (Section 5.14) is REQUIRED to express "when" this specification is valid.
事件时间：事件时间（第5.14节）需要表示本规范有效的“时间”。
spectra: The Spectrum (Section 5.11) list is REQUIRED to specify the available spectrum and permissible power levels, one per resolutionBwHz. The list MAY be empty when there is no available spectrum.
频谱：频谱（第5.11节）列表需要指定可用频谱和允许功率水平，每个分辨率BWHz一个。当没有可用频谱时，列表可能为空。
Available spectrum can be characterized by an ordered list of spectrum profiles that defines permissible power levels over a set of frequency ranges. Each Spectrum element defines permissible power levels as maximum power spectral densities over a specified resolution bandwidth, "resolutionBwHz". Note that the spectrum
可用频谱可以通过频谱剖面的有序列表来表征，该列表定义了一组频率范围内的允许功率水平。每个频谱元素将允许功率级定义为指定分辨率带宽“resolutionBwHz”上的最大功率谱密度。注意光谱
profiles represent the "availability mask", as defined by the governing ruleset; they are not intended to encode device-level transmission-mask requirements.
配置文件表示管理规则集定义的“可用性掩码”；它们不用于编码设备级传输掩码要求。
NOTE: Within the contexts of the AVAIL_SPECTRUM_RESP (Section 4.5.2), AVAIL_SPECTRUM_BATCH_RESP (Section 4.5.4), and SPECTRUM_USE_NOTIFY (Section 4.5.5) messages, the power levels expressed within the Spectrum messages refer to EIRP. Future extensions of PAWS may use Spectrum in other contexts for other definitions of power levels.
注：在AVAIL_SPECTRUM_RESP（第4.5.2节）、AVAIL_SPECTRUM_BATCH_RESP（第4.5.4节）和SPECTRUM_USE_NOTIFY（第4.5.5节）消息的上下文中，频谱消息中表示的功率级指EIRP。PAWS的未来扩展可能会在其他情况下使用频谱来定义功率级别。
o To support a ruleset that defines different "wide-band" and "narrow-band" power levels, PAWS allows multiple Spectrum elements to be included in the available-spectrum response, each with a different resolution bandwidth.
o 为了支持定义不同“宽带”和“窄带”功率电平的规则集，PAWS允许在可用频谱响应中包括多个频谱元素，每个元素具有不同的分辨率带宽。
o When multiple Spectrum elements are included in the response, each represents a constraint that the device must satisfy (logical AND).
o 当响应中包含多个频谱元素时，每个元素表示设备必须满足的约束（逻辑和）。
o Each Spectrum element covers the range of frequencies governed by a ruleset, rather than splitting the frequencies across multiple Spectrum elements for the same resolution bandwidth.
o 每个频谱元素覆盖由规则集控制的频率范围，而不是为相同分辨率带宽在多个频谱元素之间分割频率。
o Each spectrum profile represents the maximum permissible power spectral density over a contiguous range of frequencies.
o 每个频谱剖面表示连续频率范围内的最大允许功率谱密度。
o When multiple spectrum profiles are included, they MUST be disjoint and MUST be ordered in non-decreasing frequency value.
o 当包含多个频谱剖面时，它们必须是不相交的，并且必须以非递减频率值排序。
o Gaps in frequencies between consecutive spectrum profiles represent unavailability for those frequencies.
o 连续频谱剖面之间的频率间隔表示这些频率不可用。
The following figure illustrates the Spectrum element and the SpectrumProfile list.
下图说明了Spectrum元素和SpectrumProfile列表。
+-------------------------------+
|Spectrum |
+---------------------+---------+
|resolutionBwHz:float |REQUIRED |
|profiles:list |REQUIRED |---+
+---------------------+---------+ | 0..*
V
+-----------------------------+
|SpectrumProfile |
+-------------------+---------+
|list |REQUIRED |
+-------------------+---------+
|
V 2..*
+--------------------------+
|SpectrumProfilePoint |
+----------------+---------+
|hz:float |REQUIRED |
|dbm:float |REQUIRED |
+----------------+---------+
+-------------------------------+
|Spectrum |
+---------------------+---------+
|resolutionBwHz:float |REQUIRED |
|profiles:list |REQUIRED |---+
+---------------------+---------+ | 0..*
V
+-----------------------------+
|SpectrumProfile |
+-------------------+---------+
|list |REQUIRED |
+-------------------+---------+
|
V 2..*
+--------------------------+
|SpectrumProfilePoint |
+----------------+---------+
|hz:float |REQUIRED |
|dbm:float |REQUIRED |
+----------------+---------+
Parameters:
参数：
resolutionBwHz: This parameter defines the resolution bandwidth (in hertz) over which permissible power spectral density is defined. For example, FCC regulation would require one spectrum specification at a bandwidth of 6 MHz, and ETSI regulation would require two specifications, at 0.1 MHz and 8 MHz.
resolutionBwHz：此参数定义了分辨率带宽（以赫兹为单位），在该带宽上定义了允许的功率谱密度。例如，FCC法规将要求一个带宽为6MHz的频谱规格，而ETSI法规将要求两个规格，带宽为0.1MHz和8MHz。
profiles: A SpectrumProfile (Section 5.12) list specifies permissible power levels over a set of frequency ranges. The list MAY be empty if there is no available spectrum.
配置文件：频谱配置文件（第5.12节）列表规定了一组频率范围内的允许功率水平。如果没有可用频谱，列表可能为空。
The following example shows permitted power spectral densities for a single resolution bandwidth of 6 MHz (for illustrative purposes only):
以下示例显示了6MHz单分辨率带宽的允许功率谱密度（仅用于说明目的）：
[
{
"resolutionBwHz": 6e6,
"profiles": [
[
{"hz": 5.18e8, "dbm": 30.0},
{"hz": 5.30e8, "dbm": 30.0}
],
...
]
}
]
[
{
"resolutionBwHz": 6e6,
"profiles": [
[
{"hz": 5.18e8, "dbm": 30.0},
{"hz": 5.30e8, "dbm": 30.0}
],
...
]
}
]
This is interpreted as:
这被解释为：
o Over any 6 MHz within the frequency range [518 MHz, 530 MHz), maximum permitted power is 30.0 dBm (1000 mW)
o 在频率范围[518 MHz，530 MHz]内的任何6 MHz上，最大允许功率为30.0 dBm（1000 mW）
Consider now an example with two different sets of permitted power spectral densities for the same set of frequencies over different resolution bandwidths (for illustrative purposes only):
现在考虑一个例子，其中两组不同的允许功率谱密度在不同分辨率带宽上的同一组频率（仅用于说明性目的）：
[
{
"resolutionBwHz": 6e6,
"profiles": [
[
{"hz": 5.18e8, "dbm": 30.0},
{"hz": 5.30e8, "dbm": 30.0}
],
...
]
},
{
"resolutionBwHz": 1e5,
"profiles": [
[
{"hz": 5.18e8, "dbm": 27.0},
{"hz": 5.30e8, "dbm": 27.0}
],
...
]
}
]
[
{
"resolutionBwHz": 6e6,
"profiles": [
[
{"hz": 5.18e8, "dbm": 30.0},
{"hz": 5.30e8, "dbm": 30.0}
],
...
]
},
{
"resolutionBwHz": 1e5,
"profiles": [
[
{"hz": 5.18e8, "dbm": 27.0},
{"hz": 5.30e8, "dbm": 27.0}
],
...
]
}
]
This is interpreted as:
这被解释为：
o Over any 6 MHz within the frequency range [518 MHz, 530 MHz), maximum permitted power is 30.0 dBm (1000 mW), and
o 在频率范围[518 MHz，530 MHz]内的任何6 MHz上，最大允许功率为30.0 dBm（1000 mW），以及
o Over any 100 kHz within the frequency range [518 MHz, 530 MHz), maximum permitted power is 27.0 dBm (500 mW)
o 在频率范围[518 MHz，530 MHz]内的任何100 kHz上，最大允许功率为27.0 dBm（500 mW）
This would allow, for example, operating two 100 kHz sub-channels within the indicated 12 MHz range at 500 mW each, totaling 1000 mW. Of course, many combinations are possible, as long as they satisfy both conditions.
例如，这将允许在指定的12 MHz范围内以500 mW的频率运行两个100 kHz子信道，总计1000 mW。当然，许多组合是可能的，只要它们同时满足这两个条件。
The following example encodes multiple (two) spectrum profiles, each having a gap from 530 MHz to 536 MHz (for illustrative purposes only):
以下示例对多（两）个频谱剖面进行编码，每个频谱剖面的间隔为530 MHz到536 MHz（仅用于说明目的）：
[
{
"resolutionBwHz": 6e6,
"profiles": [
[
{"hz": 5.18e8, "dbm": 30.0},
{"hz": 5.24e8, "dbm": 30.0},
{"hz": 5.24e8, "dbm": 36.0},
{"hz": 5.30e8, "dbm": 36.0}
],
[
{"hz": 5.36e8, "dbm": 30.0},
{"hz": 5.42e8, "dbm": 30.0}
],
...
]
},
{
"resolutionBwHz": 1e5,
"profiles": [
[
{"hz": 5.18e8, "dbm": 27.0},
{"hz": 5.24e8, "dbm": 27.0},
{"hz": 5.24e8, "dbm": 30.0},
{"hz": 5.30e8, "dbm": 30.0}
],
[
{"hz": 5.36e8, "dbm": 27.0},
{"hz": 5.42e8, "dbm": 27.0}
],
...
]
}
]
[
{
"resolutionBwHz": 6e6,
"profiles": [
[
{"hz": 5.18e8, "dbm": 30.0},
{"hz": 5.24e8, "dbm": 30.0},
{"hz": 5.24e8, "dbm": 36.0},
{"hz": 5.30e8, "dbm": 36.0}
],
[
{"hz": 5.36e8, "dbm": 30.0},
{"hz": 5.42e8, "dbm": 30.0}
],
...
]
},
{
"resolutionBwHz": 1e5,
"profiles": [
[
{"hz": 5.18e8, "dbm": 27.0},
{"hz": 5.24e8, "dbm": 27.0},
{"hz": 5.24e8, "dbm": 30.0},
{"hz": 5.30e8, "dbm": 30.0}
],
[
{"hz": 5.36e8, "dbm": 27.0},
{"hz": 5.42e8, "dbm": 27.0}
],
...
]
}
]
A spectrum profile is characterized by an ordered list of (frequency, power) points that represents the shape of maximum permissible power levels over a range of frequencies as a piecewise linear curve.
频谱剖面的特征是（频率、功率）点的有序列表，该列表以分段线性曲线的形式表示频率范围内最大允许功率级的形状。
o It MUST contain a minimum of two entries.
o 它必须至少包含两个条目。
o The entries in the list MUST be ordered in non-decreasing frequency values.
o 列表中的条目必须按非递减频率值排序。
o Two consecutive points MAY have the same frequency value to represent a "step function".
o 两个连续点可能具有相同的频率值，以表示“阶跃函数”。
o Three or more points MUST NOT share the same frequency value.
o 三个或更多点不得共享相同的频率值。
o The first frequency is inclusive; the last frequency is exclusive.
o 第一个频率是包容性的；最后一个频率是独占的。
NOTE: This encoding allows presentation of "ramps" where the slope of a line segment may be finite and non-zero.
注：此编码允许显示“坡道”，其中线段的坡度可能有限且非零。
The following figure illustrates the SpectrumProfile element.
下图显示了SpectrumProfile元素。
+-------------------------------+
|SpectrumProfile |
+---------------------+---------+
|list |REQUIRED |---+
+---------------------+---------+ | 2..*
V
+--------------------------+
|SpectrumProfilePoint |
+----------------+---------+
|hz:float |REQUIRED |
|dbm:float |REQUIRED |
+----------------+---------+
+-------------------------------+
|SpectrumProfile |
+---------------------+---------+
|list |REQUIRED |---+
+---------------------+---------+ | 2..*
V
+--------------------------+
|SpectrumProfilePoint |
+----------------+---------+
|hz:float |REQUIRED |
|dbm:float |REQUIRED |
+----------------+---------+
Parameters of each point in the profile:
轮廓中每个点的参数：
hz: The frequency, in hertz, at which the power level is defined.
赫兹：定义功率级的频率，单位为赫兹。
dbm: The power level, expressed as dBm per resolution bandwidth, as defined by the resolutionBwHz element of the enclosing Spectrum (Section 5.11) element.
dbm：功率级，表示为dbm/分辨率带宽，由封闭频谱（第5.11节）元素的resolutionBwHz元素定义。
FrequencyRange specifies a frequency range.
FrequencyRange指定一个频率范围。
+--------------------------------+
|FrequencyRange |
+----------------------+---------+
|startHz:float |REQUIRED |
|stopHz:float |REQUIRED |
+----------------------+---------+
+--------------------------------+
|FrequencyRange |
+----------------------+---------+
|startHz:float |REQUIRED |
|stopHz:float |REQUIRED |
+----------------------+---------+
Parameters:
参数：
startHz: The inclusive start of the frequency range (in hertz) is REQUIRED.
startHz：需要频率范围（以赫兹为单位）的包含起始值。
stopHz: The exclusive end of the frequency range (in hertz) is REQUIRED.
stopHz：需要频率范围（以赫兹为单位）的唯一端点。
The EventTime element specifies the start and stop times of an "event". This is used to indicate the time period for which a Spectrum (Section 5.11) is valid.
EventTime元素指定“事件”的开始和停止时间。这用于指示频谱（第5.11节）有效的时间段。
+---------------------------+
|EventTime |
+-----------------+---------+
|startTime:string |REQUIRED |
|stopTime:string |REQUIRED |
+-----------------+---------+
+---------------------------+
|EventTime |
+-----------------+---------+
|startTime:string |REQUIRED |
|stopTime:string |REQUIRED |
+-----------------+---------+
Parameters:
参数：
startTime: The inclusive start of the event is REQUIRED.
startTime：事件的包含性开始是必需的。
stopTime: The exclusive end of the event is REQUIRED.
stopTime：事件的独占结束是必需的。
Both times are expressed using the format, YYYY-MM-DDThh:mm:ssZ, as defined by "Date and Time on the Internet: Timestamps" [RFC3339]. The times MUST be expressed using UTC.
这两个时间都使用格式YYYY-MM-DDThh:MM:ssZ表示，如“Internet上的日期和时间：时间戳”[RFC3339]所定义。时间必须使用UTC表示。
A device that does not have access to the current date and time MUST use the timestamp at the top level of the response message as a substitute for the current time (see "Available Spectrum Response" (Section 4.5.2) and "Available Spectrum Batch Response" (Section 4.5.4)). For example,
无法访问当前日期和时间的设备必须使用响应消息顶层的时间戳来替代当前时间（参见“可用频谱响应”（第4.5.2节）和“可用频谱批响应”（第4.5.4节））。例如
o (startTime - timestamp) gives the duration that a device must wait before the event becomes "active". If the value is zero or negative, the event is already active.
o （startTime-timestamp）给出设备在事件变为“活动”之前必须等待的持续时间。如果该值为零或负值，则该事件已处于活动状态。
o If the event is already active, (stopTime - timestamp) is the duration that the event remains active. If the value is zero or negative, the event is no longer active and MUST be ignored.
o 如果事件已处于活动状态，（stopTime-timestamp）是事件保持活动状态的持续时间。如果该值为零或负值，则该事件不再处于活动状态，必须忽略。
The GeoSpectrumSpec element encapsulates the available spectrum for a location. It is returned within an AVAIL_SPECTRUM_BATCH_RESP (Section 4.5.4) batch response that contains multiple GeoSpectrumSpec entries, each matching a location provided in the batch request.
GeoSpectrumSpec元素封装了某个位置的可用光谱。它在AVAIL_SPECTRUM_BATCH_RESP（第4.5.4节）批响应中返回，该批响应包含多个GeoSpectrumSpec条目，每个条目与批请求中提供的位置相匹配。
+----------------------------------+
|GeoSpectrumSpec |
+-----------------------+----------+
|location:GeoLocation | REQUIRED |
|spectrumSpecs:list | REQUIRED |-------+
+-----------------------+----------+ |
| 1..*
V
+--------------+
| SpectrumSpec |
+--------------+
+----------------------------------+
|GeoSpectrumSpec |
+-----------------------+----------+
|location:GeoLocation | REQUIRED |
|spectrumSpecs:list | REQUIRED |-------+
+-----------------------+----------+ |
| 1..*
V
+--------------+
| SpectrumSpec |
+--------------+
Parameters:
参数：
location: The GeoLocation (Section 5.1) identifies the location at which the spectrum schedule applies.
位置：地理位置（第5.1节）确定频谱计划适用的位置。
spectrumSpecs: The SpectrumSpec (Section 5.9) list is REQUIRED. At least one entry MUST be included. Each entry represents schedules of available spectrum for a ruleset. More than one entry MAY be included to support multiple rulesets at a location.
spectrumSpecs：需要SpectrumSpec（第5.9节）列表。必须至少包含一个条目。每个条目代表一个规则集的可用频谱表。可以包含多个条目以支持一个位置的多个规则集。
The DeviceValidity element is used to indicate whether a device is valid. See Section 4.6.2.
DeviceValidity元素用于指示设备是否有效。见第4.6.2节。
+---------------------------------------+
|DeviceValidity |
+----------------------------+----------+
|deviceDesc:DeviceDescriptor | REQUIRED |
|isValid:boolean | REQUIRED |
|reason:string | OPTIONAL |
+----------------------------+----------+
+---------------------------------------+
|DeviceValidity |
+----------------------------+----------+
|deviceDesc:DeviceDescriptor | REQUIRED |
|isValid:boolean | REQUIRED |
|reason:string | OPTIONAL |
+----------------------------+----------+
Parameters:
参数：
deviceDesc: The DeviceDescriptor (Section 5.2) that was used to check for validity is REQUIRED.
deviceDesc：需要用于检查有效性的DeviceDescriptor（第5.2节）。
isValid: This is a REQUIRED boolean value that indicates whether the device is valid.
isValid：这是一个必需的布尔值，用于指示设备是否有效。
reason: If the device identifier is not valid, the Database MAY include a reason. The reason MAY be in any language. Its maximum length is 128 octets.
原因：如果设备标识符无效，数据库可能包含原因。原因可以是任何语言。其最大长度为128个八位字节。
If the Database responds to a PAWS request message with an error, it MUST include an Error element.
如果数据库响应PAWS请求消息时出现错误，则必须包含错误元素。
+----------------------------------+
|Error |
+----------------+-----------------+
|code:int | REQUIRED |
|message:string | OPTIONAL |
|data:any | see description |
+----------------+-----------------+
+----------------------------------+
|Error |
+----------------+-----------------+
|code:int | REQUIRED |
|message:string | OPTIONAL |
|data:any | see description |
+----------------+-----------------+
Parameters:
参数：
code: An integer code that indicates the error type is REQUIRED. Values MUST be within the range -32768 to 32767, inclusive.
代码：表示需要错误类型的整数代码。值必须在-32768到32767（含）范围内。
message: A description of the error is OPTIONAL. It MAY be in any language. Its maximum length is 128 octets.
消息：错误描述是可选的。它可以是任何语言。其最大长度为128个八位字节。
data: The Database MAY include additional data. For some errors, additional data may be required (see Table 1). The device MUST ignore any data parameters it does not understand.
数据：数据库可能包含其他数据。对于某些错误，可能需要额外的数据（见表1）。设备必须忽略其不了解的任何数据参数。
The following table lists predefined and reserved error codes. They are loosely grouped into the following categories:
下表列出了预定义和保留的错误代码。它们大致分为以下几类：
-100s: Indicates compatibility issues, e.g., version mismatch, unsupported or unimplemented features.
-100s：表示兼容性问题，例如版本不匹配、不支持或未实现的功能。
-200s: Indicates that the device request contains an error that needs to be modified before making another request.
-200s：表示设备请求包含错误，需要在发出另一个请求之前进行修改。
-300s: Indicates authorization-related issues.
-300s：表示与授权相关的问题。
Values that are not defined explicitly in the Error Codes Table (Table 1) below are unassigned. To define new error codes, see PAWS Error Code Registry (Section 9.3).
未在下面的错误代码表（表1）中明确定义的值将被取消分配。要定义新的错误代码，请参阅PAWS错误代码注册表（第9.3节）。
Code Name Description and Additional Parameters
------ ---------------- ---------------------------------------------
0 (reserved)
-100 (reserved)
-101 VERSION The Database does not support the specified
version of the message. This error does not
use any additional data.
-102 UNSUPPORTED The Database does not support the device.
For example, it supports none of the rulesets
specified in the request or does not support
the device, based on its device type, model,
etc. This error does not use any additional
data.
-103 UNIMPLEMENTED The Database does not implement the optional
request or optional feature. This error does
not use any additional data.
-104 OUTSIDE_COVERAGE The specified geolocation is outside the
coverage area of the Database. The Database
MAY include a DbUpdateSpec (Section 5.7) to
provide a list of alternate Databases that
might be appropriate for the requested
location. See OUTSIDE_COVERAGE Error
(Section 5.17.1) for more details.
Code Name Description and Additional Parameters
------ ---------------- ---------------------------------------------
0 (reserved)
-100 (reserved)
-101 VERSION The Database does not support the specified
version of the message. This error does not
use any additional data.
-102 UNSUPPORTED The Database does not support the device.
For example, it supports none of the rulesets
specified in the request or does not support
the device, based on its device type, model,
etc. This error does not use any additional
data.
-103 UNIMPLEMENTED The Database does not implement the optional
request or optional feature. This error does
not use any additional data.
-104 OUTSIDE_COVERAGE The specified geolocation is outside the
coverage area of the Database. The Database
MAY include a DbUpdateSpec (Section 5.7) to
provide a list of alternate Databases that
might be appropriate for the requested
location. See OUTSIDE_COVERAGE Error
(Section 5.17.1) for more details.
-105 DATABASE_CHANGE The Database has changed its URI. The Database MAY include a DbUpdateSpec (Section 5.7) in the error response to provide devices with one or more alternate database URIs. The device needs to update its preconfigured entry for the responding Database with the alternate Databases listed in the DbUpdateSpec. See DATABASE_CHANGE Error (Section 5.17.2) for more details. -200 (reserved) -201 MISSING A required parameter is missing. The Database MUST include a list of the required parameter names. The Database MAY include only names of parameters that are missing, but MAY include a full list. Including the full list of missing parameters may reduce the number of re-queries from the device. See MISSING Error (Section 5.17.3) for more details. -202 INVALID_VALUE A parameter value is invalid in some way. The Database SHOULD include a message indicating which parameter and why its value is invalid. This error does not use any additional data. -300 (reserved) -301 UNAUTHORIZED The device is not authorized to used the Database. Authorization may be determined by the ruleset or be dependent on prior arrangement between the device and Database. This error does not use any additional data. -302 NOT_REGISTERED Device registration required, but the device is not registered. This error does not use any additional data. -32000 (reserved) Reserved for JSON-RPC error codes. to -32768
-105数据库\u更改数据库已更改其URI。数据库可能在错误响应中包含DbUpdateSpec（第5.7节），以向设备提供一个或多个备用数据库URI。设备需要使用DbUpdateSpec中列出的备用数据库更新其响应数据库的预配置条目。有关更多详细信息，请参阅数据库更改错误（第5.17.2节）-200（保留）-201缺少所需参数缺少。数据库必须包含所需参数名称的列表。数据库可能只包含缺少的参数名称，但可能包含完整列表。包括缺失参数的完整列表可以减少设备的重新查询次数。有关更多详细信息，请参见缺失错误（第5.17.3节）-202无效_值参数值在某种程度上无效。数据库应包含一条消息，指示哪个参数及其值无效的原因。此错误不使用任何其他数据-300（保留）-301未经授权设备无权使用数据库。授权可以由规则集确定，也可以取决于设备和数据库之间的事先安排。此错误不使用任何其他数据-302未注册设备需要注册，但设备未注册。此错误不使用任何其他数据-32000（保留）为JSON-RPC错误代码保留。至-32768
Table 1: Error Codes
表1：错误代码
When the error code is OUTSIDE_COVERAGE, the Database MAY include an ErrorData element within its Error response as the "data" parameter, and, if present, the ErrorData contains a DbUpdateSpec (Section 5.7) element that provides a list of alternate Databases that might be appropriate for the requested location.
当错误代码超出_覆盖范围时，数据库可能在其错误响应中包含一个ErrorData元素作为“data”参数，如果存在，ErrorData包含一个DbUpdateSpec（第5.7节）元素，该元素提供可能适合请求位置的备用数据库列表。
+---------------------------+
|Error |
+----------------+----------+
|code:int | REQUIRED |
|message:string | OPTIONAL | +-----------------------------+
|data:ErrorData | OPTIONAL |--->|ErrorData |
+----------------+----------+ +------------------+----------+
|spec:DbUpdateSpec | OPTIONAL |
+------------------+----------+
+---------------------------+
|Error |
+----------------+----------+
|code:int | REQUIRED |
|message:string | OPTIONAL | +-----------------------------+
|data:ErrorData | OPTIONAL |--->|ErrorData |
+----------------+----------+ +------------------+----------+
|spec:DbUpdateSpec | OPTIONAL |
+------------------+----------+
When the error code is DATABASE_CHANGE, the Database MAY include an ErrorData element within its Error response as the "data" parameter, and, if present, the ErrorData contains a DbUpdateSpec (Section 5.7) element that provides a list of alternate Databases.
当错误代码为DATABASE_CHANGE时，数据库可能在其错误响应中包含一个ErrorData元素作为“data”参数，如果存在，ErrorData包含一个DbUpdateSpec（第5.7节）元素，该元素提供备用数据库的列表。
+---------------------------+
|Error |
+----------------+----------+
|code:int | REQUIRED |
|message:string | OPTIONAL | +-----------------------------+
|data:ErrorData | OPTIONAL |--->|ErrorData |
+----------------+----------+ +------------------+----------+
|spec:DbUpdateSpec | REQUIRED |
+------------------+----------+
+---------------------------+
|Error |
+----------------+----------+
|code:int | REQUIRED |
|message:string | OPTIONAL | +-----------------------------+
|data:ErrorData | OPTIONAL |--->|ErrorData |
+----------------+----------+ +------------------+----------+
|spec:DbUpdateSpec | REQUIRED |
+------------------+----------+
When the error code is MISSING, the Database MUST include an ErrorData element within its Error response as the "data" parameter, and the ErrorData element MUST include a list of the missing required parameters and MAY include the list of all required parameters.
当错误代码缺失时，数据库必须在其错误响应中包含一个ErrorData元素作为“data”参数，ErrorData元素必须包含缺失所需参数的列表，并且可能包含所有所需参数的列表。
+---------------------------+
|Error |
+----------------+----------+
|code:int | REQUIRED |
|message:string | OPTIONAL | +---------------------------+
|data:ErrorData | REQUIRED |--->|ErrorData |
+----------------+----------+ +----------------+----------+ 1..*
|parameters:list | REQUIRED |--+
+----------------+----------+ |
v
string
+---------------------------+
|Error |
+----------------+----------+
|code:int | REQUIRED |
|message:string | OPTIONAL | +---------------------------+
|data:ErrorData | REQUIRED |--->|ErrorData |
+----------------+----------+ +----------------+----------+ 1..*
|parameters:list | REQUIRED |--+
+----------------+----------+ |
v
string
Parameters:
参数：
parameters: List of one or more parameter names (strings). The name of a parameter is expressed using dotted notation, when appropriate, e.g., "deviceDesc.serialNumber".
参数：一个或多个参数名称（字符串）的列表。参数的名称在适当时使用点符号表示，例如“deviceDesc.serialNumber”。
PAWS is encoded using JSON-RPC [JSON-RPC] (see also "The JavaScript Object Notation (JSON) Data Interchange Format" [RFC7159]). Each component described in Protocol Functionalities (Section 4) corresponds to one or more JSON-RPC methods. This section discusses how to encode the data models presented in Sections 4 and 5 into JSON and provides some example encodings. The JSON examples may contain ellipses (...) to represent additional properties or elements that have been omitted in order to make the examples more concise.
PAWS使用JSON-RPC[JSON-RPC]编码（另请参见“JavaScript对象表示法（JSON）数据交换格式”[RFC7159]）。协议功能（第4节）中描述的每个组件对应于一个或多个JSON-RPC方法。本节讨论如何将第4节和第5节中介绍的数据模型编码为JSON，并提供一些示例编码。JSON示例可能包含省略号（…），以表示为使示例更简洁而省略的其他属性或元素。
The JSON-RPC [JSON-RPC] protocol consists of two basic objects, Request and Response:
JSON-RPC[JSON-RPC]协议由两个基本对象（请求和响应）组成：
o The JSON-RPC Request object encapsulates a PAWS functionality (operation) and the request message.
o JSON-RPC请求对象封装了PAWS功能（操作）和请求消息。
o The JSON-RPC Response object encapsulates a PAWS response message and an Error element.
o JSON-RPC响应对象封装了PAWS响应消息和错误元素。
The Database and device MUST support JSON-RPC 2.0 encoding, with the restriction that the "id" parameter in the messages MUST be a string. The device should generate the "id" uniquely enough to allow the use of JSON-RPC batch.
数据库和设备必须支持JSON-RPC 2.0编码，限制消息中的“id”参数必须是字符串。设备应生成足够唯一的“id”，以允许使用JSON-RPC批处理。
The JSON-RPC Request for PAWS has the following form:
PAWS的JSON-RPC请求具有以下形式：
{
"jsonrpc": "2.0",
"method": "spectrum.paws.methodName",
"params": <PAWS_REQ>,
"id": "idString"
}
{
"jsonrpc": "2.0",
"method": "spectrum.paws.methodName",
"params": <PAWS_REQ>,
"id": "idString"
}
where "method" is the name of a PAWS functionality (operation), and <PAWS_REQ> represents one of the PAWS request messages associated with the method (see Sections 4.3 through 4.6). Method names are defined with the prefix "spectrum.paws.".
其中，“方法”是PAWS功能（操作）的名称，<PAWS_REQ>表示与该方法相关的PAWS请求消息之一（见第4.3节至第4.6节）。方法名称是用前缀“spectrum.paws”定义的。
The non-error JSON-RPC Response for PAWS has the following form:
PAWS的无错误JSON-RPC响应具有以下形式：
{
"jsonrpc": "2.0",
"result": <PAWS_RESP>,
"id": "idString"
}
{
"jsonrpc": "2.0",
"result": <PAWS_RESP>,
"id": "idString"
}
where <PAWS_RESP> represents one of the PAWS response messages associated with the method, and "id" is copied from the request.
其中，<PAWS_RESP>表示与该方法相关联的PAWS响应消息之一，并且从请求复制“id”。
The error JSON-RPC Response for PAWS has the following form:
PAWS的错误JSON-RPC响应具有以下形式：
{
"jsonrpc": "2.0",
"error": {
"code": -102,
"message": "An appropriate error message.",
"data": { ... }
},
"id": "idString"
}
{
"jsonrpc": "2.0",
"error": {
"code": -102,
"message": "An appropriate error message.",
"data": { ... }
},
"id": "idString"
}
where the "error" object corresponds to the Error Element (Section 5.17), and "code" is an error code described in the same section. The Database SHOULD attempt to use the most specific applicable PAWS error code. When an accurate one is not available, it SHOULD fall back to standard JSON-RPC error codes as defined in the JSON-RPC specification. For example, if the Database receives invalid JSON from the device, it should respond with "-32700", signifying a parse error. As a last resort, the Database MAY send a suitable HTTP 5xx response.
其中，“错误”对象对应于错误元素（第5.17节），“代码”是同一节中描述的错误代码。数据库应尝试使用最具体的适用PAWS错误代码。如果没有准确的错误代码，则应返回JSON-RPC规范中定义的标准JSON-RPC错误代码。例如，如果数据库从设备接收到无效的JSON，它应该以“-32700”响应，表示解析错误。作为最后手段，数据库可能会发送适当的HTTP 5xx响应。
Table 2 defines the method name, request object, and response object for each functionality defined in Protocol Functionalities (Section 4).
表2定义了协议功能（第4节）中定义的每个功能的方法名称、请求对象和响应对象。
+-------------------------------------------------------------------+
| Method Name |
| Request |
| Response |
+-------------------------------------------------------------------+
| spectrum.paws.init |
| INIT_REQ (Section 4.3.1) |
| INIT_RESP (Section 4.3.2) |
| |
| spectrum.paws.register |
| REGISTRATION_REQ (Section 4.4.1) |
| REGISTRATION_RESP (Section 4.4.2) |
| |
| spectrum.paws.getSpectrum |
| AVAIL_SPECTRUM_REQ (Section 4.5.1) |
| AVAIL_SPECTRUM_RESP (Section 4.5.2) |
| |
| spectrum.paws.getSpectrumBatch |
| AVAIL_SPECTRUM_BATCH_REQ (Section 4.5.3) |
| AVAIL_SPECTRUM_BATCH_RESP (Section 4.5.4) |
| |
| spectrum.paws.notifySpectrumUse |
| SPECTRUM_USE_NOTIFY (Section 4.5.5) |
| SPECTRUM_USE_RESP (Section 4.5.6) |
| |
| spectrum.paws.verifyDevice |
| DEV_VALID_REQ (Section 4.6.1) |
| DEV_VALID_RESP (Section 4.6.2) |
+-------------------------------------------------------------------+
+-------------------------------------------------------------------+
| Method Name |
| Request |
| Response |
+-------------------------------------------------------------------+
| spectrum.paws.init |
| INIT_REQ (Section 4.3.1) |
| INIT_RESP (Section 4.3.2) |
| |
| spectrum.paws.register |
| REGISTRATION_REQ (Section 4.4.1) |
| REGISTRATION_RESP (Section 4.4.2) |
| |
| spectrum.paws.getSpectrum |
| AVAIL_SPECTRUM_REQ (Section 4.5.1) |
| AVAIL_SPECTRUM_RESP (Section 4.5.2) |
| |
| spectrum.paws.getSpectrumBatch |
| AVAIL_SPECTRUM_BATCH_REQ (Section 4.5.3) |
| AVAIL_SPECTRUM_BATCH_RESP (Section 4.5.4) |
| |
| spectrum.paws.notifySpectrumUse |
| SPECTRUM_USE_NOTIFY (Section 4.5.5) |
| SPECTRUM_USE_RESP (Section 4.5.6) |
| |
| spectrum.paws.verifyDevice |
| DEV_VALID_REQ (Section 4.6.1) |
| DEV_VALID_RESP (Section 4.6.2) |
+-------------------------------------------------------------------+
Table 2: Method Names
表2：方法名称
JSON [RFC7159] encoding of the data models described in Sections 4 and 5 is straightforward:
第4节和第5节中描述的数据模型的JSON[RFC7159]编码非常简单：
o Each data model describes the contents of a JSON object.
o 每个数据模型描述JSON对象的内容。
o Each parameter of a data model corresponds to a member of the corresponding JSON object:
o 数据模型的每个参数对应于相应JSON对象的一个成员：
* The parameter name of the data model is the same as the member name of the JSON object.
* 数据模型的参数名与JSON对象的成员名相同。
* The parameter data type describes the type of the member value.
* 参数数据类型描述成员值的类型。
o Primitive types map to JSON type, as described in Section 4 and repeated here:
o 原语类型映射到JSON类型，如第4节所述，并在此处重复：
string: A JSON string, restricted to UTF-8 encoding
字符串：一个JSON字符串，限制为UTF-8编码
int: A JSON number, without a fractional or exponent part
int：一个JSON数字，没有分数或指数部分
float: A JSON number
float：一个JSON数字
boolean: One of the JSON values, true or false
布尔值：JSON值之一，true或false
o The list type maps to a JSON array, except that all values in the array are of the same type.
o 列表类型映射到JSON数组，但数组中的所有值都是相同的类型。
o When the parameter data type refers to another data model, that data model describes a nested JSON object.
o 当参数数据类型引用另一个数据模型时，该数据模型描述一个嵌套的JSON对象。
o The encoded JSON object for each of the Request and Response message listed in the Method Names Table (Table 2) also includes the following members:
o 方法名称表（表2）中列出的每个请求和响应消息的编码JSON对象还包括以下成员：
type: The name of the message, e.g., "INIT_REQ"
类型：消息的名称，例如“INIT_REQ”
version: The PAWS version, e.g., "1.0"
版本：PAWS版本，例如“1.0”
See the following sections for examples.
有关示例，请参见以下各节。
An example of the "spectrum.paws.init" JSON-RPC request is shown below.
下面显示了“spectrum.paws.init”JSON-RPC请求的示例。
{
"jsonrpc": "2.0",
"method": "spectrum.paws.init",
"params": {
"type": "INIT_REQ",
"version": "1.0",
"deviceDesc": {
"serialNumber": "XXX",
"fccId": "YYY",
"rulesetIds": ["FccTvBandWhiteSpace-2010"]
},
"location": {
"point": {
"center": {"latitude": 37.0, "longitude": -101.3}
}
}
},
"id": "xxxxxx"
}
{
"jsonrpc": "2.0",
"method": "spectrum.paws.init",
"params": {
"type": "INIT_REQ",
"version": "1.0",
"deviceDesc": {
"serialNumber": "XXX",
"fccId": "YYY",
"rulesetIds": ["FccTvBandWhiteSpace-2010"]
},
"location": {
"point": {
"center": {"latitude": 37.0, "longitude": -101.3}
}
}
},
"id": "xxxxxx"
}
An example of the corresponding JSON-RPC response is shown below.
对应的JSON-RPC响应示例如下所示。
{
"jsonrpc": "2.0",
"result": {
"type": "INIT_RESP",
"version": "1.0",
"rulesetInfos": [
{
"authority": "us",
"rulesetId": "FccTvBandWhiteSpace-2010",
"maxLocationChange": 100,
"maxPollingSecs": 86400
}
]
},
"id": "xxxxxx"
}
{
"jsonrpc": "2.0",
"result": {
"type": "INIT_RESP",
"version": "1.0",
"rulesetInfos": [
{
"authority": "us",
"rulesetId": "FccTvBandWhiteSpace-2010",
"maxLocationChange": 100,
"maxPollingSecs": 86400
}
]
},
"id": "xxxxxx"
}
An example of the "spectrum.paws.getSpectrum" JSON-RPC request is shown below:
“spectrum.paws.getSpectrum”JSON-RPC请求的示例如下所示：
{
"jsonrpc": "2.0",
"method": "spectrum.paws.getSpectrum",
"params": {
"type": "AVAIL_SPECTRUM_REQ",
"version": "1.0",
"deviceDesc": {
"serialNumber": "XXX",
"fccId": "YYY",
"rulesetIds": ["FccTvBandWhiteSpace-2010"]
},
"location": {
"point": {
"center": {"latitude": 37.0, "longitude": -101.3}
}
},
"antenna": {"height": 10.2, "heightType": "AGL"}
},
"id": "xxxxxx"
}
{
"jsonrpc": "2.0",
"method": "spectrum.paws.getSpectrum",
"params": {
"type": "AVAIL_SPECTRUM_REQ",
"version": "1.0",
"deviceDesc": {
"serialNumber": "XXX",
"fccId": "YYY",
"rulesetIds": ["FccTvBandWhiteSpace-2010"]
},
"location": {
"point": {
"center": {"latitude": 37.0, "longitude": -101.3}
}
},
"antenna": {"height": 10.2, "heightType": "AGL"}
},
"id": "xxxxxx"
}
The following example "spectrum.paws.getSpectrum" JSON-RPC response contains:
以下示例“spectrum.paws.getSpectrum”JSON-RPC响应包含：
o A schedule with two time ranges
o 有两个时间范围的时间表
o A spectrum profile for one resolution bandwidth (6 MHz)
o 一个分辨率带宽（6 MHz）的频谱剖面图
o The power levels for two frequency segments:
o 两个频率段的功率水平：
* From 518 MHz to 542 MHz
* 从518兆赫到542兆赫
* From 620 MHz to 626 MHz
* 从620兆赫到626兆赫
o In practice, each "profiles" list contains (frequency, power) points to cover all frequencies governed by the associated ruleset. See "Spectrum" (Section 5.11) for a more detailed discussion on the representation.
o 实际上，每个“配置文件”列表都包含（频率、功率）点，以涵盖由相关规则集管理的所有频率。有关表示的更详细讨论，请参见“光谱”（第5.11节）。
{
"jsonrpc": "2.0",
"result": {
"type": "AVAIL_SPECTRUM_RESP",
"version": "1.0",
"timestamp": "2013-03-02T14:30:21Z",
"deviceDesc": {
"serialNumber": "XXX",
"fccId": "YYY",
"rulesetIds": ["FccTvBandWhiteSpace-2010"]
},
"spectrumSpecs": [
{
"rulesetInfo": {
"authority": "us",
"rulesetId": "FccTvBandWhiteSpace-2010"
},
"needsSpectrumReport": false,
"spectrumSchedules": [
{
"eventTime": {
"startTime": "2013-03-02T14:30:21Z",
"stopTime": "2013-03-02T20:00:00Z"
},
"spectra": [
{
"resolutionBwHz": 6e6,
"profiles": [
...
[
{"hz":5.18e8, "dbm":30.0},
{"hz":5.36e8, "dbm":30.0},
{"hz":5.36e8, "dbm":36.0},
{"hz":5.42e8, "dbm":36.0}
],
[
{"hz":6.20e8, "dbm":30.0},
{"hz":6.26e8, "dbm":30.0}
],
...
]
}
]
},
{
"eventTime": {
"startTime": "2013-03-02T22:00:00Z",
"stopTime": "2013-03-03T14:30:21Z"
{
"jsonrpc": "2.0",
"result": {
"type": "AVAIL_SPECTRUM_RESP",
"version": "1.0",
"timestamp": "2013-03-02T14:30:21Z",
"deviceDesc": {
"serialNumber": "XXX",
"fccId": "YYY",
"rulesetIds": ["FccTvBandWhiteSpace-2010"]
},
"spectrumSpecs": [
{
"rulesetInfo": {
"authority": "us",
"rulesetId": "FccTvBandWhiteSpace-2010"
},
"needsSpectrumReport": false,
"spectrumSchedules": [
{
"eventTime": {
"startTime": "2013-03-02T14:30:21Z",
"stopTime": "2013-03-02T20:00:00Z"
},
"spectra": [
{
"resolutionBwHz": 6e6,
"profiles": [
...
[
{"hz":5.18e8, "dbm":30.0},
{"hz":5.36e8, "dbm":30.0},
{"hz":5.36e8, "dbm":36.0},
{"hz":5.42e8, "dbm":36.0}
],
[
{"hz":6.20e8, "dbm":30.0},
{"hz":6.26e8, "dbm":30.0}
],
...
]
}
]
},
{
"eventTime": {
"startTime": "2013-03-02T22:00:00Z",
"stopTime": "2013-03-03T14:30:21Z"
},
"spectra": [
...
]
}
]
}
]
},
"id": "xxxxxx"
}
},
"spectra": [
...
]
}
]
}
]
},
"id": "xxxxxx"
}
The following example "spectrum.paws.getSpectrum" JSON-RPC response includes a spectrum profile that contains specifications for two different bandwidth resolutions (6 MHz and 100 kHz):
以下示例“spectrum.paws.getSpectrum”JSON-RPC响应包括一个频谱配置文件，其中包含两种不同带宽分辨率（6 MHz和100 kHz）的规范：
{
"jsonrpc": "2.0",
"result": {
"type": "AVAIL_SPECTRUM_RESP",
"version": "1.0",
"timestamp": "2013-03-02T14:30:21Z",
"deviceDesc": {
"serialNumber": "XXX",
...
},
"spectrumSpecs": [
{
"rulesetInfo": {
"authority": "xx",
...
},
"needsSpectrumReport": false,
"spectrumSchedules": [
{
"eventTime": {
"startTime": "2013-03-02T14:30:21Z",
"stopTime": "2013-03-02T20:00:00Z"
},
"spectra": [
{
"resolutionBwHz": 6e6,
"profiles": [
...
[
{"hz":5.18e8, "dbm":30.0},
{"hz":5.36e8, "dbm":30.0},
{"hz":5.36e8, "dbm":36.0},
{
"jsonrpc": "2.0",
"result": {
"type": "AVAIL_SPECTRUM_RESP",
"version": "1.0",
"timestamp": "2013-03-02T14:30:21Z",
"deviceDesc": {
"serialNumber": "XXX",
...
},
"spectrumSpecs": [
{
"rulesetInfo": {
"authority": "xx",
...
},
"needsSpectrumReport": false,
"spectrumSchedules": [
{
"eventTime": {
"startTime": "2013-03-02T14:30:21Z",
"stopTime": "2013-03-02T20:00:00Z"
},
"spectra": [
{
"resolutionBwHz": 6e6,
"profiles": [
...
[
{"hz":5.18e8, "dbm":30.0},
{"hz":5.36e8, "dbm":30.0},
{"hz":5.36e8, "dbm":36.0},
{"hz":5.42e8, "dbm":36.0}
],
[
{"hz":6.20e8, "dbm":30.0},
{"hz":6.26e8, "dbm":30.0}
],
...
]
},
{
"resolutionBwHz": 1e5,
"profiles": [
...
[
{"hz":5.18e8, "dbm":27.0},
{"hz":5.36e8, "dbm":27.0},
{"hz":5.36e8, "dbm":30.0},
{"hz":5.42e8, "dbm":30.0}
],
[
{"hz":6.20e8, "dbm":27.0},
{"hz":6.26e8, "dbm":27.0}
],
...
]
}
]
},
{
"eventTime": {
"startTime": "2013-03-02T22:00:00Z",
"stopTime": "2013-03-03T14:30:21Z"
},
"spectra": [
...
]
}
]
}
]
},
"id": "xxxxxx"
}
{"hz":5.42e8, "dbm":36.0}
],
[
{"hz":6.20e8, "dbm":30.0},
{"hz":6.26e8, "dbm":30.0}
],
...
]
},
{
"resolutionBwHz": 1e5,
"profiles": [
...
[
{"hz":5.18e8, "dbm":27.0},
{"hz":5.36e8, "dbm":27.0},
{"hz":5.36e8, "dbm":30.0},
{"hz":5.42e8, "dbm":30.0}
],
[
{"hz":6.20e8, "dbm":27.0},
{"hz":6.26e8, "dbm":27.0}
],
...
]
}
]
},
{
"eventTime": {
"startTime": "2013-03-02T22:00:00Z",
"stopTime": "2013-03-03T14:30:21Z"
},
"spectra": [
...
]
}
]
}
]
},
"id": "xxxxxx"
}
The DeviceOwner (Section 5.5) data model contains member values that are JSON encodings of vCard, as described in "jCard: The JSON format for vCard" [RFC7095]. An example fragment is provided below:
DeviceOwner（第5.5节）数据模型包含vCard的JSON编码的成员值，如“jCard:vCard的JSON格式”[RFC7095]所述。下面提供了一个示例片段：
{
...
"deviceOwner": {
"owner": [
"vcard", [
["version", {}, "text", "4.0"],
["kind", {}, "text", "org"],
["fn", {}, "text", "Racafrax, Inc."]
]
],
"operator": [
"vcard", [
["version", {}, "text", "4.0"],
["fn", {}, "text", "John Frax"],
["adr", {}, "text",
["", "", "100 Main Street",
"Summersville", "CA", "90034", "USA"
]
],
["tel", {}, "uri", "tel:+1-213-555-1212"],
["email", {}, "text", "j.frax@rackafrax.com"]
]
]
}
}
{
...
"deviceOwner": {
"owner": [
"vcard", [
["version", {}, "text", "4.0"],
["kind", {}, "text", "org"],
["fn", {}, "text", "Racafrax, Inc."]
]
],
"operator": [
"vcard", [
["version", {}, "text", "4.0"],
["fn", {}, "text", "John Frax"],
["adr", {}, "text",
["", "", "100 Main Street",
"Summersville", "CA", "90034", "USA"
]
],
["tel", {}, "uri", "tel:+1-213-555-1212"],
["email", {}, "text", "j.frax@rackafrax.com"]
]
]
}
}
This section describes the use of "HTTP Over TLS" [RFC2818] (HTTPS) as the transfer mechanism for PAWS. TLS provides message integrity and confidentiality between the Master Device and the Database, but only when best current practices are adopted, including use of recommended cipher suites and modes of operation. Consequently, to improve PAWS security and interoperability, implementations of the Database and Master Device MUST follow best current practices defined by "Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)" [RFC7525].
本节介绍使用“HTTP Over TLS”[RFC2818]（HTTPS）作为PAWS的传输机制。TLS在主设备和数据库之间提供消息完整性和机密性，但仅当采用最佳的当前实践时，包括使用推荐的密码套件和操作模式。因此，为了提高PAWS的安全性和互操作性，数据库和主设备的实现必须遵循“传输层安全性（TLS）和数据报传输层安全性（DTLS）的安全使用建议”[RFC7525]中定义的当前最佳实践。
Depending on a prior relationship between a Database and device, the server MAY require client authentication, as described in the "Transport Layer Security (TLS) Protocol" [RFC5246], to authenticate
根据数据库和设备之间的先前关系，服务器可能需要客户端身份验证，如“传输层安全（TLS）协议”[RFC5246]中所述，以进行身份验证
the device. When client authentication is required, the Database MUST specify, by prior arrangement, acceptable root Certification Authorities (CAs) to serve as trust anchors for device certificates.
这个装置。当需要客户端身份验证时，数据库必须通过事先安排指定可接受的根证书颁发机构（CA）作为设备证书的信任锚。
To enable Databases to handle large numbers of requests from large numbers of devices, the Database MAY support and devices SHOULD support "Stateless TLS Session Resumption" [RFC5077].
为了使数据库能够处理来自大量设备的大量请求，数据库可以支持并且设备应该支持“无状态TLS会话恢复”[RFC5077]。
A PAWS request message is carried in the body of an HTTP POST request. A PAWS response message is carried in the body of an HTTP response. A PAWS response SHOULD include a Content-Length header.
在HTTP POST请求的主体中携带PAWS请求消息。PAWS响应消息包含在HTTP响应的主体中。PAWS响应应包括内容长度标题。
The POST method is the only method REQUIRED for PAWS. If a Database chooses to support GET, it MUST be an escaped URI, but the encoding of the URI is outside the scope of this document. The Database MAY refuse to support the GET request by returning an HTTP error code, such as 405 (method not allowed).
POST方法是PAWS所需的唯一方法。如果数据库选择支持GET，则它必须是转义URI，但URI的编码不在本文档的范围内。数据库可能会通过返回HTTP错误代码来拒绝支持GET请求，例如405（不允许使用方法）。
The Database MAY redirect a PAWS request by returning a HTTP 3xx response (as defined by Section 6.4 of "HTTP/1.1: Semantics and Content" [RFC7231]). The Database MUST provide the redirect URI in the Location header of the 3xx response, and the device MUST handle redirects by using the Location header provided by the Database. When redirecting, the device MUST observe the delay indicated by the Retry-After header. The device MUST authenticate the Database that returns the redirect response before following the redirect. Also, the device MUST authenticate the Database indicated in the redirect. Since the device may communicate with a Database (which it authenticated) without user interaction, when the response code is 301 (Moved Permanently), the device MAY redirect without asking a user for confirmation, even thought it is in response to an HTTP POST method.
数据库可以通过返回HTTP 3xx响应（如“HTTP/1.1：语义和内容”[RFC7231]第6.4节所定义）来重定向PAWS请求。数据库必须在3xx响应的位置头中提供重定向URI，设备必须使用数据库提供的位置头处理重定向。重定向时，设备必须遵守Retry After标头指示的延迟。在执行重定向之前，设备必须对返回重定向响应的数据库进行身份验证。此外，设备必须对重定向中指示的数据库进行身份验证。由于设备可以在没有用户交互的情况下与数据库（其已认证）通信，因此当响应代码为301（永久移动）时，设备可以重定向，而无需请求用户确认，即使它是在响应HTTP POST方法。
The Database SHOULD use HTTP status code "307 Temporary Redirect" to indicate that the device SHOULD resubmit the same request to an alternate URI. The device MAY revert to the original URI for the very next request, or it MAY continue to use the alternate URI for a period of time, e.g.,:
数据库应使用HTTP状态代码“307临时重定向”来指示设备应向备用URI重新提交相同的请求。设备可能会在下一个请求中恢复为原始URI，或者可能会在一段时间内继续使用备用URI，例如：
o For the remainder of its session, or
o 在本届会议剩余时间内，或
o For a fixed period of time, or
o 在一段固定的时间内，或
o Until power cycled, or
o 直到电源循环，或
o Until it receives another redirect
o 直到它收到另一个重定向
However, the device does not need to modify its stored list of URIs.
但是，设备不需要修改其存储的URI列表。
For a minimum of two weeks before the URI of the Database changes permanently, it MUST use the database-change (DbUpdateSpec (Section 5.7)) mechanism to notify devices, as described in "Configuration Update: Database URI Changes" (Section 4.1.2). After the Database has moved, requests to the original URI MAY return HTTP status code 301 (Moved Permanently) to indicate that the device SHOULD resubmit the request, and all future requests, to the indicated alternate URI.
如“配置更新：数据库URI更改”（第4.1.2节）所述，在数据库URI永久更改前至少两周，必须使用数据库更改（DbUpdateSpec（第5.7节））机制通知设备。在数据库已经移动之后，对原始URI的请求可以返回HTTP状态代码301（永久移动），以指示设备应该向指示的备用URI重新提交请求以及所有未来的请求。
This section describes procedures for extending PAWS. No extensions should be made that would return sensitive device-specific information in database responses.
本节介绍伸出棘爪的步骤。不应进行会在数据库响应中返回敏感设备特定信息的扩展。
A ruleset represents a set of device-side requirements for which the device has been certified. It typically corresponds to, but is not limited to, a set of rules that govern a specific set of radio spectrum for a regulatory domain.
规则集表示设备已认证的一组设备端要求。它通常对应于但不限于一组规则，这些规则管理监管领域的特定无线电频谱集。
Ruleset identifiers are defined and registered in the Ruleset ID Registry following the procedure in Section 9.1. Ruleset ID values MUST conform to the ruleset-id ABNF. If the Ruleset ID requires additional parameters, they are registered in the PAWS Parameters Registry, as described by Section 9.2. The ABNF syntax [RFC5234] is as follows.
按照第9.1节中的程序，在规则集ID注册表中定义并注册规则集标识符。规则集ID值必须符合规则集ID ABNF。如第9.2节所述，如果规则集ID需要额外的参数，它们将在PAWS参数注册表中注册。ABNF语法[RFC5234]如下所示。
ruleset-id = 1*64ruleset-char
ruleset-char = ALPHA / DIGIT / "_" / "."
ruleset-id = 1*64ruleset-char
ruleset-char = ALPHA / DIGIT / "_" / "."
When defining a Ruleset ID:
定义规则集ID时：
o It can be useful for the identifier to be descriptive of the set of rules that allow a device to operate within one or more regulatory domains. For example, it might include the name of a regulatory body or a certification process.
o 标识符描述允许设备在一个或多个监管域内操作的规则集是有用的。例如，它可能包括监管机构或认证流程的名称。
o The identifier SHOULD include some sort of version information, such as a year and/or version number.
o 标识符应包括某种版本信息，如年份和/或版本号。
o The maximum length of the identifier is 64 octets.
o 标识符的最大长度为64个八位字节。
New request or response parameters for use with PAWS are defined and registered in the parameters registry following the procedure in Section 9.2.
按照第9.2节中的程序，在参数注册表中定义并注册用于PAWS的新请求或响应参数。
Parameter names MUST conform to the param-name ABNF, and parameter values syntax MUST be well-defined (e.g., using ABNF or a reference to the syntax of an existing parameter).
参数名称必须符合参数名称ABNF，参数值语法必须定义良好（例如，使用ABNF或引用现有参数的语法）。
param-name = 1*64name-char
name-char = ALPHA / DIGIT / "_"
param-name = 1*64name-char
name-char = ALPHA / DIGIT / "_"
Parameter names use lowerCamelCase by convention. The maximum length of a name is 64 octets.
参数名称按约定使用小写字母。名称的最大长度为64个八位字节。
Unregistered vendor-specific parameter extensions that are not commonly applicable and are specific to the implementation details of the Database where they are used SHOULD use a vendor-specific prefix that is not likely to conflict with other registered values (e.g., begin with 'companyname').
未注册的特定于供应商的参数扩展通常不适用，并且特定于使用它们的数据库的实现细节，应使用不可能与其他注册值冲突的特定于供应商的前缀（例如，以“companyname”开头）。
Additional error codes can be registered to extend the set listed in Section 5.17, following the procedures in Section 9.3. If the error code requires additional response parameters, they are registered in the PAWS Parameters Registry, as described by Section 9.2.
按照第9.3节中的程序，可以注册其他错误代码以扩展第5.17节中列出的集合。如果错误代码需要额外的响应参数，它们将在PAWS参数注册表中注册，如第9.2节所述。
By convention, the error code is a negative integer value, using one of the range of values defined in Error Codes (Section 5.17). If an appropriate category does not exist, a value from a different range may be used.
按照惯例，错误代码是一个负整数值，使用错误代码中定义的值范围之一（第5.17节）。如果不存在适当的类别，则可以使用不同范围的值。
There are three registries associated with PAWS:
有三个与PAWS相关的注册表：
o PAWS Ruleset ID Registry (Section 9.1)
o PAWS规则集ID注册表（第9.1节）
o PAWS Parameter Registry (Section 9.2)
o PAWS参数注册表（第9.2节）
o PAWS Error Code Registry (Section 9.3)
o PAWS错误代码注册表（第9.3节）
All registries use the Specification Required policy [RFC5226], with a Designated Expert appointed by the IESG. Specific criteria that the Designated Expert should use in assessing registrations are given below in the description of each registry. The Designated Expert
所有注册机构均使用规范要求的政策[RFC5226]，并由IESG指定一名专家。指定专家在评估登记时应使用的具体标准见下文各登记处的说明。指定专家
should take advice from the community through the paws@ietf.org mailing list, and the registrant is encouraged to post to the mailing list before formally requesting the registration from IANA. The intention is that new registrations will be accompanied by a published specification. But in order to allow for the allocation of values prior to publication of the specification, the Designated Expert can approve allocations once it seems clear that the specification will be published. Upon approval, IANA will post the registrations that are not intended to be published in an RFC.
应通过paws@ietf.org邮件列表，并鼓励注册人在正式向IANA申请注册之前将邮件发送至邮件列表。其目的是，新注册将附带一份已发布的规范。但为了允许在规范发布之前分配值，一旦明确规范将发布，指定专家可以批准分配。经批准后，IANA将发布不打算在RFC中发布的注册。
This specification establishes the "PAWS Ruleset ID Registry".
本规范建立了“PAWS规则集ID注册表”。
Ruleset type names for inclusion in PAWS messages are registered on the advice of one or more Designated Experts, with Specification Required [RFC5226]. The specification must include a reference to the regulatory domain to which it applies. To increase interoperability, it is more desirable to have fewer rulesets than to have many rulesets with small variations. Consequently, the Designated Expert should avoid duplication and should encourage the registrant to look for alternatives if there are only small variations from an existing ruleset. The Designated Expert should ensure that the proposed registration is complete with respect to its associated regulatory domain and may seek an expert familiar with those rules to participate in the review on the paws@ietf.org mailing list.
PAWS消息中包含的规则集类型名称是根据一名或多名指定专家的建议注册的，需要规范[RFC5226]。规范必须包括对其适用的监管领域的引用。为了提高互操作性，需要的规则集更少，而不是有许多小变化的规则集。因此，指定专家应避免重复，并应鼓励注册人在现有规则集仅有微小变化的情况下寻找替代方案。指定专家应确保拟议的注册在其相关监管领域内完成，并可寻求熟悉这些规则的专家参与审查paws@ietf.org邮件列表。
The PAWS Ruleset ID Registry includes the following: 'Ruleset Identifier', 'Reference', and 'Template'. The Template column will include links to the registration templates, either posted by IANA or linked to the relevant sections of RFCs.
PAWS规则集ID注册表包括以下内容：“规则集标识符”、“引用”和“模板”。模板栏将包括注册模板的链接，由IANA发布或链接到RFC的相关章节。
Ruleset identifier: The name of the ruleset. See Section 8.1 of RFC 7545 for the format requirements of this identifier.
规则集标识符：规则集的名称。该标识符的格式要求见RFC 7545第8.1节。
Specification document(s): Reference to the document that specifies the parameter, preferably including a URI that can be used to retrieve a copy of the document. An indication of the relevant sections also may be included but is not required.
规范文档：对指定参数的文档的引用，最好包括可用于检索文档副本的URI。相关章节的指示也可能包括在内，但不是必需的。
Additional Parameter Requirements: Listing of additional parameter requirements to associate with the ruleset. Note that new parameters are registered separately in the PAWS Parameters Registry, as described by Section 8.2. Two types of additional parameter requirements are:
附加参数要求：列出与规则集关联的附加参数要求。请注意，如第8.2节所述，新参数在PAWS参数注册表中单独注册。两种类型的附加参数要求是：
* Addition of new parameters to existing structures, or modification of the REQUIRED and OPTIONAL requirements for existing parameters.
* 向现有结构添加新参数，或修改现有参数的要求和可选要求。
* Modification of requirements to existing parameter values.
* 修改对现有参数值的要求。
For adding new parameters or modifying requirements of existing parameters, the registration should include a table for each affected structure that lists the structure's parameter changes. Each table should include a structure name in its heading and have the following columns:
对于添加新参数或修改现有参数的要求，注册应包括每个受影响结构的表格，其中列出结构的参数更改。每个表的标题中应包含结构名称，并具有以下列：
Parameter name: Name of the parameter added or modified.
参数名称：添加或修改的参数的名称。
Type: Data type of the parameter value.
类型：参数值的数据类型。
Requirement: Whether the parameter is REQUIRED or OPTIONAL for the ruleset.
要求：该参数对于规则集是必需的还是可选的。
Notes: Any additional notes that might be useful to implementors.
注释：对实现者可能有用的任何附加注释。
For modifying requirements to existing parameter values, the registration should include a table for each affected structure that lists the structure's parameter changes. Each table should include a structure name in its heading and have the following columns:
为了修改对现有参数值的要求，注册应包括每个受影响结构的表格，其中列出结构的参数更改。每个表的标题中应包含结构名称，并具有以下列：
Parameter name: Name of the parameter.
参数名称：参数的名称。
Type: Data type of the parameter value.
类型：参数值的数据类型。
Additional requirements: Additional requirements on the parameter value.
附加要求：对参数值的附加要求。
IANA will post each registration template that is not intended to be published in an RFC.
IANA将发布每个不打算在RFC中发布的注册模板。
Note that the Additional Parameter Requirements section can be quite extensive, so it will not appear directly in the IANA Ruleset ID Registry table. The table, however, will contain a link to the full registration template for easy access to the additional requirements.
请注意，附加参数要求部分可能非常广泛，因此它不会直接出现在IANA规则集ID注册表表中。但是，该表将包含一个指向完整注册模板的链接，以便轻松访问附加要求。
The PAWS Ruleset ID Registry enables protocol extensibility to support any regulatory domain and ruleset. The initial contents of the registry, however, include only FCC-specific and ETSI-specific entries, because, as of this writing, they are the only regulatory domains that have finalized rules. There is no intent to restrict the protocol to any particular set of authorities.
PAWS规则集ID注册表支持协议扩展性，以支持任何监管域和规则集。然而，注册表的初始内容仅包括FCC特定和ETSI特定的条目，因为在撰写本文时，它们是唯一具有最终规则的监管领域。我们无意将该协议限制在任何特定的权限范围内。
The initial contents of the PAWS Ruleset ID Registry are listed below; each section corresponds to a single entry in the registry.
PAWS规则集ID注册表的初始内容如下所示；每个部分对应于注册表中的单个条目。
For the additional parameters that start with the "fcc" prefix, see PAWS Parameters Registry Initial Contents (Section 9.2.2) for more information.
有关以“fcc”前缀开头的其他参数，请参阅PAWS参数注册表初始内容（第9.2.2节）以了解更多信息。
Ruleset identifier: FccTvBandWhiteSpace-2010
规则集标识符：FccTvBandWhiteSpace-2010
Specification document(s): This ruleset refers to the FCC rules for TV-band white-space operations established in the Code of Federal Regulations (CFR), Title 47, Part 15, Subpart H [FCC-CFR47-15H].
规范文件：本规则集指《联邦法规》（CFR）第47篇第15部分H子部分[FCC-CFR47-15H]中制定的FCC电视频段空白操作规则。
Additional Parameter Requirements
附加参数要求
Each of the following tables defines additional parameters for the indicated PAWS message. Note that the Requirement column lists FCC, not PAWS, requirements/optionality rules.
下表分别定义了所示PAWS消息的附加参数。请注意，“要求”列列出了FCC（而非PAW）要求/可选性规则。
The FCC requires registration of "Fixed Devices". Additionally, deviceOwner is required in the registration request:
FCC要求注册“固定设备”。此外，注册请求中还需要deviceOwner：
Registration Request (Section 4.4.1)
注册申请（第4.4.1节）
+-------------+-------------------+-------------+-------------------+
| Parameter | Type | Requirement | Notes |
| Name | | | |
+-------------+-------------------+-------------+-------------------+
| deviceOwner | DeviceOwner | REQUIRED | For registering |
| | (Section 5.5) | | Fixed Devices |
+-------------+-------------------+-------------+-------------------+
+-------------+-------------------+-------------+-------------------+
| Parameter | Type | Requirement | Notes |
| Name | | | |
+-------------+-------------------+-------------+-------------------+
| deviceOwner | DeviceOwner | REQUIRED | For registering |
| | (Section 5.5) | | Fixed Devices |
+-------------+-------------------+-------------+-------------------+
Available Spectrum Request (Section 4.5.1)
可用频谱请求（第4.5.1节）
+---------------+-----------------------------+-------------+-------+
| Parameter | Type | Requirement | Notes |
| Name | | | |
+---------------+-----------------------------+-------------+-------+
| deviceDesc | DeviceDescriptor (Section | REQUIRED | |
| | 5.2) | | |
+---------------+-----------------------------+-------------+-------+
+---------------+-----------------------------+-------------+-------+
| Parameter | Type | Requirement | Notes |
| Name | | | |
+---------------+-----------------------------+-------------+-------+
| deviceDesc | DeviceDescriptor (Section | REQUIRED | |
| | 5.2) | | |
+---------------+-----------------------------+-------------+-------+
Available Spectrum Batch Request (Section 4.5.3)
可用频谱批次请求（第4.5.3节）
+---------------+-----------------------------+-------------+-------+
| Parameter | Type | Requirement | Notes |
| Name | | | |
+---------------+-----------------------------+-------------+-------+
| deviceDesc | DeviceDescriptor (Section | REQUIRED | |
| | 5.2) | | |
+---------------+-----------------------------+-------------+-------+
+---------------+-----------------------------+-------------+-------+
| Parameter | Type | Requirement | Notes |
| Name | | | |
+---------------+-----------------------------+-------------+-------+
| deviceDesc | DeviceDescriptor (Section | REQUIRED | |
| | 5.2) | | |
+---------------+-----------------------------+-------------+-------+
DeviceDescriptor (Section 5.2)
设备描述器（第5.2节）
+-------------------+--------+-------------+------------------------+
| Parameter Name | Type | Requirement | Notes |
+-------------------+--------+-------------+------------------------+
| serialNumber | string | REQUIRED | Specifies a device's |
| | | | serial number. See |
| | | | Section 5.2. |
| fccId | string | REQUIRED | Specifies a device's |
| | | | FCC certification ID |
| | | | (Section 9.2.2.1). |
| fccTvbdDeviceType | string | REQUIRED | Specifies the FCC |
| | | | Device Type (Section |
| | | | 9.2.2.2) of TV-band |
| | | | white-space device, as |
| | | | defined by the FCC |
| | | | rules. |
+-------------------+--------+-------------+------------------------+
+-------------------+--------+-------------+------------------------+
| Parameter Name | Type | Requirement | Notes |
+-------------------+--------+-------------+------------------------+
| serialNumber | string | REQUIRED | Specifies a device's |
| | | | serial number. See |
| | | | Section 5.2. |
| fccId | string | REQUIRED | Specifies a device's |
| | | | FCC certification ID |
| | | | (Section 9.2.2.1). |
| fccTvbdDeviceType | string | REQUIRED | Specifies the FCC |
| | | | Device Type (Section |
| | | | 9.2.2.2) of TV-band |
| | | | white-space device, as |
| | | | defined by the FCC |
| | | | rules. |
+-------------------+--------+-------------+------------------------+
The following table lists additional requirements for DeviceOwner (Section 5.5) parameter values.
下表列出了设备所有者（第5.5节）参数值的附加要求。
DeviceOwner (Section 5.5)
设备所有者（第5.5节）
+-----------+-------+-----------------------------------------------+
| Parameter | Type | Additional Requirement |
| Name | | |
+-----------+-------+-----------------------------------------------+
| owner | vCard | The owner is required to contain the |
| | | formatted name of an individual or |
| | | organization using the "fn" property. When |
| | | the name is that of an organization, the |
| | | entry also is required to contain the "kind" |
| | | property, with a value of "org". |
| operator | vCard | The operator entry is required to contain the |
| | | following properties for the contact person |
| | | responsible for the device's operation: "fn", |
| | | "adr", "tel", and "email". |
+-----------+-------+-----------------------------------------------+
+-----------+-------+-----------------------------------------------+
| Parameter | Type | Additional Requirement |
| Name | | |
+-----------+-------+-----------------------------------------------+
| owner | vCard | The owner is required to contain the |
| | | formatted name of an individual or |
| | | organization using the "fn" property. When |
| | | the name is that of an organization, the |
| | | entry also is required to contain the "kind" |
| | | property, with a value of "org". |
| operator | vCard | The operator entry is required to contain the |
| | | following properties for the contact person |
| | | responsible for the device's operation: "fn", |
| | | "adr", "tel", and "email". |
+-----------+-------+-----------------------------------------------+
For the additional parameters that start with the "etsi" prefix, see PAWS Parameters Registry Initial Contents (Section 9.2.2) for more information.
有关以“etsi”前缀开头的其他参数，请参阅PAWS参数注册表初始内容（第9.2.2节）了解更多信息。
Ruleset identifier: ETSI-EN-301-598-1.1.1
规则集标识符：ETSI-EN-301-598-1.1.1
Specification document(s): This ruleset refers to the ETSI Harmonised Standard [ETSI-EN-301-598] established by ETSI.
规范文件：本规则集指ETSI制定的ETSI协调标准[ETSI-EN-301-598]。
Additional Parameter Requirements
附加参数要求
Each of the following tables defines additional parameters for the indicated PAWS message. Note that the Requirement column lists ETSI, not PAWS, requirements/optionality rules.
下表分别定义了所示PAWS消息的附加参数。请注意，“需求”列列出了ETSI，而不是PAWS、需求/可选性规则。
+-------------------------------------------------------------------+
| Parameter Name |
| Type |
| Requirement |
| Notes |
+-------------------------------------------------------------------+
| serialNumber |
| string |
| REQUIRED |
| Specifies a device's serial number (Section 5.2). |
| |
| manufacturerId |
| string |
| REQUIRED |
| Specifies a device's manufacturer's identifier |
| (Section 5.2). |
| |
| modelId |
| string |
| REQUIRED |
| Specifies a device's model identifier (Section 5.2). |
| |
| etsiEnDeviceType |
| string |
| REQUIRED |
| Specifies the device's ETSI device type (Section 9.2.2.3). |
| |
| etsiEnDeviceEmissionsClass |
| string |
| REQUIRED |
| Specifies the device's ETSI device emissions class |
| (Section 9.2.2.4). |
| |
| etsiEnTechnologyId |
| string |
| REQUIRED |
| Specifies the device's ETSI technology ID (Section 9.2.2.5). |
| |
| etsiEnDeviceCategory |
| string |
| REQUIRED |
| Specifies the device's ETSI device category (Section 9.2.2.6). |
+-------------------------------------------------------------------+
+-------------------------------------------------------------------+
| Parameter Name |
| Type |
| Requirement |
| Notes |
+-------------------------------------------------------------------+
| serialNumber |
| string |
| REQUIRED |
| Specifies a device's serial number (Section 5.2). |
| |
| manufacturerId |
| string |
| REQUIRED |
| Specifies a device's manufacturer's identifier |
| (Section 5.2). |
| |
| modelId |
| string |
| REQUIRED |
| Specifies a device's model identifier (Section 5.2). |
| |
| etsiEnDeviceType |
| string |
| REQUIRED |
| Specifies the device's ETSI device type (Section 9.2.2.3). |
| |
| etsiEnDeviceEmissionsClass |
| string |
| REQUIRED |
| Specifies the device's ETSI device emissions class |
| (Section 9.2.2.4). |
| |
| etsiEnTechnologyId |
| string |
| REQUIRED |
| Specifies the device's ETSI technology ID (Section 9.2.2.5). |
| |
| etsiEnDeviceCategory |
| string |
| REQUIRED |
| Specifies the device's ETSI device category (Section 9.2.2.6). |
+-------------------------------------------------------------------+
AVAIL_SPECTRUM_REQ (Section 4.5.1)
可用频谱要求（第4.5.1节）
+-------------+--------+-------------+------------------------------+
| Parameter | Type | Requirement | Notes |
| Name | | | |
+-------------+--------+-------------+------------------------------+
| requestType | string | OPTIONAL | Modifies the available- |
| | | | spectrum request type. If |
| | | | specified, the only valid |
| | | | value is, "Generic Slave", |
| | | | and the Database is required |
| | | | to respond with generic |
| | | | operating parameters for any |
| | | | Slave Device. |
+-------------+--------+-------------+------------------------------+
+-------------+--------+-------------+------------------------------+
| Parameter | Type | Requirement | Notes |
| Name | | | |
+-------------+--------+-------------+------------------------------+
| requestType | string | OPTIONAL | Modifies the available- |
| | | | spectrum request type. If |
| | | | specified, the only valid |
| | | | value is, "Generic Slave", |
| | | | and the Database is required |
| | | | to respond with generic |
| | | | operating parameters for any |
| | | | Slave Device. |
+-------------+--------+-------------+------------------------------+
Available Spectrum Batch Request (Section 4.5.3)
可用频谱批次请求（第4.5.3节）
+-------------+--------+-------------+------------------------------+
| Parameter | Type | Requirement | Notes |
| Name | | | |
+-------------+--------+-------------+------------------------------+
| requestType | string | OPTIONAL | Modifies the available- |
| | | | spectrum request type. If |
| | | | specified, the only valid |
| | | | value is, "Generic Slave", |
| | | | and the Database is required |
| | | | to respond with generic |
| | | | operating parameters for any |
| | | | Slave Device. |
+-------------+--------+-------------+------------------------------+
+-------------+--------+-------------+------------------------------+
| Parameter | Type | Requirement | Notes |
| Name | | | |
+-------------+--------+-------------+------------------------------+
| requestType | string | OPTIONAL | Modifies the available- |
| | | | spectrum request type. If |
| | | | specified, the only valid |
| | | | value is, "Generic Slave", |
| | | | and the Database is required |
| | | | to respond with generic |
| | | | operating parameters for any |
| | | | Slave Device. |
+-------------+--------+-------------+------------------------------+
The following tables define additional requirements for the DeviceDescriptor (Section 5.2) and RulesetInfo (Section 5.6) parameters that appear in the AVAIL_SPECTRUM_RESP (Section 4.5.2) and AVAIL_SPECTRUM_BATCH_RESP (Section 4.5.4) messages. Note that this means the Database is modifying the DeviceDescriptor sent by the Master Device to return device-specific restrictions.
下表定义了AVAIL_SPECTRUM_RESP（第4.5.2节）和AVAIL_SPECTRUM_BATCH_RESP（第4.5.4节）消息中出现的DeviceDescriptor（第5.2节）和RulesetInfo（第5.6节）参数的附加要求。注意，这意味着数据库正在修改主设备发送的DeviceDescriptor，以返回特定于设备的限制。
+-------------------------------------------------------------------+
| Parameter Name |
| Type |
| Requirement |
| Notes |
+-------------------------------------------------------------------+
| needsSpectrumReport |
| boolean |
| REQUIRED |
| The Database is required to set this to true to indicate that |
| the device must report spectrum usage. |
| |
| maxTotalBwHz |
| float |
| REQUIRED |
| Specifies a constraint on total allowed bandwidth. |
| |
| maxContiguousBwHz |
| float |
| REQUIRED |
| Specifies a constraint on total allowed contiguous |
| bandwidth. |
| |
| etsiEnSimultaneousChannelOpera |
| string |
| REQUIRED |
| Specifies a constraint on simultaneous channel operation |
| (Section 9.2.2.7). If it is not provided, the default value |
| is "0". |
+-------------------------------------------------------------------+
+-------------------------------------------------------------------+
| Parameter Name |
| Type |
| Requirement |
| Notes |
+-------------------------------------------------------------------+
| needsSpectrumReport |
| boolean |
| REQUIRED |
| The Database is required to set this to true to indicate that |
| the device must report spectrum usage. |
| |
| maxTotalBwHz |
| float |
| REQUIRED |
| Specifies a constraint on total allowed bandwidth. |
| |
| maxContiguousBwHz |
| float |
| REQUIRED |
| Specifies a constraint on total allowed contiguous |
| bandwidth. |
| |
| etsiEnSimultaneousChannelOpera |
| string |
| REQUIRED |
| Specifies a constraint on simultaneous channel operation |
| (Section 9.2.2.7). If it is not provided, the default value |
| is "0". |
+-------------------------------------------------------------------+
RulesetInfo (Section 5.6)
规则集信息（第5.6节）
+-------------------+-------+-------------+-------------------------+
| Parameter Name | Type | Requirement | Notes |
+-------------------+-------+-------------+-------------------------+
| maxLocationChange | float | OPTIONAL | Specifies a constraint |
| | | | on maximum location |
| | | | changes. |
+-------------------+-------+-------------+-------------------------+
+-------------------+-------+-------------+-------------------------+
| Parameter Name | Type | Requirement | Notes |
+-------------------+-------+-------------+-------------------------+
| maxLocationChange | float | OPTIONAL | Specifies a constraint |
| | | | on maximum location |
| | | | changes. |
+-------------------+-------+-------------+-------------------------+
This specification establishes the "PAWS Parameters Registry".
本规范建立了“PAWS参数注册表”。
Additional parameters for inclusion in PAWS requests, responses, or sub-messages are registered on the advice of one or more Designated Experts, with Specification Required [RFC5226].
PAWS请求、响应或子消息中包含的其他参数根据一名或多名指定专家的建议进行注册，需要规范[RFC5226]。
The Designated Expert should avoid duplication, i.e., avoid adding a new parameter when an existing one suffices. When a set of parameters is added in support of a new ruleset (Section 9.1), the parameters should share a common prefix that reflects the ruleset ID. The prefix may be omitted, of course, if a parameter has more general applicability. Similarly, when a parameter is not associated with a ruleset, the Designated Expert should ensure that the parameter name does not have a prefix that is used by existing ruleset parameters (e.g., "fcc", "etsi") or that is the initials of an organization that has not yet registered anything, but reasonably might.
指定专家应避免重复，即在现有参数足够时避免添加新参数。当添加一组参数以支持新规则集（第9.1节）时，这些参数应共享一个反映规则集ID的通用前缀。当然，如果某个参数具有更广泛的适用性，则可以省略该前缀。类似地，当参数与规则集不关联时，指定专家应确保参数名称没有现有规则集参数（例如，“fcc”、“etsi”）使用的前缀，或者是尚未注册任何内容但可能合理注册的组织的首字母缩写。
The PAWS Parameters Registry includes the following: 'Parameter name', 'Parameter usage location', and 'Specification document(s)'.
PAWS参数注册表包括以下内容：“参数名称”、“参数使用位置”和“规范文档”。
Parameter name: The name of the parameter (e.g., "example").
参数名称：参数的名称（例如，“示例”）。
Parameter usage location: The location(s) where the parameter can be used. The possible locations are the named structures defined in "Protocol Functionalities" (Section 4) and "Protocol Parameters" (Section 5).
参数使用位置：可以使用参数的位置。可能的位置是“协议功能”（第4节）和“协议参数”（第5节）中定义的命名结构。
Specification document(s): Reference to the document that specifies the parameter, preferably including a URI that can be used to retrieve a copy of the document. An indication of the relevant sections also may be included, but is not required.
规范文档：对指定参数的文档的引用，最好包括可用于检索文档副本的URI。也可以包括相关章节的指示，但不需要。
The PAWS Parameters Registry enables protocol extensibility to support any regulatory domain and ruleset. The initial contents of the registry, however, include only FCC-specific and ETSI-specific entries, because, as of this writing, they are the only regulatory domains that have established rules. There is no intent to restrict the protocol to any particular set of authorities.
PAWS参数注册表支持协议扩展，以支持任何监管域和规则集。然而，注册表的初始内容仅包括FCC特定和ETSI特定的条目，因为在撰写本文时，它们是唯一具有既定规则的监管领域。我们无意将该协议限制在任何特定的权限范围内。
The initial contents of the PAWS Parameters Registry are listed below; each section corresponds to a row of the registry.
PAWS参数注册表的初始内容如下所示；每个部分对应于注册表的一行。
Parameter name: fccId
参数名称：fccId
Parameter usage location: DeviceDescriptor (Section 5.2)
参数使用位置：DeviceDescriptor（第5.2节）
Specification document(s): This document. Specifies the device's FCC certification identifier. A valid FCC ID is limited to 19 characters in the ASCII value range, as proposed in FCC Administration Topics Review [FCC-Review-2012-10]. For the purposes of the PAWS protocol, the maximum length of the fccId value is 32 octets.
规范文件：本文件。指定设备的FCC证书标识符。根据FCC管理主题审查[FCC-Review-2012-10]中的建议，有效的FCC ID在ASCII值范围内限制为19个字符。就PAWS协议而言，fccId值的最大长度为32个八位字节。
Parameter name: fccTvbdDeviceType
参数名称：fccTvbdDeviceType
Parameter usage location: DeviceDescriptor (Section 5.2)
参数使用位置：DeviceDescriptor（第5.2节）
Specification document(s): This document. Specifies the TV-band white-space device type, as defined by the FCC. Valid values are "FIXED", "MODE_1", and "MODE_2".
规范文件：本文件。指定FCC定义的电视频段空白设备类型。有效值为“固定”、“模式1”和“模式2”。
Parameter name: etsiEnDeviceType
参数名称：etsiEnDeviceType
Parameter usage location: DeviceDescriptor (Section 5.2)
参数使用位置：DeviceDescriptor（第5.2节）
Specification document(s): Specifies the white-space device type, as defined by the ETSI Harmonised Standard [ETSI-EN-301-598]. Valid values are single-letter strings, such as "A", "B", etc. Consult the documentation for details about the device types.
规范文件：规定了ETSI协调标准[ETSI-EN-301-598]定义的空白设备类型。有效值为单字母字符串，如“A”、“B”等。有关设备类型的详细信息，请参阅文档。
Parameter name: etsiEnDeviceEmissionsClass
参数名称：ETSIENDEVICEEMissionClass
Parameter usage location: DeviceDescriptor (Section 5.2)
参数使用位置：DeviceDescriptor（第5.2节）
Specification document(s): Specifies the white-space device emissions class, as defined by the ETSI Harmonised Standard [ETSI-EN-301-598], that characterizes the out-of-block emissions of the device. The values are represented by numeric strings, such as "1", "2", "3", etc. Consult the documentation for details about emissions classes.
规范文件：规定了ETSI协调标准[ETSI-EN-301-598]定义的空白区设备排放等级，该标准描述了设备的块外排放。数值由数字字符串表示，如“1”、“2”、“3”等。有关排放等级的详细信息，请参阅文档。
Parameter name: etsiEnTechnologyId
参数名称：etsiEnTechnologyId
Parameter usage location: DeviceDescriptor (Section 5.2)
参数使用位置：DeviceDescriptor（第5.2节）
Specification document(s): Specifies the white-space device technology identifier, as defined by the ETSI Harmonised Standard [ETSI-EN-301-598]. The maximum length of the string value is 64 octets. Consult the documentation for valid values.
规范文件：规定了ETSI协调标准[ETSI-EN-301-598]定义的空白设备技术标识符。字符串值的最大长度为64个八位字节。有关有效值，请参阅文档。
Parameter name: etsiEnDeviceCategory
参数名称：etsiEnDeviceCategory
Parameter usage location: DeviceDescriptor (Section 5.2)
参数使用位置：DeviceDescriptor（第5.2节）
Specification document(s): Specifies the white-space device category, as defined by the ETSI Harmonised Standard [ETSI-EN-301-598]. Valid values are the strings "master" and "slave". It is case insensitive.
规范文件：规定了ETSI协调标准[ETSI-EN-301-598]定义的空白设备类别。有效值是字符串“master”和“slave”。它不区分大小写。
Parameter name: etsiEnSimultaneousChannelOperationRestriction
Parameter name: etsiEnSimultaneousChannelOperationRestriction
Parameter usage location: SpectrumSpec (Section 5.9)
参数使用位置：SpectrumSpec（第5.9节）
Specification document(s): Specifies the constraint on the device maximum total EIRP, as defined by the ETSI Harmonised Standard [ETSI-EN-301-598]. The values are represented by numeric strings, such as "0", "1", etc. Consult the documentation for the specification of the power constraint corresponding to each parameter value.
规范文件：根据ETSI协调标准[ETSI-EN-301-598]的定义，规定了设备最大总EIRP的约束条件。这些值由数字字符串表示，如“0”、“1”等。有关每个参数值对应的功率约束规范，请参阅文档。
This specification establishes the "PAWS Error Code Registry".
本规范建立了“PAWS错误代码注册表”。
Additional error codes for inclusion in PAWS error messages are registered on the advice of one or more Designated Experts, with Specification Required [RFC5226].
根据一名或多名指定专家的建议，登记PAWS错误信息中包含的其他错误代码，并要求规范[RFC5226]。
Error codes are intended to be used for automated error handling by devices. Before approval, the Designated Expert should consider whether a device would handle the new error code differently from an
错误代码用于设备的自动错误处理。在批准之前，指定的专家应该考虑一个设备是否会不同于一个新的错误代码。
existing error code, or whether the difference could be communicated effectively to the end-user via the "reason" parameter of the Error (Section 5.17) object.
现有错误代码，或差异是否可以通过错误（第5.17节）对象的“原因”参数有效传达给最终用户。
The PAWS Error Code Registry includes the following: 'Code', 'Name', 'Description and Additional Parameters', and 'Specification Document(s)'.
PAWS错误代码注册表包括以下内容：“代码”、“名称”、“说明和附加参数”以及“规范文档”。
Code: Integer value of the error code. The value MUST be an unassigned value in the range -32768 to 32767, inclusive.
代码：错误代码的整数值。该值必须是-32768到32767（含）范围内的未赋值值。
Name: Name of the error.
Name：错误的名称。
Description and Additional Parameters: Description of the error and its associated parameters, if any. It also lists additional parameters that are returned in the data portion of the error (see Section 5.17). New parameters MUST be registered separately in the PAWS Parameters Registry, as described by Section 9.2.
描述和附加参数：错误及其相关参数（如果有）的描述。它还列出了错误数据部分返回的其他参数（见第5.17节）。如第9.2节所述，新参数必须在PAWS参数注册表中单独注册。
Initial registry contents are defined in the Error Codes Table (Table 1).
初始注册表内容在错误代码表（表1）中定义。
The registry will also include the error-code categories describing -100s, -200s, and -300s as a note (see "Error Codes" (Section 5.17)).
注册表还将包括描述-100s、-200s和-300s的错误代码类别作为注释（参见“错误代码”（第5.17节））。
PAWS is a protocol whereby a Master Device requests a schedule of available spectrum at its location (or location of its Slave Devices) before it (they) can operate using those frequencies. Whereas the information provided by the Database must be accurate and conform to the applicable ruleset, the Database cannot enforce, through the protocol, that a client device uses only the spectrum it provided. In other words, devices can put energy in the air and cause interference without asking the Database. Hence, PAWS security considerations do not include protection against malicious use of the white-space spectrum. For more detailed information on specific requirements and security considerations associated with PAWS, see "Protocol to Access White-Space (PAWS) Databases: Use Cases and Requirements" [RFC6953].
PAWS是一种协议，其中主设备在其位置（或其从属设备的位置）可以使用这些频率操作之前，请求其可用频谱的时间表。尽管数据库提供的信息必须准确且符合适用的规则集，但数据库不能通过协议强制客户设备仅使用其提供的频谱。换句话说，设备可以在不询问数据库的情况下向空气中注入能量并造成干扰。因此，PAWS的安全考虑不包括防止恶意使用空白频谱。有关与PAWS相关的特定要求和安全注意事项的更多详细信息，请参阅“访问空白（PAWS）数据库的协议：用例和要求”[RFC6953]。
By using PAWS, the Master Device and the Database expose themselves to the following risks:
通过使用PAW，主设备和数据库将面临以下风险：
o Accuracy: The Master Device receives incorrect spectrum-availability information.
o 准确性：主设备接收到不正确的频谱可用性信息。
o Privacy:
o 隐私：
* An unauthorized entity intercepts identifying data for the Master Device or its Slave Devices, such as serial number and location.
* 未经授权的实体拦截主设备或其从属设备的标识数据，如序列号和位置。
* Where Databases are required to take device registrations and/ or maintain request logs, there could be unauthorized access to such information.
* 如果需要数据库进行设备注册和/或维护请求日志，则可能会对此类信息进行未经授权的访问。
Protection from these risks depends on the success of the following steps:
防范这些风险取决于以下步骤的成功：
1. The Master Device must determine the address of a proper Database.
1. 主设备必须确定正确数据库的地址。
2. The Master Device must connect to the proper Database.
2. 主设备必须连接到正确的数据库。
3. The Database must determine or compute accurate spectrum-availability information.
3. 数据库必须确定或计算准确的频谱可用性信息。
4. PAWS messages must be transmitted unmodified between the Database and the Master Device.
4. PAWS消息必须在数据库和主设备之间不经修改地传输。
5. PAWS messages must be encrypted between the Database and the Master Device to prevent exposing private information.
5. PAWS消息必须在数据库和主设备之间进行加密，以防止泄露私人信息。
6. For a Slave Device, the spectrum-availability information also must be transmitted unmodified and securely between the Master Device and the Slave Device.
6. 对于从设备，频谱可用性信息也必须在主设备和从设备之间不经修改且安全地传输。
7. When a Listing Server is required, any attack that would prevent reaching a Listing Server would result in all devices relying on that Listing Server ceasing their use of any white space.
7. 当需要登录服务器时，任何阻止登录服务器的攻击都会导致依赖该登录服务器的所有设备停止使用任何空白。
8. No future extensions to PAWS can allow the return of sensitive information, such as device information or logs.
8. PAWS的未来扩展不允许返回敏感信息，如设备信息或日志。
9. The Database must not allow unauthorized access to device information and request logs and should publish and implement privacy policies regarding their use.
9. 数据库不得允许未经授权访问设备信息和请求日志，并应发布和实施有关其使用的隐私政策。
Of these, only steps 1, 2, 4, 5, and 8 are within the scope of this document. This document addresses step 1 by allowing static provisioning of one or more trusted Databases; dynamic provisioning is out of scope. Step 3 is dependent on specific database implementations and rulesets and is outside the scope of this document. Step 6 requires a protocol between master and slave devices and is thus outside the scope of this document.
其中，只有步骤1、2、4、5和8在本文档的范围内。本文档通过允许静态设置一个或多个受信任的数据库来解决步骤1；动态资源调配超出范围。步骤3取决于特定的数据库实现和规则集，不在本文档的范围之内。步骤6需要主设备和从设备之间的协议，因此不在本文档的范围内。
Use of "HTTP Over TLS" [RFC2818], assuming the PKI used is not compromised, ensures steps 2, 4, and 5, as detailed in the following sections:
使用“HTTP Over TLS”[RFC2818]，假设所使用的PKI不受损害，可确保执行步骤2、4和5，详情见以下章节：
o "Assurance of Proper Database" (Section 10.1)
o “适当数据库的保证”（第10.1节）
o "Protection against Modification" (Section 10.2)
o “防修改保护”（第10.2节）
o "Protection against Eavesdropping" (Section 10.3)
o “防止窃听”（第10.3节）
Any specification for an alternate transport MUST define mechanisms that ensure each of these steps.
备用传输的任何规范都必须定义确保每个步骤的机制。
In addition to the privacy risks described above, information provided in DeviceDescriptor (Section 5.2) and DeviceOwner (Section 5.5), along with device location, may allow a database administrator to track the activity and location of a device and its user over time. Risks of secondary use of such tracking information, including sharing with third parties, require out-of-band mitigation, such as public statements or contractual terms. Furthermore, while it is understandable that regulators require DeviceOwner information for higher-power fixed white-space devices, for privacy concerns, regulators should not require DeviceOwner information for mobile devices. Similarly, regulators should require, and implementations should provide, device location at a level of granularity only as precise as necessary to support accurate database responses.
除上述隐私风险外，DeviceDescriptor（第5.2节）和DeviceOwner（第5.5节）中提供的信息以及设备位置可能允许数据库管理员随时间跟踪设备及其用户的活动和位置。二次使用此类跟踪信息（包括与第三方共享）的风险需要带外缓解，如公开声明或合同条款。此外，尽管监管机构要求高功率固定空白设备的设备所有者信息是可以理解的，但出于隐私考虑，监管机构不应要求移动设备的设备所有者信息。类似地，监管者应该要求并且实现应该提供粒度级别上的设备位置，其精确程度仅为支持准确的数据库响应所需。
This document assumes that the Database is contacted using a domain name or an IP address. Using HTTP over TLS, the Database authenticates its identity, either as a domain name or IP address, to the Master Device by presenting a certificate containing that identifier as a "subjectAltName" (i.e., as a dNSName or IP address). If the Master Device has external information as to the expected identity or credentials of the proper Database (e.g., a certificate fingerprint), checks of the subjectAltName MAY be omitted. Note that in order for the presented certificate to be valid at the client, the client must be able to validate the certificate. In particular, the validation path of the certificate must end in one of the client's
本文档假定使用域名或IP地址联系数据库。使用TLS上的HTTP，数据库通过将包含该标识符的证书作为“subjectAltName”（即，作为dNSName或IP地址）提供给主设备，从而向主设备验证其身份（作为域名或IP地址）。如果主设备具有关于适当数据库的预期身份或凭证（例如，证书指纹）的外部信息，则可以省略对subjectAltName的检查。请注意，为了使提供的证书在客户端有效，客户端必须能够验证证书。特别是，证书的验证路径必须以客户端的
trust anchors, even if that trust anchor is the Database's certificate. A Master Device should allow for the fact that a Database can change its Certification Authorities (CAs) over time.
信任锚，即使该信任锚是数据库的证书。主设备应允许数据库可以随时间更改其证书颁发机构（CA）。
To prevent a PAWS response message from being modified en route, messages must be transmitted over an integrity-protected channel. Using HTTP over TLS, the channel will be protected by appropriate cipher suites.
为了防止PAWS响应消息在途中被修改，必须通过完整性保护通道传输消息。使用HTTP over TLS，通道将受到适当密码套件的保护。
Using HTTP over TLS, messages protected by appropriate cipher suites are also protected from eavesdropping or otherwise unrestricted reading by unauthorized parties en route.
通过使用HTTP over TLS，受适当密码套件保护的消息也可以防止未经授权方在路由过程中窃听或以其他方式不受限制地读取。
Although the Database can inform a device of available spectrum it can use, the Database cannot enforce that the Master Device uses only (or any of) those frequencies. Indeed, a malicious device can operate without ever contacting a Database. Note also that, whereas a malicious device may send fraudulent SPECTRUM_USE_NOTIFY (Section 4.5.5) messages, in the regulatory domains that have established rules, such notifications do not change the available-spectrum answers, so no harm can result from such messages. Consequently, client authentication is not required for the core PAWS (although it may be required by specific regulatory domains).
尽管数据库可以通知设备它可以使用的可用频谱，但数据库不能强制主设备仅使用（或任何）这些频率。实际上，恶意设备可以在不接触数据库的情况下运行。还要注意的是，尽管恶意设备可能发送欺诈性频谱使用通知（第4.5.5节）消息，但在已制定规则的监管域中，此类通知不会改变可用频谱应答，因此此类消息不会造成伤害。因此，核心PAW不需要客户端身份验证（尽管特定的监管领域可能需要客户端身份验证）。
Depending on a prior relationship between a Database and Master Device, the Database MAY require client authentication. TLS provides client authentication, but there are some considerations:
根据数据库和主设备之间的先前关系，数据库可能需要客户端身份验证。TLS提供客户端身份验证，但有一些注意事项：
o The Database must nominate acceptable CAs, and the Master Device must have a certificate rooted at one of those CAs.
o 数据库必须指定可接受的CA，并且主设备必须具有以这些CA之一为根的证书。
o As indicated in Section 3.2 of "HTTP Over TLS" [RFC2818], the TLS client authentication procedure only determines that the device has a certificate chain rooted in an appropriate CA (or a self-signed certificate). The Database would not know what the client identity ought to be, unless it has some external source of information. Distribution and management of such information, including revocation lists, are outside the scope of this document.
o 如“HTTP Over TLS”[RFC2818]第3.2节所述，TLS客户端身份验证过程仅确定设备具有根在适当CA（或自签名证书）中的证书链。数据库不会知道客户身份应该是什么，除非它有一些外部信息源。此类信息（包括撤销清单）的分发和管理不在本文件范围内。
o Authentication schemes are secure only to the extent that secrets or certificates are kept secure. When there are a vast number of deployed devices using PAWS, the possibility that device keys will not leak becomes small. Implementations should consider how to manage the system in the eventuality that there is a leak.
o 认证方案只有在保密或证书安全的情况下才是安全的。当有大量使用爪子部署的设备时，设备密钥不会泄漏的可能性很小。实现应该考虑如何在出现泄漏的情况下管理系统。
[JSON-RPC] "JSON-RPC 2.0 Specification", <http://www.jsonrpc.org/specification>.
[JSON-RPC]“JSON-RPC 2.0规范”<http://www.jsonrpc.org/specification>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <http://www.rfc-editor.org/info/rfc2119>.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，DOI 10.17487/RFC2119，1997年3月<http://www.rfc-editor.org/info/rfc2119>.
[RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, DOI 10.17487/RFC2818, May 2000, <http://www.rfc-editor.org/info/rfc2818>.
[RFC2818]Rescorla，E.，“TLS上的HTTP”，RFC 2818，DOI 10.17487/RFC2818，2000年5月<http://www.rfc-editor.org/info/rfc2818>.
[RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, <http://www.rfc-editor.org/info/rfc3339>.
[RFC3339]Klyne，G.和C.Newman，“互联网上的日期和时间：时间戳”，RFC 3339，DOI 10.17487/RFC3339，2002年7月<http://www.rfc-editor.org/info/rfc3339>.
[RFC5077] Salowey, J., Zhou, H., Eronen, P., and H. Tschofenig, "Transport Layer Security (TLS) Session Resumption without Server-Side State", RFC 5077, DOI 10.17487/RFC5077, January 2008, <http://www.rfc-editor.org/info/rfc5077>.
[RFC5077]Salowey，J.，Zhou，H.，Eronen，P.，和H.Tschofenig，“无服务器端状态的传输层安全（TLS）会话恢复”，RFC 5077，DOI 10.17487/RFC5077，2008年1月<http://www.rfc-editor.org/info/rfc5077>.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, DOI 10.17487/RFC5226, May 2008, <http://www.rfc-editor.org/info/rfc5226>.
[RFC5226]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 5226，DOI 10.17487/RFC5226，2008年5月<http://www.rfc-editor.org/info/rfc5226>.
[RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, DOI 10.17487/RFC5234, January 2008, <http://www.rfc-editor.org/info/rfc5234>.
[RFC5234]Crocker，D.，Ed.和P.Overell，“语法规范的扩充BNF:ABNF”，STD 68，RFC 5234，DOI 10.17487/RFC5234，2008年1月<http://www.rfc-editor.org/info/rfc5234>.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security (TLS) Protocol Version 1.2", RFC 5246, DOI 10.17487/RFC5246, August 2008, <http://www.rfc-editor.org/info/rfc5246>.
[RFC5246]Dierks，T.和E.Rescorla，“传输层安全（TLS）协议版本1.2”，RFC 5246，DOI 10.17487/RFC5246，2008年8月<http://www.rfc-editor.org/info/rfc5246>.
[RFC5491] Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV Presence Information Data Format Location Object (PIDF-LO) Usage Clarification, Considerations, and Recommendations", RFC 5491, DOI 10.17487/RFC5491, March 2009, <http://www.rfc-editor.org/info/rfc5491>.
[RFC5491]Winterbottom，J.，Thomson，M.，和H.Tschofenig，“GEOPRIV存在信息数据格式位置对象（PIDF-LO）使用说明、注意事项和建议”，RFC 5491，DOI 10.17487/RFC5491，2009年3月<http://www.rfc-editor.org/info/rfc5491>.
[RFC6350] Perreault, S., "vCard Format Specification", RFC 6350, DOI 10.17487/RFC6350, August 2011, <http://www.rfc-editor.org/info/rfc6350>.
[RFC6350]Perreault，S.，“vCard格式规范”，RFC 6350，DOI 10.17487/RFC6350，2011年8月<http://www.rfc-editor.org/info/rfc6350>.
[RFC7095] Kewisch, P., "jCard: The JSON Format for vCard", RFC 7095, DOI 10.17487/RFC7095, January 2014, <http://www.rfc-editor.org/info/rfc7095>.
[RFC7095]Kewisch，P.，“jCard:vCard的JSON格式”，RFC 7095，DOI 10.17487/RFC7095，2014年1月<http://www.rfc-editor.org/info/rfc7095>.
[RFC7159] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data Interchange Format", RFC 7159, DOI 10.17487/RFC7159, March 2014, <http://www.rfc-editor.org/info/rfc7159>.
[RFC7159]Bray，T.，Ed.“JavaScript对象表示法（JSON）数据交换格式”，RFC 7159，DOI 10.17487/RFC7159，2014年3月<http://www.rfc-editor.org/info/rfc7159>.
[RFC7231] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content", RFC 7231, DOI 10.17487/RFC7231, June 2014, <http://www.rfc-editor.org/info/rfc7231>.
[RFC7231]Fielding，R.，Ed.和J.Reschke，Ed.，“超文本传输协议（HTTP/1.1）：语义和内容”，RFC 7231，DOI 10.17487/RFC72312014年6月<http://www.rfc-editor.org/info/rfc7231>.
[RFC7525] Sheffer, Y., Holz, R., and P. Saint-Andre, "Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)", BCP 195, RFC 7525, DOI 10.17487/RFC7525, May 2015, <http://www.rfc-editor.org/info/rfc7525>.
[RFC7525]Sheffer，Y.，Holz，R.，和P.Saint Andre，“安全使用传输层安全性（TLS）和数据报传输层安全性（DTLS）的建议”，BCP 195，RFC 7525，DOI 10.17487/RFC7525，2015年5月<http://www.rfc-editor.org/info/rfc7525>.
[ETSI-EN-301-598] European Telecommunication Standards Institute (ETSI), "ETSI EN 301 598 (V1.1.1): White Space Devices (WSD); Wireless Access Systems operating in the 470 MHz to 790 MHz TV broadcast band; Harmonized EN covering the essential requirements of article 3.2 of the R&TTE Directive", April 2014, <http://www.etsi.org/deliver/ etsi_en/301500_301599/301598/01.01.01_60/ en_301598v010101p.pdf>.
[ETSI-EN-301-598]欧洲电信标准协会（ETSI），“ETSI EN 301 598（V1.1.1）：白空间设备（WSD）；在470 MHz至790 MHz电视广播频段运行的无线接入系统；涵盖R&TTE指令第3.2条基本要求的协调欧洲标准”，2014年4月， <http://www.etsi.org/deliver/ etsi_en/301500_301599/301598/01.01.01_60/en_301598V01010101P.pdf>。
[FCC-CFR47-15H] U. S. Government, "Electronic Code of Federal Regulations, Title 47, Part 15, Subpart H: Television Band Devices", December 2010, <http://www.ecfr.gov/cgi-bin/ text-idx?rgn=div6&view=text&node=47:1.0.1.1.16.8>.
[FCC-CFR47-15H]美国政府，“联邦法规电子代码，第47篇，第15部分，H子部分：电视波段设备”，2010年12月<http://www.ecfr.gov/cgi-bin/ text idx？rgn=div6&view=text&node=47:1.0.1.1.16.8>。
[FCC-Review-2012-10] Federal Communications Commission, "Administration Topics Review", October 2012, <http://transition.fcc.gov/bureaus/oet/ea/presentations/ files/oct12/2b-TCB-Admin-Issues-Oct-2012-GT.pdf>.
[FCC-Review-2012-10]联邦通信委员会，“管理主题审查”，2012年10月<http://transition.fcc.gov/bureaus/oet/ea/presentations/ 文件/oct12/2b-TCB-Admin-Issues-Oct-2012-GT.pdf>。
[ISO3166-1] "Country Codes", <http://www.iso.org/iso/country_codes.htm>.
[ISO3166-1]“国家代码”<http://www.iso.org/iso/country_codes.htm>.
[RFC6953] Mancuso, A., Ed., Probasco, S., and B. Patil, "Protocol to Access White-Space (PAWS) Databases: Use Cases and Requirements", RFC 6953, DOI 10.17487/RFC6953, May 2013, <http://www.rfc-editor.org/info/rfc6953>.
[RFC6953]Mancuso，A.，Ed.，Probasco，S.，和B.Patil，“访问空白（PAWS）数据库的协议：用例和要求”，RFC 6953，DOI 10.17487/RFC6953，2013年5月<http://www.rfc-editor.org/info/rfc6953>.
[RFC7459] Thomson, M. and J. Winterbottom, "Representation of Uncertainty and Confidence in the Presence Information Data Format Location Object (PIDF-LO)", RFC 7459, DOI 10.17487/RFC7459, February 2015, <http://www.rfc-editor.org/info/rfc7459>.
[RFC7459]Thomson，M.和J.Winterbottom，“存在信息数据格式位置对象（PIDF-LO）中不确定性和置信度的表示”，RFC 7459，DOI 10.17487/RFC7459，2015年2月<http://www.rfc-editor.org/info/rfc7459>.
[WGS-84] National Imagery and Mapping Agency, "Department of Defense World Geodetic System 1984, Its Definition and Relationships with Local Geodetic Systems", NIMA TR8350.2, Third Edition, Amendment 1, January 2000, <http://earth-info.nga.mil/GandG/publications/tr8350.2/ tr8350_2.html>.
[WGS-84]国家图像和测绘局，“1984年国防部世界大地测量系统，其定义及其与地方大地测量系统的关系”，NIMA TR8350.2，第三版，修正案1，2000年1月<http://earth-info.nga.mil/GandG/publications/tr8350.2/ tr8350_2.html>。
As discussed in "Database Discovery" (Section 4.1), some regulatory domains support the preconfiguration of devices with the URI of a listing server, to which devices can connect to obtain a list of Databases certified by the regulatory domain. Regulatory domains may require the device to periodically contact the Database Listing Server to validate and/or update its list of certified Databases. If the device is unable to validate its list of certified Databases within the required period, regulatory rules may require the device to treat this inability as equivalent to the device having no available spectrum.
如“数据库发现”（第4.1节）所述，一些监管域支持使用列表服务器的URI对设备进行预配置，设备可以连接到该服务器以获得监管域认证的数据库列表。监管域可能要求设备定期联系数据库列表服务器，以验证和/或更新其认证数据库列表。如果设备无法在规定期限内验证其认证数据库列表，监管规则可能要求设备将此无法视为等同于没有可用频谱的设备。
A sample JSON response from a Database Listing Server might be represented as follows:
来自数据库列表服务器的示例JSON响应可能表示为：
{
"lastUpdateTime": "2014-06-28T10:00:00Z",
"maxRefreshMinutes": 1440
"dbs": [
{
"name": "Some Operator",
"uris": [
{
"uri": "https://example.some.operator.com",
"protocol": "paws"
},
...
]
},
...
]
}
{
"lastUpdateTime": "2014-06-28T10:00:00Z",
"maxRefreshMinutes": 1440
"dbs": [
{
"name": "Some Operator",
"uris": [
{
"uri": "https://example.some.operator.com",
"protocol": "paws"
},
...
]
},
...
]
}
The parameters in this sample message are:
此示例消息中的参数为：
lastUpdateTime: The time at which the database entries were last updated.
lastUpdateTime：上次更新数据库项的时间。
maxRefreshMinutes: The maximum interval, expressed in minutes, that is allowed between device requests to the Database Listing Server.
maxRefreshMinutes：对数据库列表服务器的设备请求之间允许的最大间隔，以分钟为单位。
dbs: A list of entries for certified Databases, each containing the following
dbs：认证数据库的条目列表，每个条目包含以下内容
name: The name of the database operator.
名称：数据库操作员的名称。
uris: One or more URIs for each Database, allowing a Database to support more than one protocol.
URI：每个数据库有一个或多个URI，允许一个数据库支持多个协议。
uri, protocol: Each protocol supported by a certified Database is associated with a separate URI (PAWS protocol URI shown).
uri，协议：认证数据库支持的每个协议都与一个单独的uri相关联（显示了PAWS协议uri）。
Acknowledgments
致谢
The authors gratefully acknowledge the contributions of: Gabor Bajko, Ray Bellis, Teco Boot, Nancy Bravin, Rex Buddenberg, Gerald Chouinard, Stephen Farrell, Michael Fitch, Joel M. Halpern, Daniel Harasty, Michael Head, Jussi Kahtava, Kalle Kulsmanen, Warren Kumari, Paul Lambert, Andy Lee, Anthony Mancuso, Basavaraj Patil, Scott Probasco, Brian Rosen, Andy Sago, Peter Stanforth, John Stine, and Juan Carlos Zuniga.
作者衷心感谢以下人士的贡献：加博·巴伊科、雷·贝利斯、泰科·布特、南希·布拉文、雷克斯·布登伯格、杰拉尔德·乔纳德、斯蒂芬·法雷尔、迈克尔·菲奇、乔尔·哈尔彭、丹尼尔·哈拉斯蒂、迈克尔·海德、朱西·卡塔瓦、卡尔·库尔斯曼、沃伦·库马里、保罗·兰伯特、安迪·李、安东尼·曼库索、巴萨瓦拉伊·帕蒂尔、斯科特·普罗巴斯科、，布莱恩·罗森、安迪·萨戈、彼得·斯坦福斯、约翰·斯汀和胡安·卡洛斯·祖尼加。
Contributors
贡献者
This document draws heavily from draft-das-paws-protocol and draft-wei-paws-framework. The editor would like to specifically call out and thank the contributing authors of those two documents.
本文件大量借鉴了das paws协议草案和wei paws框架草案。编辑要特别呼吁并感谢这两份文件的撰稿人。
Donald Joslyn Spectrum Bridge Inc. 1064 Greenwood Blvd. Lake Mary, FL 32746 United States EMail: d.joslyn@spectrumbridge.com
唐纳德·乔斯林光谱桥公司，格林伍德大道1064号。美国佛罗里达州玛丽湖32746电子邮件：d。joslyn@spectrumbridge.com
Xinpeng Wei Huawei Phone: +86 13436822355 EMail: weixinpeng@huawei.com
魏新鹏华为电话：+86 13436822355邮箱：weixinpeng@huawei.com
Authors' Addresses
作者地址
Vincent Chen (editor) Google 1600 Amphitheatre Parkway Mountain View, CA 94043 United States
Vincent Chen（编辑）谷歌1600圆形剧场公园道山景，加利福尼亚州94043
EMail: vchen@google.com
EMail: vchen@google.com
Subir Das Applied Communication Sciences 150 Mount Airy Road Basking Ridge, NJ 07920 United States
Subir Das应用通信科学公司美国新泽西州太阳岭艾里山路150号，邮编：07920
EMail: sdas@appcomsci.com
EMail: sdas@appcomsci.com
Lei Zhu Huawei
雷竹华为
Phone: +86 13910157020
EMail: lei.zhu@huawei.com
Phone: +86 13910157020
EMail: lei.zhu@huawei.com
John Malyar iconectiv (formerly Telcordia Interconnection Solutions) 444 Hoes Lane/RRC 4E1106 Piscataway, NJ 08854 United States
美国新泽西州皮斯卡塔韦Hoes Lane/RRC 4E1106 Piscataway 444 Hoes Lane/John Malyar IConnectiv（前Telcordia互联解决方案公司）
EMail: jmalyar@iconectiv.com
EMail: jmalyar@iconectiv.com
Peter J. McCann Huawei 400 Crossing Blvd, 2nd Floor Bridgewater, NJ 08807 United States
Peter J.McCann Huawei美国新泽西州布里奇沃特市穿越大道400号2楼08807
Phone: +1 908 541 3563
EMail: peter.mccann@huawei.com
Phone: +1 908 541 3563
EMail: peter.mccann@huawei.com