Network Working Group P. Newman, Nokia
Request for Comments: 2297 W. Edwards, Sprint
Updates: 1987 R. Hinden, Nokia
Category: Informational E. Hoffman, Nokia
F. Ching Liaw
T. Lyon, Nokia
G. Minshall, Fiberlane
March 1998
Network Working Group P. Newman, Nokia
Request for Comments: 2297 W. Edwards, Sprint
Updates: 1987 R. Hinden, Nokia
Category: Informational E. Hoffman, Nokia
F. Ching Liaw
T. Lyon, Nokia
G. Minshall, Fiberlane
March 1998
Ipsilon's General Switch Management Protocol Specification Version 2.0
Ipsilon的通用交换机管理协议规范版本2.0
Status of this Memo
本备忘录的状况
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (1998). All Rights Reserved.
版权所有（C）互联网协会（1998年）。版权所有。
Abstract
摘要
This memo specifies enhancements to the General Switch Management
Protocol (GSMP) [RFC1987]. The major enhancement is the addition of
Quality of Service (QoS) messages. Other improvements have been made
to the protocol resulting from operational experience. GSMP is a
general purpose protocol to control an ATM switch. It allows a
controller to establish and release connections across the switch;
add and delete leaves on a multicast connection; manage switch ports;
request configuration information; and request statistics.
This memo specifies enhancements to the General Switch Management
Protocol (GSMP) [RFC1987]. The major enhancement is the addition of
Quality of Service (QoS) messages. Other improvements have been made
to the protocol resulting from operational experience. GSMP is a
general purpose protocol to control an ATM switch. It allows a
controller to establish and release connections across the switch;
add and delete leaves on a multicast connection; manage switch ports;
request configuration information; and request statistics.
Table of Contents
目录
1. Introduction....................................................3
1. Introduction....................................................3
2. GSMP Packet Encapsulation.......................................4
2.1 ATM Encapsulation...........................................4
2.2 Ethernet Encapsulation......................................6
2. GSMP Packet Encapsulation.......................................4
2.1 ATM Encapsulation...........................................4
2.2 Ethernet Encapsulation......................................6
3. Common Definitions and Procedures...............................7
3.1 GSMP Packet Format..........................................8
3.2 Failure Response Messages..................................11
3. Common Definitions and Procedures...............................7
3.1 GSMP Packet Format..........................................8
3.2 Failure Response Messages..................................11
4. Connection Management Messages.................................16
4.1 Add Branch Message.........................................21
4.2 Delete Tree Message........................................23
4.3 Verify Tree Message........................................24
4.4 Delete All Message.........................................24
4.5 Delete Branches Message....................................25
4.6 Move Branch Message........................................27
4. Connection Management Messages.................................16
4.1 Add Branch Message.........................................21
4.2 Delete Tree Message........................................23
4.3 Verify Tree Message........................................24
4.4 Delete All Message.........................................24
4.5 Delete Branches Message....................................25
4.6 Move Branch Message........................................27
5. Port Management Messages.......................................29
5.1 Port Management Message....................................29
5.2 Label Range Message........................................34
5. Port Management Messages.......................................29
5.1 Port Management Message....................................29
5.2 Label Range Message........................................34
6. State and Statistics Messages..................................37
6.1 Connection Activity Message................................38
6.2 Statistics Messages........................................40
6.2.1 Port Statistics Message..............................44
6.2.2 Connection Statistics Message........................44
6.2.3 QoS Class Statistics Message.........................44
6.3 Report Connection State Message............................45
6. State and Statistics Messages..................................37
6.1 Connection Activity Message................................38
6.2 Statistics Messages........................................40
6.2.1 Port Statistics Message..............................44
6.2.2 Connection Statistics Message........................44
6.2.3 QoS Class Statistics Message.........................44
6.3 Report Connection State Message............................45
7. Configuration Messages.........................................49
7.1 Switch Configuration Message...............................50
7.2 Port Configuration Message.................................51
7.3 All Ports Configuration Message............................57
7. Configuration Messages.........................................49
7.1 Switch Configuration Message...............................50
7.2 Port Configuration Message.................................51
7.3 All Ports Configuration Message............................57
8. Event Messages.................................................59
8.1 Port Up Message............................................60
8.2 Port Down Message..........................................60
8.3 Invalid VPI/VCI Message....................................61
8.4 New Port Message...........................................61
8.5 Dead Port Message..........................................61
8. Event Messages.................................................59
8.1 Port Up Message............................................60
8.2 Port Down Message..........................................60
8.3 Invalid VPI/VCI Message....................................61
8.4 New Port Message...........................................61
8.5 Dead Port Message..........................................61
9. Quality of Service Messages....................................61
9.1 Abstract Switch Model......................................62
9.2 QoS Configuration Message..................................66
9.3 Scheduler Establishment Message............................74
9. Quality of Service Messages....................................61
9.1 Abstract Switch Model......................................62
9.2 QoS Configuration Message..................................66
9.3 Scheduler Establishment Message............................74
9.4 QoS Class Establishment Message............................78
9.5 QoS Release Message........................................85
9.6 QoS Connection Management Message..........................86
9.7 QoS Failure Response Codes.................................97
9.4 QoS Class Establishment Message............................78
9.5 QoS Release Message........................................85
9.6 QoS Connection Management Message..........................86
9.7 QoS Failure Response Codes.................................97
10. Adjacency Protocol............................................97
10.1 Packet Format.............................................98
10.2 Procedure.................................................101
10.3 Loss of Synchronization...................................103
10. Adjacency Protocol............................................97
10.1 Packet Format.............................................98
10.2 Procedure.................................................101
10.3 Loss of Synchronization...................................103
11. Summary of Failure Response Codes.............................104
11. Summary of Failure Response Codes.............................104
12. Summary of Message Set........................................105
12. Summary of Message Set........................................105
References........................................................107
Security Considerations...........................................107
Authors' Addresses................................................107
Full Copyright Statement..........................................109
References........................................................107
Security Considerations...........................................107
Authors' Addresses................................................107
Full Copyright Statement..........................................109
The General Switch Management Protocol (GSMP), is a general purpose protocol to control an ATM switch. GSMP allows a controller to establish and release connections across the switch; add and delete leaves on a multicast connection; manage switch ports; request configuration information; and request statistics. It also allows the switch to inform the controller of asynchronous events such as a link going down. GSMP runs across an ATM link connecting the controller to the switch, on a control connection (virtual channel) established at initialization. GSMP operation across an Ethernet link is also specified. The GSMP protocol is asymmetric, the controller being the master and the switch being the slave. Multiple switches may be controlled by a single controller using multiple instantiations of the protocol over separate control connections.
通用交换机管理协议（GSMP）是控制ATM交换机的通用协议。GSMP允许控制器通过交换机建立和释放连接；在多播连接上添加和删除叶子；管理交换机端口；请求配置信息；并要求提供统计数据。它还允许交换机通知控制器异步事件，例如链路断开。GSMP在初始化时建立的控制连接（虚拟通道）上，通过将控制器连接到交换机的ATM链路运行。还指定了通过以太网链路的GSMP操作。GSMP协议是非对称的，控制器是主设备，交换机是从设备。多个交换机可以由单个控制器通过单独的控制连接使用协议的多个实例化来控制。
A switch is assumed to contain multiple "ports". Each port is a combination of one "input port" and one "output port". Some GSMP requests refer to the port as a whole whereas other requests are specific to the input port or the output port. ATM cells arrive at the switch from an external communication link on incoming virtual paths or virtual channels at an input port. ATM cells depart from the switch to an external communication link on outgoing virtual paths or virtual channels from an output port. Virtual paths on a port or link are referenced by their virtual path identifier (VPI). Virtual channels on a port or link are referenced by their virtual path and virtual channel identifiers (VPI/VCI).
假定交换机包含多个“端口”。每个端口是一个“输入端口”和一个“输出端口”的组合。一些GSMP请求将端口作为一个整体引用，而其他请求则特定于输入端口或输出端口。ATM信元从输入端口的输入虚拟路径或虚拟通道上的外部通信链路到达交换机。ATM信元从交换机离开到输出端口的输出虚拟路径或虚拟通道上的外部通信链路。端口或链路上的虚拟路径由其虚拟路径标识符（VPI）引用。端口或链路上的虚拟通道由其虚拟路径和虚拟通道标识符（VPI/VCI）引用。
A virtual channel connection across a switch is formed by connecting an incoming virtual channel to one or more outgoing virtual channels. Virtual channel connections are referenced by the input port on which they arrive and the virtual path and virtual channel identifiers (VPI/VCI) of their incoming virtual channel. A virtual path connection across a switch is formed by connecting an incoming virtual path to one or more outgoing virtual paths. Virtual path connections are referenced by the input port on which they arrive and their virtual path identifier (VPI). In a virtual path connection the value of the VCI in each cell on that, connection is not used by the switch and remains unchanged by the switch.
通过将传入虚拟通道连接到一个或多个传出虚拟通道，形成交换机上的虚拟通道连接。虚拟通道连接由它们到达的输入端口及其传入虚拟通道的虚拟路径和虚拟通道标识符（VPI/VCI）引用。通过将传入虚拟路径连接到一个或多个传出虚拟路径，可以形成交换机上的虚拟路径连接。虚拟路径连接由它们到达的输入端口及其虚拟路径标识符（VPI）引用。在虚拟路径连接中，该连接上每个单元的VCI值不被交换机使用，交换机保持不变。
GSMP supports point-to-point and point-to-multipoint connections. A multipoint-to-point connection is specified by establishing multiple point-to-point connections each of them specifying the same output branch. A multipoint-to-multipoint connection is specified by establishing multiple point-to-multipoint trees each of them specifying the same output branches.
GSMP支持点对点和点对多点连接。多点对点连接是通过建立多个点对点连接来指定的，每个点对点连接指定相同的输出分支。多点到多点连接是通过建立多个点到多点树来指定的，每个树指定相同的输出分支。
In general a virtual channel is established with a certain quality of service (QoS). A rich set of QoS messages is introduced in this version of the protocol. However, implementation or operation of GSMP without any of the messages defined in Section 9, "Quality of service messages," is permitted. In this case each virtual channel connection or virtual path connection may be assigned a priority when it is established. It may be assumed that for virtual connections that share the same output port, an ATM cell on a connection with a higher priority is much more likely to exit the switch before an ATM cell on a connection with a lower priority if they are both in the switch at the same time. The number of priorities that each port of the switch supports may be obtained from the port configuration message.
一般来说，虚拟信道是以一定的服务质量（QoS）建立的。此版本的协议中引入了一组丰富的QoS消息。但是，允许在没有第9节“服务质量消息”中定义的任何消息的情况下实施或运行GSMP。在这种情况下，当建立每个虚拟通道连接或虚拟路径连接时，可以为其分配优先级。可以假设，对于共享同一输出端口的虚拟连接，如果高优先级连接上的ATM信元同时位于交换机中，则高优先级连接上的ATM信元更有可能在低优先级连接上的ATM信元之前退出交换机。交换机的每个端口支持的优先级数量可以从端口配置消息中获得。
GSMP contains an adjacency protocol. The adjacency protocol is used to synchronize state across the link, to negotiate which version of the GSMP protocol to use, to discover the identity of the entity at the other end of a link, and to detect when it changes.
GSMP包含一个邻接协议。邻接协议用于同步链路上的状态，协商使用哪个版本的GSMP协议，发现链路另一端实体的身份，并检测其何时更改。
GSMP packets are variable length and for an ATM data link layer they are encapsulated directly in an AAL-5 CPCS-PDU [I.363] with an LLC/SNAP header as illustrated:
GSMP数据包长度可变，对于ATM数据链路层，它们直接封装在AAL-5 CPCS-PDU[I.363]中，带有LLC/SNAP报头，如图所示：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LLC (0xAA-AA-03) | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| SNAP (0x00-00-00-88-0C) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ GSMP Message ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Pad (0 - 47 octets) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ AAL-5 CPCS-PDU Trailer (8 octets) +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LLC (0xAA-AA-03) | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| SNAP (0x00-00-00-88-0C) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ GSMP Message ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Pad (0 - 47 octets) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ AAL-5 CPCS-PDU Trailer (8 octets) +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
(The convention in the documentation of Internet Protocols [RFC1700] is to express numbers in decimal. Numbers in hexadecimal format are specified by prefacing them with the characters "0x". Data is pictured in "big-endian" order. That is, fields are described left to right, with the most significant octet on the left and the least significant octet on the right. Whenever a diagram shows a group of octets, the order of transmission of those octets is the normal order in which they are read in English. Whenever an octet represents a numeric quantity the left most bit in the diagram is the high order or most significant bit. That is, the bit labeled 0 is the most significant bit. Similarly, whenever a multi-octet field represents a numeric quantity the left most bit of the whole field is the most significant bit. When a multi-octet quantity is transmitted, the most significant octet is transmitted first. This is the same coding convention as is used in the ATM layer [I.361] and AAL-5 [I.363].)
（互联网协议文档[RFC1700]中的惯例是用十进制表示数字。十六进制格式的数字是通过在前面加上字符“0x”来指定的。数据以“big-endian”表示。）顺序。也就是说，字段是从左到右描述的，最重要的八位字节在左边，最不重要的八位字节在右边。每当图表显示一组八位字节时，这些八位字节的传输顺序是它们在英语中读取的正常顺序。每当八位字节表示数字量时，最左边的位在图中是高阶或最高有效位。也就是说，标记为0的位是最高有效位。类似地，每当一个多八位组字段表示一个数字量时，整个字段最左边的位是最高有效位。当传输一个多八位组量时，首先传输最高有效的八位组。这与ATM层[I.361]和AAL-5[I.363]中使用的编码约定相同。）
The LLC/SNAP header contains the octets: 0xAA 0xAA 0x03 0x00 0x00 0x00 0x88 0x0C. (0x880C is the assigned Ethertype for GSMP.)
LLC/SNAP头包含八位字节：0xAA 0xAA 0x03 0x00 0x00 0x00 0x00 0x88 0x0C。（0x880C是为GSMP分配的以太网类型。）
The maximum transmission unit (MTU) of the GSMP Message field is 1492 octets.
GSMP消息字段的最大传输单元（MTU）为1492个八位字节。
The virtual channel over which a GSMP session is established between a controller and the switch it is controlling is called the GSMP control channel. The default VPI and VCI of the GSMP control channel for LLC/SNAP encapsulated GSMP messages on an ATM data link layer is:
在控制器与其控制的交换机之间建立GSMP会话的虚拟通道称为GSMP控制通道。ATM数据链路层上LLC/SNAP封装GSMP消息的GSMP控制通道的默认VPI和VCI为：
VPI = 0 VCI = 15.
VPI=0，VCI=15。
GSMP packets may be encapsulated on an Ethernet data link as illustrated:
GSMP数据包可以封装在以太网数据链路上，如图所示：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Address |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| Source Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Ethertype (0x88-0C) | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| |
~ GSMP Message ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sender Instance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Receiver Instance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Pad |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Frame Check Sequence |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Address |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| Source Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Ethertype (0x88-0C) | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| |
~ GSMP Message ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sender Instance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Receiver Instance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Pad |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Frame Check Sequence |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Destination Address For the SYN message of the adjacency protocol the Destination Address is the broadcast address 0xFFFFFFFFFFFF. (Alternatively, it is also valid to configure the node with the unicast 48-bit IEEE MAC address of the destination. In this case the configured unicast Destination Address is used in the SYN message.) For all other messages the Destination Address is the unicast 48- bit IEEE MAC address of the destination. This address may be discovered from the Source Address field of messages received during synchronization of the adjacency protocol.
邻接协议SYN消息的目标地址目标地址是广播地址0xFFFFFFFFFF。（或者，使用目标的单播48位IEEE MAC地址配置节点也是有效的。在这种情况下，配置的单播目标地址用于SYN消息。）对于所有其他消息，目标地址是目标的单播48位IEEE MAC地址。该地址可以从邻接协议同步期间接收的消息的源地址字段中发现。
Source Address For all messages the Source Address is the 48-bit IEEE MAC address of the sender.
所有消息的源地址源地址是发送方的48位IEEE MAC地址。
Ethertype The assigned Ethertype for GSMP is 0x880C.
Ethertype为GSMP分配的Ethertype为0x880C。
GSMP Message The maximum transmission unit (MTU) of the GSMP Message field is 1492 octets.
GSMP消息GSMP消息字段的最大传输单位（MTU）为1492个八位字节。
Sender Instance The Sender Instance number for the link obtained from the adjacency protocol. This field is already present in the adjacency protocol message. It is appended to all non-adjacency GSMP messages in the Ethernet encapsulation to offer additional protection against the introduction of corrupt state.
Sender Instance从邻接协议获得的链路的发送方实例号。此字段已存在于邻接协议消息中。它附加到以太网封装中的所有非邻接GSMP消息中，以提供额外的保护，防止引入损坏状态。
Receiver Instance The Receiver Instance number is what the sender believes is the current instance number for the link, allocated by the entity at the far end of the link. This field is already present in the adjacency protocol message. It is appended to all non-adjacency GSMP messages in the Ethernet encapsulation to offer additional protection against the introduction of corrupt state.
接收方实例接收方实例号发送方认为是链路的当前实例号，由链路远端的实体分配。此字段已存在于邻接协议消息中。它附加到以太网封装中的所有非邻接GSMP消息中，以提供额外的保护，防止引入损坏状态。
Pad The minimum length of the data field of an Ethernet packet is 46 octets. If necessary, padding should be added such that it meets the minimum Ethernet frame size. This padding should be octets of zero and it is not considered to be part of the GSMP message.
Pad以太网数据包数据字段的最小长度为46个八位字节。如有必要，应添加填充，使其满足最小以太网帧大小。此填充应为零的八位字节，并且不被视为GSMP消息的一部分。
After the adjacency protocol has achieved synchronization, for every GSMP message received with an Ethernet encapsulation, the receiver must check the Source Address from the Ethernet MAC header, the Sender Instance, and the Receiver Instance. The incoming GSMP message must be discarded if the Sender Instance and the Source Address do not match the values of Sender Instance and Sender Name stored by the "Update Peer Verifier" operation of the GSMP adjacency protocol. The incoming GSMP message must also be discarded if it arrives over any port other than the port over which the adjacency protocol has achieved synchronization. In addition, the incoming message must also be discarded if the Receiver Instance field does not match the current value for the Sender Instance of the GSMP adjacency protocol.
邻接协议实现同步后，对于通过以太网封装接收的每个GSMP消息，接收器必须检查来自以太网MAC头、发送方实例和接收器实例的源地址。如果发送方实例和源地址与GSMP邻接协议的“更新对等验证程序”操作存储的发送方实例和发送方名称的值不匹配，则必须丢弃传入的GSMP消息。如果传入的GSMP消息通过邻接协议已实现同步的端口以外的任何端口到达，则也必须丢弃该消息。此外，如果接收方实例字段与GSMP邻接协议的发送方实例的当前值不匹配，则也必须丢弃传入消息。
GSMP is a master-slave protocol. The controller issues request messages to the switch. Each request message indicates whether a response is required from the switch and contains a transaction
GSMP是一种主从协议。控制器向交换机发出请求消息。每个请求消息指示是否需要来自交换机的响应，并包含一个事务
identifier to enable the response to be associated with the request. The switch replies with a response message indicating either a successful result or a failure. There are five classes of GSMP request-response message: Connection Management, Port Management, State and Statistics, Configuration, and Quality of Service. The switch may also generate asynchronous Event messages to inform the controller of asynchronous events. Event messages are not acknowledged by the controller. There is also an adjacency protocol message used to establish synchronization across the link and maintain a handshake.
标识符，以使响应与请求关联。交换机会回复一条响应消息，指示结果成功或失败。GSMP请求-响应消息有五类：连接管理、端口管理、状态和统计、配置和服务质量。交换机还可以生成异步事件消息，以通知控制器异步事件。控制器不确认事件消息。还有一个邻接协议消息，用于在链路上建立同步并保持握手。
For the request-response messages, each message type has a format for the request message and a format for the success response. Unless otherwise specified a failure response message is identical to the request message that caused the failure, with the Code field indicating the nature of the failure. Event messages have only a single format defined as they are not acknowledged by the controller.
对于请求-响应消息，每种消息类型都有请求消息格式和成功响应格式。除非另有规定，否则故障响应消息与导致故障的请求消息相同，代码字段指示故障的性质。事件消息只有一种定义的格式，因为它们未被控制器确认。
Switch ports are described by a 32-bit port number. The switch assigns port numbers and it may typically choose to structure the 32 bits into subfields that have meaning to the physical structure of the switch (e.g. slot, port). In general, a port in the same physical location on the switch will always have the same port number, even across power cycles. The internal structure of the port number is opaque to the GSMP protocol. However, for the purposes of network management such as logging, port naming, and graphical representation, a switch may declare the physical location (physical slot and port) of each port. Alternatively, this information may be obtained by looking up the product identity in a database.
交换机端口由32位端口号描述。交换机分配端口号，并且通常可以选择将32位构造为对交换机的物理结构有意义的子字段（例如插槽、端口）。一般来说，交换机上相同物理位置的端口将始终具有相同的端口号，即使在整个电源循环中也是如此。端口号的内部结构对GSMP协议是不透明的。但是，出于网络管理（如日志记录、端口命名和图形表示）的目的，交换机可以声明每个端口的物理位置（物理插槽和端口）。或者，可以通过在数据库中查找产品标识来获得该信息。
Each switch port also maintains a port session number assigned by the switch. A message, with an incorrect port session number must be rejected. This allows the controller to detect a link failure and to keep state synchronized.
每个交换机端口还维护交换机分配的端口会话号。必须拒绝端口会话号不正确的消息。这允许控制器检测链路故障并保持状态同步。
Except for the adjacency protocol message, no GSMP messages may be sent across the link until the adjacency protocol has achieved synchronization, and all GSMP messages received on a link that does not currently have state synchronization must be discarded.
除邻接协议消息外，在邻接协议实现同步之前，不得通过链路发送任何GSMP消息，并且必须丢弃在当前没有状态同步的链路上接收的所有GSMP消息。
All GSMP messages, except the adjacency protocol message, have the following format:
除邻接协议消息外，所有GSMP消息的格式如下：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Message Body ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Message Body ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Version The version number of the GSMP protocol being used in this session. It should be set by the sender of the message to the GSMP protocol version negotiated by the adjacency protocol.
Version此会话中使用的GSMP协议的版本号。它应该由消息的发送者设置为通过邻接协议协商的GSMP协议版本。
Message Type The GSMP message type. GSMP messages fall into six classes: Connection Management, Port Management, State and Statistics, Configuration, Quality of Service, and Events. Each class has a number of different message types. In addition, one Message Type is allocated to the adjacency protocol.
消息类型GSMP消息类型。GSMP消息分为六类：连接管理、端口管理、状态和统计、配置、服务质量和事件。每个类都有许多不同的消息类型。此外，一种消息类型被分配给邻接协议。
Result Field in a Connection Management request message, a Port Management request message, or a Quality of Service request message is used to indicate whether a response is required to the request message if the outcome is successful. A value of "NoSuccessAck" indicates that the request message does not expect a response if the outcome is successful, and a value of "AckAll" indicates that a response is expected if the outcome is successful. In both cases a failure response must be generated if the request fails. For Sate and Statistics, and Configuration request messages, a value of "NoSuccessAck" in the request message is ignored and the request message is handled as if the field were set to "AckAll". (This facility was added to reduce the control traffic in the case where the controller periodically checks that the state in the switch is correct. If the controller does not use this capability, all request messages should be sent with a value of "AckAll.")
连接管理请求消息、端口管理请求消息或服务质量请求消息中的结果字段用于指示如果结果成功，是否需要响应请求消息。值“NoSuccessAck”表示如果结果成功，请求消息不期望响应，“AckAll”表示如果结果成功，则期望响应。在这两种情况下，如果请求失败，则必须生成失败响应。对于状态和统计信息以及配置请求消息，请求消息中的“NoSuccessAck”值将被忽略，请求消息的处理方式与字段设置为“AckAll”的处理方式相同。（添加此功能是为了在控制器定期检查交换机中的状态是否正确的情况下减少控制流量。如果控制器不使用此功能，则所有请求消息都应以“AckAll”值发送。）
In a response message the result field can have three values: "Success," "More," and "Failure". The "Success" and "More" results both indicate a success response. The "More" result indicates that the success response exceeds the maximum transmission unit of the data link and that one or more further messages will be sent to complete the success response. All messages that belong to the same success response will have the same Transaction Identifier. The "Success" result indicates a success response that may be contained in a single message or the final message of a success response spanning multiple messages.
在响应消息中，结果字段可以有三个值：“成功”、“更多”和“失败”。“成功”和“更多”结果都表明反应成功。“更多”结果表示成功响应超过了数据链路的最大传输单位，并且将发送一条或多条进一步的消息以完成成功响应。属于同一成功响应的所有消息将具有相同的事务标识符。“Success”结果表示可能包含在单个消息中的成功响应，或跨多个消息的成功响应的最终消息。
The encoding of the result field is:
结果字段的编码为：
NoSuccessAck: Result = 1 AckAll: Result = 2 Success: Result = 3 Failure: Result = 4 More: Result = 5.
NoSuccessAck:Result=1确认：结果=2成功：结果=3失败：结果=4更多：结果=5。
The Result field is not used in an adjacency protocol message.
结果字段未在邻接协议消息中使用。
Code Field gives further information concerning the result in a response message. It is mostly used to pass an error code in a failure response but can also be used to give further information in a success response message or an event message. In a request message the code field is not used and is set to zero. In an adjacency protocol message the Code field is used to determine the function of the message.
代码字段提供有关响应消息中结果的更多信息。它主要用于在故障响应中传递错误代码，但也可用于在成功响应消息或事件消息中提供更多信息。在请求消息中，不使用代码字段，并将其设置为零。在邻接协议消息中，代码字段用于确定消息的功能。
Transaction Identifier Used to associate a request message with its response message. For request messages the controller may select any transaction identifier. For response messages the transaction identifier is set to the value of the transaction identifier from the message to which it is a response. For event messages the transaction identifier should be set to zero. The Transaction Identifier is not used, and the field is not present, in the adjacency protocol.
用于将请求消息与其响应消息关联的事务标识符。对于请求消息，控制器可以选择任何事务标识符。对于响应消息，事务标识符设置为作为响应的消息的事务标识符的值。对于事件消息，事务标识符应设置为零。邻接协议中未使用事务标识符，且字段不存在。
The following fields are frequently found in GSMP messages. They are defined here to avoid repetition.
以下字段经常出现在GSMP消息中。在这里定义它们是为了避免重复。
Port Gives the port number of the switch port to which the message applies.
Port提供消息应用到的交换机端口的端口号。
Port Session Number Each switch port maintains a Port Session Number assigned by the switch. The port session number of a port remains unchanged while the port is continuously in the Available state and the link status is continuously Up. When a port returns to the Available state after it has been Unavailable or in any of the Loopback states, or when the line status returns to the Up state after it has been Down or in Test, or after a power cycle, a new Port Session Number must be generated. Port session numbers should be assigned using some form of random number.
端口会话号每个交换机端口维护交换机分配的端口会话号。当端口持续处于可用状态且链路状态持续打开时，端口的端口会话号保持不变。当端口在不可用或处于任何环回状态后返回到可用状态，或当线路状态在关闭或测试后或在电源循环后返回到向上状态时，必须生成新的端口会话号。端口会话号应使用某种形式的随机数进行分配。
If the Port Session Number in a request message does not match the current Port Session Number for the specified port, a failure response message must be returned with the Code field indicating, "Invalid port session number." The current port session number for a port may be obtained using a Port Configuration or an All Ports Configuration message.
如果请求消息中的端口会话号与指定端口的当前端口会话号不匹配，则必须返回故障响应消息，其中代码字段指示“无效端口会话号”可以使用端口配置或所有端口配置消息获取端口的当前端口会话号。
Any field in a GSMP message that is unused or defined as "reserved" must be set to zero by the sender and ignored by the receiver.
GSMP消息中未使用或定义为“保留”的任何字段必须由发送方设置为零，并由接收方忽略。
It is not an error for a GSMP message to contain additional data after the end of the Message Body. This is to support development and experimental purposes. However, the maximum transmission unit of the GSMP message, as defined by the data link layer encapsulation, must not be exceeded.
GSMP消息在消息正文结束后包含附加数据不是错误。这是为了支持开发和实验目的。但是，不得超过数据链路层封装定义的GSMP消息的最大传输单位。
A success response message must not be sent until the requested operation has been successfully completed.
在请求的操作成功完成之前，不得发送成功响应消息。
A failure response message is formed by returning the request message that caused the failure with the Result field in the header indicating failure (Result = 4) and the Code field giving the failure code. The failure code specifies the reason for the switch being unable to satisfy the request message.
通过返回导致故障的请求消息形成故障响应消息，报头中的结果字段指示故障（结果=4），代码字段给出故障代码。故障代码指定交换机无法满足请求消息的原因。
If the switch issues a failure response in reply to a request message, no change should be made to the state of the switch as a result of the message causing the failure. (For request messages that contain multiple requests, such as the Delete Branches message, the
如果交换机发出故障响应以响应请求消息，则不应因导致故障的消息而更改交换机的状态。（对于包含多个请求的请求消息，例如“删除分支”消息
failure response message will specify which requests were successful and which failed. The successful requests may result in changed state.)
失败响应消息将指定哪些请求成功，哪些请求失败。成功的请求可能会导致状态更改。）
If the switch issues a failure response it must choose the most specific failure code according to the following precedence:
如果交换机发出故障响应，则必须根据以下优先级选择最具体的故障代码：
Invalid Message
无效消息
Failure specific to the particular message type (failure code 16). (The meaning of this failure is dependent upon the particular message type and is specified in the text defining the message.)
特定于特定消息类型的故障（故障代码16）。（此故障的含义取决于特定的消息类型，并在定义消息的文本中指定。）
A failure response specified in the text defining the message type.
在定义消息类型的文本中指定的故障响应。
Connection Failures
连接故障
Virtual Path Connection Failures
虚拟路径连接失败
Multicast Failures
多播失败
QoS Failures (QoS failures are specified in Section 9.7.)
QoS故障（第9.7节规定了QoS故障。）
General Failures
一般故障
If multiple failures match in any of the following categories, the one that is listed first should be returned. The following failure response messages and failure codes are defined:
如果多个故障在以下任何类别中匹配，则应返回首先列出的故障。定义了以下故障响应消息和故障代码：
Invalid Message
无效消息
3: The specified request is not implemented on this switch. The Message Type field specifies a message that is not implemented on the switch or contains a value that is not defined in the version of the protocol running in this session of GSMP.
3:指定的请求未在此交换机上实现。Message Type（消息类型）字段指定未在交换机上实现的消息，或包含未在GSMP会话中运行的协议版本中定义的值。
5: One or more of the specified ports does not exist. At least one of the ports specified in the message is invalid. A port is invalid if it does not exist or if it has been removed from the switch.
5:一个或多个指定端口不存在。消息中指定的至少一个端口无效。如果端口不存在或已从交换机中删除，则该端口无效。
4: Invalid Port Session Number. The value given in the Port Session Number field does not match the current Port Session Number for the specified port.
4：端口会话号无效。端口会话号字段中给定的值与指定端口的当前端口会话号不匹配。
Connection Failures
连接故障
8: The specified connection does not exist. An operation that expects a connection to be specified, either a virtual channel or a virtual path connection, cannot locate the specified connection. A virtual channel connection is specified by the input port, input VPI, and input VCI on which it arrives. A virtual path connection is specified by the input port and input VPI on which it arrives.
8:指定的连接不存在。需要指定连接（虚拟通道或虚拟路径连接）的操作找不到指定的连接。虚拟通道连接由其到达的输入端口、输入VPI和输入VCI指定。虚拟路径连接由其到达的输入端口和输入VPI指定。
9: The specified branch does not exist. An operation that expects a branch of an existing connection to be specified, either a virtual channel or a virtual path connection, cannot locate the specified branch. A branch of a virtual channel connection is specified by the virtual channel connection it belongs to and the output port, output VPI, and output VCI on which it departs. A branch of a virtual path connection is specified by the virtual path connection it belongs to and the output port and output VPI on which it departs.
9:指定的分支不存在。期望指定现有连接的分支（虚拟通道或虚拟路径连接）的操作找不到指定的分支。虚拟通道连接的分支由其所属的虚拟通道连接及其离开的输出端口、输出VPI和输出VCI指定。虚拟路径连接的分支由其所属的虚拟路径连接及其离开的输出端口和输出VPI指定。
18: One or more of the specified input VPIs is invalid.
18:一个或多个指定的输入VPI无效。
19: One or more of the specified input VCIs is invalid.
19:一个或多个指定的输入VCI无效。
20: One or more of the specified output VPIs is invalid.
20:一个或多个指定的输出VPI无效。
21: One or more of the specified output VCIs is invalid.
21:一个或多个指定的输出VCI无效。
22: Invalid Class of Service field in a Connection Management message. The value of the Class of Service field is invalid.
22:连接管理消息中的服务类别字段无效。服务类别字段的值无效。
23: Insufficient resources for QoS Profile. The resources requested by the QoS Profile in the Class of service field are not available.
23:用于QoS配置文件的资源不足。服务类别字段中QoS配置文件请求的资源不可用。
Virtual Path Connections
虚拟路径连接
24: Virtual path switching is not supported on this input port.
24:此输入端口上不支持虚拟路径交换。
25: Point-to-multipoint virtual path connections are not supported on either the requested input port or the requested output port. One or both of the requested input and output ports is unable to support point-to-multipoint virtual path connections.
25:请求的输入端口或请求的输出端口均不支持点对多点虚拟路径连接。请求的一个或两个输入和输出端口无法支持点到多点虚拟路径连接。
26: Attempt to add a virtual path connection branch to an existing virtual channel connection. It is invalid to mix branches switched as virtual channel connections with branches switched as virtual path connections on the same point-to-multipoint connection.
26:尝试将虚拟路径连接分支添加到现有虚拟通道连接。在同一点对多点连接上，将作为虚拟通道连接交换的分支与作为虚拟路径连接交换的分支混合使用是无效的。
27: Attempt to add a virtual channel connection branch to an existing virtual path connection. It is invalid to mix branches switched as virtual channel connections with branches switched as virtual path connections on the same point-to-multipoint connection.
27:尝试将虚拟通道连接分支添加到现有虚拟路径连接。在同一点对多点连接上，将作为虚拟通道连接交换的分支与作为虚拟路径连接交换的分支混合使用是无效的。
Multicast Failures
多播失败
10: A branch belonging to the specified point-to-multipoint connection is already established on the specified output port and the switch cannot support more than a single branch of any point-to-multipoint connection on the same output port.
10:已在指定的输出端口上建立了属于指定的点对多点连接的分支，并且交换机不能在同一输出端口上支持任何点对多点连接的多个分支。
11: The limit on the maximum number of point-to-multipoint connections that the switch can support has been reached.
11：已达到交换机可支持的最大点对多点连接数限制。
12: The limit on the maximum number of branches that the specified point-to-multipoint connection can support has been reached.
12:已达到指定点对多点连接可支持的最大分支数限制。
17: Cannot label each output branch of a point-to-multipoint tree with a different label. Some early designs, and some low-cost ATM switch designs, require all output branches of a multicast connection to use the same value of VPI/VCI.
17:无法使用不同的标签标记点对多点树的每个输出分支。一些早期设计和一些低成本ATM交换机设计要求多播连接的所有输出分支使用相同的VPI/VCI值。
28: Only point-to-point bidirectional connections may be established. It is an error to attempt to add an additional output branch to an existing connection with the bidirectional flag set.
28：只能建立点对点双向连接。尝试使用双向标志集向现有连接添加额外的输出分支是错误的。
13: Unable to assign the requested VPI/VCI value to the requested branch on the specified point-to-multipoint connection. Although the requested VPI and VCI are valid, the switch is unable to support the request using the specified values of VPI and VCI for some reason not covered by the above failure responses. This message implies that a valid value of VPI or VCI exists that the switch could
13:无法在指定的点对多点连接上将请求的VPI/VCI值分配给请求的分支。尽管请求的VPI和VCI有效，但由于上述故障响应未涵盖的某些原因，交换机无法使用指定的VPI和VCI值支持请求。此消息表示存在有效的VPI或VCI值，交换机可以
support. For example, some switch designs restrict the number of distinct VPI/VCI values available to a point-to-multipoint connection. (Most switch designs will not require this message.)
支持例如，某些交换机设计限制点对多点连接可用的不同VPI/VCI值的数量。（大多数交换机设计不需要此消息。）
14: General problem related to the manner in which point-to-multipoint is supported by the switch. Use this message if none of the more specific multicast failure messages apply. (Most switch designs will not require this message.)
14：与交换机支持点对多点的方式有关的一般问题。如果没有更具体的多播失败消息应用，请使用此消息。（大多数交换机设计不需要此消息。）
General Failures
一般故障
2: Invalid request message. There is an error in one of the fields of the message not covered by a more specific failure message.
2：无效的请求消息。消息的一个字段中有一个错误未被更具体的故障消息覆盖。
6: One or more of the specified ports is down. A port is down if its Port Status is Unavailable. Connection Management, Connection State, Port Management, and Configuration operations are permitted on a port that is Unavailable. Connection Activity and Statistics operations are not permitted on a port that is Unavailable and will generate this failure response. A Port Management message specifying a Take Down function on a port already in the Unavailable state will also generate this failure response.
6:一个或多个指定端口关闭。如果端口状态不可用，则端口关闭。允许在不可用的端口上进行连接管理、连接状态、端口管理和配置操作。不允许在不可用且将生成此故障响应的端口上执行连接活动和统计操作。在已处于不可用状态的端口上指定取下功能的端口管理消息也将生成此故障响应。
15: Out of resources. The switch has exhausted a resource not covered by a more specific failure message, for example, running out of memory.
15：资源不足。交换机耗尽了未被更具体的故障消息覆盖的资源，例如，内存不足。
1: Unspecified reason not covered by other failure codes. The failure message of last resort.
1：其他故障代码未涵盖的未指定原因。最后的失败信息。
The following failure response messages are only used by the Label Range message.
以下故障响应消息仅由标签范围消息使用。
29: Cannot support requested VPI range.
29:无法支持请求的VPI范围。
30: Cannot support requested VCI range on all requested VPIs.
30:无法在所有请求的VPI上支持请求的VCI范围。
The following failure response messages are only used by the Set Transmit Cell Rate function of the Port Management message.
以下故障响应消息仅由端口管理消息的设置传输单元速率功能使用。
31: The transmit cell rate of this output port cannot be changed.
31:无法更改此输出端口的传输单元速率。
32: Requested transmit cell rate out of range for this output port.
32:请求的传输单元速率超出此输出端口的范围。
Connection management messages are used by the controller to establish, delete, modify and verify virtual channel connections and virtual path connections across the switch. The Add Branch, Delete Tree, and Delete All connection management messages have the following format for both request and response messages:
控制器使用连接管理消息来建立、删除、修改和验证交换机上的虚拟通道连接和虚拟路径连接。“添加分支”、“删除树”和“删除所有连接管理”消息的请求和响应消息格式如下：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|M|Q|B|C| Input VPI | Input VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x x x x| Output VPI | Output VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number of Branches | Class of Service |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|M|Q|B|C| Input VPI | Input VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x x x x| Output VPI | Output VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number of Branches | Class of Service |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Input Port Identifies a switch input port.
输入端口标识交换机输入端口。
Flags
旗帜
M: Multicast The Multicast flag is used as a hint for point-to-multipoint connections in the Add Branch message. It is not used in any other connection management messages and in these messages it should be set to zero. If set, it indicates that the virtual channel connection or the virtual path connection is very likely to be a point-to-multipoint connection. If zero, it indicates that this connection is very likely to be a point-to-point connection or is unknown.
M：多播多播标志在添加分支消息中用作点对多点连接的提示。它不用于任何其他连接管理消息中，在这些消息中，它应设置为零。如果设置，则表示虚拟通道连接或虚拟路径连接很可能是点对多点连接。如果为零，则表示此连接很可能是点对点连接或未知。
The Multicast flag is only used in the Add Branch message when establishing the first branch of a new connection. It is not required to be set when establishing subsequent branches of a point-to-multipoint connection and on such connections it should be ignored by the receiver. (On receipt of the second and subsequent Add Branch messages the receiver knows that this is a point-to-multipoint connection.) If it is known that this is the first branch of a point-to-multipoint connection this flag should be set. If it is unknown, or if it is known that the connection is point-to-point this flag should be zero. The use of this flag is not mandatory. It may be ignored by the switch. If unused the flag should be set to zero. Some switches use a different data structure for point-to-multipoint connections than for point-to-point connections. This flag avoids the switch setting up a point-to-point structure for the first branch of a point-to-multipoint connection which must immediately be deleted and reconfigured as point-to-multipoint when the second branch is established.
当建立新连接的第一个分支时，多播标志仅在添加分支消息中使用。在建立点对多点连接的后续分支时，不需要设置该值，在此类连接上，接收器应忽略该值。（在收到第二条和后续的Add分支消息时，接收方知道这是点对多点连接。）如果知道这是点对多点连接的第一条分支，则应设置此标志。如果未知，或者如果已知连接是点到点的，则此标志应为零。此标志的使用不是强制性的。该开关可能会忽略它。如果未使用，则标志应设置为零。有些交换机对点对多点连接使用与点对点连接不同的数据结构。此标志避免交换机为点对多点连接的第一个分支设置点对点结构，在建立第二个分支时，必须立即删除该分支并将其重新配置为点对多点。
Q: QoS Profile The QoS Profile flag, if set, indicates that the Class of Service field contains a QoS Profile Identifier. If this flag is zero, it indicates that the Class of Service field contains a Priority or a Scheduler Identifier.
Q:QoS配置文件QoS配置文件标志（如果设置）表示服务类别字段包含QoS配置文件标识符。如果此标志为零，则表示服务类别字段包含优先级或计划程序标识符。
B: Bidirectional The Bidirectional flag applies only to the Add Branch message. In all other Connection Management messages it is not used. It may only be used when establishing a point-to-point connection. The Bidirectional flag in an Add Branch message, if set, requests that two unidirectional virtual channels or virtual paths be established, one in the forward direction, and one in the reverse direction. It is equivalent to two Add Branch messages, one specifying the forward direction, and one specifying the reverse direction. The forward direction uses the values of Input Port, Input VPI, Input VCI, Output Port, Output VPI, and Output VCI as specified in the Add Branch message. The reverse direction is derived by exchanging the values specified in the Input Port, Input VPI, and Input VCI fields, with those of the Output Port, Output VPI, and Output VCI fields respectively. Thus, a virtual connection in the reverse direction arrives at the input port specified by the Output Port field, on the VPI/VCI specified by the Output VPI and Output VCI fields. It departs from the output port specified by the Input Port
B:双向-双向标志仅适用于添加分支消息。在所有其他连接管理消息中不使用它。它只能在建立点对点连接时使用。添加分支消息中的双向标志（如果设置）请求建立两个单向虚拟通道或虚拟路径，一个在正向，另一个在反向。它相当于两条添加分支消息，一条指定正向，另一条指定反向。正向使用添加分支消息中指定的输入端口、输入VPI、输入VCI、输出端口、输出VPI和输出VCI的值。通过将输入端口、输入VPI和输入VCI字段中指定的值分别与输出端口、输出VPI和输出VCI字段中的值进行交换，可以得出相反的方向。因此，反向虚拟连接到达输出端口字段指定的输入端口，位于输出VPI和输出VCI字段指定的VPI/VCI上。它偏离输入端口指定的输出端口
field, on the VPI/VCI specified by the Input VPI and Input VCI fields.
字段，位于输入VPI和输入VCI字段指定的VPI/VCI上。
The Bidirectional flag is simply a convenience to establish two unidirectional virtual connections in opposite directions between the same two ports, with identical VPI/VCIs, using a single Add Branch message. In all future messages the two unidirectional virtual connections must be handled separately. There is no bidirectional delete message. However, a single Delete Branches message with two Delete Branch Elements, one for the forward connection and one for the reverse, may be used.
双向标志只是为了方便在相同的两个端口之间，使用相同的VPI/VCI，使用单个Add分支消息在相反方向上建立两个单向虚拟连接。在将来的所有消息中，必须分别处理两个单向虚拟连接。没有双向删除消息。但是，可以使用带有两个删除分支元素的单个删除分支消息，一个用于正向连接，另一个用于反向连接。
C: Congestion Indication The Congestion Indication flag, if set, requests that cells on this connection be marked if congestion is experienced. If this connection passes through a queue that the switch considers to be congested, the Congestion Experienced bit will be set in the Payload Type field of the cell header of all cells on the connection. GSMP does not specify the algorithm or any threshold by which the switch decides when a queue is congested.
C：拥塞指示如果设置了拥塞指示标志，则请求在发生拥塞时标记此连接上的单元。如果此连接通过交换机认为拥塞的队列，则将在连接上所有小区的小区头的有效负载类型字段中设置经历拥塞的位。GSMP没有指定交换机决定队列何时拥塞的算法或阈值。
Input VPI Identifies an ATM virtual path arriving at the switch input port indicated by the Input Port field.
输入VPI标识到达输入端口字段指示的交换机输入端口的ATM虚拟路径。
Input VCI Identifies an ATM virtual channel arriving on the virtual path indicated by the Input VPI field at the switch input port indicated by the Input Port field. For virtual path connections the Input VCI field is not used.
输入VCI标识到达输入端口字段指示的交换机输入端口处的输入VPI字段指示的虚拟路径上的ATM虚拟通道。对于虚拟路径连接，不使用输入VCI字段。
Output Port Identifies a switch output port.
输出端口标识交换机输出端口。
x: Unused
x:未使用
Output VPI Identifies an outgoing virtual path departing from the switch output port indicated in the Output Port field.
Output VPI标识出一条离开Output port字段中指示的交换机输出端口的传出虚拟路径。
Output VCI Identifies an outgoing virtual channel departing on the virtual path indicated by the Output VPI field from the switch output port indicated in the Output Port field. For virtual path connections the Output VCI field is not used.
Output VCI标识输出虚拟通道，该通道在Output VPI字段指示的虚拟路径上离开Output port字段指示的交换机输出端口。对于虚拟路径连接，不使用输出VCI字段。
Number of Branches In a success response message and a failure response message, gives the number of output branches on a virtual channel connection or a virtual path connection after completion of the requested operation. (A point-to-point connection will have one branch, a point-to-multipoint connection will have two or more branches.) If the switch is unable to keep track of the number of branches on a virtual path connection or a virtual channel connection it must respond with the value 0xFFFF meaning: "number of branches unknown". This field is not used in the request message.
成功响应消息和失败响应消息中的分支数表示完成请求的操作后虚拟通道连接或虚拟路径连接上的输出分支数。（点对点连接将有一个分支，点对多点连接将有两个或多个分支。）如果交换机无法跟踪虚拟路径连接或虚拟通道连接上的分支数，则必须使用值0xFFFF进行响应，表示“分支数未知”。此字段未在请求消息中使用。
Class of Service This field can contain either a QoS Profile Identifier, a Priority, or a Scheduler Identifier. If the QoS Profile flag in the Flags field is set, the Class of Service field contains a QoS Profile. If the QoS Profile flag in the Flags field is zero, and the value of the Class of Service field is greater than or equal to 0x100, the Class of Service field contains a Scheduler Identifier. If the QoS Profile flag in the Flags field is zero, and the value of the Class of Service field is less than 0x100, the Class of Service field contains a Priority. (Values of Scheduler Identifier less than 0x100 are interpreted as priorities.) The Class of Service field is only used in the Add Branch and Move Branch messages.
服务类别此字段可以包含QoS配置文件标识符、优先级或调度程序标识符。如果在标志字段中设置了QoS配置文件标志，则服务类别字段包含QoS配置文件。如果标志字段中的QoS配置文件标志为零，且服务类别字段的值大于或等于0x100，则服务类别字段包含调度器标识符。如果标志字段中的QoS配置文件标志为零，且服务类别字段的值小于0x100，则服务类别字段包含优先级。（调度程序标识符小于0x100的值被解释为优先级。）服务类别字段仅在添加分支和移动分支消息中使用。
A QoS Profile Identifier is an opaque 16-bit value. It is used to identify a QoS profile in the switch which specifies the Quality of Service required by the connection. QoS profiles are established by a mechanism external to GSMP.
QoS配置文件标识符是不透明的16位值。它用于标识交换机中的QoS配置文件，该配置文件指定连接所需的服务质量。QoS配置文件由GSMP外部的机制建立。
A Scheduler Identifier is an alternative method of communicating the QoS requirements of a connection. The Scheduler Identifier is defined in Section 9, "Quality of Service Messages."
调度器标识符是传达连接的QoS要求的替代方法。调度器标识符在第9节“服务质量消息”中定义
A Priority specifies the priority of the connection for Add Branch and Move Branch messages that choose not to use a QoS profile, or the QoS capabilities defined in Section 9, "Quality of Service Messages." The highest priority is numbered zero and the lowest priority is numbered "Q-1" where "Q" is the number of priorities that the output port can support. The ability to offer different qualities of service to different connections based upon their priority is assumed to be a property of the output port of the
优先级指定选择不使用QoS配置文件的添加分支和移动分支消息的连接优先级，或第9节“服务质量消息”中定义的QoS功能。最高优先级编号为零，最低优先级编号为“Q-1”，其中“Q”输出端口可以支持的优先级数。根据优先级向不同连接提供不同服务质量的能力被假定为
switch. It is assumed that for virtual path connections or virtual channel connections that share the same output port, an ATM cell on a connection with a higher priority is much more likely to exit the switch before an ATM cell on a connection with a lower priority, if they are both in the switch at the same time. The number of priorities that each output port can support is given in the Port Configuration message.
转换假设对于共享同一输出端口的虚拟路径连接或虚拟通道连接，如果它们同时位于交换机中，则优先级较高的连接上的ATM信元更有可能在优先级较低的连接上的ATM信元之前退出交换机。端口配置消息中给出了每个输出端口可以支持的优先级数量。
For all connection management messages, except the Delete Branches message, the success response message is a copy of the request message returned with the Result field indicating success and the Number of Branches field indicating the number of branches on the connection after completion of the operation. The Code field is not used in a connection management success response message.
对于所有连接管理消息（删除分支消息除外），成功响应消息是返回的请求消息的副本，结果字段指示成功，分支数字段指示操作完成后连接上的分支数。连接管理成功响应消息中未使用代码字段。
The failure response message is a copy of the request message returned with a Result field indicating failure and the Number of Branches field indicating the number of branches on the connection.
故障响应消息是返回的请求消息的副本，返回的结果字段指示故障，分支数字段指示连接上的分支数。
Fundamentally, no distinction is made between point-to-point and point-to-multipoint connections. By default, the first Add Branch message for a particular Input Port, Input VPI, and Input VCI will establish a point-to-point virtual connection. The second Add Branch message with the same Input Port, Input VPI, and Input VCI fields will convert the connection to a point-to-multipoint virtual connection with two branches. (For virtual path connections the Input VCI is not required.) However, to avoid possible inefficiency with some switch designs, the Multicast Flag is provided. If the controller knows that a new connection is point-to-multipoint when establishing the first branch, it may indicate this in the Multicast Flag. Subsequent Add Branch messages with the same Input Port, Input VPI, and Input VCI fields will add further branches to the point-to-multipoint connection. Use of the Delete Branch message on a point-to-multipoint connection with two branches will result in a point-to-point connection. However, the switch may structure this connection as a point-to-multipoint connection with a single output branch if it chooses. (For some switch designs this structure may be more convenient.) Use of the Delete Branch message on a point-to-point connection will delete the point-to-point connection. There is no concept of a connection with zero output branches. All connections are unidirectional, one input virtual path or virtual channel to one or more output virtual paths or virtual channels.
基本上，点对点和点对多点连接之间没有区别。默认情况下，特定输入端口、输入VPI和输入VCI的第一条添加分支消息将建立点对点虚拟连接。具有相同输入端口、输入VPI和输入VCI字段的第二条添加分支消息将连接转换为具有两个分支的点对多点虚拟连接。（对于虚拟路径连接，不需要输入VCI。）但是，为了避免某些交换机设计可能的低效，提供了多播标志。如果控制器在建立第一个分支时知道一个新连接是点对多点的，它可以在多播标志中指示这一点。具有相同输入端口、输入VPI和输入VCI字段的后续添加分支消息将向点对多点连接添加更多分支。在具有两个分支的点对多点连接上使用Delete Branch消息将导致点对点连接。但是，如果交换机选择，它可以将此连接构造为具有单个输出分支的点对多点连接。（对于某些交换机设计，此结构可能更方便。）在点到点连接上使用删除分支消息将删除点到点连接。没有零输出分支连接的概念。所有连接都是单向的，一个输入虚拟路径或虚拟通道到一个或多个输出虚拟路径或虚拟通道。
GSMP supports point-to-point and point-to-multipoint connections. A multipoint-to-point connection is specified by establishing multiple point-to-point connections each of them specifying the same output branch. (An output branch is specified by an output port and output
GSMP支持点对点和点对多点连接。多点对点连接是通过建立多个点对点连接来指定的，每个点对点连接指定相同的输出分支。（输出分支由输出端口和输出端口指定
VPI for a virtual path connection and by an output port, output VPI, and output VCI for a virtual channel connection.) A multipoint-to-multipoint connection is specified by establishing multiple point-to-multipoint trees each of them specifying the same output branches.
虚拟路径连接的VPI和虚拟通道连接的输出端口、输出VPI和输出VCI。）多点对多点连接是通过建立多个点对多点树来指定的，每个树指定相同的输出分支。
The connection management messages apply both to virtual channel connections and virtual path connections. The Add Branch and Move Branch connection management messages have two Message Types. One Message Type indicates that a virtual channel connection is required, and the other Message Type indicates that a virtual path connection is required. The Delete Branches, Delete Tree, and Delete All connection management messages have only a single Message Type because they do not need to distinguish between virtual channel connections and virtual path connections. For virtual path connections, neither Input VCI fields nor Output VCI fields are required. They should be set to zero by the sender and ignored by the receiver. Virtual channel branches may not be added to an existing virtual path connection. Conversely, virtual path branches may not be added to an existing virtual channel connection. In the Port Configuration message each switch input port may declare whether it is capable of supporting virtual path switching (i.e. accepting connection management messages requesting virtual path connections).
连接管理消息同时应用于虚拟通道连接和虚拟路径连接。添加分支和移动分支连接管理消息有两种消息类型。一种消息类型表示需要虚拟通道连接，另一种消息类型表示需要虚拟路径连接。“删除分支”、“删除树”和“删除所有连接管理”消息只有一种消息类型，因为它们不需要区分虚拟通道连接和虚拟路径连接。对于虚拟路径连接，既不需要输入VCI字段，也不需要输出VCI字段。发送方应将它们设置为零，接收方应忽略它们。虚拟通道分支不能添加到现有虚拟路径连接。相反，虚拟路径分支可能不会添加到现有的虚拟通道连接。在端口配置消息中，每个交换机输入端口可以声明其是否能够支持虚拟路径交换（即，接受请求虚拟路径连接的连接管理消息）。
The connection management messages may be issued regardless of the Port Status of the switch port. Connections may be established or deleted when a switch port is in the Available, Unavailable, or any of the Loopback states. However, all connection state on an input port will be deleted when the port returns to the Available state from any other state, i.e. when a Port Management message is received for that port with the Function field indicating either Bring Up, or Reset Input Port.
无论交换机端口的端口状态如何，都可以发出连接管理消息。当交换机端口处于可用、不可用或任何环回状态时，可以建立或删除连接。但是，当输入端口从任何其他状态返回可用状态时，即当接收到该端口的端口管理消息时，输入端口上的所有连接状态都将被删除，该消息的功能字段指示打开或重置输入端口。
The Add Branch message is a connection management message used to establish a virtual channel connection or a virtual path connection or to add an additional branch to an existing virtual channel connection or virtual path connection. It may also be used to check the connection state stored in the switch. The connection is specified by the Input Port, Input VPI, and Input VCI fields. The output branch is specified by the Output Port, Output VPI, and Output VCI fields. The quality of service requirements of the connection are specified by the Class of Service field. To request a virtual channel connection the Virtual Channel Connection (VCC) Add Branch message is:
添加分支消息是一条连接管理消息，用于建立虚拟通道连接或虚拟路径连接，或向现有虚拟通道连接或虚拟路径连接添加其他分支。它还可用于检查存储在交换机中的连接状态。连接由输入端口、输入VPI和输入VCI字段指定。输出分支由输出端口、输出VPI和输出VCI字段指定。连接的服务质量要求由服务类别字段指定。要请求虚拟通道连接，虚拟通道连接（VCC）添加分支消息为：
Message Type = 16
消息类型=16
To request a virtual path connection the Virtual Path Connection (VPC) Add Branch message is:
要请求虚拟路径连接，虚拟路径连接（VPC）添加分支消息为：
Message Type = 26
消息类型=26
If a VPC Add Branch message is received and the switch input port specified by the Input Port field does not support virtual path switching, a failure response message must be returned indicating, "Virtual path switching is not supported on this input port."
如果收到VPC添加分支消息，且输入端口字段指定的交换机输入端口不支持虚拟路径切换，则必须返回故障响应消息，指示“此输入端口不支持虚拟路径切换”
If the virtual channel connection specified by the Input Port, Input VPI, and Input VCI fields; or the virtual path connection specified by the Input Port and Input VPI fields; does not already exist, it must be established with the single output branch specified in the request message. If the Bidirectional Flag in the Flags field is set, the reverse connection must also be established. The output branch should have the QoS attributes specified by the Class of Service field.
如果输入端口、输入VPI和输入VCI字段指定的虚拟通道连接；或输入端口和输入VPI字段指定的虚拟路径连接；不存在，必须使用请求消息中指定的单个输出分支建立该分支。如果在标志字段中设置了双向标志，则还必须建立反向连接。输出分支应该具有服务类别字段指定的QoS属性。
For the VCC Add Branch message, if a virtual path connection already exists on the virtual path specified by the Input Port and Input VPI fields, a failure response message must be returned indicating, "Attempt to add a virtual channel connection branch to an existing virtual path connection." For the VPC Add Branch message, if a virtual channel connection already exists on any of the virtual channels within the virtual path specified by the Input Port and Input VPI fields, a failure response message must be returned indicating, "Attempt to add a virtual path connection branch to an existing virtual channel connection."
对于VCC添加分支消息，如果输入端口和输入VPI字段指定的虚拟路径上已存在虚拟路径连接，则必须返回故障响应消息，指示“尝试将虚拟通道连接分支添加到现有虚拟路径连接”。对于VPC添加分支消息，如果输入端口和输入VPI字段指定的虚拟路径内的任何虚拟通道上已经存在虚拟通道连接，则必须返回故障响应消息，指示“尝试将虚拟路径连接分支添加到现有虚拟通道连接”
If the virtual channel connection specified by the Input Port, Input VPI, and Input VCI fields; or the virtual path connection specified by the Input Port and Input VPI fields; already exists, but the specified output branch does not, the new output branch must be added. The new output branch should have the QoS attributes specified by the Class of Service field.
如果输入端口、输入VPI和输入VCI字段指定的虚拟通道连接；或输入端口和输入VPI字段指定的虚拟路径连接；已存在，但指定的输出分支不存在，必须添加新的输出分支。新的输出分支应该具有服务类别字段指定的QoS属性。
If the virtual channel connection specified by the Input Port, Input VPI, and Input VCI fields; or the virtual path connection specified by the Input Port and Input VPI fields; already exists and the specified output branch also already exists, the QoS attributes of the connection, specified by the Class of Service field, if different from the request message, should be changed to that in the request message. A success response message must be sent if the Result field of the request message is "AckAll". This allows the controller to periodically reassert the state of a connection or to change its priority. If the result field of the request message is "NoSuccessAck" a success response message should not be returned.
如果输入端口、输入VPI和输入VCI字段指定的虚拟通道连接；或输入端口和输入VPI字段指定的虚拟路径连接；如果已存在且指定的输出分支也已存在，则由“服务类别”字段指定的连接的QoS属性（如果与请求消息不同）应更改为请求消息中的属性。如果请求消息的结果字段为“AckAll”，则必须发送成功响应消息。这允许控制器定期重新指定连接状态或更改其优先级。如果请求消息的结果字段为“NoSuccessAck”，则不应返回成功响应消息。
This may be used to reduce the traffic on the control link for messages that are reasserting previously established state. For messages that are reasserting previously established state, the switch must always check that this state is correctly established in the switch hardware (i.e. the actual connection tables used to forward cells).
这可用于减少控制链路上正在重新建立先前状态的消息的通信量。对于重新建立先前状态的消息，交换机必须始终检查交换机硬件（即用于转发单元的实际连接表）中是否正确建立了该状态。
If the output branch specified by the Output Port, Output VPI, and Output VCI fields for a virtual channel connection; or the output branch specified by the Output Port and Output VPI fields for a virtual path connection; is already in use by any connection other than that specified by the Input Port, Input VPI, and Input VCI fields, then the resulting output branch will have multiple input branches. If multiple point-to-point connections share the same output branch the result will be a multipoint-to-point connection. If multiple point-to-multipoint trees share the same output branches the result will be a multipoint-to-multipoint connection.
如果输出端口、输出VPI和输出VCI字段为虚拟通道连接指定了输出分支；或由虚拟路径连接的输出端口和输出VPI字段指定的输出分支；已由输入端口、输入VPI和输入VCI字段指定的连接以外的任何连接使用，则生成的输出分支将具有多个输入分支。如果多个点对点连接共享同一输出分支，则结果将是多点对点连接。如果多个点对多点树共享相同的输出分支，则结果将是多点对多点连接。
If the virtual channel connection specified by the Input Port, Input VPI, and Input VCI fields, or the virtual path connection specified by the Input Port and Input VPI fields, already exists, and the Bidirectional Flag in the Flags field is set, a failure response must be returned indicating: "Only point-to-point bidirectional connections may be established."
如果输入端口、输入VPI和输入VCI字段指定的虚拟通道连接或输入端口和输入VPI字段指定的虚拟路径连接已经存在，并且在标志字段中设置了双向标志，则必须返回故障响应，指示：“只能建立点对点双向连接。”
It should be noted that different switches support multicast in different ways. There will be a limit to the total number of point-to-multipoint connections any switch can support, and possibly a limit on the maximum number of branches that a point-to-multipoint connection may specify. Some switches also impose a limit on the number of different VPI/VCI values that may be assigned to the output branches of a point-to-multipoint connection. Many switches are incapable of supporting more than a single branch of any particular point-to-multipoint connection on the same output port. Specific failure codes are defined for some of these conditions.
应该注意的是，不同的交换机以不同的方式支持多播。任何交换机可以支持的点对多点连接的总数都有限制，点对多点连接可以指定的最大分支数也可能有限制。一些开关还对可能分配给点对多点连接的输出分支的不同VPI/VCI值的数量施加限制。许多交换机无法在同一输出端口上支持任何特定点对多点连接的多个分支。针对其中一些情况定义了特定的故障代码。
The Delete Tree message is a connection management message used to delete an entire virtual channel connection or an entire virtual path connection. All remaining branches of the connection are deleted. A virtual channel connection is specified by the Input Port, Input VPI, and Input VCI fields. A virtual path connection is specified by the Input Port and Input VPI fields. The Output Port, Output VPI, and Output VCI fields are not used in this message. The Delete Tree message is:
删除树消息是用于删除整个虚拟通道连接或整个虚拟路径连接的连接管理消息。将删除连接的所有剩余分支。虚拟通道连接由输入端口、输入VPI和输入VCI字段指定。虚拟路径连接由输入端口和输入VPI字段指定。此消息中不使用输出端口、输出VPI和输出VCI字段。删除树消息为：
Message Type = 18
消息类型=18
If the Result field of the request message is "AckAll" a success response message must be sent upon successful deletion of the specified connection. The success message must not be sent until the delete operation has been completed and if possible, not until all data on the connection, queued for transmission, has been transmitted. The Number of Branches field is not used in either the request or response messages of the Delete Tree message.
如果请求消息的结果字段为“AckAll”，则在成功删除指定连接时必须发送成功响应消息。在完成删除操作之前，以及在可能的情况下，在传输排队等待传输的连接上的所有数据之前，不得发送成功消息。“删除树”消息的请求或响应消息中均未使用“分支数”字段。
The Verify Tree message has been removed from this version of GSMP. Its function has been replaced by the Number of Branches field in the success response to the Add Branch message which contains the number of branches on a virtual channel connection after successful completion of an add branch operation.
验证树消息已从此版本的GSMP中删除。其功能已被添加分支消息的成功响应中的“分支数”字段替换，该消息包含成功完成添加分支操作后虚拟通道连接上的分支数。
Message Type = 19 is reserved.
保留消息类型=19。
If a request message is received with Message Type = 19 a failure response must be returned with the Code field indicating: "The specified request is not implemented in this version of the protocol."
如果收到消息类型为19的请求消息，则必须返回失败响应，代码字段指示：“此协议版本中未实现指定的请求。”
The Delete All message is a connection management message used to delete all connections on a switch input port. All connections that arrive at the specified input port must be deleted. On completion of the operation all dynamically assigned VPI/VCI values for the specified port must be unassigned, i.e. there must be no virtual connections established in the VPI/VCI space that GSMP controls on this port. The Input VPI, Input VCI, Output Port, Output VPI, and Output VCI fields are not used in this message. The Delete All message is:
“全部删除”消息是一条连接管理消息，用于删除交换机输入端口上的所有连接。必须删除到达指定输入端口的所有连接。操作完成后，必须取消指定端口的所有动态分配的VPI/VCI值，即GSMP在此端口上控制的VPI/VCI空间中不得建立虚拟连接。此消息中不使用输入VPI、输入VCI、输出端口、输出VPI和输出VCI字段。“全部删除”消息为：
Message Type = 20
消息类型=20
If the Result field of the request message is "AckAll" a success response message must be sent upon completion of the operation. The Number of Branches field is not used in either the request or response messages of the Delete All message. The success response message must not be sent until the operation has been completed.
如果请求消息的结果字段为“AckAll”，则必须在操作完成后发送成功响应消息。“全部删除”消息的请求消息或响应消息中均未使用“分支数”字段。在操作完成之前，不得发送成功响应消息。
The following failure response messages may be returned to a Delete All request.
以下故障响应消息可能会返回到“全部删除”请求。
The specified request is not implemented on this switch.
指定的请求未在此交换机上实现。
One or more of the specified ports does not exist.
一个或多个指定端口不存在。
Invalid Port Session Number.
端口会话号无效。
If any field in a Delete All message not covered by the above failure codes is invalid, a failure response must be returned indicating: "Invalid request message." Else, the delete all operation must be completed successfully and a success message returned. No other failure messages are permitted.
如果上述故障代码未涵盖的删除所有消息中的任何字段无效，则必须返回故障响应，指示“无效请求消息”。否则，必须成功完成删除所有操作并返回成功消息。不允许出现其他故障消息。
The Delete Branches message is a connection management message used to request one or more delete branch operations. Each delete branch operation deletes a branch of a virtual channel connection or a virtual path connection, or in the case of the last branch of a connection, it deletes the connection. The Delete Branches message is:
“删除分支”消息是用于请求一个或多个删除分支操作的连接管理消息。每个删除分支操作都会删除虚拟通道连接或虚拟路径连接的一个分支，如果是连接的最后一个分支，则会删除该连接。“删除分支”消息为：
Message Type = 17
消息类型=17
The request message has the following format:
请求消息的格式如下：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Number of Elements |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Delete Branch Elements ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Number of Elements |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Delete Branch Elements ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Number of Elements Specifies the number of Delete Branch Elements to follow in the message. The number of Delete Branch Elements in a Delete Branches message must not cause the packet length to exceed the maximum transmission unit defined by the encapsulation.
元素数指定消息中要遵循的删除分支元素数。Delete branchs消息中Delete Branch元素的数量不得导致数据包长度超过封装定义的最大传输单位。
Each Delete Branch Element specifies an output branch to be deleted and has the following structure:
每个Delete Branch元素指定要删除的输出分支，并具有以下结构：
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Error | Input VPI | Input VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x x x x| Output VPI | Output VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Error | Input VPI | Input VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x x x x| Output VPI | Output VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Error Is used to return a failure code indicating the reason for the failure of a specific Delete Branch Element in a Delete Branches failure response message. The Error field is not used in the request message and must be set to zero. A value of zero is used to indicate that the delete operation specified by this Delete Branch Element was successful. Values for the other failure codes are specified in Section 3.2, "Failure Response Messages."
错误用于返回故障代码，指示删除分支失败响应消息中特定删除分支元素失败的原因。错误字段未在请求消息中使用，必须设置为零。值为零表示此删除分支元素指定的删除操作已成功。第3.2节“故障响应消息”中规定了其他故障代码的值
All other fields of the Delete Branch Element have the same definition as specified for the other connection management messages.
Delete Branch元素的所有其他字段的定义与为其他连接管理消息指定的定义相同。
In each Delete Branch Element, either a virtual channel connection is specified by the Input Port, Input VPI, and Input VCI fields; or a virtual path connection is specified by the Input Port and Input VPI fields. The specific branch to be deleted is indicated by the Output Port, Output VPI, and Output VCI fields for virtual channel connections and by the Output Port and Output VPI for virtual path connections.
在每个删除分支元素中，输入端口、输入VPI和输入VCI字段指定虚拟通道连接；或者，虚拟路径连接由输入端口和输入VPI字段指定。要删除的特定分支由虚拟通道连接的输出端口、输出VPI和输出VCI字段以及虚拟路径连接的输出端口和输出VPI字段指示。
If the Result field of the Delete Branches request message is "AckAll" a success response message must be sent upon successful deletion of the branches specified by all of the Delete Branch Elements. The success response message must not be sent until all of the delete branch operations have been completed. The success response message is only sent if all of the requested delete branch operations were successful. No Delete Branch Elements are returned in a Delete Branches success response message and the Number of Elements field must be set to zero.
如果删除分支请求消息的结果字段为“AckAll”，则在成功删除所有删除分支元素指定的分支后，必须发送成功响应消息。在完成所有删除分支操作之前，不得发送成功响应消息。仅当所有请求的删除分支操作都成功时，才会发送成功响应消息。删除分支成功响应消息中不返回删除分支元素，并且元素数字段必须设置为零。
If there is a failure in any of the Delete Branch Elements a Delete Branches failure response message must be returned. The Delete Branches failure response message is a copy of the request message with the Code field of the entire message set to, "Failure specific
如果任何Delete Branch元素中出现故障，则必须返回Delete branchs故障响应消息。Delete Branchs故障响应消息是请求消息的副本，整个消息的代码字段设置为“特定于故障”
to the particular message type," and the Error field of each Delete Branch Element indicating the result of each requested delete operation. A failure in any of the Delete Branch Elements must not interfere with the processing of any other Delete Branch Elements.
对于特定的消息类型，“以及每个删除分支元素的错误字段，指示每个请求的删除操作的结果。任何删除分支元素中的故障不得干扰任何其他删除分支元素的处理。
The Move Branch message is used to move a branch of an existing connection from its current output port VPI/VCI to a new output port VPI/VCI in a single atomic transaction. This operation occurs frequently in IP switching, every time a flow is switched from hop-by-hop forwarding to a dedicated virtual channel. The Move Branch connection management message has the following format for both request and response messages:
Move Branch消息用于在单个原子事务中将现有连接的分支从其当前输出端口VPI/VCI移动到新的输出端口VPI/VCI。此操作在IP交换中经常发生，每次流从逐跳转发切换到专用虚拟通道时。移动分支连接管理消息的请求和响应消息格式如下：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags | Input VPI | Input VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Old Output Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x x x x| Old Output VPI | Old Output VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| New Output Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x x x x| New Output VPI | New Output VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number of Branches | Class of Service |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags | Input VPI | Input VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Old Output Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x x x x| Old Output VPI | Old Output VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| New Output Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x x x x| New Output VPI | New Output VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number of Branches | Class of Service |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The VCC Move Branch message is a connection management message used to move a single output branch of a virtual channel connection from its current output port, output VPI, and output VCI, to a new output port, output VPI, and output VCI on the same virtual channel connection. None of the other output branches are modified. When the operation is complete the original output VPI/VCI on the original output port will be deleted from the connection. The VCC Move Branch message is:
VCC移动分支消息是一种连接管理消息，用于将虚拟通道连接的单个输出分支从其当前输出端口、输出VPI和输出VCI移动到同一虚拟通道连接上的新输出端口、输出VPI和输出VCI。没有修改任何其他输出分支。操作完成后，原始输出端口上的原始输出VPI/VCI将从连接中删除。VCC移动分支消息为：
Message Type = 22
消息类型=22
For the VCC Move Branch message, if the virtual channel connection specified by the Input Port, Input VPI, and Input VCI fields already exists, and the output branch specified by the Old Output Port, Old Output VPI, and Old Output VCI fields exists as a branch on that connection, the output branch specified by the New Output Port, New Output VPI, and New Output VCI fields is added to the connection and the branch specified by the Old Output Port, Old Output VPI, and Old Output VCI fields is deleted. If the Result field of the request message is "AckAll" a success response message must be sent upon successful completion of the operation. The success response message must not be sent until the Move Branch operation has been completed.
对于VCC移动分支消息，如果输入端口、输入VPI和输入VCI字段指定的虚拟通道连接已经存在，并且旧输出端口、旧输出VPI和旧输出VCI字段指定的输出分支作为该连接上的分支存在，则新输出端口、新输出VPI指定的输出分支，将新的输出VCI字段添加到连接中，并删除由旧输出端口、旧输出VPI和旧输出VCI字段指定的分支。如果请求消息的结果字段为“AckAll”，则必须在成功完成操作后发送成功响应消息。在移动分支操作完成之前，不得发送成功响应消息。
For the VCC Move Branch message, if the virtual channel connection specified by the Input Port, Input VPI, and Input VCI fields already exists, but the output branch specified by the Old Output Port, Old Output VPI, and Old Output VCI fields does not exist as a branch on that connection, a failure response must be returned with the Code field indicating, "The specified branch does not exist."
对于VCC移动分支消息，如果输入端口、输入VPI和输入VCI字段指定的虚拟通道连接已存在，但旧输出端口、旧输出VPI和旧输出VCI字段指定的输出分支不作为该连接上的分支存在，必须返回故障响应，代码字段指示“指定的分支不存在”
The VPC Move Branch message is a connection management message used to move a single output branch of a virtual path connection from its current output port and output VPI, to a new output port and output VPI on the same virtual channel connection. None of the other output branches are modified. When the operation is complete the original output VPI on the original output port will be deleted from the connection. The VPC Move Branch message is:
VPC移动分支消息是一种连接管理消息，用于将虚拟路径连接的单个输出分支从其当前输出端口和输出VPI移动到同一虚拟通道连接上的新输出端口和输出VPI。没有修改任何其他输出分支。操作完成后，原始输出端口上的原始输出VPI将从连接中删除。VPC移动分支消息为：
Message Type = 27
消息类型=27
For the VPC Move Branch message, if the virtual path connection specified by the Input Port and Input VPI fields already exists, and the output branch specified by the Old Output Port and Old Output VPI fields exists as a branch on that connection, the output branch specified by the New Output Port and New Output VPI fields is added to the connection and the branch specified by the Old Output Port and Old Output VPI fields is deleted. If the Result field of the request message is "AckAll" a success response message must be sent upon successful completion of the operation. The success response message must not be sent until the Move Branch operation has been completed.
对于VPC移动分支消息，如果输入端口和输入VPI字段指定的虚拟路径连接已经存在，并且旧输出端口和旧输出VPI字段指定的输出分支作为该连接上的分支存在，将新输出端口和新输出VPI字段指定的输出分支添加到连接中，并删除旧输出端口和旧输出VPI字段指定的分支。如果请求消息的结果字段为“AckAll”，则必须在成功完成操作后发送成功响应消息。在移动分支操作完成之前，不得发送成功响应消息。
For the VPC Move Branch message, if the virtual path connection specified by the Input Port and Input VPI fields already exists, but the output branch specified by the Old Output Port and Old Output VPI fields does not exist as a branch on that connection, a failure response must be returned with the Code field indicating, "The specified branch does not exist."
对于VPC移动分支消息，如果由输入端口和输入VPI字段指定的虚拟路径连接已经存在，但由旧输出端口和旧输出VPI字段指定的输出分支不作为该连接上的分支存在，则必须返回故障响应，代码字段指示，“指定的分支不存在。”
If the virtual channel connection specified by the Input Port, Input VPI, and Input VCI fields; or the virtual path connection specified by the Input Port and Input VPI fields; does not exist, a failure response must be returned with the Code field indicating, "The specified connection does not exist."
如果输入端口、输入VPI和输入VCI字段指定的虚拟通道连接；或输入端口和输入VPI字段指定的虚拟路径连接；不存在，则必须返回故障响应，代码字段指示“指定的连接不存在”
If the output branch specified by the New Output Port, New Output VPI, and New Output VCI fields for a virtual channel connection; or the output branch specified by the New Output Port and New Output VPI fields for a virtual path connection; is already in use by any connection other than that specified by the Input Port, Input VPI, and Input VCI fields then the resulting output branch will have multiple input branches. If multiple point-to-point connections share the same output branch the result will be a multipoint-to-point connection. If multiple point-to-multipoint trees share the same output branches the result will be a multipoint-to-multipoint connection.
如果由虚拟通道连接的新输出端口、新输出VPI和新输出VCI字段指定的输出分支；或由虚拟路径连接的新输出端口和新输出VPI字段指定的输出分支；已由输入端口、输入VPI和输入VCI字段指定的连接以外的任何连接使用，则生成的输出分支将具有多个输入分支。如果多个点对点连接共享同一输出分支，则结果将是多点对点连接。如果多个点对多点树共享相同的输出分支，则结果将是多点对多点连接。
The Port Management message allows a port to be brought into service, taken out of service, looped back, reset, or the transmit cell rate changed. Only the Bring Up and the Reset Input Port functions change the connection state (established connections) on the input port. Only the Bring Up function changes the value of the Port Session Number. If the Result field of the request message is "AckAll" a success response message must be sent upon successful completion of the operation. The success response message must not be sent until the operation has been completed. The Port Management Message is:
端口管理消息允许端口投入使用、停止使用、环回、重置或更改传输单元速率。只有启动和重置输入端口功能可以更改输入端口上的连接状态（已建立的连接）。只有“打开”功能可以更改端口会话号的值。如果请求消息的结果字段为“AckAll”，则必须在成功完成操作后发送成功响应消息。在操作完成之前，不得发送成功响应消息。端口管理消息为：
Message Type = 32
消息类型=32
The Port Management message has the following format for the request and success response messages:
端口管理消息的请求和成功响应消息格式如下：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Event Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Event Flags | Duration | Function |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transmit Cell Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Event Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Event Flags | Duration | Function |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transmit Cell Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Event Sequence Number In the success response message gives the current value of the Event Sequence Number of the switch port indicated by the Port field. The Event Sequence Number is set to zero when the port is initialized. It is incremented by one each time the port detects an asynchronous event that the switch would normally report via an Event message. If the Event Sequence Number in the success response differs from the Event Sequence Number of the most recent Event message received for that port, events have occurred that were not reported via an Event message. This is most likely to be due to the flow control that restricts the rate at which a switch can send Event messages for each port. In the request message this field is not used.
成功响应消息中的事件序列号给出了端口字段指示的交换机端口的事件序列号的当前值。端口初始化时，事件序列号设置为零。每当端口检测到交换机通常通过事件消息报告的异步事件时，该值将递增一。如果成功响应中的事件序列号与该端口最近接收的事件消息的事件序列号不同，则表示发生了未通过事件消息报告的事件。这很可能是由于流控制限制了交换机可以为每个端口发送事件消息的速率。在请求消息中不使用此字段。
Event Flags Field in the request message is used to reset the Event Flags in the switch port indicated by the Port field. Each Event Flag in a switch port corresponds to a type of Event message. When a switch port sends an Event message it sets the corresponding Event Flag on that port. The port is not permitted to send another Event message of the same type until the Event Flag has been reset. If the Function field in the request message is set to "Reset Event Flags," for each bit that is set in the Event Flags field, the corresponding Event Flag in the switch port is reset.
请求消息中的事件标志字段用于重置端口字段指示的交换机端口中的事件标志。交换机端口中的每个事件标志对应于一种类型的事件消息。当交换机端口发送事件消息时，它会在该端口上设置相应的事件标志。在重置事件标志之前，不允许端口发送另一个相同类型的事件消息。如果请求消息中的功能字段设置为“重置事件标志”，则对于在事件标志字段中设置的每个位，交换机端口中相应的事件标志将重置。
The Event Flags field is only used in a request message with the Function field set to "Reset Event Flags." For all other values of the Function field, the Event Flags field
事件标志字段仅在函数字段设置为“重置事件标志”的请求消息中使用。对于函数字段的所有其他值，事件标志字段
is not used. In the success response message the Event Flags field must be set to the current value of the Event Flags for the port, after the completion of the operation specified by the request message, for all values of the Function field. Setting the Event Flags field to all zeros in a "Reset Event Flags" request message allows the controller to obtain the current state of the Event Flags and the current Event Sequence Number of the port without changing the state of the Event Flags.
没有使用。在成功响应消息中，对于函数字段的所有值，在请求消息指定的操作完成后，事件标志字段必须设置为端口事件标志的当前值。将“重置事件标志”请求消息中的事件标志字段设置为全零，可使控制器获得事件标志的当前状态和端口的当前事件序列号，而无需更改事件标志的状态。
The correspondence between the types of Event message and the bits of the Event Flags field is as follows:
事件消息类型与事件标志字段位之间的对应关系如下：
0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+
|U|D|I|N|Z|x x x|
+-+-+-+-+-+-+-+-+
0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+
|U|D|I|N|Z|x x x|
+-+-+-+-+-+-+-+-+
U: Port Up Bit 0, (most significant bit) D: Port Down Bit 1, I: Invalid VPI/VCI Bit 2, N: New Port Bit 3, Z: Dead Port Bit 4, x: Unused Bits 5--7.
U：端口上升位0，（最高有效位）D：端口下降位1，I：无效VPI/VCI位2，N：新端口位3，Z：无效端口位4，x：未使用位5-7。
Duration Is the length of time, in seconds, that any of the loopback states remain in operation. When the duration has expired the port will automatically be returned to service. If another Port Management message is received for the same port before the duration has expired, the loopback will continue to remain in operation for the length of time specified by the Duration field in the new message. The Duration field is only used in request messages with the Function field set to Internal Loopback, External Loopback, or Bothway Loopback.
Duration是任何环回状态保持运行的时间长度（以秒为单位）。持续时间到期后，端口将自动恢复服务。如果在持续时间到期之前收到同一端口的另一个端口管理消息，则环回将在新消息的持续时间字段指定的时间内继续运行。“持续时间”字段仅在功能字段设置为“内部环回”、“外部环回”或“双向环回”的请求消息中使用。
Function Specifies the action to be taken. The specified action will be taken regardless of the current status of the port (Available, Unavailable, or any Loopback state). If the specified function requires a new Port Session Number to be generated, the new Port Session Number must be returned in the success response message. The defined values of the Function field are:
函数指定要采取的操作。无论端口的当前状态如何（可用、不可用或任何环回状态），都将执行指定的操作。如果指定的函数需要生成新的端口会话号，则必须在成功响应消息中返回新的端口会话号。函数字段的定义值为：
Bring Up: Function = 1. Bring the port into service. All
打开：函数=1。使港口投入使用。全部的
connections that arrive at the specified input port must be deleted and a new Port Session Number must be selected using some form of random number. On completion of the operation all dynamically assigned VPI/VCI values for the specified input port must be unassigned, i.e. no virtual connections will be established in the VPI/VCI space that GSMP controls on this input port. The Port Status of the port afterwards will be Available.
必须删除到达指定输入端口的连接，并且必须使用某种形式的随机数选择新的端口会话号。操作完成后，必须取消指定输入端口的所有动态分配的VPI/VCI值，即GSMP在此输入端口上控制的VPI/VCI空间中不会建立任何虚拟连接。之后将提供端口的端口状态。
Take Down: Function = 2. Take the port out of service. Any cells received at this port will be discarded. No cells will be transmitted from this port. The Port Status of the port afterwards will be Unavailable.
取下：函数=2。使港口停止使用。在此端口接收到的任何单元格都将被丢弃。此端口不会传输任何单元格。之后端口的端口状态将不可用。
The behavior is undefined if the port is taken down over which the GSMP session that controls the switch is running. (In this case the most probable behavior would be for the switch either to ignore the message or to terminate the current GSMP session and to initiate another session, possibly with the backup controller, if any.) The correct method to reset the link over which GSMP is running is to issue an RSTACK message in the adjacency protocol.
如果关闭了控制交换机的GSMP会话正在其上运行的端口，则该行为未定义。（在这种情况下，交换机最可能的行为是忽略消息或终止当前GSMP会话并启动另一个会话，可能是与备份控制器（如果有））重置GSMP正在运行的链路的正确方法是在邻接协议中发出RSTACK消息。
Internal Loopback: Function = 3. Cells arriving at the output port from the switch fabric are looped through to the input port to return to the switch fabric. All of the ATM functions of the input port above the physical layer, e.g. header translation, are performed upon the looped back cells. The Port Status of the port afterwards will be Internal Loopback.
内部环回：函数=3。从交换结构到达输出端口的单元循环通过输入端口返回交换结构。物理层上输入端口的所有ATM功能，例如报头转换，都是在环回信元上执行的。之后端口的端口状态将为内部环回。
External Loopback: Function = 4. Cells arriving at the input port from the external communications link are immediately looped back to the communications link at the physical layer without entering the input port. None of the ATM functions of the input port above the physical layer are performed upon the looped back cells. The Port Status of the port afterwards will be External Loopback.
外部环回：函数=4。从外部通信链路到达输入端口的小区会立即环回物理层的通信链路，而无需进入输入端口。物理层上的输入端口的ATM功能都不会在环回信元上执行。之后端口的端口状态将为外部环回。
Bothway Loopback: Function = 5. Both internal and external loopback are
双向环回：函数=5。内部和外部环回都是
performed. The Port Status of the port afterwards will be Bothway Loopback.
表演。之后端口的端口状态将为双向环回。
Reset Input Port: Function = 6. All connections that arrive at the specified input port must be deleted and the input and output port hardware re-initialized. On completion of the operation all dynamically assigned VPI/VCI values for the specified input port must be unassigned, i.e. no virtual connections will be established in the VPI/VCI space that GSMP controls on this input port. The range of VPIs and VCIs that may be controlled by GSMP on this port will be set to the default values specified in the Port Configuration message. The transmit cell rate of the output port must be set to its default value. The Port Session Number is not changed by the Reset Input Port function. The Port Status of the port afterwards will be Unavailable.
重置输入端口：功能=6。必须删除到达指定输入端口的所有连接，并重新初始化输入和输出端口硬件。操作完成后，必须取消指定输入端口的所有动态分配的VPI/VCI值，即GSMP在此输入端口上控制的VPI/VCI空间中不会建立任何虚拟连接。GSMP可在此端口上控制的VPI和VCI范围将设置为端口配置消息中指定的默认值。输出端口的传输单元速率必须设置为其默认值。重置输入端口功能不会更改端口会话号。之后端口的端口状态将不可用。
Reset Event Flags: Function = 7. For each bit that is set in the Event Flags field, the corresponding Event Flag in the switch port must be reset. The Port Status of the port is not changed by this function.
重置事件标志：函数=7。对于在事件标志字段中设置的每个位，必须重置交换机端口中相应的事件标志。此功能不会更改端口的端口状态。
Set Transmit Cell Rate: Function = 8. Sets the transmit cell rate of the output port as close as possible to the rate specified in the Transmit Cell Rate field. In the success response message the Transmit Cell Rate must indicate the actual transmit cell rate of the output port. If the transmit cell rate of the requested output port cannot be changed, a failure response must be returned with the Code field indicating: "The transmit cell rate of this output port cannot be changed." If the transmit cell rate of the requested output port can be changed, but the value of the Transmit Cell Rate field is beyond the range of acceptable values, a failure response must be returned with the Code field indicating: "Requested transmit cell rate out of range for this output port." In the failure response message the Transmit Cell Rate must contain the same value as contained in the request message that caused the failure. The transmit cell rate of the output port is not changed by the Bring Up, Take Down, or any of the Loopback functions. It is returned to the default value by the Reset Input Port function.
设置发送单元速率：函数=8。将输出端口的传输单元速率设置为尽可能接近传输单元速率字段中指定的速率。在成功响应消息中，传输小区速率必须指示输出端口的实际传输小区速率。如果无法更改请求输出端口的传输单元速率，则必须返回故障响应，代码字段指示：“此输出端口的传输单元速率无法更改”。如果可以更改请求输出端口的传输单元速率，但是传输单元速率字段的值超出可接受值的范围，必须返回故障响应，代码字段指示：“请求的传输单元速率超出此输出端口的范围。”在故障响应消息中，传输单元速率必须包含与导致故障的请求消息中包含的值相同的值。输出端口的传输信元速率不会因上带、取下或任何环回功能而改变。重置输入端口功能会将其返回到默认值。
Transmit Cell Rate This field is only used in request and success response messages with the Function field set to "Set Transmit Cell Rate." It is used to set the output cell rate of the output port. It is specified in cells/s. If the Transmit Cell Rate field contains the value 0xFFFFFFFF the transmit cell rate of the output port should be set to the highest valid value.
传输单元速率此字段仅用于功能字段设置为“设置传输单元速率”的请求和成功响应消息。它用于设置输出端口的输出单元速率。它以单元格/秒为单位指定。如果发送单元速率字段包含值0xFFFFFFFF，则输出端口的发送单元速率应设置为最高有效值。
The default label range, Min VPI to Max VPI and Min VCI to Max VCI, is specified for each port by the Port Configuration or the All Ports Configuration messages. When the protocol is initialized, before the transmission of any Label Range messages, the label range of each port will be set to the default label range. (The default label range is dependent upon the switch design and configuration and is not specified by the GSMP protocol.) The Label Range message allows the range of VPIs supported by a specified port, or the range of VCIs supported by a specified VPI on a specified port, to be changed. Each switch port must declare whether it supports the Label Range message in the Port Configuration or the All Ports Configuration messages. The Label Range message is:
端口配置或所有端口配置消息为每个端口指定了默认标签范围，即最小VPI到最大VPI和最小VCI到最大VCI。协议初始化时，在传输任何标签范围消息之前，每个端口的标签范围将设置为默认标签范围。（默认标签范围取决于交换机设计和配置，而不是由GSMP协议指定。）标签范围消息允许更改指定端口支持的VPI范围或指定端口上指定VPI支持的VCI范围。每个交换机端口必须声明它是支持端口配置中的标签范围消息还是支持所有端口配置消息。标签范围消息为：
Message Type = 33
消息类型=33
The Label Range message has the following format for the request and success response messages:
对于请求和成功响应消息，标签范围消息具有以下格式：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Q|V|x x| Min VPI |x x x x| Max VPI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Min VCI | Max VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Remaining VPIs | Remaining VCIs |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Q|V|x x| Min VPI |x x x x| Max VPI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Min VCI | Max VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Remaining VPIs | Remaining VCIs |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Flags
旗帜
Q: Query If the Query flag is set in a request message, the switch must respond with the current range of valid VPIs, or the current range of valid VCIs on a specified VPI, according to the VPI/VCI flag. The current label range is not changed by a request message with the Query flag set. If the Query flag is zero, the message is requesting a label change operation.
Q:Query如果在请求消息中设置了查询标志，则交换机必须根据VPI/VCI标志，使用有效VPI的当前范围或指定VPI上有效VCI的当前范围进行响应。设置了查询标志的请求消息不会更改当前标签范围。如果查询标志为零，则消息将请求标签更改操作。
V: VPI/VCI If the VPI/VCI flag is set, the message refers to a range of VPIs only. The Min VCI and Max VCI fields are unused. If the VPI/VCI flag is zero the message refers to a range of VCIs on either one VPI or on a range of VPIs.
V:VPI/VCI如果设置了VPI/VCI标志，则消息仅指VPI的范围。最小VCI和最大VCI字段未使用。如果VPI/VCI标志为零，则消息表示一个VPI或一个VPI范围上的VCI范围。
x: Unused
x:未使用
Min VPI Max VPI Specify a range of VPI values, Min VPI to Max VPI inclusive. A single VPI may be specified with a Min VPI and a Max VPI having the same value. In a request message, if the value of the Max VPI field is less than or equal to the value of the Min VPI field, the requested range is a single VPI with a value equal to the Min VPI field. Zero is a valid value. In a request message, if the Query flag is set, and the VPI/VCI flag is zero, the Max VPI field specifies a single VPI and the Min VPI field is not used. The maximum valid value of these fields for both request and response messages is 0xFFF.
最小VPI最大VPI指定VPI值的范围，包括最小VPI到最大VPI。可以使用具有相同值的最小VPI和最大VPI指定单个VPI。在请求消息中，如果最大VPI字段的值小于或等于最小VPI字段的值，则请求的范围为单个VPI，其值等于最小VPI字段。零是一个有效值。在请求消息中，如果设置了查询标志，且VPI/VCI标志为零，则Max VPI字段指定单个VPI，而Min VPI字段不使用。请求和响应消息的这些字段的最大有效值均为0xFFF。
Min VCI Max VCI Specify a range of VCI values, Min VCI to Max VCI inclusive. A single VCI may be specified with a Min VCI and a Max VCI having the same value. In a request message, if the value of the Max VCI field is less than or equal to the value of the Min VCI field, the requested range is a single VCI with a value equal to the Min VCI field. Zero is a valid value. (However, VPI=0, VCI=0 is not available as a virtual channel connection as it is used as a special value in ATM to indicate an unassigned cell.)
最小VCI最大VCI指定VCI值的范围，包括最小VCI到最大VCI。可以使用具有相同值的最小VCI和最大VCI指定单个VCI。在请求消息中，如果最大VCI字段的值小于或等于最小VCI字段的值，则请求的范围为单个VCI，其值等于最小VCI字段。零是一个有效值。（但是，VPI=0、VCI=0不可用作虚拟通道连接，因为它在ATM中用作特殊值以指示未分配的信元。）
Remaining VPIs Remaining VCIs These fields are unused in the request message. In the
剩余VPI剩余VCI这些字段在请求消息中未使用。在
success response message and in the failure response message these fields give the maximum number of remaining VPIs and VCIs that could be requested for allocation on the specified port (after completion of the requested operation in the case of the success response). It gives the switch controller an idea of how many VPIs and VCIs it could request. The number given is the maximum possible given the constraints of the switch hardware. There is no implication that this number of VPIs and VCIs is available to every switch port.
成功响应消息和失败响应消息中的这些字段给出了可请求在指定端口上分配的剩余VPI和VCI的最大数量（在成功响应的情况下，完成请求的操作后）。它让交换机控制器知道它可以请求多少VPI和VCI。给定的数字是给定交换机硬件约束条件下可能的最大值。这并不意味着每个交换机端口都可以使用这个数量的VPI和VCI。
If the Query flag and the VPI/VCI flag are set in the request message, the switch must reply with a success response message containing the current range of valid VPIs that are supported by the port. The Min VPI and Max VPI fields are not used in the request message.
如果在请求消息中设置了查询标志和VPI/VCI标志，则交换机必须回复一条成功响应消息，其中包含端口支持的有效VPI的当前范围。请求消息中不使用最小VPI和最大VPI字段。
If the Query flag is set and the VPI/VCI flag is zero in the request message, the switch must reply with a success response message containing the current range of valid VCIs that are supported by the VPI specified by the Max VPI field. If the requested VPI is invalid, a failure response must be returned indicating: "One or more of the specified input VPIs is invalid." The Min VPI field is not used in either the request or success response messages.
如果设置了查询标志，且请求消息中的VPI/VCI标志为零，则交换机必须回复一条成功响应消息，其中包含由Max VPI字段指定的VPI支持的有效VCI的当前范围。如果请求的VPI无效，则必须返回一个故障响应，指示“一个或多个指定的输入VPI无效”。请求或成功响应消息中均未使用Min VPI字段。
If the Query flag is zero and the VPI/VCI flag is set in the request message, the Min VPI and Max VPI fields specify the new range of VPIs to be allocated to the input port specified by the Port field. Whatever the range of VPIs previously allocated to this port it should be increased or decreased to the specified value.
如果查询标志为零，并且在请求消息中设置了VPI/VCI标志，则最小VPI和最大VPI字段指定要分配给端口字段指定的输入端口的VPI的新范围。无论先前分配给该端口的VP的范围如何，都应将其增加或减少到指定值。
If the Query flag and the VPI/VCI flag are zero in the request message, the Min VCI and Max VCI fields specify the range of VCIs to be allocated to each of the VPIs specified by the VPI range. Whatever the range of VCIs previously allocated to each of the VPIs within the specified VPI range on this port, it should be increased or decreased to the specified value. The allocated VCI range must be the same on each of the VPIs within the specified VPI range.
如果请求消息中的查询标志和VPI/VCI标志为零，则最小VCI和最大VCI字段指定要分配给VPI范围指定的每个VPI的VCI范围。无论在此端口上指定的VPI范围内以前分配给每个VPI的VCI范围如何，都应将其增加或减少到指定值。在指定的VPI范围内，每个VPI上分配的VCI范围必须相同。
The success response to a Label Range message requesting a change of label range is a copy of the request message with the Remaining VPIs and Remaining VCIs fields updated to the new values after the Label Range operation.
对请求更改标签范围的标签范围消息的成功响应是请求消息的副本，剩余VPI和剩余VCIs字段在标签范围操作后更新为新值。
If the switch is unable to satisfy a request to change the VPI range, it must return a failure response message with the Code field set to "Cannot support requested VPI range." In this failure response
如果交换机无法满足更改VPI范围的请求，则必须返回故障响应消息，在此故障响应中，代码字段设置为“无法支持请求的VPI范围”
message the switch must use the Min VPI and Max VPI fields to suggest a VPI range that it would be able to satisfy.
消息交换机必须使用最小VPI和最大VPI字段来建议其能够满足的VPI范围。
If the switch is unable to satisfy a request to change the VCI range on all VPIs within the requested VPI range, it must return a failure response message with the Code field set to "Cannot support requested VCI range on all requested VPIs." In this failure response message the switch must use the Min VPI, Max VPI, Min VCI, and Max VCI fields to suggest a VPI and VCI range that it would be able to satisfy.
如果交换机无法满足在请求的VPI范围内更改所有VPI上VCI范围的请求，则必须返回故障响应消息，代码字段设置为“无法在所有请求的VPI上支持请求的VCI范围”。在此故障响应消息中，交换机必须使用最小VPI、最大VPI、最小VCI、，和最大VCI字段，以建议能够满足的VPI和VCI范围。
In all other failure response messages for the label range operation the switch must return the values of Min VPI, Max VPI, Min VCI, and Max VCI from the request message.
在标签范围操作的所有其他故障响应消息中，交换机必须从请求消息返回最小VPI、最大VPI、最小VCI和最大VCI值。
While switches can typically support all 256 or 4096 VPIs the VCI range that can be supported is often more constrained. Often the Min VCI must be 0 or 32. Typically all VCIs within a particular VPI must be contiguous. The hint in the failure response message allows the switch to suggest a label range that it could satisfy in view of its particular architecture.
虽然交换机通常可以支持所有256或4096 VPI，但可支持的VCI范围通常更受限制。通常最小VCI必须为0或32。通常，特定VPI中的所有VCI必须是连续的。故障响应消息中的提示允许交换机根据其特定的体系结构建议其可以满足的标签范围。
While the Label Range message is defined to specify both a range of VPIs and a range of VCIs within each VPI, the most likely use is to change either the VPI range or the range of VCIs within a single VPI. It is possible for a VPI to be valid but to be allocated no valid VCIs. Such a VPI could be used for a virtual path connection but to support virtual channel connections it would need to be allocated a range of VCIs.
虽然标签范围消息定义为指定每个VPI内的VPI范围和VCI范围，但最有可能的用途是更改VPI范围或单个VPI内的VCI范围。VPI可能有效，但没有分配有效的VCI。这种VPI可用于虚拟路径连接，但为了支持虚拟通道连接，需要为其分配一系列VCI。
A Label Range request message may be issued regardless of the Port Status or the Line Status of the target switch port. If the Port field of the request message contains an invalid port (a port that does not exist or a port that has been removed from the switch) a failure response message must be returned with the Code field set to, "One or more of the specified ports does not exist."
无论目标交换机端口的端口状态或线路状态如何，都可以发出标签范围请求消息。如果请求消息的端口字段包含无效端口（不存在的端口或已从交换机中删除的端口），则必须返回故障响应消息，并将代码字段设置为“一个或多个指定端口不存在”
The state and statistics messages permit the controller to request the values of various hardware counters associated with the switch input and output ports, virtual path connections, virtual channel connections, and QoS Classes. They also permit the controller to request the connection state of a switch input port. The Connection Activity message is used to determine whether one or more specific virtual channel connections or virtual path connections have recently been carrying traffic. The Statistics message is used to query the various port, connection, and QoS class traffic and error counters.
状态和统计信息允许控制器请求与交换机输入和输出端口、虚拟路径连接、虚拟通道连接和QoS类关联的各种硬件计数器的值。它们还允许控制器请求交换机输入端口的连接状态。连接活动消息用于确定一个或多个特定虚拟通道连接或虚拟路径连接最近是否承载了流量。统计信息用于查询各种端口、连接和QoS类流量和错误计数器。
The Report Connection State message is used to request an input port to report the connection state for a single virtual channel connection, a single virtual path connection, or for the entire input port.
报告连接状态消息用于请求输入端口报告单个虚拟通道连接、单个虚拟路径连接或整个输入端口的连接状态。
The Connection Activity message is used to determine whether one or more specific virtual channel connections or virtual path connections have recently been carrying traffic. The Connection Activity message contains one or more Activity Records. Each Activity Record is used to request and return activity information concerning a single virtual channel connection or virtual path connection. Each virtual channel connection is specified by its input port, input VPI, and input VCI. Each virtual path connection is specified by its input port and input VPI. These are specified in the Input Port, Input VPI, and Input VCI fields of each Activity Record. Two forms of activity detection are supported. If the switch supports per connection traffic accounting, the current value of the traffic counter for each specified virtual channel connection or virtual path connection must be returned. The units of traffic counted are not specified but will typically be either cells or frames. The controller must compare the traffic counts returned in the message with previous values for each of the specified connections to determine whether each connection has been active in the intervening period. If the switch does not support per connection traffic accounting, but is capable of detecting per connection activity by some other unspecified means, the result may be indicated for each connection using the Flags field. The Connection Activity message is:
连接活动消息用于确定一个或多个特定虚拟通道连接或虚拟路径连接最近是否承载了流量。连接活动消息包含一个或多个活动记录。每个活动记录用于请求和返回有关单个虚拟通道连接或虚拟路径连接的活动信息。每个虚拟通道连接由其输入端口、输入VPI和输入VCI指定。每个虚拟路径连接由其输入端口和输入VPI指定。这些在每个活动记录的输入端口、输入VPI和输入VCI字段中指定。支持两种形式的活动检测。如果交换机支持每连接流量计费，则必须返回每个指定虚拟通道连接或虚拟路径连接的流量计数器的当前值。未指定计数的流量单位，但通常为单元或帧。控制器必须将消息中返回的流量计数与每个指定连接的先前值进行比较，以确定每个连接在中间期间是否处于活动状态。如果交换机不支持每连接流量计费，但能够通过一些其他未指定的方式检测每连接活动，则可以使用Flags字段为每个连接指示结果。连接活动消息为：
Message Type = 48
消息类型=48
The Connection Activity request and success response messages have the following format:
连接活动请求和成功响应消息的格式如下：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number of Records | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Activity Records ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number of Records | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Activity Records ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Number of Records Field specifies the number of Activity Records to follow. The number of Connection Activity records in a single Connection Activity message must not cause the packet length to exceed the maximum transmission unit defined by the encapsulation.
记录数字段指定要遵循的活动记录数。单个连接活动消息中的连接活动记录数不得导致数据包长度超过封装定义的最大传输单位。
Each Activity Record has the following format:
每个活动记录的格式如下：
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|V|C|A|x| Input VPI | Input VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Traffic Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|V|C|A|x| Input VPI | Input VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Traffic Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Input Port Identifies the port number of the input port on which the connection of interest arrives in order to identify the connection (regardless of whether the traffic count for the connection is maintained on the input port or the output port).
Input Port标识感兴趣的连接到达的输入端口的端口号，以标识连接（无论连接的流量计数是在输入端口上还是在输出端口上保持）。
Input VPI Input VCI Fields identify the specific virtual path connection or virtual channel connection for which statistics are being requested. For a virtual path connection the Input VCI field is not used.
Input VPI Input VCI字段标识正在请求统计信息的特定虚拟路径连接或虚拟通道连接。对于虚拟路径连接，不使用输入VCI字段。
Flags
旗帜
V: Valid Record In the success response message the Valid Record flag is used to indicate an invalid Activity Record. The flag must be zero if any of the fields in this Activity Record are invalid, if the input port specified by the Input Port field does not exist, or if the specified connection does not exist. If the Valid Record flag is zero in a success response message, the Counter flag, the Activity flag, and the VC Traffic Count field are undefined. If the Valid Record flag is set, the Activity Record is valid, and the Counter and Activity flags are valid. The Valid Record flag is not used in the request message.
V:Valid Record成功响应消息中的Valid Record标志用于指示无效的活动记录。如果此活动记录中的任何字段无效、输入端口字段指定的输入端口不存在或指定的连接不存在，则该标志必须为零。如果成功响应消息中的有效记录标志为零，则计数器标志、活动标志和VC流量计数字段未定义。如果设置了有效记录标志，则活动记录有效，计数器和活动标志有效。请求消息中未使用有效记录标志。
C: Counter In a success response message, if the Valid Record flag is set, the Counter flag, if zero, indicates that the value in the VC Traffic Count field is valid. If set, it indicates that the value in the Activity flag is valid. The Counter flag is not used in the request message.
C：计数器在成功响应消息中，如果设置了有效记录标志，计数器标志（如果为零）表示VC Traffic Count字段中的值有效。如果设置，则表示活动标志中的值有效。请求消息中未使用计数器标志。
A: Activity In a success response message, if the Valid Record and Counter flags are set, the Activity flag, if set, indicates that there has been some activity on this connection since the last Connection Activity message for this connection. If zero, it indicates that there has been no activity on this connection since the last Connection Activity message for this connection. The Activity flag is not used in the request message.
A：成功响应消息中的活动，如果设置了有效记录和计数器标志，则活动标志（如果设置）表示自上次此连接的连接活动消息以来，此连接上已存在一些活动。如果为零，则表示自上次发送此连接的连接活动消息以来，此连接上没有任何活动。请求消息中未使用活动标志。
x: Unused
x:未使用
Traffic Count Field is not used in the request message. In the success response message, if the switch supports per connection traffic counting, the Traffic Count field must be set to the value of a free running, connection specific, 64-bit traffic counter counting traffic flowing across the specified connection. The value of the traffic counter is not modified by reading it. If per connection traffic counting is supported, the switch must report the Connection Activity result using the traffic count rather than using the Activity flag.
请求消息中未使用流量计数字段。在成功响应消息中，如果交换机支持每连接流量计数，则必须将“流量计数”字段设置为自由运行、特定于连接的64位流量计数器的值，该计数器对流经指定连接的流量进行计数。流量计数器的值不会通过读取来修改。如果支持每连接流量计数，交换机必须使用流量计数而不是使用活动标志来报告连接活动结果。
The format of the failure response is the same as the request message with the Number of Records field set to zero and no VC Activity records returned in the message. If the switch is incapable of detecting per connection activity, a failure response must be returned indicating, "The specified request is not implemented on this switch."
失败响应的格式与请求消息的格式相同，记录数字段设置为零，消息中不返回VC活动记录。如果交换机无法检测每个连接活动，则必须返回故障响应，指示“未在此交换机上实现指定的请求”
The Statistics messages are used to query the various port, connection, and QoS class traffic and error counters.
统计信息用于查询各种端口、连接和QoS类流量和错误计数器。
The Statistics request messages have the following format:
统计信息请求消息的格式如下：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| zero | VPI | VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| QoS Class Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| zero | VPI | VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| QoS Class Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
VPI VCI Fields identify the specific virtual path connection or virtual channel connection for which statistics are being requested. For a virtual path connection the Input VCI field is not used. For requests that do not require a virtual path connection or virtual channel connection to be specified, the VPI and VCI fields are not used.
VPI VCI字段标识请求统计信息的特定虚拟路径连接或虚拟通道连接。对于虚拟路径连接，不使用输入VCI字段。对于不需要指定虚拟路径连接或虚拟通道连接的请求，不使用VPI和VCI字段。
QoS Class Identifier Field identifies the QoS class for which statistics are being requested. This field is only used if the QoS Class Establishment message defined in section 9.4 is implemented.
QoS类标识符字段标识正在请求统计信息的QoS类。仅当实现第9.4节中定义的QoS类建立消息时，才使用此字段。
The success response for the Statistics message has the following format:
统计信息的成功响应具有以下格式：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| zero | VPI | VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| QoS Class Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Input Cell Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Input Frame Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Input Cell Discard Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Input Frame Discard Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Input HEC Error Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Input Invalid VPI/VCI Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Output Cell Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Output Frame Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Output Cell Discard Count +
| |
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| zero | VPI | VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| QoS Class Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Input Cell Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Input Frame Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Input Cell Discard Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Input Frame Discard Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Input HEC Error Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Input Invalid VPI/VCI Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Output Cell Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Output Frame Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Output Cell Discard Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Output Frame Discard Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Output Frame Discard Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Port VPI/VCI QoS Class Identifier Fields are the same as those of the request message.
端口VPI/VCI QoS类标识符字段与请求消息的字段相同。
Input Cell Count Output Cell Count Give the value of a free running 64-bit counter counting cells arriving at the input or departing from the output respectively.
输入单元格计数输出单元格计数给出自由运行的64位计数器的值，该计数器分别对到达输入或离开输出的单元格进行计数。
Input Frame Count Output Frame Count Give the value of a free running 64-bit counter counting frames (packets) arriving at the input or departing from the output respectively.
输入帧计数输出帧计数给出自由运行的64位计数器的值，该计数器分别对到达输入或离开输出的帧（数据包）进行计数。
Input Cell Discard Count Output Cell Discard Count Give the value of a free running 64-bit counter counting cells discarded due to queue overflow on an input port or on an output port respectively.
Input Cell Discard Count Output Cell Discard Count给出自由运行的64位计数器的值，该计数器分别对由于输入端口或输出端口上的队列溢出而丢弃的单元进行计数。
Input Frame Discard Count Output Frame Discard Count Give the value of a free running 64-bit counter counting frames discarded due to congestion on an input port or on an output port respectively.
Input Frame Discard Count Output Frame Discard Count给出自由运行的64位计数器的值，该计数器分别对输入端口或输出端口上因拥塞而丢弃的帧进行计数。
HEC Error Count Gives the value of a free running 64-bit counter counting cells discarded due to header checksum errors on arrival at an input port.
HEC Error Count给出自由运行64位计数器的值，该计数器对到达输入端口时由于报头校验和错误而丢弃的单元进行计数。
Invalid VPI/VCI Count Gives the value of a free running 64-bit counter counting cells discarded because their VPI/VCI is invalid on arrival at an input port. For a virtual channel connection an incoming VPI/VCI is invalid if no connection is currently established having that value of VPI/VCI. For a virtual path connection an incoming VPI is invalid if no connection is currently established having that value of VPI.
Invalid VPI/VCI Count给出自由运行的64位计数器计数单元的值，这些单元在到达输入端口时被丢弃，因为它们的VPI/VCI无效。对于虚拟通道连接，如果当前未建立具有该VPI/VCI值的连接，则传入VPI/VCI无效。对于虚拟路径连接，如果当前未建立具有该VPI值的连接，则传入VPI无效。
The Port Statistics message requests the statistics for the switch port specified in the Port field. The contents of the VPI/VCI and the QoS Class Identifier fields in the Port Statistics request message are ignored. All of the count fields in the success response message refer to per-port counts regardless of the connection or QoS class to which the cells belong. Any of the count fields in the success response message not supported by the port must be set to zero. The Port Statistics message is:
Port Statistics消息请求端口字段中指定的交换机端口的统计信息。忽略端口统计信息请求消息中VPI/VCI和QoS类标识符字段的内容。成功响应消息中的所有计数字段均指每个端口的计数，而与小区所属的连接或QoS类别无关。端口不支持的成功响应消息中的任何计数字段必须设置为零。端口统计信息为：
Message Type = 49
消息类型=49
The Connection Statistics message requests the statistics for the virtual channel connection specified in the VPI/VCI field, or the virtual path connection specified in the VPI field, that arrives on the switch input port specified in the Port field, regardless of the QoS class to which the cells belong. All of the count fields in the success response message refer only to the specified connection. The HEC Error Count and Invalid VPI/VCI Count fields are not connection specific and must be set to zero. Any of the other count fields not supported on a per connection basis must be set to zero in the success response message. The Connection Statistics message is:
Connection Statistics消息为到达port字段中指定的交换机输入端口的VPI/VCI字段中指定的虚拟通道连接或VPI字段中指定的虚拟路径连接请求统计信息，而与小区所属的QoS类别无关。成功响应消息中的所有计数字段仅引用指定的连接。HEC错误计数和无效VPI/VCI计数字段不是特定于连接的，必须设置为零。在成功响应消息中，每个连接都不支持的任何其他计数字段必须设置为零。连接统计信息为：
Message Type = 50
消息类型=50
The QoS Class Statistics message requests the statistics for the QoS class specified by the QoS Class Identifier field that arrives on the switch input port specified in the Port field, regardless of the connection to which the cells belong. The QoS Statistics message is only used if the QoS Class Establishment message defined in section 9.4 is implemented. The contents of the VPI/VCI fields in the QoS Class Statistics request message are ignored. All of the count fields in the success response message refer only to the specified QoS class. The HEC Error Count and Invalid VPI/VCI Count fields are not specific to a QoS class and must be set to zero. Any of the other count fields not supported on a per QoS class basis must be set to zero in the success response message. The QoS Class Statistics message is:
QoS Class Statistics消息请求QoS Class Identifier字段指定的QoS Class的统计信息，该字段到达在port字段中指定的交换机输入端口，而与小区所属的连接无关。仅当实现第9.4节中定义的QoS类建立消息时，才使用QoS统计信息。忽略QoS类统计信息请求消息中VPI/VCI字段的内容。成功响应消息中的所有计数字段仅引用指定的QoS类。HEC错误计数和无效VPI/VCI计数字段不是特定于QoS类的，必须设置为零。在成功响应消息中，每个QoS类不支持的任何其他计数字段必须设置为零。QoS类统计信息为：
Message Type = 51
消息类型=51
The Report Connection State message is used to request an input port to report the connection state for a single virtual channel connection, a single virtual path connection, or for the entire input port. The Report Connection State message is:
报告连接状态消息用于请求输入端口报告单个虚拟通道连接、单个虚拟路径连接或整个输入端口的连接状态。报告连接状态消息为：
Message Type = 52
消息类型=52
The Report Connection State request message has the following format:
报告连接状态请求消息的格式如下：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|A|V|x x| Input VPI | Input VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|A|V|x x| Input VPI | Input VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Input Port Identifies the port number of the input port for which the connection state is being requested.
Input Port标识正在请求连接状态的输入端口的端口号。
Flags
旗帜
A: All Connections If the All Connections flag is set, the message requests the connection state for all virtual path connections and virtual channel connections that arrive at the input port specified by the Input Port field. In this case the Input VPI and Input VCI fields and the VPI/VCI flag are unused.
A:All Connections如果设置了All Connections标志，则消息将请求到达输入端口字段指定的输入端口的所有虚拟路径连接和虚拟通道连接的连接状态。在这种情况下，未使用输入VPI和输入VCI字段以及VPI/VCI标志。
V: VPI/VCI If the All Connections flag is zero and the VPI/VCI flag is set, the message requests the connection state for the virtual path connection that arrives at the input port specified by the Input Port and Input VPI fields. If the specified Input VPI identifies a virtual path connection (i.e. a single switched virtual path) the state for that connection is requested. If the specified Input VPI identifies a virtual path containing virtual channel connections, the message requests the connection state for all virtual channel connections that belong to the specified virtual path. The Input VCI field is not used.
V:VPI/VCI如果“所有连接”标志为零并且设置了VPI/VCI标志，则消息将请求到达输入端口和输入VPI字段指定的输入端口的虚拟路径连接的连接状态。如果指定的输入VPI标识虚拟路径连接（即单个交换虚拟路径），则请求该连接的状态。如果指定的输入VPI标识包含虚拟通道连接的虚拟路径，则消息将请求属于指定虚拟路径的所有虚拟通道连接的连接状态。未使用输入VCI字段。
If the All Connections flag is zero and the VPI/VCI flag is also zero, the message requests the connection state for the virtual channel connection that arrives at the input port specified by the Port, Input VPI and Input VCI fields.
如果All Connections（所有连接）标志为零且VPI/VCI标志也为零，则消息将请求虚拟通道连接的连接状态，该连接将到达端口、输入VPI和输入VCI字段指定的输入端口。
x: Unused.
x:没用过。
Input VPI Input VCI Fields identify the specific virtual path connection, the specific virtual path, or the specific virtual channel connection for which connection state is being requested. For a virtual path connection (switched as a single virtual path connection) or a virtual path (switched as one or more virtual channel connections within the virtual path) the Input VCI field is not used. For requests that do not require a virtual path connection or virtual channel connection to be specified, the Input VPI and Input VCI fields are not used.
Input VPI Input VCI字段标识正在请求连接状态的特定虚拟路径连接、特定虚拟路径或特定虚拟通道连接。对于虚拟路径连接（切换为单个虚拟路径连接）或虚拟路径（切换为虚拟路径内的一个或多个虚拟通道连接），不使用输入VCI字段。对于不需要指定虚拟路径连接或虚拟通道连接的请求，不使用输入VPI和输入VCI字段。
The Report Connection State success response message has the following format:
报告连接状态成功响应消息的格式如下：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Connection Records ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Connection Records ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Input Port Is the same as the Input Port field in the request message. It identifies the port number of the input port for which the connection state is being reported.
输入端口与请求消息中的输入端口字段相同。它标识正在报告其连接状态的输入端口的端口号。
Sequence Number In the case that the requested connection state cannot be reported in a single success response message, each successive success response message in reply to the same
序列号在单个成功响应消息中无法报告请求的连接状态的情况下，每个连续的成功响应消息都响应相同的连接状态
request message must increment the Sequence Number. The Sequence Number of the first success response message, in response to a new request message, must be zero.
请求消息必须增加序列号。响应新请求消息的第一条成功响应消息的序列号必须为零。
Connection Records Each success response message must contain one or more Connection Records. Each Connection Record specifies a single point-to-point or point-to-multipoint virtual path connection or virtual channel connection. The number of Connection Records in a single Report Connection State success response must not cause the packet length to exceed the maximum transmission unit defined by the encapsulation. If the requested connection state cannot be reported in a single success response message, multiple success response messages must be sent. All success response messages that are sent in response to the same request message must have the same Input Port and Transaction Identifier fields as the request message. A single Connection Record must not be split across multiple success response messages. The More flag of the last Connection Record in a success response message indicates whether the response to the request has been completed or whether one or more further success response messages should be expected in response to the same request message.
连接记录每个成功响应消息必须包含一个或多个连接记录。每个连接记录指定一个单点对点或点对多点虚拟路径连接或虚拟通道连接。单个报告连接状态成功响应中的连接记录数不得导致数据包长度超过封装定义的最大传输单位。如果无法在单个成功响应消息中报告请求的连接状态，则必须发送多个成功响应消息。为响应同一请求消息而发送的所有成功响应消息必须具有与请求消息相同的输入端口和事务标识符字段。单个连接记录不能拆分为多个成功响应消息。成功响应消息中最后一条连接记录的“更多”标志指示对请求的响应是否已完成，或者是否应期望一条或多条进一步的成功响应消息响应同一请求消息。
Each Connection Record has the following format:
每个连接记录的格式如下：
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|A|V|P|M| Input VPI | Input VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Output Branch Records ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|A|V|P|M| Input VPI | Input VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Output Branch Records ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Flags
旗帜
A: All Connections V: VPI/VCI For the first Connection Record in each success response message the All Connections and the VPI/VCI flags must be the same as those of the request message. For successive Connection Records in the same success response message these flags are not used.
A:All Connections V:VPI/VCI对于每个成功响应消息中的第一条连接记录，所有连接和VPI/VCI标志必须与请求消息的标志相同。对于同一成功响应消息中的连续连接记录，不使用这些标志。
P: VPC The VPC flag, if set, indicates that the Connection Record refers to a virtual path connection. If zero, it indicates
P:VPC如果设置了VPC标志，则表示连接记录引用虚拟路径连接。如果为零，则表示
that the Connection Record refers to a virtual channel connection.
连接记录引用虚拟通道连接。
M: More If the More flag is set, it indicates that another Connection Record, in response to the same request message, will follow either in the same success response message or in a successive success response message. If the More flag is zero it indicates that this is the last Connection record in this success response message and that no further success response messages will be sent in response to the current request message. It indicates that the response to the request message is now complete.
M:More如果设置了More标志，则表示响应同一请求消息的另一个连接记录将在同一成功响应消息或后续成功响应消息中出现。如果“更多”标志为零，则表示这是此成功响应消息中的最后一条连接记录，并且不会再发送其他成功响应消息来响应当前请求消息。它表示现在已完成对请求消息的响应。
Input VPI Input VCI The input VPI and VCI of the connection specified in this Connection Record. If this Connection Record specifies a virtual path connection (the VPC flag is set) the Input VCI field is unused.
输入VPI输入VCI此连接记录中指定的连接的输入VPI和VCI。如果此连接记录指定了虚拟路径连接（设置了VPC标志），则输入VCI字段未使用。
Output Branch Records Each Connection Record must contain one or more Output Branch Records. Each Output Branch Record specifies a single output branch belonging to the connection identified by the Input VPI and Input VCI fields of the Connection Record. A point-to-point connection will require only a single Output Branch Record. A point-to-multipoint connection will require multiple Output Branch Records. The last Output Branch Record of each Connection Record is indicated by the Last Branch flag of the Output Branch Record. If a point-to-multipoint connection has more output branches than can fit in a single Connection Record contained within a single success response message, that connection may be reported using multiple Connection Records in multiple success response messages.
输出分支记录每个连接记录必须包含一个或多个输出分支记录。每个输出分支记录指定一个属于连接记录的输入VPI和输入VCI字段标识的连接的输出分支。点到点连接只需要一个输出分支记录。点对多点连接将需要多个输出分支记录。每个连接记录的最后一个输出分支记录由输出分支记录的最后一个分支标志指示。如果一个点对多点连接的输出分支多于包含在单个成功响应消息中的单个连接记录所能容纳的分支，则可以使用多个成功响应消息中的多个连接记录来报告该连接。
Each Output Branch Record has the following format:
每个输出分支记录具有以下格式：
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|L|x x x| Output VPI | Output VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|L|x x x| Output VPI | Output VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Output Port The output port of the switch to which this output branch is routed.
输出端口此输出分支路由到的交换机的输出端口。
Flags
旗帜
L: Last Branch The Last Branch flag, if set, indicates that this is the last Output Branch Record of this Connection Record. If zero, it indicates that one or more further Output Branch Records are to follow. If this is the last Output Branch Record in the message and the Last Branch flag is zero, further output branches belonging to the same connection will be given in another Connection Record. This Connection Record will be the first Connection Record in the next success response message. This Connection Record must have the same Input VPI and Input VCI values as the current Connection Record.
L:Last Branch如果设置了Last Branch标志，则表示这是此连接记录的最后一个输出分支记录。如果为零，则表示将遵循一个或多个进一步的输出分支记录。如果这是消息中的最后一个输出分支记录，并且最后一个分支标志为零，则属于同一连接的其他输出分支将在另一个连接记录中给出。此连接记录将是下一条成功响应消息中的第一条连接记录。此连接记录必须具有与当前连接记录相同的输入VPI和输入VCI值。
x: Unused.
x:没用过。
Output VPI Output VCI The output VPI and VCI of the output branch specified in this Output Branch Record. If this Output Branch Record is part of a Connection Record that specifies a virtual path connection (the VPC flag is set) the Output VCI field is unused.
输出VPI输出VCI此输出分支记录中指定的输出分支的输出VPI和VCI。如果此输出分支记录是指定虚拟路径连接（设置了VPC标志）的连接记录的一部分，则输出VCI字段未使用。
A Report Connection State request message may be issued regardless of the Port Status or the Line Status of the target switch port.
无论目标交换机端口的端口状态或线路状态如何，都可以发出报告连接状态请求消息。
If the Input Port of the request message is valid, and the All Connections flag is set, but there are no connections established on that port, a failure response message must be returned with the code field set to, "Failure specific to the particular message type." For the Report Connection State message, this failure code indicates that no connections matching the request message were found. This failure message should also be returned if the Input Port of the request message is valid, the All Connections flag is zero, and no connections are found on that port matching the specified virtual path connection, virtual path, or virtual channel connection.
如果请求消息的输入端口有效，并且设置了All Connections（所有连接）标志，但该端口上没有建立连接，则必须返回故障响应消息，并将报告连接状态消息的代码字段设置为“特定于特定消息类型的故障”，此故障代码表示未找到与请求消息匹配的连接。如果请求消息的输入端口有效，All Connections标志为零，并且在该端口上未找到与指定的虚拟路径连接、虚拟路径或虚拟通道连接匹配的连接，则还应返回此失败消息。
The configuration messages permit the controller to discover the capabilities of the switch. Three configuration request messages have been defined: Switch, Port, and All Ports.
配置消息允许控制器发现交换机的功能。定义了三个配置请求消息：交换机、端口和所有端口。
All configuration request messages have the following format:
所有配置请求消息的格式如下：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Switch Configuration message requests the global (non port-specific) configuration for the switch. The Switch Configuration message is:
交换机配置消息请求交换机的全局（非端口特定）配置。交换机配置消息为：
Message Type = 64
消息类型=64
The Port field is not used in the request message.
请求消息中未使用端口字段。
The Switch Configuration success response message has the following format:
交换机配置成功响应消息的格式如下：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Firmware Version Number | Window Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Switch Type | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| Switch Name |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Firmware Version Number | Window Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Switch Type | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| Switch Name |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Firmware Version Number The version number of the switch control firmware installed.
固件版本号安装的交换机控制固件的版本号。
Window Size The maximum number of unacknowledged request messages that may be transmitted by the controller without the possibility of loss. This field is used to prevent request messages being lost in the switch because of overflow in the receive buffer. The field is a hint to the controller. If desired, the controller may experiment with higher and
窗口大小控制器可以在不丢失的情况下传输的未确认请求消息的最大数量。此字段用于防止由于接收缓冲区溢出而导致交换机中的请求消息丢失。该字段是对控制器的提示。如果需要，控制器可以试验更高和更高的性能
lower window sizes to determine heuristically the best window size.
降低窗口大小，以启发式方式确定最佳窗口大小。
Switch Type A 16-bit field allocated by the manufacturer of the switch. (For these purposes the manufacturer of the switch is assumed to be the organization identified by the OUI in the Switch Name field.) The Switch Type identifies the product. When the Switch Type is combined with the OUI from the Switch Name the product is uniquely identified. Network Management may use this identification to obtain product related information from a database.
交换机类型交换机制造商分配的16位字段。（出于这些目的，假定交换机制造商是由交换机名称字段中的OUI标识的组织。）交换机类型标识产品。当开关类型与开关名称中的OUI组合时，产品将被唯一标识。网络管理可使用此标识从数据库获取产品相关信息。
Switch Name A 48-bit quantity that is unique within the operational context of the device. A 48-bit IEEE 802 MAC address, if available, may be used as the Switch Name. The most significant 24 bits of the Switch Name must be an Organizationally Unique Identifier (OUI) that identifies the manufacturer of the switch.
开关名称在设备的操作上下文中唯一的48位数量。48位IEEE 802 MAC地址（如果可用）可用作交换机名称。交换机名称的最高有效24位必须是标识交换机制造商的组织唯一标识符（OUI）。
The Port Configuration message requests the switch for the configuration information of a single switch port. The Port field in the request message specifies the port for which the configuration is requested. The Port Configuration message is:
端口配置消息向交换机请求单个交换机端口的配置信息。请求消息中的端口字段指定请求配置的端口。端口配置消息为：
Message Type = 65.
消息类型=65。
The Port Configuration success response message has the following format:
端口配置成功响应消息的格式如下：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|V|M|L|R| Min VPI |Q|x x x| Max VPI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Min VCI | Max VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Receive Cell Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transmit Cell Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Status | Port Type | Line Status | Priorities |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Physical Slot Number | Physical Port Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|V|M|L|R| Min VPI |Q|x x x| Max VPI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Min VCI | Max VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Receive Cell Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transmit Cell Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Status | Port Type | Line Status | Priorities |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Physical Slot Number | Physical Port Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Port The switch port to which the configuration information refers. Configuration information relating to both the input and the output sides of the switch port is given. Port numbers are 32 bits wide and allocated by the switch. The switch may choose to structure the 32 bits into subfields that have meaning to the physical structure of the switch hardware (e.g. physical slot and port). This structure may be indicated in the Physical Slot Number and Physical Port Number fields.
端口配置信息引用的交换机端口。给出了与交换机端口的输入侧和输出侧相关的配置信息。端口号为32位宽，由交换机分配。交换机可以选择将32位构造成对交换机硬件的物理结构（例如，物理插槽和端口）有意义的子字段。此结构可以在物理插槽号和物理端口号字段中指示。
Flags
旗帜
V: VP Switching The VP Switching flag, if set, indicates that this input port is capable of supporting virtual path switching. Else, if zero, it indicates that this input port is only capable of virtual channel switching.
V:VP交换VP交换标志（如果设置）表示此输入端口能够支持虚拟路径交换。否则，如果为零，则表示此输入端口只能进行虚拟通道切换。
M: Multicast Labels The Multicast Labels flag, if set, indicates that this output port is capable of labelling each output branch of a point-to-multipoint tree with a different label. If zero, it indicates that this output port is not able to label
M：多播标签多播标签标志（如果设置）表示此输出端口能够使用不同的标签标记点对多点树的每个输出分支。如果为零，则表示此输出端口无法标记
each output branch of a point-to-multipoint tree with a different label.
具有不同标签的点对多点树的每个输出分支。
L: Logical Multicast The Logical Multicast flag, if set, indicates that this output port is capable of supporting more than a single branch from any point-to-multipoint connection. This capability is often referred to as logical multicast. If zero, it indicates that this output port can only support a single output branch from each point-to-multipoint connection.
L：逻辑多播如果设置了逻辑多播标志，则表示此输出端口能够支持从任意点到多点连接的多个分支。这种能力通常被称为逻辑多播。如果为零，则表示此输出端口只能支持从每个点到多点连接的单个输出分支。
R: Label Range The Label Range flag, if set, indicates that this switch port is capable of reallocating its VPI label range or its VCI label range and therefore accepts the Label Range message. Else, if zero, it indicates that this port does not accept Label Range messages.
R：标签范围标签范围标志（如果设置）表示此交换机端口能够重新分配其VPI标签范围或VCI标签范围，因此接受标签范围消息。否则，如果为零，则表示此端口不接受标签范围消息。
Q: QoS The QoS flag, if set, indicates that this switch port is capable of handling the Quality of Service messages defined in section 9 of this specification. Else, if zero, it indicates that this port does not accept the Quality of Service messages.
Q:QoS如果设置QoS标志，则表明该交换机端口能够处理本规范第9节中定义的服务质量消息。否则，如果为零，则表示此端口不接受服务质量消息。
x: Unused
x:未使用
Min VPI The default minimum value of dynamically assigned incoming VPI that the connection table on the input port supports and that may be controlled by GSMP. This value is not changed as a result of the Label Range message.
Min VPI输入端口上的连接表支持的动态分配的传入VPI的默认最小值，可由GSMP控制。此值不会因标签范围消息而更改。
Max VPI The default maximum value of dynamically assigned incoming VPI that the connection table on the input port supports and that may be controlled by GSMP. This value is not changed as a result of the Label Range message.
Max VPI输入端口上的连接表支持的动态分配的传入VPI的默认最大值，可由GSMP控制。此值不会因标签范围消息而更改。
At power-on, after a hardware reset, and after the Reset Input Port function of the Port Management message, the input port must handle all values of VPI within the range Min VPI to Max VPI inclusive and GSMP must be able to control all values within this range. It should be noted that the range Min VPI to Max VPI refers only to the incoming VPI range that can be supported by the associated port. No restriction is placed on the values of outgoing
通电时，硬件复位后，以及端口管理消息的复位输入端口功能后，输入端口必须处理最小VPI至最大VPI范围内的所有VPI值，GSMP必须能够控制该范围内的所有值。应该注意的是，最小VPI到最大VPI的范围仅指关联端口可以支持的传入VPI范围。对传出的值没有限制
VPIs that may be written into the cell header. If the switch does not support virtual paths it is acceptable for both Min VPI and Max VPI to specify the same value, most likely zero.
VPI，可写入单元格标题。如果交换机不支持虚拟路径，则Min VPI和Max VPI都可以指定相同的值，很可能为零。
Use of the Label Range message allows the range of VPIs supported by the port to be changed. However, the Min VPI and Max VPI fields in the Port Configuration and All Ports Configuration messages always report the same default values regardless of the operation of the Label Range message.
使用标签范围消息可以更改端口支持的VPI范围。但是，无论标签范围消息的操作如何，端口配置和所有端口配置消息中的最小VPI和最大VPI字段始终报告相同的默认值。
Min VCI The default minimum value of dynamically assigned incoming VCI that the connection table on the input port can support and may be controlled by GSMP. This value is not changed as a result of the Label Range message.
Min VCI输入端口上的连接表可以支持并可由GSMP控制的动态分配的传入VCI的默认最小值。此值不会因标签范围消息而更改。
Max VCI The default maximum value of dynamically assigned incoming VCI that the connection table on the input port can support and may be controlled by GSMP. This value is not changed as a result of the Label Range message.
Max VCI输入端口上的连接表可以支持并可由GSMP控制的动态分配的传入VCI的默认最大值。此值不会因标签范围消息而更改。
At power-on, after a hardware reset, and after the Reset Input Port function of the Port Management message, the input port must handle all values of VCI within the range Min VCI to Max VCI inclusive, for each of the virtual paths in the range Min VPI to Max VPI inclusive, and GSMP must be able to control all values within this range. It should be noted that the range Min VCI to Max VCI refers only to the incoming VCI range that can be supported by the associated port on each of the virtual paths in the range Min VPI to Max VPI. No restriction is placed on the values of outgoing VCIs that may be written into the cell header.
通电时，硬件复位后，以及端口管理消息的复位输入端口功能后，输入端口必须处理最小VCI到最大VCI范围内的所有VCI值，对于最小VPI到最大VPI范围内的每个虚拟路径，GSMP必须能够控制此范围内的所有值。应注意，最小VCI到最大VCI范围仅指最小VPI到最大VPI范围内每个虚拟路径上的关联端口可支持的传入VCI范围。对可能写入单元格标题的传出VCI的值没有限制。
Use of the Label Range message allows the range of VCIs to be changed on each VPI supported by the port. However, the Min VCI and Max VCI fields in the Port Configuration and All Ports Configuration messages always report the same default values regardless of the operation of the Label Range message.
使用标签范围消息可以更改端口支持的每个VPI上的VCI范围。但是，无论标签范围消息的操作如何，端口配置和所有端口配置消息中的最小VCI和最大VCI字段始终报告相同的默认值。
For a port over which the GSMP protocol is operating, the VCI of the GSMP control channel may or may not be reported as lying within the range Min VCI to Max VCI. A switch should honor a connection request message that specifies
对于GSMP协议正在运行的端口，GSMP控制信道的VCI可能在最小VCI到最大VCI的范围内，也可能不在报告范围内。交换机应接受指定的连接请求消息
the VCI value of the GSMP control channel even if it lies outside the range Min VCI to Max VCI.
GSMP控制通道的VCI值，即使它位于最小VCI到最大VCI范围之外。
Receive Cell Rate The maximum rate of cells that may arrive at the input port in cells/s.
接收单元速率可能到达输入端口的最大单元速率，单位为cells/s。
Transmit Cell Rate The maximum rate of cells that may depart from the output port in cells/s. (The transmit cell rate of the output port may be changed by the Set Transmit Cell Rate function of the Port Management message.)
传输信元速率可能离开输出端口的信元的最大速率，单位为信元/秒。（输出端口的发送信元速率可通过端口管理消息的设置发送信元速率功能进行更改。）
Port Status Gives the administrative state of the port. The defined values of the Port Status field are:
端口状态提供端口的管理状态。端口状态字段的定义值为：
Available: Port Status = 1. The port is available to both send and receive cells. When a port changes to the Available state from any other administrative state, all dynamically assigned virtual connections must be cleared and a new Port Session Number must be generated.
可用：端口状态=1。该端口可用于发送和接收单元。当端口从任何其他管理状态更改为可用状态时，必须清除所有动态分配的虚拟连接，并生成新的端口会话号。
Unavailable: Port Status = 2. The port has intentionally been taken out of service. No cells will be transmitted from this port. No cells will be received by this port.
Unavailable: Port Status = 2. The port has intentionally been taken out of service. No cells will be transmitted from this port. No cells will be received by this port.translate error, please retry
Internal Loopback: Port Status = 3. The port has intentionally been taken out of service and is in internal loopback: cells arriving at the output port from the switch fabric are looped through to the input port to return to the switch fabric. All of the ATM functions of the input port above the physical layer, e.g. header translation, are performed upon the looped back cells.
内部环回：端口状态=3。该端口已被故意停止服务并处于内部环回中：从交换机结构到达输出端口的单元被环回到输入端口以返回交换机结构。物理层上输入端口的所有ATM功能，例如报头转换，都是在环回信元上执行的。
External Loopback: Port Status = 4. The port has intentionally been taken out of service and is in external loopback: cells arriving at the input port from the external communications link are immediately looped back to the communications link at the physical layer without entering the input port. None of the ATM functions of the input port above the physical layer are performed upon the looped back cells.
外部环回：端口状态=4。该端口已故意停止服务并处于外部环回中：从外部通信链路到达输入端口的单元将立即环回物理层的通信链路，而不进入输入端口。物理层上的输入端口的ATM功能都不会在环回信元上执行。
Bothway Loopback: Port Status = 5. The port has intentionally been taken out of service and is in both internal and external loopback.
双向环回：端口状态=5。该端口已被故意停用，并且处于内部和外部环回中。
The Port Status of the port over which the GSMP session controlling the switch is running, must be declared Available. The controller will ignore any other Port status for this port. The Port Status of switch ports after power-on initialization is not defined by GSMP.
控制交换机的GSMP会话正在其上运行的端口的端口状态必须声明为可用。控制器将忽略此端口的任何其他端口状态。GSMP未定义开机初始化后交换机端口的端口状态。
Port Type The type of physical transmission interface for this port. The values for this field are defined by the atmIfType object specified in the Ipsilon IP Switch MIB [IpsilonMIB].
端口类型此端口的物理传输接口类型。此字段的值由Ipsilon IP交换机MIB[IpsilonMIB]中指定的atmIfType对象定义。
Line Status The status of the physical transmission medium connected to the port. The defined values of the Line Status field are:
线路状态连接到端口的物理传输介质的状态。行状态字段的定义值为：
Up: Line Status = 1. The line is able to both send and receive cells. When the Line Status changes to Up from either the Down or Test states, a new Port Session Number must be generated.
向上：线路状态=1。该线路可以发送和接收小区。当线路状态从“向下”或“测试”状态更改为“向上”时，必须生成新的端口会话号。
Down: Line Status = 2. The line is unable either to send or receive cells or both.
向下：线路状态=2。线路无法发送或接收单元格，或两者都无法。
Test: Line Status = 3. The port or line is in a test mode, for example, power-on test.
测试：线路状态=3。端口或线路处于测试模式，例如通电测试。
Priorities The number of different priority levels that this output port can assign to virtual connections. Zero is invalid in this field. If an output port is able to support "Q" priorities, the highest priority is numbered zero and the lowest priority is numbered "Q-1". The ability to offer different qualities of service to different connections based upon their priority is assumed to be a property of the output port of the switch. It may be assumed that for connections that share the same output port, an ATM cell on a connection with a higher priority is much more likely to exit the switch before an ATM cell on a connection with a lower priority if they are both in the switch at the same time.
优先级此输出端口可以分配给虚拟连接的不同优先级的数量。零在此字段中无效。如果输出端口能够支持“Q”优先级，则最高优先级编号为零，最低优先级编号为“Q-1”。根据不同连接的优先级向其提供不同服务质量的能力被认为是交换机输出端口的特性。可以假设，对于共享同一输出端口的连接，如果具有较高优先级的连接上的ATM信元同时位于交换机中，则在具有较低优先级的连接上的ATM信元之前，具有较高优先级的连接上的ATM信元更有可能退出交换机。
Physical Slot Number The physical location of the slot in which the port is located. It is an unsigned 16-bit integer that can take any value except 0xFFFF. The value 0xFFFF is used to indicate "unknown." The Physical Slot Number is not used by the GSMP protocol. It is provided to assist network management in functions such as logging, port naming, and graphical representation.
物理插槽号端口所在插槽的物理位置。它是一个无符号16位整数，可以接受除0xFFFF以外的任何值。值0xFFFF用于指示“未知”。GSMP协议不使用物理插槽号。它用于在日志记录、端口命名和图形表示等功能方面协助网络管理。
Physical Port Number The physical location of the port within the slot in which the port is located. It is an unsigned 16-bit integer that can take any value except 0xFFFF. The value 0xFFFF is used to indicate "unknown." The Physical Port Number is not used by the GSMP protocol. It is provided to assist network management in functions such as logging, port naming, and graphical representation.
物理端口号端口所在插槽中端口的物理位置。它是一个无符号16位整数，可以接受除0xFFFF以外的任何值。值0xFFFF用于指示“未知”。GSMP协议不使用物理端口号。它用于在日志记录、端口命名和图形表示等功能方面协助网络管理。
There must be a one to one mapping between Port Number and the Physical Slot Number and Physical Port Number combination. Two different Port Numbers must not yield the same Physical Slot Number and Physical Port Number combination. The same Port Number must yield the same Physical Slot Number and Physical Port Number within a single GSMP session. If both Physical Slot Number and Physical Port Number indicate "unknown" the physical location of switch ports may be discovered by looking up the product identity in a database to reveal the physical interpretation of the 32-bit Port Number.
端口号与物理插槽号和物理端口号组合之间必须存在一对一映射。两个不同的端口号不得产生相同的物理插槽号和物理端口号组合。同一端口号必须在单个GSMP会话中产生相同的物理插槽号和物理端口号。如果物理插槽号和物理端口号都指示“未知”，则可以通过在数据库中查找产品标识来发现交换机端口的物理位置，以显示32位端口号的物理解释。
The All Ports Configuration message requests the switch for the configuration information of all of its ports. The All Ports Configuration message is:
All Ports Configuration（所有端口配置）消息请求交换机提供其所有端口的配置信息。所有端口配置消息为：
Message Type = 66
消息类型=66
The Port field is not used in the request message.
请求消息中未使用端口字段。
The All Ports Configuration success response message has the following format:
所有端口配置成功响应消息的格式如下：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number of Records | Port Record Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Port Records ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number of Records | Port Record Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Port Records ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Number of Records Field gives the total number of Port Records to be returned in response to the All Ports Configuration request message. The number of port records in a single All Ports Configuration success response must not cause the packet length to exceed the maximum transmission unit defined by the encapsulation. If a switch has more ports than can be sent in a single success response message it must send multiple success response messages. All success response messages that are sent in response to the same request message must have the same Transaction Identifier as the request message and the same value in the Number of Records field. All success response messages that are sent in response to the same request message, except for the last message, must have the result field set to "More." The last message, or a single success response message, must have the result field set to "Success." All Port records within a success response message must be complete, i.e. a single Port record must not be split across multiple success response messages.
Number of Records（记录数）字段提供响应All Ports Configuration（所有端口配置）请求消息返回的端口记录总数。单个所有端口配置成功响应中的端口记录数不得导致数据包长度超过封装定义的最大传输单位。如果交换机的端口数超过了单个成功响应消息中可以发送的端口数，则它必须发送多个成功响应消息。为响应同一请求消息而发送的所有成功响应消息必须与请求消息具有相同的事务标识符，并且在记录数字段中具有相同的值。为响应同一请求消息而发送的所有成功响应消息（最后一条消息除外）的结果字段必须设置为“更多”。最后一条消息或单个成功响应消息的结果字段必须设置为“成功”。成功响应消息中的所有端口记录必须完整，也就是说，单个端口记录不得拆分为多个成功响应消息。
Port Record Length Field gives the length of each port record in bytes. This is currently 32 but the Port Record Length field allows for the future definition of further fields at the end of the port record while preserving compatibility with earlier versions of the protocol.
端口记录长度字段以字节为单位给出每个端口记录的长度。当前为32，但端口记录长度字段允许将来在端口记录末尾定义更多字段，同时保留与协议早期版本的兼容性。
Port Records Follow in the remainder of the message. Each port record has the following format:
端口记录位于消息的其余部分。每个端口记录具有以下格式：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|V|M|L|R| Min VPI |Q|x x x| Max VPI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Min VCI | Max VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Receive Cell Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transmit Cell Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Status | Port Type | Line Status | Priorities |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Physical Slot Number | Physical Port Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|V|M|L|R| Min VPI |Q|x x x| Max VPI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Min VCI | Max VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Receive Cell Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transmit Cell Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Status | Port Type | Line Status | Priorities |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Physical Slot Number | Physical Port Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The definition of the fields in the Port Record is exactly the same as that of the Port Configuration message.
端口记录中字段的定义与端口配置消息的定义完全相同。
Event messages allow the switch to inform the controller of certain asynchronous events. Event messages are not acknowledged. The Result field and the Code field in the message header are not used and should be set to zero. Event messages are not sent during initialization. Event messages have the following format:
事件消息允许交换机通知控制器某些异步事件。未确认事件消息。消息头中的结果字段和代码字段不使用，应设置为零。初始化期间不发送事件消息。事件消息的格式如下：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Event Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| zero | VPI | VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Event Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| zero | VPI | VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Event Sequence Number The current value of the Event Sequence Number for the specified port. The Event Sequence Number is set to zero when the port is initialized. It is incremented by one each time the port detects an asynchronous event that the switch would normally report via an Event message. The Event Sequence Number must be incremented each time an event occurs even if the switch is prevented from sending an Event message due to the action of the flow control.
事件序列号指定端口的事件序列号的当前值。端口初始化时，事件序列号设置为零。每当端口检测到交换机通常通过事件消息报告的异步事件时，该值将递增一。每次发生事件时，事件序列号必须增加，即使由于流控制的操作而阻止交换机发送事件消息。
VPI/VCI Field gives the VPI/VCI to which the event message refers. If this field is not required by the event message it is set to zero.
VPI/VCI字段提供事件消息引用的VPI/VCI。如果事件消息不需要此字段，则将其设置为零。
Each switch port must maintain an Event Sequence Number and a set of Event Flags, one Event Flag for each type of Event message. When a switch port sends an Event message it must set the Event Flag on that port corresponding to the type of the event. The port is not permitted to send another Event message of the same type until the Event Flag has been reset. Event Flags are reset by the "Reset Event Flags" function of the Port Management message. This is a simple flow control preventing the switch from flooding the controller with event messages. The Event Sequence Number of the port must be incremented every time an event is detected on that port even if the port is prevented from reporting the event due to the action of the flow control. This allows the controller to detect that it has not been informed of some events that have occurred on the port due to the action of the flow control.
每个交换机端口必须维护一个事件序列号和一组事件标志，每种类型的事件消息一个事件标志。当交换机端口发送事件消息时，它必须在该端口上设置与事件类型对应的事件标志。在重置事件标志之前，不允许端口发送另一个相同类型的事件消息。事件标志由端口管理消息的“重置事件标志”功能重置。这是一个简单的流控制，防止交换机向控制器发送事件消息。每次在该端口上检测到事件时，必须增加该端口的事件序列号，即使该端口由于流量控制的操作而无法报告该事件。这使控制器能够检测到由于流量控制的动作而在端口上发生的某些事件未被通知。
The Port Up message informs the controller that the Line Status of a port has changed from either the Down or Test state to the Up state. When the Line Status of a switch port changes to the Up state from either the Down or Test state a new Port Session Number must be generated, preferably using some form of random number. The new Port Session Number is given in the Port Session Number field. The VPI/VCI field is not used and is set to zero. The Port Up message is:
端口上升消息通知控制器端口的线路状态已从下降或测试状态更改为上升状态。当交换机端口的线路状态从下降或测试状态更改为上升状态时，必须生成新的端口会话号，最好使用某种形式的随机数。新端口会话号在端口会话号字段中给出。VPI/VCI字段未使用，设置为零。端口向上消息为：
Message Type = 80
消息类型=80
The Port Down message informs the controller that the Line Status of a port has changed from the Up state to the Down state. This message will be sent to report link failure if the switch is capable of detecting link failure. The port session number that was valid before
端口下降消息通知控制器端口的线路状态已从上升状态更改为下降状态。如果交换机能够检测到链路故障，将发送此消息以报告链路故障。之前有效的端口会话号
the port went down is reported in the Port Session Number field. The VPI/VCI field is not used and is set to zero. The Port Down message is:
端口会话号字段中会报告端口关闭。VPI/VCI字段未使用，设置为零。端口关闭消息为：
Message Type = 81
消息类型=81
The Invalid VPI/VCI message is sent to inform the controller that one or more cells have arrived at an input port with a VPI/VCI that is currently not allocated to an assigned connection. The input port is indicated in the Port field, and the VPI/VCI in the VPI/VCI field. The Invalid VPI/VCI message is:
发送无效VPI/VCI消息以通知控制器，一个或多个单元已到达输入端口，且VPI/VCI当前未分配给分配的连接。输入端口在端口字段中指示，VPI/VCI在VPI/VCI字段中指示。无效的VPI/VCI消息为：
Message Type = 82
消息类型=82
The New Port message informs the controller that a new port has been added to the switch. The port number of the new port is given in the Port field. A new Port Session Number must be assigned, preferably using some form of random number. The new Port Session Number is given in the Port Session Number field. The state of the new port is undefined so the VPI/VCI field is not used and is set to zero. The New Port message is:
New Port（新端口）消息通知控制器新端口已添加到交换机。新端口的端口号在端口字段中给出。必须分配新的端口会话号，最好使用某种形式的随机数。新端口会话号在端口会话号字段中给出。新端口的状态未定义，因此不使用VPI/VCI字段，并将其设置为零。新端口消息为：
Message Type = 83
消息类型=83
The Dead Port message informs the controller that a port has been removed from the switch. The port number of the port is given in the Port field. The Port Session Number that was valid before the port was removed is reported in the Port Session Number field. The VPI/VCI fields are not used and are set to zero. The Dead Port message is:
死区端口消息通知控制器一个端口已从交换机上移除。端口的端口号在端口字段中给出。在端口会话号字段中报告删除端口之前有效的端口会话号。VPI/VCI字段未使用，设置为零。死端口消息是：
Message Type = 84
消息类型=84
The GSMP Quality of Service (QoS) messages allow a controller to group virtual path connections and virtual channel connections into QoS classes, and to allocate QoS resources to both QoS classes and to individual connections. At initialization, the switch describes its QoS capabilities to the controller, in terms of the abstract switch model, using the QoS Configuration message. The controller issues
GSMP服务质量（QoS）消息允许控制器将虚拟路径连接和虚拟通道连接分组为QoS类，并将QoS资源分配给QoS类和单个连接。在初始化时，交换机使用QoS配置消息，根据抽象交换机模型向控制器描述其QoS能力。控制员的问题
Scheduler Establishment messages to configure the scheduler on each switch output port. It also issues QoS Class Establishment messages to configure QoS classes. Connections may be added to, or deleted from, a QoS class using the QoS Connection Management message. QoS resources may also be assigned to individual connections using the QoS Connection Management message. Connections that only require the scheduler may use the simple connection management messages defined in Section 3, "Connection Management Messages."
调度器建立消息，用于在每个交换机输出端口上配置调度器。它还发出QoS类建立消息来配置QoS类。可以使用QoS连接管理消息将连接添加到QoS类或从QoS类删除连接。还可以使用QoS连接管理消息将QoS资源分配给各个连接。仅需要调度器的连接可以使用第3节“连接管理消息”中定义的简单连接管理消息
The abstract switch model, fig. 1, is the means by which a switch can describe its fundamental QoS capabilities to a controller. It consists of four main functions: a policer, a classifier, a regulator, and a scheduler. The classifier groups multiple connections (VPCs or VCCs) together into a QoS class such that QoS resources may be shared by the QoS class as a whole. Within a QoS class there is no differentiation between members of the class in terms of QoS resources received. However, the ordering of cells within each constituent VPC or VCC must be preserved on exit from the switch. Connections are not required to be aggregated into a QoS class with other connections; they may be allocated individual QoS resources.
抽象交换机模型（图1）是交换机向控制器描述其基本QoS能力的方法。它由四个主要功能组成：策略器、分类器、调节器和调度器。分类器将多个连接（VPC或VCC）一起分组到QoS类中，使得QoS资源可以由QoS类作为一个整体共享。在一个QoS类中，该类的成员之间在接收的QoS资源方面没有区别。但是，从交换机退出时，必须保留每个组成VPC或VCC内的单元顺序。连接不需要与其他连接聚合到QoS类中；可以为它们分配单独的QoS资源。
VPC/VCCs Policer Classifier Regulator Scheduler
VPC/VCCs策略器分类器调节器调度器
+--+ +----+ +--------+
-------->| |---->| | | |
+--+ | | | |
| | | |
+--+ | | +----+ | |
-------->| |---->| | | |--------->| |
+--+ | | | |conforming| |
| |------>| | | |
+--+ | | QoS | | | |
-------->| |---->| | Class | |--------->| |
+--+ | | +----+ excess | |
| | | |
+--+ | | | |
-------->| |---->| | | |
+--+ +----+ | |
| |
| | Output
| | Port
| |---------->
| |
| |
+--+ +----+ | |
-------->| |---->| | | |
+--+ | | | |
| | | |
+--+ | | +----+ | |
-------->| |---->| | | |--------->| |
+--+ | | | |conforming| |
| |------>| | | |
+--+ | | QoS | | | |
-------->| |---->| | Class | |--------->| |
+--+ | | +----+ excess | |
| | | |
+--+ | | | |
-------->| |---->| | | |
+--+ +----+ | |
+--------+
+--+ +----+ +--------+
-------->| |---->| | | |
+--+ | | | |
| | | |
+--+ | | +----+ | |
-------->| |---->| | | |--------->| |
+--+ | | | |conforming| |
| |------>| | | |
+--+ | | QoS | | | |
-------->| |---->| | Class | |--------->| |
+--+ | | +----+ excess | |
| | | |
+--+ | | | |
-------->| |---->| | | |
+--+ +----+ | |
| |
| | Output
| | Port
| |---------->
| |
| |
+--+ +----+ | |
-------->| |---->| | | |
+--+ | | | |
| | | |
+--+ | | +----+ | |
-------->| |---->| | | |--------->| |
+--+ | | | |conforming| |
| |------>| | | |
+--+ | | QoS | | | |
-------->| |---->| | Class | |--------->| |
+--+ | | +----+ excess | |
| | | |
+--+ | | | |
-------->| |---->| | | |
+--+ +----+ | |
+--------+
Fig. 1: Abstract Switch Model
图1：抽象交换机模型
The policer is a single input, single output device that can discard or tag cells. A policer may be applied to police each individual connection. A policer may also be applied to police the aggregate traffic of a QoS class. The policer is used to enforce an upper bound on the traffic on a connection or on a QoS class.
policer是一个单输入单输出设备，可以丢弃或标记单元格。可以应用一个policr来管理每个单独的连接。还可以应用policr来监控QoS类的聚合流量。policr用于对连接或QoS类上的流量强制执行上限。
The regulator follows the policer and classifier. It offers either a policing function or a shaping function. The policing function evaluates cells as conforming to the rate specified by the regulator parameters or as being in excess of that rate. One of three actions can be specified to be taken for each cell as a result of this evaluation: tagging, discard or differentiated scheduling. Tagging sets the CLP bit of cells deemed to be in excess of the rate defined by the regulator parameters. The discard function discards excess cells. The differentiated scheduling function allows conforming cells and excess cells to be scheduled for service at different points in the scheduler. This would allow conforming cells, for example, to receive service with a QoS guarantee, whereas excess cells receive best-effort service. The implementation of differentiated scheduling, however, is complicated by the requirement not to reorder cells within each connection.
调节器遵循策略器和分类器。它提供了监管功能或塑造功能。监控功能评估单元格是否符合调节器参数指定的速率或是否超过该速率。根据此评估结果，可以为每个单元格指定要执行的三个操作之一：标记、放弃或差异化调度。标记设置被视为超过调节器参数定义的速率的电池CLP位。discard函数丢弃多余的单元格。区分调度功能允许在调度器的不同点调度一致性小区和多余小区的服务。例如，这将允许一致性小区接收具有QoS保证的服务，而多余的小区接收尽力而为的服务。然而，由于不需要对每个连接中的单元重新排序，差异化调度的实现变得复杂。
The shaping function of the regulator paces cells out, on each QoS class or individual connection, at the rate specified by the regulator parameters. No jitter requirement may be specified, nor is any specific guarantee of jitter given. If traffic arrives on any QoS class or individual connection at a greater rate than the output rate specified, that traffic will be delayed. If the delayed traffic for any QoS class or individual connection exceeds a bound, discard will occur. Differentiated scheduling is supported by the shaper but its application to shaping is somewhat different than its application to policing. Conforming traffic is that traffic which leaves the shaper as a result of the shaping process. The conforming pointer specifies the point in the scheduler structure where such traffic is scheduled for output. (This is typically the highest priority of the scheduler but the GSMP specification permits other priorities to be specified.) If an excess pointer is also enabled for a particular QoS class or individual connection, traffic in excess of the rate specified by the shaper may also be transmitted. The position of the excess pointer in the scheduler structure determines the undefined amount of additional traffic that will be supported. The excess traffic may be tagged if required, if tagging is supported. The excess pointer will receive the same share of bandwidth that a best-effort class or connection would receive at the same location in the scheduler structure.
调节器的整形功能以调节器参数指定的速率在每个QoS类或单个连接上对小区进行调整。可能未规定抖动要求，也未给出抖动的任何具体保证。如果流量到达任何QoS类或单个连接的速率大于指定的输出速率，则该流量将被延迟。如果任何QoS类或单个连接的延迟流量超过一个界限，将发生丢弃。成形器支持差异化调度，但其在成形中的应用与在警务中的应用有所不同。一致性通信量是由于整形过程而离开整形器的通信量。一致指针指定调度程序结构中的一点，在该点上调度此类通信量以进行输出。（这通常是调度器的最高优先级，但GSMP规范允许指定其他优先级。）如果还为特定QoS类或单个连接启用了多余指针，则也可以传输超过整形器指定速率的流量。调度程序结构中多余指针的位置决定将支持的未定义的额外通信量。如果支持标记，如果需要，可以标记多余的流量。多余的指针将接收与“尽力而为”类或连接在调度程序结构中的同一位置接收的带宽相同的共享。
The location of the classifier and regulator functions in the switch is important. If the classifier is located on an input port, only virtual connections that arrive at that input port may be aggregated into a QoS class. If the classifier is centralized, or located on an output port, virtual connections that arrive at any input port may be aggregated into the same QoS class. If the regulator is located on an output port all virtual connections within a QoS class passing through that regulator must exit the switch at that output port.
分类器和调节器功能在开关中的位置很重要。如果分类器位于输入端口上，则只有到达该输入端口的虚拟连接可以聚合为QoS类。如果分类器是集中式的，或者位于输出端口上，则到达任何输入端口的虚拟连接可以聚合到相同的QoS类中。如果调节器位于输出端口上，通过该调节器的QoS类中的所有虚拟连接必须在该输出端口退出交换机。
However, if the regulator is centralized, or located on an input port, virtual connections that are part of the same QoS class may be switched to different output ports. Each switch port must specify the location of its classifier and regulator functions.
然而，如果调节器是集中式的，或者位于输入端口上，则属于同一QoS等级的虚拟连接可以切换到不同的输出端口。每个交换机端口必须指定其分类器和调节器功能的位置。
The scheduler is located on the output port, fig. 2. It distributes the bandwidth of the output link between the QoS classes and individual connections. It is a two-level scheduler: a priority scheduler at one level and a FIFO or a weighted scheduler at the other. Up to 255 strict priority levels may be supported. Traffic in any specific priority level may only be transmitted if no traffic is queued for transmission in any higher priority level. Within each priority level a weighted scheduler may be defined. Each leaf of the scheduler tree is connected to a waiting room. The waiting room has two functions. When it receives service from the scheduler, it must select a QoS class or individual connection for transmission. When it is notified of traffic arrival on a QoS class or connection, it must decide whether there is enough room left in the waiting room to accept the traffic, else that traffic must be discarded. The waiting room has a size parameter indicating how much traffic may be accepted. Other queueing parameters may be attached to the waiting room. Multiple conforming and excess pointers from the regulators may point to each waiting room. Within a waiting room, the scheduling of multiple connections sharing that waiting room may support weighted sharing between the connections.
调度器位于输出端口上，如图2所示。它在QoS类和各个连接之间分配输出链路的带宽。它是一个两级调度器：一级是优先级调度器，另一级是FIFO或加权调度器。最多可支持255个严格优先级。只有在没有流量排队等待任何更高优先级的传输时，才能传输任何特定优先级的流量。在每个优先级中，可以定义加权调度程序。调度程序树的每个叶子都连接到一个等候室。候车室有两个功能。当它从调度器接收服务时，它必须选择一个QoS类或单个连接进行传输。当在QoS类或连接上收到流量到达的通知时，它必须决定等待室中是否有足够的空间来接受流量，否则必须丢弃该流量。候车室有一个大小参数，指示可接受的交通量。其他排队参数可附加到等候室。来自监管机构的多个合格和多余指针可能指向每个等候室。在等待室中，共享该等待室的多个连接的调度可能支持连接之间的加权共享。
From Waiting FIFO/Weighted Priority Regulator Room Scheduler Scheduler
来自等待的FIFO/加权优先级调节器室调度器
Net +---+
+------+ Weight | |
---------->| |-%-------->| 0 |------\
+------+ | | \
+---+ \
---------->+------+ |
| |-%--\ +---+ |
---------->+------+ \---->| | |
| 1 |---\ |
+------+ /---->| | \ \
---------->| |-%--/ +---+ \ \ +---+
+------+ \ \-->| |
\----->| |--------->
---------->+------+ /-->| | Output
---------->| |-%-\ / +---+ Port
---------->+------+ \ /
\ +---+ /
+------+ \--->| | /
---------->| |-%-------->| 2 |-----/
+------+ /--->| |
/ +---+
+------+ /
---------->| |-%-/
+------+
Net +---+
+------+ Weight | |
---------->| |-%-------->| 0 |------\
+------+ | | \
+---+ \
---------->+------+ |
| |-%--\ +---+ |
---------->+------+ \---->| | |
| 1 |---\ |
+------+ /---->| | \ \
---------->| |-%--/ +---+ \ \ +---+
+------+ \ \-->| |
\----->| |--------->
---------->+------+ /-->| | Output
---------->| |-%-\ / +---+ Port
---------->+------+ \ /
\ +---+ /
+------+ \--->| | /
---------->| |-%-------->| 2 |-----/
+------+ /--->| |
/ +---+
+------+ /
---------->| |-%-/
+------+
Fig. 2: The Scheduler
图2：调度器
The QoS Configuration message permits the controller to discover the QoS capabilities of each switch port in terms of the abstract switch model. The QoS Configuration message is:
QoS配置消息允许控制器根据抽象交换机模型发现每个交换机端口的QoS能力。QoS配置消息为：
Message Type = 96
消息类型=96
The QoS Configuration request message has the following format:
QoS配置请求消息具有以下格式：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The QoS Configuration success response message has the following format:
QoS配置成功响应消息的格式如下：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scheduler Flags | Regulator Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Excess Capabilities | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hi Sharing | Lo Sharing | Max Classes |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Default Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Default Discard Threshold |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Max Buffer |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Max Shaper Buffer |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scaling Factor |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scheduler Flags | Regulator Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Excess Capabilities | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hi Sharing | Lo Sharing | Max Classes |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Default Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Default Discard Threshold |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Max Buffer |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Max Shaper Buffer |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scaling Factor |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Port The switch port to which the QoS configuration information refers. QoS configuration information relating to both the input and the output sides of the switch port is given.
端口QoS配置信息引用的交换机端口。给出了与交换机端口的输入侧和输出侧相关的QoS配置信息。
Scheduler Flags
调度程序标志
0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|W|Q|S|G|D|F|M|B|I|x x x x x x x|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|W|Q|S|G|D|F|M|B|I|x x x x x x x|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
W: Weighted Connections Bit 0 of the Scheduler Flags field, if set, indicates that a weighted service algorithm (such as weighted round-robin) is available for allocation of service to individual connections within at least some waiting rooms. It means that a Connection Weight parameter can be attached to a QoS Connection Management message. Not all waiting rooms at all priority levels may be able to support this function. Whether a particular waiting room can support this function will be discovered when a QoS Connection Management message is issued.
W:Scheduler Flags字段的加权连接位0（如果设置）表示加权服务算法（如加权循环）可用于将服务分配给至少一些等候室内的各个连接。这意味着可以将连接权重参数附加到QoS连接管理消息。并非所有优先级级别的等候室都能支持此功能。当发出QoS连接管理消息时，将发现特定等候室是否支持此功能。
Q: Weighted QoS Classes Bit 1 of the Scheduler Flags field, if set, indicates that a weighted service algorithm (such as weighted round-robin) is available for allocation of service to QoS classes within at least some waiting rooms. It means that a QoS Class Weight parameter can be attached to a QoS Class Establishment message. Not all waiting rooms at all priority levels may be able to support this function. Whether a particular waiting room can support this function will be discovered when a QoS Class Establishment message is issued.
Q:Scheduler Flags字段的加权QoS类第1位（如果设置）表示加权服务算法（如加权循环）可用于将服务分配给至少一些等候室内的QoS类。这意味着QoS类权重参数可以附加到QoS类建立消息。并非所有优先级级别的等候室都能支持此功能。当发出QoS类建立消息时，将发现特定等候室是否支持此功能。
S: Shared Waiting Room Bit 2 of the Scheduler Flags field, if set, indicates that multiple QoS classes and multiple connections may be scheduled within a single waiting room. This is expected to be the normal case. If Bit 2 of the Scheduler Flags field is zero, it indicates that only a single QoS class or a single connection may be directed to any single waiting room.
S:Scheduler Flags字段的Shared Waiting Room第2位（如果设置）表示可以在一个等候室内安排多个QoS类和多个连接。预计这是正常情况。如果Scheduler Flags字段的第2位为零，则表示只能将单个QoS类或单个连接定向到任何单个等候室。
G: Global Max Classes Bit 3 of the Scheduler Flags field, if set, indicates that the Max Classes field gives the maximum number of QoS classes that may be supported by the entire switch. If zero, it indicates that the Max Classes field gives the maximum number of QoS classes that may be supported by this switch port.
G:Scheduler Flags字段的Global Max Classes第3位（如果设置）表示Max Classes字段提供整个交换机可能支持的最大QoS类数。如果为零，则表示Max Classes字段提供此交换机端口可能支持的最大QoS类数。
D: Packet Discard Bit 4 of the Scheduler Flags field, if set, indicates that the scheduler on this output port is capable of packet discard. Packet discard indicates a discard algorithm that is aware of AAL-5 packet boundaries and attempts to discard whole packets. No specific algorithm is indicated though Early Packet Discard (EPD) is likely to be the most common. Other algorithms such as "push from front" schemes, dynamic threshold, or Random Early Detection (RED) are also examples of possible packet discard algorithms. The only parameters available to the packet discard algorithm, via GSMP, are the Size and Discard Threshold of the waiting room.
D：调度程序标志字段的数据包丢弃位4（如果设置），表示此输出端口上的调度程序能够丢弃数据包。数据包丢弃表示一种丢弃算法，该算法知道AAL-5数据包边界并尝试丢弃整个数据包。虽然早期数据包丢弃（EPD）可能是最常见的算法，但未指明具体的算法。其他算法，如“前推”方案、动态阈值或随机早期检测（RED）也是可能的数据包丢弃算法的示例。通过GSMP，数据包丢弃算法可用的唯一参数是等待室的大小和丢弃阈值。
F: Frame-Based Scheduling Bit 5 of the Scheduler Flags field, if set, indicates that the scheduler on this output port is capable of frame-based scheduling. In frame-based scheduling, a connection is only scheduled for transmission when a complete AAL-5 packet is available. When a connection is scheduled for transmission, all cells belonging to one or more complete packets from that connection will be transmitted without being interleaved with any other cells on that output port (regardless of their priority). Frame-based scheduling is a property of the waiting room and is requested in the Scheduler Establishment message. A QoS class may be routed through a waiting room configured with frame-based scheduling. In this case each component connection of the QoS class will receive frame based scheduling. For correct distribution of bandwidth, each QoS class that requires frame-based scheduling should have its own waiting room.
F:Scheduler Flags字段的基于帧的调度位5（如果设置），表示此输出端口上的调度器能够进行基于帧的调度。在基于帧的调度中，仅当完整的AAL-5数据包可用时，才为传输调度连接。当一个连接被安排传输时，属于该连接的一个或多个完整数据包的所有小区都将被传输，而不会与该输出端口上的任何其他小区交织（无论其优先级如何）。基于帧的调度是等候室的属性，在调度器建立消息中请求。QoS类可通过配置有基于帧的调度的等候室路由。在这种情况下，QoS类的每个组件连接将接收基于帧的调度。为了正确分配带宽，需要基于帧的调度的每个QoS类都应该有自己的等待室。
M: VC Merging Bit 6 of the Scheduler Flags field, if set, indicates that the scheduler on this output port is capable of VC merging by a mechanism other than frame-based scheduling. VC merging indicates that the switch is capable of the multipoint-to-point merging of two or more incoming virtual connections onto a single outgoing virtual connection without interleaving cells from different AAL-5 packets that bear the same VPI/VCI. VC merging differs from frame-based scheduling in that cells with a different VPI/VCI may be interleaved with those of a multipoint-to-point VC merging connection. Thus, higher priority cells may be interleaved during the transmission of a packet on a lower priority VC merging connection. Most switches achieve VC merging by using frame-based scheduling. VC merging is a property of the waiting room and is requested in the
M:Scheduler Flags字段的VC合并位6（如果设置）表示此输出端口上的调度器能够通过基于帧的调度以外的机制进行VC合并。VC合并表示交换机能够将两个或多个传入虚拟连接多点对点合并到单个传出虚拟连接上，而无需交错来自承载相同VPI/VCI的不同AAL-5数据包的单元。VC合并与基于帧的调度的不同之处在于，具有不同VPI/VCI的小区可以与多点到点VC合并连接的小区交织。因此，在低优先级VC合并连接上的分组传输期间，高优先级小区可以被交织。大多数交换机通过基于帧的调度实现VC合并。VC合并是候诊室的财产，在
Scheduler Establishment message. A QoS class may be routed through a waiting room configured with VC merging. In this case each component connection of the QoS class will receive VC merging.
调度程序建立消息。QoS等级可通过配置有VC合并的等候室进行路由。在这种情况下，QoS类的每个组件连接都将接收VC合并。
B: Shared Buffer Bit 7 of the Scheduler Flags field, if set, indicates that at least some of the buffer space specified by the Max Buffer field is shared with other ports. If zero, it indicates that the buffer space specified by the Max Buffer field is not shared with other ports.
B:Scheduler Flags字段的共享缓冲区位7（如果已设置）表示Max Buffer字段指定的至少部分缓冲区空间与其他端口共享。如果为零，则表示Max buffer字段指定的缓冲区空间未与其他端口共享。
I: Identical Ports Bit 8 of the Scheduler Flags field, if set, indicates that all ports of the switch have identical QoS capabilities. If this bit is set the controller does not have to request the QoS configuration of each port individually as all ports have the same capability.
I：调度程序标志字段的相同端口第8位（如果设置）表示交换机的所有端口具有相同的QoS功能。如果设置了该位，控制器不必单独请求每个端口的QoS配置，因为所有端口都具有相同的功能。
x: Bits 9--15 of the Scheduler Flags field are not used.
x：未使用调度程序标志字段的第9-15位。
Regulator Flags
调节器标志
0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|C|Q|I O|P|S|H|M|x x x x x x x x|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|C|Q|I O|P|S|H|M|x x x x x x x x|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
C: Connection Policing Bit 0 of the Regulator Flags field indicates that this input port supports the policing of individual incoming connections. The parameters for the policer are specified in the QoS Connection Management message when the connection is established.
C：调节器标志字段的连接监管位0表示该输入端口支持监管单个传入连接。建立连接时，在QoS连接管理消息中指定policer的参数。
Q: QoS Class Policing If bit 1 of the Regulator Flags field is set, a policer function is available to police each QoS class on output from the classifier. The parameters for this policer are specified in the QoS Class Establishment message. If this bit is zero, no policer function is available to police a QoS class.
Q:QoS类监控如果设置了调节器标志字段的第1位，则可以使用policr函数监控分类器输出的每个QoS类。此策略的参数在QoS类建立消息中指定。如果该位为零，则没有policr函数可用于监控QoS类。
IO: QoS Class Location Bits 2 and 3 of the Regulator Flags field specify the location of the classifier and regulator functions. If both
IO:QoS类位置调节器标志字段的第2位和第3位指定分类器和调节器功能的位置。如果两者都有
bits 2 and 3 of the Regulator Flags field are zero, no classifier or regulator function is available to this port.
调节器标志字段的第2位和第3位为零，此端口没有可用的分类器或调节器功能。
If bit 2 of the Regulator Flags field is set and bit 3 is zero, the classifier and regulator functions are available on the input port. This implies that only virtual connections arriving at this input port may be grouped into QoS classes by this classifier. However, connections in a QoS class output from this regulator may be switched to any output port.
如果调节器标志字段的第2位被设置，而第3位为零，则分类器和调节器功能在输入端口上可用。这意味着只有到达该输入端口的虚拟连接可以通过该分类器分组到QoS类中。然而，从该调节器输出的QoS类中的连接可以切换到任何输出端口。
If bit 2 of the Regulator Flags field is zero and bit 3 is set, the classifier and regulator functions are available on the output port. This implies that virtual connections arriving at any input port may be grouped into QoS classes by this classifier. However, all connections in any QoS class output from this regulator may only be switched to this output port.
如果调节器标志字段的第2位为零，并且设置了第3位，则分类器和调节器功能在输出端口上可用。这意味着到达任何输入端口的虚拟连接可以通过该分类器分组到QoS类中。但是，从该调节器输出的任何QoS类中的所有连接只能切换到此输出端口。
If both bits 2 and 3 of the Regulator Flags field are set, this switch port has access to centralized classifier and regulator functions. This implies that virtual connections arriving at any input port may be grouped into a QoS class by this classifier. Also, connections in a QoS class output from this regulator may be switched to any output port.
如果调节器标志字段的第2位和第3位都已设置，则此交换机端口可以访问集中式分类器和调节器功能。这意味着到达任何输入端口的虚拟连接可以通过该分类器分组到QoS类中。此外，从该调节器输出的QoS类中的连接可以切换到任何输出端口。
Regulator Function
调节器功能
P: If bit 4 of the Regulator Flags field is set, the regulator is able to support the policing function.
P：如果设置了调节器标志字段的第4位，则调节器能够支持监控功能。
S: If bit 5 of the Regulator Flags field is set, the regulator is able to support the shaping function on all priority levels of the scheduler.
S：如果设置了调节器标志字段的第5位，则调节器能够在调度器的所有优先级上支持整形功能。
H: If bit 5 of the Regulator Flags field is zero and bit 6 is set, the regulator is able to support the shaping function but only on the highest priority level of the scheduler. All connections and QoS classes using this regulator must be routed to a waiting room at the highest priority level of the scheduler.
H：如果调节器标志字段的第5位为零，并且设置了第6位，则调节器能够支持成形功能，但仅在调度程序的最高优先级上。使用此调节器的所有连接和QoS等级必须路由到调度程序最高优先级的等候室。
M: QoS Multicast If bit 7 of the Regulator Flags field is set, any point-to-multipoint connection arriving on this input port, with QoS parameters established by the GSMP Quality of Service messages, must use the same QoS parameters for all output branches.
M:QoS多播如果设置了调节器标志字段的第7位，则到达该输入端口的任何点对多点连接，以及由GSMP服务质量消息建立的QoS参数，必须对所有输出分支使用相同的QoS参数。
x: Bits 8--15 of the Regulator Flags field are not used.
x：未使用调节器标志字段的第8-15位。
Excess Capabilities
过剩能力
0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|D|T|S|A|B|x x x x x x x x x x x|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|D|T|S|A|B|x x x x x x x x x x x|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Policer:
警察：
D: If bit 0 of the Excess Capabilities field is set, the policer function of the regulator is able to support discard.
D：如果设置了过剩能力字段的第0位，则调节器的policer功能能够支持丢弃。
T: If bit 1 of the Excess Capabilities field is set, the policer function of the regulator is able to support tagging.
T：如果设置了过剩能力字段的第1位，则调节器的policer功能能够支持标记。
S: If bit 2 of the Excess Capabilities field is set, the policer function of the regulator is able to support differentiated scheduling.
S：如果设置了过剩能力字段的第2位，则调节器的policer功能能够支持差异化调度。
Shaper:
成型机：
A: If bit 3 of the Excess Capabilities field is set, the shaper function of the regulator is able to support tagging.
答：如果设置了过剩能力字段的第3位，则调节器的整形器功能能够支持标记。
B: If bit 4 of the Excess Capabilities field is set, the shaper function of the regulator is able to support differentiated scheduling.
B：如果设置了过剩能力字段的第4位，则调节器的整形器功能能够支持差异化调度。
x: Bits 5--15 of the Excess Capabilities field are not used.
x：多余能力字段的第5-15位未使用。
Hi Sharing Lo Sharing Defines a range of priority levels that support weighted sharing. Each priority level in the range Lo Sharing to Hi Sharing inclusive, supports weighted sharing. A priority level that supports weighted sharing offers a weighted sharing algorithm (for example, weighted round-robin) between waiting rooms within that priority level. This permits the output link bandwidth available at that priority level, to be shared between the waiting rooms allocated to that priority level, according to the Net Weight parameter of each waiting room. The value 0xFF for both parameters indicates that this output port does not support weighted sharing in any priority level.
Hi Sharing Lo Sharing定义了一系列支持加权共享的优先级。Lo共享到Hi共享（含）范围内的每个优先级都支持加权共享。支持加权共享的优先级在该优先级内的等候室之间提供加权共享算法（例如，加权循环）。这允许根据每个等待室的净重参数，在分配给该优先级的等待室之间共享该优先级的可用输出链路带宽。这两个参数的值0xFF表示此输出端口不支持任何优先级的加权共享。
Max Classes If bit 3 of the Scheduler Flags field is zero, Max Classes gives the maximum number of QoS classes that may be supported by this switch port. In this case the maximum number of QoS classes that may be supported by this switch port is not affected by the number of QoS classes in use by other switch ports. If bit 3 of the Scheduler Flags field is set, Max Classes gives the maximum number of QoS classes that may be supported by the entire switch. In this case it is assumed that use of these QoS classes may be distributed among the various switch ports.
Max Classes如果Scheduler Flags字段的第3位为零，则Max Classes提供此交换机端口可能支持的最大QoS类数。在这种情况下，此交换机端口支持的最大QoS类数不受其他交换机端口使用的QoS类数的影响。如果设置了Scheduler Flags字段的第3位，则Max Classes将提供整个交换机可能支持的最大QoS类数。在这种情况下，假设这些QoS类的使用可以分布在各种交换机端口之间。
Default Size The size of waiting room that this output port allocates by default. The actual size of waiting room may be specified in the Scheduler Establishment message. The size of a waiting room specifies the maximum number of cells permitted to wait for transmission via that waiting room. Any further cells arriving at that waiting room beyond this number will be discarded.
默认大小此输出端口默认分配的等候室大小。等候室的实际大小可在调度器建立消息中指定。等待室的大小指定允许通过该等待室等待传输的最大小区数。到达该候诊室的任何超过此数量的其他单元都将被丢弃。
Default Discard Threshold The value of discard threshold that this output port allocates by default. The actual value of discard threshold may be specified in the Scheduler Establishment message. The discard threshold specifies the number of cells waiting for transmission via a waiting room after which further arriving cells will be subject to a discard mechanism.
Default Discard Threshold此输出端口默认分配的Discard Threshold值。丢弃阈值的实际值可在调度程序建立消息中指定。丢弃阈值指定通过等待室等待传输的小区数量，之后，进一步到达的小区将接受丢弃机制。
Max Buffer The maximum amount of buffer space, measured in cells, available to this port. If bit 7 of the Scheduler Flags field is zero this, buffer space is not shared with other ports. If bit 7 of the Scheduler Flags field is set, at least some of this buffer space is shared with other ports.
Max Buffer此端口可用的最大缓冲区空间量（以单元格为单位）。如果Scheduler Flags字段的第7位为零，则不会与其他端口共享缓冲区空间。如果设置了Scheduler Flags字段的第7位，则至少部分缓冲区空间与其他端口共享。
Max Shaper Buffer The maximum amount of buffer space, measured in cells, available to a QoS connection or a QoS class within the shaper function of the regulator. This shaper buffer space is likely to be shared among all QoS classes and QoS connections using the shaper, so there is no guarantee that the amount of buffer space defined by the Max Shaper Buffer field will be available to any particular QoS class or QoS connection.
Max Shaper Buffer调节器的Shaper功能中QoS连接或QoS类可用的最大缓冲空间量（以单元为单位）。此整形器缓冲区空间可能在使用整形器的所有QoS类和QoS连接之间共享，因此不能保证由“最大整形器缓冲区”字段定义的缓冲区空间量可用于任何特定QoS类或QoS连接。
Scaling Factor The QoS Class Establishment and QoS Connection Management messages require parameters that describe cell rates in cells per second or their reciprocal, cell interarrival periods, in seconds per cell. In order that these parameters may be specified with a 32-bit unsigned integer, the switch defines a Scaling Factor to be used in defining such parameters. By appropriate choice of the Scaling Factor the switch can select the range and granularity of rate or time that can be specified with the 32-bit unsigned integer. Further details are given in the discussion of the UPC Parameters field of the QoS Connection Management message.
缩放因子QoS类建立和QoS连接管理消息需要一些参数，这些参数以每秒信元数或其倒数、信元间隔周期（以秒为单位）来描述信元速率。为了使用32位无符号整数指定这些参数，开关定义了用于定义此类参数的比例因子。通过适当选择比例因子，交换机可以选择可使用32位无符号整数指定的速率或时间的范围和粒度。关于QoS连接管理消息的UPC参数字段的讨论给出了进一步的细节。
The Scheduler Establishment message is used to configure the scheduler on a specified output port. It is used to configure a waiting room, attach it to a leaf of the scheduler tree, and return a Scheduler Identifier to reference the waiting room. The Scheduler Establishment message may also be used to modify the parameters of an already established waiting room.
计划程序建立消息用于在指定的输出端口上配置计划程序。它用于配置等候室，将其附加到调度程序树的叶子，并返回调度程序标识符以引用等候室。调度器建立消息还可用于修改已经建立的等候室的参数。
Scheduler Identifiers in the range 0--255 represent default values. They are used for the priority levels that may be specified in the Class of Service field of Connection Management messages without requiring explicit establishment via a Scheduler Establishment message. Each of these default values specifies a single waiting room with default parameters, configured as a FIFO queue, on each of the valid scheduler priority levels. (This permits Connection Management messages to continue to specify QoS requirements as a priority without requiring the use of any of the QoS messages.) The number of priority levels available to the scheduler is specified in the Priorities field of the Port Configuration and All Ports Configuration messages.
0到255范围内的计划程序标识符表示默认值。它们用于可在连接管理消息的服务类别字段中指定的优先级，而无需通过调度器建立消息进行显式建立。这些默认值中的每一个都指定一个具有默认参数的等候室，在每个有效的调度程序优先级级别上配置为FIFO队列。（这允许连接管理消息继续将QoS要求指定为优先级，而无需使用任何QoS消息。）调度程序可用的优先级级别数在端口配置和所有端口配置消息的优先级字段中指定。
The Scheduler Establishment Message is:
计划程序建立消息为：
Message Type = 97
消息类型=97
The Scheduler Establishment request and success response messages have the following format:
计划程序建立请求和成功响应消息的格式如下：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scheduler Identifier | Net Weight |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved |D|F|M|W|x x x x| Priority |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Waiting Room Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Discard Threshold |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scheduler Identifier | Net Weight |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved |D|F|M|W|x x x x| Priority |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Waiting Room Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Discard Threshold |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Scheduler Identifier The Scheduler Identifier is selected by the controller. It is used to identify the waiting room being established or modified in future messages. The Scheduler Identifier is taken from a namespace that is local to the switch port. A Scheduler Identifier in the Scheduler Establishment message must be greater than 0x00FF but less than 0xFFFF. The values 0 -- 0x00FF are reserved for use as default values. The default values of the Scheduler Identifier are used to specify the default settings for the scheduler. Each of the default values maps directly to one of the scheduler priority levels. The value 0xFFFF is reserved for use in the QoS Connection Management message.
调度器标识符调度器标识符由控制器选择。它用于在将来的消息中标识正在建立或修改的等候室。调度程序标识符取自交换机端口本地的命名空间。计划程序建立消息中的计划程序标识符必须大于0x00FF但小于0xFFFF。值0--0x00FF保留用作默认值。调度程序标识符的默认值用于指定调度程序的默认设置。每个默认值都直接映射到一个调度程序优先级。值0xFFFF保留用于QoS连接管理消息。
Net Weight The Net Weight specifies the share of the bandwidth available to the priority level, specified by the Priority field, that should be given to this waiting room. The Net Weight parameter is only valid if the priority level specified by the Priority field supports weighted sharing.
净重净重指定优先级别的可用带宽份额，该优先级由优先级字段指定，应分配给该等候室。仅当“优先级”字段指定的优先级支持加权共享时，“净重”参数才有效。
The Net Weight is an unsigned 16-bit field specifying a binary fraction. I.e. the bandwidth share, as a fraction of the bandwidth available to the priority level, is given by:
净重是指定二进制分数的无符号16位字段。即，带宽共享，作为优先级可用带宽的一部分，由以下公式给出：
Bandwidth share = Net Weight * 2**(-16)
Bandwidth share = Net Weight * 2**(-16)
A Net Weight of zero indicates equal sharing between all waiting rooms sharing this priority level that request a Net Weight of zero. While a 16-bit field is used to specify the Net Weight it is understood that the accuracy of the bandwidth sharing is hardware dependent and is not specified.
净重为零表示所有共享此优先级且净重为零的等候室之间的共享相等。虽然16位字段用于指定净重，但可以理解，带宽共享的精度取决于硬件，并且没有指定。
If weighted sharing is not required at a particular priority level, a waiting room with a Net Weight value of 0xFFFF must be specified for that priority level. A priority level that does not support weighted sharing can only support a single waiting room.
如果特定优先级不需要加权共享，则必须为该优先级指定净重值为0xFFFF的等候室。不支持加权共享的优先级只能支持单个等候室。
Flags
旗帜
D: Packet Discard Bit 0 of the Flags field, if set, indicates that packet discard is required on all connections and QoS classes routed through this waiting room.
D:Flags字段的Packet Discard位0（如果设置）表示通过该等待室路由的所有连接和QoS类都需要数据包丢弃。
F: Frame-Based Scheduling Bit 1 of the Flags field, if set, indicates that frame-based scheduling is required on all connections and QoS classes routed through this waiting room. In frame-based scheduling, a connection is only scheduled for transmission when a complete AAL-5 packet is available. When a connection is scheduled for transmission, all cells belonging to one or more complete packets from that connection will be transmitted without being interleaved with any other cells on that output port. A QoS class may be routed through a waiting room configured with frame-based scheduling. In this case each component connection of the QoS class will receive frame based scheduling. For correct distribution of bandwidth, each QoS class that requires frame-based scheduling should have its own waiting room.
F:Flags字段的基于帧的调度位1（如果设置），表示通过此等候室路由的所有连接和QoS类都需要基于帧的调度。在基于帧的调度中，仅当完整的AAL-5数据包可用时，才为传输调度连接。当一个连接被安排传输时，属于该连接的一个或多个完整数据包的所有小区都将被传输，而不会与该输出端口上的任何其他小区交织。QoS类可通过配置有基于帧的调度的等候室路由。在这种情况下，QoS类的每个组件连接将接收基于帧的调度。为了正确分配带宽，需要基于帧的调度的每个QoS类都应该有自己的等待室。
M: VC Merging Bit 2 of the Scheduler Flags field, if set, indicates that VC merging is required on all connections and QoS classes routed through this waiting room. VC merging enables the multipoint-to-point merging of two or more incoming virtual connections onto a single outgoing virtual connection, without interleaving cells from different AAL-5 packets that bear the same VPI/VCI. VC merging differs from frame-based scheduling in that cells with a different VPI/VCI may be interleaved with those of a multipoint-to-point VC merging connection. Most switches achieve VC merging by
M:Scheduler Flags字段的VC Merging第2位（如果设置）表示通过该等候室路由的所有连接和QoS类都需要VC Merging。VC合并允许将两个或多个传入虚拟连接的多点对点合并到单个传出虚拟连接上，而无需交错来自承载相同VPI/VCI的不同AAL-5数据包的单元。VC合并与基于帧的调度的不同之处在于，具有不同VPI/VCI的小区可以与多点到点VC合并连接的小区交织。大多数交换机通过以下方式实现VC合并：
using frame-based scheduling. A QoS class may be routed through a waiting room configured with VC merging. In this case each component connection of the QoS class will receive VC merging.
使用基于帧的调度。QoS等级可通过配置有VC合并的等候室进行路由。在这种情况下，QoS类的每个组件连接都将接收VC合并。
W: Weighted Scheduling Bit 3 of the Flags field, if set, indicates that weighted scheduling is required on all connections and QoS classes routed through this waiting room. All connections and QoS classes routed through this waiting room will require a Connection Weight or a QoS Class Weight respectively. The Connection Weight is specified in the QoS Connection Management message. The QoS Class Weight is specified in the QoS Class Establishment message. If weighted scheduling within this waiting room is unavailable, a failure response message must be returned indicating, "Weighted scheduling within this waiting room is unavailable."
W:Flags字段的加权调度位3（如果设置），表示通过该等待室路由的所有连接和QoS类都需要加权调度。通过该等候室路由的所有连接和QoS等级将分别需要连接权重或QoS等级权重。连接权重在QoS连接管理消息中指定。QoS类权重在QoS类建立消息中指定。如果此等候室内的加权调度不可用，则必须返回故障响应消息，指示“此等候室内的加权调度不可用”
Bit 3 of the Flags field, if zero, indicates that this waiting room should be configured as a single FIFO queue. All cells arriving at this waiting room will receive first-in-first-out service. If Frame-Based Scheduling or VC Merging are also selected, the strict first-in-first-out service discipline will be modified by the requirement to support Frame-Based Scheduling or VC Merging.
标志字段的第3位（如果为零）表示该等待室应配置为单个FIFO队列。所有到达候诊室的牢房将接受先进先出服务。如果还选择了基于帧的调度或VC合并，将根据支持基于帧的调度或VC合并的要求修改严格的先进先出服务规程。
x: Bits 4--7 of the Flags field are not used.
x：不使用标志字段的第4-7位。
Priority Specifies the priority level in the scheduler to which the waiting room should be attached. Priorities are numbered from zero, with priority level zero being the highest priority.
优先级指定计划程序中等待室应连接到的优先级。优先级从零开始编号，优先级级别0是最高优先级。
Waiting Room Size The required size of the waiting room. The size of a waiting room specifies the maximum number of cells permitted to wait for transmission via that waiting room. Any further cells arriving at that waiting room beyond this number will be discarded. If the switch is unable to grant the size requested in the Scheduler Establishment request message it may reply with the actual size allocated to the waiting room in the Waiting Room Size field of the success response message. A value of zero for the Waiting Room Size indicates that the default value should be used.
候机室大小候机室所需的大小。等待室的大小指定允许通过该等待室等待传输的最大小区数。到达该候诊室的任何超过此数量的其他单元都将被丢弃。如果交换机无法授予调度器建立请求消息中请求的大小，它可以在成功响应消息的等待室大小字段中使用分配给等待室的实际大小进行响应。等候室大小的值为零表示应使用默认值。
Discard Threshold The required value of the discard threshold. The discard threshold specifies the number of cells waiting for transmission via a waiting room after which further arriving cells will be subject to a discard mechanism. The value of the Discard Threshold must be less than or equal to the value of the Waiting Room Size parameter for any given waiting room. If the switch is unable to grant the value of discard threshold requested in the Scheduler Establishment request message it may reply with the actual value of discard threshold allocated to the waiting room in the Discard Threshold field of the success response message. A value of zero for the Discard Threshold indicates that the default value should be used.
丢弃阈值丢弃阈值的所需值。丢弃阈值指定通过等待室等待传输的小区数量，之后，进一步到达的小区将接受丢弃机制。对于任何给定的等候室，丢弃阈值的值必须小于或等于等候室大小参数的值。如果交换机无法授予调度器建立请求消息中请求的丢弃阈值的值，它可以在成功响应消息的丢弃阈值字段中使用分配给等待室的丢弃阈值的实际值进行回复。丢弃阈值的值为零表示应使用默认值。
The QoS Class Establishment message is used to configure a QoS class on a specified port or to modify the parameters of an already established QoS class. It configures the classifier and the regulator functions for the QoS class. It also configures the QoS class policer if a policing function is available for QoS classes.
QoS类建立消息用于在指定端口上配置QoS类或修改已建立的QoS类的参数。它为QoS类配置分类器和调节器功能。如果QoS类有可用的策略功能，它还配置QoS类策略。
Two styles of QoS class are available. In one style each component connection of the QoS class may be routed independently to an output port and waiting room specified in its connection management message. In this case the Scheduler Identifier, and if required, the Excess Scheduler Id, are specified in the QoS Connection Management message that references this style of QoS class. In the alternative style of QoS class, all component connections in the QoS class are routed to the same waiting room on the same output port. In this case the Output Port, the Scheduler Identifier, and if required, the Excess Scheduler Id, are specified in the QoS Class Establishment message.
有两种类型的QoS类可用。在一种样式中，QoS类的每个组件连接可以独立地路由到其连接管理消息中指定的输出端口和等待室。在这种情况下，调度器标识符和多余的调度器Id（如果需要）在引用这种类型的QoS类的QoS连接管理消息中指定。在QoS类的替代样式中，QoS类中的所有组件连接都路由到同一输出端口上的同一等待室。在这种情况下，在QoS类建立消息中指定输出端口、调度器标识符以及多余的调度器Id（如果需要）。
The classifier and regulator functions must be located together, either on an input port, on an output port, or centralized. Each port declares the location of its classifier and regulator functions at initialization using the QoS Configuration message. If the classifier and regulator functions are located on an input port, only connections that arrive at that input port may join a QoS class established on that port. However, each connection that is part of a QoS class established on that port may be switched to a different output port. If the classifier and regulator functions are located on an output port, connections that arrive at any input port may join a QoS class established on that port. However, all connections within a QoS class established on that port must be switched to that output port. For a centralized classifier and regulator function, there is
分类器和调节器功能必须一起位于输入端口、输出端口或中央。每个端口在初始化时使用QoS配置消息声明其分类器和调节器功能的位置。如果分类器和调节器功能位于输入端口上，则只有到达该输入端口的连接可以加入该端口上建立的QoS类。然而，作为在该端口上建立的QoS类的一部分的每个连接可以切换到不同的输出端口。如果分类器和调节器功能位于输出端口上，则到达任何输入端口的连接可以加入该端口上建立的QoS类。但是，在该端口上建立的QoS类中的所有连接必须切换到该输出端口。对于集中式分类器和调节器功能，有
no restriction on the input ports on which connections in a QoS class must arrive, or on the output ports to which connections in a QoS class must be switched. (For the case of a centralized classifier and regulator the actual port specified in the QoS Class Establishment message is used only for administrative purposes. Any valid value of Port and Port Session Number, that specifies a centralized classifier and regulator function, may be used.)
对QoS类中的连接必须到达的输入端口或QoS类中的连接必须切换到的输出端口没有限制。（对于集中式分类器和调节器，QoS类建立消息中指定的实际端口仅用于管理目的。可以使用指定集中式分类器和调节器功能的端口和端口会话号的任何有效值。）
The QoS Class Establishment message is:
QoS类建立消息为：
Message Type = 98
消息类型=98
The QoS Class Establishment request and success response messages have the following format:
QoS类建立请求和成功响应消息的格式如下：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| QoS Class Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Regulator | Excess Action | QoS Class Weight |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scheduler Identifier | Excess Scheduler Id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ QoS Class Policer Parameters ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ QoS Class Regulator Parameters ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| QoS Class Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Regulator | Excess Action | QoS Class Weight |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scheduler Identifier | Excess Scheduler Id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ QoS Class Policer Parameters ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ QoS Class Regulator Parameters ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
QoS Class Identifier The QoS Class Identifier is selected by the controller. It is used to identify the QoS class being established or modified, in future QoS Connection Management and QoS Class Establishment messages. It is taken from a namespace that
QoS类标识符控制器选择QoS类标识符。它用于在将来的QoS连接管理和QoS类建立消息中标识正在建立或修改的QoS类。它取自一个
is global across the entire switch. No two QoS classes may have the same QoS Class Identifier regardless of the switch ports on which they are defined. A QoS Class Identifier in a QoS Class Establishment message must be greater than 0 and less than 0xFFFFFFFF.
在整个交换机中是全局的。任何两个QoS类都不能具有相同的QoS类标识符，无论它们定义在哪个交换机端口上。QoS类建立消息中的QoS类标识符必须大于0且小于0xFFFFFF。
Regulator The Regulator field specifies which function is required of the regulator. Three possible functions are currently defined: none, policing, and shaping.
调节器调节器字段指定调节器需要的功能。目前定义了三种可能的功能：无、监管和塑造。
None: Regulator = 1
Policing: Regulator = 2
Shaping: Regulator = 3
None: Regulator = 1
Policing: Regulator = 2
Shaping: Regulator = 3
If the Regulator function is specified as none, no operations are performed by the regulator on the cells output from the classifier. Cells output from the classifier are transferred directly to the waiting room specified by the Scheduler Identifier.
如果调节器功能指定为无，则调节器不会对分类器输出的单元执行任何操作。分类器输出的单元格直接传输到调度程序标识符指定的等候室。
If policing is specified, a token bucket policer will be applied to the QoS class. The policer determines which cells conform to the specified policer traffic parameters and which do not. Conforming cells are transferred directly to the waiting room specified by the Scheduler Identifier. The action to be taken by the policer on the excess traffic is specified by the Excess Action field. The policer traffic parameters are specified in the QoS Class Regulator Parameters fields.
如果指定了策略，则令牌桶策略器将应用于QoS类。policr确定哪些单元格符合指定的policr流量参数，哪些不符合。一致性单元格直接传输到调度程序标识符指定的等候室。策略器对过剩流量采取的操作由过剩操作字段指定。policer流量参数在QoS类调节器参数字段中指定。
If shaping is specified, traffic shaping will be applied to the QoS class. Cells in a QoS class should leave the regulator spaced evenly apart at a rate defined by the QoS Class Regulator Parameters fields. These cells are transferred directly to the waiting room specified by the Scheduler Identifier. The jitter on the conforming cell stream on exit from the shaping function of the regulator is not specified.
如果指定了整形，则流量整形将应用于QoS类。QoS类中的小区应以QoS类调节器参数字段定义的速率将调节器均匀隔开。这些单元格直接传输到调度程序标识符指定的等候室。未规定调节器整形功能退出时一致性小区流上的抖动。
Excess Action
过度作用
0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+
|T|D|S|x x x x x|
+-+-+-+-+-+-+-+-+
0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+
|T|D|S|x x x x x|
+-+-+-+-+-+-+-+-+
T: Tagging If bit 0 of the Excess Action field is set, all cells transferred to the waiting room specified by the Excess Scheduler Id will have their CLP bit set. If bit 0 of the Excess Action field is zero, the CLP bit of cells transferred to the waiting room specified by the Excess Scheduler Id will remain unchanged.
T：标记如果设置了多余操作字段的位0，则传输到多余调度程序Id指定的等待室的所有单元格都将设置其CLP位。如果多余操作字段的位0为零，则传输到多余调度程序Id指定的等待室的单元格的CLP位将保持不变。
D: Discard This function is only available if policing is selected as the regulator function. If the Regulator field specifies Policing, and bit 1 of the Excess Action field is set, all cells determined by the policer to be in excess of the traffic parameters must be discarded. In this case the Excess Scheduler Id is not used and bit 0 of the Excess Action field should be ignored.
D：放弃此功能仅在选择“警务”作为调节器功能时可用。如果调节器字段指定了监控，并且设置了过量操作字段的第1位，则必须丢弃由调节器确定为超出流量参数的所有单元格。在这种情况下，将不使用多余的调度程序Id，并且应忽略多余操作字段的位0。
S: Differentiated Scheduling This function operates differently according to whether policing or shaping is selected as the regulator function.
S：差异化调度此功能根据选择的调节器功能是“控制”还是“成形”而不同。
If the Regulator field specifies Policing, and bit 1 of the Excess Action field is zero, and bit 2 of the Excess Action field is set, all cells determined by the policer to be in excess of the traffic parameters must be transferred to the waiting room specified by the Excess Scheduler Id. In this case care must be taken in the implementation to ensure that within each virtual path connection or virtual channel connection, cells depart in the same order that they arrived. If the Regulator field specifies Policing, and bit 1 of the Excess Action field is zero, and bit 2 of the Excess Action field is zero, all cells determined by the policer to be in excess of the traffic parameters must be transferred to the waiting room specified by the Scheduler Identifier. In this case the Excess Scheduler Id is not used.
如果调节器字段指定了监管，并且多余动作字段的第1位为零，并且多余动作字段的第2位被设置，由policr确定为超出流量参数的所有小区必须传输到由超额调度器Id指定的等候室。在这种情况下，在实施过程中必须小心，以确保在每个虚拟路径连接或虚拟通道连接中，小区以其到达的相同顺序离开。如果调节器字段指定了监管，并且超额操作字段的第1位为零，超额操作字段的第2位为零，则由调节器确定为超出流量参数的所有单元必须传输到调度器标识符指定的等候室。在这种情况下，不使用多余的调度程序Id。
If the Regulator field specifies Shaping, and bit 2 of the Excess Action field is zero, cells will be transferred from the QoS class to the waiting room pointed to by the Scheduler Identifier at a rate defined by the QoS Class Regulator Parameters. In this case the Excess Scheduler Id is not used. If the Regulator field specifies Shaping, and bit 2 of the Excess Action field is set, additional cells will be scheduled for transmission by the waiting room pointed to by the Excess Scheduler Id. This permits a minimum cell rate to be allocated to the QoS class using the QoS Class Regulator Parameters and additional bandwidth
如果调节器字段指定整形，并且多余操作字段的位2为零，则小区将以QoS类调节器参数定义的速率从QoS类传输到调度器标识符指向的等待室。在这种情况下，不使用多余的调度程序Id。如果调节器字段指定整形，并且设置了多余动作字段的第2位，多余调度器Id所指的等待室将调度额外的小区进行传输。这允许使用QoS类调节器参数和额外带宽将最小小区速率分配给QoS类
to be shared by the QoS class. The additional share of bandwidth is determined according to the parameters of the waiting room pointed to by the Excess Scheduler Id. If the Excess Scheduler Id is specified in the QoS Class Establishment message, the additional bandwidth will be shared by the entire QoS class. If the Excess Scheduler Id is specified in each individual QoS Connection Management message, the additional bandwidth is specific to that connection and not shared by the entire QoS class. Care must be taken in the implementation to ensure that within each virtual path connection or virtual channel connection, cells depart in the same order that they arrived.
由QoS类共享。额外的带宽共享根据超额调度器Id指向的等候室参数确定。如果在QoS类建立消息中指定了超额调度器Id，则额外的带宽将由整个QoS类共享。如果在每个单独的QoS连接管理消息中指定了多余的调度程序Id，则额外的带宽特定于该连接，而不是由整个QoS类共享。在实现过程中必须小心，以确保在每个虚拟路径连接或虚拟通道连接中，单元的离开顺序与它们到达的顺序相同。
x: Bits 3--7 of the Excess Action field are not used.
x：未使用多余动作字段的第3-7位。
QoS Class Weight If bit 1 of the Scheduler Flags field of the QoS Configuration message indicates that weighted service may be applied to a QoS class, the QoS Class Weight parameter specifies the share of the bandwidth available to the waiting room that should be given to this QoS class.
QoS类权重如果QoS配置消息的调度器标志字段的位1指示加权服务可应用于QoS类，则QoS类权重参数指定应给予该QoS类的等待室可用带宽的份额。
The QoS Class Weight is an unsigned 16-bit field specifying a binary fraction. I.e. the bandwidth share, as a fraction of the bandwidth available to the waiting room, is given by:
QoS类权重是指定二进制分数的无符号16位字段。即，带宽共享，作为候诊室可用带宽的一部分，由以下公式给出：
Bandwidth share = QoS Class Weight * 2**(-16)
Bandwidth share = QoS Class Weight * 2**(-16)
A QoS Class Weight of zero indicates equal sharing between all QoS classes sharing this waiting room that request a QoS Class Weight of zero. While a 16-bit field is used to specify the QoS Class Weight it is understood that the accuracy of the bandwidth sharing is hardware dependent and is not specified.
QoS类权重为零表示共享此等待室且请求QoS类权重为零的所有QoS类之间的平等共享。虽然使用16位字段来指定QoS类权重，但是可以理解，带宽共享的准确性取决于硬件，并且没有指定。
If the Regulator field of the QoS Class Establishment message indicates None, or Policer, the QoS Class Weight should be applied to the waiting room pointed to by the Scheduler Identifier. If the Regulator field of the QoS Class Establishment message indicates Shaper, the QoS Class Weight should be applied to the waiting room pointed to by the Excess Scheduler Id.
如果QoS类建立消息的调节器字段指示None或Policir，则QoS类权重应应用于调度程序标识符所指向的等待室。如果QoS类建立消息的调节器字段指示Shaper，则QoS类权重应应用于超额调度器Id所指向的等待室。
If the specified waiting room is unable to offer weighted sharing for a QoS class, a failure response message should be returned with the failure code indicating: "This waiting room is unable to offer weighted sharing for a QoS class."
如果指定的等候室无法为QoS类提供加权共享，则应返回故障响应消息，故障代码指示：“此等候室无法为QoS类提供加权共享。”
Scheduler Identifier If all conforming traffic from this QoS class is directed to the same waiting room, on the same output port, this field specifies the Scheduler Identifier for the entire QoS class. The Scheduler Identifier points to the waiting room, on the output port specified by the Output Port field, to which all conforming traffic should be sent. If this field is not used it should be set to 0xFFFF. If each component connection of the QoS class specifies its own output port and waiting room, the Scheduler Identifier must be specified in the QoS Connection Management message and this field must be set to 0xFFFF.
调度器标识符如果来自该QoS类的所有一致性通信量被定向到同一输出端口上的同一等候室，则该字段指定整个QoS类的调度器标识符。调度器标识符指向由输出端口字段指定的输出端口上的等待室，所有一致的通信量都应发送到该等待室。如果未使用此字段，则应将其设置为0xFFFF。如果QoS类的每个组件连接指定其自己的输出端口和等待室，则必须在QoS连接管理消息中指定调度程序标识符，并且此字段必须设置为0xFFFF。
Excess Scheduler Id If all conforming traffic from this QoS class is directed to the same waiting room, on the same output port, this field specifies the Excess Scheduler Id for the entire QoS class. The Excess Scheduler Id points to the waiting room, on the output port specified by the Output Port field, to which all excess traffic should be sent. If this field is not used it should be set to 0xFFFF. If each component connection of the QoS class specifies its own output port and waiting room, the Excess Scheduler Id must be specified in the QoS Connection Management message and this field must be set to 0xFFFF. If the Scheduler Id is specified in the QoS Class Establishment message, the Excess Scheduler Id must also be specified in the QoS Class Establishment message (or not used). If the Scheduler Id is specified in the QoS Connection Management message, the Excess Scheduler Id must also be specified in the QoS Connection Management message (or not used). The Excess Scheduler Id must not point to the same waiting room on the same output port as the Scheduler Identifier.
多余调度程序Id如果来自此QoS类的所有一致性流量都被定向到同一输出端口上的同一等候室，则此字段指定整个QoS类的多余调度程序Id。多余的调度程序Id指向等待室，位于output port字段指定的输出端口上，所有多余的流量都应发送到该等待室。如果未使用此字段，则应将其设置为0xFFFF。如果QoS类的每个组件连接都指定了自己的输出端口和等待室，则必须在QoS连接管理消息中指定多余的调度程序Id，并且该字段必须设置为0xFFFF。如果在QoS类建立消息中指定了调度程序Id，则还必须在QoS类建立消息中指定多余的调度程序Id（或不使用）。如果在QoS连接管理消息中指定了调度程序Id，则还必须在QoS连接管理消息中指定多余的调度程序Id（或不使用）。多余的计划程序Id不得与计划程序标识符指向同一输出端口上的同一等待室。
Output Port If the Scheduler Identifier field in the QoS Establishment message is not 0xFFFF the Output Port field specifies the Output Port to which traffic from this QoS class should be routed. If the Scheduler Identifier field in the QoS Establishment message is 0xFFFF, this field is not used.
输出端口如果QoS建立消息中的调度程序标识符字段不是0xFFFF，则输出端口字段指定此QoS类的流量应路由到的输出端口。如果QoS建立消息中的调度程序标识符字段为0xFFFF，则不使用此字段。
QoS Class Policer Parameters A policer function may be applied to a QoS class on output from the classifier independently of the regulator function. The QoS class policer function is identical to the connection policer function defined in the QoS
QoS类Policer参数Policer函数可独立于调节器函数，在分类器的输出上应用于QoS类。QoS类policer函数与QoS中定义的连接policer函数相同
Connection Management message with the exception that it applies to all cells that belong to the QoS class rather than just cells that belong to a single connection.
连接管理消息，例外情况是它应用于属于QoS类的所有小区，而不仅仅是属于单个连接的小区。
The QoS Class Policer Parameters have the following format:
QoS类策略参数的格式如下：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| QoS Class Increment-1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| QoS Class Limit-1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| QoS Class Increment-2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| QoS Class Limit-2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved |C|A|x x x x x x|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| QoS Class Increment-1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| QoS Class Limit-1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| QoS Class Increment-2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| QoS Class Limit-2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved |C|A|x x x x x x|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The definition of these fields is given in the UPC Parameters section of the QoS Connection Management message.
QoS连接管理消息的UPC参数部分给出了这些字段的定义。
QoS Class Regulator Parameters The QoS class regulator function is identical to the regulator function defined in the QoS Connection Management message with the exception that it applies to all cells that belong to the QoS class rather than just cells that belong to a single connection.
QoS类调节器参数QoS类调节器功能与QoS连接管理消息中定义的调节器功能相同，但适用于属于QoS类的所有小区，而不仅仅是属于单个连接的小区。
The QoS Class Regulator Parameters have the following format:
QoS等级调节器参数的格式如下：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| QoS Class Regulator Increment |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| QoS Class Regulator Limit |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| QoS Class Regulator Increment |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| QoS Class Regulator Limit |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The definition of these fields is given in the Regulator Parameters section of the QoS Connection Management message.
QoS连接管理消息的调节器参数部分给出了这些字段的定义。
The QoS Release message is used to delete a Scheduler Identifier or a QoS Class Identifier and to release all resources associated with it.
QoS释放消息用于删除调度器标识符或QoS类标识符，并释放与之相关的所有资源。
The QoS Release message is:
QoS发布消息是：
Message Type = 99
消息类型=99
The QoS Release request and success response messages have the following format:
QoS发布请求和成功响应消息的格式如下：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Scheduler Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| QoS Class Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Scheduler Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| QoS Class Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Port If the QoS Release message contains a Scheduler Identifier, the Port field must contain the Port Number of the switch output port to which the Scheduler Identifier applies. If the QoS Release message contains a QoS Class Identifier, any valid Port number may be used. (The QoS Class Identifier has a global namespace.)
端口如果QoS释放消息包含调度器标识符，则端口字段必须包含调度器标识符应用到的交换机输出端口的端口号。如果QoS释放消息包含QoS类标识符，则可以使用任何有效的端口号。（QoS类标识符具有全局命名空间。）
Port Session Number The current Port Session Number for the port specified in the Port field.
端口会话号端口字段中指定的端口的当前端口会话号。
Scheduler Identifier If the Scheduler Identifier contains the value 0xFFFF the QoS Class Identifier specified in the QoS Class Identifier field should be released. Else, if the value of the Scheduler Identifier lies in the range 0x0100 -- 0xFFFE inclusive, the Scheduler Identifier specified by the Scheduler Identifier field should be released. A Scheduler
调度器标识符如果调度器标识符包含值0xFFFF，则应释放QoS类标识符字段中指定的QoS类标识符。否则，如果调度程序标识符的值在0x0100--0xFFFE（包括0x0100--0xFFFE）范围内，则应释放调度程序标识符字段指定的调度程序标识符。调度程序
Identifier with a value less than 0x0100 is invalid in a QoS Release message. (It specifies a default value which may not be released.)
值小于0x0100的标识符在QoS发布消息中无效。（它指定了一个不能释放的默认值。）
QoS Class Identifier If the Scheduler Identifier contains the value 0xFFFF the QoS Class Identifier field specifies the QoS Class Identifier to be released.
QoS类标识符如果调度程序标识符包含值0xFFFF，则QoS类标识符字段指定要释放的QoS类标识符。
If the QoS Release message requests that a Scheduler Identifier be released, and the Scheduler Identifier is still in use by one or more established connections, a failure response must be returned with the failure code indicating: "Scheduler Identifier still in use." If the QoS Release message requests that a QoS Class Identifier be released, and the QoS Class Identifier is still in use by one or more established connections, a failure response must be returned with the failure code indicating: "QoS Class Identifier still in use."
如果QoS Release消息请求释放调度程序标识符，并且一个或多个已建立的连接仍在使用调度程序标识符，则必须返回故障响应，故障代码指示：“调度程序标识符仍在使用”。如果QoS Release消息请求释放QoS类标识符，如果一个或多个已建立的连接仍在使用QoS类标识符，则必须返回故障响应，故障代码指示：“QoS类标识符仍在使用。”
The QoS Connection Management message is used by the controller to establish and modify virtual channel connections and virtual path connections across the switch which require QoS parameters to be specified. The functionality of the QoS Connection Management message is identical to that of the Add Branch connection management message with the additional specification of QoS parameters. No specific QoS connection release messages are defined. QoS connections may be released with the Delete Tree, Delete All, and Delete Branches messages defined in Section 4, "Connection Management Messages." When a QoS connection is released, all associated QoS resources are released.
控制器使用QoS连接管理消息来建立和修改交换机上需要指定QoS参数的虚拟通道连接和虚拟路径连接。QoS连接管理消息的功能与添加分支连接管理消息的功能相同，但附加了QoS参数规范。未定义特定的QoS连接释放消息。QoS连接可以通过第4节“连接管理消息”中定义的删除树、全部删除和删除分支消息来释放。当QoS连接被释放时，所有相关的QoS资源都被释放。
There are three styles of connection with specified QoS parameters:
具有指定QoS参数的连接有三种类型：
QoS Connection: This connection style specifies its own individual QoS parameters and is routed independently to the waiting room and output port specified in the QoS Connection Management message. It is not a member of a QoS class. Each output branch of a point-to-multipoint QoS connection may specify its own QoS parameters which may be different from all other output branches of that point-to-multipoint QoS connection, if the switch supports this capability. However, all output branches must specify identical connection policer parameters. A QoS Connection Management message requesting this style of connection is identified by a QoS Class Identifier with the value 0xFFFFFFFF.
QoS连接：此连接样式指定其各自的QoS参数，并独立路由到QoS连接管理消息中指定的等候室和输出端口。它不是QoS类的成员。如果交换机支持此功能，点对多点QoS连接的每个输出分支可以指定其自己的QoS参数，这些参数可能不同于该点对多点QoS连接的所有其他输出分支。但是，所有输出分支必须指定相同的连接策略参数。请求这种连接方式的QoS连接管理消息由值为0xFFFFFF的QoS类标识符标识。
QoS Class Connection: This connection style does not specify its own individual QoS parameters. It is a member of a QoS class, and the QoS parameters are specified by the QoS class. It is, however, routed independently to the waiting room and output port specified in the QoS Connection Management message. Each output branch of a point-to-multipoint QoS Class Connection must use the same QoS parameters. A QoS Connection Management message requesting this style of connection will have a valid QoS Class Identifier and a valid Scheduler Identifier.
QoS类连接：此连接样式不指定自己的QoS参数。它是QoS类的成员，QoS参数由QoS类指定。但是，它独立地路由到QoS连接管理消息中指定的等候室和输出端口。点对多点QoS类连接的每个输出分支必须使用相同的QoS参数。请求这种连接方式的QoS连接管理消息将具有有效的QoS类标识符和有效的调度程序标识符。
QoS Class Member: This connection style does not specify its own individual QoS parameters. It is a member of a QoS class, and the QoS parameters are specified by the QoS class. The QoS class also specifies the waiting room and output port to which all members of the class are routed. This style of connection does not support point-to-multipoint connections. A QoS Connection Management message requesting this style of connection will have a valid QoS Class Identifier and a Scheduler Identifier with the value 0xFFFF.
QoS类成员：此连接样式不指定其自己的QoS参数。它是QoS类的成员，QoS参数由QoS类指定。QoS类还指定类的所有成员路由到的等待室和输出端口。这种类型的连接不支持点对多点连接。请求这种连接方式的QoS连接管理消息将具有有效的QoS类标识符和值为0xFFFF的调度程序标识符。
To request a virtual channel connection with specified QoS parameters, the Virtual Channel Connection (VCC) QoS Connection Management message is:
要请求具有指定QoS参数的虚拟通道连接，虚拟通道连接（VCC）QoS连接管理消息为：
Message Type = 100.
消息类型=100。
To request a virtual path connection with specified QoS parameters, the Virtual Path Connection (VPC) QoS Connection Management message is:
要请求具有指定QoS参数的虚拟路径连接，虚拟路径连接（VPC）QoS连接管理消息为：
Message Type = 101.
消息类型=101。
The QoS Connection Management message has the following format for both request and response messages:
QoS连接管理消息的请求和响应消息格式如下：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|M|Q|B|C| Input VPI | Input VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x x x x| Output VPI | Output VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number of Branches | Scheduler Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| QoS Class Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Regulator | Excess Action | Connection Weight |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|S|A|x x x x x x| Reserved | Excess Scheduler Id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ UPC Parameters ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Regulator Parameters ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|M|Q|B|C| Input VPI | Input VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x x x x| Output VPI | Output VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number of Branches | Scheduler Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| QoS Class Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Regulator | Excess Action | Connection Weight |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|S|A|x x x x x x| Reserved | Excess Scheduler Id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ UPC Parameters ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Regulator Parameters ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Port Session Number Input Port Input VPI Input VCI Output Port Output VPI Output VCI Number of Branches The definition of these fields is exactly the same as defined for the Add Branch message in Section 4.1, "Connection Management Messages."
端口会话号输入端口输入VPI输入VCI输出端口输出VPI输出VCI分支数这些字段的定义与第4.1节“连接管理消息”中添加分支消息的定义完全相同
M B C Flags The definition of the M, B, and C flags is exactly the same as defined in Section 4, "Connection Management Messages." They apply to the QoS Connection Management message exactly as defined for the Add Branch message.
M B C标志M、B和C标志的定义与第4节“连接管理消息”中的定义完全相同。它们适用于QoS连接管理消息，与添加分支消息的定义完全相同。
Q: QoS Profile Flag The QoS Profile flag is not used in the QoS Connection Management message.
Q:QoS配置文件标志QoS配置文件标志未在QoS连接管理消息中使用。
Scheduler Identifier For QoS Connection and QoS Class Connection styles, the Scheduler Identifier points to the waiting room, on the output port specified by the Output Port field, to which all conforming traffic on the connection should be routed. The values 0 -- 255 specify the default settings for the scheduler. Each of the default values maps directly to one of the scheduler priority levels. A Scheduler Identifier in the range 0 -- 255 may be used without first being established by a Scheduler Establishment message. All Scheduler Identifiers in the range 0x0100 to 0xFFFE must first be established by a Scheduler Establishment message.
调度器标识符对于QoS连接和QoS类连接样式，调度器标识符指向由输出端口字段指定的输出端口上的等待室，连接上的所有一致流量都应路由到该等待室。值0--255指定计划程序的默认设置。每个默认值都直接映射到一个调度程序优先级。可以使用范围为0到255的调度程序标识符，而无需首先通过调度程序建立消息建立。必须首先通过调度器建立消息建立0x0100到0xFFFE范围内的所有调度器标识符。
A Scheduler Identifier with a value of 0xFFFF indicates that a QoS Class Member connection style is being requested. In this connection style, the waiting room and output port are specified by reference to the QoS class specified by the QoS Class Identifier field. In this case the QoS Class Identifier field must contain a valid QoS Class Identifier.
值为0xFFFF的计划程序标识符表示正在请求QoS类成员连接样式。在这种连接样式中，等待室和输出端口通过引用QoS类标识符字段指定的QoS类来指定。在这种情况下，QoS类标识符字段必须包含有效的QoS类标识符。
QoS Class Identifier For QoS Class Connection and QoS Class Member connection styles, the QoS Class Identifier specifies the QoS Class to which the connection belongs. It must first be established by a QoS Class Establishment message and must have a value greater than 0 and less than 0xFFFFFFFF.
QoS类标识符对于QoS类连接和QoS类成员连接样式，QoS类标识符指定连接所属的QoS类。它必须首先由QoS类建立消息建立，并且必须具有大于0且小于0xFFFFFF的值。
A QoS Class Identifier with a value of 0xFFFFFFFF indicates that a connection of style "QoS Connection" is being requested. In this connection style, the connection does not belong to a QoS class. All QoS parameters are specified by the QoS Connection Management message and apply only to the specified connection.
值为0xFFFFFF的QoS类标识符表示正在请求“QoS连接”样式的连接。在此连接样式中，连接不属于QoS类。所有QoS参数都由QoS连接管理消息指定，并且仅适用于指定的连接。
Regulator Excess Action The Regulator and Excess Action parameters are only used in connection requests of style "QoS Connection." The
调节器过度动作调节器和过度动作参数仅用于“QoS连接”类型的连接请求
definition of these fields in the QoS Connection Management message is exactly the same as defined for the QoS Class Establishment message with the exception that they apply to an individual connection rather than to an entire QoS class.
QoS连接管理消息中这些字段的定义与QoS类建立消息中的定义完全相同，只是它们适用于单个连接，而不是整个QoS类。
Connection Weight This field is only used in connections of style "QoS Connection" and "QoS Class Connection." For QoS Class Member style connections, the QoS Class Weight parameter of the QoS Class Establishment message should be used to assign a weight to the QoS Class.
连接权重此字段仅用于“QoS连接”和“QoS类连接”类型的连接。对于QoS类成员类型的连接，应使用QoS类建立消息的QoS类权重参数为QoS类分配权重。
If bit 0 of the Scheduler Flags field of the QoS Configuration message indicates that weighted service may be applied to a connection, the Connection Weight parameter specifies the share of the bandwidth available to the waiting room that should be given to this connection.
如果QoS配置消息的Scheduler Flags字段的位0指示加权服务可应用于连接，则connection Weight参数指定应提供给此连接的等待室可用带宽的份额。
The Connection Weight is an unsigned 16-bit field specifying a binary fraction. I.e. the bandwidth share, as a fraction of the bandwidth available to the waiting room, is given by:
连接权重是指定二进制分数的无符号16位字段。即，带宽共享，作为候诊室可用带宽的一部分，由以下公式给出：
Bandwidth share = Connection Weight * 2**(-16)
Bandwidth share = Connection Weight * 2**(-16)
A Connection Weight of zero indicates equal sharing between all connections in this waiting room that request a Connection Weight of zero. While a 16-bit field is used to specify the Connection Weight it is understood that the accuracy of the bandwidth sharing is hardware dependent and is not specified.
连接权重为零表示此等候室中请求连接权重为零的所有连接之间的共享相等。虽然16位字段用于指定连接权重，但可以理解，带宽共享的精度取决于硬件，并且没有指定。
For connections of style "QoS Class Connection," if the Regulator function of the QoS Class is specified as None, or Policer, the Connection Weight should be applied to the waiting room pointed to by the Scheduler Identifier field in the QoS Connection Management message. If the Regulator function of the QoS Class is specified as Shaper, the Connection Weight should be applied to the waiting room pointed to by the Excess Scheduler Id field in the QoS Connection Management message.
对于“QoS类连接”类型的连接，如果QoS类的调节器功能指定为None或Policir，则连接权重应应用于QoS连接管理消息中调度器标识符字段所指向的等候室。如果QoS类的调节器功能被指定为整形器，则连接权重应应用于QoS连接管理消息中多余调度器Id字段所指向的等待室。
For connections of style "QoS Connection," if the Regulator field of the QoS Connection Management message specifies None, or Policer, the Connection Weight should be applied to the waiting room pointed to by the Scheduler Identifier field. If the Regulator field of the QoS Connection
对于“QoS连接”类型的连接，如果QoS连接管理消息的调节器字段指定None或Policir，则连接权重应应用于调度器标识符字段所指向的等候室。如果QoS连接的调节器字段
Management message specifies Shaper, the Connection Weight should be applied to the waiting room pointed to by the Excess Scheduler Id field.
管理消息指定了Shaper，连接权重应应用于多余调度器Id字段所指向的等候室。
If the specified waiting room is unable to offer weighted sharing for a connection, a failure response message should be returned with the failure code indicating: "this waiting room is unable to offer weighted sharing for a connection."
如果指定的等候室无法为连接提供加权共享，则应返回故障响应消息，并显示故障代码：“此等候室无法为连接提供加权共享。”
QoS Flags
QoS标志
S: Selective Discard If the Selective Discard flag is set, only cells with the Cell Loss Priority (CLP) bit set will be subject to the discard mechanism when the number of cells in the waiting room exceeds the Discard Threshold. If the Selective Discard flag is zero, all cells (CLP=0 and CLP=1) will be subject to the discard mechanism when the number of cells in the waiting room exceeds the Discard Threshold. Selective discard can be combined with packet discard. In this case only packets in which at least one cell has the CLP bit set will be subject to the discard mechanism.
S：选择性丢弃如果设置了选择性丢弃标志，当等待室中的单元数量超过丢弃阈值时，只有设置了单元丢失优先级（CLP）位的单元才会采用丢弃机制。如果选择性丢弃标志为零，则当等待室中的单元格数量超过丢弃阈值时，所有单元格（CLP=0和CLP=1）都将采用丢弃机制。选择性丢弃可以与数据包丢弃相结合。在这种情况下，只有其中至少有一个单元设置了CLP位的数据包才会受到丢弃机制的约束。
A: All Branches For a QoS Connection Management message that specifies a point-to-multipoint connection, if the All Branches flag is set, all branches of the point-to-multipoint connection must be set to the QoS parameters specified in the message. If the All Branches flag is zero, only the single output branch specified in the message should be set to the QoS parameters specified in the message. For a QoS Connection Management message that specifies a point-to-point connection, the All Branches flag is not used.
答：指定点到多点连接的QoS连接管理消息的所有分支，如果设置了“所有分支”标志，则必须将点到多点连接的所有分支设置为消息中指定的QoS参数。如果All Branchs标志为零，则只应将消息中指定的单个输出分支设置为消息中指定的QoS参数。对于指定点到点连接的QoS连接管理消息，不使用“所有分支”标志。
x: Unused
x:未使用
Excess Scheduler Id For connections of style "QoS Connection" and "QoS Class Connection," the Excess Scheduler Id points to the waiting room, on the output port specified by the Output Port field, to which all excess traffic should be routed. The values 0 -- 255 specify the default settings for the scheduler. Each of the default values maps directly to one of the scheduler priority levels. An Excess Scheduler Id in the range 0 -- 255 may be used without first being established by a Scheduler Establishment message. All
多余的调度程序Id对于“QoS连接”和“QoS类连接”类型的连接，多余的调度程序Id指向由输出端口字段指定的输出端口上的等待室，所有多余的流量都应路由到该等待室。值0--255指定计划程序的默认设置。每个默认值都直接映射到一个调度程序优先级。可以使用范围为0到255的多余调度程序Id，而无需首先通过调度程序建立消息建立。全部的
values of Excess Scheduler Id in the range 0x0100 to 0xFFFE must first be established by a Scheduler Establishment message.
必须首先通过调度器建立消息建立0x0100到0xFFFE范围内的多余调度器Id值。
If this field is not used it should be set to 0xFFFF. The Excess Scheduler Id must not point to the same waiting room on the same output port as the Scheduler Identifier.
如果未使用此字段，则应将其设置为0xFFFF。多余的计划程序Id不得与计划程序标识符指向同一输出端口上的同一等待室。
UPC Parameters All connection styles may be subject to a Usage Parameter Control (UPC) function, also known as a connection policer. The policing function is applied to each individual connection before it is combined with other connections into a QoS class by the classifier function. A policing function applied to an entire QoS class is defined in the QoS Class Establishment message.
UPC参数所有连接样式都可能受使用参数控制（UPC）功能的约束，也称为连接策略。在分类器功能将每个连接与其他连接组合成一个QoS类之前，将对每个连接应用策略功能。应用于整个QoS类的策略功能在QoS类建立消息中定义。
The connection policer is defined by reference to the Generic Cell Rate Algorithm (GCRA) defined by the ATM Forum [af-tm-0056], although any equivalent policing algorithm may be used. The GCRA takes two parameters, the increment (I) and the limit (L). The reciprocal of the increment (1/I) specifies the rate being policed. The limit specifies the burst tolerance. (For comparison with the token bucket policer discussed in [Partridge], the size of the token bucket is given by L/I.)
连接策略通过参考ATM论坛[af-tm-0056]定义的通用信元速率算法（GCRA）来定义，尽管可以使用任何等效的策略算法。GCRA采用两个参数，增量（I）和极限（L）。增量的倒数（1/I）指定了策略的速率。该限制指定突发容差。（为了与[Partridge]中讨论的令牌桶策略进行比较，令牌桶的大小由L/I给出。）
Two policers in series may be specified to permit the policing of both peak rate and average rate (also called sustainable rate). The parameters for the first policer are Increment-1 and Limit-1. For comparison with the ATM Forum specification these would be used to police the Peak Cell Rate (PCR) and Cell Delay Variation Tolerance (CDVT) respectively. The parameters for the second policer are Increment-2 and Limit-2. For comparison with the ATM Forum specification these would be used to police the Sustainable Cell Rate (SCR), and Burst Tolerance. (The Burst Tolerance may be computed from the Maximum Burst Size [af-tm-0056].)
可以指定两个串联的警察，以允许对峰值速率和平均速率（也称为可持续速率）进行监管。第一个policer的参数是Increment-1和Limit-1。为了与ATM论坛规范进行比较，这些规范将分别用于监控峰值信元速率（PCR）和信元延迟变化容忍度（CDVT）。第二个策略的参数是Increment-2和Limit-2。为了与ATM论坛规范进行比较，这些规范将用于监控可持续信元速率（SCR）和突发容忍度。（突发容差可根据最大突发大小[af-tm-0056]计算。）
There are two configurations in which the two policers may be connected in series. In the All Cells configuration, all cells (cells with the Cell Loss Priority (CLP) bit set to zero and cells with the CLP bit set to one) are subject to the policing action of both policers in series. In the CLP Selective configuration, all cells, both CLP=0 and CLP=1, are policed by the first policer; but only cells
有两种配置，其中两个策略可以串联连接。在所有单元配置中，所有单元（单元丢失优先级（CLP）位设置为零的单元和CLP位设置为一的单元）都受到两个串联的策略的监控。在CLP选择性配置中，所有单元（CLP=0和CLP=1）均由第一个策略器进行策略；但只有细胞
with CLP=0 are subject to policing by the second policer. Either tagging or discard may be specified for each of the policer configurations.
CLP=0时，由第二个警察进行监管。可以为每个policer配置指定标记或放弃。
The values of the parameters Increment and Limit in the UPC Parameters fields are given in terms of a time unit specified by the switch in the QoS Configuration Parameters message. The time unit is specified by the switch as a rate, the Scaling Factor, which gives the rate in cells per second that would result from an Increment parameter value of one. Thus to determine the value of the Increment parameter from the desired policed rate given in cells per second:
UPC参数字段中的参数增量和限制值根据QoS配置参数消息中交换机指定的时间单位给出。时间单位由开关指定为速率，即比例因子，它给出增量参数值为1时产生的速率（以每秒单元数为单位）。因此，要根据以每秒单元数为单位给出的期望策略速率来确定增量参数的值：
Increment parameter = (Scaling_Factor)/(policed_rate)
Increment parameter = (Scaling_Factor)/(policed_rate)
To determine the value of the Limit parameter from the desired Cell Delay Variation Tolerance (CDVT) given in seconds:
要根据以秒为单位给出的所需单元延迟变化公差（CDVT）确定极限参数的值：
Limit parameter = CDVT * Scaling_Factor
极限参数=CDVT*比例系数
To determine the value of the Limit parameter from the desired Burst Tolerance (BT) given in seconds:
要根据以秒为单位给出的期望脉冲串容差（BT）确定极限参数的值：
Limit parameter = BT * Scaling_Factor
极限参数=BT*比例系数
The Increment and Limit parameters are specified as 32-bit unsigned integers; so the choice of the Scaling Factor allows the switch to select the range and granularity of the policer parameters with respect to the line rate of the switch port. For example, a SONET STS-3c (155.52 Mbps) switch port has a line rate of approximately 353 kcells/s. With a Scaling Factor value of 353,000,000 we can specify a policed rate slightly less than the line rate with a granularity of 0.1%. For a policed rate of 1 kbps we can still support a bucket size of 31 cells.
增量和限制参数指定为32位无符号整数；因此，比例因子的选择允许交换机根据交换机端口的线路速率选择policer参数的范围和粒度。例如，SONET STS-3c（155.52 Mbps）交换机端口的线速率约为353 kcells/s。当比例因子值为353000000时，我们可以指定略小于行速率的策略速率，粒度为0.1%。对于1 kbps的策略速率，我们仍然可以支持31个单元的存储桶大小。
The UPC Parameters have the following format:
UPC参数的格式如下：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Increment-1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Limit-1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Increment-2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Limit-2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved |C|A|x x x x x x|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Increment-1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Limit-1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Increment-2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Limit-2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved |C|A|x x x x x x|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Increment-1 The increment parameter for the first policer, specified as a 32-bit unsigned integer. A value of zero for the Increment-1 parameter is used to disable the first policer. In this case all cells will be considered to conform to the traffic parameters of the first policer.
Increment-1第一个policr的Increment参数，指定为32位无符号整数。增量-1参数的值为零，用于禁用第一个策略。在这种情况下，所有小区将被视为符合第一个策略的流量参数。
Limit-1 The limit parameter for the first policer, specified as a 32-bit unsigned integer.
Limit-1第一个policer的Limit参数，指定为32位无符号整数。
Increment-2 The increment parameter for the second policer, specified as a 32-bit unsigned integer. A value of zero for the Increment-2 parameter is used to disable the second policer. In this case all cells will be considered to conform to the traffic parameters of the second policer.
Increment-2第二个policr的Increment参数，指定为32位无符号整数。增量-2参数的值为零用于禁用第二个策略。在这种情况下，所有小区将被视为符合第二个策略的流量参数。
Limit-2 The limit parameter for the second policer, specified as a 32-bit unsigned integer.
Limit-2第二个policer的Limit参数，指定为32位无符号整数。
Flags
旗帜
C: Configuration If the Configuration flag is set, the policer should be set to the All Cells configuration. If the Configuration flag is zero, the policer should be set to the CLP Selective configuration.
C:配置如果设置了配置标志，则应将policr设置为“所有单元”配置。如果配置标志为零，则应将policr设置为CLP选择性配置。
In the All Cells configuration, all cells (both CLP=0 and CLP=1) are subject to the policing action of both policers in series. In the CLP Selective configuration, all cells, both CLP=0 and CLP=1, are policed by the first policer; but
在All CELL配置中，所有单元（CLP=0和CLP=1）都受两个串联的策略的控制。在CLP选择性配置中，所有单元（CLP=0和CLP=1）均由第一个策略器进行策略；但是
only cells with CLP=0 are subject to policing by the second policer. Either tagging or discard may be specified for each of the policer configurations.
只有CLP=0的单元格才受第二个策略器的策略控制。可以为每个policer配置指定标记或放弃。
A: Action If the Action flag is zero, discard is required as the policing action. If the Action flag is set, tagging is required as the policing action.
A:操作如果操作标志为零，则需要放弃作为策略操作。如果设置了操作标志，则需要标记作为监控操作。
If tagging is selected in the All Cells configuration, any cell with CLP=0 in either policer, that the policer determines to be in excess of the specified policer parameters, will be changed to CLP=1. If discard is selected in the All Cells configuration, any cell (CLP=0 or CLP=1) in either policer, that the policer determines to be in excess of the specified policer parameters, will be discarded.
如果在“所有单元”配置中选择了标记，则任何一个policr中CLP=0且policr确定超出指定policr参数的单元都将更改为CLP=1。如果在“所有单元”配置中选择了“放弃”，则任何一个policr中policr确定超出指定policr参数的单元（CLP=0或CLP=1）都将被放弃。
In the CLP Selective configuration, the first policer is always set to discard any cell (CLP=0 or CLP=1) that it determines to be in excess of its specified policer parameters. If tagging is selected in the CLP Selective configuration, the second policer will change the CLP bit to CLP=1 of any cell that it determines to be in excess of its specified parameters. If discard is selected in the CLP Selective configuration, the second policer will discard any cell that it determines to be in excess of its specified parameters.
在CLP选择性配置中，第一个policr始终设置为丢弃其确定超出其指定policr参数的任何单元（CLP=0或CLP=1）。如果在CLP选择性配置中选择了标记，则第二个策略器将其确定超出其指定参数的任何单元格的CLP位更改为CLP=1。如果在CLP选择性配置中选择了discard，则第二个策略器将丢弃其确定超出其指定参数的任何单元格。
To configure the policer for the conformance definitions specified by the ATM Forum [af-tm-0056] the following configurations are suggested:
要为ATM论坛[af-tm-0056]指定的一致性定义配置策略，建议使用以下配置：
CBR.1: One policer, All Cells, Discard VBR.1: Two policers, All Cells, Discard VBR.2: Two policers, CLP Selective, Discard VBR.3: Two policers, CLP Selective, Tagging UBR.1: One policer, All Cells, Discard UBR.2: One policer, All Cells, Tagging.
案例1：一个策略，所有单元格，放弃VBR。1：两个策略，所有单元格，放弃VBR。2：两个策略，CLP选择性，放弃VBR。3：两个策略，CLP选择性，标记UBR。1：一个策略，所有单元格，放弃UBR。2：一个策略，所有单元格，标记。
x: Unused
x:未使用
Regulator Parameters Only connections of style "QoS Connection" require the Regulator Parameters to be specified in the QoS Connection Management message. For connections of style "QoS Class Connection" and "QoS Class Member" the Regulator Parameters are specified in the QoS Class Establishment message.
调节器参数仅“QoS连接”类型的连接要求在QoS连接管理消息中指定调节器参数。对于“QoS类连接”和“QoS类成员”类型的连接，调节器参数在QoS类建立消息中指定。
The Regulator Parameters are specified in a similar manner to the UPC parameters. If the regulator function is specified as Policing, a single GCRA policer is applied to all cells (both CLP=0 and CLP=1) on the connection. The policer takes two parameters: an increment, the Regulator Increment, and a limit, the Regulator Limit. The reciprocal of the increment (1/I) specifies the rate being policed. The limit (L) specifies the burst tolerance. (For comparison with the token bucket policer discussed in [Partridge], the size of the token bucket is given by L/I.)
调节器参数的规定方式与UPC参数类似。如果调节器功能指定为Policing，则单个GCRA policir将应用于连接上的所有单元（CLP=0和CLP=1）。policer接受两个参数：一个是增量，调节器增量，一个是限制，调节器限制。增量的倒数（1/I）指定了策略的速率。限值（L）指定脉冲串容差。（为了与[Partridge]中讨论的令牌桶策略进行比较，令牌桶的大小由L/I给出。）
The Regulator Increment and Regulator Limit parameters are 32-bit unsigned integers. Their values are determined in terms of the Scaling Factor specified by the switch in the QoS Configuration Parameters message. To determine the value of the Regulator Increment parameter from the desired policed rate given in cells per second:
调节器增量和调节器限制参数是32位无符号整数。它们的值根据交换机在QoS配置参数消息中指定的比例因子确定。要根据以每秒单元数为单位的所需策略速率确定调节器增量参数的值：
Regulator Increment = (Scaling_Factor)/(policed_rate)
Regulator Increment = (Scaling_Factor)/(policed_rate)
For a policed rate (r) the GCRA policer guarantees that over any time period T the amount of traffic determined by the policer to be conforming to the traffic parameters does not exceed:
对于管制费率（r），GCRA管制人员保证在任何时间段T内，管制人员确定的符合交通参数的交通量不超过：
rT + L/I
rT+L/I
The value of the Regulator Limit may be determined from this relation.
调节器限值可根据该关系确定。
If the regulator function is specified as Shaping, only the Regulator Increment parameter is used. The Regulator Limit parameter is not used. The value of the Regulator Increment parameter is determined in terms of the Scaling Factor specified by the switch in the QoS Configuration Parameters message. To determine the value of the Regulator Increment parameter from the desired shaper rate, given in cells per second, on output from the shaper:
如果调节器功能指定为整形，则仅使用调节器增量参数。未使用调节器限制参数。调节器增量参数的值根据QoS配置参数消息中交换机指定的比例因子确定。要根据整形器输出的所需整形器速率（以每秒单元数为单位）确定调节器增量参数的值：
Regulator Increment = (Scaling_Factor)/(shaper_rate)
Regulator Increment = (Scaling_Factor)/(shaper_rate)
An Increment value of zero is used to disable the policer. In this case all cells on that connection will be considered to conform to the policer traffic parameters. A shaper given a Regulator Increment parameter of zero will perform no shaping function on that connection.
增量值为零用于禁用策略器。在这种情况下，该连接上的所有单元都将被视为符合policer流量参数。给定调节器增量参数为零的整形器不会对该连接执行整形功能。
The Regulator Parameters have the following format:
调节器参数的格式如下：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Regulator Increment |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Regulator Limit |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Regulator Increment |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Regulator Limit |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
A failure response message is formed by returning the request message that caused the failure with the Result field in the header indicating failure (Result = 4) and the Code field giving the failure code. The failure code specifies the reason for the switch being unable to satisfy the request message. The following additional failure codes are defined for use in response to QoS messages. General failure codes are specified in Section 3.2, Failure Response Messages.
通过返回导致故障的请求消息形成故障响应消息，报头中的结果字段指示故障（结果=4），代码字段给出故障代码。故障代码指定交换机无法满足请求消息的原因。定义了以下附加故障代码，以用于响应QoS消息。第3.2节“故障响应消息”中规定了一般故障代码。
128: Weighted scheduling within this waiting room is unavailable. 129: This waiting room is unable to offer weighted sharing for a QoS class. 130: This waiting room is unable to offer weighted sharing for a connection. 131: Scheduler Identifier still in use. 132: QoS Class Identifier still in use. 133: Invalid QoS parameter. 134: Insufficient QoS resources. 135: Any point-to-multipoint connection arriving on this input port must use the same QoS parameters for all output branches.
128:此等候室内的加权调度不可用。129:此等候室无法为QoS类提供加权共享。130:此等候室无法为连接提供加权共享。131:计划程序标识符仍在使用中。132:QoS类标识符仍在使用中。133:无效的QoS参数。134：QoS资源不足。135:到达此输入端口的任何点对多点连接必须对所有输出分支使用相同的QoS参数。
The adjacency protocol is used to synchronize state across the link, to agree on which version of the protocol to use, to discover the identity of the entity at the other end of a link, and to detect when it changes. GSMP is a hard state protocol. It is therefore important to detect loss of contact between switch and controller, and to detect any change of identity of switch or controller. No GSMP messages other than those of the adjacency protocol may be sent across the link until the adjacency protocol has achieved synchronization.
邻接协议用于同步链路上的状态，商定要使用的协议版本，发现链路另一端实体的标识，并检测其何时更改。GSMP是一种硬状态协议。因此，检测开关和控制器之间的接触损失以及检测开关或控制器身份的任何变化非常重要。在邻接协议实现同步之前，不得通过链路发送除邻接协议以外的GSMP消息。
All GSMP messages belonging to the adjacency protocol have the following structure:
属于邻接协议的所有GSMP消息具有以下结构：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Timer |M| Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sender Name |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| Receiver Name |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sender Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Receiver Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sender Instance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Receiver Instance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Timer |M| Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sender Name |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| Receiver Name |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sender Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Receiver Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sender Instance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Receiver Instance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Version In the adjacency protocol the Version field is used for version negotiation. In a SYN message the Version field always contains the highest version understood by the sender. A receiver receiving a SYN message with a version higher than understood will ignore that message. A receiver receiving a SYN message with a version lower than its own highest version, but a version that it understands, will reply with a SYNACK with the version from the received SYN in its GSMP Version field. This defines the version of the GSMP protocol to be used while the adjacency protocol remains synchronized. All other messages will use the agreed version in the Version field.
版本在邻接协议中，版本字段用于版本协商。在SYN消息中，“版本”字段始终包含发件人理解的最高版本。接收版本高于理解版本的SYN消息的接收方将忽略该消息。接收到版本低于其最高版本但其理解的版本的SYN消息的接收方将在其GSMP版本字段中使用来自接收到的SYN的版本的SYNACK进行回复。这定义了在邻接协议保持同步时要使用的GSMP协议的版本。所有其他消息将使用版本字段中的商定版本。
The version number for the version of the GSMP protocol defined by this specification is Version = 2.
本规范定义的GSMP协议版本的版本号为version=2。
Message Type The adjacency protocol is:
邻接协议的消息类型为：
Message Type = 10
消息类型=10
Timer The Timer field is used to inform the receiver of the timer value used in the adjacency protocol of the sender. The timer specifies the nominal time between periodic adjacency protocol messages. It is a constant for the duration of a GSMP session. The timer field is specified in units of 100ms.
定时器定时器字段用于通知接收方发送方邻接协议中使用的定时器值。计时器指定周期性邻接协议消息之间的标称时间。它是GSMP会话期间的常数。计时器字段以100ms为单位指定。
M-Flag The M-Flag is used in the SYN message to indicate whether the sender is a master or a slave. If the M-Flag is set in the SYN message, the sender is a master. If zero, the sender is a slave. The GSMP protocol is asymmetric, the controller being the master and the switch being the slave. The M-Flag prevents a master from synchronizing with another master, or a slave with another slave. If a slave receives a SYN message with a zero M-Flag, it must ignore that SYN message. If a master receives a SYN message with the M-Flag set, it must ignore that SYN message. In all other messages the M-Flag is not used.
M-Flag在SYN消息中使用M-Flag来指示发送方是主发送方还是从发送方。如果在SYN消息中设置了M标志，则发送方是主发送方。如果为零，则发送方是从机。GSMP协议是非对称的，控制器是主设备，交换机是从设备。M标志防止主设备与另一主设备或从设备与另一从设备同步。如果从机接收到带有零M标志的SYN消息，则必须忽略该SYN消息。如果主机接收到设置了M标志的SYN消息，则必须忽略该SYN消息。在所有其他消息中，不使用M标志。
Code Field specifies the function of the message. Four Codes are defined for the adjacency protocol:
代码字段指定消息的功能。为邻接协议定义了四个代码：
SYN: Code = 1 SYNACK: Code = 2 ACK: Code = 3 RSTACK: Code = 4.
SYN:Code=1 SYNACK:Code=2 ACK:Code=3 RSTACK:Code=4。
Sender Name For the SYN, SYNACK, and ACK messages, is the name of the entity sending the message. The Sender Name is a 48-bit quantity that is unique within the operational context of the device. A 48-bit IEEE 802 MAC address, if available, may be used for the Sender Name. If the Ethernet encapsulation is used the Sender Name must be the Source Address from the MAC header. For the RSTACK message, the Sender Name field is set to the value of the Receiver Name field from the incoming message that caused the RSTACK message to be generated.
SYN、SYNACK和ACK消息的发件人名称是发送消息的实体的名称。发送方名称是48位的数量，在设备的操作上下文中是唯一的。48位IEEE 802 MAC地址（如果可用）可用于发送方名称。如果使用以太网封装，则发送方名称必须是MAC头中的源地址。对于RSTACK消息，发送方名称字段设置为导致生成RSTACK消息的传入消息的接收方名称字段的值。
Receiver Name For the SYN, SYNACK, and ACK messages, is the name of the entity that the sender of the message believes is at the far end of the link. If the sender of the message does not know the name of the entity at the far end of the link, this field should be set to zero. For the RSTACK message,
SYN、SYNACK和ACK消息的接收方名称是消息发送方认为位于链路远端的实体的名称。如果消息的发送者不知道链接远端实体的名称，则此字段应设置为零。对于RSTACK消息，
the Receiver Name field is set to the value of the Sender Name field from the incoming message that caused the RSTACK message to be generated.
接收方名称字段设置为导致生成RSTACK消息的传入消息的发送方名称字段的值。
Sender Port For the SYN, SYNACK, and ACK messages, is the local port number of the link across which the message is being sent. For the RSTACK message, the Sender Port field is set to the value of the Receiver Port field from the incoming message that caused the RSTACK message to be generated.
SYN、SYNACK和ACK消息的发送方端口是发送消息的链路的本地端口号。对于RSTACK消息，发送方端口字段设置为导致生成RSTACK消息的传入消息的接收方端口字段的值。
Receiver Port For the SYN, SYNACK, and ACK messages, is what the sender believes is the local port number for the link, allocated by the entity at the far end of the link. If the sender of the message does not know the port number at the far end of the link, this field should be set to zero. For the RSTACK message, the Receiver Port field is set to the value of the Sender Port field from the incoming message that caused the RSTACK message to be generated.
SYN、SYNACK和ACK消息的接收方端口是发送方认为是链路的本地端口号，由链路远端的实体分配。如果消息发送方不知道链路远端的端口号，则此字段应设置为零。对于RSTACK消息，接收方端口字段设置为导致生成RSTACK消息的传入消息的发送方端口字段的值。
Sender Instance For the SYN, SYNACK, and ACK messages, is the sender's instance number for the link. It is used to detect when the link comes back up after going down or when the identity of the entity at the other end of the link changes. The instance number is a 32-bit number that is guaranteed to be unique within the recent past and to change when the link or node comes back up after going down. Zero is not a valid instance number. For the RSTACK message, the Sender Instance field is set to the value of the Receiver Instance field from the incoming message that caused the RSTACK message to be generated.
SYN、SYNACK和ACK消息的发送方实例是链接的发送方实例号。它用于检测链路在下降后何时恢复，或者链路另一端的实体标识何时更改。实例号是一个32位的数字，保证在最近一段时间内是唯一的，并且在链路或节点关闭后恢复时会发生变化。零不是有效的实例号。对于RSTACK消息，发送方实例字段设置为导致生成RSTACK消息的传入消息的接收方实例字段的值。
Receiver Instance For the SYN, SYNACK, and ACK messages, is what the sender believes is the current instance number for the link, allocated by the entity at the far end of the link. If the sender of the message does not know the current instance number at the far end of the link, this field should be set to zero. For the RSTACK message, the Receiver Instance field is set to the value of the Sender Instance field from the incoming message that caused the RSTACK message to be generated.
SYN、SYNACK和ACK消息的接收方实例是发送方认为的链路的当前实例号，由链路远端的实体分配。如果消息的发送者不知道链接远端的当前实例号，则此字段应设置为零。对于RSTACK消息，Receiver Instance字段设置为导致生成RSTACK消息的传入消息的Sender Instance字段的值。
The adjacency protocol is described by the following rules and state tables.
邻接协议由以下规则和状态表描述。
The rules and state tables use the following operations:
规则和状态表使用以下操作：
o The "Update Peer Verifier" operation is defined as storing the values of the Sender Instance, Sender Port, and Sender Name fields from a SYN or SYNACK message received from the entity at the far end of the link.
o “更新对等验证器”操作定义为存储从链路远端的实体接收到的SYN或SYNACK消息中的发送方实例、发送方端口和发送方名称字段的值。
o The procedure "Reset the link" is defined as:
o “重置链接”程序定义为：
1. Generate a new instance number for the link 2. Delete the peer verifier (set to zero the values of Sender Instance, Sender Port, and Sender Name previously stored by the Update Peer Verifier operation) 3. Send a SYN message 4. Enter the SYNSENT state.
1. 为链接2生成新的实例号。删除对等验证器（将更新对等验证器操作之前存储的发送方实例、发送方端口和发送方名称的值设置为零）3。发送SYN消息4。输入SYNSENT状态。
o The state tables use the following Boolean terms and operators:
o 状态表使用以下布尔术语和运算符：
A The Sender Instance in the incoming message matches the value stored from a previous message by the "Update Peer Verifier" operation.
传入消息中的发送方实例与“更新对等验证器”操作从先前消息中存储的值相匹配。
B The Sender Instance, Sender Port, and Sender Name fields in the incoming message match the values stored from a previous message by the "Update Peer Verifier" operation.
B传入消息中的发送方实例、发送方端口和发送方名称字段与“更新对等验证程序”操作从以前的消息中存储的值相匹配。
C The Receiver Instance, Receiver Port, and Receiver Name fields in the incoming message match the values of the Sender Instance, Sender Port, and Sender Name currently sent in outgoing SYN, SYNACK, and ACK messages.
C The Receiver Instance, Receiver Port, and Receiver Name fields in the incoming message match the values of the Sender Instance, Sender Port, and Sender Name currently sent in outgoing SYN, SYNACK, and ACK messages.translate error, please retry
"&&" Represents the logical AND operation
“&&”表示逻辑与运算
"||" Represents the logical OR operation
“| |”表示逻辑OR操作
"!" Represents the logical negation (NOT) operation.
“！”表示逻辑否定（NOT）操作。
o A timer is required for the periodic generation of SYN, SYNACK, and ACK messages. The value of the timer is announced in the Timer field. The period of the timer is unspecified but a value of one second is suggested.
o 定期生成SYN、SYNACK和ACK消息需要计时器。计时器的值在计时器字段中宣布。未指定计时器的周期，但建议使用1秒的值。
There are two independent events: the timer expires, and a packet arrives. The processing rules for these events are:
有两个独立的事件：计时器过期和数据包到达。这些事件的处理规则是：
Timer Expires: Reset Timer If state = SYNSENT Send SYN If state = SYNRCVD Send SYNACK If state = ESTAB Send ACK
计时器过期：如果状态=SYNSED Send SYN如果状态=SYNRCVD Send SYNACK如果状态=ESTAB Send ACK，则重置计时器
Packet Arrives: If incoming message is an RSTACK: If (A && C && !SYNSENT) Reset the link Else Discard the message. If incoming message is a SYN, SYNACK, or ACK: Response defined by the following State Tables. If incoming message is any other GSMP message and state != ESTAB: Discard incoming message. If state = SYNSENT Send SYN (Note 1) If state = SYNRCVD Send SYNACK (Note 1)
数据包到达：如果传入消息是RSTACK：如果（A&&C&&！SYNSEMENT）重置链接，否则丢弃消息。如果传入消息是SYN、SYNACK或ACK：由以下状态表定义的响应。如果传入消息是任何其他GSMP消息和状态！=ESTAB：丢弃传入消息。如果状态=SYNSED Send SYN（注1）如果状态=SYNRCVD Send SYNACK（注1）
Note 1: No more than two SYN or SYNACK messages should be sent within any time period of length defined by the timer.
注1：在计时器定义的任何时间段内，发送的SYN或SYNACK消息不得超过两条。
o State synchronization across a link is considered to be achieved when the protocol reaches the ESTAB state. All GSMP messages, other than adjacency protocol messages, that are received before synchronization is achieved will be discarded.
o 当协议达到ESTAB状态时，链路上的状态同步被认为是实现的。在实现同步之前接收的所有GSMP消息（邻接协议消息除外）将被丢弃。
State Tables
状态表
State: SYNSENT
国家：SYNSENT
+======================================================================+
| Condition | Action | New State |
+====================+=====================================+===========+
| SYNACK && C | Update Peer Verifier; Send ACK | ESTAB |
+--------------------+-------------------------------------+-----------+
| SYNACK && !C | Send RSTACK | SYNSENT |
+--------------------+-------------------------------------+-----------+
| SYN | Update Peer Verifier; Send SYNACK | SYNRCVD |
+--------------------+-------------------------------------+-----------+
| ACK | Send RSTACK | SYNSENT |
+======================================================================+
+======================================================================+
| Condition | Action | New State |
+====================+=====================================+===========+
| SYNACK && C | Update Peer Verifier; Send ACK | ESTAB |
+--------------------+-------------------------------------+-----------+
| SYNACK && !C | Send RSTACK | SYNSENT |
+--------------------+-------------------------------------+-----------+
| SYN | Update Peer Verifier; Send SYNACK | SYNRCVD |
+--------------------+-------------------------------------+-----------+
| ACK | Send RSTACK | SYNSENT |
+======================================================================+
State: SYNRCVD
州：SYNRCVD
+======================================================================+
| Condition | Action | New State |
+====================+=====================================+===========+
| SYNACK && C | Update Peer Verifier; Send ACK | ESTAB |
+--------------------+-------------------------------------+-----------+
| SYNACK && !C | Send RSTACK | SYNRCVD |
+--------------------+-------------------------------------+-----------+
| SYN | Update Peer Verifier; Send SYNACK | SYNRCVD |
+--------------------+-------------------------------------+-----------+
| ACK && B && C | Send ACK | ESTAB |
+--------------------+-------------------------------------+-----------+
| ACK && !(B && C) | Send RSTACK | SYNRCVD |
+======================================================================+
+======================================================================+
| Condition | Action | New State |
+====================+=====================================+===========+
| SYNACK && C | Update Peer Verifier; Send ACK | ESTAB |
+--------------------+-------------------------------------+-----------+
| SYNACK && !C | Send RSTACK | SYNRCVD |
+--------------------+-------------------------------------+-----------+
| SYN | Update Peer Verifier; Send SYNACK | SYNRCVD |
+--------------------+-------------------------------------+-----------+
| ACK && B && C | Send ACK | ESTAB |
+--------------------+-------------------------------------+-----------+
| ACK && !(B && C) | Send RSTACK | SYNRCVD |
+======================================================================+
State: ESTAB
州：ESTAB
+======================================================================+
| Condition | Action | New State |
+====================+=====================================+===========+
| SYN || SYNACK | Send ACK (note 2) | ESTAB |
+--------------------+-------------------------------------+-----------+
| ACK && B && C | Send ACK (note 3) | ESTAB |
+--------------------+-------------------------------------+-----------+
| ACK && !(B && C) | Send RSTACK | ESTAB |
+======================================================================+
+======================================================================+
| Condition | Action | New State |
+====================+=====================================+===========+
| SYN || SYNACK | Send ACK (note 2) | ESTAB |
+--------------------+-------------------------------------+-----------+
| ACK && B && C | Send ACK (note 3) | ESTAB |
+--------------------+-------------------------------------+-----------+
| ACK && !(B && C) | Send RSTACK | ESTAB |
+======================================================================+
Note 2: No more than two ACKs should be sent within any time period of length defined by the timer. Thus, one ACK must be sent every time the timer expires. In addition, one further ACK may be sent between timer expirations if the incoming message is a SYN or SYNACK. This additional ACK allows the adjacency protocol to reach synchronization more quickly.
注2：在计时器定义的任何时间段内，发送的ACK不得超过两个。因此，每次计时器过期时必须发送一个ACK。此外，如果传入消息是SYN或SYNACK，则可以在计时器到期之间发送另一个ACK。这个额外的ACK允许邻接协议更快地达到同步。
Note 3: No more than one ACK should be sent within any time period of length defined by the timer.
注3：在计时器定义的任何时间段内，不应发送超过一个ACK。
If after synchronization is achieved, no valid GSMP messages are received in any period of time in excess of three times the value of the Timer field announced in the incoming adjacency protocol messages, loss of synchronization may be declared.
如果在实现同步后，在超过传入邻接协议消息中宣布的计时器字段值三倍的任何时间段内未收到有效的GSMP消息，则可能会宣布同步丢失。
The preferred procedure for a switch to use when it looses synchronization with its active controller is to attempt to establish
当交换机与其主动控制器失去同步时，其首选程序是尝试建立
synchronization with (one of) its backup controller(s). However, in this preferred approach, it must not reset its state until it achieves synchronization with a backup controller. This means that if, before achieving synchronization with a backup controller, it regains synchronization with its original controller, it may continue the original session (and cease attempting to establish synchronization with a backup controller). If synchronization with the original session is regained it is the responsibility of the controller to ensure consistent state between the switch and controller.
与（其中一个）备份控制器同步。但是，在这种首选方法中，在与备份控制器实现同步之前，不得重置其状态。这意味着，如果在与备份控制器实现同步之前，它恢复了与原始控制器的同步，则它可以继续原始会话（并停止尝试与备份控制器建立同步）。如果恢复与原始会话的同步，则控制器有责任确保交换机和控制器之间的状态一致。
While the above is the preferred procedure, it is also the case that the simplest procedure when declaring loss of synchronization with the active controller is to reset the switch state, and start searching for a controller. This simple procedure is legitimate.
虽然上述是首选程序，但在声明与活动控制器失去同步时，最简单的程序也是重置开关状态，并开始搜索控制器。这个简单的程序是合法的。
The following list gives a summary of the failure codes defined for failure response messages:
下表总结了为故障响应消息定义的故障代码：
1: Unspecified reason not covered by other failure codes. 2: Invalid request message. 3: The specified request is not implemented on this switch. 4: Invalid Port Session Number. 5: One or more of the specified ports does not exist. 6: One or more of the specified ports is down. 7: Unused. (This failure code has been replaced by failure codes 18--21.) 8: The specified connection does not exist. 9: The specified branch does not exist. 10: A branch belonging to the specified point-to-multipoint connection is already established on the specified output port and the switch cannot support more than a single branch of any point-to-multipoint connection on the same output port. 11: The limit on the maximum number of point-to-multipoint connections that the switch can support has been reached. 12: The limit on the maximum number of branches that the specified point-to-multipoint connection can support has been reached. 13: Unable to assign the requested VPI/VCI value to the requested branch on the specified point-to-multipoint connection. 14: General problem related to the manner in which point-to-multipoint is supported by the switch. 15: Out of resources (e.g. memory exhausted, etc.). 16: Failure specific to the particular message type. (The meaning of this failure code depends upon the Message Type. It is
1：其他故障代码未涵盖的未指定原因。2：无效的请求消息。3:指定的请求未在此交换机上实现。4：端口会话号无效。5:一个或多个指定端口不存在。6:一个或多个指定端口关闭。7：未使用。（此故障代码已替换为故障代码18--21。）8:指定的连接不存在。9:指定的分支不存在。10:已在指定的输出端口上建立了属于指定的点对多点连接的分支，并且交换机不能在同一输出端口上支持任何点对多点连接的多个分支。11：已达到交换机可支持的最大点对多点连接数限制。12:已达到指定点对多点连接可支持的最大分支数限制。13:无法在指定的点对多点连接上将请求的VPI/VCI值分配给请求的分支。14：与交换机支持点对多点的方式有关的一般问题。15：资源不足（例如内存耗尽等）。16：特定于特定消息类型的故障。（此故障代码的含义取决于消息类型。它是
defined within the description of any message that uses it.) 17: Cannot label each output branch of a point-to-multipoint tree with a different label. 18: One or more of the specified input VPIs is invalid. 19: One or more of the specified input VCIs is invalid. 20: One or more of the specified output VPIs is invalid. 21: One or more of the specified output VCIs is invalid. 22: Invalid Class of Service field in a Connection Management message. 23: Insufficient resources for QoS Profile. 24: Virtual path switching is not supported on this input port. 25: Point-to-multipoint virtual path connections are not supported on either the requested input port or the requested output port. 26: Attempt to add a virtual path connection branch to an existing virtual channel connection. 27: Attempt to add a virtual channel connection branch to an existing virtual path connection. 28: Only point-to-point bidirectional connections may be established. 29: Cannot support requested VPI range. 30: Cannot support requested VCI range on all requested VPIs. 31: The transmit cell rate of this output port cannot be changed. 32: Requested transmit cell rate out of range for this output port. 128: Weighted scheduling within this waiting room is unavailable. 129: This waiting room is unable to offer weighted sharing for a QoS class. 130: This waiting room is unable to offer weighted sharing for a connection. 131: Scheduler Identifier still in use. 132: QoS Class Identifier still in use. 133: Invalid QoS parameter. 134: Insufficient QoS resources. 135: Any point-to-multipoint connection arriving on this input port must use the same QoS parameters for all output branches.
在使用它的任何消息的描述中定义。）17:无法使用不同的标签标记点对多点树的每个输出分支。18:一个或多个指定的输入VPI无效。19:一个或多个指定的输入VCI无效。20:一个或多个指定的输出VPI无效。21:一个或多个指定的输出VCI无效。22:连接管理消息中的服务类别字段无效。23:用于QoS配置文件的资源不足。24:此输入端口上不支持虚拟路径交换。25:请求的输入端口或请求的输出端口均不支持点对多点虚拟路径连接。26:尝试将虚拟路径连接分支添加到现有虚拟通道连接。27:尝试将虚拟通道连接分支添加到现有虚拟路径连接。28：只能建立点对点双向连接。29:无法支持请求的VPI范围。30:无法在所有请求的VPI上支持请求的VCI范围。31:无法更改此输出端口的传输单元速率。32:请求的传输单元速率超出此输出端口的范围。128:此等候室内的加权调度不可用。129:此等候室无法为QoS类提供加权共享。130:此等候室无法为连接提供加权共享。131:计划程序标识符仍在使用中。132:QoS类标识符仍在使用中。133:无效的QoS参数。134：QoS资源不足。135:到达此输入端口的任何点对多点连接必须对所有输出分支使用相同的QoS参数。
The following table gives a summary of the messages defined in this version of the specification. It also indicates which messages must be supported in a minimal implementation of the protocol. Those messages marked as "Required" must be supported by the switch for an implementation to be considered to conform to this specification. (While the controller should also implement those messages marked
下表总结了本规范版本中定义的消息。它还指示在协议的最小实现中必须支持哪些消息。交换机必须支持标记为“必需”的消息，才能将实现视为符合本规范。（同时，控制器还应实现标记为
"Required," conformance cannot be tested for the controller due to the Master-Slave nature of the protocol.)
“必需”，由于协议的主从性质，无法测试控制器的一致性。）
Message Name Message Type Status
消息名称消息类型状态
Connection Management Messages
Add Branch VCC....................16 Required
VPC....................26
Delete Tree.......................18
Delete All........................20
Delete Branches...................17 Required
Move Branch VCC...................22
VPC...................27
Connection Management Messages
Add Branch VCC....................16 Required
VPC....................26
Delete Tree.......................18
Delete All........................20
Delete Branches...................17 Required
Move Branch VCC...................22
VPC...................27
Port Management Messages
Port Management...................32 Required
Label Range.......................33
Port Management Messages
Port Management...................32 Required
Label Range.......................33
State and Statistics Messages
Connection Activity...............48
Port Statistics...................49 Required
Connection Statistics.............50
QoS Class Statistics..............51
Report Connection State...........52
State and Statistics Messages
Connection Activity...............48
Port Statistics...................49 Required
Connection Statistics.............50
QoS Class Statistics..............51
Report Connection State...........52
Configuration Messages
Switch Configuration..............64 Required
Port Configuration................65 Required
All Ports Configuration...........66 Required
Configuration Messages
Switch Configuration..............64 Required
Port Configuration................65 Required
All Ports Configuration...........66 Required
Event Messages
Port Up...........................80
Port Down.........................81
Invalid VPI/VCI...................82
New Port..........................83
Dead Port.........................84
Event Messages
Port Up...........................80
Port Down.........................81
Invalid VPI/VCI...................82
New Port..........................83
Dead Port.........................84
Quality of Service Messages
QoS Configuration.................96
Scheduler Establishment...........97
QoS Class Establishment...........98
QoS Release.......................99
QoS Connection Management VCC....100
VPC....101
Quality of Service Messages
QoS Configuration.................96
Scheduler Establishment...........97
QoS Class Establishment...........98
QoS Release.......................99
QoS Connection Management VCC....100
VPC....101
Adjacency Protocol....................10 Required
Adjacency Protocol....................10 Required
REFERENCES
参考资料
[af-tm-0056] ATM Forum Traffic Management Specification 4.0, af-tm-0056.000, April 1996.
[af-tm-0056]ATM论坛流量管理规范4.0，af-tm-0056.000，1996年4月。
[I.361] "B-ISDN ATM Layer Specification," International Telecommunication Union, ITU-T Recommendation I.361, Mar. 1993.
[I.361]“B-ISDN ATM层规范”，国际电信联盟，ITU-T建议I.361，1993年3月。
[I.363] "B-ISDN ATM Adaptation Layer (AAL) Specification," International Telecommunication Union, ITU-T Recommendation I.363, Mar. 1993.
[I.363]“B-ISDN ATM适配层（AAL）规范”，国际电信联盟，ITU-T建议I.363，1993年3月。
[IpsilonMIB] Ipsilon IP Switch MIB,
http://www.ipsilon.com/products/ips.mib
[IpsilonMIB] Ipsilon IP Switch MIB,
http://www.ipsilon.com/products/ips.mib
[Partridge] C. Partridge, "Gigabit Networking," Addison-Wesley, 1994.
[Partridge]C.Partridge，“千兆网络”，Addison Wesley，1994年。
[RFC1700] Reynolds, J., and J. Postel, "Assigned Numbers," STD 2, RFC 1700, October 1994.
[RFC1700]Reynolds，J.和J.Postel，“分配的数字”，标准2，RFC 1700，1994年10月。
[RFC1987] Newman, P, Edwards, W., hinden, R., Hoffman, E. Ching Liaw, F., Lyon, T. and G. Minshall, "Ipsilon's General Switch Management Protocol Specification," Version 1.1, RFC 1987, August 1996.
[RFC1987]Newman，P，Edwards，W.，hinden，R.，Hoffman，E.Ching Liaw，F.，Lyon，T.和G.Minshall，“Ipsilon的通用交换机管理协议规范”，版本1.1，RFC 1987，1996年8月。
SECURITY CONSIDERATIONS
安全考虑
Physical security on the control link connecting the controller to the switch is assumed. Security issues are not discussed in this document.
假设控制器与交换机连接的控制链路上存在物理安全性。本文档中未讨论安全问题。
AUTHORS' ADDRESSES
作者地址
Peter Newman Phone: +1 (408) 990 2003
Nokia EMail: pn@ipsilon.com
Peter Newman Phone: +1 (408) 990 2003
Nokia EMail: pn@ipsilon.com
W. L. Edwards, Chief Scientist Phone: +1 (913) 534 5334
Sprint EMail: texas@sprintcorp.com
W. L. Edwards, Chief Scientist Phone: +1 (913) 534 5334
Sprint EMail: texas@sprintcorp.com
Robert M. Hinden Phone: +1 (408) 990 2004
Nokia EMail: hinden@ipsilon.com
Robert M. Hinden Phone: +1 (408) 990 2004
Nokia EMail: hinden@ipsilon.com
Eric Hoffman Phone: +1 (408) 990 2010
Nokia EMail: hoffman@ipsilon.com
Eric Hoffman Phone: +1 (408) 990 2010
Nokia EMail: hoffman@ipsilon.com
Fong Ching Liaw Phone: +1 (408) 873 2688
Coppercom EMail: fong@coppercom.com
Fong Ching Liaw Phone: +1 (408) 873 2688
Coppercom EMail: fong@coppercom.com
Tom Lyon Phone: +1 (408) 990 2001
Nokia EMail: pugs@ipsilon.com
Tom Lyon Phone: +1 (408) 990 2001
Nokia EMail: pugs@ipsilon.com
Greg Minshall Phone: +1 (650) 237 3164
Fiberlane Communications EMail: minshall@fiberlane.com
Greg Minshall Phone: +1 (650) 237 3164
Fiberlane Communications EMail: minshall@fiberlane.com
Nokia (Sunnyvale) is located at:
诺基亚（Sunnyvale）位于：
232 Java Drive Sunnyvale, CA 94089 USA
美国加利福尼亚州桑尼维尔Java Drive 232号，邮编94089
Sprint is located at:
Sprint位于：
Sprint Sprint Technology Services - Long Distance Division 9300 Metcalf Avenue Mailstop KSOPKB0802 Overland Park, KS 66212-6333 USA
Sprint Sprint技术服务-美国堪萨斯州梅特卡夫大道9300号邮站KSOPKB0802陆上公园长途分部，邮编66212-6333
Fiberlane Communications is located at:
Fiberlane Communications位于：
1399 Charleston Road Mountain View, CA 94043 USA
美国加利福尼亚州查尔斯顿路山景城1399号，邮编94043
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (1998). All Rights Reserved.
版权所有（C）互联网协会（1998年）。版权所有。
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
本文件及其译本可复制并提供给他人，对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发，不受任何限制，前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是，不得以任何方式修改本文件本身，例如删除版权通知或对互联网协会或其他互联网组织的引用，除非出于制定互联网标准的需要，在这种情况下，必须遵循互联网标准过程中定义的版权程序，或根据需要将其翻译成英语以外的其他语言。
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。