Multi-AP Specification V2.0 中文翻译 第10章 Link metric collection（链路度量采集）
Multi-AP Specification下载地址：https://www.wi-fi.org/download.php?file=/sites/default/files/private/Multi-AP_Specification_v2.0.pdf
#依赖百度翻译&Google翻译&个人理解
#如果有错误地方，请帮忙指出， 感谢
10 Link metric collection（链路度量采集）
10.1 Backhaul link metrics
This section defines the protocol for a Multi-AP device to convey backhaul link metric information associated with each of the BSSs in which the Multi-AP device is operating.
本节定义了用于Multi-AP设备的协议，以传达与Multi-AP设备在其中运行的每个BSS相关联的回程链路度量信息。
The 1905 link metric information dissemination protocol is used to query and report link metrics for backhaul links (e.g. link between a Multi-AP Agent AP interface and a Multi-AP Agent backhaul STA interface, or between two Multi-AP Agent Ethernet interfaces. See [2]). If triggered, a Multi-AP Controller and Multi-AP Agent shall send a 1905 Link metric query message to a Multi-AP Agent.
1905链路量度信息分发协议用于查询和报告BACKHAUL链路的链路量度（例如，Multi-AP Agent AP接口和Multi-AP Agent backhaul STA接口之间的链路，或者两个Multi-AP Agent以太网接口之间的链路。 见[2]）。 如果被触发，则Multi-AP控制器和Multi-AP代理应向Multi-AP代理发送1905链路度量查询消息。
Note: Additional clarifications with respect to fields in a 1905 Transmitter link metric TLV are as follows:
注意：关于1905 Transmitter链路度量TLV中的字段的其他说明如下：
• macThroughputCapacity field is the estimated MAC data rate in Mb/s for the backhaul link in the downlink direction when reported by a Multi-AP Agent that operates the AP for the link, or the estimated MAC data rate in Mb/s for the backhaul link in the uplink direction when reported by the Multi-AP Agent that operates the backhaul STA for the link, if 100% of channel air time and BSS operating bandwidth were to be available.
•macThroughputCapacity字段是操作该链路的AP的Multi-AP代理报告时，下行的backhaul链路的评估MAC数据速率（Mb/s），或者操作该链路的backhaul STA的Multi-AP代理报告时，上行的backhaul链路的评估MAC数据速率（Mb/s），如果信道广播时间和BSS工作带宽都是100%，则可用。
• linkAvailability field is the predicted percentage of Air Time that the backhaul link would consume given the current channel condition, assuming sufficient BE traffic is generated over the backhaul link to the client STAs and/or other backhaul STAs associated with the downstream Multi-AP Agent to fill this Air Time.
•linkAvailability字段是在给定当前信道条件下backhaul链路将消耗的时空的预测百分比，假设通过回程链路生成足够的BE通信量到客户端sta和/或与下游多AP代理相关联的其他回程sta以填充此广播时间。。
Note: Additional clarifications with respect to fields in a 1905 Receiver link metric TLV are as follows:
注意：关于1905 Receiver link metric TLV中字段的其他说明如下：
• The RSSI field is calculated from the RCPI of a number of PPDU received when reported by a Multi-AP Agent that operates the AP for the link, or the Beacon RSSI when reported by a Multi-AP Agent that operates the backhaul STA for the link.
•RSSI字段是根据由操作链路的AP的Multi-AP代理报告时接收到的多个PPDU的RCPI计算的，或者由操作链路的backhaul STA的Multi-AP 代理报告的Beacon RSSI计算的。
Note: A Multi-AP Agent supporting [11] might use the transmitter and receiver Link metric TLVs as defined in [11] to report the metrics of Generic Phy non-Wi-Fi interfaces.
注意：支持[11]的Multi-AP Agent可能会使用[11]中定义的发送器和接收器链路度量TLV来报告通用Phy非Wi-Fi接口的度量。
10.2 Per-AP metrics and bulk STA metrics（本节每AP指标和批量STA指标）
This section defines the protocol for a Multi-AP Agent to convey per-AP metric information about each of the BSS (fronthaul and/or backhaul) it is operating. These metrics pertain to the BSS overall, and can also include information relating to every STA associated to the AP. For metrics relating to a single specific STA that might be associated to the BSS, see section 10.3.
定义了Multi-AP代理的协议，该协议用于传送有关其正在运行的每个BSS（fronthaul和/或backhaul）的每个AP度量信息。这些度量与BSS总体相关，还可以包括与AP相关联的每个STA的相关信息， 有关可能与BSS相关连的单个特定STA的指标，见10.3节。
10.2.1 Link metric measurements from the AP
If triggered, a Multi-AP Controller shall send an AP Metrics Query message per section 17.1.16 to a Multi-AP Agent.
如果被触发，则Multi-AP控制器应按照第17.1.16节的要求向Multi-AP代理发送AP度量查询消息。
If a Multi-AP Agent receives an AP Metrics Query message, then it shall respond within one second with an AP Metrics response message (section 17.1.17) containing the following TLVs:
如果Multi-AP代理收到AP 度量查询消息，则它应在1秒内用包含以下TLV的AP 度量响应消息（第17.1.17节）进行响应：
• One AP Metrics TLV per section 17.2.22 for each of the BSSs specified in the query.
•根据第17.2.22节，为查询中指定的每个BSS提供一个AP度量TLV。
• If the Multi-AP Agent implements Profile-2, it shall include one AP Extended Metrics TLV for each of the BSSs specified in the query.
•如果Multi-AP代理实现Profile-2，它应为查询中指定的每个BSS包含一个AP扩展度量TLV。
• If the Multi-AP Agent implements Profile-2, it shall include one Radio Metrics TLV for each of the radios specified in the query.
•如果Multi-AP代理实现Profile-2，它应包括查询中指定的每个radio的一个radio度量TLV。
The AP Metrics Response message shall contain the same MID that was received in the AP Metrics Query message.
AP Metrics Response消息应包含与AP Metrics Query消息中收到的相同的MID。
If a Multi-AP Agent receives a Metric Reporting Policy TLV with AP Metrics Reporting Interval field set to a non-zero value, it shall send an AP Metrics Response message to the Multi-AP Controller once every reporting interval specified in the field and containing the following TLVs:
如果Multi-AP代理接收到一个度量报告策略TLV，并且AP度量报告间隔字段设置为非零值，则它应在字段中指定的每个报告间隔中向Multi-AP控制器发送一个AP度量响应消息，该消息包含以下TLV：
• One AP Metrics TLV for each BSS which it is operating.
•一个AP度量其正在运行的每个BSS的TLV。
• If the Multi-AP Agent implements Profile-2, it shall include one AP Extended Metrics TLV for each BSS which it is operating
•如果Multi-AP代理实施Profile-2，它应为其正在运行的每个BSS包括一个AP扩展度量TLV
• If the Multi-AP Agent implements Profile-2, it shall include one Radio Metrics TLV for each radio which it is operating.
•如果Multi-AP代理实现Profile-2，则它应包括其正在运行的每个无线电的一个无线电指标TLV。
If a Multi-AP Agent receives a Metric Reporting Policy TLV with AP Metrics Channel Utilization Reporting Threshold field set to a non-zero value for a given radio, it shall measure the channel utilization on that radio in each consecutive implementation-specific measurement period and, if the most recently measured channel utilization has crossed the reporting threshold in either direction (with respect to the previous measurement), it shall send an AP Metrics Response message to the Multi-AP Controller containing the following TLVs:
如果Multi-AP代理接收到一个度量报告策略TLV，并且AP Metrics Channel Utilization Reporting Threshold字段设置为给定无线电的非零值，则它应在每个连续的特定于实现的测量周期中测量该无线电上的信道利用率，并且如果最近测量的信道利用率已经超过在任一方向上的报告阈值（相对于先前的测量），它应向包含以下TLV的Multi-AP控制器发送AP度量响应消息：
• One AP Metrics TLV for each of the BSSs on that radio.
•一个AP度量该无线电上每个BSS的TLV。
• If the Multi-AP Agent implements Profile-2, it shall include one AP Extended Metrics TLV for each of the BSSs on that radio.
•如果多AP代理实现Profile-2，它应包括该无线电上每个BSS的一个AP扩展度量TLV。
• If the Multi-AP Agent implements Profile-2, it shall include one Radio Metrics TLV for that radio.
•如果多AP代理实现Profile-2，它应包括该无线电的一个无线电度量TLV。
If a Multi-AP Agent sends an AP Extended Metrics TLV, it shall encode the byte counters in that TLV according to the value of the Byte Counter Units field in its last sent Profile-2 AP Capability TLV (if the Multi-AP Agent implements Profile- 2), or in bytes if it has not sent a Profile-2 AP Capability TLV.
如果多AP代理发送AP扩展度量TLV，则应根据其上次发送的Profile-2 AP Capability TLV（如果多AP代理实现Profile-2 AP Capability TLV）中的byte Counter Units字段的值对该TLV中的字节计数器进行编码，如果该代理没有发送Profile-2 AP Capability TLV，则以字节为单位进行编码。
If a Multi-AP Agent sends an AP Metrics Response message and if the most recently received (if any) Metric Reporting Policy TLV has Associated STA Traffic Stats Inclusion Policy set to one for a specified radio, the Multi-AP Agent shall also include one Associated STA Traffic Stats TLV for each STA associated to a BSS being reported on that radio unless it has sent a previous AP Metrics Response message including the corresponding STA Traffic Stats TLVs within the previous 10 seconds, in which case it may include or omit the STA Traffic Stats TLVs.???
如果多AP代理发送AP Metrics响应消息，并且如果最近接收到的（如果有）度量报告策略TLV将关联的STA Traffic Stats Inclusion策略设置为针对指定无线电的1，则多AP代理还应包括与该无线电上正在报告的BSS相关联的每个STA的一个关联STA流量统计TLV除非它在前10秒内发送了包括相应的STA Traffic Stats tlv的先前AP Metrics响应消息，在这种情况下，它可以包括或省略STA Traffic Stats tlv。
If a Multi-AP Agent sends an Associated STA Traffic Stats TLV, it shall encode the byte counters in that TLV according to the value of the Byte Counter Units field in its last sent Profile-2 AP Capability TLV (if the Multi-AP Agent implements Profile-2), or in bytes if it has not sent a Profile-2 AP Capability TLV.？？？
如果多AP代理发送一个关联的STA流量统计TLV，则应根据其上次发送的Profile-2 AP Capability TLV（如果多AP代理实现Profile-2 AP Capability TLV）中的byte Counter Units字段的值对该TLV中的字节计数器进行编码；如果多AP代理没有发送Profile-2 AP Capability TLV，则以字节为单位进行编码。
If a Multi-AP Agent sends an AP Metrics Response message and if the most recently received (if any) Metric Reporting Policy TLV has Associated STA Link Metrics Inclusion Policy set to one for a specified radio, the Multi-AP Agent shall also include one Associated STA Link Metrics TLV and if the Multi-AP Agent implements Profile-2 one Associated STA Extended Link Metrics TLV for each STA associated to a BSS being reported on that radio.
如果多AP代理发送AP Metrics响应消息，并且如果最近接收到的（如果有）度量报告策略TLV将关联的STA Link Metrics Inclusion策略设置为指定无线电的1，多AP代理还应包括一个相关的STA链路度量TLV，如果多AP代理实现Profile-2，则每个与该无线电上报告的BSS相关联的STA扩展链路度量TLV。
When reporting STA Traffic Stats, a Multi-AP Agent should report the most recent counter information commensurate with maintaining AP throughput performance, and shall report counter information no older than 10 seconds.
在报告STA流量统计信息时，多AP代理应报告与维持AP吞吐量性能相对应的最新计数器信息，并且应报告不超过10秒的计数器信息。
Note: The Estimated Air Time Fraction subfield in the Estimated Service Parameters Information field in an AP Metrics TLV is defined in 9.4.2.174 of [1] and represents the predicted percentage of air time that a new STA joining the BSS would be allocated for data PPDUs (transmitted downlink from the AP) carrying data of the corresponding AC for the STA. For the purpose of defining the Estimated Air Time Fraction value, it is assumed that the downlink traffic load to the hypothetical newly joining STA is sufficient to fill the estimated air time fraction.???
10.2.2 Channel Scan（信道扫描）
A Multi-AP network managed by a Multi-AP Controller that implements Profile-2 provides the ability for Multi-AP Agents to perform a set of channel scans and report the results of the scans to the Multi-AP Controller. A Multi-AP Agent has the capability to perform a set of channel scans either at boot only, or upon request from the Multi-AP Controller.
由实现Profile-2的Multi-AP控制器管理的Multi-AP网络为Multi-AP代理提供了执行一组信道扫描并将扫描结果报告给Multi-AP控制器的能力。Multi-AP代理只可以在boot时执行一组通道扫描，或者根据Multi-AP控制器的请求执行一组通道扫描。
10.2.2.1 Channel Scan Requirements on a Multi-AP Controller（Multi-AP控制器的信道扫描要求）
If triggered, a Multi-AP Controller shall send a Channel Scan Request message (see section 17.1.33) to a Multi-AP Agent.
如果触发，Multi-AP控制器应向Multi-AP代理发送信道扫描请求消息（见第17.1.33节）。
If a Multi-AP Controller sends a Channel Scan Request to a Multi-AP Agent with the Perform Fresh Scan bit set to zero, it shall set the Number of Operating Classes field for each radio listed to zero.
如果Multi-AP控制器在Perform Fresh Scan位设置为零的情况下向Multi-AP代理发送信道扫描请求，则应将所列每个无线电的Number of Operating Classes段设置为零。
A Multi-AP Controller shall not send a Channel Scan Request to a Multi-AP Agent that implements Profile-1.
Multi-AP控制器不得向实现Profile-1的Multi-AP代理发送信道扫描请求。
If a Multi-AP Controller receives a Channel Scan Report message, it shall respond within one second with a 1905 Ack message.
如果Multi-AP控制器接收到信道扫描报告消息，它应在1秒内响应1905 Ack消息。
10.2.2.2 Channel Scan Requirements on a Multi-AP Agent（Multi-AP代理的信道扫描要求）
If a Multi-AP Agent receives a Channel Scan Request message, it shall respond within one second with a 1905 Ack message.
如果Multi-AP代理接收到信道扫描请求消息，它应在1秒内用1905 Ack消息响应。
On-Boot Scan（开机扫描）
If a Multi-AP Agent sets the "On boot only" bit to 1 in its Channel Scan Capabilities TLV, it shall perform a Channel Scan at boot on each of the radio and operating class and channel combinations specified in its Channel Scan Capabilities and shall store the scan results.
如果Multi-AP代理在其信道扫描能力TLV中将“仅在引导时”位设置为1，则应在开机时对信道扫描能力中指定的每个无线电和操作类以及信道组合执行信道扫描，并存储扫描结果。
Requested Channel Scan – Fresh（请求的通道扫描-刷新）
If a Multi-AP Agent has set the "On boot only" bit to 0 in its Channel Scan Capabilities TLV and receives from the Multi-AP Controller a Channel Scan Request message containing a Channel Scan Request TLV with the “Perform Fresh Scan” bit set to one and the Multi-AP Agent is currently performing a Requested Channel Scan, the Multi-AP Agent should abort the current Requested Channel Scan as soon as practical and shall send to the Multi-AP Controller a Channel Scan Report Message relating to that Channel Scan before acting on the new request as described in the following paragraph.
如果Multi-AP代理在其通道扫描功能TLV中将“On boot only”位设置为0，并从Multi-AP控制器接收到一条通道扫描请求消息，其中包含通道扫描请求TLV，“Perform Fresh Scan”位设置为1，并且Multi-AP代理当前正在执行请求的通道扫描，Multi-AP代理应尽快中止当前请求的信道扫描，并在对下一段所述的新请求采取行动之前，向Multi-AP控制器发送与该信道扫描相关的信道扫描报告消息。
If a Multi-AP Agent that has set the "On boot only" bit to 0 in its Channel Scan Capabilities TLV receives from the Multi-AP Controller a Channel Scan Request message containing a Channel Scan Request TLV with the “Perform Fresh Scan” bit set to one and is not currently performing a Requested Channel Scan, the Multi-AP Agent shall, as soon as practical, start a sequence of Channel Scans on the requested radio and operating class and channel combinations. When finished scanning, or within 5 minutes, whichever comes sooner, the Multi-AP Agent shall send to the Multi-AP Controller a Channel Scan Report Message (see section 17.1.34) containing one Timestamp TLV (see section 17.2.41) indicating the current time and one Channel Scan Result TLV (see 17.2.40) for each of the operating class and channel combinations listed in the Channel Scan Request TLV. Each Channel Scan Result TLV shall contain either a success Status Code and the scan result data or a non-Success Scan Status code, as defined in Table 50, indicating the reason the scan could not be completed. The Multi-AP Agent shall set the Status Code as follows:
如果在信道扫描能力TLV中将“On boot only”位设置为0的Multi-AP代理从Multi-AP控制器接收到一条信道扫描请求消息，其中包含信道扫描请求TLV，“Perform Fresh Scan”位设置为1，并且当前未执行请求的信道扫描，则Multi-AP代理应尽快在当前实际情况下，在请求的无线电、操作类和频道组合上启动一系列频道扫描。扫描完成后，或在5分钟内（哪个先满足，就以那个为准），Multi-AP代理应向Multi-AP控制器发送信道扫描报告消息（见第17.1.34节），其中包含一个时间戳TLV（见17.2.41节），该TLV指示信道扫描请求TLV中列出的每个操作类和信道组合的当前时间和一个信道扫描结果TLV（见17.2.40）。每个通道扫描结果TLV应包含一个成功状态代码和扫描结果数据，或一个未成功扫描状态代码，如表50所示，说明扫描无法完成的原因。Multi-AP代理设置状态码如下：
If the requested Channel Scan operating class and channel combination is in the set of operating class and channel combinations in the Multi-AP Agent's declared Channel Scan Capabilities and the Multi-AP Agent successfully completed the fresh Channel Scan, the Multi-AP Agent shall set the Status Code to 0x00 (Success).
如果请求的信道扫描操作类和信道组合在Multi-AP代理声明的信道扫描能力中的操作类和信道组合集合中，并且Multi-AP代理成功地完成了新的信道扫描，则Multi-AP代理应将状态码设置为0x00（成功）。
If the requested Channel Scan operating class and channel combination is not in the set of operating class and channel combinations in the Multi-AP Agent's declared Channel Scan Capabilities, the Multi-AP Agent shall set the Status Code to 0x01.
如果请求的信道扫描操作类和信道组合不在Multi-AP代理声明的信道扫描能力中的操作类和信道组合集合中，则Multi-AP代理应将状态码设置为0x01。
If the Multi-AP Agent received the Channel Scan Request less than the Minimum Scan Interval declared in the Multi-AP Agent's Channel Scan Capabilities after the previously received Channel Scan Request, the Multi-AP Agent may set the Status Code to 0x02 and not perform the Channel Scan.
如果Multi-AP代理在先前收到的通道扫描请求之后接收到的通道扫描请求小于在Multi-AP代理的通道扫描功能中声明的最小扫描间隔，则Multi-AP代理可以将状态代码设置为0x02，并且不执行通道扫描。
If the Multi-AP Agent has not performed the Channel Scan because the radio is too busy, the Multi-AP Agent shall set the Status Code to 0x03.
如果Multi-AP代理由于radio太忙而未执行频道扫描，则Multi-AP代理应将状态代码设置为0x03。
If the Multi-AP Agent has not been able to complete the Channel Scan in the time available, the Multi-AP Agent shall set the Status Code to 0x04.
如果Multi-AP代理未能在可用时间内完成信道扫描，则Multi-AP代理应将状态码设置为0x04。
If the Multi-AP Agent has aborted the Channel Scan due to receiving another Channel Scan Request, the Multi-AP Agent shall set the Status Code to 0x05.
如果Multi-AP代理由于接收到另一个信道扫描请求而中止了信道扫描，则Multi-AP代理应将状态码设置为0x05。
The Multi-AP Agent shall store the result of the last successful scan on each radio and operating class and channel combination.
Multi-AP代理应将最后一次成功扫描的结果存储在每个无线电、操作等级和信道组合上。
If a Multi-AP Agent has set the "On boot only" bit to 1 in its Channel Scan Capabilities TLV and receives from the Multi-AP Controller a Channel Scan Request message containing a Channel Scan Request TLV with the “Perform Fresh Scan” bit set to one, the Multi-AP Agent shall respond with a Channel Scan Report Message containing one Timestamp TLV indicating the current time and one Channel Scan Result TLV for each of the operating class and channel combinations listed in the Channel Scan Request TLV and set the Status Code to 0x06.
如果Multi-AP代理在其通道扫描功能TLV中将“On boot only”位设置为1，并从Multi-AP控制器接收到一条通道扫描请求消息，其中包含通道扫描请求TLV，“Perform Fresh Scan”位设置为1，Multi-AP代理应响应信道扫描报告消息，其中包含一个时间戳TLV，指示信道扫描请求TLV中列出的每个操作类和信道组合的当前时间和一个信道扫描结果TLV，并将状态代码设置为0x06。
Requested Channel Scan – Stored（请求的通道扫描-已存储）
If a Multi-AP Agent receives a Channel Scan Request message containing a Channel Scan Request TLV with the “Perform Fresh Scan” bit set to zero, the Multi-AP Agent shall respond with a Channel Scan Report Message (see 17.1.34) containing one Timestamp TLV (see section 17.2.41) indicating the current time and one Channel Scan Result TLV (see 17.2.40) for each of the operating class and channel combinations for which it has stored results for each of the radios listed in the Channel Scan Request TLV, even if the Channel Scan Result is from an Independent Channel Scan and the "Report Independent Channel Scans" flag was set to zero in the most recently received Channel Scan Reporting Policy TLV. If the Multi-AP Agent has set the "On boot only" bit to 1 in its Channel Scan Capabilities TLV and has not yet completed the On-boot Scan on an operating class and channel combination listed in its Channel Scan Capabilities TLV, the Multi-AP Agent shall also include a Channel Scan Result TLV for that operating class and channel combination with the Status Code set to 0x04.
如果Multi-AP代理接收到包含通道扫描请求TLV的通道扫描请求消息，“Perform Fresh Scan”位设置为零，关于每个通道扫描结果，请参见see 17.1.34中所列的通道扫描结果和一个通道扫描结果请求TLV，即使通道扫描结果来自独立通道扫描，并且在最近收到的通道扫描报告策略TLV中，“Report Independent Channel Scans”标志设置为零。如果Multi-AP代理已在其通道扫描功能TLV中将“On boot only”位设置为1，并且尚未在其通道扫描功能TLV中列出的操作类和通道组合上完成启动时扫描，Multi-AP代理还应包括该操作等级和信道组合的信道扫描结果TLV，状态代码设置为0x04。
Independent Channel Scan（独立通道扫描）
A Multi-AP Agent may perform an Independent Channel Scan.
Multi-AP代理可以执行独立通道扫描。
If a Multi-AP Agent performs a set of Independent Channel Scans, and the “Report Independent Channel Scans” flag was set to one in the most recently received Channel Scan Reporting Policy TLV, then the Multi-AP Agent shall report the channel scan results to the Multi-AP Controller in a Channel Scan Report message as described above in Section 10.2.2.2 for a fresh Requested Channel Scan.
如果Multi-AP代理执行一组独立通道扫描，并且在最近接收到的通道扫描报告策略TLV中，“Report Independent Channel Scans”标志设置为1，则Multi-AP代理应在通道扫描报告消息中向Multi-AP控制器报告通道扫描结果，如上文第10.2.2.2节对于新请求的通道扫描所述。
If a Multi-AP Agent performs a set of Independent Channel Scans, and has not received a Channel Scan Reporting Policy TLV, then the Multi-AP Agent shall not report the channel scan results to the Multi-AP Controller.
如果Multi-AP代理执行一组独立的通道扫描，并且没有收到通道扫描报告策略TLV，则Multi-AP代理不应向Multi-AP控制器报告通道扫描结果。
If the number of neighbors detected during a channel scan would mean that the channel scan report message would not fit within one 1905.1 CMDU, the Multi-AP Agent shall split the channel scan report across multiple Channel Scan Result TLVs by splitting the information related to sets of neighbor BSSs into separate Channel Scan Result TLVs and setting the NumberofNeighbors field to the number of neighbors contained in the corresponding TLV.
如果在通道扫描过程中检测到的邻居数量意味着通道扫描报告消息不适合一个1905.1 CMDU，Multi-AP代理应将多个信道扫描结果TLV的信道扫描报告拆分为多个信道扫描结果TLV，并将NumberofNeighbors字段设置为相应TLV中包含的邻居数。
10.3 Per-STA measurements（STA测量）
This section defines the protocol for a Multi-AP Agent to convey link metric information on a per-STA basis.
本节定义了Multi-AP代理在每个STA的基础上传送链路度量信息的协议。
10.3.1 Associated STA link measurements from the AP（AP测量关联的STA 链路）
This subsection defines the protocol for a Multi-AP Agent to report link quality metrics for the downlink and uplink links between a Multi-AP Agent AP and an associated STA.
本小节定义用于Multi-AP代理的协议，以报告Multi-AP代理AP和关联STA之间的下行链路和上行链路的链路质量度量。
If triggered, a Multi-AP Controller shall send an Associated STA Link Metrics Query message per section 17.1.18 to a Multi-AP Agent.
如果触发，Multi-AP控制器应根据第17.1.18节向Multi-AP代理发送相关STA链路指标查询消息。
If a Multi-AP Agent receives an Associated STA Link Metrics Query message, then it shall respond within one second with an Associated STA Link Metrics Response message per section 17.1.19 containing one Associated STA Link Metrics TLV and if the Multi-AP Agent implements Profile-2 one Associated STA Extended Link Metrics TLV for the specified STA. The Associated STA Link Metrics Response message shall contain the same MID that was received in the Associated STA Link Metrics Query message. If the specified STA is not associated with any of the BSS operated by the Multi-AP Agent (an error scenario), the Multi-AP shall set the Number of BSSIDs reported field in the Associated STA Link Metrics TLV to zero per section 17.2.24 and include an Error Code TLV with the reason code field set to 0x02 and the STA MAC address field included per section 17.2.36.
如果Multi-AP代理接收到关联的STA链路度量查询消息，则它应在1秒内响应第17.1.19节中的关联STA链路度量响应消息，其中包含一个关联的STA链路度量TLV，并且如果Multi-AP代理为指定的STA实现Profile-2一个关联的STA扩展链路度量TLV。相关的STA链路度量响应消息应包含与链路度量查询消息相同的MID。如果指定的STA不与Multi-AP代理操作的任何BSS关联（错误情况），则Multi-AP应将关联STA链路度量TLV中的BSSID报告数字段设置为根据第17.2.24节归零，并包括错误代码TLV，原因代码字段设置为0x02，STA MAC地址字段根据第17.2.36节包含。
If a Multi-AP Agent receives a Metric Reporting Policy TLV with STA Metrics Reporting RCPI Threshold field set to a nonzero value for a given radio, the Multi-AP Agent shall monitor the uplink RCPI for each STA associated to a BSS operating on that radio and, if the most recently measured uplink RCPI for a STA has crossed the STA Metrics Reporting RCPI Threshold including hysteresis margin in either direction (with respect to the previous measurement), the Multi-AP Agent shall send an Associated STA Link Metrics Response message to the Multi-AP Controller containing an Associated STA Link Metrics TLV and if the Multi-AP Agent implements Profile-2 one Associated STA Extended Link Metrics TLV corresponding to that STA. Unless STA Metrics Reporting RCPI Hysteresis Margin Override field is set to a non-zero value in the most recently received Metric Reporting Policy TLV (if any) relating to a given radio, a Multi-AP Agent should use a non-zero implementation-specific hysteresis margin that is sufficient to avoid excessive generation of Associated STA Link Metrics Response messages caused by rapid fluctuations of uplink RCPI measurements around the RCPI threshold and the Multi-AP Agent shall not use a hysteresis margin that is greater than 5 dB. If STA Metrics Reporting RCPI Hysteresis Margin Override field is set to a non-zero value in the most recently received Metric Reporting Policy TLV, a Multi-AP Agent shall use the value specified for STA Metrics Reporting RCPI Hysteresis Margin Override field as RCPI hysteresis margin when determining when to send an Associated STA Link Metrics Response message for RCPI threshold based reporting.
如果Multi-AP代理接收到一个度量报告策略TLV，并且STA Metrics Reporting RCPI Threshold字段在给定radio上设置为非零值，则Multi-AP代理应监控在该无线电上运行的BSS相关联的每个STA的上行链路RCPI，并且，如果STA的最近测量的上行链路RCPI已经越过了STA度量报告RCPI阈值，包括任一方向的磁滞幅度（相对于先前的测量），Multi-AP代理应向Multi-AP控制器发送一个相关的STA链路度量响应消息，其中包含一个相关的STA链路度量TLV，并且如果Multi-AP代理实现Profile-2，则也应包含一个与该STA相对应的关联STA扩展链路度量TLV。除非在与给定无线电相关的最近接收的度量报告策略TLV（如果有）中，STA Metrics Reporting RCPI磁滞幅度覆盖字段设置为非零值，否则Multi-AP代理应使用非零实现特定的滞后裕度， 磁滞幅度应该可以避免因为上行链路RCPI值再阈值上波动，导致生成过多的关联的STA链路指标响应消息，当然Multi-AP代理不得使用大于5db的滞后裕度（0~5db）。如果STA Metrics Reporting RCPI磁滞幅度覆盖字段在最近收到的度量报告策略TLV中设置为非零值，当确定何时为基于RCPI阈值的报告发送相关的STA链路度量响应消息时，Multi-AP代理应使用为STA Metrics报告RCPI磁滞幅度覆盖字段指定的值作为RCPI滞后裕度。
When a Multi-AP Agent measures RCPI or SNR values for the purpose of calculating the Estimated MAC Data Rate and uplink RCPI used for STA metric reporting, these values may be averaged over time using an implementation-specific smoothing function. When a non-zero STA Metrics Reporting RCPI Threshold is configured, a Multi-AP Agent should perform sufficient smoothing of uplink RCPI measurements to avoid excessive generation of Associated STA Link Metrics Response messages caused by measurement noise.
当Multi-AP代理为了计算估计的MAC数据速率和用于STA度量报告的上行链路RCPI而测量RCPI或SNR值时，可以使用特定于实现的平滑函数并以时间平均这些值。当配置了非零STA度量报告RCPI阈值时，Multi-AP代理应该对上行链路RCPI测量执行足够的平滑处理，以避免由测量噪声引起的相关STA链路度量响应消息的过度生成。
If a Multi-AP Agent sends an Associated STA Link Metrics TLV, it shall set the values of the Estimated MAC Data Rate metrics for downlink and uplink of the associated link based on the most recently measured uplink and downlink RCPI or SNR values. The Estimated MAC Data Rate metric is an estimate of the MAC layer throughput achievable on the link if 100% of channel air time and BSS operating bandwidth were to be available. The algorithm used by the Multi-AP Agent to calculate the Estimated MAC Data Rate metrics is implementation-specific. A reference method2 is defined in Annex R.7 of [1], which takes RCPI or SNR as inputs, and where with respect to Equation R-1,
如果Multi-AP代理发送关联的STA链路度量TLV，则它应基于最近测量的上行链路和下行链路RCPI或SNR值来设置相关链路的下行链路和上行链路的估计MAC数据速率度量的值。估计的MAC数据速率指标是链路上可实现的MAC层吞吐量的估计（100%的信道广播时间和BSS操作带宽可用）。Multi-AP代理用于计算估计的MAC数据速率度量的算法是特定于实现的。参考方法2在[1]的附录R.7中定义，该方法将RCPI或SNR作为输入，其中关于方程式R-1，
Multi-AP Specification下载地址:https://www.wi-fi.org/download.php?file=/sites/default/files/private/Mult ... Multi-AP Specification下载地址:https://www.wi-fi.org/download.php?file=/sites/default/files/private/Mult ... Multi-AP Specification下载地址:https://www.wi-fi.org/download.php?file=/sites/default/files/private/Mult ... 内容很多摘自 Aman JIANG(江超宇)翻译的Box2D v2.0.1 用户手册 第10章 世界(World Class) 关于 b2World类包含物体和关节.它管理着模拟的方方面面,并允许异步 ... 原文地址:http://blog.csdn.net/complex_ok/article/details/6719936 [-] 内容很多摘自 Aman JIANG(江超宇)翻译的Box2D v2.0 ... 谁有cmmi v2.0中文版本的下载地址,分享一下,谢谢 欢迎使用Markdown编辑器 你好! 这是你第一次使用 Markdown编辑器 所展示的欢迎页.如果你想学习如何使用Markdown编辑器, ... 内容很多摘自 Aman JIANG(江超宇)翻译的Box2D v2.0.1 用户手册 第09章 接触(Contacts) 9.1 关于 接触(contact)是由 Box2D 创建的用于管理fixtu ... 内容很多摘自 Aman JIANG(江超宇)翻译的Box2D v2.0.1 用户手册 第02章 Hello Box2D Box2D的发布包中有个Hello World程序.程序创建了一个大大的地面盒( ... 内容很多摘自 Aman JIANG(江超宇)翻译的Box2D v2.0.1 用户手册 第08章 关节(Joints) 8.1 关于 关节用于把物体约束到世界,或约束到其它物体上.在游戏中, 典型例子有 ...Multi-AP Specification V2.0 中文翻译 第10章 Link metric collection（链路度量采集）相关推荐
最新文章
热门文章