Network Working Group A. Doria
Request for Comments: 3292 Lulea University of Technology
Category: Standards Track F. Hellstrand
K. Sundell
Nortel Networks
T. Worster
June 2002
Network Working Group A. Doria
Request for Comments: 3292 Lulea University of Technology
Category: Standards Track F. Hellstrand
K. Sundell
Nortel Networks
T. Worster
June 2002
General Switch Management Protocol (GSMP) V3
通用交换机管理协议（GSMP）V3
Status of this Memo
本备忘录的状况
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2002). All Rights Reserved.
版权所有（C）互联网协会（2002年）。版权所有。
Abstract
摘要
This document describes the General Switch Management Protocol Version 3 (GSMPv3). The GSMPv3 is an asymmetric protocol that allows one or more external switch controllers to establish and maintain the state of a label switch such as, an ATM, frame relay or MPLS switch. The GSMPv3 allows control of both unicast and multicast switch connection state as well as control of switch system resources and QoS features.
本文档介绍通用交换机管理协议版本3（GSMPv3）。GSMPv3是一种非对称协议，允许一个或多个外部交换机控制器建立和维护标签交换机（如ATM、帧中继或MPLS交换机）的状态。GSMPv3允许控制单播和多播交换机连接状态，以及控制交换机系统资源和QoS功能。
Acknowledgement
确认
GSMP was created by P. Newman, W. Edwards, R. Hinden, E. Hoffman, F. Ching Liaw, T. Lyon, and G. Minshall (see [6] and [7]). This version of GSMP is based on their work.
GSMP由P.Newman、W.Edwards、R.Hinden、E.Hoffman、F.Ching Liaw、T.Lyon和G.Minshall创建（见[6]和[7]）。这个版本的GSMP基于他们的工作。
Contributors
贡献者
In addition to the authors/editors listed in the heading, many members of the GSMP group have made significant contributions to this specification. Among the contributors who have contributed materially are: Constantin Adam, Clint Bishard, Joachim Buerkle, Torbjorn Hedqvist, Georg Kullgren, Aurel A. Lazar, Mahesan Nandikesan, Matt Peters, Hans Sjostrand, Balaji Srinivasan, Jaroslaw Sydir, Chao-Chun Wang.
除了标题中列出的作者/编辑外，GSMP小组的许多成员对本规范做出了重大贡献。有重大贡献的贡献者包括：康斯坦丁·亚当、克林特·比沙德、约阿希姆·布尔克尔、托尔比约恩·赫德奎斯特、格奥尔格·库尔格伦、奥雷尔·拉扎尔、马赫桑·南迪凯桑、马特·彼得斯、汉斯·绍斯特兰、巴拉吉·斯里尼瓦桑、雅罗斯劳·西迪尔、王朝春。
Specification of Requirements
需求说明
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC2119]中所述进行解释。
Table of Contents
目录
1. Introduction ................................................... 4
2. GSMP Packet Encapsulation ...................................... 6
3. Common Definitions and Procedures .............................. 6
3.1 GSMP Packet Format ........................................... 7
3.1.1 Basic GSMP Message format ................................ 7
3.1.2 Fields commonly found in GSMP messages .................. 11
3.1.3 Labels .................................................. 12
3.1.4 Failure Response Messages ............................... 17
4. Connection Management Messages ................................ 18
4.1 General Message Definitions ................................. 18
4.2 Add Branch Message .......................................... 25
4.2.1 ATM specific procedures: ................................ 29
4.3 Delete Tree Message ......................................... 30
4.4 Verify Tree Message ......................................... 30
4.5 Delete All Input Port Message ............................... 30
4.6 Delete All Output Port Message .............................. 31
4.7 Delete Branches Message ..................................... 32
4.8 Move Output Branch Message .................................. 35
4.8.1 ATM Specific Procedures: ................................ 37
4.9 Move Input Branch Message ................................... 38
4.9.1 ATM Specific Procedures: ................................ 41
5. Reservation Management Messages ............................... 42
5.1 Reservation Request Message ................................. 43
5.2 Delete Reservation Message .................................. 46
5.3 Delete All Reservations Message.............................. 47
6. Management Messages ........................................... 47
6.1 Port Management Message ..................................... 47
6.2 Label Range Message ......................................... 53
6.2.1 Labels .................................................. 56
7. State and Statistics Messages ................................. 60
7.1 Connection Activity Message ................................. 61
7.2 Statistics Messages ......................................... 64
7.2.1 Port Statistics Message ................................. 67
7.2.2 Connection Statistics Message ........................... 67
7.2.3 QoS Class Statistics Message ............................ 68
7.3 Report Connection State Message ............................. 68
8. Configuration Messages ........................................ 73
8.1 Switch Configuration Message ................................ 73
8.1.1 Configuration Message Processing ........................ 75
8.2 Port Configuration Message .................................. 75
1. Introduction ................................................... 4
2. GSMP Packet Encapsulation ...................................... 6
3. Common Definitions and Procedures .............................. 6
3.1 GSMP Packet Format ........................................... 7
3.1.1 Basic GSMP Message format ................................ 7
3.1.2 Fields commonly found in GSMP messages .................. 11
3.1.3 Labels .................................................. 12
3.1.4 Failure Response Messages ............................... 17
4. Connection Management Messages ................................ 18
4.1 General Message Definitions ................................. 18
4.2 Add Branch Message .......................................... 25
4.2.1 ATM specific procedures: ................................ 29
4.3 Delete Tree Message ......................................... 30
4.4 Verify Tree Message ......................................... 30
4.5 Delete All Input Port Message ............................... 30
4.6 Delete All Output Port Message .............................. 31
4.7 Delete Branches Message ..................................... 32
4.8 Move Output Branch Message .................................. 35
4.8.1 ATM Specific Procedures: ................................ 37
4.9 Move Input Branch Message ................................... 38
4.9.1 ATM Specific Procedures: ................................ 41
5. Reservation Management Messages ............................... 42
5.1 Reservation Request Message ................................. 43
5.2 Delete Reservation Message .................................. 46
5.3 Delete All Reservations Message.............................. 47
6. Management Messages ........................................... 47
6.1 Port Management Message ..................................... 47
6.2 Label Range Message ......................................... 53
6.2.1 Labels .................................................. 56
7. State and Statistics Messages ................................. 60
7.1 Connection Activity Message ................................. 61
7.2 Statistics Messages ......................................... 64
7.2.1 Port Statistics Message ................................. 67
7.2.2 Connection Statistics Message ........................... 67
7.2.3 QoS Class Statistics Message ............................ 68
7.3 Report Connection State Message ............................. 68
8. Configuration Messages ........................................ 73
8.1 Switch Configuration Message ................................ 73
8.1.1 Configuration Message Processing ........................ 75
8.2 Port Configuration Message .................................. 75
8.2.1 PortType Specific Data .................................. 79
8.3 All Ports Configuration Message ............................. 87
8.4 Service Configuration Message ............................... 89
9. Event Messages ................................................ 93
9.1 Port Up Message ............................................ 95
9.2 Port Down Message .......................................... 95
9.3 Invalid Label Message ...................................... 95
9.4 New Port Message ........................................... 96
9.5 Dead Port Message .......................................... 96
9.6 Adjacency Update Message ................................... 96
10. Service Model Definition .................................... 96
10.1 Overview .................................................. 96
10.2 Service Model Definitions ................................. 97
10.2.1 Original Specifications ............................... 97
10.2.2 Service Definitions ................................... 98
10.2.3 Capability Sets ....................................... 99
10.3 Service Model Procedures .................................. 99
10.4 Service Definitions ....................................... 100
10.4.1 ATM Forum Service Categories .......................... 101
10.4.2 Integrated Services ................................... 104
10.4.3 MPLS CR-LDP ........................................... 105
10.4.4 Frame Relay ........................................... 105
10.4.5 DiffServ .............................................. 106
10.5 Format and Encoding of the Traffic Parameters ............. 106
10.5.1 Traffic Parameters for ATM Forum Services ............. 106
10.5.2 Traffic Parameters for Int-Serv Controlled Load Service 107
10.5.3 Traffic Parameters for CRLDP Service .................. 108
10.5.4 Traffic Parameters for Frame Relay Service ............ 109
10.6 Traffic Controls (TC) Flags ............................... 110
11. Adjacency Protocol .......................................... 111
11.1 Packet Format ............................................. 112
11.2 Procedure ................................................. 115
11.2.1 State Tables .......................................... 117
11.3 Partition Information State ............................... 118
11.4 Loss of Synchronisation.................................... 119
11.5 Multiple Controllers Per Switch Partition ................. 119
11.5.1 Multiple Controller Adjacency Process ................. 120
12. Failure Response Codes ...................................... 121
12.1 Description of Failure and Warning Response Messages ...... 121
12.2 Summary of Failure Response Codes and Warnings ............ 127
13. Security Considerations ..................................... 128
Appendix A Summary of Messages ................................. 129
Appendix B IANA Considerations ................................. 130
References ...................................................... 134
Authors' Addresses .............................................. 136
Full Copyright Statement ........................................ 137
8.2.1 PortType Specific Data .................................. 79
8.3 All Ports Configuration Message ............................. 87
8.4 Service Configuration Message ............................... 89
9. Event Messages ................................................ 93
9.1 Port Up Message ............................................ 95
9.2 Port Down Message .......................................... 95
9.3 Invalid Label Message ...................................... 95
9.4 New Port Message ........................................... 96
9.5 Dead Port Message .......................................... 96
9.6 Adjacency Update Message ................................... 96
10. Service Model Definition .................................... 96
10.1 Overview .................................................. 96
10.2 Service Model Definitions ................................. 97
10.2.1 Original Specifications ............................... 97
10.2.2 Service Definitions ................................... 98
10.2.3 Capability Sets ....................................... 99
10.3 Service Model Procedures .................................. 99
10.4 Service Definitions ....................................... 100
10.4.1 ATM Forum Service Categories .......................... 101
10.4.2 Integrated Services ................................... 104
10.4.3 MPLS CR-LDP ........................................... 105
10.4.4 Frame Relay ........................................... 105
10.4.5 DiffServ .............................................. 106
10.5 Format and Encoding of the Traffic Parameters ............. 106
10.5.1 Traffic Parameters for ATM Forum Services ............. 106
10.5.2 Traffic Parameters for Int-Serv Controlled Load Service 107
10.5.3 Traffic Parameters for CRLDP Service .................. 108
10.5.4 Traffic Parameters for Frame Relay Service ............ 109
10.6 Traffic Controls (TC) Flags ............................... 110
11. Adjacency Protocol .......................................... 111
11.1 Packet Format ............................................. 112
11.2 Procedure ................................................. 115
11.2.1 State Tables .......................................... 117
11.3 Partition Information State ............................... 118
11.4 Loss of Synchronisation.................................... 119
11.5 Multiple Controllers Per Switch Partition ................. 119
11.5.1 Multiple Controller Adjacency Process ................. 120
12. Failure Response Codes ...................................... 121
12.1 Description of Failure and Warning Response Messages ...... 121
12.2 Summary of Failure Response Codes and Warnings ............ 127
13. Security Considerations ..................................... 128
Appendix A Summary of Messages ................................. 129
Appendix B IANA Considerations ................................. 130
References ...................................................... 134
Authors' Addresses .............................................. 136
Full Copyright Statement ........................................ 137
The General Switch Management Protocol (GSMP) is a general purpose protocol to control a label 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, request and delete reservation of switch resources, and request statistics. It also allows the switch to inform the controller of asynchronous events such as a link going down. 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. Also a switch may be controlled by more than one controller by using the technique of partitioning.
通用交换机管理协议（GSMP）是控制标签交换机的通用协议。GSMP允许控制器跨交换机建立和释放连接，在多播连接上添加和删除叶子，管理交换机端口，请求配置信息，请求和删除交换机资源保留，以及请求统计信息。它还允许交换机通知控制器异步事件，例如链路断开。GSMP协议是非对称的，控制器是主设备，交换机是从设备。多个交换机可以由单个控制器通过单独的控制连接使用协议的多个实例化来控制。此外，通过使用分区技术，交换机可以由多个控制器控制。
A "physical" switch can be partitioned into several virtual switches that are referred to as partitions. In this version of GSMP, switch partitioning is static and occurs prior to running GSMP. The partitions of a physical switch are isolated from each other by the implementation and the controller assumes that the resources allocated to a partition are at all times available to that partition. A partition appears to its controller as a label switch. Throughout the rest of this document, the term switch (or equivalently, label switch) is used to refer to either a physical, non-partitioned switch or to a partition. The resources allocated to a partition appear to the controller as if they were the actual physical resources of the partition. For example if the bandwidth of a port were divided among several partitions, each partition would appear to the controller to have its own independent port.
一个“物理”交换机可以划分为多个虚拟交换机，这些虚拟交换机称为分区。在这个版本的GSMP中，交换机分区是静态的，发生在运行GSMP之前。物理交换机的分区通过实现相互隔离，控制器假设分配给分区的资源在任何时候都可用于该分区。分区在其控制器上显示为标签开关。在本文档的其余部分中，术语switch（或相当于label switch）用于指物理的、非分区的交换机或分区。分配给分区的资源在控制器看来就像是分区的实际物理资源一样。例如，如果一个端口的带宽被划分到几个分区中，那么控制器会认为每个分区都有自己的独立端口。
GSMP controls a partitioned switch through the use of a partition identifier that is carried in every GSMP message. Each partition has a one-to-one control relationship with its own logical controller entity (which in the remainder of the document is referred to simply as a controller) and GSMP independently maintains adjacency between each controller-partition pair.
GSMP通过使用每个GSMP消息中携带的分区标识符来控制分区交换机。每个分区与其自己的逻辑控制器实体（在本文档的其余部分中简称为控制器）具有一对一的控制关系，并且GSMP独立地维护每个控制器分区对之间的邻接关系。
Kinds of label switches include frame or cell switches that support connection oriented switching, using the exact match-forwarding algorithm based on labels attached to incoming cells or frames. 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. Cells or labelled frames arrive at the switch from an external communication link on
各种标签交换机包括支持面向连接的交换的帧或单元交换机，使用基于附加到传入单元或帧的标签的精确匹配转发算法。假定交换机包含多个“端口”。每个端口是一个“输入端口”和一个“输出端口”的组合。一些GSMP请求将端口作为一个整体引用，而其他请求特定于输入端口或输出端口。单元或带标签的帧从上的外部通信链路到达交换机
incoming labelled channels at an input port. Cells or labelled frames depart from the switch to an external communication link on labelled channels from an output port.
输入端口处的输入标记通道。单元或带标签的帧从交换机从输出端口到带标签通道上的外部通信链路。
A switch may support multiple label types, however, each switch port can support only one label type. The label type supported by a given port is indicated by the switch to the controller in a port configuration message. Connections may be established between ports, supporting different label types. Label types include ATM, Frame Relay, MPLS Generic and FEC Labels.
交换机可以支持多种标签类型，但是，每个交换机端口只能支持一种标签类型。给定端口支持的标签类型由端口配置消息中控制器的交换机指示。可以在端口之间建立连接，支持不同的标签类型。标签类型包括ATM、帧中继、MPLS通用和FEC标签。
A connection across a switch is formed by connecting an incoming labelled channel to one or more outgoing labelled channels. Connections are referenced by the input port on which they originate and the Label values of their incoming labelled channel.
通过将输入带标签通道连接到一个或多个输出带标签通道，形成交换机上的连接。连接由它们发起的输入端口及其传入的带标签通道的标签值引用。
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 connection is established with a certain quality of service (QoS). This version of GSMP includes a default QoS Configuration and additionally allows the negotiation of alternative, optional QoS configurations. The default QoS Configuration includes three QoS Models: a Service Model, a Simple Abstract Model (strict priorities) and a QoS Profile Model.
通常，连接是以一定的服务质量（QoS）建立的。这个版本的GSMP包括一个默认的QoS配置，另外还允许协商可选的QoS配置。默认的QoS配置包括三个QoS模型：服务模型、简单抽象模型（严格优先级）和QoS配置文件模型。
The Service Model is based on service definitions found external to GSMP such as in Integrated Services or ATM Service Categories. Each connection is assigned a specific service that defines the handling of the connection by the switch. Additionally, traffic parameters and traffic controls may be assigned to the connection depending on the assigned service.
服务模型基于GSMP外部的服务定义，例如在集成服务或ATM服务类别中。每个连接都分配了一个特定的服务，该服务定义了交换机对连接的处理。此外，根据分配的服务，可以向连接分配流量参数和流量控制。
In the Simple Abstract Model, a connection is assigned a priority when it is established. It may be assumed that for connections that share the same output port, a cell or frame on a connection with a higher priority is much more likely to exit the switch before a cell or frame 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.
在简单抽象模型中，连接在建立时被分配优先级。可以假设，对于共享相同输出端口的连接，如果具有较高优先级的连接上的小区或帧同时位于交换机中，则在具有较低优先级的连接上的小区或帧之前，具有较高优先级的连接上的小区或帧更有可能退出交换机。交换机的每个端口支持的优先级数量可以从端口配置消息中获得。
The QoS Profile Model provides a simple mechanism that allows connection to be assigned QoS semantics defined externally to GSMP. The QoS Profile Model can be used to indicate pre-defined Differentiated Service Per Hop Behaviours (PHBs). Definition of QoS profiles is outside of the scope of this specification.
QoS配置文件模型提供了一种简单的机制，允许将外部定义的QoS语义分配给GSMP。QoS配置文件模型可用于指示预定义的每跳区分服务行为（PHB）。QoS配置文件的定义不在本规范的范围内。
All GSMP switches MUST support the default QoS Configuration. A GSMP switch may additionally support one or more alternative QoS Configurations. The QoS models of alternative QoS configurations are defined outside the GSMP specification. GSMP includes a negotiation mechanism that allows a controller to select from the QoS configurations that a switch supports.
所有GSMP交换机必须支持默认的QoS配置。GSMP交换机还可以支持一个或多个备选QoS配置。替代QoS配置的QoS模型在GSMP规范之外定义。GSMP包括一种协商机制，允许控制器从交换机支持的QoS配置中进行选择。
GSMP contains an adjacency protocol. The adjacency protocol is used to synchronise states 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 may be transported via any suitable medium. GSMP packet encapsulations for ATM, Ethernet and TCP are specified in [15]. Additional encapsulations for GSMP packets may be defined in separate documents.
GSMP包可以通过任何合适的介质进行传输。[15]中规定了ATM、以太网和TCP的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 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 six classes of GSMP request-response message: Connection Management, Reservation 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. The controller can be required to acknowledge event messages, but by default does not do so. There is also an adjacency protocol message used to establish synchronisation across the link and maintain a handshake.
GSMP是一种主从协议。控制器向交换机发出请求消息。每个请求消息指示是否需要来自交换机的响应，并包含事务标识符，以使响应与请求关联。交换机会回复一条响应消息，指示结果成功或失败。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.
对于请求-响应消息，每种消息类型都有请求消息格式和成功响应格式。除非另有规定，否则故障响应消息与导致故障的请求消息相同，代码字段指示故障的性质。
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 opaque sub-fields 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 states synchronised.
每个交换机端口还维护交换机分配的端口会话号。必须拒绝端口会话号不正确的消息。这允许控制器检测链路故障并保持状态同步。
Except for the adjacency protocol message, no GSMP messages may be sent across the link until the adjacency protocol has achieved synchronisation, and all GSMP messages received on a link that do not currently have state synchronisation 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Message Body ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
(The convention in the documentation of Internet Protocols [5] is to express numbers in decimal. Numbers in hexadecimal format are specified by prefacing them with the characters "0x". Numbers in binary format are specified by prefacing them with the characters "0b". Data is pictured in "big-endian" order. That is, fields are described left to right, with the most significant byte on the left and the least significant byte on the right. Whenever a diagram shows a group of bytes, the order of transmission of those bytes is the normal order in which they are read in English. Whenever a byte represents a numeric quantity, the left most bit in the diagram is the high order or most significant bit. That is, the bit labelled 0 is the most significant bit. Similarly, whenever a multi-byte field represents a numeric quantity, the left most bit of the whole field is the most significant bit. When a multi-byte quantity is transmitted, the most significant byte is transmitted first. This is the same coding convention as is used in the ATM layer [1] and AAL-5 [2][3].)
（互联网协议文献[5]中的惯例是用十进制表示数字。十六进制格式的数字是通过在前面加上字符“0x”来指定的。二进制格式的数字是通过在前面加上字符“0b”来指定的。数据以“big-endian”表示。）顺序。也就是说，字段是从左到右描述的，最高有效字节在左边，最低有效字节在右边。每当图表显示一组字节时，这些字节的传输顺序是用英语读取的正常顺序。每当一个字节代表一个数字量时，t中最左边的位图表是高阶或最高有效位。也就是说，标记为0的位是最高有效位。类似地，每当一个多字节字段表示一个数字量时，整个字段最左边的位就是最高有效位。当传输一个多字节量时，最高有效字节首先被传输。这是与ATM层[1]和AAL-5[2][3]中使用的编码约定相同。）
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 the following classes: Connection Management, Reservation Management, Port Management, State and Statistics, Configuration, Quality of Service, Events and messages belonging to an Abstract or Resource Model (ARM) extension. Each class has a number of different message types. In addition, one Message Type is allocated to the adjacency protocol.
消息类型GSMP消息类型。GSMP消息分为以下几类：连接管理、保留管理、端口管理、状态和统计、配置、服务质量、属于抽象或资源模型（ARM）扩展的事件和消息。每个类都有许多不同的消息类型。此外，一种消息类型被分配给邻接协议。
Result Field in a Connection Management request message, a Port Management request message, or a Quality of Service request message that 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 State 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 was set to "AckAll". (This facility was added to reduce the control traffic in the case where the
连接管理请求消息、端口管理请求消息或服务质量请求消息中的结果字段，用于指示如果结果成功，是否需要响应请求消息。值“NoSuccessAck”表示如果结果成功，请求消息不期望响应，“AckAll”表示如果结果成功，则期望响应。在这两种情况下，如果请求失败，则必须生成失败响应。对于状态和统计信息以及配置请求消息，请求消息中的“NoSuccessAck”值将被忽略，请求消息的处理方式与字段设置为“AckAll”的方式相同。（增加该设施是为了在以下情况下减少控制流量：
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".)
控制器定期检查开关中的状态是否正确。如果控制器不使用此功能，则所有请求消息都应以“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. 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”结果表示可能包含在单个消息中的成功响应，或跨多个消息的成功响应的最终消息。
"More" in the result indicates that the message, either request or 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.
结果中的“更多”表示消息（请求或响应）超过了数据链路的最大传输单位，并且将发送一条或多条进一步的消息以完成成功响应。
ReturnReceipt is a result field used in Events to indicate that an acknowledgement is required for the message. The default for Events Messages is that the controller will not acknowledge Events. In the case where a switch requires acknowledgement, it will set the Result Field to ReturnReceipt in the header of the Event Message.
ReturnReceive是事件中使用的结果字段，用于指示消息需要确认。事件消息的默认值是控制器不会确认事件。在开关需要确认的情况下，它将在事件消息头中将结果字段设置为ReturnReceive。
The encoding of the result field is:
结果字段的编码为：
NoSuccessAck: Result = 1
AckAll: Result = 2
Success: Result = 3
Failure: Result = 4
More: Result = 5
ReturnReceipt Result = 6
NoSuccessAck: Result = 1
AckAll: Result = 2
Success: Result = 3
Failure: Result = 4
More: Result = 5
ReturnReceipt Result = 6
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.
代码字段提供有关响应消息中结果的更多信息。它主要用于在故障响应中传递错误代码，但也可用于在成功响应消息或事件消息中提供更多信息。在请求消息中，不使用代码字段，并将其设置为零。在邻接协议消息中，代码字段用于确定消息的功能。
Partition ID Field used to associate the command with a specific switch partition. The format of the Partition ID is not defined in GSMP. If desired, the Partition ID can be divided into multiple sub-identifiers within a single partition. For example: the Partition ID could be subdivided into a 6-bit partition number and a 2-bit sub-identifier which would allow a switch to support 64 partitions with 4 available IDs per partition.
用于将命令与特定交换机分区关联的分区ID字段。GSMP中未定义分区ID的格式。如果需要，分区ID可以在单个分区内划分为多个子标识符。例如：分区ID可以细分为6位分区号和2位子标识符，这将允许交换机支持64个分区，每个分区有4个可用ID。
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.
用于将请求消息与其响应消息关联的事务标识符。对于请求消息，控制器可以选择任何事务标识符。对于响应消息，事务标识符设置为作为响应的消息的事务标识符的值。对于事件消息，事务标识符应设置为零。邻接协议中未使用事务标识符，且字段不存在。
I flag If I is set then the SubMessage Number field indicates the total number of SubMessage segments that compose the entire message. If it is not set then the SubMessage Number field indicates the sequence number of this SubMessage segment within the whole message.
I标志如果设置了I，则子消息编号字段指示组成整个消息的子消息段的总数。如果未设置，则子消息编号字段指示整个消息中此子消息段的序列号。
SubMessage Number When a message is segmented because it exceeds the MTU of the link layer, each segment will include a submessage number to indicate its position. Alternatively, if it is the first submessage in a sequence of submessages, the I flag will be set and this field will contain the total count of submessage segments.
子消息编号当消息因超出链接层的MTU而被分段时，每个分段将包含一个子消息编号以指示其位置。或者，如果它是子消息序列中的第一个子消息，则将设置I标志，并且此字段将包含子消息段的总计数。
Length Length of the GSMP message including its header fields and defined GSMP message body. The length of additional data appended to the end of the standard message SHOULD be included in the Length field.
GSMP消息的长度，包括其头字段和定义的GSMP消息正文。附加到标准消息末尾的附加数据的长度应包含在长度字段中。
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, "5: 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.
如果请求消息中的端口会话号与指定端口的当前端口会话号不匹配，则必须返回故障响应消息，代码字段指示“5:无效端口会话号”。可以使用端口配置或所有端口配置消息获取端口的当前端口会话号。
1. 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.
1. GSMP消息中未使用或定义为“保留”的任何字段必须由发送方设置为零，并由接收方忽略。
2. Flags that are undefined will be designated as: x: reserved
2. 未定义的标志将被指定为：x:reserved
3. It is not an error for a GSMP message to contain additional data after the end of the Message Body. This is allowed to support proprietary and experimental purposes. However, the maximum transmission unit of the GSMP message, as defined by the data link layer encapsulation, MUST NOT be exceeded. The length of additional data appended to the end of the standard message SHOULD be included in the message length field.
3. GSMP消息在消息正文结束后包含附加数据不是错误。这允许支持专有和实验目的。但是，不得超过数据链路层封装定义的GSMP消息的最大传输单位。附加到标准消息末尾的附加数据的长度应包含在消息长度字段中。
4. A success response message MUST NOT be sent until the requested operation has been successfully completed.
4. 在请求的操作成功完成之前，不得发送成功响应消息。
All labels in GSMP have a common structure composed of tuples, consisting of a Type, a Length, and a Value. Such tuples are commonly known as TLV's, and are a good way of encoding information in a flexible and extensible format. A label TLV is encoded as a 2 octet field that uses 12 bits to specify a Type and four bits to specify certain behaviour specified below, followed by a 2 octet Length field, followed by a variable length Value field. Additionally, a label field can be composed of many stacked labels that together constitute the label.
GSMP中的所有标签都有一个由元组组成的公共结构，元组由类型、长度和值组成。这种元组通常被称为TLV，是一种以灵活和可扩展的格式编码信息的好方法。标签TLV编码为2个八位字段，使用12位指定类型，4位指定以下指定的特定行为，后跟2个八位长度字段，后跟可变长度值字段。此外，标签字段可以由许多堆叠的标签组成，这些标签一起构成标签。
A summary of TLV labels supported in this version of the protocol is listed below:
此版本协议支持的TLV标签摘要如下所示：
TLV Label Type Section Title
--------- ---- -------------
ATM Label 0x100 ATM TLV Labels
FR Label 0x101 Frame Relay TLV Labels
MPLS Gen Label 0x102 MPLS Generic TLV Labels
FEC Label 0x103 FEC TLV Labels
TLV Label Type Section Title
--------- ---- -------------
ATM Label 0x100 ATM TLV Labels
FR Label 0x101 Frame Relay TLV Labels
MPLS Gen Label 0x102 MPLS Generic TLV Labels
FEC Label 0x103 FEC TLV Labels
All Labels will be designated as follow:
所有标签将指定如下：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| Label Type | Label Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Label Value ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| Label Type | Label Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Label Value ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
x: Reserved Flags. These are generally used by specific messages and will be defined in those messages.
x：保留标志。这些通常由特定消息使用，并将在这些消息中定义。
S: Stacked Label Indicator Label Stacking is discussed below in section 3.1.3.5
S：堆叠标签指示器标签堆叠在下面第3.1.3.5节中讨论
Label Type A 12-bit field indicating the type of label.
标签类型指示标签类型的12位字段。
Label Length A 16-bit field indicating the length of the Label Value field in bytes.
标签长度16位字段，表示标签值字段的长度（字节）。
Label Value A variable length field that is an integer number of 32 bit words long. The Label Value field is interpreted according to the Label Type as described in the following sections.
标签值可变长度字段，长度为32位字的整数。标签值字段根据标签类型进行解释，如下节所述。
If the Label Type = ATM Label, the labels MUST be interpreted as an ATM labels as shown:
如果标签类型=ATM标签，则标签必须解释为ATM标签，如图所示：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| ATM Label (0x100) | Label Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x x x x| 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| ATM Label (0x100) | Label Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x x x x| VPI | VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 VCI field is not used.
对于虚拟路径连接（切换为单个虚拟路径连接）或虚拟路径（切换为虚拟路径内的一个或多个虚拟通道连接），不使用VCI字段。
ATM distinguishes between virtual path connections and virtual channel connections. 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).
ATM区分虚拟路径连接和虚拟通道连接。连接管理消息同时应用于虚拟通道连接和虚拟路径连接。添加分支和移动分支连接管理消息有两种消息类型。一种消息类型表示需要虚拟通道连接，另一种消息类型表示需要虚拟路径连接。“删除分支”、“删除树”和“删除所有连接管理”消息只有一种消息类型，因为它们不需要区分虚拟通道连接和虚拟路径连接。对于虚拟路径连接，既不需要输入VCI字段，也不需要输出VCI字段。发送方应将它们设置为零，接收方应忽略它们。虚拟通道分支不能添加到现有虚拟路径连接。相反，虚拟路径分支可能不会添加到现有的虚拟通道连接。在端口配置消息中，每个交换机输入端口可以声明其是否能够支持虚拟路径交换（即，接受请求虚拟路径连接的连接管理消息）。
If the TLV Type = FR Label, the labels MUST be interpreted as a Frame Relay labels as shown:
如果TLV类型=FR标签，则标签必须解释为帧中继标签，如图所示：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| FR Label (0x101) | Label Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x x x x| Res |Len| DLCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| FR Label (0x101) | Label Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x x x x| Res |Len| DLCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Res The Res field is reserved in [21], i.e., it is not explicitly reserved by GSMP.
Res Res字段在[21]中保留，即GSMP未明确保留该字段。
Len The Len field specifies the number of bits of the DLCI. The following values are supported:
Len Len字段指定DLCI的位数。支持以下值：
Len DLCI bits 0 10 2 23
Len DLCI位0 10 2 23
DLCI DLCI is the binary value of the Frame Relay Label. The significant number of bits (10 or 23) of the label value is to be encoded into the Data Link Connection Identifier (DLCI) field when part of the Frame Relay data link header [13].
DLCI DLCI是帧中继标签的二进制值。当作为帧中继数据链路头的一部分时，标签值的有效位数（10或23）将被编码到数据链路连接标识符（DLCI）字段中[13]。
If a port's attribute PortType=MPLS, then that port's labels are for use on links for which label values are independent of the underlying link technology. Examples of such links are PPP and Ethernet. On such links the labels are carried in MPLS label stacks [14]. If the Label Type = MPLS Generic Label, the labels MUST be interpreted as Generic MPLS labels as shown:
如果端口的属性PortType=MPLS，则该端口的标签用于标签值独立于基础链路技术的链路。这种链路的例子有PPP和以太网。在这样的链路上，标签以MPLS标签栈的形式携带[14]。如果标签类型=MPLS通用标签，则标签必须解释为通用MPLS标签，如图所示：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| MPLS Gen Label (0x102)| Label Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x x x x x x x x x x x x| MPLS Label |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| MPLS Gen Label (0x102)| Label Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x x x x x x x x x x x x| MPLS Label |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
MPLS Label This is a 20-bit label value as specified in [14], represented as a 20-bit number in a 4-byte field.
MPLS标签这是[14]中指定的20位标签值，表示为4字节字段中的20位数字。
Labels may be bound to Forwarding Equivalence Classes (FECs) as defined in [18]. A FEC is a list of one or more FEC elements. The FEC TLV encodes FEC items. In this version of the protocol only, Prefix FECs are supported. If the Label Type = FEC Label, the labels MUST be interpreted as Forwarding Equivalence Class Labels as shown:
标签可以绑定到[18]中定义的转发等价类（FEC）。FEC是一个或多个FEC元素的列表。FEC TLV对FEC项目进行编码。仅在此版本的协议中，支持前缀FEC。如果标签类型=FEC标签，则标签必须解释为转发等价类标签，如图所示：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| FEC Label (0x103) | Label Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ FEC Element 1 ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ FEC Element n ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| FEC Label (0x103) | Label Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ FEC Element 1 ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ FEC Element n ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
FEC Element The FEC element encoding depends on the type of FEC element. In this version of GSMP only, Prefix FECs are supported.
FEC元素FEC元素编码取决于FEC元素的类型。仅在此版本的GSMP中，支持前缀FEC。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Element Type | Address Family | Prefix Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ Prefix ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Element Type | Address Family | Prefix Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ Prefix ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Element Type In this version of GSMP the only supported Element Type is Prefix FEC Elements. The Prefix FEC Element is a one-octet value, encoded as 0x02.
元素类型在此版本的GSMP中，唯一支持的元素类型是前缀FEC元素。前缀FEC元素是一个八位字节值，编码为0x02。
Address Family Two-byte quantity containing a value from ADDRESS FAMILY NUMBERS in [5], that encodes the address family for the address prefix in the Prefix field.
地址族两字节数量，包含[5]中地址族编号的值，该值为前缀字段中的地址前缀编码地址族。
Prefix Length One byte containing the length in bits of the address prefix that follows. A length of zero indicates a prefix that matches all addresses (the default destination); in this case the Prefix itself is zero bytes.
前缀长度一个字节，包含后面地址前缀的长度（以位为单位）。长度为零表示与所有地址匹配的前缀（默认目的地）；在这种情况下，前缀本身是零字节。
Prefix An address prefix encoded according to the Address Family field, whose length, in bits, was specified in the Prefix Length field.
前缀根据地址族字段编码的地址前缀，其长度（以位为单位）在前缀长度字段中指定。
Label stacking is a technique used in MPLS [14] that allows hierarchical labelling. MPLS label stacking is similar to, but subtly different from, the VPI/VCI hierarchy of labels in ATM. There is no set limit to the depth of label stacks that can be used in GSMP.
标签堆叠是MPLS[14]中使用的一种技术，允许分层标签。MPLS标签堆叠与ATM中标签的VPI/VCI层次结构相似，但略有不同。GSMP中可以使用的标签堆栈深度没有设置限制。
When the Stacked Label Indicator S is set to 1 it indicates that an additional label field will be appended to the adjacent label field. For example, a stacked Input Short Label could be designated as follows:
当堆叠标签指示器S设置为1时，表示将向相邻标签字段追加一个附加标签字段。例如，堆叠输入短标签可以指定如下：
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| |
+-+-+-+-+ Input Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
** |x|S|x|x| |
+-+-+-+-+ Stacked Input Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| |
+-+-+-+-+ Input Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
** |x|S|x|x| |
+-+-+-+-+ Stacked Input Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
** Note: There can be zero or more Stacked Labels fields (like those marked **) following an Input or Output Label field. A Stacked Label follows the previous label field if and only if the S Flag in the previous label is set.
**注意：输入或输出标签字段后面可以有零个或多个堆叠标签字段（如标记为**的字段）。当且仅当设置了上一个标签中的S标志时，堆叠标签将跟随上一个标签字段。
When a label is extended by stacking, it is treated by the protocol as a single extended label, and all operations on that label are atomic. For example, in an add branch message, the entire input label is switched for the entire output label. Likewise, in Move Input Branch and Move Output Branch messages, the entire label is swapped. For that reason, in all messages that designate a label field, it will be depicted as a single 64-bit field, though it might be instantiated by many 64-bit fields in practice.
当通过堆叠扩展标签时，协议将其视为单个扩展标签，并且该标签上的所有操作都是原子操作。例如，在添加分支消息中，整个输入标签切换为整个输出标签。同样，在“移动输入分支”和“移动输出分支”消息中，将交换整个标签。因此，在所有指定标签字段的消息中，它将被描述为单个64位字段，尽管在实践中可能会被许多64位字段实例化。
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.)
如果交换机发出故障响应以响应请求消息，则不应因导致故障的消息而更改交换机的状态。（对于包含多个请求的请求消息，例如Delete Branchs消息，failure response消息将指定哪些请求成功，哪些请求失败。成功的请求可能会导致状态更改。）
A warning response message is a success response (Result = 3) with the Code field specifying the warning code. The warning code specifies a warning that was generated during the successful operation.
警告响应消息是成功响应（结果=3），代码字段指定警告代码。警告代码指定在成功操作期间生成的警告。
If the switch issues a failure response it MUST choose the most specific failure code according to the following precedence:
如果交换机发出故障响应，则必须根据以下优先级选择最具体的故障代码：
- Invalid Message
- 无效消息
- General Message Failure
- 一般消息失败
- Specific Message Failure A failure response specified in the text defining the message type.
- 特定消息故障在定义消息类型的文本中指定的故障响应。
- Connection Failures
- 连接故障
- Virtual Path Connection Failures
- 虚拟路径连接失败
- Multicast Failures
- 多播失败
- QoS Failures
- QoS故障
- General Failures
- 一般故障
- Warnings
- 警告
If multiple failures match in any of the categories, the one that is listed first should be returned. Descriptions of the Failure response messages can be found in section 12.
如果多个故障在任何类别中匹配，则应返回首先列出的故障。故障响应消息的说明见第12节。
Connection management messages are used by the controller to establish, delete, modify and verify 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reservation ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Service Selector |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Service Selector |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|IQS|OQS|P|x|N|O| Adaptation Method |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| |
+-+-+-+-+ Input Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| |
+-+-+-+-+ Output Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reservation ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Service Selector |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Service Selector |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|IQS|OQS|P|x|N|O| Adaptation Method |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| |
+-+-+-+-+ Input Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| |
+-+-+-+-+ Output Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
When required, the Add Branch, Move Input Branch and Move Output Branch messages have an additional, variable length data block appended to the above message. This will be required when indicated by the IQS and OQS flags (if the value of either is set to 0b10) and the service selector. The additional data block has the following format:
如果需要，添加分支、移动输入分支和移动输出分支消息会在上述消息后附加一个可变长度的附加数据块。当IQS和OQS标志（如果其中一个的值设置为0b10）和服务选择器指示时，这将是必需的。附加数据块具有以下格式：
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input TC Flags|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Traffic Parameters Block ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Output TC Flags|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Traffic Parameters Block ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input TC Flags|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Traffic Parameters Block ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Output TC Flags|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Traffic Parameters Block ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Note: Fields and Parameters that have been explained in the description of the general messages will not be explained in this section. Please refer to section 3.1 for details.
注意：本节将不解释在一般消息说明中已解释的字段和参数。详情请参考第3.1节。
Reservation ID Identifies the reservation that MUST be deployed for the branch being added. Reservations are established using reservation management messages (see Chapter 5). A value of zero indicates that no Reservation is being deployed for the branch. If a reservation with a corresponding Reservation ID exists, then the reserved resources MUST be applied to the branch. If the numerical value of Reservation ID is greater than the value of Max Reservations (from the Switch Configuration message), a failure response is returned indicating "20: Reservation ID out of Range". If the value of Input Port differs from the input port specified in the reservation, or if the value of Output Port differs from the output port specified in the reservation, a failure response MUST be returned indicating "21: Mismatched reservation ports". If no reservation corresponding to Reservation ID exists, a failure response MUST be returned indicating "23: Non-existent reservation ID".
保留ID标识必须为要添加的分支部署的保留。使用预订管理消息建立预订（参见第5章）。值为零表示没有为分支部署保留。如果存在具有相应保留ID的保留，则必须将保留资源应用于分支。如果保留ID的数值大于最大保留值（来自交换机配置消息），则返回故障响应，指示“20：保留ID超出范围”。如果输入端口的值与保留中指定的输入端口不同，或者如果输出端口的值与保留中指定的输出端口不同，则必须返回故障响应，指示“21:不匹配的保留端口”。如果不存在与保留ID对应的保留，则必须返回一个失败响应，指示“23：不存在保留ID”。
If a valid Reservation ID is specified and the Service Model is used (i.e., IQS or OQS=0b10) then the Traffic Parameters Block may be omitted from the Add Branch message indicating that the Traffic Parameters specified in the corresponding Reservation Request message are to be used.
如果指定了有效的预订ID并使用了服务模型（即IQS或OQS=0b10），则可以从添加分支消息中省略流量参数块，指示将使用相应预订请求消息中指定的流量参数。
Input Port Identifies a switch input port.
输入端口标识交换机输入端口。
Input Label Identifies an incoming labelled channel arriving at the switch input port indicated by the Input Port field. The value in the Input Label field MUST be interpreted according to the Label Type attribute of the switch input port indicated by the Input Port field.
输入标签标识到达输入端口字段指示的交换机输入端口的带标签的传入通道。输入标签字段中的值必须根据输入端口字段指示的交换机输入端口的标签类型属性进行解释。
Input Service Selector Identifies details of the service specification being used for the connection. The interpretation depends upon the Input QoS Model Selector (IQS).
输入服务选择器标识用于连接的服务规范的详细信息。解释取决于输入QoS模型选择器（IQS）。
IQS = 00: In this case, the Input Service Selector indicates a simple priority.
IQS=00：在这种情况下，输入服务选择器指示一个简单的优先级。
IQS = 01: In this case, the Input Service Selector is an opaque service profile identifier. The definition of these service profiles is outside the scope of this specification. Service Profiles can be used to indicate pre-defined Differentiated Service Per Hop Behaviours.
IQS=01：在这种情况下，输入服务选择器是一个不透明的服务配置文件标识符。这些服务配置文件的定义不在本规范的范围内。服务配置文件可用于指示预定义的区分服务每跳行为。
IQS = 10: In this case, the Input Service Selector corresponds to a Service Spec as defined in Chapter 8.2. When the value of either IQS or OQS is set to 0b10, then a Traffic Parameters Block is appended to the message.
IQS=10：在这种情况下，输入服务选择器对应于第8.2章中定义的服务规范。当IQS或OQS的值设置为0b10时，将在消息中附加一个流量参数块。
IQS = 11: In this case the Input Service Selector corresponds to an ARM service specification. Definition of ARM service specifications is outside the scope of this specification and is determined by the MType as defined in Chapter 8.1.
IQS=11：在这种情况下，输入服务选择器对应于ARM服务规范。ARM服务规范的定义不在本规范的范围内，由第8.1章中定义的MType确定。
Output Port Identifies a switch output port.
输出端口标识交换机输出端口。
Output Label Identifies an outgoing labelled channel departing at the switch output port indicated by the Output Port field. The value in the Output Label field MUST be interpreted according to the Label Type attribute of the switch input port indicated by the Output Port field
输出标签标识输出端口字段指示的交换机输出端口处离开的带标签的传出通道。输出标签字段中的值必须根据输出端口字段指示的交换机输入端口的标签类型属性进行解释
Output Service Selector Identifies details of the service model being used. The interpretation depends upon the Output QoS Model selector (OQS).
输出服务选择器标识正在使用的服务模型的详细信息。解释取决于输出QoS模型选择器（OQS）。
OQS = 00: In this case the Output Service Selector indicates a simple priority.
OQS=00：在这种情况下，输出服务选择器指示简单优先级。
OQS = 01: In this case the Output Service Selector is an opaque service profile identifier. The definition of these service profiles is outside the scope of this specification. Service Profiles can be used to indicate pre-defined Differentiated Service Per Hop Behaviours.
OQS=01：在这种情况下，输出服务选择器是一个不透明的服务配置文件标识符。这些服务配置文件的定义不在本规范的范围内。服务配置文件可用于指示预定义的区分服务每跳行为。
OQS = 10: In this case the Output Service Selector corresponds to a Service Spec as defined in Chapter 8.2. When the value of either IQS or OQS is set to 0b10 then a Traffic Parameters Block is appended to the message.
OQS=10：在这种情况下，输出服务选择器对应于第8.2章中定义的服务规范。当IQS或OQS的值设置为0b10时，将在消息中附加一个流量参数块。
OQS = 11: In this case the Output Service Selector corresponds to an ARM service specification. Definition of ARM service specifications is outside the scope of this specification and is determined by the MType as defined in Chapter 8.1.
OQS=11：在这种情况下，输出服务选择器对应于ARM服务规范。ARM服务规范的定义不在本规范的范围内，由第8.1章中定义的MType确定。
IQS, OQS Input and Output QoS Model Selector: The QoS Model Selector is used to specify a QoS Model for the connection. The values of IQS and OQS determine respectively the interpretation of the Input Service Selector and the Output Service Selector, and SHOULD be interpreted as a priority, a QoS profile, a service specification, or an ARM specification as shown:
IQS、OQS输入和输出QoS模型选择器：QoS模型选择器用于指定连接的QoS模型。IQS和OQS的值分别确定输入服务选择器和输出服务选择器的解释，并应解释为优先级、QoS配置文件、服务规范或ARM规范，如图所示：
IQS/OQS QoS Model Service Selector
------- --------- ----------------
00 Simple Abstract Model Priority
01 QoS Profile Model QoS Profile
10 Default Service Model Service Specification
11 Optional ARM ARM Specification
IQS/OQS QoS Model Service Selector
------- --------- ----------------
00 Simple Abstract Model Priority
01 QoS Profile Model QoS Profile
10 Default Service Model Service Specification
11 Optional ARM ARM Specification
P Flag If the Parameter flag is set it indicates that a single instance of the Traffic Parameter block is provided. This occurs in cases where the Input Traffic Parameters are identical to Output Traffic Parameters.
P标志如果设置了参数标志，则表示提供了交通参数块的单个实例。在输入流量参数与输出流量参数相同的情况下会发生这种情况。
N Flag The Null flag is used to indicate a null adaptation method. This occurs when the branch is connecting two ports of the same type.
N标志空标志用于指示空自适应方法。当分支连接两个相同类型的端口时会发生这种情况。
O Flag The Opaque flag indicates whether the adaptation fields are opaque, or whether they are defined by the protocol. See the definition of Adaptation Method below for further information.
O标志不透明标志指示自适应字段是不透明的，还是由协议定义的。有关更多信息，请参见下面的自适应方法定义。
Adaptation Method The adaptation method is used to define the adaptation framing that may be in use when moving traffic from one port type to another port type; e.g., from a frame relay port to an ATM port. The content of this field is defined by the Opaque flag. If the Opaque flag is set, then this field is defined by the switch manufacturer and is not defined in this protocol. If the opaque flag is not set, the field is divided into two 12- bit fields as follows:
自适应方法自适应方法用于定义在将业务从一种端口类型移动到另一种端口类型时可能正在使用的自适应帧；e、 例如，从帧中继端口到ATM端口。此字段的内容由不透明标志定义。如果设置了不透明标志，则此字段由交换机制造商定义，且不在此协议中定义。如果未设置不透明标志，该字段将分为两个12位字段，如下所示：
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|IQS|OQS|P|x|N|O| Input Adaptation | Output Adaptation |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|IQS|OQS|P|x|N|O| Input Adaptation | Output Adaptation |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Input Adaptation Adaptation framing method used on incoming connections.
传入连接上使用的输入自适应帧方法。
Output Adaptation Adaptation framing method used on outgoing connections.
输出适配成帧方法用于输出连接。
Adaptation Types:
适应类型：
0x100 PPP 0x200 FRF.5 0x201 FRF.8
0x100 PPP 0x200 FRF.5 0x201 FRF.8
Input and Output TC Flags TC (Traffic Control) Flags are used in Add Branch, Move Input Branch and Move Output Branch messages for connections using the Service Model (i.e., when IQS or OQS=0b10). The TC Flags field is defined in Section 10.6.
输入和输出TC标志TC（流量控制）标志用于使用服务模型的连接的添加分支、移动输入分支和移动输出分支消息（即，当IQS或OQS=0b10时）。TC标志字段在第10.6节中定义。
Input and Output Traffic Parameters Block This variable length field is used in Add Branch, Move Input Branch and Move Output Branch messages for connections using the Service Model (i.e., when IQS or OQS=0b10). Traffic Parameters Block is defined in Section 10.5. The Traffic Parameters Block may be omitted if a valid, non-zero Reservation ID is specified, in which case the Traffic Parameters of the corresponding Reservation Request message are used. If the P flag is set, then the appended message block will only include a single traffic parameter block which will be used for both input and output traffic.
输入和输出流量参数块此可变长度字段用于使用服务模型的连接的添加分支、移动输入分支和移动输出分支消息（即，当IQS或OQS=0b10时）。第10.5节定义了交通参数块。如果指定了有效的非零预约ID，则可以省略业务参数块，在这种情况下，使用相应预约请求消息的业务参数。如果设置了P标志，则附加的消息块将仅包括一个用于输入和输出流量的流量参数块。
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. 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.
故障响应消息是返回的请求消息的副本，返回的结果字段指示故障。
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 and Input Label will establish a point-to-point connection. The second Add Branch message with the same Input Port and Input Label fields will convert the connection to a point-to-multipoint connection with two branches. 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 and Input Label 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 labelled channel to one or more output labelled channels.
基本上，点对点和点对多点连接之间没有区别。默认情况下，特定输入端口和输入标签的第一条添加分支消息将建立点对点连接。具有相同输入端口和输入标签字段的第二条添加分支消息将连接转换为具有两个分支的点对多点连接。然而，为了避免某些交换机设计可能的低效，提供了多播标志。如果控制器在建立第一个分支时知道一个新连接是点对多点的，它可以在多播标志中指示这一点。具有相同输入端口和输入标签字段的后续添加分支消息将向点对多点连接添加更多分支。在具有两个分支的点对多点连接上使用Delete Branch消息将导致点对点连接。但是，如果交换机选择，它可以将此连接构造为具有单个输出分支的点对多点连接。（对于某些交换机设计，此结构可能更方便。）在点到点连接上使用删除分支消息将删除点到点连接。没有零输出分支连接的概念。所有连接都是单向的，一个输入标记通道到一个或多个输出标记通道。
In GSMP 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 label.)
在GSMP中，通过建立多个点对点连接来指定多点对点连接，每个点对点连接指定相同的输出分支。（输出分支由输出端口和输出标签指定。）
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 states 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 connection or to add an additional branch to an existing connection. It may also be used to check the connection state stored in the switch. The connection is specified by the Input Port and Input Label fields. The output branch is specified by the Output Port and Output Label fields. The quality of service requirements of the connection are specified by the QoS Model Selector and Service Selector fields. To request a connection the Add Branch message is:
添加分支消息是一条连接管理消息，用于建立连接或向现有连接添加其他分支。它还可用于检查存储在交换机中的连接状态。连接由输入端口和输入标签字段指定。输出分支由输出端口和输出标签字段指定。连接的服务质量要求由QoS模型选择器和服务选择器字段指定。要请求连接，添加分支消息为：
Message Type = 16
消息类型=16
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reservation ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Service Selector |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Service Selector |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|IQS|OQS|P|x|N|O| Adaptation Method |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|M|B| |
+-+-+-+-+ Input Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|M|R| |
+-+-+-+-+ Output Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reservation ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Service Selector |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Service Selector |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|IQS|OQS|P|x|N|O| Adaptation Method |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|M|B| |
+-+-+-+-+ Input Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|M|R| |
+-+-+-+-+ Output Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
When the value of either IQS or OQS is set to 0b10 then the following Traffic Parameters Block is appended to the above message:
当IQS或OQS的值设置为0b10时，以下交通参数块将附加到上述消息中：
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Input TC Flags |x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Input Traffic Parameters Block ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Output TC Flags|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Output Traffic Parameters Block ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Input TC Flags |x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Input Traffic Parameters Block ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Output TC Flags|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Output Traffic Parameters Block ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Note: Fields and Parameters that have been explained in the description of the general connection message will not be explained in this section. Please refer to section 4.1 for details.
注意：本节将不解释在常规连接消息描述中已解释的字段和参数。详情请参考第4.1节。
M: Multicast Multicast flags are used as a hint for point-to-multipoint or multipoint-to-point connections in the Add Branch message. They are not used in any other connection management messages and in these messages they SHOULD be set to zero. There are two instances of the M-bit in the Add Branch message; one for input branch specified by the Input Port and Input Label fields and one for the output branch specified by the Output Port and Output Label fields. If set for the input branch (in front of Input Label field), it indicates that the 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. If set for the output branch (in front of the Output Label field), it indicates that the connection is very likely to be a multipoint-to-point connection. If zero, it indicates that this connection is very likely to be a point-to-point connection or is unknown.
M：多播标志在添加分支消息中用作点对多点或多点对点连接的提示。它们不用于任何其他连接管理消息中，在这些消息中，它们应设置为零。添加分支消息中有两个M位实例；一个用于输入端口和输入标签字段指定的输入分支，另一个用于输出端口和输出标签字段指定的输出分支。如果为输入分支设置（在输入标签字段前面），则表示该连接很可能是点对多点连接。如果为零，则表示此连接很可能是点对点连接或未知。如果为输出分支设置（在输出标签字段前面），则表示该连接很可能是多点对点连接。如果为零，则表示此连接很可能是点对点连接或未知。
If M flags are set for input as well as output branches, it indicates that the connection is very likely to be a multipoint-to-multipoint connection.
如果为输入分支和输出分支设置了M标志，则表示该连接很可能是多点到多点连接。
The Multicast flags are 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 or a multipoint-to-point connection and
当建立新连接的第一个分支时，多播标志仅在添加分支消息中使用。在建立点对多点或多点对点连接的后续分支时，无需进行设置，并且
on such connections it SHOULD be ignored by the receiver. (Except in cases where the connection replace bit is enabled and set, the receipt of the second and subsequent Add Branch messages from the receiver indicates a point-to-multipoint or a multipoint-to-point connection.) If it is known that this is the first branch of a point-to-multipoint or a multipoint-to-point 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 the multicast flag is not mandatory and may be ignored by the switch. If unused, the flags SHOULD be set to zero. Some switches use a different data structure for multicast connections rather than for point-to-point connections. These flags prevent the switch from setting up a point-to-point structure for the first branch of a multicast connection that MUST immediately be deleted and reconfigured as point-to-multipoint or multipoint-to-point when the second branch is established.
在这种连接上，接收器应该忽略它。（除非启用并设置了连接替换位，否则从接收器接收到的第二条和后续Add分支消息表示点对多点或多点对点连接。）如果已知这是点对多点或多点对点连接的第一条分支，应设置此标志。如果未知，或者如果已知连接是点对点的，则此标志应为零。多播标志的使用不是强制性的，交换机可能会忽略它。如果未使用，则标志应设置为零。有些交换机使用不同的数据结构进行多播连接，而不是点到点连接。这些标志阻止交换机为多播连接的第一个分支设置点对点结构，当建立第二个分支时，必须立即删除该分支并将其重新配置为点对多点或多点对点。
B: Bi-directional The Bi-directional 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 Bi-directional flag in an Add Branch message, if set, requests that two unidirectional connections 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 Label, Output Port and Output Label as specified in the Add Branch message. The reverse direction is derived by exchanging the values specified in the Input Port and Input Label fields, with those of the Output Port and Output Label fields respectively. Thus, a connection in the reverse direction originates at the input port specified by the Output Port field, on the label specified by the Output Label field. It departs from the output port specified by the Input Port field, on the label specified by the Input Label field.
B:双向双向标志仅适用于添加分支消息。在所有其他连接管理消息中不使用它。它只能在建立点对点连接时使用。添加分支消息中的双向标志（如果设置）请求建立两个单向连接，一个在正向，另一个在反向。它相当于两条添加分支消息，一条指定正向，另一条指定反向。前进方向使用添加分支消息中指定的输入端口、输入标签、输出端口和输出标签的值。反向是通过将输入端口和输入标签字段中指定的值分别与输出端口和输出标签字段中的值进行交换而得出的。因此，反向连接起源于输出端口字段指定的输入端口，位于输出标签字段指定的标签上。它在输入标签字段指定的标签上偏离输入端口字段指定的输出端口。
The Bi-directional flag is simply a convenience to establish two unidirectional connections in opposite directions between the same two ports, with identical Labels, using a single Add Branch message. In all future messages the two unidirectional connections MUST be handled separately. There is no bi-directional 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.
双向标志只是为了方便使用单个Add分支消息在相同的两个端口之间以相反方向建立具有相同标签的两个单向连接。在将来的所有消息中，必须分别处理两个单向连接。没有双向删除消息。但是，可以使用带有两个删除分支元素的单个删除分支消息，一个用于正向连接，另一个用于反向连接。
R: Connection Replace The Connection Replace flag applies only to the Add Branch message and is not used in any other Connection Management messages. The R flag is used in cases when creation of multipoint-to-point connections is undesirable (e.g., POTS applications where fan-in is meaningless). If the R flag is set, the new connection replaces any existing connection if the label is already in use at the same Output Port.
R:Connection Replace连接替换标志仅适用于添加分支消息，不用于任何其他连接管理消息。R标志用于不需要创建多点对点连接的情况（例如，扇入没有意义的POTS应用程序）。如果设置了R标志，则如果标签已在同一输出端口上使用，则新连接将替换任何现有连接。
The Connection Replace mechanism allows a single Add Connection command to function as either a Move Branch message or a combination of Delete Branch/Add Branch messages. This mechanism is provided to support existing 64k call handling applications, such as emulating 64k voice switches.
连接替换机制允许单个添加连接命令作为移动分支消息或删除分支/添加分支消息的组合。提供此机制是为了支持现有的64k呼叫处理应用程序，例如模拟64k语音交换机。
The use of R flag is optional and MUST be pre-configured in the Port Management message [see section 6.1] to activate its use. The R flag MUST NOT be set if it is not pre-configured with the Port Management message. The switch MUST then return a Failure Response message: "36: Replace of connection is not activated on switch". Information about whether the function is active or not, can be obtained by using the Port Configuration message [see section 8.2].
R标志的使用是可选的，必须在端口管理消息中预先配置[参见第6.1节]以激活其使用。如果未使用端口管理消息预先配置R标志，则不得设置该标志。然后，开关必须返回故障响应消息：“36：开关上未激活连接的更换”。可通过使用端口配置消息获取有关功能是否处于活动状态的信息[参见第8.2节]。
The R flag MUST NOT be set if either the M flag or the B flag is set. If a switch receives an Add connection request that has the R flag set with either the B or the M flag set, it MUST return a failure response message of: "37: Connection replacement mode cannot be combined with Bi-directional or Multicast mode"
如果设置了M标志或B标志，则不得设置R标志。如果交换机接收到一个添加连接请求，该请求的R标志设置为B或M标志，则它必须返回故障响应消息：“37：连接替换模式不能与双向或多播模式组合”
If the connection specified by the Input Port and Input Label fields does not already exist, it MUST be established with the single output branch specified in the request message. If the Bi-directional 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.
如果输入端口和输入标签字段指定的连接不存在，则必须使用请求消息中指定的单个输出分支建立连接。如果在标志字段中设置了双向标志，则还必须建立反向连接。输出分支应该具有服务类别字段指定的QoS属性。
If the connection specified by the Input Port and Input Label fields already exists and the R flag is not set, 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.
如果输入端口和输入标签字段指定的连接已存在，并且未设置R标志，但指定的输出分支未设置，则必须添加新的输出分支。新的输出分支应该具有服务类别字段指定的QoS属性。
If the connection specified by the Input Port and Input Label 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
如果由输入端口和输入标签字段指定的连接已经存在，并且指定的输出分支也已经存在，那么由服务类别字段指定的连接的QoS属性（如果与请求消息不同）应该是
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. This may be used to reduce the traffic on the control link for messages that are reasserting a previously established state. For messages that are reasserting a 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 or frames).
更改为请求消息中的。如果请求消息的结果字段为“AckAll”，则必须发送成功响应消息。这允许控制器定期重新指定连接状态或更改其优先级。如果请求消息的结果字段为“NoSuccessAck”，则不应返回成功响应消息。这可用于减少控制链路上正在重新确认先前建立的状态的消息的通信量。对于重发先前建立的状态的消息，交换机必须始终检查交换机硬件（即用于转发小区或帧的实际连接表）中是否正确建立了该状态。
If the connection specified by the Input Port and Input Label fields already exists, and the Bi-directional Flag in the Flags field is set, a failure response MUST be returned indicating: "15: Point-to-point bi-directional connection already exists".
如果输入端口和输入标签字段指定的连接已经存在，并且在标志字段中设置了双向标志，则必须返回故障响应，指示“15：点对点双向连接已经存在”。
It should be noted that different switches support multicast in different ways. There may be a limit to the total number of point-to-multipoint or multipoint-to-point connections certain switches can support, and possibly a limit on the maximum number of branches that a point-to-multipoint or multipoint-to-point connection may specify. Some switches also impose a limit on the number of different Label values that may be assigned e.g., 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.
应该注意的是，不同的交换机以不同的方式支持多播。某些交换机可以支持的点对多点或多点对点连接的总数可能有限制，点对多点或多点对点连接可能指定的最大分支数也可能有限制。一些开关还对可分配的不同标签值的数量施加限制，例如，点对多点连接的输出分支。许多交换机无法在同一输出端口上支持任何特定点对多点连接的多个分支。针对其中一些情况定义了特定的故障代码。
4.2.1 ATM specific procedures:
4.2.1 ATM特定程序：
To request an ATM virtual path connection the ATM Virtual Path Connection (VPC) Add Branch message is:
要请求ATM虚拟路径连接，ATM虚拟路径连接（VPC）添加分支消息为：
Message Type = 26
消息类型=26
An ATM virtual path connection can only be established between ATM ports, i.e., ports with the "ATM" Label Type attribute. If an ATM VPC Add Branch message is received and either the switch input port specified by the Input Port field or the switch output port specified by the Output Port field is not an ATM port, a failure response message MUST be returned indicating, "28: ATM Virtual path switching is not supported on non-ATM ports".
ATM虚拟路径连接只能在ATM端口之间建立，即具有“ATM”标签类型属性的端口。如果收到ATM VPC Add分支消息，且输入端口字段指定的交换机输入端口或输出端口字段指定的交换机输出端口不是ATM端口，则必须返回故障响应消息，指示“28：非ATM端口不支持ATM虚拟路径交换”。
If an ATM 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, "24: ATM virtual path switching is not supported on this input port".
如果接收到ATM VPC Add分支消息，且输入端口字段指定的交换机输入端口不支持虚拟路径交换，则必须返回故障响应消息，指示“24：此输入端口不支持ATM虚拟路径交换”。
If an ATM 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 "27: Attempt to add an ATM 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, "26: Attempt to add an ATM virtual path connection branch to an existing virtual channel connection".
如果输入端口和输入VPI字段指定的虚拟路径上已经存在ATM虚拟路径连接，则必须返回故障响应消息，指示“27：尝试将ATM虚拟通道连接分支添加到现有虚拟路径连接”。对于VPC添加分支消息，如果输入端口和输入VPI字段指定的虚拟路径内的任何虚拟通道上已经存在虚拟通道连接，则必须返回故障响应消息，指示“26：尝试将ATM虚拟路径连接分支添加到现有虚拟通道连接”。
The Delete Tree message is a Connection Management message used to delete an entire connection. All remaining branches of the connection are deleted. A connection is defined by the Input Port and the Input Label fields. The Output Port and Output Label fields are not used in this message. The Delete Tree message is:
删除树消息是用于删除整个连接的连接管理消息。将删除连接的所有剩余分支。连接由输入端口和输入标签字段定义。此消息中未使用输出端口和输出标签字段。删除树消息为：
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.
如果请求消息的结果字段为“AckAll”，则在成功删除指定连接时必须发送成功响应消息。在完成删除操作之前，以及在可能的情况下，在传输排队等待传输的连接上的所有数据之前，不得发送成功消息。
The Verify Tree message has been removed from this version of GSMP.
验证树消息已从此版本的GSMP中删除。
Message Type = 19
消息类型=19
If a request message is received with Message Type = 19, a failure response MUST be returned with the Code field indicating:
如果收到消息类型为19的请求消息，则必须返回故障响应，代码字段指示：
"3: The specified request is not implemented on this switch.".
“3:指定的请求未在此交换机上实现。”。
The Delete All Input Port message is a connection management message used to delete all connections on a switch input port. All connections that originate at the specified input port MUST be deleted. On completion of the operation all dynamically assigned Label values for the specified port MUST be unassigned, i.e., there MUST be no connections established in the Label space that GSMP controls on this port. The Service Selectors, Output Port, Input
“删除所有输入端口”消息是一条连接管理消息，用于删除交换机输入端口上的所有连接。必须删除源自指定输入端口的所有连接。操作完成后，必须取消指定端口的所有动态分配的标签值，即GSMP控制的标签空间中不得建立任何连接。服务选择器、输出端口、输入
Label and Output Label fields are not used in this message. The Delete All Input Port message is:
此消息中未使用标签和输出标签字段。“删除所有输入端口”消息为：
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 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 Input Port request.
以下故障响应消息可能会返回到删除所有输入端口请求。
3: The specified request is not implemented on this switch.
3:指定的请求未在此交换机上实现。
4: One or more of the specified ports does not exist.
4:一个或多个指定端口不存在。
5: Invalid Port Session Number.
5:端口会话号无效。
If any field in a Delete All Input Port message not covered by the above failure codes is invalid, a failure response MUST be returned indicating: "2: Invalid request message". Else, the Delete All Input Port operation MUST be completed successfully and a success message returned. No other failure messages are permitted.
如果上述故障代码未涵盖的Delete All Input Port消息中的任何字段无效，则必须返回故障响应，指示“2：无效请求消息”。否则，必须成功完成删除所有输入端口操作并返回成功消息。不允许出现其他故障消息。
The Delete All message is a connection management message used to delete all connections on a switch output port. All connections that have the specified output port MUST be deleted. On completion of the operation all dynamically assigned Label values for the specified port MUST be unassigned, i.e., there MUST be no connections established in the Label space that GSMP controls on this port. The Service Selectors, Input Port, Input Label and Output Label fields are not used in this message. The Delete All Output Port message is:
“全部删除”消息是一条连接管理消息，用于删除交换机输出端口上的所有连接。必须删除具有指定输出端口的所有连接。操作完成后，必须取消指定端口的所有动态分配的标签值，即GSMP控制的标签空间中不得建立任何连接。此消息中不使用服务选择器、输入端口、输入标签和输出标签字段。删除所有输出端口消息为：
Message Type = 21
消息类型=21
If the Result field of the request message is "AckAll", a success response message MUST be sent upon completion of the operation. 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 Output Port request.
以下故障响应消息可能会返回到删除所有输出端口请求。
3: The specified request is not implemented on this switch.
3:指定的请求未在此交换机上实现。
4: One or more of the specified ports does not exist.
4:一个或多个指定端口不存在。
5: Invalid Port Session Number.
5:端口会话号无效。
If any field in a Delete All Output Port message not covered by the above failure codes is invalid, a failure response MUST be returned indicating: "2: Invalid request message". Else, the delete all operation MUST be completed successfully and a success message returned. No other failure messages are permitted.
如果上述故障代码未涵盖的Delete All Output Port消息中的任何字段无效，则必须返回故障响应，指示“2:无效请求消息”。否则，必须成功完成“全部删除”操作并返回成功消息。不允许出现其他故障消息。
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 channel, 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x| 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x| Number of Elements |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Delete Branch Elements ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Note: Fields and Parameters that have been explained in the description of the general connection message will not be explained in this section. Please refer to section 4.1 for details.
注意：本节将不解释在常规连接消息描述中已解释的字段和参数。详情请参考第4.1节。
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 a branch to be deleted and has the following structure:
每个“删除分支”元素指定要删除的分支，并具有以下结构：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Error |x|x|x|x|x|x|x|x|x|x|x|x| Element Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| |
+-+-+-+-+ Input Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| |
+-+-+-+-+ Output Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Error |x|x|x|x|x|x|x|x|x|x|x|x| Element Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| |
+-+-+-+-+ Input Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| |
+-+-+-+-+ Output Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Note: Fields and Parameters that have been explained in the description of the general connection message will not be explained in this section. Please refer to section 4.1 for details.
注意：本节将不解释在常规连接消息描述中已解释的字段和参数。详情请参考第4.1节。
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 12, "Failure Response Codes".
错误用于返回故障代码，指示删除分支失败响应消息中特定删除分支元素失败的原因。错误字段未在请求消息中使用，必须设置为零。值为零表示此删除分支元素指定的删除操作已成功。第12节“故障响应代码”中规定了其他故障代码的值。
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, a connection is specified by the Input Port and Input Label fields. The specific branch to be deleted is indicated by the Output Port and Output Label fields.
在每个Delete分支元素中，连接由输入端口和输入标签字段指定。要删除的特定分支由输出端口和输出标签字段指示。
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 "10: General Message Failure" 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.
如果任何Delete Branch元素中出现故障，则必须返回Delete branchs故障响应消息。删除分支失败响应消息是请求消息的副本，整个消息的代码字段设置为“10：一般消息失败”，每个删除分支元素的错误字段指示每个请求的删除操作的结果。任何删除分支元素中的故障不得干扰任何其他删除分支元素的处理。
The Move Output Branch message is used to move a branch of an existing connection from its current output port label to a new output port label in a single atomic transaction. The Move Output Branch connection management message has the following format for both request and response messages:
Move Output Branch消息用于在单个原子事务中将现有连接的分支从其当前输出端口标签移动到新的输出端口标签。移动输出分支连接管理消息的请求和响应消息格式如下：
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Service Selector |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Old Output Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| New Output Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Service Selector |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|IQS|OQS|P|x|N|O| Adaptation Method |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| |
+-+-+-+-+ Input Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| |
+-+-+-+-+ Old Output Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| |
+-+-+-+-+ New Output Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Service Selector |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Old Output Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| New Output Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Service Selector |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|IQS|OQS|P|x|N|O| Adaptation Method |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| |
+-+-+-+-+ Input Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| |
+-+-+-+-+ Old Output Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| |
+-+-+-+-+ New Output Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
When the value of either IQS or OQS is set to 0b10 then the following Traffic Parameters Block is appended to the above message:
当IQS或OQS的值设置为0b10时，以下交通参数块将附加到上述消息中：
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Input TC Flags |x x x x x x x x x x x x x x x x x x x x x x x x|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Input Traffic Parameters Block ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Output TC Flags|x x x x x x x x x x x x x x x x x x x x x x x x|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Output Traffic Parameters Block ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Input TC Flags |x x x x x x x x x x x x x x x x x x x x x x x x|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Input Traffic Parameters Block ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Output TC Flags|x x x x x x x x x x x x x x x x x x x x x x x x|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Output Traffic Parameters Block ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Note: Fields and Parameters that have been explained in the description of the general connection message will not be explained in this section. Please refer to section 4.1 for details.
注意：本节将不解释在常规连接消息描述中已解释的字段和参数。详情请参考第4.1节。
The Move Output Branch message is a connection management message used to move a single output branch of connection from its current output port and Output Label, to a new output port and Output Label on the same connection. None of the connection's other output branches are modified. When the operation is complete the original Output Label on the original output port will be deleted from the connection.
Move Output Branch消息是一条连接管理消息，用于将连接的单个输出分支从其当前输出端口和输出标签移动到同一连接上的新输出端口和输出标签。连接的其他输出分支均未修改。操作完成后，原始输出端口上的原始输出标签将从连接中删除。
The Move Output Branch message is:
移动输出分支消息为：
Message Type = 22
消息类型=22
For the Move Output Branch message, if the connection specified by the Input Port and Input Label fields already exists, and the output branch specified by the Old Output Port and Old Output Label fields exists as a branch on that connection, the output branch specified by the New Output Port and New Output Label fields is added to the connection and the branch specified by the Old Output Port and Old Output Label 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.
对于移动输出分支消息，如果输入端口和输入标签字段指定的连接已经存在，并且旧输出端口和旧输出标签字段指定的输出分支作为该连接上的分支存在，将新输出端口和新输出标签字段指定的输出分支添加到连接中，并删除旧输出端口和旧输出标签字段指定的分支。如果请求消息的结果字段为“AckAll”，则必须在成功完成操作后发送成功响应消息。在移动分支操作完成之前，不得发送成功响应消息。
For the Move Output Branch message, if the connection specified by the Input Port and Input Label fields already exists, but the output branch specified by the Old Output Port and Old Output Label fields
对于Move Output Branch消息，如果输入端口和输入标签字段指定的连接已存在，但旧输出端口和旧输出标签字段指定的输出分支已存在
does not exist as a branch on that connection, a failure response MUST be returned with the Code field indicating, "12: The specified branch does not exist".
不作为该连接上的分支存在，必须返回故障响应，代码字段指示“12:指定的分支不存在”。
4.8.1 ATM Specific Procedures:
4.8.1 ATM特定程序：
The ATM VPC Move Output 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.
ATM VPC移动输出分支消息是一种连接管理消息，用于将虚拟路径连接的单个输出分支从其当前输出端口和输出VPI移动到同一虚拟通道连接上的新输出端口和输出VPI。没有修改任何其他输出分支。操作完成后，原始输出端口上的原始输出VPI将从连接中删除。
The VPC Move Branch message is:
VPC移动分支消息为：
Message Type = 27
消息类型=27
For the VPC Move Output 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 Output 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, "12: The specified branch does not exist".
对于VPC Move Output Branch消息，如果输入端口和输入VPI字段指定的虚拟路径连接已经存在，但旧输出端口和旧输出VPI字段指定的输出分支不作为该连接上的分支存在，则必须返回故障响应，代码字段指示，“12:指定的分支不存在”。
If the virtual channel connection specified by the Input Port and Input Label 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, "11: The specified connection does not exist".
如果输入端口和输入标签字段指定的虚拟通道连接；或输入端口和输入VPI字段指定的虚拟路径连接；不存在，则必须返回故障响应，代码字段指示“11:指定的连接不存在”。
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 and Input
如果由虚拟通道连接的新输出端口、新输出VPI和新输出VCI字段指定的输出分支；或由虚拟路径连接的新输出端口和新输出VPI字段指定的输出分支；已由输入端口和输入端口指定的连接以外的任何连接使用
Label 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.
标记字段，则生成的输出分支将具有多个输入分支。如果多个点对点连接共享同一输出分支，则结果将是多点对点连接。如果多个点对多点树共享相同的输出分支，则结果将是多点对多点连接。
The Move Input Branch message is used to move a branch of an existing connection from its current input port label to a new input port label in a single atomic transaction. The Move Input Branch connection management message has the following format for both request and response messages:
Move Input Branch消息用于在单个原子事务中将现有连接的分支从其当前输入端口标签移动到新的输入端口标签。移动输入分支连接管理消息的请求和响应消息格式如下：
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Service Selector |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Old Input Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| New Input Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Service Selector |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|IQS|OQS|P|x|N|O| Adaptation Method |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| |
+-+-+-+-+ Output Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| |
+-+-+-+-+ Old Input Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| |
+-+-+-+-+ New Input Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Service Selector |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Old Input Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| New Input Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Service Selector |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|IQS|OQS|P|x|N|O| Adaptation Method |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| |
+-+-+-+-+ Output Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| |
+-+-+-+-+ Old Input Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| |
+-+-+-+-+ New Input Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
When the value of either IQS or OQS is set to 0b10, then the following Traffic Parameters Block is appended to the above message:
当IQS或OQS的值设置为0b10时，以下流量参数块将附加到上述消息中：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Input TC Flags |x x x x x x x x x x x x x x x x x x x x x x x x|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Input Traffic Parameters Block ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Output TC Flags|x x x x x x x x x x x x x x x x x x x x x x x x|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Output Traffic Parameters Block ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Input TC Flags |x x x x x x x x x x x x x x x x x x x x x x x x|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Input Traffic Parameters Block ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Output TC Flags|x x x x x x x x x x x x x x x x x x x x x x x x|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Output Traffic Parameters Block ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Note: Fields and Parameters that have been explained in the description of the general connection message will not be explained in this section. Please refer to section 4.1 for details.
注意：本节将不解释在常规连接消息描述中已解释的字段和参数。详情请参考第4.1节。
The Move Input Branch message is a connection management message used to move a single input branch of connection from its current input port and Input Label, to a new input port and Input Label on the same connection. None of the connection's other input branches are modified. When the operation is complete, the original Input Label on the original input port will be deleted from the connection.
Move Input Branch消息是一条连接管理消息，用于将连接的单个输入分支从其当前输入端口和输入标签移动到同一连接上的新输入端口和输入标签。连接的其他输入分支均未修改。操作完成后，原始输入端口上的原始输入标签将从连接中删除。
The Move Input Branch message is:
移动输入分支消息为：
Message Type = 23
消息类型=23
For the Move Input Branch message, if the connection specified by the Output Port and Output Label fields already exists, and the input branch specified by the Old Input Port and Old Input Label fields exists as a branch on that connection, the input branch specified by the New Input Port and New Input Label fields is added to the connection and the branch specified by the Old Input Port and Old Input Label 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 Input Branch operation has been completed.
对于移动输入分支消息，如果由输出端口和输出标签字段指定的连接已经存在，并且由旧输入端口和旧输入标签字段指定的输入分支作为该连接上的分支存在，将新输入端口和新输入标签字段指定的输入分支添加到连接中，并删除旧输入端口和旧输入标签字段指定的分支。如果请求消息的结果字段为“AckAll”，则必须在成功完成操作后发送成功响应消息。在完成移动输入分支操作之前，不得发送成功响应消息。
For the Move Input Branch message, if the connection specified by the Output Port and Output Label fields already exists, but the input branch specified by the Old Input Port and Old Input Label fields does not exist as a branch on that connection, a failure response MUST be returned with the Code field indicating, "12: The specified branch does not exist".
对于Move Input Branch消息，如果由输出端口和输出标签字段指定的连接已经存在，但由旧输入端口和旧输入标签字段指定的输入分支不作为该连接上的分支存在，则必须返回故障响应，代码字段指示，“12:指定的分支不存在”。
4.9.1 ATM Specific Procedures:
4.9.1 ATM特定程序：
The ATM VPC Move Input Branch message is a connection management message used to move a single input branch of a virtual path connection from its current input port and input VPI, to a new input port and input VPI on the same virtual channel connection. None of the other input branches are modified. When the operation is complete, the original input VPI on the original input port will be deleted from the connection.
ATM VPC移动输入分支消息是一种连接管理消息，用于将虚拟路径连接的单个输入分支从其当前输入端口和输入VPI移动到同一虚拟通道连接上的新输入端口和输入VPI。没有修改任何其他输入分支。操作完成后，原始输入端口上的原始输入VPI将从连接中删除。
The VPC Move Input Branch message is:
VPC移动输入分支消息为：
Message Type = 28
消息类型=28
For the VPC Move Input Branch message, if the virtual path connection specified by the Output Port and Output VPI fields already exists, and the input branch specified by the Old Input Port and Old Input VPI fields exists as a branch on that connection, the input branch specified by the New Input Port and New Input VPI fields is added to the connection and the branch specified by the Old Input Port and Old Input 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 Input Branch operation has been completed.
对于VPC移动输入分支消息，如果输出端口和输出VPI字段指定的虚拟路径连接已经存在，并且旧输入端口和旧输入VPI字段指定的输入分支作为该连接上的分支存在，将新输入端口和新输入VPI字段指定的输入分支添加到连接中，并删除旧输入端口和旧输入VPI字段指定的分支。如果请求消息的结果字段为“AckAll”，则必须在成功完成操作后发送成功响应消息。在完成移动输入分支操作之前，不得发送成功响应消息。
For the VPC Move Input Branch message, if the virtual path connection specified by the Output Port and Output VPI fields already exists, but the input branch specified by the Old Input Port and Old Input
对于VPC移动输入分支消息，如果输出端口和输出VPI字段指定的虚拟路径连接已经存在，但由旧输入端口和旧输入指定的输入分支仍然存在
VPI fields does not exist as a branch on that connection, a failure response MUST be returned with the Code field indicating, "12: The specified branch does not exist".
VPI字段不作为该连接上的分支存在，必须返回故障响应，代码字段指示“12:指定的分支不存在”。
If the virtual channel connection specified by the Output Port and Output Label fields, or if the virtual path connection specified by the Output Port and Output VPI fields does not exist, a failure response MUST be returned with the Code field indicating, "11: The specified connection does not exist".
如果输出端口和输出标签字段指定的虚拟通道连接，或者输出端口和输出VPI字段指定的虚拟路径连接不存在，则必须返回故障响应，代码字段指示“11：指定的连接不存在”。
If the input branch specified by the New Input Port, New Input VPI, and New Input VCI fields for a virtual channel connection, or the input branch specified by the New Input Port and New Input VPI fields for a virtual path connection, is already in use by any connection other than that specified by the Output Port and Output Label fields, then the resulting input branch will have multiple output branches. If multiple point-to-point connections share the same input branch, the result will be a point-to-multipoint connection. If multiple multipoint-to-point trees share the same input branches, the result will be a multipoint-to-multipoint connection.
如果由用于虚拟通道连接的新输入端口、新输入VPI和新输入VCI字段指定的输入分支，或由用于虚拟路径连接的新输入端口和新输入VPI字段指定的输入分支，已由除输出端口和输出标签字段指定的连接以外的任何连接使用，然后，生成的输入分支将具有多个输出分支。如果多个点对点连接共享同一输入分支，则结果将是点对多点连接。如果多个多点对点树共享相同的输入分支，则结果将是多点对多点连接。
GSMP allows switch resources (e.g., bandwidth, buffers, queues, labels, etc.) to be reserved for connections before the connections themselves are established. This is achieved through the manipulation of Reservations in the switch.
GSMP允许在建立连接之前为连接保留交换机资源（例如带宽、缓冲区、队列、标签等）。这是通过操纵开关中的保留来实现的。
Reservations are hard state objects in the switch that can be created by the controller by sending a Reservation Request message. Each Reservation is uniquely identified by an identifying number called a Reservation ID. Reservation objects can be deleted with the Delete Reservation message or the Delete All Reservations message. A reservation object is also deleted when the Reservation is deployed by specifying a Reservation ID in a valid Add Branch message.
保留是交换机中的硬状态对象，可由控制器通过发送保留请求消息来创建。每个保留都由一个称为保留ID的标识号唯一标识。可以使用“删除保留”消息或“删除所有保留”消息删除保留对象。通过在有效的添加分支消息中指定保留ID来部署保留时，也会删除保留对象。
The reserved resources MUST remain reserved until either the reservation is deployed, in which case the resources are applied to a branch, or the reservation is explicitly deleted (with a Delete Reservation message or a Delete All Reservations message), in which case the resources are freed. Reservations and reserved resources are deleted if the switch is reset.
保留的资源必须保持保留状态，直到部署保留（在这种情况下，资源应用于分支），或者明确删除保留（使用删除保留消息或删除所有保留消息），在这种情况下，资源被释放。如果重置开关，将删除保留和保留资源。
A Reservation object includes its Reservation ID plus all the connection state associated with a branch with the exception that the branch's input label and/or output label may be unspecified. The Request Reservation message is therefore almost identical to the Add Branch message.
保留对象包括其保留ID加上与分支关联的所有连接状态，但分支的输入标签和/或输出标签可能未指定。因此，请求保留消息几乎与添加分支消息相同。
The switch establishes the maximum number of reservations it can store by setting the value of Max Reservations in the Switch Configuration response message. The switch indicates that it does not support reservations by setting Max Reservations to 0. The valid range of Reservation IDs is 1 to Max Reservations).
交换机通过在交换机配置响应消息中设置最大保留值来确定其可以存储的最大保留数。该开关通过将“最大保留”设置为0表示不支持保留。保留ID的有效范围为1到最大保留）。
The Reservation Request message creates a Reservation in the switch and reserves switch resources for a connection that may later be established using an Add Branch message. The Reservation Request Message is:
保留请求消息在交换机中创建保留，并为以后可能使用添加分支消息建立的连接保留交换机资源。预订请求消息为：
Message Type = 70
消息类型=70
The Reservation Request message has the following format for the request message:
预订请求消息的格式如下：
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reservation ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Service Selector |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Service Selector |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|IQS|OQS|P|x|N|O| Adaptation Method |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|M|B| |
+-+-+-+-+ Input Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|M|x| |
+-+-+-+-+ Output Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reservation ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Service Selector |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Service Selector |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|IQS|OQS|P|x|N|O| Adaptation Method |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|M|B| |
+-+-+-+-+ Input Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|M|x| |
+-+-+-+-+ Output Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
When the value of either IQS or OQS is set to 0b10 then the following Traffic Parameters Block is appended to the above message:
当IQS或OQS的值设置为0b10时，以下交通参数块将附加到上述消息中：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Input TC Flags |x x x x x x x x x x x x x x x x x x x x x x x x|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Input Traffic Parameters Block ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Output TC Flags|x x x x x x x x x x x x x x x x x x x x x x x x|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Output Traffic Parameters Block ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Input TC Flags |x x x x x x x x x x x x x x x x x x x x x x x x|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Input Traffic Parameters Block ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Output TC Flags|x x x x x x x x x x x x x x x x x x x x x x x x|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Output Traffic Parameters Block ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Note: Fields and Parameters that have been explained in the description of the general connection message will not be explained in this section. Please refer to section 4.1 for details.
注意：本节将不解释在常规连接消息描述中已解释的字段和参数。详情请参考第4.1节。
All the fields of the Reservation Request message have the same meanings as they do in the Add Branch message with the following exceptions:
保留请求消息的所有字段的含义与添加分支消息中的相同，但以下例外情况除外：
Reservation ID Specifies the Reservation ID of the Reservation. If the numerical value of the Reservation ID is greater than the value of the Max Reservations (from the Switch Configuration message), a failure response is returned indicating "20: the Reservation ID out of Range". If the value of Reservation ID matches that of an extant Reservation, a failure response is returned indicating "22: Reservation ID in use".
预订ID指定预订的预订ID。如果保留ID的数值大于最大保留值（来自交换机配置消息），则返回故障响应，指示“20：保留ID超出范围”。如果保留ID的值与现有保留的值匹配，则返回一个失败响应，指示“22:正在使用的保留ID”。
Input Label If a specific input label is specified, then that label is reserved along with the required resources. If the Input Label is 0 then the switch reserves the resources, but will not bind them to a label until the add branch command is given, which references the Reservation Id. If the input label is 0, then all stacked labels MUST also be zeroed.
输入标签如果指定了特定的输入标签，则该标签将与所需资源一起保留。如果输入标签为0，则交换机保留资源，但在发出“添加分支”命令（该命令引用保留Id）之前，不会将资源绑定到标签。如果输入标签为0，则所有堆叠标签也必须归零。
Output Label If a specific Output Label is specified then that label is reserved along with the required resources. If the Output Label is 0 then the switch reserves the resources, but will not bind them to a label until the add branch command is given which references the Reservation Id. If the Output Label is 0, then all stacked labels MUST also be zeroed
输出标签如果指定了特定的输出标签，则该标签将与所需资源一起保留。如果输出标签为0，则交换机保留资源，但在给出引用保留Id的add branch命令之前，不会将资源绑定到标签。如果输出标签为0，则所有堆叠标签也必须归零
When the switch receives a valid Reservation Request it reserves all the appropriate switch resources needed to establish a branch with corresponding attributes. If sufficient resources are not available, a failure response is returned indicating "18: Insufficient resources". Other failure responses are as defined for the Add Branch message.
当交换机收到有效的保留请求时，它将保留建立具有相应属性的分支所需的所有适当交换机资源。如果没有足够的资源可用，将返回一个故障响应，指示“18：资源不足”。其他故障响应如添加分支消息所定义。
The Delete Reservation message deletes a Reservation object in the switch and frees the reserved switch resources associated with that reservation object. The Reservation Request Message is:
删除保留消息删除交换机中的保留对象，并释放与该保留对象关联的保留交换机资源。预订请求消息为：
Message Type = 71
消息类型=71
The Delete Reservation 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reservation ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reservation ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
If the Reservation ID matches that of an extant Reservation then the reservation is deleted and corresponding switch resources are freed. If the numerical value of the Reservation ID is greater than the value of the Max Reservations (from the Switch Configuration message), a failure response is returned indicating "20: Reservation ID out of Range". If the value of Reservation ID does not match that of any extant Reservation, a failure response is returned indicating "23: Non-existent reservation ID".
如果保留ID与现有保留的ID匹配，则删除保留并释放相应的交换机资源。如果保留ID的数值大于最大保留值（来自交换机配置消息），则返回故障响应，指示“20：保留ID超出范围”。如果保留ID的值与任何现有保留的值不匹配，则返回一个失败响应，指示“23：不存在的保留ID”。
The Delete All Reservation message deletes all extant Reservation objects in the switch and frees the reserved switch resources of these reservations. The Reservation Request Message is:
Delete All Reservation消息删除交换机中所有现存的保留对象，并释放这些保留的保留交换机资源。预订请求消息为：
Message Type = 72
消息类型=72
The Delete All Reservation 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Port Management message allows a port to be brought into service, to be taken out of service, to be set to loop back, reset, or to change the transmit data rate. 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. The Port Management message MAY also be used for enabling the replace connection mechanism. The Port Management message is also used as part of the Event Message flow control mechanism.
端口管理消息允许端口投入使用、停止使用、设置回圈、重置或更改传输数据速率。只有启动和重置输入端口功能可以更改输入端口上的连接状态（已建立的连接）。只有“打开”功能可以更改端口会话号的值。端口管理消息也可用于启用替换连接机制。端口管理消息还用作事件消息流控制机制的一部分。
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Event Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|R|x|x|x|x|x|x|x| Duration | Function |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Event Flags | Flow Control Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transmit Data 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Event Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|R|x|x|x|x|x|x|x| Duration | Function |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Event Flags | Flow Control Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transmit Data Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Note: Fields and Parameters that have been explained in the description of the general messages will not be explained in this section. Please refer to section 3.1 for details.
注意：本节将不解释在一般消息说明中已解释的字段和参数。详情请参考第3.1节。
Event Sequence Number 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 initialised. 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.
事件序列号成功响应消息给出端口字段指示的交换机端口的事件序列号的当前值。初始化端口时，事件序列号设置为零。每当端口检测到交换机通常通过事件消息报告的异步事件时，该值将递增一。如果成功响应中的事件序列号与该端口最近接收的事件消息的事件序列号不同，则表示发生了未通过事件消息报告的事件。这很可能是由于流控制限制了交换机可以为每个端口发送事件消息的速率。在请求消息中不使用此字段。
R: Connection Replace The R flag shall only be checked when the Function field = 1 (Bring Up). If the R flag is set in the Port Management request message, it indicates that a switch controller requests the switch port to support the Connection Replace mechanism.
R：连接替换仅当功能字段=1（打开）时，才应检查R标志。如果在端口管理请求消息中设置了R标志，则表示交换机控制器请求交换机端口支持连接替换机制。
Connection Replace behaviour is described in chapter 4.2. If a switch does not support the Connection Replace mechanism, it MUST reply with the failure response: "45: Connection Replace mechanism not supported on switch" and reset the R-flag. Upon successful response, the R flag SHOULD remain set in the response message.
第4.2章描述了连接更换行为。如果交换机不支持连接替换机制，则必须以故障响应“45：交换机不支持连接替换机制”进行回复，并重置R标志。成功响应后，R标志应在响应消息中保持设置。
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 connections that originate at the specified input port MUST be deleted and a new Port Session Number MUST be selected, preferably using some form of random number. On completion of the operation all dynamically assigned Label values for the specified input port MUST be unassigned, i.e., no connections will be established in the Label space that GSMP controls on this input port. Afterwards, the Port Status of the port will be Available.
打开：函数=1。使港口投入使用。必须删除源自指定输入端口的所有连接，并且必须选择新的端口会话号，最好使用某种形式的随机数。操作完成后，必须取消指定输入端口的所有动态分配的标签值，即GSMP在此输入端口上控制的标签空间中不会建立任何连接。之后，端口的端口状态将可用。
Take Down: Function = 2. Take the port out of service. Any data received at this port will be discarded. No data will be transmitted from this port. Afterwards, the Port Status of the port will be Unavailable.
取下：函数=2。使港口停止使用。在此端口接收的任何数据都将被丢弃。此端口不会传输任何数据。之后，端口的端口状态将不可用。
The behaviour 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 behaviour would be for the switch either to ignore the message or to terminate the current GSMP session and to initiate another session,
如果控制交换机的GSMP会话正在该端口上运行，则该行为未定义。（在这种情况下，交换机最可能的行为是忽略消息或终止当前GSMP会话并启动另一个会话，
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正在运行的链路的正确方法是在邻接协议中发出RSTACK消息。
Internal Loopback: Function = 3. Data 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 functions of the input port above the physical layer, e.g., header translation, are performed upon the looped back data. Afterwards, the Port Status of the port will be Internal Loopback.
内部环回：函数=3。从交换结构到达输出端口的数据将循环通过输入端口返回到交换结构。物理层上方输入端口的所有功能（例如，报头转换）都是在环回数据上执行的。之后，端口的端口状态将为内部环回。
External Loopback: Function = 4. Data 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 functions of the input port, above the physical layer are performed upon the looped back data. Afterwards, the Port Status of the port will be External Loopback.
External Loopback: Function = 4. Data 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 functions of the input port, above the physical layer are performed upon the looped back data. Afterwards, the Port Status of the port will be External Loopback.translate error, please retry
Bothway Loopback: Function = 5. Both internal and external loopbacks are performed. Afterwards, the Port Status of the port will be Bothway Loopback.
双向环回：函数=5。执行内部和外部环回。之后，端口的端口状态将为双向环回。
Reset Input Port: Function = 6. All connections that originate at the specified input port MUST be deleted and the input and output port hardware re-initialised. On completion of the operation, all dynamically assigned Label values for the specified input port MUST be unassigned, i.e., no connections will be established in the Label space that GSMP controls on this input port. The range of labels that may be controlled by GSMP on this port will be set to the default values specified in the Port Configuration message. The transmit data 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. Afterwards, the Port Status of the port will be Unavailable.
重置输入端口：功能=6。必须删除源自指定输入端口的所有连接，并重新初始化输入和输出端口硬件。操作完成后，必须取消指定输入端口的所有动态分配的标签值，即GSMP在此输入端口上控制的标签空间中不会建立任何连接。GSMP可在此端口上控制的标签范围将设置为端口配置消息中指定的默认值。输出端口的传输数据速率必须设置为其默认值。重置输入端口功能不会更改端口会话号。之后，端口的端口状态将不可用。
Reset Flags: Function = 7. This function is used to reset the Event Flags and Flow Control Flags. For each bit that is set in the Event Flags field, the corresponding Event Flag in the switch port MUST be reset to 0. For each bit that is set in the Flow Control Flags field, the corresponding Flow Control Flag in the switch port MUST be toggled; i.e., flow control
重置标志：函数=7。此函数用于重置事件标志和流控制标志。对于在事件标志字段中设置的每个位，交换机端口中相应的事件标志必须重置为0。对于流量控制标志字段中设置的每个位，必须切换交换机端口中相应的流量控制标志；i、 例如，流量控制
for the corresponding event is turned off if is currently on and it is turned on if it is currently off. The Port Status of the port is not changed by this function.
对于，如果当前处于打开状态，则相应事件将关闭；如果当前处于关闭状态，则相应事件将打开。此功能不会更改端口的端口状态。
Set Transmit Data Rate: Function = 8. Sets the transmit data rate of the output port as close as possible to the rate specified in the Transmit Data Rate field. In the success response message, the Transmit Data Rate MUST indicate the actual transmit data rate of the output port. If the transmit data rate of the requested output port cannot be changed a failure response MUST be returned with the Code field indicating: "43: The transmit data rate of this output port cannot be changed". If the transmit data rate of the requested output port can be changed, but the value of the Transmit Data Rate field is beyond the range of acceptable values, a failure response MUST be returned with the Code field indicating: "44: Requested transmit data rate out of range for this output port". In the failure response message, the Transmit Data Rate MUST contain the same value as contained in the request message that caused the failure. The transmit data 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。将输出端口的传输数据速率设置为尽可能接近传输数据速率字段中指定的速率。在成功响应消息中，传输数据速率必须指示输出端口的实际传输数据速率。如果无法更改请求输出端口的传输数据速率，则必须返回故障响应，代码字段指示：“43：此输出端口的传输数据速率无法更改”。如果请求的输出端口的传输数据速率可以更改，但传输数据速率字段的值超出可接受值的范围，则必须返回故障响应，代码字段指示：“44：请求的传输数据速率超出此输出端口的范围”。在故障响应消息中，传输数据速率必须包含与导致故障的请求消息中包含的值相同的值。输出端口的传输数据速率不会因上带、取下或任何环回功能而改变。重置输入端口功能会将其返回到默认值。
Transmit Data Rate This field is only used in request and success response messages with the Function field set to "Set Transmit Data Rate". It is used to set the output data rate of the output port. It is specified in cells/s and bytes/s. If the Transmit Data Rate field contains the value 0xFFFFFFFF the transmit data rate of the output port SHOULD be set to the highest valid value.
传输数据速率此字段仅用于功能字段设置为“设置传输数据速率”的请求和成功响应消息中。用于设置输出端口的输出数据速率。它以单元格/秒和字节/秒为单位指定。如果传输数据速率字段包含值0xFFFFFFFF，则输出端口的传输数据速率应设置为最高有效值。
Event Flags Field in the request message that 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. Depending on the setting in the Flow Control Flag, a port is either subject to flow control or not. If it is subject to flow control, then it is not permitted to send another Event message of the same type before the Event Flag has been reset. To reset an event flag, the Function field in the request message is set to "Reset 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 messages and the bits of the Event Flags field is as follows:
事件消息类型与事件标志字段位之间的对应关系如下：
1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|U|D|I|N|Z|A|x|x|x|x|x|x|x|x|x|x|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|U|D|I|N|Z|A|x|x|x|x|x|x|x|x|x|x|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
U: Port Up Bit 0, (most significant bit) D: Port Down Bit 1, I: Invalid Label Bit 2, N: New Port Bit 3, Z: Dead Port Bit 4, A: Adjacency Event Bit 5, x: Unused Bits 6-15.
U:端口上升位0，（最高有效位）D:端口下降位1，I:无效标签位2，N:新端口位3，Z:无效端口位4，A:邻接事件位5，x:未使用位6-15。
Flow Control Flags Field The flags in this field are used to indicate whether the flow control mechanism described in the Events Flag field is turned on or not. If the Flow Control Flag is set, then the flow control mechanism for that event on that port is activated. To toggle the flow control mechanism, the Function field in the request message is set to "Reset Flags". When doing a reset, for each flag that is set in the Flow Control Flags field, the corresponding flow control mechanism MUST be toggled.
流量控制标志字段此字段中的标志用于指示事件标志字段中描述的流量控制机制是否已打开。如果设置了流量控制标志，则会激活该端口上该事件的流量控制机制。要切换流量控制机制，请将请求消息中的功能字段设置为“重置标志”。进行重置时，对于在流量控制标志字段中设置的每个标志，必须切换相应的流量控制机制。
The Flow Control Flags correspond to the same event definitions as defined for the Event Flag.
流控制标志对应于为事件标志定义的相同事件定义。
The default label range, Min Label to Max Label, is specified for each port by the Port Configuration or the All Ports Configuration messages. When the protocol is initialised, 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 labels supported by 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:
“端口配置”或“所有端口配置”消息为每个端口指定了默认标签范围“最小标签到最大标签”。协议初始化时，在传输任何标签范围消息之前，每个端口的标签范围将设置为默认标签范围。（默认标签范围取决于交换机设计和配置，GSMP协议未指定。）标签范围消息允许更改指定端口支持的标签范围。每个交换机端口必须声明它是支持端口配置中的标签范围消息还是支持所有端口配置消息。标签范围消息为：
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Q|M|D|x| Range Count | Range Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Label Range Block ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Q|M|D|x| Range Count | Range Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Label Range Block ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Note: Fields and Parameters that have been explained in the description of the general messages will not be explained in this section. Please refer to section 3.1 for details.
注意：本节将不解释在一般消息说明中已解释的字段和参数。详情请参考第3.1节。
Each element of the Label Range Block has the following format:
标签范围块的每个元素具有以下格式：
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|V|C| |
+-+-+-+-+ Min Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|x|x| |
+-+-+-+-+ Max Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Remaining Labels |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|V|C| |
+-+-+-+-+ Min Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|x|x| |
+-+-+-+-+ Max Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Remaining Labels |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Flags
旗帜
Q: Query If the Query flag is set in a request message, the switch MUST respond with the current range of valid labels. 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如果在请求消息中设置了查询标志，则交换机必须使用当前有效标签范围进行响应。设置了查询标志的请求消息不会更改当前标签范围。如果查询标志为零，则消息将请求标签更改操作。
M: Multipoint Query If the Multipoint Query flag is set the switch MUST respond with the current range of valid specialized multipoint labels. The current label range is not changed by a request message with the Multipoint Query flag set.
M：多点查询如果设置了多点查询标志，则开关必须使用有效的专用多点标签的当前范围进行响应。设置了多点查询标志的请求消息不会更改当前标签范围。
D: Non-contiguous Label Range Indicator This flag will be set in a Query response if the labels available for assignment belong to a non-contiguous set.
D：非连续标签范围指示器如果可用于分配的标签属于非连续集合，则将在查询响应中设置此标志。
V: Label The Label flag use is port type specific.
V：标签标签标志使用的是端口类型特定的。
C: Multipoint Capable Indicates label range that can be used for multipoint connections.
C:Multipoint Capable表示可用于多点连接的标签范围。
Range Count Count of Label Range elements contained in the Label Range Block.
标签范围块中包含的标签范围元素的范围计数。
Range Length Byte count in the Label Range Block.
标签范围块中的范围长度字节计数。
Min Label The minimum label value in the range.
最小标签范围内的最小标签值。
Max Label The maximum label value in the range.
最大标签范围内的最大标签值。
Remaining Labels The maximum number of remaining labels that could be requested for allocation on the specified port.
剩余标签指定端口上可请求分配的最大剩余标签数。
The success response to a Label Range message requesting a change of label range is a copy of the request message with the Remaining Labels field updated to the new values after the Label Range operation.
对请求更改标签范围的标签范围消息的成功响应是请求消息的副本，其余标签字段在标签范围操作后更新为新值。
If the switch is unable to satisfy a request to change the Label range, it MUST return a failure response message with the Code field set to: "40: Cannot support one or more requested label ranges". In this failure response message, the switch MUST use the Min Label and Max Label fields to suggest a label range that it is able to satisfy.
如果交换机无法满足更改标签范围的请求，则必须返回故障响应消息，代码字段设置为：“40:无法支持一个或多个请求的标签范围”。在此故障响应消息中，交换机必须使用最小标签和最大标签字段来建议它能够满足的标签范围。
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, "4: One or more of the specified ports does not exist".
无论目标交换机端口的端口状态或线路状态如何，都可以发出标签范围请求消息。如果请求消息的端口字段包含无效端口（不存在的端口或已从交换机中删除的端口），则必须返回故障响应消息，并将代码字段设置为“4:一个或多个指定端口不存在”。
If the Query flag is set in the request message, the switch MUST reply with a success response message containing the current range of valid labels that are supported by the port. The Min Label and Max Label fields are not used in the request message.
如果在请求消息中设置了查询标志，则交换机必须返回一条成功响应消息，其中包含端口支持的有效标签的当前范围。请求消息中不使用最小标签和最大标签字段。
If the Multipoint Query flag is set in the request message and the switch does not support a range of valid multipoint labels, then the switch MUST reply with a failure response message with the Code field set to, "42: Specialised multipoint labels not supported". The Min Label and Max Label fields are not used in the Multipoint request message.
如果在请求消息中设置了多点查询标志，并且交换机不支持一系列有效的多点标签，则交换机必须回复一条故障响应消息，代码字段设置为“42：不支持专用多点标签”。在多点请求消息中不使用最小标签和最大标签字段。
If a label range changes and there are extant connection states with labels used by the previous label range, a success response message MUST be returned with the Code field set to, "46: One or more labels are still used in the previous Label Range". This action indicates that the label range has successfully changed but with a warning that there are extant connection states for the previous label range.
如果标签范围发生更改，并且存在与前一标签范围使用的标签的现有连接状态，则必须返回成功响应消息，并将代码字段设置为“46:前一标签范围中仍使用一个或多个标签”。此操作表示标签范围已成功更改，但警告上一标签范围存在现有连接状态。
If the Label Type = ATM Label, the labels range message MUST be interpreted as an ATM Label as shown:
如果标签类型=ATM标签，则标签范围消息必须解释为ATM标签，如图所示：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|V|C| ATM Label (0x100) | Label Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|x|x| min VPI | min VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|x|x| ATM Label (0x100) | Label Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|x|x| max VPI | max VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Remaining VPI's | Remaining VCI's |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|V|C| ATM Label (0x100) | Label Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|x|x| min VPI | min VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|x|x| ATM Label (0x100) | Label Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|x|x| max VPI | max VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Remaining VPI's | Remaining VCI's |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
V: Label If the Label flag is set, the message refers to a range of VPI's only. The Min VCI and Max VCI fields are unused. If the Label flag is zero the message refers to a range of VCI's on either one VPI or on a range of VPI's.
V:Label如果设置了Label标志，则消息仅指VPI的范围。最小VCI和最大VCI字段未使用。如果标签标志为零，则消息表示一个VPI或一个VPI范围上的VCI范围。
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 Label 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”字段指定单个VPI，而“最小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字段的值，则请求的范围为单个VCI，其值等于最小VCI字段。零是一个有效值。（但是，VPI=0、VCI=0不可用作虚拟通道连接，因为它在ATM中用作特殊值以指示未分配的信元。）
Remaining VPI's, Remaining VCI's These fields are unused in the request message. In the success response message and in the failure response message these fields give the maximum number of remaining VPI's and VCI's 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 VPI's and VCI's 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 VPI's and VCI's is available to every switch port.
剩余的VPI、剩余的VCI这些字段在请求消息中未使用。在成功响应消息和失败响应消息中，这些字段给出了可请求在指定端口上分配的剩余VPI和VCI的最大数量（在成功响应的情况下，完成请求的操作后）。它让交换机控制器知道它可以请求多少VPI和VCI。给定的数字是给定交换机硬件约束条件下可能的最大值。这并不意味着每个交换机端口都可以使用这个数量的VPI和VCI。
If the Query flag and the Label flag are set in the request message, the switch MUST reply with a success response message containing the current range of valid VPI's that are supported by the port. The Min VPI and Max VPI fields are not used in the request message.
如果在请求消息中设置了查询标志和标签标志，则交换机必须回复一条成功响应消息，其中包含端口支持的有效VPI的当前范围。请求消息中不使用最小VPI和最大VPI字段。
If the Query flag is set and the Label flag is zero in the request message, the switch MUST reply with a success response message containing the current range of valid VCI's 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: "13: One or more of the specified Input Labels is invalid". The Min VPI field is not used in either the request or success response messages.
如果在请求消息中设置了查询标志且标签标志为零，则交换机必须回复一条成功响应消息，其中包含由Max VPI字段指定的VPI支持的有效VCI的当前范围。如果请求的VPI无效，则必须返回故障响应，指示：“13:一个或多个指定的输入标签无效”。请求或成功响应消息中均未使用Min VPI字段。
If the Query flag is zero and the Label flag is set in the request message, the Min VPI and Max VPI fields specify the new range of VPI's to be allocated to the input port specified by the Port field. The range of VPI's previously allocated to this port SHOULD be increased or decreased to the specified value.
如果查询标志为零，并且在请求消息中设置了标签标志，则最小VPI和最大VPI字段指定要分配给端口字段指定的输入端口的新VPI范围。以前分配给此端口的VPI范围应增加或减少到指定值。
If the Query flag and the Label flag are zero in the request message, the Min VCI and Max VCI fields specify the range of VCI's to be allocated to each of the VPI's specified by the VPI range. The range of VCI's previously allocated to each of the VPI's 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 VPI's within the specified VPI range.
如果请求消息中的查询标志和标签标志为零，则最小VCI和最大VCI字段指定要分配给VPI范围指定的每个VPI的VCI范围。在此端口上指定的VPI范围内，以前分配给每个VPI的VCI范围，应增加或减少到指定值。在指定的VPI范围内，每个VPI上分配的VCI范围必须相同。
If the switch is unable to satisfy a request to change the label range, it MUST return a failure response message with the Code field set to: "40: Cannot support one or more requested label ranges". If the switch is unable to satisfy a request to change the VPI, the switch MUST use the Min VPI and Max VPI fields to suggest a VPI range that it would be able to satisfy and set the VCI fields to zero, or if the switch is unable to satisfy a request to change the VCI range
如果交换机无法满足更改标签范围的请求，则必须返回故障响应消息，代码字段设置为：“40:无法支持一个或多个请求的标签范围”。如果交换机无法满足更改VPI的请求，则交换机必须使用最小VPI和最大VPI字段来建议其能够满足的VPI范围，并将VCI字段设置为零，或者如果交换机无法满足更改VCI范围的请求
on all VPI's within the requested VPI range, 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上，交换机必须使用Min VPI、Max VPI、Min VCI和Max 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 VPI's, the VCI range that can be supported is often more constrained. Often the Min VCI MUST be 0 or 32. Typically all VCI's 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 VPI's and a range of VCI's within each VPI, the most likely use is to change either the VPI range or the range of VCI's within a single VPI. It is possible for a VPI to be valid but to be allocated no valid VCI's. 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 VCI's.
虽然标签范围消息定义为指定每个VPI内的VPI范围和VCI范围，但最有可能的用途是更改单个VPI内的VPI范围或VCI范围。VPI可能有效，但没有分配有效的VCI。这种VPI可用于虚拟路径连接，但为了支持虚拟通道连接，需要为其分配一系列VCI。
If the Label Type = FR Label, the labels range message MUST be interpreted as Frame Relay Labels as shown:
如果标签类型=FR标签，则标签范围消息必须解释为帧中继标签，如图所示：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|V|C| FR Label (0x101) | Label Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|x|x| Res |Len| Min DLCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|x|x| FR Label (0x101) | Label Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|x|x| Res |Len| Max DLCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Remaining DLCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|V|C| FR Label (0x101) | Label Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|x|x| Res |Len| Min DLCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|x|x| FR Label (0x101) | Label Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|x|x| Res |Len| Max DLCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Remaining DLCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
V: Label The Label flag is not used.
V:标签-不使用标签标志。
Res The Res field is reserved in [21], i.e., it is not explicitly reserved by GSMP.
Res Res字段在[21]中保留，即GSMP未明确保留该字段。
Len The Len field specifies the number of bits of the DLCI. The following values are supported:
Len Len字段指定DLCI的位数。支持以下值：
Len DLCI bits 0 10 2 23
Len DLCI位0 10 2 23
Min DLCI, Max DLCI Specify a range of DLCI values, Min DLCI to Max DLCI inclusive. The values SHOULD be right justified in the 23-bit fields and the preceding bits SHOULD be set to zero. A single DLCI may be specified with a Min DLCI and a Max DLCI having the same value. In a request message, if the value of the Max DLCI field is less than or equal to the value of the Min DLCI field, the requested range is a single DLCI with a value equal to the Min DLCI field. Zero is a valid value.
最小DLCI，最大DLCI指定DLCI值的范围，包括最小DLCI到最大DLCI。23位字段中的值应右对齐，前面的位应设置为零。可以使用具有相同值的最小DLCI和最大DLCI指定单个DLCI。在请求消息中，如果最大DLCI字段的值小于或等于最小DLCI字段的值，则请求的范围为单个DLCI，其值等于最小DLCI字段。零是一个有效值。
Remaining DLCI's This field is unused in the request message. In the success response message and in the failure response message, this field gives the maximum number of remaining DLCI's 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 DLCI's 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 DLCI's is available to every switch port.
请求消息中未使用剩余DLCI的此字段。在成功响应消息和失败响应消息中，此字段提供可请求在指定端口上分配的最大剩余DLCI数（在成功响应的情况下，完成请求的操作后）。它让交换机控制器知道它可以请求多少个DLCI。给定的数字是给定交换机硬件约束条件下可能的最大值。这并不意味着每个交换机端口都可以使用此数量的DLCI。
The Label Range Block for PortTypes using MPLS labels. These types of labels are for use on links for which label values are independent of the underlying link technology. Examples of such links are PPP and Ethernet. On such links the labels are carried in MPLS label stacks [14]. If Label Type = MPLS Gen Label, the labels range message MUST be interpreted as MPLS Generic Label as shown:
使用MPLS标签的端口类型的标签范围块。这些类型的标签用于标签值独立于基础链接技术的链接。这种链路的例子有PPP和以太网。在这样的链路上，标签以MPLS标签栈的形式携带[14]。如果标签类型=MPLS Gen Label，则标签范围消息必须解释为MPLS通用标签，如图所示：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|V|C| MPLS Gen Label (0x102)| Label Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|x|x|x|x|x|x|x|x|x|x| Min MPLS Label |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|x|x| MPLS Gen Label (0x102)| Label Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|x|x|x|x|x|x|x|x|x|x| Max MPLS Label |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Remaining Labels |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|V|C| MPLS Gen Label (0x102)| Label Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|x|x|x|x|x|x|x|x|x|x| Min MPLS Label |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|x|x| MPLS Gen Label (0x102)| Label Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|x|x|x|x|x|x|x|x|x|x| Max MPLS Label |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Remaining Labels |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
V: Label The Label flag is not used.
V:标签-不使用标签标志。
Min MPLS Label, Max MPLS Label Specify a range of MPLS label values, Min MPLS Label to Max MPLS Label inclusive. The Max and Min MPLS label fields are 20 bits each.
最小MPLS标签，最大MPLS标签指定一系列MPLS标签值，包括最小MPLS标签到最大MPLS标签。最大和最小MPLS标签字段各为20位。
Remaining MPLS Labels This field is unused in the request message. In the success response message and in the failure response message this field gives the maximum number of remaining MPLS Labels 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 MPLS Labels 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 Labels is available to every switch port.
剩余的MPLS标签此字段在请求消息中未使用。在成功响应消息和失败响应消息中，此字段给出可请求在指定端口上分配的最大剩余MPLS标签数（在成功响应的情况下，完成请求的操作后）。它让交换机控制器知道可以请求多少MPLS标签。给定的数字是给定交换机硬件约束条件下可能的最大值。这并不意味着每个交换机端口都可以使用这个数量的标签。
The Label Range message is not used for FEC Labels and is for further study.
标签范围消息不用于FEC标签，用于进一步研究。
The state and statistics messages permit the controller to request the values of various hardware counters associated with the switch input and output ports and connections. 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 connections have recently been carrying traffic. The Statistics message is used to query the various port and connection traffic and error counters.
更具体的连接最近正在承载流量。统计信息用于查询各种端口和连接流量以及错误计数器。
The Report Connection State message is used to request an input port to report the connection state for a single connection, a single ATM virtual path connection, or for the entire input port.
报告连接状态消息用于请求输入端口报告单个连接、单个ATM虚拟路径连接或整个输入端口的连接状态。
The Connection Activity message is used to determine whether one or more specific 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 connection. Each connection is specified by its input port and Input Label which are specified in the Input Port and Input Label 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 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:
支持两种形式的活动检测。如果交换机支持每连接流量计费，则必须返回每个指定连接的流量计数器的当前值。未指定计数的流量单位，但通常为单元或帧。控制器必须将消息中返回的流量计数与每个指定连接的先前值进行比较，以确定每个连接在中间期间是否处于活动状态。如果交换机不支持每连接流量计费，但能够通过一些其他未指定的方式检测每连接活动，则可以使用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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number of Records |x x x x x x x x x x x x x x x x|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number of Records |x x x x x x x x x x x x x x x x|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Activity Records ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Note: Fields and Parameters that have been explained in the description of the general messages will not be explained in this section. Please refer to section 3.1 for details.
注意：本节将不解释在一般消息说明中已解释的字段和参数。详情请参考第3.1节。
Number of Records Field specifies the number of Activity Records to follow. The number of 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:
每个活动记录的格式如下：
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|V|C|A|x| TC Count | TC Block Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Traffic Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| |
+-+-+-+-+ Input Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|V|C|A|x| TC Count | TC Block Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Traffic Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| |
+-+-+-+-+ Input Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 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标志用于指示无效的活动记录。如果此活动记录中的任何字段无效、输入端口字段指定的输入端口不存在或指定的连接不存在，则该标志必须为零。如果成功响应消息中的有效记录标志为零，则计数器标志、活动标志和流量计数字段未定义。如果设置了有效记录标志，则活动记录有效，计数器和活动标志有效。请求消息中未使用有效记录标志。
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 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：计数器在成功响应消息中，如果设置了有效记录标志，计数器标志（如果为零）表示流量计数字段中的值有效。如果设置，则表示活动标志中的值有效。请求消息中未使用计数器标志。
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：成功响应消息中的活动，如果设置了有效记录和计数器标志，则活动标志（如果设置）表示自上次此连接的连接活动消息以来，此连接上已存在一些活动。如果为零，则表示自上次发送此连接的连接活动消息以来，此连接上没有任何活动。请求消息中未使用活动标志。
TC Count In cases where per connection traffic counting is supported, this field contains the count of Traffic Count entries.
TC计数在支持每连接流量计数的情况下，此字段包含流量计数条目的计数。
TC Block Length In cases where per connection traffic counting is supported, this field contains the Traffic Count block size in bytes.
TC块长度在支持每连接流量计数的情况下，此字段包含以字节为单位的流量计数块大小。
Input Port Identifies the port number of the input port on which the connection of interest originates 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 Label Fields identify the specific connection for which statistics are being requested.
输入标签字段标识请求统计信息的特定连接。
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 Connection Activity records returned in the message. If the switch is incapable of detecting per connection activity, a failure response MUST be returned indicating, "3: The specified request is not implemented on this switch".
故障响应的格式与请求消息相同，记录数字段设置为零，消息中未返回连接活动记录。如果交换机无法检测每个连接活动，则必须返回故障响应，指示“3：指定的请求未在此交换机上实现”。
The Statistics messages are used to query the various port, connection and error counters.
统计信息用于查询各种端口、连接和错误计数器。
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| |
+-+-+-+-+ Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| |
+-+-+-+-+ Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Note: Fields and Parameters that have been explained in the description of the general messages will not be explained in this section. Please refer to section 3.1 for details.
注意：本节将不解释在一般消息说明中已解释的字段和参数。详情请参考第3.1节。
Label The Label Fields identifies the specific connection for which statistics are being requested.
标签标签字段标识请求统计信息的特定连接。
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| |
+-+-+-+-+ Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Input Cell Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Input Frame Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Input Cell Discard Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Input Frame Discard Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Header Checksum Error Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Input Invalid Label 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| |
+-+-+-+-+ Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Input Cell Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Input Frame Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Input Cell Discard Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Input Frame Discard Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Header Checksum Error Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Input Invalid Label Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Output Cell Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Output Frame Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Output Cell Discard Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Output Frame Discard Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Output Cell Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Output Frame Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Output Cell Discard Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ Output Frame Discard Count +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Note: Field and Parameters that have been explained in the description of the general messages will not be explained in this section. Please refer to section 3.1 for details.
注：本节将不解释在一般信息说明中已解释的字段和参数。详情请参考第3.1节。
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. These fields are relevant for label type = ATM, for all other label types these fields SHOULD be set to zero by the sender and ignored by the receiver.
输入单元计数、输出单元计数给出自由运行的64位计数器的值，分别对到达输入或离开输出的单元进行计数。这些字段与label type=ATM相关，对于所有其他标签类型，发送方应将这些字段设置为零，接收方应忽略这些字段。
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. These fields are relevant for label types = FR and MPLS, for all other label types these fields SHOULD be set to zero by the sender and ignored by the receiver.
输入帧计数、输出帧计数给出自由运行的64位计数器的值，分别对到达输入或离开输出的帧（数据包）进行计数。这些字段与标签类型=FR和MPLS相关，对于所有其他标签类型，发送方应将这些字段设置为零，接收方应忽略这些字段。
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. These fields are relevant for label type = ATM, for all other label types these fields SHOULD be set to zero by the sender and ignored by the receiver.
Input Cell Discard Count、Output Cell Discard Count给出自由运行的64位计数器的值，该计数器分别对输入端口或输出端口上由于队列溢出而丢弃的单元进行计数。这些字段与label type=ATM相关，对于所有其他标签类型，发送方应将这些字段设置为零，接收方应忽略这些字段。
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. These fields are relevant for label
Input Frame Discard Count、Output Frame Discard Count分别给出自由运行的64位计数器的值，该计数器对因输入端口或输出端口拥塞而丢弃的帧进行计数。这些字段与标签相关
types = FR and MPLS, for all other label types these fields SHOULD be set to zero by the sender and ignored by the receiver.
类型=FR和MPLS，对于所有其他标签类型，发送方应将这些字段设置为零，接收方应忽略这些字段。
Header Checksum Error Count Gives the value of a free running 64-bit counter counting cells or frames discarded due to header checksum errors on arrival at an input port. For an ATM switch this would be the HEC count.
Header Checksum Error Count给出自由运行的64位计数器的值，该计数器对到达输入端口时由于Header Checksum错误而丢弃的单元或帧进行计数。对于ATM交换机，这将是HEC计数。
Invalid Label Count Gives the value of a free running 64-bit counter counting cells or frames discarded because their Label is invalid on arrival at an input port.
Invalid Label Count给出自由运行的64位计数器的值，该计数器对由于到达输入端口时标签无效而丢弃的单元或帧进行计数。
The Port Statistics message requests the statistics for the switch port specified in the Port field. The contents of the Label field in the Port Statistics request message is ignored. All of the count fields in the success response message refer to per-port counts regardless of the connection to which the cells or frames 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消息请求端口字段中指定的交换机端口的统计信息。忽略端口统计信息请求消息中标签字段的内容。成功响应消息中的所有计数字段均指每个端口的计数，而与单元或帧所属的连接无关。端口不支持的成功响应消息中的任何计数字段必须设置为零。端口统计信息为：
Message Type = 49
消息类型=49
The Connection Statistics message requests the statistics for the connection specified in the Label field that originates on the switch input port specified in the Port field. All of the count fields in the success response message refer only to the specified connection. The Header Checksum Error Count and Invalid Label 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消息请求标签字段中指定的连接的统计信息，该连接源自端口字段中指定的交换机输入端口。成功响应消息中的所有计数字段仅引用指定的连接。标头校验和错误计数和无效标签计数字段不是特定于连接的，必须设置为零。在成功响应消息中，每个连接都不支持的任何其他计数字段必须设置为零。连接统计信息为：
Message Type = 50
消息类型=50
The QoS Class Statistics message is not supported in this version of GSMP.
此版本的GSMP不支持QoS类统计信息消息。
Message Type = 51 is reserved.
保留消息类型=51。
The Report Connection State message is used to request an input port to report the connection state for a single 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|A|V| |
+-+-+-+-+ Input Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|A|V| |
+-+-+-+-+ Input Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Note: Field and Parameters that have been explained in the description of the general messages will not be explained in this section. Please refer to section 3.1 for details.
注：本节将不解释在一般信息说明中已解释的字段和参数。详情请参考第3.1节。
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 connections that originate at the input port specified by the Input Port field. In this case the Input Label field and the Label flag are unused.
A:All Connections如果设置了All Connections标志，则消息将请求源自输入端口字段指定的输入端口的所有连接的连接状态。在这种情况下，输入标签字段和标签标志未使用。
V: ATM VPI The ATM VPI flag may only be set for ports with PortType=ATM. If the switch receives a Report Connection State message in which the ATM VPI flag set and in which the input port specified by the Input Port field does not have PortType=ATM, the switch MUST return a Failure response "28: ATM Virtual Path switching is not supported on non-ATM ports".
V:ATM VPI ATM VPI标志只能为PortType=ATM的端口设置。如果交换机收到报告连接状态消息，其中设置了ATM VPI标志，并且输入端口字段指定的输入端口没有PortType=ATM，则交换机必须返回故障响应“28：非ATM端口不支持ATM虚拟路径交换”。
If the All Connections flag is zero and the ATM VPI flag is also zero, the message requests the connection state for the connection that originates at the input port specified by the Port and Input Label fields.
如果All Connections标志为零且ATM VPI标志也为零，则消息将请求在端口和输入标签字段指定的输入端口处发起的连接的连接状态。
ATM specific procedures: If the All Connections flag is zero and the ATM VPI flag is set and the input port specified by the Input Port field has LabelType=ATM, the message requests the connection state for the virtual path connection that originates at the input port specified by the Input Port and Input VPI fields. If the specified Input VPI identifies an ATM 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.
ATM特定过程：如果所有连接标志为零，并且设置了ATM VPI标志，并且输入端口字段指定的输入端口具有LabelType=ATM，则消息将请求虚拟路径连接的连接状态，该连接起源于输入端口和输入VPI字段指定的输入端口。如果指定的输入VPI识别ATM虚拟路径连接（即单交换虚拟路径），则请求该连接的状态。如果指定的输入VPI标识包含虚拟通道连接的虚拟路径，则消息将请求属于指定虚拟路径的所有虚拟通道连接的连接状态。
Input Label Field identifies the specific connection for which the connection state is being requested. For requests that do not require a connection to be specified, the Input Label field is not used.
输入标签字段标识请求连接状态的特定连接。对于不需要指定连接的请求，不使用输入标签字段。
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Connection Records ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Note: Fields and Parameters that have been explained in the description of the general messages will not be explained in this section. Please refer to section 3.1 for details.
注意：本节将不解释在一般消息说明中已解释的字段和参数。详情请参考第3.1节。
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 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. "More" in the Result field of a response message indicates that one or more further success response messages should be expected in response to the same request message. "Success" in the Result field indicates that the response to the request has been completed. The Result values are defined in chapter 3.1.1.
对同一请求消息的响应必须具有与请求消息相同的输入端口和事务标识符字段。单个连接记录不能拆分为多个成功响应消息。响应消息的结果字段中的“更多”表示应期望一个或多个进一步的成功响应消息来响应同一请求消息。结果字段中的“成功”表示已完成对请求的响应。结果值在第3.1.1章中定义。
Each Connection Record has the following format:
每个连接记录的格式如下：
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|A|V|P| Record Count | Record Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| |
+-+-+-+-+ Input Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Output Branch Records ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|A|V|P| Record Count | Record Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| |
+-+-+-+-+ Input Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Output Branch Records ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Flags
旗帜
A: All Connections
A:所有连接
V: ATM VPI For the first Connection Record in each success response message, the All Connections and the ATM VPI 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.
V:ATM VPI对于每个成功响应消息中的第一个连接记录，所有连接和ATM VPI标志必须与请求消息的相同。对于同一成功响应消息中的连续连接记录，不使用这些标志。
P: ATM VPC The ATM VPC flag may only be set for ports with PortType=ATM. The ATM VPC flag, if set and only if set, indicates that the Connection Record refers to an ATM virtual path connection.
P:ATM VPC ATM VPC标志只能为PortType=ATM的端口设置。ATM VPC标志（如果设置且仅当设置）表示连接记录引用ATM虚拟路径连接。
Input Label The input label of the connection specified in this Connection Record.
Input Label此连接记录中指定的连接的输入标签。
Record Count Count of Output Branch Records included in a response message.
记录计数响应消息中包含的输出分支记录的计数。
Record Length Length in bytes of Output Branch Records field
记录长度输出分支记录字段的字节长度
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 Label field of the Connection Record and the Input Port field of the Report Connection State message. A point-to-point connection will require only a single Output Branch Record. A point-to-multipoint connection will require multiple Output Branch Records. 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.
输出分支记录每个连接记录必须包含一个或多个输出分支记录。每个输出分支记录指定属于连接记录的输入标签字段和报告连接状态消息的输入端口字段标识的连接的单个输出分支。点到点连接只需要一个输出分支记录。点对多点连接将需要多个输出分支记录。如果一个点对多点连接的输出分支多于包含在单个成功响应消息中的单个连接记录所能容纳的分支，则可以使用多个成功响应消息中的多个连接记录来报告该连接。
Each Output Branch Record has the following format:
每个输出分支记录具有以下格式：
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| |
+-+-+-+-+ Output Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| |
+-+-+-+-+ Output Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Output Port The output port of the switch to which this output branch is routed.
输出端口此输出分支路由到的交换机的输出端口。
Output Label The output label of the output branch specified in this Output Branch Record.
输出标签此输出分支记录中指定的输出分支的输出标签。
ATM specific procedures: If this Output Branch Record is part of a Connection Record that specifies a virtual path connection (the ATM VPC flag is set) the Output VCI field is unused.
ATM特定程序：如果此输出分支记录是指定虚拟路径连接的连接记录的一部分（设置了ATM 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, "10: General Message Failure". For the Report Connection State message, this failure code indicates that no
如果请求消息的输入端口有效，并且设置了All Connections（所有连接）标志，但该端口上未建立任何连接，则必须返回故障响应消息，并将代码字段设置为“10:常规消息故障”。对于报告连接状态消息，此故障代码表示没有
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 connection.
找到了与请求消息匹配的连接。如果请求消息的输入端口有效，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.
配置消息允许控制器发现交换机的功能。定义了三个配置请求消息：交换机、端口和所有端口。
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 switch configuration message.
端口字段未在交换机配置消息中使用。
The Switch Configuration 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MType | MType | MType | MType |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Firmware Version Number | Window Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Switch Type | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| Switch Name |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Max Reservations |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MType | MType | MType | MType |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Firmware Version Number | Window Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Switch Type | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| Switch Name |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Max Reservations |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Note: Fields and Parameters that have been explained in the description of the general messages will not be explained in this section. Please refer to section 3.1 for details.
注意：本节将不解释在一般消息说明中已解释的字段和参数。详情请参考第3.1节。
MType Represents an alternative QoS Configuration type. In the request message the requested MType is in the most significant (leftmost) MType byte; the other three MType bytes are unused. The reply message will either accept the MType request by including the requested MType in the leftmost MType field of the response message or it will reject the MType request by responding with MType=0, the default MType, in the first MType field. Optionally, in the case of a rejection, the switch reply can include up to 3 additional MType values, each of which indicates an available alternative QoS Configuration. A switch that supports only the default QoS Configuration always returns MType=0 in all four MType fields. MType negotiation is discussed in section 8.1.1.
MType表示另一种QoS配置类型。在请求消息中，请求的MType位于最高有效（最左侧）MType字节中；其他三个MType字节未使用。回复消息将通过在响应消息最左侧的MType字段中包含请求的MType来接受MType请求，或者通过在第一个MType字段中使用MType=0（默认MType）进行响应来拒绝MType请求。可选地，在拒绝的情况下，交换机应答可以包括多达3个附加的MType值，每个值都指示可用的替代QoS配置。仅支持默认QoS配置的交换机始终在所有四个MType字段中返回MType=0。第8.1.1节讨论了MType协商。
0 - Indicates use of the default GSMP model 1-200 - Reserved 201-255 - Experimental
0-表示使用默认GSMP型号1-200-保留201-255-实验性
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 organisation 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
开关名称在设备的操作上下文中唯一的48位数量。48位IEEE 802 MAC地址（如果可用）可用作交换机名称。最高有效24位
of the Switch Name MUST be an Organisationally Unique Identifier (OUI) that identifies the manufacturer of the switch.
交换机名称的名称必须是标识交换机制造商的组织唯一标识符（OUI）。
Max Reservations The maximum number of Reservations that the switch can support (see Chapter 5). A value of 0 indicates that the switch does not support Reservations.
Max Reservations交换机可以支持的最大保留数量（参见第5章）。值为0表示交换机不支持保留。
After adjacency between a controller and after a switch is first established the controller that opts to use a QoS Configuration model other then the default would send the Switch Configuration request including the requested QoS Configuration's MType value in the request message. This request MUST be sent before any connection messages are exchanged. If the switch can support the requested QoS configuration, then the switch includes the requested MType value in the response message as an indication that it accepts the request. If the switch cannot support the requested QoS Configuration, it replaces the MType value in the request message with that of the default QoS Configuration, i.e., MType=0.
在控制器之间邻接之后，以及在首先建立交换机之后，选择使用QoS配置模型的控制器将发送交换机配置请求，包括请求消息中请求的QoS配置的MType值。必须在交换任何连接消息之前发送此请求。如果交换机可以支持请求的QoS配置，则交换机在响应消息中包含请求的MType值，作为其接受请求的指示。如果交换机无法支持请求的QoS配置，它将用默认QoS配置的MType值替换请求消息中的MType值，即MType=0。
The switch configuration response messages may additionally include the MType values of up to three alternative QoS Configurations that the switch supports and that the controller may choose between.
交换机配置响应消息还可包括交换机支持且控制器可在其中选择的最多三种备选QoS配置的MType值。
The exchange continues until the controller sends a requested MType that the switch accepts or until it sends a connection request message. If the exchange ends without confirmation of an alternate switch model, then the default Mtype=0 is be used.
交换将继续，直到控制器发送交换机接受的请求MType，或者直到它发送连接请求消息。如果交换结束时未确认备用交换机型号，则使用默认的Mtype=0。
Once an MType has been established for the switch, it cannot be changed without full restart, that is the re-establishment of adjacency with the resetting of all connections.
一旦为交换机建立了MType，则在未完全重新启动（即通过重置所有连接重新建立邻接）的情况下，无法对其进行更改。
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Event Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Event Flags | Port Attribute Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PortType |S|x|x|x|x|x|x|x| Data Fields Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ PortType Specific Data ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x x x x x x x x x x x x x x x x| Number of Service Specs |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
| |
~ Service Specs List ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Event Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Event Flags | Port Attribute Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PortType |S|x|x|x|x|x|x|x| Data Fields Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ PortType Specific Data ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x x x x x x x x x x x x x x x x| Number of Service Specs |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
| |
~ Service Specs List ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Note: Fields and Parameters that have been explained in the description of the general messages will not be explained in this section. Please refer to section 3.1 for details.
注意：本节将不解释在一般消息说明中已解释的字段和参数。详情请参考第3.1节。
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位构造成对交换机硬件的物理结构（例如，物理插槽和端口）具有意义的子字段。此结构可以在物理插槽号和物理端口号字段中指示。
Event Sequence Number The Event Sequence Number is set to zero when the port is initialised. 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 is explained in section 9.
事件序列号端口初始化时，事件序列号设置为零。每当端口检测到交换机通常通过事件消息报告的异步事件时，该值将递增一。第9节解释了事件序列号。
Event Flags Event Flags in a switch port corresponds to a type of Event message.
事件标志交换机端口中的事件标志对应于一种类型的事件消息。
Port Attribute Flags Port Attribute Flags indicate specific behaviour of a switch port. The format of the Port Attribute Flags field is given below:
端口属性标志端口属性标志指示交换机端口的特定行为。端口属性标志字段的格式如下所示：
0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|R|x|x|x|x|x|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 6
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|R|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|x|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
R: Connection Replace flag If set, indicates that connections being established by an Add Branch message with a corresponding R-bit set will replace any previously established connection if a clash between the established output branch and the requested output branch occurs [see chapter 4.2].
R:Connection Replace（连接替换）标志（如果设置）表示，如果已建立的输出分支与请求的输出分支之间发生冲突，则由添加分支消息建立的连接（具有相应的R位集）将替换先前建立的任何连接[参见第4.2章]。
x: Unused.
x:没用过。
PortType
端口类型
1: PortType is ATM 2: PortType is FR 3: PortType is MPLS
1:端口类型为ATM 2:端口类型为FR 3:端口类型为MPLS
S: Service Model If set, indicates that Service Model data follows the PortSpecific port configuration data.
S：服务模型如果设置，则表示服务模型数据遵循端口特定的端口配置数据。
Data Fields Length The total length in bytes of the combined PortType Specific Data and Service Model Data fields. The length of each of these fields may be derived from the other data so the value of Data Fields Length serves primarily as a check and to assist parsing of the All Ports Configuration message success response.
Data Fields Length组合端口类型特定数据和服务模型数据字段的总长度（以字节为单位）。这些字段中的每个字段的长度可以从其他数据中派生，因此数据字段长度的值主要用作检查，并帮助解析所有端口配置消息成功响应。
PortType Specific Data This field contains the configuration data specific to the particular port type as specified by the PortType field. The field format and length also depends on the value of the PortType. PortType Specific Data is defined below.
PortType特定数据此字段包含PortType字段指定的特定端口类型的配置数据。字段格式和长度还取决于PortType的值。端口类型特定的数据定义如下。
Number of Service Specs Field contains the total number of Service Specs following in the remainder of the Port Configuration message response or Port Configuration Record.
Number of Service Specs（服务规格数）字段包含端口配置消息响应或端口配置记录其余部分中的服务规格总数。
Service Specs List The Service Specs correspond to the Input and Output Service selectors used in Connection Management and Reservation messages. Specifically they define the possible values used when the Service Selector (IQS or OQS) is set to 0b10 indicating the use of the default service specification model defined in Chapter 10.
服务规范列出与连接管理和保留消息中使用的输入和输出服务选择器相对应的服务规范。具体来说，它们定义了当服务选择器（IQS或OQS）设置为0b10时可能使用的值，表示使用第10章中定义的默认服务规范模型。
Service Spec The format of each service spec is given below:
服务规范每个服务规范的格式如下所示：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Service ID | Capability Set ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Service ID | Capability Set ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Each Service Spec identifies a Service supported by the switch together with the Capability Set ID that identifies the parameters of that instance of the Service. The Service Spec List may contain more than one Service Spec sharing the same Service ID. However, each Service Spec in the Service Specs List MUST be unique.
每个服务规范标识交换机支持的服务以及标识该服务实例参数的功能集ID。服务规范列表可能包含多个共享相同服务ID的服务规范。但是，服务规范列表中的每个服务规范必须是唯一的。
Service ID Field contains the Service ID of a Service supported on the port. Service ID values are defined as part of the Service definition in Chapter 9.6.
服务ID字段包含端口上支持的服务的服务ID。服务ID值定义为第9.6章服务定义的一部分。
Capability Set ID Field identifies a Capability Set ID of the Service specified by the Service ID that is supported on the port. Capability Set ID values are defined by the Switch in the Service Configuration response message (see Section 8.4). The switch MUST NOT return a {Service ID, Capability Set ID} pair that is not reported in a Service Configuration response message.
Capability Set ID字段标识由端口上支持的服务ID指定的服务的功能集ID。能力集ID值由服务配置响应消息中的交换机定义（见第8.4节）。交换机不得返回服务配置响应消息中未报告的{Service ID，Capability Set ID}对。
The length, format and semantics of the PortType Specific Data field in the Port Configuration message success response and in the Port Records of the All Port Configuration message success response all depend on the PortType value of the same message or record respectively. The specification of the PortType Specific Data field is given below. For each defined PortType value the Min and Max Label fields are given in the subsequent subsections.
端口配置消息成功响应中的PortType特定数据字段的长度、格式和语义以及所有端口配置消息成功响应的端口记录中的PortType特定数据字段的长度、格式和语义都分别取决于同一消息或记录的PortType值。PortType特定数据字段的规范如下所示。对于每个已定义的PortType值，最小和最大标签字段在后续小节中给出。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|P|M|L|R|Q| Label Range Count | Label Range Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Default Label Range Block ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Receive Data Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transmit Data Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Status | Line 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|P|M|L|R|Q| Label Range Count | Label Range Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Default Label Range Block ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Receive Data Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transmit Data Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Status | Line Type | Line Status | Priorities |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Physical Slot Number | Physical Port Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Note: Fields and Parameters that have been explained in the description of the general messages will not be explained in this section. Please refer to section 3.1 for details.
注意：本节将不解释在一般消息说明中已解释的字段和参数。详情请参考第3.1节。
Where each of the ranges in the Default Label Range Blocks will have the following format:
其中，默认标签范围块中的每个范围将采用以下格式：
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|V|C| |
+-+-+-+-+ Min Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|x|x| |
+-+-+-+-+ Max Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|V|C| |
+-+-+-+-+ Min Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|x|x| |
+-+-+-+-+ Max Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Flags
旗帜
P: VP Switching The ATM VPC flag may only be set for ports with PortType=ATM. 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.
P:VP交换ATM VPC标志只能为PortType=ATM的端口设置。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 each output branch of a point-to-multipoint tree with a different label.
M：多播标签多播标签标志（如果设置）表示此输出端口能够使用不同的标签标记点对多点树的每个输出分支。如果为零，则表示此输出端口无法使用不同的标签标记点对多点树的每个输出分支。
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 label range and therefore accepts the Label Range message. Else, if zero, it indicates that this port does not accept Label Range messages.
R：标签范围标签范围标志（如果设置）表示此交换机端口能够重新分配其标签范围，因此接受标签范围消息。否则，如果为零，则表示此端口不接受标签范围消息。
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节中定义的服务质量消息。否则，如果为零，则表示此端口不接受服务质量消息。
V: Label The Label flag is port type specific.
V:Label标签标志特定于端口类型。
C: Multipoint Capable This flag indicates that the label range may be used for multipoint connections.
C:多点功能此标志表示标签范围可用于多点连接。
Label Range Count The total number of Default Label Range elements contained in the Default Label Range Block.
标签范围计数默认标签范围块中包含的默认标签范围元素总数。
Label Range Length Byte count in the Default Label Range Block.
默认标签范围块中的标签范围长度字节计数。
Min Label The specification of the Min Label field for each defined PortType value is given in the subsequent subsections. The default minimum value of a dynamically assigned incoming label 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 Label每个定义的端口类型值的Min Label字段的规格在后面的小节中给出。输入端口上的连接表支持的动态分配的传入标签的默认最小值，可由GSMP控制。此值不会因标签范围消息而更改。
Max Label The specification of the Max Label field for each defined PortType value is given in the subsequent subsections. The default maximum value of a dynamically assigned incoming label 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 Label每个定义的端口类型值的Max Label字段的规格在后面的小节中给出。输入端口上的连接表支持的动态分配的传入标签的默认最大值，可由GSMP控制。此值不会因标签范围消息而更改。
Receive Data Rate
接收数据速率
The maximum rate of data that may arrive at the input port in;
中可能到达输入端口的最大数据速率；
cells/s for PortType = ATM
bytes/s for PortType = FR
bytes/s for PortType = MPLS
cells/s for PortType = ATM
bytes/s for PortType = FR
bytes/s for PortType = MPLS
Transmit Data Rate
传输数据速率
The maximum rate of data that may depart from the output port in;
中可能离开输出端口的最大数据速率；
cells/s for PortType = ATM
bytes/s for PortType = FR
bytes/s for PortType = MPLS
cells/s for PortType = ATM
bytes/s for PortType = FR
bytes/s for PortType = MPLS
(The transmit data rate of the output port may be changed by the Set Transmit Data 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 or frames. When a port changes to the Available state from any other administrative state, all dynamically assigned 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 or frames will be transmitted from this port. No cells or frames will be received by this port.
不可用：端口状态=2。该港口已被故意停用。此端口不会传输任何小区或帧。此端口不会接收任何单元格或帧。
Internal Loopback: Port Status = 3. The port has intentionally been taken out of service and is in internal loopback: cells or frames 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 functions of the input port above the physical layer, e.g., header translation, are performed upon the looped back cells or frames.
内部环回：端口状态=3。端口已被故意停止服务并处于内部环回中：从交换机结构到达输出端口的单元或帧被循环到输入端口以返回交换机结构。物理层之上的输入端口的所有功能，例如，报头转换，都在环回单元或帧上执行。
External Loopback: Port Status = 4. The port has intentionally been taken out of service and is in external loopback: cells or frames 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 functions of the input port above the physical layer are performed upon the looped back cells or frames.
外部环回：端口状态=4。该端口已故意停止服务并处于外部环回中：从外部通信链路到达输入端口的单元或帧将立即环回物理层的通信链路，而不进入输入端口。物理层上的输入端口的任何功能都不会在环回单元或帧上执行。
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 initialisation is not defined by GSMP.
控制交换机的GSMP会话正在其上运行的端口的端口状态必须声明为可用。控制器将忽略此端口的任何其他端口状态。GSMP未定义通电初始化后交换机端口的端口状态。
Line Type The type of physical transmission interface for this port. The values for this field are defined by the IANAifType's specified in [17].
Line Type此端口的物理传输接口类型。此字段的值由[17]中指定的IANAifType定义。
The following values are identified for use in this version of the protocol.
本版本协议中使用的下列值已确定。
PortType = Unknown: other(1)
PortType = MPLS: ethernetCsmacd(6),
ppp(23)
PortType = ATM: atm(37)
PortType = FR: frameRelayService(44)
PortType = Unknown: other(1)
PortType = MPLS: ethernetCsmacd(6),
ppp(23)
PortType = ATM: atm(37)
PortType = FR: frameRelayService(44)
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. 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 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 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, a cell or frame on a connection with a higher priority is much more likely to exit the switch before a cell or frame on a connection with a lower priority if they are both in the switch at the same time.
优先级此输出端口可以分配给连接的不同优先级的数量。零在此字段中无效。如果输出端口能够支持“Q”优先级，则最高优先级编号为零，最低优先级编号为“Q-1”。根据不同连接的优先级向其提供不同服务质量的能力被认为是交换机输出端口的特性。可以假设，对于共享相同输出端口的连接，如果具有较高优先级的连接上的小区或帧同时位于交换机中，则在具有较低优先级的连接上的小区或帧之前，具有较高优先级的连接上的小区或帧更有可能退出交换机。
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 the 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位端口号的物理解释。
If PortType=ATM, the Default Label Range Block has the following format:
如果PortType=ATM，默认标签范围块的格式如下：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|V|x| ATM Label (0x100) | Label Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x x x x| 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|V|x| ATM Label (0x100) | Label Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x x x x| VPI | VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
V: Label If the Label flag is set, the message refers to a range of VPI's only. The Min VCI and Max VCI fields are unused. If the Label flag is zero the message refers to a range of VCI's on either one VPI or on a range of VPI's.
V:Label如果设置了Label标志，则消息仅指VPI的范围。最小VCI和最大VCI字段未使用。如果标签标志为零，则消息表示一个VPI或一个VPI范围上的VCI范围。
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.
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.
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's 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至最大VPI范围内的所有VPI值，GSMP必须能够控制该范围内的所有值。应该注意的是，最小VPI到最大VPI的范围仅指关联端口可以支持的传入VPI范围。对可能写入单元头的传出VPI的值没有限制。如果交换机不支持虚拟路径，则Min VPI和Max VPI都可以指定相同的值，很可能为零。
Use of the Label Range message allows the range of VPI's 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 a 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 a dynamically assigned incoming VCI that the connection table on the input port can support and may be controlled by GSMP.
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 VCI's that may be written into the cell header. Use of the Label Range message allows the range of VCI's 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.
通电时，硬件复位后，以及端口管理消息的复位输入端口功能后，输入端口必须处理最小VCI到最大VCI范围内的所有VCI值，对于最小VPI到最大VPI范围内的每个虚拟路径，GSMP必须能够控制此范围内的所有值。应注意，最小VCI到最大VCI范围仅指最小VPI到最大VPI范围内每个虚拟路径上的关联端口可支持的传入VCI范围。对可能写入单元头的传出VCI的值没有限制。使用标签范围消息可以更改端口支持的每个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 honour a connection request message that specifies the VCI value of the GSMP control channel even if it lies outside the range Min VCI to Max VCI
对于GSMP协议正在运行的端口，GSMP控制信道的VCI可能在最小VCI到最大VCI的范围内，也可能不在报告范围内。即使GSMP控制通道的VCI值超出最小VCI到最大VCI的范围，交换机也应遵守指定GSMP控制通道VCI值的连接请求消息
If PortType=FR, the Default Label Range Block has the following format:
如果PortType=FR，则默认标签范围块的格式如下：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| FR Label (0x101) | Label Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x x x x|Res|Len| DLCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| FR Label (0x101) | Label Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x x x x|Res|Len| DLCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Res The Res field is reserved in [21], i.e., it is not explicitly reserved by GSMP.
Res Res字段在[21]中保留，即GSMP未明确保留该字段。
Len This field specifies the number of bits of the DLCI. The following values are supported:
Len此字段指定DLCI的位数。支持以下值：
Len DLCI bits 0 10 2 23
Len DLCI位0 10 2 23
Min DLCI, Max DLCI Specify a range of DLCI values, Min DLCI to Max DLCI inclusive. The values SHOULD be right justified in the 23-bit fields and the preceding bits SHOULD be set to zero. A single DLCI may be specified with a Min DLCI and a Max DLCI having the same value. In a request message, if the value of the Max DLCI field is less than or equal to the value of the Min DLCI field, the requested range is a single DLCI with a value equal to the Min DLCI field. Zero is a valid value.
最小DLCI，最大DLCI指定DLCI值的范围，包括最小DLCI到最大DLCI。23位字段中的值应右对齐，前面的位应设置为零。可以使用具有相同值的最小DLCI和最大DLCI指定单个DLCI。在请求消息中，如果最大DLCI字段的值小于或等于最小DLCI字段的值，则请求的范围为单个DLCI，其值等于最小DLCI字段。零是一个有效值。
The Default Label Range Block for PortTypes using MPLS labels. These types of labels are for use on links for which label values are independent of the underlying link technology. Examples of such links are PPP and Ethernet. On such links the labels are carried in MPLS label stacks [14]. Ports of the Type MPLS have the following format:
使用MPLS标签的端口类型的默认标签范围块。这些类型的标签用于标签值独立于基础链接技术的链接。这种链路的例子有PPP和以太网。在这样的链路上，标签以MPLS标签栈的形式携带[14]。MPLS类型的端口具有以下格式：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|x|x| MPLS Gen Label (0x102)| Label Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|x|x|x|x|x|x|x|x|x|x| MPLS Label |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|x|x| MPLS Gen Label (0x102)| Label Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|x|x|x|x|x|x|x|x|x|x| MPLS Label |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Min MPLS Label, Max MPLS Label Specify a range of MPLS label values, Min MPLS Label to Max MPLS Label inclusive. The Max and Min MPLS label fields are 20 bits each.
最小MPLS标签，最大MPLS标签指定一系列MPLS标签值，包括最小MPLS标签到最大MPLS标签。最大和最小MPLS标签字段各为20位。
The Default Label Range Block for PortTypes using FEC labels is not used. The Label Range Count and Label Range Length fields defined in [8.2.1] should be set to 0.
未使用使用FEC标签的端口类型的默认标签范围块。[8.2.1]中定义的标签范围计数和标签范围长度字段应设置为0。
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x x x x x x x x x x x x x x x x| Number of Records |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x x x x x x x x x x x x x x x x| Number of Records |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Port Records ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Note: Fields and Parameters that have been explained in the description of the general messages will not be explained in this section. Please refer to section 3.1 for details.
注意：本节将不解释在一般消息说明中已解释的字段和参数。详情请参考第3.1节。
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 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Event Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Event Flags | Port Attribute Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PortType |S|x|x|x|x|x|x|x| Data Fields Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ PortType Specific Data ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x x x x x x x x x x x x x x x x| Number of Service Specs |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Service Specs List ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Event Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Event Flags | Port Attribute Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PortType |S|x|x|x|x|x|x|x| Data Fields Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ PortType Specific Data ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x x x x x x x x x x x x x x x x| Number of Service Specs |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Service Specs List ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The definition of the fields in the Port Record is exactly the same as that of the Port Configuration message [section 8.2].
端口记录中字段的定义与端口配置消息的定义完全相同[第8.2节]。
The Service Configuration message requests the switch for the configuration information of the Services that are supported. The Service Configuration message is:
服务配置消息请求交换机提供所支持服务的配置信息。服务配置消息为：
Message Type = 67
消息类型=67
The Service 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x x x x x x x x x x x x x x x x| Number of Service Records |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Service 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x x x x x x x x x x x x x x x x| Number of Service Records |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Service Records ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Note: Fields and Parameters that have been explained in the description of the general messages will not be explained in this section. Please refer to section 3.1 for details.
注意：本节将不解释在一般消息说明中已解释的字段和参数。详情请参考第3.1节。
Number of Service Records Field gives the total number of Service Records to be returned in the Service Records field.
Number of Service Records（服务记录数）字段提供要在Service Records（服务记录）字段中返回的服务记录总数。
Service Records A sequence of zero or more Service Records. The switch returns one Service Record for each Service that it supports on any of its ports. A Service record contains the configuration data of the specified Service. Each Service 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Service ID | Number of Cap. Set. Records |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Capability Set 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Service ID | Number of Cap. Set. Records |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Capability Set Records ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Service ID The Service ID Field identifies the Service supported by the port. The Services are defined with their Service ID values as described in section 10.2.
服务ID服务ID字段标识端口支持的服务。服务使用第10.2节所述的服务ID值进行定义。
Number of Cap. Set. Records Field gives the total number of Capability Set Records to be returned in the Service Record field.
上限的数目。设置记录字段给出要在服务记录字段中返回的功能集记录总数。
Capability Set Records The switch returns one or more Capability Set Records in each Service Record. A Capability Set contains a set of parameters that describe the QoS parameter values and traffic controls that apply to an instance of the Service. Each Capability Set record 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Cap. Set ID | Traffic Controls |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CLR | CTD |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Frequency | CDV |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Cap. Set ID | Traffic Controls |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CLR | CTD |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Frequency | CDV |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Capability Set ID The value in this Field defines a Capability Set ID supported by the switch. The values of a Capability Set ID are assigned by the switch and used in Port Configuration messages to identify Capability Sets supported by individual ports. Each Capability Set Record within a Service Record MUST have a unique Capability Set ID.
功能集ID此字段中的值定义交换机支持的功能集ID。功能集ID的值由交换机分配，并在端口配置消息中使用，以标识各个端口支持的功能集。服务记录中的每个功能集记录必须具有唯一的功能集ID。
Traffic Controls Field identifies the availability of Traffic Controls within the Capability Set. Traffic Controls are defined as part of the respective Service definition, see Chapter 10. Some or all of the Traffic Controls may be undefined for a given Service, in which case the corresponding Flag is ignored by the controller. The Traffic Controls field is formatted into Traffic Control Sub-fields as follows:
“交通控制”字段标识功能集中交通控制的可用性。交通管制定义为各自服务定义的一部分，参见第10章。对于给定服务，某些或所有流量控制可能未定义，在这种情况下，控制器将忽略相应的标志。交通控制字段格式设置为交通控制子字段，如下所示：
0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| U | D | I | E | S | V |x x x x|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| U | D | I | E | S | V |x x x x|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Traffic Control Sub-fields have the following encoding:
交通控制子字段具有以下编码：
0b00 Indicates that the Traffic Control is not available in the Capability Set.
0b00表示交通控制在能力集中不可用。
0b01 Indicates that the Traffic Control is applied to all connections that use the Capability Set.
0b01表示流量控制应用于所有使用该功能集的连接。
0b10 Indicates that the Traffic Control is available for application to connections that use the Capability Set on a per connection basis.
0b10表示流量控制可应用于使用基于每个连接设置的功能的连接。
0b11 Reserved
0b11保留
Traffic Control Sub-fields:
交通控制子字段：
U: Usage Parameter Control The Usage Parameter Control sub-field indicates the availability of Usage Parameter Control for the specified Service and Capability Set.
U：使用参数控制使用参数控制子字段表示指定服务和功能集的使用参数控制的可用性。
D: Packet Discard The Packet Discard sub-field indicates the availability of Packet Discard for the specified Service and Capability Set.
D：数据包丢弃数据包丢弃子字段表示指定服务和功能集的数据包丢弃可用性。
I: Ingress Shaping The Ingress Shaping sub-field indicates the availability of Ingress Traffic Shaping to the Peak Cell Rate and Cell Delay Variation Tolerance for the specified Service and Capability Set.
I：入口整形入口整形子字段指示入口流量整形到指定服务和能力集的峰值小区速率和小区延迟变化容差的可用性。
E: Egress Shaping, Peak Rate The Egress Shaping, Peak Rate sub-field indicates the availability of Egress Shaping to the Peak Cell Rate and Cell Delay Variation Tolerance for the specified Service and Capability Set.
E：出口整形，峰值速率出口整形，峰值速率子字段表示出口整形对指定服务和能力集的峰值小区速率和小区延迟变化容差的可用性。
S: Egress Traffic Shaping, Sustainable Rate The Egress Shaping, Sustainable Rate sub-field, if set, indicates that Egress Traffic Shaping to the Sustainable Cell Rate and Maximum Burst Size is available for the specified Service and Capability Set.
S：出口流量整形，可持续速率出口整形，可持续速率子字段（如果设置）表示出口流量整形到可持续小区速率和最大突发大小可用于指定的服务和能力集。
V: VC Merge The VC Merge sub-field indicates the availability of ATM Virtual Channel Merge (i.e., multipoint to point ATM switching with a traffic control to avoid AAL5 PDU interleaving) capability for the specified Service and Capability Set.
V:VC Merge VC Merge子字段表示指定服务和功能集的ATM虚拟通道合并（即，具有流量控制的多点对点ATM交换，以避免AAL5 PDU交错）功能的可用性。
QoS Parameters The remaining four fields in the Capability Set Record contain the values of QoS Parameters. QoS Parameters are defined as part of the respective Service definition, see Chapter 9.6. Some or all of the QoS Parameters may be undefined for a given Service, in which case the corresponding field is ignored by the controller.
QoS参数能力集记录中的其余四个字段包含QoS参数的值。QoS参数定义为各自服务定义的一部分，参见第9.6章。对于给定的服务，某些或所有QoS参数可能未定义，在这种情况下，控制器将忽略相应字段。
CLR: Cell Loss Ratio The Cell Loss Ratio parameter indicates the CLR guaranteed by the switch for the specified Service. A cell loss ratio is expressed as an order of magnitude n, where the CLR takes the value of ten raised to the power of -n, i.e., log(CLR)=-n. The value n is coded as a binary integer, having a range of 1 <= n <= 15. In addition, the value 0b1111 1111 indicates that no CLR guarantees are given.
CLR：信元丢失率信元丢失率参数表示交换机为指定服务保证的CLR。信元丢失率以数量级n表示，其中CLR取10的值，并提升为-n的幂，即log（CLR）=-n。值n被编码为二进制整数，其范围为1<=n<=15。此外，值0b1111 1111表示未提供CLR保证。
Frequency The frequency field is coded as an 8 bit unsigned integer. Frequency applies to the MPLS CR-LDP Service (see Section 10.4.3). Valid values of Frequency are:
频率频率字段编码为8位无符号整数。频率适用于MPLS CR-LDP服务（见第10.4.3节）。频率的有效值为：
0 - Very frequent 1 - Frequent 2 - Unspecified
0-非常频繁1-频繁2-未指定
CTD: Cell Transfer Delay The CTD value is expressed in units of microseconds. It is coded as a 24-bit integer.
CTD：小区传输延迟CTD值以微秒为单位表示。它被编码为24位整数。
CDV: Peak-to-peak Cell Delay Variation The CDV value is expressed in units of microseconds. It is coded as a 24-bit integer.
CDV：峰间小区延迟变化CDV值以微秒为单位表示。它被编码为24位整数。
Event messages allow the switch to inform the controller of certain asynchronous events. By default the controller does not acknowledge event messages unless ReturnReceipt is set in the Result field. The Code field is only used in case of Adjacency Update message, otherwise it is not used and SHOULD be set to zero. Event messages are not sent during initialisation. Event messages have the following format:
事件消息允许交换机通知控制器某些异步事件。默认情况下，除非在结果字段中设置了ReturnReceive，否则控制器不会确认事件消息。代码字段仅在邻接更新消息的情况下使用，否则不使用，应设置为零。初始化期间不发送事件消息。事件消息的格式如下：
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Event Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| |
+-+-+-+-+ Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Event Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| |
+-+-+-+-+ Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Note: Fields and Parameters that have been explained in the description of the general messages will not be explained in this section. Please refer to section 3.1 for details.
注意：本节将不解释在一般消息说明中已解释的字段和参数。详情请参考第3.1节。
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 initialised. 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.
事件序列号指定端口的事件序列号的当前值。初始化端口时，事件序列号设置为零。每当端口检测到交换机通常通过事件消息报告的异步事件时，该值将递增一。每次发生事件时，事件序列号必须增加，即使由于流控制的操作而阻止交换机发送事件消息。
Label Field gives the Label to which the event message refers. If this field is not required by the event message it is set to zero.
标签字段提供事件消息所引用的标签。如果事件消息不需要此字段，则将其设置为零。
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 sends an Event message it MUST set the Event Flag for that port corresponding to the Event type. If Flow Control is activated for this Event type for this Port then the switch MUST NOT send another Event message of the same type for that port 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 Label field is not used and is set to zero. The Port Up message is:
端口上升消息通知控制器端口的线路状态已从下降或测试状态更改为上升状态。当交换机端口的线路状态从下降或测试状态更改为上升状态时，必须生成新的端口会话号，最好使用某种形式的随机数。新端口会话号在端口会话号字段中给出。标签字段未使用，设置为零。端口向上消息为：
Message Type = 80
消息类型=80
The Port Down message informs the controller that the Line Status of a port has changed from the Up state or Test 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 Label field is not used and is set to zero. The Port Down message is:
端口下降消息通知控制器端口的线路状态已从上升状态或测试状态更改为下降状态。如果交换机能够检测到链路故障，将发送此消息以报告链路故障。在端口会话号字段中报告端口关闭前有效的端口会话号。标签字段未使用，设置为零。端口关闭消息为：
Message Type = 81
消息类型=81
The Invalid Label message is sent to inform the controller that one or more cells or frames have arrived at an input port with a Label that is currently not allocated to an assigned connection. The input port is indicated in the Port field, and the Label in the Label field. The Invalid Label message is:
发送无效标签消息以通知控制器，一个或多个单元或帧已到达输入端口，其标签当前未分配给分配的连接。输入端口在端口字段中指示，标签在标签字段中指示。无效标签消息为：
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 Label field is not used and is set to zero. The New Port message is:
New Port（新端口）消息通知控制器新端口已添加到交换机。新端口的端口号在端口字段中给出。必须分配新的端口会话号，最好使用某种形式的随机数。新端口会话号在端口会话号字段中给出。新端口的状态未定义，因此不使用标签字段，并将其设置为零。新端口消息为：
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 Label fields are not used and are set to zero. The Dead Port message is:
死区端口消息通知控制器一个端口已从交换机上移除。端口的端口号在端口字段中给出。在端口会话号字段中报告删除端口之前有效的端口会话号。不使用标签字段，将其设置为零。死端口消息是：
Message Type = 84
消息类型=84
The Adjacency Update message informs the controller when adjacencies, i.e., other controllers controlling a specific partition, are joining or leaving. When a new adjacency has been established, the switch sends an Adjacency Update message to every controller with an established adjacency to that partition. The Adjacency Update message is also sent when adjacency is lost between the partition and a controller, provided that there are any remaining adjacencies with that partition. The Code field is used to indicate the number of adjacencies known by the switch partition. The Label field is not used and SHOULD be set to zero. The Adjacency Update message is:
邻接更新消息在邻接（即控制特定分区的其他控制器）加入或离开时通知控制器。当建立新的邻接关系时，交换机向每个与该分区具有已建立邻接关系的控制器发送邻接更新消息。当分区和控制器之间的邻接丢失时，也会发送邻接更新消息，前提是该分区还有剩余的邻接。代码字段用于指示交换机分区已知的邻接数。标签字段未使用，应设置为零。邻接更新消息为：
Message Type = 85
消息类型=85
In the GSMP Service Model a controller may request the switch to establish a connection with a given Service. The requested Service is identified by including a Service ID in the Add Branch message or the Reservation Message. The Service ID refers to a Service Definition provided in this chapter of the GSMP specification.
在GSMP服务模型中，控制器可以请求交换机与给定服务建立连接。通过在添加分支消息或保留消息中包含服务ID来标识请求的服务。服务ID是指GSMP规范本章中提供的服务定义。
A switch that implements one or more of the Services, as defined below, advertises the availability of these Services in the Service Configuration message response (see Section 8.4). Details of the switch's implementation of a given Service that are important to the controller (e.g., the value of delay or loss bounds or the availability of traffic controls such as policers or shapers) are reported in the form of a Capability Set in the Service Configuration message response.
实现一个或多个服务的交换机（定义见下文）在服务配置消息响应中公布这些服务的可用性（见第8.4节）。交换机实现对控制器很重要的给定服务的详细信息（例如，延迟或丢失界限的值或流量控制的可用性，如策略或整形器）以服务配置消息响应中的能力集的形式报告。
Thus a switch's implementation of a Service is defined in two parts: the Service Definition, which is part of the GSMP specification, and the Capability Set, which describes attributes of the Service specific to the switch. A switch may support more than one Capability Set for a given Service. For example if a switch supports one Service with two different values of a delay bound it could do this by reporting two Capability Sets for that Service.
因此，交换机的服务实现由两部分定义：服务定义（GSMP规范的一部分）和功能集（描述交换机特定的服务属性）。交换机可以支持给定服务的多个功能集。例如，如果交换机支持一个具有两个不同延迟界限值的服务，它可以通过报告该服务的两个功能集来实现这一点。
The Service Definition is identified in GSMP messages by the Service ID, a sixteen-bit identifier. Assigned numbers for the Service ID are given with the Service Definitions in Section 10.4. The Capability Set is identified in GSMP messages by the Capability Set ID, a sixteen-bit identifier. Numbers for the Capability Set ID are assigned by the switch and are advertised in the Service Configuration message response.
GSMP消息中的服务定义由服务ID（16位标识符）标识。服务ID的分配编号与第10.4节中的服务定义一起给出。GSMP消息中的能力集由能力集ID（一个16位标识符）标识。功能集ID的编号由交换机分配，并在服务配置消息响应中公布。
The switch reports all its supported Services and Capability Sets in the Service Configuration message response. The subset of Services and Capability Sets supported on an individual port is reported in the Port Configuration message response or in the All Ports Configuration message response. In these messages the Services and Capability Sets supported on the specified port are indicated by a list of {Service ID, Capability Set ID} number pairs.
交换机在服务配置消息响应中报告其所有支持的服务和功能集。单个端口上支持的服务和功能集子集将在端口配置消息响应或所有端口配置消息响应中报告。在这些消息中，指定端口上支持的服务和功能集由{Service ID，Capability Set ID}编号对的列表表示。
Terms and objects defined for the GSMP Service Model are given in this section.
本节给出了为GSMP服务模型定义的术语和对象。
Services in GSMP are defined largely with reference to Original Specifications, i.e., the standards or implementation agreements published by organisations such as ITU-T, IETF, and ATM Forum that originally defined the Service. This version of GSMP refers to 4 original specifications: [8], [9], [10] and [11].
GSMP中的服务定义主要参考原始规范，即ITU-T、IETF和ATM论坛等组织发布的最初定义服务的标准或实施协议。本版本的GSMP参考了4个原始规范：[8]、[9]、[10]和[11]。
Each Service Definition in GSMP includes definition of:
GSMP中的每个服务定义包括以下定义：
Traffic Parameters Traffic Parameter definitions are associated with Services while Traffic Parameter values are associated with connections.
流量参数流量参数定义与服务关联，而流量参数值与连接关联。
Traffic Parameters quantitatively describe a connection's requirements on the Service. For example, Peak Cell Rate is a Traffic Parameter of the Service defined by the ATM Forum Constant Bit Rate Service Category.
流量参数定量地描述了连接对服务的要求。例如，峰值信元速率是由ATM论坛恒定比特率服务类别定义的服务的流量参数。
Some Traffic Parameters are mandatory and some are optional, depending on the Service.
根据服务的不同，一些流量参数是强制性的，一些是可选的。
Semantics of Traffic Parameters are defined by reference to Original Specifications.
通过参考原始规范定义交通参数的语义。
QoS Parameters QoS Parameters and their values are associated with Services.
QoS参数QoS参数及其值与服务相关联。
QoS Parameters express quantitative characteristics of a switch's support of a Service. They include, for example, quantitative bounds on switch induced loss and delay.
QoS参数表示交换机对服务支持的定量特征。例如，它们包括开关引起的损耗和延迟的定量界限。
Some QoS Parameters will be mandatory and some will be optional.
有些QoS参数是强制性的，有些是可选的。
Semantics of QoS Parameters are defined by reference to Original Specifications.
QoS参数的语义是通过参考原始规范来定义的。
Traffic Controls The implementation of some Services may include the use of Traffic Controls. Traffic Controls include, for example functions such as policing, input shaping, output shaping, tagging and marking, frame vs. cell merge, frame vs. cell discard.
交通管制某些服务的实施可能包括使用交通管制。例如，流量控制包括监控、输入整形、输出整形、标记和标记、帧与单元合并、帧与单元丢弃等功能。
Switches are not required to support Traffic Controls. Any function that is always required in the implementation of a Service is considered part of the Service and is not considered a Traffic Control.
不需要交换机来支持交通控制。服务实现中始终需要的任何功能都被视为服务的一部分，而不被视为流量控制。
If a switch supports a Traffic Control then the control may be applied either to all connections that use a given Capability Set (see below) or to individual connections.
如果交换机支持流量控制，则该控制可应用于使用给定功能集（见下文）的所有连接或单个连接。
The definition of a Traffic Control is associated with a Service. Traffic Controls are defined, as far as possible, by reference to Original Specifications.
流量控制的定义与服务相关联。交通管制尽可能参考原始规范进行定义。
For each Service that a switch supports the switch MUST also support at least one Capability Set. A Capability Set establishes characteristics of a switch's implementation of a Service. It may be appropriate for a switch to support more than one Capability Set for a given Service.
对于交换机支持的每个服务，交换机还必须至少支持一个功能集。能力集建立交换机实现服务的特征。交换机可能适合为给定服务支持多个功能集。
A Capability Set may contain, depending on the Service definition, QoS Parameter values and an indication of availability of Traffic Controls.
根据服务定义，能力集可以包含QoS参数值和业务控制可用性的指示。
If a switch reports QoS Parameter values in a Capability Set then these apply to all the connections that use that Capability Set.
如果交换机在功能集中报告QoS参数值，则这些值将应用于使用该功能集的所有连接。
For each Traffic Control defined for a given Service the switch reports availability of that control as one of the following:
对于为给定服务定义的每个流量控制，交换机将该控制的可用性报告为以下之一：
Not available in the Capability Set,
在功能集中不可用，
Applied to all connections that use the Capability Set, or
应用于使用功能集的所有连接，或
Available for application to connections that use the Capability Set on a per connection basis. In this case, a controller may request application of the Traffic Control in connection management messages.
可用于应用到基于每个连接使用功能集的连接。在这种情况下，控制器可以请求在连接管理消息中应用业务控制。
A switch's Services and Capability Sets are reported to a controller in a Service Configuration message. A Service Configuration message response includes the list of Services defined for GSMP that the switch supports and, for each Service, a specification of the Capability Sets supported for the Service. Services are referred to by numbers standardised in the GSMP specification. Capability Sets are referred to by a numbering system reported by the switch. Each Capability Set within a given Service includes a unique identifying number together with the switch's specification of QoS Parameters and Traffic Controls.
交换机的服务和功能集在服务配置消息中报告给控制器。服务配置消息响应包括交换机支持的GSMP定义的服务列表，以及每个服务支持的功能集规范。服务是指GSMP规范中标准化的数字。能力集由交换机报告的编号系统引用。给定服务中的每个功能集包括一个唯一的标识号以及交换机的QoS参数和流量控制规范。
A switch need not support all the defined Services and Capability Sets on every port. The supported Services and Capability Sets are reported to the controller on a per port basis in port configuration messages. Port configuration response messages list the supported
交换机不需要在每个端口上支持所有定义的服务和功能集。支持的服务和功能集在端口配置消息中按每个端口报告给控制器。端口配置响应消息列出支持的端口配置
Services using the standardised identifying numbers and the Capability Sets by using the identifying numbers established in the switch Service configuration messages.
使用标准化标识号的服务和使用交换机服务配置消息中建立的标识号的能力集。
GSMP does not provide a negotiation mechanism by which a controller may establish or modify Capability Sets.
GSMP不提供控制器可用于建立或修改能力集的协商机制。
When a controller establishes a connection, the connection management message includes indication of the Service and the Capability Set. Depending on these the connection management message may additionally include Traffic Parameter values and Traffic Control flags.
当控制器建立连接时，连接管理消息包括服务和能力集的指示。根据这些，连接管理消息还可以包括流量参数值和流量控制标志。
A connection with a given Service can only be established if both the requested Service and the requested Capability Set are available on all of the connection's input and output ports.
只有当请求的服务和请求的功能集在连接的所有输入和输出端口上都可用时，才能建立与给定服务的连接。
Refresh of an extant connection is permitted but the add branch message requesting the message MUST NOT include indication of Service, Capability Sets or Traffic Parameters.
允许刷新现有连接，但请求消息的添加分支消息不得包括服务、功能集或流量参数的指示。
An extant connection's Traffic Parameters may be changed without first deleting the connection. The Service and Capability Sets of an extant connection cannot be changed.
可以在不首先删除连接的情况下更改现有连接的流量参数。无法更改现有连接的服务和功能集。
Move branch messages may be refused on the grounds of resource depletion.
移动分支消息可能会因资源耗尽而被拒绝。
This section sets forth the definition of Services. The following Service Identifiers are defined:
本节阐述了服务的定义。定义了以下服务标识符：
ID Service Type
ID服务类型
1 CBR= 1 2 rt-VBR.1 3 rt-VBR.2 4 rt-VBR.3 5 nrt-VBR.1 6 nrt-VBR.2 7 nrt-VBR.3 8 UBR.1 9 UBR.2 10-11 Reserved 12 GFR.1 13 GFR.2 14-19 Reserved 20 Int-Serv Controlled Load
1 CBR=1 2 rt VBR.1 3 rt VBR.2 4 rt VBR.3 5 nrt VBR.1 6 nrt VBR.2 7 nrt VBR.3 UBR.1 9 UBR.2 10-11预留12 GFR.1 13 GFR.2 14-19预留20内部维修控制负载
21-24 Reserved 25 MPLS CR-LDP QoS 26-29 Reserved 30 Frame Relay Service 31-49 Reserved 50-69 Reserved GMPLS 70-65535 Reserved
21-24保留25 MPLS CR-LDP QoS 26-29保留30帧中继服务31-49保留50-69保留GMPLS 70-65535保留
Each Service will be defined in its own subsection. Each Service definition includes the following definitions:
每项服务将在其各自的小节中定义。每个服务定义包括以下定义：
Service Identifier The reference number used to identify the Service in GSMP messages.
服务标识符用于在GSMP消息中标识服务的参考号。
Service Characteristics A definition of the Service.
服务特征服务的定义。
Traffic Parameters A definition of the Traffic Parameters used in connection management messages.
流量参数连接管理消息中使用的流量参数的定义。
QoS Parameters A definition of the QoS Parameters that are included in the Capability Set for instances of the Service.
QoS参数服务实例的能力集中包含的QoS参数的定义。
Traffic Controls A definition of the Traffic Controls that may be supported by an instance of the Service.
流量控制服务实例可能支持的流量控制的定义。
Descriptive text is avoided wherever possible in order to minimise any possibility of semantic conflict with the Original Specifications.
尽可能避免使用描述性文本，以尽量减少与原始规范发生语义冲突的可能性。
Service Identifier: CBR.1 - Service ID = 1
服务标识符：CBR.1-服务ID=1
Service Characteristics: Equivalent to ATM Forum CBR.1 Service, see [8].
服务特点：相当于ATM论坛CBR.1服务，见[8]。
Traffic Parameters: - Peak Cell Rate - Cell Delay Variation Tolerance
流量参数：-峰值信元速率-信元延迟变化容差
QoS Parameters: - Cell Loss Ratio - Maximum Cell Transfer Delay - Peak-to-peak Cell Delay Variation
QoS参数：-信元丢失率-最大信元传输延迟-峰间信元延迟变化
Traffic Controls: - (U) Usage Parameter Control - (I) Ingress Traffic Shaping to the Peak Cell Rate - (E) Egress Traffic Shaping to the Peak Cell Rate and Cell Delay Variation Tolerance - (D) Packet Discard
流量控制：-（U）使用参数控制-（I）入口流量整形到峰值小区速率-（E）出口流量整形到峰值小区速率和小区延迟变化容差-（D）数据包丢弃
Service Identifier:
rt-VBR.1 - Service ID = 2
rt-VBR.2 - Service ID = 3
rt-VBR.3 - Service ID = 4
Service Identifier:
rt-VBR.1 - Service ID = 2
rt-VBR.2 - Service ID = 3
rt-VBR.3 - Service ID = 4
Service Characteristics: Equivalent to ATM Forum rt-VBR Service, see [8].
服务特点：相当于ATM论坛rt VBR服务，见[8]。
Traffic Parameters: - Peak Cell Rate - Cell Delay Variation Tolerance - Sustainable Cell Rate - Maximum Burst Size
流量参数：-峰值信元速率-信元延迟变化容差-可持续信元速率-最大突发大小
QoS Parameters: - Cell Loss Ratio - Maximum Cell Transfer Delay - Peak-to-peak Cell Delay Variation
QoS参数：-信元丢失率-最大信元传输延迟-峰间信元延迟变化
Traffic Controls: - (U) Usage Parameter Control - (I) Ingress Traffic Shaping to the Peak Cell Rate - (E) Egress Traffic Shaping to the Peak Cell Rate and Cell Delay Variation Tolerance - (S) Egress Traffic Shaping to the Sustainable Cell Rate and Maximum Burst Size - (P) Packet Discard - (V) VC Merge
流量控制：-（U）使用参数控制-（I）峰值小区速率的入口流量整形-（E）峰值小区速率的出口流量整形和小区延迟变化容差-（S）可持续小区速率和最大突发大小的出口流量整形-（P）包丢弃-（V）VC合并
Service Identifier:
nrt-VBR.1 - Service ID = 5
nrt-VBR.2 - Service ID = 6
nrt-VBR.3 - Service ID = 7
Service Identifier:
nrt-VBR.1 - Service ID = 5
nrt-VBR.2 - Service ID = 6
nrt-VBR.3 - Service ID = 7
Service Characteristics: Equivalent to ATM Forum nrt-VBR Service, see [8].
服务特点：相当于ATM论坛nrt VBR服务，见[8]。
Traffic Parameters: - Peak Cell Rate - Cell Delay Variation Tolerance - Sustainable Cell Rate - Maximum Burst Size
流量参数：-峰值信元速率-信元延迟变化容差-可持续信元速率-最大突发大小
QoS Parameter: - Cell Loss Ratio
QoS参数：-小区丢失率
Traffic Controls: - (U) Usage Parameter Control - (I) Ingress Traffic Shaping to the Peak Cell Rate - (E) Egress Traffic Shaping to the Peak Cell Rate and Cell Delay Variation Tolerance - (S) Egress Traffic Shaping to the Sustainable Cell Rate and Maximum Burst Size - (P) Packet Discard - (V) VC Merge
流量控制：-（U）使用参数控制-（I）峰值小区速率的入口流量整形-（E）峰值小区速率的出口流量整形和小区延迟变化容差-（S）可持续小区速率和最大突发大小的出口流量整形-（P）包丢弃-（V）VC合并
Service Identifier:
UBR.1 - Service ID = 8
UBR.2 - Service ID = 9
Service Identifier:
UBR.1 - Service ID = 8
UBR.2 - Service ID = 9
Service Characteristics: Equivalent to ATM Forum UBR Service, see [8].
服务特点：相当于ATM论坛UBR服务，见[8]。
Traffic Parameters: - Peak Cell Rate - Cell Delay Variation Tolerance
流量参数：-峰值信元速率-信元延迟变化容差
QoS Parameter: None
QoS参数：无
Traffic Controls: - (U) Usage Parameter Control - (I) Ingress Traffic Shaping to the Peak Cell Rate
流量控制：-（U）使用参数控制-（I）将流量整形到峰值小区速率
- (E) Egress Traffic Shaping to the Peak Cell Rate and Cell Delay Variation Tolerance - (P) Packet Discard - (V) VC Merge
- （E） 出口流量对峰值信元速率和信元延迟变化容忍度的整形-（P）数据包丢弃-（V）VC合并
ABR is not supported in this version of GSMP.
此版本的GSMP不支持ABR。
Service Identifier:
GFR.1 - Service ID = 12
GFR.2 - Service ID = 13
Service Identifier:
GFR.1 - Service ID = 12
GFR.2 - Service ID = 13
Service Characteristics: Equivalent to ATM Forum GFR Service, see [8].
服务特点：相当于ATM论坛GFR服务，见[8]。
Traffic Parameters: - Peak Cell Rate - Cell Delay Variation Tolerance - Minimum Cell Rate - Maximum Burst Size - Maximum Frame Size
流量参数：-峰值信元速率-信元延迟变化容差-最小信元速率-最大突发大小-最大帧大小
QoS Parameter: - Cell Loss Ratio
QoS参数：-小区丢失率
Traffic Controls: - (U) Usage Parameter Control - (I) Ingress Traffic Shaping to the Peak Cell Rate - (E) Egress Traffic Shaping to the Peak Cell Rate and Cell Delay Variation Tolerance - (V) VC Merge
流量控制：-（U）使用参数控制-（I）入口流量整形到峰值小区速率-（E）出口流量整形到峰值小区速率和小区延迟变化容差-（V）VC合并
Service Identifier: Int-Serv Controlled Load - Service ID = 20
服务标识符：Int Serv受控负载-服务ID=20
Service Characteristics: See [9].
服务特征：见[9]。
Traffic Parameters: - Token bucket rate (r) - Token bucket depth (b) - Peak rate (p) - Minimum policed unit (m) - Maximum packet size (M)
流量参数：-令牌桶速率（r）-令牌桶深度（b）-峰值速率（p）-最小策略单元（m）-最大数据包大小（m）
QoS Parameter: None.
QoS参数：无。
Traffic Controls: None.
交通管制：无。
Service Identifier: MPLS CR-LDP QoS - Service ID = 25
服务标识符：MPLS CR-LDP QoS-服务ID=25
Service Characteristics: See [10].
服务特征：见[10]。
Traffic Parameters: - Peak Data Rate - Peak Burst Size - Committed Data Rate - Committed Burst Size - Excess Burst Size - Weight
流量参数：-峰值数据速率-峰值突发大小-提交的数据速率-提交的突发大小-超出的突发大小-重量
QoS Parameter: - Frequency
QoS参数：-频率
Traffic Controls: None currently defined.
交通控制：当前未定义。
Service Identifier: Frame Relay Service - Service ID = 30
服务标识符：帧中继服务-服务ID=30
Service Characteristics: Equivalent to Frame Relay Bearer Service, see [11].
业务特性：相当于帧中继承载业务，参见[11]。
Traffic Parameters: - Committed Information Rate - Committed Burst Rate - Excess Burst Rate
流量参数：-提交的信息速率-提交的突发速率-超额突发速率
QoS Parameters: None.
QoS参数：无。
Traffic Controls: - Usage Parameter Control - Egress Traffic Shaping to the Committed Information Rate and Committed Burst Size
流量控制：-使用参数控制-根据提交的信息速率和提交的突发大小进行出口流量整形
DiffServ is not supported in this version of GSMP.
此版本的GSMP不支持DiffServ。
Connection management messages that use the GSMP Service Model (i.e., those that have IQS or OQS set to 0b10) include the Traffic Parameters Block that specifies the Traffic Parameter values of a connection. The required Traffic Parameters of a given Service are given in Section 10.4. The format and encoding of these parameters are given below.
使用GSMP服务模型的连接管理消息（即IQS或OQS设置为0b10的消息）包括指定连接的流量参数值的流量参数块。第10.4节给出了给定服务所需的交通参数。这些参数的格式和编码如下所示。
The Traffic Parameters:
交通参数：
- Peak Cell Rate
- 峰值细胞率
- Cell Delay Variation Tolerance
- 信元抖动容限
- Sustainable Cell Rate
- 可持续细胞率
- Maximum Burst Size
- 最大突发大小
- Minimum Cell Rate
- 最小信元速率
- Maximum Frame Size
- 最大帧大小
are defined in [8]. These Parameters are encoded as 24-bit unsigned integers. Peak Cell Rate, Sustainable Cell Rate, and Minimum Cell Rate are in units of cells per second. Cell Delay Variation Tolerance is in units of microseconds. Maximum Burst Size and Maximum Frame Size are in units of cells. In GSMP messages, the individual Traffic Parameters are encoded as follows:
定义见[8]。这些参数被编码为24位无符号整数。峰值信元速率、持续信元速率和最小信元速率以每秒信元为单位。单元延迟变化公差以微秒为单位。最大突发大小和最大帧大小以单元为单位。在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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x x x x x x x x| 24 bit unsigned integer |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x x x x x x x x| 24 bit unsigned integer |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format of the Traffic Parameters Block in connection management messages depends on the Service. It is a sequence of the 32 bit words (as shown above) corresponding to the Traffic Parameters as specified in the Service Definitions given in Section 10.4.1 in the order given there.
连接管理消息中流量参数块的格式取决于服务。它是一个32位字序列（如上所示），对应于第10.4.1节服务定义中规定的流量参数，顺序如下。
The Traffic Parameters:
交通参数：
- Token bucket rate (r)
- 令牌桶速率（r）
- Token bucket size (b)
- 令牌桶大小（b）
- Peak rate (p)
- 峰值速率（p）
are defined in [9]. They are encoded as 32-bit IEEE single-precision floating point numbers. The Traffic Parameters Token bucket rate (r) and Peak rate (p) are in units of bytes per seconds. The Traffic Parameter Token bucket size (b) is in units of bytes.
定义见[9]。它们被编码为32位IEEE单精度浮点数。流量参数令牌桶速率（r）和峰值速率（p）以字节/秒为单位。流量参数令牌桶大小（b）以字节为单位。
The Traffic Parameters:
交通参数：
- Minimum policed unit (m)
- 最小政策单位（m）
- Maximum packet size (M)
- 最大数据包大小（M）
are defined in [9]. They are encoded as 32 integer in units of bytes.
定义见[9]。它们以字节为单位编码为32整数。
The Traffic Parameters Block for the Int-Serv Controlled Load Service is as follows:
Int Serv控制负载服务的流量参数块如下所示：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Token bucket rate (r) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Token bucket size (b) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peak rate (p) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Minimum policed unit (m) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Maximum packet size (M) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Token bucket rate (r) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Token bucket size (b) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peak rate (p) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Minimum policed unit (m) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Maximum packet size (M) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Traffic Parameters:
交通参数：
- Peak Data Rate
- 峰值数据速率
- Peak Burst Size
- 峰值突发大小
- Committed Data Rate
- 提交数据速率
- Committed Burst Size
- 提交的突发大小
- Excess Burst Size
- 过量突发大小
are defined in [10] to be encoded as a 32-bit IEEE single-precision floating point number. A value of positive infinity is represented as an IEEE single-precision floating-point number with an exponent of all ones (255) and a sign and mantissa of all zeros. The values Peak Data Rate and Committed Data Rate are in units of bytes per second. The values Peak Burst Size, Committed Burst Size and Excess Burst Size are in units of bytes.
在[10]中定义为32位IEEE单精度浮点数。正无穷大的值表示为IEEE单精度浮点数，其指数为全1（255），符号和尾数均为零。峰值数据速率和提交数据速率的值以字节/秒为单位。峰值突发大小、提交突发大小和多余突发大小的值以字节为单位。
The Traffic Parameter
交通参数
- Weight
- 重量
is defined in [10] to be an 8-bit unsigned integer indicating the weight of the CRLSP. Valid weight values are from 1 to 255. The value 0 means that weight is not applicable for the CRLSP.
在[10]中定义为8位无符号整数，表示CRLSP的权重。有效的权重值介于1到255之间。值0表示重量不适用于CRLSP。
The Traffic Parameters Block for the CRLDP Service is as follows:
CRLDP业务的业务参数块如下：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peak Data Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peak Burst Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Committed Data Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Committed Burst Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Excess Burst Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x x x x x x x x x x x x x x x x x x x x x x x x| Weight |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peak Data Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peak Burst Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Committed Data Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Committed Burst Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Excess Burst Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x x x x x x x x x x x x x x x x x x x x x x x x| Weight |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Traffic Parameters:
交通参数：
- Committed Information Rate
- 承诺信息率
- Committed Burst Size
- 提交的突发大小
- Excess Burst Size
- 过量突发大小
are defined in [11]. Format and encoding of these parameters for frame relay signalling messages are defined in [12]. (Note than in [12] the Committed Information Rate is called "Throughput".) GSMP uses the encoding defined in [12] but uses a different format.
定义见[11]。[12]中定义了帧中继信令消息的这些参数的格式和编码。（注意，与[12]相比，提交的信息速率称为“吞吐量”。）GSMP使用[12]中定义的编码，但使用不同的格式。
The format of the Traffic Parameters Block for Frame Relay Service is as follows:
帧中继服务的业务参数块格式如下：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x x x x x x x x x x x x x| Mag |x x x x x| CIR Multiplier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x x x x x x x x x x x x x| Mag |x x| CBS Multiplier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x x x x x x x x x x x x x| Mag |x x| EBS Multiplier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x x x x x x x x x x x x x| Mag |x x x x x| CIR Multiplier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x x x x x x x x x x x x x| Mag |x x| CBS Multiplier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x x x x x x x x x x x x x| Mag |x x| EBS Multiplier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Mag This field is an unsigned integer in the range from 0 to 6. The value 7 is not allowed. Mag is the decimal exponent for the adjacent multiplier field (which itself functions as a mantissa).
Mag此字段是0到6范围内的无符号整数。值7是不允许的。Mag是相邻乘数字段的十进制指数（它本身起尾数的作用）。
CIR Multiplier This field is an unsigned integer. It functions as the mantissa of the Committed Information Rate Traffic Parameter.
CIR乘数此字段是无符号整数。它用作提交的信息速率流量参数的尾数。
CBS Multiplier EBS Multiplier These fields are unsigned integers. They function as the mantissas of the Committed Burst Size and Excess Burst Size Traffic Parameters respectively.
CBS乘数EBS乘数这些字段是无符号整数。它们分别用作提交的突发大小和超额突发大小流量参数的尾数。
The Traffic Parameter Values are related to their encoding in GSMP messages as follows:
流量参数值与GSMP消息中的编码相关，如下所示：
Committed Information Rate = 10^(Mag) * (CIR Multiplier)
Committed Information Rate = 10^(Mag) * (CIR Multiplier)
Committed Burst Size = 10^(Mag) * (CBS Multiplier)
Committed Burst Size = 10^(Mag) * (CBS Multiplier)
Excess Burst Size = 10^(Mag) * (EBS Multiplier)
Excess Burst Size = 10^(Mag) * (EBS Multiplier)
The TC Flags field in Add Branch messages for connections using the Service Model are set by the controller to indicate that specific traffic controls are requested for the requested connection. The TC Flags field is shown below:
控制器设置使用服务模型的连接的添加分支消息中的TC标志字段，以指示为请求的连接请求特定的流量控制。TC标志字段如下所示：
0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+
|U|D|I|E|S|V|P|x|
+-+-+-+-+-+-+-+-+
0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+
|U|D|I|E|S|V|P|x|
+-+-+-+-+-+-+-+-+
U: Usage Parameter Control When set, this flag indicates that Usage Parameter Control is requested.
U：使用参数控制设置时，此标志表示请求使用参数控制。
D: Packet Discard When set, this flag indicates that Packet Discard is requested.
D：数据包丢弃设置时，此标志表示请求数据包丢弃。
I: Ingress Shaping When set, this flag indicates the availability of Ingress Traffic Shaping to the Peak Rate and Delay Variation Tolerance is requested.
I：入口整形设置时，此标志表示入口流量整形到峰值速率的可用性，并请求延迟变化容差。
E: Egress Shaping, Peak Rate When set, this flag indicates that Egress Shaping to the Peak Rate and Delay Variation Tolerance is requested.
E：出口整形，峰值速率设置时，此标志表示要求出口整形到峰值速率和延迟变化公差。
S: Egress Traffic Shaping, Sustainable Rate When set, this flag indicates that Egress Traffic Shaping to the Sustainable Rate and Maximum Burst Size is requested.
S：出口流量整形，可持续速率设置时，此标志表示请求出口流量整形到可持续速率和最大突发大小。
V: VC Merge When set, this flag indicates that ATM Virtual Channel Merge (i.e., multipoint to point ATM switching with a traffic control to avoid AAL5 PDU interleaving) is requested.
V:VC Merge设置时，此标志表示请求ATM虚拟通道合并（即，具有流量控制的多点到点ATM交换，以避免AAL5 PDU交错）。
P: Port When set indicates that traffic block pertains to Ingress Port.
P：端口当设置时，表示通信阻塞属于入口端口。
x: Reserved
x:保留
The controller may set (to one) the flag corresponding to the requested Traffic Control if the corresponding Traffic Control has been indicated in the Service Configuration response message (Section 8.4) as available for application to connections that use the requested Capability Set on a per connection basis. (The requested Capability Set is indicated by the Capability Set ID the least significant byte of the Service Selector field of the Add Branch message.) If the Traffic Control has been indicated in the Service Configuration response message as either not available in the Capability Set or applied to all connections that use the Capability Set then the controller sets the flag to zero and the switch ignores the flag.
如果服务配置响应消息（第8.4节）中已指示相应的流量控制可用于基于每个连接使用请求的功能集的连接，则控制器可设置（一个）与请求的流量控制相对应的标志。（请求的能力集由能力集ID表示，该ID是添加分支消息的服务选择器字段的最低有效字节。）如果在服务配置响应消息中指示流量控制在功能集中不可用或应用于使用该功能集的所有连接，则控制器将该标志设置为零，交换机将忽略该标志。
The adjacency protocol is used to synchronise 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 synchronisation.
邻接协议用于同步链路上的状态，商定使用哪个版本的协议，发现链路另一端实体的身份，并检测其何时更改。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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PType | PFlag | Sender Instance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PType | PFlag | Sender Instance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Receiver Instance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Version In the adjacency protocol the Version field is used for version negotiation. The version negotiation is performed before synchronisation is achieved. 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 synchronised. 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 = 3.
本规范定义的GSMP协议版本的版本号为version=3。
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 synchronising 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, 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.
SYN、SYNACK和ACK消息的接收方名称是消息发送方认为位于链路远端的实体的名称。如果消息的发送者不知道链接远端实体的名称，则此字段应设置为零。对于RSTACK消息，接收方名称字段设置为导致生成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消息的传入消息的发送方端口字段的值。
PType PType is used to specify if partitions are used and how the Partition ID is negotiated.
PType PType用于指定是否使用分区以及如何协商分区ID。
Type of partition being requested. 0 No Partition 1 Fixed Partition Request 2 Fixed Partition Assigned
正在请求的分区的类型。0未分配分区1固定分区请求2固定分区
PFlag Used to indicate the type of partition request.
PFlag用于指示分区请求的类型。
1 - New Adjacency. In the case of a new adjacency, the state of the switch will be reset.
1-新邻接。如果是新的邻接，开关的状态将被重置。
2 - Recovered Adjacency. In the case of a recovered adjacency, the state of the switch will remain, and the Switch Controller will be responsible for confirming that the state of the switch matches the desired state.
2-恢复邻接。在恢复邻接的情况下，开关的状态将保持不变，开关控制器将负责确认开关的状态与所需状态匹配。
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 24-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
SYN、SYNACK和ACK消息的发送方实例是链接的发送方实例号。它用于检测链路在下降后何时恢复，或者链路另一端的实体标识何时更改。实例号是一个24位的数字，保证在最近的时间内是唯一的，并且在链路或节点关闭后恢复时会发生变化。零不是有效的实例号。对于RSTACK消息，发送方实例字段设置为
of the Receiver Instance field from the incoming message that caused the RSTACK message to be generated.
来自导致生成RSTACK消息的传入消息的Receiver实例字段。
Partition ID Field used to associate the message with a specific switch partition.
用于将消息与特定交换机分区关联的分区ID字段。
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, Sender Name and Partition ID fields from a SYN or SYNACK message received from the entity at the far end of the link.
o “更新对等验证器”操作定义为存储从链路远端的实体接收到的SYN或SYNACK消息中的发送方实例、发送方端口、发送方名称和分区ID字段的值。
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, Sender Name and Partition ID fields in the incoming message match the values stored from a previous message by the "Update Peer Verifier" operation.
B传入消息中的发送方实例、发送方端口、发送方名称和分区ID字段与“更新对等验证程序”操作从以前的消息中存储的值相匹配。
C The Receiver Instance, Receiver Port, Receiver Name and Partition ID fields in the incoming message match the values of the Sender Instance, Sender Port, Sender Name and Partition ID currently sent in outgoing SYN, SYNACK, and ACK messages.
C传入消息中的接收方实例、接收方端口、接收方名称和分区ID字段与传出SYN、SYNACK和ACK消息中当前发送的发送方实例、发送方端口、发送方名称和分区ID的值匹配。
"&&" 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 synchronisation 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 synchronisation is achieved, will be discarded.
o 当协议达到ESTAB状态时，链路上的状态同步被认为是实现的。在实现同步之前接收到的所有GSMP消息（邻接协议消息除外）将被丢弃。
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 synchronisation 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。
Each instance of a [switch controller-switch partition] pair will need to establish adjacency synchronisation independently.
[switch controller switch partition]对的每个实例都需要独立地建立邻接同步。
Part of the process of establishing synchronisation when using partition will be to establish the assignment of partition identifiers. The following scenarios are provided for:
使用分区时建立同步的过程的一部分是建立分区标识符的分配。提供了以下场景：
- A controller can request a specific partition ID by setting the PType to Fixed Partition Request.
- 控制器可以通过将PType设置为Fixed partition request来请求特定的分区ID。
- A controller can let the switch decide whether it wants to assign a fixed partition ID or not, by setting the PType to No Partition.
- 通过将PType设置为No partition，控制器可以让交换机决定是否要分配固定的分区ID。
- A switch can assign the specific Partition ID to the session by setting the PType to Fixed Partition Assigned. A switch can specify that no partitions are handled in the session by setting the PType to No Partition.
- 交换机可以通过将PType设置为Fixed Partition Assigned，将特定分区ID分配给会话。通过将PType设置为no Partition，交换机可以指定会话中不处理任何分区。
The assignment is determined by the following behaviour:
分配由以下行为决定：
- An adjacency message from a controller with PType = 1 and Code = SYN SHOULD be treated as a partition request.
- 来自PType=1且Code=SYN的控制器的邻接消息应视为分区请求。
- An adjacency message from a switch with PType = 2 and Code = SYN SHOULD be treated as a partition assignment.
- 来自PType=2且Code=SYN的交换机的邻接消息应视为分区分配。
- An adjacency message from a controller or a switch with PType = 2 and Code = (SYNACK || ACK) SHOULD be treated as a success response, the partition is assigned.
- 当分配分区时，来自控制器或PType=2且Code=（SYNACK | | ACK）的相邻消息应视为成功响应。
- An adjacency message from a controller with PType = 0 and Code = SYN indicates that the controller has not specified if it requests partitions or not.
- 来自PType=0且Code=SYN的控制器的邻接消息表示该控制器未指定是否请求分区。
- An adjacency message from a switch with PType = 0 and Code = SYN indicates that the switch does not support partitions.
- 来自PType=0且Code=SYN的交换机的邻接消息表示该交换机不支持分区。
- An adjacency message from a controller or a switch with PType = 0 and Code = (SYNACK || ACK) indicates that the session does not support partitions.
- 来自PType=0且Code=（SYNACK | | ACK）的控制器或交换机的邻接消息表示会话不支持分区。
- An adjacency message from a controller or a switch with PType = (1 || 2) and Code = RSTACK indicates that requested Partition ID is unavailable.
- 来自控制器或开关的PType=（1 | | 2）且Code=RSTACK的邻接消息表示请求的分区ID不可用。
- An adjacency message from a controller or a switch with PType = 0 and Code = RSTACK indicates that an unidentified error has occurred. The session SHOULD be reset.
- 来自控制器或PType=0且Code=RSTACK的交换机的邻接消息表示发生了未识别的错误。应重置会话。
All other combinations of PType and Code are undefined in this version of GSMP.
此版本的GSMP中未定义所有其他类型和代码的组合。
If after synchronisation 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 synchronisation may be declared.
如果在实现同步后，在超过传入邻接协议消息中宣布的计时器字段值三倍的任何时间段内未接收到有效的GSMP消息，则可宣布同步丢失。
While re-establishing synchronisation with a controller, a switch SHOULD maintain its connection state, deferring the decision about resetting the state until after synchronisation is re-established.
当与控制器重新建立同步时，交换机应保持其连接状态，将重置状态的决定推迟到重新建立同步之后。
Once synchronisation is re-established the decision about resetting the connection state SHOULD be made on the following basis:
重新建立同步后，应根据以下基础决定重置连接状态：
- If PFLAG = 1, then a new adjacency has been established and the state SHOULD be reset
- 如果PFLAG=1，则已建立新的邻接，且应重置状态
- If PFLAG = 2, then adjacency has been re-established and the connection state SHOULD be retained. Verification that controller and connection state are the same is the responsibility of the controller.
- 如果PFLAG=2，则已重新建立邻接关系，并且应保留连接状态。验证控制器和连接状态是否相同是控制器的责任。
Multiple switch controllers may jointly control a single switch partition. The controllers may control a switch partition either in a primary/standby fashion or as part of multiple controllers providing load-sharing for the same partition. It is the responsibility of the controllers to co-ordinate their interactions
多个交换机控制器可以联合控制单个交换机分区。控制器可以主/备用方式控制交换机分区，或者作为多个控制器的一部分，为同一分区提供负载共享。控制员有责任协调他们之间的互动
with the switch partition. In order to assist the controllers in tracking multiple controller adjacencies to a single switch partition, the Adjacency Update message is used to inform a controller that there are other controllers interacting with the same partition. It should be noted that the GSMP does not include features that allow the switch to co-ordinate cache synchronization information among controllers. The switch partition will service each command it receives in turn as if it were interacting with a single controller. Controller implementations without controller entity synchronisation SHOULD NOT use multiple controllers with a single switch partition.
使用交换机分区。为了帮助控制器跟踪单个交换机分区的多个控制器邻接，邻接更新消息用于通知控制器有其他控制器与同一分区交互。应该注意的是，GSMP不包括允许交换机在控制器之间协调缓存同步信息的功能。交换机分区将依次为它接收的每个命令提供服务，就像它与单个控制器交互一样。没有控制器实体同步的控制器实现不应使用带有单个交换机分区的多个控制器。
The first adjacency for a specific partition is determined by the procedures described in section 11.2 and an Adjacency Update message will be sent. The next adjacencies to the partition are identified by a new partition request with the same Partition ID as the first one but with the different Sender Name. Upon establishing adjacency the Adjacency count will be increased and an Adjacency Update message will be sent.
特定分区的第一个邻接由第11.2节中描述的程序确定，并将发送邻接更新消息。分区的下一个邻接由一个新的分区请求标识，该请求与第一个请求具有相同的分区ID，但发送方名称不同。建立邻接后，邻接计数将增加，并发送邻接更新消息。
When adjacency between one partition and a controller is lost, the adjacency count will be decremented and an Adjacency Update message will be sent.
当一个分区和控制器之间的邻接丢失时，邻接计数将减少，并发送邻接更新消息。
Example:
例子：
A switch partition has never been used. When the first controller (A) achieves adjacency, an adjacency count will be initiated and (A) will get an Adjacency Update message about itself with Code field = 1. Since (A) receives an adjacency count of 1 this indicates that it is the only controller for that partition.
从未使用过交换机分区。当第一个控制器（A）实现邻接时，将启动邻接计数，并且（A）将获得关于其自身的邻接更新消息，代码字段=1。由于（A）接收到邻接计数为1，这表明它是该分区的唯一控制器。
When a second adjacency (B), using the same Partition ID, achieves adjacency, the adjacency counter will be increased by 1. Both (A) and (B) will receive an Adjacency Update message indicating an adjacency count of 2 in the Code field. Since the count is greater than 1, this will indicate to both (A) and (B) that there is another controller interacting with the switch; identification of the other controller will not be provided by GSMP, but will be the responsibility of the controllers.
当使用相同分区ID的第二个邻接（B）实现邻接时，邻接计数器将增加1。（A）和（B）都将收到邻接更新消息，指示代码字段中的邻接计数为2。由于计数大于1，这将向（A）和（B）表明有另一个控制器与交换机交互；GSMP不提供其他控制器的标识，但由控制器负责。
If (A) looses adjacency, the adjacency count will be decreased and an Adjacency Update message will be sent to (B) indicating an adjacency count of 1 in the Code field. If (B) leaves as well, the partition is regarded as idle and the adjacency count may be reset.
如果（A）失去邻接，邻接计数将减少，并向（B）发送邻接更新消息，指示代码字段中的邻接计数为1。如果（B）也离开，则分区被视为空闲，邻接计数可能被重置。
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），代码字段给出故障代码。故障代码指定交换机无法满足请求消息的原因。
A warning response message is a success response (Result = 3) with the Code field specifying the warning code. The warning code specifies a warning that was generated during the successful operation.
警告响应消息是成功响应（结果=3），代码字段指定警告代码。警告代码指定在成功操作期间生成的警告。
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 a changed state.)
如果交换机发出故障响应以响应请求消息，则不应因导致故障的消息而更改交换机的状态。（对于包含多个请求的请求消息，例如Delete Branchs消息，failure response消息将指定哪些请求成功，哪些请求失败。成功的请求可能会导致状态更改。）
If the switch issues a failure response it MUST choose the most specific failure code according to the following precedence:
如果交换机发出故障响应，则必须根据以下优先级选择最具体的故障代码：
- Invalid Message
- 无效消息
- General Message Failure
- 一般消息失败
- Specific Message Failure A failure response specified in the text defining the message type.
- 特定消息故障在定义消息类型的文本中指定的故障响应。
- Connection Failures
- 连接故障
- Virtual Path Connection Failures
- 虚拟路径连接失败
- Multicast Failures
- 多播失败
- QoS Failures
- QoS故障
- General Failures
- 一般故障
- Warnings
- 警告
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 and warning 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会话中运行的协议版本中定义的值。
4: 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.
4:一个或多个指定端口不存在。消息中指定的至少一个端口无效。如果端口不存在或已从交换机中删除，则该端口无效。
5: 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.
5:端口会话号无效。端口会话号字段中给定的值与指定端口的当前端口会话号不匹配。
7: Invalid Partition ID The value given in the Partition ID field is not legal for this partition.
7:分区ID无效分区ID字段中给定的值对此分区不合法。
General Message Failure
一般消息失败
10: The meaning of this failure is dependent upon the particular message type and is specified in the text defining the message.
10：此故障的含义取决于特定的消息类型，并在定义消息的文本中指定。
Specific Message Failure - A failure response that is only used by a specific message type
特定消息故障-仅由特定消息类型使用的故障响应
- Failure response messages used by the Label Range message
- 标签范围消息使用的故障响应消息
40: Cannot support one or more requested label ranges.
40:无法支持一个或多个请求的标签范围。
41: Cannot support disjoint label ranges.
41:无法支持不相交的标签范围。
42: Specialised multipoint labels not supported.
42：不支持专用多点标签。
- Failure response messages used by the Set Transmit Data Rate function of the Port Management message
- 端口管理消息的设置传输数据速率功能使用的故障响应消息
43: The transmit data rate of this output port cannot be changed.
43:无法更改此输出端口的传输数据速率。
44: Requested transmit data rate out of range for this output port. The transmit data rate of the requested output port can be changed, but the value of the Transmit Data Rate field is beyond the range of acceptable values.
44:请求的传输数据速率超出此输出端口的范围。可以更改请求输出端口的传输数据速率，但传输数据速率字段的值超出可接受值的范围。
- Failure response message of the Port Management message
- 端口管理消息的故障响应消息
45: Connection Replace mechanism not supported on switch. The R-flag SHOULD be reset in the Response Port Management message.
45：开关上不支持连接更换机构。应在响应端口管理消息中重置R标志。
- Failure response message range reserved for the ARM extension
- 为臂扩展保留的故障响应消息范围
128-159: These failure response codes will be interpreted according to definitions provided by the model description.
128-159：这些故障响应代码将根据模型说明提供的定义进行解释。
Connection Failures
连接故障
11: The specified connection does not exist. An operation that expects a connection to be specified cannot locate the specified connection. A connection is specified by the input port and input label on which it originates. An ATM virtual path connection is specified by the input port and input VPI on which it originates.
11:指定的连接不存在。期望指定连接的操作找不到指定的连接。连接由其发起的输入端口和输入标签指定。ATM虚拟路径连接由其发起的输入端口和输入VPI指定。
12: The specified branch does not exist. An operation that expects a branch of an existing connection to be specified cannot locate the specified branch. A branch of a connection is specified by the connection it belongs to and the output port and output label on which it departs. A branch of an ATM virtual path connection is specified by the virtual path connection it belongs to and the output port and output VPI on which it departs.
12:指定的分支不存在。期望指定现有连接的分支的操作找不到指定的分支。连接的分支由其所属的连接及其离开的输出端口和输出标签指定。ATM虚拟路径连接的分支由其所属的虚拟路径连接及其离开的输出端口和输出VPI指定。
13: One or more of the specified Input Labels is invalid.
13:一个或多个指定的输入标签无效。
14: One or more of the specified Output Labels is invalid.
14:一个或多个指定的输出标签无效。
15: Point-to-point bi-directional connection already exists. The connection specified by the Input Port and Input Label fields already exists, and the bi-directional Flag in the Flags field is set.
15:点对点双向连接已存在。输入端口和输入标签字段指定的连接已存在，并且已设置标志字段中的双向标志。
16: Invalid Service Selector field in a Connection Management message. The value of the Service Selector field is invalid.
16:连接管理消息中的服务选择器字段无效。服务选择器字段的值无效。
17: Insufficient resources for QoS Profile. The resources requested by the QoS Profile in the Service Selector field are not available.
17:用于QoS配置文件的资源不足。服务选择器字段中QoS配置文件请求的资源不可用。
18: Insufficient Resources. Switch resources needed to establish a branch are not available.
18：资源不足。建立分支所需的交换机资源不可用。
20: Reservation ID out of Range The numerical value of Reservation ID is greater than the value of Max Reservations (from the Switch Configuration message).
20:保留ID超出范围保留ID的数值大于最大保留值（来自交换机配置消息）。
21: Mismatched reservation ports The value of Input Port differs from the input port specified in the reservation or the value of Output Port differs from the output port specified in the reservation.
21:保留端口不匹配输入端口的值与保留中指定的输入端口不同，或输出端口的值与保留中指定的输出端口不同。
22: Reservation ID in use The value of Reservation ID matches that of an extant Reservation.
22:正在使用的保留ID保留ID的值与现有保留的值匹配。
23: Non-existent reservation ID No reservation corresponding to Reservation ID exists.
23:不存在保留ID不存在与保留ID对应的保留。
36: Replace of connection is not activated on switch. Only applicable for Add Branch messages. The Replace Connection mechanism has not been activated on port by the Port Management message.
36：开关上未激活连接的更换。仅适用于添加分支消息。端口管理消息未在端口上激活替换连接机制。
37: Connection replacement mode cannot be combined with Bi-directional or Multicast mode. The R flag MUST NOT be used in conjunction with either the M flag or the B flag.
37:连接替换模式不能与双向或多播模式组合。R标志不得与M标志或B标志一起使用。
ATM Virtual Path Connections
ATM虚拟路径连接
24: ATM virtual path switching is not supported on this input port.
24:此输入端口不支持ATM虚拟路径交换。
25: Point-to-multipoint ATM 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 ATM virtual path connections.
25：请求的输入端口或请求的输出端口均不支持点对多点ATM虚拟路径连接。请求的一个或两个输入和输出端口无法支持点对多点ATM虚拟路径连接。
26: Attempt to add an ATM 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 ATM virtual path connections on the same point-to-multipoint connection.
26:尝试将ATM虚拟路径连接分支添加到现有虚拟通道连接。在同一点对多点连接上，将作为虚拟通道连接交换的分支与作为ATM虚拟路径连接交换的分支混合使用是无效的。
27: Attempt to add an ATM virtual channel connection branch to an existing ATM virtual path connection. It is invalid to mix branches switched as virtual channel connections with branches switched as ATM virtual path connections on the same point-to-multipoint connection.
27:尝试将ATM虚拟通道连接分支添加到现有ATM虚拟路径连接。在同一点对多点连接上，将作为虚拟通道连接交换的分支与作为ATM虚拟路径连接交换的分支混合使用是无效的。
28: ATM Virtual path switching is not supported on non-ATM ports. One or both of the requested input and output ports is not an ATM port. ATM virtual path switching is only supported on ATM ports.
28:非ATM端口上不支持ATM虚拟路径交换。请求的一个或两个输入和输出端口不是ATM端口。ATM虚拟路径交换仅在ATM端口上受支持。
Multicast Failures
多播失败
29: 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.
29:已在指定的输出端口上建立了属于指定的点对多点连接的分支，并且交换机不能在同一输出端口上支持任何点对多点连接的多个分支。
30: The limit on the maximum number of multicast connections that the switch can support has been reached.
30:已达到交换机可支持的最大多播连接数限制。
31: The limit on the maximum number of branches that the specified multicast connection can support has been reached.
31:已达到指定多播连接可支持的最大分支数限制。
32: Cannot label each output branch of a point-to-multipoint tree with a different label. Some switch designs, require all output branches of a point-to-multipoint connection to use the same value of Label.
32:无法使用不同的标签标记点对多点树的每个输出分支。某些交换机设计要求点对多点连接的所有输出分支使用相同的标签值。
33: Cannot add multi-point branch to bi-directional connection. It is an error to attempt to add an additional branch to an existing connection with the bi-directional flag set.
33:无法将多点分支添加到双向连接。尝试使用双向标志集向现有连接添加其他分支是错误的。
34: Unable to assign the requested Label value to the requested branch on the specified multicast connection. Although the requested Labels are valid, the switch is unable to support the request using the specified Label values for some reason not covered by the above failure responses. This message implies that a valid value of Labels exists that the switch could support. For example, some switch designs restrict the number of distinct Label values available to a multicast connection. (Most switch designs will not require this message.)
34:无法在指定的多播连接上将请求的标签值分配给请求的分支。尽管请求的标签有效，但由于上述故障响应未涵盖的某些原因，交换机无法使用指定的标签值支持请求。此消息表示存在开关可以支持的有效标签值。例如，某些交换机设计限制多播连接可用的不同标签值的数量。（大多数交换机设计不需要此消息。）
35: General problem related to the manner in which multicast 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.)
35：与交换机支持多播的方式有关的一般问题。如果没有更具体的多播失败消息应用，请使用此消息。（大多数交换机设计不需要此消息。）
QoS Failures
QoS故障
60-79: These failure response codes will be interpreted according to definitions provided by the model description.
60-79：这些故障响应代码将根据模型说明提供的定义进行解释。
80: Switch does not support different QoS parameters for different branches within a multipoint connection.
80:交换机不支持多点连接中不同分支的不同QoS参数。
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:一个或多个指定端口关闭。如果端口状态不可用，则端口关闭。允许在不可用的端口上进行连接管理、连接状态、端口管理和配置操作。不允许在不可用且将生成此故障响应的端口上执行连接活动和统计操作。在已处于不可用状态的端口上指定取下功能的端口管理消息也将生成此故障响应。
19: Out of resources. The switch has exhausted a resource not covered by a more specific failure message, for example, running out of memory.
19：资源不足。交换机耗尽了未被更具体的故障消息覆盖的资源，例如，内存不足。
1: Unspecified reason not covered by other failure codes. The failure message of last resort.
1：其他故障代码未涵盖的未指定原因。最后的失败信息。
Warnings
警告
46: One or more labels are still used in the previous Label Range.
46:一个或多个标签仍在以前的标签范围内使用。
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: One or more of the specified ports does not exist. 5: Invalid Port Session Number. 6: One or more of the specified ports is down. 7: Invalid Partition ID. 10: General message failure. (The meaning of this failure code depends upon the Message Type. It is defined within the description of any message that uses it.) 11: The specified connection does not exist. 12: The specified branch does not exist. 13: One or more of the specified Input Labels is invalid. 14: One or more of the specified Output Labels is invalid. 15: Point-to-point bi-directional connection already exists. 16: Invalid service selector field in a connection management message. 17: Insufficient resources for QoS profile. 18: Insufficient resources. 19: Out of resources (e.g., memory exhausted, etc.). 20: Reservation ID out of Range 21: Mismatched reservation ports 22: Reservation ID in use 23: Non-existent reservation ID 24: ATM virtual path switching is not supported on this input port. 25: Point-to-multipoint ATM virtual path connections are not supported on either the requested input port or the requested output port. 26: Attempt to add an ATM virtual path connection branch to an existing virtual channel connection. 27: Attempt to add an ATM virtual channel connection branch to an existing virtual path connection. 28: ATM Virtual Path switching is not supported on non-ATM ports.
1：其他故障代码未涵盖的未指定原因。2：无效的请求消息。3:指定的请求未在此交换机上实现。4:一个或多个指定端口不存在。5:端口会话号无效。6:一个或多个指定端口关闭。7：分区ID无效。10：一般消息失败。（此故障代码的含义取决于消息类型。它在使用它的任何消息的描述中定义。）11:指定的连接不存在。12:指定的分支不存在。13:一个或多个指定的输入标签无效。14:一个或多个指定的输出标签无效。15:点对点双向连接已存在。16:连接管理消息中的服务选择器字段无效。17:用于QoS配置文件的资源不足。18：资源不足。19：资源不足（例如，内存耗尽等）。20:保留ID超出范围21:不匹配的保留端口22:使用中的保留ID 23:不存在的保留ID 24:此输入端口不支持ATM虚拟路径交换。25：请求的输入端口或请求的输出端口均不支持点对多点ATM虚拟路径连接。26:尝试将ATM虚拟路径连接分支添加到现有虚拟通道连接。27:尝试将ATM虚拟通道连接分支添加到现有虚拟路径连接。28:非ATM端口上不支持ATM虚拟路径交换。
29: 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.
30: The limit on the maximum number of point-to-multipoint
connections that the switch can support has been
reached.
31: The limit on the maximum number of branches that the
specified point-to-multipoint connection can support has
been reached.
32: Cannot label each output branch of a point-to-multipoint
tree with a different label.
33: Cannot add multi-point branch to bi-directional
connection.
34: Unable to assign the requested Label value to the
requested branch on the specified point-to-multipoint
connection.
35: General problem related to the manner in which point-to-
multipoint is supported by the switch.
36: Replace of connection is not activated on switch.
37: Connection replacement mode cannot be combined with Bi-
directional or Multicast mode.
40: Cannot support one or more requested label ranges.
41: Cannot support disjoint label ranges.
42: Specialised multipoint labels not supported.
43: The transmit data rate of this output port cannot be
changed.
44: Requested transmit data rate out of range for this output
port.
45: Connection Replace mechanism not supported on switch.
46: Labels are still used in the existing Label Range.
60-79: Reserved for QoS failures.
80: Switch does not support different QoS parameters for
different branches within a multipoint connection.
128-159: Reserved for the ARM extensions.
29: 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.
30: The limit on the maximum number of point-to-multipoint
connections that the switch can support has been
reached.
31: The limit on the maximum number of branches that the
specified point-to-multipoint connection can support has
been reached.
32: Cannot label each output branch of a point-to-multipoint
tree with a different label.
33: Cannot add multi-point branch to bi-directional
connection.
34: Unable to assign the requested Label value to the
requested branch on the specified point-to-multipoint
connection.
35: General problem related to the manner in which point-to-
multipoint is supported by the switch.
36: Replace of connection is not activated on switch.
37: Connection replacement mode cannot be combined with Bi-
directional or Multicast mode.
40: Cannot support one or more requested label ranges.
41: Cannot support disjoint label ranges.
42: Specialised multipoint labels not supported.
43: The transmit data rate of this output port cannot be
changed.
44: Requested transmit data rate out of range for this output
port.
45: Connection Replace mechanism not supported on switch.
46: Labels are still used in the existing Label Range.
60-79: Reserved for QoS failures.
80: Switch does not support different QoS parameters for
different branches within a multipoint connection.
128-159: Reserved for the ARM extensions.
The security of GSMP's TCP/IP control channel has been addressed in [15]. For all uses of GSMP over an IP network it is REQUIRED that GSMP be run over TCP/IP using the security considerations discussed in [15].
GSMP的TCP/IP控制通道的安全性已在[15]中说明。对于通过IP网络使用GSMP的所有情况，需要使用[15]中讨论的安全注意事项通过TCP/IP运行GSMP。
Appendix A Summary of Messages
附录A信息摘要
Message Name Message Number Status
消息名称消息编号状态
Connection Management Messages
Add Branch .......................16
ATM Specific - VPC.............26
Delete Tree.......................18
Verify Tree.......................19 Obsoleted
Delete All Input..................20
Delete All Output.................21
Delete Branches...................17
Move Output Branch................22
ATM Specific - VPC............27
Move Input Branch.................23
ATM Specifc - VPC............28
Connection Management Messages
Add Branch .......................16
ATM Specific - VPC.............26
Delete Tree.......................18
Verify Tree.......................19 Obsoleted
Delete All Input..................20
Delete All Output.................21
Delete Branches...................17
Move Output Branch................22
ATM Specific - VPC............27
Move Input Branch.................23
ATM Specifc - VPC............28
Port Management Messages
Port Management...................32
Label Range.......................33
Port Management Messages
Port Management...................32
Label Range.......................33
State and Statistics Messages
Connection Activity...............48
Port Statistics...................49
Connection Statistics.............50
QoS Class Statistics..............51 Reserved
Report Connection State...........52
State and Statistics Messages
Connection Activity...............48
Port Statistics...................49
Connection Statistics.............50
QoS Class Statistics..............51 Reserved
Report Connection State...........52
Configuration Messages
Switch Configuration..............64
Port Configuration................65
All Ports Configuration...........66
Service Configuration.............67
Configuration Messages
Switch Configuration..............64
Port Configuration................65
All Ports Configuration...........66
Service Configuration.............67
Reservation Messages
Reservation Request...............70
Delete Reservation................71
Delete All Reservations...........72
Reservation Messages
Reservation Request...............70
Delete Reservation................71
Delete All Reservations...........72
Event Messages
Port Up...........................80
Port Down.........................81
Invalid Label.....................82
New Port..........................83
Dead Port.........................84
Event Messages
Port Up...........................80
Port Down.........................81
Invalid Label.....................82
New Port..........................83
Dead Port.........................84
Abstract and Resource Model Extension Messages
Reserved..........................200-249
Abstract and Resource Model Extension Messages
Reserved..........................200-249
Adjacency Protocol....................10 Required
Adjacency Protocol....................10 Required
Appendix B IANA Considerations
附录B IANA注意事项
Following the policies outlined in "Guidelines for Writing an IANA Considerations Section in RFCs" (RFC 2434 [19]), the following name spaces are defined in GSMPv3.
按照“在RFCs中编写IANA注意事项部分的指南”（RFC 2434[19]）中概述的策略，GSMPv3中定义了以下名称空间。
- Message Type Name Space [Appendix A]
- 消息类型名称空间[附录A]
- Label Type Name Space [3.1.3]
- 标签类型名称空间[3.1.3]
- Result Name Space [3.1.1]
- 结果名称空间[3.1.1]
- Failure Response Message Name Space [3.1.4],[11]
- 故障响应消息名称空间[3.1.4]，[11]
- Adaptation Type Name Space [4.1]
- 自适应类型名称空间[4.1]
- Model Type Name Space [8.1]
- 模型类型名称空间[8.1]
- Port Type Name Space [8.2]
- 端口类型名称空间[8.2]
- Service ID Name Space [10.4]
- 服务ID名称空间[10.4]
- Traffic Control Name Space [8.4]
- 交通管制名称空间[8.4]
- Event Flag Name Space [6.1]
- 事件标志名称空间[6.1]
GSMPv3 divides the name space for Message Types into four ranges. The following are the guidelines for managing these ranges.
GSMPv3将消息类型的名称空间划分为四个范围。以下是管理这些范围的指南。
- Message Types 0-99. Message Types in this range are part of the GSMPv3 base protocol. Message types in this range are allocated through an IETF consensus action [19].
- 消息类型为0-99。此范围内的消息类型是GSMPv3基本协议的一部分。此范围内的消息类型通过IETF一致行动分配[19]。
- Message Types 100-199. Message Types in this range are Specification Required [19]. Message Types using this range must be documented in an RFC or other permanent and readily available references.
- 消息类型100-199。此范围内的消息类型是规范要求的[19]。使用此范围的消息类型必须记录在RFC或其他永久且随时可用的参考文件中。
- Message Types 200-249. Message Types in this range are Specification Required [19] and are intended for Abstract and Resource Model Extension Messages. Message Types using this range must be documented in an RFC or other permanent and readily available references.
- 消息类型200-249。此范围内的消息类型是规范要求的[19]，用于抽象和资源模型扩展消息。使用此范围的消息类型必须记录在RFC或其他永久且随时可用的参考文件中。
- Message Types 250-255. Message Types in this range are reserved for vendor private extensions and are the responsibility of individual vendors. IANA management of this range of the Message Type Name Space is unnecessary.
- 消息类型250-255。此范围内的消息类型是为供应商专用扩展保留的，由各个供应商负责。IANA不需要管理此范围的消息类型名称空间。
GSMPv3 divides the name space for Label Types into three ranges. The following are the guidelines for managing these ranges.
GSMPv3将标签类型的名称空间划分为三个范围。以下是管理这些范围的指南。
- Label Types 0x000-0xAFF. Label Types in this range are part of the GSMPv3 base protocol. Label Types in this range are allocated through an IETF consensus action [19].
- 标签类型0x000-0xAFF。此范围内的标签类型是GSMPv3基本协议的一部分。此范围内的标签类型通过IETF一致行动分配[19]。
- Label Types 0xB00-0xEFF. Label Types in this range are Specification Required [19]. Label Types using this range must be documented in an RFC or other permanent and readily available reference.
- 标签类型0xB00-0xEFF。此范围内的标签类型是规范要求的[19]。使用此范围的标签类型必须记录在RFC或其他永久性且随时可用的参考文件中。
- Label Types 0xF00-0xFFF. Label Types in this range are reserved for vendor private extensions and are the responsibility of individual vendors. IANA management of this range of the Label Type Name Space is unnecessary.
- 标签类型0xF00-0xFFF。此范围内的标签类型是为供应商专用扩展保留的，由各个供应商负责。IANA不需要管理此范围的标签类型名称空间。
The following is the guideline for managing the Result Name Space:
以下是管理结果名称空间的指南：
- Result values 0-255. Result values in this range need an expert review, i.e., approval by a Designated Expert is required [19].
- 结果值为0-255。该范围内的结果值需要专家审查，即需要指定专家的批准[19]。
GSMPv3 divides the name space for Failure Responses into three ranges. The following are the guidelines for managing these ranges:
GSMPv3将故障响应的名称空间划分为三个范围。以下是管理这些范围的指南：
- Failure Responses 0-59, 80-127, 160-255. Failure responses in these ranges are part of the GSMPv3 base protocol. Failure Responses in these ranges are allocated through an IETF consensus action [19].
- 故障响应0-59、80-127、160-255。这些范围内的故障响应是GSMPv3基本协议的一部分。这些范围内的故障响应通过IETF一致行动分配[19]。
- Failure Responses 60-79, 128-159. Failure responses in these ranges are reserved for vendor private extensions and are the responsibility of individual vendors. IANA management of these ranges of the Failure Response Name Space are unnecessary.
- 故障响应60-79、128-159。这些范围内的故障响应保留给供应商专用扩展，由各个供应商负责。IANA对这些故障响应名称空间范围的管理是不必要的。
GSMPv3 divides the name space for Adaptation Types into two ranges. The following are the guidelines for managing these ranges:
GSMPv3将适配类型的名称空间划分为两个范围。以下是管理这些范围的指南：
- Adaptation Type 0x000-0x2FF. Adaptation Types in this range are part of the GSMPv3 base protocol. Adaptation Types in this range are allocated through an IETF consensus action [19].
- 自适应类型0x000-0x2FF。此范围内的自适应类型是GSMPv3基本协议的一部分。该范围内的适应类型通过IETF共识行动分配[19]。
- Adaptation Type 0x300-0xFFF. Adaptation Types in this range are allocated by the first come first served principle [19].
- 自适应类型0x300-0xFFF。此范围内的适应类型按照先到先得原则分配[19]。
GSMPv3 divides the name space for Model Types into three ranges. The following are the guidelines for managing these ranges:
GSMPv3将模型类型的名称空间划分为三个范围。以下是管理这些范围的指南：
- Model Type 0. Model Types in this range are part of the GSMPv3 base protocol. Model Types in this range are allocated through an IETF consensus action [19].
- 模型类型0。此范围内的型号是GSMPv3基本协议的一部分。该范围内的模型类型通过IETF共识行动分配[19]。
- Model Type 1-200. Model Types in this range are Specification Required [19]. Message Types using this range must be documented in an RFC or other permanent and readily available references.
- 型号1-200。此范围内的型号为所需规格[19]。使用此范围的消息类型必须记录在RFC或其他永久且随时可用的参考文件中。
- Model Type 201-255. Model Types in this range are reserved for vendor private extensions and are the responsibility of individual vendors. IANA management of these ranges of the Model Type Name Space are unnecessary.
- 型号201-255。此范围内的模型类型是为供应商专用扩展保留的，由各个供应商负责。IANA对这些模型类型名称空间范围的管理是不必要的。
GSMPv3 divides the name space for Port Types into two ranges. The following are the guidelines for managing these ranges:
GSMPv3将端口类型的名称空间划分为两个范围。以下是管理这些范围的指南：
- Port Type 0-127. Port Types in this range are part of the GSMPv3 base protocol. Port Types in this range are allocated through an IETF consensus action [19].
- 端口类型0-127。此范围内的端口类型是GSMPv3基本协议的一部分。此范围内的端口类型通过IETF一致行动分配[19]。
- Port Type 128-255. Port Types in this range are Specification Required [19]. Port Types using this range must be documented in an RFC or other permanent and readily available references.
- 端口类型128-255。此范围内的端口类型是规范要求的[19]。使用此范围的端口类型必须记录在RFC或其他永久且随时可用的参考文件中。
GSMPv3 divides the name space for Service IDs into two ranges. The following are the guidelines for managing these ranges:
GSMPv3将服务ID的名称空间划分为两个范围。以下是管理这些范围的指南：
- Service ID 0-1023. Service ID's in this range are part of the GSMPv3 base protocol. Service ID's in this range are allocated through an IETF consensus action [19].
- 服务ID 0-1023。此范围内的服务ID是GSMPv3基本协议的一部分。此范围内的服务ID通过IETF一致行动分配[19]。
- Service ID 1024-65535. Service ID's in this range are Specification Required [19]. Service ID's using this range must be documented in an RFC or other permanent and readily available references.
- 服务ID 1024-65535。此范围内的服务ID是规范要求的[19]。使用此范围的服务ID必须记录在RFC或其他永久且随时可用的参考文件中。
The following are the guidelines for managing Traffic Control Flags in GSMPv3:
以下是GSMPv3中管理交通控制标志的指南：
- All Traffic Control Flags are allocated through an expert review, i.e., approval by a Designated Expert [19].
- 所有交通控制标志都是通过专家审查分配的，即由指定专家批准[19]。
The following are the guidelines for managing Event Flags in GSMPv3:
以下是在GSMPv3中管理事件标志的指南：
- All Event Flags are allocated through an expert review, i.e., approval by a Designated Expert [19].
- 所有事件标志均通过专家评审分配，即由指定专家批准[19]。
The TCP port for establishing GSMP connections has been defined as 6068.
用于建立GSMP连接的TCP端口已定义为6068。
References
工具书类
[1] "B-ISDN ATM Layer Specification", International Telecommunication Union, ITU-T Recommendation I.361, Feb. 1999.
[1] “B-ISDN ATM层规范”，国际电信联盟，ITU-T建议I.3611999年2月。
[2] "B-ISDN ATM Adaptation Layer (AAL) Specification", International Telecommunication Union, ITU-T Recommendation I.363, Mar. 1993.
[2] “B-ISDN ATM适配层（AAL）规范”，国际电信联盟，ITU-T建议I.363，1993年3月。
[3] "B-ISDN ATM Adaptation Layer specification: Type 5 AAL", International Telecommunication Union, ITU-T, Recommendation I.363.5, Aug. 1996.
[3] “B-ISDN ATM适配层规范：5型AAL”，国际电信联盟，ITU-T，建议I.363.5，1996年8月。
[4] Sjostrand, H., Buerkle, J. and B. Srinivasan, "Definitions of Managed Objects for the General Switch Management Protocol (GSMP)", RFC 3295, June 2002.
[4] Sjostrand，H.，Buerkle，J.和B.Srinivasan，“通用交换机管理协议（GSMP）受管对象的定义”，RFC 32952002年6月。
[5] IANA Assigned Port Numbers, http://www.iana.org
[5] IANA Assigned Port Numbers, http://www.iana.org
[6] 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.
[6] Newman，P，Edwards，W.，Hinden，R.，Hoffman，E.Ching Liaw，F.，Lyon，T.和G.Minshall，“Ipsilon的通用交换机管理协议规范版本1.1”，RFC 1987，1996年8月。
[7] Newman, P., Edwards, W., Hinden, R., Hoffman, E., Ching Liaw, F., Lyon, T. and G. Minshall, "Ipsilon's General Switch Management Protocol Specification Version 2.0", RFC 2297, March 1998.
[7] Newman，P.，Edwards，W.，Hinden，R.，Hoffman，E.，Ching Liaw，F.，Lyon，T.和G.Minshall，“Ipsilon的通用交换机管理协议规范版本2.0”，RFC 2297，1998年3月。
[8] ATM Forum Technical Committee, "Traffic Management Specification Version 4.1", af-tm-0121.000, 1999.
[8] ATM论坛技术委员会，“交通管理规范版本4.1”，af-tm-0121.0001999。
[9] Wroclawski, J., "Specification of the Controlled-Load Network Element Service", RFC 2211, September 1997.
[9] Wroclawski，J.，“受控负荷网元服务规范”，RFC2211，1997年9月。
[10] Jamoussi, B., Andersson, L., Callon, R., Dantu, R., Wu, L., Doolan, P., Worster, T., Feldman, N., Fredette, A., Girish, M., Gray, E., Heinanen, J., Kilty, T. and A. Malis, "Constraint-Based LSP Setup using LDP", RFC 3212, January 2002.
[10] Jamoussi，B.，Andersson，L.，Callon，R.，Dantu，R.，Wu，L.，Doolan，P.，Worster，T.，Feldman，N.，Fredette，A.，Girish，M.，Gray，E.，Heinanen，J.，Kilty，T.和A.Malis，“使用LDP的基于约束的LSP设置”，RFC 3212，2002年1月。
[11] ITU-T Recommendation I.233 Frame Mode Bearer Services, ISDN frame relaying bearer services and ISDN switching bearer service, Nov. 1991.
[11] ITU-T建议I.233帧模式承载业务，ISDN帧中继承载业务和ISDN交换承载业务，1991年11月。
[12] ITU-T Recommendation Q.933, Integrated Services Digital Network (ISDN) Digital Subscriber Signaling System No. 1 (DSS 1) Signaling Specifications For Frame Mode Switched And Permanent Virtual Connection Control And Status Monitoring, 1995.
[12] ITU-T建议Q.933，综合业务数字网（ISDN）数字用户信令系统第1号（DSS 1）帧模式交换和永久虚拟连接控制和状态监测信令规范，1995年。
[13] ITU-T Recommendation Q.922, Integrated Services Digital Network (ISDN) Data Link Layer Specification For Frame Mode Bearer Services, 1992
[13] ITU-T建议Q.922，《综合业务数字网（ISDN）帧模式承载业务数据链路层规范》，1992年
[14] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., Farinacci, D., Li, T. and A. Conta, "MPLS Label Stack Encoding", RFC 3032, January 2001.
[14] Rosen，E.，Tappan，D.，Fedorkow，G.，Rekhter，Y.，Farinaci，D.，Li，T.和A.Conta，“MPLS标签堆栈编码”，RFC 3032，2001年1月。
[15] Worster, T., Doria, A. and J. Buerkle, "General Switch Management Protocol (GSMP) Packet Encapsulations for Asynchronous Transfer Mode (ATM), Ethernet and Transmission Control Protocol (TCP)", RFC 3293, June 2002.
[15] Worster，T.，Doria，A.和J.Buerkle，“异步传输模式（ATM）、以太网和传输控制协议（TCP）的通用交换机管理协议（GSMP）数据包封装”，RFC 3293，2002年6月。
[16] Doria, A. and K. Sundell, "General Switch Management Protocol Applicability", RFC 3294, June 2002.
[16] Doria，A.和K.Sundell，“通用交换机管理协议适用性”，RFC 32942002年6月。
[17] IANAifType - MIB DEFINITIONS, http://www.iana.org, January 2001.
[17] IANAifType-MIB定义，http://www.iana.org，2001年1月。
[18] Anderson, L., Doolan, P., Feldman, N., Fredette, A. and B. Thomas, "LDP Specification", RFC 3036, January 2001.
[18] Anderson，L.，Doolan，P.，Feldman，N.，Fredette，A.和B.Thomas，“LDP规范”，RFC 3036，2001年1月。
[19] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.
[19] Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 2434，1998年10月。
[20] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[20] Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[21] Conta, A., Doolan, P. and A. Malis, "Use of Label Switching on Frame Relay Networks Specification", RFC 3034, January 2001.
[21] Conta，A.，Doolan，P.和A.Malis，“帧中继网络上标签切换的使用规范”，RFC 3034，2001年1月。
Authors' Addresses
作者地址
Avri Doria Div. of Computer Communications Lulea University of Technology S-971 87 Lulea Sweden
Lulea科技大学计算机通信系Avri Doria Div. -瑞典87
Phone: +1 401 663 5024
EMail: avri@acm.org
Phone: +1 401 663 5024
EMail: avri@acm.org
Fiffi Hellstrand Nortel Networks AB S:t Eriksgatan 115 A SE-113 85 Stockholm Sweden
Fiffi Hellstrand Nortel Networks AB S:t Eriksgatan 115 A SE-113 85瑞典斯德哥尔摩
EMail: fiffi@nortelnetworks.com
EMail: fiffi@nortelnetworks.com
Kenneth Sundell Nortel Networks AB S:t Eriksgatan 115 A SE-113 85 Stockholm Sweden
Kenneth Sundell Nortel Networks AB S:t Eriksgatan 115 A SE-113 85瑞典斯德哥尔摩
EMail: ksundell@nortelnetworks.com
EMail: ksundell@nortelnetworks.com
Tom Worster
汤姆沃斯特
Phone: +1 617 247 2624
EMail: fsb@thefsb.org
Phone: +1 617 247 2624
EMail: fsb@thefsb.org
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2002). All Rights Reserved.
版权所有（C）互联网协会（2002年）。版权所有。
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.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。